Database Info

[Q] possibily bricked - bootloader broken

Hy to all,
my Nexus S one day decide to not power on at all!
SYMPTOMS:
- black screen
- power button doesn't do anything (also phone not vibrate)
- no button combination boots to download mode
- no charghing indication when connected to charger or USB
- no detection in the computer when connected to the USB
After some days without battery, the problem persists:
NEW SYMPTOMS:
- when plugged on computer usb port, Windows 7 start to find Sec S5pc110 Test B/D driver
In a formum of Bada (I now is not my phone) Samsung support tells that can be the bootloader broken!!
Someone can help me to solve my problem!
Thenks in advance, and sorry for my bad english
PS: my problem is similar to the one described in this thread http://forum.xda-developers.com/showthread.php?t=882189

Well, did you do anything to it before this started? Anything like flash some new rom, or the OTA or similar?
There was another dude a few days ago who reported his phone was bricked and described similar symptoms to yours, but it turned out his issue was just a totally discharged battery that wouldn't start taking a charge until he forced it with some homemade 9-volt battery thing. You might try a different battery if you can obtain one.
The only other thing, besides warranty repair, might be to get the 301k resistor jig and use Odin to flash a new bootloader image to the phone, per this thread: http://forum.xda-developers.com/showthread.php?t=947950

Mate,
have you had any progress in unbricking your phone. I too am in the sam state with my Nexus S... unfortunately I can get this phone back to USA & when I spoke to the Samsung helpline the crooks simply refused to help since the instrument is outside of USA.

I'm in the same situation - did you get anywhere with yours ?

[Q] Bricked? Or just battery acting up?

Hi guys
I've had the Sensation for about 3months now, and suddently yesterday it stopped working. It wont charge, no LED's and wont start at all. There have not been any waterdamage, drops or rough use.
I've read a lot concerning similar problems on this forum, but none of the solutions has worked for me.
What I can tell is that I have tried after searching the forums:
- SDK, ADB and try to reboot the device via USB-connection (device not found)
- Win7 (32bit) can't recognise the phone (asking for drivers which are not found in HTC Sync, QHSUSB_DLOAD)
- Trying to enter recovery mode (Volume Down + Power up)
- Charge the battery overnight
- Charge the battery with a plastic-piece covering the two middle pins on the battery (As suggested in a thread)
- Battery out for 1min and then put it back in and start up
Neither of these worked, so are there any other good ideas? Or is it bricked?

Hi guys,
i have exactly the same problem, already have tried all of these solutions, nothing have worked for me... Please help.
PS:sometimes my screen lights up <black totally, but lights up>... when plugged into usb cable or charger... but not now anymore...
I have bought this phone in china, there is S/N but i guess that here in UK i cannot do anything about it since HTC's warranty is not global...

listenger said:
Hi guys
I've had the Sensation for about 3months now, and suddently yesterday it stopped working. It wont charge, no LED's and wont start at all. There have not been any waterdamage, drops or rough use.
I've read a lot concerning similar problems on this forum, but none of the solutions has worked for me.
What I can tell is that I have tried after searching the forums:
- SDK, ADB and try to reboot the device via USB-connection (device not found)
- Win7 (32bit) can't recognise the phone (asking for drivers which are not found in HTC Sync, QHSUSB_DLOAD)
- Trying to enter recovery mode (Volume Down + Power up)
- Charge the battery overnight
- Charge the battery with a plastic-piece covering the two middle pins on the battery (As suggested in a thread)
- Battery out for 1min and then put it back in and start up
Neither of these worked, so are there any other good ideas? Or is it bricked?
Click to expand...
Click to collapse
Have you tried a different battery?

I just ordered a new battery... Takes a couple of days before I recieve it

listenger said:
I just ordered a new battery... Takes a couple of days before I recieve it
Click to expand...
Click to collapse
Also keep note of which recovery you are working off of. There have been charging issues with certain recoveries.

Yeah, I read several threads and posts about recovery-issues... Unfortuantly I cant check what version I got myself, as it wont start up at all :/

listenger said:
Yeah, I read several threads and posts about recovery-issues... Unfortuantly I cant check what version I got myself, as it wont start up at all :/
Click to expand...
Click to collapse
I would suggest to go to a store that sell's the Sensation and ask if you can test one of their batteries out to see if your phone has either a battery issue or something else. If you are stateside, of course try a tmobile store, but without knowing where you are located, this is a hypothetical at this point.
I know I had an issue with my Nexus1 not booting up from a kernel I had flashed. But I noticed my charging led was flashing three times and then stop. I researched this here on xda and found that it just needed to be put into recovery again somehow. I ended up just plugging the phone into the wall and remove the battery. Try to power it on there and then reinsert the battery and try the power + volume down button. That time it booted for me. But again, this was for my Nexus1 not with this phone.

same happened to me, sent to HTC and had main board replaced, lcd, flex cable etc. the driver the phone looks for is the equip HTC use to jtag... I am not sure if this is a hardware failure or boot corruption...but even though it was s-off via alpha rev it was that damaged they didnt complain... i say hardware failure. the thing is even when i have s-off i didnt change the rom. I have a riff box on order so if this happens again we can surely see if this failure is software or hardware..

Yeah, do what kpjimmy said; go to a store where Sensation's are sold and ask if you could use a battery to test it out to see if it's bricked. It it's not, you'll need a new battery (try getting one for free from HTC, citing warranty. I did it with my battery cover). If it doesn't work, you're mostly likely bricked, unfortunately. Refer to anarchy's post for more info on that side of things

Same problem here yesterday.. can't charge. But phone heat. I just pull out battery, n put back.keep repeated that. Finally can on. U use custom kernal?

arifafzan said:
Same problem here yesterday.. can't charge. But phone heat. I just pull out battery, n put back.keep repeated that. Finally can on. U use custom kernal?
Click to expand...
Click to collapse
Havn't had the time to really do any custom ROM or the like, so the phone was all original from the factory...

[Q] About to buy a bricked Xoom, anything I should know?

As the title says.
Thinking of getting this device on the cheap. I have a Moto factory cable that i've used to flash stock firmware onto a couple different devices.
Would that same cable work on this device to get it into fastboot?
Are there any cases of completely hard bricked devices?
Also, if any of you experts know some questions i might want to ask the guy, I'm all ears! Thanks!

Markyzz said:
As the title says.
Thinking of getting this device on the cheap. I have a Moto factory cable that i've used to flash stock firmware onto a couple different devices.
Would that same cable work on this device to get it into fastboot?
Are there any cases of complete hard bricked devices?
Also, if any of you experts know some questions i might want to ask the guy, I'm all ears! Thanks!
Click to expand...
Click to collapse
You can use the moto factory cable on the xoom but that just gives it power to fastboot.
You can have a xoom be hard bricked. If you plug it in and it shows up as a APX device it is hard bricked. (i own one that's sits in the drawer for spare parts for it's replacement) The charge light will still come on.
What type of xoom is it a (wifi 3g/4g family edition)
You should ask what caused it to brick?
was he rooted?
If you buy it post here and I can give a one click restore for it. AI have it for most versions of the xoom.

Be Sure...
Before you buy it I would recommend getting as much information as possible from the seller as this device may be beyond repair. If the device can still be recognized in fast boot then you should be fine.

if it is a 3g/4g xoom you might want to get the esn/meid number and check with verizon if it is clean.

If the bootloader is damaged it is of no use other than spare parts. You must at the very least be able to get to fast boot. If it is not recognised when plugged into the USB there is nothing to be done without serious hardware hacking.
I have one just like that in a box. It is rare, but it happens. It will not even flicker when powered up - nothing.

Grege50 said:
If the bootloader is damaged it is of no use other than spare parts. You must at the very least be able to get to fast boot. If it is not recognised when plugged into the USB there is nothing to be done without serious hardware hacking.
I have one just like that in a box. It is rare, but it happens. It will not even flicker when powered up - nothing.
Click to expand...
Click to collapse
This morning while loading a webpage (20% of battery life left) my MZ601 just froze, didn't respond to any screen or button presses, slowly went to sleep and has resisted all attempts to start since then. Even hooked up to the charger for the last hour, it still doesn't respond no matter what buttons I press, completely blank, no lights, nada...
I'm guessing it's a dead parrot, has anyone else had a similar Xoom death?
EDIT: Just found a more appropriate thread, ignore...

Zenfone 6 stays black after EDL Mode

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.

Bricked my OnePlus 8 beyond anything ive done before

So, i've been flashing custom ROMS on my android phones for many many years. Never really screwed up... Except now. Let me explain;
I was going to flash LineageOS on my OnePlus 8 phone. Nothing I haven't done before. I follow the guide as the maintainer described (for your reference, https://wiki.lineageos.org/devices/instantnoodlep/install).
Towards the end of the process when I got to Installing LineageOS from recovery I'm asked to format data. Here something went horribly wrong. As the process of formatting finished. All that's left to do is reboot. And so I reboot. This was the last time I ever got any sign of life from my phone. Because after shutting down, it never started back up. No sign of life at all. No fastboot, no adb, not even a splash screen. I've tried to boot it with any combination of keys. But no matter which one (reset, boot to recovery, even boot to EDL). nothing. Not even a buzz or a battery indicator when I plug it into the charger either. Bricked beyond anything I've ever seen.
In the 3 days since it happened I've:
- Charged my phone for 20+ hours
- attempted rescue using fastboot/ adb
- followed the steps from about every comment in this thread: https://forum.xda-developers.com/t/cannot-unbrick-cannot-enter-edl-mode.4148589/ (on USB3 and USB2, with the oneplus official cable and 3rd party cables)
- followed the steps this friendly youtuber explained:
- pressed any button and any combination of buttons on my phone for at least multiple minutes
- screamed at the phone really loud
Obviously none of these steps did the trick. My computer (I tried 3 computers actually, and both in Windows and Linux) just does not recognize the phone anymore. Nothing in device manager. Not even when i'm attempting to EDL.
Quite honestly I'm just stumped. It's not even recognized by device manager. If I didn't know any better I'd suspect the hardware itself failed at the exact same time as the software. I hope any of you can help me out.

One option you can try is getting an EDL cable.

Xryphon said:
One option you can try is getting an EDL cable.
Click to expand...
Click to collapse
Hi Xryphon,
That's interesting actually. I didn't know there were specialized cables for this. I was just using regular USB C. I'll look into getting one.