So I've got Zenfone 5 A501CG. As you may know, all cyanogens/roms are made for A500CG. It works on A501CG aswell, but once you unlock bootloader on this model, camera will stop working. It's caused by incompatible .bin files for motherboard. But when you relock bootloader, camera is working again, just fine. I did this like 5 times and it always worked.
Now I reverted from Resurrection 5.5.9/TWRP 2.8.7.0 to Stock android (.87 - last update)/Stock recovery with relocked bootloader (like always) and the camera is still not working. I tried using different ifwi/dnx and tried to re-flash stock rom (ADB sideload) with formating cache/data. Camera is still not working.
I even tried to go back and flash 2.22.40.53 (KitKat 4.4.2). Still the same, camera not found.
Can someone help me? Do someone face the same issue?
u have to downgrade all the way back to KK, and then use this http://forum.xda-developers.com/android/general/asus-zenfone-5-root-ww-2-22-40-54-4-4-2-t3128704
I already did this, like mentioned. It didn't help at all.
Hi,
Before flashing your DNX/IFWI, you must downgrade your fastboot image to 2.21.40.30, this way:
Download the fastboot from 2.21.40.30 image
Flash it
Code:
fastboot flash fastboot fastboot-2.21.40.30.img
fastboot reboot-bootloader
Flash your DNX/IFWI
Thanks!
dgadelha said:
Hi,
Before flashing your DNX/IFWI, you must downgrade your fastboot image to 2.21.40.30, this way:
Download the fastboot from 2.21.40.30 image
Flash it
Code:
fastboot flash fastboot fastboot-2.21.40.30.img
fastboot reboot-bootloader
Flash your DNX/IFWI
Thanks!
Click to expand...
Click to collapse
Okay and then I can flash the newest fastboot then firmware right?
Masterfellow said:
Okay and then I can flash the newest fastboot then firmware right?
Click to expand...
Click to collapse
In that order,
fastboot from 2.21.40.30
dnx from latest version
ifwi from latest version
then you can do whatever you want after, like
boot from latest version
fastboot from latest version
dgadelha said:
In that order,
fastboot from 2.21.40.30
dnx from latest version
ifwi from latest version
then you can do whatever you want after, like
boot from latest version
fastboot from latest version
Click to expand...
Click to collapse
Alright, I'll get home and I'll try. Thanks for now.
dgadelha said:
In that order,
fastboot from 2.21.40.30
dnx from latest version
ifwi from latest version
then you can do whatever you want after, like
boot from latest version
fastboot from latest version
Click to expand...
Click to collapse
Oh my gosh it really works! Wow... I didn't expect that... Thank you so much man! Now install/update those 40apps again
Masterfellow said:
Oh my gosh it really works! Wow... I didn't expect that... Thank you so much man! Now install/update those 40apps again
Click to expand...
Click to collapse
Glad it helped! Thanks.
Related
Hi all,
on my Nexus 9, update to LRX21Q failed: After reboot, the android icon was shown with "error" below.
I suppose, update failed as my system is rooted with the method Chainfire posted in the development forum.
After an additional reboot, the previous firmware is still shown. The system does not offer the update anymore but claims to be up-to-date.
Any hints? Thanks in advance.
Maybe it's the modified kernel from Chainfire. Try to get back to the stock kernel and try again.
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
I got the same error from OTA with no root. Only had 9 for 2 days, got OTA rite out of box no issue.
Yesterday for new build i get little error android icon upon reboot/install.
Obviously, something that is being changed by the "root" process is being checked DURING the update process. Probably a checksum on the boot partition. If it doesn't match, it bails on the update.
The likely reason for this is they acknowledge that you don't want to lose your root.
All it means is that you need to do the update manually.
It may be possible for a modified recovery to bypass this check, or possibly even be made to auto-root new boot images.
Thanks, guys. Will try as suggest above and post results.
Update: worked perfectly, needed to root again though.
StuMcBill said:
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
Click to expand...
Click to collapse
has anyone tried this? i would like to update without losing data...
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
mk92595 said:
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
Click to expand...
Click to collapse
What's the fastboot command for the img? Do you flash as boot, system, etc?
zeebone said:
What's the fastboot command for the img? Do you flash as boot, system, etc?
Click to expand...
Click to collapse
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
mk92595 said:
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
Click to expand...
Click to collapse
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
pantmunu said:
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
Click to expand...
Click to collapse
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
mk92595 said:
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
Click to expand...
Click to collapse
Thank you sir .
Where can i find the images for download. Thx
Google for nexus factory image.
Sent from my Nexus 9 using XDA Premium HD app
Update failed on me too. Completely stock
UPDATE:
Apparently *some* devices didn't get the recovery updated with the last update (LRX21L).
The new update (LRX21Q) requires the newer version of the recovery to install.
Google really messed up the launch of the Nexus 9 with all the HW/SW quality control issues
Serious f#ck-up from Google really
Interesting thing I noticed: I restored factory images manually in order to unroot and the OTA was no longer available. I verified I was still running on L. I manually installed the update and it went in just fine.
Now waiting on the root package to be updated for the Q kernel. You can re-root but you will be running on the L kernel, not the Q kernel.
maarten08 said:
Update failed on me too. Completely stock
Click to expand...
Click to collapse
My too fck Google
Mine failed and Im not even rooted
And im not sure if it did the update as its not showing a new one. Im on L
Hi guys
I forget to do a nandroid backup accidentally before test a build of cm12.1 that i make, the problem now installation stuck at 90%, and no progress after that, many tries on internal and external sdcard and with 2 different firmware, (perhaps was for dual sim verison) any solution for that before bring to assistance?
P.S: each day did new progress for cm12.1, hope to got booted rom.
Can't you flash the B052 version with Fastboot?
https://mega.nz/#!lEcGQZCC!X2fmOZ-ShY-Kx-9lwnSUN16Vo52_aU0i4K1KmdBW64Q
Normally you will then be on stock boot, recovery and system images.
olrak said:
Can't you flash the B052 version with Fastboot?
https://mega.nz/#!lEcGQZCC!X2fmOZ-ShY-Kx-9lwnSUN16Vo52_aU0i4K1KmdBW64Q
Normally you will then be on stock boot, recovery and system images.
Click to expand...
Click to collapse
Yes fastboot is working, will report if work, with the following order?
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
???
services in italy are really slow like one month for a stupid reparation.
No, all the commands are normally in a FLASH-ALL.bat file (yeah windows )
Commands are:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash cust cust.img
mfastboot flash system system.img
olrak said:
No, all the commands are normally in a FLASH-ALL.bat file (yeah windows )
Commands are:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash cust cust.img
mfastboot flash system system.img
Click to expand...
Click to collapse
alright, so should use mfastboot instead of fastboot?
Problem solved, thanx a lot :good::good::good::good::good:
hows your progress on that cm12.1 build that youre workin on?
ruben parra said:
hows your progress on that cm12.1 build that youre workin on?
Click to expand...
Click to collapse
i got progress on boot.img, we have hope
haky 86 said:
i got progress on boot.img, we have hope
Click to expand...
Click to collapse
Good luck man , I hope we get a custom rom soon
AmINoS007 said:
Good luck man , I hope we get a custom rom soon
Click to expand...
Click to collapse
I almost finish a cm-12.1 and doesn't boot due to blobs issue and still cannot copy them to the build :/
Probs
Hi everyone
What can I do to upgrade from b052 (after flash with fastboot ) because this Rom cause too much problems to my Huawei p8 lite so if you have a link for download an upgrade to replace B052
Then
haky 86 said:
Problem solved, thanx a lot :good::good::good::good::good:
Click to expand...
Click to collapse
Then did you uptade you're android system?is it possible to install new firmware from B052
hi guys/girls
android TV shield 2015 16 GB model.
well it is long been while.. i gave up with 5.1 i want to more upgrades. but it was already old problem. i ignored it.
but i want to upgrade right now =/
i did installed via ADB
i remember i did type
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot -w
fastboot flash recovery recovery.img
fastboot reboot
any someone have idea how to fix those?
thx you
Any someone else have idea about this how to fixed? thank you a lot.
you didnt flash the blobs needed for it
Code:
fastboot flash staging blob
Adromir said:
you didnt flash the blobs needed for it
Code:
fastboot flash staging blob
Click to expand...
Click to collapse
what does flash staging blob? ya it seems i didn't add those
I assume that is the updated bootloader. Id flash it as first and then flash all the other things
Adromir said:
I assume that is the updated bootloader. Id flash it as first and then flash all the other things
Click to expand...
Click to collapse
tsorry late reply, thx you a lot. it works perfect now
Glad I could help
Hello, good day. I just wanted to ask, (Im using custom rom now and my old backup is nowhere to be found) If I am going to flash my device to official stock rom, like if I flashed the older version (lets say the MM) can I still update my device today (up to nougat) through OTA update?
i think huawei cloud is the site where we download OTA updates from but I think is already dead.
(sorry if my poiint is confusing, I just really don't know how to explain it clearly)
emmanueldlauron said:
Hello, good day. I just wanted to ask, (Im using custom rom now and my old backup is nowhere to be found) If I am going to flash my device to official stock rom, like if I flashed the older version (lets say the MM) can I still update my device today (up to nougat) through OTA update?
i think huawei cloud is the site where we download OTA updates from but I think is already dead.
(sorry if my poiint is confusing, I just really don't know how to explain it clearly)
Click to expand...
Click to collapse
Hi,
in fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
and post results.
thanks for resonding
(bootloader) :Elite ROM v7.7
(bootloader) HUAWEI VNS-L31
vendorcountry: hw/spcseas
FAILED (remote: 'invalid command')
emmanueldlauron said:
thanks for resonding
(bootloader) :Elite ROM v7.7
(bootloader) HUAWEI VNS-L31
vendorcountry: hw/spcseas
FAILED (remote: 'invalid command')
Click to expand...
Click to collapse
Okay, last question - single SIM or dual SIM?
Dual Sim
emmanueldlauron said:
flash my device to official stock rom
Click to expand...
Click to collapse
So if I not mistaken, your build number is VNS-L31C185 EMUI 5 (correct me if I'm wrong).
Firmware finder and Huawei old server are down, so download service ROM.
IMO now you have two possibilities:
A) flash Service ROM using dload method, guide can be found in ReleaseDoc folder. The process will erase all your data and lock the BL again!
B)
- from downloaded ROM extract BOOT.img
RECOVERY.img
SYSTEM.img
CUST.img via 'Huawei update extractor' , follow Guide
(Note: CUST.img on Nougat can be found in the second archive)
- In fastboot mode flash extracted partitions using commands
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
- fastboot reboot
- Factory reset in stock recovery
-Alf- said:
So if I not mistaken, your build number is VNS-L31C185 EMUI 5 (correct me if I'm wrong).
Firmware finder and Huawei old server are down, so download Service ROM
IMO now you have two possibilities:
A) flash Service ROM using dload method, guide can be found in ReleaseDoc folder. The process will erase all your data and lock the BL again!
B)
- from downloaded ROM extract BOOT.img
RECOVERY.img
SYSTEM.img
CUST.img via 'Huawei update extractor' , follow Guide
(Note: CUST.img on Nougat can be found in the second archive)
- In fastboot mode flash extracted partitions using commands
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
- fastboot reboot
- Factory reset in stock recovery
Click to expand...
Click to collapse
I don't have sd card on me right now. is there any way I can flash service rom without sd card?
Edit: and also this device is C636xxx.
neverming the first paragraph I said. I'm confused with CUST.img thing, I donwloaded the C635 update but there's no second archive on what I had downloaded
emmanueldlauron said:
flash service rom without sd card?
Click to expand...
Click to collapse
Nope.
emmanueldlauron said:
this device is C636xxx.
Click to expand...
Click to collapse
Okay, then download C636
-Alf- said:
Nope.
Okay, then download C636
Click to expand...
Click to collapse
Thanks for the tips and ideas, I somehow understand something new today.
emmanueldlauron said:
there's no second archive on what I had downloaded
Click to expand...
Click to collapse
VNS-L31_hw_xxxxx
-Alf- said:
VNS-L31_hw_meafnaf
Click to expand...
Click to collapse
Oh yeah. I just figured it out but had to rename that to update.app so update extractor can accept the file. Thanks by the way.
for now SYSTEM and CUST takes time to finish extracting.
-Alf- said:
So if I not mistaken, your build number is VNS-L31C185 EMUI 5 (correct me if I'm wrong).
Firmware finder and Huawei old server are down, so download service ROM.
IMO now you have two possibilities:
A) flash Service ROM using dload method, guide can be found in ReleaseDoc folder. The process will erase all your data and lock the BL again!
B)
- from downloaded ROM extract BOOT.img
RECOVERY.img
SYSTEM.img
CUST.img via 'Huawei update extractor' , follow Guide
(Note: CUST.img on Nougat can be found in the second archive)
- In fastboot mode flash extracted partitions using commands
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
- fastboot reboot
- Factory reset in stock recovery
Click to expand...
Click to collapse
UPDATE: I did the B. they're all finished without any errors, but I ended with bootloop, like I can't go to recovery and when I tried to it vibrates twice and show nothing but just the huawei logo with "powered by android" texts.
emmanueldlauron said:
UPDATE: I did the B. they're all finished without any errors, but I ended with bootloop, like I can't go to recovery and when I tried to it vibrates twice and show nothing but just the huawei logo with "powered by android" texts.
Click to expand...
Click to collapse
Try command
fastboot erase userdata
and reboot.
Check your current build number etc.
https://forum.xda-developers.com/t/stock-rom-to-update-in-2021.4320501/post-85489493
-Alf- said:
Try command
fastboot erase userdata
and reboot.
Check your current build number etc.
https://forum.xda-developers.com/t/stock-rom-to-update-in-2021.4320501/post-85489493
Click to expand...
Click to collapse
emmanueldlauron said:
(bootloader) :Elite ROM v7.7
(bootloader) HUAWEI VNS-L31
vendorcountry: hw/spcseas
FAILED (remote: 'invalid command')
Click to expand...
Click to collapse
still the same with these
emmanueldlauron said:
still the same with these
Click to expand...
Click to collapse
Bro try this way out...
Download and install TWRP (if possible) and let me know
Upd.: nevermind, I forgot you don't have an sd card,.
Upd.2.: without SD you can try to flash Service ROM (or B361 firmware) using TWRP and sideload method. Unfortunately, sideload is Greek to me , so google it.
-Alf- said:
Bro try this way out...
Download and install TWRP (if possible) and let me know
Upd.: nevermind, I forgot you don't have an sd card,.
Upd.2.: without SD you can try to flash Service ROM (or B361 firmware) using TWRP and sideload method. Unfortunately, sideload is Greek to me , so google it.
B361 firmware is a fullOTA-MF-PV version, download and instructions here
Click to expand...
Click to collapse
I can still go fastboot mode and install everything without any errors but I don't why, it confuses me that let say I just flashed recovery (custom or stock) but when I'm going to access it (volume up + power button) phone just vibrates twice but nothing will happen.
emmanueldlauron said:
I can still go fastboot mode and install everything without any errors but I don't why, it confuses me that let say I just flashed recovery (custom or stock) but when I'm going to access it (volume up + power button) phone just vibrates twice but nothing will happen.
Click to expand...
Click to collapse
Flash TWRP over eRecovery, run command
fastboot flash recovery2 twrp.img
fastboot reboot
when a yellow warning appears on the screen, pres and hold Vol Up for 3 sec.
Edit: maybe your data partition is formatted with f2fs (after installing Elite ROM) , it should be ext4. I'm out of ideas bro, sorry.
-Alf- said:
Flash TWRP over eRecovery, run command
fastboot flash recovery2 twrp.img
fastboot reboot
when a yellow warning appears on the screen, pres and hold Vol Up for 3 sec.
Edit: maybe your data partition is formatted with f2fs (after installing Elite ROM) , it should be ext4. I'm out of ideas bro, sorry.
Click to expand...
Click to collapse
No problem. I think I hard bricked my phone, I just got boot logo and fastboot but I can't find any fix or solution or anything to do with this.
Flashing recovery or recovery2 finished w/o any errors but I can't boot to recovery.
Thanks for your help by the way. I appreciate it! Kudos and have a nice day. Keep safe.
emmanueldlauron said:
I think I hard bricked my phone,
Click to expand...
Click to collapse
IMO you only need an SD card and flash the Service ROM.
Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
LinhBT said:
Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
Click to expand...
Click to collapse
Can you share your file?
Rootk1t said:
Can you share your file?
Click to expand...
Click to collapse
Sure man, find attachment
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
houstontaxi said:
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
Click to expand...
Click to collapse
unpack your firmware, extract stock recovery.img and flash it.
But for flashing do I need to unlock bootloader or it can be done without unlocking?
houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Rootk1t said:
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Click to expand...
Click to collapse
If it needs to flash recovery the same way as we do for custom roms like fastboot flash recovery in platform tools then i tried that doesn't work to make it work bootloader needs to be unlocked I did that(unlocked the boot loader) then flashed stock recovery and it worked but after locking the boot loader with fastboot oem lock same issue happened again couldn't boot into recovery.
houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
LinhBT said:
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
Click to expand...
Click to collapse
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
houstontaxi said:
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
Click to expand...
Click to collapse
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
I'm gonna try that thanks for the help and I hope it resolves my issue with OOS A12 recovery as I don't face this kind of issue on OOS11
1
LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
lenox30 said:
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
Click to expand...
Click to collapse
This is simply Stock Recovery with ADB enabled bro. It only can help u in some tasks which need to access adb via Recovery, it won't help to decrypt ur device and/or have any functions as other custom recovery