Develop Bugs

Galaxy Y Animation bootloop help

I followed all the instructions in the stock rooting post of Doky37 (done it 3 x) and my problem is I keep getting a bootloop . I tried wiping the cache, wiping/restoring the factory setting, etc. but I still get the boot loop everytime I turn on the phone.
I took a picture of the screen just before the loop and noticed that it says it cannot mount the data (??) . ANy idea on what I should do?

Do this
spiderworld said:
I followed all the instructions in the stock rooting post of Doky37 (done it 3 x) and my problem is I keep getting a bootloop . I tried wiping the cache, wiping/restoring the factory setting, etc. but I still get the boot loop everytime I turn on the phone.
I took a picture of the screen just before the loop and noticed that it says it cannot mount the data (??) . ANy idea on what I should do?
Click to expand...
Click to collapse
Follow this video carefully..check out the description for the proper steps and download link...u r in stock rom right???
http://www.youtube.com/watch?v=R_0l9zscf0o&context=C3442e2bADOEgsToPDskKPIKjoeGf8tXrCn-BjSOtZ
---------- Post added at 06:08 PM ---------- Previous post was at 06:07 PM ----------
spiderworld said:
I followed all the instructions in the stock rooting post of Doky37 (done it 3 x) and my problem is I keep getting a bootloop . I tried wiping the cache, wiping/restoring the factory setting, etc. but I still get the boot loop everytime I turn on the phone.
I took a picture of the screen just before the loop and noticed that it says it cannot mount the data (??) . ANy idea on what I should do?
Click to expand...
Click to collapse
make sure u have kies installed before flashing

I followed the instruction and it still bootloops.
Yes I am in stock ROM.

Do you mean I should have KIes running in the background when I Flash using Odin? or just installed but not running?

spiderworld said:
Do you mean I should have KIes running in the background when I Flash using Odin? or just installed but not running?
Click to expand...
Click to collapse
u must have installed kies before
---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------
spiderworld said:
I followed the instruction and it still bootloops.
Yes I am in stock ROM.
Click to expand...
Click to collapse
while it is in boot now,take the battery off..put it on again..recovery mode..wipe data.reboot..

Yes Kies is installed. Odin is working and I can flash the phone but after flashing I get the boot loop.
I am thinking there might be wrong with the internal memory

spiderworld said:
Yes Kies is installed. Odin is working and I can flash the phone but after flashing I get the boot loop.
I am thinking there might be wrong with the internal memory
Click to expand...
Click to collapse
while the phone is stuck in the samsung screen take out battery,put it in again,recovery mode and data wipe,,this has worked for many

aadaars said:
while the phone is stuck in the samsung screen take out battery,put it in again,recovery mode and data wipe,,this has worked for many
Click to expand...
Click to collapse
yes I have tried removing the battery, wait a few minutes, replace battery, power up in recovery mode, wipe data, re boot, then it goes back to boot loop.

spiderworld said:
I followed the instruction and it still bootloops.
Yes I am in stock ROM.
Click to expand...
Click to collapse
Do you remember, what version you had before?

flash it in odin to fix...it happens to my phone too...and the recovery menu bootloop too...

Found some corruption in S5360_DDLA3_ODDLA2_DDLA2_by_Doky.zip's CSC part. I've removed the full pack, uploading a CSC update, and a repaired full package as well.

Doky73 said:
Found some corruption in S5360_DDLA3_ODDLA2_DDLA2_by_Doky.zip's CSC part. I've removed the full pack, uploading a CSC update, and a repaired full package as well.
Click to expand...
Click to collapse
Okay sir,when u uploading...M using that nw and found it to be quite good...
There were slight problems with the touch while the battery was charging thats it

I went to the Samsung repair center and brought the phone
they re flashed with a PIT, bootloader, CSC, PDA tar files. it booted up after that but the ginger bread version is now back to 2.3.5 (it used to be 2.3.6}
I an planning to update it back to 2.3.6 and flash with stock ROM LA2.

i'm having the same problem.
I read this thread and wanted to try something. I just added a line at-last ro.com.android.dateformat=dd-MM-yyyy and rebooted.
Then happens the boot loop.
I tried wipe/factory reset. no use
I tried flash with Odin, and it says
Code:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/003> Added!!
What am i supposed to do..?
I recently updated my firmware using Kies

Neva mind..
I just flashed with XXLA2 and got back into galaxy...

follow this for "can't mount data. format failed on :/dev/stl11" or something like that.
http://androidadvices.com/samsung-g...cial-global-gingerbread-ddla1-236-firmware/2/

[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.

[Q] 4.4 install big goof, help please!

So, I decided to try out the CM11 Rom because it was looking stable enough to not have many issues. I used Odin 3.7 and installed CWM 6.0.2.3, Wen't to load up the rom and got the Status 7 install aborted, No big deal, I read if I received it that I needed to upgrade to the newest CWM, which is now 6.0.4.3. Not a problem, just need to reboot the phone and download in rom manager. This is where the problem lies, if I try to reboot the phone, I am stuck at the Samsung Galaxy S III screen, have kept it on there for 20+ minutes to make sure it wasn't just a delayed boot. I tried to reload a stock rom and will either get a failure on Odin or failure in CWM. Stuck here in an infinite loop with a semi-bricked phone.
I have the 6.0.4.3 disk image file, If I can find a version to load in with Odin I think I should be able to at least install CM 11, but no matter what else I have tried, nothing has worked, been at the computer all day trying to fix it, can anyone help? Many thanks in advance!!!

Well if I understand correctly, I think you should first check if you can get into Recovery or Download mode. If you can get to Recovery, first try wipe Dalvik +Cache. If that didn't help, flash another Rom AFTER a Factory Reset. Don't forget to wipe Dalvik +Cache before or after.
If you can't get to Recovery but can get Download, then Odin Flash Stock Rom. Root66 is a good Candidate. After that flash latest CWM and then try CM 11.

Perseus71 said:
Well if I understand correctly, I think you should first check if you can get into Recovery or Download mode. If you can get to Recovery, first try wipe Dalvik +Cache. If that didn't help, flash another Rom AFTER a Factory Reset. Don't forget to wipe Dalvik +Cache before or after.
If you can't get to Recovery but can get Download, then Odin Flash Stock Rom. Root66 is a good Candidate. After that flash latest CWM and then try CM 11.
Click to expand...
Click to collapse
Im positive I have done that, but not sure if I flashed cashe and Dalvik each time. I tried to flash root666 on Odin and get a failure, Will try again and share exactly what the error is.
edit: I can do both download and recovery but that is it, no actual boot

Just attempted to run root666 via Odin 3.7 and this is what I get.
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDMD5.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> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

attempted to flash CM 10.1.3 d2tmo and received the status 7 again, downloading CM 10.0.0 to see if I have better luck

Dabesiv said:
attempted to flash CM 10.1.3 d2tmo and received the status 7 again, downloading CM 10.0.0 to see if I have better luck
Click to expand...
Click to collapse
It won't help. Don't try to Odin again (yet).
What's the model number of your phone, and did you get the 4.3 update prior to this?

Aerowinder said:
It won't help. Don't try to Odin again (yet).
What's the model number of your phone, and did you get the 4.3 update prior to this?
Click to expand...
Click to collapse
yup, did nothing. model number is SGH T-999, I did the 4.3 update roughly 8 hours prior to this which I am sure didn't make things easier.
On the bright side, I just got it working. I took a big risk and removed the assert line off the CM 10.0.0 code and was able to boot in CM. From here I should be good, but thank you guys for trying to help. I hope if anyone else has this issue what I did helps.

Fyi, once you take the full update to 4.3, you cannot flash any previous firmware anymore. Dont try to force it or you'll brick.

IDK how I did it then, but I am now running CM 11 post 4.3 update, with only a small hiccup that got fixed.

Dabesiv said:
IDK how I did it then, but I am now running CM 11 post 4.3 update, with only a small hiccup that got fixed.
Click to expand...
Click to collapse
Do not attempt to Odin anything unless it is 4.3 or you will hard brick. You can still Odin recoveries, but don't try to flash the older firmware or modems.
You can install any ROM you want so long as you remove the asserts from the install script.

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

[Q] i747 Bootloop

I just got my first brick / bootloop in 2 years, and not from flashing bootloaders, so I hope someone can help me out.
I have an i747 with the MJB bootloader and modem. I've been running CM10.2 for around a year. Lately my phone has been a bit laggy, and plugging it into the computer would cause a bootloop, so I figured I'd start over with a clean wipe.
I booted into Multiboot 2.2 recovery (based on TWRP 2.8.3.0), and wiped /system, /data, cache, and Dalvik. I noticed that the log had a bunch of errors to the effect of "Cannot open /lost+found". I used the File Manager to look at /data, and there were around 10 items (not sure if folders or files) named "lost+found". I could not select them to try and delete them. I figured I'd try wiping data again, but the phone crashed in middle and started bootlooping.
As of now, booting normally or into recovery shows the splash screen for a few seconds then reboots, bootlooping.
I can boot into Download Mode, but when I tried flashing TWRP with Odin, but I only got this far, and then it would start bootlooping again (the box in the top left said RESET on a blue background):
Code:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> recovery.img
<ID:0/010> NAND Write Start!!
<ID:0/010> RQT_CLOSE !!
<ID:0/010> RES OK !!
<ID:0/010> Removed!!
I can try a debrick.img, but I don't have the correct SD card, so if there's anything else I can do first, I'd like to try that.
Does anyone have any ideas? TIA

adambrown said:
Does anyone have any ideas? TIA
Click to expand...
Click to collapse
Something to try. Grab this Odin flashable stock recovery.
Flash stock recovery. Make sure everything in Odin is unchecked but f.reset time. Once you see reset in the status window unplug USB and pull the battery. Replace battery and boot into stock recovery. Do a full wipe.
Boot back to download mode and Odin flash TWRP 2.8.5, like above. Boot into TWRP and follow normal clean flash procedure for CM10 or CM11.
This might not work, but stock recovery can be better than custom recoveries or Odin for cleaning up some storage problems. Good luck.

I don't see a reason to flash the PIT file yet. If TWRP doesn't work, try the latest Philz Touch for the d2lte.

jason2678 said:
Something to try. Grab this Odin flashable stock recovery.
Flash stock recovery. Make sure everything in Odin is unchecked but f.reset time. Once you see reset in the status window unplug USB and pull the battery. Replace battery and boot into stock recovery. Do a full wipe.
Boot back to download mode and Odin flash TWRP 2.8.5, like above. Boot into TWRP and follow normal clean flash procedure for CM10 or CM11.
This might not work, but stock recovery can be better than custom recoveries or Odin for cleaning up some storage problems. Good luck.
Click to expand...
Click to collapse
audit13 said:
I don't see a reason to flash the PIT file yet. If TWRP doesn't work, try the latest Philz Touch for the d2lte.
Click to expand...
Click to collapse
Thanks guys for the advice. I didn't see it in time, so I ended up doing a full Odin back to stock, and then flashing TWRP, which worked. Your suggestions would have been faster and easier, but now I know for next time. Thanks!