I had really hard time naming this thread because I'm not sure anymore what's the problem.
I tried to update my Moto G (unlocked bootloader and rooted) to 4.4.2. First I unrooted the device by flashing stock rom using this guide. After I had succesfully updated to 4.4.2 I changed from dalvik to ART. When I tried to reboot, after the Motorola boot animation there was only a black screen. I tried to downgrade back to 4.3 with no success. Now when I try to boot I only get the "warning bootloader unlocked" sign over and over again. CWM recovery can't mount /sdcard/.
Have I bricked my phone or is there something I can and should do?
Thanks for the replies, I'm covered in cold sweat here.
EDIT: Seems I was too quick to make a thread. After editing the flashall.bat a little like stated in the thread I was able to flash back to stock.
FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Original post:
SHORT VERSION:
My god this has been one crazy root journey.
I have done absolutely EVERYTHING I could pull up on google to fix my phone, and what seemed to be the final piece to the puzzle, still has not fixed anything.
My phone is bricked, and i would really appreciate help at this point.
The current problem:
When I turn on my phone, it vibrates, and displays the WARNING BOOT LOADER UNLOCKED screen, and stays there forever.
I can access my boot loader, and recovery, but I dont know what to do at this point.
I tried a quick flash stock recovery kit kat with moto tool AIO, and it didnt help.
Any ideas?
LONG VERSION (backround info may help to understand the current issue)
Now, if you want to know what began all of this, continue reading, otherwise the above is my current issue.
After successfully unlocking and rooting my phone
I downloaded SWITCHME, an app that lets you create multible users on the phone. the instructions say that you can use a sub account to test and mess around with anything because you can simply go back to the admin account that has everything untouched.
That was a lie.
1.I deleted .setup, along with a few other things THAT WHERE NOT FLAGGED AS IMPORTANT, assuming the phone would still work. and my phone went bonkers, displaying this infinite message: UNFORTUNATELY, SETUP HAS STOPPED. It was impossible to use the phone, and I could only access bootloader.
2.After endless googling, driver downloading, xda mod installing, I managed to set up my boot loader to do the guide restore stock firmware:http://forum.xda-developers.com/showthread.php?t=2542219
Sadly, I flashed the wrong model number package, I was flashing x35, when I later discovered that my phone is x45.
Flashing the x35 firmware bricked my phone further, to where it would "fail to boot up" and would only display bootloader over and over after attempting to turn the phone on.
3. Simple, I realized I flashed the wrong thing, so I downloaded the x45 firmware from the firmware teem on this website, flashed all of the commands, and bam, the phone starts up with the boot loader warning, and DOES NOT get stuck in the previous boot loader issue I had.
But now the phone wont get past that warning screen so... now im pissed.
Please, if anyone can help me I would greatly appreciate it, Im so close to getting my phone back...
EDIT 2: Looks like the phone wont stay shut down, I realized that if I dont open up boot loader, it will turn itself on and display the warning message.
EDIT:
The stuffs I have, ready to try anything:
CWM touch mod
Moto Tool AIO
Minimal ADB and Fast boot
RETUS x1045 factory firmware
All directories, folders, cmd commands are set up and working properly between all of the programs.
The phone appears to be responding to all cmd commands properly.
I also have the windows one touch super boot root method. (he superboot-windows.bat )
Im afraid to try anything major after freshly flashing the x45 firmware that seemed to bring me one step closer without the help of someone else.
I restored stock to my phone using this link yesturday http://www.ibtimes.co.uk/how-restore-motorola-moto-g-stock-firmware-1447290
it may work for you
I have almost the same problem as if the fastboot not install anything despite not display errors
great that you got it done.
maybe my few cents about my "bricking" story. (xt1032 moto g)
yesterday i wanted to change the rom from cm11 nightly to another custom rom like ehndroix/carbonrom...
first i thought that will be done in a few mins, after having already flashed a custom rom.
then the story began, getting adb work, but, 2weeks ago everything was setup and went fine. dunno why my laptop lost the "drivers".
thats the link which solved that problem: tinyurl . com / kgffjh4 [sorry cant post links outside of xda yet, spam protection]
so after a few hours of getting that fixed i, i began flashing.
suddently i got stuck in bootscreen (ehndroix logo for example)...
then i wanted to go back with my previous backup made internaly of clockworkmod. though i couldnt restore my backup because there was an error message while restoring /data of my backup
also when restoring to factory/wipe in cwm there was that error message about clouldnt "touch" /data, i dont remember the message exactly.
after thinking i bricked everything, i though lets wipe my internal sdcard, maybe that causes the /data error.
then i restarted the device and went for a shower... after 15min i came back and my device was "started".
now i dont know that exactly helped, maybe wiping all data on my phone, or just letting my device boot for a "long" time...
so, thats my yesterdays brick story.
do a factory reset if the bootloader has that option.. otherwise install or run/boot a custom revovery, then either
try the factory reset option there and reboot or..
wipe everything and install a rom
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
ngr.hd said:
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
Click to expand...
Click to collapse
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
angelgzg said:
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
Click to expand...
Click to collapse
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
ngr.hd said:
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
Click to expand...
Click to collapse
I flash the recovery but rebooted into recovery, the android keeps popping up (no commands)
FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Sorry I'm traveling a d couldnt update thread fast enough.
Hi guys,
I have a Moto G XT1039 (peregrine) 4.4.4
I unlocked bootloader, flashed Clockwork recovery and rooted.
Tried to flash Cyanogen but failed so went back to 4.4.4 and after updating Motorola Update Services tried to install 5.1 but failed again. Tried reflashing stock firmware and recovery but it still failed to update to 5.1. Maybe I got the wrong stock firmware, EU as opposed to GB...
Anyway, tried to flash 5.1 with XT1039_PEREGRINE_RETGB_5.1_LPB23.13-17_cid7_CFC.xml.zip using the following method http://forum.xda-developers.com/showthread.php?t=2542219
All looked good but after reboot it was stuck on Warning Bootloader Unlocked screen.
I'm now back in fastboot screen and tried again to use the above method but this time for XT1039_RET-GB-SS_4.4.4_KXB21.14-L1.56-1_cid7_CFC_1FF.xml.zip as this appears to be the correct firmware for my phone.
But in cmd I keep getting 'mfastboot' is not recognized as an internal or external command, operable program or batch file.
What can I do to get my phone working again?
Thanks in advance
Just realised I forgot to get the mfastboot... will try again.
Repeated the steps but with the 4.4.4 zip. It looked like a fail at first (had a dead green dalek with an exclamation mark in a red triangle on the screen) but after some waiting it started showing some signs of life and eventually booted up. The only problem is it has like a shockwave line constantly traveling down the screen. Any ideas why and how to fix it?
Repeated the flashing process once more with XT1039_RET-GB-SS_4.4.4_KXB21.14-L1.56-1_cid7_CFC_1FF.xml.zip but this time added mfastboot oem lock begin in front of other commands.
Didn't solve the line accross the screen but was able to download and install the 5.1 through the official channel.
All sorted now.
Was good talking to self
Over and out
So, My phone was rooted and I unlocked the bootloader. I have relocked bootloader and flashed my stock recovery so I can update to Marshmallow. Here is the problem:
When the update downloads and verifies the phone usually reboots so it can download. The progress bar doesn't even finish and the phone opens the recovery which shows State 7 installation aborted. Running stock OS 5.0.1 Lollipop. Help is aprecciated
Not sure what process you used to re-lock your boot loader. A couple of things you can try: 1st you may not want to loose your data but you could try a factory reset. 2nd if factory reset doesn't work you could use RUU to set device back to factory check this thread here
Recovery errors?
HeckNoTechnO said:
Not sure what process you used to re-lock your boot loader. A couple of things you can try: 1st you may not want to loose your data but you could try a factory reset. 2nd if factory reset doesn't work you could use RUU to set device back to factory check this thread here
Click to expand...
Click to collapse
Quick last question, when I open the recovery itself, it shows some errors like bitmap error oem, and down on thr bottom it says something like CW files not found skipped CW installation. Do I still proceed with the factory reset because i dont wsnna end up bricking my phone? Thanks for the quick reply, aprecciate it.
DreamFantom said:
Quick last question, when I open the recovery itself, it shows some errors like bitmap error oem, and down on thr bottom it says something like CW files not found skipped CW installation. Do I still proceed with the factory reset because i dont wsnna end up bricking my phone? Thanks for the quick reply, aprecciate it.
Click to expand...
Click to collapse
I think in your situation to get stock recovery on your device you may want to use the RUU method.
Sent from my Nexus 6 using Tapatalk
Hello all, this is my first post so I apologize if anything isn't right.
I recently flashed my Mate 9 to stock Nougat B19x through a method I found on this site and then decided I wanted root. Bootloader was already unlocked so I flashed TWRP and then tried to flash a couple different root methods that all failed... So I factory reset through TWRP and tried again but they still failed so on the initial boot everything worked except the screen was blank except for the soft keys. I rebooted and the same again so I put it in fastboot and tried to re-install Nougat through the same method that worked before. It went through the whole process seemingly fine and finished with 'Update should start automatically' but then the phone boot into error mode. I've looked through everything I can find here and done everything I can think of myself but nothing has worked. I can boot into to fasboot but nothing else, not even after flashing any recoveries or stock images extracted from UPDATE.app.
Func no is 14 and error no is 1.
It's a MHA-L09 and I really need to fix it as I can't really afford anything else right now. Any help would be really appreciated and I'm happy to add more info if I've missed anything.
Thanks guys!!!
BUMP
Sorry if it's not very concise, just really need help!
What commands are you using to flash the stock files?
CandyFoxJ said:
What commands are you using to flash the stock files?
Click to expand...
Click to collapse
Standard fastboot flash recovery/system/boot
Not sure if I'm flashing all the right files or if huawei needs different commands.
Follow this guide.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Thanks for your help. That's the one that I used in the first place but everytime I try again, TWRP either doesn't flash even though it says success or I can't get into recovery.
Everytime I try to access recovery using the hardware keys it boots to error mode so is there another way??
I've been looking into this some more and have found it could be a motherboard issue. Is this correct? And if so how much would that kind of repair cost and would it even be possible considering I've unlocked the bootloader?
Thanks again.