Once Odin finished, I pulled the battery out, then put it back in then went straight to recovery mode. Still stock Android recovery loader.
Nevermind admin, u can delete this. Download was corrupt second mirror made it work
Related
I just accepted the cyanogen 10 snapshot update today for my d2spr; after the update finished it left me stuck in a bootloop, and Im unable to access recovery! I want to go back to the rom I was at before the update, which was the cm-10.1.3. Please help!!
Download mode and flash a custom recovery tar
CNexus said:
Download mode and flash a custom recovery tar
Click to expand...
Click to collapse
Thanks for the reply, I just downloaded a stock rom from samsung, and flashed via odin. It was successful, however even with the stock rom, I am still stuck in a boot load, and it still wont let me into recovery mode....
Solved!!
So I finally solved the issue. After I had flashed the stock rom via odin, I needed to find away to wipe cache's and do a factory reset. I finally accomplished this by downloading the .pit file, and re-flashing it together with the stock rom all through odin. After doing so, I was finally able to get into recovery, wipe, and do a factory reset. For anyone else having this issue, here is a link where I found the .pit file, and a thread with some basic instructions:
:laugh:
PIT Files: http://d2tehp.chickenkiller.com:22222/pits/
Basic Instructions: http://teamuscellular.com/Forum/topic/3882-pit-files-for-all-us-variants-of-sgsiii/
Help. I think I bricked my phone. I was running S3Rx 3.0 with JB4.3 on my T999 GS3. I attempted to update the rom to its latest version 3-20-14. I made a nandroid backup. I wiped cache and dalvik and then tried to install the zip file in TWRP, but it said install failed. I tried again with same failed results. I then did a factory reset, wipe cache, dalvik, data and system. I tried to flash the zip file and it failed again. So giving up on the failed update, I then restored my nandroid backup. After the restore was complete, I rebooted the phone and it got stuck at bootup with the Samsung logo and the blue LED light. I let it sit for over 15 minutes and it was still stuck there. I powered off the phone and went back into TWRP recovery and repeated the restore and reboot again, and it was stuck at that same part for over 15 minutes. Should it take that long? I've done backups and restores in the past and I don't recall it having take that long to bootup.
Does anyone have any suggestions? Please let me know if you need more explanation. Thanks in advance.
Try using odin to update the recovery system and flashing a rom.
Sent from my SGH-T999 using Tapatalk
It's been a long while since I used odin. I want to get the steps right before I risk further damaging my phone. Should I download odin and latest TWRP tar file to my pc. Put my phone into download mode and go thru the odin process...run as admin, placing tar file in pda... Then do I reboot into recovery mode? From there I'm not sure what to do. How do I flash a rom to my phone? Do or can I download a zip file via odin? One other option I thought of is to odin root66. So am I actually downloading 2 files via odin? Sorry for my confusion.
Ok, so I odined root66. My phone initially booted up to stock, but I got a pop up "unfortunately system ui has stopped". I went to recovery mode to do a factory reset. It took me to android system recovery. Apparently i lost my TWRP recovery. I did a factory reset and rebooted. Hallelujah!! my phone booted up into stock successfully. Whew...
Cool.
Sorry I couldnt respond earlier, I just woke up.
I always keep copies of odin flashable packages for the latest cwm and twrp recoveries just in case some craziness happens.
Ive had a similar issue when dualbooting. Recovery seemed to work 100% but one bad flash sent me into a bootloop I couldnt get out of. Booting to recovery just tried booting my corrupt 2nd rom and I had to odin cwm on to stop the boot script from locking me out of recovery.
Sent from my SGH-T999 using Tapatalk
All part of the hazards of tinkering with the phone. It goes with the territory. But as long as I can get into download or recovery mode I believe there's always a fighting chance.
Separately I reinstalled TWRP via odin. Next will be to reflash the custom rom.
Odin success on each version NB4,NE6 and OB6
Everything goes through smoothly, but it gets stuck on "rebooting to recovery" and never actually gets to recovery
I've flashed twrp,stock recovery img,chainfire, phils, none will actually boot
got this device from a person who said they tried to flash a custom rom and got it into this boot
all I can think of is to repartition the device, but cannot find a pit file that works
odin mode says write protection: enabled
if that is of importance
also tried the unbrick images on sd card, no luck
is there a way to make a bootable recovery.img sdcard? like how nooks can
made a pit from a working note 3 tmo, repartitioned, no go
What you are saying is that you odin successful, and it will not go into recovery, even if you force it to? After the rom image flash, are you in download mode and trying to flash a working recovery?
AxAtAx said:
What you are saying is that you odin successful, and it will not go into recovery, even if you force it to? After the rom image flash, are you in download mode and trying to flash a working recovery?
Click to expand...
Click to collapse
yes odin completely finishes, I tried forcing into recovery mode
loaded twrp,philz recovery, cwm, older versions of recovery, the current version etc.
no longer have the phone but still wonder why it was a no go
I installed root from here:
http://forum.xda-developers.com/showthread.php?t=2421594
i installed custom recovery twrp and i did something wrong with odin, now it's stuck on boot screen and i can't go in recovery mode anymore. I have the original firmware and odin ready but i can't get in recovery/install mode.
Another thing, i downloaded odin from odind*** the first odin download that shows up on google, but it doesn't look like it's he official page, is the files on there safe?
Bumping this thread for help.
Still need help.
update.
I managed to get into recovery mode and did a factory reset and wipe. Device is still stuck on boot screen and keeps rebooting.
Try the guide here.
And when you flash TWRP, uncheck the auto reboot box in Odin. After it flashes, unplug and power off tab. Then boot to recovery, that should work
Today I tried using the SkipSoft Toolkit to install a custom recovery and root my note 2. I followed the instructions (installed USB drivers) then i got to the part to install custom recovery with odin. At this point i noticed the program was failing to but my phone into download mode. Yet it was moving on and launching odin and pretending everything was ok. Even odin recognized the phone. I don't know what to do so i tried to flash twrp. It failed. I then manually went into download mode. Tried again and it failed. I closed everything. I manually launched odin and went into download mode and flashed twrp. This time it worked. After rebooting i went to recovery and i noticed it was stock recovery. SkipSoft warned me about some phones reflashing stock recovery and that i needed to flash a custom recovery and go into it before the phone boots then flash a permanentrecovery.zip file inside the custom recovery so it stayed that way.
I went into download mode again, i flashed twrp again, but i forgot to disable the auto-reboot setting. I quickly hold power+upvol+home to try to get into the recovery instead of booting normally. I don't know if that was the problem or something else, but my phone got stuck in a bootloop. I can't enter recovery and only download mode. I tried reflashing recovery with odin in download mode but i noticed it was getting stuck and the process didn't even start. I reinstalled the drivers and now my computer or odin are not even recognizing the phone anymore.
Any ideas on what the problem could be or how to fix this?
TL/DR: Phone stuck in bootloop, can't access recovery only download mode but computer doesn't recognize it even with the samsung drivers installed anymore.
It was the usb cable. Apparently usb cables that come with chargers are not good. Good to know.