Related
Hey guys,
I've been using this website as reference for years but never had an issue I hadn't already seen asked.
I've been looking for weeks for a solution to this and haven't found anything.
I tried to flash cm10.1 over my stock 4.1.2 and corrupted the system.
It was booting directly to AP Fastboot and showing an error about not calling the ROM properly.
I tried reflashing using RSD Light 5.7 but every time it tried to flash the system it said the phone returned failed.
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
ShiningRaven said:
Hey guys,
I've been using this website as reference for years but never had an issue I hadn't already seen asked.
I've been looking for weeks for a solution to this and haven't found anything.
I tried to flash cm10.1 over my stock 4.1.2 and corrupted the system.
It was booting directly to AP Fastboot and showing an error about not calling the ROM properly.
I tried reflashing using RSD Light 5.7 but every time it tried to flash the system it said the phone returned failed.
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
Click to expand...
Click to collapse
Format system via any of the custom recoveries before flashing your new ROM - this will wipe out any leftover problems completely & should let you start 100% fresh with a new ROM.
tzlot said:
Format system via any of the custom recoveries before flashing your new ROM - this will wipe out any leftover problems completely & should let you start 100% fresh with a new ROM.
Click to expand...
Click to collapse
I lost my root when I originally got stuck in fastboot. And I can't boot up the phone until I can get it fixed.
ShiningRaven said:
I lost my root when I originally got stuck in fastboot. And I can't boot up the phone until I can get it fixed.
Click to expand...
Click to collapse
Can you get back into fastboot now? If so
Use fastboot to flash a custom recovery (CWM, TWRP or OUDHS)
use the recovery to factory reset, wipe cache/dalvic, AND format system (sometimes in the advanced menu)
then flash rom of your choice.
If you can't get fastboot working you'll need smarter help than I can give you... but the format system step clears out all kinds of gremlins.
I can get into fast boot but I don't have an unlocked boot loader to flash anything custom.
ShiningRaven said:
I can get into fast boot but I don't have an unlocked boot loader to flash anything custom.[/QUOTE
If you can get into fastboot then you should be able to unlock b/l with this toolkit I used it and it worked for me you can also flash rom with it its in the orginial development thread
http://forum.xda-developers.com/showthread.php?t=2154995
Click to expand...
Click to collapse
ShiningRaven said:
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
Click to expand...
Click to collapse
Had the same problem after a fastboot via the utility. Try powering your phone down completely and leaving it off for about 5-10 min. This can be tricky with the hardware buttons so if you have access to TWRP that will help as it has a power off option. You might also try flashing again via the utility. I believe that's what I had to do, but the power down method is what a friend suggested based of his experience with the same exact problem you documented.
FIXED!!!
OK first I want to thank everybody who responded. I got tied up with work and kind of forgot about this project for a few days.
Repeated uses of the Utility and RSD both left me stuck with the phone freezing every time it tried to load the system into memory.
I had checked out the toolbox before but I didn't think I could do much from a locked bootloader.
After your suggestion jmcdonald I tried it again. It says my device isn't available to be unlocked so I tried downgrading back to ICS.
The toolbox says that it failed but it must have fixed something because the phone booted back up to android 4.1.2 stock!
So far I have bricked a lot of phones and learned a lot about ADB in the process of fixing them but I've never had one I was so certain was bricked permanently. But now it seems to be working fine, I'm scared to try rebooting in now.
Definatly going to unlock the bootloader pronto.
Thanks again jmcdonald!
Hello guys, having a bit of a dilemna here as only took the plunge to root today and is my first time in doing so. What I have done is updated to 4.4.2 KitKat OTA and then rooted my moto g. I used the superboot method and got the horrible pink screen and had to manually install supersu, however the device is rooted and obviously the bootloader is unlocked. I then proceeded to put everything back on my phone and then encrypted my phone.
However, I tried to get into recovery (stock) and was fronted with the on its back android with its belly open and red "!" in a triangle. I got this before I even unlocked to bootloader. Anyhow, I wanted to use a custom recovery so I could manage different ROMs in ROM manager etc, so I flashed CWM6046-MotoG44.img (CMW ver. 6.0.4.6) and all was swell.... until i wanted to make a backup.
I did a little searching around and was stumped until I found a post suggesting that CMW couldnt mount storage because the device was encrypted.
What I would like to know if at all possible; what would be the best course of action to take, as im unsure what will/could brick/break my device and as its encrypted I dont think adb commands are pushed as when flashing the recovery image, my device was listed in fastboot devices but not adb devices.
Should I flash a stock image and go from there, put everything back on yada yada yada and NOT encrypt the device, or....
Should I do a factory reset? will this brick my device/lose root access? or will I be able to re root?
I really appreciate any input you guys can give me, and for the meantime im just going to leave my device as it is and not flash anything else,
Many thanks and best regards,
voosh
Anybody have any ideas?
Can anybody help me here. Need to get this sorted so I can flash a custom ROM. Thanks
Bump...................
voosh710 said:
Hello guys, having a bit of a dilemna here as only took the plunge to root today and is my first time in doing so. What I have done is updated to 4.4.2 KitKat OTA and then rooted my moto g. I used the superboot method and got the horrible pink screen and had to manually install supersu, however the device is rooted and obviously the bootloader is unlocked. I then proceeded to put everything back on my phone and then encrypted my phone.
However, I tried to get into recovery (stock) and was fronted with the on its back android with its belly open and red "!" in a triangle. I got this before I even unlocked to bootloader. Anyhow, I wanted to use a custom recovery so I could manage different ROMs in ROM manager etc, so I flashed CWM6046-MotoG44.img (CMW ver. 6.0.4.6) and all was swell.... until i wanted to make a backup.
I did a little searching around and was stumped until I found a post suggesting that CMW couldnt mount storage because the device was encrypted.
What I would like to know if at all possible; what would be the best course of action to take, as im unsure what will/could brick/break my device and as its encrypted I dont think adb commands are pushed as when flashing the recovery image, my device was listed in fastboot devices but not adb devices.
Should I flash a stock image and go from there, put everything back on yada yada yada and NOT encrypt the device, or....
Should I do a factory reset? will this brick my device/lose root access? or will I be able to re root?
I really appreciate any input you guys can give me, and for the meantime im just going to leave my device as it is and not flash anything else,
Many thanks and best regards,
voosh
Click to expand...
Click to collapse
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Thanks for the reply but I have already installed the cwm custom recovery. Should I add that I'm still able to access device, my problem mainly is getting rid of encryption as I can't use cwm while device is encrypted and can only do so by factory reset or flashing a stock ROM, but unsure of which option to take. Many thanks and best regards
kieranc88 said:
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Click to expand...
Click to collapse
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview try this cwm it worked for me,I'm not too clued up on encryption but I'm guessing you can't read/write to phones system to easily with it on so I'd guess it conflicts with root
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
kieranc88 said:
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Click to expand...
Click to collapse
voosh710 said:
Thanks for the reply but I have already installed the cwm custom recovery. Should I add that I'm still able to access device, my problem mainly is getting rid of encryption as I can't use cwm while device is encrypted and can only do so by factory reset or flashing a stock ROM, but unsure of which option to take. Many thanks and best regards
Click to expand...
Click to collapse
So when you boot to recovery can you access recovery options or do you get dead robot
kieranc88 said:
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview try this cwm it worked for me,I'm not too clued up on encryption but I'm guessing you can't read/write to phones system to easily with it on so I'd guess it conflicts with root
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
So when you boot to recovery can you access recovery options or do you get dead robot
Click to expand...
Click to collapse
I did get a dead robot. So I flashed CWM custom recovery. I now get the cwm recovery and options, but I can't make a backup becausey filesystem is encrypted, so would like to know the best way to decrypt by means of flashing a new or ROM or simply doing a factory reset within tho phones menus.
Many thanks
voosh710 said:
I did get a dead robot. So I flashed CWM custom recovery. I now get the cwm recovery and options, but I can't make a backup becausey filesystem is encrypted, so would like to know the best way to decrypt by means of flashing a new or ROM or simply doing a factory reset within tho phones menus.
Many thanks
Click to expand...
Click to collapse
OK,you need to boot into cwm and choose the wipe data factory reset option from cwm, I tried to wipe my phone before from the phones menu and because it had a custom recovery it didn't work,but if you boot cwm-wipe data/factory reset it will remove encryption.
Any luck???
kieranc88 said:
Any luck???
Click to expand...
Click to collapse
Sorry, I fell asleep lol was a long day.
Going to try it now and will keep you posted, Cheers.
EDIT - Didnt work - failed to mount storage because "android secure"
Factory reset within the phone also didnt work - The phone reset and the android with the blue thing in its stomach was stuck in a loop, probably because of custom recovery.
Is there a stock recovery I can flash to factory restore the phone?
EDIT 2 - Flashed this recovery - http://forum.xda-developers.com/showthread.php?t=2578243
Now when I boot into recovery it just boots into the phone regularly. When performing a factory reset now the android doesnt even appear and the phone boots regularly again, still encrypted
voosh710 said:
Sorry, I fell asleep lol was a long day.
Going to try it now and will keep you posted, Cheers.
EDIT - Didnt work - failed to mount storage because "android secure"
Factory reset within the phone also didnt work - The phone reset and the android with the blue thing in its stomach was stuck in a loop, probably because of custom recovery.
Is there a stock recovery I can flash to factory restore the phone?
EDIT 2 - Flashed this recovery - http://forum.xda-developers.com/showthread.php?t=2578243
Now when I boot into recovery it just boots into the phone regularly. When performing a factory reset now the android doesnt even appear and the phone boots regularly again, still encrypted
Click to expand...
Click to collapse
I kinda guessed that would happen because its not stock recovery,have u got a us version or international(is it xt1032 or xt1034?
kieranc88 said:
I kinda guessed that would happen because its not stock recovery,have u got a us version or international(is it xt1032 or xt1034?
Click to expand...
Click to collapse
Its a unlocked retail UK version, not sure if its xt1032 or xt1034 because I renamed it to Moto G.
voosh710 said:
Its a unlocked retail UK version, not sure if its xt1032 or xt1034 because I renamed it to Moto G.
Click to expand...
Click to collapse
You've got the same as mine,OK if that didn't work it might be because its jellybean, this is a recovery for the us version but its a KitKat recovery but worst that can happen is it won't boot to recovery, flash it and if doesn't work I'll see can I extract the recovery image from my phone, try it and get back to me asap fastboot flash recovery recovery.IMG
https://www.dropbox.com/s/66br4aiyzipu6x9/recovery.img
kieranc88 said:
You've got the same as mine,OK if that didn't work it might be because its jellybean, this is a recovery for the us version but its a KitKat recovery but worst that can happen is it won't boot to recovery, flash it and if doesn't work I'll see can I extract the recovery image from my phone, try it and get back to me asap fastboot flash recovery recovery.IMG
https://www.dropbox.com/s/66br4aiyzipu6x9/recovery.img
Click to expand...
Click to collapse
Flashed and still boots regularly .
voosh710 said:
Flashed and still boots regularly .
Click to expand...
Click to collapse
In the command line is it saying recovery sent
kieranc88 said:
In the command line is it saying recovery sent
Click to expand...
Click to collapse
Sent and finished ok
voosh710 said:
Sent and finished ok
Click to expand...
Click to collapse
How many times have you flashed it,try flashing two three timees
kieranc88 said:
How many times have you flashed it,try flashing two three timees
Click to expand...
Click to collapse
Actually, looking at the device it says "hab check failed for recovery"
However the other one (jellybean one i think that I linked to) never.
tried flashing 5 or 6 times no luck
Try this link to restore to 4.3 then ota to 4.4 again http://www.modaco.com/topic/366786-how-to-flash-to-the-standard-uk-rom/
I have a Moto G X1032 rooted with TWRP installed. I've been using the stock firmware for 4.4.2 without any issues for a while, but after June 6th's OTA update to 4.4.3, my phone has gotten stuck in a boot loop. It turns on and runs Android as usual, without any issues, for less than a minute and then shuts down. It then continues to boot back up and continue the process. The only way to stop the loop is to boot into the bootloader from TWRP and power off the phone from there. Luckily I have a backup to that reverts me back to 4.4.2, which successfully stops the loop. But after several attempts to update to 4.4.3, it has become quite clear that this boot loop is inevitable unless I stick with 4.4.2. I read an article that seems to address some conflict with rooted phones and 4.4.3, but I'm not quite sure what the conflict is. Can anyone explain to me why this boot loop is most likely happening, what I could do to fix it, or if it is even possible to have a rooted X1032 with 4.4.3 installed? Any help whatsoever would be greatly appreciated. Thank you.
Are you saying you tried to install the OTA with TWRP installed and not the stock recovery?
Just go into recovery clear all cache,kavik cache that should do
NerdNoob1210 said:
I have a Moto G X1032 rooted with TWRP installed. I've been using the stock firmware for 4.4.2 without any issues for a while, but after June 6th's OTA update to 4.4.3, my phone has gotten stuck in a boot loop. It turns on and runs Android as usual, without any issues, for less than a minute and then shuts down. It then continues to boot back up and continue the process. The only way to stop the loop is to boot into the bootloader from TWRP and power off the phone from there. Luckily I have a backup to that reverts me back to 4.4.2, which successfully stops the loop. But after several attempts to update to 4.4.3, it has become quite clear that this boot loop is inevitable unless I stick with 4.4.2. I read an article that seems to address some conflict with rooted phones and 4.4.3, but I'm not quite sure what the conflict is. Can anyone explain to me why this boot loop is most likely happening, what I could do to fix it, or if it is even possible to have a rooted X1032 with 4.4.3 installed? Any help whatsoever would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
secretkloud said:
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
Click to expand...
Click to collapse
Thank you. I will try that. Before I do though, do you know of any places I could find 4.4.3 online, so I could just download it from my PC and flash it over via sideload? I usually prefer to flash things that way, rather than straight from the phone.
bozzykid said:
Are you saying you tried to install the OTA with TWRP installed and not the stock recovery?
Click to expand...
Click to collapse
Yes. This is my first time doing so, excuse my lack of knowledge on the subject. In retrospect, I suppose I should have known there must be a different method with which I install it. Secretkloud gave me a good suggestion though. Is there a reason in particular as to why I can't do OTA updates with custom recovery installed?
secretkloud said:
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
Click to expand...
Click to collapse
I just downloaded the zip from my phone and flashed it from Phillz recovery. It worked very well and the update was successful. Thanks for pointing me to Phillz recovery by the way. It's the only functional recovery image that allows me to mount the sdcard.
NerdNoob1210 said:
Thank you. I will try that. Before I do though, do you know of any places I could find 4.4.3 online, so I could just download it from my PC and flash it over via sideload? I usually prefer to flash things that way, rather than straight from the phone.
Click to expand...
Click to collapse
Copy the one you have in your phone onto your PC. Smallest chance of error if you do it that way...
it's not easy getting out of the loop.
I did a factory reload of a rooted phone with CWM.
Now for the CWM issue the Moto G loaded OK and then said there was an update for android to fix some bugs. This was 4.4.3. I loaded it and it gets half way and it then says
"Signature verification fail"
at the bottom of the screen and
" Install Untrusted Package"
The options are yes, no or go back
at the top....
whichever one I try it then tries to boot shows the Android / Motorola screen and starts up gets a txt message for 2-3 seconds... it then goes back to Android CWM recovery with the same options as above and repeats the process. again and again and again. No function keys will stop this cycle which just repeats again. This continues until the battery dies.
any ideas ? how can I override this action in CWM v6.0.4.6 and force it to do a factory reload ? any help or advice much appreciated.
If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose.
Sent from my XT1032 using XDA Premium 4 mobile app
NerdNoob1210 said:
If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
unfortunately I can't get into bootloader. I can connect usb and it makes no difference. therefore adb commands dont work. it just goes straight into screen described with those three options. I'm hoping that there is an override action in CWM which isn't power and volume down which do nothing.
thanks for the suggestion tho. it was a good idea.
Hm... Without access to the boot loader, I'm not sure there's much of anything you can do anymore... You've completely lost the ability to communicate any sort of commands to your phone save for the 3 options that menu provides. I assume that what CWM is trying to do is install the zip from your cache and is failing to do so. The only viable option would be to flash a new recovery image and install the zip manually, but that's impossible for you given your current circumstances. I would give up looking for an override command for CWM, your best hope is to find an alternative means with which you can access your boot loader. I suggest you start a thread dedicated to your issue and see if a more experienced user can provide you with the information you need. Sorry, I hope you get the help you need. :/
Sent from my XT1032 using XDA Premium 4 mobile app
Thanks for trying to help. I have followed your advice and opened a thread
NerdNoob1210 said:
Hm... Without access to the boot loader, I'm not sure there's much of anything you can do anymore... You've completely lost the ability to communicate any sort of commands to your phone save for the 3 options that menu provides. I assume that what CWM is trying to do is install the zip from your cache and is failing to do so. The only viable option would be to flash a new recovery image and install the zip manually, but that's impossible for you given your current circumstances. I would give up looking for an override command for CWM, your best hope is to find an alternative means with which you can access your boot loader. I suggest you start a thread dedicated to your issue and see if a more experienced user can provide you with the information you need. Sorry, I hope you get the help you need. :/
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flashed “BETA-SuperSU-v2.66-20160103015024.zip”. System now stuck on "Warning Bootloader unlocked" screen. I can get to Android recovery. I did wipe cache but same condition exists. Is it safe to do a factory reset at this point?
Although I recovered by restoring a Nandroid backup, I am still curious if selecting factory reset from stock recovery would have worked, or is this not an advisable method for soft brick recovery?
MrTooPhone said:
Although I recovered by restoring a Nandroid backup, I am still curious if selecting factory reset from stock recovery would have worked, or is this not an advisable method for soft brick recovery?
Click to expand...
Click to collapse
Flash BETA-SuperSU-v2.62-3-20151211162651.zip in xt1550 moto g3. Done and working fine
MrTooPhone said:
Flashed “BETA-SuperSU-v2.66-20160103015024.zip”. System now stuck on "Warning Bootloader unlocked" screen. I can get to Android recovery. I did wipe cache but same condition exists. Is it safe to do a factory reset at this point?
Click to expand...
Click to collapse
First flash system firmware.. then flash TWRP recovery.. then Flash BETA-SuperSU-v2.62-3-20151211162651.zip SuperSU Package.. Done..
sieze.s said:
Flash BETA-SuperSU-v2.62-3-20151211162651.zip in xt1550 moto g3. Done and working fine
Click to expand...
Click to collapse
Maybe I did not use the best words to ask my question. Can you recover from a system stuck on "Warning Bootloader unlocked" screen by simply doing a factory reset?
Did the same thing
MrTooPhone said:
Flashed “BETA-SuperSU-v2.66-20160103015024.zip”. System now stuck on "Warning Bootloader unlocked" screen. I can get to Android recovery. I did wipe cache but same condition exists. Is it safe to do a factory reset at this point?
Click to expand...
Click to collapse
I did the same thing could someone help me? I updated to 6.0 a couple days ago (I just got the phone) and decided to unlock the bootloader. Everything worked fine. I have minimal ADB and fastboot set up and all the drivers are set up properly too.
I then decided to flash TWRP. I didn't check "Read Only". Everything seemed fine. I swiped to reboot and was told to install supersu so I did and then rebooted.
Now I can't get past the white "Warning Bootloader Unlocked" screen. I can access the bootloader and TWRP, I'm just not sure what exactly to do next.
I have a Moto G 2015 2GB on T-Mobile USA
dcalf94 said:
I then decided to flash TWRP. I didn't check "Read Only". Everything seemed fine. I swiped to reboot and was told to install supersu so I did and then rebooted.
Now I can't get past the white "Warning Bootloader Unlocked" screen. I can access the bootloader and TWRP, I'm just not sure what exactly to do next.
I have a Moto G 2015 2GB on T-Mobile USA
Click to expand...
Click to collapse
You should not have installed supersu. Not sure why that option exists.
MrTooPhone said:
You should not have installed supersu. Not sure why that option exists.
Click to expand...
Click to collapse
What can I do to fix it?
dcalf94 said:
What can I do to fix it?
Click to expand...
Click to collapse
Did you make a Nandroid backup before flashing SuperSU? If so, restore your backup and start again.
MrTooPhone said:
Did you make a Nandroid backup before flashing SuperSU? If so, restore your backup and start again.
Click to expand...
Click to collapse
I do not have a back-up :/ Is it still safe to flash the 5.1.1 stock firmware if I was already on 6.0 via OTA? I tried a factory reset in TWRP, but that did't work.
dcalf94 said:
I do not have a back-up :/ Is it still safe to flash the 5.1.1 stock firmware if I was already on 6.0 via OTA? I tried a factory reset in TWRP, but that did't work.
Click to expand...
Click to collapse
If you are going to reflash, why not 6.0 firmware?
Is flashing my only option since I have no back-up?
MrTooPhone said:
If you are going to reflash, why not 6.0 firmware?
Click to expand...
Click to collapse
I haven't been able to find the 6.0 stock firmware for it. only 5.1.1
If all I have to do is flash 6.0 stock firmware and my phone is fixed could I do it in TWRP? Like, just drag the firmware into my phone's download folder and just install in TWRP?
MrTooPhone said:
If you are going to reflash, why not 6.0 firmware?
Click to expand...
Click to collapse
Did you look at http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 or http://firmware.center/firmware/Motorola/Moto G (3rd gen-2015)/Stock/
dcalf94 said:
I haven't been able to find the 6.0 stock firmware for it. only 5.1.1
If all I have to do is flash 6.0 stock firmware and my phone is fixed could I do it in TWRP? Like, just drag the firmware into my phone's download folder and just install in TWRP?
Click to expand...
Click to collapse
You also may want to look at http://forum.xda-developers.com/2015-moto-g/development/rom-stock-motorola-rom-collection-t3296964
MrTooPhone said:
Maybe I did not use the best words to ask my question. Can you recover from a system stuck on "Warning Bootloader unlocked" screen by simply doing a factory reset?
Click to expand...
Click to collapse
Yes you can.
Edit - My phone was also stuck at this screen only - "Warning Bootloader unlocked"
I also soft bricked my phone 3-4 days ago but got it back.
Follow below steps and you are good to go -
1. Download and install Motorola Moto Drivers
2. download stock firmware from http://forum.xda-developers.com/2015...mages-t3169639 for your Moto G3 model (in my case it was XT1550)
3. download TWRP from http://forum.xda-developers.com/devd...1051#downloads [ i used twrp-osprey-2.8.7-r5.img version ]
4. download SuperSU from http://forum.xda-developers.com/show...25&postcount=3 [make sure you download BETA-SuperSU-v2.62-3-20151211162651.zip version only else you'll again brick your phone]
Now as you have all required things to get your phone back, now follow below steps -
Now flash stock ROM, Instruction here -> http://forum.xda-developers.com/2015...ctory-t3187750
Now flash TWRP - fastboot flash recovery your_recovery_name_here.img
now start your phone (takes 15 minutes around)
now go to recovery and flash BETA-SuperSU-v2.62-3-20151211162651.zip and start your phone [ do not allow TWRP to root your phone when it asks you to root your phone just tap not now (or whatever i don't remember right now)]
Starting up phone now takes 25-30 minutes approx.
Rooted
[Don't brick and blame me , do it at your own risk ]
The point where things went wrong was that last screen where TWRP asks you if you want to root the phone - NEVER let it do that, ever, even after you properly root it the right way (which is manually flashing that specific version of SuperSU or a later version).
I've had instances where on a random reboot into TWRP - on a properly rooted Moto G3 - where that question screen comes up. It should not come up when the phone is actually rooted but I've seen it once or twice. Again, the point is: NEVER EVER let TWRP do it's own internal rooting process because that's what breaks things on the Moto G3.
- flash stock firmware complete
- go back and flash TWRP
- use TWRP to manually flash the SuperSU version (at least 2.62 beta which is what the Moto G3 running Marshmallow requires)
- make sure after that flash of SuperSU you do NOT use the TWRP option to root the device when you close out TWRP, ever
- flash a replacement logo so you don't see the bootloader is locked splash screen
That's about it.
I just unlocked BL. How long does it take to restart the phone from ADB recovery screen? Seems like forever.
guest_2011 said:
I just unlocked BL. How long does it take to restart the phone from ADB recovery screen? Seems like forever.
Click to expand...
Click to collapse
It is basically a factory reset. Not sure you need adb at this point.
MrTooPhone said:
It is basically a factory reset. Not sure you need adb at this point.
Click to expand...
Click to collapse
I kept holding pow button, it kept restarting back to the same BL unlocked message, then finally booted back to MM. Took a while i thought i bricked it.
guest_2011 said:
I kept holding pow button, it kept restarting back to the same BL unlocked message, then finally booted back to MM. Took a while i thought i bricked it.
Click to expand...
Click to collapse
same problem with me. almost an hour and the same page "BL Unlocked". how long did it take for your phone to spring back to life?
Hi, I came here because I've tried to fix my phone but no hope. My situation si that I'm on a Loop in the booting process where the phone starts the booting process but crashes maybe on the bootloader. My system can see the Port COM 4 and I tried the Mobile upgrade program but after it detects the phone and I click "Update" button the phone goes into the loop maybe trying to get into Fastboot. Lastly, the download fails.
I have never hacked or made any modifications on an Android phone before so I'm a complete noob to this ADB tools and don't have a clue on how to use any tool to recover this phone.
I'm able to boot into "Download mode" and nothing else, maybe there's a combination for getting into the bootloader but I don't see anything about that in the many searches.
Any help is much appreciated.
you device is bricked and you try root install a custom rom or a bad upgrade
ravendepth said:
Hi, I came here because I've tried to fix my phone but no hope. My situation si that I'm on a Loop in the booting process where the phone starts the booting process but crashes maybe on the bootloader. My system can see the Port COM 4 and I tried the Mobile upgrade program but after it detects the phone and I click "Update" button the phone goes into the loop maybe trying to get into Fastboot. Lastly, the download fails.
I have never hacked or made any modifications on an Android phone before so I'm a complete noob to this ADB tools and don't have a clue on how to use any tool to recover this phone.
I'm able to boot into "Download mode" and nothing else, maybe there's a combination for getting into the bootloader but I don't see anything about that in the many searches.
Any help is much appreciated.
Click to expand...
Click to collapse
First boot into recovery and wipe cache and data.
If that fails try again. It fails again use the below method to restore your phone.
Go into download mode and using the ABD install your stock rom., Meaning your phones original version.
Your phones not bricked.
Stuck at Bootscreen (BootLoop)
Custo481 said:
First boot into recovery and wipe cache and data.
If that fails try again. It fails again use the below method to restore your phone.
Go into download mode and using the ABD install your stock rom., Meaning your phones original version.
Your phones not bricked.
Click to expand...
Click to collapse
Hi,
I tried to install RR on my Alcatel Idol 3 4.7 with using Shara & Firehorse according to this thread https://forum.xda-developers.com/idol-3/general/guide-unlock-flash-root-updated-alcatel-t3751845
everything went accordingly but TWRP never installed. I to boot into recovery and it booted android recovery instead of TWRP. So i tried again using Firehorse but my phone did not boot to download mode, so i cleared cache using the Android system recovery but then i received an error can't mount cache/recovery , so i tried to reset to factory data and received yet again other errors. Force-Restarting my phone ended up in a bootloop that i am not sure how to remove. Please help
Model: Alcatel One Touch Idol 3 6039 K
its-ian said:
Hi,
I tried to install RR on my Alcatel Idol 3 4.7 with using Shara & Firehorse according to this thread https://forum.xda-developers.com/idol-3/general/guide-unlock-flash-root-updated-alcatel-t3751845
everything went accordingly but TWRP never installed. I to boot into recovery and it booted android recovery instead of TWRP. So i tried again using Firehorse but my phone did not boot to download mode, so i cleared cache using the Android system recovery but then i received an error can't mount cache/recovery , so i tried to reset to factory data and received yet again other errors. Force-Restarting my phone ended up in a bootloop that i am not sure how to remove. Please help
Model: Alcatel One Touch Idol 3 6039 K
Click to expand...
Click to collapse
Hi, you may want to try a different TWRP recovery. Had the same problem. solved with TWRP 3.0.0 f2fs from Decker's MM TWRP backup. TWRP 3.1 also works with Sahara&Firehose.
Hope this helps.