Related
Good day! Anyone care to tell me how can I apply an official update through the updater while being rooted? I just know there is a way, but really can't find one. Thanks in advance folks! Cheers! ?
AFAIK you have to flash original recovery... And if your CUST is the same.aa the update you want to flash by DLOAD or by OTA should work..You'll lose your root when flashing ... There a lot of posts and info... Search
Enviado desde mi EVA-L09 mediante Tapatalk
jcalderonv74 said:
AFAIK you have to flash original recovery... And if your CUST is the same.aa the update you want to flash by DLOAD or by OTA should work..You'll lose your root when flashing ... There a lot of posts and info... Search
Enviado desde mi EVA-L09 mediante Tapatalk
Click to expand...
Click to collapse
I have searched the internet with no luck on this detail:
I have flashed TWRP on my still NOT-rooted Huawei P9 EVA-L09 (adb reboot bootloader ; fastboot flash twrp-3.1.0-0-eva.img) successfully:
target reported max download size of 471859200 bytes
sending 'recovery' (22462 KB)...
OKAY [ 0.639s]
writing 'recovery'...
OKAY [ 0.302s]
finished. total time: 0.944s
What do I do after this? When I try to boot into TWRP I either get stuck forever at Device is booting now... or otherwise I boot into original Huawei eRecovery... I have read somewhere that original EMUI ROM maybe rewrites custom recovery if OS(ROM) boots before you entered recovery?
What is the correct way to boot into TWRP, what key combo? Since I get phone bootloader unlocked warning! right after powering on the phone, do I press the combination right away or after the warning shows up? I've been trying to boot custom recovery for hours, this is silly...
This is not the first I'm rooting a phone, but I simply can't seem to get into TWRP I just flashed so I can install SuperSU from SD card...
I have tried older TWRP version too, didn't help.
Phone is Huawei P9 EVA-L09, Android 7.0 EMUI 5.0
I have originally followed this guide:
https://theunlockr.com/2016/12/06/root-huawei-p9-p9-plus/
Vernicht said:
I have searched the internet with no luck on this detail:
I have flashed TWRP on my still NOT-rooted Huawei P9 EVA-L09 (adb reboot bootloader ; fastboot flash twrp-3.1.0-0-eva.img) successfully:
target reported max download size of 471859200 bytes
sending 'recovery' (22462 KB)...
OKAY [ 0.639s]
writing 'recovery'...
OKAY [ 0.302s]
finished. total time: 0.944s
What do I do after this? When I try to boot into TWRP I either get stuck forever at Device is booting now... or otherwise I boot into original Huawei eRecovery... I have read somewhere that original EMUI ROM maybe rewrites custom recovery if OS(ROM) boots before you entered recovery?
What is the correct way to boot into TWRP, what key combo? Since I get phone bootloader unlocked warning! right after powering on the phone, do I press the combination right away or after the warning shows up? I've been trying to boot custom recovery for hours, this is silly...
This is not the first I'm rooting a phone, but I simply can't seem to get into TWRP I just flashed so I can install SuperSU from SD card...
I have tried older TWRP version too, didn't help.
Phone is Huawei P9 EVA-L09, Android 7.0 EMUI 5.0
I have originally followed this guide:
https://theunlockr.com/2016/12/06/root-huawei-p9-p9-plus/
Click to expand...
Click to collapse
You don't need TWRP to root, just fastboot flash the modified boot.img
He doesn't want to root... He wants to get official updates so he needs to change CUST.
1st open BL
2nd flash TWRP
3rd put oemcust432. Zip on internal storage
4th boot TWRP and flash that zip
5th flash with Dload method the full c432b136... And enjoy the updates...
Note: if you already are at nougat... Not sure if you need you follow the steps I did when I was under an operator MM release
Enviado desde mi EVA-L09 mediante Tapatalk
Hi Guys,
My friend bricked his phone. Im trying to recover it. Its a VNS-L21.
I tried putting the stock rom on it using dload method from
https://boycracked.com/2016/09/13/official-huawei-p9-lite-vns-l21-stock-rom/amp/
and
http://huafirmware.com/8-firmware/16-huawei-p9-lite-vns-l21
but the upgrade fails everytime saying incompatible.
any help is appreciated :fingers-crossed:
My fix for the issue
malikusmanrasheed said:
Hi Guys,
My friend bricked his phone. Im trying to recover it. Its a VNS-L21.
I tried putting the stock rom on it using dload method from
https://boycracked.com/2016/09/13/official-huawei-p9-lite-vns-l21-stock-rom/amp/
and
http://huafirmware.com/8-firmware/16-huawei-p9-lite-vns-l21
but the upgrade fails everytime saying incompatible.
any help is appreciated :fingers-crossed:
Click to expand...
Click to collapse
Hey man, I got a problem just like you and this is the way I fixed it.
Download the Huawei update extractor:
https://forum.xda-developers.com/showthread.php?t=2433454
And use this to open your Update.app you already downloaded.
Extract the 'boot.img' and the 'system.img'.
Now you need fastboot, follow this tutorial:
https://www.xda-developers.com/xda-...tall-adb-and-fastboot-system-wide-in-windows/
Now open terminal/cmd/powershell and open the folder the boot.img and system.img you extracted are in.
Connect your phone in fastboot and run the following commands:
fastboot flash system [Extracted_System.Img]
fastboot flash boot [Extracted_Boot.img]
fastboot reboot
This resolved the issue for me, I hope also for you!
JatanX said:
Hey man, I got a problem just like you and this is the way I fixed it.
Download the Huawei update extractor:
https://forum.xda-developers.com/showthread.php?t=2433454
And use this to open your Update.app you already downloaded.
Extract the 'boot.img' and the 'system.img'.
Now you need fastboot, follow this tutorial:
https://www.xda-developers.com/xda-...tall-adb-and-fastboot-system-wide-in-windows/
Now open terminal/cmd/powershell and open the folder the boot.img and system.img you extracted are in.
Connect your phone in fastboot and run the following commands:
fastboot flash system [Extracted_System.Img]
fastboot flash boot [Extracted_Boot.img]
fastboot reboot
This resolved the issue for me, I hope also for you!
Click to expand...
Click to collapse
Hi Jatan,
Thanks for the reply. I tried that as well with a couple of stock images but all i got was a blank screen. Can you share the stock image that you used?
:good:
for most Stock images when i try to "Fastboot flash system d:\System.img" ( system.img is in D: in my case), i get this error
FAILED (remote: sparse flash write failure)
malikusmanrasheed said:
for most Stock images when i try to "Fastboot flash system d:\System.img" ( system.img is in D: in my case), i get this error
FAILED (remote: sparse flash write failure)
Click to expand...
Click to collapse
How did he brick it? What was he specifically doing (nougat update etc.)? Do you get the same error when you try and flash a boot image, stock recovery or other partitions?
Can you install twrp? If so, try wiping the system & boot partitions in twrp, then try flashing boot & system again in fastboot. If he'd updated to nougat, then you'll need to try and flash the rollback package first then dload a Marshmallow rom and go from there
I would suggest using this tool:
https://forum.xda-developers.com/p9/development/huawei-p9-eva-l09-eva-l19-eva-l29-tool-t3591358
to install this tool to unlock bootloader and install twrp.
After unlocking your bootloader everything on your phone is gone though.
Then in twrp you can try to repair your your partitians by going to wipe->advanced wipe->repair or change...
And thereafter continue with the steps is provided earlier or install a new rom, this is up to you.
I hope it fixes it for you.
colthekid said:
How did he brick it? What was he specifically doing (nougat update etc.)? Do you get the same error when you try and flash a boot image, stock recovery or other partitions?
Can you install twrp? If so, try wiping the system & boot partitions in twrp, then try flashing boot & system again in fastboot. If he'd updated to nougat, then you'll need to try and flash the rollback package first then dload a Marshmallow rom and go from there
Click to expand...
Click to collapse
Hi colthekid,
He just went nuts and wiped everything he could see in the twrp.
After that I have tried to write this via the method jatan suggested:
VNS-L21C185B360
from http://www.stechguide.com/download-huawei-p9-lite-b360-nougat-update/
still no boot.
JatanX said:
I would suggest using this tool:
https://forum.xda-developers.com/p9/development/huawei-p9-eva-l09-eva-l19-eva-l29-tool-t3591358
to install this tool to unlock bootloader and install twrp.
After unlocking your bootloader everything on your phone is gone though.
Then in twrp you can try to repair your your partitians by going to wipe->advanced wipe->repair or change...
And thereafter continue with the steps is provided earlier or install a new rom, this is up to you.
I hope it fixes it for you.
Click to expand...
Click to collapse
I'l try that and update.
i have twrp. repaired the partitions. did the flast via fast boot using the above method
"Now open terminal/cmd/powershell and open the folder the boot.img and system.img you extracted are in.
Connect your phone in fastboot and run the following commands:
fastboot flash system [Extracted_System.Img]
fastboot flash boot [Extracted_Boot.img]
fastboot reboot"
and still the same. It flashes the files fine. but at boot i get a black screen.
I think im using the wrong files. Can anyone please share the link for a full stock rom nougat , or a roll back from nougat to mm (i flashed this VNS-L21C185B360 latest)
or maybe i need to do write the oeminfo or something. Read it somewhere. not clear on what it is
malikusmanrasheed said:
I think im using the wrong files. Can anyone please share the link for a full stock rom nougat , or a roll back from nougat to mm (i flashed this VNS-L21C185B360 latest)
Click to expand...
Click to collapse
Maybe you need to continue this in the P9 Lite forum?
However, in the meantime, this should help you along!!
Firmware... https://forum.xda-developers.com/hu...huawei-p9-lite-firmware-compilations-t3517124 (pick a full MM rom)
Downgrade... https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932 (partway down first post)
colthekid said:
Maybe you need to continue this in the P9 Lite forum?
However, in the meantime, this should help you along!!
Firmware... https://forum.xda-developers.com/hu...huawei-p9-lite-firmware-compilations-t3517124 (pick a full MM rom)
Downgrade... https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932 (partway down first post)
Click to expand...
Click to collapse
This:
Downgrade... https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932 (partway down first post)
solved my problem.
Putting the puzzle back again:
I think the genius removed the oeminfo along with everything else he could see in the twrp wipe menu.
I tried to put multiple firmwares on the device nougat ( as he updated) but the boot still showed blank.
As soon as i flashed the oeminfo --> then MM firmware, the device booted up.
Thank you so much everyone for your help. Really appreciate it :good::good::good::good::good::good:
Excellent! :good::good:
And I'm sure your friend is glad to have a working phone again!
Explains why dload wouldn't work as well. As far as I'm aware the update.app checks oeminfo to make sure the firmware is compatible. Hence if you want to debrand a phone to C432, you have to flash a C432 oeminfo before the C432 update.app will flash successfully. No oeminfo=no compatibility for anything!!!
hi,
please help unbrick my P9
I can't get into fastboot, the only one thing it boots is the eRecovery, (system partition damaged)
---------- Post added at 04:26 AM ---------- Previous post was at 04:11 AM ----------
konstwww said:
hi,
please help unbrick my P9
I can't get into fastboot, the only one thing it boots is the eRecovery, (system partition damaged)
Click to expand...
Click to collapse
somehow i managed to get to fastboot but trying to flash system get error
sending sparse 'system' (449861 KB)...
OKAY [ 14.749s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.142s
Update: To get into fastboot is very important that smartphone is connected via USB to PC, then Power-button and VolumeDown together till Phone gets into fastboot.
from there flash TWRP, and reboot to recovery, after that install full Update (Files and guideline is here in first post part 3 and 4 https://forum.xda-developers.com/p9/development/rom-huawei-p9-magic-rainbow-t3601064).
malikusmanrasheed said:
This:
Downgrade... https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932 (partway down first post)
solved my problem.
Putting the puzzle back again:
I think the genius removed the oeminfo along with everything else he could see in the twrp wipe menu.
I tried to put multiple firmwares on the device nougat ( as he updated) but the boot still showed blank.
As soon as i flashed the oeminfo --> then MM firmware, the device booted up.
Thank you so much everyone for your help. Really appreciate it :good::good::good::good::good::good:
Click to expand...
Click to collapse
Can you please send me your full steps. I really need it
Hello,
I have unlocked the bootloader of my Honor 5C (it seems to work) and now I wanted to flash it with TWRP.
I have downloaded the latest 3.1.1 image.
Code:
$ fastboot flash recovery /tmp/twrp-3.1.1-0-nemo.img
target reported max download size of 471859200 bytes
sending 'recovery' (21918 KB)...
OKAY [ 0.620s]
writing 'recovery'...
OKAY [ 0.542s]
finished. total time: 1.163s
But when I reboot, I now get stuck at
Code:
Your device has been unlocked and can't be trusted
To learn more, visit: http://zh.ui.vmail.com/emotiondownload.php?mod=restore
Your device is booting now...
Already got this screen when I had first unlocked the bootloader but I had choices to continue which I no longer have.
Any idea? Did I forgot something?
I can still access the fastboot mode by holding power+volume down.
Any idea?
Thanks
Update: I succeed to boot into eRocovery when holding volume up+power during boot. However, how can I go to ROM now?
Ok, I can try that
Where can I find these images? I have the NEM-L51 C432B355 version.
I am using Linux
Oh sorry, you mean the OS on the phone or on my PC? I can access a Windows PC if needed.
I have the stock ROM on the phone, EMUI 5 which is Android 7.0 Nougat I believe.
Rommco05 said:
Nougat is ok and I don't know if will be some change from Windows, but u can try
Click to expand...
Click to collapse
Try what? Sorry but I am noy sure how to flash stock recovery.
Could you guide?
Thank you. I have found a link to the stock image NEM-L51C10B355 (google).
Then, using the software Huawei Update Extractor (still using google) on a Windows PC. I was able to extract the recovery.img and boot.img files.
I have flashed both using fastboot
Code:
$ fastboot flash boot BOOT.img
$ fastboot flash recovery RECOVERY.img
$ fasboot reboot
recovery.img B355
boot.img B355
and it worked.
I guess I will retry TWRP later
I guess it should not be very different, you just need a different image.
I have given the steps I made to resolve it in my previous message, I hope it helps.
>==°> said:
I guess it should not be very different, you just need a different image.
I have given the steps I made to resolve it in my previous message, I hope it helps.
Click to expand...
Click to collapse
Hey man, did you found the TWRP Image for B355??
SCUZZY1337 said:
Hey man, did you found the TWRP Image for B355??
Click to expand...
Click to collapse
Do you mean the stock recovery or the TWRP ?
For the TWRP, I used the official website with the honor 5c page but it seems it does not work as I got stuck in a recovery loop (so maybe there is a better image somewhere else). I have tried both 3.1.1 and 3.1.0 version.
To restore, I used the stock ROM NEM-L51 C432B355 I have found here and I extracted the stock recovery using Huawei Update Extractor.
Rommco05 said:
Hi please can u confirm >> OEM info is the same for L51C432 and L21C432?
Click to expand...
Click to collapse
How can I check that? I only have a L51C phone
>==°> said:
Do you mean the stock recovery or the TWRP ?
For the TWRP, I used the official website with the honor 5c page but it seems it does not work as I got stuck in a recovery loop (so maybe there is a better image somewhere else). I have tried both 3.1.1 and 3.1.0 version.
To restore, I used the stock ROM NEM-L51 C432B355 I have found here and I extracted the stock recovery using Huawei Update Extractor.
Click to expand...
Click to collapse
I asked you about TWRP Image.... Do you have it?
---------- Post added at 11:10 AM ---------- Previous post was at 11:09 AM ----------
SCUZZY1337 said:
I asked you about TWRP Image.... Do you have it?
Click to expand...
Click to collapse
There is an image working on latest N for all 5C's, if you need it, i can drop you the link...
SCUZZY1337 said:
I asked you about TWRP Image.... Do you have it?
Click to expand...
Click to collapse
Geeze, no need to be rude. I gave you above the link where I got the image. If you have better source, you can just give the link.
>==°> said:
Geeze, no need to be rude. I gave you above the link where I got the image. If you have better source, you can just give the link.
Click to expand...
Click to collapse
You won't be able to use these twrp on twrp.me bro, if you on N, you need a special unofficial TWRP:
https://github.com/OpenKirin/androi...eases/download/3.1.1-0/twrp-3.1.1-0-venus.img
SCUZZY1337 said:
You won't be able to use these twrp on twrp.me bro, if you on N, you need a special unofficial TWRP:
https://github.com/OpenKirin/androi...eases/download/3.1.1-0/twrp-3.1.1-0-venus.img
Click to expand...
Click to collapse
Cool! Did not know the twrp.me did not work for Nougat.
It looks like this is the image for the P9. Did you used it successfully on a 5C ?
>==°> said:
Cool! Did not know the twrp.me did not work for Nougat.
It looks like this is the image for the P9. Did you used it successfully on a 5C ?
Click to expand...
Click to collapse
It's not for a P9, it's Open Kirin version for P's, Honor's... Working for me very well, rooting is possible too, i'm rooted. SuperSU 2.82 SR1.
>==°> said:
Hello,
I have unlocked the bootloader of my Honor 5C (it seems to work) and now I wanted to flash it with TWRP.
I have downloaded the latest 3.1.1 image.
Code:
$ fastboot flash recovery /tmp/twrp-3.1.1-0-nemo.img
target reported max download size of 471859200 bytes
sending 'recovery' (21918 KB)...
OKAY [ 0.620s]
writing 'recovery'...
OKAY [ 0.542s]
finished. total time: 1.163s
But when I reboot, I now get stuck at
Code:
Your device has been unlocked and can't be trusted
To learn more, visit: http://zh.ui.vmail.com/emotiondownload.php?mod=restore
Your device is booting now...
Already got this screen when I had first unlocked the bootloader but I had choices to continue which I no longer have.
Any idea? Did I forgot something?
I can still access the fastboot mode by holding power+volume down.
Any idea?
Thanks
Update: I succeed to boot into eRocovery when holding volume up+power during boot. However, how can I go to ROM now?
Click to expand...
Click to collapse
Are you on Emiui 5.0 or 4.0/4.1 ?
AlexMihai26 said:
Are you on Emiui 5.0 or 4.0/4.1 ?
Click to expand...
Click to collapse
5.0
>==°> said:
5.0
Click to expand...
Click to collapse
Well,if you can open fastboot,install this : https://github.com/OpenKirin/android....1-0-venus.img . If you cannot open fastboot after unlocking the bootloader you can try the method that i used,because i unlocked my bootloader,but my phone won`t boot,cannot open fastboot, it was like a "brick".So what did i do ? Well its kind of stupid but it worked. Let my phone to go at 0% battery,then charge to 100%. Then it worked.
But before anyone is gonna say that is bull****,well its not .My phone stayed at Your device is booting now... for 2 hours.
Rommco05 said:
Man, I see this situation before (somewhere on xda honor threads), but I can't explain how this work, but probably myabe is it a true
Click to expand...
Click to collapse
Well for me it worked,that was the only way to make my phone open fsatboot.
Can anyone help please
yesterday i follow the instructions for twrp recovery i got stucked too somehow i manage to get out of it without any flashing
but when i boot to recovery it shows the stock one not the twrp i flashed it and everything so anyone can tell me if theres a newer version of twrp 3.1.1 my phone is 5c NEM-L21. Thanks !
theshadow79 said:
yesterday i follow the instructions for twrp recovery i got stucked too somehow i manage to get out of it without any flashing
but when i boot to recovery it shows the stock one not the twrp i flashed it and everything so anyone can tell me if theres a newer version of twrp 3.1.1 my phone is 5c NEM-L21. Thanks !
Click to expand...
Click to collapse
You can try this twrp : https://github.com/OpenKirin/android....1-0-venus.img . You need to press vol up + power,keep pressing them until the twrp logo shows up. I`m using the same twrp on my NEM-L21 .
Hi guys,
got a little problem on my VTR-L09C432.
I got Oreo running like explained right here: http://www.stechguide.com/install-android-8-0-oreo-on-huawei-p10/#comment-12332
After that, Oreo bootet fine. But to get a clean install, I did a factory reset.
After that my Version is 8.0.0.046(01BN) and not 8.0.0.311.
There are a few little bugs so I decided to flash once again. I tried to flash TWRP in fastboot mode. -> No success
I tried to flash with the following command: fastboot flash recovery_ramdisk twrp***.img -> SUCCESS!
BUT no i get an Error message when trying to boot into recovery:
Attention! Please update system!
"- picture of the little green guy-"
Error!
Func No 11 (recovery image)
Error No 2 (load failed)
gettin into eRecovery is no Problem. System boots fine and runs better than Nougat, better battery life, with a fews little bugs.
How do I get a TWRP running?
In case if no chance, how do I get system oreo Recovery flashed an running?
Will it be possible to get official updates, when I will get back to original recovery?
One big bug is that my screen won't turn on when receiving notifications... even not with the help of a third party app Any idea how to fix it anyway?
If TWRP will be flashed successfully, is there a Chance to flash these 3 Update-Files through twrp?
Thx a lot!
You have flashed a C900 and you have a C432. So your device didnt find all needed files.
Try to flash this twrp (its in a MEGA Folder) and report .
https://forum.xda-developers.com/honor-9/how-to/stf-l09c432-how-to-install-oreo-h9-t3707729
Thx for your reply. You mean there are files, which I need to flash again for my c432 device?
I flashed the twrp from your link.
Flashing was fine but no chance to get into twrp. Still the same error.
Can I flash the RAMDISK or Recovery Ramdisk from your mega-source?
UPDATE: I flashed STR_Stock_Recovery from your Mega-Folder and got success. Now I can boot into stock recovery and into Erecovery. But still no TWRP is working...
UPDATE2: I got a working TWRP by flashing this one: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
Now my question...can i flash the Supersu from your mega-folder onto my P10? Or will it be bricked?
Gesendet von meinem VTR-L09 mit Tapatalk
SOLVED!
Hi Guys,
Problem is solved! For those who got the same problem, follow these steps:
You need this link for all following steps(thx to blackball!): https://forum.xda-developers.com/honor-9/how-to/stf-l09c432-how-to-install-oreo-h9-t3707729
If you haven't got fastboot error, start at point 2.!
1. To get Fastboot Error removed, flash Stock Recovery from link above (in fastboot mode)
2. boot in fastboot mode (shutdown, restart by pressing power&vol- with usb cable attached)
3. Flash TWRP Recovery from link above fastboot flash recovery_ramdisk TWRP***.img
3.1. if this doesn't work, flash TWRP attached below this link
4. boot in to twrp recovery (shutdown phone, restart by pressing power & vol+)
5. Flash supersu.zip from link above
6. reboot
7. install root browser or similar from playstore
8. get root privileges to root browser
9. reboot
10. navigate to /cust/hw/
11. rename "normal" folder to "eu" (without the quotes)
12. navigate to /version/special_cust/STF-L09/hw
13. rename "normal" folder to "eu" (without the quotes)
14. reboot
15. that's it!
Thx to blackball for the help!
TWRP link:
https://drive.google.com/drive/folders/1twgKVop02omG9vuVyc8ELwMxtB6nCko1
Thx for this guide, i will try it later!!! But whats the main change now???
When i see it clearly, then you still have the 8.0.0.046 Version on your device... But you have a working TWRP.... And you will receive official updates?
I am wondering, becaus i did the same with my P10 ( i am on 8.0.0.046 too) and i am not sure, if this is an official version with official updates... If it isnt, i will try to go back to Nougat...
stefan.irmen said:
Thx for this guide, i will try it later!!! But whats the main change now???
When i see it clearly, then you still have the 8.0.0.046 Version on your device... But you have a working TWRP.... And you will receive official updates?
I am wondering, becaus i did the same with my P10 ( i am on 8.0.0.046 too) and i am not sure, if this is an official version with official updates... If it isnt, i will try to go back to Nougat...
Click to expand...
Click to collapse
After these steps, you have 8.0.0.311 version, themes working, screen on notification working and so on.
Gesendet von meinem VTR-L09 mit Tapatalk
Hey cologne83!
First of all, thanks for this helpful guide, now i see finally 8.0.0.311 on my phone
But you dont actually need the root browser, because you can change those folders in twrp too!
Secondly i have a question:
cologne83 said:
5. Flash supersu.zip from link above
Click to expand...
Click to collapse
how did you do this? everytime i boot in twrp it shows me only gibberish until i go one directory up.
Root on Oreo would be super nice
Put zip file on external SD card. Your internal is encrypted.
Gesendet von meinem VTR-L09 mit Tapatalk
ok, i hoped it is on Android O not encrypted anymore.
But anyway thank you works likes new now!
just a little bit off topic question: is there any new version available? when i check systemupdates it says that that my Version (8.0.0.311) is the latest available. just wanna be sure
deleted
8.0.0.046(04vt)
Does someone has a solution for the 8.0.0.046(04VT) version? If I navigate to /cust/hw/ I find now two folders: eu and normal. In /version/special_cust/VTR-L09/hw I find the eu. folder. So what to change here? Thx
anabolic_guy said:
I have upgraded from Nougat to Oreo following the guide written at the beginning of this post.
Oreo now is installed, phone is not rooted and when I go to fastboot mode to flash Oreo TWRP, this happens:
C:\adb>fastboot flash recovery_ramdisk twrp_oreo.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (20336 KB)...
OKAY [ 0.474s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.498s
Bootloader and frp are both opened and RED in fastbooot mode.
The build number is: System 8.0.0.046(01UV)
EMUI version: 8.0.0
Android version: 8.00
Some ideas ?
Thanks for th attention.
Click to expand...
Click to collapse
This guide is my last chance to save phone. Afther update to b360 my phone brick, no recovery, no eRecovery, no TWRP.... I can flash all but nothing change
urbanboymne said:
This guide is my last chance to save phone. Afther update to b360 my phone brick, no recovery, no eRecovery, no TWRP.... I can flash all but nothing change
Click to expand...
Click to collapse
Which guide? If you are able flash you get access to phone so it should work in some way
kwaichang said:
Which guide? If you are able flash you get access to phone so it should work in some way
Click to expand...
Click to collapse
Yes i'm able some recovery images or twrp, also all system.img i can flash withouth problem, cust.img... But nothing change. Somethimes stay in boot black screen, somethimes reboot to ERROR MODE, and also i'm able to get into fastboot mode, unlock/relock bootloader but always says me no recovery image - load fail in error mode
urbanboymne said:
Yes i'm able some recovery images or twrp, also all system.img i can flash withouth problem, cust.img... But nothing change. Somethimes stay in boot black screen, somethimes reboot to ERROR MODE, and also i'm able to get into fastboot mode, unlock/relock bootloader but always says me no recovery image - load fail in error mode
Click to expand...
Click to collapse
same for me after hwota and rebrand fail. And I don't find the STR_stock just 2 STR_recovery but even if android say flash sucessfully i can't acces to recovery nor ercovery.
P.S: I was using OREO rom when I try to rebrand
It can works on Huawei P10 EMUI 8.0.0? How to root that model? I stuck on how to install twrp,. Please help me.....
my system is saying im on 8.0.0.046(0BZC and i can't even get the erecovery or twrp to work at all. nobody around here wants to help or pin point me in any direction either
I have exactly the same problem, but the locations mentioned here don't even exist on my phone, so I can't rename them
10. navigate to /cust/hw/
11. rename "normal" folder to "eu" (without the quotes)
12. navigate to /version/special_cust/STF-L09/hw
cust does not contain a "hw" folder, just a "lost+found" one.
version/special_cust/VTR-L09/hw does exist, but when I try to rename "hw" I get "operation failed".
Very annoying!
I stuck also inside the 8.0.0.046 !
And i dind´t found any solution for this.
This is what i allready tried:
- official eRecovery : download from huawei. But didn´t worked after download. Stucked at 0%
- TWRP oreoupdate ( https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286 )
- TWRP HuRuUpdate ( https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279/ )
- TWRP HWOTA8 ( https://www.******.com/huawei-hwota-tool-for-huawei-devices/ )
Just to answer my pre-writers:
You need to "mount" the folders "cust" and "version" to see something inside. Only then you are able to change things. In my case this changes
didn´t affect something positive to my version number.
Not sure what i did wrong. Maybe my false was
- Wipe all with TWRP instead with eRecovery
or because
- i flash my (C02) witth (C432) version
So i tried 4x different ways to solve my issue (mostly with TWRP). With no success. If somebody read this, it would be great to get some tips or a complete solution. Would appretiate it.
Okay.
Somehow i found a solution by myself. I have to guess, that the issue is / was of a wrong build nr. In my case i got a previous vers. VTR-L09 8.0.0.382(C02)-FULL. So i updatet to a different build (C432). After
this my Themes disappeared, no file manager and the vers. no. was 8.0.0.046 , somehow. So i tried to go back to VTR-L09 8.0.0.382(C02)-FULL which i downloaded before. Tried both methods: dload, TWRP. No
success. In the end i downloaded VTR-L09 8.0.0.389(C02)-FULL and this worked with the TWRP update method: oreoupdate (check my previous post). After the Update with TWRP before it boots into the
system i was triggering eRecovery to do a "wipe chache / factory reset". Finaly, after all of this, i got a working device as it should ! I hope it can help maybe some people. If everything doesn´t work, just try a different update build number.
How many people bricked specifically hardbricked their phone after 2018-04-16 updates,while OTA or rebranding using any tool and choose which methods you tried to solve.
we need to show how many people we are,and seek for solution or encourage BOX groups to do something for this matter.
Even huawei may help us if they see we are bunch of people.
Edit: Just comment only if you solved the issue with this tool or any other tool that is not mentioned,here we are seeking help.
reza6d said:
How many people bricked specifically hardbricked their phone after 2018-04-16 noxloader updates,while OTA or rebranding using any tool and choose which methods you tried to solve.
we need to show how many people we are,and seek for solution or encourage BOX groups to do something for this matter.
Even huawei may help us if the ysee we are bunch of people.
Click to expand...
Click to collapse
The only versions that will brick (so far anyway) are BLA-L29C636B137 and ALP-L29C636B134 from 16/4, neither is a noxloader version.
Bricks occur when you update/downgrade/rebrand FROM those 2 firmwares.
ante0 said:
The only versions that will brick (so far anyway) are BLA-L29C636B137 and ALP-L29C636B134 from 16/4, neither is a noxloader version.
Bricks occur when you update/downgrade/rebrand FROM those 2 firmwares.
Click to expand...
Click to collapse
maybe i recall wrong but after first time seeing these noxloaders,somethings changed,anyway i edited the post.thanks.
My BLA-L29 is still on the black screen and I can not even revert to DC-Phoenix. After upgrading to 138.
Used funky
mikaole said:
Used funky
Click to expand...
Click to collapse
i think your phone was in fastboot or bootloop,we are talking about hardbrick bro,black screen not even charge led in our devices.
I bricked my Huawei Mate 10 too
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Carnage! said:
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Click to expand...
Click to collapse
did you tried huawei pc app (hisuite)?
your problem maybe is because magisk, try to install in twrp "magisk uninstaller". or try to install via twrp, recovery_ramdisk.img, kernel.img and ramdisk.img from the last rom of android 8 (extract with huaweiupdateextractor), then install via twrp with hrupdater 0,4 the same update.zip that you extract the kernel.img, recovery and the other img that I told you.
look at the guides of the preocesses that I told you, if you have any question let me know
durc12 said:
did you tried huawei pc app (hisuite)?
your problem maybe is because magisk, try to install in twrp "magisk uninstaller". or try to install via twrp, recovery_ramdisk.img, kernel.img and ramdisk.img from the last rom of android 8 (extract with huaweiupdateextractor), then install via twrp with hrupdater 0,4 the same update.zip that you extract the kernel.img, recovery and the other img that I told you.
look at the guides of the preocesses that I told you, if you have any question let me know
Click to expand...
Click to collapse
Yes, I tried hisuite but it says my device isn't supported. I will try your suggestion and will get back to you if I have questions
Carnage! said:
Yes, I tried hisuite but it says my device isn't supported. I will try your suggestion and will get back to you if I have questions
Click to expand...
Click to collapse
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Pretoriano80 said:
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Click to expand...
Click to collapse
I see. I only tried flashing the recovery_ramdisk and system.img. I will try it later and I will let you know if it worked.
Pretoriano80 said:
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Click to expand...
Click to collapse
as far as I can read, I think he wants to come back to OREO, so he has to install first recovery_ramdisk.img, kernel.img and ramdisk.img from 8.0.0.143 (extracting those files with huaweiextractorupdate) and then flashing those files via fastboot or your twrp version. Then, he has to use hrupdater 0.4 to install 8.0.0.143
Am I right Pretoriano80?
please, fell free to correct me if i have commited any mistake
PD: MANDATORY TO HAVE UNLOCKED BOOTLOADER FOR THE PROCESS
durc12 said:
as far as I can read, I think he wants to come back to OREO, so he has to install first recovery_ramdisk.img, kernel.img and ramdisk.img from 8.0.0.143 (extracting those files with huaweiextractorupdate) and then flashing those files via fastboot or your twrp version. Then, he has to use hrupdater 0.4 to install 8.0.0.143
Am I right Pretoriano80?
please, fell free to correct me if i have commited any mistake
PD: MANDATORY TO HAVE UNLOCKED BOOTLOADER FOR THE PROCESS
Click to expand...
Click to collapse
No, first he has to recover the current OS, and my advise was only for that.
Then he will need to use a TWRP + NoCheck combo, to get back to Oreo.
HuRUpdater can't get you back to Oreo so you guys should stop using that with Pie.
Mate 10 Pro BLA-L09
I also installed the EMUI 9.0 on my device using the HWOTA8 method which was successful. The EMUI 9.0 (9.0.0.108). I didn't have any issues too. After a while I decided to switch back to EMUI 8.0. using also HWOTA8 I put three zip files with EMUI8 (update.zip .....). Update ended with error. That's it.
I only have fastboot working but I am able to flash only few partitions System.img, Recovery_ramdisk.img, Kernel.img. I tried to flash them many times - nothing.
Couple months ago I messed up with my phone and I had to buy and use DC-Phoenix. It worked for me then. This time did not because DC-Phoenix only support EMUI 8. They refunded me money I paid for - that's good thing but my phone is still bricked.
Then I've found MultiTool for Huawei
https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
It shows that
https://gyazo.com/70820957c6638e27bfe79418dfb07e3e
(Firmware 9.0.0.108,device bla-l09,no serial number, no IMEI and battery status 0)
HiSuite says device is not supported.
Is there any way to force HiSuite to recover not supported device?
Anyone knows the solution?
I booked my phone for repair with Huawei Service.
diowil4 said:
I also installed the EMUI 9.0 on my device using the HWOTA8 method which was successful. The EMUI 9.0 (9.0.0.108). I didn't have any issues too. After a while I decided to switch back to EMUI 8.0. using also HWOTA8 I put three zip files with EMUI8 (update.zip .....). Update ended with error. That's it.
I only have fastboot working but I am able to flash only few partitions System.img, Recovery_ramdisk.img, Kernel.img. I tried to flash them many times - nothing.
Couple months ago I messed up with my phone and I had to buy and use DC-Phoenix. It worked for me then. This time did not because DC-Phoenix only support EMUI 8. They refunded me money I paid for - that's good thing but my phone is still bricked.
Then I've found MultiTool for Huawei
https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
It shows that
https://gyazo.com/70820957c6638e27bfe79418dfb07e3e
(Firmware 9.0.0.108,device bla-l09,no serial number, no IMEI and battery status 0)
HiSuite says device is not supported.
Is there any way to force HiSuite to recover not supported device?
Anyone knows the solution?
I booked my phone for repair with Huawei Service.
Click to expand...
Click to collapse
It should be possible to recover your phone.Tried to flash Pie B108 recovery_ramdisk, kernel and system with fastboot?
Pretoriano80 said:
It should be possible to recover your phone.Tried to flash Pie B108 recovery_ramdisk, kernel and system with fastboot?
Click to expand...
Click to collapse
I have tried. I flashed Pie 9.0.0.108 - nothing, 9.0.0.112 (chinese ver) - nothing. I tried BLA-L09 8.0.0.148(SP1C432) - nothing.
After flashing recovery_ramdisk, kernel and system of all above firmware there is no change only fastboot is working.
The problem is that downgrade process from Pie to Oreo went to 95% ( I thing - I don't remember exactly but for sure it was 90 something). It could have changed most of partitions to Oreo but left one or few unchanged (like verlist.img, xloadr.img, vendor.img, product.img).
From fastboot I am able to change (flash) only few partitions.
Do you gays know any other tools like dc-phoenix to force to flash all partitions. (Couple months ago when I used DC Phoenix with Emui 8 it used backdoor to flash difficult partitions.)
Example:
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...OK
diowil4 said:
I have tried. I flashed Pie 9.0.0.108 - nothing, 9.0.0.112 (chinese ver) - nothing. I tried BLA-L09 8.0.0.148(SP1C432) - nothing.
After flashing recovery_ramdisk, kernel and system of all above firmware there is no change only fastboot is working.
The problem is that downgrade process from Pie to Oreo went to 95% ( I thing - I don't remember exactly but for sure it was 90 something). It could have changed most of partitions to Oreo but left one or few unchanged (like verlist.img, xloadr.img, vendor.img, product.img).
From fastboot I am able to change (flash) only few partitions.
Do you gays know any other tools like dc-phoenix to force to flash all partitions. (Couple months ago when I used DC Phoenix with Emui 8 it used backdoor to flash difficult partitions.)
Example:
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...OK
Click to expand...
Click to collapse
I think you should use my TWRP + NoCheck recovery and try to flash the Pie beta again.
Pretoriano80 said:
I think you should use my TWRP + NoCheck recovery and try to flash the Pie beta again.
Click to expand...
Click to collapse
After flashing It cannot boot to recovery.
diowil4 said:
After flashing It cannot boot to recovery.
Click to expand...
Click to collapse
So you can only boot to fastboot, no matter what?
Pretoriano80 said:
So you can only boot to fastboot, no matter what?
Click to expand...
Click to collapse
Yes.