Hi guys. Please bear with me - I am a noob to rooting phones and custome recoveries. I haven't had an android device since ~2011, so I need some time to get reacquainted. (Poke fun at me for using iPhones)
Either way, I recently got a 5" Google Pixel and have been looking for a decent guide to root it. I have done research on the topic, but I can't find a straightforward guide or instruction list. I believe I could do it, I just don't want to risk bricking a $700 device.
From my understanding, I need to unlock the boot loader, adb boot some custom recovery image, then install the latest root package. Again, if my jargon is confusing I apologize - I've beeb with the Jailbreaking community for quite a while and haven't tweaked an android device forever.
Could someone link a guide or help me out? Also I have been reading places that you must flash the supersu zip to two different locations for it to work properly.
In the end, I'm hoping to have my Pixel rooted on the most recent firmware and be able to use Adaway and to be able to update with FlashFire (I think that's the name). Also, I'm hoping to keep systemless root to avoid tripping SafetyNet. I would like to be able to easily update.
Thanks in advance guys, sorry for the long post. Hopefully someone more knowledgable can take me under their wing.
xxbilxx said:
From my understanding, I need to unlock the boot loader, adb boot some custom recovery image, then install the latest root package.
Click to expand...
Click to collapse
That's the procedure. I booted TWRP Alpha 2 for installing SuperSU, so that I didn't need to worry about the popup that sometimes doesn't show up on TWRP RC1. The following seems somewhat verbose to me, but it's the correct procedure and includes videos if you want to watch someone do each step. You don't need to download the TWRP zip, so like noted, you can stop at step 12 on the TWRP instructions and avoid installing TWRP to the phone.
https://www.androidexplained.com/pixel-systemless-root/
The latest SuperSU zip can be found here:
https://plus.google.com/+Chainfire/posts/27xToSqi5em
https://plus.google.com/+Chainfire
TWRP images for the Pixel (Sailfish):
https://dl.twrp.me/sailfish/
Related
Hi everyone! Excuse my limited knowledge on this. I did not see any threads on this question that was specifically related to 5.1. So I just side loaded the zip file for 5.1 LMY47D to my UNrooted and Locked Nexus 5 yesterday. Before doing so I did a facotry reset, mainly to keep it a fresh install and minimize issues. I figured before redownloading all my apps and setting everything back up, I might as well go ahead and finally unlock and root. So my main question is rooting 5.1 going to be the same procedure as rooting 5.0.1? If it is not the same, then can someone point me in the direction of the most reliable instructions on rooting 5.1. I have not found any rooting instructions relating specifically to 5.1 that I would completely trust or that were pretty detailed.
Same method for old version ,
First unlock device , flash recovery via fastboot
"Fastboot flash recovery recovery.img"
Download the latest root zip from chaunfire website or you can find the thread in forum , just flash it by recovery that already flashed ?
Thats all my friend nothing complicated
ali8383 said:
Same method for old version ,
First unlock device , flash recovery via fastboot
"Fastboot flash recovery recovery.img"
Download the latest root zip from chaunfire website or you can find the thread in forum , just flash it by recovery that already flashed
Thats all my friend nothing complicated
Click to expand...
Click to collapse
+1
Thanks! Straight forward! Exactly the answer I was looking for. I thought it might be different since I know there was difference between rooting 4.4 and 5.0. Anyways Thanks I will start checking it out now!
My device is European L04, currently running North Africa release (the earliest Marshmallow build uploaded) - L04_2016_0316_0900 (B820)
I'd like to unlock the bootloader and root my Honor 6. I've never done it (on this particular device), because I've read enough here to know it's slightly more risky than on other devices, especially when you plan to update the stock rom soon, so I preferred to wait until I have the last important update the device is likely to receive - Android 6.0.
What I want to know (some of the answers are in the topics which I listed below):
MultiTool - I've seen reports of bricks when using MultiTool with EMUI4/Marshmallow - why does it happen? My understanding is that MultiTool is a bundle of adb/fastboot and some recovery images for older Android versions, so my theory is that instead of using MultiTool, I should simply get the proper recovery for Marshmallow and flash it manually with fastboot, right?
unlocking bootloader, rooting, flashing recovery - I think I understand the process; in a nutshell: 'fastboot oem unlock X', 'fastboot flash recovery imagename.img', then flash the proper SU.zip in recovery. Where do I find the code, the Marshmallow recovery image, the SU.zip file?
will recovery backup in TWRP work without any problems?
what is the procedure to go back to stock completely after rooting? Unroot, (then wipe if it's needed?) so I am able to safely flash stock firmware again (since, from what I know, flashing stock on a rooted phone makes itself brick permanently, right? or is it just a soft-brick and it can be fixed?)
is there anything else I should know before proceeding?
What I found so far:
http://forum.xda-developers.com/showpost.php?p=66615082&postcount=502 - two recovery images, TWRP and another one (stock?) for the Marshmallow release
http://forum.xda-developers.com/honor-6/general/honor6-multi-tool-t2963060/page50 some rooting instructions for the L02 beta, see posts 494 and 498; no idea whether this is applicable to final Marshmallow or L04 at all
http://forum.xda-developers.com/honor-6/general/huawei-honor-6-plus-unlock-bootloader-id-t3357259 an app to get the unlock code, seems a bit shady to me though on the first glance
http://forum.xda-developers.com/honor-6/development/honor-6-rooting-method-t2962795 alternate methods for bootloader (through a website or by email), in case the app won't work; also, detailed instructions on unlocking and rooting
Basically, I need to know whether my procedure is more or less right before I proceed. I think the information is quite hard to find and the risks are quite high, so I'd like to make a promise - when I'm done rooting it and I know the correct process, I'm going to make a "Update to Marshmallow, unlock, root" how-to thread for all the people that will need it in the future.
Another two questions...
1. Where do I get proper SuperSU for Marshmallow? I get a boot loop (yeah, I know I have to wait and I did, but it's a pretty obvious bootloop from watching the logcat content, and nothing new happens...) after flashing http://download.chainfire.eu/supersu-stable (2.65).
2. I have unlocked my bootloader and installed TWRP, so recovery and fastboot are functional. I didn't make a backup before flashing the zip and now I'm in a bootloop. How do I restore working Marshmallow? I assume I can either beg somebody to upload a TWRP backup for my H60-L04, or somehow flash the stock over what I have now. Can I simply use manual update from SD? Can I somehow flash Marshmallow again with fastboot? I'm too scared of bricking my device right now so I guess I'll brace myself for a few days without a phone until somebody helps me :/
I just flashed the Marshmallow release I had before the bootloop (I used Huawei Update Extractor and flashed boot, cust, system and recovery with fastboot; then open up Huawei recovery and factory reset for good measure, I'm not sure it was even needed) and the device is working. I'll restore my stuff, install TWRP, make a backup then try out your ZIP. Thanks
edit: thanks again - your zip works indeed. So after the initial hurdles, now I've got working root and a reasonable way of restoring in case I screw something up along the way.
Before making a new topic with the tutorial I have a few more questions.
First of all, why exactly we weren't supposed to update the rooted devices? I'm not currently interested in OTAs (it's pretty obvious that it needs a functional Huawei recovery, and you need to unroot cause an update can make a mess in a rooted system, making it bootloop for example), but can we flash extracted images with fastboot on rooted devices? Logically, we should be able to... How about sdcard update method?
Can we flash Marshmallow on Kitkat? (fastboot, sdcard, local update methods?) Or do we need to update to Lollipop along the way?
Can I flash stock roms in general (evenbetween different Android versions) by using fastboot with {boot, cust, recovery, system} images only? There's a lot of images that you can extract with Huawei Update Extractor - why there's so many if they're not needed?
This is the first phone where I don't plan to install a custom ROM, and I don't know how OTA updates work while rooted.
Can they still be downloaded/installed normally while rooted? If so do I need to re-apply root each update? Does updating while rooted, or reapplying root afterwords wipe apps/settings?
I'm not sure if these are questions that can even be answered now, before anything has shipped, but worth a shot.
I might be wrong but I believe once you root you have to side load any OTA updates that come along and you may have to reroot and no this won't wipe ur phone
Flash Fire will be the way to go....
On rooted 2016 pixel never got flashfire to work for an ota. As for sideloading, that didn't work either. Had to download latest full image and use minimal adb to flash the full image. That can be done without wiping the phone and the detailed instructions are on XDA. I wonder if the pixel2 will be rootable by the same method to root the 2016 pixel. If I trade in for the pixel2 I will try it.
me_droid said:
On rooted 2016 pixel never got flashfire to work for an ota. As for sideloading, that didn't work either. Had to download latest full image and use minimal adb to flash the full image. That can be done without wiping the phone and the detailed instructions are on XDA. I wonder if the pixel2 will be rootable by the same method to root the 2016 pixel. If I trade in for the pixel2 I will try it.
Click to expand...
Click to collapse
I started with full image and removing the w.
Then Google started releasing OTA So I used flashfire and it worked fine.
I tried sideloading and it worked also.
During the whole period, I never lost root or hotspot accept for the last update I lost hotspot because of an update changing Carrier entitlement. So I had to go about modding system file but. My hats off to developers. I suggest everyone donates to the people who make things available.
Thanks,
There is a tutorial for using Magisk Manager with OTA Updates and A/B partition. I hope this will work with Pixel 2?
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
FSMcas said:
There is a tutorial for using Magisk Manager with OTA Updates and A/B partition. I hope this will work with Pixel 2?
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Nice tutorial. Is there a way to install magisk any easier if I don't care about OTA's? Can't I just flash magisk and carry on or do I still have to worry about the A/B partitions?
I did this and now I'm stuck in a bootloop!
FSMcas said:
There is a tutorial for using Magisk Manager with OTA Updates and A/B partition. I hope this will work with Pixel 2?
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
I followed this procedure and everything seemed to be fine until reboot. At first it would attempt to boot, get to the screen with the G logo, and then after a few seconds reboot again, showing the unlocked bootloader warning screen. i interrupted the loop with the power button, and now I get to the G logo with the small grey animated progress bar going back and forth, but it hangs there and never completes booting..
I need a little direction on what my next step should be for obtaining root and twrp on my device.
As it states in the title, I just unlocked bootloader on my Sprint\Tmo OnePlus 8 5G.
I want to root and install TWRP, ultimately.
What I THINK I know so far in what I need to do next:
Obtain root (I need a good walkthrough on this as well)
Back up persist.img
Back up boot.img
Install magisk?
Patch boot.img with magisk?
Install TWRP via magisk?
Flash rom via twrp or magisk depending on rom requirements?
As you might see, I'm a little confused.
Can someone clarify the process for my specific adventure? Again, it's and freshly BL Unlocked Spront\Tmo OnePlus 8 5G on 10.5.21.IN55CB software.
Search the threads for guides.
TheKnux said:
Search the threads for guides.
Click to expand...
Click to collapse
As you can see it's read through a number of them but it all feels jumbled.
There's not one coherent guide that I could find. Could someone link me a complete guide to rooting this device?
I have been reading more articles about getting root access on an Android device and am finding the information to be contradictary. It might be the way I am reading it but when it says
"How To Install TWRP Custom Recovery On Any Android Phone (Without Root)"
I assume it actually means any Android, but it requires a custom recovery image for a particular phone so therefore it can only be for an android device where a custom image is available.
When I was running android 5.1 I installed TWRP so as to backup and restore my phone in case things went wrong, now I am running Android 7 it seems I cannot get a version of TWRP.
Can anyone assist as to what recovery tools I could install on a Ruggex 2 phone running android 7 please
thanks Roy
recovery is "independent" from main android OS. if you already have custom recovery installed on your device, it will even work without any OS installed, so it doesn't care if your phone is running Lollipop or Nougat. you can however check download source for newer version
If that is the case then why does the forum state
How to install TWRP on any Android device
but then goes on to say
Downloading TWRP for your device
which implies it is device dependant and not generic?
thanks Roy
Thx, I got it first time. of course custom recovery is device dependant. but that's not what I said. I said recovery mode is independent from android version. (at least till < 11)
btw it's not contradictory to say the Installation is generic for "any" android device (despites the difference device has recovery in partition or in ramdisk) while the Download is device dependant.
also take note that installing custom recovery and rooting android are two different tasks that do not depend on each other.
I think I am just getting more confused the deeper I go, it was fairly easy on my Android 5.1 device but with Android 7 it just seems to fight at every corner. I just cannot install and access TWRP on my device which is important for so many task.
what exactly is the problem?
I am trying to get root access on my Ruggex Rhino device, I had it all working when it was running Android 5.1 but the OS had to be upgraded to Android 6 or above for the new program to work, it is now on Android 7 .
I tryed the original method using King root but that fails to root and having read these forums it appears the way forward is to use Magisk rather than super user but that is another issue. This device on Android 7 does not have any recovery mode, power button and volume up just states no command and not sure if this is anything to do with my problems.
My ideal end goal would be a device running just the one navigation program and all the rest gone including phone module but have been told that is not possible so have to live with the bloated.
Roy
So you are the one who is confusing different things.
King root is so called one-click rooting app that tries to find exploit in its online database and provides root. This method is outdated, you can read more about here
https://android.stackexchange.com/questions/205706
the only one-click rooting app still working I am aware of is mtk-easy-su based on mtk-su exploit and magisk.
the "no command" screen is part of your stock recovery. this indicates your custom recovery has been replaced by stock recovery. read about "no command" screen here
https://android.stackexchange.com/questions/155705
installing custom recovery on android devices will break boot chain of trust. device will boot-loop and deny booting. therefore android will restore stock recovery on each boot, unless you disabled that feature.
read about dm-verity and stock recovery failsafe here
https://android.stackexchange.com/questions/214902
systemless-root is the root method available with SuperSU or Magisk, where system partition no longer is modified (to keep it healthy for updates). instead, the boot partition is modified, that requires bootloader to be unlocked (most devices).
bootloader unlocking will factory reset your device. some older devices allow installing custom recovery on locked bootloader, but you need to find a way to flash it.
Thats good information, move on away from Kingroot due to obsolescence and look into systemless root which from what I have gathered so far is not detected by the system. I will initially look into SuperSu as that was running on Android 5.1, I remember it used to ask for permision to access root and so far Magisk has just taken me round in circles. But first I will look at those articles and see what I can learn.
thanks Roy
actually, rooting with SuperSU is done by flashing SuperSU zip from TWRP. I couldn't find TWRP for your device, but we can help you porting generic TWRP for your device.
rooting with Magisk is done without TWRP
- unlock bootloader (+ factory reset)
- install Magisk apk
- patch boot.img with Magisk app
- flash patched boot.img
(see Installation Instructions)