Database Info

How I bricked my 8125

At The Beginning
I have a Cingular 8125 G3. I first began flashing new roms onto my phone 4 months ago after I unlocked it using "the definitive guide to unlocking phone" by DrDot. Everything went smoothly.
The Start of the Problem
A couple days ago, I was running the TNT 1933 with CoolCamera. SUDDENLY, my phone started to reset itself everytime I went on the internet, or downloaded emails.
The Attempted Fix
I decided to flash my phone to another rom, so I began by flashing it back to 1.05 rom that you use in "the definitive guide to unlocking phone" by DrDot, before flashing it to a better rom.
The Final Finally
In the middle of the udate process (for the 1.05 rom), my computer screen said, an error occured, and to redo the update. When I looked at my phone, it started to blink on the 3 color bars. It kept blinking until it died. Now it cannot read a charge or turn on. I tried leaving it on my charger overnight, hoping it would charge, and nothing (not even the charge light on the phone would go on. I also made sure the phone charger was fine, which it is. I even tried to charge it on the usb cable, and occassionally I see the 3 color bars flash). My phone is bricked.

buy a new battery and then flash a new rom

It is not bricked

I will try that
spencepu3 said:
buy a new battery and then flash a new rom
Click to expand...
Click to collapse
Okay, I'll try that. I'll let you know tonight.

keep in mind that when you are in bootloader mode (tri-color screen) the phone cannot be charged, this is why you should always have a 50% battery level when you flash a rom. A new battery should definately fix it, id flash it with a manufacturers rom that is known to work like the wizard love or t mobile 2.26

Everything is good thanks
I put a new battery in there and it is fine now. Thanks. How can I delete this thread? It is pointless now.

bringing the emty battery UP again with home tools
Please note that the following is highly experimental and if you consider to use the following "workaround" it is TOTALLY AT YOUR OWN RISK and i can not be held responsible for damages caused to your hardware or to yourself!!!!!
I had the same issue 2 times till now, what i made:
i took a USB cable (like the normal one i use for the wizard to connect it to the pc), cut off the mini usb jack. There are 4 wires in the cable we need the black one and the red one. The red goes to the + of the battery and the black goes to the - of the battery (on my battery the + and the - are marked), if on some batteries there are no marks for + and - you can use multi zet tool to check. The next thing is to put the cable in a free usb on the pc and the wires on the battery. Its quite difficult to find out the right place and position for charging the battery this way - but you actually need to charge it this way not more than 5-10 mins. Then you can boot normally and continue charging the "right" way. Use your old battery again. Thats all...
Regards

Completely Stock 19020T Bricked?

So I haven't used my Nexus for somewhere around 2 months since I got a new phone. The Nexus S was working fine prior, I had actually just got it back from Samsung after them fixing an issue related to my top volume button. After, I received it, the phone was in a complete stock condition, like it was just bought from a store (no unlocked bootloader, fastboot, Clockwork, etc.). A bit later, the OTA Jelly Bean update comes in, but I don't use it too much as I just got my new phone.
I left it on and ignored it for the past 2 months. I just assumed the battery would run out, and if I wanted to use it I would just plug it back in and that would work. Now the Nexus S won't show any sign of life. I've tried removing the battery and trying to turn it on while plugged in, when it's plugged in with my battery in, the charging indicator it used to show never shows up. Plugging it into my computer with or without a battery does nothing, it doesn't even show up in my device manager as "Unknown". I've also tried holding VOLUP + PWR for 10 seconds with all these different situations. Nothing. The phone is essentially dead. Any clue why this happened and how I should go about fixing it?

Nevermind. After leaving it plugged in with the battery for ~20 minutes it finally powered on! Hopefully this thread helps out someone in the same situation. It just seems as though it takes a long time to get it to a state in which it'll power on.

Nexus S [CM11] - hardbricked, no vigration, no computer detection!

My phone: Nexus S, 16Gb, Rom CM11, Android 4.4.4 (List of updates: https://download.cyanogenmod.org/?device=crespo)
My story
Yesterday, (about 9.00pm 13/12/2015) my phone got some laggy, so I powered him off. I left it there, 15 minutes later I came back, and I forgot that he had been powered off, so I thought it was just sleeping. I picked him up and press PowerButton. Nothing happended!
Then I got a look at CM rom, found that interesting is my Rom just got a new update at 2.00pm 13/12/2015. I think that my phone has auto-updated!!
In the past, sometime he behaved the same: PowerButton not respond. So, after that 1st press, about 5 sec later, I started to press the PowerButton repeatedly and rapidly, hopefully the phone would wake up.
But no, the reality was that he was being off. There were about 6-7 presses, I will describe slowly below (assume between each press is 0.2 sec):
1st and 2nd press: nothing happened
3rd press: the phone vibrated, and Google logo appeared
4th press: (I had no mean to continue pressing, but it was too fast, I couldn't stop) suddenly, the Google logo disappeared (so the logo stayed on screen just for about 0.2 sec; while normally, it should stay there for atleast 5 sec)
5th and 6th press: nothing happened!
And from then on, no more, anything happened.
What I tried
Hold PowerButton for even 1 minute: nothing happen!
Hold PowerButton + VolumeUP for even 1 minute: none!
Hold PowerButton + VolumeUPandDOWN for even 1 minute: none too!
Connect to charger (wall or pc): no Battery Animation show up! BUT the phone and Battery get warming up!
Take out the Battery for even 15 minutes, then put it back, and PowerButton: nothing!
And the phone not get recognized by PC too.
Sumary
No display
No vigration
No recognized by PC (because of this, I can not follow this method: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
More Information
In the past, the VolumeDOWN sometimes seems get stucked, cause the phone silent and auto boot to safemode, after many try to press and reboot, the phone may get out of safemode (because VolumeDOWN back to normal)
PowerButton sometimes not respond.
My Battery is not good, sometimes it drops too much! Eg: having 50%, after reboot, dropped to 3%, and start to increase slowly, max around 30% and become normally.
Hope you guys have some ideas! I still can't do anything, when the phone is not regconized by PC!!
Thanks for reading!
Thank you!

Hey,
2 things come to mind and I bet are both the problems. First off you need a new battery and you seem to know this, very cheap now a days but still buy a good one as cheap knock offs are abundant and don't support the power they say, try mugen, anker or stock oem
Also you need to replace power button, this phone was always notorious with bad ones, a new one is cheap but many often found just a loose connection so if you open up the phone, check the ribbon connections and then throw in that new battery all should be well, hopefully
Best of luck!

demkantor said:
Hey,
2 things come to mind and I bet are both the problems. First off you need a new battery and you seem to know this, very cheap now a days but still buy a good one as cheap knock offs are abundant and don't support the power they say, try mugen, anker or stock oem
Also you need to replace power button, this phone was always notorious with bad ones, a new one is cheap but many often found just a loose connection so if you open up the phone, check the ribbon connections and then throw in that new battery all should be well, hopefully
Best of luck!
Click to expand...
Click to collapse
Thank you. I'll try your suggest ASAP.
But I'm wondering, that do you think that CM Update maybe also a reason?

I kind of doubt it as that should only effect the software, if you were getting a bootloop or anything to that extant yeah, but being it won't power on at all I doubt it

thank you

Nope, I've seen these symptoms before - exactly the same thing. Dude, I think your phone is Superbricked.
I've got a stack of 3 Nexus S 4G's that have exactly the same problem - the eMMC card is trashed by a buggy "secure erase" implementation. See: https://wiki.cyanogenmod.org/w/EMMC_Bugs
My "working" one was working great, even set it up to sell on eBay, when I went to wipe its data with a factory-reset from the settings menus. When it shut down to reboot, I pulled the battery. That's what bricked it - because the eMMC was halfway through a background erase/rewrite procedure, it wiped out the boot loader somehow and completely bricked the phone. It now does precisely, exactly the same thing you describe - absolutely nothing, except when it's plugged in, it warms up after a while.
Best I can tell, the only way out from here is to use a JTAG device to reflash the chip, but even then, the eMMC itself might be "unbootable" (i.e. can't start up, can't be read or written, can't be reformatted/restored).
I just called it "end of life" for those phones and now they're just a sour reminder on my shelf

FalconFour said:
Nope, I've seen these symptoms before - exactly the same thing. Dude, I think your phone is Superbricked.
I've got a stack of 3 Nexus S 4G's that have exactly the same problem - the eMMC card is trashed by a buggy "secure erase" implementation. See:
My "working" one was working great, even set it up to sell on eBay, when I went to wipe its data with a factory-reset from the settings menus. When it shut down to reboot, I pulled the battery. That's what bricked it - because the eMMC was halfway through a background erase/rewrite procedure, it wiped out the boot loader somehow and completely bricked the phone. It now does precisely, exactly the same thing you describe - absolutely nothing, except when it's plugged in, it warms up after a while.
Best I can tell, the only way out from here is to use a JTAG device[/URL] to reflash the chip, but even then, the eMMC itself might be "unbootable" (i.e. can't start up, can't be read or written, can't be reformatted/restored).
I just called it "end of life" for those phones and now they're just a sour reminder on my shelf
Click to expand...
Click to collapse
thank you!!
my heart just stop breathing :'( :'(

God, I wish there were a solution to it. I'd really like to donate a phone to anyone that thinks they have the tools or skills to make a "how I did it" explanation - involving whatever tools/software are necessary - to bring these phones back and help us all. I bought 2 of those 3 phones as "for parts" on eBay, and it turned out that both of those phones appeared to have exactly this same issue (though one also had a cracked glass). I even verified the issue by swapping in my good phone's eMMC (at least on the NS4G, it's a swappable card module), and the boards booted up. I only needed the one for the good screen (as I had a good board but completely destroyed display panel) - and that's how I got my one working again.
Then, in the end, I accidentally stumbled upon the method by which the previous two phones were bricked - and now there are three. It seems like a fairly common problem. :/

Nexus 5x, The 3 episodes of DOOM.

My Nexus 5x was bought by May 15 2018, i was excited for this phone, but i never knew about all the issues it is inclined to have.
EP 1:
It started with this simple notification that started to appear randomly without any solid cause.
"USB supplying power to attached device"
I tried a couple of fixes, like cleaning the usb port, Factory and Cache wipe, and nothing worked, it was just becoming a real annoyance.
EP 2:
The next day, after i did the factory reset and realized there was nothing different about the issue, i put it to charge, moments later i tried to turn it on but i realized it wouldn't go past the google screen, google screen was just rebooting constantly, it was at this moment i got acquainted with our fellow bootloop.
I started investigating, talked to a couple of people and they recommended flashing.
At that moment i could access bootloader, and recovery...
Ok, i turn it off.
After a while, when im ready to flash, cant access recovery.
Bootloader is accesible, but oem is locked and wont allow.
Later i finally found what could be the way of solving the issue.
And i could sleep peacefully that night.
EP 3:
Now, on top of all the complications, the fatality:
Next morning.
It wont even turn on into bootloader.
But i do see that it is charging, however; it wont turn on.
Is there some way of booting it connected through the pc ?
I think i wont be letting this problem like this anytime soon, im still up and willing to find a way to solve this.

If it's still early, just return it for a refund the Snapdragon 808 and 810 are infamous for problems 9 times out of 10 for not being soldered to the motherboard properly so I would advise to return for refund or replacement

Poco X3 NFC - Can't access bootloader, fastboot or system (bootloop)

Hi. My close friend has this issue. I'm posting this because she can't figure it out by herself. A month ago, her phone downloaded an update and she installed it. Since then, the phone has restarted by itself without any reason, just random restarts and the frequency of restarts was more frequent with each day. Fast forward to this day and the phone is constantly turning up and shows the POCO logo and restarts by itself. This loop is not ending until the battery is completely dead. When trying to access fastboot or recovery mode, she can get there but only for few seconds (until the device restarts again) which is not enough time to make any changes / factory reset. She did not accessed developer tools in system, so the bootloader is still locked. Holding down power button does nothing. ONE SINGLE UPDATE screwed up whole phone. Can't do ****. There's no SD card or SIM card in the slot. Is there any "hack" to stop the phone from restarting itself? Note when the battery is completely empty and she plugs the charger, the whole nightmare starts again. I'm lost. Did you guys have any ideas what to do? Or is the repair centre only solution? (She cracked glass of the display, i'm not sure if that voids warranty. [it's not glass COVER, it's the glass which is part of the display])

Is this device unlocked? If not, then RMA.
If it is, my best guess is to get the device into recovery (or fastboot?) and immediately connect to PC.
If it holds, leave it there as it will charge, although at much slower rate.
When charged, use TWRP to try to reboot to system.
If it doesn't work, then factory reset.

Sadly, i can not get to recovery because in about 2 seconds the device will reboot. There's literally no time to make any changes - factory reset. Also the device is not unlocked. I hope RMA accept the phone even though it has cracked screen . Thanks for response anyway

Then RMA it is. If you're in EU they'll have to take it, even with the cracked screen.
But does the reboot happen even when connected to PC? Two seconds is enough to plug it in if you're fast...

Yeah, we tried every possible idea we can think of. Pressing the toggle button from different angles with different intensity to make sure it isn't stuck inside, covering up the proximity sensor (yeah makes no sense but even that we tried, lol). Tried with connected to PC as with classical charging brick. No change. Back in those days where smartphones doesn't have unibody construction and you were able to take down the back cover and remove battery it was way simple. Nowadays it's not possible to stop the phone from booting itself until battery is completely empty. My friend says the problem started about month ago, when the phone annouced that there is an update available so she downloaded it and installed it. Before that, there was no problem with the phone whatsoever. Maybe it's caused by some kind of virus but IDK which apps she was using. She didn't have rooted phone not unlocked bootloader in developer tools. Also i googled that it may be caused by "Airtel Thanks" app which she didn't have installed aswell. I will keep this thread updated as what happend to the phone cause i'm also interested what went wrong and to help future users who will struggle with this problem a solution. Thank you.

CaptainFedora, did you solve the problem? I have the same issue...

Yeah, actually. Sorry for not posting the answer although it was definitely her fault. It was the power button being pressed down (which made continuous bootloop). But the button was somehow pressed deep into the phone's body. So complete dissasembly was needed.
Btw. my friend lives in other country so we discussed this problem over internet. If i could have the phone physically with me i would definitely know what was the problem.

Hi.
Yesterday I had the same problem, the device kept restarting every 10 seconds, it didn't even come to any screen besides the first one with the POCO logo in yellow.
Things I tried that did NOT work:
restart
hard restart
fastboot (it did enter the fastboot mode, but only showing the picture of the 2 robots and after 10 seconds restarting again to the POCO logo image)
plug it to power
plug it to computer
After 3 hours of continuous restarting and trying anything I could find in the internet and I could imagine of (except extracting the battery because it seemed complicated and difficult to revert), I tried randomly something that miraculously worked...don't ask me why.
pressing the power button shortly and quickly around 30 times (it might have worked after 10 or 20, but I just kept doing it a little longer
Afterwards it just started as if nothing had happened...doesn't make any sense, but I just wanted to tell you in case you are in a similar situation and desperate to not lose all the images and videos as I was yesterday.