so I have the latest software, used the HTC unlock method, was rooted and had the TWRP recovery working just fine, I'm an idiot and flashed the CM recovery through RM and of course it didn't work, so I've tried every which way I can find to re-flash the TWRP and even tried flashing AMON but it will not go into recovery with any of them after it says it successfully wrote the recovery.
TWRP and CM just wait for a minute then reboot normal, AMON reboots then sits at the HTC screen... forever and i have to pull the battery.
I tried uninstalling RM to see if it was F'ing with it, didn't matter.
not sure what to try next to get a working recovery back onto the phone, I'm still rooted just running the stock ROM, I had loaded an alternate ROM successfully last week, just didn't like it. So I know all is 'working' as expected I just F'd up the recovery part now
any help??
afaik if you used the HTC unlock you need to fastboot flash it, or maybe hboot zip it? What have you tried so far?
I've tried using fastboot to flash amon and TWRP, same result
tried doing TWRP as a zip as well
what's weird is each method seems to "work" i get that it's pushing, writing, completed, no errors with any of them but then it just won't go into recovery and if i change to different recoveries I get different reboot behaviors just none of them work.
that's where I'm stuck, I feel like I've tried all the methods it just refuses to actually go into recovery when it's loaded.
another thing I thought was weird though, when I reflashed TWRP, and then go into RM it would say at the top that I had the latest version of CM installed like it didn't take? I uninstalled RM and tried it all again, same result.
morellox said:
I've tried using fastboot to flash amon and TWRP, same result
tried doing TWRP as a zip as well
what's weird is each method seems to "work" i get that it's pushing, writing, completed, no errors with any of them but then it just won't go into recovery and if i change to different recoveries I get different reboot behaviors just none of them work.
that's where I'm stuck, I feel like I've tried all the methods it just refuses to actually go into recovery when it's loaded.
another thing I thought was weird though, when I reflashed TWRP, and then go into RM it would say at the top that I had the latest version of CM installed like it didn't take? I uninstalled RM and tried it all again, same result.
Click to expand...
Click to collapse
*my opinion*
delete rom manager
boot into recovery using adb
"adb reboot recovery"
or terminal emulator
"reboot recovery"
or the app "quickboot"
does that work?
I've tried all those except Quickboot... *trying now......*
annnnnd
same thing with the app...
I'm thinking at this point I almost need to just write everything over again? use a flashable zip in the bootloader and just have it write everything over again, I was going to do a new rom anyways bored with the stock again.
so I need to find that I guess? re-write everything go back to fresh and start over
1. Make sure u r not flashing CDMA recovery over a GSM device, or vice versa.
2. How did u get ur device rooted in the first place?
3. Last resort, relock ur device and apply the correct RUU, then unlock and root again.
Sent from my HTC EVO 3D X515m using XDA App
1) good there
2) I followed a tutuorial where I pushed the recovery and the SU file after doing the HTC official unlock method, worked great at first, I'm the idiot that pushed the CM recovery over top of it and now I can't get a working recovery back on.
3) do I really have to relock first, I've seen the simple tutorial on doing so, I was hoping maybe I could find an all in one flashable ROM that would at least get me back to operational on all partitions and then re-work that one with a new ROM later or something, not possible?
This is of no help to you but - I had the same error. TWRP v1.0.3. I tried everything in the book to get it to work... but got stuck at the HTC splash screen like you. And I tried installing the 1.13 PG86IMG and then my device turned off while installing the PG86IMG (it was fully charged during flashing, I checked). Be careful with what you do.
I was unlocked with AlphaRev's tool, running my own ROM.
mine hung like that if i flashed AMON, but i could still pull the battery and go back into the bootloader to flash at least TRWP using FastBoot so I could get back into the phone
ugh
morellox said:
mine hung like that if i flashed AMON, but i could still pull the battery and go back into the bootloader to flash at least TRWP using FastBoot so I could get back into the phone
ugh
Click to expand...
Click to collapse
htc unlock method has proven to be a bit shady for the community in that it doesnt allow all the features/functions the revolutionary (and prior unrevoked) unlock method does.
most developers unlocked with revolutionary and haven't performed the htc unlock method so it has been hard to gather technical details on the htc unlock method.
one item we can eliminate in the effort to narrow down your issue: there is no working Amon RA recovery for the EVO 3D. not sure where you obtained Amon RA recovery. TWRP was created to pick up the torch from the Amon RA recovery as he retired from developing his recovery to support emmc devices.
stick to either flashing the twrp or cwm recovery images. there are only a handful of ways to load a custom recovery and only a handful of ways to boot the device into recovery mode.
i'd follow a logical pattern and work your way through the avaiable options. by following the available options one step at a time you should be able to narrow down which methods work and don't work. sorry it has been difficult as this htc unlock method is newer to the community we aren't as familiar with it as we are the revolutionary method.
ways to flash a custom recovery:
1) fastboot - fastboot flash recovery c:\downloads\recovery.img
2) bootloader - PG86IMG.zip file containing recovery.img and android-info.txt
3) flash_image - while in normal android mode (my app Flash Image GUI works well for this)
ways to boot into recovery mode:
1) turn device completely off and unplug USB. vol down + pwr loads bootloader. select recovery from the menu
2) from android mode: adb shell reboot recovery
3) from android mode: use a 3rd party app like quick boot.
this is all off the top of my head so it might not be an *exhaustive* list but it should cover all the common approaches. hope that helps and keep us updated! good luck!
damn...
I really appreciate everyone's help here I've been a part of various forums for a REALLY REALLY long time... from the days of Nextel, then I was a Palm Lover for a few years and now Android.
this obviously isn't urgent as my phone is working just fine, I just can't flash a new ROM since I can't get any recoveries working.
unfortunately I'm pretty sure I've tried all the methods listed above, I'm going to probably sit down sometime this weekend and systematically go through each method one more time just to be sure. TWRP worked for me just fine in the beginning, I flashed a ROM more than once, reverted back to my old ROM, made back ups, cleared cache's all the stuff I'd need to do.
thanks everyone, I'll keep trying
and no one knows of a flashable 'rom' that would have all the different partitions included in a zip or something like that? like.... what is in place of recovery in a stock phone? I can always unroot and start over but I did use the HTC unlock method so I hope that even works
got one to work! followed this method
http://forum.xda-developers.com/showthread.php?t=1239455
Related
Early today, I was working on a G2 trying to get it rooted with a custom ROM installed. I managed to root the phone and disable the bootloader security. From here, I attempted to install clockwork recovery via rom manager... here's where the disaster starts.
Everything seemed to be going well (no errors), so I tried to load a custom ROM. The Rom installation started but failed partway through. This is when I noticed that the clockwork recovery wasn't working properly. It was flickering and none of the options worked (screen just flashed or turned black if you selected anything). So at this point, the phone would not boot since the ROM installation didn't complete, and I had a buggy recovery image installed.
Unfortunately, the fun doesn't stop here. I figured that I should load the PC10IMG.zip and start from scratch... bad idea. This flashed the bootloader (relocking it) then failed-- leaving me with a bad ROM, bad recovery image, and a locked bootloader. Luckily for me, I was able to use adb via the buggy recovery to unlock the bootloader again.
At this point, I got a bit antsy and jumped the gun. I decided to use fastboot to erase and load a new recovery image. Unfortunately, I realized that I didn't have a recovery.img file to flash... just after I used the fastboot erase recovery command.
I'm hoping that someone here has a recovery.img file compatible with the T-Mobile G2 so I can flash the recovery partition with fastboot. If anyone has any better ideas I'm open to suggestions.
Thanks in advance for any help.
Install amon recovery. It's much better then clockword. Do it using adb
Sent from my HTC Hero using XDA App
Just an update. I couldn't get into adb but I was able to flash clockwork via fastboot. For whatever reason, the amon recovery would go through. Nevertheless, I installed cyanogen using clockwork and everything is gravy!
i have been searching these forums for the past few days and have come up dry.. i have an htc rezound and I want the OTA BUT i have perm rooted it and removed most (if not all) the bloat... how do i go about rebloat and relocking my phone? i have tried using cleantool and it keeps waiting for the phone or it just fails all over itself repeatedly
edit: i have it set to charge only, sync is off and closed, and it is in fastboot mode. I have also tried something I found on here which seems like it is very similar to cleantools with less functionality and it just says <waiting for device> indefinitely
twich12 said:
i have been searching these forums for the past few days and have come up dry.. i have an htc rezound and I want the OTA BUT i have perm rooted it and removed most (if not all) the bloat... how do i go about rebloat and relocking my phone? i have tried using cleantool and it keeps waiting for the phone or it just fails all over itself repeatedly
edit: i have it set to charge only, sync is off and closed, and it is in fastboot mode. I have also tried something I found on here which seems like it is very similar to cleantools with less functionality and it just says <waiting for device> indefinitely
Click to expand...
Click to collapse
There are a few different ways to do it. Easiest way I did it to make it foolproof, is flash stock recovery if your on a custom recovery and relock phone and run the RUU. It will put you back to stock and you can just download the OTA and update it, then Unlock and flash Amon Ra recovery and from the developer menu install SU and superuser to reroot.
If you need more instructions , just ask otherwise to me that was the easiest way.
P.S. Just be aware the internal SD card gets wiped after you unlock again so move anything off the internal SD to the external SD that you want to save prior to unlocking again.
I didnt take the ota, I used cons ota rom.. this was my steps for that
1) download rom from here http://forum.xda-developers.com/showthread.php?t=1467329
2) boot into recovery, flash rom....
here you can go two ways, if you dont want the new baseband, it will flash the ph98img and not do anything, if you want the new radios I will tell you how I did it, then tell you where you need to start if you wont want them.
3)perform nandroid
4)via adb (thing you used to unlock originally) fastboot oem lock YOU ARE NOW LOCKED.
5)boot into hboot it will flash the ph98img
6) Unlock bootloader (find the email with the unlock.bin code and follow those instructions)
7)Reboot phone
8)connect to pc, charge only usb debugging enabled
9)run one click root
Proceed with this if you get the mainver error ONLY otherwise if having wifi issues, proceed to step 13
10) after rooted follow this post http://forum.xda-developers.com/showthread.php?t=1467099 NOTE, op in the thread supplied his miscnew.img USE IT!
11)Read this thread http://forum.xda-developers.com/showthread.php?t=1459347&highlight=mainver it will explain how to get the ph98s to work.
11a) do the ph98 file thing to the ph98 img in amon ra to get it to flash in bootloader
12) after amon ra is restored, perform restore nandroid.
If wifi is not working, even if you dont have mainver issues do step 13
13) If having wifi issues as in not working go to this thread http://forum.xda-developers.com/showthread.php?t=1467793 and follow instructions EXACTLY!!!
Now you should be running new radios, hb2.11, the 2.6 kernel etc.
You will have to follow the post in step 11 to get any ph to work from now on.
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE, BURN YOUR HOUSE DOWN OR ABDUCTED BY ALIENS BY FOLLOWING THE ABOVE INSTRUCTIONS.
im having some trouble getting into recovery because clockworkmod says it does not have an officially supported recovery... how do i manually install one?
Assuming you installed a recovery, just boot to Hboot. Pull the battery, then hold the power button and volume down button. Once in Hboot you can choose Recovery.
twich12 said:
im having some trouble getting into recovery because clockworkmod says it does not have an officially supported recovery... how do i manually install one?
Click to expand...
Click to collapse
To flash a recovery do the above steps to get into hboot (power down, pull battery, hold volume down and power buttons) and once you are in hboot, choose fastboot. Then connect to your pc and in the pc cmd prompt type:
fastboot flash recovery nameofrecovery.img (name of stock recovery you need to download, trying to find a link for you...)
That will put the stock recovery on the phone, then you can run RUU to get the rest back to stock and you can then accept the OTA.
feralicious said:
To flash a recovery do the above steps to get into hboot (power down, pull battery, hold volume down and power buttons) and once you are in hboot, choose fastboot. Then connect to your pc and in the pc cmd prompt type:
fastboot flash recovery nameofrecovery.img (name of stock recovery you need to download, trying to find a link for you...)
That will put the stock recovery on the phone, then you can run RUU to get the rest back to stock and you can then accept the OTA.
Click to expand...
Click to collapse
got it! OTA and everything.. debating on rerooting for a bit thanks a lot everyone! +rep
All you have to do to reroot now is flash Amon Ra and then install su from within that. So it's super easy at this point.
su seems to have remained installed.... no root but su is definitely still installed! the only reason i am going to wait on rerooting is so i can learn more about it before i flash or anything
Yeah, it will show up in your apps but it doesn't work properly until you reinstall. I thought I had remained rooted but when I went to use Titanium Backup it couldn't get root access, then after I reinstalled su it worked fine.
But yeah, if you don't need it yet don't worry about it. The only good reason to do it is to use TiBU to save all your settings and if you have Amon Ra you can make a nandroid of your phone so that if something happens you have a backup image of everything and can restore it very easily via Amon Ra. You can still stay on stock ROM etc... the only thing you would need to flash is the Amon Ra recovery.
ya i see what you mean... I also want to get rid of this unbelievable amount of bloat... geez their are a ton of useless verizon apps never mind the stupid games
HTC Dumlock
HTC Dumlock is a workaround for devices with HTC's unlock that cannot flash boot from recovery. Put simply, we make backups of recovery and boot, then we flash the backup of recovery to boot. When you reboot normally, you'll be in your recovery, but since your recovery is flashed to boot, you can make changes to boot. Head on over to our website for download links and instructions.
New v2 version scans / compares the backups of boot and recovery to help ensure that you don't run it twice and wipe out your backup of boot.
Hooray for Team Win! Here's my contribution:
http://rootzwiki.com/_/articles/rec...unlock-and-flashes-kernels-from-recovery-r432
Awesome work guys!
Sent from my Clean and MeanROM 3D
Can we flash custom roms with unlocked phone and hboot 1.5 with s-on directly from recovery now?
Edit: Nevermind the answer is yes. you guys are awesome.
this is awesome if i ever get hboot 1.5 again. Wish this was out a week ago i wouldn't of sold my phone so i could buy one with hboot 1.4
Kernels ok, but are we able to flash radios and such with this method?
I just htc unlocked, flashed the updated twrp via fastboot, then backed up, flashed su, installed HTC DumLock. When I try to use the app it finishes within a minute but does not reboot, rebooting to system reboots doesn't boot into TWRP. I gave the app root permissions, what else should I try?
Real cool news
This is awesome! Kudos! I'm a little squeamish to try it yet (I'm still android noobish ;-) ); I'll wait a bit until the more seasoned folk work the kinks out, but I'm extremely encouraged.
Edit: Changed notification
i tried twice to flash a kernel and i get is the progress bar sits there, i let it go for 10 minutes each time but it never flashed the zip
UPDATE: I got it i had to restore the backup
Everything went fine for me until i try to boot to system from recovery,it just reboots back to recovery
I even tried powering down and do a normal start and it go's into recovery
Can the recovery be made to recognize when it is booted using dumlock app and restore original boot automatically? Something like this,
Run dumlock app, writes recovery to boot but also sets a flag in your config file on the sdcard,
reboot to recovery in boot partition,
recovery sees flag in config file, then before allowing any interaction flashes your boot partition back to original and then allows you to flash away and reboot normal afterwards.
This to me would seem to make it a seemless process. I would think a modification could even be made to CM9 code that would execute the same type of commands to rewrite recovery to boot whenever you select "reboot to recovery" from the reboot menu by holding the power button to make this 100% seemless, no?
can I flash a radio with 1.50?
benny3 said:
UPDATE: I got it i had to restore the backup
Everything went fine for me until i try to boot to system from recovery,it just reboots back to recovery
I even tried powering down and do a normal start and it go's into recovery
Click to expand...
Click to collapse
re-read the instructions paying particular attention to steps 13-18.... then repeat step 18 like 9 times or so
gotojanoo said:
can I flash a radio with 1.50?
Click to expand...
Click to collapse
no...you are still s-off
alvintimothyjr said:
no...you are still s-off
Click to expand...
Click to collapse
actually am s-on with 1.50
Holy smokes, such an elegant solution. Doing this when I'm off work.
If u cant use fast boot to get to recovery how do u flash straigh to recovery?
Sent from my ADR6400L using Tapatalk
Anyone got this successfully working?
gotojanoo said:
actually am s-on with 1.50
Click to expand...
Click to collapse
Yeah that's what I meant...my bad
Interesting.
Is it basically copying the recovery image to the boot partition to get full access for flashing kernels/roms, then copying the recovery back afterwards?
I was wondering if someone would come up with something like this. Specifically, I had been wondering if there was a way to run fastboot from sdcard vs Pc to enter recovery.
Hi all,
It seems that I have managed to brick my device. I am on 1.50 S-ON, and was trying to flash one of the ICS ROMs through the usual method (push the zip, reboot to bootloader, fastboot to the recovery.img) which I have used multiple times successfully in the past, but the phone ended up in a reboot loop. I did not apply any firmware changes (at least not voluntarily!), since the ROM (CleanROM was the first one I tried to flash) said that this was necessary. I tried flashing different ROMs (GB or ICS), and a Nandroid backup, but none seem to work. The only clue I have as to what is going on is that fastboot says that there is no image of PG86DIAG.[zip,nbh] and PG86IMG.[zip,nbh,tar,aes,enc]. This looks like a radio issue to me, but I don't want to do anything stupid (again!), so any input would be appreciated.
Thanks a lot!
I would recommend flashing this: http://dev-host.org/ru0ow8ps0i01/PG86IMG_2.17.651.5.zip
Its haus's 2.17 fw package and has everything in it. I flashed the new fw and a rom and had the same bootloop and nothing stopped it except returning to a stock system. After flashing this i flashed a new rom and everything worked as normal.
Rename the zip file PG86IMG.zip put on root of sdcard and reboot to bootloader. (Just in case anyone needs to know) This is a completely stock rom and fw so you will need to flash another rom with superuser in it for root apps.
Hope that helps...
If I'm reading it correctly you tried ics flash and it failed and now you wanna go back or flash to another working Rom right?....if so, unplug phone from comp, pull battery and reboot into bootloader (power +vol up), pick fastboot, connect to comp, use fastboot command to get into recovery and wipe and flash a working Rom....that's also assuming you already have a Rom on sdcard......if not then push a tom to card or in cwm you can mount USB storage and do drag and drop....I really hope that points you in right direction....let me know.
With hboot 1.5 s-on you have to do the fastboot command in order to get into recovery in order to do flashes...
Sent from my PG86100 using XDA
It booted!
Hey both,
I did somehow manage to flash a regular GB ROM. The weird thing is I was doing the exact same thing I was doing before (which is onefasttereopro's method), but for whatever reason it didn't work until now. The one thing that did in fact change is that I tried flashing Chad's kernel to see if any of the ICS ROMs would work, but I don't think that's it (it seems to have been overwritten, judging by /proc/version and the fact that USB works). Thank you very much both for your help, I am very glad that I have a working device again!
I am running santod's rooted Stock ICS rom, which has been running excellent, love it very much. Today I went to do a backup in recovery and noticedit will not boot into recovery. I am running the 4EXT recovery as suggested in the rom forum post. Nothing I do seems to be able to boot the recovery. I can't reboot into recovery from the 4EXT app. I boot the phone with the volume down key, and try to enter recovery from there. Still nothing. I get my initial boot logo, then screen goes black, then boot logo again and it proceeds to boot up normally. I have tried re-flashing the recovery from the 4EXT app, I even tried rom manages and using the latest clockwork mod recovery. Nothing gets me into recovery. Also have noticed my phone will not stay powered off when on the charger. If I power off, plug the charger in, after a few seconds phone powers itself on. Could it be related?
I followed the rom installation instructions to the letter.
Installed the 4EXT recovery.
Flashed the ICS radios.
Wiped all my partitions except my SD card.
Flashed rom and have enjoyed for weeks now.
Only other info I know to provide is I installed the debloated/deodexed rom
Did not flash the kernel as I didn't experience boot loops.
Thanks in advance for any assistance folks!
JM1084 said:
I am running santod's rooted Stock ICS rom, which has been running excellent, love it very much. Today I went to do a backup in recovery and noticedit will not boot into recovery. I am running the 4EXT recovery as suggested in the rom forum post. Nothing I do seems to be able to boot the recovery. I can't reboot into recovery from the 4EXT app. I boot the phone with the volume down key, and try to enter recovery from there. Still nothing. I get my initial boot logo, then screen goes black, then boot logo again and it proceeds to boot up normally. I have tried re-flashing the recovery from the 4EXT app, I even tried rom manages and using the latest clockwork mod recovery. Nothing gets me into recovery. Also have noticed my phone will not stay powered off when on the charger. If I power off, plug the charger in, after a few seconds phone powers itself on. Could it be related?
I followed the rom installation instructions to the letter.
Installed the 4EXT recovery.
Flashed the ICS radios.
Wiped all my partitions except my SD card.
Flashed rom and have enjoyed for weeks now.
Only other info I know to provide is I installed the debloated/deodexed rom
Did not flash the kernel as I didn't experience boot loops.
Thanks in advance for any assistance folks!
Click to expand...
Click to collapse
Did you rename or remove the Radio file from the sd card as suggested in the OP of the rom thread?
It will not let you get into Recovery if there is a PG05IMG.zip present on the root of the sd card.
If that's not the case, reflash 4ext from within the Recovery control app.
Just installing the app doesn't install the Recovery.
You must also install the actual Recovery from within the app if you haven't.
santod040 said:
Did you rename or remove the Radio file from the sd card as suggested in the OP of the rom thread?
It will not let you get into Recovery if there is a PG05IMG.zip present on the root of the sd card.
If that's not the case, reflash 4ext from within the Recovery control app.
Just installing the app doesn't install the Recovery.
You must also install the actual Recovery from within the app if you haven't.
Click to expand...
Click to collapse
Yeah, there is no PG05IMG.zip in the sd card root. Also I have tried reinstalling the recovery from the 4EXT recovery control app.
Current verson of recovery installed is 4EXT Recovery Touch v1.0.0.5 RC8.
Tried reflashing that, and also the RC9 test build that is out right now.
Still no go on getting into the recovery.
Thanks.
When you do the volume down and power option with the device off, you need to first press the volume down and then while holding that, then press and also hold the power button, you should feel it vibrate, keeeeeep holding them down, do not let go.
Wait until you see what should be a white hboot screen with menu options, then you may let go.
If you hold power first or don't hold them both down long enough, it will just try to boot normally.
Not that that would explain why you can't get there from within Recovery Control app.
What is your hboot version and how did you root your device?
santod040 said:
When you do the volume down and power option with the device off, you need to first press the volume down and then while holding that, then press and also hold the power button, you should feel it vibrate, keeeeeep holding them down, do not let go.
Wait until you see what should be a white hboot screen with menu options, then you may let go.
If you hold power first or don't hold them both down long enough, it will just try to boot normally.
Not that that would explain why you can't get there from within Recovery Control app.
What is your hboot version and how did you root your device?
Click to expand...
Click to collapse
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
JM1084 said:
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
Click to expand...
Click to collapse
Yes, you can flash Recovery images from hboot, just like you flash a radio.
With it named PG05IMG.zip and placed on the root of the sd card.
HERE is one you can try.
If that doesn't work, I may have something you can try from fastboot to clear the Recovery cache, and maybe that will resolve the issue.
I have only seen one other user have this occur and his device simply ended up getting replaced because he wasn't able to mount to usb for doing fastboot commands either.
santod040 said:
Yes, you can flash Recovery images from hboot, just like you flash a radio.
With it named PG05IMG.zip and placed on the root of the sd card.
HERE is one you can try.
If that doesn't work, I may have something you can try from fastboot to clear the Recovery cache, and maybe that will resolve the issue.
I have only seen one other user have this occur and his device simply ended up getting replaced because he wasn't able to mount to usb for doing fastboot commands either.
Click to expand...
Click to collapse
Still no go flashing that recovery in hboot. What is the process of clearing recovery cache?
On a side note, in talking to my father, his bolt seems to have the same issue. We both were rooted with the same method, and I believe we have the same hboot version. Only difference is he flashed the rom using clockwork recovery.
Edit: I confirmed his hboot is 6.04.1002. same as mine
JM1084 said:
Still no go flashing that recovery in hboot. What is the process of clearing recovery cache?
On a side note, in talking to my father, his bolt seems to have the same issue. We both were rooted with the same method, and I believe we have the same hboot version. Only difference is he flashed the rom using clockwork recovery.
Click to expand...
Click to collapse
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
santod040 said:
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
Click to expand...
Click to collapse
Alrighty, I will give that a shot. I am at work right now and am about to head out of town so I will be unable to try it until sunday. I'll post the results here asap. Thanks again!
Same ROM, same problem,I even tried flashing a different recovery. Rooted using really old one click method a month after thunderbolt release.
Sent from my HTC Thunderbolt
zomgalama said:
Same ROM, same problem,I even tried flashing a different recovery. Rooted using really old one click method a month after thunderbolt release.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
What is your h boot version?
Sent from my ADR6400L using Tapatalk 2
santod040 said:
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
Click to expand...
Click to collapse
No Go, my tbolt will not mount in Win7, it just says the device has malfunctioned. Rebooting into the bootloader with USB in will not show anything in Windows, even in fastboot. It makes the device connection sound but no devices show up. Running the CMD file in the zip you linked does nothing, I'm at 10 minutes now where it just says "Waiting for device". Is my device just done for?
JM1084 said:
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
Click to expand...
Click to collapse
I think I had a similar problem once. Boot back into your hboot screen. Then select "factory reset". If you have a 3rd party recovery installed, like it sound like you have (4ext, right?), it will boot you to recovery so you can administer the reset yourself (it doesn't actually wipe anything, just brings you to your recovery's home screen).
Let me know how it goes.
coltspackers said:
I think I had a similar problem once. Boot back into your hboot screen. Then select "factory reset". If you have a 3rd party recovery installed, like it sound like you have (4ext, right?), it will boot you to recovery so you can administer the reset yourself (it doesn't actually wipe anything, just brings you to your recovery's home screen).
Let me know how it goes.
Click to expand...
Click to collapse
Thanks for the info, but this didn't work either. I'm also on 6.04.1002 and rooted mine a week after the T-Bolt shipped manually via adb.
This happened about a month ago also, and I thought it was ext4 but managed to get an older TWRP recovery to work after working on it for about a day and a half without a working phone. At least I have a working phone at this point.
Same ROM, same recovery (4ext), same problem. Rooted by adb a month after launch, hboot 6.04.1002
allo_87 said:
Same ROM, same recovery (4ext), same problem. Rooted by adb a month after launch, hboot 6.04.1002
Click to expand...
Click to collapse
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
santod040 said:
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
Click to expand...
Click to collapse
Excellent advice, thanks man.
Sent from my ADR6400L using Tapatalk 2
My thunderbolt's recovery spin mysteriously started working again yesterday, not sure why.
Doesn't matter though since I switched carriers now:/
Sent from my Sprint LG Optimus G
Still nothing for me. Worse yet is the fact that I can't adb because my usb has not worked properly since "the soup incident"
Sent from my ADR6400L using Tapatalk 2
santod040 said:
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
Click to expand...
Click to collapse
After going over the issue with Max and trying several fixes he suggested (he even made me an app that would format my cache), it seems I either need to obtain an RUU and flash the stock software/recovery back on and re-root or try flashing an updated hboot that already has s-off. The thinking is that it is my hboot that is causing the issue. Does anyone know what files I need? I have a couple of things to try at home to see if I can get my usb working again, if not, anything I do will have to be a flashable zip from the bootloader. Thanks!