Related
okay guys here's my issue. I was flashing over to liberty and I forgot to wipe everything so as liberty was going through its stuff through bootstrap I pulled the battery hoping to stop the process.
HOWEVER, I am not stuck at the "liberty" logo. I have tried to sbf and I am getting....
failed flashing process: Phone (0000): Phone did not re-enumerate after RAM-downloader was sent. (0x703E) phone was disconnected.
Can someone please help me?
I've seen people have sucess with SBF errors by renaming the SBF file, trying a diff comp, and if ya vista or win7 ya have to be running as Admin. Give any of those a try that ya can while I'm looking over google to see if I can find anything more directly relevant to the errors you are getting.
Luckily I still have my x sitting around. I'm using macbook pro with vmware running windows 7. I have sbfed successfully on my x using the same setup.
Sent from my DROIDX using Tapatalk
I should also note that I tried booting into recovery and wiping data and cache still didn't help.
I do have a backup of stock from that I made. However, I just don't think its possible for me to access that backup to restore?
Sent from my DROIDX using Tapatalk
I'm not sure then. I've looked over quite a few different articles were people have had this problem, and have had it solved, and everytime it was some type of comp issue that was causing it. Some people fixed by changing USB ports, some by reinstalling the Moto RSD software (Also, with RSD, make sure you are using version 4.8 or 4.9), or using a completely different computer or OS. Past that the only other thing I can suggest is make sure you have the correct SBF file, and maybe try re-downloading it incase it somehow got corrupted during the download.
EDIT: Which recovery are you using? The stock recovery, or Clockwork? If ya using stock, then as far as I am aware you don't have the ability to backup/restore.
-Gilgamesh- said:
I'm not sure then. I've looked over quite a few different articles were people have had this problem, and have had it solved, and everytime it was some type of comp issue that was causing it. Some people fixed by changing USB ports, some by reinstalling the Moto RSD software (Also, with RSD, make sure you are using version 4.8 or 4.9), or using a completely different computer or OS. Past that the only other thing I can suggest is make sure you have the correct SBF file, and maybe try re-downloading it incase it somehow got corrupted during the download.
EDIT: Which recovery are you using? The stock recovery, or Clockwork? If ya using stock, then as far as I am aware you don't have the ability to backup/restore.
Click to expand...
Click to collapse
I am using rsd 4.9. I tried everything you stated except a new computer.
I have droid 2 bootstrapper installed and clockwork. However, whenever I boot into recovery it keeps bringing me to the stock one so I can't restore. If I can figure out how to restore maybe I would be good?
Sent from my DROIDX using Tapatalk
Likely you got far enough into SBF to erase clockwork. Though you can try pulling you battery during boot while its on the moto logo, and if clockwork is still installed it will then boot directly to it.
Yupp nothing. Stuck at the liberty boot logo where it says "liberty"
Sent from my DROIDX using Tapatalk
I donno then. I would try a diff comp and see if that helps. Or maybe someone else will see this thread and have some other ideas. You may could also try posting directly in the SBF thread, maybe someone with more experance with it will see it there? Just a thought.
Thanks for the help.
If anyone else can help I am all ears!
Sent from my DROIDX using Tapatalk
Ok, the bad news...
The first thing Liberty does when installing is format the /system directory. I dont know at what point you pulled the battery but, while you did at one time have bootstrapper and clockwork mod installed, you no longer do. Your only option at this point is to SBF.
I have had, as have others, lots of issues with getting it to go through on Windows 7. It will get to a point where it tries to switch modes (unfortunately I don't recall the name of that mode right now), then it wont find the driver fast enough and fail. If you can get that driver installed when it tries to switch modes, it should work, and cause no problems in the future. The problem for you though, may be even greater given that Windows 7 is bad enough and being run in VMware probably will just compound those issues.
If at all possible, try from a windows XP machine.
OK so im not sure about the Liberty ROM however I have had to SBF when I tried installing Fission 2.4.3 on my D2G.
My process was turning the phone on boot mode. This is done but holding the +- Volume button and then hitting the power button.
Next I got RSDLite 4.9 and lastest drivers from motorola. Next is restart computer! This was important as RSD wasn't finding my phone until I did. Once I restarted ran RSD hooked up the phone in boot mode found the sbf file and hit start. Took about 15 min to finish.
Not sure if this helps.
Rsd is finding my phone no problem right away. I suppose I should try it on a different computer though, one that's running xp.
Sent from my DROIDX using Tapatalk
buryboi said:
Ok, the bad news...
The first thing Liberty does when installing is format the /system directory. I dont know at what point you pulled the battery but, while you did at one time have bootstrapper and clockwork mod installed, you no longer do. Your only option at this point is to SBF.
I have had, as have others, lots of issues with getting it to go through on Windows 7. It will get to a point where it tries to switch modes (unfortunately I don't recall the name of that mode right now), then it wont find the driver fast enough and fail. If you can get that driver installed when it tries to switch modes, it should work, and cause no problems in the future. The problem for you though, may be even greater given that Windows 7 is bad enough and being run in VMware probably will just compound those issues.
If at all possible, try from a windows XP machine.
Click to expand...
Click to collapse
Do you know what driver your talking about or where to find it?
Okay guys I tried doing it on Windows XP and I am still getting the same exact message it wont' re-enumerate.
I am scared beyond belief right now and don't know what to do. If someone can suggest something I would really appreciate it.
Not sure if this helps, but this is what "my device" info says while in rsd lite...
IMEI/ESN/MEID:
N / A
Technology:
N / A
Software Version:
N / A
Flex Version:
N / A
Bootloader Version:
v0x00D011
DRM Version:
N / A
AP Die ID:
14b0001391953a0a0000d8ff0100
BP Die ID:
0000000000000000cd6932890485
AP Public ID:
6df40c77da38d6f01bc27cc2f40c041ee4491ae2
BP Public ID:
040000000500000002000000ffff0000ed153289
If you are on Win7 64 then try the drivers in the attached zip file.
It is the BP passthrough mode that fails at the end of the flash because it needs to load a separate interface to flash the baseband radio partition.
That interface is a Motorola Flash device MDM6600 and not the S-Flash OMAP3460 device.
If you are having trouble with the drivers loading during the flash cycle re enumeration then you can try this trick to get them to load.
Turn off the phone and then power on holding the Volume Up + Power.
The phone will boot to the M Logo and just stay there like it is hung.
It is now in BP passthrough mode and will enumerate as a Motorola MDM6600 flash device and Windows will attempt to load those drivers when you connect the USB cable. Point the New Hardware Found wizard to the folder where you extracted the zip and it should load them. If not, you may have to manually force it to load them in the Have Disk dialog.
Now pull the battery and reboot the phone normally and try flashing in RSD Lite again. You will already have the BP passthrough interface drivers loaded now and it should re enumerate and complete the flash of the baseband(CG5) and reboot the phone at the end. Wait at least a minute after it reboots for all the post boot initializations to complete and RSD Lite should eventually say Pass and allow you to disconnect without the error warning about damaging the attached device.
If none of this works, get an XP box and it will all work without any issues 99% of the time.
Good luck!
Okay... So I downloaded the drivers, connected via USB and it did show up as what you said it would. However, I then ran the sbf and it says "The Motorola AP flash interface could not be found and kept failing.
What do I do?
Also, another thing it now says my battery is low. If I just plug it into the wall, will it charge or do I need to USB it? I can't tell if its charging or not
nickb2005 said:
Also, another thing it now says my battery is low. If I just plug it into the wall, will it charge or do I need to USB it? I can't tell if its charging or not
Click to expand...
Click to collapse
It won't charge in the bootloader until you have software on your phone you need to use another D1 or D2 to charge. Or use an external charger.
If windows isn't working there are ways to flash in linux that usually yield better results.
Sent from my DROID2 using XDA App
Getting Rainbow screen on every boot and when trying to get to recovery mode
For some reason I cannot get my computer to detect my device thus I can not even get into download mode. when I launch Odin and and not able to access my SD. I am at a lost here since now I cannot flash nor can I odin to get back to stock can anyone help here? I think I have tried everything I can find.
I just recently flashed octane 2.x per the instructions under development
rozzko said:
Getting Rainbow screen on every boot and when trying to get to recovery mode
For some reason I cannot get my computer to detect my device thus I can not even get into download mode. when I launch Odin and and not able to access my SD. I am at a lost here since now I cannot flash nor can I odin to get back to stock can anyone help here? I think I have tried everything I can find.
I just recently flashed octane 2.x per the instructions under development
Click to expand...
Click to collapse
If you came from Froyo, follow this guide: http://forum.xda-developers.com/showthread.php?p=16762954
Hope this helps.
sent from my CommandCenter using xda premium
sounds like the bootloader.
flash a froyo rom, then try to odin. AFTER you have tried installing the drivers linked in the previous post. That guide should work.
Did you get this fixed?
Sent from my SGH-T959V using xda premium
I bought a Jig an can get into download mode but still cant get into recover (because of the rainbow screen) and i cannot get my computer to recognize my my phone either via sd or via odin or i think i could solve this.
thanks in advance
I bought a Jig an can get into download mode but still cant get into recover (because of the rainbow screen) and i cannot get my computer to recognize my my phone either via sd or via odin or i think i could solve this.
thanks in advance
Click to expand...
Click to collapse
Go into the control panel & uninstall the USB drivers & kies mini if installed. Then reinstall Kies Mini & use the menu option to reinstall the drivers. See if that helps.
Sent from my SGH-T959V using XDA App
I re installed drivers several times and used a different machine. I feel like I am stuck and there might now be a solution to this except toss the phone in the ocean!
rozzko said:
I re installed drivers several times and used a different machine. I feel like I am stuck and there might now be a solution to this except toss the phone in the ocean!
Click to expand...
Click to collapse
Could it be the cable you're using? I've seen quite a few posts here about people using cables that were bad and/or too long and it prevented the phone from being recognized via USB. People could charge the phone but not use ODIN or anything.
Do you have a different cable to try?
ive tried two different cables, i could try another one thats a good idea. somehow i think maybe i messed up the mounting, i thought i followed the instructions to a t. UMMU .. i will try a few different cables when i get home tonight... actually just tried at work no dice, my system storage is also only showing 126 MB
rozzko said:
ive tried two different cables, i could try another one thats a good idea. somehow i think maybe i messed up the mounting, i thought i followed the instructions to a t. UMMU .. i will try a few different cables when i get home tonight... actually just tried at work no dice, my system storage is also only showing 126 MB
Click to expand...
Click to collapse
I thought the phone did not boot up. How are you seeing how much storage you have left?
I'm curious to know what state it really is in. There has to be a way to get it going for you.
the phone boots fine during the boot after the initial boot screen where it says galaxy s 4g it goes into rainbow patterns. so every time i try to get into recovery when I am in the recovery menu (or into where the recovery menu should be) i cannot see anything because of the rainbow screen. I was told maybe i have the wrong boot loaders installed.
because i cant see recovery and I cannot get my computer to see my phone I have no idea what to do get my phone back to stock to start over.
This is why I am stuck.
If i could get my computer to see the phone I think i could odin back to stock, using the dongle is half the battle as i can get in recovery
rozzko said:
the phone boots fine during the boot after the initial boot screen where it says galaxy s 4g it goes into rainbow patterns. so every time i try to get into recovery when I am in the recovery menu (or into where the recovery menu should be) i cannot see anything because of the rainbow screen. I was told maybe i have the wrong boot loaders installed.
because i cant see recovery and I cannot get my computer to see my phone I have no idea what to do get my phone back to stock to start over.
This is why I am stuck.
If i could get my computer to see the phone I think i could odin back to stock, using the dongle is half the battle as i can get in recovery
Click to expand...
Click to collapse
Pardon me if I'm not getting it....but yo said it boots fine but then you get the rainbow screen when the Galaxy S 4G logo should appear? The rainbow screen is definitely a boot loader issue. I'm just trying to figure out a way to either get you into a download mode where the phone is recognized or into recovery so you can get it going again.
How are you getting it into recovery mode?
I'm wondering if Heimdall would be your best bet? You could try to download it from here, extract it somewhere, then go into the Drivers folder and double-click zadig.exe. Select Options from the menu bar, select List All Devics then select Samsung Android Composite (something along those lines), then click Install Driver. This is a different driver than the one that comes from Samsung.
After that, maybe try Bhundven's [Heimdall][One-Click][UVKJ6] The KJ6 Heimdall One-Click Collection [12/11/2011]. Select whichever one-click file you want to go for and follow his instructions. They all have the GB bootloaders in them, so you should be set.
Usually both volume buttons power button for a few secs or through rom mgr
rozzko said:
Usually both volume buttons power button for a few secs or through rom mgr
Click to expand...
Click to collapse
From what I've read ROM Manager is a no-no on this model phone. I dunno why, but I've read that on a few threads.
Let me know if you're able to install Heimdall and the open source drivers that come with it. If you can, you can get into download mode, and it sees the phone, then you can try the One Clicks or even just flash the boot loaders from a ROM that contains them.
I will try when i go home tonight.
just an fyi every time i plug in my phone, it does not show up on my computer. i have tried using debugging mode and mass storage and neither work.
rozzko said:
I will try when i go home tonight.
just an fyi every time i plug in my phone, it does not show up on my computer. i have tried using debugging mode and mass storage and neither work.
Click to expand...
Click to collapse
Ugh...well let's hope for the best. I would uninstall any drivers and programs like Kies you have installed first, then install the Heimdall drivers. Let me know how it goes.
so i uninstalled drivers executed Heimdall and put phone in download mode with dongle. the computer still did not detect phone, however i got my replacement SGS4 today put it in download mode and it was detected immediately.
I dont know what else I can do do get the phone detected or fix the boot loader to get into recovery
rozzko said:
I will try when i go home tonight.
just an fyi every time i plug in my phone, it does not show up on my computer. i have tried using debugging mode and mass storage and neither work.
Click to expand...
Click to collapse
Maybe I'm missing something. How are you switching between debugging mode and mass media if you can't boot the phone?
The way I understood the problem, you would get to the SgS logo screen during boot, then the whole screen would be covered by the rainbow effect, which renders the screen unreadable, nd thus the phone unusable. Is that correct, or is the problem different?
the rainbow screen happens right after the SGS Logo then fades out once the lock screen comes on.
it also shows up once I try to get into recovery but from that point I cannot see anything and have to reboot.
Phone works after fully booted
both debugging and mass storage have been tried
You need to flash the "GINGERBREAD" bootloaders. This issue is 100% caused by froyo bootloaders. Once you obtain the GINGERBREAD bootloader, there is a 100% chance that the issue will go away. Flash THISTHIS/download. in heimdall. Get into recovery, then flash a rom of your choice.
I have a Samsung Infuse that I recently rooted and installed Serendipity on. I then attempted to load CM7, which caused some problems. Now the phone gets stuck on the Samsung logo and doesn't go any further; I can only load into CWM (Red), which can be "updated" to Green, after a hard reset. I've attempted to reflash the ROM from the SD card (even after wiping Dalvik cache, cache partition, and factory reset), but it just gets stuck on the Samsung logo.
My issue is further complicated by the fact that Download mode doesn't want to work - my phone can enter Download mode, but my computer (with Kies installed for the drivers) doesn't recognize the phone being connected. I've occasionally gotten Download mode to work if the battery is removed at just the right moment, but it doesn't last. Due to this, I can't get Odin to work.
Any ideas on what to do next?
kmv_007 said:
I have a Samsung Infuse that I recently rooted and installed Serendipity on. I then attempted to load CM7, which caused some problems. Now the phone gets stuck on the Samsung logo and doesn't go any further; I can only load into CWM (Red), which can be "updated" to Green, after a hard reset. I've attempted to reflash the ROM from the SD card (even after wiping Dalvik cache, cache partition, and factory reset), but it just gets stuck on the Samsung logo.
My issue is further complicated by the fact that Download mode doesn't want to work - my phone can enter Download mode, but my computer (with Kies installed for the drivers) doesn't recognize the phone being connected. I've occasionally gotten Download mode to work if the battery is removed at just the right moment, but it doesn't last. Due to this, I can't get Odin to work.
Any ideas on what to do next?
Click to expand...
Click to collapse
You have a soft brick.
Odin or heimdall back to stock.
There are about fifty threads previously posted on this topic.
Just read thru a few...
Gl
qkster said:
You have a soft brick.
Odin or heimdall back to stock.
There are about fifty threads previously posted on this topic.
Just read thru a few...
Gl
Click to expand...
Click to collapse
Thanks for the attempt, but as I said before Download mode isn't recognized by the computer, and that is an important component for Odin or heimdall to work.
I have occasionally gotten access to the SD card through CWM, so I can place ZIP files directly on the phone. If anyone has any ideas on what to flash from the phone, I'd love to hear it.
Thanks in advance!
kmv_007 said:
Thanks for the attempt, but as I said before Download mode isn't recognized by the computer, and that is an important component for Odin or heimdall to work.
I have occasionally gotten access to the SD card through CWM, so I can place ZIP files directly on the phone. If anyone has any ideas on what to flash from the phone, I'd love to hear it.
Thanks in advance!
Click to expand...
Click to collapse
Try it on another computer. I recommended Odin back to stock first before you start flashing!
Sent from my SGH-I997 using Tapatalk
Thanks, I'll give a different computer a try.
kmv_007 said:
Thanks, I'll give a different computer a try.
Click to expand...
Click to collapse
make sure you are trying to get into DL mode correctly...
pull battery, hold ONLY the volume buttonS - not the power button -;
insert battery, plug in cable.
if that doesnt work, use a different usb cable.
try different port on the computer
try a different computer or winxp or win7
it's kinda finicky at times.
Finally got it working - needed to use a different computer. Used my brother's laptop and it worked first try. Thanks for your guys' help.
I am in desperate need of help .. I am not a noob to flashing roms and rooting, however I have a one-off situation w/ no precedents to my knowledge. I have read these and other forums for days to no avail.
I was flashing Infintium Rom 4.0.4 from MIUI 2.3.6. I followed the steps listed in the post (http://forum.xda-developers.com/showthread.php?t=1661690). After flashing I rebooted and waited however the phone was/is stuck on the Samsung logo and never progressed. I then pulled the battery and attempted to go back to recovery mode to reflash make sure I did flashed correctly. However, upon going back into recovery I was greeted by the below image.
Clockwork Mod is extremely distorted and flat out unusable !! As I read further down it advised to use Heimdall (http://forum.xda-developers.com/showthread.php?t=1331381). I downloaded and attempted to use, however my PC (Which by the way is Windows 7 64-Bit) recognized the phone but the Heimdall software did not. I already had the right drivers for the PC and phone. After a few tries I deleted the files and reapplied them. On the 2nd menu after selecting list devices, on the drop down the option for Samsung USB Composite Device neeever ever appears. I also tried on a different PC that ddnt have the drivers and started brand new. Still, Heimdall ddnt recognize.
I also tried to flash numerous files including but not limited to GTG Ultimate Unbrick via Odin. Again, PC recognized USB connection however program ddnt. At this point, I do not know if it is because the status of Clockwork Mod on my phone, but I know it is not because of the drivers or the USB ports on my PC.
In addition to that, I have just scrapped the idea of flashing or getting in CWM and just wanted to do a hard reset (While phone is off held Vol down and Power, once started released power and contimued to hold Vol down. This should take the phone from the Samsung logo to an alt menu that will give the option to do a factory reset. But again w/ my luck .. that screen neeever appears.
In short I have tried at least 3 different ways and many maaany variations to get the phone back into recovery or into a full boot and had NO success.. Please help and ask as many questions as needed to diagnose and resolve this issue .. Thanx in advance and apologize in advance if posted in the wrong thread.
Are you placing your phone in download mode?
Remove battery and place it back.
Hold vol+ & vol- , and plug in the usb to your phone with the other end already connected to the PC.
Now see if Odin or heimdall recognize your device.
Sent from my sweet & buttery Infuse
andros11 said:
Are you placing your phone in download mode?
Remove battery and place it back.
Hold vol+ & vol- , and plug in the usb to your phone with the other end already connected to the PC.
Now see if Odin or heimdall recognize your device.
Sent from my sweet & buttery Infuse
Click to expand...
Click to collapse
I have done so neither Odin or Heimdall are recognizing it or showing the phone is connected.
ohsirus said:
I have done so neither Odin or Heimdall are recognizing it or showing the phone is connected.
Click to expand...
Click to collapse
If neither Odin or Hemdall can 'see' the phone, then possibly you don't have the correct drivers installed...
Try downloading and installing these:
http://d-h.st/sKF
Then open Odin/Hemdall and plug your phone in again while in Download Mode.
Ryo Misaki said:
If neither Odin or Hemdall can 'see' the phone, then possibly you don't have the correct drivers installed...
Try downloading and installing these:
Then open Odin/Hemdall and plug your phone in again while in Download Mode.
Click to expand...
Click to collapse
I will try again .. Downloaded, rebooting then will go thru the process again .. standby
Ryo Misaki said:
If neither Odin or Hemdall can 'see' the phone, then possibly you don't have the correct drivers installed...
Try downloading and installing these:
Then open Odin/Hemdall and plug your phone in again while in Download Mode.
Click to expand...
Click to collapse
no change .. still shows disconnected
The pic u have posted it shows u need to press the up button to get the download mode (continue)
Sent from my Galaxy Nexus using Tapatalk 2
rkkaranrk said:
The pic u have posted it shows u need to press the up button to get the download mode (continue)
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I just did that to post a pic as an example .. I did go to download mode and not recognizing it
The CWM screen is shot because you don't have gingerbread bootloaders, it will always look like that until to can flash the right ones..
Have you tried different cables, different ports, etc?
Sometimes mine would recognize.. sometimes being plugged in first then running Odin works, sometimes I would have to run Odin and then plug in the phone.. kinda a crapshoot...
Its powered by Jellybeaned AOKP!
drnecropolis said:
The CWM screen is shot because you don't have gingerbread bootloaders, it will always look like that until to can flash the right ones..
Have you tried different cables, different ports, etc?
Sometimes mine would recognize.. sometimes being plugged in first then running Odin works, sometimes I would have to run Odin and then plug in the phone.. kinda a crapshoot...
Its powered by Jellybeaned AOKP!
Click to expand...
Click to collapse
I know I need to get the bootloader and a kernel on it however I cant = ( .. yet .. I have 4 different ports on my PC and have tried them all. i have tried phone on then run programs and programs on 1st then phone on and no new results.
I found this short video and it describes my exact situation .. please watch to futher understand http://www.youtube.com/watch?v=OHLUYckTlug
So u have odin and heimdal both on the same PC and drivers for them if yes then try this.
On the PC/Laptop uninstall all the drivers for samsung or any other phone and follow this.
Go to accessories> system tool> system restore and check the restore point where the drivers for heimdall were installed restore to a previous restore point after restore finishes install the drivers for Infuse and see now Odin recognizes ur phone, It should.
I had the same exact problem, do you have another phone on which you can install the same CWM recovery on? ...Because the clockwork mod recovery still works, it's just that you can't see it. So just flash a new ROM, by going back n forth between phones, clock how many clicks it takes to get to 'choose zip to install' then 'download' on the not messed up phone, then do the same on the screwy one, just keep doing that till u flash the new ROM.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
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.