Related
I'm having difficulty flashing the rom (There may be an issue with the phone, not sure yet). The phone was at 99% and the upgrade died, I'm stuck at the 3 color red/green/blue with the USB connection. I think there is a way to fix this, but I forget. Can anyone point me in the right direction? Thanks!
alan1974us said:
I'm having difficulty flashing the rom (There may be an issue with the phone, not sure yet). The phone was at 99% and the upgrade died, I'm stuck at the 3 color red/green/blue with the USB connection. I think there is a way to fix this, but I forget. Can anyone point me in the right direction? Thanks!
Click to expand...
Click to collapse
What phone you got... G3, G4 ... CID Locked/Unlocked ?
G3, CID was unlocked a long long time ago. IPL/SPL 2.25 and it says RUU at the top right corner. I should of included the info, thanks for the help!
alan1974us said:
G3, CID was unlocked a long long time ago. IPL/SPL 2.25 and it says RUU at the top right corner. I should of included the info, thanks for the help!
Click to expand...
Click to collapse
Turn the phone off (pull the battery if you have to) and unplug the USB cable. Then turn it back on so its back at the bootloader screen (rainbow color bars screen you saw). Now plug in the USB cable. ActiveSync will NOT connect, but thats fine. You will see USB above the left soft key. Now flash an offical rom (either the Cingular 2.25 found on the HTC website, or T-Mobile 2.26).
Read this thread for details, steps and links:
http://forum.xda-developers.com/showthread.php?t=298613
Once you get back on an official rom, then you can reinstall whatever custom rom you want (but you need to get back to an official one first at this point).
alan1974us said:
G3, CID was unlocked a long long time ago. IPL/SPL 2.25 and it says RUU at the top right corner. I should of included the info, thanks for the help!
Click to expand...
Click to collapse
OK then...
Plug it into the usb, and when the bootloader appears, start flashing whatever rom you like...
Easy, right ?
hmm, it died again at 99% on the upgrade. I can do the official install w/no problem. Maybe I need to go back through the cid unlocker?
alan1974us said:
hmm, it died again at 99% on the upgrade. I can do the official install w/no problem. Maybe I need to go back through the cid unlocker?
Click to expand...
Click to collapse
Please forgive me for stating the obvious but you do know that it is normal to stall at 99% for a few minutes sometimes longer.... What do you mean by "Died at 99%"?
To be honest. You didn't said anything but typical wrong flash case...RUU from custom ROMs to another custom ROM(or having CIDlock probs) is good method for having 3bars relax time.
it's question of the day: what do You mean by "died @ 99%". when i am flashing anything, stalls up to 5 minutes @ ANY percent arent reason to PLUG CABLE OFF,or ANY manipulation on pc, or ppc. if it just stuck forever, its time to turn back to old ROM image, or just any rescue ROM, SO:
revert to old rom with ruu, then install 2 cabs from shelltool, wait 30 secs, reset, turn radio off, plug usb on, and after adding nk.nbf into shelltools directory, and spectacular launching earlier mentioned shelltool, and rtfm od its docs, you may start to do what you've just read.
while flashing DO NOT DO ANYTHING with machines.
After finished operation you will see end so it IS END.
Hard reset.
100% positive flashes, if net is turned off, firewall killed and antivirus turned off. also, remove sd card before flash.
btw, what's your IPL/SPL...
Sorry, I should of been more descriptive. The rom update gets to 99%, then hangs for awhile, then the update application on my computer says that there was a communications error and goes into a recovery instructions. The phone itself stays at 99% until I unplug the battery.
I'll try doing the revert back to old rom in the morning, it's a secondary phone and I left it at work.
I had this problem as well...
I ended up just flashing a stock rom multiple times until it finally took.
I think I had to do it at least 2, if not 3 times before I was finally able to boot the phone.
alan1974us said:
Sorry, I should of been more descriptive. The rom update gets to 99%, then hangs for awhile, then the update application on my computer says that there was a communications error and goes into a recovery instructions. The phone itself stays at 99% until I unplug the battery.
I'll try doing the revert back to old rom in the morning, it's a secondary phone and I left it at work.
Click to expand...
Click to collapse
So, you are experiencing this when trying to flash a stock rom.
Check if the RUU is not corupted. If you downloaded it now, it may also cause this.
Also...restart your PC and don't run anything in the bacground while flashing. Just to make sure.
alan1974us said:
Sorry, I should of been more descriptive. The rom update gets to 99%, then hangs for awhile, then the update application on my computer says that there was a communications error and goes into a recovery instructions. The phone itself stays at 99% until I unplug the battery.
I'll try doing the revert back to old rom in the morning, it's a secondary phone and I left it at work.
Click to expand...
Click to collapse
Also make sure you remove the SD card in your phone if you have one. I've seen flashes fail when SD cards are installed.
Ok, I reloaded the rom. I can't figure out the button rom, there is a screen with a bunch of ???? that come up and none of the buttons do anything. :\ I loaded the wizard love one, which loaded ok. I tried the crossbow reloaded but it hung at 99% again and the application went back into error recovery mode. Maybe I'm just not meant to have it! lol. I don't have the sim or sd card installed atm.
Oh ya, this is probably the most responsive/helpful forum I think I have ever seen.
..removed..
I've tried on a clean machine and still same thing. What happens at 99%? Could the phone itself have issues?
alan1974us said:
I've tried on a clean machine and still same thing. What happens at 99%? Could the phone itself have issues?
Click to expand...
Click to collapse
All the roms will hang at some point towards the end of the flash (official ones tend to hang around 85% or so. The cooked ones hang closer to 99%). This is the point where the final part of the flashing is occuring and I think there is verification that what was written checks out as being valid.
If you can get a rom on and the phone working, and then do a hardreset and that works, then I would say you do not have a hardware issue with your phone (at least not from the flashing side).
BTW: Crossbow Reloaded v1.5 is out now. Please try downloading it and flashing that one (just to see if it makes a difference for you). It is very odd that multiple roms stop at 99% on your like this (hard to say its a bad download).
Sorry, I haven't reread this entire thread, but have you tried this from a different computer? ALso try to turn off any firewall, VPN, or even antivirus software on your computer while you flash to see if that corrects the issue. I think I remember someone trying to go into Safemode one time to do a flash.
Then there is also stand on your head or wave a dead chicken over your head while the flash is happening.... (yeah, I'm grasping at straws on this one )
Lol, thanks. I downloaded the 1.5 and going to give that a wing.
People... pleas read throught the forums!!!
Its so annoying that people asks the same question again and again and again. Dont be so lazy, do your research, search the forum and dont post ST$#"D questions!!!
Gah, error 302 every time. I loaded buttons ROM, unlocked again, tried reloading rom, then BOOM 302! Maybe WM6 isn't meant for this phone.. lol I can load any WM5 or lower and have zero issues.
I started this thread as a constructive and positive place for those of us that have recently lost our G1's or ADP's. I am going to document all my settings, Radio version, Firmware, Build info, etc here and hopefully reverse engineer this issue until I have an answer. If anyone has any hardware engineering information on this device it would be greatly appreciated. I'm even willing to host a private forum from my site to work on this.
Thanks everyone for your continued hard work and Haykuro, you're still the man!
-JFv1.43 RC9 firmware (just did this one update, not the radio update)
-1 GB micro SD which was deliverd with the phone
-Google's Developers Edition
-rooted
-sim ulocked
-almost fully loaded about 80 % battery
-everything went fine, the update went fine, restarting, and then no response and always and always the same android screen,
now im trying to crash it by low battery, not by just take the battery out, maybe this'll work (but I dont think so)
don't know anything else
Partioned Fat32/EXT2 1GB SDcard from t-mobile
Flashed RC29 via Bootloader .NBH file
Rooted with RC29
Updated to RC33
Flashed Hard SPL
Flashed JF v1.5 ADP Lucid MOD - did APPs2SD and Dalvik2SD
Flash 2.22.19.26I Radio
Flashed Grafitti Citrus Theme JFv1.50 Beta
Flashed H Special SPL with battery at 89% - saw it update, rebooted on its own, saw the chip with the arrow on it and it rebooted. once after that it hanged. I waited 5 minutes and then took the battery out. Got my sdcard reader, renamed the jf v1.5 to update to reflash like instructed. powered the phone with home+power and got nothing but a hang on t-mobile G1 screen.
Both phones were done the same. One phone bricked and one phone flashed the SPL.
I wonder if the Dream responds to goldcards like other HTC phones do...
That's how we fixed our Heralds, which is how the Elf's got their fix, etc.
ivanmmj said:
I wonder if the Dream responds to goldcards like other HTC phones do...
That's how we fixed our Heralds, which is how the Elf's got their fix, etc.
Click to expand...
Click to collapse
Goldcard as in a specialized SIM?
d474rpr said:
Goldcard as in a specialized SIM?
Click to expand...
Click to collapse
Goldcards as in a specialized SD card
d474rpr said:
Goldcard as in a specialized SIM?
Click to expand...
Click to collapse
You convert a SD card into a Goldcard and the phone will read it and allow the phone to flash ANY NBH file, regardless of CID, etc etc.
MosquitoD4K said:
-JFv1.43 RC9 firmware (just did this one update, not the radio update)
-1 GB micro SD which was deliverd with the phone
-Google's Developers Edition
-rooted
-sim ulocked
-almost fully loaded about 80 % battery
-everything went fine, the update went fine, restarting, and then no response and always and always the same android screen,
now im trying to crash it by low battery, not by just take the battery out, maybe this'll work (but I dont think so)
don't know anything else
Click to expand...
Click to collapse
This has happened to me many times when I didn't wipe (the PHONE ). Take the battery out, place back in and hold Home + Power to get into menu. Type alt + w to wipe, afterwards, alt + s to apply update.zip from sdcard, then Home+Back to restart. The first time loading, it can take up to ten minutes to get past the Android screen (mine took 7-10 minutes), so be patient.
Post back with any results.
ivanmmj said:
You convert a SD card into a Goldcard and the phone will read it and allow the phone to flash ANY NBH file, regardless of CID, etc etc.
Click to expand...
Click to collapse
that wont work i just read the write up. In order for the goldcard to work, the g1 has to go into fastboot, which none of our devices can go into fastboot nor recovery. I even formatted a sdcard to start the process but when i got to the fastboot i was so disappointed.
One detail, when i flashed the new spl I was doing something else and when i check my phone it back to recovery utility windows itself ,it was in 15 20 minute, after that i reinstalle jf1.5 and all worked ok
what this means. if you are flashing your phone and before these process finishes your take out you battery, you can bricking you phone. take patience and wait.
Good luck
ps:i change the final text for sir*mez
sir*mez said:
that wont work i just read the write up. In order for the goldcard to work, the g1 has to go into fastboot, which none of our devices can go into fastboot nor recovery. I even formatted a sdcard to start the process but when i got to the fastboot i was so disappointed.
Click to expand...
Click to collapse
satru said:
One detail, when i flashed the new spl I was doing something else and when i check my phone it back to recovery utility windows itself ,it was in 15 20 minute, after that i reinstalle jf1.5 and all worked ok
what this means. if you are flashing your phone and before these process finishes your take out you battery, you and only you bricking you phone. take patience and wait.
Good luck
Click to expand...
Click to collapse
this happened to the one that bricked.
Flashed H Special SPL with battery at 89% - saw it update, rebooted on its own, saw the chip with the arrow on it and it rebooted. once after that it hanged. I waited 5 minutes and then took the battery out. Got my sdcard reader, renamed the jf v1.5 to update to reflash like instructed. powered the phone with home+power and got nothing but a hang on t-mobile G1 screen.
Both phones were done the same. One phone bricked and one phone flashed the SPL. So yes I guess I bricked one phone but a miracle happened with the other one. the one that flashed properly went into the recovery on its own right after the boot, but not in no 15-20 min wait like you said. you sure need to stop the blaming. i am not blaming anyone for my bricked phone, im just trying to find a solution. you are going to get this locked because of the bickering.
hey sir*mes was no my intentions blaming to anyone , i only want to say that all need to give more time to flash before take out the battery. only that.
i will do something for you , i will change the text, happy?
Good luck
sir*mez said:
this happened to the one that bricked.
Flashed H Special SPL with battery at 89% - saw it update, rebooted on its own, saw the chip with the arrow on it and it rebooted. once after that it hanged. I waited 5 minutes and then took the battery out. Got my sdcard reader, renamed the jf v1.5 to update to reflash like instructed. powered the phone with home+power and got nothing but a hang on t-mobile G1 screen.
Both phones were done the same. One phone bricked and one phone flashed the SPL. So yes I guess I bricked one phone but a miracle happened with the other one. the one that flashed properly went into the recovery on its own right after the boot, but not in no 15-20 min wait like you said. you sure need to stop the blaming. i am not blaming anyone im just trying to find a solution. you are going to get this locked because of the bickering.
Click to expand...
Click to collapse
sir*mez said:
that wont work i just read the write up. In order for the goldcard to work, the g1 has to go into fastboot, which none of our devices can go into fastboot nor recovery. I even formatted a sdcard to start the process but when i got to the fastboot i was so disappointed.
Click to expand...
Click to collapse
So what harm would it do to try? From what I remember the goldcard on herald was supposed to get us into the bootloader even when we couldn't normally.
Let me be perfectly clear, those of us with the issue of a bricked device from loading the SPL from Haykuro are experiencing an actual case of being bricked.
Read carefully.
The phone WILL NOT turn on!!!!
We are looking for a solution that runs as far back as actually burning the SPL image directly to the phone's memory. I am even willing to try a hardware to hardware method to accomplish this.
I know the phone is still somewhat responsive because my laptop detects the USB connection to the phone but it will not recognize the device.. obviously because the communication is broken since the phone is dead. The power LED will turn on but only after I remove the battery first. Once I press the POWER key the LED turns off and will not light again until I remove and replace the battery.
Solutions that we are trying:
GoldCard method.
Looks like a couple of us have tried this but since fastboot can't see the device then we can't use this method unless someone knows something super seceret.
Crashing the device by allowing the battery to fully discharge. Unlikely but trying anyway.
Any other ideas?????
Thanks everyone for helping thus far!
neoobs said:
So what harm would it do to try? From what I remember the goldcard on herald was supposed to get us into the bootloader even when we couldn't normally.
Click to expand...
Click to collapse
I tried it and so far no luck...
neoobs said:
So what harm would it do to try? From what I remember the goldcard on herald was supposed to get us into the bootloader even when we couldn't normally.
Click to expand...
Click to collapse
ok but the phone wont go into bootloader. which is what im trying to get it to do. if i get it to bootloader i know i can fix it. even if it went to the recovery i could fix it. but I get nothing.
in order to create a goldcard for the dream it has to read the sdcard off fastboot which i cant get into.
d474rpr said:
Let me be perfectly clear, those of us with the issue of a bricked device from loading the SPL from Haykuro are experiencing an actual case of being bricked.
Read carefully.
The phone WILL NOT turn on!!!!
We are looking for a solution that runs as far back as actually burning the SPL image directly to the phone's memory. I am even willing to try a hardware to hardware method to accomplish this.
I know the phone is still somewhat responsive because my laptop detects the USB connection to the phone but it will not recognize the device.. obviously because the communication is broken since the phone is dead. The power LED will turn on but only after I remove the battery first. Once I press the POWER key the LED turns off and will not light again until I remove and replace the battery.
Solutions that we are trying:
GoldCard method.
Looks like a couple of us have tried this but since fastboot can't see the device then we can't use this method unless someone knows something super seceret.
Crashing the device by allowing the battery to fully discharge. Unlikely but trying anyway.
Any other ideas?????
Thanks everyone for helping thus far!
Click to expand...
Click to collapse
Are you saying your screen doesn't turn on?
neoobs said:
Are you saying your screen doesn't turn on?
Click to expand...
Click to collapse
No, I'm saying it doesn't turn on.
d474rpr said:
No, I'm saying it doesn't turn on.
Click to expand...
Click to collapse
The same happens on Heralds when the imgfs is messed up. To fix it, we force it to go into the bootloader mode and it does turn on. I wonder if it's something similar.
I meantioned in the big main topic an idea though I dont think anyone saw it.
In the past for other phones I was able to make recoveries using the computer while it was in the boot loop.
Anyone with the brick, try to see what happens when you do this:
adb remount
After the "T-Mobile G1" screen shows up. See if it says mount sucessful. I would try though it does not stay on the screen too long for me, not only that it might work for me just because it continues fine so its inconclusive.
If you get lucky and it says remount successful, you could try this:
adb shell recovery
I am not sure of the commands to follow from there, but it might allow you to flash a different update.zip file from the command line. If you get lucky like that, look up the commands and see how that might go. There has to be a way to communicate to the hardware when that screen comes up. Its good that that screen comes up, because it means its not 'fried' so to speak, it just has a misconfigured loader which doesnt have the correct set of instructions (good point about the different types of boards, thats most likely the issue) for THAT board. I would go back to the one that worked previously.
OK so I followed all the instructions correctly on the video pertaining to performing a task 29 and my (U.S. T-mobile HD2)and is now only showing a white screen, with the t-mobile logo on it. The phone is unresponsive and doesn't have any connection drivers on it apparently because my computer wont recognize it at all. I am aware that it has no ROM on it but the video said that I could flash one with a boot loader but I haven't figured out how to do that yet im a lil new at this anyway I guess we all have to start somewhere... any help would be greatly appreciated
P.S. - i used HSPL3 and it worked fabulously when I flashed the Elegancia Rom. Then decided to try the maxsense ROM and tried task 29 and now this...
First you have to turn off the phone by removing the battery. Then enter the boot loader by holding down VOLUME DOWN button (keep holding) and pressing power on/off button for a sec or two. Keep holding vol. down untill you get into bootloader. It will be a tri-colored screen (Red, green, blue and white), one you have probably seen before. Then connect it via USB cable and flash your ROM. Make sure you have the proper radio for it.
I'm still a bit ''noobish'' myself, but that's what I think one is supposed to do. Pros please correct me if I'm wrong.
Nice! I got to the boot loader now I'm going to try and flash the rom I downloaded today, Man you are a lifesaver! I know it is a simple task to tha pros but I have to get through the trials and errors before i can get where they are lol PROS PLEASE BARE WITH ME!! Ill get back to ya after i attempt the flash thanks again!
It works! man i was freakin out for a minute and i ended up ordering another phone so now im gonna sell this one lol But i do have one other question, I downloaded the max sense Elegancia series Rom and it said i had to have a specific radio so i downloaded one of those that were provided with the program but when i opened it, it had a .NBH and a bunch of other files with it. I am wandering if I am supposed to copy all of those files to the custom RUU file along with the radio?
hello all,
I am new here and I have been searching the forums for a few days as well as the internet but I could not seem to find one that had my same problem, but if there is can you please direct me to it and apologies for that.
I was installing a new rom, the Blackout ICS Incredible v3.0.0 FULLY WORKING!!! [4.0.4][Sense 3.6], onto my inspire i did a full wipe using FULL_WIPE_1.5_EXT4_.zip and I cleared the caches. the install i thought went well because it went to 100% and i even chose what kind of background i could as well as choosing to over clock my processor. The phone the restarted after all of that and it went to the htc screen then faded to black, after about ten minutes of it being black screen i pulled out the battery.
Now when i try to recover it it wont go into hboot and it just goes to the htc white screen then it quickly fades to a black screen and stays like that.
so my question to you all is a Jtag the only way i can save my phone or is there something else i can do?
http://forum.xda-developers.com/showthread.php?p=30480411
Sent from a dream.
Teichopsia said:
http://forum.xda-developers.com/showthread.php?p=30480411
Sent from a dream.
Click to expand...
Click to collapse
Im sorry but I dont understand. I cannot enter hboot no mater what i do and don't you need to enter hboot to reflash it?
True, but I'm hoping you are doing something wrong.
Pull battery, wait a few minutes, place back in. Press and hold Volume down, then power button. Does it go into hboot? If not.
Read this.
http://forum.xda-developers.com/showthread.php?p=20382502
Edit: you are the first report with that issue after trying to flash that rom. My bet (that is, if you are new), you are not doing something wrong.
2nd edit: if you are new, then read the guide in post#7
http://forum.xda-developers.com/showthread.php?p=30007255
Sent from a dream.
Teichopsia said:
True, but I'm hoping you are doing something wrong.
Pull battery, wait a few minutes, place back in. Press and hold Volume down, then power button. Does it go into hboot? If not.
Read this.
http://forum.xda-developers.com/showthread.php?p=20382502
Edit: you are the first report with that issue after trying to flash that rom. My bet (that is, if you are new), you are not doing something wrong.
.
Click to expand...
Click to collapse
I really appreciate the help Teichopsia , but I've tried the power /volume - method many times and it still wont go to hboot. if it helps this is the 5 time i have have flashed a rom on my phone (and it is rooted) and yes sadly i had to be the first person to be unlucky enough to get my phone bricked from the blackout rom :crying:
i think i could get out of this mess if i could only get into hboot.
reading the method you linked to me will it work if i cant even get to the hboot screen? my phone only stays of the white htc logo screen for about 3 seconds then it goes to a lit black screen
on a side note should i report what happened to team blackout to see if they have any soloutions?
The only thing I can think of is trying to get into hboot without the sd card and sim card.
The rest is beyond my knowledge.
You'll need to wait for someone more knowledgable than myself to help you.
Remember, first press and hold the volume down button, while holding that down press the power button. Do not release either button till it shows the hboot. If that doesn't work, pull the battery for five minutes and try again. If you did this part exactly like that, then you can skip it.
Well, you already posyed your issue here, just wait for someone to help you. Glevitan is bound to show up sooner or later.
Sent from a dream.
I would see if you can send commands to it from adb while its in the blacked out state. adb is pretty easy to use and can be found easy online. if you get it installed type "adb devices", if it recognizes your device type "adb reboot bootloader" or "adb reboot recovery".
Novius vi said:
hello all,
I am new here and I have been searching the forums for a few days as well as the internet but I could not seem to find one that had my same problem, but if there is can you please direct me to it and apologies for that.
I was installing a new rom, the Blackout ICS Incredible v3.0.0 FULLY WORKING!!! [4.0.4][Sense 3.6], onto my inspire i did a full wipe using FULL_WIPE_1.5_EXT4_.zip and I cleared the caches. the install i thought went well because it went to 100% and i even chose what kind of background i could as well as choosing to over clock my processor. The phone the restarted after all of that and it went to the htc screen then faded to black, after about ten minutes of it being black screen i pulled out the battery.
Now when i try to recover it it wont go into hboot and it just goes to the htc white screen then it quickly fades to a black screen and stays like that.
so my question to you all is a Jtag the only way i can save my phone or is there something else i can do?
Click to expand...
Click to collapse
i also have the same problem. i'm using a DHD. and to add to that, my volume rocker is broken. i wonder why the warning not to select reboot immediately after installation wasnt part of the download as a readme or something. i may have just lost a perfectly good phone as a result
I can confirm as a third user and one knowledgable in flashing roms that the ICS blackout does the same thing to my phone. I can also confirm that pulling the battery and then trying hboot just results in the white htc screen instead of just popping up hboot. I was able to boot into recovery from the white htc screen by using adb and doing the "adb reboot recovery" command. I am able to restore my backup just fine so you guys will be able to fix it. it must just have a bad boot image for the version of hboot that we have installed.
Gizmoe said:
I can confirm as a third user and one knowledgable in flashing roms that the ICS blackout does the same thing to my phone. I can also confirm that pulling the battery and then trying hboot just results in the white htc screen instead of just popping up hboot. I was able to boot into recovery from the white htc screen by using adb and doing the "adb reboot recovery" command. I am able to restore my backup just fine so you guys will be able to fix it. it must just have a bad boot image for the version of hboot that we have installed.
Click to expand...
Click to collapse
Im sorry but this is the first time i have ever done something like that can you give me a step by step instruction how to do it or a link that says how, i dont want to sound lazy but I scared to mess up my phone even more
Use this guide its very easy. if you have already used your phone on your pc and the drivers are installed all you need to do is download the easyadb and follow the instrucions to where is says to type adb.exe. once it is started just type adb devices to make sure it sees your device and then adb reboot recovery
Ignore the fact the instructions are written for a xoom as it will work for any android device with the drivers already installed, which they should be from rooting, syncing and all the other stuff you have probably already done on pc.
UPDATE: I reinstalled ICS blackout but instead of wiping myself i just let aroma installer do it and everything went fine this time. I noticed the aroma installer reformats everything to ext4. its not mentioned in the op as a requirement but seems thats the case. Hboot version has nothing to do with it like i previously commented. It really is a cool rom with both ics and sense. I have only tried the sense version so far
Hope this helps?
Novius vi said:
Im sorry but this is the first time i have ever done something like that can you give me a step by step instruction how to do it or a link that says how, i dont want to sound lazy but I scared to mess up my phone even more
Click to expand...
Click to collapse
Just in case-- to get into recovery you must press and hold the volume down for a few seconds and then hold the power button. Do not do press them both at the same time. I realize you wrote that your volume rocker seems or is broken but I wrote above just in case-- when I first tried to root my phone, I was pushing them both at first and thought my rocker was broken....
Since you rooted the phone originally-- not sure how you did it. But if you go to this link you can download recovery flash. Read the "readme" file:
http://forum.xda-developers.com/showpost.php?p=29208930&postcount=10
Assuming you can get into recovery-- then reload the blackout ROM but you MUST let the aroma installer wipe and format do not use any other wipe/format tool. Then do NOT press the "FINISH" button-- instead press the back arrow-- you want to go back to flash recovery and reboot from there. If you press finish (like I did multiple times, the phone will just lockup).
Best of luck!
Three of us confirmed that hboot was inaccessible even after battery pull. I am no stranger to this device as well. The only fix was using adb reboot. Also if you actually reformat your partitions to ext4 before install, then aroma will install correctly. It's just not mounting anything if it's still in ext3 format. Definitely better to just do the full wipe within aroma though. I do agree with not hitting restart from aroma but someone already mentioned that a few posts up.
Thank you thank you thank you
After putting it into abd it recognized it and then i was able to put it into hboot. Im not out of the woods yet, but after not being to see hboot in so long, well its just amazing to see it again
ok now its in hboot it gives me 4 choices
bootloader
Reboot
Reboot Bootloader
power down
apologies again but just for reassurance which one should i select?
THANK YOU GUYS for getting me this far!!!
special thanks to Gizmoe for suggesting the adb route
Novius vi said:
After putting it into abd it recognized it and then i was able to put it into hboot. Im not out of the woods yet, but after not being to see hboot in so long, well its just amazing to see it again
ok now its in hboot it gives me 4 choices
bootloader
Reboot
Reboot Bootloader
power down
apologies again but just for reassurance which one should i select?
THANK YOU GUYS for getting me this far!!!
special thanks to Gizmoe for suggesting the adb route
Click to expand...
Click to collapse
Select bootloader to get to recovery option.
1shukla said:
Just in case-- to get into recovery you must press and hold the volume down for a few seconds and then hold the power
Assuming you can get into recovery-- then reload the blackout ROM but you MUST let the aroma installer wipe and format do not use any other wipe/format tool. Then do NOT press the "FINISH" button-- instead press the back arrow-- you want to go back to flash recovery and reboot from there. If you press finish (like I did multiple times, the phone will just lockup).
Best of luck!
Click to expand...
Click to collapse
I did exactly as you said I pressed finished and it asked if i wanted to reboot i said no. then it sent me back to recovery mode crossing my fingers hoping to see that it works:fingers-crossed:
Now, just manually reboot.
Sent from a dream.
You saved my phone!!
Thank you guys sooo much this Rom is great once I got past that minor issue
My phones working better than ever I even oced it a little bit
Again I am eternally grateful to you guys and team black out for this great Rom!
I'm here, requesting help, i've read (i think) almost everything. Try everything and i'm not able to recover my G2x.
I'm from mexico, and my english it's no so good, i hope that everyone can understand what i'm trying to say U_U
I brought a used T-Mobile G2x from ebay. I was SOOO happy with the phone, a good one, a kickass and it was about $250 dlls for me. I think that was a good deal. The phone was on a average/good condition.
So, i rooted it, then after, moved the rom from stock to CM7 stable.
I changed then to eaglesblood ICS, then another eaglesblood, and then again CM7.
The phone was working very good. Then, a issue appeared.
Some day, the phone was a little slow, then i rebooted it. And then started the pain...
The screen showed the LG Logo, white brilliant. And after a seconds, power off. What!?
I tried to power on again. Nothing. I did the battery pull and then worked fine. I thought that was a simple bug or something.
Later, the phone ran out of energy. I pluged on the wall charger but nothing happened. I left it for an hour and tried to turn it on. Nothing...
Then charged the battery with a multicharger and the same problem. LG Logo, nothing. Checked on the CWM Recovery and did a cleanup of battery stats, nothing. I was desperate, so i've flashed my phone with Eaglesblood again. Vuala, the phone worked... 'till froze and i had to pull the battery... Again, LG Logo... nothing.
The phone boot up by himself after leaving it for an hour or more. But i had another problem... Battery at 999% Or battery stuck at 32% and suddenly dies...
I've checked with the battery app and saw that the battery said 0 mV
I have 2 batteries, and the both with the same problem. One LG, one chinese.
So, i went with a friend of mine, i took borrowed a battery of his LGO3D, and... nothing
The phone works with APX, powers on on the recovery, i even sometimes reads ok the battery and the phone comes alive, 'till i have to reboot it because the phone is so slow after 2 or 3 weeks without a reboot... but it's so rare and random...
I even updated the phone with the 21y baseband and the new stock rom, but keeps doing the same thing...
I'm just at the point that i want to throw the phone to the wall...
There are something that i can do?
Change some piece?
I must say that when the phone read the battery and it's ok, i can charge it normally, works perfectly, usb ok, everything it's like nothing was bad. But the problem is if the phone shut's down...
Get adb working with USB and if using a windows pc open Command Prompt and run
HTML:
adb devices
....Make sure your device is found, an ID number will appear if successful....
HTML:
adb reboot
....Let the phone start rebooting. When "adb devices" works and shows the phone ID again proceed...
HTML:
adb shell
$ su
# dmesg > /sdcard/dmesg.txt
# logcat -v time -d > /sdcard/logcat.txt
# exit
$ exit
adb pull /sdcard/logcat.txt %USERPROFILE%\Desktop\logcat.txt
adb pull /sdcard/dmesg.txt %USERPROFILE%\Desktop\dmesg.txt
exit
If you get a complaint with those last 2 commands; change %USERPROFILE% = whatever your username is where your Desktop is located. (i.e. C:\Users\me\Desktop\dmesg.txt)
Then either email them to me or post them on www.pastebin.com and post links to both files.
I'm a little lost...
First of All! Thanks for the help
And i dont know... The phone must be ON to do that?
The phone right now doesn't power on, just the LG Logo, at this point, when i attach to a computer via USB Cable, the computer doesn't detect anything...
I can enter the CWM Recovery, it's enough??
And a funny thing: The phone NEVER powers ON (Not even the LG LOGO) when usb or charger it's connected.
EDIT:
Good news, i've got adb working, but i don't have su, i'm downloading it thanks
EDIT AGAIN
The last time that i've flashed to stock rom the g2x forgot to root the phone
i've already tried with adb commands, but i got errors when i try...
I guess that i need usb debugging On, and i doesn't have it...
I'm on a dead end??
Go to the ROM for recovery thread in development section, follow it step by step and your phone will be 100% alive and kicking on GB 2.3.4.
Sent from my SPH-D710 using xda premium
supertaco said:
First of All! Thanks for the help
And i dont know... The phone must be ON to do that?
The phone right now doesn't power on, just the LG Logo, at this point, when i attach to a computer via USB Cable, the computer doesn't detect anything...
I can enter the CWM Recovery, it's enough??
And a funny thing: The phone NEVER powers ON (Not even the LG LOGO) when usb or charger it's connected.
EDIT:
Good news, i've got adb working, but i don't have su, i'm downloading it thanks
EDIT AGAIN
The last time that i've flashed to stock rom the g2x forgot to root the phone
i've already tried with adb commands, but i got errors when i try...
I guess that i need usb debugging On, and i doesn't have it...
I'm on a dead end??
Click to expand...
Click to collapse
If I recall you were the one who emailed me and I sent you links to NVFlash correct? Did that work for you? I'm just trying to see what your question really is. It sounded from you OP that the hardware perhaps keeps failing and no matter which ROM you flash, you eventually get stuck in bootloop like you are now. Are you just trying to get out of bootloop or is this a reocurring problem? If your stuck in bootloop then your only solution is to NVFlash a recovery and push a rom. If its reocurring then we gotta figure out why... thats where my instructions come in. So you need to tell us exactly what you're trying to do.
As for adb yes you can adb from recovery. You gotta go to Mounts and storage > Mount /system though or else the device wont show.
oOo B0XeR oOo said:
If I recall you were the one who emailed me and I sent you links to NVFlash correct? Did that work for you? I'm just trying to see what your question really is. It sounded from you OP that the hardware perhaps keeps failing and no matter which ROM you flash, you eventually get stuck in bootloop like you are now. Are you just trying to get out of bootloop or is this a reocurring problem? If your stuck in bootloop then your only solution is to NVFlash a recovery and push a rom. If its reocurring then we gotta figure out why... thats where my instructions come in. So you need to tell us exactly what you're trying to do.
As for adb yes you can adb from recovery. You gotta go to Mounts and storage > Mount /system though or else the device wont show.
Click to expand...
Click to collapse
Ok... my first problem: Language. I don't have problem with the reading, but writing... i'll try to put my words on the right place
I don't remember, when i first flashed my G2x i did it with the Rom Manager App... the result came on a bootloop. Then i used NVFlash and flashed a correct ClockworkMod Recovery. Installed CM7 and everything was fine. Then i wanted to try ICS and flashed it again. No problem. I normally follow the guides step by step, and the phone was right. Then, one day the phone froze and was the first time that i had the bootloop with the LG Bright Logo, then dim, and then power off.
The problem not was while i was flashing a rom. Because while i was on the problem, i flashed with NVFlash the original bootloader and then restore the original firmware, and the problem still there. Right now the phone has the stock rom, updated by the LG utility, and the problem persists.
I think that is what you say. The phone doesn't pass the LG Logo screen no matter which rom i flash... What i don't understand is that the phone seems to be ok. When it powers (a week ago) it worked just fine...
I don't think that is a bootloop caused by a bad flashing... i think that is a recurring problem...
I have this 2 folders with tools for the NVFlash, i think that the both of them are right...
One-Click-G2x-recovery-flasher-04-28-12 [Folder]
One-Click-G2x-recovery-flasher-09-23 [Folder]
They have the APX drivers and NVFlash and the One-click-G2xr-recovery-flasher app...
I'll mount the /system in recovery and i will try to get that log. With the /system mounted then i think that i can root the phone...
I'm gonna try... let's see what happen...
Thanks
EDIT: I noticed (when the problem first came) that the sticker of water damage was ripped off... is not there... But i don't know if the phone was really damaged by water, because i'm not the first owner... The phone was working fine for about 6 months and now it's just like i'm explaining...
supertaco said:
Ok... my first problem: Language. I don't have problem with the reading, but writing... i'll try to put my words on the right place
I don't remember, when i first flashed my G2x i did it with the Rom Manager App... the result came on a bootloop. Then i used NVFlash and flashed a correct ClockworkMod Recovery. Installed CM7 and everything was fine. Then i wanted to try ICS and flashed it again. No problem. I normally follow the guides step by step, and the phone was right. Then, one day the phone froze and was the first time that i had the bootloop with the LG Bright Logo, then dim, and then power off.
The problem not was while i was flashing a rom. Because while i was on the problem, i flashed with NVFlash the original bootloader and then restore the original firmware, and the problem still there. Right now the phone has the stock rom, updated by the LG utility, and the problem persists.
I think that is what you say. The phone doesn't pass the LG Logo screen no matter which rom i flash... What i don't understand is that the phone seems to be ok. When it powers (a week ago) it worked just fine...
I don't think that is a bootloop caused by a bad flashing... i think that is a recurring problem...
I have this 2 folders with tools for the NVFlash, i think that the both of them are right...
One-Click-G2x-recovery-flasher-04-28-12 [Folder]
One-Click-G2x-recovery-flasher-09-23 [Folder]
They have the APX drivers and NVFlash and the One-click-G2xr-recovery-flasher app...
I'll mount the /system in recovery and i will try to get that log. With the /system mounted then i think that i can root the phone...
I'm gonna try... let's see what happen...
Thanks
EDIT: I noticed (when the problem first came) that the sticker of water damage was ripped off... is not there... But i don't know if the phone was really damaged by water, because i'm not the first owner... The phone was working fine for about 6 months and now it's just like i'm explaining...
Click to expand...
Click to collapse
Ok, I bet your partition tables are messed up. If you can get that dmesg and logcat file it would be ideal but if you cant then we just gotta move forward.
First copy all your stuff from SDcard and internal memory into a folder on a PC. Make a backup using clockwork or whatever and also copy that onto a PC just to be safe.
Then you need to search the G2x forum for this batch utility called something like "auto-formatter partition repair tool" or something similar. If you cant find it message me.
Youll want to run that first, its going to completely wipe all of your stuff and reformat the blocks sizes. Once done youll need to NVFlash a CWM recovery again. Then push a ROM over to the phone and install with CWM. (Dont push a stock rom or anything Gingerbread. Ideally push EaglesBlood ICS since I know it works and can help you troubleshoot.
So i would do that first because i bet your upgrade when u said you attempted to install ICS corrupted the file system, which can happen if you dont format /system prior.
Get the utility, backup everything , format the partitions, NVflash CWM recovery, push ICS rom, install, install GAPPS, come back here and tell me it worked
oOo B0XeR oOo said:
Ok, I bet your partition tables are messed up. If you can get that dmesg and logcat file it would be ideal but if you cant then we just gotta move forward.
First copy all your stuff from SDcard and internal memory into a folder on a PC. Make a backup using clockwork or whatever and also copy that onto a PC just to be safe.
Then you need to search the G2x forum for this batch utility called something like "auto-formatter partition repair tool" or something similar. If you cant find it message me.
Youll want to run that first, its going to completely wipe all of your stuff and reformat the blocks sizes. Once done youll need to NVFlash a CWM recovery again. Then push a ROM over to the phone and install with CWM. (Dont push a stock rom or anything Gingerbread. Ideally push EaglesBlood ICS since I know it works and can help you troubleshoot.
So i would do that first because i bet your upgrade when u said you attempted to install ICS corrupted the file system, which can happen if you dont format /system prior.
Get the utility, backup everything , format the partitions, NVflash CWM recovery, push ICS rom, install, install GAPPS, come back here and tell me it worked
Click to expand...
Click to collapse
It's a shame that i cannot get that logcat... :/
Well... i have nothing to lose (data, or something), so i searched over the forums and i found this utility:
Code:
[URL="http://forum.xda-developers.com/showthread.php?t=1590523"]http://forum.xda-developers.com/showthread.php?t=1590523[/URL]
I think thats the right one, or at least, one of many...
That utility flashes a CWM Touch, then, i installed Eaglesblood Gingerbread (because the utility said that if i don't, the sdcard will not be recognized) and the gaaps...
Turned off the phone...
Turned On...
But then again, i have the LG logo bright, then dim, then power off :/
Do you think that could be a charger flex problem? Motherboard? I should burn it?? :/
Use the batch cleanup tool, then flash stock rooted ROM. That way you cab make sure something works, and stock is going to be the safest flash. If that works, then you can go on to custom Roms
Sent from my LG-P999 using xda premium
supertaco said:
It's a shame that i cannot get that logcat... :/
Well... i have nothing to lose (data, or something), so i searched over the forums and i found this utility:
Code:
[URL="http://forum.xda-developers.com/showthread.php?t=1590523"]http://forum.xda-developers.com/showthread.php?t=1590523[/URL]
I think thats the right one, or at least, one of many...
That utility flashes a CWM Touch, then, i installed Eaglesblood Gingerbread (because the utility said that if i don't, the sdcard will not be recognized) and the gaaps...
Turned off the phone...
Turned On...
But then again, i have the LG logo bright, then dim, then power off :/
Do you think that could be a charger flex problem? Motherboard? I should burn it?? :/
Click to expand...
Click to collapse
Yes thats the utility, and the post above by "rtotheichie" is correct too.
You cant flash a Gingerbread ROM. You need to either push a stock/rooted build, or an ICS build. It's that gingerbread -to- ICS thats causing the partition problem (if it even is that). So what you're doing is fixing it then messing it up again.
--> There could be any number of things going on and we can guess at anything but what good is that gonna do? ... You NEED to get that #dmesg log. I would focus on doing whatever you can to get ADB working because thats going to tell us exactly what is failing at boot time. Can you get into Recovery? I wouldn't even worry about starting the ROM, you should focus on getting into Recovery first. If you cant get into Recovery then you didn't flash it correctly with NVFlash. If you can get in, then go to Mounts & Storage > mount /system ...then get that ADB going using my 1st post above. Thats your only hope if you cant get it on your own.
oOo B0XeR oOo said:
Yes thats the utility, and the post above by "rtotheichie" is correct too.
You cant flash a Gingerbread ROM. You need to either push a stock/rooted build, or an ICS build. It's that gingerbread -to- ICS thats causing the partition problem (if it even is that). So what you're doing is fixing it then messing it up again.
--> There could be any number of things going on and we can guess at anything but what good is that gonna do? ... You NEED to get that #dmesg log. I would focus on doing whatever you can to get ADB working because thats going to tell us exactly what is failing at boot time. Can you get into Recovery? I wouldn't even worry about starting the ROM, you should focus on getting into Recovery first. If you cant get into Recovery then you didn't flash it correctly with NVFlash. If you can get in, then go to Mounts & Storage > mount /system ...then get that ADB going using my 1st post above. Thats your only hope if you cant get it on your own.
Click to expand...
Click to collapse
Well, i have no problems with recovery. Never had IT. But the last time i tried to use the commands failed... I'll post a video, maybe that will be more self explaining... I really appreciate that you take a time for helping me thanks
supertaco said:
Well, i have no problems with recovery. Never had IT. But the last time i tried to use the commands failed... I'll post a video, maybe that will be more self explaining... I really appreciate that you take a time for helping me thanks
Click to expand...
Click to collapse
No problem.
Well if you can get into recovery and if you have ADB and the drivers for the phone setup on your PC you should have no problems connecting. Try using a Windows PC if you can, it's funny but ADB is probably the only thing that is easier to get going the 1st time in Windows rather than Linux (Ubuntu).
Just keep trying and run
HTML:
$ adb devices
each time until a device ID shows up.
I've noticed you've posted this same question on like every single Android website that exists; but I'm telling you what the correct answer is and the only way you're going to be able to figure out what is going on is to get to a log file. No one has a magic trick that will automagically fix this from afar. Anything else is just guessing and checking.
In recovery, try going to Advanced > Show log ...what does that say? Also it won't hurt to try going to Advanced > Fix permissions. I doubt that will do anything for you but it won't hurt to try at this point.
oOo B0XeR oOo said:
No problem.
Well if you can get into recovery and if you have ADB and the drivers for the phone setup on your PC you should have no problems connecting. Try using a Windows PC if you can, it's funny but ADB is probably the only thing that is easier to get going the 1st time in Windows rather than Linux (Ubuntu).
Just keep trying and run
HTML:
$ adb devices
each time until a device ID shows up.
I've noticed you've posted this same question on like every single Android website that exists; but I'm telling you what the correct answer is and the only way you're going to be able to figure out what is going on is to get to a log file. No one has a magic trick that will automagically fix this from afar. Anything else is just guessing and checking.
In recovery, try going to Advanced > Show log ...what does that say? Also it won't hurt to try going to Advanced > Fix permissions. I doubt that will do anything for you but it won't hurt to try at this point.
Click to expand...
Click to collapse
I'll try that, today
And i know that aint no magic trick that fix my phone... I'll try everything to resolve the problem.
Thanks...
And another thing. I've checked my PM's, and saw that i've never send a PM to you. And no, i'm not flooding the entire www with my question. But i think that i should have used a diferent question to describe my problem. This is the first time that i ask for help, after reading and reading on the web, and almost everyone says: "send it back to t-mobile", but that's not an option for me. And my first choice (and olny) for asking help of course it's xda.
I remember that once clicked "show log" and an error pop out, but i didn't try the fix permissions options.
This is the video. Sorry for my bad english.
Video
supertaco said:
I'll try that, today
And i know that aint no magic trick that fix my phone... I'll try everything to resolve the problem.
Thanks...
And another thing. I've checked my PM's, and saw that i've never send a PM to you. And no, i'm not flooding the entire www with my question. But i think that i should have used a diferent question to describe my problem. This is the first time that i ask for help, after reading and reading on the web, and almost everyone says: "send it back to t-mobile", but that's not an option for me. And my first choice (and olny) for asking help of course it's xda.
I remember that once clicked "show log" and an error pop out, but i didn't try the fix permissions options.
This is the video. Sorry for my bad english.
Video
Click to expand...
Click to collapse
I saw the video.
Take out the battery > then put it back in.
Press and hold BOTH the [Power] and [Volume Down-] at the same time and keep holding them.
Keep them both pressed while the "LG logo" appears; shortly after you should see the white logo change to a BLUE logo... once you see that you can let go.
Does that work and get you into Recovery? ...let me know.
One other thing to try...
Plug your USB cable into the Computer ONLY ---Not the phone.
Take out the battery, do NOT put it back in.
Now (with the battery still removed), Press and Hold [Volume Up+] and [Volume Down-] together. Do not press the Power button.
While still holding both Volume buttons together, insert the USB cable into the phone.
Now wait a second or two, does the phone Power On into a "Download mode screen"?
If not, let go of the Volume buttons and unplug the USB from the phone.
Now plug the USB back into the phone. Press and hold the [POWER] Button for several seconds (still with NO battery in, just the USB).
Does that turn the phone on?
P.S. - This might be good to have as well:
User manual (Spanish): http://www.lg.com/us/products/documents/LG-G2x-UserGuide_ES.pdf
Service Repair Manual (English): http://www.mediafire.com/view/?cscdjc6p08t2omq
oOo B0XeR oOo said:
I saw the video.
Take out the battery > then put it back in.
Press and hold BOTH the [Power] and [Volume Down-] at the same time and keep holding them.
Keep them both pressed while the "LG logo" appears; shortly after you should see the white logo change to a BLUE logo... once you see that you can let go.
Does that work and get you into Recovery? ...let me know.
One other thing to try...
Plug your USB cable into the Computer ONLY ---Not the phone.
Take out the battery, do NOT put it back in.
Now (with the battery still removed), Press and Hold [Volume Up+] and [Volume Down-] together. Do not press the Power button.
While still holding both Volume buttons together, insert the USB cable into the phone.
Now wait a second or two, does the phone Power On into a "Download mode screen"?
If not, let go of the Volume buttons and unplug the USB from the phone.
Now plug the USB back into the phone. Press and hold the [POWER] Button for several seconds (still with NO battery in, just the USB).
Does that turn the phone on?
P.S. - This might be good to have as well:
User manual (Spanish): http://www.lg.com/us/products/documents/LG-G2x-UserGuide_ES.pdf
Service Repair Manual (English): http://www.mediafire.com/view/?cscdjc6p08t2omq
Click to expand...
Click to collapse
I'm currently downloading the service manual and the user manual.
Ok, i tried the first thing. The phone gets on recovery mode. All good.
On the second thing to try:
-I followed the steps just as you said: vol+ and vol- and connect usb cable. It makes a sound of connected device, checked and windows detects a NVIDIA USB Boot-recovery driver for Mobile devices, but the phone screen never powers up or show a download mode screen. When i flash anything with NVFlash it shows the Download mode screen...
-I plugged the phone without battery, and pushed the power button. The phone does not power on. Not even the LG logo or anything.
I'm still trying to get that logcat. But everytime that i want to type "su" on the adb shell says that cannot found su...
Now i'm on recovery.
Advanced> fix permissions: Done.
Show log:
Init.svc.adbd=running
I: Checking for extendedcommand...
I: Skipping execution of extendedcommand, file not found...
W: Failed to mount /dev/block/mmcblk0p1 (invalid argument)
W: Failed to mount /dev/block/mmcblk0p7 (invalid argument)
Fixing permissions...
/sbin/fix_permissions 2.04 started at 01-01-2007 00:00:36
cat: can't open '/data/system/packages.xml' : no such file or directory
cat: can't open '/data/system/packages.xml' : no such file or directory
/sbin/fix_permissions 2.04 ended at 01-01-2007 00:00:36 (runtime: 0m0s)
Done!
Whats the status on this are you still dead? Looks like you need to do that partition formatter script now... appears your partitions are messed up. What ROM is on there now?
oOo B0XeR oOo said:
Whats the status on this are you still dead? Looks like you need to do that partition formatter script now... appears your partitions are messed up. What ROM is on there now?
Click to expand...
Click to collapse
Sorry, i didn't get the mail of new post...
Yeah, it's still dead...
Today, i put the battery on the phone and it started right away. Battery status ok, everything working fine. But i didn't put a sim card, so i turned off the phone and it's dead again.
I don't know if i'm getting a GOOD partition formatter. But i've already used one... and the result it's the same...
And even tried a crazy method of one guy that put the phone on the fridge for 10 mins and then NVFlashed-it to a stock gb...
And nothing U_U
Power up, show a bright LG logo, then a less bright one... power off...
Thanks for your help...
EDIT:
Today i opened the phone, extracted the logic board and watched everything. A VERY SMALL bga chip (i don´t know wich) had a little crack on it, i cleaned with a soft brush and a little piece came off... Now the phone doesn't boot at all, not even the LG logo... i think that's the end...
If someone can indicate me where i can buy a new mainboard it would be very appreciated. Thanks.
END
LG
eBay
Stuff wanted/selling here
Find a person selling a great phone but like the screen is broken or something. Look at the repair manual i posted previously above.