Related
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:
Is there a way to force a update after yu delete bloatware
Sent from my LG-P769 using XDA Premium 4 mobile app
Update won't work without the bloatware installed. If you are rooted then don't forget to install voodoo ota rootkeeper. Then you go inside the app and hit the protect root button before the update.
Sent from my LG-P769 using xda app-developers app
Any body have extra copies or can someone backup the bloatware for me plz?
Sent from my LG-P769 using XDA Premium 4 mobile app
yungvilleprod said:
Any body have extra copies or can someone backup the bloatware for me plz?
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey I want to try this: Do you have cwm? If you do try to do an advanced restore then choose your backup then choose your file.
No boatloader locked
-_-
yungvilleprod said:
No boatloader locked
-_-
Click to expand...
Click to collapse
SO? My bootloader is locked too and I still have custom recovery. Listen I'm working on my update.zip file that will transfer all system apps via cwm. If you have root then get the l9 recovery installer 1.5 from Artas182x from here.
EDIT: Ok here is my update.zip link. Just install the zip in cwm and you should be good to go.
Nathan.7118391 said:
SO? My bootloader is locked too and I still have custom recovery. Listen I'm working on my update.zip file that will transfer all system apps via cwm. If you have root then get the l9 recovery installer 1.5 from Artas182x from here.
EDIT: Ok here is my update.zip link. Just install the zip in cwm and you should be good to go.
Click to expand...
Click to collapse
This update bootlooped my device. I wiped and reset my device no avail.
Really, boot looped? Weird, didn't encounter that problem before. Had it to where it would not boot, but never boot loop. Look go here to get s rooted cwm ROM and flash it. But it will reset your phone.
http://forum.xda-developers.com/showthread.php?t=2136204
Sent from my LG-P769 using xda app-developers app
Ok so I have the newest Verizon firmware and have been able to unlock bootloader root and install custom recovery now when I flash a custom Rom it bootloops and I just have to restore my nandroid backup any ideas
Sent from my ADR6425LVW using XDA Premium 4 mobile app
ruler1976 said:
Ok so I have the newest Verizon firmware and have been able to unlock bootloader root and install custom recovery now when I flash a custom Rom it bootloops and I just have to restore my nandroid backup any ideas
Sent from my ADR6425LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
if your s-on you forgot to take the boot.img from the rom and flash it via fastboot
Edit: Only use boot.img from the rom your gonna install....make sure you read proper method in first few posts from developer as there is instructions to make your phone work properly
Yes, you need to flash the boot image if you are S-ON...
But save the headaches and don't even bother flashing a ROM from your installed recovery (you really don't even need to install a custom recovery at all), all you need is the "recovery.img" from the recovery ZIP file of choice, although I currently recommend TWRP, in your adb directory and the ROM on your SD card then...
1) Reboot into Hboot and start Fastboot, connect PC
2) Type "fastboot boot recovery.img" and wait a minute for the Recovery to start on the phone
3) Wipe as per normal for installing a ROM
4) Install/Flash ROM zip as per normal
5) Reboot and enjoy!
Thank you guys this is my first HTC someone stole sgs3
Sent from my ADR6425LVW using XDA Premium 4 mobile app
ruler1976 said:
Thank you guys this is my first HTC someone stole sgs3
Sent from my ADR6425LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's worth going S-Off if you are going to flash very often at all... makes it so much easier to just flash one file and done.
It seems scary, but if you follow the instructions, it's not bad at all. I've done it twice now.
Also, you will have to flash a stock rom first (it's been done on other rom's, but ymmv... its safest to go stock before s-off).
I am stock newest ics
Sent from my ADR6425LVW using XDA Premium 4 mobile app
Is that ok
Sent from my ADR6425LVW using XDA Premium 4 mobile app
Yes
Sent from my Rezound using xda app-developers app
ruler1976 said:
Is that ok
Sent from my ADR6425LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can do it from custom roms too, from what I've seen, but since you are stock, that is perfect
So my friend rooted his s4 he cant remember how then got the tarp app from the play store to install tarp not goomanager and then when he booted to recovery its said could not boot normally and went into download mode. We tried goomanager but now no matter what you try to boot it says the same thing. I tried flashing the stock firmware on it but it failed in Odin. Any ideas?
Sent from my SPH-L300 using xda app-developers app
You never mentioned what firmware your friend is on. But I'm guessing it's me7. Flash the me7 firmware in Odin. Then don't try to put a recovery on the phone. You can't or you'll end up where you are now. Then have your friend read a lot before he tried custom roms.
well that's what I as trying to do was flash the stock I don't know what he was on. It failed right after aboot.mbn
Sent from my SPH-L300 using xda app-developers app
I tried to flash MDC
Maybe try the other one? Do you have a link for that?
Sent from my SPH-L300 using xda app-developers app
And don't I need to put a recovery on the phone TO put on a custom ROM? How do you put them on I thought you just flashed the zip/tar
Sent from my SPH-L300 using xda app-developers app
I'll try me7
Sent from my SPH-L300 using xda app-developers app
blu422 said:
And don't I need to put a recovery on the phone TO put on a custom ROM? How do you put them on I thought you just flashed the zip/tar
Sent from my SPH-L300 using xda app-developers app
Click to expand...
Click to collapse
It failed on aboot because he has an me7 phone and your trying to flash the mdk firmware which yoh cant do. Grab the me7 image from the dev section and flash that. You cant install a custom recovery on me7. Youre only options for romming are rooting then installing safestrap. So you and your friend got a bit of reading to do.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
hexitnow said:
It failed on aboot because he has an me7 phone and your trying to flash the mdk firmware which yoh cant do. Grab the me7 image from the dev section and flash that. You cant install a custom recovery on me7. Youre only options for romming are rooting then installing safestrap. So you and your friend got a bit of reading to do.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
Click to expand...
Click to collapse
Thanks for the help me7 worked I'll look into safestrap
Sent from my SPH-L300 using xda app-developers app
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. :/