Related
Hi there everyone,
I have a huge problem. Last night i bricked my xoom. I was following a tutorial on this forum. and after unlocking the bootloader it told to flash a file called boot.img after doing so and typing fastboot reboot, the device wouldnt start behind the motorola logo. i tried allot of thing and also did flash some other stock android 4.0.4 boot.img files now with the last one mentioned i managed to get the xoom (wifi) to boot a little further. because the ripple movie with the motorola logo is shown. but it stucks at that movie.
Does anyone know if i can flash an image on the xoom that will atleast fix the problem of not rebooting so i can try another tutorial.
I have searched the internet for solutions, many of them linked to threads on this forum. but almost all download links in these tutorials are old and broken.
Can someone please help me unbrick my device? And maybe a link to a good working unroot tutorial for my xoom wifi with android 4.0.4.
Try get back to Stock.
Download from HERE
and do some OTA updates afterwards so everything will be up to date.
Then wipe and try again from scratch..
Worked for me perfectly just a few days ago.
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Cubanluke88 said:
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Click to expand...
Click to collapse
Indeed it worked. i downloaded the official images and flashed them im on android 3.0.1 again and all seems to work just fine now.
Next problem is i cant find a descent tutorial on this forum how to root the xoom. all download links are either removed due to copyright issues or the links are just broken.
How does it work actually?
1. I unlocked the boot loader wich is very easy.
but then? Do i need to flash a rooted image over the existing? i dont really understand how this works. I rooted my Desire HD with a good tutorial in minutes. Not many people seems to really know how to root the Xoom.
Also i would like to know if the different tutorials are for different android versions or can i aply all tutorials of rooting when i stay on android 3.0.1?
I also tried to flash a recovery.img to the recovery partition and press volume down 3 seconds after the moto logo apears but when i do i get an android robot with a big " ! " on his belly and it takes 5 minutes to load the menu. when im in it tells me there is no sdcard present when i try to flash a rooted rom (zip file).
Is there someone reading this thats willin to explain to me how to do a root the easiest way? Please if links are posted be sure everything on that thread is working. Im pretty sure i will pull it off with some push in the right direction.
Thank you!
(edit) omg im stupid, offcourse the sdcard wont work... it never worked at 3.0.1. on the xoom. can i follow this tutorial:
http://rootzwiki.com/topic/451-how-to-root-the-wifi-only-xoom-301/
Could someone read over it and see if this is a good tutorial? last time i flashed a boot.img the whole xoom got stuck... is that because i had the wrong boot.img on the wrong android version? or should boot.img always work?
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Cubanluke88 said:
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Click to expand...
Click to collapse
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
eos 4.1.1 is simply awesome and its also pre rooted' so your bootloader is unlocked, all you gotta do now is install twrp recovery via fastboot ( my preffered recovery) then flash eos via recovery
Sent from my Xoom using XDA Premium App
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
EOS is a pretty AOSP rom. No theme, though you can apply one if you like and change a few colors. There are various toggle additions you can add that make the user experience much better. It also comes with an overclockable kernel and is very very stable (despite being a nightly) The team has been supporting the Xoom for over a year and is very committed to the Xoom.
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
As for flashing, just gotta make sure your text is good before hitting the enter key. Recovery flash should look something like this:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Some instructions for flashing can be found here
While that page is specifically for locking and flashing to return to stock, the commands are universal for fastboot. Hell, if you wanted to, you could manually restore a nandroid backup via fastboot and flashing images.
Hi everyone, i'm new here as you can see... I had installed Android 4.2.1 CM10.1 Nightly ROM in the last 2-3 days but now I am to stock firmware, I've unrooted my device successfully after reading all the threads in this forum, BUT it seems that I can't find any method to download my original recovery kernel image because I can't install any new updates, it says: "Entering recovery kernel image" a loading bar appear under the android logo and after that an android logo with the red exclamation mark. I couldn't find any helpful information on how to bypass this error here in this forum so PLEASE HELP ME, I don't know what to do...I've spend almost 2 days trying to figure it out and nothing. THANK YOU IN ADVANCE and sorry for "my english".
When i put the device into fastboot mode and run the command "fastboot oem lock" i've got this message on the screen: "The system.img is not a official image"
I am assuming that no one knows... now i screwed up things and i deleted my recovery img, tablet doesn't enter recovery mode anymore. Please guys i'm begging you, i'm desperate...what should I do???
You cannot "re-lock" your bootloader once you have unlocked it. Although, a few users have has success re-locking it after installing certain ICS stock roms. You may have to try several ICS stock roms and get lucky.
You can get a stock recovery image for the 700/701 here in the dev forum. Just make sure you select the one for your OS. (ICS-JB). Don't mix them.
Typically, once you do OEM unlock, you will not be able to get OTA updates. 50-50
MD
Moscow Desire said:
You cannot "re-lock" your bootloader once you have unlocked it. Although, a few users have has success re-locking it after installing certain ICS stock roms. You may have to try several ICS stock roms and get lucky.
You can get a stock recovery image for the 700/701 here in the dev forum. Just make sure you select the one for your OS. (ICS-JB). Don't mix them.
Typically, once you do OEM unlock, you will not be able to get OTA updates. 50-50
MD
Click to expand...
Click to collapse
Thank you, i've made it reinstalling recovery image, everything working fine. From what I understand my warranty is gone, even if I install ICS they will know.
I can install updates but only manually...renaming file in update.zip but before modifying in "META-INF"...google...com the updater script the line with "assert prop".
Moscow Desire said:
You cannot "re-lock" your bootloader once you have unlocked it. Although, a few users have has success re-locking it after installing certain ICS stock roms. You may have to try several ICS stock roms and get lucky.
You can get a stock recovery image for the 700/701 here in the dev forum. Just make sure you select the one for your OS. (ICS-JB). Don't mix them.
Typically, once you do OEM unlock, you will not be able to get OTA updates. 50-50
MD
Click to expand...
Click to collapse
On the end of the update (flashing update.zip trough cwm) proces i got the question if i want to keep cwm recovery, when not stock was installed. (or am i confused?)
Please note: I know there are other guides here on XDA but none worked for me, so I'm writing this to help other stuck people.
Disclaimer: I tested this on my XT1032, I don't know if or how it will work on other variants. Following this guide you'll lose all data on your phone, make sure to backup important stuff. I'm not responsible for what you do to your phone following this guide (anyway if you're here probably you have not much to lose...)
Introduction
What happened: a couple of weeks ago I wanted to try GPE rom on my XT1032, so I flashed the appropriate rom for my device (4.4.3 KOT49H.M004) and then applied OTA (4.4.3 KOT49H.M004 to 4.4.4 KTU84P.M003). Today I decided to go back to stock, so I rebooted in bootloader mode and tried to flash stock 4.4.3.
Result: a bunch of fastboot errors, ranging from "wrong size partitions", to "preflash validation failed", to ... well I don't remember all of them, as I said they were a lot..
Then I tried older versions, I tried to reflash 4.4.3 GPE, I tried to follow guides, here on XDA and around the vast internet.. All with no luck. Until I found one and, long story short I did it. I'm back to stock 4.4.4 (flashed stock 4.4.3 and applied OTA)
I'm sharing this what I did to recover from the soft-brick, hoping to help someone. This guide is not a temporary workaround while waiting for full 4.4.4 GPE image, this will fully restore your Moto G.
Let's start
- Make sure you have fastboot drivers installed (if you managed to soft-brick it you probably have them already installed, otherwise you can get them here)
- Download and extract this
- Reboot your phone in fastboot mode (keep Volume Down and Power buttons pressed for about 5 seconds then release the power button) and plug it to the PC
- Open the extracted folder and run "GPE_XT1032_KOT49H.M004_CFC.bat". Wait for it to finish (ignore errors, they're normal), then reboot to bootloader again (choose Normal powerup and keep pressed Volume Down until it boots to bootloader again)
- Download and extract this (mirror)
- Open the extracted folder and run THE FILE "fastboot flash recovery recovery.img.bat" (poorly chosen filenames, I know)
- Wait for it to finish, then choose "Recovery" item in bootloader and let it reboot to recovery.
- Go to "mounts and storage" and select "format cache", confirm, then select "format /data and /data/media", confirm.
- Go back to main menu and select "wipe data/factory", confirm.
- Return to the folder and run the file "adb push a.zip sdcard a.zip.bat", let it finish (it will take a couple of minutes, the window will close itself when done).
- From recovery select "install zip", then "choose zip from sd card" and select "a.zip". Let it finish, then go back to main menu and choose "power options", then "reboot to bootloader"
- Download and extract this (mirror)
- Open the extracted folder and run "flashall.bat". You should see no error (I got an error while it was flashing recovery but this is not important, what you should notice is that all the errors you got before are gone). Let it finish, then give it some time to boot.
Enjoy
You're done. Now you should have a stock 4.4.2 retail EU moto g. At this point you can flash the rom you want (for example, I flashed the original retail de, since my phone is german) without getting errors
---------------------------------------------------------------------------------------------------------
More or less I followed this, but I wrote the exact steps I made, I fixed wrong commands and uploaded a more complete version for last file
i have the same problem... i am waiting for thoe missing files... and i will try to go back to stock
EDIT i can't download the filles from mega
and the first download is broken
bannab said:
i have the same problem... i am waiting for thoe missing files... and i will try to go back to stock
EDIT i can't download the filles from mega
and the first download is broken
Click to expand...
Click to collapse
I fixed first link, I'm going to check the one from mega... If you find some other problems please let me know so I'll update
Edit: mega link is working. I suppose you're from Italy (me too), it's a DNS problem (mega has been blocked by AGCOM). you can follow this guide to change dns to google ones (8.8.8.8 and 8.8.4.4). When you downloaded the file you can set them back to auto. If someone can suggest an alternative good host (and possibly a way to directly upload from mega (I have a veeeeery slow upload bandwidth) I'll appreciate
i have already tried that method but no luck..
bannab said:
i have already tried that method but no luck..
Click to expand...
Click to collapse
Try with tor bundle.. It's a version of firefox modified for privacy and security purposes, you should be able to download from mega with it
Or this
nope
again lo luck for me.. flash of stock gives me always the same errors.. i think i will keep gpe with root... and wait for a camera with slow-mo..
bannab said:
again lo luck for me.. flash of stock gives me always the same errors.. i think i will keep gpe with root... and wait for a camera with slow-mo..
Click to expand...
Click to collapse
Did you follow exactly the guide? Did you get errors while wiping or flashing a.zip from recovery?
flashing stock
maybe beacuse i have booted after flashing gpe... i needed to boot it beacuse adb gives me error (device not found)
so i will keep gpe
bannab said:
flashing stock
maybe beacuse i have booted after flashing gpe... i needed to boot it beacuse adb gives me error (device not found)
so i will keep gpe
Click to expand...
Click to collapse
That is due to drivers.. OK, in case you do it again, check recovery messages to be sure it's doing its things
You saved my phone, thank you ! :victory:
JcruzV said:
You saved my phone, thank you ! :victory:
Click to expand...
Click to collapse
You're welcome.. That little heart attack when you see it's not booting and it doesn't flash anything [emoji1]
It worked! Thank you.
doodoo28s said:
It worked! Thank you.
Click to expand...
Click to collapse
Glad I helped
Thank's my Friend ! You have save my phone ! Thank youuuuuuu !!!!!!! <3
Hello.I tried to root my device with superboot and now my phone is not booting up,i tried to reboot but still the same,my screen stays black.Can this fix my phone? thnks
Nicolae-Daniel said:
Hello.I tried to root my device with superboot and now my phone is not booting up,i tried to reboot but still the same,my screen stays black.Can this fix my phone? thnks
Click to expand...
Click to collapse
This is useful if you can't flash anything. If you can, you can just flash stock or custom ROM
i suceed come back to 4.4.2 stock!!! thank you!!!!
finally a fix
thanks for posting this fix and all the others involved. i'm on EU so now i have to get back to my regular 4.4.4 Google Play Edition. this is good till i can get that back. been trying for 2 weeks to unbrick this thing and now i have it. thanks again and to the member JcruzV who linked this post. and not to forget PhilZ. :good:
bootsie35 said:
thanks for posting this fix and all the others involved. i'm on EU so now i have to get back to my regular 4.4.4 Google Play Edition. this is good till i can get that back. been trying for 2 weeks to unbrick this thing and now i have it. thanks again and to the member JcruzV who linked this post. and not to forget PhilZ. :good:
Click to expand...
Click to collapse
Didn't know this was linked in other threads
I hope this will be sticked or something, to avoid being forgotten in a couple of months. When I was searching how to unbrick I read of people who gave up and bought a replacement, wasting money when fortunately there is a solution
It did work!
I used Linux, so had to change a few things in the command files.
There are also two things:
1.
adb push a.zip /sdcard/a.zip - no apsce before the 2nd a.zip
2.
after the 3rd step recovery complains about "new ROM will overwrite recovery" - I have answered Yes.
I have got also another problem. Meanwhile I tried to recover my phone after the downgrade from 4.4.4 GPE to 4.4.2 Motorola ROM (before this thread), I have lost the IMEI... Currently it's still 0.
Anyone have an idea to recover this?
So i tried flashing the lollipop software to my moto g xt1032 (i am a noob at this) and i think i messed up my phone. It now wont go past the bootloader/fastboot screen. Before updating i was running android 4.4.2. When i initially boot up my phone it says version downgraded for boot, failed to validate boot image, fastboot reason: fall through from normal boot cycle i have tried to follow the many guides their are out there that work/i am too dumb to understand them. If anyone can please help me. If i did not give enough info please ask and i will try my best to give it to you.
austin66887 said:
So i tried flashing the lollipop software to my moto g xt1032 (i am a noob at this) and i think i messed up my phone. It now wont go past the bootloader/fastboot screen. Before updating i was running android 4.4.2. When i initially boot up my phone it says version downgraded for boot, failed to validate boot image, fastboot reason: fall through from normal boot cycle i have tried to follow the many guides their are out there that work/i am too dumb to understand them. If anyone can please help me. If i did not give enough info please ask and i will try my best to give it to you.
Click to expand...
Click to collapse
You need to flash android 5.0 factory image for boot, and system. Follow the regular fastboot procedures to flash the 5.0 firmware. Makr sure you don't downgrade back to kitkat once you flash lolipop or else YOU WILL END UP IN A HARDBRICK!!!!!
skyguy126 said:
You need to flash android 5.0 factory image for boot, and system. Follow the regular fastboot procedures to flash the 5.0 firmware. Makr sure you don't downgrade back to kitkat once you flash lolipop or else YOU WILL END UP IN A HARDBRICK!!!!!
Click to expand...
Click to collapse
as i said i am a noob i am not really sure how to do that
skyguy126 said:
You need to flash android 5.0 factory image for boot, and system. Follow the regular fastboot procedures to flash the 5.0 firmware. Makr sure you don't downgrade back to kitkat once you flash lolipop or else YOU WILL END UP IN A HARDBRICK!!!!!
Click to expand...
Click to collapse
i have been trying to flash 5 and when i go in to recovery and load the file through adb it goes for like 5 minutes then says installation aborted
austin66887 said:
i have been trying to flash 5 and when i go in to recovery and load the file through adb it goes for like 5 minutes then says installation aborted
Click to expand...
Click to collapse
You need to flash using fastboot not adb. Look around the forum there are some great tutorials for a beginner.
skyguy126 said:
You need to flash using fastboot not adb. Look around the forum there are some great tutorials for a beginner.
Click to expand...
Click to collapse
So I tried to flashing using fastboot and my device still wont load up
Were you trying to install GPE 5.0.1? Or the soak test for X1033?
austin66887 said:
So I tried to flashing using fastboot and my device still wont load up
Click to expand...
Click to collapse
You need to flash all the partitions.
motorola actually agreed send me a new one despite what i did so all is good
Hello everybody i have a moto g XT1032 16 gb, bought on amazon. after unlocking bootloader and rooting my device, i used a guide on youtube (Convert Moto G (XT1032) to a Google Play Edition) to try the gp edition .... i updated to kitkat 4.4.4 and after that i received the update to lollipop 5.0.1, i updated it but now my device is stuck on bootloop
please someone help me!!
Can you give us more details?
Like if this is really a bootloop (in wich you would see that white image with an exclamation mark for a loooong time) or if you just can't switch your phone on?
I've read about it and, in a situation like yours, the phone usually bricks...
______________________________________
Edit:
When it happened to me, I did the following:
Download and execute the .bat of this topic after installing the phone drivers.
http://forum.xda-developers.com/moto-g/general/guide-xt1033-downgrade-lollipop-5-0-to-t2969729
After this, my phone went to the GPE but it could not flash an stock rom. Than, I did this:
forum.xda-developers.com/ moto-g/general/guide-moto-g-xt1033-android-5-0-lollipop-t2979623
Follow this steps exactly the way its written and it should work.
BobDiaz said:
Can you give us more details?
Like if this is really a bootloop (in wich you would see that white image with an exclamation mark for a loooong time) or if you just can't switch your phone on?
I've read about it and, in a situation like yours, the phone usually bricks...
______________________________________
Edit:
When it happened to me, I did the following:
Download and execute the .bat of this topic after installing the phone drivers.
forum. xda-developers. com/ moto-g/general/ guide-xt1033-downgrade-lollipop-5-0-to-t2969729
After this, my phone went to the GPE but it could not flash an stock rom. Than, I did this:
forum. xda-developers. com/ moto-g/general/guide-moto-g-xt1033-android-5-0-lollipop-t2979623
Follow this steps exactly the way its written and it should work.
Click to expand...
Click to collapse
Thanks for your reply, basically is stuck on the boot with the google logo and a lock unlocked that i think it's for the unlocked bootloader..And when I power off the device by pressing for a long time the power button, after 2/3 seconds it reboot automatically....
now i'll try with the guides you gave me! I hope it will works
------------------------------------------------------------------------------
Edit: I did execute the .bat file and it did work! Thank you so much! now,i can't understand the second link you gave me... do i have to do that process' or it's fine like this? and now if I download the lollipop update, am i supposed to have the same problem?
stechiocca said:
Edit: I did execute the .bat file and it did work! Thank you so much! now,i can't understand the second link you gave me... do i have to do that process' or it's fine like this? and now if I download the lollipop update, am i supposed to have the same problem?
Click to expand...
Click to collapse
When you say "it work", did you mean that you can boot normally or that you can flash any rom that you wish? Or you didn't try that? The second link helped me because I couldn't flash any rom except GPE's (the partition table of these are different). If you wish to revert to your stock rom, you'll need to do as the second tutorial said.
I am now with an 5.0.1 Lollipop running well.
Please, give-me a feedback of your situation.
:good:
BobDiaz said:
When you say "it work", did you mean that you can boot normally or that you can flash any rom that you wish? Or you didn't try that? The second link helped me because I couldn't flash any rom except GPE's (the partition table of these are different). If you wish to revert to your stock rom, you'll need to do as the second tutorial said.
I am now with an 5.0.1 Lollipop running well.
Please, give-me a feedback of your situation.
:good:
Click to expand...
Click to collapse
So, first of all, now I can only boot normally and use it as gpe 4.4.4... This morning I received the lollipo 5.0.1 update, I did it but when it was at half of the installation, it stopped and there was the little android with an "ERROR" message.. if you want I can attach a photo with the error, so you may know how to solve (I did it when I had the stock recovery)... Now I tried to flash a ROM, so I put the CWM and rebooted into recovery, but when I tried ti install zip from SD card it said me "error: can't mount /sdcard" (I had this problem already when I used the guide to convert into gpe) So now what I have to do? I would like to try Lollipop, and I would like also to be able to flash any rom whenever I want!
--------------------------------
Edit: I just attached a photo of the problem so may be you can understand what happens!
stechiocca said:
So, first of all, now I can only boot normally and use it as gpe 4.4.4... This morning I received the lollipo 5.0.1 update, I did it but when it was at half of the installation, it stopped and there was the little android with an "ERROR" message.. if you want I can attach a photo with the error, so you may know how to solve (I did it when I had the stock recovery)... Now I tried to flash a ROM, so I put the CWM and rebooted into recovery, but when I tried ti install zip from SD card it said me "error: can't mount /sdcard" (I had this problem already when I used the guide to convert into gpe) So now what I have to do? I would like to try Lollipop, and I would like also to be able to flash any rom whenever I want!
--------------------------------
Edit: I just attached a photo of the problem so may be you can understand what happens!
Click to expand...
Click to collapse
So, like I said above... Just follow the second link.
The first one give you a temporary solution. It main objective is restore the capacity of mounting the partitions and booting into /system.
The second one open your horizons again, letting you decide which rom you will install. Just follow this and you'll can feel the sweetness of the Lollipop!
DO NOT try to install ANY actualizations over the TEMPORARY GPE edition. If you want do go back to GPE, do the second tutorial before.
Gimme your feedback and click ThankYou if it was usefull!
Nice wood bench, by the way.
:good:
BobDiaz said:
So, like I said above... Just follow the second link.
The first one give you a temporary solution. It main objective is restore the capacity of mounting the partitions and booting into /system.
The second one open your horizons again, letting you decide which rom you will install. Just follow this and you'll can feel the sweetness of the Lollipop!
DO NOT try to install ANY actualizations over the TEMPORARY GPE edition. If you want do go back to GPE, do the second tutorial before.
Gimme your feedback and click ThankYou if it was usefull!
Nice wood bench, by the way.
:good:
Click to expand...
Click to collapse
Ok i'm downloading the necessary files ... just two last questions before I do this, cause i'll wait for your answer before starting doing everything... 1) Will I lose all userdata? obviously I'm going to backup my data but ... am I going to lose my file and data?
2) will it work even if my original software was Retail DE?
and finally, thank you for the help, I'm going to click thank you even if it doesn't work (hope not obviously ), cause you were very helpful
I've got the same problem after trying to convert my Moto G to Google Play Edition (worked fine up to 4.4.4), then I wanted to install Android 5.0.1 OTA and ended in the Reboot Loop.
I followed the first link and was able to get 4.4.4 working again. Then I tried to continue with the second link to get the chance to update later on 5.0.1, but everytime I wanted to run the command "mfastboot flash system system.img_sparsechunk.0" my Moto G in Fastboot alerts "File Size too large". Is there a way to get an 4.4.4 which enables me OTA Update to 5.0.1?
stechiocca said:
Ok i'm downloading the necessary files ... just two last questions before I do this, cause i'll wait for your answer before starting doing everything... 1) Will I lose all userdata? obviously I'm going to backup my data but ... am I going to lose my file and data?
2) will it work even if my original software was Retail DE?
and finally, thank you for the help, I'm going to click thank you even if it doesn't work (hope not obviously ), cause you were very helpful
Click to expand...
Click to collapse
Wel... The answers:
1) Yes. You'll loose all your user data. One of the steps during the installation of any room is erase all the cache partitions and the userdata. That way, you can prevent any compatibility issues.
2) You phone will "forget everything about it's past", and will "think" that it is Brazilian now. If you don't like it, try downloading an ADB compatible DE rom. But, in my opinion, the Lollipop is way better than the Kit Kat. Unless you need the Xposed Modules.
Cheers!
Merry Christmas! :laugh:
---------- Post added at 01:30 AM ---------- Previous post was at 01:19 AM ----------
redbull93 said:
I've got the same problem after trying to convert my Moto G to Google Play Edition (worked fine up to 4.4.4), then I wanted to install Android 5.0.1 OTA and ended in the Reboot Loop.
I followed the first link and was able to get 4.4.4 working again. Then I tried to continue with the second link to get the chance to update later on 5.0.1, but everytime I wanted to run the command "mfastboot flash system system.img_sparsechunk.0" my Moto G in Fastboot alerts "File Size too large". Is there a way to get an 4.4.4 which enables me OTA Update to 5.0.1?
Click to expand...
Click to collapse
Did you did everything like said in the tutorial? Well, if yes, I suggest trying to do as the first link before. That way, all the partition table will be in the correct place.
Give us a feedback!
Cheers!
@BobDiaz do you think i should also erase dalvik cache? because i do everything step by step but it does remain in bootloop with the google logo ....
Let me just understand:
Did you try the first tutorial again or you are in the second for the first time?
You ALWAYS need to erase your cache partitions. Doing a clean installation always prevent bugs and incompatibility issues.
I'll ask for photos again. Show me, if possible, the step-by-step; Or upload a video on youtube.
Cheers!
BobDiaz said:
Did you did everything like said in the tutorial? Well, if yes, I suggest trying to do as the first link before. That way, all the partition table will be in the correct place.
Give us a feedback!
Cheers!
Click to expand...
Click to collapse
Thanks for your answer! I tried to do everything as described, the first tutorial worked fine. Then I wanted to flash the Brazilian kitkat image image with fastboot like described in the second tutorial. While flashing the phone dropped the error notice "Image File Size too Large" while flashing system.img_sparsechunk.0, system.img_sparsechunk.1 and system.img_sparsechunk.2. I was able to finish the further steps but after rebooting the bootloader the Moto G was back in Boot Loop.
Can I do the second part of this tutorial (transfering moto g brazilian update to the phone and apply the update from sd card) also with the image of the first tutorial? How does this work?
redbull93 said:
Thanks for your answer! I tried to do everything as described, the first tutorial worked fine. Then I wanted to flash the Brazilian kitkat image image with fastboot like described in the second tutorial. While flashing the phone dropped the error notice "Image File Size too Large" while flashing system.img_sparsechunk.0, system.img_sparsechunk.1 and system.img_sparsechunk.2. I was able to finish the further steps but after rebooting the bootloader the Moto G was back in Boot Loop.
Can I do the second part of this tutorial (transfering moto g brazilian update to the phone and apply the update from sd card) also with the image of the first tutorial? How does this work?
Click to expand...
Click to collapse
Actually, you can't.
You can only apply UPDATES to the rom it was meant to be. You cannot apply an Lollipop Update made to an 4.4.4 Retail-BR to an GPE, even if it was an 4.4.4. It will bug the partition table, leading your device to bootloop.
If you've already tried to do as the second tutorial said more than one time, following all the steps, and it still is in bootloop, i recommend you to try searching for a alternative.
Give us the feedback anyway!
Cheers!
Here are some pictures of the error that occurs during flashing Kitkat 4.4.4 like it is described in the second tutorial.
Before, I launched the first tutorial and got a running 4.4.4 on my Moto G.
Image 1: State after entering "mfastboot flash system system.img_sparsechunk.0"
Image 2: Feedback on the Windows console after entering "mfastboot flash system system.img_sparsechunk.0"
Image 3: State after entering the last "flash system .. " command
redbull93 said:
Here are some pictures of the error that occurs during flashing Kitkat 4.4.4 like it is described in the second tutorial.
Before, I launched the first tutorial and got a running 4.4.4 on my Moto G.
Image 1: State after entering "mfastboot flash system system.img_sparsechunk.0"
Image 2: Feedback on the Windows console after entering "mfastboot flash system system.img_sparsechunk.0"
Image 3: State after entering the last "flash system .. " command
Click to expand...
Click to collapse
You may need to flash gpt.bin from 4.4.4 (it is in the 4.4.4 flashable). This will create a new correctly sized partition table.
Also, make sure you are using the mfastboot to flash (a.k.a motorola fastboot) and not the Google fastboot.
This is probably a partition table error.
Give us the feedback!
=]
________________________________________
I've seen this in other topic:
http://forum.xda-developers.com/moto-g/general/guide-restore-moto-firmware-gpe-t2914884
BobDiaz said:
You may need to flash gpt.bin from 4.4.4 (it is in the 4.4.4 flashable). This will create a new correctly sized partition table.
Also, make sure you are using the mfastboot to flash (a.k.a motorola fastboot) and not the Google fastboot.
This is probably a partition table error.
Give us the feedback!
=]
________________________________________
I've seen this in other topic:
http://forum.xda-developers.com/moto-g/general/guide-restore-moto-firmware-gpe-t2914884
Click to expand...
Click to collapse
I can't find the gpt.bin file, probably this is why i'm getting "image is too large" error... can you please explain to where i can find it??
stechiocca said:
I can't find the gpt.bin file, probably this is why i'm getting "image is too large" error... can you please explain to where i can find it??
Click to expand...
Click to collapse
I could not upload here in XDA the gpt.bin that I've used.
Try catching the one that comes with any ADB flashable rom (it is called "gpt.bin").
Try the stock from your country.
BobDiaz said:
I could not upload here in XDA the gpt.bin that I've used.
Try catching the one that comes with any ADB flashable rom (it is called "gpt.bin").
Try the stock from your country.
Click to expand...
Click to collapse
hey, how are you? i'm really happy because it finally worked! I just had to "mfastboot flash partition gpt.bin" to make it works and i didn't get the "image is too large" problem... now i'll do the second part of the second guide hope it will work!! thank you a lot @BobDiaz
Excellent.
Try the other tutorial and tell me how did it go.
@BobDiaz Now i'm currently running correctly lollipop 5.0 brazil en BR, am i able to install a custom recovery and flash any rom whenever i want?