I've been trying to find an answer on this forum and on google but I cannot find anyone with a problem similar to mine.
All of a sudden after trying to update CWM, (failed), I cannot go into recovery anymore.
I know the button combinations and have previously done it before but now it just vibrates and displays the Samsung logo.
If I try and use an app to boot into recovery mode it soft bricks the phone I believe (does not boot and I have to get it into download mode to
flash the system.img).
Does this mean that I have no recovery?
Yes. It means you have no recovery. I would suggest flashing TWRP with Odin.
Sent from my SGH-I717D using xda premium
I tried to flash TWRP using Odin but after the Check status, Odin is crashing and force closes. I tried installing CWM but the progress bar seems like it is stuck on 0%.
I'm not quite sure how to fix this. I am trying to install CM10 but this is the first android I have had.
It's rooted but everything is stock. I am not sure if I need a custom kernel also.
Is your phone a Canadian version? There's an extra step needed when you flash a custom recovery.
It's just an American version
try this and flash cwm-touch-i717-120414.tar.md5 with odin if twrp does not work, then download the updated zip from twrp and flash that via recovery. unless u just want to keep cwm touch.
ODIN + CWM Touch or TWRP
Hey All just tried flashing CWM to My galaxy player 4.2 using this method: http://forum.xda-developers.com/showthread.php?t=2198444 But now my device comes up with the S2 logo which is what expeceted from what I read on the tutorial. But what I didn't know is that after flashing the kernel my device would no longer be able go into download mode and can only go into CWM recovery which won't let me flash anything. Just says "operation aborted" Although that could be due to the files not being in a ZIP format. I can still use the device as normal but would like to return to stock for warranty purposes.
Any ideas on how to get my Galaxy player to complete stock? Without using Odin as I can no longer enter download mode.
Many thanks
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
William31 said:
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
Click to expand...
Click to collapse
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
mattnmag said:
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
Click to expand...
Click to collapse
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
William31 said:
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
Click to expand...
Click to collapse
Cool. Glad you got it fixed.
As you know, you can root with GhettoRoot from this thread: http://forum.xda-developers.com/showthread.php?p=57238246
Then can install Safestrap from this thread: http://forum.xda-developers.com/showthread.php?p=51616723
I've never used Safestrap because I can use regular custom recoveries like CWM and TWRP. I'm still on a 4.1.2 unlocked bootloader and currently running TrentsKKRom, Build #2...which is 4.4.2 based with stock kernel, so I think it would work with Safestrap.
I'd recommend reading through the Safestrap thread thoroughly and asking questions there to make sure you get everything installed correctly. I've read that with Safestrap, you need to make a backup of your Stock ROM first and save it somewhere safe, like to your computer and on your external sd card...so you can easily restore it if needed. (I'd also make a backup of the ESF in Safestrap if it lets you, then save it somewhere safe).
After you are rooted with Safestrap, you'll have to flash custom ROM's over the stock slot in Safestrap, as the other slots apparently don't work. Again, you're limited to only using Touchwiz ROM's with the stock kernel because of the bootloader still being locked.
Check out TrentsKKRom and Alliance build 30 . (I personally like Trent's build 2 best with the S5 clean theme). I've also found Trent's ROM to be really smooth without UI lagging, the Bluetooth works good with no stuttering, and it pairs well with my Sony Smartwatch 3. (Edit: If you do try Trent's ROM, you may need to install a couple apps.... Chainfire's Supersu app to control your root permissions (at least I needed to), and the FolderMount app to fix a KitKat internal storage mounting issue).
Have fun!!
Hi everyone, i'm gonna install a new rom for my s3, so i want to ask you sth before install it
First, if install stock rom via Odin fail, may i boot into custom recovery to recovery my android OS?
Second, if install cr via Odin fail, may i use my phone normally?
Last, if install rom fail, may i boot into custom recovery to recovery my android OS?
Sorry for asking to much, just because i have once installed stock rom via Odin fail and i too scared after that.
All things are flashed with Odin, including custom recovery so if you can't get that to work then nothing will happen.
Follow the guide in general forum sticky thread on how to flash with Odin, understand what you are doing before you start.
I recently bought a used Galaxy Tab 2 off of Craigslist where everything worked perfectly fine.
I wanted to update to Lollipop, having done so already on my Note II, so I was gonna get CWM to flash the zip.
The CWM wouldn't boot up so I tried TWRP, didn't work also.
I found all the appropriate .tar files for Odin to flash but it simply won't boot into neither CWM nor TWRP.
I tried many versions of each one and when i go into bootloader mode, it recognizes that i did change the binary.
I used odin to flash the recovery mods.
Can't find a way to root without CWM so i can't use apps like ROM Manager or Rashr.
Fastboot from SDK won't recognize my phone so that wasn't an option.
Please help!
Searched far and wide for an answer but still can't boot into CWM nor TWRP.
I love Lollipop and really want it on my tab.
Everything else works fine except this frustration.