I’m almost ready to make the jump from verygreen’s unofficial emmc CM 10.1 to the official CM 10.2: I have the newest TWRP, backups made, ROM and Gapps downloaded. However, I'm concerned that if I bootloop, I may not be able to get to recover, since I can't seem to find a hard-button set that forces Cyanoboot to either display a menu or boot into recovery.
Am I missing a particular combination of hard-buttons that I just haven't managed to figure out or locate online, or is there an updated bootloader that I need?
Thanks in advance.
Scratch that. Another bunch of trial and error bore out that you can force it into recovery by:
1. Powering off.
2. Holding the power and n buttons until it turns on and turns off.
3 Starting it again.
Nothing to see here, move along...
NanoKnow said:
Scratch that. Another bunch of trial and error bore out that you can force it into recovery by:
1. Powering off.
2. Holding the power and n buttons until it turns on and turns off.
3 Starting it again.
Nothing to see here, move along...
Click to expand...
Click to collapse
Don't hold the power button so long that it turns off. Hold the power and n for only about 5 seconds and release the power. It should boot to recovery.
Sent from my Galaxy Tab 2 using XDA Premium
Related
Absolute NooB to the NC here, so please be gentle!
I've got four issues that should be no-brainers but they are beating me up. I've split them into four separate posts to keep things clean.
1. Booting to recovery
What I've read is to power the NC off, power on, hold down power & N key until boot screen (which I assume is the "Touch the future of reading" screen), then release both to boot into recovery mode.
Certainly sounds simple.
I can't make it work. Been trying for days.
So, does this actually work? What is the trick?
Timing on that can be tricky, so don't get frustrated. When the 'touch the future' logo comes up, continue holding N and power and count to about 4. Hopefully that gets you, but if not, try 3 and 5 counts. If it powers back off, you held too long, but it won't hurt anything!
I have the same darn problem with mine---but I never see "touch of the future" script, I see " loading". I always see "loading".
CM7 on the sd card.
I have never booted into recovery.
?
I usually reboot to recovery from rom manager.
Thanks! Got it down now. Once I got the timing down, tis as easy as on my original Droid.
john10101 said:
I usually reboot to recovery from rom manager.
Click to expand...
Click to collapse
That's my preferred method (on my original Droid) but it doesn't work for me on the Nook.
Maybe because I am still booting CM7 from the sdcard?
I'm on the same boat here cant figure out how to get into recovery mode.
I tried the power/N button combinations, reboot into recovery from CM7 desktop, and ROM manager still doesn't get me into recovery mode.
atrociousNK said:
I'm on the same boat here cant figure out how to get into recovery mode.
I tried the power/N button combinations, reboot into recovery from CM7 desktop, and ROM manager still doesn't get me into recovery mode.
Click to expand...
Click to collapse
Problem fixed, stopped using stable build 7.03 and used nightly build 102 and now I could get in and out of recovery mode with no issues.
Hi um I'm pretty new to Android phones, and my Captivate's stuck in a bootloop...
I had CyanogenMod 9 on it, based on ICS 4.0.4, which i still have the .zip for if necessary. But I think I did something stupid... in the recovery (which said something about CWMrecovery) mode, I absent-mindedly formatted the /system directory... derp....
Now basically the phone shows the AT&T logo, then shows some kind of recovery screen, it only flashes up for a short time but I can see in the background both an android, like stock recovery mode, and the logo from ROM manager (or something very similar). There is some text at the bottom but it's very small and only flashes up for a split second so I can't read it... and what's worse, it won't boot into recovery...
I'm not exactly sure how to even do it, but random combinations of the volume & power buttons and home.. screen-area-thing work eventually.. but it's just not working now, as i hold the buttons it either just keeps rebooting before it gets past the AT&T logo or ignoring it completely, showing the recovery screen then rebooting again anyway
Sorry it's kinda long.. I tried to be detailed XD
tl;dr CM9 rom Captivate, formatted /system, stuck in bootloop, recovery mode won't work
Any help would be much appreciated
Edit: Forgot to say, I've searched around already but I haven't found anyone else who's bootloop is caused by formatting /system -.-
re flash the rom. you erased the rom.
dont wipe dont format just flash the rom again. you should be back as if it never happened.
If your in a boot loop you might want to invest in a jig, only $6 on eBay
You also said recovery doesn't work? Have you tried putting it into download mode?
Sent from my SGH-I897 using Tapatalk 2
This might help you:
http://forum.cyanogenmod.com/topic/39685-stuck-on-boot-loop/
If not google Samsung captivate boot loop. Lots of info on how to fix out there. Sorry I don't work on many Samsung phones. Primarily HTC.
Sent from my Inspire 4G using XDA
jig will not help bootloop.
you are freaking out because of the bootloop and not holding the button combo for recovery long enough.
take out the battery. and replace
hold both volume buttons
then hold power
keep buttons held for 5 seconds AFTER screen comes on.
if your phone turns on and starts to boot, you have recovery and download.
TRusselo said:
jig will not help boot loop
Click to expand...
Click to collapse
You sure? Fixed my phone from boot loop!
Sent from my SGH-I897 using Tapatalk 2
TRusselo said:
jig will not help bootloop.
you are freaking out because of the bootloop and not holding the button combo for recovery long enough.
take out the battery. and replace
hold both volume buttons
then hold power
keep buttons held for 5 seconds AFTER screen comes on.
if your phone turns on and starts to boot, you have recovery and download.
Click to expand...
Click to collapse
Tried that, isn't working :\ it just ignores it, shows the recovery screen realy quick then reboots again...
I've had this happen on my captivate...only option is to flash back to a stock ROM and work your way back up to CM9 or whatever you were trying to flash originally. To do this your gonna have to get into download mode. A jiff is your best friend in this situation as suggested by several others. however if the button combo for download mode works for you, that is best. Try unplugging the battery, wait for like 10 seconds and plug back in. Have a PC running, and make sure you have the drivers installed. have the USB cable plugged into your computer, and while holding both the volume buttons down, plug the cable into your phone as well. This should put you into download mode and your good to go.
Sent from my SGH-I897 using XDA
thanks cmilldrummin (and everyone else)
I got my phone into download mode fine... but i don't think I have the drivers :s (googling still, but can't find them so far)
Also I got it into recovery mode earlier, re-flashed the same custom ROM but when I tried to load it it just kept loading with the blue android on a skateboard until the battery ran out (It was the same one, CM9)
Is the like actual android system openable in download mode? so I could re-write the /system folder? if not I guess I'll just try to re-flash a stock rom then upgrade.. *crosses fingers*
Best way is to flash back to stock and start fresh.
Sent from my Serendipity VII flashed Captivate using xda premium
Np Dolei, but yea back to stock is best, gives you a nice clean slate, with no glitches or errors
Sent from my SGH-I897 using XDA
TRusselo is right. The other posts here are taking the sledgehammer approach for a simple fix. If you cannot get into recovery mode - you're doing it wrong, try again. reflash your rom from recovery and all done.
Dolei said:
Hi um I'm pretty new to Android phones, and my Captivate's stuck in a bootloop...
I had CyanogenMod 9 on it, based on ICS 4.0.4, which i still have the .zip for if necessary. But I think I did something stupid... in the recovery (which said something about CWMrecovery) mode, I absent-mindedly formatted the /system directory... derp....
Now basically the phone shows the AT&T logo, then shows some kind of recovery screen, it only flashes up for a short time but I can see in the background both an android, like stock recovery mode, and the logo from ROM manager (or something very similar). There is some text at the bottom but it's very small and only flashes up for a split second so I can't read it... and what's worse, it won't boot into recovery...
I'm not exactly sure how to even do it, but random combinations of the volume & power buttons and home.. screen-area-thing work eventually.. but it's just not working now, as i hold the buttons it either just keeps rebooting before it gets past the AT&T logo or ignoring it completely, showing the recovery screen then rebooting again anyway
Sorry it's kinda long.. I tried to be detailed XD
tl;dr CM9 rom Captivate, formatted /system, stuck in bootloop, recovery mode won't work
Any help would be much appreciated
Edit: Forgot to say, I've searched around already but I haven't found anyone else who's bootloop is caused by formatting /system -.-
Click to expand...
Click to collapse
TRusselo said:
re flash the rom. you erased the rom.
dont wipe dont format just flash the rom again. you should be back as if it never happened.
Click to expand...
Click to collapse
TRusselo said:
jig will not help bootloop.
you are freaking out because of the bootloop and not holding the button combo for recovery long enough.
take out the battery. and replace
hold both volume buttons
then hold power
keep buttons held for 5 seconds AFTER screen comes on.
if your phone turns on and starts to boot, you have recovery and download.
Click to expand...
Click to collapse
Try doing this, this has worked for me since I can't get into recovery with the traditional button combo method of holding all three buttons at the same time.
Turn the phone off. Hold the power button, vol up, vol down. Once the ATT boot screen comes on, let go of the power button. Keep holding the volume buttons and voila, you're in recovery.
Agree. Definitely go back to stock if possible first.
Sent from my Inspire 4G using XDA
Hopefully you all don't sigh or roll your eyes at my questions, I came from iOS 2 weeks ago and the Android learning curve is pretty damn steep!
Many guides I read says to enter recovery mode by turning the phone off, then holding volume down and power buttons until the screen flashes and you should enter right into recovery, especially guides to flash a rom. I installed TWRP last week and the way I enter it is hit restart with phone powered on and as the phone begins to restart hold volume down only, then I enter it.
When I hold power and volume down when the phone is shut off, I get the HTC boot image as the phone is rebooting and then a message saying something along the lines of the phone will reboot and it counts down 3,2,1 then the phone reboots a second time and not into recovery. Plus my wallpaper gets removed. I rebooted but the wallpaper was still removed.
Two questions; Is this some sort of faulty installation of my recovery? Which way should I boot into recovery when about to wipe and flash a rom? Thanks a million!
twrp quicker reboot...
AcerRacer said:
Hopefully you all don't sigh or roll your eyes at my questions, I came from iOS 2 weeks ago and the Android learning curve is pretty damn steep!
Many guides I read says to enter recovery mode by turning the phone off, then holding volume down and power buttons until the screen flashes and you should enter right into recovery, especially guides to flash a rom. I installed TWRP last week and the way I enter it is hit restart with phone powered on and as the phone begins to restart hold volume down only, then I enter it.
When I hold power and volume down when the phone is shut off, I get the HTC boot image as the phone is rebooting and then a message saying something along the lines of the phone will reboot and it counts down 3,2,1 then the phone reboots a second time and not into recovery. Plus my wallpaper gets removed. I rebooted but the wallpaper was still removed.
Two questions; Is this some sort of faulty installation of my recovery? Which way should I boot into recovery when about to wipe and flash a rom? Thanks a million!
Click to expand...
Click to collapse
way i do it is i unlock the screen hold power down to get the power options screen then i select reboot i wait for the screen to go blank then i hold the power and volume down it will load into bootloader then i just hit whatever boot loader has the recovery on it (twrp 2.5... had a problem wouldnt do system boot just take me back to recovery so i had to do to bootloader then restart from there) then you will hit recovery i would do a factory wipe but dont have it delete anything else just do a normal factory wipe and maybe delete cache and your problem should be fixed unless there is an issue with your rom you are using then if it bugs you that much find a different one.
another not when the system reboots i think you can just hit volume down dont have to hold power also but im so aggrivated with my current issue i just hold power also to make sure it goes thew.
AcerRacer said:
Hopefully you all don't sigh or roll your eyes at my questions, I came from iOS 2 weeks ago and the Android learning curve is pretty damn steep!
Many guides I read says to enter recovery mode by turning the phone off, then holding volume down and power buttons until the screen flashes and you should enter right into recovery, especially guides to flash a rom. I installed TWRP last week and the way I enter it is hit restart with phone powered on and as the phone begins to restart hold volume down only, then I enter it.
When I hold power and volume down when the phone is shut off, I get the HTC boot image as the phone is rebooting and then a message saying something along the lines of the phone will reboot and it counts down 3,2,1 then the phone reboots a second time and not into recovery. Plus my wallpaper gets removed. I rebooted but the wallpaper was still removed.
Two questions; Is this some sort of faulty installation of my recovery? Which way should I boot into recovery when about to wipe and flash a rom? Thanks a million!
Click to expand...
Click to collapse
*Update*
Ok so after trying again to enter bootloader from power off holding volume down and power button, the same thing happened where I got the 3 second countdown but I continued to hold the buttons and I correctly entered into bootloader. So my question then stands, when flashing a new rom does it matter which method I use? (Reboot, volume down or Power on, volume down/power)
Thanks
Sent from my HTC One using xda app-developers app
Wiped data cache AND dalvik, flashed to Malladus, installed GApps and LGApps at the same time. Been sitting at the android animation for at least 45 minutes all three times and still wont boot. I'm downloading stock image but was hoping someone had an experience similar and had an easy solution?
briangp said:
Wiped data cache AND dalvik, flashed to Malladus, installed GApps and LGApps at the same time. Been sitting at the android animation for at least 45 minutes all three times and still wont boot. I'm downloading stock image but was hoping someone had an experience similar and had an easy solution?
Click to expand...
Click to collapse
And now I offically think my phone is screwed. I cant boot into recovery, every time I try it wont enter and just reboots because I'm holding the power and volume down buttons. So far I don't think I can enter download mode either.
briangp said:
And now I offically think my phone is screwed. I cant boot into recovery, every time I try it wont enter and just reboots because I'm holding the power and volume down buttons. So far I don't think I can enter download mode either.
Click to expand...
Click to collapse
How to get into TWRP with hardware keys on G2
1. Make sure phone is completely powered down.
2. Press and hold the Volume down button and the Power button.
3. When the LG logo is displayed release the Power button only then immediately press and hold the Power button again.
4. Release both buttons when the Factory Hard Reset screen displays.
5. Press the power button three times, like it says. Even though it says it will delete everything, it won't (I can confirm that if you are at least on v2.6.3.2).
6. After a "factory reset processing" appears, you should get the TWRP flash screen, and you are good to go.
From this thread: http://forum.xda-developers.com/showthread.php?t=2534981
acejavelin said:
How to get into TWRP with hardware keys on G2
1. Make sure phone is completely powered down.
2. Press and hold the Volume down button and the Power button.
3. When the LG logo is displayed release the Power button only then immediately press and hold the Power button again.
4. Release both buttons when the Factory Hard Reset screen displays.
5. Press the power button three times, like it says. Even though it says it will delete everything, it won't (I can confirm that if you are at least on v2.6.3.2).
6. After a "factory reset processing" appears, you should get the TWRP flash screen, and you are good to go.
From this thread: http://forum.xda-developers.com/showthread.php?t=2534981
Click to expand...
Click to collapse
Thanks for replying. I've read how to get into the recovery menu many times. Something is wrong with my phone that prevents me from doing it. I'm assuming its hardware related. I was almost ready to give up yesterday when I found out that if I do the key combo while plugging it into USB, it enters the menu normally. At that point I was able to restore my backup and start again.
I think my phone has a fluke, but I've figured out a way around it.
For those who are using Malladus on Verizon, something was wrong with the radios in the set. I had to find a seperate KK baseband file for the VS980 and flash it over top of the ROM to get it to work. I'm not saying its the same results for everyone, but I tried every variant of his directions (just in case) and was unable to get LTE online. It was the seperate BB file later on that fixed it.
Hey guys,
So I'm having issues trying to fix my Samsung Tab A 10.1 ( SM-T510 ).
At first I was trying to install a custom TWRP recovery image, and I had a boot loop where it kept getting stuck at the SAMSUNG splash screen(not the initial samsung boot screen that shows TAB A 10.1). I however overcame that issue by factory reseting and through some additional tinkering.
Now the part I'm starting to regret.
I tried once again to flash the custom TWRP to the tablet, but this time I forgot to tick the "autoreboot" setting off.
So ODIN shows a PASS for the flash, but now when the tablet boots its stuck in the following boot sequence:
START:
Initial Samsung boot screen asking to press power button to continue due to unknown boot image source etc
PRESS POWER
SAME INITIAL SAMSUNG BOOT SCREEN minus the power button prompt, lasts for about 3-5 seconds
REBOOT
Now I have managed to get into download mode with the tablet connected to a computer.
I CANNOT get into recovery mode to factory reset the tablet, which was the solution the last go around.
I am starting to think that the only way I am going to get the tablet back in original working order, or any working order for that matter is to:
A: LOCATE original firmware for my device, I believe it is GTAXLWIFI firmware for my device. However the files I have found don't seem to be accepted in ODIN...
B: Try to continue on with the TWRP process, which I have tried to reflash the TWRP recovery that I have, and it shows pass. But, the issue persists.
Any suggestions or help would be amazing!
Thanks!
Timing is the key
Set your finger on position where you gonna restart the device.
Hold power + vol down
After the screen restart switch soon as possible you finger to set to recovery by
Hold vol up + down + insert the USB C cable
Remember timing is the key. I have done this for several tabs that screw on my home so you are welcome bro
frontchasack said:
Hey guys,
So I'm having issues trying to fix my Samsung Tab A 10.1 ( SM-T510 ).
At first I was trying to install a custom TWRP recovery image, and I had a boot loop where it kept getting stuck at the SAMSUNG splash screen(not the initial samsung boot screen that shows TAB A 10.1). I however overcame that issue by factory reseting and through some additional tinkering.
Now the part I'm starting to regret.
I tried once again to flash the custom TWRP to the tablet, but this time I forgot to tick the "autoreboot" setting off.
So ODIN shows a PASS for the flash, but now when the tablet boots its stuck in the following boot sequence:
START:
Initial Samsung boot screen asking to press power button to continue due to unknown boot image source etc
PRESS POWER
SAME INITIAL SAMSUNG BOOT SCREEN minus the power button prompt, lasts for about 3-5 seconds
REBOOT
Now I have managed to get into download mode with the tablet connected to a computer.
I CANNOT get into recovery mode to factory reset the tablet, which was the solution the last go around.
I am starting to think that the only way I am going to get the tablet back in original working order, or any working order for that matter is to:
A: LOCATE original firmware for my device, I believe it is GTAXLWIFI firmware for my device. However the files I have found don't seem to be accepted in ODIN...
B: Try to continue on with the TWRP process, which I have tried to reflash the TWRP recovery that I have, and it shows pass. But, the issue persists.
Any suggestions or help would be amazing!
Thanks!
Click to expand...
Click to collapse
Original firmware I used to fix my sm-t510
Account Suspended
flavarasa said:
Timing is the key
Set your finger on position where you gonna restart the device.
Hold power + vol down
After the screen restart switch soon as possible you finger to set to recovery by
Hold vol up + down + insert the USB C cable
Remember timing is the key. I have done this for several tabs that screw on my home so you are welcome bro
Click to expand...
Click to collapse
I think "restarts" may be confusing. Switch from down to up as soon as the screen turns off.
frontchasack said:
Hey guys,
So I'm having issues trying to fix my Samsung Tab A 10.1 ( SM-T510 ).
At first I was trying to install a custom TWRP recovery image, and I had a boot loop where it kept getting stuck at the SAMSUNG splash screen(not the initial samsung boot screen that shows TAB A 10.1). I however overcame that issue by factory reseting and through some additional tinkering.
Now the part I'm starting to regret.
I tried once again to flash the custom TWRP to the tablet, but this time I forgot to tick the "autoreboot" setting off.
So ODIN shows a PASS for the flash, but now when the tablet boots its stuck in the following boot sequence:
START:
Initial Samsung boot screen asking to press power button to continue due to unknown boot image source etc
PRESS POWER
SAME INITIAL SAMSUNG BOOT SCREEN minus the power button prompt, lasts for about 3-5 seconds
REBOOT
Now I have managed to get into download mode with the tablet connected to a computer.
I CANNOT get into recovery mode to factory reset the tablet, which was the solution the last go around.
I am starting to think that the only way I am going to get the tablet back in original working order, or any working order for that matter is to:
A: LOCATE original firmware for my device, I believe it is GTAXLWIFI firmware for my device. However the files I have found don't seem to be accepted in ODIN...
B: Try to continue on with the TWRP process, which I have tried to reflash the TWRP recovery that I have, and it shows pass. But, the issue persists.
Any suggestions or help would be amazing!
Thanks!
Click to expand...
Click to collapse
You can use frija.exe to get the latest stock firmware. To get TWRP you MUST boot to recovery before system. If you allow the tablet to boot to system first, it will overwrite TWRP with the stock recovery. Do this by pressing vol down and power till the screen turns off. As soon as it does, switch from vol down to up while still pressing power and keep holding both till the red warning message appears. You also need to leave the cable attached to the PC while doing this.