Hello all
I was doing factory reset on my Samsung Galaxy y duos GT-S6102 using ClockWorkMod recovery. For this I followed these steps. After it, on rebooting the system, it's taking too much time. It has already been upto 8-9 hours and still in process and it's being annoying now
Please tell me what's the general time it takes to reboot after formatting using ClockWorkMod recovery?
Sounds like you wiped your system partition, flash a new ROM or a backup
Sent from my Nexus 4 using xda premium
demkantor said:
Sounds like you wiped your system partition, flash a new ROM or a backup
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks for the reply demkantor. Yes I wiped my systems partition. So what to do now to get my phone start? For flashing a new ROM it requires the phone to be switched on.
Can you not boot into bootloader or recovery?
Sent from my Nexus 4 using xda premium
demkantor said:
Can you not boot into bootloader or recovery?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I am booting it into normal mode. Doesn't work
So you are saying you can not boot into recovery or bootloader no matter how hard you try? The only thing you can do is boot to os and it fails?
There is no way of getting into recovery mode or bootloader?
Sent from my Nexus 4 using xda premium
demkantor said:
So you are saying you can not boot into recovery or bootloader no matter how hard you try? The only thing you can do is boot to os and it fails?
There is no way of getting into recovery mode or bootloader?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
No, I am saying that I tried both recovery or bootloader mode, it fails. And even booting in normal mode fails. The only thing I am seeing for hours while booting is the black screen with my phone name.
Unfortunately if you can't get into bootloader and have no functioning os or recovery there is nothing to do but JTAG, unless you phone has a download mode function. I'm unfamiliar with your specific phone but many samsungs have a download mode, can you get into this.
demkantor said:
Unfortunately if you can't get into bootloader and have no functioning os or recovery there is nothing to do but JTAG, unless you phone has a download mode function. I'm unfamiliar with your specific phone but many samsungs have a download mode, can you get into this.
Click to expand...
Click to collapse
Yes....my Galaxy y duos GT-S6102 has download mod. What to do with it now?
Use Odin or hiemdall to flash back to stock, it will be like the day you got your phone, everything but SD card will be returned to stock.
Sent from my Nexus 4 using xda premium
demkantor said:
Use Odin or hiemdall to flash back to stock, it will be like the day you got your phone, everything but SD card will be returned to stock.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I used Odin and it worked. Thanks a lot :victory:
demkantor said:
Use Odin or hiemdall to flash back to stock, it will be like the day you got your phone, everything but SD card will be returned to stock.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I used Odin and it worked. Thanks a lot :victory:
Related
HI guys me again, heres the story, i went into cwm recovery, wiped everything i could in it, booted to download mode, flashed terrasilent through odin, i had it set to auto reboot so it did that and its stuck on the terrasilent screen, cant get into download mode, when will i learn lol
TheFro74 said:
HI guys me again, heres the story, i went into cwm recovery, wiped everything i could in it, booted to download mode, flashed terrasilent through odin, i had it set to auto reboot so it did that and its stuck on the terrasilent screen, cant get into download mode, when will i learn lol
Click to expand...
Click to collapse
if you wiped everything, that means you wiped /system which means you have no OS anymore.
take out the battery --> put it back in --> hold power and volume down --> and flash a rom via odin/heimdall
I cant get into download mode, by pressing vol down and power, but the kernel animation runs
Sent from my Nexus 7 using xda app-developers app
TheFro74 said:
I cant get into download mode, by pressing vol down and power, but the kernel animation runs
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
you have an intl or a us device?
International
Sent from my Nexus 7 using xda app-developers app
It shows up in odin but when i go to flash something it gets stuck on setupconnection
Sent from my Nexus 7 using xda app-developers app
TheFro74 said:
International
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Well I the kernel animation runs, you should still be able to get into cwm. Can you confirm this please?
Sent from my YP-G1 using Tapatalk 2
How do you boot into cwm again?
Sent from my Nexus 7 using xda app-developers app
TheFro74 said:
How do you boot into cwm again?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Pull out battery, put it back in, power and volume up
Make sure to press both of them at the same time
Sent from my Kindle Fire running CM10.1/SGT7
No, just the samsung logo then kernel animation
Sent from my Nexus 7 using xda app-developers app
Hi guys,
Last week, I was installing some custom ROMs on my brothers OT-955.
Everything worked fine, I got CWM on there and installed a ROM called PAC (http://forum.xda-developers.com/showthread.php?t=2088694).
It worked pretty well, but the phone froze a couple of times a day so I decided to try some others yesterday.
When I installed a CM-based ROM, I got a 'status 7' error in CWM and after I rebooted the phone was stuck in a boot loop.
After a while, it showed up when I ran `fastboot devices` and I was able to get it into recovery and install a different ROM.
When that ROM had some trouble I ran into the same 'status 7' error with another one.
I miss-clicked and rebooted instead of installing a working ROM.
Once again, I was able to reboot to recovery using fastboot and everything worked out.
Fast forward 30 minutes, the last ROM had some trouble too and I decided to move back to stock.
CWM reported that stock was installed successfully so I rebooted.
Since then, the phone won't move past the boot screen.
Fastboot doesn't recognize it, `adb` used to recognize it as offline until I replugged it.
I already:
Reinstalled the device driver
Cycled the power (empty, full)
Tried a different host machine
I have no idea what to try next.
Is there someone here with general 'stuck on bootscreen' experience or in-depth OT-995 experience?
Kind Regards,
Tim
Have you wiped cache and dalvik cache before installing a ROM ? You should also format the /system partition for a clean install. Before installing a ROM.
Sent from my Nexus 4 using xda premium
Ki6465 said:
Have you wiped cache and dalvik cache before installing a ROM ? You should also format the /system partition for a clean install. Before installing a ROM.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yes, I wiped the data and cache before installing new ROMs.
I did not format the /system partition, though.
Try wiping cache, dalvik cache and format /system then install the ROM. Hope this works
Sent from my Nexus 4 using xda premium
Ki6465 said:
Try wiping cache, dalvik cache and format /system then install the ROM. Hope this works
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I have no way to get to the recovery since I can't connect using fastboot or adb.
timvdalen said:
I have no way to get to the recovery since I can't connect using fastboot or adb.
Click to expand...
Click to collapse
Oh so the only way to enter CWM is through adb ? Not using any key combinations ? Like volume up or down ?
Sent from my Nexus 4 using xda premium
Ki6465 said:
Oh so the only way to enter CWM is through adb ? Not using any key combinations ? Like volume up or down ?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
It's not my own phone so I don't know for sure, but it isn't volume down + power on.
I'm also pretty sure that something is wrong beyond that.
If I had fastboot access I would just directly boot the image (although I did flash it).
EDIT: oh wow, volume up did it.
How stupid of me to not try it.
Okay so you're in recovery ?
Sent from my Nexus 4 using xda premium
Ki6465 said:
Okay so you're in recovery ?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yep, everything will work out.
I feel so stupid now, hehe.
Thanks for the suggestion!
You're welcome :thumbup: Let me know if it works.
Sent from my Nexus 4 using xda premium
Ki6465 said:
You're welcome :thumbup: Let me know if it works.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yup, got it to boot
Awesome :thumbup:
Sent from my Nexus 4 using xda premium
brick alcatel 995A
Hi, i need your help, i have a alcatel ot 995A bricked, it just stock on alcatel logo, i was triying to isntal custom rom on it, durring the installition it give an error an when boot it just reach to alcatel logo. sorry for my English. (s.o.s guys)
Ki6465 said:
Awesome :thumbup:
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I have this same problem with my alcatel ot 995, but my hard reset doesnt do anything. how could i replace this android with new one?
I am running the Cyanogenmod 11 Nightly from the 11th, and also running crpalmers kernel 5.4.2. I had ART turned on, and was running Gravitybox Xposed Modules. While I was using the phone, while on the charger, it randomly rebooted, and showed the splash screen. The phone was just about dead when it was being used on the charger. While on the charger, the phone repeatedly shows the splash screen, followed by a black screen, and then a vibration like it had just been powered on, and shows the splash screen. This cycles while plugged into the computer. When first plugged into the computer, the computer (Windows 7) makes noises like it is connected and then removed. The phone is not recognized in fastboot or adb. I was able to access the bootloader menu by holding the power and volume down keys. Usually I can not navigate through it by using the volume keys, and it reverts back to the bootloop within 30 seconds. I don't know what is causing this problem, so I tried to give as much info as possible. Any help is appreciated. Thank you in advance.
Hope someone can get you sorted out. Never experienced that particular issue.
Sent from my HTC6435LVW using Tapatalk
Can you get to your recovery or factory reset in the bootload
Sent from my HTC6435LVW using XDA Premium 4 mobile app
thayl0 said:
Can you get to your recovery or factory reset in the bootload
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When I access the bootloader I am unable to select anything before the phone returns to the bootloop. I can't get to recovery or factory reset. I also believe that running an RUU would be unsuccessful because the phone is in neither ADB and Fastboot mode.
zach p said:
When I access the bootloader I am unable to select anything before the phone returns to the bootloop. I can't get to recovery or factory reset. I also believe that running an RUU would be unsuccessful because the phone is in neither ADB and Fastboot mode.
Click to expand...
Click to collapse
I'd just get a replacement then.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
thayl0 said:
I'd just get a replacement then.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was able to stop the bootloop somehow. Must have been a combination of attempting to charge it all day and the constant attempts to reboot into recovery. Now I'm in recovery, and there is no partitions. I am unable to factory reset or format data of any kind. I had pushed a ROM to the device in the recovery. I was unable to flash this rom, or the stock splash screen.
zach p said:
I was able to stop the bootloop somehow. Must have been a combination of attempting to charge it all day and the constant attempts to reboot into recovery. Now I'm in recovery, and there is no partitions. I am unable to factory reset or format data of any kind. I had pushed a ROM to the device in the recovery. I was unable to flash this rom, or the stock splash screen.
Click to expand...
Click to collapse
Can you use adv and fastboot. If so I'm going to send you a link to 3.06 ruu
Sent from my HTC6435LVW using XDA Premium 4 mobile app
thayl0 said:
Can you use adv and fastboot. If so I'm going to send you a link to 3.06 ruu
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Fastboot and ADB are working properly, and that would be great!
zach p said:
Fastboot and ADB are working properly, and that would be great!
Click to expand...
Click to collapse
just remember to backup everything u want to keep this will delete everything and put your pho e back to the current 3.06 it will also install latest radio and hboot so it might lock your bootloader but all you'll half to do is run rumrunner.
http://forum.xda-developers.com/showthread.php?t=2570548
Sent from my HTC6435LVW using XDA Premium 4 mobile app
thayl0 said:
just remember to backup everything u want to keep this will delete everything and put your pho e back to the current 3.06 it will also install latest radio and hboot so it might lock your bootloader but all you'll half to do is run rumrunner.
http://forum.xda-developers.com/showthread.php?t=2570548
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you so much you have been a great help
Let me know if it fails. You half to b s off to flash it threw fastboot.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
thayl0 said:
Let me know if it fails. You half to b s off to flash it threw fastboot.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It failed at first, but I tried using jailbird's workaround mentioned in the thread, and it worked like a charm. Thank you again for all your help!
zach p said:
It failed at first, but I tried using jailbird's workaround mentioned in the thread, and it worked like a charm. Thank you again for all your help!
Click to expand...
Click to collapse
Now you may half to rerun runrummer before anything. Then install custom recovery.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
So i had a similar problem last evening, left phone over night in bootloop off charger till it died and woke up this morning reconnected bootloop continued for 10 mins then phone booted up, relocked bootloader, flashed stock ruu, unlocked bootloader and installed nusense working fine so far.
Hey guys, I recently got a replacement device from best buy because my old ones screen broke. I successfully rooted the new device using the towelroot method. I just tried to install the loki recovery via goomanager and when I rebooted it just boots into odin mode and says that it "could not do normal boot." I've tried everything I can think of but cant get it to boot. Any help?
christianstudebaker said:
Hey guys, I recently got a replacement device from best buy because my old ones screen broke. I successfully rooted the new device using the towelroot method. I just tried to install the loki recovery via goomanager and when I rebooted it just boots into odin mode and says that it "could not do normal boot." I've tried everything I can think of but cant get it to boot. Any help?
Click to expand...
Click to collapse
Have actually research what firmware you have and what recovery can be used. You do know that unless you have mdk...you can't use goomanger or twrp or Cwm right?
Sent from my SCH-I545 using Tapatalk
decaturbob said:
Have actually research what firmware you have and what recovery can be used. You do know that unless you have mdk...you can't use goomanger or twrp or Cwm right?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
How many times do you think this same question has been asked and answered?
Sent from my NCC-1701
riker147 said:
How many times do you think this same question has been asked and answered?
Sent from my NCC-1701
Click to expand...
Click to collapse
Countless times....not even 15 mins of reading anything...
Sent from my SCH-I545 using Tapatalk
christianstudebaker said:
Hey guys, I recently got a replacement device from best buy because my old ones screen broke. I successfully rooted the new device using the towelroot method. I just tried to install the loki recovery via goomanager and when I rebooted it just boots into odin mode and says that it "could not do normal boot." I've tried everything I can think of but cant get it to boot. Any help?
Click to expand...
Click to collapse
I believe you are going to have to go with SafeStrap 3.72. You don't have an unlocked bootloader but Safestrap isn't bad. You can still install some really good roms
The problem is that I can't boot my phone now. It just boots into Odin mode. When I got my phone originally it wasn't mdk so I didn't have to deal with safestrap. So I didn't know there was other options.
Sent from my XT907 using XDA Premium 4 mobile app
christianstudebaker said:
The problem is that I can't boot my phone now. It just boots into Odin mode. When I got my phone originally it wasn't mdk so I didn't have to deal with safestrap. So I didn't know there was other options.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
this is a stickie in general forum that all new S4 people should be required to read...I can not imagine how some one ignores a thread when its titled
What you need to know before, during and after modifying your verizon S4
http://forum.xda-developers.com/showthread.php?t=2606501
christianstudebaker said:
The problem is that I can't boot my phone now. It just boots into Odin mode. When I got my phone originally it wasn't mdk so I didn't have to deal with safestrap. So I didn't know there was other options.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
if you can get into download mode and have Odin, flash a full wipe or a no wipe tar and start over.
http://forum.xda-developers.com/showthread.php?t=2735172
Hello fellow members.
I have an S4 SCH-I545
I feel as if I'm out of options, I have read many forums for the past 3 days and cannot find a method that works. I am currently soft bricked and cannot get ODIN to successfully flash anything. When I pull the battery and try to boot it immediately takes me to ODIN Mode, and I can't seem to get into anything but that. Just recently it has given me a new image that says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I don't exactly know what it is referring to but I have Kies and there is only an emergency recover area and that does nothing.
Am I out of options? Any help is extremely appreciated.
If I left anything out let me know.
jeffysonp said:
Hello fellow members.
I have an S4 SCH-I545
I feel as if I'm out of options, I have read many forums for the past 3 days and cannot find a method that works. I am currently soft bricked and cannot get ODIN to successfully flash anything. When I pull the battery and try to boot it immediately takes me to ODIN Mode, and I can't seem to get into anything but that. Just recently it has given me a new image that says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I don't exactly know what it is referring to but I have Kies and there is only an emergency recover area and that does nothing.
Am I out of options? Any help is extremely appreciated.
If I left anything out let me know.
Click to expand...
Click to collapse
What build were you on prior to this?? Jellybean...Kit Kat ?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
What build were you on prior to this?? Jellybean...Kit Kat ?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
aircooledbusses said:
Alright, I know this is not the help/question/noob thread, but I'm I'm a pickle. Redirect me if you must. Verizon s4 that was on nc5 baseband-i don't know the bootloader, but it was 4.4.2 if that helps. Rooted with towel root and twrp through too manager. Yeah, I know that's where the problem came from. So now the phone is (hopefully) in a soft brick state stuck in down load or Odin mode. Odin recognizes the phone. I don't care to keep DAT or retain root, I just was it to function. Is the nc5 full wipe with the pit my correct next step? Thank you in advance, razz me if you must, I deserve it
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Looks like me and snoopy are in the same boat, or at least our phone is in the same soft brick state. Is there any hope?
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Looks like me and snoopy are in the same boat, or at least our phone is in the same soft brick state. Is there any hope?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Absolutely there is hope. We just need to know what exact build your phones were on prior to this soft brick. Then we'd know what Odin files to give you.
Then if there were still errors you could post them here for more help.
What were you guys doing exactly that brought you to this point?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Absolutely there is hope. We just need to know what exact build your phones were on prior to this soft brick. Then we'd know what Odin files to give you.
Then if there were still errors you could post them here for more help.
What were you guys doing exactly that brought you to this point?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I had baseband nc5. It was android version 4.4.2. Phone worked and I rooted it with towel root, the phone was rebooted and checked root with rootchecker. Then I flashed twrp 2.7.1 for jfltevzw with gooo manager and after that my problems began. Phone would not come out of Odin mode. I did try to Odin the nc5 emergency no wipe and it failed changing the Odin screen to the one that snoopy described.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
I had baseband nc5. It was android version 4.4.2. Phone worked and I rooted it with towel root, the phone was rebooted and checked root with rootchecker. Then I flashed twrp 2.7.1 for jfltevzw with gooo manager and after that my problems began. Phone would not come out of Odin mode. I did try to Odin the nc5 emergency no wipe and it failed changing the Odin screen to the one that snoopy described.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright sorry to make you write that again.. I just now saw you included your quote from an earlier post.
Are you able to hop onto your PC and copy and paste what the Odin error is into this thread?
Trying to flash a custom recovery on anything other than MDK will certainly lead to a soft brick most of the time. However you should be able to recover your phone back.
Using the full wipe NC5 Odin file should do it.. However if that's not working for you only those errors being posted here will allow the right people to help you along.
May seem silly but have you tried simply trying another USB cable? I've seen people on here have Odin flashes fail just due to the cable.
Grab the Odin errors though if you can
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Alright sorry to make you write that again.. I just now saw you included your quote from an earlier post.
Are you able to hop onto your PC and copy and paste what the Odin error is into this thread?
Trying to flash a custom recovery on anything other than MDK will certainly lead to a soft brick most of the time. However you should be able to recover your phone back.
Using the full wipe NC5 Odin file should do it.. However if that's not working for you only those errors being posted here will allow the right people to help you along.
May seem silly but have you tried simply trying another USB cable? I've seen people on here have Odin flashes fail just due to the cable.
Grab the Odin errors though if you can
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thank you, I'm traveling for the next few days, but will get set up with a different Samsung stock cable at my PC and report back. Knowing there is hope is a relief.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Thank you, I'm traveling for the next few days, but will get set up with a different Samsung stock cable at my PC and report back. Knowing there is hope is a relief.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There's definitely hope. If Odin can't bring you back I bet Heimdall could. It's a little more involved but obviously worth it.
Sent from my SCH-I545 using Tapatalk
Awesome! I've never used hemidal yet, but have recently been doing much better with adb commands, so I'm totally willing to learn. I'll post back here in a few days
Sent from my Nexus 7 using XDA Premium 4 mobile app
I was trying to flash Hyperdrive and ended up having to update to NC5, I can't remember what my phone was out of the box, I will be able to tell you in a few hours when I get my box. I just got the phone last week, so probably 4.3.
aircooledbusses said:
I had baseband nc5. It was android version 4.4.2. Phone worked and I rooted it with towel root, the phone was rebooted and checked root with rootchecker. Then I flashed twrp 2.7.1 for jfltevzw with gooo manager and after that my problems began. Phone would not come out of Odin mode. I did try to Odin the nc5 emergency no wipe and it failed changing the Odin screen to the one that snoopy described.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Your firmware is mdk?....because if you not mdk you CANT use goo manger or twrp or cwm. ...you can only use safestrap....If you were mdk...and you went to nc5 you can never go back.
sent by safestrap powered echo v26
decaturbob said:
Your firmware is mdk?....because if you not mdk you CANT use goo manger or twrp or cwm. ...you can only use safestrap....If you were mdk...and you went to nc5 you can never go back.
sent by safestrap powered echo v26
Click to expand...
Click to collapse
Uh yeah I think that was my mistake. The attempt to flash twrp while on nc5 borked the phone.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Uh yeah I think that was my mistake. The attempt to flash twrp while on nc5 borked the phone.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yep..definitely the mistake
this thread and links would have helped you before you jumped off the cliff
http://forum.xda-developers.com/showthread.php?t=2606501
also odin is very touchy with using usb cables, usb ports and computers
Looks like you are trying to Odin to an image that was lower firmware than what your phone was on. You might want to try flashing the full wipe nc5 image that has been posted. I can't link to it now as I'm on my phone but if you Google Odin full wipe Verizon nc5 it should bring you to the proper xda thread to get the file.
Sent from my SCH-I545 using XDA Premium 4 mobile app
decaturbob said:
yep..definitely the mistake
this thread and links would have helped you before you jumped off the cliff
http://forum.xda-developers.com/showthread.php?t=2606501
Yep, from the thread you suggest.......... "The number one reason people brick their Verizon Galaxy S4 phones is due to attempts to flash recovery using Goo Manager, dd, and other tools without understanding when those will or won't work. The Verizon S4 is very locked down, and will reject such attempts in most cases."
Sent from my GT-I9070 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
NC5 is in this thread
http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my SCH-I545 using Tapatalk
Slowbalt said:
Looks like you are trying to Odin to an image that was lower firmware than what your phone was on. You might want to try flashing the full wipe nc5 image that has been posted. I can't link to it now as I'm on my phone but if you Google Odin full wipe Verizon nc5 it should bring you to the proper xda thread to get the file.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So I followed what you said and ended up using this guide. http://forum.xda-developers.com/showthread.php?t=2735172
I did the full wipe version, and it was successful, however I still cannot boot. It will give me the samsung icon with the unlocked padlock, and then just go black, I still can boot into ODIN mode but not into recovery. Any idea what's going on?
jeffysonp said:
So I followed what you said and ended up using this guide. http://forum.xda-developers.com/showthread.php?t=2735172
I did the full wipe version, and it was successful, however I still cannot boot. It will give me the samsung icon with the unlocked padlock, and then just go black, I still can boot into ODIN mode but not into recovery. Any idea what's going on?
Click to expand...
Click to collapse
Try booting into stock recovery and do a Factory Data Reset and wipe cache then reboot.
Sent from my SCH-I545 using Tapatalk
Also once you're back to stock run Tri Angle Away to get rid of that annoying CUSTOM screen at boot lol can't stand that thing and on my phone it can make getting into CWM a pain as well.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Try booting into stock recovery and do a Factory Data Reset and wipe cache then reboot.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I can't seem to get into stock recovery either. I tried re-flashing and I still get the same results, when I try to boot into recovery I get the Samsung logo with the unlocked padlock, and then it just shuts down. :/