Related
Hi someone, i hope...
Recently i do a bad upgrade (I think that i flashed recovery on boot, ups!) and after a long, long while i have the phone working again But....
I can't change rom!!!!
Now i have:
- B609 boot unlocked
- B609 stock recovery
- B609 (Flashed through CWM, the only way i can do it)
But i can't change rom, not by dload, neither twrp, neither cwm
Some help? Any idea?
I can flash every recovery and i have tried to roolback b133, update b620 and even b805, but it doesnt work
Can i try another solution?
Thanks in advance!
I'm having the same issue, neither the original stock rom with emui 2.3 or any 3.0 rom install on my p7, all roms ends with an error and after booting there's some apps missing
EDIT: I've followed the only two guides on this forum and still can't install stock rom emui 2.3
So no way to downgrade from b805???
Hey guys... Look @ my edited answer here:
http://forum.xda-developers.com/showthread.php?p=60766165
I'll try! Thanks!
Tonight i've discovered another issue... :-/
When i switch off the phone and connect usb for charging, the phone switchs on, no charging screen, it boots
I think your phone is "dirty". I dont know the right word in english. Try my solution and be happy
Ohhhh! No luck! It gives me the same error, install failed
I've tried to erase the partitions with fastboot and it says: Command nos allowed, i think' perhaps i have security on, but i dont know how to s-off this terminal
I've entered in engineering mode and i can see: fastboot P7-L10C900B805 while i am in b609 (b805 was installed before the fail) so i have to try to downgrade fastboot. Unfortunately it cannot be done with fastboot, again "Command not allowed" :-S
Try to make a install via fastboot with all partions. I think you can try it with b609. If that not work - i have no idea ! I think that you have to wait for full b805, install that via dload and then you can downgrade. The same issue i have with b609 @ beginn
Flash MyROM 3.3, then flash a 3.0 stock recovery. Now do a normal update to the full b609 using the dload folder. Use thw update feature from the settings menu, and not the 3 button method. From here you can do the same for b621 and then b805.
Hope that helps.
I see this http://forum.xda-developers.com/showthread.php?t=3163748
I think thats help
No way
Nadir_Baderoon said:
Flash MyROM 3.3, then flash a 3.0 stock recovery. Now do a normal update to the full b609 using the dload folder. Use thw update feature from the settings menu, and not the 3 button method. From here you can do the same for b621 and then b805.
Hope that helps.
Click to expand...
Click to collapse
I've tried, same results It's is being complicated...
I can believe it!
87insane said:
I see this http://forum.xda-developers.com/showthread.php?t=3163748
I think thats help
Click to expand...
Click to collapse
Yujuuuuu!!!
I'm now in b800, crossing fingers and copying b609 to flash it.... Flashing!!! Fantastic!!!!!
Huawei cust fail, update post process fail
But I'm on b609, then let's try...
Flashing b621! It's solved!!!!
Thank you very much for your support!
:good::good::good::good::good::good::good::good:
The transition package was the key, but i wasn't thinking in emui version anytime....
b805 again... And.... Success!!!
TWRP and Root (http://forum.xda-developers.com/ascend-p7/general/guide-root-b803-recovery-version-t3157477)
All ok!!!
Thanks, thanks, thanks!
onosenday said:
Yujuuuuu!!!
I'm now in b800, crossing fingers and copying b609 to flash it.... Flashing!!! Fantastic!!!!!
Huawei cust fail, update post process fail
But I'm on b609, then let's try...
Flashing b621! It's solved!!!!
Thank you very much for your support!
:good::good::good::good::good::good::good::good:
The transition package was the key, but i wasn't thinking in emui version anytime....
b805 again... And.... Success!!!
TWRP and Root (http://forum.xda-developers.com/ascend-p7/general/guide-root-b803-recovery-version-t3157477)
All ok!!!
Thanks, thanks, thanks!
Click to expand...
Click to collapse
I'm going to try this method too, wish me luck
Hi All,
So Marshmallow 6.0 was just released today for ZD551KL Zenfone Selfie and I had basically trouble upgrading manually since I already have unlocked bootloader and have TWRP flashed instead of the original recovery.img which is needed to do the manual firmware upgrade from ASUS.
Since I no longer have my original recovery.img I was able to find the complete list of recovery.img, I'm glad someone uploaded it and i was able to find it.
If you're having trouble upgrading to Marshmallow from LP because of TWRP installed, flash the stock 1.15.40.1582 first and then flash the ASUS official MM firmware.
The recovery.img can be found here:
https://mega.nz/#F!Ao1RjT7D!hQ5x60r02WveB9-Hl32B4g!V0tUXT6a
I hope this helps.
Thanks
Finally you got the stock recovery. ?
Hit Thanks If I Helped
pjl3dm said:
The recovery.img can be found here:
https://mega.nz/#F!Ao1RjT7D!hQ5x60r02WveB9-Hl32B4g!V0tUXT6a
I hope this helps.
Thanks
Click to expand...
Click to collapse
Recovery images for ZE550KL/ZE600KL and ZE601KL/ZE551KL can be found here
It would be nice if you download are recovery images and provide direct download links here. Make a clean well documented thread. This will benefit many users
signature verification failed
I have ZD551KL Selfie,
I Got error as
E: failed to verify whole-file signature
E: signature verification failed
while update to MM Stock update.
i flashed stock recovery.
i previously installed CM-13 RR Rom
Help Need
Advance Thanks
Atm I'm on WW-1.15.40.1582, stock recovery and I'm trying to update to android M from the recovery, yet I got stuck on "Verifying update package..."
Fulga666 said:
Atm I'm on WW-1.15.40.1582, stock recovery and I'm trying to update to android M from the recovery, yet I got stuck on "Verifying update package..."
Click to expand...
Click to collapse
I think you need to update to latest LP firmware so that boot and recovery img get updated. Then it might not stuck at verifying update package. Although it did took time around 10 minutes in my Z00L to complete verifying image process while upgrading to MM.
Hope it helps
Hit Thanks If I Helped
kunalchitara said:
I think you need to update to latest LP firmware so that boot and recovery img get updated. Then it might not stuck at verifying update package. Although it did took time around 10 minutes in my Z00L to complete verifying image process while upgrading to MM.
Hope it helps
Hit Thanks If I Helped
Click to expand...
Click to collapse
well, I've been waiting for about 1 hour. What I did was to install the recovery from this thread then the latest L update, so I can also get the latest recovery, then tried updating to M. Adb sideload doesn't seem to work. I'll try once again.
Fulga666 said:
well, I've been waiting for about 1 hour. What I did was to install the recovery from this thread then the latest L update, so I can also get the latest recovery, then tried updating to M. Adb sideload doesn't seem to work. I'll try once again.
Click to expand...
Click to collapse
Well, did you booted the latest LP once, before upgrading to MM?
Hit Thanks If I Helped
kunalchitara said:
Well, did you booted the latest LP once, before upgrading to MM?
Hit Thanks If I Helped
Click to expand...
Click to collapse
Yes, ofc I dod boot it. I've been waiting since I last replied.
Fulga666 said:
Yes, ofc I dod boot it. I've been waiting since I last replied.
Click to expand...
Click to collapse
I am not sure but wiping system through fastboot might help.
Might lead devs like @sziraqui can help you on this more precisely.
Hit Thanks If I Helped
raindaddy said:
I have ZD551KL Selfie,
I Got error as
E: failed to verify whole-file signature
E: signature verification failed
while update to MM Stock update.
i flashed stock recovery.
i previously installed CM-13 RR Rom
Help Need
Advance Thanks
Click to expand...
Click to collapse
Fulga666 said:
Atm I'm on WW-1.15.40.1582, stock recovery and I'm trying to update to android M from the recovery, yet I got stuck on "Verifying update package..."
Click to expand...
Click to collapse
No need to flash stock recovery and last lollipop update. Just flash twrp and then use this guide
sziraqui said:
No need to flash stock recovery and last lollipop update. Just flash twrp and then use this guide
Click to expand...
Click to collapse
In the end I have simply placed the update zip in the internal memory and that did the job, I'll use twrp to flash the smoothified room when it's available for Z00T. Thanks anyway!
boot.img and recovery.img for zenfone 2 laser ZE500KL (vesion 13.10.7.1) ???
Hi,
I also had cm13 installed, now want to go back to asus stock rom WW-1.15.40.1582, I have installed original boot and recovery from link posted in original post, however when I try flashing through adb I am getting error 'can not read zip' while installing from sd card I get message 'verifying update package' and it goes back to recovery home screen thereafter
Please help
Fulga666 said:
Atm I'm on WW-1.15.40.1582, stock recovery and I'm trying to update to android M from the recovery, yet I got stuck on "Verifying update package..."
Click to expand...
Click to collapse
Did u whipe data before update..?
Reboot ur phone first and wait after loading complete try to update..
Hope this help
is there a recovery img for ZE550KL? 21.40.1220.1877 new update. tnx
Has someone the stock recovery.img for ze551kl z00td WW_user_21.40.1220.1615 ?
Sent from my ASUS_Z00TD using XDA-Developers mobile app
Stock Recovery for WW-21.40.1220.1943 (Zenfone 2 Laser ZE550KL @ 2 GB)
Please provide the download links
I need ZE601KL Files to Recover IMEI.
I need help. Whoever has ZenFone 2 Laser model ZE601KL SKU WW has root or system comstum, could you send me these files so I repair my system that does not recognize the imei.
Do the following process below.
Active in Android:
Active USB Depuration
Select Acess Root ADB Mode
Commands Terminal use ADB.exe
adb shell
su
cat /dev/block/mmcblk0p17 > /mnt/sdcard/fsc.mbn
cat /dev/block/mmcblk0p16 > /mnt/sdcard/fsg.mbn
cat /dev/block/mmcblk0p41 > /mnt/sdcard/modemst.img
cat /dev/block/mmcblk0p18 > /mnt/sdcard/modemst1.img
cat /dev/block/mmcblk0p19 > /mnt/sdcard/modemst2.img
Take these files saved in your internal memory and send me, thank you.
[QUOTE="raindaddy, post: 67571907, member: 7561460"]I have ZD551KL Selfie, I Got error as E: failed to verify
how did you successfully flashed stock rom UL-Z00T-WW-1.15.40.1582-user.zip? i have ZD551KL Selfie too. i tried to flash many stock roms for my Zenfie but no luck.
please help
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
Honor 4x hanged (in some Indian kitkat version, not rooted) and after restart it is in bootloop. Honor logo appears then blue light starts to appear then restart.
Recovery mode and dload update not working.
After unlocking bootloader tried fastboot -w, still in bootloop.
Extracted Lollipop, Marshmallow, Kitkat - B161, B126 and flashed in fastboot. Possible to flash only recovery, boot, userdata & system. For others - failed : remote command not allowed. After flashing no change, still in bootloop.
Tried to boot to recovery from fastboot boot
- for lollipop and marshmallow recoveries it says "dtb not found"
- others including twrp, cm it is in bootloop.
Out of warranty.
Need help.
oppili said:
Honor 4x hanged (in some Indian kitkat version, not rooted) and after restart it is in bootloop. Honor logo appears then blue light starts to appear then restart.
Recovery mode and dload update not working.
After unlocking bootloader tried fastboot -w, still in bootloop.
Extracted Lollipop, Marshmallow, Kitkat - B161, B126 and flashed in fastboot. Possible to flash only recovery, boot, userdata & system. For others - failed : remote command not allowed. After flashing no change, still in bootloop.
Tried to boot to recovery from fastboot boot
- for lollipop and marshmallow recoveries it says "dtb not found"
- others including twrp, cm it is in bootloop.
Out of warranty.
Need help.
Click to expand...
Click to collapse
Oh ****, that seems like a frustrating situation. What made the device mess up so much? Have you gone to service centres?
Regards,
PoseidonKing
Not tried to flash or root. It just hanged while using.
Service centre said board gone (as always). MTK devices have a factory mode through which we can check working of all board parts. I did not find any way for this.
oppili said:
Not tried to flash or root. It just hanged while using.
Service centre said board gone (as always). MTK devices have a factory mode through which we can check working of all board parts. I did not find any way for this.
Click to expand...
Click to collapse
Sorry bro, can't help you out over here in this situation.... Best of Luck regarding your device. I would suggest pm'ing a forum moderator for your issue
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
HELP.!!Back to Stock Rom ????
I am struggling like anything to go back to stock rom. I am using Honor 4x Che1-L04 snapdragon. Pls send a link where can i find the instructions to do this. Or Better U expain.
EDIT:
Roll back to EMUI 4.0 success. Used the Hauwei update extractor and used CMD. Anyhow THANKS
NEW Problem:
How to enable ADOPTED STORAGE in honor 4x che1-L04 snapdragon edition.
In Xda they mentioned only about the kirin processor version.
Help!!!!!!!!!!
balongc52b311 after failing kangvip 6.7.1
hey there. will tell you my experience with failing to flashing kangvip 6.7.1 due to wiping problem
i wiped my cache, data, system even internal storage and yet failed to flashing kangvip 6.7.1 4 custom rom due to "cust" folder unable to mount giving me this:
error 1 can't mount /cust (Invalid argument)
so after failing to mount that folder and even deleting it by mistake,i got a new error:
error 1 can't mount cust no such file or directory
i lost hope and let my my honor 4x normally boot but it took too long and i was determined its stuck on bootloop :cyclops:
i woke up today finding it on 5% battery and giving me that first time setup as if all i did was a factory format BUT all in chinese. checked the build number and it was balongc52b311.
i tried mounting "cust" folder to r/w and rebooted into bootloader but it gave me the same first error. i tried deleting the folder and then rebooting into recovery and it gave me the 2nd error. created the folder "/cast" and then rebooted into recovery and it gave me the same first problem that the folder can't mount EVENTHO it was mounted successfully right before i rebooted into recovery (did this 3 times to make sure)
did some researching and found a solution for honor 4c http://forum.xda-developers.com/honor-4x/help/huawei-honor-4x-balong-hi6210sft-fixed-t3324335 or two BUT both for lolllipop and i'm marshmallow.
i'm already halfway at the method i mentioned above but i stopped after i realized it was for lollipop. i rooted my mobile and changed my build number to "Che2-L11C636B330". worth to mention that my model number remained already the same "Che2-L11".
the cust folder error is still there whenever i go to the bootloader
now i have no idea what to do, what firmware to download and if i have to downgrade first to lollipop and then upgrade to marshmallow again...
my marshmallow version was the middle east final version before this balong happened: Che2-L11C185B561 and i would like to go back to it again.. thank you in advance ( :
###*UPDATED BELOW*
fixed my problem trying the method here http://forum.xda-developers.com/honor-8/help/honor-8-rooted-twrp-modaco-rom-unable-t3462039/page2
>>>>worth to mention that i flashed my oeminfo for my UPDATE.APK REGION before flashing the extracted files from UPDATE.APP "wasn't mentioned in that method"
now i'm back to my original marshmallow version "middle east". good luck people.
abdurrahmanzaki said:
hey there. will tell you my experience with failing to flashing kangvip 6.7.1 due to wiping problem
i wiped my cache, data, system even internal storage and yet failed to flashing kangvip 6.7.1 4 custom rom due to "cust" folder unable to mount giving me this:
error 1 can't mount /cust (Invalid argument)
so after failing to mount that folder and even deleting it by mistake,i got a new error:
error 1 can't mount cust no such file or directory
i lost hope and let my my honor 4x normally boot but it took too long and i was determined its stuck on bootloop :cyclops:
i woke up today finding it on 5% battery and giving me that first time setup as if all i did was a factory format BUT all in chinese. checked the build number and it was balongc52b311.
i tried mounting "cust" folder to r/w and rebooted into bootloader but it gave me the same first error. i tried deleting the folder and then rebooting into recovery and it gave me the 2nd error. created the folder "/cast" and then rebooted into recovery and it gave me the same first problem that the folder can't mount EVENTHO it was mounted successfully right before i rebooted into recovery (did this 3 times to make sure)
did some researching and found a solution for honor 4c http://forum.xda-developers.com/honor-4x/help/huawei-honor-4x-balong-hi6210sft-fixed-t3324335 or two BUT both for lolllipop and i'm marshmallow.
i'm already halfway at the method i mentioned above but i stopped after i realized it was for lollipop. i rooted my mobile and changed my build number to "Che2-L11C636B330". worth to mention that my model number remained already the same "Che2-L11".
the cust folder error is still there whenever i go to the bootloader
now i have no idea what to do, what firmware to download and if i have to downgrade first to lollipop and then upgrade to marshmallow again...
my marshmallow version was the middle east final version before this balong happened: Che2-L11C185B561 and i would like to go back to it again.. thank you in advance ( :
###*UPDATED BELOW*
fixed my problem trying the method here http://forum.xda-developers.com/honor-8/help/honor-8-rooted-twrp-modaco-rom-unable-t3462039/page2
>>>>worth to mention that i flashed my oeminfo for my UPDATE.APK REGION before flashing the extracted files from UPDATE.APP "wasn't mentioned in that method"
now i'm back to my original marshmallow version "middle east". good luck people.
Click to expand...
Click to collapse
Thanks on the update about your success on restoring your phone. Surely some poor soul will get along the same problem and your post will help him out. Sorry for the late reply btw.
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
How to Root my honor 4x Che2-L11?
Hi everyone, I'm noob, so I need a step to step guide if there's such a thing
my android version is 6.0 and EMUI 4.0
I have bootloader code for unlocking the phone, thanks in advance guys, also happy new year :good:
Phone Honor 4x (che1-L04) Stuck in fastboot mode
My phone is stuck in fastboot mode. Couldn't get the bootloader unlock key online as it requires the product id which can be obtained by dialing a number which isn't possible. I have requested directly from the customer care number and the official chat portal as well but its been more than a week and still they are asking for 24 working hours. Is there any alternative method of getting the key or atleast the Product ID?
Model name :Che1-L04
Stuck in Fastboot & Rescue mode with the bootloader locked.
I got unlock key after 12 days. Honor 4x hanged after restart it is in bootloop.
3 button sd card update not working ?
oppili said:
I got unlock key after 12 days. Honor 4x hanged after restart it is in bootloop.
3 button sd card update not working ?
Click to expand...
Click to collapse
No the update.app isnt working I guess because I have already flashed the CM13 recovery image with the bootloader locked. However, I recieved the bootloader key yesterday from the email but when I tried unlocking by the fastboot command it said it is an invalid or wrong key. Is there any other way to take my phone back to stock condition atleast without actually unlocking the Bootloader?
Princeshubh said:
No the update.app isnt working I guess because I have already flashed the CM13 recovery image with the bootloader locked. However, I recieved the bootloader key yesterday from the email but when I tried unlocking by the fastboot command it said it is an invalid or wrong key. Is there any other way to take my phone back to stock condition atleast without actually unlocking the Bootloader?
Click to expand...
Click to collapse
1. Try "fastboot continue" it will directly boot without going to recovery.
2. If fastboot flash works flash recovery of the firmware installed in phone before bootloop.
3. If still not works flash boot, system, recovery (in this order) of firmware installed before bootloop.
Confirm unlock key with customer care if it is still locked.
I wanna know is there any other method to install xposed framework since the normal installation is not working for me.
Using Honor 4x Che1-l04 running on (stock ROM) Android marshmallow 6.0.1, have TWRP custom recovery and is rooted.
SumitGupta2442 said:
I wanna know is there any other method to install xposed framework since the normal installation is not working for me.
Using Honor 4x Che1-l04 running on (stock ROM) Android marshmallow 6.0.1, have TWRP custom recovery and is rooted.
Click to expand...
Click to collapse
no other way, unfortunatly.. one way or the other, you have to flash the zip...
ps: if you are on emui, first boot after flashing xposed will take a really long time.. mine took around 25 minutes to boot.. so dont consider it a boot loop, wait untill 30 minutes and you will be profitted
Mine was in boot screen for around 3 minutes and then rebooted into recovery. Same thing was happening again and again. So at last did the restore process from TWRP.
oppili said:
1. Try "fastboot continue" it will directly boot without going to recovery.
2. If fastboot flash works flash recovery of the firmware installed in phone before bootloop.
3. If still not works flash boot, system, recovery (in this order) of firmware installed before bootloop.
Confirm unlock key with customer care if it is still locked.
Click to expand...
Click to collapse
Its not working. Please help me I am still stuck....any way of installing the stock ROM back via fastboot mode with the phone showing 'Phone Locked'
Restoring TOO MUCH with twrp?
Can restoring too much with TWRP damage my phone?
jwalker9715 said:
Can restoring too much with TWRP damage my phone?
Click to expand...
Click to collapse
not really..
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
hi guys,
yesterday i installed the oreo beta on my VTR-L29 but then i brickedd it *cry*. unfortunateley the unbrick methods found here in the forum don't work because the oreo update made some changes in the system file structure...
has anyone an idea what to do?
maybe someone can provide me a recovery image for twrp? (one for oreo, otherwise it wont work) so i can give this a try...
after over 10 hours of fiddeling around a found a really easy solution:
most of you know HWOTA helps with this, but the "normal" version wont work after flashing oreo. but this version is flashed via twrp and is still working!
but you will need a oreo compatible twrp, which you can find here
i know the links are to mate 9 software, but since the p10 and mate 9 are nearly identical, it works on the p10 as well
can you post the step by step guide?
i am on oreo 8.0.0.046 and want to flash another version, or downgrade to nougat because few things don't work on this version
i dont know if downgrading works, i just reflashed the latest oreo.
accordingly to the first link it should work, just flash the TWRP from the second link and then follow the instructions from the first link.
johdost said:
i dont know if downgrading works, i just reflashed the latest oreo.
accordingly to the first link it should work, just flash the TWRP from the second link and then follow the instructions from the first link.
Click to expand...
Click to collapse
failed install twrp- error find twrp 3.0.3, and i replaced to oero mate 9 recovery....
EDIT: success - problem was on the computer
johdost said:
i dont know if downgrading works, i just reflashed the latest oreo.
accordingly to the first link it should work, just flash the TWRP from the second link and then follow the instructions from the first link.
Click to expand...
Click to collapse
i did sucsses to install twrp but on the second step, when i press on install on twrp, the phone restart to erocovey and failed to find the files. what am i doing wrong?
i think that i am stuck with that version forever....
if you reboot to erecovery, you have not successfully installed twrp. you have to install it with "fastboot flash recovery_ramdisk <path to twrp>"
johdost said:
if you reboot to erecovery, you have not successfully installed twrp. you have to install it with "fastboot flash recovery_ramdisk <path to twrp>"
Click to expand...
Click to collapse
you misunderstood me.
i do have twrp, i created HWOTA8 folder on sd card, copied hwota8 update zip, MHA_RECOVERY8 No check and the 3 files that i renamed as it said. after that, from twrp i clicked on hwota8 update zip and begin flash, the phone reboot to stock recovery and failed to install - "files don't found".
please help me fegure out what's the problem.
thanks
t.h.i said:
you misunderstood me.
i do have twrp, i created HWOTA8 folder on sd card, copied hwota8 update zip, MHA_RECOVERY8 No check and the 3 files that i renamed as it said. after that, from twrp i clicked on hwota8 update zip and begin flash, the phone reboot to stock recovery and failed to install - "files don't found".
please help me fegure out what's the problem.
thanks
Click to expand...
Click to collapse
EDIT : the process is sucsses, but its the same version.... 8.0.0.046
Bricked, no TWRP access, any ideas?
Hi.
I know this about a P10, I have a P10 Plus (VKY-L29C605), but the process should be similar, I think.
I bricked my phone after succesfully upgrading from B174 to B321 using HWOTA. After which I decided, since I was at it, to flash the Hyperplus Kernel. This led to a bootloop. To fix it I decided to just go ahead and HWOTA B321 all over again and get over it, and would have probably gone just fine, except I decided to rebrand (C605 > C432) while I was doing that, silly (no, stupid) mistake. This led to the brick I am currently expriencing, I have no recovery access, erecovery or TWRP.
So now I am left trying to unbrick the phone. I extracted the UPDATE.APP for both update_all_hw.zip and update.zip using the Huawei Extractor Tool with no difficulty, except unbricking methods ask for boot.img, which I could not find, so I went along without it and flashed: cust.img, recovery_ramdisk.img (using fastboot recovery_ramdisk command for Oreo), and system.img. All of the commands completed succesfully, but no shebang, still bricked and no recovery access. I figure this has to do with the rebrand as the result after executing the command "fastboot getvar vendorcountry" shows the rebrand pulled through (hw/eu 432).
I am currently downloading HWOTA8.zip (3GB worth of download) to see if I can do something it. I am also downloading the L29C432B360 OTA-FULL, since I believe I am not getting any progress becuase I used the updates for L29C605B321.
The kind people at funkyhuawei told me they could fix it with their tool, but I don't have the money for that right now.
I will post updates, but any ideas would be greatly appreciated.
Many of us have posted over this in the last couple of days. Seems like Funky Huawei unbrick tool was the mehtod to get it work for me. You could try that!
or use dc-phoenix for me it worked (= in the moment i try to capture the usb ports kommunikation so i have the tool with the aktual firmware longer for 3 days :silly:
would first give dc a try 20 bucks for 3 days is ok i think (=
johdost said:
hi guys,
yesterday i installed the oreo beta on my VTR-L29 but then i brickedd it *cry*. unfortunateley the unbrick methods found here in the forum don't work because the oreo update made some changes in the system file structure...
has anyone an idea what to do?
maybe someone can provide me a recovery image for twrp? (one for oreo, otherwise it wont work) so i can give this a try...
Click to expand...
Click to collapse
Must download some software for your phone, unzip update.zip, decompile UPDATE.APP to .iso files, (like recovery.iso, system, iso, vendor iso, boot iso) use fastboot and 10 minuts job, I brik my device over 10 thimes, and repair it.
So I was able to get the C432B360 firmware and I flashed it, but no I can't enter recovery mode because the battery is low (red lightning bolt/red led flash). Anybody know how to charge or force recovery mode boot from fastboot?
If anyone needs, can use my DC-Phoenix account, I don`t need it anymore.
Your username is: cesedy
Your password is: dnL4eHEm
Greting
ure3808 said:
Must download some software for your phone, unzip update.zip, decompile UPDATE.APP to .iso files, (like recovery.iso, system, iso, vendor iso, boot iso) use fastboot and 10 minuts job, I brik my device over 10 thimes, and repair it.
Click to expand...
Click to collapse
Greeting,
Can you explain the procedure of how to do it?
Thank you