[Q] Help!!! Phone stuck in TWRP boot loop!! - Sprint HTC EVO 4G LTE

I installed the CM10 9/21 nightly on my phone, and upon reboot it is now just jumping into TWRP, no matter what reboot option I select.
I've already tried fixing permissions, wiping cache/Dalvik, even going so far as to wipe system/factory reset and reinstalling the nightly, all with no success. I can't seem to boot past TWRP.
Can anyone help?

tendomentis said:
I installed the CM10 9/21 nightly on my phone, and upon reboot it is now just jumping into TWRP, no matter what reboot option I select.
I've already tried fixing permissions, wiping cache/Dalvik, even going so far as to wipe system/factory reset and reinstalling the nightly, all with no success. I can't seem to boot past TWRP.
Can anyone help?
Click to expand...
Click to collapse
Did you try flashing sense rom?
Sent from my lair.

volk9029 said:
Did you try flashing sense rom?
Sent from my lair.
Click to expand...
Click to collapse
I finally figured it out. Somehow, the boot image had gotten corrupted. I fastbooted into the phone and replaced it and the phone finally booted normally.
Scared the crap out of me.
I'm kinda missing the relative simplicity of my old Evo 4G...I hope I can get this stupid S-OFF soon.

I have an LG2x with the same problem. How do you fastboot, and what did you replace? Any help would be appreciated.
QUOTE=tendomentis;31859818]I finally figured it out. Somehow, the boot image had gotten corrupted. I fastbooted into the phone and replaced it and the phone finally booted normally.
Scared the crap out of me.
I'm kinda missing the relative simplicity of my old Evo 4G...I hope I can get this stupid S-OFF soon.[/QUOTE]

Get rid of TWRP
How can I get rid of the TWRP? Take the phone back to stock off the shelf OS.

Boot to bootloader, enable fastboot and from command prompt type fastboot oem lock. Download ruu and run it, it will rewrite the phone
Do you have adb tools or sdk?

om4 said:
Boot to bootloader, enable fastboot and from command prompt type fastboot oem lock. Download ruu and run it, it will rewrite the phone
Do you have adb tools or sdk?
Click to expand...
Click to collapse
I have SDK but not ADB. Everything I do reverts back to the TWRP.

Adb and fastboot is built into sdk, open terminal navigate to sdk and relock the bootloader then ruu

RuggyPuppy said:
How can I get rid of the TWRP? Take the phone back to stock off the shelf OS.
Click to expand...
Click to collapse
Thank you. That is what I had to do.

Related

[Q] Stuck in HTC boot loop after a rom install

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

[Q] Can't access recovery

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!

[Q]Flyer won't go past HTC Screen

Hi, I tried to put NexusFlyer on my Flyer Wifi-only. I did everything ok, unlock, root, install SU, and install ROM. When it went to reboot, it wouldn't go past the HTC Screen. I feel like its the boot.img but I did that before going into recovery.
Help?
Hey. What android version were you on when you rooted. Gingerbread or Honeycomb?
TheWizardOfROMs said:
Hey. What android version were you on when you rooted. Gingerbread or Honeycomb?
Click to expand...
Click to collapse
honeycomb, the latest ota update
it now just goes to CWM recovery and that will just close and turn off randomly... I don't know whats going on
boypool said:
honeycomb, the latest ota update
it now just goes to CWM recovery and that will just close and turn off randomly... I don't know whats going on
Click to expand...
Click to collapse
Alright since your bootloader is unlocked try this.
Extract boot.img from the ROM
Place it where you have fastboot and adb
Open command prompt or terminal or whatever you have
Boot the flyer in to fastboot mode(If you don't know how ask me)
And type the following:
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
reboot the tablet and tell me if it worked
TheWizardOfROMs said:
Alright since your bootloader is unlocked try this.
Extract boot.img from the ROM
Place it where you have fastboot and adb
Open command prompt or terminal or whatever you have
Boot the flyer in to fastboot mode(If you don't know how ask me)
And type the following:
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
reboot the tablet and tell me if it worked
Click to expand...
Click to collapse
Ive tried that but ill try again, I can barely get it into fastboot because it just goes to cwm whenever I do anything
Tried it, when I hit reboot it just went to CWM recovery.
boypool said:
Ive tried that but ill try again, I can barely get it into fastboot because it just goes to cwm whenever I do anything
Tried it, when I hit reboot it just went to CWM recovery.
Click to expand...
Click to collapse
Try reinstalling the ROM then insert the commands again
TheWizardOfROMs said:
Try reinstalling the ROM then insert the commands again
Click to expand...
Click to collapse
That worked, thank you so much!!!
boypool said:
That worked, thank you so much!!!
Click to expand...
Click to collapse
Don't mention it. Just hit the thanks button if it's not too much trouble and enjoy the ROM
I did the ROM is just a little laggy and touch doesnt always work, its fine though.
Sent from my HTC Flyer P512
HTC Screen
Tried installing several roms but doesnt work i get stuck on the htc screen and now i cant even access the recovery to restore the stock rom. Any advice?
Try reinstalling the recovery and flash the Rom again. Make sure you wipe data and cache twice. Once from recovery and next time with fastboot.
Sent from my HTC Flyer P510e using xda app-developers app

Stuck in Recovery/Bootloader

I have S-off, Unlocked Bootloader, and my EVO is rooted. I have HBOOT 2.09
I tried to install Vanir so I flashed the Gapps 4.4 in TWRP which seemed to work, then I tried to flash Vanir after and got an error.
Now no matter what I do I boot right into recovery and can't seem to figure my way out. Clearly I'm in over my head so if someone could just help me get back to stock at least I would really appreciate it. Thanks
Did you install the proper twrp for kitkat.. if so just try flashing the Rom first then let it boot up and sit for a minute.. then boot back into recovery and flash gapps this works for me..
Sent from my EVO using Tapatalk
It's 2.6.3 twrp, and whenever I tried to install the ROM it gave me an error message.
MrScrufff said:
I have S-off, Unlocked Bootloader, and my EVO is rooted. I have HBOOT 2.09
I tried to install Vanir so I flashed the Gapps 4.4 in TWRP which seemed to work, then I tried to flash Vanir after and got an error.
Now no matter what I do I boot right into recovery and can't seem to figure my way out. Clearly I'm in over my head so if someone could just help me get back to stock at least I would really appreciate it. Thanks
Click to expand...
Click to collapse
Even though you use TWRP 2.6.3.0, it has to be a modded one that allows SELinux support.
Click Me -Flash the Recovery in the OP of this thread
If you have a working fastboot and adb environment on your computer you can flash it by going to to fastboot USB in the bootloader of your phone, and make sure your phone is connected to your PC properly.
Place the .img file in your adb and fastboot folder and then open a command prompt from that location.
then type fastboot flash recovery "recoveryfilename.img" and ofcourse replace recoveryfilename with the actual filename.
after that reboot into recovery and try reflashing Vanir.
This is the method I use to flash recoveries, its fairly simple and fast in my opinion.
Hope this helps.
Link420able said:
Even though you use TWRP 2.6.3.0, it has to be a modded one that allows SELinux support.
Click Me -Flash the Recovery in the OP of this thread
If you have a working fastboot and adb environment on your computer you can flash it by going to to fastboot USB in the bootloader of your phone, and make sure your phone is connected to your PC properly.
Place the .img file in your adb and fastboot folder and then open a command prompt from that location.
then type fastboot flash recovery "recoveryfilename.img" and ofcourse replace recoveryfilename with the actual filename.
after that reboot into recovery and try reflashing Vanir.
This is the method I use to flash recoveries, its fairly simple and fast in my opinion.
Hope this helps.
Click to expand...
Click to collapse
Thanks, I just ran the RUU and went back to stock and everything's good
MrScrufff said:
Thanks, I just ran the RUU and went back to stock and everything's good
Click to expand...
Click to collapse
Ah ok. Glad you got everything sorted out.
Good deal.
Sometimes an RUU is all you have left. A powerful option no doubt.

[Q] HELP can not install TWRP through Fastboot! What am I doing wrong?

OK, so I was rolling along just fine...
Got Fastboot up and running, got myself an unlocked bootloader, got myself the latest TWRP image, and no matter WHAT I DO, I can not get TWRP to flash to my device, and it is driving me absolutely INSANE. Below is what i am getting from command prompt. Any help is GREATLY appreciated.
Code:
C:\Users\saltam\Downloads\TWRP>fastboot flash recovery recovery.img
sending 'recovery' (13186 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I am pulling what little hair I have out over here, and I am no beginner when it comes to this stuff. Please help if you can.
Only a couple of things I can think, which I'm sure you've already done. Have you re-downloaded the image file and you have renamed it recovery.img?
Edit, is your bootloader unlocked?
Sent from my Nexus 5 using XDA Free mobile app
Boot loader is unlocked, tried everything besides a different computer. Tried different cord, different USB port, everything. It's like once I unlocked the boot loader the tablet stopped communicating with fast boot. Anything I try to do hangs until I hit reboot fast boot then it fails. Irritating the hell out of me...
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
blakeslee14 said:
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Click to expand...
Click to collapse
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
craig.buckie said:
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
Click to expand...
Click to collapse
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
SwoRNLeaDejZ said:
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
Click to expand...
Click to collapse
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Going to give this a shot now..
Worth mentioning, I ran an OEM Lock command, and successfully relocked the bootloader, so it appears fastboot is at least partially working. Going to attempt to flash the bootloader in the image from Google, because that is all there is. Just bootloader and image, no recovery image. I will post results here. I don't know why fastboot commands are broken after unlocking bootloader, but there is one thing that seems odd to me:
When I run fastboot devices, it returns the following (has been like this from the beginning):
Code:
C:\Users\saltam\Downloads\TWRP>fastboot devices
???????????? fastboot
Thoughts?
Something's not right. Do you have the newest fastboot?
di11igaf said:
Something's not right. Do you have the newest fastboot?
Click to expand...
Click to collapse
Yes, recently updated it via the minimalist fastboot/adb tool. This is REALLY irritating the hell out of me at this point... Been trying to get recovery on this stupid tablet all damn day...
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
SwoRNLeaDejZ said:
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
Click to expand...
Click to collapse
To your first edit, twrp is probably working correctly. Lollipop forces the stock recovery. There are two files, one in /system and one in /system/bin that force the stock recovery upon boot. You can remove those files or first
fastboot boot twrp.img
Then flash supersu in twrp, then
fastboot flash recovery twrp.img
Sent from my Nexus 9 using XDA Free mobile app
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
xtcdk said:
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
Click to expand...
Click to collapse
Kind of mystified with your response... Had nothing to do with the USB drivers. Found out afterward that the problem was the security that my company had setup on my laptop (was using my company thinkpad). Switching laptops solved the problem.

Categories

Resources