Related
So my phone was working perfectly fine until two days ago it rebooted itself with no apparent reason. After that the phone stayed stuck on boot screen (Where it says "samsung galaxy note II GT-N7100).
I can't get into recovery mode, but can get into download mode.
I tried about anything to fix this but nothing seemed to help and I'm starting to lose hope. I really wish you guys can help me fix this, because I'm having trouble facing the fact that my phone can just die on me and i have nothing to do about it (I have no insurance on the device).
Thanks in advance to anyone who wishes to help!
yotiXD said:
So my phone was working perfectly fine until two days ago it rebooted itself with no apparent reason. After that the phone stayed stuck on boot screen (Where it says "samsung galaxy note II GT-N7100).
I can't get into recovery mode, but can get into download mode.
I tried about anything to fix this but nothing seemed to help and I'm starting to lose hope. I really wish you guys can help me fix this, because I'm having trouble facing the fact that my phone can just die on me and i have nothing to do about it (I have no insurance on the device).
Thanks in advance to anyone who wishes to help!
Click to expand...
Click to collapse
This just happened to my GT-N7105 too....
....for the second time! lol.
First time i solved it by using Odin, flashed CWM then checking to see if CWM could mount my SDcard, i loaded up a ROM in it and reboot into CWM and installed the rom from there. SIMPLE!
This time, my CWM works but it can't mount my SD-CARD... :crying:
So, i'm just gonna flash in another rom with Ordin and see what happens! lol.
If you need help using Odin, try this guide:
galaxynote2root.com/galaxy-note-2-tutorials/how-to-unrootunbrick-galaxy-note-2-with-stock-firmware/
Granted it's a bit old, but it might still work (im using this guide too!) Only difference is that you'll have to flash in CWM instead of a ROM and we should use latest ordin 3.7.
So good luck to you and me! :good::laugh:
yotiXD said:
So my phone was working perfectly fine until two days ago it rebooted itself with no apparent reason. After that the phone stayed stuck on boot screen (Where it says "samsung galaxy note II GT-N7100).
I can't get into recovery mode, but can get into download mode.
I tried about anything to fix this but nothing seemed to help and I'm starting to lose hope. I really wish you guys can help me fix this, because I'm having trouble facing the fact that my phone can just die on me and i have nothing to do about it (I have no insurance on the device).
Thanks in advance to anyone who wishes to help!
Click to expand...
Click to collapse
well just flash philz recoverry using odin in download mode and then enter to recovery wipe data ,cache and u are good to go
flash the .tar file from here http://forum.xda-developers.com/showthread.php?t=2028103
I can flash this recovery, odin shows pass but i still can't get into recovery mode
shhbz said:
well just flash philz recoverry using odin in download mode and then enter to recovery wipe data ,cache and u are good to go
flash the .tar file from here http://forum.xda-developers.com/showthread.php?t=2028103
Click to expand...
Click to collapse
I am not able to go into download mode. Now the screen just hangs on "Galaxy Note II" logo. Even if I switch off the phone and connect it for charging, all it displays is "Galaxy Note II" logo instead of BIG Battery Charging Icon. Now am not able to boot into android also. Any Help?
darthvedor said:
I am not able to go into download mode. Now the screen just hangs on "Galaxy Note II" logo. Even if I switch off the phone and connect it for charging, all it displays is "Galaxy Note II" logo instead of BIG Battery Charging Icon. Now am not able to boot into android also. Any Help?
Click to expand...
Click to collapse
I've got the same stupid problem. I have the Samsung Galaxy Note II logo. Can't get to recovery, I can get to download. I've flashed stock at least 5 times now, even tried cwm. Odin says successful/pass, phone never boots past this initial screen. What is going on?
cameron213 said:
I've got the same stupid problem. I have the Samsung Galaxy Note II logo. Can't get to recovery, I can get to download. I've flashed stock at least 5 times now, even tried cwm. Odin says successful/pass, phone never boots past this initial screen. What is going on?
Click to expand...
Click to collapse
you might try to download the stock rom from sammobile flash it with odin，then only redo root and flash custom Rom
thats what i did when it stuck at note 2 screen and wont boot into system
kw5129 said:
you might try to download the stock rom from sammobile flash it with odin，then only redo root and flash custom Rom
thats what i did when it stuck at note 2 screen and wont boot into system
Click to expand...
Click to collapse
Like my post says, I have downloaded the stock rom, used odin to flash. Odin says successful/passed...Phone restarts only to get stuck at the Samsung Galaxy Note II screen. Won't go past this screen. I cannot get into recovery mode, only download mode.
have you check all the setting in your Odin is it correct?
Sent from my GT-N7100 using xda app-developers app
I had the same problem wit my Samsung Tab 7. I rolled back to stock rom and modem with odin. Thats how i solved...
same here but
Same thing is happening to me right now, except that I can enter recovery mode.
I did one factory reset, but still nothing
I just had the same thing happen i managed to reflash stock rom via odin to recover my phone again but then odin is acting wierd wont connect all the time in download mode.
hi guys, so mine isnt an n7100, but woah is it the same exact problem!!! i've been searching all over the internet just to find someone with THIS particular issue....that i've been having for three days now. so....as i'm still working on it, has anyone else been able to solve yet? thanks in advance guys!!!
kw5129 said:
you might try to download the stock rom from sammobile flash it with odin，then only redo root and flash custom Rom
thats what i did when it stuck at note 2 screen and wont boot into system
Click to expand...
Click to collapse
Press vol. up + menu key and then Power key if your phone is stuck on boot screen for 4~8sec, and don't leave the button until your phone get restarted and for ~3 secs after.
MADD MILK said:
hi guys, so mine isnt an n7100, but woah is it the same exact problem!!! i've been searching all over the internet just to find someone with THIS particular issue....that i've been having for three days now. so....as i'm still working on it, has anyone else been able to solve yet? thanks in advance guys!!!
Click to expand...
Click to collapse
Has anyone found a fix for this, im using my gnex cause my n7105 is bricked due to this,
someone help us please.
Just change the battery. it worked for me :good:
My N7100 got bricked spontaneously. I was on stock rooted rom. I can boot it to download mode and philz recovery, but not Android. I tried odin, flash was successful but still cant boot. I was able to push via adb, but installation failed. Can i still recover it? Plz help me.
Sent from my Nexus 5 using XDA Free mobile app
yeah, this just happened to my moms note 2,
we were outside and she was using her phone normally until it suddenly started to reboot repeatedly.
i knew it's not her firmware nor her kernel cause they're all the official ones,
luckily my father has a note 1 which uses a battery of the same size, so i tried it's battery and it worked, so i put back the original battery and wala,
worked like a charm
have you tried to install custom recovery? CWM or TWRP or Philz and then install a custom rom from the recovery?
If someone can't go to download mode there is a micro usb callesd usb jig(you find it on ebay) that helps you go into download mode.
Oh my God!!! I inserted the spare battery that i had into my "bricked" note 2... And it got a life.. I can't understand the logic behind this.. Its a topic worth research!!
BTW, thanks to rZZ87
Sent from my Nexus 5 using XDA Free mobile app
Device: Samsung Galaxy Note 8.0 WiFi Tablet ((GT-N5110))
-+-+-+-+-+-+-+-
Last night I started to attempt to return my GT-N5110 to the complete Stock ROM and everything however after spending HOURS looking for the Stock ROM files, I decided to try downloading the ROM directly from the Note 8.0 Toolkit. After it finished downloading and I installed it via ODIN like the toolkit asked, I tried to turn my tablet on and now it won't boot past the Samsung logo boot screen.
If someone could please give me the URL of the correct files needed as well as to a walk-through webpage so that I can fix this annoying problem and get my Note 8 up and running again, I'd greatly appreciate it.
Unfortunately I have been unable to find anything that even looks like it could work on my GT-N5110 on here so I have been rather hesitant to try using the stock files for a different model of the Note 8.0 rather than whichever is needed for the WiFi model. I've finally thrown in the towel and am asking someone, ANYONE, for some help.
Thanks guys!
you can get mostly all of stock firmware on sammobile.com
http://www.sammobile.com/firmwares/2/
Update
I downloaded the firmware from that site and followed the instructions that were provided with the firmware download however I'm still stuck at the Samsung boot screen. I tried leaving it alone for a while since I know that after installing a gapps file, the first boot may take a little bit but it stays on the same screen.
There has to be something I'm missing because I've never had this much trouble with any of my devices before. I thought to try an Emergency Firmware Restoration using Kies but my tablet doesnt show as being connected in Kies.
Anyone know what I'm unknowingly doing wrong?
Get into stock recovery and factory reset, should clear up the being stuck at Samsung boot.
CKrzacz said:
Get into stock recovery and factory reset, should clear up the being stuck at Samsung boot.
Click to expand...
Click to collapse
+1
CKrzacz said:
Get into stock recovery and factory reset, should clear up the being stuck at Samsung boot.
Click to expand...
Click to collapse
^^^^^This^^^^^
OR
Check this post out, http://forum.xda-developers.com/showthread.php?t=2289441 if CKrzacz's tip didn't work.
Hello guys
I just want to say i'm no where near an expert on this, and i feel i have tried to fix this issue but made it way worse in the process so please be gentle.
This morning i woke to my Samsung Note 2 N7100 just hanging on the samsung start up screen. Tried all the normal things, taking bat out, restarting many times etc. No luck, just kept hitting the samsung screen and freezing.
After some goggling i found my way to the Recovery screen (power+vol up+home) but when it was loading there was a lot of Red Error messages. It loaded the options screen and i tried to do a factory reset. A lot more error messages to basically then say failed. Tired it a few times and even tried to clear the cache but kept failing.
So i tried loading it into Kies, which didn't connect to the phone so i couldn't reinstall the software.
So i decided maybe i need to flash the phone. I downloaded a stock Rom for the phone (i was on Kitkat so found that version) Used odin and half way through the install it came up failed.
Since then the phone only displays the "Fireware upgrade encountered an issue. Please select recovery mode in Kies"
So i went back to Kies but still couldn't find the phone. It also won't let me go back into recovery mode, only into download mode.
I thought maybe i'd give the flashing another go but this time when i flashed it, it just hangs trying to find Pit but eventually fails saying no Pit.
From research it appears that the partition is buggered. All the research i've done seems to say stay away from messing with the partition. some people say its Emmc thats gone and its game over but others say there is hope still.
I can still access the Download menu and the product name is still GTn7100, Binary still samsung official so i am holding out hope there is some life left in it. I'm on my last legs now so open to all offers for solutions. Please assist if you can
Thank you in advance
Andy
If you're able to get in download mode.. Maybe try flashing a custom recovery (TWRP) which you could try full format in it then install a ROM using it.. Also, maybe trying to use a CM based one? Though you might need a external SD card to move files from PC to your phone.
I don't know if this would work, but try it.
Sent from my Galaxy Note II using Tapatalk
Hello all,
I've got a Tab 3 7.0 T210R stuck on the Samsung logo with pulsing blue background. I've read through several Samsung boot loop help threads as well as the general Loop noob helper but haven't found a fix yet.
For my stuck T210R, What I've done & can do:
Was rooted with a "patched" stock UK ROM from last March [sorry, don't recall which]
Was running fine until after I tried to install from Play the TWRP Manager, I obviously did something bad! like select wrong device maybe
I can get into Philz, TWRP, & use Odin
I don't have a recovery back up [i really don't care about restoring back to anything - just want it to work, clean slate, ya know]
Tried a couple of latest ROM's through Philz and a stock ROM XAC-T210RUEAMK1-20131122134958.zip though ODIN. They seemed to be successful but I still can't get past Samsung logo
I've tried these ROMS that seem to load but ixna on successful boot afterwards:
ODIN: KIES_HOME_T210RUEAMK1_T210RXACAMK1_1304745_REV00_user_low_ship.tar.md5
Philz: Stock.rooted.deodexed.T210R.zip
Philz: TAB3-T210-HASSAN-ROM-V1.0-kitkat-4.4.2-Aroma-Mods-all Languages.zip
Philz: cm-10.1-20131209(1)-UNOFFICIAL-lt02wifiue.mine.zip
What's killing me is that loading new or stock ROM's SEEM to work - no errors or anything obviously indicative that I'll still be boot looping as soon as I restart. I'm quite desperate and thinking I'm truly bricked.
I haven't yet tried using ADB but if I can use ODIN and TWRP or Philz, will ADB do anything better than what I've already done? I haven't tried anything with the kernel as I can't really understand what to do there. I read and read and read the kernel threads but with my experience its really not as straight forward as rooting or flashing a ROM or software, and I could conceivably screw up worse! I'm mildly experienced at following guides to have rooted and ROM loaded a 1st gen Kindle Fire, Samsung SII skyrocket, S4, Tab 2 7.0, Tab 3 7.0.
No replies or interest? Please help
I'm I in the wrong forum? Did I offend someone? Could really use some input, please.
Any one seen this before? If you've any experience LOSING this battle, please speak up and I'll know to just resign to now owning a pretty white Samsung brick.
Boot to customed recovery under wipe choose format this will zero all partitions then redo
thanks!
andynroid said:
Boot to customed recovery under wipe choose format this will zero all partitions then redo
Click to expand...
Click to collapse
if i could find the "thanks" button I'd use it.
I'm traveling now but definitely try your solution. By "redo" I presume you mean load a ROM. When I wipe I also presume I'll still have custom recovery? I should still be able to ODIN, too, if needed?
thanks again
Yes exactly recovery will not go away once you have formatted the partitions you can now flash a new customed ROM or reflash original FW using Odin..Cheers
Hey buddy wanted to know if you ever found a solution for your issue? I am in the same bind you were in. Can you help guide me. I tried installing the same files you did and to no avail. I bought a Tab 3 T210R from eBay that was stuck in boot loop, I am assuming that it isn't rooted as when I would I went into download mode, it said the firmware was official.
Hello there, all xda members.
I got Ace 2 to fix from my friend. He doesnt know exactly why did the phone becoming stuck on bootlogo. Maybe messing up with flashing GB or JB. or maybe wrong terminal command.
Ace 2 Condition :
- Its unable to pass boot logo samsung galaxy ace 2
- Its unable to enter recovery mode
- Its able to enter download mode, and its custom binary download : No, Current binary : Samsung official
Here all the thing that i have tried to fix the phone :
1. Flashing the phone with Russian Gingerbread with 3 files, Pit, CSC, and PDA. But it still stuck on bootlogo and unable to enter stock recovery. it shows succeed though on Odin, but it can't boot.
2. Flashing the phone with Latest Jelly bean, with Jelly bean pit file. Odin displaying succeed, but it doesnt boot either.
Can someone help me how to solve this problem?
Is there a condition where phone completely unable to recover from hardbrick such as stuck on bootlogo, but still able to enter download mode?
I'm going to download jelly bean mb2 or mb4 which include pit and csc from jelly bean and try to reflash it. Hope it gonna work.
Thanks for any help.
Anyone here to help me?
@ChronoMonochrome , maybe you've experienced something like this and able to resolve the problem.
The phone can't boot at all. and im a little frustrated here. I've already tried a 3 parted firmware MB4, and it doesnt work either. Tried to flash chrono 4.3 cwm through odin and it doesnt work either.
And if it really doesnt have a solution, maybe i'll just give it up. And doesnt continue researching to fix this phone. Thanks
maybe another devs that able to fix this. @ace2nutzer @fluffi444 or anyone??
It got the same case. Successfull flashing, but still doesnt boot, it just like flashing is fail. or it just like it reverted the way it was before flashing. Your help is very appreciated.
riyosakura said:
maybe another devs that able to fix this. @ace2nutzer @fluffi444 or anyone??
Click to expand...
Click to collapse
Very strange. And more strange is that several people have this "only boot to logo / only downloadmode issue"
Up to now I have no Idea - I asume that ADB is not working, because of missing recovery mode? With ADB there are plenty of possibilities.
An complete Factory reset could be helpfull - But how to do it out of downloadmode ?! Don't know.
Up to now I didn't had a Phone with this behaviour for repair at home. If it would be reproducible how this all happens, I would bring my phone to this state to find out how to repair it (riff box here - so dead ACE 2 is not a problem) - But even this is unclear - Every report regarding this said only "suddenly" "without any reason" "flashed this or that" - But no exact infomation what happend acctually.
I'm out of Ideas. Sorry!
Thanks for answering.
I dont know if i have to give up already or not. But i'll try to flash it with another pc and data cable. Maybe it gonna work.
riyosakura said:
Thanks for answering.
I dont know if i have to give up already or not. But i'll try to flash it with another pc and data cable. Maybe it gonna work.
Click to expand...
Click to collapse
Another try:
Flash with ODIN Ace2Nutzers Stock Kernel (search on FTP)
Do not let the Phone boot
After Flashing pull usb und press drictly the 3 keys to get into Rec. Mode
riyosakura said:
Anyone here to help me?
@ChronoMonochrome , maybe you've experienced something like this and able to resolve the problem.
The phone can't boot at all. and im a little frustrated here. I've already tried a 3 parted firmware MB4, and it doesnt work either. Tried to flash chrono 4.3 cwm through odin and it doesnt work either.
Click to expand...
Click to collapse
No, I haven't had the phone in such condition as described above. But I have heard that any odin-flashable file that's wrongly flashed via "Phone" entry can lead brick which is similar to this. I remember only one case - one user from 4pda has flashed some file via odin, wrongly putting file to the "phone", and wasn't able to restore it anyhow - but he also had some brick on GPIO side - vol.up worked like vol.down, and the real vol.down didn't work at all. I don't know however, what memory partitions / any devices capable of storing data would be messed after this operation, and whether it's reparable at all. I mentioned devices, that can also store data, I know only that touchscreen has small memory for its firmware(that what I had broke one day in the past after accidental firmware change in the kernel) - but maybe some other devices also has it?!
There are also some chances that it's dead flash memory - chances are pretty small, but should also be taken into account.