Related
Hi,
Today I will introduce the changes you can make to your Huawei P9 lite device.
These methods have been tested on my VNS-L31C432 and it's work on B130 update and earlier.
Sorry in advance for my incorrect syntax in inglish, i'am french user
1. Update to latest version
If your device is NOT ROOTED install the OTA update.
Otherwise place a folder named "dload" into you external or internal SD card and put update file (unzipped) on this folder.
Update for VNS-L31C432BXXX to VNS-L31C432B130 dual-sim, european version here >> https://www.hidrive.strato.com/lnk/H2ljl9lt
Turn off your device.
Hold volume up/down and power button for a long time.... Update starts automatically after this.
If your device is bricked, do not format the partition (except dalvik and cache) and go update (this update is a full version, your system will be restored).
2. Unlock Bootloader/install TWRP/Root your device
Follow this steps >> http://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701
if you have problems to get the unlocking code, log on Huawei site with your Facebook login, CHOOSE your device model and click request the code, enter the requested information, done!
TWRP 3.0.2.0 work but nandroid backup doesn't work!
For solve this, install the "TWRP Manager" app and go backup page, done!!!
(If you need set SElinux in permissive mode please read below).
3. Set SElinux to permissive mode for ever!
Download "Terminal IDE" app.
Open it and run this:
(please, type a command at a time)
Code:
su
mount -o remount,rw /system
mkdir /system/su.d
echo "#!/system/bin/sh" > /system/su.d/permissive.sh
echo "setenforce 0" > /system/su.d/permissive.sh
echo "0" > /sys/fs/selinux/enforce
chmod 755 /system/su.d/permissive.sh
restart your device, done!
4. Install Xposed Frameworks
Follow this step >> http://forum.xda-developers.com/huawei-p9lite/how-to/guide-xposed-p9-lite-t3425315 and chose this version >> http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v86-sdk23-arm64.zip (xposed-v86-sdk23-arm64 work fine, no battery drained).
5. Best Xposed module worked fine
Here are some useful and functional modules (not exhaustive list..)
-Amplify (for battery saving)
-Greenify (for battery saving)
-BootManager (for chose your apps in start on boot)
-Play Store Changelog (to display your apps and update at the opening of the Play Store)
-WiFiKeyView (view your wifi key in new tab at wifi setting. Little bug your key is not visible but copy your key and past on a note worked)
-XInternalSD (chage the path to dowload file from Chrome >> external SD) (work on other app )
-VolumeSteps+ (If you find that your volume increases too quickly, This module add steps in the volume bar! Customisable)
-ActivityForceNewTask (Force app open in correct app)
-Force Immersive Mode (Force immersive mode in your app, customisable)
-VirtualSensor (Material emulation of gyroscop, not worked with pogo dev running for this isue)
-AdBlocker and Lucky Patcher Module (I'm not sure that really works..)
6. Use your External SD on Internal (Full supported!!)
This trick enable the official feature "adoptable storage" on your Marshmallow with EMUI. better than Link2SD.
-Connect your device in your PC.
-Run ADB and run this comand:
Code:
adb shell
sm list-disks
you will see a number, that is the identifier of your SD card. For example "159,49".
Run this comand (replace YOUR_SD_IDENTIFIER ):
Code:
sm partition disk:YOUR_SD_IDENTIFIER mixed:50
Done, your external SD have 50% of memory for external and 50% for internal emulation.
Next, appointment in your storage settings and check the total capacity of the device! It may appear 0.00 o available, it's just a visual bug don't worries
Use a "DiskInfo" app or a file explorer for see correctly values.
7. BONUS play the walking dead season 1 and 2 on your P9 lite
I love this game! But device not suported..
the only solution is to take a file from the game with the unlocked level ...
Version named "Mali".
I hope you enjoyed my guide if you have questions or other tricks leave a comment.
Thanks!
nice guide, thinking myself do one like this, but can be improved... add multi user, multi window, calling recorder, substratum/layer support, build.prop mods, smart-e, smart cover etc
Therand said:
...
Hold volume up/down and power button for a long time.... Update starts automatically after this.
...
Click to expand...
Click to collapse
I was trying this some time ago...
With TWRP, I was just getting booted into TWRP. Is there something I'm doing wrong or is it just me? I would appreciate any suggestions.
Thank you Snapdesign, If you have more info to add , I would edit the post and I would quote you.
Zeruno, TWRP, stock recovery and stock updater some many diferent. if you don't remove it, you have full acces on it.
Your device is shutdown, hold volume up + volume down + power and don't release it before the updater screen appears!
normally it works...
Therand said:
Thank you Snapdesign, If you have more info to add , I would edit the post and I would quote you.
Zeruno, TWRP, stock recovery and stock updater some many diferent. if you don't remove it, you have full acces on it.
Your device is shutdown, hold volume up + volume down + power and don't release it before the updater screen appears!
normally it works...
Click to expand...
Click to collapse
Yep there's my problem -- updater screen never comes but TWRP loads instead. I wonder if there is some adb command?! That would solve a problem.
i do not think there is an command to go in the updater..
Wait for a more positive response from another user
Or try this at your risk...
Put any file for update (update.app, META-INF, ...) On a .zip archive named "update.zip" and place in your adb folder.
Connect your device on PC launch adb and run this:
Code:
Adb reboot bootloader
Wait for see bootloader screen and run:
Code:
Adb sideload update.zip
I not tested personally this method...
Otherwise place a folder named "dload" into you external or internal SD card and put update file (unzipped) on this folder.
Update for VNS-L31C432BXXX to VNS-L31C432B130 dual-sim, european version here >> https://www.hidrive.strato.com/lnk/H2ljl9lt
Turn off your device.
Hold volume up/down and power button for a long time.... Update starts automatically after this.
If your device is bricked, do not format the partition (except dalvik and cache) and go update (this update is a full version, your system will be restored).
Click to expand...
Click to collapse
Is this the procedure if your phone is rooted but you still want to install the OTA? (My current situation)
This method work on a rooted and no-rooted device.
The root "disable" the OTA function.
Don't try OTA on stock app update in your setting if your device is rooted.
The trick to use ext sd to increase space works with both stock and root or only with root?
Inviato dal mio SM-N9005 utilizzando Tapatalk
This trick no need a su promp comand.
Su command is only available for root user.
Trick work on no root acces
EDIT: im not sur if adb shell work for guest user.. try it
After lot of test, this version Xposed Framework is not a better for P9 lite.
Version unmodified v86 work fine with resource hook activated!
The direct download link >> http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v86-sdk23-arm64.zip
Therand said:
1. Update to latest version
If your device is NOT ROOTED install the OTA update.
Otherwise place a folder named "dload" into you external or internal SD card and put update file (unzipped) on this folder.
Update for VNS-L31C432BXXX to VNS-L31C432B130 dual-sim, european version here >> https://www.hidrive.strato.com/lnk/H2ljl9lt
Turn off your device.
Hold volume up/down and power button for a long time.... Update starts automatically after this.
Click to expand...
Click to collapse
Hello,
will this trick work even with TWRP recovery or only with stock recovery? is there any other way to install OTA updates if I have TWRP and root?
SwH.85 said:
Hello,
will this trick work even with TWRP recovery or only with stock recovery? is there any other way to install OTA updates if I have TWRP and root?
Click to expand...
Click to collapse
This trick work on a rooted or stock device.
Work only with stock updater.
Is not possible to update with OTA if your device is rooted, no isue.
If you proced a manual install, your device lost the root and your bootloader re-lock automatically.
Possible to re-unlock and re-root after this update.
Therand said:
After lot of test, this version Xposed Framework is not a better for P9 lite.
Version unmodified v86 work fine with resource hook activated!
The direct download link >> http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v86-sdk23-arm64.zip
Click to expand...
Click to collapse
I'm with xposed-v86.0-sdk23-arm64 by-wanam, but in fact i see in xposed the oficial xposed-v86-sdk23-arm64.zip showing as compatible with huawei devices.
So, how can i change it, in a safe way?
Nomatrix said:
I'm with xposed-v86.0-sdk23-arm64 by-wanam, but in fact i see in xposed the oficial xposed-v86-sdk23-arm64.zip showing as compatible with huawei devices.
So, how can i change it, in a safe way?
Click to expand...
Click to collapse
Version 86 by wanam possible drain battery faster...
For use version 86 unmodifier follow steps:
1. Unistall your framework with this zip file >> http://dl-xda.xposed.info/framework/uninstaller/xposed-uninstaller-20160829-arm64.zip flash zip with TWRP recovery and reboot.
2.Install the v86 framework with TWRP recovery, reboot
3. Done
About the 6th step, is it reversible? Once I've done it, can I change it again to what it used to be?
Thank you
inrope said:
About the 6th step, is it reversible? Once I've done it, can I change it again to what it used to be?
Thank you
Click to expand...
Click to collapse
use root essentials... much easier... you can revert but be aware that you might lose some data
Hi guys, I have two questions. First, how can I move apps data from internal memory to SD card? And second, does our phone have a front camera flash? Thanks
so it is possible to use my sd card as internal storage? how will this be displayed in my os?
does it just think of it as 1 bigger internal sd or something else? just want to make sure before buying the phone .
also, is the huawei p9 lite a good phone to be rooted and used with custom firmware (e.g. supportive community etc.)
thank you very much in advance for answers!
have a nice day everybody
Kyrok said:
so it is possible to use my sd card as internal storage? how will this be displayed in my os?
does it just think of it as 1 bigger internal sd or something else? just want to make sure before buying the phone .
also, is the huawei p9 lite a good phone to be rooted and used with custom firmware (e.g. supportive community etc.)
thank you very much in advance for answers!
have a nice day everybody
Click to expand...
Click to collapse
Adoptable storage for SD card is not available in stock firmware due to EMUI security policy. But you can do it in custom firmware based on AOSP.
P9 Lite has fully functional CyanogenMod, SlimRom, Resurrection Remix, MedRom (based on stock EMUI 4.1.1 Android 6) and Revolution OS ( Bases on stock EMUI 5.0 Android 7).
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Click to expand...
Click to collapse
WARNING!!! Be careful what you do here. One mistake and the device is soft-bricked. I take no responsibility for bricked devices, lost warranty or even OTAs not working!! Booting and/or flashing files from this post is on your own risk.
Requirements
Unlocked bootloader
Yoga Tablet 3 Plus with and without LTE (YT-X703L and YT-X703F) are supported
Known Issues
WARNING! Our device uses dm-verity (verified boot). The system partition should remain read-only. Otherwise a bootloop will occur. You can flash my modified kernel or SuperSU to resolve this but OTA's are no longer possible! You have to restore a factory image or clean system backup to receive OTAs
Potentially DRM keys are lost! Pure unlocking and rooting does not cause the issue. However, there have been reports of lost DRM keys by some unknown action. It is advised to act with caution. Losing your DRM keys can lead to issues with some apps which use DRM which could then have limited or no functionality. E.g. Netflix will only stream in SD (480p). You can check with DRM info if you still have L1 security level which means DRM keys are intact.
Download
Official TWRP for YT-X703F (Wifi): twrp.me
Official TWRP for YT-X703L (LTE): twrp.me
Instructions
Install fastboot and adb on your PC, e.g. from here
Enable developer options and in there select to unlock your bootloader by enabling OEM unlock and enable USB debugging
Connect your PC to your tablet and run
Code:
adb reboot bootloader
using adb on command line. The tablet will reboot into bootloader mode where you will only see the Lenovo logo. Now you use
Code:
fastboot oem unlock-go
to unlock. This will factory reset your device
Setup the tablet again and reboot again to the bootloader
Then run
Code:
fastboot boot twrp-3.2.1-0-yt_x703f.img
to temporarily boot into TWRP. You can also flash if you are sure
Select to keep system read only when TWRP starts to avoid modification which will make OTAs impossible
Optionally flash SuperSU or Magisk in TWRP which should install system less. Keep OEM unlock enabled if you flash or modify anything
Additional Downloads
Backup of original boot, recovery and system image for YT-X703F S000936: MEGA
Modified Boot image with forceencrypt disabled and it switches off CABC fully. You need to factory reset after flashing to format data without encryption boot_yt_x703f_s000963_noforceencrypt_cabc.img (YT-X703F S000963) / boot_yt_x703l_s000963_noforceencrypt_cabc.img (YT-X703L S000963) . Use
Code:
fastboot flash boot boot_yt_x703f_s000963_noforceencrypt_cabc.img
to flash the kernel in fastboot. SuperSU or Magisk should be flashed afterwards if root is desired.
Full factory images with flash tool and instructions YT_X703F_S000689, YT_X703L_S000704, YT_X703F_S000725, YT_X703L_S000725, YT_X703F_S000734, YT_X703L_S000734, YT_X703L_S000744, YT-X703F_S000744, YT-X703L_S000963, YT-X703F_S000963 and OTA updates: MEGA (These images contain the individual boot, recovery and system images that you need to restore from any modification mentioned above)
System Updates (OTA)
In order to successfully apply Lenovo system updates after root you have to restore the original boot, recovery (if you flashed TWRP) and system partitions from your current installed version (e.g. S000744) for your variant of the tablet. This will NOT delete your apps and data but will unroot. Note that OTAs are block based and always check the contents of most of the partitions. This means that all of these partitions (except your data) have to be original and have to be on the exact same version (e.g. S000734) for the update to succeed.
See here for instructions how to restore the partitions with fastboot.
Credits
@pogo1975 - for providing the factory images and fixing the AV sync issue
@launcher20 and @deecept - for testing the LTE version
TeamWin
Changelog
v4:
Now official TWRP with version 3.0.3-0
v3:
enable full disk encryption for access to the encrypted data partition
update TWRP kernel to latest S000725 version
v2:
add support for LTE variant (YT-X703L)
add further mount points to be able to backup more data
Thanks buddy! You are an absolute champion! Tell me what you need me to do and I'll do it before rooting and up load what you need.
Doing good work here.
Who wants to bet on a race between matshias and Lenovo support for who can fix the issues with this device first?
That's great and fast, I'm thinking tab 3 plus is getting hot now.
Great to see there is something moving for the yoga now. You think it will support the lte Version anytime? Or maybee even lineageos?
so you know, i've managed to install xposed thanks to this thread https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268 and is working well.
wayney said:
Thanks buddy! You are an absolute champion! Tell me what you need me to do and I'll do it before rooting and up load what you need.
Click to expand...
Click to collapse
Well if you haven't modified anything yet then it'd be great if you can boot into TWRP with system read only and then connect via ADB to the tablet with a big SD card inserted which has enough free space (4 GB).
The run the following command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
This will take a while. Then copy the file system.img from your SD card to a PC and zip it (or 7z, rar). Then upload it
Gogoho said:
Great to see there is something moving for the yoga now. You think it will support the lte Version anytime? Or maybee even lineageos?
Click to expand...
Click to collapse
The LTE variant is probably very similar and it wouldn't be much work. But I don't own the device, so I would need some help. So someone with the LTE variant who is not afraid to experiment with fastboot and adb and who can provide me with the details needed I am happy to compile a TWRP for it.
LineageOS is much much more work than TWRP. For an experienced cyanogenmod/LineageOS dev it is not much of a thing and would take only a few days, especially since it is a Qualcomm device and there are already ports for devices with SD 652. But for me this is new as well so it'll take much longer. As soon as I have time I'll look into it.
matshias said:
Well if you haven't modified anything yet then it'd be great if you can boot into TWRP with system read only and then connect via ADB to the tablet with a big SD card inserted which has enough free space (4 GB).
The run the following command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
This will take a while. Then copy the file system.img from your SD card to a PC and zip it (or 7z, rar). Then upload it
Click to expand...
Click to collapse
You forgot to tell me to go to adb shell :silly:
DD is currently doing a dump, non interactive so I hope it is still alive, it has been close to 1 hour so far. I will upload the clean image once it is done and await further instructions from you. :good:
I'm in Perth, Western Australia (UTC +8:00), so we might be playing timezone tag.
wayney said:
You forgot to tell me to go to adb shell :silly:
DD is currently doing a dump, non interactive so I hope it is still alive, it has been close to 1 hour so far. I will upload the clean image once it is done and await further instructions from you. :good:
I'm in Perth, Western Australia (UTC +8:00), so we might be playing timezone tag.
Click to expand...
Click to collapse
I think I forgot one more thing. The external SD card needs to be mounted in the TWRP menu. I believe it's not mounted automatically. So the DD command does nothing. It shouldn't take that long. Sorry about that!
It's UTC +1:00 here in Germany
matshias said:
Well if you haven't modified anything yet then it'd be great if you can boot into TWRP with system read only and then connect via ADB to the tablet with a big SD card inserted which has enough free space (4 GB).
The run the following command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
This will take a while. Then copy the file system.img from your SD card to a PC and zip it (or 7z, rar). Then upload it
Click to expand...
Click to collapse
matshias said:
I think I forgot one more thing. The external SD card needs to be mounted in the TWRP menu. I believe it's not mounted automatically. So the DD command does nothing. It shouldn't take that long. Sorry about that!
It's UTC +1:00 here in Germany
Click to expand...
Click to collapse
I was wondering why nothing was happening after 3 hours.
I have rared it and it is uploading at the moment, it is going to take 5 hours.
wayney said:
I was wondering why nothing was happening after 3 hours.
I have rared it and it is uploading at the moment, it is going to take 5 hours.
Click to expand...
Click to collapse
Wow ok. Well thanks a lot for your efforts. This will not just help me but anyone with modified system partition to get OTAs.
Unmodified System Image
Here is the vanilla image via DD of the system partition.
Software Version : YT-X703F_160817
Android Version : 6.0.1
Security Patch Level : 1 September 2016
Kernel Version : 3.10.84-perf
Build Number : YT-X703F_S000689_161105_ROW
Tablet purchased retail from Australia.
https://mega.nz/#!bos0GIjI!vcO9dpSJX...Grjb7k3z6mjnqA
wayney said:
Here is the vanilla image via DD of the system partition.
Software Version : YT-X703F_160817
Android Version : 6.0.1
Security Patch Level : 1 September 2016
Kernel Version : 3.10.84-perf
Build Number : YT-X703F_S000689_161105_ROW
Tablet purchased retail from Australia.
https://mega.nz/#!bos0GIjI
Click to expand...
Click to collapse
Perfect!!
Can you send me the key for the download via PM or post it?
matshias said:
Perfect!!
Can you send me the key for the download via PM or post it?
Click to expand...
Click to collapse
Let's try that again.
https://mega.nz/#!bos0GIjI!vcO9dpSJXp6cKtdH07Kt0RSaqpqQ7Grjb7k3z6mjnqA
matshias said:
Wow ok. Well thanks a lot for your efforts. This will not just help me but anyone with modified system partition to get OTAs.
Click to expand...
Click to collapse
Thank you guys for spending times on it, it would be wonderful if Lenovo people do thing like this way, too.
In the depths of the Russian Internet i have found this
YT-X703F_USR_S000689_1611051146_Q00237_ROW.zip
https://drive.google.com/drive/folders/0B_jGuhC9WsNfYUZzZmhRY2NhQlU?usp=sharing
it is supose to be complete image to Wifi-Version.
I HAVE NOT FLASHED THIS YET. Do it on your risk.
pogo1975 said:
In the depths of the Russian Internet i have found this
YT-X703F_USR_S000689_1611051146_Q00237_ROW.zip
https://drive.google.com/drive/folders/0B_jGuhC9WsNfYUZzZmhRY2NhQlU?usp=sharing
it is supose to be complete image to Wifi-Version.
I HAVE NOT FLASHED THIS YET. Do it on your risk.
Click to expand...
Click to collapse
Hahaha got to love the dark corner of the Russian internets :laugh:
pogo1975 said:
In the depths of the Russian Internet i have found this
YT-X703F_USR_S000689_1611051146_Q00237_ROW.zip
https://drive.google.com/drive/folders/0B_jGuhC9WsNfYUZzZmhRY2NhQlU?usp=sharing
it is supose to be complete image to Wifi-Version.
I HAVE NOT FLASHED THIS YET. Do it on your risk.
Click to expand...
Click to collapse
If that's real it would have saved me a lot of time finding the loophole in the system to extract the boot and recovery image. But still a great find which will rescue some soft-bricked devices.
matshias said:
If that's real it would have saved me a lot of time finding the loophole in the system to extract the boot and recovery image. But still a great find which will rescue some soft-bricked devices.
Click to expand...
Click to collapse
so long as it's safe and not loaded with malware...
[How To Root] Huawei P smart - Android 8 - EMUI 8.0.0
The Rooting was tested by me on this device:
Model: FIG-LX1
Board: FIG-L31
Build No.: 8.0.0.128(C432)
EMUI 8 - Android 8
"free device"
Whether the following instructions are based on provider-branding is applicable, I could not test
and therefore advise against it.
Warning: Rooting will void the device warranty. Be careful with the newly acquired root rights.
I recommend this only to users who are fit in handling a custom recovery.
This TWRP is not yet perfect and should be used with caution.
Make sure to backup all data on the SD card. (PC, stick, or HD)
Create a backup with the Huawei Backup App.
Make sure the bootloader is open.
OEM and FRP unlocked,
in the device settings, OEM unlock and USB debugging enabled.
The stock kernel is mandatory.
This is flashed in fast boot mode/ bootloader:
If the device is unroot, it does not need to be done.
fastboot flash kernel kernel.img
(KERNEL.img.header must also be in the adb folder.)
This steps must be followed exactly:
Factoryreset in recovery.
Flashing TWRP in the bootloader: fastboot flash recovery_ramdisk FIGO.img
Boot to TWRP and change the file system of the external SD card:
Wipe> Advanced Wipe> Micro SD card> Repair or Change File System> Change File System> FAT:
Execute with "Swipe to Change".
This change deletes all data on the SD card.
Switch to the Mount menu and unmount all partitions. (remove all hooks)
On the internal and external memory.
Then create a backup:
Backup> Select Storage> Micro SD card> select all partitions,
except cache. Then reboot the device into the system and copy the Magisk Zip to the SD card.
Then install in TWRP: Install> Select Storage> Micro SD card> Magisk-v16(1600).zip> Swipe to confirm Flash.
Is there an error message, installing this Zip via MagiskManager App.
Reboot and if not available, install the MagiskManager App and check the root.
The routing is now complete.
Install Magisk modules only with the app; never with TWRP.
Important:
Never wipe the cache or perform a factoryreset.
[*]Please do not experiment with Xposed. This leads to the bootloop and the Firmware must be completely reinstalled.
[*]Please with each backup, make sure to unmount all partitions again. (internal and external)
Update via Firmwarefinder:
Start Firmwarefinder App and select the appropriate update.
Then on GET AN UPDATE THROUGH DNA.
Then on WITHOUT IMEI.
Availability is displayed.
Now click on REGISTER UPDATE and the registration is displayed.
Then click IN-APP PROXY.
Now activate DNS in the router, enter 81.177.139.39 as addresses and save.
Now go to the WLAN settings on the phone, touch and hold the active connection.
Then change to Network in the menu.
Under Proxy-manual, enter localhost and port 8080 as host names for extended options.
Now only set the IP setting to DHCP. Now start the eRecovery.
Vol.+ and Power with PC connection
There on "Download latest version and recovery".
Then click on "Download and recovery" and register there under Select WIFI.
Now the update is displayed and can be started.
When rebooting, the device lands in the bootloop,
execute a factoryreset in the recovery.
After the update reboot and all changed WLAN settings, also in the router
and reboot it again. If you don't, it'll be over by the time
next OTA update is displayed again and again, since the authorization remains in memory.
Themes-Fix, How to Unbrick, FRP-Unlocking and Bootloader Unlocking I described here. Or follow this thread.
https://www.android-hilfe.de/forum/...t-how-to-root-twrp-root-anleitung.866625.html
It is easy to translate with: https://www.deepl.com/translator
All downloads are here: http://www.mediafire.com/folder/7qdu5je08caya/FIGO
Attention: Changing the oem.info can
cause the phone to lock. OEM/FRP=LOCK
Thread Update 2017-03-28:
A new TWRP is now available. It is version 3.2.1-0.
Original Chinese developer version.
Instructions:
First perform the Huawei data backup.
Flash TWRP per Adb as usual.
Then switch from Chinese to English.
Then assign write and read rights by removing the hook in wipe menu.
Now for security, create a backup without data.
Then Format Data.
Create a new full backup including data. This is possible now that the
formatting is the size of Data = 0.
Now reboot the device and set it up completely new.
Now there is a new and configured data partition.
Then turn OEM and USB back on and boot to TWRP.
Then create a new full backup.
TWRP is now fully functional. Only the MTP mode does not work.
http://www.mediafire.com/file/icpfjhw9eysjlao/FIGO321.img
Good luck!
My special thanks for this original Chinese TWRP for free use,
goes to: "weibo.com/xinkid520", FIRE Team(Developer) and "Team Win Recovery Project".
Despite careful elaboration, I cannot guarantee that the execution of this manual will not cause any damage to the device or operating system and therefore I do not assume any liability for any damage or malfunction of the hardware and software! If you are still unsure, follow these steps: Follow the instructions only if you or your device is subject to any conditions (model number, Android version, etc.). Read the instructions carefully and completely, look up unknown terms. Check downloaded files for viruses. Make a backup of important settings and data. Do not follow the instructions if you do not know what you are doing.
These warnings must be logical. Please process my comments correctly.
Many thanks to: funkyhuawei.club, Jrummy, Chainfire, Stephen (Stericson) +
Jmz Software, TWRP, osmOsis,Topjohnwu and Huawei Technologies Co., Ltd 华为技术有限公司
it's alive!!! FIGO-LX1C10B120
Men I love you!!!
Thank you monster!!!! [emoji8]
thanks !! are we getting a Huawei P smart forum here soon ??
Themes
I cannot apply themes after Root ?
Hello,
could you also provide the vendor.img?
Would be really nice.
Thx in advance
@enjac
Forum habe ich beantragt.
I have applied for a new forum.
@JahSound77
Flash the cust.img. Then it works.
@Destroyer706
Vendor kannst Du nicht mit adb flashen.
You cannot flash Vendor with adb.
Hey, guys, I got a brick. Can someone save/extract the "kernel. img"
from the 122. Or can someone from the sources compose a kernel. img? I don't have a linux pc.
:crying:
I know I can't flash with adb, but fastboot. I made some changes and want to role back easily.
I try to provide you the kernel img
Themes
I followed your instructions.... fastboot flash cust cust. img
But no luck, after reboot... still can't apply themes from the store .
Destroyer706 said:
I know I can't flash with adb, but fastboot. I made some changes and want to role back easily.
I try to provide you the kernel img
Click to expand...
Click to collapse
I uploaded it now. :good:
https://mega.nz/#F!EplhBBzS!UUgXBRC9DRaExP9HY57FKQ
JahSound77 said:
I followed your instructions.... fastboot flash cust cust. img
But no luck, after reboot... still can't apply themes from the store .
Click to expand...
Click to collapse
You must be logged in to the google account and huawei id. Outside Asia. If it doesn't work, wait one or two days. It'll probably work then. It was like that with me.
Thx. I am already compiling the kernel from source
Destroyer706 said:
Thx. I am already compiling the kernel from source
Click to expand...
Click to collapse
This has never happened to me before. I have always been able to rely on TWRP backups. But without.....
ChinHon said:
This has never happened to me before. I have always been able to rely on TWRP backups. But without.....
Click to expand...
Click to collapse
The thing, I didn't think about, is, I don't know how to repack the image.gz after compiling to flashable boot.img as I don't have a existing boot.img.
Maybe you can advice me.
Can you upload oeminfo file for FIG-LX1 8.0.0.122 (C432) please?
I would like to rebrand my Chinese version (FIG-AL10).
Destroyer706 said:
The thing, I didn't think about, is, I don't know how to repack the image.gz after compiling to flashable boot.img as I don't have a existing boot.img.
Maybe you can advice me.
Click to expand...
Click to collapse
There is no boot. img in the 121 firmware anymore. Only the kernel. img. I flashed that. So I have the bootloop and need the img from 122, so I thought you might be able to extract it from your device.
steveleg said:
Can you upload oeminfo file for FIG-LX1 8.0.0.122 (C432) please?
I would like to rebrand my Chinese version (FIG-AL10).
Click to expand...
Click to collapse
Not included in the UPDATE. APP anymore.
See filelist:
Here is the extracted kernel.img. Hope it helps.
https://mega.nz/#!auo2TAaC!7009dtrK8-uBR39s9fNFf2xCQkEzR1EXURSLBabkuk8
steveleg said:
Can you upload oeminfo file for FIG-LX1 8.0.0.122 (C432) please?
I would like to rebrand my Chinese version (FIG-AL10).
Click to expand...
Click to collapse
I found another update in the net. Here the oeminfo as a self-extracting archive.
https://mega.nz/#!5gcygYLL!Wdlvg5jUo2hv6L7DBtAVT1-0z_WRmSBLuBin7iUGjig
Destroyer706 said:
Here is the extracted kernel.img. Hope it helps.
https://mega.nz/#!auo2TAaC!7009dtrK8-uBR39s9fNFf2xCQkEzR1EXURSLBabkuk8
Click to expand...
Click to collapse
Hey bro, FIGO's alive again. Thanks a million. You're the best.
:good::good:
How to ROOT Samsung Note 9 N960F/FD/N
Before trying make sure that flashing said file,
- Warranty will be void
- You won't be able to use Secure Folder/Samsung Pay forever (or may be more)
- May lose OEM unlock option
- Backup important stuff as you need to full wipe device (including internal storage)
DO IT ON YOUR OWN RISK
What is OEM fix?
Since Note8 samsung have introduced OEM unlock control remotely and flashing any custom binary removes OEM unlock option and rebooting in this state it ends with custom binary error and have to flash stock firmware. OEM patch will retain OEM unlock option in spite of having custom recovery. If you are not sure your device have OEM issue then there is nothing wrong to use 'OEM patch' option.
If you don't have OEM unlock option out of box then it may appear after 7 days, before this nothing can be done. Also this suggest, you have OEM affected device.
Click to expand...
Click to collapse
METHOD 1 : Root with TWRP Also works on Android Q (RECOMMENDED)
1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
2.Enable OEM Unlock from developer option (Currently no workaround for those who doesn't have this option)
3.Download and copy N9_S9_Root_for_OEM_issue_devices_V*.zip to Ext SD card
4.Download TWRP for N9
5.Switch Off device
6.Press Vol down + Bixby and connect to PC to reboot to download mode, press volume up when asked to continue to download mode
7.Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
8.Select TWRP (tar image) with AP tab of Odin and Start
9.Once Successfully flashed, you will see 'Passed' in Odin tab
10.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
11.Select to allow modification
12.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
13.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
14A (If you are on Pie)
.Now select Install and navigate path to Ext SD card - N960_root_OEM_issue_devices_V*.zip, you have copied earlier, select desired root method and select 'OEM Patch' option if your device have OEM issue. If you are not sure about this then better select 'OEM Patch', this will prevent losing OEM unlock option and so prevent 'custom binary error'
OR
14B (If you are on Android Q)
Flash Latest magisk & then DM-VERITY, FORCED ENCRYPTION, AND DISC QUOTA DISABLER
15.Once flash successfully finish, Reboot to System
Magisk app may appear in drawer after one reboot.
Important Note for Pie - There will be OEM unlock option there in developer setting but it will be disabled and can not enabled, this is because of it is hacked. Just ignore it. You can not boot device with TWRP if it is really disabled. Also If magisk app may not appear then simply download Magisk_for_Pie.apk from below attachement and install as regular app.
Open settings - Developer option - Look for OEM Unlock option. If it is there, it is safe to reboot device.
Credits and Thanks goes to BlackMesa123 for OEM fix
Click to expand...
Click to collapse
METHOD 2: Root with Stock Recovery (NOT SAFE ON OEM ISSUE DEVICES)
1.Download Magisk.apk attached below
2.Download Prerooted_N960_Exynos.zip (For Oreo Only)
3. Keep stock ROM file ready in case this doesn't work
4.Download De-Knox tool attached below (optional)
Installation :
- Enable OEM unlock
- Reboot to Download mode
(Here method changed - Switch off device - connect top PC - Press Vol down + Bixby)
- Extract (Unzip) Patched kernel - you will get N960F_kernel_PreRoot_RH5_DrKetan.tar.md5
Flash it using latest Odin with AP tab
- Once file successfully flashed, device will reboot and ask to reset device.
- Reset device, keep patience, device may take 5-7 minutes to boot.
- Once device reboot - Install Magisk manager apk manually
- install De-Knox tool apk and click icon, this will remove all knox app (no more useful on rooted device). This will also remove security messages
YOU MUST BACKUP EFS AS SOON AS ROOT DEVICE, and copy it to safer place,
Click to expand...
Click to collapse
14.01.2019 - Added support for Pie
Credit and Thanks to breakersvd for ril patch (defex fix) and @topjohnwu for magisk
EFS Backup Tool
As soon as you root device, you must make backup of EFS and must store a copy of backup to safer place like on cloud and on a PC
XDA version - Free version, complimentary tools for XDA users attached below.
Play Store version - You can buy from Play store to support us.
Both version make same form of backup and have no difference, Paid version have additional function to make Auto Backup when you change the ROM
So if we do lose OEM unlock, this means we will never be able to unlock the bootloader later on down the road, right?
I love your work and look forward to it every time I get a phone.
chrispyutec said:
So if we do lose OEM unlock, this means we will never be able to unlock the bootloader later on down the road, right?
I love your work and look forward to it every time I get a phone.
Click to expand...
Click to collapse
No, on previous device you get oem unlock option back again after 7 days
Though this is csc related and not all users will lose this option. Usually if your device have unlock option out of box then mostly you won't lose it. Though if we get root working we may need move forward to fix this
When its a kernel parched with normal magisk it will break ril because samsung added defex to the galaxy n9. I have only a semi working root on mine with ril
Here you see the half working root with ril. Normal magisk will break ril like i said
geiti94 said:
Here you see the half working root with ril. Normal magisk will break ril like i said
Click to expand...
Click to collapse
Have you tried hex patch similar issue reported on A series? Tried TWRP? Or you are waiting for kernel source. We badly needed it now.
dr.ketan said:
Have you tried hex patch similar issue reported on A series? Tried TWRP? Or you are waiting for kernel source. We badly needed it now.
Click to expand...
Click to collapse
Twrp with stock zimage dont boots and with compiled img from s9+ source same thats why i am waiting soueces. Twrp tree is allready finished and defconfig too. Only source is missing but sammy dont released it today. And n9 defex is different from a8 one
geiti94 said:
When its a kernel parched with normal magisk it will break ril because samsung added defex to the galaxy n9. I have only a semi working root on mine with ril
Click to expand...
Click to collapse
Wow! Wtf Samsung!!!??
How did you manage that half working root ?
siriom said:
How did you manage that half working root ?
Click to expand...
Click to collapse
Its a modded magisk where magisk hide and magisk manager gives fc. That means root is all time enabled and i dont need to press confirm and works only with some apps. For example es file explorer cant get root and titanium backup same
geiti94 said:
Its a modded magisk where magisk hide and magisk manager gives fc. That means root is all time enabled and i dont need to press confirm and works only with some apps. For example es file explorer cant get root and titanium backup same
Click to expand...
Click to collapse
If you to open a prompt and su ? would that work ?
I would like to mount or chgroot ....
This obviously blows up the whole knox deal right ?
geiti94 said:
Twrp with stock zimage dont boots and with compiled img from s9+ source same thats why i am waiting soueces. Twrp tree is allready finished and defconfig too. Only source is missing but sammy dont released it today. And n9 defex is different from a8 one
Click to expand...
Click to collapse
It's up now
FINALLY ROOTED NOTE9
May be Worlds first fully rooted Note9
Big thanks goes to @breakersvd for his special hex fix for recent samsung devices.
I will re-write first post with new files soo
Amazing @dr.ketan ??
Amazing @dr.ketan ??
Really appreciate this! Just to confirm, by rooting we will lose Secure Folder and Samsung Pay only (for now)?
If I unroot, will I receive ota?
Plzz let us know how to fully root note 9 dr.ketan
Plzz update file and root process .. i am very excited to root my note 9 .. dr. Ketan u r the best.. love ur work????
Nasty_z said:
Really appreciate this! Just to confirm, by rooting we will lose Secure Folder and Samsung Pay only (for now)?
If I unroot, will I receive ota?
Click to expand...
Click to collapse
You will lose secure folder and Samsung pay forever even if you unroot. You cannot undo this once done
pankajgavri said:
You will lose secure folder and Samsung pay forever even if you unroot. You cannot undo this once done
Click to expand...
Click to collapse
Yes, I know. I asked about ota after unrooting. I can still get ota if I unroot?
Hello Guys! In the past 2 days i wanted to rebrand my phone (Huawei P9 EVA-L09) to the AL10 chinese version with a guide i found in the thread of the HWOTA7 tool. I succesfully flashed it without complications. But then my luck went out and i maybe have softbricked my phone. Here's how it happened.
As i did't like huawei's emui i wanted to load the Base ROM on my phone for flashing my favorite rom, Resurrection Remix. After i flashed my phones RAMDISK with the TWRP version as explained in Tecalotes post (fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img) i went straight in it to flash the img because i didn't know what command i needed to flash it over fastboot. So i tried wiping the Dalvik-/cache, factory reset and then wiping data. Then i went to rebooting my phone into the OS to check if the files are in the right place, but then it just was stuck at the screen (Your device has been unlocked and can't be trusted.) and down below just stands "Your device is booting now". I thought it just could take a while, but even after 10 minutes it did't change a bit, then it automatically reset to the eRecovery. After browsing in some german forums i found out that my phone isn't lost yet After this i booted TWRP again over fastboot and deleted all system files. Then nothing worked anymore. Tried sideloading, it said adb: error: connect failed: closed. or uknowncommand[errno] and then it stopped). I sat there for 6 hours, then my big IQ tried the UPDATE.app extractor and extracted recovery, system, ramdisk and vendor and flashed it. And it worked, it booted in eRecovery again and said "Your OS has mayor errors, do you wan't to download latest version and recovery?". I accepted. It downloaded for 10 minutes, then i repeated the last step of HWOTA7 and again, it worked. Then i could boot in the OS again, and enable ADB Debug and USB debug. After that i booted in TWRP and tried staying at EMIU 8, but again, i couldn't find the files. Then i tried sideload, again a error telling me that sideloading can't be done. Rebooted in OS, again stuck at the screen after the unlocking. I did go to sleep. Now its day 2 and i am writing here with my phone at the side in eRecovery. This time i didnt wipe anything else than data and the cache, also i did a factory reset. I easely can go in the OS again, but then i still would get the false directory without any files and couldnt load OpenGapps and the network fix or the BASE ROM, because i know now that it isnt a problem with base rom. I grately would accept anyone that can help. Also i cant use a SD card because i do not have the money for it right now because i'm in high school. Besides that, I personally think it's a faulty directory because of the TWRP. Also i can't go back to nougat because i can't find the zips. If someone is a expert, hit me up in the DMs here and if i got a fix i write it on this post for everyone that has this problem and i will mention the god that found it!
Many regards!
Since you have followed the re-branding guide by @Tecalote, why didn't you follow also his instructions for going back to stock (Oreo or even Nougat)
https://forum.xda-developers.com/showpost.php?p=77161314&postcount=3
Same things have also been asked in the Open Kirin thread, see e.g.
https://forum.xda-developers.com/showpost.php?p=77589852&postcount=79
Good luck, as long as you have Fastboot and eRecovery, your phone is not dead
Restore your phone and try to be not confused
Bumo Gaming said:
Hello Guys! In the past 2 days i wanted to rebrand my phone (Huawei P9 EVA-L09) to the AL10 chinese version with a guide i found in the thread of the HWOTA7 tool.
As i did't like huawei's emui i wanted to load the Base ROM on my phone for flashing my favorite rom, Resurrection Remix.
After i flashed my phones RAMDISK with the TWRP version as explained in Tecalotes post (fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img) i went straight in it to flash the img because i didn't know what command i needed to flash it over fastboot.
Click to expand...
Click to collapse
Okay, first of all → You should learn to read the instructions carefully. And if you do not understand something, then you should ask first - in the Rebrand Thread - before you do something!
"After i flashed my phones RAMDISK with the TWRP" → which ramdisk to you mean? Since you speak of the "Base ROM", you refer to the renewed post # 2 in the Rebrand Thread. I did not mention anything about flashing a "Ramdisk" there.
Note: ramdisk.img = similar the same than boot.img on Android 7 → and if, it must be flashed to: ramdisk
recovery_ramdisk = on Oreo the place of Recovery on the phone (on Nougat it was: recovery) → and if, it must be flashed to: recovery_ramdisk
In post # 2 I do not offer "ramdisk" for download or to flash.
There are only two recoveries to flash there: 1) P9-EVA-8.0.0-TWRP-v4.img → which must be flashed to: recovery_ramdisk and
2) b528-RECOVERY_RAMDIS.img, which is the EMUI-Stock-Recovery → and must be flashed to the same place: recovery_ramdisk (after flashing the Base ROM for doing the Factory reset)
"After i flashed my phones RAMDISK with the TWRP version as explained in Tecalotes post (fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img) i went straight in it to flash the img because i didn't know what command i needed to flash it over fastboot."
BTW: every Recovery (TWRP, EMUI-Stock-Recovery) can be flashed in Fastboot Mode with: fastboot flash recovery_ramdisk "name-of-the-file".img
→ That means, you flashed already TWRP (P9-EVA-8.0.0-TWRP-v4.img) in Fastboot Mode and you did boot into TWRP → and then?? Which img did you flash then? I did not mention to flash any img immediately after flashing TWRP.
→ After flashing TWRP you should flash either the NetworkPatch.zip or the Base ROM (suitable for your device) and after that you should: Reboot Recovery from TWRP main menu, after TWRP is rebooted you should flash: b528-RECOVERY_RAMDIS.img to: recovery_ramdisk - and NOT TO: ramdisk!!
It is well explained in the Thread.
The next step would be to Reboot Recovery from TWRP main menu into Stock Recovery (which is flashed right now) and perform from EMUI-Stock-Recovery Wipe Cache Partition and Factoryreset....
→ if you flashed b528-recovery_ramdis.img to ramdisk instead to: recovery_ramdisk → then it's clear why your P9 did not boot into the system and was stuck on the Bootscreen!
→ But what I dont understand is: How could you flash recovery_ramdis.img with TWRP if you have no external SD??
I wrote directly under the Download-Link of TWRP a short summary about this TWRP and I told clearly, that this TWRP has currently no access to /data and the internal storage → therefore: nothing can be done without external SD!
So, my question is - from where can you flash anything?
→ It would only possible to flash anything without external SD, if you did "format data" → but that would be a completely wrong step that I have not mentioned anywhere in the instructions.
"Format data" is only required, if you use HuRUpdater, as long TWRP can not decrypt the encrypted data Partiton.
→ But "Format data" can not be used for doing the NetworkPatch or flashing the Base Rom → it requires, that /data is originally encrypted - and NOT formatted.
Bumo Gaming said:
So i tried wiping the Dalvik-/cache, factory reset and then wiping data. Then i went to rebooting my phone into the OS to check if the files are in the right place, but then it just was stuck at the screen (Your device has been unlocked and can't be trusted.) and down below just stands "Your device is booting now". I thought it just could take a while, but even after 10 minutes it did't change a bit, then it automatically reset to the eRecovery.
Click to expand...
Click to collapse
Clear, if you did several things wrong and and not according to the instructions, the phone can not boot and goes and goes after some unsuccessful attempts into eRecovery.
→ But that would not be any problem. Because it is possible on rebranded P9 to EVA-AL10 - to use eRecovery. Just click on "Download latest version and recovery" - then P9 connects to the wifi, get the info package and download and restore your P9 to latest approved Firmware.
"So i tried wiping the Dalvik-/cache, factory reset and then wiping data. " - forget about it → if TWRP has no access to /data - you can not wipe Dalvik and you can not do Factory reset and you can not wipe data with TWRP! → Thats why I advised to do it with Stock EMUI Recovery after the zips are flashed.
Bumo Gaming said:
After browsing in some german forums i found out that my phone isn't lost yet After this i booted TWRP again over fastboot and deleted all system files. Then nothing worked anymore. Tried sideloading, it said adb: error: connect failed: closed. or uknowncommand[errno] and then it stopped). I sat there for 6 hours, then my big IQ tried the UPDATE.app extractor and extracted recovery, system, ramdisk and vendor and flashed it. And it worked, it booted in eRecovery again and said "Your OS has mayor errors, do you wan't to download latest version and recovery?". I accepted.
It downloaded for 10 minutes, then i repeated the last step of HWOTA7 and again, it worked. Then i could boot in the OS again, and enable ADB Debug and USB debug. After that i booted in TWRP and tried staying at EMIU 8, but again, i couldn't find the files. Then i tried sideload, again a error telling me that sideloading can't be done. Rebooted in OS, again stuck at the screen after the unlocking.
Click to expand...
Click to collapse
→ There is a much more simple way to restore your Phone that it can work again properly. I will write at the end.
→ You should not flash any GApps - Open GApps - or whatever, because GApps are not compatible with this firmware and not necessary. All necessary Google core apps and Google services are included in the firmware. Most of them not in the system, but in the data partiton.
→ The NetworkPatch zip as well as the Base Rom are including Playstore and Gboard and all the other Google Apps you need, you can simply install from Playstore.
→ You should not use HWOTA7 on Oreo - it is programmed to work on Android 7 (hwota7) and not on Android 8. It includes TWRP for Android 7 and not for Android 8 - and I already mentioned it in OP.
Bumo Gaming said:
I grately would accept anyone that can help. Also i cant use a SD card because i do not have the money for it right now because i'm in high school. Besides that, I personally think it's a faulty directory because of the TWRP. Also i can't go back to nougat because i can't find the zips. If someone is a expert, hit me up in the DMs here and if i got a fix i write it on this post for everyone that has this problem and i will mention the god that found it! Many regards!
Click to expand...
Click to collapse
→ if you have no money for SD Card or USB OTG, you can go back to a working system (EVA-AL10 as well as make a downgrade to Nougat) - I have it already explained in Post #3 as @zgfg told you - but you will not be able for now to use the NetworkPatch.zip or the Base ROM.zip, because this TWRP can only flash from Micro SD or USB OTG (current version, until decryption of encrypted data is solved)
→ it could be done instead with Root and copy the files from the NetworkPatch.zip to the right places to replace the existent ones. But I made no instruction for it right now.
→ this TWRP has no "faulty directory" and everything is working correctly, except you can not use internal storage for now
→ "everyone that has this problem" - will only have it, if he is quite confused and does not know what he is doing - neither reads instructions properly, nor asks if he does not know
→ if you want to go back to Nougat, read Post #3, it is well explained. The Link EVA-AL10b399Sp17a /Android 7 you can find in Post #2
Using HuRUpdater from internal storage:
1) Flash TWRP for Oreo (not the one from hwota7, which is for Nougat) - flash it in Fastboot Mode with the code in Post #2
2) Boot into TWRP and use: Wipe and right down the Button: format data (for HuRUpdater it is required ) - confirm format data by typing:yes → go back (after) to main menu of TWRP and use: Reboot - but not system - Reboot instead: Recovery
3) Phone reboot again to TWRP and then TWRP is able to see the internal storage (because data is formatted - but note: this practice can not be used for the Base ROM and also not for the NetworkPatch, because it requires original encrypted storage!!)
4) Connect USB cable to P9 and PC - you should see internal storage in Windows Explorer.
If not, go to the Button "Mount" in TWRP and click 1x on "disable MTP" and then "enable MTP" - now you should see the internal storage in Windows Explorer.
6) Make a folder on your internal storage, name it as you like - Copy inside this folder:
a) HuRUpdater 0.4
b) update.zip
c) update_data_public.zip (= renamed, as written in OP)
d) update_all_hw.zip (=renamed, as written in OP)
→ Note: If you use EVA-AL10C00B528 for this operation, you will stay on Oreo, with properly installed Firmware (but without NetworkPatch...)
→ if you use instead EVA-AL10b399Sp17a for this operation, you will downgrade to Nougat, EVA-AL10 and can then use HWOTA7 to rebrand back to your original P9
After you copied the files, disconnect USB from P9.
7) Navigate to the folder you had created on internal storage (with HuRUpdater inside) and flash now ONLY the file: HuRUpdater.
8) The Battery will make some noice - in that moment press shortly VOL- (not Vol+) and HuRUpdater will flash the Firmware (all 3 zip files) from your folder automatically.
9) After it is succesfully flashed, click on the left button to Wipe Dalvik and Cache (it will work now, because of decrypted data) → the go back to the main menu and use again Reboot - But not System! - you choose: Reboot Recovery. This will reboot the Phone into EMUI-Stock-Recovery
10) In Stock Recovery make first Wipe Cache Partition and then Factory Reset → you have a properly working system back.
Can't you borrow an SD card of 4 GB to execute HuRU, I'm not sure could it work from Internal mem
zgfg said:
Can't you borrow an SD card of 4 GB to execute HuRU, I'm not sure could it work from Internal mem
Click to expand...
Click to collapse
SD Card is easier, but HuRUpdater works also from internal storage → and it works also from USB (with OTG cable)
Only problem, TWRP hasn't support for encrypted data yet - but the steps with format data and then copy with PC in Windows Explorer the required files to internal storage, should solve this. ( for this case)
Tecalote said:
Okay, first of all → You should learn to read the instructions carefully. And if you do not understand something, then you should ask first - in the Rebrand Thread - before you do something!
"After i flashed my phones RAMDISK with the TWRP" → which ramdisk to you mean? Since you speak of the "Base ROM", you refer to the renewed post # 2 in the Rebrand Thread. I did not mention anything about flashing a "Ramdisk" there.
Note: ramdisk.img = similar the same than boot.img on Android 7 → and if, it must be flashed to: ramdisk
recovery_ramdisk = on Oreo the place of Recovery on the phone (on Nougat it was: recovery) → and if, it must be flashed to: recovery_ramdisk
In post # 2 I do not offer "ramdisk" for download or to flash.
There are only two recoveries to flash there: 1) P9-EVA-8.0.0-TWRP-v4.img → which must be flashed to: recovery_ramdisk and
2) b528-RECOVERY_RAMDIS.img, which is the EMUI-Stock-Recovery → and must be flashed to the same place: recovery_ramdisk (after flashing the Base ROM for doing the Factory reset)
"After i flashed my phones RAMDISK with the TWRP version as explained in Tecalotes post (fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img) i went straight in it to flash the img because i didn't know what command i needed to flash it over fastboot."
BTW: every Recovery (TWRP, EMUI-Stock-Recovery) can be flashed in Fastboot Mode with: fastboot flash recovery_ramdisk "name-of-the-file".img
→ That means, you flashed already TWRP (P9-EVA-8.0.0-TWRP-v4.img) in Fastboot Mode and you did boot into TWRP → and then?? Which img did you flash then? I did not mention to flash any img immediately after flashing TWRP.
→ After flashing TWRP you should flash either the NetworkPatch.zip or the Base ROM (suitable for your device) and after that you should: Reboot Recovery from TWRP main menu, after TWRP is rebooted you should flash: b528-RECOVERY_RAMDIS.img to: recovery_ramdisk - and NOT TO: ramdisk!!
It is well explained in the Thread.
The next step would be to Reboot Recovery from TWRP main menu into Stock Recovery (which is flashed right now) and perform from EMUI-Stock-Recovery Wipe Cache Partition and Factoryreset....
→ if you flashed b528-recovery_ramdis.img to ramdisk instead to: recovery_ramdisk → then it's clear why your P9 did not boot into the system and was stuck on the Bootscreen!
→ But what I dont understand is: How could you flash recovery_ramdis.img with TWRP if you have no external SD??
I wrote directly under the Download-Link of TWRP a short summary about this TWRP and I told clearly, that this TWRP has currently no access to /data and the internal storage → therefore: nothing can be done without external SD!
So, my question is - from where can you flash anything?
→ It would only possible to flash anything without external SD, if you did "format data" → but that would be a completely wrong step that I have not mentioned anywhere in the instructions.
"Format data" is only required, if you use HuRUpdater, as long TWRP can not decrypt the encrypted data Partiton.
→ But "Format data" can not be used for doing the NetworkPatch or flashing the Base Rom → it requires, that /data is originally encrypted - and NOT formatted.
Clear, if you did several things wrong and and not according to the instructions, the phone can not boot and goes and goes after some unsuccessful attempts into eRecovery.
→ But that would not be any problem. Because it is possible on rebranded P9 to EVA-AL10 - to use eRecovery. Just click on "Download latest version and recovery" - then P9 connects to the wifi, get the info package and download and restore your P9 to latest approved Firmware.
"So i tried wiping the Dalvik-/cache, factory reset and then wiping data. " - forget about it → if TWRP has no access to /data - you can not wipe Dalvik and you can not do Factory reset and you can not wipe data with TWRP! → Thats why I advised to do it with Stock EMUI Recovery after the zips are flashed.
→ There is a much more simple way to restore your Phone that it can work again properly. I will write at the end.
→ You should not flash any GApps - Open GApps - or whatever, because GApps are not compatible with this firmware and not necessary. All necessary Google core apps and Google services are included in the firmware. Most of them not in the system, but in the data partiton.
→ The NetworkPatch zip as well as the Base Rom are including Playstore and Gboard and all the other Google Apps you need, you can simply install from Playstore.
→ You should not use HWOTA7 on Oreo - it is programmed to work on Android 7 (hwota7) and not on Android 8. It includes TWRP for Android 7 and not for Android 8 - and I already mentioned it in OP.
→ if you have no money for SD Card or USB OTG, you can go back to a working system (EVA-AL10 as well as make a downgrade to Nougat) - I have it already explained in Post #3 as @zgfg told you - but you will not be able for now to use the NetworkPatch.zip or the Base ROM.zip, because this TWRP can only flash from Micro SD or USB OTG (current version, until decryption of encrypted data is solved)
→ it could be done instead with Root and copy the files from the NetworkPatch.zip to the right places to replace the existent ones. But I made no instruction for it right now.
→ this TWRP has no "faulty directory" and everything is working correctly, except you can not use internal storage for now
→ "everyone that has this problem" - will only have it, if he is quite confused and does not know what he is doing - neither reads instructions properly, nor asks if he does not know
→ if you want to go back to Nougat, read Post #3, it is well explained. The Link EVA-AL10b399Sp17a /Android 7 you can find in Post #2
Using HuRUpdater from internal storage:
1) Flash TWRP for Oreo (not the one from hwota7, which is for Nougat) - flash it in Fastboot Mode with the code in Post #2
2) Boot into TWRP and use: Wipe and right down the Button: format data (for HuRUpdater it is required ) - confirm format data by typing:yes → go back (after) to main menu of TWRP and use: Reboot - but not system - Reboot instead: Recovery
3) Phone reboot again to TWRP and then TWRP is able to see the internal storage (because data is formatted - but note: this practice can not be used for the Base ROM and also not for the NetworkPatch, because it requires original encrypted storage!!)
4) Connect USB cable to P9 and PC - you should see internal storage in Windows Explorer.
If not, go to the Button "Mount" in TWRP and click 1x on "disable MTP" and then "enable MTP" - now you should see the internal storage in Windows Explorer.
6) Make a folder on your internal storage, name it as you like - Copy inside this folder:
a) HuRUpdater 0.4
b) update.zip
c) update_data_public.zip (= renamed, as written in OP)
d) update_all_hw.zip (=renamed, as written in OP)
→ Note: If you use EVA-AL10C00B528 for this operation, you will stay on Oreo, with properly installed Firmware (but without NetworkPatch...)
→ if you use instead EVA-AL10b399Sp17a for this operation, you will downgrade to Nougat, EVA-AL10 and can then use HWOTA7 to rebrand back to your original P9
After you copied the files, disconnect USB from P9.
7) Navigate to the folder you had created on internal storage (with HuRUpdater inside) and flash now ONLY the file: HuRUpdater.
8) The Battery will make some noice - in that moment press shortly VOL- (not Vol+) and HuRUpdater will flash the Firmware (all 3 zip files) from your folder automatically.
9) After it is succesfully flashed, click on the left button to Wipe Dalvik and Cache (it will work now, because of decrypted data) → the go back to the main menu and use again Reboot - But not System! - you choose: Reboot Recovery. This will reboot the Phone into EMUI-Stock-Recovery
10) In Stock Recovery make first Wipe Cache Partition and then Factory Reset → you have a properly working system back.
Click to expand...
Click to collapse
Thanks for your help for people that may come in this thread with the same problem, fortunally 2 days after this post i totally forgot about it and i allready got a fix that was right in my nose. With Ramdisk i ment the TWRP recovery_ramdisk that you provided for installing the network patch or the BaseRom on the Oreo version of the AL10 Firmware. In the timespan of 2 days i found myself finding a old SD Card in my old broken phone that had 64 GB, so plenty for installing everything. With my foolishness as a beginner at that time i cleared every system partition even if there was no need for it and as i said i had the eRecovery with the install newest version of recovery and EMUI, that for some reason was set on the AL10 8.0.0 patch what still was in beta. I figured it all out after looking in some posts of the thread of the HWOTA7 tool and the post for unofficial update to oreo and just followed everything once again but this time with the SD Card, now my phone is partly stable with the custom rom i installed because of your tutorial. I want to thank you for that and give you my up-most respect for taking the time and helping out people like me that just came to the forums and didn't really understand a thing at first. With that out of the way i will take insperation from you and help others out in this wonderfull community.
BTW: every Recovery (TWRP, EMUI-Stock-Recovery) can be flashed in Fastboot Mode with: fastboot flash recovery_ramdisk "name-of-the-file".img
→ That means, you flashed already TWRP (P9-EVA-8.0.0-TWRP-v4.img) in Fastboot Mode and you did boot into TWRP → and then?? Which img did you flash then? I did not mention to flash any img immediately after flashing TWRP.
→ After flashing TWRP you should flash either the NetworkPatch.zip or the Base ROM (suitable for your device) and after that you should: Reboot Recovery from TWRP main menu, after TWRP is rebooted you should flash: b528-RECOVERY_RAMDIS.img to: recovery_ramdisk - and NOT TO: ramdisk!!
Click to expand...
Click to collapse
I was refering to the TWRP.img i was talking about. I really don't know what i ment by not knowing the command. Also with the ramdisk i got confused between recovery_ramdisk and ramdisk, but i didn't flash the b528 in the wrong kind of ramdisk. Because i was still new to it i didn't know the difference and just called the recovery_ramdisk; ramdisk what may have confused you.
Also with the DATA i've figured out that it can't get accessed by TWRP due to not having encryption. That's where i tried sideloading baserom or network-patch that gave me back the error that it wouldn't install the zip. So i got confused because it worked when i still had the L09 Firmware and flashed RROS 5.8.5 that was on nougat and not on oreo, a big difference now for me after i was looking it up. Thats really the problem i had and fixed allready but i didn't want to leave you without an explanation.
→ You should not flash any GApps - Open GApps - or whatever, because GApps are not compatible with this firmware and not necessary. All necessary Google core apps and Google services are included in the firmware. Most of them not in the system, but in the data partiton.
Click to expand...
Click to collapse
Also also i tried flashing GApps because for some unknown reason the first time i had my os back to the CHINESE firmware that didn't come with the Playstore but rather their own chinese stuff so i got confused and tried getting the Playstore with flashing the OpenGapps what as we know didn't work out that well.
→ "everyone that has this problem" - will only have it, if he is quite confused and does not know what he is doing - neither reads instructions properly, nor asks if he does not know
Click to expand...
Click to collapse
i tried reading the instructions but i misinterpreted them for no reason what-so-ever. Also i had a bit of a problem with xda 'cus i couldn't create a account over my IP because it said i allready created one with this ip today, so i needed to figure out how to find my old account, but it's a whole story for itself. Still i want to thank you for taking out your time for helping people like me.
Many regards
Bumo Gaming said:
Thanks for your help for people that may come in this thread with the same problem, fortunally 2 days after this post i totally forgot about it and i allready got a fix that was right in my nose. With Ramdisk i ment the TWRP recovery_ramdisk that you provided for installing the network patch or the BaseRom on the Oreo version of the AL10 Firmware. In the timespan of 2 days i found myself finding a old SD Card in my old broken phone that had 64 GB, so plenty for installing everything. With my foolishness as a beginner at that time i cleared every system partition even if there was no need for it and as i said i had the eRecovery with the install newest version of recovery and EMUI, that for some reason was set on the AL10 8.0.0 patch what still was in beta. I figured it all out after looking in some posts of the thread of the HWOTA7 tool and the post for unofficial update to oreo and just followed everything once again but this time with the SD Card, now my phone is partly stable with the custom rom i installed because of your tutorial. I want to thank you for that and give you my up-most respect for taking the time and helping out people like me that just came to the forums and didn't really understand a thing at first. With that out of the way i will take insperation from you and help others out in this wonderfull community.
I was refering to the TWRP.img i was talking about. I really don't know what i ment by not knowing the command. Also with the ramdisk i got confused between recovery_ramdisk and ramdisk, but i didn't flash the b528 in the wrong kind of ramdisk. Because i was still new to it i didn't know the difference and just called the recovery_ramdisk; ramdisk what may have confused you.
Also with the DATA i've figured out that it can't get accessed by TWRP due to not having encryption. That's where i tried sideloading baserom or network-patch that gave me back the error that it wouldn't install the zip. So i got confused because it worked when i still had the L09 Firmware and flashed RROS 5.8.5 that was on nougat and not on oreo, a big difference now for me after i was looking it up. Thats really the problem i had and fixed allready but i didn't want to leave you without an explanation.
Also also i tried flashing GApps because for some unknown reason the first time i had my os back to the CHINESE firmware that didn't come with the Playstore but rather their own chinese stuff so i got confused and tried getting the Playstore with flashing the OpenGapps what as we know didn't work out that well.
i tried reading the instructions but i misinterpreted them for no reason what-so-ever. Also i had a bit of a problem with xda 'cus i couldn't create a account over my IP because it said i allready created one with this ip today, so i needed to figure out how to find my old account, but it's a whole story for itself. Still i want to thank you for taking out your time for helping people like me.
Many regards
Click to expand...
Click to collapse
Many thanks for your detailed feedback! :good:
slayernn said:
Plz HELP! History: I did everything from this thread and it worked fine for few monts until last official update, after that sim card was not recognised. I did lots of mistakes after,cant even imagine.. what i did in end is that i changed oem info via hwota to EVA-L09C636 and put again chinese EVA-AL10 oreo.. now my android system have lots of problem, no aps, keyboard was gone (only chinese kb and somehow i managed to put en). Everything is messed. Now problem gets bigger: OEM unlock is grayed in developer options, so i cant unlock bootloader (and in fastboot mode, bootloader and FRP are locked), so there is no way to put TWRP and everything look bricked (( Also dload update always fail at 5% with any room i try... Pls help me, i just want to go back to original nougat, like when i bought and forget chinese brand and oreo... Thanx in advance
droid info app:
Model: EVA-L09 (EVA-L09)
Manufacturer: HUAWEI
Baseband Version: 21.258.09.00.030
RIL Version: android infineon balong-ril 1.0
Build Number: System 8.0.0.046(0EET)
Build Fingerprint: Huawei/generic_a15/generic_a15:8.0.0/OPR6.170623.010/jenkin07111806:user/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: O (8.0.0)
SDK: 26
Click to expand...
Click to collapse
zgfg said:
First and most important for any further analysis, please clearly write on which exact build name/number you are
Can you post a screenshot of Setting/About
Click to expand...
Click to collapse
slayernn said:
Plz HELP! History: I did everything from this thread and it worked fine for few monts until last official update, after that sim card was not recognised. I did lots of mistakes after,cant even imagine..
Click to expand...
Click to collapse
1) It is normally → mobile network and IMEI is lost after OTA Update, but as you can read above - no problem to solve, if you doing the right steps
2) For the next time: First ask here in this Thread: https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849/page93#post77981310
if you face anything you dont know how to do.... before you are doing steps without sence
Where do you live? Because if you live in Germany, I could repair.
If not, we will find a solution - I am just think about it
@slayernn
I moved your issue to this Thread, because it is OT in the main Thread, since your problem is not made by me or my instructions, but because you did several things wrong without asking before.
Here is a Repair Firmware - which can be flashed with dload method (inside is also instructions). I will download in the evening and have a look. Then I can give you further instructions, how to use it. So far I remember, it must be extracted two times....
Huawei P9 EVA-AL10 8.0.0.528(C00) Firmware Android8.0:
https://androidhost.ru/6sl
Tecalote said:
1) It is normally → mobile network and IMEI is lost after OTA Update, but as you can read above - no problem to solve, if you doing the right steps
2) For the next time: First ask here in this Thread: https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849/page93#post77981310
if you face anything you dont know how to do.... before you are doing steps without sence
Where do you live? Because if you live in Germany, I could repair.
If not, we will find a solution - I am just think about it
@slayernn
I moved your issue to this Thread, because it is OT in the main Thread, since your problem is not made by me or my instructions, but because you did several things wrong without asking before.
Here is a Repair Firmware - which can be flashed with dload method (inside is also instructions). I will download in the evening and have a look. Then I can give you further instructions, how to use it. So far I remember, it must be extracted two times....
Huawei P9 EVA-AL10 8.0.0.528(C00) Firmware Android8.0:
https://androidhost.ru/6sl
Click to expand...
Click to collapse
Thanx man and sorry for posting in wrong thread. I'm looking forward! Downloading file right now.
Best regards , ps damn slow download from link (takes 8h to dl) you provide. Is there alternative?
slayernn said:
Thanx man and sorry for posting in wrong thread. I'm looking forward! Downloading file right now.
Best regards , ps damn slow download from link (takes 8h to dl) you provide. Is there alternative?
Click to expand...
Click to collapse
Yes, this is really a slow download, but no - it's the only place where you can get Firmware, which is installable with dload method!
If you create a User on this Site, download is faster, but needs even some hours....
@slayernn
When your Download is ready → you have: Huawei P9 EVA-AL10 8.0.0.528(C00) Firmware Android8.0 EMUI8.0.0 05014GSG androidhost.ru.zip
Rename it to: Huawei P9 EVA-AL10 8.0.0.528.zip
→ unpack/extract zip, then you have the folder: Huawei P9 EVA-AL10 8.0.0.528 - the folder contains:
ReleaseDoc
Software - go inside this folder, there is: SDupdate_Package.tar.gz → unzip/extract it, then you have the folder: SDupdate_Package.tar - this folder contains:
SDupdate_Package.tar - unzip/extract it, then you get finally the folder: SDupdate_Package - and this folder contains, what we need, the folder:
dload
Inside this folder you find the UPDATE.APP - and probably one or two additional folders with another UPDATE.APP (for the location, example: update_EVA-AL10_all_cn.app)
Now you have two possibilites
A)
1) Flash first the UPDATE.APP with dload method → after it is flashed, dont boot to system, press VOL+ during automatically restart to enter EMUI-Recovery
2) reject SD-Card, delete the previous update.app and copy the second update.app (update_EVA-AL10....) into dload folder → rename it to: UPDATE.APP
3) In EMUI-Recovery go to Reboot and during restart press Vol+ and Vol- to force update:
4) now second UPDATE.APP will be flashed → after it is flashed, dont boot to system, press VOL+ during automatically restart to enter EMUI-Recovery
5) delete second Update.app in dload folder and copy the first UPDATE.APP again into dload folder and flash it once again with dload → once you have done this and phone reboot automatically, press again VOL+ to enter EMUI-Recovery
6) Make Wipe Cache and Factoryreset
7) Phone should boot → and be able to enable OEM-Unlock → then a downgrade to Nougat and rebranding would be possible (ask me for the steps, before doing)
B) Second possibility (costs about 15 EUR, but it is easier and probably better)
Buy from DC 15 Credits (=15 EUR) from here: https://www.dc-unlocker.com/buy
Download DCPhoenix Software v63 - extract it and open DCPhoenix, log-in to your Account
In the first field above choose the big, first UPDATE.APP
on Customation field select the second UPDATE.APP (no need to rename for DC)
Flash it → additional you can change oeminfo on second tab....
Wish you success
@slayernn
I answered your PM → forgot to ask: Can you please tell me each exately name of the second two folders (with the two other update.app)
Thx
@slayernn It would be good if you write a summary here with the steps (as far as you remember) - how you managed to restore your P9
Tecalote said:
@slayernn It would be good if you write a summary here with the steps (as far as you remember) - how you managed to restore your P9
Click to expand...
Click to collapse
First of all, thank you Tecalote on all your tutorials and support in every step, without you restoring phone to original stock state would be imposible.
In short, i will explain what problem i had and how it is fixed.
History:
My P9 EVA-L09 was changed to EVA-AL10 and oreo, after few stupid mistakes in a rush, i changed oem info to EVA-L09c63.. and re-update AL-10 files in final step from hwota7. After that i got semi bricked device, oreo with damaged build number, oem info, and most important bootloader/frp was locked and couldnt change oem unlock (it was grayed). After that i tried many different fw/roms via dload method without success until Tecalote suggest downloading Huawei P9 EVA-AL10 8.0.0.528. UPDATE.app of that pack always worked and it was crucial later, but next dload EVA-AL10_all_cn didnt work, so i was at beginning again, with damaged oreo.
What i did later and steps that restore my device to stock nougat:
Next thing i did is taking DC-Phoenix + HCU timed license after which i tried to change oem info, but in dc-phoenix there was no EVA-L09 so i used EVA-L29 and tried some appropriate files to upload. It ended with errors and phone was dead bricked.. cant power on/dload/recovery but dc-phoenix still recognise it in fastboot so then i tried to upload EVA-AL10 8.0.0.528 again and it worked, during period of update device was unlocked and i realised i could use hwota7 tool during that time, just to unlock bootloader with code, so i did and it was successful, was it clever? dont know! What i got now is old oreo with f****d oem info / build etc but unlocked. Next thing i did is to use HCU program and in repair cdma tab, i changed model/vendor/country to EVA-L09/hw/eu! Right after that uploaded EVA-L09_C432B390_Firmware_France_Ger... and update_EVA-L09_C432B390_hw_eu from dc-phoenix and it was successful! Now i got nougat (poor without camera and so) and original EVA-L09 model name. Next, Tecalote send me HWOTA download link and steps to take https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3 and after that, phone was fully restored to original state and everything is working perfecto. It took me 2-3 days of work, many errors.. in a moments i was thinking that device is completely bricked and want it to throw in trash can. Never give up..thats point Best regards!