[Q] Bricked/Boot Loop Galaxy Note 10.1!! - Galaxy Note 10.1 Q&A, Help & Troubleshooting

Hello fellow XDA members! I am a Noob.
So I believe I have a Bricked Galaxy Note 10.1. Model GT-N8013
I Rooted Stock ROM, and flashed Collective Edition 5 Dark Side.
So heres what happened, everything seemed fine, until I made a mistake, I was Pimping my ROM with the PimpMyRom app. Every change seemed fine and my note worked, but when i saw the double boot screen slide in the app, i did what it said, i have the imf support or something like that. Then after i had the ''support'' needed, i clicked install button on the double boot slide, it seemed to do something and requested nothing, so i went ahead chose a second clip, and clicked set as second boot screen. It said it wont take effect until the 3rd boot, so i rebooted 3x, but at the third time, it was stuck at the boot screen with the galaxy note 10.1 logo ! It did not start or did anything, over time it would turn off and automatically reboot, but it would get stuck again !.
To attempt to fix it, I Booted into recovery (CWM) and did everything i could. I wiped nearly all cache, factory reseted, then out of fear, i flashed the stock firmware ROM from Sammobile website, with ODIN, and to my knowledge, it got worse!! It booted, seemed to do something then in the logo screen it got stuck once again!! Stock recovery says unable to mount /efs, i don't believe EFS is completely corrupted, I left it stuck for awhile and it shut down in like an hour. Help, what can i do to fix this!?!?!?!
Device cannot boot up.
I could boot into recovery and download mode only.

I thought that I too had bricked my 8013 the past weekend. Trying to do something that I shouldn't. It took me a bit of work and a lot of worry (my wife gave me my 8013 for Xmas and if I had to tell her that it was now a doorstop, she would have killed me). I used this method to get back to stock and then was able to work my way back to the ROM I use. I disremember in which order I Odin'd things, but in the end was able to un-brick. All I can say is give it a shot.

jusliloleme said:
I thought that I too had bricked my 8013 the past weekend. Trying to do something that I shouldn't. It took me a bit of work and a lot of worry (my wife gave me my 8013 for Xmas and if I had to tell her that it was now a doorstop, she would have killed me). I used this method to get back to stock and then was able to work my way back to the ROM I use. I disremember in which order I Odin'd things, but in the end was able to un-brick. All I can say is give it a shot.
Click to expand...
Click to collapse
i did what u said...but all i got is i able to get through the logo but without seeing anything only able to hear the sound. any other tip? i got the same problem as above.

Related

Issues with recovery

Just bought my phone a couple of days ago, I was looking to root it as I had an Incredible but stepped up to this. Rooting went pretty good, failed first time but went through the second. Then I installed rom manager and flashed clockwork. I then went into the recovery but saw that I had an issue with with it about signatuire verification so I figured I still had the stock recovery. I went in and got the modded recovery file and just renamed the old one. Rebooted into recovery and the phone would lock at the samsung screen and not go anywhere. So i booted it back up like regular and flashed clockwork again and tried to boot into recovery again with the same issue but now I can't get the phone to boot up regularly. Its just hanging at the samsung screen, I have the battery pulled while I wait just to make sure its not an issue like that. Did I miss something when I was doing this? I watched the videos on how to root and install the recovery but I'm lost as to what is going on now. I thought my only issue was the stock recovery was still installed for some reason so I replaced that with the modded version. Thanks for you help and I hope I don't have to redo everything again.
Alright, delete this as I got inpatient and figured my phone was screwed anyways so I went ahead and used odin and I'm in clockwork right now. Sorry for creating a useless thread.

[Q] Please help me on this i cant seem to find the answer anywheres

i have rooted my g2x several time but after i shut if off to charge at night i tuirned it on and it went straight to the cwm recovery screen i wiped it and restarted it and it went right back to it i flashed several other roms and when i went to reboot it it still rebooted to recovery screen i formated everything i new of what am i doing wrong. i had a stable rom in it and it was working for like 3 weeks before this happened . I hope someone can help me on this i love my phone and dont want to lose it. My computer is running on windows 7 i have tried these
http://forum.xda-developers.com/showthread.php?t=1056847
http://forum.xda-developers.com/show....php?t=1056847
and i even tried one where i tried to flash it back to stock and and now it stuck on a white box with an arrow coming out of it with and android robot in front of it
Did i brick this can it be saved i hope someone can help me one this i just pray i didnt brick it
STANC1 said:
i have rooted my g2x several time but after i shut if off to charge at night i tuirned it on and it went straight to the cwm recovery screen i wiped it and restarted it and it went right back to it i flashed several other roms and when i went to reboot it it still rebooted to recovery screen i formated everything i new of what am i doing wrong. i had a stable rom in it and it was working for like 3 weeks before this happened . I hope someone can help me on this i love my phone and dont want to lose it. My computer is running on windows 7 i have tried these
http://forum.xda-developers.com/showthread.php?t=1056847
http://forum.xda-developers.com/show....php?t=1056847
and i even tried one where i tried to flash it back to stock and and now it stuck on a white box with an arrow coming out of it with and android robot in front of it
Did i brick this can it be saved i hope someone can help me one this i just pray i didnt brick it
Click to expand...
Click to collapse
I don't exactly know how to fix your problem, but to shine some light, your not bricked. If u were, u wouldn't be able to access anything
Sent from my LG-P999 using XDA
STANC1 said:
i have rooted my g2x several time but after i shut if off to charge at night i tuirned it on and it went straight to the cwm recovery screen i wiped it and restarted it and it went right back to it i flashed several other roms and when i went to reboot it it still rebooted to recovery screen i formated everything i new of what am i doing wrong. i had a stable rom in it and it was working for like 3 weeks before this happened . I hope someone can help me on this i love my phone and dont want to lose it. My computer is running on windows 7 i have tried these
http://forum.xda-developers.com/showthread.php?t=1056847
http://forum.xda-developers.com/show....php?t=1056847
and i even tried one where i tried to flash it back to stock and and now it stuck on a white box with an arrow coming out of it with and android robot in front of it
Did i brick this can it be saved i hope someone can help me one this i just pray i didnt brick it
Click to expand...
Click to collapse
Use this to put cwm and then flash the rom you like.
If phone still boots into recovery you may have a stuck vol- button.
http://forum.xda-developers.com/showthread.php?t=1590523
Sent from my LG-P999 using XDA
i cant get into recoveery now im stuck in it relaoding as i tried to flash the recovery again and its stuck
try and flash again, if it doesn't stick, then try again. If it gives you an error report the error. Try what mansa_noob posted, it usually works for everyone, it fixes everything (partition and issues) and then flashes the recovery for you.

[Q] Galaxy S2 Soft Bricked after root....

Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
Try flash a stock firmware by using flashtool, it will work 100%:angel:
revernwe therefore
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
brandonarev said:
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
Click to expand...
Click to collapse
Thanks for the advice! Should i flash it back to ICS then try to root again via Odin before i upgrade back to JB? I'm guessing there's something that isn't getting wiped. Since i can run CWM and Root with Odin without a hitch. it's the initial reboot after all that is done that I go into the boot loop.
tainiun rioters
pierm said:
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
Click to expand...
Click to collapse
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
addamT989 said:
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
Click to expand...
Click to collapse
addamT989 said:
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
Click to expand...
Click to collapse
Hi
TWRP and the 'one touch recovery, better than CWM.
The backup kies can not recover from CWM
steps:
install odin, after recovery, nandroid backup, ROM, and root.
hi
Flash the stock firmware using odin!!..it will work!
Sent from my GT-N7100 using xda premium
freezes then booted
Hello I have this problem with my galaxy s2 i9100. After reboot the phone wasn't booting something like "boot loop" so I re flashed the firmware and now the phone boots up but after the boot it freezes immediately. So I decided to install clock work mod recovery and install cyanogen mode 11 with cyanogen mode the phone boots up and are able to be used again until the screen goes to sleep mode or the power button is pressed then the screen goes black and doesn't turn on after long pressing the power button it reboots. So I don't know what else to do I have tried kernels, operating systems re flashing reseting and nothing helps. No need to tel me to do resettings. Also my galaxy s2 i9100 chip has insane chip bug but I don't know if it has to do something with my problem.

[Q] samsung infuse 4g crashing just as it starts

Hi there everyone, recently signed up on here as xda seems to be the holy grail when it comes to all thing smartphone.
I'm fairly new to these type of phones and recently was given an infuse 4g that was suffering a power button problem.
The power button problem has been resolved with a new one and the phone was working fine for 3 / 4 weeks.
One day the phone shut down by itself and entered the boot loop syndrome. Factory clearing it hasnt seemed to do anything to resolve the problem as it continued to reboot continuosly.
I came across the thread about gtg ultimate unbrick guide in the developers forum and this seemed like a good way to go, get the phone all the way back to stock and then work from there.
Kies installed and all drivers installed fine. downloaded the gtg unbrick pack and followed the instructions line for line. Odin reports everything passed, took about 2:59 to complete.
phone rebooted and continued to do boot loop so went into recovery as stated and wiped data and cache and rebooted again.
phone is still stuck in some sort of boot loop, but it gets to display the 1st of the setup android phone screens, then just as you get a chance to select next to go onto the next screen, the phone reboots.
Any one have any idea what could be going wrong or as im fairly new to this, is there anything im doing or not doing right that is causing this.
The phone is an at&t infuse.
regards
Trevor
sound like an issue with stuck power button. it's a know issue with this model. google "infuse 4g boot loop" there's few youtube videos you can try.
tt33333 said:
sound like an issue with stuck power button. it's a know issue with this model. google "infuse 4g boot loop" there's few youtube videos you can try.
Click to expand...
Click to collapse
I've already replaced the power button with a new one, but the technician i use did say he will remove the power button completely to see if it does the same, just to rule that out
Trev
just redone the gtg flash and it boots into the os (ver2.2.1) and then within about 5 seconds turns off and reboots
can the new on off switch be faulty......im not so sure as in recovery mode, i can leave it on that screen forever and it doesnt attempt to reboot
Tried the one click repair with hemdial or what its called, updating thisnpost via a moto defy mini so excuse any typos.. The hemdiaOl just seemed to meas it up further. So got baxk into downliad mode with odin and reflashed to gtg brick recovery. Not fixed, still booting but at least the screen is now viewable.
To recover one of these phones, is there like a definitive guide as to what to do to first prepare one of these phones for recovery, ie, first, flash to this with cwm and then clear data, cache, dalcik etc. like an idiots fuide, i feel i may need one
Regards
Trev

[Q] HELP!! Sprint Galaxy S5

Hello everyone! I was sincerely hoping that someone would be able to help. I believe I messed up my phone beyond repair by trying to root it for the 2nd time. I rooted my phone in Sept 2014 and accidentally dropped it and broke the LCD (not the actual screen, but a piece inside of the phone). Samsung replaced the screen but they had to reset it so I lost the root. I wanted to try to root it again today. I already had all the tools; Odin, Superuser, and Philz Recovery. I put the phone into download mode, flashed Philz, and Odin said "Passed". When I put the phone into recovery mode, it didn't look like it did before. It just looked like the android stock recovery. I assumed (noob) that I may have done something wrong. So I tried flashing it again and it failed and was stuck in the download mode (Do not turn Target off). I waited approx 30 min and just said, "Screw it" and pulled the battery. I know stupid. Then I got the "Firmware upgrade encountered an issue message..." I did some research and many people on here and other android forums were telling others with somewhat of the same problem to download the stock rom. I'm currently downloading it but am worried it's going to do the same thing; "fail". I will update as soon as I try to flash the stock rom, but if anyone has other options, I'd so appreciate them.
Thanks so much for helping.....
Hedup34
P.s. I had the most up to date software for Sprint (maybe that was the problem)

Categories

Resources