SOLVED HERE
Hey guys, first post, but I'm kinda stuck right now.
My phone:
*** Software Status: Modified ***
*** Relocked ***
A5-UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.101.111011.20.0123
OpenDSP-v27.2.2.00546.0311
OS-
eMMC-boot 1536MB
Aug 7 2015,14:02:57.0
Okay, I tried flashing a custom ROM (InsertCoin A5_CHL & UL) and it installed properly, without any issues. But after rebooting it wouldn't connect to my Google Account. It just keeps checking and checking.. and after a good five minutes it states that vDM client ist shut down.
So, I followed this guide and tried going back to Stock RUU, but every time I enter the fastboot command
Code:
adb reboot fastboot
my phone just restarts, it won't enter fastboot mode.
I already tried to enter manually [Bootloader -> Fastboot] and the command
Code:
fastboot flash zip 0P9CIMG.zip
is working. It's sending the zip file to my phone, but every time it starts to write the actual file I get an error message.
Code:
C:\ADB>fastboot flash zip 0P9CIMG.zip
sending 'zip' (1033121 KB)...
OKAY [ 46.667s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 122.015s
So, my question..
How can I get back to Stock RUU? Is there any other way to make it happen?
You will need to flash stock recovery, and relock bootloader, then just place 0P9CIMG.zip on SD card, and HBoot will pick it up and install on its own
topher2632 said:
You will need to flash stock recovery, and relock bootloader, then just place 0P9CIMG.zip on SD card, and HBoot will pick it up and install on its own
Click to expand...
Click to collapse
Just tried. Flashed Stock recovery and relocked Bootloader. HBoot attempts to flash, but after checking the zip file an error comes up.
Code:
Hboot Version is older!
Update Fail!
Device halted due to Large Image Update fail.
Press >>Power<< to reboot.
StockRUU is
0P9CIMG_A5_UL_L50_DESIRE_SENSE60_MR_HTC_Europe_2.34.401.2_Radio_1.101.111011.20.0123_10.28.4149A.00L_release_449710_combined_signed.zip
renamed to 0P9CIMG.zip.
_______________________________________
Edit: After downloading two other RUUs, all named like the one mentioned above, the third one finally worked.
For other guys who want to do a downgrade...:
A5ul, single sim, europe android kk
http://forum.xda-developers.com/desire-816/general/0p9cimga5ulk44desiresense60htceurope1-t2946515
nukaru said:
Just tried. Flashed Stock recovery and relocked Bootloader. HBoot attempts to flash, but after checking the zip file an error comes up.
Code:
Hboot Version is older!
Update Fail!
Device halted due to Large Image Update fail.
Press >>Power<< to reboot.
StockRUU is
0P9CIMG_A5_UL_L50_DESIRE_SENSE60_MR_HTC_Europe_2.34.401.2_Radio_1.101.111011.20.0123_10.28.4149A.00L_release_449710_combined_signed.zip
renamed to 0P9CIMG.zip.
_______________________________________
Edit: After downloading two other RUUs, all named like the one mentioned above, the third one finally worked.
Click to expand...
Click to collapse
Could you please share the link ?
Thanks!
mtk31 said:
Could you please share the link ?
Thanks!
Click to expand...
Click to collapse
You can use mine which i posted if you have a5_ul
TobiBot said:
You can use mine which i posted if you have a5_ul
Click to expand...
Click to collapse
I tried it but i got older version error, thanks
nukaru said:
Just tried. Flashed Stock recovery and relocked Bootloader. HBoot attempts to flash, but after checking the zip file an error comes up.
Code:
Hboot Version is older!
Update Fail!
Device halted due to Large Image Update fail.
Press >>Power<< to reboot.
StockRUU is
0P9CIMG_A5_UL_L50_DESIRE_SENSE60_MR_HTC_Europe_2.34.401.2_Radio_1.101.111011.20.0123_10.28.4149A.00L_release_449710_combined_signed.zip
renamed to 0P9CIMG.zip.
_______________________________________
Edit: After downloading two other RUUs, all named like the one mentioned above, the third one finally worked.
Click to expand...
Click to collapse
Enviado desde mi HTC Desire 816 mediante Tapatalk
mtk31 said:
I tried it but i got older version error, thanks
Enviado desde mi HTC Desire 816 mediante Tapatalk
Click to expand...
Click to collapse
Which hboot version do you have? It should work with 3.xxx
mtk31 said:
Could you please share the link ?
Thanks!
Click to expand...
Click to collapse
I'm uploading the file I used, once I'll get back home, I'll write you a pm.
TobiBot said:
Which hboot version do you have? It should work with 3.xxx
Click to expand...
Click to collapse
3.19.xxx
Enviado desde mi HTC Desire 816 mediante Tapatalk
---------- Post added at 11:19 AM ---------- Previous post was at 11:18 AM ----------
nukaru said:
I'm uploading the file I used, once I'll get back home, I'll write you a pm.
Click to expand...
Click to collapse
Ty!
Enviado desde mi HTC Desire 816 mediante Tapatalk
Okay, if you have got hboot 3.19.xxx i dont know why it doesnt work..
If he/she's got the same specs I did, Kit Kat downgrade won't work. He/She needs the lollipop RUU to flash. Radio and OS need to be identical to the previous specs.
[Guide] How to flash 0P9CIMG on HTC Desire 816 [A5_UL]
Okay, since I was having a hard time flashing these files the first time, here's a guide how it worked for me.
First of all, if you need to flash the recovery too (eg. black screen in recovery, bootloop), make sure USB-Debugging is enabled on your device, all drivers are up-to-date (HTC Sync, Java and fastboot) and your bootloader is unlocked.
If it's still locked/relocked visit the HTC Developer Center and follow the guide to unlock your bootloader.
- Create a folder 'ADB' in disc drive C and copy all files into this folder, this way you can just copy/paste the commands.
My ADB fastboot folder (just extract it to C:\ and you're good to go)
- Connect your device and PC using usb data cable
Step 1
Flashing recovery (before relocking your bootloader)
- Download recovery.img
- Save it to C:\ADB folder
- Navigate to ADB folder and click on any free space while holding the shift Key
- Choose 'Open command window' here
- Once cmd is started use this command
Code:
fastboot devices
and check if your device is listed, then type
Code:
adb reboot fastboot
to reboot your device. It should start in fastboot mode. If it's not, shut down your phone and restart using power + volume down buttons, pressed at the same time. Once Hboot starts just navigate (using volume up or volume down buttons on your device) to Fastboot and press the power button. Make sure FASTBOOT USB is display under your specs.
- Enter
Code:
fastboot flash recovery recovery.img
into the cmd window and press enter to flash your recovery.
- If it's successful go to step 2, if it's not try again.
Step 2
Relock Bootloader using Fastboot:
Now you need to relock the bootloader, otherwise the Stock RUU can't be installed.
- Copy command to the cmd window
Code:
fastboot oem lock
- Press enter
Your device should now be relocked.
{
"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"
}
Step 3.a
Flashing Stock RUU using fastboot commands
- Download 0P9CIMG.zip
- Place it in ADB folder
- now type the following command in the cmd window
Code:
fastboot flash zip 0P9CIMG.zip
- Wait for the flashing process to finish.
If that doesn't work try to install the RUU using Hboot.
Step 3.b
Flashing Stock RUU using HBOOT
- Save 0P9CIMG.zip to the root folder of an sd-card (min. 2GB )
- Put sd-card into your device
- Start the device by pushing Power + Vol Down at the same time
- At this point, your device should pick the 0P9CIMG.zip you downloaded up and install it as an update.
- Wait till the flashing process is finished. (Might take some time )
Now, you're back to Stock Android Lollipop 5.0.2
If this fails and you're still unable to get back to Stock Android, follow the next guide:
Restore system using clean twrp Android 5.0.1 nandroid backup
Make sure your device battery is charged upto 80%.
Make sure your bootloader is unlocked and usb debugging is activated
- Download twrp for your device (HTC Desire 816 a5 )
- Follow the guide Fastboot Install Method (No Root Required) to flash custom recovery
- Download TWRP Nandroid backup
- Boot to bootloader (volume down + power), use volume buttons to navigate to Fastboot and then select recovery
- Once twrp is running, tab the Wipe button, followed by Advanced Wipe
- Select Dalvik Cache, System, Cache and Internal Storage
- Swipe to confirm, wait till it's finished
- Unzip A5_UL TWRP Nandroid 2016-01-25--03-37-20 UNROOTED.zip file to desktop
!!! IMPORTANT !!!
You will need to insert your device ID into the folder structure otherwise the folder won't be listed.
To get your device ID, start cmd in your adb folder and enter adb devices. The number/letter combination is your device id. (eg. SH45...)
Browse through the TWRP folder until you get to fastboot_getvar (bootloader) serialno and replace the text with your serialno.
- Move TWRP folder to sd-card
- Connect device to pc
- Insert sd-card into device
- Tab Restore button
- Choose nandroid backup folder
- Swipe on screen to confirm restore
There’s no going back once you do this. All your data will be lost, so make sure you've got your own data backup and placed it somewhere safe!
After this you will have a functional factory reset device.
nukaru said:
If he/she's got the same specs I did, Kit Kat downgrade won't work. He/She needs the lollipop RUU to flash. Radio and OS need to be identical to the previous specs.
Click to expand...
Click to collapse
I can´t downgrade then. Thanks anyway
The only way (as far as I know) to downgrade to kit kat is to turn your device s-off. But that's the riskiest procedure, since you'll unable all security options. If you'll use a wrong RUU, flashing gets aborted or another error pops up, the device WILL be hard-bricked.
Updated guide.
TWRP nandroid backup in progress.
mtk31 said:
I can´t downgrade then. Thanks anyway
Click to expand...
Click to collapse
theres ROM SVHD ROM with Kitkat using twrp u can flash that rom its kitkat . I also tried flash the kitkat RUU its not worked but I used the kitkat svhd ROM its fine
aselasanjeewab said:
theres ROM SVHD ROM with Kitkat using twrp u can flash that rom its kitkat . I also tried flash the kitkat RUU its not worked but I used the kitkat svhd ROM its fine
Click to expand...
Click to collapse
Great news, ty!
Do you have a5ul patch? Link is not working
yes I got I can upload it in the evening im at office now when I back home I will upload and share the link to u
mtk31 said:
Great news, ty!
Do you have a5ul patch? Link is not working
Click to expand...
Click to collapse
A5_ul patch from here.
Related
In this tutorial, I will show you how to downgrade Any HBOOT and Radio to "around" HBOOT 1.03.001 and Radio 7.48.36.1 or less with S-ON. How amazing is that!
Disclaimer: I am not responsible for any damage that you bring to your android device! This will Downgrade you to Android 2.3.3!
1. Download these files:
*http://www.filefactory.com/f/7b4aa0a541dcf00f/
-look for your RUU for your Carrier for example I downloaded "RUU_Marvel_TMOUS_1.62.531.3_Radio_47.10f.35.3032"
*http://forum.xda-developers.com/showthread.php?t=1530864
-Bootloader Controler, thank you theq86
*http://www.mediafire.com/?m546mkk0yp7cbdb
-Boot.img that we are gonna flash
*http://www.mediafire.com/?5lf77c7sposqkck
-System.img we are also gonna flash
*http://www.mediafire.com/?4o2dbgqbb2t30lh
-Extact it and place in your "C:/" drive
1a. Flash CWM Recovery or some other compatible recovery on your wildfire s
2.After theses files above have been downloaded, connect your wfs to computer via USB drive
3. open cmd and open up the folder you extracted in "C:/" drive Ex: cd c:/Android
4.Place boot.img and system.img in the root of the android folder
5. execute these commands
fastboot flash system system.img
fastboot flash boot boot.img
"its gonna take time so wait by looking at the bootlader screen at the top right"
IMPORTANT: After reboot it ill try to load Android Recovery but it cant since it has CWM Recovery, so it will load cwm recovery and say "E: Invalid command arguement" so all you have to do is reboot
after completed reboot, the rom is going to be buggy and gltchy so dont freak out YET
6. Place the bootloader Controller tool to the root of SD Card, DO NOT UNZIP!
7.Go into bootloader and enter your recovery, if your using cwm go to install zip from sd card>choose zip from sd card> look for the bl tool and flash it.
8.While attempting to flash it, there will be a Visual UI that popped up like a window, go to "Superversion" and press on that with your soft keys or Volume/Power Keys.
9. After Superversion update has completed reboot back into recovery and reattempt to install the bl tool, this time press on "LOCK" and wait for it to complete update and power down.
10.Open bootloader and you wil see "LOCKED OOW" at the top in hboot 1.08.0099 or "LOCKED" in hboot 1.09.0099, we are half way there
11. Now normal reboot to android and enable USB debugging if you havent done so.
12. Launch the RUU you downloaded and wait for it to complete the starting process. When completed starting up, accept all the notifications and continue to the update. Dont freak out when it keeps rebooting, its normal Wait for the update to complete then you quet done!
13. It will reboot and will show you the factory reset of android 2.3.3. After completing that you can now enter bootloader and see that you have downgrade like this for example:
{
"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"
}
i used to be on hboot 1.08.0099
You are now Downgraded to Android 2.3.3 and Downgraded HBOOT + Radio with S-ON
Big thanks to, couldnt done it without you:
theq86 for the nice bl controller tool
Football for the RUU's
MrTaco505 for the .img files and tutorial
When I attempt the commands I get:
sending 'system' (248075 KB)...
OKAY [ 29.814s]
writing 'system'...
FAILED (remote: not allowed)
finished. total time: 29.815s
Click to expand...
Click to collapse
kalaker said:
When I attempt the commands I get:
Click to expand...
Click to collapse
What is your hboot version and use bootloader needs to be unlocked
Also it needs to be extracted
Sent from my HTC Wildfire S using xda premium
If unable to flash .ing via fastboot try flashing from recovery
No , this may help you , before flashing system or the other thing , type in the cmd
fastboot oem rebootRUU
Click to expand...
Click to collapse
This will allow flashing hboot or system on unlocked bootloader and some on locked ...
maybe you have something wrong in this , because when I try rebooting to system after flashing system and boot , it sends me to CWM and says down
E: Invalid command arguement
Click to expand...
Click to collapse
seaskyways said:
maybe you have something wrong in this , because when I try rebooting to system after flashing system and boot , it sends me to CWM and says down
Click to expand...
Click to collapse
Yea that happens but power off then power on
my hboot is unlocked it is 1.09.0099 and still S-ON wat to doo now? wen i load recovery file it say cid errorr and update failed
it wont boot to the rom after flashing system and boot and keeps sending me to recovery nevermind got it to work thank for the post it seems to be that i had to wait a couple of minutes after flashing the system and boot and take the battery off and put it back it then i was able to boot to the rom and did the rest of the steps. Next time i'll create a backup before flashing a new custom rom
i want to know from hboot 1.08.0099 downgrade to hboot 1.03.0000 or 0.90.0000?
because PG76DIAG.nbh is not work on hboot 1.08.0099,can't s-off,only htc unlock,
can't network unlock
nasiaaasss said:
i want to know from hboot 1.08.0099 downgrade to hboot 1.03.0000 or 0.90.0000?
because PG76DIAG.nbh is not work on hboot 1.08.0099,can't s-off,only htc unlock,
can't network unlock
Click to expand...
Click to collapse
Yes this works any hboot but to downgrade, the hboot must be an unlockable version 1.08.0099 or 1.09.0099 that is unlocked.
From the image in the tutorial, I downgraded from hboot 1.08.0099 to 1.03.0001.
The PG76DIAG.nbh for s-off only works for cdma version of the wfs
it is workiiing, thanks
johnyfly1 said:
it is workiiing, thanks
Click to expand...
Click to collapse
Your welcome
Next time hit the thanks button
ou sorry, I am new here
I hit a tanks button right now
Downgrade
Will phone be able to receive and instal OTA updates after this? Just curious...
cyclonus00210 said:
Will phone be able to receive and instal OTA updates after this? Just curious...
Click to expand...
Click to collapse
Yes, its just a downgraded wfs that wants to upgrade again.
will try it
davidang said:
will try it
Click to expand...
Click to collapse
Ok
i cannot get through.. the phone is not booting into the bootloader.. it gets stucked at htc logo.. with "!" on all corners..
please suggest me something..
sameer.patil291 said:
i cannot get through.. the phone is not booting into the bootloader.. it gets stucked at htc logo.. with "!" on all corners..
please suggest me something..
Click to expand...
Click to collapse
The update failed, and could have almost hard bricked your phone. Rerun the ruu in recovery and if it fails again, use the recovery option in the ruu
Sent from my HTC Wildfire S using xda premium
Hello,
I purchased HTC Desire 816 on eBay and unfortunately i received a Taiwan imported mobile.
When i try to update the phone it downloads the update and asks to install it now or later and when i click install now it reboots
and shows a green line for 20% of the full line and then i get a red exclamation mark. I have to restart it by holding power+volume up
buttons.
Can anyone help me out so that i can upgrade the software, i live in India.
I also did a factory reset from recovery mode but didn't resolve the issue and everything was in Chinese language after the reset.
Thanks.
Known69 said:
Hello,
I purchased HTC Desire 816 on eBay and unfortunately i received a Taiwan imported mobile.
When i try to update the phone it downloads the update and asks to install it now or later and when i click install now it reboots
and shows a green line for 20% of the full line and then i get a red exclamation mark. I have to restart it by holding power+volume up
buttons.
Can anyone help me out so that i can upgrade the software, i live in India.
I also did a factory reset from recovery mode but didn't resolve the issue and everything was in Chinese language after the reset.
Thanks.
Click to expand...
Click to collapse
@Known69 is your device currently rooted or do you have an unlocked bootloader? If so, root needs to be removed via the SuperSU app which will remove all root files and then going into the bootloader and typing
fastboot oem lock
Now you can try to update.
If your device is completely stock on the other hand it could be an issue with the update not downloading correctly. I will try to locate the RUU for your device so you can use it to restore to complete stock but could you provide me with the bootloader version of your device? Also you said you performed a factory reset and it didn't fix the issue, does that mean that you attempted to download the update once again and it failed at the same part in the process?
Sent from my 710C using XDA Free mobile app
@Known69,
I too received a Taiwan imported model. But my seller was so kind that he helped me to update the ROM to latest HTC sense 6. when I received the device, it was running sense 5.5 and rooted. Due to this the new update wouldn't install. After I installed the ROM, root is now removed and I can update when HTC releases further updates.
jaysoblitzed said:
@Known69 is your device currently rooted or do you have an unlocked bootloader? If so, root needs to be removed via the SuperSU app which will remove all root files and then going into the bootloader and typing
fastboot oem lock
Now you can try to update.
If your device is completely stock on the other hand it could be an issue with the update not downloading correctly. I will try to locate the RUU for your device so you can use it to restore to complete stock but could you provide me with the bootloader version of your device? Also you said you performed a factory reset and it didn't fix the issue, does that mean that you attempted to download the update once again and it failed at the same part in the process?
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
No sir, it isn't rooted.
HBOOT-3.18.0.0000
Yes after the factory reset from the menu(Vol Down+Power) it completely changed the language to Chinese.
Then i tried it again and the same problem remained unsolved.
Known69 said:
No sir, it isn't rooted.
HBOOT-3.18.0.0000
Yes after the factory reset from the menu(Vol Down+Power) it completely changed the language to Chinese.
Then i tried it again and the same problem remained unsolved.
Click to expand...
Click to collapse
This file below is the Stock RUU only for the HTC Desire 816W / A5_DUG !
@Known69 Based off of you stating it was an Desire 816W via msg.
https://www.dropbox.com/s/h32sc97xl...8.3230.00D_F_release_389233_signed_2.zip?dl=1
Download it and make a copy of it.
Now rename both copies.
-Name one 0P9CIMG.zip
-Name one 0PC9DIAG.zip
Not sure which name your device uses but its one of these so just test both starting with the first one or put two copies one of each on your device.
You'll know because when you put this on the phone and go back into the bootloader it will ask you to use Volume Key to confirm the update. (Check to make sure it says A5_dug at the top)
Do this and let it update & complete.
Once done you can start up and update if its available but I'm pretty sure this is the latest full stock update for your device.
If its in Chinese and you want it to be a different language simply skip past everything and go into settings.
Go to this icon -> [[[A] (Should be the 7th icon from the bottom.)
Now select the first option.
Choose your language.
Done!
(P.S. Now you can root if you'd like!)
jaysoblitzed said:
This file below is the Stock RUU only for the HTC Desire 816W / A5_DUG !
@Known69 Based off of you stating it was an Desire 816W via msg.
https://www.dropbox.com/s/h32sc97xl...8.3230.00D_F_release_389233_signed_2.zip?dl=1
Download it and make a copy of it.
Now rename both copies.
-Name one 0P9CIMG.zip
-Name one 0PC9DIAG.zip
Not sure which name your device uses but its one of these so just test both starting with the first one or put two copies one of each on your device.
You'll know because when you put this on the phone and go back into the bootloader it will ask you to use Volume Key to confirm the update. (Check to make sure it says A5_dug at the top)
Do this and let it update & complete.
Once done you can start up and update if its available but I'm pretty sure this is the latest full stock update for your device.
If its in Chinese and you want it to be a different language simply skip past everything and go into settings.
Go to this icon -> [[[A] (Should be the 7th icon from the bottom.)
Now select the first option.
Choose your language.
Done!
(P.S. Now you can root if you'd like!)
Click to expand...
Click to collapse
Thanks for you time sir.
I have sent you PM regarding further issue if any, otherwise.
jaysoblitzed said:
This file below is the Stock RUU only for the HTC Desire 816W / A5_DUG !
@Known69 Based off of you stating it was an Desire 816W via msg.
https://www.dropbox.com/s/h32sc97xl...8.3230.00D_F_release_389233_signed_2.zip?dl=1
Download it and make a copy of it.
Now rename both copies.
-Name one 0P9CIMG.zip
-Name one 0PC9DIAG.zip
Not sure which name your device uses but its one of these so just test both starting with the first one or put two copies one of each on your device.
You'll know because when you put this on the phone and go back into the bootloader it will ask you to use Volume Key to confirm the update. (Check to make sure it says A5_dug at the top)
Do this and let it update & complete.
Once done you can start up and update if its available but I'm pretty sure this is the latest full stock update for your device.
If its in Chinese and you want it to be a different language simply skip past everything and go into settings.
Go to this icon -> [[[A] (Should be the 7th icon from the bottom.)
Now select the first option.
Choose your language.
Done!
(P.S. Now you can root if you'd like!)
Click to expand...
Click to collapse
Just tried with your solution.
The steps which i followed are:
Downloaded and renamed to the first name which you gave(0P9CIMG.zip) and placed in SDcard.
Loaded bootloader-->FastBoot-->Checking SD... and got an error "No image or Wrong image".
Then renamed it to "0PC9DIAG.zip" and repeated the same procedure and still got the same error.
Verified it was A5_dug and in the fast line it was stating "LOCKED" in red color, don't know if it is normal for this procedure or need it Unlocked.
Known69 said:
Just tried with your solution.
The steps which i followed are:
Downloaded and renamed to the first name which you gave(0P9CIMG.zip) and placed in SDcard.
Loaded bootloader-->FastBoot-->Checking SD... and got an error "No image or Wrong image".
Then renamed it to "0PC9DIAG.zip" and repeated the same procedure and still got the same error.
Verified it was A5_dug and in the fast line it was stating "LOCKED" in red color, don't know if it is normal for this procedure or need it Unlocked.
Click to expand...
Click to collapse
Do you see the green text that goes on and off within 3-4 seconds? In that green text when you first enter the bootloader it has the correct name that the file needs to be named.
Once it's on the SD/internal storage you don't have to click fastboot for it to flash. It will automatically scan and detect the moment after you see the green text in hboot/ first screen of bootloader.
As an alternative, you could also just flash the .zip image with
fastboot flash zip "zipname"
So for future example it will be
fastboot flash zip 0PC9IMG.zip
(No quotes)
Also you can type fastboot getvar all
It will show all your device information for you to double check everything is correct.
Sent from my 710C using XDA Free mobile app
I tried but it's reading both the files.
In first line **DIAG..Wrong or no image, continues in second line too. In third line **IMG.zip...Wrong or no image, continues in 4th line too. Now comes back to main boot loader screen.
I didn't get your manual instruction.
Where should I write those commands and which file as by default both the files are selected as stated above.
Thanks.
Known69 said:
I tried but it's reading both the files.
In first line **DIAG..Wrong or no image, continues in second line too. In third line **IMG.zip...Wrong or no image, continues in 4th line too. Now comes back to main boot loader screen.
I didn't get your manual instruction.
Where should I write those commands and which file as by default both the files are selected as stated above.
Thanks.
Click to expand...
Click to collapse
Doesn't matter which file you use and you can use those commands via fastboot in the bootloader, not hboot. Basically when you go into the bootloader just press the power button once and you'll be in fastboot. Plug it into your PC and use the command I posted above with adb on your PC to flash either file.
Sent from my 710C using XDA Free mobile app
jaysoblitzed said:
Doesn't matter which file you use and you can use those commands via fastboot in the bootloader, not hboot. Basically when you go into the bootloader just press the power button once and you'll be in fastboot. Plug it into your PC and use the command I posted above with adb on your PC to flash either file.
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
I got the error.
{
"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"
}
Well when you enter the bootloader, the green text that comes up has the exact name that needs to be used for your device's RUU. I noticed that with the Virgin Mobile model it was 0P9CDIAG.zip
I also saw that some people stated their device says 0P9CIMG.zip
Your device zip name requirement could be different depending on the variant and you might have to reboot a few times to get the correct name written down correctly but it should be something along those lines provided above. Instead of IMG or DIAG it might say something else.
I also found the RUU for the Virgin Mobile model and I tested it but it only works when the device has the stock recovery and root permissions are removed.
When you remove all root from inside the SuperSU settings you HAVE to make sure to uninstall the app itself to ensure your device is completely stock. Use titanium backup if you have to.
After that I relocked my bootloader then the RUU flashed just by putting it on my SD card.
What I REALLY want to know is how your device has S-OFF.
Could you possibly make a CWM backup of your device and upload it? The boot.img would be really helpful with development of this device if S-OFF is achieved.
Sent from my 710C using XDA Free mobile app
jaysoblitzed said:
Well when you enter the bootloader, the green text that comes up has the exact name that needs to be used for your device's RUU. I noticed that with the Virgin Mobile model it was 0P9CDIAG.zip
I also saw that some people stated their device says 0P9CIMG.zip
Your device zip name requirement could be different depending on the variant and you might have to reboot a few times to get the correct name written down correctly but it should be something along those lines provided above. Instead of IMG or DIAG it might say something else.
I also found the RUU for the Virgin Mobile model and I tested it but it only works when the device has the stock recovery and root permissions are removed.
When you remove all root from inside the SuperSU settings you HAVE to make sure to uninstall the app itself to ensure your device is completely stock. Use titanium backup if you have to.
After that I relocked my bootloader then the RUU flashed just by putting it on my SD card.
What I REALLY want to know is how your device has S-OFF.
Could you possibly make a CWM backup of your device and upload it? The boot.img would be really helpful with development of this device if S-OFF is achieved.
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
Can you please help me achieving this "Could you possibly make a CWM backup of your device and upload it? The boot.img would be really helpful with development of this device if S-OFF is achieved."
Thanks.
Managed to take a screenshot of the error and the name.
http://puu.sh/cpSn2/3f0df7fc9c.jpg
Still failed.
Known69 said:
Managed to take a screenshot of the error and the name.
http://puu.sh/cpSn2/3f0df7fc9c.jpg
Still failed.
Click to expand...
Click to collapse
I will get the correct file for your device I noticed the CID and the S-OFF on your device. Is it possible to contact the source from where you obtained your device to ask them how they obtained those statuses?
Sent from my 710C using XDA Free mobile app
jaysoblitzed said:
I will get the correct file for your device I noticed the CID and the S-OFF on your device. Is it possible to contact the source from where you obtained your device to ask them how they obtained those statuses?
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
I bought it from eBay and seller don't want to disclose the information
But he told he imported from Taiwan. I am sure he has tweaked something, he's fraud.
Bro For solving this issue you need twrp installed on your device.
Then ask someone for your stock recovery image and a twrp backup.
After obtaining this flash the image and install the backup and then try the OTA Update and im sure you will now be able to update
Known69 said:
I got the error.
Click to expand...
Click to collapse
I THINK ruu file should be ---.zip only ( not ---.zip.zip)
try that copy ruu file after rename it in your ext-memo and try
baager said:
I THINK ruu file should be ---.zip only ( not ---.zip.zip)
try that copy ruu file after rename it in your ext-memo and try
Click to expand...
Click to collapse
Yeah i too had the same doubt but didn't dare to try that out.
It booted up the **IMG.zip file for me.
Update is in progress...
Thanks.
Known69 said:
Yeah i too had the same doubt but didn't dare to try that out.
It booted up the **IMG.zip file for me.
Update is in progress...
Thanks.
Click to expand...
Click to collapse
you are welcome
just share us your final progress ???
I. Before You Begin Doing Anything
**As with all of these types of tutorials, this may void the warranty of your device. Do it at your own risk.
**Download and install the Asus USB Drivers on your PC, if you haven’t done so yet.
**This should only work on a Windows based PC only.
II. Downloading Required Files
** Necessary tools and Drivers - Mediafire Folder
**Latest OTA form ASUS website : WW_2.17.40.12
** Boot.img, Droidboot.img and Recovery.img from this MEGA Drive posted by Chinaphonearena user and belong to Shakalaca.
** System.img - if you want your phone ROOTed on latest ASUS ZF2 Firmware.
III. Yeah! Im ready to do it
**Plug in your device to your PC using a USB cable.
**Boot your device to fastboot mode Power + Vol Up to enter Bootloader Mode
**Hold down Shift and Right-Click anywhere in Fastboot Folder on your PC and select Open command here. It will launch a Command Prompt Window for you to issue commands to your device.
**When it launches, type in the following command and press Enter (.img files has to be in same folder as fastboot tools):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img - droidboot.img is fastboot, and if you somehow will flash corrupted image, you won't be able to boot to fastboot anymore. Thanks to sorg
fastboot flash system system.img - Only if you use Pre-ROOTed system image from MEGA Drive.
IV. Ready to go with OTA!
** Upload WW_2.17.40.12 or latest Firmware OTA ( Full firmware ) file to phone storage (Phone storage/File.zip)
** After uploading .zip OTA file to phone storage, unplug USB cable from phone. You will recieve notification that new OTA UPDATE is avaliable for installation.
When you bought CN version of ZF2 you may have to Rename OTA file from UL-Z00A-WW-2.17.40.12-user.zip to UL-Z00A-CN-2.17.40.12-user.zip to get notification about update avaliable.
** Wait till update will finish (approx 10 - 15 min) . Phone will restart when finished. First boot may take longer.
V. Dam! No Notification!? what now...
** Boot your device to fastboot mode Power + Vol Up to enter Bootloader Mode
** At Bootloader press Vol Up to choose Recovery Mode
** You will see an error message of updating ota. Wait 5 sec and then press Power + Vol Up simultaneously until you see recovery menu.
** Using Vol Down + Vol Up choose ADB mode and connect your phone to PC via USB cable
** You need Fastboot version 1.0.32 and up to make ADB Sideload working properly with Zenfone 2
** Extract Fastboot.zip somewhere at your PC and put OTA update file ( .zip) in same folder as Fastboot.
** Hold down Shift and Right-Click anywhere in Fastboot Folder on your PC and select Open command here. It will launch a Command Prompt Window for you to issue commands to your device.
** Use command : adb sideload filename.zip
** At 100% it will go back to Recovery Mode main menu. Restart your phone.
** Done !
** Hit THANKS button and RATE this thread for 5 STARS !
Credits to : Chinaphonearena for posting a link to latest pre-rooted system images.
Credits to : Shakalaca for making it all possible
Remember ! You should only do this at your own responsibility.
Please note !
If you posting somwhere else my guide. Please give me a Credit or just link to this thread. Thanks
Please read all pages if you have a issue with guide. I believe other people had it as well and its already solved.
vivix said:
1) Download image files http://www.mediafire.com/folder/setyy42t2cymy#dy87k1a0f8m81
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash files by using fastboot commands :
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
4) reboot phone
5) upload 2.15.40.10 OTA file to phone storage (http://dlcdnet.asus.com/pub/ASUS/Ze...user.zip?_ga=1.221138204.542811237.1430874705)
6) Update via notification about new update avaliable
7)Wait till update will finish (approx 10 min)
8)Enjoy
Say thanks if i helpedI lost 6 hours to achieve this.
Click to expand...
Click to collapse
Are you sure this works i mean there are thousands of threads regarding this issue but none of them work..Can someone with CN version confirm the working of this method....
I bought phone on Aliexpress website. Phone has WW OTA but update via Wi-Fi was impossible. Firmware was 13.40.13 so i think people with that firmware had CN version at start, then sellers updated it to 13.40.13 WW and sended to buyers. Following my method you can update to the latest WW.
Works fine. We've published a similar method. I recommend using the latest rooted ROM. Note, your LTE 4G bands won't be changed with this method.
Have written out the steps in detail for novice users. Includes setting up adb etc: http://www.chinaphonearena.com/forum/showthread.php?tid=10253
Chinaphonearena said:
Works fine. We've published a similar method. I recommend using the latest rooted ROM. Note, your LTE 4G bands won't be changed with this method.
Have written out the steps in detail for novice users. Includes setting up adb etc: http://www.chinaphonearena.com/forum/showthread.php?tid=10253
Click to expand...
Click to collapse
I agree.
But your method is only for pre-rooted system.img with 2.13.40.13 firmware.
I posted method for full OTA firmware upgrade.
Yes, it is similar )
vivix said:
I agree.
But your method is only for pre-rooted system.img with 2.13.40.13 firmware.
I posted method for full OTA firmware upgrade.
Yes, it is similar )
Click to expand...
Click to collapse
The method posted can be done with any system.img (don't have to use rooted ROM), there's no need to do the OTA update as its already the latest ROM (though it will be compatible with future OTA updates, thanks to the ROM creator), and you end up rooted.
They are essentially the same, except for flashing system.img at fastboot instead of doing OTA update. Take your pick. If not caring about root, your method is certainly quicker, as there's no need to DL the huge system.img file.
Thanks. Much appreciated
confirmed works fine on a rooted CN version
Hi,
I followed all the steps and apart from thinking I'd bricked it (the system update screen was sat with the blue bar unmoved for 15 minutes) . It's just completed perfectly.
Really great advice - thanks - I got 2 of these handsets yesterday via ebay both came rooted and it turns out they are CN models but had WW software on them - as per your model - prior to reading your post I was probably going to try and send them back.
I hope and presume for future updates I can continue to use this method?
will do 2nd one now.
Cheers
Ian
Thanksssssssssssssssssssss
Honestly, last time that I tried to have a custom ROM or in any other words, last time I installed and used ( I'm still using it) it was on my samsung galaxy tab(the first galaxy tab of all time) two years ago!
At first I was puzzled in all of these forum pages. I started to change my CN rom to WW Rom yesterday at 2 o'clock. Since I started this process, I just ate dinner and slept for 5 hours. The rest of the time I was trying to install 7 different roms which are available in this forum or asus zenfone forum by 3 different methods of loading a ROM! NONE OF THEM WORKED CORRECT AND COMPLETELY. so I had to start again and read. I can easily say that I've read more than a fat ass book for this process (most of them were duplicates, but I was looking for s.th new among them...)
Your method worked just nolw (@ 1 pm) and I'm really thankful. Honestly I was so bumped and I was thinking to send this device back, just an hour ago I saw your way for the second time and I just decided to try this time as the last way, before returning it!! thank u again for giving me a zenfone
keep up the good work
Confirmed ok on 2nd handset - red CN model 32gb 4gb ram.
It has removed the root access though... Supersu app has gone. and Root checker confirms not rooted.
Which is ok because I can now use Skygo app on the phone - really wasn't expecting that to work!
Thanks guys for good news that it work for you too. I hope that TUT will help others to get rid of 13.40.13 which drain battery as $%^&. Without root it's hard for efficient battery save but atm i use battery doctor from G market and I need to say after 4h it drained 3% battery with turned WiFi. I just wait for proper root tutorial.
vivix said:
Thanks guys for good news that it work for you too. I hope that TUT will help others to get rid of 13.40.13 which drain battery as $%^&. Without root it's hard for efficient battery save but atm i use battery doctor from G market and I need to say after 4h it drained 3% battery with turned WiFi. I just wait for proper root tutorial.
Click to expand...
Click to collapse
Several proper root tutorials already posted. Just follow your own tutorial but flash the pre-rooted system.img. Bam, done.
But latest system.img is not from newest bug fixed firmware mate. That's the problem.
vivix said:
But latest system.img is not from newest bug fixed firmware mate. That's the problem.
Click to expand...
Click to collapse
Latest pre-rooted system.img is the latest ROM available and OTA updateable.
https://www.mediafire.com/folder/k7z5qzh579oc4/Asus_Zenfone_2_ROOT_System_Image
Hello,
Im stuck at no.5, sorry to ask but I don't know what you mean by phone root storage and where it is found.
Can you help please
He means the base of your SD card. Don't copy the OTA into a folder on SD. Copy it to the base of the SD.
with my cable still connected and fastboot still open?
Because I have put it in the sd card nothing happen
Reboot the phone. You should get an OTA update notification. Or boot into recovery and apply the update from there.
Chinaphonearena said:
Latest pre-rooted system.img is the latest ROM available and OTA updateable.
https://www.mediafire.com/folder/k7z5qzh579oc4/Asus_Zenfone_2_ROOT_System_Image
Click to expand...
Click to collapse
Latest WW Firmware is : Version WW_2.15.40.10
Latest pre-rooted system.img you posted is : Version WW_2.13.40.13
I just rewrited whole GUIDE to make it more easier to understand.
vivix said:
1) Download 2.15.40.10 .img files from : http://www.mediafire.com/folder/setyy42t2cymy#dy87k1a0f8m81
2) Boot to fastboot mode (Power + Vol Up) to enter Bootloader Manu and connect it to PC using USB cable provided.
3) Download ADB TOOLS : http://tools.asuszenfoneblog.com/2014/10/adb-fastboot-tool.html
TIP : At Flashtool/fastboot folder <b>press Shift+Right Click then Open Command Here
Using ADB command prompt flash files by using following fastboot commands :
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
4) Reboot phone connected to PC
5) Upload 2.15.40.10 Firmware OTA file to phone storage (Phone storage/File.zip) :
http://dlcdnet.asus.com/pub/ASUS/Ze...user.zip?_ga=1.221138204.542811237.1430874705
6) After uploading .zip file to phone storage, unplug USB cable from phone.
You will recieve notification that new OTS UPDATE is avaliable for installation.
7)Wait till update will finish (approx 10 - 15 min) . Phone will restart when finished.
Dont touch phone because you can mess up something .
8)Enjoy latest V2.15.40.10 WW Firmware.
Say THANKS if i helped !
I Lost 6 hours to achieve this and only THIS method working for 100%.
You will lose your ROOT.
Be careful! Pre-rooted system.img widely avaliable have glitch where when you update superuser app you will soft/hard brick your phone, bootloops etc.
Above method work also as UNBRICK method.
Click to expand...
Click to collapse
You fail to give credit to those who made this possible, especially shakalaca.
This is my version of the steps:
ddfault said:
I recommend using the tools directly from google. (Links fixed 2015MAY08)
These include fastboot and adb
Windows SHA1:720214bd29d08eb82673cd81a8159b083eef19d7
Linux SHA1:b78be9cc31cf9f9fe0609e29a6a133beacf03b52
MacOS SHA1:ddc96385bccf8a15d4f8a11eb1cb9d2a08a531c8
Click to expand...
Click to collapse
As far as steps, I can only speak of the ZE551ML. Start with an unrooted OS.
1.) Download the ADB and Fastboot tools from google (see links above). Download the pre-rooted from from shakalaca in post #1 (If you download the 200MB split version, Windows File Explorer will allow you to open the .zip and copy the .img file out.)
2.) Download the stock full ROM WW_2.15.40.10 directly from support.asus.com
3.) Plug the phone into the PC via USB and copy the UL-Z00A-WW-2.15.40.10-user.zip onto the phone.
4.) The phone will notify you that there is an update:
{
"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"
}
5.) When you select the notification you will be prompted of which file to use in the update:
6.) Hit OK and the phone will reboot and update everything it needs to update per ASUS. (This will include the fastboot/droidboot image, boot, recovery, system, silentlake, and modem firmware.)
7.) Once the update has completed, unplug and power off the phone.
8.) While holding volume up, press the power button until the phone vibrates. At this point release the power button but keep holding the volume up button until the screen flickers to the fastboot menu. Release the volume button when the screen flickers.
9.) Plug the phone back into your computer, open a command prompt and navigate to where you extracted the google tools and the system.img.
10.) Run:
fastboot devices
11.) You should see a your device listed, if you do not, your device is not in fastboot mode.
12.) Assuming you see your device listed in Step 10, run:
fastboot flash system system.img
This will erase your current system partition and then start writting the new image to the partition. Fastboot will split the system.img file into ruffly 500MB chucks and send them to your device.
13.) Once its finished, you can select boot normally on your phone by pressing the power button or run:
fastboot reboot[/QUOTE]
Hey,
since nobody posted a tutorial on how to root the G8 here I will explain how I worked through the tutorial here:
http://www.android-hilfe.de/thema/how-to-root-huawei-g8-bootloader-unlock-cwm-root.729546/
For me it worked like this, but remember that you do the steps at your own risk. Also note that the process will factory reset your phone, so make sure to backup everything in advance!
Getting an unlock code:
Go to hwid5.vmall[dot]com an Register to get a Huawei ID.
Login at the unlock page: https://hwid5.vmall.com
Accept Unlocking Agreement
Enter model number (on your phone you find it at: Settings > About phone > Model number)
Enter serial number (on your phone you find it at: Settings > About phone > Status > Serial number)
Enter IMEI (on your phone you find it at: Settings > About phone > Status > IMEI or IMEI1)
Enter Product ID (on your phone enter: *#*#1357946#*#*)
Submit and get the unlock code. Save it somehow.
Unlock Bootloader:
Download Tools from https://www.mega.nz
Unzip everything to folder HUAWEI G8
Copy HUAWEI G8\SuperSU-PRO-V2.46.zip on your devices storage or sd-card.
Install ADB Driver: HUAWEI G8\UniversalAdbDriverSetup6.msi
Enable developer options on phone: Settings > About phone > build number (tap number 10 times)
Enable oem-unlock on phone: Settings -> developer options -> activate oem unlock
Power off your phone, attach USB cable from phone to pc, hold VOLUME DOWN + POWER BUTTON for some seconds until you see the Fastboot Mode
You should see PHONE Locked and FRP Unlock
On PC goto HUAWEI G8 folder hit SHIFT + RIGHT-CLICK and "Open Command Prompt here"
Enter Command: fastboot oem unlock YOUR_UNLOCK_CODE
Phone should be unlocked. Reboot phone.
Install TWRP Recovery:
Boot phone to fastboot (VOLUME DOWN + POWER BUTTON)
Enter Command: fastboot devices
The command should list your phone
Flash TWRP recovery with command: fastboot flash recovery twrp.img
Install Super-SU:
Boot to recovery with VOLUME UP + POWER BUTTON
Make a backup
Choose Install Zip and install SuperSU-PRO-V2.46.zip (the zip you copied to the device in the beginning)
Reboot. Done!
I hope this helps some of you.
Cheers.
Thank you for posting this!
thanks for ur hard work i just have question why is it important to unlock bootloader ? sorry i know its noob question and let me know guys if the root works i just got my G8 i also found out that there is G8 and GX8
GX8 is only a new name. The first was G8. Same as G7plus.
Root: Some have Problems in Germany after doing the root on androidhilfe.de was explained. But some have no Problems
Please mark that in this thread we also get TWRP recovery Just to avoid more topics about these
Matada02 said:
Please mark that in this thread we also get TWRP recovery Just to avoid more topics about these
Click to expand...
Click to collapse
Sorry, I'm new here. What do you mean by 'mark'? Should I just point it out in the text or is there a feature I'm missing.
TWRP TeamWin endless loop, no system start
Sorry for my stupide english, it´s not my native language, but I had problem´s after install TWRP. First time it seems that´s all ok, i have root on my G8. But by the next reboot the phone starts TeamWin and that´s all. I had no chance to start the system, TeamWin goes into a bootloop. The only thing that helped was to flash the original bootloader.
Details of my system:
Huawei RIO-L01 (G8)
Kernel 3.10.49
Android version 5.1
EMUI version 3.1
If you have problems like this load the orignal stock.img from uploaded [dot]net/file/4pafyrxf
Flash it with fastboot.
Re-zip the file in the same folder as fastboot.exe
Power off your phone
Press Vol down + power button on your phone for about 10 seconds
If you see the white display, connect the phone on your PC
Have a look if phone and FRP is unlocked
in the folder of fastboot.exe click shift + the right mouse button
Choose "Command Prompt open here"
fastboot starts on your PC
write „fastboot devices „ (without the „ “ )
Now you must see a answere from your phone. (it´s abc123 or something like that)
Write „fastboot flash recovery stock.img“ (also without the „“) and press enter
If all is right you have the Stock Recovery and the phone starts normaly.
I hope I can help someone
Please note, i give no warranty! You make it at your own risk!
bertl237 said:
Sorry for my stupide english, it´s not my native language, but I had problem´s after install TWRP. First time it seems that´s all ok, i have root on my G8. But by the next reboot the phone starts TeamWin and that´s all. I had no chance to start the system, TeamWin goes into a endless loop. The only thing that helped was to flash the original recovery
Click to expand...
Click to collapse
For me too. After i flashed twrp.img. everything works... iv'e did a Backup an flashed superuser, after a few retarts iv'e got bootloops.. flashing Original stock recovery solves it... i have now root with stock recovery
this deosnt work give me a 14 days error
jolly_roger_hook said:
this deosnt work give me a 14 days error
Click to expand...
Click to collapse
where do you get that error?
On the unlock code website after I enter all my info
Sent from my HUAWEI RIO-L03 using Tapatalk
Hi Guys, i have a rooted G8, but today i unrooted it to get OTA updates. It turns out i still can't, because the bootloader is still unlocked. Is there any way of re locking it? I have stock Rom and Recovery, and removed root completely. Thanks in advance.
This is what I get
{
"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"
}
Sent from my Nexus 6 using Tapatalk
Pawha said:
Hi Guys, i have a rooted G8, but today i unrooted it to get OTA updates. It turns out i still can't, because the bootloader is still unlocked. Is there any way of re locking it? I have stock Rom and Recovery, and removed root completely. Thanks in advance.
Click to expand...
Click to collapse
Hy Pawha!
I had an unlocked bootloader and locked it by flashing the stock Rom manual.
I downloaded the original Stock Rom from the Huawei page, Re ziped the dload folder to a NTFS formated SD card.
Turn off the phone, press Vol up + Vol down + power button for a view seconds.
The phone start´s with flashing.
After flashing i had a closed bootloader.
In another forum I read that it apparently still is no proper effective method to close a bootloader.
This method is an attempt!
full backup
Is any way to make full backup of my official ROM without unlock bootloader& flash TWRP?
My G8 ROM single sim (bought from Romania) :
Build number RIO-L01C432B130.
Custom version CUSTC432D005.
Thank you!
bertl237 said:
Hy Pawha!
I had an unlocked bootloader and locked it by flashing the stock Rom manual.
I downloaded the original Stock Rom from the Huawei page, Re ziped the dload folder to a NTFS formated SD card.
Turn off the phone, press Vol up + Vol down + power button for a view seconds.
The phone start´s with flashing.
After flashing i had a closed bootloader.
In another forum I read that it apparently still is no proper effective method to close a bootloader.
This method is an attempt!
Click to expand...
Click to collapse
Thanks for the reply! But i'm affraid i blew it up this time. I remembered that i uninstalled some system apps, and that must have been the problem to install the new update, even after i removed the root, and relocked the bootloader. So i just unlocked it again, rooted it again, and restored a backup on Twrp that had all system apps. After that, re-installed stock recovery, toggled OEM lock on settings and relocked bootloader. The update went ok, no errors, but the phone is stuck on the Huawei logo. And now i can't do anything because the OEM is locked on settings... Anyway of unlocking it via ADB? please help me, the phone is new!
Pawha said:
Thanks for the reply! But i'm affraid i blew it up this time. I remembered that i uninstalled some system apps, and that must have been the problem to install the new update, even after i removed the root, and relocked the bootloader. So i just unlocked it again, rooted it again, and restored a backup on Twrp that had all system apps. After that, re-installed stock recovery, toggled OEM lock on settings and relocked bootloader. The update went ok, no errors, but the phone is stuck on the Huawei logo. And now i can't do anything because the OEM is locked on settings... Anyway of unlocking it via ADB? please help me, the phone is new!
Click to expand...
Click to collapse
Turn off your Phone, press Vol+ and then the Power button. When the phone vibrate, leave only the Power button, but not the Vol+ .Hold it, Team Win or EMUI is starting. Make a data/ factory reset and a cache reset. Reboot your system, maybe the phone starts normaly!
I had the same problems a year ago with a Nexus 4. I could fix it with this reset´s
bertl237 said:
Turn off your Phone, press Vol+ and then the Power button. When the phone vibrate, leave only the Power button, but not the Vol+ .Hold it, Team Win or EMUI is starting. Make a data/ factory reset and a cache reset. Reboot your system, maybe the phone starts normaly!
I had the same problems a year ago with a Nexus 4. I could fix it with this reset´s
Click to expand...
Click to collapse
I did it countless times, nothing works. Stuck on a bootloop, with a relocked bootloader and a locked FRP. I really screwed it up this time, have to take it to the store and hope for the best
S̶o̶r̶r̶y̶ ̶f̶o̶r̶ ̶t̶h̶e̶ ̶d̶u̶m̶b̶ ̶q̶u̶e̶s̶t̶i̶o̶n̶ ̶b̶u̶t̶ ̶w̶h̶e̶r̶e̶ ̶d̶i̶d̶ ̶y̶o̶u̶ ̶g̶e̶t̶ ̶T̶W̶R̶P̶?̶
Got it but trying to install it gives me this error. Can someone help?
C:\Android-adb>fastboot flash recovery twrp.img
target reported max download size of 266338304 bytes
sending 'recovery' (43550 KB)...
FAILED (status read failed (Too many links))
finished. total time: 1.438s
Skytop said:
S̶o̶r̶r̶y̶ ̶f̶o̶r̶ ̶t̶h̶e̶ ̶d̶u̶m̶b̶ ̶q̶u̶e̶s̶t̶i̶o̶n̶ ̶b̶u̶t̶ ̶w̶h̶e̶r̶e̶ ̶d̶i̶d̶ ̶y̶o̶u̶ ̶g̶e̶t̶ ̶T̶W̶R̶P̶?̶
Got it but trying to install it gives me this error. Can someone help?
C:\Android-adb>fastboot flash recovery twrp.img
target reported max download size of 266338304 bytes
sending 'recovery' (43550 KB)...
FAILED (status read failed (Too many links))
finished. total time: 1.438s
Click to expand...
Click to collapse
Try an other usb port. Or some other pc some usb-ports doesn't gave enough ampere... it helps me out
Sent from my HUAWEI RIO-L01 using XDA Free mobile app
Hello.
This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like.
Note: Unlocked bootloader is not required to do any of the actions described in this guide.
Disclaimer: I'm in no way responsible for the actions you perform and whatever happens to your device due to these actions. Proceed at your own risk.
Prerequisites:
Service firmware. Can be downloaded here. It's an older build, but it will do the trick and it's the only one I could find freely available at the time of writing. Only for WW SKU
Zip for your desired build. Can be found here.
- Note: For this guide, my desired build will be WW-17.1810.1910.63, which is a special case, as you will need to flash in the following order: Service Firmware -> WW-16.1220.1909.194 -> WW-17.1810.1910.63. In other cases, unless noted otherwise in a description of the build on the ASUS website, Service Firmware -> Desired build will suffice.
Platform tools of Android SDK. Latest package can be downloaded from: Windows | Linux. Somewhat optional but good to have.
Step 1 - Preparing the environment
This is not required but for the sake of simplicity and keeping everything in one place, create a folder and name it whatever you like, for example ASUS or Unbrick
Create a sub-folder inside the folder you've created in the previous step, call it service_firmware, download and unzip service firmware into this folder
Download files for the desired builds from the above link. For this specific case, WW-16.1220.1909.194 and WW-17.1810.1910.63.
3.a If you have microSD card, transfer zip file for the desired build into its root and insert the card into the phone.
3.b. If you do not have a microSD card, download and unzip platform tools mentioned in the prerequisites as you will need adb to flash firmware/s via sideload
Step 2 - Flashing service firmware
Connect your phone via USB
Enter fastboot mode via one of the methods:
1.1. Turn off your device, then turn it on while holding down the power and volume up buttons at the same time. Release the power button when it powers up (keep holding the volume up button)
1.2. If you have platform tools, you can do adb reboot fastboot
Open CMD (windows) | Terminal (unix)
CD into the folder with service firmware from item #2 from the step above.
Make sure your phone is detected by typing fastboot devices
Ensure battery is at least 20% charged. Aside from normal means, it's possible to check the battery charge via fastboot oem get-batcap.
Sample output: (bootloader) bat cap = 35, which means that the battery is 35% charged.
IMPORTANT NOTE BEFORE CONTINUING:
By default, flashing with one of the scripts wipes your userdata, in other words, it performs a factory reset.
It is possible to avoid userdata wipe (although not encouraged) but keep in mind, unless you flash your current build after flashing service firmware, your phone will not boot up.
If you absolutely would like to preserve your userdata, even if for the sake of backing it up before doing a factory reset, you have to edit the flashall script in the following way:
Windows: Open flashall.cmd in your favorite text editor, go to line #298 and change it from fastboot -w to REM fastboot -wand save the changes.
Unix: Open flashall.sh in your favorite text editor, go to line #275 and change it from $fastbootcmd -w to #$fastbootcmd -w and save the changes.
Once again, this is not encouraged as it can potentially cause issues later on. You've been warned.
Run the script
1. 1. Windows: In the CMD you opened earlier, type flashall.cmd
1. 2. Unix: In the Terminal you opened earlier, type ./flashall.sh
Note: An obvious note, do not disconnect your device from your PC while flashall script is running. Your device will reboot a few times during the execution.
Once script outputs format logdump... and the phone reboots, service firmware will be flashed.
Step 3 - Upgrade to your desired build
Enter Recovery mode via one of the following methods:
1.1. If your phone is turned on and USB debugging is enabled, use command adb reboot recovery
1.2. While in fastboot mode, navigate to Recovery Mode using Volume Up/Down buttons and select with a single press of a Power button
1.3. While in fastboot mode, issue one of the following commands : fastboot reboot recovery or fastboot oem reboot-recovery
Once in Recovery Mode, you have 2 ways to proceed:
A: Update from SD card
A.1. Select Apply update from SD card option
A.2. Navigate your SD card and select UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip
A.3. Confirm your choice with a single press of the Power button
A.4. Once you're back to the menu of Recovery Mode, reboot by selecting Reboot system now and enter Recovery Mode once again via any of the above methods
A.5. Select Apply update from SD card option again
A.6. Navigate your SD card and select UL-ASUS_I01WD-ASUS-17.1810.1910.63-1.1.1-user.zip
A.7. Confirm your choice with a single press of the Power button
A.8. Once you're back to the menu of Recovery Mode, select Reboot system now
B: Update through ADB Sideload
B.1. Select Apply update from ADB option
B.2. In your CMD/ Terminal, issue command adb sideload "UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip"
B.3. Once you're back to the menu of Recovery Mode, reboot by selecting Reboot system now and enter Recovery Mode once again via any of the above methods
B.4. Select Apply update from ADB again
B.5. In your CMD/ Terminal, issue command adb sideload "UL-ASUS_I01WD-ASUS-17.1810.1910.63-1.1.1-user.zip"
B.6. Once you're back to the menu of Recovery Mode, select Reboot system now
Note: Like I've mentioned earlier, these steps are specifically for build WW-17.1810.1910.63. If your target build does not require another build for an update, you can skip steps A.4 to A.7 or B3 to B5
That's pretty much it. If you followed the steps above correctly, you should once again have a running phone with your desired build of firmware.
If you have any questions, do not hesitate to ask.
Cheers.
Hello i've a question (sorry for my bad English). This morning my phone was bricked (red message logo), and with this tuto i remove this logo and i found my original recovery.
But when i want to install firmware from recovery with SDcard option, i've a message no SDcard found and impossible to install firmware. (even after several tries)...
If i reboot my phone i have android logo bootloop...
Can you help me???
https://drive.google.com/file/d/1GStfEgZFpb66JRaAmjeYOKmyn9d8WcPz/view?usp=sharing
https://drive.google.com/file/d/1FSRZfI1vNAyDQDZaLDGrHyiC-lImsYhr/view?usp=sharing
Thank you and Happy New Year...
Thanks for the link to that service firmware!
_Kuroi_ said:
This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like.
Cheers.
Click to expand...
Click to collapse
Thanks a lot mate, you made my day!
Please, one question: can you tell me, if both slots (A & B) are flashed by this method?
Thanks!
Thank you so much!
I've wanted to go back to stock for so long, but I haven't been able to find a stock ROM. I've even contacted ASUS support and they couldn't even get it! Thank you so much for the download and for the guide, you've made my week. I'll be smiling every time I use my phone thanks to you!
Great guide. I have a soft bricked device after flashing Lineage 16.0 recovery. Have a boot loop and can't get to recovery. I realise the mistake was flashing the recovery as should have just booted it.
Has anyone else had success with this on a Zenfone 6?
For those who need it; managed to resolve by downloading the stock firmware from Asus, extracting the boot.img and flashing it. Back working.
Didn't try the guide but this is quicker in this scenario if you have flashed a custom recovery to the boot partition. There is no separate recovery partition so this soft bricked the device, overwriting boot with recovery (I followed the guide here for LineageOS which is ill advised) . Should be booting the recovery rather than flashing, or booting into stock recovery and using the installer zip for your custom recovery.
Steps to recover:
1. Download stock firmware from Asus - make sure you use the same firmware version installed on the device or you may find it will boot but some hardware such as WiFi or others may not work.
2. Extract the archive and then you need to extract the boot.img from payload.bin - see this article and use the payload dumper
3. Flash your boot.img with fastboot flash boot boot.img
4. Reboot
Device should restart and boot up. Now to see why TWRP and LineageOS custom recoveries won't boot.
Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.
This worked for me, but I'm still in CSC FastBoot Mode and when Android boots, I'm asked to insert a previous pin, which nothing works. Any advice?
kenturky said:
Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.
Click to expand...
Click to collapse
hey, did you manage to fix this? i'm having the exact same problem
sapientsaxonsaboo said:
1. Download stock firmware from Asus - make sure you use the same firmware version installed on the device or you may find it will boot but some hardware such as WiFi or others may not work.
2. Extract the archive and then you need to extract the boot.img from payload.bin - see this article and use the payload dumper
3. Flash your boot.img with fastboot flash boot boot.img
4. Reboot
Device should restart and boot up. Now to see why TWRP and LineageOS custom recoveries won't boot.
Click to expand...
Click to collapse
I tried to install latest firmware from
https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_BIOS/
everything goes fine but it shows till this moment:
fastboot flash boot_b boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.295s]
Writing 'boot_b' FAILED (remote: 'Flashing is not allowed for non-official image')
any suggestions ?
kenturky said:
Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.
Click to expand...
Click to collapse
Taylor Moon said:
hey, did you manage to fix this? i'm having the exact same problem
Click to expand...
Click to collapse
Try flashing latest image of Android 9 and then flash Android 10
Can somebody please help me with my problem?
So I was able to get my hands on a new 8gb/512gb matte black version of this. Was setting up the phone, updated to Android 10 first before transfering sms, call logs and updating apps. Went to turn off the phone to insert my SIM card and now the phone won't turn on. It vibrates every time I press the power button but then nothing. Currently it's connected to the supplied charger with the LED light lit red. It was already charging while I was using it, had about 70% battery before I switched it off. I've tried volume down + power button for 10 seconds, LED light turns off and it vibrates, and it keeps vibrating every 10 seconds when it's connected to the charger (doesn't keep vibrating when it's not connected). Can feel the area between the fingerprint reader and camera pretty hot during this. Volume up + power doesn't work either. Any ideas?
Click to expand...
Click to collapse
Also, the phone gets detected when I connect it to my laptop but I can't do an "adb reboot" or "adb reboot fastboot" as it says the "error: device is not found."
I left it on charge overnight and the LED changed from red to green too.
Any help would be greatly appreciated.
CVonV said:
Can somebody please help me with my problem?
Also, the phone gets detected when I connect it to my laptop but I can't do an "adb reboot" or "adb reboot fastboot" as it says the "error: device is not found."
I left it on charge overnight and the LED changed from red to green too.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
When you connect it to your laptop, go to device manager and check what it is detected as.
_Kuroi_ said:
When you connect it to your laptop, go to device manager and check what it is detected as.
Click to expand...
Click to collapse
I can't seem to find any listing that would correspond to the phone under the Ports section :/
CVonV said:
I can't seem to find any listing that would correspond to the phone under the Ports section :/
Click to expand...
Click to collapse
Maybe upload a screenshot of the devices listing?
_Kuroi_ said:
Maybe upload a screenshot of the devices listing?
Click to expand...
Click to collapse
I thought it would've been listed in the Ports section but it's right at the top under "Android Device" as "Android ADB Interface". I believe I have the correct Qualcomm drivers installed.
Attached screenie also shows device not found when I try an "adb reboot" in command prompt.
{
"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"
}
Hmm, I half expected it to be listed as QDLoader 9008, but then it would be under serial ports.
Try fastboot commands instead of adb and also try holding power + vol down for 10-15 seconds
Great guide @_Kuroi_ , I will be trying it out soon. The service rom you are using is pretty old. So I grabbed the last P update service firmware (WW-16.1220.1909.194) and the latest Q build I could get currently (WW-17.1810.2002.133). I have a subscription to one of the paid firmware sites for reasons like this. This way people have more options and it will simplify most people's updating because they can go from the new P service rom to any Q ota. Q firmware doesn't really make sense until it's not being updated anymore but it's here just in case someone finds it useful. If there is some incompatibility in the future or something that requires a newer update I will grab it then. If there isn't I will grab the last firmware once Q is stopped being updated.
WW-16.1220.1909.194
Here
WW-17.1810.2002.133
Here
WW-17.1810.2009.176
Here
Feel free to update your guide to incorporate these all I ask is a credit in the OP for providing it.
After running ./flashall.sh I get the following output:
Done.
target reported max download size of 805306368 bytes
File system type is raw !!!
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'userdata'...
OKAY ( 0.266s)
Sending 'userdata' (1888 KB)...
OKAY ( 0.067s)
Writing 'userdata'...
OKAY ( 0.003s)
Erasing 'metadata'...
OKAY ( 0.027s)
Finished. Total time: 0.799s
Rebooting...
(I changed square brackets to round brackets in the output because otherwise it wouldnt let me post this comment because of bbcode)
I don't seem to have a recovery partition by the end of it and "adb devices" doesn't show me anything.
Does anyone know what might have gone wrong?