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
Related
Hey guys, long time lurker, couple time poster here. I'm going to try my best to explain what's going on. A while back I rooted and installed a custom ROM on my Verizon S4. It had some data issues so I dabbled with it for a while, managed to brick it once, finally got it up and running again. LTE was still an issue so I took it to Verizon and played dumb hoping to just get a new phone. They called tech support and managed to get it running as normal.
Fast forward to tonight. I decided to get adventurous again and re-root my phone. However after I installed TWRP via GooManager (also tried CWRM after I ran into trouble) I tried rebooting to recovery to flash a custom ROM and recovery appears to not exist. It instead boots straight into Download Mode. I tried installing TWRP via Odin, that Failed. Now with every reboot it goes straight to Download Mode. My only remedy to boot the phone is to attempt to boot into Download Mode then proceed to cancel. I have tried re-flashing CWRM and TWRP numerous times. Below is the text available on the Download Mode screen. Any ideas on how I can regain Recovery? Please let me know if there are any additional details I can provide.
Download Mode text
Could not do normal boot.
ODIN Mode
Product Name: SCH-I545
Current Binary: Samsung Official
System Status: Official
CSB-Config-LSB: 0x30
Write Protection: Enable
PUstudentNDfan said:
Hey guys, long time lurker, couple time poster here. I'm going to try my best to explain what's going on. A while back I rooted and installed a custom ROM on my Verizon S4. It had some data issues so I dabbled with it for a while, managed to brick it once, finally got it up and running again. LTE was still an issue so I took it to Verizon and played dumb hoping to just get a new phone. They called tech support and managed to get it running as normal.
Fast forward to tonight. I decided to get adventurous again and re-root my phone. However after I installed TWRP via GooManager (also tried CWRM after I ran into trouble) I tried rebooting to recovery to flash a custom ROM and recovery appears to not exist. It instead boots straight into Download Mode. I tried installing TWRP via Odin, that Failed. Now with every reboot it goes straight to Download Mode. My only remedy to boot the phone is to attempt to boot into Download Mode then proceed to cancel. I have tried re-flashing CWRM and TWRP numerous times. Below is the text available on the Download Mode screen. Any ideas on how I can regain Recovery? Please let me know if there are any additional details I can provide.
Download Mode text
Could not do normal boot.
ODIN Mode
Product Name: SCH-I545
Current Binary: Samsung Official
System Status: Official
CSB-Config-LSB: 0x30
Write Protection: Enable
Click to expand...
Click to collapse
You're probably running release VRUAME7, which means that you can't successfully flash an updated recovery using ODIN.
Grab the stock no-wipe ME7 image and flash that using ODIN. That'll get you out of download mode.
The no-wipe images are at http://forum.xda-developers.com/showthread.php?t=2301259
Okay, So the title pretty much says it all. I am stuck at the Samsung boot logo (not bootanimation) and it only shows for about 1 second then reboots and continues.
This started after I tried to flash a rom and it messed up and I tried to flash via odin. I was on MJ9 and and got a bootloop so I did the odin thing. I've used odin before but it is not working well for me now.
I am able to boot into download mode but TWRP no longer works. I was able to flash via odin and it says success but the phone does not reboot like it should.
I have purchased a galaxy nexus on the cheap to hold me over until the nexus 6 is out but if I can fix my note, I would like to.
I know there were other threads about this same issue but it seems that they are all on a different version of the note, or on a s3 or something. Not to mention, I don't see anything that I could try without asking for some help on here. Can someone maybe point me in the direction of the factory firmware (preferably a rootable or already rooted version) that I can flash that will play well with my note.
Thanks guys!!!
amberkalvin said:
Okay, So the title pretty much says it all. I am stuck at the Samsung boot logo (not bootanimation) and it only shows for about 1 second then reboots and continues.
This started after I tried to flash a rom and it messed up and I tried to flash via odin. I was on MJ9 and and got a bootloop so I did the odin thing. I've used odin before but it is not working well for me now.
I am able to boot into download mode but TWRP no longer works. I was able to flash via odin and it says success but the phone does not reboot like it should.
Click to expand...
Click to collapse
Before you tried to flash a custom ROM and things went wonky...were you on Verizon's factory stock 4.3 MJ9 firmware, or on Beanstown106’s modified 4.3 MJ9 with TWRP installed?
Does the phone still boot into stock recovery? If so, you may be able to fix the phone by doing a factory reset.
amberkalvin said:
Can someone maybe point me in the direction of the factory firmware (preferably a rootable or already rooted version) that I can flash that will play well with my note.
Click to expand...
Click to collapse
If you were on Verizon's factory stock 4.3 MJ9, then you won't be able to Odin flash back to 4.1.2 or any earlier Android version because the bootloader has been locked down tight on 4.3 (and 4.4.2) with no current do it yourself method to unlock for those newer versions. You would want to restore the phone back to factory stock 4.3 though, if that's what version you were on before your phone got messed up. You can root the phone on 4.3 with saferoot, then use safestrap recovery to flash some custom Touchwiz ROM's.
If you were on the 4.1.2 based bootloader, (but running Beanstown106’s MJ9 firmware and TWRP), then you would want to restore your phone back to factory stock 4.1.2 and then root and unlock the bootloader again with CASUAL. This would give you the most flexibility with flashing custom kernels, ROM's, etc...
Check out Section 1b in Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. The guide has download links for the files you'll need to restore the phone back to the correct build version.
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
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!!
Hello all,
Recently I bought the S8 Plus and I want to sell my S6 Edge, so I wanted to clean it first before actually selling it.
I rooted my phone before, I can't remember how or what software I used, I have a feeling it was Odin,
anyway, I cleaned up my phone by doing a factory reset from within Android's settings.
Since that moment, my phone is stuck in TWRP's Recovery mode.
I have multiple stock roms, but Odin is not able to make a connection with the phone, because I can't get into boot mode.
I've also read things about ADB Sideload, but that freezes up my phone.
Then I read about some command line to type in via the terminal, but that didn't work either.
Also trying to install stuck roms didn't do anything.
Does anyone have an idea how I can get my phone back into bootmode so I can load up Odin and put a stock rom on it?
Any help is greatly appreciated
Ghrane
Ghrane said:
Hello all,
Recently I bought the S8 Plus and I want to sell my S6 Edge, so I wanted to clean it first before actually selling it.
I rooted my phone before, I can't remember how or what software I used, I have a feeling it was Odin,
anyway, I cleaned up my phone by doing a factory reset from within Android's settings.
Since that moment, my phone is stuck in TWRP's Recovery mode.
I have multiple stock roms, but Odin is not able to make a connection with the phone, because I can't get into boot mode.
I've also read things about ADB Sideload, but that freezes up my phone.
Then I read about some command line to type in via the terminal, but that didn't work either.
Also trying to install stuck roms didn't do anything.
Does anyone have an idea how I can get my phone back into bootmode so I can load up Odin and put a stock rom on it?
Any help is greatly appreciated
Ghrane
Click to expand...
Click to collapse
hi try flashing a custom ROM again with a kernel option carhd ROM has stock kernel in aroma .leave thanks with the developer.
hope this helps.regards.
I don't really understand that, got any clear information?
Ghrane
Ghrane said:
I don't really understand that, got any clear information?
Ghrane
Click to expand...
Click to collapse
Boot to Download from TWRP Recovery (Reboot - select - Download)
Fire-up Odin, flash one of your multiple stock roms.
02xda2 said:
Boot to Download from TWRP Recovery (Reboot - select - Download)
Fire-up Odin, flash one of your multiple stock roms.
Click to expand...
Click to collapse
That doesn't work either.
If I select Download, my phones freezes up.
Update:
I managed to update TWRP, making me able to go back to Download mode!
But, once I tried Odin to flash a stock rom, it failed.
Also, my KNOX Warrenty Void is set '1'.
Am I still able to install any roms or get this KNOX fixed?
Ghrane
If you have a PC, use samsung smart switch to re-initialize your device.
And you can not do anything for tripped knox.