[MODEM][PORT]Stock Android 6.0.1 Baseband Radio for xt1526 Moto E LTE - E 2015 Original Android Development

XT1526 MOTO E LTE
STOCK 6.0.1 BASEBAND RADIO
VERSION: M8916_2020632.44.03.21.54.01R
PORTED FROM XT1548 MOTO G (3rd Gen)​
SPECIFICATIONS:
This is a Stock Android 6.0.1 Baseband Radio (/modem & /fsg) for the Moto E LTE, xt1526 model only. It has been ported from the xt1548 Moto G (3rd Gen), modded for full compatibility with the xt1526, and optimized for roaming on the Verizon network. This Baseband was pulled from Stock Android 6.0.1, Build No. MCIS24.107-82-18, System Version 24.221.18.en.US.
This Baseband installer is for the Sprint, Boost Mobile & Virgin Mobile variants of the xt1526. It HAS NOT been tested on the US Cellular xt1526 variant. If using the Boost Mobile xt1526 variant, XDA Member @anthonykb has reported that the device must first be updated to a 6.0 Stock bootloader.img and partition index (gpt.bin) before this Baseband will function. Anybody with the Boost Mobile xt1526 can head over to @Buzbee2's thread on ported stock 6.0 for the xt1526. You will simply need to flash the 6.0_Stock_Partition_Updater zip available in Buzbee's thread. https://forum.xda-developers.com/mo...stock-xt1521-gsm-xt1526-cdma-t3342789/page19. For members who use @Buzbee2's thread and/or files, be sure and hit the thanks button on his thread.
This Baseband should work on all CM/LOS, AOSP, Stock, & Stock Based ROMS, on any Android Version from 5.0.2 Lollipop to 7.1.2 Nougat. You should notice a marked improvement in connectivity, signal strength, download/upload speeds, and domestic roaming. This Baseband has been optimized to force handover of data connectivity to the Verizon network in situations where (1) your signal on the Sprint towers has fallen below a 110dB signal; and (2) when your xt1526 cellular radio is unable to locate a viable Sprint signal. NOTE: The optimized roaming mod has only been tested on stock and stock based ROMs. This feature may or may not work on custom ROMs such as CyanogenMod or LineageOS.
NOTE: This Baseband performs best on Stock Android 5.0.2 or 5.1 factory firmware.
DISCLAIMER:
Flashing the partitions of your device or altering its stock factory configuration poses an inherent risk of bricking or rendering your device inoperable. By proceeding any further, you absolve me of any liability in the event your device is damaged in any way from installing this radio firmware.
Follow the instructions closely and things should go smoothly.
REQUIREMENTS:
For purposes of this guide, you must have an unlocked bootloader and TWRP custom recovery installed on your xt1526. If you do not have both of these requirements, search the XDA threads for tutorials on how to do so. While it is certainly possible -- and feasible -- to flash this installer using an on-device flashing application, like Flashfire, this thread is geared towards installation via TWRP custom recovery. (Preferably @squid2's 3.1.1-r1 rebased build) Be sure and hit the thanks button on @squid2's TWRP thread if you use his recoveries.
INSTRUCTIONS:
1. Download the Baseband Updater zip from the below link and save it either to internal storage or your external micro SD card;
2. Boot your xt1526 into TWRP recovery;
3. Select INSTALL, navigate to the storage location of the zip you downloaded in Step 1, select the file, and swipe to commence with installation.
4. When installation is complete, reboot system. Done. Your xt1526 Baseband Radio is now updated to M8916_2020632.44.03.21.54.01R.
DOWNLOAD LINK: https://drive.google.com/file/d/0B1Sfod4HWfk2cWFVeUdsU3JYQTg/view?usp=sharing

I just tested this on Boost xt1526 with ViperOS and it didn't work. I'll try flashing and doing a clean rom install and see if it makes a difference.

amarc78 said:
I just tested this on Boost xt1526 with ViperOS and it didn't work. I'll try flashing and doing a clean rom install and see if it makes a difference.
Click to expand...
Click to collapse
Yes do a clean install always. I need to incorporate that into the instructions. Also, if you do a "dirty" install, you can always clear nv data by by entering fastboot and using: fastboot erase modemst1 and fastboot erase modemst2. This baseband seems to perform best on stock based ROMs.

MotoJunkie01 said:
Yes do a clean install always. I need to incorporate that into the instructions. Also, if you do a "dirty" install, you can always clear nv data by by entering fastboot and using: fastboot erase modemst1 and fastboot erase modemst2. This baseband seems to perform best on stock based ROMs.
Click to expand...
Click to collapse
I did do erase modemst1/2, but it didn't make a difference. I was going to mention you can add erase modemst1 erase modemst2 to the update script without the fastboot part and it will work. I'll try a clean flash and report back.
Sent from my Motorola XT1526 using XDA Labs

amarc78 said:
I did do erase modemst1/2, but it didn't make a difference. I was going to mention you can add erase modemst1 erase modemst2 to the update script without the fastboot part and it will work. I'll try a clean flash and report back.
Click to expand...
Click to collapse
I did have the format command in updater-script but removed it, because many people do not want nv data erased upon installation of the baseband. I may have to revise the thread to clarify Virgin Mobile only. It doesn't seem to be working on Boost. Thank you for your testing. I really appreciate it.
By the way did you try:
fastboot oem confg fsg-id boost
fastboot oem config carrier boost

I just revised the thread to specify Virgin & Sprint only for now, until further testing can be done on Boost. In theory it should work on Boost, since the Virgin & Boost xt1526 variants both used the same stock firmware builds.

--- Flash files that are contained in Surnia_Moto_E_2015_6.0_Stock_Partition_Updater.zip from 2nd post at linked thread by Buzbee2 >
https://forum.xda-developers.com/moto-e-2015/cdma-development/stock-xt1521-gsm-xt1526-cdma-t3342789
--- Flash using following fastboot commands as follows with the images from the zip extracted to the C:\ drive ---
fastboot flash partition C:\gpt.bin
fastboot flash bootloader C:\bootloader.img
--- Then the radio firmware will operate fine on the Moto E 2015 Boost Mobile XT1526 phone after flashing the radio in TWRP---

anthonykb said:
--- Flash files that are contained in Surnia_Moto_E_2015_6.0_Stock_Partition_Updater.zip from 2nd post at linked thread by Buzbee2 >
https://forum.xda-developers.com/moto-e-2015/cdma-development/stock-xt1521-gsm-xt1526-cdma-t3342789
--- Flash using following fastboot commands as follows with the images from the zip extracted to the C:\ drive ---
fastboot flash partition C:\gpt.bin
fastboot flash bootloader C:\bootloader.img
--- Then the radio firmware will operate fine on the Moto E 2015 Boost Mobile XT1526 phone after flashing the radio in TWRP---
Click to expand...
Click to collapse
Interesting, so the Boost variant must first have the bootloader and partition index updated to stock6.0? Good find. Glad you got it working on your Boost Mobile variant. @anthonykb, what I'll probably do, or you can do it either one, is go ahead and incorporate gpt.bin and bootloader.img from stock 6.0 into my updater-script for Boost users. For Virgin & Sprint users, I'll leave everything like it is.

anthonykb said:
--- Flash files that are contained in Surnia_Moto_E_2015_6.0_Stock_Partition_Updater.zip from 2nd post at linked thread by Buzbee2 >
https://forum.xda-developers.com/moto-e-2015/cdma-development/stock-xt1521-gsm-xt1526-cdma-t3342789
--- Flash using following fastboot commands as follows with the images from the zip extracted to the C:\ drive ---
fastboot flash partition C:\gpt.bin
fastboot flash bootloader C:\bootloader.img
--- Then the radio firmware will operate fine on the Moto E 2015 Boost Mobile XT1526 phone after flashing the radio in TWRP---
Click to expand...
Click to collapse
I was already updated to the 6.0 bootloader and even with a clean install it still didn't work for me. Won't read sim card at all.
Sent from my Motorola XT1526 using XDA Labs

amarc78 said:
I was already updated to the 6.0 bootloader and even with a clean install it still didn't work for me. Won't read sim card at all.
Click to expand...
Click to collapse
Hmmmm. Did you fastboot configure your carrier and fsg partitions?
fastboot oem config fsg-id boost
fastboot oem config carrier boost

MotoJunkie01 said:
Hmmmm. Did you fastboot configure your carrier and fsg partitions?
fastboot oem config fsg-id boost
fastboot oem config carrier boost
Click to expand...
Click to collapse
I'll try again, but yes.
Sent from my Motorola Moto E (4) using XDA Labs

Try this, and I think we can get things working. Install a pure stock 5.1 firmware build. I'll get you an Aroma installer that will configure your configs for Boost Mobile. I want to try pure stock because we need to do a PRL & Data Profile update. Use any 5.1 build except s.12. And, of course, disregard flashing gpt.bin or bootloader.img from the firmware package of 5.1.Let me know if you install 5.1 stock. I'll get some of the files together we will need. Also, should you need any firmware builds for your xt1526 let me known. I have all firmware packages that were ever made for the device. I've got fastboot flashable packages and TWRP flashable zip versions.

MotoJunkie01 said:
Try this, and I think we can get things working. Install a pure stock 5.1 firmware build. I'll get you an Aroma installer that will configure your configs for Boost Mobile. I want to try pure stock because we need to do a PRL & Data Profile update. Use any 5.1 build except s.12. And, of course, disregard flashing gpt.bin or bootloader.img from the firmware package of 5.1.Let me know if you install 5.1 stock. I'll get some of the files together we will need. Also, should you need any firmware builds for your xt1526 let me known. I have all firmware packages that were ever made for the device. I've got fastboot flashable packages and TWRP flashable zip versions.
Click to expand...
Click to collapse
Here is the Aroma installer. Simply flash this using TWRP recovery. Select "Boost" when the installer prompts you to choose a carrier.
https://drive.google.com/file/d/0B1Sfod4HWfk2ZFQybXFiZHZDYkE/view?usp=drivesdk
You could try the Aroma installer now, before going through the 5.1 firmware package flashing. There's a pretty good chance that the Aroma installer alone will configure the baseband to work with Boost on your device.

On the Boost Mobile xt1526 variant, here is what I just done and it worked perfect on mine. I "dirty flashed" the baseband installer, basically installing the radio firmware and leaving nv data intact, then rebooted system. On the stock dialer, I opened the SCRTN Menu (Network & Carrier Config Reset) by dialing ##72786# and choosing "YES" when prompted. Upon reboot, I again booted into TWRP and installed the MVNO_Slayer Aroma zip and selected "Boost" from the carrier menu. Then I rebooted system. RIL is fully functional, as is 4G/LTE data connectivity. Updating my partition index and bootloader to stock 6.0 was not necessary. (My bootloader.img and gpt.bin are the original stock 5.0.2 versions that shipped on the Moto E LTE xt1526 during initial release of the device).

@anthonykb, I'm going to compile a separate zip installer for the Boost variant. It can be done one of two ways, both of which we have confirmed to work: (1) I can either include stock 6.0 bootloader.img & gpt.bin in the zip/updater-script, or (2) I can reincorporate a format command for modemst1 & modemst2, and include the apns-config.xml/eri.xml for Boost from the mvno_slayer Aroma installer. What are your thoughts?

Just wondering, are the IMG files essentially the same as fsg.mbn and NON-HLOS.bin? Regards

tzheng0311 said:
Just wondering, are the IMG files essentially the same as fsg.mbn and NON-HLOS.bin? Regards
Click to expand...
Click to collapse
img, mbn, bin, etc, are all image type formats which can be flashed from fastboot. For the purposes for which I am using them, yes they are exactly the same. To clarify, NON-HLOS.bin and modem.img are the same, and fsg.mbn is the same as fsg.img.

@tzheng0311 have you given this a try on your DDR devices yet? Works great on forced roaming on DDR, on stock ROMs anyway. I've not had a chance to test the data handover on custom ROM roaming yet.

I'm going to try it later on today, thanks for the heads up. I'll let you know, I have like 3 on stock ROM and the rest on CM13
Edit: Woop, turns out i'm on S.12 and this baseband really doesn't like it lol, gonna update first

MotoJunkie01 said:
On the Boost Mobile xt1526 variant, here is what I just done and it worked perfect on mine. I "dirty flashed" the baseband installer, basically installing the radio firmware and leaving nv data intact, then rebooted system. On the stock dialer, I opened the SCRTN Menu (Network & Carrier Config Reset) by dialing ##72786# and choosing "YES" when prompted. Upon reboot, I again booted into TWRP and installed the MVNO_Slayer Aroma zip and selected "Boost" from the carrier menu. Then I rebooted system. RIL is fully functional, as is 4G/LTE data connectivity. Updating my partition index and bootloader to stock 6.0 was not necessary. (My bootloader.img and gpt.bin are the original stock 5.0.2 versions that shipped on the Moto E LTE xt1526 during initial release of the device).
Click to expand...
Click to collapse
Did you get this to work running stock or a custom rom? I tried again running HalogenOS and still didn't work. I'll restore stock and try it, then if it works I'll try flashing some custom rom. When I can have my phone down for a bit.
Sent from my LGLS755 using XDA Labs

Related

[ROM][ATT][4.4]Kitkat 140.44.3.ghost_att + root for locked bootloader [UPDATED]

Intro: Below are the instructions for 3 steps to get Kitkat 4.4 (140.44.3.ghost_att) running on the AT&T moto x with locked bootloaders:
Install full 139.44.44.ghost_att (leaked) rom
Patch the rom to 140.44.3.ghost_att (ota to leak)
Patch the modem to the 140.44.3.ghost_att version
The updates came in stages, otherwise it would not have been my intention for this to be so long and messy. I soon hope to create a single rom and simplify the instructions. Testers can help with the WIP items below...
WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE.
This rom is simply a flashable zip made from the ATT 4.4 leak which will install version 139.44.44. It is intended for the ATT moto x with locked bootloaders, however it should work with an unlocked bootloader if you fastboot flash the included boot.img. The flashable zip does not modify the bootloader or anything besides /system, but the full instructions will wipe out everything.
Prerequisite:
Att moto x with either the .51 (original) or .54 (1st OTA) stock rom
BACKUP ANYTHING YOU DON'T WANT TO LOSE. THESE INSTRUCTIONS WILL WIPE YOUR USERDATA AND SDCARD.
Instructions for ATT moto x with locked bootloader:
root with PwnMyMoto or RockMyMoto (for .51 or .54 respectively, thanks jcase)
install safestrap (thanks Hashcode and Team Win)
download rom to sdcard (motox-att-kitkat-leak-44.zip, link below)
download supersu flashable to sdcard (link below, thanks Chainfire)
enter safestrap recovery (TWRP) and activate the stock-slot
flash rom (motox-att-kitkat-leak-44.zip) to the stock-slot using TWRP recovery
immediately flash supersu using TWRP recovery
within TWRP reboot to bootloader
flash boot.img (included in ROM) to boot: fastboot flash boot boot.img
flash same boot.img to recovery: fastboot flash recovery boot.img
erase cache: fastboot erase cache
erase userdata: fastboot erase userdata (This wipes everything) This is not necessary. Thanks HeroSon.
powerup normally and enjoy
Update 11/17/2013: I made a patch to safely apply the ota that was received by people running the att 4.4 leak. This will bring the system build up to 140.44.3.ghost_att. The patch script DOES NOT modify anything except /system, and should be safe. The updated kernel (boot.img) is included in the zip. In case something goes wrong, backup your data to be on the safe side. Here are the Instructions:
Complete the installation of the att 4.4 leak (above instructions)
Reinstall safestrap This is not necessary. Thanks HeroSon.
Download the patch to sdcard (motox-140.44.3.ghost_att-ota-safepatch.zip, link below)
Reboot into safestrap recovery (TWRP)
Install the patch (motox-140.44.3.ghost_att-ota-safepatch.zip)
within TWRP reboot to bootloader
flash boot.img (included in the patch) to boot: fastboot flash boot boot.img
flash same boot.img to recovery: fastboot flash recovery boot.img
powerup normally
Update 11/18/2013: I attached a link to the modem patch that will update the 139.44.44 modem to a 140.44.3 modem. I really wanted to create a fastboot flashable NON-HLOS.bin image, but I haven't tested the procedure. Here are the instructions for the modem patch that I have tested:
Download the modem patch to the sdcard (motox-140.44.3.ghost_att-modem-patch.zip, link below)
Fastboot flash NON-HLOS.bin (included within the zip): fastboot flash modem NON-HLOS.bin
erase modemst1: fastboot erase modemst1 (I've done these erases a few times. They are prudent when you flash a modem.)
erase modemst2: fastboot erase modemst2
Reboot into safestrap recovery TWRP
Install the modem patch (motox-140.44.3.ghost_att-modem-patch.zip)
Powerup normally
Notes:
I am running the modem from the .54 ota, and it works with kitkat. I am not sure about the original .51 modem. The 140.44.3 modem is necessary after running patch to 144.44.3. This fixes the settings->security force close.
The safestrap "recovery or continue" screen still appears when you boot. If you erased userdata, reinstall safestrap to get all of the program back.
You should always be able to flash back to stock, as this procedure does not modify your bootloader.
There is a new version of safestrap. These instructions work with either v3.63 and v3.65. (Thanks HeroSon.)
I get a FC in settings->security on the 140.44.3 (patched) version. So far this is the only problem I have noticed. This force close is fixed by the modem patch.
WIP: I would like testers to help with the following:
What happens if you skip step 12 and don't erase useradata (this will keep [more of] safestrap intact)?
How do you remove safestrap manually?
Safestrap has been updated. Does the original 139.44.44 rom now run in a rom slot with 4.2.2 running in the stock-slot? What about the patches? I tried it - doesn't work.
Once 4.4 is installed in the stock-slot, can you backup the stock slot and restore to a rom-slot? (I'm guessing it works this way.) I guessed wrong. This doesn't work. Apparently safestrap needs a bit of tweaking to work with KK.
Is it possible for Safestrap TWRP to flash boot.img to the stock slot? (My experience is that it did not flash boot.img when using a rom-slot)
To clean up this mess, I am considering making a single rom that includes the base 4.4 version with the safepatch included. PM if you want to help by testing this all in one rom once I have it finished. There is a new rom of the official att 4.4.
I have an 100MB ext4 image of /modem. I would like guidance making a fastboot flashable non-HLOS.bin image. (Otherwise I wont be able to combine the leak and the patch.) I see instructions that might work if someone wants to try it and report their findings: http://forum.xda-developers.com/showthread.php?t=1588461 The official att 4.4 SBF includes NON-HLOS.bin
Part of the stock modem procedure is to flash "fsg.mbn", but I have not done that because I have been able to confirm that you can downgrade after flashing it. Can anyone confirm that this is safe on the moto x? (http://forum.xda-developers.com/showthread.php?t=2529569) This works.
139.44.44 rom download : http://www.androidfilehost.com/?fid=23212708291677349
rom patch to 140.44.3 download: http://www.androidfilehost.com/?fid=23212708291678076
modem patch to 140.44.3 download: http://www.androidfilehost.com/?fid=23212708291678561
supersu: http://forum.xda-developers.com/showthread.php?t=1538053 (download "CWM / TWRP / MobileODIN installable ZIP")
Original source files: http://rootzwiki.com/topic/107721-att-moto-x-44-leak/ (thanks designgears)
ooo yeah !! Nice job !!
Sa sens le Rooting icite !!
Wish mine was from AT&T, still have one year of warranty....cant see the time when kitkat comes global.
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
Sent from my XT1058 using XDA Premium 4 mobile app
How do I do steps 9-12?
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?
Sent from my XT1053
rubiksmoose said:
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It might work without the wipe. Honestly, I tried this so many times that I quit once I had something that worked... I attributed most of my failures to a incompatibility between safestrap and the 4.4 boot process, but each of those attempts was done to a rom slot and not the stock slot.
Hopefully someone else can 'give it a whirl' and report their findings.
penpen72 said:
How do I do steps 9-12?
Click to expand...
Click to collapse
These steps are done using "FASTBOOT" from a PC while the phone is booted to the bootloader in fastboot mode.
phositadc said:
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?
Click to expand...
Click to collapse
The rom was made from the original leak. I have been thinking about the OTA, but I am unclear how to approach this.
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
penpen72 said:
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
Click to expand...
Click to collapse
I assume you are on windows. First you need to download the FASTBOOT.exe program for our Motorola phones, and make sure the fastboot drivers install on your PC. (Maybe someone can help with this link.) Then you can issue the "fastboot ..." commands 9-12 I listed above from your PC with your phone plugged into the PC.
You certainly need to flash /boot, and you should also flash boot to recovery to allow RW access to /system. It might be possible to skip the "erase userdata" step, but that is unclear to me at this moment.
How is the leaked ROM working for you? Worth it? Any bugs or anything?
rubiksmoose said:
How is the leaked ROM working for you? Worth it? Any bugs or anything?
Click to expand...
Click to collapse
Everything is working fine. Take a look here for other people's observations:http://forum.xda-developers.com/showthread.php?t=2517577
There are only two odd things I have noticed. 1) the recent apps screen acts a bit strange when you swipe away apps 2) the transparent status bar becomes less transparent when you go for a drive and the "driving" notification is displayed. It is almost not worth mentioning, and a reboot fixes this issue.
It is hard to answer the "worth it" question. Ultimately, it is a still a smartphone with the same core capabilities, but I enjoy the challenge and the opportunity to learn something.
[edit]I am starting to think that there is additional battery drain vs the .54 ota version. "Wakelock detector" doesn't work, and settings->battery shows "Android System" at the top. This is a 'deal breaker' for me. I'll try and figure out how to apply the 4.4 ota without modifying the bootloader.[/edit]
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
n1ckr0th said:
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
Click to expand...
Click to collapse
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
Ctrl-Freak said:
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
Click to expand...
Click to collapse
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
n1ckr0th said:
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
Click to expand...
Click to collapse
Yes. After you have 4.4 working, you must still boot to recovery to enable RW mode on /system. Step 10 ensures you have the 4.4 boot.img in the recovery partition.
(The stock bootloader is still enforcing RO mode for a normal boot.)
I install this and skip step 12 and don't erase useradata. Everything working and all the data still there.
So can I clarify a few things for myself?
You made this by taking the leak files and packaging them into the zip, and it just works with safestrap now? Can you explain what you did to make the leak imgs Safestrap-bootable?
j2cool2012 said:
You made this by taking the leak files and packaging them into the zip,
Click to expand...
Click to collapse
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.
Can you explain what you did to make the leak imgs Safestrap-bootable?
Click to expand...
Click to collapse
Nothing.
and it just works with safestrap now?
Click to expand...
Click to collapse
I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...
Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.
The only other thing I did was describe a set of instructions that worked for me.
Ctrl-Freak said:
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.
Nothing.
I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...
Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.
The only other thing I did was describe a set of instructions that worked for me.
Click to expand...
Click to collapse
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
j2cool2012 said:
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
Click to expand...
Click to collapse
the Att bloatware and carrier name in notification bar scared me away

[25-11-2013][UNLOCKED BL] Moto X Open Recovery 2.09 by Skrilax_CZ

First of all: I am not developer of this recovery. ALL CREDITS MUST GO TO Skrilax_CZ. He just allow me to post it here.
Open Recovery (OR) is for MOTO X with UNLOCKED Bootloader. It is compatible with KitKat.
Detailed OR description (made by Skrilax_CZ) is here.
From my point of view, one of the big difference from TWRP and CWM is: OR can make backup/restore of modem software.
In particular OR make backup of the following partitions: boot, cache, data, fsg, logo, modem, modemst1, modemst2, system.
INSTALLATION
1) Download the image
2) Flash using fastboot (fastboot flash recovery open_recovery.img)
3) Reboot to recovery
Open Recovery for Moto X DOWNLOAD
Man I wish I could unlock my bootloader this looks awesome!
Sent from my XT1058 using XDA Premium 4 mobile app
So.....can it flash back previous radio (modem=radio right?)firmware alone? Can it do it independent from everything else? Meaning, I save my current everything 4.2.2, take the 4.4 kk update, notice the call quality isn't as good, flash back JUST modem/radio firmware, drink beer?
Yes, it can. You can select partitions to backup as well as you can select partitions to restore from backup. So if you would like to restore only modem software just select corresponding partitions and restore them.

US Dev/AT&T 442/443/444/501/502 Debloated VVM/ISIS Release 06-10-2015

This ROM has been tested and retested... IF you cannot follow instructions provided DO NOT FLASH,IF your wanting tweaks etc DO NOT FLASH OR ASK FOR THEM THERE ARE OTHER ROMS WITH YOUR WANTS AND DESIRES,IF you are uneasy about flashing firmware DO NOT FLASH THIS ROM,DO NOT USE ANY PART OF THIS ROM WITHOUT PERMISSION, IF your wanting to use another kernel (99% stock is included) etc,DONT ASK HERE IF ISSUES ARISE (ASK THE KERNEL DEV) Folks who use this want a clean stable ROM..IF you are a flashaholic,id suggest copying pics,music etc to computer format your data partition then flashing.
Whats included:
Extra Themes
Eye Experience
Extra Camera Modes
Xposed ONLY included in 4.4.4 and below for now
Integrated VVM (Dialer and Messages)
Isis (Working with Xposed Modules) ONLY WORKING 4.4.4 and below for now
Speed Tweaks
Battery Tweaks
SD Card Tweaks
Screen Touch Tweaks(more sensative)
Dalvik Tweaks
Hardware Tweaks (Qualcomm)
Network Tweaks (Qualcomm)
Stock recovery
Twrp recovery
Weather images updated Thanks Basil3 Not included in latest 5.0.2
Read write module Thanks Flar ONLY WORKING on 4.4.4 and below for now
Rooted
Stock file manager
Quick office Removed in 5.0.1
Extreme Power Saving
S-OFF IS MANDITORY!!!!
BACKUP Pictures,Music,Etc. just in case device is wiped when flashing firmware
***Current 5.0.1 Lollipop Flashing Instructions***
If you have not flashed the 5.0.1 firmware it is included:
CID's that will flash correctly
cidnum: BS_US001
cidnum: BS_US002
cidnum: CWS__001
****S-OFF is necessary to proceed with flashing firmware package****
Extract firmware.zip from zip, copy to adb/fastboot location,reboot phone into bootloader connecting it via fastboot option,run commands listed below
Also included in this firmware package is the modified hboot with red text removed
IF you do flash this firmware package the commands to do so are as such:
* 1.fastboot oem rebootRUU
* 2.fastboot flash zip firmware.zip(if needed re-run this command)
* 3.fastboot reboot-bootloader
After flashing this firmware package stock recovery will be installed,extract twrp_2_8_3_0_m8.img from zip, copy to adb/fastboot location reflash twrp recovery that is included by running command:
fastboot flash recovery twrp_2_8_3_0_m8.img or latest twrp image
Now after flashing twrp reboot device into recovery,do these steps as it is important!!
factory wipe device,click advanced wipe and select data,system,cache and dalvik wipe these partitions.(TWRP will reload,do not flash until after rebooting recovery) Once this is finished reboot recovery and proceed to flash this ROM.
ATT_4_28_502_1_M8_Lollipop_No_CIQ_Firmware and ROM(is full firmware with modified boot.img and hboot.img,will need to reflash twrp)
https://goo.gl/0gGHLr(current)
ATT_4_16_1540_8_M8_Lollipop_Firmware and ROM
http://goo.gl/iumj9r(depreciated)
ATT_ISIS_3_42_502_1_M8 ***Use Instructions below for 4.4.4*** (Firmware not included)
http://goo.gl/YM12mn (depreciated)
3_42_502_1 Firmware Bundle (is full firmware with modified boot.img and hboot.img,will need to reflash twrp)
http://goo.gl/U7gocS (depreciated)
DEPRECIATED
Updating Firmware:
1. Copy ROM to storage
2. Copy Firmwarezip to adb/fastboot location
3. Drag twrp openrecovery-twrp-2.7.1.0-m8.img to adb/fastboot location
4. Reboot phone to bootloader/fastbootusb(adb reboot bootloader)
5. Once connected via fastbootusb
6. Open command prompt,
7. Run these commands:
* 1.fastboot oem rebootRUU
* 2.fastboot flash zip 2.22.1540.3_firmware.zip or whatever the latest builds firmware zip is called.
* 3 repeat #2 command to finish firmware flashing.
Already modified to work on cid's,so no need to change cid
cidnum: BS_US001
cidnum: BS_US002
cidnum: CWS__001
* 4.fastboot reboot-bootloader
8. Once rebooted, run these commands:
* 1.fastboot flash recovery openrecovery-twrp-2.7.1.0-m8.img or whatever latest twrp image is
* 2.fastboot reboot-bootloader
* 3.Boot into recovery,factory reset,flash rom (IF ROM has been wiped off data partition,copy rom zip to fastboot/adb location and run adb sideload from recovery..Or adb push nameofrom.zip /sdcard/. Then flash
Modified hboot is already included to remove developer text
After installing ROM:
REMINDER *You MUST flash the latest 2.22.1540.3/.4 or whatever the latest builds firmware zip is called firmware(Included)* ,Once booted DO THESE NEXT STEPS FIRST BEFORE ANYTHING ELSE!!!!,ROM is rooted,has read/write protection disabled,has at&t apn's ...Set Superuser permissions to grant always(no prompts)...Update Xposed Framework and installer...Reboot when prompted....Download Rootcloaker Module, install and activate it....reboot run isis....THEN finish setting up ROM...I dont have a secure sim,butit asks for it,so that means its a go...this also has visual voicemail integrated into system(dialer/messaging app)...I suggest disabling animations in developer options to get the full effect of rom speed...
Enjoy
Download:
M8 - 2.23.502.3(depreciated)
http://goo.gl/3DiIQz FULL WIPE REQUIRED
Mirror: http://goo.gl/9wNs1J (Thanks krazyace35)
ATT 1.16 Radio fix (Thanks runsoverfrogs)
** S-OFF IS MANDATORY **
Radio Download: ONLY For 2.23.502.3
http://goo.gl/vB9dA7(depreciated)
Copy radio-1.16.zip to adb/fastboot loacation
Open cmd
Run commands as shown below
fastboot oem rebootRUU
fastboot flash zip radio-1.16.zip
fastboot reboot-bootloader
Make sure radio has flashed correctly reboot...
Modded Hboot(Thanks santod040):
M8 - 2.23.502.3
No Red Text: http://goo.gl/ins3or(depreciated)
Download:
M8 - 2.22.1540.3
http://goo.gl/uoRz8X(depreciated)
Download:
M8 - 2.22.1540.4
http://goo.gl/yE6s5V (depreciated)
Download:
M8 - 3.28.1540.5 (Read flashing instructions included in download)11-11-2014 Update :good:
http://goo.gl/S5hpMC(depreciated)
Blinkfeed update 11-11-2014
http://goo.gl/iYYAEp(depreciated)
Blinkfeed update 12-10-2014
http://goo.gl/FHpxlV(depreciated)
For those who want to update to newest versions for developer build,you must have stock operating system and recovery and soff to run any of these files
Download:
2.22.1540.4 ota
http://goo.gl/7mec4o (Upgrade original stock device,not for custom roms) (depreciated)
Download:
3.28.1540.5 ota
http://goo.gl/MHF4ie(Upgrade original stock device,not for custom roms) (depreciated)
Download:
3.28.1540.5 Firmware only unmodified (Latest 4.4.4 Update,S-OFF REQUIRED)
http://goo.gl/tyhRRZ(depreciated)
Download:
2.22.1540.4 firmware only unmodified(Latest 4.4.3Update,S-OFF REQUIRED)
http://goo.gl/FJ7Hhv(depreciated)
Mirrors for ROM's(Thanks tarund)
http://goo.gl/7AuuJf
Changelog:
08-09-2014: App updates....Speed increase,some other minor fixes
08-13-2014 App updates...Minor tweakage
08-27-2014 New base 2.22.1540.4
08-29-2014 New base AT&T Official 2.23.502.3 Debloated and carrieriq removed
09-08-2014 Fixed double/not sending txt issue (I think),Kernel enhancement
9-10-2014 Reverted back to TWRP 2.6.3.3 as used recovery,Reverted Some edits back to stock.
10-19-2014 New Base 4.4.4 3.28.1540.5
11-06-2014 Updated HTC apps, 3rd party apps & some other stuff I dont recall off top of my head.
11-10-2014 Updated LTE configs,Some Camera Enhancements
1-20-2015 Developer Lollipop Release
5-19-2015 Official AT&T Lollipop Release
Thanks for this possible fix as well if the dble txt is still happening
runsoverfrogs said:
I fixed my hanging double text by rolling my radio back from 1.19 to 1.14 Edit WNC 1.16 works as well) baseband
Click to expand...
Click to collapse
Donations:
Thank you...
bruce7373
swapgut
orvon.freeman
co.ag.2005
vegasdiceshooter
cortez.i
ozziedog
effezie
fuzz_33594
Alpione
mimart7
aka120
Vegasdiceshooter
Isis111
Thanks to
ccb101
californiarailroader
orvon freeman for getting me the files
HolyAngel for helping with update script
homeslice for helping with carrieriq
Big thanks to my testers
manup456
mobb315
zero209
pumpiron579
ccb101
tarund
Judge Joseph Dredd
redpoint
swapgut
Already have the firmware installed can i just flash rom
Nice work, flashed firmware, installed rom, isis working vvm great job wnc
Firmware also includes unsecured boot image modded hboot suggested to flash it,then flash rom afterwards.
vegasdiceshooter said:
Already have the firmware installed can i just flash rom
Click to expand...
Click to collapse
Enjoy....
Pumpiron579 said:
Nice work, flashed firmware, installed rom, isis working vvm great job wnc
Click to expand...
Click to collapse
This Rom is kick ass! Way better than any Euro Rom imo.
Glad my boy is back in the building great work bro.
Sent from my HTC One_M8 using Tapatalk
Flashed and its a great ROM much better for AT&T than European ROMs
Glad your enjoying it...
vegasdiceshooter said:
Flashed and its a great ROM much better for AT&T than European ROMs
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Firmware also includes unsecured boot image modded hboot suggested to flash it,then flash rom afterwards.
Click to expand...
Click to collapse
So is the z-data file that wipes the phones removed from the firmware?
Read o.p. BACKUP Pictures,Music,Etc. just in case device is wiped when flashing firmware
GermanGuy said:
So is the z-data file that wipes the phones removed from the firmware?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Read o.p. BACKUP Pictures,Music,Etc. just in case device is wiped when flashing firmware
Click to expand...
Click to collapse
I did read the OP. Just had the simple question of whether the z-data file has been removed. If that file is removed, the phone should not get wiped.
No its not, and will not be removed from download,this ensures no bugs from things left on storage...and also ensure the storage doesnt encrypt because of stuff left over from other roms...So if you want to remove it thats on you,not resposible for anything that goes wrong.
GermanGuy said:
I did read the OP. Just had the simple question of whether the z-data file has been removed. If that file is removed, the phone should not get wiped.
Click to expand...
Click to collapse
This is developer edition firmware and Rom though right? Or is the developer edition the same for the most part as att?
Sent from my HTC One_M8 using Tapatalk
Yes developer edition is same device only difference is ones locked and ones not.The base for the rom is developer edition correct...
Johnny424 said:
This is developer edition firmware and Rom though right? Or is the developer edition the same for the most part as att?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thanks for the 2.22.1540 firmware, and great instructions. While I've flashed firmware before and familiar with the process, its nice to not have the proper command syntax right here.
Also great forethought to have it packaged with the ROM, and a good explanation of the process.
Anyone having issues with keeping wifi on? Mine keeps turning off...
Nope has been flawless what have you added/modified? Did you follow the instructions included or did you do it the way you wanted to?(Just a question..Not being rude).
diehardbattery said:
Anyone having issues with keeping wifi on? Mine keeps turning off...
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Nope has been flawless what have you added/modified? Did you follow the instructions included or did you do it the way you wanted to?(Just a question..Not being rude).
Click to expand...
Click to collapse
Installed Sense Toolbox, changed the theme of the statusbar icons. At first I thought maybe it was the theme and the icon just wasn't showing, but when I went to wifi settings, it wasn't connected to anything. Made some other tweaks in there, mostly visual.
Installed Battery Stats Permission, SD Full access, and Xposed Call blocker. That's it.
And I did follow the directions to the letter.

How to get back to a Stock ROM

Hi,
sorry if i'm the 100th person to ask this question but how can i go back to the stock ROM with OTA?
I currently have a flavor of LinageOS with the Turbo Z kernel installed on my phone but it's just to buggy for me. I want to have root access on my phone for various reasons though.
I tried to just download different (6.0/7.0) stock ROM files but i can't install them with TWRP. I know that 7.1.x was released but i can not find the ROM for it.
What is the easiest way to just go back to a stock ROM? I know my way around the console but i don't want to brick my phone. I made backups of my files and also with TWRP so data loss is not an issue.
https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
First things first.
On which bootloader are you, MM or are you on Nougat. If your device has been flashed with the 7(N) bootloader, you cannot flash the 6.0 stock, you will have to stay of 7.
Use the fastboot flash / erase commands, as in this thread:
https://forum.xda-developers.com/showpost.php?p=73119650&postcount=1
If at any stage your phone get bricked, ie, black screen after reboot, no charging, etc. Use these instructions. They saved me in the last week from returning my device for a replacement(and paying $350.00):
https://forum.xda-developers.com/showpost.php?p=71874880&postcount=1
lollyjay said:
https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
Click to expand...
Click to collapse
Does this work for the EU version too? I'm not sure if the baseband thingy is compatible. I'll need a EU ROM otherwise but i can't find any for Android 7 :/
bert269 said:
On which bootloader are you, MM or are you on Nougat. If your device has been flashed with the 7(N) bootloader, you cannot flash the 6.0 stock, you will have to stay of 7.
Click to expand...
Click to collapse
I've already updated to Android 7 so i guess i've to use a stock Nougat ROM.
Read my last post on page 15 of this thread
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113/page15
Where can I find the stock recovery for XT1650-03 RETEU without downloading an entire ROM zip file?
I have stock 7.0.0 with TWRP and Magisk 13.3.
I want to install the stock recovery so that I can install the 7.1.1 OTA which is available on my device, after which I will flash TWRP and root again. Will this work?
Byte_76 said:
Where can I find the stock recovery for XT1650-03 RETEU without downloading an entire ROM zip file?
I have stock 7.0.0 with TWRP and Magisk 13.3.
I want to install the stock recovery so that I can install the 7.1.1 OTA which is available on my device, after which I will flash TWRP and root again. Will this work?
Click to expand...
Click to collapse
If you didn't take a backup of your stock boot and recovery before, then i think you'll have to go the long way by flashing the whole rom.
If you manage to install the 7.1.1 OTA after that, boot once into TWRP, backup stock recovery & boot and save it on your sdcard/pc. Then you can start flashing TWRP permantly, root, etc
Someone correct me, if I'm wrong.
Byte_76 said:
Where can I find the stock recovery for XT1650-03 RETEU without downloading an entire ROM zip file?
I have stock 7.0.0 with TWRP and Magisk 13.3.
I want to install the stock recovery so that I can install the 7.1.1 OTA which is available on my device, after which I will flash TWRP and root again. Will this work?
Click to expand...
Click to collapse
What is your build number?
lollyjay said:
What is your build number?
Click to expand...
Click to collapse
The current build number is NPLS25.86-30-12
Byte_76 said:
The current build number is NPLS25.86-30-12
Click to expand...
Click to collapse
Here is my recovery.img for NPLS25.86-30-12
https://drive.google.com/file/d/0B3gcDbDvV4MkOHhPd0lBVE9IMzg/view?usp=drivesdk
It should work for reteu also if not you can just reflash twrp:cyclops:
lollyjay said:
Here is my recovery.img for NPLS25.86-30-12
https://drive.google.com/file/d/0B3gcDbDvV4MkOHhPd0lBVE9IMzg/view?usp=drivesdk
It should work for reteu also if not you can just reflash twrp:cyclops:
Click to expand...
Click to collapse
Thank you!
---------- Post added at 12:31 AM ---------- Previous post was at 12:15 AM ----------
lollyjay said:
Here is my recovery.img for NPLS25.86-30-12
https://drive.google.com/file/d/0B3gcDbDvV4MkOHhPd0lBVE9IMzg/view?usp=drivesdk
It should work for reteu also if not you can just reflash twrp:cyclops:
Click to expand...
Click to collapse
Your recovery works on my Moto Z.
I now have stock 7.0.0 rooted with Magisk 13.3, stock recovery and unlocked bootloader.
If I proceed with the 7.1.1 OTA, will it work?
Byte_76 said:
Thank you!
---------- Post added at 12:31 AM ---------- Previous post was at 12:15 AM ----------
Your recovery works on my Moto Z.
I now have stock 7.0.0 rooted with Magisk 13.3, stock recovery and unlocked bootloader.
If I proceed with the 7.1.1 OTA, will it work?
Click to expand...
Click to collapse
You must have fully stock. I would suggest that you uninstall Magisk
lollyjay said:
You must have fully stock. I would suggest that you uninstall Magisk
Click to expand...
Click to collapse
The reason that I installed Magisk is because after unlocking the bootloader with the stock rom, it would not boot anymore. Installing a custom kernel or Magisk solves that issue.
Byte_76 said:
The reason that I installed Magisk is because after unlocking the bootloader with the stock rom, it would not boot anymore. Installing a custom kernel or Magisk solves that issue.
Click to expand...
Click to collapse
I still would suggest that you uninstall Magisk because the OTA would not work.
lollyjay said:
I still would suggest that you uninstall Magisk because the OTA would not work.
Click to expand...
Click to collapse
Okay I uninstalled Magisk which initiated an immediate reboot and resulted in a bootloop just after the bootloader message.
I think the issue occurs because the Data partition gets encrypted when root is uninstalled and decrpyption fails because of a bad key due to the unlocked bootloader.
To recover, I used TWRP to wipe/format the Data partition and then flashed the no_verity zip file from the thread below which disables encryption. I then ran "fastboot continue" after which my phone booted back into Android:
https://forum.xda-developers.com/moto-z/help/bricked-moto-z-unlocking-bootlader-t3634701
My phone status was then: Stock Android 7.0.0, no_verity patch (no encryption), stock recovery, unlocked bootloader.
So my phone is about as close to stock as I can get it with unlocked bootloader.
I finally attempted to install the 7.1.1 OTA again. It reboots and indicates that it is installing and then pops up with a message that says "Error".
Pressing the power and up button brings up the recovery screen with the error log (with info that I don't understand) and from there I can reboot into system again where I get another message indicating that the update failed and no changes were made.
I'm hesitant to install RETBR or other non-RETEU roms (Because although they might work, there probably are some differences such as LTE bands etc. and they are not actually correct for my phone) so I'm not sure how else to get to 7.1.1 unless the wifi issue is resolved with the image that Erfanoabdi uploaded in another thread or Lenovo releases an official 7.1.1 firmware package for the RETEU model.
Byte_76 said:
.....
To recover, I used TWRP to wipe/format the Data partition and then flashed the no_verity zip file from the thread below which disables encryption.........
Click to expand...
Click to collapse
You still have a modified ROM as you flashed "no_verity patch"
The best for you would be to search for your version of ROM and FASTBOOT FLASH everything back.
Then see if the 7.1.1 OTA wants to stick.
bert269 said:
You still have a modified ROM as you flashed "no_verity patch"
The best for you would be to search for your version of ROM and FASTBOOT FLASH everything back.
Then see if the 7.1.1 OTA wants to stick.
Click to expand...
Click to collapse
So far I have been unable to find the official RETEU firmware from Adnroid 7.0.0 and I'm hesitant to flash the firmware for another region because it isn't technically correct for my phone and there are likely small differences that might become an issue at a later stage. (Maybe the LTE bands are different etc...)
Byte_76 said:
So far I have been unable to find the official RETEU firmware from Adnroid 7.0.0 and I'm hesitant to flash the firmware for another region because it isn't technically correct for my phone and there are likely small differences that might become an issue at a later stage. (Maybe the LTE bands are different etc...)
Click to expand...
Click to collapse
The LTE band on RETEU is 20 and stays 20 with RETBR. No change and everything works. No issues with LTE.
As I mentioned before, the RETBR version is the only working 7.0 backup for RETEU devices. After flashing RETBR , the softwarechannel changed automatically into RETEU. With this, i took the OTA 7.1.1.
Btw. the 7.1.1 OTA doesn't even change the boot loader Nr.( 0x9107). That means, if you mess up with 7.1.1 you can safely downgrade to 7.0 by flashing RETBR (and take a fresh 7.1.1 OTA again)
Did that twice without issues.(for security reason i always skip the two lines with "bootloader" and "gpt" at the top of the flash commands)
bullfinch110 said:
The LTE band on RETEU is 20 and stays 20 with RETBR. No change and everything works. No issues with LTE.
As I mentioned before, the RETBR version is the only working 7.0 backup for RETEU devices. After flashing RETBR , the softwarechannel changed automatically into RETEU. With this, i took the OTA 7.1.1.
Btw. the 7.1.1 OTA doesn't even change the boot loader Nr.( 0x9107). That means, if you mess up with 7.1.1 you can safely downgrade to 7.0 by flashing RETBR (and take a fresh 7.1.1 OTA again)
Did that twice without issues.(for security reason i always skip the two lines with "bootloader" and "gpt" at the top of the flash commands)
Click to expand...
Click to collapse
Thank you for the clarification. I will take your advice and flash the RETBR firmware.
---------- Post added at 08:40 PM ---------- Previous post was at 08:01 PM ----------
bullfinch110 said:
The LTE band on RETEU is 20 and stays 20 with RETBR. No change and everything works. No issues with LTE.
As I mentioned before, the RETBR version is the only working 7.0 backup for RETEU devices. After flashing RETBR , the softwarechannel changed automatically into RETEU. With this, i took the OTA 7.1.1.
Btw. the 7.1.1 OTA doesn't even change the boot loader Nr.( 0x9107). That means, if you mess up with 7.1.1 you can safely downgrade to 7.0 by flashing RETBR (and take a fresh 7.1.1 OTA again)
Did that twice without issues.(for security reason i always skip the two lines with "bootloader" and "gpt" at the top of the flash commands)
Click to expand...
Click to collapse
I cannot get RSDLite to detect my phone in fastboot mode so I guess I'm going to have to run the fastboot commands manually.
What do you mean about skipping the bootloader and gpt commands? If I skip those, I keep my stock "unlocked bootloader" and "gpt" but then the phone probably won't boot again because that is very much like what I have now except that I flashed the no_verity patch when my phone would not boot.
What exactly are you avoiding by skipping those two lines? Should I skip them too?
---------- Post added at 08:46 PM ---------- Previous post was at 08:40 PM ----------
Byte_76 said:
Thank you for the clarification. I will take your advice and flash the RETBR firmware.
---------- Post added at 08:40 PM ---------- Previous post was at 08:01 PM ----------
I cannot get RSDLite to detect my phone in fastboot mode so I guess I'm going to have to run the fastboot commands manually.
What do you mean about skipping the bootloader and gpt commands? If I skip those, I keep my stock "unlocked bootloader" and "gpt" but then the phone probably won't boot again because that is very much like what I have now except that I flashed the no_verity patch when my phone would not boot.
What exactly are you avoiding by skipping those two lines? Should I skip them too?
Click to expand...
Click to collapse
Are these the commands that I should run?
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Byte_76 said:
Thank you for the clarification. I will take your advice and flash the RETBR firmware.
---------- Post added at 08:40 PM ---------- Previous post was at 08:01 PM ----------
I cannot get RSDLite to detect my phone in fastboot mode so I guess I'm going to have to run the fastboot commands manually.
What do you mean about skipping the bootloader and gpt commands? If I skip those, I keep my stock "unlocked bootloader" and "gpt" but then the phone probably won't boot again because that is very much like what I have now except that I flashed the no_verity patch when my phone would not boot.
What exactly are you avoiding by skipping those two lines? Should I skip them too?
Click to expand...
Click to collapse
It's out of my knowledge if your verity patch influences either bootloader or gpt partition. So i would recommend to flash those two commands in order to "repair" them. If you'll get an error message, skip them and proceed with the rest.
I always prefer RSD method instead of manually flashing by fastboot commands.
Have you installed the latest version of RSD-lite 6.2.4? Have you installed the latest moto drivers?
If you have extracted the RETBR. zip, search for "flashall.xml" file. Open it with a texteditor and you'll find the correct flashing commands.

[ROM][OREO][STOCK] LG V20 [20B][H990DS] Security Patch [01-APR-2019]

About
**********
I've created a flashable ROM zip of the latest H990DS KDZ SEA Region. Everything is working correctly on my H990 Single SIM.
ARB
**********
0
Security Patch
**********
1 April 2019
Download
**********
1. With modem & cust partitions (only if you know what you are doing):
https://drive.google.com/open?id=1YARnnE4-V1y9Jd1EhTzdizdkd6DaAYz_
2. Without modem & cust partitions (keeps your existing modem, recommended):
https://drive.google.com/open?id=1gCHxAk3hXjCsA4Qm3djgSmJEb3rSL5WA
Installation process:
**********
1. Upgrading / flashing over another stock Oreo ROM:
• Flash latest TWRP
• BACKUP everything
• Wipe (caches)
• Flash ROM
• Flash Magisk
• Flash MK2000 Oreo kernel (Important!)
• Reboot
• Enjoy
2. Clean from scratch install:
• Flash latest TWRP
• BACKUP everything
• Backup everything you want to put back, it will be wiped
• Clean wipe (data, system, caches)
• Flash ROM
• Flash Magisk
• Flash MK2000 Oreo kernel (Important!)
• Reboot
• Enjoy
flashing the second rom without modem or cust now on my h990ds , i hope everything goes well
sniper9911 said:
flashing the second rom without modem or cust now on my h990ds , i hope everything goes well
Click to expand...
Click to collapse
Just please remember to flash MK2000 kernel after you flash the ROM without rebooting in-between.
I made the mistake of rebooting afterwards and the stock kernel restored the stock recovery and wiped my device.
(This wasn't an issue because I made a full backup of all of my data though)
updated successfully
Updated the dirty way flashed over my current ROM ... I wiped cache and art cache just in case
Seems legit and so far my device is finishing the data setting , i did make a backup of my firmware files just in case and so far it went smoothly
All i did was downloading the ROM , Twrp , mk2000 h990ds v2.1 And Magisk latest
Flashed Twrp first then recovery rebooted , wiped Dalvick and cache then flashed ROM then flashed mk2000 then magisk and phone booted
Thanks for the update
I have also updated my H990DS successfully by "dirty" upgrade keeping all apps.
I just added H990DS_Hide_Boot_Warning.zip to remove the error message at boot start.
sniper9911 said:
Thanks for the update
Click to expand...
Click to collapse
tapir1505 said:
I have also updated my H990DS successfully by "dirty" upgrade keeping all apps.
Click to expand...
Click to collapse
Thanks for your feedback!
Glad to know it is working correctly
Against 20a the only difference is s3curity patch?
faeterov said:
Against 20a the only difference is s3curity patch?
Click to expand...
Click to collapse
I'm not sure of any other difference except the security patch.
I assume there are some minor tweaks as the update notification
generally mentions "usability improvements", but LG being LG don't
release a change-log so who knows unfortunately...
I have installed v20b (stock room and rooted room), but this version do not support fingerprint sensor, terrible, it took me more than 2 days for this :crying::crying:
luuhungit said:
I have installed v20b (stock room and rooted room), but this version do not support fingerprint sensor, terrible, it took me more than 2 days for this :crying::crying:
Click to expand...
Click to collapse
You'll need to provide more details than this.
Which variant V20? What ROM did you come from? Did you backup partitions? etc.
Also: to add, this is normally a modem issue and is resolved by restoring / flashing the correct modem
jl10101 said:
You'll need to provide more details than this.
Which variant V20? What ROM did you come from? Did you backup partitions? etc.
Also: to add, this is normally a modem issue and is resolved by restoring / flashing the correct modem
Click to expand...
Click to collapse
maybe, thank for idea
i is using h900ds, taiwan version
yesterday, i used LGUP to flash v20b version with refusbish function, but second sim and fingerprint inactive.
maybe refusbish function did not flashed all partition on device
today, i have to flash v10c to use dirtysanta root, then flash all partition of v20b version, but ignore aboot to keep bootloader unlocked, it is using with old data partition very well.
luuhungit said:
maybe, thank for idea
i is using h900ds, taiwan version
yesterday, i used LGUP to flash v20b version with refusbish function, but second sim and fingerprint inactive.
maybe refusbish function did not flashed all partition on device
today, i have to flash v10c to use dirtysanta root, then flash all partition of v20b version, but ignore aboot to keep bootloader unlocked, it is using with old data partition very well.
Click to expand...
Click to collapse
Go to 10c root flash 20a partitions through Patched LGUP ignoring aboot aboot.bak and recovery recovery.bak (tarp may be gone but as long as you'll have boatloads unlocked you can flash twrp back)after that just flash only 20b system via LGUP Partitions DL I dunno whats going on with LG KDZs from now on all you should keep the old partitions from 20A and just flash system
jl10101 said:
Just please remember to flash MK2000 kernel after you flash the ROM without rebooting in-between.
I made the mistake of rebooting afterwards and the stock kernel restored the stock recovery and wiped my device.
(This wasn't an issue because I made a full backup of all of my data though)
Click to expand...
Click to collapse
unfortunately im using F800L, so it will not work if i flash this rom into my device.
is there any change to tell me how to update the security patch for my device?
thx b4 m8
can I use this patch for H990DS IDN (Indonesia version) that is still 2.0? It's dual sim version...
thanks
stingbandel said:
can I use this patch for H990DS IDN (Indonesia version) that is still 2.0? It's dual sim version...
thanks
Click to expand...
Click to collapse
Yes. Use mk200 beta38
Update to 20B and Just remember to back up firmware and efs folders from Oreo 20A and restore after flashing 20B otherwise you will lose the second sim
sniper9911 said:
Updated the dirty way flashed over my current ROM ... I wiped cache and art cache just in case
Seems legit and so far my device is finishing the data setting , i did make a backup of my firmware files just in case and so far it went smoothly
All i did was downloading the ROM , Twrp , mk2000 h990ds v2.1 And Magisk latest
Flashed Twrp first then recovery rebooted , wiped Dalvick and cache then flashed ROM then flashed mk2000 then magisk and phone booted
Thanks for the update
Click to expand...
Click to collapse
I followed exact steps in OP (wiped caches, flashed 20b ROM, Magisk 19.3, MK2000 v2.2b38 H990DS, rebooted) and thought it worked for me as well until I noticed some built-in system apps were not working. Calendar, Chrome and others had strange names in Apps list (Chrome was called "add to dictionary" and Calendar was something like "on time (%s,..."). I managed to get them working again by stopping them and reinstalling from the apk files in system but wasn't sure I woudn't have other issues, so I wiped system partition and reflashed it although it didn't seem to change anything. When I noticed Bluetooth wouldn't enable I decided to go back to 20a by flashing full ROM (all done through TWRP) but that didn't fix the issue. I had even tried going back to MK2000 2.1 but no change. Finally had to do full restore from TWRP backup to get BT working again. Would like to have latest security patch.
Does anyone have any ideas what went wrong? Could any Magisk modules cause issues? Any help is appreciated.
Works perfect.
I flashed it straight from Lineague 16.1 after wipe, no problems.
(LG H990DS)
albaniax said:
Works perfect.
I flashed it straight from Lineague 16.1 after wipe, no problems.
Click to expand...
Click to collapse
Good to hear! Thanks for the feedback!
Hi. H990DS Twn variant. Currently running stock rom 20a (first oreo rom released for 990DS).
I see that you've uploaded another stock rom for 990DS that is 20H. But security patch is from FEB.
But this is a newer thread, so I assume this is the newest release. Could you please just confirm if this is the rom I should flash.
Thanks in advance
Salvaparalyzer said:
Hi. H990DS Twn variant. Currently running stock rom 20a (first oreo rom released for 990DS).
I see that you've uploaded another stock rom for 990DS that is 20H. But security patch is from FEB.
But this is a newer thread, so I assume this is the newest release. Could you please just confirm if this is the rom I should flash.
Thanks in advance
Click to expand...
Click to collapse
I'm not sure why 20H is effectively a "newer" ROM going by LG's naming convention.
They used 20B (this ROM) with a newer security patch, and the actual file is newer than 20H.
I would normally assume that 20H should have a newer security patch and be a newer build of Oreo, but it seems not.
This ROM essentially is the latest available. I cannot find any changelogs to verify that 20H has a newer system / android build though. Sorry!

Categories

Resources