Related
Hello Developers,
I am a HK Version Hero user. My region started the OTA 2.1 update for HERO.
I have already restore my Nanbackup to the first 1.5 backup.
When it finished the download, my phone reboot to the recovery mode and start the update and prompted:
E:No signature (231 files)
E:Verification failed
Installation aborted.
My need rom version should be 2.73.721.91.
Anyway that I can update to the new stock rom?
Thanks for the help !!
I got the link for the first OTA download, but I am a new user I cannot post it out.
Is it I just delete the recovery.img file? and it will work?
Thanks again
hero-err said:
I got the link for the first OTA download, but I am a new user I cannot post it out.
Is it I just delete the recovery.img file? and it will work?
Thanks again
Click to expand...
Click to collapse
No, you'd have to re-sign the zipfile. If a file is added/removed or editted, the hashes don't match anymore and no one will be able to flash it.
Learn how to re-sign, or just upload it @ multishare as-is, and request re-signing of it. Mayb someone will help you out .
just take the recovery img out of the ruu and flash it then try to update.Should work then
I have the same problem. I really didnt understand what you just said..
My file is a .zip and can not be flashed with flashrec.
can you explain better for a n00b like me?
sundrik said:
I have the same problem. I really didnt understand what you just said..
My file is a .zip and can not be flashed with flashrec.
can you explain better for a n00b like me?
Click to expand...
Click to collapse
you don't flash files with flashrec, you flash them from recovery mode.
and just because something is a .zip doesn't mean it can be flashed. it has to be signed with the appropriate update script.
It like this.
I got an OTA for the 2.1. This generated an error when updating. So i thought i just download the file and do it from recovery mode.
Downloaded the file from here: liveimage.htc.com//OTA_Hero_ChungHwa_3.31.751.1_R-2.73.751.13_release048gnt2ecw16ubyr.zip
The link is not active anymore.
But i still get the same error.
I tried to do a factory reset and do the update after that, but without any luck.
I know this is the update for my phone, but i cant do it. And you guys speak about signing the file before, but i dont know how.
Probably same error for topic starter.
to do what i said you have to boot the phone in recovery.take the files out of the update.zip (or if it a RUU go HERE) in the .zip file should be boot.img,recovery.img,userdata.img,system.img,HBOOT and a few others....
Take out the recovery.img
and flash via fastboot (turn phone one holding back)
open cmd window (windows key + r) type cmd
fastboot flash recovery (drag and drop recover.img into cmd window) press enter
Then try updating
I dont get it to work.
I take out the recovery.img
Turn the phone on by holding 'back' while power on. (Screen with three android skaters)
Then i plug in the usb.
The text 'FASTBOOT' change to 'FASTBOOT USB'
Open cmd (windowskey + r and type cmd adn enter)
Drag and drop the recovery.img to command window and press enter.
This makes the DVD burning application on the computer to start and wants to burn the file.
sundrik said:
I dont get it to work.
I take out the recovery.img
Turn the phone on by holding 'back' while power on. (Screen with three android skaters)
Then i plug in the usb.
The text 'FASTBOOT' change to 'FASTBOOT USB'
Open cmd (windowskey + r and type cmd adn enter)
Drag and drop the recovery.img to command window and press enter.
This makes the DVD burning application on the computer to start and wants to burn the file.
Click to expand...
Click to collapse
Maybe you should use fastboot - the program for your pc?
The steps that were told to you were right, but I think you didn't do the last one as you should. Once in the command-line, you have to type "fastboot flash recovery " (yep, there's a space at the end) and then write the path of the recovery image (i.e., if it's in C:\asd\recovery.img, it would be "fastboot flash recovery \asd\recovery.img"), or drag and drop the file to the cmd, and it will write the path.
You know where to get this fastboot program...
I only find this from 2008. Should be a better one with not so much tweaking?
http://forum.xda-developers.com/showthread.php?t=463627
Nope, not really, I use linux.
Thanks for all the help!! I finally upgraded.
I restore to my 1.5 backup and down the update part by part.
I pull out the recovery.img and zip it back and re-sign it, copy to my phone and rename it to Update.zip and flash the first part. Reboot and copy the OTA2 to the phone and also rename it to Update.zip, flash it again. Final reboot, its now the official 2.1 android update. Also the root is still there.
OTA1
Badongo file 23546527
OTA2
Badongo file 23546783
THANKS again!!!
(sorry about the link, they won't let me post it ><)
hero-err said:
Thanks for all the help!! I finally upgraded.
I restore to my 1.5 backup and down the update part by part.
I pull out the recovery.img and zip it back and re-sign it, copy to my phone and rename it to Update.zip and flash the first part. Reboot and copy the OTA2 to the phone and also rename it to Update.zip, flash it again. Final reboot, its now the official 2.1 android update. Also the root is still there.
OTA1
Badongo file 23546527
OTA2
Badongo file 23546783
THANKS again!!!
(sorry about the link, they won't let me post it ><)
Click to expand...
Click to collapse
PM u, thank you.
Could you tell me the Second HK OTA Package filename?
I really need it, if anyone who know it, please tell me.
Thank you very much.
hello, I flashed RUU_Hero_hTC_Asia_HK_WWE_3.34.721.1_R_Radio_63.18. 55.06P_6.35.15.14_release_signed on my taiwaan hero using goldcard and now i cannot flash my RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoD river. . . please help me! it says error - invalid update tool! WTF ... i have used that ruu many times but now it aint working. it strucks at updating signature.
and even the flash recovery software aint working !
hello, I flashed RUU_Hero_hTC_Asia_HK_WWE_3.34.721.1_R_Radio_63.18. 55.06P_6.35.15.14_release_signed on my taiwaan hero using goldcard and now i cannot flash my RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoD river. . . please help me! it says error - invalid update tool! WTF ... i have used that ruu many times but now it aint working. it strucks at updating signature.
and even the flash recovery software aint working !
I think u need to restore it back to your 1.5 backup first.
Thanks for Hero-err.. I have solved my problem too by following his hints ^_^
i dont have flashed recovery so how would i do nandroid restore ?
So it seems I have messed up my phone decently bad
decided to go back and reload everything from scratch but unfortunately flashed back a CWM version thats 3.0.1 and when I try to flash my old recovery (ICS CM9) it gives me error 7
I am guessing thats because I have to install 5.0 CWM can anyone explain to me how to do this?
Thank you so much all!
Yan
More Info:
Ok so heres the deal.
I was originally running CM9 from Nexus MV ICS rom with a Franco Kernel.
All was well and phone was rock solid for weeks since he released with everything working.
as the update came out I was told I should revert back to 2.3.6 and wait for the OTA update that way I could have the true OEM ICS. It is pretty much 90% of why I originally Rooted and unlocked my phone.
I used this link.
http://forum.xda-developers.com/showthread.php?t=1063664
and downloaded
Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
That I flashed using CWM
Phone rebooted fine but had no SuperUser file and seemed like it no longer was rooted so though if I go back and re-root it should be fine.
Went to.
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
and went straight to instruction 5) Open up a command prompt by typing “cmd” under Start->Search Programs and files.
Then type “cd \nexussrootnew” to browse into the directory in Windows. For Linux and Mac, should be similar to “cd /nexussrootnew“.
Then type “fastboot oem unlock“.
Thats when I went back to CWM 3.1.0.1 and tried to install any rom or backup and it just seems to give me Status 7 error.
I hate that I cant figure this out alone but I am a little lost.
Here's a link: http://forum.xda-developers.com/showthread.php?t=1382624
Use the search next time, it took less than 10 seconds for me to find the page.
063_XOBX said:
Here's a link: http://forum.xda-developers.com/showthread.php?t=1382624
Use the search next time, it took less than 10 seconds for me to find the page.
Click to expand...
Click to collapse
Actually I tried this originally
http://forum.xda-developers.com/showthread.php?t=1248760
Still get Status 7!
Sorry I usually search before just forgot to write that in!
Download CWM 5.0.2.0 and rename the .img to recovery.img
(i'll assume you have phone drivers and everything working, and fastboot)
Put the recovery.img into the same directory as your fastboot.exe
Boot into your bootmanager (vol up+power)
Plug phone into PC
Open up CMD prompt and change to the directory where you have fastboot.exe
(cd c:\android\tools) for example
type in:
> fastboot flash recovery recovery.img
reboot to recovery
seriosbrad said:
Download CWM 5.0.2.0 and rename the .img to recovery.img
(i'll assume you have phone drivers and everything working, and fastboot)
Put the recovery.img into the same directory as your fastboot.exe
Boot into your bootmanager (vol up+power)
Plug phone into PC
Open up CMD prompt and change to the directory where you have fastboot.exe
(cd c:\android\tools) for example
type in:
> fastboot flash recovery recovery.img
reboot to recovery
Click to expand...
Click to collapse
I tried that and unfortunately it gives me an error when I try it
says
"Error: cannot load recovery.img"
Used the download from this link!
http://forum.xda-developers.com/showthread.php?t=988686&highlight=recovery
Looks like someone else is having the same issue as me.
http://forum.xda-developers.com/showthread.php?t=996914&page=4
Try to just boot the newer cwm recovery with fastboot
Fastboot boot recovery recovery name.img
albundy2010 said:
Try to just boot the newer cwm recovery with fastboot
Fastboot boot recovery recovery name.img
Click to expand...
Click to collapse
Same error as earlier....
Can Not load
Darn this is frustrating!
sspikey said:
Same error as earlier....
Can Not load
Darn this is frustrating!
Click to expand...
Click to collapse
SWEET just got this phone to boot up again! No network right now for some reason but wifi works!
Here is what I used.
http://forum.xda-developers.com/showthread.php?t=884093
Where should I go from here? Ideas? I am guessing I have to install super user Zip through the current 3.0XX CWM right?
MORE PROGRESS!!!!!
Got CWM 5.0.2.0 loaded on to it by flashing the IMG through CMD
Worked after what I did earlier!
Progressing forward!!!!
Final cherry on top of the cake!!!
works perfectly again accepted my nandroid backup and shes running at 100%
ah feels good!
please help me i am also having the same problem i tried everything nothing seemed to work out and please check my thread ( http://forum.xda-developers.com/showthread.php?t=1533346 ) thnx.
I tried to use the kindle fire utility in order to root my fire, but when I tried to use it, the first thing I did was install the drivers..... Then change it into fast boot mode, which I didn't realize would make it automatically reboot.... With out TWRP, or the fire fire fire boot loader. It is stuck at the "Kindle Fire" splash screen, and does not even connect to my computer. Is there a way to change it back to normal boot mode? Because when I tried to use the kindle de-bricking utility, it did not work, because it says waiting for device. If anyone could give me some advice, I would appreciate it.
May not help, but try the following: http://forum.xda-developers.com/showpost.php?p=21477909&postcount=13
have you tried to hold pwr button for ~20sec ?
I had the same problem and it was because the TWRP file was corrupt or incomplete. It went to reboot, and just stuck on the Kindle Fire logo. tried resetting, and everything. What I did was re-install the drivers, plug the device back in to the computer and even if KFU says your kindle isn't connected, try changing the boot mode back to normal. It worked for me and I restarted and tried the whole TWRP installation process over with a non-corrupt file and it worked just fine.
b63 said:
have you tried to hold pwr button for ~20sec ?
Click to expand...
Click to collapse
I actually did, I had tried a hard reboot several times.
then i would try as suggested above - if it don't work you can do it manually by opening a (elevated) command prompt and cd to the tools folder of kfu (eg c:\kfu\tools) and issue "fastboot -i 0x1949 oem idme bootmode 4000"
if it says <waiting for device> cold reboot the kf - the command should be picked up and finished - another reboot should bring you to normal boot
if this not working then you should check your drivers:
for fastboot it should be "android adb interface"
jblack426 said:
I had the same problem and it was because the TWRP file was corrupt or incomplete. It went to reboot, and just stuck on the Kindle Fire logo. tried resetting, and everything. What I did was re-install the drivers, plug the device back in to the computer and even if KFU says your kindle isn't connected, try changing the boot mode back to normal. It worked for me and I restarted and tried the whole TWRP installation process over with a non-corrupt file and it worked just fine.
Click to expand...
Click to collapse
I will try as soon as I get home. Thanks for the help so far!
jblack426 said:
I had the same problem and it was because the TWRP file was corrupt or incomplete. It went to reboot, and just stuck on the Kindle Fire logo. tried resetting, and everything. What I did was re-install the drivers, plug the device back in to the computer and even if KFU says your kindle isn't connected, try changing the boot mode back to normal. It worked for me and I restarted and tried the whole TWRP installation process over with a non-corrupt file and it worked just fine.
Click to expand...
Click to collapse
I tried your method and it rebooted my kindle succesfully, although it restored itself to factory conditions (which i dont think it's a bad thing, since i was scared of seeing the device stuck with the logo)
I will try to run kfu all over again and see if it works this time. I'll let know how it goes.
Thanks!
EDIT: Which twrp file did you use the second time? Can you post a link to it?
EDIT2: Nevermind about the first edit; the second time, kfu downloaded twrp instead of using its own recovery.img (which i believe is the corrupt file). I still cannot install firefirefire; a command line says "'adb' is not recognized as an internal or external command, operable program or batch file." Any help with that? Or can my kindle be safe without firefirefire? Thanks again!
it's not save without fff ! you need it to get to twrp and to have fastboot available for some seconds during startup
would recomend to try with kfu 0.9.3 and 0.9.1
some people have success with only one of the versions
Glad you got back to stock at least. The problem I had was that my internet connection timed out when KFU was downloading the files for the TWRP and FFF installation. There were incomplete files that KFU recognized as being there when i re-tried and it tried to install them again. You need to make sure you delete the files in the TWRP folder before you try again that way KFU won't find them and will download them again, hopefully successfully this time. You could also just delete the entire KFU you already have on your computer and download the whole thing again and re-try.
Hopefully this helps.
elporsche said:
I tried your method and it rebooted my kindle succesfully, although it restored itself to factory conditions (which i dont think it's a bad thing, since i was scared of seeing the device stuck with the logo)
I will try to run kfu all over again and see if it works this time. I'll let know how it goes.
Thanks!
EDIT: Which twrp file did you use the second time? Can you post a link to it?
EDIT2: Nevermind about the first edit; the second time, kfu downloaded twrp instead of using its own recovery.img (which i believe is the corrupt file). I still cannot install firefirefire; a command line says "'adb' is not recognized as an internal or external command, operable program or batch file." Any help with that? Or can my kindle be safe without firefirefire? Thanks again!
Click to expand...
Click to collapse
That means it can't find the ADB.exe in tools for Kindke Fire Utility. The tools folder must be in the same folder as the batch file.
b63 said:
then i would try as suggested above - if it don't work you can do it manually by opening a (elevated) command prompt and cd to the tools folder of kfu (eg c:\kfu\tools) and issue "fastboot -i 0x1949 oem idme bootmode 4000"
if it says <waiting for device> cold reboot the kf - the command should be picked up and finished - another reboot should bring you to normal boot
if this not working then you should check your drivers:
for fastboot it should be "android adb interface"
Click to expand...
Click to collapse
Worked! Thank you so much sir! Now that I followed a guide! (since I am no longer a derp about it) I am now rooted.
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Can you please tell me how you changed the boot mode because i also bricked my kindle by the kfu.
- run kfu
- key in "1" and enter (bootmode menu)
- key in "1" and enter (bootmode normal)
that's it
can't explain easier ...
b63 said:
- run kfu
- key in "1" and enter (bootmode menu)
- key in "1" and enter (bootmode normal)
that's it
can't explain easier ...
Click to expand...
Click to collapse
Not Exactly. First he needs to check the device status by pressing 0, becouse if device have offline mode in KFU, he can't do much (propably he will need to use fastboot comands rather than adb)
papugoz said:
Not Exactly. First he needs to check the device status by pressing 0, becouse if device have offline mode in KFU, he can't do much (propably he will need to use fastboot comands rather than adb)
Click to expand...
Click to collapse
wrong - if the device is in fastboot mode adb will allways be offline !
btw. kfu is using fastboot commands
So what your saying is i can't do anything.
kingrafa135 said:
So what your saying is i can't do anything.
Click to expand...
Click to collapse
it is nearly impossible to realy brick a kf - just do as i suggested
if it's not working tell us what exactly happens ...
some important hints from the op of kfu:
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Click to expand...
Click to collapse
and from vashypooh - dev of kfu:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
b63 said:
wrong - if the device is in fastboot mode adb will allways be offline !
btw. kfu is using fastboot commands
Click to expand...
Click to collapse
From my exp with KFU, I had to use fastboot command directly, becouse KFU, couldn't hadle it.
Hi,
i am searching this forum for about 5-6 hours without finding a solution for my problem.
My KF is stucked on "kindle fire" start screen (it blinks) after i made a bad misstake by editing the account.db . I wanted to add a second google account to my new installed market.
But after that it is stucked.
I tried the kfu 0.9.3 but no matter what i do, i get an error with "operation not permitted" or "Could not access the Package Manager. Is the system runnung?"
[edit]Everytime i try to enter su at adb shell, i got this message "[1] + Stopped (signal) su"[/edit]
My driver seem to work.
And i dont know what i did, after some utility uses i got this yellow triangle and it stucked first. But now it continued again to the blinking kindle fire logo.
Can somebody please help me? I realy dont know what to do.
And i am sorry for my bad english :/ .
Thank you.
Have you tried going into recovery?
Sent from my Kindle Fire using xda premium
Issue the following commands to reboot to normal
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot
Sent from my Amazon Kindle Fire using Tapatalk
Hey, thanks for the answer.
I was able to get twrp running with this post:
b63 said:
hey cool - thought the shell is messed up - it's not - you can get to fastboot - great
would suggest to follow this thread starting at point 2:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
and your allready downloaded twrp is recovery.img not twrp-blaze-2.0.0RC0.img
simply adapt the corresponding command in the above thread
is you want stock rom i would suggest to use a prerooted stock rom (i prefer the unsecure version):
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20
Click to expand...
Click to collapse
Now i tried to install a rom, but i am not sure it worked. Because the kf is starting for over 10 min now and just showing this "kindle fire" logo. Do you or anybody has got a link for the original 6.2.2 or maybe with google play? I have got the problem that the roms i downloaded dont have a md5 file and that discription i used said i have to activate md5 check.
Thank you.
P.S. How long do i have to wait until i can be sure it wont start? And do i realy have to command "adb shell idme bootmode 4000" and "adb reboot" after flashing? Or can i just click on reboot?
Check the check sum md5 before you install.
It looks like the KF is booting into fastboot mode. You need to issue the mentioned commands to boot normal either before or after you install a new ROM. First you to boot to normal and find the ROM you like to install. As you know, use TWRP to install a new ROM.
Sent from my Amazon Kindle Fire using Tapatalk
Guys, thank you. Its alive..again .
I just found a rom that worked .
Its is 5 am and i rly have to sleep now..what a night -.- .
Again, thanks for your help.
just for info:
had a case where a prerooted stock rom needed 20min for first boot
so be patient ...
please mark the subject of the topic (edit first post) with [Solved]
Hello all,
I really need help for my ZE500KL. In summary, it stucks on ASUS logo and bootloop. I can't get to welcome screen.
It is not rooted, i've never touched to the original system. I got this problem after an update from OTA. The update was not interrupted for information.
I can get to the recovery menu, can do a wipe data/factory reset, but it solves nothing. Same problem.
I've tried :
- apply update from adb but this stops at 46% and failed with an error like E:failed to verify the whole-file signature
- apply update from microSD but it stops and failed without error message
I don't know if there is another way to fix.
Thanks
Bro go to the asus site and download the whole rom nd flash it thru recovery.
M also had a same problem.
So let me know nd which variant u hav?
Thanks for the reply.
When i said "I have apply update", this means that i've downloaded zip file from Asus website, and loaded it via the recovery but the process stops at 46%.
Maybe it will work for a custom recovery like CWM or TWRP but as i know, there is not a working CWM or TWRP for ZE500KL at this time. Maybe.
For me, the stock recovery don't work for loading the zip file from ASUS. It says something like : Unable to verify the whole-file signature, Process failed
Fus_XDA said:
Thanks for the reply.
When i said "I have apply update", this means that i've downloaded zip file from Asus website, and loaded it via the recovery but the process stops at 46%.
Maybe it will work for a custom recovery like CWM or TWRP but as i know, there is not a working CWM or TWRP for ZE500KL at this time. Maybe.
For me, the stock recovery don't work for loading the zip file from ASUS. It says something like : Unable to verify the whole-file signature, Process failed
Click to expand...
Click to collapse
If your device stops at logo this means that it boots into fastboot mode. I`ve had a same problem. You can take this adb driver . After installing you need to put in C:\adb file boot.img from archive which you dowloaded from official asus.com, then run cmd.
Code:
cd c:\adb
and last command will be...
Code:
fastboot boot boot.img
try it.
kvantor said:
If your device stops at logo this means that it boots into fastboot mode. I`ve had a same problem. You can take this adb driver . After installing you need to put in C:\adb file boot.img from archive which you dowloaded from official asus.com, then run cmd.
Code:
cd c:\adb
and last command will be...
Code:
fastboot boot boot.img
try it.
Click to expand...
Click to collapse
I tried. It doesn't work.
I proceed like this :
1- I've booted the device in recovery mode, connect it to PC and uninstall the device and his driver in to the device manager. I do the same in fastboot mode
2- I've installed the 15 seconds adb ver 1.43. As it is recommanded, I force install of drivers to "Android ADB interface" for recovery mode and "Android Bootloader Interface" for fastboot mode. At this time, adb detects the device via "c:\adb> adb devices"
3-I've extracted the "boot.img" from UL-ASUS Z00E-WW-12 8 5 106-user.zip from Asus Website
4-No problem to proceed with "c:\adb> fastboot boot boot.img" BUT that's all.
--> The device boots, passes the ASUS logo with the powered by android at the bottom", arrives to the second ASUS logo (the one animated), then there are messages "Android upgrading, optimising 1 of 1 app", "Starting apps", then it reboots, and bootloops .... again and again. I have to take out the battery to turn it off.
Have you tried downloading the full ROM image from the ASUS support website again? (yes, download again and try flashing your device again). Usually when it says something about signature verification failed, it is due to the incomplete download of the ROM image (corrupted), or that it has been modified.
Do report back the results.
Download Link (for your convenience): http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500KL/UL-ASUS_Z00E-WW-12.8.5.222-user.zip
Download Link (for your convenience): http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500KL/UL-ASUS_Z00E-WW-12.8.5.222-user.zip
Click to expand...
Click to collapse
I's been thinking to this ...
I've downloaded 3 times the ROM from asus website. The download procees has been interrupted because of internet problem but i was able to resume after. I've even downloaded previous version. I am able to extract the zip file to my computer without error like cooupted file or CRC..
I need to know if other persons have the same problem exactly with this ZE500KL because, i have recently done the same thing with my ZE551ML and i had no problem.
Have you tried flashing the previous updates (software versions) instead? Could be a "bogus" update.
Rizzed said:
Have you tried flashing the previous updates (software versions) instead? Could be a "bogus" update.
Click to expand...
Click to collapse
Yes. Same problem with .172
I was been delighted when i see this TWRP for ZE500KL http://forum.xda-developers.com/zenfone-2-laser/development/recovery-twrp-3-0-0-0-recovery-t3319704 and it works,
But my joy was so short.
It says that it was unable to install the ZIP file because the ZIP is for WW_PHONE, and my phone is an OMNI_ZE500KL !!! What is this ? Never heard about it before. What's weird with this AUS ZIP file !!!??
Can you try to ADB Sideload the ASUS ROM?
sagematt said:
Can you try to ADB Sideload the ASUS ROM?
Click to expand...
Click to collapse
Yes. I've tried every way to install.
Fusxda said:
Yes. I've tried every way to install.
Click to expand...
Click to collapse
Open a thread on ZenTalk: http://www.asus.com/zentalk/
Never heard about this OMNI SKU before.
If someone else has the same exact phone with you with a different SKU (perhaps WW?), you could try asking him to backup the recovery.img on his phone for you to flash. After that, just flash recovery via fastboot and you should be good to go.
up
Rizzed said:
If someone else has the same exact phone with you with a different SKU (perhaps WW?), you could try asking him to backup the recovery.img on his phone for you to flash. After that, just flash recovery via fastboot and you should be good to go.
Click to expand...
Click to collapse
Hello , do you find the solution i have the same problem
could you help me , thanx a lot :good:
2xboy said:
Hello , do you find the solution i have the same problem
could you help me , thanx a lot :good:
Click to expand...
Click to collapse
Stock recovery (and TWRP):
https://github.com/sabpprook/android_device_asus_ze500kl/releases
Guys I Found The Solution For This Problem :
1-Flash TWRP Recovery From The Link : https://github.com/sabpprook/android_device_asus_ze500kl/releases
2- Wipe Data and Cache And dalvik Cache and Very Important (Wipe System).
3-Flash Back The Stock recovery From The Same Link Above.
4-Flash Your .zip Stock Frimware From The Link : https://www.asus.com/support/Download/39/1/0/20/KsY29RCpsJ2bea9O/32/
5-Please if this Helped You Press Thanks! Button And Enjoy.
The Trick: Stock Recovery Cannot Wipe System But TWRP Can.
P.S: You Cannot Flash The Frimware From TWRP ... It Will Give An Error.
Enjoy
I find answer
Bro, download this file failobmennik.usite.pro/updater-script.noext and change \META-INF\com\google\android\updater-script
Hi,
I'll test it, and will give feed-back
Thanks