Related
Hello, I have a weird issue, I looked in the brick thread but didn't see any thing that was just like my issue. Last night I tried flashing the rom and used the zero system wipe available in the dev thread (not saying that is the issue just saying what I was doing). It was clearing the cache(never got passed the cache) for over an hour, then it powered off. I tried restarting it into recovery and it did half the time(especially if I removed the sd card) but couldn't mount anything(sd card /system, /data, etc). But this is were it starts getting weird and not like the brick thread. This morning I tried it again and it booted to recovery and mounted everything!!! Thought it was fixed so I went to do a factory reset to install a new rom. That was an hour ago and it is still clearing cache. The lines in the progress bar slowly move but no blue progress bar at all. Any help at all will be appreciated. I am afraid it will power off again and be a true brick this time (then again maybe it already is)
I am using TWRP and was on the 9/02 cm10 nightly before this all happened.
Thank You.
Edit: still clearing/formating cache but upon closer look it did format /data
nsmith4 said:
Hello, I have a weird issue, I looked in the brick thread but didn't see any thing that was just like my issue. Last night I tried flashing the rom and used the zero system wipe available in the dev thread (not saying that is the issue just saying what I was doing). It was clearing the cache(never got passed the cache) for over an hour, then it powered off. I tried restarting it into recovery and it did half the time(especially if I removed the sd card) but couldn't mount anything(sd card /system, /data, etc). But this is were it starts getting weird and not like the brick thread. This morning I tried it again and it booted to recovery and mounted everything!!! Thought it was fixed so I went to do a factory reset to install a new rom. That was an hour ago and it is still clearing cache. The lines in the progress bar slowly move but no blue progress bar at all. Any help at all will be appreciated. I am afraid it will power off again and be a true brick this time (then again maybe it already is)
I am using TWRP and was on the 9/02 cm10 nightly before this all happened.
Thank You.
Edit: still clearing/formating cache but upon closer look it did format /data
Click to expand...
Click to collapse
I've seen this happen one other time, though it happened just running in android, lost cache etc but just magically came back to life after being off for awhile. In that case AFAIK it didn't brick, or it did and they just never mentioned it.
It does however sound like its gonna give out and just lose them for good.
Only thing I can really suggest is just flash a ROM and see how it goes.
Tapatalked from my Galaxy S II.
pio_masaki said:
I've seen this happen one other time, though it happened just running in android, lost cache etc but just magically came back to life after being off for awhile. In that case AFAIK it didn't brick, or it did and they just never mentioned it.
It does however sound like its gonna give out and just lose them for good.
Only thing I can really suggest is just flash a ROM and see how it goes.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
It still says formatting cache should I just force shut down.
The diagonal lines in the progress bar are moving more smoothly now if that means anything.
Thanks for the reply.
nsmith4 said:
It still says formatting cache should I just force shut down.
The diagonal lines in the progress bar are moving more smoothly now if that means anything.
Thanks for the reply.
Click to expand...
Click to collapse
It will probably eventually shut down or reboot on its own if its having filesystem problems.
If you have adb up you can do adb reboot recovery and bypass the cache format it usually does when you use the volume button. Also you can pull a dmesg which will show what's going on in the file systems.
Tapatalked from my Galaxy S II.
well the device shut down again. It won't even boot to the acer screen, blue light just flashes. The computer knew I plugged something in but ADB says no devices. Guess it is bricked.
thanks for your help
nsmith4 said:
well the device shut down again. It won't even boot to the acer screen, blue light just flashes. The computer knew I plugged something in but ADB says no devices. Guess it is bricked.
thanks for your help
Click to expand...
Click to collapse
Yeah sounds like failsafe apx which happens on numerous sequential failed system or boot reads. If its under a year old I should suggest getting a rep on acer chat to set a repair in motion. If its under warranty it just costs shipping it to them. The rep can tell you if you're still covered.
Tapatalked from my Galaxy S II.
Thanks for all your help. Hopefully since it won't boot they won't notice I rooted and unlocked the boot loader.
nsmith4 said:
Thanks for all your help. Hopefully since it won't boot they won't notice I rooted and unlocked the boot loader.
Click to expand...
Click to collapse
If its in failsafe no they just replace the board and send it back. If it can get to the Acer screen then they can tell.
Tapatalked from my Galaxy S II.
100% Stock, Stuck at "X" Logo on boot. "Dead Android" w/ Exclamation (!) in Recovery
Can someone please help me, PLEASE!!
I just want to be able to download the data from my phone, I don't care about getting android working again right now, I just want to download my photos and videos from the phone. I have a Verizon Galaxy Nexus that's completely stock, including locked bootloader. I tried using the toolkit and I am able to have it see the device while it's in fastboot but I can't do any of the functions because it wants to unlock my bootloader which will erase all my data! I was just swapping the battery on my phone when this happened. I wasn't trying to do anything special, it was just supposed to be a normal boot up but it just got stuck on the "X". I'm running 4.1.1. My stock recovery shows a photo of a dead android and an exclamation point. It looks like this: http://3.bp.blogspot.com/-jF4CgOU8c...ASKg/m6YOuDRcs4g/s1600/AndroidRedTriangle.JPG
Can someone please help me? I will seriously send you a paypal for your time, just please help me the data from my phone. I am somewhat savvy, like I said...I am in fastboot, my drivers are installed, and the toolkit can recognize my phone without any issue.
Thank you soooo sooo much in advance!
Why don't you just boot into stock recovery and just wipe cache. Maybe some rogue app is preventing your boot up.
You will not lose any data by only wiping cache.
Sent from my Galaxy Nexus using xda premium
mariosraptor said:
Why don't you just boot into stock recovery and just wipe cache. Maybe some rogue app is preventing your boot up.
You will not lose any data by only wiping cache.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
My stock recovery shows a big "!" with a dead android. It looks like this.
http://3.bp.blogspot.com/-jF4CgOU8c...ASKg/m6YOuDRcs4g/s1600/AndroidRedTriangle.JPG
I think this might be my only option once I get the phone working again.
http://forum.xda-developers.com/showthread.php?t=1994705
What steps should I take right now though?
Thank you again so much in advance.
Don't fear....
Even if you unlock your boot loader your data is not actually gone. But let's cross that bridge if we get there.
First things first: take your battery out, take your sim card out, put your sim card in and put your battery in. Boot up the phone.
If that doesn't fix you then the next thing to do is try safe mode. Power off the phone. Then, press the power button and BOTH (yes both) the volume up AND the volume down buttons. Hold them until the phone boots up.
If that doesn't work write back. Don't worry though. Your data is safe.
Wartickler said:
Even if you unlock your boot loader your data is not actually gone. But let's cross that bridge if we get there.
First things first: take your battery out, take your sim card out, put your sim card in and put your battery in. Boot up the phone.
If that doesn't fix you then the next thing to do is try safe mode. Power off the phone. Then, press the power button and BOTH (yes both) the volume up AND the volume down buttons. Hold them until the phone boots up.
If that doesn't work write back. Don't worry though. Your data is safe.
Click to expand...
Click to collapse
First, thank you so much for replying.
I should have been more clear in my original message, I took my battery out and sim card in and out over 10 times and I even let the phone sit there for 30 minutes while it was at the X animation to no avail.
I have now also attempted a safe mode boot 4 times with no luck. During my safe mode boot attempts, the phone vibrated a few times but the display just remained at the X animation. It even did it after I let go of the volume key. I'm not sure what to make of this but I attempted it twice with holding both volume keys down as soon as the "google" logo appeared and twice with just the volume down key as soon as the "google" logo appeared. Same thing all 4 times, just sits at the X animation.
What would you recommend as a next step to recover the data? I really only care about the DCIM folder, nothing else matters that much.
forumsid987 said:
What would you recommend as a next step to recover the data? I really only care about the DCIM folder, nothing else matters that much.
Click to expand...
Click to collapse
So can you get into your boot loader at all?
Sent from my Galaxy Nexus
"Two hours? I think I could do better than that streaming Netflix with torch on. Something is very wrong there." - mmuzzy
forumsid987 said:
My stock recovery shows a big "!" with a dead android. It looks like this.
http://3.bp.blogspot.com/-jF4CgOU8c...ASKg/m6YOuDRcs4g/s1600/AndroidRedTriangle.JPG
Click to expand...
Click to collapse
When you see this, press power+ vol up to get to the stock recovery menu. There is a wipe cache option there. It may take you a few tries to press both buttons at exactly the same time, but keep trying. No need to reboot in between tries.
Sent from my Xoom using xda premium
Winesnob said:
When you see this, press power+ vol up to get to the stock recovery menu. There is a wipe cache option there. It may take you a few tries to press both buttons at exactly the same time, but keep trying. No need to reboot in between tries.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Thank you for your reply. I was able to get there and I formatted my cache. After that completed I chose the option to reboot the phone. I didn't do anything special during that reboot like trying to hold the volume down button as well for safe mode, I just let it go. It sat at the "X" animation for about 15 minutes before I gave up and tried it again holding the down volume button, again...no luck. I tried it a third time with holding the down and up volume buttons, no luck.
Any other ideas? Again, I know I've said this a few times but believe me when I say...I really appreciate your guys' help.
forumsid987 said:
Thank you for your reply. I was able to get there and I formatted my cache. After that completed I chose the option to reboot the phone. I didn't do anything special during that reboot like trying to hold the volume down button as well for safe mode, I just let it go. It sat at the "X" animation for about 15 minutes before I gave up and tried it again holding the down volume button, again...no luck. I tried it a third time with holding the down and up volume buttons, no luck.
Any other ideas? Again, I know I've said this a few times but believe me when I say...I really appreciate your guys' help.
Click to expand...
Click to collapse
I think you need to get into fastboot, unlock the bootloader (if it isn't already) and put a clean factory image on. You'll lose your data when you unlock, but there is a thread in this forum on recovering that information. If you're already unlocked, just flash the boot and system images individually - it may clean up whatever is corrupt.
Sent from my Xoom using xda premium
Winesnob said:
I think you need to get into fastboot, unlock the bootloader (if it isn't already) and put a clean factory image on. You'll lose your data when you unlock, but there is a thread in this forum on recovering that information.
Click to expand...
Click to collapse
Yep. That's pretty much where you are headed now: http://forum.xda-developers.com/showthread.php?t=1994705
Sent from my Galaxy Nexus
"Two hours? I think I could do better than that streaming Netflix with torch on. Something is very wrong there." - mmuzzy
Wartickler said:
Yep. That's pretty much where you are headed now: http://forum.xda-developers.com/showthread.php?t=1994705
Sent from my Galaxy Nexus
"Two hours? I think I could do better than that streaming Netflix with torch on. Something is very wrong there." - mmuzzy
Click to expand...
Click to collapse
Thanks guys. I will be attempting this now. Crossing fingers!
Please post questions and issues in Q&A
Thread moved
Thanks
FNM
Wartickler said:
Yep. That's pretty much where you are headed now: http://forum.xda-developers.com/showthread.php?t=1994705
Sent from my Galaxy Nexus
"Two hours? I think I could do better than that streaming Netflix with torch on. Something is very wrong there." - mmuzzy
Click to expand...
Click to collapse
I tried this, it recovered only 36 files out of a 28 GB data file, and the files it did recover were all just files that have been on the phone since I unlocked the bootloader, flashed a custom recovery and flashed a stock OS so I could boot up and do all this. Frankly it seems like the files recovered were all the ones that were on the phone since I flashed a rom, none of my previous data are there. I followed the instructions to a T. Am I doing something wrong? Is the recovery software limiting me somehow because I am not using the paid version?
You have been so kind and helpful thus far, please assist me in figuring out what else I can do.
Thank you!
How the hell..
You can unlock your bootloader using omap flash, doing so will not cause you to lose tour data..................................
There is a thread on it..
Beamed from my Maguro.
Mach3.2 said:
How the hell..
You can unlock your bootloader using omap flash, doing so will not cause you to lose tour data..................................
There is a thread on it..
Beamed from my Maguro.
Click to expand...
Click to collapse
Where were you 24 hours ago??? I am so sad right now, I cannot even begin to describe it. I searched like crazy before I did this, or so I thought.
forumsid987 said:
Where were you 24 hours ago??? I am so sad right now, I cannot even begin to describe it. I searched like crazy before I did this, or so I thought.
Click to expand...
Click to collapse
Wasn't around..
http://forum.xda-developers.com/showthread.php?t=2016628
It's legit.
Figured out it's easier to download from dropbox as compared to rapidshare.
https://www.dropbox.com/s/y0aouzpuppdnivo/OMAPFlash_tuna.zip
No matter how many darn times I try or how many different recovery software suites out there I try, I am getting nothing back. This is so disappointing. Can anyone please recommend something to me? A better data recovery solution? A better way to extract the data from the phone? Anything. I am desperate. I am contemplating going to a legit data recovery center and paying the $500 cause I don't know what to do anymore but I don't even know if they'll be able to do anything.
forumsid987 said:
This is so disappointing. Can anyone please recommend something to me? A better data recovery solution? A better way to extract the data from the phone? Anything. I am desperate.
Click to expand...
Click to collapse
Which phone are you using? Make sure you are pulling from the correct partition for the userdata of your phone.
Sent from my Galaxy Nexus using xda app-developers app
---------- Post added at 12:30 AM ---------- Previous post was at 12:24 AM ----------
Winesnob said:
I think you need to get into fastboot, unlock the bootloader (if it isn't already) and put a clean factory image on...
Click to expand...
Click to collapse
Not sure of the need to flash a new image. May do more harm than good....
Sent from my Galaxy Nexus using xda app-developers app
You could have just transferred files using adb and then a factory reset on your phone with the recovery.
I have created this thread for all you SG-SIII Noobs & Senior Members!
The purpose of this thread is to limit the number of (sometimes useless) threads, that are created over a simple problem that can easily be solved by READING OR SEARCHING.
This is the Emergency thread!
*Did you run into a problem and need quick assistance?
*Do you have a question or concern about your SG-SIII device?
Don't panic just ask here and I or WE THE SG-SIII COMMUNITY will gladly help!
In case of emergency!
Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?
Rayman0625 said:
Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?
Click to expand...
Click to collapse
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2
...Awesome... said:
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.
Sv: ***Emergency Thread*** Here To Help!
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app
lintz said:
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Phone wont boot without the battery in, and with it in I cant stay in recovery without with rebooting.
Rayman0625 said:
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.
Click to expand...
Click to collapse
Even better then lol just test it out at work. I'm about 80% its your battery specially if you OV/UC.
I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.
heartspains88 said:
I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.
Click to expand...
Click to collapse
after you odin, you need to wipe data/ factory reset to boot. If you can't get into recovery ( Power, Home Button, and Volume Up), then try reflashing your stock image in Odin and check your MD5 sum, so you can rule out a bad download
Thanks for the reply, I'm re-downloading the stock rom now to verify it's integrity and do a new flash. I cannot get into recovery, so we will see after the new flash. Pleading ignorance on one subject, how would I go about checking the MD5 sum to verify the file has no issues?
Additionally I did try to Odin recovery and still could not boot into it, this was however before attempting to re-download and flash a stock rom again.
**Edit//Update** Re-downloaded and flashed stock rom, was able to get into recovery and wipe, booted up fine.
Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!
frettfreak said:
Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!
Click to expand...
Click to collapse
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2
Towle said:
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!
frettfreak said:
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!
Click to expand...
Click to collapse
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2
Flashing stock with Odin can take up to ten minutes its normal like the man said above just let it do its thing
Towle said:
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Worked great! Thanks!!
http://forum.xda-developers.com/showthread.php?t=2113883
Let's see if you have any solution for me?
Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)
ohshootrawr said:
Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)
Click to expand...
Click to collapse
Do u happened to have apps that control frequency like setcpu etc? They might be conflicting each other
Sent from my HTC One S using Tapatalk 2
Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?
Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.
BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.
beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link
Hello. So my problem is as follows : out of the blue, my galaxy nexus started to reboot after getting to android (10-15 seconds after booting into the OS). I tried to uninstall some apps, but couldn't because i would get a FC and then the device would freeze.
After i got sick of that, i tried to reboot into CWM and do literally everything to try and fix the phone (this includes sideloading a different rom,factory reset, cache wipe, formatting all of the partitions) but to no avail, the device keeps returning to the same state ! (even after restarting and turning off 3G or wifi the device wouldn't register the command).
Needless to say, i cant backup my phone and cant reach a state that the internal SD will be visible under windows.
What can i do ? i am completely hopeless and would love for some tips on what to do.
P.S - because the phone remembers the last state he was in, and wouldn't write any new information, i believe the problem is with the internal sd memory, but i hope to god i'm wrong. And factory reset from android is impossible because selecting anything instantly reboots the device.
Please, please..help me.
aschlon4 said:
Hello. So my problem is as follows : out of the blue, my galaxy nexus started to reboot after getting to android (10-15 seconds after booting into the OS). I tried to uninstall some apps, but couldn't because i would get a FC and then the device would freeze.
After i got sick of that, i tried to reboot into CWM and do literally everything to try and fix the phone (this includes sideloading a different rom,factory reset, cache wipe, formatting all of the partitions) but to no avail, the device keeps returning to the same state ! (even after restarting and turning off 3G or wifi the device wouldn't register the command).
Needless to say, i cant backup my phone and cant reach a state that the internal SD will be visible under windows.
What can i do ? i am completely hopeless and would love for some tips on what to do.
P.S - because the phone remembers the last state he was in, and wouldn't write any new information, i believe the problem is with the internal sd memory, but i hope to god i'm wrong. And factory reset from android is impossible because selecting anything instantly reboots the device.
Please, please..help me.
Click to expand...
Click to collapse
Have you tried wiping everything through Fastboot? There are a few steps that can wipe the bootloader, boot, userdata, and other components. That could help you out.
Sent from my Xoom using xda app-developers app
TheMan0790 said:
Have you tried wiping everything through Fastboot? There are a few steps that can wipe the bootloader, boot, userdata, and other components. That could help you out.
Sent from my Xoom using xda app-developers app
Click to expand...
Click to collapse
I tried using fastboot just now, through CWM (sideload), but i think the phone needs to be in the os and connected as a MTP..problem is i can't reach that state.
P.S - Does the phone need to be in android for fastboot to work ?! because otherwise i'm back to square one.
aschlon4 said:
I tried using fastboot just now, through CWM (sideload), but i think the phone needs to be in the os and connected as a MTP..problem is i can't reach that state.
P.S - Does the phone need to be in android for fastboot to work ?! because otherwise i'm back to square one.
Click to expand...
Click to collapse
Yes. Turn the phone off. Hold the volume down button while turning the phone on. Keep holding the button down until you see "Starting Fastboot Protocol" and then you can do what you have to do.
Sent from my Xoom using xda app-developers app
TheMan0790 said:
Yes. Turn the phone off. Hold the volume down button while turning the phone on. Keep holding the button down until you see "Starting Fastboot Protocol" and then you can do what you have to do.
Sent from my Xoom using xda app-developers app
Click to expand...
Click to collapse
I tried to do what you said, but i just get the message "downloading..do not turn off target". I also tried Odin through fastboot but recieved a fail message 4 times in a row (after changing computers,usb ports etc..)
Is there anything else i can do ?
I don't understand what the hell is going on..I tried to flash stock firmware through Nexus Root Toolkit, and it said that the flash was successful and i saw how i deleted all my user data and formatted the sd card, but when the device restarted, it was back in the state it was and nothing was altered or changed in any way.
Is this even possible ?!