Related
Is there a way to sideload the 5.1 update (downloaded from the google images page) without losing the CF root AND not losing any of my system settings and configurations?
Thanks in advance.
LordGrahf said:
Is there a way to sideload the 5.1 update (downloaded from the google images page) without losing the CF root AND not losing any of my system settings and configurations?
Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
Edit after rereading this http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I would prob also do the reboot step after radio flash.
Maybe what your lookin for. If rooting is lost simply redo the cf root process and flash your custom recovery via fastboot. Most importantly this route will prevent data loss. I am going this route but will still backup because its safer and more responsible.
Without a modified img, and using the google provided stuff, you can't keep root. Just re-root, it's not hard.
Thanks guys. Few questions:
1. Do I need to unroot before sideloading the update?
2. Would I loose my currently installed and configured apps?
3. If I'm not losing my installed apps, what would happen to my root-required apps? For example I HAVE LMT pie control installed and configured. Would reinstalling root make it work as before without the need to reinstall and reconfigure LMT?
4. I'm still using stock recovery, would that affect what I'm trying to do in any way?
5. What is the minimal set of the update's images can I use to get this update? Like I think I should probably skip the user.img if I don't want my user settings to be wiped out, correct? What other images should I skip in order to not wipe out apps, apps settings, and system settings.
Thank you very much
LordGrahf said:
Thanks guys. Few questions:
1. Do I need to unroot before sideloading the update?
2. Would I loose my currently installed and configured apps?
3. If I'm not losing my installed apps, what would happen to my root-required apps? For example I HAVE LMT pie control installed and configured. Would reinstalling root make it work as before without the need to reinstall and reconfigure LMT?
4. I'm still using stock recovery, would that affect what I'm trying to do in any way?
5. What is the minimal set of the update's images can I use to get this update? Like I think I should probably skip the user.img if I don't want my user settings to be wiped out, correct? What other images should I skip in order to not wipe out apps, apps settings, and system settings.
Thank you very much
Click to expand...
Click to collapse
If doing the fastboot way like I linked (I have not read through the procedure for sideload, so I don't know)
1) no
2) no if you only flash some of the IMG files. For your purpose it seems (I'm also assuming you don't have custom kernel) these are the ones to not lose data. Make sure you follow the links in how to flash this correctly with the appropriate order and spots where to fastboot reboot.
Bootloader image
Radio image
Boot image (kernel)
Cache image
System image
Recovery image
Then reroot with the cf zip like before then reinstall the su app.
4) no we flash the new stock recovery too
5) minimal, to not overwrite the user data, above. Yup we skip the user data image
LordGrahf said:
Thanks guys. Few questions:
1. Do I need to unroot before sideloading the update?
2. Would I loose my currently installed and configured apps?
Click to expand...
Click to collapse
No.
LordGrahf said:
3. If I'm not losing my installed apps, what would happen to my root-required apps?
Click to expand...
Click to collapse
You'll have to install su since it was deleted by system.img but that's all. Note that last time I looked CF-Auto still said it was 5.0.1 but ...
LordGrahf said:
4. I'm still using stock recovery, would that affect what I'm trying to do in any way?
Click to expand...
Click to collapse
If you install a current TWRP it will install super-su for you when you request a reboot.
LordGrahf said:
5. What is the minimal set of the update's images can I use to get this update?
Click to expand...
Click to collapse
Everything except user.img. You can read or run flash-base to get the Google suggested initial ordering.
MunkinDrunky said:
http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
Edit after rereading this http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I would prob also do the reboot step after radio flash.
Maybe what your lookin for. If rooting is lost simply redo the cf root process and flash your custom recovery via fastboot. Most importantly this route will prevent data loss. I am going this route but will still backup because its safer and more responsible.
Click to expand...
Click to collapse
I flashed the bootloader, but the command to flash the radio (fastboot flash radio radio-shamu-d4.0-9625-02.95.img) failed
Any idea?
Nikos2k said:
I flashed the bootloader, but the command to flash the radio (fastboot flash radio radio-shamu-d4.0-9625-02.95.img) failed
Any idea?
Click to expand...
Click to collapse
I don't really know. I usually just follow instructions. Did you fastboot reboot after flashing bootloader?
MunkinDrunky said:
I don't really know. I usually just follow instructions. Did you fastboot reboot after flashing bootloader?
Click to expand...
Click to collapse
Yes, I rebooted the boot loader (and it indeed showed the new boot loader version after the reboot)
After the fail message of the radio flash command, I rebooted to the system, it works, and from the baseband number in settings/about, it seems that the new radio has been flashed (besides the fail message)
Nikos2k said:
Yes, I rebooted the boot loader (and it indeed showed the new boot loader version after the reboot)
After the fail message of the radio flash command, I rebooted to the system, it works, and from the baseband number in settings/about, it seems that the new radio has been flashed (besides the fail message)
Click to expand...
Click to collapse
hmm yeah i really dont know why that happend. I guess as long as the new radio shows up as you say then it worked. I will actually be doing this shortly, since i am now at a computer
Just updated to 5.1
for those who will read later and more importantly in my same position.
I was on 5.0.1 BL unlocked, custom recovery+root, custom kernel- -wanting to go to->>5.1, root+custom recovery (cause flashing kernels is trivial) without any data loss (basically don't flash the userdata image) (also you could have left out the radio, I guess if you don't want newest radio, and the boot if you want to just keep your kernel--**not 100% about these two though)
I flashed via fastboot the: bootloader (then fastboot reboot-bootloader), the radio (then fastboot reboot-bootloader), then the boot (updated stock kernel), cache, system. Done, exit command prompt, then while in fastboot menu go into TWRP, whereby I choose system reboot and TWRP RE-ROOTS for me! Now I just kernel shop again
Thanks a lot gents. I followed the directions and upgraded/rerouted and none of my apps/settings got wiped. Yay!!
Can someone verify I'm on the latest versions for all components from my screenshot?
Thanks!
I also updated my Nexus 6 with 5.0.1, unlock and root, to 5.1 without losing data. I just had to re-root it afterwards.
I used Wugfresh Nexus root toolkit.
In short I used "Flash stock + unroot", in which I selected "Enable no-wipe" and "force-flash".
After this I rerooted the device from within NRT.
Worked like a charm!
---------- Post added at 03:23 PM ---------- Previous post was at 03:13 PM ----------
LordGrahf said:
Thanks a lot gents. I followed the directions and upgraded/rerouted and none of my apps/settings got wiped. Yay!!
Can someone verify I'm on the latest versions for all components from my screenshot?
Thanks!
Click to expand...
Click to collapse
That's all the latest versions yes...
Hey guys
So I just bought a new Z3C and I'm planning on rooting it and installing CM12.1 on it. But before that I wanna make sure I perfectly understood the entire process. So if anyone could help by answering/confirming some of the things below, I would really appreciate that.
First, Sony devices don't come with a default recovery? Did I get that part right? That's why I need to flash a custom one, right? I suppose this is also the reason why I need a custom recovery in order to flash CM12.1 on my phone. Since I don't know if CM can run without one.
Second of all, kingroot. Ok, so this is an app for PC or phone that will root your phone in one click. Still without needing to unlock the bootloader (thus compromising that TA partition), right? It's in Chinese but I guess I don't need to know Chinese to click the only button on the screen. ) So that won't be a problem.
Third, I need root access for the backup part, right? So after running kingroot, I need to make a backup of my DRM stuff, right? It won't be of any use in CM, I suppose. So I just keep it somewhere safe.
Another thing, since I don't already have a custom recovery, I need the "installer" version of that xzdrecovery recovery, right? Cause there is also a flashable zip version of it, and I was wondering how the hell do I install that with no default recovery.
Can CM12 run on a locked bootloader? Probably stupid question. But this forum seems to pack some really interesting tricks I never thought were possible. So...I'm asking.
One thing I didn't quite understand: why do I need to flash part of CM12.1 to have a working recovery? Is the recovery not usable after installing it? Does it need a "simulated" ROM in order to be accessible/visible? I mean, on my SGS4, I just had to have a custom recovery (in my case it was CWM, but I'm not sure there is such a thing for the Z3C) and then just boot into it and flash CyanogenMod ROM or any other custom ROM for that matter. I didn't have to "split" the installation. First the boot.img, and then the rest (which will basically rewrite the boot.img anyway). So this part is still a bit confusing to me. Can anyone explain?
Thank you very much.
arsradu said:
First, Sony devices don't come with a default recovery? Did I get that part right? That's why I need to flash a custom one, right? I suppose this is also the reason why I need a custom recovery in order to flash CM12.1 on my phone. Since I don't know if CM can run without one.
Click to expand...
Click to collapse
As far as I know there really isn't a default recovery for Sony devices so to install CM you will need a recovery.
arsradu said:
Second of all, kingroot. Ok, so this is an app for PC or phone that will root your phone in one click. Still without needing to unlock the bootloader (thus compromising that TA partition), right? It's in Chinese but I guess I don't need to know Chinese to click the only button on the screen. ) So that won't be a problem.
Click to expand...
Click to collapse
I do not recommend kingroot but you can try it if you trust it. I used the xda guide on doing it and it worked fine for me: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343 (takes some time but its worth it if you ever want to go back to factory). As long as the bootloader stays locked the TA partition wont be touched thats right but once you unlock it you will lose all DRM keys and they wont restore if you flash a factory frimware again.
arsradu said:
Third, I need root access for the backup part, right? So after running kingroot, I need to make a backup of my DRM stuff, right? It won't be of any use in CM, I suppose. So I just keep it somewhere safe.
Click to expand...
Click to collapse
Yes you need root to backup the TA parition and yes only Sony roms use the DRM keys, CM doesn't touch them.
arsradu said:
Another thing, since I don't already have a custom recovery, I need the "installer" version of that xzdrecovery recovery, right? Cause there is also a flashable zip version of it, and I was wondering how the hell do I install that with no default recovery.
Click to expand...
Click to collapse
You install it over fastboot pretty much or with locked bootloader you use the Sony flash tool. More here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Also keep in mind that custom Kernels like "M5 Kernel" come with a pre-installed recovery.
arsradu said:
Can CM12 run on a locked bootloader? Probably stupid question. But this forum seems to pack some really interesting tricks I never thought were possible. So...I'm asking.
Click to expand...
Click to collapse
Im pretty sure its not possible. For not sony kernels you need a unlocked bootloader, otherwise it wont even boot up.
arsradu said:
One thing I didn't quite understand: why do I need to flash part of CM12.1 to have a working recovery? Is the recovery not usable after installing it? Does it need a "simulated" ROM in order to be accessible/visible? I mean, on my SGS4, I just had to have a custom recovery (in my case it was CWM, but I'm not sure there is such a thing for the Z3C) and then just boot into it and flash CyanogenMod ROM or any other custom ROM for that matter. I didn't have to "split" the installation. First the boot.img, and then the rest (which will basically rewrite the boot.img anyway). So this part is still a bit confusing to me. Can anyone explain?
Click to expand...
Click to collapse
Unlike Samsung... Sony devices have no recovery (maybe at a later time?) so you cant just replace the stock recovery with a custom one. You have to take out boot.img because fastboot cant flash entire zips like a recovery, so you flash the boot.img over fastboot which installs the recovery for you.
After that you execute "fastboot reboot" and spam your volume up key till you enter the recovery and from there you can install cyanogenmod and other.
MyPictures said:
As far as I know there really isn't a default recovery for Sony devices so to install CM you will need a recovery.
I do not recommend kingroot but you can try it if you trust it. I used the xda guide on doing it and it worked fine for me: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343 (takes some time but its worth it if you ever want to go back to factory). As long as the bootloader stays locked the TA partition wont be touched thats right but once you unlock it you will lose all DRM keys and they wont restore if you flash a factory frimware again.
Yes you need root to backup the TA parition and yes only Sony roms use the DRM keys, CM doesn't touch them.
You install it over fastboot pretty much or with locked bootloader you use the Sony flash tool. More here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Also keep in mind that custom Kernels like "M5 Kernel" come with a pre-installed recovery.
Im pretty sure its not possible. For not sony kernels you need a unlocked bootloader, otherwise it wont even boot up.
Unlike Samsung... Sony devices have no recovery (maybe at a later time?) so you cant just replace the stock recovery with a custom one. You have to take out boot.img because fastboot cant flash entire zips like a recovery, so you flash the boot.img over fastboot which installs the recovery for you.
After that you execute "fastboot reboot" and spam your volume up key till you enter the recovery and from there you can install cyanogenmod and other.
Click to expand...
Click to collapse
Alright. Thank you a lot for your answers.
So, to sum up:
First, I need to root my device. You said you would not recommend Kingroot. Ok. But I'm on stock Lollipop right now. And for as far as I understood, in order to get root on it without using Kingroot method, I need to downgrade to KitKat using FlashTool. Did I get it right?
Second, I need to backup my TA partition stuff.
Third, I need to flash the boot.img from CM12.1 flashable zip and then the recovery (flashable zip version of it, right?). In this order. Am I right?
And for the recovery part, I think I'm gonna go with that FlashTool (since I already got it for downgrading to KitKat) or via fastboot (command line), for which I need the Android SDK installed, I suppose?
Forth, unlock the bootloader. I guess I'm gonna have to Google that part. I saw some videos explaining how to do that, so I guess I'm gonna be ok.
Fifth, boot into recovery and flash CM12.1 (finally).
Please, let me know if I got the flow right or if you would make any suggestions/adjustments/corrections to it.
Also, one other thing, I heard people not being able to flash back stock and booting with it, after having a custom ROM installed, even after re-adding the content of the TA partition back and re-locking the bootloader. Any idea how to get this right from the first time, in case I need to revert to stock?
Again, big thank you for your help.
arsradu said:
Alright. Thank you a lot for your answers.
So, to sum up:
First, I need to root my device. You said you would not recommend Kingroot. Ok. But I'm on stock Lollipop right now. And for as far as I understood, in order to get root on it without using Kingroot method, I need to downgrade to KitKat using FlashTool. Did I get it right?
Second, I need to backup my TA partition stuff.
Third, I need to flash the boot.img from CM12.1 flashable zip and then the recovery (flashable zip version of it, right?). In this order. Am I right?
And for the recovery part, I think I'm gonna go with that FlashTool (since I already got it for downgrading to KitKat) or via fastboot (command line), for which I need the Android SDK installed, I suppose?
Forth, unlock the bootloader. I guess I'm gonna have to Google that part. I saw some videos explaining how to do that, so I guess I'm gonna be ok.
Fifth, boot into recovery and flash CM12.1 (finally).
Please, let me know if I got the flow right or if you would make any suggestions/adjustments/corrections to it.
Also, one other thing, I heard people not being able to flash back stock and booting with it, after having a custom ROM installed, even after re-adding the content of the TA partition back and re-locking the bootloader. Any idea how to get this right from the first time, in case I need to revert to stock?
Again, big thank you for your help.
Click to expand...
Click to collapse
- Yes you need to downgrade to a version where that root exploit isn't patched and root that way
- Yea then when you got root and all, you use that tool to backup your TA partition
- Yea after that you unlock your bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ and then you flash boot.img from CM (or a custom Kernel that implements a recovery). After flashing the boot.img you reboot into your recovery and flash the whole Cyanogenmod.zip there (Apply update). I just installed my recovery over fastboot, never actually tried the FashTool way. fastboot.exe is in the Android SDK yeah but you can also just get the small ADB installer which has it too: http://forum.xda-developers.com/showthread.php?t=2588979 (For Linux you need to install it over your package manager I think).
- No. You need to unlock the bootloader before, otherwhise it wont allow you to flash a custom boot.img
Not sure about the restoring process, I kinda don't think that I will move back from CM anyways.
However if I would go back then I would try this:
- Relock bootloader
- Factory reset
- Flash back old sony rom with root exploit over flashtool
- Gain root over that exploit and use the TA Backup tool to restore TA partition
- Install latest Sony ROM and that should work? (Not sure)
Can you post one of those theards where they get issues with restoring? How do they do it?
MyPictures said:
- Yes you need to downgrade to a version where that root exploit isn't patched and root that way
- Yea then when you got root and all, you use that tool to backup your TA partition
- Yea after that you unlock your bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ and then you flash boot.img from CM (or a custom Kernel that implements a recovery). After flashing the boot.img you reboot into your recovery and flash the whole Cyanogenmod.zip there (Apply update). I just installed my recovery over fastboot, never actually tried the FashTool way. fastboot.exe is in the Android SDK yeah but you can also just get the small ADB installer which has it too: http://forum.xda-developers.com/showthread.php?t=2588979 (For Linux you need to install it over your package manager I think).
- No. You need to unlock the bootloader before, otherwhise it wont allow you to flash a custom boot.img
Not sure about the restoring process, I kinda don't think that I will move back from CM anyways.
However if I would go back then I would try this:
- Relock bootloader
- Factory reset
- Flash back old sony rom with root exploit over flashtool
- Gain root over that exploit and use the TA Backup tool to restore TA partition
- Install latest Sony ROM and that should work? (Not sure)
Can you post one of those theards where they get issues with restoring? How do they do it?
Click to expand...
Click to collapse
It was a post in a long thread. I'm not sure I can find it right now.
Anyway, I got stuck at flashing back KitKat. FlashTool says "waiting for flashmode", whike asking me to disconnect my phone, press the back button (I got it that this is for older phones that do have a physical button), and plugging back. Which I did. The result being a very nice animation for charging. The USB debugging is ON. What am I missing here?
Sent from my D5803 using Tapatalk
arsradu said:
It was a post in a long thread. I'm not sure I can find it right now.
Anyway, I got stuck at flashing back KitKat. FlashTool says "waiting for flashmode", whike asking me to disconnect my phone, press the back button (I got it that this is for older phones that do have a physical button), and plugging back. Which I did. The result being a very nice animation for charging. The USB debugging is ON. What am I missing here?
Sent from my D5803 using Tapatalk
Click to expand...
Click to collapse
Did you install the drivers properly and on which Operating system are you flashing it?
MyPictures said:
Did you install the drivers properly and on which Operating system are you flashing it?
Click to expand...
Click to collapse
I would say yes. I mean...after googling a bit, I saw that I actually don't need to just "ignore" that message asking to press the Back button, but to actually press Volume Down instead. Which I did. And I was able to go into Flash Mode. (Flash Tool says "device connected in Flash Mode"). The device was properly recognized in MTP mode. Still, I had to manually install the Flash-tool drivers to get it recognized in flash mode, as well. Not sure why...
I mean, if the phone was properly recognized without manually installing anything (Windows downloaded and installed its own drivers), why the hell do I need to install custom drivers to get it recognized in flash mode? By the way, this "flash mode" is similar to Samsung's "Download Mode", for as far as I could see. And, just like on Samsung's devices, the access is made by pressing the Volume Down upon booting up.
Anyway, even though the device is now recognized in flash mode, I still get an error trying to flash stock 4.4.4.
I get this:
Code:
14/014/2015 21:14:34 - INFO - Please connect your device into flashmode.
14/016/2015 21:16:28 - INFO - Device disconnected
14/017/2015 21:17:03 - INFO - Device connected in flash mode
14/017/2015 21:17:03 - INFO - Opening device for R/W
14/017/2015 21:17:03 - INFO - Reading device information
14/017/2015 21:17:03 - INFO - Unable to read from phone after having opened it.
14/017/2015 21:17:03 - INFO - trying to continue anyway
14/017/2015 21:17:03 - INFO - Start Flashing
14/017/2015 21:17:03 - INFO - Processing loader.sin
14/017/2015 21:17:03 - INFO - Checking header
14/017/2015 21:17:03 - ERROR - Processing of loader.sin finished with errors.
14/017/2015 21:17:03 - INFO - Ending flash session
14/017/2015 21:17:03 - ERROR - Error in processHeader : 1 : Incorrect function.
14/017/2015 21:17:03 - ERROR - Error flashing. Aborted
14/017/2015 21:17:03 - INFO - Device connected in flash mode
And after a while, it automatically reboots in normal mode.
Windows version is Windows 10. But I'm not sure that's the problem here since, as I said, the device does get recognized both in MTP and flash modes. Also, for as far as I could see, other people are having the same issues on other versions of Windows.
Hmm not exactly sure but for Windows 8 and 8.1 (also Vista 64 bit and 7 64 Bit) You sometimes need to disable enforced driver signature.
Are you running the correct executable for your OS?:
FlashTool64.exe for 64 Bit OS and
FlashTool.exe for 32 Bit OS.
Is the device properly recognized in your device manager. Maybe re-downloading the frimware might help.
MyPictures said:
Hmm not exactly sure but for Windows 8 and 8.1 (also Vista 64 bit and 7 64 Bit) You sometimes need to disable enforced driver signature.
Are you running the correct executable for your OS?:
FlashTool64.exe for 64 Bit OS and
FlashTool.exe for 32 Bit OS.
Is the device properly recognized in your device manager. Maybe re-downloading the frimware might help.
Click to expand...
Click to collapse
Yes, I'm running FlashTool64.exe since I'm running a 64-bit version of Windows.
The device is correctly recognized in flash mode (after manually selecting the driver installed with flash-tool). See the attached image for more info.
But indeed maybe I got the wrong firmware. Problem is that I'm not really sure which one should I choose.
I got one called D5803_23.0.1.A.5.77_Customized_FR.ftf. I don't mind it that it's in French. All of them have English anyway.
Also, I saw one for UK here called D5803_23.0.A.2.105_UK.ftf. Seems to be different.... I will try with that as well.
Update: same error with that UK firmware, as well.
Update2: Well I'm half way there. Got 4.4.4 installed and got it rooted. YAY. Still trying to figure out why adb is not correctly running when trying to backup TA.
Update3: ok, backup done too!
Update4: the boot.img that comes with CM12.1 doesn't seem to have a recovery.... Or if it does, I couldn't boot in it so I can flash CM12.1.
I tried the one from Doomlord (Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img) and that seems to be based on CWM v6.0.4.7.
Problem with that is that, even though I can boot into recovery, I can't flash CM12.1. It says error status 7. Any idea why or how to fix this?
I belive error 7 indicates a outdated recovery (CM 12.1 needs a up to date one).
MyPictures said:
I belive error 7 indicates a outdated recovery (CM 12.1 needs a up to date one).
Click to expand...
Click to collapse
Might be. The problem is the device is not correctly recognized upon flashing (it says the device is "Aries" but the ROM is for D5803, D5833, z3c LOL), due to the check made within the updater-script (first line). For as far as I could see, this is a known issue... Not sure why it hasn't been fixed by now.
Anyway, removing that line will get the ROM installed successfully (at least with THAT recovery).
So I'm on CM12.1 , been for a few days now (thank you for your help), and I was wondering if there are any "permanent" recoveries (compatible with CM12.1, of course) that I can flash, something that can give me the ability to boot into recovery (and not Cyanogen Recovery, since that one sucks) and do things like nandroid backup (I know TWRP and CWM can do that, but I couldn't find any permanent version of those (or maybe I just didn't dig deep enough), and I'm not sure they are compatible with CM12.1) and formatting /system. The last one is really important for a clean installation of the ROM, especially since it doesn't look like it's done by the ROM itself.
Hello,
I have Oneplus 3 A3000 running on OOS 4.0.1 (Android 7.0). I also have official OP3 twrp recovery version 3.0.3-0 installed and root was done using supersu free v2.82.. It also has dm verity prompt which comes up during boot time because it is oem unlocked.
I want to know exact procedure to go to complete stock rom + stock recovery along with links to download stock recovery and rom. I saw different versions of stock recovery for different OOS. I don't care about device data as everything is on cloud and nothing on is on device. App list also I can get from google account history. Only thing I care is not to corrupt any system partitions. I also saw few posts that go into boot loop if incorrectly unrooted. I would not want that either.
Your help is greatly appreciated. Virtual beer for you ???. I am software engineer so even though I am noob in terms of hacking my android, I can follow the instructions properly.
Thanks again.
You can flash official OOS Rom and just use TWRP, you can try using the current recovery you have. Allow it to boot after if it allows you then do not go back to TWRP, allow it to boot to its system and then normally it will just override TWRP with OOS stock recovery.
reyscott said:
You can flash official OOS Rom and just use TWRP, you can try using the current recovery you have. Allow it to boot after if it allows you then do not go back to TWRP, allow it to boot to its system and then normally it will just override TWRP with OOS stock recovery.
Click to expand...
Click to collapse
What about unroot and oem lock and dm verity? do I need to do all that before doing OOS update? I am getting OOS 4.1.6 in system update.
mit2nil said:
What about unroot and oem lock and dm verity? do I need to do all that before doing OOS update? I am getting OOS 4.1.6 in system update.
Click to expand...
Click to collapse
you sure you want to be locked again ? i doubt..
dm verity is not a big deal for me.. i allowed it.. im ok with but if you want to remove it siankatbg has a guide on how to remove it..
reyscott said:
you sure you want to be locked again ? i doubt..
dm verity is not a big deal for me.. i allowed it.. im ok with but if you want to remove it siankatbg has a guide on how to remove it..
Click to expand...
Click to collapse
I actually want to go to systemless su + magisk + xposed later on. This one didn't work well with some apps that can detect root. But before I do that I want to start fresh because things tend to go messy and i do not have a backup device right now
mit2nil said:
I actually want to go to systemless su + magisk + xposed later on. This one didn't work well with some apps that can detect root. But before I do that I want to start fresh because things tend to go messy and i do not have a backup device right now
Click to expand...
Click to collapse
flash stock oos thats it.. you may leave the bootloader unlocked. better that way..
Sorry but I am still not sure about exact process. Here are my noob queries:
1. Should I update twrp to latest version before proceding? If so which one? currently it is 3.0.3-0. I remember running into encryption issue due to unsupported twrp when I did this last time.
2. Should I use wipe option to wipe anything before I update OOS? I want to do clean install. If so, what should I be wiping out of dalvik/system/data/internal storage/cache/usb otg?
3. To update, I should copy full ota zip on internal memory -> go to recovery -> install -> select zip file -> swipe to flash. Is that correct?
4. After that if I boot into recovery -> I will keep twrp and if I let it boot, it will replace twrp with stock recovery right?
5. Let say, I let it boot n install stock recovery, will I have dm-verity during next boot?
6. Will my superSU root be gone or still be there? If it is still there should I do complete unroot before starting this process?
7. If it is not gone, is it ok to do complete unroot after stock oos + recovery is installed?
8. I saw a dm-verity patch zip which can be used to patch dm-verity in bootloader mode if I do "fastboot oem disable_dm_verity and fastboot oem enable_dm_verity". Does it suppress the issue or it resolves it gracefully?
Thanks for the patience and help in answering the queries advance.
mit2nil said:
Sorry but I am still not sure about exact process. Here are my noob queries:
1. Should I update twrp to latest version before proceding? If so which one? currently it is 3.0.3-0. I remember running into encryption issue due to unsupported twrp when I did this last time.
2. Should I use wipe option to wipe anything before I update OOS? I want to do clean install. If so, what should I be wiping out of dalvik/system/data/internal storage/cache/usb otg?
3. To update, I should copy full ota zip on internal memory -> go to recovery -> install -> select zip file -> swipe to flash. Is that correct?
4. After that if I boot into recovery -> I will keep twrp and if I let it boot, it will replace twrp with stock recovery right?
5. Let say, I let it boot n install stock recovery, will I have dm-verity during next boot?
6. Will my superSU root be gone or still be there? If it is still there should I do complete unroot before starting this process?
7. If it is not gone, is it ok to do complete unroot after stock oos + recovery is installed?
8. I saw a dm-verity patch zip which can be used to patch dm-verity in bootloader mode if I do "fastboot oem disable_dm_verity and fastboot oem enable_dm_verity". Does it suppress the issue or it resolves it gracefully?
Thanks for the patience and help in answering the queries advance.
Click to expand...
Click to collapse
1. Try the first the current TWRP that you have. If it work, then just reboot it on to the system and TWRP will be overwritten by Stock OOS recovery.
2. Wipe dalvik/system/data/cache ..
3. YES , if im not mistaken.
4. answered on question 1.
5. most probably. Try flashing a certain firmware (not sure which one would work) . This is what I did before. But cant be sure.
6. It will be gone.
7. gone.
8. You can try.
reyscott said:
1. Try the first the current TWRP that you have. If it work, then just reboot it on to the system and TWRP will be overwritten by Stock OOS recovery.
2. Wipe dalvik/system/data/cache ..
3. YES , if im not mistaken.
4. answered on question 1.
5. most probably. Try flashing a certain firmware (not sure which one would work) . This is what I did before. But cant be sure.
6. It will be gone.
7. gone.
8. You can try.
Click to expand...
Click to collapse
Thank you so much.
mit2nil said:
Thank you so much.
Click to expand...
Click to collapse
I will tell you what I do.
Flash the latest official TWRP which is 3.1.1-2
If you want a totally clean install, boot into recovery and wipe system data including internal storage, dalvik and cache.
Then without rebooting, push the ROM downloaded from the OnePlus site to the phone. Select the ROM in recovery and swipe to flash.
Otherwise you can copy the ROM to the phone, boot into recovery, wipe system, data, dalvik and cache and then in recovery, flash the ROM.
Wipe dalvik and cache and reboot into system.
Your root will be gone and along with it TWRP. You will be on stock ROM with stock recovery.
Leave the bootloader unlocked. If necessary, it can be locked at any time.
Most likely you will not get the dm verity error. If you do, simply flash the zip given in post #215 in siankatabg's thread on dm verity. It will merely remove the message as all such methods do.
Enjoy
tnsmani said:
I will tell you what I do.
Flash the latest official TWRP which is 3.1.1-2
If you want a totally clean install, boot into recovery and wipe system data including internal storage, dalvik and cache.
Then without rebooting, push the ROM downloaded from the OnePlus site to the phone. Select the ROM in recovery and swipe to flash.
Otherwise you can copy the ROM to the phone, boot into recovery, wipe system, data, dalvik and cache and then in recovery, flash the ROM.
Wipe dalvik and cache and reboot into system.
Your root will be gone and along with it TWRP. You will be on stock ROM with stock recovery.
Leave the bootloader unlocked. If necessary, it can be locked at any time.
Most likely you will not get the dm verity error. If you do, simply flash the zip given in post #215 in siankatabg's thread on dm verity. It will merely remove the message as all such methods do.
Enjoy
Click to expand...
Click to collapse
Hi sorry I was afk for couple of weeks. So I started following this procedure. Very strangely, after I did a reboot post stock OOS (1.4gb zip) flash, twrp said no os installed, you are sure you want to reboot? I wasn't sure so I just said yes. Then I also so dm-verity coming back which was not the case when I started as I had disabled it using "fastboot enable_dm_verity" command.
Now, its been more than five minutes and my phone is stuck on the boot animation forever. (red dot in middle and two while dots rotating).
I am not sure what happened. Can someone please help me ?
mit2nil said:
Hi sorry I was afk for couple of weeks. So I started following this procedure. Very strangely, after I did a reboot post stock OOS (1.4gb zip) flash, twrp said no os installed, you are sure you want to reboot? I wasn't sure so I just said yes. Then I also so dm-verity coming back which was not the case when I started as I had disabled it using "fastboot enable_dm_verity" command.
Now, its been more than five minutes and my phone is stuck on the boot animation forever. (red dot in middle and two while dots rotating).
I am not sure what happened. Can someone please help me ?
Click to expand...
Click to collapse
Never mind. It booted to setup screen after few minutes. I guess I was in too much hurry.
i just went to stock yesterday, i flash stock recovery followed by sideloading the Oxygen OS and after that relock the bootloader.. i kinda feel the battery is much better now compare to when it was rooted with OOS
danxtian said:
i just went to stock yesterday, i flash stock recovery followed by sideloading the Oxygen OS and after that relock the bootloader.. i kinda feel the battery is much better now compare to when it was rooted with OOS
Click to expand...
Click to collapse
Awesome. I am still getting safety net failure even after locking bootloader lock. Any ideas? It fails on CTS profile match. I even did factory reset. Only thing I can think of is the "dm verity" which is back for some reason even though I am on complete stock rom+recovery with no root or unlocked bootloader.
Any way to remove it from stock recovery?
mit2nil said:
Awesome. I am still getting safety net failure even after locking bootloader lock. Any ideas? It fails on CTS profile match. I even did factory reset. Only thing I can think of is the "dm verity" which is back for some reason even though I am on complete stock rom+recovery with no root or unlocked bootloader.
Any way to remove it from stock recovery?
Click to expand...
Click to collapse
There is a zip floating around XDA which I am not able to locate immediately. It may be on siankatabg's thread on dm verity. Simply flash it.
There is also another method I read about where you flash the 4.0.2 firmware, use the enable verity command on adb, boot the phone and then flash the current firmware.
Both methods are mentioned here in XDA. Search for it.
EDIT: One of them here: https://forum.xda-developers.com/showpost.php?p=72273041&postcount=215
See also the OP of the same thread for the other method.
mit2nil said:
Awesome. I am still getting safety net failure even after locking bootloader lock. Any ideas? It fails on CTS profile match. I even did factory reset. Only thing I can think of is the "dm verity" which is back for some reason even though I am on complete stock rom+recovery with no root or unlocked bootloader.
Any way to remove it from stock recovery?
Click to expand...
Click to collapse
i remember having the dm verity but i forgot what i did to make it disappear.. after that time ive been running OOS rooted with twrp until i decided to go back to stock locked
So, I stopped doing anything as I got busy with my life. Here comes the 4.1.7 OTA and my DM verity was gone. So, it seems like if you go to stock and if still dm verity exists, try to do ota update or go to one ota back for flashing.
I am on stock rom, rooted with magisk, and I cannot seem to get this phone decrypted. Every time I try to format data in twrp, I get an error, and I get stuck in a bootloop to recovery. Is there a step(s) I am missing here? I've tried looking through the forum but all I've seen are the same instructions on formatting data.
Use Advanced Wipe, select all except sdcard. Then flash any custom rom you like. Flash Magisk too. Reboot. After reboot try running your custom rom os for a few. Then go back to twrp, do it again advanced wipe except sdcard. Reboot. See if it decrypt now.
Note: Make sure you backup everything in it first before doing so. Goodluck
Sent from my XT1805 using Tapatalk
jdesignz said:
Use Advanced Wipe, select all except sdcard. Then flash any custom rom you like. Flash Magisk too. Reboot. After reboot try running your custom rom os for a few. Then go back to twrp, do it again advanced wipe except sdcard. Reboot. See if it decrypt now.
Note: Make sure you backup everything in it first before doing so. Goodluck
Sent from my XT1805 using Tapatalk
Click to expand...
Click to collapse
Well, I tried it, it booted, but it doesnt detect my sim card, and I have no service. I am still not decrypted as well, I am afraid to format data because of the fact that in the past it has put me into a recovery bootloop.
L4ndon said:
Well, I tried it, it booted, but it doesnt detect my sim card, and I have no service. I am still not decrypted as well, I am afraid to format data because of the fact that in the past it has put me into a recovery bootloop.
Click to expand...
Click to collapse
UPDATE:
I tried to redo the process again, just to verify the process, and I am still having the same network issues. I have 3g every once in a while, but its iffy and I no longer have LTE.
L4ndon said:
Well, I tried it, it booted, but it doesnt detect my sim card, and I have no service. I am still not decrypted as well, I am afraid to format data because of the fact that in the past it has put me into a recovery bootloop.
Click to expand...
Click to collapse
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Phazmos said:
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Click to expand...
Click to collapse
IT WORKED! Thank you so much. This was the post I needed, it really helps when everything is put in a step by step format, I am not the best when it comes to this stuff, the only reason I wanted a custom rom was to be able to use wifi tether, being on sprint makes that hard. But now that i have the first step down hopefully everything else goes this smooth. Thank you so much again!
Well, as long as you have done backup with twrp you have nothing to worry about.
Sent from my XT1805 using Tapatalk
L4ndon said:
IT WORKED! Thank you so much. This was the post I needed, it really helps when everything is put in a step by step format, I am not the best when it comes to this stuff, the only reason I wanted a custom rom was to be able to use wifi tether, being on sprint makes that hard. But now that i have the first step down hopefully everything else goes this smooth. Thank you so much again!
Click to expand...
Click to collapse
Doing things the right way always works! Trouble is finding that right way (heed my warning about bad info in these threads - there is a lot of it - as you found out). Just so happens I also know how to splain things to users, I've done it for something like 25+ years (yeah, I am old - make that experienced). Tethering - used to be ya add a build.prop entry to allow it, but that was many years ago and most of not all enable it by default now.
Anyways, enjoy the ride. It may be a little bumpy, but it's the bumps that keep ya awake!
Phazmos said:
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Click to expand...
Click to collapse
THX for that, got stuck in recovery process (loop).
I followed your instructions, but need of stock recovery.
My Path :
Backup DATA (w/o /media/)
Manually Backup Media with TWRP to Ext.SD
FORMAT /Data (use the DATA Button in TWRP), in my case it showed Errors, i ignored it and did it once again - this time it worked.
flashed Magisk
ended up in Recovery Loop - flashed stock recov. via FASTBOOT, reboot
a rainbow lightning circle turned up, said " DELETING", device rebooted by itself.
Now the Phone boots to Android, shut it down, restart with PWR BUTOON + VOL DOWN pressed to access bootloader and flash twrp again with FASTBOOT ( fastboot flash recovery nameoftheimage.img ENTER).
Now u can restore /DATA TWRP Backup and then the manually part - in my case that worked.
THX!
//EDIT
After first boot, i noticed missing write permissions for most Apps - so i decided to Reset SELinux via TWRP, worked !
te amo hice format data con r15 y al parecer se soluciono todo son lo maximo cauros
Phazmos said:
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Click to expand...
Click to collapse
still sim not showing on my device which is xt1804
Never had the problem so can't help.
EASY ROOT/UNROOT FOR S7 OR S7E ALL NOUGAT OR OREO STOCK ROMS
THANKS @klabit87 FOR OREO ROOT
TEMPORARY TWRP RECOVERY VIA ADB THANKS TO @afaneh92
This is for AT&T, T-Mobile and Verizon and Sprint running V4 bootloaders only!
This tool will allow you too easily root any stock rom allowing you to make any modifications you might want then easily unroot for better performance
This will Also give you a fully functional TWRP recovery that can be accessed via adb. TWRP is fully functional on OREO Roms but is limited on Nougat roms
The initial setup does require a data wipe.
S7 G935T Edge Odin Factory FIrmware Downloads
G935TUVU4CRI2_8.0_4File_USA (T-Mobile).rar
ADB_Root Temporary Twrp Tool Download
S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z
S7 G935 Edge Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G935_EDGE_OREO.7z
SM_G935_EDGE_NOUGAT.7z
S7 G930 Flat Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G930_FLAT_OREO.7z
SM_G930_FLAT_NOUGAT.7z
Instructions
1. Download S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z and your model and version you want from above
2. Unzip S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z to S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
3. Unzip the Model/Version file you downloaded and copy the files to the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and place them in the Odin folder
4. Prepare your phone for a data wipe
5. Reboot your phone to download mode and flash the AP_ROOT_G93*.tar in the Odin AP slot and reboot your phone to recovery
6. Once phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
7. Now in the cmd window make sure your device is connected and choose Option (1) Launch TWRP
8. Your phone should launch TWRP leave phone plugged in and command window open on computer
9. Now In Twrp choose wipe and choose format data. Type yes in the box when it ask
10. Now in cmd window choose Option(8) Push Root.zip to Phone
11. Now in TWRP choose install and select the Root.zip
12. After zip is installed reboot and go through setup.
13. Once through setup make sure you are rooted
To Unroot Your Phone
1. In the Root Control app choose phone settings and unroot phone make sure phone is connected to computer
2. Now depending on the type of root you choose your phone will reboot to download if you chose system root or stock recovery if you chose systemless root. If your phone reboots to download mode skip to number 5
3. If your phone reboots to recovery once your phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
4. In cmd window choose Option(3) Unroot phone will reboot too download mode
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar
To Reroot Your Phone
1. Reboot to download in Odin AP slot flash AP_ROOT_G93***.tar
2. Phone will reboot then will reboot one more time and you will be rerooted
To Enter TWRP When Rooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Manually reboot phone to recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP
2. To Exit TWRP simply choose reboot
To Enter TWRP When Unrooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Put phone in download mode In Odin AP slot flash AP_ROOT_G93***.tar force phone to reboot to recovery. If you let phone boot it will reroot and you will have to run the unroot from the root control app.
2. In recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP.
3. Do whatever you need too do
4. To exit Twrp choose reboot to Download
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Thank you sir. Amazing is you, works great much better than safestrap and much easier to get into and out of. I hope one day im able to return the favor and help you out with something to make your life easier as you have done with countless people, much appreciated
Thank you so much for all the work you have done here and for injecting this phone with a much needed revitalization.
Now for the first dumb question, what can be flashed? ROMs? Custom Kernel? (Nethunter?) Any idea would ve helpful. Thanks again!
how to know that which version v4 or v8 on are we?
Rehan Ul Hsaan said:
how to know that which version v4 or v8 on are we?
Click to expand...
Click to collapse
The bootloader version is the 5th to last number in the build version
G935XXXX4XXXX
Sent using some kind of device I modified
gdfdedh8d said:
Thank you so much for all the work you have done here and for injecting this phone with a much needed revitalization.
Now for the first dumb question, what can be flashed? ROMs? Custom Kernel? (Nethunter?) Any idea would ve helpful. Thanks again!
Click to expand...
Click to collapse
No custom boot.img can be flashed
Sent using some kind of device I modified
jrkruse said:
The bootloader version is the 5th to last number in the build version
G935XXXX4XXXX
Sent using some kind of device I modified
Click to expand...
Click to collapse
i thinks i updated to "G935TUVS8CRJ1" can i be flash on it?
Quick question. I just used this method to root my phone (v4 bootloader, CRI2 firmware if I'm reading it right). I had been looking at the post [Rom][ALL+CARRIERS_CRF1][Stock_Oreo_Hybrid][Safestrap_Preinstalled]. That one seemed like a good deal because of the followup post on Safestrap flashable zips, like Xposed framework, Extreme Debloater, Dual Speaker, etc....
I didn't consider that ROM because of the big warning Must Be On Stock CRF1, whereas I'm on CRI2 and this looked nicer anyway.
So, just to be sure I understand, now that I've used this method to root my phone I can install all those things and more by using this technique to get into TWRP on my phone. Correct? Further, I can use TWRP in this way to flash anything except a custom bootloader. Yes?
More specifically, all those ROMs listed over in the general Tools Samsung Galaxy S7 Edge ROMs, Kernels, Recoveries, & Other Development forum that say "for G9350 only", I can use this TWRP to flash those on my G935T ?? Is that right?
Rehan Ul Hsaan said:
i thinks i updated to "G935TUVS8CRJ1" can i be flash on it?
Click to expand...
Click to collapse
Nope that's v8
jrkruse said:
Nope that's v8
Click to expand...
Click to collapse
My bad luck ?
Rehan Ul Hsaan said:
My bad luck
Click to expand...
Click to collapse
Should have been aware of what you are flashing a bootloader update is always an attempt to patch something. Usually root related. It is never to benefit the user. The first indication to me would have been a 4 version jump in bootloader versions all in one shot. I warned people all along that a bootloader change would come one of these days and kill root. Sprint seen it months ago. Tmobile and Sprint can now have there cozy little relationship with one another. I feel bad for you tmobile people. Remember when tmobile was the friendly carrier in the dev community along with sprint as well now they are the most unfriendly carrier in the dev community.
SailorJoe6 said:
Quick question. I just used this method to root my phone (v4 bootloader, CRI2 firmware if I'm reading it right). I had been looking at the post [Rom][ALL+CARRIERS_CRF1][Stock_Oreo_Hybrid][Safestrap_Preinstalled]. That one seemed like a good deal because of the followup post on Safestrap flashable zips, like Xposed framework, Extreme Debloater, Dual Speaker, etc....
I didn't consider that ROM because of the big warning Must Be On Stock CRF1, whereas I'm on CRI2 and this looked nicer anyway.
So, just to be sure I understand, now that I've used this method to root my phone I can install all those things and more by using this technique to get into TWRP on my phone. Correct? Further, I can use TWRP in this way to flash anything except a custom bootloader. Yes?
More specifically, all those ROMs listed over in the general Tools Samsung Galaxy S7 Edge ROMs, Kernels, Recoveries, & Other Development forum that say "for G9350 only", I can use this TWRP to flash those on my G935T ?? Is that right?
Click to expand...
Click to collapse
Twrp gives you no more options than you had before. You cannot just magically go flashing anything you want just because you have twrp. You can run a stock rom and mod it a little and that is it
How do you know what bootloader you're running?
i can not install this metod .
i have problem with sw. rev check faiL device, can any dody help me & please
i use OS G935TUVS8CRJ1
Does this require the fixes for lag/battery life?
jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
im exactly onthis s7 verizon heroltevzw sm g930v latest firmware oreo8.0
v8 bootloader locked:laugh:
can i downgrade and follow your path,s?
if no f9vk it
then time to move on upgrade, please can you recomend me some decent device better/much better than s7 that i can root without bricked it down to paperweight?
thankyou
much appreciated
cheers
omgaruda said:
can i downgrade and follow your path,s?
if no f9vk it
then time to move on upgrade, please can you recomend me some decent device better/much better than s7 that i can root without bricked it down to paperweight?
Click to expand...
Click to collapse
No, if your build number indicates that you're on the v8 bootloader, you're screwed for now. If you like the S7's features, you can grab an Exynos. Those you can root and modify to your heart's content. Plenty of custom ROMs available. It's not too expensive either. It's what I'm going to upgrade to, since I'm tired of this bull with the bootloader, and my glass is cracked anyway. Would probably cost nearly as much to repair as to just buy an Exynos.
S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z this is a trojan
Ihavetodothis said:
S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z this is a trojan
Click to expand...
Click to collapse
That's a false positive by a single antivirus program. VirusTotal gives it clean on 54 out of 56 antivirus programs, and one of those is merely "suspicious," probably because it's a rooting tool.