If you're getting an "unlock check fail" error, take these steps to successfully unlock your bootloader, flash recovery, root, and upgrade back to .29.
Step 1:
Backup anything you want on your tablet using titanium backup (if you're already rooted) or app backup if you prefer. (**These steps will erase EVERYTHING on your tablet**)
Step 2:
Backup the backups onto your computer (again, it will even erase the sdcard partition)
Step 3:
Downgrade to .17 using this method: http://forum.xda-developers.com/showthread.php?t=1645029 (using viperMOD)
Step 4:
Use the "Factory Reset" option under Settings > Backup & Reset (**again, EVERYTHING WILL BE DELETED OFF THE TABLET**)
Step 5:
Once that's done, it should reboot and bring you to the setup screen, you can skip setting up everything and just go straight to the home screen. Now, install the Unlock apk from ASUS and unlock, it should work fine now.
Step 6:
Once that is done, to get back up to .29, follow Step 3 again, but instead of using a .17 blob file, download the .29 update from the ASUS website (http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download), unzip the zip, then unzip the zip that's inside of that and that should have the .29 blob file. Use the same method as Step 3, except with this .29 blob file instead of the .17 blob file.
Step 7:
Once you've confirmed you're back on .29, you can go ahead and flash CWM and root using this method: http://forum.xda-developers.com/showthread.php?t=1668173
And you should be good!
**Note: There seems to be some issue with tablets with the serial number starting with C4OKCT so this may not work for those tablets. Mine starts with C3OKCT so it worked fine. You can verify your serial number from the sticker on the tablet (if you haven't removed it yet) or Settings > About tablet > Status
Berzerker7 said:
If you're getting an "unlock check fail" error, take these steps to successfully unlock your bootloader, flash recovery, root, and upgrade back to .29.
Step 1:
Backup anything you want on your tablet using titanium backup (if you're already rooted) or app backup if you prefer. (**These steps will erase EVERYTHING on your tablet**)
Step 2:
Backup the backups onto your computer (again, it will even erase the sdcard partition)
Step 3:
Downgrade to .17 using this method: http://forum.xda-developers.com/showthread.php?t=1645029 (using viperMOD)
Step 4:
Use the "Factory Reset" option under Settings > Backup & Reset (**again, EVERYTHING WILL BE DELETED OFF THE TABLET**)
Step 5:
Once that's done, it should reboot and bring you to the setup screen, you can skip setting up everything and just go straight to the home screen. Now, install the Unlock apk from ASUS and unlock, it should work fine now.
Step 6:
Once that is done, to get back up to .29, follow Step 3 again, but instead of using a .17 blob file, download the .29 update from the ASUS website (http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download), unzip the zip, then unzip the zip that's inside of that and that should have the .29 blob file. Use the same method as Step 3, except with this .29 blob file instead of the .17 blob file.
Step 7:
Once you've confirmed you're back on .29, you can go ahead and flash CWM and root using this method: http://forum.xda-developers.com/showthread.php?t=1668173
And you should be good!
**Note: There seems to be some issue with tablets with the serial number starting with C4OKCT so this may not work for those tablets. Mine starts with C3OKCT so it worked fine. You can verify your serial number from the sticker on the tablet (if you haven't removed it yet) or Settings > About tablet > Status
Click to expand...
Click to collapse
THANKS MY FRIEND... I was already downloaded (by a wired ASUS OTA from .29 to .17 ) I did the factory reset and got the Unlocker to work.... back to life.
Nice, thanks for typing all that out.
Can't wait to try it out. Thx
Sent from my Galaxy Nexus using Tapatalk
Has anyone with the Serial C4OKC had success with this, or problems?
Berzerker7 said:
If you're getting an "unlock check fail" error, take these steps to successfully unlock your bootloader, flash recovery, root, and upgrade back to .29.
Step 1:
Backup anything you want on your tablet using titanium backup (if you're already rooted) or app backup if you prefer. (**These steps will erase EVERYTHING on your tablet**)
Step 2:
Backup the backups onto your computer (again, it will even erase the sdcard partition)
Step 3:
Downgrade to .17 using this method: http://forum.xda-developers.com/showthread.php?t=1645029 (using viperMOD)
Step 4:
Use the "Factory Reset" option under Settings > Backup & Reset (**again, EVERYTHING WILL BE DELETED OFF THE TABLET**)
Step 5:
Once that's done, it should reboot and bring you to the setup screen, you can skip setting up everything and just go straight to the home screen. Now, install the Unlock apk from ASUS and unlock, it should work fine now.
Step 6:
Once that is done, to get back up to .29, follow Step 3 again, but instead of using a .17 blob file, download the .29 update from the ASUS website (http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download), unzip the zip, then unzip the zip that's inside of that and that should have the .29 blob file. Use the same method as Step 3, except with this .29 blob file instead of the .17 blob file.
Step 7:
Once you've confirmed you're back on .29, you can go ahead and flash CWM and root using this method: http://forum.xda-developers.com/showthread.php?t=1668173
And you should be good!
**Note: There seems to be some issue with tablets with the serial number starting with C4OKCT so this may not work for those tablets. Mine starts with C3OKCT so it worked fine. You can verify your serial number from the sticker on the tablet (if you haven't removed it yet) or Settings > About tablet > Status
Click to expand...
Click to collapse
Not working for me with C4OKCT
danthrax66 said:
Not working for me with C4OKCT
Click to expand...
Click to collapse
Same here. I have had no issues with OTA's or anything else. This is the only issue I have had.
**EDIT** I am on .29, shut down and did a cold boot. Did a wipe data/factory reset. Reinstalled the unlocker and voila success. I am now off to install CWM Recovery. I tried this first and it worked as I didn't want to have to go downgrade and unlock and upgrade again.
Would have been lost without this guide, thank you!
Got a response back from the email tech support... was told to call the service center. IT'S A DATABASE ISSUE JUST ADD MY SERIAL TO THE DATABASE.
Hopefully someone will be able to reverse engineer the unlocker so I don't have to wait for Asus to fix a problem that shouldn't exist.
Worked like a charm on my C4OKCT.
rwa66 said:
Worked like a charm on my C4OKCT.
Click to expand...
Click to collapse
Didn't work for me C4OKCT
not working on mine
i am running .17v us c90kc and getting error for network connectivity. any sugestions since i am already running . 17?
got the same issue with a TF300TG with latest JB software. unlock Tool is always declining with "unknown network error" and "check failed".
This solved it within 5 minutes:
go to asus homepage > add an account > register your product
now the serial number is in the asus DB and the unlock is working like a charm.
got the hint from anddroid-hilfe.de forum.
Hi, I unlocked my TF300TG via the program from Asus website and the tab shows it when it boots.
However, when I boot with Power + Vol down I also don't have the USB icon, only "RCK", "Android" and "Wipe data".
At the top left it said device unlocked. Next, and together with the 3 icons, it says:
"Key driver not found.. Booting OS"
Android cardhu-user bootloader <1.00 e> released by WW_epad-10.6.2.3-20130402"A03
Starting Fastboot USB download protocol
Does this mean it's already in fastboot mode?
If not, how to get this USB icon? I installed the Android SDK and Asus drivers on the computer, reset the tab with factory reset, still no USB icon...
Yes....with this new bootloader when you enter in the bootloader menu you start fastboot
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I'm confused with the .17 and Whatnots and will the work if its on 4.2.2?
philofax said:
got the same issue with a TF300TG with latest JB software. unlock Tool is always declining with "unknown network error" and "check failed".
This solved it within 5 minutes:
go to asus homepage > add an account > register your product
now the serial number is in the asus DB and the unlock is working like a charm.
got the hint from anddroid-hilfe.de forum.
Click to expand...
Click to collapse
you are lucky then, i'm registered for months and the tool doesn't work(v7 ics 4.1, v8 4.2) did you do anything else?
Related
This guide is for you that have a new Xoom (WiFi only, US model) with Android 3.1 and want to
- get root access
- enable the external SD card unit
Please note that Android 3.2, which now is available for the US Wifi models, make this guide more or less obsolete. If your aim is to have root access, then there are probably simpler methods.
What you need to do can be encompassed in these following short steps (will be detailed later on) in the following order. Each step is required before you can proceed to the next one. However, make sure that you are very very careful and dont try to take any shortcuts. That may soft-brick your device, and you may have a difficult time to explain that to your wife ... You have been warned!
I strongly recommend you to read the entire guide before trying this. In fact, read it twice to ensure that you have understood everything. If there is wierd stuff that you dont understand, dont hesitate to ask. The reason for me writing this down is that I like to document what I have learned. This is to me an excellent way to ensure that I will remember what I just did. Another reason was that I could not find a single thread that encompassed all steps required. There are many different threads, but noone (that I could find) that really guides you from start to goal. So enjoy and good luck!
I would like to thank LandMaster and cam30era for helping out with advice during my initial trail-and-error session. I soft-bricked my device once and had big problems to get by point 4.3 (avoid overwriting of CWM), but with their encouragement I finally succeeded.
If someone else adapts this guide for the EU model or the 3G model, feel free to drop me an IM and I will update the guide for these devices too. Until then, this has only been tested on a WiFi only, 32 GB device bought in the US. If you brick your 3G or EU bought model, dont call me ...
0. Overview of the 6 required steps
1. Install Motorola USB drivers for your computers (for USB connectivity)
2. Install Java SDK and Android SDK tools (for adb and fastboot commands)
3. Unlock the device for flashing (allowing replacement of recovery and boot images)
4. Install a modified recovery image (ClockWorkMod recovery for Android)
5. Root the device (Allow r/w access to the device filesystem)
6. Flash a kernel that supports the SD card (SD card access, overclocking etc.)
Steps 1, 2, 4, 5 and 6 require that you download install, image and zip files needed for the flashing.
All this was performed on a Windows XP x86 SP3. Windows 7, Mac and Linux users will probably have to do some steps differently.
Update July 7: I have tested the procedure on Windows 7 x86 now and the procedure is identical to Windows XP.
1. Install the latest Motorola USB drivers
The installation file can be found here
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
1.1 Install the drivers and ensure that your Xoom is recognized by the computer
2. Installation of development software
Java SDK 6 and Android SDK (for Honeycomb at least) need to be installed. You can find the installation kits here.
http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html
http://developer.android.com/sdk/index.html
2.1 Install them as any other software.
2.2 What I had to do was to manually modify the PATH environment variable. I use Windows XP so I did that by right clicking on My Computer, choose Properties and select Advanced. Here I added the path to platform-tools and Tools
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\QuickTime\QTSystem\;D:\Java\Android-sdk\platform-tools;D:\Java\Android-sdk\tools
Note: If the Android SDK complains that the Java Dev Kit cant be found, just press Back and then Next again. Wierd, but that seems to do the trick ... go figure.
2.3 Test that ADB and FASTBOOT works. You should open a command window and go to your Android installation directory. Plug in your Xoom to your computer and write 'adb devices'. Your Xoom should now be listed like this
C:\Documents and Settings\Anders>adb devices
List of devices attached
0288414343813157 device
Did your device not show up? Make sure that you have USB debugging enabled in Settings / Applications / Development
3. Unlocking the device for flashing
This step will effectively erase the internal storage, including all your apps and settings. Use whatever backup you want to rescure important data before you start.
3.1 Power up and start the Xoom
3.2 Ensure that your device is fully recognized by the computer. A good sign is that the 'Portable device' dialog is activated on Windows when your Xoom has booted. The Xoom should also be seen in 'My Computer'. If not, go back to step 2 and double check your USB drivers.
3.3 Use the command 'adb reboot bootloader' to go into Flash mode
3.4 Use the command 'fastboot oem unlock'. This will trigger a dialog on your Xoom. Follow the instructions on the screen to complete the unlocking. I repeat, this *will* do a factory reset and all data will be lost!
3.5 Once unlocked, the Xoom will restart and work as normal, but now ready for step 4
4. Install recovery image (CWM)
Download the recovery image file and save it to your computer
4.1 Boot into flash mode with 'adb reboot bootloader'
4.2 Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
4.3 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.4 Enter CWM with the following procedure
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ...
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. There are ways to prevent this (see posts below), but I recommend you to redo step 4 instead of messing with removal of system files. But both methods would probably work. Experiment!
5. Rooting the Xoom
The root zip file is located here
5.1 You need to transfer the ROOT zip file to a working micro SD card. You can do this on a computer or cell phone, but the ROOT zip must be located in the root directory of the SD card.
5.2 Insert the now prepared SD card in the Xoom
5.3 Boot into recovery (as described in 4.3). Navigate using the volume buttons and press the power button to select the active option
5.4 Select 'Install ZIP from sd card'
5.5 Select 'Choose ZIP'
5.6 Navigate to the ROOT zip file with the Volume buttons and select it with the Power button. Confirm that you want to install it.
5.7 Everything should indicate success, so back out to the main CWM menu and reboot the device.
5.8 From Android Market, install the ROM Manager app and start it. If the rooting was successful, then ROM Manager should start without any complaints.
6. Flashing a new kernel that supports SD cards (and maybe more ...)
The kernel that I used is described here http://forum.xda-developers.com/showthread.php?t=978013
The kernel zip file is located here
6.1 This step is identical to 5, but swap the ROOT zip towards the KERNEL zip. For simplicity, you may want to prepare the SD card with both zip files at the same time in step 5.1 ...
Looks great. You just might want to give credit to LandMaster and cam30era, too.
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
okantomi said:
Looks great. You just might want to give credit to LandMaster and cam30era, too.
Click to expand...
Click to collapse
Of course, done
juDGEY2k10 said:
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
Click to expand...
Click to collapse
This is only tested on a US device. OP updated.
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
When you unlock your Xoom, it will wipe all user data.
bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
You're right. I rooted 1st and flashed CWR later. I then used brd's method to update to 3.1, re-root and flash the new bootloader and kernel. So there is a step missing after Step 3. I'm sorry, I don't remember exactly how to do this from HC 3.1. (meaning what files to use) as I was on HC 3.0 at the time.
BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
Yes it will. Read 3.4 again, it will do factory reset.
The root file may vary from case to case, but the procedure is the same AFAIK. I used the one that "charge light off"... There are probably others too.
bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
This is true, and I will update the OP to reflect that.
So has anyone followed this guide successfully yet? I don't really want to be the first...
yordikins said:
So has anyone followed this guide successfully yet? I don't really want to be the first...
Click to expand...
Click to collapse
Hi
I did!. And you know that someone gotta be first (actually second). Why not take the credit?
pingvinen said:
This is true, and I will update the OP to reflect that.
Click to expand...
Click to collapse
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App
Abracastabya said:
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
cam30era said:
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
Click to expand...
Click to collapse
Sounds good and thanks B-)
Sent from my Xoom using XDA Premium App
Tnx . Very help full .
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).
rmcsc said:
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).
Click to expand...
Click to collapse
Try again, and remember that timing (3 seconds) are key to success ...
I'll retry being more precise. I do get into Recovery and I flash the file mentioned. It seems it flashes correctly but when I boot into the OS, there's no signs of root anywhere.
I'll update in a few. Thanks!
Sent from my T-Mobile G2 using Tapatalk
Dear Sir,
I have followed all the steps but still not rooted my htc desire 820 dual sim
http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064..............this link I have followed.....
but didn't sucess.......
plz....help...Sir
HTC Desire 820 can be easily rooted with few simple steps.
I am not responsible for your warranty loss or device not functioning properly.
Steps
1] Unlock Bootloader if you don't know how to do it visit this page
2] Download TWRP Recovery from here
3] Download Super Su from Here and transfer it to your device
4] Reboot to Fastbboot mode using Volume Down and Power Key
5] Connect Phone to PC
6] Extract files from Recovery.zip in one location and simply click on flash-recovery.bat
7] After Step 6 is finished Using volume keys navigate and select recovery option and go to recovery
8] After rebooting in recovery select Install zip > and selecting supersu.zip transferred in first step to obtain root access.
9] Reboot
Very much urgent.......plz. reply...........
subinoy.bose said:
Dear Sir,
I have followed all the steps but still not rooted my htc desire 820 dual sim
http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064..............this link I have followed.....
but didn't sucess.......
plz....help...Sir
HTC Desire 820 can be easily rooted with few simple steps.
I am not responsible for your warranty loss or device not functioning properly.
Steps
1] Unlock Bootloader if you don't know how to do it visit this page
2] Download TWRP Recovery from here
3] Download Super Su from Here and transfer it to your device
4] Reboot to Fastbboot mode using Volume Down and Power Key
5] Connect Phone to PC
6] Extract files from Recovery.zip in one location and simply click on flash-recovery.bat
7] After Step 6 is finished Using volume keys navigate and select recovery option and go to recovery
8] After rebooting in recovery select Install zip > and selecting supersu.zip transferred in first step to obtain root access.
9] Reboot
Very much urgent.......plz. reply...........
Click to expand...
Click to collapse
Try thishttp://forum.xda-developers.com/attachment.php?attachmentid=2784451&d=1402084843
Please let us know what is the exact message your getting are you not able to get to Recovery ???
I have been able to successfully root my device by following the steps outlined did not face any challenges hence wanted to check.
Same Probleam here pls help me
I AM SUFFERING FROM SAME PROBLEAM.
i am using desire 820q.
bootloader unlocked.
but when i enter in recovery then that says entering recovery then come back.
pls help me...
problem with htc 820q root
mukulatri said:
Try thishttp://forum.xda-developers.com/attachment.php?attachmentid=2784451&d=1402084843
Click to expand...
Click to collapse
I'm following this instruction and could not root my device,
My HTC 820q is unlock but when I want read SuperU.zip from Sd card at fastboot>recovery my mobile goes to restart and procedures been uncompleted.
Please help me, is this instruction only for HTC 820?
How we can root HTC 820q?
tah3r said:
I'm following this instruction and could not root my device,
My HTC 820q is unlock but when I want read SuperU.zip from Sd card at fastboot>recovery my mobile goes to restart and procedures been uncompleted.
Please help me, is this instruction only for HTC 820?
How we can root HTC 820q?
Click to expand...
Click to collapse
http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064
mukulatri said:
Try thishttp://forum.xda-developers.com/attachment.php?attachmentid=2784451&d=1402084843
Click to expand...
Click to collapse
Well I have the same issue, recovery looks installed after pressing power button to launch it goes to a screen and go back almost instantly on fastboot screen. I also tried last version of framaroot, does not help either... just get a failed message
尚雷諾 said:
Well I have the same issue, recovery looks installed after pressing power button to launch it goes to a screen and go back almost instantly on fastboot screen. I also tried last version of framaroot, does not help either... just get a failed message
Click to expand...
Click to collapse
Hi there, let's go step by step without "shortcuts" that are typically working on PC/WIn.
1. Unlock bootloader of your phone at HTCdev[dot]com [replace 'dot' with . - sorry for confusion I haven't earned reputation to post external links yet]. All necessary tools (fastboot) will be provided to download during process as well as necessary instructions. You need Windows/Linux or OS X computer to complete this step.
2. Download custom recovery .img file and save it to same directory you have fastboot files (e.g. from step 1) on you computer
3. Start phone in fastboot mode (mind fast boot option in Power settings must be unchecked if you using VolDown [-] start option (not necessary if you use adb reboot bootloader). Battery must be charged over 10% (I suggest 30% to stay secure); connect to computer (phone shall display Fastboot USB)
4. Navigate command/terminal window on your computer to location of recovery image file from step 2 (fastboot files must be there or have a correct path specified).
5. On computer terminal window run command: fastboot flash recovery filename_of_recovery.img . Red section must be exact custom recovery file name.
6. You'll get some communication in terminal. If completed OK will be among them, if failure, there will be FAIL with description of reason (e.g. low_power). If only "waitng for device" dislays, check connection with phone.
7. Navigate phone to HBOOT, then select recovery. If recovery don't start, check step 1 and restart from step 3. If only icon with red ! appears, it means you have stock recovery installed. Please verify from step 1.
8. Once custom recovery is installed and working, use it to flash SuperSU or any other superuser app (must be flashable .zip to be applied). Install just 1 root application, to avoid problems. At this point, you may consider flashing busybox also if you plan extensive file modification, but it's not necessary for root. For any sake, clear cache befor restart.
9. Restart the phone - you shall view SuperSU application or any other superuses app you've flashed i step 8.
Hope now works.
T0ark said:
Hi there, let's go step by step without "shortcuts" that are typically working on PC/WIn.
1. Unlock bootloader of your phone at HTCdev[dot]com [replace 'dot' with . - sorry for confusion I haven't earned reputation to post external links yet]. All necessary tools (fastboot) will be provided to download during process as well as necessary instructions. You need Windows/Linux or OS X computer to complete this step.
2. Download custom recovery .img file and save it to same directory you have fastboot files (e.g. from step 1) on you computer
3. Start phone in fastboot mode (mind fast boot option in Power settings must be unchecked if you using VolDown [-] start option (not necessary if you use adb reboot bootloader). Battery must be charged over 10% (I suggest 30% to stay secure); connect to computer (phone shall display Fastboot USB)
4. Navigate command/terminal window on your computer to location of recovery image file from step 2 (fastboot files must be there or have a correct path specified).
5. On computer terminal window run command: fastboot flash recovery filename_of_recovery.img . Red section must be exact custom recovery file name.
6. You'll get some communication in terminal. If completed OK will be among them, if failure, there will be FAIL with description of reason (e.g. low_power). If only "waitng for device" dislays, check connection with phone.
7. Navigate phone to HBOOT, then select recovery. If recovery don't start, check step 1 and restart from step 3. If only icon with red ! appears, it means you have stock recovery installed. Please verify from step 1.
8. Once custom recovery is installed and working, use it to flash SuperSU or any other superuser app (must be flashable .zip to be applied). Install just 1 root application, to avoid problems. At this point, you may consider flashing busybox also if you plan extensive file modification, but it's not necessary for root. For any sake, clear cache befor restart.
9. Restart the phone - you shall view SuperSU application or any other superuses app you've flashed i step 8.
Hope now works.
Click to expand...
Click to collapse
Thanks for your answer, I have to say I properly unlocked the phone so I do not think there is a way I messed up with this step as when I start bootloader it clearly shows on the top of the screen ''UNLOCKED".
When I flashed recovery on my phone I had no errors prompted or any message of failure. The process went well until a success notification.
Now when I start my phone into bootloader I repeat, I clearly see that recovery has been installed but when I attempt to start it then I'll be almost instantly brought back to the bootloader screen... now I started to wonder if... if an update of android could cause this kind of issue? The point is my phone is using android 4.4.4 and not the factory version 4.4.2. I remember having updated my android version which was perhaps a mistake as this phone is not very old and I was planning to root it in the next days... Now I'm not expert just try to figure it out.
I tried different system to auto root via different apps, some using the PC some using directly the phone, I never get any success...
尚雷諾 said:
Thanks for your answer, I have to say I properly unlocked the phone so I do not think there is a way I messed up with this step as when I start bootloader it clearly shows on the top of the screen ''UNLOCKED".
When I flashed recovery on my phone I had no errors prompted or any message of failure. The process went well until a success notification.
Now when I start my phone into bootloader I repeat, I clearly see that recovery has been installed but when I attempt to start it then I'll be almost instantly brought back to the bootloader screen... now I started to wonder if... if an update of android could cause this kind of issue? The point is my phone is using android 4.4.4 and not the factory version 4.4.2. I remember having updated my android version which was perhaps a mistake as this phone is not very old and I was planning to root it in the next days... Now I'm not expert just try to figure it out.
I tried different system to auto root via different apps, some using the PC some using directly the phone, I never get any success...
Click to expand...
Click to collapse
Ok, please try twrp from Original Android Development tread (it works for me, mind, I'd question it's stability) or Philz recovery (sorry, I found only Chinese, but it's for verivication only: h...ps://drive.google.com/file/d/0BygOvRquk4z8S05kRC1XMXdSbXM/view?usp=sharing - please adjust tt in address - rookie rules).
I'd suggest test running from Fastboot: fastboot boot custom_recovery.img - replace with actual file name from directory you're running terminal.
This shall verify if it's problem with recovery file or any remaining protection...
T0ark said:
Ok, please try twrp from Original Android Development tread (it works for me, mind, I'd question it's stability) or Philz recovery (sorry, I found only Chinese, but it's for verivication only: h...ps://drive.google.com/file/d/0BygOvRquk4z8S05kRC1XMXdSbXM/view?usp=sharing - please adjust tt in address - rookie rules).
I'd suggest test running from Fastboot: fastboot boot custom_recovery.img - replace with actual file name from directory you're running terminal.
This shall verify if it's problem with recovery file or any remaining protection...
Click to expand...
Click to collapse
Does having S-ON bother? I was also wondering about that but all tutorials I found no one mentions anything about the S-ON or S-OFF thing.
But I do have a S-ON under UNLOCKED
what is stock recovery.img name
i dont know what is the real stock recovery.img name.
htc desire 820q dualsim
I can't root my htc desire 820q by this method, is any alternative way?
I just root my phone with same procedure but my phone still show s-on..... How can i s-off my phone.....
Hey guys,
I'm in the process of flashing CM's Marshmallow onto my LG G3s (D722) however after successfully rooting using KingRoot I can't seem to be able to apply the necessary bootloader patch as the /dev/block folders and contents are completely missing. Anyone have any suggestions? I installed a kdz lollipop stock room to begin the process if it helps.
heyy
you can you help me?
I have the CM13 but the root was not well and using the kingroot but is dont working .
as you did with the kingroot ?
sorry for the inconvenient
Hey,
I flashed a stock ROM (make sure you download the right one for your model/IMEI) via LG Flash Tool and then used Kingroot, be sure you haven't downloaded KingoRoot by mistake, it's not the same app as it just installs a heap of apps on your phone and does nothing but tell you it's failed after.
I'm still stuck with the bootloader patch though :s
There is a thread with all the info about this phone, tells you the right way to patch boot
Hi,
I figured out what the problem was, the thread you mention doesn't cater for my specific issue. Which I had hoped for a response about, however incase others have this same issue I'll list the process I went through here to resolve my issue and correctly root, patch and flash the D722;
1: Install Kingroot on your phone with your data connection active and let it try to root your phone, if it fails proceed to the next steps. Otherwise skip to step 3
THINGS TO DOWNLOAD: (If initial root attempt fails)
Download & install LG Flash tool on your PC.
Download & install Unified Android Toolkit (Optional, but useful for mass installation of aps)
Search for the correct KDZ file for your phone model/IMEI HERE
Install Busybox on your phone
Install Flashify on your phone
2: With your phone in download mode Flash your downloaded ROM using the LG Flash tool in CSE mode and click start, ignore language settings and any error messages. It should proceed as normal.
3: Follow the instructions for patching the bootloader HERE. If it fails proceed to step 4.
NOTE: The root location of your external SD card may be in a different directory, for example like mine it was in /storage/external_SD/ so try to change the file location in the command before proceeding.
4: Download and install CWM ROM Manager on your device (use Unified Android Toolkit to do this if you don't have/want gapps). Then choose fix permissions and repeat step 3.
5: Flash twrp via Flashify.
6: Download your desired ROM and place it in the root of your SD card, reboot to recovery.
7: Install the ROM as usual via TWRP, remember to wipe dalvic etc.
If mods would like me to post this as a guide instead I'll gladly do so!
NarcissusFarie said:
Hi,
I figured out what the problem was, the thread you mention doesn't cater for my specific issue. Which I had hoped for a response about, however incase others have this same issue I'll list the process I went through here to resolve my issue and correctly root, patch and flash the D722;
1: Install Kingroot on your phone with your data connection active and let it try to root your phone, if it fails proceed to the next steps. Otherwise skip to step 3
THINGS TO DOWNLOAD: (If initial root attempt fails)
Download & install LG Flash tool on your PC.
Download & install Unified Android Toolkit (Optional, but useful for mass installation of aps)
Search for the correct KDZ file for your phone model/IMEI HERE
Install Busybox on your phone
Install Flashify on your phone
2: With your phone in download mode Flash your downloaded ROM using the LG Flash tool in CSE mode and click start, ignore language settings and any error messages. It should proceed as normal.
3: Follow the instructions for patching the bootloader HERE. If it fails proceed to step 4.
NOTE: The root location of your external SD card may be in a different directory, for example like mine it was in /storage/external_SD/ so try to change the file location in the command before proceeding.
4: Download and install CWM ROM Manager on your device (use Unified Android Toolkit to do this if you don't have/want gapps). Then choose fix permissions and repeat step 3.
5: Flash twrp via Flashify.
6: Download your desired ROM and place it in the root of your SD card, reboot to recovery.
7: Install the ROM as usual via TWRP, remember to wipe dalvic etc.
If mods would like me to post this as a guide instead I'll gladly do so!
Click to expand...
Click to collapse
help me please. i cant patch bootloader says sdcard/aboot.bin: no such file or directory, i have the file on internal and external memory... please help.....
feikacab said:
help me please. i cant patch bootloader says sdcard/aboot.bin: no such file or directory, i have the file on internal and external memory... please help.....
Click to expand...
Click to collapse
Some versions have another path.
Sent from my D722P using XDA-Developers mobile app
ErnuB said:
Some versions have another path.
Sent from my D722P using XDA-Developers mobile app
Click to expand...
Click to collapse
yes. works fine. thanks dude.
Could you tell me the path I should use? or the full code I should write?
NarcissusFarie said:
Hi,
I figured out what the problem was, the thread you mention doesn't cater for my specific issue. Which I had hoped for a response about, however incase others have this same issue I'll list the process I went through here to resolve my issue and correctly root, patch and flash the D722;
1: Install Kingroot on your phone with your data connection active and let it try to root your phone, if it fails proceed to the next steps. Otherwise skip to step 3
THINGS TO DOWNLOAD: (If initial root attempt fails)
Download & install LG Flash tool on your PC.
Download & install Unified Android Toolkit (Optional, but useful for mass installation of aps)
Search for the correct KDZ file for your phone model/IMEI HERE
Install Busybox on your phone
Install Flashify on your phone
2: With your phone in download mode Flash your downloaded ROM using the LG Flash tool in CSE mode and click start, ignore language settings and any error messages. It should proceed as normal.
3: Follow the instructions for patching the bootloader HERE. If it fails proceed to step 4.
NOTE: The root location of your external SD card may be in a different directory, for example like mine it was in /storage/external_SD/ so try to change the file location in the command before proceeding.
4: Download and install CWM ROM Manager on your device (use Unified Android Toolkit to do this if you don't have/want gapps). Then choose fix permissions and repeat step 3.
5: Flash twrp via Flashify.
6: Download your desired ROM and place it in the root of your SD card, reboot to recovery.
7: Install the ROM as usual via TWRP, remember to wipe dalvic etc.
If mods would like me to post this as a guide instead I'll gladly do so!
Click to expand...
Click to collapse
Is this guide still works or will you update instructions? also where can I download TWRP and LineageOS for LG G3s D722?
A small update 136mb or so for the L03 devices, is there someone who can convert this update to a twrp friendly zip flash update? Would appreciate any help, thanks.
Do you still have this OTA file somewhere? If so can you setup a link to download it?
I think I have figured this one out
Nicolfa said:
Do you still have this OTA file somewhere? If so can you setup a link to download it?
Click to expand...
Click to collapse
It seems like we are the only 3 people who seems to be working on this phone and this update.
So I have 2 developments:
First, I pulled the stock 136.3 mb "update.zip" file of this update and have uploaded to the following:
https://mega.nz/#!rppjnLSY!djq4xpEiiH-lLircX9DZDlIkWu0_OMSG0SYTyKaelMY
Second, I manage to successfully update to this version through trial and error by doing the following:
0. I flashed stock recovery back into my phone through Flashify and update. This didn't work.
1. I then tried updating by "unrooting" SuperSu after above step. This didn't work.
2. I followed up the above step #1 by "relocking" my bootloader through ADB. Relocking was a success but update failed. It downloads and then as it installs/reboots, once it reaches ~26%, it will say installation failed.
3. Finally, I performed a "Local Update" in the EMUI menu by dirty flashing stock RIO-L03_C567B141CUSTC567D002_Android 5.1_EMUI 3.1_United States over the version that is already on my phone by the "dload - update.app" method through my external SD card. (create folder "dload" in ext SD card and place "update.app" in the folder).
4. After completing step #3, I went back to "Settings - Updater" and tapped "Check for updates", followed the prompts and the phone successfully updated. Verified again that there are no further updates.
The phone now reads:
Build number RIO-L03C567B160
Android security patch level: April 1, 2016
Android version: 5.1
Baseband version: 20234
Custom Version: CUSTC567D002
I have T-Mobile and no issue with reception. I am going back to unlocking bootloader, root, and debloat the junkwares
I know there is a MM version (HUAWEI_G8_Firmware_RIO-L03_Android 6.0.1_EMUI 4.0_C469B330_Latin America_Channel-Others_Dual SIM). I am NOT going to flash this at this time. Also I don't like EMUI 4. I have Honor 5x also and after MM update, EMUI 4 removed the "Local update" option which takes away the ability to "sideload" updates via the "dload - update.app" method.
Encrypted download password needed
spunky168 said:
I know there is a MM version (HUAWEI_G8_Firmware_RIO-L03_Android 6.0.1_EMUI 4.0_C469B330_Latin America_Channel-Others_Dual SIM). I am NOT going to flash this at this time. Also I don't like EMUI 4. I have Honor 5x also and after MM update, EMUI 4 removed the "Local update" option which takes away the ability to "sideload" updates via the "dload - update.app" method.
Click to expand...
Click to collapse
a solution for this is:
dial *#*#2846579#*#* with the phone app and you will get a service menu
(first picture) where you can select software upgrade and than
(second picture) load an update vom the dload-folder from your sd-card
THANK YOU!!!
firithmorgulion said:
a solution for this is:
dial *#*#2846579#*#* with the phone app and you will get a service menu
(first picture) where you can select software upgrade and than
(second picture) load an update vom the dload-folder from your sd-card
Click to expand...
Click to collapse
THANK YOU SO MUCH firithmorgulion!!!!! This is so awesome and helpful. The rest of the service menu also provides lots of useful information about my phone also.
spunky168 said:
THANK YOU SO MUCH firithmorgulion!!!!! This is so awesome and helpful. The rest of the service menu also provides lots of useful information about my phone also.
Click to expand...
Click to collapse
On G8 I have also the option to go to settings -> update program -> hit the menu key (middle of bottom) -> Local update and now I can select from the updates that where found.
In my case even force update fails. My mobile tells RIO-L01C150B130CUSTAUTC150D004 (T-Mobile Austria) and it want's to OTA update right away to B331 of that version.
In many places I read that it is necessary to update in smaller junks (eg. B130-->B160 first or maybe even B130->B140->B160). Maybe noone told Huawei.
Not only OTA is failing. All dload attempts are failing, too. Even if bootloader is re-locked.
Btw. I can provide G8 OTA update file for RIO-L01C150B331CUSTAUTC150D004 (Marshmallow T-Mobile Austria) if someone needs. I could not manage to create some images out of it, yet. I didn't try hard, though .
On my phone cust- and modem partitions are not accessible with fastboot. I assume they are mounted as read only to prevent removal of branding (I unlocked the bootloader before I tried).
I'll have a look if I can access the cust / modem partitions with TWRP today. I would like to go from C150 to C432.
There are some things that I don't understand yet.
1) I can wipe all partitions with TWRP that ist finds (including cust partition). I'm not sure if it has any effect. I can select remove data in TWRP. In any case it seems cust and modem partition content stays completely untouched. -> I have not found a way to make a complete wipe aka a super clean install.
2) I flash boot.img, recovery.img and system.img from B160 but the mobile keeps telling it has B130. Beside that, the phone runs fine.
Chilli
Updated link
Nicolfa said:
Encrypted download password needed
Click to expand...
Click to collapse
Here is the updated link: https://mega.nz/#!rppjnLSY!djq4xpEiiH-lLircX9DZDlIkWu0_OMSG0SYTyKaelMY
Is compatible with my RIO-L03c469B330?
Thanks
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.