:crying: any ideas ?
everything was working perfectly and i didn't do anything , just when my first battery ran out , i shut it down and switch second battery then it just doesn't boot up anymore ... even with data cable connect with charger or PC, because usually it will show a charging animation when system isn't booted up ...
and one thing strange is that when i plug in my battery , phone doesn't boot up but it still heat up like i am using it ...
a little help please ...
qtwrk said:
:crying: any ideas ?
everything was working perfectly and i didn't do anything , just when my first battery ran out , i shut it down and switch second battery then it just doesn't boot up anymore ... even with data cable connect with charger or PC, because usually it will show a charging animation when system isn't booted up ...
and one thing strange is that when i plug in my battery , phone doesn't boot up but it still heat up like i am using it ...
a little help please ...
Click to expand...
Click to collapse
the same happen to me week ago! i think its jellybean...
Cascabreu said:
the same happen to me week ago! i think its jellybean...
Click to expand...
Click to collapse
how did you fix it?
i am using the unbrickable resurrector , but it keep shows device not found, no device detected
qtwrk said:
i am using the unbrickable resurrector , but it keep shows device not found, no device detected
Click to expand...
Click to collapse
Same issue with mine. Yesterday, 8/20/12, I broke a sim card connector pin and Nexus S wouldn't recognize sim card after a reboot. Rebooted the device again after the warning message: Sim card not detected/found.
Now Nexus S won't boot. Computers (Windows & OSX) can't recognize it's connected and 5 different charges won't show that the battery is charging. Battery still has a charge as I tested it in another Nexus S. When the battery is in, the device heats up. When connected to a power source, the device heats up.
Used Unbrickable resurrector with no success. UR shows: Device not found, No device detected.
Finally, I was running Jelly Bean from OTA update and not rooted. I noticed that in the past week or two the stock Andoird keyboard would cause force closing of apps or exceed processor threshold of 35% even if there was no program running. Google Now was also sucking the battery after the JB update. Turned that battery drain off on the other Nexus. Also, the Android Media process was taking a drain on the processor. Usually running at 40-50%.
Bought this used from CowBoom and hoping the extended warranty will replace or fix the broken sim card connector and unbrick the phone.
Luckily I have an iPhone 4S and a 2 yr old HTC Desire to turn to.
I've read on another thread, perhaps?, that two other users in the past week or so have had this same problem.
nexus s GT-I9020T Bricked after JellyBean
qtwrk said:
i am using the unbrickable resurrector , but it keep shows device not found, no device detected
Click to expand...
Click to collapse
Same happened to me. The Unbrickable resurrector also didnt detect the phone. so i made the Unbrickable Hardware Mod (httpxx://forum.xda-developers.com/showthread.php?t=1566475) remove the xx from httpxx. now my phone is being detected and the tool is able to load its files. but still the phone is dead, no thing happens and the tool shows no device found after it loads the files. but when i picked GALAXY S from the drop down menu. the tool loads the files and now both the tool and the phone shows download mode with an android shoveling dirt. heimdall now detects the phone but it doesnt work caz its not a GALAXY S. So let us know what happens if u try this mod. cheers
The exact same thing happened to me. Strangely, it's happening with JB roms. And yeah, i told my problem in a very educated way on the ROM topic and they simply deleted the post, how nice.
Anyway, i just sent the phone to the warranty almost three weeks ago, i'm waiting for them to fix it or give me a new one.
djdeepblue said:
The exact same thing happened to me. Strangely, it's happening with JB roms. And yeah, i told my problem in a very educated way on the ROM topic and they simply deleted the post, how nice.
Anyway, i just sent the phone to the warranty almost three weeks ago, i'm waiting for them to fix it or give me a new one.
Click to expand...
Click to collapse
no , i was running 4.0.4 , AOKP M6 , as matter fact , it seems to be a problem of latest BOOTLOADER
dokugan ryu said:
Same happened to me. The Unbrickable resurrector also didnt detect the phone. so i made the Unbrickable Hardware Mod (httpxx://forum.xda-developers.com/showthread.php?t=1566475) remove the xx from httpxx. now my phone is being detected and the tool is able to load its files. but still the phone is dead, no thing happens and the tool shows no device found after it loads the files. but when i picked GALAXY S from the drop down menu. the tool loads the files and now both the tool and the phone shows download mode with an android shoveling dirt. heimdall now detects the phone but it doesnt work caz its not a GALAXY S. So let us know what happens if u try this mod. cheers
Click to expand...
Click to collapse
well ... i don't have these tools to do hardware level of modifications ...
anyway , i just send to repair , i think , the motherborad or something should be replaced ...
i was thinking about buying a new phone such as Galaxy Nexus if my Nexus S can not be repaired or way too expensive to repair...
i had same issue a few days after upgrading to JB JRO03E. i got the main board replaced under warranty. took about 2 and half weeks.
the phone came back with GB installed but OTA'd to ICS then JB JRO03L.
I had the same issue running cm10-0823. Screen froze while sitting idle. Pulled and replaced battery, and phone won't come back.
Looks like cm10/jb is causing some burn-out in circuit board; cpu, memory...?
_android_ said:
I had the same issue running cm10-0823. Screen froze while sitting idle. Pulled and replaced battery, and phone won't come back.
Looks like cm10/jb is causing some burn-out in circuit board; cpu, memory...?
Click to expand...
Click to collapse
as i have heard is that new bootloader messes with hummingbird CPU ...
I have exactly the same problem I flashed Codename Android ROM 3.4.1, done some overclocking (only 1200 MHz) and the device crashed. Well, nothing unusual. But I removed the battery, I think it was just when the device was rebooting - I think display turned on, I noticed some flash when the battery was already removed.
I tried to turn on the device, but it's dead. Display doesn't turn on, UnBrickable Resurrector says device not found.
I can send the phone to the warranty, but it's unlocked. Do you think they will find out it's unlocked? Even if the download mod doesn't work etc?
What should I do?
Well, I happened to end up with the same problem. Installed latest cm 10 nightly, started rebooting my phone. The moment I restarted it from CWM I realised that I forgot to flash some mod in CWM so I pulled the battery to go into recovery. Phone bricked, no input at all. Sent my phone on warranty, I hope they won't mind it had unlocked bootloader and cm10 on it ;P
That's just a bit stupid to be honest, pulling the battery while booting why not just wait?
Sent from my Nexus S
Now I know it's stupid. Do you think they will repair it even though it's cm flashed and unlocked?
i sent mine to repair and they fixed without paying a dime!
Cascabreu, you just made my day Well, I just have to wait now
nexususer1 said:
Now I know it's stupid. Do you think they will repair it even though it's cm flashed and unlocked?
Click to expand...
Click to collapse
The mainboard is fried. No way of knowing previous state of your phone. They will just replace the board.
Sent from my Nexus S using XDA Premium HD app
_android_ said:
The mainboard is fried. No way of knowing previous state of your phone. They will just replace the board.
Click to expand...
Click to collapse
I had the same issue back in August just after I flashed 4.1.1/JRO03E. It just died one day while listening to music. Took about 3 weeks to get the mainboard replaced under warranty. It came back bootloader unlocked and with Gingerbread 2.3.3 installed.
Related
Just wondering how often are people experiencing this problem when the phone become completely unresponsive (unable to turn on, unable to detect, no light when charged).
I had this problem and never had it resolved and just sent the phone back for repair. It seems more and more people are posting they have this problem. Is this a ROM problem or does the HTC phone just get fried? Mine happened after I installed Revolution 6.6.2..it rebooted fine...and reinstalled apps with titanium..then all of a sudden a long tone while I was on phone and the phone unresponsive, turned off...and never turned on again.
Anyone with same problem...would appreciate your experience..and maybe we can figure out why it's happening. And I mean...the phone is just dead...no bootloop, no adb...nothing.
I ''had'' rooted Sensation Juopunutbear S-OFF,I filled the battery full...and install AOKP ROM Everything is working fine....After resetting the phone,
He did not respond...do not want to boot,does not want to even turn on,I tried everything from taking the battery to charge...no signs.....
when connecting phone to computer,sound is heard...and requires some drivers QHSUSB_DLOAD
removing battery sim sdcard and connect to power outlet and tried to switch it on-nothing...not react
is still under warranty....9 months old
I asked no one knows why it happened
I sent it to the service and I hope will not notice that he S-OFF and ROOTED :\
there are still a lot of people this problem here http://forum.xda-developers.com/showthread.php?t=1618683
Hmmm..at least yours is detected on computer. Mine was completely unresponsive...nothing worked. Some had similar problem as mine when not even the computer detects it.
IT seems to be happening quite often..and I am not sure if it's a ROM problem....but it seems it's not only from a specifice ROM.
I had one just like the op except it was stock with s-off, no custom rom yet. I turned it off and it never came back, so got a new one!
From another similar thread:
Charge your phone for 20 minutes. If you're using a Sense ROM, disable fast boot in Settings>Power. Fastboot doesn't actually power off your device, just puts it into sleep, like in Windows. This means the battery drains, even while it's "off".
On this forum, we see it atleast once a week. Something was going totally fine, no biggy, then suddenly it won't turn on, seemingly won't charge, no LEDs, not recognized by PC, etc etc.
The odds are low that it'll happen to you, but more so than other phones.
sshede said:
On this forum, we see it atleast once a week. Something was going totally fine, no biggy, then suddenly it won't turn on, seemingly won't charge, no LEDs, not recognized by PC, etc etc.
The odds are low that it'll happen to you, but more so than other phones.
Click to expand...
Click to collapse
But is this related to hardware issue or a custom ROM / firmware problem? My question is....should I try to root and do the same thing again if my phone get replaced?
If it's related to custom ROM/firmware pb...maybe it needs to be looked at? Especially when everything is running fine like many people report...
Well it would be nice if ALL of these occurrences were logged into a single thread and each user listed their firmware, rom, and kernel (which I'm most interested in)...
well i got the same problem . while playing a game phone got stuck and automatically turned off with some sound . now its desnt turning on and cant charge it coz led doesnt working ( what should i do?? going to use a another battery . if not :s idk (
Experience Senseless
HTC sensation XE with beats audio
Unlocked -Revolutionary
Pyramid Pvt S-off
Hboot 1.27.0000
Radio 11.22.3504.07_m
CID 11111111
Hi to all,
I'm in a similar situation, yesterday I updated the 4ext recovery the beta (sorry dont know what version it is) and it worked fine on the phone.
Until I thought hmm, I try [ROM][04/26/12] Virtuous Inquisition v4.0.2 :: AOSP-Experience Senseless ICS (4.0.3). I was going through the software and I've done a format on the microSD card though virtuous, and done a REBOOT on the phone, no Reboot at all. By the way while running the OS lights for the Home, Menu, Back and Search weren't truned on.
Now my phone wont turn on (although I can hear the USB being connected to my windows7 X32 bit PC). When connected to Pc or power outlet there is no indication of my phone is charged or being recharged, no light indicator.
Ok, so what if I tried using ADB commands to see if my phone still beeing detected.
I used ADB under Administrator
adb devices
*daemon not running. starting it now on port 5037 *
*daemon started successfully*
List of devices attached ( although i dont get the model number of the phone)
fastboot reboot
waiting for device
fastboot reboot-bootloader
waiting for device
fastboot flash recovery recovery.img
waiting for device
Ok no luck. Now tried to do install with the RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105_R_Radio_11.69.3504.00U_11.22.3504.07_M_release_251961_signed.exe
Runed under Admin again, so still no luck, all I get was an Error[170] usb connection Error. So the utility rom still could not detect the phone.
By the way when the phone is off, then I press volume down and power button, my phone is AOSP-Experience Senseless indeed, can't switch nothing on.
All well see what happens.
Yes..I think it's good to have a thread about this problem...maybe some more experienced DEVs can see why this is happening especially if this is occuring because of ROM/firmware or more hardware problems.
I am waiting for my phone to be sent to HTC and see what they say..hope they'll fix/replace one!
Battery, Brick or Senseless
By any chance, did anyone tried to use some friends or family they have the same phone, and use their battery. Maybe battery needs replacing?
Hopefully I can here someone says that I'm right, battery problem.
Also I'm looking at other websites to see whats the alternative to our situation.
Or maybe its just a brick, I will wait and see the Developers of this thread
http://forum.xda-developers.com/showthread.php?t=1522351
[Release coming next week. With a surprise!] Sensation Unbricking Project
hopefully will have a solution I feel lost without my phone, AOSP-Experience Senseless these two days.
God bless them hope they can do it.
barascus said:
By any chance, did anyone tried to use some friends or family they have the same phone, and use their battery. Maybe battery needs replacing?
Hopefully I can here someone says that I'm right, battery problem.
Also I'm looking at other websites to see whats the alternative to our situation.
Or maybe its just a brick, I will wait and see the Developers of this thread
http://forum.xda-developers.com/showthread.php?t=1522351
[Release coming next week. With a surprise!] Sensation Unbricking Project
hopefully will have a solution I feel lost without my phone, AOSP-Experience Senseless these two days.
God bless them hope they can do it.
Click to expand...
Click to collapse
For some it could be battery problems....but I think most of the ones reported it's not. As with mine..the battery was fully charged 100% when it happened...I think it was actually plugged in even.
The thread is for bricked phone that had this driver thing when it plugs into the computer...but if the phone is completely unresponsive...it's not goign to work!
I kept my phone charged for few hours, although my battery was full as well, the phone remained cold.
i had a similar problem last week on 04/19... battery was charging over night... at morning i turned the alarm off and after that the phone was dead... i sented it to support and now i have a new board inside and totaly new problems...locked bootloader and an unkown H-BOOT version (1.29.0000)
i also tried my battery in a other phone with no problems.
i had revolutionary 6.3. on it
Well I think I finally bricked my Nexus S. What's weird is that it's been working fine. Had JellyBro 20120817 installed for the past few days with no issues. Last night I plugged my phone in to charge and went to bed. Woke up this morning and clicked the power on button to see what time it is and it showed just fine. 20 minutes later I went to check the time again and NOTHING. Pulled battery, tried every button combo, everything. My wife has a Nexus S also, so I tried her battery with the same results. No lights, vibrations, nothing. Plugged it into my computer to see if I could get any response and still nada. Tried Fastboot and device is not found. UGH. If anyone can give me any advice on what to try feel free to chime in. I've been around long enuff to realize that I'm pretty sure it's toast. Either way... it's been a nice run.
d_phekt said:
Well I think I finally bricked my Nexus S. What's weird is that it's been working fine. Had JellyBro 20120817 installed for the past few days with no issues. Last night I plugged my phone in to charge and went to bed. Woke up this morning and clicked the power on button to see what time it is and it showed just fine. 20 minutes later I went to check the time again and NOTHING. Pulled battery, tried every button combo, everything. My wife has a Nexus S also, so I tried her battery with the same results. No lights, vibrations, nothing. Plugged it into my computer to see if I could get any response and still nada. Tried Fastboot and device is not found. UGH. If anyone can give me any advice on what to try feel free to chime in. I've been around long enuff to realize that I'm pretty sure it's toast. Either way... it's been a nice run.
Click to expand...
Click to collapse
Take it off charge and pull the battery out. Let it sit for a while (1 hour at least) without the battery. Put your wife known working battery in and cross your fingers.
polobunny said:
Take it off charge and pull the battery out. Let it sit for a while (1 hour at least) without the battery. Put your wife known working battery in and cross your fingers.
Click to expand...
Click to collapse
Tried that and still no dice. So yeah... It's done.
d_phekt said:
Tried that and still no dice. So yeah... It's done.
Click to expand...
Click to collapse
This is paranormal stuff, you have no recollection of having messed around with it flash-wise?
dinuvali said:
This is paranormal stuff, you have no recollection of having messed around with it flash-wise?
Click to expand...
Click to collapse
LOL Yeah I'm a crackflasher, but I hadn't flashed anything for a few days. It was working just fine and POOF... done.
Try odin.
Sent from my Nexus S using xda app-developers app
d_phekt said:
LOL Yeah I'm a crackflasher, but I hadn't flashed anything for a few days. It was working just fine and POOF... done.
Click to expand...
Click to collapse
I don't imagine it shows as charging when plugged in? Otherwise I'd send it for repair or just buy a new phone. :/
polobunny said:
I don't imagine it shows as charging when plugged in? Otherwise I'd send it for repair or just buy a new phone. :/
Click to expand...
Click to collapse
No it doesn't show as charging at all. Won't find device in adb, no lights, no vibration when trying to power on, nothing. It does get warm when the battery is in it tho. And it is discharging somehow, because I tried my battery in my wifes phone and it showed 33 % when I know it had a full charge before it died. GNex is on its way.
i just have had same problem days ago , unfortunately i tried all , even Odin , just non-responsive
i also tried that unbrickable tool run under Ubuntu , still no good ...
i just send it to repair... Gosh
qtwrk said:
i just have had same problem days ago , unfortunately i tried all , even Odin , just non-responsive
i also tried that unbrickable tool run under Ubuntu , still no good ...
i just send it to repair... Gosh
Click to expand...
Click to collapse
Yep, I tried the unbrickable tool also... didn't find device there either. SUX!
nexus s GT-I9020T Bricked after JellyBean
d_phekt said:
Well I think I finally bricked my Nexus S. What's weird is that it's been working fine. Had JellyBro 20120817 installed for the past few days with no issues. Last night I plugged my phone in to charge and went to bed. Woke up this morning and clicked the power on button to see what time it is and it showed just fine. 20 minutes later I went to check the time again and NOTHING. Pulled battery, tried every button combo, everything. My wife has a Nexus S also, so I tried her battery with the same results. No lights, vibrations, nothing. Plugged it into my computer to see if I could get any response and still nada. Tried Fastboot and device is not found. UGH. If anyone can give me any advice on what to try feel free to chime in. I've been around long enuff to realize that I'm pretty sure it's toast. Either way... it's been a nice run.
Click to expand...
Click to collapse
Same Problem here. It was working fine on jelly bean and rooted with clock work recovery. I removed the battery out to change the sim and now it wont power on, fastboot doesn't work and the USB JIG also doesn't work, doesn't show the charging animated when plugged in.
i tried AdamOutlers Resurector tool, it didnt detect the phone, so i made the hardware mod and now it detect the phone, but still dead after the tool loads the files. but when i choose GALAXY S from the drop down menu, the tool and the phone, both shows download mode, heimdall detect the phone but doesnt work as it is not a GALAXY S.
At least now you have a reason to upgrade. But that sure sucks, if you still want to revive it you could give this a shot... http://www.youtube.com/watch?v=Ecp8jKmm48k
Three people with Nexus S's with Jelly Been roms just spontaneously get bricked phones? Just flashed mine to CM10 Nightly yesterday...
Hmmmm
I'm not sure if I would call mine a true bricking since most bricks happen directly from a rom flash. Mine was actually working fine for a couple of days after my last flash and then suddenly stopped working. It was an almost 2 year old phone and heavily abused internally with almost daily rom/kernel flashes and overclocking. I think maybe it just got tired LOL. Oh well...we have 2 other Nexus S's in our house, so now we have a decent parts phone since externally the phone is flawless.
Try cleaning your the phone's usb slot with a toothbrush and medical alcohol. also after removing your battery, try pressing the power button for 10 Secs(without battery) this cleans any extra charges in your phone. Gd luck!
Sounds more like hardware failure than bricking.
Sent from my Crespo using xda premium
i read something that is problme of bootloader that messes with hummingbird CPU or something , i don't know
i had flashed the latest bootloader and 4.1 once it came out , but then i back to 4.0.4 and decided wait for AOKP JB.
and , my phone was also unable to power up after i pull out and change a new battery ! , first of all i was thinking battery's unstable output current damaged hardware or something , but now i am more convinced it should be the problem of bootloader as i read before
I am using vanilla rootbox 4.2.2 yesterday i flashed the kernel 3.0.80 from cm10.1 threat and today i had only 30% of battery and my phone had a little lag so i turned off the phone and removed the battery again i tried to turn on the phone and it never turned on, I had a doubt on battery so i checked the voltage and it showed 2volt i tried charging the phone for more than 5 hrs but nothing happened
so wat is the problem? ??? i cant access my recovery, hboot or anything have i bricked my phone???????
balajithegreat said:
I am using vanilla rootbox 4.2.2 yesterday i flashed the kernel 3.0.80 from cm10.1 threat and today i had only 30% of battery and my phone had a little lag so i turned off the phone and removed the battery again i tried to turn on the phone and it never turned on, I had a doubt on battery so i checked the voltage and it showed 2volt i tried charging the phone for more than 5 hrs but nothing happened
so wat is the problem? ??? i cant access my recovery, hboot or anything have i bricked my phone???????
Click to expand...
Click to collapse
Bricking HTC phones got very less chances .....like out of 100% HTC phones won't brick for 99.99% .
So try changing your battery...might help
Sent from my HTC Explorer using xda premium
It's definitly no a brick 'cause you did flashed your kernel and ROM successfully after rooting it. I've never heard of anyone who bricked his phone while he rooted it succesfully and had a working custom ROM on it.
Have you overclocked it, may the battery/chipsets died this way? Any scripts or tweaks on it?
Mhmmm...found this:
http://lifehacker.com/5853519/how-do-i-fix-my-bricked-android-phone
It says sth. about phones that won't turn on anymore
Dude ... Yeah Firstly .. trying changing The Batt. cause .. i have a feeling ur Battery has gone Bad ... :/ n try to clean ur like golden slots in battery .. Check if there is Carbon type thing in those ..
This may be the first case of bricking i've seen for Pico. Have a look at your battery, or the port in which your charger plugs in.
Do you charge with USB? I had a problem with my USB wire, it did not charge when connected to adapter, so i used my Samsung charger and charged the phone. So check your charging apparatus.
If everything is in vain, go to HTC Store and play dumb (i.e. "Sir i was using it and suddenly it did not start")
and Rule 1 in playing dumb: Never utter the "root" word, nor bootloader, its best if the store guy thinks you're a noob
Trust me, most of the time if you are within the warranty time they wont bother and give you a new phone, my friend once did with Micromax, and got it repaired free of cost.
I have been using this site for years and searching for the last few weeks I am not new to changing roms but this time i missed a step and the situation is this the phones does not respond to any buttons and the white led indication light comes on when i connect to PC normally this means battery is totally dead but I followed other instructions on this site and recharge battery independently and checked its charge with multimeter and everything good.
The only time the phone gives me any indication that it is responding is when connected to the PC with white LED, any suggestions or is it the time for the bin, any suggestions help appreciated, thanks in advance and just to make it clear the phone not booting up into anything from what i can see.
Looks like you're hard bricked, but it also can be dead battery. So first I recomended recharge battery. And also tell us that you did to the phone before - downgrade to GB & etc.
Sorry man. Sounds like she's dead.
http://forum.xda-developers.com/showthread.php?t=1937112
EDIT
Beat to the punch.
I also had screwed up my phone. I had tried to downgrade to GB after ICS (OTA)... I know it was really stupid of me...
Anyway, I also used to get white LED when connected to PC.
When connected to wall charger I used to get Moto Logo. I thought it was getting charged, but it was not.
I then gave it to the Moto authorised service center, and then gave me back phone with GB flashed...
When I asked them what they did, they told me battery was dead and the charged it(not through the phone, but by using some other sort of charger)...
You should also try the same.
Tell them that the battery went completely dead, while you were trying to do OTA update. (That's what i told)
karthiks.840 said:
I also had screwed up my phone. I had tried to downgrade to GB after ICS (OTA)... I know it was really stupid of me...
Anyway, I also used to get white LED when connected to PC.
When connected to wall charger I used to get Moto Logo. I thought it was getting charged, but it was not.
I then gave it to the Moto authorised service center, and then gave me back phone with GB flashed...
When I asked them what they did, they told me battery was dead and the charged it(not through the phone, but by using some other sort of charger)...
You should also try the same.
Tell them that the battery went completely dead, while you were trying to do OTA update. (That's what i told)
Click to expand...
Click to collapse
If you can see the Moto Logo when you switch on the phone or connect to a charger, that means your phone is not Hard Bricked, its Soft Bricked. You can use RSDLite and fxz your phone back to life, but if you see a black screen and a white LED when you connect to your phone to a PC/Laptop, that means your phone is Hard Bricked. If you are on warranty, return it to Motorola and get a replacement. Hope this helps.
minhajlk said:
If you can see the Moto Logo when you switch on the phone or connect to a charger, that means your phone is not Hard Bricked, its Soft Bricked. You can use RSDLite and fxz your phone back to life, but if you see a black screen and a white LED when you connect to your phone to a PC/Laptop, that means your phone is Hard Bricked. If you are on warranty, return it to Motorola and get a replacement. Hope this helps.
Click to expand...
Click to collapse
Dear Sir,
I was using Stock ICS 4.0.4 (InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml) on my atrix but later when i try to restart it, it shows Customer ID error so i used to open it again by using BP Tools. Later i found in some threads that switching back to Stock GB will help you recovering that error. so i download Stock GB (InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285). while doing it from RSDLite during the middle process (5/20 reboot bootflash) it went fails and my phone turned black. now its not opening neither any combination of keys are working and nor showing the LED lite. Now what to do? any solution?
moiz.mithani said:
Dear Sir,
I was using Stock ICS 4.0.4 (InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml) on my atrix but later when i try to restart it, it shows Customer ID error so i used to open it again by using BP Tools. Later i found in some threads that switching back to Stock GB will help you recovering that error. so i download Stock GB (InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285). while doing it from RSDLite during the middle process (5/20 reboot bootflash) it went fails and my phone turned black. now its not opening neither any combination of keys are working and nor showing the LED lite. Now what to do? any solution?
Click to expand...
Click to collapse
I replied to the other thread you opened. Please do not post the same thing in a thread then, open another with the same thing, as it just clutters this board.
Please look in the other thread you posted:
http://forum.xda-developers.com/showthread.php?p=44971858
moiz.mithani said:
Dear Sir,
I was using Stock ICS 4.0.4 (InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml) on my atrix but later when i try to restart it, it shows Customer ID error so i used to open it again by using BP Tools. Later i found in some threads that switching back to Stock GB will help you recovering that error. so i download Stock GB (InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285). while doing it from RSDLite during the middle process (5/20 reboot bootflash) it went fails and my phone turned black. now its not opening neither any combination of keys are working and nor showing the LED lite. Now what to do? any solution?
Click to expand...
Click to collapse
Sorry to be the bearer of bad news, but there is no known way to recover a lost CID if you didn't back it up. I don't know where you read that flashing back to GB would fix it, because the general consensus in this forum is flashing back to GB from ICS will, more often than not, hard brick your phone. It sounds to me like that is exactly what happened, you've hard bricked your phone. There is no "fix" for that though there is still some hope. If your phone is still under warranty you can just get it replaced. If it's not under warranty, you can try to buy another Atrix 2 with a cracked screen and use the mother board from it to replace the one in your phone.
Is there any possibility you can provide a link to where it was said that the Customer Identification Number could be restored in this manner? I think it's important to correct whomever gave you this bad information before they cause someone else to make this same mistake.
Brought to you by time and relative dimensions in space.
1BadWolf said:
Sorry to be the bearer of bad news, but there is no known way to recover a lost CID if you didn't back it up. I don't know where you read that flashing back to GB would fix it, because the general consensus in this forum is flashing back to GB from ICS will, more often than not, hard brick your phone. It sounds to me like that is exactly what happened, you've hard bricked your phone. There is no "fix" for that though there is still some hope. If your phone is still under warranty you can just get it replaced. If it's not under warranty, you can try to buy another Atrix 2 with a cracked screen and use the mother board from it to replace the one in your phone.
Is there any possibility you can provide a link to where it was said that the Customer Identification Number could be restored in this manner? I think it's important to correct whomever gave you this bad information before they cause someone else to make this same mistake.
Brought to you by time and relative dimensions in space.
Click to expand...
Click to collapse
Thanks for the reply, m in Pakistan and the phone is AT&T came from US .. so no point of warranty for me and it happens exactly after one year lol .. anyways i showed it to market .. hardware person says its software issue and vise versa ... board is perfect .. but its not opening .. bootloader is dead .. and i cant find anyone here using test point for flashing motorola ..
Stick with one thread. Multi posting is frowned upon.
Sent from my MB865 using Tapatalk 2
bildar said:
I have been using this site for years and searching for the last few weeks I am not new to changing roms but this time i missed a step and the situation is this the phones does not respond to any buttons and the white led indication light comes on when i connect to PC normally this means battery is totally dead but I followed other instructions on this site and recharge battery independently and checked its charge with multimeter and everything good.
The only time the phone gives me any indication that it is responding is when connected to the PC with white LED, any suggestions or is it the time for the bin, any suggestions help appreciated, thanks in advance and just to make it clear the phone not booting up into anything from what i can see.
Click to expand...
Click to collapse
What message do you get when you use RSD lite.... does the PC recognize the device in any way or not...
coz my defy went the same way with the white led coz of a dead battery (try MCgruvier method ) and check once......
I just got this very neatly used 32GB Nexus 5 and on arrival yesterday afternoon it worked well except for the reboot problem the seller indicated. I flashed stock all over and rooted and installed ElementalX kernel for tap to wake and everything was going well, until last night when it just up and died on me. I thought maybe the battery was drained and I plugged it on the charger. It wasn't charging so I left it overnight. On waking up the phone is still dead. Doesn't charge, doesn't boot, nothing. I've opened it up, disassembled it to check all the parts, and everything looks fine. I also tested the battery by touching the tip of my tongue to the connector and I got the normal tingy feeling indicating the battery still has juice in it. I also checked the two LDIs and they are all still white; no water damage. I'm just at my wit's end now and considering getting another motherboard if that would fix it, but I just want to ask if there is any hope through any kind of fix before I commit to getting a new motherboard.
It might be that ?
http://forum.xda-developers.com/google-nexus-5/help/battery-issue-charge-cold-t3100267
Quentincc said:
It might be that ?
http://forum.xda-developers.com/google-nexus-5/help/battery-issue-charge-cold-t3100267
Click to expand...
Click to collapse
Thanks for your response but my phone is not even booting up at all. It's just dead. Not booting, not charging, nothing. Thanks again.
IF you press power and the volume buttons and connect it to computer, did you have in device manager something?
If it was something like QHSUSB ... you can try that (it use and LG debuging software who reflash the nexus all at stock like in the factory) : http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
If not it was possible that the EMMC is dead
I hope i have help you
Quentincc said:
IF you press power and the volume buttons and connect it to computer, did you have in device manager something?
If it was something like QHSUSB ... you can try that (it use and LG debuging software who reflash the nexus all at stock like in the factory) : http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
If not it was possible that the EMMC is dead
I hope i have help you
Click to expand...
Click to collapse
I tried that but nothing comes up in Device Manager at all. The computer does not detect the phone in any way at all too. I think the motherboard is dead. I ordered another working Nexus 5 with a broken screen on ebay to use and swap out the motherboard.
Thanks for your replies. I appreciate it.