Hello everyone on XDA,
Ive try rooting my HTCONE on Sprint. S-OFF ,did flash ClockworkMod latest .img than i flash SuperSU.130. i was already on 4.3 android .. everything went well but when i open my SuperSU an error pop up "there is no binaries installed, su cannot installed it, there is problem to it". i did some further research, it seeem i flash an outdated SuperSU. aftewards i downloaded the latest SuperSU 1.65. Try to flash it in recovery, for some reason it aborted the command. than ive try a earlier release supersu1.43 . Same problem it will abort the command. than i switch to TWRP latest image . try doing the same and it still fails. ive also try -viperboys- method it did the same thing it aborted the command of flashing any type of zip files.
im stuck can proceed further . what can i do so i could get fully rooted.
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!!!
Hi there
If anyone can help me with this I would appreciate. I'll try to keep it short.
I have a HTC mini 2 and a few months ago installed TWRP and cyanogen.
Basically I followed the instructions from wiki.cyanogenmod.org.
One day the phone started to make reboots by itself until it got stuck in cyanogen boot logo.
I tried to install cyanogen again using TWRP but it kept failing. Wipe gave messages of "unable to mout data \ cache \ internal storage"
I decided to install a new version of TWRP and now every time I go to recovery, it boots back to bootload.
I tried to flash different versions of TWRP with the same result.
The phone is unlocked, S-ON.
Any ideas anyone?
dOeVENTS said:
Hi there
If anyone can help me with this I would appreciate. I'll try to keep it short.
I have a HTC mini 2 and a few months ago installed TWRP and cyanogen.
Basically I followed the instructions from wiki.cyanogenmod.org.
One day the phone started to make reboots by itself until it got stuck in cyanogen boot logo.
I tried to install cyanogen again using TWRP but it kept failing. Wipe gave messages of "unable to mout data \ cache \ internal storage"
I decided to install a new version of TWRP and now every time I go to recovery, it boots back to bootload.
I tried to flash different versions of TWRP with the same result.
The phone is unlocked, S-ON.
Any ideas anyone?
Click to expand...
Click to collapse
Which versions of TWRP u tried? i sounds for me, that you did a TWRP or Cyanogen Update that isnt comfortable with your phone... Try a TWRP 2.8.5.0, flash it with ADB and give a Feedback. Or try to wipe dalvik-Cache aswell..
dOeVENTS said:
Hi there
If anyone can help me with this I would appreciate. I'll try to keep it short.
I have a HTC mini 2 and a few months ago installed TWRP and cyanogen.
Basically I followed the instructions from wiki.cyanogenmod.org.
One day the phone started to make reboots by itself until it got stuck in cyanogen boot logo.
I tried to install cyanogen again using TWRP but it kept failing. Wipe gave messages of "unable to mout data \ cache \ internal storage"
I decided to install a new version of TWRP and now every time I go to recovery, it boots back to bootload.
I tried to flash different versions of TWRP with the same result.
The phone is unlocked, S-ON.
Any ideas anyone?
Click to expand...
Click to collapse
remove USB cable when rebooting phone. see if it works
Hello guys, i really need help. i have htc one m7 device and i rooted/ bootloader unlocked and flash a custom recovery CWM 6.0.4.7 and custom ROM android 5.0.2. after a while i experienced a constant reboot so i decided to flash another ROM, this time cyanogenmod 13 official after backing up the initial Rom. i run into an error while flashing the CM13. However, i decided to restore the backup i created initial but i think the error in CM13 flash has corrupted the cwm recovery. i get this error when restoring backup -- E: volume not found.
i have been trying to flash another recovery in fastboot mode but i get this error anytime i try in command prompt. this is the error-- error: cannot load "recovery"
i have tried to rename the downloaded recovery file and flash but with no success. when i check the device manager i see htc andriod interface with a sign on it plus android adb interface.
what really am i not doing right. someone should please help me out of this.
Good night guys, first of all I'm sorry if the text is confusing, English is not my strong point, i'm Brazilian.
I had the cyanogenmod in my phone(Moto g thea 1078) and as it was giving so many problems I decided to change the rom to the crDroid, but by a huge oversight of my part when I wipe I marked all the options, now I am not able to install any rom, not even the stock rom, some I can install by twrp without any error (crDroid, Viper), but when I try restart the system after installing twrp says that I am without any rom's installed, and if I ignore and restart anyway my cell phone is eternally on the logo screen, there is only one rom that I was able to install and start the phone, the 1068 rom stock, but chips and wifi doesn't work, when I'm going to install a 1078 stock of error in primary_gpt, in boot and the sparsechunks
"version downgraded for primary_gpt
version downgraded for boot
e img is too big for the sparsechunk"
does anyone have any ideas to help me?
Copy a proper ROM for Thea and Gapps on a micro SD card using a computer or a friend's phone, then place the SD card on your phone and install it through TWRP.
Of course you needed to wipe everything - you always need to delete everything before flashing new ROM, just NOT the external storage, because that's where your installation package is. Try any of the following (some of them don't have SuperSU included, so you will have to flash it separately):
- Viper or
- [proper] crDroid or
- DarkNess reDefined or
- Paranoid Android etc.
Don't forget about the Gapps package and SuperSu (the zip file).
Good luck.
i'v tried this once, doesn't work, but now i can't even install twrp or similar recoverys, always gives an erro "mismatched partition size (recovery)", i google it and people says that this error is normal, the twrp should start even with this errro, but when i start the recovery i got 'boot up failed' or starts the original recovery
luizwalber said:
i'v tried this once, doesn't work, but now i can't even install twrp or similar recoverys, always gives an erro "mismatched partition size (recovery)", i google it and people says that this error is normal, the twrp should start even with this errro, but when i start the recovery i got 'boot up failed' or starts the original recovery
Click to expand...
Click to collapse
Your phone is crippled for life, you installed a firmware for the wrong device. Go install a Titan ROM and TWRP, there is nothing to do. Your phone is an XT1068 now. You lost your LTE ability forever.
https://dl.twrp.me/titan/