Related
New to me tablet and I'm new to rooting/etc.
Factory tablet on 4.1.1, build 10.4.2.20-20121228
I downloaded and ran the Asus unlock utility, then ran motochopper to root. I then loaded TWRP 2.2.2.0 (I realized the mistake later). Made stock backup using twrp ok. Wiped cache/dalvik/etc and tried to recover to CM.10.0.0. Boots to cyanogenmod logo and just sits and spins. I can reboot back into recovery and restore from backup ok.
I realize now that I've loaded an early version of twrp, would that affect the cm bootup? If so, how do I upgrade twrp? Or should I try CM10.1 exp using twrp 2.2.2.0?
kbud123 said:
New to me tablet and I'm new to rooting/etc.
Factory tablet on 4.1.1, build 10.4.2.20-20121228
I downloaded and ran the Asus unlock utility, then ran motochopper to root. I then loaded TWRP 2.2.2.0 (I realized the mistake later). Made stock backup using twrp ok. Wiped cache/dalvik/etc and tried to recover to CM.10.0.0. Boots to cyanogenmod logo and just sits and spins. I can reboot back into recovery and restore from backup ok.
I realize now that I've loaded an early version of twrp, would that affect the cm bootup? If so, how do I upgrade twrp? Or should I try CM10.1 exp using twrp 2.2.2.0?
Click to expand...
Click to collapse
I can see you are on the 4.1 BL. I would suggest upgrading to the 4.2 bootloader and the using the most recent versions of TWRP and CM. You would do that by flashing the stock 4.2 Asus firmware, then the latest TWRP from their website with -42 and then the latest cyanogen mod ROM which is compatible with that bootloader.
cmendonc2 said:
I can see you are on the 4.1 BL. I would suggest upgrading to the 4.2 bootloader and the using the most recent versions of TWRP and CM. You would do that by flashing the stock 4.2 Asus firmware, then the latest TWRP from their website with -42 and then the latest cyanogen mod ROM which is compatible with that bootloader.
Click to expand...
Click to collapse
First off, thank you for the assistance. Here are the steps I believe I should take. Please correct me if I'm wrong.
1. Download and install latest 4.2 bootloader from Asus= US_epad-10.6.1.27.5
2. Would I need to download and install the unlocker from Asus? = Unlock_v8 for 4.2JB
3. Download and install TWRP for 4.2= TWRP 2.6.3.0-tf300t-4.2 blob
4. Then I should be able to run any of the CM 10.0.0 and up on the 4.2 bootloader, right?
kbud123 said:
First off, thank you for the assistance. Here are the steps I believe I should take. Please correct me if I'm wrong.
1. Download and install latest 4.2 bootloader from Asus= US_epad-10.6.1.27.5
2. Would I need to download and install the unlocker from Asus? = Unlock_v8 for 4.2JB
3. Download and install TWRP for 4.2= TWRP 2.6.3.0-tf300t-4.2 blob
4. Then I should be able to run any of the CM 10.0.0 and up on the 4.2 bootloader, right?
Click to expand...
Click to collapse
Lots of ppl are having problems with the V8 unlocker. Since you are already on 4.1, you could just unlock now with the V7 tool.
1. Unlock with V7 tool (http://forum.xda-developers.com/showthread.php?t=1949758)
2. Flash Latest Asus Stock (http://forum.xda-developers.com/showthread.php?t=1949758)
3. Download and install TWRP for 4.2= TWRP 2.6.3.0-tf300t-4.2 blob (http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.6.3.0-tf300t-4.2.blob)
4. Flash Latest CM (http://forum.xda-developers.com/showthread.php?t=2413878)
Personally, I would also make NvFlash Backups so you can restore your tablet just in case anything bad happens. Link is in my sig
cmendonc2 said:
Lots of ppl are having problems with the V8 unlocker. Since you are already on 4.1, you could just unlock now with the V7 tool.
1. Unlock with V7 tool (http://forum.xda-developers.com/showthread.php?t=1949758) Why would I use this now? Shouldn't I already be unlocked?
2. Flash Latest Asus Stock (http://forum.xda-developers.com/showthread.php?t=1949758)Will this put a locked or unlocked version on the tablet?
3. Download and install TWRP for 4.2= TWRP 2.6.3.0-tf300t-4.2 blob (http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.6.3.0-tf300t-4.2.blob)
4. Flash Latest CM (http://forum.xda-developers.com/showthread.php?t=2413878)
Personally, I would also make NvFlash Backups so you can restore your tablet just in case anything bad happens. Link is in my sig From what I'm reading, I can only do this after updating to 10.6.?.? So I would have to update to the latest Asus stock, then run this procedure.
Thanks again, and I appreciate your patience.
Click to expand...
Click to collapse
Ok, been reading until my eyes are bleeding.
From what I've read, Motochopper doesn't work for 10.6.1.27.x versions, so I would have to load 10.6.1.15.3. I should be able to download it and unzip it the first time on my pc. Then transfer it to the root directory of the tablet and run TWRP to install the .zip file. This would overwrite everything and bring it up to 4.2. I would then run the unlocker_v8 and install twrp for 4.2 using adb. If all that works, I should be rooted and unlocked and allowed to install CM 10 and above.
Please, anyone, check me on this. And thanks for the help.
kbud123 said:
Ok, been reading until my eyes are bleeding.
From what I've read, Motochopper doesn't work for 10.6.1.27.x versions, so I would have to load 10.6.1.15.3. I should be able to download it and unzip it the first time on my pc. Then transfer it to the root directory of the tablet and run TWRP to install the .zip file. This would overwrite everything and bring it up to 4.2. I would then run the unlocker_v8 and install twrp for 4.2 using adb. If all that works, I should be rooted and unlocked and allowed to install CM 10 and above.
Please, anyone, check me on this. And thanks for the help.
Click to expand...
Click to collapse
Oh sorry, I thought you meant that it had failed to unlock and flash.
Flashing a stock ROM will not relock your bootloader. Asus doesn't want people relocking their bootloader .
I'm not sure why you are using motochopper if you are going to install a custom ROM anyways. Almost all custom ROMs have the SU binaries in them.
Once you have unlocked your tablet, you will never need to run another unlocker, so dont worry about v8. The NvFlash backups need you to be on the 10.6.x.x bootloader, so you would flash the stock ROM then do the nvflash procedure.
cmendonc2 said:
Oh sorry, I thought you meant that it had failed to unlock and flash.
Flashing a stock ROM will not relock your bootloader. Asus doesn't want people relocking their bootloader .
I'm not sure why you are using motochopper if you are going to install a custom ROM anyways. Almost all custom ROMs have the SU binaries in them.
Once you have unlocked your tablet, you will never need to run another unlocker, so dont worry about v8. The NvFlash backups need you to be on the 10.6.x.x bootloader, so you would flash the stock ROM then do the nvflash procedure.
Click to expand...
Click to collapse
Just so I'm clear, I should be able to flash the stock rom w/ the TWRP I have now, using the install command for the zip file, right?
kbud123 said:
Just so I'm clear, I should be able to flash the stock rom w/ the TWRP I have now, using the install command for the zip file, right?
Click to expand...
Click to collapse
I'm not sure if you can flash the stock from the TWRP, to be safe I'd fastboot it from a computer. Once you flash the stock, it will upgrade the bootloader and erase TWRP. You would use the install command.
Success so far! I got it updated to 4.2.1 /10.6.1.27.5 using http://forum.xda-developers.com/showpost.php?p=35294881&postcount=1.
I put LRX21O on my N5 by sideloading the factory image (incl the fresh cache and userdata images). Worked fine!
I used ChainFire's first(?) Lollipop Autoroot package. I don't see a version in there, but all its files are dated 11/14. As I understand it, that method needed to patch the kernel to keep root.
His new package (as of 11/25) uses another method, allowing the kernel to remain stock. I did not run the new CFAR, but I let SuperSU update from the market and update the SU binary ("normal" method, not booting into recovery).
My questions:
Did that also undo the kernel patching from the earlier root retention method?
If not, how do I go back to the stock kernel without losing any data?
Thanks! Hope these aren't dumb-ass questions.
Well as far as I know Cf auto root just booted into another customised kernel by chainfire and then rooted the system. It didn't flash a new kernel. Maybe he changed the ramdisk. Not sure about that. But since nothing got flashed I doubt he changed even that.
On how to flash stock kernel just use flashify to flash the img or do it using fastboot.
Code:
fastboot flash boot boot.img
My understanding is that the ramdisk was changed, so that means the boot partition has been edited.
I just did a fastboot flash of the image:
Code:
fastboot flash boot boot.img
If you're really concerned, you can also flash system and re-root using the newer SuperSU ZIP. Flashing boot or system doesn't wipe data. I didn't bother with re-flashing system. No ill effects as far as I can tell.
Code:
fastboot flash system system.img
I've just flashed boot and system.
Then I had to reflash twrp.
Finally SuperSU. All working fine
This is only for devices currently on 4.4 or rooted 5.1 w/ moforoot. This upgrade path allows moforoot to continue to work, and retains the ability to downgrade to 4.4.
Note 12/2/2015:
Development on this has been discontinued with the release of the SunShine bootloader unlock.
To use SunShine without having to deal with KingRoot, you can flash the Rooted v3 system img and then use SunShine to unlock. This is the most stable method if you can use mofo.
After unlocking using SunShine, please flash the latest bootloader/radio images from here. This will bring your phone completely up to date and provide a more stable experience with custom ROMs.
These images are still flashable after unlocking your bootloader if you'd like a stable, closest-to-stock ROM possible.
Instead of using mofo to flash the system image, you can just use
Code:
fastboot flash system filename-goes-here.img
You can then flash your own tweaks like Xposed.
I'd recommend making a back up of the stock ROM in TWRP so you have a stable base to go back to if anything goes wrong.
Note 10/10/2015:
Updated all images to the latest OTA update (SU4TL-44) and included the latest official Xposed version (v75) in extras v5.
Follow the instructions with 5.1_images_v4.zip to flash the updated firmware images.
Note 9/5/2015:
Updated extras (v4) to include the latest official Xposed version (v73). Read the previous note for more information.
Note 8/31/2015:
Updated extras to the latest official Xposed version (v72). Reflashing all of the images is not required, only the extras system.img using mofo.
You can download the full extras image (1.5gb), or if you already have the rooted v2 image, use the extras v3 patch (8mb) with the instructions below.
Using the rooted v2 image + patch will allow you to update in the future without redownloading the entire image (as long as you keep the original after patching).
Note 7/23/2015:
Updated to the latest OTA (23.11.39). Make sure to follow instructions and reflash all images from the latest zip.
Unfortunately, I couldn't provide a patch to go from rooted image v1->v2, so a redownload is needed.
When applying the latest extras, make sure you're applying it to the rooted image v2.
Files (updated 10/10/2015 w/ latest OTA & extras v5)
5.1 firmware images (v4)
SHA1: 8be8a19664e6ba5aa556838bb3f744cdbf41f2ef
Stock 5.1 system image (v3)
SHA1: 1e67fc22331f035e9f3bd6c28d81fb173dd86a3e
Rooted 5.1 system image (v3)
SHA1: b8ff04d7f6ad9de31292cf62da94a3d80d3e373c
Extras 5.1 system image (rooted v3 + extras v5) (see below for details)
SHA1: 126744919f86132c05d15e79373ea759f74e37cf
Instructions
A data wipe is not required, but please back up any important data beforehand in case something goes wrong.
After extracting 5.1_images_v4.zip, reboot into bootloader and run the following commands to prepare your phone for the latest 5.1 system image:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem modem.img
fastboot flash mdm1m9kefs3 fsg.mbn
fastboot erase mdm1m9kefs1
fastboot erase mdm1m9kefs2
fastboot flash recovery recovery.img
fastboot erase ddr
fastboot reboot-bootloader
Then use mofo to flash the system image of your choice and reboot.
After flashing a system image, the first boot will stay on the Motorola logo for an extra 30 seconds to 1 minute. This is rebuilding the cache partition (erased by moforoot after every flash).
If your phone doesn't boot after 5 minutes (and isn't showing the "Upgrading apps" dialog), try formatting the cache in recovery by doing the following:
While phone is off, hold the volume down button and turn it on to boot into bootloader. Use the volume keys to find the recovery option and press power to confirm.
Once you see the dead Android (it may also say "No Command", this is normal), pull up the recovery menu by holding power and pressing volume up (5.1 recovery is different than 4.4) and use the wipe cache option.
If the screen is blank in recovery with a periodically flashing Android icon, try booting the phone normally and trying again. This happened to me a few times, and I theorize it's because of the cache partition not being formatted after erased.
Extras (updated 10/10/2015 w/ latest OTA & Xposed official v75)
Download patch (v5)
SHA1: 451be2eef3df509facf16b807c6fc665c8fac090
If you don't want to deal with patching the image using xdelta3, you can download the full extras image in the Files section above.
This will prevent you from updating without redownloading the whole image in the future, but is easier for less experienced users.
Current extras:
Xposed official v75 (download APK from here)
(optional) ad blocking
busybox/sqlite3
tethering enabled
To apply the patch, use the rooted v3 image (not an already patched image) as a base, and follow the patching instructions (using xdelta3) in this post.
After patching the system.img with the extras, you'll use mofo to flash the patched image.
To use ad blocking, download AdAway (available in F-Droid) and enable it. Make sure the "Target hosts file" is set to "/data/hosts" in settings.
shouldnt we also be updating the radio?
diabl0w said:
shouldnt we also be updating the radio?
Click to expand...
Click to collapse
I haven't personally tested upgrading the radio, and whether that affects downgrading at all. If someone confirms it's without risk, I'll add the radio.img to the zip and instructions.
firstEncounter said:
I haven't personally tested upgrading the radio, and whether that affects downgrading at all. If someone confirms it's without risk, I'll add the radio.img to the zip and instructions.
Click to expand...
Click to collapse
ive downgraded radio from 4.4 to 4.2 in the past, but it messed up wifi somehow... isnt wifi part of the modem image? anyways, nothing else bad happened so idk if this is useful info
edit: when i did the downgrade (4.4.4 to 4.4.2 radio) it disabled the ability to turn on wifi and log messages gave the error wifistatemachine: failed to load wifi driver
diabl0w said:
ive downgraded radio from 4.4 to 4.2 in the past, but it messed up wifi somehow... isnt wifi part of the modem image? anyways, nothing else bad happened so idk if this is useful info
Click to expand...
Click to collapse
It looks like radio is just a collection of the modem images, so that should eliminate some of the commands. I'll update the OP.
firstEncounter said:
It looks like radio is just a collection of the modem images, so that should eliminate some of the commands. I'll update the OP.
Click to expand...
Click to collapse
check my edit
diabl0w said:
check my edit
Click to expand...
Click to collapse
Radios won't be compatible across ROM versions. You would flash the 4.4.4 radio if downgrading to a 4.4.4 image, not while running 5.1.
Ummmmm. Is this a dream? Someone pinch me...... There's no one around....... Can this really be true!? I'm afraid to try it and bork everything.
firstEncounter said:
This is only for devices currently on 4.4, requires moforoot. This upgrade path allows moforoot to continue to work, and retains the ability to downgrade to 4.4.
Files:
5.1 upgrade images
Stock 5.1 system image
Rooted 5.1 system image
After extracting the 5.1_images_v2.zip, run the following commands to prepare your phone for a 5.1 system image:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot erase ddr
(Commands based on this post. Thanks @mikeoswego and @JulesJam!)
Then use mofo to flash the system image of your choice.
Xposed and Adblock images coming soon.
Click to expand...
Click to collapse
Why aren't you flashing 5.1 recovery?
JulesJam said:
Why aren't you flashing 5.1 recovery?
Click to expand...
Click to collapse
Missed that command in the OP. Thanks!
Is the rooted image debloated
Sent from my XT1254 using Tapatalk
JulesJam said:
Why aren't you flashing 5.1 recovery?
Click to expand...
Click to collapse
So we should do that command as well?
janitorjohnson said:
So we should do that command as well?
Click to expand...
Click to collapse
I had trouble when I tried to stay on 5.0 recovery after I flashed 5.1 system image on my MX14.
JulesJam said:
I has trouble when I tried to stay on 5.0 recovery after I flashed 5.1 system image on my MX14.
Click to expand...
Click to collapse
Is that the final command?
trikotret said:
Is the rooted image debloated
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
No, it's completely stock with SuperSU installed.
janitorjohnson said:
Is that the final command?
Click to expand...
Click to collapse
I do
logo
boot
recovery
radios
But I do that b/c that is the way they are usually written in the scripts that come with the images. I think the only 2 where the order really matters is the bootloader and partition table and you aren't flashing those.
---------- Post added at 05:18 AM ---------- Previous post was at 05:16 AM ----------
firstEncounter said:
No, it's completely stock with SuperSU installed.
Click to expand...
Click to collapse
I went ahead and made one too just in case there were any issues with FirstEncounter's since I already have a device set up to do this anyhow.
https://www.dropbox.com/s/rmuev8agm5wl2lh/XT1254_5.1_root_system_ext4.zip?dl=0
PLMK if there are any issues with my image. I will take it down once people have started to modify the images, test them and are sure there are no issues.
It should be easy for someone to modify the buildprop so you can have free tether.
works like a charm
firstEncounter said:
This is only for devices currently on 4.4, requires moforoot. This upgrade path allows moforoot to continue to work, and retains the ability to downgrade to 4.4.
Files:
5.1 upgrade images
Stock 5.1 system image
Rooted 5.1 system image
After extracting the 5.1_images_v2.zip, run the following commands to prepare your phone for a 5.1 system image:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot erase ddr
Then use mofo to flash the system image of your choice.
Xposed and Adblock images coming soon.
Click to expand...
Click to collapse
Followed instructions to a T and used OP's files... Everything works like a charm and is buttery smooth: http://imgur.com/ZwIRB8X
Bootloader acted a little weird, got a couple screen flickers... not sure if related or not. It worked itself out after one or two reboots. Thanks for the awesome instructions!
Just updated the OP with a patch for Xposed, ad blocking, busybox and tethering. Let me know if it works for everyone.
firstEncounter said:
Just updated the OP with a patch for Xposed, ad blocking, busybox and tethering. Let me know if it works for everyone.
Click to expand...
Click to collapse
Thank you! You are working mighty quickly I must say. We all really appreciate it!
I can not seem to boot it to recovery after doing the steps in OP. Little man blinks and says "no command" under him. Wanted to do a factory reset after the steps in OP. Any ideas? I am letting it boot into LP for the first time and then will try to get into recovery to do the reset.
After I let LP boot up, I could enter into recovery and factory reset without a problem.
I have rooted my Xperia L stock ROM 15.3.A.1.17 and unlocked the bootloader. Now I wish to install TWRP recovery on a separate partition. As indicated on official TWRP page on Xperia L,
The Xperia devices have a recovery-in-boot arrangement. This means that the recovery is booted using the regular kernel / boot image in the device. Team Win has worked with the FreeXperia device maintainers to come up with a way to extract the ramdisk from the FOTAKernel partition and use the ramdisk from that partition instead of the recovery that is included in the boot image of your device. This means that if you install current CM nightlies and flash TWRP to the FOTAKernel partition, you will be able to use TWRP instead of the CWM or CM recovery that normally comes in a CM boot image. Other boot images including stock kernels can be repacked to include this extraction utility to allow you to use TWRP from the FOTAKernel partition. This setup allows you to choose what recovery you want to have installed and allows you to update your recovery more easily. Unfortunately this setup requires that the boot image that you have installed include the ramdisk extraction utility. The source for this utility is here.
This setup means that you must have a kernel or boot image installed that will use the FOTAKernel method. This utility is designed to work in conjunction with the current methods that most AOSP ROMs, like OmniROM or CyanogenMod, will support. Some rare stock kernels may also support the FOTAKernel method.
What does all this mean? It means that TWRP may not work on your device unless you install other custom software as well. Check with your ROM developer to see what they support.
Click to expand...
Click to collapse
However, the stock kernel does not support FOTAkernel method a.ka. extract_elf_ramdisk feature. The webpage does not address the issue of running TWRP on stock kernel. It's like a chicken and egg problem. To have TWRP running, one needs a custom kernel. To flash a custom ROM, one needs TWRP (or other custom recovery).
I can think of two possible ways of breaking this deadlock.
Possible method #1:
Flash TWRP using Recovery Installer Toolkit for Xperia L
Flash a custom ROM (zip) from this recovery
Flash TWRP to FOTAkernel using official TWRP app or dd-ing a TWRP raw image on FOTAkernel partition or using Recoveries and Recovery Installer for Taoshan
Possible method #2:
Use a stock ROM image with TWRP integrated:
Code:
adb flash boot boot_twrp2.img
Flash a custom ROM (zip) from this recovery
Flash TWRP to FOTAkernel using official TWRP app or dd-ing a TWRP raw image on FOTAkernel partition or using Recoveries and Recovery Installer for Taoshan
Possible method #3:
Boot into fastboot mode
Flash the TWRP image directly onto the boot partition
Code:
fastboot flash boot twrp.img
Reboot the phone which now should boot directly to TWRP recovery
The screen flickers when you are in recovery menu. However, flashing a custom ROM will fix the problem
Flash a custom ROM (zip) from this recovery
Flash TWRP to FOTAkernel using official TWRP app or dd-ing a TWRP raw image on FOTAkernel partition or using Recoveries and Recovery Installer for Taoshan
As of now, I installed TWRP on FOTAkernel partition using official TWRP app. As expected, when I issue,
Code:
adb reboot recovery[/CODEL] the phone boots to stock recovery instead of TWRP. This behavior is expected as stock kernel knows nothing about TWRP being located on FOTAkernel.
I don't even know if any of the proposed methods work. However, before embarking down any one of those routes, I want to ask the community if I am overlooking any straightforward, less cumbersome alternative(s).
[B]Credits:[/B]
[LIST]
[*] Dees_Troy
[*] Kungfu73
[/LIST]
Holmes.Sherlock said:
I have rooted my Xperia L stock ROM 15.3.A.1.17 and unlocked the bootloader. Now I wish to install TWRP recovery on a separate partition. As indicated on official TWRP page on Xperia L,
However, the stock kernel does not support FOTAkernel method a.ka. extract_elf_ramdisk feature. The webpage does not address the issue of running TWRP on stock kernel. It's like a chicken and egg problem. To have TWRP running, one needs a custom kernel. To flash a custom ROM, one needs TWRP (or other custom recovery).
I can think of two possible ways of breaking this deadlock.
Possible method #1:
Flash TWRP using Recovery Installer Toolkit for Xperia L
Flash a custom ROM (zip) from this recovery
Flash TWRP to FOTAkernel using official TWRP app or dd-ing a TWRP raw image on FOTAkernel partition or using Recoveries and Recovery Installer for Taoshan
Possible method #2:
Use a stock ROM image with TWRP integrated:
Code:
adb flash boot boot_twrp2.img
Flash a custom ROM (zip) from this recovery
Flash TWRP to FOTAkernel using official TWRP app or dd-ing a TWRP raw image on FOTAkernel partition or using Recoveries and Recovery Installer for Taoshan
As of now, I installed TWRP on FOTAkernel partition using official TWRP app. As expected, when I issue,
Code:
adb reboot recovery[/CODEL] the phone boots to stock recovery instead of TWRP. This behavior is expected as stock kernel knows nothing about TWRP being located on FOTAkernel.
I don't even know if any of the proposed methods work. However, before embarking down any one of those routes, I want to ask the community if I am overlooking any straightforward, less cumbersome alternative(s).[/QUOTE]
Well, I think installing latest TWRP directly from stock XL ROM for first time is hard for everyone :D
I myself exactly used first method and worked fine. Also please note that in step 2 of method 1, you should install some Lollipop or KitKat versions of custom ROM (because current recovery is old)
I've not tested 2nd method, but it should work too.
I think these methods are the most simple ones if you want to jump from stock to latest TWRP ;)[COLOR="Silver"]
[SIZE=1]---------- Post added at 12:06 PM ---------- Previous post was at 11:53 AM ----------[/SIZE]
[/COLOR]Oh I forgot to mention that there is another (a little risky) way to use latest TWRP.
Using adb&fastboot run this command:
[B]fastboot flash boot twrp.img[/B]
[I](twrp.img is your recovery image name)[/I]
This command flashes recovery image directly to boot partition and because of that, when you power on the phone, you jump directly to TWRP recovery!
[B] Please note that in this method, the screen flickers when you are in recovery menu, but it's normal and gets fixed by flashing custom ROM
Note 2: immediately after booting to recovery, flash your custom ROM to avoid any problems![/B]
If there were any problems, simply flash stock ROM to get back to normal state.
Click to expand...
Click to collapse
Kungfu73 said:
Also please note that in step 2 of method 1, you should install some Lollipop or KitKat versions of custom ROM (because current recovery is old)
Click to expand...
Click to collapse
I don't get the point why I need a KitKat/Lollipop based custom ROM. What do you mean by current recovery being old?
Oh I forgot to mention that there is another (a little risky) way to use latest TWRP.
Using adb&fastboot run this command:
fastboot flash boot twrp.img
(twrp.img is your recovery image name)
This command flashes recovery image directly to boot partition and because of that, when you power on the phone, you jump directly to TWRP recovery!
.
Click to expand...
Click to collapse
I talked to @Dees_Troy on IRC about the issue and he suggested the same to me.
.
Please note that in this method, the screen flickers when you are in recovery menu, but it's normal and gets fixed by flashing custom ROM
Note 2: immediately after booting to recovery, flash your custom ROM to avoid any problems!
If there were any problems, simply flash stock ROM to get back to normal state.
Click to expand...
Click to collapse
I am also experiencing flickering. It's surprising to hear that the problem is supposed to go away with custom ROM. Do you have any idea how does having a custom ROM make any difference at all?
Holmes.Sherlock said:
I don't get the point why I need a KitKat/Lollipop based custom ROM. What do you mean by current recovery being old?
Click to expand...
Click to collapse
Well, the version of twrp that recovery installer app flashes, is 2.7 or something like that (not 3.0.2) and it may fail to flash MM or N ROMs (it's mentioned in some official custom ROMs download page to use latest TWRP)
Holmes.Sherlock said:
I am also experiencing flickering. It's surprising to hear that the problem is supposed to go away with custom ROM. Do you have any idea how does having a custom ROM make any difference at all?
Click to expand...
Click to collapse
If you mean by difference, fixing the flickering, well it wipes boot partition while flashing ROM, and (some of ROMs) flash latest TWRP to fota agian, and it fixes that
But if you mean difference between stock and custom ROM, well... it depends on your using. The most obvious ones are the improved security and more space for apps and tons of customizable and useful features, etc.
(And also sorry if I had mistakes in English!)
Kungfu73 said:
Well, the version of twrp that recovery installer app flashes, is 2.7 or something like that (not 3.0.2) and it may fail to flash MM or N ROMs (it's mentioned in some official custom ROMs download page to use latest TWRP).
Click to expand...
Click to collapse
The installer app lets you choose the version to flash. You can very well flash any version (of twrp.img) downloaded on your phone.
Holmes.Sherlock said:
The installer app lets you choose the version to flash. You can very well flash any version (of twrp.img) downloaded on your phone.
Click to expand...
Click to collapse
Oh this is what that makes difference!
On stock ROM, you can only use old TWRP's that are compatible with stock ROMs that don't support fota !
And also you should use the recovery that the app gives to you
Kungfu73 said:
On stock ROM, you can only use old TWRP's that are compatible with stock ROMs that don't support fota !
And also you should use the recovery that the app gives to you
Click to expand...
Click to collapse
The app gives a list of all recovery versions available on the official website for category `taoshan`. Are you sure that there is some TWRP version that does not support FOTA and works with stock ROM?
Holmes.Sherlock said:
The app gives a list of all recovery versions available on the official website for category `taoshan`. Are you sure that there is some TWRP version that does not support FOTA and works with stock ROM?
Click to expand...
Click to collapse
Well, if you check the official twrp website, there is no version before 2.8 for XL , and lol those removed ones are compatible!
Kungfu73 said:
Well, if you check the official twrp website, there is no version before 2.8 for XL , and lol those removed ones are compatible!
Click to expand...
Click to collapse
I am curious to know how come any TWRP version be compatible with stock ROM unless the recovery ramdisk is integrated with the boot image than being written onto FOTAkernel.
Holmes.Sherlock said:
I am curious to know how come any TWRP version be compatible with stock ROM unless the recovery ramdisk is integrated with the boot image than being written onto FOTAkernel.
Click to expand...
Click to collapse
I don't have much detailed information about that.
You can get help from experts
And could you finally flash and boot any version of twrp using that 3 methods?
Kungfu73 said:
And could you finally flash and boot any version of twrp using that 3 methods?
Click to expand...
Click to collapse
I tried method #2 and #3. Both works
[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root
THIS GUIDE IS NOW DEPRECATED. THERE IS NO NEED ANYMORE TO GO THROUGH THE UPDATING PROCESS AS THERE IS A FULL NOUGAT FACTORY IMAGE AVAILABLE (Build NPH25.200-22). FIRMWARE AVAILABLE HERE: https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 BE SURE TO THANK @acejavelin FOR TRACKING DOWN THE FIRMWARE PACKAGE FOR US.
Notes:
-YOU ATTEMPT THIS AT YOUR OWN RISK IF YOU FLASHED ANY FIRMWARE PREVIOUSLY NOT FOR THE XT1575 US VERSION
-This guide will have 2 parts. 1 for those that kept their systems read only/systemless, and 1 for those that did not.
-Whether you live booted TWRP or Installed TWRP, if you chose to allow system modifications your OTA will likely fail (you'll need part 2).
-Restoring a TWRP backup will not work and will cause an OTA to fail due to having to allow system write access in TWRP - You Need Part 2.
-This guide assumes you have basic ADB knowledge and already know what fastboot is and how it works.
-Thanks to @gokart2 for the OTA and @acejavelin for the return to stock guides
Part 1: Those That Tweaked Systemlessly Currently On 24.49-18-16 (Will only work if you kept TWRP read only/used systemless root):
1: Disable & Remove systemless Xposed within Magisk Manager and all other Magisk modules. Reboot and wait for Art cache to rebuild.
2: Remove any adblock hosts within your adblock app if installed, or any other root level system altering apps like Greenify (don't worry, you'll get them back).
3: Remove Magisk by booting into TWRP and flashing the current Magisk Removal zip. Reboot.
4: For systemless SuperSu you need to consult their thread as I do not use it. (I'll update this if someone knows the correct process).
5: ADB reboot bootloader and fastboot flash the stock recovery. Latest MM recovery links at the bottom of this post. (rename file to recovery.img).
6: Move the OTA Blur_Version.24.231.16.clark_retus.retus.en.US.zip to the root of your internal sd card (NOT in a folder). File links at the bottom of the post. Thanks @gokart2
7: ADB reboot recovery, when "no command" is listed, hold power + tap volume up then release to access recovery options. Choose "apply update from phone storage". Choose the file and wait for the flash. It's a large update so be patient (about 10-20min). Choose reboot manually in recovery after flash succeeds. Enjoy Nougat!
8: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly.
Part 2: Those That Have Done Everything - TWRP Write Access, Custom Roms, On Older Firmware, Etc (XT1572 Build Flashers Do This At Their Own Risk):
1: Flash the latest full factory image available (24.49-18-8) available here: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110. Thank @acejavelin for the thread while your at it. Follow the directions in that guide, it's well detailed and accurate - however read my notes just below first:
NOTES:
-Omit the "fastboot oem lock begin" & "fastboot oem lock" commands to remain bootloader unlocked.
-Omit the "fastboot erase userdata" command if you want to dirty flash and keep all of your data. I recommend clean, you can always root & restore each apps data with Titanium after the Playstore installs everything.
-The "fastboot oem fb_mode_set" instead of "fastboot oem lock begin" & "fastboot oem fb_mode_clear" instead of "fastboot oem lock" I've found to be unnecessary if staying unlocked. Your choice.
-The "fastboot flash partition gpt.bin" & "fastboot flash bootloader bootloader.img" commands will likely fail due to version mismatches. This is ok.
-The "fastboot flash modem NON-HLOS.bin" tends to fail too. For this, just run the command again until it succeeds.
2: After flashing 24.49-18-8 take the OTA to 24.49-18-16. Reboot. OTA zip provided below if you prefer to sideload.
3: Either install the 7.0 OTA the normal way via the update center or just side load it using the directions above. I recommend side loading due to the file size being very close to 1GB.
4: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly!
For Xposed, See My Guide Here: https://forum.xda-developers.com/showpost.php?p=74014516&postcount=96
Stock MM 24.49-18-16 Recovery: https://mega.nz/#!aZpC2RzQ!Fy3GTo_XYPjB1lwuHffCUUERuvnsyvON3kS8kMJ9Cm8
Stock MM 24.49-18-16 Recovery Mirror: https://drive.google.com/file/d/0BxxRfNko9QDKNS1NdnAyZVp6dVU/view?usp=sharing
24.49-18-8 OTA to 24.49-18-16: https://mega.nz/#!yZx2FLzR!cWfKIAYe5VyuadLI55UNHJvwWU98CXUi1g0DO1pDoKg
NPH25.200-22 OTA: https://mega.nz/#!HVhWWLxK!h-8G3vO3Sye_YwypyIJyWb2_79Ow34vNiDnMl2Q8uJg
NPH25.200-22 OTA Mirror: https://drive.google.com/file/d/0B3gPYUZ4nRLwOHJKQnNYczNEMHc/view?usp=sharing
MD5 for NPH25.200-22 OTA: 74d1a4b135200661cc4efd248f99ce33
Stock 7.0 NPH25.200-22 Recovery: https://mega.nz/#!TNoHQAjI!5U2w4p_G7pHlW6Mak7LqFR_PeWUDpSLc7S3OiUs_Qf8
Alrighty. I got back to stock 6.0 with the 18-16 update. I couldn't get the OTA via the system update, so I tried doing it via ADB. That threw up a "status 7 error". I then copied the file to my internal storage and selected update via SD Card in recovery. It hung on "Patching System Files" for a while, but in the end it moved on and worked fine. Thanks for the awesome guide!
Thread updated with downloads for the 24.49-18-8 OTA to 24.49-18-16 zip.
I exctracted the 7.0 Stock recovery to replace if you decide to flash TWRP and want to go back to the stock recovery for future updates (HAHAHA yeah right!). Download link in OP. The 7.0 Recovery is different than the MM recovery. They are not interchangeable. Don't flash the 7.0 recovery on MM.
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Bwangster12 said:
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Click to expand...
Click to collapse
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
annoyingduck said:
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
Click to expand...
Click to collapse
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Here's the recovery before the 7.0 one, just incase.. Was bored. Ok, I won't lie....didn't see u posted the 7.0 recovery....lol.:good::highfive:
Bwangster12 said:
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
Click to expand...
Click to collapse
Yup. TWRP flashes and works, magisk v14 works, and so far systemless xposed api24 is working.
EsteBandido4444 said:
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Click to expand...
Click to collapse
What is everyone's fascination with relocking the bootloader? You do not need to relock your bootloader. You cannot relock the bootloader unless all your system partitions match. Use my part 2 section. Read the notes, skip the bootloader lock commands. Leave your bootloader unlocked, get up and running on nougat, then you can issue the lock commands if you really want a locked bootloader.
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
EDIT nevermind didn't read lol
Amp699435 said:
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
Click to expand...
Click to collapse
Copy the file to the root of your internal storage. Reboot into recovery. Hold power = volume up & release to access menu options. Choose apply update from storage. Select the OTA.zip package and let it install. (Directions are clearly written in OP.)
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
Click to expand...
Click to collapse
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
GrandAdmiral said:
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
Click to expand...
Click to collapse
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
annoyingduck said:
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
Click to expand...
Click to collapse
Gotcha. I know I'm going to root again, but I've never used Magisk before so I wasn't sure of that piece.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
I am running Dirty Unicorns right now and when i looked up what I'm on in fastboot, it showed MPSH24.49-18-16. Would I just follow part 2 and use MPSH24.49-18-8 or something? I thought I had to use at least the version I'm on or newer.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.[/QUOTE
Your issue is that TWRP has modified your
System, any restoring of the stock rom will fail to update. So yes, you'll need to go through part 2 and downgrade and work your way back up.
Click to expand...
Click to collapse
I downloaded the zip (it took a while).
Restored to stock like 3 different ways but still hit a road block. I went the adb sideload route but got status error 7 because my build fingerprint wasn't correct. I tried searching for the right build I need, but I'm not an expert and couldn't find the right set of files that I was sure I knew how to restore. I ended up restoring my AICP backup.
If somebody could PM me and give me a hand (messaging through Hangouts or something) that would be AWESOME!
I'm planning trying to snag an XL 2 pre-order next week, but until then the less headache the better! Plus stock Nougat looks better on a Swappa listing
Trying to sideload via recovery 24.49-18-16 but I keep getting "("unexpected contents:EMMC:/dev/block/bootdevice/by-name/boot...". I've also tried installing from the phone but the same error appears in recovery. Any ideas?