Related
TWRP 2.8.7.0 custom recovery
thanx to user @Unjustified Dev we have TWRP custom recovery for our phone.
download HERE
So anyone who download the TWRP should send him a dollar for beer or at least thank him!
Of course you do everything on your own!
To test before installation (linux users need sudo before fastboot):
Code:
fastboot -i 0x1bbb boot twrp-2.8.7.0-idol3.img
To install (linux users need sudo before fastboot):
Code:
fastboot -i 0x1bbb flash recovery twrp-2.8.7.0-idol3.img
!BEFORE YOU START, PLEASE READ THIS!
And don´t forget to thank Famewolf for the tutorial, because this could save your phone when something go bad!
Thanks, tried it. It worked.
I also just installed SU directly, bypassing the previous root thread.
1. Download the .zip package from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
2. Put it on the root of my SD card.
3. In TWRP click install and find the .zip.
Wonderful. Just a question: is this recovery for Idol 3 4.7 (6039) or 5.5 (6045) ?
Gynoid said:
Wonderful. Just a question: is this recovery for Idol 3 4.7 (6039) or 5.5 (6045) ?
Click to expand...
Click to collapse
It's for 6045. For 4.7 TWRP, see this post: http://forum.xda-developers.com/showpost.php?p=61976520&postcount=18
Thanks!
is it functional for backing up our system in TWRP?
@DallasCZ could you please provide the original link to TWRP. That was a bit unfair to upload it elsewhere as I tend to track the number of downloads.
Sent from my LGMS395 using Tapatalk
gecko702 said:
is it functional for backing up our system in TWRP?
Click to expand...
Click to collapse
Yes although to my knowledge noone has actually done a restore yet. He's fixing some minor bugs and will be releasing a new version at some point.
famewolf said:
Yes although to my knowledge noone has actually done a restore yet. He's fixing some minor bugs and will be releasing a new version at some point.
Click to expand...
Click to collapse
i am in touch with the dev and allready downloading the new build..will be soon on my google drive
Unjustified Dev said:
@DallasCZ could you please provide the original link to TWRP. That was a bit unfair to upload it elsewhere as I tend to track the number of downloads.
Sent from my LGMS395 using Tapatalk
Click to expand...
Click to collapse
sorry, i corrected the link...
Convert TWRP Backup into flashable rom zip
I found these instructions that explain how to take a TWRP backup and turn it into a flashable zip file. This would allow someone to create a "factory" rom pre-rooted to be flashed.
For TWRP Backup
Transfer the TWRP backup from Phone to PC.
You’ll see a file named system.ext4.win which is the System partition backup of your device. Rename it to system.ext4.tar (Changing its extension from .win to .tar)
Extract the system.ext4.tar using an archive software like Winrar or 7zip.
If your TWRP backup is not in compression mode, you will directly get the system folder, else you will get a file named system.ext4, which should be renamed again to system.ext4.tar and extract it to get the system folder.
Take the boot.emmc.win file and rename it to boot.img.
Now collect a META-INF folder from any custom ROM which is made for your device. Make sure you get the correct Meta-Inf folder, else the Zip won’t work and might worsen the condition of your device.
Select the META-INF, System folders and the boot.img and right click your mouse and select add to Archive.
In the Archive settings, choose the extension of the compressed file as Zip (Make sure of this part)
Now you can use this Zip file to flash it on your Custom recovery.
we dont have the meta-inf folder...there is one in the update i got, but i dont know if this id the right one.
and we dont have custom rom to get meta-inf from.
also the main thing is, that i cannot unpack the system win file when renamed to .tar i dunno why (i got latest 7-zip app).
DallasCZ said:
we dont have the meta-inf folder...there is one in the update i got, but i dont know if this id the right one.
and we dont have custom rom to get meta-inf from.
also the main thing is, that i cannot unpack the system win file when renamed to .tar i dunno why (i got latest 7-zip app).
Click to expand...
Click to collapse
What they primarily want is the "update-binary" which is device specific. I don't remember if the update had one....I did take apart an update-supersu.zip and it uses a script as it's update binary...thought about trying to convert that. Theoretically you could take a meta-inf for another device's rom...and use it's meta-inf making sure to replace the update-binary. It also has an installer script that tells it to mount system and data....extract files from the zip and where to put them. I learned a bit when I was trying to make an update.zip to fix my build.prop.
It untar'd fine for me on my linux pc:
[email protected]:/workarea/android/idol3/TWRP/BACKUPS/408adcbe/1970-01-01--22-28-53_LRX22G_release-keys/work > tar -xvf ../system.ext4.win000
tar: Removing leading `/' from member names
/system/app/
/system/app/AntHalService/
/system/app/AntHalService/AntHalService.apk
/system/app/AntHalService/arm64/
/system/app/AntHalService/arm64/AntHalService.odex
/system/app/BasicDreams/
/system/app/BasicDreams/BasicDreams.apk
/system/app/BasicDreams/arm64/
/system/app/BasicDreams/arm64/BasicDreams.odex
/system/app/Bluetooth/
/system/app/Bluetooth/Bluetooth.apk
/system/app/Bluetooth/arm/
/system/app/Bluetooth/arm/Bluetooth.odex
famewolf said:
What they primarily want is the "update-binary" which is device specific. I don't remember if the update had one....I did take apart an update-supersu.zip and it uses a script as it's update binary...thought about trying to convert that. Theoretically you could take a meta-inf for another device's rom...and use it's meta-inf making sure to replace the update-binary. It also has an installer script that tells it to mount system and data....extract files from the zip and where to put them. I learned a bit when I was trying to make an update.zip to fix my build.prop.
It untar'd fine for me on my linux pc:
[email protected]:/workarea/android/idol3/TWRP/BACKUPS/408adcbe/1970-01-01--22-28-53_LRX22G_release-keys/work > tar -xvf ../system.ext4.win000
tar: Removing leading `/' from member names
/system/app/
/system/app/AntHalService/
/system/app/AntHalService/AntHalService.apk
/system/app/AntHalService/arm64/
/system/app/AntHalService/arm64/AntHalService.odex
/system/app/BasicDreams/
/system/app/BasicDreams/BasicDreams.apk
/system/app/BasicDreams/arm64/
/system/app/BasicDreams/arm64/BasicDreams.odex
/system/app/Bluetooth/
/system/app/Bluetooth/Bluetooth.apk
/system/app/Bluetooth/arm/
/system/app/Bluetooth/arm/Bluetooth.odex
Click to expand...
Click to collapse
i allready build some roms for my older device, so i know what it is about.
For the proper rom zip you have to make the updater script with all the simlinks and metadata ...in the latest update there were no simlinks in the updater script...
without them you can brick your phone.
for example simlinks from 4.4.2 Os from zte V5
Code:
symlink("/data/misc/audio/mbhc.bin", "/system/etc/firmware/wcd9306/wcd9306_mbhc.bin");
symlink("/data/misc/audio/wcd9320_anc.bin", "/system/etc/firmware/wcd9306/wcd9306_anc.bin");
symlink("/persist/WCNSS_qcom_cfg.ini", "/system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini");
symlink("/persist/WCNSS_qcom_wlan_nv.bin", "/system/etc/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin");
symlink("/system/lib/modules/pronto/pronto_wlan.ko", "/system/lib/modules/wlan.ko");
symlink("Roboto-Bold.ttf", "/system/fonts/DroidSans-Bold.ttf");
symlink("Roboto-Regular.ttf", "/system/fonts/DroidSans.ttf");
symlink("libGLESv2.so", "/system/lib/libGLESv3.so");
symlink("mksh", "/system/bin/sh");
this you cannot copy from another device....
Never mind. I installed the second build.
How do I boot into the custom recovery? Is it power up + power button on the Idol 3?
Acreo Aeneas said:
Never mind. I installed the second build.
How do I boot into the custom recovery? Is it power up + power button on the Idol 3?
Click to expand...
Click to collapse
Reboot or power on till you see the alcatel screen pop up....right away hold down up arrow and it should go into recovery.
Thank you so much...been waiting for this....
so now let ROM's start pouring in )))))))
Hmm odd. I had to reflash it. For some reason it didn't take the first time I flashed the second build TWRP to my Idol 3.
What partitions should I backup using TWRP? I'd assume: Boot, System, and Data? Should I include System Image too?
Acreo Aeneas said:
Hmm odd. I had to reflash it. For some reason it didn't take the first time I flash the second build TWRP to my Idol 3.
What partitions should I backup using TWRP? I'd assume: Boot, System, and Data? Should I include System Image too?
Click to expand...
Click to collapse
The default of boot, system and data should be fine for personal use however if you have not yet rooted please read here first! http://forum.xda-developers.com/idol-3/help/want-to-able-to-install-ota-updates-t3163745
So Awesome! best looking twrp Ive seen yet xD. Also, works well too. I havent tested backing up data, but I did a successful restore of the system and boot So far so good!
Manually Install Full-OTA Files-Upgrade or Downgrade
Steps:
Prepare and Notice
A. Warning! Flash phone might get it bricked. I am not responsible for it.
B. Backup your data, it might be restore factory default setting especially using downgrade ROM version.
C. Unlock bootloader before flash steps. If already unlocked it is OK.
D. After update successfully, device might be locked again. Unlock again if needed.
E. HWOTA--hi6250-7-8.zip Download
F.Download Update files for your device from Pro-teammt.ru
Process
A. Extract HWOTA package(Step E. from above). Copy both HWOTA7 and HWOTA8 folders onto root of (ext-sdcard, decrypted internal sdcard, usb flash otg).
B. Add your Three (3) update files to HWOTA* folder; HWOTA7 if on Nougat: HWOTA8 if on Oreo.
C. (if have twrp already skip to E)Connect phone and enable adb , Use Replace_Recovery.bat in HWOTA to flash TWRP recovery.
D. Disconnect USB cable, use Vol-Up + Power to boot into TWRP.
E. From in TWRP install sdcard hwota7-8-auto.zip-- If using USB-otg or decrypted internal , flash hwota7-8-auto-internal.zip
F. Watch twrp screen for the message to press volume button to continue.
*******************************************************************************************************
*******************************************************************************************************
To Downgrade Back to Nougat from OREO --
A. Download roll-back update for your device (not all versions have roll-back yet, many do) from Pro-teammt.ru
B. Roll-backs have only two (2) files, other than that difference, follow directions same as above.
PARTIAL ROLL-BACK LIST --
A. BND-L21c432 http://pro-teammt.ru/firmware-database/?firmware_model=BND-L21C432B124&firmware_page=0
B. BND-L24c567 http://pro-teammt.ru/firmware-database/?firmware_model=Bond-l24c567b150&firmware_page=0
C. BND-L34c567 (MATE se) http://pro-teammt.ru/firmware-database/?firmware_model=Bond-l34c567b&firmware_page=0
D. BND-al10c675 (BND-L22)http://pro-teammt.ru/firmware-database/?firmware_model=BND-al10c675b161&firmware_page=0
E. BND-L21C636 https://pro-teammt.ru/firmware-database/?firmware_model=BND-L21C636B158CUSTC636D001&firmware_page=0
*******************************************************************************************************
Updated(Nov 2018) Version V17 (Can run built in updater on Older V) on Firmware downloader
Beta Tool Folder ==> Download
Tool checks version of phone with "getprop" or also with input from user.
Tool only gets available listed FullOTA for your device Model and Region code. Then you choose from that list.
Tool also verifies md5 of downloaded files and saves them onto your desktop in device/version sub folders.
Can Be used to extract the downloaded zip. and extract the update.app into separate images.
Last step gives option to push updates to phone to help with HWOTA
************************************
************************************
Alternate HWOTA with full rebrand
HWOTA with RE-brand
************************************
************************************
FILE INTEGRITY IS IMPORTANT, Please be in good Habit and always check numbers after a download.
My download links above are on Android file host. they all show MD5 on the download site.
The update files from http://pro-teammt.ru do not have MD5 listed.
Here are the MD5 numbers for the USA L24 update files
Code:
e75a21769f049430840ea900b11600c4 update.zip
73414b5383e5fb3391e77a13c17dca53 update_data_full_public.zip
122f0e91d77fba6e399300926d1ef289 update_full_bnd-l24_hw_usa.zip
Old thread. Not continued.
Search emui-flasher instead
.
---------RESERVED-----
Contents of HWOTA7-8-auto-V3.1.zip
Replace recovery batch file
Code:
@echo off
if not defined in_subprocess (cmd /k set in_subprocess=y ^& %0 %*) & exit )
title Lazy Recovery Auto Launcher
echo Waiting For device to be recognized by ADB
adb wait-for-device
adb shell getprop ro.build.version.emui > %~dp0\version-info.txt
for /f %%i in ('FINDSTR "EmotionUI_" %~dp0\version-info.txt') do set emui=%%i
echo %emui%
set str=%emui:~10,1%
echo.%str%
pause
if %str% equ 8 call HwOTA8\Replace_Recovery.bat
if %str% equ 5 call HWOTA7\Replace_Recovery.bat
echo THIS SCRIPT SHOULD BE FINISHED
pause
exit
HwOTA8\Replace_Recovery.bat contents
Code:
@echo off
title Recovery Replace Oreo
echo Waiting For device to be recognized by ADB
adb wait-for-device
adb shell getprop ro.build.version.emui > %~dp0\version-info.txt
for /f %%i in ('FINDSTR "EmotionUI_" %~dp0\version-info.txt') do set emui=%%i
echo %emui%
set str=%emui:~10%
echo.%str%
pause
if %str% lss 5.3 (goto Nougat
)else (
echo ok to continue)
echo Next will reboot to Fastboot Mode (bootloader)
pause
adb reboot bootloader
echo Wait Here untill fastboot mode Loads On Phone
pause
fastboot oem get-build-number 2> %~dp0\build-info.txt
for /f "tokens=2" %%i in ('findstr "^(bootloader)" "%~dp0\build-info.txt"') do set Device=%%i
for /f "tokens=3" %%i in ('findstr "^(bootloader)" "%~dp0\build-info.txt"') do set Build=%%i
echo Your Current Device is = %Device% %Build%
echo next will flash Oreo twrp
pause
fastboot flash recovery_ramdisk HWOTA8\complete_twrp_ramdisk.img
echo RECOVERY SHOULD NOW BE FLASHED
echo GET READY TO PULL USB PLUG OUT AND HOLD VOLUME UP
echo RIGHT AFTER YOU PRESS BUTTON TO CONTINUE
pause
fastboot reboot
exit
:Nougat
echo You are On NOUGAT DO NOT USE THIS
pause
exit
Contents of restore-package
Replace recovery batch file
Code:
adb reboot bootloader
pause
fastboot flash recovery twrp-honor.img
pause
Update-binary from restore.zip
Code:
#!/sbin/sh
dd if=/external_sd/restore-package/boot.img of=/dev/block/mmcblk0p28
dd if=/external_sd/restore-package/cust.img of=/dev/block/mmcblk0p45
dd if=/external_sd/restore-package/product.img of=/dev/block/mmcblk0p48
dd if=/external_sd/restore-package/system.img of=/dev/block/mmcblk0p44
dd if=/external_sd/restore-package/vendor.img of=/dev/block/mmcblk0p47
dd if=/external_sd/restore-package/version.img of=/dev/block/mmcblk0p46
.
Hi !
Does it work on L21C432 for rollback to Nougat ?
Thanks !
DaRkLinK_35 said:
Hi !
Does it work on L21C432 for rollback to Nougat ?
Thanks !
Click to expand...
Click to collapse
It should. I had couple chats in telegram group for 7x dev with users doing this. But they ran into trouble because they did not have good emui-5 backup images. The first part of flashing the cn nougat roll-back worked fine.
mrmazak said:
It should. I had couple chats in telegram group for 7x dev with users doing this. But they ran into trouble because they did not have good emui-5 backup images. The first part of flashing the cn nougat roll-back worked fine.
Click to expand...
Click to collapse
So it's not guaranteed to work? Is it better if I wait or flash?
DaRkLinK_35 said:
So it's not guaranteed to work? Is it better if I wait or flash?
Click to expand...
Click to collapse
Up ?
DaRkLinK_35 said:
Up ?
Click to expand...
Click to collapse
I used it . It worked for me.
Ymmv
Works for BND-AL10?
verma.avesh said:
Works for BND-AL10?
Click to expand...
Click to collapse
Yes it should
In futures if huawei release new modem say do I need to revert to stock first then flash treble aosp? Thx
optionalmgrr.la said:
In futures if huawei release new modem say do I need to revert to stock first then flash treble aosp? Thx
Click to expand...
Click to collapse
I expect , in order to take advantage of ota improvements such as updated modem you will need to be back on stock, yes
I was able to successfully update to orea form nouguat following your guide without issue. so do now can i relock or do i need to do the first part of the guide also
shadowsiul said:
I was able to successfully update to orea form nouguat following your guide without issue. so do now can i relock or do i need to do the first part of the guide also
Click to expand...
Click to collapse
Umm, No.
The guide is for going both ways (upgrade, and downgrade).
No need to relock bootloader either. Unless you want to.
mrmazak said:
Umm, No.
The guide is for going both ways (upgrade, and downgrade).
No need to relock bootloader either. Unless you want to.
Click to expand...
Click to collapse
if i relock bootloader after going total stock will i get official ota and if so will i able install thos ota since i saw verification failed for many people
Mohan0004 said:
if i relock bootloader after going total stock will i get official ota and if so will i able install thos ota since i saw verification failed for many people
Click to expand...
Click to collapse
Someone else has already posted that they received the ota while unlocked, so not nessisary
Nougat to Oreo FullOTA
successfully done the upgrade from Nougat to Oreo on AL-10 Indian version with the method on page-1
kavena78 said:
successfully done the upgrade from Nougat to Oreo on AL-10 Indian version with the method on page-1
Click to expand...
Click to collapse
Let me ask you something, please.
Did it work in one step, or did you have to do install a second time from Oreo in order to get it fully done?
I ask because my first time I used this I had to repeat the install process again from Oreo to get the data part of install to flash. I made changes (no longer shortening the file names to fit the script, instead change the script to fit the file names) and second time it worked for me.
If confirmed worked for you the new way, then I can remove the large warning (somewhat confusing) text from the first post.
mrmazak said:
Let me ask you something, please.
Did it work in one step, or did you have to do install a second time from Oreo in order to get it fully done?
I ask because my first time I used this I had to repeat the install process again from Oreo to get the data part of install to flash. I made changes (no longer shortening the file names to fit the script, instead change the script to fit the file names) and second time it worked for me.
If confirmed worked for you the new way, then I can remove the large warning (somewhat confusing) text from the first post.
Click to expand...
Click to collapse
It's worked in 1st attempt used the HWOTA7. Appreciate your efforts
DISCLAIMER: I will not be responsible of any issues you could face following this how-to. You do it at your own risk!
Here is a guide to root Honor 8 B521 Oreo. I did this on FRD-L09C432B521. Even if i think the "easy method" should work with other iteration of the phone (L02, L19, ...), I am not sure ramdisk is the same for all so test it if you feel lucky and please report if it works or not.
Requirements:
- Honor 8 running Oreo
- Unlocked Bootloader
- adb and fastboot installed on your computer (https://forum.xda-developers.com/android/software-hacking/alpha-adb-fastboot-installer-windows-t3637255 (Hit the thanks button)
Long method: (should work for all honor 8)
1 -- Visit http://pro-teammt.ru/firmware-database/ and search your exact build (FRD-L09C432B521 for me). If you have several phones listed for your build, click the name of the build on the left. This will open an xml file on the first line of which you will see the exact model it is for.
2 -- Once you know which firmware is yours, click on "filelist". This will list the files for this build and theirs url. Copy the link pointing to "update.zip" (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3109/g1699/v159456/f1/full/update.zip for me). Decompress it wherever you want.
3 -- Download and run Huawei Update Extractor (Hit the thanks button) . Untick "verify header checksum" in "settings" tab.
4 -- In the "extract" tab, click on "..." and select "update.app" in the previously "update.zip" decompressed folder.
5 -- Files from "update.app" should now be listed. Find "ramdisk" and right click on it. Choose "extract" and you will be able to save the file wherever you want. Copy this file on your phone.
6 -- On your phone: Go to Magisk thread (Hit the thanks button) and download the latest magisk manager. Install it. Grant permission to the manager to access your storage in phone settings > applications.
7 -- Run Magisk Manager, it will ask you if you want to install the zip. Select "Yes". It will now ask if you want to flash the zip or to patch a boot image, choose this last one. Point to the ramdisk img you previously copied on your phone. Magisk manager will now patch it and create a new "patched_boot.img" file. Copy this on your computer.
8 -- On your computer: Open a command prompt where you copied "patched_boot.img". Enter the following commands:
adb reboot bootloader (your phone will reboot in bootloader mode)
fastboot flash ramdisk patched_boot.img
fastboot reboot
9 -- Your phone will now reboot and be rooted. To unroot, repeat the process (8) with your stock ramdisk (the one extracted with Huawei Update Extractor)
Easy method
If your build is FRD-L09C432B521, FRD-L02C432B521, FRD-L04C567B520 or FRD-L09C432B562, you can use these already patched ramdisk.img.
patched_RAMDISKL09B521.img
stock_RAMDISKL09B521.img
patched_RAMDISKL02B521.img thanks to @Sharath007for the file
patched_RAMDISKL04B520.img thanks to @macbuggo for the file
stock_RAMDISKL04B520.img thanks to @macbuggo for the file
patched_RAMDISKL09B562.img thanks to @topscorer for the file
stock_RAMDISKL09B562.img thanks to @topscorer for the file
On your computer: Open a command prompt where you downloaded "patched_RAMDISKL09B521.img" (or L02/L04 ramdisk) .
Enter the following commands:
adb reboot bootloader (your phone will reboot in bootloader mode)
fastboot flash ramdisk patched_RAMDISKLXXBXXX.img (the exact name depends of the ramdisk you downloaded)
fastboot reboot
Your phone will now reboot
Go to Magisk thread (Hit the thanks button) and download the latest magisk manager. Install it.
You now got root. To unroot, repeat the process with stock ramdisk.
Worked in the first attempt.. Safety net passes..
Sharath007 said:
Worked in the first attempt.. Safety net passes..
Click to expand...
Click to collapse
Did you do this on L09? Otherwise, could you share the patched ramdisk so I can add it in OP?
stephtban said:
Did you do this on L09? Otherwise, could you share the patched ramdisk so I can add it in OP?
Click to expand...
Click to collapse
Thanks for your guide. I did it on my FRD-L02 Variant.
FRD_L02_patched_boot
Sharath007 said:
Thanks for your guide. I did it on my FRD-L02 Variant.
FRD_L02_patched_boot
Click to expand...
Click to collapse
Thanks! I added your ramdisk to OP. Do you still have unpatched version of it for easy unrooting?
delete
PremiumBlaze said:
Can't guys flash Magisk using twrp? It worked for me in android oreo.
Click to expand...
Click to collapse
You can indeed use twrp but as it is not completely functional yet, some people don't use it. Besides, Open Kirin suggest to flash their rom with fastboot so it limits the interest of having twrp.
stephtban said:
DISCLAIMER: I will not be responsible of any issues you could face following this how-to. You do it at your own risk!
Here is a guide to root Honor 8 B521 Oreo. I did this on FRD-L09C432B521. Even if i think the "easy method" should work with other iteration of the phone (L02, L19, ...), I am not sure ramdisk is the same for all so test it if you feel lucky and please report if it works or not.
Requirements:
- Honor 8 running Oreo
- Unlocked Bootloader
- adb and fastboot installed on your computer (https://forum.xda-developers.com/android/software-hacking/alpha-adb-fastboot-installer-windows-t3637255 (Hit the thanks button)
Long method: (should work for all honor 8)
1 -- Visit http://pro-teammt.ru/firmware-database/ and search your exact build (FRD-L09C432B521 for me). If you have several phones listed for your build, click the name of the build on the left. This will open an xml file on the first line of which you will see the exact model it is for.
2 -- Once you know which firmware is yours, click on "filelist". This will list the files for this build and theirs url. Copy the link pointing to "update.zip" (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3109/g1699/v159456/f1/full/update.zip for me). Decompress it wherever you want.
3 -- Download and run Huawei Update Extractor (Hit the thanks button) . Untick "verify header checksum" in "settings" tab.
4 -- In the "extract" tab, click on "..." and select "update.app" in the previously "update.zip" decompressed folder.
5 -- Files from "update.app" should now be listed. Find "ramdisk" and right click on it. Choose "extract" and you will be able to save the file wherever you want. Copy this file on your phone.
6 -- On your phone: Go to Magisk thread (Hit the thanks button) and download the latest magisk manager. Install it. Grant permission to the manager to access your storage in phone settings > applications.
7 -- Run Magisk Manager, it will ask you if you want to install the zip. Select "Yes". It will now ask if you want to flash the zip or to patch a boot image, choose this last one. Point to the ramdisk img you previously copied on your phone. Magisk manager will now patch it and create a new "patched_boot.img" file. Copy this on your computer.
8 -- On your computer: Open a command prompt where you copied "patched_boot.img". Enter the following commands:
adb reboot bootloader (your phone will reboot in bootloader mode)
fastboot flash ramdisk patched_boot.img
fastboot reboot
9 -- Your phone will now reboot and be rooted. To unroot, repeat the process (8) with your stock ramdisk (the one extracted with Huawei Update Extractor)
Easy method
If your build is FRD-L09C432B521 or FRD-L02C432B521, you can use these already patched ramdisk.img.
patched_RAMDISKL09B521.img
stock_RAMDISKL09B521.img
patched_RAMDISKL02B521.img thanks to @Sharath007for the file
On your computer: Open a command prompt where you downloaded "patched_RAMDISKL09B521.img" (or L02 ramdisk) .
Enter the following commands:
adb reboot bootloader (your phone will reboot in bootloader mode)
fastboot flash ramdisk patched_RAMDISKL09B521.img OR fastboot flash ramdisk patched_RAMDISKL02B521.img
fastboot reboot
Your phone will now reboot and be rooted
To unroot, repeat the process with stock ramdisk.
Click to expand...
Click to collapse
Thanks! work perfectly
freewind29 said:
Thanks! work perfectly
Click to expand...
Click to collapse
Don't quote entire op please.
Did not work on my phone (L09C432) with the "easy way".
Flashed patched ramdisk, no root, but at least still running.
daFlox said:
Did not work on my phone (L09C432) with the "easy way".
Flashed patched ramdisk, no root, but at least still running.
Click to expand...
Click to collapse
Sorry, I forgot a step. After you flashed the patched ramdisk, go to Magisk thread (Hit the thanks button) and download the latest magisk manager. Install it. This should work then. Please tell me if it helped.
OP edited with this new step.
Worked great here for FRD-04, one thing to add
You may have to restart your phone to be able to see the patched file via MTP in order to copy it to your PC.
macbuggo said:
Worked great here for FRD-04, one thing to add
You may have to restart your phone to be able to see the patched file via MTP in order to copy it to your PC.
Click to expand...
Click to collapse
Happy this works. Could you share the stock ramdisk and the patched ramdisk so I can add it in OP.
stephtban said:
Sorry, I forgot a step. After you flashed the patched ramdisk, go to Magisk thread (Hit the thanks button) and download the latest magisk manager. Install it. This should work then. Please tell me if it helped.
OP edited with this new step.
Click to expand...
Click to collapse
Ahhh, okay!
Will try it this evening and report tomorrow.
daFlox said:
Will try it this evening and report tomorrow.
Click to expand...
Click to collapse
Works, thanks a lot!! (additional thanks in the original post )
stephtban said:
Happy this works. Could you share the stock ramdisk and the patched ramdisk so I can add it in OP.
Click to expand...
Click to collapse
I couldn't upload to XDA directly due to 8MB limit unfortunately, here it is if you want to put it up on your google drive or something
http://s000.tinyupload.com/index.php?file_id=10562650897614852938
This is a patched image of FRD-04C567 8.0.0.520 with Magisk 17.1
macbuggo said:
I couldn't upload to XDA directly due to 8MB limit unfortunately, here it is if you want to put it up on your google drive or something
http://s000.tinyupload.com/index.php?file_id=10562650897614852938
This is a patched image of FRD-04C567 8.0.0.520 with Magisk 17.1
Click to expand...
Click to collapse
Thanks. File and credit added to OP. Do you still have stock ramdisk for easy unrooting?
Tinyupload appears to be down, these links will last for 30 days
FRD-L04C567 8.0.0.520 ramdisk patched Magisk 17.1
https://ufile.io/nsa1h
Stock L04 520 ramdisk
https://ufile.io/34eq5
macbuggo said:
Tinyupload appears to be down, these links will last for 30 days
FRD-L04C567 8.0.0.520 ramdisk patched Magisk 17.1
https://ufile.io/nsa1h
Stock L04 520 ramdisk
https://ufile.io/34eq5
Click to expand...
Click to collapse
File added. Thx.
Hallo! Is it possible to root my FRD-L09 Honor 8 Oreo this way too? And after then can I flash/install a Stock Version with Emui 5 Android 7 Nougat and then un-root again? I need my device unrooted, because of SkyGo App (Germany) doesnt work with rootet Devices ...
If theres another way to downgrade without these operations, please let me know and maybe show me the steps for that?! Thank you so much!
Hello !
October update is available.
Lets talk about it?
Confirmed, October patch rolling! Downloading!
prannoytambe said:
Confirmed, October patch rolling! Downloading!
Click to expand...
Click to collapse
That was news yesterday?
Someone could corroborate this news .. according to the aptx function has been included "Streaming: Qualcomm aptX audio"
Souce: http://en.miui.com/thread-4235944-1-1.html
jcunltd said:
Someone could corroborate this news .. according to the aptx function has been included "Streaming: Qualcomm aptX audio"
Souce: http://en.miui.com/thread-4235944-1-1.html
Click to expand...
Click to collapse
I can confirm this:
aptx and aptX HD are now working with my MI A2 and Sony WH-1000XM2
Letitflow said:
I can confirm this:
aptx and aptX HD are now working with my MI A2 and Sony WH-1000XM2
Click to expand...
Click to collapse
anyone knows why the update size is so much smaller than the beta testers got? thanks
installations fails on my phone.
Voniaak said:
Hello !
October update is available.
Lets talk about it?
Click to expand...
Click to collapse
I noticed, when scrolling, I rarely get accidental taps. I used to get them a lot with September update.
bavmouse said:
installations fails on my phone.
Click to expand...
Click to collapse
Did you restore stock boot image and not modify the system partition?
Benjamin_L said:
Did you restore stock boot image and not modify the system partition?
Click to expand...
Click to collapse
that's possible. how can i modify ? thanks.
bavmouse said:
that's possible. how can i modify ? thanks.
Click to expand...
Click to collapse
First I need to know what you did? did you flash the patched boot image? Other apps that modify system like adblock? Did you modify build.prop?
Benjamin_L said:
First I need to know what you did? did you flash the patched boot image? Other apps that modify system like adblock? Did you modify build.prop?
Click to expand...
Click to collapse
i bricked my device and restored it with fastboot flash.
CPU frequency stuck at 100% bug still exist. Work fine for 10 mins after reboot, after that stuck at 100% again.
yes. I can confirm, that after using FP sensor, CPU stuck at 100% load. :/
Why do we need to repeat this in this thread. Everything has already been mentioned before in other threads.. Doesn't help when someone is looking for information
Benjamin_L said:
First I need to know what you did? did you flash the patched boot image? Other apps that modify system like adblock? Did you modify build.prop?
Click to expand...
Click to collapse
Installation also fails in my phone
The things I reverted are:
Changes made by adblock
Magisk mods: emojiOne and Mi A2 Camera app (I thought it was an enhanced version)
I flashed the original boot.img
But after these steps the installation doesn't work.
Other root apps I use:
Greenify, but not for system apps
Uptodown, but it has root privileges denied always
SD Maid. I think I didn't delete anything but maybe I compacted some databases
Any ideas? Is there any way to get more detailed info about the installation error?
Thanks!
ccbz said:
Installation also fails in my phone
The things I reverted are:
Changes made by adblock
Magisk mods: emojiOne and Mi A2 Camera app (I thought it was an enhanced version)
I flashed the original boot.img
But after these steps the installation doesn't work.
Other root apps I use:
Greenify, but not for system apps
Uptodown, but it has root privileges denied always
SD Maid. I think I didn't delete anything but maybe I compacted some databases
Any ideas? Is there any way to get more detailed info about the installation error?
Thanks!
Click to expand...
Click to collapse
Before trying this, I suggest you to backup your files.
Verify the system version in Settings > System > About the device > Version number and download the same version installed in your device:
V9.6.10.0.ODIMIFE
V9.6.13.0.ODIMIFE
V9.6.13.0.ODIMIFE
V9.6.14.0.ODIMIFE
V9.6.15.0.ODIMIFE
Unzip the package (7zip works perfectly to this job) and copy the files boot.img and system.img
1) Copy system.img and boot.img into adb folder
2) go to "settings > system > developer ... > USB deployment and enable it
3) plug you device on your computer, turn it off and turn it on again while holding power + volume down until your screen shows the Xiaomi bunny and "Fastboot".
4) in Fastboot, type "fastboot devices" and make sure your device is listed.
5) in Fastboot, type "fastboot flash system system.img" (without quotes) and wait it finishes.
6) in Fastboot, type "fastboot flash boot_b boot.img" (without quotes) and wait it finishes.
7) in Fastboot, type "fastboot flash boot_a boot.img" (without quotes) and wait it finishes.
8) in Fastboot, type "fastboot reboot" and unplug your device.
This works for me, maybe works for you.
ccbz said:
Installation also fails in my phone
The things I reverted are:
Changes made by adblock
Magisk mods: emojiOne and Mi A2 Camera app (I thought it was an enhanced version)
I flashed the original boot.img
But after these steps the installation doesn't work.
Other root apps I use:
Greenify, but not for system apps
Uptodown, but it has root privileges denied always
SD Maid. I think I didn't delete anything but maybe I compacted some databases
Any ideas? Is there any way to get more detailed info about the installation error?
Thanks!
Click to expand...
Click to collapse
Mounting system makes otas impossible already so follow the instructions before my post
New update today...
After yesterday an update was delivered, I am now offered a new update. The installation is now running. I noticed after yesterday's update that there were significant "memory / processing delays", which had previously not occurred on my device. The update is 203 mb, yesterday only 103.5mb were delivered.
Hello,
Please and thanks in advance for any assistance!
I've successfully rooted my HD8 7th gen fire tablet, thanks to the many helpful posts here. However during some of my failed attempts while using Magisk, TWRP App, etc, I've somehow managed to wipe out my stock Recovery partition/files. I can do normal booting fine and I'm sure that I have root, as confirmed by the # at ADB shell and the Root Checker apps available.
I've tried the following:
-Entered Fastboot mode and tried several commands there: always resulting in a 'the command you input is restricted on locked hw' (So, obviously, my bootloader is locked (but I've overwritten it somehow, so it makes me think that at some point I was able to unlock it and overwrite it?)
-Flashfire, TWRP, Magisk and Flashify apps - successful messages every time I try, but no joy when trying to enter recovery mode (it's possible I'm trying to flash the wrong recovery.img file? - does anyone have it and what is it's size? i searched my tablet for the file and found two: one 17mb and the other 8mb - both "flashed" successfully, but no joy when trying to boot into them)
-adb su commands
-Giving up and doing a full Factory Restore via the GUI - it just tries to reboot to the recovery mode, which doesn't exist, so i can't do anything.
-Giving up and doing a full Factory Restore via Fastboot mode - 'the command you input is restricted on locked hw'
I was so happy I was able to obtain root, but if something gets wonky or I decide to try the much raved about resurrection image, i need to have the recovery boot available if/when everything goes wrong.
Please and thanks again for any advice.
Daveychan said:
Please and thanks again for any advice.
Click to expand...
Click to collapse
It's fairly simple but cumbersome to recreate recovery with root. You need to locate the original install-recovery script for your Rom. You may search in /etc or /system/etc . Most likely though your SuperSu deleted it.
So you download your particular Rom version from amazon, unpack it into a system image via mtk-extractor, mount that system image, and find the files.
You can mount this extracted system.bin either on Linux, or directly on your tablet. Just push it to /sdcard, and do this: https://stackoverflow.com/questions/36448234/how-to-mount-a-loop-device-in-android
Then you run the full install-recovery script which will patch your boot.img into recovery partition.
Alternatively, you can beg someone here to dump their HD8 2017 recovery, and upload the image here. So you can dd it in using root into the appropriate partition.
See, I told you - it's all very simple !
Edit: @dondraper23 - can you help a fellow XDA-er? Just dd your HD8 2017 recovery, and post it here.
Code:
dd if=/dev/block/platform/soc/by-name/recovery of=/sdcard/recovery.img
Then zip it, and post it here.
Thank you very much for the fast reply. Much appreciated!
I’ll give this a try ASAP and post back.
If anyone has the recovery.img for the HD8 Gen7, please do post it.
Thank you again!
Okay, i've spent several hours on this and I need to ask for more help.
I managed to get the system.img file from the Amazon .bin as you described. (I used the MTK Extractor for that. It's 1.57 GB by the way.) Next, I moved the system.img file to my Fire's SD card, then I connected the Fire to my Linux, and mounted the system.img file in Linux so I can see the file directory.
I can now see the install-recovery.sh file, located in the /bin folder of the mounted image, but it's read-only. Even by opening to that path via terminal with SU and trying to chmod 777 the file, it's still locked as read-only.
So, I don't know what to do next. I can't copy the file, and I don't see how to run the file via Fire anyway. (Was I supposed to somehow mount the system.img file via ADB commands and then run it that way? If so, I don't know how to do that.)
Sorry if I've asked something obvious or silly. As before, I appreciate the assistance!
Please and Thanks!
Daveychan said:
Okay, i've spent several hours on this and I need to ask for more help.
I managed to get the system.img file from the Amazon .bin as you described. (I used the MTK Extractor for that. It's 1.57 GB by the way.) Next, I moved the system.img file to my Fire's SD card, then I connected the Fire to my Linux, and mounted the system.img file in Linux so I can see the file directory.
I can now see the install-recovery.sh file, located in the /bin folder of the mounted image, but it's read-only. Even by opening to that path via terminal with SU and trying to chmod 777 the file, it's still locked as read-only.
So, I don't know what to do next. I can't copy the file, and I don't see how to run the file via Fire anyway. (Was I supposed to somehow mount the system.img file via ADB commands and then run it that way? If so, I don't know how to do that.)
Sorry if I've asked something obvious or silly. As before, I appreciate the assistance!
Please and Thanks!
Click to expand...
Click to collapse
Sure, just copy that install-recovery.sh file to your tablet, into /data/local/tmp. There is also another file you will need, it's /system/recovery-from-boot.p . Copy this one to /data/local/tmp as well. Then edit your install recovery script, to point to this /data/local/tmp/recovery-from-boot.p . Then just su, chmod 777 your install recovery script, and run it. It should take your boot, and patch it into recovery using recovery-from-boot.p patch file.
Thank you for the fast reply. But because that sh file its read-only, I can't open it or copy it.
Error when running the script
Hello again,
I managed to get around the read-only problem (opening everything as Superuser in Linux was the trick to making that work, for other noobs who may be following along with my pain here.)
I grabbed those two files as you indicated and followed the instructions. Unfortunately I was met with a ton of error messages. Here they are:
=====================
[email protected]:/data/local/tmp # /data/local/tmp/install-recovery.sh
contents of partition "/dev/block/platform/mtk-msdc.0/by-name/recovery" didn't match EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:7022592:38eeb844c578f6bbfb6edf8ddf7ba1112200a25c
file "EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:7022592:38eeb844c578f6bbfb6edf8ddf7ba1112200a25c" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
patch EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:4720640:9dc6d0ebab0b237a7b2f31ae0fabe026da83cda5: LoadPartitionContents called with bad filename (EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery)
contents of partition "/dev/block/platform/mtk-msdc.0/by-name/recovery" didn't match EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery
contents of partition "/dev/block/platform/mtk-msdc.0/by-name/boot" didn't match EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:4720640:9dc6d0ebab0b237a7b2f31ae0fabe026da83cda5
source file is bad; trying copy
failed to stat "/cache/saved.file": No such file or directory
failed to read copy file
=====================
I'm attaching the two files i pulled from the system.img file - as converted from the .bin file downloaded from Amazon (as above), in case you are still willing to help out and can take a look. (I edited the install-recovery.sh file to the correct path already, so it's not the original anymore.)
MUCH APPRECIATED!
Thank you!
Daveychan said:
Hello,
Please and thanks in advance for any assistance!
I've successfully rooted my HD8 7th gen fire tablet, thanks to the many helpful posts here. However during some of my failed attempts while using Magisk, TWRP App, etc, I've somehow managed to wipe out my stock Recovery partition/files. I can do normal booting fine and I'm sure that I have root, as confirmed by the # at ADB shell and the Root Checker apps available.
I've tried the following:
-Entered Fastboot mode and tried several commands there: always resulting in a 'the command you input is restricted on locked hw' (So, obviously, my bootloader is locked (but I've overwritten it somehow, so it makes me think that at some point I was able to unlock it and overwrite it?)
-Flashfire, TWRP, Magisk and Flashify apps - successful messages every time I try, but no joy when trying to enter recovery mode (it's possible I'm trying to flash the wrong recovery.img file? - does anyone have it and what is it's size? i searched my tablet for the file and found two: one 17mb and the other 8mb - both "flashed" successfully, but no joy when trying to boot into them)
-adb su commands
-Giving up and doing a full Factory Restore via the GUI - it just tries to reboot to the recovery mode, which doesn't exist, so i can't do anything.
-Giving up and doing a full Factory Restore via Fastboot mode - 'the command you input is restricted on locked hw'
I was so happy I was able to obtain root, but if something gets wonky or I decide to try the much raved about resurrection image, i need to have the recovery boot available if/when everything goes wrong.
Please and thanks again for any advice.
Click to expand...
Click to collapse
You shuld try:
-Extract an ota update in a folder
-Run from the folder with the extracted files
Code:
fastboot flash boot boot.img
the recovery is in boot.img, doing this helped me on a similar situation
Thanks to @bibikalka for pointing me to this thread
On the 7th gen fire hd8 TWRP doesn't work yet
t0x1cSH said:
You shuld try:
-Extract an ota update in a folder
-Run from the folder with the extracted files
Code:
fastboot flash boot boot.img
the recovery is in boot.img, doing this helped me on a similar situation
Thanks to @bibikalka for pointing me to this thread
On the 7th gen fire hd8 TWRP doesn't work yet
Click to expand...
Click to collapse
It's not enough to reflash boot.img ! Recovery is created on boot by patching boot.img, but the OP's fire has messed up recovery creation scripts due to SuperSu. So he needs to either re-run the recovery creation script manually - which seems to produce errors, or simply flash a full recovery image - hence my request to extract it from a fire with working recovery.
Hey, I'll pull the recovery off mine tomorrow
NFSP G35 said:
Hey, I'll pull the recovery off mine tomorrow
Click to expand...
Click to collapse
That would be fantastic! Thank you much!
Here you go
Daveychan said:
That would be fantastic! Thank you much!
Click to expand...
Click to collapse
Just FYI, to flash this image file into recovery (assuming you have the recovery image sitting in /sdcard/recovery.img):
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/mtk-msdc.0/by-name/recovery
bibikalka said:
It's not enough to reflash boot.img ! Recovery is created on boot by patching boot.img, but the OP's fire has messed up recovery creation scripts due to SuperSu. So he needs to either re-run the recovery creation script manually - which seems to produce errors, or simply flash a full recovery image - hence my request to extract it from a fire with working recovery.
Click to expand...
Click to collapse
this is the recovery partition straight from my hd8 2017
but i am very curious about a thing, if you look at booth the boot.img and the recovery partition they contains exactly the same data, in the same structure so why cant he simply flash boot.img?
t0x1cSH said:
this is the recovery partition straight from my hd8 2017
but i am very curious about a thing, if you look at booth the boot.img and the recovery partition they contains exactly the same data, in the same structure so why cant he simply flash boot.img?
Click to expand...
Click to collapse
They do have a lot of similarities, that's why recovery is created by patching boot via a relatively small patch file. But, they are still different! That recovery menu is contained entirely within the recovery image, while the boot image does not do that.
Just to add to this, you don't need to flash the boot.img to use install-recovery.sh.
You can also modify the script to read boot from an img file.
k4y0z said:
Just to add to this, you don't need to flash the boot.img to use install-recovery.sh.
You can also modify the script to read boot from an img file.
Click to expand...
Click to collapse
Do you care to post a script that does that, and writes into a recovery image file? The syntax of that patch command is a bit messy, so I would not mind having a debugged working script
Hello again,
My apologies for the delay, work was busy this week, and I couldn't find the time to check the solution until now.
I'm so VERY HAPPY to report that all worked well, and the recovery.img and the command line you provided worked perfectly. (WOW! Thank you!)
For those who want the details, the message after the command in the terminal was:
==
#dd if=/sdcard/recovery.img of=/dev/block/platform/mtk-msdc.0/by-name/recovery
----
34816+0 records in
34816+0 records out
17825792 bytes transferred in 1.159 secs (15380320 bytes/sec)
==
I then did a full power down, and then a started it up again while holding the top-left Volume key and the Power key, and look at that! I'm sitting at the Amazon system recovery screen again! <insert YAY! here>
I'm not sure if it matters, but I thought I'd mention it. At the bottom of the screen in orange letters, it says:
===
E:Error in /cache/recovery/last_kmsg
(No space left on device)
===
So, after a little bit of searching, I selected "wipe cache partition", rebooted again into recovery, and the error is gone now.
Another normal reboot started the "Optimizing apps..." thingy, but it finished quickly and I can confirm that all my stuff is still there. Just to be sure, I did another reboot to recovery, no error messages this time, and then another regular reboot, with no optimizing.
It appears that everything in my world is good again!
My sincerest gratitude and appreciation to all who helped contribute and support this solution.
THANK YOU VERY MUCH!
Daveychan said:
the much raved about resurrection image .
Click to expand...
Click to collapse
Out of curiosity, what is this? There is an image, other than stock, for the 7th Gen HD8?
Resurrection-remix
xnatex21 said:
Out of curiosity, what is this? There is an image, other than stock, for the 7th Gen HD8?
Click to expand...
Click to collapse
It's a WIP for the HD8 I've read. My friend has this on his HD7 and swears it's twice as fast as the regular.
Here's some info:
https://forum.xda-developers.com/kindle-fire-hd/7-development/rom-resurrection-remix-5-1-x-t3234535
and here:
https://forum.xda-developers.com/le-pro3/development/9-0-resurrection-remix-v7-0-t3894663