Hey all, I saw a similar thread to this one, however I could not seem to fix my phone using the method described by the OP of this thread:
http://forum.xda-developers.com/showthread.php?t=2791231
Anyways, just as in this other thread, I rebooted my phone and was stuck in the red verizon boot logo so I went to recovery and did a factory reset. Just as in the other thread I found that my phone was stuck on the custom samsung boot logo, normally I would just ODIN flash a stock version and go back to normal however my computer does not detect that I have the phone plugged in due to not being able to install drivers prior to flashing the new version. Is there anything I can do or am I stuck on the custom Samsung logo? I cannot enter safestrap, only ODIN mode.
ProtossPaul said:
Hey all, I saw a similar thread to this one, however I could not seem to fix my phone using the method described by the OP of this thread:
http://forum.xda-developers.com/showthread.php?t=2791231
Anyways, just as in this other thread, I rebooted my phone and was stuck in the red verizon boot logo so I went to recovery and did a factory reset. Just as in the other thread I found that my phone was stuck on the custom samsung boot logo, normally I would just ODIN flash a stock version and go back to normal however my computer does not detect that I have the phone plugged in due to not being able to install drivers prior to flashing the new version. Is there anything I can do or am I stuck on the custom Samsung logo? I cannot enter safestrap, only ODIN mode.
Click to expand...
Click to collapse
Kies can download drivers to your computer. I've never used it but I know its fairly simple.
You can also download drivers off the internet. Just Google s4 drivers and make sure it for whatever windows version you have. Ie- xp, 7, 8.
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
CheckOutMyThemedGoogleKeyboards!!!!!!
MyColorScreen
Related
I installed the latest nightly build (cm_galaxys2_full-88.zip) on my phone yesterday night and restored the all the apps through Titanium Backup. Everything was working fine until this morning I tried to create a backup using CWM recovery in Rom Manager. The phone shut down and has since been stuck on the initial boot screen (one with the Samasung galaxy S2 logo). It does not boot into recovery mode using the button combinations. I can only get it into download mode but Odin does not recognize it as I thing i forgot to enable USB debugging.
I have tried removing the battery and rebooting and also tried to access it through odin a number of times. But nothing seems to work.
What am I missing here ?
This might help?
mjondj said:
I cannot boot into recovery, but I can boot into download. However, odin is no longer recognizing my GS2 when I plug it into my PC.
The bootloop began when I was attempting to flash the cyanogen7 with the google apps.
I read every post in this thread, and have seen a number of people who cant boot into recovery, but can boot to download. I haven't seen anyone else mention that their phone is no longer recognized by odin on their pc.
Please help.
edit:
Perhaps odin doesn't see my phone because I didn't have USB debugging enabled? if that's the case, what can I do?
------------------------------------------------------------------------------------------------------------------
solved:
heimdall overwrites a driver and stops odin from seeing your phone. i attempted to remove it, unsuccesfully. but loaded odin onto a different computer (that had never seen heimdall).
i booted into download, connected to 2nd pc w/ odin, and ran CF-Root-SGS2_XW_NEE_KI8-v4.3-CWM4.tar (search forum) in PDA. this made my phone bootable again.
Click to expand...
Click to collapse
also check that you dont have kies running on your pc
icecreampop3 said:
This might help?
also check that you dont have kies running on your pc
Click to expand...
Click to collapse
Thanks. Although that did not do what I expected it to (due to some license issues), but it got me into recovery mode from where I could restore a Nandroid backup. Am back on RevolutionROM for now. Looks like CyanogenMod will have to wait for me.
I experienced the very same thing for the first time today. Had checkrom revolution and ran rom manager to backup and am now unable to boot into recovery/download. Will try to hook it to odin then
Hello
I have been using my int Gs3 for sometime and decided to root and explore the mods and custom fw world. I have started with getting to root access and after that install CWM.
Then I try to install nightly cyanogenmod 10. It didnt work and boot back to normal GS3 Touchwiz interface. After that I tried the GooManager and when the phone is restarted it went to bootloop. I removed the battery and put it back. The problem started there.
The phone does not boot to any OS, I only can see the galaxy s3 9300 black splash screen and awatis there. I can go into download mode, but when I go into recovery mode, I can see the Android robot, and it dies The screen is too fast but what I can see it cannot mount EFS, System and any folder.
So I have tried several different methods
- Tried to flash with original rom, different roms, CWM and what I can find suitable for international model. But everytime I got stucked in Nand Write part. In some of them, the flash started and stucked in installing some parts(passes the cache and hidden and stuck after that)
- Tried with bricked phone roms, different PIT files and Bootloader Vralec methods.
- When I am trying these, I have tried with 3 different PC's with/without KIES and Samsung drivers installed. When I plug the phone in Download mode, the PC recognizes it as Generic device.
- I manage to flash the CWM but when it restarts it does not go any further than the first splash screen, but in Odin, some time later it turns to pass. Funny, when the phone is on Galasy S3 black splash screen, the pc recognizes the phone and starts to install the driver.
So, here is an interesting flashing story of mine. I really would appreciate your valuable comments and suggestions.
Thanks in advance.
cugami said:
Hello
I have been using my int Gs3 for sometime and decided to root and explore the mods and custom fw world. I have started with getting to root access and after that install CWM.
Then I try to install nightly cyanogenmod 10. It didnt work and boot back to normal GS3 Touchwiz interface. After that I tried the GooManager and when the phone is restarted it went to bootloop. I removed the battery and put it back. The problem started there.
The phone does not boot to any OS, I only can see the galaxy s3 9300 black splash screen and awatis there. I can go into download mode, but when I go into recovery mode, I can see the Android robot, and it dies The screen is too fast but what I can see it cannot mount EFS, System and any folder.
So I have tried several different methods
- Tried to flash with original rom, different roms, CWM and what I can find suitable for international model. But everytime I got stucked in Nand Write part. In some of them, the flash started and stucked in installing some parts(passes the cache and hidden and stuck after that)
- Tried with bricked phone roms, different PIT files and Bootloader Vralec methods.
- When I am trying these, I have tried with 3 different PC's with/without KIES and Samsung drivers installed. When I plug the phone in Download mode, the PC recognizes it as Generic device.
- I manage to flash the CWM but when it restarts it does not go any further than the first splash screen, but in Odin, some time later it turns to pass. Funny, when the phone is on Galasy S3 black splash screen, the pc recognizes the phone and starts to install the driver.
So, here is an interesting flashing story of mine. I really would appreciate your valuable comments and suggestions.
Thanks in advance.
Click to expand...
Click to collapse
GO here : http://forum.xda-developers.com/showthread.php?t=1993044
Dear all.
First of all, thanks for your attention, I really appreciate.
I have a GNote 10.1 Wi-Fi version (N8013) with stock Android 4.1.
My S-Pen was getting me crazy, because I was not able to use it correctly on the edges of the device. I tried an app that supposed to reset the alignment, but I did not work, so I googled and found that the only way to fix it was "factory reseting" the tablet.
So, I installed the TeamWin recovery and backed up my data. After that I hit the button "reboot". But before rebooting, the recovery screen "told me" that I was not rooted and "asked" if I would like to install SuperSU to get root access. I checked YES and rebooted.
After that I got stucked at the "Samsung Galaxy Note" screen (see attached file).
I've tried to switch off the note, but the screen goes off for one second and it lights up again at the same screen.
If I plug the USB cable and try to switch it off, the note goes to the battery charging screen. If I remove the USB and push the power button again, the tablet gets back to the "Samsung Galaxy Note" screen.
Odin seems to "connect" with the tablet.
I can enter both the download mode and the recovery mode (not the teamwin recovery).
Attached pictures of what I get.
Any sugestions?
Thanks!!!
Everything is ok now
Dear all,
Hope I can help you if you have a problem similar to mine.
I remembered that a PC with no OS stops on some screen, but everything else works, just as what was happening with my note.
I tought that I might have wiped more things than I should, so, the only thing I had to do was to restore the backup that I had.
To do this I should reinstall the TWRP and the only way was via Odin.
Solved the problem this way:
1. Downloaded the Odin (http://techbeasts.com/2013/08/08/download-odin-pc-latest-version-v-3-07/)
2. Downloaded the TWRP file (http://techerrata.com/get/twrp2/p4noterf/openrecovery-twrp-2.6.1.0-p4notewifi.tar)
3. Connected the Galaxy Note to my PC using the USB cable
4. Entered the "download mode"
5. Loaded the file from step 2 into the tablet using Odin
6. Rebooted the tablet
7. Entered the recovery mode (TWRP was working)
8. Restored the backup that I had
9. Rebooted again
Did the dance of victory!!!
I am so glad to have my device back.
Regards
how to access recovery mode? mine can't access recovery mode with power+volume up :crying:
rizalabd said:
how to access recovery mode? mine can't access recovery mode with power+volume up :crying:
Click to expand...
Click to collapse
Hi all
mine neither.. followed your steps with odin but still stuck in start screen (Samsung Galaxy Note 10.1). By the way mine is the 8010. I tried almost everything. Cant even load the recovery mode!.... And Have no backup either.
PLease someone help me...
Thank you in advance
I have an SM-P600
My Note 10.1 2014 Edition is stuck on the tablet title screen, not sure if its in reboot mode it returns to this screen if I try to shut it off... basically Its frozen, and when I try to shut it off it goes away a few seconds and comes back. This happened after I rooted with KingRoot, and tried to Flash a ROM, Im a complete Noob and should have done my homework... but I didnt. I see everyone suggesting odin and going into download mode... I can get to download mode but I am using a macbook pro, and there are very little options to use odin, I tried Jodin3... and Heimdall... no luck...
PLEASE HELP !
HELP stuck on Samsung screen
I didn't any root or install a different firmware to mine.
But after charging it I removed the cable and it rebooted and got stuck on the Samsung screen. I can only access to Download mode. I didn't have any Recovery mode installed, and now I can't install one successfully via Odin...
I tried to install a new firmware... a recovery mode... nothing is working...
Please I need HELP...
@ agelcer: Was your tablet rooted?
Hello. I havea similar problem with my note 2 phone. It will not get past the
samsung screen. My cpu knowledge is very limited. Are you open to accepting payment for attempting to fix my cell phone? All I want is the pictures off of it if that is all you can do to it. Pleass email me at [email protected] if you or anyone you know can help. Thanks....Jay
Same thing is happening to mine. I tried Odin but after the download the srceen goes black and then comes back to the Samsung Galaxy Note 10.1 screen.
Hello folks.
Same problem here with a n8000.
It had the stock unrooted rom probably JellyBean.
Can only access Download Mode, nothing else.
I get connection to Odin, tried to flash original firmware, 4 file firmware, re-partition with pit file, flash a custom recovery, all seem to pass through but nothing changes, still stuck on 'Samsung Galaxy Note 10.1' screen, never moves on to boot animation and still can't access Recovery Mode.
However, something else I triy with Odin and it FAILS is ticking 'Nand Erase All'. It won't let me erase nand.
Could this mean some kind of memory corruption?
Does it have anything to do with EMMC?
If it does, is there a possible way to fix without replacing the hardware?
What else can I try before giving up?
It would be nice if other users who report this problem attempt to Nand Erase All and see if it also FAILS..
Thanks alot and sorry for the long post.
Edit: after posting I found this which is PROBABLY THE SOLUTION for me.
And here is another topic on this issue.
did you find the solution?
giba_fernando said:
Hello folks.
Same problem here with a n8000.
It had the stock unrooted rom probably JellyBean.
Can only access Download Mode, nothing else.
I get connection to Odin, tried to flash original firmware, 4 file firmware, re-partition with pit file, flash a custom recovery, all seem to pass through but nothing changes, still stuck on 'Samsung Galaxy Note 10.1' screen, never moves on to boot animation and still can't access Recovery Mode.
However, something else I triy with Odin and it FAILS is ticking 'Nand Erase All'. It won't let me erase nand.
Could this mean some kind of memory corruption?
Does it have anything to do with EMMC?
If it does, is there a possible way to fix without replacing the hardware?
What else can I try before giving up?
It would be nice if other users who report this problem attempt to Nand Erase All and see if it also FAILS..
Thanks alot and sorry for the long post.
Edit: after posting I found this which is PROBABLY THE SOLUTION for me.
And here is another topic on this issue.
Click to expand...
Click to collapse
i am looking for any solution since two years without any benefit. did you find any?
chozex said:
i am looking for any solution since two years without any benefit. did you find any?
Click to expand...
Click to collapse
I assumed from my searches the solution would be JTAG or replace the EMMC.
Since I don't have the resources for any of those, I just abandoned it to the dust and rust..
bootloader
Is this after the boot loader is updated?
osirisx69 said:
Is this after the boot loader is updated?
Click to expand...
Click to collapse
I'm not very clear about bootloader upgrading, but I guess it was included in the 4 file firmware I tried flashing and it said 'success' but nothing changed..
I think it ain't just a softbrick since I can't erase nand..
What's your background, osirisx69?
This happened to ours as well just today. Unplugged it rebooted it and it's stuck. Can only access the Odin mode.
Sent from my XT1254 using Tapatalk
i got same issue at last 4 months
just try reset then got same issue.
Same problem for 3 months. Guys have anyone tried jtag flashing firmware as in this post which was provided earlier?
Hello,
Some threads with similar issues are already around, but I didn't find one with the same problem as me.
What I was doing when the issue happened:
I was trying to install cyanogenmod from the isntaller method (apk isntalled on the phone, application running on windows that installs it automatically). At certain point, it rebooted the device and the cyanogenmod logo was on the screen. After a while, the program gave an error "'We couldn't talk to your phone' - Samsung devices ONLY", which is described in their wiki. So the pc lost connection to the phone.
What I did:
1 - Since I had installed the clockwork recovery and tested it before, I thought "hey, no problem. I'll hust recover this S*it". So I disconnected the SIII from the PC and tried to enter recovery mode pressing "volume ip + home + power". While I have these pressed, the phone in in an infinite loop on the initial screen showing the brand and model. When I release them, it goes straight to the cyanogenmod blue creepy robot just there staring.
2 - Since that didn't work out since I now don't have a recovery mode and I don't have any functioning rom either, I found several tutorials for using Odin and reflashing and or repartitioning. PROBLEM: Odin seems to recognize the phone (com port), I click on the option and... FAIL!
2.1 - What I have tried: Different Odin versions (1.83 and 3.09), stock drivers from Kies, Zadig drivers.
So. There you go. I pretty much exhausted everything I could get from my head and interpret from google. So, No recovery, no ROM, fail at odin.
Any ideas?
Thanks in advance.
Remove kies from the pc reinstall drivers and flash a cwm recovery. From there flash a custom rom in recovery from ext sd. Odin 3.04 is good. I would keep trying to get into recovery though. Do you have that red mark in the corner on Sammy splash screen?
My phone is a verzon note 2 on deodox 4.3 with twrp recovery. The phone only boots to teamwin logo and flickers on and off. my computer will not recognize my phone either at this point.This is what happened. Ive been having some 4g lte loss and unstable wifi issues to i decided to do a factoty reset. when i rebooted into recovery i was stuck at the twrp logo and it would constantly bootloop the twrp logo.. I restarted my phone and did a factory reset from under the general setting. At that point it rebooted int the twrp but continued to just stay at the logo and would not go into recovery. I pulled the battery and restarted the phone but from that point on it would only boot into the twrp logo and stay there. I can get into download mode but my pc (win7) no longer recognizes the phone so i cant attempt to fix this in odin. Im not sure what to do to get this phone to work properly at this point.
yoda254 said:
My phone is a verzon note 2 on deodox 4.3 with twrp recovery. The phone only boots to teamwin logo and flickers on and off. my computer will not recognize my phone either at this point.This is what happened. Ive been having some 4g lte loss and unstable wifi issues to i decided to do a factoty reset. when i rebooted into recovery i was stuck at the twrp logo and it would constantly bootloop the twrp logo.. I restarted my phone and did a factory reset from under the general setting. At that point it rebooted int the twrp but continued to just stay at the logo and would not go into recovery. I pulled the battery and restarted the phone but from that point on it would only boot into the twrp logo and stay there. I can get into download mode but my pc (win7) no longer recognizes the phone so i cant attempt to fix this in odin. Im not sure what to do to get this phone to work properly at this point.
Click to expand...
Click to collapse
My guess is that when you rooted with CASUAL, it changed the Samsung device driver on your computer and you need to reinstall the Samsung driver to get the computer to recognize the phone again in download mode.
Underneath step 7 of section 1b on Droidstyle's restore guide, he discusses issue with CASUAL replacing the Samsung driver... and he gives a link to Jeremy Loper's fix... "If odin no longer recognizes your device, most likely Casual killed the driver for odin!! follow this tutorial for restoring the driver: http://www.youtube.com/watch?v=zzghcV8HVVk"
Once the computer recognizes the phone again, you should be able to use ODIN to restore back to 4.1.2 so you can root/unlock again with CASUAL. After you get the phone restored with Odin, I would recommend booting into Stock Recovery and wiping cache/doing factory reset before running Casual again... this would enure you are starting over with a totally clean slate.
If the above doesn't work, then here's a thread where I tried to help someone else who couldn't get their computer to recognize the phone.... maybe some of those ideas will help - http://forum.xda-developers.com/showthread.php?p=55833998
Good luck!!
1 step forward two steps back. I got my pc /odin to recognizes my note 2(changed usb cords). Then tried to odin back to stock 4.1.2. At first odin kept saying (odin not responding) and would ask to close the program,after several attemps i final got it to flash the 4.1.2 file. When i flashed the file and was at the point where it reboots, it would not get past the samsung note 2 logo and continued to flicker and not boot up even when i tried to put it into download mode like it said to in this thread. http://forum.xda-developers.com/showthread.php?t=2024207. When i tried to reflash the file it failed. when i attempted again it just hangs at setupconnection. Tried again and it failed. Btw thanks for the help mattnmag.
Got it working! i simply forgot to place the sch-i605 pit. into the pit section of odin when i flashed the 4.1.2 rom.
Similar problems
I was running AllianceROM 26. My phone had been spontaneously rebooting for a bit recently. Today, it started to spontaneously reboot again, but this time, it never got past the Galaxy Note 2 screen. After pulling the battery, I tried to boot into TWRP. It just hangs on the twrp boot screen for a few minutes but never goes into twrp.
I figured I would try taking it back to stock. So, I used ODIN to try and put 4.1.2 on it and a new PIT file. That appeared to work fine. I got no errors in ODIN. However, I still cannot get this thing to get past these boot screens, either the Galaxy Note 2 one or TWRP when I try that there. I have tried this twice now, once with re-partition checked and another time with re-partition unchecked (saw conflicting instructions on that so I figured I would try it both ways). I still am not getting past the boot screen.
Any help or ideas are appreciated as right now, my phone appears to be bricked and I am out of ideas.
so what was the solution to the teamwin flashing on and off after a factory reset? this is certainly not a solution, having to reflash the phone...