Unlocked bootloader. Rooted. S-ON. TWRP (then flashed to CWM to see if that would work).
I tried flashing a Android Revolution but kept getting error messages so I formatted but like an idiot formated /system/ so now I'm in a bootloop that sends me back to recovery.
I've tried adb sideloading about five different roms, even stock, but I keep getting the error messages "failed to open driver control: no such file or directory" and then "E: can't open /tmp/update.zip (bad)" when installing.
Can anyone help me out? I don't have any nandroid back ups to fall back on because like mentioned before... I'm an idiot. Thank you in advance to whoever is willing to help out.
Classick206 said:
Unlocked bootloader. Rooted. S-ON. TWRP (then flashed to CWM to see if that would work).
I tried flashing a Android Revolution but kept getting error messages so I formatted but like an idiot formated /system/ so now I'm in a bootloop that sends me back to recovery.
I've tried adb sideloading about five different roms, even stock, but I keep getting the error messages "failed to open driver control: no such file or directory" and then "E: can't open /tmp/update.zip (bad)" when installing.
Can anyone help me out? I don't have any nandroid back ups to fall back on because like mentioned before... I'm an idiot. Thank you in advance to whoever is willing to help out.
Click to expand...
Click to collapse
1- for 4.4 ROMs you need TWRP 2.6.3.3 or higher
2- adb sideload how to: http://forum.xda-developers.com/showthread.php?t=2317986
3- or you can use "adb push <name of rom>.zip /data/media/0/"
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
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
I used WugFresh's awesome Nexus Root Toolkit to unlock, root and install custom TWRP recovery. I have 2.8.2.1 version installed. I am unable to do any tasks with this TWRP, however. It throw error when I try to Wipe Cache, make backup or anything else for that matter.
I tried to update using fastboot but I haven't figured that part out yet.
Can anyone provides some assistance as to what the cause of error could be? I am on 5.0.1 build, encrypted.
Thanks
Try:
Code:
fastboot flash cache cache.img
From your 5.0.1 factory image, keep extracting until you see all the .img files including cache.img.
I didnt have any issues with 2.8.2.1 but i have since switched to 2.8.2.0 since its the official version.
Download 2.8.2.0 from their website. Boot into bootloader and type fastboot flash recovery recovery.img where recovery.img is the downloaded twrp file.
I was able to flash cache.img, but TWRP is still giving error when I try to do any action. It keeps saying unable to mount storage.
JManekia said:
I was able to flash cache.img, but TWRP is still giving error when I try to do any action. It keeps saying unable to mount storage.
Click to expand...
Click to collapse
Flash the 2.8.2.0 twrp img
Thanks. It was the encryption doing its job. I had to put in the password to get it going. Appreciate all the help here
I can't seem to flash new ROMs - get an error message "E:Error executing updater binary in zip". Tried both slimRom and Liquidsmooth
I'm rooted on 5.0, decrypted, busyboxed, with the latest TWRP v2.8.2.1. Any ideas?
Any ideas?
I'm having the same issue, did you ever get it resolved?
i am also having this issue....I have a thread going. "HELP i cannot flash any custom roms"
The TWRP 2.8.3 is out and has been for a little while I would try the newest version (the one I said above) it seems to be working better for me than the earlier ones.
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