Hey,
So I've been searching for a few days now in the moto g section. I can't find any guides to restore my moto g GPE US version to stock. I found somewhat of walkthrough using the moto tool but I dont' have a windows machine to run that program. Is there another way to do this? Please let me know, also if I missed a post that shows this info please reply with the link.
Thank you!
If you don't have a Windows machine, it'd be good if we knew what you do have in order to guide you properly.
Flashing back to stock on Linux is quite easy once you've got the tools set up. I would assume MacOS X is similar provided you can get a suitable fastboot or mfastboot binary. (I recommend having them in a directeory listed in your $PATH variable with proper permissions for USB so that you don't need to sudo to use them.)
If you've got no computer, but can boot in a modified recovery, it should be possible to flash the entire stock ROM with that. You wouldn't be able to relock the bootloader though, if that's something you were aiming for.
killjoydreams said:
Hey,
So I've been searching for a few days now in the moto g section. I can't find any guides to restore my moto g GPE US version to stock. I found somewhat of walkthrough using the moto tool but I dont' have a windows machine to run that program. Is there another way to do this? Please let me know, also if I missed a post that shows this info please reply with the link.
Thank you!
Click to expand...
Click to collapse
If you are on MAC or linux I suppose you have fastboot installed! If not get it installed from here
Now To restore your phone to stock download this firmware.
After Downloading! Extract the firmware. cd to the directory of extraction.
Use the script in the attachement to restore your phone.
OR
Enter these commands manually
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
You will need the path to fastboot to be added in path variable!
OMG!!!! thank you, thank you, thank you!!!!!
Worked like a charm, I was flipping out trying to figure this out b4 I had to work, your a life saver!!! Btw is there any downside to this process, like can I re-lock the boot loader and is it still possible to get OTA updates?
OTA updates work regardless of whether your bootloader is unlocked or not.
It's root and other changes to the /system partition that'd prevent such updates from working.
killjoydreams said:
Worked like a charm, I was flipping out trying to figure this out b4 I had to work, your a life saver!!! Btw is there any downside to this process, like can I re-lock the boot loader and is it still possible to get OTA updates?
Click to expand...
Click to collapse
No no downsides
You can re-lock the bootloader
And you will get OTA updates as well, even if your bootloader is unlocked!
Just have stock recovery
Related
hi all
Im trying to flash stock recovery and stock 4.4.2 so i can get the 4.4.4 update.
All drivers installed done the adb boot command get to that screen then get this error on first line
C:\Users\Michael1\Desktop\new1\VODAFONE-GB-SL_FALCON_KLB20.9-1.10-1.24-1.1_cid7_
CFC_1FF_SVC.xml>mfastboot flash partition gpt.bin
********'mfastboot' is not recognized as an internal or external command,
operable program or batch file.*********
Ive followed this exactly always getting this error please could someone help out there I thank you for your time cheers
3b) If you downloaded and extracted a firmware in .xml.zip format.
Flash each of the partitions in sequence using mfastboot, you need to enter the following commands one-by-one checking that each one returns an [OKAY]
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
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
AndroidHtc101 said:
hi all
Im trying to flash stock recovery and stock 4.4.2 so i can get the 4.4.4 update.
All drivers installed done the adb boot command get to that screen then get this error on first line
C:\Users\Michael1\Desktop\new1\VODAFONE-GB-SL_FALCON_KLB20.9-1.10-1.24-1.1_cid7_
CFC_1FF_SVC.xml>mfastboot flash partition gpt.bin
********'mfastboot' is not recognized as an internal or external command,
operable program or batch file.*********
Ive followed this exactly always getting this error please could someone help out there I thank you for your time cheers
Click to expand...
Click to collapse
Sounds like you don't have mfastboot.exe in the same folder as the files you are trying to flash. Make sure you have downloaded and extracted THIS package to the same folder as the firmware you're flashing.
hi finish i put fastboot in working until now i get this error
mfastboot flash system system.img_sparsechunk2 max sparse size 256 error cannot load system image
thanks for your help on this one
Confirm that you are inputing the correct filenames. For example my first system chunkfile number was zero, and maybe it had a dot before the number.
There is an XT1032 Global GSM 4.4.4 firmware image now available:
http://forum.xda-developers.com/showpost.php?p=54365926&postcount=292
It's intended for Retail Brasil, but should work anywhere.
Your are a Legend thank you very much it worked Now I will be able to get the 4.4.4 update because i had a touch to retry error before.
Much appreciated Finish Flash
AndroidHtc101 said:
Your are a Legend thank you very much it worked Now I will be able to get the 4.4.4 update because i had a touch to retry error before.
Much appreciated Finish Flash
Click to expand...
Click to collapse
You're welcome.
One quick question Ive noticed I dont have superuser do I needed to do that all again after i upgrade to 4.4.4?
cheers
To avoid possible problems with upgrading process, first upgrade and then re-root.
ok thanks
Did that last process make my bootloader locked again? It was so long ago cant remember how I unlocked bootloader and rooted
No, bootloader is still unlocked.
Rooting method described here might be the easiest:
http://www.modaco.com/topic/366771-root-your-moto-g-option-1-superboot/
Finnish Flash said:
No, bootloader is still unlocked.
Rooting method described here might be the easiest:
http://www.modaco.com/topic/366771-root-your-moto-g-option-1-superboot/
Click to expand...
Click to collapse
thanks for all your help:_)
Hi,
after an apparently failed attempt to install the 5.0 OTA update my XT1032 now will boot to a droid lying on its back.
I went to the recovery from there (by pressing VolUp+Power) and did the "factory reset/wipe data" and rebooted.
Same result.
I did "wipe chache". Same result: Droid lying on its back, saying "Kein Befehl" (I guess that means "no command")
I can get into recovery mode (CWM was installed before all this*) so I could try to flash stuff from outside.
But what should I try to flash? I tried flashing a (supposedly) stock system but as soon as I start with "fastboot flash boot boot.img" the phone starts booting again. So I am not really sure what to do now.
Something is seriously wrong with this phone and I would like to restore it to stock settings. I bought it on amazon.DE - so if any one of you guys knows where I could find a truly original stock image for this phone and what to do with it, please let me know.
PS: Right now I can't even get into recovery anymore. The thing just keeps booting and booting. Can't even turn it off.
* meaning: before I flashed the supposed stock recovery that apparently, in combination with the OTA update, got me into this mess
I now followed this guide:
http://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I used option 3b with a 4.4.4 rom ( RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF )
I excuted all these commands. However, upon flashing the boot.img the phone immediately boots (and gets stuck).
So I re-entered fastboot again to finish the job. Everything else went fine.
But the problem persists: When booting, the phone now displays the "Warning: Bootloader unlocked" message for a long time, with a kind of water ripple effect from bottom to top, repeating.
When I switch it off, it switches back on automatically, trying to boot and getting stuck at this screen. Sometimes I get to the droid lying on its back with a red !-Triangle on top. Poor little bugger. Soft bricked.
What can I do to fix this?
I can still enter fastboot.
I assume that yet again I grabbed the wrong ROM.
Is this supposed to be dead? http://sbf.droid-developers.org/phone.php?device=14
I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.
legolas06 said:
I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.
Click to expand...
Click to collapse
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.
ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.
fertchen said:
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.
Click to expand...
Click to collapse
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
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 system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.
audit13 said:
ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.
Click to expand...
Click to collapse
The problem here is that the phone will boot as soon as I flash the boot.img and the whole thing fails.
Do you see a way out of this situation?
Any way to do this with a .zip ROM?
Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.
@Fretchen
That might be because you are on lollipop bootloader & you are trying to flash kitkat bootloader?But I may be wrong. Previously you told that you tried restoring to kitkat & that boot.img is kitkat bootloader. Try with this lollipop firmware.
audit13 said:
Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.
Click to expand...
Click to collapse
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
fertchen said:
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
Happy that I could help.
You flashed the stock firmware so everything should work again. OTA updates if available would work.
fertchen said:
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
I don't know if you can apply OTA updates. Before the OTA update will work, you may need to update all Motorol apps via Play store.
You could wait until a fulkl stock lollipop pop is released for your phone and flash it using fastboot.
You can try different ROMs but stick to the ROMs made for your model. I have an xt1032 and I have installed US Retail, stock Telus, and GPE.
worked for me too, thank you soo much. give this solution a try
legolas06 said:
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
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 system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.
Click to expand...
Click to collapse
these steps look soo similar that the ones you can find in other blogs/discussions, but for me, in my case the main difference was the firmware, I tried with a loot of them, but the one that is mentioned in this post, installed smoothly, and with no issues, thank you so much, to post your experience and this solution.
My Best Regards,
Esteban
DISCLAIMER - if you have never rooted or flashed a phone in the past, please stop reading now. Don't even try this, you will probably brick your phone. This process complete replaces all OS components on your phone which can be hard to reverse if you don't know what you are doing. Proceed at your own risk! Backup and have a few roms handy to flash in case you mess up if the guide does not work for you. Make sure you have plenty of battery life before beginning.
This is a guide to restore to stock a Retail Asia (Australian Vodafone) Moto X Style XT1572 single sim phone.
I rooted and then flashed the EU single sim version rom of 6.0 a while ago, but now I wanted to go back to stock. Here is guide how. You will need your bootloader unlocked and developer mode on for USB debugging.
I believe the original Stock OS for the Retail Asia single sim Moto X style was 'X_Style_XT1572_CLARK_RETASIA_5.1.1_LPH23.116-18.1'. That is version 23.116-18.1. Retail Asia, NOT dual sim. The only reason to do this is you have an Australia/ Retail Asia handset and you flashed another rom on to it and want to go back to the Retail Asia single sim OTA update (Australian vodafone). If you have not messed with your phone you should not need to do this. But you could download the OS image as a future backup in case you ever want to back original stock rom the phone shipped with.
Google drive link - 'X_Style_XT1572_CLARK_RETASIA_5.1.1_LPH23.116-18.1 (1.4gb)
Once you have downloaded the zip, decompress it to a folder. Then using Command prompt or Terminal navigate to the folder. Make sure you have fastboot or mfastboot running properly (not sure why you need to use mfastboot but some do), boot in to the bootloader and beginning flashing the individual components of the zip file.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
Once you reboot the phone you should be running the completely stock rom the phone come with. It will remove root and any custom recovery you might have installed. It will not relock the bootloader.
To get the OTA you need to be on the stock rom and NOT rooted. Once you reboot within seconds you should get an update notification to download the new 24.11.20 Android M 6.0 update. It is about 640mb.
I hope this helps.
Thanks
Was wondering when they would release the official update for retasia
Have reverted back to stock to download the OTA and also captured the OTA for single sim retasia. The version number on this is slightly newer than the Europe and US versions I have been using
edit: Link to retasia MM
https://drive.google.com/file/d/0B4G7mEPBaNoHckxCWWxnY0dzaVU/view?usp=sharing
Awesome! Thank you @Sensation_NZ. I tried to capture the OTA but for some reason my adb would flash but not rewrite anything from the device back. I have grabbed a copy for future use.
wondering if all Australian X Style handsets are Asian? or EU?
Thanks for the post... Just wondering if you could help me, where could I find the modem for the Australian version? Thank you
swifteagle said:
Thanks for the post... Just wondering if you could help me, where could I find the modem for the Australian version? Thank you
Click to expand...
Click to collapse
Never mind, it is included. "fastboot flash modem NON-HLOS.bin" . Thank you very much for this post, life saver!
How did you capture the OTA?
Will this work for dual sim??
Great .. My 1st BootLoop ..
I followed this to the T .. And now it doesn't boot ...
Anyone know how to fix this so it works again, like back to Stock that works.?
I think you flashed Lolipop.
The same way as here:
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
Don't copy&paste; read, think & retype, download newest 6.x.x for your model, check how many sparsechunks it has(9,10,12?). @Lethal_1
After tried to root my device without the assist of PC (only using apk), my device only starts on AP Fastboot Flash Mode (Secure).
I downloaded the brazilian firmware, tried to flash it but I can't.
Was getting this ERROR: "(bootloader) Preflash validation failed".
My bootloader is locked, so I tried to unlock it following the Motorola's guide. Got my device ID via fastboot, copy and paste on their site and requested the unlock key.
Then again, when I use "fastboot oem unlock CODE"
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.016s
The problem is that I can't pass trough flash mode screen.
I've been reading some threads over here, and one guy which had his bootloader locked on XT1563 tried to flash the Canadian firmware and didn't get any error, then he was able to fully unlock his bootloader and after this he was able to flash the Brazilian firmware.
I didn't try to flash the Canadian firmware yet. How risky is this? There is another way to unlock the bootloader?
If you flash the right firmware for a locked phone (model and version), it won't give the prevalidation error. Then it can boot again and you can turn on the OEM unlock, and unlock the bootloader.
Try to use the right firmware for your phone.
TImMaia said:
After tried to root my device without the assist of PC (only using apk), my device only starts on AP Fastboot Flash Mode (Secure).
I downloaded the brazilian firmware, tried to flash it but I can't.
Was getting this ERROR: "(bootloader) Preflash validation failed".
Click to expand...
Click to collapse
I don't believe it is possible to root without first unlocking your bootloader (which will factory reset your device). What apk were you attempting to install?
MrTooPhone said:
I don't believe it is possible to root without first unlocking your bootloader (which will factory reset your device). What apk were you attempting to install?
Click to expand...
Click to collapse
I'm a real noob at this issue. I tried to root with Kingroot. I took the device to the Motorola Tech Support in my city yesterday afternoon and it is ready to pick up.
Thank you guys for helping me :good::good::good:
TImMaia said:
I'm a real noob at this issue. I tried to root with Kingroot. I took the device to the Motorola Tech Support in my city yesterday afternoon and it is ready to pick up.
Thank you guys for helping me :good::good::good:
Click to expand...
Click to collapse
If you really want to root, you need to follow these instructions. Although you can use the latest version of TWRP, do not use any other version of Supersu except v2.62-3. Any other methods will most likely soft brick your phone.
Boys, is not difficult, not just fiddling around to fix it.
Motorola install drivers
Install ADB and fastboot
Looking for your stock rom here: " github dot com dash motoxplay dash stock dash releases " for example.
Saddled with fastboot Tooda the rom (eye, if downloaded from out there commands, you may be wanting to them upload any image rom, this drove me crazy to me all one day until I realized I was missing two sparsechunk).
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
On the subject battery, the XT1563 charge the batt when it is in this mode, we just have to leave it connected to the charger and is loading very slowly.
On the bootloader issue, I have LOCK, and may do so without problems because they look the same version of rom that he had.
About not having DEPURACION USB, I did not have it on, and yet I could do it.
My stay in Fastboot mode I when installing the app Kingroot, and turned off the phone and start no more.
In this way it is solved, 100% sure I did not do myself. Do not try other methods like TWRP or things like that because with locked bootloader will hit the wall every time.
Anyone who needs a hand, ask or send mail.
Sorry if he had been resolved, but it was a big achievement for me, so I leave the info. I cost a lot to buy the cell phone and had ****ed the other day.
Regards!
(Sorry, its googletranslated, im from argentina)
Yeah, what ever @jonatandirocca1 said is right
i also once faced the problem of missing sparse file but after flashing every file you can make your Phone revoke
if you want to install STOCK FIRMWARE , you dont need to unlock bootloader, you just need your phone detected in ADB
Hey, I just installed June security patch on my Moto G6 and I gotta say this build is super smooth.
I’m getting more than 5-6hrs of SOT and yes DIGITAL WELLBEING IS A SYSTEM APP NOW.
I downloaded the latest firmware from here : https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
And flashed it via RSD Lite.
Don’t forget to hit thanks
aaryan1596 said:
Hey, I just installed June security patch on my Moto G6 and I gotta say this build is super smooth.
I’m getting more than 5-6hrs of SOT and yes DIGITAL WELLBEING IS A SYSTEM APP NOW.
I downloaded the latest firmware from here : https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
And flashed it via RSD Lite.
Don’t forget to hit thanks
Click to expand...
Click to collapse
Can I install this patch with Android 9 OTA with Root?
bradz28 said:
Can I install this patch with Android 9 OTA with Root?
Click to expand...
Click to collapse
No, unfortunately not. This is a full wipe/fresh install only. The same rooting method works, but it will have to be a fresh install.
xfrobex said:
No, unfortunately not. This is a full wipe/fresh install only. The same rooting method works, but it will have to be a fresh install.
Click to expand...
Click to collapse
Ok, thanks
Hello, I upgraded my phone through CMD commands in fastboot folder, but now I can't hear nor be heard in calls. I tried already intalling the NON-HLOS.bin from Stock ROM RETAIL OPSS27.104-92-4 and tried with the NON-HLOS.bin from the Sotck ROM from my region OPENMX OPSS27.82-87-8 too, but it didn't work.
Tried turning the phone on Secure Mode to see if it was a problem related with an app but it wasn't the case, also tried couple of times doing factory reset, but it gave the same result.
I was on the RETAIL PPSS29.55-34-1 with NON-HLOS.bin from OPENMX OPSS27.82-87-8 and the calls were fine. Could someone help me, please?
I did all of above with locked bootloader.
Edit:
Now I unlocked bootloader to downgrading to RETAIL PPSS29.55-34-1 with NON-HLOS.bin from OPENMX OPSS27.82-87-8, and it didn't work so I relock bootloader.
mariconojoda said:
Hello, I upgraded my phone through CMD commands in a fastboot folder, but now I can't hear and can't be heard in calls. I tried already intalling the NON-HLOS.bin from Stock ROM RETAIL OPSS27.104-92-4 and tried with the NON-HLOS.bin from the Sotck ROM from my region OPENMX OPSS27.82-87-8, but it didn't work.
Also tried turning the phone on Secure Mode to see if it was a problem related with an app but it wasn't the case, also tried couple of times doing factory reset, but it gave the same result.
I was on the RETAIL PPSS29.55-34-1 and the calls were fine. Could someone help me, please?
All of above with locked bootloader.
Edit:
Now I unlocked bootloader to downgrading, I donwgrade to RETAIL PPSS29.55-34-1 with NON-HLOS.bin from OPENMX OPSS27.82-87-8, it didn't work so I relock bootloader.
Click to expand...
Click to collapse
As you unlocked the bootloader your warranty is gone, plus I didn’t try with CMD commands, I used RSD Lite, so maybe try a fresh install again if problem persists.
aaryan1596 said:
As you unlocked the bootloader your warranty is gone, plus I didn’t try with CMD commands, I used RSD Lite, so maybe try a fresh install again if problem persists.
Click to expand...
Click to collapse
It don't recognize the device
Nevermind I just needed to connect the device in another port, also now the calls work thank you @aaryan1596
How do I install this without RSDLite? The program doesn't work for me at all (v5.7 on Win10), and I do not fully understand how to use fastboot/batch files to install the unpacked .zip file. Thank you for your help.
Edit: I was able to easily install this using Minimal ADB and Fastboot. Simply extract the contents of your .xml.zip file to your Minimal ADB and Fastboot installation folder. Boot your phone into fastboot mode (volume+power down) and copy and paste these commands (you can copy and paste the entire block and they will run sequentially):
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
fastboot flash dsp adspso.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot erase cache
fastboot reboot
Using this method I was able to easily install to latest version onto my XT1925-6, which shipped with Oreo.
Is there any different between ROM with february security patch and this one (june security patch)?
Has anyone in the UK been able to download this update via system updates yet?
um.z said:
Has anyone in the UK been able to download this update via system updates yet?
Click to expand...
Click to collapse
Just downloading via system updates, channel: retgb.
Well, I received the June 1, PPS29.55-37-4 OTA (retgb channel) at around 9:40pm (Mon 5th Aug, UK time). It took 12 minutes to download the 818.6Mb package over a 4G connection, and a further 26 minutes to install it.
Everything went without a hitch, and all seemed perfectly fine afterwards...
...however, having previously read about the problems reported here on XDA and on the Lenovo/Motorola community support forum regarding recent Pie updates, I decided to perform a factory wipe/reset immediately after the update. A tiresome chore to be sure, having to set everything up again aftwards, but it just seemed the prudent thing to do.
So now, some 19 hours later, my G6 is still working perfectly, with no obvious problems, and it does certainly feel smoother and more responsive than it's predecessor, PPS29.55-24, which I received at the end of March. And, yep, this new 'build' includes Google's Digital Wellbeing app integrated at the system level, so I guess that's something new to tinker around with.
Anyhow, just some thoughts regarding my experience of updating to this latest version of Pie.
Rgrds,
Ged.
test