Problems while flashing Optimus M. Please help - Android Software/Hacking General [Developers Only]

Hey all,
I have been a long time flasher of phones however I did a bonehead move and need to see what if anything can be done. Here is what happened.
I have an Optimus M and I have successfully upgraded and downgraded the phone before. Today I was trying a downgrade and as I was flashing I was deleting some files to make some room on my netbook and deleted the .cab flash file. So I tried many times to get the image to take to no avail. I went to my other netbook and tried to flash with the upgrade file and no go there either. What I get when I try to turn the phone on is a very quick LG logo and then nothing. When I hook up the phone on usb with no battery I get a s/w screen however no recovery or reboot sequence I have been able to find works either. Here is a list of what I have already tried. Please let me know if there is anything else you can think of.
-Downgrade flash with Kp500
-pulled out battery and allowed to sit
-connected to other cpu to try upgrade flash via lg upgrader (no go)
-tried recovery sequence
-tried hard reset sequence
Man after all of these years of hacking phones I would hate to think I finally have had the bad luck to make a stupid mistake and brick one.
Thanks everyone!

Related

Reviving the Samsung Galaxy S 4G

I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
hechoen said:
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
Click to expand...
Click to collapse
I didn't feel like i really hard bricked it until i saw the USB computer connection error "device pluged in malfunctioned" in more than one PC.
Then i really felt like its a hardware BIOS chipset level problem now but man...
That story cracked me up. That is exactly why I spend days reading before I even root my phone. I made the mistake one time on my old G1 and it could not be revived.
Congrats on getting it working. (especially without flooding the q&a with redundant questions that have been described in detail several places )
hani1400 said:
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Click to expand...
Click to collapse
Wheooooooooowwww,..you just UNBRICKED mine, I know of the Battery pull etc...but the post you referenced
is MAGIC
This was not my first Rom nor Root on this phone, it weirdly happened while doing the GB starter....via ODIN, which i also used before..no clue what went wrong, oh well...
Thank you, thank you "i did"....Yohoooo
Yup i agree i like to read, reread then read as i do. This way i got a pretty good understanding of what I'm doing. Btw i have just started using one click and it is sooooo simple. I love it.
Sent from my SGH-T959V using XDA App
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
diavel said:
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=881162
Im still carrying this phone, stupid baseband unlock for iphone won't come out now I am carrying 2 phones, one as an ipod touch and the galaxy s! Good story, hope it can help others, but I am prepared to jump off of this bandwagon anytime now!

Pantech Burst Bricked HELP!!!

I recently picked up a Pantech Burst phone from At&t, and upgraded to ICS. I then proceeded to root the phone using the prestoroot.img method and it worked. Everything was running dandy until I got the VM Heap tool app and(stupidly) set the vm heap to 52m and attempted to reboot... It failed and all I got was a loop of boot up animations. I tried several times to reboot, and then tried to boot to recovery mode and factory reset. That worked, but it STILL didnt reboot..! I dont have a backup, and whenever i try to " Install update from external storage", it just fails over and over again. I found thestock firmware and downloaded it to my external sd card and install(still to no success). Im only 13 and cant afford a new phone! PLEASE SOMEONE HEEEELLLLPPPPPP!!!!!!!!!!!!!
Use P9070_Download_Tool_v3.3.zip and flash PRESTO_BIN_JUUS09032012_TP20_user using this method http://forum.xda-developers.com/showthread.php?p=28602800#post28602800. You might find other answers in that same thread Pantech Burst Essentials.
I love you!!!!!!!
dvinelord said:
use p9070_download_tool_v3.3.zip and flash presto_bin_juus09032012_tp20_user using this method http://forum.xda-developers.com/showthread.php?p=28602800#post28602800. You might find other answers in that same thread pantech burst essentials.
Click to expand...
Click to collapse
it workkeed!!!!!:d
DvineLord said:
Use P9070_Download_Tool_v3.3.zip and flash PRESTO_BIN_JUUS09032012_TP20_user using this method http://forum.xda-developers.com/showthread.php?p=28602800#post28602800. You might find other answers in that same thread Pantech Burst Essentials.
Click to expand...
Click to collapse
I bricked my phone few days back doing restore from CWM 6 downloeded online from ROM manager,
I wiped cache dalvik etc & rebooted, I could see the Tap the android screen then suddenly blank now it wont start
I get QHSUSB_dload in PC device manager any way out
I tried this method but I dont get the download button to click it remains greyed out.
Is there any driver for QHSUSB_dload?
Or do I have no hope at the moment or in near future?
just don`t use ROM manager for installing recovery . usually the result is bricked phone
Yah, i remember a fastboot brick i got from rom manager (LG Optimud ME)
Sent from a 2.8 inch screen
I also just bricked my Pantech Burst the same way...using ROM Manager. Is there a way to fix this or am I out of luck? I did try the method posted at the top of this thread. It just gets locked in the S/W Upgrading screen. Any help will be greatly appreciated.
I'm too in same situation.....i tried it updating via Pantech OS Upgrade tool......it updates successfully but doesnot bootup....
and now it shows some S/W Upgrading with red colour background
plz help me out:crying::crying::crying::crying::crying:
coolamjadkhan said:
I'm too in same situation.....i tried it updating via Pantech OS Upgrade tool......it updates successfully but doesnot bootup....
and now it shows some S/W Upgrading with red colour background
plz help me out:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Mine did not upgrade successfully, but I have the exact same problem. On day three of waiting for a callback from Pantech on the issue. They are supposedly talking to the techs in Korea about it.
Maybe solved!
tajlund said:
Mine did not upgrade successfully, but I have the exact same problem. On day three of waiting for a callback from Pantech on the issue. They are supposedly talking to the techs in Korea about it.
Click to expand...
Click to collapse
Don't know if this is going to help, but I had the problem (as I described) red S/W Upgrading and couldn't do anything. Well, after about two weeks of sitting with the battery out, I decided to redownload and rerun the Pantech update app, and lo and behold, it fixed my phone. It also installed a more up to date version of Android 4.0, I went from 4.01 to 4.04.
This is after running the updater a good 30 or so times the past two weeks hoping for anything to work, now today, bam, it works fine.
I would recommend anyone in this situation give the most recent updater a try, it may solve your problem.
need help with my burst!!!!!
Hey! i have a pantech burst and i love it! but i had to reset it and now it wont work. my exhusband root it a few months ago....and he deleted the keyboard and the launcher..... so.... when i turn it on i cant do anything cause i cant write .... and if i skip the android start menu i cant see anything cause i dont have a launcher.... please someone help! what can i do?
:crying: Bricked my phone total unable start. any hardware diagnostic tool or manual reset button.
please help urgently
needhelppantech said:
Hey! i have a pantech burst and i love it! but i had to reset it and now it wont work. my exhusband root it a few months ago....and he deleted the keyboard and the launcher..... so.... when i turn it on i cant do anything cause i cant write .... and if i skip the android start menu i cant see anything cause i dont have a launcher.... please someone help! what can i do?
Click to expand...
Click to collapse
would you like to sell it cheaper rate???
Bricked Pantech Burst Stuck in S/W Downloading Mode and completely wiped ...
Ok I am having a similar issue guys. Last night I had to wipe my phone because it was overly full and I switched providers and the phone had become unusable. I tried using clockworkmod to do this and it wiped everything ( including clockworkmod. ) Now I only get a S/W Upgrading screen with a red box. I tried using the pantech download tool and the PANTECH_PRESTO_BIN_JUUS03122012.pdl file. It did appear that it was installing it but then it became stuck at the very very very end of things. I basically had to take the battery out to do anything at all as I had left the phone on all night to download the pdl file but without any luck.
When I reboot the phone it had the S/W Upgrading mode with the red screen. I've tried all of the different key combinations on the pantech burst etc volume up + volume down and power, volume down + power, volume up + power. None of these things will reboot the phone.
I am hoping I can use the pantech download tool to install a different pdl instead and possibly get it working that way. I know that when the phone is off if I plug it into usb then the screen lights up on it with the S/W Upgrading screen and the red box. If I press the power button or any other combinations of buttons + the power button it also does this. It literally will not do anything else.
I cannot use pantech pc suite because the phone originally was so unusable I could not put the android apk file on the phone even though I have it on my laptop.
I tried using adb and fastboot and it will not even find my device through ANY usb port on the laptop. I've tried deleting and reinstalling the drivers over and over. The only thing I know to do is reboot afterward and hopefully it will find my phone on usb with adb. If I can just get to a bootloader or flash functional firmware onto this phone I think I could get it working but I do not know enough about the pantech burst to try physically jumping anything on it in order to hard reset it.
So my only options right now look like maybe get a different pdl, possibly reboot and the drivers may find my phone, or JTAG this thing.
I can't put it in usb debugging mode because it won't boot. Since adb does not even find the device as being attached it seems as if this phone should be operating in a different port mode or something to make it visible. I could be wrong but I am hoping that rebooting fixes the driver issue and makes the phone visible.
I tried PDAnet also and once again it does not work because it cannot find the device. This could be a usb cable issue I suppose but I only have this particular cable I am pretty sure
I might try another cable as well...
Any other ideas ? Am I going to have to JTAG this thing or should it be fixable using the download tool and a different pdl ? Or do I need to find another way to completely wipe the phone first and THEN use the download tool with the pdl file ?
It does get a bit confusing with so many mods, roms, and methods to recover android phones. If I can get the phone to boot then I can reload my backups and all should be well. I do need this phone for business purposes also. Any ideas guys ?
PS> I am also pretty decent with linux distros like arch or ubuntu so I would like to also know if it would just be better to do this in linux and possibly use linux to manually switch the phone to a different device mode to make it visible in the instance of there being nothing wrong with the drivers.
Thanks for any ideas or suggestions ...
UPDATE - progress ???
dsull1981 said:
Ok I am having a similar issue guys. Last night I had to wipe my phone because it was overly full and I switched providers and the phone had become unusable. I tried using clockworkmod to do this and it wiped everything ( including clockworkmod. ) Now I only get a S/W Upgrading screen with a red box. I tried using the pantech download tool and the PANTECH_PRESTO_BIN_JUUS03122012.pdl file. It did appear that it was installing it but then it became stuck at the very very very end of things. I basically had to take the battery out to do anything at all as I had left the phone on all night to download the pdl file but without any luck.
When I reboot the phone it had the S/W Upgrading mode with the red screen. I've tried all of the different key combinations on the pantech burst etc volume up + volume down and power, volume down + power, volume up + power. None of these things will reboot the phone.
I am hoping I can use the pantech download tool to install a different pdl instead and possibly get it working that way. I know that when the phone is off if I plug it into usb then the screen lights up on it with the S/W Upgrading screen and the red box. If I press the power button or any other combinations of buttons + the power button it also does this. It literally will not do anything else.
I cannot use pantech pc suite because the phone originally was so unusable I could not put the android apk file on the phone even though I have it on my laptop.
I tried using adb and fastboot and it will not even find my device through ANY usb port on the laptop. I've tried deleting and reinstalling the drivers over and over. The only thing I know to do is reboot afterward and hopefully it will find my phone on usb with adb. If I can just get to a bootloader or flash functional firmware onto this phone I think I could get it working but I do not know enough about the pantech burst to try physically jumping anything on it in order to hard reset it.
So my only options right now look like maybe get a different pdl, possibly reboot and the drivers may find my phone, or JTAG this thing.
I can't put it in usb debugging mode because it won't boot. Since adb does not even find the device as being attached it seems as if this phone should be operating in a different port mode or something to make it visible. I could be wrong but I am hoping that rebooting fixes the driver issue and makes the phone visible.
I tried PDAnet also and once again it does not work because it cannot find the device. This could be a usb cable issue I suppose but I only have this particular cable I am pretty sure
I might try another cable as well...
Any other ideas ? Am I going to have to JTAG this thing or should it be fixable using the download tool and a different pdl ? Or do I need to find another way to completely wipe the phone first and THEN use the download tool with the pdl file ?
It does get a bit confusing with so many mods, roms, and methods to recover android phones. If I can get the phone to boot then I can reload my backups and all should be well. I do need this phone for business purposes also. Any ideas guys ?
PS> I am also pretty decent with linux distros like arch or ubuntu so I would like to also know if it would just be better to do this in linux and possibly use linux to manually switch the phone to a different device mode to make it visible in the instance of there being nothing wrong with the drivers.
Thanks for any ideas or suggestions ...
Click to expand...
Click to collapse
--------------------------------------------------------------------------
OK quick update, I found the pantech burst upgrade tool and the burst-hack.cmd script
I managed to successfully find my phone with the upgrade tool and it completely ran its course and I am guessing it installed Ice Cream Sandwich.
My new problem is that the phone goes to the pantech logo boot screen if I plug the phone into usb but that is all it will do. If I unplug the phone and try to get into S/W Upgrade mode again or power it on it will not do anything at all. Basically the display only comes on when plugged in at this point so I am wondering if the battery is even charged or if it will charge. I read somewhere ( in the gizmolord forum ) that a guy had the same issue as me and he ran this tool for his pantech burst and then left the battery out for 2 weeks and tried to power it back on and it worked for him.
Is it possible that I just need to power the device down completely and let it completely discharge before it will reboot or is this thing bricked ?
I am thinking that either the battery needs to charge, or the phone needs to discharge and power down completely, or the phone could be bricked. I have a feeling it is not bricked because the update tool said everything was successful and no errors or anything.
I will try leaving the battery out for awhile and letting the phone discharge on its own and see what kind of results I get. I would think that 16 - 24 hours would be sufficient. Any ideas ?
---------------------------------------------------------------------------------------------------------------------
Ok so I did a bit more digging and research and found out that the culprit is most likely the poorly designed charging circuit in the pantech phones. I found a tech blog called Mikes Techblog where he shows how to solve this on a pantech jest phone with the same issue. The problem is that the battery is 3.7v and is currently reading 2.8v on the volt meter. The phone will not even attempt to charge until 3.7v is available on the battery because of how the charge circuit is designed. I am going to try the usb cable trick and usb adapter and see if I can monitor its progress with the voltmeter and get it back up to 3.7 volts. After this it should allow me to charge it normally and should boot just fine. It is showing the pantech logo which tells me that the firmware is there and isn't buzzing or doing anything else weird so more than likely this is related to the battery and not having enough of a charge when running the official upgrade tool. This problem probably had already existed prior running the update tool and is why the S/W Upgrading screen only would come up AFTER being plugged into a power source and would disappear immediately. If the battery had any charge whatsoever and if the phone could see it then I would see a screen that tells me to plug my phone in and charge it. I am thinking this is solved but will only know after I charge the battery. From what I've been reading in comments from others the battery issue is prevalent on many different pantech phones including the burst model. Other people with the pantech burst have said in comments on Mike's blog that this made their phone boot right up and said that this was EXACTLY the issue. Perhaps the best way to use these pantech phones is to never ever let them fully discharge the battery.

[Q] Another Botched CWM upgrade

Hi Folks Im looking for help. I have the p920 AND I botched it.
I tapped for CWM to upgrade to the latest version and it all went wrong now im stuck on an LG logo with some what fuzzy appearance. Nothing happens eventually goes black.
Looking for some assistance?
I have searched as many bricked LGoptimus 3d posts and threads on here and tried but to no avail. I have the LGtool working but doesnt find the LG the latop cant detect it, it have some times shown something connecting but windows 7 knows best as aposed to letting me select the correct driver.
Help would be greatly appreciated.
DOBW said:
Hi Folks Im looking for help. I have the p920 AND I botched it.
I tapped for CWM to upgrade to the latest version and it all went wrong now im stuck on an LG logo with some what fuzzy appearance. Nothing happens eventually goes black.
Looking for some assistance?
I have searched as many bricked LGoptimus 3d posts and threads on here and tried but to no avail. I have the LGtool working but doesnt find the LG the latop cant detect it, it have some times shown something connecting but windows 7 knows best as aposed to letting me select the correct driver.
Help would be greatly appreciated.
Click to expand...
Click to collapse
try to flash the recovery using fastboot
The same thing happened to me a few days ago.
Version 6.0 of CWM Recovery caused my phone no stop boot at LG logo.
Use LG's official flash tool to recover phone (you will need to input your IMEI).
It will flash the latest stock rom to your phone.
After that I flashed CWM Recovery 5.0, that one works fine.
yep first time i tried cwm 6 i got stuck on lg boot too and without recovery... you can recover using fast boot like sww said (flash cmw 5 recovery in fastboot [if you go this way flash x and u bin's too, that way if you want to upgrade to cm10 you will be ready] and then restore rom in cmw) or put your phone in download mode (vol up+pwr) and use LG_KDZ_FW-Update_OfflineFix to flash a full kdz (that's how i did it) or like daniel.mota said use the official flash tool to make emergency recovery (probably the easiest method).
btw I tried flashing cmw 6 again a few days ago and it flashed fine this time, entered recovery fine, backed up fine but never restores correctly...
I agree. The new version has a lot of bugs. When I tried to reinstall a previous rom backup it stated that the md5sum was incorrect when it checked among other small glitches. I'm back to v5.0.2.7.
After back to version 5.0.2.7. The same back up was fine.
Sent from my LG-P925 using xda premium

lg g2 will not boot, not recognized but is showing as QSUSB_BULK

i have an lg g2 vs980 and i rooted it but have not yet installed a recovery like twrp it is only the very basic root with super user. it decided to install some ota update and now it will not boot past lg screen, white letters flash really fast all i could make out was secure boot error or something. i cannot get it into any kind of download or reset mode, iv tried absolutely everything anyone on this forum has recommended or suggested and nothing works, also when i connect it to my pc running windows 8 it is seen as QSUSB_BULK i have installed the correct updated drivers for my phone and iv manually installed them, nothing i have done will allow my pc to see my phone correctly. when i plug it in it under computer there are local drives f-u that pop up and say i have to format them in order to use them, but they are write protected so i cannot view whats in them, format them or anything. does anyone out there have any kind of suggestion to fix this or am i just completely stupid and missing some big major step? i am also very new to android this is my first android phone lol im a converted apple user haha so the more indept detailed instructions would be greatly appreciated
Same issue here
haeli said:
i have an lg g2 vs980 and i rooted it but have not yet installed a recovery like twrp it is only the very basic root with super user. it decided to install some ota update and now it will not boot past lg screen, white letters flash really fast all i could make out was secure boot error or something. i cannot get it into any kind of download or reset mode, iv tried absolutely everything anyone on this forum has recommended or suggested and nothing works, also when i connect it to my pc running windows 8 it is seen as QSUSB_BULK i have installed the correct updated drivers for my phone and iv manually installed them, nothing i have done will allow my pc to see my phone correctly. when i plug it in it under computer there are local drives f-u that pop up and say i have to format them in order to use them, but they are write protected so i cannot view whats in them, format them or anything. does anyone out there have any kind of suggestion to fix this or am i just completely stupid and missing some big major step? i am also very new to android this is my first android phone lol im a converted apple user haha so the more indept detailed instructions would be greatly appreciated
Click to expand...
Click to collapse
Has anyone come up with a solution to this? I am very new to Android, I have Rooted my G2 so I could install Custom Rom's. Yesterday I receive a OTA update, I refused it and then later when it came up again was going to refuse it, but my shaky finger touched the screen and started the update! next thing I know I have a $600.00 brick. if you hold the power button down It will flash the LG logo and then NADA, screen is lit but nothing happens. Hold the power button and after a few it will Flash the logo again but NADA again. If you hold the down and power button it will go to the reset screen, but again this will not reset the device. PLEASE HELP!
Thank you.

[Q] Ok so my device is not quite dead but close please help

Hi Everyone,
I've come on bended knee, and I have about 30 xda windows up where Ive tried to upgrade a perfectly working LG from android 2.2. But no matter what I try I cant get beyond the LG wink icon on the screen.
I have tried fastboot omao4boot 1.22 modified etc but I cant get past MLO (x-loader) I say YES to this but NO to 'fastboot devises' as per instructions (although why I say no to this, I dont know?) anyway it just says 'waiting for device' but nothing happens even if I take the battery out and disconnect from USB and reconnect, nothing ever happens?
So having redone the fastboot procedure, I managed to into boot mode - yellow round icon on screen and then tried to flash using LG flash tool 1.2 with LGP920 30A bin & fls files which it does and completes successfully, I have also used the LG recovery tool to flash recovery and firmware but all of the above wont let me boot the devise it just sits at the LG Icon.
Tried booting into recovery with 3d + vol + key but just ignores and goes to red LG Icon with the usual boot sound, I just cant get anything else to work! Is it down to the MLO loader issue. I dont know what else to do.
Please can anyone help me recover my phone I wanted to upgrade to JellycreamR5 cause its suppose to be a good rom but nothing now works :crying:
I know its not a busy forum now days and most have moved on, but please any assistance to get this beautiful phone going again would be brilliant.
Thanks for the time to read about this dilemma!
ATB
Ok, so if it boots to the LG logo with boot sound it is probably nothing wrong with bootloaders. It is either the system or just something incompatible on the data partition. Of you can make it too recovery try factory reset
Ok I think Ive fixed it!
Did lots of things to try to get to work, but heres roughly the guide.
Used 'rebooter' for Optimus 3d which saved the phone in the 1st instance, it was the only flasher that completed the flash... but remember 1st unplug the phone but micro usb in then remove the battery, then hold the + vol key and insert into the Win XP computer usb, I had already prepared and ran the rebooter.bat file which was waiting for omao device. Once detected keep hold the + key add battery when it says wait 5 secs, dont let the key go, say NO to flash boot but yes to the rest. It will say job done or words to that effect.
Turn on phone holding just the + key to get into download mode. Change the LGE CDMA USB SERIAL PORT to com41 in control panel device manager, refresh search for new hardware to check updated port.
Then use LG Flash to flash V3.0A which worked !
Disconnect the phone remove battery and reinsert, reboot devise, it will boot in TWRP which isnt great but good enough for flash, loaded a Rom onto the sd card and installed the software, after the usual clearing everything like Delvick/Settings etc.
Job done, rebooted and worked, still got TRWP on the boot loading would prefer Clockwork but never mind, had enough of fiddling and just enjoying having my device back
Havent tried a sim in it but might have to to the IMEI fix but hoping not.
Many thanks for your input, I know tech moves on, but there is a wealth on knowledge on these devices and it just seems to be lost in the ether.
Best wishes.

Categories

Resources