Database Info

[Q] Unroot to update, without reflash ?

Hello,
I need some help with the transformer firmware upgrade.My tf is rooted,and therefor the update process fails with a orange ! android.I red that an unroot is absolutely nescessary in order to upgrade,but I am looking for a way to do it without refashing and then reinstalling everything.From what I understand both methods listed here: http://is.gd/nGRo5s implie a complete reinstall.
So,any way to get the update without re-installing anything ?
Thanks.

There is a way to flash the update without reinstalling everything, but you need to change your recovery.
A non-stock recovery will let you flash a modified OTA that will let you keep root. Or even better, just flash a rooted stock image.

Great !
Do you have a link to the modified recovery I should use and one to the modified FOTA ?
I assume I would be doing this using the update.zip function of the modded recovery ?
Thanks for the help !

Roach has a modded version of Clockworkmod
http://forum.xda-developers.com/showthread.php?t=1213723
I'm not sure anyone has posted a 8.6.5.13 rom yet.
Edit: the OTA will break root since it will flash a secure boot.img.
---------- Post added at 08:16 PM ---------- Previous post was at 07:59 PM ----------
Actually, if you have the stock recovery, there will be a few extra steps to flash CWM.
You can 1) use nvflash and modify the commands so that it doesn't erase everything or 2) use terminal and flash the recovery through the staging partition.
Then, after you have a working recovery, you can modify the OTA to flash without breaking root or giving you a secure boot.img.
---------- Post added at 08:55 PM ---------- Previous post was at 08:16 PM ----------
I think terminal will be easier since Roach packed up his recovery as a blob. What a guy!
1) download the zip file from Roach's thread
2) unzip it and you'll find a file called recoveryblob- save this to your external SD card
3) use adb or terminal and type
Code:
su
dd if=/Removable/MicroSD/recoveryblob of=/dev/block/mmcblk0p4
reboot
The last piece is zero-pee-four. Be sure to get this right or else you'll be gravely inconvenienced. Your TF will reboot and CWM ala Roach will flash. You'll see a turquoise progress bar and then your TF will reboot.
edit again: daoist posted this already http://forum.xda-developers.com/showthread.php?t=1281161
once you have clockworkmod, go to his thread and flash via clockworkmod.
Happy Flashing!

Well,that's a precise answer ! I'll do the flah soon and will update this thread.Thanks for the help !

After Custom Recovery OTA and Recovery-flashable Incrementals Don't work

I've had the OPO for over a year, and just now had the need to root it. An OTA happened to come in the next day, and the update process didn't work as I expected. So I'd like to know if I did something wrong, a random problem occurred, or this is the way it's supposed to work.
Until a couple days ago, the OPO was stock + all OTAs that had been released. I unlocked the bootloader, installed TWRP recovery, and installed SuperSU. All that went as expected. When the OTA notification arrived the next day, I tried to install it with "Update Cyanogen recovery" still unchecked (because original reports with CM 11S said you could keep your custom recovery with an OTA).
When I tried to install the update, the phone just rebooted to TWRP and the update was not stored anywhere on /sdcard. I then checked "Update Cyanogen recovery" and tried to install the OTA again. It did not install, and TWRP was still my recovery. Several repeats of this had no different result.
Then I flashed the stock CM recovery with fastboot. After verifying I had the CM recovery, I installed the OTA again, and it failed again, reboting to recovery and doing nothing else. Then I downloaded the incremental update and tried to flash that via CM recovery, and that failed too. I checked the file /System/build.opt, and line "ro.build.version.incremental" said 49d90510ef, which meant I should have been able to install the cm-bacon-49d90510ef-to-d91bf047f5-signed.zip file. But it failed and said the current build number was not as expected. The number it gave me was not anything that made sense looking at the list of recent incremental updates.
So at that point I bailed out and installed via recovery the full flashable zip file, and that worked.
If this is what I have to do each time, it's certainly doable, but I don't think this is how it's supposed to go. I'm surprised the OTA didn't work with the custom recovery installed, and I'm even more surprised that the incremental installation failed. Maybe trying to install the OTA without updating the CM recovery messed things up, but that doesn't seem likely either. When the next OTA comes out, I'll see if any of these troubles are repeated. But I'd like to know how the OTA was supposed to work after installing a custom recovery.

I am still yet to figure this one out also, my friend I'm sure with time someone will respond who had better experience with this; just be patient
Have you been able to root yet? I can't seem to be able to on the new incremental yet.
@MidnightJava

Looks like I'm not the only one with this problem.
I'm trying to find now the link for Cyanogen Recovery flashable to see it that fix the OTAs

Check the CyanogenMod website, @distante

vince.lupe said:
Have you been able to root yet? I can't seem to be able to on the new incremental yet.
@MidnightJava
Click to expand...
Click to collapse
After installing the latest CM 12.1 ROM, I had to re-flash SuperSU. After doing that, root access is working fine. If you're having trouble rooting after installing the incremental, then my experience is perhaps not applIcable—since I was not able to do an incremental installation and had to re-flash the entire ROM.

distante said:
Looks like I'm not the only one with this problem.
I'm trying to find now the link for Cyanogen Recovery flashable to see it that fix the OTAs
Click to expand...
Click to collapse
This thread with Cyanogen mirrors and info has exactly what you need.

MidnightJava said:
After installing the latest CM 12.1 ROM, I had to re-flash SuperSU. After doing that, root access is working fine. If you're having trouble rooting after installing the incremental, then my experience is perhaps not applIcable—since I was not able to do an incremental installation and had to re-flash the entire ROM.
Click to expand...
Click to collapse
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/

vince.lupe said:
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/
Click to expand...
Click to collapse
What happens when you try to root? Does it seem successful, but then you don't actually have root access? Or do you get some failure indication when you flash SuperSU? I've rooted a few phones in the last few years, but I'm far from an expert. Hopefully someone else will jump in with some idea of what went wrong. Shooting somewhat in the dark, I'd say look at the version of SuperSU and make sure it's the latest and the right one for the ROM, look at read-write permissions on your storage (if you can, you may need root access to check it properly). Of course wiping cache is always a good step, and if nothing else works, maybe factory reset, re-lock the bootloader, and then unlock and flash custom recovery again, and see if root can be successful then.

Once on custom recovery ( TWRP ) OTAs will NOT not install, unless you revert back to CM stock recovery. If you don't want to do that, wait for a signed flashable version to come out, which is normally 1-2 days after. Everytime you flash an update you will have to reinstall TWRP and SuperSU.
---------- Post added at 03:31 PM ---------- Previous post was at 03:25 PM ----------
vince.lupe said:
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/
Click to expand...
Click to collapse
Did you guys remove the " Update Cyanogen recovery" in Dev options and "respect CM root settings " In SuperSU settings ?

Cholerabob said:
Once on custom recovery ( TWRP ) OTAs will NOT not install, unless you revert back to CM stock recovery. If you don't want to do that, wait for a signed flashable version to come out, which is normally 1-2 days after. Everytime you flash an update you will have to reinstall TWRP and SuperSU.
Click to expand...
Click to collapse
I figured that was the case when it failed. What seems anomalous in my case is that even after reverting to the stock recovery and verifying that it was installed, OTAs would not succeed. I didn't know about the "respect CM root settings " In SuperSU settings that you mentioned. Maybe that was the problem? Either that or the fact that I tried to install the OTA first with the custom recovery. Certainly the fact that the incremental installation reported I was at a different build number than what was listed in /System/build.opts indicates something was out of whack on my phone.
Temporarily reverting to the stock recovery and installing the OTA, then going back to custom recovery, seems a bit simpler than flashing the signed zip file and then re-installing recovery and SuperSU, but either way is not too bad. But being an engineer, I always have to find the optimum path and understand why things don't work the way I thought they should.

MidnightJava said:
What happens when you try to root? Does it seem successful, but then you don't actually have root access? Or do you get some failure indication when you flash SuperSU? I've rooted a few phones in the last few years, but I'm far from an expert. Hopefully someone else will jump in with some idea of what went wrong. Shooting somewhat in the dark, I'd say look at the version of SuperSU and make sure it's the latest and the right one for the ROM, look at read-write permissions on your storage (if you can, you may need root access to check it properly). Of course wiping cache is always a good step, and if nothing else works, maybe factory reset, re-lock the bootloader, and then unlock and flash custom recovery again, and see if root can be successful then.
Click to expand...
Click to collapse
It just tells me that I don't have access :/ Everything flashes perfectly fine, but then when I boot up and try to access root, it tells me that I don't have access. I've tried everything already :/
---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------
Cholerabob said:
Did you guys remove the " Update Cyanogen recovery" in Dev options and "respect CM root settings " In SuperSU settings ?
Click to expand...
Click to collapse
I did do both :/

MidnightJava said:
I figured that was the case when it failed. What seems anomalous in my case is that even after reverting to the stock recovery and verifying that it was installed, OTAs would not succeed. I didn't know about the "respect CM root settings " In SuperSU settings that you mentioned. Maybe that was the problem? Either that or the fact that I tried to install the OTA first with the custom recovery. Certainly the fact that the incremental installation reported I was at a different build number than what was listed in /System/build.opts indicates something was out of whack on my phone.
Temporarily reverting to the stock recovery and installing the OTA, then going back to custom recovery, seems a bit simpler than flashing the signed zip file and then re-installing recovery and SuperSU, but either way is not too bad. But being an engineer, I always have to find the optimum path and understand why things don't work the way I thought they should.
Click to expand...
Click to collapse
Not really since the signed zip file come with superSU, after the install it will ask you if you want to install superSU automatically, and TWRP will too when you start your TWRP app on your phone after reboot. But to each his own
---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------
vince.lupe said:
It just tells me that I don't have access :/ Everything flashes perfectly fine, but then when I boot up and try to access root, it tells me that I don't have access. I've tried everything already :/
---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------
I did do both :/
Click to expand...
Click to collapse
Is your bootloader unlocked ? Reinstalled superSU ? Did you check with the fastboot command ? If you don't know how, look at Heisenberg's guide.

Cholerabob said:
Not really since the signed zip file come with superSU, after the install it will ask you if you want to install superSU automatically, and TWRP will too when you start your TWRP app on your phone after reboot. But to each his own
---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------
Is your bootloader unlocked ? Reinstalled superSU ? Did you check with the fastboot command ? If you don't know how, look at Heisenberg's guide.
Click to expand...
Click to collapse
Yes, bootloader is unlocked and SuperSu was reinstalled :/

J700P Boot-Loop

Heya. I restored a full backup in TWRP, and I ended up bootlooping. I tried flashing stock firmware, and nothing has changed. I can access downloading mode, and I can flash TWRP and boot into that. Any help? I've tried everything I've came.

I used flashify to get twrp into recovery but it recovery looped and the only way i got out of it was to reflash root with odin. Hope that helps.
Is your device still rooted? I was getting set warranty bit: recovery. It just kept going back to twrp.
Sent from my SM-J700P using Tapatalk

Synz86 said:
I used flashify to get twrp into recovery but it recovery looped and the only way i got out of it was to reflash root with odin. Hope that helps.
Is your device still rooted? I was getting set warranty bit: recovery. It just kept going back to twrp.
Sent from my SM-J700P using Tapatalk
Click to expand...
Click to collapse
I'll try reflashing the root thing. Thanks.
EDIT: Does not work.

No problem, good luck. Let me know if it works, took me a couple times.
Sent from my SM-J700P using Tapatalk

I personally just had to reflash stock boot.img in odin when i got my bootloop and all was well

where can i download the stockl firmware for the boost mobile variant. I am in a bootloop here and have tried everything . I need the stock firmware so i can flash it via odin.

Having the same problem!
I rooted, flashed twrp, and Xposed successfully and made a complete backup. I got a little excessive with my debloating, so I tried to restore my nandroid backup with twrp.. Been bootlooped ever since. I tried flashing the stock boot, recovery, and rom with odin. Nothing works. The best result I can get is when I use Odin to flash stock firmware, then flash the chainfire autoroot. If I do that, it still bootloops, but it gets all the way to the "optimizing apps" screen... If I don't flash the autoroot, it loops after the virgin mobile logo. If I try to use stock rom, cf autoroot, and twrp, it goes all crazy at the initial Samsung screen and won't even loop. I've tried every combination I can think of. Maybe has something to do with the initial welcome/activation not being active? I would think the stock rom does have it enabled though.. HELP PLEASE! I have the 2016 variant from Virgin, 6.1.1
---------- Post added at 01:39 PM ---------- Previous post was at 01:35 PM ----------
DirtyPISTOLA said:
I personally just had to reflash stock boot.img in odin when i got my bootloop and all was well
Click to expand...
Click to collapse
Do you have the 2016 Virgin mobile variant? I know the 2015s have different firmware and seem to have no problems unbricking. Just curious

uberpyrit said:
I rooted, flashed twrp, and Xposed successfully and made a complete backup. I got a little excessive with my debloating, so I tried to restore my nandroid backup with twrp.. Been bootlooped ever since. I tried flashing the stock boot, recovery, and rom with odin. Nothing works. The best result I can get is when I use Odin to flash stock firmware, then flash the chainfire autoroot. If I do that, it still bootloops, but it gets all the way to the "optimizing apps" screen... If I don't flash the autoroot, it loops after the virgin mobile logo. If I try to use stock rom, cf autoroot, and twrp, it goes all crazy at the initial Samsung screen and won't even loop. I've tried every combination I can think of. Maybe has something to do with the initial welcome/activation not being active? I would think the stock rom does have it enabled though.. HELP PLEASE! I have the 2016 variant from Virgin, 6.1.1
---------- Post added at 01:39 PM ---------- Previous post was at 01:35 PM ----------
Do you have the 2016 Virgin mobile variant? I know the 2015s have different firmware and seem to have no problems unbricking. Just curious
Click to expand...
Click to collapse
You need an adb enabled boot.img and get a logcat on boot to know the reason of this problem

chucksaysblah said:
where can i download the stockl firmware for the boost mobile variant. I am in a bootloop here and have tried everything . I need the stock firmware so i can flash it via odin.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-j7/how-to/sm-j700p-stock-recovery-stock-boot-t3423314
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
messi2050 said:
You need an adb enabled boot.img and get a logcat on boot to know the reason of this problem
Click to expand...
Click to collapse
OK. Would the boot.img extracted from the stock rom be adb enabled? I'm on my way to work, so I'll have to wait till I get home to try.

uberpyrit said:
http://forum.xda-developers.com/galaxy-j7/how-to/sm-j700p-stock-recovery-stock-boot-t3423314
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
OK. Would the boot.img extracted from the stock rom be adb enabled? I'm on my way to work, so I'll have to wait till I get home to try.
Click to expand...
Click to collapse
No It's not

uberpyrit said:
http://forum.xda-developers.com/galaxy-j7/how-to/sm-j700p-stock-recovery-stock-boot-t3423314
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
OK. Would the boot.img extracted from the stock rom be adb enabled? I'm on my way to work, so I'll have to wait till I get home to try.
Click to expand...
Click to collapse
You need to go to CoffeeNAndroids thread here http://forum.xda-developers.com/galaxy-j7/development/adb-root-access-boot-image-custom-t3431590 to downkoad the adb enabled boot.img

DirtyPISTOLA said:
You need to go to CoffeeNAndroids thread here http://forum.xda-developers.com/galaxy-j7/development/adb-root-access-boot-image-custom-t3431590 to downkoad the adb enabled boot.img
Click to expand...
Click to collapse
Downloaded and flashed the adb-enabled boot.img, now doing the research on how to make it work so i can post my logcat output. ive never done this before so im having to research it(noob, sorry ) i dont want to waste anyones time, ill figure it out, but if someone has time and could post the steps to do it id be grateful. gonna read up on it till i figure out how to work it anyway, but in the meantime someone could be reading my logs.

uberpyrit said:
Downloaded and flashed the adb-enabled boot.img, now doing the research on how to make it work so i can post my logcat output. ive never done this before so im having to research it(noob, sorry ) i dont want to waste anyones time, ill figure it out, but if someone has time and could post the steps to do it id be grateful. gonna read up on it till i figure out how to work it anyway, but in the meantime someone could be reading my logs.
Click to expand...
Click to collapse
np we all were noobs in the beginning here are the steps
-connect your phone to pc
-download mini adb from here :
http://forum.xda-developers.com/showthread.php?t=2317790
-turn on your phone and while it's stuck at sam logo type in mini adb [adb logcat -v long > name of problem.txt}
-u will get a file in the mini adb folder upload it here so i can help you .

messi2050 said:
np we all were noobs in the beginning here are the steps
-connect your phone to pc
-download mini adb from here :
http://forum.xda-developers.com/showthread.php?t=2317790
-turn on your phone and while it's stuck at sam logo type in mini adb [adb logcat -v long > name of problem.txt}
-u will get a file in the mini adb folder upload it here so i can help you .
Click to expand...
Click to collapse
ok, so, every way i try this it isnt working. i flashed twrp so i could do a total wipe. then flashed the stock rom/firmware(J700PVPU1APB7.tar.md5). i flashed the adb-enabled boot.img and tried the logcat, it says waiting on device while the phone bootloops... when i flash cfautoroot and adb boot.img after rom flash, same thing. What am I doing wrong? Device drivers and adb drivers installed 2 weeks ago.
so, i just flashed stock rom:cfautoroot:adb boot.img:stock recovery, and it started to boot properly, ie: android updating apps to android starting, and a bunch of other stuff, then rebooted to bootloop.. farther than ive gotten so far.
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
uberpyrit said:
ok, so, every way i try this it isnt working. i flashed twrp so i could do a total wipe. then flashed the stock rom/firmware(J700PVPU1APB7.tar.md5). i flashed the adb-enabled boot.img and tried the logcat, it says waiting on device while the phone bootloops... when i flash cfautoroot and adb boot.img after rom flash, same thing. What am I doing wrong? Device drivers and adb drivers installed 2 weeks ago.
so, i just flashed stock rom:cfautoroot:adb boot.img:stock recovery, and it started to boot properly, ie: android updating apps to android starting, and a bunch of other stuff, then rebooted to bootloop.. farther than ive gotten so far.
Click to expand...
Click to collapse
trying to recreate the process now...

uberpyrit said:
ok, so, every way i try this it isnt working. i flashed twrp so i could do a total wipe. then flashed the stock rom/firmware(J700PVPU1APB7.tar.md5). i flashed the adb-enabled boot.img and tried the logcat, it says waiting on device while the phone bootloops... when i flash cfautoroot and adb boot.img after rom flash, same thing. What am I doing wrong? Device drivers and adb drivers installed 2 weeks ago.
so, i just flashed stock rom:cfautoroot:adb boot.img:stock recovery, and it started to boot properly, ie: android updating apps to android starting, and a bunch of other stuff, then rebooted to bootloop.. farther than ive gotten so far.
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
trying to recreate the process now...
Click to expand...
Click to collapse
You didn't did anything wrong , it's coffenandroid adb enabled is not working correctly , now try to flash stock recovery as i heard that twrp cause bootloop on j700p

messi2050 said:
No It's not
Click to expand...
Click to collapse
Hey messie,
I have somehow switched the variant of my boost j7 when I was rebuilding it with wifi tethering anyways since I did that my phone is on xas which is Australia I believe and it was working fine even on that variant until I put twrp on it and not even the stock boost firmware has fixed it I do have a backup before the variant was changed that was made with FlashFire but the twrp backup FlashFire makes by default doesn't work and all it does it boot loop over and over and sometimes it will say it is optimizing apps sometumes but doesn't ever load it just reboots and repeats the same thing I tried doing a complete wipe in twrp and tried ur debloated firmware which was very similar to the project I was working on as well as a cm port. I can't go any further on my projects until I can get functionality outta the phone again is there maybe a way I could load FlashFire in twrp as I have root and adb working fully or it there other stuff I could do in adb to fix this I even tried Making the csc only for BST instead of XAS but no go it had no effect

Starchild2k said:
Hey messie,
I have somehow switched the variant of my boost j7 when I was rebuilding it with wifi tethering anyways since I did that my phone is on xas which is Australia I believe and it was working fine even on that variant until I put twrp on it and not even the stock boost firmware has fixed it I do have a backup before the variant was changed that was made with FlashFire but the twrp backup FlashFire makes by default doesn't work and all it does it boot loop over and over and sometimes it will say it is optimizing apps sometumes but doesn't ever load it just reboots and repeats the same thing I tried doing a complete wipe in twrp and tried ur debloated firmware which was very similar to the project I was working on as well as a cm port. I can't go any further on my projects until I can get functionality outta the phone again is there maybe a way I could load FlashFire in twrp as I have root and adb working fully or it there other stuff I could do in adb to fix this I even tried Making the csc only for BST instead of XAS but no go it had no effect
Click to expand...
Click to collapse
Hi
Although a logcat is needed to solve the problem , i believe that this happens because of the kernel security , i think that a permissive kernel is included in this file
http://www.mediafire.com/?u6skqbc4x5bo73p
If it's there flash it and you should have successful boot proces , good luck!

messi2050 said:
Hi
Although a logcat is needed to solve the problem , i believe that this happens because of the kernel security , i think that a permissive kernel is included in this file
http://www.mediafire.com/?u6skqbc4x5bo73p
If it's there flash it and you should have successful boot proces , good luck!
Click to expand...
Click to collapse
Thanx Messi I am going to try it now

messi2050 said:
np we all were noobs in the beginning here are the steps
-connect your phone to pc
-download mini adb from here :
http://forum.xda-developers.com/showthread.php?t=2317790
-turn on your phone and while it's stuck at sam logo type in mini adb [adb logcat -v long > name of problem.txt}
-u will get a file in the mini adb folder upload it here so i can help you .
Click to expand...
Click to collapse
im still working on getting the logs, nothing seems to make the phone readable to logcat. it just says waiting for device..

Starchild2k said:
Thanx Messi I am going to try it now
Click to expand...
Click to collapse
np , tell me if it works for you
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
uberpyrit said:
im still working on getting the logs, nothing seems to make the phone readable to logcat. it just says waiting for device..
Click to expand...
Click to collapse
I'm going to make one and upload it

Trouble rooting my Pixel

I have tried TWRP (twrp.me/devices/googlepixel.html) and the Unified Android Toolkit (skipsoft.net/download/uat-v156/) to root the Pixel I bought directly from Google. With TWRP, I cannot see the .zip I downloaded (the phone is encrypted and /sdcard/* are all gibberish names; I'm never prompted for a decrypting password when booting for recovery) and with the Toolkit I end up in a reboot loop (I've tried twice with the same results).
I'm surprised that the Toolkit thinks my build is "Verizon" (NDE63X). I'm not sure if that matters.
Thoughts? Pointers? Diagnostics? TIA.

go get the new alpah2 of twrp.
---------- Post added at 01:51 PM ---------- Previous post was at 01:48 PM ----------
Save v4 root on sd. Save alpha 2 img on desktop, and .zip on sd on phone. fastboot img, enter pin or pattern, then flash alpha2 zip. restart in recovery, flash v4 root. Done.

computercarl said:
go get the new alpah2 of twrp.
---------- Post added at 01:51 PM ---------- Previous post was at 01:48 PM ----------
Save v4 root on sd. Save alpha 2 img on desktop, and .zip on sd on phone. fastboot img, enter pin or pattern, then flash alpha2 zip. restart in recovery, flash v4 root. Done.
Click to expand...
Click to collapse
Thanks. That gets me further. I put twrp-pixel-installer-sailfish-3.0.2-0-alpha2.zip and SR3-SuperSU-v2.78-SR3-20161103171345.zip on the SD card. I booted with twrp-3.0.2-0-alpha2-fastboot-sailfish.img and I could see the zips. I installed alpha2.zip, reboooted, installed SuperSU, rebooted. I don't see SuperSU in my app list. I'm missing something. I'm not sure what you mean by "v4 root".

ChrisNelsonPE said:
Thanks. That gets me further. I put twrp-pixel-installer-sailfish-3.0.2-0-alpha2.zip and SR3-SuperSU-v2.78-SR3-20161103171345.zip on the SD card. I booted with twrp-3.0.2-0-alpha2-fastboot-sailfish.img and I could see the zips. I installed alpha2.zip, reboooted, installed SuperSU, rebooted. I don't see SuperSU in my app list. I'm missing something. I'm not sure what you mean by "v4 root".
Click to expand...
Click to collapse
Since you have to temp boot twrp, I just use adb sideload to flash the twrp and SuperSU zips.
I reflash stock boot img
Boot into twrp from fast boot
Sideload twrp zip
Reboot recovery
Sideload supersu sr4 zip

GeekMcLeod said:
Since you have to temp boot twrp, I just use adb sideload to flash the twrp and SuperSU zips.
...
Sideload supersu sr4 zip
Click to expand...
Click to collapse
I found download.chainfire.eu/1013/SuperSU/SR4-SuperSU-v2.78-SR4-20161115184928.zip. Trying that shortly.

ChrisNelsonPE said:
I found download.chainfire.eu/1013/SuperSU/SR4-SuperSU-v2.78-SR4-20161115184928.zip. Trying that shortly.
Click to expand...
Click to collapse
Just let me know if you need any help. I'd happily help you get your phone rooted.

GeekMcLeod said:
Just let me know if you need any help. I'd happily help you get your phone rooted.
Click to expand...
Click to collapse
SU4 did it for me.
And a shout out to the Helium app for moving my data, even without root. Best $5 I spent this year!

ChrisNelsonPE said:
SU4 did it for me.
And a shout out to the Helium app for moving my data, even without root. Best $5 I spent this year!
Click to expand...
Click to collapse
I'm curious, I think I have ADB set up correctly but I have never had any luck I. Using it before ( mainly because of ADB language and commands to do what I want to do). Is there a guide that tells people like myself what to type and where to put files? Man that would be nice .

quinejh said:
I'm curious, I think I have ADB set up correctly but I have never had any luck I. Using it before ( mainly because of ADB language and commands to do what I want to do). Is there a guide that tells people like myself what to type and where to put files? Man that would be nice .
Click to expand...
Click to collapse
I highly recommend that if you're going to be doing stuff like this to your phone you get familiar with ADB and fastboot otherwise you're just asking for trouble. Each of the threads on custom recovery and root have the links and instructions including commands, read everything twice since you're new to this and I mean everything.

I stupidly tried to install the new OTA while rooted

I saw a notification for a new system OTA and, without thinking, I downloaded and installed it even though I'm rooted.
So when the install starts, it just boots to TWRP. And every time I reboot back into system, it attempts to install the OTA again and just boots me back to TWRP.
Any help?

clankfu said:
I saw a notification for a new system OTA and, without thinking, I downloaded and installed it even though I'm rooted.
So when the install starts, it just boots to TWRP. And every time I reboot back into system, it attempts to install the OTA again and just boots me back to TWRP.
Any help?
Click to expand...
Click to collapse
A quick Google search would have yielded the answer almost immediately, just clear (wipe) caches and reboot.

acejavelin said:
A quick Google search would have yielded the answer almost immediately, just clear (wipe) caches and reboot.
Click to expand...
Click to collapse
thank you

so your phone survived the update? I would like to know if I can install it on my TWRP'd phones. Thanks.

bradmoss said:
so your phone survived the update? I would like to know if I can install it on my TWRP'd phones. Thanks.
Click to expand...
Click to collapse
It won't install, it will get stuck in recovery... Wiping cache deleted the update file and allows the phone to boot to its previous state.

where is the update file?
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
I wiped the cache but it still keeps in the loop...

bradmoss said:
where is the update file?
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
I wiped the cache but it still keeps in the loop...
Click to expand...
Click to collapse
All you did was try to update and wiping cache didn't fix it? Then there is more wrong. Backup in TWRP and do a factory reset (wipe data and caches)

In twrp go to file manager and find cache folder inside there is file update ( -----.zip) deleted then reboot

Hello is there a way to install the new update zip file from Motorola on stock Android from Motorola; 6.0.1

Agiofws said:
Hello is there a way to install the new update zip file from Motorola on stock Android from Motorola; 6.0.1
Click to expand...
Click to collapse
Are PURE stock and are certain you have the correct OTA zip file? Then sure... Start recovery, go to the menu and select Update via ADB, then on PC use 'adb sideload update.zip'
But to be honest, I don't think people capture the update zip or url on this device, so it probably isn't feasible.

---------- Post added at 07:03 AM ---------- Previous post was at 06:57 AM ----------
[/COLOR]
acejavelin said:
Are PURE stock and are certain you have the correct OTA zip file? Then sure... Start recovery, go to the menu and select Update via ADB, then on PC use 'adb sideload update.zip'
But to be honest, I don't think people capture the update zip or url on this device, so it probably isn't feasible.
Click to expand...
Click to collapse
My phone is rooted and unlocked and has TWRP. The update zip file file was automatically downloaded by Motorolas-androids OEM. System updates which I accepted. But as I can see from custom recovery it has a message about something like a pure signature to install even when I try manually. Thank you