Hy all!
I've unlocked my Moto G (XT1032), and installed Philz Advanced CWM Recovery. My problem is that if I restart my phone it auto boots into recovery, I have to restart to bootloader and select normal powerup. It's quite annoying (I can live with it, but I hope that it can be solved).
I've tried reflashing the recovery, but id it not helped.
Is there any way to force the boot process, to start normall?
Thanks, Abel
Sent from my Nexus 7 using xda app-developers app
fastboot oem fb_mode_clear
mokkami said:
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
it is still the same
boot loop
I had same problem on my moto g 1034 i had return to stock and flash CWM6046-MotoG44 image i found here or online somewhere. The basic non touch version
tclaw said:
I had same problem on my moto g 1034 i had return to stock and flash CWM6046-MotoG44 image i found here or online somewhere. The basic non touch version
Click to expand...
Click to collapse
I've used it with the normal CWM first, but it was the same there... maybe returning to stock, and start the whole process would help, I will give it a try, if I have some time for that, and let you know about the result.
Bumper03 said:
I've used it with the normal CWM first, but it was the same there... maybe returning to stock, and start the whole process would help, I will give it a try, if I have some time for that, and let you know about the result.
Click to expand...
Click to collapse
Restored everything to original, and now it boots normally. Thanks
Related
Hey everyone,
Basically I was trying to flash a new ROM onto an old Nexus S of mine and when I tried to boot into recovery there was just a black screen. I pressed the power button and a single line saying "Clockwork mod Recovery" and the version number popped up. I assumed that the recovery must've been corrupted so I erased it and installed the latest version using fastboot which seemed to work fine.
Now whenever I try to boot into recovery I just get a blank screen with nothing else. I've tried using other recovery images such as twrp but the same problem happened, I just get the background wallpaper/image and nothing else.
I searched the forums and apparently people were having this issue earlier on when the i9023 was first released but now most custom recoveries are supposed to work with both i9020 and i9023.
Also the touch buttons light up and vibrate whenever I touch them when I'm in recovery mode.
Any help to this problem would be greatly appreciated as atm I have an old ROM which is buggy as hell and I need to get rid of it.
Cheers!
I had the same Issue. If you can boot into the rom, you can try to download the rommanager-app and install the recovery from there.
Hey I tried that already that and instead of booting into recovery it just went into the bootloader and said "No Recovery or Bootloader found".
Any other ideas?
Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App
Hey
I have the i9023 and I install rom manager. install CWM and if I reboot into recovery it works and I get in to CWM recovery.. but after reboot into os.. if I go into Rom manager and reboot to recovery it dont work? I just get the android figur and a "!".. then I just can Power + vol up and I'm in bootloader recovery..
Do I have to install CWM every time i want to use it? and can't I access CWM on boot op ?
sorry for my bad English
Normaly you have to flash the recovery only once.
Try to flash the newer clockwork-recovery with fastboot.
http://forum.xda-developers.com/showthread.php?t=988686
Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES
bedalus said:
Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES
Click to expand...
Click to collapse
I havent unlock my phone, but I can get in to bootloader is it then necessary to unlock ?
I try to delete the /install-recovery.sh
Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App
Xziped said:
Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Then it must be unlock as default.. I havent unlock it.. just delete the install install-recovery.sh and it works every time now.
now I just have to find a ROM to try..
Xziped said:
Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...
Simultaneity said:
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...
Click to expand...
Click to collapse
what happens when you try to temporary boot into the recovery?
instead of "fastboot flash recovery recovery.img", try to "fastboot boot recovery.img"
Just look for an recovery.img that works temporary and then try to flash it permanently.
I'll try it and get back to you Xziped. If anyone else can think of any other ideas please just throw'em at me, I'm willing to try anything!
Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.
Simultaneity said:
Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.
Click to expand...
Click to collapse
Sorry but if not even the temporary recovery boots up, i dont know what else we can do
did you try some of the older recoverys? is your bootloader unlocked?
I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next
Simultaneity said:
I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next
Click to expand...
Click to collapse
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.
khartaras said:
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.
Click to expand...
Click to collapse
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!
Simultaneity said:
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!
Click to expand...
Click to collapse
Just look @ http://www.samfirmware.com/ .
There you should find all you need
Sent from my Full Android on Crespo using XDA App
So, today I trade my HTC One for a RAZR XT925, $350, and a water proof 32GB Sandisk ultra sd card on Kijiji. I thought it was kinda weird to get all of this stuff, but it seemed fine at the time. Afterwards however, I found out that every time you turn off or reboot the phone, it tried to go into recovery mode or something with the android guy and a bar at the bottom in a loop and always factory reset the phone, so no matter what, every time you turned it off, it'd reset it. After hours and hours of work, I have the bootloader unlocked, rooted, CWM installed, and Cynogenmod also installed. It no longer factory resets it (I think, but i sent a text to a random number and when I rebooted it was still there), however, everytime i power off and power on, it goes into recovery mode. This is very annoying and will make it very hard to sell again, but if I can fix this last thing, I'll have a solid phone until the waterproof S4 comes out as well as having made like $100.
So basically, I need to know what to do to make it boot into the rom by default and not the recovery. Also, I searched it up and someone else had a problem where they kept booting into AP fastboot mode I think, I tried that line, it said successful, but it didnt work. For me, it's booting into the recovery by default.
Does it boot into stock recovery?
Sent from my Galaxy Nexus using xda premium
recovery
jmcdonald58 said:
Does it boot into stock recovery?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I root it, unlocked the boot loader, flashed cwm recovery, and installed CyanogenMod. Now it boots into cwm recovery by default and if I click reboot system now, it just boots back into cwm. Only way to get to the system is to go to the boot menu by pressing all three buttons and selecting boot normally.
Stock recovery is gone. Cwm asked to replace it so that the phone doesn't reinstall it on reboot. Cwm doesn't, but when the phone booted it stock recovery, it used to get wiped.
roguezz said:
I root it, unlocked the boot loader, flashed cwm recovery, and installed CyanogenMod. Now it boots into cwm recovery by default and if I click reboot system now, it just boots back into cwm. Only way to get to the system is to go to the boot menu by pressing all three buttons and selecting boot normally.
Stock recovery is gone. Cwm asked to replace it so that the phone doesn't reinstall it on reboot. Cwm doesn't, but when the phone booted it stock recovery, it used to get wiped.
Click to expand...
Click to collapse
Strange If it was me I would try a toolkit and redo the whole process something went wrong somewhere wish I could help Good Luck
recovery
jmcdonald58 said:
Strange If it was me I would try a toolkit and redo the whole process something went wrong somewhere wish I could help Good Luck
Click to expand...
Click to collapse
No the problem was in stock. When I got it it wasn't rooted or anything, rooting helped fix the problem partially by not making it wipe every time I boot it. Now the only problem is that whenever I boot it up after a shut down or restart, it boots into recovery mode instead of the ROM.
roguezz said:
No the problem was in stock. When I got it it wasn't rooted or anything, rooting helped fix the problem partially by not making it wipe every time I boot it. Now the only problem is that whenever I boot it up after a shut down or restart, it boots into recovery mode instead of the ROM.
Click to expand...
Click to collapse
did you ever find a solution for this? I just bought a used phone and am facing the same problem - I can't even boot into recovery, it will just start bootlooping again. Only thing that seems to be working is fastbood mode. (or regular reboot, but then everything is wiped every time)
coldtech said:
did you ever find a solution for this? I just bought a used phone and am facing the same problem - I can't even boot into recovery, it will just start bootlooping again. Only thing that seems to be working is fastbood mode. (or regular reboot, but then everything is wiped every time)
Click to expand...
Click to collapse
Fastboot the stock ROM. That should return the phone to it's bone stock condition.
Sent from my DROID RAZR HD using Tapatalk 4
mentose457 said:
Fastboot the stock ROM. That should return the phone to it's bone stock condition.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
trying right now. RSDLite is giving me an "unknown fastboot command getvar" error...still trying to figure out why.
coldtech said:
trying right now. RSDLite is giving me an "unknown fastboot command getvar" error...still trying to figure out why.
Click to expand...
Click to collapse
I wouldnt mess with RSDLite. Google gave us fastboot for a reason.
mentose457 said:
I wouldnt mess with RSDLite. Google gave us fastboot for a reason.
Click to expand...
Click to collapse
is there an alternative to flash the stock ROM on a locked device?
coldtech said:
is there an alternative to flash the stock ROM on a locked device?
Click to expand...
Click to collapse
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
mentose457 said:
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
Click to expand...
Click to collapse
Thanks for the hint, will give it a try. RSDLite just completed flashing, but the odd behaviour of the phone is still the same. Guess I might just have a broken phone... :/
mentose457 said:
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
Click to expand...
Click to collapse
After a few hours, I (somehow) ended up being able to enter recovery. On the downside though, now it always goes automatically into fastboot, because everything seems to be screwed up. I even got CWM installed though (unlocked the device because I didn't know what else to do).
Now every time it goes into fastboot, the reason given is: "sticky bit fastboot"
Any ideas left?
Oh btw, I have a german phone, in case that matters somehow. I can't flash in any fastboot way anymore, now I always get some message about a downgraded version. Of course details can be supplied if needed.
edit: was now able to flash CM, no idea what I did so that it didn't give me errors anymore. It still goes into fastboot by default on every reboot though, I always need to select "reboot device" manually every time.
coldtech said:
After a few hours, I (somehow) ended up being able to enter recovery. On the downside though, now it always goes automatically into fastboot, because everything seems to be screwed up. I even got CWM installed though (unlocked the device because I didn't know what else to do).
Now every time it goes into fastboot, the reason given is: "sticky bit fastboot"
Any ideas left?
Oh btw, I have a german phone, in case that matters somehow. I can't flash in any fastboot way anymore, now I always get some message about a downgraded version. Of course details can be supplied if needed.
edit: was now able to flash CM, no idea what I did so that it didn't give me errors anymore. It still goes into fastboot by default on every reboot though, I always need to select "reboot device" manually every time.
Click to expand...
Click to collapse
Sounds like you are able to use the phone. That’s good.
The error is saying it can’t downgrade the trust zone (tz) right? That is normal for a phone with an unlocked bootloader. You can simply ignore that.
The sticky bit fastboot problem looks like it can be fixed by issuing this command while in fastboot mode: fastboot oem fb_mode_clear
mentose457 said:
Sounds like you are able to use the phone. That’s good.
The error is saying it can’t downgrade the trust zone (tz) right? That is normal for a phone with an unlocked bootloader. You can simply ignore that.
The sticky bit fastboot problem looks like it can be fixed by issuing this command while in fastboot mode: fastboot oem fb_mode_clear
Click to expand...
Click to collapse
the fb_mode_clear was the culprit, thanks a lot!
and the error says: "downgraded security version. update gpt_main version failed. preflash validation failed for GPT" - which is still keeping me from flashing stuff via fastboot.
since I can't fastboot flash at the moment: do you happen to know where I can get the german modem image so that I can flash it using CWM? I think through all the flashing and trying I have a corrupt or wrong modem file (probably the US version). I can not log into the carrier network right now. it asks me for my SIM PIN and unlocks the SIM, but that's it. so I can't make phone calls or anything right now.
Hello everybody, today I just unlocked the bootloader of my Moto g like motorola says in official website. After this I turn on the phone and after motorola earth animation display just turns all black. I don't know what to do. Please can you help me? Im desperate... Please help.
Anarkau said:
Hello everybody, today I just unlocked the bootloader of my Moto g like motorola says in official website. After this I turn on the phone and after motorola earth animation display just turns all black. I don't know what to do. Please can you help me? Im desperate... Please help.
Click to expand...
Click to collapse
Go to the bootloade mode again by pressing "power button + volume down button" and check your device status.. If it unlocked, we can proceed with next steps.. If it locked, try unlock it again using the same guide...
Sent from my XT1032 using XDA Premium 4 mobile app
padhu1989 said:
Go to the bootloade mode again by pressing "power button + volume down button" and check your device status.. If it unlocked, we can proceed with next steps.. If it locked, try unlock it again using the same guide...
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Actually is unlocked and I just installed CWM on device. I have acces to bootloader mode and CWM mode. What can I do now? I think the better choice is to flash a rom again but i don't now how to do if I havent got access to my phone memory, so i cant put the files into phone.
//
I downloaded Carbon-kk rom and a repack stock 4.4.2. I dont know where can I find the original stock.
which is the next step?
Anarkau said:
Actually is unlocked and I just installed CWM on device. I have acces to bootloader mode and CWM mode. What can I do now? I think the better choice is to flash a rom again but i don't now how to do if I havent got access to my phone memory, so i cant put the files into phone.
//
I downloaded Carbon-kk rom and a repack stock 4.4.2. I dont know where can I find the original stock.
which is the next step?
Click to expand...
Click to collapse
Can you try clearing dalvik cache, cache partition, erase user data and Try to boot the mobile once.. If nothing works, need to flash the stock rom..
Which version are you using?? Single sim or dual sim or GPE one?
padhu1989 said:
Can you try clearing dalvik cache, cache partition, erase user data and Try to boot the mobile once.. If nothing works, need to flash the stock rom..
Which version are you using?? Single sim or dual sim or GPE one?
Click to expand...
Click to collapse
Thank you very much for your help. I just flashed again stock rom with cmd. This threat help me with all the comands.
http://www.htcmania.com/showthread.php?t=738212
Same issue
this happens to me occasionally. it goes to black screen when an app restarts the phone or the device was forced shutdown (hold power 20secs)
to fix it, i go to recovery, either reset to factory or install a backup rom will revive the phone, but it is very annoying.
anyone knows a permanent solution?
not sure what to format on cwm, im afraid to lose anything important..
God I'm stupid.
So I flashed a 4.4.3 theme on a 4.4.4 ROM, and I was stuck at the boot animation.
I went to recovery, found out I don't have any ROM's on my phone, so I figured I should flash through fastboot.
I downloaded the stock 4.4.4 image, tried to do the flash-all.bat, got an error.
I extracted the RAR inside it, manually flashed recovery, system, boot etc.
I can now only enter fastboot. Whenever I try to go to recovery or start the phone the screen just goes black, and all I can do is hold down the power button and restart to fastboot.
I sure hope you guys can help me, I don't have the money to buy a new phone
Drunkbag said:
God I'm stupid.
So I flashed a 4.4.3 theme on a 4.4.4 ROM, and I was stuck at the boot animation.
I went to recovery, found out I don't have any ROM's on my phone, so I figured I should flash through fastboot.
I downloaded the stock 4.4.4 image, tried to do the flash-all.bat, got an error.
I extracted the RAR inside it, manually flashed recovery, system, boot etc.
I can now only enter fastboot. Whenever I try to go to recovery or start the phone the screen just goes black, and all I can do is hold down the power button and restart to fastboot.
I sure hope you guys can help me, I don't have the money to buy a new phone
Click to expand...
Click to collapse
Do you know what error you got when you did the flash-all?
Sent from my Nexus 5 using XDA Free mobile app
Have you tried flashing stock 4.4.3 or even 4.4.2 completely in fastboot? Including recovery again??
jd1639 said:
Do you know what error you got when you did the flash-all?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I don't remember really, something about missing .sig files I think
KJ said:
Have you tried flashing stock 4.4.3 or even 4.4.2 completely in fastboot? Including recovery again??
Click to expand...
Click to collapse
I'm trying the Nexus Root Toolkit, and before that I managed to install TWRP 2.7.1.1 and boot to recovery.
However, I can't boot to the system.
I also downloaded 4.4.3 and going to attempt to flash it.
The missing Sig error is normal and nothing to worry about
Sent from my Nexus 5 using XDA Free mobile app
It's all fine.
Luckily a friend called me on Skype and I told him about my bricked device, he suggested to use NRT.
Thanks for the help guys!
Ok, I'll to be be as detailed as possible.
I recently got a Moto G XT1072, so I was planning to sell my Moto G XT1032.
The Moto G XT1032 was rooted, working perfectly fine on 4.4.2. Like a fool, because I recently rooted my Moto G XT1072 with relative ease, I thought I understand the whole fastboot process etc and I thought I'd try to update the Moto G XT1032 to lollipop. I saw a thread here and downloaded GPE 5.1 Lollipop and put it in the SDCard internal memory via Laptop. Then I loaded fastboot, went into fastboot in the phone and tried to update firmware via TWRP. It said it was loaded but then when I reboot is, it would load with little multi coloured balls spinning around. I left it all night but it was the same.
So, earlier today, I used the following thread, thinking that might help it. http://forum.xda-developers.com/moto-g/general/install-brazil-5-0-ota-xt1033-t2963800
However, as I followed all the instructions, the phone now is stuck on the "bootloader unlocked warning" and it just stays there and the phone doesn't load.
Any ideas on how to get my phone back to normal please?
Thanks!
P.s. I cannot get into recovery anymore either! Help!
Why would you follow a guide for XT1033 + 5.0 OTA when you tried to flash an XT1032 with 5.1 GPE?
Anyway, I think your initial problem might be due to an incorrect partition format.
Now, for your new problem... Are you sure you cannot enter recovery at all? Try to push power + volume down for a least 10 seconds... I had a similar problem a while ago and I was able to enter recovery that way after a few tries... Don't give up just yet.
nekobibu said:
Why would you follow a guide for XT1033 + 5.0 OTA when you tried to flash an XT1032 with 5.1 GPE?
Anyway, I think your initial problem might be due to an incorrect partition format.
Now, for your new problem... Are you sure you cannot enter recovery at all? Try to push power + volume down for a least 10 seconds... I had a similar problem a while ago and I was able to enter recovery that way after a few tries... Don't give up just yet.
Click to expand...
Click to collapse
Because I thought I know it all but I'm actually stupid!
I can get into fastboot on my phone, but I cannot get into recovery. Any idea what to do?
I just thought about something... You probably flashed an incorrect recovery, so maybe flashing TWRP (GPE version) again from fastboot mode would solve the recovery problem and from there you can try and flash GPE again...
Actually, I don't see why it wouldn't work.
nekobibu said:
I just thought about something... You probably flashed an incorrect recovery, so maybe flashing TWRP (GPE version) again from fastboot mode would solve the recovery problem and from there you can try and flash GPE again...
Actually, I don't see why it wouldn't work.
Click to expand...
Click to collapse
Awesome, thanks. I can now access recovery. Any ideas on what to do now? I am absolutely clueless!
When I go to File manager and click on Sdcard, there is nothing there! Dunno if that makes any difference.
Please help!
Oh... You probably formatted your whole phone, then...
OK... What happens when you plug your phone (in recovery mode) to your computer? Are you able to access it? Can you copy files to it? If you can, you can copy the GPE zip to it and then flash it using the "Install" command in TWRP. If you can't, you need to "push" it to your sdcard using adb sideload. Are you familiar with that method?
nekobibu said:
Oh... You probably formatted your whole phone, then...
OK... What happens when you plug your phone (in recovery mode) to your computer? Are you able to access it? Can you copy files to it? If you can, you can copy the GPE zip to it and then flash it using the "Install" command in TWRP. If you can't, you need to "push" it to your sdcard using adb sideload. Are you familiar with that method?
Click to expand...
Click to collapse
It's ok buddy, I sorted it out using a tutorial on youtube. I just flashed a different version of 4.4.4 on it and it worked! Thankfully