Moto G4 Plus US Variant XT1644
Build# MPJ24.139-64 Android 6.0.1
Stock Unmodified TWRP Backup
Stock Recovery.img & Logo.bin​
Description:
I could not find ANY stock images for the US XT1644 variant so I made my own for others that have modified their system partition and wish to restore to a factory state and take the 7.0 update. Backup created on a factory reset unmodified stock build (not previously rooted/xposed/modified in any way) via fastboot booting TWRP w/system write disabled. Stock recovery and logo extracted via DD from stock rooted rom after TWRP backup was made. I pulled the recovery and logo images as these are the most commonly modified partitions (other than the system). This backup will work if you stayed on 6.0.1 and rooted/exposed/changed boot logo/etc. If you played with the 7.0 updates made for other variants, I honestly don't know if this will work for you to take the OTA as the bootloader/modem were likely modified - Test and let us know.
Directions:
-Have ADB working on your PC (google it, not getting into that here)
-Download TWRP backup here: https://mega.nz/#F!vBgU3QJB!R5J5RgZkvUiWHwmIfN6BkA
-Move backup to your proper TWRP backup location on your sd or external sd
-Restore backup via TWRP and reboot
-Download stock recovery & logo images here: https://mega.nz/#F!eBpB3Z5C!J6hoLKdfcObSLavWCsLnyw
-Power off device/plug into pc/hold volume down for 5 seconds/press and hold power & volume down until fastboot appears
-Move files to adb location (Windows) or open terminal where you downloaded the files (Linux) on your pc
-Verify connection
Code:
fastboot devices
-Restore stock recovery:
Code:
fastboot flash recovery recovery.img
-Restore stock logo (if you changed it previously to get rid of warning):
Code:
fastboot flash logo logo.bin
-Reboot and enjoy stock 6.0.1 and be able to take OTA
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Click to expand...
Click to collapse
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Sent from my XT1575 using Tapatalk
annoyingduck said:
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Click to expand...
Click to collapse
I Will flash stock xt1644 firmware 64, then i restore your backup
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
pupamonkey said:
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
Click to expand...
Click to collapse
It's not available, we're still waiting for it, that's why we flashing stock firmware again
Thanks for doing this! It's essentially what I did to get the marshmallow update (restore stock system & boot via TWRP, then recovery & logo via fastboot).
Please let us know when you see moto/Lenovo push out the nougat update via OTA!
Sent from my Moto G4 Plus using Tapatalk
you are the champ!! i have exact same model but i am yet to update to 64 release as i just got the phone today. Just doing some research before i grease my hands! thanks man!
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
bmeek said:
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
Click to expand...
Click to collapse
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
where to check?
i have the us variant from best buy as well , but i twicked it a lot .
How can i know when a nougat release is available? where can i check .
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
Click to expand...
Click to collapse
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Hymizzle said:
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Click to expand...
Click to collapse
If you flash a XT1625-XT1644 firmware and you use it "normally" on a XT1644, at some point you will have ghost touch even with low brightness, but...
For upgrading, I'll recommend flashing XT1625-XT1644, (cause there's no
...139-64 XT1644 firmware, just a firmware for both)
Flash it via fastboot, boot it up, flash TWRP recovery, wipe the full system with it, download the TWRP backup that was posted here, restore it, then via fastboot flash the stock recovery (for removing TWRP) and stock logo, then you will have MPJ24.139-64 with no problems, just waiting for nougat OTA for retus version.
Here's the link for retus firmwares: https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
TheDude1998 said:
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
Click to expand...
Click to collapse
Yeah I wouldn't think so, but thanks for letting us know.
Sent from my XT1575 using Tapatalk
getting the Nougat OTA
annoyingduck said:
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
Click to expand...
Click to collapse
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Click to expand...
Click to collapse
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
dedik46 said:
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
Click to expand...
Click to collapse
Yes your bootloader will still be unlocked unless you specifically enter the oem lock command. Read the tutorials, they all explain how to keep your bootloader unlocked.
Sent from my XT1575 using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
vishnureddy17 said:
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
Click to expand...
Click to collapse
Which of these 5 download? .
Related
Verizon announced yesterday they have released the OTA update for 4.4.4 for the Verizon Moto G, 210.12.41.falcon_cdma.Verizon.en.US. I was wondering if anyone has captured the update yet as mine still says Software is up to date. Even tried the Framework Trick with no luck.
judask24 said:
Verizon announced yesterday they have released the OTA update for 4.4.4 for the Verizon Moto G, 210.12.41.falcon_cdma.Verizon.en.US. I was wondering if anyone has captured the update yet as mine still says Software is up to date. Even tried the Framework Trick with no luck.
Click to expand...
Click to collapse
No luck here...there is post over on Android Forums that Verizon users are getting the 4.4.4 OTA update but nobody has posted the captured zip file yet.
Captured Verizon CDMA Moto G 4.4.4 Update Zip
Here's a link to download the new Verizon Moto G 4.4.4 CDMA version of Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
http://goo.gl/Vuw0P9
or
http://www.mediafire.com/download/3q7paotltq951id/Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
I have not installed it yet as I'm running a Boost Mobile Moto G flashed to Verizon Wireless running on Page Plus that's rooted. I'm waiting to see if someone has completed the update without problems before I try.
If someone attempts the update for a Page Plus flashed Moto G let me know how it goes.
netkeys said:
Here's a link to download the new Verizon Moto G 4.4.4 CDMA version of Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
http://goo.gl/Vuw0P9
or
http://www.mediafire.com/download/3q7paotltq951id/Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
I have not installed it yet as I'm running a Boost Mobile Moto G flashed to Verizon Wireless running on Page Plus that's rooted. I'm waiting to see if someone has completed the update without problems before I try.
If someone attempts the update for a Page Plus flashed Moto G let me know how it goes.
Click to expand...
Click to collapse
That 173.44.20.falcon_cdma.Verizon.en.US is the 4.4.2 Kit Kat currently installed on the G's. I am looking for the newer one. 210.12.41.falcon_cdma.Verizon.en.US which is the 4.4.4 update.
judask24 said:
That 173.44.20.falcon_cdma.Verizon.en.US is the 4.4.2 Kit Kat currently installed on the G's. I am looking for the newer one. 210.12.41.falcon_cdma.Verizon.en.US which is the 4.4.4 update.
Click to expand...
Click to collapse
This is the file downloaded on 7-21-2014. Attached is a screen shot of the updater.
netkeys said:
I have not installed it yet as I'm running a Boost Mobile Moto G flashed to Verizon Wireless running on Page Plus that's rooted. I'm waiting to see if someone has completed the update without problems before I try.
If someone attempts the update for a Page Plus flashed Moto G let me know how it goes.
Click to expand...
Click to collapse
I have a Page Plus flashed Moto G, it's only a backup phone, so I guess I'll be the guinea pig today. I'll let you know if it catches on fire, burns down the neighborhood, kills small fluffy animals, etc.
randomchaos26 said:
I have a Page Plus flashed Moto G, it's only a backup phone, so I guess I'll be the guinea pig today. I'll let you know if it catches on fire, burns down the neighborhood, kills small fluffy animals, etc.
Click to expand...
Click to collapse
I am also on cdma Moto G (stock/no root) flashed to Page Plus...I downloaded the captured update zip and put in root of SD but is not detected when I check for system update in settings, still says "software is up to date". Any suggestions?
chinocritter said:
I am also on cdma Moto G (stock/no root) flashed to Page Plus...I downloaded the captured update zip and put in root of SD but is not detected when when I check for system update in settings, still says "software is up to date". Any suggestions?
Click to expand...
Click to collapse
It was pulled from the /cache folder. If you put in /storage/sdcard0 you may also need to rename to update.zip
randomchaos26 said:
I have a Page Plus flashed Moto G, it's only a backup phone, so I guess I'll be the guinea pig today. I'll let you know if it catches on fire, burns down the neighborhood, kills small fluffy animals, etc.
Click to expand...
Click to collapse
Yes please do. My wife's phone is wanting to update since Sunday night.
Seems to work just fine on Page Plus after the update, root works, and nothing has caught on fire yet. Edit: Tested data and calling, both seem to work fine.
Steps to update (this assumes your bootloader is already unlocked and you have cwm recovery installed):
Save the update zip and the cwm flashable supersu zip to your phone.
Boot into cwm recovery and do a backup (assuming you have space on /media/data for a backup.)
Reboot to bootloader.
Restore *just* your system partition to stock with fastboot (using: CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip)
Boot into cwm again, apply the update zip, then immediately apply the supersu zip.
Boot up normally and let it do its update stuff, then go into titanium backup and kill off any of the verizon bloatware that you don't want.
If you want to get rid of the ugly "WARNING BOOTLOADER UNLOCKED IT WILL KILL YOUR FAMILY" boot logo, flash the logo.bin (fastboot flash logo logo.bin) in the attached zip file. It is just a simple hex edit of the logo address in the file header. I've included the original as logo.bin.bak so you can verify it against the original, and compare the two files if you want to see how it's done.
chinocritter said:
I am also on cdma Moto G (stock/no root) flashed to Page Plus...I downloaded the captured update zip and put in root of SD but is not detected when I check for system update in settings, still says "software is up to date". Any suggestions?
Click to expand...
Click to collapse
I think you can select "apply update from sdcard" in the recovery mode. No?
EDIT: You flashed to PagePlus. I missed that part. Sorry about that.
I was on a AOSP based rom.
So I flashed back to stock via CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.
Booted up once to make sure the the flash went well.
Flashed CWM via bootloader. Tried TWRP first, did not work with the update.zip.
Renamed the zip above to update.zip and flashed via cwm. Worked fine. (yes the zip is 4.4.4)
Before rebooting, went ahead and flashed supersu.zip.
Then rebooted back to bootloader and flashed my preferred recovery, TWRP.
All seems well. This is on PagePlus.
Bout time we get 4.4.4. I'm also using Boost Moto G to Verizon/Page Plus. I will update when I have free time. Thanks for the info, guys.
XDA Dark said:
Bout time we get 4.4.4. I'm also using Boost Moto G to Verizon/Page Plus. I will update when I have free time. Thanks for the info, guys.
Click to expand...
Click to collapse
It sounds like the 4.4.4 update is working fine...the only issue is that there doesn't seem to be a full stock 4.4.4 flash available (like we have for 4.4.2), and from what I can tell from posts (haven't tried this myself), you cannot reflash the full stock 4.4.2 after the 4.4.4 update since the bootloader and/or partitions have changed. There may be some workarounds, but those seem to be for other models or geographies as best I can tell. Once we have the full 4.4.4 flash, then at least you can always revert to that, but it doesn't appear to be released yet.
I've been keeping an eye out for the update OTA. I guess I'd rather just go down that path officially since my phones not rooted and had stock locked bootloader. Just wish it would hurry up and be pushed to my device.
Install zip via stock recovery
judask24 said:
Verizon announced yesterday they have released the OTA update for 4.4.4 for the Verizon Moto G, 210.12.41.falcon_cdma.Verizon.en.US. I was wondering if anyone has captured the update yet as mine still says Software is up to date. Even tried the Framework Trick with no luck.
Click to expand...
Click to collapse
Ota file works it is 4.4.4 update for Verizon Mota G. Download zip to phone power off. Hold down power and volume down for a few seconds release. Once at menu go to recovery. Once in recovery android with exclamation with no options will appear. Press and hold Volume up for 10 seconds continue to hold while now also pressing power button for 3 seconds release. Your in recovery mode select update from zip and proceed. Happy camping with new dialer update camera shots in low lightness and other fixes and features!
randomchaos26 said:
Seems to work just fine on Page Plus after the update, root works, and nothing has caught on fire yet. Edit: Tested data and calling, both seem to work fine.
Steps to update (this assumes your bootloader is already unlocked and you have cwm recovery installed):
Save the update zip and the cwm flashable supersu zip to your phone.
Boot into cwm recovery and do a backup (assuming you have space on /media/data for a backup.)
Reboot to bootloader.
Restore *just* your system partition to stock with fastboot (using: CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip)
Boot into cwm again, apply the update zip, then immediately apply the supersu zip.
Boot up normally and let it do its update stuff, then go into titanium backup and kill off any of the verizon bloatware that you don't want.
If you want to get rid of the ugly "WARNING BOOTLOADER UNLOCKED IT WILL KILL YOUR FAMILY" boot logo, flash the logo.bin (fastboot flash logo logo.bin) in the attached zip file. It is just a simple hex edit of the logo address in the file header. I've included the original as logo.bin.bak so you can verify it against the original, and compare the two files if you want to see how it's done.
Click to expand...
Click to collapse
Followed these directions and worked without any problem.
The fixed the external USB mounting problem that was in 4.4.2
I updated today on Boost Mobile Moto G flashed to Page Plus with no issues... Success
Sent from my XT1028 using XDA Free mobile app
randomchaos26 said:
Steps to update (this assumes your bootloader is already unlocked and you have cwm recovery installed):
Save the update zip and the cwm flashable supersu zip to your phone.
Boot into cwm recovery and do a backup (assuming you have space on /media/data for a backup.)
Reboot to bootloader.
Restore *just* your system partition to stock with fastboot (using: CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip)
Boot into cwm again, apply the update zip, then immediately apply the supersu zip.
Boot up normally and let it do its update stuff, then go into titanium backup and kill off any of the verizon bloatware that you don't want.
Click to expand...
Click to collapse
Thanks for the instruction. Questions:
(1) My flashed page plus moto-g is on rooted stock rom (with unlocked bootloader of course). Do I still need to restore the system partition back to stock?
(2) What is "CFC-fastboot"? Do you mean
fastboot falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip
(i.e. no underscore between fastboot and falcon) ?
Thanks!
it's available on OTA now yay
Okay so here's the info to the best of my knowledge,
Phone Model : Moto G 3rd Gen (XT1550, dual sim, 2gb RAM, 16gb ROM, India)
Bootloader Status : Unlocked
Root Status : Rooted
Recovery : Stock
ROM : Stock ROM 5.1.1
I've been running the stock Recovery & ROM with high hopes of getting an official OTA Marshamallow update.
To truly customize the device to my liking I flashed the xposed framework (the arm version) , it worked fine and all the modules I installed worked perfectly.
I also had Device Control, Xposed Gels, and some other apps to bring my Stock ROM experience close to that of Cyanogen MOD.
When the OTA Marshmallow update started rolling in , I was unable to install the update even after successfully downloading the file numerous times. But i was so comfortable with my device and all the customization I had on my device that I decided to keep using my customized Stock ROM.
4 months later (now) the lack of a gyro in this device and my eagerness to get into VR headsets has left me with no choice but to sell it and get another phone. So i needed it in a sale worthy condition, without the customization and with the Marshmallow update installed.
I uninstalled the xposed framework and all the modules but was still unable to install the OTA update.
So i figured i'd install CyanogenMOD with TWRP custom recovery.
I have done this for quiet a lot of my friends and am fairly used to the steps involved. I use the " minimalADB fastboot " kit and my device on fastboot to flash recovery. For some reason i was not able to flash the lastest TWRP image (twrp-osprey-3.0.0-r2.img ) for the device nor was i able to boot from it :crying:. The fastboot command prompt on my PC would show success but the devices would not restart into the custom recovery like it is supposed to, but the device would stay at the fastboot mode and kept restarting everytime i selected the recovery mode option.
I had an older image (twrp-osprey-2.8.7-r3.img ) which i couldn't flash either but i was able to boot into TWRP with this image. From here i tried installing the latest CM12.1 nightly available (cm-12.1-20160227-NIGHTLY-osprey.zip) as soon as i swiped the device would just reboot, i tried this numerous times and with other nightly builds as well.
In haste and frustration i wiped the cache/dalvik , internal storage and system through TWRP , thinking that changes made in the quest of customizing my device were causing this hindrance. I had no OS now. I went over trying to flash TWRP and CM12.1 many times again with the same issues.
I came about a thread on How to " Fastboot Flash Moto G (3rd Gen) Factory Firmware Images " (http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750) & used this firmware image " Retail Asia | India (2GB) - XT1550_OSPREY_RETASIA_DS_2GB_6.0_MPI24.65-25_cid7 ". Still no progress.
The bootloader unlocked warning has come back (i flashed a stock MOTO logo there earlier) which keeps flashing on my screen again and again , no booting into OS or anything else. Not even an error. As if there is no OS installed.
I have gone about the procedure in the above thread a couple of times, with no success and the same problem.
Is there any reason why i'm unable to flash a custom recovery or ROM ??? What am i missing???
Please help i'm stuck, pulling my hair out with no phone and completely frustrated.
Thanks in advance.
Did you check your build no for stock ROM?
samirza692 said:
Did you check your build no for stock ROM?
Click to expand...
Click to collapse
Nope. Too late for that now.
If you're asking in regard to the stock firmware I tried to flash, it didnt depend on the build number. Just the model number and the RAM.
ashrith.s said:
Nope. Too late for that now.
If you're asking in regard to the stock firmware I tried to flash, it didnt depend on the build number. Just the model number and the RAM.
Click to expand...
Click to collapse
okay i am not a developer nor a noop but trying to help you
try to flash stock rom from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 but dont mistake this time double check your model with build number using carefuly the steps from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
You will not brick the phone if you use the latest firmware and do a factory reset before flashing.
Good luck.
but do at your own risk i am not responsible for anything
samirza692 said:
okay i am not a developer nor a noop but trying to help you
try to flash stock rom from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 but dont mistake this time double check your model with build number using carefuly the steps from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
You will not brick the phone if you use the latest firmware and do a factory reset before flashing.
Good luck.
but do at your own risk i am not responsible for anything
Click to expand...
Click to collapse
the link provided is the exact same link from where I flashed a stock rom before.
build number for stock rom??? am i missing something???
all i see is the model variant (xt1550 is my phone)
RAM specification (mine is 2gb)
and the region (mine is retails asia | india )
so i went with the following firmware
Retail Asia | India (2GB) - XT1550_OSPREY_RETASIA_DS_2GB_6.0_MPI24.65-25_cid7
where does the build number come into the equation???
Please lemme know if im doing something wrong. Thanks for the replies.
So I've successfully flashed twrp-osprey-2.8.7-r3.img to my device and I've been able to boot into twrp. The touchscreen doesn't seem to respond though. It asks to swipe to begin and I'm stuck again.
I had the screen replaced a couple of days ago.
Could it be a faulty screen or a software issue?
P.S. I have not been able to flash any version of twrp after the above mentioned version (v 3.0.0 is the latest stable version) but the ones prior are flashable.
Hey, contact me via PM and il do my best to help you in this.
therealduff1 said:
Hey, contact me via PM and il do my best to help you in this.
Click to expand...
Click to collapse
Is not big issue
Is it still possible to boot back into the OS? If it is, check if you have OEM unlocking enabled, since you're on stock ROM, it might be gotten unchecked after unlocking your bootloader because that's what happened with me. If you do t wether or not that was checked, you're at a dead end and there's nothing you can do. You can try paying someone to fix it, i.e., Motorola.
Disclaimer:
I am not responsible for anything that may happen to your phone as a result of installing this rom. You do so at your own risk and take responsibility upon yourself.
About:
The Stock ROMs posted here are extracted from official LG KDZ files for the T-Mobile LG G Pad X 8.0 | v521 | b3.
Only change made on ROM was to prevent stock recovery from restoring itself
ROM includes modem/radio, however you can also manually flash the modem/radio from here
root is NOT included. However feel free to flash your choice of root with Magisk, SuperSU, or any others at anytime to get root.
Info:
Android version: 7.0
Kernel version: 3.10.84
Build number: NRD90U
init.d support
forceencrypt disabled
Requirements:
Your device must be or have been on 20f or newer at one point or another. If your device has always been on Marshmallow and has never been updated to Nougat by kdz or OTA, you'll need to upgrade to Nougat and re-root first. (Thank to monkeyass408 for verifying)
You can follow this guide to do so: Guide to Update V521 LG GPAD X 8.0 to 7.0 and Root
You must have TWRP or another custom recovery already installed in order to flash this rom.
Instructions:
Download the version of your choice from below.
Boot into TWRP and make a backup. You may want to remove any lock screen security before doing this as restoring with lock screen may cause unexpected issues.
Optional: Wipe data and/or system. As of TWRP 3.1.1.0, you will want to reboot recovery after wiping data/system before flashing as TWRP may get stuck on a black screen during the flashing process without a reboot.
Flash ROM.
Optional: Flash the disable OTA zip to prevent and disable official LG OTA updates & notifications
Reboot and you should be all set.
Downloads: (Listed by Sofware version / Android security patch level)
Note: As of 2017-02-21, TWRP 3.0.2-0, will sometimes give the error "Failed to map file" when attempting to flash this rom. Rebooting TWRP will resolve it and allow you to flash the zip.
v52120n >> Apr 1, 2018
v52120m >> Feb 1, 2018
v52120l >> Dec 1, 2017
v52120k >> Oct 1, 2017
v52120j >> Aug 1, 2017
v52120i >> Jun 1, 2017
v52120h >> Apr 1, 2017
v52120g >> Feb 1, 2017
v52120f >> Dec 1, 2016
All Stock ROMs Folder
Disable Stock OTA
Note: This should prevent you from verifying and updating via OTA. The OTA notification may still pop up but it should go away when you attempt to update after flashing this. I haven't fully tested this so backup first and don't be surprised if it returns you to full stock.
Credits/Thanks:
tungkick for the initial root method
shabbypenguin for TWRP on the LG G Pad X
All other devs who make rom building possible
Reserved - Unlikely I'll need it but who knows?
Can this be flashed over marshmallow 10c? If so, what should be wiped? Thanks.
channeledbymodem said:
Can this be flashed over marshmallow 10c? If so, what should be wiped? Thanks.
Click to expand...
Click to collapse
Yes you can flash this over Marshmallow v52110c. Technically a dirty flash (no wipe) would work fine but you never know so don't be surprised if issues spring up. After you flash the rom, since you're upgrading from Marshmallow, you'll want to update the radios too. The flashable zips for it can be found @ https://forum.xda-developers.com/lg...irmware-modem-flashable-modem-zips-t-t3564590. I'd recommend flashing the respective radio of the Nougat version you end up using.
so after I flash the 20g my 5ghz wifi keeps on disconnecting, same thing after flashing the 20g modem. wiped data as well. coming from official 20f rooted with dirtycow.
my 10 other devices are fine so it's not my router. not sure if it's an issue with the 20g, never had any issue with 20f
supaet said:
so after I flash the 20g my 5ghz wifi keeps on disconnecting, same thing after flashing the 20g modem. wiped data as well. coming from official 20f rooted with dirtycow.
my 10 other devices are fine so it's not my router. not sure if it's an issue with the 20g, never had any issue with 20f
Click to expand...
Click to collapse
Hmmm I haven't had any issues with my 5ghz on my tablet. The roms are ripped straight out of the kdz files so any changes between 20g and 20f are strictly from LG/T-Mobile. Although I do recommend keeping the modem version and the rom version the same, I am curious, would you be able to test and see if it still happens if you downgrade the modem version to 20f while you're on the 20g rom?
Long overdue but added 20h, 20i, and 20j.
Decided to get rid of AROMA and root selection so any root method can be manually flashed afterwards.
Stock recovery shouldn't restore itself now. init.d support and forceencrypt is set to disabled by default since TWRP doesn't play along nicely with encrypt anyways.
.fenrir said:
Long overdue but added 20h, 20i, and 20j.
Decided to get rid of AROMA and root selection so any root method can be manually flashed afterwards.
Stock recovery shouldn't restore itself now. init.d support and forceencrypt is set to disabled by default since TWRP doesn't play along nicely with encrypt anyways.
Click to expand...
Click to collapse
Appreciate the update Thanks!!!
A bit quicker this time around. 20k has been added.
Amd4life said:
Appreciate the update Thanks!!!
Click to expand...
Click to collapse
No problem.
.fenrir said:
Yes you can flash this over Marshmallow v52110c. Technically a dirty flash (no wipe) would work fine but you never know so don't be surprised if issues spring up. After you flash the rom, since you're upgrading from Marshmallow, you'll want to update the radios too. The flashable zips for it can be found @ https://forum.xda-developers.com/lg...irmware-modem-flashable-modem-zips-t-t3564590. I'd recommend flashing the respective radio of the Nougat version you end up using.
Click to expand...
Click to collapse
i flashed from 10c marshmallow to nougat 20k. i am having problems getting lte data to even show up. Would u happen to know how to get it working?
i did wipe and started fresh install. I also flashed the k modem and it didnt work.
monkeyass408 said:
i flashed from 10c marshmallow to nougat 20k. i am having problems getting lte data to even show up. Would u happen to know how to get it working?
i did wipe and started fresh install. I also flashed the k modem and it didnt work.
Click to expand...
Click to collapse
Shouldn't need to do anything for LTE to work. Does it get signal at least? I would confirm the APN settings just to make sure they aren't missing for whatever reason.
Otherwise, try another version and see if it does the same thing. Although it shouldn't be the case, it's possible that the device may need to be kdz'd to Nougat first before a Nougat ROM works without any problems. That being said, I do remember being able to manually flash Nougat on my tablet from 10c with no issues back when I was on it.
.fenrir said:
Shouldn't need to do anything for LTE to work. Does it get signal at least? I would confirm the APN settings just to make sure they aren't missing for whatever reason.
Otherwise, try another version and see if it does the same thing. Although it shouldn't be the case, it's possible that the device may need to be kdz'd to Nougat first before a Nougat ROM works without any problems. That being said, I do remember being able to manually flash Nougat on my tablet from 10c with no issues back when I was on it.
Click to expand...
Click to collapse
I figured it out. I had to take 10c marsh to 20f nougat stock and rerooted +twrp in order for it to work. No longee had grayed out lte and apn and missing imei. Thanks for the reply.
Flashing straight 10c marsh to a nougat rom will always give me those errors. Same when tried with resurection remix.
monkeyass408 said:
I figured it out. I had to take 10c marsh to 20f nougat stock and rerooted +twrp in order for it to work. No longee had grayed out lte and apn and missing imei. Thanks for the reply.
Flashing straight 10c marsh to a nougat rom will always give me those errors. Same when tried with resurection remix.
Click to expand...
Click to collapse
Glad to hear it worked out for you. I stand corrected on it being flashed over Marshmallow so I've updated the first post to reflect that. Thanks for trying and verifying it.
Hello,
The V52120l_00_1201.kdz is OTA, so could you please make the lastest ROM base on V52120l_00_1201.kdz
thanks in advance
@ .fenrir: I appreciate all the work you've done on this and don't really need the monthly patches. Is there a way to disable ota download and notification on a rooted tablet?
Thanks.
20l has been added. I also realized on the older files I accidentally called the device 8.3 instead of 8.0 in the zip so that's been corrected now.
Char_Liu said:
Hello,
The V52120l_00_1201.kdz is OTA, so could you please make the lastest ROM base on V52120l_00_1201.kdz
thanks in advance
Click to expand...
Click to collapse
Thanks for the heads up. Been busy with the holidays so didn't have a chance to do anything.
channeledbymodem said:
@ .fenrir: I appreciate all the work you've done on this and don't really need the monthly patches. Is there a way to disable ota download and notification on a rooted tablet?
Thanks.
Click to expand...
Click to collapse
When rooted, you should be able to delete /system/etc/security/otacerts.zip which should prevent the device from verifying for the OTA. Afterwards if the OTA was already downloaded on the device, you can delete the OTA update file at /cache/update.zip . That SHOULD be enough to do it but I won't make any guarantees until I get a chance to test it as you would probably need to delete the other LGFOTA as well. I'll make a flashable zip for it later on if necessary/when I get a chance.
.fenrir said:
20l has been added. I also realized on the older files I accidentally called the device 8.3 instead of 8.0 in the zip so that's been corrected now.
Thanks for the heads up. Been busy with the holidays so didn't have a chance to do anything.
When rooted, you should be able to delete /system/etc/security/otacerts.zip which should prevent the device from verifying for the OTA. Afterwards if the OTA was already downloaded on the device, you can delete the OTA update file at /cache/update.zip . That SHOULD be enough to do it but I won't make any guarantees until I get a chance to test it as you would probably need to delete the other LGFOTA as well. I'll make a flashable zip for it later on if necessary/when I get a chance.
Click to expand...
Click to collapse
Thank you for the update.!
Appreciate the update
Thx a lot
.fenrir said:
20l has been added. I also realized on the older files I accidentally called the device 8.3 instead of 8.0 in the zip so that's been corrected now.
Thanks for the heads up. Been busy with the holidays so didn't have a chance to do anything.
When rooted, you should be able to delete /system/etc/security/otacerts.zip which should prevent the device from verifying for the OTA. Afterwards if the OTA was already downloaded on the device, you can delete the OTA update file at /cache/update.zip . That SHOULD be enough to do it but I won't make any guarantees until I get a chance to test it as you would probably need to delete the other LGFOTA as well. I'll make a flashable zip for it later on if necessary/when I get a chance.
Click to expand...
Click to collapse
I have always had excellent battery life but after a dirty flash of v.l it is terrible. I am losing 30% overnight. Can I roll back to v.k? I am reluctant to clean flash v.l; it's a lot of work getting back to normal.
I've got my FRD-L14 (64GB US honor 8) running stable with B360 firmware (released 02-13-17) bootloader unlocked, SU flashed via TWRP.
I wanted to try the latest B385 OTA firmware flash so I used fastboot to flash my current stock B360 System.img, boot.img, and recovery.img to be sure I am running all stock boot/system files before flashing the B360 OTA.
I rebooted from fastboot successfully and continued with the OTA interface to install latest system update, it rebooted into Huawei recovery interface, verifying, installing, and then fails to verify and install.
Do I really have to lock the bootloader and wipe the entire phone in order to install latest OTA and then re-unlock bootloader, reflash twrp, and restore data ?
Thanks !
Well, that wasn't hard.
I used the "download latest full package" in the top-right menu of the OTA updates screen. This successfully installed B385 OTA update package for me without failure, while bootloader unlocked. Imagine that. I hope this helps someone else! Now, to figure out how to use magisk rather than supersu....
[remove, accidental doublepost]
I have the FRD-L04 32GB US model and im wondering why I havent had the update yet
I did revert to stock boot loader and unrooted im on 360 at the moment but no updates.
crowruin said:
I have the FRD-L04 32GB US model and im wondering why I havent had the update yet
I did revert to stock boot loader and unrooted im on 360 at the moment but no updates.
Click to expand...
Click to collapse
I just got the new update
mine26135 said:
I just got the new update
Click to expand...
Click to collapse
same here hahaha updating now.
About a year ago I downgraded my quark to android 4.4.4, though it started an automatic update to marshmallow, and after it finished, I was presented with this (picture is in a attachment) afaik the bootloader is or was unlocked. I tried flashing stock but it fails.
sambow23 said:
About a year ago I downgraded my quark to android 4.4.4, though it started an automatic update to marshmallow, and after it finished, I was presented with this (picture is in a attachment) afaik the bootloader is or was unlocked. I tried flashing stock but it fails.
Click to expand...
Click to collapse
You have to flash the same or newer firmware you had before you downgraded. Your bootloader is still whatever that is before you downgraded to 4.4.4.
The only way you can flash older is to leave off the bootloader as well as leave off gpt.bin. That's what you did when you went back to 4.4 4. But this automatic update was STILL probably older than what you were on a year ago. So, it borked your phone because it was flashing older bootloader and gpt.bin files.
Sent via open market LG US998 V30/V30+
I came from a custom rom, so i guess that means I'm out of luck since i can't flash twrp.
sambow23 said:
I came from a custom rom, so i guess that means I'm out of luck since i can't flash twrp.
Click to expand...
Click to collapse
I didn't say anything about flashing TWRP.
When you downgraded to stock 4.4.4 you didn't use TWRP. Flash the stock firmware the normal way.
You flashed stock firmware, but had to leave off bootloader and gpt.bin.
When you allowed the automatic update to happen (to older Marshmallow than what you had before you downgraded), you broke that rule.
Sent via open market LG US998 V30/V30+