Hi guys, as the title says my nexus was going great, howver randomly it switched off then into a loop, it goes to the part were the google logo comes up then just keeps repeating this, ive cleared the cache, restored factory settings. none of it has fixed it! Please help guys.
I have no solution but the same thing happened to me, I used fastboot to lock the bootloader and took it to verizon and exchanged it.
I got it to boot once after locking the bootloader but then it just stayed in the boot loop. I chalked it up to a hardware failure and moved on.
Hopefully someone else will have a better suggestion.
Sent from my Galaxy Nexus using xda premium
sjameson6969 said:
Hi guys, as the title says my nexus was going great, howver randomly it switched off then into a loop, it goes to the part were the google logo comes up then just keeps repeating this, ive cleared the cache, restored factory settings. none of it has fixed it! Please help guys.
Click to expand...
Click to collapse
More info needed. GSM or LTE? Custom ROM or stock?
sjameson6969 said:
Hi guys, as the title says my nexus was going great, howver randomly it switched off then into a loop, it goes to the part were the google logo comes up then just keeps repeating this, ive cleared the cache, restored factory settings. none of it has fixed it! Please help guys.
Click to expand...
Click to collapse
Flash the factory image and you should be good. You can use the tool kit to do this if you are not familiar with manual methods.
http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my Galaxy Nexus using Tapatalk
Have you been trying to root it ? it's weird it just switched off and is in a loop.
El Daddy said:
More info needed. GSM or LTE? Custom ROM or stock?
Click to expand...
Click to collapse
Im not sure I know the difference, its got a sim card so i think its GSM? I'm on three in the uk.
custom rom I downloaded it from here.
mine just switched off in google earth after the phone got real hot and after battery pull everything loaded fine but 10 seconds after launcher loaded up, GPS icon appeared in status bar and it rebooted again. Did this same thing continually for over an hour so I had to restore factory image. I've since installed 4.0.2 and it hasn't happened again.
Sent from my Galaxy Nexus using xda premium
han4mi said:
Have you been trying to root it ? it's weird it just switched off and is in a loop.
Click to expand...
Click to collapse
No it was already rooted. I was actually streaming a video off the internet at the time then the screen just went blank
Did you do a nandroid backup before flashing the custom rom? If so, restore that. If not try reflashing your current rom.
Sent from my Xoom using xda premium
the toolkit doesn't even pick the device up!
Probably has something to do with your drivers not recognizing it...are you using parallels?
Sent from my Galaxy Nexus using xda premium
sjameson6969 said:
the toolkit doesn't even pick the device up!
Click to expand...
Click to collapse
Looks like the adb driver is missing.
Sent from my Galaxy Nexus using Tapatalk
same thing is happening to my non-rooted GN (GSM and stock). Was using my phone then all of a sudden it turned off and rebooted, but it is stuck on the google screen, then black screen, then back to google screen (loop). Help!
missnexusone said:
same thing is happening to my non-rooted GN (GSM and stock). Was using my phone then all of a sudden it turned off and rebooted, but it is stuck on the google screen, then black screen, then back to google screen (loop). Help!
Click to expand...
Click to collapse
this happened to me too right now.
I can get into odin mode and the bootloader but if I try to get to recovery I see a garbled screen but I can see the android on his back and a red triangle with an exclamation point. After a few seconds there the phone reboots. what's going on?!?
missnexusone said:
same thing is happening to my non-rooted GN (GSM and stock). Was using my phone then all of a sudden it turned off and rebooted, but it is stuck on the google screen, then black screen, then back to google screen (loop). Help!
Click to expand...
Click to collapse
geemaan said:
this happened to me too right now.
I can get into odin mode and the bootloader but if I try to get to recovery I see a garbled screen but I can see the android on his back and a red triangle with an exclamation point. After a few seconds there the phone reboots. what's going on?!?
Click to expand...
Click to collapse
Exact same thing happened to me a week or two ago (GSM, stock, not rooted).
I followed these steps to solve the issue - http://forum.xda-developers.com/showpost.php?p=20302409&postcount=2
It was very simple, but it restored the phone and so wiped everything on it.
didn't work for me. now I'm stuck at a yellow triangle with an exclamation mark between a phone and a pc...
You did download the file properly right? It was around 180mb if I remember correctly.
Yeah, got it from the rs link. Zip was ok. when run, the exe checks crc ok. It gets stuck when starts writing nand for recovery. I really think there's something broken with the phone because of the screen desynchronisation.I'm gonna take it back monday morning...
Try giving it the fast boot command to lock the boot loader (your driver might not be configured for the phones regular state but if you can get it to recognize the decide when the phone is in the boot loader this may work). Give it the fast boot OEM lock command, and then give it the faatboot OEM unlock command. Make sure you have the stock .img on your ccmputer. When you unlock it, it will wipe everything. I mean everything, your Android backups and all. But, it managed to bring mine back after I got stuck in a boot loop that wouldn't make it passed the Google logo. After you unlock it, try and configure the drivers to recognize the phone again. Hopefully then you can push what you need from the computer
Here is what I mean with screen desync:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the recovery screen had the same "video effect".
The duplicate images have a flicker effect.
Related
I'm sure this has been asked a bunch of times, but I don't know what this screen is called, therefore I can't search for a solution.
When I first looked at my phone (used) before I bought it, it didn't do this. And then I brought it to the Verizon store to get a new SIM card. The salesperson reset the phone for me. The battery died on the way home while I was using it and it shut down. Now, every time I turn on the phone it shows this screen. If I pull the battery and boot into upgrade mode (volume down + power) it will boot, but it resets data (all of my stuff is gone). It will do this every time. I suspect the file system has become corrupted due to the improper shut down.
So, how can I solve this? Do I need to reflash everything through Odin, or can I sort of just push /system and /data to it via adb? I'd like to stick with stock ICS for now.
I'm coming from a Samsung Fascinate. I've owned a Galaxy Nexus before, but only for a few weeks. I have quite a bit of experience with all of this stuff, so any basic info should be easy for me to understand. I just don't know what this screen is and why it's appearing.
EDIT: It would probably help if I posted the photo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jmattp said:
I'm sure this has been asked a bunch of times, but I don't know what this screen is called, therefore I can't search for a solution.
When I first looked at my phone (used) before I bought it, it didn't do this. And then I brought it to the Verizon store to get a new SIM card. The salesperson reset the phone for me. The battery died on the way home while I was using it and it shut down. Now, every time I turn on the phone it shows this screen. If I pull the battery and boot into upgrade mode (volume down + power) it will boot, but it resets data (all of my stuff is gone). It will do this every time. I suspect the file system has become corrupted due to the improper shut down.
So, how can I solve this? Do I need to reflash everything through Odin, or can I sort of just push /system and /data to it via adb? I'd like to stick with stock ICS for now.
I'm coming from a Samsung Fascinate. I've owned a Galaxy Nexus before, but only for a few weeks. I have quite a bit of experience with all of this stuff, so any basic info should be easy for me to understand. I just don't know what this screen is and why it's appearing.
EDIT: It would probably help if I posted the photo
Click to expand...
Click to collapse
Its the stock Recovery screen. I would just do a fresh install using Odin
Sent from my Galaxy Nexus using XDA
That's the stock recovery screen? Funny.. I've never seen it. I've seen fastboot a bunch of times, and Clockwork recovery (and other recoveries) but I assumed that was some kind of looping loading screen or something.
I'm resetting it to stock through the terminal, pushing everything in fastboot. I want the OTA 4.0.4 update. I should be able to get that with the stock ROM and OEM locked bootloader right?
Thanks for telling me what that screen was. I had no idea.
EDIT: Oh, I was also wondering if the improper shutdown caused this problem, or if something could be wrong with the device that I should be worried about.
jmattp said:
That's the stock recovery screen? Funny.. I've never seen it. I've seen fastboot a bunch of times, and Clockwork recovery (and other recoveries) but I assumed that was some kind of looping loading screen or something.
I'm resetting it to stock through the terminal, pushing everything in fastboot. I want the OTA 4.0.4 update. I should be able to get that with the stock ROM and OEM locked bootloader right?
Thanks for telling me what that screen was. I had no idea.
EDIT: Oh, I was also wondering if the improper shutdown caused this problem, or if something could be wrong with the device that I should be worried about.
Click to expand...
Click to collapse
If you can get into fastboot and recovery then you don't have any serious problems.
Sent from my Galaxy Nexus using XDA
Thanks. After returning to stock, everything seems fine. I guess the battery dying borked something. I hope this doesn't happen every time the battery dies. (I don't plan on letting it die... but in the event that it does, it will suck)
jmattp said:
Thanks. After returning to stock, everything seems fine. I guess the battery dying borked something. I hope this doesn't happen every time the battery dies. (I don't plan on letting it die... but in the event that it does, it will suck)
Click to expand...
Click to collapse
It must've been something else, I've had the battery die a few times, its booted up fine. Glad you fixed it.
Sent from my Galaxy Nexus using XDA
Ok i have a verizon gnex with latest ota. At times if i reboot or turn off the phone then turn it back on the phone will get stuck at the google splash screen. One time i pulled the lte sim card and then after a few tries it booted without the lte sim.. then i powered it down and placed the lte sim card in and it started back up... other times that does not work.... Twice today i had to turn it off and wait like 20 minutes or so and then turn it back on with the lte sim in and then it booted. I did use nrt nexus root toolkit and redid the phone but still have the issue.... should i try a custom rom and wipe the system or did the nexus root tool when i used that also wiped the system?
rezoundness said:
Ok i have a verizon gnex with latest ota. At times if i reboot or turn off the phone then turn it back on the phone will get stuck at the google splash screen. One time i pulled the lte sim card and then after a few tries it booted without the lte sim.. then i powered it down and placed the lte sim card in and it started back up... other times that does not work.... Twice today i had to turn it off and wait like 20 minutes or so and then turn it back on with the lte sim in and then it booted. I did use nrt nexus root toolkit and redid the phone but still have the issue.... should i try a custom rom and wipe the system or did the nexus root tool when i used that also wiped the system?
Click to expand...
Click to collapse
use the tootkit to flash the latest stock image and see if that fixes your problem
k786 said:
use the tootkit to flash the latest stock image and see if that fixes your problem
Click to expand...
Click to collapse
i am trying that now nexus tool klit 1.5.5
http://www.droidforums.net/forum/galaxy-nexus-development/192031-toolkit-nexus-root-toolkit-v1-5-5-updated-11-04-12-a.html
i selected the recovery / unroot with the checkbox of softbrick/bootloop....
So far so good... I have isntalled a few apps and now listening to ihart radio and will reboot the phone in a little bit and see what happens. Also is this nexus root kit 1.5.5 the best to root it as well...
Still doing the stuck at google logo... gonna leave it their for a bit and see what happens. It took about a minute or two... to get passed the google screen...
Don't use a toolkit because if something goes wrong (which it seems to be ) you won't know what, where or why it happened. Read the stickies, learn ADB and never have this problem again. Ever. It only takes a few minutes to learn.
I mean you wouldn't hoist your engine out of your car and begin to take it apart without having any idea what you're doing, would you? Go read the stickies..... seriously
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
RoyJ said:
Don't use a toolkit because if something goes wrong (which it seems to be ) you won't know what, where or why it happened. Read the stickies, learn ADB and never have this problem again. Ever. It only takes a few minutes to learn.
I mean you wouldn't hoist your engine out of your car and begin to take it apart without having any idea what you're doing, would you? Go read the stickies..... seriously
Click to expand...
Click to collapse
you mean the mr fusion engine wont work in my DeLorian....
http://blogs.discovermagazine.com/discoblog/files/2008/04/mr-fusion.jpg
My gnex was doing the same thing every time I rebooted I had to pull the battery for it to start up. I actually just left it one day for like 30 mins on the splash screen and I guess it just took its time cause now it starts up normally
Sent from my Galaxy Nexus using xda app-developers app
My phone has done this twice. Both times, I solved it by pulling the battery for about 30 seconds, popping it back in, and letting it boot like normal.
Card83 said:
My phone has done this twice. Both times, I solved it by pulling the battery for about 30 seconds, popping it back in, and letting it boot like normal.
Click to expand...
Click to collapse
i wonder if it has something to do with automatically zip aligning at boot or something? I hate to waite as i did pull the battery at times for 3 or 4 minutes and still had to wait a few minutes at boot...
rezoundness said:
i wonder if it has something to do with automatically zip aligning at boot or something? I hate to waite as i did pull the battery at times for 3 or 4 minutes and still had to wait a few minutes at boot...
Click to expand...
Click to collapse
When running JellyBean, the Nexus can sometimes run a filesystem check (similar to Windows' chkdsk or *nix fsck) if it wasn't booted properly or for other random reasons. That check can take a few minutes, up to 10 minutes or so on some devices after certain actions. If anything, pulling the battery during this is doing more harm than good.
I have searched high and low for an answer to my problem for the past 5 hours. Haven't found a solution or guide on XDA or anywhere else that can help, so I am making this post as my last effort.
I bought an unlocked GSM Galaxy Nexus off of ebay knowing that it was stuck in a boot loop. I figured it could be fixed. I may be wrong.
I AM ON A MAC The pictures have Windows but I am running Parallels and it sucks.
--------
Ok, so here is my problem lies, when turning the device on normally I get this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get this for a few seconds, then it goes away, vibrates, and comes back ..... over and over.
I can get to both Odin mode and Fastboot:
This is no problem.
I even managed to get CWM on the phone and to come up:
My issue now is that I can't get ADB to work .. Wugs ToolKit won't work ... Galaxy Nexus ToolKit wont work ... nothing.
I can't be 100% sure that USB Debugging is enabled as I can't get past the Google Logo.
Is there anything that can be done to save this phone ... or is it a fancy paperweight?
I have an N4, I just bought this because the seller had no clue how to fix it, and it was a good deal. (not to mention I was planning to use it as a dev device for apps and such)
Thanks everyone!!!
Use the terminal on the Mac. I also have a Mac. Let me find u the files needed for adb and fast boot for macs.
Sent From My Miui Powered Galaxy Nexus
---------- Post added at 10:46 PM ---------- Previous post was at 10:42 PM ----------
OK. This was the guide I used when I first got my nexus s 4g but I also used it for my galaxy nexus. Follow the instructions and make sure u use the correct files for your phone. forum.xda-developers.com/showthread.php?t=1129759
Sent From My Miui Powered Galaxy Nexus
Well crap .... after trying to use Fastboot (as ADB doesn't seem to want to recognize my device) I am stuck at the Google logo with the unlocked padlock.
I can still get in to CWM Recovery and Fastboot, but I am 100% lost on what to do now. I can not find a solution anywhere that works
clay_cauley said:
Well crap .... after trying to use Fastboot (as ADB doesn't seem to want to recognize my device) I am stuck at the Google logo with the unlocked padlock.
I can still get in to CWM Recovery and Fastboot, but I am 100% lost on what to do now. I can not find a solution anywhere that works
Click to expand...
Click to collapse
Did you try using anther pc? Maybe windows can manage this out.. I don't know what else to suggest..
Sent from my Galaxy Nexus
Jar3112 said:
Did you try using anther pc? Maybe windows can manage this out.. I don't know what else to suggest..
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Unfortunately so ---- Windows XP and Windows 7 both ... I may try again tomorrow : /
Ok, so here is my status now ---
Flashed stock image using Odin. Said it was completed and successful. Gave a big "PASS" message.
Rebooted phone, and watched the Google logo bootloop for 30mins.
On the plus side, my phone is now getting recognized as an ADB Interface --- but only in Fastboot. When I enter Stock Recovery or CWM Recovery, I can no longer use adb.
1 step closer, or totally effed?
clay_cauley said:
Ok, so here is my status now ---
Flashed stock image using Odin. Said it was completed and successful. Gave a big "PASS" message.
Rebooted phone, and watched the Google logo bootloop for 30mins.
On the plus side, my phone is now getting recognized as an ADB Interface --- but only in Fastboot. When I enter Stock Recovery or CWM Recovery, I can no longer use adb.
1 step closer, or totally effed?
Click to expand...
Click to collapse
Flash the image, bootloader and radio and that should get you booted
Same Problem
jaymazz13 said:
Flash the image, bootloader and radio and that should get you booted
Click to expand...
Click to collapse
So I just had this happen to me over lunch, after an hour of trying to re-flash stock image, bootloader, and radios, i'm still getting the Google boot up screen. I too can get into flashboot, but I can not get into recovery... Suggestions?
Sorry, I know this threads a little old, but it was the same problem I am having, wasn't sure if anyone found a solution.
Thanks in advance...
marker2002 said:
So I just had this happen to me over lunch, after an hour of trying to re-flash stock image, bootloader, and radios, i'm still getting the Google boot up screen. I too can get into flashboot, but I can not get into recovery... Suggestions?
Sorry, I know this threads a little old, but it was the same problem I am having, wasn't sure if anyone found a solution.
Thanks in advance...
Click to expand...
Click to collapse
Does ur computer recognize ur device when u plug it in?
Sent from my HTC6435LVW using xda app-developers app
jaymazz13 said:
Does ur computer recognize ur device when u plug it in?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yes it does, but only in fast boot.
Other things I found:
-My battery is full. When I plug it in it shows it's charging then shows me battery life, shows full.
-When I turn it on, it gets stuck at Google screen
-When I go into fastboot my computer recognizes it, but after flashing anything to it, it just continues to be stuck on the Google start-up screen
Update since I've written this post... when I plug it in, it wont go past the 'showing that it's charging screen" I have to wait till it shows battery status before I can go into fast boot, and now it wont even do that... neat. Headed home, then i'll swap batteries and try it all again.
marker2002 said:
Yes it does, but only in fast boot.
Other things I found:
-My battery is full. When I plug it in it shows it's charging then shows me battery life, shows full.
-When I turn it on, it gets stuck at Google screen
-When I go into fastboot my computer recognizes it, but after flashing anything to it, it just continues to be stuck on the Google start-up screen
Update since I've written this post... when I plug it in, it wont go past the 'showing that it's charging screen" I have to wait till it shows battery status before I can go into fast boot, and now it wont even do that... neat. Headed home, then i'll swap batteries and try it all again.
Click to expand...
Click to collapse
any updates?
hi clay_cauley .. I have the same problem..did y find any worked solution??
RiotSauce said:
any updates?
Click to expand...
Click to collapse
Hi all, I have the same issue I'll try all the above even though half of it sounds half Chinese to me XD (not a developer, heh).
Cheers,
Hello,
I recently tried out the latest version of "PhilZ-Touch Recovery 6.0" located in this thread: http://forum.xda-developers.com/showthread.php?t=2446393. I did this from my previously installed recovery (TWRP V2.6.3.0) and everything went and had no problems, but I decided to go back to TWRP anyway and installed the latest TWRP version for my phone (V2.6.3.1) and again everything went fine and I was back to using TWRP again. The only problem I noticed is that when I boot into TWRP recovery now, I see this blue logo on my screen before I am presented with the TWRP curtain screen that I was used to seeing before.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did a little searching and discovered this logo is the CyanogenMod Logo and since I do not have CyanogenMod installed on my phone, I can only assume it was placed on my phone as part of the philz recovery install. My question is then, how do I get rid of this logo since I do not have CM installed and do not want it to show up when I boot into TWRP?
TIA,
Mtcell
P.S. I would have posted this in the thread above, but I am a newly registered member and was not able to post in that tread until I have accumulated 10 or most post. Instead of spamming the forum to get my post count up (and taking a change on getting my account suspended in the process), I felt it would be better to post this question here.
I have been running the PhilZ recovery since @CNexus made it available, it doesn't place that image on your phone.
What ROM are you running? TW or AOSP??
jdelano said:
I have been running the PhilZ recovery since @CNexus made it available, it doesn't place that image on your phone.
What ROM are you running? TW or AOSP??
Click to expand...
Click to collapse
I am totally stock, rooted, and have been since I got the phone back in June. This is what is confusing me. Please note, the icon only shows up when I boot into recovery. If I do a normal boot / reboot then I cannot see it.
Thanks again for any and all replies,
Mtcell
mtcellph said:
I am totally stock, rooted, and have been since I got the phone back in June. This is what is confusing me. Please note, the icon only shows up when I boot into recovery. If I do a normal boot / reboot then I cannot see it.
Thanks again for any and all replies,
Mtcell
Click to expand...
Click to collapse
Hmmm, booting into recovery from android or with the phone off?
I just updated to 6.0.5 and I went into recovery to flash that update, though it was via the power menu.
Let me try with the power off ... ah yes, there is a little blue guy there when I go to recovery that way. (its been so long since I've done that)
TWRP probably doesn't over right that part of the phone.
Maybe try normal CMW flash and then back to TWRP or do a nandroid restore from a previous backup.
Twrp added that as the logo in the last update prob was a mistake
Sent from my SPH-L710 using xda app-developers app
jdelano said:
Hmmm, booting into recovery from android or with the phone off?
I just updated to 6.0.5 and I went into recovery to flash that update, though it was via the power menu.
Let me try with the power off ... ah yes, there is a little blue guy there when I go to recovery that way. (its been so long since I've done that)
TWRP probably doesn't over right that part of the phone.
Maybe try normal CMW flash and then back to TWRP or do a nandroid restore from a previous backup.
Click to expand...
Click to collapse
Thanks for the confirmation. At least I know I did not mess something up. I mainly do all of my rebooting into recovery from within android using GooManager, but I tried it from TWRP as well and the same result happened and finally, I tried it from a cold boot using the power, home, volume up buttons and the same result each time.
As far as the logo goes, I am not really overtly concerned about it as long as it's not going to mess anything up, I will probably leave it unless I find some reason I should remove it.
Thanks again for your replies,
Mtcell
yeah nothing messed up at all, you just have a new blue pal
Your welcome; a sanity test now and again is a good thing (some - like me - need them more often)
Notorious said:
Twrp added that as the logo in the last update prob was a mistake
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Ahh, that makes sense now. As I said, I will keep it just as long as it's not going to mess with anything (which it hasn't) so no harm no foul.
Thx again,
MTCell
Hi all hoping someone can help me out with this. I have AT&T note 2 SGH-I317 that is stock everything recovery and firmware and it will not boot past the Samsung Note 2 screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
. When I boot into recovery this is what I see. I have tried ODIN 3.07 & 3.09 to reinstall the stock firmware Odin says it passes but nothing changes on phone. Any help would be very appreciated.
Sent from my LG-VS980 using Tapatalk 2
mike t said:
Hi all hoping someone can help me out with this. I have AT&T note 2 SGH-I317 that is stock everything recovery and firmware and it will not boot past the Samsung Note 2 screen.
. When I boot into recovery this is what I see. I have tried ODIN 3.07 & 3.09 to reinstall the stock firmware Odin says it passes but nothing changes on phone. Any help would be very appreciated.
Sent from my LG-VS980 using Tapatalk 2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2618447
thanks for your reply. I tried the steps in that thread and had the same result. ODIN says everything passes with no error but nothing changes phone still will not boot and recovery gives the same errors.
mike t said:
thanks for your reply. I tried the steps in that thread and had the same result. ODIN says everything passes with no error but nothing changes phone still will not boot and recovery gives the same errors.
Click to expand...
Click to collapse
Which steps have you completed?
What are you flashing in ODIN?
4.1.1 stock firmware?
The main step after the ODIN flash, and it reboots, before it gets to starting it's boot you need to power it off, pull battery whatever, and boot into stock recovery. Then do a factory reset. That step has recovered many phones stuck at the first white Samsung logo.
If it's stuck at the pulsing blue Samsung logo. There's another fix.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
I could not get past the first step. I flashed the 4.1.1 tar linked in the first step ODIN says it passed, phone reboots and gets stuck at the white Samsung note 2 screen. I pulled the battery booted into recovery and got the same errors. Did a factory reset which gave me the same "can not mount" errors rebooted and still getting stuck at the same screen. Could it be the emmc bug?
Sent from my LG-VS980 using Tapatalk 2
dicksteele said:
Which steps have you completed?
What are you flashing in ODIN?
4.1.1 stock firmware?
The main step after the ODIN flash, and it reboots, before it gets to starting it's boot you need to power it off, pull battery whatever, and boot into stock recovery. Then do a factory reset. That step has recovered many phones stuck at the first white Samsung logo.
If it's stuck at the pulsing blue Samsung logo. There's another fix.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my LG-VS980 using Tapatalk 2
Pull the usb cable out and pull the battery as soon as odin shows "Passed". If you let it start to boot on its own, its too late.
Timing is everything. Once the phone is disconnected and off, insert the battery and boot into 3e (stock) recovery, and factory reset. Then let it boot normally from recovery.
rangercaptain said:
Pull the usb cable out and pull the battery as soon as odin shows "Passed". If you let it start to boot on its own, its too late.
Timing is everything. Once the phone is disconnected and off, insert the battery and boot into 3e (stock) recovery, and factory reset. Then let it boot normally from recovery.
Click to expand...
Click to collapse
Thanks for the help, but i still get the same result. Only thing I can think of is the memory got messed up somehow.
If you've double-checked the steps, and redid your work very carefully, and your phone is still borked, you can use a JTAG service. The phone is flashed with a device connected directly to the phone rom chip. It costs $50 and takes a week. www.mobiletechvideos.com
I got the phone in trade for replacing a screen in a mega so if I can't get it going I will prob just use it for parts. If I can get it working I plan on using it to test drive straight talk. I may look up how to JTAG and try to do it myself I've J taged Xbox 360's but I'm sure that's a totally different thing.
Sent from my LG-VS980 using Tapatalk 2
If it was a EMMC brick it would not boot into recovery or download mode would it?
Sent from my LG-VS980 using Tapatalk 2
JTAG is usually the last resort after flashing wrong roms or kernels, but it sounds like this is the last resort, and it works.
rangercaptain said:
JTAG is usually the last resort after flashing wrong roms or kernels, but it sounds like this is the last resort, and it works.
Click to expand...
Click to collapse
Yea, but the weird thing is that this phone has never been rooted or messed with in any way.
Sent from my VS980 4G using xda app-developers app
So what stock firmware were you on ?
http://forum.xda-developers.com/showthread.php?t=2618447
Try everything in Post #1 from above... It's what you already have done.
But as soon as the phone boots from the ODIN flash. Pull the battery and do the factory reset.
I have a sph-l900 and I'm in the same boat. My recovery mode is all in red and won't go past the note 2 logo on start up. I never rooted out fear something like this happening and yet it has. I've tried every stock tar file with Odin but getting "nand start write" followed by "failed". I'm posting on here because this is the only other image I have found that looks like what I have
Surgemidnight13 said:
I have a sph-l900 and I'm in the same boat. My recovery mode is all in red and won't go past the note 2 logo on start up. I never rooted out fear something like this happening and yet it has. I've tried every stock tar file with Odin but getting "nand start write" followed by "failed". I'm posting on here because this is the only other image I have found that looks like what I have
Click to expand...
Click to collapse
Not recommended that you flash anything from this section ...
Sph-i900 is a windows phone with massive chipset differences...(omnia with win 6.1)using an intel marvell cpu)...
Flashing anything from the note 2 section will perma-brick your device....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
gregsarg said:
Not recommended that you flash anything from this section ...
Sph-i900 is a windows phone with massive chipset differences...(omnia with win 6.1)using an intel marvell cpu)...
Flashing anything from the note 2 section will perma-brick your device....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have a Sph-L900 (sorry for the misunderstanding) which is the Sprint Note 2. I was looking at this thread because the picture shows exactly the current problem my phone is having and with the same situation of not rooting it. I was looking to see if anyone had additional information since trying to flash stock rom keeps giving the fail notice on odin
Surgemidnight13 said:
I have a Sph-L900 (sorry for the misunderstanding) which is the Sprint Note 2. I was looking at this thread because the picture shows exactly the current problem my phone is having and with the same situation of not rooting it. I was looking to see if anyone had additional information since trying to flash stock rom keeps giving the fail notice on odin
Click to expand...
Click to collapse
Just curious if you ever found a solution.
mike t said:
Just curious if you ever found a solution.
Click to expand...
Click to collapse
After exhausting every possible solution people gave me or I could come across, I caved in and sent it to Samsung repair. Turns out it was hardware that needed replacing. I heard it could just be a damaged internal memory or caused by a virus, but Samsung has fixed it for $70 and I should be getting it back this week.