Related
This guide is for you that have a new Xoom (WiFi only, US model) with Android 3.1 and want to
- get root access
- enable the external SD card unit
Please note that Android 3.2, which now is available for the US Wifi models, make this guide more or less obsolete. If your aim is to have root access, then there are probably simpler methods.
What you need to do can be encompassed in these following short steps (will be detailed later on) in the following order. Each step is required before you can proceed to the next one. However, make sure that you are very very careful and dont try to take any shortcuts. That may soft-brick your device, and you may have a difficult time to explain that to your wife ... You have been warned!
I strongly recommend you to read the entire guide before trying this. In fact, read it twice to ensure that you have understood everything. If there is wierd stuff that you dont understand, dont hesitate to ask. The reason for me writing this down is that I like to document what I have learned. This is to me an excellent way to ensure that I will remember what I just did. Another reason was that I could not find a single thread that encompassed all steps required. There are many different threads, but noone (that I could find) that really guides you from start to goal. So enjoy and good luck!
I would like to thank LandMaster and cam30era for helping out with advice during my initial trail-and-error session. I soft-bricked my device once and had big problems to get by point 4.3 (avoid overwriting of CWM), but with their encouragement I finally succeeded.
If someone else adapts this guide for the EU model or the 3G model, feel free to drop me an IM and I will update the guide for these devices too. Until then, this has only been tested on a WiFi only, 32 GB device bought in the US. If you brick your 3G or EU bought model, dont call me ...
0. Overview of the 6 required steps
1. Install Motorola USB drivers for your computers (for USB connectivity)
2. Install Java SDK and Android SDK tools (for adb and fastboot commands)
3. Unlock the device for flashing (allowing replacement of recovery and boot images)
4. Install a modified recovery image (ClockWorkMod recovery for Android)
5. Root the device (Allow r/w access to the device filesystem)
6. Flash a kernel that supports the SD card (SD card access, overclocking etc.)
Steps 1, 2, 4, 5 and 6 require that you download install, image and zip files needed for the flashing.
All this was performed on a Windows XP x86 SP3. Windows 7, Mac and Linux users will probably have to do some steps differently.
Update July 7: I have tested the procedure on Windows 7 x86 now and the procedure is identical to Windows XP.
1. Install the latest Motorola USB drivers
The installation file can be found here
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
1.1 Install the drivers and ensure that your Xoom is recognized by the computer
2. Installation of development software
Java SDK 6 and Android SDK (for Honeycomb at least) need to be installed. You can find the installation kits here.
http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html
http://developer.android.com/sdk/index.html
2.1 Install them as any other software.
2.2 What I had to do was to manually modify the PATH environment variable. I use Windows XP so I did that by right clicking on My Computer, choose Properties and select Advanced. Here I added the path to platform-tools and Tools
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\QuickTime\QTSystem\;D:\Java\Android-sdk\platform-tools;D:\Java\Android-sdk\tools
Note: If the Android SDK complains that the Java Dev Kit cant be found, just press Back and then Next again. Wierd, but that seems to do the trick ... go figure.
2.3 Test that ADB and FASTBOOT works. You should open a command window and go to your Android installation directory. Plug in your Xoom to your computer and write 'adb devices'. Your Xoom should now be listed like this
C:\Documents and Settings\Anders>adb devices
List of devices attached
0288414343813157 device
Did your device not show up? Make sure that you have USB debugging enabled in Settings / Applications / Development
3. Unlocking the device for flashing
This step will effectively erase the internal storage, including all your apps and settings. Use whatever backup you want to rescure important data before you start.
3.1 Power up and start the Xoom
3.2 Ensure that your device is fully recognized by the computer. A good sign is that the 'Portable device' dialog is activated on Windows when your Xoom has booted. The Xoom should also be seen in 'My Computer'. If not, go back to step 2 and double check your USB drivers.
3.3 Use the command 'adb reboot bootloader' to go into Flash mode
3.4 Use the command 'fastboot oem unlock'. This will trigger a dialog on your Xoom. Follow the instructions on the screen to complete the unlocking. I repeat, this *will* do a factory reset and all data will be lost!
3.5 Once unlocked, the Xoom will restart and work as normal, but now ready for step 4
4. Install recovery image (CWM)
Download the recovery image file and save it to your computer
4.1 Boot into flash mode with 'adb reboot bootloader'
4.2 Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
4.3 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.4 Enter CWM with the following procedure
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ...
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. There are ways to prevent this (see posts below), but I recommend you to redo step 4 instead of messing with removal of system files. But both methods would probably work. Experiment!
5. Rooting the Xoom
The root zip file is located here
5.1 You need to transfer the ROOT zip file to a working micro SD card. You can do this on a computer or cell phone, but the ROOT zip must be located in the root directory of the SD card.
5.2 Insert the now prepared SD card in the Xoom
5.3 Boot into recovery (as described in 4.3). Navigate using the volume buttons and press the power button to select the active option
5.4 Select 'Install ZIP from sd card'
5.5 Select 'Choose ZIP'
5.6 Navigate to the ROOT zip file with the Volume buttons and select it with the Power button. Confirm that you want to install it.
5.7 Everything should indicate success, so back out to the main CWM menu and reboot the device.
5.8 From Android Market, install the ROM Manager app and start it. If the rooting was successful, then ROM Manager should start without any complaints.
6. Flashing a new kernel that supports SD cards (and maybe more ...)
The kernel that I used is described here http://forum.xda-developers.com/showthread.php?t=978013
The kernel zip file is located here
6.1 This step is identical to 5, but swap the ROOT zip towards the KERNEL zip. For simplicity, you may want to prepare the SD card with both zip files at the same time in step 5.1 ...
Looks great. You just might want to give credit to LandMaster and cam30era, too.
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
okantomi said:
Looks great. You just might want to give credit to LandMaster and cam30era, too.
Click to expand...
Click to collapse
Of course, done
juDGEY2k10 said:
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
Click to expand...
Click to collapse
This is only tested on a US device. OP updated.
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
When you unlock your Xoom, it will wipe all user data.
bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
You're right. I rooted 1st and flashed CWR later. I then used brd's method to update to 3.1, re-root and flash the new bootloader and kernel. So there is a step missing after Step 3. I'm sorry, I don't remember exactly how to do this from HC 3.1. (meaning what files to use) as I was on HC 3.0 at the time.
BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
Yes it will. Read 3.4 again, it will do factory reset.
The root file may vary from case to case, but the procedure is the same AFAIK. I used the one that "charge light off"... There are probably others too.
bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
This is true, and I will update the OP to reflect that.
So has anyone followed this guide successfully yet? I don't really want to be the first...
yordikins said:
So has anyone followed this guide successfully yet? I don't really want to be the first...
Click to expand...
Click to collapse
Hi
I did!. And you know that someone gotta be first (actually second). Why not take the credit?
pingvinen said:
This is true, and I will update the OP to reflect that.
Click to expand...
Click to collapse
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App
Abracastabya said:
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
cam30era said:
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
Click to expand...
Click to collapse
Sounds good and thanks B-)
Sent from my Xoom using XDA Premium App
Tnx . Very help full .
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).
rmcsc said:
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).
Click to expand...
Click to collapse
Try again, and remember that timing (3 seconds) are key to success ...
I'll retry being more precise. I do get into Recovery and I flash the file mentioned. It seems it flashes correctly but when I boot into the OS, there's no signs of root anywhere.
I'll update in a few. Thanks!
Sent from my T-Mobile G2 using Tapatalk
Note: This is for the Find 7 (the QHD version) not the 7a. I tested it on the x9076.
Note 2: I am on a Mac, so these instructions explain how to install Cyanogen on a Mac.
Note 3: If this is the wrong forum feel free to move it.
Note 4: The Find 7 is one of the few phones you can install 3rd party ROMs on without voiding your warranty.
Download Files
Get the simplified Fastboot and ADB package from here:
http://www.oppoforums.com/threads/find-7a-s-team-gummy-recovery.17476/
Get the boot.img from here:
http://www.oppoforums.com/threads/find-7a-s-team-gummy-recovery.17476/
Get Cyanogenmod nightly for 7a here (the branch supports both 7 and 7a):
http://download.cyanogenmod.org/?device=find7
Get Cyanogenmod google apps for KK:
http://wiki.cyanogenmod.org/w/Google_Apps
Get Android File Transfer for OS X here:
http://www.android.com/filetransfer/
You have now downloaded all the components you need.
Copy Files to your Find 7
Put all the zip files into a fresh folder to make them easy to find.
Rename the .img file to recovery.img.
Install Android File Transfer and restart your Mac or restart Finder.
Plug your phone into your Mac
Close the dialog informing you that the filesystem of the device you plugged in can't be read.
Android File Transfer will pop up automatically and open a folder view. If it doesn't, pull down the shade on your phone and try toggling between the two filesystem options (Image and File).
Copy the Cyanogen zip and the Google Apps zip onto your phone in the Download folder on your Find 7.
Install Bootloader
Turn on your phone and hold Power until the power off menu pops up.
Touch Power Off.
Immediately press and hold Volume Up.
Your phone will reboot into Fastboot.
Note: The words "Fastboot" appear in tiny, dim letters in the middle of the display.
Open a terminal on your Mac.
cd into the folder where you put your files.
Type the following commands:
Code:
chmod +X ./fastboot
./fastboot flash recovery recovery.img
You'll see some status go by on the terminal, then it will return to the command prompt.
Reboot Into Recovery, Wipe and Flash New Software
In your Mac terminal type:
Code:
./fastboot boot recovery.img
Wait for the recovery to load on your Find 7 and show the menu.
Use the volume down key to move to Wipe Data & Factory Reset.
Select this option and confirm.
After the wipe is done, go to Install Zip from SD Card (you're not actually installing it form an SD card, it just says this because the internal flash storage emulates an SD card).
Browse to the folder you put your Cynogen and Gapps zips into.
Select the Cyanogen zip to flash it and confirm you want to do that.
Repeat the process to flash the Gapps zipp.
Use +++GO BACK+++ until you return to the main menu.
Select Reboot.
If all goes well your phone will boot into Cyanogenmod.
The first boot can take several minutes, so be patient and don't yank the battery.
After first boot you'll be taken through the onboarding.
When the onboarding is done your Google stuff will start to syncronize and you'll be notified that you need to update Google Play Services.
Update Google Play Services, wait for Android to finish downloading app updates, then reboot your phone.
You're now ready to use Cyanogen on your Find 7.
Note: I found that upgrading the Google Search app included in the GApps package with the one from the Play Store breaks Google Now hotword detection on my phone. If you encounter this you can wipe, re-install gapps package, then go into the Play Store, browse to Google Search, hit the menu key and uncheck Automatic Update to stop it updating when you use Update All.
Note: This is a pretty unstable build.
In my testing I found that it crashed and hung a lot, and that many apps did not work as expected (force closes, refusal to install apk's, etc).
Also you will lose all the special camera features. You can't just port the camera apk because it has some system dependencies.
Ultimately I went back to ColorOS because this build doesn't seem to be ready for daily use.
Here's a bonus tip: If you install the Chinese version of ColorOS from here, you can go to About Phone > Updates and update to 2.14 Beta.
Edit: Gummy is a really good, stable, functional ROM. The only thing it's missing is the special camera app.
looking forward for Windows' instruction :laugh:
Anyway, thank you so much for posting instruction!
Is the VOOC still working? Is the 3GB apps limitation gone?
doomboss, attached is the fastboot with the gummy recovery in place for windows.
Just put your phone into fastboot follow the instruction of majikfox by putting the CM and Gapps zip file into your phone root folder.
Open command prompt on the fastboot folder by clicking shift+right click =Open command window here.
Then type the command:
fastboot flash recovery recovery.img
Once done
type:
fastboot boot recovery.img
and follow on the instruction of majikfox
1.Wait for the recovery to load on your Find 7 and show the menu.
2.Use the volume down key to move to Wipe Data & Factory Reset.
3.Select this option and confirm.
4.After the wipe is done, go to Install Zip from SD Card (you're not actually installing it form an SD card, it just says this because the internal flash storage emulates an SD card).
5.Browse to the folder you put your Cynogen and Gapps zips into.
6.Select the Cyanogen zip to flash it and confirm you want to do that.
7.Repeat the process to flash the Gapps zipp.
8.Use +++GO BACK+++ until you return to the main menu.
9.Select Reboot.
lexta said:
Is the VOOC still working? Is the 3GB apps limitation gone?
Click to expand...
Click to collapse
I'm having the same question also... looking forward! :good:
Which gapps do u need? 4.4.4 or 4.4.3?
bobbydigital222 said:
Which gapps do u need? 4.4.4 or 4.4.3?
Click to expand...
Click to collapse
Both version are fine just that do not download the version that will get overwritten by google camera.
Read all the package description. Safer to download the Micro modular package
kaiwong1020 said:
I'm having the same question also... looking forward! :good:
Click to expand...
Click to collapse
VOOC is not software related, so it should work.
Skickat från min GT-I9300 via Tapatalk
Exculpo said:
VOOC is not software related, so it should work.
Skickat från min GT-I9300 via Tapatalk
Click to expand...
Click to collapse
so CM should not have the 3GB apps storage issue :fingers-crossed:
Exculpo said:
VOOC is not software related, so it should work.
Skickat från min GT-I9300 via Tapatalk
Click to expand...
Click to collapse
VOOC is a hardware thing. It worked fine for me.
My answer was regarding whether the VOOC charger would work or not in 3rd party ROMs. The storage limit isn't that easy to just incorporate in a ROM since changes in the partition table would have to be made. Just settle with 3Gb for now and wait for a safer way to unify/modify the partitions. Who knows, you just might be fine with 3Gb for now
Skickat från min GT-I9300 via Tapatalk
Exculpo said:
My answer was regarding whether the VOOC charger would work or not in 3rd party ROMs. The storage limit isn't that easy to just incorporate in a ROM since changes in the partition table would have to be made. Just settle with 3Gb for now and wait for a safer way to unify/modify the partitions. Who knows, you just might be fine with 3Gb for now
Skickat från min GT-I9300 via Tapatalk
Click to expand...
Click to collapse
Just read in oppoforums that CM will be coming real soon for find7 but is a standard version. Hopefully the solution for unifying the storage will be ready soon.Everyone is waiting for that
lexta said:
doomboss, attached is the fastboot with the gummy recovery in place for windows.
Just put your phone into fastboot follow the instruction of majikfox by putting the CM and Gapps zip file into your phone root folder.
Open command prompt on the fastboot folder by clicking shift+right click =Open command window here.
Then type the command:
fastboot flash recovery recovery.img
Once done
type:
fastboot boot recovery.img
and follow on the instruction of majikfox
1.Wait for the recovery to load on your Find 7 and show the menu.
2.Use the volume down key to move to Wipe Data & Factory Reset.
3.Select this option and confirm.
4.After the wipe is done, go to Install Zip from SD Card (you're not actually installing it form an SD card, it just says this because the internal flash storage emulates an SD card).
5.Browse to the folder you put your Cynogen and Gapps zips into.
6.Select the Cyanogen zip to flash it and confirm you want to do that.
7.Repeat the process to flash the Gapps zipp.
8.Use +++GO BACK+++ until you return to the main menu.
9.Select Reboot.
Click to expand...
Click to collapse
I actually managed to install custom recovery and flashed CM11 already But I am just waiting for someone to post an instruction so that other people can have a clue of what they need to do (I am too lazy to write it ). Looks like this is the post that will help people using Windows :good::good::good::laugh::laugh::fingers-crossed:
Hmm. Fastboot cant find the device. Do we need drivers for Oppo find 7?
Edit: Switched pc. Now erverything works.
Exculpo said:
My answer was regarding whether the VOOC charger would work or not in 3rd party ROMs. The storage limit isn't that easy to just incorporate in a ROM since changes in the partition table would have to be made. Just settle with 3Gb for now and wait for a safer way to unify/modify the partitions. Who knows, you just might be fine with 3Gb for now
Click to expand...
Click to collapse
I tried to check this "limitation" and you could go really far away from it. I installed Asphalt8 (1GB) + GT Racing2 (1.4GB) + The Cave (1.5GB) and all my used apps (some have more than 100MB apk's size) and I still have space left (and no low storage notification).
I'm using ColorOS-1.2.2i without any modifications (it's just rooted) ...
Enjoy !
MrJiM said:
Hmm. Fastboot cant find the device. Do we need drivers for Oppo find 7?
Edit: Switched pc. Now erverything works.
Click to expand...
Click to collapse
When you plug in your phone, it should show you the OPPO driver. Double click on it to install the driver. I don't know if you need driver to access fastboot but doesn't hurt to try
last nightly (cm-11-20140703-NIGHTLY-find7) not work
blank screen when lock then unlock
I've been running the 7/3 nightly all day...no problems...no black screen.
Are you using the X9076?
Sent from my X9076 using XDA Free mobile app
***
All thanks go to our awesome XDA-Developers, the developers at Oppo, and also to scumpicule for this working root method.
It doesn't require any alterations to the recovery system, just stick with the one that Oppo has provided.
This has only been tested on the X9076, it should theoretically work for other versions of the Find 7 as well, but please do this under your own discretion.
**Update: It has been reported that the newest Rom release of 1.2.2i or 1.2.3i and onward might not work with this root method! If this is the case, you will need to use these instructions from this post: http://forum.xda-developers.com/showpost.php?p=53902937&postcount=10
________________________________________________________________________________
CONTINUE with these instructions if you have Rom Version: 1.2.1i, otherwise if you have updated, click on the above link ^
INSTRUCTIONS:
Download the "Find7_ROOT4.3_bbs.oppo.cn.zip" file.
** It is also available at:
http://forum.xda-developers.com/showthread.php?t=2739102&highlight=find+7 **
Then Copy/Paste it in your phone on your root folder
Turn Off your phone
Simultaneously press the buttons ' power ' and 'volume down ' until you feel a vibration.
Your phone will reboot into recovery mode. ( Should be the OPPO recovery ! )
Select ' Choose English ' & Install zip file
Then choose the zip file that you have downloaded in step 1 & click "YES" to install.
Hit "Reboot" once everything is completed.
Go into app drawer and select the SuperSU app. Update the binary by selecting the "NORMAL" method.
Reopen SuperSU and make sure binary is okay.
Try downloading "Root Checker" or a app that requires root.
Congratulations, your device is now Rooted!!
________________________________________________________________________________
If you run into any errors, try updating the SuperSU binary again, or check under "NOTES" on the link above that scumpicule has posted.
________________________________________________________________________________
HIT THE THANKS BUTTON IF THIS HAS HELPED YOU.
Credits & Thanks
@karben @kedro @tk @Jimmy McGee
@scumpicule
installation failed unfortunately
i followed your steps and my device number is X9076
crackjas said:
installation failed unfortunately
i followed your steps and my device number is X9076
Click to expand...
Click to collapse
I'm pretty sure I used the same .zip file earlier today with the stock recovery, installation failed here too. (X9076).
Fortunately this worked perfectly: Click Here
binaryfalcon said:
I'm pretty sure I used the same .zip file earlier today with the stock recovery, installation failed here too. (X9076).
Fortunately this worked perfectly: Click Here
Click to expand...
Click to collapse
Thanks. It works!:good:
crackjas said:
installation failed unfortunately
i followed your steps and my device number is X9076
Click to expand...
Click to collapse
Were you able to get to SuperSU in the app drawer? Make sure that the binary was installed properly.
It's interesting because I was able to get it to work perfectly.
See attached photos of Root Checker.
Does not work on ColorOS 1.2.2i
I just got my Find 7 phone and after the OTA upgraded the system to 1.2.2i, when I tried to install the root file and it failed to install.
Installation Failed
No luck. Failed at the zip file installation part. Please let me know if you have any solution. Thanks. Cheers.:cyclops:
KoTP said:
No luck. Failed at the zip file installation part. Please let me know if you have any solution. Thanks. Cheers.:cyclops:
Click to expand...
Click to collapse
I'm having the same problem. When installing the zip from Oppo Recovery, it fails immediately every time. Tried both the Find7_ROOT4.3 and the Find7_GSM4.3 files. Any suggestions?
I think that after the update to 1.2.2i, the root might not work anymore. For all those that don't have it working, can you confirm if you have the 1.2.2i Rom version?
Sent from my X9076 using XDA Free mobile app
Good news!
I have found the Rooting method and instructions for Rom version 1.2.2i
It should work for every Oppo Find 7 and 7a (not confirmed) with any system (till 1.2.2i at least).
In the end system, bootloader and recovery will be intact - > stock rooted.
WORKING ON: x9077, x9076, x9006 (confirmed by #Oiler)
(NOTE):
Android SDK is required (which gives ADB and FASTBOOT files), if you have these files already on your computer, then you can just download TWRP, STOCK RECOVERY (oppo), and SUPERSU.
All the files are located below:
Preparation:
1. Phone with at least 30% battery.
2. Install Oppo drivers from "OPPO Driver" phone partition.
3. Download and unzip: AndroidSDKSlim - https://mega.co.nz/#!SEhFXbzL!Xy4PrX_NKFnAZvPaggQL-1Vw1PESzRCyqXiPrMlvWVM
4. Download: TWRP - https://mega.co.nz/#!gF0GhBzT!HGaWCcQfqr_ns2z7ZEIeeF-0KvXFliEOAFZ_Z-wHcdw and put it in "platform-tools" folder wich u get from zip above. (img file)
5. Download: Stock Recovery - https://mega.co.nz/#!rVQWXKhD!Ljy9pw_sy0VlKzxqJwuD4UoZGMwF_dOmOYWgR1mMRc4 Mod or Stock Recoveryhttp://ge.tt/2EQ5h2m1/v/0?c *2 and put it in "platform-tools" folder. (img file)
6. Download: SuperSU - http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip?retrieve_file=1 and put it on phone internal storage. (do not unpack)
Changing Recovery Menu:
1. Turn Off phone.
2. Press Volume UP + Power
3. Now u should see small discription on screen: fastboot
5. Plug the phone to PC.
4. Open command prompt inside "platform-tools" folder -> press SHIFT + Right Mouse Click, pick open command prompt here.
5. Write:
Code:
fastboot devices
6. You should see:
Code:
"your phone product code" Dartmoor
7. If you don't see your device listed, make sure drivers are installed properly. Next, write:
Code:
fastboot flash recovery twrp-x9077.img
after few second you should see OKAY. (No need to turn off phone) *1
Rooting the phone:
1. Power off the phone.
2. Hold volume DOWN and the POWER button to get into the TWRP Recovery.
3. Pick install and find the SuperSU zip file, confirm the flash.
4. Reboot the phone. (cash and davlik wipe not nessesary)
5. Phone is now rooted. (Check if there is working SuperSU app. Update binary if needed.)
Restoring stock Recovery Menu:
1. Power off the phone.
2. Press Volume UP + Power
3. Open command prompt on your PC inside "platform-tools" folder -> press SHIFT + Right Mouse Click, pick open command prompt here.
4. Write:
Code:
fastboot flash recovery x9077-official-recovery-mod.img
after few second you should see OKAY.
5. REBOOT, or turn off phone by pressing POWER for 3 sec.
6. Check Recovery Menu (Volume DOWN + Power)
____________________________________________________________________
NOTES:
*1 turning off after installing Recovery Mod is unnecessary, this is because the phone won't startup automatically into the installed Recovery Mod.
*2 Stock Recovery is provided as genuine by #Zeus (Oppo Official Staff). The other one - Stock Recovery Mod is provided by #Kedros which have removed checking of Oppo system (provides possibility to install custom files like roms or SuperSU etc.). #Kedros confirmed that OTA update is still available on it.
____________________________________________________________________
Give a Like if it helped
SOURCE: Jach0o from OPPO forums
JiraffeLeung said:
I think that after the update to 1.2.2i, the root might not work anymore. For all those that don't have it working, can you confirm if you have the 1.2.2i Rom version?
Sent from my X9076 using XDA Free mobile app
Click to expand...
Click to collapse
Yes. Mine is 1.2.2i
Same for me on the version number. 1.2.2I I was hoping the process would be easier. Oh well.
The link to the TWRP recovery is down. I tried to download it in every possible way, but I always get an error. WHen I click download once I get to MEGA, it is saying "temporary error, retrying". Please fix, thanks.
Edit - NM working now, thanks just in case you fixed it.
Edit - Rooted phone, left TWRP on if I ever go to CM11s. Had to do a few things diffrent than what you said, but got it to work. Thanks
JiraffeLeung said:
Good news!
I have found the Rooting method and instructions for Rom version 1.2.2i
It should work for every Oppo Find 7 and 7a (not confirmed) with any system (till 1.2.2i at least).
In the end system, bootloader and recovery will be intact - > stock rooted.
WORKING ON: x9077, x9076, x9006 (confirmed by #Oiler)
(NOTE):
Android SDK is required (which gives ADB and FASTBOOT files), if you have these files already on your computer, then you can just download TWRP, STOCK RECOVERY (oppo), and SUPERSU.
All the files are located below:
Preparation:
1. Phone with at least 30% battery.
2. Install Oppo drivers from "OPPO Driver" phone partition.
3. Download and unzip: AndroidSDKSlim - https://mega.co.nz/#!SEhFXbzL!Xy4PrX_NKFnAZvPaggQL-1Vw1PESzRCyqXiPrMlvWVM
4. Download: TWRP - https://mega.co.nz/#!gF0GhBzT!HGaWCcQfqr_ns2z7ZEIeeF-0KvXFliEOAFZ_Z-wHcdw and put it in "platform-tools" folder wich u get from zip above. (img file)
5. Download: Stock Recovery - https://mega.co.nz/#!rVQWXKhD!Ljy9pw_sy0VlKzxqJwuD4UoZGMwF_dOmOYWgR1mMRc4 Mod or Stock Recoveryhttp://ge.tt/2EQ5h2m1/v/0?c *2 and put it in "platform-tools" folder. (img file)
6. Download: SuperSU - http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip?retrieve_file=1 and put it on phone internal storage. (do not unpack)
Click to expand...
Click to collapse
Great stuff.
Feel free to share how you got it Rooted and which steps you took. It will help others here as well.
Sent from my X9076 using XDA Free mobile app
JiraffeLeung said:
Great stuff.
Feel free to share how you got it Rooted and which steps you took. It will help others here as well.
Sent from my X9076 using XDA Free mobile app
Click to expand...
Click to collapse
Total newbie. Could you explain preparation step 2 to me? (2. Install Oppo drivers from "OPPO Driver" phone partition.)
Will this method work with version 1.2.3i?
Many thanks.
Hey, yes the method should work for the most recent version as well. When you plug in your phone to you pc, it prompts you install the drivers from OPPO, just continue and install them.
If you don't see "Developer Options" in your settings ( in "More" ) then go into "About Phone" and click on "Build number" 5 times until you receive a message indicating that developer options is enabled.
Then plug in your phone and see if the drivers get updated. This process has been tested to work on Windows 7.
Sent from my X9076
I'm eager to try
JiraffeLeung said:
Hey, yes the method should work for the most recent version as well. When you plug in your phone to you pc, it prompts you install the drivers from OPPO, just continue and install them.
If you don't see "Developer Options" in your settings ( in "More" ) then go into "About Phone" and click on "Build number" 5 times until you receive a message indicating that developer options is enabled.
Then plug in your phone and see if the drivers get updated. This process has been tested to work on Windows 7.
Sent from my X9076
Click to expand...
Click to collapse
Thanks. Just waiting to find the time to try. I'll post the result.
Thanks again.
One more thing, you'll have to enable "USB Debugging" in developer options, then try plugging the phone in again.
Failed
JiraffeLeung said:
One more thing, you'll have to enable "USB Debugging" in developer options, then try plugging the phone in again.
Click to expand...
Click to collapse
Hi,
Thanks a lot for your help.
Though I'm pretty sure I've followed your instructions to the letter the phone would fail to install the update.SuperUser file so I can't get to get it rooted.
Any idea, suggestion, tip etc, will be much appreciated.
Thanks
How far were you able to get to? Any errors or freezing? What version of Rom are you on?
EDIT 8/2/19: I do not own this device anymore. So i cannot and dont know if anything changed about the procedures unlocking rooting etc. BUT if you are getting any trouble i might can help you. Comment your thoughts below
Hey guy, i saw a lot of guys here wondering how to root and flash twrp recovery on thier devices . Today i am gonna show you how to do that.
First of all make sure 3 things :
1. backup your images, contacts, music tracks etc on a external SD CARD, or on your computer.
2. You MUST have the BOOTLOADER unlocked. To do that, read this guide http://en.miui.com/thread-202290-1-1.html
3.Charge your device to 80%+
HOW TO FLASH TWRP AND ROOT MI MAX
1. Go to Settings-About phone-Find the MIUI VERSION, and tap on it for 5-10 times.
2. Go back to settings, sellect adittional settings. click on Developer options, and select enable
3. Find the option USB Debugging and enable it.
4. Download the TWRP recovery from the link
5. rename the file to 'recovery.img'
6. Move the image to the same file where the ADB was installed ( it should be on Computer-> C: -> Adb )
7. Open the adb folder
8. Press and hold the shift key and right click in the folder
9. click on the option "Open command window here"
10. Boot your device on fastboot mode by turning it off, pressing Power and the Volume Down buttons together, and then connect it with your computer
11. First type this command "fastboot devices" to check if your device is into fastboot mode
12. Enter the command "fastboot flash recovery recovery.img"
13. Enter the command "fastboot boot recovery.img"
14. Your phone is now in TWRP recovery mode ( if it is not, the write on ADB: reboot recovery )
15. select Install Zip and click on 'SuperSu.zip'
16. corfirm the flash
17. reboot your device
18. DONT PANIC IF YOU DEVICE WONT TURN ON. Sometimes need to wait 10-20 secs.
DOWNLOADS
1. ADB- (https://forum.xda-developers.com/showthread.php?t=2588979)
2. XIAOMI MI MAX HYDROGEN DRIVERS (http://xiaomiadvices.com/download-xiaomi-usb-drivers/)
3. TWRP RECOVERY IMAGE https://dl.twrp.me/hydrogen/ LATEST VERSION IS twrp-3.2.3-0
4. BetaSuperSu 2.74 http://www13.zippyshare.com/v/OFQGvIyA/file.html
RESERVED
The thread must be removed to XIAOMI MI MAX GUIDES, NEWS, & DISCUSSION
Hallo Friend!
I am about to test your guide. I think it is most decent among other guides on the net...
Could you please just tell me if it's gonna work on:
Android 6.0.1 MMB29M
MIUI 8.2.1.0 (MBCMIDL) Stable
kernel 3.10.84-perf-gfe86e7b
bootloader UNLOCKED
Is superSU by default included in the TWRP you gave? No need to download it additionally from somewhere?
What about warning about "dm-verity" on official TWRP website?
This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
Click to expand...
Click to collapse
Should this be any concern that the phone will not boot up again? Should this be disabled first?
Is it better to use the TWRP version you provided (3.0.3.0? not listed on official TWRP website? why?) or the lastest 3.1.0.0?
noob456 said:
Hallo Friend!
I am about to test your guide. I think it is most decent among other guides on the net...
Could you please just tell me if it's gonna work on:
Android 6.0.1 MMB29M
MIUI 8.2.1.0 (MBCMIDL) Stable
kernel 3.10.84-perf-gfe86e7b
bootloader UNLOCKED
Is superSU by default included in the TWRP you gave? No need to download it additionally from somewhere?
What about warning about "dm-verity" on official TWRP website?
Should this be any concern that the phone will not boot up again? Should this be disabled first?
Is it better to use the TWRP version you provided (3.0.3.0? not listed on official TWRP website? why?) or the lastest 3.1.0.0?
Click to expand...
Click to collapse
hello, please write again your problem. I can understand what do you mean.
StonebridgeGr said:
hello, please write again your problem. I can understand what do you mean.
Click to expand...
Click to collapse
Ok just two questions then, because I'm not sure what you can't understand. Please explain.
1) What Android, MIUI and kernel did you root?
2) Do you have SuperSu.zip in TWRP 3.0.3 by default? You didn't say anything in your guide about downloading it and from where + what version.
noob456 said:
Hallo Friend!
I am about to test your guide. I think it is most decent among other guides on the net...
Could you please just tell me if it's gonna work on:
Android 6.0.1 MMB29M
MIUI 8.2.1.0 (MBCMIDL) Stable
kernel 3.10.84-perf-gfe86e7b
bootloader UNLOCKED
Is superSU by default included in the TWRP you gave? No need to download it additionally from somewhere?
What about warning about "dm-verity" on official TWRP website?
Should this be any concern that the phone will not boot up again? Should this be disabled first?
Is it better to use the TWRP version you provided (3.0.3.0? not listed on official TWRP website? why?) or the lastest 3.1.0.0?
Click to expand...
Click to collapse
This twrp. Img it's for all the versions but only for mi max. Not the prime . This twrp doesn't contain superSU. If I remember correctly. But if on the TWRP contain the super su. Don't say yes. Just flash it like I saying on the guide. Maybe they upload a newest version. You can use the new. I think I put the official website . I will check it.
Ok thanks for the answer. Please check from where I download SuperSu - which version would be best.
Please tell me your Android, kernel and MIUI version that you rooted.
noob456 said:
Ok thanks for the answer. Please check from where I download SuperSu - which version would be best.
Please tell me your Android, kernel and MIUI version that you rooted.
Click to expand...
Click to collapse
LOL I forgot to add the superSU link...
That's what I told you. Then please do.
noob456 said:
That's what I told you. Then please do.
Click to expand...
Click to collapse
ok on the first post you can find all the links. if i miss something please tell me here !
Is this beta version of SuperSU reliable? Did you use it? Not better to use a stable version?
noob456 said:
Is this beta version of SuperSU reliable? Did you use it? Not better to use a stable version?
Click to expand...
Click to collapse
It's compatible with mi max. You will not have any problem. Don't worry
noob456 said:
Is this beta version of SuperSU reliable? Did you use it? Not better to use a stable version?
Click to expand...
Click to collapse
Waiting to tell me if everything went fine with the installation and the flashing
Hey, tried following Your guide to install a new rom last night. Great guide for noobs like me, but it may be worth renaming the thread to something like "How to flash whatever makes You happy on to Your Mi Max". These instructions seem to work fine regardless of what's being flashed. Great job, mate!
So I finally tried it and it was successful for me as well! But I used the latest version of TWRP (3.1.0) and SuperSu (2.79-20161205). Please add a point in your tutorial to upload SuperSU.zip to the phone first, because out of emotion, I forgot... So I flashed TWRP, booted it and then... ups... no SuperSu So I wanted to reboot the phone to upload SuperSU but since only SuperSU patches dm-verity (the thing I was afraid of the most - I told you before), my phone got into boot-loop and didn't want to start. So I just uploaded SuperSU to a memory card, entered Fastboot Mode again with key-combination, plugged the cable, typed "fastboot reboot-bootloader" command and was again in TWRP to flash SuperSu from my memory card.... ufff.
So I would reedit it a bit:
0. Copy SuperSU.zip to the phone/memory card!
1. Go to Settings-About phone-Find the MIUI VERSION, and tap on it for 5-10 times.
2. Go back to settings, sellect adittional settings. click on Developer options, and select enable
3. Find the option USB Debugging and enable it.
4. Download the TWRP recovery from the link
5. rename the file to 'recovery.img'
6. Move the image to the same file where the ADB was installed ( it should be on Computer-> C: -> Adb )
7. Open the adb folder
8. Press and hold the shift key and right click in the folder
9. click on the option "Open command window here"
10. Boot your device on fastboot mode by turning it off, pressing Power and the Volume Down buttons together, and then connect it with your computer
11. First type this command "fastboot devices" to check if your device is into fastboot mode
12. Enter the command "fastboot flash recovery recovery.img"
13. Enter the command "fastboot boot recovery.img" - the phone will get disconnected from your PC automatically
14. Your phone is now in TWRP recovery mode (it takes about 30-60 seconds before FastBoot screen switches into TWRP - wait patiently)
15. select Install Zip and click on 'SuperSu.zip'
16. corfirm the flash
17. reboot your device
18. DONT PANIC IF YOU DEVICE WONT TURN ON. Sometimes need to wait 10-20 secs.
Hey, I just got connected with WiFi and new MIUI 8.2.3.0 MBCMIDL wants to be installed, although the phone is rooted with bootloader unlocked. Is it safe to apply the update? Is it goona remove root so that I have to go over the process again?
So I tried the update. First time it said it failed, second time it downloaded the whole ROM after which it rebooted device and TWRP started doing "something" - I don't know what. After that the phone didn't want to boot, and what's even better didn't want to run recovery (TWRP), instead it went into fastboot. What I had to do was to use MiPhoneDrivers from this topic: https://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594 (including MiFlash 2015, because 2016 version didn't want to work properly on my PC) and follow the instruction from official MIUI website to flash from scratch the new ROM MIUI 8.2.3.0 which I did. After that my phone was alive again. I installed TWRP and rooted the phone again. Now I've got MIUI 8.2.30 rooted. :] End of the story so far. My settings left untouched - icons, wallpaper etc. So that would be the way to update MIUI if they prepare a new one.
Is there anyway to root the phone without connecting it to pc?
noob456 said:
So I tried the update. First time it said it failed, second time it downloaded the whole ROM after which it rebooted device and TWRP started doing "something" - I don't know what. After that the phone didn't want to boot, and what's even better didn't want to run recovery (TWRP), instead it went into fastboot. What I had to do was to use MiPhoneDrivers from this topic: https://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594 (including MiFlash 2015, because 2016 version didn't want to work properly on my PC) and follow the instruction from official MIUI website to flash from scratch the new ROM MIUI 8.2.3.0 which I did. After that my phone was alive again. I installed TWRP and rooted the phone again. Now I've got MIUI 8.2.30 rooted. :] End of the story so far. My settings left untouched - icons, wallpaper etc. So that would be the way to update MIUI if they prepare a new one.
Click to expand...
Click to collapse
Thanks for saving me the trouble.
Can someone help with a better method of applying updates?
Will downloading the zip (1.4GB approx) and flashing via TWRP help?
Hi, as written in the title, I would like to root my phone. I never touch root with xiaomi (the only thing I've done is unlock bootloader)
I usualy root samsung's phone
I want to know if it possible to have my phone rooted with magisk, twrp as custom recovery with android 11
Sorry if my english is bad, sorry if wrong place/category
The best way is to searc already written threat..
Or watch YouTube.
You need to download ADB ,ind ADB folder put oFox or TWRP ,depens what tou want from recovery. in that folder, holding shift+left click open powershell, then type , fastboot flash recovery _name of recovery.img
Fastboot boot name of recovery.img
And that it.
tze_vitamin said:
The best way is to searc already written threat..
Or watch YouTube.
You need to download ADB ,ind ADB folder put oFox or TWRP ,depens what tou want from recovery. in that folder, holding shift+left click open powershell, then type , fastboot flash recovery _name of recovery.img
Fastboot boot name of recovery.img
And that it.
Click to expand...
Click to collapse
Of course I have already searched
If I write here, it is because I did not find some information
Flash twrp, like you say, yes but is twrp for this phone compatible with android 11 or 10 only ?
Most of guide I found say "root ... android 10" or just root without precise the version
That's why I want to be sure
Rooting with Magisk is pretty much always the same, doesn't matter if Samsung or Xiaomi.
1. Download https://androidfilehost.com/?fid=2188818919693773066 (link from https://forum.xda-developers.com/t/...-lite-mi10i-redmi-note-9-pro-5g-beta.4228655/)
2. "fastboot boot twrp_xyz.img" (don't flash custom recovery as internal memory can't be decrypted in TWRP afterwards)
3. install magisk.zip
Works on stock Android 11.
_mysiak_ said:
Rooting with Magisk is pretty much always the same, doesn't matter if Samsung or Xiaomi.
1. Download https://androidfilehost.com/?fid=2188818919693773066 (link from https://forum.xda-developers.com/t/...-lite-mi10i-redmi-note-9-pro-5g-beta.4228655/)
2. "fastboot boot twrp_xyz.img" (don't flash custom recovery as internal memory can't be decrypted in TWRP afterwards)
3. install magisk.zip
Works on stock Android 11.
Click to expand...
Click to collapse
(don't flash custom recovery as internal memory can't be decrypted in TWRP afterwards)
Is it still possible to backup/restore in case of problem ?
No need to reset ?
Xyphoseos said:
(don't flash custom recovery as internal memory can't be decrypted in TWRP afterwards)
Is it still possible to backup/restore in case of problem ?
No need to reset ?
Click to expand...
Click to collapse
Backup most probably yes, I never tried restore so can't confirm. But obviously you will need to "hot boot" TWRP whenever you want to use it, so you must have PC at hand.
_mysiak_ said:
Backup most probably yes, I never tried restore so can't confirm. But obviously you will need to "hot boot" TWRP whenever you want to use it, so you must have PC at hand.
Click to expand...
Click to collapse
Ive read in some guide (that there were not clearly) twrp is flashed, phone reseted and vmbeta disable (or something like that) this make us able to see those crypted data in twrp
Maybe Im wrong
Xyphoseos said:
Ive read in some guide (that there were not clearly) twrp is flashed, phone reseted and vmbeta disable (or something like that) this make us able to see those crypted data in twrp
Maybe Im wrong
Click to expand...
Click to collapse
I don't know about this. I want my phone encrypted, so I boot TWRP after every OTA update to root it again..
_mysiak_ said:
I don't know about this. I want my phone encrypted, so I boot TWRP after every OTA update to root it again..
Click to expand...
Click to collapse
okay, thank you for your help !
Root like this prevent me from ota updates right ?
Xyphoseos said:
okay, thank you for your help !
Root like this prevent me from ota updates right ?
Click to expand...
Click to collapse
For incremental ("small" OTA) update you will need to restore stock images in Magisk.
Full ("big" OTA) update can be installed without any further steps.
In both cases, after a reboot you will have updated system with no root, so you need to reinstall Magisk from TWRP.
What Android you have. I am on A11 and Orangefox working perfect
Hi,
having Android 11
"reboot bootloader" doesn't seem to work on my Sharp.
"reboot sideload" works: is there a version of that "twrp img" that can be sideloaded on Android 11?
( has to be a zip )
petit-lion said:
Hi,
having Android 11
"reboot bootloader" doesn't seem to work on my Sharp.
"reboot sideload" works: is there a version of that "twrp img" that can be sideloaded on Android 11?
( has to be a zip )
Click to expand...
Click to collapse
If "reboot bootloader" is the command line and does not work, do it manually ?
Btw, thank you again @_mysiak_ , everything works like a charm
_mysiak_ said:
Rooting with Magisk is pretty much always the same, doesn't matter if Samsung or Xiaomi.
1. Download https://androidfilehost.com/?fid=2188818919693773066 (link from https://forum.xda-developers.com/t/...-lite-mi10i-redmi-note-9-pro-5g-beta.4228655/)
2. "fastboot boot twrp_xyz.img" (don't flash custom recovery as internal memory can't be decrypted in TWRP afterwards)
3. install magisk.zip
Works on stock Android 11.
Click to expand...
Click to collapse
Xyphoseos said:
If "reboot bootloader" is the command line and does not work, do it manually ?
Click to expand...
Click to collapse
What I mean is "adb reboot bootloader" just reboots, does not go into bootloader.
Manually, the vol-down power goes into "factory reset", there is no other option.
It's a Sharp, and these phones are known not to be very bootloader-tolerant.
Only "adb reboot sideload" works and goes into "sideload" mode, waiting for a ZIP file to be uploaded.
Then, the "sideload" zip must contain a valid signature, and "edify" commands.
That motivated my question:
For Android 11, is there a zip sideloadable of twrp, with a valid signature?
petit-lion said:
What I mean is "adb reboot bootloader" just reboots, does not go into bootloader.
Manually, the vol-down power goes into "factory reset", there is no other option.
It's a Sharp, and these phones are known not to be very bootloader-tolerant.
Only "adb reboot sideload" works and goes into "sideload" mode, waiting for a ZIP file to be uploaded.
Then, the "sideload" zip must contain a valid signature, and "edify" commands.
That motivated my question:
For Android 11, is there a zip sideloadable of twrp, with a valid signature?
Click to expand...
Click to collapse
I dont know, sorry
petit-lion said:
What I mean is "adb reboot bootloader" just reboots, does not go into bootloader.
Manually, the vol-down power goes into "factory reset", there is no other option.
It's a Sharp, and these phones are known not to be very bootloader-tolerant.
Only "adb reboot sideload" works and goes into "sideload" mode, waiting for a ZIP file to be uploaded.
Then, the "sideload" zip must contain a valid signature, and "edify" commands.
That motivated my question:
For Android 11, is there a zip sideloadable of twrp, with a valid signature?
Click to expand...
Click to collapse
Not sure why you discuss Sharp phone in this topic, but nevertheless, "adb sideload" mode is for stock ROM updates/installations. As far as I'm aware, it is not possible to install anything else this way.
_mysiak_ said:
Not sure why you discuss Sharp phone in this topic, but nevertheless, "adb sideload" mode is for stock ROM updates/installations. As far as I'm aware, it is not possible to install anything else this way.
Click to expand...
Click to collapse
Sorry, I saw "root Android 11" and jumped into it.
Desperate to find an access to that damn Sharp.
petit-lion said:
Sorry, I saw "root Android 11" and jumped into it.
Desperate to find an access to that damn Sharp.
Click to expand...
Click to collapse
You will need either unlocked bootloader + device specific custom recovery, or functional exploit which could root the phone. You are most probably out of luck, so buying a phone with good support on XDA might save you some headaches.
_mysiak_ said:
You will need either unlocked bootloader + device specific custom recovery, or functional exploit which could root the phone. You are most probably out of luck, so buying a phone with good support on XDA might save you some headaches.
Click to expand...
Click to collapse
Learned the lesson
But this Sharp Sense 3 was offered to me by a carrier.
It had initially Android 9 Pie on it, and, biiig mistake, let it upgrade itself
(no upgrade until root from now on!)
Anyway, that's an interesting challenge. Had a look at the open-source visible code from Sharp, checked the 'recovery.cpp' part, and tried all the 'reboot' allowed in the code (eg oem-xxx ...).
Saw the "panic" code (Snapdragon 630 has a panic mode), but could not trigger it.
Saw the part from the Google code handling the sideload signature, and this one will be hard to beat!
And, unfortunately the part handling 'bootloader', Sharp cutstomized, is not visible.
To be continued...
I have a mi10t lite with vodafone brand. I would like to have a europe firmware so i can receive the last ota and so on..
is this a way I can do too?