i know alot of people are going to hate on me for this. ive been at this for the past 9 hours. i tried to upgrade my xperia s to 4.1 CMOD 10. in order to do that i had to unlock bootloader and install doomRecovery for clockwork mod. in the process i was confused and thought that id be able to restore my phone back to its normal self by clicking on factory reset. that ended up wiping everything. everytime i try to go to flash and 'fastboot devices' it doesnt even say waiting for devices anymore...it just does nothing. i think ive completely wiped out everything on my phone except for doom Recovery. ive been searching for the past 9 hours, but no one has had the same problem as me. oen other person accidently factory reseted his tablet, but there was not much help there. no one was stupid enough to press factory reset. If anyone out there can relate to my problem, or at least offer some advice, can you please do so. i use to be good with computers...but i guess not anymore... im an idiot.
Related
Hey All,
New to XDA but been using this site years so my level of Android knowledge is not bad.
I am currently having a huge problem with my Nexus. I used Google Apps encryption on it recently and that seems to have bricked my phone. I am unable to reset to factory settings to wipe the encryption as recommended by Google and I am stuck now with a bricked Nexus.
I also tried flashing stock roms with Odin which appears to work but the encryption still remains. All I am trying to do is put the stock back on my phone and re-root but I am having no joy. When using CWM to flash a new rom the system does not mount in recovery mode so I can't load any other roms. I have also tried the fastboot method but it stalls on waiting for device all the time.
If anyone has seen this and can help or if anyone just knows how to fix it please help me! I am stuck now with a useless Nexus. I should have just left it alone but as usual I couldn't.
Any help would be so appreciated. Thank you.
By some chance is your phone both rooted with CWM?
Hey, yeah it was so when I did a factory reset it could'nt use the stock bootloader so it didn't know how to wipe it. Unfortunetly once you apply encryption from a Google Apps the only way to remove is to factory reset.
I got around it by fastbooting the stock bootloader, radio and image from Google. Then I completed a manual reset using the original bootloader.
A world of hurt really! I have learned a lot but never going near Google Apps encryption again. It also slowed down the phone too.
Anyhow all sorted now, re rooted and running revolution rom now.
theres another thread with a guy who had the same problem. I wonder if vzw nexus has an issue with encrypting...
If the phone wasn't rooted I would have had no issues. It is simply a problem when it comes to loading roms. In CWM the recovery cant mount the data/system so you can't flash anything. Also doing a factory reset from settings doesnt work because the phone is looking for a stock bootloader which it doesn't have once you root. So I ended up in a loop and could do nothing. Fortunetly I learned all about adb and fastboot this morning, never heard of them before and that allowed me to reload stock and unroot. I still had to wipe the phone using the bootloader as I couldn't get into the phone or past the encryption.
If anyone is having issues with this I will gladly help as I really thought that my phone was bricked and was very frustrated. The only way I got help was from a guy on this tread http://forum.xda-developers.com/showthread.php?t=1392037&page=3
Hello, all. I've had this problem for about a year, but I just kind of put the KF away once I got it replaced instead of fixing it.
Last year, I put my KF into a softbrick, factory reset bootloop. On boot, the KF warns:
Your Kindle has detected a problem and must clear App storage. The recovery process will erase some apps and data from your device.
Click to expand...
Click to collapse
The rest is the generic factory reset info. Press power to proceed. This looks like it goes through the process, restarts, and just boots back up into this message. Thus, bootloop. I've tried looking up others with the same problem, but no one has had the same one I mention. I don't have a custom bootloader or TWRP.
As for what caused this, if i can remember correctly I was having trouble with google apps permissions and changed a folder in /system/ to something else. The fire freaked out and I rebooted it. The above has happened ever since. So the only modification is being rooted. I've tried getting access to adb, but it hasn't listed the device. Maybe I installed the drivers wrong or something, but I didn't mess with it for long because I don't like being in Windows if I can help it.
Any help would be greatly appreciated. Not in too big of a hurry, though, as I have a Nexus 7 currently. ^.^
Get a factory cable to force it into fastboot so you can flash a new bootloader and twrp , then flash a new rom. You can also attempt to race it to factory reset and reset it some have success.
Thepooch said:
Get a factory cable to force it into fastboot so you can flash a new bootloader and twrp , then flash a new rom. You can also attempt to race it to factory reset and reset it some have success.
Click to expand...
Click to collapse
I knew about fastboot, I should have mentioned. I just don't have the money to spend on one currently. What do you mean by attempt to race it to factory reset and reset it?
Just what I said you have just a little time to race to settings and factory reset it before it fc`s and shuts down some people manage to pull it off.
I'm having a weird issue with the phone not booting up, and wanted to see if anyone could offer some insight.
Got the S3 the beginning of the month, the only thing I did was use this guide to root the phone - http://forum.xda-developers.com/showthread.php?t=1739426 Have not put any custom rom on the phone, just the rooted stock. It was running smoothly till last week. Put my phone in my pocket leaving a building and got in my car pulled it out and I was faced with the dreaded "Glowing Samsung Logo." Nothing I did would get it to boot. I tried restarting (Holding Volume Up and Power,) then taking the battery out and restarting. No luck, get the ATT logo (droplets) and music, then the glowing samsung logo and nothing. I then tried taking the battery out and letting it out for the drive home. Get home, nothing still does the same thing. I then thought maybe it's the battery, so with the phone off I let it charge for an hour, tried to start it up and same deal no go.
I then did all the reading I could. I could get into Download Mode and Recovery, so I first tried wiping cache. That didn't work, glowing logo again. Then I bite the bullet, do a factory wipe and get the phone back up and running.
My first assumption through problem solving was that I did something wrong. Putting it in my pocket maybe the buttons got pressed in a weird manner. Maybe it's an app. But after setting the phone back up, it was running smoothly again - til last night. I set my phone down last night and when I come back to it I see the glowing logo again. Repeated all my steps again, no luck booting up, just a glowing logo. I figured I would take it to an ATT store to see what they can diagnose, but they are closed. So I used Odin again and tried just re-applying the rooted stock back on. No luck, bite the bullet wipe the phone and it's up and running again.
Can anyone give me any insight into what is happening. I have looked at the Sudden Death threads and it would seem that I don't have the issue. Maybe a bad assumption, but the fact that I can always get into Download Mode and Recovery leads me to think I don't have the Sudden Death issue. I'm perplexed and can't think of why this issue is happening or what the cause is. I would like to find the root cause of what is going on.
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
OfficialDoughboy said:
I'm having a weird issue with the phone not booting up, and wanted to see if anyone could offer some insight.
Got the S3 the beginning of the month, the only thing I did was use this guide to root the phone - http://forum.xda-developers.com/showthread.php?t=1739426 Have not put any custom rom on the phone, just the rooted stock. It was running smoothly till last week. Put my phone in my pocket leaving a building and got in my car pulled it out and I was faced with the dreaded "Glowing Samsung Logo." Nothing I did would get it to boot. I tried restarting (Holding Volume Up and Power,) then taking the battery out and restarting. No luck, get the ATT logo (droplets) and music, then the glowing samsung logo and nothing. I then tried taking the battery out and letting it out for the drive home. Get home, nothing still does the same thing. I then thought maybe it's the battery, so with the phone off I let it charge for an hour, tried to start it up and same deal no go.
I then did all the reading I could. I could get into Download Mode and Recovery, so I first tried wiping cache. That didn't work, glowing logo again. Then I bite the bullet, do a factory wipe and get the phone back up and running.
My first assumption through problem solving was that I did something wrong. Putting it in my pocket maybe the buttons got pressed in a weird manner. Maybe it's an app. But after setting the phone back up, it was running smoothly again - til last night. I set my phone down last night and when I come back to it I see the glowing logo again. Repeated all my steps again, no luck booting up, just a glowing logo. I figured I would take it to an ATT store to see what they can diagnose, but they are closed. So I used Odin again and tried just re-applying the rooted stock back on. No luck, bite the bullet wipe the phone and it's up and running again.
Can anyone give me any insight into what is happening. I have looked at the Sudden Death threads and it would seem that I don't have the issue. Maybe a bad assumption, but the fact that I can always get into Download Mode and Recovery leads me to think I don't have the Sudden Death issue. I'm perplexed and can't think of why this issue is happening or what the cause is. I would like to find the root cause of what is going on.
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
Click to expand...
Click to collapse
It's just a simple bootloop, do you have any recoveries installed? If yes then make a nandroid backup, do a factory reset, then restore data.
Ali7000 said:
It's just a simple bootloop, do you have any recoveries installed? If yes then make a nandroid backup, do a factory reset, then restore data.
Click to expand...
Click to collapse
Actually no custom recovery installed, had no intention to install a custom rom so I heeded the warning on the thread - " flashing a custom recovery will trip your counter no matter the method used." My most important data is sitting on the external SD, so I had that precaution in place.
I did start looking at the custom recoveries (CWM/TWRP,) know how they work (had CWM on my HTC Inspire) but in this case something is causing the phone to bootloop. I see the benefit of getting up and running quick, but I want to find the source of the problem.
Thanks for the response and taking time to answer.
OfficialDoughboy said:
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
Click to expand...
Click to collapse
OfficialDoughboy said:
Actually no custom recovery installed, had no intention to install a custom rom so I heeded the warning on the thread - " flashing a custom recovery will trip your counter no matter the method used." My most important data is sitting on the external SD, so I had that precaution in place.
I did start looking at the custom recoveries (CWM/TWRP,) know how they work (had CWM on my HTC Inspire) but in this case something is causing the phone to bootloop. I see the benefit of getting up and running quick, but I want to find the source of the problem.
Click to expand...
Click to collapse
It could be your hardware. Of course this is not my area of expertise. You could try to install a custom recovery, wipe everything (system, data, cache, dalvik) and try reinstalling the rooted rom via ODIN. You can use Triangle Away later if needed. If you do not want to go through all of this, you can try going through warranty (just be sure you counter is not tripped and you have stock unrooted before you do).
aybarrap1 said:
It could be your hardware. Of course this is not my area of expertise. You could try to install a custom recovery, wipe everything (system, data, cache, dalvik) and try reinstalling the rooted rom via ODIN. You can use Triangle Away later if needed. If you do not want to go through all of this, you can try going through warranty (just be sure you counter is not tripped and you have stock unrooted before you do).
Click to expand...
Click to collapse
Thanks for the reply. I have all my apps now backed up with Titanium Backup just in case. I also checked for Sudden Death Syndrome with the eMMC Check app and it says I don't have an affected phone. I'm going to give it another week and see if the same thing happens again. If it does I'm going to go through warranty to get a replacement.
OfficialDoughboy said:
Thanks for the reply. I have all my apps now backed up with Titanium Backup just in case. I also checked for Sudden Death Syndrome with the eMMC Check app and it says I don't have an affected phone. I'm going to give it another week and see if the same thing happens again. If it does I'm going to go through warranty to get a replacement.
Click to expand...
Click to collapse
Honestly I suggest going into stock recovery and doing a factory reset and wiping cache. When you flash back stock with Odin you usually have to do a factory reset anyway because it will bootloop.
About tripping the flash counter is almost a non issue as all you have to do is use triangle away and Odin flash back to stock and its gone.
hednik said:
Honestly I suggest going into stock recovery and doing a factory reset and wiping cache. When you flash back stock with Odin you usually have to do a factory reset anyway because it will bootloop.
About tripping the flash counter is almost a non issue as all you have to do is use triangle away and Odin flash back to stock and its gone.
Click to expand...
Click to collapse
I actually did that, sorry I wasn't clear in my original post. This last time, I wiped the cache and rebooted the phone, that didn't work. Then I tried Odin to see if I could save internal data, re-flashed and again couldn't boot. Last thing I did was do a factory reset through stock recovery and got the phone to boot.
Hi everyone,
today I woke up and as usual i turned on my Gnex GSM (that has TWRP 2.8.0.0 and PA 4.6 beta 3 release1) and after a few minutes it started rebooting. i tried to remove battery at first but nothing happened; every time I put in the battery it starts, ask me for PIN, seems everything ok but reboots again.
I tried to enter in recovery mode to do a factory reset and even if TWRP says successful wipe nothing happens because when i reboot everything is like before. Itried to change recovery from TWRP to CWM but I can't even do that it "stucks" with TWRP. Fortunately I made a backup recently so I don't mind losing everything but if everyone has a solution please tell me because I don't know what to do!!
Another thing that compared in the log of TWRP during wipes was some strange ( for me, I'm not a developer) errors like "E: enable to stat '/data/media/.....'
If anyone can help I'll appreciate a lot!!! :laugh::laugh::laugh:
Thanks all!!
Same thing happened to me too....
Everything was working butter smooth when **** hit the fan.
I own GSM Gnex, rooted with stock 4.3 with Xposed installed. Custom recovery was TWRP
One fine day I was sitting with a friend in an restaurant when my phone suddenly started rebooting after reaching the homescreen. Mind you I can unlock my phone but after a couple of seconds, it would reboot
For two days, I did everything I could, used Wugs NRT, did a factory reset using TWRP, used ODIN, Flashed stock using toolkit and did that again manually using ADB. Nothing happened.
It says 'successful' when I flash using NRT, but nothing really changes and it freezes halfway while using ODIN and 'FAIL' error shows up.
After two days, I gave it to the shop from where I bought the device and its fourth day today but he still isnt able to repair my phone.
Mind you, I can access TWRP and all the functions, even factory reset but nothing happens.
At first I thought it might be moisture but it wasnt the case. I think it has to be an hardware issue
Hello,
today I accidentally tapped on "Update" (to 7.1.1) on my rooted Nexus 5X... Something you usually shouldn't do, but it was 2am and I was tired and.... Doesn't matter. After this my phone rebooted and almost instantly showed the dead android with the message "No command". And now I'm stuck there. After rebooting I still land there.
Since the error message almost instantly appeared and since I still can boot into TWRP (3.0.2-2), I think the update wasn't installed and I hope to find a way to avoid the factory reset of my phone. Do you have some tips or possible solutions what I should do in this case?
Thank you for your help.
Its odd this happened, when rooted and twrp installed. in my experience, the update will just simply fail and it will boot back up.... in your case, it sounds like something flashed but the phone didnt like it.... All I can think of is if you cant get into twrp, boot into fastboot and flash the factory image from google, you will loose all data though.....
EDIT, RE-READ you post, if you CAN get into TWRP, try flashing a backup... you should have a backup I hope, lol... First rule of root and flashing is make a backup asap....LOL
When I rooted my phone I did a backup. But the problem is, it was several months ago. So I tried the only method I could save all my data. It wasn't safe, I knew this, but no risk no fun.
My solution was: Download the ota update from Google and flash it with TWRP... Voila! My phone boots properly with the new update... But this method is like I mentioned before not safe and can probably cause a boot-loop with an overwritten recovery. I had to flash my recovery again, but everything works fine now.