Hello all,
On my htc one whenever i try to install a rom I am greeted with the following error message.
"E:Error executing updater binary in zip '/usb-o" So far I have tried 6 different roms, all to no avail. I am trying to install a rom because I accidentally wiped the system partition, causing my os to be deleted(woops). Ever since this occured I have been unable to connect my phone to a computer. I can still charge the phone and the phone appears in windows explorer, but gives an error message when i try to access the files. I have seen in on other thread, that the guy(who was also unable to install roms) changed his version of twrp to an older version, but I dont know if this is possible to do in twrp recovery mode.
Thanks in advance
Atheos
Hello all,
Since my TF701T returned from RMA (touch screen issues), it has drained the battery like hell.
So I decided to flash original firmware again (done that before sending it), only to find out it now failed with this error:
Verifying update package...
E:failed to open /sdcard/T4_SDUPDATE.zip (No such file or directory)
So I renamed the zip to that file, but it didn't help.
This package is for "K00C" devices; this is a "tf701t"
In custom recovery log, one can find this:
ro.build.product=tf701t
ro.product.device=tf701t
Installed CWM, then flashed 2 custom ROMs (CROMbi KK and last AOKP), either system is stuck on boot or systemui fails permanently preventing using the tablet.
Then I flashed the original firmware with CWM instead of stock recovery, system stuck on boot-loop, except with 11.4.1.17, boot up but systemui fails again.
It's like the tablet Asus sent me back is not really a TF701T ?
Any help would be highly appreciated as the tablet is unusable at the moment, only boot-loader and stock/custom recovery are accessible.
Can you provide a logcat of the boot process from an adb connection please. Also the recovery.log from cwm (it's in /tmp/recovery.log so adb pull /tmp/recovery.log recovery.log)
It sounds like your system partition is not getting setup correctly or /data is corrupted somehow.
Also for stock you have to flash the zip inside the zip - you did do that right?
Let me get this straight:
You are on the 11.4.1.17 bootloader? That would mean you had the latest stock 4.4.2 firmware installed right?
The T4_SDUPDATE.zip is WW JB 4.3 firmware, is it not? You tried to flash that in stock recovery?
I read about one user who tried to downgrade from 4.4.2 to 4.3 yesterday and that also failed.
Another user contacted Asus support and they told him a downgrade is not possible from 4.4.2. No idea if that is true. The Asus reps are not always well informed....
sbdags said:
Can you provide a logcat of the boot process from an adb connection please. Also the recovery.log from cwm (it's in /tmp/recovery.log so adb pull /tmp/recovery.log recovery.log)
It sounds like your system partition is not getting setup correctly or /data is corrupted somehow.
Also for stock you have to flash the zip inside the zip - you did do that right?
Click to expand...
Click to collapse
berndblb said:
Let me get this straight:
You are on the 11.4.1.17 bootloader? That would mean you had the latest stock 4.4.2 firmware installed right?
The T4_SDUPDATE.zip is WW JB 4.3 firmware, is it not? You tried to flash that in stock recovery?
I read about one user who tried to downgrade from 4.4.2 to 4.3 yesterday and that also failed.
Another user contacted Asus support and they told him a downgrade is not possible from 4.4.2. No idea if that is true. The Asus reps are not always well informed....
Click to expand...
Click to collapse
Thanks for replying. Turns out I made a series of misleading mistake
First: custom recovery was installed, so it would not install an original firmware (device identifier incorrect, k00c while expecting tf701t).
Second: tried installing a custom ROM using Aroma, but the full wipe option didn't worked and ROM would boot loop!
Third: started using a modified ZIP of the original firmware without device identifier check, which was not allowed to install in stock recovery.
Bootloader was still on 10.26, however the closest thing to work was to flash original 11.4 firmware in CWM
At the end I use the original firmware ZIP and copied it to /sdcard/S4_SDUPDATE.zip, flashed stock recovery, and it installed flawlessly. That's when I realized the full wipe never occurred, all data where still there!
Hi guys, I've been working on my ATT m7 for a day or so now.
Story:
I was on CWM recovery and CyanogenMod 11 M7 without any issues for a long time, rooted, S-OFF, etc. Phone all of a sudden got a bunch of force closes and errors such as "com.google.gapps has encountered an error and needs to close" it would repeatedly appear. I tried killing apps, force closing apps, etc to no avail.
I restarted the phone and it froze on the HTC logo. Hard reset, same thing. Wouldn't go past HTC logo. No big deal, went into recovery, cleared cache, Dalvik, reboot, hangs on HTC logo. Kept trying this, same result. Decided to just factory wipe and try that. Used adb to pull my files off the phone, then factory wiped, still no luck, hangs on HTC logo. Tried reflashing previously working CyanogenMod zip, no luck.
Flashed TWRP recovery and tried all of the above again, still no luck. Strangely, TWRP says it looks like my phone is not rooted and asks to install su. I verified root through adb shell, but TWRP still reports no root. Also verified in TWRP going to console and "whoami" gives "root" so not sure what's going on there.
Tried an RUU that looked like it was working, but then randomly failed out ERR 155.
Then I just happened to notice my bootloader says I now have S-ON! Wtf?
Not really sure what to try at this point, you guys have any suggestions?
Edit:
Just tried flashing a stock ATT Sense OTA zip but TWRP gives errors:
Full SELinux support is present
E: Unable to mount '/cache'
E: Unable to mount '/cache'
MTP Enabled
Installing '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Error flashing zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Updating partition details
E: Unable to mount '/cache'
eguh.
wingman358 said:
Hi guys, I've been working on my ATT m7 for a day or so now.
Story:
I was on CWM recovery and CyanogenMod 11 M7 without any issues for a long time, rooted, S-OFF, etc. Phone all of a sudden got a bunch of force closes and errors such as "com.google.gapps has encountered an error and needs to close" it would repeatedly appear. I tried killing apps, force closing apps, etc to no avail.
I restarted the phone and it froze on the HTC logo. Hard reset, same thing. Wouldn't go past HTC logo. No big deal, went into recovery, cleared cache, Dalvik, reboot, hangs on HTC logo. Kept trying this, same result. Decided to just factory wipe and try that. Used adb to pull my files off the phone, then factory wiped, still no luck, hangs on HTC logo. Tried reflashing previously working CyanogenMod zip, no luck.
Flashed TWRP recovery and tried all of the above again, still no luck. Strangely, TWRP says it looks like my phone is not rooted and asks to install su. I verified root through adb shell, but TWRP still reports no root. Also verified in TWRP going to console and "whoami" gives "root" so not sure what's going on there.
Tried an RUU that looked like it was working, but then randomly failed out ERR 155.
Then I just happened to notice my bootloader says I now have S-ON! Wtf?
Not really sure what to try at this point, you guys have any suggestions?
Edit:
Just tried flashing a stock ATT Sense OTA zip but TWRP gives errors:
Full SELinux support is present
E: Unable to mount '/cache'
E: Unable to mount '/cache'
MTP Enabled
Installing '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Error flashing zip '/sdcard/TWRP/ATT_Sense6_OTAPkg.zip'
Updating partition details
E: Unable to mount '/cache'
eguh.
Click to expand...
Click to collapse
you can not flash OTA, these are patches, not complete rom and when flashed over the appropriate rom version, must be done using stock recovery, not twrp.
What version of twrp are you using? CM11 need block:by-name support in the recovery kernel.
For your s-on issue, you probably have used 'fastboot oem writesecureflag3' command by mistake
alray said:
you can not flash OTA, these are patches, not complete rom and when flashed over the appropriate rom version, must be done using stock recovery, not twrp.
What version of twrp are you using? CM11 need block:by-name support in the recovery kernel.
For your s-on issue, you probably have used 'fastboot oem writesecureflag3' command by mistake
Click to expand...
Click to collapse
Thanks for the info... do you recommend trying a stock rom or CM11? I'm on the latest TWRP, it's v2.8.0.2.
And regarding the command 'fastboot oem writesecureflag3' I've never seen it before, and certainly haven't issued it by hand. Whether the command was issued by some tool or file I've tried, I don't know.
EDIT:
I think the reason for the RUU failure may be due to the version, I believe it was trying to flash 1.xx over 3.xx. Does that sound right? Also, is it correct that I need stock recovery and locked bootloader for a RUU??
wingman358 said:
Thanks for the info... do you recommend trying a stock rom or CM11? I'm on the latest TWRP, it's v2.8.0.2.
And regarding the command 'fastboot oem writesecureflag3' I've never seen it before, and certainly haven't issued it by hand. Whether the command was issued by some tool or file I've tried, I don't know.
EDIT:
I think the reason for the RUU failure may be due to the version, I believe it was trying to flash 1.xx over 3.xx. Does that sound right? Also, is it correct that I need stock recovery and locked bootloader for a RUU??
Click to expand...
Click to collapse
Well somehow I was able to flash a stock ROM ([ROM][4.4.2] - AT&T 4.18.502.7 Stock Rooted from this thread). Then flashed PA_gapps over (with dalvik and cache wipe before and after flashes).
On boot, it cleared the HTC logo (finally!). Then it hit me with "Google search has stopped unexpectedly" and goes back to the HTC logo... wtf... then it popped up "Dialer has stopped unexpectedly"... then the home screen came up, and it rebooted itself.
After rebooting, I swiped to unlock the screen and it showed the dreaded white HTC logo... ugh, then it hits me in quick succession with "Hangouts has stopped" "Google Play Music has stopped" "Youtube has stopped" and so on. If I hit the screen off button then turn it on, it showed the lock screen. The lock screen seemed fine, the clock worked, and swiping to unlock worked, but when it unlocked instead of the home screen it showed the white HTC logo. Eventually it rebooted itself. After I think the third time rebooting itself, the android setup/configuration came up. "_____ has stopped" keeps popping up.
I was able to restore contacts and stuff by signing into my google account, but I am almost continually getting "_____has stopped" pop-ups, and if I let the phone sit for a few minutes it reboots itself maybe every 5 minutes or so. Also I don't think I have cell service (it just shows an X with no bars). It seems normal aside from those (not much home screen lag, apps open, wifi seems to work).
I did a permissions fix from recovery which completed without errors, but it didn't seem to help.
wingman358 said:
Well somehow I was able to flash a stock ROM ([ROM][4.4.2] - AT&T 4.18.502.7 Stock Rooted from this thread). Then flashed PA_gapps over (with dalvik and cache wipe before and after flashes).
Click to expand...
Click to collapse
Why flashing gapps over a stock sense rom?
alray said:
Why flashing gapps over a stock sense rom?
Click to expand...
Click to collapse
Great question... I've been in the habit of always flashing gapps after flashing rom, does gapps come with stock rom??
wingman358 said:
Great question... I've been in the habit of always flashing gapps after flashing rom, does gapps come with stock rom??
Click to expand...
Click to collapse
Yes, wipe everything and reflash the rom
alray said:
Yes, wipe everything and reflash the rom
Click to expand...
Click to collapse
That did it! Wiped, reflashed, and no more force closes, not one. Thanks a bunch alray!!!
Hello everyone,
I´m using the s3mini i8190 and i´m in a bootloop. I read on other sites that i should go into download mode and use odin, problem: I can´t get into download mode (or recovery mode). The last thing i did was flashing GApps after i flashed an aosb rom without GApps. after that i think i flashed a bad zip(I wanted to flash titanium backup into the system), because it gave the error :
Code:
Flashing failed
E: Can't mount data
E: Can't mount system
after that i went into the advanced menu of twrp to manually mount data and system, which didn't work.
so, basically i'm stuck with a bootloop without being able to go into download mode.
I hope I've given enough information
Any suggestions?
Hi there, so i was on firmware b386 and i tried to install other ROM i can't remember now, but i think i messed something up because i erased everything and now when i try to flash any ROM, for example Bluewei 4.1 it tells me that "Failed to mount /vendor" and "Failed to mount /product"
I have bootloader unlocked and latest twrp installed, anyway what can i do to fix this please?
hfmls said:
Hi there, so i was on firmware b386 and i tried to install other ROM i can't remember now, but i think i messed something up because i erased everything and now when i try to flash any ROM, for example Bluewei 4.1 it tells me that "Failed to mount /vendor" and "Failed to mount /product"
I have bootloader unlocked and latest twrp installed, anyway what can i do to fix this please?
Click to expand...
Click to collapse
There's a lot of threads about this. It's probably broken.
https://forum.xda-developers.com/p9/help/unable-to-mount-vendor-product-version-t3578596 <-one of these