I'm on 4.4 right now and I just reviewed the ota but when it finished downloading, it went stock recovery and just said "error". Obviously I was pissed so I then went the adb root but that wouldn't work either. Something about it not being able to find "update.zip" when it is clearly in the same folder. After that I decided to flash a custom recovery, not clockwork but the other one. Whenever I try to go that route it still says it failed. I have been looking at posts and none have helped so far.
I am rooted, I don't have busybox/xposed, I am using art. I read something about having to have all of the stock apps. I had a modded playstore on here but I didn't work so I re-download one and installed it, could that have anything to do with my problems? And if so, where can I find another playstore app?
also, this is what it says in the custom recovery: /system/framework/core-libert. Jar unexpected E:Error executing updater in zip I tried googling but to no avail.
That modded play store might have changed some system files that prevent the update. You can try flashing one of the stock 4.4.2 Roms available in the android development forums. I used the one by bigxie.
Sent from my Nexus 5 using Tapatalk
Thanks man. Should I use an odex or deoxdex? And what's the difference?
I have this problem too....i'm rooted and get the error logo when i try to update too.....
paulbadassbriant said:
I have this problem too....i'm rooted and get the error logo when i try to update too.....
Click to expand...
Click to collapse
Try what the guy who replied to me said, it worked for me
Related
I'm using the default ROM for my One X and I'd like to update it (I haven't since I got it 6 month ago); do I need to re-lock the bootloader and unroot it before I can use the OTA update? Also it's been a while since I even fiddled with my phones software so I forgot anything else I may have done, is there a way I can check to see what else has been done and if it's safe to update it?
Currently I have:
Android Version: 4.0.3
HTC Sense Version: 4.0
Software Number: 1.73.631.1
HTC SDK API Level: 4.11
HTC Extension Version: HTCExtension_403_1_HA_4
What firmware are u on currently for starters
Sent from my HTC One XL using xda app-developers app
I added the info to the original post
bman3k said:
do I need to re-lock the bootloader and unroot it before I can use the OTA update?
Click to expand...
Click to collapse
Your phone should be factory default before performing OTA updates or results may be unexpected.
Most OTA updates are patch file based and require the files to be exactly what is expected.
There have been known issues with root being detected and the OTA failing.
Rooted phones progressing with an update but root lost after the update.
System files being modified and the OTA failing.
Recovery must be factory; not TWRP or CWM.
CID and MID must suit OTA.
The only modification I would consider safe through all OTA's so far has been SuperCID.
If you have any interest in rooting and flashing custom ROMs, I would suggest rooting and unlocking the bootloader now, while you are on 1.73, and not updating via OTA. The latest 2.20 update will also update your hboot, which plugs the holes by which kernels and radios can be flashed from recovery.
Since you're with att you can expect the jelly bean update any time from now till the end of the world which isn't fun waiting for .. I'd suggest if you were rooted download goo manager flash twrp....than flash a solid ics Rom if your prefer ice sense or you can go venture into the jb realms
omario8484 said:
Since you're with att you can expect the jelly bean update any time from now till the end of the world which isn't fun waiting for .. I'd suggest if you were rooted download goo manager flash twrp....than flash a solid ics Rom if your prefer ice sense or you can go venture into the jb realms
Click to expand...
Click to collapse
Agree. If you are already BL unlocked and rooted, why go through the hassle of relocking the BL and returning to stock, just to wait for the OTA?
Just flash a JB ROM, as there are already stock and custom JB ROMs posted in Development.
Plus, until the OTA actually hits, we don't know if it will even be rootable. They have plugged the existing root exploits with every successive AT&T OTA for this phone so far. No reason to think any different for the JB update.
Just flash a JB ROM and stay rooted.
Ya I really like viper xl v3 . Just apply fix listed on op and you should be good to go
Sent from my HTC One XL using xda premium
Stock OTA is not WORTH IT IMO, been there
Reselling the phone is probably the only reason i'd revert to stock.
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
bman3k said:
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
Click to expand...
Click to collapse
Ok you're really lucky you didn't just brick your phone.... You want to stay in the att one x forums.... Notice theres a title diff. You're lucky it didn't succesfully flash or your phone would be dead... That's an international one x rom
bman3k said:
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
Click to expand...
Click to collapse
Stick to the ROM's in our forum, I never heard of anything like that ROM for our phone sorry. Lucky you didn't brick it
O damn I feel very stupid now...
Can someone recommend me a JB ROM?
Also how would I even install one now? The AR HD one was the only ROM I had on my SD card
Edit: I figured out the Mount function in TWRP, so I know how to add new ROMs now
bman3k said:
O damn I feel very stupid now...
Can someone recommend me a JB ROM? Also how would I even install one now? The AR HD one was the only ROM I had on my SD card
Click to expand...
Click to collapse
Try them all, they are all good, the time it takes to ask for other peoples opinions you could have test driven them all yourself.
Are you looking for jb sense?
omario8484 said:
Are you looking for jb sense?
Click to expand...
Click to collapse
I'm just going to try a couple like wrecker suggested now that I've figured out how to flash ROM's properly
Thanks for your guys' helps
Is there a way to back up my apps/texts and stuff when flashing ROM's? I totally forgot about that and lost all of it, I didn't have anything particularly important, but it'd be a hassle to redownload everything everytime. I had Titanium Backup, but that's not a recovery for if you reflash right?
bman3k said:
I'm just going to try a couple like wrecker suggested now that I've figured out how to flash ROM's properly
Thanks for your guys' helps
Is there a way to back up my apps/texts and stuff when flashing ROM's? I totally forgot about that and lost all of it, I didn't have anything particularly important, but it'd be a hassle to redownload everything everytime. I had Titanium Backup, but that's not a recovery for if you reflash right?
Click to expand...
Click to collapse
Funny that you bring titanium up...titanium helps you back up apps it also backs up your app data...and for sms just download something from the market here's one download the app super backup and you can backup your sms
So I installed Cyanogen 10.0.0 but it didn't come with Google Play so I installed Gapps as well; now I keep getting the "Android Keyboard ASOP has stopped working" and I can't do anything. I've tried multiple versions of Gapps but they all give the error. I've also tried installing a keyboard apk on it's own but I am still unable to type anything.
Edit: Also when I downloaded Google Play as an apk separately it would crash immediately, but when I installed it from Gapps it was ok.
bman3k said:
So I installed Cyanogen 10.0.0 but it didn't come with Google Play so I installed Gapps as well; now I keep getting the "Android Keyboard ASOP has stopped working" and I can't do anything. I've tried multiple versions of Gapps but they all give the error. I've also tried installing a keyboard apk on it's own but I am still unable to type anything.
Edit: Also when I downloaded Google Play as an apk separately it would crash immediately, but when I installed it from Gapps it was ok.
Click to expand...
Click to collapse
You did a full wipe before hand right?
I did the factory, system, cache and dalvik cache wipes
Edit: I got it to work, not really sure what I did different =/
I am a new member to XDA, though I have been to this site countless times before, and finally thought it was about time to join. I am not a noob to rooting or flashing or any of that-though I am still learning.
I have come across a problem and need help. I have a T-Mobile SGS III SGH-T999 and was running 4.1.2 Axis M rom, but I decided try something else. I've been searching for a good debloated stock touchwiz rom with the latest update, but until I find one I wanted to try something I found called JellyBam. Right now I'm back to 4.1.1 stock-I made a rooky mistake and had to reroot, just fyi.
I downloaded the latest JellyBam from get.jellybam.com and flashed it but all I got was, "status (7) error, Installation Aborted". I found out that "status (7)" happens when the phone checks to make sure the rom is compatible and the way to fix it is delete the line of coding above "show progress" in the "updater-script" file that causes the phone to check for compatibility and rezip the package and flash it. When I flash it now, it doesn't check for it to be compatible, which is good, so it goes straight to install. This time I don't get the "status (7) error" but it still aborts installation and I can't find out what's wrong.
I stopped trying to figure out how to get it to work. I just couldn't figure out what's wrong, I kept getting "status 7" and then "status 6"-and I have no clue what that one is-so I went with a rom my father used and I love it. I went with the inFAMOUS rom.
I would still appreciate some help with that whole "status 6/7" problem if anyone knows. Also, if anyone knows of a good debloated touchwiz rom that has the latest 4.2.2 or 4.2.1 tell me cause I've been searching for one and can't find one I like. I would like one that gets the latest updates.
Thanks.
Nexus 9.
Running M preview 2, clean flashed a few days ago. Rooted, TWRP installed, ElementalX kernel. I just started getting this message on the splash screen during boot.
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co/ABH"
It boots fine and works fine. No other symptoms, at all.
Does anyone know what this is?
I searched XDA and did a more general Google search and found nothing.
Thanks, in advance.
Having the same issue except it doesn't boot. I've had it unlocked for a while. Just flashed M v2 yesterday. Wanted to root just now. Ran "sh root-mac.sh" and started getting this error.
joehouin said:
Having the same issue except it doesn't boot. I've had it unlocked for a while. Just flashed M v2 yesterday. Wanted to root just now. Ran "sh root-mac.sh" and started getting this error.
Click to expand...
Click to collapse
same problem here.... only on my nexus 6. Anybody have a solution?
i found a solution download Nexus root toolkit v2.0.5.
download the preview v.2
Use Flash stock+ Unroot
Flash it again and you fine..
to enable fastboot, but you mobile in bootloader!!
pricedpizza said:
same problem here.... only on my nexus 6. Anybody have a solution?
i found a solution download Nexus root toolkit v2.0.5.
download the preview v.2
Use Flash stock+ Unroot
Flash it again and you fine..
to enable fastboot, but you mobile in bootloader!!
Click to expand...
Click to collapse
Hello, do you mind sharing the link to preview 2, i googled it but didn't see an exact mention of "preview v.2"
Is it one of the ones found on this link?
https://developers.google.com/android/nexus/images#shamu
Thanks in advance,
Julian
I have this same message on my Nexsus 6. Neither Google, Motorola or Sprint can help me get my phone to turn on again. It's past the one year warranty, so no one will replace it. Can anyone help me?
cam30era said:
Nexus 9.
Running M preview 2, clean flashed a few days ago. Rooted, TWRP installed, ElementalX kernel. I just started getting this message on the splash screen during boot.
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co/ABH"
It boots fine and works fine. No other symptoms, at all.
Does anyone know what this is?
I searched XDA and did a more general Google search and found nothing.
Thanks, in advance.
Click to expand...
Click to collapse
I hit the same message loading CM13 on a Nexus 9. Google explains here - support.google.com nexus answer 6185381? I wiped all partitions and loaded stock Marshmallow - the error disappeared. After re-flashing TWRP 3.0.2 the "corrupt" error came back. I then rooted with BETA-SuperSU-v2.66 which got rid of the error. Have since added Google account, updated apps etc. Still booting without error.
So would you say twrp is the reason it gives that error? I rooted my phone today, but when I went to my recovery to check to see if I indeed had a nandroid back up, I didn't... I made one using titanium backup, but didn't show in twrp. Anyhow, about that error message... I didn't know what to do after I had the pop up error message so many times... so i just unrooted my Nexus 6p. I really would like to keep my phone rooted, but I didn't like seeing that concerning error message. Any ideas of what I can do. I would be starting from scratch again. Any links would help! Thank you in advance.
(this belongs elsewhere but 10 posts...)
I have a rooted S4 and just installed Dandvh's Google Play Edition v.20150919 (http://forum.xda-developers.com/showthread.php?t=2539361) rom. I used TWRP to install, wiping everything but internal storage, then flashed the rom. Installed fine, no errors. Took the usual bit of extra time to boot the first time then up and running clean and stable. The issue is that the OTA Updater app doesn't work, severely limiting my ROM options. It didn't install as part of the rom install, though I'm not sure if it's normal to just get it off the play store. I get an error message about not being compatible with the ROM and can't access it (error message screen cap below). Just in case, I wiped the phone and flashed again just to be sure, same result. The OTA Updater is important as this is where you can change kernals, audioFX stuff, toggle advanced power menus, and quite a bit more. When I used this ROM during the first part of the year OTA Updater worked just fine but I switched off in July to try another ROM so maybe something with the ROM has changed? I tried searching for any comments in the thread to indicate either that something changed with OTA Updater or if anyone else had a similar problem, found nothing. Would appreciate if anyone might know why OTA Updater isn't working or how I might correct it. Thanks.
Edit #1: I haven't changed the model number to SGH-M919 (as seen in the screen cap) in build.prop yet as if I can't get this ROM to work right I'll need to flash something else.
Edit #2: I noted in the patch notes that the ROM was updated for OTA Updater 2.4.2 and I was running 2.5.3 so I uninstalled it and installed 2.4.2. No luck there either.
Version and Build Screenshot
https://imgur.com/SQ6ie5i
Error message
https://imgur.com/TfWN7p2
Hey folks. I am trying to get the hang of messing around with my android device. I am quite good with Windows/Linux, so this is the next frontier. So here is my problem: I am trying to update my TF101 to 5.1 and the installation failed. I installed Clockwork Recovery v3.2.0.1 and it worked well, I can get into recovery no prob. I installed the kitkass 5.1 on the SD card, the Update-Super-v2.46, and Katkiss_5.1_030c.
When I trying to install from zip the Katkiss I get this error:
set_metadata_recursive: Some changes failed.
E:error in sdcard/Kitkass/Katkiss-5.1_030c.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I am a bit stumped. Did I download a bad copy? I can't get into the TF101 at this point except for recovery. When I try, it just stays on the ASUS splash page.
I am sure this has been asked before, but I couldn't find any threads with this issue. Any help is appreciated.
xa3phod said:
Hey folks. I am trying to get the hang of messing around with my android device. I am quite good with Windows/Linux, so this is the next frontier. So here is my problem: I am trying to update my TF101 to 5.1 and the installation failed. I installed Clockwork Recovery v3.2.0.1 and it worked well, I can get into recovery no prob. I installed the kitkass 5.1 on the SD card, the Update-Super-v2.46, and Katkiss_5.1_030c.
When I trying to install from zip the Katkiss I get this error:
I am a bit stumped. Did I download a bad copy? I can't get into the TF101 at this point except for recovery. When I try, it just stays on the ASUS splash page.
I am sure this has been asked before, but I couldn't find any threads with this issue. Any help is appreciated.
Click to expand...
Click to collapse
I have this devices some were in a drawer lol anyways sounds like u mave have downloaded a bad copy try redownloading and get a md5 checker and check it. Also did you make a back up in twrp? If so could restore that in time being. Have a read trew kitkass thread agin and see if you missed any thing i know i had that rom running at one point but went back to kitkat cuz it was more stable.
Thanks for the help. I think I had a bad copy and a redownload fixed the issue. Android 5.1 is on the device and it sort of works. Well, not really. It runs poorly, reboots a lot and now it actually reboots before I can log in. I think I should hit a lower version of Android. Any suggestions on which version works best on the TF101? As of now its not usable.
Also, if I go to say, 4.4, can I use the same gapps-Katkiss-5.1 or do I need a correct version for 4.4? Can I just install it over 5.1 or do I need to wipe the device and start from scratch?
Again, thanks for the help.:good:
I tried to install 4.0.3, the official TF101 image from Asus but it wouldn't install. How do I go back to stock?