I followed this guide http://www.xoomforums.com/forum/non...sion/7918-updating-3-2-3-0-1-non-us-user.html to turn my UK Xoom (wifi) into a US GED so I could get the OTA ICS.
I unlocked the bootloader, flashed the boot.img but when I try to flash the system.img, it will not do it. It seems to time out and I get an error. I can flash every .img (recovery etc) except the system.img.
I have re-downloaded in case it was corrupt, but that didn't help. I have tried flashing it back to the UK version but once again it will not flash the system.img.
Now it won't boot, it sticks on the "dual core" screen.
I really cannot work out what is problem. It is like the system is still locked.
Is it possible to try and get round it by installing CWM via fastboot and then flashing a rom from recovery?
If so, will I need a UK custom ROM?
I have installed CWM and installed this http://forum.xda-developers.com/showthread.php?t=1400958
FIRST THING FIRST, THIS IS DANGEROUS. DO IT AT YOUR OWN RISK.
Myself and one other person have successfully done this. If you have success as well, please post here. What you DO NOT want to flash, and is the cause of bricks is motoboot.img that is older than what you have now. Just dont mess with it.
What you can do, is flash gpt.bin to get the partition tables re-partitioned to get you back to be able to flash roms from CWM, TWRP, Philz, etc.
That being said, this is my PERSONAL experience, and am only sharing because it got me out of GPE lollipop hell, and I was terrified of the bricks, like everyone else. I will attempt to be more clear in my OP.
I have an XT1034 that I converted to GPE to flash 5.0 Lollipop OTA and it gave me the new bootloader 41.18. I couldnt get to CM12 due to Status 7, and I could only flash 4.4.4 stock, lollipop stock, or CM11, any flashing to CM12 always gave errors about Status 7. Others have reported not being able to wipe /data or /system or mount either in any recovery. The problem is the updated partition table and here is the solution:
IF YOU DO NOT FOLLOW THIS DIRECTION YOU WILL HARD BRICK. DO NOT RUN THE BATCH FILE IN THE DOWNLOAD. IT CONTAINS 4.4.2 motoboot.img and YOU WILL BRICK. ONLY RUN THE COMMANDS LISTED BELOW!!!
ALSO DO NOT use an older gpt.bin, it must be 4.4.2 or newer!! Use the link below to get a 4.4.2 XT1034 stock rom.)
I flashed a 4.4.2 GPT.bin from this: US_retail_XT1034_KXB20.9-1.8-1.4_CFC.xml.zip (http://motofirmware.com/files/getdow...-14-cfcxmlzip/)
If you want to try the same thing, you can extract gpt.bin from the zip and run this: (ONLY!!)
Code:
fastboot flash partition gpt.bin
then download philz here: http://fs1.d-h.st/download/00145/DEw...8.7-falcon.img
rename to philz.img
fastboot flash recovery philz.img
Hold vol - and power, to reboot into recovery, then
format /system
format /data
Download the latest nightlies and gapps and push them like this:
adb push cm-10-10-1000.zip /data/media/0
Reboot into recovery, and flash cm12 and gapps.
Marcus Lemonis!
I thought it had been established flashing the KitKat Partiton Table (gpt.bin) was the cause of downgrade hard-bricking.
It would appear the 4.4.4 Partition Table is specifically the cause.
People have been hard-bricking (now have to wait for full firmware images to fix) - because they flashed the 4.4.2 image and then applied the 4.4.4 OTA Update.
Perhaps you should mention that in OP.
I don't think a gpt.bin "4.4.2 or newer" is wise advice. Please correct me if I'm wrong.
lost101 said:
I thought it had been established flashing the KitKat Partiton Table (gpt.bin) was the cause of downgrade hard-bricking.
It would appear the 4.4.4 Partition Table is specifically the cause.
People have been hard-bricking (now have to wait for full firmware images to fix) - because they flashed the 4.4.2 image and then applied the 4.4.4 OTA Update.
Perhaps you should mention that in OP.
I don't think a gpt.bin "4.4.2 or newer" is wise advice. Please correct me if I'm wrong.
Click to expand...
Click to collapse
It is possible to flash 4.4.4 gpt bin, bit it's not possible to OTA update to 4.4.4 from 4.4.2.
andogeek10 said:
It is possible to flash 4.4.4 gpt bin, bit it's not possible to OTA update to 4.4.4 from 4.4.2.
Click to expand...
Click to collapse
Exactly.
It's the same if you want come back from GPe to Retail Motorola STOCK, you need change GPe-partitions to Motorola-Partitions. There are some differents between both partitions:
GPE
Code:
'cache' -> 560,00 Mb
'system' -> 840,00 Mb
Motorola
Code:
'cache' -> 662,13 Mb
'system' -> 976,00 Mb
There is a partition with 2,28 Mb: In GPe is called 'metadata'; and in Motorola is Called 'padA'.
And there is a partition en GPE with 6,13 Mb called 'padC', but in Motorola didn't exists.
Any way, if you downgrade from LP, you don't must flash BL (motoboot.img), or you'll have a pretty brick.
updated op, I shouldnt have tried to walk anyone through that last night, i couldnt even understand my own english, apologies.
I just don't understand why peoples push 4.4.2 into phones when there is "safer" 4.4.4 that works perfectly and you must be retarded to brick phone when flashing 4.4.4 and doing anything after it. I will say for sure that 80% of hard bricks are caused by 4.4.2 android and updating to 4.4.4(which makes no sense at all) or doing anything after 4.4.2. Just. Stop. Doing. That.
Flash everything from last KITKAT except motoboot and everything will be fine.
how can I know my current bootloader version ?
P.s : ok sorry got it... it is in the bootloader mode (41.13)
http://forum.xda-developers.com/showthread.php?t=3002572
Tell me where to find the 4.4.4 stock xt1034 and I'll link it. My process works. No bricks. Sbf.droid developers is down, send me the 4.4.4 and I'll link it. It is not 4.4.2 causing bricks, it is 4.3!
Sent from my Moto G using XDA Free mobile app
The link is not able to be verified where that gpt.bin came from, that's why I linked the whole stock ROM and not just gpt.bin
Again, try it if you like, and if you don't, don't!
Sent from my Moto G using XDA Free mobile app
I am not suggesting that people flash the whole way back to 4. 4.2. I'm only saying that people need to flash the partition tables from 4.4.2 so then you can install recovery and move on to CM. Re read the op I tell you NOT to flash that rom, but to only update gpt.bin
Sent from my Moto G using XDA Free mobile app
Xt1032?
Do you think this will work for an XT1032 converted to GPE? I have been unable to flash any sort of custom recovery as of yet like it keeps on disappearing when I reboot the device and becoming stock recovery.
Fuchsie said:
Do you think this will work for an XT1032 converted to GPE? I have been unable to flash any sort of custom recovery as of yet like it keeps on disappearing when I reboot the device and becoming stock recovery.
Click to expand...
Click to collapse
Are you flashing recovery from fastboot? If you use fastboot, try flashing the recovery and using the button combo to boot into recovery from fastboot.
Do you have the 41.18 bootloader?
I have an 8 GB Telus xt1032 that I converted to GPE. While on GPE 4.4.4, I mistakenly allowed the 5.01 OTA update to install. Needless to say, it hung at the boot screen and I could do nothing.
I booted back into bootloader and noticed that my bootloader was now 41.18. I downloaded the stock Telus 4.4.4 ROM and manually flashed everything except motoboot.img (this is the bootloader image and is older than 41.18) and the phone booted without issue. I then installed TWRP and can flash pretty much any custom ROM.
I've heard it's possible to flash CM12 over Lollipop 5.0.2 official firmware. It was from 3 sources that peoples did it without problems
brainscollector said:
I've heard it's possible to flash CM12 over Lollipop 5.0.2 official firmware. It was from 3 sources that peoples did it without problems
Click to expand...
Click to collapse
It is possible but not on the GPE firmware. There are differences in the /system partition size and the update script doesn't expect this and hence the flashing fails.
audit13 said:
Are you flashing recovery from fastboot? If you use fastboot, try flashing the recovery and using the button combo to boot into recovery from fastboot.
Do you have the 41.18 bootloader?
I have an 8 GB Telus xt1032 that I converted to GPE. While on GPE 4.4.4, I mistakenly allowed the 5.01 OTA update to install. Needless to say, it hung at the boot screen and I could do nothing.
I booted back into bootloader and noticed that my bootloader was now 41.18. I downloaded the stock Telus 4.4.4 ROM and manually flashed everything except motoboot.img (this is the bootloader image and is older than 41.18) and the phone booted without issue. I then installed TWRP and can flash pretty much any custom ROM.
Click to expand...
Click to collapse
No no I have the 41.18 bootloader as it's a full conversion.
To get around the boot screen hanging I fastboot flashed a gpt.bin. Cheers for the advice though
d33dvb said:
FIRST THING FIRST, THIS IS DANGEROUS. DO IT AT YOUR OWN RISK.
Myself and one other person have successfully done this. If you have success as well, please post here. <snip>
Marcus Lemonis!
Click to expand...
Click to collapse
Finally!
It worked for me: UK Stock KK to GPE KK to GPE LP, on bootloader 41.18 and unable to flash CM12.
It didn't work exactly as you described, it only worked when I did teh following: flash stock v4.4.4 gbt.bin, reboot, flash philz, reboot to recovery, format system (unable to mount it otherwise), flash twrp, convert data from f2fs to ext4 (unable to mount it otherwise), format data, then install CM12, pagapps, and SU.
Thanks!
Does this downgrade the bootloader to 41.13? I'm on retail 4.4.4 with bootloader 41.18, tried flashing gpt.bin from 4.4.4 and it booted straight to bootloader with the message "fastboot reason: utag flash fail configured as fastboot", then I fixed it by flashing all the other files (except motoboot of course) However I'm still on 41.18..
I just want to get rid permanently of the ripple efect every time you reboot.
Motoboot.img is the bootloader file. Once on the 41.18 bootloader, you cannot flash an older bootloader.
The best method imo to flash custom ROMs on the 41.18 boot-loader is:
1) Flash the official Moto 5.0.2 firmwares for your respective devices
2) Flash the OFFICIAL TWRP 2.8.5.0
3) Wipe everything except internal storage. The first wipe will fail and the phone will reboot. Reboot again into the recovery and perform the wipe again. It will work this time.
4) Flash the ROM zip now.
PS: ADB sideload works for me but not MTP.
I flashed the newest firmware considering that it will be smoother. And now I can't even go back. Flashing the G935FXXU1BPIO, the latest update but it still produced the same error. Now, even if I go back and flash any earlier firmware, it would give me the same error "Random Reboot". Digging into deep for two days what I found that flashing any custom kernel using flashfire, would trigger the error "E cannot mount /data (Invalid argument)" in recovery. This was strange, as I was flashing the same kernel, same stock firmware and same autoroot. The recovery will always say G935FXXU1BPH6. Now, if I flash anything on flashfire, I face the same thing. Is it a bug in flashfire or anything wrong with my device? Anyone else facing this?
So I wanted to root my phone. Everything worked. Then I decided to factory reset my phone. Phone kept going in recovery mode. I wipe all (system,data,cache,dalvik) and tried to install stock rom from firmware center using RSDlite , but I couldn't. I keep getting "Failed flashing process. 3/23 flash partition "gpt.bin" "
I guess this because the stock rom is potentially downgrading the phone as there was a security update to the phone last month.
Other things I tried :
Wiped everything, tried custom rom (LineageOS) - Kept getting stuck in bootloader.
Please help
When you flash a custom rom, do you try to boot to system from the recovery? If so, boot into the bootloader right away from the recovery and select "qcom" and press the power button. This is what I have to do.
Try flashing another boot.img with a custom rom
Finally working
So, basically the problem was that the stock rom wouldn't install as my phone had been updated.
so whenever I tried to flash the stock rom using RSDlite it would fail at gpt.bin (which was the first operation).
Solution was to extract the xml.zip and edit the xml files to remove the operations that would flash gpt.bin .
Luckily the other files flashed successfully.
kuchbhinet said:
So, basically the problem was that the stock rom wouldn't install as my phone had been updated.
so whenever I tried to flash the stock rom using RSDlite it would fail at gpt.bin (which was the first operation).
Solution was to extract the xml.zip and edit the xml files to remove the operations that would flash gpt.bin .
Luckily the other files flashed successfully.
Click to expand...
Click to collapse
how do we do that to have it skip flashing gpt.bin? i tried erasing the line that said flash gpt but it still gives the same error
alexcass4 said:
how do we do that to have it skip flashing gpt.bin? i tried erasing the line that said flash gpt but it still gives the same error
Click to expand...
Click to collapse
Just use the updated firmware.
Hi all i hope i'm in the right section.
I have a T510 with stock rom T510XXU5CUF4.
I successful unlocked the bootloader (i have the message when i bott that tells me that the bootloader in unlocked).
After the bootloader unlovk i've tryied to flash the custom rom (Lineage) using tarball with odin.
The procedure says that i must flash the rom with Odin using AP.
Every time i try to flash it immediately i have a FAIL message from Odin (i've try different cables and different computers) and the result is a softbrick.
the same happen when after the bootloader unlock i try to flash twrp.
Could someone explain me why i can't flash a costum rom or twrp on this tablet?
Thanks
PdorITA said:
Hi all i hope i'm in the right section.
I have a T510 with stock rom T510XXU5CUF4.
I successful unlocked the bootloader (i have the message when i bott that tells me that the bootloader in unlocked).
After the bootloader unlovk i've tryied to flash the custom rom (Lineage) using tarball with odin.
The procedure says that i must flash the rom with Odin using AP.
Every time i try to flash it immediately i have a FAIL message from Odin (i've try different cables and different computers) and the result is a softbrick.
the same happen when after the bootloader unlock i try to flash twrp.
Could someone explain me why i can't flash a costum rom or twrp on this tablet?
Thanks
Click to expand...
Click to collapse
I can see two possibilities. First of all, the latest stock is CUJ1 and not CUF4. Two, does the custom ROM include a blank vbmeta file? You might want to follow the instructions to flash TWRP prior to flashing the ROM.
I've try with the instructions for twrp and it doesn't work too. Anything I try to flash except stock I get fail message. Maybe I should do something else? Does my bootloader looks unlocked but it is locked?
PdorITA said:
I've try with the instructions for twrp and it doesn't work too. Anything I try to flash except stock I get fail message. Maybe I should do something else? Does my bootloader looks unlocked but it is locked?
Click to expand...
Click to collapse
The first thing you need to do is flash the latest, CUJ1, stock ROM. You can use frija.exe to get it. All of the things you are trying to flash are based on that kernel. Also, you need to boot the stock ROM, connect wifi, skip the rest of the setup and enable Dev mode before trying to flash custom stuff.