I tried flashing the renovate rom to my sprint one and got a kernal error at the end and it would not boot. I somehow also managed to wipe everything off the phone including the backup so i can even go back to stock. I tried pushing a rom via adb but i can get that to work and when i try use fastboot it says failed and i get a signature verified error. I am really starting to panic because i spent all of last night trying to find a solution and was unsuccessful. I also tried flashing using the ruu but it was unsuccessful but im pretty sure thats because i am on the 1.31 ota and it was a 1.29 ruu because i cant find a 1.31 ruu. Any help would be greatly appreciated.
which recovery do you have installed? if you have TWRP, you could try adb sideloading a ROM.... in TWRP, choose Advanced/ADB Sideload. then you send the ROM to the phone from your computer with 'adb sideload <rom name>.zip'.
if you don't have TWRP installed maybe you can install it from fastboot. there are probably other solutions too, but hopefully this would work. good luck!
Did you relock the bootloader before you tried the RUU?
SO I wiped my whole internal memory after creating a backup of my rom and trying to flash a new one. I quickly press to wipe and I guess i picked to wipe my internal memory too. So now I have No OS on the phone and nothing on the card to flash.
I tried ADB Sideload and all i got it was can't mount system, and cach..Samething happens if I try to backup or mount
I tried to send my zip file through fastboot with the "fastboot flash data " command but at the end I get a failed bootloader checking and I tried the same with system and nothing happen or I count find my zip file when I went back to recovery.
SO can someone help me fix this ? or Is there an RUU i can use?? my phone Hboot is 1.55 and came with Android 4.3 so idk if any old RUU will work
Oh and ADB dont some to work ...I get an error telling that it can't find devices.
pimix2009 said:
SO I wiped my whole internal memory after creating a backup of my rom and trying to flash a new one. I quickly press to wipe and I guess i picked to wipe my internal memory too. So now I have No OS on the phone and nothing on the card to flash.
I tried ADB Sideload and all i got it was can't mount system, and cach..Samething happens if I try to backup or mount
I tried to send my zip file through fastboot with the "fastboot flash data " command but at the end I get a failed bootloader checking and I tried the same with system and nothing happen or I count find my zip file when I went back to recovery.
SO can someone help me fix this ? or Is there an RUU i can use?? my phone Hboot is 1.55 and came with Android 4.3 so idk if any old RUU will work
Oh and ADB dont some to work ...I get an error telling that it can't find devices.
Click to expand...
Click to collapse
I have had the issue of ADB unable to find devices. Don't know if this will help you, but has worked for me. Make sure phone if powered off. Hold the volume down button and press and hold the power button in order to boot into bootloader. Then plug your phone into the computer. You should see the screen change to Fastboot USB. From my experience, that is where you need to be.
YMMV. Good luck.
pimix2009 said:
SO I wiped my whole internal memory after creating a backup of my rom and trying to flash a new one. I quickly press to wipe and I guess i picked to wipe my internal memory too. So now I have No OS on the phone and nothing on the card to flash.
I tried ADB Sideload and all i got it was can't mount system, and cach..Samething happens if I try to backup or mount
I tried to send my zip file through fastboot with the "fastboot flash data " command but at the end I get a failed bootloader checking and I tried the same with system and nothing happen or I count find my zip file when I went back to recovery.
SO can someone help me fix this ? or Is there an RUU i can use?? my phone Hboot is 1.55 and came with Android 4.3 so idk if any old RUU will work
Oh and ADB dont some to work ...I get an error telling that it can't find devices.
Click to expand...
Click to collapse
If you want to sideload you'll need TWRP recovery. Here's a guide. http://forum.xda-developers.com/showthread.php?t=2318497 I myself had trouble finding my device, but than I uninstalled all the HTC drivers I had and installed the "universal naked driver" from here http://forum.xda-developers.com/showthread.php?t=2263822
I have the exact same thing I can't save a ROM to the device to flash it anymore I just want it to go back to stock I don't want root anymore it never works. My bootloader version is 3.04.651.2 which is too high to use the RUU installer. I can't mount the storage to use any of the S-Off Tools to downgrade it. I can't even push files using adb. All because of a ROM....
Sirricharic said:
I have the exact same thing I can't save a ROM to the device to flash it anymore I just want it to go back to stock I don't want root anymore it never works. My bootloader version is 3.04.651.2 which is too high to use the RUU installer. I can't mount the storage to use any of the S-Off Tools to downgrade it. I can't even push files using adb. All because of a ROM....
Click to expand...
Click to collapse
If you dont have a custom recovery make sure you flash one thru bootloader, fastboot. Regardless of you Hboot or bootlaoder number, you can get it unlock at the htcdev.com website. then you have to flash TWRP recovery. After doing then go to recovery....Don't do anything yet, make sure that you computer recognizes your phone. THATS the mistake I made. Open device manager and look for android USB devices if its not there then you need to install the adb drivers. If its there then on TWRP recovery look for adb side... I think its under advance .... then open the command to tour adb folder and type "adb version" you need at least 1.0.21 or higher. then type adb sideload name of rom.zip
okay so i went through a bit of problems, and now i can only access recovery/bootloader because the rom i originally flashed messed up for some reason
anyways, im in recovery i use : adb push rom.zip /sdcard/rom.zip
it works i get the rom
i got to install from sd card
and when i flash the rom i get the error unable to open zip file. i also tried sideload but to avail.
any suggestions?
using TWRP, S-off , unlocked.
trying to flash a 4.4 rom
EDIT:::
after pushing loads of times, i guess the rom pushed correctly, anyways i try to flash here's what i get:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip
for 4.4 roms you need twrp 2.6.3.3
baadnewz said:
for 4.4 roms you need twrp 2.6.3.3
Click to expand...
Click to collapse
ah im using 2.6.3.0 at the moment, ill try getting 2.6.3.3 and seeing if it works
thanks in advance!
EDIT: IT WORKED! thanks so much
so I used the all in one tool and followed the steps to unlock successfully. Then I tried to install a ROM leaving S-On and it failed. Now I'm stuck Unlocked, S-on and I can't seem to install any custom roms and I can't use the RUU utility because I'm S-On.
I have tried loading numerous ROMs via sideloading both in TWRP and CM and they keep failing giving me the following error about halfway through:
* failed to write data 'protocol fault (no status)' *
I can hard reset and get into the bootloader just fine, and since it's unlocked I can push recoveries, but I can't seem to make anything else work at this point.
Is there a way to gain s-off with Firewater using just ADB at the bootloader? or is there another way to gain s-off?
Or is there a way I can just go back to stock and start over?
Thanks again for the help in advance!
Need more info.
What roms are you trying to flash?
Are you checking the MD5 to make sure they are good downloads?
As far as I know there is not an official version of CWM recovery.
Have you tried pushing a rom while booted to recovery?
Code:
adb push ROMname.zip /sdcard/
BD619 said:
Need more info.
What roms are you trying to flash?
Are you checking the MD5 to make sure they are good downloads?
As far as I know there is not an official version of CWM recovery.
Have you tried pushing a rom while booted to recovery?
Code:
adb push ROMname.zip /sdcard/
Click to expand...
Click to collapse
I've been trying all of the roms while sideloading while in recovery.
Viper: http://forum.xda-developers.com/showthread.php?t=2715224
Renovate 3.0: http://forum.xda-developers.com/showthread.php?t=2748512
Bad Boyz 1.1 : http://forum.xda-developers.com/showthread.php?t=2729170
Tried TWRP 2.7.0.2 official.
and TWRP 2.7.0.7 from Captain Throwback: http://themikmik.com/showthread.php?16278
I'm also getting errors when running the sideloads about mounting the partitions when sideloading in 2.7.0.7:
"E:Unable to mount '/data'"
"E:Unable to mount internal storage"
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!!!