Okay so here's the chain of events. I had hyperdrive 10 and I saw the update to 18 was out. SO I downloaded and proceeded to install. It didn't work so I went to follow the instructions to update to nc5. downloaded the new safestrap went into the safestrap menu. deleted all OS. And installed the new NC5. Went to download mode. And I kept getting PIT not found then would disconnect. Attempted to ODIN a recovery rom. Didn't work. Download a PIT. didn't work. And finally I downloaded a stock rom and it will not install on recovery mode. Please help...
EDIT: I got it to move into restore from kies mode. And I have attempted flashing multiple roms via odin. They all fail after attempting aboot. I don't know what version I was on so I'm not sure what stock rom to download/flash.
I think I found a thread that might have helped me out... Will report back in the morning if any success
I'm in the same boat, the recovery thread http://forum.xda-developers.com/showthread.php?t=2735172 is not working for me...
Related
Ok so i had ICS passion installed then one day the rom gave me an error telling me encryption unsuccessful. So i followed the instructions to fix it, by putting the partition on the micro sd card (8gb). I then decided to flash back to stock gingerbread with odin. I thought that if I put a galaxy s international rom on the US vibrant it would work, but i was wrong so dont try that. I was stuck on a bootloop and was able to get to download mode. Then i used Odin to flash JFD for vibrant it said i passed but when i booted it did the same. Now im on KB5 and it gave me android system recovery <3e> but i have an error dev/block/mmcblk0p1.
I cannot go to menu, i can access download mode and android system recovery, i also tried to install update zip but it gave me the signature fail.
Please help me back to stock firmware or any stable version. Thank You
http://forum.xda-developers.com/showthread.php?t=1278683 follow the instructions in the thread and remember to flash the bootloaders
You should just Odin back to JFD and go from there. Flashing bootloaders is dangerous, shouldn't be done lightly, but can be done with caution if needed, usually isn't.
try the 1click root method. see if that helps.
Ok so i had ICS passion installed then one day the rom gave me an error telling me encryption unsuccessful. So i followed the instructions to fix it, by putting the partition on the micro sd card (8gb). I then decided to flash back to stock gingerbread with odin. I thought that if I put a galaxy s international rom on the US vibrant it would work, but i was wrong so dont try that. I was stuck on a bootloop and was able to get to download mode. Then i used Odin to flash JFD for vibrant it said i passed but when i booted it did the same. Now im on KB5 and it gave me android system recovery <3e> but i have an error dev/block/mmcblk0p1.
I cannot go to menu, i can access download mode and android system recovery, i also tried to install update zip but it gave me the signature fail.
Please help me back to stock firmware or any stable version. Thank You
Hey guys, I dug out my old i605 the other day and wanted to update to the latest cm nightly for the device. Not realizing I was about to do something wrong, I downloaded an app called Flashify and installed the latest cm recovery through the app. Well this made my device boot loop. So now, I need to flash a working recovery to my device to fix it. After googling for a bit, I learned that I need Odin to do so. So I am now using Odin v3.10.7. But, I cannot get any recovery tars I've found to flash. They all come back as failed. I'm at a loss here and hope someone knows how to get this thing back up and running.
My PC is on Windows 10 and I do have the latest Samsung drivers installed. On my Note 2 in download mode, it says my current binary is Samsung Official and my system status is custom. What I do not know is what recovery and firmware my i605 was on previously.
Thanks guys
EDIT: I guess what I'd really like to do is get the device back to stock rooted.
Edit 2: Fixed the problem. Uninstalled the Samsung drivers and reinstalled them and changed to Odin 3.07. Ended up restoring the device with the unlocked bootloader restore here: http://forum.xda-developers.com/showthread.php?t=2040264
I lost TWRP not sure how but I did. I was going to flash my old OC1 to to tmobile so I could have a backup. I loaded all the roms and apks. to the phone and realized i was missing TWRP.
I downloaded TWRP in the ap store and tried to install it. It gave me root access and said it installed it. I turned on the phone and it failed to find he recovery. I tried to install over and over and kept trying previous versions. I think at around 2.8.7 it started booting only into down load mode. I can no longer get into recovery only into download mode. how can I get back to an OS?
Uhhh.. you are only able to flash/install twrp or any other custom boot with MDK and that was several revisions back.. There are dozens and dozens of thread stating this. your are going to have to use odin to reinstall your bootloader/system there are tutorials in the "Help & Troubleshooting" where this probably should have been posted for you to get a the best chance of help.
There is also a few YouTube videos covering the process using ODIN
I recently soft-bricked my SCH I545 and have been trying to restore through Odin. I had SafeStrap installed and was running a custom rom (I don't remember which but I think it was the S5 variant) when I decided to try and upgrade it to the 7.1 rom that just came out. I got a bootloop after flashing the 7.1 and figured that I would just wipe and restore the backup but realized too late that the backup wasn't saved on the external and got wiped. I've tried a bunch of different tar files (MK2, MDK, ME7, and MI1) but they all fail at aboot.mbn which I have read means that I am trying to flash an older rom. Hence the question about the latest .tar files? Also, I can't boot into recovery (I guess I wiped that) and can only boot into Odin. When I either try to boot normally or into recovery it goes into Odin and gives me an error message saying that the firmware needs to be updated through Kies. I've been digging around for a good couple days and figured it was time to ask. Please direct me appropriately if this has already been solved elsewhere.