Related
To start off everyone should know that messing with your phone can brick it!! You should not mess with your phone if you are unsure of what you are doing. You will get this (or a similar) warning while following the unlock instructions from Motorola as well. Following these instructions also voids your warranty!
I only use Motorola's official firmware for the moment and these instructions were originally performed on the ASA14 firmware. They should be useful for previous versions of the firmware but I will not be testing those. These instructions may not work for releases after ASA14.
While following this guide you need to be on a Windows PC with the administrator account or an account with administrative privileges. If you do not have these privileges you will likely run into issues. All instructions are written for a PC running Windows 7 as that is the only PC I have access to. If anyone has any instructions using a different version of Windows I will gladly add them in.
Windows commands:
dir - Lists all directories (folders) and files of the directory you are currently in.
cd {directory name} - Moves into the named directory. The directory names are case-sensitive.
cd.. - Moves to the directory before the one you are currently in. For instance if you are in C:\Users\Public and perform cd.. you will move to C:\Users
{Unlocking the Bootloader}
I'm writing this pretty late and formatting takes forever so I'll update this section later with my own set of instructions. For now use this guide which I plan on using for inspiration since I can't really repeat the unlock process.
Below is my work in progress. This is incomplete and will be unhidden when it is completed.
Updated Unlock
1. Download the Android SDK
2. Unzip the file. If you don't have a program to unzip the file 7-zip is great.
3. Move the unzipped folder to a location that is easy to locate. For me I put this in "Documents".
4. Rename the folder to something shorter, that way it's easier to type in later. "ADT" is easy to use and remember.
5. Download the drivers for the phone.
6. Open "MotorolaDeviceManager_2.3.9.exe" and install the drivers.
7. Go here
8. Click "PROCEED ANYWAY"
9. Register an account with Motorola.
10. Go to Start > All Programs > Accessories
11. Open “Command Prompt”
12. Use the cd commands to navigate to your “platform-tools” folder.
13. Turn off your phone (power button + volume down if you can't select any options to turn off the phone)
14. Turn it back on using the power button + volume up + volume down combination
15. Select “Fastboot” (volume down cycles through, volume up selects the option)
16. Connect your phone to your PC.
17. Type "fastboot oem get_unlock_data" in Command Prompt.
{Installing a New Recovery}
For the recovery we’re going to install the Photon Q Open Recovery. Every recovery has its advantages and disadvantages. This one is familiar to me and so I chose it for this guide.
1. Download the recovery image
2. Place the image in the Android SDK “platform-tools” folder which is in the "sdk" folder
3. Turn off your phone (power button + volume down if you can't select any options to turn off the phone)
4. Turn it back on using the power button + volume up + volume down combination
5. Select “Fastboot” (volume down cycles through, volume up selects the option)
6. Connect your phone to your PC
7. Go to Start > All Programs > Accessories
8. Right-click “Command Prompt”
9. Click “Run as administrator”
10. Use the cd commands to navigate to your “platform-tools” folder (Unfortunately I cannot tell you where this is as each computer will have it placed differently)
11. Type in “fasboot flash recovery open_recovery_206_05_06_2013.img”
{Getting Root}
1. Download the zip file for rooting
2. Place the file in the root (ie. not within a folder) of your phone’s SD card
3. Turn your phone off
4. Turn it back on using the power button + volume up + volume down combination
5. Select “Recovery” (volume down cycles through, volume up selects the option)
6. Select “Apply Update” (In recovery the the controls change. Volume up and volume down move in the list, the camera button at the bottom right of the device selects.)
7. Select the file you placed on your SD card from step 2
8. Wait for the update to apply, it should say that it finished successfully
9. Select “Reboot Phone”
Credit for all of this goes to their respective creators. I will name them all by name at a later date, but the credit can also be found following the linked material. Hopefully that doesn't bother the creators, writers, or hosts.
The Open Recovery port was done by Skrilax_CZ.
SuperSU is hosted by shabbypenguin and developed by Chainfire.
Please don't re-post this how-to without crediting. I've had it happen before and it was a huge disincentive for updating and making new guides.
section "{Installing a New Bootloader}" and "1. Download the bootloader image" below it are actually reffering to recovery (probably the best one out there). Not a bootloader.
Bootloader boots the system. Depending on keys pressed during boot (if any, or if instructed by commands) it can boot to bootloader menu, recovery, system (android)...
Ah, thanks. I would have known that if I rechecked but I haven't had time to.
Edit:
While I was editing I noticed I referenced it as recovery multiple times and was switching between the two as the guide went on!
unlocking bootloader failed
ok so i got the device id went to the motorola site said it was good got the unlock key did the step and typed it in the command prompt and it says
(bootloader) password incorrect
(bootloader) oem unlock failure
FAILED <remote failure>
sorry if this is a noob question usualy dont post first time last time i rooted a fone was on an evo 4g so never really messed with command prompts and unlock keys to much i repeted the whole process 3 times already and i still get the same message
edit: nvm got it to work hahaha forgot to capslock the letter in the key thanks for the write up man
demi_god_619 said:
ok so i got the device id went to the motorola site said it was good got the unlock key did the step and typed it in the command prompt and it says
(bootloader) password incorrect
(bootloader) oem unlock failure
FAILED <remote failure>
sorry if this is a noob question usualy dont post first time last time i rooted a fone was on an evo 4g so never really messed with command prompts and unlock keys to much i repeted the whole process 3 times already and i still get the same message
edit: nvm got it to work hahaha forgot to capslock the letter in the key thanks for the write up man
Click to expand...
Click to collapse
Yeah, unfortunately there's are a few points where unlocking get's confusing. I had to enter my stuff from the command prompt to Motorola's site like 5 times before I figured out where the copy/paste had spaces. It took me a while to figure out I had pasted an extra space at the end. This was the first phone for Motorola's bootloader unlock plan so I'm hoping they improve on it for their future phones.
The OP is updated with some more color-coding, updated credits (though I didn't try to get everyone just yet), and changed the link to an updated SuperSU. This should work on the Jellybean update though I won't know for sure unless someone confirms it in this thread. I've taken a break from messing with my personal phone for a while so I won't be checking the boards as often but I'll still be checking every few days.
Solust said:
The OP is updated with some more color-coding, updated credits (though I didn't try to get everyone just yet), and changed the link to an updated SuperSU. This should work on the Jellybean update though I won't know for sure unless someone confirms it in this thread. I've taken a break from messing with my personal phone for a while so I won't be checking the boards as often but I'll still be checking every few days.
Click to expand...
Click to collapse
FYI, if you install TWRP it will detect whether you have root or not and offer to install it for you.
Simplifies the guide a bit, and IMHO TWRP is a great recovery - all touch based, no more mashing the volume keys .
Nicely done regardless.
I noticed I was missing a step in the {Getting Root} section. It was an implied step but I added it for clarity.
I also had forgotten to mention that once you get into recovery the buttons used to control things change slightly. You can use the keyboard in addition to the device buttons.
Thanks for the How-to!:good: I was wondering if you would mind if I gave you or added some instructions for Linux users?
xaelith said:
Thanks for the How-to!:good: I was wondering if you would mind if I gave you or added some instructions for Linux users?
Click to expand...
Click to collapse
Yeah that would be fine. PM me the instructions and I'll test them out on my Linux partition. It'll probably take a few days as I have things coming up.
I've updated the links in the OP to Open Recovery 2.06 (changing the name in the command accordingly) and started writing my own set of bootloader unlock steps. They aren't complete yet but if someone is having troubles understanding the first few steps of the linked article mine should be broken down to be a bit easier to digest.
Solust said:
I've updated the links in the OP to Open Recovery 2.06 (changing the name in the command accordingly) and started writing my own set of bootloader unlock steps. They aren't complete yet but if someone is having troubles understanding the first few steps of the linked article mine should be broken down to be a bit easier to digest.
Click to expand...
Click to collapse
Open Recovery is on version 2.09 now. Has anyone tried it? I tried it using the posted steps but I got the same result as when I tried cmwrecovery, the phone doesn't boot to it, it boots to an image of the android guy on his back with his belly open and a red exclamation point hovering over him. Any advise? It's a Photon Q using Android version 4.1.2 nand I have successfully unlocked the bootloader.
I never changed versions because most of the updates target Kit-Kat based custom ROMs. Make sure your phone is NOT plugged in when you try to get into recovery. If it doesn't work when not attached to anything re-download the recovery and try installing again.
Entomology onsaboo
Solust said:
I never changed versions because most of the updates target Kit-Kat based custom ROMs. Make sure your phone is NOT plugged in when you try to get into recovery. If it doesn't work when not attached to anything re-download the recovery and try installing again.
Click to expand...
Click to collapse
I have tried to get into recovery both plugged in and not plugged in. I tried downloading and re downloading both CMWrecovery and open recovery 2.09 both.
Are you saying Open Recovery 2.09 is targeted at Kit-Kat custom ROMs and won't work on my phone? Should I try the version in your OP?
It should work in theory regardless of Kit-Kat, but if you've already tried all of that then give the older version a shot. I really post only what I know and have tried in the original post. It's beyond the scope of my thread though so you may have better luck asking in the recovery threads if you can't get any version to work. I'm on my phone for the time being or I would link you to the appropriate threads myself.
Solust said:
It should work in theory regardless of Kit-Kat, but if you've already tried all of that then give the older version a shot. I really post only what I know and have tried in the original post. It's beyond the scope of my thread though so you may have better luck asking in the recovery threads if you can't get any version to work. I'm on my phone for the time being or I would link you to the appropriate threads myself.
Click to expand...
Click to collapse
I couldn't fine a copy of the older version anywhere.
I understand, and I thank you for your help.
Solust said:
To start off everyone should know that messing with your phone can brick it!! You should not mess with your phone if you are unsure of what you are doing. You will get this (or a similar) warning while following the unlock instructions from Motorola as well. Following these instructions also voids your warranty!
I only use Motorola's official firmware for the moment and these instructions were originally performed on the ASA14 firmware. They should be useful for previous versions of the firmware but I will not be testing those. These instructions may not work for releases after ASA14.
While following this guide you need to be on a Windows PC with the administrator account or an account with administrative privileges. If you do not have these privileges you will likely run into issues. All instructions are written for a PC running Windows 7 as that is the only PC I have access to. If anyone has any instructions using a different version of Windows I will gladly add them in.
Windows commands:
dir - Lists all directories (folders) and files of the directory you are currently in.
cd {directory name} - Moves into the named directory. The directory names are case-sensitive.
cd.. - Moves to the directory before the one you are currently in. For instance if you are in C:\Users\Public and perform cd.. you will move to C:\Users
{Unlocking the Bootloader}
I'm writing this pretty late and formatting takes forever so I'll update this section later with my own set of instructions. For now use this guide which I plan on using for inspiration since I can't really repeat the unlock process.
Below is my work in progress. This is incomplete and will be unhidden when it is completed.
Updated Unlock
1. Download the Android SDK
2. Unzip the file. If you don't have a program to unzip the file 7-zip is great.
3. Move the unzipped folder to a location that is easy to locate. For me I put this in "Documents".
4. Rename the folder to something shorter, that way it's easier to type in later. "ADT" is easy to use and remember.
5. Download the drivers for the phone.
6. Open "MotorolaDeviceManager_2.3.9.exe" and install the drivers.
7. Go here
8. Click "PROCEED ANYWAY"
9. Register an account with Motorola.
10. Go to Start > All Programs > Accessories
11. Open “Command Prompt”
12. Use the cd commands to navigate to your “platform-tools” folder.
13. Turn off your phone (power button + volume down if you can't select any options to turn off the phone)
14. Turn it back on using the power button + volume up + volume down combination
15. Select “Fastboot” (volume down cycles through, volume up selects the option)
16. Connect your phone to your PC.
17. Type "fastboot oem get_unlock_data" in Command Prompt.
{Installing a New Recovery}
For the recovery we’re going to install the Photon Q Open Recovery. Every recovery has its advantages and disadvantages. This one is familiar to me and so I chose it for this guide.
1. Download the recovery image
2. Place the image in the Android SDK “platform-tools” folder which is in the "sdk" folder
3. Turn off your phone (power button + volume down if you can't select any options to turn off the phone)
4. Turn it back on using the power button + volume up + volume down combination
5. Select “Fastboot” (volume down cycles through, volume up selects the option)
6. Connect your phone to your PC
7. Go to Start > All Programs > Accessories
8. Right-click “Command Prompt”
9. Click “Run as administrator”
10. Use the cd commands to navigate to your “platform-tools” folder (Unfortunately I cannot tell you where this is as each computer will have it placed differently)
11. Type in “fasboot flash recovery open_recovery_206_05_06_2013.img”
{Getting Root}
1. Download the zip file for rooting
2. Place the file in the root (ie. not within a folder) of your phone’s SD card
3. Turn your phone off
4. Turn it back on using the power button + volume up + volume down combination
5. Select “Recovery” (volume down cycles through, volume up selects the option)
6. Select “Apply Update” (In recovery the the controls change. Volume up and volume down move in the list, the camera button at the bottom right of the device selects.)
7. Select the file you placed on your SD card from step 2
8. Wait for the update to apply, it should say that it finished successfully
9. Select “Reboot Phone”
Credit for all of this goes to their respective creators. I will name them all by name at a later date, but the credit can also be found following the linked material. Hopefully that doesn't bother the creators, writers, or hosts.
The Open Recovery port was done by Skrilax_CZ.
SuperSU is hosted by shabbypenguin and developed by Chainfire.
Please don't re-post this how-to without crediting. I've had it happen before and it was a huge disincentive for updating and making new guides.
Click to expand...
Click to collapse
I got an error when I clicked on the recovery image download link. Is there a better method?
EpicSaga said:
I got an error when I clicked on the recovery image download link. Is there a better method?
Click to expand...
Click to collapse
See the OpenRecovery thread for a valid link to that recovery... the links are a bit outdated for OR, look near the end of the thread.
I have the link to the Open Recovery thread at the very start of the section about installing recovery. It's there in case links die, someone wants more info on what they're installing, or someone has support questions pertaining to Open Recovery. This thread didn't seem to be very popular compared to one I made for an older phone so I haven't kept it up to date. The phone has been out for some time as well so I likely won't be updating this thread.
Files To Download:
*
Odin File *For Windows
*
TWRP-2.8.7.0-S820L File •UPDATED
*
SuperSU Root File
*
***ALSO DOWNLOAD SAMSUNG USB DRIVERS VIA ON THERE WEBSITE, if its your first time reboot your pc after you install them.
**********************************"**************************************"************
Directions To Install:
1. Download the given files ODIN & TWRP Recovery + SuperSU ZIP File
2. Put them where they're easy to access like in your deskop.
3. Make sure usb debugging is enable via your phone before connecting it into your computer.
4. Fire up odin program. Make sure reboot, partitioning isnt checked.
5. Put your phone into download mode by holding and pressing (volume down + home button + power button). Then hit volume up when prompt.
6. Connect your device into your computer with the usb cable that came with your device.
7. On the odin program you should see a yellowish box light up, if you see that, it means its recognized for flashing. *If you dont see it, you need to enable usb debugging in your phone or install samsung usb drivers, if not both.
8. On the odin program Click on the PDA box and find your twrp tar file that youve download.
9. Hit Start, and wait til its successfully installed. You should see a blueish box light up.
10. Disconnect your device from the usb cable. Take out the battery then put it back , or you can just go into recovery mode directly by holding and pressing the (volume up + home button + power button) hold it like for about 2-3 seconds then release just the power button.
11. You should be on the TWRP Recovery Main Menu
12. Congrats for reading the direction carefully.
-------------------------------------------
13. For already rooted users just extract the recovery.img from the tar file, put it into your external sdcard. you'll need terminal emulator, dl it via play store. Open terminal emu type:
su *for root perms
Later,
dd if=/storage/extSdCard/recovery.img of =/dev/block/platform/7824900.sdhci/by-name/recovery
hit enter *please make sure youve type it correctly before hitting ENTER*
Once finished turn off your device and go into recovery mode.
-------------------------------------------
14. If you want to root it just download the superSU flashable zip file, flash it via twrp recovery.
15. Success? Great! ENJOY YOUR NEW TWRP CUSTOM RECOVERY + ROOT!!
-------------------------------------------------------------------------------------------------------------------------
Im usin a straighttalk SM-M820L. Is there any way any of this can be done without a pc? My phone is rooted tho. I used the {yup you guessed it} kingroot method and then i did the "replace kingroot with supersu" no pc method. Is there any tips or pointers that you could give me? I'm not using a pc because it was stolen a little while back and I just haven't had the spare cash to get another. Plus I just started tinkering with this and it's super more interesting than I thought. I'm trying to learn all that I can. Thank you for any help you can offer.
None of them downloads are linked. Where are they?
galaxy core prime
PakRatt said:
None of them downloads are linked. Where are they?
Click to expand...
Click to collapse
go to area 51 site..its all in there...
Thanks, but im already done rooting it now...lol.
Sent from my SM-S820L using Tapatalk
will this by any chance allow the mobile hotspot feature that straight talk removed from there phones specifically the sm-s820l to be utilized
Area 51 wont let me join their site because i dont know the color of water! I really need a recovery for Sm S820L yesterday. No TWRP, I need one working for this phone without scouring having to the internet. Does anybody have one PLZ?!
They think water is Blue.
balrogs! said:
Area 51 wont let me join their site because i dont know the color of water! I really need a recovery for Sm S820L yesterday. No TWRP, I need one working for this phone without scouring having to the internet. Does anybody have one PLZ?!
Click to expand...
Click to collapse
They think water is blue, I guess it is in a toilet.
You guys can always check out my threads over at Needrom as well. I have 2 different posted threads there.
Here are the TWRP + Supersu files. FU Area52, with your dumb registration and all. And your stupid blue color.
Code:
https://goo.gl/hLaHCe
I am not responsible for anything that happens in your life. Including what happens as result of following steps in this thread.
Hello all. After a long journey here, we figured a new thread would be in order for new comers not to have to read through fifty pages of information. Here you will find firmware to fix or update your Viking Pro. You will also find root methods, bootloader unlock and custom recoveries for this tablet. Lets start with ROOT...
Method 1: Kingroot. Kingroot works on this device. you can find it here. It's pretty straight forward, just download and install the apk and root.
Method 1.5: SuperSu. Kingroot works but it's not the best root out there. once you have root, follow the instructions here and Kingroot will be replaced with SuperSu.
Method 2: Su flash-able ZIP. This method requires you to follow steps in posts No. 3 and 4. Once you have custom recovery installed, You can flash This.
This method is a bit redundant. However, it does allow you to make a completely stock unooted backup of your rom before making any changes.
Check out posts 2, 3, 4 & 5 for the good stuff.
I'm gonna go ahead and thank everyone responsible and If I forgot to mention you, please don't hesitate to tell me and I will correct the situation:
@Bogram (Edited the bootloader so it could be unlocked on x.12.x versions)
@Jacube22 (Duplicated the method from Bogram to make the bootloader on x.9.x versions unlockable)
@vampirefo (Compiled a compatible CWM recovery for us)
@ewilley2008 (Found most of the firmware)
@mayzemay (Initial root thread)
@NepoRood
@jerryvail35
@Sir Jaxxy
@Snigglez
@Spartan Legionnaire
@bobl61
@csla
@Chainfire (For root)
FIRMWARE
There are two main branches of development for this tablet. It is very important to know which one you have because they are incompatible with each other. I personally bricked my first one with firmware from a x.9.x while mine is x.12.x. How do you check? Simple. In your build number, you can find it in "About tablet" in Settings or in the text at the top of the recovery screen. It's at the end of the number and it will look like 1.12.30, 10.12.20, 2.12.20, 1.9.1, 1.9.5, 10.9.1...etc The number in the middle is the important one.
Steps(Windows): For step 2 you will have five seconds. Preloader mode is only active for five seconds. So read first!
1- Extract the drivers to the destktop and open the device manager.
2- Plug your tablet in as such: turn off the tablet. Plug a male to male USB wire from the computer to the USB port on the tablet. now plug the power wire into the tablet. now very quickly in the device manager locate the new device and right click on it. select "update driver software" then select "browse my computer for driver software" and "browse". Now navigate to the driver folder, select the "CDC" folder and click on "OK" the "Next". The driver should install at this point. Once that is done, unplug the power cable from the tablet.
3- Extract the firmware and the sp flash tools to your desktop.
4- Start the sp flash tools and where it says scatter file loading click and navigate to the folder where you have the firmware and load the scatter file. You will see the firmware get loaded and a checksum check.
5- Once that is done, uncheck the preloader from the list and click on the download button.
6- Plug the power cable into your tablet. At this point the sp flash tool will load the firmware into the tablet. DO NOT UNPLUG ANYTHING UNTIL THE SP FLASH TOOLS SHOWS YOU A GREEN CHECK MARK TO INDICATE THAT IT IS DONE OR YOUR TABLET COULD BE HARD BRICKED AND UNREPAIRABLE.
7- Press the reset button and turn it on. Done!
Drivers: https://drive.google.com/file/d/0Bz4bOoJ_E5XzRWJCbGFINndmVmc/view?usp=sharing
SP Flash tools: https://drive.google.com/file/d/0Bz4bOoJ_E5Xzb0g3ZnlEcHE0bEE/view?usp=sharing
Firmware x.9.x:
RCT6303W87DK-ANDROID5.0-V37-V10.9.21-NFC-V2.3LA-20150820
RCT6303W87DK-ANDROID5.0-V32-1.9.1-20150409
Do not flash the preloader for the Surf1001 versions!!
Firrmware x.12.x:
RCT6303W87DK-ANDROID5.0-V77-V1.12.50-EMMC-user-Kingston-V6.1_20160316
RCT6303W87DK-ANDROID5.0-V70-V1.12.30-B-EMMC-user-Kingston-V6.1_20160121
SURF1001-ANDROID5.0-V11-V7.15.0_T8515B_V6.3_SAMSUNG2G_20151116 (Use method No.2 for root)
RCT6303W87DK-ANDROID5.0-V63-V10.12.0_T8515B_V6.3_PCDDR31G_20151106
SURF1001-ANDROID5.0-V07-V7.15.0_T8515B_V6.3_SAMSUNG2G_20151016
RCT6503W87DK-ANDROID5.0-V66-V20.12.20-B-Camera-2M_PCDDR_V6.3-20150928
RCT6303W87DK-ANDROID5.0-V63-V2.12.20-B-EMMC-user-Kingston-V6.1_20150811
Sources:
http://laurentiumihet.ro/technology/...test-versions/
http://www.needrom.com/download/mtk-...er-v5-1453-03/
http://pan.baidu.com/share/home?uk=2...ategory/type=0
http://baiduyun.57fx.cn/so-result.ht...7DK&type=share
And Google of course...
Bootloader
So the bootloader on this tablet is locked. To unlock the bootloader, in a perfect world, you would usually boot the tablet in fastboot and type the command "fastboot oem unlock" and then follow the instructions on the screen. However RCA did not code in the volume keys in fastboot mode so it was impossible to unlock the bootloader that way. So our friend Bogram edited the bootloader and now the volume keys are not needed. What swell guy eh?
Unlocking your phone’s bootloader completely wipes (formats) your Android phone’s internal memory including applications, contacts, SMS and MMS messages etc.
So what you need is a scatter file like this one and a patched bootloader like these: x.12.x or x.9.x .
You will also need ADB & Fastboot and the drivers.
1- Just like in the FIRMWARE section, install drivers and SP Flash Tools.
2- Open SP Flash Tools and load the scatter file and in the line where you see "uboot" on the right click in the blank field and a window will pop up. select the patched bootloader. Make sure it checked and click on the "Download" button.
3- Now plug the male to male USB cable and then plug in the power. SP flash tool will flash the bootloader and then show you a nice little green check mark.
4- At this point you need to unpack the adb folder from the RAR file and place it in the root of you hard drive(C: ) then open a command prompt and nvigate to you adb folder (cd c:\adb) and leave it there for just a second.
5- On your tablet unplug the power wire, hit the reset button in the back and boot it into recovery mode by pressing and holding the volume up and power buttons together until the RCA splash screen comes up then release them.
6- In recovery, use the volume keys to navigate to "reboot to bootloader" and use the power button to select.
7- At this point your tablet will be in fastboot and your computer should detect it and install the driver. If not, the driver is in the "Android" folder in the driver files you extracted.
8- In your command prompt you left opened earlier, type "fastboot oem unlock".
9-Your tablet will do some magic, summon a demon, banish it to the depths of hell, reboot a couple of times and then it will have a unlocked bootloader.
10- Done. now you ca move on the next post and flash recovery.
Bogram also created a tool that patches the bootloader automatically should you have a different version we don't know about or what not...
Code:
RCA LittleKernel Unlock Patcher
By Bogram (http://forum.xda-developers.com/member.php?u=7182821)
Tested models:
RCA Viking Pro (RCT6303W87DK), RCA Maven Pro (RCT6213W87DK)
USE THIS TOOL AT YOUR OWN RISK, NO WARRANTY IS PROVIDED.
License: http://www.gnu.org/licenses/gpl-3.0.html
Input file:
W:/HaxeToolkit/projects/patcher/lk.bin
Wrote to:
W:/HaxeToolkit/projects/patcher/lk_patched.bin
Press any key to exit.
https://drive.google.com/file/d/0Bz4bOoJ_E5XzSnJ2R3d2NkxlU0k/view?usp=sharing
RECOVERY
This section depends on a unlocked bootloader. If you did not unlock your bootloader in the previous post, do so before continuing to this one.
So what you need is a scatter file like this one and a recovery.
CWM + Carliv compiled by vampirefo: (x.9.x)Clockworkmod recovery (x.12.x)Clockworkmod recovery
TWRP V3.00 compiled by Neporood: (x.9.x)TWRP V3.00 recovery (x.12.x)TWRP V3.00 recovery(Coming soon)
- Open SP Flash tool and select the scatter file.
- in the recovery line, on the right side in the blank field, click and select your downloaded recovery.
- Click on the download button.
- Make sure your tablet is off, plug the USB cable first and then the power cable.
- SP Flash tool will flash the recovery and show you a lovely green check mark.
- Once that is done your recovery will be flashed.
** The stock system has a file in the system folder called "recovery-from-boot.p". this file flashes stock recovery randomly at boot so with a rooted system, navigate to the folder with a root capable explorer and delete the file so that your new recovery stays there.
** When rebooting from recovery, cwm will tell you to fix root. Don't. Select no every time.
For thos of you who want a file explorer in recovery, You can download this Aroma installer flashable
It's a nice tool to have...
Aroma comes from here: http://forum.xda-developers.com/showthread.php?t=1646108
ROMS
Not yet but soon.....
I'd swear I've seen all this somewhere before... lol
Good job, brother!
Now , let the roms...begin.....
woot ... just in time as I brought my Viking Pro home from Wallyworld Saturday night.
Any thoughts on ADB? I couldn't make it all the way through the other thread and eventually just gave up.... ended up figuring out Kingroot on my own and then just enabled ADB over wifi. Would much rather have a wired ADB solution as moving an APK (I'm a developer, duh) over wifi can be somewhat s-l-o-w.
Any plans to make a thread like this for the RCA Maven Pro (RCT6213W87DK)? It'd be really swell.
EDIT: Actually, with those sources you posted, I actually might be able to do this on my own.
thevypr said:
Any plans to make a thread like this for the RCA Maven Pro (RCT6213W87DK)? It'd be really swell.
EDIT: Actually, with those sources you posted, I actually might be able to do this on my own.
Click to expand...
Click to collapse
I've got a Maven, and I've already done the porting. I'll be posting a guide tomorrow morning sometime. For now, I've sent you a PM with links to the firmware. Check your firmware version, mine is V36-1.9.21 (as long as you have the "9", you should be ok) The zip file has everything in it, preloader, scatter, custom recovery, etc...
Maven Guide is up, find it here
Synman said:
woot ... just in time as I brought my Viking Pro home from Wallyworld Saturday night.
Any thoughts on ADB? I couldn't make it all the way through the other thread and eventually just gave up.... ended up figuring out Kingroot on my own and then just enabled ADB over wifi. Would much rather have a wired ADB solution as moving an APK (I'm a developer, duh) over wifi can be somewhat s-l-o-w.
Click to expand...
Click to collapse
Still working on adb... Trying to make a flashable ROM with the fixes... No timeframe tho..
smartmanvartan said:
Still working on adb... Trying to make a flashable ROM with the fixes... No timeframe tho..
Click to expand...
Click to collapse
I can't get the port(s) to light up under OSX. I've tried a couple build.prop changes, plugging in micro usb, usb type a, power connector, and various combinations but none of them appear to trigger registration of a usb device of any kind on the host machine.
I can't even get simple stuff like MTP to work.
Synman said:
I can't get the port(s) to light up under OSX. I've tried a couple build.prop changes, plugging in micro usb, usb type a, power connector, and various combinations but none of them appear to trigger registration of a usb device of any kind on the host machine.
I can't even get simple stuff like MTP to work.
Click to expand...
Click to collapse
Time is my issue but I'm looking at two things. there is a firmware package i found on the Chinese server for a tablet with the model number rct6603w47dk with the same board as the viking pro but with a 8163 instead of the 8127. i think its doable to port over to our tablet. it is android 6. also the maven pro(rct6213w87dk) which is really close to our tablet with the same board but a larger screen, has adb working on it...
You should be getting a reaction through the micro usb port... on windows it shows up as a malfunctioning device.
i get nothing when sniffing the USB bus on my MBP.
Synman said:
i get nothing when sniffing the USB bus on my MBP.
Click to expand...
Click to collapse
I does the same thing on Ubuntu 14.04, absolutely nothing shows with "lsusb" in the terminal, unless it's in fastboot mode. You can use fastboot to flash the device, if you don't have access to a Windows machine...
I tested the new 1.9.3 firmware on my tablet... and it just shows a black screen.
DO NOT FLASH IT. it didn't work
Jacube22 said:
I tested the new 1.9.3 firmware on my tablet... and it just shows a black screen.
DO NOT FLASH IT. it didn't work
Click to expand...
Click to collapse
Ill find you guys some newer software that boots...
What's the difference between sp_drive_v2.0_finally & mtk_sp_drivers_v2.0
Because I got the sp_drive install but having a problem with the mtk_sp , it keep popping up as incompatible software.... I'm stuck on the boot loader section
e923 said:
What's the difference between sp_drive_v2.0_finally & mtk_sp_drivers_v2.0
Because I got the sp_drive install but having a problem with the mtk_sp , it keep popping up as incompatible software.... I'm stuck on the boot loader section
Click to expand...
Click to collapse
What version of Windows are you running..the difference is the drivers are signed or unsigned.. This matters more on newer versions of Windows.
Hi! After struggling in rooting my C9 pro (SM-C9000, TGY) due to the lack of a proper guide, I decided to provide my guide to the community.
Of course, I don't take responsibility for damages etc. etc. Read the entirety of the guide before doing anything.
Useful shortcuts: Holding down power+volume down for a couple seconds force reboots from almost anywhere. Vol up+home+power while booting boots into recovery. Vol down+home+power boots into download (odin) mode.
Step 1) Fetch the required files(sorry I can't post direct links):
Nougat 7.1.1 firmware from sammobile
Oreo 8.0 firmware from sammobile
Odin https://www.xda-developers.com/update-firmware-any-samsung-phone/
Magisk Manager https://www.xda-developers.com/how-to-install-magisk/ (The link that says "Download the latest Magisk Manager APK here")
ADB https://www.xda-developers.com/install-adb-windows-macos-linux/
CROM Service apk from apkmirror
Step 2) Prepare the files
Unlock developer options on your phone by spamming Build Number in Settings> About Phone> Software Information. Enable USB debugging from developer options. Connect your phone to your PC via cable. Extract ADB (platform-tools) on your desktop (or other location). Extract Oreo firmware. There should be 5 files. Copy the one that starts with AP into platform-tools folder. Open the platform-tools folder. Hold down shift and right click inside the folder. Choose "Open PowerShell window here" from the context menu. Type or copy-paste
Code:
.\adb devices
to start ADB. On your phone, check "always allow on this PC" and click OK when prompted. Enter the code again and check if a device appears on the list. Then type
Code:
.\adb push AP_C9000ZHU1CSC1_CL14667562_QB22709761_REV00_user_low_ship_MULTI_CERT_meta.tar.md5 /sdcard/
.(Change the name of the file corresponding to yours. You can change the destination to another folder in your phone. Ex. /sdcard/download/) This will transfer the file from your PC to your phone. Do not drag and drop the file. This might corrupt it, causing a bootloop upon installiation. (Happened to me initially. Recovered & used the push command to get it to work.). Transfer Magisk Manager's apk to your phone or download it directly from your phone(you can drag and drop this one, as it won't install if corrupted(it won't corrupt)). Install Magisk Manager on the phone(Enable sideloading if asked). In the app, touch the topmost install button and touch install again in the next screen. You will have two options: "Download zip only" and "Select and patch a file". Choose "Select and patch a file", then locate the AP file you transferred to the device. Magisk manager will patch the file and generate magisk_patched.tar in /sdcard/download/. In ADB, type
Code:
.\adb pull /sdcard/download/magisk_patched.tar
This will transfer it to the platform-tools folder. Again, don't use windows explorer to transfer. That will most certainly corrupt the file.
Step 2.5) Backup
Backup your data (you can use smart switch desktop program paired with mobile app to backup most of the stuff). Remove your google account from the device.
Step 3) Install Nougat 7.1.1
Extract Nougat 7.1.1 firmware. Extract odin. Run Odin.exe (might have version in name). Click OK. Factory reset your phone (You can do so from settings or recovery mode.). After the reset, reboot into download mode. It will ask if you're sure you want to install unofficial software, choose continue (If I don't recall incorrectly, the button for that was vol up). Plug your phone into your PC. Odin log should say "added!!" and you should see your device in one of the rectangles above. Now select the tar.md5 files extracted from the 7.1.1 firmware. Click the BL button, locate the BL_etcetc.tar.md5 file, click open. It will check the md5 for a second then let you click the next button. After choosing the BL(bootloader), AP(system), CP(radio) and CSC(localization) files (USERDATA button should remain empty, HOME_CSC file has no use) make sure only F.reset time and auto reboot are selected in options. Click start to begin. After flashing, it will do another factory reset and show you the setup.
Step 4) Unlock Bootloader
Skip everything in setup, then unlock develper options and you should see "OEM Unlocking" option that was removed in OREO firmware in there. Enable it. Next transfer the CROM service apk to your device (or download it directly). Install the app. Open it. Unlock the bootloader. (This step is required because C9000 is a Chinese phone)
Step 5) Install Oreo again
Boot into download and connect to odin. You can use the reset button to empty the buttons. Now select BL, CP and CSC files from the extracted oreo firmware. For AP, choose magisk_patched.tar . Start. If the installiation fails, you didn't unlock the Bootloader properly. The phone will reboot and factory reset a couple times. When it boots up, you'll have magisk installed.
Step 6) Things to do after rooting(optional)
First of all, magisk can hide root from Google, but not Samsung. Samsung Health, Knox secure container, Maximum power saving mode and Samsung pay won't work after you root. NFC will keep turning on on its own unless you uninstall Samsung pay. A samsung package (I'm not sure about the name but I think it was security log agent) will keep sending an unblockable notification offering to unroot. Uninstall that too, and you'll have a stable experience.
Recovering from fails:
If download mode refuses to install because of unofficial binaries, the bootloader isn't properly unlocked. Wait a couple seconds and force reboot with the key combination. Since it couldn't flash the system, that should reboot back to download mode (or recovery. in that case, choose "reboot to bootloader"). Install the official firmware, unlock bootloader and try again.
If the magisk_patched.tar file gets corruped and you flash the corrupted file successfully, your device will get into a bootloop. After the install, odin orders the phone to reboot into recovery to factory reset, but since the system image is corrupted, it won't be able to boot and produce a kernel panic. This will cause the phone to reboot, which will fail and cause it to try to reboot again. Since the phone doesn't get past the splash screen, this bootloop cannot be interrupted by button shortcuts. You should wait for the battery to die out for the bootloop to end. (It should take a day at max. Wrap a towel around it to block the vibration sounds if you want) After battery gets depleted, you need to perform a quick maneuver. You should plug the phone into a power supply (preferably your computer) while holding down volume down+home+power buttons. If you do it right, it will boot into download mode. (Otherwise, it will bootloop again. Simply unplug, wait for it to stop and try again) Flash the official firmware and repatch the AP file. Just in case you run into this issue, I recommend having less than 10% charge in your phone while flashing, just to make the wait time shorter.
Important: Check your firmware's baseband version from settings before flashing. In C9000ZHU1CSC1, CSC1 is the system and U1 is the bootloader version. Compare the bootloader version to the firmware you're going to flash and make sure they match. You can't downgrade bootloader versions. Flashing a previous version will brick your phone. (Probably permanently) This shouldn't be an issue since sm-C9000 has only one bootloader version, but check it anyways just to be sure.
Lojcs said:
Hi! After struggling in rooting my C9 pro (SM-C9000, TGY) due to the lack of a proper guide, I decided to provide my guide to the community.
Of course, I don't take responsibility for damages etc. etc. Read the entirety of the guide before doing anything.
Useful shortcuts: Holding down power+volume down for a couple seconds force reboots from almost anywhere. Vol up+home+power while booting boots into recovery. Vol down+home+power boots into download (odin) mode.
Step 1) Fetch the required files(sorry I can't post direct links):
Nougat 7.1.1 firmware from sammobile
Oreo 8.0 firmware from sammobile
Odin https://www.xda-developers.com/update-firmware-any-samsung-phone/
Magisk Manager https://www.xda-developers.com/how-to-install-magisk/ (The link that says "Download the latest Magisk Manager APK here")
ADB https://www.xda-developers.com/install-adb-windows-macos-linux/
CROM Service apk from apkmirror
Step 2) Prepare the files
Unlock developer options on your phone by spamming Build Number in Settings> About Phone> Software Information. Enable USB debugging from developer options. Connect your phone to your PC via cable. Extract ADB (platform-tools) on your desktop (or other location). Extract Oreo firmware. There should be 5 files. Copy the one that starts with AP into platform-tools folder. Open the platform-tools folder. Hold down shift and right click inside the folder. Choose "Open PowerShell window here" from the context menu. Type or copy-paste to start ADB. On your phone, check "always allow on this PC" and click OK when prompted. Enter the code again and check if a device appears on the list. Then type .(Change the name of the file corresponding to yours. You can change the destination to another folder in your phone. Ex. /sdcard/download/) This will transfer the file from your PC to your phone. Do not drag and drop the file. This might corrupt it, causing a bootloop upon installiation. (Happened to me initially. Recovered & used the push command to get it to work.). Transfer Magisk Manager's apk to your phone or download it directly from your phone(you can drag and drop this one, as it won't install if corrupted(it won't corrupt)). Install Magisk Manager on the phone(Enable sideloading if asked). In the app, touch the topmost install button and touch install again in the next screen. You will have two options: "Download zip only" and "Select and patch a file". Choose "Select and patch a file", then locate the AP file you transferred to the device. Magisk manager will patch the file and generate magisk_patched.tar in /sdcard/download/. In ADB, type This will transfer it to the platform-tools folder. Again, don't use windows explorer to transfer. That will most certainly corrupt the file.
Step 2.5) Backup
Backup your data (you can use smart switch desktop program paired with mobile app to backup most of the stuff). Remove your google account from the device.
Step 3) Install Nougat 7.1.1
Extract Nougat 7.1.1 firmware. Extract odin. Run Odin.exe (might have version in name). Click OK. Factory reset your phone (You can do so from settings or recovery mode.). After the reset, reboot into download mode. It will ask if you're sure you want to install unofficial software, choose continue (If I don't recall incorrectly, the button for that was vol up). Plug your phone into your PC. Odin log should say "added!!" and you should see your device in one of the rectangles above. Now select the tar.md5 files extracted from the 7.1.1 firmware. Click the BL button, locate the BL_etcetc.tar.md5 file, click open. It will check the md5 for a second then let you click the next button. After choosing the BL(bootloader), AP(system), CP(radio) and CSC(localization) files (USERDATA button should remain empty, HOME_CSC file has no use) make sure only F.reset time and auto reboot are selected in options. Click start to begin. After flashing, it will do another factory reset and show you the setup.
Step 4) Unlock Bootloader
Skip everything in setup, then unlock develper options and you should see "OEM Unlocking" option that was removed in OREO firmware in there. Enable it. Next transfer the CROM service apk to your device (or download it directly). Install the app. Open it. Unlock the bootloader. (This step is required because C9000 is a Chinese phone)
Step 5) Install Oreo again
Boot into download and connect to odin. You can use the reset button to empty the buttons. Now select BL, CP and CSC files from the extracted oreo firmware. For AP, choose magisk_patched.tar . Start. If the installiation fails, you didn't unlock the Bootloader properly. The phone will reboot and factory reset a couple times. When it boots up, you'll have magisk installed.
Step 6) Things to do after rooting(optional)
First of all, magisk can hide root from Google, but not Samsung. Samsung Health, Knox secure container, Maximum power saving mode and Samsung pay won't work after you root. NFC will keep turning on on its own unless you uninstall Samsung pay. A samsung package (I'm not sure about the name but I think it was security log agent) will keep sending an unblockable notification offering to unroot. Uninstall that too, and you'll have a stable experience.
Recovering from fails:
If download mode refuses to install because of unofficial binaries, the bootloader isn't properly unlocked. Wait a couple seconds and force reboot with the key combination. Since it couldn't flash the system, that should reboot back to download mode (or recovery. in that case, choose "reboot to bootloader"). Install the official firmware, unlock bootloader and try again.
If the magisk_patched.tar file gets corruped and you flash the corrupted file successfully, your device will get into a bootloop. After the install, odin orders the phone to reboot into recovery to factory reset, but since the system image is corrupted, it won't be able to boot and produce a kernel panic. This will cause the phone to reboot, which will fail and cause it to try to reboot again. Since the phone doesn't get past the splash screen, this bootloop cannot be interrupted by button shortcuts. You should wait for the battery to die out for the bootloop to end. (It should take a day at max. Wrap a towel around it to block the vibration sounds if you want) After battery gets depleted, you need to perform a quick maneuver. You should plug the phone into a power supply (preferably your computer) while holding down volume down+home+power buttons. If you do it right, it will boot into download mode. (Otherwise, it will bootloop again. Simply unplug, wait for it to stop and try again) Flash the official firmware and repatch the AP file. Just in case you run into this issue, I recommend having less than 10% charge in your phone while flashing, just to make the wait time shorter.
Important: Check your firmware's baseband version from settings before flashing. In C9000ZHU1CSC1, CSC1 is the system and U1 is the bootloader version. Compare the bootloader version to the firmware you're going to flash and make sure they match. You can't downgrade bootloader versions. Flashing a previous version will brick your phone. (Probably permanently) This shouldn't be an issue since sm-C9000 has only one bootloader version, but check it anyways just to be sure.
Click to expand...
Click to collapse
Have you tried this method and phone working fine will there will be any problem if i use this method for rooting c9000?
khankk42 said:
Have you tried this method and phone working fine will there will be any problem if i use this method for rooting c9000?
Click to expand...
Click to collapse
Yes, I did root my SM-C9000 using this method, and it is working nicely. Obviously I lost access to Secure Folder and Samsung Pay. You should be able to install the Play Store version of Samsung Health. Maximum Power Saving froze the phone the first two times I enabled it, but it's working fine now. One unexpected caveat is that mobile hotspot started to turn itself off if mobile data is enabled even though my carrier has no restrictions on using hotspot. You can't share your data connection using Bluetooth or usb cable neither. You can still use the hotspot for creating a local network. Other than those, I didn't experience any problems after rooting. While I was rooting, I did the mistake of using MTP to transfer the image and as a result my phone bootlooped for half a day but if you follow the instructions, that won't be a problem.
Of course, I don't guarantee anything and don't take responsibility, but there is no reason anything should go wrong.
My base band R16NW.C9000ZHU1CSC1, model number SM-C9000, android 8.0.0...
I have never rooted any phones in my life. What should i do? I search on internet but i didnt found any spesific things about "R16NW.C9000ZHU1CSC1" can you help me? Those options will work for me to ?
otocu said:
My base band R16NW.C9000ZHU1CSC1, model number SM-C9000, android 8.0.0...
I have never rooted any phones in my life. What should i do? I search on internet but i didnt found any spesific things about "R16NW.C9000ZHU1CSC1" can you help me? Those options will work for me to ?
Click to expand...
Click to collapse
Sorry for responding late. Yes, that is the exact model that I have and rooted using the method in the post. If you feel confident, you can follow trough it and root your phone. You can grab the required firmware from Sammobile. Keep in mind that after rooting some features might stop working (like hotspot and knox-related features). Good luck!
I got the same model of Samsung phone. I follow the steps but till step five, when i press open the files in odin and press start button, the odin will disappear in my computer. Then i try again and it failed. My phone shows: unsuppoted dev types. Here are my photos. Do you have any ideas? And i dunno how can i redo it again to root my phone. Would love to see helps from you, thanks!
cherrio128 said:
I got the same model of Samsung phone. I follow the steps but till step five, when i press open the files in odin and press start button, the odin will disappear in my computer. Then i try again and it failed. My phone shows: unsuppoted dev types. Here are my photos. Do you have any ideas? And i dunno how can i redo it again to root my phone. Would love to see helps from you, thanks!
Click to expand...
Click to collapse
Sorry for the late response. Searching that on the internet, it seems you might be using an old version of Odin. Please make sure you're using 3.13.1 and try again
ROOT (ALMOST) EVERY DEVICE WITH MAGISK + FASTBOOT
As an Android user, I understand how frustrating it will be when you desperately look for an exact rooting tutorial for your device but end up finding nothing, all one-click root tools do not work, or no custom recovery made for yours.
So, this tutorial shows you how to root a wide range of Android devices (not all, because there will be exceptions, I guess) with Magisk. First, we should take a look at the pros and cons, so that you can generally acknowledge this method.
---------------------------------------------------------------------------
PROS
- No custom recovery (TWRP, ClockworkMod,etc.) needed
- Easy to find prerequisites
- Successful root attempt CONFIRMED on my 10 devices (including popular devices, rare devices, and devices with OS based on Android)
- Support recent Android versions, including Android 10 (tested on Google Pixel XL).
CONS
- Phone brick might occur
- You might not find your device's firmware in .zip format, which will stop you from using this method.
- Not being able to unlock the bootloader (only on some device) will stop you from using this method, too.
That's about the pros and cons. I hope you guys all understand these points before going to read my tutorial and start your attempt.
---------------------------------------------------------------------------
REQUIREMENTS & STEPS
I. REQUIREMENTS
- Your device's Android version is 5.0 or up. If it's below 5.0, then you can root your device easily with any one-click tool.
- A computer & USB cable.
On your phone
- Download & install Magisk
- Download the exact firmware version (in .zip format) of your device and only extract the boot.img to any directory.
On your computer
- Download & install Fastboot, extract the folder to "Downloads" directory
- Download & install Android USB driver for Windows
(I am not sure if XDA allows inserting links in threads or not, so please search for these prerequisites on the internet, it is easy)
II. STEPS
1. Unlocking your phone's bootloader
- Open Settings > About phone > Tap on Build number about 7 times till you see a notification "You are now a developer"
- Now in the About phone tab, you can see the "Developer option". Tap on it and make sure:
+ the OEM unlocking is turned ON
+ The USB Debugging is turned On
- Plug your phone on your computer (with Fastboot & driver fully installed). Allow the USB Debugging notification on your phone
- Open Command Prompt on your computer. Enter commands below steps by steps:
cd Downloads
cd fastboot
adb reboot bootloader
(press Enter after each line to proceed)
- Your phone will reset to the bootloader menu after these commands. Next, enter this:
fastboot oem unlock
- A message asking you to make sure you want to unlock the bootloader. Use the volume and power button to choose "Yes". Your phone will reset data and reboot right after.
*Note: This method works on many Android devices, but doesn't on many devices. You might have to google a method for your own phone
2. Patching the boot.img file
After you extracted the boot.img from your device, use the Magisk app installed on your device to patch it up.
- Click the "Install" button on the first line
- Click "Select and Patch a file"
- Choose the boot.img file extracted. The patching progress will start right after.
- You will receive a file named "magisk_patched.img" after finished.
3. Flashing the "magisk_patched.img"
- Copy the "magisk_patched.img" into the Fastboot folder
- Reboot your phone to Bootloader mode by powering off and then hold Power + Volume down button simultaneously
- Open Command Prompt again, and type:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
- The flashing progress will begin. Wait until it finishes, and type the last command:
fastboot reboot
- Your phone will restart once again, and of course, with root access gained
---------------------------------------------------------------------------
UNROOT DEVICE
- If you want to unroot your device, you just have to flash the original boot.img file, with the same steps with flashing the magisk_patched.img!
---------------------------------------------------------------------------
This instruction is not truly detailed, so maybe you might encounter some difficulties at some point. If any, please feel free to leave your question below.
It is also the first time I create an instruction post, therefore I appreciate all of your comments. Thanks a lot <3
richarshub said:
ROOT (ALMOST) EVERY DEVICE WITH MAGISK + FASTBOOT
As an Android user, I understand how frustrating it will be when you desperately look for an exact rooting tutorial for your device but end up finding nothing, all one-click root tools do not work, or no custom recovery made for yours.
So, this tutorial shows you how to root a wide range of Android devices (not all, because there will be exceptions, I guess) with Magisk. First, we should take a look at the pros and cons, so that you can generally acknowledge this method.
---------------------------------------------------------------------------
PROS
- No custom recovery (TWRP, ClockworkMod,etc.) needed
- Easy to find prerequisites
- Successful root attempt CONFIRMED on my 10 devices (including popular devices, rare devices, and devices with OS based on Android)
- Support recent Android versions, including Android 10 (tested on Google Pixel XL).
CONS
- Phone brick might occur
- You might not find your device's firmware in .zip format, which will stop you from using this method.
- Not being able to unlock the bootloader (only on some device) will stop you from using this method, too.
That's about the pros and cons. I hope you guys all understand these points before going to read my tutorial and start your attempt.
---------------------------------------------------------------------------
REQUIREMENTS & STEPS
I. REQUIREMENTS
- Your device's Android version is 5.0 or up. If it's below 5.0, then you can root your device easily with any one-click tool.
- A computer & USB cable.
On your phone
- Download & install Magisk
- Download the exact firmware version (in .zip format) of your device and only extract the boot.img to any directory.
On your computer
- Download & install Fastboot, extract the folder to "Downloads" directory
- Download & install Android USB driver for Windows
(I am not sure if XDA allows inserting links in threads or not, so please search for these prerequisites on the internet, it is easy)
II. STEPS
1. Unlocking your phone's bootloader
- Open Settings > About phone > Tap on Build number about 7 times till you see a notification "You are now a developer"
- Now in the About phone tab, you can see the "Developer option". Tap on it and make sure:
+ the OEM unlocking is turned ON
+ The USB Debugging is turned On
- Plug your phone on your computer (with Fastboot & driver fully installed). Allow the USB Debugging notification on your phone
- Open Command Prompt on your computer. Enter commands below steps by steps:
cd Downloads
cd fastboot
adb reboot bootloader
(press Enter after each line to proceed)
- Your phone will reset to the bootloader menu after these commands. Next, enter this:
fastboot oem unlock
- A message asking you to make sure you want to unlock the bootloader. Use the volume and power button to choose "Yes". Your phone will reset data and reboot right after.
*Note: This method works on many Android devices, but doesn't on many devices. You might have to google a method for your own phone
2. Patching the boot.img file
After you extracted the boot.img from your device, use the Magisk app installed on your device to patch it up.
- Click the "Install" button on the first line
- Click "Select and Patch a file"
- Choose the boot.img file extracted. The patching progress will start right after.
- You will receive a file named "magisk_patched.img" after finished.
3. Flashing the "magisk_patched.img"
- Copy the "magisk_patched.img" into the Fastboot folder
- Reboot your phone to Bootloader mode by powering off and then hold Power + Volume down button simultaneously
- Open Command Prompt again, and type:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
- The flashing progress will begin. Wait until it finishes, and type the last command:
fastboot reboot
- Your phone will restart once again, and of course, with root access gained
---------------------------------------------------------------------------
UNROOT DEVICE
- If you want to unroot your device, you just have to flash the original boot.img file, with the same steps with flashing the magisk_patched.img!
---------------------------------------------------------------------------
This instruction is not truly detailed, so maybe you might encounter some difficulties at some point. If any, please feel free to leave your question below.
It is also the first time I create an instruction post, therefore I appreciate all of your comments. Thanks a lot <3
Click to expand...
Click to collapse
It's different for a/b devices where root has to be accessed by booting into the phone from recovery to boot with root
([emoji3590]09-09-18[emoji3590])
PoochyX said:
It's different for a/b devices where root has to be accessed by booting into the phone from recovery to boot with root
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
Hi PoochyX,
Thanks for your reply, could you be more specific, please? Does it mean that this method cannot work on a/b devices?
I will edit my instruction again if needed.
Thanks for your suggestions!