Code:
[B]NOTE : [/B]PROCEED AT YOUR OWN RISK. Guide tested successfully to flash [U]Stock WW-15.2016.1810.334[/U] on primary device. Also I will try to help out in case of issues.
This GUIDE is useful to achieve following,
Unbrick your device
Flash Stock Rom
Remove TWRP / flash stock recovery
Lock the bootloader
Enable OTA ( if you have unlocked using Asus official bootloader unlock tool then you will not get OTA )
Files Needed are,
Fastboot Firmware :
WW-15.2016.1810.334 AFH (md5 : fd39c734cbe2722c0cea02f09cba528e) OR
WW-15.2016.1810.337 AndroidHost (md5 : 84197c90f2c913f5cd18dd06b9d82c4b)
Updates : Latest Update (Optional for all, mandatory only if you have UNLOCKED officially)
Steps to be followed,
Charge your device to more than 50%.
Remove all password protections - select SWIPE to unlock.
Create a new folder which does not have any spaces in folder name as well as folder path.
Download Fastboot Firmware and Drivers to above folder & extract both zips which will give you 2 new folders .. one for each.
Connect device to Computer and Install drivers based on your system. [ General process, go to windows Device manager --> Select Android device --> right click and select update driver --> browse to base path where the drivers are extracted and select it .. wait for windows to finish and show success message. ]
Enable USB debugging. Connect device to PC and open shell in ADB. Type adb devices it should list your phone.
You should be able to see results just like below before you proceed,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Boot into fastboot mode & connect to PC. [ For fastboot mode, turn the device off then Press power+Volume Up until you see Asus logo OR use command adb reboot bootloader as shown in above screenshot. ]
Open firmware folder and click on flashall_AFT.cmd & wait for the device to restart on its own. Takes about 5 min so be patient.
Setup your device.
You will have System update notification after that. Install OTA and enjoy.
ALTERNATE
You can download the recovery firmware from above links and put it in Internal Storage (DO NOT keep it inside any folder.).
You will get system update file detected message. Click on it to update.
If you want to uninstall few of the stock apps without ROOT access then refer to my other post HERE.
.A.V.i.n.a.S.h. said:
This GUIDE is useful to achieve following,
Unbrick your device
Flash Stock Rom
Remove TWRP / flash stock recovery
Lock the bootloader
Enable OTA ( if you have unlocked using Asus official bootloader unlock tool then you will not get OTA )
Downgrade firmware
Applicable for,
Model : ZB601KL (try on ZB602KL on your own risk)
ROM : Does not matter - Stock or Custom (AEX,Lineage etc.)
Recovery: Stock / TWRP
Bootloader State : Locked / Unlocked
Root : Rooted / Non-rooted users
Files Needed are,
Firmware : Uploading on AFH. At 73% right now so be patient
Drivers : Windows Drivers AFH
Prerequisites,
Make backup of all your apps and data. Internal Storage will be formatted. External will be safe but better to back it up as well.
Make a mind to take full responsibility of your actions. I have tested the solution on my personal device which was UNOFFICIALLY unlocked. But the risk is entirely yours if you follow the guide.
Make sure you validate checksum of all downloaded files before proceeding.
Steps to be followed,
Charge your device to more than 50%.
Download Firmware and Drivers & extract both zips which will give you 2 folders .. one for each.
Boot into fastboot mode & connect to PC. [ For fastboot mode, turn the device off then Press power+Volume Up until you see Asus logo. ]
Install drivers based on your system. [ General process, go to windows Device manager --> Select device --> right click and select update driver --> browse to base path where the drivers are extracted and select it .. wait for windows to finish and show success message. ]
Open firmware folder and click on flashall_AFT.bat & wait for the device to restart on its own. Takes about 5 min so be patient.
Setup your device. You will have System update notification after that. Install OTA and enjoy.
If you want to uninstall few of the stock apps without ROOT access then refer to my other post here.
Follow the spirit of XDA and hit THANKS if this actually helps you, so that future users also know that the method works.
Click to expand...
Click to collapse
U mean after flashing, the device bootloader gets locked again assuming it was unlocked initially (unofficially) ??
jide1 said:
U mean after flashing, the device bootloader gets locked again assuming it was unlocked initially (unofficially) ??
Click to expand...
Click to collapse
Yes .. you will have stock ROM + stock Recovery + Locked device + OTA ( if unlocked unofficially)
Not working on new firmware kindly see my other post for relocking bootloader. I have also replied to you.
---------- Post added at 11:59 AM ---------- Previous post was at 11:58 AM ----------
i am going to create a detail process guide soon.
myapky said:
Not working on new firmware kindly see my other post for relocking bootloader. I have also replied to you.
---------- Post added at 11:59 AM ---------- Previous post was at 11:58 AM ----------
i am going to create a detail process guide soon.
Click to expand...
Click to collapse
I was on OPM1.WW_Phone-14.2016.1804.305-20180521 then unlocked bootloader unofficially. Installed AEX rom. Tested it for 4 days.
Reverted with this method to 247 and updated again to 305. So it works on latest formware.
And if you do a compare of flashall_AFT.bat and unlock.bat (or relock.bat) the commands are one and the same. Partial code of flashall_AFT.bat is used for lock/unlock process. flashall_AFT.bat just have additional commnds to reflash recovery, system and other partitions.
Please create the guide .. at last we want a working process to revert back.
User will have success with at least one of the process
MY PROCESS WORK 100% FOR RELOCK BOOTLOADER TESTED !!
CURRENT FIRMWARE : OPM1.WW_Phone-14.2016.1804.305-20180521
AFTER UNLOCK BOOTLOADER DO THE FOLLOWING :
ASUS DRIVERS : FROM HERE https://androidfilehost.com/?fid=818222786056030820
FIRMWARE : DOWNLOAD CSC FACTORY IMAGE FROM HERE https://androidfilehost.com/?fid=962339331458995708. ZB610KL INDIAN VERSION.
EXTRACT THE ZIP FILE
AND EXTRACT RECOVERY.IMG FILE -(52MB) APPROX. ( FOR RECEIVING OTA)
FLASH IT WITH COMMAND : fastboot flash recovery recovery.img
1) Download Zenfone_Max_M1_Pro_Relock.zip and extract it to a folder on your desktop.
2) Power off your phone. Then press Power and Volume + key together, to boot into fastboot mode.
3) Connect your Asus Zenfone Max Pro M1 to the PC using a USB cable.
4) Windows will now automatically detect the device and start installing the fastboot drivers for it. If not, download and install these ASUS drivers.
5) Open the directory where you extracted the file from #1.
6) In that directory, open a file named relock_bl.cmd
7) A Command (CMD) prompt will do the rest of the work for you.
Let the phone restart.
8) It will then erase all the data on your phone (excluding Micro SD card).
9) Now the phone won’t show the “bootloader unlocked” warning that was displayed before you relocked the bootloader.
You have successfully relocked the bootloader.
REMEMBER : LOCKED BOOTLOADER SHOWS = CSC FASTBOOT MODE ( TO VERIFY IF LOCKED OR NOT)
UNLOCKED BOOTLOADER SHOWS = FASTBOOT MODE AND WARNING WHILE BOOTING THE PHONE
---------- Post added at 12:42 PM ---------- Previous post was at 12:41 PM ----------
.A.V.i.n.a.S.h. said:
I was on OPM1.WW_Phone-14.2016.1804.305-20180521 then unlocked bootloader unofficially. Installed AEX rom. Tested it for 4 days.
Reverted with this method to 247 and updated again to 305. So it works on latest formware.
And if you do a compare of flashall_AFT.bat and unlock.bat (or relock.bat) the commands are one and the same. Partial code of flashall_AFT.bat is used for lock/unlock process. flashall_AFT.bat just have additional commnds to reflash recovery, system and other partitions.
Please create the guide .. at last we want a working process to revert back.
User will have success with at least one of the process
Click to expand...
Click to collapse
I get your process, first downgrade then upgrade to latest firmware, by this stock recovery is installed with bootloader locked. then update to latest firmware, but this process doesnt work on some phone as mine another guide i have posted it works and easy method if anyone knows about adb and fastboot.
How to know our device is ZB601/ZB602 ?
Greetings
gusbalaa said:
How to know our device is ZB601/ZB602 ?
Greetings
Click to expand...
Click to collapse
ASUS ZENFONE MAX PRO M1 - INDIAN VERSION IS ZB601KL ( PURCHASED FROM FLIPKART ) -ALL PURCHASED IN INDIA WITH VALID INDIAN BILL FOR WARRANTY.
ASUS ZENFONE MAX PRO M1 - INDONESIAN VERSION / GLOBAL VERSION IS ZB602KL (INTERNATIONAL WARRANTY)
REFER BELOW LINKS :
INDIAN SUPPORT SITE ASUS :https://www.asus.com/in/Phone/ZenFone-Max-Pro-ZB601KL/HelpDesk_Download/
INDONESIAN / GLOBAL SUPPORT SITE ASUS : https://www.asus.com/Phone/ZenFone-Max-Pro-ZB602KL/HelpDesk_BIOS/
---------- Post added at 06:03 PM ---------- Previous post was at 05:46 PM ----------
CHECK BOOTLOADER LOCKED OR NOT VIA ADB FASTBOOT METHOD (CMD) AND ALSO CHECK DEVICE & BOOTLOADER VERSION
IN FASTBOOT TYPE :
fastboot devices
fastboot oem device-info
RESULTS : AFTER LOCKED BOOTLOADER
#SN NUMBER fastboot
VERIFY MODE - TRUE
DEVICE UNLOCKED - FALSE (BL LOCKED), TRUE (BL UNLOCKED)
DEVICE CRITICAL UNLOCKED - FALSE (BL LOCKED), TRUE (BL UNLOCKED)
CHARGER SCREEN ENABLED - TRUE
BOOTLOADER VERSION - ZB601KL (INDIAN VERSION) -0x01
OKAY
FINISHED
myapky said:
ASUS ZENFONE MAX PRO M1 - INDIAN VERSION IS ZB601KL ( PURCHASED FROM FLIPKART ) -ALL PURCHASED IN INDIA WITH VALID INDIAN BILL FOR WARRANTY.
ASUS ZENFONE MAX PRO M1 - INDONESIAN VERSION / GLOBAL VERSION IS ZB602KL (INTERNATIONAL WARRANTY)
REFER BELOW LINKS :
INDIAN SUPPORT SITE ASUS :https://www.asus.com/in/Phone/ZenFone-Max-Pro-ZB601KL/HelpDesk_Download/
INDONESIAN / GLOBAL SUPPORT SITE ASUS : https://www.asus.com/Phone/ZenFone-Max-Pro-ZB602KL/HelpDesk_BIOS/
---------- Post added at 06:03 PM ---------- Previous post was at 05:46 PM ----------
CHECK BOOTLOADER LOCKED OR NOT VIA ADB FASTBOOT METHOD (CMD) AND ALSO CHECK DEVICE & BOOTLOADER VERSION
IN FASTBOOT TYPE :
fastboot devices
fastboot oem device-info
RESULTS : AFTER LOCKED BOOTLOADER
#SN NUMBER fastboot
VERIFY MODE - TRUE
DEVICE UNLOCKED - FALSE (BL LOCKED), TRUE (BL UNLOCKED)
DEVICE CRITICAL UNLOCKED - FALSE (BL LOCKED), TRUE (BL UNLOCKED)
CHARGER SCREEN ENABLED - TRUE
BOOTLOADER VERSION - ZB601KL (INDIAN VERSION) -0x01
OKAY
FINISHED
Click to expand...
Click to collapse
Thanks. I have Indonesian version.
Got it
Will these methods work with official Unlocking also?
Thank you
atf2m4 said:
will these methods work with official unlocking also?
Thank you
Click to expand...
Click to collapse
not tested,
but better to use unofficial method to unlock as : If u unlock through official method service support team, they have a count of imei & serial number (record) of ur phone which is unlocked , so u might lose warranty by using official method so better to try unofficial method.
Check your version via ADB
gusbalaa said:
How to know our device is ZB601/ZB602 ?
Greetings
Click to expand...
Click to collapse
Enable USB debugging
connect to PC and type "adb devices" -- you will get ID from here
Type adb -s <id from last step> shell getprop | grep ro.product.device
.A.V.i.n.a.S.h. said:
Enable USB debugging
connect to PC and type "adb devices" -- you will get ID from here
Type adb -s <id from last step> shell getprop | grep ro.product.device
Click to expand...
Click to collapse
Thanks, i will try and report later.
I have a few questions
1.Will it remove the bootloader unlocked warning during boot
2.Can we do this step over a newer version of stock rom
3.do we have to unroot before flashing
4.ZB601KL is indian version or Indonesian
pranavsree00 said:
I have a few questions
1.Will it remove the bootloader unlocked warning during boot
2.Can we do this step over a newer version of stock rom
3.do we have to unroot before flashing
4.ZB601KL is indian version or Indonesian
Click to expand...
Click to collapse
Yes
I did it today on v305 so yes .. it works .. just remember to enable usb debugging & check device is detected in ADB & fastboot as well.
Commands to check device -
adb devices
fastboot devices
Not needed but you can if you feel like it.
601 is INDIAN.
Flashed and flashed successfully great guide ?
not working. getting this messege
Begin fastboot flashall
------------------------
Earse Data: Yes
Support All device
FINDSTR: Cannot open max
FINDSTR: Cannot open pro
FINDSTR: Cannot open m1\WW_ZB601KL_14.2016.1802.247_20180419_AFT\\platform.txt
FINDSTR: Cannot open max
FINDSTR: Cannot open pro
FINDSTR: Cannot open m1\WW_ZB601KL_14.2016.1802.247_20180419_AFT\\current-slot.txt
himanshu_atrix2 said:
not working. getting this messege
Begin fastboot flashall
------------------------
Earse Data: Yes
Support All device
FINDSTR: Cannot open max
FINDSTR: Cannot open pro
FINDSTR: Cannot open m1\WW_ZB601KL_14.2016.1802.247_20180419_AFT\\platform.txt
FINDSTR: Cannot open max
FINDSTR: Cannot open pro
FINDSTR: Cannot open m1\WW_ZB601KL_14.2016.1802.247_20180419_AFT\\current-slot.txt
Click to expand...
Click to collapse
Please keep the files in the path which does not have spaces.
If you have a folder named max pro m1 then rename it to MaxProM1.
Also before clicking on flashall_AFT.bat check that device is detected in fastboot mode by fastboot devices command.
I think the command line arguments are not working due to whitespaces in directory/folder name.
latest indian ota WW-14.2016.1804.305 showing error
rs
sir
i unlocked bootloader official and after two day get back to stock rom because i unlocked it official i got not ota updates but i flash update manually one ota is (WW-14.2016.1804.252)sucessfully update, one which is latest(WW-14.2016.1804.305) is showing error on the time while phone reboot to flast update Also The latest update file is not extract on pc
??
???
.A.V.i.n.a.S.h. said:
Please keep the files in the path which does not have spaces.
If you have a folder named max pro m1 then rename it to MaxProM1.
Also before clicking on flashall_AFT.bat check that device is detected in fastboot mode by fastboot devices command.
I think the command line arguments are not working due to whitespaces in directory/folder name.
Click to expand...
Click to collapse
thanks. did what you said. it started but stuck here
Begin fastboot flashall
------------------------
Earse Data: Yes
Support All device
current-slot is current-slot
buildtype is build-type
--------------------------------
begin to flash partition xbl
target didn't report max-download-size
sending 'xbl' (2802 KB)...
FAILED (remote: unknown command)
finished. total time: 0.002s
done
--------------------------------
--------------------------------
begin to flash partition xblbak
target didn't report max-download-size
sending 'xblbak' (2802 KB)...
Related
----------------------------------------------------
I'm kinda busy at my life and won't be able to answer your questions...you can still ask here and hope someone else will reply, or post at the other similar thread - MEGA-THREAD ALE-L21, ALE-L23, ALE-L02, Converting, Root, Unbrick, Updating, Xposed
----------------------------------------------------
Debranding is easy once you find infos how to do it...sadly there's nothing in english. I used a combination of Google Translate + some spanish/italian/polish sites and howto's for other Huawei models to convert my branded single sim ALE-L21 from C150B130 to dual sim C432B188.
Here's how i did it...proceed at your own risk. Don't forget to make a backup because you'll lose your data. Also, your warranty will be void.
Please look at the Q&A section at end of the post; feel free to ask me if something isn't answered, but be prepared for an answer like "flash it again" because that's my first Huawei phone and i own it just for a week...i'm more of a Google Nexus guy.
----------------------------------------------------
Part 1: Unlocking bootloader
Stuff you'll need:
- Model number inside "Settings > About phone"
- Serial number inside "Settings > About phone > Status"
- IMEI inside "Settings > About phone > Status" (write down the first one if you have two of them)
- Product ID by opening dialer and typing *#*#1357946#*#*
- "Updated Step by Step guide to Root P8 lite.pdf" file - http://forum.xda-developers.com/p8lite/general/step-step-guide-to-unlock-bootloader-t3150616
- Minimal ADB and Fastboot from unlocking bootloader pdf
First you'll need to get your bootloader unlocking code:
1. Go to http://emui.huawei.com/en/plugin.php?id=hwdownload&mod=list and click "Unlock Bootloader"
2. Register a Huawei ID account, repeat step 1, login and click "Unlock Bootloader" again; accept the terms and click Next
3. Enter your phone data and Press Submit; wait a little for the code to show up and save it somewhere safe in case you'll need it someday
Then you'll need to unlock your bootloader:
1. Open "Updated Step by Step guide to Root P8 lite.pdf" and do just step B
Like i said many times in replies/pm's - if you didn't do anything of this, your bootloader is still locked. Doesn't matter if it says unlocked.
-----------------------------------------
Want to go back from 6.0 to 5.01? Read Q&A first, there's a special procedure for that. If you do it directly, you'll lose your imei!
Part 2: Flashing the unbranded firmware
Stuff you'll need:
- Minimal ADB and Fastboot from last part
- C432B132 Europe dual sim firmware - http://carbontesla.com/2015/09/download-huawei-p8-lite-b132-firmware-dual-sim
- Huawei Update Extractor - http://forum.xda-developers.com/showthread.php?t=2433454
First we need to get img files out of Huawei's update.app:
1. Extract the firmware; you should have a folder with dload and CUSTOM
2. Open Huawei Update Extractor as administrator (otherwise you won't be able to extract directly into adb folder), browse (button with two dots) to dload folder from step 1 and open UPDATE.APP
3. Hold Ctrl and select BOOT.IMG, CUST.IMG, RECOVERY.IMG and SYSTEM.IMG; release Ctrl, right click on any marked file, click "Extract Selected" and find your ADB folder (should be "C:\Program Files (x86)\Minimal ADB and Fastboot" or "C:\Program Files\Minimal ADB and Fastboot")
Now the most fun and...ehm...most "dangerous" thing - flashing the files:
1. Do B 2, 3, 4, 5, 6 and 7 from unlocking bootloader pdf file (to boot your phone into fastboot mode and get a cmd window with the right starting location)
2. Type:
Code:
fastboot flash system system.img
press enter and wait until finish...it will take some time
Code:
fastboot flash recovery recovery.img
press enter and wait
Code:
fastboot flash boot boot.img
enter and wait again
Code:
fastboot flash cust cust.img
enter and wait
Code:
fastboot reboot
and enter to reboot your phone
You may think that's the end...let me tell you - it's not. Your phone booted into an ugly version of EMUI with funny icons and "Settings > About phone" Build number says BalongC**B*** instead of the flashed ALE-L21C432B132. Let's fix that.
Fixing balong "bug" - this will cause a factory reset...i hope you made a backup:
1. Remember CUSTOM folder from extracted firmware? Copy it on your phone's internal storage or sdcard
2. Rename CUSTOM to dload
3. Run the Updater app, tap Menu, select "Local update", tap UPDATE.APP and wait until it finishes it's work and reboots
4. Go to "Settings > About phone" and check if it says the right build number (should be ALE-L21C432B132); if it's not, repeat the img file flashing process
-----------------------------------------
DON'T OTA if you're rooted!
Part 3: Getting the latest firmware update (B200) via OTA and (optionally) manually updating to MM B560
a. Getting the latest firmware:
1. Open Updater app, tap Check for updates and install it
2. Repeat step 1 until it says No updates; now you should be on B200
b. Update to MM (6.0):
1. Download C432B560
2. Extract it and copy the dload folder on your phone's internal memory or sd card.
3. Run the Updater app, tap Menu, select "Local update", tap UPDATE.APP and wait until it finishes it's work and reboots.
4. Go to "Settings > About phone" and check if it says the right build number (ALE-L21C432B560)
----------------------------------------------------
Q&A:
Q: I have a ALE-L04 or something else. Can i still do what you wrote?
A: Don't even try because you'll brick your phone. ALE-L04 for example got a totally different chipset (Qualcomm Snapdragon 615) than ALE-L21 (HiSilicon Kirin 620).
Q: What's the difference between ALE-L21 and ALE-L02? Will there be any benefits or disadvantages after changing from L02 to L21?
A: L02 doesn't support some LTE frequencies and NFC; detailed specs: ALE-L02, ALE-L21. There will be no benefits or disadvantages after flashing a L21 rom; everything will be the same, except a different model and build number.
Q: Are there any other uses for this, except for debranding and converting to dual sim?
A: Yes, you can basically use it for everything from upgrading and downgrading firmwares, fixing your bricked phone (if you still can access Fastboot mode) and more.
Q: I don't want dual sim. Why should i flash it?
A: Because why not? You get a bonus functionality and you won't lose anything even if you never intend to use it - you can still use just one sim and a sdcard without any problems. Huawei also planned P8lite to be a dual sim phone, so it's possible you'll get updates faster than people with the single sim variant.
Q: I don't live in Europe. Why should i flash that firmware?
A: Well, you can always find an appropriate firmware on carbontesla website, but be prepared you won't be able to fix the balong bug. Only a few firmware packs include the vendor patch (CUSTOM folder).
Q: Huawei Update Extractor gives me errors why i try to extract img's. What should i do?
A: You didn't listen and didn't run it as administrator. One workaround would be extracting the img's somewhere else (for example new folder on desktop) and then copy/paste them into adb folder. Do as you wish.
Q: I get errors when i type "fastboot flash xxxxx xxxxx.img". What should i do?
A: First look if you typed it correctly, then check if you have the right files - BOOT.IMG, CUST.IMG, SYSTEM.IMG and RECOVERY.IMG (there are multiple RECOVERY files, make sure you get the one without any numbers in it's name) and repeat the command. The last resort would be running "fastboot reboot-bootloader" and retrying the command that gives you errors. By the way - if you can't run fastboot at all, then try opening cmd as administrator. If you used KingRoot, read the next question too.
Q: I unlocked the bootloader via KingRoot and i can't flash anything, help?
A: No, you didn't. Do everything from part 1 and you will be able to flash.
Q: I don't like 6.0, how can i go back to 5.01?
A: Read this. After doing everything it said, repeat part 2 and 3a of this guide to get back on B200.
Q: You broke my phone, i will beat/curse/sue you!
A: Ok, that's not a question. Anyways, not my fault, i said you proceed at your own risk.
Hi,
Thanks for this guide. I've followed it successfully but I need to make a small remark/alert: When correcting the Balong error, the local update caused a factory reset and my data was lost.
Nothing that a local restore can't solve but it might happen to others as well.
Paulo
pmp said:
Hi,
Thanks for this guide. I've followed it successfully but I need to make a small remark/alert: When correcting the Balong error, the local update caused a factory reset and my data was lost.
Nothing that a local restore can't solve but it might happen to others as well.
Paulo
Click to expand...
Click to collapse
Fixing balong "bug":
fixed or no ? please answer
Fixed.
Sent from my ALE-L21 using XDA Free mobile app
please Possible steps to resolve the problem balong "bug"
1. Extract the firmware; you should have a folder with dload and CUSTOM
I do not understand What CUSTOM
Extract the firmware produces a single file dload no custom
please help
pmp said:
Hi,
Thanks for this guide. I've followed it successfully but I need to make a small remark/alert: When correcting the Balong error, the local update caused a factory reset and my data was lost.
Nothing that a local restore can't solve but it might happen to others as well.
Paulo
Click to expand...
Click to collapse
Thanks for your input. I'll put it into first post...better to be safe than sorry.
darklove0 said:
1. Extract the firmware; you should have a folder with dload and CUSTOM
I do not understand What CUSTOM
Extract the firmware produces a single file dload no custom
please help
Click to expand...
Click to collapse
I already replied to your pm and will repeat it here because it will be maybe useful for others too.
Did you download C432B132? When you extract it, there should be something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you downloaded any other version, then it's like i said in Q&A...most of the firmwares don't have the vendor patch (CUSTOM folder).
dennyn said:
I already replied to your pm and will repeat it here because it will be maybe useful for others too.
Did you download C432B132? When you extract it, there should be something like this:
If you downloaded any other version, then it's like i said in Q&A...most of the firmwares don't have the vendor patch (CUSTOM folder).
Click to expand...
Click to collapse
thnx answer
i dawnload Huawei_P8_Lite_ALE-L21_V100R001C432B170_Europe but not folder (CUSTOM or vendor)
i have update for this 6.0
http://forum.xda-developers.com/p8li...allow-t3305550
Can I flash using fastboot a zip containing the dolby atmos app?
rareshutzu said:
Can I flash using fastboot a zip containing the dolby atmos app?
Click to expand...
Click to collapse
No, fastboot can only flash whole partitions. You'll need a custom recovery (twrp) to flash your thing.
dennyn said:
No, fastboot can only flash whole partitions. You'll need a custom recovery (twrp) to flash your thing.
Click to expand...
Click to collapse
I was afraid of that. Thank you for your answer.
Great threads (and for the p8 lite this thread's was the only one )with real instructions, good and easy to understand.
Thanks for the explanation and for the time you have past for sharing this with the p8 comunity .
after enabling dual sim support on the UK variant, I was expecting to see the phone returning two unique IMEI numbers when dialing *#06#. However, it only returned one IMEI. Is this correct? Is there a way to make sure two IMEIs are returned?
ken218 said:
after enabling dual sim support on the UK variant, I was expecting to see the phone returning two unique IMEI numbers when dialing *#06#. However, it only returned one IMEI. Is this correct? Is there a way to make sure two IMEIs are returned?
Click to expand...
Click to collapse
It (always) shows just one imei after converting from single to dualsim. There shouldn't be any problems while using both sims because the phone is "dualsim standby".
Hello, just for help, I have downgrade my two p8 lite from 6.0 to the latest version B190 5.0.1, and I have full wipe and format all (dalvik, cache, system, data, internal storage) with twrp before and like this no need to flash any fix for balong. just B052, B170 and B190 without any trouble.
I did everything like you said but...
My phone does not read the sim card...
How can i soluve this ???
bjkhami said:
I did everything like you said but...
My phone does not read the sim card...
How can i soluve this ???
Click to expand...
Click to collapse
Sim1 or sim2? Anyways, try repeating part 2 with B170 (link is inside Q&A section) and then OTA to B188 because sometimes you lose your baseband when flashing older firmwares and OTA usually fixes it.
FAILED (remote: Command not allowed)
When I try to run the command fastboot flash...... I always get the error "FAILED (remote: Command not allowed)" The phone has bootloader unlocked and appears listed when I enter "fastboot devices". Do you know why could I be receiving this error or what can I do to flash manually using fastboot? I had the phone rooted with KingRoot but I unrooted it back. Any help would be very appreciated.
pelukin said:
When I try to run the command fastboot flash...... I always get the error "FAILED (remote: Command not allowed)" The phone has bootloader unlocked and appears listed when I enter "fastboot devices". Do you know why could I be receiving this error or what can I do to flash manually using fastboot? I had the phone rooted with KingRoot but I unrooted it back. Any help would be very appreciated.
Click to expand...
Click to collapse
Did you run cmd as administrator? Try relocking and unlocking bootloader again, also try a factory reset.
That error usually appears if you try to flash any locked partition...it shouldnt happen with system, recovery, boot and cust. Let's hope you don't have any hardware problems.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
INTRODUCTION
I'm providing a set of files that allow you to unlock your bootloader or recover from the closest thing you can get to a hard brick.
MiFlash is capable of flashing anything to your phone while it is in Emergency Download mode.
Yes, this is voodoo magic and it works! Recover from any and all bricks! Some might call it necromancy.
However, it can be also be used even if the device is perfectly alright to simplify upgrading procedures and make ROM flashing fairly painless.
This is for A2017U (North America) and A2017 (China) models only! Do not attempt this on A2017G.
INSTRUCTIONS
If you are flashing TWRP on a locked bootloader, you must first enable OEM unlocking on your device.
You can do this by navigating to Settings -> About phone -> Tap "Build number" 7 times.
Now navigate to Settings -> Advanced settings -> Developer options -> Enable "OEM unlocking".
Follow the steps below with the FASTBOOT_UNLOCK package first, then go into fastboot mode and use the
"fastboot oem unlock" command to unlock (and wipe) your device. Download adb and fastboot below.
Install the Qualcomm QUSB_BULK drivers from below.
You should be able to simply extract them, then right click qcser.inf and press Install.
If you don't have this option, then use devmgmt.msc (Device Manager) to update the driver after entering EDL mode by
selecting manual install and browsing to the qcser.inf file there.
Once the drivers are installed, your device should be recognized as a COM port called "Qualcomm HS-USB QDLoader 9008".
Now install MiFlash (download below).
Open MiFlash and use the [select] button to select the A2017U_*_EDL folder package that you wish to flash.
Boot into EDL mode. (hold Volume Up + Volume Down + Power until you're stuck on a black screen)
Now just hit [flash] - watch the progress bars move and wait for the device row to turn green with flash complete!
If you are flashing TWRP, use the [Power] + [Volume Up] key combo to exit EDL mode and enter recovery. Release the keys when you see the ZTE logo.
You must have an unlocked bootloader to enter TWRP!
If the flash fails or is unable to communicate with the device, use the [Power] + [Volume Up] + [Volume Down] key combo to restart EDL mode.
Release the keys after 5 seconds then wait another 5 seconds before using the [refresh] or [flash] buttons on MiFlash.
EDL PACKAGES
FASTBOOT_UNLOCK
This will unlock all fastboot operations, including OEM unlock and fastboot boot/flash.
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Click here to download! (ZIP, 195.8 KiB)
B29_TWRP (Marshmallow 6.0)
This will install TWRP 3.0.4-1 and unlock fastboot operations while restoring B29 boot stack.
Click here to download! (ZIP, 59.4 MiB)
B15-NEW_TWRP (Nougat 7.0)
This will install TWRP 3.0.4-1 and unlock fastboot operations while restoring B15-NEW boot stack.
Click here to download! (ZIP, 60.6 MiB)
B15-NEW_FULL (Nougat 7.0)
This will install the entirety of the B15-NEW firmware and boot stack, including signed OEM system and boot. OTA capable and unlocks fastboot operations.
Click here to download! (ZIP, 2.4 GiB)
B19-NOUGAT_TWRP (Nougat 7.1.1)
This will install TWRP 3.0.4-1 and unlock fastboot operations while restoring B19-NOUGAT boot stack.
Click here to download! (ZIP, 61.0 MiB)
B19-NOUGAT_FULL (Nougat 7.1.1)
This will install the entirety of the B19-NOUGAT firmware and boot stack, including signed OEM system and boot. OTA capable and unlocks fastboot operations.
Click here to download! (ZIP, 2.4 GiB)
TOOLS
Xiaomi MiFlash Installer
Version: 2016.08.30.0
Click here to download! (MSI, 31.0 MiB)
Qualcomm QUSB_BULK Drivers
Version: 2.1.1.0 (2014-01-25)
WHQL signed.
Once the drivers are installed, your device should be recognized as a COM port called "Qualcomm HS-USB QDLoader 9008".
Click here to download! (ZIP, 2.7 MiB)
ADB & Fastboot
Visit the SDK Platform Tools download page
Using this, you should safely be able to recover from any brick!
Once in TWRP, you can flash a full OTA or restore your backups and be on your way.
It is tested and working on Windows 10 64-bit.
All zips are signed with Android SignApk and can be verified with TWRP. (they won't install, just say it's not a valid zip after verifying)
A2017 (China) can use this to convert their phone to A2017U if they want. DO NOT flash on A2017G.
POSSIBLE ISSUES & SOLUTIONS
OTA update zips may fail in stock recovery even after flashing FULL EDL packages. This is because MiFlash does not erase blocks before writing the system image. You can run this command from TWRP terminal or adb shell to erase system partition before flashing the EDL package:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/system bs=272144
Once this is done, OTA zips should succeed in stock recovery after flashing a FULL EDL package.
CREDITS
This was based on the A2017 B07 EDL zip provided by @tenfar at this XDA thread.
HISTORY
2017-04-10 - Added B19-NOUGAT FULL and TWRP package
2017-02-11 - Added B15-NEW FULL signed OTA capable package
2017-02-11 - Added fastboot operation unlock package
2017-02-11 - Separated MiFlash, Qualcomm QUSB_BULK Driver, and EDL packages, removed 7z archives
2017-02-09 - Added B15-NEW TWRP package
2017-02-09 - Added B29 TWRP package
Any idea if this will work with Nougat or not?
neo4uo said:
Any idea if this will work with Nougat or not?
Click to expand...
Click to collapse
It will work on Nougat, however, you will end up on B29 bootloader. You'll need to flash B29 full and upgrade again.
I am having some weird issues with Nougat boot stack flashing + TWRP so I'll hold off on posting a B15-NEW version of this for now.
Update: You can now flash the B15-NEW TWRP package instead.
@jcadduono
N BootStack from LineageOS thread can be use for this if you want to give a try, instead of B29.
The stack is from a zip N file (I can't disclose right now) and is full N stack, minus Boot and System of course.
P.S. be advice that " keymaster.mbn " file flashes to " xlbbak " partition. Or just check the updater_script for N changes.
Situation: A2017U full stock in Nougat no unlocked bootloader, no root
Want to: Install LOS because i HATE this bullsh... called MIFAidonotknowWTF
Can i use this procedure to do that?
Thanks a LOT
So basically, MiFlash just lets you firehose in any file to a QualComm device from EDL mode? That's pretty handy.
I assume the TWRP image will only work on an unlocked bootloader device, right?
Then again, I don't see why a locked bootloader device would get in such a bricked state in the first place.
Snaptraks said:
I assume the TWRP image will only work on an unlocked bootloader device, right?
Then again, I don't see why a locked bootloader device would get in such a bricked state in the first place.
Click to expand...
Click to collapse
It is softbrickable by adb commands... I have one device in boot loop.
trying to wrap my head around this whole bootstack/fastboot issue we have with the a7.
So in theory one could use this tool and then unlock (or just have working fastboot) directly from b15?
Then download the bootstack from los thread and be good to go? Or would that bork fastboot again...
I think I am currently running b20 bootstack on b15 by flashing draken's unlock zip without issue (that I know of) but am considering flashing the N version from los thread.
This thing works, guys! OMGOMGOMG! :highfive::laugh:
My device was in a "heavily bricked" state. No LED light on connect and permanent EDL mode. I am now fully functional after trying EVERYTHING but this.
KwesiJnr said:
This thing works, guys! OMGOMGOMG! :highfive::laugh:
My device was in a "heavily bricked" state. No LED light on connect and permanent EDL mode. I am now fully functional after trying EVERYTHING but this.
Click to expand...
Click to collapse
Have fun! Nougat images are now up!
jcadduono said:
Have fun! Nougat images are now up!
Click to expand...
Click to collapse
Can you help me to do this from full stock nougat?
1) Enable "OEM UNLOCKING" under Developer Options
2) Flash with MIflash the "A2017U_B15-NEW_TWRP_EDL"
2) reboot to recovery (vol - and power)
3) fastboot oem unlock
4) reboot to TWRP
5) Flash LineajeOS and Gapps
thanks for your help
Altomugriento said:
Can you help me to do this from full stock nougat?
1) Enable "OEM UNLOCKING" under Developer Options
2) Flash with MIflash the "A2017U_B15-NEW_TWRP_EDL"
2) reboot to recovery (vol - and power)
3) fastboot oem unlock
4) reboot to TWRP
5) Flash LineajeOS and Gapps
thanks for your help
Click to expand...
Click to collapse
step 2.5) reboot to bootloader from recovery
step 4) wipe system in twrp
step 6) use the [Format Data] button on wipe page of twrp (lineageOS may not be compatible with your current encryption, this will wipe all your settings and internal storage)
and yes that's everything, I believe.
Sticky. Nuff said.
Dev is finally taking off on this phone, thanks to literally 4 or 5 key people. I was afraid I'd made a mistake purchasing instead of O+3, but has worked out well.
Thanks for all your help in your free time.
DrakenFX said:
@jcadduono
N BootStack from LineageOS thread can be use for this if you want to give a try, instead of B29.
The stack is from a zip N file (I can't disclose right now) and is full N stack, minus Boot and System of course.
P.S. be advice that " keymaster.mbn " file flashes to " xlbbak " partition. Or just check the updater_script for N changes.
Click to expand...
Click to collapse
Thanks buddy, that keymaster -> xblbak appears to have been my issue! So illogical.
I compiled applypatch and used that to apply the B29_TO_B15-NEW .p files to my B29 binaries so they should be nice and exact. (sha1 matches from updater-script)
I can provide a full B15-NEW verity/OTA update friendly package if somebody wants. Just let me know.
Flash Done.
But i can't join to TWRP, it just turn it self off.
Eroticus said:
Flash Done.
But i can't join to TWRP, it just turn it self off.
Click to expand...
Click to collapse
If you are not unlocked you now need to go to fastboot mode and unlock before you can enter TWRP.
If you just mean the screen is still black, you have to hold volume + power up after flashing until it starts up, then let go when you see the ZTE logo.
Hi @jcadduono
I'm about to get my A7 (A2017U version) in few days. Would you please advise which method/process/steps is the best to upgrade to stock, rooted and fastboot working N B15 build?
Thanks
khangozzy said:
Hi @jcadduono
I'm about to get my A7 (A2017U version) in few days. Would you please advise which method/process/steps is the best to upgrade to stock and rooted N B15 build?
Thanks
Click to expand...
Click to collapse
Look up a couple posts.
jcadduono said:
Have fun! Nougat images are now up!
Click to expand...
Click to collapse
Because it had been reported that this was impossible, or at least very difficult, I wanted to clarify whether this means people with locked bootloader running N can now unlock and install TWRP?
[How To Root]
[2017 Family] Huawei/ Honor series PRA (Prague)
-Android 7.0 -EMUI 5.0
P8 Lite 2017 - PRA-LX1, LX2, LX3, LA-1
P9 Lite 20176
NovaLite
Honor 8 Youth
Rooting has been developed and tested on this device:
Huawei P8 lite 2017 [PRAGUE]
Model number: PRA-LX1
Build number: PRA-LX1C432B170
Free device
You need:
- PC or Windows tablet
- USB cable
- Windows 7 / 8.1 / 10
- Minimal Adb and Fastboot
- OEM unlocking in the developer options active
- Huawei HiSuite (installs all necessary drivers)
OEM and FRP unlocked
Bootloader unlocking:
- Go to this page: Homepage - EMUI - on UNLOCK (Currently offline.),
- then on Account login - and log in with the Huawei ID.
- Then confirm the terms and conditions.
- On the next page, fill in the form. This page is self-explanatory.
- Confirm your entries with "Commit". The unlock code is now displayed immediately.
- Please note down immediately.
- Now start the PRA in fastboot mode and enter fastboot oem unlock in the Adb command window (PC)
- followed by your unlock code. (like this: fastboot oem unlock 123456787890987654)
- Now comes a hint screen, in which the unlocking is pointed out.
- You now have the option to cancel this action. If you confirm with yes, it will be unlocked and a
- Factoryreset will be performed.
FRP - Unlocking:
- After the reboot has just been executed, the device starts the new setup.
- Reject or skip anything related to security and Google. Can be made up later.
- After setup, turn on OEM unlock and USB debugging in the developer settings and boot back into Fastboot mode.
- It should be there now: FRP Unlock
Rooting:
The following is required:
TWRP recovery (prague311.img)
-in the ADB directory
SuperSU2.82-EMUI5-dm-verityPermissive.zip
(By @Tecalote)
-to the Ext Sd
Backup your data using Huawei Backup.
Please enter only flash commands by using Adb.
Reboots only by keyboard combination.
Installing TWRP:
Connect the device via USB to the PC and start into the boot loader
(Fastboot Mode):
Now start adb on the PC and enter it in the terminal:
fastboot flash recovery prague311.img
Disconnect device from PC and start TWRP: Press Vol + and Power and hold both.
When signs or logo appears on the screen, release the buttons.
After a few seconds TWRP starts.
There the SuperSU2.82-EMUI5-dm-verityPermissive.zip flash
and reboot.
The device starts twice before it finally boots.
Then load from the Playstore the Busybox.apk from Stericson
and thus install Busybox into this path:
/ Su / Xbin
In the future:
All actions in TWRP must be executed wisely.
Learn about the features of this custom recovery.
Note:
The data partition is mountable in TWRP,
but is not reliably secured or restored.
Therefore, never delete the internal memory and data partition,
or perform a factory reset. I have had the experience that too.
Other partition backups will never be restored as they are
were created. A perfect restoring is not possible.
Please do not use TWRP for backup and restore operations.
If a backup or restore should be done, please always without the data partition.
Apply a factory reset only in stock recovery.
This can be done with a regular backup per Huawei data backup.
Button combinations:
Fastboot Mode: Vol.- and Power with PC connection
Recovery: Vol. + and Power without PC connection
eRecovery: Vol. + and Power with PC connection
All system reboots always without PC connection.
Without PC connection means that the cable from the PRA
is separated, only from the PC is not sufficient.
I wish you success!
Root the PRA is now also available with the Magisk-v13./16.
Requirement:
- Firmware from the B164
- not root
Who has already rooted with SuperSu, lets
everything as it is.
Magisk Rooting:
- Install MagiskManager-v5.3.0.apk
- flash Magisk-v14.0.zip by TWRP
- flash BusyBox-Magisk-1.25.zip by TWRP
- reboot and update the MagiskManager.
For this we thank the Magisk developer
@topjohnwu.
[How to unbrick]
The procedure of rescue is risky.
Without appropriate knowledge, I advise.
It is only successful if the instructions are executed exactly.
This TWRP backup rom is not suitable for normal use. It was created for the following purpose:
- Rescue of bricked phones.
- Force an OTA update.
Do not root this rom!
Unzip the download 2017-08-11-RESCUE.ROM.PRA.OTA.B164.to.170.rar (1.05 GB).
This creates the TWRP backup:
2017-08-11-RESCUE.ROM.PRA.OTA.B164.to.170
installation:
copy my backup to the TWRP backup path to the Ext Sd.
(see screenshot)
Boot into the Bootloader.
Stock Recovery flash by adb.
In the recovery start and
perform a factory reset.
Boot into the Bootloader.
TWRP flash by adb.
To start TWRP.
There data wipe
and restore my backup.
In the Bootloader start and
flash by adb the Stock Recovery.
There then again a factory reset.
Reboot
When the boot process is finished,
Go to Settings> Update program> New version> Update.
Will not be offered, in the Stock Recovery again perform a factory reset.
The upgrade to the B170 succeeds only with sim-card.
You have now done an official update and a new, clean and up-to-date firmware.
Congratulation!
Thread Update: 2017-11-10
There is also an alternative method. This can work, but it doesn't have to.
Starts the device into eRecovery and tries to recover and download the firmware.
If you had the B170, this one will also be sent to you here offered.
If it works, then immediately starts the download and installation.
Thread update: 2017-12-09
[Rooting B182]
With SuperUser:
After the update to the B182
surely TWRP already flashed
and created a backup.
Now installed in TWRP, on the Stock Kernel,
the "SuperSU-v2.82. PRA. B182. zip"
from the appendix.
Reboot and ready.
You can use the Busybox from the App
suggested path.
With Magisk:
As described above.
Nothing's changed.
Threadupdate: 2017-12-30
Here's the new rescue rom:
https://forum.xda-developers.com/p8...ck-rom-huawei-prague-pra-xxxc432b182-t3727816
Threadupdate: 2018-01-04
Here I have a new possibility to restore a bricked device:
It's an original Huawei UPDATE.APP.
It is designed for emergencies to repair damaged firmware.
However, some functions are limited until the next OTA Update.
The Magazine-Unlocking does not work and other themes cannot be activated.
TWRP backup and restore are faulty and can lead to a brick.
Don't use dual recovery here. eRecovery is mandatory.
After downloading the UPDATE. ZIP you unpack the archive.
Now create the folder dload on the ExtSd
and copies the resulting UPDATE.APP there.
Now in the dialer with the input of *#*#2846579#*#*
call up the secret menu and perform the update. If you can't boot anymore, you start
the update as follows, without USB connection:
Vol. + and vol. - and power and press together and hold on tight. The device goes off and on again.
As soon as text appears on the display, release all keys. Now start after the update process within a few seconds.
After this update the firmware should be repaired.
TWRP and root do not need to be removed as they are overwritten during the update.
The FRP is then locked again.
After the first reboot go to recovery and make a factoryreset and reboot again.
Now disable in the developer options the oem unlocking und your device is full stock wihout the bootscreen: "your device has been unlocked and can't be trusted". If you need twrp and root again, unlock with the huawei unlockcode.
Good luck.
And now we install the OREO-Beta:
Download:
LX1C432B321-PRA log (8.0.0.321)
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2312/g1699/v130567/f1/full/update.zip
Instructions:
The UPDATE.ZIP from the download, nocheck.img and Magisk-v16.0.zip copy to the extSd card.
Perform a HW backup
Sync your Google Account.
Write down Google Login data.
Enable OEM unlocking and USB debugging.
Perform a factoryreset. (Stock Recovery)
Now carry out a short new setup.
Reject everything for security and google, or skip it.
Can be made up later.
Reactivate OEM unlock and USB debugging.
Now flash TWRP. (prague311.img)
Then install nocheck.img into the recovery partition with TWRP.
This is a stock recovery that bypasses the UPDATE.ZIP check and makes it
so that it can be installed.
Now enter the following command in the TWRP terminal:
echo -update_package=/sdcard/update.zip > /cache/recovery/command
Please follow the exact spelling!
Then enter in the terminal: reboot recovery.
The device now boots into the recovery and installs the UPDATE.ZIP.
That'll take a while. Afterwards you boot directly to OREO.
Congratulations!
I've been using OREO for a few hours now and haven't found any bugs yet. They are of course
as it is probably a beta version.
The settings still contain the same firmware entry,
as before installation. I don't know why that is. But it is
actually the EMUI 8 firmware with Google patch from 01.04.2018.
A test of the eRecovery recovery revealed that there the rollback of
EMUI 8 on 5 is offered. I promptly tested it successfully.
Rooting:
Install the OREO TWRP via ADB. (FIGO4.img)
fastboot flash recovery_ramdisk figo4.img
Install the Magisk-v16.zip there.
After rebooting the Magisk Manager app and check the root.
To what extent an update capability to the following firmware exists,
is unfortunately beyond my knowledge and remains to be seen.
Have fun with OREO.
One more comment on the new TWRP:
The TWRP comes from my P smart and is compatible.
More partitions can be backed up there than used to be the case.
However, restoring carries unpredictable risks/results.
Please select only the following partitions for backups in the future:
kernel
Boot Ramdisk
Recovery Ramdisk
System
The data partition can only be backed up after a previous formatting.
You will to get back to EMUI 5:
Starts the eRecovery. There will be a rollback for EMUI 5, at the latest after a Factoryreset.
And now for the final:
[OREO-Custom Rom] Huawei P8 lite 2017 - PRA-LX1 -
K-Rom V.1.1 - EMUI 8, Android 8
On TWRP backup basis:
Developed and tested on this device:
Huawei P8 lite 2017 (Prague)
Model Number: Huawei PRA-LX1
Build Number: FIG-LX1 8.0.0.0.046(C432)
free device, without branding, with root and
TWRP recovery
The OREO beta from this thread is required:
Huawei P8 lite 2017 - PRA-LX1C432B321(8.0.0.321) - EMUI 8/ Android 8 - OREO
Mods:
Call Recorder and KangVip Advanced Settings
It is based on the official Asia-B046 and KangVip version for the Honor V10 (BKL)
Quick guide for experienced users:
Please make a TWRP backup of these partitions,
separately: Kernel, Boot Ramdisk, Recovery Ramdisk and System.
It serves to restore the old system, if you don't like this Rom.
The Rom will be installed as if you were restoring a TWRP backup.
wanted to. All your apps will be preserved.
Further requirements:
TWRP Recovery,
Root is not necessary,
OEM and FRP unlocked,
USB debugging on.
You are familiar with the subject? Then let's go!
A Unroot is not necessary.
Preparation:
Your device must be fully equipped. Including all accounts and apps.
Synchronize the accounts as usual. Especially the Google Account.
Perform a backup with the Huawei data backup.
Remove the device pin, Sim Pin, Face Unlock and the fingerprint.
Installation:
Download: 2018-04-22-PRA-OREO-K-ROM-V1.1.exe
Run this self-extracting archive on the PC.
This creates a TWRP backup folder.
Copy to the TWRP backup directory on extSd.
Restore the backup completely and reboot it into the system.
Do not wipe before and after restoring.
The installation is now complete.
Xposed is not perfectly compatible yet and I will send it later. The system has root
with Magisk. Therefore the existing SuperSu app has to be deleted.
Do not use "hide NavBar" in the Kangvip Advanced Settings, as it only works in China Roms.
Hiding the NavBar is integrated in the EMUI 8.
In the K-Advanced Settings / tune cpu, some changes of the Cpu power are possible. Anyone who
Power needed, can do that. Testing the "Save" options is useless. I tested it extensively.
The in-house Huawei energy saving settings are unbeatable. The Advanced Settings
I will not describe in more detail here, as these are very extensive. Most settings can be set to
the screenshots. On these it can also be seen that I have already been
I've made some design changes. See Notification Bar, Desktop and Appdrawer.
Good luck!
Downloads:*
https://mega.nz/#F!3SwSFIgK!VvtbxPWV2PssIxoHQf556g
[Team HRC]
The Rom I offer is original Huawei firmware. Modified by Kangvip and reworked by me.
If you like this work, you can make a donation to Kangvip: 志康 黄 Send money with PayPal.Me
Not for me, because I don't take money for it. I made this Rom for my purposes.
I love it when these things work. And it does. Now I share it with you.
Here is the link to the original and the developer: 微博正文 - 版版
Many thanks to:
KangVIP - Rom
topjohnwu - Magisk
@Tecalote - SuperSU
Chainfire - SuperSu
Stephen (Stericson) - Busybox
TeamWinRecoveryProject - TWRP
Huawei Technologies Co, Ltd. 华为技术有限公司
WARNING !
If all this has worked on my device, it does not mean that it goes with everyone else. Follow exactly the instructions to prevent damage. The execution is your risk.
Never make a factory reset in TWRP. Brick !!! Wipes only in stock recovery.
Tipp:
The current bricks were mostly caused by TWRP. The Data Partition is missing or corrupted. This is done by TWRP, which still generates errors. There is still no TWRP that works properly. Directly after a new update usually goes everything. But at the latest after the rooting come the problems. Then you can not edit the data partition anymore. No backup and no restoration of data partition.
NOTE: Despite careful preparation I can not guarantee that through the implementation of this Guidance does not create damage to the device or operating system, and therefore assume no liability for ensuing damage and malfunction of hardware and software! If you are still unsure, follow these steps: Only perform the procedure if any mentioned conditions (model number, Android version, etc.) apply to you or your device. Read the instructions carefully and completely, check unfamiliar terminology by google or xda. Downloaded files check for viruses. A backup of important settings and data make. The instructions do not perform, if you do not know what you're doing.
These warnings must be, that is logical. In the end, I have experienced this: For testing, I have seven times a complete backup and can also restore. TWRP worked wonderfully now. When I then restored an older backup, the old error came back.
TWRP works correctly: Before the first restoring first in the stock recovery make a factoryreset. Then also in TWRP and there data wipe. Then restore the backup. All goes well. All older backups I have deleted.
This project is finished. There are no more downloads available.
I appreciate the work of @G.Man. He tested every possible situation with this Phone to find the best way how to Root it despite the limitations of EMUI 5.0!
He wasn't afraid to bring his phone three or more times nearly to a brick just in the hope to find a possible Root Solution for us, which works pretty much good
Many thanks at this point. Without his testing and work we would not be able to get Root Rights on this Phone with newest SuperSU
I bought this phone (pra-lx1) yesterday and i check at the settings that my build number is NRD90M test-keys and i don't have the system update option available and some other stuff(like file manager).
How is this possible on a brand new device??? Is there something i can do without losing warranty?
alimentas said:
I bought this phone (pra-lx1) yesterday and i check at the settings that my build number is NRD90M test-keys and i don't have the system update option available and some other stuff(like file manager).
How is this possible on a brand new device??? Is there something i can do without losing warranty?
Click to expand...
Click to collapse
Seriously ? You got a model test then can you show a screen shot ?, I think it would be better to change it
Test model??? Really??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello, i'm trying to unlock my bootlader, i have my unlocking password from huawei and when i type adb devices i get my device, then i boot into fastmode but when i type fastbbot oem unlock followed by my unlocking code it replies FAILED (remote: Command not allowed)
on the lower part on the fastboot mode it's written phone locked and frp lock : what does FRP Lock mean ?
alimentas said:
Test model??? Really??
Click to expand...
Click to collapse
That's not a test model, your oeminfo partition doesn't match the installed firmware. Is yours an operator bought one? or did you buy it unlocked?
randhackr said:
That's not a test model, your oeminfo partition doesn't match the installed firmware. Is yours an operator bought one? or did you buy it unlocked?
Click to expand...
Click to collapse
Οperator bought one.I just bought it ''factory sealed''.I am fron Greece and this was supposed to be by the place i bought it,αn unbranded EU device.
Is there is something i can do or i change it with a new one????
alimentas said:
Οperator bought one.I just bought it ''factory sealed''.I am fron Greece and this was supposed to be by the place i bought it,αn unbranded EU device.
Is there is something i can do or i change it with a new one????
Click to expand...
Click to collapse
Dial *#*#2846579#*#* (this opens project menu), select Network information Query and vendor country info a report back what you've got there.
i've succeeded unlocking my bootloader, i had to go to developer mode enable oem unlock then retry fastboot mode then it worked.
harlock59 said:
i've succeeded unlocking my bootloader, i had to go to developer mode enable oem unlock then retry fastboot mode then it worked.
Click to expand...
Click to collapse
Yes you need to enable the oem unlock option to disable the frp lock.
Is your phone not branded to any operator? If it is not could you use the twrp that is used for the rooting process to dump the oeminfo partition of your phone?
randhackr said:
Dial *#*#2846579#*#* (this opens project menu), select Network information Query and vendor country info a report back what you've got there.
Click to expand...
Click to collapse
That 's what i got.
Vendor:hw
Country:eu
alimentas said:
That 's what i got.
Vendor:hw
Country:eu
Click to expand...
Click to collapse
That's strange. You seem to have a stock oeminfo. You could try o use the firmware finder in the playstore to try to update your phone to the b118 firmware. You should have something like the screenshot that I uploaded.
i didn't understand what i had to do after unlocking bootloader, i have RootBoxLX1.rar but i don't know how to use it, i've unrared it but what should i do to make them work ?
harlock59 said:
i didn't understand what i had to do after unlocking bootloader, i have RootBoxLX1.rar but i don't know how to use it, i've unrared it but what should i do to make them work ?
Click to expand...
Click to collapse
I only installed twrp, but as far as I understand you must use fastboot to flash the modified boot.img provided in the rar file.
randhackr said:
I only installed twrp, but as far as I understand you must use fastboot to flash the modified boot.img provided in the rar file.
Click to expand...
Click to collapse
how can i install twrp and where can i find twrp for huawei pra-lx1or what is the command line to flash the modified boot.img ?
---------- Post added at 05:36 PM ---------- Previous post was at 05:32 PM ----------
isn't there a mistype (mis spelling) fastboot flash boat boot_root.img shouldn't it be fastboot flash boot boot_root.img ???
harlock59 said:
how can i install twrp and where can i find twrp for huawei pra-lx1or what is the command line to flash the modified boot.img ?
---------- Post added at 05:36 PM ---------- Previous post was at 05:32 PM ----------
isn't there a mistype (mis spelling) fastboot flash boat boot_root.img shouldn't it be fastboot flash boot boot_root.img ???
Click to expand...
Click to collapse
Check this post https://forum.xda-developers.com/showpost.php?p=71601405&postcount=62
Edit: Yes there is a misspelling it should be boot
harlock59 said:
i didn't understand what i had to do after unlocking bootloader, i have RootBoxLX1.rar but i don't know how to use it, i've unrared it but what should i do to make them work ?
Click to expand...
Click to collapse
Extract RootBoxLX1.rar, gets so all necessary files. Then work the Root instructions. TWRP may not be on the device separate the original Recovery.
I have changed the write errors boat to boot.
Sorry
randhackr said:
Check this post https://forum.xda-developers.com/showpost.php?p=71601405&postcount=62
Edit: Yes there is a misspelling it should be boot
Click to expand...
Click to collapse
thanks, that helped !
Realme XT Wiki
For convenience : https://www.androidfilehost.com/?w=files&flid=304989
First things first.
DISCLAIMER : Use this guide at your own risk. I won't be responsible for you bricking your device due to following this guide. It's also necessary to back up your data before you attempt anything.
Realme XT is not really a developer friendly device as they claim to be for the following reasons.
- Bootloader restricts flashing critical partitions and certain fastboot options are disabled like
Code:
fastboot boot recovery.img
- The flash tool is only available to service centres.
- Kernel sources are not actively updated by realme.
- Nil response to developer's queries.
Code:
[B][U]Table of contents :[/U][/B]
- Unlocking the bootloader
- Unbrick guide
- TWRP guide
- Upgrade guide
- Downgrade guide
- Project Treble for Realme XT
- Links
For unlocking the bootloader, follow the official instrutions from here :
https://c.realme.com/in/post-details/1184740422732218368
As of 28/03/20, you can unlock the bootloader in Realme UI. The official guide for XT is still not updated by realme, but the bootloader unlock app tool that was released for realme3pro works for XT.
UNBRICK GUIDE FOR REALME XT : (FASTBOOT)
Most bricks that happen with devices are softbricks. This means you can boot into stock recovery using key combination or you can access fastboot.
Hardbricks are where your device basically does nothing no matter what you do.
If you are on Color OS 6 or realme UI on locked bootloader :
- Switch off your device
- Press volume up + power button hold it until it finishes starting up.
- You will see the recovery menu now
- Press online update and connect it to wifi and follow instructions
If you are on color os 6 on unlocked bootloader :
Prerequisite:
1. You need to have unlocked bootloader
2. Platform tools setup and added to system environmental variables under windows
OR
Just install this : https://forum.xda-developers.com/showthread.php?t=2317790
Since custom ROMS don't deal with critical partitions, there is very less chance that the critical partitions are messed up. Majority of the times you would be fine with just flashing the boot image, system image, vendor image, vbmeta.
Instructions for color os 6 (Android pie firmware) :
Download the stock pie A16 fastboot image from the links section and extract it :
Just flash by executing the following commands :-
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash dtbo dtbo.img
fastboot flash oppo_sec oppo_sec.img
fastboot flash modem modem.img
fastboot flash splash splash.img
fastboot flash DRIVER DRIVER.img
fastboot reboot
If you are on Realme UI on unlocked bootloader :
Prerequisite :
Download the stock Realme UI fastboot image from the links section and extract it :
Note : The zip file has other partitions too. Hopefully, you shouldn't need them.
Just flash the boot,system,vendor and vbmeta by executing the following commands
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash dtbo dtbo.img
fastboot flash oppo_sec oppo_sec.img
fastboot flash modem modem.img
fastboot flash splash splash.img
fastboot flash DRIVER DRIVER.img
fastboot reboot
Guide to Custom Recovery:
Prerequisite:
1. You need to have unlocked bootloader
2. Platform tools setup and added to system environmental variables under windows
OR
Just install this : https://forum.xda-developers.com/showthread.php?t=2317790
TWRP Recovery
Orangefox Recovery
Instructions to install TWRP recovery:
Run this command
Code:
fastboot flash recovery TWRP.img
You can install orangefox recovery by flashing it via TWRP recovery or by extracting the recovery.img from orangefox recovery.zip file.
Upgrade guide :
You can always find the latest update from here : https://www.realme.com/in/support/software-update
Upgrading from android pie to android 10 carries the risk of bricking your device. Be it locked or unlocked. Thus proceed with caution and ONLY use stock recovery to update from android pie to android 10.
If you are on locked bootloader,
Step 1 :Simply download the update of your choice from the Links section and try to open it in stock file manager.
Note : If it doesn't show the update option in stock file manager, just rename the file from *.zip to *.ozip and try again
Step 2 : Press reboot immediately after the flashing is done
Step 3 (Very important) : Pray that everything works. Bricks can happen to anyone.
If you are on unlocked bootloader,
Step 1:In case you already have TWRP working on pie, simply flash the official stock android pie A16 through twrp and let it boot.
Step 2:Now, let it fully boot into the system
Step 3: Go to stock file manager and follow similar instructions as is for locked bootloader that's written above.
Downgrade guide :
Prerequisite:
In case you are in realme UI (Android 10) and want to roll back to android pie for any reason, you need to backup your data and flash stock pie A16 via TWRP
Step 0 : Back up your data and download stock A16 firmware from the links section below
Step 1 : Go to TWRP and flash stock pie
Step 2 : Flash stock pie again
Step 3 : Format data and reboot
Project Treble for Realme XT :-
You could refer here for what works and what doesn't
https://github.com/phhusson/treble_experimentations/wiki/realme-XT
Prerequisite :
1. You need to have unlocked bootloader
2. Platform tools setup and added to system environmental variables under windows
OR
Just install this : https://forum.xda-developers.com/showthread.php?t=2317790
3. You need to be on realme UI (Android 10)
Typically, you could install GSI without even using TWRP.
Step 1: Download any A/B arm64 GSI of your choice
Step 2: Erase userdata using the command
Code:
fastboot -w
Step 3: Flash system.img using fastboot command
Code:
fastboot erase system && flash system system.img
Step 4: Flash RUI vbmeta with flags
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Optional : Flashing TWRP helps with installing magisk and device specific treble fixes and is highly recommended.
USEFUL LINKS :
Recovery (Both stock and TWRP), Fastboot images and Official Updates
https://www.androidfilehost.com/?w=files&flid=304989
Realme XT Android 10 C01 (Realme UI)
https://download.c.realme.com/osupdate/RMX1921EX_11_OTA_1010_all_yuEH87qmmZhw.ozip
Realme XT Android pie A16
https://download.c.realme.com/osupdate/RMX1921EX_11_OTA_0160_all_CcmkxwAnmByA.ozip
Realme XT stock vbmeta Android 10 C01 (Realme UI)
Help!!
I am on coloros 6 (a16) and i have unlocked bootloader (twrp not installed) so how can i update it to rui. Via stock file manager method or just install twrp in a16 and flash rui(c_02) ozip in twrp. So, Which will be a better and safe way to update and avoid bricking the phone according to you.
mehtakush007 said:
I am on coloros 6 (a16) and i have unlocked bootloader (twrp not installed) so how can i update it to rui. Via stock file manager method or just install twrp in a16 and flash rui(c_02) ozip in twrp. So, Which will be a better and safe way to update and avoid bricking the phone according to you.
Click to expand...
Click to collapse
Use the stock recovery for update and wait for official OTA.
Reset Device
My device is locked and now i forgot my password and when i am trying to wipe data from realme ui recovery its asking for password again is there anyway to bypass that security and reset my device please help i cant go to sevice centers right now due to lockdown in my country.
Leamusex said:
My device is locked and now i forgot my password and when i am trying to wipe data from realme ui recovery its asking for password again is there anyway to bypass that security and reset my device please help i cant go to sevice centers right now due to lockdown in my country.
Click to expand...
Click to collapse
So u must wait for that. . Me waiting for tutorial to downgrade realme ui to a16 or. How to unlock bootloader with realmeui firmware.
Leamusex said:
My device is locked and now i forgot my password and when i am trying to wipe data from realme ui recovery its asking for password again is there anyway to bypass that security and reset my device please help i cant go to sevice centers right now due to lockdown in my country.
Click to expand...
Click to collapse
Unfortunately no. you must input password or your data is a lost cause.
krizhiel said:
So u must wait for that. . Me waiting for tutorial to downgrade realme ui to a16 or. How to unlock bootloader with realmeui firmware.
Click to expand...
Click to collapse
The tutorial is already there in the wiki. Although make sure you backup your data first.
PS C:\adb> fastboot flash recovery C:\adb\TWRP_RMX1921_pjgowtham_290320.img
sending 'recovery' (65536 KB)...
it did not flash it just stayed there forever
I have bricked my device. I have a bootloop. Combinations of keys don't work, recovery doesn't show up. Bootloader is locked. Can anyone help?
dmmas21 said:
I have bricked my device. I have a bootloop. Combinations of keys don't work, recovery doesn't show up. Bootloader is locked. Can anyone help?
Click to expand...
Click to collapse
Same problem i have..Any help please..
dmmas21 said:
I have bricked my device. I have a bootloop. Combinations of keys don't work, recovery doesn't show up. Bootloader is locked. Can anyone help?
Click to expand...
Click to collapse
You locked manually?
akashavel said:
You locked manually?
Click to expand...
Click to collapse
yes, me too. And now i have hardbrick and dont know how to fix this without service centre
bro Did You fixed it ?
I am on RMX1921_11_C.04 is there anyway to install custom recovery?
I bought a realme xt and upgraded it to realme ui version c04 but I get some random crash reports I don't know what is it they just randomly pop up 1-2 times per day along with a screenshot I am uploading those please can someone check.
My device bootloop'ed after following your downgrade tutorial. Tried boot unbrick it like your tutorial to no avail
Anyone who is now used to with this device and have done all these steps from Unlocking bootloader to flashing recoveries to installing custom & Stock Roms, can you please tell me what are the senarios in which this device can brick and only restored by Realme service center? I mean what possible error we can make that gives error of boot/recovery destroyed and only needs to visit realme service center?
I am very new to realme, before getting started with unlocking bootloader, i want to be sure about my steps, actually all i need is to use titanium backup for old data transfer of apps, my phone records etc, and most importantly using viper4android. This is all i am going to do after unlocking bootloader.
Raju Sah said:
Same problem i have..Any help please..
Click to expand...
Click to collapse
A reply this late isnt probably useful. But for others who refer this thread, once locked, it can be saved only by flashtool if you cant access stock recovery.
Fastboot commands not working
Hey there.
I am using realme xt with realme UI and i tried to unlock the bootloader. The bootloader is unlocked successfully but the fastboot commands arent working now on the device. This is whats happened while relocking the bootloader and same error for flashing recovery.
D:\Root\platform-tools>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
f40db298 device
D:\Root\platform-tools>adb reboot bootloader
D:\Root\platform-tools>fastboot devices
f40db298 fastboot
D:\Root\platform-tools>fastboot flashing lock
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
D:\Root\platform-tools>fastboot flashing lock
< waiting for any device >
^C
D:\Root\platform-tools>fastboot devices
D:\Root\platform-tools>
this also happened while flashing recovery also. And I am kind of stuck i cant relock the bootloader and cant install custom recovery to root the device.
Kindly, guide me to solve this problem. Thanks in Advance.
Hi, anybody can help me? I want to sell my phone so i wanted to flash stock rom and lock the bootloader. But i dont find any post or something like that to do so... Do you know how can i flash the stock rom and relock the bootloader like we can do with xiaomi phones?
Hello everyone,
just got this tablet from my internet provider in bundle !
I found one or 2 post talking about root ( via twrp ) but here i report ( tested by myself ) another way to root your
TB-X606x without the need of installing TWRP ( well if you need it just use the other method )
I've root on this latest ROM TB_X606X_S300326_210720_BMP available on ( Rescue and Smart Assistant (LMSA)
DISCLAIMER as always.. " do it at your OWN risk , i won't be responsible if anything goes wrong, you might risk to brick your tablet "
that said let's go :
1- let's reboot in fastboot mode
Code:
adb reboot booatloader
(if your m10 just restart without entering fastboot than just poweroff, after that keep press POWER + VOLUME DOWN )
2 - unlock your bootloader ( if you don't know how.. have a quick search ..)
Code:
fastboot oem unlock
( if this gives you this error : FAILED (remote: 'unknown command') than do this:
Code:
fastboot flashing unlock
is gonna ask you to press VOLUME UP to unlock
or Volume DOWN to NOT unlock
you press volume UP
3 -
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
( you find the empty vbmeta.img attached to this post )
4 -
Code:
fastboot flash boot boot.img
(you find the ALREADY patched BOOT.IMG for ROM TB_X606X_S300326_210720_BMP attached in this post )
BE AWARE .. if you are going to ROOT another ROM version of TB-X606x you need to get the original BOOT.IMG from the official rom( the exact same version your system is updated to ) and than PATCH IT with magisk !!!
5 -
Code:
fastboot reboot
that's it ! Your m10 FHD PLUS TB-X606x is ROOTED !!!
FILES INCLUDED :
Vbmeta_empty.img is the EMPTY vbmeta .. simply rename it vbmeta.img before flash it
vbmeta_ORIG.img is the ORIGINAL vbmeta of ROM TB_X606X_S300326_210720_BMP just in case you need it..!!!
magisk_patched_boot_TB_X606X_S300326_210720.img is the PATCHED BOOT.IMG(rename it like this for convenience )
always for ROM TB_X606X_S300326_210720_BMP
ORIG_boot_TB_X606X_S300326_210720.img is the original boot.img
[reserved]
Hello, thx. i have one problem. my device not react to reboot to fastboot mode. my pc send message: waiting to device.
pleas help me. thx
bazzilisek85 said:
Hello, thx. i have one problem. my device not react to reboot to fastboot mode. my pc send message: waiting to device.
pleas help me. thx
Click to expand...
Click to collapse
turn it off , wait few seconds than keep press POWER + VOLUME DOWN
it'll enter fastboot , now plug your cable and write fastboot devices
you'll see your device connected
bazzilisek85 said:
Hello, thx. i have one problem. my device not react to reboot to fastboot mode. my pc send message: waiting to device.
pleas help me. thx
Click to expand...
Click to collapse
Make sure you have the latest MTK usb drivers.
Postup funkční - potvrzuji.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LiborCZ said:
Postup funkční - potvrzuji.View attachment 5416675
Click to expand...
Click to collapse
This forum is English only, try here:
Google Translate
Google's service, offered free of charge, instantly translates words, phrases, and web pages between English and over 100 other languages.
translate.google.com
simika said:
Hello everyone,
just got this tablet from my internet provider in bundle !
I found one or 2 post talking about root ( via twrp ) but here i report ( tested by myself ) another way to root your
TB-X606x without the need of installing TWRP ( well if you need it just use the other method )
I've root on this latest ROM TB_X606X_S300326_210720_BMP available on ( Rescue and Smart Assistant (LMSA)
DISCLAIMER as always.. " do it at your OWN risk , i won't be responsible if anything goes wrong, you might risk to brick your tablet "
that said let's go :
1- let's reboot in fastboot mode
Code:
adb reboot booatloader
(if your m10 just restart without entering fastboot than just poweroff, after that keep press POWER + VOLUME DOWN )
2 - unlock your bootloader ( if you don't know how.. have a quick search ..)
Code:
fastboot oem unlock
( if this gives you this error : FAILED (remote: 'unknown command') than do this:
Code:
fastboot flashing unlock
is gonna ask you to press VOLUME UP to unlock
or Volume DOWN to NOT unlock
you press volume UP
3 -
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
( you find the empty vbmeta.img attached to this post )
4 -
Code:
fastboot flash boot boot.img
(you find the ALREADY patched BOOT.IMG for ROM TB_X606X_S300326_210720_BMP attached in this post )
BE AWARE .. if you are going to ROOT another ROM version of TB-X606x you need to get the original BOOT.IMG from the official rom( the exact same version your system is updated to ) and than PATCH IT with magisk !!!
5 -
Code:
fastboot reboot
that's it ! Your m10 FHD PLUS TB-X606x is ROOTED !!!
FILES INCLUDED :
Vbmeta_empty.img is the EMPTY vbmeta .. simply rename it vbmeta.img before flash it
vbmeta_ORIG.img is the ORIGINAL vbmeta of ROM TB_X606X_S300326_210720_BMP just in case you need it..!!!
magisk_patched_boot_TB_X606X_S300326_210720.img is the PATCHED BOOT.IMG(rename it like this for convenience )
always for ROM TB_X606X_S300326_210720_BMP
ORIG_boot_TB_X606X_S300326_210720.img is the original boot.img
Click to expand...
Click to collapse
Hello guys, I tried this method today and it work with my model. I live in India and here in India, TB x606v model is available. The above method works with my model and is successful in performing root. I just patched the boot.img of rom of my particular model. All the other process is same as mentioned. Thanks Simika.
The tarapstar said:
Hello guys, I tried this method today and it work with my model. I live in India and here in India, TB x606v model is available. The above method works with my model and is successful in performing root. I just patched the boot.img of rom of my particular model. All the other process is same as mentioned. Thanks Simika.
Click to expand...
Click to collapse
I'm glad I could help
Okay so guys, the above root method works for all models of Lenovo tab M10 FHD Plus. I have tested. However, those who are facing bootloop problem after flashing patched boot image and empty vbmeta image. You can do one thing is that get the device in fastboot mode(by pressing volume down and power button for 10seconds) then connect it to your computer/laptop. Now using fastboot commands flash the original vbmeta.img, boot.img, vendor.img, system.img, and cache.img . These files can be downloaded using the Lenovo rescue assistant for your model. Then enter fastboot reboot command and your device will start working again. If after few days of rooting your device face problem of bootloop, then do the above mentioned method and then flash the patched magisk image again. It will fix the problem.
Hello, Just picked up a X606F model. I haven't even connected it to the internet yet. I was wondering if the root persists over updates? Or should I update first? Presently I'm on TB-X606F_S300320_210716_BPM
thanks,
A-
alexacm said:
Hello, Just picked up a X606F model. I haven't even connected it to the internet yet. I was wondering if the root persists over updates? Or should I update first? Presently I'm on TB-X606F_S300320_210716_BPM
thanks,
A-
Click to expand...
Click to collapse
doesn't matter cause when you'll root by patching the latest rom, latest updates will be applied after rooting.
I used this method to Root my M10 FHD Plus ( TB-X606F ) a few months ago.
Now, I am attempting to update, but I cannot find the location of the OTA file for TWRP to install?
Any one offer any clues as to what folder it might be in ?
Or a link to some repo of Lenovo ROMs ?
Thanks in Advance !
Can I Install update if I have root without TWRP?
Have I must full OTA download and unpack, extract boot.img and patch it in Magisk?
simika said:
Hello everyone,
just got this tablet from my internet provider in bundle !
I found one or 2 post talking about root ( via twrp ) but here i report ( tested by myself ) another way to root your
TB-X606x without the need of installing TWRP ( well if you need it just use the other method )
I've root on this latest ROM TB_X606X_S300326_210720_BMP available on ( Rescue and Smart Assistant (LMSA)
DISCLAIMER as always.. " do it at your OWN risk , i won't be responsible if anything goes wrong, you might risk to brick your tablet "
that said let's go :
1- let's reboot in fastboot mode
Code:
adb reboot booatloader
(if your m10 just restart without entering fastboot than just poweroff, after that keep press POWER + VOLUME DOWN )
2 - unlock your bootloader ( if you don't know how.. have a quick search ..)
Code:
fastboot oem unlock
( if this gives you this error : FAILED (remote: 'unknown command') than do this:
Code:
fastboot flashing unlock
is gonna ask you to press VOLUME UP to unlock
or Volume DOWN to NOT unlock
you press volume UP
3 -
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
( you find the empty vbmeta.img attached to this post )
4 -
Code:
fastboot flash boot boot.img
(you find the ALREADY patched BOOT.IMG for ROM TB_X606X_S300326_210720_BMP attached in this post )
BE AWARE .. if you are going to ROOT another ROM version of TB-X606x you need to get the original BOOT.IMG from the official rom( the exact same version your system is updated to ) and than PATCH IT with magisk !!!
5 -
Code:
fastboot reboot
that's it ! Your m10 FHD PLUS TB-X606x is ROOTED !!!
FILES INCLUDED :
Vbmeta_empty.img is the EMPTY vbmeta .. simply rename it vbmeta.img before flash it
vbmeta_ORIG.img is the ORIGINAL vbmeta of ROM TB_X606X_S300326_210720_BMP just in case you need it..!!!
magisk_patched_boot_TB_X606X_S300326_210720.img is the PATCHED BOOT.IMG(rename it like this for convenience )
always for ROM TB_X606X_S300326_210720_BMP
ORIG_boot_TB_X606X_S300326_210720.img is the original boot.img
Click to expand...
Click to collapse
you can make phone calls as root?
alexacm said:
Hello, Just picked up a X606F model. I haven't even connected it to the internet yet. I was wondering if the root persists over updates? Or should I update first? Presently I'm on TB-X606F_S300320_210716_BPM
thanks,
A-
Click to expand...
Click to collapse
after any Ota update you need to do the process again
Hello, I just d/l the latest OTA. When I try and install it, it fails and reboots. Any ideas?
thanks-
Hello. I can help someone, a friend has this tablet model, adb detects the name nicely, reset to the bootloader, then after typing the command to unlock it, nothing happens, the tablet is in the place, no message. I was doing root on samsung, on sony and I had no such problems. win 10 64x. drivers are, turn off the signature of drivers too,
What could be wrong ?
adek89 said:
Hello. I can help someone, a friend has this tablet model, adb detects the name nicely, reset to the bootloader, then after typing the command to unlock it, nothing happens, the tablet is in the place, no message. I was doing root on samsung, on sony and I had no such problems. win 10 64x. drivers are, turn off the signature of drivers too,
What could be wrong ?
Click to expand...
Click to collapse
Make sure you have the latest fastboot and MTK drivers.
Yahoo Mike said:
Make sure you have the latest fastboot and MTK drivers.
Click to expand...
Click to collapse
Hello, I visited this link, but the download of MTK Drivers doesn't start.