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?
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.
Is there a CWM recovery released that I can flash with Odin?
The reason I need CWM and not TWRP is that I'm getting the "E: failed to mount /efs (Invalid argument)" error on recovery (stock or TWRP) whenever I'm trying to do anything so I'll need to run a couple of ADB lines to fix that issue.
If any of you can help me fix that issue w/o CWM, that would be great too.
Also, I can't boot up so the only thing I have access to currently is download mode and recovery. When the phone boots, it hangs on a black screen with the blue LED indicator showing, not flashing though like some others have experienced.
Hi. I had miui7 running on my Mi3 and I wanted to run cm13. I used cm12 before but went back to stock miui7.
But I needed to update baseband to update to cm13 so i used the cm13update.zip from jrizzoli.github.io/dotfiles/ and it had TWRP (modified maybe?) as the recovery and I easily installed CM13 after that. Later I updated via OTA several times and it went fine until the last time when it would not boot anymore and would stay stuck in bootloop or if i went to recovery, it would start installing the last cm13 update and then end with error 7 and would give system partition has unexpected contents error.
I tried to do EVERYTHING I could to make the phone show ANYTHING other than the cm13 updating in recovery screen or the ANNOYING cm13 logo. NOTHING worked.
I tried using miflash to flash old kitkat 4.3 rom, 4.4 rom (would give partition error but i replaced the flash_all.bat from a tutorial to bypass the partition erro) and the latest 6.0 chinese developer rom and it would finish successfully within under 100 seconds and would either go back to the cm13 bootloop or go to recovery and update cm13.
I tried QPST and emmc download with 4.4 rom and it would end with no error and go right back to bootlogo. tried flashing that rom with miflash and it would end within 80 seconds and go back to boot logo.
I tried QFIL with the latest miui8 chinese dev one with firehose and it would fail when it would go near userdata. dont remember the exact error but it was something like cannot divide by zero.
The ONLY time i could flash a different recovery is when i would use the same cm13update.zip and replace the recovery.img with another img such as cwm or mi stock recovery. when i used cwm, it would also try to install cm13 and fail as well.
I tried taking the battery off and shorting the two points which made it easier to get into EDL mode to try to use QPST with no luck.
among so many tries I booted to cm13 a few times. never could it go to homescreen though. once it would not go past the password lockscreen even if i put in the proper password and another time it would but ALL the apps would crash and i would not be able to even swipe the home screens.
sometimes when i tried flashing the cwm ota roms that was in the phone previously or the latest cm14 with otg usb, i would get
INSTALL ZIP SUCCESSFUL on top of twrp but the whole screen would fill up with red writing which said
Error opening : 'data/data/cyanogenmod.platform' (no such file or directory)
and the same thing about every app that was there on the phone.
i do not care about my files theyre all backed up. I just want to use the phone again. Any help is appreciated. thanks.
bump
Hello there, I can make and upload twrp backup of miui v8 dev version. Have you tried to restore a backup?
You'll have to make new partition for this backup ( there are so many threads like "extend partition mi3" or smth like that)
http://en.miui.com/thread-99430-1-1.html
Tried the ones from this thread?
http://forum.xda-developers.com/xia...instruction-to-restore-mi4-mi3-t3279927/page5