I'm downloading BLU_R0011UU_V17_GENERIC_6.0_20161115-1444, rootable? - BLU R1 HD Questions & Answers

My phone was pushed this update yesterday, it's currently rooted, after the update will I be able to root it again, will the bootloader remain unlocked?

richardred15 said:
My phone was pushed this update yesterday, it's currently rooted, after the update will I be able to root it again, will the bootloader remain unlocked?
Click to expand...
Click to collapse
if boot loader is unlocked before, will be able to keep unlocked. but the update puts into boot loop, need to do oem unlock again.
and as far as root, i am not certain, I haven't done the update my self but I have read at least two posts that report root seems to be not working. There is a safe updated rom made already of v17 and reports are root is working normal in it.
moddified v17 "safe"
http://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532

That was the same question re root on v17 I'm trying to get confirmed.
Sent from my iPhone using Tapatalk

I'm having issues rooting even the custom rom provided in link. seems to be having issues with writing to system. so stuff isn't sticking after reboots. flashing superuser gets bootloops. I know nothing of this type of phone though maybe others will chime in that know what they are doing. magisk installs but phhsuperuser wont activate or even display a icon. cannot activat magisk built in busybox after reboots
all this stuff work no problem on the older bases

vampire's 7.42 worked fine for me root and with xposed etc but I'm not going to v17 for now
Sent from my iPhone using Tapatalk

I installed Vamps V17 stock and have root.
This is what I did. (I didnt have root when I updated, I had just restored a mildly debloated V12)
1. Move rom to ext SDcard and modified settings
2. Move supersu to SDcard thanks to @Chainfire (download attached)
3. Wipe system/dalvik/cache (do not wipe data or internal)
4. Flash stock V17 modified by Vamp
5. Right after you flash the stock... flash the modified settings zip.
6. reboot and let it sync (data is all there)
7. Go to settings and make sure you still have usb debugging and oem unlock ticked.
8. Reboot to recovery and flash supersu attached below. (when you reboot phone may reboot 2 or 3 times)
9. You're rooted and updated.
:good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good:

This is my exact process, was going to write it up, but you beat me to it. Nice.

Thanks
Sent from my iPhone using Tapatalk

no problemo! :good:

richardred15 said:
My phone was pushed this update yesterday, it's currently rooted, after the update will I be able to root it again, will the bootloader remain unlocked?
Click to expand...
Click to collapse
This update correct?

Related

Systemless root (Android 6.0) - Method for easy future OTA updates

I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
yosmokinman said:
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
Click to expand...
Click to collapse
That is true, kind of just wondering/gathering information. It just seemed like with the new root method, OTA would be possible and less risky than before.
Sent from my MotoG3 using Tapatalk
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Srandista said:
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Click to expand...
Click to collapse
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
quakeaz said:
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Sounds good!
Sent from my MotoG3 using Tapatalk
quakeaz said:
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Click to expand...
Click to collapse
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Thanks for the info. So I take it while using systemless root, installing ota without unrooting is a big nono? The January ota just downloaded and is asking me to install, should I do it manually?
Chainfire said:
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Click to expand...
Click to collapse
Thank you for this thread and the procedure. I tried myself to avoid as much as possible to use a computer for super easy OTA update. But there is always one obligatory step: to root the phone.
Phone systemless rooted (2.66) - TWRP installed - OTA arrives.
In SuperSu app : Fully unroot
Install OTA - success
Fastboot boot (or install) TWRP
Flash superSu 2.66.zip
And that's it!
My question is the following: Does it exist a possibility to load on step 3. something that could flash superSu.zip from within the phone, no computer required?
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Judim said:
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Click to expand...
Click to collapse
Yes, this is one of the use-cases of FlashFire. I just haven't finished updating it to 6.0 yet.
Oh nice!
I didn't know it cause I never had the chance to try out FlashFire.
Thanks so much for everything you do for the Android community!
Cheers!
Srandista said:
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Click to expand...
Click to collapse
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
ShanxRoux said:
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
Click to expand...
Click to collapse
Did you modify system?
Try flashing system, boot, and recovery.
Then try again.
Hi, I have a Oneplus One and today has been released an OTA, so I tried the method. I have COS13 JK (latest full rom) firmware, with systemless 2.84beta supersu and twrp.
The only apps that have root access are AdAway and Greenify (without mods to system apps). No Busybox installed.
I reverted via fastboot to original JK boot.img and recovery.img, and restored, via Adaway, the original hosts file, then I applied the OTA via stock Cyano Recovery, but update failed ("system partition has unexpected contents" error).
Why?
Thanks.
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
caldent said:
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
Click to expand...
Click to collapse
I tried: no way to install OTA, I had to wait for the full rom, and dirty flashed it via TWRP without a problem.
Then I rerooted.
Bye!
ok i seem to be getting the run around on where i need to be to ask my question(s)
i am very interested in systemless root....
that being said i am clueless and all info i am findingis just super confusing me.
if someone could humor a noob to systemless rooting that would be greatly appreciated!!
i recently bought 2 new phone for my household, both are the lg tribute hd (also called lg x style)
one click root and pc method of kingoroot etc dont work... i cant locate a twrp or a cwm for this model easily by searching so i am assuming there isnt one (maybe someone could located or help to build one?)- or maybe im not tech smart enough and i can use any?(i dont think so)
model is lg ls675,android 6.0.1, kernel version 3.10.49, build # MXB48T, software is ls676zv3
main reason at the moment for trying to get root is to remove bloatware and to be able to wifi tether without limitations buy the provider, on ther phone that i have obtained root on i used an app called WIFI Tether Router which works beautifully but requires root...
please help as this is how we use our computer with internet and its beneficial all the way around especially to get rid of bloatware and keep device running smoothly...
thanks again for any help. greatly appreciated.
if im not in the right thread please kindly direct me to the correct one. thanks

Root with Marshmallow 6.0.1?

I just bought my nexus 6 and only have a pc to use for one day and wanted to know the best, safe way to root this phone. It's a Google play edition.
nellycruzz said:
I just bought my nexus 6 and only have a pc to use for one day and wanted to know the best, safe way to root this phone. It's a Google play edition.
Click to expand...
Click to collapse
Realy dude? Tons of threads of how to root with 6.0.1.
Anyway here are the basics:
- Enable oem unlocking and usb debugging in developer options
- Unlock the bootloader: Boot into fastboot and in cmd type: fastboot oem unlock (will wipe your phone so backup first!), reboot
- Flash or boot into TWRP, do NOT modify system if TWRP asks you to.
- Flash the latest systemless superSU.2.67 root zip from here http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344, TWRP will ask you to root, ignore that!
- Reboot and install BusyBox from Play
- Done.
Don't i have to install the files for the computer and all that for the drivers and download such stuff?
nellycruzz said:
Don't i have to install the files for the computer and all that for the drivers and download such stuff?
Click to expand...
Click to collapse
Yes, you have to install the sdk platform-tools in order to do this. Look here for a fast and easy way http://forum.xda-developers.com/showthread.php?t=2588979.
What happens if I mistakenly let TWRP root the phone after I have already installed the supersu zip?
android94301 said:
What happens if I mistakenly let TWRP root the phone after I have already installed the supersu zip?
Click to expand...
Click to collapse
You can unroot from within the superSU app or flash the UPDATE-unSU.zip in recovery and reroot. Next version of TWRP will probably be compatible with systemless root.
gee2012 said:
You can unroot from within the superSU app or flash the UPDATE-unSU.zip in recovery and reroot. Next version of TWRP will probably be compatible with systemless root.
Click to expand...
Click to collapse
Do I need to do this even if everything is working fine?
android94301 said:
Do I need to do this even if everything is working fine?
Click to expand...
Click to collapse
Leave it as it is if you have no issues, but both methods used at the same time on the same phone can cause problems with root and permissions.
gee2012 said:
Leave it as it is if you have no issues, but both methods used at the same time on the same phone can cause problems with root and permissions.
Click to expand...
Click to collapse
Thanks a lot...seems fine for now, will follow your recommendations if I have issues.

[GUIDE] Marshmallow Root Guide for ZE500KL

ATTENTION!
You MUST read all the guide BEFORE doing it, if you do it without reading all of it first you may ends up bricking your phone!
Prerequisites:
Asus ZE500KL (may work on ZE500KG, but haven't tested, do it on your own risk) on Marshmallow, NOT LOLLIPOP!
Also, it must have fully booted AT LEAST one time, otherwise, you'll soft-brick it.
If your phone is not on Marshmallow, you can use THIS guide instead​Download and put the unlocker zip file and the SuperSu zip file in the phone
How To:
1 - Install adb and fastboot driver (follow THIS guide)
Now you can connect the phone to your computer​2 - Reboot in fastboot mode with one of the following method:
a -Volume Up while booting up​b -With adb, after enabling USB debugging in developer settings, using:
Code:
adb reboot bootloader
Now that you are in bootloader, you have to boot in TWRP,
download THIS recovery (is the twrp one) and boot in to it, using this command:
IMPORTANT: DON'T FLASH IT OR YOU WILL GET BOOTLOOP!!!
Code:
fastboot boot TWRP-x-x-x-x.img
(Obviusly the recovery name must be the one you downloaded)
IMPORTANT: DON'T FLASH IT OR YOU WILL GET BOOTLOOP!!!
It should automaticaly enter in recovery.
Now you MUST flash FIRST ZE500KL_BootloaderUnlock.zip, otherwise you'll brick your phone
Btw, the recovery will mount your phone's memory, so you can put now the files in the phone, if you forgot to do it before​
AFTER you installed the unlocker zip, you can install the SuperSu zip
When the install is complete, clear the cache and reboot your phone, now you can enjoy your root!
Downloads:
Latest @MiauLightouch TWRP - 3.0.0.2 Mirror
Latest SuperSu zip - 2.65 Mirror
Bootloader Unlocker (from @MiauLightouch original post) - Mirror
Credits:
@MiauLightouch for pretty much everything
@LuK1337 , @luca020400 and everyone on #titandev for being awesome
So.. I'm thinking of buying a ZE500KL and I've been doing some reading on this phone on the forums.. did it really just get unlocked like yesterday? does that mean custom roms from now on?
MuzgontarAco said:
So.. I'm thinking of buying a ZE500KL and I've been doing some reading on this phone on the forums.. did it really just get unlocked like yesterday? does that mean custom roms from now on?
Click to expand...
Click to collapse
I would recommend Z00L/T, you will get cm13, official unlock at least.
You Say " May Work On ZE500KG" Is ze500kg already receive Marshmallow Update?
MiauLightouch said:
I would recommend Z00L/T, you will get cm13, official unlock at least.
Click to expand...
Click to collapse
thanks for the advice but my choices are poor with about 5 phones in this price range with this one looking waay better.. getting it via contract so yeah..
How to install supersu zip? Tia.
Working! Have you tried to flash Viper4Android? On lollipop this will break Call recording and FM Radio, maybe this will not be a problem on MM?
Seanjhon027 said:
How to install supersu zip? Tia.
Click to expand...
Click to collapse
Inside TWRP there is a big "Install" button, press it and select the zip
what is the meaning of booted
mohamedelkholy said:
what is the meaning of booted
Click to expand...
Click to collapse
context?
until you saw the lock screen, that's what "booted".
stuck waiting for device
C:\Users\Clynt\Desktop\Android M>adb reboot bootloader
C:\Users\Clynt\Desktop\Android M>fastboot boot twrp.img
< waiting for device >
Ok I don't know where I get wrong but I got this error.
Img file name is ok because I renamed it.
Drivers were installed already.
Developers mode is enabled already.
Windows 7 64bit
Tried rooting this using lollipop and everything went well.
thanks!
UPDATE: i got it. it has something to do with the drivers.
Without opening the bootloader.
Notice. I have not tried it.
http://www.asus-zenfone.com/2016/05/how-to-root-asus-zenfone-2-laser-ze50kl-marshmallow.html?m=1
thanl you man i have rooted my zenfone 2 laser
Thanks very much for this guide and your work.
Can I install the new update v13.10.7.1 when I opened bootloader.
The twrp recovery is temporary or permanent? If permanent how to go back to stock recovery? Tia
thanks
thks TS
now my phone its rooted
Muminek111 said:
Without opening the bootloader.
Notice. I have not tried it.
No... when trace a perequisite link Given..
you really need to unlock bootloader first
wulfe13 said:
The twrp recovery is temporary or permanent? If permanent how to go back to stock recovery? Tia
Click to expand...
Click to collapse
i think isnt permanent, this step is needed to boot into twrp then flashing a unlockBL..
to make permanent.. the command must "fastboot flash recovery twrp_X.X.X.X.img"
but make sure to unlock bootloader first...
CMIIW
Click to expand...
Click to collapse
Is it me or everytime I reboot the device after rooted, it's going back to unrooted?
Root is a success tho, great job, OP!
Edit: okay, not every reboot, but after several reboots, then it went back unrooted

Stock Owens XT1775, just got notice update is ready to install - root first or after?

Sorry if this seems like a dumb question - I'm a little green on the phone modding (last phone was a S3, rooted with oneclickroot I think) I have a bootloader unlockable XT1775 owens (bought from retail, no carrier lock) that I have been planning to bootloader unlock and root with TWRP & Magisk. I just got a notification that update "NPR26-58-45" is available. I downloaded it, but haven't installed yet - for fear that it might affect what I want to do for root.
What should I do? ie: - install it, and go forward with the root process? Root first, and then install?
jdsmn21 said:
Sorry if this seems like a dumb question - I'm a little green on the phone modding (last phone was a S3, rooted with oneclickroot I think) I have a bootloader unlockable XT1775 owens (bought from retail, no carrier lock) that I have been planning to bootloader unlock and root with TWRP & Magisk. I just got a notification that update "NPR26-58-45" is available. I downloaded it, but haven't installed yet - for fear that it might affect what I want to do for root.
What should I do? ie: - install it, and go forward with the root process? Root first, and then install?
Click to expand...
Click to collapse
Do NOT root first!
Edit: do me a favor and upload a system backup after you update, root and install twrp (if you do anyway), so I can make a twrp flashable ROM.
Edit-2: actually, if you could backup system before rooting or anything, that would be better.
You do not want to root first. Update then root as doing an ota while rooted may loose your root status or worse!
Goose03 said:
Do NOT root first!
Edit: do me a favor and upload a system backup after you update, root and install twrp (if you do anyway), so I can make a twrp flashable ROM.
Edit-2: actually, if you could backup system before rooting or anything, that would be better.
Click to expand...
Click to collapse
Thanks Goose. I will gladly upload that, but I will have to get back to you after the weekend - I apologize, heading out of town after work.
To clarify on the process, I would go through the step to unlock the bootloader (using the code I will get from Moto website and "fastboot oem unlock CODE"). After that is the TWRP step, right? If so, which command do I use: "fastboot boot recovery.img" or "fastboot flash recovery recovery.img" ??
jdsmn21 said:
Thanks Goose. I will gladly upload that, but I will have to get back to you after the weekend - I apologize, heading out of town after work.
To clarify on the process, I would go through the step to unlock the bootloader (using the code I will get from Moto website and "fastboot oem unlock CODE"). After that is the TWRP step, right? If so, which command do I use: "fastboot boot recovery.img" or "fastboot flash recovery recovery.img" ??
Click to expand...
Click to collapse
Np. Take your time. Thanks. Yes, that is what you do to unlock. Then for flashing twrp it's like you have but make sure to match the last part "recovery.img" to whatever the recovery is named. If your recovery is named twrp.img the command is:
fastboot flash recovery twrp.img
If it helps, I posted a step-by-step guide to unlocking, installing TWRP and rooting here: https://forum.xda-developers.com/moto-e4-plus/help/step-step-how-to-root-moto-e4-plus-t3752334
koop1955 said:
If it helps, I posted a step-by-step guide to unlocking, installing TWRP and rooting here: https://forum.xda-developers.com/moto-e4-plus/help/step-step-how-to-root-moto-e4-plus-t3752334
Click to expand...
Click to collapse
That's the one I had been following! I found that very helpful - that would make a good sticky post for guys like myself.
Since I have your attention too, I'd like to ask - is dmnoverity and phh's SU not needed at all? The only three files copied to the SD card (and then installed) are TWRP, Magisk zip, and Magiskmanager APK?
jdsmn21 said:
That's the one I had been following! I found that very helpful - that would make a good sticky post for guys like myself.
Since I have your attention too, I'd like to ask - is dmnoverity and phh's SU not needed at all? The only three files copied to the SD card (and then installed) are TWRP, Magisk zip, and Magiskmanager APK?
Click to expand...
Click to collapse
Phh SU is not needed since Magisk gives you all the necessary root and features. dmnoverity is not needed. I recommend you allow twrp system write access.
koop1955 said:
If it helps, I posted a step-by-step guide to unlocking, installing TWRP and rooting here: https://forum.xda-developers.com/moto-e4-plus/help/step-step-how-to-root-moto-e4-plus-t3752334
Click to expand...
Click to collapse
Well, I followed your instructions....with a minor tweak - and I'm having problems.
I unlocked the bootloader a couple days ago, but couldn't download the TWRP.bin file, so I used my phone through today. Formatted a 64gb card and loaded the magisk zip and apk on it. Flashed the TWRP on the phone, and used the wipe function to wipe data, cache, and dalvik, and then made a backup to my sd card. Flashed the magisk.zip, and then hit reboot "system". Now it just reboots to TWRP. I can reboot to bootloader, but hitting "start" goes to TWRP again.
What do I do? Where did I go wrong?
jdsmn21 said:
Well, I followed your instructions....with a minor tweak - and I'm having problems.
I unlocked the bootloader a couple days ago, but couldn't download the TWRP.bin file, so I used my phone through today. Formatted a 64gb card and loaded the magisk zip and apk on it. Flashed the TWRP on the phone, and used the wipe function to wipe data, cache, and dalvik, and then made a backup to my sd card. Flashed the magisk.zip, and then hit reboot "system". Now it just reboots to TWRP. I can reboot to bootloader, but hitting "start" goes to TWRP again.
What do I do? Where did I go wrong?
Click to expand...
Click to collapse
Try fastboot oem fb_mode_clear
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
Try fastboot oem fb_mode_clear
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Thank you. I tried the command, and it said OK, but it still boots to TWRP; i then reboot to bootloader, and select Start and it goes into the normal system. Is that how it is supposed to work?
Last night I was stuck in a TWRP loop, but i got it to go with formatting data and factory reset wipe in TWRP. After finally getting the system to boot, I installed the Magisk Manager and then Adaway. Now today I was playing with the Chase Pay app, which won't let me sign in due to being rooted. I then reverted my hosts file and uninstalled Adaway, and played with all the hide options in Magisk., to no avail. Root Checker app says that Safetynet is tripped.
Does Magisk effectively work for apps that look at Safetynet on this phone - apps like Chase Pay?
jdsmn21 said:
Thank you. I tried the command, and it said OK, but it still boots to TWRP; i then reboot to bootloader, and select Start and it goes into the normal system. Is that how it is supposed to work?
Last night I was stuck in a TWRP loop, but i got it to go with formatting data and factory reset wipe in TWRP. After finally getting the system to boot, I installed the Magisk Manager and then Adaway. Now today I was playing with the Chase Pay app, which won't let me sign in due to being rooted. I then reverted my hosts file and uninstalled Adaway, and played with all the hide options in Magisk., to no avail. Root Checker app says that Safetynet is tripped.
Does Magisk effectively work for apps that look at Safetynet on this phone - apps like Chase Pay?
Click to expand...
Click to collapse
It is not normal to have it boot straight to twrp or the bootloader rather than the rom unless you do so manually.
Have you triedbplaying with the settings in Magisk Manager? There is an option to hide Magisk from your choice of apps. There is also a couple other options in the settings to hide things as much as possible. If you have Xposed installed it won't pass a safteynet check.
Sent from my Moto E (4) Plus using XDA Labs
XT1775 rom's is possible install on XT1776 ?
almao11 said:
XT1775 rom's is possible install on XT1776 ?
Click to expand...
Click to collapse
You could. I've flashed xt1775 firmware to my xt1776 to get a backup of the system to make a twrp flashable from. I don't recommend it, but if you only flash the system and not the modem and oem it should provision data services. Why do you ask exactly?
Sent from my Moto E (4) Plus using XDA Labs

[Easy_Root/Unroot][Any_Oreo/Nougat_Firmware_V4_Bootloaders][Tmp_Twrp_Recovery]

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 G930T Flat Odin Factory FIrmware Downloads
G930TUVU4CRI2_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
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
I had to look this up so thought I'd share This is for Tmobile Versions
Example: G930TUVS8CRJ1 (5th # from right is 8, BL version - this is found in Settings>About Phone>Software Information>Baseband Version)
Which Oreo versions are safe (ver 4):
G930TUVU4CRI2 Oct 1, 2018
G930TUVU4CRF1 June 28, 2018
Not safe (ver 8):
G930TUVS8CRJ1 Oct 26, 2018 release date
---------- Post added at 02:55 AM ---------- Previous post was at 02:49 AM ----------
BTW nice work as always Jr! Oh, & almost forgot ...your last comment saved my @zz!!! I wasn't aware of the ver 8 issue, and the fact that u can't downgrade!! DAMN Samsung!!!!! I was seriously about to try this latest update just to try & figure out RCS not working on CRF1 & randomly came across this! THANKS! (BTW if you know anything about RCS on s7 or services/apks needed for functionality on CRF1 please pm me!)
On another note, let's have a contest to see who can hold on to the S7 the longest as their primary phone
It works perfectly , I had no problem installing it. But I have a question:
Could I replace the SuperSu with the Magisk?
I am also in the Rom Project L S7 of Lanc-City: 3
FranMLG said:
It works perfectly , I had no problem installing it. But I have a question:
Could I replace the SuperSu with the Magisk?
I am also in the Rom Project L S7 of Lanc-City: 3
Click to expand...
Click to collapse
No magisk requires custom boot.img
Sent using some kind of device I modified
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
Thanks for the effort and providing root for T-Mobile. Perhaps I am an unlucky person. By the time I discovered this thread, my phone was already updated to G930TUVS8CRJ1 version. I am wondering if there is any hope for V8 bootloader to root their phone in near future. Here is my humble request if you could provide root for V8 update. TIA.
jrkruse said:
No magisk requires custom boot.img
Sent using some kind of device I modified
Click to expand...
Click to collapse
can we do full backup after setting up the phone and then restore it without any bugs and issues?
zfk110 said:
can we do full backup after setting up the phone and then restore it without any bugs and issues?
Click to expand...
Click to collapse
Do a system.img backup
Sent using some kind of device I modified
Thank you. It worked fine on my nougat s7 flat with v4 bootloader. Now I have nougat root. I have a question if I may, Can I use tmp twrp to flash Oreo or one of your, or other roms? Or would I need to upgrade the kernel or something because I can flash Oreo being that I'm on Nougat. Thanks.
boofbatch said:
Thank you. It worked fine on my nougat s7 flat with v4 bootloader. Now I have nougat root. I have a question if I may, Can I use tmp twrp to flash Oreo or one of your, or other roms? Or would I need to upgrade the kernel or something because I can flash Oreo being that I'm on Nougat. Thanks.
Click to expand...
Click to collapse
You have to update bootloaders and firmware as well so its better to update to oreo first
Sent using some kind of device I modified
working fine.
update: gonna have to switch back to u firmware because even when i unroot the phone, certain games wont work or connect to server. i cant install magisk to bypass safetynet or hide magisk after installing so root isnt even seeming worth it on this device. might as well stick to the u firmware and disable the apps I dont need and disable ota update so that i dont get the v8 bootloader update. It was fun while it lasted.
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
Man, will you update the Recovery for the new security patch (CRJ1) ?, I've run out of Root , and I can no longer go back in the version.
---------- Post added at 04:50 PM ---------- Previous post was at 04:47 PM ----------
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
That's exactly what happened to me, I did not know
FranMLG said:
Man, will you update the Recovery for the new security patch (CRJ1) ?, I've run out of Root , and I can no longer go back in the version.
---------- Post added at 04:50 PM ---------- Previous post was at 04:47 PM ----------
That's exactly what happened to me, I did not know
Click to expand...
Click to collapse
yikes sorry to hear that
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
I bought a phone which is already to g930tuvs8crj1 I tried to down grade but it wont let me, what are my options? Thanks
zfk110 said:
I bought a phone which is already to g930tuvs8crj1 I tried to down grade but it wont let me, what are my options? Thanks
Click to expand...
Click to collapse
Enjoy Stock
Sent using some kind of device I modified
jrkruse said:
Enjoy Stock
Sent using some kind of device I modified
Click to expand...
Click to collapse
After looking around for 4 days I was finally able to find G930T U8 ENG ROOT Modem.bin file, but when I'm trying to flash it using odin it wont pass file Analyzing
I hope you can look more into it. if we can flash this then we can able to root U8 bootloaders too
https://drive.google.com/open?id=1dhHeYAPsCqKQ_eFfuzPaYbgFv0y1BSLr
These guys also selling Eng boot for $60
https://support.halabtech.com/index.php?a=downloads&b=file&id=90428
zfk110 said:
After looking around for 4 days I was finally able to find G930T U8 ENG ROOT Modem.bin file, but when I'm trying to flash it using odin it wont pass file Analyzing
I hope you can look more into it. if we can flash this then we can able to root U8 bootloaders too
https://drive.google.com/open?id=1dhHeYAPsCqKQ_eFfuzPaYbgFv0y1BSLr
These guys also selling Eng boot for $60
https://support.halabtech.com/index.php?a=downloads&b=file&id=90428
Click to expand...
Click to collapse
Im just waiting on them to email me the passwords
Sent using some kind of device I modified
Alright guys i really need your help...i just bought a used samsung. galaxy s7 G930T...the problem is it doesnt get any network...thr signal says searching and theres is nl network bar...the issue is i cant tell if it is unlocked or not..because it reads my sim...it displays the right access point....shoes sim tools...but just doesn't get network..i ve tried all sim cards...i tried using the tmobile unlock tool that came with the device butbit says unlock failed reboot device repeatedly....ive tried factory reset....i love this phone and would really like to use it...Pls any suggestions or help...the software version is 8.0. baseband version is G930TUVS8CRL1
marvelv94 said:
Alright guys i really need your help...i just bought a used samsung. galaxy s7 G930T...the problem is it doesnt get any network...thr signal says searching and theres is nl network bar...the issue is i cant tell if it is unlocked or not..because it reads my sim...it displays the right access point....shoes sim tools...but just doesn't get network..i ve tried all sim cards...i tried using the tmobile unlock tool that came with the device butbit says unlock failed reboot device repeatedly....ive tried factory reset....i love this phone and would really like to use it...Pls any suggestions or help...the software version is 8.0. baseband version is G930TUVS8CRL1
Click to expand...
Click to collapse
Sounds like you bought yourself a blacklisted phone
Sent using some kind of device I modified
jrkruse said:
Sounds like you bought yourself a blacklisted phone
Sent using some kind of device I modified
Click to expand...
Click to collapse
It is not blacklisted ...i already checked...any help?

Categories

Resources