Database Info

[Q] Install CWM or unroot

I'm trying to install cwm or unroot my device so i can get the FOTA update installed but I haven't been successful
-NVflash doesn't work coz my transformer is B90
-using the recovery installer.apk gives me "problem praising the package"
-Installing cwm itself, gives me install successfully but I cant boot into recovery( I used the reboot into recovery app and volume +power)
-I tried installing a recovery touch .img using adb it didn't work(I couldn't get the device into fastboot
I'v been going at for 2 days now, this 5th device to root and use custom Rom's for but I m really stuck on this one. what I might be doing wrong, any help is appreciated. thanks

What firmware are you on?
"parsing error" is usually a bad download or not compatible with your firmware.

its
HRI66.us_epad-8.2.3.13-20110511
kernel 2.6.36.3

Yeah that's a pretty old firmware.
What method did you use to root it?
Try this thread.
http://forum.xda-developers.com/showthread.php?t=1106587

no luck with that one. I'm gonna try it again tomorrow on a diff pc.
the asus auto update fails every time I ran it, is that because of the device being rooted?

jado85 said:
no luck with that one. I'm gonna try it again tomorrow on a diff pc.
the asus auto update fails every time I ran it, is that because of the device being rooted?
Click to expand...
Click to collapse
Root only should be ok for ota update.
If you have custom recovery or delete any system apps ota update will fail

baseballfanz said:
Root only should be ok for ota update.
If you have custom recovery or delete any system apps ota update will fail
Click to expand...
Click to collapse
When I run the auto update it freezez and I have to erase the data and bypass linux boot or something like that, that's why Im trying to get cwm or unroot, i hate beeng stuck on this firmware.
Sent from my Transformer TF101 using xda premium

Do you have stock recovery? I also noticed you said +volume, It is -volume to get into recovery, just to confirm/make sure. If you have stock recovery you can try pushing an update.zip and using that, then flashing cwm on that updated firmware.

[Q] Rooting T-Mobile SG3

I installed the OTA for 4.1.2 and have not rooted my T-mobile T999 at all. I've watched videos that said it was for this firmware and model, but when I go into recovery mode and try to install the zip file, I get a message saying "E: Signature Verification Failed." SuperSU is on my phone, but when I try to launch it, it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!"
I've never rooted a phone before, but the videos I watched seemed really easy, but it's not working for me.
Can somebody post how to do it with the most updated G3rootsprint.zip file. Maybe I'm using one that's too old, or maybe since the update is only days old, it's not possible with the processes that are online already.

gstoliby said:
I installed the OTA for 4.1.2 and have not rooted my T-mobile T999 at all. I've watched videos that said it was for this firmware and model, but when I go into recovery mode and try to install the zip file, I get a message saying "E: Signature Verification Failed." SuperSU is on my phone, but when I try to launch it, it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!"
I've never rooted a phone before, but the videos I watched seemed really easy, but it's not working for me.
Can somebody post how to do it with the most updated G3rootsprint.zip file. Maybe I'm using one that's too old, or maybe since the update is only days old, it's not possible with the processes that are online already.
Click to expand...
Click to collapse
try disabling signature verification in your recovery

chromium96 said:
try disabling signature verification in your recovery
Click to expand...
Click to collapse
I can't even figure out how to do that!

gstoliby said:
I can't even figure out how to do that!
Click to expand...
Click to collapse
Which recovery are you using? In clockwordmod the option is located in the advacned menu

chromium96 said:
Which recovery are you using? In clockwordmod the option is located in the advacned menu
Click to expand...
Click to collapse
I'm attempting to root with clockworkmod, but since I can't get that far, it's the android recovery.

gstoliby said:
I'm attempting to root with clockworkmod, but since I can't get that far, it's the android recovery.
Click to expand...
Click to collapse
Use this guide to root the t999v. I used it a couple months ago and it works fine, and as a bonus it wont trip your flash counter.

chromium96 said:
Use this guide to root the t999v. I used it a couple months ago and it works fine, and as a bonus it wont trip your flash counter.
Click to expand...
Click to collapse
I'll have to give it a try when I get to my personal computer.

Unable to apply newest cricket OTA update

I have an unlocked bootloader and them routed, although I was unable to achieve s-off following any of the guides on this forum. When I try the OTA update, I get an error in CWM saying it was unable to flash the image and it was cancelled. I have tried it with signature verification enabled and disabled, with the same results.
Sent from my HTC One SV using Tapatalk now Free

zomgitsanoob said:
I have an unlocked bootloader and them routed, although I was unable to achieve s-off following any of the guides on this forum. When I try the OTA update, I get an error in CWM saying it was unable to flash the image and it was cancelled. I have tried it with signature verification enabled and disabled, with the same results.
Sent from my HTC One SV using Tapatalk now Free
Click to expand...
Click to collapse
The update to Jelly Bean i guess?
As long as you have cwm installed you will not be able to update. The OTA update is not for flashing in recovery!
You need stock boot.img, stock recovery and stock system partition to update.

Already on jb. Update 2.04.1050.5
I assume the same rules still apply, though?
Sent from my HTC One SV using Tapatalk now Free

zomgitsanoob said:
Already on jb. Update 2.04.1050.5
I assume the same rules still apply, though?
Click to expand...
Click to collapse
Ah, ok. Cricket gets also a small update.
Yes, the same rules as before

OTA installation aborted
I have bought this phone a couple of months ago and rooted it and have clockworkmod recovery 6.0.3.2 installed. The phone is running good and i have not had problems. However, I see that there is an OTA update for the version 2.04.1050.5. I tried installing the 15 mb file and it told me to restart the phone. When it does, it takes me to the clockworkmod Recovery thing and tells me the installation is aborted? What do I do? Do I really need this update or can I go without? Also, is this the update for the 4.2.2 Jelly Bean?
Any help is appreciated.

quickser4u619 said:
I have bought this phone a couple of months ago and rooted it and have clockworkmod recovery 6.0.3.2 installed. The phone is running good and i have not had problems. However, I see that there is an OTA update for the version 2.04.1050.5. I tried installing the 15 mb file and it told me to restart the phone. When it does, it takes me to the clockworkmod Recovery thing and tells me the installation is aborted? What do I do? Do I really need this update or can I go without? Also, is this the update for the 4.2.2 Jelly Bean?
Any help is appreciated.
Click to expand...
Click to collapse
that tiny update cab be accepted if you haven't deleted or modified ahh of the system.
if your s-on then you have to relock your bootloader
but first of all you need to flash the stock boot.img and stock recovery.img

How to update to newest bootloader and install custom ROM

I'm currently on a HYDRO ROM 4.1 and want to update to the newest bootloader and JB. I downloaded the latest ROM from ASUS but when I try to flash it via TWRP it just says failed before anything gets started. What steps to I have to take from where I am to get the latest and greatest?

Bagel Bear said:
I'm currently on a HYDRO ROM 4.1 and want to update to the newest bootloader and JB. I downloaded the latest ROM from ASUS but when I try to flash it via TWRP it just says failed before anything gets started. What steps to I have to take from where I am to get the latest and greatest?
Click to expand...
Click to collapse
Did u try using fastboot to flash it? Also dont forget to extract the ROM from the downloaded zip file.

I did not realize the ROM .zip file was inside the .zip file...
Thank you installing now. After that I just have to flash an updated recovery and then install an custom ROM, correct. You've been a great help.

Now TWRP says Successful but it didn't take but a couple of minutes and the log says "E:Unable to mount '/staging'
I assume it failed for some reason.

Bagel Bear said:
Now TWRP says Successful but it didn't take but a couple of minutes and the log says "E:Unable to mount '/staging'
I assume it failed for some reason.
Click to expand...
Click to collapse
Did you install the -42 TWRP since you are now on the 4.2 boootloader?

Ah I see. It did actually install the latest bootloader. I installed the latest TWRP but it seems that it can't see files from various partitions. I guess it can't mount them or something so I can't installed a custom ROM from my micro sd or anything. Any help for this problem?

Bagel Bear said:
Ah I see. It did actually install the latest bootloader. I installed the latest TWRP but it seems that it can't see files from various partitions. I guess it can't mount them or something so I can't installed a custom ROM from my micro sd or anything. Any help for this problem?
Click to expand...
Click to collapse
Did you mount the correct partition in the settings of TWRP. Try unmounting and then remounting what you need.

Even the log on TWRP says it is unable to mount anything on startup. When I try to exit TWRP it says that I am not rooted and prompts me if it can root for me. Can I do it this way?

Anyone know anything about this?

Bump

E:Error executing updater binary in zip

Anybody figure out how to fix this? I can find people having this problem flashing 4.4 but I can't flash anything. I've tried to flash mf1 firmware, a 4.3 carbon nightly, and a 4.3 pac nightly. All with the same results. Here is exactly what I did -
I flashed PhilZ recovery earlier on a earlier version of TWRP.
kept getting a "failed" in PhilZ
Flashed latest TWRP via Odin
Tried flashing the above mentioned zips all with the error message.
Restored my hyper drive rls16 backup (4.1.2)
Installed latest TWRP via goomanager app
Edit : my phone is flashed to PagePlus so I kinda have to be careful I'm afraid of using Odin to go back to stock/rooted but my luck that's what it'll take. When I get home I'm going to try it with a older version of TWRP that's the only other thing I can think to try.
Any suggestions or info is appreciated.

delete

anyone ? please ?

Supposedly the update binary here is generic, you could try replacing the one in the rom zip with it
http://forum.xda-developers.com/showthread.php?t=2492496
Sent from my SCH-I535 using XDA Premium 4 mobile app

I've tried CWM PhilZ and TWRP all latest versions, and still can't get rid of this.
I Cannot install any rom, whatsoever. I did manage to install a MF1 radio zip, but that's it. I can't install 4.3 or even 4.2 ..
I've replaced the update-binary inside the zips, and edited the update-script and removed the stuff used for recognizing the device, still no dice ..
I ended up flashing a full mf1 img via Odin and then used casual to root/unlock/recovery install - and I STILL get the error. Not sure where to go from here. Seems like nobody else is having this problem unless they're not on the latest recovery and trying to flash KitKat.
Thought I'd share the rest of my story ..
edit: I was able to restore a old backup of 1.7 carbon ...lol. better than nothing or a TW rom, that's for sure.

When you replaced the update binary did you get the same error or a different one? Also, have you tried flashing from internal and external SD?
Sent from my SCH-I535 using XDA Premium 4 mobile app

dpeeps74 said:
When you replaced the update binary did you get the same error or a different one? Also, have you tried flashing from internal and external SD?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry I didn't get a notification for this.
I did get the same error. I did get a error 6 once or twice but it was because I edited the update-script file and used word or word pad I downloaded note++ and it stopped and went back to error 7 :banghead:
Sent from my SCH-I535 using Tapatalk

cjmcsw87 said:
Sorry I didn't get a notification for this.
I did get the same error. I did get a error 6 once or twice but it was because I edited the update-script file and used word or word pad I downloaded note++ and it stopped and went back to error 7 :banghead:
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
OK, I have one for you to try, use the original rom zip (don't edit the update-script), when you flash in recovery and it failed, select boot and boot back into recovery, then reflash again. Try it with the latest TWRP 2.6.3.2.

SOLVED ! only took a week ...
I had been using an update-binary file that was posted in a thread.
I took the file from PhilZ recovery ( which I had been able to flash, just nothing else ) and used that one. Imagine that, it worked.
**DUH** :silly:

cjmcsw87 said:
SOLVED ! only took a week ...
I had been using an update-binary file that was posted in a thread.
I took the file from PhilZ recovery ( which I had been able to flash, just nothing else ) and used that one. Imagine that, it worked.
**DUH** :silly:
Click to expand...
Click to collapse
Nice, glad you have a happy ending!!

buhohitr said:
Nice, glad you have a happy ending!!
Click to expand...
Click to collapse
Me too buddy, let me tell ya ..
I appreciate the advice along the way. Thank you.
now I just have to decide if I want carbon or pac as my daily driver for awhile.. Carbon is what i've almost always used after I figured out how bloated and laggy TW is.. Best of all my PagePlus flash is perfectly fine, didn't have to add APN's or mess with anything else to get data to work.
I hope this thread helps somebody else.

I am having the same issue with HTC One.
Could you please let me know how you solved this. Maybe it can help with my device as well. had no luck in our threds..
Thank you

umka83 said:
I am having the same issue with HTC One.
Could you please let me know how you solved this. Maybe it can help with my device as well. had no luck in our threds..
Thank you
Click to expand...
Click to collapse
If you're getting a status 7 error you have to replace the update binary with the latest nightly from cm11 in anything you want to flash. The update binary is universal and will work on anything you want to flash. If it is throwing another error then this won't work.
This will probably only work with cwm or philz.

BadUsername said:
If you're getting a status 7 error you have to replace the update binary with the latest nightly from cm11 in anything you want to flash. The update binary is universal and will work on anything you want to flash. If it is throwing another error then this won't work.
This will probably only work with cwm or philz.
Click to expand...
Click to collapse
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU

umka83 said:
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
Click to expand...
Click to collapse
It's a recovery version problem, so either update your recovery or use an older one until you find something that works.

Problem Solved
umka83 said:
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
Click to expand...
Click to collapse
After conducting my own research with this same problem I discovered a much simpler method of correcting the issue. When flashing KK roms with older versions of custom recoveries, the recoveries did not have sufficient instructions to to handle some of the file system changes in KK. I tried replacing the updater binaries from multiple ROMs to no avail. After about 24 hours of trial and error I managed to successfully flash Cyanogenmod cm-11-20140709-NIGHTLY-d801 and GAPPs aokp_gapps-kk-20140517 to my LG G2 D801. All that had to be done is to update TWRP from 2.6.3.2 to version 2.7.1. This version of TWRP had the necessary instructions to support a KK version custom ROM.

Good Job
Sent from my SM-G900F using XDA Free mobile app

Fixed
buhohitr said:
Nice, glad you have a happy ending!!
Click to expand...
Click to collapse
I had same issue, installed newest TWRP. Fixed! Used Odin to install.

I had the same issue as the OP. I was trying to flash a rom from the external SD card. I moved it to the Internal SD and it worked.
J