Related
Hello!
Introduction:
I have just only recently bought myself a nice Miro and I have to say I'm in love (with my girlfriend). When I first wanted to flash, most of the guides were VERY generic and assumed that I knew most of the things that I did not know and I had to go out and discover things; let me tell you that was not fun... SO MUCH STRESS!
THIS THREAD IS A WORK IN PROGRESS. PLEASE DO A LITTLE MORE RESEARCH BEFORE FLASHING. THIS MEANS LOOK AT THE DEVELOPER'S FLASH INSTRUCTIONS AS WELL AS THIS THREAD FOR NOW
__________________________________________________ ____________
Terms and words -->
Flashing ==> means installing a new ROM or modification or kernel, etc.
ROM ==> is the operating system, any version of modded or un-modded android
Android ==> Google made operating system!!!
Flashtool ==> Software to Flash things on Xperia devices.
Kernel ==> The mind of your device, this is a rather important part of the operating system.
Flashmode ==> You put your phone on this mode when you want to use Flashtool. Access by pressing and holding Vol down + connect USB when phone has been turned off. Flashtool has a nice animation to help you if you do it wrong.
Fastboot mode ==> You put your phone on this mode to flash kernels and stuff like that. You can use Flashtool or fastboot on the terminal (or CMD) to access. You put your phone on this mode by pressing and holding Vol up + plug USB in, similar (but not the same) as Flashmode.
Soft brick ==> No, not the construction brick, this means you've got no working operating system or you have one but its damaged and you can't use it, so you cant see your homescreen, you only see a boot-loop when it wants to come up (you see your start animation and android won't start). You can view your recovery and boot loader (The Flashmode and Fastboot mode) when soft bricked, so you can easily fix this problem by re-flashing any working ROM.
Hard brick ==> Similar to the construction brick, your phone with little hope of recovery without sending to the Sony Center for repairs. There is one last resort as well, I will mention that in the notes toward the end of this guide; but still do not rely on that stuff too much.
__________________________________________________ ____________
Should this guide be followed carefully, nothing harmful can happen to your phone. Yet I wont take responsibility if something happens to your phone.
__________________________________________________ ____________
***Remember to back up our contacts and apps ***__________________________________________________ ____________
Starting with the basics; Using Flashtool and setting things up:
1) Download Flashtool from Here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2) Install.
3) Go to the directory you installed Flashtool in [for me it was C:\flashtool]
4) You need to go to C:\flashtool\drivers
5) Install the drivers.exe file there. I just installed the Fasboot and Flashmode drivers from the list it gave me mid-installation.
6) Install Sony's PC Companion and connect your Miro while it is on. This will install ADB drivers.
7) You are all set, but may need to reboot.
__________________________________________________ ____________
How to flash stock firmware:
1) Download correct FTF from here [Miro], and do not forget to read the thread OP before doing anything.
2) Open up Flashtool as admin. Put your .FTF file on C:\Flashtool\firmwares
3) Connect your phone on Flashmode, then press the lightning button.
4) From the two options, press Flash mode.
5) Select the firmware you want to flash (usually, the latest is the better, and as of now, version 11.A.0.5.5 is the latest; so that will be what I am using)
6) Tick "no final verfication" start! DO NOT CHANGE ANY OTHER OPTION UNLESS YOU ARE ABSOLUTELY SURE
7) Now the process will start. If it gives an error, there are a few possibilities: either you are running windows 8, which I just could not use with Flashtool, or you do not have the right drivers installed correctly, or your files/USB/phone are corrupted.Usually, the problem is that the right permission (run Flashtool as admin), so be careful.
8) Enjoy
__________________________________________________ ____________
Kernels:
This is very simple, and there are two ways.
[1] Fastboot from Flashtool:
1) Run Flashtool as admin
2) Connect phone in Fastboot mode.
3) Press lightning button.
4) Out of the two options, choose Fastboot
5) A menu will pop up; select Select kernel to flash.
6) Browse for your kernel; if you are installing FXP, it will be boot.img, if you are installing Vengeance it will be kernel.elf, etc.
NOTE! Remember that you have to extract FXP's kernel [boot.img] from the various zip files they have provided. Installing FXP will be given a tutorial too, in this thread
!! I did not have FXP downloaded on this laptop; I will put an image up for this as soon as someone gives me a screenie or I download it myself. !!
7) After you press OK, the file will be flashed and the process takes less than 2 seconds on all cases (the longest for me was 1.48 s)
[2] Fastboot from Terminal
Winows:
1) Press Start Button and search for CMD and run it.
2) You need to have Google's Android SDK installed from here. The Google page for it is to be read, just in case. [ZzzzzzZzzzzzz]
3) From the SDK, install these two:
4) Put kernel file in the same folder fastboot (normally \android-sdk\platform-files\)
5) Connect phone in Fastboot mode.
6) After you have those installed, go back to CMD and type this:
Code:
cd C:\android\android-sdk\platform-tools [COLOR="YellowGreen"]//[I]HINT! You may install or paste these files elsewhere. Just use cd to show your PC where they are :) [/I][/COLOR]
fastboot devices [COLOR="YellowGreen"]//Continue if you get a response. If not, you do not have the drivers or there is a problem in your connection.[/COLOR]
fastboot flash boot [COLOR="YellowGreen"]/*KERNEL NAME, such as boot.img, or kernel.elf*/[/COLOR]
fastboot reboot
7) Done!
Linux:
- Same as the windows, except to open the terminal (like CMD in Windows) you press CTRL+ALT+T.
- You do not need to install drivers on Linux.
- Ubuntu is a very easy Linux distribution [also referred to as distro] to install, if you don't have but want it, go to THIS website and download multiboot
- on every command on your terminal that starts with
Code:
fastboot
, you have to add
Code:
sudo
to the start of it; so if the command is for example
Code:
fastboot devices
, you enter instead
Code:
sudo fastboot devices
. It will ask for your password and you have to give it. It will not type it so don't worry, just type it out and press enter.
- Much easier, right?
Please don't judge my old laptop model, this was my first computer
__________________________________________________ ____________
Popularity, how to install FXP CM10:
1) Download the latest version from FXP's signature and your SD card (it doesn't matter if it is internal or external).
2) Open the download .zip file and from it, extract the file labelled "boot.img"
!! No images yet, will put up soon. !!
3) Flash this boot.img by the kernel flashing tutorial given above.
4) After you boot the phone, You will see the illumination bar (on Miro) turn purple. At this point press the Volume buttons a lot.
5) The illumination bar will turn blue and you will be presented with CWM. Open install zip and install the FXP CM10 version you had downloaded. (This is how I do it every time, but some people say this is only necessary for the first time flashing. For updates, only flashing the zip is fine and you do not need to install the boot.img as well; I will update after people enlighten me in comments )
6) After this, reboot and have fun with CM10
CM10 based ROMs:
You have to be on CM10 to install any CM10 based ROM.
- Simply go to CM10, factory reset, and install the zip provided by the dev.
MORE TO COME SOON. If you think that I am wrong at specific points, tell me.
Reserved for more!
This one is for videos; reserved.
Thanks for the nice guide
Sent from my Xperia Miro using xda app-developers app
Great guide buddy! Thanks!
Sent from my LT26i using xda app-developers app
Hey, when i am flashing fxp 220 do i have to be rooted and does cwm have to be installed or can i just directly follow ur guide?
I have an unlocked bootloader.
Great guide thanks a lot
wizsid said:
Hey, when i am flashing fxp 220 do i have to be rooted and does cwm have to be installed or can i just directly follow ur guide?
I have an unlocked bootloader.
Great guide thanks a lot
Click to expand...
Click to collapse
Just follow the guide, you need none of the things you said. Flashing boot.img from FXP gives you CWM and the ROM is pre-rooted so don't worry about that.
Nice guide dude
•°•♡ⓣⓗⓐⓝⓚⓢ♡ •°•
Sent from my Xperia Tipo using xda premium
thanks :good::good:
Please Help, i just wanna help my friend with his xperia MIRO, he wanna downgrade from firmware 58 to firmware 55, but every flashtool process it alway stuck at Flashing Data :
- Start Flashing
- Processing Loader
- Checking Header
- Flashing Data
- and the process STUCK on Here
can anyone help, or any procedure for downgrade firmware via flashtoll that i should know, thanks B4
allaboutarif said:
Please Help, i just wanna help my friend with his xperia MIRO, he wanna downgrade from firmware 58 to firmware 55, but every flashtool process it alway stuck at Flashing Data :
- Start Flashing
- Processing Loader
- Checking Header
- Flashing Data
- and the process STUCK on Here
can anyone help, or any procedure for downgrade firmware via flashtoll that i should know, thanks B4
Click to expand...
Click to collapse
Oh my sorry for the late reply, you must know that you have correct drivers, but if your computer noticed the phone in flashmode and stuff then thats fair enough...
I would recommend that you flash Gimlo if you can. If you don't have CWM flash Vengeance kernel first and then install Gimlo.
If you just want stock, based on my own knowledge of this matter, I'd say that you have to either re-download the FTF, or try doing it all on a new pc. Maybe that will work?
Thanx a lot bro. Helped me.
Sent from my ST21i using xda premium
problems while flashing kernels
Hey I have Xperia Tipo Dual While flashing kernel in fastbood mode it Gets An error That "Your Phone Must be rooted" I have alreay rooted my phone An Have bootloader unlock What Shoul I Do??
26/031/2013 18:31:42 - INFO - <- This level is successfully initialized
26/031/2013 18:31:42 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
26/031/2013 18:31:48 - INFO - Device connected in fastboot mode
26/031/2013 18:31:53 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\home\Desktop\kernel.elf
26/031/2013 18:31:53 - INFO - Flashing selected kernel
26/031/2013 18:31:53 - INFO - sending 'boot' (9523 KB)...
26/031/2013 18:31:53 - INFO - FAILED (remote: The Device must be rooted first)
26/031/2013 18:31:53 - INFO - finished. total time: 0.006s
26/031/2013 18:31:53 - INFO - FASTBOOT Output:
sending 'boot' (9523 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.006s
this is the Error i am getting
26/031/2013 18:31:53 - INFO - Please check the log before rebooting into system
vikas singh said:
Hey I have Xperia Tipo Dual While flashing kernel in fastbood mode it Gets An error That "Your Phone Must be rooted" I have alreay rooted my phone An Have bootloader unlock What Shoul I Do??
26/031/2013 18:31:42 - INFO - <- This level is successfully initialized
26/031/2013 18:31:42 - INFO - Flashtool Version 0.9.11.0 built on 2013-06-04 22:50:00
26/031/2013 18:31:48 - INFO - Device connected in fastboot mode
26/031/2013 18:31:53 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\home\Desktop\kernel.elf
26/031/2013 18:31:53 - INFO - Flashing selected kernel
26/031/2013 18:31:53 - INFO - sending 'boot' (9523 KB)...
26/031/2013 18:31:53 - INFO - FAILED (remote: The Device must be rooted first)
26/031/2013 18:31:53 - INFO - finished. total time: 0.006s
26/031/2013 18:31:53 - INFO - FASTBOOT Output:
sending 'boot' (9523 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.006s
this is the Error i am getting
26/031/2013 18:31:53 - INFO - Please check the log before rebooting into system
Click to expand...
Click to collapse
try the direct fastboot method, rather than the flashtool. that should help i imagine. apparantly you are not the only one getting this error, but i have no idea why this is happening...
Update
I installed Flashtool a long back. my version is 0.7.0.0
What should i do to update? install the new one directly or uninstall the old one 1st and then install the new one.
kenny_cfc said:
I installed Flashtool a long back. my version is 0.7.0.0
What should i do to update? install the new one directly or uninstall the old one 1st and then install the new one.
Click to expand...
Click to collapse
uninstall the old one then install the new one.
still getting the same error
---------- Post added at 06:54 PM ---------- Previous post was at 06:49 PM ----------
PersianSphinx said:
try the rather than the flashtool. that should help i imagine. apparantly you are not the only one getting this error, but i have no idea why this is happening...
Click to expand...
Click to collapse
even though by using the direct fastboot method still getting the same error
vikas singh said:
still getting the same error
---------- Post added at 06:54 PM ---------- Previous post was at 06:49 PM ----------
even though by using the direct fastboot method still getting the same error
Click to expand...
Click to collapse
How inconvenient... Alright, can you unroot then go places from there? I wasnt first rooted when I flashed FXP on my phone... If you must know I was on 5.8 version. Let's see if this helps?
PersianSphinx said:
uninstall the old one then install the new one.
Click to expand...
Click to collapse
Ok. Will i have to install the drivers again?
Xperia Miro st23i
Vengeance Kernel 1.46
Gimlo ROM 2.0
kenny_cfc said:
Ok. Will i have to install the drivers again?
Xperia Miro st23i
Vengeance Kernel 1.46
Gimlo ROM 2.0
Click to expand...
Click to collapse
Yeah, I would do that if I was you, I mean there's nothing to lose. By the way, slight off topic: how's Gimlo v2.0? I REALLY liked v1.3, is 2.0 a lot better? I'm considering getting it...
Hi
I have a problem becouse when my m2 back from warranty i can't unlock bootloader. Flashtool say error:
07/036/2015 08:36:04 - INFO - ...
07/036/2015 08:36:04 - INFO - FAILED (remote: Command did not succeed)
07/036/2015 08:36:04 - INFO - finished. total time: 0.094s
and when i'm click second time it's says: "Bootloader unlocked" but i can't flash kernel.
i don't know why i can't, anyone could help me?
Sorry for bad english
Go to the folder where Flashtool was installed
2.: Open the folder named "custom"
3.: Open the folder named "mydevices" (if it exists, in my case Flashtool version 0.9.18.4)
4.: Right button, New, Folder. Name the folder with your device code.
5.: Open the folder created previously
6.: Right button, New, Text Document. Name the text document as ulcode
7.: Open the text document created previously
8.: Paste your unlock code and save
9.: Open Flashtools and try the BLU option again.
07/001/2015 10:01:28 - INFO - FAILED (remote: Command did not succeed)
07/001/2015 10:01:28 - INFO - finished. total time: 0.093s
07/001/2015 10:01:33 - INFO - Unlocking phone using key 823CB0285AED7EC1
07/001/2015 10:01:33 - INFO - ...
07/001/2015 10:01:33 - INFO - FAILED (remote: Device is already rooted)
07/001/2015 10:01:33 - INFO - finished. total time: 0.004s
again... maybe flashtool 9.18.5 is broken, could someone upload or link me flashtool 9.18.4?
Edit
No, it isn't flashtool... i don't know what wrong with this phone...
*#*#7378423*#*#
Use this code to check unlocking status under Service info--> Configuration
You can find 9.18.4 flashtool from official site
I had a same problem and I used the latest version of flashtool!
You must be on 4.4.2 first update to unlock bootloader!
Hmm... I unlocked mine while JB 4.3 somehow!
It is a copy/paste from the original post created by dead5loth in OPPO forums: http://community.oppo.com/en/forum.php?mod=viewthread&tid=40709&extra=&page=1
Disclamer
1. Rooting your device may void your warranty!
2. Please note that I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about applying this modification and remember, YOU are choosing to make these modifications and if you point the finger at me for messing up your device, I will laugh at you. A lot.
Notice
1. OPPO Tools claims to support both the R7 and R7 Plus (check the about tab) but I have only tested it with the OPPO R7g! If you are using a different varaient- PLEASE LEAVE FEEDBACK!
2. USING THIS TOOL IS YOUR RESPONSIBILITY, UPON DOWNLOADING AND USING THIS TOOL YOU AGREE THAT YOU MAY DAMAGE YOUR DEVICE AND MAY NEVER BE ABLE TO RECIEVE OTA UPDATES. (Side note: You will still have access to manual updates.)
Compatability
1. Please check below and see if this method is safe and works on your device.
2. Working - OPPO R7g on ColorOS v2.1 / Android 5.1.1
3. Working - OPPO R7f on Unspecified - (Thanks @bbgt2)
4. Working - OPPO R7 Plus M (Chinese Version w/ international 3G & 4G (FDD)) on ColorOS 2.1 / Android 5.1.1 (Thanks @jensehuk)
5. Partition / Possible Bricking Issues - OPPO R7 Plus F on Unspecified - (Thanks @ait-Solutions)
Requirements
1. OPPO R7 / R7 Plus on ColorOS (using this on custom ROMs may cause issues)
2. OPPO Tools v1.6.3 (or higher) - GitHub Project Page | Direct APK Download
3. Stock Recovery - USING TWRP OR ANY OTHER CUSTOM RECOVERY WILL NOT WORK
4. 50% or more remaining battery - THIS IS IMPORTANT
Steps
1. Download and Install the latest OPPOTools.apk ( https://github.com/wuxianlin/OppoTools/raw/server/OppoTools.apk ).
2. Launch OPPO Tools (check the About tab and verify that your device is listed)
3. Go to the Common tab and select ROOT.
4. An application install prompt will appear for "OppoToolsPlugin", Install it.
5. Once complete, re-open OPPO Tools and select ROOT once again.
6. One Key Root will open, Select the One Key Root button to start the ROOT process.
7. Your device will restart multiple times, just be patient.
8. If the installation was successful, you will notice SuperSU has been installed.
Phone: R7 Plus f (International version)
ColorOs Version: V2.1.0i
Compilation number: R7plusfEX_11:150902
Status: It works correctly!
Thanks, I think your post is missing the .apk so there it is: https://github.com/wuxianlin/OppoTools/raw/server/OppoTools.apk
There's been an update yesterday for the F version 'R7PlusfEX_11_150916' I'm unsure if it changes anything or adds any problems with rooting.
Unlock Bootloader/Backup/Root/Viper4Android
Unlock Bootloader/Backup/Root/Viper4Android
Tested myself on latest stock rom version R7PlusfEX_11_150916
Do it at your own risk, I am not responsible for any damage to your phone, your computer nor your cat.
1. You must have right ADB drivers installed. Please follow this guide (Prerequisites part)
You must end up with this:
Code:
C:\sdk\platform-tools>adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
Before I have installed SDK my R7+ was showing as Marshall London bootloader interface:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Correct drivers installed:
2. Maybe not needed but go to developers options and allow USB debugging
3. Power off your phone (wait, sometimes it take long time, it will vibrate when done)
4. Hold power button + volume UP to enter fastboot mode
5. Connect USB cable
6. Go to folder where your fastboot.exe is and press shift + right mouse and click on "Open command window from here"
7. Type
Code:
fastboot devices
- It should return your device serial number, if not you need to make sure your drivers are installed correctly.
8. Type
Code:
fastboot oem device-info
and see if your bootloader is locked (some phones comes with bootloader unlocked). You should see this:
Code:
C:\sdk\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.006s
9. To unlock bootloader type
Code:
fastboot oem unlock
You should see this:
Code:
C:\sdk\platform-tools>fastboot oem unlock
...
OKAY [ 0.004s]
finished. total time: 0.005s
To check type again
Code:
fastboot oem device-info
You should see this:
Code:
C:\sdk\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.006s
pic:
10. You are unlocked and your DATA are NOT wiped, congrats :highfive:
TWRP Recovery:
We are not going to flash twrp, because there is a risk of damage partition in the moment, so instead of flash, we only boot to it which is all we need!
1. Download this TWRP recovery (MIRROR) and put the file into the folder where your fastboot.exe is!
2. With phone in fastboot mode type
Code:
fastboot boot recovery.img
You should see this:
Code:
C:\sdk\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.865s]
booting...
OKAY [ 3.639s]
finished. total time: 4.506s
3. Wait, it can take 30 seconds to boot into TWRP!
Backup:
With TWRP running first of all I recommend you to backup all partitions and after backup is complete, restart phone and COPY the backup files from phone to your computer!
Root:
1. When still connected to computer copy SuperSU file to phone`s memory
2. Disconnect usb cable, power phone off, enter fastboot mode and connect the usb cable.
3. BOOT into TWRP recovery again and flash the SuperSU and reboot.
4. Check if you are rooted:
Viper4Android:
1. First we need to change the SElinux to permissive
2. Download SELinuxModeChanger-v3.2-release.apk here and place it to phone`s memory.
3. Install the app (unknown sources must be allowed in settings)
4. Run the app, grand root rights, click on permissive and I recommend tick "show notification after mode changed"
5. Go to Security center, Privacy Permission, scroll down and click Auto-run Management and ALLOW SELinuxModeChanger to start automatically after restart.
6. Reboot phone and see if SELinuxModeChanger starts - you should see the notification. If everything is fine, you can disable the notification by untick it in app.
7. Download Viper4Android and copy to phone.
8. BOOT into TWRP recovery again and simply flash the downloaded zip and reboot.
9. Click on Viper4Android app to install its drivers, grand root rights and reboot phone.
10. Now run app and enable it for headphones and you are ready to enjoy great sound.
11. I recommend to disable "Dirac HD Sound" in Music app settings to not interfere with Viper4Android.
Does everything work as you want now? Go back to TWRP and make a new backup!!!
That`s it! Hopefully someone will find this guide helpful! Enjoy!!!
Hello,
I have Oppo R7 plus mediatek version
R7Plus_11_A.06_OTA_006_all_201509030909_wipe.zip
When i use the Oppo tools v1.6.2 my phone is stuck at the Oppo logo screen.
I have already try Iroot, kingroot, kingoroot and shuameroot do not work
Can anybody help me root the device.
Thank you.
Has anyone installed xposedframework after root yet ?
Guys anyone have oppotools saved anywhere?
Osleg said:
Guys anyone have oppotools saved anywhere?
Click to expand...
Click to collapse
I dont, but use oppotools with chinesse version of phone only or there is a high chance you`ll brick your phone.
Works with oppo r7 lite (r7kf)?
Anyone got Oppotools anywhere?
OppoTools1.6.3
mikejasonsmith said:
Anyone got Oppotools anywhere?
Click to expand...
Click to collapse
https://github.com/asshadiqi/OppoTools/blob/server/OppoTools.apk
Click "view the full file" to download.
titanium_gld said:
https://github.com/asshadiqi/OppoTools/blob/server/OppoTools.apk
Click "view the full file" to download.
Click to expand...
Click to collapse
Your a star!
Does this work on a chinese phone?
I just updated my R7 Plus to R7PlusfEX_11_151225. Oppotools 1.6.5 can be installed but the root button doesn't do anything. Is this a known issue and will this be fixed in a new version of Oppotools?
Hi all FYI rooting method for R7plus using the OppoTools v1.6.5 is no longer supported on R7PlusfEX_11_151225.
So to root it just use the old method.
Just install/flash the UPDATE-SuperSU-v2.46.zip via TWRP
That's all. Cheers!
noodlecore said:
Hi all FYI rooting method for R7plus using the OppoTools v1.6.5 is no longer supported on R7PlusfEX_11_151225.
So to root it just use the old method.
Just install/flash the UPDATE-SuperSU-v2.46.zip via TWRP
That's all. Cheers!
Click to expand...
Click to collapse
Would anyone be able to provide a copy of 1.6.5? I'm still on 1.6.3... Thanks.
Nexus5-32GB said:
Unlock Bootloader/Backup/Root/Viper4Android
Tested myself on latest stock rom version R7PlusfEX_11_150916
Do it at your own risk, I am not responsible for any damage to your phone, your computer nor your cat.
1. You must have right ADB drivers installed. Please follow this guide (Prerequisites part)
You must end up with this:
Code:
C:\sdk\platform-tools>adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
Before I have installed SDK my R7+ was showing as Marshall London bootloader interface:
Correct drivers installed:
2. Maybe not needed but go to developers options and allow USB debugging
3. Power off your phone (wait, sometimes it take long time, it will vibrate when done)
4. Hold power button + volume UP to enter fastboot mode
5. Connect USB cable
6. Go to folder where your fastboot.exe is and press shift + right mouse and click on "Open command window from here"
7. Type
Code:
fastboot devices
- It should return your device serial number, if not you need to make sure your drivers are installed correctly.
8. Type
Code:
fastboot oem device-info
and see if your bootloader is locked (some phones comes with bootloader unlocked). You should see this:
Code:
C:\sdk\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.006s
9. To unlock bootloader type
Code:
fastboot oem unlock
You should see this:
Code:
C:\sdk\platform-tools>fastboot oem unlock
...
OKAY [ 0.004s]
finished. total time: 0.005s
To check type again
Code:
fastboot oem device-info
You should see this:
Code:
C:\sdk\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.006s
pic:
10. You are unlocked and your DATA are NOT wiped, congrats :highfive:
TWRP Recovery:
We are not going to flash twrp, because there is a risk of damage partition in the moment, so instead of flash, we only boot to it which is all we need!
1. Download this TWRP recovery (MIRROR) and put the file into the folder where your fastboot.exe is!
2. With phone in fastboot mode type
Code:
fastboot boot recovery.img
You should see this:
Code:
C:\sdk\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.865s]
booting...
OKAY [ 3.639s]
finished. total time: 4.506s
3. Wait, it can take 30 seconds to boot into TWRP!
Backup:
With TWRP running first of all I recommend you to backup all partitions and after backup is complete, restart phone and COPY the backup files from phone to your computer!
Root:
1. When still connected to computer copy SuperSU file to phone`s memory
2. Disconnect usb cable, power phone off, enter fastboot mode and connect the usb cable.
3. BOOT into TWRP recovery again and flash the SuperSU and reboot.
4. Check if you are rooted:
Viper4Android:
1. First we need to change the SElinux to permissive
2. Download SELinuxModeChanger-v3.2-release.apk here and place it to phone`s memory.
3. Install the app (unknown sources must be allowed in settings)
4. Run the app, grand root rights, click on permissive and I recommend tick "show notification after mode changed"
5. Go to Security center, Privacy Permission, scroll down and click Auto-run Management and ALLOW SELinuxModeChanger to start automatically after restart.
6. Reboot phone and see if SELinuxModeChanger starts - you should see the notification. If everything is fine, you can disable the notification by untick it in app.
7. Download Viper4Android and copy to phone.
8. BOOT into TWRP recovery again and simply flash the downloaded zip and reboot.
9. Click on Viper4Android app to install its drivers, grand root rights and reboot phone.
10. Now run app and enable it for headphones and you are ready to enjoy great sound.
11. I recommend to disable "Dirac HD Sound" in Music app settings to not interfere with Viper4Android.
Does everything work as you want now? Go back to TWRP and make a new backup!!!
That`s it! Hopefully someone will find this guide helpful! Enjoy!!!
Click to expand...
Click to collapse
Also Working on latest R7+ build R7plusfEX_11_151225. :good::laugh:
Hello,
I did the following step:
"2. With phone in fastboot mode typeCode:
fastboot boot recovery.img
You should see this:Code:
C:\sdk\platform-tools>fastboot boot recovery.imgdownloading 'boot.img'...OKAY [ 0.865s]booting...OKAY [ 3.639s]finished. total time: 4.506s"
However it did not go to TWRP. the phone rebooted and wet back to normal.
I turn the phone off and went to recovery but it was still OPPO's recovery.
Any help?
Omg ... I Use latest oppo tool 5 min job done
---------- Post added at 08:08 PM ---------- Previous post was at 08:05 PM ----------
Oppo tool V1.6.5
https://drive.google.com/file/d/0B-aJHtkQl-HNT2E3RnNzb1o4dU0/view?pref=2&pli=1
Successfully rooted Oppo R7s with Oppotools 1.6.5
I have a Levovo Tab M10 FHD Plus TB-X606F running android 10.
After having the device for several months and reading everything I coul dfind on rooting it or previous versions. I decided to attempt. (Note: I have route plenty of phone and tablets before)
Steps and Results
Enable USB debugging
Install Magisk 8.0.7
Download Factory ROM
Copy boot.img to device via adb
Run Magisk and patch img.
Copy patched img to PC via ADB
fastboot flashing unlock (fasboot oem unlock erros)
fastboot boot patched_boot.img
Sending 'boot.img' (32768 KB) OKAY [ 1.512s]
Booting OKAY [ 0.063s]
Finished. Total time: 2.807s
Device rebooted on its own.
Rebooted into fastboot.
fastboot flash boot_a patched_boot.img
fastboot: error: cannot get boot partition size
fastboot flash boot_b patched_boot.img
fastboot: error: cannot get boot partition size
fastboot flash boot patched_boot.img
Sending 'boot' (32768 KB) OKAY [ 1.158s]
Writing 'boot' OKAY [ 0.445s]
Finished. Total time: 1.621s
DeviceDevice reboots on its own and boot loops
Use SP Flash Tool to reinstall factory image.
Device boots normally.
Use SP Flash to flash patched boot image.
Device boot loops.
Thoughts? Looks to me that the patched boot.img is invalid. Not sure how to verify or how else to get patched boot.img.
I also tried
fastboot boot patched_boot.img
Device reboots twice and then comes up with stock boot.img.
snickle said:
...
fastboot flash boot patched_boot.img
Sending 'boot' (32768 KB) OKAY [ 1.158s]
Writing 'boot' OKAY [ 0.445s]
Finished. Total time: 1.621s
DeviceDevice reboots on its own and boot loops
...
Thoughts? Looks to me that the patched boot.img is invalid. Not sure how to verify or how else to get patched boot.img.
Click to expand...
Click to collapse
Try installing Magisk using TWRP.
The patched boot.img method is only usually used when TWRP is unavailable.
Make sure you flash the stock boot.img (or the whole stock ROM) before installing TWRP and Magisk.
Got it working using canary version of magisk manager.
Hi, i just wanted to share the exact steps i took to root this tablet.
Funnily enough (for me at least), this was the easiest android device i've rooted out of all the ones i've previously owned. Thanks in part to OP of this thread!
The tablet i have is the following version:
TB-X606F_S300429_211101_BMP
unlock bootloader preparations
1. on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
2. go to Settings->System->DeveloperOptions.
3. Turn on: "OEM unlocking" and "USB debugging".
flash/root/recovery preparation
1. install latest: https://developer.android.com/studio/releases/platform-tools#downloads
2. install MTK_Android_USB_Driver
3. download TWRP for Lenovo Tab M10 Plus x606 (put it in the platform-tools directory)
4. reboot computer
5. run CMD command in the platform-tools directory:
fastboot flashing unlock
6. accept the conditions on the tablet screen
7. turn off tablet
8. turn on tablet into recovery mode with: Vol Up + Vol Down + Power (hold steady for several seconds after it vibrates)
9. choose "boot into bootloader" in the menu = now youre in fastboot mode
10. connect USB cable to computer
11. run CMD commands (wait for each commadn to finish ffirst of course):
fastboot flash recovery [TWRP you downloaded].img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
now youre in TWRP again:
1. finish the decryption in TWRP. (same pin as regular android encryption pin code if you chose one before)
2. do NOT keep read only
3. go to backup tab and make a backup (boot, system, vendor, data)
4. advanced wipe -> wipe "data"
Time to flash root/magisk
1. download Magisk-v23.0.apk
2. rename to zip
3. place the zip in tablet storage via USB cable
4. go to "install" in TWRP
5. select the magisk zip
6. flash magisk
7. reboot into system
8. enable installation of untrusted apk sources in android settings
9. start magisk manager just to check that things are OK
10. download root checker and verify root
11. reboot tablet a bunch of times to see that root is sticking
12. enable developer options again [for some reason it resets this during the flashing/wiping from above steps]
skribb said:
Hi, i just wanted to share the exact steps i took to root this tablet.
Funnily enough (for me at least), this was the easiest android device i've rooted out of all the ones i've previously owned. Thanks in part to OP of this thread!
The tablet i have is the following version:
TB-X606F_S300429_211101_BMP
unlock bootloader preparations
1. on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
2. go to Settings->System->DeveloperOptions.
3. Turn on: "OEM unlocking" and "USB debugging".
flash/root/recovery preparation
1. install latest: https://developer.android.com/studio/releases/platform-tools#downloads
2. install MTK_Android_USB_Driver
3. download TWRP for Lenovo Tab M10 Plus x606 (put it in the platform-tools directory)
4. reboot computer
5. run CMD command in the platform-tools directory:
fastboot flashing unlock
6. accept the conditions on the tablet screen
7. turn off tablet
8. turn on tablet into recovery mode with: Vol Up + Vol Down + Power (hold steady for several seconds after it vibrates)
9. choose "boot into bootloader" in the menu = now youre in fastboot mode
10. connect USB cable to computer
11. run CMD commands (wait for each commadn to finish ffirst of course):
fastboot flash recovery [TWRP you downloaded].img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
now youre in TWRP again:
1. finish the decryption in TWRP. (same pin as regular android encryption pin code if you chose one before)
2. do NOT keep read only
3. go to backup tab and make a backup (boot, system, vendor, data)
4. advanced wipe -> wipe "data"
Time to flash root/magisk
1. download Magisk-v23.0.apk
2. rename to zip
3. place the zip in tablet storage via USB cable
4. go to "install" in TWRP
5. select the magisk zip
6. flash magisk
7. reboot into system
8. enable installation of untrusted apk sources in android settings
9. start magisk manager just to check that things are OK
10. download root checker and verify root
11. reboot tablet a bunch of times to see that root is sticking
12. enable developer options again [for some reason it resets this during the flashing/wiping from above steps]
Click to expand...
Click to collapse
What ADB driver did you use? I cant get a good driver to load in Windows.
@be_the_shooter
Not 100% sure but I think it was Universal ADB Driver 1.0.4 from ClockworkMod. I'm on win7 x64.
(Sorry if this is the wrong place to post, I could not find a forum for the blackview bv 4900 pro)
I am trying to install TWRP (unofficial build at https://unofficialtwrp.com/twrp-3-5-2-blackview-bv4900-pro/ ) on my Blackview BV 4900 Pro, seems to be able to transfer it to my phone, but cannot start it. The files vbmeta.img and recovery.img come from the previous link, respectively https://unofficialtwrp.com/wp-content/uploads/2019/11/vbmeta.zip and https://www.mediafire.com/file/hq4sq1xlnkafduv/352_BV4900_pro_lopestom.rar/file .
Firmware: BV4900Pro_US_ZN128e_V1.0_20211119V08_20211119-2023
What I have done:
- USB debugging on,
- OEM unlocking,
- Re-start in fastboot mode,
- Plug phone to computer
- In terminal:
Code:
fastboot flashing unlock
< waiting for any device >
...
(bootloader) Start unlock flow
OKAY [ 4.394s]
finished. total time: 4.394s
(I confirmed on the phone that I wanted to unlock by pressing the volume + button),
-
Code:
fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [ 0.011s]
finished. total time: 0.011s
-
Code:
fastboot flash vbmeta vbmeta.img
target reported max download size of 134217728 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.007s]
writing 'vbmeta'...
OKAY [ 0.002s]
finished. total time: 0.009s
-
Code:
fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (23588 KB)...
OKAY [ 0.762s]
writing 'recovery'...
OKAY [ 0.313s]
finished. total time: 1.075s
- Unplug phone
- Turn off phone by pressing & maintaining power + volume +,
- Keep pressing power + volume +,
- See the "Select boot mode" page (that gives me the options to select Recovery mode / Fastboot mode / Normal boot),
- Select "Recovery mode",
- See Blackview's logo + the message "Orange state", then the phone becomes irresponsive. It is still turned on, but nothing on display. I can run
Code:
adb reboot recovery
and it will reboot, but again in orange state, then it reboots to the "normal" system.
What am I missing? Is this version of twrp unsuitable for my phone?
Apparently there used to be a twrp at https://4pda.to/forum/index.php?showtopic=789936&st=2060#entry110507536 but it is not available anymore :-(
Apparently there was another twrp developed for this phone, shared at https://4pda-to.translate.goog/foru...=fr&_x_tr_hl=fr&_x_tr_pto=wapp#entry111020420 but the link is in error too :-(
I was able to flash a different firmware on the phone ( BV4900Pro_S1_210909 ), but the result is still the same.
Once rebooted (in recovery), the screen is still black (after a green line briefly flash at the top of the screen). The phone is still on :I can do
Code:
adb shell
BV4900Pro:/ #
But then if I try, following this post ( https://forum.xda-developers.com/t/guide-flashing-roms-with-twrp-black-screen.3913052/ ), I try to use twrp from the command line, then it seems that it is not started:
Code:
BV4900Pro:/ # twrp wipe cache
TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit.
The files at
Стол заказов кастомного рекавери - 4PDA
Стол заказов кастомного рекавери
4pda.to
works, but you have to create an account to download them.
There is a tutorial on how to pass those captcha at https://doorsgeek.blogspot.com/2015/08/4pdaru-loginregister-captcha-tutorial.html
Hello tbtbtata!
Could you upload the working TWRP for BV4900 Pro?
The files on the links above does not exist any more.
Thanks in advance.
Edit: I've got it. One has to register on 4pda, then you can download files.
Edit: Unfortunately this TWRP does not work on my BV4900Pro (Edition 2022 with android 12).
WowkaZ said:
Hello tbtbtata!
Could you upload the working TWRP for BV4900 Pro?
The files on the links above does not exist any more.
Thanks in advance.
Edit: I've got it. One has to register on 4pda, then you can download files.
Edit: Unfortunately this TWRP does not work on my BV4900Pro (Edition 2022 with android 12).
Click to expand...
Click to collapse
Hey! Sorry for the very late reply. They are attached. I am sorry they are not working on more recent versions of that phone, and honestly have no idea how to update them :-(
Keep us posted!
WowkaZ said:
Hello tbtbtata!
Could you upload the working TWRP for BV4900 Pro?
The files on the links above does not exist any more.
Thanks in advance.
Edit: I've got it. One has to register on 4pda, then you can download files.
Edit: Unfortunately this TWRP does not work on my BV4900Pro (Edition 2022 with android 12).
Click to expand...
Click to collapse
Hey btw you don't neeed twrp to flash GSI, just so you know…
Not as good as lineageOs, bat with fewer bloatwares and more up-to-date than what your phone cme shipped with.
[SOLVED] GSI on BV 4900 Pro: "Cannot load Android system. Your data may be corrupt. "
tl;dr: I followed the procedure to flash Android's Generic System Image (gsi_gms_arm64-exp-TP1A.220624.014-8819323-8a77fef1) on my Blackview BV 4900 Pro, but I am stuck in a bootloop that ends with "Cannot load Android system. Your data may be...
forum.xda-developers.com
I have the 2022 Version too. I try to flash the 2021 Version lk.bin (bootloader) and hope it works. Because the 2022 lk.bin don't play nice with a empty vbmeta.
WowkaZ said:
Hello tbtbtata!
Could you upload the working TWRP for BV4900 Pro?
The files on the links above does not exist any more.
Thanks in advance.
Edit: I've got it. One has to register on 4pda, then you can download files.
Edit: Unfortunately this TWRP does not work on my BV4900Pro (Edition 2022 with android 12).
Click to expand...
Click to collapse