Database Info

Taking the risk of GB radiofor the sake of science.

Just talked to a friend from vzw, he told me that if something happened he will hook me up with a replacement for my tbolt.
I've been using gb radio since the 1st day it was leaked, i have no problems on my phone, just some random FCs but that's given.
Since we don't have a solid demographics on how many people got bricked, Im going to take the risk and see if i get bricked.
This morning i just got into a bootloop but looks like its just the battery giving false stats. Its been more than 6 hours now in my external charger and i assume battery doesn't hold charge anymore, Im going tommorow to vzw to have it replaced.
Question is, will logcat be enough to monitor my phone in case i got bricked so i can pull some important data regarding how it happen?, that way we can find a clue on how to fix a radio-bricked tbolt.

Have you cleared battery stats under cwr advanced?
Sent from my ADR6400L using XDA Premium App

Wow. Very cool that you're willing to do this. Looking forward to seeing what you find out.

dopediculous said:
Have you cleared battery stats under cwr advanced?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
From what I've read, that's not possible as the bootloop happens even booting into recovery.

kudos to you. I would not do it. Thats a 600 dollar risk you are taking there.

dopediculous said:
Have you cleared battery stats under cwr advanced?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Yes i have cleared my battery stats. My previous battery is now dead. I think i discharged it too much, now its not holding any charge. My phone still runs on gb bamf and loving my lockscreen. Will let you know if i get bricked.
Sent from my ADR6400L using XDA App

i too am sticking it through, im too in love with this to revert back.

yakitori2 said:
kudos to you. I would not do it. Thats a 600 dollar risk you are taking there.
Click to expand...
Click to collapse
Lol you obviously didn't read his post. No risk involved.

I hope someone could shed a light to my questions.
1st. How does the radio firmware work on our phone? Does it work like a driver where it acts a mediator between the roms(software) to the phone's hardware.
2nd. What are the possible trigger to recreate the bootloop of death? There are some cases that my phone overheats because of non responsive apps and ever since i flashed on GB rom there i times i can feel my phone hot, which could be the case from some of the boot loop victim that they fried something inside their phone.
3rd. What are the chances that same bootloop of death could also occur in froyo radio? Just because vzw officially released the radio doesn't mean it has same risk like the leaked GB radio. It is like how HTC manufactured the phone, they tested most of it but some are still lemons.
Everything is in theory right now, there are no fix because it happens in random and the reason is still unknown. I'd choose to participate for the fix instead of waiting for someone to figure out the fix. We all do take a bold step in rooting our phone, flashing different roms, putting our faith on the battery that it wouldn't fail during the flashing process. Once we modified our phone from its stock settings we acknowledge the risk, and that risk is the one of the few factors the fuels the development of the rom/kernel community.
I've noticed several repacks of the GB radio:
http://www.multiupload.com/HU471CMQI0 ----
MD5: EE2A824E51CB148A2256F93E30A3B9F9
http://www.worldofjohnboy.com/dhemke17/ROMFiles/PG05IMGGB.zip ---- MD5: fda2a314975dd829b4e3611ecc8cfa13
PG05IMG_gingerradio.zip <- from http://forum.xda-developers.com/showthread.php?t=1082001 links alread removed. This is the same radio from androidpolice.com----
MD5: 52DD83AA40E30186C9FBEFAFD1BAB534
For the record, i flashed mine with the MD5: EE2A824E51CB148A2256F93E30A3B9F9
right now im using das bamf 2.0-5 running on imoseyon_leanKernel_v2.5.4GBtest6
Im keeping a close watch on my temp running on "extreme settings" 1.4ghz extremely undervolt.
SetCPU profile set to minimum setting when temp goes more than 97F

I just called verizon 611. My phone is not bricked and still functioning properly, but i told the operator that my phone constantly reboots( I pretended that my phone was bricked), i was passed to higher level tier support and they said they will be sending a new phone to me and there will be an extra envelop where i need to put my old phone to return to them. The call only took me 10-15 minutes and I believe VZW is aware that Tbolt has this issue even if its GB or the stock froyo rom.

i reverted back last night but i will def be back once things are more stable.. i already miss it

Phone keeps powering down?

So my just powers off, doesn't matter what state the battery in. It does not reboot. It just turns off. I have no idea what is causing this and I have been running this setup for awhile now without problems.
ROM: BAMF Stripped 1.7
Kernel: leanKernel 1.92x
Any ideas?

engagedtosmile said:
So my just powers off, doesn't matter what state the battery in. It does not reboot. It just turns off. I have no idea what is causing this and I have been running this setup for awhile now without problems.
ROM: BAMF Stripped 1.7
Kernel: leanKernel 1.92x
Any ideas?
Click to expand...
Click to collapse
You're burning up the CPU from overclocking it?
Asside from that obvious first, thought. I'm leaning more and more towards the fact that these sd cards are having issues wiping the info off of them. You know, the one that comes with the phone that's 32GB.
I've noticed that with mine I keep having issues seeing partitions and wiping old information off of the sdcard for that matter.
I won't delve to much in to details but I know for a fact that a couple of times that I've told my phone to wipe info from the sdcard, it leaves stuff behind and i tshows when I boot up in to my freshly installed ROM what ever it may be at the time.
I've even gone as far as booting in to gparted only to see that it doesn't see the partition...

thewebsiteisdown said:
You're burning up the CPU from overclocking it?
Asside from that obvious first, thought. I'm leaning more and more towards the fact that these sd cards are having issues wiping the info off of them. You know, the one that comes with the phone that's 32GB.
I've noticed that with mine I keep having issues seeing partitions and wiping old information off of the sdcard for that matter.
I won't delve to much in to details but I know for a fact that a couple of times that I've told my phone to wipe info from the sdcard, it leaves stuff behind and i tshows when I boot up in to my freshly installed ROM what ever it may be at the time.
I've even gone as far as booting in to gparted only to see that it doesn't see the partition...
Click to expand...
Click to collapse
I have caught it saying that the SD card was inaccessible but I don't see why that would make it power down. I lowered the overclock back down to 1.4ghz to see if it helps.

Just curious.. but are you running the "new" radio that came out with the OTA update? (Obviously not the official OTA, but the leaked version? and no I don't mean GB radio).
Hubby's phone started doing this after he got the OTA. I wasn't even rooted at the time but the new radio started causing his phone to shut down. Mine which was rooted and had received the leaked and rooted version of the OTA was rebooting at random times throughout the day.
This weekend I flashed them both back to the previous radio (Combo #2 in the obligatory radio post) and they've been running ever since with no shutdowns or reboots.

engagedtosmile said:
I have caught it saying that the SD card was inaccessible but I don't see why that would make it power down. I lowered the overclock back down to 1.4ghz to see if it helps.
Click to expand...
Click to collapse
I have mine set to 1.4. There's no reason besides for epenus to really go over that IMO. You don't want to burn the CPU up. Even at 1.4 you need to find out if it likes to be undervolted or uber undervolted as well. Mine was happy with uber undervolt then on the next couple kernels that came out that changed to the undervolted so..
That part is a crap shoot. The sd card is deffinately causing some funky behavior IMO. Probably not shutting down like you said but funky things none the less and I really wish I could get a better handle on it.
I had a program the other day on my computer that seen the partitions fine and now none of them do that I try. I don't know if I'm using the wrong app now or what...
I'm busy getting ready to move in to a house right now though so I'll get to it more later I suppose for now I'm chilling on GB.
I agree with Sam as well a little I suppose but Sam, factory resetting the phone is supposed to fix the new ota update issue or atleast it did for my wifes phone. That was per HTC's advice that we tried that with hers and hers is unrooted not even touched and it stopped it so..
Some people say it didn't work for them but that's neither here nor there..

thewebsiteisdown said:
I have mine set to 1.4. There's no reason besides for epenus to really go over that IMO. You don't want to burn the CPU up. Even at 1.4 you need to find out if it likes to be undervolted or uber undervolted as well. Mine was happy with uber undervolt then on the next couple kernels that came out that changed to the undervolted so..
Click to expand...
Click to collapse
I play a lot of PSX on my phone and the few FPS helps sometime. Also helps with the audio becoming choppy.
And yes, this is the leaked radio but I have been using it since day one. I lowered it to 1.4ghz and I think was it. The rise in temperature outside probably wasn't helping.

engagedtosmile said:
I play a lot of PSX on my phone and the few FPS helps sometime. Also helps with the audio becoming choppy.
And yes, this is the leaked radio but I have been using it since day one. I lowered it to 1.4ghz and I think was it. The rise in temperature outside probably wasn't helping.
Click to expand...
Click to collapse
Sweet glad I could help. You should thank me and Samxxx .

thewebsiteisdown said:
Sweet glad I could help. You should thank me and Samxxx .
Click to expand...
Click to collapse
It happened again last night so it wasn't the OC afterall, I am on the stock radio now.

Happened again with stock radio, I'm out of ideas as to what is causing it.

engagedtosmile said:
Happened again with stock radio, I'm out of ideas as to what is causing it.
Click to expand...
Click to collapse
Mine did this a couple times. I read some stats and realized it was reading the battery as dead when it would happen. So I took the battery out and made sure it was in firmly and correctly, made sure the battery door was on tight and it never happened again.

Is the phone actually powering off or is it just not waking up? If its not waking up then its just undervolted to much. I would try another kernel that's not as undervolted.
Sent from my ADR6400L using XDA Premium App

dlongb13 said:
Is the phone actually powering off or is it just not waking up? If its not waking up then its just undervolted to much. I would try another kernel that's not as undervolted.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Powers off completely.
I think I found the issue, it's the hardware. If I put any pressure on it or if it bends a little, it will power off like its shorting out. (Happens mostly in my pocket while sitting.) Going to talk to verizon about it.

Bad thing is you don't like to use the thank you button so I won't be helping you any more at this point.

thewebsiteisdown said:
Bad thing is you don't like to use the thank you button so I won't be helping you any more at this point.
Click to expand...
Click to collapse
lol okay.
heres your thanks.
Thanks.

My phone seems to be having a similar issue. I'm running BamfGingerRemix 2.1, the MR2 radio, with Nerozehl's Dream Kernel, overclocked to 1.4Ghz, and with swap enabled. The low clock speed is 368.
I have no idea what is causing it, but I'm pretty sure the phone is actually off. I have to do a battery pull before I can get it to boot. This has happened 3 times over the past 3 days. If it happens again, I'm going to call myself from my roommate's phone to see if it is truly off.
I know it isn't from the battery being too low because last night after I got it rebooted, the battery was at 99% (it was on the charger when I tried to wake it). I'm hoping this isn't a sign of something bad coming to my phone.

I've heard some people call this the sleep of death? I'm on aosp (both cm7 and OMFGB) and I've seen this a few times. Werid eh?
Edit: I'm on the 402w1 radio
Sent from my Thunderbolt using XDA Premium App

My phone would also not wake up a few times when I was running various BAMF Roms - I should note that I have only run their ROMs since rooting the phone. It seemed to happen a few minutes after sending a text, not every time but randomly. I haven't changed any of the defaults regarding overclocking, so it would seem strange if that was the reason. I also don't know if it was off, or if it just wouldn't wake up because I had to pull the battery to get it running again.
However, I have been running the newest 3.0 RC3 for a couple of days and haven't seen it happen at all.

[Q] Anyone have success fixing restart issues?

I've had my G2X for about a month, and have been experiencing the common issue where my phone randomly shuts off and the only way to get it to turn back on is to pull the battery.
I've installed the GB update, that didn't fix it. Factory reset didn't help either.
Has anyone successfully fixed this issue on their phone? If so, what'd you do? Is there any chance that rooting my phone would correct the problem?
Sorry if there was a post about this, I couldn't find anything talking about if anyone's been able to fix the problem.
Thanks

yes... the onlyhh way to fix the problem is to root! nvflash clock work mod recovery, then flash eagle blood 2.3.3 rom and it is perfect...

Thanks, this did indeed seems to do the trick. Not a single reboot so far after 2.5 days.
Sent from my LG-P999 using XDA App

My G2X actually restarted on its own today. It was the first time since the first few days I had the phone over a month-month and a half ago. Wasn't really a big deal, lol. It comes back on.

Have been playing with this phone for 3 days now and haven't had any issues (I did install xboarder's stock rooted version). Minor screen bleed is the only issue.
Sent from my LG-P999 using XDA Premium App

Finally, someone (dmaniscool) who can say they switched to an xda dev'ed ROM and got rid of the lock ups. I've posted many times asking if anybody ACTUALLY FIXED a problem (specifically the battery pull lock up); I got no responses, and someone finally stated it. Great. Next time my wife's G2x locks up, I'm rooting and putting a ROM on it.
Thank you dmaniscool
-Bob

so, PLEASE dmaniscool, occasionally update this thread with your lack of lock-ups, or if you get a lock-up. PLEASE!!!
Thanks,
-Bob

namklak said:
so, PLEASE dmaniscool, occasionally update this thread with your lack of lock-ups, or if you get a lock-up. PLEASE!!!
Thanks,
-Bob
Click to expand...
Click to collapse
Will do, so far so good! I had no experience with rooting, and was able to figure it out looking at the guides available on the forum. It kind of looks intimidating, but it's not actually very difficult.

By restart does everyone mean just shuts down? Mine never restarts, it will just shut off.
Sent from my LG-P999 using XDA App

RZJZA80 said:
By restart does everyone mean just shuts down? Mine never restarts, it will just shut off.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Mine did both actually, shut down and restarts. But mostly just shut downs, which required a battery pull to power back on.

My 2 will do both - but I think the "shut-off" is a lock up, because the longer I leave it locked up, the less battery I'll have after I do a battery pull.
8 days of both phones not locking up by doing one restart per day per phone.

Since I raised the minimum CPU speed to 389 from 216, I have far fewer sleeps of death
You don't wanna know where this was sent from.

I've tried every ROM and kernel combination possible and nothing actually fixes these problems for me.

Wow this post was scary at first, I had a thunderbolt and no matter what. RUU, Different ROMS, Stock, Kernels, Radios. Changing all that didn't matter it still turns off constantly and doesn't turn back on till I do it meaning no text or calls, basically same as having a phone on silent all the time without even having the luck chance of pulling it out while ringing.....

I am on miui x.26 (whatever kernal that comes with it) and have over 40 hours of uptime. I haven't had a crash yet, I just manually restart every couple of days because I'm weird like that.
Sent from my LG-P999

Well 6 days into it and I've had a total of 2 shutdowns. I don't know if it was a coincidence, but both times were after being outside when it was ~90 degrees out.
This is still much improved, I used to get 3-4 per day on average.
I'm using Eaglesblood 2.3.3. I'm thinking of trying MIUI because it's so nice looking.

For me I did a battery replacement the first time directly from T-Mobile and the phone continued restarting on me. I was just about to request a replacement phone from T-Mobile until I recently purchased a different brand of battery containing the same specs as the stock battery and to my surprise no overheating and definitely no restarts. I feel that the restarts and lockups are due to faulty batteries shipped out with the phones. I'm suprised no one has mentioned this.
Sent from my LG-P999 using Tapatalk

Do you mind sharing what brand battery you purchased?
Sent from my LG-P999 using XDA App

Wow, I told the CostCo kiosk girl I was having lock up problems and I had my grandkids with me. She took my phone and pulled the battery - at the same time my grandson stated he had to go to the bathroom NOW. She either looked at the battery or something on the phone under the battery. I didn't have time to ask. She didn't really comment and gave me my phone back.
Hmmmmmm........
-Bob

ok so do they know what exactly is causing the shut downs or reboot on this phone? i just got mine today and it was pre installed with gingerbread and idk if there is root for the gingerbread build yet. i just want root but no custom rom for me. i love the stock rom. it kicked the crap out of my sensation 4g as far as speed goes in everyday use.

Phone stuck after dead battery.

The past two nights I have fallen asleep with a close (30%) to dead battery only to wake up and realize it died. No biggie, my fault for not throwing it on the carger. I plugged it in and was stuck at the 'Samsung Galaxy SIII' screen. I was able to manually enter recovery and do the wipe/flash routine.
My question is, is this a symptom of a bad flash or root or something? Do I have to live in fear of a dead phone? I have never experienced this on my other phones, although I don't make a habit of letting the phone die, not withstanding the last two nights
I have since made a nandroid
I am on synergy r118.
Thanks.
Sent from my SCH-I535 using Tapatalk 2

enix316 said:
The past two nights I have fallen asleep with a close (30%) to dead battery only to wake up and realize it died. No biggie, my fault for not throwing it on the carger. I plugged it in and was stuck at the 'Samsung Galaxy SIII' screen. I was able to manually enter recovery and do the wipe/flash routine.
My question is, is this a symptom of a bad flash or root or something? Do I have to live in fear of a dead phone? I have never experienced this on my other phones, although I don't make a habit of letting the phone die, not withstanding the last two nights
I have since made a nandroid
I am on synergy r118.
Thanks.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Possibly Synergy 118...possibly a bad flash even tho you would have other symptoms as well. Just try to flash any other ROM and see what happens....but also if you just pulled the battery and tried to boot it again and did...then it's most likely just caused by the leaked JB it's not good but not that terrible either. good luck :fingers-crossed:

Thanks for the reply.
I will have to wait until this weekend to try another rom....
I would think if it's a synergy issue I would not be the first to find out.
My only other thought is the battery being too dead to do anything, even with wall usb plugged in. When I got my phone to boot after flashing it would show less than 15% charge.
I will try to troubleshoot it with different roms when I get a chance and post here with the results.
Sent from my SCH-I535 using Tapatalk 2

For anyone following this.
I have decided it is an app issue. I reflashed a fresh synergy rom. I am currently restoring apps a few at a time, rebooting,then making a nand everytime it boots ok.
I will let you know what app is doing this when/if i come across it.
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.