Is there any other way to flash the Zenfone 2 than through recovery?
I received a CN version with WW software. It wasn't possible to flash to the latest WW because got build.prop error (Sku is CN error).
So I succesfully flashed to latest CN version. But the CN version has no Play store.
But now I can't flash back to WW because it's on the CN version now.
I hope you're following what I'm saying.
Is there some alternative flashing method where you can force the flash? I tried changing build.prop to CN Sku, but of course this ruined the signing.
What a mess.
damian5000 said:
Is there any other way to flash the Zenfone 2 than through recovery?
I received a CN version with WW software. It wasn't possible to flash to the latest WW because got build.prop error (Sku is CN error).
So I succesfully flashed to latest CN version. But the CN version has no Play store.
But now I can't flash back to WW because it's on the CN version now.
I hope you're following what I'm saying.
Is there some alternative flashing method where you can force the flash? I tried changing build.prop to CN Sku, but of course this ruined the signing.
What a mess.
Click to expand...
Click to collapse
What version of ROM are you on now? post screenshot .
smartbuddy said:
What version of ROM are you on now? post screenshot .
Click to expand...
Click to collapse
Thanks for your help smartbuddy.
I'm now on this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When it originally came, it came with: LRX21V.WW-ASUS_Z00A-2.13.40.13_20150401_8390_user......... But wouldn't offer up any OTA and couldn't flash newest WW because of CN Sku build.prop error. So upgraded to latest CN, but now stuck without any Google apps and some apps spouting CN even when switched to English. Ugh.
damian5000 said:
Thanks for your help smartbuddy.
I'm now on this
When it originally came, it came with: LRX21V.WW-ASUS_Z00A-2.13.40.13_20150401_8390_user......... But wouldn't offer up any OTA and couldn't flash newest WW because of CN Sku build.prop error. So upgraded to latest CN, but now stuck without any Google apps and some apps spouting CN even when switched to English. Ugh.
Click to expand...
Click to collapse
1) Download recovery image file (https://app.box.com/s/ohk0aki3nfxjqyuygbl629612tfmi6d9)
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash recovery by using command : fastboot flash recovery recovery.img
4) reboot to fastboot again
5) launch recovery from fastboot
6) Flash the latest WW firmware same way u flashed latest CN firmware
7) wipe cache
8) reboot
smartbuddy said:
1) Download recovery image file (https://app.box.com/s/ohk0aki3nfxjqyuygbl629612tfmi6d9)
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash recovery by using command : fastboot flash recovery recovery.img
4) reboot to fastboot again
5) launch recovery from fastboot
6) Flash the latest WW firmware same way u flashed latest CN firmware
7) wipe cache
8) reboot
Click to expand...
Click to collapse
Okay. Thank you. This has gotten me one step further. I'm now getting this error:
Can't install this package (Wed Apr 15 00:42:20 CST 2015) oer newer build (Thu Apr 16 14:55:02 CST 2015).
E:Error in /sdcard/MOFD_SDUPDATE.ZIP
(Status 7)
This is the correct ROM, I've checked build.prop: ro.build.version.incremental=WW_Z00A-WW_2.14.40.19_20150415_9660_user_rel-user-20150415
Indeed the date is older than what's on there currently. Even though Asus site says this was released on 4.27.
Any way to get around this? Or need to wait for some newer ROM to be released?
damian5000 said:
Okay. Thank you. This has gotten me one step further. I'm now getting this error:
Can't install this package (Wed Apr 15 00:42:20 CST 2015) oer newer build (Thu Apr 16 14:55:02 CST 2015).
E:Error in /sdcard/MOFD_SDUPDATE.ZIP
(Status 7)
This is the correct ROM, I've checked build.prop: ro.build.version.incremental=WW_Z00A-WW_2.14.40.19_20150415_9660_user_rel-user-20150415
Indeed the date is older than what's on there currently. Even though Asus site says this was released on 4.27.
Any way to get around this? Or need to wait for some newer ROM to be released?
Click to expand...
Click to collapse
Not sure if this would surely work but try the latest zip OTA update for WW Rom (2.15.40.10) from this thread : http://forum.xda-developers.com/zenfone2/orig-development/ota-links-stock-rom-t3093999
smartbuddy said:
Not sure if this would surely work but try the latest zip OTA update for WW Rom (2.15.40.10) from this thread : http://forum.xda-developers.com/zenfone2/orig-development/ota-links-stock-rom-t3093999
Click to expand...
Click to collapse
Okay. Will try. I'm not optimistic though. I'm on a totally different ROM than what this package is for. This is updated the same way as a full ROM?
Any other ideas am appreciating them.
The thing that's screwing me is the kernel on CN ROM is from 16th April.
There's nothing like Odin or some such to flash via PC?
damian5000 said:
Okay. Will try. I'm not optimistic though. I'm on a totally different ROM than what this package is for. This is updated the same way as a full ROM?
Any other ideas am appreciating them.
The thing that's screwing me is the kernel on CN ROM is from 16th April.
There's nothing like Odin or some such to flash via PC?
Click to expand...
Click to collapse
Instead of flashing the Rom from SD Card , use PC / Laptop to flash the WW Rom and follow the steps mentioned for Method 1 from here:
http://www.asus-zenfone.com/2015/04/how-to-flash-asus-zenfone-2.html
Ignore previous post as its just OTA update not complete Rom, so wont work, you need to get WW Rom on ur phone first and then apply OTA.
smartbuddy said:
Instead of flashing the Rom from SD Card , use PC / Laptop to flash the WW Rom and follow the steps mentioned for Method 1 from here:
http://www.asus-zenfone.com/2015/04/how-to-flash-asus-zenfone-2.html
Ignore previous post as its just OTA update not complete Rom, so wont work, you need to get WW Rom on ur phone first and then apply OTA.
Click to expand...
Click to collapse
Got up to like 40%, then:
E: Failed to verify whole-file signature
E: Signature verification failed
Crap. Frustration beginning to kick in. Have lost 8 hours of my life already.
Okay. This time got through verification, but same error again regarding kernel date. Ugh. Guess will have to wait until Asus modifies the kernel? Or someone smarter than I creates a signed ROM with a newer kernel date.
damian5000 said:
Okay. This time got through verification, but same error again regarding kernel date. Ugh. Guess will have to wait until Asus modifies the kernel? Or someone smarter than I creates a signed ROM with a newer kernel date.
Click to expand...
Click to collapse
I can understand your frustration bro, try this last one :
Flash system.img directly like you flashed recovery.img :
1) Download system image file (http://www.mediafire.com/download/xfnbk12g2kdbxpb/Z00A_2.13.40.13_preroot_system.zip)
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash system by using command : fastboot flash system system.img
4) wipe cache
5) reboot
I hope this works... :good:
smartbuddy said:
I can understand your frustration bro, try this last one :
Flash system.img directly like you flashed recovery.img :
1) Download system image file (http://www.mediafire.com/download/xfnbk12g2kdbxpb/Z00A_2.13.40.13_preroot_system.zip)
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash system by using command : fastboot flash system system.img
4) wipe cache
5) reboot
I hope this works... :good:
Click to expand...
Click to collapse
Butter, homie.
All good with Play so far. Haven't tested the network. Guess this is a bit of a frankenstein ROM now? I see kernel still reading the same, can flash kernel over via fastboot as well?
I've had strange behavior since got the phone trying to get into fastboot. Tough to do from boot. So have had to mostly do it through adb reboot fastboot. Also, every time I go into recovery it tries to update automatically to MOFD_UPDATE.ZIP. Whether I have an SD card in or not, tries to do the update from this file. Not sure if this is normal behavior or not. What do you think? (there's no option to select Update from SD within menu). Annoying. Every time try to go into recovery. (has had this issue since before Fn with it).
Anyways, what's your PayPal, man? Will forward you a tenner.
damian5000 said:
Butter, homie.
All good with Play so far. Haven't tested the network. Guess this is a bit of a frankenstein ROM now? I see kernel still reading the same, can flash kernel over via fastboot as well?
I've had strange behavior since got the phone trying to get into fastboot. Tough to do from boot. So have had to mostly do it through adb reboot fastboot. Also, every time I go into recovery it tries to update automatically to MOFD_UPDATE.ZIP. Whether I have an SD card in or not, tries to do the update from this file. Not sure if this is normal behavior or not. What do you think? (there's no option to select Update from SD within menu). Annoying. Every time try to go into recovery. (has had this issue since before Fn with it).
Anyways, what's your PayPal, man? Will forward you a tenner.
Click to expand...
Click to collapse
Yes recovery is annoying for the phone. Glad that this worked. Now you can flash latest stock rom via adb, this will update everything, but u will loose Root.
Regarding Paypal, I am happy that I was able to help, Thanks.
smartbuddy said:
Yes recovery is annoying for the phone. Glad that this worked. Now you can flash latest stock rom via adb, this will update everything, but u will loose Root.
Regarding Paypal, I am happy that I was able to help, Thanks.
Click to expand...
Click to collapse
I noticed kernel still reading 16th, so I took a shot and flashed boot.img over from the 15th (latest full ROM from Asus).
I'm very curious if the adb flash update will go fully successfully, but I have a feeling it will. I think I'll stick with root for now though...I really need to change DPI on this. FHD on 5.5"@240 (looks thereabouts) is not going to cut it.
It looks like lots of updates coming out regularly. Guessing someone will put out a new rooted system.img fairly soon.
I insist on the tenner man. Please send me a PM. I have learned a lot through this.
damian5000 said:
I noticed kernel still reading 16th, so I took a shot and flashed boot.img over from the 15th (latest full ROM from Asus).
I'm very curious if the adb flash update will go fully successfully, but I have a feeling it will. I think I'll stick with root for now though...I really need to change DPI on this. FHD on 5.5"@240 (looks thereabouts) is not going to cut it.
It looks like lots of updates coming out regularly. Guessing someone will put out a new rooted system.img fairly soon.
I insist on the tenner man. Please send me a PM. I have learned a lot through this.
Click to expand...
Click to collapse
Follow this thread, OP has posted latest Rooted System.img, recovery etc :
http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
DO NOT UPDATE SuperSU and su binary
If you wish to then pls donate to charity bro, Thanks !
Great help Smartbuddy! Actually I'm hoping that similar steps would work on my Asus Memo Pad 7 ME572CL with JP sku, as I want to change it to WW sku and update to latest firmware. Do you happen to know where I can get the equivalent WW recovery and system img files for that device?
smartbuddy said:
1) Download recovery image file (https://app.box.com/s/ohk0aki3nfxjqyuygbl629612tfmi6d9)
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash recovery by using command : fastboot flash recovery recovery.img
4) reboot to fastboot again
5) launch recovery from fastboot
6) Flash the latest WW firmware same way u flashed latest CN firmware
7) wipe cache
8) reboot
Click to expand...
Click to collapse
Thank you Man! It solve my problem! I had "...cannot over new build .....
(Status 7)" this error while updating from 63 to 90 firmware. Find the solution for few hour through google but nothing found ,almost despair TT . Finally found this thread and saved my phone! Thank you so much! :good:
Btw, ASUS phone is so trouble to flash a rom ><
Related
Hello, friends!
It's been a really long time after my Q900 and X3D-SE...
For those who are having trouble with Asus Fonepad 7 2014 FE170CG in terms of softbrick, kindly take some time to read this thread.
I am currently on Latest Kitkat with version: 11.2.3.33
1.) In terms of Rooting(Offcourse YES, this tab is rootable) i rooted this device with Rootzenphone.apk(attached below). Kindly follow the tutorial here to root the device. When it doesn't get rooted in first time, repeat it. I got it rooted at 1st time itself. After rooting, i removed all the apps i don't need!
2.) To update your Fonepad, download the appropriate zip firmware(zip rom) from the Asus site. Download the matching SKU's only. For eg: WW-WW, CN-CN, JP-JP etc... And i really don't know about installing CN firmware over WW variants. After downloading, rename your file accordingly. Eg: UL-K012-WW-11.2.3.33-user.zip to k012_sdupdate.zip and put the file in the root of external SD card. Time to backup all your critical data! Finally switch off your tab. Now press Vol up + Power buttons until you see the Asus logo. If you are in Jelly Bean, the options are slightly different where you have to choose SD update. Your tab will now reboot to recovery, installs the update and reboots back to the installed firmware. On the other hand, if you are in KitKat, the options like SD download and SD update won't be available because they are removed from the newer Fastboot images. The SD update and SD download are now replaced by recovery option which is the one you need to select. After that device will reboot and install the updates.
3.) To downgrade the firmware to JellyBean, download the appropriate version of the firmware file(I used UpdateLauncher_K012_WW_10_32_1_33_1.zip) and follow the steps as above. Your device will be downgraded. In this version the options on the Droidboot menu will be different from the KitKat version. Just choose SD update to install any other updates.
4.) This is the main part for which i am creating this thread!
THE SOFT BRICK
I was pulling off my hairs for about a day trying to figure out the problem.
Reason for my softbrick: I got a feeling that my device was slightly going slow and the amount of available free RAM was only 200MB. SO, i was considering to Downgrade the firmware from Kitkat to Jellybean. I downloaded the Jellybean firmware UpdateLauncher_K012_WW_10_32_1_33_1.zip from the Asus site and installed it using the method above! Everything went fine and device booted to JellyBean with the familiar interface. Everything was fine but i noticed that the device was slightly heating up and was missing many features like dual apps etc... Hence i decided to go back to KitKat which is were all the problems began! I downloaded the latest firmware UL-K012-WW-11.2.3.33-user.zip. Installation begun as usual but at the end, installation was terminated with a message error. I was shocked! When i rebooted the device i got a USB icon with a red progress bar in a second and went away! The device neither booted nor charged! I repeatedly tried this procedure but failed continuously. I booted to the Droid Boot and saw the firmware version was fine and can't figure what the problem was! But i noticed that the same JellyBean firmware installed again without any glitches and booted fine. When i tried the Kitkat firmware, it failed again and device didnt't boot. This is tricky part! So, i downloaded the first kitkat firmware UL-K012-WW-11.2.3.18.2-user.zip after the JellyBean and tried to install it. To my suprise, the installation went fine and device booted up with that KitKat firmware. Now i put the latest Kitkat firmware UL-K012-WW-11.2.3.33-user.zip to the external SD card and tried to install it and it successfully installed :victory: :victory: Now i am back on the latest firmware
My recommendation : If you do anything, make sure to backup data and have knowledge on what you are doing. Thanks for reading this thread. Please press thanks if i helped you!
Lollipop update has been released some time ago. Please remember to unroot before you update or else you'll get soft bricked.
downgrade and ota update
In lillipop i got major laggs and baterry drained more than 50% over night in standby mode.
So I downgrade to latest kitkat WW_V11.2.3.33 from asus site, using fastboot and intel temporary cwm recovery.
It works great but now ifwi is 64.33 from lollipop, not 64.25 from kitkat.
It seems there is an OTA update WW_V11.2.3.34 but I dont get notification for download.
Is there any way to downgrade ifwi version?
Or do I have to ask here someone for capture the WW_V11.2.3.34 OTA update from /cache and upload here?
Or is there any fix for lillipop horrible lag (2-3 secs after presing or swiping) and masive battery drain? I tried factory reset lollipop and even reinstall with fastboot erase system and intel thetered temp cwm install UL-K012-WW-12.8.1.26-user.zip
b0by said:
In lillipop i got major laggs and baterry drained more than 50% over night in standby mode.
So I downgrade to latest kitkat WW_V11.2.3.33 from asus site, using fastboot and intel temporary cwm recovery.
It works great but now ifwi is 64.33 from lollipop, not 64.25 from kitkat.
It seems there is an OTA update WW_V11.2.3.34 but I dont get notification for download.
Is there any way to downgrade ifwi version?
Or do I have to ask here someone for capture the WW_V11.2.3.34 OTA update from /cache and upload here?
Or is there any fix for lillipop horrible lag (2-3 secs after presing or swiping) and masive battery drain? I tried factory reset lollipop and even reinstall with fastboot erase system and intel thetered temp cwm install UL-K012-WW-12.8.1.26-user.zip
Click to expand...
Click to collapse
For some reasons, i too didn't get that update! I am also in 11.2.3.33 I flashed the device 4 times just to get this update but didn't!
b0by said:
In lillipop i got major laggs and baterry drained more than 50% over night in standby mode.
So I downgrade to latest kitkat WW_V11.2.3.33 from asus site, using fastboot and intel temporary cwm recovery.
It works great but now ifwi is 64.33 from lollipop, not 64.25 from kitkat.
It seems there is an OTA update WW_V11.2.3.34 but I dont get notification for download.
Is there any way to downgrade ifwi version?
Or do I have to ask here someone for capture the WW_V11.2.3.34 OTA update from /cache and upload here?
Or is there any fix for lillipop horrible lag (2-3 secs after presing or swiping) and masive battery drain? I tried factory reset lollipop and even reinstall with fastboot erase system and intel thetered temp cwm install UL-K012-WW-12.8.1.26-user.zip
Click to expand...
Click to collapse
Hello! Ifwi is easy! Take the KitKat Firmware and unzip it complitely, so that you have acces to the files of the rom.zip (Firmware)! In the Firmware (1st-Site) is a ifwi.zip! Unzip this ifwi.zip, and take the dnx_fwr.bin (VLC) and the ifwi.bin (VLC) file, and copy it to your adb/fastboot binarys! Then go to fastboot-mode and First: fastboot flash dnx dnx_fwr.bin, when its done, Second: fastboot flash ifwi ifwi.bin, when its done, reboot bootloader, and check ifwi-version! Should be the version you have flashed!
But do it in your own! Im not responsebile for failure or brick!
Bluetooth permission to receive apk
hi
i cant underestand English very well but i have question
i have asus fonepad 7 fe 170 cg kitkat and i rooted this but i cant receive .apk with Bluetooth for this reason i installed xposed and i downloaded Bluetooth ToolKit.apk
whit this program my bluetooth have permission to receive apk but i want to know what file chenged in root divice and in permission that my bluetooth can receive apk
please say me what file chenged???????
Are you getting play store links when you send an .apk file or can't receive files at all??? And i never installed xposed since it has no use for me....
roselanguste said:
Hello! Ifwi is easy! Take the KitKat Firmware and unzip it complitely, so that you have acces to the files of the rom.zip (Firmware)! In the Firmware (1st-Site) is a ifwi.zip! Unzip this ifwi.zip, and take the dnx_fwr.bin (VLC) and the ifwi.bin (VLC) file, and copy it to your adb/fastboot binarys! Then go to fastboot-mode and First: fastboot flash dnx dnx_fwr.bin, when its done, Second: fastboot flash ifwi ifwi.bin, when its done, reboot bootloader, and check ifwi-version! Should be the version you have flashed!
But do it in your own! Im not responsebile for failure or brick!
Click to expand...
Click to collapse
I have 4 .bin files in ifwi.zip:
CLVp_CSAX_FWR_DnX_20.3E.bin
CLVp_CSAX_OS_DnX_20.3E.bin
IFWI_v64.25_CSAX_PROD.bin
signed_CLVP_CSAX_SoftFuseFile.bin
Dont I have to flash them all? or just the ...FWR_DnX.bin and IFWI_v64.24....bin?
My dear friends, please concentrate on getting Clockworkmod and Cyanogenmod... I am trying real hard here. I contacted all the devs i could, none willing to help me! No device & vendor tree, Locked bootloader, No custom recovery, No stable ROM...... Really feeling so down
OK! You have Four ifwi-Files, Yes then Flash them All!
Expecting some help over here!!! Support me for creating device and vendor trees........
Downgrade IFWI version!
roselanguste said:
Hello! Ifwi is easy! Take the KitKat Firmware and unzip it complitely, so that you have acces to the files of the rom.zip (Firmware)! In the Firmware (1st-Site) is a ifwi.zip! Unzip this ifwi.zip, and take the dnx_fwr.bin (VLC) and the ifwi.bin (VLC) file, and copy it to your adb/fastboot binarys! Then go to fastboot-mode and First: fastboot flash dnx dnx_fwr.bin, when its done, Second: fastboot flash ifwi ifwi.bin, when its done, reboot bootloader, and check ifwi-version! Should be the version you have flashed!
But do it in your own! Im not responsebile for failure or brick!
Click to expand...
Click to collapse
Hello, i tried to downgrade IFWI version by following your method... Everything flashed successfully but the version number stays the same! For eg. if i flash version 64.25, it still stays the 64.33 version of Lollipop firmware only!!! Do you know why???
irfanjunaid said:
Hello, i tried to downgrade IFWI version by following your method... Everything flashed successfully but the version number stays the same! For eg. if i flash version 64.25, it still stays the 64.33 version of Lollipop firmware only!!! Do you know why???
Click to expand...
Click to collapse
Hello! Have you more than this two files in your ifwi.zip? In many cases there are more files in ifwi.zip! Unzip the ifwi.zip and flash all files what is in there! Token.files=fastboot flash token filename, dnx.files=fastboot flash dnx filename, and ifwi.files=fastboot flash ifwi filename! But i suggest you, when you not need this ifwi/dnx for anything, then you should stay on the newer ifwi?! ifwi is BIOS for Intel Phones! So you have KitKat with the newer BIOS-update from Lollipop! Its like a BIOS-update for PC!
Ever since i flashed that Lollipop 64.33 IFWI, i didn't get access to the 11.2.3.34 update at all! So, do you think this IFWI version is problem or Asus pulled that firmware from its servers???
@irfanjunaid , Hello sir.
I just got Asus model: k012 Stuck on logo.
Now i am downloading all the firmwares u mentioned in the OP, but one question .. Did u flash them via stock recovery or u flashed the temporary cwm recovery available .
Sobaro said:
@irfanjunaid , Hello sir.
I just got Asus model: k012 Stuck on logo.
Now i am downloading all the firmwares u mentioned in the OP, but one question .. Did u flash them via stock recovery or u flashed the temporary cwm recovery available .
Click to expand...
Click to collapse
Always flash Stock ROM via stock recovery.... I did via stock recovery... But don't forget, rename the downloaded zip file to k012_sdupdate.zip and put it into a clean formatted SD card. Now press volume up + Power button until you see Asus logo. Now choose Recovery. Now your tab boots to recovery, installs firmware and reboots itself.... Note: No downgrade possible, cannot change SKU(WW-CN etc.....)
I get stuck at the Asus Logo after intel splash.... with a spinning wheel that keeps on going and going and going.... I have download the files you mentioned above, put them on SD card but cannot boot into droidboot, it goes back to main screen. When I select Recovery, it runs about 5 seconds and gives error and then restarts. What seems to be the problem here?
Thanks!
Jabbacks said:
I get stuck at the Asus Logo after intel splash.... with a spinning wheel that keeps on going and going and going.... I have download the files you mentioned above, put them on SD card but cannot boot into droidboot, it goes back to main screen. When I select Recovery, it runs about 5 seconds and gives error and then restarts. What seems to be the problem here?
Thanks!
Click to expand...
Click to collapse
What version of firmware are you in now? Is it rooted? Did you try a factory reset? After factory reset allow tab to take some time to boot up... After that go developer settings -> turn ON usb debugging... Now in PC, run adb via commandline and run adb reboot bootloader... Now see if it goes to droidboot...
This is what I find in bootloader mode. Why can't it go in to droidboot?
IFWI Version: 64.25
SERIAL: E60KBC383526
DROIDBOOT VERSION: TW_FONEPAD-11.2.3.18.2-20141022
PRODUCT: K012
Following Firmwares:
UL-K012-WW-11.2.3.18.2-user.zip
UL-K012-WW-11.2.3.33-user.zip
I tried the old version but to no avail. Also the latest!
Thanks!
Jabbacks said:
This is what I find in bootloader mode. Why can't it go in to droidboot?
IFWI Version: 64.25
SERIAL: E60KBC383526
DROIDBOOT VERSION: TW_FONEPAD-11.2.3.18.2-20141022
PRODUCT: K012
Following Firmwares:
UL-K012-WW-11.2.3.18.2-user.zip
UL-K012-WW-11.2.3.33-user.zip
I tried the old version but to no avail. Also the latest!
Thanks!
Click to expand...
Click to collapse
This is the droidboot.... You can now connect your tab to PC and issue fastboot commands to it.... For example: Fastboot erase cache
But for heaven's sake please don't install lollipop update.....
Now try this: Fastboot erase cache
Fastboot erase userdata
Now choose reboot....
See if it boots up....
Hi,
I have the flickering screen problem with my phone and it is out of warranty so i can't send it back to repair.
I tried upgrading to the latest firmware, tried factory reset, wipe cache, installing google launcher, enabling the HW thing in developer mode and nothing worked.
I read that WW_2.12.40.11 version doesn't have the screen problem and i want to try it, but i wanna be sure i'm doing it the right way.
1) I read that i can't just put the wanted firmware in my phone and install the update but i must also flash the matching recovery to flash the wanted version - is it true?
2) Can i downgrade straight from my version to the lower one because i think the other way around, i need to have higher version for upgrading to the higher version i now have.
3) Where can i find the adb driver for this?
Thanks
You can downgrade via ext sd card using the downgrade version from asus > 52.20.40.196 LP which when installed , reboots to 2.20.40.196LP
When putting WW-UL- 52.20.40.196.zip.zip ,make sure to put an extra .zip on the end in file manager or in sd from pc first and reboot.
If you then put WW-UL-2.12.40.11-user.zip.zip (extra .zip) on sd or in file manager . You might get that to give you notification after a reboot too. Although i have not tested to downgrade that far .
You must use the first 52.20 blah blah fw to initially downgrade first though. Ignore this and you are liable to brick. Here >
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-52.20.40.196-user.zip
See my downgrade via ext sd video and thread , familiarise yourself with the process first !
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
Any questions , just ask
timbernot said:
You can downgrade via ext sd card using the downgrade version from asus > 52.20.40.196 LP which when installed , reboots to 2.20.40.196LP
When putting WW-UL- 52.20.40.196.zip.zip ,make sure to put an extra .zip on the end in file manager or in sd from pc first and reboot.
If you then put WW-UL-2.12.40.11-user.zip.zip (extra .zip) on sd or in file manager . You might get that to give you notification after a reboot too. Although i have not tested to downgrade that far .
You must use the first 52.20 blah blah fw to initially downgrade first though. Ignore this and you are liable to brick. Here >
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-52.20.40.196-user.zip
See my downgrade via ext sd video and thread , familiarise yourself with the process first !
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
Any questions , just ask
Click to expand...
Click to collapse
Thanks alot
Just a question before i try your method: I already installed 2.12.40.11 recovery.img into the phone. can i still use your method or should i first flash 4.21.40.223 recovery.img back to the phone?
gifnooky said:
Thanks alot
Just a question before i try your method: I already installed 2.12.40.11 recovery.img into the phone. can i still use your method or should i first flash 4.21.40.223 recovery.img back to the phone?
Click to expand...
Click to collapse
OK, it's weird, i did flash the 2.12.40.11 recovery.img to the phone using adb and it was said in the console that the process completed, but now when i enter recovery mode it still shows me 4.21.40.223 version.
OK, I did downgrade with your method and it works great, but when i try to downgrade fro that version to the version i want to try i get error that i cant install the package over the existing newer version.
Just to inform.
gifnooky said:
OK, I did downgrade with your method and it works great, but when i try to downgrade fro that version to the version i want to try i get error that i cant install the package over the existing newer version.
Just to inform.
Click to expand...
Click to collapse
If you want to downgrade to such an old version, find the .raw file of that version (search here on XDA) and flash it via Asus Flash Tool.
JBolho said:
If you want to downgrade to such an old version, find the .raw file of that version (search here on XDA) and flash it via Asus Flash Tool.
Click to expand...
Click to collapse
Thanks for the advice.
I searched and found raw firmware versions but no the one i'm looking for.
Is there any way i can install the official firmware i have? i also found recovery.img, boot.img, droidboot.img of the version i want.
gifnooky said:
Thanks for the advice.
I searched and found raw firmware versions but no the one i'm looking for.
Is there any way i can install the official firmware i have? i also found recovery.img, boot.img, droidboot.img of the version i want.
Click to expand...
Click to collapse
If you have all the img partitions you can always try installing via fastboot commands but i really recommend using a raw with Asus Flash Tool...
Hai friend try flash 3 file of boot.img recovery.img and droidboot.img version 40.11.. and then flash rom with adb sideload.. its work for me... and solve my prob flicker display..
Sent from my ASUS_Z00AD using Tapatalk
savve said:
Hai friend try flash 3 file of boot.img recovery.img and droidboot.img version 40.11.. and then flash rom with adb sideload.. its work for me... and solve my prob flicker display..
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Hi, thanks i'l try that.
does it matter in what order i flash this 3 files?
Edit: If i already flashed the ROM can i just flash the boot.img and droidboot.img or do i need to do the whole process including flashing the ROM again?
Is your screen flickering problem like this: https://www.youtube.com/watch?v=kRuxTefNcKw
If its like that I was told its a LCD hardware problem which gets fixed by replacing LCD.
Update:
Well, I installed firmware 2.12.40.11 and it worked fine for several days but then the screen started to flicker again.
i started to update the devices with OTA updates and then i saw that in firmware WW_2.20.40.174 the screen didn't flicker.
i had further updates and then the screen started to flicker again.
i tried to flash recovery.img, boot.img and droidboot.img but not the device only enters fastboot mode but when i try to enter normal boot or recovery mode, it only comes back to fast boot mode.
any suggestion what should i do to unbrick the phone?
Thanks
After the last OTA update, my Moto G5 started to boot with the following warning:
"
Your device has failed verification and may not work properly.
To learn more visit:
motorolacom/unlockbootloader
ID: N/A
Your device will boot in 5 seconds
"
It also started to restart randomly.
I did some research on the web and found out that this warning appears when someone unlocks/roots the device.
The problem is that I aver never unlocked the bootloader or rooted the device.
When I boot to fastboot it says "OEM Locked" and the app DevCheck says that I am not rooted.
It seems to me that the update corrupted something and now some piece of software flags my device as unlocked.
Besides the irritating screen, some apps are not working properly or cannot be downloaded from the store.
I tried to reset to factory settings and wipe caches. Problem still happens.
I'd like to know if you guys know a solution for this problem.
I saw on another post that this problem was happening on some Verizon Moto Zs and they provided a software to reinstall the rom
Unfortunately, Motorola has not released a software to do the same to unlocked devices.
My ROM version is: NPPS25.137-33-6 (yeah, there is an "S" that I don't find in the roms available here)
The baseband is: M8937_8000.122.02.45R
(CEDRIC_BRAZILDSDS_CUST)
I was thinking in loading the rom into internal memory, reboot in recovery mode and flash the rom using the option "Install package from zip".
Do you know if it would work without an unlocked bootloader. Is it safe?
Thank you for the help,
Don't know if you can flash the boot logo without an unlocked bootloader but if you can here it is
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files (Google to learn howto install Android sdk) & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
If you can't then you have no option but to wait for Motorola to fix it if you really haven't modded your phone
TheFixItMan, I really appreciate your answer.
But in that case wouldn't I just be changing the warning screen?
The problems with Netflix and other apps would remain.
I need something to fix the cause of the problem.
Have you guys heard about that problem before?
This guy had the same problem, but verizon patched it:
https://community.verizonwireless.com/thread/921991
hoferbr said:
TheFixItMan, I really appreciate your answer.
But in that case wouldn't I just be changing the warning screen?
The problems with Netflix and other apps would remain.
I need something to fix the cause of the problem.
Have you guys heard about that problem before?
This guy had the same problem, but verizon patched it:
/QUOTE]
I have the same problem as you. Could you fix it?
Thank you,
Luciano
Click to expand...
Click to collapse
You can go back to stock using ADB update or by flashing VERIFIED images in bootloader mode. This will work even when bootloader is locked.
p8tgames said:
You can go back to stock using ADB update or by flashing VERIFIED images in bootloader mode. This will work even when bootloader is locked.
Click to expand...
Click to collapse
To flash using bootloader I need just to copy the .zip in the internal memory, reboot in reboot in bootloader mode and select the option "install from .zip file"?
Where do I find the verified image for my device?
If I flash an unverified image will my device brick ou the bootloader will present a "impossible to procede" screen?
Thank you for the help!
hoferbr said:
To flash using bootloader I need just to copy the .zip in the internal memory, reboot in reboot in bootloader mode and select the option "install from .zip file"?
Where do I find the verified image for my device?
If I flash an unverified image will my device brick ou the bootloader will present a "impossible to procede" screen?
Thank you for the help!
Click to expand...
Click to collapse
you can flash what ever you want in fastboot -
However - In terms of firmware, if you are trying to flash incorrect firmware then the verification check will fail and it will not flash
Just don't flash a new bootloader if you are worried about it - its not needed unless you are upgrading an android version and that version has an updated bootloader
So I am safe if I follow these steps:
Manually Update Android Nougat for Moto G5 (NPP25.137-33) via Recovery
First of all, Go to Settings –> About Phone –> Tap on Build Number 7 Times.
Go to Developer Options –> Enable USB Debugging.
Save Stock Android Nougat rom for Moto G5 and save it in Internal storage.
Reboot Moto G5 Plus to Recovery Mode.
Select Apply Update from SD Card.
Select the Downloaded ZIP file from SD Card.
Wait until Installation process Completes.
Once the Installation completed. Reboot the Phone.
If my ROM is a wrong version, will the bootloader detect and deny instalation?
hoferbr said:
So I am safe if I follow these steps:
Manually Update Android Nougat for Moto G5 (NPP25.137-33) via Recovery
First of all, Go to Settings –> About Phone –> Tap on Build Number 7 Times.
Go to Developer Options –> Enable USB Debugging.
Save Stock Android Nougat rom for Moto G5 and save it in Internal storage.
Reboot Moto G5 Plus to Recovery Mode.
Select Apply Update from SD Card.
Select the Downloaded ZIP file from SD Card.
Wait until Installation process Completes.
Once the Installation completed. Reboot the Phone.
If my ROM is a wrong version, will the bootloader detect and deny instalation?
Click to expand...
Click to collapse
if you are talking about an official ota update then it will fail - you cannot update like this
An offical ota zip requires a non rooted device, unmodified system partition and stock recovery
you maybe able to download the ota update and save it (its in the cache partition)
then use flashfire app to install it
note if its a custom rom than recovery mode will allow you to flash any zip and will flash anything unless the updater script specifies a certain build.prop target eg phone model or other criteria that would stop it flashing if it was false
If you want to flash firmware you need the firmware image and flash it via fastboot
TheFixItMan said:
if you are talking about an official ota update then it will fail - you cannot update like this
An offical ota zip requires a non rooted device, unmodified system partition and stock recovery
you maybe able to download the ota update and save it (its in the cache partition)
then use flashfire app to install it
note if its a custom rom than recovery mode will allow you to flash any zip and will flash anything unless the updater script specifies a certain build.prop target eg phone model or other criteria that would stop it flashing if it was false
If you want to flash firmware you need the firmware image and flash it via fastboot
Click to expand...
Click to collapse
I have the same problem, but I unlock the booloader after with the intention to relock when flashing a stock rom.
But every stock rom I have downloaded when flashing with mfastboot shows a version security downgrade error and cannot reflash stock rom.
My bootloader is B8.23.
Any help appreciatte.
jdonadel said:
I have the same problem, but I unlock the booloader after with the intention to relock when flashing a stock rom.
But every stock rom I have downloaded when flashing with mfastboot shows a version security downgrade error and cannot reflash stock rom.
My bootloader is B8.23.
Any help appreciatte.
Click to expand...
Click to collapse
You need firmware that matches or exceeds your current firmware version - you cannot flash a lower firmware version
TheFixItMan said:
You need firmware that matches or exceeds your current firmware version - you cannot flash a lower firmware version
Click to expand...
Click to collapse
Yeah, I see that, but looking into the stock rom .zip file I cannot find the correct ID that matches to my. But since I posted the reply, I´ve downloaded from a mirror in lolinet, and correct flash my phone.
I had trouble updating my Honor 6X (BLN-L21) after I rooted it, so I searched the whole xda to gain some information. Finally I made it, so I thought I could share this information with you guys, hope it helps, but I do not take responsibility if not, as you may have already heard, the Honor 6X (like every Kirin device) is very easy to brick.
- If everything is gone alright you should keep all of your data, apps and settings.
- If there is a big update, like from MM to N you maybe should backup all your stuff and relock the bootloader to update (big updates can relock frp so you can't unlock your bootloader then a rollback is the only way.
Successfully tried from:
B360 to B365
B365 to B367
Short Version (for expert users):
1. uninstall busybox bynaries and the Xposed Framework
2. uninstall magisk (inside the app)
3. flash stock recovery.img (of your actual firmware)
4. flash stock boot.img (of your actual firmware)
5. make OTA update (Reminder: safe update file)
6. flash twrp again and root
7. you are all done
Detailed Version:
#cmd commands#
1. backup your system over TWRP #adb reboot recovery# and do a backup there (for safety reasons)
2. #fastboot reboot#
3. uninstall busybox bynaries and the Xposed Framework(not just the app) (if you have it)
4. uninstall magisk (in app over "complete Uninstall button")
5. restart to bootloader #adb reboot bootloader#
6. flash stock recovery #fastboot flash recovery recovery.img# [use the recovery out of your actual firmware, how to extract is explained in the Forum I added at the end
7. flash stock boot #fastboot flash boot boot.img# [also use the extracted version of your actual package]
8. #fastboot reboot#
9. download update over OTA Update app (System update) in stock system. -> If the "System updater" app does not provide a Full version of the update package, the update could get stopped at 8% saying it could not verify the update, if so, just take the step to the error and reboot, if you then search for an update again, the "System updater" should now show you a Full version of the update package. like "BLN-L21C432B365-FULL"
10. you should safe that update files out of the HwOUC folder, so you can extract the recovery.img and boot.img later before you restart your device to do the update, because the system deletes these files after successful update
11. update over OTA Update app (System update) in stock system
12. restart to bootloader (#adb restart bootloader#)
13. flash twrp again #fastboot flash recovery twrp-3.1.1-0-berlin.img# [use the OpenKirin twrp edition (the official leads to a bootloop] -> [url]https://forum.xda-developers.com/honor-6x/development/twrp-t3583413[/URL]
14. Important is not to boot to system after flashing TWRP, exactly like as you installed it the first time. So you do #fastboot reboot# and then Vol down + lock
15. backup your system over TWRP (for safety reasons)
16. #adb reboot recovery#
17. flash Magisk zip in TWRP again
18. reboot in twrp
19. you are ready to go with the latest stock rom
How to extract boot.img and recovery.img out of your actual firmware is explained here:
[url]https://forum.xda-developers.com/honor-6x/how-to/extract-stock-recovery-img-boot-img-img-t3676880[/URL] thanks @Khan ubaid
citizenserious said:
the Honor 6X is very easy to brick.
Click to expand...
Click to collapse
Not just the 6X but every Kirin device.
This work only with packages like "xxxB360-FULL" or even with smaller downloaded packages that just updates some files? And, if I choose to do this with the FULL package do i have to re modify all the settings that i use actually?
RedSkull23 said:
This work only with packages like "xxxB360-FULL" or even with smaller downloaded packages that just updates some files? And, if I choose to do this with the FULL package do i have to re modify all the settings that i use actually?
Click to expand...
Click to collapse
I already tried it with the FULL package (edited the Guide btw.) you keep all your settings and stuff like before.
If it doesn't show you the FULL package just try the update until it fails, the system than will show you a FULL version of the update after the restart and research. That worked for me so far.
Hope I could help
citizenserious said:
I already tried it with the FULL package (edited the Guide btw.) you keep all your settings and stuff like before.
If it doesn't show you the FULL package just try the update until it fails, the system than will show you a FULL version of the update after the restart and research. That worked for me so far.
Hope I could help
Click to expand...
Click to collapse
What a nice notice, thanks dude! I already own the FULL, i only was worried about the fact that i could lose my data with the FULL one, i waa seeing it a clean firmware install but after this i can go straight with the update. I'll do that later today
RedSkull23 said:
What a nice notice, thanks dude! I already own the FULL, i only was worried about the fact that i could lose my data with the FULL one, i waa seeing it a clean firmware install but after this i can go straight with the update. I'll do that later today
Click to expand...
Click to collapse
I have done it that way yesterday, from B365 to B367 with the FULL package.
But nevertheless please back up your data.
edit: please let us know if it worked for you too
Thank for this guide. I might use this when an update comes.
[email protected] said:
Click to expand...
Click to collapse
What's the matter?
citizenserious said:
I have done it that way yesterday, from B365 to B367 with the FULL package.
But nevertheless please back up your data.
edit: please let us know if it worked for you too
Click to expand...
Click to collapse
Finally i found some time to dedicate on updating my phone, and I'm happy to say that it worked. I made from B360 to B365 and from B365 to B367, both worked at first shot. The only thing that i just can't understand is why the OTA package downloaded yesterday worked immediately, while the same B365-FULL package downloaded a month ago, copied on PC before starting it and later started didn't. With stock recovery and boot images obviously. I tried to start it later but nothing, i tried dload method with the update.app but neither that worked. Probably the OTA downloaded creates a sort of signature that can't be recreated that easily, if the same package fails through dload method... But what matters most is that now I'm on B367, protected with the latest security patch. Sorry for the late answer, time is hard to find... Thanks
Hi
Can someone upload the boot.img and and recovery.img from B367
Thanks in advance
Archerous said:
Hi
Can someone upload the boot.img and and recovery.img from B367
Thanks in advance
Click to expand...
Click to collapse
B367 of which model BLN-LXXCXXX?
shashank1320 said:
B367 of which model BLN-LXXCXXX?
Click to expand...
Click to collapse
I forgot sorry
BLN-L21C432B367
Archerous said:
I forgot sorry
BLN-L21C432B367
Click to expand...
Click to collapse
Check repository thread. Redskull23 has updated there. You may find in OP also in that thread. Link to the thread in my signature
shashank1320 said:
Check repository thread. Redskull23 has updated there. You may find in OP also in that thread. Link to the thread in my signature
Click to expand...
Click to collapse
There is no B367 in the Repository,no boot.img or recovery. thanks for you help
I wait for the next update,and i will not forget to save the update.app to pc. And extract the files
Archerous said:
There is no B367 in the Repository,no boot.img or recovery. thanks for you help
I wait for the next update,and i will not forget to save the update.app to pc. And extract the files
Click to expand...
Click to collapse
@RedSkull23, please see bro. You have updated to this and may be able to share :good:
shashank1320 said:
@RedSkull23, please see bro. You have updated to this and may be able to share :good:
Click to expand...
Click to collapse
I share ist,with the next update :good:
shashank1320 said:
@RedSkull23, please see bro. You have updated to this and may be able to share :good:
Click to expand...
Click to collapse
If we find the B367 package I'll upload everything from it!
I was on rooted BLN-L24C5678B360, and I want to take the OTA 365, so I flashed stock recovery and boot, reboot into system and started the update, but it failed, afterwards the phone stuck at booting up screen.
I have to boot into fastboot and run "fastboot oem relock [my unlock code]" to relock it, then followed by a factory reset. But when it comes to update, it failed again. Upon reboot, it stuck again with the message "Your device has failed verification and may not work properly."
What did I do wrong?
Update: recovered with the official rollback software to 6.0.
shadowcliffs said:
I was on rooted BLN-L24C5678B360, and I want to take the OTA 365, so I flashed stock recovery and boot, reboot into system and started the update, but it failed, afterwards the phone stuck at booting up screen.
I have to boot into fastboot and run "fastboot oem relock [my unlock code]" to relock it, then followed by a factory reset. But when it comes to update, it failed again. Upon reboot, it stuck again with the message "Your device has failed verification and may not work properly."
What did I do wrong?
Click to expand...
Click to collapse
You can try full firmware for b365 if available via dload.
Unlock your bootloader and it will boot to twrp and then boot normally.
My phone has unlocked bootloader, TWRP, and is rooted with magisk. Got the OTA for (global) 9.5.4.0 last night - it downloads/de-crypts ok, reboots into TWRP, and then fails to flash. I also tried to flash manually via TWRP by locating the downloaded file, still fails. During the night, it rebooted itself (to try again I suppose), and my alarm didn't go off.
So here I am, late in work, wasting more "work time" to ask you for a possible solution :angel:
Go back to original miui recovery then you can update your miui successfully. After update,reflash twrp and magisk.
jimandy60 said:
Go back to original miui recovery then you can update your miui successfully. After update,reflash twrp and magisk.
Click to expand...
Click to collapse
Sounds easy, but I don't know how to do that. Could you point me in the right direction?
you can't flash an OTA with TWRP
Flash recovery img with fastboot
Code:
fastboot flash recovery recovery.img
then boot your phone
settings->about phone->system update->update
it will get in origin miui recovery and update system automatically
after update finished,reflash twrp and magisk
Thank you very much @jimandy60
With all the respect though, I would prefer downloading the file from a popular location. Is there any way to find this hosted somewhere else, maybe by Xiaomi?
ang3l said:
Thank you very much @jimandy60
With all the respect though, I would prefer downloading the file from a popular location. Is there any way to find this hosted somewhere else, maybe by Xiaomi?
Click to expand...
Click to collapse
maybe try this site?
en.miui.com
Hello!
I got the same problem but instead to come here and ask for help I tried to solve myself. I downloaded the lastest TWRP version and the device was not going into recovering mode. Then I installed again the previous one without results. I downloaded the TWRP app from Play Store and trying to solve I made wipe data, cache and I am not sure but I think also choose wipe system. Now my phone is stuck on the fastboot screen. Does not start. Using ADB I installed back the stck recovery but the problem remains. Somebody can help me please?
reflash the full rom?
download&unzip full rom package,get in fastboot mode and run flash_all.bat
Check out my guide here:
https://forum.xda-developers.com/mi-mix-2/how-to/guide-mi-mix-2-unroot-restore-recovery-t3770690
It has all the steps and files you will need to go from rooted stock MIUI Nougat to rooted stock MIUI Oreo applying the OTA update
colorado_al said:
Check out my guide here:
https://forum.xda-developers.com/mi-mix-2/how-to/guide-mi-mix-2-unroot-restore-recovery-t3770690
It has all the steps and files you will need to go from rooted stock MIUI Nougat to rooted stock MIUI Oreo applying the OTA update
Click to expand...
Click to collapse
Thanks, I'll take a look.