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
Related
I got the update for 5.1.1 but when I pressed install, it took me to twrp recovery and did not install anything. I tried to manually flash it but it showed error executing updater binary. Then I flashed cwm recovery and tried again but I got the same error. PLEASE HELP ME!!
Btw i am rooted.
rkrohan said:
I got the update for 5.1.1 but when I pressed install, it took me to twrp recovery and did not install anything. I tried to manually flash it but it showed error executing updater binary. Then I flashed cwm recovery and tried again but I got the same error. PLEASE HELP ME!!
Btw i am rooted.
Click to expand...
Click to collapse
you need stock recovery bro....
Saurabh K said:
you need stock recovery bro....
Click to expand...
Click to collapse
I am rooted but I have stock recovery
100% stock LMY47O required, no mods, no customs.........
How to successfully install 5.1.1 on Android One
There is another thread where the solution for your problem is given!
Check this link
http://forum.xda-developers.com/cro...o-official-t3122884/post61145935#post61145935
The posts in the end of this thread might help you
Hi, I'm new to this forum.
I have a problem with my phone.
After rooting it was good, but later I wanted to upload another ROM and confused the versions to the Snapdragon processor than HiSilicon and now I don't have a baseband and IMEI.
I have tried the original 6.0, 5.1 trough adb-fastboot, because I can't restore trough dload, I had message 'Install software failed' and nothing helps.
Do you have any ideas?
moczu17 said:
Hi, I'm new to this forum.
I have a problem with my phone.
After rooting it was good, but later I wanted to upload another ROM and confused the versions to the Snapdragon processor than HiSilicon and now I don't have a baseband and IMEI.
I have tried the original 6.0, 5.1 trough adb-fastboot, because I can't restore trough dload, I had message 'Install software failed' and nothing helps.
Do you have any ideas?
Click to expand...
Click to collapse
I don't know, but maybe @MarcoPLs or @panchovix has an idea? Sorry to quote you guys, but this is a quite important question: What if someone flashes the wrong rom? Honor 4x can be confusing with snapdragon/kirin versions.
Bob1900 said:
I don't know, but maybe @MarcoPLs or @panchovix has an idea? Sorry to quote you guys, but this is a quite important question: What if someone flashes the wrong rom? Honor 4x can be confusing with snapdragon/kirin versions.
Click to expand...
Click to collapse
Flashing sd rom is 100% brick.
Try to use rollback package and then reflash lollipop. (you can also try to flash marshmallow with updateappflasher but i think it flash only stuff you need to boot)
http://www.hihonor.com/uk/support/details/index.html?DOC_ID=82283
moczu17 said:
Hi, I'm new to this forum.
I have a problem with my phone.
After rooting it was good, but later I wanted to upload another ROM and confused the versions to the Snapdragon processor than HiSilicon and now I don't have a baseband and IMEI.
I have tried the original 6.0, 5.1 trough adb-fastboot, because I can't restore trough dload, I had message 'Install software failed' and nothing helps.
Do you have any ideas?
Click to expand...
Click to collapse
If you can boot to TWRP use this method to install stock rom.
https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702
keikari said:
If you can boot to TWRP use this method to install stock rom.
https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702
Click to expand...
Click to collapse
I think using stock recovery is better for fixing bugs because it flash all partitions
MarcoPLs said:
I think using stock recovery is better for fixing bugs because it flash all partitions
Click to expand...
Click to collapse
If you install with that you can have easier access to use dload method.
MarcoPLs said:
I think using stock recovery is better for fixing bugs because it flash all partitions
Click to expand...
Click to collapse
I tried to use rollback, but always durning instalation from dload 'Instal software failed'...
I tried too method with TWRP, but durning instalation:
' unmounf of /system failed; no such volume
unmounf of /cust failed; no such volume
write radio image...
E:unknow command [errno]
Updater process ended with ERROR: 7 '.
I'm worried...
moczu17 said:
I tried to use rollback, but always durning instalation from dload 'Instal software failed'...
I tried too method with TWRP, but durning instalation:
' unmounf of /system failed; no such volume
unmounf of /cust failed; no such volume
write radio image...
E:unknow command [errno]
Updater process ended with ERROR: 7 '.
I'm worried...
Click to expand...
Click to collapse
Flash system and cust with fastboot and use twrp flasher again.
(rollback is not full update, you have formated system thats why it also failed)
MarcoPLs said:
Flash system and cust with fastboot and use twrp flasher again.
(rollback is not full update, you have formated system thats why it also failed)
Click to expand...
Click to collapse
OK, done, but I still can't install rollback and stock ROM.
Now I only have:
'write radio image...
E:unknow command [errno]
Updater process ended with ERROR: 7 '.
moczu17 said:
OK, done, but I still can't install rollback and stock ROM.
Now I only have:
'write radio image...
E:unknow command [errno]
Updater process ended with ERROR: 7 '.
Click to expand...
Click to collapse
unknow command is nornal.
im not sure what status 7 could be. you are not trying to flash rollback with twrp? with twrp you can only flash full roms
I tried flash rollback from dload, but failed.
I tried flash full stock rom MM b535 trough TWPR, but failed, so I don't know...
I must trying with other rom or meta-inf is wrong?
It works!
I extract META-INF in Huawei Multi-Tool and install rollback in TWRP, but I still didn't have baseband and IMEIs.
I flashed 6.0 B535 trough adb.
Extract from update.app and flash, flash, flash *.img.
Only full packages work, so thanks for Your help!
moczu17 said:
It works!
I extract META-INF in Huawei Multi-Tool and install rollback in TWRP, but I still didn't have baseband and IMEIs.
I flashed 6.0 B535 trough adb.
Extract from update.app and flash, flash, flash *.img.
Only full packages work, so thanks for Your help!
Click to expand...
Click to collapse
Have you restored your IMEI numbers or not?
If not flash stock ROM which you got with your device.
Yes, I have restored my IMEI.
moczu17 said:
Yes, I have restored my IMEI.
Click to expand...
Click to collapse
how did you get succeeded by flashing stock rom or any other?
moczu17 said:
Yes, I have restored my IMEI.
Click to expand...
Click to collapse
Can you let us know how you were able to solve this ?
I wrote, that I flashed rom 6.0 B535 trough adb.
I extracted file update.app in huawei extractor and manually flashed images.
Only full packages work...
moczu17 said:
I wrote, that I flashed rom 6.0 B535 trough adb.
I extracted file update.app in huawei extractor and manually flashed images.
Only full packages work...
Click to expand...
Click to collapse
Ya,sure it is one of the best way to regain lost phone information.
moczu17 said:
I wrote, that I flashed rom 6.0 B535 trough adb.
I extracted file update.app in huawei extractor and manually flashed images.
Only full packages work...
Click to expand...
Click to collapse
Glad u sorted things on your own .hope to see u helping someone in future. Goodluck
moczu17 said:
I wrote, that I flashed rom 6.0 B535 trough adb.
I extracted file update.app in huawei extractor and manually flashed images.
Only full packages work...
Click to expand...
Click to collapse
please edit the title and write as [solved ] in front of the question
Hello,
Instead of wipe data, I formatted the internal memory.
I tried to go through twrp or fastboot to reflash but it does not work.
I flash the boot and recovery with TWRP "twrp-3.1.1-0-venus.img", but it does not work with the system.img file.
In fastboot mod, I flashed boot.img and recovery img that I retrieved on a stock ROM, but when I try to flash system.img I have the error message : "failed (remote: sparse flash write failure)".
Thx for your help
Try to use the Multi-tool form Team MT,you can unbrick your phone with it.
:good:
AlexMihai26 said:
Try to use the Multi-tool form Team MT,you can unbrick your phone with it.
Click to expand...
Click to collapse
Thx for your help AlexMihai26 :good:,
I
I managed to start the phone, but it is not the right ROM, I have to put the build NMO-L31C185B170 (emui4.1 android 6). At this moment, the phone starts with the NRD90M test-keys build (emui 5.0 android 7).
Hello,
Thanks to those who helped me. I finally solved my problem by installing a "Rollback Package" for NMO-L31C636B300, South-asia that I found on this page http://consumer.huawei.com/np/mobile-phones/support/downloads/detail/gr5-mini-np.htm?id=94461
I then installed an update.app of the official ROM NMO-L31C185B171 is normally everything got back in order. There it uploads an update NMO-L31C185B171-FULL. I will publish my message to inform you of the continuation. I hope it will help the clumsy like me.
Edit. The smartphone moved to EMUI 5.0 in OTA Build NMO-L31C185B356. Everything is back to normal. I have no problem anymore.
Resolved
sarrazinX said:
Hello,
Thanks to those who helped me. I finally solved my problem by installing a "Rollback Package" for NMO-L31C636B300, South-asia that I found on this page http://consumer.huawei.com/np/mobile-phones/support/downloads/detail/gr5-mini-np.htm?id=94461
I then installed an update.app of the official ROM NMO-L31C185B171 is normally everything got back in order. There it uploads an update NMO-L31C185B171-FULL. I will publish my message to inform you of the continuation. I hope it will help the clumsy like me.
Edit. The smartphone moved to EMUI 5.0 in OTA Build NMO-L31C185B356. Everything is back to normal. I have no problem anymore.
Resolved
Click to expand...
Click to collapse
That is great.
Please, edit the title of the thread as solved
Hello,
Some weeks ago I have rooted my P10 with magisk (and twrp as recovery). Now I hot update Infos for new fw B371 (C432). Ota update won't work so I downloaded full Ota with huawei firmware finder. After download phone restarts but no update. It boots to recovery. Do I have to install the update files manually or isn't an update possible.
Thanks
painkiller_one said:
Hello,
Some weeks ago I have rooted my P10 with magisk (and twrp as recovery). Now I hot update Infos for new fw B371 (C432). Ota update won't work so I downloaded full Ota with huawei firmware finder. After download phone restarts but no update. It boots to recovery. Do I have to install the update files manually or isn't an update possible.
Thanks
Click to expand...
Click to collapse
Just flash a stock oreo recovery, and you should be fine.
Use my guide. Tutorial #3 is the right one.
https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286
Thanks. So root will be undone with this process? After this I can easily install twrp and magisk again without any problems?
Edit: Testet this, but install of officialupdate.zip failed (put the directory in /cust - boot into TWRP, mount cust and tried to install officialupdate.zip). Install from sdcard won´t work too.
Anyone has a solution to fix this. Removed root but it won't work.
Please post the TWRP log after trying to install officialupdate.zip. I need to know, what's failing so I'm able to help you out.
Jannomag said:
Please post the TWRP log after trying to install officialupdate.zip. I need to know, what's failing so I'm able to help you out.
Click to expand...
Click to collapse
Tried the root method (install from /cust directory) but again error. And here is the log from TWRP:
https://pastebin.com/1EL41MV5
Hope it is ok with pastebin link?
Thanx
painkiller_one said:
Tried the root method (install from /cust directory) but again error. And here is the log from TWRP:
https://pastebin.com/1EL41MV5
Hope it is ok with pastebin link?
Thanx
Click to expand...
Click to collapse
Okay, I can't figure it out, the log says error in line 141 in my script. I tried this on my phone and there's no such error.
What this script does is quiet simple - it just flashes a modified EMUI recovery, where the file and online check are disabled. So, you can flash the recovery from the archive manually via fastboot with "fastboot flash recovery_ramdisk PATH\TO\RECOVERY.IMG".
Then restart and do the update via Settings or FF.
After this you need to reroot, so reinstall TWRP and Magisk / SuperSU.
Jannomag said:
Okay, I can't figure it out, the log says error in line 141 in my script. I tried this on my phone and there's no such error.
What this script does is quiet simple - it just flashes a modified EMUI recovery, where the file and online check are disabled. So, you can flash the recovery from the archive manually via fastboot with "fastboot flash recovery_ramdisk PATH\TO\RECOVERY.IMG".
Then restart and do the update via Settings or FF.
After this you need to reroot, so reinstall TWRP and Magisk / SuperSU.
Click to expand...
Click to collapse
Ok thanks for looking. Don´t know why it won´t work. Device was simply rooted with TWRP + Magisk. Ok will try out manual way. Wiht Archive you mean this: https://forum.xda-developers.com/p10/development/recovery-p10-vtr-l09-t3782163 ?
painkiller_one said:
Ok thanks for looking. Don´t know why it won´t work. Device was simply rooted with TWRP + Magisk. Ok will try out manual way. Wiht Archive you mean this: https://forum.xda-developers.com/p10/development/recovery-p10-vtr-l09-t3782163 ?
Click to expand...
Click to collapse
No, my officialupdate rar achive, it contains the zip for TWRP and a recovery IMG file. This is the right one.
OK then you mean the VTR_RECOVERY_OREO-NoCheck.img. I will check this. Thanks
Jannomag said:
No, my officialupdate rar achive, it contains the zip for TWRP and a recovery IMG file. This is the right one.
Click to expand...
Click to collapse
Update worked only via Firmware Finder. But all is fine now. Reinstalled TWRP and magisk (no data loss) and all is working. Thanks for your help.
painkiller_one said:
Update worked only via Firmware Finder. But all is fine now. Reinstalled TWRP and magisk (no data loss) and all is working. Thanks for your help.
Click to expand...
Click to collapse
Would you mind sharing the steps you took to make it work?
I'm travelling abroad and keep getting the update reminder, and I'm too afraid to get an unusable phone to try anything
I have installed Lineage OS 18 Android 11 Rom from below thread,
https://forum.xda-developers.com/realme-x2-pro/development/rom-lineageos-18-0-realme-x2-pro-t4177291
I have used the OrangFox R11 Recovery for the installation.
Now I can not go back to stock C.33 firmware. I have tried installing OZIP both with TWRP and OrangeFox but no luck so far. Whenever the installation completes and I reboot the device, it shows boot/recovery damaged error message.
I have tried OZIP installation followed by vbmeta.img flashing as well. But no luck. Still the same error message.
I have tried flashing fastboot rom with all files (but no recovery img was inside) as well but still the same error.
I have tried RealMe Flash Tool with Firmware OFP but still the same error.
I'm simply stuck on this LineagOS 18 rom and I badly wanna go back to the Stock rom. :crying:
Please help!
P.S : If this thread needs to be moved somewhere elsle please be kind enough to do so. I'm not so familiar with thread openings. Sorry about it. :fingers-crossed:
Format data after flashing Ozip thats important . try that with twrp
Anask3444 said:
Format data after flashing Ozip thats important . try that with twrp
Click to expand...
Click to collapse
Already tried bro.. no luck
ImperoDroider said:
Already tried bro.. no luck
Click to expand...
Click to collapse
Did you try the fastboot flashable images?
https://forum.xda-developers.com/re...ock-fastboot-flashable-images-realme-t4003107
ImperoDroider said:
I have installed Lineage OS 18 Android 11 Rom from below thread,
https://forum.xda-developers.com/realme-x2-pro/development/rom-lineageos-18-0-realme-x2-pro-t4177291
I have used the OrangFox R11 Recovery for the installation.
Now I can not go back to stock C.33 firmware. I have tried installing OZIP both with TWRP and OrangeFox but no luck so far. Whenever the installation completes and I reboot the device, it shows boot/recovery damaged error message.
I have tried OZIP installation followed by vbmeta.img flashing as well. But no luck. Still the same error message.
I have tried flashing fastboot rom with all files (but no recovery img was inside) as well but still the same error.
I have tried RealMe Flash Tool with Firmware OFP but still the same error.
I'm simply stuck on this LineagOS 18 rom and I badly wanna go back to the Stock rom. :crying:
Please help!
P.S : If this thread needs to be moved somewhere elsle please be kind enough to do so. I'm not so familiar with thread openings. Sorry about it. :fingers-crossed:
Click to expand...
Click to collapse
If it says "boot/recovery damaged" and you're still able to use your phone, you should consider yourself lucky. I had to send mine in warranty for repair. I too am trying to go back to stock ROM after installing LOS 18.
Schumanzuar said:
Did you try the fastboot flashable images?
https://forum.xda-developers.com/re...ock-fastboot-flashable-images-realme-t4003107
Click to expand...
Click to collapse
These images have bricked my phone! Error message:
The current image(boot/recovery) have been destroyed and can not boot.
Please flash the correct image or contact customer service to fix it.
Tried flashing TWRP, no luck. Cannot boot.
do you have flash again the vbmeta.bin
I do that and after the rom start again for me
rpfe26 said:
do you have flash again the vbmeta.bin
I do that and after the rom start again for me
Click to expand...
Click to collapse
I didn't try that, however I did manage to get my phone up and working again after having destroyed the boot/recovery
I used Realme Flash Tool in combination with TWRP to get the phone up and running.
ImperoDroider said:
I have installed Lineage OS 18 Android 11 Rom from below thread,
https://forum.xda-developers.com/realme-x2-pro/development/rom-lineageos-18-0-realme-x2-pro-t4177291
I have used the OrangFox R11 Recovery for the installation.
Now I can not go back to stock C.33 firmware. I have tried installing OZIP both with TWRP and OrangeFox but no luck so far. Whenever the installation completes and I reboot the device, it shows boot/recovery damaged error message.
I have tried OZIP installation followed by vbmeta.img flashing as well. But no luck. Still the same error message.
I have tried flashing fastboot rom with all files (but no recovery img was inside) as well but still the same error.
I have tried RealMe Flash Tool with Firmware OFP but still the same error.
I'm simply stuck on this LineagOS 18 rom and I badly wanna go back to the Stock rom. :crying:
Please help!
P.S : If this thread needs to be moved somewhere elsle please be kind enough to do so. I'm not so familiar with thread openings. Sorry about it. :fingers-crossed:
Click to expand...
Click to collapse
I managed to get my phone up and running. Did you manage to get yours?
Milan-XDA said:
I managed to get my phone up and running. Did you manage to get yours?
Click to expand...
Click to collapse
You mean you got it back to stock from lineage os 18 by flashing through realme flash tool?
adimegarocker said:
You mean you got it back to stock from lineage os 18 by flashing through realme flash tool?
Click to expand...
Click to collapse
Yes, that is correct.