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.
Related
U9200 AIO guide
This guide is made by me, but I've collected information from many others.
Special thanks to: arkedk, Urmet77, lee140685, faust93, spanorg, kiprap and others.
First of all:
1. I am not responsible for ANY bricked device! You are doing this at your own risk.
2. Downloads are located here. Most of my uploads are heavily compressed by 7zip. Only 7zip will unzip correctly.
3. Install ADB and FASTBOOT drivers for making stuff in this guide work. Very easily done with: 15 seconds ADB Installer by Snoop05 @ xda
Eventually: Android SDK | Guide by demkantor | Guide by TeamAndroid
4. Backup stuff you want to keep. Easy with tools such as: MyPhoneExplorer, Super Backup, Titanium Backup or others. (Use Google)
5. Other things you should know:
→ Reboot phone to recovery: Turn on while holding volume up + volume down. Or through ADB: "adb reboot recovery"
→ Reboot phone to fastboot: Turn on while holding volume down. Huawei logo will appear and won't disappear. Or through ADB: "adb reboot-bootloader"
→ Shut down phone if it freezes: Hold power button until dead.
→ For ADB to work, debug mode must be enabled, and you must choose "Hi suite" as USB connection mode.
→ Some Huawei ICS ROM's comes without the FM radio app. If you want it, you can install this apk. NB: ONLY ICS (Android 4.0.X). For JB: B704 was the first version to include FM radio.
Here is "ascend-p1" forum category on xda: https://forum.xda-developers.com/t/ascend-p1
Gain root access (Works on ANY Huawei stock firmware. Inspiration taken from arkedk's thread)
TWRP has the ability to root our device, regardless of firmware version!
1. Download TWRP v2.6.3.0 (img). Unzip it, and place the .IMG in "C:\Program Files (x86)\Android\android-sdk\platform-tools" folder.
2. Turn off your phone. Restart it while holding volume down (Fastboot mode). Connect your phone via USB. (ADB: adb reboot-bootloader)
3. In the "C:\Program Files (x86)\Android\android-sdk\platform-tools"-folder, hold shift while right click. Choose "open command window here".
5. Write "fastboot devices" to verify that the computer detects your device. If not detected, you failed install Fastboot drivers. (Look at the top of this guide)
6. Write "fastboot flash recovery recovery.img". This will flash/ install TWRP to your device. (Given that your recovery file is named recovery.img)
7. Boot into your new recovery, TWRP. (Volume + and - together at startup)
→ Go to the "Mount" menu and mount System.
→ Then go to the Reboot menu and reboot the system.
→ When it detects you are not rooted, TWRP will ask if you want to root.
→ Swipe to do so and let it boot back into the system.
8. Hit the SuperSU icon and let it setup for the first time. Either by downloading a flashable zip or by going to the Play Store. Both methods works.
9. You should now be rooted!
Install/flash stock or custom recovery. (Root not required.)
1. Download the recovery you want. Place the .IMG file in "C:\Program Files (x86)\Android\android-sdk\platform-tools"
2. Turn off your phone. Restart it while holding volume down (Fastboot mode). Connect your phone via USB
3. In the "C:\Program Files (x86)\Android\android-sdk\platform-tools" folder, hold shift while right click. Choose "open command window here".
4. Write "fastboot devices" to verify that the computer detects your device. If not detected, you failed install Fastboot drivers. (Look at the top of this guide)
5. Write "fastboot flash recovery <recovery_name>.img".
→ Let's say the recovery file is named twrp.img. Then you will type: "fastboot flash recovery twrp.img"
6. If unsuccessful, try again, be very careful about typing it right. If successful, write "fastboot reboot" to reboot your phone. You are done.
Install any Huawei stock firmware, regardless of version (even from custom ROM)
- This will delete everything on your phone's internal memory, and you will loose root.
- The easiest way is by first flashing Intermediate Pack (B123). This is a stock Huawei ROM that will flash regardless of previous firmware version. Any Huawei ROM then will flash straight from Intermediate Pack. No build.prop modifications needed!
- Chinese versions don't have GAPPS installed. This must be installed through a custom recovery after flashing the firmware.
1. Grab "Intermediate Pack", desired firmware version, intermediate FashPack. Links in bottom of this guide.
2. Take the RECOVERY.IMG out of intermediate FlashPack, and Install it through the steps above. (fastboot flash recovery recovery.img)
3. Place "Intermediate Pack" UPDATE.APP on your SD-card. The file structure MUST be: (Root of SD-card) dload\UPDATE.APP
4. Boot into recovery (Volume up+down when powering on the device). This should start flashing procedure of B123, Intermediate Pack. If it doesn't work and you come from a custom ROM, you must change build.prop to the one included in Intermediate Pack FlashPack. See "FAQ" on how to replace build.prop.
5. After install, it will boot. Now switch the UPDATE.APP from Intermediate Pack with the one from desired firmware version. ((Root of SD-card) dload\UPDATE.APP)
6. Boot to recovery. The firmware flashing procedure will start.
Chinese version extra instructions. This is the time to install GAPPS! B704 extra instructions! arkedk has made a zip to enable all languages in B704. Grab Enable all languages in B704, by arkedk
→ FIRST boot the phone after the firmware installation has succeed.
→ Grab GAPPS corresponding to your android version. (I recommend miuiandroid.com's GAPPS lite, as they removed all unuseful stuff) Place the .zip on the sd-card. Place language enabler.zip on the sd-card as well
→ Install a TWRP v2.4.4.0 recovery
→ Boot into recovery. Install GAPPS.zip. Install language enabler .zip as well
→ Reboot. TWRP will ask you if you want ROOT access. Entirely up to you! For the language enabler to work, you must do a device reset. Relax, GAPPS should be there after the reset.
7. Done! If you want root access, check root guide on top. You can remove Chinese system apps with Uninstall Master. Weather, baidu, and Chinese market won't work outside china anyway. REQUIRES ROOT!
OLD METHOD
Install any Huawei stock firmware, regardless of version (even from custom rom) B229 is a bit different. See "FAQ" at bottom.
This will delete everything on your phone's internal memory, and you will loose root.
Your phone must be rooted for this method to work (replacing/modifying build.prop. Check FAQ about build.prop if you have any questions)
1. Grab firmware (UPDATE.APP), recovery.img and build.prop (Both included in attached FlashPacks) for desired firmware version. Links in buttom of this guide.
2. Place UPDATE.APP on your SD-card. The file structure MUST be: (Root of SD-card) dload\UPDATE.APP
3. Install recovery through the steps above.
4. Download and open "Universal Android AIO Flasher Tool$" to replace build.prop:
→ A: Open desired build.prop in notepad, notepad++ or similar. Copy everything.
→ B: Connect phone in ADB mode (See "First of all" ↑ ).
→ C: Open "Universal Android AIO Flasher Tool$". Go to "Build.prop Editor"-tab
→ D: Insert what you copied into the empty text field.
→ E: Click the "save" button and then "Flash to device". You must grant access with SuperSU (or whatever superuser access management tool) on your phone.
→ F: If successful, you must click "Reboot device" for the changes to take effect. Let the phone reboot.
Manually: "adb pull /system/build.prop" to get the build.prop from your phone.. "adb push build.prop /system/build.prop" to push build.prop to device. "adb reboot" to reboot it (Must be done)
5. After reboot, check "Settings -> About" to check if stated firmware version has been changed to the one you want.
6. Turn off your phone. Restart while pressing volume up + volume down. The firmware flashing procedure will start. If not, you have done something wrong.
7. Done.
Install custom firmwares/ROMs (Root not required)
- This will delete everything on your phone's internal memory. Backup stuff you want to keep.
- All custom ROMs i know is pre-rooted, so nothing to worry about there!
- You will need custom recovery for this to work. Look above.
Depending on firmware, GAPPS (Google Apps) might not be included and must be flashed afterwards if it's wanted. I recommend miuiandroid.com's GAPPS lite, as they removed all unuseful stuff
1. Download desired 3rd-party firmware, it must be a CWM/TWRP flashable .zip. Place it on you memory card. If you're flashing GAPPS aswell, place gapps.zip on the memory card too.
2. Reboot you phone to recovery.
3. Wipe everything the custom firmware needs to have wiped. Generally cache, dalvik and user data.
4. Flash the firmware .zip. Wait for everything to finish!
6. Restart the phone. It will use alot of time the first time. If it uses more than, let's say.. 7 minutes, something is wrong (bootloop).
You can eventually try these steps:
→ Wipe cache, dalvik and userdata with CWM.
→ If this does not solve the problem, check the files and reflash. If it still bootloops: The files don't work with U9200.
If you are going to flash GAPPS, now after the first boot is the time to do it. Boot into recovery, then flash the GAPPS .zip corresponding to your firmware version.
7. Restart and enjoy!
"Ey, Olav! Do you know any other useful stuff I can do to my rooted phone?"
These settings can be edited by using the app Root Browser, for instance.
Boost GPS performance by changing default server to the respective one for your country. Should make the GPS faster and more precise.
The file holding this information is located in: /system/etc/gps.conf
Find respective gps server (NTP) here: http://www.pool.ntp.org/zone/@
I'm from Norway. My customized gps.cfg looks like this:
Code:
NTP_SERVER=no.pool.ntp.org
XTRA_SERVER_1=http://gllto.glpals.com/4day/glo/v2/latest/lto2.dat
XTRA_SERVER_2=http://gllto.glpals.com/4day/glo/v2/latest/lto2.dat
XTRA_SERVER_3=http://gllto.glpals.com/4day/glo/v2/latest/lto2.dat
# SUPL_HOST=supl.google.com
# SUPL_PORT=7276
Fix GPS log bug found in some Huawei ROMs. There seem to be a bug, where stock Huawei ROMs will create huge unnecessary GPS logs, that eventually will fill your entire SD card with trash! (We are talking several 100 MB's of logs!).
Disable log keeping by editing a setting in this file: /system/etc/gpsconfig.xml.
Edit: "cLogEnabled" from "true" to "false". Then delete all the logs in: system/data/gps/log.
FAQ
Install latest baseband version
Why? Baseband / radio.img is the software controlling everything that has to do with signal. Newer baseband versions can boost your performance + make battery last longer. It might make things worse, but generally newer means better.
How? There is no way to extract radio.img from Huawei firmware at this point. So only way to do this is through flashing a stock firmware from Huawei containing the baseband (radio.img) version you want. (New firmware sometimes includes updated baseband version). If you want custom firmware/ROMs you can flash them over it, baseband version will remain/ radio.img/baseband is not included in custom firmwares/ROMs. Flashing any Huawei firmware will replace baseband with its own version.
For flashing procedure, see "Install any Huawei stock firmware, regardless of version you are on (even from custom rom)"
GAPPS
Why? You want Google applications, but it's not included in the ROM you've flashed.
Which? GAPPS is made for every android version (ICS=4.0.x, JB=4.1.x/4.2.x). Make sure you pick the right one! (Links in download section). I recommend OpenGapps Pico. Heavier GAPPS will make your device much slower.
How?
- Download GAPPS.zip, move it to your memory card.
- Use custom recovery such as CWM or TWRP to flash it.
Remember:
- Has to be done after the ROM is flashed (obviously) and it's recommended to boot the ROM once before flashing GAPPS.
- All Huawei stock firmwares (Except Chinese versions) have this preinstalled.
What does "Root"/"Root access" mean?
- System files is not editable on stock firmware. Editing these can potentially make your phone into a brick. To remove these restrictions follow the steps in my guide.
- Rooting will in most cases destroy warranty!
- MIUI, CM and other custom ROMs are pre-rooted[/I]
What is build.prop?
- This is a text file stored on your phone, which tells the phone about what firmware version it has + some other stuff.
Why replace build.prop?
Build.prop stores lots of settings and info about your phone. Changing it is most commonly used for tricking the upgrade procedure to think the firmware on the phone is compatible with the update.
- Huawei firmware updates is restricted to some few firmware versions. But they have made a "Intermediate Pack" which will flash from ANY stock huawei ROM. All huawei ROM's will flash from this intermediate pack without the need of changing build.prop. Think of "Intermediate Pack" as a intermediary for getting the firmware version you want.
- If you come from a custom ROM, and intermediate pack won't flash (verification fail in recovery), you must change build.prop to any stock huawei build.prop for it to work.
How to replace build.prop?
Phone must be rooted!
NB: There's a chance your custom ROM won't boot because of using stock Huawei build.prop with it. In case of updating to Huawei stock firmware, be smart. Flash stock recovery, and add the update.app to SD card BEFORE you change build.prop!
- Get desired build.prop (included in my "FlashPack" files.
- Download Universal Android AIO Flasher Tool$, by "fonehacker".
- Plug your phone in ADB mode. Open the tool above. Go to build.prop tab. Open your recovery. Press save. Then flash it to your device.
- Device must restart for the changes to work. The tool will ask you about this, and you press YES.
(Alternative: Take a custom rom zip (LineageOS for instance), open zip without unzipping (Use 7-zip), delete all the folders in the /system, including build.prop. Drag desired build.prop to /system folder. Flash this file from a custom recovery, such as CWM or TWRP. No root needed.)
What is boot.img for?
- It's a file that get flashed to your boot partition on the phone. This file is managing the booting process of your phone. This file is included in all ROM's, therefore there is no need for manual flashing. If the boot partition get's damaged in any way, flashing a boot.img made for the same firmware can fix it. Don't try boot.img from different firmwares/android version!
Why is boot.img included in your FlashPacks?
- ROM developers might use it for developing new and better roms. If you just are updating your phone, you will have no use for it.
What is EmUI?
- Huawei is making a custom version of android for their phones. This project is named Emotion UI, EmUI in short.
What is latest firmware(s) for my U9200?
- The download section always contains latest version of Huawei firmware. If there is a new version I have not listed, tell me
What's the difference of "boot recovery" and "flash recovery"?
Boot recovery will make your phone boot from the recovery file stored on your computer (Through fastboot, your phone is connected with usb)
Flash recovery will replace what ever recovery you already have on your phone.
Can I remove/change battery?
- It's not meant to be possible as there is no plastic cover you can remove without disassemble the phone. There is a small bolt underneath the SD-card cover. I think that's the place to start if you want to open it. This will most certainly break the warranty. If the phone's hardware misbehave in any way you should contact Huawei or the store you bought it from.
Guides:
→ How to split Huawei firmwares (get boot.img and recovery.img for a given Huawei firmware): http://madmodder.co.uk/huawei_gener...recovery-images-from-most-huawei-firmware.htm
→ How to root and install custom ROM and recovery, by lee140685: https://forum.xda-developers.com/showpost.php?p=33621360&postcount=310
→ Firmwares with flashing guide, by arkedk: https://forum.xda-developers.com/showthread.php?t=2075028
→ How to setup and use fastboot, by demkantor (Absolutely noob proof): https://forum.xda-developers.com/showthread.php?t=2277112
→ How to install and set up fastboot and adb (Android SDK), by Team Android: http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/
<.< Download links is found in a separate post - Click the image below >.>
Something's missing? You got feedback? Updates I've not included yet? Anything else? Reply to this thread.
Please press THANKS if this guide has helped you
Great job,man! Thanks!:good:
This is THE GUIDE! :good:
Re: [GUIDE] Huawei Ascend P1 U9200 COMPLETE
Thanks Olav.
I suksessfulle installed muiu english v. On my p1.works Great.
Sent from my HUAWEI U9510E using xda app-developers app
gifr87 said:
Thanks Olav.
I suksessfulle installed muiu english v. On my p1.works Great.
Sent from my HUAWEI U9510E using xda app-developers app
Click to expand...
Click to collapse
Nice No problem!
Any Non-Huawei screenshots for EMUI? I mean uploaded by users
How's it working generally? Better than stock 4.0.3? Any bugs?
Thx
Great All-In-One for the Ascend P1... Was thinking about doing the same, but then I saw you already did it ...
Great work Olav!
arkedk said:
Great All-In-One for the Ascend P1... Was thinking about doing the same, but then I saw you already did it ...
Great work Olav!
Click to expand...
Click to collapse
Thanks
New EmUI beta, chinese version. B528
Mirror: https://mega.co.nz/#!7oRRlZ5Z!f8jFjj_HgVw1OWRLCbg4vgVloQNgRgNsNHv_f1C-wfY
FlashPack (Includes build.prop, recovery.img and boot.img): https://mega.co.nz/#!O9wjXByA!VzMAVV9zhmC70K9VI7jhwWLlDAs8CnBCvnfrAnVaRyc
o-l-a-v said:
Thanks
New EmUI beta, chinese version. B528
Mirror: https://mega.co.nz/#!7oRRlZ5Z!f8jFjj_HgVw1OWRLCbg4vgVloQNgRgNsNHv_f1C-wfY
FlashPack (Includes build.prop, recovery.img and boot.img): https://mega.co.nz/#!O9wjXByA!VzMAVV9zhmC70K9VI7jhwWLlDAs8CnBCvnfrAnVaRyc
Click to expand...
Click to collapse
perfomance wise, is emui better to miui?
areankim said:
perfomance wise, is emui better to miui?
Click to expand...
Click to collapse
When I tried the jelly bean emui, I thought it was a bit of a ripoff of MIUI. I like MIUI better.
Sent from my U9200 using xda app-developers app
Guys, jst flash to EMUI B528 custom without gapps, and dowlonad the 4.1.x gapss 20121011 but after i flash it, nothing appear.
then i tried the prev version and 20121130, stll nothing. Weird,
areankim said:
Guys, jst flash to EMUI B528 custom without gapps, and dowlonad the 4.1.x gapss 20121011 but after i flash it, nothing appear.
then i tried the prev version and 20121130, stll nothing. Weird,
Click to expand...
Click to collapse
You rooted before flashing GAPPS?
The "power bar"
I flashed B229 to a U9200, it had originally B103 which had been updated to 105. manually edited the build to B226 before updating with cwm. Everything is working fine no problems. Only couple of things are missing. The "power bar" which i use to control wifi, BT etc. power on and off in the notification menu (or what ever it is called, the menu that appears when swiping down from the upper edge) is missing and it is quite handy and I'm used to it. Other is the missing boot animation which i knew will be missing after update but did not care about that originally since other bigger issues in the B10x FWs forced me to update to B229. But if easy to apply and anyone knows the way to restore the animation (restore the looks as much "stock" as possible) i would appreciate. But the "power bar" would be very important, anyone know how to restore that? I have messed around with Android a bit and have installed and used custom ROMs and rooted several phones so using the basic root / fastboot / adb functions is no problem even though I'm no Android/Linux expert.
Thanks in advance for your help!
And thank you Olav for the very nice compilation thread for U9200.
JJVilzu said:
I flashed B229 to a U9200, it had originally B103 which had been updated to 105. manually edited the build to B226 before updating with cwm. Everything is working fine no problems. Only couple of things are missing. The "power bar" which i use to control wifi, BT etc. power on and off in the notification menu (or what ever it is called, the menu that appears when swiping down from the upper edge) is missing and it is quite handy and I'm used to it. Other is the missing boot animation which i knew will be missing after update but did not care about that originally since other bigger issues in the B10x FWs forced me to update to B229. But if easy to apply and anyone knows the way to restore the animation (restore the looks as much "stock" as possible) i would appreciate. But the "power bar" would be very important, anyone know how to restore that? I have messed around with Android a bit and have installed and used custom ROMs and rooted several phones so using the basic root / fastboot / adb functions is no problem even though I'm no Android/Linux expert.
Thanks in advance for your help!
And thank you Olav for the very nice compilation thread for U9200.
Click to expand...
Click to collapse
Check in the Display settings if the "Notification settings" option is checked. See screenshot from the B226 ROM attached. I hope it's still there?
Boot animation can changed with the AIO flasher tool.
Krizzii said:
Check in the Display settings if the "Notification settings" option is checked. See screenshot from the B226 ROM attached. I hope it's still there?
Click to expand...
Click to collapse
I checked, it's not there in B229 wtf
JJVilzu said:
I flashed B229 to a U9200, it had originally B103 which had been updated to 105. manually edited the build to B226 before updating with cwm. Everything is working fine no problems. Only couple of things are missing. The "power bar" which i use to control wifi, BT etc. power on and off in the notification menu (or what ever it is called, the menu that appears when swiping down from the upper edge) is missing and it is quite handy and I'm used to it. Other is the missing boot animation which i knew will be missing after update but did not care about that originally since other bigger issues in the B10x FWs forced me to update to B229. But if easy to apply and anyone knows the way to restore the animation (restore the looks as much "stock" as possible) i would appreciate. But the "power bar" would be very important, anyone know how to restore that? I have messed around with Android a bit and have installed and used custom ROMs and rooted several phones so using the basic root / fastboot / adb functions is no problem even though I'm no Android/Linux expert.
Thanks in advance for your help!
And thank you Olav for the very nice compilation thread for U9200.
Click to expand...
Click to collapse
Read Dddrko's post on page 13 at http://forum.xda-developers.com/showthread.php?t=1694228&page=13, he explained how to restore toggles.with this metod u will also restore original bootanimation.
Hello,
I own an huawei u9200
I would like to flash the B229 ROM on my device running B102.
I find this thread very interesting however I have a problem at the very first step.
I can't install fastboot usb drivers
I've been trying to follow the guide you linked at the top of your post, I had a slight issue with ADB Drivers as well,
I could not make those Google USB Drivers downloaded through Android SDK work, I would get the error telling me those drivers are not developed to work with windows x64. But after checking with the command prompt, it turns out that the drivers I needed were already installed and the device is detected as ADB Device.
Back on my current issue:
I understand that I have to shut down my phone and switch it on while pressing both volume up and volume down and after turning it on, I have to plug it to the computer through USB cable. My phone does turn on in download mode, however when I connect it to the USB my computer doesn't detect anything.
Is the screen I am getting the right screen or should I switch the phone on with a different shortcut?
How do I get my computer to detect my phone when I switch it on with the volume+&- buttons?
Which are the correct fastboot drivers to install and where can I download them?
I hope to receive assistance as soon as possible.
Thank you.
EDIT:
I've managed to reboot correctly by using ADB command prompt (typing ADB reboot fastboot)
Now, I'm trying to root and in the command prompt I get this error:
"cannot load 'cwm_touch_recovery_viva_beta.img': No error"
EDIT:
Supersu installed.
Now when attempting to edit the build.prop I get a error message
I check the Concole and I see "Remount failed: Operation not permitted
But I granted root access when prompted. Any Idea?
EDIT:
Tried 39 times until I got it successfully.
And don't ask me how. It's beyond me.
Checked About and version is good.
Now rebooted and "Version list verify fail!"
WHY?
I've checked the build.prop and it is flashed,
I've flashed the 229recovery.img
I reboot and it gives me "Version list verify fail!"
What could have I done wrong?
DenesS said:
I've checked the build.prop and it is flashed,
I've flashed the 229recovery.img
I reboot and it gives me "Version list verify fail!"
What could have I done wrong?
Click to expand...
Click to collapse
Try with the build.prop from b226, avaible here: http://openbuildprop.scheffsblend.com/mfg/Huawei (copy -> paste into notepad, save as build.prop)
o-l-a-v said:
Try with the build.prop from b226
Click to expand...
Click to collapse
Ok, this makes sense, it probably wouldn't like to update to a version which is already installed.
This wasn't clear on the tutorial, thanks for the hint.
I'm trying now
EDIT:
Nope, still "Version list verify fail!"
Even though I checked in the "About" and the version shown is B226, which means the .prop was correctly flashed.
So what could the problem be?
EDIT:
Should I also try flashing the B226 recovery?
Do you have a link for any download page?
Can I flash it directly through CWM? CWM wants a root://Update.zip can I put my UPDATE.APP into a zip archive and flash it or does it work differently?
People have had problems updating to B229 with the build.prop i extracted from the B229 fw.
There is simply a little difference at this line:
Code:
ro.build.display.id=V100R001C00B229
It should be:
Code:
ro.build.display.id=U9200-V100R001C00B229
Build.prop from all earlier firmwares (Exept B226) including EmUI betas and stables have the "U9200-"-part before product version on this line.
This is a mistake by Huawei, not me :good:
Updated the FlashPack for B229, new link from mega in first post!
Just going to dump all the info I've found about this device into this thread. All the threads pertaining to this thread are in Russian and I can't read Russian, so this might be helpful to any English speaking owners of this tablet.
Special thanks to Telegram user @SSDD_1744 (don't know your XDA/Reddit user, I'm sorry) for basically spoonfeeding me all these instructions!
WARNING: If you need to flash to stock for whatever reason, be sure to download a image file specific to your country. If you don't, you'll hard brick your device that can only be fixed QPST (supposedly).
Rooting:
(Tested on 5.0.2)
Install KingRoot. Let it root your device.
Install Super-SU Me, to get rid of the bloatware that comes with KingRoot.
Installing Xposed:
I used Flashify to flash TWRP. Be sure to flash the right version though (2.8.7.7 v2) or else you won't be able to mount cache.
Then download Xposed (version sdk21 ARM) and flash it.
WARNING: Flash v1 of the modded TWRP and you won't be able install any apps after flashing Xposed.
Unbricking:
Still working on it. Downloaded QPST but have not been able to get QPST 2.7 to read the tablet.
Links:
Discussion:
https://translate.googleusercontent...690491&usg=ALkJrhiWSlkbZ-tUofZx68NPSGIv8pjIPA
Root:
https://translate.googleusercontent...JrhhQszcRvUo8HILThvz57JmsLj4L9g#entry44556703
https://translate.googleusercontent...JrhiCt__6apcRhk-gtcBExYJCnC9nGQ#entry41676452
Instructions for obtaining the rights to Ruth phones / tablets.
Tested on Android 4.4+
perhaps this algorithm works on Android 5+, I have no way to verify
All transactions with their phones / tablets are performing at your own risk !!!
To get started, read this post from start to finish and only then proceed to action!
Introduction
This instruction is written based on my own experience obtaining root on their plates, and then on the Xperia M2, bought plemyashki. For instructions attached versions of applications that were relevant at the time, the new version can download the relevant topics on the forum, there will find all information on how to work with the proposed programs and algorithms for their actions (links to topics added).
For all the action with your phone / tablet you are responsible for yourself!
Download all the necessary tools to obtain Root (of instructions / topics on the forum), obespechte for phone / tablet access to the Internet (Wi-F / mobile data) and let the phone settings / tablet installation from unknown sources.
Needed Downloads
KingRoot_V4.5.0B202.apk (6.76 MB)
Me_5.9.apk-SuperSU (9.07 MB)
V2.49 Beta.apk SuperSU (5.63 MB)
eu.chainfire.supersu.pro.205.apk (52,88 KB)
Next in series:
1. Install KingRoot .
Get Ruth's right, in the device may reboot.
2. Set SuperSU-Me, .
Run the grantor, the program deletes KingRoot and Chinese KingUser with replacement SuperSu.
Remove the longer SuperSu-Me the desired program.
3. Obnovyaem SuperSu to the latest version. Then set PRO-key .
Installing Pro-key Optionally !!! Use Cases SuperSu without installing key .
4. Open SuperSu and on-demand update binary SU normal way. After a successful update, confirm the request to restart.
5. To make sure that everything is done correctly, check the correct installation and operation of Ruth (mount the system partition on the record), I used the Root Checker Pro and Root Explorer , respectively.
The output is a complete rut without kitayschiny with SuperSu Pro. We use and enjoy
Click to expand...
Click to collapse
Unlocking bootloader (haven't tried this):
https://translate.googleusercontent...Jrhh6g4wI-8Hb_LzAcPnIUxYvWNzZ0A#entry46711087
Stock firmware:
https://translate.googleusercontent...?s=&showtopic=703414&view=findpost&p=45272695
Damn, development has really boomed on this little tablet! Finally got it back after a few months (I sent it into Asus to repair it for me).
Stock ROM:
https://www.asus.com/ru/Tablets/ASUS_ZenPad_80_Z380KL/HelpDesk_Download/ (I can't get the English version to load, delete the /ru/ and you'll be redirected to the English site)
https://www.asus.com.cn/Tablets/ASUS_ZenPad_80_Z380KL/HelpDesk_Download/ (Chinese site)
==== REMEMBER TO DOWNLOAD THE CORRECT COUNTRY OR YOU'LL BE BRICKED) ====
https://yadi.sk/d/b1NMLXHBsNV8C (latest software for the worldwide model)
[http://4pda.ru/forum/index.php?showtopic=703414&st=320#entry50270292]
http://4pda.ru/forum/index.php?showtopic=703414&st=200#entry49389176 (Asus Flash Tool and stock ROM v4.8.2 WW [WorldWide])
Unlocking bootloader:
http://4pda.ru/forum/index.php?showtopic=690491&st=1280#entry48200665 (use fastboot oem device-info to check if it's unlocked)
Root:
http://4pda.ru/forum/index.php?showtopic=690491&st=580#entry44778545 (KingRoot - you'll need a 4PDA.ru account to download this)
http://4pda.ru/forum/index.php?showtopic=690491&st=1280#entry48185323 (last section of the post)
CM13:
http://get.cm/?device=P024&type=nightly
https://vasy.ru/CM13/
http://forum.xda-developers.com/android/help/asus-zenpad-8-z380kl-custom-rom-t3370277
http://forum.xda-developers.com/android/development/kernel-asus-z380kl-p024-kcal2-t3405595 (Kernel)
Recovery:
https://vasy.ru/TWRP/P024/
http://4pda.ru/forum/index.php?showtopic=690491&st=1220#entry48094504 (TWRP 2.8.7.0)
http://forum.xda-developers.com/android/help/asus-zenpad-8-0-z380kl-bootloop-t3373051
Guides:
http://4pda.ru/forum/index.php?showtopic=690491&st=1280#entry48185323 (this has a lot of instructions: root, recovery, boot partition restore, adb drivers etc.)
http://forum.xda-developers.com/android/help/asus-zenpad-8-0-z380kl-bootloop-t3373051 (this has a bunch of files, Resurrection Remix [I haven't tested it yet tho], and instructions on getting out a bootloop)
http://4pda.ru/forum/index.php?showtopic=690491&st=1640#entry49724823 (flashing stock software)
If you want to open the engineering menu, type " * # * # 4636 # * # * "
To boot into fastboot, restart/turn on the device and hold volume up. It'll pop you into a menu with three options.
To boot into recovery, from the fastboot screen (three options), use the volume buttons and navigate to the second option "factory reset" and hit power to confirm. It'll boot into recovery.
=====================================================================================
Recommended way to flash ROMs:
1) Download TWRP. Use adb to boot (NOT flash) into TWRP. Flash ROM there.
2) use KingRoot to root. Use Flashify to flash the ROM.
======================================================================================
If you want to go look up some more info or guides, go here:
http://4pda.ru/forum/index.php?act=...=rel&subforums=0&query=z380kl&forums=570&st=0
and use GTranslate to translate the page. The first page is the earliest posts with the keyword, the last page are the latest post.
please add these ROM's for this Device:
Ressurection Remix:
https://www.androidfilehost.com/?w=files&flid=121811
AICP 12.1:
https://www.androidfilehost.com/?w=files&flid=136181
The latest Official ROM P024 model:
http://dlcdnet.asus.com/pub/ASUS/Ee...ser.zip?_ga=1.109506565.1670552787.1483182775
ZenPad 8 Z380KL Firmware: V5.9.0.0 (WW SKU version only)
Improved Item:
1. Update Google security patch
2. Support unlock tool
9008 brick info:
https://4pda.ru/forum/index.php?showtopic=643084
Pertaining to p024:
https://4pda.ru/forum/index.php?showtopic=643084&st=5740
https://4pda.ru/forum/index.php?showtopic=643084&st=3660 (page 179 - 180, 183 - 185 discusses the files needed to unbrick and how you would - CTRL + F Russ and read the people who quote him)
How I bricked: https://4pda.ru/forum/index.php?showtopic=703414&st=180#entry49329798
https://4pda.ru/forum/index.php?showtopic=690491&st=1420#entry48527044 (unbricking files - dead link though)
https://4pda.ru/forum/index.php?showtopic=703414&st=140 (discussing how to fix using the images from the dump)
I see that Lineage OS is supported on Z380KL. However, I found the wiki spec showing Snapdragon 410, but I found Z380KL in Asia with Snapdragon 615. Before I commit, I'd like to know if anyone knows whether LineageOS is fully compatible with Z380KL with Snapdragon 615 chipsets? Thanks.
Special thanks to @a350tv for helping me comb through 4PDA - this process would've been a lot slower or just wouldn't have happened if he hadn't offered to translate guides and download links to me. So most of the credit goes to him.
Flashing TWRP on 6.0.1 (Sept 1, 2016 patch):
1) grab your drivers (W10: boot into "no driver signature verification mode" to install the drivers needed for fastboot)
https://drive.google.com/open?id=1cGcoDCvmTxfXWNTG0iOXHw1WScmYBrKS
2) turn on debugging
3) type in "adb devices", verify that your computer sees your tablet (if you don't have ADB/Fastboot, get https://forum.xda-developers.com/showthread.php?t=2317790)
4) type in "adb reboot bootloader"
5) you'll see three options: 1. Enter SD DL mode, 2. Factory Reset, 3. Exit update mode
6) type in "fastboot devices", verify that your computer sees your tablet
7) grab your TWRP file (http://vasy.ru/TWRP/P024/) and type in "fastboot flash recovery [replace w/ location of the TWRP file].img"
8) once it says "finished", click factory reset mode (use volume buttons to navigate, power button to enter)
9) it should reboot into TWRP, slide to allow modifications
10) Boom, TWRP is installed.
OPTIONAL, BUT HELPS TO KEEP TWRP INSTALLED: Flash Magisk.
That way, stock recovery won't overwrite TWRP when you reboot.
IF YOU WANT TO KEEP TWRP BUT DON'T WANT Magisk:
1) After first boot into TWRP, turn off tablet.
2) Then turn on and hold Volume Up + Power. That will boot you into Bootloader Mode.
3) Go into factory reset and it should boot you into TWRP.
Now, it's safe to boot into the OS.
(TL;DR: Boot into TWRP twice before booting into the OS or else stock recovery will overwrite TWRP.)
Flashing LineageOS:
1) DL LOS from https://download.lineageos.org/P024
2) DL GApps from http://opengapps.org/ (choose 7.1)
3) boot into TWRP
4) go into Wipe, slide to wipe
5) go to Install, click on LOS file > add to queue, click on Open GApps file > add to queue, flash
6) wait til it's done, click "reboot"
7) wait a while (took mine 3 or so minutes to boot)
8) enjoy!
My GDrive folder with all files needed (except ROM and GApps)
https://drive.google.com/open?id=0BzJ-WWaQYXttTkttdHNELVBEc2M
To do:
Use this tutorial to backup all my partitions, just in case I get bricked yet again.
https://forum.xda-developers.com/showthread.php?t=2450045
Links to unbrick device via Asus FlashTool
Links to service ROMs (for use with AFT)
Add original links from 4PDA
ROMs
LineageOS: https://download.lineageos.org/P024
AICP: https://saki-sss.blogspot.com.by/2016/12/z380k-aicp-121.html
Resurrection Remix: https://androidfilehost.com/?w=files&flid=121811
(made by https://androidfilehost.com/?w=profile&uid=457095661767100043, found from http://andmem.blogspot.jp/2016/05/asus-zenpad-8-z380kl-root-rom.html#chapter-19) - abandoned?
seities said:
I see that Lineage OS is supported on Z380KL. However, I found the wiki spec showing Snapdragon 410, but I found Z380KL in Asia with Snapdragon 615. Before I commit, I'd like to know if anyone knows whether LineageOS is fully compatible with Z380KL with Snapdragon 615 chipsets? Thanks.
Click to expand...
Click to collapse
probably not. I think it's only compatible with the SD 410.
xDark_ said:
Special thanks to @a350tv for helping me comb through 4PDA - this process would've been a lot slower or just wouldn't have happened if he hadn't offered to translate guides and download links to me. So most of the credit goes to him.
Flashing TWRP on 6.0.1 (Sept 1, 2016 patch):
1) grab your drivers (W10: boot into "no driver signature verification mode" to install the drivers needed for fastboot)
https://drive.google.com/open?id=1cGcoDCvmTxfXWNTG0iOXHw1WScmYBrKS
2) turn on debugging
3) type in "adb devices", verify that your computer sees your tablet (if you don't have ADB/Fastboot, get https://forum.xda-developers.com/showthread.php?t=2317790)
4) type in "adb reboot bootloader"
5) you'll see three options: 1. Enter SD DL mode, 2. Factory Reset, 3. Exit update mode
6) type in "fastboot devices", verify that your computer sees your tablet
7) grab your TWRP file (http://vasy.ru/TWRP/P024/) and type in "fastboot flash recovery [replace w/ location of the TWRP file].img"
8) once it says "finished", click factory reset mode (use volume buttons to navigate, power button to enter)
9) it should reboot into TWRP, slide to allow modifications
10) Boom, TWRP is installed.
OPTIONAL, BUT HELPS TO KEEP TWRP INSTALLED: Flash Magisk.
That way, stock recovery won't overwrite TWRP when you reboot.
IF YOU WANT TO KEEP TWRP BUT DON'T WANT Magisk:
1) After first boot into TWRP, turn off tablet.
2) Then turn on and hold Volume Up + Power. That will boot you into Bootloader Mode.
3) Go into factory reset and it should boot you into TWRP.
Now, it's safe to boot into the OS.
(TL;DR: Boot into TWRP twice before booting into the OS or else stock recovery will overwrite TWRP.)
Flashing LineageOS:
1) DL LOS from https://download.lineageos.org/P024
2) DL GApps from http://opengapps.org/ (choose 7.1)
3) boot into TWRP
4) go into Wipe, slide to wipe
5) go to Install, click on LOS file > add to queue, click on Open GApps file > add to queue, flash
6) wait til it's done, click "reboot"
7) wait a while (took mine 3 or so minutes to boot)
8) enjoy!
My GDrive folder with all files needed (except ROM and GApps)
https://drive.google.com/open?id=0BzJ-WWaQYXttTkttdHNELVBEc2M
To do:
Use this tutorial to backup all my partitions, just in case I get bricked yet again.
https://forum.xda-developers.com/showthread.php?t=2450045
Links to unbrick device via Asus FlashTool
Links to service ROMs (for use with AFT)
Add original links from 4PDA
Click to expand...
Click to collapse
Thanks for the tutorial, I had already dared to flash twrp recovery before you wrote this tutorial...
I believe my bootloader is still locked. And I could not reproduce/ write exactly what I did. But, in my case, just for information, when I want to go back into twrp, I can boot into bootloader (power volume up) and then option 2 reset the device gives me the twrp... I am not sure if that is how you get it, but for me, I still had twrp.
I think i will install magisk after reading your post.
jutphaas said:
Thanks for the tutorial, I had already dared to flash twrp recovery before you wrote this tutorial...
I believe my bootloader is still locked. And I could not reproduce/ write exactly what I did. But, in my case, just for information, when I want to go back into twrp, I can boot into bootloader (power volume up) and then option 2 reset the device gives me the twrp... I am not sure if that is how you get it, but for me, I still had twrp.
I think i will install magisk after reading your post.
Click to expand...
Click to collapse
I don't think unlocking the BL is necessary for flashing LOS. But yes, that's how I get into TWRP as well.
Hello I'm new in the forum and I write from Italy, yesterday unfortunately I had the brilliant idea to downgrade my Asus z380kl through ADB, Fastboot and TWRP from pc so far so good, I go to flash the new rom and gives me error, I try to restore the backup here too error result? Tablet locked the only way to make it recognize to the PC is with ASUS FLASH TOOL ROM problem in format.raw unobtainable not even on the Russian site. Any good soul has the possibility to let me download it? Thanks, Sorry English but it is a translation of the very useful Google translate.
pucci2 said:
Hello I'm new in the forum and I write from Italy, yesterday unfortunately I had the brilliant idea to downgrade my Asus z380kl through ADB, Fastboot and TWRP from pc so far so good, I go to flash the new rom and gives me error, I try to restore the backup here too error result? Tablet locked the only way to make it recognize to the PC is with ASUS FLASH TOOL ROM problem in format.raw unobtainable not even on the Russian site. Any good soul has the possibility to let me download it? Thanks, Sorry English but it is a translation of the very useful Google translate.
Click to expand...
Click to collapse
Can you still access fastboot, then at least you can flash twrp as described before in this thread and install from twrp lineageos p024 (lineage-14.1-20180105-nightly-P024-signed.zip) and Open gapps to get google playstore etc , select Arm, (not 64) then version 7.1, then Pico would work.
If you have twrp, you at least can still use your asus... I have found no way to flash original stock... stock must not be flashed from twrp.
Since you mention twrp already used, you can try: turn your device off, then press volume up then the bootloader menu comes, select 2: reset to enter twrp(where it says reset. if you had flashed twrp, that is how you can get into twrp) from there, install lineage os and gapps from micro sd card
My rom is MMB29M.WW_P024-V5.9.4-20170613
xDark_ said:
OPTIONAL, BUT HELPS TO KEEP TWRP INSTALLED: Flash Magisk.
That way, stock recovery won't overwrite TWRP when you reboot.
Click to expand...
Click to collapse
I assume this is on stock rom ? What version of magisk would work? I found I can be back at stock with my twrp backup so ..
But magisk 15.3 zip failed to install on stock-
I also used supersu v82 working on stock, or lineageos.
Would you know what magisk works on lineageos?
I like the exsd extension of magisk so I would like to try it on this device, either stock or lineageos
jutphaas said:
I assume this is on stock rom ? What version of magisk would work? I found I can be back at stock with my twrp backup so ..
But magisk 15.3 zip failed to install on stock-
I also used supersu v82 working on stock, or lineageos.
Would you know what magisk works on lineageos?
I like the exsd extension of magisk so I would like to try it on this device, either stock or lineageos
Click to expand...
Click to collapse
Yes it was. I flashed 15.2 on both stock and LOS. I've heard of some issues with 15.x so you can try .2 or 14.x.
pucci2 said:
Hello I'm new in the forum and I write from Italy, yesterday unfortunately I had the brilliant idea to downgrade my Asus z380kl through ADB, Fastboot and TWRP from pc so far so good, I go to flash the new rom and gives me error, I try to restore the backup here too error result? Tablet locked the only way to make it recognize to the PC is with ASUS FLASH TOOL ROM problem in format.raw unobtainable not even on the Russian site. Any good soul has the possibility to let me download it? Thanks, Sorry English but it is a translation of the very useful Google translate.
Click to expand...
Click to collapse
What error was given? What do you see when you connect it to a computer? What does "tablet locked" mean? Would help if you gave some pictures too.
I'm currently in the process of getting the RAW files/service ROMs for AFT but I don't have an ETA on when I'll be able to get that.
No on the tablet I have not installed TWRP and no other recovery.When I go into the original recovery of the tablet there is always the screen with the lock closed at the bottom right and there is no way to show it to the PC even with adb sideload, l 'only program that recognizes me the tablet is Asus flash tool, however, as I have already written the damn ROM in RAW format is untraceable.
pucci2 said:
No on the tablet I have not installed TWRP and no other recovery.When I go into the original recovery of the tablet there is always the screen with the lock closed at the bottom right and there is no way to show it to the PC even with adb sideload, l 'only program that recognizes me the tablet is Asus flash tool, however, as I have already written the damn ROM in RAW format is untraceable.
Click to expand...
Click to collapse
Does it respons to adb devices of fastboot devices in this stage?
no, it is not recognized
(I wrote the 'new' version of rooting out of memory / conjecture, it should not do irreversible harm to your tablet, however, always apply common sense and proceed with caution. Caveat - I am neither a developer nor software engineer.)
'New' version of rooting procedures can be carried out with relative ease now that @krustymars has done the heavy lifting and ported TWRP to Teclast X16Plus; applies to both native android 5.1.1 and Remix 2.0.
In his write-up, it wasn't mentioned that TWRP can only be installed if X16 Plus's bootloader is 'OEM unlocked' and ROM will only boot if X16 Plus's boot image is patched (insecured), after the flashing of TWRP.
To unlock is not difficult (fastboot oem unlock), but it will also wipe /data of the ROM (making it unbootable too?). Question mark here as I am uncertain whether this action will render the ROM unbootable or not. For the sake of not doing double jobs, we assume it will.
The third condition for the ROM to first boot properly after flashing is the original recovery must be present (again I am not sure if a patched boot image will do the trick; for the same reason above, we assume it won't)
Therefore the only way out is to ensure the bootloader is not re-locked after the flashing of ROM, for us to be able to flash an effective TWRP AFTER the ROM has finished its first boot.
I believe the above are the main reasons why @stratos7 faced difficulties when intending to root via TWRP.
A simple and rudimentary step by step guide as below (you will LOSE ALL DATA in the tablet, backup all your important stuffs before proceeding):
1) Rename the ROM's original recovery.img to recovery.org. Copy krustymars' TWRP over and rename it recovery.img
This is to ensure that after the flashing, the reboot process will fail and the script will not re-lock the bootloader
2) Flash the ROM as per normal (enter DNX Fastboot by pressing vol+ vol- and power button concurrently, then use Intel Platform Flash Tool Program to flash).
3) After a successful flash, the tablet will enter recovery (TWRP) first time during reboot, and failed. It will be stuck in a boot loop (showing TWRP error).
4) Force shut it by pressing the power button for 10-15secs.
5) Enter fastboot by pressing vol- and power button concurrently.
6) Flash the orginal recovery via adb fastboot.
fastboot flash recovery recovery.img
7) Reboot normally and the ROM will load properly (1st successful boot will take a while; as long as you see the Remix OS logo flashing, all are good).
8) 10x click on Build Number to activate Developer's Menu
9) Activate USB debugging
10) Reboot into fastboot by typing
adb reboot fastboot
11) Check to ensure that bootloader is still unlocked.
12) Flash krustymars' TWRP
fastboot flash recovery TWRP_TeclastX16Plus_by_krustymars.img
13) Flash patched boot image
fastboot flash boot boot.img
14) Choose Recovery Mode, ensure X16 Plus boots into TWRP fine
15) Reboot into ROM from TWRP
16) If you are satisfied that all are fine after rebooting into the ROM, and have copied the latest downloaded SuperSU.zip flashable file into the Internal or Micro SD memory, you can either adb reboot fastboot or shutdown the tablet and vol- power button into fastboot, and then choose Recovery Mode from within fastboot to enter TWRP to flash SuperSU to get root.
Do note that you cannot update binaries within Android, you can update the SuperSU app though if a new version comes up in Play store, just not the binaries. If your binaries become outdated, you will need to flash the latest SuperSU.zip again via TWRP.
The necessary files (minus SuperSU, do grab that from Chainfire's site) - https://www.mediafire.com/?3blso8sjw4kb3e6
Once again, proceed with caution / common sense and the above shouldn't land you in any irreversible situation. All the best!
_____________________________________________________________________________________________________________________________
OLD METHOD
The below instructions for rooting Teclast X16 Plus originated from Teclast's forums. All credits go to the respective creator(s), I merely translated them to post here.
1) Download the standard rooting package from http://www.mediafire.com/download/nrez4ggzau1u8ax/Root.X16Plus.V1.zip
2) Download your corresponding edited boot image file and extracted build prop file (for either Remix OS 2.0 ver B2016062701 or Android 5.1 ver 1.07)
- for Remix OS http://www.mediafire.com/download/b6aazky2y9eqch7/Remix_OS_2.0.zip
- for Android 5.1 http://www.mediafire.com/download/zz40a8cgav385l3/android5.1.zip
3) Download and install Intel's tools and drivers in the order below - http://www.mediafire.com/download/p723or9hxip5eu8/Intel_Flash_Tools.rar
You can omit this step if these drivers are already installed.
- iSocUSB-Driver-Setup-1.2.0.exe
- IntelAndroidDrvSetup1.10.0.zip
- PhoneFlashToolLite_5.5.2.0_win32.exe
4) Download kingroot tool from below, copy the apk file to your X16 Plus and install. There is no need to run the installed app now.
5) Ensure USB debugging is switched on under developer options in your ROM
6) Unzip both the rooting package and your corresponding edited boot image and extracted build.prop files. Cut and paste the unzipped boot image and build prop files into the unzipped rooting package directory.
7) Launch command prompt and change directory to the unzipped rooting package directory
8) Connect your X16 Plus via USB
9) Type and enter - adb reboot bootloader
10) X16 Plus will reboot into fastboot mode
11) Type and enter - fastboot flash boot boot-root.img
12) Type and enter - fastboot reboot
13) X16 Plus will reboot into normal mode, wait for the bootup process to finish
14) Type and enter - su.bat
15) Run the previously install Kingroot app, Kingroot will prompt you to repair root privileges, allow it to do so.
16) Reboot your X16 Plus after the above repair and you will have full root access. If root access is still incomplete, run the above step 14) su.bat command again
Just one thanks cannot say how much grateful I am. THANKS. It work.
Thanks a lot Potatohead ! You rock !
I will try this instruction and post a feedback as soon as possible !
potatohead,
I have just finish to root my tablet. It's very easy and everything is fine.
Once again, thanks a lot ! :good:
great job !!
all are OK under win XP
Thx
Hi @potatohead , Hi @TrYkeR ,
I've just discovered a new firmware V1.07 for our X16 plus on the Teclast website (in the download section) . My tablet is running with the V1.04 version.
Do you know you to flash it, cause TeclastOTA is unable to ugrade it both with the Online mode ("undiscover new version") and the Local mode ?
Reno.
I'm using 1.07, I use a tutorial from their webside.
The big problem is download the firmware, their server sucks a lot. I use jdownload since chrome crash 2 times and do not recover the download
Firmware:
http://pan.baidu.com/s/1nvKVjnF
https://yadi.sk/d/TrUPzmkXsFrXJ (mirror)
here they talk about it:
http://techtablets.com/forum/topic/teclast-x16-plus-i-want-to-change-from-v-1-04-to-v-1-07/
I didn't find the post that I use, but was really easy, like paste the .img files into a folder, put teclast plus in "download mode", they called it diferent, and run an script (.bat)
Hi @TrYkeR,
Thanks for your prompt reply.
I searched for the tuto but I didn't find it too (I already have the V1.07 download). I do not want to do it by myself, i'm not enough confident.
If you find it...
Reno
renofaringite said:
Hi @TrYkeR,
Thanks for your prompt reply.
I searched for the tuto but I didn't find it too (I already have the V1.07 download). I do not want to do it by myself, i'm not enough confident.
If you find it...
Reno
Click to expand...
Click to collapse
I didn't found the exactly post I've use.
Was in this forum:
http://techtablets.com/forum/forums/teclast/general-discussion/page/1/
im new users teclast x16 plus .. is better remixos or android 5.1 firmware 1.0.7 (for drain battery etc..)
Hello friends,
I have the same question.... is better remixos or android 5.1 firmware 1.0.7?
Thanks a lot !!
Renew link
Potatohead, could you please post another link to root.x16plus.v1.zip?
Mediafire removed the file, nowhere else to be found (according to google...)
Thanks in advance!
So did anyone else happen to pick this up from tinydeal while they had it for $79? Not sure if it's arriving with 5.1 or Remix, but this is good to know.
Henk S. said:
Potatohead, could you please post another link to root.x16plus.v1.zip?
Mediafire removed the file, nowhere else to be found (according to google...)
Thanks in advance!
Click to expand...
Click to collapse
As you, I'm looking for this file to root my tablet.
Henk S. said:
Potatohead, could you please post another link to root.x16plus.v1.zip?
Mediafire removed the file, nowhere else to be found (according to google...)
Thanks in advance!
Click to expand...
Click to collapse
bja9 said:
As you, I'm looking for this file to root my tablet.
Click to expand...
Click to collapse
Guys, you can get it here
Link:
pan.baidu.com/s/1eSfpVW2
Password:
xc1u
---------- Post added at 05:20 AM ---------- Previous post was at 05:17 AM ----------
potatohead said:
The below instructions for rooting Teclast X16 Plus originated from Teclast's forums. All credits go to the respective creator(s), I merely translated them to post here.
...
Click to expand...
Click to collapse
I followed the instructions and flashed boot-root.img successfully, however I'm unable to run adb remount in su.bat
it says "remount of system failed: Permission denied", "remount failed"
any ideas?
btc002 said:
Guys, you can get it here
Link:
pan.baidu.com/s/1eSfpVW2
Password:
xc1u
---------- Post added at 05:20 AM ---------- Previous post was at 05:17 AM ----------
I followed the instructions and flashed boot-root.img successfully, however I'm unable to run adb remount in su.bat
it says "remount of system failed: Permission denied", "remount failed"
any ideas?
Click to expand...
Click to collapse
Tank you for the link to the file. It works fine for me !
Rooting in progress.
Did someone sucessfully installed Remix OS 3.0 or W10 ? (W10 i get acpi boot error :/)
I followed the instructions and flashed boot-root.img successfully, however I'm unable to run adb remount in su.bat
it says "remount of system failed: Permission denied", "remount failed"
any ideas?
Click to expand...
Click to collapse
me too...any ideas?
best regards
:good:
..
EDIT 8/2/19: I do not own this device anymore. So i cannot and dont know if anything changed about the procedures unlocking rooting etc. BUT if you are getting any trouble i might can help you. Comment your thoughts below
Hey guy, i saw a lot of guys here wondering how to root and flash twrp recovery on thier devices . Today i am gonna show you how to do that.
First of all make sure 3 things :
1. backup your images, contacts, music tracks etc on a external SD CARD, or on your computer.
2. You MUST have the BOOTLOADER unlocked. To do that, read this guide http://en.miui.com/thread-202290-1-1.html
3.Charge your device to 80%+
HOW TO FLASH TWRP AND ROOT MI MAX
1. Go to Settings-About phone-Find the MIUI VERSION, and tap on it for 5-10 times.
2. Go back to settings, sellect adittional settings. click on Developer options, and select enable
3. Find the option USB Debugging and enable it.
4. Download the TWRP recovery from the link
5. rename the file to 'recovery.img'
6. Move the image to the same file where the ADB was installed ( it should be on Computer-> C: -> Adb )
7. Open the adb folder
8. Press and hold the shift key and right click in the folder
9. click on the option "Open command window here"
10. Boot your device on fastboot mode by turning it off, pressing Power and the Volume Down buttons together, and then connect it with your computer
11. First type this command "fastboot devices" to check if your device is into fastboot mode
12. Enter the command "fastboot flash recovery recovery.img"
13. Enter the command "fastboot boot recovery.img"
14. Your phone is now in TWRP recovery mode ( if it is not, the write on ADB: reboot recovery )
15. select Install Zip and click on 'SuperSu.zip'
16. corfirm the flash
17. reboot your device
18. DONT PANIC IF YOU DEVICE WONT TURN ON. Sometimes need to wait 10-20 secs.
DOWNLOADS
1. ADB- (https://forum.xda-developers.com/showthread.php?t=2588979)
2. XIAOMI MI MAX HYDROGEN DRIVERS (http://xiaomiadvices.com/download-xiaomi-usb-drivers/)
3. TWRP RECOVERY IMAGE https://dl.twrp.me/hydrogen/ LATEST VERSION IS twrp-3.2.3-0
4. BetaSuperSu 2.74 http://www13.zippyshare.com/v/OFQGvIyA/file.html
RESERVED
The thread must be removed to XIAOMI MI MAX GUIDES, NEWS, & DISCUSSION
Hallo Friend!
I am about to test your guide. I think it is most decent among other guides on the net...
Could you please just tell me if it's gonna work on:
Android 6.0.1 MMB29M
MIUI 8.2.1.0 (MBCMIDL) Stable
kernel 3.10.84-perf-gfe86e7b
bootloader UNLOCKED
Is superSU by default included in the TWRP you gave? No need to download it additionally from somewhere?
What about warning about "dm-verity" on official TWRP website?
This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
Click to expand...
Click to collapse
Should this be any concern that the phone will not boot up again? Should this be disabled first?
Is it better to use the TWRP version you provided (3.0.3.0? not listed on official TWRP website? why?) or the lastest 3.1.0.0?
noob456 said:
Hallo Friend!
I am about to test your guide. I think it is most decent among other guides on the net...
Could you please just tell me if it's gonna work on:
Android 6.0.1 MMB29M
MIUI 8.2.1.0 (MBCMIDL) Stable
kernel 3.10.84-perf-gfe86e7b
bootloader UNLOCKED
Is superSU by default included in the TWRP you gave? No need to download it additionally from somewhere?
What about warning about "dm-verity" on official TWRP website?
Should this be any concern that the phone will not boot up again? Should this be disabled first?
Is it better to use the TWRP version you provided (3.0.3.0? not listed on official TWRP website? why?) or the lastest 3.1.0.0?
Click to expand...
Click to collapse
hello, please write again your problem. I can understand what do you mean.
StonebridgeGr said:
hello, please write again your problem. I can understand what do you mean.
Click to expand...
Click to collapse
Ok just two questions then, because I'm not sure what you can't understand. Please explain.
1) What Android, MIUI and kernel did you root?
2) Do you have SuperSu.zip in TWRP 3.0.3 by default? You didn't say anything in your guide about downloading it and from where + what version.
noob456 said:
Hallo Friend!
I am about to test your guide. I think it is most decent among other guides on the net...
Could you please just tell me if it's gonna work on:
Android 6.0.1 MMB29M
MIUI 8.2.1.0 (MBCMIDL) Stable
kernel 3.10.84-perf-gfe86e7b
bootloader UNLOCKED
Is superSU by default included in the TWRP you gave? No need to download it additionally from somewhere?
What about warning about "dm-verity" on official TWRP website?
Should this be any concern that the phone will not boot up again? Should this be disabled first?
Is it better to use the TWRP version you provided (3.0.3.0? not listed on official TWRP website? why?) or the lastest 3.1.0.0?
Click to expand...
Click to collapse
This twrp. Img it's for all the versions but only for mi max. Not the prime . This twrp doesn't contain superSU. If I remember correctly. But if on the TWRP contain the super su. Don't say yes. Just flash it like I saying on the guide. Maybe they upload a newest version. You can use the new. I think I put the official website . I will check it.
Ok thanks for the answer. Please check from where I download SuperSu - which version would be best.
Please tell me your Android, kernel and MIUI version that you rooted.
noob456 said:
Ok thanks for the answer. Please check from where I download SuperSu - which version would be best.
Please tell me your Android, kernel and MIUI version that you rooted.
Click to expand...
Click to collapse
LOL I forgot to add the superSU link...
That's what I told you. Then please do.
noob456 said:
That's what I told you. Then please do.
Click to expand...
Click to collapse
ok on the first post you can find all the links. if i miss something please tell me here !
Is this beta version of SuperSU reliable? Did you use it? Not better to use a stable version?
noob456 said:
Is this beta version of SuperSU reliable? Did you use it? Not better to use a stable version?
Click to expand...
Click to collapse
It's compatible with mi max. You will not have any problem. Don't worry
noob456 said:
Is this beta version of SuperSU reliable? Did you use it? Not better to use a stable version?
Click to expand...
Click to collapse
Waiting to tell me if everything went fine with the installation and the flashing
Hey, tried following Your guide to install a new rom last night. Great guide for noobs like me, but it may be worth renaming the thread to something like "How to flash whatever makes You happy on to Your Mi Max". These instructions seem to work fine regardless of what's being flashed. Great job, mate!
So I finally tried it and it was successful for me as well! But I used the latest version of TWRP (3.1.0) and SuperSu (2.79-20161205). Please add a point in your tutorial to upload SuperSU.zip to the phone first, because out of emotion, I forgot... So I flashed TWRP, booted it and then... ups... no SuperSu So I wanted to reboot the phone to upload SuperSU but since only SuperSU patches dm-verity (the thing I was afraid of the most - I told you before), my phone got into boot-loop and didn't want to start. So I just uploaded SuperSU to a memory card, entered Fastboot Mode again with key-combination, plugged the cable, typed "fastboot reboot-bootloader" command and was again in TWRP to flash SuperSu from my memory card.... ufff.
So I would reedit it a bit:
0. Copy SuperSU.zip to the phone/memory card!
1. Go to Settings-About phone-Find the MIUI VERSION, and tap on it for 5-10 times.
2. Go back to settings, sellect adittional settings. click on Developer options, and select enable
3. Find the option USB Debugging and enable it.
4. Download the TWRP recovery from the link
5. rename the file to 'recovery.img'
6. Move the image to the same file where the ADB was installed ( it should be on Computer-> C: -> Adb )
7. Open the adb folder
8. Press and hold the shift key and right click in the folder
9. click on the option "Open command window here"
10. Boot your device on fastboot mode by turning it off, pressing Power and the Volume Down buttons together, and then connect it with your computer
11. First type this command "fastboot devices" to check if your device is into fastboot mode
12. Enter the command "fastboot flash recovery recovery.img"
13. Enter the command "fastboot boot recovery.img" - the phone will get disconnected from your PC automatically
14. Your phone is now in TWRP recovery mode (it takes about 30-60 seconds before FastBoot screen switches into TWRP - wait patiently)
15. select Install Zip and click on 'SuperSu.zip'
16. corfirm the flash
17. reboot your device
18. DONT PANIC IF YOU DEVICE WONT TURN ON. Sometimes need to wait 10-20 secs.
Hey, I just got connected with WiFi and new MIUI 8.2.3.0 MBCMIDL wants to be installed, although the phone is rooted with bootloader unlocked. Is it safe to apply the update? Is it goona remove root so that I have to go over the process again?
So I tried the update. First time it said it failed, second time it downloaded the whole ROM after which it rebooted device and TWRP started doing "something" - I don't know what. After that the phone didn't want to boot, and what's even better didn't want to run recovery (TWRP), instead it went into fastboot. What I had to do was to use MiPhoneDrivers from this topic: https://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594 (including MiFlash 2015, because 2016 version didn't want to work properly on my PC) and follow the instruction from official MIUI website to flash from scratch the new ROM MIUI 8.2.3.0 which I did. After that my phone was alive again. I installed TWRP and rooted the phone again. Now I've got MIUI 8.2.30 rooted. :] End of the story so far. My settings left untouched - icons, wallpaper etc. So that would be the way to update MIUI if they prepare a new one.
Is there anyway to root the phone without connecting it to pc?
noob456 said:
So I tried the update. First time it said it failed, second time it downloaded the whole ROM after which it rebooted device and TWRP started doing "something" - I don't know what. After that the phone didn't want to boot, and what's even better didn't want to run recovery (TWRP), instead it went into fastboot. What I had to do was to use MiPhoneDrivers from this topic: https://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594 (including MiFlash 2015, because 2016 version didn't want to work properly on my PC) and follow the instruction from official MIUI website to flash from scratch the new ROM MIUI 8.2.3.0 which I did. After that my phone was alive again. I installed TWRP and rooted the phone again. Now I've got MIUI 8.2.30 rooted. :] End of the story so far. My settings left untouched - icons, wallpaper etc. So that would be the way to update MIUI if they prepare a new one.
Click to expand...
Click to collapse
Thanks for saving me the trouble.
Can someone help with a better method of applying updates?
Will downloading the zip (1.4GB approx) and flashing via TWRP help?
Hello everyone, after struggling for a few hours I managed to finally disable force encryption in my phone (so that TWRP could backup the data partition).
I'd like to write a quick list of what I did in the form of a guide to unlocking the bootloader, installing TWRP and getting root with Magisk. I'm just a user, not a developer and this guide is brief, it's not a detailed tutorial and does not include trivial steps (like how to install drivers for your OS).
Warnings: Although small, there is always the chance this bricks your phone. I take no responsibilities.
This will factory reset your phone so back up everything before you start.
My phone is Lenovo S5 (K520) Global version (see screenshot) I don't know if this will work for other firmwares.
Prerequisites:
Install Phone, ADB and Fastboot drives. You can get ADB and Fastboot binaries from here:
https://forum.xda-developers.com/showthread.php?t=2588979
Download this archive:
http://www.mediafire.com/?4dcvzw1hdmzfn10
It contains all the files used in this guide.
Alternatively, download all the files used from their sources.
You will need an SD card or a USB flash drive with an OTG adapter.
Copy the following files to it:
A. "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip"
(Downloaded from http://forum.xda-developers.com/showthread.php?t=3817389 )
B. "Magisk-v18.0.zip"
(Downloaded from http://forum.xda-developers.com/showthread.php?t=3473445 )
C. (optional) "\stock\boot.img"
(Downloaded from the global firmware @ 4pda)
If you chose to use Micro SD card, you can insert it now.
Note: I know there is a way to push these files directly to TWRP from PC through USB instead of using SD Card/Flash drive but I've never tried it.
Lets start:
1. Go to 'Settings>About phone' and tap on "Lenovo version" several times until developer options are enabled.
2. Go to 'Settings>System>Developer options' and enable "OEM unlocking" (Note: for me this option was greyed out and I had to connect to wifi and wait for a minute or two).
Optional: Enable "USB debugging" if you wish to enter fastboot via ADB.
3. Turn off the phone and press and hold 'Volume down'+'Power' buttons until you see "fastboot mode" on the phone screen (alternatively, don't turn off the phone and instead enter fastboot mode via ADB (adb.exe reboot bootloader)).
4. Connect the phone to the PC via USB and open a command prompt in the location that you installed fastboot binary to.
Type (after each command press enter):
Code:
fastboot devices
To verify that the phone is recognized. And if it is type:
Code:
fastboot oem unlock
Now on the phone LCD navigate to "Yes" with volume buttons and press power to select it.
Your phone will factory reset, this will take a few minutes. Let it finish.
5. Put the TWRP image in your fastboot path. I used "recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img" downloaded from this URL:
https://forum.xda-developers.com/android/development/lenovo-s5-k520-twrps-t3863860
But I included 2 more files that I found (I did not try them).
6. Enter fasboot mode again and type:
Code:
fastboot flash recovery recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img
(Substitute "recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img" with the recovery filename of you choice)
7. If successful, disconnect the USB cable and enter Recovery mode, do not turn off or reboot the phone because upon restart the phone will revert to stock recovery (I.E. delete TWRP).
To enter Recovery mode press and hold 'Volume down'+'Power' buttons until you see "fastboot mode" and from there choose "Recovery mode" with the volume buttons and confirm with the power button.
(Alternatively, you can try holding 'Volume up'+'Power' to directly enter Recovery mode but I found it a little finicky)
8. In TWRP, swipe to allow changes. Press cancel when asked for a password to decrypt data.
If you chose to use a USB flash drive with an OTG adapter, connect it and mount it (Mount>usb-otg).
9. Go to Wipe>format data, type "yes" and confirm (if you have any data like installed apps, contacts etc., it will be deleted).
10. Go to Install and install "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip".
The files will be in (/external_sd/ or /usb-otg/).
11. Install "Magisk-v18.0.zip"
Important note: If you want to keep encryption (if you don't care if TWRP can't access /data/) and just obtain root, skip steps 9 and 10.
12. Reboot to system and wait for a few minutes for the initial setup.
If for some reason boot fails (nothing happens after 10 minutes) and you can still enter TWRP (hold 'Volume up'+'Power'), then you can revert the changes by restoring the stock boot image (TWRP>Install>Install image>boot.img - put a checkmark on "boot").
If this worked for you, please tell us by replying to this thread.
Thanks a lot man. This phone is a beast in quality/price when talking about hardware. Costs a bit more than 100€ and has the same hard than others at 180-200€ at least. Bad thing is software but with TWRP and root everything is possible . Just found what project treble is, amazing possibilities. Can't beliebe nobody replied yet to yor post. Its a great guide and you show all the sources from where your downloads come. As you said in another thread its better this way so people can trust your content more:
C4lculated said:
I also wanted to root but I didn't want to run a bunch of unknown programs (from XN Logos), so I managed to install TWRP and root with magisk. I wrote a guide on how to do it:
https://forum.xda-developers.com/ge...ide-lenovo-s5-k520-twrp-root-decrypt-t3882402
Click to expand...
Click to collapse
I am yet waiting for my Lenovo S5 to arrive but I will give this guide a try. I was about to follow XN logos (stupdroid) guide/software but I prefer yours. Just one question... have you checked whether the TWRP v3.2.3 (latest) from dmilz make proper working backups? Can I trust that a full backup will be loaded correctly after installing any unofficial ROM, to go back to stock if necessary? I made once the mistake of relying a TWRP and later I found out that one was ok for flashing but didn't create working backups. I asked him also the same question, but I guess you also tried yourself to make a backup and restore from it using TWRP.
Next step will be to flash an Android 8.1 or 9 GSI rom (did I already say I'm amazed by GSI/project treble roms? just found about them last days). I will update you about my luck following your guide
does anyone enable lte bands, 4 and 28?
just bought this phone, currently on shipping..
I'll first try with twrp + aosp 9 GSI
Hi man, have you upgrade to gsi
acost91 said:
Thanks a lot man. This phone is a beast in quality/price when talking about hardware. Costs a bit more than 100€ and has the same hard than others at 180-200€ at least. Bad thing is software but with TWRP and root everything is possible . Just found what project treble is, amazing possibilities. Can't beliebe nobody replied yet to yor post. Its a great guide and you show all the sources from where your downloads come. As you said in another thread its better this way so people can trust your content more:
I am yet waiting for my Lenovo S5 to arrive but I will give this guide a try. I was about to follow XN logos (stupdroid) guide/software but I prefer yours. Just one question... have you checked whether the TWRP v3.2.3 (latest) from dmilz make proper working backups? Can I trust that a full backup will be loaded correctly after installing any unofficial ROM, to go back to stock if necessary? I made once the mistake of relying a TWRP and later I found out that one was ok for flashing but didn't create working backups. I asked him also the same question, but I guess you also tried yourself to make a backup and restore from it using TWRP.
Next step will be to flash an Android 8.1 or 9 GSI rom (did I already say I'm amazed by GSI/project treble roms? just found about them last days). I will update you about my luck following your guide
Click to expand...
Click to collapse
Kindly drop the procedure am hitting brick with all the method i used .????????
Stock firmware lenovo k520
I have tried your method on ROM that is based on China and also globally, and TWRP was successfully installed, and I have also tried several Rom GSI, and only AOSP Extended is successful, but with Bluetooth bugs it cannot be turned on, if others want flash files and stock firmware for k520, just let me know, thanks.
Working on S5 Pro too?
Hi! Can it work on S5 Pro too? I really want to root this device and I don't find out a way to get this happening. Thanks!
Does this work for s5 pro l58041?
Thanks
B4ph0 said:
I have tried your method on ROM that is based on China and also globally, and TWRP was successfully installed, and I have also tried several Rom GSI, and only AOSP Extended is successful, but with Bluetooth bugs it cannot be turned on, if others want flash files and stock firmware for k520, just let me know, thanks.
Click to expand...
Click to collapse
Hi! Sorry for offtopic!
Could you please PM me the link on AOSP extended image which you installed. Thank you!
Hello! Did somebody managed to install GCAM to Lenovo S5? I'm trying and I can;t do this, magisk modules are not loading...
so far I've used 2 alternative rom and works fine, aosp & octopus os, especially octopus os
I need some help..
Did anyone had lenovo s5 persist.img..
I lost my persist afer flashing global rom.208st via qfil..
I check the rom has no persist.img
Please visit to https://youtu.be/wbpV59kutJM for tutorial flash and upgrade Lenovo S5 in YouTube
hello guys, i always get into download mode,after press reboot system (twrp), any solution for my problem ?
has anyone achieved unlocking bands in this phone?
Please port miui 11 9.10.30 mi-room pie 9.0 redmi note 4x SD625 to lenovo S5.
https://megaroms.net/miui-11-9-10-30-stable-port-for-redmi-note-4-4x/
https://sourceforge.net/projects/miui-ports.whats-new.p/files/mido/miroom/
After unlocking bootloader, is there anyway to remove the hideous "software can't check for corruption" warning? Thanks.
---------- Post added at 01:44 AM ---------- Previous post was at 01:39 AM ----------
Suryo75 said:
hello guys, i always get into download mode,after press reboot system (twrp), any solution for my problem ?
Click to expand...
Click to collapse
This means no rom is installed in your phone. Either you accidentally wipe system in twrp, or the rom is corrupted.
Download the deodexed stock rom below and flash with twrp. Should fix your problem.
https://drive.google.com/open?id=13tRqo5eSpRiVJwKiA-iSj2GyIF353ATQ
jychung93 said:
After unlocking bootloader, is there anyway to remove the hideous "software can't check for corruption" warning? Thanks.
---------- Post added at 01:44 AM ---------- Previous post was at 01:39 AM ----------
This means no rom is installed in your phone. Either you accidentally wipe system in twrp, or the rom is corrupted.
Download the deodexed stock rom below and flash with twrp. Should fix your problem.
https://drive.google.com/open?id=13tRqo5eSpRiVJwKiA-iSj2GyIF353ATQ
Click to expand...
Click to collapse
thank you i'll try
Could you plz make tutorial about getting back to stock unroot...thx
Twrp gone
Hello sir thank you for this wonderful tutorial,
But I have a problem , after booting to TWRP , then boot to system after that when I try to go back to recovery mode TWRP , twrp is gone , stock recovery back