[Q] " no recoveries found for your device" - Sprint HTC EVO 4G LTE

I was going to flash CM 11 today and kept getting this error code" no recoveries found for your device".in twrp!....Anthing i try to flash through twrp fails..could the recovery image itself been corrupted? .. I guess twrp wont recognise my device type ,iTried uninstall re installing twrp a half dozen times but to no avail. tried using search but didnt find anything defininitve,im sure some one has ran across this before ,but its a new one to me ,twrp has always run flawless for me .. any ideas anyone?

Get a fresh copy here http://techerrata.com/browse/twrp2/jewel
After flashing twrp type fastboot erase cache

heliguide62 said:
I was going to flash CM 11 today and kept getting this error code" no recoveries found for your device".in twrp!....Anthing i try to flash through twrp fails..could the recovery image itself been corrupted? .. I guess twrp wont recognise my device type ,iTried uninstall re installing twrp a half dozen times but to no avail. tried using search but didnt find anything defininitve,im sure some one has ran across this before ,but its a new one to me ,twrp has always run flawless for me .. any ideas anyone?
Click to expand...
Click to collapse
Did you use the version of TWRP posted in the OP of the CM11 thread? You have to use it, otherwise the flash will fail.
Sent from my HTC EVO 4G LTE

FinZ28 said:
Did you use the version of TWRP posted in the OP of the CM11 thread? You have to use it, otherwise the flash will fail.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
^This.
I also compiled a version with the updated kernel: http://tinyurl.com/TWRP-Recovery-2-6-3-0-selinux
Essentially the same as deck's, just the font in recovery appears much larger and more readable .

Thanks for the help guys!... but im still not getting it ..twp must be really messed up for me .. i downloaded both versions of twrp ..captain t/backs and the one from topic .. and i cant find either or them in "install" mode of twrp.,however i CAN find them in file manager mode,which is baffling, but when i try to move them to some place flashable they are nowhere to be seen!..i also can see them in ES file explorer and tried to move them that way but same result...maybe my download path is incorrect?..this one has me stumped.. anyone have any advice?

heliguide62 said:
Thanks for the help guys!... but im still not getting it ..twp must be really messed up for me .. i downloaded both versions of twrp ..captain t/backs and the one from topic .. and i cant find either or them in "install" mode of twrp.,however i CAN find them in file manager mode,which is baffling, but when i try to move them to some place flashable they are nowhere to be seen!..i also can see them in ES file explorer and tried to move them that way but same result...maybe my download path is incorrect?..this one has me stumped.. anyone have any advice?
Click to expand...
Click to collapse
You have to flash the image files via fastboot, not through recovery.

no wonder i couldnt do it ..lol..havnt to used fast boot since the og evo days hope i can remember how..

Connect the phone to your pc and boot into bootloader, then go to fastboot.
you can test if your comp sees your phone by using
Code:
fastboot devices
Then, just open up cmd wherever your recovery image is stored (if on pc) by holding shift and right clicking. Then in the code below, replace recovery.img with the name of the recovery file you have.
Code:
fastboot flash recovery recovery.img

sorry if im turning this thread into a fastboot tutorial.. but i have the phone in usb fast boot .. downloaded sdk again and when i type in cmd Fast boot .. i get " not recognized as internal or Internal command".. so its not recognizing phone?

heliguide62 said:
sorry if im turning this thread into a fastboot tutorial.. but i have the phone in usb fast boot .. downloaded sdk again and when i type in cmd Fast boot .. i get " not recognized as internal or Internal command".. so its not recognizing phone?
Click to expand...
Click to collapse
Open the cmd from the platform tools folder

ok so downloaded sdk manager .. and maybe i didn't download the right version or something, but nothing will "open up" in sdk .. perhaps i need some drivers or something?.. cause it shows everything is installed .. tools, platform ect .. what i downloaded dosnt look like anything ive seen looking around the web.

heliguide62 said:
ok so downloaded sdk manager .. and maybe i didn't download the right version or something, but nothing will "open up" in sdk .. perhaps i need some drivers or something?.. cause it shows everything is installed .. tools, platform ect .. what i downloaded dosnt look like anything ive seen looking around the web.
Click to expand...
Click to collapse
This is what I use http://developer.android.com/sdk/index.html

You can also download the version that's included in my Hboot guide (top link in my sig). It's not the entire SDK-just ADB & Fastboot. It's what I use. Just download and install. Once installed, highlight the file & hit Shift+right click on mouse, and you're ready to go.
Sent from my HTC EVO 4G LTE

Related

convert zip to img

hello to all...i am new to this developing. i have a rom file in .zip format....inside it there is system folder. i want to convert this .zip into a system img file. is it possible?? actually i hav a phone on which sdcard is not getting detected. so cwm recovery wont work, niether adb is detecting that device, so i want to make a system img file from this rom so that i can flash it using fastboot. Plz help me
niranjand147 said:
hello to all...i am new to this developing. i have a rom file in .zip format....inside it there is system folder. i want to convert this .zip into a system img file. is it possible?? actually i hav a phone on which sdcard is not getting detected. so cwm recovery wont work, niether adb is detecting that device, so i want to make a system img file from this rom so that i can flash it using fastboot. Plz help me
Click to expand...
Click to collapse
For future reference, at the very least, state the device you have and or are having problems with. Makes things easier for people like me
What your asking for doesn't exist to my knowledge. However, you can extract the contents of the zip to your hard disk and use fastboot to flash the file "boot.img' which should be in the root of the zip you have. Everything else needs to be pushed via ADB to the /system partition. If your CWM is built correctly, ADB should detect your device when connected. That's assuming that you have your drivers installed already.
In reality, I don't think that what you are wanting to do can be done, however I don't know everything either. :silly: Best of luck
bill.weckel said:
For future reference, at the very least, state the device you have and or are having problems with. Makes things easier for people like me
What your asking for doesn't exist to my knowledge. However, you can extract the contents of the zip to your hard disk and use fastboot to flash the file "boot.img' which should be in the root of the zip you have. Everything else needs to be pushed via ADB to the /system partition. If your CWM is built correctly, ADB should detect your device when connected. That's assuming that you have your drivers installed already.
In reality, I don't think that what you are wanting to do can be done, however I don't know everything either. :silly: Best of luck
Click to expand...
Click to collapse
i am trying it for huawei u8180
shinobisoft said:
For future reference, at the very least, state the device you have and or are having problems with. Makes things easier for people like me
What your asking for doesn't exist to my knowledge. However, you can extract the contents of the zip to your hard disk and use fastboot to flash the file "boot.img' which should be in the root of the zip you have. Everything else needs to be pushed via ADB to the /system partition. If your CWM is built correctly, ADB should detect your device when connected. That's assuming that you have your drivers installed already.
In reality, I don't think that what you are wanting to do can be done, however I don't know everything either. :silly: Best of luck
Click to expand...
Click to collapse
I tried this using Livesuit 1.11 for a softwinerEvb a13 tablet (no other known device specs) and it said the image file was invalid. Situation is I soft bricked my tablet by flashing the wrong cwm zip. Finally found out how to connect via Livesuit (kinda like fastboot or bootloader mode or something? like Odin?) to flash stuff to it. I decided to use an erase img .img because where I found how to connect it suggested that to the OP (on techknow). So now instead of the tablet just being stuck on the first screen when trying to boot (normal or recovery), it doesn't do anything at all since there's no boot.img. Which I'm not worried about since It connects to my laptop just fine via livesuit still so I can get a boot on it (ADB won't detect it - pretty positive it's not ADB user error [I run cmd "adb root" when the tablet is connect in whatever mode its in - the way livesuit detects it - and adb says no device found]. BUT I can't find a stock firmware/rom/boot.img for it anywhere (mainly since there's a bunch of clones of this tablet). I'm downloading a few roms (in boot.img format? - .7z files) that I found for "this" tablet (meaning the devs don't know which clones which roms work on lol).
ANYWAY haha, my question is, is there a way to do what you said in the above quote that will work in my situation? I'm not advanced enough to know why livesuit says the image is invalid. I tried it with a cm10.1 zip made for this tablet and a cwm zip made for this tablet (for both I extracted the files and then tried flashing the boot.img I found in the directory(extracted folder right?) via livesuit. livesuit said image file invalid for both .img's.
Please help me and THANK YOU in advance.
I'm open to anyone's help and any help is much appreciated! Thanks buttons will be pressed!!!
Same situation
Same Situation but I know the Specs,, It is allwinner A10 .and Stuck in the soft brick
could you solved this problem? i need a help too, the same problem
---------- Post added at 09:21 PM ---------- Previous post was at 09:13 PM ----------
vennkis said:
Same Situation but I know the Specs,, It is allwinner A10 .and Stuck in the soft brick
Click to expand...
Click to collapse
Hi, could you solved that?
i have a Chinese tablet a10, i have repaired different tablets and android phone trough ADB, but this devices is not detected, i have download some software to help me download the tablet drivers, but hasn't possible that.
finally the only source i have, is charge the firmware again, i use phoenix , and i have some rooms in zip format, what can i do for convert to IMG format?
Hello everyone
Finally what can we do?
How to convert .ZIP to .IMG ?
how to convert?
m.morcielago said:
Hello everyone
Finally what can we do?
How to convert .ZIP to .IMG ?
Click to expand...
Click to collapse
m.morcielago said:
Hello everyone
Finally what can we do?
How to convert .ZIP to .IMG ?
Click to expand...
Click to collapse
hahaha...no answer....i am still waiting for this software
doelwit.sunny said:
hahaha...no answer....i am still waiting for this software
Click to expand...
Click to collapse
You know just converting is not enough
I can convert it
But you need "partition table" for making .IMG
So we don't have it
check sdat2img and imgpatchtools

[Q] LG G2 D802 EE UK bootloop

I'm sorry if this isn't the right place.
I rooted my LG G2 D802 around 2 months ago, and completely forgot about it.
I got the Kitkat update about 5 hours ago, and stupidly downloaded it.
The phone got stuck in a team win bootloop and again, in a bit of a panic I wiped the phone (not thinking of just restoring my back up from when i rooted the device)
after that didn't solve anything, i reverted to google. I found a guide on here for my exact problem http://forum.xda-developers.com/showthread.php?t=2451696
I read it carefully and proceeded to follow this by the letter. I think I messed up though, with the 'ADB' thing, the last i remembered about it was using it to root the device, so I followed to guide but using the root folder i had used. now I'm no longer in a team win bootloop, I'm not in a LG splash screen boot loop, I can just about manage to get into recovery and get back to team win, but can't get into download mode.
I really wasn't looking to replace this device until the LG G3 got released, and don't really have the money to spare - so i'm really hoping this is fixable.
a note is, to root the device i followed a guide, and the TWRP (I'm not actually sure) I think i just went with it and managed it so i'm not very good when it comes to the terms, and stuff like that, any help would be greatly appreciated!
I can use a Win7 laptop to do whatever is needed, it is an EE LG G2 D802, UK, 16GB black.
I don't have insurance, I kept pushing myself to wait to do anything like this until I had insurance, but at 2 in the morning, nothing to do, ready to root - It's hard to resist.
(I do have the USB drivers on my laptop)
Sounds like you are in this boat now:
http://forum.xda-developers.com/showthread.php?t=2582142
That should do the trick since it's exactly what's happened to you and the same phone. The update might be different though as that is important to know. Just use the files from whichever the last official update you had was from.
es0tericcha0s said:
Sounds like you are in this boat now:
http://forum.xda-developers.com/showthread.php?t=2582142
That should do the trick since it's exactly what's happened to you and the same phone. The update might be different though as that is important to know. Just use the files from whichever the last official update you had was from.
Click to expand...
Click to collapse
I dont think thats the same problem as mine, i have no error, my screen doesnt go off, it just stays on lg splash screen with multicoloured led flashing, cant turn it off only restart it, i dont have linux & i can get into recovery with a few attempts. Is there anythjng that can be done or is my phone ****ed? Thanks
I have just had another read through, mainly the comments and that guide seems to get you to the point where you can get into recovery and enter those commands in the guide on my opening post - i can get into recovery and i did both fixes, the one using adb if using the adb in the root folder on my laptop i used to root the device is okay, and then again using the terminal emulator in recovery, after neither worked (actually, the terminal emulator one got me from a TWRP bootloop into an lg splash screen bootloop, after reading into thr comment to about page 7 there was an additional line to the terminal emulator method changing only the /fota to /misc which did nothing for my device. The fix there simply changed the type of bootloop i am in
yoalphadied said:
I dont think thats the same problem as mine, i have no error, my screen doesnt go off, it just stays on lg splash screen with multicoloured led flashing, cant turn it off only restart it, i dont have linux & i can get into recovery with a few attempts. Is there anythjng that can be done or is my phone ****ed? Thanks
Click to expand...
Click to collapse
Oh ok. Well, if you can still get into recovery, then you should be able to push another rom to the phone's storage via adb. But your phone definitely isn't screwed. It's pretty hard to totally mess these things up to the point of no return.
es0tericcha0s said:
Oh ok. Well, if you can still get into recovery, then you should be able to push another rom to the phone's storage via adb. But your phone definitely isn't screwed. It's pretty hard to totally mess these things up to the point of no return.
Click to expand...
Click to collapse
Im glad to hear it, got to the point of looking at a new ouone even though i wanted to keep this one until the g3 was on the shelves.
I hate to say, but how would i do this? I only know the very basics, and is the adb used to root fine to do it with? I didnt even know i had flashed TWRP correctly, think i used an app, flashify or something? Any help would be massively appreciated
yoalphadied said:
Im glad to hear it, got to the point of looking at a new ouone even though i wanted to keep this one until the g3 was on the shelves.
I hate to say, but how would i do this? I only know the very basics, and is the adb used to root fine to do it with? I didnt even know i had flashed TWRP correctly, think i used an app, flashify or something? Any help would be massively appreciated
Click to expand...
Click to collapse
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: https://mega.co.nz/#!rU0RkSaK!JzUCoZ5emWOsc_Tw6h8a3JZtRNT1-JvGvc8EC_u9rnI
adb and fastboot files: https://mega.co.nz/#!SJ8ijCKY!UKpr4ufVyPq4DVL2i90RI9CD7TX5AETPHrcqMQdpG5w
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
es0tericcha0s said:
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: link
adb and fastboot files: link
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
Click to expand...
Click to collapse
Just making sure I understand correctly, the 'rom' i need ks the stock rom, right? Im not looking to root again as the whole reason i rooted was because it was everywhere that ee werent releasing the kitkat update for the g2, since they have now i dont need root anymore.
Ill try this fix later on and tell you if it worked! Thanks
es0tericcha0s said:
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: link
adb and fastboot files: link
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
Click to expand...
Click to collapse
Okay, I can't seem to find the LG G2's stock rom anywhere, also the adb push nameofrom.zip /sdcard/ is that the exact command?
I found the stock firmware, but nothing for EE, just o2 and so on.
I also can't seem to get the drivers to work, I have an 'unidentified device' connected to the computer, I have tried to download from the link you gave me, and another place but neither work, once it searches for drivers again after download it just says drivers not found
saying that after trying 'adb devices' i got a random string of letters and numbers, roughly 21 characters long followed by recovery on the same line
yoalphadied said:
Okay, I can't seem to find the LG G2's stock rom anywhere, also the adb push nameofrom.zip /sdcard/ is that the exact command?
I found the stock firmware, but nothing for EE, just o2 and so on.
I also can't seem to get the drivers to work, I have an 'unidentified device' connected to the computer, I have tried to download from the link you gave me, and another place but neither work, once it searches for drivers again after download it just says drivers not found
saying that after trying 'adb devices' i got a random string of letters and numbers, roughly 21 characters long followed by recovery on the same line
Click to expand...
Click to collapse
Hmm if adb devices returned that, that means adb is working which means at least part of the drivers loaded correctly. I would grab the files from here:
http://forum.xda-developers.com/showthread.php?t=2736854
And then adb push the files to the /sdcard/. You want the Philz recovery, and the rom. You can grab the root and the kernel if you want to be rooted and the kernel might make a difference in battery life and performance. Whether that is a positive or negative influence, I've no clue. The poster seemed to like it, and he would know better than I. So you just want to download the files needed and put them in the same folder where you have your adb files. Then for each one you want to use:
adb push
then
nameoffile.zip - where you fill in the name of file with whatever (you can rename the files - but not extensions - to be easier, ie recovery.zip, rom.zip)
then /sdcard/
Full command of pushing the rom to the internal storage, assuming you renamed it to rom.zip would be:
adb push rom.zip /sdcard/
This will take awhile. Probably a good 10 minutes.
After you get it transferred over, then install the recovery zip in your current recovery and then reboot to recovery again so you will be in the new Philz. Then do a factory reset and install the rom zip.
es0tericcha0s said:
Hmm if adb devices returned that, that means adb is working which means at least part of the drivers loaded correctly. I would grab the files from here:
And then adb push the files to the /sdcard/. You want the Philz recovery, and the rom. You can grab the root and the kernel if you want to be rooted and the kernel might make a difference in battery life and performance. Whether that is a positive or negative influence, I've no clue. The poster seemed to like it, and he would know better than I. So you just want to download the files needed and put them in the same folder where you have your adb files. Then for each one you want to use:
adb push
then
nameoffile.zip - where you fill in the name of file with whatever (you can rename the files - but not extensions - to be easier, ie recovery.zip, rom.zip)
then /sdcard/
Full command of pushing the rom to the internal storage, assuming you renamed it to rom.zip would be:
adb push rom.zip /sdcard/
This will take awhile. Probably a good 10 minutes.
After you get it transferred over, then install the recovery zip in your current recovery and then reboot to recovery again so you will be in the new Philz. Then do a factory reset and install the rom zip.
Click to expand...
Click to collapse
Which of those files should I download.
as I understand it, once downloaded and in the file with the ADB.
adb devices (to make sure it is connected)
then
adb push recovery.zip /sdcard/ (saying recovery if I rename the file, and pushing the recovery is first?)
then straight after do I push the rom, after rebooting the device, or push them both - reboot the device then install the rom from the recovery?
the first file is Open Euro D80220D.zip - this is the rom, right? and since it is .ZIP do I extract it to the folder where the ADB is or keep it as .zip to push it?
sorry, I'm really new to all this stuff and starting to regret rooting in the first place.
yoalphadied said:
Which of those files should I download.
as I understand it, once downloaded and in the file with the ADB.
adb devices (to make sure it is connected)
then
adb push recovery.zip /sdcard/ (saying recovery if I rename the file, and pushing the recovery is first?)
then straight after do I push the rom, after rebooting the device, or push them both - reboot the device then install the rom from the recovery?
the first file is Open Euro D80220D.zip - this is the rom, right? and since it is .ZIP do I extract it to the folder where the ADB is or keep it as .zip to push it?
sorry, I'm really new to all this stuff and starting to regret rooting in the first place.
Click to expand...
Click to collapse
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
Okay, I just tried pushing the rom, the line entered, i got no return so far but it won't allow me to type anything else in the CMD, i'm guessing its because it's pushing the file?
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
The recovery is working fine, but after factory resetting, and then trying to install the rom.zip it tries to open it
then e: cant open /data/media/rom.zip
(bad)
installation aborted
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
I didn't actually check to see if i got any errors during the push, so i tried pushing again with a different name rommy.zip and got this error
cannot read 'rommy.zip' : input/output error
3583 KB/s <1372848128 bytes in 374.008s>
yoalphadied said:
I didn't actually check to see if i got any errors during the push, so i tried pushing again with a different name rommy.zip and got this error
cannot read 'rommy.zip' : input/output error
3583 KB/s <1372848128 bytes in 374.008s>
Click to expand...
Click to collapse
Are you trying to sideload it? This is different than pushing the file. You don't need to sideload it. Just plug it in and adb push the files you need to the /sdcard/. And are you trying to install it with Philz?
es0tericcha0s said:
Are you trying to sideload it? This is different than pushing the file. You don't need to sideload it. Just plug it in and adb push the files you need to the /sdcard/. And are you trying to install it with Philz?
Click to expand...
Click to collapse
After realising that the push hadnt completed properly, I redownloaded the file, and then pushed it - now it has got past where it had the error and is at 'installing KitKat 4.4.2 ROM
Thanks for your help, greatly appreciated.
What are the benefits of using the Kernal you mentioned earlier?
maybe everything isn't as clear cut as it seemed, after the ROM installed correctly it asked me to reboot now, so I did and now I'm back stuck on the LG splash screen.
Maybe the rom is the wrong one for my phone? It's an LG G2 16gb D802 UK on EE.
yoalphadied said:
After realising that the push hadnt completed properly, I redownloaded the file, and then pushed it - now it has got past where it had the error and is at 'installing KitKat 4.4.2 ROM
Thanks for your help, greatly appreciated.
What are the benefits of using the Kernal you mentioned earlier?
maybe everything isn't as clear cut as it seemed, after the ROM installed correctly it asked me to reboot now, so I did and now I'm back stuck on the LG splash screen.
Maybe the rom is the wrong one for my phone? It's an LG G2 16gb D802 UK on EE.
Click to expand...
Click to collapse
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
es0tericcha0s said:
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
Click to expand...
Click to collapse
Should i try installing the kernal? See if that works? As it does say in comments that the 1st works for 16 &32
*EDIT*
install Kernal & supersu doesn't resolve the issue, going to try the new rom you posted now
yoalphadied said:
Should i try installing the kernal? See if that works? As it does say in comments that the 1st works for 16 &32
Click to expand...
Click to collapse
That's what I would do. Won't make it worse. Might help. If not, it's only a few more minutes altogether to try. Just make sure to wipe cache and dalvik cache.
es0tericcha0s said:
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
Click to expand...
Click to collapse
Okay, I came across another problem.
with the several versions of the same ROM at /sdcard/ my memory was running low, so i formatted it - then it wouldn't let me push anything to it, anyway i sorted that (can't remember how) and then installed the Kernal and superuser, which didn't seem to sort anything, but I did a little digging and mounted all the directories on Philz.
Then after I restarted the phone, whilst trying to get into recovery I heard the 'LG' splash screen animation noise. and then the phone loaded up the country setting - and then I got an error which made the screen unresponsive, I tried reloading to get yet another error, similar but not the same.
I booted into recovery, did a factory reset and again rebooted the phone and now it works, with the Knock Code! thank you so much you have saved my phone..
Is there anything I can do to say thank you properly, you've just saved me over £250

[Q] HOX+ problems after root/flash...

Hello everyone,
first of all im a total beginner on this field and it's the first time doing this stuff.
since there are no updates further than 4.2 for the beautiful HOX+ i tried to flash the cyanogenmod11 rom on my device. i used hasoons all-in-one toolkit. i followed the guide step by step and got stuck now in a hopefully not that serious problem.
i unlocked bootloader and flashed the cwm international recovery. the recovery was working fine and i did a backup. then i flashed the kernel with the boot.img from the cyanogenmod11.zip and the problems started. when normally booted the phone lights up with the white htc screen and then turns off again after about 3 seconds. i haven't flashed the CM11.zip yet and i guess that was the mistake? i still can acces the recover as well as the bootloader but like already said the phone doesn't start. another problem is that adb doesn't find the device enymore and only prints an empty line when using "adb devices" howevery using "fastboot devices" still gives me the proper result. hasoons toolkit also doesn't recognice the phone anymore.
if anyone could help either getting back to a custom rom or preferably setting up cyanogenmod properly would make me really happy =).
i hope this is the right place for this. i also searched around for hours and hours but can't find anything that helps me.
Lukas
ceevaa said:
Hello everyone,
first of all im a total beginner on this field and it's the first time doing this stuff.
since there are no updates further than 4.2 for the beautiful HOX+ i tried to flash the cyanogenmod11 rom on my device. i used hasoons all-in-one toolkit. i followed the guide step by step and got stuck now in a hopefully not that serious problem.
i unlocked bootloader and flashed the cwm international recovery. the recovery was working fine and i did a backup. then i flashed the kernel with the boot.img from the cyanogenmod11.zip and the problems started. when normally booted the phone lights up with the white htc screen and then turns off again after about 3 seconds. i haven't flashed the CM11.zip yet and i guess that was the mistake? i still can acces the recover as well as the bootloader but like already said the phone doesn't start. another problem is that adb doesn't find the device enymore and only prints an empty line when using "adb devices" howevery using "fastboot devices" still gives me the proper result. hasoons toolkit also doesn't recognice the phone anymore.
if anyone could help either getting back to a custom rom or preferably setting up cyanogenmod properly would make me really happy =).
i hope this is the right place for this. i also searched around for hours and hours but can't find anything that helps me.
Lukas
Click to expand...
Click to collapse
so you have installed the kernel but not the rom? if so, then you need to flash the rom and then it should work
leefear said:
so you have installed the kernel but not the rom? if so, then you need to flash the rom and then it should work
Click to expand...
Click to collapse
thanks for the answer so far.
the problem with this is that i cant flash the .zip using fastboot so i have to get an cyanogenmod image i think? dont know if that is somewhere out there ill check when im back home later.
ceevaa said:
thanks for the answer so far.
the problem with this is that i cant flash the .zip using fastboot so i have to get an cyanogenmod image i think? dont know if that is somewhere out there ill check when im back home later.
Click to expand...
Click to collapse
you normally flash the zip via recovery, do you already have the zip on your phone?
if so, go into recovery and install, find the zip file and install it
if you don't have the zip on your phone then you will need to sideload the zip to your phone, (fancy way of copying the file to your phone) then post 4 tells you how to sideload the rom: http://forum.xda-developers.com/showthread.php?t=2066390
thanks
leefear said:
you normally flash the zip via recovery, do you already have the zip on your phone?
if so, go into recovery and install, find the zip file and install it
if you don't have the zip on your phone then you will need to sideload the zip to your phone, (fancy way of copying the file to your phone) then post 4 tells you how to sideload the rom: http://forum.xda-developers.com/showthread.php?t=2066390
thanks
Click to expand...
Click to collapse
the problem with this is that i first don't have the zip on my phone so cant install from the recovery and second that adb doesnt recognize my phone for whatever reasone so i can't sideload the rom. if anyone experienced similar problems (fastboot working, adb not) please let me know how to fix it
Lukas
another thing i just read about is the possibility if one already has installed a running cyanogenmod rom on his device he can extract that as an system.img if i remember right and i could use it on my hox+. just in case anyone knows how to pull that off let me know =)
otherwise still looking for hints how to install rom via fastboot or how to make adb working again
Lukas
this phone is killing me -.-
now when entering fastboot mode it says battery too low to fast boot. so i connect it to the charger overnight but it apparently doesnt charge anymore.
help, please =(
ceevaa said:
this phone is killing me -.-
now when entering fastboot mode it says battery too low to fast boot. so i connect it to the charger overnight but it apparently doesnt charge anymore.
help, please =(
Click to expand...
Click to collapse
Try flashing the ROM onto the phones storage. Then you can install the ROM. If you cant even charge your phone then you have bigger problems than not having an OS installed.
Moynia said:
Try flashing the ROM onto the phones storage. Then you can install the ROM. If you cant even charge your phone then you have bigger problems than not having an OS installed.
Click to expand...
Click to collapse
Hey thanks for the answer
but how do i flash the rom on the phone storage using fastboot?
Lukas

HTC Desire 825, is it rootable?

Hello,
I have the device HTC Desire 825 with the pre-installed 6.0.1. I have tried loads to root my device, I have tried all the one-click root ways from Kingo etc but they all fail.
I tried to find a way to flash the device but on the list of devices, the HTC Desire 825 is not on the list. Not sure if there is a way to root it or not, I done it before on previous devices but never been stuck like this. If someone knows a way, please tell me how, it would be much appreciated
Thank you,
zemauk said:
Hello,
I have the device HTC Desire 825 with the pre-installed 6.0.1. I have tried loads to root my device, I have tried all the one-click root ways from Kingo etc but they all fail.
I tried to find a way to flash the device but on the list of devices, the HTC Desire 825 is not on the list. Not sure if there is a way to root it or not, I done it before on previous devices but never been stuck like this. If someone knows a way, please tell me how, it would be much appreciated
Thank you,
Click to expand...
Click to collapse
Why not you try goes to HTC dev..might be they knew it much better..I mean rooting your devuces
HTC dev - all other devices.
Twrp found in a discussion here in one of the threads.
Latest Superuser Beta zip or img.
brunkonjaa said:
HTC dev - all other devices.
Twrp found in a discussion here in one of the threads.
Latest Superuser Beta zip or img.
Click to expand...
Click to collapse
And how I can install TWRP to use for root my device?
Xxshark888xX said:
And how I can install TWRP to use for root my device?
Click to expand...
Click to collapse
Go to HTC dev site. Register. Log in. Look for "unlock bootloader" option. Click on it. Follow instructions. Great, you have now unlocked your bootloader !
Now, in order to unlock bootloader you had to download HTC fastbooot . Open the folder where that HTC fast boot has been extracted.....
Now, previously downloaded Superuser and Twrp files......
Place them in that folder where you extracted your HTC fastboot files.
Right click on empty space anywhere inside that folder while holding "shift", and you will get an option to "open cmd window here". Click on it. Type "adb devices". Your phone should show as some numbers followed by the word device ( "1234567 device").
Your device should be recognized and you can continue to the next step. If it isn’t recognised then you should re-install all the USB Drivers for your device.
Next, enter the following command line in CMD in order to flash the TWRP Recovery files:?*fastboot flash recovery "name of downloaded recovery".img.
When the TWRP Recovery file is successfully installed, CMD will display a confirmation message. Disconnect the device from computer now.Use the Volume buttons to select ‘HBOOT’ option on your smartphone and select it by pressing Power. Test to see if the RECOVERY mode works by selecting the ‘RECOVERY’ option. Your phone should boot into TWRP Recovery mode now and this means that the install has been successfully completed.
To install Superuser, repeat above steps BUT instead of typing "Twrp xxxxxx.img" type "name of superuser file". Once you have confirmation of the file being sent, disconnect from PC, enter recovery, choose install, and click on the superuser file.
Little tip: I spent hours trying to send both Twrp and superuser files to the phone with all kinds error messages showing inside cmd screen. File too big, can't read file, destination unreachable...... then I found simple solution:
Inside the fastboot folder I created new empty folder.
I copy/pasted Twrp and superuser files inside of it.
Opened cmd folder inside of that new folder and tried sending files again, one at the time. It worked flawlessly straight away.
Little tip 2: if you have trouble writing the names of your Twrp and superuser files in your cmd window, you can do the following:
Type "fastboot flash recovery", press space bar once, now left click on the required file in you fastboot folder (Twrp or superuser) and drag it across into your cmd window.
If you need anything else, feel free to ask. When dealing with this kind of fiddling with your device, no question is stupid or irrelevant.
brunkonjaa said:
Go to HTC dev site. Register. Log in. Look for "unlock bootloader" option. Click on it. Follow instructions. Great, you have now unlocked your bootloader !
Now, in order to unlock bootloader you had to download HTC fastbooot . Open the folder where that HTC fast boot has been extracted.....
Now, previously downloaded Superuser and Twrp files......
Place them in that folder where you extracted your HTC fastboot files.
Right click on empty space anywhere inside that folder while holding "shift", and you will get an option to "open cmd window here". Click on it. Type "adb devices". Your phone should show as some numbers followed by the word device ( "1234567 device").
Your device should be recognized and you can continue to the next step. If it isn’t recognised then you should re-install all the USB Drivers for your device.
Next, enter the following command line in CMD in order to flash the TWRP Recovery files:?*fastboot flash recovery "name of downloaded recovery".img.
When the TWRP Recovery file is successfully installed, CMD will display a confirmation message. Disconnect the device from computer now.Use the Volume buttons to select ‘HBOOT’ option on your smartphone and select it by pressing Power. Test to see if the RECOVERY mode works by selecting the ‘RECOVERY’ option. Your phone should boot into TWRP Recovery mode now and this means that the install has been successfully completed.
To install Superuser, repeat above steps BUT instead of typing "Twrp xxxxxx.img" type "name of superuser file". Once you have confirmation of the file being sent, disconnect from PC, enter recovery, choose install, and click on the superuser file.
Little tip: I spent hours trying to send both Twrp and superuser files to the phone with all kinds error messages showing inside cmd screen. File too big, can't read file, destination unreachable...... then I found simple solution:
Inside the fastboot folder I created new empty folder.
I copy/pasted Twrp and superuser files inside of it.
Opened cmd folder inside of that new folder and tried sending files again, one at the time. It worked flawlessly straight away.
Little tip 2: if you have trouble writing the names of your Twrp and superuser files in your cmd window, you can do the following:
Type "fastboot flash recovery", press space bar once, now left click on the required file in you fastboot folder (Twrp or superuser) and drag it across into your cmd window.
If you need anything else, feel free to ask. When dealing with this kind of fiddling with your device, no question is stupid or irrelevant.
Click to expand...
Click to collapse
Thanks for the help. I successful rooted my HTC Desire 825. But I have another question. I downloaded Titanium Backup to uninstall bloatware apps. the problem is that after uninstalling the apps still remain in the memory of the device, why?
Xxshark888xX said:
Thanks for the help. I successful rooted my HTC Desire 825. But I have another question. I downloaded Titanium Backup to uninstall bloatware apps. the problem is that after uninstalling the apps still remain in the memory of the device, why?
Click to expand...
Click to collapse
Oh the joys of bloatware!!!!!!!
Here's what I did: after trying to remove it, and soft bricking ????, I installed xposed, lucky patched and Greenify. In this forum I am not allowed to explain how I got specific version of Greenify that works with lucky patcher patch in order to gain pro version, so I won't explain it ????.
I simply greenified most of bloatware, so it's out if the way.
I know it doesn't really answer your question but at least it allows to keep the beast at bay.
brunkonjaa said:
Oh the joys of bloatware!!!!!!!
Here's what I did: after trying to remove it, and soft bricking ????, I installed xposed, lucky patched and Greenify. In this forum I am not allowed to explain how I got specific version of Greenify that works with lucky patcher patch in order to gain pro version, so I won't explain it ????.
I simply greenified most of bloatware, so it's out if the way.
I know it doesn't really answer your question but at least it allows to keep the beast at bay.
Click to expand...
Click to collapse
I already have Lucky Patcher. Later I will search Greenify and try to uninstall all the bloatware. Thanks again ?
Xxshark888xX said:
I already have Lucky Patcher. Later I will search Greenify and try to uninstall all the bloatware. Thanks again ?
Click to expand...
Click to collapse
Unlike stock Android, manufacturer skins like TouchWiz, Sense etc. come with a plethora of pre-loaded apps that you can’t uninstall. Be careful.
Xxshark888xX said:
I already have Lucky Patcher. Later I will search Greenify and try to uninstall all the bloatware. Thanks again ?
Click to expand...
Click to collapse
Hi! Did you manage to uninstall any of the bloatware?
Xxshark888xX said:
Thanks for the help. I successful rooted my HTC Desire 825. But I have another question. I downloaded Titanium Backup to uninstall bloatware apps. the problem is that after uninstalling the apps still remain in the memory of the device, why?
Click to expand...
Click to collapse
The uninstalled Apps will crawl back after reboot because the device is still S-ON. There are couple ways to handle this. One is to S-OFF the device using Sunshine or similar app. Method 2 is using TWRP. Use the TWRP built-in file explorer, mount system, head to where the apps are and delete the ones you wouldn't need.
Hello guys. Does someone have a back up of the htc 825 stock recovery.img? Maybe someone can extract the stock recovery and share it here please ?
stenlibi said:
Hello guys. Does someone have a back up of the htc 825 stock recovery.img? Maybe someone can extract the stock recovery and share it here please ?
Click to expand...
Click to collapse
Hi, did you manage to find the recovery img?
I need to flash it instead of buggy twrp, searched for hours and nowhere to be found
Ok, i've managed to find it This is the stock recovery IMG, working fine, extracted from original firmware.
https://mega.nz/#!yYd30a7A!hK7RoQjhWkG8S2nS3__B8xbnwAssN4QI59rXJyQ1y9o
Credits go to nkk71 https://forum.xda-developers.com/member.php?u=2605798 for the great tool to exctract the firmware image,
without it i wouldn't accomplish the task.
If the link will die, PM me, i'll reupload.

TWRP

Hey please can someone give me a link to the newest twrp wit scatter file for flashing? I've been on the official site and for it but there was no scatter file... Seems impossible to find, thanks anyone who can help =)
Pikachu666 said:
Hey please can someone give me a link to the newest twrp wit scatter file for flashing? I've been on the official site and for it but there was no scatter file... Seems impossible to find, thanks anyone who can help =)
Click to expand...
Click to collapse
scatter file is the one included in every stock rom that is flashable to sp flash tools, when you load the scatter file, it loads a list of partitions and it allows you to flash files onto those partition, in thus case you needed the partition table to flash the recovery, so you need to load the scatter file that is found on any stock rom made for flash tools
haidar123 said:
scatter file is the one included in every stock rom that is flashable to sp flash tools, when you load the scatter file, it loads a list of partitions and it allows you to flash files onto those partition, in thus case you needed the partition table to flash the recovery, so you need to load the scatter file that is found on any stock rom made for flash tools
Click to expand...
Click to collapse
Sorry I don't get it, well do you have link for the zip file for that then?
Pikachu666 said:
Sorry I don't get it, well do you have link for the zip file for that then?
Click to expand...
Click to collapse
twrp can be found here: https://twrp.me/devices/elephonep9000.html
for the scatter file you need to download the rom you are currently on unzip it and in the rom there will be a file called MT6755_Android_scatter.txt or something along the lines of that
haidar123 said:
twrp can be found here:
for the scatter file you need to download the rom you are currently on unzip it and in the rom there will be a file called MT6755_Android_scatter.txt or something along the lines of that
Click to expand...
Click to collapse
I have tried a different way no via cmd with adb...
And I followed the steps meticulously - unlocked bootloader etc, but I get to the "writing recovery part" -
And it says FAILED (remote not allowed in locked state)
I don't get it! =(
I have unlocked bootloader, I have installed drivers, I did EVERYTHING...
Any advice?
Pikachu666 said:
I have tried a different way no via cmd with adb...
And I followed the steps meticulously - unlocked bootloader etc, but I get to the "writing recovery part" -
And it says FAILED (remote not allowed in locked state)
I don't get it! =(
I have unlocked bootloader, I have installed drivers, I did EVERYTHING...
Any advice?
Click to expand...
Click to collapse
Go to spflash tools click scatter loading file and find the file in the rom you have downloaded then select it. Then uncheck everything and click on recovery and select the twrp.img. turn your phone off press download and connect your phone
haidar123 said:
Go to spflash tools click scatter loading file and find the file in the rom you have downloaded then select it. Then uncheck everything and click on recovery and select the twrp.img. turn your phone off press download and connect your phone
Click to expand...
Click to collapse
I only have a twrp img file
I don't have anything that is a scatter file - When I downloaded twrp img from the official site it came with no scatter file and I don't know how to obtain it =(
Pikachu666 said:
I only have a twrp img file
I don't have anything that is a scatter file - When I downloaded twrp img from the official site it came with no scatter file and I don't know how to obtain it =(
Click to expand...
Click to collapse
for the scatter file you need to download the rom you are currently on unzip it and in the rom there will be a file called MT6755_Android_scatter.txt or something along the lines of that
Go to settings > about phone and tell me build number and i will find you a link to the rom which will contain scatter file
haidar123 said:
for the scatter file you need to download the rom you are currently on unzip it and in the rom there will be a file called MT6755_Android_scatter.txt or something along the lines of that
Go to settings > about phone and tell me build number and i will find you a link to the rom which will contain scatter file
Click to expand...
Click to collapse
I don't have a rom, sorry i'm abit of a noob...
but my phone build Elephone_P9000_20170904
Pikachu666 said:
I don't have a rom, sorry i'm abit of a noob...
but my phone build Elephone_P9000_20170904
Click to expand...
Click to collapse
http://bbs.elephone.hk/thread-13874-1-1.html#.WbE_GKhSyUl
this link contains the rom you require and instructions
haidar123 said:
http://bbs.elephone.hk/thread-13874-1-1.html#.WbE_GKhSyUl
this link contains the rom you require and instructions
Click to expand...
Click to collapse
Thank you, if I do manage to install twrp and supersu,
will it factory reset my phone?
Or do I keep all apps settings amd just carry on, with the only difference being root?
Pikachu666 said:
Thank you, if I do manage to install twrp and supersu,
will it factory reset my phone?
Or do I keep all apps settings amd just carry on, with the only difference being root?
Click to expand...
Click to collapse
If you uncheck everything and change the recovery to twrp then it will keep everything if you leave all boxes checked then everything will be deleted.
haidar123 said:
http://bbs.elephone.hk/thread-13874-1-1.html#.WbE_GKhSyUl
this link contains the rom you require and instructions
Click to expand...
Click to collapse
haidar123 said:
If you uncheck everything and change the recovery to twrp then it will keep everything if you leave all boxes checked then everything will be deleted.
Click to expand...
Click to collapse
Okay so got all that. now on sp tools when i plug phone in after download, it doesnt do anything...
Ive tried it with phone off and phone on. Doesnt acknowledge its plugged in on the flash tool
Pikachu666 said:
Okay so got all that. now on sp tools when i plug phone in after download, it doesnt do anything...
Ive tried it with phone off and phone on. Doesnt acknowledge its plugged in on the flash tool
Click to expand...
Click to collapse
The drivers havent been installed correctly. The link i sent before will show how to install them.
haidar123 said:
The drivers havent been installed correctly. The link i sent before will show how to install them.
Click to expand...
Click to collapse
Im following the tutorial but it doesnt work for me how it did on the tutorial, when I install nothing happens, and when I plug in turned off phone nothing happens.
Pikachu666 said:
Im following the tutorial but it doesnt work for me how it did on the tutorial, when I install nothing happens, and when I plug in turned off phone nothing happens.
Click to expand...
Click to collapse
If your're on windows 10 try finding a machine with windows 7 or xp. If not search the internet and there will be other guides. It took me quite a while to get the drivers to work on windows 10 i cant remember how i did it
haidar123 said:
If your're on windows 10 try finding a machine with windows 7 or xp. If not search the internet and there will be other guides. It took me quite a while to get the drivers to work on windows 10 i cant remember how i did it
Click to expand...
Click to collapse
I ran the installer and it stated that it had installed the mediatek drivers, but in device manager it is not there. SO frustrating lol, gonna try manually install from legacy
haidar123 said:
If your're on windows 10 try finding a machine with windows 7 or xp. If not search the internet and there will be other guides. It took me quite a while to get the drivers to work on windows 10 i cant remember how i did it
Click to expand...
Click to collapse
Still no luck, I get a device cannot start code 10
Pikachu666 said:
Still no luck, I get a device cannot start code 10
Click to expand...
Click to collapse
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
haidar123 said:
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
Click to expand...
Click to collapse
Okay so, I have now got twrp downloaded.
I have supersu on my internal storage.
Now I press volup + power to enter twrp recovery - no does not work I just get elephone logo, then I release power and get no command?
Ive came so far and now am stuck again lol

Categories

Resources