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
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
Hello to everyone and respect to all you developers for your hard work!
as you can see i'm noob but i'll try not to be too noobish.
here's the situation.. now, i have hephappy's CM9 bluepill rom installed in my lg p500 and it works just perfect (i mean it,just perfect),
and before that i have flashed custom rom's couple of times with success but once when i tried to boot into emergency mode (vol down+back+power) after that i couldn't get rid of that yellow message every time i restarted or turn on my phone till today.
so, now i'm living with that issue,but it bothers me,i can't understand why yellow emergency screen is showing EVERY time i reboot my mobile.
then i find out that the only way to avoid that is pulling battery out and wait for at least 5 minutes and then switch on (then it's ok - LG logo and blah blah).
but when i try to turn it on for less than 5 mins, emergeny mode will be showing everytime i switched mobile on.
so, i don't have a clue or answer what it could be. i tried to flash stock firmware through KDZ and actually everything seems ok and everything works just fine but that yellow screen still spy on me.
as i said, everything works perfect but when battery is drained or i wanna reboot my mobile i have emergency mode shown,so i must repeat above procedure with pulling out battery for 5 mins everytime.
i hope i didn't complicate this
Try to change RADIO (BASEBAND),maybe it might help you!
Sent from my LG-P500 using xda premium
totalka said:
Hello to everyone and respect to all you developers for your hard work!
as you can see i'm noob but i'll try not to be too noobish.
here's the situation.. now, i have hephappy's CM9 bluepill rom installed in my lg p500 and it works just perfect (i mean it,just perfect),
and before that i have flashed custom rom's couple of times with success but once when i tried to boot into emergency mode (vol down+back+power) after that i couldn't get rid of that yellow message every time i restarted or turn on my phone till today.
so, now i'm living with that issue,but it bothers me,i can't understand why yellow emergency screen is showing EVERY time i reboot my mobile.
then i find out that the only way to avoid that is pulling battery out and wait for at least 5 minutes and then switch on (then it's ok - LG logo and blah blah).
but when i try to turn it on for less than 5 mins, emergeny mode will be showing everytime i switched mobile on.
so, i don't have a clue or answer what it could be. i tried to flash stock firmware through KDZ and actually everything seems ok and everything works just fine but that yellow screen still spy on me.
as i said, everything works perfect but when battery is drained or i wanna reboot my mobile i have emergency mode shown,so i must repeat above procedure with pulling out battery for 5 mins everytime.
i hope i didn't complicate this
Click to expand...
Click to collapse
your not noobish. you post in the right place.
I have like no idea what you are expierencing. have you tried booting to recovery?
-DarkKnight- said:
your not noobish. you post in the right place.
I have like no idea what you are expierencing. have you tried booting to recovery?
Click to expand...
Click to collapse
yes pal. everything i can remember including booting into recovery with clockworkmod, wiping all data,cache,update with kdz,then root,flash new rom...and everytime everything goes like a glowe,everything is stable,with no errors.
i suppose i'm one of the luckiest lg p500 users when it's about good,stable device,which could be overclocked or tweaked without kernel panic,errors, etc (i heard that differences between same devices can vary).
BUT after all that i have that same issue with yellow emergency mode.
finally, i suppose that yellow screen is the price i must pay at the cost of good stability and great performance
did you try flashing gb stock rom by lgmdp?
totalka said:
yes pal. everything i can remember including booting into recovery with clockworkmod, wiping all data,cache,update with kdz,then root,flash new rom...and everytime everything goes like a glowe,everything is stable,with no errors.
i suppose i'm one of the luckiest lg p500 users when it's about good,stable device,which could be overclocked or tweaked without kernel panic,errors, etc (i heard that differences between same devices can vary).
BUT after all that i have that same issue with yellow emergency mode.
finally, i suppose that yellow screen is the price i must pay at the cost of good stability and great performance
Click to expand...
Click to collapse
If you can get into yellow screen your ok
Last resort use kdz just don't take out battery or disconnect and you should be fine
Sent from the My Little Pony Official App
@dhruv:
I heard about lgmdp,but i didn't found myself interested enough to try it
Because i actualy didn't had any issues excep that yellow screen.so you think it could be helpful?
@darkknight:
It is the only way i can avoid yellow screen by pulling out battery for 5 mins.
I know that my prob is unusal but now i have a lot of apps installed linked with link2sd,so i should find some way to safely backup all that stuff and try to do smtg.
Sent from my LG-P500 using xda app-developers app
totalka said:
yes pal. everything i can remember including booting into recovery with clockworkmod, wiping all data,cache,update with kdz,then root,flash new rom...and everytime everything goes like a glowe,everything is stable,with no errors.
i suppose i'm one of the luckiest lg p500 users when it's about good,stable device,which could be overclocked or tweaked without kernel panic,errors, etc (i heard that differences between same devices can vary).
BUT after all that i have that same issue with yellow emergency mode.
finally, i suppose that yellow screen is the price i must pay at the cost of good stability and great performance
Click to expand...
Click to collapse
I didnt get the method of flashing rom.. what you said above!!
You root again after updating from kdz.. you have gone wrong somewhere thats why you
get emergency mode everytime you restart.
I would suggest.. clear all the links.. make a nandroid backup. Dont use kdz as its not
required. Go into recovery.. clean everything (specially boot) and flash any rom and see if the problem persists.
which rom and which recovery maybe you can try and change the recovery. I wont reccomend kdz because i flashed it 10-12 times but after that i bricked my phone 2 times while flashing with kdz.
Here it is..
I had official gingerbread used when i found out that cm9 ics was out.then i have wait for stable cm9 rom,till hephappy's premature version.
So,i decided to flash premature,so here is a short procedure..
I don't have exact rooting/flashing guide link right now but i found it on xda forums for p500.
Downloaded short fuse,adb,etc and root via usb & command prompt..everything was ok,device sucesfully rooted,i got superuser.
Next step i installed rom manager from google play and follow flash instructions from xda including nandroid backup,booting to recovery,wiping data,dalvik,battery,everything that could be wiped..then installed premature,gapps,everything goes just fine.
I have been using premature till bluepill cames out.
just before flashing new rom i decided to hard reset via vol up+home+power, but i accidently entered into emergency mode by pressing vol down+back+power instead and after that yellow showing i have issue with it.
Downloaded then stock ginger rom from xda sites (20g),installed via kdz,everything flows fine,rooted againg with same procedure,flashed bluepill rom too with same procedure and still having that yellow emergency mode issue.
I think i made it much more clear
Sent from my LG-P500 using xda app-developers app
I was trying to root my Galaxy Tab 2 for the first time. The process started, but failed. Now I'm stuck on the "firmware upgrade encountered an issue" screen. The device will turn off and back on, but remains on error screen. Seems to be trapped in download mode (as I can still see the download progress bar). Go Mobile and Odin say the device has connected to PC.
Anyone know of anything to fix this? Should I just revert to stock ROM and try again later?
davick said:
I was trying to root my Galaxy Tab 2 for the first time. The process started, but failed. Now I'm stuck on the "firmware upgrade encountered an issue" screen. The device will turn off and back on, but remains on error screen. Seems to be trapped in download mode (as I can still see the download progress bar). Go Mobile and Odin say the device has connected to PC.
Anyone know of anything to fix this? Should I just revert to stock ROM and try again later?
Click to expand...
Click to collapse
can you actually boot in to download mode? power and vol down after power off? I know you say it seems to trapped in download mode but they're different! If you can, flash a stock rom from sammobile.com
squ89r97 said:
can you actually boot in to download mode? power and vol down after power off? I know you say it seems to trapped in download mode but they're different! If you can, flash a stock rom from sammobile.com
Click to expand...
Click to collapse
I cannot boot into download mode. When I turn it off, it simply flashes off for a few secs then goes back to the error screen on its own. Does the same thing when I turn it back on myself. No logo screen. No droid. Nothing.
EDIT: Unplugged device entirely and retried the stock ROM in Odin. Finally worked! Looks like it might be fixed now.
davick said:
I cannot boot into download mode. When I turn it off, it simply flashes off for a few secs then goes back to the error screen on its own. Does the same thing when I turn it back on myself. No logo screen. No droid. Nothing.
EDIT: Unplugged device entirely and retried the stock ROM in Odin. Finally worked! Looks like it might be fixed now.
Click to expand...
Click to collapse
Phew, glad to hear it. I've been there myself with the P3110 - take a step back, breath and relax. compose and BOOM! make backups! and backup some more!
squ89r97 said:
Phew, glad to hear it. I've been there myself with the P3110 - take a step back, breath and relax. compose and BOOM! make backups! and backup some more!
Click to expand...
Click to collapse
One can never have too many backups. I back-up EVERYTHING, even software and drivers I know will become outdated eventually.
Thanks for the help. I also pressed the button. Plz don't thanksrage on me! *cowers*
davick said:
One can never have too many backups. I back-up EVERYTHING, even software and drivers I know will become outdated eventually.
Thanks for the help. I also pressed the button. Plz don't Thank Rage on me. *cowers*
Click to expand...
Click to collapse
Better to have them and not need them, than not have them and need them - Thanks for thanking *Shakes fist and shouts "I'll let you off this once"*
davick said:
I cannot boot into download mode. When I turn it off, it simply flashes off for a few secs then goes back to the error screen on its own. Does the same thing when I turn it back on myself. No logo screen. No droid. Nothing.
EDIT: Unplugged device entirely and retried the stock ROM in Odin. Finally worked! Looks like it might be fixed now.
Click to expand...
Click to collapse
It was already in download mode.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I think my cord might have an issue (or they're just testy in general). I was noticing the battery wasn't fully charging for a while before all this. After the whole brick issue, I plugged it in to charge and it started flashing the "loading charge (empty battery + loading circle)" screen on and off until I unplugged and re-plugged it. I suspect that this is why the rooting failed in the first place.
Hi you may use cf auto root for gt p5113 with odin.this happend to me couple days ago.
Sent from my SAMSUNG-SGH-I747 using xda premium
I also bricked my tablet. Searched wide and low for ideas on how to fix. But I can't find a thing. I cannot get into Odin mode or recovery. Just hangs on the battery charging screen. My windows 7 computer can't even recognize it in Kies or odin. Yes the tablet is rooted.
Hi, I am new at this forum and i would like to ask you the following question.
recently i bought a samsung galaxy ace 2 phone and today i decided to try a custom ROM with, being a Linux geek for years...
So i chose Kyrillos Rom for my phone and after several failures i got to understand that before i try to load the custom ROM i had to upgrade my firmware and kernel as described here :http://forum.xda-developers.com/showthread.php?t=1955679
So i used Odin tool , and tried to flash the new firmware as described here :http://forum.xda-developers.com/showthread.php?t=2118119,before proceeding to kernel flash.
Everything went smooth , Odin showed 'pass' indication and my phone after the procedure tried to reboot...and never woke up...
From then i cannot boot my phone at all, i mean neither in usual mode by pressing the power button nor in recovery or download mode. It does not respond to any of those, the screen and the buttons are completely black no matter how many seconds i press them
When i started the procedure my battery level was at 70% and just to be sure i connected it to USB port so as not to empty the battery during the procedure..Now that i connected it to its' charger it does not show the charging indicator
Any ideas as to what happened and how i can fix my problem?
Thank you in advance and keep up the good job!!!
seems motherboard is dead u need to get it replaced anyway did u follow the odin guide carefully cause it seems not
Blackwolf10 said:
seems motherboard is dead u need to get it replaced anyway did u follow the odin guide carefully cause it seems not
Click to expand...
Click to collapse
It seems that i followed the exact directions in the posts mentioned, but my phone is I8160P and not I8160 something that i had not noticed up until tonight,so i think that it has something to do with this, even though i cannot understand how my motherboard died because of the firmware upgrade even thw firmware is made for another model...
VisagenNoir said:
It seems that i followed the exact directions in the posts mentioned, but my phone is I8160P and not I8160 something that i had not noticed up until tonight,so i think that it has something to do with this, even though i cannot understand how my motherboard died because of the firmware upgrade even thw firmware is made for another model...
Click to expand...
Click to collapse
it does have everything to do with that but it seems more like a hardbrick to me so does the phone charge or have u tried a lot of times to boot it or maybe pull the battery out for 5 min then put it back in and try to go to recovery or download if none of these stuff work then i think its dead
Blackwolf10 said:
it does have everything to do with that but it seems more like a hardbrick to me so does the phone charge or have u tried a lot of times to boot it or maybe pull the battery out for 5 min then put it back in and try to go to recovery or download if none of these stuff work then i think its dead
Click to expand...
Click to collapse
Yes i tried both normal boot pressing the power button and recovery - download modes and it did not power on in any of those cases. Also i tried pulling out the battery for 5 - 10 minutes and it did not power on afterwards either.Is this something that happens often because it seems really strange to me. If it has nothing to do with the firmware upgrade and it is a hardware issue then ok, i can sent it to repair it but if i have already lost the warranty due to root and firmware - custom recovery etc.. then what exactly do i have to do..
VisagenNoir said:
Yes i tried both normal boot pressing the power button and recovery - download modes and it did not power on in any of those cases. Also i tried pulling out the battery for 5 - 10 minutes and it did not power on afterwards either.Is this something that happens often because it seems really strange to me. If it has nothing to do with the firmware upgrade and it is a hardware issue then ok, i can sent it to repair it but if i have already lost the warranty due to root and firmware - custom recovery etc.. them what exactly to i have to do..
Click to expand...
Click to collapse
i don't think they will know since the phone won't boot up at all they know by going to download so give it a try and take it to a service and if ur in europe rooting does not affect ur warranty hope this helps
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)...