Develop Bugs

Idiot's guide to flashing the Xoom (for fun and profit)

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

[TUT] Root & install any custom recovery on your XS/XSL

Hey guys! So I just had my first Xperia phone-rooting experience, after ditching my old Galaxy Ace for an Xperia SL,
and I thought I'd share my experience on how to root your Xperia S or SL, and install CWM on it.
I bricked it TWICE since I didn't find good tutorials, so I thought I'd help out newcomers.
The following steps were followed on a Windows Machine, on a "virgin" Xperia SL whilst on the latest stock 4.1.2 build (6.2.B.1.96).
__________________________________________________
__________________________________________________
INGREDIENTS (what you need):
Flashtool. They say it is recommended to use one version before the latest (i.e. right now the latest is 0.9.13.0, so you should use 0.9.12.0).
However, the one that worked for me was 0.9.11.0. You can get the very latest here (official Flashtool website), 0.9.12.0 here (uploaded.net), or you can get the one I used here (mediafire). NOTE: The latest version (0.9.16.0) might fix the Windows 8+ recognition issue stated below. Try that version first.
The stock 6.2.B.0.211 kernel.
DooMLoRD's Easy Rooting Toolkit v18.
The stock 6.2.B.1.96 kernel.
DooMLoRD's CWM6 Installer or LEDelete's RecoverX.
An Xperia S/SL with stock JB 6.2.B.1.96 and USB Debugging Mode enabled.
Android SDK.(optional, in case you want to install TWRP recovery)
A computer.
Patience.
__________________________________________________
__________________________________________________
DISCLAIMER:
I am not responsible for whatever happens to your phone. Whatever does happen to your phone is your fault, since you decided to be a daredevil and try this out.
Therefore I am not to be accused of any damage (temporary or permanent) done to your phone. I will try to be as helpful as possible, should you get lost or break your XS/SL.
I bricked my phone in my first try, and fixed it, so I think I can help you.
STEPS
Ok, now that the warning is over, let's go ahead and root the hell out of that Xperia.
I am assuming you have already installed Flashtool, and that you know what it does. If you have any doubts about it, you can Google that information or ask me on this thread.
Also, this tutorial tells you how to do this on unlocked bootloader. Sony has a nice page on how to unlock it, in case it is.
The instructions are here, including how to check if your phone has or not an unlocked bootloader.
Basically, a locked bootloader means you can't flash custom kernels on your phone (hence not allowing you to flash CWM, for example).
First of all, you need to make sure whether you're on Windows 7, Windows 8, or Windows 8.1. This is very important, because it can save you hours of useless efforts to get your PC to recognize your device.
Apparently, both Windows 8 and Windows 8.1 struggle at identifying the right drivers for your phone in order for you to flash anything using Flashtool. If you're on Windows 7, head on to step 3.
If you're on a Windows 8/8.1, and you have no trouble with Flashtool (it recognizes your phone right away), then you can go to step 3 as well.
IF YOU'RE ON W8/W8.1, and your phone isn't recognized, check if you're using USB 3.0 ports, this might be the reason.
If you're on Windows 8/8.1 and Flashtool doesn't recognize your phone, then you might be in trouble; go to step 2.
FOR XSL USERS: it is very likely your phone is not recognized right away, but Flashtool might also show you a list with all the Xperia devices for you to choose your model from. Choose Xperia S, you'll be fine.
Windows 8/8.1 introduced an issue with drivers and that's why your Xperia phone might not get recognized in Flashtool as soon as you plug it in. If this is the case, try this:
Go to C:\Flashtool (or wherever you have installed it), and run the .exe inside the drivers folder. This should start an installer that will extract the desired drivers onto your system.
You must check your phone's drivers along with the Flashboot and Fastboot drivers(the last two in the list).
If the installation of the drivers finished successfully, then go to step 3. Otherwise, you must "Disable Driver Signature Enforcement" on your Windows 8/8.1 PC.
This will let you install unsigned drivers on your computer. Once you're done with Step 9 in that tutorial, try to install the drivers on C:\Flashtool\drivers once again.
This time, you should be greeted with this message:
{
"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"
}
Click on "Install this driver software anyway" as many times as prompted (three times, in my case).
When this driver installation is done, a window will tell you the installation is finished and a list with the drivers that were successfully installed will be shown.
All of the selected drivers should have a green check on their left.
Should this window still show you red crosses and fail to install the drivers, I'm afraid you might be screwed, unless you can find a Windows 7 PC.
So you have no problems with your drivers? Great! This means you can root your phone right away.
The method I use is the same explained here, but I'll explain it with more detail, as the one there assumes you know a lot about flashing.
The method DooMLoRD uses is flashing an older kernel first (6.2.B.0.211), because his toolkit doesn't support the latest 6.2.B.1.96 kernel. This is called downgrading you kernel. This will wipe all your applications and settings, just like a factory reset. Your SD data will remain intact.
So, what you need to do is download the files on the "Ingredients" SECTION (and install the Android SDK), and then:
Open Flashtool. Verify your phone has been detected by Flashtool. If it hasn't, install a different version of Flashtool while your phone is connected. Then click on the lightning icon on the top left.
Select Flashmode, because we're going to select the kernel files to flash (to turn on your cell phone on flash mode, turn it off, and once it's off plug it in to your computer while holding down the VOLUME DOWN key, a green LED will flash. If it's blue, you're in fastboot mode and you held down the VOLUME UP key instead).
Change the source folder to wherever you downloaded the stock 6.2.B.0.211 and 6.2.B.1.96 kernels.
Make sure the highlighted on is the .211 kernel, and click on flash. This should start the kernel downgrade and restart your phone once it's done.
When your phone has booted, disconnect your phone and close Flashtool (this is very important).
Great! Now your phone has the old .211 kernel and can be rooted. Extract DooMLoRD's Easy Toolkit to your C drive.
Run the "runme_file" that corresponds to your OS. MAKE SURE YOU RUN THE RIGHT ONE. Since this tutorial is for Windows PCs, the file you should run is the .bat.
This will open a console window with a set of instructions. Once you've read them and your device is plugged in (it must be on), press enter. The toolkit will go on from then. You must not worry when it says something about daemons and outdated servers.
Your device will restart as soon as it's done. You can check if it really is rooted by opening the apps drawer and verifying the SuperSU app is there.
Remember, you just downgraded your phone's kernel, so some of the old stock apps will come back up. You can uninstall them, but I recommend you do this later on (I'll tell you when).
Now your phone is rooted.
NOTE: The app drawer takes a while to fully load the first time after the root, so give it some time and you should see the SuperSU app. Don't rush things and assume it isn't there.
I did that and rooted it twice, thinking it had failed. That was such a waste of time :silly:.
Now that your phone is rooted, you can go and flash the newest stock kernel. Follow steps 3.1. to 3.5., but flash kernel 6.2.B.1.96.
Now your phone is rooted and on the latest stock kernel! Feel free to uninstall those useless stock apps that appeared back on your app drawer.
__________________________________________________
CWM INSTALLATION STEPS
This should be relatively easy now. Your phone is now rooted, and you will now flash CWM Recovery on your phone. For this, I found a quick installer by DooMLoRD.
Just extract it anywhere, run it (cwm-install-en.bat, press Enter 3 times and it will start) while your phone is connected via USB, and you should be just fine.
I had to use this method, since I used RecoverX and it did not work.
You know CWM was flashed correctly when you shut down your phone, turn it on and your see the LED turns on BLUE when the Sony logo comes up.
When it does, press the Volume Up button and the LED should turn GREEN for a couple of seconds, then boot into Recovery.
__________________________________________________
TWRP INSTALLATION STEPS
You might also want to install TWRP instead of CWM, because RaymanFX's ROMs recommend this, or because you come from a different phone and you had TWRP on it.
If you want to install one of RaymanFX's ROMs, I recommend you get the img.boot file from the ROM (extract the install .zip file and look for it) and flash it as a new Recovery. This will get you TWRP.
If you just want to flash it, you can try out the TWRP Manager app from the Play Store. This is pretty straightforward.
Also, you can try flashing the boot image on TWRP's website using fastboot (this is why you need the Android SDK). The instructions are there, just make sure you have the .elf image file in the same folder as the Android adb.exe and the fastboot.exe files, and run the command they tell you to use while your phone is connected.
Just make sure you have Busybox installed.
I strongly recommend you do a NAND Backup with your newly installed CWM Recovery.
In order to flash any custom ROM, the instructions are different, but they all follow a pattern. If you're in rooted stock, Factory reset your phone and Wipe the Dalvik cache.
If you're in a custom ROM and you're flashing an update to that ROM (say, from Beta 2 to Beta 3), you can do a dirty install on top of it (no wipes), or Wipe Dalvik and normal cache before doing so.
These instructions may vary between ROMs, however.
If you have any questions, please don't hesitate to post here. I hope this was helpful enough for everyone!
This is all DooMLoRD's work and I'm only saying how you could use it. I do not own any of the downloadable files I have posted here.
DooMLoRD's Dev-Host

Thanx dude.

Dr. NAC said:
Thanx dude.
Click to expand...
Click to collapse
Did it help? Any feedback that might help me improve this tutorial?

Good job bro
Sent from my Xperia S using xda premium

I have tried RecoverX to install recovery. The installation is finished but cannot boot into the CWM.

hm9408 said:
For this, I found a quick installer by DooMLoRD. Just extract it anywhere, run it (cwm-install-en.bat, press Enter 3 times and it will start) while your phone is connected via USB, and you should be just fine. I had to use this method, since I used RecoverX and it did not work. You know CWM was flashed correctly when you shut down your phone, turn it on and your see the LED turns on BLUE when the Sony logo comes up. When it does, press the Volume Up button and the LED should turn GREEN for a couple of seconds, then boot into Recovery.
Click to expand...
Click to collapse
timespace7 said:
I have tried RecoverX to install recovery. The installation is finished but cannot boot into the CWM.
Click to expand...
Click to collapse
Might as well try DooMLoRD's installer.

I have windows 8.1 and i have successfully installed the drivers but my PC still doesn't recognize my phone. Every time i try to enter the fast boot, the led turn blue, my windows sais that the device is not recognized and the led turns off and my phone starts charging...any ideas how to fix this? I try to make the fastboot work to unlock the bootloader.
PS: I have windwos 8.1
PPS: Never mind i figured it out...i just used the fix for USB3.

catalin1122 said:
I have windows 8.1 and i have successfully installed the drivers but my PC still doesn't recognize my phone. Every time i try to enter the fast boot, the led turn blue, my windows sais that the device is not recognized and the led turns off and my phone starts charging...any ideas how to fix this? I try to make the fastboot work to unlock the bootloader.
PS: I have windwos 8.1
PPS: Never mind i figured it out...i just used the fix for USB3.
Click to expand...
Click to collapse
I will note this on the tutorial. I had forgotten how picky W8 is with USB 3.0 ports, too.
Anything else I should add to this tutorial, by the way?
Don't forget to click on that thanks button

[TUT] How to install CyanogenMod 11 /or any other ROM on your Xperia S 6.2.b.1.96

Okay guys,
I spent a whole day yesterday to exterminate lame SONY's firmware, and get a refreshment alternation
so I gathered all tutorials, which I had followed to give my Xperia S new soul, and made this all-in-one tutorial for anyone, who's not sure how to do it.
Big thank to DooMLoRD, who's is making all this awesome tools and stuff to make our Xperias alive again.
Before proceding, Your Xperia S should run on the latest official Sony's firmware (6.2.b.1.96). Otherwise...otherwise you probably ought to update it to the latest version.
Here are the links to the sites I used. I also recommend you to check them out, because there may be a more recent version of a file:
http://forum.xda-developers.com/showthread.php?t=2555243
http://forum.xda-developers.com/showthread.php?t=2447319
http://forum.xda-developers.com/showthread.php?t=2417672
1. Bootloader unlock
Checking (source: JuniorMember's post: http://forum.xda-developers.com/showpost.php?p=44713761&postcount=14)
1.1.1. In dial pad, type in *#*#7378423#*#*
1.1.2.Go to Service Info > Configuration
1.1.3. And check the Rooting Status
If it's Bootloader unlock allowed:Yes/No, then its not unlocked. If it says NO, you're not able to unlock it.
And if it's Bootloader unlocked:Yes, then it's (already) unlocked.
Unlocking (source: DooMLoRD's tutorial)
[ before we begin unlocking bootloader ]
1.2.1 Get the IMEI code for your device: type *#06# in phone dialer to find it out; note only the digits (no dashes)
1.2.2 Download the fastboot package with usb drivers (alternate drivers if the ones in package dont work OR this)
IMPORTANT: if you are using Windows 8 you will need to enable few things to allow driver installation
1.2.3.Make sure you have a windows PC with USB cable to connect the phone
1.2.4.Power down your phone and keeping the Volume Up button pressed connect the USB cable to PC; this will trigger FASTBOOT mode and windows will start driver installation, extract the above package and point the driver install to that location (usb_driver) folder.
If a phone enters but does not stay in a fastboot mode:I had that kind of problem, but I'm not sure how I actually fixed it; I only remember I did that:
1.2.4.1. Download and install Flashtool . After Installing, go to the folder where fastboot is installed and look for drivers folder; there you'll find Flashtool-drivers.exe. Install that: Be aware that there are Flashboot and Fastboot drivers at the bottom or at the top of the list Check also your phone's name.
1.2.4.2. If still does not work go to Device manager, trigger fastboot mode, connect to your computer, and quickly (when S1 Boot or sth like that appers in Device Manager) click with right mouse button (go to properties), then update driver and point to (usb_driver) folder in fastboot_with_Android_USB_file folder -> step 1.3.6.
1.2.5. Once drivers are installed just disconnect cable and power on device
[ how to unlock ] (official way)
1.3.1 First, you should confirm that it is possible to unlock the boot loader of your phone by checking the service menu: steps 1.1.1 - 1.1.3
1.3.2 Go to: http://unlockbootloader.sonymobile.com/ and read everything!
1.3.3 At the bottom click 'Start Unlocking the Bootloader'. Scroll to the bottom of the page and click "Continue" You will get numerous prompts, read all info and if you agree, click on "Accept"/"OK"/"Proceed"
1.3.4 Finally you will get a "Create Unlock request" page, enter your IMEI (sometimes the last digit needs to be removed for this to work), name and email address
1.3.5 You should now receive your unique unlock key via EMAIL, SAVE THIS KEY SAFELY
1.3.6 Extract fastboot_with_Android_USB_file.rar and open fastboot folder
1.3.7 Hold SHIFT and right click on the background of the folder Select 'Open command window here'
1.3.8 Connect your phone in fastboot mode (turn phone off, hold Volume UP button and plug in USB Cable) [make sure drivers are installed as explained above)
1.3.9 In the cmd windows type in fastboot.exe -i 0x0fce getvar version
1.3.10 If a value is returned (it will return 0.5), it means the phone is correctly connected
1.3.11 Type in fastboot.exe -i 0x0fce oem unlock 0xKEY and replace KEY with the key which u received earlier.
1.3.12 You're device should now be bootloader unlocked. You can check by followin steps 1.1.1 - 1.1.3.
2. Root (source: DooMLoRD's tutorial)
2.3.1 Download the three files from the download section in this post.
2.3.2 Open FlashTool and flash the XperiaS_LT26i_6.2.B.0.211_KernelOnly.ftf - 6.36 MB file, this is JUST the kernel of an older firmware which was rootable.
2.3.3 How to flash Put XperiaS_LT26i_6.2.B.0.211_KernelOnly.ftf to firware folder, which you can find in Fastboot's installation folder. Then hit the lighting strike, select Flashboot mode and select the kernel and hit flash and follow instructions how to enter flashmode.
2.3.4 Now once flashing is done reboot device and connect to PC in usb debuggin mode
2.3.5 CLOSE FLASHTOOL <<< VVVIMP STEP (Very very very important step it took me some time to figure out its meaning)
2.3.6 Extract the file DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit.zip to root directory on c:\
execute runme_ file corresponding to your OS on desktop PC, this will execute a SPECIAL version of DooMLoRDs easy rooting toolkit <<< VVVIMP STEP
2.3.7 the above step is crucial! if you use any older version of the toolkit then IT WILL NOT WORK!
2.3.8 after rooting is over the device will restart
2.3.9 you can verify if device is rooted by checking for SuperSU app (it is the newest version)
2.3.10 once that's done, power down device and open FlashTool again
2.3.11 now flash XperiaS_LT26i_6.2.B.1.96_KernelOnly.ftf - 6.33 MB file to get back to the true kernel for the firmware
that's it after flashing is done just disconnect and power on device and enjoy rooted phone! Check with Root Checker app from GPlay.
3. CWM Recovery (source: hm9408's thorough version of DooMLoRD's tutorial)
3.1 Go to google play and download busybox. Once installed, open the app and tap install Also, make sure, you have SuperSU installed.
3.2. This should be relatively easy now. Your phone is now rooted, and you will now flash CWM Recovery on your phone. For this, hm9408 found a quick installer by DooMLoRD.
3.3 Just extract it anywhere, run it (cwm-install-en.bat, press Enter 3 times and it will start) while your phone is connected via USB, and you should be just fine. I had to do this step twice, because I didn't know you have to grant something with SuperSU. So during the process, watch the phone's screen.
3.4 You know CWM was flashed correctly when you shut down your phone, turn it on and your see the LED turns on BLUE when the Sony logo comes up. When it does, press the Volume Up button and the LED should turn GREEN for a couple of seconds, then boot into Recovery.
4. Installing custom ROM and gapps (google apps)
There's a link toCyanogenMod 11 beta 3 by RaymanFX which has already included kernel.
Other ROMs may not have included kernel, so you'll have to (1) flash it with Flastool, if it has kernel extension or (2) install it via recovery, it it has .zip extension.
4.1 Copy your ROM and gapps (their extensions have to be .zip.
4.2 Boot into recovery (step 3.4).
4.3 Navigate (with volume + and -, and power to select) to install zip, then select the file of you rom, install it, then install also the gapps by selecting the gapps.zip.
4.4. This is the most important step, DO NOT SKIP IT AT ALL COSTS For God's sake, in the main menu, wipe the cache and partitions and dalvik's cache. (I'm not sure if it's available to wipe dalvik's cache, but if it is, wipe it).
I forgot to wipe, and, holy cow, almost lost my pants, because phone didn't start, there was only sony's logo, slowly passing away again and again.
Well if that happens, look for an Xperia S firmware (e.g.) and appropriate kernel (e.g.), flash them via flashtool and wipe your sweat .

I think for a 2 years old phone, everybody should already know how to do this.
Or i think most of the people here on Xperia S XDA do already know how to do this.

xDroidZz said:
I think for a 2 years old phone, everybody should already know how to do this.
Or i think most of the people here on Xperia S XDA do already know how to do this.
Click to expand...
Click to collapse
Lol ya.

Sure?
xDroidZz said:
I think for a 2 years old phone, everybody should already know how to do this.
Or i think most of the people here on Xperia S XDA do already know how to do this.
Click to expand...
Click to collapse
I've had it for 2 years, but spent a whole day yesterday to install CM, because I struggled with fastboot drivers for 4hs, then 1h to root it, then another 2hs to properly install CWMrecovery, because I didn't know I have to have BusyBox installed and then I didn't wipe the cache and had to do everything again. And don't say me everybody should know that, because there are people who does not even try to do that, because then don't konw where to start and nothing.
Cheers!

Joej970 said:
I've had it for 2 years, but spent a whole day yesterday to install CM, because I struggled with fastboot drivers for 4hs, then 1h to root it, then another 2hs to properly install CWMrecovery, because I didn't know I have to have BusyBox installed and then I didn't wipe the cache and had to do everything again. And don't say me everybody should know that, because there are people who does not even try to do that, because then don't konw where to start and nothing.
Cheers!
Click to expand...
Click to collapse
are you kidding me? it takes me max 1 hour to read tutorial, unlock BL, flash custom kernel and flasch CM rom :laugh:

Joej970 said:
I've had it for 2 years, but spent a whole day yesterday to install CM, because I struggled with fastboot drivers for 4hs, then 1h to root it, then another 2hs to properly install CWMrecovery, because I didn't know I have to have BusyBox installed and then I didn't wipe the cache and had to do everything again. And don't say me everybody should know that, because there are people who does not even try to do that, because then don't konw where to start and nothing.
Cheers!
Click to expand...
Click to collapse
Nah. Max is 1H. there are alot of TUT already. but thanks anyways for this TUT helps alot of people who are actually new to this device

dobi235 said:
are you kidding me? it takes me max 1 hour to read tutorial, unlock BL, flash custom kernel and flasch CM rom :laugh:
Click to expand...
Click to collapse
It takes you one hour once you exactly know how to do it and in case you already have all files downloaded.
And about tutorials: they're often incomplete. In my case, I struggled with finding drivers for fastboot and making them work 4hs. The unlock tutorial says to install one drivers then try another, but none of them worked. So it took me time to search forums and find something out. Here, I wrote what I'd done, so anyone else would know what to do.
Edit: every tutorial about unlocking says Windows should report unsuccessful installation when you connect the device in fast boot mode. Well, my didn't report that, so I wasn't able to point to the usb_folder. And then phone booted up after 5secs in fastboot.

Joej970 said:
It takes you one hour once you exactly know how to do it and in case you already have all files downloaded.
And about tutorials: they're often incomplete. In my case, I struggled with finding drivers for fastboot and making them work 4hs. The unlock tutorial says to install one drivers then try another, but none of them worked. So it took me time to search forums and find something out. Here, I wrote what I'd done, so anyone else would know what to do.
Edit: every tutorial about unlocking says Windows should report unsuccessful installation when you connect the device in fast boot mode. Well, my didn't report that, so I wasn't able to point to the usb_folder. And then phone booted up after 5secs in fastboot.
Click to expand...
Click to collapse
no it took me hour to search for tutuorials (doom has for root and for unlocking BL too), read that, backup TA partiton, unlock, root, flash... DONE

I needed an whole afternoon, too! If you have to read everything from beginning and you are not able even to deal with the technical terms it needs long time. So, if I wouldn't have done it before, this tutorial would have been very useful to me :good:

magician
dobi235 said:
no it took me hour to search for tutuorials (doom has for root and for unlocking BL too), read that, backup TA partiton, unlock, root, flash... DONE
Click to expand...
Click to collapse
Well okay. Then write that down to a paper and stick it to a mirror, so you'll see your extraordinary achievement every time you wake up, and be proud of yourself, cause you did all that for the fisrt time in only one hour, although everyone else needed an afternoon. You're probably the smartest person I've ever seen, cause you apparently do magic :good:
Repair shops should totally hire you, since they often need an eternity to do their job.
Cheers

Joej970 said:
Well okay. Then write that down to a paper and stick it to a mirror, so you'll see your extraordinary achievement every time you wake up, and be proud of yourself, cause you did all that for the fisrt time in only one hour, although everyone else needed an afternoon. You're probably the smartest person I've ever seen, cause you apparently do magic :good:
Repair shops should totally hire you, since they often need an eternity to do their job.
Cheers
Click to expand...
Click to collapse
i only wanted to say that this thread is completely unnecessary.. this phone is more than 2 years old... last update was i think 1year ago.. so there is nothing new... tutorials for unlocking BL (2nd March 2012) and for rooting (17th June 2013) are here for more than a year...and tutorial for instaling CM you can find in almost every CM thread... thats all I wanted to say :victory:... have a nice day

It is kinda necessary..
Some people still dont know how to flash these roms...And then end up spamming other threads...:/

Joej970 said:
Okay guys,
I spent a whole day yesterday to exterminate lame SONY's firmware, and get a refreshment alternation
so I gathered all tutorials, which I had followed to give my Xperia S new soul, and made this all-in-one tutorial for anyone, who's not sure how to do it.
Big thank to DooMLoRD, who's is making all this awesome tools and stuff to make our Xperias alive again.
Click to expand...
Click to collapse
Your method is long and unnecessarily beating around the bush. Here's a much quicker way (how I did it in less than half an hour):
1) Copy the ROM zip to your internal storage
2) Unlock bootloader with Sony's info on their site.
3) Extract boot.img from the ROM zip / kernel zip.
4) In fastboot mode,
Code:
fastboot flash boot boot.img
fastboot reboot
5) Go into recovery while it's rebooting, wipe everything & flash the ROM zip.
TBH, DoomLord's stuff is not required, never really was for me..
Sure, it's good stuff, but not required in this case..

The tutorial is good, it's just unfortunate, is that after more than two years, yet no one has been able to unlock the bootloader problem that allows not be unlocked.
Sent from my LT26i using XDA Premium 4 mobile app

Great_Geek said:
Your method is long and unnecessarily beating around the bush. Here's a much quicker way (how I did it in less than half an hour):
1) Copy the ROM zip to your internal storage
2) Unlock bootloader with Sony's info on their site.
3) Extract boot.img from the ROM zip / kernel zip.
4) In fastboot mode,
Code:
fastboot flash boot boot.img
fastboot reboot
5) Go into recovery while it's rebooting, wipe everything & flash the ROM zip.
TBH, DoomLord's stuff is not required, never really was for me..
Sure, it's good stuff, but not required in this case..
Click to expand...
Click to collapse
Hey, hey, hey,
where do you type that code in? In terminal emulator on a phone or maybe cmd on a computer? I've seen a lot of tutorials ordering to type a code, but none of them actually explained how and where you have to write it.
Thankss!

Joej970 said:
Hey, hey, hey,
where do you type that code in? In terminal emulator on a phone or maybe cmd on a computer? I've seen a lot of tutorials ordering to type a code, but none of them actually explained how and where you have to write it.
Thankss!
Click to expand...
Click to collapse
You use fastboot.exe or the fastboot binary for linux, same one that you used for unlocking bootloader..
Finding something to type into terminal emulator is pretty rare, and it'll usually be specified that you need to type it there..

Bootloop after accidental re-enabling Init.d

Hello,
At first, sorry for my English, because I'm from Poland.
I have a problem: some time ago I've swapped the memory by rooting, installing Busybox, enabling Init.d and adding swap script to system/etc/init.d. Today, the swap unexpectedly stopped working. I've entered the Universal Init.d app to verify that Init.d is enabled. Unfortunately, I've accidentally clicked the Install option and restarted the phone. After that, my phone went in a bootloop.
Question is: how to unbrick phone, preferably without data loss? I have few important contacts on phone memory and I don't want to lose it.
My phone is Sony Xperia M C1905 with Android 4.3 (15.4.A.0.23) and Locked bootloader.
Please help.

krnl22 said:
Hello,
At first, sorry for my English, because I'm from Poland.
I have a problem: some time ago I've swapped the memory by rooting, installing Busybox, enabling Init.d and adding swap script to system/etc/init.d. Today, the swap unexpectedly stopped working. I've entered the Universal Init.d app to verify that Init.d is enabled. Unfortunately, I've accidentally clicked the Install option and restarted the phone. After that, my phone went in a bootloop.
Question is: how to unbrick phone, preferably without data loss? I have few important contacts on phone memory and I don't want to lose it.
My phone is Sony Xperia M C1905 with Android 4.3 (15.4.A.0.23) and Locked bootloader.
Please help.
Click to expand...
Click to collapse
may be you can use flashtool to the stock firmware , and you can download the stock firmware here https://drive.google.com/file/d/0B_d8uWGbkaetNHNXUGZXQkFIUTg/edit?usp=sharing, after that install the flashtool, and install the flashtool to that was place it i directory of flashtool installation folder that called flashtool-driver.exe, you can install driver that you need it, after that copy the ftf file that have you download it before and copy to flashtool installation folder in the firmware folder, after that open the flashtool select the thundfer/flash and select the ftf file and uncheck the data to avoid wipe data after flash it, so you don;t have to loose all of your contact , after that hit flash and wait for a while second until the flashtool prepare for flash it and if ready turn off your device and hold the vol down and connect your xperia m to pc, after that only wait until the flash process is completed, after completed turn on your phone and disconnect from pc and wait for a while minute untill your phone is boot up correctly ok, don't worry your data is not wipe ok:good:

Nicklas Van Dam said:
may be you can use flashtool to the stock firmware , and you can download the stock firmware here (url here), after that install the flashtool, and install the flashtool to that was place it i directory of flashtool installation folder that called flashtool-driver.exe, you can install driver that you need it, after that copy the ftf file that have you download it before and copy to flashtool installation folder in the firmware folder, after that open the flashtool select the thundfer/flash and select the ftf file and uncheck the data to avoid wipe data after flash it, so you don;t have to loose all of your contact , after that hit flash and wait for a while second until the flashtool prepare for flash it and if ready turn off your device and hold the vol down and connect your xperia m to pc, after that only wait until the flash process is completed, after completed turn on your phone and disconnect from pc and wait for a while minute untill your phone is boot up correctly ok, don't worry your data is not wipe ok:good:
Click to expand...
Click to collapse
OK, flashing now.
I'm a advanced Android user and I know about Flashtool, but before you posted I didn't know about flashing without data loss, that's why I wrote this thread.
EDIT: Thanks, that saved my phone!

krnl22 said:
OK, flashing now.
I'm a advanced Android user and I know about Flashtool, but before you posted I didn't know about flashing without data loss, that's why I wrote this thread.
EDIT: Thanks, that saved my phone!
Click to expand...
Click to collapse
ya you're welcome

Blackview BV9000 Pro-F ROOT SUCCESS [TWRP + Magisk v16 + Stock Rom]

EDIT: included rough procedures for OEM unlocking, and updated link to recovery-verified.img (Sorry for uploading the wrong file ><)
Hi all bv9000 pro Users!
Recently I went on a journey to root this awesome rugged phone with one purspose: to remove that F*@(#&$ god awful loud annoying sound triggered by the OS when you use a camera app to take a picture + the boot startup sound (A bug blackview hasn't gotten around to fixing).
I successfully managed to port TWRP 3.1.1 from the Blackview bv8000 Pro and run it on the Blackview bv9000 Pro-f!
I've then managed to flash in Magisk to gain root access.
DISCLAIMER: I do not take responsibility for any bricked phones caused by the process, do so at your own risk (yadayadayada).
NOTE 1: Although I've got it running on the bv9000 Pro-F, this image should also work for the non-fullHD version, if someone can test this I'd be happy.
The link to the stock ROM (with the modified recovery img) can be found in the post below.
NOTE 2: No need to download anything other than what I've listed, Magisk is included in my custom recovery to circumvent the need to load the devices encrypted storage (or any other external storage) nothing stops you from mounting external usb storage.
What you'll need:
- USB Mouse (As there is no touchscreen input support, your device should have come with a usb-c otg cable so there's no problem here!)
- MediaTek SP Flash tools (I'd recommend the latest version) https://spflashtool.com/
- unlocked bootloader (You should be able to do this via the developer settings -> unlock OEM Bootloader)
EDIT: To unlock the boot loader, do the following:
1) Go to settings -> unlock OEM Bootloader (tick)
2) plug your device in (assuming you have ADB installed), use adb to access fastboot via. command prompt:
"adb reboot bootloader"
Then once the device is rebooted into fastboot mode
"fastboot oem unlock"
KEEP IN MIND THIS WILL REMOVE ANY FILES, so back them up
- I've done this with windows, but you should be able to repeat with linux no problems!
- A little patience
Pre-preparation:
First install any updates and back up your data (it's just easiest to use the google cloud backup as restoring becomes easy as pie, updating also fixes the setup wizard crashing on first setup). This is necessary because OTA updates cannot be performed with TWRP recovery, and flashing TWRP before doing OTA updates will flick the device into a recovery boot loop.
Install the SP Flash tools, and the MediaTek VCOM Drivers
(I won't link the specifics here, a quick google search should be able to help you, just note you might need to disable driver signature enforcement)
Two options for flashing:
1)
My Full Stock ROM already pre-prepared for flashing:
Patched ROM
No need for extra prep here! you should just be able to load the scatter
2)
My custom patched TWRP stock rom: recovery-verified.img
Blackiew's stock rom: stock rom
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
Once you've done with the pre-prep, switch off your device, take a deep breath and you're ready to go!
Steps!
1) Load up SP Flash Tools, select the android scatter file you've downloaded in the R06 folder
2) Select Download Only (I MEAN IT, FORMATTING WILL REMOVE YOUR IMEI AND RENDER THE PHONE USELESS)
3) Deselect everything but recovery (You only want to flash this)
4) Hit download
https://pasteboard.co/HkufwZZ.png
5) Hold volume up + power and plug in your phone, keep the volume up button held
6) very quickly the flash should be complete, and you should be greeted with a big ol' green tick to verify
https://pasteboard.co/HkuiTBB.png
7) Once you're done, remove your USB cable, plug in the OTG then we proceed to flash magisk
8) Hold power + volume up until you reach the bootloader, then use the menu to select recovery
9) You *should* be greeted with the TWRP recovery screen (Which is great success! )
DON'T PANIC IF YOU CANNOT USE THE TOUCH SCREEN, the kernel I've patched is missing this, seems the driver is different between touch screens, just plug in your OTG mouse to continue from here!
10) Use your mouse to first hit cancel, we don't need to decrypt the user data storage.
11) But oh no! it's all in Russian (no problem, Next step sorts that)
12) Use your mouse to navigate the menus as shown here to change to English! (or your preferred language) Change Language
13) Click install, then navigate up folder levels until you are in the root directory
14) scroll down and click on Magisk.zip, install it, allow it to install any apps as system apps (because this will then install to the system image, not the userdata)
15) reboot the phone (if it hasn't rebooted already)
16) You should be able to boot into your usual phones OS, if you don't see Magisk listed in your phone apps, just download it from here:
Magisk Manager
17) Congratulations! You should have complete root access :laugh::laugh::laugh:
Feel free to express your thanks, or list any problems you have, but keep in mind my studies take all my life, so I may not be able to help with all the problems you have

Congrats! Would it work on the BV9000 HD version?

Hi!
From what I've seen they both run the helio p25 chip
(Just a difference in RAM size) so it should.
You're more than welcome to try.
Just keep a backup of the original ROMs recovery. If something goes wrong during the boot to recovery you can easily re flash

hi i tried both optinos but they didn't work for me
I tried the first and the second options and it was showed me same error:
ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
I tried download only, format all and download, if i install original ROM its installing without problems!
In settings-> developer options -> OEM unlocking is enabled
can someone give me tips if I'm doing something wrong. thanks
My phone is Blackview BV9000PRO-F

Hello,
i have the blackview 9000 pro Hd (not full hd)
i first tried your prepared patched rom = not working (get erorrers in step 6)
then i chose step 2 and i was thinking to use the stock rom from the NOT full hd rom
now i get a green screen from the flashing: but after rebooting in recovery nothing happens, just normal reboot then
perhaps this is not so clair for me:
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
the file name you posted here " My custom patched TWRP stock rom: recovery-verified.img" is ramdisk-recovery.img
i replaced the ramdisk-recovery.img... it is not clair need to replace recovery-verified.img to?

>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.

>
dingsje said:
Hello,
>i have the blackview 9000 pro Hd (not full hd)
>i first tried your prepared patched rom = not working >(get erorrers in step 6)
>then i chose step 2 and i was thinking to use the stock >rom from the NOT full hd rom
>now i get a green screen from the flashing: but after >rebooting in recovery nothing happens, just normal >reboot then
>perhaps this is not so clair for me:
>- Download the stock rom, backup the recovery->verified.img in the R06 folder, and then replace it with >my custom patched TWRP stock rom (file name should >be the same).
>- Run "CheckSum_Gen.exe" once you replaced the file, >it will generate the necessary checksum to allow SP >flash tools to successfully flash recovery.
>the file name you posted here " My custom patched >TWRP stock rom: recovery-verified.img" is ramdisk->recovery.img
>i replaced the ramdisk-recovery.img... it is not clair >need to replace recovery-verified.img to?
Click to expand...
Click to collapse
Hi,
I've uploaded the wrong file, the uploaded file should be recovery-verified.img.
I'm uploading a new file and will correct the link now,
Please accept my apologies ><

hyperlethalvector92 said:
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
Click to expand...
Click to collapse
I already did this step:
Enable developer options-> OEM unlocking is enabled
Is that enough for this MTK phone to be unlocked the bootloader ?
And tried the both options but the results are same.
I have been unlocking bootloaders on many phones but first time MTK phones. If i try with adb commands it recognize when is in the android with command adb devices and show my device but if I try reboot bootloader and check in device manager in windows its show its connected and drives are correct but if i try to show the devices, it doesn't show any device connected

Hi,
You need to install fastboot drivers once it's in bootloader mode,
then use fastboot, not adb.
"fastboot oem unlock"
Then follow instructions.
simply doing settings -> oem unlock won't unlock the bootloader, it allows you to do so later via. fastboot
Check the original post, I've added the extra instructions sorry about the confusion!

Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers

zlatkomas said:
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
Click to expand...
Click to collapse
I'm glad ^______^
Enjoy your rooted phone

I used this video to root my bv9000 pro hd
much easier than this above, i think it works to on bv9000 pro fhd
https://www.youtube.com/watch?v=c48ISLPjn4Q

Congratulations .... I need a tip,.
And, brother, thank you very much. Worked perfectly.
But first I would like to get you a tip ..
One of the main reasons I have done all this complicated process was to be able to disable the crap of the loud music that plays when the device is started.
I want complete silence at startup.
How do I disable this ****?

Code for Huawei mobile Wi-Fi e5577s-321
Pls help unlock my Huawei mobile Wi-Fi e5577s-321
Imei
860782038163889

TWRP looping after OTA update
My dear, the procedure worked very well, until an OTA update was downloaded.
You are now looping on TWRP. How do I get out of this?
:crying:

help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?

mackie_ma said:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
Click to expand...
Click to collapse
Hi guys, lemme apologize for disappearing, life and whatnot!
For those stuck in a TWRP boot loop, simply restoring the original recovery then restarting the phone will be enough to fix the problem.
(Actually you really don't need TWRP after the phone is rooted, maybe I should update the guide?)

Many Thanks
First off, thank you for your hard work. Loved the "**** it we have an OTG cable let's use it" haha. It works fine for me.
Second, do you happen to know if someone has ported Oreo on our bv9000 ? Or do you know of any ETA ?
Thanks again,
Cheers

Anyone tried on the BV9000 Pro? Don't think mine is 'F' OR 'Fhd'.... I must have first model brought out...

Ugh.. Windows and Drivers?!?!
I keep getting Driver not Recognized in Windows 7 Pro X86.
I installed the latest vcom/usb drivers, in legacy also. No Go.
I installed from several other sources the drivers, including the Automatic Mediatek driver install. No Go.
So if anyone has a tip for me, please let me know because once more Windows is proving itself ridiculous. I can't even get to the storage of my phone. Did something change with a Windows Update that it's not allowed anymore?
I put my BV9000 Pro in OEM Unlock and USB Debugging. I backupped everything. My phone is ready for it. It's as ready as Amy having coitus with Sheldon for the first time.