[fix] easy fix for balong issue - P8lite Q&A, Help & Troubleshooting

Hi!
i create a software to fix Balong issue after flashing a ROM.
Download the zip, extract the folder then only need to follow the steps in software!
Check the pictures bellow!
If fails check if cust image is properly installed before execute the software again.
Tell me if worked for you!
.

Thanks.

I've installed TWRP 3.1.1-0, but when I use your software it says "error: no devices/emulators found", even if I put the correct cust path

persona78 said:
Hi!
i create a software to fix Balong issue after flashing a ROM.
Download the zip, extract the folder then only need to follow the steps in software!
Check the pictures bellow!
If fails check if cust image is properly installed before execute the software again.
Tell me if worked for you!
.
Click to expand...
Click to collapse
Hi
After an update (official!) I re-encountered BALONG. After using your marvelous tool, it worked again, but there's no need to reset device (as written on CMD).
In addition, for the ones that get the error "no device attached" or something similar, you've only to reboot to TWRP, connect the phone to Windows and press Win+X, click on "device manager", look for "android device" or something similar. Right click on it and select "update driver", click the second option and than select that you already have the CD driver. You'll see a list: select "ADB composite device" and than finish: you've done!
Ah, I was about to forget: thank you!
Regards,
F

fixed
Hi.
Thanks for fast answer. I could fix the problem.
I downloaded the EMUI 3.1 as Magyar Telekom firmware from an arabic server cause ru huawei servers doesnt work lol. So I downloaded it I extracted boot, recovery, system, cust img files from UPDATE.APP with Huawei AppImage Extractor application. I flashed these with fastboot (Not TWRP, not huawei recovery). Fastboot from computer. Ok. But at the moment SIM does not work. I upgraded the system from Huawei update from settings (not recovery, system settings). After update the ROM and SIM is work perfectly.
Btw thanks your answer, topices too. This is a big help from you.
Have a nice day, Balázs.

How Can i use it for Meanaf Localization ????
How Can i use it for Meanaf Localization ????
@persona78
can you provide me Tool To fix Balong
Countryakistan
Mobile:ALE-L21
ROM:C185

Hello thanks for creating such tool
I've tried to use it but i get this error after TWRP boot :
mount: No such file or directory
mkdir: '/cust/hw': No such file or directory
ln: cannot create symbolic link from '/cust/hw/eu' to '/cust/hw/meafnaf': No such file or directory
Is there any solution for this?

-Mouhammad said:
Hello thanks for creating such tool
I've tried to use it but i get this error after TWRP boot :
mount: No such file or directory
mkdir: '/cust/hw': No such file or directory
ln: cannot create symbolic link from '/cust/hw/eu' to '/cust/hw/meafnaf': No such file or directory
Is there any solution for this?
Click to expand...
Click to collapse
Which Cust Path Do you Want?
hw/meafnaf?

MohmmadUzairKhan said:
Which Cust Path Do you Want?
hw/meafnaf?
Click to expand...
Click to collapse
The program detected this path : cust/hw/meanfaf
Is this what you mean?

-Mouhammad said:
The program detected this path : cust/hw/meanfaf
Is this what you mean?
Click to expand...
Click to collapse
What Do You Want?
hw/eu?

MohmmadUzairKhan said:
What Do You Want?
hw/eu?
Click to expand...
Click to collapse
Do you know what cuases this error?

Thank you its working excellent . And wipe is not needed. Tnx again ?

pls say me
how can i fix it with opened bootloader? must i flash cast?

Doesn't work. Did everything by the instructions. Twice.

Related

Can't flash KRT16S (from KRT16O)

Hi everybody
When the factory images came out, I flash my N4 with the stock factory images that we used to find here : https://developers.google.com/android/nexus/images#occamkrt16s because it is now the KRT16S build
After a few days, when the KRT16S build came out, I was proposed in my phone to update it. I downloaded it, tried to flash it but nothing worked, I'm still on KRT16O and the OTA doesn't appear anymore... Then I remembered that I flashed a mod found here : http://forum.xda-developers.com/showthread.php?t=2527525 (that's a great mod btw) so I guessed that I could reflash the undo file available on the thread, flash the ota file dl mannually (I attached it in this thread) which I did through TWRP. Then I was able to see the problem, it told me that, from what I remember, Agenda.apk was missing (I think it's diary in english, not sure) then I remembered that I manually deleted some apps I never use (diary is one of them...)
So, what's next, shall I reflash the gapps to finally update my phone
Thanks for your help :laugh:
Are you using latest TWR? I did it ok
Sent from my Nokia 3210
howard bamber said:
Are you using latest TWR? I did it ok
Sent from my Nokia 3210
Click to expand...
Click to collapse
I run the 2.6.3.3 version I guess it's the latest because I flashed it a few days ago
I installed the few missing apps that i uninstalled and Calendar didn't create any error. This time it EmailGoogle.apk... I transformed it as a system application and I went to /system/app to change its name from com.google.android.apps.email or something to EmailGoogle.apk, didn't work... But I'm sure I'm on the way to achieve it :victory:
Here's the whole mesage :
Code:
Updating partition details...
Installing '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Checking for MD5 file...
Skipping MD5 check : no MD5 dile found.
Verifying current system...
"/system/app/EmailGoogle.apk" has unexpected contents.
E:Error executing updater binary in zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip
Error flashing zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Updating partition détails...
[CENTER][COLOR="Red"][SIZE="4"]Failed[/SIZE][/COLOR][/CENTER]
azertguigui said:
I run the 2.6.3.3 version I guess it's the latest because I flashed it a few days ago
I installed the few missing apps that i uninstalled and Calendar didn't create any error. This time it EmailGoogle.apk... I transformed it as a system application and I went to /system/app to change its name from com.google.android.apps.email or something to EmailGoogle.apk, didn't work... But I'm sure I'm on the way to achieve it :victory:
Here's the whole mesage :
Code:
Updating partition details...
Installing '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Checking for MD5 file...
Skipping MD5 check : no MD5 dile found.
Verifying current system...
"/system/app/EmailGoogle.apk" has unexpected contents.
E:Error executing updater binary in zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip
Error flashing zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Updating partition détails...
[CENTER][COLOR="Red"][SIZE="4"]Failed[/SIZE][/COLOR][/CENTER]
Click to expand...
Click to collapse
You can not install an apk in recovery. Use ES File Explorer to install the apk. In addition, to avoid the error, while you are in recovery, select "Mount" and uncheck the box "System" when flashing a zip file.
taodan said:
You can not install an apk in recovery. Use ES File Explorer to install the apk. In addition, to avoid the error, while you are in recovery, select "Mount" and uncheck the box "System" when flashing a zip file.
Click to expand...
Click to collapse
I did not installed it with TWRP, I did it by simply openning the apk while my phone is on, it installed the Email app...
But thanks anyway for the mount function, I'll give a try
azertguigui said:
I did not installed it with TWRP, I did it by simply openning the apk while my phone is on, it installed the Email app...
But thanks anyway for the mount function, I'll give a try
Click to expand...
Click to collapse
Simpler way to update without OTA package:
Download the factory image, and before running the flash-all script, open it with a text editor and change "fastboot -w update" to "fastboot update"
MameTozhio said:
Simpler way to update without OTA package:
Download the factory image, and before running the flash-all script, open it with a text editor and change "fastboot -w update" to "fastboot update"
Click to expand...
Click to collapse
You mean with the sdk? I don't know how to use it, when I flash something, it's with the recovery or the nexus root toolkit..
-From my Nexus 4-
UP
azertguigui said:
UP
Click to expand...
Click to collapse
**
azertguigui said:
UP
Click to expand...
Click to collapse
azertguigui said:
**
Click to expand...
Click to collapse
Not sure what you're trying to say here..
azertguigui said:
You mean with the sdk? I don't know how to use it, when I flash something, it's with the recovery or the nexus root toolkit..
-From my Nexus 4-
Click to expand...
Click to collapse
Try avoiding toolkits as they can lead to problems and leave you stuck with no idea what to do. Yes he is referring to the sdk. Only the platform-tools folder in the sdk is required so if you don't wanna bother downloading the complete file, just download the platform-tools from here and extract it to an appropriate location. Extract and move the Factory Image that you downloaded to your platform-tools directory. If you don't want your data to be erased, edit the flash-all script with a text editor and remove -w and save. Plug in your phone. Make sure you have the drivers installed. In the platform tools directory, press shift+right click> open command prompt here. Type adb devices. You will see "device <Serial Number>. If you don't, your drivers are faulty. Then type adb reboot bootloader. Once your phone has rebooted into bootloader, make sure that it is being detected by typing fastboot devices. You should see an output similar to adb devices. Now simply run the flash-all script and let it do its work. Reboot after flashing is completed.
Hope this helps!
try search any youtube on how to flash factory images to your device. I guess u'll find lots.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Words of advice, learn how to use ADB instead of relying solely on toolkits. It's very simple actually.
Now there's a simple way to update which is sideload. Oh and btw to sideload, you still need ADB though (this is why learning ADB is VERY important to us, the N4 users). Here is a video tutorial on how to perform adb sideload. All the links are attached in his youtube video.
Ibrahim.Rahman said:
Not sure what you're trying to say here..
Click to expand...
Click to collapse
:laugh: I quoted my own UP post but it told me that my post should have at least 2 letters, so I taped the spacebar twice and it wrote this
Ibrahim.Rahman said:
Try avoiding toolkits as they can lead to problems and leave you stuck with no idea what to do. Yes he is referring to the sdk. Only the platform-tools folder in the sdk is required so if you don't wanna bother downloading the complete file, just download the platform-tools from here and extract it to an appropriate location. Extract and move the Factory Image that you downloaded to your platform-tools directory. If you don't want your data to be erased, edit the flash-all script with a text editor and remove -w and save. Plug in your phone. Make sure you have the drivers installed. In the platform tools directory, press shift+right click> open command prompt here. Type adb devices. You will see "device <Serial Number>. If you don't, your drivers are faulty. Then type adb reboot bootloader. Once your phone has rebooted into bootloader, make sure that it is being detected by typing fastboot devices. You should see an output similar to adb devices. Now simply run the flash-all script and let it do its work. Reboot after flashing is completed.
Hope this helps!
Click to expand...
Click to collapse
Thanks, I'll give a try
saifulh2304 said:
try search any youtube on how to flash factory images to your device. I guess u'll find lots.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
arffrhn said:
Words of advice, learn how to use ADB instead of relying solely on toolkits. It's very simple actually.
Now there's a simple way to update which is sideload. Oh and btw to sideload, you still need ADB though (this is why learning ADB is VERY important to us, the N4 users). Here is a video tutorial on how to perform adb sideload. All the links are attached in his youtube video.
Click to expand...
Click to collapse
thanks guys, I'm gonna find tutorials on the web like the one you pointed to me
azertguigui said:
:laugh: I quoted my own UP post but it told me that my post should have at least 2 letters, so I taped the spacebar twice and it wrote this
Click to expand...
Click to collapse
Haha right!
Sent from my Nexus 4 using xda app-developers app

[Utility] Android boot Manager APK

Android Boot Manager (ABM), my goal is to make the procedure (Backup, Unpack, Edit, Repack and Flashe boot.img or recovery.img) so easy and accessible to all users without resorting to the command prompt , only a single click to get a quick and successful outcome at the same time .
This is the third version of the program.
Source (GITHUB SOURCE https://github.com/aToxyD/android_boot_image_manager_apk).
WHAT'S NEW
- Some optimization.
- Add new Text Editor with high syntax.
THANKS
* xiaolu, original author of boot.img tool(GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools).
* Modding.MyMind, for his heavily modification of boot.img tool.
* Tah Wei Hoon, for TextWarrior.
* Dmytro Tarianyk, for Android Floating Action Button.
* Anthony Restaino, for Grant.
IMPORTANT
- Root is only necessary for Unpacking boot patched by "superSu or Magisk" and Backup/Flash Operations, so if you want to unpack stock boot or you have your favorite flasher apk like "Rachr", if so you dont need to check "Root Access" in settings menu.
- Please uninstall any previous version of ABM before installing the newer.
I do not like people to coming here and take what they wanted and leave like a thief , at least leave a comment. . .
This work is for all, so help your self.
atoxyd said:
Android Boot Manager (ABM), my goal is to make the procedure (Backup, Unpack, Edit, Repack and Flashe boot.img or recovery.img) so easy and accessible to all users without resorting to the command prompt , only a single click to get a quick and successful outcome at the same time .
This is the second version of the program.
WHAT'S NEW
- Corrected some bugs related to compatibility with Android 6.
- Use xiaolu mkbootimg tools (GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools)
TODO
- add support to x86, mips arch.
- add support to put files to unpacked folder.
- add support to combinedboot , in Xperia device recovery ramdisk is combined with system ramdisk.
IMPORTANT
- The apk need root access to work.
- Note that make change by adding files to unpacked folder with root explorer, the owner will be root and the apk will not work, if you do this you must change the owner to ABM apk.
THANKS
* xiaolu, original author of boot.img tool(GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools).
* modding.MyMind, for his heavily modification of boot.img tool.
* @bigsupersquid for his support and motivate from the beginning.
Click to expand...
Click to collapse
mtk support?
lixia1998 said:
mtk support?
Click to expand...
Click to collapse
Certainly I am working on this , but you should help me.
New version won't install on Kit Kat
PiggyFlooper said:
New version won't install on Kit Kat
Click to expand...
Click to collapse
Okay my friend, try to uninstall the old version, and tell me.
atoxyd said:
Okay my friend, try to uninstall the old version, and tell me.
Click to expand...
Click to collapse
You were right, I'll start project tonight editing ramdisk on my LG Volt
Are extracted files accessible in file system? I can't find them
levone1 said:
Are extracted files accessible in file system? I can't find them
Click to expand...
Click to collapse
Unpacked to /data/local/ABM
PiggyFlooper said:
Unpacked to /data/local/ABM
Click to expand...
Click to collapse
But beware when you add new files to the unpacked folder , you must take into account that owner will be. root , so you must set owner to ABM apk.
atoxyd said:
But beware when you add new files to the unpacked folder , you must take into account that owner will be. root , so you must set owner to ABM apk.
Click to expand...
Click to collapse
So I tested with twrp IMG, and successful unpack to /data/local. Then I tried with my current kernel, and nothing's happening. I get a message that's not clear to me, (screenshot 2), and no output. Any ideas?
levone1 said:
So I tested with twrp IMG, and successful unpack to /data/local. Then I tried with my current kernel, and nothing's happening. I get a message that's not clear to me, (screenshot 2), and no output. Any ideas?
Click to expand...
Click to collapse
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
atoxyd said:
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
Click to expand...
Click to collapse
That was my original thought, so I wiped data and tries again, but no different... I'll just uninstall and reinstall, and probably be fine. Thanks
atoxyd said:
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
Click to expand...
Click to collapse
Same thing after reinstall. I tried with twrp file again, and works fine, but with kernel file, error msg...
It seems that the image you want to unpack it is not an android image.
atoxyd said:
It seems that the image you want to unpack it is not an android image.
Click to expand...
Click to collapse
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Try to edit devices.xml in /sdcard/ABM directory and backup kernel using ABM app, after try to unpack boo.img backed up, you find it in /sdcard/ABM/backup directory.
levone1 said:
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Click to expand...
Click to collapse
Well my friend, try to delete space in the name of image.
Linux ..........img will be
Linix_..........img
levone1 said:
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Click to expand...
Click to collapse
Well my friend, delete space in the name of the image.
Linux 3.10....img
will be
Linux_3.10....img
Well my friend @levone1, delete space in the name of the image.
Linux 3.10....img
will be
Linux_3.10....img

Nexus 6p stuck on Google screen during boot due to replacing build.prop

I Replaced the build.prop on my rooted Google nexus 6p running Android 7.0 with the build.prop file from the pixel to run Google Assistant.The phone is now stuck on the Google logo during boot,PLEASE HELP.
Did you make a backup copy of the file before replacing it, are you rooted, and have TWRP installed?
If so, reboot to recovery, use TWRP Terminal function to copy the backup of the build.prop to the modified one.
dratsablive said:
Did you make a backup copy of the file before replacing it, are you rooted, and have TWRP installed?
If so, reboot to recovery, use TWRP Terminal function to copy the backup of the build.prop to the modified one.
Click to expand...
Click to collapse
I did not make a back up but I am rooted and have Twrp installed.What can i do from here?
If you can boot to bootloader you should be able to replace the file with a standard one.
Alden1227 said:
I Replaced the build.prop on my rooted Google nexus 6p running Android 7.0 with the build.prop file from the pixel to run Google Assistant.The phone is now stuck on the Google logo during boot,PLEASE HELP.
Click to expand...
Click to collapse
same here please help.....freaking out
1. The build.prop contains the settings for a specific build for a specific phone. You can't just replace it from another build, not to mention another phone. Well, I guess, you already know this.
2. You should know exactly which build you were on. Exactly. Then:
* What I would do, is download the factory image from https://developers.google.com/android/nexus/images#angler
o Extract it, extract the image-angler-...zip, and mount the system.img, find the build.prop and adb push it to the phone.
o Reboot
* But you can also ask somebody who has the exact build as you do, and ask for the build.prop. Then push it to the phone.
Either restore from backup or edit the buildprop (if possible) I guess.
You only needed to edit 2 lines in the buildprop though, why replace the whole thing?
Alden1227 said:
I did not make a back up but I am rooted and have Twrp installed.What can i do from here?
Click to expand...
Click to collapse
First thing's first. Since you didn't just edit your build.prop, but replaced it with another, try setting permissions.
Step 1: Boot to TWRP > Mount > Select "System"
Step 2: Advanced > File Manager
Step 3: Navigate to /system/build.prop
Step 4: Select "chmod" and type "644" (don't include quotation marks)
Reboot and see if it works. If the permissions weren't right and you didn't change them, you'd most likely be in a boot loop. If this doesn't work you can just flash your system.img again. It won't wipe your internal storage, data (installed apps, etc.) If you have custom host files for ad blocking, you may need to apply them again.
If that does not work;
I'm going to assume you were on stock Nougat. Download the factory image (same build you were on before) and unzip the file. You'll end up with a folder with another zip archive in it. Unzip that as well. Inside you'll find a file named "system.img"
Move that system.img file to your ADB/fastboot folder. Shift+Right Click that folder and select "Open command window here"
Hold volume down + power to boot into the bootloader. Connect the phone to the PC and in the command prompt, type "fastboot devices" (no quotes again. ) It should show your devices serial number. If it does, perfect. If not, check your ADB/fastboot installation.
Once you get fastboot to show your serial number all you need to do is type;
Code:
fastboot flash system system.img
That should do it. If you need any more help, just reply back.
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
RoyJ said:
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
Click to expand...
Click to collapse
It's a sparse image, you have to convert it to normal mage with simg2img. Then you can mount it normally.
istperson said:
It's a sparse image, you have to convert it to normal mage with simg2img. Then you can mount it normally.
Click to expand...
Click to collapse
Awesome, thanks!
Fixed the issue
frreak said:
same here please help.....freaking out
Click to expand...
Click to collapse
I got mine to work by flashing Android 7.0
same thing happened to me.... stuck on google even after flashing stock....
dadoc04 said:
same thing happened to me.... stuck on google even after flashing stock....
Click to expand...
Click to collapse
Flash stock boot, system and vendor img files.
Sent from my Pixel XL using XDA-Developers mobile app
Same thing happened to me at first (though I did not use the build prop from a Pixel). I just dirty flashed my ROM (Octo N) and it then got passed the Google screen and loaded with no problem. I updated my build prop manually in order to get Google Assistant to work, and it's been working great ever since.
RoyJ said:
First thing's first. Since you didn't just edit your build.prop, but replaced it with another, try setting permissions.
Step 1: Boot to TWRP > Mount > Select "System"
Step 2: Advanced > File Manager
Step 3: Navigate to /system/build.prop
Step 4: Select "chmod" and type "644" (don't include quotation marks)
Reboot and see if it works. If the permissions weren't right and you didn't change them, you'd most likely be in a boot loop. If this doesn't work you can just flash your system.img again. It won't wipe your internal storage, data (installed apps, etc.) If you have custom host files for ad blocking, you may need to apply them again.
If that does not work;
I'm going to assume you were on stock Nougat. Download the factory image (same build you were on before) and unzip the file. You'll end up with a folder with another zip archive in it. Unzip that as well. Inside you'll find a file named "system.img"
Move that system.img file to your ADB/fastboot folder. Shift+Right Click that folder and select "Open command window here"
Hold volume down + power to boot into the bootloader. Connect the phone to the PC and in the command prompt, type "fastboot devices" (no quotes again. ) It should show your devices serial number. If it does, perfect. If not, check your ADB/fastboot installation.
Once you get fastboot to show your serial number all you need to do is type;
That should do it. If you need any more help, just reply back.
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
Click to expand...
Click to collapse
Chmod 755 worked too

Huawei P9 Stock Camera on Others Phone Like S7

Require
ROOTED Device
Here is link
http://www.mediafire.com/file/rjenjjzrcv9cj8v/HwCamera_p9_gizdev.zip
Invalid ZIP. Can't flash un twrp..
Baalzeph said:
Invalid ZIP. Can't flash un twrp..
Click to expand...
Click to collapse
Yes that's why you need to be root... copy the directory's content to the right system path directly from your phone.
Marsou77 said:
Yes that's why you need to be root... copy the directory's content to the right system path directly from your phone.
Click to expand...
Click to collapse
how about you let us know the correct system path then hmmmmm.
and also is it working on your P9 or not since you haven't said so, atm I can only assume that it is from your written response
aceclift said:
how about you let us know the correct system path then hmmmmm.
and also is it working on your P9 or not since you haven't said so, atm I can only assume that it is from your written response
Click to expand...
Click to collapse
Create a directory called Hw_Camera2 in /system/app or /system/priv-app (if the 1st path give nothing) then put everything from the zip to the new directory.
I'm running Bluewei, so I can't try
Give us your result
Hi,
Sorry, but i followed your steps. Package is corrupted.

[GUIDE] [MAGISK] Root stock Oreo B520 B521 B562

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!

Categories

Resources