Related
I don't know what went wrong..
My phone stuck at dialer after i made a phone call..therefore I pulled out the battery,put it back & try to turn it on..but nothing happened.
I tried to go into recovery (volume down+power) but it still wont turn on..
Also i tried to use ADB but my phone not detected..
The phone wont turn on,nothing on the screen,LED light not blinking (even when i connect to PC or wall charger)
Please let me know if you guys got any suggestion or even better if there is a solution..
please dont tell me that my phone is bricked
far8s said:
I don't know what went wrong..
My phone stuck at dialer after i made a phone call..therefore I pulled out the battery,put it back & try to turn it on..but nothing happened.
I tried to go into recovery (volume down+power) but it still wont turn on..
Also i tried to use ADB but my phone not detected..
The phone wont turn on,nothing on the screen,LED light not blinking (even when i connect to PC or wall charger)
Please let me know if you guys got any suggestion or even better if there is a solution..
please dont tell me that my phone is bricked
Click to expand...
Click to collapse
any luck on this??? i jacked mine up trying to flash a new firmware and am stuck in the same boat with my sensation being completely unresponsive.
You could factory reset it:
From the manual:
If you can’t turn HTC Sensation 4G on or access settings, you can still perform a factory reset by using the hardware buttons on HTC Sensation 4G.
1. Remove the battery, wait for a few seconds, then reinsert the battery.
2. Press and hold the VOLUME DOWN button, and then briefly press the POWER button.
3. Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button.
4. Press VOLUME DOWN to select FACTORY RESET, and then press the POWER button."
Overlord-in-training said:
You could factory reset it:
From the manual:
If you can’t turn HTC Sensation 4G on or access settings, you can still perform a factory reset by using the hardware buttons on HTC Sensation 4G.
1. Remove the battery, wait for a few seconds, then reinsert the battery.
2. Press and hold the VOLUME DOWN button, and then briefly press the POWER button.
3. Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button.
4. Press VOLUME DOWN to select FACTORY RESET, and then press the POWER button."
Click to expand...
Click to collapse
It was stated that he can't access the bootloader, which is what is required for the "FACTORY RESET"...
There are a number of people reporting this issue. I've even experienced the issue after the device powered down due to a drained battery. Luckily I have a stand alone charger. I put the battery on the charger for about 15 minutes, put it back in the device and it was able to boot, charge, connect usb etc...
I tried for 20 minutes to get any response from the device before trying the charger.
No charging LED isn't a good sign.
There seem to be more and more people reporting with this problem these last few weeks. IT happened with mine....it was not battery drained cuz it went dead when battery was 100% charged. I've been trying to get input as to whether this is related to ROM or firmware we're flashing....but no one seem to know.
Nothing will work...ADB...battery out...etc...I've sent my phone back to HTC...waiting to see what happens.
There are at least 3-4 different post with the same problem the past few weeks.
newr said:
There seem to be more and more people reporting with this problem these last few weeks. IT happened with mine....it was not battery drained cuz it went dead when battery was 100% charged. I've been trying to get input as to whether this is related to ROM or firmware we're flashing....but no one seem to know.
Nothing will work...ADB...battery out...etc...I've sent my phone back to HTC...waiting to see what happens.
There are at least 3-4 different post with the same problem the past few weeks.
Click to expand...
Click to collapse
What rom were you running when this happened?
GROGG88 said:
It was stated that he can't access the bootloader, which is what is required for the "FACTORY RESET"...
There are a number of people reporting this issue. I've even experienced the issue after the device powered down due to a drained battery. Luckily I have a stand alone charger. I put the battery on the charger for about 15 minutes, put it back in the device and it was able to boot, charge, connect usb etc...
I tried for 20 minutes to get any response from the device before trying the charger.
Click to expand...
Click to collapse
Well what i did was that i had a brand new sensation, i got it s-offed, rooted, cwm, superCID. all that done following the guide here on XDA. i wanted to have the new elegancia ICS rom which required the 3.32 firmware with the 4ext recovery. I got the 4ext flashed and then flashed the 3.32 firmware which caused a bootloop. then i panicked and tried to put it back to stock. not realizing that it was prolly bootlooping due the stock rom not being compatible with that firmware (not positive if that caused the bootloop. just a guess) it bricked after trying to put it back to stock. nothing responds. computer doesnt recognize it. new battery doesnt to anything. no charging led. looking back on what i did. I was still able to get into the 4ext recovery when it was bootlooping. If i flashed a compatible rom while it was doing that would it have fixed the issue. can anyone confirm if the bootloop was caused due the the stock TMOUSA rom not being compatible with 3.32? Tmobile is going to send me a brand new one. I'd like that rom but dont wanna repeat the same mistake lol
Thanks
shawn0223 said:
Well what i did was that i had a brand new sensation, i got it s-offed, rooted, cwm, superCID. all that done following the guide here on XDA. i wanted to have the new elegancia ICS rom which required the 3.32 firmware with the 4ext recovery. I got the 4ext flashed and then flashed the 3.32 firmware which caused a bootloop. then i panicked and tried to put it back to stock. not realizing that it was prolly bootlooping due the stock rom not being compatible with that firmware (not positive if that caused the bootloop. just a guess) it bricked after trying to put it back to stock. nothing responds. computer doesnt recognize it. new battery doesnt to anything. no charging led. looking back on what i did. I was still able to get into the 4ext recovery when it was bootlooping. If i flashed a compatible rom while it was doing that would it have fixed the issue. can anyone confirm if the bootloop was caused due the the stock TMOUSA rom not being compatible with 3.32? Tmobile is going to send me a brand new one. I'd like that rom but dont wanna repeat the same mistake lol
Thanks
Click to expand...
Click to collapse
Yep, it was because stock was incompatible with that fw, happened to me two weeks ago when I got my sensation and I started tinkering, I flashed opensensation and I was good to go
Sent from my sensational sensation 4g
yahhboy said:
Yep, it was because stock was incompatible with that fw, happened to me two weeks ago when I got my sensation and I started tinkering, I flashed opensensation and I was good to go
Sent from my sensational sensation 4g
Click to expand...
Click to collapse
so if i do the same process and go flash the new rom right after flashing the fw. i shouldnt have a problem right?
tjamaican said:
What rom were you running when this happened?
Click to expand...
Click to collapse
I installed 6.6.2 Revolution. It booted fine after I installed the ROM...so unlike some others, the installation seems to worked fine. I was able to run Titanium and restalled all the programs....but then when I talked on the phone....it became unresponsive and shutdown and never turned on again
Having similar problem.........only thing my phone just vibrates......the led is red for couple seconds when charger is connected
dreaddie101 said:
Having similar problem.........only thing my phone just vibrates......the led is red for couple seconds when charger is connected
Click to expand...
Click to collapse
WEll..if your phone lights up or have some response.maybe you can still do something by connecting to computer. Mine was completely unresponsive...and can't be detected on computer!
Maybe it's an overclock issue? I've read on different threads that there may be a motherboard issue. The sensation is known for overheating. Maybe it's frying the motherboard.
What frequency were you guys running and was your phones randomly shutting down before it became unresponsive?
i think we guyz got the same problem :S its just turned off with a constant beep
http://forum.xda-developers.com/showthread.php?t=1624293
shawn0223 said:
so if i do the same process and go flash the new rom right after flashing the fw. i shouldnt have a problem right?
Click to expand...
Click to collapse
Yes you should be fine, just make a backup of stock in case something goes wrong when you flash your first rom
Sent from my sensational sensation 4g
yahhboy said:
Yes you should be fine, just make a backup of stock in case something goes wrong when you flash your first rom
Sent from my sensational sensation 4g
Click to expand...
Click to collapse
Awesome, I just got my new sensation yesterday. Worked like a charm.
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
shawn0223 said:
Awesome, I just got my new sensation yesterday. Worked like a charm.
Click to expand...
Click to collapse
Oh and thanks lol
Hi, my Atrix seems to be stuck in a boot loop although I don't think it's totally bricked.
My phone was unlocked, rooted, and running CM7 fine for several months and then the other day while charging it via USB, several apps kept started to force close so I thought I would try rebooting the phone. Upon reboot the got to the CM7 splash screen and automatically rebooted then it would only load up the Motorola symbol then reboot again and every time after it would reboot after the moto symbol. I thought no problem I would just flash back to stock via .sbf
I plugged in the phone and RSD Lite detected it. I loaded the 2.3.4 ATT SBF file (used it before 2 or 3 times safely) then started the flashing process and waited. I got to where it said reboot phone manually, so I did. After restarting the phone, it showed the Motorola creen then the ATT screen so I had thought I fixed it. While on the ATT screen it froze for a few minutes then it entered the boot loop process again getting to ATT screen each time.
I thought maybe it was a bad flash so I tried flashing the SBF again (in hindsight, probably not a good idea). It got to same place it did before and asked me too reboot and the boot loop process started again. I tried to manually restart it by holding volume down and power, but I would get the RSD Protocol Support message.
Is my phone recoverable or is bricked? If bricked, what are my options regarding obtaining a new phone since I am out of warranty, no insurance and cant upgrade till September and don't exactly have $500 for a new smartphone?
i think your phone is recoverable soft bricked
Yes soft bricked, hey you ride a 450?
Sent from my HTC Wildfire S using xda premium
Yes, soft bricked. If you can get into download mode just flash back to stock and try again. If not, use a jig. You can also buy a jig from ebay for less then $4 buy it now , free shipping.
There might be other ways but I cannot think of any atm. Its almost 4am here lol.
Sent from my Serendipity 6.4 flashed Captivate using xda premium
soft bricked...majorly due to kernal problem..reflash the kernal
Thanks all and no I don't "ride a 450" sorry (I'm assuming by that you mean motorcycle or ATV with a 450cc engine)
oh sorry I meant to ask that question to dirtbikerr450, but yes a 450cc engine
Android311 said:
oh sorry I meant to ask that question to dirtbikerr450, but yes a 450cc engine
Click to expand...
Click to collapse
No i dont sadly i ride a 125
I was finally able to get into Android Recovery by unplugging the battery then plugging in the usb then simultaneously holding volume down and plugging in the battery, I wiped the data and cache then rebooted, to my suprise it booted back up but, only to where I could make emergency calls. Tried to reflash stock with RSD Lite again this time it said passed though but I can still only make emergency calls. Any suggestions?
dirtbikerr450 said:
No i dont sadly i ride a 125
Click to expand...
Click to collapse
125s are great, I ride a crf450 great bike
Sent from my HTC Wildfire S using xda premium
whenemusattack said:
I was finally able to get into Android Recovery by unplugging the battery then plugging in the usb then simultaneously holding volume down and plugging in the battery, I wiped the data and cache then rebooted, to my suprise it booted back up but, only to where I could make emergency calls. Tried to reflash stock with RSD Lite again this time it said passed though but I can still only make emergency calls. Any suggestions?
Click to expand...
Click to collapse
Nice man! Why don't you flash cm7?
Sent from my HTC Wildfire S using xda premium
I took out the sim card and wiped it and then reinserted it and the phone booted. I don't know if I want to unlock and root again, at least probably not until ICS is here. How is CM9, stable enough for everyday use?
Im not sure, but most cm9 here are still nightlys (I think) which would be stable for everyday use, so maybe next month you will start to see stable versions out
Sent from my HTC_A510c using XDA
Ok, here's where I'm at...
Rooted/Kexec installed
Flashed several ROM's over the last two weeks or so with no issue.
Never did a backup and restore.
Flashed a CM10 Invisitek(?) ROM today and didn't like it.
Before I flashed it, I made a backup of my XTC install.
Tried to restore that XTC and it failed.
Tried to restore again and it said that it passed and I rebooted.
Now, when you turn the phone on, it will boot up to Samsung Custom with a lock icon then flash the Samsung Galaxy SIII screen.
Once it flashes the second screen, it will go to a blank screen and that's it.
I've tried to get the phone into Download mode by pressing both volume keys, home and power at the same time and it boots as described above.
Any nudges in the right direction? :fingers-crossed:
Laramie1997 said:
Ok, here's where I'm at...
Rooted/Kexec installed
Flashed several ROM's over the last two weeks or so with no issue.
Never did a backup and restore.
Flashed a CM10 Invisitek(?) ROM today and didn't like it.
Before I flashed it, I made a backup of my XTC install.
Tried to restore that XTC and it failed.
Tried to restore again and it said that it passed and I rebooted.
Now, when you turn the phone on, it will boot up to Samsung Custom with a lock icon then flash the Samsung Galaxy SIII screen.
Once it flashes the second screen, it will go to a blank screen and that's it.
I've tried to get the phone into Download mode by pressing both volume keys, home and power at the same time and it boots as described above.
Any nudges in the right direction? :fingers-crossed:
Click to expand...
Click to collapse
Since I'm in a similar situation have you tried using odin
joka10 said:
Since I'm in a similar situation have you tried using odin
Click to expand...
Click to collapse
I can't put it in download mode, so I can't use ODIN...
sorry i did see that lol what i ment to ask was can you get into the recovery
joka10 said:
sorry i did see that lol what i ment to ask was can you get into the recovery
Click to expand...
Click to collapse
No I can't unless I'm missing something other than power/volume up and down/home button at the same time...
try this instead press all three at the same time volume up, home, and power
joka10 said:
try this instead press all three at the same time volume up, home, and power
Click to expand...
Click to collapse
That's what I've been doing.
Laramie1997 said:
That's what I've been doing.
Click to expand...
Click to collapse
If you have a custom rom still on your sd card, try booting into recovery volume up+home+power and wipe data/ factory reset and then install zip from sdcard.choose your rom and flash.. that should be able to get you to boot up again. I had to do this when my phone would boot up and go blank after the sgs3 logo screen.
Do those two ROMs use different kernels? Because if that's the case, there's your problem. To my knowledge, CWM doesn't backup kernels, so restoring a nandroid wouldn't restore the kernel needed for that particular ROM to function. At least, that's how it was for my old Xperia Play. You needed to flash the new kernel before the ROM to ensure it would boot. With kexec, that's a little different.
But, I could be totally off base. Just throwing my limited knowledge out there for someone to maybe expound upon.
sorry you thru me off in your post above i thought you saying that you pressing all four my mistake but you can go here http://webchat.freenode.net/?channels= and for the channel use either #verizons3 or #verizons3-dev, they can also help you but of course stay on this thread to.
mustbepbs said:
Do those two ROMs use different kernels? Because if that's the case, there's your problem. To my knowledge, CWM doesn't backup kernels, so restoring a nandroid wouldn't restore the kernel needed for that particular ROM to function. At least, that's how it was for my old Xperia Play. You needed to flash the new kernel before the ROM to ensure it would boot. With kexec, that's a little different.
But, I could be totally off base. Just throwing my limited knowledge out there for someone to maybe expound upon.
Click to expand...
Click to collapse
That makes sense and I overlooked that. Dam.
I wonder if there is a fix???
Laramie1997 said:
That makes sense and I overlooked that. Dam.
I wonder if there is a fix???
Click to expand...
Click to collapse
It makes sense for some phones, but it doesn't make sense that you're unable to get into download mode. Regardless of the incorrect kernel, you should be able to get into download/recovery mode. What is your device registered as when you plug it into your machine (such as QHSUSB_DLOAD)? Are you running Windows/Mac/Linux?
If your phone turns on you can get to Odin. Your best bet is making a usb jig. It's a special usb end that has 300k ohm resistor between two pins of the usb. When plugged in and the phone turns on it puts you directly into download mode. You can Google on how to make one from a usb cable and resistors from Radio Shack or mobiletechvideos.com sells them for $8.
Once in download/Odin mode you can re flash everything to stock.
Sent from my DROIDX using xda app-developers app
mikejr83 said:
If your phone turns on you can get to Odin. Your best bet is making a usb jig. It's a special usb end that has 300k ohm resistor between two pins of the usb. When plugged in and the phone turns on it puts you directly into download mode. You can Google on how to make one from a usb cable and resistors from Radio Shack or mobiletechvideos.com sells them for $8.
Once in download/Odin mode you can re flash everything to stock.
Sent from my DROIDX using xda app-developers app
Click to expand...
Click to collapse
This is your best bet if nothing else is working. I bought one from China on eBay last year for my GNex. I'm glad I've always got it.
Yea, I ended up having to jig it this morning when I got to the office and had access to my other tools. THAT got it into Download mode and allowed me to flash it back to stock. Bizzare evening for sure.
Thanks for all the help!
For the record...
To get into DOWNLOAD mode you hold home, power, and volume DOWN.
Volume up is for recovery.
Hope that helps.
I've seen the samething
joka10 said:
Since I'm in a similar situation have you tried using odin
Click to expand...
Click to collapse
I've seen the same issue, I was on Senergy and then tried to test CM10, I didn't like it and I went back to Senergy and I flashed it like normal way, however my phone stack on Samsung logo, after 15 minutes pressing all buttons then I was finally able to get recovery, reflashed senegy and it was alright, I Had very less battery, it could be that but not sure..
maybe
Laramie1997 said:
That makes sense and I overlooked that. Dam.
I wonder if there is a fix???
Click to expand...
Click to collapse
yeah that's right
Same problem
I had this same problem for a AT&T gs3 but I think my battery died and when I plug it in it won't charge. How can I fix that charging problem and then the start up problem?
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 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)...