I used the phone for about 2 days after I updated to mango. While I was at class the phone died because of low battery. Once I plugged it back up it's been stuck at the samsung screen for three days now. Tried format, tried download mode but can't get the software to do anything when I open it just says "cannot image file", and I tired recovering the phone with zune. It will get to Step 2 and do nothing more even after running for a good 10 hours. Any suggestions? Using Samsung Focus 1.3
bulletdog said:
I used the phone for about 2 days after I updated to mango. While I was at class the phone died because of low battery. Once I plugged it back up it's been stuck at the samsung screen for three days now. Tried format, tried download mode but can't get the software to do anything when I open it just says "cannot image file", and I tired recovering the phone with zune. It will get to Step 2 and do nothing more even after running for a good 10 hours. Any suggestions? Using Samsung Focus 1.3
Click to expand...
Click to collapse
There is a chance that the battery went below control charge and it appears dead. Before you do anything to the phone I recommend to replace the battery. There is a control circuit in the battery that tracks capacity. If the capacity falls below a critical value, it won't charge anymore and the battery appears dead.
edit: sorry, never mind, I didn't read your post carefully enough.
Do you have an expansion microsd card? if so, pull it out... might just be a cooincidence that you had one fail.
ROCOAFZ said:
Do you have an expansion microsd card? if so, pull it out... might just be a cooincidence that you had one fail.
Click to expand...
Click to collapse
Never used a SD card with phone, I went to ATT store and tried a new battery, didn't help. From reading it sounds like a firmware ordeal but like I said before the software for tye binaries won't do anything
tried running zune restore again, this time got a error message. Downloaded the windows phone support tools and and ran it. This time got a error of 80004005
This happened to me when I was trying to hack update to mango. I fixed it by doing these steps.
1) Restore it to the original ROM. I think it is 7004.
Here is a good tutorial (just read the description no need to watch the vid http://www.youtube.com/watch?v=hvw5gLY6sOc
2) Use Chevron hack to update to nodo.
3) Update to Mango
Not sure if it has changed where the device will auto update from 7004 to 7720, so you can check that right after you flash it.
Sk8rjwd said:
This happened to me when I was trying to hack update to mango. I fixed it by doing these steps.
1) Restore it to the original ROM. I think it is 7004.
Here is a good tutorial (just read the description no need to watch the vid
2) Use Chevron hack to update to nodo.
3) Update to Mango
Not sure if it has changed where the device will auto update from 7004 to 7720, so you can check that right after you flash it.
Click to expand...
Click to collapse
Followed the link and stuck at connecting my phone while it's in download mode, the computer wont recognize it so I can't start the flash. The search continues.
UPATE:
Finally got the computer to recognize the phone, I had to download the samsung usb drivers from their website. Installing mango right now. Should I try a recovery now that the phone is working that was made before the orginal mango update? Or should I just suck it up and start from scratch. THANKS Sk8rjwd!
bulletdog said:
I used the phone for about 2 days after I updated to mango. While I was at class the phone died because of low battery. Once I plugged it back up it's been stuck at the samsung screen for three days now. Tried format, tried download mode but can't get the software to do anything when I open it just says "cannot image file", and I tired recovering the phone with zune. It will get to Step 2 and do nothing more even after running for a good 10 hours. Any suggestions? Using Samsung Focus 1.3
Click to expand...
Click to collapse
i got this problem with my omnia gt 8350 , battery die, and now my phone is brick no power no nothing replace the battery still no go. no power, when i plug to usb the pc telling me to install driver called QHSUSB installed susses ,and in the device manager i can see the phone is detected, by the windows but, still cant reflash it, i dont have the rom for this device plus, i cant boot to download mode.
find another phone with a similar battery, running something other than wp7 and charge it till boot. you should be good to go from then on. happened to me once. lucky my dad has an incredible s so my mozart battery fit there and i could charge. i was on beta mango though. rtm mango fixed this issue for me where in several cases my battery died but i still managed to get it charged up normally
Related
AFTER ATTEMPTED DEV MANGO UPDATE 7661 build RECEIVED ERROR CODE C101002E
NOTE:I HAVE SUCCESSFULLY UPDATED 3 OTHER SAMSUNG FOCUS CELL PHONES AS WELL AS DOWNGRADED/FLASHED BACK TO ROM 7004 WITH NO PROBLEMS-SO IDK WUTS UP WITH THIS PHONE
I TRIED TO FLASH ROM BUILD 7004-BUT DURING THE PROCESS THE DOWNLOAD SCREEN ON MY CELL PHONE WENT BLANK.
I REMOVED THE BATTERY & WAITED FOR APPROX 5 MINUTES. THEN REINSERTED IT. ATTEMPTED POWERING UP & FELT VIBRATION BUT NO SCREEN DISPLAY. TRIED TO FIND RESTORE BACKUP ON ZUNE, BUT WOULDN'T LET ME RESTORE FROM ZUNE. ALSO COULDN'T FIND BACKED UP PKS FILE EITHER ON WP7 BACK UP TOOL--TRIED TO RETRIEVE FROM ARCHIVED FILE; BUT KEPT POSTING UNSUCCESSFUL LOAD OF ARCHIVED FILE. (also tried charging battery overnight, as well as used fully charged battery from 1 of my other samsung focus phones that are MANGOED already-but no luck either.)
I WAS ABLE TO OBTAIN DOWNLOAD MODE WITHOUT SCREEN DISPLAY & I
REATTEMPTED FLASHING ROM BUILD 7004--THIS TIME THE PHONE WENT COMPLETELY DEAD DURING THE ROM FLASHING; RECEIVED FAILED FLASH MESSAGE & NOW THE PHONE WILL NOT TURN ON, WILL NOT SOFT OR HARD RESET, WILL NOT GO INTO RECOVERY MODE, OR GO INTO DOWNLOAD MODE!!
ANY SUGGESTIONS--WILL A JIG POSSIBLY WORK?? ANY INPUT WOULD BE APPRECIATED!
I'm not sure a jig is going to help. But I guess your only possibilities are trying a jig or RMA. If you want to make a jig, read this post I wrote.
Good luck!
Heathcliff74
Heathcliff74
Thanks again for your quick response-- I'm going to try a jig & follow your post.
Wish me luck!!!
I tried (risk) this tonite and it work out good. It took me like 20 min (should be shorter if I understand with the instruction means the first time). It's prretty simply and straight forward.
**It works with me but I can't guarantee it'll work with anyone else. I just think that it don't make sense requiring a window XP machine to do the update. I don't responsible to anyone brick their phone**
1) Go to LG Support web site and "Download LG Mobile Support Tool to PC"
2) After download the LG Mobile support tool (updater tool), run it. It'll show phone is discounted. Plug in your phone and it should start connecting it. If doesn't connect, click the install driver on the right hand side. After the new driver installed it will connect.
3) Once connected to your phone, click the update button on the bottom. The software will update your phone now. Your phone will show up the S/W update screen now.
4) When the installation bar run to 50%, it'll stop and ask you to do something. The instruction ask you to first unplug the phone; second remove battery and then put it back in; third turn on your phone (it'll show S/W update screen); forth click "restart" button; fifth when it show phone disconnected, plug back in your phone and click restart again.
5) Now it'll start the update all over again from 0%. Here's the tricky part. This time the installation will run pass 50% but stop at 75% asking you to do the same thing on step 4. So you just do exactly what you just did from step 4.
6) Same thing it'll start the update from 0% again. This time it'll run all the way to 100% and complete the update. Once it complete your phone will boot up again. Then you'll have updated baseband 2.3.3 v21e rom.
After that you'll do all the recovery and flashing as usual. The speed is faster than 2.2.2 (I test it with a bone stock G2x). Everything is working fine.
I just found one problem. IF you need to install new driver from the LG Mobile Support Tool in order to connect your phone, you'll need to re-install the T-Mobile USB driver v2.2 to get your phone mount to your PC again.
Enjoy and hope this help.
PS: If the Mods find it useful, please sticky this.
nice write up.
A few things i found.
works much better on 32 bit versions.
you must have a t-mobile SIM for the updater to work.
I am on Walmart Family Mobile and if fails the Cell # check.
if you fail somewhere, it may be required to uninstall everything and start over.
darknessxyz said:
I tried (risk) this tonite and it work out good. It took me like 20 min (should be shorter if I understand with the instruction means the first time). It's prretty simply and straight forward.
**It works with me but I can't guarantee it'll work with anyone else. I just think that it don't make sense requiring a window XP machine to do the update. I don't responsible to anyone brick their phone**
1) Go to LG Support web site and "Download LG Mobile Support Tool to PC"
2) After download the LG Mobile support tool (updater tool), run it. It'll show phone is discounted. Plug in your phone and it should start connecting it. If doesn't connect, click the install driver on the right hand side. After the new driver installed it will connect.
3) Once connected to your phone, click the update button on the bottom. The software will update your phone now. Your phone will show up the S/W update screen now.
4) When the installation bar run to 50%, it'll stop and ask you to do something. The instruction ask you to first unplug the phone; second remove battery and then put it back in; third turn on your phone (it'll show S/W update screen); forth click "restart" button; fifth when it show phone disconnected, plug back in your phone and click restart again.
5) Now it'll start the update all over again from 0%. Here's the tricky part. This time the installation will run pass 50% but stop at 75% asking you to do the same thing on step 4. So you just do exactly what you just did from step 4.
6) Same thing it'll start the update from 0% again. This time it'll run all the way to 100% and complete the update. Once it complete your phone will boot up again. Then you'll have updated baseband 2.3.3 v21e rom.
After that you'll do all the recovery and flashing as usual. The speed is faster than 2.2.2 (I test it with a bone stock G2x). Everything is working fine.
I just found one problem. IF you need to install new driver from the LG Mobile Support Tool in order to connect your phone, you'll need to re-install the T-Mobile USB driver v2.2 to get your phone mount to your PC again.
Enjoy and hope this help.
PS: If the Mods find it useful, please sticky this.
Click to expand...
Click to collapse
Man, this is a dangerous post. You were told to remove your battery, because a connection could not be made. If you remove the battery during an install that has no connection problem, you will brick your phone.
Be very clear here. When updating anything, first and foremost, follow instructions listed on the page. Read the instructions through BEFORE starting update. If you do not understand, do NOT update.
Do not adlib. Do not think you know better. Do NOT pull your battery unless you are told Pull your battery.
32bit/64 bit Windows 7 makes not difference. It will update equally with either. But you should protect your update by making sure pop up blockers and malware/AV are turned off. Turn off fax programs, skype, things like that. Then try your update. BTW....this is true for most updates on any other device, to include your PC.
Just be careful and follow instructions.
I dont understand I Used the LG update tool the day no wait the hour the update came out I have a windows 7 64 bit pc my phone is a p999dw and it went off without a hich. I did not have to pull the battery and I did not have to install the updated drivers. I had the LG mobile updater on my computer since I bought the phone about 2 weeks after relese and discovered that I needed to install the drivers. I dont understand why all the problems and I never heard You can only use an xp machine. I did however read that you originally needed an xp machine to fix your phone if it bricked but even that was fixed. Just like the dude said in the post above me just read the directictions and be careful
ehh all i can see now is S/W uptade srcreen, i can reboot to cwm recovery,
does it mean i need a new phone or there is still a chance? ;/
Nvm, ive just called TM and they gonna send me a replacement
I decided to try to update to GB because my G2X rebooted while on the charger, clock night mode turns off and the screen locks, and wifi is ok but resets sometimes. My phone is stock 2.2 with stock recovery but rooted.
I turned off all programs on my Windows 7 32 bit laptop, turned off anti virus and turned off Windows firewall. The updater ran ok, checked the phone environment and downloaded the update. Then at 4% when the phone is supposed to download into software update mode, it just sat there staying in Android. After the update failed and it told me to remove the cable and remove battery, etc., I just shutdown the phone, did a battery pull and turned the phone back on. I then canceled the update.
My phone booted back into Android no problem. I tried to boot into recovery using Quickboot but that just rebooted the phone back into Android. My questions are as follows:
1. Did the update change anything on the phone or did it fail before attempting to change anything?
2. Why did it fail to boot into software update mode? Do I need to try another USB port or another computer?
3. Should I use the alternate method on a Windows XP machine that people use when their phone is soft bricked?
4. Should I just install CWM recovery and use the pre-rooted zip of GB with the old baseband?
5. Or should I just forego the update for now and see if another update is released?
Try reinstalling everything, and restarting your computer. It worked just fine on Windows 7 Ultimate x86, and x64.
My update went the same way but everytime I retried it got a little further so I just retried it over and over till I hit 100 percent
Sent from my LG-P999 using XDA App
I just tried to run the LG update program on my XP machine but I got a runtime error (see attached). Anybody know what this means and how to fix it?
Does anyone know why it just sits there on 4% and never boots into the software update mode? Can I just run it and then when it fails manually boot into software update mode? Or is that risking a brick?
jboxer said:
I decided to try to update to GB because my G2X rebooted while on the charger, clock night mode turns off and the screen locks, and wifi is ok but resets sometimes. My phone is stock 2.2 with stock recovery but rooted.
I turned off all programs on my Windows 7 32 bit laptop, turned off anti virus and turned off Windows firewall. The updater ran ok, checked the phone environment and downloaded the update. Then at 4% when the phone is supposed to download into software update mode, it just sat there staying in Android. After the update failed and it told me to remove the cable and remove battery, etc., I just shutdown the phone, did a battery pull and turned the phone back on. I then canceled the update.
My phone booted back into Android no problem. I tried to boot into recovery using Quickboot but that just rebooted the phone back into Android. My questions are as follows:
1. Did the update change anything on the phone or did it fail before attempting to change anything?
2. Why did it fail to boot into software update mode? Do I need to try another USB port or another computer?
3. Should I use the alternate method on a Windows XP machine that people use when their phone is soft bricked?
4. Should I just install CWM recovery and use the pre-rooted zip of GB with the old baseband?
5. Or should I just forego the update for now and see if another update is released?
Click to expand...
Click to collapse
Follow your Item 4
Finally got it updated
Used Windows 7 32bit.
The update progressed very scarily.
I downloaded the drivers and reinstalled them directly from the update program. I then used a different USB port then my previous attempt, unplugged all other USB devices, and shutdown everything running on the computer I could including Avast andti-virus and the Windows Firewall. This time when I plugged the G2X into my computer a lot more devices installed than last time (first time only 2 devices were installed, this time about 8 to 10).
During the first download of the firmware I canceled it because I realized I left the micro sd card in the phone and the instructions on the website say to remove the card. Then I also decided to unroot the phone and remove all programs that require root access. Since the phone would be unrooted after an update I decided I didn't want superuser in the system if I couldn't use it, and after the update I would be unable to remove it since the phone would not be rooted.
Then I ran the program again and this time the phone booted into software update mode. It started pushing the update to the phone and at 5% the phone disconnects from the computer and reconnects (does this three times during the update) but the software doesn't see the phone and tells me to unplug the USB cable, remove the battery, reinsert the battery and turn the phone back on. But I heard the computer reconnect to the phone so I decided I would just remove the cable and reinsert it. This worked and the update started over again. This time it went past 5% and then reset the phone connection again at 46%. It then slowly completed the update resetting one more time at 76% and when it reconnected it went back to 75% but then progressed to 100% and rebooted the phone.
It now has an updated baseband and Gingerbread 2.3.3. I am leaving it unrooted for now and just use it stock.
jboxer said:
Does anyone know why it just sits there on 4% and never boots into the software update mode? Can I just run it and then when it fails manually boot into software update mode? Or is that risking a brick?
Click to expand...
Click to collapse
I do! It's installing one of the THREE usb drivers that it installs over the course of the upgrade. Mine got stuck at 4% for just a second (at which point I about **** my pants), but then I saw a Win7 notification pop up that it had just installed a USB driver, and then it proceeded to do the update.
So maybe the failure mode is the LG updater not being able to install a USB driver?
Maris_ said:
Follow your Item 4
Click to expand...
Click to collapse
Is there any significant reason to update to get the newest baseband and then flash CM7? Or is there no benefit from the new baseband?
brdma said:
Is there any significant reason to update to get the newest baseband and then flash CM7? Or is there no benefit from the new baseband?
Click to expand...
Click to collapse
July 15, 2011 baseband has more reliable wifi and much better GPS lock. After the scares of getting mine updated finally, my G2X has had no issues in the 30+ hours since the update. No reboots on charger, no sleep of death and everything is working as it should.
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.
My Google Pixel 2 (running May version already) was working fine until last week. I don't recall if my memory ran out, but I don't think so. After using it for a while, I drove home, and when I got home, the phone was off. Thinking that the battery was just dead, I plugged it into a charger , turned it on, and didn't think too much about it. When I next looked at my phone, it was stuck on the G logo with a loading bar under there.
I tried turning the phone off, charging it more, etc.
I contacted google support and they told me that the only way is to factory reset (i want to keep my data, though). I began looking online and came across sideloading OTA, which seemed to be the only way to save my data. I am not that tech savvy and wasn't sure how to do it, so for a second time I contacted google support, they told me that for sideloading, I should go to a UBreakIFix, an authorized Google repair place. I made an appointment and when I got there, I asked them to help do a sideload of the OTA or more information about it, and the technician didn't even seem to know what that is. Then after a long diagnosis, they also told me that i have to factory reset and wanted to charge me $80 to do so...
I decided to come home and try to sideload myself.
Techno Bill had some very detailed explanations on how to do it, and some of the google support threads also gave other suggestions as well. I appreciate all of them and went through everything.
While trying to sideload, I came across a few issues:
- First, I tried to sideload from my laptop (windows 10), which only has USB C ports. Apparently, this sideload doesn't work when you use USBC to USBC cables, so it kept getting stuck at verifying update package.
- Then, when I realized that, I switched to a desktop running windows 7. And my USB C to USB A cable. But my computer wasn't able to read my Pixel 2. Thinking that it was that my computer was too old, I went to my parents house. (I later found out that it was my USB C- USB A cable that didn't work)
- Then at my parents house running Windows 8, my sideload worked, but at 94%, it always said completed with Status 0. Then it would prompt me to reboot, which it did, but the it keeps getting stuck on the G loading screen.
- Then I tried going to a friend's house, windows 10, and tried the same, and every time, it would complete with status 0 at 94%. but it continues to get stuck at the G loading screen
Then I kept searching and tried different OTAs like P version or previous versions, etc. and they would usually say "installation aborted" because the version is a downgrade. Also tried powering off and on 7 times,
I thought that maybe I needed to use a new version of Google OTA, which just released this week (June version), but for some reason, it still tells me that it's a downgrade, when my phone's current version is the May version.
Does anyone have any idea what I should do at this point?
I would really like to keep my data.
Thanks in advance.
wallychang said:
My Google Pixel 2 (running May version already) was working fine until last week. I don't recall if my memory ran out, but I don't think so. After using it for a while, I drove home, and when I got home, the phone was off. Thinking that the battery was just dead, I plugged it into a charger , turned it on, and didn't think too much about it. When I next looked at my phone, it was stuck on the G logo with a loading bar under there.
I tried turning the phone off, charging it more, etc.
I contacted google support and they told me that the only way is to factory reset (i want to keep my data, though). I began looking online and came across sideloading OTA, which seemed to be the only way to save my data. I am not that tech savvy and wasn't sure how to do it, so for a second time I contacted google support, they told me that for sideloading, I should go to a UBreakIFix, an authorized Google repair place. I made an appointment and when I got there, I asked them to help do a sideload of the OTA or more information about it, and the technician didn't even seem to know what that is. Then after a long diagnosis, they also told me that i have to factory reset and wanted to charge me $80 to do so...
I decided to come home and try to sideload myself.
Techno Bill had some very detailed explanations on how to do it, and some of the google support threads also gave other suggestions as well. I appreciate all of them and went through everything.
While trying to sideload, I came across a few issues:
- First, I tried to sideload from my laptop (windows 10), which only has USB C ports. Apparently, this sideload doesn't work when you use USBC to USBC cables, so it kept getting stuck at verifying update package.
- Then, when I realized that, I switched to a desktop running windows 7. And my USB C to USB A cable. But my computer wasn't able to read my Pixel 2. Thinking that it was that my computer was too old, I went to my parents house. (I later found out that it was my USB C- USB A cable that didn't work)
- Then at my parents house running Windows 8, my sideload worked, but at 94%, it always said completed with Status 0. Then it would prompt me to reboot, which it did, but the it keeps getting stuck on the G loading screen.
- Then I tried going to a friend's house, windows 10, and tried the same, and every time, it would complete with status 0 at 94%. but it continues to get stuck at the G loading screen
Then I kept searching and tried different OTAs like P version or previous versions, etc. and they would usually say "installation aborted" because the version is a downgrade. Also tried powering off and on 7 times,
I thought that maybe I needed to use a new version of Google OTA, which just released this week (June version), but for some reason, it still tells me that it's a downgrade, when my phone's current version is the May version.
Does anyone have any idea what I should do at this point?
I would really like to keep my data.
Thanks in advance.
Click to expand...
Click to collapse
You might make sure you have the most current Android platform tools.
Ermmm, just the same issue as mine, my memory just a little ran out. Google's June's Full OTA for pixel 2 is a broken one, as I posted in the google forum thread 50683931 (I can't post link for now, sorry), but not replies.
So, you can do the factory reset now (via official recovery) or maybe you need to wait for July's Full OTA, unless Google guys fixed June's pixel2 full OTA time issue, it's a log time already .
BTW, I am still waiting for the fix.
wallychang said:
My Google Pixel 2 (running May version already) was working fine until last week. I don't recall if my memory ran out, but I don't think so. After using it for a while, I drove home, and when I got home, the phone was off. Thinking that the battery was just dead, I plugged it into a charger , turned it on, and didn't think too much about it. When I next looked at my phone, it was stuck on the G logo with a loading bar under there.
I tried turning the phone off, charging it more, etc.
I contacted google support and they told me that the only way is to factory reset (i want to keep my data, though). I began looking online and came across sideloading OTA, which seemed to be the only way to save my data. I am not that tech savvy and wasn't sure how to do it, so for a second time I contacted google support, they told me that for sideloading, I should go to a UBreakIFix, an authorized Google repair place. I made an appointment and when I got there, I asked them to help do a sideload of the OTA or more information about it, and the technician didn't even seem to know what that is. Then after a long diagnosis, they also told me that i have to factory reset and wanted to charge me $80 to do so...
I decided to come home and try to sideload myself.
Techno Bill had some very detailed explanations on how to do it, and some of the google support threads also gave other suggestions as well. I appreciate all of them and went through everything.
While trying to sideload, I came across a few issues:
- First, I tried to sideload from my laptop (windows 10), which only has USB C ports. Apparently, this sideload doesn't work when you use USBC to USBC cables, so it kept getting stuck at verifying update package.
- Then, when I realized that, I switched to a desktop running windows 7. And my USB C to USB A cable. But my computer wasn't able to read my Pixel 2. Thinking that it was that my computer was too old, I went to my parents house. (I later found out that it was my USB C- USB A cable that didn't work)
- Then at my parents house running Windows 8, my sideload worked, but at 94%, it always said completed with Status 0. Then it would prompt me to reboot, which it did, but the it keeps getting stuck on the G loading screen.
- Then I tried going to a friend's house, windows 10, and tried the same, and every time, it would complete with status 0 at 94%. but it continues to get stuck at the G loading screen
Then I kept searching and tried different OTAs like P version or previous versions, etc. and they would usually say "installation aborted" because the version is a downgrade. Also tried powering off and on 7 times,
I thought that maybe I needed to use a new version of Google OTA, which just released this week (June version), but for some reason, it still tells me that it's a downgrade, when my phone's current version is the May version.
Does anyone have any idea what I should do at this point?
I would really like to keep my data.
Thanks in advance.
Click to expand...
Click to collapse
lonelinsky said:
Ermmm, just the same issue as mine, my memory just a little ran out. Google's June's Full OTA for pixel 2 is a broken one, as I posted in the google forum thread 50683931 (I can't post link for now, sorry), but not replies.
So, you can do the factory reset now (via official recovery) or maybe you need to wait for July's Full OTA, unless Google guys fixed June's pixel2 full OTA time issue, it's a log time already .
BTW, I am still waiting for the fix.
Click to expand...
Click to collapse
I don't know about the OTA but there's nothing wrong with the full system zip.
OP, did you ever get this resolved? Either getting the phone booted or getting access to your data?
My phone is in a similar boat, stuck at G logo and empty loading bar.
Some updated was downloaded and the phone requested for a restart, restarted and now stuck at G logo.
I have tried to flash the OTA, but stuck at verify package, tried on two different Windows 10 machine, latest platform tools from Google, two different usb A to C cable, but same behaviour.
There are some valuable data I would like to retrieve. Does anyone have and suggestion on what I should do next?
You can try to flash the last Android 9 OTA, then the first Android 10 OTA, and then the latest OTA on Google's website. That should fix the issue.
The above doesn't work, as old OTAs fail. Every single Android 10 OTA failed for me, or worked/installed ok as sideload (July and Aug since they weren't older) but gave me the G logo for hours. The Android 11 beta 3 preview DID WORK: developer.android.com/preview/download-ota Clearly a software bug.
*If you get this bug please try the Android 11 OTA *
For reference, I got the G logo/boot fail situation not after updating but after my battery drained entirely, phone shut down, i plugged in phone and booted and then it sat there. So battery related software bug (???)
For fixes like what you all are attempting, you shouldn't be using OTAs. In fact, if you are rooted, it's best to never use OTAs and always update with the latest full system image.
Go to Google's site for Pixel factory images and download the latest image for your device, make sure you have the latest version of platform-tools on your computer, then follow my instructions from this thread:
https://forum.xda-developers.com/showpost.php?p=83009945&postcount=2
Whenever it asks if you want to unlock or wipe data, press N (no).
If all the previous failed attempts haven't somehow corrupted or already wiped your data, you should be able to boot back into your phone normally.
"If you are rooted"
Yeah, if i had root or even an unlocked bootloader I would have had five thousand other options.
jallenhayslett said:
For fixes like what you all are attempting, you shouldn't be using OTAs. In fact, if you are rooted, it's best to never use OTAs and always update with the latest full system image.
Go to Google's site for Pixel factory images and download the latest image for your device, make sure you have the latest version of platform-tools on your computer, then follow my instructions from this thread:
https://forum.xda-developers.com/showpost.php?p=83009945&postcount=2
Whenever it asks if you want to unlock or wipe data, press N (no).
If all the previous failed attempts haven't somehow corrupted or already wiped your data, you should be able to boot back into your phone normally.
Click to expand...
Click to collapse
Unlocked bootloader + Magisk + TWRP + custom kernel here, I've always used OTAs without a problem. Just have to use fastboot to boot the TWRP image and reinstall after an update. Flashing radio and bootloader are easy too.