Related
So I'm stumped... I've flashed my Charge many times, no problems until now.
I wanted to flash back to stock ROM and had my Samsung drivers installed and Odin recognizing the phone and everything was good, but then Odin was taking WAAAAAAY too long. In the past this usually took about 20 mins. This time, after 45 mins and the progress bar hanging in the same place for 30+ mins on factory.rfs I disconnected the phone (I know this is where I screwed up). Now Odin won't recognize the phone at all. It does get into download mode, but Odin won't pick it up.
Same computer, same cable, and same USB ports as I've had when flashing this phone many times before. I don't know what my options are now. I don't think I can flash either the ROM or PIT without Odin at least recognizing the phone. What can I do now?
So I've done some more tinkering - trying different cords, multiple computers, uninstall/reinstall different drivers... What I've noticed on more than one computer is that Odin doesn't recognize the phone when it's in download mode ONLY.
If I power on the phone Odin is able to detect it and windows detects it as a Samsung USB device (even though the phone hangs on the Samsung logo). When I put it into download mode both the computer and Odin don't recognize it.
dragonlady726 said:
So I've done some more tinkering - trying different cords, multiple computers, uninstall/reinstall different drivers... What I've noticed on more than one computer is that Odin doesn't recognize the phone when it's in download mode ONLY.
If I power on the phone Odin is able to detect it and windows detects it as a Samsung USB device (even though the phone hangs on the Samsung logo). When I put it into download mode both the computer and Odin don't recognize it.
Click to expand...
Click to collapse
FWIW, I've also noticed a simple computer reboot fixes it....
jco23 said:
FWIW, I've also noticed a simple computer reboot fixes it....
Click to expand...
Click to collapse
I neglected to mention in my OP that I was going through the right protocol with driver uninstall/reinstall and rebooting each time. I rebooted again for good measure after seeing your post but I still get the same.
It's the same result from two different computers, one with Win7 and the other XP (I read in another thread that XP had worked better for some). If the phone is powered on, even though it doesn't successfully boot, Odin and Windows recognize it properly. If it's in download mode neither one recognize it, windows says the device failed to start and shows either unrecognized device or "Gadget Serial" (which would be a great name for a band, but google searches for it aren't much help).
I don't think it's a driver problem because it's recognized when the phone is powered on. But could there be a specific driver out there for the phone when in download mode only? I've flashed this phone dozens of times and never had a problem until now. I'm on the verge of forking over the $50 and sending it to JTAG if no one can suggest something else to try. Please help
did you make sure your phone is in debugging mode?... i forget who flashed what... or where I read something about flashing and it turned off their debugging mode...so check that first...and try reinstalling Odin on your computer... i don't think jtag is necessary on a Droid charge... if your phone is being recognized then it seems your missing a step...like maybe pulling your battery before hooking up the usb... or reinstalling the battery after going in download mode... and last of all check and make sure your not accidentally making mistakes when setting up your Odin before flashing... and last efforts to get a working phone would be going into cwm... volume up... home... and power button... hold while powering up and releasing on the second Samsung logo...and install your last back up...or reflash your rom with cache and dalvik wipes
Sent from my SCH-I510 using xda premium
curious, when you are/were performing the Odin process, were you still using the computer (web-surfing, e-mail, etc.)? in my experience, whenever I tried to multi-task on my computer while running Odin on my phone, Odin freezes. this has happened on more than one occasion. also, my toddler daughter even pressed the power button while Odin was running - so on three separate occasions, I've had a reflash interrupted. however, I've clearly been able to recover.
the key was using the right cord in the right port. I had one cord working fine for awhile, but then when I switched cords, it worked again.
also, some folks have had better success when removing the battery during the process.
finally, what are your steps exactly when flashing - and which guide are you using?
lukegman said:
did you make sure your phone is in debugging mode?... i forget who flashed what... or where I read something about flashing and it turned off their debugging mode...so check that first...and try reinstalling Odin on your computer... i don't think jtag is necessary on a Droid charge... if your phone is being recognized then it seems your missing a step...like maybe pulling your battery before hooking up the usb... or reinstalling the battery after going in download mode... and last of all check and make sure your not accidentally making mistakes when setting up your Odin before flashing... and last efforts to get a working phone would be going into cwm... volume up... home... and power button... hold while powering up and releasing on the second Samsung logo...and install your last back up...or reflash your rom with cache and dalvik wipes
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
I can't actually get the phone to boot (doesn't get past Samsung logo) so I don't know how I can tell if it's in debugging mode or how to change it if it's not.
Going in to download mode I've tried both battery in and out, using multiple USB ports and cables and can't get any version of Odin to detect it. I've tried v1.82 and 1.85 of Odin. I get the same result for both - Odin does not detect the phone when in download mode, but will detect it if it's powered on or just connected to the computer with battery in to "charge." But afaik I can't flash it when it's NOT in download mode
It won't boot into into recovery either... It never gets past Samsung logo no matter how long I hold the buttons... I've used recovery before, so I'm sure I'm giving the android 3-finger salute correctly.
I'm thinking maybe I got unlucky because the whole key to flashing is having Odin recognize the phone in download mode and that's the only time that Odin won't recognize it.
jco23 said:
curious, when you are/were performing the Odin process, were you still using the computer (web-surfing, e-mail, etc.)? in my experience, whenever I tried to multi-task on my computer while running Odin on my phone, Odin freezes. this has happened on more than one occasion. also, my toddler daughter even pressed the power button while Odin was running - so on three separate occasions, I've had a reflash interrupted. however, I've clearly been able to recover.
the key was using the right cord in the right port. I had one cord working fine for awhile, but then when I switched cords, it worked again.
also, some folks have had better success when removing the battery during the process.
finally, what are your steps exactly when flashing - and which guide are you using?
Click to expand...
Click to collapse
I wasn't actively multitasking during the bad flash, although I may have had email running in the background. Since then I've been rebooting and only had Odin running in the foreground when trying. I did use multiple usb ports/cables and try going into download with battery in/out.
As far as guides go, I had been using trparky's awesome guide for years until he took it down and lately went to the one in the dev forum here on xda: http://forum.xda-developers.com/showthread.php?t=1160580
Like I said, I'm thinking maybe I got unlucky because Odin recognizes the phone when plugged into the computer EXCEPT when it's in download mode and without that I don't know what else to do.
dragonlady726 said:
I can't actually get the phone to boot (doesn't get past Samsung logo) so I don't know how I can tell if it's in debugging mode or how to change it if it's not.
Going in to download mode I've tried both battery in and out, using multiple USB ports and cables and can't get any version of Odin to detect it. I've tried v1.82 and 1.85 of Odin. I get the same result for both - Odin does not detect the phone when in download mode, but will detect it if it's powered on or just connected to the computer with battery in to "charge." But afaik I can't flash it when it's NOT in download mode
It won't boot into into recovery either... It never gets past Samsung logo no matter how long I hold the buttons... I've used recovery before, so I'm sure I'm giving the android 3-finger salute correctly.
I'm thinking maybe I got unlucky because the whole key to flashing is having Odin recognize the phone in download mode and that's the only time that Odin won't recognize it.
I wasn't actively multitasking during the bad flash, although I may have had email running in the background. Since then I've been rebooting and only had Odin running in the foreground when trying. I did use multiple usb ports/cables and try going into download with battery in/out.
As far as guides go, I had been using trparky's awesome guide for years until he took it down and lately went to the one in the dev forum here on xda: http://forum.xda-developers.com/showthread.php?t=1160580
Like I said, I'm thinking maybe I got unlucky because Odin recognizes the phone when plugged into the computer EXCEPT when it's in download mode and without that I don't know what else to do.
Click to expand...
Click to collapse
Also, are you sure you have enough battery juice? To make sure, leave it plugged in to a wall outlet for about 30 min to an hour.
tappin' that....
Finally fixed - Bad USB port
Just to close out the thread, I did finally get my phone fixed. The issue was a bad USB port that decided to fail during flash. This is according to Josh from MobileTechVideos, who is a great guy with amazing customer service.
Longer version: I sent it off to MobileTechVideos/JTAG and after a week I got a call back saying the JTAG process didn't work and as a last resort they could try replacing the USB port itself. Josh told me that it was either the port or the controller, that the port was a known failure point on the Charge, and if replacing the port didn't work it meant the USB controller had failed and I'd be out of luck. He also said that if the port replacement didn't fix the issue he wouldn't charge me and refund my original payment (which impressed the hell out of me given the time he had already put into it and there was no guarantee that the extra work would fix it). This was late afternoon on Valentine's Day... he said that he'd get to swapping out the port the next day but an hour later called back to tell me that he replaced the port and flash was successful. I wish everyone was as straightforward in communication and dedicated to their job.
So yeah, MobileTechVideos is legit, Josh is a rock star, and send those guys your phone if something really screwy happens. They will take the time and go above and beyond if necessary to fix it, and you will absolutely get your money's worth.
Hoping that no one else is "lucky" enough to have their USB port fail mid-flash, but if your symptoms look like mine a bad port might be your problem.
I've heard nothing but good things about them. I've never used them myself, but I have directed a couple of people to them and heard nothing but glowing reviews.
Cool I managed to finally back up my sd card after a few attempts with a bad port (went out after a month of having the phone). I've been on a rotating batteries off a wall charger system, but need to odin because everytime I get down to 110-120 ish mb of internal memory my charge says low memory blah blah, I clear cache, play store , etc.
Needless to say people have said resorting back to stock ep4 etc with Odin should work, but I'm afraid mid flash something will happen. I have to jam the cord in, wrap extremenly tight while holding the phone at a perfect angle and sometimes it still will beep like being disconnected.
I have no idea if this would be possible for you, but I wonder if Mobile Odin could help you?
Youve probably all dealt with similar multiple times. but a little help here would be great.
i was installing some updates on my wifes phone and it crashed. it will now not turn on or charge. ive tried a battery pull, ive tried loading the bootloader (power and volume down). i plugged the phone into my computer with HTC sync manager. it didnt recognise the phone, but my computer did install a qualcomm snapdragon driver. so the phone is sort of being recognised by my system.
can anyone help, id rather not send it off for repair and have it factory reset then hope that i can recover things through recovery programs.
cheers all
I think you need to be more specific related to:
- what you have done with your phone
- your phone version (there are 4 different versions out of this phone)
topha.cmd said:
Youve probably all dealt with similar multiple times. but a little help here would be great.
i was installing some updates on my wifes phone and it crashed. it will now not turn on or charge. ive tried a battery pull, ive tried loading the bootloader (power and volume down). i plugged the phone into my computer with HTC sync manager. it didnt recognise the phone, but my computer did install a qualcomm snapdragon driver. so the phone is sort of being recognised by my system.
can anyone help, id rather not send it off for repair and have it factory reset then hope that i can recover things through recovery programs.
cheers all
Click to expand...
Click to collapse
Same thing happened to me 5 WEEKS AFTER BUYING IT! Sat on my microwave til the end of august before I thought to try an external battery charger. It worked and I'm using it again! It still happens a lot so I have to keep that charger handy [emoji36]
Sent from my HTC One SV
ok so im working on a nexus 5. i was already all too aware of the potential power button issue so that was the 1st thing i checked out, ive cleaned it twice now and made dbl damn sure i can feel it both click in and click out when being pressed.
on top of that i can boot into twrp both temp boot and flashing recovery for it. it does not cut off when in twrp (as i imagine it would if it were the power button being stuck)
previously i could not boot into twrp or flash anything at all so i ordered and installed a breand new battery.. now i can flash twrp via fastboot (progress right?)
however when it is powered off, on teh charger it shows the battery full with lightening bolt, then that fades and is replaced with a hollow battery being filled, then goes black and starts over... leading me to believe its not taking any charge in..
ive tried stock 7.1.1, stock 7.0.1, stock 6.0.1, cyanogenmod 14 and even ran the NRT by Wugs... i have wiped everything, i formatted data and made sure the partition was correct pre-flashing by running NRT to return stock values n such, i have also tried different approachs to flashing. fastboot flash system, adb sideload, twrp install zip and NRT...
with my small (yet excessive) experience so far with android im led to believe this is being caused by some sort of conflict inside the system memory, it almost has a rythym to when it cuts off, like when it hits block such n such it goes "OUCH DAMMIT" and retreats for safety (powering off)
you'll have to forgive me for starting a new thread, the only info i can find pertains to the power button which i am fairly confident it is NOT, and after hours of searching tonight alone im really not for diffing thru every thread, i did however do a quick search prior to posting....
Where did you get the battery? Tried different USB cables and chargers? The phone boots and runs properly on stock?
I had a similar problem. I talked to LG customer support and they were aware of this issue and suggested that the whole logic board needs to be replaced. Apparently this is common with LG devices.
A workaround that worked for me is to turn off the phone for 1 day (let it cool down), clean flash whatever rom you like, then flash ElementalX kernel with the CPU under-clocked to minimum.
I have tried various ports and cords, battery from a top seller on ebay (checked reviews prior) and I cannot boot into stock Android either... During my extensive tweaking of the device last night I relocked the bootloader while returning to complete stock... After doing such I later tried some thing I saw suggested on the forums, removal of the power button.. so I desoldered it.. didn't change anything so it's def not the button... However now I cannot click the screen to confirm unlocking the BL again so I'm close to boned as far as flashing options ATM... Lol fail...
If it is a motherboard problem, and it sounds like it is, the cheapest solution may be to buy a used Nexus 5 with smashed screen and working motherboard. Swapping the motherboards is quite simple.
That's probably gonna happen, I don't see many other viable options .... It's not my phone so imma be putting money into someone else's to save face. U don't get a broke device back from me
Thanks guys
Okay, this one seems slightly different, so anyone who has had the problem and found a solution, I'm all ears. While reflashing the second Q beta (over the second Q beta - I was getting Play Services FCs and rebooting didn't fix it) everything went fine until the command window closed and the phone stayed in the bootloader. After that the PC didn't recognize anything being plugged in or our, it's stuck on slot b, which is unbootable, I can't change it and I can't boot from it, because I can't talk to it. I've removed and replaced the driver, I'm using a USB 2.1 connection, the computer recognizes other phones on that cable, I've used the same combination to flash factory versions and sideload updates all year using exactly the same thing, so ...
Google recommended an RMA, so they did, and Fedex has it on the truck today for delivery but ... has anyone found a way to get this to work without changing the motherboard? (I've treated this battery well, and the phone's been a case since day 1 - who knows what I'm getting.)
Rukbat said:
Okay, this one seems slightly different, so anyone who has had the problem and found a solution, I'm all ears. While reflashing the second Q beta (over the second Q beta - I was getting Play Services FCs and rebooting didn't fix it) everything went fine until the command window closed and the phone stayed in the bootloader. After that the PC didn't recognize anything being plugged in or our, it's stuck on slot b, which is unbootable, I can't change it and I can't boot from it, because I can't talk to it. I've removed and replaced the driver, I'm using a USB 2.1 connection, the computer recognizes other phones on that cable, I've used the same combination to flash factory versions and sideload updates all year using exactly the same thing, so ...
Google recommended an RMA, so they did, and Fedex has it on the truck today for delivery but ... has anyone found a way to get this to work without changing the motherboard? (I've treated this battery well, and the phone's been a case since day 1 - who knows what I'm getting.)
Click to expand...
Click to collapse
I would try skipsoft Android toolkit. It might not recognize your phone right off. Try uninstalling and reinstalling USB drivers through the toolkit with phone plugged in. Downloading and installing firmware, etc. It got me out of a bind once. Worth a try.
Hi, I got to this "not bootlable" situation for second time when I was downgrading from Q beta 2 back to Pie. But I am probably lucky one Same situation like you, only bootloader screen and PC didn't see my phone, but I was able to fix it I was in bootloader, connected to PC and I hold power button for long time (2 minutes maybe more). Phone was still restarting, bootlader screen, black screen, bootlader, black.....sometimes it vibrated. After this 2 minutes I just tried "flash-all.bat" command and phone arose from the dead and is working.
somin.n said:
Hi, I got to this "not bootlable" situation for second time when I was downgrading from Q beta 2 back to Pie. But I am probably lucky one Same situation like you, only bootloader screen and PC didn't see my phone, but I was able to fix it I was in bootloader, connected to PC and I hold power button for long time (2 minutes maybe more). Phone was still restarting, bootlader screen, black screen, bootlader, black.....sometimes it vibrated. After this 2 minutes I just tried "flash-all.bat" command and phone arose from the dead and is working.
Click to expand...
Click to collapse
This should work. Had something similar happen to me, keep holding power for about 10 seconds or so while it keeps rebooting until you feel the phone vibrate. Release the power button, connect to the computer and it should detect it then.
https://forum.xda-developers.com/showpost.php?p=78744315&postcount=31
somin.n, I just wanted to thank you for rescuing my phone. After a lot of problems with Q, I decided to go back to Pie and bricked the bootloader. I tried your trick and it came back - but ... I flashed Pie, it rebooted and hung on the "G" screen. So I did a factory reset and resigned myself to use the refurb they sent me. This morning I tried once more and flashed Pie. Voila! The phone works. The original, non-refurb, phone. So now, since the refurb they sent me has the "bootloader unlockable flag = '1', but the bootloader won't unlock" problem, which seems to be common, there's another refurb on its way. So on Tuesday, I'm returning two refurbs to Google.
But you saved my phone so, again, thank you.
Rukbat said:
somin.n, I just wanted to thank you for rescuing my phone...
Click to expand...
Click to collapse
Hey, you are welcome I was really lost when it happened to me, because google is not selling phones in our country officialy, so no RMA and secondly, my pixel is my bussiness phone so I can't tell to my boss that my phone is broken because of flashing beta builds Yeah, I had to find a solution
Hi!
TL,DR:
Phone froze while using, and it kept freezing. Now phone wont boot at all, only EDL Mode works. However, after EDL phone wont still boot.
Longer story:
I've got quite a problem here. I was playing Pokemon GO with my friend yesterday. Suddenly my phone went quiet. I saw PoGo froze for 5 seconds and then phone rebooted itself. It went back to LineageOS (17.1) which I've installed successfully via TWRP. Then the phone rebooted itself again many times again and again, and each time it crashed earlier than before. When LineageOS did fail for booting for several times, the phone went straight to bootloader. I tried to open recovery but it crashed too. Then It came back to bootloader and I said Power Off.
I waited for half an hour but the phone was failing boot. It wen't even worse: the phone wont go to bootloader any longer, it just stays black.
I've done an EDL Mode recovery couple of times before when I was messing around my first custom ROM installation with Lineage. Now when I set the phone to EDL Mode via cable I made (it was an easy task) I can hear Windows detecting my phone (which it didn't detect before) and uses the QDLoader 9008 EDL Driver.
Then I use the "update_image_EDL.bat" to regenerate the partitions.
Now here's the tricky part: After the .bat file the phone should reboot to bootloader, however this doesn't happen, and the phone just exits ELD mode (I can hear it from Windows it doesn't detect the phone anymore) and then just stays black. It doesn't react to any buttons or cables, and Im also sure it has battery. I even opened the case and removed the battery from its port and putting it back to see if the phone reacts then my actions, but no.
It feels like the only thing I can do here is the ELD mode. I tried it several times later, and that's all.
Also trying to continue with the instructions with QDLoader 9008 fix (the flashall_AFT.cmd) won't lead anywhere, because Windows doesn't detect the phone after that.
Thank you in advance for any tips and tricks.
Edit: Just to add; I've tried removing SDcard and SIM cards also. No effect.
Edit2: Here's the copy of the 'update_install_EDL.bat' results: https: //paste.ofcode.org/bPLQA6T484rKEEb2URa8yv
After more failed tries and thinking, my friend was looking at my log from update_install_EDL.bat he was thinking about the warning it gave. Well, I went looking for the sector limit which was put by rawprogram4.xml and I added the missing sector to the count. Now the error is missing from log but it went nowhere in the progress however. I've done the .bat now many times, but nothing seems to be working. I've removed the battery and put it back before edl and after edl and tried booting with just the powerbutton and with the Vol+ and power btn, but nothing comes up.
If you got a log from the update_install_EDL.bat, I'd appreciate if you could post it somewhere for me to see did you get the same warning as I did.
I also want to point out that ANY comment is welcome... I keep you posted whenever theres some progress.
Okay. I decided to take my Zenfone 6 to Asus authorized repair shop. They said I've got short circuit in the motherboard. God knows how that happened. However I can't get it under the warranty because earlier I repaired my broken screen glass in a unauthorized repair shop. which has voided the warranty. Asus told me that the repair would cost me 527,2 EUR (624,30 USD). I'll not be paying that much for a repair, so it looks like Im out of the business..
I also want to note that I purchased the phone 4.6.2020 and it was in the screen repair for 30 days. So with my quick calculations I paid totally 12 eur for each day I had a chance to use it.
Edit: I want to say here that the repair shop takes 60€ (71 USD) for their excellent service. Okay, I admit that they we're quick on the result, for about 30 hours they responded, but ofc I'd like to have more info but they told the phone must be taken to the ASUS factory then.
Hey bud stumbled upon the post somehow!
What was your error code with the EDL script? (Link that you had shared expired :/) was if shahara error? I'm not so experienced but combining the infos that I've read across the forum maybe try charging the phone for 8+ hrs and try again. Also try diff cable, the one that came with the phone. There are two contact points at the back with which you can force EDL mode as said here. Also the firmware folder should be kept in the main drive (C:// or D) and named without spaces just alpha numerics. Lots of people seems to be getting the same Sahara error damn. Let us know any of these got it fixed! Cheers
Honestly it seems like whoever ASUS sourced to make the main motherboards did a rubbish job with all the failures. My wifes bog standard firmware just died 16 days out of warranty.
ASUS should either offer extended warranty and free motherboard replacements or conduct a voluntary recall to fix them.
I didn't spend a grand to use a phone for 12 months.
abx12 said:
Hey bud stumbled upon the post somehow!
What was your error code with the EDL script? (Link that you had shared expired :/) was if shahara error? I'm not so experienced but combining the infos that I've read across the forum maybe try charging the phone for 8+ hrs and try again. Also try diff cable, the one that came with the phone. There are two contact points at the back with which you can force EDL mode as said here. Also the firmware folder should be kept in the main drive (C:// or D) and named without spaces just alpha numerics. Lots of people seems to be getting the same Sahara error damn. Let us know any of these got it fixed! Cheers
Click to expand...
Click to collapse
Yeah Im sorry for the log. The warning on there was basicly telling that the bios.img is larger by one sector than the sector size given to the update_install_edl.bat. It was fixed by adding the one sector to the rawprogram4.xml file.
I was aware of the sahara fail, it was fixed by unplugging the cable and back in (restarting the edl mode ofc). And I also tried another cable.
What comes to the directory (folder) names I was aware of that too, the script don't do a very good job with folders having spaces or special letters.
homerlovesbeer said:
Honestly it seems like whoever ASUS sourced to make the main motherboards did a rubbish job with all the failures. My wifes bog standard firmware just died 16 days out of warranty.
ASUS should either offer extended warranty and free motherboard replacements or conduct a voluntary recall to fix them.
I didn't spend a grand to use a phone for 12 months.
Click to expand...
Click to collapse
My working theory is that this high failure rate is affecting all of series so they have no way to determine which units should be fixed/replaced. It's very sketchy but they've put themselves into this situation with poor QC in the first place.