[help] stuck in download mode - Verizon Samsung Galaxy Note II

tried to unlock bootloader....i have already done this successfully on another device.
i went through all the steps and after the last step the phone booted into download mode instead of recovery.
I have tried to odin back to stock but no matter what i do it boots right back into download mode.
Any ideas?

EDIT!
seems like the bootloader prep file i flashed on my laptop windows 8 was corrupt. not sure
I flashed the bootloader prep file again. Got the funny take your device to verizon screen. Flahsed stock again and IT BOOTS!!!!
but now i have one on the flash counter. oh well it works.

Related

[Q] Bricked photon?? Help me get it back, please?

I cant get it to boot in recovery(CWM) It comes up a big list of RSD BP Tools all that in a single page in white text when i try to enter recovery or any mode. And i cant get the RSD Lite drivers to install!! I already have used RSD lite 2 days ago with my phone. I managed to get phone into RSD mode once but it still wouldnt show up under the actual RSD Lite program, and it came up saying it failed to install drivers. It fails to install the driver "NS Flash Sunfire" and ive looked around and cant seem to find it anywhere.. I can get the phone into RSD mode fine, but it wont boot to CWM recovery, apparently something went AWOL. Tell me how i can get my photon back please?!
try removing all your motorola drivers and reinstalling them from yay 4 juggs link. you should be able to flash the sbf from his thread (in rsd mode) and be back in business.
Didnt even think of that.. i already had the 5.21 drivers installed, but sure enough did what you said and im flashing back to stock sbf right now. THANK YOU!
OK, so i just flashed 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_6-CM-release-keys-signed-Sprint-US and now im stuck in a bootloop of the dual core screen.. Any ideas..? I know its not latest SBF, but the link for latest was dead.. So i just used this one i had on my desktop already. Anything im missing here?
EDIT: Oh yeah, the flash went through fine and said completed, and when i boot into recovery its back to stock recovery of android triangle and my bootloader menu system is how it should be again. Im just stuck in a boot loop.. Can i go ahead and like unlock bootloader and install CWM and get back on CM7 or will i most likely still be in a bootloop even after that..? Any insight would be great
w0lf215 said:
OK, so i just flashed 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_6-CM-release-keys-signed-Sprint-US and now im stuck in a bootloop of the dual core screen.. Any ideas..? I know its not latest SBF, but the link for latest was dead.. So i just used this one i had on my desktop already. Anything im missing here?
EDIT: Oh yeah, the flash went through fine and said completed, and when i boot into recovery its back to stock recovery of android triangle and my bootloader menu system is how it should be again. Im just stuck in a boot loop.. Can i go ahead and like unlock bootloader and install CWM and get back on CM7 or will i most likely still be in a bootloop even after that..? Any insight would be great
Click to expand...
Click to collapse
you may need to factory wipe to get it to boot up... are you stuck on the dual core or the sprint now screen? it may be a bad flash as well - did it reboot by itself and such?
Im at the Dual core screen, i reflashed same sbf and its still doing same thing. ONE time it boot through the sprint now boot logo stuff, then just fell back into same old loop of just the dual core boot animation/screen. How can i factory reset it..? It rebooted right after it installed(never successfully into OS though) then RSDLite told me to manually power up phone, so i battery pulled and powered up to just have it go into moto dual core boot screen loop
Ok sweet i just unlocked bootloader and installed CWM and was able to restore to my CM7 backup fine! Im not activated atm, going to have to call sprint i guess.. But everything else looks to be working!!

Need help with RE-ROOT SGS3

I am following the instructions at: http://forum.xda-developers.com/showthread.php?t=1726088
I already did it once. Worked perfectly, very simple. I then unrooted my phone because I was planning to return it (then decided to keep it).
Now I'm trying to re-root the phone using the same exact instructions. I've followed the instructions about 50 times and I cannot get the phone to boot in CWM based recovery. It keeps going back to the Android Recovery mode even though Odin says Pass! and Successful and everything appears normal when I load the clockworkmod.TAR in PDA.
I am so frustrated - it is incredible. I have factory reset and wiped the cache. I reinstalled the Samsung drivers. I re-downloaded Odin. I re-downloaded the TAR. I follow the instructions exactly as I did it before. But whatever I do, it will not load in CWM recovery mode.
Any possible explanations?
EDIT: Out of sheer desperation I tried renaming clockworkmod.TAR to clockworkmod.tar and WALLAH! Worked on the first attempt. Very bizarre.
Please delete thread if possible
evoman44 said:
I am following the instructions at: http://forum.xda-developers.com/showthread.php?t=1726088
I already did it once. Worked perfectly, very simple. I then unrooted my phone because I was planning to return it (then decided to keep it).
Now I'm trying to re-root the phone using the same exact instructions. I've followed the instructions about 50 times and I cannot get the phone to boot in CWM based recovery. It keeps going back to the Android Recovery mode even though Odin says Pass! and Successful and everything appears normal when I load the clockworkmod.TAR in PDA.
I am so frustrated - it is incredible. I have factory reset and wiped the cache. I reinstalled the Samsung drivers. I re-downloaded Odin. I re-downloaded the TAR. I follow the instructions exactly as I did it before. But whatever I do, it will not load in CWM recovery mode.
Any possible explanations?
Click to expand...
Click to collapse
Cable is bad...? Try different one....
Sent from my SPH-L710 using xda premium

[Q] I dont know what the problems is?

Hi, so I've been flashing for a while now on my phone and my friend wanted to root his phone so i agreed to help him out. After flashing multiple files in order to get cwm recovery and just get everything working, the phone started to act up.
Here are the problems:
Phone can boot into stock recovery but i cant flash anything from it
i wiped data/factory reset many times.
i tried to install the cwm kernal by applying update from sd card (I followed the install custom recovery instructions from here: http://wiki.cyanogenmod.org/w/Install_CM_for_i777) but when into recovery to flash, 2 red signs come up saying "E: Failed to verify whole-file signature" and "E: signature verificatoin failed" after this is just aborts the process
i tried download mode, but none of my computers recocgnize the phone (2 computers) i have tried all usb ports, reinstalling usb drivers, different usb ports many times but all have failed
if i try to boot, the phone just stays stuck on the Samsung galaxy s2 logo (no triangle? even though its rooted)
my only option is to hang out in recovery, i have a bunch of files saved to an external sd card but i cannot access that from stock recovery
any help would be appreciated, Thanks
You can not install any unsigned files with stock 3e recovery, as you have discovered. That is normal behavior.
I don't know why performing a wipe data/factory reset from 3e recovery does not clear the phone to boot normally. It should. But since it won't...
You will need to get the phone recognized by a computer, and then flash with Odin, or you could try flashing with Heimdall command line. I would suggest that you flash the full stock plus root I777UCKH7 (2.3.4), and then when it boots normally into the system, install Mobile Odin Lite or Mobile Odin Pro, and use that to flash a custom kernel. You can find the stock firmware in the Download Repository, and the basic directions in my guide, both of which are linked in my signature.
creepyncrawly said:
You can not install any unsigned files with stock 3e recovery, as you have discovered. That is normal behavior.
I don't know why performing a wipe data/factory reset from 3e recovery does not clear the phone to boot normally. It should. But since it won't...
You will need to get the phone recognized by a computer, and then flash with Odin, or you could try flashing with Heimdall command line. I would suggest that you flash the full stock plus root I777UCKH7 (2.3.4), and then when it boots normally into the system, install Mobile Odin Lite or Mobile Odin Pro, and use that to flash a custom kernel. You can find the stock firmware in the Download Repository, and the basic directions in my guide, both of which are linked in my signature.
Click to expand...
Click to collapse
The hardest part about this is getting my computers to recognize the phone
i guess i shouldve mentioned this earlier, i attempted to flash in Odin but it was stuck on zImage so i unplugged it
before i flashed in odin, i used to be able to boot into the phone like touchwiz and whatnot, now it just gets stuck on the samsung galaxy s ii boot logo
This is now [Solved}! thanks for the help creepyncrawly! i figured it out after doing some more reasearch online. apparently, youre not supposed to use the charger wire that came with the device since samsung doesnt want to waste their time on creating a good enough cable for this kind of stuff. so i grabbed some random cable that i found in my house, hooked it up and BAM! both of my computers were able to detect my phone just finished flashing bone stock on the phone thanks
I noticed in your post that you tried everything but another cable. But I'm glad you got it working. I had the same problem before too. Cables are finicky little things.
Sent from my SGH-I777 using xda app-developers app

[Q] Custom Recovery problem (Rom manager-cwm)

im on stock root and i wanted to hopefully flash a rom, but first i needed a custom recovery. On my phone, i downloaded Rom manager and it asked me to install cwm. it found my device and it downloaded and said installed successfully. i rebooted into recovery and from there it loops and boots into recovery non stop. i remove the battery and put it back in and it still tries to boot into recovery with the loop. (Semi-fix) when i remove my battery and boot into download mode. i can cancel it and it will skip trying to boot into recovery and load just fine. i can then shut down or restart as needed. but booting back into recovery will start the issue over again. i just want to know a safe way to have cwm on my note 3, or how to revert it back to normal. any help please?
scarface195894 said:
im on stock root and i wanted to hopefully flash a rom, but first i needed a custom recovery. On my phone, i downloaded Rom manager and it asked me to install cwm. it found my device and it downloaded and said installed successfully. i rebooted into recovery and from there it loops and boots into recovery non stop. i remove the battery and put it back in and it still tries to boot into recovery with the loop. (Semi-fix) when i remove my battery and boot into download mode. i can cancel it and it will skip trying to boot into recovery and load just fine. i can then shut down or restart as needed. but booting back into recovery will start the issue over again. i just want to know a safe way to have cwm on my note 3, or how to revert it back to normal. any help please?
Click to expand...
Click to collapse
Pull battery let it sit for two minutes. Push menu button, volume down button, and power button at the same time boot into download mode. once there flash a fresh copy of your OS which ever version of KitKat your running. You lose all your personal data, but your beyond that now. Then here is link to my thread should answer all your questions http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 enjoy !!!
uknow said:
Yeah ive said it a few times this should not be used
If youve bricked your phone you can get back into your phone by holding volume down menu botton and power botton at the same time when it pops up the warning screen to enter download mode hit cancel your phone will then boot up after your phone is on if you do not have a computer the way you fix the phone so you dont have to do this every time your phone is off you need mobile odin and a kitkat cwm.img.tar for our phone flash it and problem solved you can now boot into cwm recovery then if you want you can flash a twrp img zip through cwm or just keep cwm hope this helps
Ps if you Google mobile odin the dev gives it away on his xda mobile odin page
Click to expand...
Click to collapse
.............^^^^^^...........
stuck in recovery loop also
hi i am new to all this..i managed to get my sprint note 3 4.4.4 NK4 rooted and i read that i also needed a custom recovery so i used odin to install "philz_touch_6.08.7-hltespr.tar.md5" and it said success but when i tried to get into it it just says recovery is not seandroid enforcing i also used rom manager to get into it automatically but it just keeps looping saying same thing. is there a way out of this mess?
update-- i found an updated version of the philz tar file and installed it with odin and that got me out of the loop..just havent tried to get back into recovery yet...lol
Cat1970 said:
hi i am new to all this..i managed to get my sprint note 3 4.4.4 NK4 rooted and i read that i also needed a custom recovery so i used odin to install "philz_touch_6.08.7-hltespr.tar.md5" and it said success but when i tried to get into it it just says recovery is not seandroid enforcing i also used rom manager to get into it automatically but it just keeps looping saying same thing. is there a way out of this mess?
Click to expand...
Click to collapse
First, pull the battery for a minute then reinstall hold the power, menu, and volume down buttons at the same time and boot into download mode. The version of Phil'z CWM you flashed is to old for 4.4.4 NK4. Now download to your desktop the right Philz CWM recovery file (Phil'z_Touch_6.48.4-hlte.tar.md5 ) here is the link https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hlte/ there are two listed use the second one. Flash with odin and you should be good to go. Go to my thread http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 for more info.
done exactly as you said and the same screen came up saying recovery is not seandroid enforcing and then it jumps to Philz Touch 6 so im assuming everything is right now...i really appreciate the help! tyvm
different rom
ok..i installed cyanogen rom..i also used titanium backup..i want to go back to where i was but i dont see titanium backup on there anymore..how do i revert back?
i guess i need to update my phone n900p (help)
my rooted note 3 was running 5.0 L so i tried flashing a custom recovery both TWR and CWM now its stuck in boot loop. i read all the post showing you how to get out the bootloop. how ever i still need to put a recovery on my phone are there any updated links for this with odin because i was using the odin 3.0 sorry odin 307

Bricked? I cant figure this out!

Hi, I have a GS4 (SCH-I545) and I tried to get TWRP and then CyangenMod, so I rooted my phone, used ROM Manager to get TWRP, rebooted into recovery, only to get the stock recovery. So I tried Flashify, rebooted, but got the Verizon warning screen, so then I used the workaround to get back in to my phone. I then tried again but then I couldn't get bacl into a recovery mode, just odin mode with "Could not do normal boot" in the top left. So I did the workaround again, I then figured something was wrong with the bootloader, so I used Flashify to flash "a-boot.img" hoping it would work, now I can't get into recovery mode, can't get into Android, can't even charge my phone, the odin mode will always come on, I can go intpo normal odin mode though, but that's it, I can't do anything on my phone, only go into odin mode, so I guess I've bricked my phone. What should I do?
SolidSG said:
Hi, I have a GS4 (SCH-I545) and I tried to get TWRP and then CyangenMod, so I rooted my phone, used ROM Manager to get TWRP, rebooted into recovery, only to get the stock recovery. So I tried Flashify, rebooted, but got the Verizon warning screen, so then I used the workaround to get back in to my phone. I then tried again but then I couldn't get bacl into a recovery mode, just odin mode with "Could not do normal boot" in the top left. So I did the workaround again, I then figured something was wrong with the bootloader, so I used Flashify to flash "a-boot.img" hoping it would work, now I can't get into recovery mode, can't get into Android, can't even charge my phone, the odin mode will always come on, I can go intpo normal odin mode though, but that's it, I can't do anything on my phone, only go into odin mode, so I guess I've bricked my phone. What should I do?
Click to expand...
Click to collapse
Well, first of all, if your galaxy didn't have the MDK bootloader (first version of firmware, android 4.2.2) you are not able to get CM nor Recovery (CWM, TWRP...), because Verizon locked the bootloader in all the other versions. If you touched our "lovely" bootloader you could have messed up your device, but you can get into download mode so you should try downloading a stock rom equal or newer to the android version you used to have before you bricked your device (you cannot downgrade your phone), if that doesn't work you can try Samsung Smart Switch to repair it.
Okay ill try downloadig a stock rom, but I don't really know how to do it, got any links telling how?
Well, we can't point you to a stock ROM to odin with. You can't just simply Odin back to MDK. That has been blocked off by a physical qfuse, which will further mess up your device. Can you get into download mode and tell us what version do you have?
All download mode says is this: odin mode
Product name: SCH-I545
Current binary: Samsung Official
System status: custom
CSB-CONFIG-LSB: 0x30
Write protection: Enable
eMMC BURST MODE enabled
Nothing about the version
Id say the version I have was later than 4.2.2 considering I couldn't get a recovery working, the previous owner updated it some time in early 2014 maybe june so any version of KitKat later than that might work

Categories

Resources