Related
. I don't even want a custom ROM. I just want to be rooted and run stock with rooted google play store apps. Am I there?
I just want to run rooted apps with no ROM flashing...oh god why...where is the guide to root and only root?
You'd think this http://forum.xda-developers.com/show....php?t=1652398 would be where to go to do that, but evidently it's sending me down the road to custom ROM flashing. AGHGHGhjkdashbdas. Do not want.
Ok, so here's where I am, I have finished step 8:
1. Download Odin 1.85 .
2. Download(USE FIREFOX!) ClockworkMod TOUCH 5.5.0.4 OR TWRP 2.2.2.0, they are both named "recovery.tar.md5" and will be downloaded as "recovery.tar.md5", DO NOT CHANGE the filename or else it wont install.
3. Extract the contents of odin-185.zip to a folder.
4. Run Odin 1.85.exe from the folder you extracted it to.
5. Prepare Odin: Check "auto-reboot" and UNCHECK ALL OTHER OPTIONS. SEE COMPUTER SREEN PICS BELOW.
6. Only Click "PDA" and select the recovery.tar.md5 file you downloaded. SEE COMPUTER SREEN PICS BELOW.
7. How To Put your device into Download Mode: DO NOT TOUCH THE POWER BUTTON FOR THIS PROCEDURE. - download mode is NOT the same as recovery mode
a. Connect the USB cable to your PC, but NOT to your phone.
b. Remove the battery.
c. Reinsert the battery.
d. ATT PHONES - Press and keep down both Volume Up and Volume Down keys simultaneously.
ROGERS PHONES - Press and keep down only the Volume Down key.
DO NOT RELEASE THE VOLUME KEY(S) UNTIL INSTRUCTED TO DO SO IN STEP (f)
e. Insert the USB cable into your device. The phone will turn itself on when usb cable is inserted - DO NOT TOUCH THE POWER BUTTON.
f. You will now see a screen w/a yellow triangle warning you about installing a rom . Now release the volume key(s) - SEE PHONE PICS BELOW
g. Press and release the "Volume Up" key to enter into download mode - SEE PHONE PICS BELOW
h. You should now be at the Download Mode screen w/odin recognizing your phone. SEE COMPUTER SREEN PICS BELOW.
8. Click Start in Odin. It will flash the new recovery and will reboot the phone when completed. Your device will autoreboot into android. You are done using ODIN.
9. UPDATING CWM OR TWRP:
Now you need to udate CWM, download and copy cwm6027touch_v14.4.6_skyrocket.zip file to your sdcard, boot into recovery and choose "INSTALL FROM SDCARD" from recovery, install the file and reboot back into recovery to see if it installed correctly.
sk8erwitskil's CWM thread is here HERE , check to see if above file is the latest or dl the "Flashable zip" CWM file from there.
If upgrading TWRP go here HERE and follow the dev's instructions on using goo app, or you can use the flashable TWRP 2.4.1.0 file HERE and copy that file to your sdcard, boot into recovery and pick "INSTALL" from recovery, install the file and reboot back into recovery to see if it installed correctly.
How to enter recovery read section #2 below.
How to use cwm read THIS, also read Q&A on recoveries
You can upgrade to either CWM OR TWRP from which ever recovery TAR file you used in ODIN in step #2 from above.
10. You're done newbie and soon to be a power user, read and educate yourself as much as you can before flashing, happy flashing.
Click to expand...
Click to collapse
I don't know how to do step 9. Do I even need it? I have no desire to run a custom ROM.
yargdpirate said:
OK so here's the list of instructions I'm using to root my Skyrocket:
I have completed everything through step 4. I completely do not understand what to do after that. So, like I'm a 40 year old soccer mom, can you explain what I'm supposed to do to fulfill step 5? Is it through the odin app on my pc? Is this completed on my phone? The link provided that ostensibly explains to noobs how to do this (http://forum.xda-developers.com/showthread.php?t=1777970) doesn't adequately explain to me what I'm doing and where.
Help, please!
Click to expand...
Click to collapse
Assuming that you have successfully installed your custom recovery you then need to know which recovery you installed before you update it. If you used CWM you can get the updated version from the Skyrocket development thread. Put the updated CWM file on your SD card and flash that zip while in recovery. If you used TWRP you can update it through the app that it installed if it did install one. GooManager (someone correct me if I am wrong on the name) I think GooManager needs suoeruser privileges. So which recovery did you flash?
CodeNameRedNeck said:
Assuming that you have successfully installed your custom recovery you then need to know which recovery you installed before you update it. If you used CWM you can get the updated version from the Skyrocket development thread. Put the updated CWM file on your SD card and flash that zip while in recovery. If you used TWRP you can update it through the app that it installed if it did install one. GooManager (someone correct me if I am wrong on the name) I think GooManager needs suoeruser privileges. So which recovery did you flash?
Click to expand...
Click to collapse
Put the updated CWM file on your SD card and flash that zip while in recovery?
Click to expand...
Click to collapse
It's CWM. How do I
A. Put the updated CWM file on my SD card and
B. Flash that zip while in recovery? Is that through Odin, or what?
Thanks
yargdpirate said:
It's CWM. How do I
A. Put the updated CWM file on my SD card and
B. Flash that zip while in recovery? Is that through Odin, or what?
Thanks
Click to expand...
Click to collapse
i think you should stay on stock, read more b4 you brick your phone, no sense in rooting/installing custom roms when you dont know how to install a file on your scard, im not putting you down but trying to give you friendly advice
Vincom has a point. I taught myself through these forums and Google how to do it back in October of 2011. I flashed many a ROM and many files since then until I bricked mine Thursday. Now I have to pay 60 dollars to get it fixed. But on the upside I now have a Note II to play with.
Edit: She is asking for help though and she did ask in the right thread. Some people need more help than others.
vincom said:
i think you should stay on stock, read more b4 you brick your phone, no sense in rooting/installing custom roms when you dont know how to install a file on your scard, im not putting you down but trying to give you friendly advice
Click to expand...
Click to collapse
Oh. ****. I don't even want a custom ROM. I just want to be rooted and run stock with rooted google play store apps. Am I there?
I just want to run rooted apps with no ROM flashing...oh god why...where is the guide to root and only root?
You'd think this http://forum.xda-developers.com/showthread.php?t=1652398 would be where to go to do that, but evidently it's sending me down the road to custom ROM flashing. AGHGHGhjkdashbdas. Do not want.
Ok, so here's where I am, I have finished step 8:
1. Download Odin 1.85 .
2. Download(USE FIREFOX!) ClockworkMod TOUCH 5.5.0.4 OR TWRP 2.2.2.0, they are both named "recovery.tar.md5" and will be downloaded as "recovery.tar.md5", DO NOT CHANGE the filename or else it wont install.
3. Extract the contents of odin-185.zip to a folder.
4. Run Odin 1.85.exe from the folder you extracted it to.
5. Prepare Odin: Check "auto-reboot" and UNCHECK ALL OTHER OPTIONS. SEE COMPUTER SREEN PICS BELOW.
6. Only Click "PDA" and select the recovery.tar.md5 file you downloaded. SEE COMPUTER SREEN PICS BELOW.
7. How To Put your device into Download Mode: DO NOT TOUCH THE POWER BUTTON FOR THIS PROCEDURE. - download mode is NOT the same as recovery mode
a. Connect the USB cable to your PC, but NOT to your phone.
b. Remove the battery.
c. Reinsert the battery.
d. ATT PHONES - Press and keep down both Volume Up and Volume Down keys simultaneously.
ROGERS PHONES - Press and keep down only the Volume Down key.
DO NOT RELEASE THE VOLUME KEY(S) UNTIL INSTRUCTED TO DO SO IN STEP (f)
e. Insert the USB cable into your device. The phone will turn itself on when usb cable is inserted - DO NOT TOUCH THE POWER BUTTON.
f. You will now see a screen w/a yellow triangle warning you about installing a rom . Now release the volume key(s) - SEE PHONE PICS BELOW
g. Press and release the "Volume Up" key to enter into download mode - SEE PHONE PICS BELOW
h. You should now be at the Download Mode screen w/odin recognizing your phone. SEE COMPUTER SREEN PICS BELOW.
8. Click Start in Odin. It will flash the new recovery and will reboot the phone when completed. Your device will autoreboot into android. You are done using ODIN.
9. UPDATING CWM OR TWRP:
Now you need to udate CWM, download and copy cwm6027touch_v14.4.6_skyrocket.zip file to your sdcard, boot into recovery and choose "INSTALL FROM SDCARD" from recovery, install the file and reboot back into recovery to see if it installed correctly.
sk8erwitskil's CWM thread is here HERE , check to see if above file is the latest or dl the "Flashable zip" CWM file from there.
If upgrading TWRP go here HERE and follow the dev's instructions on using goo app, or you can use the flashable TWRP 2.4.1.0 file HERE and copy that file to your sdcard, boot into recovery and pick "INSTALL" from recovery, install the file and reboot back into recovery to see if it installed correctly.
How to enter recovery read section #2 below.
How to use cwm read THIS, also read Q&A on recoveries
You can upgrade to either CWM OR TWRP from which ever recovery TAR file you used in ODIN in step #2 from above.
10. You're done newbie and soon to be a power user, read and educate yourself as much as you can before flashing, happy flashing.
Click to expand...
Click to collapse
I don't know how to do step 9. Do I even need it? I have no desire to run a custom ROM.
For just rooting u have to run the superuser zip through your recovery
Oh and if you are not understanding what the stickies are saying to do then look it up on youtube because there are a lot of step by step instructions there.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
a. put updated file in your micro sd card.... plug ur micro sd card to pc... drag file and drop it in your micro sd card. put the micro sd card back in phone.
b. to go to recovery press power button + vol+ + vol- all at once and hold.
why do u need to unlock play store app? playstore is accessible completely even without root. you can also sideload Amazon appstore and other apps without root. no need to get all bricked up just to run playstore. i'm confused what are you trying to do again?
droidbabyxda said:
a. put updated file in your micro sd card.... plug ur micro sd card to pc... drag file and drop it in your micro sd card. put the micro sd card back in phone.
b. to go to recovery press power button + vol+ + vol- all at once and hold.
why do u need to unlock play store app? playstore is accessible completely even without root. you can also sideload Amazon appstore and other apps without root. no need to get all bricked up just to run playstore. i'm confused what are you trying to do again?
Click to expand...
Click to collapse
im guessing he wants to run apps from play that require root, eg titanuim backup, but he doesnt know how to put a file on his sdcard, but then he has to learn how to install zips from recovery which someones got to teach him since he doesnt want to read/learn/search for the answers. he seems to be impatient and wants it done "now", its a brick waiting to happen, my advice to him was to slowdown and learn
vincom said:
im guessing he wants to run apps from play that require root, eg titanuim backup, but he doesnt know how to put a file on his sdcard, but then he has to learn how to install zips from recovery which someones got to teach him since he doesnt want to read/learn/search for the answers. he seems to be impatient and wants it done "now", its a brick waiting to happen, my advice to him was to slowdown and learn
Click to expand...
Click to collapse
agree and such bad attituted too. i wouldn't want to help anybody who cusses in every conversation geez little respect goes a long way
It you just want to root and not want to flash any custom ROMs or anything related to it,I will tell you how to from total beginning
ALL DATA WILL BE LOST , BACKUP EVERYTHING
In order to root Android 4.2 the following three requirements must be satisfied beforehand:
The Android SDK, which you can download from Google Developers
A custom recovery like ClockworkMod (CWM) or Team Win Recovery Project (TWRP)
SuperSU, which you can download from CF-Root
There are no major differences between the two, but TWRP is more touch-oriented thanks to larger buttons. CWM is also available in a touch-compatible variant, but it has much smaller buttons. It's a matter of personal preference between the two though, but you have to choose one.
Before starting the process I urge you to perform a backup, as all data might be lost afterwards. You can copy the contents of the SD card to a safe external location such as cloud storage service or computer hard drive.
The first step that needs to be performed after all the files are downloaded is to install the Android SDK. Afterwards open the Android SDK Manager and select the following two items:
Android SDK Platform-tools -- it contains the required programs to install Android 4.2 Jelly Bean
Google USB Driver -- it contains the necessary drivers for the Nexus device
Then you should create a folder in an easily accessible location within the command line. In this example I will use a folder named "Root" in my C:\ drive in Windows. The path name will therefore be: "C:\Root".
From the folder where Android SDK Platform-tools is installed (in my case it is "C:\Program Files x86)\Android\android-sdk\platform-tools" copy the following files to the previously created "Root" folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
The following files must also be copied to the "Root" folder:
CWM-SuperSU-v0.97.zip -- SuperSU file
The custom recovery that you previously downloaded for your specific device (please see below)
For my 8 GB nexus 7 wifi(codename "grouper" I will use TWRP with the name "openrecovery-twrp-2.3.1.0-grouper.img".
You can easily find the codename for your devoice by looking into Google
The custom recovery file differs for each device, please make sure you download the correct file
In order to make the process smoother for instance the SuperSU file can be renamed to "root.zip" and the custom recovery to "customrecovery.zip". It's a matter of convenience, but for accuracy I will stick to the original naming for this guide.
If the previous steps are completed you must have the following six files in your "Root" folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
CWM-SuperSU-v0.97.zip -- SuperSU file
The custom recovery. In my case it is "openrecovery-twrp-2.3.1.0-grouper.img"
From there, you can proceed to install the drivers for "fastboot mode". To install them, follow these steps:
Power off your Nexus device.
Press and hold Volume Up and Volume Down then press and hold the Power button; the device will now enter "fastboot mode".
Go to Device Manager (Computer -> Properties -> Device Manager in Windows 7/8) and identify the device; for me it shows up as Android 1.0.
Right click Android 1.0 and select "Update Driver Software," then select "Browse my computer for driver software".
Select "Let me pick from a list of device drivers on my computer," then click "Next".
From "Have Disk..." option go to the folder where you have Google USB Driver installed (for me it's "C:\Program Files .(x86)\Android\android-sdk\extras\google\usb_driver" and select "android_winusb.inf".
Out of the three options select "Android ADB Interface" and validate any future warning window to install the driver.
Final preparations
Everything is prepared in order to start the installation process, but in order to do so a command window must be opened. Windows Key + R opens "Run"; type in "cmd" and the command window appears. Typing "cd C:\Root" and pressing Enter sets the "Root" folder as the working directory. Pressing the Shift key and right clicking inside the "Root" folder will also deliver the same result.
The device must be turned on in "fastboot mode" which I have explained at step no.2 during the driver installation process, and obviously plugged-in to the computer. You then have to type in the following commands while in "fastboot mode":
fastboot devices -- this is just for verification purposes; if there is no listed device then the drivers have been improperly installed and steps 1 through 7 must be redone.
fastboot oem unlock -> you have to accept the prompt in order to continue -- this command will unlock the bootloader, but it will also erase the data on the device which is why a backup is necessary.
fastboot reboot-bootloader -- this will reboot the bootloader.
fastboot flash recovery openrecovery-twrp-2.3.1.0-grouper.img -- this will flash the custom recovery --please use the specific file and name for your particular Nexus device!
fastboot erase cache -- this will erase the cache -- might not be necessary but it's just as a precaution.
fastboot reboot -- this will reboot the device.
After Android 4.2 is loaded and running the SuperSU file must be copied from the "Root" folder to the internal storage (shows up in Windows Explorer as a Nexus device). A simple copy and paste will do the trick here.
Then you have to power off the Nexus device and enter "fastboot mode" again. Use the Volume Up and Volume Down keys to navigate until you can select "Recovery Mode". After the power button is pressed the device will reboot in the new custom recovery.
Rooting your Nexus device
If you have ClockworkMod installed, you have to perform the following steps:
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select "0" (zero) folder
Select "CWM-SuperSU-v0.97.zip"
Select "Yes - Install CWM-SuperSU-v0.97.zip"
Select "Go Back"
Select "reboot system now"
If you have Team Win Recovery Project installed, you have to perform the following steps:
Press "Install".\
Select "CWM-SuperSU-v0.97.zip" -- for me it's in the "0" (zero) folder
Swipe to confirm flash
Press "Wipe cache/dalvik" (just as a precaution)
Swipe to wipe
Press "Reboot System"
After Android 4.2 loads your device can run apps with elevated privileges (meaning it's rooted). A SuperSU app is installed in order to allow root requests, so please use your judgement on which apps you grant access.
If you experiences any problem, please reply and I will look into it.
Sent from my Nexus 7 using xda app-developers app
Sent from my Nexus 7 using xda app-developers app
^^you want him todo that, lmao, he doesnt even know how to put a file on his sdcard to flash it in recovery, theres no way a computer newb is going to be able to follow what you posted
That's why I have not used the word flash anywhere, I know that he does not know how to flash , I have posted the right thing for a total noob,( at least if he knows how to use command in windows or install drivers)
I helped him in the way I could and what he requested
Sent from my Nexus 7 using xda app-developers app
You think that helped. LOL. Your telling him to do things that aren't even required to gain root with this device. Not everything is a nexus bro. Next time you wanna help study up on the phone your giving advice about. lol
Well , thanks for telling me that every android isn't rooted in same manner, I was thinking that all devices are rooted in same ways like for my nexus
Sent from my Nexus 7 using xda app-developers app
naman14, im not putting you down, your step by step howto is admirable, good work, but the problem is that the op is clueless on tech stuff, its not the word "flash" he has a problem with, i could of said "install" and it would lead to same conclusion, he doesnt know how to copy a file to his sdcard, if he cant do that he has no business in modding his phone until he learns more. anyhow the op is long gone by now
I upgraded my samsung skyrocket s2 version 2.3.6 to 4.0.4 through the Kies. Then I tried to install TWRP 2.2.0 and Odin 1.85. I saw COM 14 ; COM 17 when I hit start button .It said
FAILED. Now it showed a yellow triangle in the middle of phone & monitor pictures. ( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again). Please help . Thank you very much.
I just tried other laptop . I saw COM 3 but it said it couldn't open the serial (COM )port . All thread completed (success 0/ failed 1)
How to root, how to install custom recovery last but not the least how to install custom ROM and make your Mobile FAST
How to ROOT
Step 1. You need to download MI4I TOOLKIT.
Step 2. Once file is downloaded extract .zip file.
Step 3. Go to your Phone Settings-About phone-Click MIUI version option and tap it for 7 times. After 7 taps, a notification should appear saying " You are now a developer"."Developer mode has been enabled" or "You have enabled Developer Options".
Step 4. Go to Settings-Additional Settings-Developers Options. Turn on USB Debugging.
Step 5. Go to the folder where you had downloaded the Toolkit . Open the folder you will found Start Command Prompt file (CMD FILE), and Right click on Start and Run as Administrator. (Make sure Xiaomi PC suit is not working in background to end the PC suit process , open Task Manager click on the process find Mi PC Suit select the process and click End Process).
Step 6. For rooting your phone:- press 1 and Press Enter and there will be a notification in your phone Allow this notification and your phone will go into Bootloader, have patience it will take 5 minutes.
After your phone is restarted you will find the APP called SUPERSU. Open supersu and update binary, click the Normal button and reboot your phone.
How to install CUSTOM RECOVERY
Step 1. Go to the folder where you downloaded the Toolkit. Open the folder you will found Start Command Prompt file (CMD FILE) and Right click on Start and Run as Administrator.
Step 2. Press 2 and Hit Enter and there will be a notification in your phone, Allow this notification and your will go into Bootloader, it will take 2 minutes. After your phone restarted TWRP CUSTOM RECOVERY is successfully installed.
Step 3. To find your phone is having custom recovery, you will have to press Volume UP and Power Button/Lock Button together about 6 or 7 seconds your phone will restarted in TWRP CUSTOM RECOVERY MODE.
How to install Custom ROM
BACKUP YOUR PHONE DATA IN SECURE PLACE for backup your data Download BACKUP App
Step 1. First thing first you need to select and download the custom rom. For ROMS click here.
Step 2. You need to download GAPPS (Google Apps i.e Play Store). For MI4I you will select PLATFORM-ARM64, ANDROID-it depends upon on your rom android version, VARIANT-if don't want lots of google apps download PICO either you need to download STOCK.
Step 3. Copy these zip file into your OTG Pen-drive or with the help of OTG cable and insert your pen-drive in your phone.
Step 4. Open your Custom Recovery (press Volume UP and Power/Lock Button together).
Step 5. When Custom Recovery is open click on WIPE-ADVANCED, WIPE-Tick Dalvik Cache, System, Cache and Data. Slide Swipe to Wipe Left to Right.
Step 6. Click On Home Button and now click install then Click UP A LEVEL swipe down you will found USB_OTG and Navigate your Custom Rom and GAPPS.
Step 7. Install Custom Rom, after installation wipe cache and install GAPPS when gapps is installed successfully, you need to wipe cache and format the data when data is formatted click on REBOOT-System.
This Process will take max 15 minutes.
Now you are successfully installed the ROM enjoy . PEACE
'fastboot' is not recognised as an internal or external command, operable program or batch file.
what did it mean. and im getting this when i press 1 to root my mi 4i .
i turned on usb debugging successfully .
what shall i do now
Pavankumar1999 said:
'fastboot' is not recognised as an internal or external command, operable program or batch file.
what did it mean. and im getting this when i press 1 to root my mi 4i .
i turned on usb debugging successfully .
what shall i do now
Click to expand...
Click to collapse
install fastboot drivers
https://www14.zippyshare.com/v/ufYG71o0/file.html
thwn follow process
Background:
So, I recently bought the, “Ulefone Armor 6” Android phone. I didn't do much research into rooting the phone before I bought it, however tonight I did and couldn't find any solution. So I made my own.
Disclaimer:
I am not responsible if you damage, brick, or willingly alter your phone in any way shape or form blah blah blah, you get the point.
Prerequisites:
Make sure you have drivers installed, here.
Rooting process:
1. Obtain a local copy of the, “boot.img” file from the stock rom archive, which can be found on the, “Ulefone” website.
2. Download the compressed file of your choice, "EU" or "Non-EU." (Ex. I downloaded the one for, "Non-EU" which is, "Armor_6_RF1_V01_user_20190329.tar.gz")
3. Extract the downloaded file in the location of your choice, using your favorite archive extractor (7-zip, winzip, winrar, etc...)
4. To begin the root process, Download the android app or .apk file "Magiskmanager.apk" from the Magisk Manager website, and install it in your, Armor 6 device. (Note: the Play Store does not have the, Magisk Manager app.)
5. Now pass the, "boot.img" file downloaded earlier from your computer to your Armor 6 device. Place the "boot.img" file preferably in the "downloads" folder of your Armor 6 device.
6. Open up the Magisk Manager app, and click, "install 19.3" (or what ever is the current version is) then click, "Select and Patch a File".
7. Locate your, "boot.img" file you placed in your downloads folder, and patch it with Magisk Manager. (Note: This step will create another file named, "Magisk_patched.img" in your device.)
8. After Magisk Manager has patched your file, pass the patched file from your downloads folder, back onto your computer. (Note: Not necessary but customary, to rename the patched file to, "boot.img")
9. Now, in your Armor 6 phone, go to your settings, scroll down to system click it, click on about phone, and then tap the crap out of build number, until you have become a developer.
10. Go back from about phone, click on developer options, and tick on "OEM unlocking." also scroll down and tick, "USB debugging."
11. Download ADB tools with fastboot from Android/Google.
12. With the phone connected to the computer, open up the folder where ADB is located in command prompt and type, "adb reboot bootloader"
13. Now that you are in fastboot mode, type the following prompts into the command. (NOTE: the following commands will WIPE your phone clean to stock, so backup any important files/documents before you wipe.)
fastboot oem unlock
OR (if the first one fails, try the second one)
fastboot flashing unlock
14. Once you have unlocked your bootloader, reboot the phone, "fastboot reboot", wait till the phone boots up, go through the setting up process, enable USB debugging again (Step 13), install magisk manager again, and "adb reboot bootloader" in adb command prompt.
15. Once in fastboot mode again, flash the patched, "boot.img" file. (Note: This command will not wipe your device.)
fastboot flash boot boot.img
16. Reboot the phone once more, open up magisk manager, and enjoy root.
A lot of steps yes, but simple easy to do.
Note: that the basis of my instructions on telling you what to do is my assumption of you the end user having basic if not full knowledge of what I am talking about. Because I wont be providing help for basic knowledge, if that makes sense. I do not plan on making a video as this tutorial is mainly meant for users who already know what of the majority they are doing with the tools they are using. If anyone wants to make a video feel free to share it here, I will added to the thread. thanks!
UPDATE 1.0:
I organized a thread on this link, with everything needed to root, twrp, and stock image.
UPDATE 1.2:
Re-organized this thread. Removed a few steps. Added more detail to this thread specifying a few things.
Extosis said:
Story:
I recently bought the, Ulefone Armor 6 Android phone. Didn't do much research into rooting before I bought it, however tonight I did and couldn't find any solution. So I made my own.
Disclaimer:
I am not responsible if you damage, brick, or willingly alter your phone in any way shape or form blah blah blah, you get the point.
Rooting procedure:
1. Get a local copy of the boot.img file from the Ulefone website (To make things simpler for you, Ulefone.com/index.html > Scroll down and click on "download" > Select your device model "Armor series" "Armor 6" > Scroll all the way down and click the download button for "The latest rom".)
2. Now you are at the google drive folder from Ulefone, with the files you need. Select EU if you have the EU version, or Non-EU for any other country.
3. Download the compressed file of your choice EU or Non-EU. (Ex. I downloaded the one for Non-EU which is, "Armor_6_RF1_V01_user_20190329.tar.gz")
4. Open the file in your favorite archiver software, 7-zip, winrar, etc.... open the first folder in the archive, and extract "boot.img"
5. Download, "Magiskmanager.apk" from their Magisk Manager, and install it in your, Armor 6 phone.
7. Pass the, "boot.img" file from your computer to your cellphone. Preferably the "downloads" folder.
8. Open up Magisk manager, and click install 19.3 (or what ever is the current version) then click "Select and Patch a File".
9. Find your "boot.img" file and patch it with magisk manager.
10. After magisk manager has patched your file, pass the patched file, back onto your computer.
11. Now, in your Armor 6 phone, go to settings, scroll down to system and click it, click on about phone, and then tap the crap out of build number, until you become a developer.
12. Go back from about phone, click on developer options, and tick on "OEM unlocking".
13. Scroll down and tick on USB debugging.
14. Download your ADB tools with fastboot from android/google.
15. With the phone connected to the computer, open up the folder where ADB is located in command prompt and type, "adb reboot bootloader"
16. Now that you are in fastboot mode, type the following prompts into the command. (NOTE: the following commands will WIPE your phone clean to stock, so backup any important files/documents.)
fastboot oem unlock
OR (if the first one fails, try the second one)
fastboot flashing unlock
17. Once you have unlocked your bootloader, reboot the phone "fastboot reboot", wait till the phone boots up, go through the set up process, enable USB debugging again (Step 13), install magisk manager again, adb reboot bootloader in adb command prompt.
18. Once in fastboot mode again, flash the patched boot.img file.
fastboot flash boot boot.img
19. Reboot the phone once more, open up magisk manager, and enjoy root.
A lot of steps yes, but simple easy to do.
Note: that the basis of my instructions on telling you what to do is my assumption of you the end user having basic if not full knowledge of what I am talking about. Because I wont be providing help for basic knowledge, if that makes sense.
Click to expand...
Click to collapse
Nice work around for a phone that doesn't have Twrp
([emoji813]9/[emoji725]/9[emoji813])
PoochyX said:
Nice work around for a phone that doesn't have Twrp
([emoji813]9/[emoji725]/9[emoji813])
Click to expand...
Click to collapse
Upon doing a bit more research, the phone actually has TWRP & a TWRP fork.
How do we know we can trust you? I'm a nubee as I've said.
SteeleB89 said:
How do we know we can trust you? I'm a nubee as I've said.
Click to expand...
Click to collapse
Then this isnt for you and stick with stock... Stock honestly works just certain people want greater freedom with thier phones only issue is with that you yourself at greater risk of breaking something and wouldn't know how to fix it and in situations like that factory restores wouldn't even save you because the system partition doesn't go back to the way it was with a factory restore
Sent from my SM-J327P using Tapatalk
I understand and accept the risk. I'm asking if this is a legit fix or some attempt to put malware on my phone.
SteeleB89 said:
I understand and accept the risk. I'm asking if this is a legit fix or some attempt to put malware on my phone.
Click to expand...
Click to collapse
Well to start with, I didn't attach anything in this thread, only photos.
1. You bought the phone, a phone that is made from a Chinese company, odds are that it already has malware, backdoors, or things you don't want on the OS.
2. Like I said, I didn't attach anything for you to download, so I am not infecting you with anything. Fastboot even comes with Google SDK.
3. Magisk is a wide known group who release root for the public to download/install. Just like TWRP, clockworkmod, cynaogenmod, etc...
4. If you don't feel comfortable doing this process, then like stated above, you should probably feel safer staying with stock & no root.
As I am sure, everyone who mod their devices are fully aware of the consequences of exploiting their devices. Brinking, killing, or messing something up.
Cheers.
For the life of me I cannot get the drivers to install. I've tried on Windows 10 and 7, but can't get fastboot to recognize the device. ADB works just fine, but Windows won't recognize the device when in recovery. I tried the official Ulefone drivers for Windows 10 and 7, as well as the MTK/VCOM usb drivers through manual installation.. How did you get it working? What other drivers are you using?
A.Fitz said:
For the life of me I cannot get the drivers to install. I've tried on Windows 10 and 7, but can't get fastboot to recognize the device. ADB works just fine, but Windows won't recognize the device when in recovery. I tried the official Ulefone drivers for Windows 10 and 7, as well as the MTK/VCOM usb drivers through manual installation.. How did you get it working? What other drivers are you using?
Click to expand...
Click to collapse
I have literally used the "driver installer" from the Ulefone website. Install the MTK/VCOM Drivers.
Adb gets detected in TWRP & Fastboot is found on my computer just fine.
My suggestion would be to check if your anti-virus (if you have one) if it's blocking the drivers from being installed.
Ps: I have the latest Windows 10 1903 x64 Edu and the drivers work perfectly.
Will try at end of month and tell you guys the result later.
Hi!!!
Thanks for the tutorial. I managed to root my Ulefone Armor 6.
Just one thing, maybe it will be nice to add in the tutorial (suggestion): Magisk generates another boot.img file, called magisk_patched. That is the one to be used on step 17 (rename it before).
One question. If I do a factory reset, will the phone remain rooted? Can't remember for the life of me from past roots I've done.
Stabys said:
Hi!!!
Thanks for the tutorial. I managed to root my Ulefone Armor 6.
Just one thing, maybe it will be nice to add in the tutorial (suggestion): Magisk generates another boot.img file, called magisk_patched. That is the one to be used on step 17 (rename it before).
One question. If I do a factory reset, will the phone remain rooted? Can't remember for the life of me from past roots I've done.
Click to expand...
Click to collapse
Oh most definitely. I am actually going to add more detail to this tutorial once I have the free time to do so. This tutorial was mainly supposed to be like a rough idea on how to do it. However yes, I did a factory reset not to long ago and root was maintained.
Update:
Added more information and cleaned the thread up.
Well, IDK if that's a common understanding or even if it's going to happen to everybody but.. Ulefone released an software update that undid the root and reinstalled every single native app that I had uninstalled. I tried rooting again, buuut they did not put the new rom in their website yet, so my phone got stuck in boot XD. So I reinstalled the ROM available using SP Flash Tool (thank god that worked, lost some information but that's fine).
I'm not sure if I'm going to root it again when they release the ROM in the website.. I wanted root so I could make Cerberus an native app, but even though I can do it, if the phone is reset Cerberus loses my account information, so it is no use to me.
English is not my native language, but I guess that's pretty understandable
@edit: They did not release the new rom in the official website.. I did not look into the Mega or Drive link actually.
Stabys said:
Well, IDK if that's a common understanding or even if it's going to happen to everybody but.. Ulefone released an software update that undid the root and reinstalled every single native app that I had uninstalled. I tried rooting again, buuut they did not put the new rom in their website yet, so my phone got stuck in boot XD. So I reinstalled the ROM available using SP Flash Tool (thank god that worked, lost some information but that's fine).
I'm not sure if I'm going to root it again when they release the ROM in the website.. I wanted root so I could make Cerberus an native app, but even though I can do it, if the phone is reset Cerberus loses my account information, so it is no use to me.
English is not my native language, but I guess that's pretty understandable
@edit: They did not release the new rom in the official website.. I did not look into the Mega or Drive link actually.
Click to expand...
Click to collapse
Yeah, I think their new rom has a few security updates as well as other updates.
I haven't updated as of yet, because I fear I will lose root. However if I ever do, I'll update everyone if successful.
I understand you very well too.
Hello again..
I've decided to stay on 2019.03.29 update.. Just to be able to uninstall those da** native apps..
I'd appreciate if you post here if or when you have any news about root in the latest wireless update.
Then again, can't say thanks enough.
Cheers.
Stabys said:
Hello again..
I've decided to stay on 2019.03.29 update.. Just to be able to uninstall those da** native apps..
I'd appreciate if you post here if or when you have any news about root in the latest wireless update.
Then again, can't say thanks enough.
Cheers.
Click to expand...
Click to collapse
Hello it's been a while.
I have updated to the latest version by Ulefone for our Armor 6's.
Version: 2019.06.05.
I was able to root it again, using the same method in this thread.
As for the native apps, I haven't tried to remove them, however I am sure it is possible to.
HELP!
Guys, I need some help here. For some reason I'm not able to find the file in the downloads folder. When i go to Magisk, the file is there, however I cannot find it with any file explorer or through the PC. Any help here??
Extosis said:
Background:
So, I recently bought the, “Ulefone Armor 6” Android phone. I didn't do much research into rooting the phone before I bought it, however tonight I did and couldn't find any solution. So I made my own.
Disclaimer:
I am not responsible if you damage, brick, or willingly alter your phone in any way shape or form blah blah blah, you get the point.
Prerequisites:
Make sure you have drivers installed, here.
Rooting process:
1. Obtain a local copy of the, “boot.img” file from the stock rom archive, which can be found on the, “Ulefone” website.
2. Download the compressed file of your choice, "EU" or "Non-EU." (Ex. I downloaded the one for, "Non-EU" which is, "Armor_6_RF1_V01_user_20190329.tar.gz")
3. Extract the downloaded file in the location of your choice, using your favorite archive extractor (7-zip, winzip, winrar, etc...)
4. To begin the root process, Download the android app or .apk file "Magiskmanager.apk" from the Magisk Manager website, and install it in your, Armor 6 device. (Note: the Play Store does not have the, Magisk Manager app.)
5. Now pass the, "boot.img" file downloaded earlier from your computer to your Armor 6 device. Place the "boot.img" file preferably in the "downloads" folder of your Armor 6 device.
6. Open up the Magisk Manager app, and click, "install 19.3" (or what ever is the current version is) then click, "Select and Patch a File".
7. Locate your, "boot.img" file you placed in your downloads folder, and patch it with Magisk Manager. (Note: This step will create another file named, "Magisk_patched.img" in your device.)
8. After Magisk Manager has patched your file, pass the patched file from your downloads folder, back onto your computer. (Note: Not necessary but customary, to rename the patched file to, "boot.img")
9. Now, in your Armor 6 phone, go to your settings, scroll down to system click it, click on about phone, and then tap the crap out of build number, until you have become a developer.
10. Go back from about phone, click on developer options, and tick on "OEM unlocking." also scroll down and tick, "USB debugging."
11. Download ADB tools with fastboot from Android/Google.
12. With the phone connected to the computer, open up the folder where ADB is located in command prompt and type, "adb reboot bootloader"
13. Now that you are in fastboot mode, type the following prompts into the command. (NOTE: the following commands will WIPE your phone clean to stock, so backup any important files/documents before you wipe.)
fastboot oem unlock
OR (if the first one fails, try the second one)
fastboot flashing unlock
14. Once you have unlocked your bootloader, reboot the phone, "fastboot reboot", wait till the phone boots up, go through the setting up process, enable USB debugging again (Step 13), install magisk manager again, and "adb reboot bootloader" in adb command prompt.
15. Once in fastboot mode again, flash the patched, "boot.img" file. (Note: This command will not wipe your device.)
fastboot flash boot boot.img
16. Reboot the phone once more, open up magisk manager, and enjoy root.
A lot of steps yes, but simple easy to do.
Note: that the basis of my instructions on telling you what to do is my assumption of you the end user having basic if not full knowledge of what I am talking about. Because I wont be providing help for basic knowledge, if that makes sense. I do not plan on making a video as this tutorial is mainly meant for users who already know what of the majority they are doing with the tools they are using. If anyone wants to make a video feel free to share it here, I will added to the thread. thanks!
UPDATE 1.0:
I organized a thread on this link, with everything needed to root, twrp, and stock image.
UPDATE 1.2:
Re-organized this thread. Removed a few steps. Added more detail to this thread specifying a few things.
Click to expand...
Click to collapse
babyboy_legolas said:
Guys, I need some help here. For some reason I'm not able to find the file in the downloads folder. When i go to Magisk, the file is there, however I cannot find it with any file explorer or through the PC. Any help here??
Click to expand...
Click to collapse
After I did the last flash with the boot.img, the phone keeps rebooting and rebooting. its like something on that image is wrong. the thins is, giving the fact the phone is continuing booting. How can i put it again to flash the original boot.img?
babyboy_legolas said:
After I did the last flash with the boot.img, the phone keeps rebooting and rebooting. its like something on that image is wrong. the thins is, giving the fact the phone is continuing booting. How can i put it again to flash the original boot.img?
Click to expand...
Click to collapse
To put the phone in manual fastboot mode, you have to power off your device first. By pressing both, "power button + volume down button" until you feel the phone vibrate.
Once the phone vibrates, quickly press, "Power button + volume up button" to view the fastboot/recovery/normal boot menu options. To select fastboot use the volume buttons.
Volume up = select
Volume down = move down through options.
Hi!
Oh I tried it once more now and managed to do it.
I did it with the ROM from Mega (20190605).
Thanks again!
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
Hello, I'm new here, I've been dealing with certain ROM mods for a little while. My test device is an old Samsung Galaxy S4 mini (GTI9195). Now I've been sitting for a few days trying to figure out how to bring my device up to date as best as possible. Lineage OS seemed the best to me. Unfortunately there is no officially confirmed software for my device directly from Lineage, which is why I looked elsewhere. I came across this thread on XDA: https://forum.xda-developers.com/t/...520-r890-unofficial-11-0-0-lineageos-18-1-for -s4-mini.4189967/ . The user arco68 is, so to speak, the boss among S4 mini modifications. Unfortunately, I can't find exact instructions anywhere (especially for the recovery) on how to install all the packages correctly. That's why I researched. I was able to record various steps, but cannot determine if they are correct. Can someone on this forum please help me? My steps:
1. Turn on developer options
2. Turn off OEM encryption (if available)
3. USB debugging on.
4. Download and install Android platform tools in Path
5. Download and zip Magisc
7. Put the phone in bootloader/fastboot/download mode (volume down + home)
8. Flash Team Win Recovery Project (or other custom recovery).
9. Restart phone and boot into recovery mode (volume up + home + power)
10. Erase all data
11. Copy Google Apps to Phone (Optional)
12. Copy Lineage OS (or other custom rom) to phone
13. Install packages one by one (OS first)
14. Reboot device
15. Wait and set up
Okay, First of all requirement-
A portable sd card- Because after flashing twrp, you might face issue where you can't access internal storage from twrp. That's because the phone might be encrypted. You have to decrypt it by flashing a "disable dm verity- forceencrypt.zip". In this case, you might not be able to transfer files from pc when booted into twrp. So, It's a smart move to insert a sd card containing all required files before to avoid these problems.
Another requirement is samsung drivers installed in pc. I will attach that file.
Follow these steps -
1/Unlock bootloader -Go to developer options. Turn on oem unlocking. It will tell you that you're going to loss all data. Proceed. If it doesn’t tell you anything, then there is definitely some extra process to unlock bootloader of your device.(search on internet)
2/Download your phone's official firmware in pc- it will help you if anything goes wrong. Search " Sm fw" on google. Go to first site. Create an account. Search the model number, Download a firmware that matches with all your device's information in "About phone".
3/ Download the lineageos rom and twrp recovery for your model. Then install device info hw from play store to check bits(32/64). Search open gapps. Go to the website. "arm" is for 32 bit & "arm64" is for 64 bit. Select which matches to your device’s bit. Then select the android version of the custom rom. Then select "Pico". Download the file. Next, download latest magisk 25.2 from github page. Rename the apk file to "magisk.zip" Move rom,gapps, magisk.zip to SD CARD. Keep twrp in pc.
4/In pc, download latest odin software. It's an special software for samsung download mode. (There is no fastboot mode in samsung)
5/Boot your device into download mode. And connect with pc.
6/In pc, extract the twrp file(If It's in zip format). Open odin software, Go to options, turn off auto reboot. Now select "AP" & select that extracted twrp file. Click open. Then hit start button.
(Note that most of the samsung devices can't boot stock rom after flashing twrp. So you have to flash custom rom to boot your device. Follow the next step)
7/Boot into twrp wipe>format data>type "yes". Press home button. Install>Select storage>SD card>select the rom.zip. Then add more zips> select the gapps.zip. Again, add more zips> select magisk.zip. After all, swipe to flash.
After installation, reboot device.
What if anything goes wrong?
Extract the stock firmware that you downloaded from sm fw. Connect device in download mode. Open odin, select AP,BL,CP,CSC file one by one. Start flashing. You device will be alive again.