Hello,
Yesterday there was an update for the Moto G, I confirmed to do the update. Since then the phone is in a reboot loop. I mean it doesn't matter what ever I do,the phone restart itself in every 2-3 minutes. The phone is rooted.
I've tried to do a factory reset from the setting,however nothing happens when I want to erase the settings. In the bootloader if I chose Recovery or Factory reset,the phone reboots.
I've got a tip that I should remove the update file from the /chace directory,however I don't know how to do so,as the phone keeps reboot itself.
The only place,where the phone is not restarts is in the bootloader.
Is there any way to somehow solve this problem without flash a stock rom ?
Thanks for your help!
Regards,
Péter
The same here. Help!
Tussky said:
Hello,
I've tried to do a factory reset from the setting,however nothing happens when I want to erase the settings. In the bootloader if I chose Recovery or Factory reset,the phone reboots.
Click to expand...
Click to collapse
You have to press volume up instead of power to choose something in fastboot menu.
Unroot and if used custom recovery go back to stock recovery.
mokkami said:
Unroot and stock recovery.
Click to expand...
Click to collapse
How should I do the unroot ? I find this solution,but I can't post the link,as I didn't have 10+ posts... its in the site unlockr and there's an article about moto g unroot.
However I can't enable the usb debug,as the phone restart faster,than I'am able to do this.
Yes I know I have to press volume up,however if I chose recovery it's reboot itself,so I'am not able to select Recovery from the bootloader.
Tussky said:
How should I do the unroot ? I find this solution,but I can't post the link,as I didn't have 10+ posts... its in the site unlockr and there's an article about moto g unroot.
However I can't enable the usb debug,as the phone restart faster,than I'am able to do this.
Click to expand...
Click to collapse
My is rooted and cwm 6.0.4.6
May be we must do something with fastboot command
my GF's Moto G did the same thing, luckily it was a simple fix.
I had already rooted her stock 4.4.2 and installed CWM Recovery 6.0.4.6.
If you havent installed, CWM or TWRP, then I recommend to do so by fastboot command and the recovery.img.
Here is the forum link to install CWM Recovery for your Moto G:
http://forum.xda-developers.com/showthread.php?t=2563599
So I just Powered Off the phone. Then go back into the CWM Recovery by:
- hold down Volume Down and hold down Power Button for about 4-5 secs
- then let them go and you will see the Fastboot menu
- Press Volume Down (to highlight Recovery)
- then Press Volume Up (to select and go into Recovery, in this case the custom recovery)
- then just Wipe Cache and Wipe Dalvik Cache
- then Reboot Phone.
Done.
I think I will install CM11 for her and not have to deal with the stock ROM that gets official updates pushed onto it causing issues like this.
eyeoncomputers said:
my GF's Moto G did the same thing, luckily it was a simple fix.
I had already rooted her stock 4.4.2 and installed CWM Recovery 6.0.4.6.
So I just Powered Off the phone. Then go back into the CWM Recovery by:
- hold down Volume Down and hold down Power Button for about 4-5 secs
- then let them go and you will see the Recovery menu
- Press Volume Down (to highlight Recovery)
- then Press Volume Up (to select and go into Recovery, in this case the custom recovery)
- then just Wipe Cache and Wipe Dalvik Cache
- then Reboot Phone.
Done.
Click to expand...
Click to collapse
I see,however It's not possible on the phone. If I select the Recovery and I press volume up -> phone reboots
You mean this.
Download Stock image, extract.
Go to fastboot mode and flash following.
If you used Superboot method then use:
fastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
if you used the modified recovery method:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Tussky said:
I see,however It's not possible on the phone. If I select the Recovery and I press volume up -> phone reboots
Click to expand...
Click to collapse
Thats strange.
eyeoncomputers said:
my GF's Moto G did the same thing, luckily it was a simple fix.
I had already rooted her stock 4.4.2 and installed CWM Recovery 6.0.4.6.
If you havent installed, CWM or TWRP, then I recommend to do so by fastboot command and the recovery.img.
The general command to install a custom recovery in Fastboot is:
fastboot flash recovery your_recovery_image.img
So I just Powered Off the phone. Then go back into the CWM Recovery by:
- hold down Volume Down and hold down Power Button for about 4-5 secs
- then let them go and you will see the Fastboot menu
- Press Volume Down (to highlight Recovery)
- then Press Volume Up (to select and go into Recovery, in this case the custom recovery)
- then just Wipe Cache and Wipe Dalvik Cache
- then Reboot Phone.
Done.
I think I will install CM11 for her and not have to deal with the stock ROM that gets official updates pushed onto it causing issues like this.
Click to expand...
Click to collapse
Thanks MAN! It works perfect!
mokkami said:
You mean this[/URL].
Download Stock image, extract.
Go to fastboot mode and flash following.
If you used Superboot method then use:
if you used the modified recovery method:
Thats strange.
Click to expand...
Click to collapse
Yes, I mean that,so if I follow this guide,then it will help ? I used the followin from modaco site -> Root your Moto G - option 1: Superboot
@kokonai OH? I thought unroot is essential?
I guess u used the modified recovery to root?
Tussky said:
Yes, I mean that,so if I follow this guide,then it will help ? I used the followin from modaco site -> Root your Moto G - option 1: Superboot
Click to expand...
Click to collapse
At the moment i am confused. But yeah i'm assuming it will work.
Cause if i understand it right, the superboot method is a modified kernel.
So you should flash motoboot.img.
There are several ways now. Either you flash cwm and wipe /cache as described above.
Or you flash motoboot and then , in my opinion, it should work.
mokkami said:
@kokonai OH? I thought unroot is essential?
I guess u used the modified recovery to root?
At the moment i am confused. But yeah i'm assuming it will work.
Cause if i understand it right, the superboot method is a modified kernel.
So you should flash motoboot.img.
There are several ways now. Either you flash cwm and wipe /cache as described above.
Or you flash motoboot and then , in my opinion, it should work.
Click to expand...
Click to collapse
I used the method to root the phone what is on that site,I followed that description and it worked. I'am not an expert in it,so I just followed PaulOBrien guide,so I can't answer for it for sure.
At this point I'am really desperate as the phone is completely useless, so I don't care even if I had data loss,as I can't access it anymore,nor save it to my PC.
In my knowledge, which seems not to be true anymore, the phone needs to be stock to install any update.
I am not talking about installed apps. It is more about system partition, recovery, kernel and so on.
I would try now to flash the motoboot.img and see what happens.
If this does not work i would flash cmw and try what was mentioned above.
Sure you can go completly stock. But in my view you are not that lost.
I'll stay with you
......but max 5 hours =)
mokkami said:
In my knowledge, which seems not to be true anymore, the phone needs to be stock to install any update.
I am not talking about installed apps. It is more about system partition, recovery, kernel and so on.
I would try now to flash the motoboot.img and see what happens.
If this does not work i would flash cmw and try what was mentioned above.
Sure you can go completly stock. But in my view you are not that lost.
I'll stay with you
......but max 5 hours =)
Click to expand...
Click to collapse
Thanks! However I can try it out only after 20 UTC.
However I have an idea,but maybe I'am wrong.
What happens if I try the chace wipe via in command line, I mean:
mfastboot erase cache
This should delete the cache right ? Shouldn't this command remove the problematic update file ?
Oh yeah this should be also an option.
But you'll come again to that point where you wanna install the update?!
mokkami said:
Oh yeah this should be also an option.
But you'll come again to that point where you wanna install the update?!
Click to expand...
Click to collapse
I want to give it a try. Yes,however I don't have to install the update. But I think I will flash a stock rom,make the update and then re-root the phone.
Thank you guys, I was going crazy with this rebooting problem. So now it is fixed, but how can I get the update? Noway?
mokkami said:
Oh yeah this should be also an option.
But you'll come again to that point where you wanna install the update?!
Click to expand...
Click to collapse
I was able to enable the usb debugging,and then to start the bootloader. However If I connected the phone and tried to execute the adb reboot-bootloader command it didn't worked. So I restarted the phone and entered into the bootloader,then I've done the following:
fastboot reboot-bootloader
fastboot erase cache
After the first command,the phone rebooted into bootloader,then the second command finally cleared the chace. Now my uptime is more then 8 minutes,so the phone is working great now
However I will do the complete process on the weekend,but not now as I'am really tired,but I will flash a stock rom at the weekend.
Possible solution...
Just started a thread with a possible solution
http://forum.xda-developers.com/showthread.php?t=2663205
Hope it helps...
Related
Hello, I've recently completed the Bootloader unlocking method with Easy Ace Root Tool. Bootloader is unlocked and SHIP S-ON, I need to flash a rom. These roms require S-OFF and have no method to flash them with only an unlocked bootloader and S-ON.
So let me get this straight, us 'low level' and unexperienced users are left without any method to gain S-OFF privileges without following the vague guide provided at tau(dot)shadowchild(dot)nl/attn1/?p=411 Yeah... I can't.
Trying to find alternate methods I have only gone in circles and keep running into old how-to guides. The more I read the more confused I become. I hope someone can point me in the right direction, I would really appreciate it!
Thanks,
Ninjewbag
You don't need S-Off. Flash a ROM in recovery, then flash the ROM zip's boot.img in fastboot.
bananagranola said:
You don't need S-Off. Flash a ROM in recovery, then flash the ROM zip's boot.img in fastboot.
Click to expand...
Click to collapse
Good deal, thanks for the reply!
I put the ROM Android Revolution HD 9.0 on the root of my SD card, booted in recovery mode and chose the recovery option, I got the red exclamation mark icon so I pressed VOL up + power button which didn't work so I pulled the battery. I tried all above steps again but this time I was able to successfully get into "Android system recovery <3e> with VOL up + power button. With 4 options:
Reboot system now
Apply update from sdcard
wipe data/factory reset
wipe cache partition
I chose the option to wipe all data, said it could not find Efolder name)'s and "data wipe completed successfully".
Then I wiped cache, then chose the option to apply update from sdcard, it said "Invalid operation" then "success rebooting by reason 00" and proceeded to reboot by itself.
Phone factory reset, I rebooted into recovery again with the same red exclamation mark error. Pressed Vol up + power and back into "Android system recovery". At the bottom in yellow text it says "E: Can't open /cache/recovery/command". I tried another "update from SD card" and recieved error: "success rebooting by reason 00" and reboots.
I don't have a nandroid backup as I read I needed Root to make one, but the phone still works fine as far as I can tell. I don't have a working simcard in it though.
Also from what I've read my eMMC chip may be fried so it looks like I'm retiring early. I'll keep an eye on this thread among others with the same problems.
Cheers,
Ninjewbag
Volume + and power brings you to the factory recovery; you need to use vol - have you flashed a different recovery? If not, flash 4ext recovery through fast boot and try again
RadRacer said:
Volume + and power brings you to the factory recovery; you need to use vol - have you flashed a different recovery? If not, flash 4ext recovery through fast boot and try again
Click to expand...
Click to collapse
Thank you for the info! No luck finding the 4ext .IMG file anywhere yet, they're all dead links. I have the 4ext recovery.APK but that doesn't do me any good since I don't have root. Still looking and thanks again.
http://forum.xda-developers.com/showthread.php?p=31211732
ninjewbag said:
Thank you for the info! No luck finding the 4ext .IMG file anywhere yet, they're all dead links. I have the 4ext recovery.APK but that doesn't do me any good since I don't have root. Still looking and thanks again.
Click to expand...
Click to collapse
You can install the app and then open the app and use it to manually download the recovery zip which you can flash or copy it to your pc and extract the recovery.img file and flash with fastboot. It's a good idea to familiarize yourself wiht the adb and fastboot utils as they come in handy.
turboyoshi said:
You can install the app and then open the app and use it to manually download the recovery zip which you can flash or copy it to your pc and extract the recovery.img file and flash with fastboot. It's a good idea to familiarize yourself wiht the adb and fastboot utils as they come in handy.
Click to expand...
Click to collapse
Thanks for the reply but as for installing the 4ext free updater version, it wasn't on the market so I used android injector to place and install that APK. None of the options worked as they all give the same error "it seems your phone is not rooted, this option will not function" etc.
RadRacer said:
http://forum.xda-developers.com/showthread.php?p=31211732
Click to expand...
Click to collapse
Nice! Wasn't expecting to find the 4ext recovery within the adbfastboot.zip. With that I was able to move on, create a nandroid and successfully install a custom rom, thanks! Was a little scared after rebooting, it took around 5 minutes to load past the "quietly brilliant" screen but is working fine now nonetheless.
ninjewbag said:
Nice! Wasn't expecting to find the 4ext recovery within the adbfastboot.zip. With that I was able to move on, create a nandroid and successfully install a custom rom, thanks! Was a little scared after rebooting, it took around 5 minutes to load past the "quietly brilliant" screen but is working fine now nonetheless.
Click to expand...
Click to collapse
Glad to help. Wanna hit thanks?
Like the title says, my Nexus 5 won't boot unless I manually plug it in, hold down volume buttons and power, then wait 15 seconds for fast boot to appear, and then select "start."
Thats the problem. Now for some more information:
1. Nexus 5 32 gb
2. ROM: CM 11 Dec 13s Nightly
3. Kernel: Bricked 3.4.0
4. The phone is totally functional. The only thing wrong with it is that it can't reboot. From the system, TWRP recover, or anything, it simply will not reboot. Every time I must go into fast boot then press the power button when it says "start." After this, the phone works just as I would expect it to. I can still flash kernels and backups through recovery, it just must be restarted manually through the fast boot. This is a problem for me because I don't always want to have to plug it in when I want to reboot it.
When did it start:
Let me start off by saying that I thing the root of all my problems was the TouchControl app that allows the knock to wake function to work. I downloaded the app and was told to install the developers custom kernel. I did and not only did the app not work, it also seemed to brick my phone. I was scared, but, after doing some research, I found the method of plugging it in and holding down all buttons for about 15 seconds and my phone was saved. Ever since then there has been the problem. I must always do this to reboot my phone. Since the app didn't work I decided to install the Bricked Kernel and everything went fine except that I wasn't prompted with the interactive installer. The kernel works fine and I am now using the Knock to wake feature built into the kernel and am very happy.
Seems to be caused by swipe2wake aka knock 2 wake aka knock knock (but not totally sure)
What I've Tried (don't assume I've tried something I haven't. I could have missed something obvious.):
1. Resetting permissions through TWRP (just thought I'd try)
2. Putting back CM 11 Kernel
3. Restoring to a time when my phone did restart
Any help would be greatly appreciated. I will try to keep the original post updated with everything I try.
FIXED with the help of jd1639 and meangreenie
------------------------------------------------------------------
1.Follow jd1639's link in 3rd comment to the page and
A. Install adb and flashboot drivers
B. Install your version of factory images from google (if you are running 4.4.2 get the image for 4.4.2)
2. Plug in phone to AC CHARGER and hold down power and volume buttons for up to 20 seconds. This should put it into fast boot mode
3. After getting phone in fast boot mode, plug it into your mac or pc.
4. Out of all the instructions in the "How to flash a factory image" thread go to method 2 and ONLY DO THE FIRST TWO LINES OF CODE. All that needs to be flashed is the bootloader.img
5. After it says complete and your phone restarts you should be able to push "start" on your phone and be good!
I would try and fastboot flash boot boot.img. where boot.img is the boot image from the factory image.
jd1639 said:
I would try and fastboot flash boot boot.img. where boot.img is the boot image from the factory image.
Click to expand...
Click to collapse
So that's essentially flashing the stock ROM?
benaside said:
So that's essentially flashing the stock ROM?
Click to expand...
Click to collapse
No just the boot.img
Edit, look at method #2 but only flash the boot.img nothing else http://forum.xda-developers.com/showthread.php?p=47156064
jd1639 said:
No just the boot.img
Edit, look at method #2 but only flash the boot.img nothing else http://forum.xda-developers.com/showthread.php?p=47156064
Click to expand...
Click to collapse
Thanks so much for trying to help. I installed all the things and flashed Boot.img from fast boot, but once I restarted my phone everything was messed up (booted to home screen but basically the system started failing). After this, I retried but deleted my cache and delvik cache. This time the system simply wouldn't boot. Luckily I backed up and restored to my previous version. Thanks for trying, but this did not work.
benaside said:
Thanks so much for trying to help. I installed all the things and flashed Boot.img from fast boot, but once I restarted my phone everything was messed up (booted to home screen but basically the system started failing). After this, I retried but deleted my cache and delvik cache. This time the system simply wouldn't boot. Luckily I backed up and restored to my previous version. Thanks for trying, but this did not work.
Click to expand...
Click to collapse
Were you on 4.4 or 4.4.2. Sounds like 4.4.2. The factory image in the link was 4.4
jd1639 said:
Were you on 4.4 or 4.4.2. Sounds like 4.4.2. The factory image in the link was 4.4
Click to expand...
Click to collapse
I downloaded the folder for 4.4.2 from the link developers.google .com/android/nexus/images#hammerhead
try reflashing via custom recovery or fastboot.. bootloader, recovery and suitable boot.img for your rom, maybe give the radio a reflash too
meangreenie said:
try reflashing via custom recovery or fastboot.. bootloader, recovery and suitable boot.img for your rom, maybe give the radio a reflash too
Click to expand...
Click to collapse
Will this'd elite all my files and unroot?
Btw thanks so much for the help
benaside said:
Will this'd elite all my files and unroot?
Btw thanks so much for the help
Click to expand...
Click to collapse
no it won't delete your data.. but please triple check your files and fastboot commands before executing
the last resort is to format data if all else fails
Thank you both so much. I have (with both of your help fixed it). I will post how in the original post. Thanks again.
Trying to install CyanogenMod for my razr maxx HD. Recently used RSDlite to install 183.46.10 after OTA KK update kept failing. Then used towelroot to root and motopocalype to unlock bootloader. Fastboot screen shows bootloader is unlocked with status code: 3.
I then followed the instructions on the CyanogenMod site to flash CWM 6.0.4.4 recovery using fastboot, and all appeared to work fine.
However, when I try to reboot into recovery, nothing happens. I get hung up on the motorola dual core flashscreen for about a minute or two, then the screen goes black, then the phone reboots normally.
I tried flashing a different copy of CWM, tried TRWP, and tried several third party apps from Google Play store to boot directly into recovery using software reboot instead of hardware keys - all with the same results. I even tried flashing custom CWM recovery using ROM Manager and Rashr, same result.
Do I have a corrupt recovery partition? Any suggestions for how to fix?
You need to install a recovery for that phone specifically.
http://androidhosting.org/Devs/Dhacker29/
Use the recovery files found here.
Edit: on the site I posted, browse to the msm8690 folder. There you will find the recovery files.
to make this even easier here
TWRP http://forum.xda-developers.com/showthread.php?t=2776515
CWM http://forum.xda-developers.com/showthread.php?t=2747535
next time be sure your flashing for this phone and bootloader
billycar11 said:
to make this even easier here
TWRP http://forum.xda-developers.com/showthread.php?t=2776515
CWM http://forum.xda-developers.com/showthread.php?t=2747535
next time be sure your flashing for this phone and bootloader
Click to expand...
Click to collapse
Thanks, guys, total noob mistake. I knew the recovery needed to be specific for the phone, but didn't realize it varied depending on the bootloader. Will try again with the right recovery!
billycar11 said:
to make this even easier here
TWRP http://forum.xda-developers.com/showthread.php?t=2776515
CWM http://forum.xda-developers.com/showthread.php?t=2747535
next time be sure your flashing for this phone and bootloader
Click to expand...
Click to collapse
Those recovery aren't sticking for me. Does anyone have a suggestion to fix that issue.
Pushing the buttons doesn't work.
The only thing that is working is place the phone in fastboot mode and flash the recovery to my device three time and then I will go straight in recovery and there it is.
Sent from my SM-N900V using Tapatalk
TheGman125 said:
Those recovery aren't sticking for me. Does anyone have a suggestion to fix that issue.
Pushing the buttons doesn't work.
The only thing that is working is place the phone in fastboot mode and flash the recovery to my device three time and then I will go straight in recovery and there it is.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Your phone has been upgraded to Kit Kat and the bootloader unlocked, correct? The two recoveries linked to are for phones that already have already been upgraded to KK.
If so, power off your phone.
Then, hold down volume up and then press and hold power. After a few seconds, let go and the boot menu should come up.
Use Volume down to select "Recovery" and then hit "Volume Up". That should boot you into the custom recovery, depending on which one you flashed.
I prefer TWRP. CWM seemed buggy and it wouldn't always boot into it. A lot of times, I'd get a blank screen and would have to reflash it.
Another option is, when it's booted up, hooked up your phone to your pc and use adb to reboot it into recovery using "adb reboot recovery".
iBolski said:
Your phone has been upgraded to Kit Kat and the bootloader unlocked, correct? The two recoveries linked to are for phones that already have already been upgraded to KK.
If so, power off your phone.
Then, hold down volume up and then press and hold power. After a few seconds, let go and the boot menu should come up.
Use Volume down to select "Recovery" and then hit "Volume Up". That should boot you into the custom recovery, depending on which one you flashed.
I prefer TWRP. CWM seemed buggy and it wouldn't always boot into it. A lot of times, I'd get a blank screen and would have to reflash it.
Another option is, when it's booted up, hooked up your phone to your pc and use adb to reboot it into recovery using "adb reboot recovery".
Click to expand...
Click to collapse
Yep.. I had some issue with my devices. I tried the update well root and the devices didn't want to boot up anymore. So I had to RSD lite the devices back to health. So I do have the latest software for the devices. I guess. I am going to use Twrp since you say it boots fine from the boot menu.
TheGman125 said:
Yep.. I had some issue with my devices. I tried the update well root and the devices didn't want to boot up anymore. So I had to RSD lite the devices back to health. So I do have the latest software for the devices. I guess. I am going to use Twrp since you say it boots fine from the boot menu.
Click to expand...
Click to collapse
Is your bootloader unlocked? If not, that is your problem. You need to root, and then unlock the bootloader before you can flash TWRP and use CM.
iBolski said:
Is your bootloader unlocked? If not, that is your problem. You need to root, and then unlock the bootloader before you can flash TWRP and use CM.
Click to expand...
Click to collapse
Yes my bootloader is unlocked. Have code 3 on the devices.
try and unplug from USB when you reboot
Hi,
just got time to update my 2nd XT925 to KK (RSD'd back from CM11 JBBL to stock SFR rom, let the phone find its update and apply it, everything went fine).
But whatever KK recovery I try to flash, it gives me an exclamation mark and nothing else (I'm unlocked, yes).
Don't know what's happening here. Can someone helps please ?
Poursinet said:
Hi,
just got time to update my 2nd XT925 to KK (RSD'd back from CM11 JBBL to stock SFR rom, let the phone find its update and apply it, everything went fine).
But whatever KK recovery I try to flash, it gives me an exclamation mark and nothing else (I'm unlocked, yes).
Don't know what's happening here. Can someone helps please ?
Click to expand...
Click to collapse
Are you saying you are trying to flash a recovery or are you trying to GET to the stock recovery? If you are trying to get to the stock recovery, the key presses to get to it have changed.
Your best bet is to power off your phone. Then, press and hold power+vol up for a few seconds until you see the menu come up. Then, press vol down to highlight Recovery and then press the vol up button.
Eventually, you'll see the "Dead Andy". From there, press and hold vol down+vol up+power. You might have to do it a couple of times. Eventually, you'll be in the recovery but for the XT926, it's kind of hard to read because for some reason, they decided to make it dim.
No (but thanks anyway). What I tried to was only to install a KK recovery for CM11.
I successed but I had 2 problems mixed: the 1st one was that the Linux version of fastboot (or mfastboot) did'nt work with the new bootloader. Both were complaining about "(bootloader) Variable not supported! ". Had to find some old laptop with Windows installed to use it to flash the recovery without error.
But even then if I just let the phone reboot, I would'nt get the new recovery (just the stock one after the keypress you speak about). I had to go straight from bootloader screen to the recovery (by manually rebooting) to get it work. Looks like the standard boot just restored the stock recovery each time I tried.
Thanks anyway, it's working now.
Poursinet said:
No (but thanks anyway). What I tried to was only to install a KK recovery for CM11.
I successed but I had 2 problems mixed: the 1st one was that the Linux version of fastboot (or mfastboot) did'nt work with the new bootloader. Both were complaining about "(bootloader) Variable not supported! ". Had to find some old laptop with Windows installed to use it to flash the recovery without error.
But even then if I just let the phone reboot, I would'nt get the new recovery (just the stock one after the keypress you speak about). I had to go straight from bootloader screen to the recovery (by manually rebooting) to get it work. Looks like the standard boot just restored the stock recovery each time I tried.
Thanks anyway, it's working now.
Click to expand...
Click to collapse
Variable not supported comes up under some Windows, but it usually still works.
You never go straight to the bootloader when you reboot. You have to reboot the phone (or turn it off first) and then press and hold vol up+power. Then, from there, you use vol down to select recovery and then press vol up.
It never boots directly into the recovery unless you tell it to via an ADB command or from within a custom ROM that allows it.
Keep in mind, the stock recovery will override the custom recovery if you don't immediately boot back into recovery. Flash recovery, when that's done, press power to shutdown, and use the method Bolski described to boot into recovery.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
Keep in mind, the stock recovery will override the custom recovery if you don't immediately boot back into recovery. Flash recovery, when that's done, press power to shutdown, and use the method Bolski described to boot into recovery.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Let me see if i undestood.
You say that if you don't boot right into recovery, the stock one will overwrite CWM/TWRP. So i understand that, after very reboot you must reflash recovery if you want to use it again.
Or am I missing something?
Caliburno said:
Let me see if i undestood.
You say that if you don't boot right into recovery, the stock one will overwrite CWM/TWRP. So i understand that, after very reboot you must reflash recovery if you want to use it again.
Or am I missing something?
Click to expand...
Click to collapse
It won't reflash every time. You only need to boot straight into recovery the first time, so that the update binary completes. After the first time, you'll be good.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
It won't reflash every time. You only need to boot straight into recovery the first time, so that the update binary completes. After the first time, you'll be good.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I think this may be the problem I am having. I cant get my 926 to boot to recovery from fastboot after I load CWM recovery. Is there some trick?
Hello everyone,
Lately I've changed my rom from to another (both of them are custom). The problem is when I try to reboot my phone into recovery (TWRP) but instead it reboots into bootloader.
Re3xth said:
Hello everyone,
Lately I've changed my rom from to another (both of them are custom). The problem is when I try to reboot my phone into recovery (TWRP) but instead it reboots into bootloader.
Click to expand...
Click to collapse
How did you try to reboot into recovery? Sorry for such stupid question but you might using wrong commands or key combinations that's why I wanna know the detail info for further support
LinhBT said:
How did you try to reboot into recovery? Sorry for such stupid question but you might using wrong commands or key combinations that's why I wanna know the detail info for further support
Click to expand...
Click to collapse
I have an advanced menu in the rom where I can choose if I want to reboot into recovery, system or boot loader, so I choose recovery but the phone reboots in bootloader. Even if I just pressed the power button and volume up it also go to the bootloader
Re3xth said:
I have an advanced menu in the rom where I can choose if I want to reboot into recovery, system or boot loader, so I choose recovery but the phone reboots in bootloader. Even if I just pressed the power button and volume up it also go to the bootloader
Click to expand...
Click to collapse
Please be specific the information :
1. Which ROM r u in?
2. Before this happen, which Recovery r u in?
3. Did you try to boot into recovery by adb command : adb reboot recovery ?
1. I'm currently using Arrow os.
2. TWRP.
3.Yes I did because there's no other way you can get into the recovery but using adb only gives me access to TWRP, but the problem is that every rime I want to access TWRP I should use a computer.
Re3xth said:
1. I'm currently using Arrow os.
2. TWRP.
3.Yes I did because there's no other way you can get into the recovery but using adb only gives me access to TWRP, but the problem is that every rime I want to access TWRP I should use a computer.
Click to expand...
Click to collapse
Means you still able to boot into recovery, just that u must use command lines and the recovery's not there when u try to boot into it by other method, correct?
If so, download OF latest build R11.1.2.1 ( zip file ) boot into TWRP, flash the zip, boot info OF, flash the zip in OF again, then let it do the auto reboot into recovery. When done, clear cache, Dalvik then reboot to system as normal.
Then try to reboot to recovery by normal ways, inform me back if it's work
Thank you for your reply. I will try to do it after some time because I'm busy right now hopefully it works