Database Info

[Q] How to flash stock unbranded firmware?

Hey guys,
Can someone post a step by step "for dummies" guide to flashing the stock unbranded firmware to over right the UK Tesco firmware?
I've already downloaded the unbranded UK RETAIL firmware and unlocked my phone to use in other networks, that's as far as I've got.
Not looking to root or anything else, just to apply the stock unbranded firmware so that I can get future updates from Motorola and not Tesco.
Thanks.

You need to unlock the bootloader, then either use RSD Lite or fastboot flash the images in the archive.

Give that, from the FAQ, the 'adb' access seems to work with the Moto G would the 'adb sideload' method not work? I assume this would avoid the need to unlock the bootloader.

Rusty! said:
You need to unlock the bootloader, then either use RSD Lite or fastboot flash the images in the archive.
Click to expand...
Click to collapse
Any chance for a step by step? And is this a confirmed working method?

Ydnaroo said:
Give that, from the FAQ, the 'adb' access seems to work with the Moto G would the 'adb sideload' method not work? I assume this would avoid the need to unlock the bootloader.
Click to expand...
Click to collapse
No. Sideload is for OTA updates. Completely different scenario.

Rusty! said:
No. Sideload is for OTA updates. Completely different scenario.
Click to expand...
Click to collapse
Ah! Of course. Brain fade here.

failed system.img when flashing unbranded stock
I have attempted to flash the stock unbranded firmware but am having no succes
The fastboot instructions given by Motorola website are as follows:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
Click to expand...
Click to collapse
Although I'm guessing that may be for the motox as the .xml included in the MotoG zip is as follows:
<?xml version="1.0"?>
-<flashing>-<header><phone_model model="QC8x26_CFC"/><software_version version="falcon_retgb-user 4.3 14.10.0Q3.X-76-LGG-8 54 release-keysMSM8626BP_1032.3051.51.00R"/><sparsing max-sparse-size="268435456" enabled="true"/>-<interfaces><interface name="AP"/></interfaces></header>-<steps interface="AP"><step MD5="173f47c2b411e291f8b0f512b8935190" filename="gpt.bin" partition="partition" operation="flash"/><step MD5="a2a1c181283543186f7ef069a9f63374" filename="motoboot.img" partition="motoboot" operation="flash"/><step MD5="187908e994f5b42710d13dbb5126d6d2" filename="logo.bin" partition="logo" operation="flash"/><step MD5="c99ebf47655a7609f10a8673ea229b72" filename="boot.img" partition="boot" operation="flash"/><step MD5="f79ca6436a8214fc7728dd927bd16898" filename="recovery.img" partition="recovery" operation="flash"/><step MD5="28ed691836a16e09be1edb7736086a49" filename="system.img_sparsechunk.0" partition="system" operation="flash"/><step MD5="9a188eb562f2abf336b66d1db53ab1f1" filename="system.img_sparsechunk.1" partition="system" operation="flash"/><step MD5="6a6ca5174610c48a855a7d16be75f948" filename="system.img_sparsechunk.2" partition="system" operation="flash"/><step MD5="b298426137783b6163fcda3621bed159" filename="NON-HLOS.bin" partition="modem" operation="flash"/><step partition="modemst1" operation="erase"/><step partition="modemst2" operation="erase"/><step MD5="73941708b28eb41f54b7c2326feec38a" filename="fsg.mbn" partition="fsg" operation="flash"/><step partition="cache" operation="erase"/><step partition="userdata" operation="erase"/></steps></flashing>
Click to expand...
Click to collapse
This seems to work via fastboot untill I get to the system.img files, they all fail when I try to flash them in order, or if I just try to flash one system.img as a whole.
I have also tried using the RSD tool, the phone is recognised when plugged in & booted up normally, after you select the .xml & click start it reboots to fastboot then can no longer see the device so the flash fails.
Unable to get the tool to see the phone if I manually reboot to fastboot first.
Any Ideas? Im guessing that manually flashing via fastboot is the only way, but cant get that 3 part system.img to install
>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.047s
Click to expand...
Click to collapse

Have you gone through the bootloader unlock process?

Rusty! said:
Have you gone through the bootloader unlock process?
Click to expand...
Click to collapse
Yes by following the steps on the Motorola website.
I have that annoying white warning screen now every time I reboot

How about adb sideload? Shouldnt it work just like on nexus devices? Just guessing, dont own the phone... Yet
Sent from my LG-P760 using xda app-developers app

N00BY0815 said:
How about adb sideload? Shouldnt it work just like on nexus devices? Just guessing, dont own the phone... Yet
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
Coming from a nexus, I thought that also, but I'm sure on another thread it is mentioned that ADB sideload only applies to OTA update files.
I tried pushing the whole zip to the phone but as expected it did nothing.
Fastboot flash should work but the bootloader won't give permission so something isn't right.
Although on the instructions from motorola website it says not to use android fastboot, but use RSD tool instead. I have 2 potential issus with that #1 the software itself hasn't been updated to support the MotoG or #2 it wont work with my 64bit copy of windows 7.

You need too bit the phone into BP Tools mode from fastboot for RSD Lite if you haven't been

Rusty! said:
You need too bit the phone into BP Tools mode from fastboot for RSD Lite if you haven't been
Click to expand...
Click to collapse
Yep, tried that the 1st time you posted it, still no luck.
I have noticed that after every reboot the usb debugging has switched itself off, could this be causing the permission problem?

Paul over at Modaco has created a root tool (says so on his twitter).
not sure if that will be any help in applying a stock Retrail rom on the Tesco phones. he also says RSD should work?
hope you guys can figure it out .

TeamKilo said:
Hey guys,
Can someone post a step by step "for dummies" guide to flashing the stock unbranded firmware to over right the UK Tesco firmware?
I've already downloaded the unbranded UK RETAIL firmware and unlocked my phone to use in other networks, that's as far as I've got.
Not looking to root or anything else, just to apply the stock unbranded firmware so that I can get future updates from Motorola and not Tesco.
Thanks.
Click to expand...
Click to collapse
Where did you download it from?

he's in the process of uploading it. called Superboot?

The Jones said:
Where did you download it from?
Click to expand...
Click to collapse
Moto G aka Falcon aka Motorola G (XT1032, XT1033) firmwares
http://sbf.droid-developers.org/falcon/list.php
---------- Post added at 04:20 PM ---------- Previous post was at 03:35 PM ----------
seapoint said:
Moto G aka Falcon aka Motorola G (XT1032, XT1033) firmwares
http://sbf.droid-developers.org/falcon/list.php
Click to expand...
Click to collapse
Code:
Motorola G (XT1032, XT1033)
Back
Size MD5 Carrier File
382.6 MiB 2E5FADFE1F8DE917AF0ABE6B9610AEC1 O2 Germany O2-DE_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
398.7 MiB 18394D6F7268A9D489CFCFAE3B63E803 O2 Great Britain O2SL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
382.6 MiB BD4BA4AE781BDB3DE20FD53D185E8C2C Retail Germany RETAIL-DE_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
394.1 MiB DA99BD447878CDF35E7D2929E8E2A61E Retail French RETAIL-FR_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
397.9 MiB 2D45BDDDA22C46EF4C4023B78F9EE172 Retail British RETAIL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF_svc.xml.zip
398.7 MiB 1B5988BD4CDB676E217F87891AB4667F Tesco Great Britain TESCOSL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
382.6 MiB 12B83CD9B0F945C9D25881843AC50AC8 SFR France VODAFONE-DE_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.xml.zip
396.7 MiB F69CE3807C2FEE310987F83144E8CABC SFR France VODAFONESL-FR_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF_v2.xml.zip
409.2 MiB 9E782FA758557C526599F723E5A33F69 Claro Brazil fastboot_falcon_amxbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_43_release-keys-cid12-AmericaMovil_BR.tar.gz
409.1 MiB 3768338F742347A22DF8568B4B927449 Claro Brazil fastboot_falcon_amxbr_user_4.3_14.10.0Q3.X-76-LCG-8_53_release-keys-cid12-AmericaMovil_BR.tar.gz
403.4 MiB 1B4D1C455C16D2526D08D117B15C3EA6 Telcel Mexico fastboot_falcon_amxmx_user_4.3_14.10.0Q3.X-76-LCG-8-1_1_release-keys-cid12-AmericaMovil_MX.tar.gz
409.2 MiB AB46415C9D344B45F7954ADD834BC215 OI Brazil fastboot_falcon_oibr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_57_release-keys-cid12-Oi_BR.tar.gz
409.2 MiB 4C194E4FCBF508743EE7D5309281A0AE Retail Brazilian fastboot_falcon_retbr_ds_user_4.3_14.10.0Q3.X-76-LCG-8_60_release-keys-cid12-Brasil_BR.tar.gz
409.1 MiB FA7B72E00EB3141E8B614C2022FBB9CB Retail Brazilian fastboot_falcon_retbr_user_4.3_14.10.0Q3.X-76-LCG-8_41_release-keys-cid12-Brasil_BR.tar.gz
396.6 MiB E8580CDCCB9E669D5CA1ECA8B6D4F9DF Movistar Chile fastboot_falcon_tefcl_user_4.3_14.10.0Q3.X-76-LCG-8_53_release-keys-cid12-Movistar_CL.tar.gz
396.6 MiB 38BE1E4EAA8A938CE78DB7B2678B0481 Movistar Peru fastboot_falcon_tefpe_user_4.3_14.10.0Q3.X-76-LCG-8_53_release-keys-cid12-Movistar_PE.tar.gz
We have 6.22 GiB of firmwares for Motorola Motorola G.
Actually, it seems the South American firmwares are pachaged , and named, differently. They're specifically labelled beginning with fastboot, and the archives let you expand to a directory giving you a single image for system.img The only one of interest to me is Brazil - I wonder will the Brazil system image work instead of the GB, FR or DE retail devices. If we get root I suppose we can edit build prop.
There has to be a way of concatenating the system images in the European retail images?
I wonder is this

jusumgeezer said:
Coming from a nexus, I thought that also, but I'm sure on another thread it is mentioned that ADB sideload only applies to OTA update files.
I tried pushing the whole zip to the phone but as expected it did nothing.
Fastboot flash should work but the bootloader won't give permission so something isn't right.
Although on the instructions from motorola website it says not to use android fastboot, but use RSD tool instead. I have 2 potential issus with that #1 the software itself hasn't been updated to support the MotoG or #2 it wont work with my 64bit copy of windows 7.
Click to expand...
Click to collapse
I am wondering if you need to use the Motorola version of fastboot which is different to the normal Android one. Sorry, I dont have a link to it, but I think it is in the Moto X section somewhere.

The Jones said:
I am wondering if you need to use the Motorola version of fastboot which is different to the normal Android one. Sorry, I dont have a link to it, but I think it is in the Moto X section somewhere.
Click to expand...
Click to collapse
The Motorola version is in a "Windows" folder in the Brazil firmware download!

heres root http://www.modaco.com/topic/366771-superboot-moto-g-root-solution/

[GUIDE] Flash Official US Global Firmware to European/Internationl devices

So as you already know the KitKat update started rolling for our beloved Moto G - but sadly for the moment only for those with the US Global / US GSM firmwares.
So first thing first you need to do is UNLOCK THE BOOTLOADER (guide here) and download the following files:
Drivers: http://d-h.st/5j0 or install Motorola Device Manager
Firmware: http://sbf.droid-developers.org/download.php?device=14&file=127 (US Global) or http://sbf.droid-developers.org/download.php?device=14&file=121 (US GSM aka for T-Mobile aka for AWS networks)
Minimal ADB & Fastboot: https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing
mfastboot: http://dc342.4shared.com/download/i...&dsid=3oh7jy.ce197763503e738750fd87149655184b
1. Enable USB Debugging on the device and Install the drivers accordingly to the OS version you have - either x86 for 32bits or x64 for 64bits
2. Install Minimal ADB and Fastboot
3. Extract mfastboot.exe to the folder where you installed Minimal ADB and Fastboot
4. Now in the same folder where you installed Minimal ADB and Fastboot extract files from the firmware folder.
5. Start Minimal ADB and Fastboot using shortcut created or py_cmd.exe
6. Connect the device via USB cable and in the cmd window that opens type
Code:
adb reboot-bootloader
7. Your device should reboot in Bootloader now.
8. While in Bootloader paste the following lines one by one, and be sure you get an OKAY after each one (some bootloader errors may appear, ignore them)
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk1
mfastboot.exe flash system system.img_sparsechunk2
mfastboot.exe flash system system.img_sparsechunk3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
9. You should now be rebooted in the official US firmware.
10. Wait for the OTA update to come OR flash the official OTA update.zip - US Global is here (thanks to @ZealotRush) and US AWS is here (thanks to @antiquezip) OR if you are rooted and with CWM you can flash the REPACK 4.4 KitKat system here (thanks to @josalaito)
my first guide, hopes everything goes well. I would love some feedback from those who tries this - as it worked perfect for me

Did mobile data still work after you flashed it ? Did you leave the UK radio
Sent from my XT1032 using Tapatalk

I had to unlock the bootloader of my Telcel Moto G to flash the US Retail, with the locked bootloader doesn't let me flash the boot and the system files...

kyler084 said:
Did mobile data still work after you flashed it ? Did you leave the UK radio
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Yes, my data connection works.
My device is a retail.de version.

joel_sinbad said:
I had to unlock the bootloader of my Telcel Moto G to flash the US Retail, with the locked bootloader doesn't let me flash the boot and the system files...
Click to expand...
Click to collapse
But did it worked? Si funciona con el bootloader desbloqueado?
Sent from my XT1032 using Tapatalk

thanks for the guide, did work like a charm on my European retail model. everything works perfectly, including FM-radio.
No OTA update yet, but the FW change worked.

Do you really need to unlock the bootloader?

xmattjus said:
If you want to change it back to default (in my case retail-uk) we just need to flash with the same process the previous firmware, right?
Click to expand...
Click to collapse
Even easier, as the European firmwares I tested all have a flash.bat that flash all the things automatically - you just need to reboot in bootloader and double-click a file in Windows

If i flash the us gsm firmware on the global us model will i get the other bands

Kfire21 said:
If i flash the us gsm firmware on the global us model will i get the other bands
Click to expand...
Click to collapse
US firmware presumably has the same config as the European ones. However, after flashing I can't get HSPA+ but only 3G.

darkeingel said:
US firmware presumably has the same config as the European ones. However, after flashing I can't get HSPA+ but only 3G.
Click to expand...
Click to collapse
But would it then work on T mobiles network aws 1700/2100

Kfire21 said:
But would it then work on T mobiles network aws 1700/2100
Click to expand...
Click to collapse
Theres an AWS retail firmware linked in the guide too, especially for T-Mobile

darkeingel said:
Theres an AWS retail firmware linked in the guide too, especially for T-Mobile
Click to expand...
Click to collapse
So you're saying if have the global gsm version and flash the t mobile firmware from the post, I can then use it on T-mobiles aws network

Kfire21 said:
If i flash the us gsm firmware on the global us model will i get the other bands
Click to expand...
Click to collapse
No you can't do that the phones have different model numbers.

Kfire21 said:
So you're saying if have the global gsm version and flash the t mobile firmware from the post, I can then use it on T-mobiles aws network
Click to expand...
Click to collapse
I can't confirm that, as I didn't try but it should be working.
The official specs says - Networks: GSM (850/900/1800/1900 MHz); UMTS (850/900/1700/1900/2100 MHz); CDMA (850/1900 MHz) the code numbers from T-Mobile version and Global US does not differ - so my guess that the firmware is the only thing that stands out between you and AWS network connection - I may be wrong tho'

darkeingel said:
I can't confirm that, as I didn't try but it should be working.
The official specs says - Networks: GSM (850/900/1800/1900 MHz); UMTS (850/900/1700/1900/2100 MHz); CDMA (850/1900 MHz) the code numbers from T-Mobile version and Global US does not differ - so my guess that the firmware is the only thing that stands out between you and AWS network connection - I may be wrong tho'
Click to expand...
Click to collapse
Someone test it out please, that would be fantastic if it works.

Can I do this in a Telcel(Mexico) motorola g?, Someone in Canada that already did this? (telus, bell bla bla bands are compatible with Mexico)

Thunderwrath said:
Can I do this in a Telcel(Mexico) motorola g?, Someone in Canada that already did this? (telus, bell bla bla bands are compatible with Mexico)
Click to expand...
Click to collapse
I can confirm this working on a Telcel Mexico Moto G

frijolito18 said:
I can confirm this working on a Telcel Mexico Moto G
Click to expand...
Click to collapse
Did you have to unlock the bootloader?

darkeingel said:
The official specs says - Networks: GSM (850/900/1800/1900 MHz); UMTS (850/900/1700/1900/2100 MHz); CDMA (850/1900 MHz) the code numbers from T-Mobile version and Global US does not differ - so my guess that the firmware is the only thing that stands out between you and AWS network connection - I may be wrong tho'
Click to expand...
Click to collapse
I think it should work on all the Single sim Moto Gs (Carrier locked too) since hardware is the same al across (including bands)

[TESTED][Downgrade][xt1022] 5.0.x to 4.4.4 stock firmware

FOR XT 1022 ONLY
Step 1> Download xt 1022 stock 4.4.4 firmware.
Step 2> Extract it to a folder on your PC
Step 3> Extract mfastboot and adb tools in the same folder.
Step 4> put your phone in bootloader mode.
Step 5> connect via USB cable to PC
Step 6> Now start flashing following lines in command prompt(shift+right click)
Or
Just run the given 5.0.2 to 4.4.4.bat file(after extracting the zip provided in our folder)
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
AND u will be running stock kitkat 4.4.4....
DOWNLOADS
Stock firmware link..
https://docs.google.com/uc?id=0B05Crz57q4zgY2lWUE9KZjlGeVU&export=download
CREDITS: XDA
prince.d.emperor
Final verdict: we are just not flashing the gpt, motoboot, logo for avoiding bootloader downgrade....which will be suicidal for device.......otherwise the procedure is same as flashing stock firmware....​

thanks for the info!
---------- Post added at 03:10 PM ---------- Previous post was at 02:57 PM ----------
love4chat said:
thanks for the info!
Click to expand...
Click to collapse
can we use this process with minimal adb n fastboot?

love4chat said:
thanks for the info!
---------- Post added at 03:10 PM ---------- Previous post was at 02:57 PM ----------
can we use this process with minimal adb n fastboot?
Click to expand...
Click to collapse
Yes
Sent from my Moto G using XDA Free mobile app

Quick question: If the device came with 4.4.4, and I am running a custom ROM now, would it be safe to flash the bootloader?

u-wot-m8 said:
Quick question: If the device came with 4.4.4, and I am running a custom ROM now, would it be safe to flash the bootloader?
Click to expand...
Click to collapse
Completely safe:thumbup:
Just to be safe....have you got any screen flicker during boot???(after installing 5.0 customs)
If not then you are on kitkat bootloader..and ready to flash full stock firmware.....
If yes then you have to follow above procedure
Sent from my Moto G using XDA Free mobile app

hi bro i will follow your steps but it will not work for me for downgrade 5.02 to 4.4.4
coz my device have prob with 4.4.4 restart prob from power on button
So plz if u have any other steps for restart solution
Br,....
omkar3268

omkar3268 said:
hi bro i will follow your steps but it will not work for me for downgrade 5.02 to 4.4.4
coz my device have prob with 4.4.4 restart prob from power on button
So plz if u have any other steps for restart solution
Br,....
omkar3268
Click to expand...
Click to collapse
Just enable advanced reboot in developer options.....if u r on any custom ROM
Then u can reboot directly to boot loader.....by long pressing power and selecting...
If you are rooted then use
Terminal emulator app
In that type this....
reboot bootloader
And press enter
Sent from my Moto G using XDA Free mobile app

Deleted
Sent from my Moto G using XDA Free mobile app

can restore be done through old CWM backup?
i have and old CWM backup of 4.4.4. im running on 5.0.2
can the old backup be restored without any issues?

anil2705 said:
i have and old CWM backup of 4.4.4. im running on 5.0.2
can the old backup be restored without any issues?
Click to expand...
Click to collapse
If you have installed only custom ROMs of 5.0.2....then its ok to flash 4.4.4 backup...
If you have installed stock ota 5.0.2.....then u shouldn't......
Sent from my Moto G using XDA Free mobile app

4.4.2?
Can I do the same with a 4.4.2 firmware image?

kumarsid7 said:
Can I do the same with a 4.4.2 firmware image?
Click to expand...
Click to collapse
Yes
Sent from my Moto G using XDA Free mobile app

I am using this to downgrade from 5.0.2 official lollipop preview to 4.4.4, but I am getting an error:
(bootloader) Preflash validation failed
FAILED (remote failure)
Why? I can't understand.

Did it manually instead of using .bat, and the radios don't work for either of my SIM cards. The SIMs are listed as "disabled" under "Dual SIM settings". Tried to turn on the radio via the hidden menu to no avail. Flashing the modem again didn't help :/
Any help please?

5.0.2 was install in my mobile and its was working gr8 but from two day i facing wifi on/off problem i cant turn it on, so i downgrade with your batch file and now i have 4.4.4 stock and wifi working fine. thanks for your help and post,
i want to upgrade 5.0.2 or 5.1 any help ?
thanks again

This downgrade will also work if I am currently on lollipop 5.1 (unrooted and bootloader locked) ?

I know the post says XT1022, but I wonder if this would work with XT1021 too? The only difference between the 2 phones is that mine (XT1021) is not dual-sim.

worked for me

I'm on CM 12.1 Lollipop (5.1.1)...
Is it ok to try it?

With your cmd line flashing sequence guide I easily downgraded from CM12 (5.1.1) to stock KitKat mate - many thanks for your effort!

[Q] Back to 4.4.4 from 5.0.2 - Moto G 2013

hello everybody
my english is not so good, i try to describe and hope you understand what i mean.
ok let´s go
i updated my moto g 2013 (with open bootloader but without root) from original stock 4.4.4. manually to 5.0.2 - Not OTA. i did it with fastboot.
i don´t like 5.0.2 because the phone has to many bugs and it won´t be better. bad 3g and sometimes i don´t have any signal, play store services are shut down very often, can´t open playstore because my account is not available and yesterday all my apps from homescreen were gone......and so on.....
now i want to have 4.4.4 back again and i hope you can help me.
what i have is the original stock 4.4.4 (XT1032_RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml)!
in this post, there are only BR, FR, MX, GB Firmware http://forum.xda-developers.com/moto-g/general/restore-to-kitkat-lollipop-moto-g-t3011553
1. what about my firmware, does it works too with this method?
so, here are so many posts about downgrade/restore..... just give me a link or post a description here or something else with an easy guide please.
more questions i have
2. which is the right description, tools, downgrade for my phone? the link above?
2. i read that after downgrade to 4.4.4 the phone has a kind of line or light on the display, is that right and why the phone get this?
3. what about this here? has it something to do with this display bug or for what is this file http://forum.xda-developers.com/showpost.php?p=54103676&postcount=2
what i have to do with this file? important for downgrade?
4. is it possible to downgrade bootloader too and how?
i know here are many posts about this and don´t be angry to me that i start a new one. a friend recommend this forum and said, here are a lot of good and helpful people.
so thank you so much

I hate lollipop!!
xodbx said:
hello everybody
my english is not so good, i try to describe and hope you understand what i mean.
ok let´s go
i updated my moto g 2013 (with open bootloader but without root) from original stock 4.4.4. manually to 5.0.2 - Not OTA. i did it with fastboot.
i don´t like 5.0.2 because the phone has to many bugs and it won´t be better. bad 3g and sometimes i don´t have any signal, play store services are shut down very often, can´t open playstore because my account is not available and yesterday all my apps from homescreen were gone......and so on.....
now i want to have 4.4.4 back again and i hope you can help me.
what i have is the original stock 4.4.4 (XT1032_RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml)!
in this post, there are only BR, FR, MX, GB Firmware http://forum.xda-developers.com/moto-g/general/restore-to-kitkat-lollipop-moto-g-t3011553
1. what about my firmware, does it works too with this method?
so, here are so many posts about downgrade/restore..... just give me a link or post a description here or something else with an easy guide please.
more questions i have
2. which is the right description, tools, downgrade for my phone? the link above?
2. i read that after downgrade to 4.4.4 the phone has a kind of line or light on the display, is that right and why the phone get this?
3. what about this here? has it something to do with this display bug or for what is this file http://forum.xda-developers.com/showpost.php?p=54103676&postcount=2
what i have to do with this file? important for downgrade?
4. is it possible to downgrade bootloader too and how?
i know here are many posts about this and don´t be angry to me that i start a new one. a friend recommend this forum and said, here are a lot of good and helpful people.
so thank you so much
Click to expand...
Click to collapse
Did u find a way to revert back to kit Kat?

hey
no, sorry
i´m waiting for the answers

Just flash the 4.4.4 firmware via fastboot, using the following commands:
Code:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Use only this commands, absolutely DON'T flash gpt.bin and motoboot.bin, or you'll end bricking your device.
mfastboot download link: https://mega.co.nz/#!xgYkgI6I!E4MkiSwCm1AS4qor5xP8QTNeL-BAFZLrV9JDCIlBImM
I have successfully downgraded from 5.0.2 Retail DE to 4.4.4 Retail DE this way. The line glitch is due to a compatibility issue between kitkat kernel and lollipop bootloader, but it isn't so annoying, you only have to lock and unlock your device only once after every reboot. BTW I think that a hard reset will solve most of the problems you've faced on lollipop, I haven't experienced any of the issues you're talking about.

hello and thanks for your answer
why is there a different way for downgrade between yours and this http://forum.xda-developers.com/moto-g/general/restore-to-kitkat-lollipop-moto-g-t3011553 ???
whats the different?
and what about the adb drivers. it must be installed first, saw on a video? i don´t need it for downgrade? i have a "minimal adb+fastboot setup.exe"!
what is behind ...... don´t flash gpt.bin and motoboot.bin...?
and i did a hard reset after update to 502, but have still some bugs
sorry for all my questions, i´m a bit careful

The partition layout may be different between KK and LP; therefore, I would recommend flashing gpt.bin.
You won't be able to flash motoboot.bin because your phone probably has the 41.18 bootloader which cannot be downgraded.
When you downgrade to KK, you will see a line running from the top to the bottom of the screen. It looks like it is rippling. Don't worry, this is happening because your are running KK on a LP bootloader. To get rid of the rippling, just lock and unlock the phone using the power button.
If you flash to stock KK and run the OTA update to 5.02, the rippling will go away because you'll be running stock LP on a LP bootloader.

Hello and thanks for answer, but you say its recommend to flash GPT and the other member said DON'T. so two different answers,. What happened if i flash and don't flash???

You can try to install the ROM without flash gpt.bin.
When going from GPE to non-GPE and vice versa, gpt.bin had to be flashed.

Hey audit13
Thanks for answer but i don't understand what you mean. What is gpe ?non gpe? Vice versa? No plan, sorry

Gpe means google play edition and non gpe means non Google play edition
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
As there are many threads about downgrading
So Im very much confused
Can anyone help me with the best way
If yes then it will be needfull to me

xodbx said:
Hey audit13
Thanks for answer but i don't understand what you mean. What is gpe ?non gpe? Vice versa? No plan, sorry
Click to expand...
Click to collapse
GPE = Google Play Edition
Non-GPE = Stock ROM
GPE uses the ext4 file system for data.
Non-GPE uses f2fs for data.
Flashing GPT.bin is recommended, in my experience, when going from GPE to non-GPE and vicer versa.

audit13 said:
GPE = Google Play Edition
Non-GPE = Stock ROM
GPE uses the ext4 file system for data.
Non-GPE uses f2fs for data.
Flashing GPT.bin is recommended, in my experience, when going from GPE to non-GPE and vicer versa.
Click to expand...
Click to collapse
hello and thanks for your answers. sorry, i was sick for a few days and could not write back.
so my moto g has the google play app. is it a gpe? i have the original ....XT1032_RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml...
have to flash or not gpt.bin?
thanks again

xodbx said:
hello and thanks for your answers. sorry, i was sick for a few days and could not write back.
so my moto g has the google play app. is it a gpe? i have the original ....XT1032_RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml...
have to flash or not gpt.bin?
thanks again
Click to expand...
Click to collapse
OK guys, i did it without flashing bootloader and GPT and it works. Thanks for Helping me :good:

[ROOT]&[MAGISK]For Asus ZenPad Z10 (ZT500KL) And ZenPad 3s 10(Z500KL)

Guide to get full root access of ZT500KL and it is supposed to work on Z500KL(ZenPad 3s 10) as well.(not yet tested on the latter device.)
As we know,the Verizon modified devices are often difficult to unlock and get root access.BUT,this device ZT500KL has got a 'sister' version,which named similar called Z500KL.
The bootloader of ZT500KL is strict and of course will not boot without unlock.
HOWEVER,the Z500KL's bootloader does not seem to fully verify the signature of boot.img.
Also i found a post by Shakalaca which contains a command to allow partition flashing even without bootloader unlock on some ASUS devices.
So,here it comes the magisk.
DISCLAIMER
THIS POST IS FOR EDUCATIONAL ONLY,OUR PURPOSE IS TRYING TO FIND OUT SECURITY WEAKNESS OF THE DEVICE,AND WE ALWAYS SUGGEST THE MANUFACTUAR TO ENHANCE DATA SAFETY.
YOUR WARRANTY MAY NOW VOID
I AM NOT RESONSIBLE FOR ANY UNEXPECTED CIRCUMSTANCES,INCLUDING DATA LOSS,SOFTWARE ERROR EVEN HARDWARE DAMAGE.
REQUIREMENTS
A ZT500KL tablet,running on ZenUI version 3.3.7//3.4.3//5.4.6//5.4.7 or Z500KL
Backup all your data,including internel storage,such as your photos or movies.
aboot file of z500kl,magisk patched boot image.(All files are provided below)
Adb and fastboot driver installed
basic knowledge of shell commands
INSTRUCTIONS
IF YOUR HARDWARE IS Z500KL,please jump to step
reboot device to fastboot,plug cable and type this command to allow partition flashing
Code:
fastboot getvar sofia_support
flash aboot image of z500kl(skip this step if your device itself is z500kl):
Code:
fastboot flash aboot ww5.4.6-emmc_appsboot.mbn
reboot to bootloader again:
Code:
fastboot reboot-bootloader
in fastboot,check your tablet,the 'TARGET PROJECT 'should be z500kl,not zt500kl
allow partiiton flashing again and flash magisk patched boot image:
Code:
fastboot getvar sofia_support
fastboot flash boot boot_patched.img
unplug your cable after flashing the boot,use the volume key on your tablet to select 'factory reset',it will reboot to recovery automaticly and wipe your data.
finish the new device set up and install magisk manually,at first time magisk will ask you to download additional setup,just click download now,and your device will reboot again.
now you've got a magisk full root.
THANKS AND ACKNOWLEDGEMENTS
Shakalaca,thanks for his post for the partition flashing command. The original post was in his medium,you can search this in google[ZenPad S 8.0 (Z580CA) bootloader unlocked]
(i cant put link on xda cause i am a new user)
落落大 in CoolApk,for his work on getting the full boot image of 5.4.7 os version
IMPORTANT NOTES
As the bootloader is still locked,the device will refuse to boot without signature.if you want to modify the boot,remeber to sign it.you can sign it using your own signature.
the version of boot should be same as your os,for example if you want to root 3.3.7,flash the 3.3.7patched.the image for other version may not function well
if you are using Z500kl,you can extract the boot image from ota package from asus website,and patch the boot by yourself
All attched files:
mega.nz/#F!mrJzWIyb!ABRueM7EoRJ1hkKhRVpexg
discuss QQ group(Chinese only)(QQ群):657908957
find me in CoolAPK(酷安):建华WEI业的前HR

Thank you !!!
You are the man !!! It works perfectly bro. Thank you so much.
BTW: Device: Z500KL, Android 7, Asus Zen Ui 5.4.6 Version and Global (WW)

Mine was BRICKED following this tutorial. Can't restore system and need HELP.
Looking for a way to flash stock firmware again. ANY ideas would be graciously accepted.
Anyone want to chime in on the procedure to "sign the bootloader" or is that not strictly necessary to root+magisk?

Hi @jose tronco any luck fro Asus Z8s from Verizon to do the same thing ?

MoPhoMike said:
Mine was BRICKED following this tutorial. Can't restore system and need HELP.
Looking for a way to flash stock firmware again. ANY ideas would be graciously accepted.
Anyone want to chime in on the procedure to "sign the bootloader" or is that not strictly necessary to root+magisk?
Click to expand...
Click to collapse
which device?
---------- Post added at 12:05 PM ---------- Previous post was at 12:04 PM ----------
demonntl said:
Hi @jose tronco any luck fro Asus Z8s from Verizon to do the same thing ?
Click to expand...
Click to collapse
if getvar sofia support command valid for your device, it can be root
---------- Post added at 12:06 PM ---------- Previous post was at 12:05 PM ----------
demonntl said:
Hi @jose tronco any luck fro Asus Z8s from Verizon to do the same thing ?
Click to expand...
Click to collapse
if getvar sofia support command valid for your device, it can be root

Z8s does respond to the command, can i used the same modified files to flash ?
NC503 said:
which device?
---------- Post added at 12:05 PM ---------- Previous post was at 12:04 PM ----------
if getvar sofia support command valid for your device, it can be root
---------- Post added at 12:06 PM ---------- Previous post was at 12:05 PM ----------
if getvar sofia support command valid for your device, it can be root
Click to expand...
Click to collapse

PHP:
No ! You have to find your own rom's boot.img and modify it via magisk app. After that, you can flash this boot image via sofia support command at the fastboot mode.
You can find your own rom's boot.img at the zip file from Asus support's website.

MoPhoMike said:
Mine was BRICKED following this tutorial. Can't restore system and need HELP.
Looking for a way to flash stock firmware again. ANY ideas would be graciously accepted.
Anyone want to chime in on the procedure to "sign the bootloader" or is that not strictly necessary to root+magisk?
Click to expand...
Click to collapse
Mine was bricked too.
When ZT500KL was rooted, bootloop may happen during the first 2 or 3 boot/reboot if you change any setting or install any app.
To avoid this, just don't do anything.
Let the table reboot a few times, make sure everything works fine without bootloop.
Then, do whatever you want.
If you already got bootloop, the solution as follows.
The reason why a rooted ZT500KL can't flash stock ZT500KL firmware is that, the root process has already changed the name of the table into "Z500KL".
So, the stock firmware of ZT500KL could not be flashed.
In order the chang the name of the tablet back to ZT500KL, you have to flash the aboot of stock ZT500KL.
Here is the download link.
https://drive.google.com/file/d/1HKXHEEB3LtFqfwU9DyTFutsWQjcEtPQg/view?usp=sharing
Just download it, and flash it as the way you root.
"fastboot getvar sofia_support"
then
"fastboot flash aboot emmc_appsboot.signed.mbn"
then, reboot.
The tablet will be renamed to "ZT500KL".
Now, you can just download stock VZW 5.4.6 firmware from ASUS website, and flash it with asus flash tool.
If you still want to root your tablet, just root it again.

This is awesome! Thanks for the support! I thought this device was dead and no more development would ever be done for this.
I have the Z500KL and as soon as some ROMs come along I'm doing this. I'm also happy to help out if I can. I'm currently on the latest Japanese ROM JP_V5.4.0_20170711 (Device name is ASUS_P001, but is essentially the same as every other Z500KL and can be flashed to WW ROMS no problem)
I assume that once you have gone through these steps above, then as long as the boot image is signed (with any old signature) you can install a ROM for a higher version of Android, or are we limited to Android 7?

Hello, is there any chance you could write a step by step guide for dummies? I've rooted and flashed a hundred times, but I'm just not following some of the instructions, and others report a bricked device.

Ok where to start...to start I rooted my Zenpad and was dumb enough to use Titanium Backup to get rid of bloat and now it just sits on loading screen for the last two days...now I screwed it up really bad by erasing the system partition....I got it to recovery but won't let me flash the Z500KL firmware UL-ASUS_P00I-WW-5.4.6.0-user.zip because over newer build (See pic) is there anyway to change the firmware or the recovery (see pic) to an earlier date to install the firmware? If not in right forum please move....
SOLVED!!! Took all morning to do...used ASUS.Flash.Tool.v1.0.0.45 after changing
aboot ww5.4.6-emmc_appsboot.mbn to aboot emmc_appsboot.signed.mbn, rebooted fastboot, (DID NOT RESET and flashed ZT500KL_all_VZW_user_V3.4.3.raw. booted up to setup! Yah!!!!

This worked great on a z10 i got from China. For some reason it fails in the middle of updating to android 7 and the verizon update software doesn't work. Was wondering if I could use the update files from the z500kl?

i need a video for detail guild, please. Someone will post that on social media or youtube. My device is ZT500KL. With ZT500kl I have to do all 7 steps above, right ?
Thanks

Hello, guys! Just installed root and faced the problem: wi-fi died. It doesn't turning on and has MAC-Adress 02:00:00:00:00:00. How can I repair it? I have Z500KL with 5.3.6 firmware

Hi, I’m new here and really, really want to get rid of the Verizon firmware as apps are constantly crashing and not working well, likely driven by the Verizon garbage. I have a ZT500KL with VZW_V5.4.7_20180101, and ZenUI of 3.0. I read through the thread and have a couple questions:
1) The initial post doesn’t mention ZenUI of 3.0. Is it dangerous to try this given my version isn’t listed? If so, is there a way to update my ZenUI?
2) Being new to this, if I successfully complete the steps outlined, what do I do next in terms of the firmware? Am I right in assuming that the above steps remove all aspects of Verizon? If so, can I simply update to the latest version of Android? With Verizon gone will I be able to freely update ZenUI, as it seems mine is quite behind at this point.
Thanks for any help and guidance, I’m new to this and really just want a tablet that works properly and doesn’t crash apps constantly.

Hi,
Could anyone please share the recovery img of ZT500KL? I'd bricked mine and need it.