Related
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
MY TBOLT MUST DID THE OTA OR ATLEAST TRIED TO WHILE I WAS SLEEP NOW IT KEEPS POWERING OFF THOUGHT I HAD ROM MANNAGER TO RESTORE A BACK UP OFF MY SD BUT IT MUST DIDNT INSTALL AFTER LAST UPDATE I ONLY HAVE JUST THE PREMIUM LICENSE. I THOUGHT IT WOULD STAY POWERED LONG ENOUGH TO GO DL ROM MANAGER IN THE MARKET BUT IT WONT. I TRIED DL THE NEW OTA SO I CANN PUT IT ON MY SD AND FLASH HBOOT BUT IT KEEPS NAMING WITH THE .ZIP.ZIP EXT NO MATTER HOW MANY TIMES I RENAME IT WHAT CAN I DO I LOOKED HERE http://www.thunderboltforums.com/fo...-get-rid-ota-forced-reboots-rooted-phone.html BUT I NEED ROM MGR DO I NEED TO DL A STOCK AND UNROOT IT WHAT CAN I DO.... HELP PLEASE SAD PART I WORK FOR VZW AND I KNOW HOW THEY DO WITH EQUIP CHARGEBACKS
First, locate your caps lock and TURN IT OFF. Next locate your period key and put them on the end of your sentences. Making sense of your post is giving me a headache.
Now, on your computer you need to disable the "hide file extensions for known file types" option to fix the zip.zip problem. Can't give you exact directions since you didn't say which os you're using.
Sent from my ADR6400L using Tapatalk
Windows7 currently
I have the same problem and I tried to get in through the clorkworkMod adb shell, but the device is not recognized by adb...? When the device boots up it is recognized. with my DINC I could use the shell while in clorkworkmod.
Is it showing as device offline or not showing the device at all. If its offline, through cmd, close adb server, then start it back up, half the time that fixed that problem for me. If its not showing at all, try setting it to HTC Sync i believe was the one i had to do at one point for it to register. I've rooted 4 times using ADB method and each time its been a little different, so i can't narrow down what i'm doing wrong to help you more with the adb, sorry.
Similar Issue
Hi All and thanks to all the cats on here that willfully give their knowledge! I have a Tbolt - Rooted with Revolutionary, stock rom (removed VZ Bloat via Titanium ), but this latest OTA update is not leaving me alone. I try to reject it and magically a few days later I get out of nowhere reboot and then the android exclamation point with a triangle. I use the Clockwork Mod Recovery to wipe data cache and reboot which makes the update manager get upset saying it failed. The error I see in Clockwork is this:
CWM Recovery V5.0.2.1
E: Failed to verify whole file signature
E: Signature Verification Failed
Install Aborted
So how can I get this update (I am assuming it is to fix the HTC fail for new exploit out there) which I think would be a good thing. I am not ready to flash a custom ROM yet so please don't reply saying "Just flash with my favorite ROM"
Thanks ahead of time!
It pushes the update, and if you don't reject within 3 mins, viola, you have a nice new update. If you can still get into recovery, which it sounds you can, install a stock rooted either full or debloated. Thats the updated equivalent to what you have now. Make sure you grab the rooted though. Here is the full rooted (not debloated) http://www.multiupload.com/H06XI7W380
from this thread
http://forum.xda-developers.com/showthread.php?t=1312193
I'd probably wipe cache and dalvik cache, but you can probably leave data since you're staying stock.
Thanks for the direction nbdysreal!
About a month ago I rooted a HTC EVO 4G LTE, installed the recovery with touch screen and Cyanogenmod nighties.
It worked great, including tethering on Sprint.
Last week an update to latest Cyanogenmod was made. Phone worked normally, until today when screen stopped responding completely (physical buttons were working), including after rebooting. On a second reboot phone was stuck on a boot loop.
Went into bootloader mode and tried to go to recovery. It would boot loop again. Noted that it said UNLOCKED S-ON (I thought it was supposed to be S-OFF). I tried flashing the boot.img from latest Cyanogenmod. Nothing. Tried reseting from the menu. Tried more things. Nothing worked. So I downloaded and used the latest version of RUU after fastboot oem lock. RUU was successful (no error, phone no longer displays HTC developer message), however it's still stuck on the boot loop. I thought RUU would restore it completely.
What am I missing?
Read here
http://forum.xda-developers.com/showthread.php?t=2084633
And here
http://forum.xda-developers.com/showthread.php?t=2097150
#Root-Hack_Mod*Always=SG3
I followed the instructions.
Then I tried all RUU that I had and always got Error 140.
Finally, found in a rooting pack RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe which worked to restore.
However, the phone is still in the same state. What do I do?
How long did you give the phone to boot.? Also did you flash the firmware zip after you relocked your boot loader?
#Root-Hack_Mod*Always=SG3
Phone is RELOCKED.
What I did:
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip jewel_jb_ota_firmware.zip
Then used that RUU to restore. After this I left the phone without touching it for about ten minutes, but it keeps restarting (never passes booting stage).
Try this. Remove your sd. Then back up all your data. Then format it threw your PC and return it to factory defaults. Then put it back in your phone and redo the steps. Also were did you get the ruu your using from ?? Also if that fails to work look here
http://forum.xda-developers.com/showthread.php?t=2045935
And try the firmware zip with the stock recovery. Then run the ruu. Hope this helps.
#Root-Hack_Mod*Always=SG3
Does it matter if the SD is in?
So, I took out the SD card, repeated those three steps and I should use RUU again.
The RUU is from 3.15_RUU_PLUS_ROOT.zip.
I'm going to try again now with no SD.
Same result after trying without SD card. Also I did flashboot flash zip
Code:
PJ75IMG_3.15.651.6-firmware.zip
from the link you provided without help.
PepeJones said:
Does it matter if the SD is in?
So, I took out the SD card, repeated those three steps and I should use RUU again.
The RUU is from 3.15_RUU_PLUS_ROOT.zip.
I'm going to try again now with no SD.
Click to expand...
Click to collapse
Yes the sd card should be in your phone. Also your trying to go back to stock so using the ruu that's stock with root might be the issue given your phones current state. I'll try and find you just the stock ruu with no root, unless you have one or if you know were one is download it and run it. Also when I posted about the SD card you were only supposed to remove it to "back up your data" and then "format" it. After you have formatted it then place it back into your phone. I'm not aware of any potential issues with running a ruu without the SD card being in the phone, however I would strongly suggest always running the ruu with the SD in the phone. Its what I've always done. Also make sure that your battery is over 75%. And did you flash the one with the stock recovery? There are several firmware zips on that thread but the one with the stock recovery is the one I suggested you try. And I'm not sure what the "without help" post is about. I'll help you as much as I can and I'm sure if I don't reply to you right away that there are more than enough knowledgeable members in this forum to help you as well. Take in mind that phones are so easy to screw up but it might take some time to get it back up and running. But troubleshooting is all part of the process.
#Root-Hack_Mod*Always=SG3
I'll try it again with the SD card in the phone. No, the RUU I'm using it's in a pack for rooting and updating. I don't think it's modified at all. I don't even think RUU can be altered and signed anyway. I'll search for another RUU again.
Yes, the one that I flashed is
Code:
PJ75IMG - Firmware zip with hBoot and stock recovery (signature intact)
http://d-h.st/sKO (MD5: 0d8f9d65e29c1c824654bf88b9438f15)
and I had enough battery. (It was supposed to be without luck not without help).
So, I'll flash the above mentioned PJ75IMG, then use the RUU (I'll search for one that's in no pack, but I'm confident it's not altered) - all this with the SD card inside.
Thanks for your help.
laie1472 said:
Yes the sd card should be in your phone. Also your trying to go back to stock so using the ruu that's stock with root might be the issue given your phones current state. I'll try and find you just the stock ruu with no root, unless you have one or if you know were one is download it and run it. Also when I posted about the SD card you were only supposed to remove it to "back up your data" and then "format" it. After you have formatted it then place it back into your phone. I'm not aware of any potential issues with running a ruu without the SD card being in the phone, however I would strongly suggest always running the ruu with the SD in the phone. Its what I've always done. Also make sure that your battery is over 75%. And did you flash the one with the stock recovery? There are several firmware zips on that thread but the one with the stock recovery is the one I suggested you try. And I'm not sure what the "without help" post is about. I'll help you as much as I can and I'm sure if I don't reply to you right away that there are more than enough knowledgeable members in this forum to help you as well. Take in mind that phones are so easy to screw up but it might take some time to get it back up and running. But troubleshooting is all part of the process.
#Root-Hack_Mod*Always=SG3
Click to expand...
Click to collapse
PepeJones said:
I'll try it again with the SD card in the phone. No, the RUU I'm using it's in a pack for rooting and updating. I don't think it's modified at all. I don't even think RUU can be altered and signed anyway. I'll search for another RUU again.
Yes, the one that I flashed is
Code:
PJ75IMG - Firmware zip with hBoot and stock recovery (signature intact)
http://d-h.st/sKO (MD5: 0d8f9d65e29c1c824654bf88b9438f15)
and I had enough battery. (It was supposed to be without luck not without help).
So, I'll flash the above mentioned PJ75IMG, then use the RUU (I'll search for one that's in no pack, but I'm confident it's not altered) - all this with the SD card inside.
Thanks for your help.
Click to expand...
Click to collapse
You can't flash a PJ75IMG.zip unless you are S-OFF and the file you posted above is not an RUU it's just the updated firmware
It didn't work.
So I followed the steps from this link.
After using HTCDev to unlock the phone and I try to open RabiesShot, it reboots the phone but it's not able to connect. Sometimes the phone goes in a loop, sometimes the phone boots (it did boot twice). However, even when it booted, the screen didn't work at all, which is the original problem.
Right now the phone is ON but the only thing that works is the power and volume buttons (screen and soft buttons do not work). I've also noticed the phone reboots alone.
Any ideas left?
(This is my friend's phone. Anyway, I'll convince anyone to stay away from HTC. Nexus is so much better than this...)
Its not the phone its the user. I've never heard of a phone hacking itself. So usually the fault is the owner of the device and not the device itself. And In this case I'd say its user error. Also I'm lost as in what your doing at the moment. I thought you were trying to go back to stock? Now you post says your basically trying to obtain s-off. If this is the case then you make it extremely difficult to try and pin point what's actually the issue with your firends phone because you jump methods. So at this point exactly what are you trying to do ? Are you trying to go back to stock to gain s-off ?? Also if you come here to receive help with your issue you should always try the posted methods first so the member that's helping you is aware of what steps your taking and what your going to do. If not then it becomes difficult to help you.
#Root-Hack_Mod*Always=SG3
laie1472 said:
Its not the phone its the user. I've never heard of a phone hacking itself. So usually the fault is the owner of the device and not the device itself. And In this case I'd say its user error. Also I'm lost as in what your doing at the moment. I thought you were trying to go back to stock? Now you post says your basically trying to obtain s-off. If this is the case then you make it extremely difficult to try and pin point what's actually the issue with your firends phone because you jump methods. So at this point exactly what are you trying to do ? Are you trying to go back to stock to gain s-off ?? Also if you come here to receive help with your issue you should always try the posted methods first so the member that's helping you is aware of what steps your taking and what your going to do. If not then it becomes difficult to help you.
#Root-Hack_Mod*Always=SG3
Click to expand...
Click to collapse
Not hacked itself, just not working. At least, that's what I've been told. Right now I'm trying to make it stock, but since what you proposed didn't work I tried different things such as obtaining S-OFF (no success).
The comment regarding HTC wasn't necessarily related to this case but in general. Just look how miserably is the process to just obtain root and unlock the bootloader. And in many cases is not even possible until some exploit is found. Why...? HTC used to be great.
I'm just trying to get this phone work again. Initial idea was to go stock, since it seems logical that it should be straight forward.
So I tried everything you have posted, including the last instructions you left me (backup everything off SD, deleted everything and inserted SD in the phone, then repeated the process).
Thanks for your help.
I understand your frustration about the issues with the phone in its current state. However if done correctly gaining root/s-off can be achieved in less that an hour. I do realize the fact that even if guides are followed to the exact directions that issues still occur. But that's the risk you take when you modify you phone. Your aware of this I'm sure. However that's why xda is a great website. Not only can you get the software to modify your phone, you can also get help in case the process didn't go the way it should have. You can't dispute the fact that there are more than a few members with the evo-lte who had no problems at all with gaining root or s-off. As far as the steps I suggested there was no guarantee that they would work its just the process of trouble shooting to see what will work. If you don't mind can you post the exacts steps you took before you tried to achieve s-off ? Also can you post the links to the exact ruu and firmware you last used as well.? Also if the phone is on try powering it down and attempt to boot into the boot loader. If your successful then try factory reset.
#Root-Hack_Mod*Always=SG3
A few weird things are happening on my phone and I'm quite concerned (even though it's actually working perfectly fine, which is the weirdest part of all!)
A little background: I recently wiped my phone and flashed the Sense 5 Android 4.3, stock rom. Now I'm trying to flash Viper 4.0.
First of all, as the title suggests, whenever I put a zip file on my phone it doesn't show in the TWRP recovery. I downloaded the correct one on the site (the newest one for the HTC EVO 4G LTE) so I don't think that's the problem. Also, I tried to push the file Viper zip onto my phone using this program called WinDroid Toolkit, and it claims it did but when I go into TWRP I cannot see the zip file at all, and if I try to use other folder names (such as the 'boot' folder I saw when I was in TWRP recovery) it says those folders don't exist!
Second of all, TWRP claims there is no OS installed on my phone but when I reboot my phone, it's fine! It just goes to the home screen as usual and it works perfectly fine... so I don't understand this warning but I couldn't shake the feeling that this was relevant to my issue.
I've been combing the forums looking for this type of problem, and I've tried multiple things but to no avail. I've read snippets about partition problems after formatting some phones but I'm not sure because there doesn't seem to be much information about it (at least from what I could find).
Altom85 said:
A few weird things are happening on my phone and I'm quite concerned (even though it's actually working perfectly fine, which is the weirdest part of all!)
A little background: I recently wiped my phone and flashed the Sense 5 Android 4.3, stock rom. Now I'm trying to flash Viper 4.0.
First of all, as the title suggests, whenever I put a zip file on my phone it doesn't show in the TWRP recovery. I downloaded the correct one on the site (the newest one for the HTC EVO 4G LTE) so I don't think that's the problem. Also, I tried to push the file Viper zip onto my phone using this program called WinDroid Toolkit, and it claims it did but when I go into TWRP I cannot see the zip file at all, and if I try to use other folder names (such as the 'boot' folder I saw when I was in TWRP recovery) it says those folders don't exist!
Second of all, TWRP claims there is no OS installed on my phone but when I reboot my phone, it's fine! It just goes to the home screen as usual and it works perfectly fine... so I don't understand this warning but I couldn't shake the feeling that this was relevant to my issue.
I've been combing the forums looking for this type of problem, and I've tried multiple things but to no avail. I've read snippets about partition problems after formatting some phones but I'm not sure because there doesn't seem to be much information about it (at least from what I could find).
Click to expand...
Click to collapse
Try using the TWRP found here:
http://forum.xda-developers.com/showthread.php?t=2639180
Sent from my Nexus 5 using XDA Premium 4 mobile app
download this twrp http://d-h.st/7Cr
name it properly and fastboot flash it. after that mount your device to you pc and transfer a rom zip to storage.
Okay, well I flashed that TWRP and now I'm stuck at the white HTC screen. I can't even get into the bootloader, it just continually boots to the white HTC screen. Thoughts?
Altom85 said:
Okay, well I flashed that TWRP and now I'm stuck at the white HTC screen. I can't even get into the bootloader, it just continually boots to the white HTC screen. Thoughts?
Click to expand...
Click to collapse
RUU or ViperRUU. TBH it sounds like the behavior of a dirty flash. ViperRUU is especially helpful in these situations.
Once done, use the TWRP recommended by Evolution_Freak. There were some major changes to the partitioning in the last few releases, make sure your recovery is appropriate for your ROM.
FesterCluck said:
RUU or ViperRUU. TBH it sounds like the behavior of a dirty flash. ViperRUU is especially helpful in these situations.
Once done, use the TWRP recommended by Evolution_Freak. There were some major changes to the partitioning in the last few releases, make sure your recovery is appropriate for your ROM.
Click to expand...
Click to collapse
Ok it's not stuck anymore, I can get into recovery and bootloader, so I'm not in a panic anymore at least However, my computer is not detecting my phone, nor is VipeRUU. If I try to mount to the computer via TWRP, nothing comes up. BTW my recovery is 2.7.8.0b now. Still no OS, still gets stuck on the HTC screen until I boot to recovery or bootloader
Edit: Now the computer tries to install drivers for my phone whenever I plug it in. It pops up as HTC MTP Device, always fails to install, then has a warning in the device manager. So I uninstalled the drivers, uninstalled HTC Sync, reinstalled HTC Sync. Didn't help. This is beyond frustrating...
Edit 2: After scouring the internet someone said to lock the bootloader and that'll allow my PC to see my phone. Well, now i have a RELOCKED (that's what it says on top) bootloader and I'm no closer to the solution methinks. I'm ready to just throw this phone out the window.
Edit 3: I actually discovered ViperRUU has a way to bypass the initial screen so I can use it in bootloader. Great, except now it's stuck on "Flashing..." and has been for half an hour. I really might throw this phone out the window.
5th and final edit: VipeRUU just would not work at all, so I had to go back to an older stock RUU, which sucks but at least my phone is working now Thanks for your help guys!
I am rooted and S-Off. I am using the ViperOne custom ROM for my phone.
The end goal is for me to update my firmware, because my phone has an over 10 minutes boot time normally. (Not an exaggeration. I have actually timed it with a timer.) I read that in order to fix this, I should try to update the firmware by going to stock recovery and doing an OTA update.
My TWRP has worked flawlessly for me over the years, but for some reason it won't work anymore. It will hang on the boot screen for over an hour. After that hour, I assumed it's not slowly booting. (As a bit of background, recovery would boot quickly while my phone still had problems with 10 minute boot times).
Another piece of information is that the last time TWRP worked was when I used it to install .zip files from Titanium to get all my apps working. That worked perfectly fine, my apps got updated, and no trouble. I wish I could say what happened between then and now, but from what I can remember, I just used my phone normally, such as using web browsers and games. I don't remember messing with any system files.
I do know that ClockWorkMod recovery DOES work if I flash that, but my nandroids are all on TWRP. I have tried to flash different version of TWRP as well. It doesn't seem to matter which one I flash, my phone reacts exactly the same.
Another thing to note, I'm not sure if it's significant or not, is that when I got into hboot, I get the following message for a split second. I can't read the file names exactly, but I got the extensions. Then I get the normal screen with the vol instructions and choices to go to fastboot, recovery, etc... The message reads:
SD Checking...
Loading [(something).zip]
No Image!
Loading [(something).nbh]
No Image or wrong image!
Loading [(something).zip]
Loading [(something).nbh]
No Image or wrong image!
I hope this is a decent amount of information. I tried to include as much as I could, but if I'm missing any critical details, let me know and I will GREATLY appreciate your help!
have u tried to rewrite the image, download the new TWRP and load it via adb
Bradl79 said:
have u tried to rewrite the image, download the new TWRP and load it via adb
Click to expand...
Click to collapse
Well, I did do that. I rewrote different versions of the image and none worked.
Sadly, my solution was to completely wipe my phone. More than the default factory reset.
I'm so it has been solved, but probably not in the most practical way for others with a similar problem.
Battletooth said:
Well, I did do that. I rewrote different versions of the image and none worked.
Sadly, my solution was to completely wipe my phone. More than the default factory reset.
I'm so it has been solved, but probably not in the most practical way for others with a similar problem.
Click to expand...
Click to collapse
Having the exact same issue. Attempted to install twrp-2.8.6.0-m8.img using adb, but TWRP never loads. I can load prior versions but same results. Going to HBOOT I get a bunch of messages related to 0P6BDIAG.zip, 0P6BIMG.zip
and some .nbh. I think it's looking on my SDCARD for those.
If you're looking to update your firmware, you can use an official RUU to change the firmware of your phone. You can read more about it in this stickied thread in the general forum to see if it fits your needs. If you decide to do this, your phone will be completely stock after the RUU finishes running so use fastboot to flash TWRP (or whichever recovery you prefer).
Regarding the messages you see in hboot, it will always check for those files if you have an external sdcard mounted. If they are present, you will be given the option to flash the update. If not, you will get regular hboot access after the check. It is completely normal and nothing to worry about.