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
I'm kind of stuck here. I'm not big into flashing roms and stuff.....but had issues with the one ROM I flashed 2 years agao so I thought I'd upgrade to CM10 finally. I flashed it properly using CWM and had a working rom....but forgot todarkside super wipe and to install the gapps.zip. So I thought I'd just do it over again. Everything seemed fine in the reinstallations of all 3.....but when I started the phone up it got stuck on a boot loop on the Cyanogen animation. No big deal....I'll just flash it again. Go into recovery mode.....wipe the data/cache.....it freezes on the cache. Try to flash the rom, cWM , the old rom, anything.......it gets stuck on the first "Installing....." . Not good. Can't do anything in CWM.
So I read a million webpages trying to figure out what to do next......someone else had to have had this problem. Seems like my only option is to go through Odin and flash it there. I make sure I get the USB drivers from Samsung and install those first. The installation goes through no problem......I reboot....and then try to plug in my phone via Download Mode. I make sure I use the USB cable that came with my phone and use a powered port on the back of my computer (XP btw). Windows recognizes it with its usual bull**** fanfare of 3 different notifications......"Found New Hardware!" then it says Found! "MSM8x60" then it says Windows failed to fully install new hardware. In the Device Manager its shown as the "Samsung Mobile USB CDC Composite Device" with the dreaded yellow exclamation mark on it. I tried uninstalling the drivers....rebooting.....and then reinstalling. No luck. Tried an older driver package.....no luck. I've spent hours trying every combination with no luck. I can't get Windows to recognize it....or more importantly.....Odin to recognize it. Any thoughts? Thanks.
Sorry for my English.
A lot of different things can happen if you are not using the correct version of recovery. The latest recovery doesn't always mean it will flash properly. For example I had to use TWRP 2.6 for 4.3 based ROM and had to roll back to TWRP 2.5 for some other versions of a rom. I don't know which version of CM you are using but maybe try TWRP or another version of CM.
Sent from my SGH-T989D using Tapatalk
Yeah....that makes sense. But how do I flash a different version of CWM? I can't get the phone detected by Odin.
Resolved.....tried a couple of other PCs....found one that worked
So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!
titostats said:
So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!
Click to expand...
Click to collapse
Download the latest kies from the samsung website.. and then open tools and then firmware update and initialization.. pull out the battery and type the model number and serial number kies asks.. follow the instructions.. your phone will be fine..
Sent from my GT-N7100
titostats said:
So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!
Click to expand...
Click to collapse
Try flashing a recovery for ur device with Odin, not a ROM, just flash twrp recovery with Odin, after u flash the recovery u will be able to access recovery and flash a stock ROM through twrp. I think what happened to u is when u flashed the update it tried to right over the unlocked bootloader which caused the soft brick, try flashing the recovery for ur device and if that doesn't work try the above posters way...
Sent from my Nexus 5 using XDA Premium 4 mobile app
I turned on my rooted Virgin Mobile Galaxy S 3 when it got stuck on the Samsung logo. The logo is animated but the phone will not progress past it. The phone is unable to boot into recovery or download mode; when I try to do so, the phone behaves as if I tried to simply turn it on normally. Samsung Kies is unable to connect to my phone but it does notice when I connect the phone to my computer. Odin also knows when the phone is connected. This occurred after using Odin for something I downloaded from http://forum.xda-developers.com/showthread.php?t=1739426.
asodiu said:
I was messing around with my rooted Virgin Mobile Galaxy S 3 when it got stuck on the Samsung logo. The logo is animated but the phone will not progress past it. The phone is unable to boot into recovery or download mode; when I try to do so, the phone behaves as if I tried to simply turn it on normally. Samsung Kies is unable to connect to my phone but it does notice when I connect the phone to my computer. Odin also knows when the phone is connected.
Click to expand...
Click to collapse
You are actually at the forum for the i747M/U variants of the SG3. To see if we can help you, however, you would need to provide more info ... You said you were doing stuff with your phone? Were you trying to flash a firmware or something? If so, what were you flashing and at what stage did your phone get stuck in the bootloop?
It's not a hard brick if your phone still makes some attempt at starting.
Larry2999 said:
You are actually at the forum for the i747M/U variants of the SG3. To see if we can help you, however, you would need to provide more info ... You said you were doing stuff with your phone? Were you trying to flash a firmware or something? If so, what were you flashing and at what stage did your phone get stuck in the bootloop?
It's not a hard brick if your phone still makes some attempt at starting.
Click to expand...
Click to collapse
I was flashing a download found in the link I have given (the newest Bell one). My phone had progressed past the first sign of the Samsung logo, past the screen saying "Samsung GALAXY S III" and past the animation with the sound before getting stuck on the next Samsung logo.
After flashing, did you boot to recovery and wipe data and cache?
audit13 said:
After flashing, did you boot to recovery and wipe data and cache?
Click to expand...
Click to collapse
As I have said, I am unable to boot to recovery or boot to download mode. I did not wipe data and cache.
Actually, after removing my battery for approximately forty minutes, I was able to boot into download mode. When I attempted to boot into recovery mode after turning on the phone normally (which resulted in the phone being unable to progress past the Samsung logo), I was once again only able to turn on the phone normally and get stuck on the logo.
asodiu said:
Actually, after removing my battery for approximately forty minutes, I was able to boot into download mode. When I attempted to boot into recovery mode after turning on the phone normally (which resulted in the phone being unable to progress past the Samsung logo), I was once again only able to turn on the phone normally and get stuck on the logo.
Click to expand...
Click to collapse
I recommend getting your hands on the Android SDK and using adb to boot into download and recovery modes. I got a water damaged d2att from friend a few months ago and the old volume down key doesn't work and using the command prompt and adb, you can get it to boot to whichever mode you want.
Sent from my SPH-L710 using Tapatalk
asodiu said:
I was flashing a download found in the link I have given (the newest Bell one). My phone had progressed past the first sign of the Samsung logo, past the screen saying "Samsung GALAXY S III" and past the animation with the sound before getting stuck on the next Samsung logo.
Click to expand...
Click to collapse
Virgin Mobile is a 'virtual' mobile network operator but ports mainly on the Sprint CDMA network. Unless your phone specifically had Bell firmware or was porting on Bell, flashing the Bell version would be wrong and could, nay would, cause a brick. Thankfully, though it appears to be only a soft brick and may be recoverable by re-flashing compatible firmware. Unlike Sprint and Virgin which are CDMA networks, Bell is GSM so I'd very much doubt that the firmware you were trying to flash was compatible with your phone. The fact that your phone is still trying to boot suggests that the bootloader is still intact but the system itself has been compromised. Can you remember what Android version your phone was on the last time it functioned normally? If so, I would suggest you visit Sammobile.com or androidfilehost.com and find the same version (or higher) for your phone and then flash to return to stock or near stock. You can always re-root afterwards or flash a custom ROM when your phone is back to working normally.
Since you can get into download mode, you can flash custom recovery in case the stock file you find is a zip file to be flashed via recovery. You should be able to get into recovery mode if you try the button combo again after you have flashed custom recovery via Odin. Otherwise, if it's a *.tar file, just flash directly with Odin.
Larry2999 said:
Virgin Mobile is a 'virtual' mobile network operator but ports mainly on the Sprint CDMA network. Unless your phone specifically had Bell firmware or was porting on Bell, flashing the Bell version would be wrong and could, nay would, cause a brick. Thankfully, though it appears to be only a soft brick and may be recoverable by re-flashing compatible firmware. Unlike Sprint and Virgin which are CDMA networks, Bell is GSM so I'd very much doubt that the firmware you were trying to flash was compatible with your phone. The fact that your phone is still trying to boot suggests that the bootloader is still intact but the system itself has been compromised. Can you remember what Android version your phone was on the last time it functioned normally? If so, I would suggest you visit Sammobile.com or androidfilehost.com and find the same version (or higher) for your phone and then flash to return to stock or near stock. You can always re-root afterwards or flash a custom ROM when your phone is back to working normally.
Since you can get into download mode, you can flash custom recovery in case the stock file you find is a zip file to be flashed via recovery. You should be able to get into recovery mode if you try the button combo again after you have flashed custom recovery via Odin. Otherwise, if it's a *.tar file, just flash directly with Odin.
Click to expand...
Click to collapse
I have successfully managed to flash stock filmware on my phone and now it is working fine. The post which I got the file that I attempted to flash stated that the Bell version would work with the Virgin Mobile phones. My Galaxy S 3 was running Android 4.3.
asodiu said:
I have successfully managed to flash stock filmware on my phone and now it is working fine. The post which I got the file that I attempted to flash stated that the Bell version would work with the Virgin Mobile phones. My Galaxy S 3 was running Android 4.3.
Click to expand...
Click to collapse
Glad to know it's working fine now. Unless the firmware for the 2 phone models have identical build numbers, I'd be surprised the post suggested that cross-flashing may be OK.
Where to start...
First, as a disclaimer, I may use language or terms that sound noobish. I have rooted and run custom ROMs on several devices in the past, however generally when I get a ROM I like I stick with it, so I'm not constantly tinkering. I've done my best to search and find solutions so please go easy on me.
17 days ago I was running stock 4.3 on my SGNII when the battery died. Upon charging I found I was stuck in bootloop and had a bad /efs mount. I searched and searched and spent around 15 hours trying this and that but to no avail. I finally threw my hands in the air and got ahold of Josh at mobiletechvideos and he was able to fix the efs mount issue. However, he left me in factory mode which required me to root to get out of, and once I did this I was unable to activate data on my carrier (Ting). I was so happy to have my phone "back" though that I used it like this for 4 or 5 days. I could get on wifi and I could call and send text messages. I had been off the grid so this felt like something I'd fix fully later.
Well I kept reading and found "fix" after "fix", flashed this and that and still no dice. FINALLY, last night, I found this thread: http://forum.xda-developers.com/show....php?t=2086769 which helped immensely. I was able to get TWRP flashed by unchecking the "auto-reboot" option in Odin and pulling the battery after the update took, and via TWRP I was able to install the ROM. I booted up, the device activated, I was running 4.1.2, I made and received some calls, the birds were chirping, the air was sweet...
I had struggled for so long and I had finally achieved success! Then, for seemingly no reason at all, I accepted an OTA update which bricked my Note2. Devastation.
The current state of things...
* Cannot get past the initial "Samsung Galaxy Note 2" screen
* Cannot boot into recovery
* I CAN get into dl mode,
* but, I CANNOT successfully flash anything. TWRP will flash like it took, but upon reboot I'm not able to boot into it. I'm also able to flash a ROM but it fails when it gets to sbin, and upon rebooting I'm greeted by the screen "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I try to use Kies it doesn't find the device. I've installed all of the most recent drivers and I'm running Kies as administrator. I select Tools > Emergency Firmware Recovery, THEN connect my device as instructed.
I'm at the apex of frustration. I beg thee to help!!
I have roughly the same situation. Was rooted and on an MK4 rom, battery ran down super fast yesterday and when charged, only get splash screen and slowly flashing blue light. I can get into Philz recovery but no matter what I try, no dice. Also can get into DL mode, but haven't been able to get anywhere. What the heck happened?
Well i bought another phone because of this problem of unknown baseband and 0 for everything in settings which didnt allow me to connect to sprint. Now when that happen it put me in safe mode . and i couldn't find a fix for months i ended up getting a lg g2 and let my note 2 collect dust. Well I'm using my note 2 and its up in running . my partition was messed up . if you have this issue which it sound like i can help. My phone was running fine then rebooted on its own and rebooted on safe mode with no signal
Sent from my SGH-M919 using XDA Premium 4 mobile app