I have an unlocked, rooted (Chainfire SuperSU) Nexus 6 running LMY48I with TWRP as recovery. Today, my Google FI SIM card is arriving in the mail. I would like to do the following:
* Switch to LVY48E (5.1.1 for FI)
* Ensure the resulting ROM is rooted
* Avoid losing existing apps and settings
My plan is to perform the following in order:
* Download LVY48E (shamu-lvy48e) from the Google factory images site to my laptop
* Boot to bootloader
* Flash the radio.img with fastboot
* Reboot to bootloader
* Flash the boot.img with fastboot
* Reboot to bootloader
* Clear the caches with fastboot
* Flash system.img with mfastboot (have had problems with large files previously)
* Flash cache.img with fastboot
* Power down
* Insert new FI SIM card
* Boot normally
* Reboot to TWRP recovery
* Root the device with TWRP
* Reboot normally (all done)
In the steps above, I am not flashing recovery.img (to maintain TWRP) and not flashing userdata.img (to keep my existing apps and settings).
Does the above sound like a sensible plan of attack? Am I inserting the SIM card at the right point? There was information on other forum posts about allowing the phone to boot normally once without using TWRP to root so the system partition is set up properly and then rooting on the next boot. Is that right? And finally, TWRP has previously given me an option to fix the system partition after I have flashed prior factory images. Should I allow it to do that? What is it fixing?
Much obliged, looking forward to enjoying a Nexus with FI! And thanks to XDA for such a great resource and for all the time everyone has put into making these flashes a less intimidating process for novices like me.
- Saschter
You can just power off, put the sim in, power on and download the Project Fi app the way you are now. Or are you just wanting to start fresh for some reason?
obtained said:
You can just power off, put the sim in, power on and download the Project Fi app the way you are now. Or are you just wanting to start fresh for some reason?
Click to expand...
Click to collapse
Thanks for the quick response. I assumed that I needed the full blown FI android factory image (or at least the radio) and that OTA would not work since I am rooted. There is simply an app to install? Is that the only difference between LMY48I (5.1.1 AT&T) and LMY48E (5.1.1 FI)? If yes, that is great news.
Saschter
Similar question. I'm on T-mo LYZ28J 5.1.1. Do I need to flash the Fi rom to get full support for Fi? My guess would be yes, but I'm asking anyway.
Saschter said:
Thanks for the quick response. I assumed that I needed the full blown FI android factory image (or at least the radio) and that OTA would not work since I am rooted. There is simply an app to install? Is that the only difference between LMY48I (5.1.1 AT&T) and LMY48E (5.1.1 FI)? If yes, that is great news.
Saschter
Click to expand...
Click to collapse
Fi should activate and work just fine on both of those builds. Pure Nexus is great and works very well with Fi if that's something you would want to do.
Groid said:
Similar question. I'm on T-mo LYZ28J 5.1.1. Do I need to flash the Fi rom to get full support for Fi? My guess would be yes, but I'm asking anyway.
Click to expand...
Click to collapse
Fi should work fine LYZ28J. I'm not too sure of it, but I think if you wan't the best customer support from the Fi support team, they would recommend using the Fi factory image, but most other builds work just fine with Fi.
obtained said:
Fi should activate and work just fine on both of those builds. Pure Nexus is great and works very well with Fi if that's something you would want to do.
Fi should work fine LYZ28J. I'm not too sure of it, but I think if you wan't the best customer support from the Fi support team, they would recommend using the Fi factory image, but most other builds work just fine with Fi.
Click to expand...
Click to collapse
Thanks so much @obtained. If we do want to flash to the FI ROM, do the above steps sound reasonable? FWIW, I will try first with my existing ROM and see how that goes.
Thanks again,
Saschter
Saschter said:
Thanks so much @obtained. If we do want to flash to the FI ROM, do the above steps sound reasonable? FWIW, I will try first with my existing ROM and see how that goes.
Thanks again,
Saschter
Click to expand...
Click to collapse
The above steps should work flawlessly.
No need for all the reboot to bootloaders or the mfastboot.
obtained said:
The above steps should work flawlessly.
Click to expand...
Click to collapse
Scwheeet. Thanks.
Saschter
prdog1 said:
No need for all the reboot to bootloaders or the mfastboot.
Click to expand...
Click to collapse
Good to know. Thanks. I have had to use mfastboot in the past as flashing the image (or the full zip file) results in a buffer overflow error with vanilla fastboot (even the latest version from the platform tools). The only reliable way I have handled truly large files to flash (at least for Motorola) devices has been mfastboot, but will try again and let you know.
Thanks,
Saschter
Saschter said:
Good to know. Thanks. I have had to use mfastboot in the past as flashing the image (or the full zip file) results in a buffer overflow error with vanilla fastboot (even the latest version from the platform tools). The only reliable way I have handled truly large files to flash (at least for Motorola) devices has been mfastboot, but will try again and let you know.
Thanks,
Saschter
Click to expand...
Click to collapse
Never have used mfastboot so don't know. I just use the one in SDK.
Just to wrap this thread up. I did not need to flash to enable my rooted (nearly stock) 5.1.1 to use FI. As indicated earlier, simply inserting the SIM card, powering up, downloading the Project FI app and then following the instructions in the app were enough to get everything working. (Note, it took 40 minutes or so for AT&T to switch my cellular over to the new SIM).
I separately then flashed everything as indicated in the beginning of this thread. The only gotcha was that TWRP had to be re-flashed (not sure why, since I did not flash recovery.img). However, that was relatively painless. Then rooted via TWRP, ran the SuperSU re-install process, then rebooted and all is now well.
Thanks to everyone who replied.
- Saschter
Saschter said:
Just to wrap this thread up. I did not need to flash to enable my rooted (nearly stock) 5.1.1 to use FI. As indicated earlier, simply inserting the SIM card, powering up, downloading the Project FI app and then following the instructions in the app were enough to get everything working. (Note, it took 40 minutes or so for AT&T to switch my cellular over to the new SIM).
I separately then flashed everything as indicated in the beginning of this thread. The only gotcha was that TWRP had to be re-flashed (not sure why, since I did not flash recovery.img). However, that was relatively painless. Then rooted via TWRP, ran the SuperSU re-install process, then rebooted and all is now well.
Thanks to everyone who replied.
- Saschter
Click to expand...
Click to collapse
So were you able to flash system with fastboot or did you use mfastboot? When I flashed the T-mo LYZ28J it failed with fastboot, but flashed with mfastboot. Maybe I don't have the latest fastboot. Anyone who flashed system with fastboot, please let me know the version of fastboot. Mine is March 13,2015 @ 196,608 bytes.
Groid said:
So were you able to flash system with fastboot or did you use mfastboot? When I flashed the T-mo LYZ28J it failed with fastboot, but flashed with mfastboot. Maybe I don't have the latest fastboot. Anyone who flashed system with fastboot, please let me know the version of fastboot. Mine is March 13,2015 @ 196,608 bytes.
Click to expand...
Click to collapse
Flashed with mfastboot as well. Have never been able to flash on my Nexus 6 with vanilla fastboot, even the most recent version from platform-tools.
Saschter
Related
I'm having issues flashing factory images for 5.1.0 LMY47D & LMY47E (tried both) from my ubuntu box. Every time I try these images, I see this:
Code:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
and then end up with:
Code:
sending 'system' (1736396 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
Boot loader on "Device is UNLOCKED Status Code: 3" and I've updated fastboot to the best of my knowledge, using Android Studio SDK Manager, as well as ran apt-get update. Bootloader version is moto-apq8084-71.08. I did an md5sum on the .tgz files and confirmed I'm not getting a bad download on either. After extracting I removed the -w from
Code:
fastboot -w update image-shamu-LMY47D.zip
in the flash-all.sh file, really would rather not wipe, but if someone tells me there's a valid reason I need to, I'll do it. I do not have encryption turned off.
This leaves my phone in an unusable state due to the partial flash, so I'm about to FDR it, but was hoping someone could help first.
Have you tried flashing each image manually?
jfcooley said:
Have you tried flashing each image manually?
Click to expand...
Click to collapse
That was a good idea, just tried it. no dice:
Code:
****@Ubuntu-Media:~/Downloads/shamu-lmy47e$ fastboot flash system system.img
sending 'system' (1736380 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
I just read something about how I might need to use mFastboot made by motorola... trying that now
You have to unzip. Fastboot flashes IMG.
When you download the factory image you unzip, should leave you with 2 image files and another .zip. You have to unzip that as well. It contains the rest of the img you need to manually flash.
jfcooley said:
You have to unzip. Fastboot flashes IMG.
When you download the factory image you unzip, should leave you with 2 image files and another .zip. You have to unzip that as well. It contains the rest of the img you need to manually flash.
Click to expand...
Click to collapse
yeah, sorry realized that seconds after I posted... edited my original post, sorry for thread confusion.
So after a few other mistakes I'd rather not own up to, I figured out that yes, mFastBoot was the solution to my issue. I'm not sure why I can't find any other folks posting about needing it for 5.1 builds on the the N6, but I did. I never needed it before 5.1, but I'm assuming the system.img file has grown larger than the standard SDK fastboot supports. I'm wondering if this is only an issue when flashing from linux. Theoretically, it should not be though; this issue is based on the memory available on the device (tmo N6, btw).
For those that don't know, "mFastboot" aka Motorola Fastboot is a tweaked version of fastboot provided by Motorola. It will actually split up the image and flash it in pieces.
Here are Instruction for installing and using mFastBoot to flash a Moto G on linux, but the process is the same, except for the images obviously. You'll have to either modify the flash-all.sh file or do each of the images manually.
Hope this helps someone else... it would be really weird if I'm the only one that runs into this.
GoldPaintedLemons said:
So after a few other mistakes I'd rather not own up to, I figured out that yes, mFastBoot was the solution to my issue. I'm not sure why I can't find any other folks posting about needing it for 5.1 builds on the the N6, but I did. I never needed it before 5.1, but I'm assuming the system.img file has grown larger than the standard SDK fastboot supports. I'm wondering if this is only an issue when flashing from linux. Theoretically, it should not be though; this issue is based on the memory available on the device (tmo N6, btw).
For those that don't know, "mFastboot" aka Motorola Fastboot is a tweaked version of fastboot provided by Motorola. It will actually split up the image and flash it in pieces.
Here are Instruction for installing and using mFastBoot to flash a Moto G on linux, but the process is the same, except for the images obviously. You'll have to either modify the flash-all.sh file or do each of the images manually.
Hope this helps someone else... it would be really weird if I'm the only one that runs into this.
Click to expand...
Click to collapse
just fyi, fastboot works fine with all the factory images google puts online but you have to use the latest version. it's available as part of the Android sdk and is included with Android studio.
PhilDX said:
just fyi, fastboot works fine with all the factory images google puts online but you have to use the latest version. it's available as part of the Android sdk and is included with Android studio.
Click to expand...
Click to collapse
Thanks, but if you read my original post you'll see I did that and more. Not saying you're wrong, but unless someone can tell me specifically a step in that process I apparently missed, I think there might be exceptions to that rule.
GoldPaintedLemons said:
Thanks, but if you read my original post you'll see I did that and more. Not saying you're wrong, but unless someone can tell me specifically a step in that process I apparently missed, I think there might be exceptions to that rule.
Click to expand...
Click to collapse
guilty as charged
I see now that you're on Linux, I use a Windows box so that's probably the difference. glad to see you found a solution.
GoldPaintedLemons said:
Thanks, but if you read my original post you'll see I did that and more. Not saying you're wrong, but unless someone can tell me specifically a step in that process I apparently missed, I think there might be exceptions to that rule.
Click to expand...
Click to collapse
On Windows with virtually the exact same issue. I went back to 5.0.1 but the bootloader is stuck on the newer version and can not be modified. I do not use ADB manually anymore. I use toolkits these days and then try manually. Now I'm stuck on 5.0.1 and can not update the OS at all. I get some message when attempting to ADB-Sideload the 5.1m T-Mo OTA saying that "a file located at dev/block/msm.... Has been changed to R/W. Reflash and reboot to regain OTA privilege."
Only issue is I am on a LRX22C Factory Image with Stock recovery. Any help or questions will be welcomed.
PhilDX said:
guilty as charged
I see now that you're on Linux, I use a Windows box so that's probably the difference. glad to see you found a solution.
Click to expand...
Click to collapse
Google images flash perfectly fine in Linux with fastboot.
Sent from my Nexus 6 using XDA Free mobile app
Freshly_Snipes said:
On Windows with virtually the exact same issue. I went back to 5.0.1 but the bootloader is stuck on the newer version and can not be modified. I do not use ADB manually anymore. I use toolkits these days and then try manually. Now I'm stuck on 5.0.1 and can not update the OS at all. I get some message when attempting to ADB-Sideload the 5.1m T-Mo OTA saying that "a file located at dev/block/msm.... Has been changed to R/W. Reflash and reboot to regain OTA privilege."
Only issue is I am on a LRX22C Factory Image with Stock recovery. Any help or questions will be welcomed.
Click to expand...
Click to collapse
I'm not a T-Mobile guy but based on the posts I've come across, the radio in the M update is 95R. since you can't take the OTA now with the boot loader issue, one option may be to flash the D or E factory image to get back onto 5.1. either way I think you want the 95R radio included with D, not the 98R included with E. I have to believe the M update will be released as a factory image at some point or something newer will be released.
GoldPaintedLemons said:
So after a few other mistakes I'd rather not own up to, I figured out that yes, mFastBoot was the solution to my issue. I'm not sure why I can't find any other folks posting about needing it for 5.1 builds on the the N6, but I did. I never needed it before 5.1, but I'm assuming the system.img file has grown larger than the standard SDK fastboot supports. I'm wondering if this is only an issue when flashing from linux. Theoretically, it should not be though; this issue is based on the memory available on the device (tmo N6, btw).
For those that don't know, "mFastboot" aka Motorola Fastboot is a tweaked version of fastboot provided by Motorola. It will actually split up the image and flash it in pieces.
Here are Instruction for installing and using mFastBoot to flash a Moto G on linux, but the process is the same, except for the images obviously. You'll have to either modify the flash-all.sh file or do each of the images manually.
Hope this helps someone else... it would be really weird if I'm the only one that runs into this.
Click to expand...
Click to collapse
You're not alone. I spent over 11hrs trying to get one or the other to flash too using a Mac with OS v10.10.2 and had the exact same issues. Found an mfastboot and was able to flash the images separately (flash-all.sh still failed).
Glad we're both all set... Now to delete the Android SDK and Java files!
X
Nexus 6 via Tapatalk
Freshly_Snipes said:
On Windows with virtually the exact same issue. I went back to 5.0.1 but the bootloader is stuck on the newer version and can not be modified. I do not use ADB manually anymore. I use toolkits these days and then try manually. Now I'm stuck on 5.0.1 and can not update the OS at all. I get some message when attempting to ADB-Sideload the 5.1m T-Mo OTA saying that "a file located at dev/block/msm.... Has been changed to R/W. Reflash and reboot to regain OTA privilege."
Only issue is I am on a LRX22C Factory Image with Stock recovery. Any help or questions will be welcomed.
Click to expand...
Click to collapse
Have you tried using mFastboot (just google it the windows exe is easily found)? You'll need to use that and flash each .img separately.
THANK YOU
I've been working with this off and on for some time, and your post was immensely helpful.
Latest fastboot drivers, latest ADB (truly the latest, not just apt-get-whatever). Same issue - system.img would not flash. Not with a script, not standalone, not in the zip file, nothing. What I see (almost constantly) is a buffer issue where the actual size of system.img is throwing a significant error with fastboot drivers. mFastboot (as you provided) on the other hand, utilizes a component called "sparse-flash", which appears to break large files into smaller (256mb) chunks that for whatever reason my N6 preferred. No issues with flashing after that, but again it must be done individually (system, boot, radio, etc.) - never as a zip with "-w update".
I find it curious that so few people have this issue (others can use the "normal" fastboot with large system files and no issue occurs). Those who do run into this problem seem to know their way around a terminal, so it makes me wonder what the underlying difference between us is.
For the record, I was on a machine running Mint 17.2, which is essentially Ubuntu 14.04.
Just really wanted to say thank you and hopefully promote the thread a bit to help others. Especially as many of us are flashing to bone stock momentarily to properly activate Project Fi.
@caain,
A couple of points/questions:
1) You mention having the latest fastboot "drivers". I'm not sure what you are referring to, but I've never heard of such a thing on Linux.
2) Where did you get ADB and fastboot from? Did you download the latest Android SDK?
2a) The point here, is that Google updated fastboot in November of last year to enable flashing the very large system.img from Lollipop. You can only get this necessary version of (if your are running Linux) fastboot via the Android SDK.... And without it, you can not successfully flash a Lollipop system.img.
cam30era said:
@caain,
A couple of points/questions:
1) You mention having the latest fastboot "drivers". I'm not sure what you are referring to, but I've never heard of such a thing on Linux.
2) Where did you get ADB and fastboot from? Did you download the latest Android SDK?
2a) The point here, is that Google updated fastboot in November of last year to enable flashing the very large system.img from Lollipop. You can only get this necessary version of fastboot via the Android SDK.... And without it, you can not successfully flash a Lollipop system.img.
Click to expand...
Click to collapse
You can flash the system image manually with fastboot. Can't fastboot flash the flash-all.bat without SDK 23+ platform tools. System image will fail. The 15 second adb/fastboot is not updated to achieve this. Not sure about Linux but if have latest SDK updated it will do the flash-all.bat.
none
I flashed M just to check it out, but prior to doing that I grabbed the SDK that had very recently updated to include the 6.0 M files, so I updated the 6.0 SDK prior to trying M, and when I went back I had zero issues with the flash.bat The only issue I had which was more of a pain than a problem is that flashing the factory image it unrooted the phone so I had to completely set up the phone all over again.
No more M for me until it's released because in the preview 3 not every component is functional, why they would do that I have no idea, so after learning that M wasn't complete I abandoned it. Hope this helps if you want to go back
cam30era said:
@caain,
A couple of points/questions:
1) You mention having the latest fastboot "drivers". I'm not sure what you are referring to, but I've never heard of such a thing on Linux.
2) Where did you get ADB and fastboot from? Did you download the latest Android SDK?
2a) The point here, is that Google updated fastboot in November of last year to enable flashing the very large system.img from Lollipop. You can only get this necessary version of (if your are running Linux) fastboot via the Android SDK.... And without it, you can not successfully flash a Lollipop system.img.
Click to expand...
Click to collapse
I suppose I use the word "drivers" a bit too flippantly, as you are correct and there is most certainly not a fastboot "driver" for linux. Perhaps the issue I was running into is that I was merely installing ABD and fastboot standalone, without including the entire Android SDK. In which case I ought to feel quite foolish!
Thank you for the clarification regarding the patch from November. I've no need for fastboot in the immediate future, but will certainly make sure install the SDK as a whole rather than pulling tools from other repositories in the future.
caain said:
I've no need for fastboot in the immediate future, but will certainly make sure install the SDK as a whole rather than pulling tools from other repositories in the future.
Click to expand...
Click to collapse
That's a very good idea. I would suggest doing this soon, so it's set up and ready to go when you need it.
Hello,
This is a short (hopefully) guide on how to downgrade your Moto X 2013 from Android 5.1 to 4.4.4 (and lower).
The procedure is fairly simple and takes about 10-15 minutes, once you get the files you need.It does however needs some technical understanding of how to use fastboot, command prompt and eventually unlocking your bootloader.Fairly strong reading skills recommended.
WIth that said, make sure you read thorough and even few times before you take any actions.
This method has now been proven to be working by multiple people, on many different versions of Moto X 2013, including GPE
Disclaimer
Although this procedure has been tested by me and some friends numerous times, it still has some risk involved.You MUST be aware of the potential risks of modifying your phone software and performing actions that may lead to complete defunct of your device.
As you may expect I will not take any responsibility or be accountable for any damage or loss you may incur by following this guide.
Performing a system downgrade WILL void your warranty and it is NOT supported by Motorola/Lenovo or their service network.
I also recommend you read This post by KidJoe about the potential risks that downgrade might involve.
This guide has came up being needed as many people were afraid to downgrade after reading the post of KidJoe and I don't blame them, it is possible something to go wrong and you end up with non-working device.
HOWEVER, this has been tested on more than 10 separate Moto X 2013 and more than 12 times on my own device, which makes me to believe that it's generally safe.
Prerequisites
You need your bootloader unlocked.Motorola and their bootloader does NOT support downgrading and it will spit errors in fastboot.
WHEN YOU UNLOCK YOUR BOOTLOADER ALL YOUR PERSONAL DATA ON YOUR DEVICE WILL BE LOST.MAKE SURE YOU BACKUP YOUR FILES AND THEN PROCEED.
You can find how to unlock your bootloader HERE or just use the search here in the forums, plenty of info on that matter.
If you cannot or don't want to unlock your bootloader, then you CANNOT downgrade.
Files Needed
For this tutorial we`ll do downgrade from 5.1 to 4.4.4.This is the safest downgrade and it will be successful if you follow all the steps w/o any skipping.
The Android image used is for XT1052, but if you got different model, you can find the image for your own model and use that instead.
1.First you need a signed image of Android 4.4.4 for Moto X 2013.You can find one Filefactory or RetailEU here <=> RetailGB here <=> RetailDE here
If you want to download the image faster, use the Yandex-hosted images, FileFactory is slow.
2.Motorola Device Drivers: You can find them Here
3.Motorola Fastboot and generic adb/fastboot tools package: You can find it attached to this post or click Here
Flashing your device
0.Charge your device's battery to at least 35%.
1.Extract the archive with the signed images somewhere (in this case I`ll use C:\temp , but you can use any drive or directory if you so desire).
2.Extract the android-tools archive in the same directory.You should have boot.img, recovery.img, system.img and mfastboot in same directory.
3.Reboot your device in bootloader (Power your device off -> Hold Volume Down and Press Power button -> then release).
!!THIS WILL DELETE YOUR USER FILES EVEN IF YOU HAVE YOUR BOOTLOADER ALREADY UNLOCKED!!!
4.Open a command prompt and navigate to C:\temp and execute the following commands:
Code:
mfastboot erase cache
mfastboot erase userdata
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot erase userdata
mfastboot reboot
DO NOT skip erasing the userdata, doing so , you'll most likely end up with soft brick.Just don't do it.
Result
Congratz, now you have successfully downgraded your device to Android 4.4.4
The device will take some time the first boot to create dalvik cache and some other stuff, but it should not take more than 5 minutes.
When your device boots, it will ask you at some point to downgrade the motorola services bla bla, agree to that, your device will reboot and it will tell you that the downgrade was successful.I did this more than 10 times, seems to be totally safe.
Any feedback will be appreciated, you may ask questions, but don't expect me to answer to every single one.
If I missed something, I'll add up/fix as soon as I can.
FAQ
What if I want to downgrade to Android 4.4.2 / 4.3 / 4.2.2 ?
This is possible, the procedure is the same as listed above.You just have to know that if you do such downgrade, you should never update via OTA update, at any cost.This will corrupt the bootloader of your device and you won't be able to restore it.If you downgrade to anything below 4.4.4 and you want at some point to upgrade, you should do it ONLY by official signed image and NOT OTA.
You've been warned.
I can't find the exact same firmware that my device runs, eg. AsiaRetail.Is it possible to use firmware image from a different region/operator?
While it's recommended to use your exact firmware image, it is not necessary. You can use an image from other region, but you should follow some simple rule. Try to stick to the same phone model, eg XT1052 firmware.
I updated via OTA but I've recently rooted and installed a custom rom. Is it necessary to go back to stock 5.1 to downgrade?
No need, as long as your custom rom/kernel didn't mess with the fs of the partitions.
Why is this flashing procedure cut down, omg there are other commands that I've read in other guides and they say that I must flash modem, fsg, delete some magical modem states, why you didn't include these?!?
While it is true that other guides suggest you flash modem, fsg and some other things, these are mainly driven from the Motorola's own procedure xml file, flashing these is not necessary at all, this is used to repair eventual errors in these parts, but usually there is no problem there at all.
Another thing is that these parts are cross-compatible and leaving them as they are is perfectly fine.
How do I go back to 5.1 stock?
1.Do NOT update by OTA, just to be on the safe side.
2. Use the same procedure as described, but with image of 5.1 instead.
How do I disable the OTA notifications?
1. If you're rooted, then just delete or revoke permissions of /system/priv-app/3c_ota.apk
2. If you're not rooted, then don't install the Motorola Update Services from the Play Store. If you already updated them, then just uninstall the update and that's all.
I'm getting "Not enough space" errors, when I try to flash the system.img.I'm using mfastboot, but still the same problem?!?
Use this and it will work:
mfastboot flash system system.img -P
What if I have a custom recovery? Sorry I'm new to this stuff. Which mode do you enter before entering the commands in cmd prompt?
legend.in.boxers said:
What if I have a custom recovery? Sorry I'm new to this stuff. Which mode do you enter before entering the commands in cmd prompt?
Click to expand...
Click to collapse
Having custom recovery doesn't affect anything. This process will flash the stock recovery.
You don't need to enter any mode in the list, just leave the phone in the bootloader menu.
Hello.
I just might use this method to downlograde from 5.1 to 4.4.4...
I have the always mobile radio active bug while being connected to wifi, so my stand by time with wifi is just awful.
Thanks.
SanD-82 said:
Hello.
I just might use this method to downlograde from 5.1 to 4.4.4...
I have the always mobile radio active bug while being connected to wifi, so my stand by time with wifi is just awful.
Thanks.
Click to expand...
Click to collapse
I had the same issue, wifi would never go sleep. RAM management is horrific and the YouTube app was causing some troubles with the sound module, at some point the sound was totally not working.
liveroy said:
I had the same issue, wifi would never go sleep. RAM management is horrific and the YouTube app was causing some troubles with the sound module, at some point the sound was totally not working.
Click to expand...
Click to collapse
I also have a problem with the optimising apps bug every time I reboot. Going to downgrade today. Hopefully everything will go well
liveroy said:
I had the same issue, wifi would never go sleep. RAM management is horrific and the YouTube app was causing some troubles with the sound module, at some point the sound was totally not working.
Click to expand...
Click to collapse
Actually, that's not what's happening to me... Wifi is active only when connected to a network...
Now, what you are saying is that your wifi is always on?
Did you check in the advanced wifi properties the status of the 'always on' setting?... Because if you configured the location settings to use WiFi, then WiFi will be always on, even when you manually turn it off...
So, make sure you do not have that turned on...
Enviado desde mi XT1058
SanD-82 said:
Actually, that's not what's happening to me... Wifi is active only when connected to a network...
Now, what you are saying is that your wifi is always on?
Did you check in the advanced wifi properties the status of the 'always on' setting?... Because if you configured the location settings to use WiFi, then WiFi will be always on, even when you manually turn it off...
So, make sure you do not have that turned on...
Enviado desde mi XT1058
Click to expand...
Click to collapse
That's not the case either, it was set to never keep it on during sleep and scaning always available was not allowed.The wifi just wont go off durring sleep and that's it.Tried all possible settings to no avail.Actually wifi was the 2nd highest battery consumer in the stats after the screen.This problem does not exist in 4.4.4.
I see...
It's actually hard to see how in 2015, Android keeps having these deal breaker issues...
I somehow feel that the best version of my xt1058 was when it was at 4.2.2... After the subsequent updates, bugs started to appear, and on 5.1 i got the first big issue...
Sent from my XT1058
Works!
Successfully downgraded. Thank you so much!
What would i have to be aware of in the future if i do this?
Of course, no OTA install for 5.1...
Before making any 'stock upgrade' or something **** that, i would have to flash the 5.1 full firm right?
Sent from my XT1058
SanD-82 said:
What would i have to be aware of in the future if i do this?
Of course, no OTA install for 5.1...
Before making any 'stock upgrade' or something **** that, i would have to flash the 5.1 full firm right?
Sent from my XT1058
Click to expand...
Click to collapse
Basically if you are on 4.4.4, shouldn't be any problem to update back to 5.1 even via OTA.But since the images for 5.1 are available, I wouldn't suggest OTA update anyway.
For future updates, when Android M is out for example, just update to 5.1 using fastboot, then update through the OTA.
Other than that, there are no other potential problems that might arise, at least nothing that I can think of.
IS Android 4.4.2 or 4.2.2 files avalable for indian moto x (xt1052 asian retail)
liveroy said:
Basically if you are on 4.4.4, shouldn't be any problem to update back to 5.1 even via OTA.But since the images for 5.1 are available, I wouldn't suggest OTA update anyway.
For future updates, when Android M is out for example, just update to 5.1 using fastboot, then update through the OTA.
Other than that, there are no other potential problems that might arise, at least nothing that I can think of.
Click to expand...
Click to collapse
WHere can i find those files??
visheshjotshi said:
WHere can i find those files??
Click to expand...
Click to collapse
Check the first post, the File Factory link, you can find tons of images there, the moto x 2013 is codenamed Ghost, if there is no model listed.
Good Luck.
Cant find files
File factory doesnt have files for asian retail other than android 4.4.4 file can i find it any where else?????
How many people frm india have sucessfully downgraded thier phones??
visheshjotshi said:
File factory doesnt have files for asian retail other than android 4.4.4 file can i find it any where else?????
How many people frm india have sucessfully downgraded thier phones??
Click to expand...
Click to collapse
Try searching 4pda.
Also, you don't need exactly your original firmware to begin with, it's recommended, but not necessary.
Thank you for this information. I dont have the wifi bug. But i have the mobile data bug. (Even turning it off it still continues to sap battery)
Sent from my XT1052 using XDA Free mobile app
I was looking for a post like this becouse my WiFi doesn't work on XT1058 5.1... i thought was a Lollipop related issue so wanted to downgrade to 4.4.4 and see if the problem really was related to android version, but it isn't. I downgraded successfully from 5.1 to 4.4.4 with your tutorial, but the WiFi problem persist. Now i know i'm really screwed up becouse i tried i believe everything possible... airplane mode, factory reset, cache wipe, full wipe, custom rom, custom kernel, android 5.1, android 4.4.4, different AP's and routers, delete supplicant conf... So i don't know what to do. Te specific problem is that WiFi can see available networks, but randomly some of them disappear and others show up, and when i try to connect por ex to my home network, it says "connecting" and then "saved", with all networks happens the same. Does anyone has a clue? BTW, thanks for your post!
Download the archive from this link https://app.box.com/s/idnxxhunecvtxf1mbqve0bpooyogvxng
unzip it on your device and copy the files to /persist.You need root to do that. Set the permissions to rw-r-r--- and rw-rw---- for the .bt_nv.bin
Reboot and see if something changes.
Don't you hate it when you flash something and it puts you in an unrecoverable state?
Does it aggravate you to no end when you flash something and then all you can do is go into bootloader and nothing else?
Well, have no fear Motorola Z2 Force users! Your issues will be resolved!
Reasons for using this method:
If you haphazardly flashed a ROM, and now can't boot.
If you tried flashing an audio mod and have issues getting things to work.
If you accidentally (or purposefully) deleted a file and now can't OTA.
Anything else that you can do to soft brick your device.
This zip will fix that and put you back to stock.
You then can update.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits:
Motorola Firmware Team for the zips
Great, So you've read why you might have borked your phone!
Now, let's get it fixed! Below is the link to the only flashall bat file I currently have. This is a simple process to do. There are some requirements though.
Requirements:
Correct drivers (ADB and fastboot is included in the utilities zip if you don't have minimal adb and fastboot installed, or don't have the SDK.)
Over 4GB of RAM.
How to fix your phone:
Download the Utilities zip
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
This process can take up to 10-15 minutes depending on USB connection and your PC
Disclaimer: I did not personally test the zips below besides the Sprint and T-Mobile ones. These are the official Firmware links from the Motorola Firmware Team. My only contribution is this thread and the utilities zip.
Disclaimer 2: it is never suggested to flash a zip not intended for your device/major patch version. If you're on Oreo, DO NOT FLASH NOUGAT. (I flashed T-Mobile to my Sprint phone for testing purposes and so I can tell you what it does. I lost all sim functionality and had to do some wonky stuff to get my phone back to working shape... Word of advise: don't do it.)
Disclaimer 3: if you have minimal adb and fastboot or the Android SDK, please be sure you update to the latest fastboot. The exe files included in the zip are for those who don't have a development environment set up.
Downloads:
Flash All Utilities
AT&T Oreo Flash All
Sprint Oreo Flash All
T-Mobile Flash All (Not official download link, but official files, See here)
USC (check version) Flash All
Verizon Flash All
NOTE: yes, it's in the Z2 play folder. Motorola Firmware Team did not make another folder for our device. Check the file name. It has "Nash" specifying the Z2 force. If you ask why it's in the Play folder, I will not respond.
If you have any other official links, I will add to second post and give proper credits to who found the zip. Only perm links like the AFH ones I posted.
Uzephi said:
First: The Sprint variant is different than the AT&T and T-Mobile phone as it is GSM/CDMA. This means it's baseband, oem, and boot.img are different. Boot is slightly different, but oem and baseband is completely different.
If you haphazardly flashed a T-Mobile ROM, you might find out that after wiping oem, you cannot get mobile data to work.
This zip will fix that and put you back to stock on the "August" security patch (September update). You then can update to the "September" security update that came out in October.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits: Motorola Firmware Team for the zips
Me for modifying the zip to fix oem.img issue on B partitions and turning the xml into a simple flash all.bat
Note: I am mobile and I will clean up the OP and second post when I get time @ home
Click to expand...
Click to collapse
I was going to add yours in but kinda got busy
Thanks for this! I flashed a modified boot.img for root to get my phone unlocked, and flashed the stock kernel back, but I couldn't update to the September patch. After flashing this, updates are working fine. A bit of a lifesaver!
full circle...
i went from stock, to rooted to soft bricked and hopefully after these download ill be back at stock... thanks for all your hard work ...payday ill buy ya beer!
esuormai said:
i went from stock, to rooted to soft bricked and hopefully after these download ill be back at stock... thanks for all your hard work ...payday ill buy ya beer!
Click to expand...
Click to collapse
I don't take donations, just pay it forward! Thanks for the offer though.
NOTE: make sure your computer has more than 1 GB ram when you flash this you will get a buffer error because this requires a lot of memory I MADE THIS MISTAKE
WeUseLord- said:
NOTE: make sure your computer has more than 1 GB ram when you flash this you will get a buffer error because this requires a lot of memory I MADE THIS MISTAKE
Click to expand...
Click to collapse
Added in requirements, thank you for verifying that.
Uzephi said:
Added in requirements, thank you for verifying that.
Click to expand...
Click to collapse
Okay thanks OP
when i did this (i did this so that i could go back to stock with a locked bootloader which as of writing i just realized would work fine if i just did fastboot oem lock without anything else, goddamnit) it told me that a different operating system had been installed, even though it's (presumably) the same os. what's going on?
cooleoboom5 said:
when i did this (i did this so that i could go back to stock with a locked bootloader which as of writing i just realized would work fine if i just did fastboot oem lock without anything else, goddamnit) it told me that a different operating system had been installed, even though it's (presumably) the same os. what's going on?
Click to expand...
Click to collapse
That is a "permanent" flag that triggers when you flash something unsigned and not from Motorola. I.E. custom boot image for root. Reason it's in quotes is because we don't know how to return it back or if we even can.
moto z2 force
WeUseLord- said:
Okay thanks OP
Click to expand...
Click to collapse
where do you download the bat file from
irule1977 said:
where do you download the bat file from
Click to expand...
Click to collapse
It's in the zip
So Sprint Z2 can't get GSM unlocked by flashing ROMs from other carriers? Any idea how it can be unlocked?
How to get back to software status official in bootloader menu? I did managed to do it with T-Mobile version but cant get that from this one.
Uzephi said:
Don't you hate it when you flash something and it puts you in an unrecoverable state?
Does it aggravate you to no end when you flash something and then all you can do is go into bootloader and nothing else?
Well, have no fear Sprint Motorola Z2 force users! Your issues will be resolved!
First: Our phone differences
The Sprint variant is different than the AT&T and T-Mobile phone as it is GSM/CDMA.
This means it's baseband, oem, and boot.img are different. Boot is slightly different, but oem and baseband is completely different.
Reasons for using this method:
If you haphazardly flashed a T-Mobile ROM, you might find out that after wiping oem, you cannot get mobile data to work.
If you tried flashing an audio mod and have issues getting things to work.
If you accidentally (or purposefully) deleted a file and now can't OTA.
Anything else that you can do to soft brick your device.
This zip will fix that and put you back to stock on the "August" security patch (September update).
You then can update to the "September" security update that came out in October.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits:Motorola Firmware Team for the zips
Versions currently available:
NCXS26.122-59-8-6
NCX26.122-59-8
NCX26.122-51
Versions on OTA but no firmware files available:
NCXS26.122-59-8-9
Click to expand...
Click to collapse
Would you be able to make T-Mobile Stock? I've got flash all zips 7.1.1 but when flashing them I can't get any ota's. Every ota just failing on installation even via sideload. I've had multiple carriers ROMs installed on my device earlier looking the way to sim unlock it. Now my device unlock app failing to request unlock.
robdevil said:
Would you be able to make T-Mobile Stock? I've got flash all zips 7.1.1 but when flashing them I can't get any ota's. Every ota just failing on installation even via sideload. I've had multiple carriers ROMs installed on my device earlier looking the way to sim unlock it. Now my device unlock app failing to request unlock.
Click to expand...
Click to collapse
I would only release something I can test. I don't have TMobile service, so I won't be releasing TMobile only firmware. There is a thread by joemossjr for TMobile flashall.
A quick question sorry for newbie question in advance, I return to Motorola after a long years a lot changed
I got a Moto Z2 from a friend (he no have knowledge of rooting and modifying) which he got from his cousin in UK so when I got it seem it have a Tmobile sprint hybrid rom installed and google warning screen on the start, it is my guess it is Sprint's phone but I am not confirm.
XT-1789-03 is etched on the bottom near the and by search on google it is showing sprint so please if anyone can confirm -03 is sprint or not? imei is also showing the clean on the sprint site but it NOT definitely saying this phone is sprint.
Please someone tell me if I can flash this and get back to normal and get the OTA updates.
hackenggr said:
A quick question sorry for newbie question in advance, I return to Motorola after a long years a lot changed
I got a Moto Z2 from a friend (he no have knowledge of rooting and modifying) which he got from his cousin in UK so when I got it seem it have a Tmobile sprint hybrid rom installed and google warning screen on the start, it is my guess it is Sprint's phone but I am not confirm.
XT-1789-03 is etched on the bottom near the and by search on google it is showing sprint so please if anyone can confirm -03 is sprint or not? imei is also showing the clean on the sprint site but it NOT definitely saying this phone is sprint.
Please someone tell me if I can flash this and get back to normal and get the OTA updates.
Click to expand...
Click to collapse
My Sprint model has the -03 identifier. You should be safe if the bootloader is unlocked. Needs that to flash this
AS OF RIGHT NOW THIS IS ONLY FOR T-MOBILE AND NOW SPRINT!
This is a stock rom for the retail brazil MotoZ(2) force ported over to our phone.
This is stock with only encryption and dm verity removed for support with twrp. (No more boot image including.)
Flashing instructions.
NOTE: CLEAN FLASH! This is a rom from another phone. I cant help you if you write me and say system fc's or any other fc's and you didnt clean flash.
1. Download rom and place it on sd card or internal.
2. Download oem.img and flash it (fastboot flash oem oem.img)
3. Reboot to recovery
2. Wipe system data cache.
3 Flash rom.
4. Reflash whatever root you had. (Magisk)
5. Profit.
As far as I know this does have all the latest fixings (KRACK,Bluebourne, ECT)
Includes VOLTE
Includes WIFI Calling
Usually all roms are pretty stable. IF there is any bugs post below and ill get to working on it.
Sprint install guide
Guide for Sprint users:
Go into Bootloader
Flash This oem.img (courtesy @joemossjr) "fastboot flash oem oem.img
Go into recovery
wipe system and data.
Flash rom
Tested this on my Sprint phone and everything works just fine and with Pantheon, you will pass Safetynet if you flash the image in bootloader.
note: for Sprint users, we NEED to flash the oem.img to not have dialer issues, so I will stress, flash that oem image and if you don't want the bloat, you can delete everything but oem.prop from /oem folder through root or recovery's file manager after you mount OEM.
FLASH ALL
Flash all has been made this includes T-Mobiles Modem with stock everything else. you wont be able to take otas on it due to modified Modem. But updates for thes roms come a lot faster then ours so when one comes out ill update it. Please flash the latest twrp. This is going to encrypt you so your gonna have to format data in twrp and flash this Unencrypt Zip
This will format data. Treat it as a flash all to get back to stock also if you dont want tmobile bloat. This rom in it self with twrp will pass safetynet without magisk as long as you dont modify oem partition. Other then that happy flashing. Download for flash all is below
Downloads: November
oem.img
November Flash all
CREDITS
Motorola Firmware Team
@SuperR. for providing a bad ass platform for Rom making.
@Uzephi for testing the Sprint side of things lol
First! ?
Pantheon works on this rom.
Edit: kernel upstream has KRACK and blueborne fixes in it ?
Edit: tried same install instructions. Works for Sprint phones and activates them
Edit 3: well had to do some dialer stuff, but everything else worked. Will give guide in the morning to get the rom 100%
Sprint install guide
Guide for Sprint users:
Go into Bootloader
Flash This oem.img (courtesy @joemossjr) "fastboot flash oem oem.img
Go into recovery
mount oem. (you can delete everything using file manager in /oem besides oem.prop)
wipe system and data.
Flash rom
Tested this on my Sprint phone and everything works just fine and with Pantheon, you will pass Safetynet if you flash the image in bootloader.
Edit: for Sprint users, we NEED to flash the oem.img to not have dialer issues, so I will stress, flash that oem image and if you don't want the bloat, you can delete everything but oem.prop from /oem folder through root or recovery's file manager after you mount OEM.
Edit 2: Wifi Calling will not work, that file is in sprint's OEM partition and it FC's when adding it or using sprint's oem.img, so if you want this rom, I advise WiFi calling will not work until further notice.
updated thread
ADDED Stock oem image
ADDED Sprint support per @Uzephi
joemossjr said:
updated thread
ADDED Stock oem image
ADDED Sprint support per @Uzephi
Click to expand...
Click to collapse
WiFi calling currently doesn't work for Sprint. Technical details: Sprint uses a different WiFi calling setup where a special Google dialer is in /oem to work. If you use this dialer or the included wifi dialer.jar file, it will just continuously FC and you can't do anything. To get Sprint models working we have to use the stock dialer which doesn't work with Sprint's WiFi calling. We will put a poll up to see interest in WiFi calling since this will take a bit of hackery to get working. I want to gauge interest before I take on this task.
My new T mobile Moto Z2 Force still has stock August image on it. I am waiting for my screen protector and case to arrive before I transfer my account to this phone. I am also waiting to unlock the bootloader and root the device. Now, should I flash your new Nov image since I want KRACK and blueborne fixes OR should I first flash the August image first, then upgrade to Nov image.
kendallgreen said:
My new T mobile Moto Z2 Force still has stock August image on it. I am waiting for my screen protector and case to arrive before I transfer my account to this phone. I am also waiting to unlock the bootloader and root the device. Now, should I flash your new Nov image since I want KRACK and blueborne fixes OR should I first flash the August image first, then upgrade to Nov image.
Click to expand...
Click to collapse
Either or honestly lol you can go to August for the updated firmware
So going from a brand new device on NCX26.7, how do we go about getting our phones ready to flash this? Unlock bootloader, root, then flash this and reroot? Then follow the instructions for TWRP in your other post?
swidger said:
So going from a brand new device on NCX26.7, how do we go about getting our phones ready to flash this? Unlock bootloader, root, then flash this and reroot? Then follow the instructions for TWRP in your other post?
Click to expand...
Click to collapse
Unlock bootloader, install TWRP, follow instructions in OP.
Moto Z2 Force Edition - T-Mobile
Unlocked Bootloader
TWRP 3.2.0-0
I keep trying to flash this ROM, and have succeed in the flashing process. However, whenever I boot up, I get "TMOConfig has stopped" and then I can close it. I notice, that cellular data is not active. I continue through setup as normal until the Moto Permissions screen. When I try to go through this screen, whether I accept or decline, "com.motorola.tmo.setupext has stopped" comes up. The only option is to open app again and it takes me to the prior screen for Google setup and gets stuck in this loop until I restart the phone.
I've followed the instructions exactly MULTIPLE times just to verify I got it right. I'm clean flashing as well, so no it's not cuz of that. I've even redownload the files three times just to ensure it wasn't the result of possible file issues. Anyone else having this issue? I'd greatly appreciate a second pair of eyes on this!
champ784 said:
Moto Z2 Force Edition - T-Mobile
Unlocked Bootloader
TWRP 3.2.0-0
I keep trying to flash this ROM, and have succeed in the flashing process. However, whenever I boot up, I get "TMOConfig has stopped" and then I can close it. I notice, that cellular data is not active. I continue through setup as normal until the Moto Permissions screen. When I try to go through this screen, whether I accept or decline, "com.motorola.tmo.setupext has stopped" comes up. The only option is to open app again and it takes me to the prior screen for Google setup and gets stuck in this loop until I restart the phone.
I've followed the instructions exactly MULTIPLE times just to verify I got it right. I'm clean flashing as well, so no it's not cuz of that. I've even redownload the files three times just to ensure it wasn't the result of possible file issues. Anyone else having this issue? I'd greatly appreciate a second pair of eyes on this!
Click to expand...
Click to collapse
you still have OEM stuff - you need to wipe oem partition and then flash.
byt3b0mb said:
you still have OEM stuff - you need to wipe oem partition and then flash.
Click to expand...
Click to collapse
Does formatting help wipe that? I've done wipes and formatting just to be safe
Gotta flash the oem.img then reflash
joemossjr said:
Gotta flash the oem.img then reflash
Click to expand...
Click to collapse
Just tried redoing everything again. I get cellular now, and it boots. But now the phone will randomly freeze after a few minutes and restart
Sorry for being such a noob... This is my first dual partition device I've worked with... I've gotten spoiled with OnePlus and Nexus devices lol
champ784 said:
Just tried redoing everything again. I get cellular now, and it boots. But now the phone will randomly freeze after a few minutes and restart
Sorry for being such a noob... This is my first dual partition device I've worked with... I've gotten spoiled with OnePlus and Nexus devices lol
Click to expand...
Click to collapse
Sorry I meant which slot/ota are you on
joemossjr said:
Sorry I meant which slot/ota are you on
Click to expand...
Click to collapse
To check this, go to TWRP and in the reboot menu it will tell you which slot you're on like the below screenshot of me on slot B
For sprint users, there is a poll to end on dec 8th asking if WiFi calling is a must for your rom. please answer it. I have tried a few methods but all fail. any further would require editing the framework.jar file in oem and some trickery that needs some serious coding done to work correctly. So I will take on the task if enough vote for it. (I do this in my free time for free and if not enough interest is given, I'd rather not waste the time as another update might break it, and it also takes me away from my EAS project which has a lot of interest.)
joemossjr said:
Sorry I meant which slot/ota are you on
Click to expand...
Click to collapse
Mine shows Slot A. Am I correct in assuming that should be Slot B?
champ784 said:
Mine shows Slot A. Am I correct in assuming that should be Slot B?
Click to expand...
Click to collapse
Slot A has less bugs than Slot B. I would stay slot A if you can. I would suggest wiping oem in TWRP, mount oem, wipe oem, then reboot to bootloader and flash the oem img in OP.
Okay so this is my first post so don't crucify me but I have a Moto e5 Plus (xt1924-8) on Boost Mobile. I currently have the stock rom on my phone as that has working data. Since this device launched with treble support, I figured I'd try flashing some GSIs. The one I had settled on was Resurrection Remix as it had the most working features. In the thread for the GSI https://forum.xda-developers.com/moto-e5/development/gsi-resurrection-remix-o-6-1-0-t3843928 it says that you should be able to flash on top of the stock rom. However, when I do that, everything works fine except for mobile data. I tried reflashing and editing APN settings all to no avail. It's not the modem firmware as I reflashed that as well. Can anyone tell me what I could try to get mobile data working in RR on the xt1924-8?
Also, I tried to get lineageOS as that might've been needed to get RIL working but I was unable to find one that works with the -8 variant. If someone could link to an image that would be nice.
TinTrapezoid said:
Okay so this is my first post so don't crucify me but I have a Moto e5 Plus (xt1924-8) on Boost Mobile. I currently have the stock rom on my phone as that has working data. Since this device launched with treble support, I figured I'd try flashing some GSIs. The one I had settled on was Resurrection Remix as it had the most working features. In the thread for the GSI https://forum.xda-developers.com/moto-e5/development/gsi-resurrection-remix-o-6-1-0-t3843928 it says that you should be able to flash on top of the stock rom. However, when I do that, everything works fine except for mobile data. I tried reflashing and editing APN settings all to no avail. It's not the modem firmware as I reflashed that as well. Can anyone tell me what I could try to get mobile data working in RR on the xt1924-8?
Click to expand...
Click to collapse
Hey, do you have the method available for how you got root for the boost mobile variant?
shezzy83 said:
Hey, do you have the method available for how you got root for the boost mobile variant?
Click to expand...
Click to collapse
I used the guide for the e5 play. Flash stock, erase data, cache and DDR. Boot, wait for encryption
Then boot twrp don't flash. Flash universal dm verity and encryption remover and then flash magisk 17.1.
That's how I recall it. Probably wrong. Check the thread for the e5 play. Use the difficult route. Sorry :/
shezzy83 said:
Hey, do you have the method available for how you got root for the boost mobile variant?
Click to expand...
Click to collapse
The method that worked for me and my 2 Boost E5 Pluses was to:
Unlock boot loader through Motorola website
Reboot phone into bootloader
Fastboot boot into twrp (the boot image "twrp_james" worked for me)
While in twrp, do a backup onto microsd card.
Boot into android and install Magisk manager
Use Magisk to patch your boot.emmc file from your twrp backup
Find the patched-boot file that it output and copy to your pc
Reboot phone into bootloader
Flash the patched-boot file using fastboot flash boot (file name)
Reboot and enjoy ROOT!!!
Just fyi, I didn't do any dm-noverity kernel flashing or flashing twrp to recovery.
TinTrapezoid said:
Also, I tried to get lineageOS as that might've been needed to get RIL working but I was unable to find one that works with the -8 variant. If someone could link to an image that would be nice.
Click to expand...
Click to collapse
did you find a solution? im in the same boat
JimmyJurner said:
did you find a solution? im in the same boat
Click to expand...
Click to collapse
Naw sorry dude. All the GSI's for lineage bootlooped or didn't have data. Just gave up and reflashed stock with magisk.
Try manually inputting stock apn in gsi
TinTrapezoid said:
Naw sorry dude. All the GSI's for lineage bootlooped or didn't have data. Just gave up and reflashed stock with magisk.
Click to expand...
Click to collapse
I'm assuming there's still no fix right I'm on lineage 15. and have no service for sprint same model