Hello,
I've been using my rooted/unlocked Galaxy Nexus for a while now with no problems at all. Earlier today it rebooted for no reason when it was just sitting on my desk. The phone never actually booted and was stuck in a boot loop. I pulled the battery and restarted and went into the recovery menu to do a factory reset. Before I could select the recovery option my phone froze with an exclamation mark android on the screen. I pulled the battery again and now the screen doesn't turn on at all and the phone isn't recognized by my computer. I can't Adb, fastboot, or even Odin. However I can feel the phone vibrate when I power it on. Is there any hope for my phone?
I'm not too sure on this so I'd wait for someone for experienced to reply.
But I can say that it's very hard to brick a Galaxy Nexus. So have some hope.
How do you know you can't fastboot? Are you not able to pull the battery and boot into fastboot when connnected to a computer? Even if the screen doesn't show it, can you do "Fastboot devices" and see it in Command line?
If you can start it up and feel it vibrate, you're definitely not bricked.
Can you get into bootloader? Hold volume up+down and power on.
The android logo you recognised before with the '!' sign was 'Download mode'. If you can see anything on screen there should be no reason why you cant recover it. Don't worry your not bricked.
Same problem!!!
CuteFuzzyPuppy said:
Hello,
I've been using my rooted/unlocked Galaxy Nexus for a while now with no problems at all. Earlier today it rebooted for no reason when it was just sitting on my desk. The phone never actually booted and was stuck in a boot loop. I pulled the battery and restarted and went into the recovery menu to do a factory reset. Before I could select the recovery option my phone froze with an exclamation mark android on the screen. I pulled the battery again and now the screen doesn't turn on at all and the phone isn't recognized by my computer. I can't Adb, fastboot, or even Odin. However I can feel the phone vibrate when I power it on. Is there any hope for my phone?
Click to expand...
Click to collapse
Woke up during the night because the color start up screen was looping. Exact the same problem as CuteFuzzyPuppy. I pulled the battery and went wanted to do a restore both it can't fint volume E:. The files are listed, but when you push one it doesn't work. HELP!
coprotsap said:
Woke up during the night because the color start up screen was looping. Exact the same problem as CuteFuzzyPuppy. I pulled the battery and went wanted to do a restore both it can't fint volume E:. The files are listed, but when you push one it doesn't work. HELP!
Click to expand...
Click to collapse
Are you on stock? Have you unlocked the bootloader and rooted your device?
Yes to all
RTContent said:
Are you on stock? Have you unlocked the bootloader and rooted your device?
Click to expand...
Click to collapse
Meaning, I'm on latest Android Revolution (not stock), and it's unlocked and rooted. Thanks for any help on this!
coprotsap said:
Meaning, I'm on latest Android Revolution (not stock), and it's unlocked and rooted. Thanks for any help on this!
Click to expand...
Click to collapse
do you have clockworkmod recovery? restore a backup if u have one, or wipe data/factory reset, it will work for sure if it was only bootlooping
martonikaj said:
How do you know you can't fastboot? Are you not able to pull the battery and boot into fastboot when connnected to a computer? Even if the screen doesn't show it, can you do "Fastboot devices" and see it in Command line?
If you can start it up and feel it vibrate, you're definitely not bricked.
Click to expand...
Click to collapse
Thanks for the reply. If I hold the volume up, volume down, and power button with the battery in and with the USB unplugged I can feel a vibrate. When I plug the phone into my computer I don't see any fastboot devices. All the drivers are the same and I have tried several USB ports and cords.
If I remove the battery and connect the phone to my computer I hear constant USB connect/disconnect sounds and OMAP4440 constantly appears and disappears in the device manager. Still unable to detect the phone using fastboot or Odin.
What device do you see in device manager? My computer, properties, device manager (top left). It should say something like samsung galaxy Nexus adb device or something.
Sent from my Galaxy Nexus using Tapatalk
RTContent said:
What device do you see in device manager? My computer, properties, device manager (top left). It should say something like samsung galaxy Nexus adb device or something.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
OMAP4440, but it only appears when the battery is out and it constantly connects and disconnects.
CuteFuzzyPuppy said:
OMAP4440, but it only appears when the battery is out and it constantly connects and disconnects.
Click to expand...
Click to collapse
And with the battery in and loaded into the bootloader?
Sent from my Galaxy Nexus using Tapatalk
RTContent said:
And with the battery in and loaded into the bootloader?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Nothing at all.
any luck? I am having similar problems. Phone will not be recognized and I can't access the bootloader. Constant bootloops
i had a similar problem last saturday. Worked on fixing it until yesterday. It was a corrupted sd(from what I can tell) so I never was able to start up my phone again or flash anything to it. I am waiting on a warrenty replacement from samsung. At first I could get to fastboot ect but all flashing errored out. Pretty soon I could only get to a screen with a phone ......triange.....computer screen. Thats where I am at now. I even tried a usb jig to get it back to download mode (which works on lots of samsung devices to get them back from bricked to the oden screen) with no luck. I have seen a few posts saying it is confirmed to work on galaxy nexus, but I had no luck. no luck. On the bright side I was able to pull my droid 2 global out of bricked state yesterday which made me feel a bit better.
CuteFuzzyPuppy said:
Hello,
I've been using my rooted/unlocked Galaxy Nexus for a while now with no problems at all. Earlier today it rebooted for no reason when it was just sitting on my desk. The phone never actually booted and was stuck in a boot loop. I pulled the battery and restarted and went into the recovery menu to do a factory reset. Before I could select the recovery option my phone froze with an exclamation mark android on the screen. I pulled the battery again and now the screen doesn't turn on at all and the phone isn't recognized by my computer. I can't Adb, fastboot, or even Odin. However I can feel the phone vibrate when I power it on. Is there any hope for my phone?
Click to expand...
Click to collapse
Flash thw phone again. Happend to me on symbian.. so I flashed it,, your phone is not bricked
Sent from my Gnex
my phone is similar with yours.So did you solve it?
Related
So I just flashed the stock image through Odin (used the USB cable that came with the phone) and it boots past the boot animation(the T-Mobile 4g one) and then just hangs on "SAMSUNG" and it's still glowing and so is the notification LED but it won't boot, it just stays there. Can someone point me in the right direction to get this thing going? Is this a brick? I don't know what is wrong with it.
I believe It is hanging on the kernel (panic.... not you, the phone). Have you tried booting into recovery and wiping cache? (volume up + home button during hard reset)
Edit: Also what are you flashing from (i.e. CM, AOKP, TW custom ROM)?
if you were on a custom rom prior to reverting to stock, you need to do a wipe in recovery
Serious_Beans said:
So I just flashed the stock image through Odin (used the USB cable that came with the phone) and it boots past the boot animation(the T-Mobile 4g one) and then just hangs on "SAMSUNG" and it's still glowing and so is the notification LED but it won't boot, it just stays there. Can someone point me in the right direction to get this thing going? Is this a brick? I don't know what is wrong with it.
Click to expand...
Click to collapse
It took mine a very long time to boot after odin stock flash. But i dont think your screwed since it still powers on. Can you still get into download mode? Try to flash it again and see what happens.
Go into stock recovery and do a factory reset. Then reboot, that should do the trick.
Powered by the SGSIII
Reboot after ODIN
sswb27 said:
It took mine a very long time to boot after odin stock flash. But i dont think your screwed since it still powers on. Can you still get into download mode? Try to flash it again and see what happens.
Click to expand...
Click to collapse
OK, I am sure I am going to get blasted for putting this on the wrong thread but I have search!
Ran the boot program through ODIN on the Sprint version SPH-L710 and phone will not reboot now and cannot power on
toolkit says waiting for device
get the battery, Samsung and download screen briefly then it dies,
Afraid that I bricked it!
Any help would be appreciated!
rvshaw said:
OK, I am sure I am going to get blasted for putting this on the wrong thread but I have search!
Ran the boot program through ODIN on the Sprint version SPH-L710 and phone will not reboot now and cannot power on
toolkit says waiting for device
get the battery, Samsung and download screen briefly then it dies,
Afraid that I bricked it!
Any help would be appreciated!
Click to expand...
Click to collapse
Take out battery, unplug from computer, press and hold volume keys, plug in cable and insert battery again.
See if it goes into download mode.
Powered by the SGSIII
ThC23 said:
Take out battery, unplug from computer, press and hold volume keys, plug in cable and insert battery again.
See if it goes into download mode.
Powered by the SGSIII
Click to expand...
Click to collapse
red light does come on in the left
then battery symbol flash for a minute and nothing else
I ran into this exact same issue. I tried flashing kernal and everything after I did odin. What I had to do in order for my phone to boot was boot into recovery and do a factory reset. Keep in mind this was stock recovery so everything on your sd card will be gone after the wipe.
crash822 said:
I ran into this exact same issue. I tried flashing kernal and everything after I did odin. What I had to do in order for my phone to boot was boot into recovery and do a factory reset. Keep in mind this was stock recovery so everything on your sd card will be gone after the wipe.
Click to expand...
Click to collapse
Yes, wish I could boot into recovery but it will not even boot into recovery. Not sure if is a soft brick cannot load a screen regardless
Volume down + home screen + power button doesn't work for download mode? If you're screen is still powering on and showing the battery charging icon and samsung logo you haven't bricked your phone. I know on previous phones I have had that even though it showed nothing but a black screen odin still picked the phone up and was able to flash it.
crash822 said:
Volume down + home screen + power button doesn't work for download mode? If you're screen is still powering on and showing the battery charging icon and samsung logo you haven't bricked your phone. I know on previous phones I have had that even though it showed nothing but a black screen odin still picked the phone up and was able to flash it.
Click to expand...
Click to collapse
No, Volume down+home screen+power button only produces the Samsung or the Battery symbol for about a second, goes away and nothing else after that but a black screen, ODIN does not see the phone as it is not powered on, hope that makes sense
Factory reset worked perfectly. Too bad T-Mobile already shipped the replacement.
Sent from my SGH-T999 using Tapatalk 2
Johnny Blaze says ________?
I can't believe you called T-Mo for a replacement before performing a simple factory reset. Talk about a waste of money. As a future business owner this upsets me.
Eh lol oh well. Didn't think it would boot.
Sent from my SGH-T999 using Tapatalk 2
Serious_Beans said:
Eh lol oh well. Didn't think it would boot.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Well, if you're gonna play the system, might as well use your old phone to help us diagnose the imei lost problem and help the community. If you feel like helping us out, get ahold of lordmorphus or someone closely involved in this situation to have you run a few tests so we can figure this thing out. Ill be your bestest friend if you do
mrmako777 said:
Well, if you're gonna play the system, might as well use your old phone to help us diagnose the imei lost problem and help the community. If you feel like helping us out, get ahold of lordmorphus or someone closely involved in this situation to have you run a few tests so we can figure this thing out. Ill be your bestest friend if you do
Click to expand...
Click to collapse
Sure I'll pm him and see what we can do.
Sent from my SGH-T999 using Tapatalk 2
I pmed him. I'll see what we can do when he responds.
Sent from my SGH-T999 using Tapatalk 2
Serious_Beans said:
Eh lol oh well. Didn't think it would boot.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I can care less about exchanging the phone, but you did get a reply here of what to do.
What was the point of asking if you weren't gonna bother listening??
Powered by the SGSIII
Oh, Sh*t, I think I just bricked my phone - same thing happened. It now won't even allow me to boot. I took the battery out, unplugged the USB. Plugged the USB in and then put the battery back in. The LED light comes on for about 30 seconds and then goes off and stays OFF. I've tried POWER+UP/DOWN volume and HOME...still no avail.
The computer does recognize [the phone] when I plug it in by making a thumping sound and then it makes a few thumping sounds and then that's it.
PLEASE HELP!
Hey guys, today i was using my DHD when a usual random reboot occurred, but this time the phone got caught in a bootloop, (I really have no idea why) as with Android 4.2 you now have to register a computer to the phone for ADB to become 'Online'. I know this isn't really a problem for others but my volume down key actually died last week, ADB isn't playing very nicely at all, as it comes up as 'Offline'. I really need your help guys, i have work tomorrow so i really need it. Anythings appreciated. Thanks guys.
Bump
humzaahmed155 said:
Hey guys, today i was using my DHD when a usual random reboot occurred, but this time the phone got caught in a bootloop, (I really have no idea why) as with Android 4.2 you now have to register a computer to the phone for ADB to become 'Online'. I know this isn't really a problem for others but my volume down key actually died last week, ADB isn't playing very nicely at all, as it comes up as 'Offline'. I really need your help guys, i have work tomorrow so i really need it. Anythings appreciated. Thanks guys.
Click to expand...
Click to collapse
If you are in a bootloop and therefore your device is not turning on, you won't be able to use adb commands. What about booting in hboot or recovery and reflashing the rom or a RUU?
glevitan said:
If you are in a bootloop and therefore your device is not turning on, you won't be able to use adb commands. What about booting in hboot or recovery and reflashing the rom or a RUU?
Click to expand...
Click to collapse
I thought about hboot and recovery, but my volume buttons are completely dead, so the phone will just go ahead and attempt to boot normally, back in the Nexus One days I could remove the battery and insert it again whilst plugging a usb cable in, that would get it into recovery, but it doesnt work (as guessed) with my DHD
humzaahmed155 said:
I thought about hboot and recovery, but my volume buttons are completely dead, so the phone will just go ahead and attempt to boot normally, back in the Nexus One days I could remove the battery and insert it again whilst plugging a usb cable in, that would get it into recovery, but it doesnt work (as guessed) with my DHD
Click to expand...
Click to collapse
It is not a wise decision to be messing with a broken device. I am afraid to say that until you can solve the volume rocker issue you won't be able to fix it.
glevitan said:
It is not a wise decision to be messing with a broken device. I am afraid to say that until you can solve the volume rocker issue you won't be able to fix it.
Click to expand...
Click to collapse
Yeah, i'll take it to repair tomorrow and get the volume keys sorted out, then i'll be able to reflash my rom, thanks for the reply though.
EDIT: I discovered that ADB is actually running when the phone is switched off, I typed adb reboot recovery, and it booted into recovery!
humzaahmed155 said:
EDIT: I discovered that ADB is actually running when the phone is switched off, I typed adb reboot recovery, and it booted into recovery!
Click to expand...
Click to collapse
If the device is off... How do you get into adv without power to the device?
Sent from my Reborn Desire HD in another dimension...
That thanks button doesn't bite
GuyInTheCorner said:
If the device is off... How do you get into adv without power to the device?
Sent from my Reborn Desire HD in another dimension...
That thanks button doesn't bite
Click to expand...
Click to collapse
The DHD was powered off, I plugged it into my PC and windows recognised it as "Android ADB Interface" I myself was quite surprised, the LEDs on the phone were flashing orange and green rapidly, I typed adb reboot recovery and it booted straight into recovery
Sent from my GT-I9305 using Tapatalk 2
humzaahmed155 said:
The DHD was powered off, I plugged it into my PC and windows recognised it as "Android ADB Interface" I myself was quite surprised, the LEDs on the phone were flashing orange and green rapidly, I typed adb reboot recovery and it booted straight into recovery
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
Nice, thanks for the heads up :good:
It works like that. Turn off the device, plug in USB cable and adb detects it. I don't know if that works on all devices, but it does on ours. It's an easy way to boot into recovery/bootloader if volume buttons are damaged. But this is too late.
Sent from my Nexus 7 using xda premium
sashank said:
It works like that. Turn off the device, plug in USB cable and adb detects it. I don't know if that works on all devices, but it does on ours. It's an easy way to boot into recovery/bootloader if volume buttons are damaged. But this is too late.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks! Good to know, cause my volume buttons are borked.
Sent from my REVOlutionary Desire HD
thanks don't hurt ya know?
Woke up this morning and my N7 wouldn't turn on. Plugged it in and the charging indicator came up showing at nearly full charge. Holding the power button then turned it on. Went away for an hour or two, came back and it was off. When I turned it back on it was stuck on the X screen. Forcing a reboot with power+vol just led to the tablet turning off. And now I just plugged it into my computer and QHSUSB_DLOAD came up.
Just got the damn thing a couple days ago and it was 100% stock. Any ideas as to what may have caused this?
Just unplugged it and it turned on but is again stuck on the X. Is QHSUSB_DLOAD no longer indicative of a hard brick?
I'm a newbie here, but let's try.
If you can get to the X one, then I think it's not brick yet.
Maybe your should try to press pwer button and volume down to get to fastboot. You press this combination when your Nexus is turned off.
opticaldh said:
I'm a newbie here, but let's try.
If you can get to the X one, then I think it's not brick yet.
Maybe your should try to press pwer button and volume down to get to fastboot. You press this combination when your Nexus is turned off.
Click to expand...
Click to collapse
once I turn it off the whole cycle starts over again. It's sporadically deciding whether or not it wants to boot but I'll keep trying to get into fastboot
herculesgs said:
Woke up this morning and my N7 wouldn't turn on. Plugged it in and the charging indicator came up showing at nearly full charge. Holding the power button then turned it on. Went away for an hour or two, came back and it was off. When I turned it back on it was stuck on the X screen. Forcing a reboot with power+vol just led to the tablet turning off. And now I just plugged it into my computer and QHSUSB_DLOAD came up.
Just got the damn thing a couple days ago and it was 100% stock. Any ideas as to what may have caused this?
Click to expand...
Click to collapse
In doing a little googling it looks to be possibly caused by the update. If you look up the error, you will see a common problem where HTC bricked a bunch of different phones when they pushed an ota a while back. I would say just return it and get a new one . You could do some research and try it yourself. Are you able to get into your bootloader ( vol+ and Vol - when you trun it on)?
uprightbass360 said:
In doing a little googling it looks to be possibly caused by the update. If you look up the error, you will see a common problem where HTC bricked a bunch of different phones when they pushed an ota a while back. I would say just return it and get a new one . You could do some research and try it yourself. Are you able to get into your bootloader ( vol+ and Vol - when you trun it on)?
Click to expand...
Click to collapse
I was able to get into it this morning and I wiped my cache. The next time it decides to turn on/I can get it into the bootloader I'll try a factory reset
herculesgs said:
I was able to get into it this morning and I wiped my cache. The next time it decides to turn on/I can get it into the bootloader I'll try a factory reset
Click to expand...
Click to collapse
Well something got corrupted, but if its booting its not hard bricked (that's good news). Luckily for you as well the aosp images are up so if you want to do a restore you can snag your images, and just do a fastboot install. I hope this isn't indicative of another problem with the device itself, I still maintain that you should probably exchange your device for a new one if you did indeed do nothing to the device. It would be a shame if the same problem happened again because of a faulty component.
uprightbass360 said:
Well something got corrupted, but if its booting its not hard bricked (that's good news). Luckily for you as well the aosp images are up so if you want to do a restore you can snag your images, and just do a fastboot install. I hope this isn't indicative of another problem with the device itself, I still maintain that you should probably exchange your device for a new one if you did indeed do nothing to the device. It would be a shame if the same problem happened again because of a faulty component.
Click to expand...
Click to collapse
Yeah, I most likely will. It'll boot to the X probably once every 25 tries so there's something weird going on and it's probably safer just to return it then find a fix and have it happen again.
herculesgs said:
Yeah, I most likely will. It'll boot to the X probably once every 25 tries so there's something weird going on and it's probably safer just to return it then find a fix and have it happen again.
Click to expand...
Click to collapse
Just out of curiosity, where did you purchase it from? Does the seller recognize a lemon as returnable, would you possibly have to tell them you just didn't like it?
uprightbass360 said:
Just out of curiosity, where did you purchase it from? Does the seller recognize a lemon as returnable, would you possibly have to tell them you just didn't like it?
Click to expand...
Click to collapse
Wally world. afaik they're pretty lax on returns
update
Got into the bootloader and did a factory reset. Everything seems to be working again now
herculesgs said:
Got into the bootloader and did a factory reset. Everything seems to be working again now
Click to expand...
Click to collapse
Awesome! Love a happy ending.
Mine was like that all day. I am unlocked and rooted but stock ROM. Damn thing was on an x all day. I was finally able to get to TWRP and flashed my latest backup. No ideas what happened or why.
Sent from my Nexus 7 using xda app-developers app
AnarchoXen said:
Mine was like that all day. I am unlocked and rooted but stock ROM. Damn thing was on an x all day. I was finally able to get to TWRP and flashed my latest backup. No ideas what happened or why.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Mine is just stuck on Google...... I got into fastboot and flashes stock image but it still will not get past google. I can not boot it to recovery or anything other than fastboot.
What happens when you do vol down and power to try and get into the bootloader? Nothing at all?
Sent from my Nexus 7 using xda app-developers app
kd5dmg said:
Mine is just stuck on Google...... I got into fastboot and flashes stock image but it still will not get past google. I can not boot it to recovery or anything other than fastboot.
Click to expand...
Click to collapse
Follow hercules advice. Vol Down + Power to get to bootloader. Then you should be able to get to recovery. Let us know.
Sent from my Nexus 7 using Tapatalk 4
kd5dmg said:
Mine is just stuck on Google...... I got into fastboot and flashes stock image but it still will not get past google. I can not boot it to recovery or anything other than fastboot.
Click to expand...
Click to collapse
Stuck at Google means /system is corrupted or erased (fastboot to restore system.img)
Stuck at X means something wrong with userdata/cache (factory restore from recovery)
Won't start at all with USB identifying as QHSUSB_DLOAD means either bootloader corrupted or raw partitions corrupted
I suggest you reflash again.
So, my Galaxy S3 suddenly shut off on me, so I tried to reboot it, and it would just say "Galaxy s3" then nothing would show. So I figured it was a software brick and I can just restore a backup. When I tried to access Recovery Mode, it would show that its trying to boot into Recovery, but nothing would happen. So I figured I can just go into Download Mode and restore it through ODIN to get all the partitions working again. It would go to Download Mode for a few seconds, and then just shut off on me before I can even do anything. Everytime I take out the battery and put it back in, it tries to auto boot, but it never gets passed the Samsung s3 logo. Do you think this is a software or hardware brick? And would any of you know how I should go about fixing this?
Thanks a bunch
neim81094 said:
So, my Galaxy S3 suddenly shut off on me, so I tried to reboot it, and it would just say "Galaxy s3" then nothing would show. So I figured it was a software brick and I can just restore a backup. When I tried to access Recovery Mode, it would show that its trying to boot into Recovery, but nothing would happen. So I figured I can just go into Download Mode and restore it through ODIN to get all the partitions working again. It would go to Download Mode for a few seconds, and then just shut off on me before I can even do anything. Everytime I take out the battery and put it back in, it tries to auto boot, but it never gets passed the Samsung s3 logo. Do you think this is a software or hardware brick? And would any of you know how I should go about fixing this?
Thanks a bunch
Click to expand...
Click to collapse
i think the problem is on power button...
if the power button press contiues will be like that
i meet the same case like u...
sory my englis
press thanks if i help...
I agree, the only way it should turn on when you replace the battery is if power was held down. It would explain everything else you mentioned as well. Try gently knocking it back out. Or if comfortable with it, open the device to have a closer kook.
Sent from my SCH-I535 using Tapatalk 4
DocHoliday77 said:
I agree, the only way it should turn on when you replace the battery is if power was held down. It would explain everything else you mentioned as well. Try gently knocking it back out. Or if comfortable with it, open the device to have a closer kook.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
It just turned on, I guess it was the power button.
Sent from my SGH-T999 using xda app-developers app
i'm experiencing a similar issue. I can only get any result while it's plugged in. it wont boot past the second splash screen, I got it into download mode and flashed the stock package from sammobile.com with no change. the phone keeps trying to boot into recovery after flashing stock but it goes to the android with the open chest screen and reboots and tries again over and over. i've taken the phone apart and seen nothing wrong, no corrosion, no water damage and i've even replaced the battery with no success. i tried flashing clockworkmod recovery, the flash was successful but it still wont even boot to recovery. the power button isnt stuck, i can manipulate it when i have the bare motherboard in my hands and still it's fine. would replacing the power switch have any affect? please any thoughts would be appreciated
edit: since flashing stock, plugging the phone into the computer with oem cable causes it to vibrate intermittently. holding power causes it to try recovery mode. running windows 7 with samsung drivers properly installed and adb recognizes my galaxy s2 and captivate no problems. someone mentioned on a post i read about using a 3 part stock rom, modem, pda and phone to flash instead of the all in one tar file, any thoughts?
another edit. this phone has never to my knowledge been rooted or had any kernel/rom flashed onto it. as far as i know it's stock from Wind mobile, 3 months past warranty
Okay so for some context:
My phone had water spill on it, it then immediately started vibrating uncontrollably. I turned it off, it kept vibrating. I had no choice but to let it die of battery exhaustion.
I let it dry in a bag of rice for a week and now I trying to turn it on. It got stuck in a bootloop, booted up the main screen once, rebooted again. Kept vibrating uncontrollably which led to quicker battery exhaustion.
Eventually after like 30 reboots, it said, "this phone ass flashed with an unauthorized image and has been locked" and it told me to contact the manufacturer.
See, from the beginning, I don't give a damn about the phone itself, I just want to get the data off.
How do I achieve this? It's very important.
Thank you, any help is appreciated.
Power it up holding the volume up and power button down. Will boot into boot loader. Select hboot, then recovery. Wipe everything using your recovery. Is that what you are trying to do?
eskimosound said:
Power it up holding the volume up and power button down. Will boot into boot loader. Select hboot, then recovery. Wipe everything using your recovery. Is that what you are trying to do?
Click to expand...
Click to collapse
I want to get all data off correct. It's rooted and I have TWRP on here.
Also since that security message, my phone hasn't booted back up. It's a black screen.
Sent from my SM-A800F using XDA-Developers mobile app
mmmm, just try charging it and doing what I said but it does sound like you've fried it.
There was a program I used a few years back on my One X+ that switched the phone on and off for hours and that recharged the battery but I don't think the M8 works like that....may be worth a Google, recharging dead One battery.
eskimosound said:
mmmm, just try charging it and doing what I said but it does sound like you've fried it.
There was a program I used a few years back on my One X+ that switched the phone on and off for hours and that recharged the battery but I don't think the M8 works like that....may be worth a Google, recharging dead One battery.
Click to expand...
Click to collapse
Okay, here's an update.
The phone turns on but the screen will not work, I cannot unlock my devices but I can get INTO recovery and I can get into ADB Recovery. What can I do in this situation that will allow me to pull my files?
All I want to do is to pull my pictures off, that's it!
Thanks!
technocrat7 said:
Okay, here's an update.
The phone turns on but the screen will not work, I cannot unlock my devices but I can get INTO recovery and I can get into ADB Recovery. What can I do in this situation that will allow me to pull my files?
All I want to do is to pull my pictures off, that's it!
Thanks!
Click to expand...
Click to collapse
If you can get into recovery with adb access, just enter the following from a Windows CMD prompt...
For the entire contents of Internal Storage:
adb pull /data/media/0 C:\Users\(your username)\Desktop (or any location)
If you only want to recover your pictures:
adb pull /data/media/0/DCIM C:\Users\(your username)\Desktop (or any location)
Sent from my m8whl using Tapatalk