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 ?!
Related
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.
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
I brought my phone in to have the charger port replaced. It worked fine ad then all of a sudden the phone boots up, stays booted for a minute and then reboots. also the screen is unresponsive.
I have used a gnex kit to get into CWM and erase cache and dalvik cache and fix permission and the problem is not resolved.
with out the gnex kit i can't even get into CWM and all i get is a little droid guy with an open stomach hatch with a red mark.
i would erase all data and factory reset as a last option but i have some work photos on the device that are extremely important for me to extract. I should also mention that with the CWM kit I am unable to find the files I wish to pull yet for the few seconds I am able to boot into android my photos are there in the album.
can someone please help me find a way to extract those files so I can try to wipe the device and move on?
cardozanick said:
I brought my phone in to have the charger port replaced. It worked fine ad then all of a sudden the phone boots up, stays booted for a minute and then reboots. also the screen is unresponsive.
I have used a gnex kit to get into CWM and erase cache and dalvik cache and fix permission and the problem is not resolved.
with out the gnex kit i can't even get into CWM and all i get is a little droid guy with an open stomach hatch with a red mark.
i would erase all data and factory reset as a last option but i have some work photos on the device that are extremely important for me to extract. I should also mention that with the CWM kit I am unable to find the files I wish to pull yet for the few seconds I am able to boot into android my photos are there in the album.
can someone please help me find a way to extract those files so I can try to wipe the device and move on?
Click to expand...
Click to collapse
With factory reset your sdcard will not be touched. You will have all your files (unless youre in stock recovery I think). You can use adb pull /sdcard/ to get all youre files.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
With factory reset your sdcard will not be touched. You will have all your files (unless youre in stock recovery I think). You can use adb pull /sdcard/ to get all youre files.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
so what you're saying is if I boot into CWM with the kit, do a factory reset, all my photos will be there? can you please elaborate?
cardozanick said:
so what you're saying is if I boot into CWM with the kit, do a factory reset, all my photos will be there? can you please elaborate?
Click to expand...
Click to collapse
Yes that is correct. You can wipe everything as long as you dont wipe /sdcard. I am not a 100% sure since you are on stock but I know sure for 99%. Google is your friend
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Yes that is correct. You can wipe everything as long as you dont wipe /sdcard. I am not a 100% sure since you are on stock but I know sure for 99%. Google is your friend
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Alright,
alright, we have 50% success!
I was able to get all the files off that I was looking to get, albeit during 20 second intervals in which the phone would allow me to before rebooting....
which brings me to my next point - Phone is stuck in bootloop after following (successfully) this guide to flash stock and unroot which, needless to say, seems strange to me.
Now I supposedly have a fully formatted i9250 maguro with a fresh flash of stock running and i'm stuck in a boot loop which if i leave sitting long enough will eventually get to the "Welcome" [choose your language] screen with an unresponsive display panel until it reboots after about 30 seconds.
please help.
EDIT: I flashed the Factory Image Android 4.2.2 (JDQ39) and still stuck in bootloop with unresponsive screen. maybe this is better as a paperweight??
cardozanick said:
Alright,
alright, we have 50% success!
I was able to get all the files off that I was looking to get, albeit during 20 second intervals in which the phone would allow me to before rebooting....
which brings me to my next point - Phone is stuck in bootloop after following (successfully) this guide to flash stock and unroot which, needless to say, seems strange to me.
Now I supposedly have a fully formatted i9250 maguro with a fresh flash of stock running and i'm stuck in a boot loop which if i leave sitting long enough will eventually get to the "Welcome" [choose your language] screen with an unresponsive display panel until it reboots after about 30 seconds.
please help.
EDIT: I flashed the Factory Image Android 4.2.2 (JDQ39) and still stuck in bootloop with unresponsive screen. maybe this is better as a paperweight??
Click to expand...
Click to collapse
Thats strange. But you have your files and you are on completely stock unrooted. If you still have warranty you can send it back. Maybe you can try this: http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop
Sent from my Galaxy Nexus using XDA Premium HD app
Strange Fix reveals deeper issue
good news and bad news
Alright, so I have swapped the motherboard with an old gnex i had laying around that has a broken screen that wouldn't turn on at all..
I found out that the motherboard on the old phone must be dead because it won't work in the newer phone so I put the guts of the newer on into the broken screen phone and it worked perfectly - albeit with a huge crack in it. so i then thought maybe the issue was solved and put the guts that worked back into the original phone and it is unresponsive and reboots... I've come to the conclusion that the screen is the issue on that device.
but is this fixable??? i have taken the whole thing apart and can't see how that screen could be shorting the device and cause it to reboot nor can i understand why it wouldn't be responsive to the touch for no reason.
anybody have a clue how i can fix that?
Hey guys I have a weird problem. When i turn on the phone, it reboots itself after several second. When i take a photo or make a backup with titanium backup at that time, all data goes away after a reboot. I tried doing a factory reset and i tried to format all the data partition and it is no good. I am really frustrated because i cannot use my phone for more than a week and i cannot afford a new phone right now. Hope you guys can help me.
Cheers
karakalem said:
Hey guys I have a weird problem. When i turn on the phone, it reboots itself after several second. When i take a photo or make a backup with titanium backup at that time, all data goes away after a reboot. I tried doing a factory reset and i tried to format all the data partition and it is no good. I am really frustrated because i cannot use my phone for more than a week and i cannot afford a new phone right now. Hope you guys can help me.
Cheers
Click to expand...
Click to collapse
First try to flash stock via fastboot. If that fails try to lock your bootloader with fastboot with this command: fastboot oem lock. If it has no effect your emmc is fried..
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
First try to flash stock via fastboot. If that fails try to lock your bootloader with fastboot with this command: fastboot oem lock. If it has no effect your emmc is fried..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I tried flashing stock system.img and it gets stuck in writing system
karakalem said:
I tried flashing stock system.img and it gets stuck in writing system
Click to expand...
Click to collapse
I waited a little bit longer and everything went well. I rebooted and the phone booted into my old custom rom with all my apps installed. I even got the same sms from 10days ago again like it is the first time. I played with it a little bit and it made a popping sound with instant bright screen and rebooted itself again. I think this is definitely a hardware issue what are your opinions?
karakalem said:
I waited a little bit longer and everything went well. I rebooted and the phone booted into my old custom rom with all my apps installed. I even got the same sms from 10days ago again like it is the first time. I played with it a little bit and it made a popping sound with instant bright screen and rebooted itself again. I think this is definitely a hardware issue what are your opinions?
Click to expand...
Click to collapse
Use the flash-all.bat.. If that doesn't work execute this command: fastboot oem lock. If your bootloader isn't locked your emmc is fried.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Use the flash-all.bat.. If that doesn't work execute this command: fastboot oem lock. If your bootloader isn't locked your emmc is fried.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I tried flash-all.bat and it didn't worked. Then I tried to lock the bootloader. It was a success, I even tried to unlock it and it said are you sure bla bla bla. I clicked no and rebooted and it booted to my same old friggin ROM!! I rebooted into the fastboot and it says unlocked again. I think that my phones emmc chip locked itself in a particular state and it doesnt allow any changes to be made on it. What should I do next? Is emmc repairable or should i start to searching for a new phone?
karakalem said:
I tried flash-all.bat and it didn't worked. Then I tried to lock the bootloader. It was a success, I even tried to unlock it and it said are you sure bla bla bla. I clicked no and rebooted and it booted to my same old friggin ROM!! I rebooted into the fastboot and it says unlocked again. I think that my phones emmc chip locked itself in a particular state and it doesnt allow any changes to be made on it. What should I do next? Is emmc repairable or should i start to searching for a new phone?
Click to expand...
Click to collapse
I have the exact same issue.
The phone shut itself down at some random point - if it is being charged or on a laptop it seems to be a bit more stable.
When it reboots, it goes into the status from the day it first happened. It asks to update apps again and even though they are updated, the next time the phone starts, it happens all over. If I delete an app, it will be there again after reboot/relaunch.
All the settings remain the same.
My phone is currently unlocked but not rooted and runs stock 4.3. I tried to flash stock 4.3 again and even 4.2 - later I tried Cyanogen. I use CWM to format /data, /system, /sdcard, deleted cache and devlink cache multiple times.
Each time it boot, it remains the same background, settings, and so on....
Bumping it up - really hope that someone has an idea what I could try to fix this...
Tomfk said:
Bumping it up - really hope that someone has an idea what I could try to fix this...
Click to expand...
Click to collapse
I gave it to warranty and they said the eMMC chip is broken. They are going to fix it soon. But I already got myself an LG g2 so it does not matter anymore lol. Try the warranty and good luck.
karakalem said:
I gave it to warranty and they said the eMMC chip is broken. They are going to fix it soon. But I already got myself an LG g2 so it does not matter anymore lol. Try the warranty and good luck.
Click to expand...
Click to collapse
How much did you pay for a new emmc? (i've the same problem )
lo97 said:
How much did you pay for a new emmc? (i've the same problem )
Click to expand...
Click to collapse
It's dollar equivalent is about 50$. Normally they didn't accept my phone to warranty but I know a guy, who knows a guy who knows another guy that works in Samsung Turkey so I got that worked out:laugh:
So, like in the topic, I were using 'service menu'. Everything was good, until I found 'AAT' option. When I entered it, notification appered: Press ok to enter AAT. Phone will reboot. So I pressed ok, on down message appered: 'enter AAT' and phone have rebooted. From now, phone didn't want to boot, it was stuck at LG logo. I wasn't really worried, because I knew I had a backup of system and data in case something worng happened. I entered TWRP and restored everything BUT system still didn't want to boot. I tried to restore second backup (without Xposed) but same result. Now I started to worry that I killed my phone.
Also phone still goes into download mode but I think that PC doesn't detect it because I hear only characteristic Windows 10 plug in sound and nothing more. So what do I supose to do now?
Also what is AAT? And why it killed whole system
Krystiannnnnn said:
So, like in the topic, I were using 'service menu'. Everything was good, until I found 'AAT' option. When I entered it, notification appered: Press ok to enter AAT. Phone will reboot. So I pressed ok, on down message appered: 'enter AAT' and phone have rebooted. From now, phone didn't want to boot, it was stuck at LG logo. I wasn't really worried, because I knew I had a backup of system and data in case something worng happened. I entered TWRP and restored everything BUT system still didn't want to boot. I tried to restore second backup (without Xposed) but same result. Now I started to worry that I killed my phone.
Also phone still goes into download mode but I think that PC doesn't detect it because I hear only characteristic Windows 10 plug in sound and nothing more. So what do I supose to do now?
Also what is AAT? And why it killed whole system
Click to expand...
Click to collapse
It shouldn't happen though
Try to flash the firmware again in download mode.
Krystiannnnnn said:
So, like in the topic, I were using 'service menu'. Everything was good, until I found 'AAT' option. When I entered it, notification appered: Press ok to enter AAT. Phone will reboot. So I pressed ok, on down message appered: 'enter AAT' and phone have rebooted. From now, phone didn't want to boot, it was stuck at LG logo. I wasn't really worried, because I knew I had a backup of system and data in case something worng happened. I entered TWRP and restored everything BUT system still didn't want to boot. I tried to restore second backup (without Xposed) but same result. Now I started to worry that I killed my phone.
Also phone still goes into download mode but I think that PC doesn't detect it because I hear only characteristic Windows 10 plug in sound and nothing more. So what do I supose to do now?
Also what is AAT? And why it killed whole system
Click to expand...
Click to collapse
Are you sure LG Drivers well installed? They might not have been and that's why your device isn't recognized. If your device gets recognized while it's in download mode, you can try these guides:
LG Bridge: https://forum.xda-developers.com/lg-k10/how-to/guide-unbricking-flashing-firmware-due-t3380529
LG UP: https://forum.xda-developers.com/lg-k10/how-to/flashing-firmware-using-lg-t3517839
Finally, after 5 hour tough battle with my phone, I made it to boot up.
thx for help xd
Krystiannnnnn said:
Finally, after 5 hour tough battle with my phone, I made it to boot up.
thx for help xd
Click to expand...
Click to collapse
Ciao bro, how did you solved that, I did the same mistake and now have the same problem
dioariete said:
Ciao bro, how did you solved that, I did the same mistake and now have the same problem
Click to expand...
Click to collapse
Flash ROM 5.1.1 (for me (K420n), flashing ROM 6.0 didn't work - I had to update to 6.0 earlier) until phone boots up. I think that I used this ROM: https://forum.xda-developers.com/lg-k10/development/stock-versions-model-lg-k10-t3457319
You can also try to recover/flash via TWRP but this method didn't work for me.
Krystiannnnnn said:
Flash ROM 5.1.1 (for me (K420n), flashing ROM 6.0 didn't work - I had to update to 6.0 earlier) until phone boots up. I think that I used this ROM: https://forum.xda-developers.com/lg-k10/development/stock-versions-model-lg-k10-t3457319
You can also try to recover/flash via TWRP but this method didn't work for me.
Click to expand...
Click to collapse
Thank you bro, you helped me solve the problem :good: . Have a nice day !