Was given a vivid to try and fix for someone who "plugged it in to the wall and boom phone won't gte passed white HTC screen" So I unlock the bootloader flash a recovery and go in to try and mount the internal memory to put the RUU on it and go back to stock however it won't mount. Tried TWRP and CWM with no luck. So then I was like f** it I'll just flash a custom ROM but it will not let me wipe system/cache/data/dalvik cache and says failed everytime. After a bit more troubleshooting I've come to the conclusion that the internal memory is FUBAR but I haven't found anything on here on how to fix this. Any help would be GREATLY appreciated!
so you used cwm and im thinking it messed up your internal memory. try flashing twrp and formatting and see if it works then
ZeRo2o9 said:
so you used cwm and im thinking it messed up your internal memory. try flashing twrp and formatting and see if it works then
Click to expand...
Click to collapse
I've tried TWRP and it still will not let me format anything. Says failed everytime. When I go the phone it wouldn't even boot passed the HTC logo screen and still won't... however I can still get into the bootloader and recoveries :/
EDIT: It says unable to mount cache/system/etc when trying to flash anything
and when I try to manually format anything through fastboot it gives me FAILED cannot access... wtf
samftw said:
I've tried TWRP and it still will not let me format anything. Says failed everytime. When I go the phone it wouldn't even boot passed the HTC logo screen and still won't... however I can still get into the bootloader and recoveries :/
EDIT: It says unable to mount cache/system/etc when trying to flash anything
Click to expand...
Click to collapse
After TWRP or WCX (key thing is NOT CWM) is flashed, boot to recovery, choose mounts (or mounts and storage), and mount internal. Your PC should tell you that it's corrupt and needs to be formatted, you'll have to do this. When it's done, do the same for the external SD. If it tells you it needs formatted too, do it.
homeslice976 said:
After TWRP or WCX (key thing is NOT CWM) is flashed, boot to recovery, choose mounts (or mounts and storage), and mount internal. Your PC should tell you that it's corrupt and needs to be formatted, you'll have to do this. When it's done, do the same for the external SD. If it tells you it needs formatted too, do it.
Click to expand...
Click to collapse
It will not let me mount internal storage thought that's the issue.
samftw said:
It will not let me mount internal storage thought that's the issue.
Click to expand...
Click to collapse
If the above outlined process doesn't work, you'll need to relock your bootloader and run the proper RUU for your device. Then unlock the bootloader again, don't flash cwm recovery, and go about your business.
You can also try preceeding the above procedure with a Factory Reset from Bootloader
i just wanted to wipe clean my phone so it'll be like my stupid head, and i deleted everything now nothing is showiing not even on pc adb and fast boot are working, im S-OFF and RELOCKED bootloader -just locked it to do a RUU but i cant seem to find a fitting image what should i do ruu'it anyway
Note TWRP says error E\ unable to mount \Cache
UPDATE: i flashed the most similar RUU and it worked back like charm i re-unlocked it rooted it and flashed cyanogen .
anyone STUCK just read how to flash a RUU and download the similar one.
http://forum.xda-developers.com/showthread.php?t=2358738
Like an idiot, I accepted an OTA (4.4.2) while rooted with a custom recovery (Philz). I got stuck in a boot loop and proceded to run through the instructions here (method 2) to get back to stock. I have tried several iterations of this using different stock images with the same result, I can't mount /cache or /data. In the end my phone tries to boot, but gets past the unlocked bootloader screen and flashes the android laying on its back with error written below. My bootloader is 30.B2. Oh yeah, I even tried to download an experimental Cyanogenmod and install it using the ADB sideload, but it failed because it could not access /data.
Any help would be greatly appreciated.
T-Mobile Moto X with unlocked bootloader.
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, 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