My computer is down and TWRP seems stuck in recovery mode? possibly. Every time I try to flash a ROM TWRP just reboots itself. I'm able to backup and restore fine but cannot flash. I'm running dualboot bootloader if that matters.
Is there a way to check what mode it is in via terminal and also change it?
Any help would be greatly appreciated.
http://m.youtube.com/#/watch?desktop_uri=/watch?v=2u5Dav9beuk&v=2u5Dav9beuk&gl=US
Sent from my Amazon Kindle Fire using XDA
freefaling said:
http://m.youtube.com/#/watch?desktop_uri=/watch?v=2u5Dav9beuk&v=2u5Dav9beuk&gl=US
Sent from my Amazon Kindle Fire using XDA
Click to expand...
Click to collapse
I know how to flash via terminal. I need to know of you can change boot mode via terminal. I already tried flashing the recovery over top of it but I still cannot flash a new ROM. (The tablet boots up fine, fyi)
Sent from my Nexus One using xda premium
uoY_redruM said:
I know how to flash via terminal. I need to know of you can change boot mode via terminal. I already tried flashing the recovery over top of it but I still cannot flash a new ROM. (The tablet boots up fine, fyi)
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
If you can flash twrp 2.1.1, then you can boot into your rom from twrp. It used to have a bug where it would not change bootmode. I believe it is now fixed with v2.1.1.
Hope it helps.
Sent from my Amazon Kindle Fire using XDA
freefaling said:
If you can flash twrp 2.1.1, then you can boot into your rom from twrp. It used to have a bug where it would not change bootmode. I believe it is now fixed with v2.1.1.
Hope it helps.
Sent from my Amazon Kindle Fire using XDA
Click to expand...
Click to collapse
I flashed 2.1.1 with success but still was unable to flash a ROM. To top it off, I clicked the "reset boot loader" option and now my Kindle is stuck on the dual-boot boot loader screen and will not respond or go further....
Sent from my Nexus One using xda premium
uoY_redruM said:
I flashed 2.1.1 with success but still was unable to flash a ROM. To top it off, I clicked the "reset boot loader" option and now my Kindle is stuck on the dual-boot boot loader screen and will not respond or go further....
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=943772&d=1331571368
Someone (user:b63) over at the firefirefire thread posted this handy file explaining how to change bootmodes via command line. Try it.
Sent from my Amazon Kindle Fire using XDA
freefaling said:
http://forum.xda-developers.com/attachment.php?attachmentid=943772&d=1331571368
Someone (user:b63) over at the firefirefire thread posted this handy file explaining how to change bootmodes via command line. Try it.
Sent from my Amazon Kindle Fire using XDA
Click to expand...
Click to collapse
Would love to but now I'm stuck and cannot even boot.
Sent from my Nexus One using xda premium
uoY_redruM said:
Would love to but now I'm stuck and cannot even boot.
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
your in fastboot. who reboots to bootloader not knowing what it does?
u need a PC now for sure.
why it won't flash, is beyond me tho.
Sent from my HTC Glacier using xda premium
smirkis said:
your in fastboot. who reboots to bootloader not knowing what it does?
u need a PC now for sure.
why it won't flash, is beyond me tho.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Yeah it was a stupid move, I was just getting frustrated with it not flashing ROMs all of a sudden and I just started trying random ****. Waiting for my friend and his laptop now.
Sent from my Nexus One using xda premium
Maybe this can help?
http://forum.xda-developers.com/showpost.php?p=22619437&postcount=5
Type this in terminal emulator:
Su
Oem idme bootmode 4000
FINALLY! Damn, his laptop was being defiant and didn't want to install the fastboot drivers. Was starting to piss me off, but an hour later and I got it going!
I had to run
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
I haven't tried to flash a new ROM yet, I don't even care at this point, happy the Kindle is back up. Now time to try and get ROMs to flash...
OK so I reset my partition to stock, flashed the latest FFF (replacing the dual-boot bootloader) and flashed the latest TWRP 2.1.1 and it still failed to flash ANY ROM. I reverted to TWRP 2.0 again and tried and it didn't fail...yet. It started the flashing process but I'm not sure it'll complete (been flashing for about 5 minutes now and has not completed). Really not sure what the deal is with flash failing. This never happened before.
EDIT-
Nope, goes...
Formatting /cache...
Formatting /cache...
Formatting /cache...
E:Unable to open zip file.
Related
So I was an idiot and tried to install ICS on here. I flashed it through TWRP and did a full wipe of it and NOW it just boots in to recovery and that is it. Does anyone know of a fix or what went wrong with it? I tried restoring my backup and it didn't do anything to fix it.
htcdesirezgeorge said:
So I was an idiot and tried to install ICS on here. I flashed it through TWRP and did a full wipe of it and NOW it just boots in to recovery and that is it. Does anyone know of a fix or what went wrong with it? I tried restoring my backup and it didn't do anything to fix it.
Click to expand...
Click to collapse
adb shell
idme bootmode 4000
reboot
lolz, im a idiot arent I? I read that over 4x before realizing that I've read that before lol!
vanduhl said:
adb shell
idme bootmode 4000
reboot
Click to expand...
Click to collapse
Anyone know who maintains TWRP for KF? There's no reason it shouldn't be doing this when you tap reboot.
pokey9000 said:
Anyone know who maintains TWRP for KF? There's no reason it shouldn't be doing this when you tap reboot.
Click to expand...
Click to collapse
I think it happens when in CM7 you select reboot into recovery. I don't believe it's a TWRP specific thing
vanduhl said:
I think it happens when in CM7 you select reboot into recovery. I don't believe it's a TWRP specific thing
Click to expand...
Click to collapse
Well, yeah. TWRP doesn't do anything with the bootmode, which is misleading behavior when you click "reboot". CWM does this on other platforms where the boot selection isn't a one-shot.
I told agrabren the day he released it in twitter, surprised it never got fixed
Sent from my HTC Glacier using xda premium
smirkis said:
I told agrabren the day he released it in twitter, surprised it never got fixed
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
He is not in teamwin or working on twrp anymore ... he is working on cm9 for epic touch ...
Sent from my SPH-D710 using xda premium
Everyone using CM7 on their kindle should just go into settings->interface->power prompt and uncheck it. This disables the selection menu when you pick reboot (so you can't accidentally choose "reboot into recovery").
Then just go into recovery the manual way from firefirefire with your power switch.
I just want to know which recovery should I install...I'm new to the pad game and I just wanted some input...I just rooted my N7 and ready to install a recovery...I'm used to CWR on my sgIII...but I see that TWRP is the new recovery that some guys are installing...also is there problem with boring into recovery from the device? Thanks in advanced...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I prefer cwm touch which you can get from the site. Or you can flash the button version from rommanager
Twrp does work tho, but I've read issues with restoring backups.
Booting into recovery on the device in a way is messed up. The button combo method to enter using the bootloader hangs when not connected to a PC, so there are two options on getting into recovery.
A. Connect to a PC and use bootloader
B. With a working OS, reboot to recovery using an app such as rommanager or goomanager
If you ever flash a rom that won't boot, u need to connect to a PC and boot into recovery via bootloader (button combo).
Sent from my Nexus 7 using xda premium
I use TWRP and had successfully restored now a couple of times. Once was a complete device replacement where I restored the TWRP restore files from my workstation.
How I do my backups to ensure I can restore from a total loss.
http://forum.xda-developers.com/showthread.php?p=29550640
Sent from my Nexus 7
smirkis said:
Booting into recovery on the device in a way is messed up. The button combo method to enter using the bootloader hangs when not connected to a PC, so there are two options on getting into recovery.
A. Connect to a PC and use bootloader
B. With a working OS, reboot to recovery using an app such as rommanager or goomanager
If you ever flash a rom that won't boot, u need to connect to a PC and boot into recovery via bootloader (button combo).
Click to expand...
Click to collapse
Ah, I was curious if this bug still existed or not.
I'd go with CWM, quite stable, easy to use, and you can flash the touch recovery, speeds it up.
Sent from my Nexus 7 using xda app-developers app
Thanks, I read somewhere that if you go into system/ and rename recovery-from-boot.p to recovery-from-boot.bak, fixes the bootloop...can anyone confirm this... thank in advance
Sent from my Nexus 7 using xda app-developers app
Try it. Bootloader issue still exists regardless.
Sent from my Nexus 7 using xda premium
I'm a TWRP guy all the way. I have never had an issue restoring a backup, and the ability to compress my nandroid is invaluable.
Sent from my Nexus 7 using Tapatalk 2
TWRP has definitely converted me.
Sent from my SAMSUNG-SGH-I747 using xda premium
05GT said:
TWRP has definitely converted me.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
+1
Ok so heres the story. Ubuntu released a version of it self for the N7 and I went to try it out. Works ok kinda sluggish, but I digress.
Went back to stock and it went smooth as butter. Now I went to flash CWM and it flashed like it was supposed to. Now for some reason my tablet only boots into recovery no matter what. I tried to press power and vol down to get into the bootloader and it just boots recovery.
I used Nexus Root Toolkit v1.5.4 to flash the image.
It's stuck in cwm?
Can you reach it via adb?
If so enter "adb reboot fastboot"
Sent from my Nexus 7 using xda app-developers app
mvmacd said:
It's stuck in cwm?
Can you reach it via adb?
If so enter "adb reboot fastboot"
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Tried that and ADB said there was no device attached. So, I reinstalled my drivers and that worked. Managed to get into fast boot and reflashed stock. I manually flashed cwm and that worked no problem. I'm now back on my own version of cm10.
Sent from my SCH-I535 using xda premium
I have a Nexus 7 wifi, It is stuck at the Google screen boot looping. It is unlocked and has TWRP 2.5 which I can access. I have tried every tool kit to no avail. Need some help please!
dont use a toolkit
get to a command line and figure out whats wrong by trying to flash a factory image, or run factory reset in recovery and see if it fixes it.
Pirateghost said:
dont use a toolkit
get to a command line and figure out whats wrong by trying to flash a factory image, or run factory reset in recovery and see if it fixes it.
Click to expand...
Click to collapse
I tried factory reset but it fails. I tried to flash a factory image through side load but it fails.
If I go to advanced wipe and do them one at a time they all work except data.
It appears to have nothing on intrenal or external storage.
One other thing is when I try to mount the system in twrp it asks for a password?
I have never setup a password so I don't understand this.
Thanks
Did you encrypt your device?
Sent from my Galaxy Nexus
No, not at all that's what's so strange.
I purchased it new and it started locking up and after an attempted factory reset here we are.
Sent from my SCH-I605 using xda app-developers app
Factory reset would wipe data partition leaving nothing in data. Makes sense that it wouldnt let you wipe that when there is nothing there.
Try flashing a factory image from fast boot. Not from recovery.
Sent from my Galaxy Nexus
Would it not have to be loaded on the device? I tried it with a tool kit and it gets to the end and fails on verification.
I don't remember what version it was so that doesn't help. I think it was 4.1.2
But not positive.
Sent from my SCH-I605 using xda app-developers app
Pirateghost said:
Factory reset would wipe data partition leaving nothing in data. Makes sense that it wouldnt let you wipe that when there is nothing there.
Try flashing a factory image from fast boot. Not from recovery.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Okay seems to be a problem with twrp 2.5 as far as the password I'm downloading 2.6 now.
Use fastboot to flash new recovery and system partition. You run fastboot commands from your computer not from recovery and your device needs to be in bootloader not recovery. It does not require you to load it onto the device prior
Sent from my Galaxy Nexus
Pirateghost said:
Use fastboot to flash new recovery and system partition. You run fastboot commands from your computer not from recovery and your device needs to be in bootloader not recovery. It does not require you to load it onto the device prior
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
After reading more I decided to go with CWM for the recovery. I flashed it in fast boot and it works fine but what now?
Thanks for your time!
ugadawg67 said:
After reading more I decided to go with CWM for the recovery. I flashed it in fast boot and it works fine but what now?
Thanks for your time!
Click to expand...
Click to collapse
personally i would flash a stock system image in fastboot, root it, and use it....or pick from the hundreds of ROMs available around here.
Pirateghost said:
personally i would flash a stock system image in fastboot, root it, and use it....or pick from the hundreds of ROMs available around here.
Click to expand...
Click to collapse
What would I use to flash the stock image in fast boot? a toolkit? I have the stock img downloaded already.
ugadawg67 said:
What would I use to flash the stock image in fast boot? a toolkit? I have the stock img downloaded already.
Click to expand...
Click to collapse
you dont need a toolkit
you use fastboot command to flash.....
Pirateghost said:
you dont need a toolkit
you use fastboot command to flash.....
Click to expand...
Click to collapse
Sorry I need a little more help with that. Are you talking about from a command prompt?
Sent from my SCH-I605 using xda app-developers app
you need to do some reading
http://forum.xda-developers.com/showthread.php?t=1907796
Pirateghost said:
you need to do some reading
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
thanks!
okay I removed my sdk folder and started over. I followed the instructions on the link and it says failed cannot load bootloader. It performs all commands until that one.
Any ideas what I'm doing wrong?
Sent from my Galaxy Note 2 using xda app-developers app
Pirateghost said:
you need to do some reading
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
okay I removed my sdk folder and started over. I followed the instructions on the link and it says failed cannot load bootloader. It performs all commands until that one.
Any ideas what I'm doing wrong?
Sent from my SCH-I605 using xda app-developers app
Hey guys, I seem to have a problem with my Nexus 4
I installed Odyssey ROM (4.3) coming from Illusion (4.2.2) following the usual procedure of wiping etc...
It didn't boot, stuck on the Google logo....
Strange thing is that it stuck when I tried to reinstall Illusion and also when I restored the Backup I made before the install.
What couldve cause this problem and how can I solve it?
Thanks
I don't know the cause but try this:
1.Go to bootloader.
2.Use adb fastboot to flash to stock.
3.profit
Sent from my Nexus 4 using xda app-developers app
wargasm009 said:
Hey guys, I seem to have a problem with my Nexus 4
I installed Odyssey ROM (4.3) coming from Illusion (4.2.2) following the usual procedure of wiping etc...
It didn't boot, stuck on the Google logo....
Strange thing is that it stuck when I tried to reinstall Illusion and also when I restored the Backup I made before the install.
What couldve cause this problem and how can I solve it?
Thanks
Click to expand...
Click to collapse
Go into recovery:
- Wipe cache and dalvik cache and reboot or
- if that`s not enough do a data factory reset and reboot. That should do it.
gee2012 said:
Go into recovery:
- Wipe cache and dalvik cache and reboot or
- if that`s not enough do a data factory reset and reboot. That should do it.
Click to expand...
Click to collapse
This, plus reflash ROM.
Sent from my Nexus 4 using Tapatalk 4
OK guys.... Slight update... I get it to work but it seems to only boot ROMs after a factory reset..... Even now, Odyssey, PA etc no matter what ROMs I'm on if I reboot it hangs at the Google logo.... Forcing me into another factory reset.
Sent from my Nexus 4 using xda app-developers app
wargasm009 said:
OK guys.... Slight update... I get it to work but it seems to only boot ROMs after a factory reset..... Even now, Odyssey, PA etc no matter what ROMs I'm on if I reboot it hangs at the Google logo.... Forcing me into another factory reset.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Flash the factory image, so completly stock. Then you can go ahead and start running custom roms again!:highfive:
failly said:
Flash the factory image, so completly stock. Then you can go ahead and start running custom roms again!:highfive:
Click to expand...
Click to collapse
Than you... That's probably my best bet right now.
Sent from my GT-N8013 using xda app-developers app
wargasm009 said:
Than you... That's probably my best bet right now.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
Good luck! Let us know if you got it fixed!
failly said:
Good luck! Let us know if you got it fixed!
Click to expand...
Click to collapse
Will do bro
Sent from my GT-N8013 using xda app-developers app
I'm having this same problem with a friend's Nexus 4, my Nexus 4 I can flash whatever and it boots up no problem. With his it doesn't matter what ROM I flash it will not boot up. I have done the full wipe and installed factory image from Google Dev website at least 5 times and then installed customer recovery and root several times. I'm using the latest CWM touch and it will not boot. Any ideas? Thanks.
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
Now boot to new recovery
adb sideload nameofrom.zip
adb sideload gapps.zip
Reboot
May is suggest the latest twrp recovery and latest slimkat and their all in one gapps for this as well
Also be sure you have the latest bootloader and modem
Best of luck
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
Now boot to new recovery
adb sideload nameofrom.zip
adb sideload gapps.zip
Reboot
May is suggest the latest twrp recovery and latest slimkat and their all in one gapps for this as well
Also be sure you have the latest bootloader and modem
Best of luck
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did all of this except the adb sideloading, I just flashed the ROM and Gapps in CWM, I'll try it like this, thanks.