Database Info

[Q] Weird screen. Might be broken?

Okay so I was in the process of installing gingerbread on my phone with Odin when my phone just turned off unexpectedly. Not thinking anything of it, I turned it back on to this weird screen and the phone is stuck here. Any help would be appreciated. I have attached a picture of the screen for reference. Thanks.

Don't know if it'll help since I haven't had this problem before but, try removing the battery (just to get rid of that screen for now), then without even turning it on, go straight to Download mode and return it back to stock using GTG's procedure.
Sent from my SAMSUNG-SGH-I997 using XDA

How do I go about doing that? How do I put it into download without turning it on?

Pull Batt, Hold the volume up and down rocker....put batt back in and plug in your USB cable that is plugged into your Computer.
you should be in DL mode after that.

Okay that's what I thought you meant, but I wanted to clarify because I tried that before and I tried it again just now and still the same thing. The screen is slightly different, but basically the same.

does it boot at all, into a logo or anything?
without a method to get to Recovery or DL mode......i would think you needed a Jig to accomplish getting your phone back to a working state.

No it doesn't boot to anything. Just comes on to that screen.

http://forum.xda-developers.com/showthread.php?t=1147636
this is the Jig i was speaking of........otherwise you may just have to return it.

No you don't have to return it. It will go into dl mode. Hold volume up and down and insert USB cable. Open odin and reflash.
That is a static rainbow screen. I ran into that among others while trying to flash it. I just gave up and flashed to stock and reflashed miui. There are some who did have success in getting it to boot but not me.
Sent from my SGH-I997 using XDA App

TOA Duck said:
No you don't have to return it. It will go into dl mode. Hold volume up and down and insert USB cable. Open odin and reflash.
That is a static rainbow screen. I ran into that among others while trying to flash it. I just gave up and flashed to stock and reflashed miui. There are some who did have success in getting it to boot but not me.
Sent from my SGH-I997 using XDA App
Click to expand...
Click to collapse
if you had the same screen/problem how did you get into DL mode to reflash stock.
this may help him out.

Okay so the jig is something that I have to buy? And TOA Duck how did you reflash to stock from this? Thanks.

infamousosiris said:
Okay so the jig is something that I have to buy? And TOA Duck how did you reflash to stock from this? Thanks.
Click to expand...
Click to collapse
you could make it, just resisters and a gutted USB cable. but for 8 bucks to have a DL mode fix is kind of worth it.
i have only bricked my Cappy like that though, and i made one at work.

Goto gtg's ultimate unbrick thread in development and read through the directions for unbricking.
All I did to get into dl mode was pull battery, reinsert battery, hold vol up and down together and plug in USB.
Don't make the mistake I made the first few times trying to get into dl mode and hold power button along with. ONLY hold the 2 volume keys.
I understand where you are coming from. I thought my phone was f--ked too when I got that static screen.
Hope it helps
Edit,.... my dl mode screen looked different than the usual one this time. It looked like a computer and a phone side by side with an ! Between them. No worries its still dl mode.
Sent from my SGH-I997 using XDA App

Okay well I don't know what happened, but I was able to reflash to stock somehow. I did the process for getting to the download screen, but the rainbow screen showed up so I just decided to act like it was there and hit the volume up and it showed up in odin finally and I was able to flash it. Thanks for the help everyone!

Hand claps, im glad it was an easy fix.

Kudos to you for not freaking out or giving up.
*applause*

Okay I got it working again and reflashed the stock ROM using GTG. But now that its running its running like crap and the second I turn on the phone it gives me like 5 notifications that some apps have stopped unexpectedly and I have to force close them. Not only that, but now every time that I open an app it almost immediately closes saying that it has stopped unexpectedly and needs to be force closed. Any ideas on what might be causing this? I'm thinking that it has something to do with the reflash, but I'm not sure. Oh also on a smaller note, my market app is completely different as far as how it looks. Not a big deal but just thought it was interesting. Thanks.

i always a fan of reflashing.....lol
since you got it past that rainbow of death, i would go back to stock one more time wipe EVERYTHING and go from there....the Force Closes is not a Huge deal. usually happens from a bad install or using TiBu to restore sys data.
so Flash away,

weird screen
that kind of screen happens when you use the lagfix with a rom in 2.2 base and change it from rfs. you have to put it back to rfs and try the rom you installed again or you have to reflash back to stock. This has primarily happened to me when going from a 2.2 base rom to a 2.3 rom

[Q] Unpleasantness... Bricked phone?

So, while I'm no expert I'm not new to rooting and flashing. Did it quite a bit on my older Droid Inc 1, and have performed a few on my new SG3.
I have 3 backed up ROMs on my SD, Synergy, Beans and CM10. I was running Synergy and decided to give CM10 another shot to see if I could figure out what was killing NFC. So, flashed it up with ROM Manager (Used Odin previously) and everything went swimmingly. ROM was running, NFC was working, all my apps were reinstalled, no problems.....
Decided to see if I could get Wallet working on this install, so flashed it in, made the changes to build.prop and rebooted.
Heeerreeee's where the trouble started. Part way through the reboot the phone just shut down. Completely. 100%. Dead.
I had 87% battery when I started so it 'shouldn't be a battery problem. No power, no LED when I plug in the charger, no vol-up, home, power to get into recovery.
One interesting thing did happen while I was trying to get the phone up, I removed the battery for a bit, and plugged the USB cable in and got a red charging light. Put the battery back in, light still there. 1 minute later, light goes off and still nothing happening with the phone at all.
Anyone have any ideas beyond all the stuff I've given a shot to?

Will it show up when plugged in on your CPU?
Sent from my Nexus S 4G using xda app-developers app

nexus995743 said:
Will it show up when plugged in on your CPU?
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Unfortunately not. Only thing that seems to show up is in the device manager, a QHSUSB_DLOAD device that's banged.

Hmmmm
Sent from my Nexus S 4G using xda app-developers app

nexus995743 said:
Hmmmm
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Well, I called Verizon and they've shipped me a replacement. I guess throwing all my bit and pieces into a new main body should work fine...

Oh no. Another one sending a phone back because of rooting. That's why they lock bootloaders.
Sent from my Galaxy Nexus using xda app-developers app

+1

Have you tried borrowing someone's battery to see if you can also least boot? I have four samsung batteries for the S3 and would consider sending it to you before getting a replacement. I think the cost of a battery is $3 on Amazon.
Sent from my SCH-I535 using xda premium

The reasons were different but i had the same thing happen to me, my phone wouldn't boot, wouldn't show up in the computer. Nothing, i tried my wife's battery, no change there either. I left it on the charger overnight and tried turning it on in the morning and after messing with it it came back on. Haven't had an issue since. Don't know what caused it, the phone just freaked out, turned off and wouldn't turn back on.
You can also try the resistor trick to see if that will bring your phone back. Here is a cheap way to do it.
http://hackaday.com/2012/09/03/saving-a-bricked-phone-with-a-pencil-lead/ Otherwise you can go to radio shack and pick up a resistor.
If Verizon sends you your phone back cause you messed with it, there is a brick repair service for like $60 bucks PM for the link if it comes to that.

Congrats on the new phone
Sent from my Nexus S 4G using xda app-developers app

nexus995743 said:
Congrats on the new phone
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
hehe.. I can't say I was pleased with having to go that route, (can't stand being defeated by electronics) but all in all I can't imagine a simple software change causing the entire unit to just go dead. Not booting properly, or locking up and such, sure... but not just dead.
By this morning I had tried another battery (a friend has an SG3 also) to no effect, but I didn't try leaving it plugged in overnight. I did check the battery with an external charger I have and it was showing fully charged....
So, I'll get a replacement and stay away from CM10 at the very least.
**ihavenewnike - Not sure why you're on an android developers forum really...

Ok, so the new phone got here at about 12:30. Plugged all my stuff into it and it fired right up.
Rooted and unlocked it, put my latest Synergy backup (1 day old) on the SD card and restored it.
Ahhhh... It's just like it never left. :victory:

keno1964 said:
Ok, so the new phone got here at about 12:30. Plugged all my stuff into it and it fired right up.
Rooted and unlocked it, put my latest Synergy backup (1 day old) on the SD card and restored it. . .
Click to expand...
Click to collapse
. . . and then the display went black and it wouldn't power on! What the heck?!
. . .
Oh, sorry: I was just imagining a funny ending to this topic.
- ooofest

ooofest said:
. . . and then the display went black and it wouldn't power on! What the heck?!
. . .
Oh, sorry: I was just imagining a funny ending to this topic.
- ooofest
Click to expand...
Click to collapse
Don't like you.......

Same thing happened to me when I tried to mess with the NFC hack on my SGS III.
What saved me was a USB Jig I happened to have handy when I...accidentally... soft bricked a friend's Samsung Captivate a few months back. The USB Jig is used to put the SGS III into download mode when all else fails that tiny little gadget saves the day.

tekrhino said:
Same thing happened to me when I tried to mess with the NFC hack on my SGS III.
What saved me was a USB Jig I happened to have handy when I...accidentally... soft bricked a friend's Samsung Captivate a few months back. The USB Jig is used to put the SGS III into download mode when all else fails that tiny little gadget saves the day.
Click to expand...
Click to collapse
I have looked into those and will most likely make one very soon. (I think I have everything I'd need, just may need to cobble some resistors together).
Couple of things I noticed throughout this 'process', regarding the CM10 (9-15 nightly) ROM, NFC and google wallet....
At first install of CM10 I noticed that NFC was active and working normally. It could read my tags without issue. After Wallet was installed though, NFC disappeared. It wasn't just disabled, it simply wasn't there any more. It was after noticing this that I decided to reboot, at which point my original problem started.
The reboot never came close to completing though, it shut down before it actually made it to the 'boot' phase, as in, while it was shutting down.
The actual cause of the power off is still a mystery to me, as I can't see a simple app change causing hardware failure.

So you bricked your phone, just like a few of us did yesterday.
What did you call Verizon saying in order for them to send you a new phone?

AB_ said:
So you bricked your phone, just like a few of us did yesterday.
What did you call Verizon saying in order for them to send you a new phone?
Click to expand...
Click to collapse
I told them what happened, just left out a few bits of info.
"I rebooted it, and it never came back on." and that was that.

Nice.
I should have gone that method, but ended up paying for the repair service from MobileTechVideos

A friend has the qhsusb-dload showing up as well.. phone won't turn on.. flashed a bad kernel or rom I forget which.. red light comes on.. that's it.. its a Verizon i535 .. tried the resistor jig and nothing happens.. any ideas to fix?
---------- Post added at 12:03 PM ---------- Previous post was at 11:59 AM ----------
Guess he had aokp rom then flashed neak kernel and that's when it died..

[Q] Sidekick 4g Bootloop Please Help!!!

I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help

Use heimdall n hold the volume buttons n enable flash bootlaoders
Sent from my SGH-T959V using xda app-developers app

@karose465 How old is the phone? If less than a year (doubtful), it should still be under warranty. Or you may be eligible for upgrade pricing: Fore example, "Customers with a Classic plan (two-year contract) are eligible for our lowest upgrade price on a new phone when at least 22 months have passed since their last phone upgrade. A new two-year contract is required to take advantage of best upgrade pricing. Of course, you can always upgrade a phone at any time, regardless of how many months have passed since your contract began."
For more info on Heimdall, just Google Heimdall Android.

Anyone with a sidekick contract ends earliest next march..

karose465 said:
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Click to expand...
Click to collapse
Try Odin...choose repartition and you're golden. This is someone that has bricked his phone many, many times. Odin will give you the original stock Froyo.

RicAndroid said:
Try Odin...choose repartition and you're golden. This is someone that has bricked his phone many, many times. Odin will give you the original stock Froyo.
Click to expand...
Click to collapse
I think for him and myself, the biggest problem is being unable to get the phone to stay in download mode. For some reason, the battery won't charge and the phone itself continously turns off and on when plugged in. So the charge isn't holding, therefore nothing will stay on/open.

Im having the same problem. I have searched everywere and cannot find an answer that will fix it. If anyone can please help us fix this issue.
Sent from my MyTouch 4G using xda premium

gamingwiz said:
Im having the same problem. I have searched everywere and cannot find an answer that will fix it. If anyone can please help us fix this issue.
Sent from my MyTouch 4G using xda premium
Click to expand...
Click to collapse
I did some forum searching and found this. Hope it helps.
http://forum.xda-developers.com/showthread.php?t=1477838

Thanks ill check into that
Sent from my HTC Glacier using xda premium

karose465 said:
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Click to expand...
Click to collapse
Hmm here is a link with for the ODIN and also provides some pretty cool roms that you might like to try.
http://forum.xda-developers.com/showthread.php?t=1538576
---------- Post added at 04:33 PM ---------- Previous post was at 03:41 PM ----------
karose465 said:
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Click to expand...
Click to collapse
Hmm here is a link with for the ODIN and also provides some pretty cool roms that you might like to try.
http://forum.xda-developers.com/showthread.php?t=1538576

Took the phone apart, put everything back. Still no luck
Sent from my HTC Glacier using xda premium

EpicLordPhone said:
Took the phone apart, put everything back. Still no luck
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.

Power Button Repair relating to Boot Loop
MythEdge said:
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Click to expand...
Click to collapse
my Sidekick 4G is very old and just now went into bootloop... i googled the word and came across this forum.
As quoted above by previous poster that a power button repair was needed... I figured that I had nothing to lose, it being so old, I smashed the crap out of the Sidekick 4G on its power button. Lo and Behold, it booted into the system successfully.
SO... if no one has any qualms about smashing the crap out of their power button... give it a shot. It worked for me.

MythEdge said:
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Click to expand...
Click to collapse
Thanks for the info, but is there anyway I could turn it on without the power button?
Sent from my Amazon Kindle Fire2 using xda app-developers app

EpicLordPhone said:
Thanks for the info, but is there anyway I could turn it on without the power button?
Sent from my Amazon Kindle Fire2 using xda app-developers app
Click to expand...
Click to collapse
I don't believe so ?
You can switch the power button to like the track pad or something but you need to edit the phones ettings somehow
Sent from my SGH-T839 using xda app-developers app

immorality said:
I don't believe so ?
You can switch the power button to like the track pad or something but you need to edit the phones ettings somehow
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
Hmmm thanks, I might just try that!
Sent from my Amazon Kindle Fire2 using xda app-developers app

Mines stuck in a boot loop too.
I don't know if my Sidekicks problem is related to this or not. I rooted it and flashed it over to Glorious Overdose v5 on May 22nd this year and it's been running great. At least it was until last Friday, Sep 13. I was having trouble connecting to the WiFi at my house so I rebooted the phone. When it started to come back up a female voice started saying, "VooDoo lagfix has been disabled." "Converting /data and /system partitions." "Conversion time estimated 10 minutes."
I let it do it's thing and that's all it's been doing all weekend. I can get into recovery mode, I've tried restoring the phone from my backup with no success. I've even tried running through the process of setting up GOv5 again and it says it's successful, but the phone never boots up. It just stays in the same blasted bootloop and saying the same things over and over again about VooDoo. I've checked the VooDoo logs and there is an error file for the 13th and the logs following say "conversion." Can someone point me in the right direction as to what I can do to get my phone working again? Everything I've tried to research so far hasn't worked.

v5 hold both volume button, the track button and power button. Should put you into recovery mode. If not, you will have to put phone into download mode. You do this by taking out battery, then pluging into computer. When you reinsert battery hold volume down and power, if I remember correctly, and your download screen should come up. From your cp manually unroot it. Then it should be fixed, and just reroot it. I hope this was helpful
Sent from my SGH-T839 using xda app-developers app

No idea what I'm doing, precisely, but...
MythEdge said:
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Click to expand...
Click to collapse
Hey, MythEdge. I'm not sure if you get notifications here or anything, but I registered to this site specifically to thank you; my phone ( Sidekick 4G, like OP ) bricked, and I smashed it against the table a few times ( you know, delicately... ) and it resurrected.
So thank you, sir; you were precisely correct. It worked on both of my phones, which had the exact same problem.
Just, wow. Thank you.

LathyrusRoots said:
Hey, MythEdge. I'm not sure if you get notifications here or anything, but I registered to this site specifically to thank you; my phone ( Sidekick 4G, like OP ) bricked, and I smashed it against the table a few times ( you know, delicately... ) and it resurrected.
So thank you, sir; you were precisely correct. It worked on both of my phones, which had the exact same problem.
Just, wow. Thank you.
Click to expand...
Click to collapse
And almost a year later I log in and see this. Your most welcome. I haven't been working on phones for awhile but if I remember right, some models can be powered on by plugging the phone into a power source and when the phone vibrates or has a sign of life unplugging the unit. Some cables don't work and sometimes doing this via a computer can power up a device. Other than that, the other more dangerous way is to short out the pins on the bottom of the unit. I don't remember the pins but you can google a charge port diagram to help. I don't recommend doing this unless you have absolutely no other choice. Incidentally, this is why a phone will power itself on when a battery is put in and no other button is touched. The port is wet and corrosion has caused a link on the power pin and believe its pin 3. A simple cleaning with 90%+ rubbing alcohol solution will fix if cleaned quick enough.

[Q] Bricked? And why?

So I am running cleanrom 5.5.1, unlocked bootloader and original first leak radios. I was texting and all the sudden bam. rebooted to a black screen. Can't access download mode or recovery. The Samsung logo pops up followed by the s3 logo, then a dimly lit black screen that never ceases till battery pull. When I try download mode, some blue text pops up in the upper left hand corner, then reboots to logo screens then back to black screen. Also, when I pull battery and put it back in, plug in a charger and the battery icon appers on screen. When it goes dark I can wake it with the menu button and see the battery icon again. Any suggestions? If not fixable, would I be able to get a replacement from verizon? (I bought the phone less than a month ago renewed contract. Any help is much appreciated!

If the blue text is popping up your trying recovery, not download mode. Pull battery put it back in then hold volume down , home, and power until the download mode warning shows up
Sent from my SCH-I535 using xda app-developers app

kintwofan said:
If the blue text is popping up your trying recovery, not download mode. Pull battery put it back in then hold volume down , home, and power until the download mode warning shows up
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
i too just ran into the black screen after flashing an aosp kernel running slim 3.1 and im trying this way of getting into recovery and i hold down volume home and power and it still boots normally. i think i soft bricked my phone because i see the samsung logo but i never get to a bootlogo and only the hardkeys light up. im losing my damn mind and dont know what to do! i know its fixable cause i can see the samsung logo but i dont know what to do because the three finger salute wont work to get into recovery and i know that my bootloader is unlocked. not trying to thread jack just figured itd be pointless to post a new thread when the op is having virtually the same problem -___- lol go figure the first day i have my s3 i do this ****.. good thing i still have my nexus til i get it fixed.

Deltadood24 said:
i too just ran into the black screen after flashing an aosp kernel running slim 3.1 and im trying this way of getting into recovery and i hold down volume home and power and it still boots normally. i think i soft bricked my phone because i see the samsung logo but i never get to a bootlogo and only the hardkeys light up. im losing my damn mind and dont know what to do! i know its fixable cause i can see the samsung logo but i dont know what to do because the three finger salute wont work to get into recovery and i know that my bootloader is unlocked. not trying to thread jack just figured itd be pointless to post a new thread when the op is having virtually the same problem -___- lol go figure the first day i have my s3 i do this ****.. good thing i still have my nexus til i get it fixed.
Click to expand...
Click to collapse
Well you're right. Since you get life it's fixable. I would say pull your battery for a little while. Put it back in then hold volume down, home and while holding them both hold power. Your phone should boot into Odin mode.
Back stock for now....YUCK!

I had exactly what your describing
jndd333 said:
So I am running cleanrom 5.5.1, unlocked bootloader and original first leak radios. I was texting and all the sudden bam. rebooted to a black screen. Can't access download mode or recovery. The Samsung logo pops up followed by the s3 logo, then a dimly lit black screen that never ceases till battery pull. When I try download mode, some blue text pops up in the upper left hand corner, then reboots to logo screens then back to black screen. Also, when I pull battery and put it back in, plug in a charger and the battery icon appers on screen. When it goes dark I can wake it with the menu button and see the battery icon again. Any suggestions? If not fixable, would I be able to get a replacement from verizon? (I bought the phone less than a month ago renewed contract. Any help is much appreciated!
Click to expand...
Click to collapse
I had just rooted and flashed Jellywiz the previous day. The next day at work, I don't know why, but I must have experienced some kind of massive battery drain. The phone would not reboot, I would plug it in and it would just vibrate and flash the battery sign on the display every few moments. I had to put the phone on a charger for about 15 minutes and let the battery charge until I was even able to get the phone to boot. I would not boot while plugged into an AC charger until I let it charge. Very weird, and it hasn't happened again since but I swore that my phone was bricked. Basically the battery was so dead it wouldn't boot the phone, let it charge with out ****ing with it for a while and then try and boot it up.

kintwofan said:
Well you're right. Since you get life it's fixable. I would say pull your battery for a little while. Put it back in then hold volume down, home and while holding them both hold power. Your phone should boot into Odin mode.
Back stock for now....YUCK!
Click to expand...
Click to collapse
I don't know how to use Odin I did the non odin way to root lol I can get into download mode tho so apparently its fixable thank god. I feel like a noob right now I didn't ever do anything like this on my nexus or tbolt and then the first day I do it on my s3 -___- guess I gotta read up on Odin
Sent from my Galaxy Nexus using Tapatalk 2

Deltadood24 said:
I don't know how to use Odin I did the non odin way to root lol I can get into download mode tho so apparently its fixable thank god. I feel like a noob right now I didn't ever do anything like this on my nexus or tbolt and then the first day I do it on my s3 -___- guess I gotta read up on Odin
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Odin is easier then it seems, but make sure you know what you're doing because you can brick your phone with it. However, there is a great guide right here on how to unbrick your phone. Just follow section 5, I did it last night(to just clean up my phone)
http://forum.xda-developers.com/showthread.php?p=28530394
Sent from my SCH-I535 using xda app-developers app

kintwofan said:
Odin is easier then it seems, but make sure you know what you're doing because you can brick your phone with it. However, there is a great guide right here on how to unbrick your phone. Just follow section 5, I did it last night(to just clean up my phone)
http://forum.xda-developers.com/showthread.php?p=28530394
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So do I need to do all the steps in section 5 including flashing the radios if I never messed with them prior to rooting?
Sent from my Galaxy Nexus using Tapatalk 2

Deltadood24 said:
So do I need to do all the steps in section 5 including flashing the radios if I never messed with them prior to rooting?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You may want to double check section 5 it's one file that includes the entire stock ROM including a locked boot loader and the radios that match.
Sent from my SCH-I535 using xda app-developers app

kintwofan said:
You may want to double check section 5 it's one file that includes the entire stock ROM including a locked boot loader and the radios that match.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Oh okay thank you man! Sorry to thread jack op! I'll check it out
Sent from my Galaxy Nexus using Tapatalk 2

thanks guys
The first several times nothing would work not even download mode, my recovery console was gone too. after several tries download mode popped up so I immediately hooked up to odin and reflashed a stock root. all good now. Still wonder why it borked itself in the first place. Seems to be a mystery but I'm not too keen on flashing cleanrom 5.5.1 again...

jndd333 said:
The first several times nothing would work not even download mode, my recovery console was gone too. after several tries download mode popped up so I immediately hooked up to odin and reflashed a stock root. all good now. Still wonder why it borked itself in the first place. Seems to be a mystery but I'm not too keen on flashing cleanrom 5.5.1 again...
Click to expand...
Click to collapse
i couldnt get odin to work on my computer for some reason and after searching through google i found a forum on getting into the stock recovery and figured id try it and my phone decided to cooperate and go back to clockworkmod after all that and now my phone is fixed lol technology..

No worries about jacking thread I'm glad my post lead others to help another with not the same but similar issues. I've been out of the dev circle since g1 days but I think its time to play around and execute some system dumps after a bit of tweaking. definitely like Odin! All in one multi partition flaher! Fashing via adb used to be too cumbersome with the early sdk's!
Sent from my SCH-I535 using xda app-developers app

Yeah I got a lot to learn about programs its crazy how much stuff there is to know and things constantly get added every day lol the android community is very interesting that's for sure
Sent from my SCH-I535 using Tapatalk 2

Restored to Factory, Phone is freaking out, Screaming/Rebooting every couple seconds

Okay, So ive been banging my head against the wall for 2 days straight now with this problem so ive finally come to post about it to see if anybody has ANY idea how i can fix this. I have searched high and low for anyone who has come across this problem and i cant find another poor soul stuck in this predicament.
I have the D850, and have had it since last July. It was Bumped the day that it came out and ive been happily running roms on it since. I have honestly probably tried every ROM that was ever released for this phone, never had any issues.
I had flashed back to stock maybe a few weeks ago bc i had never done so, and after flashing a million roms i figured id try out straight stock for the first time in a year. SO i flashed the kitkat stock rom, and booted up everything was fine, then there was maybe 2 updates that i did OTA. I knew lollipop was out so i updated to that and all was well. I eventually got weary of straight stock quickly so i rooted and installed some of the fun stuff. Now this is where i noticed something i hadn't had before- when i would boot into TWRP i would get an unsecured boot error: error 1300- or at least i think that's what it said...Everything would flash fine and boot up so i didn't think much of it, but now that im having the issues im having, i think this is where it stems from.
Fast forward to 2 days ago- i figured i would flash back to 100% stock because i will be receiving my 6P next week and was going to donate this phone to my aunt bc i have taken such good care of it i figured id hand it down to a needy relative instead of get $20 bucks for it on ebay- All goes well i get the Blue screen with the 3 on it, pull battery and reboot. Everything seems normal..att logo...welcome screen..i go to touch the screen and its frozen. then reboots. weird. it does this a few more times, sometimes staying alive for up to 3 mins before freezing and rebooting again. Sometimes it even screams at me- no joke- it will freeze and make a high pitch screeching noise then shut down. scared the Sh*t out of me the first time it did it.
Ive tried everything people...i have downloaded fresh tot files/tried 5 different computers/fresh installs of flashtool/LG PC suit/hard reset/ran in safe mode/changed flash settings form upgrade to Board- to no avail. I honestly don't know how the phone hasn't died yet bc i think ive flashed the thing 30 times in the last 2 days from various computers. Remember- every time i flash in flash tool it passes, its only when it boots back up that it freezes/screams/reboots.
Sorry for the long winded post, but i wanted to give you some context. I'm going to try and mess around with it some more today but i keep getting closer and closer to throwing it off the wall bc this is frustrating. I think my problems would be solved if there was a lollipop tot file to flash, but i looked around and couldn't find anything. Thanks for reading everyone, any ideas are welcome. I'm out of warranty so ill try ANYTHING to fix this. At this point even if i FUBAR it i don't gaf bc its broken right now anyways. Any ideas are welcome. Thanks guys and i hope this never happens to you

Wickidmasshole said:
Okay, So ive been banging my head against the wall for 2 days straight now with this problem so ive finally come to post about it to see if anybody has ANY idea how i can fix this. I have searched high and low for anyone who has come across this problem and i cant find another poor soul stuck in this predicament.
I have the D850, and have had it since last July. It was Bumped the day that it came out and ive been happily running roms on it since. I have honestly probably tried every ROM that was ever released for this phone, never had any issues.
I had flashed back to stock maybe a few weeks ago bc i had never done so, and after flashing a million roms i figured id try out straight stock for the first time in a year. SO i flashed the kitkat stock rom, and booted up everything was fine, then there was maybe 2 updates that i did OTA. I knew lollipop was out so i updated to that and all was well. I eventually got weary of straight stock quickly so i rooted and installed some of the fun stuff. Now this is where i noticed something i hadn't had before- when i would boot into TWRP i would get an unsecured boot error: error 1300- or at least i think that's what it said...Everything would flash fine and boot up so i didn't think much of it, but now that im having the issues im having, i think this is where it stems from.
Fast forward to 2 days ago- i figured i would flash back to 100% stock because i will be receiving my 6P next week and was going to donate this phone to my aunt bc i have taken such good care of it i figured id hand it down to a needy relative instead of get $20 bucks for it on ebay- All goes well i get the Blue screen with the 3 on it, pull battery and reboot. Everything seems normal..att logo...welcome screen..i go to touch the screen and its frozen. then reboots. weird. it does this a few more times, sometimes staying alive for up to 3 mins before freezing and rebooting again. Sometimes it even screams at me- no joke- it will freeze and make a high pitch screeching noise then shut down. scared the Sh*t out of me the first time it did it.
Ive tried everything people...i have downloaded fresh tot files/tried 5 different computers/fresh installs of flashtool/LG PC suit/hard reset/ran in safe mode/changed flash settings form upgrade to Board- to no avail. I honestly don't know how the phone hasn't died yet bc i think ive flashed the thing 30 times in the last 2 days from various computers. Remember- every time i flash in flash tool it passes, its only when it boots back up that it freezes/screams/reboots.
Sorry for the long winded post, but i wanted to give you some context. I'm going to try and mess around with it some more today but i keep getting closer and closer to throwing it off the wall bc this is frustrating. I think my problems would be solved if there was a lollipop tot file to flash, but i looked around and couldn't find anything. Thanks for reading everyone, any ideas are welcome. I'm out of warranty so ill try ANYTHING to fix this. At this point even if i FUBAR it i don't gaf bc its broken right now anyways. Any ideas are welcome. Thanks guys and i hope this never happens to you
Click to expand...
Click to collapse
If it's making noise and freezing after flashing, that sounds like an hardware issue. Since you've already tried reflashing it several times and it still does it nothing else can really be done. You can try selecting board_id in flash tool at the tot selection screen and try that.
Also I always gotten secure boot error when booting into twrp on my LG phones I've rooted and loaded twrp on them.
Sent from my iPhone using Tapatalk

hyelton said:
If it's making noise and freezing after flashing, that sounds like an hardware issue. Since you've already tried reflashing it several times and it still does it nothing else can really be done. You can try selecting board_id in flash tool at the tot selection screen and try that.
Also I always gotten secure boot error when booting into twrp on my LG phones I've rooted and loaded twrp on them.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Yea man i tried that and it it boots into a screen that says DO NOT TOUCH SCREEN and then just continues to boot to that and i get a fail on the flash tool . thanks for your tutorial btw, thats what i used for all this troubleshooting. i found a thread about actually taking the phone apart and shorting it out and then trying to flash. i am going to give that a try if i cant get this f0cker to boot up correctly.

wait- did you mean select board DL?

Wickidmasshole said:
Yea man i tried that and it it boots into a screen that says DO NOT TOUCH SCREEN and then just continues to boot to that and i get a fail on the flash tool . thanks for your tutorial btw, thats what i used for all this troubleshooting. i found a thread about actually taking the phone apart and shorting it out and then trying to flash. i am going to give that a try if i cant get this f0cker to boot up correctly.
Click to expand...
Click to collapse
When it continues to boot what happens? Flash tool is supposed to fail.. Once the phone is out of download mode flash tool will fail as its done and has no connection. Once flash tool hits 80/85% its done. Never heard of the LG phone and taking it apart to short it out. That would be something if you had a brick and the phone doesnt go into download mode.

hyelton said:
When it continues to boot what happens? Flash tool is supposed to fail.. Once the phone is out of download mode flash tool will fail as its done and has no connection. Once flash tool hits 80/85% its done. Never heard of the LG phone and taking it apart to short it out. That would be something if you had a brick and the phone doesnt go into download mode.
Click to expand...
Click to collapse
so it faild out at 89%, then the miniOS screen comes up, but then it just keeps boot looping into the AAT-mini OS 3.1 screen where it says AUTO TOUCH TEST dont touch screen!!

Wickidmasshole said:
so it faild out at 89%, then the miniOS screen comes up, but then it just keeps boot looping into the AAT-mini OS 3.1 screen where it says AUTO TOUCH TEST dont touch screen!!
Click to expand...
Click to collapse
Strange. But yeah once phone reboots it's done. Flash tool percent means nothing. But very strange.
Sent from my iPhone using Tapatalk

hyelton said:
Strange. But yeah once phone reboots it's done. Flash tool percent means nothing. But very strange.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
oh well it was a great phone while it lasted. Thanks for the input.