Database Develop

[HOWTO] get root back after ota update!

this is how i did it anyways. i had to flash the boot.img and update via stock recovery to get the ota to flash. but then no root!
so heres how i got it back:
download the superboot/paulobrien method (http://forum.xda-developers.com/showthread.php?t=882333).
boot phone to fastboot.
Code:
fastboot boot boot.superboot.img
let phone boot, open terminal, su, just to check.
reboot phone.
rooted and ota'd now!

I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
The method I used was:
1. Boot into fastboot.
2.
Code:
fastboot flash recovery recovery-clockwork-3.0.0.0-crespo.img
3. Reboot from fastboot directly into recovery (not doing so will cause android to replace CWR).
4. Mount USB, copy su-2.3.6.1-ef-signed.zip to the /sdcard via windows/linux
5. Mount /system
6. Install update from zip (browse to were you put su-2.3.6.1-ef-signed.zip).
7. Install it, and reboot.
8. open root explorer, and rename /etc/install-recovery.sh to install-recovery.sh.old
9. open ROM Manager, reflash CWR.
now you are all done, rooted, w/ CWR

I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).

Luxferro said:
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
Click to expand...
Click to collapse
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.

distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
im using stock recovery.

I'm rooted on 2.3.1 but I lose clockwork recovery when I reboot an gota reflash it using rom manager. Anyone having this problem

k0mpresd said:
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
Click to expand...
Click to collapse
Sure it is. But on Android bootup, a script is running somewhere to replace it with stock recovery. They did this on Droid_1 after the first or second update (that's my only other android phone... so my android experience is limited).
edit: I just found the script. It's /etc/install-recovery.sh .... just renamed my to install-recovery.sh.old. gonna reflash CWR and test it now.
edit2: yep, works great now. CWR, and retained my 2.3.1 boot.img

So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone

chris6278 said:
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
Click to expand...
Click to collapse
No, it's a safety mechanism so you can't lose recovery... It has nothing to do with clockworkmod. Someone can make a root script or app that disables it easily. Or people can just do it themselves manually.
edit: actually, all that needs to be done is add some code to the update script inside su-2.3.6.1-ef-signed.zip so when it installs the update, it renames install-recovery.sh

distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks

If u dont mind can u please provide the instructions on how to do it manually. Id really appreciate it. Sorry im a noob lol

Where in root explorer do i need to rename

Where in root explorer do i rename it

plmiller0905 said:
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
Click to expand...
Click to collapse
chmod needs to be done at a # prompt.

chris6278 said:
Where in root explorer do i rename it
Click to expand...
Click to collapse
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...

Is it just me or does adb remount no longer work?
If I use the old koush rootboot.img it works, but no wifi, if I use the stock boot.img, I get no wifi but am able to remount.

I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes

chris6278 said:
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
Click to expand...
Click to collapse
do you have root explorer? if not, it's just a file explorer that has root access. by default when you open it you are at /
you need to scroll down to /etc
go in that folder and find the install-recovery.sh
look up top for the button to turn it from read-only to read-write, click it
go back to the file long press it, and then choose rename.

Luxferro said:
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Click to expand...
Click to collapse
Thanks..I already rerooted but thanks anways

I got root explorer an followed ur directions an now everything works great. Thanx for ur help an sorry for being a pain lol

[Q] Rom Manager on Nexus s claims device is not rooted

Hi
When I start the Rom Manager I get the message "You must root your phone for ROM Manager to function. Superuser was not found as "/system/bin/su" or/system/xbin/su".
I have followed the instructions here on how to root my Nexus s and I am able to enter recovery mode and am able to go into bootloader. I also see that is says "Unlock" there.
So the way I understand it, the phone is rooted. Unless I miss something here.
I also see the Superuser icon in my launcher.
What am I doing wrong?

Think this is the wrong area to ask but when you flashed the su file did you mount system in the mount and storage before flashing the su file?

I dont think it was mentioned in the guide.
how do I do that?
Can I reapply the su zip file again?

jerrycycle said:
Think this is the wrong area to ask but when you flashed the su file did you mount system in the mount and storage before flashing the su file?
Click to expand...
Click to collapse
OK. That is what I was missing.
Now its done.
Thanks

dbenyakar said:
OK. That is what I was missing.
Now its done.
Thanks
Click to expand...
Click to collapse
What method did you use to root?

How to Install 4.2 images, keep root and all data

**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images

Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?

Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..

jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.

mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.

tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window

Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!

kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.

OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/

rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options

You have .bat file in the package.

Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.

Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions

I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?

I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app

mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.

Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app

can I install image-nakasi-jop40c.zip directly without upgrading bootloader?

Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.

Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!

unroot

Hi all,
I am unable to remove supersu and unroot my phone to send it for repair..
After using Full unroot from within SuperSU to unroot my phone then restart as directed but when the phone restarts, I still have supersu installed.
I have manually deleted the SuperSU from /data and SU from /bin and SU from /xbin but when I do a full factory wipe to remove my google account and any other details from the phone, on restart the SuperSU is back........................................
Any advice please.
Thanks all

worf105 said:
Hi all,
I am unable to remove supersu and unroot my phone to send it for repair..
After using Full unroot from within SuperSU to unroot my phone then restart as directed but when the phone restarts, I still have supersu installed.
I have manually deleted the SuperSU from /data and SU from /bin and SU from /xbin but when I do a full factory wipe to remove my googal account and any other details from the phone, on restart the SuperSU is back........................................
Any advice please.
Thanks all
Click to expand...
Click to collapse
Am loosing my hair with this

worf105 said:
Am loosing my hair with this
Click to expand...
Click to collapse
If you originally rooted by flashing superuser or supersu in custom recovery (TWRP/CWM) then superuser.apk and su binary are installed in the system partition and a factory reset will not remove them. Further, attempting to delete them using a file explorer won't work either because the system partition is write protected once the OS boots (they appear to delete, but return on reboot.)
One solution is to remove the root files in custom recovery by flashing the attached zip, it has a script that will delete /system/app/superuser.apk and /system/xbin/su files.
Another solution is to install the RUU for your phone, that will reinstall a fresh copy of the system partition without root files.

cschmitt said:
If you originally rooted by flashing superuser or supersu in custom recovery (TWRP/CWM) then superuser.apk and su binary are installed in the system partition and a factory reset will not remove them. Further, attempting to delete them using a file explorer won't work either because the system partition is write protected once the OS boots (they appear to delete, but return on reboot.)
One solution is to remove the root files in custom recovery by flashing the attached zip, it has a script that will delete /system/app/superuser.apk and /system/xbin/su files.
Another solution is to install the RUU for your phone, that will reinstall a fresh copy of the system partition without root files.
Click to expand...
Click to collapse
Thank you (only wish there is an RUU for 2.24.161.1 VODAP001 as I would really love to get back to stock) will get back to you as soon as I try your solution.
Cheers,
worf105

worf105 said:
Thank you (only wish there is an RUU for 2.24.161.1 VODAP001 as I would really love to get back to stock) will get back to you as soon as I try your solution.
Cheers,
worf105
Click to expand...
Click to collapse
It worked, it worked great, Thanks cschmitt :good::good::good::good::good:

*UNTESTED* OE2 to OI2 While Keeping Root

I pulled this from my phone when it was released yesterday. I'm in OE2 rooted, so this file is from OE2 to OI2
THIS IS NOT AN ODIN FILE!
Build is G925AUCU3BOI2
http://www.mediafire.com/?xksb71307dofox8
designgears said:
*** UNCONFIRMED *** This hasn't been tested.
This is for upgrading from G925AUCU1AOE2 to G925AUCU3BOI2 while retaining root.
Flash with FlashFire
2400258_s6_edge.zip
https://mega.nz/#!S1BnHSSJ!emk9y52XQIaVE0KFyRBwzYmXav0MByBOPtVeZwRCUmw
Flash With Odin
boot.tar.md5
https://mega.nz/#!T05xiaDR!3SVrDVONPGfRU898PSwQ52e631ubArsSNKV4mHPqMXM
modem.tar.md5
https://mega.nz/#!D8gxkA6J!riyZ69REc0DoSBO0O43Ykfa4sI9Pl5gRVSljWTqS2lc
-----------------------------------
In Flashfire select "Flash ZIP or OTA"
Select 2400258_s6_edge.zip from your sdcard
Leave all of the settings default and flash.
After it has flashed, reboot to download mode and use Odin to flash the updated kernel and modem.
In Odin put boot.tar.md5 in the AP slot.
Put modem.tar.md5 in the CP slot.
Leave all other settings alone and click start.
Once the phone has rebooted you should be on G925AUCU3BOI2.
Click to expand...
Click to collapse

how to use this..i am in stock 5.0.2

Thank you!
Downloaded this, then sideloaded it with ADB Sideload while having OE2. Worked perfectly!

Krestic said:
Thank you!
Downloaded this, then sideloaded it with ADB Sideload while having OE2. Worked perfectly!
Click to expand...
Click to collapse
Did you retain root?

Yes. I was prepared to lose it imo, but still have it so that's kind off weird. But I won't be complaining. Now I'll wait for deodoexed rom then I can go xposed with flashfire..

Krestic said:
Thank you!
Downloaded this, then sideloaded it with ADB Sideload while having OE2. Worked perfectly!
Click to expand...
Click to collapse
Can you please post pic to confirm you have root still on 5.1.1 and please provide instructions on how you sideloaded this with adb?

I unlocked my phone and i still didn't get the update yet is that a problem?

Krestic said:
Thank you!
Downloaded this, then sideloaded it with ADB Sideload while having OE2. Worked perfectly!
Click to expand...
Click to collapse
How did you do this? I get a DM-Verification error in recovery.

Please help me:
when i'm in recovery 3e and choice apply update from adb but he said Update from ADB is disabled
then i choice apply update from external storage but not ok. 'apply update from external storage is diabled'
Someone know please help me. Thank a lot!

tronghienk32 said:
Please help me:
when i'm in recovery 3e and choice apply update from adb but he said Update from ADB is disabled
then i choice apply update from external storage but not ok. 'apply update from external storage is diabled'
Someone know please help me. Thank a lot!
Click to expand...
Click to collapse
Same errors I'm getting. That's why I'm waiting for a response on how he got it to work.

teamfresno said:
Same errors I'm getting. That's why I'm waiting for a response on how he got it to work.
Click to expand...
Click to collapse
Did you sideload it from your storage or your computer? From previous phones, I know it has to be sideloaded from a computer.

Rodman101 said:
Did you sideload it from your storage or your computer? From previous phones, I know it has to be sideloaded from a computer.
Click to expand...
Click to collapse
The computer. I put the phone into recovery mode, then I scroll down to install from ADB, but I always get an "ADB is disabled". I thought you have to get into there and then ADB sideload xxxx.cfg from the command prompt.
Am I doing it wrong?

Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked.
This taken from the S4 forum

krolla03 said:
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked.
This taken from the S4 forum
Click to expand...
Click to collapse
It worked and you remained rooted?

krolla03 said:
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked.
This taken from the S4 forum
Click to expand...
Click to collapse
Like others are saying, everyone gets ADB is disabled message when they select apply update. What did you do for that?

srideep said:
Like others are saying, everyone gets ADB is disabled message when they select apply update. What did you do for that?
Click to expand...
Click to collapse
same problem!

krolla03 said:
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked.
This taken from the S4 forum
Click to expand...
Click to collapse
AT&T? Seems like you have a custom recovery. We don't have "ADB sideload", it comes up as "install from ADB".

Krestic said:
Thank you!
Downloaded this, then sideloaded it with ADB Sideload while having OE2. Worked perfectly!
Click to expand...
Click to collapse
He couldn't have been rooted because the OTA has build in checks.
Designgears created a flashfire zip that updates from OE2 to OF3 while maintaining the OE2 Recovery and Bootloader. I have been trying to mimic his form, but I haven't been able to take the .p files and work with them.
Here're the threads if anyone is knowledgeable enough to work with these things or can get a hold of him or Wesgarner who created a similar zip between OF3 and OF4
http://forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-flashfire-update-t3156221
http://forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-to-of4-flashfire-update-t3181135

Rodman101 said:
He couldn't have been rooted because the OTA has build in checks.
Designgears created a flashfire zip that updates from OE2 to OF3 while maintaining the OE2 Recovery and Bootloader. I have been trying to mimic his form, but I haven't been able to take the .p files and work with them.
Here're the threads if anyone is knowledgeable enough to work with these things or can get a hold of him or Wesgarner who created a similar zip between OF3 and OF4
http://forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-flashfire-update-t3156221
http://forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-to-of4-flashfire-update-t3181135
Click to expand...
Click to collapse
Well here is a zip like the ones you linked to. I can't test it but I tried to make as safe as possible. removed all checks so it won't fail. I don't let it patch boot.img sboot.bin, etc. Idea is that IF something does mess up you should be able to odin back to OE2. outside of that, this *should* take you from G925AUCU1AOE2 to G925AUCU3BOI2. If anyone wants to give it go: 2400258.zip

Krestic said:
Thank you!
Downloaded this, then sideloaded it with ADB Sideload while having OE2. Worked perfectly!
Click to expand...
Click to collapse
mrRobinson said:
Well here is a zip like the ones you linked to. I can't test it but I tried to make as safe as possible. removed all checks so it won't fail. I don't let it patch boot.img sboot.bin, etc. Idea is that IF something does mess up you should be able to odin back to OE2. outside of that, this *should* take you from G925AUCU1AOE2 to G925AUCU3BOI2. If anyone wants to give it go: 2400258.zip
Click to expand...
Click to collapse
ADB sideload right?