In short: Canceled Factory Reset, Now my SD card is not being detected properly and I am unable to format/mount it in recovery
Hey Everyone,
I've recently created quite a frustrating problem on my HTC Vivid that I'm unable to figure out. While attempting to go into CWM Recovery to check what version I have I accidentally selected Factory Reset from the bootloader. I quickly pulled the battery, as my back cover was off, within a second or two of this selection, and to my knowledge the phone was still on the bootloader screen and hadn't begun the process. After rebooting into my ROM and I attempted to install TWRP Recovery via Goo Manager in preparation for flashing a new ROM. After the download timer expired my Goo Manager crashed. Any attempt to install via Goo Manager since then is giving me this error, or it just hangs at the download web page. I suspect that this is because of the botched Factory Reset I mentioned earlier, and I'm worried I've somehow messed up the internal SD. My internal sd card is not detected by the camera app nor correctly seen in my file manager, in settings it is reported at the correct size, but apparently all my media has been deleted. I'm unable to format/mount ext sd or emmc in Recovery. My questions are: Has my sd card been corrupted, and If so, why did all my apps and user data remain? Secondly, how can I remedy this situation? I should mention that my phones data port is basically unusable, so I am unable to connect my device to a PC and use adb/fastboot.
My recovery is CWM 5.5.0.4 and my ROM is CM-10.2 | AOSP 4.3.1 Jellybean [KANG] [Oct-31] My phone is unlocked and S-OFF
Update: I tried to Factory Reset, thinking maybe what got me into this mess would get me out, but that option just takes me into recovery. This leaves me even more puzzled. I followed that up with a factory reset/davlik cache wipe from recovery but that hasn't done anything either. My conclusion thus far is that I need to somehow reformat my internal storage, is that possible without connecting my phone to a pc?
Thank you for any responses, and taking the time to read this.
I inadvertently hit the factory reset once from the boot loader and it did the reset in just a few seconds. It hosed my internal memory and unfortunately had to run the ruu to fix it. I know that is not what you want to hear if you can't connect it to a computer.
Sent from my Nexus 10 using Tapatalk
Seriously?
I have answered this question literally 100 times...
Please use the search feature...
Or at least scroll down and read thread titles...
And if your port is borked... Replace it
Sent from my Vivid 4G using Tapatalk
I did a forum search, I was unable to find a satisfactory answer so I started my own thread. (All were referring to using some method of connecting the phone to a PC)
If anyone is wondering, I solved my problem by simply doing a reset/data wipe via recovery and reflashing my ROM. During setup it prompted me to format my internal storage and now my phone is behaving as normal.
Mods feel free to lock and delete this thread.
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
chg911225 said:
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
Click to expand...
Click to collapse
If your bootloader is unlocked, you should be able to either flash the stock factory image, or re-flash each partition separately through the tool-kit. Since you're getting remote errors with the toolkit, double check that you have the right drivers installed, the tookit and a search on the forum should help with that.
did you already try :
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Don't want to raise any alarms already but I shut mine down on Sunday night (Unlocked/ Rooted/ custom kernel & rom) in order to boot in Recovery and flash a new kernel version and:
1) The sdcard looked empty, it read ~ 26 GB free (I had no more than 20 gb free before reboot) and no folders whatsoever.
2) The phone was stuck at the Google logo heating up but going nowhere.
As I said don't want to start assuming things but the phone randomly going "nuts" and losing all data is scary... I had to spent my entire day yesterday flashing stock 5.0.1 back and re-setting up everything. I followed the guide posted above (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 oh, go with Method 2 and it will work fine).
Out of curiosity how does your SD look like from recovery? Oh, but then you say you can't even boot to Recovery. Which recovery do you have? (I had/have TWRP 2.8.3.1 ). Anyway to repair it you only need to be able to boot into Bootloader properly I guess.
Hi,
I've got XT1068, updated to 6.0 Marshmallow. In the past, I got it FDE (full disk encrypted).
Few days ago I unlocked my bootloader to gain root access on my phone using http://forum.xda-developers.com/moto-g-2014/general/simplified-modifying-boot-img-t3317605
everything went as expected, but by unlocking it wiped all userdata, so I wanted to re-encrypt the phone (and the external SD especially). But now, encryption fails, telling me "encryption fails, you have to reset your phone" each time I start the encryption, ending in a userdata-wipe.
So I thought about going back to stock fw.
After locking the bootloader and applying stock 6.0 FW, I tried again to encrypt the phone, but I am still unable to do so.
Can someone help me giving some suggestions, how I can fix that behavior and (mainly) how to get some errors/debug shown?
When selecting "encrypt now", the green android symbol with black background is shown for 5seconds, then the phone reboots, shows the bootscreen with the M, then it restarts again (after ~30minute) and shows after another 20seconds the message that something went wrong encrypting.
Ok it seems that I found out the problem in my case by myself.
Instead of using mfastboot.exe -w to delete the data and cache partition, I used recovery mode to delete userdata. I did it twice, since the first run, returns some errors.
After reset, I started the phone and got the fresh-install screen. I skipped mobile and wifi networking and did not entered google account details. Then I restarted the phone and waited for ~5minutes and tried to encrypt - everything works. Everytime I started encryption without waiting for some time it failed.
I hope I can save someone else some time, since factory reset takes ~15minutes each time you do it.
Hello Friends,
Yesterday I was chatting on whatsapp and suddenly my le2 restarts, and then a blue splash screen appears and device keeps on booting,
hence I went to recovery and clear the data, but that also didnt help me,
Then i flash the 13s rom via Flashone 1.9 then also same problem happens, sometimes it went to optimizing apps 3 of 4 and again restarts with blue LED, i were unable to switch it off,
after draining the whole battery I keep mobile to charge but now it is not charging, it only showing Red Solid LED Continuously.
Now I am also Unable to boot into recovery or fastboot mode.
I again flash the stock 13s rom via flashone 1.9 , i got success msg but then also mobile is not booting nor it is charging.
Note: I am on complete stock rom on locked bootloader, never unlocked or rooted, used as come in box.
Please give me a solution on this, I have searched everywhere but not getting any solutions.
Thanks in advance
Try to check your USB cable, most of the time charging issue is due to cable
shubham1358 said:
Try to check your USB cable, most of the time charging issue is due to cable
Click to expand...
Click to collapse
Cable is ok. I have another Le2 and it is charging with that cable very well
I am facing same problem. How you solve this issue? Blue led blinks after flashing any rom and bootloop.
xerol said:
Hello Friends,
Yesterday I was chatting on whatsapp and suddenly my le2 restarts, and then a blue splash screen appears and device keeps on booting,
hence I went to recovery and clear the data, but that also didnt help me,
Then i flash the 13s rom via Flashone 1.9 then also same problem happens, sometimes it went to optimizing apps 3 of 4 and again restarts with blue LED, i were unable to switch it off,
after draining the whole battery I keep mobile to charge but now it is not charging, it only showing Red Solid LED Continuously.
Now I am also Unable to boot into recovery or fastboot mode.
I again flash the stock 13s rom via flashone 1.9 , i got success msg but then also mobile is not booting nor it is charging.
Note: I am on complete stock rom on locked bootloader, never unlocked or rooted, used as come in box.
Please give me a solution on this, I have searched everywhere but not getting any solutions.
Thanks in advance
Click to expand...
Click to collapse
I also have the exact same problem. Phone started rebooting as soon as it booted up. Somehow i managed to unlock the bootloader, but to no avail. Can't seems to find any rom which can boot up. So practically i have a bricked device with trwp. Formatted the system and other partitions with twrp, flashed many roms. Still the result is same. Bootloops.
Hi,
try to to reimage your phone with QFIL from this site:
https://www.techpoison.in/2017/12/how-to-flash-letv-le-2-x526-stock.html
I downloaded everything from there, QFIL, Sparse image and drivers. My phone was bricked, but its working normally now. After you flash the image your phone should charge normally, just try to boot it up. In my case i had issues with baseband, not detected, no sim function and no wifi and phone was restarting each 3-4 minutes, but it was operable. Basedband issues can be solved by hard reseting the phone and updating it to 21s using the local update, just put the 21s stock renamed to update.zip to internal storage and run system update. When you get the error - APK missing, just boot it up again and retry the local update, should work fine the second time, i just deleted the update.zip and put back again and ran the update.
---------- Post added at 03:24 PM ---------- Previous post was at 03:18 PM ----------
Forthe55 said:
I also have the exact same problem. Phone started rebooting as soon as it booted up. Somehow i managed to unlock the bootloader, but to no avail. Can't seems to find any rom which can boot up. So practically i have a bricked device with trwp. Formatted the system and other partitions with twrp, flashed many roms. Still the result is same. Bootloops.
Click to expand...
Click to collapse
Flash the 21s bootloader + modem, one ZIP file, should work fine. Not sure what ROM did you install last time. You can give it a shot with with MIUI 10 - its nougat.
I had similar issues, see my topic, maybe it helps a bit.
https://forum.xda-developers.com/le-2/help/x526-bricked-unknown-baseband-4g-t3838093
Modem + bootloader 21s.
https://drive.google.com/file/d/0B_R...FxTGxlMHM/view
Brother same thing happened to me, a week ago. I cant say about your problem but my problem was due to faulty power button. Actually due to that reason my phone actually kept restarting itself. It showed red light blinking while charging and wasn't able to bypass the optimizing app screen. I also thought it was a software issue but actually it wasn't. I spent about 2 hours figuring out what the actual problem was. The problem was: As we know when power button is hard pressed for about 10-15 seconds it reboots itself.
Although the repair shop guy didn't put new power button but he added a tiny piece of paper in between the power button and body housing to prevent the issue and voila the problem was solved.
delltech1 said:
Hi,
try to to reimage your phone with QFIL from this site:
https://www.techpoison.in/2017/12/how-to-flash-letv-le-2-x526-stock.html
I downloaded everything from there, QFIL, Sparse image and drivers. My phone was bricked, but its working normally now. After you flash the image your phone should charge normally, just try to boot it up. In my case i had issues with baseband, not detected, no sim function and no wifi and phone was restarting each 3-4 minutes, but it was operable. Basedband issues can be solved by hard reseting the phone and updating it to 21s using the local update, just put the 21s stock renamed to update.zip to internal storage and run system update. When you get the error - APK missing, just boot it up again and retry the local update, should work fine the second time, i just deleted the update.zip and put back again and ran the update.
---------- Post added at 03:24 PM ---------- Previous post was at 03:18 PM ----------
Flash the 21s bootloader + modem, one ZIP file, should work fine. Not sure what ROM did you install last time. You can give it a shot with with MIUI 10 - its nougat.
I had similar issues, see my topic, maybe it helps a bit.
https://forum.xda-developers.com/le-2/help/x526-bricked-unknown-baseband-4g-t3838093
Modem + bootloader 21s.
https://drive.google.com/file/d/0B_R...FxTGxlMHM/view
Click to expand...
Click to collapse
Hi, Thanks. I actually did that first, flashing through qfil the same rom. it helped me to go to settings after umpteen attempts to go past language selection screen, and i was just able to oem unlock and enable usb debugging (actually after a 2nd partial failed flashing). the phone kept freezing within seconds of booting up. Now After i unlocked the bootloader and installing twrp and flashing many roms thru twrp, i am still having the same problem of booting up and freezing at start-up. cant flash again through qfil, as i will again loose the unlocked bootloader and twrp.
At least , now i can try different roms to see which can unbrick it. last one used was the twrp flashable rom based on eui (small eui by aurel) but it also freezes on language selection screen or beyond.
I am running out of ideas, lets see.
2nd partial failed flashing? any issues during the flash process? i had some issues when i used usb 3.0, 2.0 worked fine for me. If you have also charging issues stay in twrp and let the phone charge properly, its slower but should work fine. You can try to flash the 21s bootloader with modem, maybe it will boot properly. But try it only when you are able to enter the fastboot mode, longpress volume down and power for 10-15 seconds, if that is working you should be able to flash twrp via fastboot and you can experiment a bit. Try to find the chinesse twrp 3.0.2.0 and try to flash the stock 21s version. Should be also an image file, in standard twrp go to install - image, after selecting the image file click on recovery and install, after installation go back, reboot, recovery. Copy 21s to storage, wipe data, cache, dalvik and flash it, chinesse twrp will skip version check and will let you install the stock image, after install reboot but click on do not replace recovery button - this will keep the chinesse twrp installed.
If nothing helps it can be only a HW failure, maybe the power button, try usb 2.0 port during the flash process, i had issues with 3.0 on my pc, if that doesnt help.try a different cable, no more suggestions, sorry.
delltech1 said:
2nd partial failed flashing? any issues during the flash process? i had some issues when i used usb 3.0, 2.0 worked fine for me. If you have also charging issues stay in twrp and let the phone charge properly, its slower but should work fine. You can try to flash the 21s bootloader with modem, maybe it will boot properly. But try it only when you are able to enter the fastboot mode, longpress volume down and power for 10-15 seconds, if that is working you should be able to flash twrp via fastboot and you can experiment a bit. Try to find the chinesse twrp 3.0.2.0 and try to flash the stock 21s version. Should be also an image file, in standard twrp go to install - image, after selecting the image file click on recovery and install, after installation go back, reboot, recovery. Copy 21s to storage, wipe data, cache, dalvik and flash it, chinesse twrp will skip version check and will let you install the stock image, after install reboot but click on do not replace recovery button - this will keep the chinesse twrp installed.
Click to expand...
Click to collapse
My phone has been flashed multiple times by qfil method. And always it hangs at initial setup (so it boots up, but hangs at language selection or further up screens, before setup can complete and launcher could be loaded).
While trying to flash again with qfil once it stopped at 25 percent (because the battery went dead). Charged the battery and booted up the phone, and i was surprised it booted up. After 2-3 attempts i was able to reach the launcher screen and immediately enabled developer options and oem unlock / usb debugging. Only had few split seconds to do this and the phone froze again. After that i installed twrp and hence treying different roms. Most fail at setup.
Just tried MIUI 9PRO ROM. It also froze at setup multiple times, but once i was able to complete the setup and miui launcher is up , but it reboots or turn off the phone just after that. So cant do anything with the phone. Unsure of whether a newer bootloader will help in these freezing issues as i have been able to boot up at least in some roms only if for few seconds. Will try to tinker the settings of miui rom (if the phone let me do it before freezing/hanging). Lets see. Thanks for suggestions. More suggestions welcome, because i am still unsure weather this is a software or hardware related problem. I am guessing that it may have something to do with Google security as earlier i was getting msg that phone has been wrongly resetted and needs to verify with Google (but i couldn't get a chance to use the same account, as phone kept freezing at setup).
Did you fully charge the battery, if not let it fully charge in twrp. Flashing the roms in twrp works everytime or do you see any errors? Before you flash anything disconnect the usb cable.
---------- Post added at 09:54 PM ---------- Previous post was at 09:47 PM ----------
Try to flash the 21s bootloarder with modem, one zip using twrp. Go to fastboot mode and wipe modems. fastboot erase modem1st fastboot erase modem2st. Put the phone to flash mode and reimage with qfil. Before you do it write down both imeis, you can find them also on the original package on the backside. Also try to remove all sim cards from the phone and try a different cable. If nothing helps, hw issue, maybe the power button mention earlier in this thread.
After reflash skip everything at setup and reset phone to factory defaults. OEM is already unlocked, you dont have to do it again.
I have charged the phone fully before any flashing after that error. I can flash the phone through twrp without any error msg. The phone boots up most of times in various roms but hangs at or after the initial setup screens show (like language selection etc). Flashed the modem+bootloader, success, but it showed bootloader version as 20s (not 21s). Tried the commands u mentioned to erase modems, it say error failed, no such partition found. I had checked the partitions with parted and 56 partitions are there including the modemst1 & 2.
Now re flashed via qfil , did as advised but again the same problem of hanging / freezing at or after initialization screens of various roms.
Forthe55 said:
I have charged the phone fully before any flashing after that error. I can flash the phone through twrp without any error msg. The phone boots up most of times in various roms but hangs at or after the initial setup screens show (like language selection etc). Flashed the modem+bootloader, success, but it showed bootloader version as 20s (not 21s). Tried the commands u mentioned to erase modems, it say error failed, no such partition found. I had checked the partitions with parted and 56 partitions are there including the modemst1 & 2.
Now re flashed via qfil , did as advised but again the same problem of hanging / freezing at or after initialization screens of various roms.
Click to expand...
Click to collapse
Yeah sorry i screwed the command its fastboot erase modest1 modemst2, my bad.
Just now i was able to complete the initialization (setup screen) of sparse image india rom. I can reach the launcher and settings for few seconds before the device freezes or reboots.
So the same problem , with which i started, the only good thing is that i have been able to set oem unlock to on, so that i can flash trwp and various roms (but all fail with the same freezing issues)
Forthe55 said:
Just now i was able to complete the initialization (setup screen) of sparse image india rom. I can reach the launcher and settings for few seconds before the device freezes or reboots.
So the same problem , with which i started, the only good thing is that i have been able to set oem unlock to on, so that i can flash trwp and various roms (but all fail with the same freezing issues)
Click to expand...
Click to collapse
So you erased modems and reflashed with qfil right? If so i assume its a HW problem. Try the fix with the power button, i ran out of ideas
Last thing which can help maybe: https://www.youtube.com/watch?v=LH3VOIlLfvo&t=135s
Download 21s stock image + the chinesse twrp, links should be under the video, i think so, or look somewhere in the forum for new links. Try to reflash the 21s, some people reported that freezing issues were gone after installing the latest EUI. Basically you can do the same after QFIL reflash but you need enough time to copy the ZIP file as UPDATE.ZIP to the internal storage and run the local update via setting, system update and local update, i hope that TWRP will work for you, just follow the video tutorial.
delltech1 said:
Last thing which can help maybe: https://www.youtube.com/watch?v=LH3VOIlLfvo&t=135s
Download 21s stock image + the chinesse twrp, links should be under the video, i think so, or look somewhere in the forum for new links. Try to reflash the 21s, some people reported that freezing issues were gone after installing the latest EUI. Basically you can do the same after QFIL reflash but you need enough time to copy the ZIP file as UPDATE.ZIP to the internal storage and run the local update via setting, system update and local update, i hope that TWRP will work for you, just follow the video tutorial.
Click to expand...
Click to collapse
Did that also, the same problem. The phone freezes after the os is booted. I was wondering what is that isnt touched by flashing ( in download mode or fastboot mode or through twrp). I may need to tinker that. The roms are all fine in the sense they all stop at the same points. Something in the phones partition, which isnt touched by flashing? (There must be, as i flashed with qfil, the oem unlock remains, the bootloader didn't lock, and it remains unaffected by re-imaging)
Try this, maybe it helps:
https://forum.xda-developers.com/le-2/help/issues-installing-twrp-rom-le-s3-x522-t3618662/page2
like the title says I uninstalled the mentioned apps using adb and all of a sudden my camera stopped working so I decided for a simple restart and the device stuck in the loop ever since.
it restarts several times and open realme UI recovery and when I choose language it says " KINDLY REMINDER : system error, after select language, please select Online update(keep data) to recovery system, thanks! " .
So I did what the message said and I connect the wifi but instead of updating it says no updates found.
I also tried to wipe data but I got asked whether to retain contacts/media or format data.
I obviously tried the first one because I need the data but as expected it didn't work.
I am skeptical to clean format because I feel that I can still fix it with retaining the data.
I tried all the key combinations but only the realme UI recovery comes up . Please help me!
thank you
I don't think you'll be able to fix this without a full reflashing of the ROM using SP Tools and a format of the data partition from Recovery. You probably don't have access to full ADB now, if at all, and Fastboot won't help you recover anything. However, you should be able to rescue important files before you do this, as long as you have unlocked your bootloader.
Follow the steps here to install TWRP custom recovery. Once done, you can boot into it from fastboot by running `fastboot reboot recovery`. Once you're in TWRP, you can mount partitions so you can access them over USB from your PC.
Once you've got your important files transferred to your PC, take a full backup to be safe, then flash the stock ROM. This thread can help you do both of those things. Note that flashing the stock ROM using SP Tools will also restore the stock recovery. Once the process is done, boot right into fastboot and use it to reboot back into the stock recovery before letting it actually boot the ROM. Format your data partition (yes the whole thing). Now you can restart, and it should go through first time setup just fine.
I was going to uninstall these apps, but was too lazy. Guess lazyness is not too bad after all.
@Ricodey have you got the solution for this thing beacause i am also experiencing same issue
e_v_i_l_x_ said:
@Ricodey have you got the solution for this thing beacause i am also experiencing same issue
Click to expand...
Click to collapse
Unfortunately I had to go for the latter option of complete reset with the loss of data to get my device boot up . It seems the option to recover the device with data seems too complicated and not to mention the fact that this process is not without it's own risks. If you want an easy out from this issue I suggest that you complete format the device and have your important data backed up from now.
And Obviously I had data not backed up which I wanted on my device during this issue but it wasn't too important and I could let go of it cuz rest of my data was backed up.. but being the nerd I am, I tried to recover that data too.. but as I said it wasn't worth the time and risk for me so I chose the latter option.
Hope this helps! Do reply if you need further assistance !
Ricodey said:
Unfortunately I had to go for the latter option of complete reset with the loss of data to get my device boot up . It seems the option to recover the device with data seems too complicated and not to mention the fact that this process is not without it's own risks. If you want an easy out from this issue I suggest that you complete format the device and have your important data backed up from now.
And Obviously I had data not backed up which I wanted on my device during this issue but it wasn't too important and I could let go of it cuz rest of my data was backed up.. but being the nerd I am, I tried to recover that data too.. but as I said it wasn't worth the time and risk for me so I chose the latter option.
Hope this helps! Do reply if you need further assistance
Click to expand...
Click to collapse
for me the issue was like i just downgraded my device to the a.15 firmware after setting up i uninstalled the bloatware apps and some google apps which were not needed obviously and restarted my device and it got a bootloop, the issue of bootloop wasn't new to me i previoulsy had the same issue when i have downgraded to a.19 firmware. there is a simple fix, if you want to get rid of the bloatware apps now also you can use the disable command like.
(pm uninstall-user --user 0 ----package name---) this will not give any bootloop and can enjoy a part of RAM....
THIS WILL HELP
get in touch if need anything else