Related
[GUIDE] Root & recovery WITHOUT oem unlock & wipe (2.3.2 & older, plus now 2.3)
UPDATE #2 - Fitchman has reported successful root and rom flash without unlocking the bootloader by using Ginger Break. Full details in this post: http://forum.xda-developers.com/showpost.php?p=13236136&postcount=135
UPDATE - IMPORTANT: This method does not work with Android 2.3.3. Search the forum or this post in this thread for a way to update to 2.3.3 and root without unlocking if you haven't updated yet.
Alternatively, use this method on 2.3.2 and lower, then use titanium to back up everything, store it on your laptop (along with all your sdcard's data), then do the oem unlock step first and then continue from there with the rest of the guide.
Not my original idea, but a consolidation of a discussion between inakipaz and shrivelfig and myself in another thread and being posted here for easier finding by future root-seekers.
Shrivelfig's tested the method to re-root a previously rooted pone with a re-locked bootloader, and inakipaz has done it on a phone that's never had the bootloader unlocked.
The advantage here is that those who chose not to root when they first got the phone won't lose any app data or sdcard data like the methods that have you unlock the bootloader do. The disadvantage is your bootloader remains locked, which may prevent you flashing certain things in the future.
edit: see ravidavi's posts below; he's shown you can even flash custom roms that are clockwork compatible while having a locked bootloader with this method.
Download these two files:
clockwork recovery v3.0.0.5 or clockwork recovery v3.0.0.5 mirror if above not working
su-2.3.6.1-ef-signed.zip
Koush's blog for the latest clockwork updates (find Nexus S in the list).
Also, if you don't already have the necessary android sdk and drivers on your computer, get them from here: http://developer.android.com/sdk/index.html and install them. Some Windows users report better luck just installing pdanet. There's a decent guide for Windows users on installing the sdk here.
Place the recovery file on your laptop where you can access it while using the sdk fastboot commands.
Place the su zip one in the top level folder of your sdcard.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the excellent instructions that Allgamer gives in this GUIDE, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps below.
To navigate in the clockwork recovery, you use the volume keys to scroll up/down through the menus, and the on/off button to select what's highlighted.
(note: some report success without these first 3 steps, others don't get a succesful root without, I recommend doing them)
select mounts and storage.
select mount /system
select go back
select install ZIP from sdcard
select choose zip from sdcard
select su-version#-signed.zip file you downloaded earlier
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
After the phone reboots, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
This method doesn't install busybox, so go to the Market and download/install busybox directly, or get Titanium Backup and check it's "problems?" button and let it install busybox for you. There's also an app called root checker that supposedly verifies you have a working root on your phone.
Once you have a successful root installed, I'd suggest getting back into clockwork recovery and running a nandroid back up from clockwork's backs and restore menu. Then copy that file from your sdcard (in the /clockwork/backups folder) to your laptop for safe-keeping and an easy full system restore to a known working config.
Usual disclaimers about I'm not responsible for damage to your phone or loss of data apply. Use any rooting method at your own risk.
Thanks and all the real credit go to inakipaz, shrivelfig and allgamer, and of course to koush, and ChainsDD for the superuser apk.
Worked perfectly. I used fastboot from my Mac (outlined in the stickied Mac Root thread). Root checker verifies that I have root.
And by the way, my phone and I are both root/ROM cherry. First android phone, first time rooter. Will work up the guts to flash a ROM soon, but of course there's no chance of doing THAT without unlocking the bootloader.
Thanks to all involved in this!
yeah! good work!
Srsly. Awsom.
Someone sticky this....
Question: When you do the fastboot boot command, does that overwrite the stock recovery with Clockwork? Or is it just booting into the recovery img without actually flashing it?
I would think this method also gives you a way to back up before unlocking the bootloader.
1) fastboot boot into Clockwork as described here
2) Full nandroid backup from Clockwork
3) Mount "SD" from Clockwork over USB, copy everything to computer (since it wipes everything)
4) Go back and unlock the bootloader as usual, resulting in a full wipe
5) Flash Clockwork Recovery again through whichever method
6) Mount "SD" from Clockwork over USB, copy the backup back to phone
7) Restore nandroid
And now you've unlocked the bootloader without amnesia =)
ravidavi said:
And by the way, my phone and I are both root/ROM cherry. First android phone, first time rooter. Will work up the guts to flash a ROM soon, but of course there's no chance of doing THAT without unlocking the bootloader.
Thanks to all involved in this!
Click to expand...
Click to collapse
Are you sure you need to unlock the bootloader to flash a ROM? Now that you have root, try installing ROM Manager from the Market, and see if it lets you flash custom recovery with bootloader still locked. If so, then yes you can install a ROM!
Also, the fact that you're able to boot into Clockwork using "fastboot boot" - that also means you can install a ROM .zip file right from there.
cmstlist said:
Question: When you do the fastboot boot command, does that overwrite the stock recovery with Clockwork? Or is it just booting into the recovery img without actually flashing it?
Click to expand...
Click to collapse
"fastboot boot" only launches the recovery no unlock needed. "fastboot flash" flash the recovery
cmstlist said:
Are you sure you need to unlock the bootloader to flash a ROM? Now that you have root, try installing ROM Manager from the Market, and see if it lets you flash custom recovery with bootloader still locked. If so, then yes you can install a ROM!.
Click to expand...
Click to collapse
It worked! Here's the process I used, starting from a completely unmodded Nexus S.
1: Use the method detailed here to gain root access without unlocking the bootloader.
2: Using a root-enabled file explorer (I used Super Manager), rename install-recovery.sh (in /etc) to install-recovery.sh.old . You'll need to remount as r/w to do this. NOTE: You don't *have* to do this step, but if you don't, then you can only use clockwork once after which it will be erased on reboot.
3: Using ROM Manager, install Clockwork Recovery.
4: Pleasure yourself, because your bootloader is still locked and nothing was erased.
I have yet to try actually flashing a custom ROM. Does this mean that it can also be done without unlocking bootloader?
Well damn, whaddaya know. I just flashed MoDaCo r10 without unlocking the bootloader, and without losing any personal data on /sdcard.
I figure someone at XDA should like this.
Pretty much followed distortedloop's advice. Starting from a fully stock Nexus S with Android 2.3.2 (GRH78C):
* Root using the method on this thread.
* Rename install-recovery.su to install-recovery-old.su. (in /bin)
* Install Clockwork Recovery from ROM Manager.
* Download whatever ROM you want (compatible with Clockwork), rename to update.zip, and copy to sdcard.
* Reboot into Clockwork.
* Wipe cache, reset to factory (IF REQUIRED BY NEW ROM). This was my first install of MoDaCo, and that requires it. This step does NOT erase your personal files on sdcard, just all android-related files.
* Install update.zip from Clockwork.
* Continue self-pleasuring ... you now have a custom rom without touching your bootloader or wiping your personal sdcard data.
Maybe it's just because I'm a noob here, but it seems to me that this is a BIG deal. All root/ROM installation methods that I've seen so far have required an unlocked bootloader. This seems to be the first time a Nexus S has been unlocked and custom-ROM'd without unlocking the bootloader and wiping the entire /sdcard.
Ravi
Yeah, it's pretty clear that the unlock the bootloader step isn't necessary for most of what we want to do. Just a habit from earlier devices, perhaps?
What's really odd is now we have to wonder what's the purpose of the oem unlock erasing your sdcard? Speculation was that it was a security feature to keep people from accessing your data if they stole your phone; they couldn't flash something on the phone to get access, but clearly they can. Fastboot into a custom recovery and you own the phone.
Perhaps this is a security hole Google will try to fix some day?
At any rate, I wish we'd discovered this sooner, it would have saved several people some grief in having to lose saved games (Angry Birds!) when they finally decided to root.
distortedloop said:
Yeah, it's pretty clear that the unlock the bootloader step isn't necessary for most of what we want to do. Just a habit from earlier devices, perhaps?
...
At any rate, I wish we'd discovered this sooner, it would have saved several people some grief in having to lose saved games (Angry Birds!) when they finally decided to root.
Click to expand...
Click to collapse
You say "for most of what we want to do." Could you think of a case where you would need to unlock it now? It's now shown to be unnecessary for rooting and installing custom recovery/ROM.
Is there any way to get the word out? This thread isn't stickied, and all the stickied threads on rooting & custom ROMs currently assert that you have to unlock the bootloader.
Ravi
ravidavi said:
You say "for most of what we want to do." Could you think of a case where you would need to unlock it now? It's now shown to be unnecessary for rooting and installing custom recovery/ROM.
Click to expand...
Click to collapse
I'm thinking that something like Superboot might need to have the bootloader unlocked, since it replaces the boot image, right? But I'm not sure.
ravidavi said:
Is there any way to get the word out? This thread isn't stickied, and all the stickied threads on rooting & custom ROMs currently assert that you have to unlock the bootloader.
Ravi
Click to expand...
Click to collapse
There's only a page and a half of posts in the development section right now, so it's not likely to disappear any time soon, but you could ask a mod (theimpaler747 is ours) via PM to sticky it. I thought about asking myself, but seemed a bit tacky to ask for my own thread.
Meanwhile, I'd been linking people to various posts I'd made in other threads suggesting this might work, but once inakipaz and shrivelfig confirmed it, I'm just now pointing people here. I just hope people see this before wiping their phones unnecessarily.
Really, the other guides should just be updated to skip the oem unlock step. That's really the only different thing we're doing here.
i'm just waiting for more people "newbies" to confirm this actually works for them, before making it a sticky
In theory if you really really screw up your phone, you might need fastboot flash in order to recover it. But if fastboot also lets you boot into an img recovery... then you still have a recovery route that doesn't require unlocking.
Sent from my Nexus One using XDA App
I know it's a noob question and all since all you're doing is flashing a custom recovery but will you still be able to get OTA updates after doing this as well?
Sent from my Nexus S using XDA App
qreffie said:
I know it's a noob question and all since all you're doing is flashing a custom recovery but will you still be able to get OTA updates after doing this as well?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
yes because you still have the original recovery installed
distortedloop said:
Perhaps this is a security hole Google will try to fix some day?
Click to expand...
Click to collapse
This would be my guess.
But how? Is it possible to plug this with just a software update? Time will show, I guess.
This (security hole) should also make it possible to do perfect out-of-the-box OS backups. And restores. The problem is that nobody's going to do a backup without playing with their shiny new toy first.
shrivelfig said:
This would be my guess.
But how? Is it possible to plug this with just a software update? Time will show, I guess.
This (security hole) should also make it possible to do perfect out-of-the-box OS backups. And restores. The problem is that nobody's going to do a backup without playing with their shiny new toy first.
Click to expand...
Click to collapse
I can confirm that the Nexus One does not allow this "fastboot boot" on a locked bootloader. Maybe this was just an oversight?
It is entirely possible to plug this with a software update: Samsung/Google could issue a signed update that includes a bootloader upgrade. This has been done many times by HTC for example.
I can confirm that this method works, without unlocking the BL or erasing the SD part.
This is pretty cool. I wish I new about this before I unlocked the bootloader days after I received my phone. I too wonder if this was intentional or an oversite. Google did want this phone to be for developers, but like other's said, this is also a bit of a security hole. The wiping of the sd card on unlock would protect the person if the phone was stolen, like if there was confidential corporate stuff on there. Even if you password protect your phone, someone could fastboot clockwork, mount the sd card and retrieve all the information that was on there.
cmstlist said:
It is entirely possible to plug this with a software update: Samsung/Google could issue a signed update that includes a bootloader upgrade. This has been done many times by HTC for example.
Click to expand...
Click to collapse
It's also been done by Samsung with some versions of the Galaxy S line (some of the "leaked" roms, and even one official kies push (IIRC) changed the bootloader, causing people the ability to use 3 button mode for Odin access, and causing others to lose it.
Since none of the Root Toolkits were working for me, I've gone ahead to try to root through the command prompt.
I have a question about CWM Recovery though. I've flashed it on my Nexus 7, but not permanently since adb always hangs. (Which is why the toolkits weren't working for me). Everytime I reboot my Nexus 7, I have to re-flash the recovery.
My question is: Is there another way to make the CWM Recovery permanent? Not through adb? Would I be able to first root my Nexus, and then make the CWM permanent another way?
You're losing cwm every reboot because you happened t to overlook the fact that, to make it permanent, you need to delete the script that reverts you to stock recovery upon reboot. Read one of the routing guides stickied in the dev forum and follow the instructions. Easy as pie.
Sent from my Nexus 7 using Tapatalk HD
well, you dont use ADB to install recovery, you use FASTBOOT
once you are rooted, you could go the easy way and install GooManager and use TWRP instead of CWM...or use ROM Manager to flash cwm
*hint: the reason its not sticking is because of a file you didnt delete in the /system partition.....
najaboy said:
You're losing cwm every reboot because you happened t to overlook the fact that, to make it permanent, you need to delete the script that reverts you to stock recovery upon reboot. Read one of the routing guides stickied in the dev forum and follow the instructions. Easy as pie.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I was following this thread here: http://forum.xda-developers.com/showthread.php?t=1741395
In order to make it permanent, I need to run adb which always hangs on me as stated above. Hence why I was looking for an alternate route.
Pirateghost said:
well, you dont use ADB to install recovery, you use FASTBOOT
once you are rooted, you could go the easy way and install GooManager and use TWRP instead of CWM...or use ROM Manager to flash cwm
*hint: the reason its not sticking is because of a file you didnt delete in the /system partition.....
Click to expand...
Click to collapse
I know you use Fastboot to install the recovery, though you use adb to make the recovery permanent.
I think I might try out GooManager and flash TWRP after I am rooted. Thanks!
Daniuhl said:
I was following this thread here: http://forum.xda-developers.com/showthread.php?t=1741395
In order to make it permanent, I need to run adb which always hangs on me as stated above. Hence why I was looking for an alternate route.
I know you use Fastboot to install the recovery, though you use adb to make the recovery permanent.
I think I might try out GooManager and flash TWRP after I am rooted. Thanks!
Click to expand...
Click to collapse
You don't need adb to make it permanent. Use a root file explorer or a terminal emulator
Sent from my Nexus 7 using Tapatalk HD
I tried to root my Nexus 6P and now I'm stuck. It won't finish booting. I followed instructions found on the web. I unlocked bootloader with no problem. I copied the latest SuperSU file to the phone. I installed TWRP recovery. However, I could not find the SuperSU file when using TWRP. Nevertheless, when I went to exit, TWRP asked if I wanted to instal SuperSU. I recall reading somewhere that it will install the wrong version of SuperSU (not the one for 6.0.1). Somehow I must have hit the wrong selection because it installed it anyway. Now I have an infinite loop.
I have tried to factory reset with TWRP. That fails. I downloaded the 6.0.1 images files from Google. I tried to run flash-all.bat, but that doesn't work. I have pushed images and ZIPs to the /sdcard/ folder with ADB. ADB recognizes the device, but fastboot does not (when connected to my laptop) (which is why flash-all doesn't work). I have tried to install the images/zips with TWRP. However, I always get "failed" messages. I get messages that partitions won't load.
Stupidly, I do not have a nandroid backup (yes, I know, a dumb move).
Any suggestions on what to try next? I'm at my wit's end with this. I've searched the web all morning and found all kinds of helpful info, but I can't find anything to get me past this point. I am perfectly willing to wipe it all out and start over again if I could just force it to do that. I just bought it so I suppose I could return it (I think there's a 30-day return policy), but Google might not like it if it comes back in this state, I suppose. I had an AT&T Galaxy Note 5 for half a day but found out, after the fact, that I can't root it.
Thanks for any help or suggestions.
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
jaidev.s said:
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
Click to expand...
Click to collapse
I saw that post. I wish I had followed it. However, the instructions are very similar to what I tried, although not exact. Where I went wrong is letting TWRP install SuperSU for me. I didn't mean to but when I touched the phone it installed it (of course, I hit something, but I don't know what). Fastboot does not recognize the phone in recovery. I can follow Heisenberg's instructions to get back to stock IF fastboot would recognize the phone. ADB recognizes the phone. Would it be possible to use ADB Sideload instead? How can I force fastboot to recognize the phone? If I could do that, I would be able to flash images back to the phone. Thanks!
U should try fastboot in bootloader / download mode instead of recovery mode..
OK, two comments: Duh (as I slap my head) and Bless You! That worked. I'm back to stock. At least the phone works now. I'll try again to root following Heinsenberg's instructions! Thanks. Where do I sent the beer money?
jaidev.s said:
U should try fastboot in bootloader / download mode instead of recovery mode..
Click to expand...
Click to collapse
Well, I'm back to a stock phone, anyway. Flashing SuperSU per Heinsenberg's instructions did not give me root. Oh well. I'll keep trying. It did install and it did reboot just fine. However, root checker says I have no root and Titanium Backup won't run, either. Thanks.
The phone is the Huawei Nexus 6P (MMB29M). No clue how this happened, but I managed to get root (working fine I can run apps that require root), but TWRP isn't on my phone. When I try to boot to recovery, it gives me the dead android symbol (dead android with front flap opened up and little red exclamation point). I can get into the boot loader just fine though, it's ONLY the recovery that is missing. Is it okay to use the TWRP app to install recovery the easy way? I have the TWRP app on my phone from the (failed) TWRP install, I guess. Or do I need to go through the whole root/recovery fastboot process again?
I don't know how I even got root without recovery, tbh. I was obviously in TWRP when I flashed superSU and busybox, but for whatever reason, it didn't stick. The only thing I can think of is that the phone took the liberty of replacing the recovery on its own when I restarted the phone (I didn't think to go back into recovery immediately, so the phone overwrote it...is that possible?)
The reason I'm asking about the TWRP app is because it has a very specific directory that it says it needs to install into and if that directory is wrong, the phone could be bricked. I've had the phone for less than a week, I'd prefer not to brick it. This is my 5th android device and I've never run into this issue before...in fact, I didn't even know it was POSSIBLE to get root without recovery. I did get a soft-brick earlier in the process, but I fixed it by re-flashing the stock android ROM (I also had to go change my pants afterward, but that's a story for another thread).
Thanks in advance for any assistance you can provide and have a nice Friday.
baronmax said:
The phone is the Huawei Nexus 6P (MMB29M). No clue how this happened, but I managed to get root (working fine I can run apps that require root), but TWRP isn't on my phone. When I try to boot to recovery, it gives me the dead android symbol (dead android with front flap opened up and little red exclamation point). I can get into the boot loader just fine though, it's ONLY the recovery that is missing. Is it okay to use the TWRP app to install recovery the easy way? I have the TWRP app on my phone from the (failed) TWRP install, I guess. Or do I need to go through the whole root/recovery fastboot process again?
I don't know how I even got root without recovery, tbh. I was obviously in TWRP when I flashed superSU and busybox, but for whatever reason, it didn't stick. The only thing I can think of is that the phone took the liberty of replacing the recovery on its own when I restarted the phone (I didn't think to go back into recovery immediately, so the phone overwrote it...is that possible?)
The reason I'm asking about the TWRP app is because it has a very specific directory that it says it needs to install into and if that directory is wrong, the phone could be bricked. I've had the phone for less than a week, I'd prefer not to brick it. This is my 5th android device and I've never run into this issue before...in fact, I didn't even know it was POSSIBLE to get root without recovery. I did get a soft-brick earlier in the process, but I fixed it by re-flashing the stock android ROM (I also had to go change my pants afterward, but that's a story for another thread).
Thanks in advance for any assistance you can provide and have a nice Friday.
Click to expand...
Click to collapse
This happened to me after the first time I installed twrp. I selected read only system after booting into twrp for the first time(they ask you if you want a read only option) and the stock rom would over write twrp with the stock recovery. Only fix for me was starting from scratch using step 11 here http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928. When you install twrp dont select the read only option and you'll be fine. Just remember not to let twrp install Su when it asks you to.
did you not read and follow the VERY detailed and specific instructions on how to do all of this, before beginning the process?
mistakes happen, and we are all here to help, but a softbrick followed by no recovery etc just seems like you tried to wing it without taking the proper time to read how to do it on your new device.
I'm sure someone will be able to give you a definite answer, but I also advise you to read @Heisenberg's guide on how to do it all on your 6P in the General section
Soulfly3 said:
did you not read and follow the VERY detailed and specific instructions on how to do all of this, before beginning the process?
mistakes happen, and we are all here to help, but a softbrick followed by no recovery etc just seems like you tried to wing it without taking the proper time to read how to do it on your new device.
I'm sure someone will be able to give you a definite answer, but I also advise you to read @Heisenberg's guide on how to do it all on your 6P in the General section
Click to expand...
Click to collapse
I read everything and my only mistake was selecting the read only option which clearly tell you that if you select read only it cant prevent the stock rom from over writing twrp with its own recovery. Mistakes happen.
can you not just install twrp again from the bootloader?
ahfu25 said:
I read everything and my only mistake was selecting the read only option which clearly tell you that if you select read only it cant prevent the stock rom from over writing twrp with its own recovery. Mistakes happen.
Click to expand...
Click to collapse
I was responding to the OP, not you.
uicnren said:
can you not just install twrp again from the bootloader?
Click to expand...
Click to collapse
Yes, but I was wondering if it was a bad idea to just let the TWRP app do it? That's what it's designed to do (that, and update TWRP). That's why I asked the question, I wasn't sure if that was a viable way to go about this or whether I just needed to re-do it from the nexus 6p "how to" that's on the site here.
Soulfly3 said:
I was responding to the OP, not you.
Click to expand...
Click to collapse
OK...have a nice day
I can't say for sure that I understand what you mean by using twrp when you don't even have it... but maybe see this post. (The bottom of that post.)
---------- Post added at 11:51 AM ---------- Previous post was at 11:46 AM ----------
oh, I get what you're saying now - can you do it with the twrp app - as in an actual app. i missed that word. I think i remember Heisenburg saying that, no, you shouldn't use the app. I think it doesn't get the right twrp version. the version we need for the 6p is in beta and not available throught the app.
---------- Post added at 12:07 PM ---------- Previous post was at 11:51 AM ----------
In a previous post of mine, I quoted the explanation from TWRP of the system read-only vs read-write thing: http://forum.xda-developers.com/showpost.php?p=64707169&postcount=2143 I think you may need to mount the system read-write to get twrp to "stick". ...or you need root (according to sirxdroid)? I don't know which... I'd love to know how you get it working again!
p.s. Sorry to keep appending to my response...
Good explanations and links, I had the same issue when I decided to root. I did not choose read only during my initial flash of TWRP and could not figure out why every time I flashed TWRP, rebooted then went into recovery, I lost TWRP! After I did my due diligence and read the threads, I realized what I did wrong. I flashed back to stock, then flashed TWRP as recovery. I went into recovery via bootloader and chose read only. Then I installed the su.zip, rebooted the bootloader, then it was all good. Good luck.
I think what I did wrong is fail to wipe the caches (not sure how I missed it, but I did, originally). I'm not entirely sure why that makes any difference, but I went through the rooting process again and installed TWRP, now things are working properly. I did two things differently, wiping the cache and booting directly back into recovery after installing recovery. I saw on the TWRP website that some ROMs will overwrite the boot.img and recovery sections if you don't boot back into recovery immediately (it doesn't overwrite them after the second time, for whatever reason). I'm not sure if this is what happened or not, but it's the one thing that actually makes SOME sense to me.
It's interesting that there's an app out there which claims to install TWRP, but people shouldn't use it, that would be a mighty handy app to have if it worked properly, no more worries and very little fuss.
Why not just fastboot flash recovery........takes 10 seconds.
I have a v20 US996 (unlocked) that I'm getting ready to unlock the bootloader and then I'll want to root. I've always rooted with SuperSU in the past, but now there is also Magisk.
For our v20s (US996):
1) Should we use Magisk instead of SuperSU?
2) Is it as stable as SuperSU (without random reboots, etc)?
3) If 1+2 are "yes" then where can I find out how to root with Magisk safely without any problems?
Thanks!
I say yes to your first two questions. I accidentally upgraded to 10H on the 996 and I thought I was stuck with an unrootable phone. I had already had an unlocked bootloader and I used ADB to flash TWRP, flashed Magisk and boom. Rooted again. Been happy ever since. I don't have the exact thread for Magisk but if you Google I wanna say Magisk 14.0 you should be able to find it. Been working great for me. Hope that helps.
Anyone else's thoughts?
Also, will I still be able to use the 2nd screen?
And where can I find instructions specific to the v20?
Magisk works great and passes SafetyNet. No reason to still use SuperSU. Switching can be problematic. You need to reflash the correct boot.img, then flash Magisk WITHOUT LEAVING TWRP.
Sizzlechest said:
Magisk works great and passes SafetyNet. No reason to still use SuperSU. Switching can be problematic. You need to reflash the correct boot.img, then flash Magisk WITHOUT LEAVING TWRP.
Click to expand...
Click to collapse
Especially with chainfire retiring, now is all the more reason to use magisk only. I've been using supersu for the entire duration of my smart phones but I need to make the switch.
Thanks.
I have not yet rooted this phone. Should I follow the instructions from jcadduono to root this and then be sure to flash magisk instead of supersu?
(jcadduono's instructions are here: https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
baldybill said:
Thanks.
I have not yet rooted this phone. Should I follow the instructions from jcadduono to root this and then be sure to flash magisk instead of supersu?
(jcadduono's instructions are here: https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Click to expand...
Click to collapse
I had this same problem, I asked this question on the subreddit, I got an absolutely amazing response and I fixed the phone. Pretty much just flash the 10f kdz, and then re unlock the bootloader if needed, then flash twrp normally, DO NOT US RECOWVERY. here is the link to the person who helped me with all of this, https://www.reddit.com/r/lgv20/comments/73hsl3/upgrading/. Just read the comments from Pheonix591 and I.
GreenDinoXD said:
I had this same problem, I asked this question on the subreddit, I got an absolutely amazing response and I fixed the phone. Pretty much just flash the 10f kdz, and then re unlock the bootloader if needed, then flash twrp normally, DO NOT US RECOWVERY. here is the link to the person who helped me with all of this, https://www.reddit.com/r/lgv20/comments/73hsl3/upgrading/. Just read the comments from Pheonix591 and I.
Click to expand...
Click to collapse
Thanks
(I've never rooted this phone, so it's not an issue of re-rooting, it's an issue of rooting to begin with)
Why not use recowvery?
baldybill said:
Thanks
(I've never rooted this phone, so it's not an issue of re-rooting, it's an issue of rooting to begin with)
Why not use recowvery?
Click to expand...
Click to collapse
It isn't necessary for our device since we can just flash TWRP through fastboot after unlocking bootloader officially. If you need me to I can write you a step by step guide, it'll be done tomorrow after school but I can write it for ya if need be.
GreenDinoXD said:
It isn't necessary for our device since we can just flash TWRP through fastboot after unlocking bootloader officially. If you need me to I can write you a step by step guide, it'll be done tomorrow after school but I can write it for ya if need be.
Click to expand...
Click to collapse
Please do, I don't want to mess up my phone.
It's never been unlocked or rooted. [Currently, I'm having trouble getting the unlock image from LG. ]
Okay i am going to copy the exact text that the person who helped me said. It is really well explained and he says the steps very clearly. To do a TWRP backup and restore it it's one of the main buttons on the screen, I highly recommend using an SD card. Use the select storage button to change between internal storage and the SDcard, just check the box for data, and that has all your apps and pretty much everything else. And when you do the kdz part below you can just restore the version f firmware and do the update that way and skip the ota. I copy and pasted most of the rest from the last time I typed this up.
Get a hold of LGUP and downloading the kdz, heres (https://forum.xda-developers.com/v20/how-to/v20-kdz-restore-failing-9-completing-fix-t3546817) a good thread on it, with even all the tools attached except the kdz, for getting on the older more stable twrp just flash flash it in fastboot (use lgup to restore the kdz which gets back to full stock, then use fastboot to get the info needed to fill out the form on LG's site(https://developer.lge.com/resource/mobile/RetrieveBootloader.dev), (basically this guide has it all listed out, plus once you've created an lg account and actually gotten to the form, the page with has directions too(http://www.droidviews.com/unlock-bootloader-on-lg-v20-us996/))
So heres how we're going to get twrp on here from a stock, but unlocked us996. You probably don't need the no-verity-opt-encrypt if also flashing supersu or magisk but I did it anyway to be safe.First get the latest version of no-verity-opt-encrypt.zip from here(https://build.nethunter.com/android-tools/no-verity-opt-encrypt/), and the stable version of Twrp-3.0.2-1-us996.img from a different directory on the same site(https://build.nethunter.com/test-builds/twrp/lge/), if you have an sd card in your phone put the no-verity zip on it ahead of time (and if you want to save a boot, put magisk on there too) (if not twrp should let you transfer it from your pc, but I havn't done it that way). So go ahead and reboot into fastboot (adb reboot bootloader) mode, then fastboot flash the_FULL_PATH_to_twrp-3.0.2-1-us996.img . once it successfully completes, until we flash the no verity zip in twrp if the phone boots into stock it will overwrite twrp and it will need to be reflashed in fastboot mode. So once you've flashed it the first time, pull the battery, wait a second, then put it back in, hold down volume down, hold the power button just until the LG logo appears, then let go of the power button, and immediately press (and release) it once while still holding down volume down, keep holding volume down until, if you've done it successfully, it will ask you to factory reset your phone (for future note, while twrp is installed this will NOT factory reset your phone), say yes both times and twrp will boot shortly.
From here, go to install, and then change to your sd card and install the no-verity-opt-encrypt.zip, then go back and hit wipe (in twrp), on the wipe screen, hit the format data button (the correct button will make you type out yes to confirm), from here twrp will be installed and not tampered with and you can safely install magisk or a custom rom, and/or boot back into stock.
I do not know where i downloaded magisk from but here is the latest version:https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I recommend getting version 13.3 and then upgrading to version 14. Hope this helps and if you have any questions feel free to ask, im just busy so i may not answer quickly, working on college applications so i apologize in advance
I'm in a similar situation, with a fresh US996 factory-unlocked. Does this method (stock + magisk + twrp) preserve Android Pay / SafetyNet?
I switched from SuperSU to Magisk and now I can download Netflix from Play Store.
Switch away if you want to.
Thanks, GreenDinaXD, I'll give that a try after a while.
Thanks
GreenDinoXD said:
I recommend getting version 13.3 and then upgrading to version 14. Hope this helps and if you have any questions feel free to ask, im just busy so i may not answer quickly, working on college applications so i apologize in advance
Click to expand...
Click to collapse
Oh, why do you suggest using Magisk 13.3 and then upgrading? Why not just go straight to 14?
baldybill said:
Oh, why do you suggest using Magisk 13.3 and then upgrading? Why not just go straight to 14?
Click to expand...
Click to collapse
Believe I read somewhere that it didn't work as well or gave someone trouble, so I just told you the way I did it and I had no problems. If you want to try going straight to 14, go for it.
With my experience from MagiskSU, absolutely, Magisk let's you use any anti-root app, like Snapchat, or Netflix, etc... So you don't need to go through the Xposed McCluster**** ordeal
GreenDinoXD said:
Believe I read somewhere that it didn't work as well or gave someone trouble, so I just told you the way I did it and I had no problems. If you want to try going straight to 14, go for it.
Click to expand...
Click to collapse
Are there stability issues with Magisk? Random reboots?
I'm curious since this is my everyday phone and I want it to be running decently. Thanks!