This happened a couple of weeks ago, but I decided to post it because I want to help others and I am always open to some explanation as to why this happened. By way of background, I have had 2 HTC MDAs, a G1, and a Dash, amongst over phones. I've been flashing ROMs for probably 5 years or so, and I'd specifically flashed the Dash at least a dozen times. About two months ago I finally got off Windows as my primary OS. I am running Ubuntu 9.04 and Sun's Virtualbox on all my systems with Windows VMs. It has worked brilliantly, and by using this setup I still have access to all my apps that will only play nice with Windows including Outlook and Activesync. I've even flashed a ROM to the Dash from within Activesync before.
HOWEVER, in early July I tried to flash the 3VO 7.01 ROM to the phone using the same cable and same laptop I've used before. Battery was fully charged. I got some error about communications being interrupted or something and it walked me through recovery and restarted the flash. I got some other error and had to take out the battery and after I booted the phone again I restarted the flash and I got a similar error. When I looked at the phone, it was COMPLETELY DEAD. It would not turn on at all, even holding the center button, two soft buttons, etc. I took it to the Tmo store the next day and they plugged in a new battery and nothing. Nada.
If anyone has used Virtualbox for this, when the flash script is run and it goes through the steps and switches modes it will change the recognized USB device type at some point. To complete it in the past I had to re-enable that USB device for the VM to actually start the flash from the tricolor screen. This time when it switched modes was when it died. I didn't realize it could brick this way, but apparently it can and I have made a note to self not to flash from a VM Windows box ever again.
Just thought I'd pass it along as a warning to others.
Can u reach the bootloader by holding the camera button while powering on?
A red-blue-green screen should appear..
No, in fact it shows no sign of life at all, though it worked fine before this event. It won't even show a charge light when plugged in.
Hmm this is something that should be posted as a warning on the wiki for everyone to remember when updating their phones. I have never used a virtual machine for any type of flashing of any thing.
Yup, and I bet we all expect it is going to become a more common occurrence, even if it isn't a mainstream situation...
Hi!
First of all i got AOKP + Franco kernel for 2w without any problem and I didn't change any option since last week.
This morning i rebooted it, it switched off and it didn't start again.
I cannot switch one my nexus again since then. I have always a black screen, also if I try to enter in download mode or in the recovery.
I tried to connect to my computer and smt times my laptop see a omap4400 (i'm not sure about the name) but after few second it disappears.
Tomorrow I'm going to the service center... But I have a big doubt:
What the hell happened this morning?
Thanks
Remove the battery for 5 minutes and try again.
If that doesn't work,
Follow this guide:
1. Download the zip file from http://forum.gsmhosting.com/vbb/f634...eeeee-1465412/, created by Legija
2. Extract zip to whatever location you're comfortable with (I used Android directory)
3. Open up Device Manager (Hold down Windows Key, press R, the type in devmgmt.msc and press OK)
4. Go to actions menu, select Add Legacy Hardware
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process
9. Once completed, unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)
Click to expand...
Click to collapse
biscuitownz said:
Remove the battery for 5 minutes and try again.
If that doesn't work,
Follow this guide:
Click to expand...
Click to collapse
This, if OP can't reach fastboot.
Sent from my i9250
I'm having the exact same problem. I saw my phone at maybe 10% battery in the AM, said screw it and let it die, woke up this morning and plugged the phone in and nothing. No LED light, black screen, completely unresponsive. I've tried every trick in the book, and the only one that seemed to work marginally even was using a different battery, which got my phone to boot to the encryption screen, but then shut off again. It did that twice, and now both batteries are useless.
I used Legija's program to try and bring some life back to my gnex, even though it's not the international version, just in hopes of getting some of my data back (I have already started the replacement process with Verizon since the phone was insured), but I got no luck there either.
It's extremely disappointing and annoying to me that this phone survived all sorts of ROM installations (I was also using AOKP on 4.1 if someone wants to start making connections), reformatting, tweaking, almost every setting on that phone was modified by me.
Not only that but almost any software or hardware problem I did run into I could solve in maybe an hour, but I let my charge run out and the phone just up and bricks itself? Now, that's just bull****... I would be very curious as to an explanation as to WHY on earth this would happen. Very confusing.
Not to hijack the thread, but my interest here is not restoring the phone to working condition but just seeing if I can pull my data off of it. I wouldn't even be posting here had I been able to have an SD card with my gnex, which I figured was unnecessary at the time I bought it since I knew the space on their was enough for me already, and the added branding of "Nexus" brand which had me under the impression it was maybe stable enough by itself. Not a mistake I'll make again..
Is it at all possible to get the data off of my phone at this point? At least partially? I believe encryption makes it impossible but I'm rather stubborn. Any help would be greatly appreciated..
owlieowl said:
I'm having the exact same problem. I saw my phone at maybe 10% battery in the AM, said screw it and let it die, woke up this morning and plugged the phone in and nothing. No LED light, black screen, completely unresponsive. I've tried every trick in the book, and the only one that seemed to work marginally even was using a different battery, which got my phone to boot to the encryption screen, but then shut off again. It did that twice, and now both batteries are useless.
I used Legija's program to try and bring some life back to my gnex, even though it's not the international version, just in hopes of getting some of my data back (I have already started the replacement process with Verizon since the phone was insured), but I got no luck there either.
It's extremely disappointing and annoying to me that this phone survived all sorts of ROM installations (I was also using AOKP on 4.1 if someone wants to start making connections), reformatting, tweaking, almost every setting on that phone was modified by me.
Not only that but almost any software or hardware problem I did run into I could solve in maybe an hour, but I let my charge run out and the phone just up and bricks itself? Now, that's just bull****...
Not to hijack the thread, but my interest here is not restoring the phone to working condition but just seeing if I can pull my data off of it. I wouldn't even be posting here had I been able to have an SD card with my gnex, which I figured was unnecessary at the time I bought it since I knew the space on their was enough for me already, and the added branding of "Nexus" brand which had me under the impression it was maybe stable enough by itself. Not a mistake I'll make again..
Is it at all possible to get the data off of my phone at this point? At least partially? I believe encryption makes it impossible but I'm rather stubborn. Any help would be greatly appreciated..
Click to expand...
Click to collapse
So just to be clear... You've been able to get it to boot all the way up to the encryption screen, right? If so you should be able to get into fastboot (Holding down BOTH volume rockers and the power key.) From there you could relock/unlock the bootloader to do a full factory wipe which might solve your boot issue.
As far as the data loss from the wipe, you could then try this: http://forum.xda-developers.com/showthread.php?t=1994705
TomBall718 said:
So just to be clear... You've been able to get it to boot all the way up to the encryption screen, right? If so you should be able to get into fastboot (Holding down BOTH volume rockers and the power key.) From there you could relock/unlock the bootloader to do a full factory wipe which might solve your boot issue.
As far as the data loss from the wipe, you could then try this: http://forum.xda-developers.com/showthread.php?t=1994705
Click to expand...
Click to collapse
I was able to get it to the encryption screen with my old battery that had a little bit of charge left in it twice, but it shut itself down on me both times. So now both batteries are useless.. I took it to the Verizon store hoping they would maybe try one of their batteries, but they just called customer service and told me they're just going to replace it at this point.
I have a feeling the charging mechanism is somehow damaged, because when I did get it to the encryption screen I had it plugged into a wall outlet and it wasn't charging at all. So, I can't turn the phone on whatsoever anymore.. if I could turn it on I could solve this problem... but it simply refuses to boot. The closest I came to interfacing with it was the OMAP Flash script, which did work, but didn't fix the problem.
So maybe if I could get the phone working enough to use ADB with it I could get my data back, but not even that seems possible..
owlieowl said:
I was able to get it to the encryption screen with my old battery that had a little bit of charge left in it twice, but it shut itself down on me both times. So now both batteries are useless.. I took it to the Verizon store hoping they would maybe try one of their batteries, but they just called customer service and told me they're just going to replace it at this point.
I have a feeling the charging mechanism is somehow damaged, because when I did get it to the encryption screen I had it plugged into a wall outlet and it wasn't charging at all. So, I can't turn the phone on whatsoever anymore.. if I could turn it on I could solve this problem... but it simply refuses to boot. The closest I came to interfacing with it was the OMAP Flash script, which did work, but didn't fix the problem.
So maybe if I could get the phone working enough to use ADB with it I could get my data back, but not even that seems possible..
Click to expand...
Click to collapse
If the phone isn't charging then there's something wrong with the USB port. One way to test that would be to use a battery charger. Also, try a different cable. I've had issues with a few different cables that for whatever reason started to not fit properly in the phone.
If you're USB port has gone bad then you'll need to either A) Always use an external battery charger. B) Get a replacement. C) Fix it yourself (Good guide here: http://www.ifixit.com/Guide/Repairi...+LTE)+Micro+USB+Charge+Port+&+Main+Mic/9641/1 )
Hey guys, wondering if anyone is able to create a recovery image for me to download of 8.1+update 1.
My surface rt wont boot past the surface logo. I can't find my usb drive that had my restore image but on top of that it was 8.0 anyway. I checked the ms website and they only host an 8.0 image as well.
At this point I am willing to try anything. I did attempt to download and boot to the 8.0 recovery image by inserting the usb drive and holding power and volume down until the logo came up, but so far doesn't seem to do anything. Am I completely hosed?
long version:
About a year ago, my surface started performing really poorly. Basically any swipe gestures would either not work or they would be extremely delayed. The animation would also be delayed. Other things would be really slow for instance, in IE tapping inside an address bar wouldn't load the keyboard for about a minute. PS 90% of my activity is on IE reading news or watching youtube.
Several months back I finally noticed that anytime I would start experience these issues, the disk usage in task manager would be pegged at 99% even though the read might literally show only 14 KB/s and the write might only be 1 MB/s. The biggest flag though was the response time was always in the thousands of ms.
I pretty much lived with the problem and often a restart would seem to make things happy for a while. And I usually leave task manager open so I can peek and see the utilization anything things feel sluggish.
Last night it was behaving worse than before. I managed to navigate through the charms and attempted to restart. But after waiting several minutes of it just saying restarting with that circular loading image decided to force the issue and I held down the power button until it shut off. It only said restarting, not installing updates or anything like that. I waited way longer than it would have reasonably taken and under normal circumstances, if it was installing updates, it is very obvious and the messages are clear. Plus the charms power option was simply restart, not update and restart.
Sadly when I tried to power back on, it just gets stuck at the "Surface" logo and doesn't do anything. I waited 10 minutes and forced the power off and tried again. It was late so I decided to go to bed, but left it running in hopes that it would eventually boot up. I woke up 4 hours later and it still showed the Surface text on a black screen. At that point I decided to shut it off.
I had already installed update 1 last week, BUT just in case it is some kind of failed windows update. Is there anyway to "reinstall" from this state?
Gonna be extremely bummed if my device is permanently bricked.
If memory serves, I'm pretty sure I deleted the recovery partition BUT I have a flash drive that has the backup, although it would be an 8.0 backup not 8.1.
Restore to 8 then update?
drearyworlds said:
Restore to 8 then update?
Click to expand...
Click to collapse
It doesn't boot from the 8.0 image. Not sure if its cause it's completely hosed or because it needs 8.1. I'm not getting the boot record problem as reported by people when 8.1 first came out.
Yesterday my phone got stuck in a bootloop (wouldn't go beyond the htc logo screen, recovery was still accessible) after turning itself off (from being too hot I think?). I turned it off via recovery as there was no other way and I wanted to look into the problem now, but the phone won't even turn on anymore. It doesn't seem to charge either (at least the LED doesn't light up).
It's running Android 4.2.2 I think (the latest officially provided) and is rooted. I did not change anything system related recently. The last "noteworthy" things I did were updating a game and "playing" it for maybe 30 minutes (I use quotation marks because I think I left the game running but stepped away from the phone for like 5-10 minutes, but I can't say for sure; it was turned off when I came back), until itself shut down.
The only suggestions I could find for phones that would not turn on or charge were trying different cables/power sockets and removing the battery. Tried 2 different cables on 2 different sockets and my PC; removing the battery it not really possible with this phone...
Any way to fix this?
Looking for suggestions as it seems I'm experiencing issues that don't really fit into one exact category.
*D855 LG G3
*Chupa Chups Rom (Lolipop)
*TWRP 2.8.4.0
The story so far;
Woke up the other day to unresponsive G3. Pulled battery, popped it back in and it booted. LG Lifes Good, Chupa Chups Rom Animation (Lolipop) then to my password entry to decrypt phone. Seems to cycle for a bit like its decrypting. LED is a steady flash of green into blue, over and over, and then black screen, LEDs off, unresponsive. Let it sit for over 40 mins just to make sure it's not just taking forever and when I check it its back to being unresponsive. Pop the Batt again and won't even boot this time. Do this several times till it eventually boots again. At this point, it seems random when it decides it wants to boot. Even if I hold the power button to drain any leftover energy without the batt in. Finally boot again and it cycles to the Rom animation then Blue Screens for a bit and powers off. Pop bat again. Let sit for 10mins. get it to boot and it cycles like the first time. Get to decrypt stage and then Black again. Called my phone from a diff phone just to make sure it wasn't the screen and still nothing. I rinse and repeat this process about another 30 plus times to varying success and any successful boots would always end in either Blue or Black screens. At this point, I believe the Black screen is just the phone being powered off as that's what always follows the Blue screen.
Edit:
Also tested 3.8v batt and is holding charge at 3.9 to 4v without any abnormal drain.
6/1/[email protected]:55pm - Just booted again after sitting overnight and the boot cycle actually went all the way through the decryption and I caught a glimps of the home screen about to load before it blue screened again. Thats the farthest its gotten so far.
6/4/[email protected]:45am - After a full battery drain and recharge apx 3 days since last attempt. same cycle as previous boot. Decrypted. Got to home screen. Blue screened, then black screen and this time following the black screen it blue screened again and then finally shhut down.
I am NOT able to boot into download mode as I'm pretty sure I had USB debugging turned off at the time of the incident. I can boot into recovery (TWRP 2.8.4.0) but can't really do anything there as the phone is encrypted and I'm not able to decrypt it in that older version. It shows all the encrypted partitions as 0mb. I tried to update TWRP to any newer version as well as Blu_Spark or Codeworkx for encryption support to no avail as it can't mount /data. I did reboot from TWRP back to recovery successfully over and over again without issue or having to reseat the battery. I did try to boot to the system and it just Blue screens again. I would like to try and save any data I can and would like to exhaust any options leading to that end first, but if it comes to it I will just wipe and reflash it.
First and foremost I would like to try and use TWRP to restore my phone if possible. I do have some Baks I can use but since the phone is encrypted now (and wasn't when the baks were made) I feel like that still poses an issue. So any help starting with that route would be great otherwise it's on to other methods. I don't believe its the fade/flicker issue as when the screen is displaying it's always fine. However, when I disassemble the phone I'll make sure to check the ribbons first as that's easy enough. I'm leaning more towards the CPU possibly having a bad seat or something. After some sleuthing, I'm thinking about the oven method, but have no idea what temp to do it at. I've seen everything from 160 to 400 degrees. Even blowdryers and Irons. I could just make a reflow oven, but would still like to know the proper temps for that kind of thing assuming the TWRP recovery method of things doesn't work out first.
Thanks in advance to this great community for any help that should follow!
Edit:Well It seems like there's not much in the way of potential solution responses so I think I might just attempt this so-called "Oven Method" and see what happens. If, and when, I do Ill post results. In the meantime, I am still searching for a way to use TWRP to decrypt and rescue the data currently on the phone. Barring any success in that arena on to the Easy Bake Oven