Develop Bugs

[Urgent] - Unable to boot after CM10 20121221

Hi,
I decided to install the nightly version of CM10 from the stable. After using recovery to install CM10 nightly, I am stuck at CyanogenMod loading screen and cannot boot into recovery nor download mode. Anyone experience the same thing? Help please
Thanks,

How are you trying to get into recovery?
Sent from my SGH-T999 using xda premium
---------- Post added at 04:13 AM ---------- Previous post was at 04:12 AM ----------
Watch zedomax do it at around 3.5 minutes in and try again
http://forum.xda-developers.com/showthread.php?t=1735561
Sent from my SGH-T999 using xda premium

gary.liu07 said:
Hi,
I decided to install the nightly version of CM10 from the stable. After using recovery to install CM10 nightly, I am stuck at CyanogenMod loading screen and cannot boot into recovery nor download mode. Anyone experience the same thing? Help please
Thanks,
Click to expand...
Click to collapse
Same issue. I installed CM10.1 12/17, everything worked fine for a couple of days, wanted to do a benchmark, moved to lightning rev3, worked fine. And then I went to recovery again, wiped. And now, I can't install anything and nothing but the recovery and download works.
I tried resetting it a >10 times through ODIN to no avail (odin 3.04).
Error: <OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVALH2_T999TMBALH2_T999UVALH2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
And the error message hasn't changed in the past hour.
Stock roms seem to install fine through recovery, but they freeze at the kernel boot screen. AOSP roms are not even installing giving set_perms error (status 7).

Did you try to odin back to stock. Cm10.1 messes with sd card no bueno
sent from my Samsung Gangster S III on the T-Mobile network

md1008 said:
Did you try to odin back to stock. Cm10.1 messes with sd card no bueno
Click to expand...
Click to collapse
Yea, I downloaded both "T999UVALH2_T999TMBALH2_TMB.zip" (the old one) and "T999UVDLJA_T999TMBDLJA_TMB.zip" (the new one), and tried both. I don't think that a CM10 flashable tar/md5 is even available right now. According to TWRP, everything about the SD card seems fine. In the file explorer, I saw that except /data/media/0/, there is nothing in /media, so i moved everything from media/0 to media/ (because TWRP can do this). However, I can't run fix-permissions because I haven't booted into the ROM yet. Any suggestions? I looked up somethings, and ended up finding this: http://forum.xda-developers.com/showthread.php?t=1161769, but windows 8 is too fast. It finds and installs the drivers for my phone before I have a chance to use it through the drivers in the link ^. Any other suggestions?

No odin is only good for going back tp stock rom. I would back up sd card, odin back to stock, factory reset then flash "no tripping counter odin tar. Then flash twrp via goo manager and not flash cm10.1 till its more stable
sent from my Samsung Gangster S III on the T-Mobile network
---------- Post added at 04:13 AM ---------- Previous post was at 04:12 AM ----------
If the above doesn't work than I am all out of ideas
sent from my Samsung Gangster S III on the T-Mobile network

md1008 said:
No odin is only good for going back tp stock rom. I would back up sd card, odin back to stock, factory reset then flash "no tripping counter odin tar. Then flash twrp via goo manager and not flash cm10.1 till its more stable
If the above doesn't work than I am all out of ideas
Click to expand...
Click to collapse
Wait, was I missing something, I was flashing the stock ROMs. in the two .zips are the official Samsung .tar.md5 images taht can be flashed through ODIN. Problem is, I can't get it flashing. I don't mind if I lose my data, I have nothing there I haven't backed up in the past month. I just want my phone back.
And I figured out part of the problem. Whenever I flash one of the stock ROMs (I have Darthstalker 6 and Wicked JB 5 to work with right now) through recovery, the system is not for whatever reason mounted, and this causes most of the data to be lost. /system is empty except for a single folder /system/bin. When I chmod'ed it to 777, it gained 1 more folder and a couple more files. However, it still doesn't boot. So is this a device problem? That it not able to mount and stay mounted through a flash? Is this why the Download mode isn't working either?
ERMAGHERD! I FIXED IT. So it turns out that my old phone (t989) (which is now my mom's) has an SD card. I initially suspected that the rom zips were corrupt right? So it turns out they were. I just began to do a backup, and I had this genius idea to dl cm10.1 again and move it to my internal. Installed. Works. Boots up, but ODIN still doesn't work (not that it really matters anymore).

[Q] Bricked my phone - can't revert to stock

So I'll preface this by saying I'm pretty new to this whole thing and don't exactly know what I'm doing (big surprise to most of you, I'm sure). Around a month ago I attempted to flash CM9 on my Epic 4G Touch, and after a few hours and a lot of reading through this forum I was able to get it to work without any major issues. I liked it but continued to experience issues with various wireless capabilities (wifi, mobile data, GPS) that I'm pretty sure are just a problem with the phone, but today I decided to try to give CM10 a go anyways to see if it might solve the problem.
Here's where I made two very stupid mistakes - first, I assumed that since I figured it out before I would be able to do it again this time from memory. Second, and probably worse, I did not really keep track of what exactly I did, so I can't explain with certainty the steps leading to the problem.
So, here's what I think I did:
Pretty sure I started off by going into download mode and and using the Odin one-click executable to flash the rooted stock EL29 ROM (SPH-D710.EL29_CL852097_ROOTED-OneClick.exe). I was able to boot after this, and everything seemed to work fine for stock Gingerbread. I then installed ROM Manager, and flashed ClockworkMod recovery.
Then here's where I think I first ran into problems: I tried to reboot the phone into recovery mode. From the last time I flashed a custom ROM, I remember having an issue where I would get CWM on the first reboot, but after that it would go back to normal (or is this the intended design?). I cant quite remember, but I think I booted into recovery mode and somehow only had the default recovery. At this point, for some reason I decided that as long as I was here I should go ahead and factory reset and clear the cache (why I did that, I don't know). I know with some Samsung devices there is a bug where the factory reset can brick you phone, but I thought this was only when doing it from an ICS rom and I'm pretty positive that I did this from Gingerbread.
Instead of just reflashing the stock ROM and starting over I decided to just flash CWM again from Odin. I booted into download mode and opened up Odin 1.85. I selected a file called "StockCWM-EL26.tar" for PDA. I'm not quite sure where I got that, it was left over in my phone folder from when I flashed CM9. I do think it works, however in what I'm absolutely sure was a big mistake I was also under the impression that I needed to repartition and loaded "1_02_20110310_emmc_EXT4.pit" in the PIT field. I'm not sure where I got that one either, but from a search I did on the name I got the impression that you should never use it.
At this point I was able to boot into CWM, but when I tried to navigate to "install zip from sdcard"->"choose zip from internal sdcard" it gave an error, saying something about not being able to mount emmc. When trying to boot up normally, I also got an error message about a firmware update having failed and needing to use Kies. Not able to proceed, I tried to use the Odin one-click executable to go back to EL29. It failed, giving the following output:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.bin
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
This happened on additional attempts as well. Thinking I was suffering from the EMMC brick problem, I followed Jaymoon's post in this thread and used Odin to flash the EL30 ROM with the "Q1_20110914_16GB-patched.pit" PIT file. Afterwards the phone would show the standard spring "4G" boot animation, and would enter a boot loop thereafter.
That's about it. I've spent the last several hours looking through the forums, but I haven't been able to find any additional information that I'm sure would help. I figure this is about the time to ask you guys instead of probably mucking it up further on my own.
EDIT: I should say that I am able to get into download mode without a problem, as well as recovery mode (I can flash CWM with Odin and that works as well, although some directories can't be mounted).

Can you still get into download mode? If so find the fi27 one click. Use it. Do not use pit files in regular odin.
sent from MY BAD A$$ ET4G

Yes, this is where you likely borked it:
Jumpy89 said:
I was able to boot after this, and everything seemed to work fine for stock Gingerbread. I then installed ROM Manager, and flashed ClockworkMod recovery.
Click to expand...
Click to collapse
If you can't get into download mode you've probably hosed the bootloader by doing this. Really hope you have TEP and can replace it.
And I'm seeing this a lot lately so I've got to ask - where did you read that it's okay to install ROM Manager on this phone? It's been posted here for almost a year or more to not use it. I'd like to address that with your source as I think more and more are hitting that same location lately.
Thanks!

garwynn said:
Yes, this is where you likely borked it:
If you can't get into download mode you've probably hosed the bootloader by doing this. Really hope you have TEP and can replace it.
And I'm seeing this a lot lately so I've got to ask - where did you read that it's okay to install ROM Manager on this phone? It's been posted here for almost a year or more to not use it. I'd like to address that with your source as I think more and more are hitting that same location lately.
Thanks!
Click to expand...
Click to collapse
Thanks, but what's the problem with ROM Manager? Pretty much all of the "Install a custom ROM" tutorials I've seen recommend using it (although not on this site). Should I just use Odin instead? I actually can get into download mode just fine, but I do have TEP in case that's what I need to do.

Jumpy89 said:
Thanks, but what's the problem with ROM Manager? Pretty much all of the "Install a custom ROM" tutorials I've seen recommend using it (although not on this site). Should I just use Odin instead? I actually can get into download mode just fine, but I do have TEP in case that's what I need to do.
Click to expand...
Click to collapse
Rom Manager is outdated and very buggy the last time I used it which has been some time now I switched to RomToolBox for a while but didn't like it so now I don't use a "rom manager program" on any of my phones
You can find everything you need here on XDA

Jumpy89 said:
Thanks, but what's the problem with ROM Manager? Pretty much all of the "Install a custom ROM" tutorials I've seen recommend using it (although not on this site). Should I just use Odin instead? I actually can get into download mode just fine, but I do have TEP in case that's what I need to do.
Click to expand...
Click to collapse
Don't use ROM manager...it doesn't work correctly.....

Since you can get to recovery and Odin mode you might be able to still save this.
Try this:
http://forum.xda-developers.com/showthread.php?t=1865102
...and we'll go from there.

garwynn said:
Since you can get to recovery and Odin mode you might be able to still save this.
Try this:
http://forum.xda-developers.com/showthread.php?t=1865102
...and we'll go from there.
Click to expand...
Click to collapse
Thanks. Unfortunately, this happened last night and I realized that without proper firmware the battery won't charge, so I either need to first get a different battery or charger or just call it a loss and file a TEP claim.

Those instructions seem well but I would've just said to ODIN the Direct boot EL29.tar found in one of cyanogenmod's post and flashed CM10 (AFTER wiping everything)
Sent from my SPH-D710 using xda premium

Tr0LL-$_$ said:
Those instructions seem well but I would've just said to ODIN the Direct boot EL29.tar found in one of cyanogenmod's post and flashed CM10 (AFTER wiping everything)
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Seeing as he tried flashing EL29 and it failed - on recovery nonetheless - it seems something else is at play here.
OP, you might want to try a newer build as an alternative - for example, the FL16 stock restore.
The flash order changed over EL29 and the first thing flashed is the bootloader.
If this is where the problem is it may fix it and allow the rest to flash.

garwynn said:
Seeing as he tried flashing EL29 and it failed - on recovery nonetheless - it seems something else is at play here.
OP, you might want to try a newer build as an alternative - for example, the FL16 stock restore.
The flash order changed over EL29 and the first thing flashed is the bootloader.
If this is where the problem is it may fix it and allow the rest to flash.
Click to expand...
Click to collapse
Now this is strange - I downloaded the FL16 stock (rooted) Odin one-click executable here and, borrowing a friend's battery, was able to get it to complete successfully. Unfortunately it was asking me for a PIN number (don't remember having one enabled) and I didn't know what to give it. It wouldn't give me the option to just wipe my data after entering it incorrectly several times, either. Thinking I might be OK, I tried to flash the EL26 build again but it failed at the same point as before. Then I tried flashing FL16 again, but using the version that wipes user data thinking it might remove the lock. This one failed for some reason too. So I just flashed the first FL16 version again and I can't get in but at least my battery charges. Any idea on where to proceed from here?
EDIT: If I try to boot into (stock) recovery mode I get a lot of errors saying "failed to mount /data (Invalid argument)." Not sure if that reveals anything.
EDIT2: Here's what it says when I try to flash the "restore" FL16 ROM instead of the "nodata" version:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.bin
<ID:0/008> cache.img
<ID:0/008>
<ID:0/008>
<OSM> All threads completed. (succeed 0 / failed 1)

How about FI27 instead? New flash order but ICS.... might have luck with your data partition from there, even if it is just a factory reset.
Or you could try just Agat's FI27 kernel and repacked recovery after flashing FL16 since that seems to be okay...
Sent from my SPH-L900 using Tapatalk 2

garwynn said:
How about FI27 instead? New flash order but ICS.... might have luck with your data partition from there, even if it is just a factory reset.
Or you could try just Agat's FI27 kernel and repacked recovery after flashing FL16 since that seems to be okay...
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Nice, the FI27 "reset" version worked! From there I just went back to EL29, flashed CWM, then updated to CM 10. I'm wondering if the problem might possibly have been with the battery. The only successful flashes I had were when using my friend's battery until I got working firmware and was able to fully charge my own again. Don't know if it's possible but it might have had enough juice for download mode to start but not enough to really complete the flashing process. Either way, thank you for all your help.

No ROM, No Recovery -- am I bricked?

Hi forum,
I was going for a clean install of CM 10.1 today, when I accidentally wiped too much. After the cache and dalvik, I also did a factory reset, system wipe, and internal and external storage wipe (In TWRP). As far as I can tell there's almost nothing left on there now. I can boot into ANYTHING (the most I get a is samsung screen). Flashing a recovery through odin doesn't work (never completes a reset) and the PC doesn't seem to recognize the phone either. I've seen posts by people who either wiped the system or internal storage, but I haven't seen a solution to having flash both. Any experts know how to deal with this compounded problem?
PS: I'm a long time lurker and big fan...wish I didn't wait until something like this to start posting.
Please help!
Thanks,
Batk

Just wanted to add, the only thing I can do is get into download mode..but even then odin won't flash anything successfully.

batkbatk said:
Just wanted to add, the only thing I can do is get into download mode..but even then odin won't flash anything successfully.
Click to expand...
Click to collapse
Have you tried different USB ports(or a different computer)? Some people who had Odin problems had to keep trying it a bunch of times until it works.

Try kies emergency firmware recovery
Sent from XDA app

ndwstd staff
gc84245 said:
Try kies emergency firmware recovery
Sent from XDA app
Click to expand...
Click to collapse
But how do I get Kies to recognize the device for the emergency recovery if the phone won't turn on or be recognized.

meekrawb said:
Have you tried different USB ports(or a different computer)? Some people who had Odin problems had to keep trying it a bunch of times until it works.
Click to expand...
Click to collapse
So I tried a bunch of different usb ports with a bunch of different recoveries. Every time Odin said it failed...but all of the sudden the phone booted into TWRP...I already had cm 10.1 RC5 loaded (only think I loaded after wiping the system), so I flashed that...and it worked. Phone is back, not sure how. thanks for your help guys

batkbatk said:
So I tried a bunch of different usb ports with a bunch of different recoveries. Every time Odin said it failed...but all of the sudden the phone booted into TWRP...I already had cm 10.1 RC5 loaded (only think I loaded after wiping the system), so I flashed that...and it worked. Phone is back, not sure how. thanks for your help guys
Click to expand...
Click to collapse
U shuld flash the stock rom or ur phone is gone die thia happen to me to
Sent from my SGH-T989 using Tapatalk 2

Happened to me too, it didn't recognize the phone right away but after I selected emergency firmware upgrade it worked. So what happens when you try to turn it on or put in download mode, any sign of life at all?
Sent from XDA app

esema1o said:
U shuld flash the stock rom or ur phone is gone die thia happen to me to
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Do you mean as a transition or permanently?

batkbatk said:
Do you mean as a transition or permanently?
Click to expand...
Click to collapse
I tried going back to stock using these instructions:
http://galaxys2root.com/t-mobile-ga...-to-ics-stock-on-t-mobile-galaxy-s2-sgh-t989/
But Odin fails with this message and the phone doesnt boot (only gives samsung/telus splash screen)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T989UVLE1_T989TMBLE1_T989UVLE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> amss.bin
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Download the drivers again.

Are you using a phone from telus? Did you use the telus firmware or the tmobile firmware? You need the telus firmware if you have a telus phone.
Sent from my Nexus 7 using xda app-developers app

gc84245 said:
Are you using a phone from telus? Did you use the telus firmware or the tmobile firmware? You need the telus firmware if you have a telus phone.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I think that's probably what was wrong!
I managed to use Odin to flash TWRP 2.4.2, got into the recovery, mounted internal storage, loaded stock KOODO rom from here:
http://someandroidinfo.blogspot.ca/2012/08/cwm-koodo-sgh-t989d-ics-404-stock-rom.html
and flashed it successfully and I wiped the dalvik/cache. The phone now flashes the KOODO sign, the samsung S sign, but never boots into the ROM. Could it be a recovery compatibility problem?
I at least have a recovery I get into and that works well, I don't think there is much of anything else. I want to get back to as stock as possible (without un rooting)

I ran the emergency firmware recovery tool, set my phone into recovery mode and let it run. Then I got a notice where the text was all boxes. I pressed ok and the emergency procedure ended. Any ideas?

Also, there are no folders on my internal storage, just the .android_secure and TWRP folder

PROBLEM SOLVED
I used odin to flash "T989DTLUMC4_T989OYBMC4_T989DTLUMC4_HOME.tar.md5" (stock JB for T989D KOODO)
Everything works with Odin, I get the green "Pass", but when the phone reboots its stuck in the "S samsung galaxy s2 splash screen"
I went into the recovery (which is now stock, not TWRP) and did a wipe and factory reset.
Thanks everyone! XDA rocks.

Note 2 boot loop, can't tell if rooted or modded

A friend of mine gave me a Note 2 to tinker with, but it just keeps booting to the "Samsung Galaxy Note II" screen and then rebooting.
I can get to Odin Mode, but I can't flash a new rom because I have no idea what the "stock" rom for this model is.

Ryutso said:
A friend of mine gave me a Note 2 to tinker with, but it just keeps booting to the "Samsung Galaxy Note II" screen and then rebooting.
I can get to Odin Mode, but I can't flash a new rom because I have no idea what the "stock" rom for this model is.
Click to expand...
Click to collapse
Well since it is a tinker toy no worries about knox. Just use the new NE2 tar and it should flash without any trouble. Not sure if it will cure the bootloop but most likely will.
Sent from my SPH-L900 using XDA Premium 4 mobile app

jlmancuso said:
Well since it is a tinker toy no worries about knox. Just use the new NE2 tar and it should flash without any trouble. Not sure if it will cure the bootloop but most likely will.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Explain to me "knox" anyways.
EDIT: I flashed with the NE2 tar, installation apparently went great, but it's still bootlooping.

Ryutso said:
Explain to me "knox" anyways.
EDIT: I flashed with the NE2 tar, installation apparently went great, but it's still bootlooping.
Click to expand...
Click to collapse
Odin custom recovery with reboot option off. When done disconnect from pc and pull battery. Boot into recovery mode (vol+, home, power) while inserting battery. Try flashing any custom aosp rom and see what happens.
Sent from my GT-N7105 using XDA Free mobile app

jlmancuso said:
Odin custom recovery with reboot option off. When done disconnect from pc and pull battery. Boot into recovery mode (vol+, home, power) while inserting battery. Try flashing any custom aosp rom and see what happens.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Flashed it in Odin with the reboot option off. Vol+, home, power takes me to an Android installation screen that fails about halfway in and it goes back into the bootloop. No recovery menu at all.
EDIT: Odin'd philz touch 06.07.9 so I'd have a recovery menu and installed aokp_l900_kitkat_unofficial_2014-01-19 from garwynn's site through that. It took me to a battery charging screen, then continued bootlooping.

Ryutso said:
Flashed it in Odin with the reboot option off. Vol+, home, power takes me to an Android installation screen that fails about halfway in and it goes back into the bootloop. No recovery menu at all.
EDIT: Odin'd philz touch 06.07.9 so I'd have a recovery menu and installed aokp_l900_kitkat_unofficial_2014-01-19 from garwynn's site through that. It took me to a battery charging screen, then continued bootlooping.
Click to expand...
Click to collapse
Not sure if you got this fixed (I see it's been a couple of weeks since this was posted)... if not, have you tried flashing Billard's MC2? You may need to do the reboot option off and then the vol+home+power thingy again.
http://forum.xda-developers.com/showthread.php?t=2086769

lennykravitz2004 said:
Not sure if you got this fixed (I see it's been a couple of weeks since this was posted)... if not, have you tried flashing Billard's MC2? You may need to do the reboot option off and then the vol+home+power thingy again.
http://forum.xda-developers.com/showthread.php?t=2086769
Click to expand...
Click to collapse
It hasn't been fixed, but mostly because I stopped after trying everything. I will try this when I get home from work tonight and see if it fixes.

Ryutso said:
Flashed it in Odin with the reboot option off. Vol+, home, power takes me to an Android installation screen that fails about halfway in and it goes back into the bootloop. No recovery menu at all.
EDIT: Odin'd philz touch 06.07.9 so I'd have a recovery menu and installed aokp_l900_kitkat_unofficial_2014-01-19 from garwynn's site through that. It took me to a battery charging screen, then continued bootlooping.
Click to expand...
Click to collapse
What version did you try to flash and what was the log on Odin? (Can you please copy/paste?)
I need to see where you got stopped in the flash process.

garwynn said:
What version did you try to flash and what was the log on Odin? (Can you please copy/paste?)
I need to see where you got stopped in the flash process.
Click to expand...
Click to collapse
I can't copy/paste the log because it was a couple weeks ago. Tried billard's MC2 stock rom through TWRP and it failed about halfway through installation.
I keep having to flash between TWRP and philz because TWRP won't let me connect to my laptop.
Here's the log of TWRP when it failed to flash billard's MC2 Stock ROM.
EDIT: After this flashing, it's not even turning on anymore with the battery plugged in. I have to have it connected to the charger, it'll boot to a battery charging screen and freeze there.
EDIT 2: For garwynn:
I downloaded this:http://rwilco12.com/Files/Devices/S...Unrooted/SPH-L900_MA5_853599_Stock_Nodata.exe
Plugged my phone in Odin mode, and then got this for the log:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> carrier.img
<ID:0/003> param.bin
<ID:0/003> recovery.img
<ID:0/003> sboot.bin
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone itself it says SW REV. Invalid magic string.

Tried going back to stock... Can only boot off debrick SD card now

Hey,
I'll try to keep this short. I have an ATT GS3 i747, was running Slimkat 4.4.4, my Bootloader & baseband were "I747UCDLK3." I also had PHILZ recovery
I wanted to go back to a reliable stock image where everything didn't crash. It's late now but this is what I believe I did:
-Went to this thread and downloaded the ROM and the bootloader "Touchwiz KITKAT 4.4" (KT747-TW-KK-4.4-ATT-05-13-2014)
http://forum.xda-developers.com/showthread.php?t=2658486
-I'm not sure which I did now since it's late, but I believe I flashed the above ROM and bootloader. After this my phone could still get to Download mode but not boot. So I flashed the below STOCK Restore rom.
http://forum.xda-developers.com/showthread.php?t=2658486
-At this point it wouldn't turn on. I used Debrick image "SGH-I747U-CUEMJB3" and was able to boot into the stock recovery or download mode.
-Tried many many things, Finally found this thread:forum.xda-developers.com/showthread.php?t=2549068
-Downloaded all the files from that thread, started by flashing TWRP "openrecovery-twrp-2.6.3.0-d2att.tar"
-Now my phone boots into stock 4.3 and works fine but only boots with debrick SD card. I can still get to download mode but can't get into a recovery mode. It will say "booting to recovery" but just boots normal.
-Looks like in the process of all these mess ups I flipped the warranty counter to 1. Wasn't really planning on selling it right now anyways.
So any advice on what I should do next to get it to boot normally without the SD card in?
Current about phone shows
-Baseband: I747UCUEMJB
-Build: JSS15J.I747UCUEMJB

Maybe your version of TWRP is too outdated. Try flashing TWRP or CWM for the d2lte.

Thanks,
I have downloaded the latest one from http://teamw.in/project/twrp2/104
I'll give this a try and see what happens.

I prefer Philz on the i747m. If TWRP doesn't work, give Philz a try.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/

audit13 said:
I prefer Philz on the i747m. If TWRP doesn't work, give Philz a try.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Click to expand...
Click to collapse
Yeah I had PHILZ before and really liked it but I think it kept failing to flash.. I'll redownload and try it again.

audit13 said:
I prefer Philz on the i747m. If TWRP doesn't work, give Philz a try.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Click to expand...
Click to collapse
okay I'm able to flash these without any problem but I cannot boot into recovery. It says booting to recovery... Then it goes black for a few seconds and will vibrate and boot normally. I believe it's because of the Debrick image its booting from? I still can't get it to boot without the debrick image.
Do I need to try flashing the MJB Kernel/bootloader?

Can you get phone into download mode without the SD card in the phone?
I've never had to restore a bricked phone so I'm just guessing here.

audit13 said:
Can you get phone into download mode without the SD card in the phone?
I've never had to restore a bricked phone so I'm just guessing here.
Click to expand...
Click to collapse
No :/ It doesn't even turn on without the SD card in.
With the SD card out, i can plug the phone into the computer and the red notification light will come on. If I then put the battery in and hold the power button down, the red light will eventually go off (like it's turned on) but the phone stays blank.
I can get to Download mode with the SD card in and remove the SD card though, Once the phone is on I can take the SD card out and it still works fine.

Thanks for the update. Are you flashing recovery without the SD card in the phone?

audit13 said:
Thanks for the update. Are you flashing recovery without the SD card in the phone?
Click to expand...
Click to collapse
Yeah.. The Kernel is "kernel 3.031-2024954" Is that correct? Not sure what to do lol

79TAKid said:
Yeah.. The Kernel is "kernel 3.031-2024954" Is that correct? Not sure what to do lol
Click to expand...
Click to collapse
Maybe the partitions are messed up? Since you can get into Odin, try flashing a stock recovery and see what happens.
http://forum.xda-developers.com/showthread.php?t=2789917

audit13 said:
Maybe the partitions are messed up? Since you can get into Odin, try flashing a stock recovery and see what happens.
http://forum.xda-developers.com/showthread.php?t=2789917
Click to expand...
Click to collapse
Okay so I tried flashing that w/re-partition enabled. It flashed but nothing changed... (I realized though that I still had the SD card in when I flashed)
I reflashed without the SD card (and re-partition on) but it failed .
<OSM> Please wait..
<OSM> I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img.ext4
<ID:0/007> NON-HLOS.bin
<ID:0/007> recovery.img
<ID:0/007> rpm.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> system.img.ext4
<ID:0/007> __Xmit Write fail
<ID:0/007> XmitData Fail..
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Before I turned it off, I just flashed it one more time (only auto-reboot checked) and it completed, but won't boot on its own still

Where did you get the rom? I see that there was no aboot.mbn included.

audit13 said:
Where did you get the rom? I see that there was no aboot.mbn included.
Click to expand...
Click to collapse
It was from these instructions I believe.
http://forum.xda-developers.com/showpost.php?p=53574211&postcount=9
I clicked your link and saw these instructions on the same page.
In the thread you sent me, I didn't a stock recovery file I could flash with ODIN. Seemed like everything needed to be flashed with in the custom recovery that I cant get to.

Tried a different de-brick image, didn't work. Tried a 2nd one, worked but then my phone said unknown baseband and unknown IMEI (maybe wrong version?)... Trying to go back to the one I had been using and now that's not working! This phone is driving me crazy

not buttin in audit13 , but havent some people had to try different SDcards and maybe multiple times ?? (p.s. what the heck is "aboot.mbn" ?). excuse newbness please.
p.s. will google.
err on the side of kindness

mrrocketdog said:
not buttin in audit13 , but havent some people had to try different SDcards and maybe multiple times ?? (p.s. what the heck is "aboot.mbn" ?). excuse newbness please.
p.s. will google.
err on the side of kindness
Click to expand...
Click to collapse
Yeah I have 2 SD cards with me. The one that has always worked is a Sandisk 16gb class 4. I have a Samsung 16gb class 6 but it has never worked when I write a de-brick image to it.
I should probably just stop trying things because I seem to be making it worse. I will try loading the de-brick image that HAD been working great for me again but i've already tried multiple times. I had to go back to the de-brick image that messed up my IMEI again as it's the only one that works now.
I got into download mode (which looks slightly different now (doesnt show the flash counter anymore). I tried starting over and flashing the 4.3 rom through ODIN again. It failed, trying a 2nd time now. Might be failing because I took the SD card out? Was going to try flashing 4.3 and then going back to the 4.3 De-brick image before it loads. This may accomplish absolutely nothing lol, just trying to get back to where I was so my phone will have connectivity
Edit*
If any of this is making since, the 2nd reflash of stock 4.3 ROM worked fine. But I can't get it to start up with the MJB de-brick image yet.
Edit** Yeah what I did, didn't do anything.

I've borrowed another phone (An identical ATT Galaxy S3) so I have a phone for now but would still like to try fixing mine. I guess I'll do some more research unless someone has a suggestion. Unless I didn't see it, I couldn't find an ODIN flashable stock recovery the other day.

tried google ?
"all i can really do, is stay out of my own way and let the will of heaven be done"

audit13 said:
Maybe the partitions are messed up? Since you can get into Odin, try flashing a stock recovery and see what happens.
http://forum.xda-developers.com/showthread.php?t=2789917
Click to expand...
Click to collapse
I've had mroe time to mess with the phone. I've got it booting without the SD card now and can get to recovery I successfully flashed TWRP with Odin now and can get into it fine. :good:
Now I just need to figure out which rom/stock rom to load and hope I dont have to start over again