Hi everyone,
I recently rooted my moto g and installed TWRP. The next day I get notifications saying that there is an update available and I downloaded it and installed it. The phone proceeded to shut down and install the update, but rather than the Android logo with the blue bar as I expected a long string of messages came from TWRP and I was dumped at the TWRP home screen. So when I reboot my phone the update hasn't installed and I was still being pestered by pop up messages to install the new update. So I came to the conclusion to un-root, install the stock rom as shown in the video "Flash your Tesco Moto G To Stock" by AndroidAndyUK.
I thought I should install the update without a recovery. The only problem is that when I go to install the rom like in the video, something goes wrong i guess and once its finished the "Bootloader Unlocked" white screen with red writing appears to go into an infinite boot loop. I flashed TWRP and wiped cache and everything then tried re installing the rom numerous times. At the fastboot screen three key things show in purple writing rather than yellow like in the video, which are:
version downgraded for primary_gpt
version downgraded for tz
version downgraded for boot
I can flash TWRP from ADB in my C drive but its not recognized by the command "adb devices".
At the moment I have an unusable phone and I would really appreciate any advice on the topic.
At the moment I have an unusable phone and I would really appreciate any advice on the topic.
Thanks very much.
Do not flash gpt.bin
Do not flash motoboot.img
Flash the rest as usual.
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.
After updating to CM12 my phone started having battery issues, someone told me to use mfastboot and flash back to 4.4.4 I did this and It worked, after a couple of updates I went back to CM12 It worked fine for about a week until I started to have issues with my battery again, so I tried to update the version of CM12 straight from the phone and it just turned off and died, I read on a thread in this forum that I had to use mfastboot again to be able to get my phone working, I did so but now everytime I get the phone to turn on it does not go past the "WARNING, BOOTLOADER UNLOCKED" screen.
I have used mfastboot to flash a 4.4.4 firmware, a 4.4.2 firmware and a 5.0.1 firmware, everytime I can do this succesfully, but when the phone reboots I see my self stuck in the Warning screen again.
If anyone can help me with this issue I would really appreciate it! :laugh:
Ok so Im thinking it might be a bootloader error, anyway I can flash the bootloader?
Hello Guys!
Recently i received my used Motorola Moto G. Phone was nice, I was using it like every teenager, instagram snapchat etc. But last night i wanted to install rom on phone. Saw thread about installing everything, root rom etc. with 1 program. I tought it will be nice, so i downloaded it, run, and there is a problem. It was command line tool, everything gone right, there was messeage about clicking any button to continue, I did it and then my phone restarted, but there was like normal 5.0.2 android not 5.1 what was saying guy who wrote thread about that program. So i thought that i will do everything step by step, unlocked bootloader, installed recovery and when i first time opened recovery from bootloader menu it had problem with mounting data partition. I was trying to install firmware roms, but it had problems with downgrading bootloader. Downloaded 5.0.2 firmware .xml.zip file, it gone ok, i mean there wasn't a problem with motoboot.img, and at every single command there was only okay, there wasn't failed, just had 2 problems on phone screen, it was saying "hab check failed for boot" and "hab check failed for recovery". After typing every single command to fastboot and restarting phone always phone was stucked on boot screen, i mean on 4.4 it was stuck on messeage about unlocking bootloader, on 5.0.2 it was stucked on that 4 colors orbs flying around the screen. Then i was trying to open my stock recovery, but it was always broken, opened android with warning sign on it. When i was installing custom recovery that had problems with mounting /command /log /last_log /last_install, and when i was trying to mount data it couldn't mount it, I was trying to format /data and /data/media, it was always going ok and then i could mount data partition, but my phone was still stuck on boot screen. I was trying to install custom recovery again but it had same problem, just opened android with warning sign. And there is a question, what can I do to make my telephone working.
I'm sorry for mistakes, but my english is not the best
Try reading this thread here and see if that helps.
I was having a problem with my Moto G XT1033 yesterday as most apps get closed automatically at launch. this morning i installed AVG to do a scan, i also used Root file manager to clean up some files (junks, duplicates etc)
I then did a restart after which my phone will not boot to home screen again.
It boots up showing the boot animation bout after that i get a black blank screen which back light on.
Things i have tried
did cache partition wipe
did wipe/restore
all to no avail
I then downloaded a stock ROM from Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip
downloaded minimal ADB and fastbook.
- put the phone to fastboot
- on android system recovery mode i clicked apply update from ADB
then on PC i confirmed it can see my phone by typing adb devices, my phone get listed.
I then do adb sideload Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip
Finding update package.........
Opening update package........
Verifying update package........
Installing update..........
Then i get Package expects build fingerprint of motorola/falcon_asia_ds/falcon_umtsds:5.0./LXB22.46-28/30:user/release-keys or motorola/falcon_asia_ds/falcon_umtsds:5.1/PB23.13-56:user/release-keys; this device has motorola/falcon_asia_ds/falcon_umtsds:5.1/LPBS
E:Error in /sodeload/package.zip (status 7)
Install aborted.
Device Details
Moto G
XT1033
build LPBS23
Indian version
running Android 5.1.1 (running latest android for the device, i only do OTA updates/upgrades)
Not rooted
no custom OS
I will really appreciate any help to get the device up again
wasconet said:
I was having a problem with my Moto G XT1033 yesterday as most apps get closed automatically at launch. this morning i installed AVG to do a scan, i also used Root file manager to clean up some files (junks, duplicates etc)
I then did a restart after which my phone will not boot to home screen again.
It boots up showing the boot animation bout after that i get a black blank screen which back light on.
Things i have tried
did cache partition wipe
did wipe/restore
all to no avail
I then downloaded a stock ROM from Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip
downloaded minimal ADB and fastbook.
- put the phone to fastboot
- on android system recovery mode i clicked apply update from ADB
then on PC i confirmed it can see my phone by typing adb devices, my phone get listed.
I then do adb sideload Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip
Finding update package.........
Opening update package........
Verifying update package........
Installing update..........
Then i get Package expects build fingerprint of motorola/falcon_asia_ds/falcon_umtsds:5.0./LXB22.46-28/30:user/release-keys or motorola/falcon_asia_ds/falcon_umtsds:5.1/PB23.13-56:user/release-keys; this device has motorola/falcon_asia_ds/falcon_umtsds:5.1/LPBS
E:Error in /sodeload/package.zip (status 7)
Install aborted.
Device Details
Moto G
XT1033
build LPBS23
Indian version
running Android 5.1.1 (running latest android for the device, i only do OTA updates/upgrades)
Not rooted
no custom OS
I will really appreciate any help to get the device up again
Click to expand...
Click to collapse
Firstly, I would like to point out that your phone is merely soft-bricked. Hard bricks are much more serious and happen when your phone does not turn on at all. So, in future, please do not complain about a hard brick where there is none.
Onto the actual issue, it appears to be an easy fix. The problem was simply that you were attempting to sideload an OTA update, as opposed to flashing full firmware, which will not work. So all you need to do is flash the full factory firmware using fastboot flash, not adb sideload. To do this, flash factory firmware from here using the fastboot commands linked on that thread.
Professor Gibbins said:
Firstly, I would like to point out that your phone is merely soft-bricked. Hard bricks are much more serious and happen when your phone does not turn on at all. So, in future, please do not complain about a hard brick where there is none.
Onto the actual issue, it appears to be an easy fix. The problem was simply that you were attempting to sideload an OTA update, as opposed to flashing full firmware, which will not work. So all you need to do is flash the full factory firmware using fastboot flash, not adb sideload. To do this, flash factory firmware from here using the fastboot commands linked on that thread.
Click to expand...
Click to collapse
im sorry for the false alarm.
Thanks! :good: