Hi, I was running Meanrom 36 s-off....everything was great! Then I flashed Paranoid Androids boot.img with Flash Gui and rebooted (intending to do the ROM next). It now reboots to the Meanrom screen and stops. Won't boot into recovery and wont mount. Any way to just get back to Meanrom???
LazyPanda
Jewel Pvt Ship S-off rl
Cid-Spcs_001
Hboot 1.12.2222
OpenDsp-v25.1.0.32.0405
eMMC-boot
If you have s-off then there is no real need for flashgui, just flash from recovery
Why are you using the kernel workarounds with S-OFF? Just flash the ROMS normally.
Also, this is why people shouldnt use flash image GUI unless they already know how to do it manually from fastboot. Because if something goes wrong they are screwed
these threads are starting to remind me of that time my neighbor gave his son a box of matches....
I didn't realize that when I began. Its been awhile since I've done this and i suck. Cant reboot into recovery now, just reboots normally then gets stuck on the Meanrom boot screen. Matches? I think I've been handed C4!
okay well the most basic BASIC solution would be to try and restore a nandroid backup, you're s-off so thats not a problem, otherwise boot recovery, use a wipe script and install a rom. After you get the phone going again, never ever touch anything like flash gui again, learn basic adb, read up on the features your recovery offers, learn to trouble shoot your phone using adb tools, from within recovery, just by using the rom, or hell check out the irc channels and watch the devs troubleshoot problems themselves. some of them are more then willing to help if they have the time to do so
How can I restore the backup if I can only boot into bootloader? I completely agree. Hell I don't even want to flash another ROM again! I loved Meanrom....
cmm67 said:
How can I restore the backup if I can only boot into bootloader? I completely agree. Hell I don't even want to flash another ROM again! I loved Meanrom....
Click to expand...
Click to collapse
You should be able to boot into the bootloader. Power down the phone by pressing the power button and volume down key for about 15 seconds. The phone will power off and then press and hold down the volume down button and press the power button at the same time for about 5 seconds. Continue to hold the volume key and your bootloader should load. You should then select fastboot and then reboot recovery or recovery can't remember which it shows. The phone will power off and power back on and should boot int recovery. Then you can nandroid provided you nandroid before you flashed the Rom. If you didn't then just flash the Rom again no need to wipe anything Mean Rom wipes davlik already. Then once the Rom is done flashing you should be good.
Sent from my EVO using xda premium
yes, I can reboot into bootloader. When I select recovery it just reboots normally and then gets stuck on the Meanrom boot screen. Never opens recovery
I guess that means you need to fastboot recovery
edit: sorry if it seems I left you hanging, in my area wimax is the only means of internet and to top it off im in a spot that struggles to get wimax despite the fact that all around the outside of my house I can perfect signal
cmm67 said:
yes, I can reboot into bootloader. When I select recovery it just reboots normally and then gets stuck on the Meanrom boot screen. Never opens recovery
Click to expand...
Click to collapse
Reflash the recovery. You can download it from twrp website...the lastest version you should be able to flash recovery via fastboot using
Fastboot flash recovery (recovery file name)
The direction are on the twrp website. The lastest version is 2.2.2.0 .
Flash thay and then reboot the bootloader and then fastboot
Fastboot reboot recovery
It should then load into recovery
Sent from my EVO using xda premium
Thanks! Ended up flashing recovery again in fastboot then could restore my nandroid. I was so lost
Sent from my EVO using xda app-developers app
I really appreciate everyone's help!
Sent from my EVO using xda app-developers app
Related
i was able to successfully unlock bootloader, was able to flash a rom successfully, used that rom for a good couple days. then i decided to try a new rom InfectedROM Eternity™ | RLS_1.5 | NIGHTLYS | 3.0 & 3.5 | XE BEATS |(http://forum.xda-developers.com/showthread.php?t=1277431&highlight=stock+radio), so i went into recovery, wipe cache, dalvik, factory reset, system. then i flashed the new rom, new rom loaded but stuck in that roms boot screen.
i went back to recovery wiped everything out again, installed the 1st orig rom i installed, now it just loads to the htc boot screen, & every 30sec or so the htc boot screen would go off & come back on. i went to recovery wiped everything again, did nandroid restore, same results, any suggestions?
what im using:
unlocked bootloader
s -on
hboot 1.50
using teamwin recovery v2.0
Just wipe flash a new rom. Should be good to go
reaper24 said:
Just wipe flash a new rom. Should be good to go
Click to expand...
Click to collapse
already tried no luck
flyimages said:
already tried no luck
Click to expand...
Click to collapse
Did you apply any tweaks or different kernels? was your kernal that you are on now compatible with the rom that you had put on? The recovery your on, r you on 2.0 or the second releaese of 2.0?
You could try to reflash your recovery and then try to nandroid back. Or try a different kernel and or different rom and go from there. Kind of hard to diagnose bc not sure of exactly what you have done completely. If all else fails, search for the ruu and re apply the original rom and re root.
From my guess, it sounds as something that was applied didn't apply right. Again, not sure on all the details.. I know its not much to go on but good luck on it.
Look at the bright side, your obviously not bricked and if you have to re apply the original and start over, its not that bad. Just a little time out of the afternoon.
only update i did was the rom
tried about 2 more diff roms, still same issue
hmm.. i also choose the "system format" in twrp, would that have done some damage?
Are you using fastboot to boot into recovery? If not, and you're hboot 1.5, then that's your problem.
And wiping system wouldn't cause any issues as long as you flash a new ROM after wiping the system, before you reboot.
Sent from my HTC Evo 3D using Tapatalk
k2buckley said:
Are you using fastboot to boot into recovery? If not, and you're hboot 1.5, then that's your problem.
And wiping system wouldn't cause any issues as long as you flash a new ROM after wiping the system, before you reboot.
Sent from my HTC Evo 3D using Tapatalk
Click to expand...
Click to collapse
ah ok i manually go into hboot with the down volume + power. did "fastboot reboot-bootloader" into bootloader, wiped out everything & reinstall rom, still same issue.
Try extracting the boot.img from the zip file containing the rom and flashing it with with fastboot binary. If you have S-ON, CWM can't flash the boot partition so you'll get bootloops with any rom that needs a custom initrd.gz. You need to manually flash the boot partition.
flyimages said:
ah ok i manually go into hboot with the down volume + power. doing fastboot into bootloader now, so we'll see.
Click to expand...
Click to collapse
Yea, do adb reboot bootloader, and then do fastboot boot recovery.img.
You will need to make sure that you have a copy of your recovery.img in the folder that you are working out of when you issue the fastboot boot recovery.img command
Sent from my HTC Evo 3D using Tapatalk
k2buckley said:
Yea, do adb reboot bootloader, and then do fastboot boot recovery.img.
You will need to make sure that you have a copy of your recovery.img in the folder that you are working out of when you issue the fastboot boot recovery.img command
Sent from my HTC Evo 3D using Tapatalk
Click to expand...
Click to collapse
thanks all for the help, the "fastboot flash recovery recovery.img" was pretty much what i was missing!
wow didnt wonder somethin so small could cause something this big, i got everything up & running now!
flyimages said:
thanks all for the help, the "fastboot flash recovery recovery.img" was pretty much what i was missing!
wow didnt wonder somethin so small could cause something this big, i got everything up & running now!
Click to expand...
Click to collapse
glad to see your on the up and up
Okay, I'm having the same problem. No matter what I do, I get stuck in a boot loop after installing a rom. Extracting the boot.img and flashing in fastboot doesn't do a thing. My nand backups don't work either (get stuck at restoring boot).
Don't have any problems installing recovery and gaining root. I'm at a loss here. I really want to get my MIUI on!
Mes3 said:
Okay, I'm having the same problem. No matter what I do, I get stuck in a boot loop after installing a rom. Extracting the boot.img and flashing in fastboot doesn't do a thing. My nand backups don't work either (get stuck at restoring boot).
Don't have any problems installing recovery and gaining root. I'm at a loss here. I really want to get my MIUI on!
Click to expand...
Click to collapse
Are you booting your recovery from fastboot? Fastboot boot recovery.img. If not, boot.img won't flash. It's not necessary to flash the boot.img separately, just boot your recovery from fastboot and you'll be good.
Sent from my HTC Evo 3D using Tapatalk
Yup, definitely booting recovery from fastboot.
I had the same problem try to install new recovery VIA fastboot an wipe data/factory reset then flash new ROM u should be all set to go
Sent from EPIC JWOLF 1 using XDA App
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.
i have been running Synergy Rom and causing a lot of problems so I have been tryin to install a numerous amount of roms and after wiping the phone back to factory and the dalvik then when its time to reboot the system i reboot the phone it just stays in the HTC boot up screen. so after a wait 10 or so min i just reload the Synergy rom which is the only one that works.
i am also running Revolutionary CWM v4.0.1.4 if that helps
i would really appreciate it if someone could point me into the right the direction thank you.
Are you on hboot 1.5? Are you flashing the correct kernel?
We're comin from a pure power source.
Yes it is and to be honest I haven't flashed them with any kernels cuz I never have before
Hmmmm, and you're doing a full complete wipe right? Which recovery are you using
We're comin from a pure power source.
Revolutionary CWM v4.0.1.4 and yes full wipe and dalvik.
Have you tried a different recovery?
We're comin from a pure power source.
nspyr05 said:
i have been running Synergy Rom and causing a lot of problems so I have been tryin to install a numerous amount of roms and after wiping the phone back to factory and the dalvik then when its time to reboot the system i reboot the phone it just stays in the HTC boot up screen. so after a wait 10 or so min i just reload the Synergy rom which is the only one that works.
i am also running Revolutionary CWM v4.0.1.4 if that helps
i would really appreciate it if someone could point me into the right the direction thank you.
Click to expand...
Click to collapse
ok as you know the roms come as .zips and we apply them through recovery.... some times that recovery doesnt writ the boot img correctly.... try installing ANY rom....then try to boot up... if it hangs at htc then pull the battery out then put it right back in and hold vol down and press power..then connect the phone to your computer so on your phone you see "fastboot usb"now the rom you tried installing that was the zip have a copy of that on your computer and open up with any program you use to open zips...extract that boot.img file to your fast boot file and where adb is too ,once extracted go back to your terminal window and type in
fastboot flash boot boot.img
it should say that its sending the data then writing it and then from there wait about 30 seconds and then select reboot and the rom should boot up
nspyr05 said:
Yes it is and to be honest I haven't flashed them with any kernels cuz I never have before
Click to expand...
Click to collapse
You cannot directly install ROMs with custom kernels on hboot 1.5 .
You always have to use "fastboot boot <your recovery>.img" or "fastboot flash boot boot.img" like the above post says..... If you dont use PC to flash ROMs with custom kernels , you will always get stuck on the HTC screen.
If you want to be able to flash ROMs / kernels / radios etc without PC, downgrade your hboot from 1.5 to 1.4.
Get flash image GUI from market to bypass fast boot and install custom kernels, or downgrade using unbeknownforce method and closeones live cd
Sent from my PG86100 using xda premium
Are you s off and if your knott you may need to use the GUI app from the market
Sent from my HTC EVO 3D X515m using xda premium
Idk if someone already said this but for 1.5 boot you need to go into fasboot usb . Fastboot boot recovery.img
Replace "recovery" with recovery file name. If your using 4.0.1.0 it might be. Cwm-4.0.1.4-shooter.img something like that
Second option is use 4EXT and you won't need to use your computer to flash rooms or kernels
Sent from my PG86100 using Tapatalk
First I assume you have the adb drivers.
place new rom on sd card
boot phone in bootloader, select fastboot
Access the adb folder via CMD
type in fastboot boot recovery.img
it should say waiting for device then connect..
you'll see the recovery screen
this will let you wipe and install new rom on hboot 1.5
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!
Hi, I oem unlocked my Nexus 9, installed TWRP and SuperSU, but I think I missed a step before I can go to custom ROMs and all. I've looked for instructions but I'm just getting confused. I firstly cannot reboot into TWRP unless I fastboot boot recovery from my PC every time. If I don't do that, it just boots into the Flounder PVT Ship white screen with Fastboot USB in red and below that HBOOT, REBOOT, REBOOT FASTBOOT, and POWER DOWN.
What step am I missing in this process? Do I need some sort of custom image or what am I doing wrong?
Thanks,
Chris
Hello,
It can get a bit confusing sometimes and people generally expect you to just know lol.
You've not missed a step. Getting into recovery is irritating lol. For as long as I've had it if booted into recovery from the power menu lol xD.
Reboot the Google Nexus 9 by holding the Power and the Volume Down buttons at the same time and wait until the tablet display shows a Google splash screen before releasing the buttons.
If you get a android with an exclamation mark then you've made a boo boo. Dw, even us pros muck up ;]
Go back to your fastboot. Flash twrp like you do. But this time once you've flashed it type
Code:
fastboot boot recovery twrp.img
That should boot your device into recovery after flashing it.
There it should be stuck on there nicely of it takes a while Dw. That's just the fun of owning a N9 lol. That should Do it .
Happy Flashing.
Give us a Thanka if I helped
ChrispyChris said:
Hi, I oem unlocked my Nexus 9, installed TWRP and SuperSU, but I think I missed a step before I can go to custom ROMs and all. I've looked for instructions but I'm just getting confused. I firstly cannot reboot into TWRP unless I fastboot boot recovery from my PC every time. If I don't do that, it just boots into the Flounder PVT Ship white screen with Fastboot USB in red and below that HBOOT, REBOOT, REBOOT FASTBOOT, and POWER DOWN.
What step am I missing in this process? Do I need some sort of custom image or what am I doing wrong?
Thanks,
Chris
Click to expand...
Click to collapse
If you installed TWRP using
Code:
fastboot flash recovery twrp.img
The only ways I know to get into recovery are to reboot to recovery from the Power menu of your ROM
OR
Boot to fastboot, select HBOOT, then select Recovery. If TWRP is installed as your recovery this will boot TWRP. If it goes to the dead droid screen then you need to install TWRP properly, using the fastboot flash command above.
I can't get my nexus 9 to run twrp as well.
I go to fastboo, select Hboot, then I get the android with exclamation, volume up and power brings up the original android recovery menu, not twrp. I've unlocked the bootloader, wiped everything and tried again, no luck. Always the same result
Mephisto_POA said:
I can't get my nexus 9 to run twrp as well.
I go to fastboo, select Hboot, then I get the android with exclamation, volume up and power brings up the original android recovery menu, not twrp. I've unlocked the bootloader, wiped everything and tried again, no luck. Always the same result
Click to expand...
Click to collapse
Are you using the newest TWRP? 3.1.0.0? It's not working for me either, can't boot to recovery. Use 3.0.2.2 or whatever the last version was
I used the 3.1.0.0
the trick was, after installing it, reboot straight back into recovery, so it doesn't get overwritten