Related
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?
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/
I am playing with different rom from many years but recently I am not able to root using SuperSU in a custom ROM (Stock Rom is finely rooted!)
These custom roms are not new and I used to have root in them earlier but now SuperSU is not showing up even after flashing from Recovery!!!
I am getting this error in Recovery while flashing:
SuperSU Boot Image Patcher
Patching Boot Image,
Boot Image not found, aborting!
Life is really bad without root.
(KingRoot is what I am using right now but I want SuperSU!)
Please come up with all kind of solutions I really need it!
Abhinay Pandey said:
I am playing with different rom from many years but recently I am not able to root using SuperSU in a custom ROM (Stock Rom is finely rooted!)
These custom roms are not new and I used to have root in them earlier but now SuperSU is not showing up even after flashing from Recovery!!!
I am getting this error in Recovery while flashing:
SuperSU Boot Image Patcher
Patching Boot Image,
Boot Image not found, aborting!
Life is really bad without root.
(KingRoot is what I am using right now but I want SuperSU!)
Please come up with all kind of solutions I really need it!
Click to expand...
Click to collapse
Logs will be critical in giving leads.
Just finished responding one on SuperSu here. (Got some references in there)
Questions:
1) "Tried flashing SuperSu from recovery". How about installing from Google Store?
2) Are the Recovery and SuperSu of the latest versions?
SR1-SuperSU-v2.82-SR1-20170608224931.zip
Google Store
3) Is the device is rooted? (Read that you are using KingRoot as of now, bear in mind uninstalling it revokes the root permissions just the way it does for SuperSu - you may want to refer the NOTICE on the Google Store link for SuperSu)
Btw the author has some more logs for you to zero in
Reference/s:
[APP][4.3+][ROOT][2016.12.10] LiveBoot (Logcat/Dmesg Boot Animation) v1.50
https://forum.xda-developers.com/android/apps-games/liveboot-t2976189
For known issues you may get help online, for rest you may find solace by reaching the SuperSu Guru, though you may not get any answers on PM as the Notice says.
Hope this helps.
Finally, Thank if you feel helped.
Please add my device for rooting. Is Micromax A106
Abhinay Pandey said:
I am playing with different rom from many years but recently I am not able to root using SuperSU in a custom ROM (Stock Rom is finely rooted!)
These custom roms are not new and I used to have root in them earlier but now SuperSU is not showing up even after flashing from Recovery!!!
I am getting this error in Recovery while flashing:
SuperSU Boot Image Patcher
Patching Boot Image,
Boot Image not found, aborting!
Life is really bad without root.
(KingRoot is what I am using right now but I want SuperSU!)
Please come up with all kind of solutions I really need it!
Click to expand...
Click to collapse
why don't you use magisk it worked for me in all custom ROMs and its like super su
Abhisekh sahoo said:
why don't you use magisk it worked for me in all custom ROMs and its like super su
Click to expand...
Click to collapse
can you tell me how to use magisk in MMX A106? I"m a noob
TL; DR: If you update to 5.6.1.0, do _not_ go back to an earlier bootloader.
It looks like Amz has finally implemented anti-rollback for the 2017 HD 10. If you update to the 5.6.1.0 bootloader (by adb sideloading the 5.6.1.0 update .bin or from Settings), rolling back to 5.6.0.1 or earlier (through an adb sideload) will brick the device. This has been an issue for other Fire tablets, but not for the 2017 HD 10 until this new update.
Note:
-- Moving back and forth between 5.5.0.0/5.6.0.0/5.6.0.1 is not a problem.
-- 5.6.1.0 continues to be rootable.
If you want to try out the 5.6.1.0 update, do the following:
-- Extract system.new.dat from the 5.6.1.0 update .bin
-- Convert system.new.dat to system.img using one of the MTK tools
-- Mount system.img in Ubuntu and inject the su binary and other su files
-- Flash the rooted system.img and the 5.6.1.0 boot.img (from the update .bin) in FlashFire
retyre said:
TL; DR: If you update to 5.6.1.0, do _not_ go back to an earlier bootloader.
It looks like Amz has finally implemented anti-rollback for the 2017 HD 10. If you update to the 5.6.1.0 bootloader (by adb sideloading the 5.6.1.0 update .bin or from Settings), rolling back to 5.6.0.1 or earlier (through an adb sideload) will brick the device. This has been an issue for other Fire tablets, but not for the 2017 HD 10 until this new update.
Click to expand...
Click to collapse
How did you find out - did you brick a tablet?
bibikalka said:
How did you find out - did you brick a tablet?
Click to expand...
Click to collapse
Si senor.
Well deserved, though. I was able to (successfully) inject su into 5.6.1.0 and flash it in FlashFire. I had also hashed the bootloader files and determined things had changed. I should have stopped there, but I wanted to see whether this is rootable from scratch. And it is. This was my second chance to stop, but no. I wanted to go back 5.6.0.1 (with adb sideload instead of FF because I wanted the old bootloader). As a result, I have a package to drop off tomorrow.
I wanted someone to take one for the team to figure out whether 5.6.1.0 is rootable; little did I know I was volunteering.
Thanks for your efforts with this, retyre!
Since the stakes on this seem a bit higher, I have some questions:
1) Can you confirm that flashing boot.img with FlashFire does not update the bootloader? In other words, if I flashed the boot.img from 5.6.1.0 and then decided to sideload 5.6.0.1, I'd be okay?
1a) If so, where does the evil bootloader-updating code come from? Is that the "preloader.bin" etc. files?
2) One of the steps is: "Mount [the converted system.new.dat] system.img in Ubuntu and inject the su binary and other su files". I have offline Kingo rooting files taken from an earlier root effort on this tablet. Since 5.6.1.0 is still rootable, would it also work to flash the "plain" (converter) system.img with Flashfire, then use the Kingo root method to get back root?
3) Would flashing the converted system.img with Flashfire wipe the existing /system partition? (IOW, if I already have System files like I like them, would I need to re-add any apps I made System apps with Link2SD — NovaLauncher, Xposed Installer, etc.?)
4) Regardless, it sounds like it wouldn't mess with /data at all, right? Meaning the bulk of my apps would stay in place?
Thanks in advance!
GamerOfRassilon said:
...
Click to expand...
Click to collapse
1) Yes. boot.img is not the bootloader.
1a) The "images" folder in the update .bin.
2) Yes, that will work. You will find my 5.6.1.0 system.img in the other thread.
3) Yes. You're dumping a raw image onto the partition. Move them to /data/app/ before you flash and make them system apps after you flash.
4) Yes.
Great! Thanks again for your help. I'll post my results in the other thread.
Is there any chance fire HD8 can be root?
retyre said:
Si senor.
As a result, I have a package to drop off tomorrow.
I wanted someone to take one for the team to figure out whether 5.6.1.0 is rootable; little did I know I was volunteering.
Click to expand...
Click to collapse
What does Brick look like on the device? Can it boot to fire animation, then stay there?
endleesss said:
What does Brick look like on the device? Can it boot to fire animation, then stay there?
Click to expand...
Click to collapse
Brick looks like, well, a brick. Nothing. No animation, no light, no sound, nothing, if you solder out and connect to the internal serial port when booting you can see the reason.
...
...
...
...
[ANTI-ROLLBACK] PL:2 LK:3
[ANTI-ROLLBACK] LK version mismatch!!
(turns off again)
I'm having a bit of a problem with root after the 5.6.1.0 update. I was previously rooted before and the tablet updated itself to the latest version.
I tried running Kingoroot again and the root seems to have worked. It shows success in the application that it installs. However, when opening supersu which was already installed from the previous time, it says that the binary was already occupied. I don't know how to let supersu take control of root again.
Any differences between these? 5.5.0.0/5.6.0.0/5.6.0.1
Should I bother downgrading to 5.5?
endleesss said:
Any differences between these? 5.5.0.0/5.6.0.0/5.6.0.1
Should I bother downgrading to 5.5?
Click to expand...
Click to collapse
Not many differences, but it's always good to prevent updating, in case bootloader exploits were found for older firmware.
Hello all,
I installed the latest update for my 8T KB2005 which is 11.0.8.13.KB05AA. I have unlocked the bootloader and would like to root it, however I'm not sure if it is possible to root from my current firmware version. Some root methods I read about say I need the stock image of my OS, but I believe my current firmware version is an incremental update and that will not work? I read it's possible to use payload dumper to get my image, but this doesn't work with incremental updates either. Maybe I am misunderstanding things. If someone could enlighten me, that would be greatly appreciated. Is is possible to root from my current firmware?
*Update: upon researching further, one possible solutions seems to be using the MSM tool to downgrade to an older version of OOS, then locally upgrading to 11.0.8.11.KB05AA, and then being my root process from there. I will attempt this, but if anyone knows if a root method from 11.0.8.13.KB05AA. I would like to know as well
joo14 said:
Hello all,
I installed the latest update for my 8T KB2005 which is 11.0.8.13.KB05AA. I have unlocked the bootloader and would like to root it, however I'm not sure if it is possible to root from my current firmware version. Some root methods I read about say I need the stock image of my OS, but I believe my current firmware version is an incremental update and that will not work? I read it's possible to use payload dumper to get my image, but this doesn't work with incremental updates either. Maybe I am misunderstanding things. If someone could enlighten me, that would be greatly appreciated. Is is possible to root from my current firmware?
*Update: upon researching further, one possible solutions seems to be using the MSM tool to downgrade to an older version of OOS, then locally upgrading to 11.0.8.11.KB05AA, and then being my root process from there. I will attempt this, but if anyone knows if a root method from 11.0.8.13.KB05AA. I would like to know as well
Click to expand...
Click to collapse
You don't need to use the MSM route. It's far simpler to patch the stock boot or use a patched stock boot.
@g96818 had kindly posted the boot image(s) you need in thread '[Guide] How to ROOT OnePlus8T (CN/IN/EU/US) KB2000,KB2001,KB2003,KB2005' https://forum.xda-developers.com/t/...00-kb2001-kb2003-kb2005.4178675/post-85165277
Its possible to use adb to pull the boot image and patch it in magisk. Then you use fastboot to boot from that image( not flash) and do direct install from magisk.
jwarrior319 said:
Its possible to use adb to pull the boot image and patch it in magisk. Then you use fastboot to boot from that image( not flash) and do direct install from magisk.
Click to expand...
Click to collapse
You can only do that if the phone is rooted. You need root access to pull a boot image from /dev/block/by-name/boot_[ab].
BillGoss said:
You can only do that if the phone is rooted. You need root access to pull a boot image from /dev/block/by-name/boot_[ab].
Click to expand...
Click to collapse
In a non root situation you can boot the semi working twrp posted here somewhere which gives a root adb shell via usb.
simple root instructions using the patched image I posted:
[Guide] How to ROOT OnePlus8T (CN/IN/EU/International) KB2000,KB2001,KB2003,KB2005
DISCLAIMER I have only tested this on my OnePlus8T Indian model - KB2001 Huge thanks to @topjohnwu for his magic. YOU NEED TO UNLOCK YOUR BOOTLOADER! In case you brick your device, use this unbrick guide If you get into a boot-loop by flashing...
forum.xda-developers.com
g96818 said:
simple root instructions using the patched image I posted:
[Guide] How to ROOT OnePlus8T (CN/IN/EU/International) KB2000,KB2001,KB2003,KB2005
DISCLAIMER I have only tested this on my OnePlus8T Indian model - KB2001 Huge thanks to @topjohnwu for his magic. YOU NEED TO UNLOCK YOUR BOOTLOADER! In case you brick your device, use this unbrick guide If you get into a boot-loop by flashing...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi g96818 Thank you for posting the 11.0.8.13 stock boot.img I was able to patch it in magisk and successfully root my phone! Thank you everyone for your fast responses. It was very much appreciated