Hello xda,
So I have a Note GT-N8010 and I was on Gnabo V5. Last week, I wanted to use my note, but I noticed it was shut off, I didnt shut it off, but it was, so I charged it because I thought it may be empty. The next morning it was fully charged so I put it on, but it didnt go further then the samsung logo. I tried everything, I have wiped everything via CWM (I can still acces that) and installed gnabo again, still the same problem. So I went into download mode and it was saying I have a N8000. I downloaded a N8010 firmware from Sammobile, but still it was keeping stuck at the samsung logo. So I tried the N8000 firmware and again the same. I downloaded different ones (N8000 & N8010) and searched the forums but I still don't know what to do...
Does someone know what I have to do in order to make it work?
Related
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.
Hi everybody, I´m kinda new in this and I´m really sad because my tablet won't boot anymore :crying:, I have a samsung galaxy 10.1 gt-n8010 wich I've been using for like a 2 years or so, everything was perfect(I was using omega rom v2.1 for more than a year!!!) until last week, I was recharging the battery of my tablet it was turned on , then later that day I realized that the tablet was on the boot logo (samsung galaxy 10.1), I tried to restart it but same thing happend, it got stuck at the boot logo, and when I tried to enter the recovery menu, only the letters teamwin are shown, but after 2-3 seconds it reboots and again got stuck at the logo that's how the pain and suffering started :crying::crying:
I´ve tried so many things to revive my tablet, wich I will list here;
I´ve flashed it (4.1.2 and 4.4.2 both stock roms and even the custom omega rom wich was the one I was using) using several versions of odin (v3.07 - v1.85 - v3.10.6) and odin says it passed succesfully, but then the problem remains
I´ve removed the battery and leave it just like that all day long, even I tried to turned it on without the battery (with direct power), but nothing it doesn't even turn on at all, no luck either.
I've flashed with some custom recoverys, (cwm,twrp), and again, no recovery.
I've tried to flashed it with several versions of pit files (I´m desperate and mad by now !!!) using several versions of roms and NOTHING even a file for a bootloader and again, no recovery, no boot no nothing it's just like if it wasn't flashing anything at all.
I'm sad, desperate, mad, angry, I wan´t my precious back !!!
Does anybody knows how to revive it ???
I have searched and searched and I've found nothing
Thanks in advance.
i have the same problem with my gt-n8000 :S:S:S:S someone help pls :S:S:S
Kindly get debrick.img for your phone to revive again
Even I have bricked my note 10.1 and past 1 week im searching solution for it.
Got this that is debrick.img which can be created by unbricked device only and can be used via sdcard to revive your bricked phone.
Can check this post - http://forum.xda-developers.com/showthread.php?t=2626147
Please help me also if someone can create a debrick.img for note 10.1 N8000 too.
Hello;
several days ago, suddenly my N8013 restarted. After rebooting, it stuck at Samsung logo, and I couldn't go to Recovery mode. I flashed an official rom from sammobile. the process was passed but my N8013 problem didn't solve.
What's the solution? Is it a hardware problem??
I don't know exactly what happened, mine did the same thing. I fiddled around with it enough that i got it to reload back to samsung 'new' but it never recovered where it was at the time it went haywire. I installed Kies on my PC and let it update the kernel to the latest stock. I had not rooted or anything up to that point. it just went kapuut. Now I am rooted and tried a couple ROMS, but so far I keep coming back to stock because I can't get something or another to work right (or at least the way I am used to)
I had my phone just sitting on a wireless charger this morning and had been there for about 15-30 minutes. I noticed it was rebooting, odd I thought? I took it off and then realized it was going into a boot loop. I gave it a soft reset and then it would turn on and stay on for about 10 seconds before boot looping again. I again gave it a soft reset after a couple loops and now it seems to totally dead, as the title implies.
No button combination has worked and I've held them all down for well over 30 seconds each. I've tried plugging it into my PC and haven't gotten any response that way. The blue LED is on so I know it's not dead...I think? To make matters worse, I bought this phone off Craigslist about 5 months ago and it's the Exynos version so I definitely can't get any kind of warranty on it. I'm hoping someone has had this problem and can help or just has some advice. Thanks everyone.
EDIT: To keep this updated, I have been able to get into Odin Mode and have tried to flash stock firmware. Odin says everything went fine but the phone hangs up at the Samsung Galaxy S7 logo. I'm unable to boot into recovery mode and I've even tried to reinstall TWRP with Odin and that has not worked.
Seen the LED only problem before, waiting for the battery to drain and the phone to turn off seems to be the only known cure atm
Once it does, connect the charger for 15 mins, then boot directly into recovery and clear caches to try fix the bootloop, possible it may need factory resetting / clean flash of stock ROM
Using the MicroUSB > USB white adapter, you may be able to connect a power hungry USB peripheral to the phone to drain the battery faster, I use a USB desktop fan, but some people report it not working when it is stuck in this LED loop and have just had to wait it out
Thanks for that advice, I'll let it drain over night. However, I have been able to get it to boot into Odin Mode and Odin v.3 recognized it. I flashed the stock firmware but upon rebooting nothing happened and now it gets stuck at the Samsung logo screen. I can still get it back into Odin mode, which I believe will be the fastest way to kill the battery, but I find it odd that I can get into that but not recovery? I am rooted and have TWRP installed, if that matters at all.
If you can get into Download (ODIN) mode, then letting the battery drain probably won't help, that only seems to help when the phone is completely stuck with nothing but the LED working
Make sure you flash CSC (Not HOME_CSC) along with the other 3 sections of the ROM, using ODIN 3.12.3, that should factory reset the phone after the flash
If you successfully flashed stock with ODIN already, you are no longer rooted and do not have TWRP installed, flashing stock with ODIN replaces all that with stock
I updated Odin and once again tried to flash the 4 parts, making sure I used the right CSC file, but I'm still getting hung up at the Samsung Galaxy S7 logo. Do you have a suggestion as to which region's firmware I should use? I have been trying the Australia one from SamMobile's site.
EDIT: And to clarify, I have the G930FD(the duos one).
jonny727272 said:
I updated Odin and once again tried to flash the 4 parts, making sure I used the right CSC file, but I'm still getting hung up at the Samsung Galaxy S7 logo. Do you have a suggestion as to which region's firmware I should use? I have been trying the Australia one from SamMobile's site.
EDIT: And to clarify, I have the G930FD(the duos one).
Click to expand...
Click to collapse
Any region would work, and the F firmware works for the FD too
Hi Guys,
So the issue seems to be straightforward and I read many threads about it, but none of them actually solve my problem.
My S6 is locked to Orange Poland (which is currently running 6.0.1 Android). I wanted to flash unbranded Marshmallow rom but that did not go well and in the process of flashing Odin returned an error (Complete(Write) operation failed). That's the way my phone became bricked. I tried to reflash this rom several times (while changing ODIN versions and also I tried single AP as well as 4 files + PIT). None of this worked. So I decided to go back to the branded rom—exactly the same as it was before.
Odin this time didn't show any fail messages and the phone actually started booting up. And here is my problem, it is stuck on the Samsung logo. I tried going to recovery mode, wipe cache and then factory reset but it still cannot go through Samsung logo.
My phone was never rooted. I have up to date samsung usb drivers. I tried SmartSwitch but it fails to recover the phone every time.
Do you kind people have any ideas?
Hi again,
Just a quick update from me. I finally managed to revive my phone. It seems that the bootloop was caused by the low battery (actually 0%, while being connected to PC). Once I charged the phone to 100%, it miraculously booted up and went to the setup wizard. I have no idea if the low battery had an effect on it, but once I charged it, the phone started to work properly.
In the end, I flashed back the stock rom with Orange Poland brand. The rom consisted of 4 files + PIT file. I used Odin3_v3.12.3.
Maybe this will help someone
axapies said:
Hi again,
Just a quick update from me. I finally managed to revive my phone. It seems that the bootloop was caused by the low battery (actually 0%, while being connected to PC). Once I charged the phone to 100%, it miraculously booted up and went to the setup wizard. I have no idea if the low battery had an effect on it, but once I charged it, the phone started to work properly.
In the end, I flashed back the stock rom with Orange Poland brand. The rom consisted of 4 files + PIT file. I used Odin3_v3.12.3.
Maybe this will help someone
Click to expand...
Click to collapse
Thats why you should always charge your phone to at least 70% before doing any flash :good: