I am so sad as I write this...:crying:
I had TWRP custom recovery and running the ARHD 9.0 rom.
I was tempted to try the other roms so I played around with Omega and ReVolt rom..they worked fine...
Then, when I tried to reflash ARHD 9.0, I could get to TWRP recovery but it just reboots even before any of the buttons appear.
So, I went into download mode and flashed HighOnAndroid custom recovery.
It seem to work fine....so I went ahead and flashed ARHD 9.0....It installed fine and completed successfully.
But when I rebooted the device...sigh...no power, not even the charging animation when I plug it into the charger...
So, if anyone has a solution on what I should do, please do tell me or I am really sad...so so sad...:crying:
Try a different charger, cable and wall outlet. Leave the n8000 there for a while. Hold the power button for a while, then let it go. Listen closely to the speakers for the little samsung sound when it turns on. Idk if the rom you installed has a boot sound tho. Anyways, if you still dont have an answer after that.. I would maybe start to think the power button is dead. Its a last ditch option but plausible i suppose lol.
Beyond that, you might have to think about sell it for parts.
Oh and i remember from my time with the Samsung vibrant that sometimes, even if nothing comes up on the screen, the device might be picked up by Odin after doing the dl mode button combo
Sent from my Nexus 4 using xda app-developers app
younix258 said:
Try a different charger, cable and wall outlet. Leave the n8000 there for a while.
Click to expand...
Click to collapse
I brought a friend's Note and charged using my usb charger/cable...it is working ok.
I would maybe start to think the power button is dead. Its a last ditch option but plausible i suppose lol.
Beyond that, you might have to think about sell it for parts.
Click to expand...
Click to collapse
My Note is about 2 months old and is still under warranty period. As a last resort, I can send it to them.
Oh and i remember from my time with the Samsung vibrant that sometimes, even if nothing comes up on the screen, the device might be picked up by Odin after doing the dl mode button combo
Click to expand...
Click to collapse
I will try and post back here.
Thanks for sharing your thoughts though.
freelancer81 said:
I brought a friend's Note and charged using my usb charger/cable...it is working ok.
My Note is about 2 months old and is still under warranty period. As a last resort, I can send it to them.
As you have root and custom rom then warranty is void .
If Samsung cannot tell that you have root and custom rom is a different matter .
Click to expand...
Click to collapse
Have you tried plugging in to your pc, see if odin recognizes it? If so try flashing stock samsung rom.
Sent from my GT-N8013 using XDA Premium App
rail205 said:
Have you tried plugging in to your pc, see if odin recognizes it? If so try flashing stock samsung rom.
Click to expand...
Click to collapse
I tried it....not detected...
It's very strange...no backlit or sound even when pressing power, power+vol up/vol down combos.
There was no error at all while flashing the ARHD 9.0.....and when I click on the finish and restart/reboot button at the end, boom..it shutdowns and dies on me...
I have googled it but no one has ever come across this kind of problem.
Since it is completely dead, there is a chance that sammy will not know it's rooted and running custom firmware.
Thanks to you and JJEgan for your concerns and suggestions.
As it sounds like a hardware issue, Samsung will likely fix it under warranty. At least that was my experience with Asus on my previous tablet.
Sent from my Vivid 4G using xda app-developers app
Do you know.if your battery was almost dead when flashing that last. Rom? I've heard that can brick ur device if it dies in flashing process. (Even tho you said flash completed) but who knows?
trevor7428 said:
Do you know.if your battery was almost dead when flashing that last. Rom? I've heard that can brick ur device if it dies in flashing process. (Even tho you said flash completed) but who knows?
Click to expand...
Click to collapse
I am not very sure about the exact battery percentage but yeah, it was low...somewhere about 10%~30%.
So, does that mean there is no way to revive it?
:crying:
freelancer81 said:
I am not very sure about the exact battery percentage but yeah, it was low...somewhere about 10%~30%.
So, does that mean there is no way to revive it?
:crying:
Click to expand...
Click to collapse
Unfortunately not without a new motherboard it seems like. If the is no sign of life, no recovery, no download mode and can't flash via oden or kies on computer with proper drivers installed. Then it sounds like a hard brick. Not recoverable unless new motherboard or JTAG. :/
Sorry man. But in future never flash if less than 30% battory. I've heard some pple say not below 50%
I don't know if your 10.1 died while flashing, but if so it could hard brick
50% is the suggested level of battery because flashing actually uses a large amount of battery. Also the tablets seem to power down things at 10%power.
Could be it shut off if the power dropped below 10%. This is why we suggest to not flash below 50%...
trevor7428 said:
Unfortunately not without a new motherboard it seems like. If the is no sign of life, no recovery, no download mode and can't flash via oden or kies on computer with proper drivers installed. Then it sounds like a hard brick. Not recoverable unless new motherboard or JTAG. :/
Sorry man. But in future never flash if less than 30% battory. I've heard some pple say not below 50%
I don't know if your 10.1 died while flashing, but if so it could hard brick
Click to expand...
Click to collapse
ultramag69 said:
50% is the suggested level of battery because flashing actually uses a large amount of battery. Also the tablets seem to power down things at 10%power.
Could be it shut off if the power dropped below 10%. This is why we suggest to not flash below 50%...
Click to expand...
Click to collapse
so sad....lesson learnt too late....the hard way :crying:
But I guess I have learnt one more way of hardbricking a device.
dude, seems like maybe a problem with your "main board"... i had the same issue at my galaxy tab 2, and i sent it to the shop ( because its passed warranty period already)...
Related
my atrix 2 don't know dead or what?
it did't on while pressing the power button and the screen black or nothing appear while i plug in the charger.
Help!!!!!!
say someting in detail please~
say someting in detail please~
My atrix 2 ME865 was running ICS4.0.4 MERetail.I wanna flash it back to 2.3.6,so i download the (InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip) from the droid-developers.
My phone battery is 40% while flashing using RSDlite 5.6.
Everything ok but at the process 5/21 it say "FAIL"
then the phone just black screen.
atrix2 said:
my atrix 2 don't know dead or what?
it did't on while pressing the power button and the screen black or nothing appear while i plug in the charger.
Help!!!!!!
Click to expand...
Click to collapse
Have you tried holding down BOTH volume buttons while powering on the device to boot into AP Fastboot, and try to flash the FXZ that way?
I try that but nothing happen.
atrix2 said:
My atrix 2 ME865 was running ICS4.0.4 MERetail.I wanna flash it back to 2.3.6,so i download the (InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip) from the droid-developers.
My phone battery is 40% while flashing using RSDlite 5.6.
Everything ok but at the process 5/21 it say "FAIL"
then the phone just black screen.
Click to expand...
Click to collapse
Meretail flashing with at&t rom?
It does not seem like a good idea.
You can downgrade it to http://sbf.droid-developers.org/edison/5.5.1-EDEM-27-MEARET_cfc.xml.zip with RSd Lite (Made it with RSD Lite 4.7 successfully).
atrix2 said:
I try that but nothing happen.
Click to expand...
Click to collapse
So, can you even boot into AP Fastboot, or is your device not powering on at all...?
Solution
seems like ur rom chip in the motherboard has gone bad. same happened to me when trying to flash custom rom to AT&T atrix 2. Went to Motorola service center costed me $160 to get a new motherboard ...but it got fixed and worth the effort....worth a try...
So i was flash the wrong rom.
But i can't flash again because i cannot enter the AP Fastboot,both vol button n power on do nothing.
atrix2 said:
So i was flash the wrong rom.
But i can't flash again because i cannot enter the AP Fastboot,both vol button n power on do nothing.
Click to expand...
Click to collapse
Maybe your battery is empty. Never start to flash without full battery (and not correct rom of course).
If you're feeling brave, try THIS...
Thanks for the feedback.
So i can still hold both vol button + power up to enter the bootloader if i flash fail?
I remember it stuck at 5/21 in RSDlite.
atrix2 said:
Thanks for the feedback.
So i can still hold both vol button + power up to enter the bootloader if i flash fail?
I remember it stuck at 5/21 in RSDlite.
Click to expand...
Click to collapse
No, the bootloader is locked on the MB865. You mentioned before that trying to boot into AP Fastboot isn't responsive either, right? If you are able to do anything, you need to flash 5.5.1-EDEM-27-MEARET_cfc.xml.zip as xanadu suggested.
Always a good idea to make a CWM backup before flashing any new roms, just in case...
LOCKED??
I think my battery is empty so it black screen when i press the button.
And i got many cwm backup which i backup before my phone cannot boot.
How to restore the cwm backup if my phone can't boot?
atrix2 said:
LOCKED??
I think my battery is empty so it black screen when i press the button.
And i got many cwm backup which i backup before my phone cannot boot.
How to restore the cwm backup if my phone can't boot?
Click to expand...
Click to collapse
If you're completely dead in the water, you'll have to find a way to get charge to the battery. You might try The McGuyver Method to get a charge to battery, but be very wary in doing this -you could fry your phone and/or explode your battery. If you're not comfortable doing this (and I don't recommend this if you are not savvy with electrical stuff and 'open phone surgery' you should first try and get your hands on a new OEM battery!
Apex_Strider said:
If you're completely dead in the water, you'll have to find a way to get charge to the battery. You might try The McGuyver Method to get a charge to battery, but be very wary in doing this -you could fry your phone and/or explode your battery. If you're not comfortable doing this (and I don't recommend this if you are not savvy with electrical stuff and 'open phone surgery' you should first try and get your hands on a new OEM battery!
Click to expand...
Click to collapse
i tried that method on my defy 3 times .....never had issue.....but still it was quite scary for me every time.....but in the end it worked......risk is needed to be taken ......
Thanks but that way is too dangerous.I was afraid so i will send it to the Motoservice because i got no ideo for the empty battery on a dead phone.
atrix2 said:
Thanks but that way is too dangerous.I was afraid so i will send it to the Motoservice because i got no ideo for the empty battery on a dead phone.
Click to expand...
Click to collapse
Before you ship your device off to the netherworld of Motorubbish, try getting a new battery. It may be a faster fix and you won't have to deal with wait tine from Moto. Plus, if you've rooted and Moto is able to determine that you'll have no warranty.
Sent from my MB865 using xda premium
Apex_Strider said:
Before you ship your device off to the netherworld of Motorubbish, try getting a new battery. It may be a faster fix and you won't have to deal with wait tine from Moto. Plus, if you've rooted and Moto is able to determine that you'll have no warranty.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Also if you are debating getting a new battery, try to get an external charger, it costs a lot less and you will be able to recover from this a whole lot easier if you have the external charger, otherwise McGyver is the only way out for you...
I would NOT take this into Motorola, especially since you failed a flash, they can see that, the first time they get it to turn on it will go to the recovery screen and say failed flash.... They may NOT give you any support.
I would try the external battery charger.
Here are a couple examples of Atrix2 external battery chargers:
http://www.wirelessemporium.com/p-1...pare-battery-charger-w-usb-port-mid-size-.asp
http://www.wirelessemporium.com/p-102964-universal-spare-battery-charger-w-usb-port.asp
jimbridgman said:
Also if you are debating getting a new battery, try to get an external charger, it costs a lot less and you will be able to recover from this a whole lot easier if you have the external charger, otherwise McGyver is the only way out for you...
I would NOT take this into Motorola, especially since you failed a flash, they can see that, the first time they get it to turn on it will go to the recovery screen and say failed flash.... They may NOT give you any support.
I would try the external battery charger.
Here are a couple examples of Atrix2 external battery chargers:
http://www.wirelessemporium.com/p-1...pare-battery-charger-w-usb-port-mid-size-.asp
http://www.wirelessemporium.com/p-102964-univertssal-spare-battery-charger-w-usb-port.asp
Click to expand...
Click to collapse
thats your best bet unless you know someone with the same phone. I have a family member with the same one, so when I killed my battery during a flash I just stole that one for 5 minutes.
While I was flashing a ROM (Synergy1.3), my wife decided to move my phone to another table. When i looked at it a few minutes later,the screen was blank. Now it wont turn on at all. I had used that particular ROM before without any problems. My battery was at 90% when i started to flash. I have a terrible feeling i am bricked. Any ideas?
goralla said:
While I was flashing a ROM (Synergy1.3), my wife decided to move my phone to another table. When i looked at it a few minutes later,the screen was blank. Now it wont turn on at all. I had used that particular ROM before without any problems. My battery was at 90% when i started to flash. I have a terrible feeling i am bricked. Any ideas?
Click to expand...
Click to collapse
You take out the battery..then try it?
Dominazn said:
You take out the battery..then try it?
Click to expand...
Click to collapse
yes,also tried charging it from wall charger ans USB. I get this error when plugging into USB (QHSUSB_DLOAD)
It's hard to brick a phone. Worst case, boot into download mode and Odin up the stock image.
If you can't access Download mode, you've most likely bricked as any research I've done points to it. If you've got insurance you can pay the premium, or send it to one of the JTAG services for repair (such as MobileTechVideos).
Just don't leave or touch the phone next time when you're flashing!
With my case it's hard to hit the buttons for recovery and download. I created across to get to them. Not what you're wanting to here. But here's a tip: if you can get adb to recognize your phone but can't use buttons to get into download mode you can "adb shell" and then "reboot download". That will cause the phone to boot download/Odin mode. Hopefully that will work and you can flash back to stock.
Sent from my SCH-I535 using xda app-developers app
The phone will not power up in any way at all. I am in the 5th stage of the grieving process. Back to my Tbolt and hope Samsung honors the warranty.
goralla said:
The phone will not power up in any way at all. I am in the 5th stage of the grieving process. Back to my Tbolt and hope Samsung honors the warranty.
Click to expand...
Click to collapse
They won't honor it with a rooted phone or flash count pass 0
Sent from my Verizon Samsung Galaxy S3 4G LTE
If you cant get to download mode or get adb to recognize when properly set up you do probably have a brick. What's happening to you with the warning happened to my friend on Sprint while accidentally flashing a ROM for a different phone. What he had to do was send it in to MobileTechVideos and got it repaired for around 60$. Samsung/Verizon wont likely fix them under warranty.
My only question is if you indeed were flashing synergy, how did a system ROM brick a device. o_0 And hell even if it was another phones ROM wouldn't our locked bootloader deny overwriting?
enomele said:
If you cant get to download mode or get adb to recognize when properly set up you do probably have a brick. What's happening to you with the warning happened to my friend on Sprint while accidentally flashing a ROM for a different phone. What he had to do was send it in to MobileTechVideos and got it repaired for around 60$. Samsung/Verizon wont likely fix them under warranty.
My only question is if you indeed were flashing synergy, how did a system ROM brick a device. o_0 And hell even if it was another phones ROM wouldn't our locked bootloader deny overwriting?
Click to expand...
Click to collapse
I also accidentally flashed a rom for a different phone and am considering sending it to MobileTechVideos. Your friend had good success with them fixing his phone?
-Purk
I think this might also work for you, if the battery charging icon comes on while your charging it then this might work. When you have it connected and the charging icon comes on put it in download mode(do not unplug it until your in download mode). Then use odin to flash it back to stock. It happen to me ones and when i did this it work for me, so i don't know if this will work for you. (Sorry for my grammar)
I flashed a Jellybean touchwiz rom for Verizon GS3, and went to reboot and now nothing, zero zip nada. No charging led light, no way to get into recovery and no response.
Anything I can do?
what happens when you do vol up + home+power button?
Absolutely nothing. I tried to get back into the recovery to see if I could restore my backup and nope.
did you try leave it pluged in for 30mins ?
does it vibrate once when you try to turn it on?
No vibrating and no sign of life at all. Even when plugged into my computer, I was going to try the unbrick guide but it listed that I should be able to get into the recovery still.
NickTheMajin said:
No vibrating and no sign of life at all. Even when plugged into my computer, I was going to try the unbrick guide but it listed that I should be able to get into the recovery still.
Click to expand...
Click to collapse
leave it plugged in for a while to make sure its not drained battery
do you have a usb jig?
I don't have a USB jig but this is possibly good news. I removed the battery and SD card and plugged it into my computer and it tried to install drivers (failed but tried) and the led light comes on red.
if your gettin led now you more then likely need to let it charge
It doesn't give me the led with the battery in
Plug it into a wall charger for at least 30 or even better if you can get a battery from someone.
Sent from my sexy white Eclipsed galaxy S3
I think its gone still nothing.
red led means qualcomm download mode. sounds dead to me
Yeah, haha. I saw it and mentally prepared myself for it. Literally just got the phone today so Verizon had no qualms with just sending me a new phone. Guess I'm reactivating my Rezound in the meantime. Thanks for the help guys.
you know
I am surprised. That also happened to me the first time i flashed that very same rom (touchwiz) with twrp . I have done this so many times , i literarily can flash a rom on the way to work .
I was in shock , i still dont know how the heck can i flash a rom and brick .
I plugged mine into windows and i got the device manager driver error from hell . and my phone never came back up again
I stayed away form twrp and touchwiz and i still cant possibly comprehend how a simple rom flash can brick my phone .
Which ROM did you flash?
Sent from my SCH-I535 using xda premium
you could probably send it to get Jtag'ed for around $60 if your warranty is invalid (ie used device)
You just hard bricked it. I did the same thing. Check here - post 5 shows the same symptoms :http://forum.xda-developers.com/showthread.php?t=1770341
And here: http://forum.xda-developers.com/showthread.php?t=1791721
I was pushing a copy of root66 that I hadn't md5'd. Took a JTAG to bring me back (twice) .
Sent from my SCH-I535 using xda app-developers app
So, in the future, md5 checksum absolutely everything since I'm assuming now that that is why this happened? (Since I made doubly sure I was flashing a rom for my phone).
If you still have the file you downloaded, you can check it. That would answer that question. If it checks out fine, then we have to look elsewhere for the problem.
BTW, MobileTechVideos.com can bring you back - based on my experience with them, I highly recommend.
Sent from my SCH-I535 using xda app-developers app
Please share exactly what you did so others can benefit from your unfortunate experience.
What ROM did you flash?
Did you use ODIN or a recovery?
If recovery, which one - CWM or TWRP?
Was there any unusual condition you can think of ... low battery, USB connected to computer or to charger, etc?
I flashed the JB ROM on my Tab 7 Plus. After the "succeess" of the flashing as said by Odin v1.85, I tried to turn on the device, but it didn't. I tried to access download mode or recovery mode but it didn't work either. I tried to hold the volume down button and connect the cable to the tablet. That opened the download mode but the screen was "flashing". The rate at which the screen "flashes" keeps increasing until it becomes very fast and the device turns off. I tried to flash a ROM, but Unfortunately it turns off fast that there will be no time for the flashing process to continue.
Any idea what should I do?
what model device do you have and what exact ROM did you flash? and which ROM did you have before flashing.
If you say I dont know to any of these.....
Reply
chrisrotolo said:
what model device do you have and what exact ROM did you flash? and which ROM did you have before flashing.
If you say I dont know to any of these.....
Click to expand...
Click to collapse
My Device is GT-P6200 and I got the GT-P6200 JB ROM for it.
______________
I left my device to charge all night. When I woke up I tried to see if the 'flashing' of the screen still occurs, but it didn't happen. I think I can flash a ROM now
I tried to flash the ROM again and it worked, luckily it was not a hard brick. Problem solved. It is weird that the flashing didn't succeed the previous time. Maybe the battery level was low (about 20%) when I flashed the ROM the previous time, can this be the problem?
yes, also a faulty or non-OEM cable would be the culprit.
SudoHalt said:
I tried to flash the ROM again and it worked, luckily it was not a hard brick. Problem solved. It is weird that the flashing didn't succeed the previous time. Maybe the battery level was low (about 20%) when I flashed the ROM the previous time, can this be the problem?
Click to expand...
Click to collapse
yess. flashing(blinking) screen is how download mode tells you that your battery is low. probably less than 10% since it even turned off by itself.
This Happend To me and I got it BACK
Hello... I totally understand your frustration... This exact same thing happened to me after my battery went dead just after I installed JB...
well here is the kick and it's kind of tricky...
If you want you can call me and I can tell you the instructions, it's complicated but if you follow the steps it will work...
I can also take the time to write it down, but i'm bad a typing.
let me know if you are interested...
Sorry for the late reply. It was fixed after less than a day from starting this thread.
Sent from my GT-I9001 using xda app-developers app
Guys,
Have been running MIUI V5 on my d2vzw (ported from d2spr) for a couple of days now. Noticed today that the videos were playing reversed (probably due to the ROM running on sprint kernel, correct me if i am wrong). So i flashed one of the kernels for vzw and had a bootloop.
So, in a moment of inspiration :crying:, i restored the boot partition from my MIUI v4 backup in TWRP (thinking that must be the kernel part) and the phone wont boot. No Download mode, no vibration, get the red indicator on for some seconds but thats it. I get QHSUSB_DLOAD error when connected to my computer.
Guess this is a hard brick. Would i be able to get into download mode with USB JIG (i would need to make one, if there is no chance i will not try it). Is JTAG my only option? I have no warranty between since i am using this phone in India.
Guys,
Any Help??
I doubt it, have you trying taking out the battery holding vol up, power, and home for about 3 seconds and letting go to get into recovery to wipe the miuiv4 boot
They are different versions so flashing different rom boots won't boot the rom.
Sent from my SCH-I535 using Tapatalk 2
Addiso said:
I doubt it, have you trying taking out the battery holding vol up, power, and home for about 3 seconds and letting go to get into recovery to wipe the miuiv4 boot
They are different versions so flashing different rom boots won't boot the rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Well, my thinking was since both were 4.1.2, it should not be a problem. I was proved wrong anyway. The phone has no life at all. Is JTAG my only option??
killmastern3 said:
Well, my thinking was since both were 4.1.2, it should not be a problem. I was proved wrong anyway. The phone has no life at all. Is JTAG my only option??
Click to expand...
Click to collapse
I believe so if nothing comes up but it's weird it was just the boot that you messed with. And you still get at least a red light. If it's hard bricked I believe there is no light whatsoever.
Sent from my SCH-I535 using Tapatalk 2
What is the reality of this thought anyone have the truth?, ThanksQ
Is this statement TRUE for certain? Quote: "I believe so if nothing comes up but it's weird it was just the boot that you messed with. And you still get at least a red light. If it's hard bricked I believe there is no light whatsoever."
Thanks in advance! moi
killmastern3 said:
Well, my thinking was since both were 4.1.2, it should not be a problem. I was proved wrong anyway. The phone has no life at all. Is JTAG my only option??
Click to expand...
Click to collapse
Pull battery and let sit an hour so everything discharges and try again. If still blacked out most likely J-Tag. QHSUSB_DLOAD error is a bad sign.