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
Related
Like an idiot I wiped my System inside TWRP. Using TWRP 2.6.0.2
Earlier tonight my phone starting rebooting. I was inside GooManager and tapped reboot to recovery. When I did that, for some reason my phone lost root. Meaning when I went to reboot inside TWRP it stated that it looks as if my phone is not rooted. I rebooted anyway without installing SuperSU through TWRP. I was already rooted. Afterwards, it would boot up fine but kept constantly rebooting only after a minute or two.
I went back into TWRP and clicked through dalvik wipe and cache wipe. Still got reboots. I was planning on flashing CyanogenMod anyways so I thought I'd go on and wipe everything. I went in to advance wipe and check everything. As I swiped the slider to wipe I realized I checked System too, but it was too late.
Now my phone won't boot past the HTC logo with the red text underneath. I can boot into TWRP however so I hope all is not lost. I am currently at work so I have no way to try anything on the phone at the moment but was hoping for some advice on what to try later when I get home.
I'm thinking maybe I'll be able to use the "Mount" tab in TWRP to load a ROM on and flash and everything will be well again. Would I mistaken to think that? If not, I'll purchase an USB OTG cable and use a USB stick but I really need this up an running as quickly as possible.
Also, does anyone think it would be best just to go back to stock at this point (if I can) and start from scratch?
Much thanks for your help and advice,
dgb1891
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
hayame said:
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
Click to expand...
Click to collapse
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
dgb1891 said:
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
Click to expand...
Click to collapse
Literally stock recovery.img, not TWRP or CWM.
hayame said:
Literally stock recovery.img, not TWRP or CWM.
Click to expand...
Click to collapse
K. Thanks. I have a feeling this is going to be a bit more complicated than I first thought...
I followed what you suggested and got the phone back up and working. Thanks again.
I'm on a C6603 with an Unlocked Bootloader running 10.5.A.0.230 from an FTF flash.
I flashed this recovery's boot.img via fastboot and it worked fine. Went in to recovery and it can't flash anything. The internal storage only shows default folders but it claims they are all empty. SD Card wont mount at all, when I click on it it just hangs for like 30 seconds then errors saying unable to mount. I'm guessing this may be due to not flashing the full zip and only the boot.img? If so, how do I go about flashing the full zip since my recovery wont find it? I amen't rooted since I can't flash the SU APK & Binary zip in recovery...
Any ideas on how to fix recovery then gain root? (I'm having the battery drain issue and I can't live with like 2 hours screen off time)
Roscobigfoot said:
I'm on a C6603 with an Unlocked Bootloader running 10.5.A.0.230 from an FTF flash.
I flashed this recovery's boot.img via fastboot and it worked fine. Went in to recovery and it can't flash anything. The internal storage only shows default folders but it claims they are all empty. SD Card wont mount at all, when I click on it it just hangs for like 30 seconds then errors saying unable to mount. I'm guessing this may be due to not flashing the full zip and only the boot.img? If so, how do I go about flashing the full zip since my recovery wont find it? I amen't rooted since I can't flash the SU APK & Binary zip in recovery...
Any ideas on how to fix recovery then gain root? (I'm having the battery drain issue and I can't live with like 2 hours screen off time)
Click to expand...
Click to collapse
Try a different recovery like twrp
For twrp img file click here
androidtweaker1 said:
Try a different recovery like twrp
For twrp img file click here
Click to expand...
Click to collapse
The install instructions, if you could actually call them that, are horrendously worded. Any more understandable ones? (I'm not a noob, I'm pretty experienced, those instructions are truly just ****ty)...
uninstall recovery & reinstall latest xzdual recovery by nut.
Try Dual Boot recovery with Philz Touch CWM Advanced Edition and TWRP by @shoey63
Sent from my C6603 using Tapatalk
Hi, I need help with a (possibly) soft bricked phone. It boots, yet it reboot itself once it tries to read the multimedia files in the internal storage. The owner is a co-worker so I really don't know how or what could possibly trigger this behavior (a virus perhaps?). The device is not rooted, even if I set usb debugging it just keep rebooting and losing all configuration. Uninstalled apps respawn again once it reboots. I tried to flash it with many Odin versions to a proper stock rom, but when the device reboots all the files remain the same, as if nothing were ever done. I tried wiping everything from recovery mode, didn't work either. Whenever I enter recovery mode it updates some files and says it can't gain access to CSC. I'm not an expert on repairing phones so I'm already out of options, any suggestion would be appreciated.
Edit: Android version is 2.3
Try this: http://forum.xda-developers.com/showthread.php?t=2100642
The guide is meant for Jelly Bean, but works even with Gingerbread and should repair the csc.
Cassiusss said:
Try this: http://forum.xda-developers.com/showthread.php?t=2100642
The guide is meant for Jelly Bean, but works even with Gingerbread and should repair the csc.
Click to expand...
Click to collapse
Didn't work either. All files are still there after rebooting. CSC still fails to load in recovery.
I saw some people with this issue in other android devices, it seems the problem is a corrupted internal memory (nothing can be erased or written). I may just give up
Try to perform this shell command:
mke2fs /dev/block/mmcblk0p3
It will force the format of system partition. You can do it with the Terminal included in TWRP recovery for Gingebread. Once done, you'll have to flash a firmware with Odin to rewrite the system partition.
Cassiusss said:
Try to perform this shell command:
mke2fs /dev/block/mmcblk0p3
It will force the format of system partition. You can do it with the Terminal included in TWRP recovery for Gingebread. Once done, you'll have to flash a firmware with Odin to rewrite the system partition.
Click to expand...
Click to collapse
I can't install custom recoveries, it doesn't recognize external storage and not even Odin can rewrite the recovery.
If you're sure that you can't install TWRP with Odin then I don't know how you could solve your problem, sorry. :/
@Cassiusss Hey Bro,
I have been using epirex cm13 builds
but later these days, i didnt used it much as i was flashing around on my 1+3.
Now, i cant boot in recovery and bootloader, whenever i reboot to recovery or bootloader it boots back to rom.
i try adb commands and flashing recoveries through app but didnt work.
Also I tried odin flash it but as it cant boot in bootloader, how can i revert back.
I am using 12 june build Cm13.
Please help.
Try to reboot to recovery or in download mode with this: https://play.google.com/store/apps/details?id=com.antaresone.quickreboot
Anyway, what error is shown when you try to flash a recovery?
Cassiusss said:
Try to reboot to recovery or in download mode with this: https://play.google.com/store/apps/details?id=com.antaresone.quickreboot
Anyway, what error is shown when you try to flash a recovery?
Click to expand...
Click to collapse
I tried ur mentioned app but it again takes 1-2 secs and boots to system.
I also extracted out boot.img from cm13 and flashed it through rashr but after flashing it again booted to system.
Also tried to factory reset from phone but surprisingly it again didnt show anything and booted to system.
Can You tell me any method to HARD RESET or format its system partition so i can odin it ezily.
I think that formatting system will not bring back recovery or download mode.
What's important is to gain access to download mode (because without it you can't use Odin).
Are you sure that booting your phone while pressing "Volume down" + "Home" + "Power ON" keys is ineffective?
Maybe you'll need an USB JIG to force the download mode...
I guess your device memory is broken. Because my friend's ace3 had the same problem with you, and the service center said that the emmc had been broken. So no hope at all
i tried to install the new update, and when phone restared i got massage Encryption Unsuccessful
i cant wipe, i cant flash nothing to phone because the phone cant find storage.
please help me!
Calm down, panicking is what may lead to further accidents.
Now, explain what you flashed after the (I'm assuming the OOS 5.0 File) update file. What add-ons did you flash? Any other audio mods or anything else?
What is your recovery? Which OOS version or ROM did you come from?
maor23 said:
i tried to install the new update, and when phone restared i got massage Encryption Unsuccessful
i cant wipe, i cant flash nothing to phone because the phone cant find storage.
please help me!
Click to expand...
Click to collapse
Had the same thing. I was lucky, because I backup all my data on my computer before update.
I was able to boot the system. I wiped it with stock recovery.
It ask for password and if u press "forgot password" u can wipe the whole phone. But it does a full wipe than. (Storage included)
An inconvenience at most but not the end of the world. Does it every time to me when I flash an Oxygen ROM. I'm always next to my computer anyway so I end up going ahead and just booting to download mode and doing a fastboot format userdata, fastboot flash recovery <twrp img>, booting to recovery, wiping everything, moving my data back to the phone, and proceeding with setting up the ROM... It's a big hassle and I know there's an easier way but I dunno...
If it doesn't find your internal storage or its only showing a percentage of your total (I have the 128GB 3T and it shows like 48 or 60GB total internal storage) you will HAVE to boot into TWRP and wipe your internal storage anyway to recover that space.. it's lost anyway, so not losing anything.
So I have my Moto X 2014 bootloader unlocked and rooted (Android 6.0)
I wanted to update to LineageOS, and realized everything I try with TWRP Recovery (3.1.2-0) does fail.
I am able to flash another recovery though. i tried downgrading and upgrading TWRP but it didn't help at all.
I also noticed that, while adb is working just fine, my PC can't find my device when in fastboot mode.
So the actions I tried to perform (and failed) with TWRP are: Wiping (davlik, cache, system, data, all together and separately). Trying to copy the log to the SD card also fails.
Mounting (and unmounting) partitions seem to work, at least the checkboxes work and i can see all the contents of my internal sd card.
I'm pretty much out of ideas what to do. Should I try another recovery? Any other ideas?
Thanks in advance!
SteepSheep said:
So I have my Moto X 2014 bootloader unlocked and rooted (Android 6.0)
I wanted to update to LineageOS, and realized everything I try with TWRP Recovery (3.1.2-0) does fail.
I am able to flash another recovery though. i tried downgrading and upgrading TWRP but it didn't help at all.
I also noticed that, while adb is working just fine, my PC can't find my device when in fastboot mode.
So the actions I tried to perform (and failed) with TWRP are: Wiping (davlik, cache, system, data, all together and separately). Trying to copy the log to the SD card also fails.
Mounting (and unmounting) partitions seem to work, at least the checkboxes work and i can see all the contents of my internal sd card.
I'm pretty much out of ideas what to do. Should I try another recovery? Any other ideas?
Thanks in advance!
Click to expand...
Click to collapse
Install Motorola USB driver,
Download last stock rom for your device(not downgrade or you risk an hard brick)
Use zahidim script or mine for install rom
Enable USB debug
Reboot in fastboot
Flash twrp 3.1.1-0