(XT-1644) Lost Root after TWRP stock Rooted ROM restore - Moto G4 Plus Questions & Answers

I've never ran into this issue all the Android Devices I have owned. I'm hoping it's something simple yet annoying as fukc. Not sure if it's a TWRP issue ? SuperSU (latest version after update) is there and it shows as all apps are Granted su permissions.
As of right now, I'm back to my original stock MPJ24.139-49 , with unlocked bootloader. I am seeing a few different SuperSU(s) in the threads to flash. I would just flash stock firmware but trying to get to file is a pain in the ass.
Any help greatly appreciated...

https://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip this works for me and i also restored from nandroid backup and didn't lose root so yeah try it u don't need to patch boot.img or anything just flash it with twrp dats it

Related

Updating firmware and root?

Hi guys,
I know how rooting and flashing works but I've been using HTC devices since the nexus one so there are some differences I just want to make sure of. I got my 6P yesterday, I unlocked the bootloader and flashed TWRP. I wanted to gain root but Im not sure about flashing the modified boot img and the vendor thing.
My build was K but I got an OTA before unlocking the bootloader which updated to L. Anyway I don't know why I just formatted every thing in TWRP instead of the factory reset and I lost the OS X_X I tried to restore my nandroid with no luck. Anyway I got the factory img (MDB08L) from google dev and flashed used 'flash-all.bat' in the bootloader, the phone is running fine right now but I would like to update to the latest firmware 6.0.1+root since im not getting any OTA.
I would like to install CleanCore(6.0.1), the guide is
-> Flash Bootloader & Radio (as needed)
-> Flash CleanCore
-> Flash Modified Boot (named angler-xxxxxx-boot.zip)
-> Flash SuperSU or SuperSU Beta
-> Flash latest vendor.img (ROM & Vendor builds need to match!)
1. Should I use MMB29M factory img and flash 'flash-all.bat' like I did with the L build for the first step? then I flash new recovery?
-Flashing the rom through the recovery
2. so after I flash the rom I boot into the bootloader and flash the modified boot img with fastboot flash boot boot.img right?
3. then I go back to recovery and flash SU which I should download before.
4. vendor img is flashed in recovery too or fastboot?
Sorry for the hassle I just want to make sure.
One more thing, in this guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 at step 9, OP flashes the factroy img files separately (bootloader,radio,etc), is there a problem with using flashall.bat?
Thanks in advance and sorry for my noobish questions.
If you want to keep your data while doing this process, then yes, using the flash-all.bat is a problem. However, if you are fine with reverting back to stock(where you have to activate Android and reinstall all of your apps) then the flash-all.bat file is just fine.
That guide in the thread you linked walks you through how to update without losing data. After doing all of that, you'll just need to install TWRP and SuperSU again(do the latest systemless supersu though)
Enddo said:
If you want to keep your data while doing this process, then yes, using the flash-all.bat is a problem. However, if you are fine with reverting back to stock(where you have to activate Android and reinstall all of your apps) then the flash-all.bat file is just fine.
That guide in the thread you linked walks you through how to update without losing data. After doing all of that, you'll just need to install TWRP and SuperSU again(do the latest systemless supersu though)
Click to expand...
Click to collapse
Thanks for the help.
I have rooted my stock rom and gained root. I also installed exposed so i'll be fine without a custom rom for some time. There has been a report that some cameras aren't working on 6.0.1 with root so I'll wait for a while.
Thanks again
mr.dj26 said:
Thanks for the help.
I have rooted my stock rom and gained root. I also installed exposed so i'll be fine without a custom rom for some time. There has been a report that some cameras aren't working on 6.0.1 with root so I'll wait for a while.
Thanks again
Click to expand...
Click to collapse
I'm pretty sure those reports are because they used the SuperSU root method that didn't auto patch the boot image(which is the version(or two versions) behind the current version of SuperSU). This is happening because people are updating to 6.0.1, but the patched SuperSU boot image is for 6.0 and the 6.0 boot image conflicts with 6.0.1
As long as you use the latest version of SuperSU then you won't have any trouble with the camera
Enddo said:
I'm pretty sure those reports are because they used the SuperSU root method that didn't auto patch the boot image(which is the version(or two versions) behind the current version of SuperSU). This is happening because people are updating to 6.0.1, but the patched SuperSU boot image is for 6.0 and the 6.0 boot image conflicts with 6.0.1
As long as you use the latest version of SuperSU then you won't have any trouble with the camera
Click to expand...
Click to collapse
Thanks for the info

Stock rooted Lollipop with TWRP - Is this the best method to upgrade to MM?

There are a few threads that deal with upgrading lollipop to marshmallow, but they seem to raise as many questions as they answer - mainly since they were usually written before rooted images were distributed.
Basically, I am on an unlocked, rooted stock XT1575 with TWRP 2.8.7.0. It sounds like it's less efficient and has lots of potential problems to go back to stock, unroot, install OTA, do new system root, and re-add TWRP.
Instead, it sounds like the simplest method to get to stock rooted MM, with least steps and potential problems, should be this:
Update TWRP to 2.8.7.1 using IMG file here from within TWRP Recovery (TWRP Manager did not install it when I tried via Android proper - I was still at 2.8.7.0)
Do a full TWRP backup of my current Lollipop stock rooted installation (I assume this means I can restore without problems if the MM install goes awry)
*Optional: Use Titanium Backup to backup settings of important apps, and text messages/MMS.
In TWRP, Wipe->Swipe to Factory Reset
Transfer to phone and Flash via TWRP the stock rooted odexed ROM from this thread (not sure if there is a good argument for deodexed? I've never gotten a clear answer why one should be better, but would stick with odexed just because I believe it is "stock" so maybe less problems?)
Install SuperSU 2.62 from this thread by simply flashing it as normal in TWRP 2.8.7.1.
Reinstall all programs on initial setup. [*Optional: Reinstall via Titanium backup]
I assume if I do this I will: have marshmallow; have root; have working TWRP.
Does anyone see any obvious problems with this method? Thanks, I really appreciate any comments.
EDIT: Yes, I tried this method. It all worked, except I've added SuperSU installation steps that worked for me, since the "Stock Rooted" ROM is NOT actually rooted when I flash it. Also, used Titanium Backup successfully for some programs, so added that as an option.
Sorry to bump, but any response from someone with experience would be very helpful. I just want to make sure I don't have to go through the whole unroot/OTA/reinstall TWRP/reinstall root procedure that every thread says seems to cause problems...
Answered my own question - edited the main post to show the method used successfully.
Thank you for this answer thread. I was looking for the simplest answer for upgrading to MM without having to unroot and reflash everything. Looks like this is the easiest for now (I have having to reinstall everything, since some games I play to NOT react nicely to data being restored via titanium).
Have a brand new XT1575 with 5.1.1, Does the MM Update break root ability. I primarily want it for xposed, adaway. No ROMing
Should I update and then root? or root and then update?
I personally have found that following this method breaks root possibilities. MM is rooted, but when I got to the point of installing SuperSU via these steps, it broke EVERYTHING (settings stopped working, Motorola Services stopped working, etc).
I have to start from scratch again now.

Upgrading Rooted (TWRP+SU) PE 1575 from 5.1 to M. Need Advice + I have a guide

Hello,
Now before you ask, I've been doing a lot of research though searching threads and post. I'm actually going to post everything I found so far. On my first attempt of getting Marshmallow a few weeks ago, I downloaded the OTA and installed it. BIG mistake as I had TWRP and stock update didn't know what to do. I had to use CLARK to go back to stock then restore my phone back to Lolipop. Then I had to fix my Wifi Issue. After that I started doing a lot of research.
Here's all of my research links:
[FiRMWARE] XT1575 PuRE FiRMWARE aNd STuFF
Already Rooted Moto X Pure 2015 (KitKat) - Upgrade to Marshmallow, How?
Marshmallow and root -pg 2
MXPE on the way. Root after getting M update? (POST #18)
I need some input on people who have already went though this. So, this is what I'm getting:
1) Flash/Update to TWRP twrp-2.8.7.1-clark.img
2) Download "XT1575 stock unrooted TWRP backup" (from the first link). UNZIP THE FILE and place it in the TWRP folder on your phones internal storage.
3) Reboot into Recovery. Backup, then Restore the "XT1575 stock unrooted TWRP backup" image
4) If TWRP ask to install SuperSU, DON'T INSTALL
5) Let the phone boot back up and setup Marshmallow.
NOW, in order to Restore your apps+data with Titanium Backup, your phone has to be rooted. Currently, your phone is not rooted so you have to do the following:
6) Download 2.62 supersu and move it to internal/external SD.
7) Reboot into Twerp.
8) Install 2.62 supersu
9) Reboot
10) Test Titanium Backup and you should be OK.
Now, has anybody used this method or a similar method? I think this is possibly a correct method. Also reading that there's no need to use the seamless root since you can use supersu 2.62.
Personally I would flash the full stock mm firmware in fastboot. Then flash twrp and root. I don't believe your method will update modem.
lafester said:
Personally I would flash the full stock mm firmware in fastboot. Then flash twrp and root. I don't believe your method will update modem.
Click to expand...
Click to collapse
But if it doesn't update the modem, I could just flash that on there though TWRP right? NON-HLOS.bin?
If I can get some more feetback, it would be great. I'm going to attempt in one more day. If everything goes good, I want to make a quick guide since it's hard to find concrete guides for this situation.

Moto X Play bootlooping after installing SuperSU

Hi,
A while ago i unlocked the bootloader so that i can root but have only had chance to do it now. I flashed SuperSU the same way as people who rooted successfully but now my phone bootloops. I did have a nandroid backup but i cant find it now so there isnt a backup. I flashed each system file seperatly as people had said and still no luck. I cant factory reset for some reason. Any help would be much appreciated.
You need a systemless root:
http://forum.xda-developers.com/showpost.php?p=66735900&postcount=126

17S update - can't root phone anymore

Hi,
Can anyone help me, please?
I used to have the version 16s installed on my phone but after the forced update, got the official 17s version installed.
Lost root access and got a lot of chinese apps installed.
Now I can't root my phone anymore. I've tried a a lot of methods/twrps and can't get the phone to boot to twrp recovery.
After flashing the recovery.img, phone only reboot again to the chinese rom.
From what I'm reading on a xda topic, it seems the same as this guy:
http://forum.xda-developers.com/leeco-le1-pro/development/letv-x800-ruschrom-1-0-25e-t3224702/page41
Thanks for the reply. My phone used to be rooted, too (Lollipop), but became unrooted during an unwanted OTA update and can not be re-rooted ever since (Marshmallow). None of the King/o/root/etc. apps did the job over ADB from a pc or installed on my phone. Flashing supersu zip from TWRP got my phone into a bootloop last night from which I could only get out by re-locking the bootloader and installing a stock ROM. The bloody 17v update notice keep popping up and I have no choice but to let it install sooner or later. If I ever manage to re-root my device, I'll try your method.
laoki said:
Hi,
Can anyone help me, please?
I used to have the version 16s installed on my phone but after the forced update, got the official 17s version installed.
Lost root access and got a lot of chinese apps installed.
Now I can't root my phone anymore. I've tried a a lot of methods/twrps and can't get the phone to boot to twrp recovery.
After flashing the recovery.img, phone only reboot again to the chinese rom.
From what I'm reading on a xda topic, it seems the same as this guy:
http://forum.xda-developers.com/leeco-le1-pro/development/letv-x800-ruschrom-1-0-25e-t3224702/page41
Thanks for the reply. My phone used to be rooted, too (Lollipop), but became unrooted during an unwanted OTA update and can not be re-rooted ever since (Marshmallow). None of the King/o/root/etc. apps did the job over ADB from a pc or installed on my phone. Flashing supersu zip from TWRP got my phone into a bootloop last night from which I could only get out by re-locking the bootloader and installing a stock ROM. The bloody 17v update notice keep popping up and I have no choice but to let it install sooner or later. If I ever manage to re-root my device, I'll try your method.
Click to expand...
Click to collapse
CN? Or US!?
dieselman6969 said:
CN? Or US!?
Click to expand...
Click to collapse
Thank you for your reply, it is CN version.
I was able to root the phone again, by doing fastboot commands manually.
flash recovery, flash misc
After that, I was able to enter recovery mode.

Categories

Resources