[Q] S3 Only boots to ClockWorkMod Recovery. - T-Mobile, Samsung Galaxy SIII

Hey guys, Not sure if this question was answered already, even while looking at the past threads... but
My Phone only boots to ClockWorkMod. I tried to flash the Pac 4.4.2 ROM onto my Galaxy, but I seem to have just failed at that >.<
My device now only boots in ClockWorkMod, no matter how many times I reboot it. I'm not sure what else to do.
The ROM initially failed on me, and now I'm stuck basically without a phone (I know not very smart)
If anyone has dealt with this problem because please if you could help me out
Thank you!

Did you wipe /system? Don't do this anymore if you make it part of your flashing process. You have two options.
Odin back to stock, factory reset and start over.
Or
Find a rom that will flash, factory reset and go from there.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Related

Soft brick? Recovery not working properly

Hey guys all my restores are failing half way through. It also fails if I try to factory reset or wipe dalvik but wipe cache works fine It fails if i try flash any ROM.. And if I try to boot to system it shows SG logo then black screen I'm really kind of lost here. I've already tried flashing 4 different versions of Twrp/clockworkmod and I get the same result every time. The roms I'm trying to flash were running fine on my device before this happened. Never seen this before please help thank you.
Sent from RootBox infected sensation or my PacMan e739
djwuh said:
Hey guys all my restores are failing half way through. It also fails if I try to factory reset or wipe dalvik but wipe cache works fine It fails if i try flash any ROM.. And if I try to boot to system it shows SG logo then black screen I'm really kind of lost here. I've already tried flashing 4 different versions of Twrp/clockworkmod and I get the same result every time. The roms I'm trying to flash were running fine on my device before this happened. Never seen this before please help thank you.
Sent from RootBox infected sensation or my PacMan e739
Click to expand...
Click to collapse
is this an i747 or i747m (carrier?)? what was the last thing you did to the device/had you just modified or flashed something? were you using recovery or odin to flash the 4 different recoveries?
xBeerdroiDx said:
is this an i747 or i747m (carrier?)? what was the last thing you did to the device/had you just modified or flashed something? were you using recovery or odin to flash the 4 different recoveries?
Click to expand...
Click to collapse
I have sgh i747 at&t us model. Unlocked Sim for Tmobile use. Before having problems. I flashed vanilla rootbox att nightly. it was running fine then I flashed acid audio mod. And it worked but not well with my player of choice. So i flashed a restore from fright before the sound mod. And all I got was 2 different Samsung logos then black screen. At this point Twrp started asking for a password. I tried an older backup. (rootbox stable) and it booted fine. Everything seemed to be working. But when I rebooted again I got the 1St SG logo then black screen. Now recovery doesn't read anything on the internal card as well as the other problems I stated. I used mskips toolkit to flash Twrp originally and now I've been flashing back and forth between recoveries using recovery flashable zips. Also every time I flash roms or restore I did factory wipe/cache/dalvik and after I started having these issues I tried wiping system and that didn't help either. Thanks for trying to help
Sent from RootBox infected sensation or my PacMan e739
what recovery are you currently sitting on?
Twrp 2.4.4.0 is what I started with and now I'm back on it but from a flashable zip this time instead of whatever mskips toolkit used
Sent from RootBox infected sensation or my PacMan e739
here is the link to an odin flashable twrp 2.5.0.0 tar: http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.5.0.0-d2att.tar
and here's a recovery flashable twrp 2.5.0.0 zip link: http://forum.xda-developers.com/attachment.php?attachmentid=1917517&d=1367104589
if you flash in recovery, be sure to reboot recovery in order to boot into the new version. i'm sure you know most of this but i'm just trying to cover all the bases.
is twrp still asking for the password or were you able to get passed that?
if you have a micro sd card, you could place a ROM/gapps on it, flash this latest twrp recovery from odin or recovery, perform a full wipe (cache, dalvik, data, system) and flash the ROM/gapps. see if that remedies your situation.
if you dont have a micro sd card, and it appears you've wiped the system so there's no OS, you may have to odin back to rooted stock and start over. keep me posted
Still no luck. i flashed twrp2.5 through recovery and after rebooting back to recovery it still asked for a password so I hit cancel at which point it lets me continue and after full wipe as you described above and a fresh flash of stable rootbox 3.9.1 (md5 matched) im still in the same situation. also factory wipe says failed still
I think at this point if it were me, I would Odin flash back to stock then start from scratch. Pain in the butt I know, and no guarantee, but usually flash back to stock is a safe bet.
Another option is to grab the Odin flashable cwm tar in the "root from recovery" method in the general section. Flash the tar, boot into recovery and flash the 6.0.3.1 zip in post #2 of my signature link. Reboot recovery and try wiping/flashing again.
Since you're not entering the password in TWRP, I think that's why you're not getting successful wipes and flashes.
now I used the power+home+vol down button combo to see if bootloader would start. it gave me a choice to download a custom rom or cancel so I canceled and the phone rebooted and i was blessed with the beautifull rootbox animation. my rootbox 3.9.1 nandroid booted and seems to be running fine. Now Im afraid to reboot in fear it will start the whole process over again. any suggestions? or should I just leave it powered on for the rest of its life lol
edit: well I got up the guff to reboot and everything came back fine again WTH. this is so weird, I wish I had a clue what happened. anyways I just wanted to thank you guys one more time for you help. hopefully we wont have to come back to this thread. Peace ;-]
Man that is strange. If that ever happens again it would be interesting to see the log if you can get it. I wonder if there were issues mounting a partition and/or your SD card. If TWRP and CWM were both having an error and the files were on your SD card that would probably be the only thing in common that could cause something like this. Some Transformers seemed to have the password issue, but doesn't seem related to your experience. Glad you got it sorted.

[Q] Stuck samsung screen even after odin stock

Hey guys hopefully you can help me. I was rooted for like 3 or 4 months now and have had not many problems or not anything I couldn't fix my self. My phone gets stuck on the Samsung Galaxy s4 screen anytime I reboot. I have tried different roms, different kernels, I even odin back to stock. I was using TWRP 6.0 then reverted back to TWRP 5.2 to see if that was causing the problem. Still have problems. I am going to re download the stock tar to see if it was a bad download but Odin checks the md5 and says it was good. Odin says passed every time also. Odin version is 3.07.
I get a error before and when trying to wipe dalvic cashe. I can wipe reg cash no problem. I think my phone is not mounting the internal storage when it reboots. I could be way off but need help asap. If I format super wipe with twrp then restart twrp and then factory reset I can install or restore a rom some times but still cant restart the phone. Any hope would be greatly appreciated.
EDIT
I wanted to edit my previous commet. LiquidSmooth seems to be running fine. So TW roms and GE roms **** up on my phone when I restart. so is it the internal systems when I have TW roms. I think it has something to do with partictions messing around maybe.
I like TW roms and want to continue to use them... Thank you
Get into recovery and do a factory reset, it is a must after you odin back to stock. Make sure you are also using a tmo kernel.
Thanks you
I got this problem a few days ago and found some topic including this one. You should check it out.
Well, what worked for me was Odin to stock firmware, root again, install recovery then custom rom. Now it's working fine. Try to downloading it again to see if it works. I downloaded mine from here, rooted and recovery it using this one.
TheAxman said:
Get into recovery and do a factory reset, it is a must after you odin back to stock. Make sure you are also using a tmo kernel.
Thanks you
Click to expand...
Click to collapse
+1 to what he said. I bet if you go into the stock recovery after odin flashing it will say something like cannot mount /data partition. Factory reset there, and it should fix that and make it mountable. (Its important to use the stock recovery factory reset after the odin, don't flash a custom recovery right after flashing)
This was incredibly helpful. I had the same issue. Thank you.
This is also applicable to the Verizon Wireless model.

[Q] [SOLVED] T-Mobile Samsung Galaxy S4 (SGH-M919) Soft-bricked

Hi all, hope you are doing well (I also hope that you can help me ).
I just recently got a replacement phone because my other one had a faulty speaker (crackling, etc.). The other one was rooted (via CF-AutoRoot) and had TWRP on it, and I made a complete nandroid backup of it onto my MicroSD card.
I rooted the new phone using CF-AutoRoot via Odin and installed TWRP on it as well (also via Odin). Then I swapped the SD card and SIM card and restored the complete backup to the new phone.
It took a while, but the phone booted up and I had two working clones, the only way to tell which was which was by changing the volume and hearing the crackling on the old one.
So the new phone worked all day (was able to make calls and everything, and the GUI that was customized with Wanam Xposed even looked good), however when I restarted it to put in my backup battery, I didn't have root for some reason. I tried and tried to get it back (reinstalled SuperSU, tried the TWRP method) to no avail.
I re-flashed CF-AutoRoot just to see, and the phone booted up but and for some reason SuperSU was gone (and I didn't have root). When I restarted, I got a boot loop and could not even get back into a recovery.
I got tired of this and wanted a fresh start, so I just flashed the stock ROM via ODIN and did a factory reset. However now if I try to boot, the Samsung logo will flash and just shut down, and I won't be able to get into the recovery no matter what. If I flash a recovery (CWM, TWRP or even stock), the recovery will work until I try to actually try to boot the phone. I've tried taking the battery out for a good 5 minutes and retrying (also tried swapping batteries), I've tried doing complete resets galore from all three recoveries mentioned with no success. Obviously Download mode still works so I know it's not completely bricked, but I am getting a little scared.
Any and all help is extremely appreciated as I would prefer not to have such an expensive paper-weight.
Thanks a bunch!
I would suggest going all the way back stock on stock firmware via Odin. Then re-root, TWRP, and re-download the rom of your choice. Dont restore the backup. Just start fresh.
I Think My S4 Is Insane
SICK MADE DEVELOPMENT
alloycowboy said:
I would suggest going all the way back stock on stock firmware via Odin
Click to expand...
Click to collapse
Thanks for the reply.
And okay, I tried that.
I flashed stock using the T-Mobile ROM I found here: galaxys4root_(dot)_com/galaxy-s4-stock-firmware/
This is the same ROM file I used to completely restore the phone I had to return, and that worked fine.
But it still won't boot up or go into recovery mode (just shows the Samsung logo for a split second before shutting down).
One thing I did do on the other phone was flash a kernel which had set-MUID to off so I could WiFi tether, but I thought flashing the stock ROM would revert that back as well. Do you think that's the reason it messed up so badly? I restored the backup from the other phone with a different kernel? Right after I restored the backup to the new phone and everything was working, I remember checking the kernel info in the About Phone section of the settings, and it was in fact the kernel I'd installed on the other phone.
TLDR: Tried flashing stock ROM to no avail. Download mode still works but can't enter recovery mode or boot.
Are you doing a factory reset after flashing stock firmware?
I Think My S4 Is Insane
SICK MADE DEVELOPMENT
I'd flash a stock rooted ROM. Get that root and recovery back. The konane tar file from the stickies, perhaps.
Sent from my SGH-M919 using xda app-developers app
alloycowboy said:
Are you doing a factory reset after flashing stock firmware?
Click to expand...
Click to collapse
Yeah, as soon as it finished installing I went into stock recovery and did a factory reset.
Karakoram2 said:
I'd flash a stock rooted ROM. Get that root and recovery back. The konane tar file from the stickies, perhaps.
Click to expand...
Click to collapse
Alright, I'll try that.
Is the konane tar an actual ROM? And what do you mean in the stickies?
Sorry, not very familiar with XDA forums.
Samsung GT-I9500 flashes n switches off!
BallisticallySimilar said:
Hi all, hope you are doing well (I also hope that you can help me ).
I just recently got a replacement phone because my other one had a faulty speaker (crackling, etc.). The other one was rooted (via CF-AutoRoot) and had TWRP on it, and I made a complete nandroid backup of it onto my MicroSD card.
I rooted the new phone using CF-AutoRoot via Odin and installed TWRP on it as well (also via Odin). Then I swapped the SD card and SIM card and restored the complete backup to the new phone.
It took a while, but the phone booted up and I had two working clones, the only way to tell which was which was by changing the volume and hearing the crackling on the old one.
So the new phone worked all day (was able to make calls and everything, and the GUI that was customized with Wanam Xposed even looked good), however when I restarted it to put in my backup battery, I didn't have root for some reason. I tried and tried to get it back (reinstalled SuperSU, tried the TWRP method) to no avail.
I re-flashed CF-AutoRoot just to see, and the phone booted up but and for some reason SuperSU was gone (and I didn't have root). When I restarted, I got a boot loop and could not even get back into a recovery.
I got tired of this and wanted a fresh start, so I just flashed the stock ROM via ODIN and did a factory reset. However now if I try to boot, the Samsung logo will flash and just shut down, and I won't be able to get into the recovery no matter what. If I flash a recovery (CWM, TWRP or even stock), the recovery will work until I try to actually try to boot the phone. I've tried taking the battery out for a good 5 minutes and retrying (also tried swapping batteries), I've tried doing complete resets galore from all three recoveries mentioned with no success. Obviously Download mode still works so I know it's not completely bricked, but I am getting a little scared.
Any and all help is extremely appreciated as I would prefer not to have such an expensive paper-weight.
Thanks a bunch!
Click to expand...
Click to collapse
The same thing has happened to me! Did you find any solustion for this?? Please help!! This was my first attempt and i have no idea wats going on!
Here are the stickies for our forum: http://forum.xda-developers.com/showthread.php?t=2419828
Sent from my SGH-M919 using XDA Premium 4 mobile app
What I did to unbrick my T-Mobile S4 (SGH-M919)
killerwolf2121 said:
The same thing has happened to me!
Did you find any solutions for this? Please help if you can; this was my first attempt and I have to idea what's going on.
Click to expand...
Click to collapse
Well, for the first problem, flashing the stock ROM did it for me. I followed this tutorial.
For the second issue of not booting up after displaying the Samsung logo; my battery just simply was too dead and didn't have enough juice to start. You have no idea how stupid I felt.
Let your phone charge from the wall cable for a good while before trying all this again; then see if that works. It did it for me. If it doesn't, I'm not sure what else to try.
After that (if it works), if you still want root, just flash CF-Auto-Root and then a custom recovery if you want (like ClockworkMod Recovery (click the little version link, not the "Download ROMs" button) or TWRP via GooManager) (I use TWRP)
All the best and let me know how it went!
Keep in mind that I did this on an SGH-M919 (T-Mobile S4) running Android 4.2.2, so if you don't have that, I have no idea if any of the above will work for you. Also I'm pretty sure if you do have 4.3, you will ruin your warranty forever due to the Knox restriction they added (if you haven't already).
Android_Monsters said:
Here are the stickies for our forum: http://forum.xda-developers.com/showthread.php?t=2419828
Click to expand...
Click to collapse
Thanks
BallisticallySimilar said:
Well, for the first problem, flashing the stock ROM did it for me. I followed this tutorial.
For the second issue of not booting up after displaying the Samsung logo; my battery just simply was too dead and didn't have enough juice to start. You have no idea how stupid I felt.
Let your phone charge from the wall cable for a good while before trying all this again; then see if that works. It did it for me. If it doesn't, I'm not sure what else to try.
After that (if it works), if you still want root, just flash CF-Auto-Root and then a custom recovery if you want (like ClockworkMod Recovery (click the little version link, not the "Download ROMs" button) or TWRP via GooManager) (I use TWRP)
All the best and let me know how it went!
Keep in mind that I did this on an SGH-M919 (T-Mobile S4) running Android 4.2.2, so if you don't have that, I have no idea if any of the above will work for you. Also I'm pretty sure if you do have 4.3, you will ruin your warranty forever due to the Knox restriction they added (if you haven't already).
Thanks
Click to expand...
Click to collapse
I am on 4.3 and yes, flashing the stock rom worked for me too! relief thanks a ton!
Having trouble unbricking M919 T-Mobile
Hi, I'm trying to unbrick my M919 through Odin. I have all the updated software, but I keep getting a fail message. Any help would be appreciated.

[Q][SOFT BRICK] Weird...

So this is the weirdest "brick" I have ever experienced. My phone was working flawlessly with a TWRP recovery and a slightly modded mostly stock ROM. I was playing around modding the stock MMS app, SecMms.apk, and flashing it through recovery. One of these flashes did not complete successfully. I got to the lockscreen, but it would not respond. And there was no network connection. So I figured something got screwed up. I rebooted into recovery and flashed a stock ROM. Boot loop. I got back into recovery and performed a factory data reset, erased everything, flashed a stock ROM. Boot loop. I downloaded a completely stock ROM with stock recovery, stock everything. Got into download mode and flashed it through ODIN. Boot loop. Well, actually, the initial boot got a screen where I could see the taskbar with time and no-service indicator; the rest of the screen was black for a minute; then I got a popup window stating that "Process system is unable to continue" and asking if I wanted to wait of close it. Then it boot looped. I tried booting without a SIM card and an external SD card - same result.
So, to recap - I can get to Download Mode, and ODIN, but anything I flash, including completely stock ROM boot loops.
I am at a loss as to what to try next. If anyone has ideas, I'm willing to try just about anything. I'm gonna take it to T-Mo store tomorrow to see if they can do anything with it...
re: phone issues
6uPMAH said:
So this is the weirdest "brick" I have ever experienced. My phone was working flawlessly with a TWRP recovery and a slightly modded mostly stock ROM. I was playing around modding the stock MMS app, SecMms.apk, and flashing it through recovery. One of these flashes did not complete successfully. I got to the lockscreen, but it would not respond. And there was no network connection. So I figured something got screwed up. I rebooted into recovery and flashed a stock ROM. Boot loop. I got back into recovery and performed a factory data reset, erased everything, flashed a stock ROM. Boot loop. I downloaded a completely stock ROM with stock recovery, stock everything. Got into download mode and flashed it through ODIN. Boot loop. Well, actually, the initial boot got a screen where I could see the taskbar with time and no-service indicator; the rest of the screen was black for a minute; then I got a popup window stating that "Process system is unable to continue" and asking if I wanted to wait of close it. Then it boot looped. I tried booting without a SIM card and an external SD card - same result.
So, to recap - I can get to Download Mode, and ODIN, but anything I flash, including completely stock ROM boot loops.
I am at a loss as to what to try next. If anyone has ideas, I'm willing to try just about anything. I'm gonna take it to T-Mo store tomorrow to see if they can do anything with it...
Click to expand...
Click to collapse
Go into recovery mode and do a complete wipe including "Factory Reset", wipe data, wipe system,
wipe cache, wipe dalvik cache and then if you have a working nandroiod backup restore it.
If you don't have a nandroid backup then go into download mode and flash the official stock
firmware for the N900T phone from http://SamMobile.com
Either one of these two options will get your phone back up and running.
Good luck!
I have already done all of the above, and...no go. Even stock firmware from SamMobile boot loops. Unfortunately, I do not have a nandroid backup, so that's the one thing I cannot do.
6uPMAH said:
I have already done all of the above, and...no go. Even stock firmware from SamMobile boot loops. Unfortunately, I do not have a nandroid backup, so that's the one thing I cannot do.
Click to expand...
Click to collapse
Google zedomax you will find his website for unrooting note 3. Will walk you thru with ever step.
It is no longer rooted after I have flashed stock firmware/ROM from SamMobile. Believe me , I have tried all the known methods of returning this phone to stock/unroot. I have flashed through recovery when I had custom recovery. I have flashed through ODIN. So far I have been unable to fix the issue. I am thinking my internal storage is corrupt, or the partition is corrupt. Anyone knows of a way to rebuild/repartition internal storage?
6uPMAH said:
It is no longer rooted after I have flashed stock firmware/ROM from SamMobile. Believe me , I have tried all the known methods of returning this phone to stock/unroot. I have flashed through recovery when I had custom recovery. I have flashed through ODIN. So far I have been unable to fix the issue. I am thinking my internal storage is corrupt, or the partition is corrupt. Anyone knows of a way to rebuild/repartition internal storage?
Click to expand...
Click to collapse
Did you try the "boot loop fix" flashable? It's essentially a script that sort of recreates the efs partition in recovery. It's been linked a few times in the twrp thread, and there may be a thread dedicated to the topic (search for "brick loop") - I don't have the links handy though, apologies.
The mans right^ that helped me out through my "soft brick". Totally out of the blue. Wasnt even messing around with anything I didnt knew I was doing
Sent from my SM-N900T using Tapatalk
Anybody has a link? I've searched, but there's nothing specific to Note 3 TMO...
6uPMAH said:
Anybody has a link? I've searched, but there's nothing specific to Note 3 TMO...
Click to expand...
Click to collapse
The method is outlined in the OP of this thread but the flashable version of what is outlined there can be found in this thread - hope that helps!
Thanks. I'll give it a go after work.
UPDATE: All is well in the world again. Thanks everyone for all your help. Thanks dwitherell ! The thread you pointed me to was the solution!

[HELP] Unable to mount /data | Bootloop on first screen

Hi, I have been trying to flash a new ROM to my Note II.
It was on Official Stock 4.3 ROM and I flashed succesfully another 4.3 ROM based on stock with some Note 3 features using Philipz Touch.
Then I switch Philipz to TWRP in order to install DN3 V4 ROM and I made the wipes and format /data and I start flashing the ROM, and since that moment It stucks on the first screen.
When I try to flash a stock 4.3 ROM using Odin, It seems to flash correctly, but when I try to boot, it stucks again.
I can enter to recovery and download mode, I can install some ROMS using TWRP but when it finishes it shows "Unable to mount /data" and if I try to boot, It always stucks on fisrt screen.
I hope you can help me.
Do it again: format cache; davik; systems; data and install rom again. If not, flash cwm recovery via odin.
Good luck.
Sent from my Assistant
Still the same
biokiller said:
Do it again: format cache; davik; systems; data and install rom again. If not, flash cwm recovery via odin.
Good luck.
Sent from my Assistant
Click to expand...
Click to collapse
I really appreciate your help, but I can't fix the problem yet.
With CWM I can't make a factory reset, when I try to make it, it restarts the phone and it stuks on the first screen.
I have flashed stock ROMS with odin and it says PASS but when the phone boots It always stucks on the first screen.
Fear not.
I am fairly confident this will work, but read the whole post first
You tick erase all nand as well as the usual two options. Then boot into recovery (should give warnings about unmountable /data) and wipe data / factory reset. Then reboot and it should work / odin a stock rom as normal.
If that doesnt work / or instead you get the correct pit file and flash it as well as the rom and have four options ticked: pit, erase all nand + normal two.
If someone gave me their phone with the same symptoms as yours and said: fix it right now that's what I'd do. I'd also warn them I really need to do more research before doing this and using these two options in odin could brick the phone forever.
I hope this gives you lines of inquiry. I found many mixed messages with the erase nand option, most said nothing of merit except don't do it, some said you must wipe data first (which u can't), some said exactly what I've repeated, some say a pit is enough, others had many steps and files ive never heard of to solve the same issue. There is a large thread in the S3 forum about this, even got mentioned on xda proper. My brief cookie crumbs journey did not return any note 2 threads.
Remember one thing, before using odin, double check every detail. Battery, cable being used, files being used (right ones, md5s), right options ticked, computer is in good health, internet is off, Kies is not running. (I'm sure ive missed some)
Solved
I install again the stock kit Kat firmware and the problem was the same, but this time I boot stock recovery and there I made factory reset and that's it. Problem solved and Note boot normally.
Thanks for your help
With or without erase nand in odin?
No, I just flashed normally as all the stock firmwares
I see, thought you'd rule that out. Disappointing really. Glad ur sorted anyway. Remeber wiping data is important when changing roms, even if it's not always absolutely necessary.
Did you try TWRP or Philztouch ? Did you flash 4.3 stock rom?
Sent from my GT-N7100 using Tapatalk

Categories

Resources