Related
i just updated my galaxy note and when i rebooted its not getting passed the note N 7000 screen can any one help me with that? i had previously updated it to XXLA3 and it was working fine!
noteN7000 said:
i just updated my galaxy note and when i rebooted its not getting passed the note N 7000 screen can any one help me with that? i had previously updated it to XXLA3 and it was working fine!
Click to expand...
Click to collapse
Was it an OTA or KIES update u did?
U rooted and on stock or any custom rom ?
If not rooted....then u can still try hitting volume up + home + power buttons all at the same time and holding them pressed till the time the same N7000 logo shows up and leave the buttons then. The phone should boot into stock recovery. Now try clearing the cache there if the option is available. If nothing works then either wipe/format your note (warning all data will be lost except the internal/external sd card) or reflash the firmware through PC odin using Dr Ketan's guide from the stickies post in the development section of note forum here on xda.
How did you update you phone? Via kies?
i am new to all these things! i haven't rooted my phone as well! jst went on to "about phone" and update. after which it didn't started. tried the vol. up home key and power didn't worked...
So it was an OTA update. Did you tried pressing volume down + home + power button for booting into download mode?
ya tried that as well but it said custom OS can cause critical problems so canceled it...
noteN7000 said:
ya tried that as well but it said custom OS can cause critical problems so canceled it...
Click to expand...
Click to collapse
vol up+home+power should work. Try that again and keep pressing them till the time the n7000 logo shows up and leave them immediately after it.
if u are not able to get into recovery then the only way for you is to flash via odin.
Refer the guide and roms here-
http://forum.xda-developers.com/showthread.php?t=1424997
does that mean my phone will be rooted?
noteN7000 said:
does that mean my phone will be rooted?
Click to expand...
Click to collapse
No. You just flash the latest firmware you want from the PC odin. The phone will be stock rom and wont be rooted unless you run the rooting tool.
Remember to read the full post !
Hi, My note is stuck at boot screen after the official OTA update. I tried googling but most seems to pertain to Rooted/flashed phones.
Mine is a new note which has not been rooted at all in the past. I downloaded to OTA update and it has been stuck at the bootscreen for the past few hours.
Any help appreciated!
1. Try pulling out the battery for a few minutes.
2. Boot into recovery mode and wipe cache and dalvik cache.
should i also wipe the data/factory reset in recovery mode?
No. God forbid, then you might end up with a superbrick
Thanks for your help
Sent from my GT-N7000 using XDA
Unable to enter recovery mode
Hey I got similar problem, my phone gets stuck at Samsung logo screen. I am unable to enter recovery mode. When it shows android update screen after pressing recovery mode combination, my phone restarts.
Is there anyway I can get back normal mode without losing data on phone
indianphoenix said:
Hey I got similar problem, my phone gets stuck at Samsung logo screen. I am unable to enter recovery mode. When it shows android update screen after pressing recovery mode combination, my phone restarts.
Is there anyway I can get back normal mode without losing data on phone
Click to expand...
Click to collapse
Keep them pressed for 3 seconds more then you end up to recovery. They need to be pressed while booting the device from reboot or off state, then you will end up in recovery or download mode.
Sent from my GT-N7000 using Tapatalk 2
Yesterday, I received an OTA on my galaxy note and now it is also stuck in boot screen with the breathing samsung logo.
I tried to go into recovery mode using the 3 button combo, but it wouldnt enter into recovery mode. I get the green android logo with wire mesh and the phone reboots.
Can someone help me to boot my phone?
Got mine backup and running after OTA update gave me Samsung logo freeze issue
So after the 7MB OTA stability patch mine too was stuck on samsung logo.
Kies wouldn't recover it and putting into download mode or recovery mode didn't help. I too tried to go into recovery mode using the 3 button combo, but it wouldnt enter into recovery mode. I get the green android logo with wire mesh and the phone reboots but i didn't at the time try for 3 more seconds.
I then used ODIN and applied a downloaded Aussie Gingerbread ROM as i couldn't find Aussie ICS ROM. With my plan to do a Kies/wifi update to ICS. This caused acore and other processes to crash every few seconds. I then did a factory reset which got it stable and then tried to update to ICS but the phone said there were no updates available. Then I applied the international ICS using ODIN so i'm back were i was two days ago before the stupid 7MB patch.
Unfortunately, I don't think i can get anymore OTA updates but after the 7MB one i don't think i want to.
Long story short i think you should be able to go into recovery mode do a factory reset and it should be OK.
bigwalabig said:
Hi, My note is stuck at boot screen after the official OTA update. I tried googling but most seems to pertain to Rooted/flashed phones.
Mine is a new note which has not been rooted at all in the past. I downloaded to OTA update and it has been stuck at the bootscreen for the past few hours.
Any help appreciated!
Click to expand...
Click to collapse
U can download stock ics and flash it through pc odin. Cheers.
Press 3 combo button to enter download mode and plug ur cable data once u have open pc odin with downloaded rom on pda :beer:
Sent from my GT-N7000 using xda premium
ODIN voids warranty?
I have the same issue after receiving 7MB OTA update. I am unable to go into recovery mode(same green robot and wire mesh etc...), so i am going to use ODIN method... but will flashing stock ROM using ODIN void my warranty?? I am not rooted.
Thanks.
vinit.the.one said:
I have the same issue after receiving 7MB OTA update. I am unable to go into recovery mode(same green robot and wire mesh etc...), so i am going to use ODIN method... but will flashing stock ROM using ODIN void my warranty?? I am not rooted.
Thanks.
Click to expand...
Click to collapse
To flash yoi have to root...which voids warranty
But not to worry
Check the videos in my sig...it will explain how to succesfully unroot and get back to normal :good:
Rulinglionadi said:
To flash yoi have to root...which voids warranty
But not to worry
Check the videos in my sig...it will explain how to succesfully unroot and get back to normal :good:
Click to expand...
Click to collapse
Thanks.... but this is my aunt's phone, so rooting is not an option. I use HTC Hero... and we have RUU which we run on the PC and everything is restored to stock.... it removes root if you have it and also runs without root. Is there anything similar for samsung devices?
Also, now I am considering going for warranty repair... didnt want to do that at first as i have a really bad experience with HTC service centers... now lets see what samsung does..!!
Same problem here please find a fix!!
Rulinglionadi said:
To flash yoi have to root...which voids warranty
But not to worry
Check the videos in my sig...it will explain how to succesfully unroot and get back to normal :good:
Click to expand...
Click to collapse
You don't need root to flash stock with PC Odin, and flashing any stock does not affect warranty. To use Odin you need phone in download mode (vol down, home and power until reboot into download)
Sent from my GT-N7000 using xda premium
SOLVED!
vinit.the.one said:
I have the same issue after receiving 7MB OTA update. I am unable to go into recovery mode(same green robot and wire mesh etc...), so i am going to use ODIN method... but will flashing stock ROM using ODIN void my warranty?? I am not rooted.
Thanks.
Click to expand...
Click to collapse
Just flash it using the same os version you already have installed in my case I had the same problem with this little ota update and I've just flash it with the same ics version that was installed and my phone was back with all my stuff and rooted... once you finish doing the re flash you'll get an on screen message saying "Fail to update try using samsung kies on your computer" or something like that...
Thanks... but I went for warranty repair .. and I got it back in 2 hours..... unfortunately I lost all my data .. even on external partition. Now it is on ICS and still I have a notification for available update ... which I wont do.
Anyone has had success with that update?
Sent from my Hero using xda app-developers app
hello I have an i9305t was on official 4.1.1 upgraded to official 4.3 with odin .3.09 and it gets stuck on boot on the blue white pulsating Samsung logo. tried 4.1.2 fails tried 4.1.1 phone works fine, just cant upgrade to any new firmware at all. help would be great
vnholden said:
hello I have an i9305t was on official 4.1.1 upgraded to official 4.3 with odin .3.09 and it gets stuck on boot on the blue white pulsating Samsung logo. tried 4.1.2 fails tried 4.1.1 phone works fine, just cant upgrade to any new firmware at all. help would be great
Click to expand...
Click to collapse
To prevent you from being stuck onto the Samsung boot logo, you should wipe cache and wipe data from recovery after flashing the firmware. To do so follow these instructions.
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
After entering recovery, you should see the options, to wipe cache and wipe data. wipe them. Hope you did a backup as you will use most of you files.
LucasBass said:
To prevent you from being stuck onto the Samsung boot logo, you should wipe cache and wipe data from recovery after flashing the firmware. To do so follow these instructions.
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
After entering recovery, you should see the options, to wipe cache and wipe data. wipe them. Hope you did a backup as you will use most of you files.
Click to expand...
Click to collapse
thank for the reply I should of put that ive tried all that. doesn't work, just stays on that logo only way past it is to install 4.1.1.
Does your phone's IMEI (baseband) show up on 4.1.1 ?
dashing_9508 said:
Does your phone's IMEI (baseband) show up on 4.1.1 ?
Click to expand...
Click to collapse
yeah but only if I use perseus kernel. with out it I have no coverage aswell.
so has anyone got any ideas. much appreciated
vnholden said:
so has anyone got any ideas. much appreciated
Click to expand...
Click to collapse
I think you could try installing Stock 4.3 with Heimdall.
http://forum.xda-developers.com/showthread.php?t=1127419
viktorak said:
I think you could try installing Stock 4.3 with Heimdall.
http://forum.xda-developers.com/showthread.php?t=1127419
Click to expand...
Click to collapse
daaam was hoping that would of worked but no unfortunately. ready to throw this thing at the wall.
still having problems updating to any new firmware be it official or custom roms. nothing works, I tried cm11 all went well till the loading screen just cant get past that point. but 4.1.1 works without any problems.
I think you could try to use Triangle away,to reset flash counter and then use KIES recovery to reflash 4.1.1 stock.Then try to update to 4.1.2 or 4.3.
viktorak said:
I think you could try to use Triangle away,to reset flash counter and then use KIES recovery to reflash 4.1.1 stock.Then try to update to 4.1.2 or 4.3.
Click to expand...
Click to collapse
cheers mate ill give it a whirl but I don't think it will work. ill give you a big thanks anyway.
viktorak said:
I think you could try to use Triangle away,to reset flash counter and then use KIES recovery to reflash 4.1.1 stock.Then try to update to 4.1.2 or 4.3.
Click to expand...
Click to collapse
ok I tried what you recommended, but as I thought stuck on Samsung writing blue led light stays on. only one that worked was 4.1.1. I wonder if a modified binary or kernel is causing it. its how I got the phone so I don't no its history.
Well, let's try to flash true Mobile Odin pro a stock Samsung firmware.You need to be root.See if we're lucky.
Here you have the XDA Thread:http://forum.xda-developers.com/showthread.php?t=1347899
viktorak said:
Well, let's try to flash true Mobile Odin pro a stock Samsung firmware.You need to be root.See if we're lucky.
Here you have the XDA Thread:http://forum.xda-developers.com/showthread.php?t=1347899
Click to expand...
Click to collapse
thanks for trying to help I really appreciate it. as for mobile odin it will have to wait no funds on my card at moment. but I did manage to install a custom rom its 4.3 but I have no network coverage. in about settings unknown baseband.
this is the rom im using.
http://forum.xda-developers.com/gal...-amcha-rom-v5-00-simply-customizable-t2619670
perseus kernel stops the phone from not booting. that gives me my baseband. atleast ive got some where with it just need network to work now.
p.s sorry if im not making much sense but its beer drinking time for me. lol
You have to check the IMEI of your phone.If you have lost your IMEI see this thread:http://forum.xda-developers.com/gal...warning-guide-backup-restore-imei-nv-t1946915
I've searched around the forum and haven't hit a solution, so sorry if it's out there.
So, I have a Galaxy S4 Active (i537) ATT. I was given to me in a bootlooping state, and if I fix it I can keep the device.
What I have done to the moment:
Flashed every stock rom found in the forum with Odin (No luck on the device booting)
What the device does:
It shows the samsung splash, and restarts over and over, sometimes it doesn't even manage to get to the samsung splash.
Attempting to boot into recover mode produces the same result, it says booting recovery and it restarts.
Info on Download mode:
Product name: SGH-i537
Current Binary: Samsung official
System Status: Official
Knox kernel lock: 0xfffffffc
Knox kernel warranty void: 0xfffffffc
CSB-CONFIG-LSB: 0x30
Write protection: enable
emmc burst mode enabled
I'm new to samsung devices, so I hope someone can help me out here.
Thanks in advanced!
rguilamo said:
I've searched around the forum and haven't hit a solution, so sorry if it's out there.
So, I have a Galaxy S4 Active (i537) ATT. I was given to me in a bootlooping state, and if I fix it I can keep the device.
What I have done to the moment:
Flashed every stock rom found in the forum with Odin (No luck on the device booting)
What the device does:
It shows the samsung splash, and restarts over and over, sometimes it doesn't even manage to get to the samsung splash.
Attempting to boot into recover mode produces the same result, it says booting recovery and it restarts.
Info on Download mode:
Product name: SGH-i537
Current Binary: Samsung official
System Status: Official
Knox kernel lock: 0xfffffffc
Knox kernel warranty void: 0xfffffffc
CSB-CONFIG-LSB: 0x30
Write protection: enable
emmc burst mode enabled
I'm new to samsung devices, so I hope someone can help me out here.
Thanks in advanced!
Click to expand...
Click to collapse
It's hard to say what is wrong, but it sounds like you definitely need to flash stock firmware. One question, is it definitely the AT&T version (with the AT&T logo on the back cover) or could it be the Mexican version?
If it's the AT&T version, then flash the NE3 firmware by following the instructions in i537 Firmware Install Guide. The OP of the guide will ask you which firmware you're currently on, but for NE3 it doesn't matter which one you select because all the instructions will be the same. Make sure you don't have a corrupted download by checking the MD5 of the file you downloaded against the MD5 posted in the i537 Firmware Thread.
If you have the Mexican/Uruguayan version, you need to download the latest version of the firmware from sammobile and flash that. Flashing AT&T firmware on a Mexican/Uruguayan phone could result in the bootloops you are experiencing.
Devo7v said:
It's hard to say what is wrong, but it sounds like you definitely need to flash stock firmware. One question, is it definitely the AT&T version (with the AT&T logo on the back cover) or could it be the Mexican version?
If it's the AT&T version, then flash the NE3 firmware by following the instructions in i537 Firmware Install Guide. The OP of the guide will ask you which firmware you're currently on, but for NE3 it doesn't matter which one you select because all the instructions will be the same. Make sure you don't have a corrupted download by checking the MD5 of the file you downloaded against the MD5 posted in the i537 Firmware Thread.
If you have the Mexican/Uruguayan version, you need to download the latest version of the firmware from sammobile and flash that. Flashing AT&T firmware on a Mexican/Uruguayan phone could result in the bootloops you are experiencing.
Click to expand...
Click to collapse
Yes I'm sure It's AT&T. I had already tried NE3, as I said, I've flashed as many stock firmwares as I have been able to lay hands on. I did notice that when I tried NE3 again, knox kernel lock and knox kernel warranty changed from my previous posted states to these:
Knox kernel lock: 0x0
Knox kernel warranty void: 0x1
I cand add that exactly when Odin sends the reboot the phone tries to boot but into recovery mode, instead of just booting normally.
The only thing I can think of now, is that the device must have a hrdware issue.
rguilamo said:
Yes I'm sure It's AT&T. I had already tried NE3, as I said, I've flashed as many stock firmwares as I have been able to lay hands on. I did notice that when I tried NE3 again, knox kernel lock and knox kernel warranty changed from my previous posted states to these:
Knox kernel lock: 0x0
Knox kernel warranty void: 0x1
I cand add that exactly when Odin sends the reboot the phone tries to boot but into recovery mode, instead of just booting normally.
The only thing I can think of now, is that the device must have a hrdware issue.
Click to expand...
Click to collapse
It's supposed to try to reboot into recovery mode when you first Odin back to stock NE3. I just recovered from a soft brick myself where I couldn't boot at all. Flashed NE3 through Odin and the first time it rebooted, it went to stock recovery (I assume to finish installing the stock rom), did what it needed, and eventually rebooted normally. Plus (sorry, I just have to ask), you are using download mode for Odin (not recovery mode), correct?
thisisapoorusernamechoice said:
It's supposed to try to reboot into recovery mode when you first Odin back to stock NE3. I just recovered from a soft brick myself where I couldn't boot at all. Flashed NE3 through Odin and the first time it rebooted, it went to stock recovery (I assume to finish installing the stock rom), did what it needed, and eventually rebooted normally. Plus (sorry, I just have to ask), you are using download mode for Odin (not recovery mode), correct?
Click to expand...
Click to collapse
Yes I'm using Download mode for ODIN, the thing is, when it tries to boot to recovery mode after flashing with ODIN, and the reboot command is sent, the recovery never boots, the screen goes off, and then it just starts restarting itself
rguilamo said:
Yes I'm using Download mode for ODIN, the thing is, when it tries to boot to recovery mode after flashing with ODIN, and the reboot command is sent, the recovery never boots, the screen goes off, and then it just starts restarting itself
Click to expand...
Click to collapse
And you definitely don't have a corrupted download, and you've tried different usb cables, different usb ports, and different computers?
Devo7v said:
And you definitely don't have a corrupted download, and you've tried different usb cables, different usb ports, and different computers?
Click to expand...
Click to collapse
Checked MD5's, used original Samsung cable, Asus Nexus 7 Cable, tried Windows 7 (Desktop), and windows 8.1 on two different laptops.
Curiously I said to myself, let me try and charge it, since all this flashing might have taken out the battery. When I plugged in the USB cable the device showed the Samsung splash, and turned off, yet I let it be and didn't disconnect it, after an hour or so, I came back and saw him charging the battery, with the red light indicator on, about 20 minutes later it tried to boot, got to the ATT logo, and after I while with the ATT logo (I assume since it has to compile the dalvik, because it's the first boot) it just turned off again, and back to ATT logo, and it was bootlooping like this until I unplugged it and gave up.
Was streaming some music when my phone decided to shut down. I thought it was out of battery since it was low so I plugged into the charger. Now it only boots up to the Samsung logo and nothing else. I cannot access recovery, only Odin (download mode). I set it to download mode and tried the emergency recovery on Smart Switcher. No luck still boot loop. I then tried to flash the stock firmware via Odin 3.10.7 and still no luck. I was on G920TUVU3DOI1. I bought the phone pre owned on Swappa and the previous owner assured me it was not rooted or tampered with in any way. My system status reads Custom though. Knox is not tripped. Would attempting to flash via Odin have given me the custom status? Samsung store here won't touch the phone since it says Custom for system status. Since I wasn't planning on rooting this phone until after the warranty period I did not do any of the options in developer mode. So now I have FRP lock to contend with. It blocks me from installing a custom recovery. Does any one have any other suggestions I can try?
Thanks in advance!
Brunkhorse said:
Was streaming some music when my phone decided to shut down. I thought it was out of battery since it was low so I plugged into the charger. Now it only boots up to the Samsung logo and nothing else. I cannot access recovery, only Odin (download mode). I set it to download mode and tried the emergency recovery on Smart Switcher. No luck still boot loop. I then tried to flash the stock firmware via Odin 3.10.7 and still no luck. I was on G920TUVU3DOI1. I bought the phone pre owned on Swappa and the previous owner assured me it was not rooted or tampered with in any way. My system status reads Custom though. Knox is not tripped. Would attempting to flash via Odin have given me the custom status? Samsung store here won't touch the phone since it says Custom for system status. Since I wasn't planning on rooting this phone until after the warranty period I did not do any of the options in developer mode. So now I have FRP lock to contend with. It blocks me from installing a custom recovery. Does any one have any other suggestions I can try?
Thanks in advance!
Click to expand...
Click to collapse
Have you tried downloading the official Firmware from sammobile and flashing through Odin? that's all essentially a store could do and that will not trip the counter as it is official, there is also a link in General if Sammobile is slow DL, which it often is. I would just to a full stock restore via ODIN and you should be good (unless there's something new with S6 and TMO I haven't been privy to)
Sammobile and Odin are your friend good luck
sleshepic said:
Have you tried downloading the official Firmware from sammobile and flashing through Odin? that's all essentially a store could do and that will not trip the counter as it is official, there is also a link in General if Sammobile is slow DL, which it often is. I would just to a full stock restore via ODIN and you should be good (unless there's something new with S6 and TMO I haven't been privy to)
Sammobile and Odin are your friend good luck
Click to expand...
Click to collapse
yes I tried that after Smart Switcher failed to fix my phone. More and more I feel it is a hardware issue. I wasn't messing with the phone when it decided to die, it was just doing it mid stream of Pandora. Odin and the stock firmware from SamMobile did not help me. From anyone's experience will Samsung give you a hard time if your System says "Custom" when you send it in for service? Knox is NOT tripped.