Since there are some request from other fellow users, i decide to create a dedicated guide thread to show the process of UNLOCKING BOOTLOADER & ROOTING the Huawei Mate 10 (FOR MATE 10 LITE, CHECK BOTTOM OF THE POST)
Warning : Unlocking bootloader and rooting your phone come with a risk of bricked devices, bootlooping, loss of data, etc. I am not responsible for any harm that can happen during the process , ALWAYS MAKE BACKUP FIRST - use Huawei Backup App to backup your data to MicroSD, or get HiSuite ready to reflash your phone in case of brick situation happen
Pre-requisites :
1. "Enable OEM unlock" & "USB Debugging" option turned on from developer options
2. ADB & Fastboot installed on your WINDOWS 7 (YES, Win 10 has problem with Mate 10 Fastboot driver. except you know how to properly install the driver manually i would suggest you do this on Windows 7) - if you havent, search "Minimal ADB & fastboot" on XDA.
UPDATE : Windows 10 driver fix can be found HERE
3. Download FunkyHuawei Tool from : HERE - ALL CREDIT GOES TO FUNKYHUAWEI for PROVIDING THE TOOL
4. Valid Huawei Account logged in on your Mate 10
UNLOCKING BOOTLOADER
1. Go to : emui.huawei.com/en/plugin/unlock/index
2. Log in using your Huawei Account, make one if you dont have it yet
3. "Agree" to Huawei unlocking agreement presented
4. Input all neccessary values related to your device (the one you want to unlock) - IMEI, Model Number etc
5. Click "Commit"
6. You will get a pop up dialog, containing your unlock KEY. Save this key or screenshot the screen, you gonna need it to unlock your phone
7. Now, plug your phone to your PC. Assumed that you got USB debugging enabled, pop up will appear on your phone screen, asking whether you want to allow the PC to access your phone or not. Authorize the request
8. Fire up ADB on your CMD/Terminal. and type
Code:
adb devices
9. Your devices should listed on your adb window, if it isn't, either you didnt install the adb driver properly, or your usb port has problem
10. Now type
Code:
adb reboot bootloader
to reboot your phone to fastboot mode
11. Once the phone is booted up to the fastboot mode screen, type this in your CMD windows :
Code:
fastboot oem unlock [your UNLOCK KEY here]
- without the brackets
12. Confirmation dialog should appear on your phone screen, give you a warning about unlocking bootloader, just go with proceeding the process (YOU WILL LOSS YOUR USER DATA]
13. Once the unlocking process is finished, your phone will boot up to initial set up stage
14. Set up everything up until you can re-enable USB Debugging option in Developer Options (you can skip all account stuff, security and elses, you gonna do it again anyay after ROOTING)
15. Plug back your phone, and from your CMD Windows, retype this code :
Code:
adb reboot bootloader
16. Your phone will rebooted to FASTBOOT MODE again - now close your CMD Windows
ROOTING
1. Now launch "FHMate10Tool.exe" which you have downloaded from the prerequisites step
2. 5 Options will be presented, and the 1st is "Root your Mate 10"
3. Type "1" and hit ENTER
4. few more dialog and instructions will be given, and Rooting process will started
5. Once the process finished, your phone will booted back to initial set up screen with all USERDATA ERASED, but with SuperSU INSTALLED
CONGRATULATION, YOU HAVE ROOTED YOUR MATE 10
Addendum :
FOR MATE 10 LITE ONLY
Use same step to unlock bootloader.
Download TWRP from HERE and SuperSU from attached.
Place SuperSU to MicroSD and place TWRP img file to your directory in PC where fastboot and adb installed
Reboot to fastboot mode,
Execute this command :
Code:
fastboot boot twrp-mate10-lite.img
Your device will boot into temporary TWRP,
Go to Terminal in TWRP and type this :
Code:
echo "systemless = true" /data/.supersu
(Tick the bottom right corner)
go back to TWRP main menu and choose "Install"
Choose external storage and choose the Supersu.zip file and flash it,
Reboot System
Your device should be rooted.
Note : this method wont install TWRP to your device. You can install it using fastboot flash recovery twrp-mate10-lite.img command, but since the TWRP is still in beta stage, i do not recommend it.
Credit to Aonja for Mate 10 Lite TWRP img
Thanks for the info, I'm having difficulty getting a Windows 7 machine going, anyone know how to install the fastboot drivers manually on Windows 10?
Hello. I request that you don’t link directly to the google drive download page of the FunkyHuawei tool but rather if you want to link, link to the Reddit page that explains how to use it.
duraaraa said:
Hello. I request that you don’t link directly to the google drive download page of the FunkyHuawei tool but rather if you want to link, link to the Reddit page that explains how to use it.
Click to expand...
Click to collapse
Noted, can you give me latest link ?
I was using link that given to me by customer support after purchasing credit
otonieru said:
Noted, can you give me latest link ?
I was using link that given to me by customer support after purchasing credit
Click to expand...
Click to collapse
Check your PM for more info.
Basically the idea is, I might update it if a bug is found/fixed, so it should point to the latest version to avoid issues. If we have a direct link, that makes it difficult. Thanks
ballistykx said:
Thanks for the info, I'm having difficulty getting a Windows 7 machine going, anyone know how to install the fastboot drivers manually on Windows 10?
Click to expand...
Click to collapse
You need to disable driver signature verification on windows 10. And install the huawei driver afterward
duraaraa said:
Check your PM for more info.
Basically the idea is, I might update it if a bug is found/fixed, so it should point to the latest version to avoid issues. If we have a direct link, that makes it difficult. Thanks
Click to expand...
Click to collapse
Done
@otonieru , i have mate 10 standard,
- If i rooted the phone would i still receive OTA ? and if i received and installed them, would that brick my phone or just remove the root?
and if my phone ended up being bricked, is it easy to just flash back the rom of huawei using Hisuite ?
- is it easy to unroot the phone back to original, if i needed to use back the warranty? or maybe just flash the huawei rom.
- can the root be hidden ? like magisk ?
Thank you very much for this thread, it is a must ! <3
Two questions (sorry, I'm new to Huawei world...):
1. UNLOCKING BOOTLOADER does not void my warranty, right?
2. Will I loose root when install OTA update?
taddzio said:
Two questions (sorry, I'm new to Huawei world...):
1. UNLOCKING BOOTLOADER does not void my warranty, right?
2. Will I loose root when install OTA update?
Click to expand...
Click to collapse
1. Yes, it voids it in most cases, but might depend on your local Huawei region.
2. Yes, you lose root.
---------- Post added at 09:00 PM ---------- Previous post was at 08:58 PM ----------
Shady282 said:
@otonieru , i have mate 10 standard,
- If i rooted the phone would i still receive OTA ? and if i received and installed them, would that brick my phone or just remove the root?
and if my phone ended up being bricked, is it easy to just flash back the rom of huawei using Hisuite ?
- is it easy to unroot the phone back to original, if i needed to use back the warranty? or maybe just flash the huawei rom.
- can the root be hidden ? like magisk ?
Thank you very much for this thread, it is a must ! <3
Click to expand...
Click to collapse
If you root you will apparently still receive OTA. Receiving an OTA will unroot your phone, but should not brick it.
You can't unroot the phone back to original. Even if you relock the bootloader, it will show relocked, not locked. There are tools which you'd need to pay for which can help in that case.
The root cannot be hidden.
Anyone who roots, I urge you, be VERY VERY careful. Huawei phones are very finnicky, brick easily (the Mate 10 even more easily than previous versions), and there is no free way to restore them if they do brick. Even with paid methods,
it's not easy.
duraaraa said:
1. Yes, it voids it in most cases, but might depend on your local Huawei region.
2. Yes, you lose root.
---------- Post added at 09:00 PM ---------- Previous post was at 08:58 PM ----------
If you root you will apparently still receive OTA. Receiving an OTA will unroot your phone, but should not brick it.
You can't unroot the phone back to original. Even if you relock the bootloader, it will show relocked, not locked. There are tools which you'd need to pay for which can help in that case.
The root cannot be hidden.
Anyone who roots, I urge you, be VERY VERY careful. Huawei phones are very finnicky, brick easily (the Mate 10 even more easily than previous versions), and there is no free way to restore them if they do brick. Even with paid methods,
it's not easy.
Click to expand...
Click to collapse
Dunno but you people are scaring me of rooting huawei tho i have rooted and flashed so many roms on my LG and other phones...
I mean if i follow the procedures and use your tool wouldn't that just work ? or there are factors that may affect it
Shady282 said:
Dunno but you people are scaring me of rooting huawei tho i have rooted and flashed so many roms on my LG and other phones...
I mean if i follow the procedures and use your tool wouldn't that just work ? or there are factors that may affect it
Click to expand...
Click to collapse
The procedure is safe, but it's what you do with the root powers that could cause a brick. If you touch the wrong file on the phone, caput. In the worst case, the phone won't turn on, won't be recognized with USB, and can't be unbricked.
Obviously you're protected from doing that when you don't have root.
I've already lost two test devices to the symptoms described above.
So my opinion is, as the developer of the tool, root only if it's absolutely essential to you. And if you do root, only use the root privilege for things you absolutely must do, or things that have been tested on the phone and proven to be safe. Hopefully you won't brick it, but I need to put out this warning so I'm not blamed if someone does.
Any other down sides to unlocking bootloader and or rooting on this device eg apps auto removed, loss of camera functionality or codecs disabled etc as seen with other devices?
somemadcaaant said:
Any other down sides to unlocking bootloader and or rooting on this device eg apps auto removed, loss of camera functionality or codecs disabled etc as seen with other devices?
Click to expand...
Click to collapse
None as i may concern. Android pay wont work though, and some banking app as well. Since those app wont allow rooted phone.
But if you didnt use such an app. Or like me, have another phone for that, then its perfectly fine.
For me, there's more benefit / advantage come from rooting
Example :
1. Effective adblocking (not VPN solution)
2. Removing unneccessary stuff and app
3. Youtube without ads + background play
4. Better battery life (with appops, greenify, and my own GMSDoze)
5. Enabling VoLTE option
6. Audio MOD (gain, and better dual speaker)
7. etc
Fastboot driver fix
Use the fix from DC Unlocker for the fastboot driver under Windows 10
https://www.dc-unlocker.com/huawei-mate-10-fastboot-usb-device-not-recognised-fix
ElMartinoAT said:
Use the fix from DC Unlocker for the fastboot driver under Windows 10
https://www.dc-unlocker.com/huawei-mate-10-fastboot-usb-device-not-recognised-fix
Click to expand...
Click to collapse
Thx for heads up,
I'll include it in main post soon
otonieru said:
None as i may concern. Android pay wont work though, and some banking app as well. Since those app wont allow rooted phone.
But if you didnt use such an app. Or like me, have another phone for that, then its perfectly fine.
For me, there's more benefit / advantage come from rooting...
Click to expand...
Click to collapse
Good point about NFC pay methods, I do use those a lot.
I read a few people here having issues with their devices eg here, Lg devices has a similar issue with camera and missing appps, Samsung devices would lose the IR blaster after bootloader unlock.
somemadcaaant said:
Good point about NFC pay methods, I do use those a lot.
I read a few people here having issues with their devices eg here, Lg devices has a similar issue with camera and missing appps, Samsung devices would lose the IR blaster after bootloader unlock.
Click to expand...
Click to collapse
Am still using nfc payment, but not android pay.
Android pay is not even working in my country after all.
Nothing is lose after UBL, this UBL method is official from huawei anyway
It may be that after unlocking the bootloader the theme manager does not correctly apply the themes in emui?
Thanks in advance
sonice21 said:
It may be that after unlocking the bootloader the theme manager does not correctly apply the themes in emui?
Thanks in advance
Click to expand...
Click to collapse
Working just fine on mine. But experience might be vary.
Related
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!
shabydog said:
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!
Click to expand...
Click to collapse
AFAIK you will need a pc to 1)unlock your bootloader and 2)flash TWRP. After that the rest can be done locally. I also never used any toolkit. Making it easy is making it more dangerous IMHO.
Droidphilev said:
I also never used any toolkit. Making it easy is making it more dangerous IMHO.
Click to expand...
Click to collapse
Second that.
shabydog said:
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Click to expand...
Click to collapse
So at least once you need to connect your phone to a desktop computer. It can be practically running anything, within reason of course: Wiindows. Mac OSX, Linux (almost any distro).
You need to unlock your bootloader with one command, but a warning here: Unlocking the bootloader will erase everything from your phone..
Then you need to install a custom recovery, preferably TWRP. After that everything can be done from the phone itself. Well at least until you soft brick it somehow, then you'll might have to use the PC again.
Also two things:
1. No OTAs for rooted phones
2. Don't lock your bootloader if you want to mess with it, because with a locked bootloader, and Enable OEM Unlocking set to off, and without TWRP, if you soft brick it accidentally, you are boned.
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use?
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
And i really prefer to do it on the device and not by ADB commands.
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!
shabydog said:
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!
Click to expand...
Click to collapse
Well, you still will have to unlock it, if you want root, or want to flash a custom recovery.
Sent from my Nexus 6 running cyosp using Tapatalk
shabydog said:
......I really don't like the issue of trying to set the drivers of fastboot/google and so on!
Click to expand...
Click to collapse
Than do not 'root' your phone.
hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:
simms22 said:
hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:
Click to expand...
Click to collapse
Ha ha, or I don't want my birthday to be on the day I was born every year ?
I can recommend the NTRT, the Nexus Telepathic Rooting Tools.
OK.
I want to do that with a toolkit, only bcs it install the drivers.
What Is the most recommended and easiest to use?
I do looking for the 1 click do all.
Does NTRT do that?
Thank you all.
we are eventually goung to have a "my n6 is bricked, how do i fix it with one click" thread here. seriously though, thats what happens when you use toolkits, but do no real research about modding your device.
Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Sent from my Nexus 6 using Tapatalk
shabydog said:
Could anybody guide me through the steps, if needed?
Click to expand...
Click to collapse
<prev> step <next>
simms22 said:
seriously though, thats what happens when you use toolkits, but do no real research about modding your device.
Click to expand...
Click to collapse
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
wtherrell said:
Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Click to expand...
Click to collapse
It is fairly enough to read directions and slowly-slowly.
NLBeev said:
<prev> step <next>
Click to expand...
Click to collapse
Thanks!
==========================================================
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?
shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
Click to expand...
Click to collapse
i agree with you. if there is somebody who knows the ins and outs already, a one click root would be great. and there will be. problem is that marshmallow just came out, and a few things have changed, like like yoe also need a custom kernel to have root on marshmallow.
shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
It is fairly enough to read directions and slowly-slowly.
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?
Click to expand...
Click to collapse
There is a reason you're pushing this topic, and I'm quite sure it's because you would feel safer, if there was a tool that did the scary things instead of you. Well, there's no such tool. If you were willing to search XDA, you would find out that the first two weeks after Marshmallow came out were about people bricking their Nexus 6s with toolkits. Then the toolkit got updated and suddenly it knew that is has to flash a modified boot.img too for the root not to brick the phone. But for two weeks it didn't know, because it wasn't necessary for Lollipop. And it will only work until the next security update comes out. And that's once a month.
Meanwhile those who were willing to use the search function, and learned the five minute procedure, were able to update their rooted phones to the next security update and were able to root it as soon as the new modified boot image came out.
And this above is not something somebody will put in a help, or instructions for future updates.
Actually, this is my first time and I was able to do it pretty easily.
fastboot devices
fastboot oem unlock
my bootloader was unlocked within 30 seconds of turning it on.
then, you can easily root via CF Auto root. Just put it into fastboot then doubleclick on the windows, then root, etc....
or.............go into fastboot flash recovery twrpxxxx.img, then it always offers to run SuperSU, and you get custom recovery and root at the same time, etc......
actually the biggest pain is unlocking the bootloader. My Galaxy S4 already was unlocked, so all I did was use goomanager, flash TWRP which always offers to run SuperSU if you don't have it.
Pretty easy, I did unlock bootloader, root, and custom recovery in 10 min.
---------- Post added at 01:48 AM ---------- Previous post was at 01:44 AM ----------
............................Then I got sick of stock Google's ROM in 15 min and wiped it and put a custom ROM instead.
Thank you all so much...
@mikeprius
Thank you so much for the info'!
But, could you plz write more details? such as:
1. How did you installed the drivers? (from my expirience, many times the pc dosent install this easily).
I just need the Google oem driver and that's it?
2. When drivers was set - did you made anything in your phones settings? Which?
3. What did you had to do before pushing the files? (Like...put all the files in the same folder? *which files?)
4. And then entered to fastboot mode and typed in these commands in pc:
fastboot devices
fastboot oem unlock
Regarding your last sentence ("or...."):
If i just flash the recovery via fastbot mode I can enter to twrp recovery and it offers to flash the SuperSU?
Sounds to me the best option.
Thanks!
1. The drivers were set from a previous device, so I didn't have to set them, but they can be downloaded and set though.
2. You need to enable developer options and select OEM unlock and USB debugging.
3. I didn't push the files, I just had them on my computer and ran fastboot commands.
4. Those commands are to unlock the bootloader.
There are a lot of different ways to do the same thing (Root, custom recovery, unlock bootloader)
1. Run CF Auto Root on a locked bootloader. It will unlock it automatically (Chainfire has it set that way), root, then download Flashify app and flash the latest img of TWRP.
2. Run fastboot commands to manually unlock the bootloader, flash TWRP, then use TWRP's SuperSU which will root it.
3. Run fastboot commands to unlock bootloader, run CF Autoroot which will root and load SuperSU, then flash TWRP via Flashify or fastboot.
There are many different ways to do the same thing. I actually just googled youtube videos and watched them.
TWRP has SuperSU and root built in. TWRP knows if you don't have it and offers to load it for you.
I went the scenic route just because, but presumably you can achieve all (3) using Option #1 without having to deal with fastboot, adb, etc.....Chainfire's script runs automatically.
I realy try to help people but users that run into problems because of the usage of tookits (and innability to solve problems and/or even lack the most basic knowledge needed) should ask the toolkit dev. for support imo, and not boughter users that have invested time and effort to gain that knowledge to clean up their mess. Period
When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting. I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging.
jwils1236 said:
When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting and wouldn't have bought it if I would have known (or at least not updated to Pie). I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging/impossible. Any help would be appreciated and if a solution is brought to light, I am gladly offering $. This could easily be considered a device with best hardware and when rooted, access to best software -- I didn't see significant enough improvements in Note 9 and figured by now the support from XDA community would be abundant for the exynos processor. Turning out ridiculous waste of money if I can't root it (already purchased silver carbon fiber skin, 256 GB Samsung Evo Select SD card, attachable portable wireless charging pack, etc.). Please help!
Click to expand...
Click to collapse
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.
Its just easy step
Things u needed before proceed
* SD card
*Magisk latest version
*Odin
* Twrp zip file
1. Reflash ur device with proper firmware
2. After done go download mode and flash Twrp zip on odin. After done reboot ur device to Twrp again
3. After boot up to Twrp go to Wipe and do a factory restore . After this done u must install Magisk or u will get official binary only after reboot to system
4. After all the step are followed u are good to go. Cheers
stonedpsycho said:
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.
Click to expand...
Click to collapse
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
Also, for anyone reading this with the same issue, extracting the boot image from stock firmware (can be done through command prompt/terminal dump or by extracting from stock firmware -- AP Odin file) and patching with Magisk will not flash or work/give root access either unless this device is fully unlocked -- OEM unlock doesn't matter, if RMM still says "Prenormal" in download mode.
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I am quite sure it is still rootable on bootloader 6, so updating would be fine.
The trick to get the OEM toggle is a bit hit and miss, the guide below is the method that has had a higher success rate for me, if followed exacty as written.
https://www.google.com/amp/s/www.xd...-samsung-galaxy-s8-samsung-galaxy-note-8/amp/
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I ended up using Chimera Tool to bypass RMM state. Worked instantly. This seems to be a common issue for many Samsung devices, at least on Pie. Not sure there is an alternative solution, currently. Only one I could find for my device.
Notes: This trips KNOX so you will void your warranty, read all the steps carefully before beginning, flashing can be dangerous if you do it wrong. Don't blame me if you brick your device.
Backup all of your data and settings before starting as you will need to reset to factory defaults during this process.
With that being said, the process is relatively straightforward and easy.
PS: my device is the A908B, there is also an A908N if anyone wants to test on that be my guest.
Needed:
ADB
SamFirm
Odin
Magisk Manager
Step 1 - Downloading your firmware.
Go to SamMobile SM-A908B
Find the correct firmware for your device according to country and operator.
Note: You can use generic country firmware instead, this will remove carrier added software and limitations but may remove features and disables OTA updates.
Note the 'product code'.
Now open SamFirm.
Type SM-A908B for model
In the region box type the product code you noted earlier.
Click Check Updates.
When it has found the firmware, make sure decrypt automatically is checked and then click download rom.
The firmware is around 4gb.
Part 2 - Unlocking the Bootloader
Go to settings > about phone > software information. Hit build number a bunch of times until you activate developer options.
Go back to settings > developer options
Enable OEM unlocking
Enable USB debugging
Turn off the phone
Hold volume up and volume down whilst inserting the USB cable
This should take you to the bootloader unlock screen.
Long press Volume up to unlock the bootloader.
Part 3 - Obtaining root
After SamFirm finished downloading the rom it should have extracted it into 5 tar files.
Copy the tar file beginning with AP to your device.
Download Magisk Manager on the device and install.
Press Install on Magisk Manager
Confirm the Install
Select the option 'select and patch file', then locate the APdjkfgrsdkfhgkjrg.tar.md5 on your device and select it.
Magisk will then patch the file and dump the patched version to your phone.
Copy the patched.tar to your PC
Reboot phone into download mode
Open Odin
For BL use the BL.tar.md5 file from stock firmware
For AP use the patched.tar file
For CP use the CP.tar.md5 file from stock firmware
For CSC use the CSC.tar.md5 file from stock firmware (not the CSC_HOME)
Press Start and wait for it to flash
After flashing, the phone will reset.
After initial setup, install magisk manager again.
Remove the USB cable and turn off the phone.
Turn on the phone by holding volume up and power, let go when you see the bootloader warning.
Open Magisk Manager Click Install.
Phone is now rooted.
Note: Powering on the device normally will disable root, you must hold volume up to power on the device to activate root.
Awesome job thanks a lot
Going to put a few hours into compiling twrp tonight but this might take me forever, I'm really busy with work and I got 2 kids too so free time is scarce. So feel free to have a go at it yourself.
After root activation with the volume button start up will the root persist? Can the device be restarted without any hidden key?
Thank you
Yes the root persists, but every time you turn the phone off and back on again you will have to hold up to activate the root. Resetting the phone while root is enabled does not disable it though iirc.
More work done on twrp last night, nearly ready to attempt compiling.
Edit: So I made a device tree and compiled twrp fine. Unfortunately it needs a custom kernel to be able to boot. Working on this now.
Any further progress??
No not really. I need to reach out to the twrp Devs of the S10 and see what modifications they did to theirs, but super busy at the moment. Sorry.
johnoponi said:
Any further progress??
Click to expand...
Click to collapse
Ok so I made a lot of progress since last post. I'm compiling the kernel as I type. But the process takes a long time. If we are lucky it will boot twrp straight away if not I'll keep at it until I manage.
triggz881 said:
Ok so I made a lot of progress since last post. I'm compiling the kernel as I type. But the process takes a long time. If we are lucky it will boot twrp straight away if not I'll keep at it until I manage.
Click to expand...
Click to collapse
Are you still trying?
Failure on Model SM-A9080 (China Version)
Today I did this on model SM-A9080 but unluckily failed, and the OS could not be loaded, with boot loop on the phone.
Really the specified TWRP should be developed.
triggz881 said:
Ok so I made a lot of progress since last post. I'm compiling the kernel as I type. But the process takes a long time. If we are lucky it will boot twrp straight away if not I'll keep at it until I manage.
Click to expand...
Click to collapse
Hey - did you manage to get anywhere with this? If you'd like help, i'd be happy to get stuck in. Could you put the code on Github?
Hello,
I tried to root my phone today, and I followed every step exactly, but now I am stuck in a Boot Loop, after the Step of Flashing. Can someone help, or knows why this happened? Thank you.
---------- Post added at 07:48 PM ---------- Previous post was at 07:03 PM ----------
Okay I fixed it myself. The Problem was, I only Flashed the BL File. After that I flashed the other files one by one, did a Factory Reset in Recovery mode and now it worked! I even have root now.
Do we have a custom rom yet? Can't stand the samsung rom or whatever its called.
xijaw said:
Do we have a custom rom yet? Can't stand the samsung rom or whatever its called.
Click to expand...
Click to collapse
So why did you buy a Samsung.
Srbija2012 said:
So why did you buy a Samsung.
Click to expand...
Click to collapse
Lmao, true. He could of easily went for one plus etc..
And bull****, Samsung ui is definitely top it's really nice.. just the notifications could be improved
Srbija2012 said:
So why did you buy a Samsung.
Click to expand...
Click to collapse
I live in Australia and here we don't have a market like Europe and India. We only have couple of brands- Apple and Samsung.
---------- Post added at 01:31 PM ---------- Previous post was at 01:30 PM ----------
underdog_656 said:
Lmao, true. He could of easily went for one plus etc..
And bull****, Samsung ui is definitely top it's really nice.. just the notifications could be improved
Click to expand...
Click to collapse
Lets stick to the topic and get the damn custom rom built. Aren't there any devs who willing to take A90 as a project ?
can you get the ctsprofile pass in the magisk manager？
Steveee101 said:
Hey - did you manage to get anywhere with this? If you'd like help, i'd be happy to get stuck in. Could you put the code on Github?
Click to expand...
Click to collapse
can i ask you whather you can get the cts profile pass or false or not after you root by magisk？
Hello please can someone help me root this phone, i have followed the steps but i just seem to be missing something so can someone take me through this step by step for a dumb person like myself lol?
At first i was struggling with part one of this tutorial but once i updated samfirm i was able to download it without a problem. moving over to the last step which is using odin to do its thing with the tar files and upon finishing where it should reboot it is stuck into a boot loop saying "this phone is not running samsungs offical software", i am not sure what i am missing and i am able to fix the phone without any problems but no root is achieved
Hello. May I ask about the progress on TWRP for this phone?
Hi all,
I am trying to relock the bootloader on 3T, with no success. I want to do it because of too many apps nagging me or not working with unlocked bootloader
here's what I did to unlock in the past and relock:
unlocking:
- enable dev options, enable oem unlocking & usb debugging
- flashed TWRP & fastboot oem unlock from command line (don't remember which I did first)
- got my phone wiped which was an an unexpected surprise!
- bootloader unlocked, the fist of those lovely warning screens telling me so
- tried to root without success, so no custom ROMs for me
- lived with it like this for a while, too many apps telling me they won't work, decided to relock
- got latest stock ROM, flashed it via TWRP, wiped, tried to fastboot oem lock ==> success reported by CLI, BUT device still unlocked
- flashed just the 3t recovery img, wiped, fastboot oem lock ==> success reported by CLI, BUT device still unlocked
- tried the qualcomm unbrick tool after installing the recommended drivers, can't have it see my device maybe because it's not bricked or maybe some other reason, I don't know. it doesn't show up in the app. Will uninstall and reactivate driver signature checks soon unless someone explains me how to make the bloody phone show up ...
So at this moment I have a many times-wiped phone with latest 9.0.4 stock ROM whose bootloader won't lock back. I am quite at a loss. I haven't tried any magisk or similat, SuperSU at the time told me I am not rooted.
I am tearing out the few hairs I have left. Any help for this poor family man so that he may not be allowed to walk in darkness? (quote from Uninvited). Thanks
Why don't you use Magisk hide to hide root/unlock status to those apps instead of loosing root/adaway and more?
pitrus- said:
Why don't you use Magisk hide to hide root/unlock status to those apps instead of loosing root/adaway and more?
Click to expand...
Click to collapse
I have never investigated Magisk, I think I installed it at the tima but there was some problem with it so I uninstalled it and didn't think much more about it. The problem is, my phone is not rooted (even though I tried it failed, I unlocked the bootloader to root it in the first place but was not successful), only OEM unblocked. So, so to say, I'm stuck in the worst of the possible worlds except for a bricked device. unlocked with no apparent way to relock it, and not rooted.
I feel like my phone is in some strange state where the normal procedures do not work. If I could at least figure out what's wrong with the rooting, I could go the full way AND then, in case use Magisk. but at the moment I feel like there is a need to put the phone in a known definite state whichever it is and work from there. I'd be happy to revert to stock and locked and then redo everything when needed in the future.
How could I troubleshoot further or get to such a "known state"? many thanks
The thing you did wrong was using the outdated SuperSU method of rooting which is not supported anymore. You should just flash the latest Magisk zip of their github page and then you will have root with the possibility of hiding it for bank apps and others.
https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
pitrus- said:
The thing you did wrong was using the outdated SuperSU method of rooting which is not supported anymore. You should just flash the latest Magisk zip of their github page and then you will have root with the possibility of hiding it for bank apps and others.
https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
Click to expand...
Click to collapse
Thanks pitrus, I'll have a look at it tomorrow and will update with what happened
MassiB said:
Thanks pitrus, I'll have a look at it tomorrow and will update with what happened
Click to expand...
Click to collapse
Hi, update. I installed Magisk but, seeing that it had a way to put the phone in EDL mode, instead of going full root I decided to go the other way around and try to make my phone as stock as possible and reserve the experiments to an unit other than my primary. So I used the Qualcomm "unbrick" tool, and was able to flash the OxygenOS version that came with it - a rather old Android 6 whose networking (wifi, mobile...) wasn't working. But an adb sideload of the latest version after having put the phone in recovery mode allowed me to restore the networking and to update to the last supported version.
Magisk made the difference in getting me out of the spot. Thanks for bringing it to my attention!
i just want to say, i used my device for long, i dont wanna wipe my data but i want to root it. is that possible?
THX in advance
If your bootloader isn't unlocked then doing so will wipe data. If it is unlocked you can use the latest version of Magisk. Following this guide:
Magisk Root without custom Recovery and without losing Encryption
So, I unlocked my bootloader a couple of days ago, but when I got into the point of flashing TWRP, I realized that there is no custom recovery that supports device encryption. For that reason I didn't root my phone but there is a way around...
forum.xda-developers.com
Obviously you will need the correct boot.img file relevant to your specific Redmi Note 10s device extracted from an official rom.
You'll also need to enable usb debugging in the hidden developer options and configure ADB properly on your computer.
If you don't use the correct rom for your device it will get stuck in a bootloop, or just won't boot at all, requiring a hard reset and loss of all data.
There are guides for all these things on the XDA forums.
If you haven't heard of these things before, this is your main phone, or you aren't confident in your abilities then I don't recommend doing it, but it's your choice just don't blame others if something goes wrong.
stuntdouble said:
You can use the latest version of Magisk. Following this guide:
Magisk Root without custom Recovery and without losing Encryption
So, I unlocked my bootloader a couple of days ago, but when I got into the point of flashing TWRP, I realized that there is no custom recovery that supports device encryption. For that reason I didn't root my phone but there is a way around...
forum.xda-developers.com
Obviously you will need the correct boot.img file relevant to your specific Redmi Note 10s device extracted from an official rom.
You'll also need to enable usb debugging in the hidden developer options and configure ADB properly on your computer.
If you don't use the correct rom for your device it will get stuck in a bootloop, or just won't boot at all, requiring a hard reset and loss of all data.
There are guides for all these things on the XDA forums.
If you haven't heard of these things before, this is your main phone, or you aren't confident in your abilities then I don't recommend doing it, but it's your choice just don't blame others if something goes wrong.
Click to expand...
Click to collapse
okay! i think i dont wanna root it then if you give advice to not do so
Sorry I missed out the part about the bootloader which is important and edited the post above so please re-read.
Yeah if unsure then just don't do it as you could end up losing everything very easily.
KerbMario said:
i just want to say, i used my device for long, i dont wanna wipe my data but i want to root it. is that possible?
THX in advance
Click to expand...
Click to collapse
technically there is a way to unlock the bootloader without losing data but magisk is kinda fuc*ed up on MIUI, and it can cause the phone to not boot
J6idot said:
technically there is a way to unlock the bootloader without losing data but magisk is kinda fuc*ed up on MIUI, and it can cause the phone to not boot
Click to expand...
Click to collapse
isnt unlocking bootloader an option in developer mode options?
KerbMario said:
isnt unlocking bootloader an option in developer mode options?
Click to expand...
Click to collapse
it's not as simple as that, you can register to unlock your bootloader by xiaomi from the dev options, but you still have to do the unlock though your pc with the miunlock program logged into your account. This takes 7 days to verify and the moment you do it it wipes your data.
This is the official way of unlocking your bootloader and being able to do with the device whatever you want.
There is an alternative unofficial way of doing it and that method claims to not delete data on your device, but I have no idea how well that method works since it seems to rely on some sort of workaround. here's a link to the post about that method, I just did mine the official way and copied my files back and redownloaded the apps.
[Rosemary] Instant Unlock Bootloader with no data wipe
Hi I want to share with you guys how to unlock Bootloader without waiting dan best of part is your data will no wiped I am not the programmer of this software, I just want to shares All credit goes to developer: Tapin Recovery Installer Here's...
forum.xda-developers.com
also if you do decide to unlock your bootloader one way or the other, I recommend the following Kernel if you want a less throttled gaming experience.
https://forum.xda-developers.com/t/shared-kernel-beta-genom-r-kernel.4342549/
Cryptonite26 said:
it's not as simple as that, you can register to unlock your bootloader by xiaomi from the dev options, but you still have to do the unlock though your pc with the miunlock program logged into your account. This takes 7 days to verify and the moment you do it it wipes your data.
This is the official way of unlocking your bootloader and being able to do with the device whatever you want.
There is an alternative unofficial way of doing it and that method claims to not delete data on your device, but I have no idea how well that method works since it seems to rely on some sort of workaround. here's a link to the post about that method, I just did mine the official way and copied my files back and redownloaded the apps.
[Rosemary] Instant Unlock Bootloader with no data wipe
Hi I want to share with you guys how to unlock Bootloader without waiting dan best of part is your data will no wiped I am not the programmer of this software, I just want to shares All credit goes to developer: Tapin Recovery Installer Here's...
forum.xda-developers.com
also if you do decide to unlock your bootloader one way or the other, I recommend the following Kernel if you want a less throttled gaming experience.
https://forum.xda-developers.com/t/shared-kernel-beta-genom-r-kernel.4342549/
Click to expand...
Click to collapse
+1 this works
Yes its possible to not wipe data or lose it during the process at this point in time.
Just this past week (I'm new to redmi phones ) did the same process for the note 10s and note 9.
The issue with bootloader unLocking (which normally means a data wipe) is negated with mtkclient.
A Data backup is just a good standard practice but understanding the procedures posted before and following them correctly should give no issue.
You can root it by using termux too.
To root an Android phone using Termux, follow these steps:
Install Termux app from the Google Play Store
Open Termux and run pkg install git to install Git
Run git clone https://github.com/Magisk-Modules-Repo/termux-root.git to clone the root repository
Change directory with cd termux-root
Run sh install.sh to install the root tool
Restart the phone and the phone should be rooted.
Note: Rooting a phone voids its warranty and can potentially harm the device if not done carefully. Proceed at your own risk.