I changed the rom from CosmicCM 4.5 to original I9082XXAMF5_I9082OLBAMF1_XSE via Odin v3.07, the phone was successfully flashed (I checked Auto Reboot & F.Reset Time). When the phone reboot it go directly to android recovery mode, but it didn't load completely and get stuck (hang) on the green robot screen with all animation was stopped.
I tried to boot the phone several times but no avail, it always stuck on the android recovery mode like before. I also tried to flash the phone with CWM Philz TouchWiz recovery but the results were the same, the recovery mode didn't load completely stuck at green robot screen.
If you guys happened to experience the same problem with me, please kindly tell me what is the problem and the solution. Thanks a lot!
..
Thanks for the reply, I followed your tips and unfortunately the phone still stuck like before. Maybe it's time to visit service center.
Sent from my GT-I9100 using XDA Premium 4 mobile app
Related
I have attempted to flash multiple ROMs via CWM and everyone results in a bootloop, I am normally rather tech savy and believe I am installing them properly. Each time I have to flash back to stock via Odin. I am rather lost as I don't know where to start with the problem (Which results in a lack of explanation)
What other information may be needed to try to solve this?
I have primarily tried Juggernaut http://forum.xda-developers.com/showthread.php?t=1322642
avarize said:
I have attempted to flash multiple ROMs via CWM and everyone results in a bootloop, I am normally rather tech savy and believe I am installing them properly. Each time I have to flash back to stock via Odin. I am rather lost as I don't know where to start with the problem (Which results in a lack of explanation)
What other information may be needed to try to solve this?
I have primarily tried Juggernaut http://forum.xda-developers.com/showthread.php?t=1322642
Click to expand...
Click to collapse
Is it actually boot looping or just getting stuck on the logo??
Mine has taken as long as 10 minutes setting on the logo after a new rom flash ...
I assumed a boot loop was classified as the logo repeating over and over, as this is what is going on. When I attempted CM7 the blue circle/arrow just spun for 15+ minutes and with Juggernaut the "splash" colors thing just repeats over and over. No other screens appear.
Boot Loop, in my experience, has been when the logo is shown for a few minutes and then a quick (up to 30 seconds) black screen, phone vibrates and then the logo appears again repeating ad nauseam.
_eroz said:
Boot Loop, in my experience, has been when the logo is shown for a few minutes and then a quick (up to 30 seconds) black screen, phone vibrates and then the logo appears again repeating ad nauseam.
Click to expand...
Click to collapse
Yeah that is a boot loop ... the logo just hanging , is not a boot loop ..
I know it sounds strange, but try putting jug 4.1 and say the Faux123 kernel both on the phone, flash jug and then the kernel, then do a clear dalvik cache, and a fix permissions, then reboot, and let it sit for 10 - 30 minutes, I know it sucks ...
Can I flash these via odin somehow? Can no longer get into CWR after this last attempt.
avarize said:
Can I flash these via odin somehow? Can no longer get into CWR after this last attempt.
Click to expand...
Click to collapse
I would Odin back to stock, root via odin, and then flash the superuser zip , there is a tutorial on it , I don't have the link handy ...
tcboo said:
I would Odin back to stock, root via odin, and then flash the superuser zip , there is a tutorial on it , I don't have the link handy ...
Click to expand...
Click to collapse
Finally got it all going, Ended up opting for Domination. Now trying to find out exactly how to apply themes. Thanks for your assistance.
*Goes hunting*
Dear XDA,
I have tried all I can to fix this problem. Let me explain how it all started.
I was using my phone normally, running the same custom rom ive been running for the past 6 months. I went to turn on wifi then turned off the screen. Later when i went to check my phone the screen would not turn on, so i performed a battery pull. After that i saw the normal google boot screen and then the custom rom boot screen. It stayed on that screen for a few seconds and then went back to the google boot screen. It then did this over and over, ive left it on for an hour once and it kept doing the same thing. Only way to stop this is with battery pull.
So what can i do with the phone:
I can access fastboot
I can access download mode
What have i tried:
I tried the following methods:
1) Flashing a Back Up
2) Wiping data, flashing a rom and gapps
3) fastboot adb http://rootzwiki.com/topic/13819-how-tovzw-return-to-factory-state-unroot-and-relock/
4) ODIN http://rootzwiki.com/topic/27050-vzwodin-files-needed-for-odin-winstructions/
The same issue continues even after successfully completing these methods. Im now down to my last strand and hoping the great xda community can help me.
seanrobot said:
Dear XDA,
I have tried all I can to fix this problem. Let me explain how it all started.
I was using my phone normally, running the same custom rom ive been running for the past 6 months. I went to turn on wifi then turned off the screen. Later when i went to check my phone the screen would not turn on, so i performed a battery pull. After that i saw the normal google boot screen and then the custom rom boot screen. It stayed on that screen for a few seconds and then went back to the google boot screen. It then did this over and over, ive left it on for an hour once and it kept doing the same thing. Only way to stop this is with battery pull.
So what can i do with the phone:
I can access fastboot
I can access download mode
What have i tried:
I tried the following methods:
1) Flashing a Back Up
2) Wiping data, flashing a rom and gapps
3) fastboot adb http://rootzwiki.com/topic/13819-how-tovzw-return-to-factory-state-unroot-and-relock/
4) ODIN http://rootzwiki.com/topic/27050-vzwodin-files-needed-for-odin-winstructions/
The same issue continues even after successfully completing these methods. Im now down to my last strand and hoping the great xda community can help me.
Click to expand...
Click to collapse
Fastboot seems the best solution to me. What exactly went wrong? Also you could try a OMAP flash.
Sent from my Galaxy Nexus using XDA Premium HD app
To be honest I have no idea what happened. It happened out of no where didn't flash a new rom or anything. OMAP flash? Never heard of it but I'll definitely look into it and try it. I've tried fastboot method and still got the same problem sadly
Really hoping this isn't a hardware issue
I just tried an OMAP Flash and still have the same problem. Ive moved on to a new phone but I still want to get this one working. Any other ideas to fix this problem?
Got into the same problem as yours. I googled around, and most people fix this problem by flashing stock image. Basically wipe your phone clean, e.g system,data,cache etc. and then flash in the stock image u downloaded from google website throught fastboot mode. I tried that method, but my phone is still stuck in bootloop. You can give it a try and see if it works
(Originally posted this in the wrong forum, so I am reposting here.)
I have the Galaxy Note II with T-Mobile.
Some background: It was running Android 4.1.2. I rooted my phone once, about two weeks ago, just so I could take an image of it in case of an update issue. (I think the software was called nandroid.) Once I took the backup, I unrooted it again.
Since then, doing the Software Update check under settings never returned any results. It would just keep checking until I clicked cancel.
Anyway, when T-Mobile released the 4.3 update Monday morning, I tried updating to it using the Kies software on my PC (by connecting it through the USB cable). It got up to about 60% installation and then just hung for over an hour. So I unplugged the phone, re-plugged it back in, and then attempted the emergency firmware recovery through Kies. It went through this and got upto 76% installation and then just hung again for another hour. I again unplugged it to re-try the emergency recovery again, but every time I connected the phone, Kies would not detect it again. I re-seated the battery, rebooted my computer, uninstalled and reinstalled Kies, but Kies would not detect my phone again.
I am/was running the stock rom, but my phone won't even boot into it's normal screen. Any time I turn it again, i see the screen--"there were errors during firmware upgrade. try emergency recovery in Kies."
I can't even figure out a way to get to a screen where I can install the image I took using Nandroid a few weeks ago.
Any help or advice anyone can provide would be extremely appreciated!
Use Odin to fix it.
If you can put your phone into download mode then it should be 'saveable' ..
Double0EK said:
Use Odin to fix it.
If you can put your phone into download mode then it should be 'saveable' ..
Click to expand...
Click to collapse
I am able to put it into download mode. When I follow the instructions I found for Odin, the process seems to go smoothly. However, once my phone reboots, it stays on the "Samsung Galaxy Note II" screen (with the black background). I've left it like that for over 30 minutes, and it just stays on that screen.
Should there be another step I should be following?
diggeryo said:
I am able to put it into download mode. When I follow the instructions I found for Odin, the process seems to go smoothly. However, once my phone reboots, it stays on the "Samsung Galaxy Note II" screen (with the black background). I've left it like that for over 30 minutes, and it just stays on that screen.
Should there be another step I should be following?
Click to expand...
Click to collapse
Try installing SuperSU from Playstore
It has an option of doing a FULL UNROOT
I am sure that will help.
If not then install Rom Manager from PS
Through RomManager reboot in Recovery
1.) Wipe device 3x times
2.) Wipe cache 3x times
3.) Under advance you will Find Dalvik Cache -- wipe that 3x times
[MENTION=522570 [MENTION=1065870 [user=1879310]@@@@[/user][/MENTION]@@[/MENTION]@@
But more importantly why would you want 4.3 stock anyway?
Install TWRP Recovery or ClockWorkMod recovery and install/Flash CM1 (Cyagonemod) or any other custom roms 4.4.x kitkat
Nothing is really working for me.
I can't boot into normal mode. I am able to get into "download" mode, but whenever I try to load an image using the Odin software (both a stock image and a Cyagonemod image), it starts to load the image, but just hangs a certain percent of the way through.
I also can't get to that screen where it gives you the text based options to wipe your device, cache, etc.
I've tried loading both TWRP recovery and ClockWorkMod recovery (through Odin), and though it seems to load properly (Odin says "Pass"), when the phone reboots, it goes to the "Samsumg Galaxy Note II" screen (the one with white text on a black background), and just stays there.
I've gotten T-Mobile to agree to send me a new phone. But if I can't get into any of the items I mention above, how can I make sure my old device is wiped before sending it back to them?
Just do this un root with chain fire root away app.
Then use triangle away app.
Then find 4.1.2 MB1 stock Odin tar. The complete package .
Odin to stock .
Reboot and then update via Ota.
You have to un root first and also have to triangle away which removes flash counter in Odin.
System modified status will not allow Ota.
That's the best suggestion I have
Sent from my SGH-T889 using xda app-developers app
diggeryo said:
Nothing is really working for me.
I can't boot into normal mode. I am able to get into "download" mode, but whenever I try to load an image using the Odin software (both a stock image and a Cyagonemod image), it starts to load the image, but just hangs a certain percent of the way through.
I also can't get to that screen where it gives you the text based options to wipe your device, cache, etc.
I've tried loading both TWRP recovery and ClockWorkMod recovery (through Odin), and though it seems to load properly (Odin says "Pass"), when the phone reboots, it goes to the "Samsumg Galaxy Note II" screen (the one with white text on a black background), and just stays there.
I've gotten T-Mobile to agree to send me a new phone. But if I can't get into any of the items I mention above, how can I make sure my old device is wiped before sending it back to them?
Click to expand...
Click to collapse
have you tried booting into recovery? after you load the custom recovery with odin and it reboots, pull the battery put it back, then hold vol up + home and then + power. hold all 3 until recovery. try a factory reset and reboot.
Sent from my SGH-T889 using XDA Premium 4 mobile app
wolfpack612 said:
have you tried booting into recovery? after you load the custom recovery with odin and it reboots, pull the battery put it back, then hold vol up + home and then + power. hold all 3 until recovery. try a factory reset and reboot.
Click to expand...
Click to collapse
I have. It brings me to the same screen with the Samsung Galaxy Note II text on the black background and just stays there.
So, in summary, I can get into download mode (vol down+home+power), but it seems nothing else.
Try factory settings the phone through stock recovery and then check your phone status. It should say 'normal' but if it says 'modified,' download Triangle away and run the tracking setting (it'll make your phone say normal so you can download the OTA). Given you're on tmobile and your phone is the T889 model, check for software updates and install the OTA. Your phone will take a bit and will probably be stuck on the T-Mobile 4G boot screen for several minutes (it's normal). This should work.
I screwed up.
I wanted to install a new custom mod after purchasing a new SM-P605. I rooted my device, and searched for a while on how to install a custom recovery (TWRP). I downloaded ODIN and flashed it a couple of times but it didn't work, I kept getting a "recovery is not seandroid enforcing" and the screen freezes.
Then I tried Rashr's flash tool to install TWRP for me, and afterwards selected "boot into recovery".
Now i'm stuck in the same screen, but whenever I tried to restart, i get back to it, and can't get back in the system.
What can I do?
I'm unfortunately stuck in a very similar situation.
I was updating the firmware on my tablet to 4.4.2 downloaded off Sammy mobile, uploading using Odin. I've done this dozens of times since my S2 which was 12 handsets and 6 Android tablets ago. This time, about a third of the way through the process hung for a few minutes then the device restarted without warning and now its stuck in a loop where it starts normally
http://imgur.com/MTwiE5V [1]
Then says
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery.
Then this
http://imgur.com/Ua1nmhi [2]
and stays on that screen for short periods before rebooting and starting the above again.
Thanks in advance for any tips or help you guys can provide!
SleepyDonald said:
I screwed up.
I wanted to install a new custom mod after purchasing a new SM-P605. I rooted my device, and searched for a while on how to install a custom recovery (TWRP). I downloaded ODIN and flashed it a couple of times but it didn't work, I kept getting a "recovery is not seandroid enforcing" and the screen freezes.
Then I tried Rashr's flash tool to install TWRP for me, and afterwards selected "boot into recovery".
Now i'm stuck in the same screen, but whenever I tried to restart, i get back to it, and can't get back in the system.
What can I do?
Click to expand...
Click to collapse
Have tried factory reset/clear cache/clear dalvik?
shayind4 said:
Have tried factory reset/clear cache/clear dalvik?
Click to expand...
Click to collapse
Thanks, but it turns out the solution to my problem was simple. I took it to the place I got it from and the guy just pressed power, vol and menu button long enough until it rebooted. I'm quite a noob it seems.
I'm not sure if it will help you Nationalmaverick, because my problem was slightly different.
Hello XDA experts,
Thanks in advance for your time & help with my problem. Any advice that helps me fix my phone will be highly appreciated!
[apologies for the longish post but I wanted to give you as much detail as possible to help me resolve the issue]
Background:
I had been using my Galaxy Note 2 [SGH-I317] since December 2012, without any modifications. The phone was not rooted, did not have any recovery tool installed & I had not done any upgrade to the OS after buying the phone as I was wary of bricking it.
A couple of days ago, my phone was connected to the charger (it was 100% charged, but I hadn't unplugged the cable yet), I just opened WhatsApp & the phone re-booted suddenly. It has done that at random times once in a while so that was not a huge surprise, but then things started going down-hill.....as I got stuck in the infamous bootloop & I am unable to get into recovery mode.
The phone gets stuck at the following point in the boot sequence:
a)"Samsung Galaxy Note II" screen --> b)Animated Samsung logo [with Blue n Purple Ring] --> c)AT&T logo screen [with sound] --> d)Samsung logo [the one where area outside the Samsung text glows blue then turns black & again glows blue]
Screen d) is where the phone gets stuck.
I tried getting into recovery mode but the phone simply restarts, so I am not able to get to the recovery mode.
I can only get into download mode.
After reading through all the threads where people reported similar sort of problems, I did the following things:
1) Wanting to recover data, I flashed "twrp-2.8.6.0-t0lteatt.img.tar" (from http://forum.xda-developers.com/showthread.php?t=1981198) using Odin [v3.09]. Odin finished without any errors & the phone re-booted [<OSM> All threads completed. (succeed 1 / failed 0)]
However this did not change anything, the phone was still stuck at Screen d) & unable to get into recovery mode. (Odin Message log & Screenshot attached for reference)
2) After that I flashed "CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar.md5" (from http://forum.xda-developers.com/showthread.php?t=1980683) using Odin. Result was similar to previous effort. (Odin Message log & Screenshot attached for reference)
3) I gave up on recovering the data & only hoped I could recover the phone atleast (the phone looks practically new without a scratch as I handle it like a baby!) Then I flashed the newer stock ROM [KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar, dated 2013-04-05] (from http://www.sammobile.com/firmwares/database/SGH-I317/). I chose the newer stock ROM even though my phone originally was on the older stock ROM as I was like, might as well get the improved OS while I am trying to fix the phone. Odin finished without any errors & the phone re-booted [<OSM> All threads completed. (succeed 1 / failed 0)] However this still did not change anything, the phone was still stuck at Screen d) & unable to get into recovery mode. (Odin Message log & Screenshot attached for reference)
4) Lastly I flashed the older stock ROM [KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar, dated 2012-11-27]. Still there was no change in the situation (Odin Message log & Screenshot attached for reference).
5) Finally I tried firmware upgrade from Kies as suggested here http://forum.xda-developers.com/showthread.php?t=2585879, which completed as well (after taking an eternity) No luck even then (Kies initial Screenshot attached for reference)
For reference, this is what my download screen has shown from the beginning (still shows the same):
ODIN MODE
PRODUCT NAME: SGH-I317
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Now I am at my wits end in trying to bring back my phone from the dead. I have faith in all you experts out there in helping me point in the right direction. What else can I do to revive it? Are there any options in ODIN that I can check/uncheck to help me out of this?
I do not know a lot about EFS, but is this problem related to that? Please let me know if I need to provide any additional information.
Awaiting your expert replies & solutions!
Are you using the 3 button combo to enter recovery mode only ?
Or have you tried a root capable advanced reboot menu application from the play store ?
..I recall that the power button will get stuck and cause a bootloop regardless of the OS...
If the button is stuck. ..then no application or OS will help. ..but if the device will boot to recovery using an advanced reboot menu app....then the device needs more work. ..g
gregsarg said:
Are you using the 3 button combo to enter recovery mode only ?
Or have you tried a root capable advanced reboot menu application from the play store ?
..I recall that the power button will get stuck and cause a bootloop regardless of the OS...
If the button is stuck. ..then no application or OS will help. ..but if the device will boot to recovery using an advanced reboot menu app....then the device needs more work. ..g
Click to expand...
Click to collapse
First of all thanks for your reply.
I am using the 3 button combo.
I haven't tried any application to enter recovery mode......can you recommend any such app?
Also given that the phone wont boot, how would I install it on the phone in the 1st place?
Lastly I think that the power button is not stuck, as otherwise I would face issue getting into download mode as well, right?
Thanks much!
gregsarg said:
Are you using the 3 button combo to enter recovery mode only ?
Or have you tried a root capable advanced reboot menu application from the play store ?
..I recall that the power button will get stuck and cause a bootloop regardless of the OS...
If the button is stuck. ..then no application or OS will help. ..but if the device will boot to recovery using an advanced reboot menu app....then the device needs more work. ..g
Click to expand...
Click to collapse
Would you recommend trying Odin with
"Re-partition" checked?
or
"NAND erase all" checked?
dalwani said:
Would you recommend trying Odin with
"Re-partition" checked?
or
"NAND erase all" checked?
Click to expand...
Click to collapse
Awaiting invaluable advice from all experts out there!