Develop Bugs

[Q] Broken Epic? (Physically or Bricked?)

Alright, here's the deal, this happened about a month ago (ive been stuck with the hero since lol).
I was running ERA EH06 Leak 1.1 (name of the file, i think it was the unnamed rom at the time) which was running perfectly for a few days until I get the google services etc force closes. Anyway I get home from work, I go to switch to stock and reflash to something else (at the time I was flashing roms like crazy lol). Anyway, as im odin'ing to stock, I accidentally pull the usb from the phone in the middle of it and the phone is stuck on the download screen, so I pull the battery and try again.
Now the phone isnt connecting to my computer, and its not even turning on. It wont show anything when I have it plugged into usb, I cant go into recovery or download mode. I saw on another thread a power cycle reset thing that didnt work.
I took it into the sprint store to have them see whats up and they said the usb was pulled off of the motherboard. I open it up myself (im semi experienced in this, and i found a good tutorial online) and nothing is noticeably wrong and the usb isnt pulled off the motherboard.
Also, the battery indicator is red because of "water damage" ( i have taken it in the bathroom with me as I showered, but that was only a few times and I stopped weeks before this happened, so I dont think water damage could be the main problem).
So basically has anyone else had the same or similar issue? Or at least can point me in some direction?

No dl mode? Try taking the battery and SD card out, and holding power and 1 THEN plugging it in still without the battery or SD. No odin then, well...
sent from my epic 4g. with the key skips.

holy s*** its in dl mode, i havent tried anything yet, but i didnt expect that lol

Lmao I assume you know what to do from there. But yeah, I always odin with the battery out after I found out you could
sent from my epic 4g. with the key skips.

Sweet, yeah I got it up n running, thanks yo! I looked up all over the place and couldnt find anything saying to go into dl mode then plug in the usb! Oh well its working now!

[Q] Black screen of death?

Here is what happened on my month new Galaxy Nexus.
1. Listening to mp3 via Bluetooth headset
2. Playing a game
3. Standing up
4. On a train
Sound stopped working across everything, in the game and on the mp3. Tried killing the applications and reloading, the mp3 player refused to even start the mp3.
Rebooted the phone, well, I turned it off. It has never turned back on. Tried removing the battery, all that, nothing.
Got home, tried plugging in the USB into a PC. Nothing. Tried booting into recovery mode, nothing, other than the PC claiming to have found a new device.
I haven't plugged it into a PC in recovery mode before. I haven't even seen recovery mode on the Galaxy Nexus.
I was running OTA Vodafone UK 4.0.2 I hadn't even considered rooting it or anything.
Anyone know if this is salvageable or had the same happen to them?

Hi. If popping the battery does no good I'd get it replaced without any further investigation. Sounds like hardware fail, so long as you are sure you have not got it wet or caused any damage to it.
Sent from my Galaxy Nexus using XDA App

If you cant bring it back on after a battery pull then its a dead phone for sure

I had the same problem last month. An usb jig solved the problem.

USB Jig?
Any more details? Something you can point me at?
Cheers
Found this:
http://forum.xda-developers.com/showthread.php?p=20504509
Appropriate?

So does the phone show anything at all? Does the screen come up for any amount of time? Can you get into bootloader?

So for completeness I have exactly this issue:
http://forum.xda-developers.com/showthread.php?t=1384415
Basically this paragraph:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Click to expand...
Click to collapse
Sounds like a USB Jig might do it. But in this case its back to vodafone and jumping through those hoops.
For the record I hadn't done anything at all to the phone than a normal consumer would. i.e. no rooting, hacking, booting, fruiting or cheesing.
It just died.

a very strange hard brick

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 )

Note 2 Rogers Canada acting very very strange

Hey Guys,
So i've done some research all evening here and I've done nothing different than i'd do any other day with the phone and all of a sudden today around 6 PM eastern the phone started acting up. I came home from work plugged it in and it started to lag and then froze, finally unfroze and got that error " Unfortunately, %1$S %2$S has stopped running. I only have the option to click (ok) So I would do that and I thought all was well, turns out this is not the case. When this error pops up it also disables the phone from charging. I unplug and plug back in, the phone starts to freeze and the error comes back. I've been doing some online re-search some people say it's a synch issue with google and to turn synch of, did so, still same error. Some people have said unplug charger, power off phone wait 10 seconds, plug charger back on and boot up, this also did not resolve my issue. I will say that if the power cable is not in the device, it works fine. After about 2 hours of trying different things, I plugged it back into the charger and the phone started acting out really strange, changing from screen to screen and indicating " The dock is connected" I don't own a dock and the phone has never been into dock. I'm using the stock charger that came with the Note 2.
I will say I have TWRP installed and I've been using the JEDI X Rom for this phone without any problems. I thought, okay well none of this is working maybe it's the rom acting up, so I decided to go into recovery wipe all cache & system and re-installed the rom, same thing. The dock is connected, phone freezing and Unfortunately, %1$S %2$S has stopped running. So, I re-did everything again, wiped all cache systems, fixed permission and put the stock rom back on the phone. Now the phone is indicating in stock mode that the "dock is connected" when really it's just the charger. The phone is going into the time out then pops back on automatically all by it's self. Not getting the Unfortunately, %1$S %2$S has stopped running anymore though. the phone is 3 weeks old, and i'm at a loss here as to what I should do next.
Any suggestions, if not, Is there away to erase the phone "call" time so I can get it down to below 30 minutes so I can return this one for a new one?
Thanks,

Well, after hours of reading, I came across this post for an Android EVO phone and it mentioned something about a connect point of the charging port in the phone and said slightly bend the charger cable when it's attached inside, I tried this at a last cause and everything fixed itself, I re-flashed Jedi X and all errors have cleared itself. I find it strange because I'm very gentle with inserting/disconnecting these cables...
Thanks,

I'm not surprised. I've had similar issues with a S2 and other Sammy phones. In fact my brothers Galaxy S as well. He had to get the whole board replaced. I hate MicroUsb. Although its nice to have a generic sync port that is the same across almost all Android devices, this port needs to change.
Just my $0.02. Glad to see you figured it out. Knock on wood my Note2 hasent had these issues yet.
Sent from my SGH-I317 using xda app-developers app

[Q] Battery doesn't seem to charge, can't get into Odin

I have a Samsung Galaxy S2 Epic Touch for Virgin Mobile I'm selling to a friend of mine. It's been working great for me for about the last year on VM. It was rooted and running Liquid Smooth and then CM 10.1 (both using CWM). When I called VM to transfer the phone to my friends account we ran into a road block because CM doesn't respond to the keypad phone codes VM uses to update the phone, or have the VM hands free activation apps.
I figured I might as well flash back to stock ROM anyway. I downloaded the ROM from here.
Odin got about 75% of the way through the flash and then failed. The phone won't turn off but instead keeps up a persistent splash screen asking me to connect the phone to Kies to do a system recovery (Which I did try and Kies can't seem to complete the connection. It sees the phone but can't connect to it, even after ensuring all drivers are up to date. But then I've never had much success with Kies).
I can still get into Odin on my phone so I tried downloading the .exe ROM instead of the md5 this time, but by the time the ROM downloaded Odin tells me the battery is too low to flash anything (which I believe). Problem is I can turn the phone off to let it charge properly (it pops up with the Kies message whenever I plug the phone in).
I've left the phone plugged into the wall hoping that maybe it is in fact charging, but the indicator light only flashes for a second when I plug it in. I'm working a double shift today so I left the phone at home hoping it will charge so that I can try flashing again, but does anybody have any experience with this sort of problem, or know if the phone will in fact charge?

jonnierod said:
I have a Samsung Galaxy S2 Epic Touch for Virgin Mobile I'm selling to a friend of mine. It's been working great for me for about the last year on VM. It was rooted and running Liquid Smooth and then CM 10.1 (both using CWM). When I called VM to transfer the phone to my friends account we ran into a road block because CM doesn't respond to the keypad phone codes VM uses to update the phone, or have the VM hands free activation apps.
I figured I might as well flash back to stock ROM anyway. I downloaded the ROM from here.
Odin got about 75% of the way through the flash and then failed. The phone won't turn off but instead keeps up a persistent splash screen asking me to connect the phone to Kies to do a system recovery (Which I did try and Kies can't seem to complete the connection. It sees the phone but can't connect to it, even after ensuring all drivers are up to date. But then I've never had much success with Kies).
I can still get into Odin on my phone so I tried downloading the .exe ROM instead of the md5 this time, but by the time the ROM downloaded Odin tells me the battery is too low to flash anything (which I believe). Problem is I can turn the phone off to let it charge properly (it pops up with the Kies message whenever I plug the phone in).
I've left the phone plugged into the wall hoping that maybe it is in fact charging, but the indicator light only flashes for a second when I plug it in. I'm working a double shift today so I left the phone at home hoping it will charge so that I can try flashing again, but does anybody have any experience with this sort of problem, or know if the phone will in fact charge?
Click to expand...
Click to collapse
The easy options are to borrow a battery from a friend with a s2 phone, or get a charger off ebay, or buy a new battery from the store which will probably come with a partial charge.
Sounds like your usb port may have died. That happens sometimes.

I was thinking of borrowing a battery. I have a friend with the same phone, so that's possible.
If the USB charger failed, however, would the blue charging light still flicker on when first plugged in? Because that's what it does. It doesn't charge, but it does seem to acknowledge that it's been plugged in. Also, when plugged into the computer it will still flash the plug me into Kies screen, but now my computer doesn't seem to even recognize that anything is plugged in.
Sent from my HTC0P4E1 using Tapatalk

jonnierod said:
I was thinking of borrowing a battery. I have a friend with the same phone, so that's possible.
If the USB charger failed, however, would the blue charging light still flicker on when first plugged in? Because that's what it does. It doesn't charge, but it does seem to acknowledge that it's been plugged in. Also, when plugged into the computer it will still flash the plug me into Kies screen, but now my computer doesn't seem to even recognize that anything is plugged in.
Sent from my HTC0P4E1 using Tapatalk
Click to expand...
Click to collapse
It is possible. I had a phone that the data burnt out on, but would still charge. Just one pin needs to be bad to cause some issues, but not break everything.
Could just be the battery is totally empty too. Getting a known good battery with a charge is the first step to troubleshoot this.

I have encountered this problem a time or two before when testing some of my many attempted multiwindow mods, the device will in fact charge, but it is going to take forever. After a double shift I would imagine you'd have enough charge to flash properly, so try it again afterwards. Also have you attempted to return to recovery? If Odin only partially completed, your custom recovery may still be there and you might be able to use the power off option from recovery, while the device is plugged in, and possibly tricking it into not powering on to the error screen.
WARNING! Everything in blue is simply conjecture and has not been proven to work, it is simply a working theory. If it does not work don't say I didn't warn you.