[Q] Soft-bricked and Need Help - [d2att] - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Hey all,
After hours of intense Googling, I've finally reached my limit and decided to make a forum post. I don't know what kind of info you guys need to help me out so I'm including everything I know.
Before you guys say anything, I've looked at the sticky and went through the soft-bricked guide, but it says to just flash back to stock, which I already tried.
Here is the backstory:
I had Cyanogenmod 10.2 installed (using the default get.cm installing process) for about a month when a notification popped up prompting me to install a system update. I had it only set up to install stable updates (or so I thought), so I installed it and it ended up being stuck in a boot loop. Unfortunately, all of my data was encrypted and I couldn't figure out how to recover it, but I just thought screw it, formatted everything, and reinstalled Cyanogenmod 10.2.1 using Clockwork Recovery. I also ended up trying to install gapps using a zip using Clockwork Recovery as well, but it still wouldn't show up even though the install passed in Clockwork without any problems. Soo, I figured to try to install using get.cm again and during the reboot process during install, it froze (I left it running for an hour to no avail).
Now I'm stuck in this situation:
~ The phone is stuck on the waving blue alien and won't finish booting.
~ Cannot access Clockwork Recovery. Just goes back to the blue alien even though I see the blue debug text in the upper left on the Samsung screen when holding Power, Vol. Down, and Home that suggests it will open Clockwork Recovery.
~ I can still access the Download mode.
~ My computer can still see the phone in ODIN v3.07.
Here's the troubleshooting I've tried to do:
~ I made a TAR archive with the boot.img file from the CM10.2.1 zip and renamed the boot.img to zImage (no extension). Tried flashing it in the PDA input and I get this ODIN output:
<ID:0/003> Added!!
<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> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Here is my phone's text in the top right:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: Yes (7 counts)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
WARRANTY Bit: 1
BOOTLOADER RP SWREV: 2
SW REV CHECK FAIL : Fused 2 > Binary 0
Unsupport dev_type
~ Tried the same thing above with stock rom too. Same errors and everything.
~ I've tried installing Clockwork Recovery again using heimdall and it looked like it installed fine, but I still can't access it.
Any help is greatly appreciated. Thanks!
UPDATE: I tried installing adb but it can't detect my device in download mode.
UPDATE 2: I found a small glimmer of hope that seems like it's a similar issue to what I'm having: http://forum.xda-developers.com/showthread.php?t=2427016
Problem is, is that it looks like my internal SD might be corrupted and I might have to resort to a hardware mod. I'd rather not take out my internal SD if I don't have to, so do any of you guys have any ideas or thoughts on fixing this?

[SOLVED] Woo!
So I noticed after leaving my phone plugged in for a while that the bootloop started occurring on the other cyanogenmod loading screen with the arrow circling around the logo. Seeing something was different, I rebooted my phone and lo and behold, I managed to get into Clockwork Recovery! I installed the cyanogenmod zip I had from earlier and managed to boot it up fully! I got Google Apps on there and updated successfully to CM11.
I guess the thing to take from this is to make sure your phone is fully charged before troubleshooting.

Glad to see you solved it w/o having to replace the motherboard.
When I saw you renamed the bootloader to zImage I caught my breath. I think the kernel is zImage and the bootloader is boot.bin, or Sbl.bin for the secondary bootloader. (At least for flashing in Heimdall.)

dawgdoc said:
Glad to see you solved it w/o having to replace the motherboard.
When I saw you renamed the bootloader to zImage I caught my breath. I think the kernel is zImage and the bootloader is boot.bin, or Sbl.bin for the secondary bootloader. (At least for flashing in Heimdall.)
Click to expand...
Click to collapse
Thanks for the info For some reason it never occurred to me to flash CM using Heimdall, haha. Still kinda new to this stuff and good thing ODIN caught my mistake. I was blindly trying things on forums and renaming boot.img to zImage was one of the things I read, but looking at more forum answers, I'm now realizing that zImage is actually in the boot.img file in the CM zip.

Related

[Q] SGS3 Kernel Panic / Soft Brick

Hi,
I have a rooted Sprint SGS3 SPH-L710 which I was attempting to update from 4.1.1 to 4.1.2. I never did get the update to work and afterwards, I started getting random reboots, which seemed like SDS. Now powering it on puts it into a reboot cycle and it never gets past the Samsung Galaxy S III logo. Attempting to go into recovery mode gives the following kernel panic message:
Kernel Panic
KRAIT INFO
Panic caller : __stack_chk_fail+0x10/0x14
Panic Msg: stack-protector: Kernel stack is corrupted in: c002
Thread : swapper:1
Wait....
Done
Kernel Panic
Upload Mode
I can get into download mode, and have attempted to use Odin to flash both the kernel with KERNEL-SPR-L710VPBMD4-1366019975.tar and the ROM SPR-L710VPBMD4-20130418114128.zip which I obtained from samsung-updates.com
When I attempt to flash the kernel, I get the following from Odin:
Firmware update start…
boot.img
NAND Write Start!!
RQT_CLOSE !!
RES OK !!
Remain Port …. 0
All threads completed (succeed 1 / failed 0)
But no change in behavior on the phone.
When I attempt to flash the ROM, I get the following from Odin:
Odin v.3 engine (ID:3)..
File analysis..
SetupConnection
Initialization..
Get PIT for mapping..
Firmware update start..
sbl2.mbin
NAND Write Start!!
FAIL! (Write)
All threads completed. (succeed 0 / failed1)
and I also get the following on the phone download mode screen:
ODIN : flash write failure
I've tried searching, but cannot seem to find much about the kernel panic. I'm guessing it is either a symptom of SDS or that I may have accidentally loaded an incompatible ROM when unrooting. I've tried flashing with Odin on different systems with different cables, but always get the same results.
tl;dr I have a soft bricked phone that gives a kernel panic error when I try to go into recovery mode and a write failure when flashing the ROM.
Any suggestions are appreciated.
Thanks!
I've never seen that before! Scary. Try using Odin with the files from this link, everything you need should be there.
http://rwilco12.com/downloads.php?dir=Files/Devices/Samsung Galaxy S3 (SPH-L710)/
Actually, use the tar file from this link
http://rwilco12.com/downloads.php?d...L710)/Stock ROMs/JB/MD4/Full Restore/Unrooted
Make sure you try different ports and cables when using Odin. Some things that helps me.
------------------------
Sprint Galaxy S3
Stock - Whiplashh Rom - MIUI - Wicked Sensations
Hit that "Thanks" Button if I helped you!
Thanks for the advice, Metalfan and Whiplashh. I have tried 3 difference cables and different usb ports. I also downloaded the file SPH-L710_MD4_1130792_Stock_Restore.tar.md5.gz that Metalfan linked, but got the same results from Odin as the other ROM I attempted loading.
I did notice something that changed before I attempted to load that ROM, the download mode screen now shows CUSTOM BINARY DOWNLOAD: No, it used to show 11. So I guess at some point in troubleshooting I must have reset the counter, but not sure that it really matters.
Now I'm condsidering trying this solution for hard bricked devices, I figure it can't hurt.
http://forum.xda-developers.com/showthread.php?t=2369125
I just thought I would post a follow-up to my own issue. All of my own attempts to flash a new ROM to the device were failing and the device was out of warranty, so I sent it off to a independent repair service who informed me the device had a bad eMMC (internal memory / memory controller) which I suppose matches up with the write fail errors that I was seeing. Not sure if I broke it while flashing it or if it was a result of the SDS symptoms that I had seen, either way its pretty much scrap now.

Fix: semi bricked/bricked SPH-L710 Sprint S3

when I 1st rooted my s3 on 4.3, I messed it up lol I fixed it this way, which is installing a clean slate of 4.3 OTA via Odin...mine was a semi brick and keyboard was somehow gone as well, so this was my only choice:
1st download my bundle I made here
-once downloaded, extract the bundle preferably to your open desktop or wherever is easiest for you to guide through
your phone must have USB debugging mode enabled if you haven't done it already
-settings>more>developer options>enable usb debugging
-if you've never done this before, you'll have to go to: settings>more>about device>build number (tap on build number several times until the countdown states you're now a developer, once done press back once and developer options will now be present)
now once that's done, pull the battery, reinsert the battery and reboot into recovery by: holding volume up/home and power keys
once in recovery, do a factory data/cache wipe (fully wipe it out!)
now once that's done, pull your battery, reinsert your battery, hold: volume down/home and power keys and you'll be prompted with a warning and to press volume up to proceed, press volume up...this is "download mode"
on your computer, open the extracted bundle and run Odin 3.09 and make sure ONLY "auto reboot" and "f. reset time" boxes are checked
-connect your phone via usb cord and the ID: com will now light up and indicate it has detected your phone (if not, you'll need samsung drivers which can be found here)
-once recognized, load the necessary file by checking the box by the AP tab and then clicking the AP tab and load the .tar.md5 file in the bundled folder...this may take a few seconds, it's a large file so be patient
-once file is loaded, hit the "start" button and DO NOT INTERRUPT THIS PROCESS! once it's finished, again this is a large file and will take some time to finish, you'll see a "PASS" in Odin and also in the log box it will say "all threads completed (succeed 1/fail 0)
your phone will now reboot itself and restart with a freshly installed 4.3 OTA operating system! if it fails, try again and if it fails again, your phone may just be beyond repair...heard they can make a nice paper weight decoration lol GOOD LUCK!
To Reroot your phone: use my rooting guide
Nice post, I am sure that it will save someone.
Thanks OP!
I had a software brick and it worked out perfectly
phone_dude said:
Thanks OP!
I had a software brick and it worked out perfectly
Click to expand...
Click to collapse
thanks for the feedback and glad it worked! if you're looking to root it again, I have a guide up as well on doing that for 4.3, you won't brick by following that guide
Question, will doing this while on 4.3 and reinstalling 4.3 reset Knox counters? Or is there anyways yet to return to an unroofed stock with all Knox trips reset?
Sent from my SPH-L710 using Tapatalk
it should...this would be just like going to the sprint service techs and having them completely wipe and reinstall the 4.3 ota firmware like new
THANK YOU!!!!
Had a soft brick of my wife's phone. Had NO OS on the phone, wasn't able to flash ANY custom ROMs, even after ODINing and reODINing various recoveries.... Anyway... just nothing... Then THIS!
Great work. Wish I could hit Thanks 1000 more times. Cheers!
---------- Post added at 08:27 PM ---------- Previous post was at 08:26 PM ----------
Seriously. THIS is what should be stickied for returning to stock. Easy Peasy.
beejmeister said:
THANK YOU!!!!
Had a soft brick of my wife's phone. Had NO OS on the phone, wasn't able to flash ANY custom ROMs, even after ODINing and reODINing various recoveries.... Anyway... just nothing... Then THIS!
Great work. Wish I could hit Thanks 1000 more times. Cheers!
---------- Post added at 08:27 PM ---------- Previous post was at 08:26 PM ----------
Seriously. THIS is what should be stickied for returning to stock. Easy Peasy.
Click to expand...
Click to collapse
thanks for the compliments and glad it worked out for you, that's all that matters
Count my @$$ as saved
Well, looks like you saved my @$$. My phone noted that there was an update for cyanogenmod.... and bricked on reboot.
hi @goku2778
i'm about to try these instructions. you responded to my post in another thread. basically i'm still stuck. i've attempted several times to format data/wipe everything in the hopes of clearing the PIN code, or is it called PUC/PUK code that the phone wants to decrypt and boot into the ROM home screen. i used up the 10 attempts and it said "invalid PIN/password" or something like that, and keeps booting back to recovery to perform an automatic data reset.
but the problem is it still asks for a PUK/PIN code.
will your unbricking instructions that care of this?
-----------------------
WOOHOOO!!!! My ordeal has is over. Thank you very much for posting this. This cleared that pesky PIN code prompt like a champ.
And was able to update my PRL and Profile. Now I'll jump to one of the other ROMs, using your other thread.:good::laugh:
mister-crackers said:
hi @goku2778
i'm about to try these instructions. you responded to my post in another thread. basically i'm still stuck. i've attempted several times to format data/wipe everything in the hopes of clearing the PIN code, or is it called PUC/PUK code that the phone wants to decrypt and boot into the ROM home screen. i used up the 10 attempts and it said "invalid PIN/password" or something like that, and keeps booting back to recovery to perform an automatic data reset.
but the problem is it still asks for a PUK/PIN code.
will your unbricking instructions that care of this?
-----------------------
WOOHOOO!!!! My ordeal has is over. Thank you very much for posting this. This cleared that pesky PIN code prompt like a champ.
And was able to update my PRL and Profile. Now I'll jump to one of the other ROMs, using your other thread.:good::laugh:
Click to expand...
Click to collapse
just saw your post...glad it worked for you! let me know how you make out on your next tasks bro!
"Process com.android.phone has stopped"
How do you think I can modify to get this idea to work on my semi-bricked Sprint SGS3? I just can't get past that error message once the phone starts. It was a result of a bad flash of CM11, unified yesterday where i must have lost the connection somehow. I do have it set for debugging. but I can't use phone buttons to enter the recovery or download modes. Everytime I pull the battery and try to enter recovery, it says it is going there,but then the CM logo appears and then that darn message shows up again not allowing for me to get past it. I can see it with the computer via the USB however. Would you suggest or recommend something else(ie. trying to get it back to factory reset)? If so, then please leave a link for instx.
neadams99 said:
How do you think I can modify to get this idea to work on my semi-bricked Sprint SGS3? I just can't get past that error message once the phone starts. It was a result of a bad flash of CM11, unified yesterday where i must have lost the connection somehow. I do have it set for debugging. but I can't use phone buttons to enter the recovery or download modes. Everytime I pull the battery and try to enter recovery, it says it is going there,but then the CM logo appears and then that darn message shows up again not allowing for me to get past it. I can see it with the computer via the USB however. Would you suggest or recommend something else(ie. trying to get it back to factory reset)? If so, then please leave a link for instx.
Click to expand...
Click to collapse
damn...if you can't get into recovery, then I don't know what else you could do to be honest. 1 of those cm unifieds wrecked my phone also, my backup stock rom wouldn't load either, I could get into recovery but no other roms I downloaded would install, I had to do this method again...it took about 25 mins or so to do start to finish, finish meaning resetting up the phone after reinstalling 4.3 again and signing into it with Google id, updating the prl and profile to enable my data.
then spent another 20mins or so to reroot it, remove knox, and reinstall my cm11 package I have with the 2/03/2014 build release which I'm still on and phone has been awesome all over again. so if you can't get into recovery at all, I'd do the Odin 4.3 reinstall
Followed your steps using ODIN -passed- stuck on s'sng logo
goku2778 said:
damn...if you can't get into recovery, then I don't know what else you could do to be honest. 1 of those cm unifieds wrecked my phone also, my backup stock rom wouldn't load either, I could get into recovery but no other roms I downloaded would install, I had to do this method again...it took about 25 mins or so to do start to finish, finish meaning resetting up the phone after reinstalling 4.3 again and signing into it with Google id, updating the prl and profile to enable my data.
then spent another 20mins or so to reroot it, remove knox, and reinstall my cm11 package I have with the 2/03/2014 build release which I'm still on and phone has been awesome all over again. so if you can't get into recovery at all, I'd do the Odin 4.3 reinstall
Click to expand...
Click to collapse
Woah. THat is rough, but I need it to be awesome again. It's been 4+ hours and I am still going on trying to fix it. Total noob. So, you must slow down the steps you mentioned above for me to follow along. Should I try getting into DL mode again and rerun ODIN? Please advise.
neadams99 said:
Woah. THat is rough, but I need it to be awesome again. It's been 4+ hours and I am still going on trying to fix it. Total noob. So, you must slow down the steps you mentioned above for me to follow along. Should I try getting into DL mode again and rerun ODIN? Please advise.
Click to expand...
Click to collapse
lol try getting into download mode and if that works, just follow this guide along from download mode, don't worry about the debug part...let me know what happens with that part:
download mode, if it works, proceed with Odin flashing and report back
2nd attempt failed.
goku2778 said:
lol try getting into download mode and if that works, just follow this guide along from download mode, don't worry about the debug part...let me know what happens with that part:
download mode, if it works, proceed with Odin flashing and report back
Click to expand...
Click to collapse
Failed to get past the logo again on second ODIN attempt. Does your .tar file include CM11 or another? I'm wondering if there is any ROM on the device to upgrade to as I had an interruption when flashing to CM11. Also ve second screw up was that I did not wipe the data / cache prior to that attempt to upgrade. I did have TWRP and TiBackup Pro (ran on Sunday last) on device. How can I recover those files to reinstall to device?
neadams99 said:
Failed to get past the logo again on second ODIN attempt. Does your .tar file include CM11 or another? I'm wondering if there is any ROM on the device to upgrade to as I had an interruption when flashing to CM11. Also ve second screw up was that I did not wipe the data / cache prior to that attempt to upgrade. I did have TWRP and TiBackup Pro (ran on Sunday last) on device. How can I recover those files to reinstall to device?
Click to expand...
Click to collapse
wait...can you get into download mode? sounds like you can't, and if you can't get into that or recovery, dude you're probably pretty screwed.
um, there's a boot image unbrick method but it's quite complex and I've never done it myself, you'd have to search here for if in the general thread and it was made by cnexus...without the ability to go into recovery, you cannot flash a rom, without the ability to get into download mode, you can't use Odin
can get into DL mode passed ODIN but then stuck w/logo
goku2778 said:
wait...can you get into download mode? sounds like you can't, and if you can't get into that or recovery, dude you're probably pretty screwed.
um, there's a boot image unbrick method but it's quite complex and I've never done it myself, you'd have to search here for if in the general thread and it was made by cnexus...without the ability to go into recovery, you cannot flash a rom, without the ability to get into download mode, you can't use Odin
Click to expand...
Click to collapse
I can get into DL mode. Here is the readout from second ODIN attempt ( which shows it passed). <ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> NON-HLOS.bin
<ID:0/006> cache.img.ext4
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
Why would it not allow me into recovery mode?? that just makes no sense to me. I've tried it a dozen times and know to hold the three buttons for a long while. Then the phone shows "recovery reboot" or something like that in blue micro font up in the left top corner but then the CM logo comes on and then I get stuck again on Samsung logo forever. looks like your .tar files have the MD5 only, right? WHat more do I need to push onto phone? Can we send these msgs to another person to help further?
Plus, as I said I've been auto backing up weekly so how to restore old files, ROM, etc...via USB?
neadams99 said:
I can get into DL mode. Here is the readout from second ODIN attempt ( which shows it passed). <ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> NON-HLOS.bin
<ID:0/006> cache.img.ext4
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
Why would it not allow me into recovery mode?? that just makes no sense to me. I've tried it a dozen times and know to hold the three buttons for a long while. Then the phone shows "recovery reboot" or something like that in blue micro font up in the left top corner but then the CM logo comes on and then I get stuck again on Samsung logo forever. looks like your .tar files have the MD5 only, right? WHat more do I need to push onto phone? Can we send these msgs to another person to help further?
Plus, as I said I've been auto backing up weekly so how to restore old files, ROM, etc...via USB?
Click to expand...
Click to collapse
you're making me wanna beat you!! lol jk OK, read me/hear me and follow lol
you flashed 4.3 with Odin and looks like it worked, it should have auto reset itself after it worked and started booting back up into it's now completely stock rom...with me? you should see the Samsung logo working, it takes a good minute or 2 to finish its initial boot up after Odin, then like the 1St day you bought it you'll need to connect to a Wi-Fi source, sign in with a Google ID
did you do that or are you skipping the most important part of restoring your phone into working condition by right away trying to get into recovery mode?????? if so, please slap yourself hard!!! lol it must boot up and fully initialize, forget about recovery and back up roms right now, it must initialize like you just bought the phone new and set it up
THEN........
you have to reinstall philz recovery with Odin, remove the knox again and reroot by reinstalling supersu
saying it 1 last time...let the phone reboot itself after you performed the Odin steps from this guide and set up your phone like you just bought if brand new from sprint
do that, report back and stop messing with recovery steps and rom this and that or I'm not helping you bro!! lol report back
Not getting past Samsung logo
goku2778 said:
you're making me wanna beat you!! lol jk OK, read me/hear me and follow lol
you flashed 4.3 with Odin and looks like it worked, it should have auto reset itself after it worked and started booting back up into it's now completely stock rom...with me? you should see the Samsung logo working, it takes a good minute or 2 to finish its initial boot up after Odin, then like the 1St day you bought it you'll need to connect to a Wi-Fi source, sign in with a Google ID
did you do that or are you skipping the most important part of restoring your phone into working condition by right away trying to get into recovery mode?????? if so, please slap yourself hard!!! lol it must boot up and fully initialize, forget about recovery and back up roms right now, it must initialize like you just bought the phone new and set it up
THEN........
you have to reinstall philz recovery with Odin, remove the knox again and reroot by reinstalling supersu
saying it 1 last time...let the phone reboot itself after you performed the Odin steps from this guide and set up your phone like you just bought if brand new from sprint
do that, report back and stop messing with recovery steps and rom this and that or I'm not helping you bro!! lol report back
Click to expand...
Click to collapse
So so Sorry, if you were in CA, I'd come by so you could do it yourself. I;d even pay you good money. OK, sorry, I was freakin out, brah.
I did use ODIn and waited for a long time and the Samsung logo just hangs there. There is no progress, nothing. I can't get to the signing into Google or anything at all.
You said, " THEN you have to reinstall philz recovery with Odin, remove the knox again and reroot by reinstalling supersu." But I cant get past the logo. I see the "Samsung" for two secs, then "Samsung Galaxy Slll" then the Sprint logo goes by with music, then back to the "Samsung" logo where it sits forever. This is killing me.

[Q] Major issues flashing new ROM, help needed badly!

Hi.
First off, I've had my sgh-t999 since launch. I rooted it, and put TWRP recovery on it. I have used multiple roms over the past year with no problems at all.
I recently went to switch to a new rom. (new version of IOKP, upgrading from old infamous rom)
steps I took:
1. Placed rom on SD
2. Booted into Recovery
3. Wiped dalvik, and did full data wipe
4. flashed rom, success
5. Rom got stuck loading and wouldn't work.
Figured I needed to reinstall the rom, as this has happened to me before on previous phones.
6. Tried to reboot into recovery, Phone would not allow me to go into recovery, the blue text appeared at the top, but the phone would reboot itself after a second of the blue text leaving. (I tried adjusting the length of time I kept the buttons pressed down, both shorter and longer, to no avail.)
7. I looked up how to fix this. I used odin and the stock T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar.md5 to flash it back to stock.
8. The phone booted fine and I was back like normal. HOWEVER, I had no 4g, no wifi, my home button didn't work, and I had a lot of other errors.
9. I figured I should try to use a different stock rom, however ODIN began giving me error messages.
<ID:0/007> boot.img
<ID:0/007> Transmission Complete..
<ID:0/007> Now Writing.. Please wait about 2 minutes
<ID:0/007> Receive Response from boot-loader
<ID:0/007> recovery.img
<ID:0/007> Transmission Complete..
<ID:0/007> Now Writing.. Please wait about 2 minutes
<ID:0/007> Receive Response from boot-loader
<ID:0/007> system.img.ext4
<ID:0/007> Transmission Complete..
<ID:0/007> Now Writing.. Please wait about 2 minutes
<ID:0/007> Receive Response from boot-loader
<ID:0/007> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
No matter what USB port I use I get the same error. I even downloaded a .PIT file and tried to flash again. Same error message.
10. Now my phone is stuck. I cannot get into the phone, I cannot get into recovery, and when in download mode it reads "Firmware upgrade encountered an issue."
11. Kies doesn't even recognize my phone.
I am at a loss for what I need to do.
In case it helps my "download mode" screen says
sgh-t999
6 counts
binary:samsung official
status:custom
secureboot:enable
warranty bit:1
bootloader ap swerv: 1
Does anyone have any idea where I should go from here? I hate being stuck. I also use my phone for work, and am losing money the longer I go without it. If anyone can provide help, I would be forever grateful.
What is it that you're trying to flash? You need to flash the mjc firmware again, anything less than that won't work
Sent from my SGH-M919 using Tapatalk
serio22 said:
What is it that you're trying to flash? You need to flash the mjc firmware again, anything less than that won't work
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Stock 4.3: T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar.md5 was the file I had flashed. My phone booted up, but I had no 4g and no wifi. I hooked it up to odin again to reflash the same firmware, and my phone is now stuck at the black screen that says firmware update error.
Every time I use odin it returns an error no matter what stock firmware I try and use. I tried a .PIT file in combination with T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar.md5, and it still returned an error.

Looking for a debrick.img for Android 5.1.1

Is anyone able to point me in the right direction or is willing to make one?
The i747 does not have a stock 5.1.1 rom; therefore, there is no debrick image for a 5.1.1 rom.
What bootloader is on the phone? Did any of the images from the debrick thread boot the phone?
Does installing 5.1 change your bootloader?
As in Cyanogenmod 12.1?
Softbricked my S3, and I'm not sure which way to attempt to recover/debrick & would appreciate any advice.
SGH I747 (ATT)
rooted 2 years ago just after 4.3 OTA updated, flashed with CM 11.
Had that on there for almost a year, got bored & installed carbonrom.
Beginning of december, flashed CM 12.1.
A week ago it got stuck on the boot logo.
Still able to get into both Recovery & download modes.
Clockwork mod 6.0.4.7
trying to flash from a new image or wipe & factory restore both give me
Code:
detected file system ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
patching unconditionally
E: error in /storage/sdcard1/cm-12.1-201511117-sna[status 0] installation aborted
trying to use Odin, it gives me
Code:
<ID:0/003> Added!!
<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.img
but never does anything, even hours later.
At unplug, I get
Code:
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
The info on the download screen is
Code:
odin mode
product name: sgh-i747
custom binary download: yes (6 counts)
current binary: custom
system status: custom
qualcomm secureboot: enable
warranty bit: 1
bootloader ap swrev: 2
My guess from another thread is that the /system and /data partitions are not wiped properly, causing those partitions to be formatted with read-only (R/O) permissions rather than read-write (R/W)? But those files are definitely not right for my phone, so what now?
Use twrp to as cwm is out of date. Once on twrp, you can try flashing cm12.1 again.
Flashing a custom rom via twrp does not touch the bootloader or modem.
Do not flash any files via Odin as doing so could result in a hard brick. Once the phone is on a 4.3 or newer bootloader, Odin cannot be used.
audit13 said:
Use twrp to as cwm is out of date. Once on twrp, you can try flashing cm12.1 again.
Flashing a custom rom via twrp does not touch the bootloader or modem.
Do not flash any files via Odin as doing so could result in a hard brick. Once the phone is on a 4.3 or newer bootloader, Odin cannot be used.
Click to expand...
Click to collapse
Good to know.
Thanks.
But how do I get twrp onto the phone?
was actually trying to put twrp on with odin, but that's not working.
The downloads I've seen are for:
app-phone doesnt boot
odin- aint working
TWRP Install - Requires TWRP 2.8.4 or higher already installed
dd Install Method - oh, didn't see that one. I'll try that & let you know.:laugh:
---------- Post added at 06:54 AM ---------- Previous post was at 06:16 AM ----------
well, I'm not figuring it out....
As per the twrp page, tried: dd if=/sdcard/twrp-2.8.7.0-d2att.img of=/dev/block/mmcblk0p18
file not found error
tried: dd if=/storage/sdcard1/twrp-2.8.7.0-d2att.img of=/dev/block/mmcblk0p18
file not found error
did ls (hey it's like linux!)
got possible locations: external_sd, sd-ext, sdcard, also looked under mnt.
file not found error
cd'ed & ls'ed to /storage/sdcard1/ there it frickken is!
ran the command there, sans path, and still get file not found error
arrrrgh.
Try this:
1) download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=j...07763241,d.dmo
2) download the tar version of TWRP 2.8.7.0 from here: https://dl.twrp.me/d2att/
3) download the latest cm12.1 for the phone from here ( http://www.cmxlog.com/12.1/d2att/) and save it to a micro SD card;
4) download the version of cm12.1 gapps you want from here (https://wiki.cyanogenmod.org/w/Google_Apps) and save it to the same sd card where you saved CM12.1;
5) place the micro SD card into the phone;
6) boot the phone into download mode;
7) open Odin 3.07 and uncheck everything except f. reset time;
8) click on PDA and browse to the tar TWRP file and select it;
9) connect the phone and it should show up as a com port in Odin;
10) flash TWRP;
11) when you see the word RESET in the status window, remove the USB cable, remove the battery, replace the battery, use the button combination to get into recovery which should now be TWRP;
12) perform a full wipe of system, data, and cache;
13) flash CM12.1 and gapps from the micro SD card;
14) reboot and enjoy
very detailed response, thanks. I've tried most of that, as some thread I was reading said that twrp probably has the capability to fix the issue, and CWM definitely doesn't.
Odin never really does anything, though. How long should I wait?
This step is the one I haven't done "7) open Odin 3.07 and uncheck everything except f. reset time;" Just left everything alone the multiple times I tried. Hopefully that'll make a difference.
Tried 3.07, 3.09, 3.10.6. I'll try again.
By default in Odin 3.07, only auto reboot and f reset time are checked.
What do you mean when you say Odin does nothing? Does the phone appear as a com device in Odin? Are there error messages in Odin during the flash process?
never gives anything other than:
Code:
<ID:0/003> Added!!
<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.img
not at a windows computer for a couple days. stuck on linux mint with no internet. has heimdall & adb, though....
have twrp img & tar, cm12.1, and gapps on the sdcard.
All I can suggest is to try and get access to a pc or try VMware with win7.
Tried again last night for about 12 hours, no response from Odin.
Decided to give jtag a shot.
Contacted the jtag guy & gave him all the above info.
He says
"Unfortunately there are many indicators that your phone has a hardware failure.... Most likely a failed emmc memory chip.
1) the phone getting stuck on boot logo for no reason.
2) Odin not flashing...
3) files not found or... Not being able to do.
These are all indicators that the emmc memory chip is toast...... The biggest clue is finding the phone stuck on boot logo... Out of nowhere for no reason.
Jtag would not be able to fix it.
Thank you"
:crying::crying::crying::crying::crying::crying:
Thanks for the help.
Might sell the remains.
16G I747 blue, normal wear & tear, small chip in one corner, the case covers it.
2 stock batteries
1 7800mah best4power battery
1 otterbox defender modified to hold extended battery without the turtleback
any offers?
i suggest trying on a Windows machine before giving up. I am not convinced the memory is damaged.
That was on a windows machine...
Odin recognizes the phone but it won't flash twrp? Have you tried different USB cables and USB ports?
I found that my s4 and s3 would fail to flash if I don't use the USB cable that came with my Samsung or LG phones.
yes to both cable & ports.
bought an LG K7, which I mostly hate, and can not root.
keeping my S3, looking for someplace cheap to replace the chip.
I bought my lg k7 today(LGMS330)metropcs i rooted it in 2 mins.with xda's KINGROOT..then removed Kingroot with WOLFDROIDS script...and now im running BUSYBOX STERICSON 1.24.1 and ChainFires SUPERSU 2.49..IT KILLS me when people cant root there devices...i did this ALL in the BURGERKING BATHROOM GOIN BOO BOO
Ok so i rooted my darn k7 ...but like a jackars i bricked it...no TWRP...NO KDZ FIRMWARE...CAN ANYONE PLEASE ...PRETTY PLEASE SEND ME A LINK TO THE METROPCS variant of the LG K7 (TRIBUTE 5) KDZ STOCK FIRMWARE..I JUST BOUGHT A $150 ELECTRONIC PAPERWEIGHT...the k7 is so new there is no support anywhere...in fact all u really find is the ads for the debut of the device in stores ...major noob mistake..im truly embarassed..PLZ HELP
yeah, got it rooted. was missing the "enable oem unlock" step. d'oh.
thanks for the tip on the script.
no idea on the firmware. if you find one, let me know.
just got a $150 paperweight...lg ms330 i do hate you now...
o4tuna said:
yeah, got it rooted. was missing the "enable oem unlock" step. d'oh.
thanks for the tip on the script.
no idea on the firmware. if you find one, let me know.
Click to expand...
Click to collapse
I'm in the same boat as you...unfortunately tht step was completely left out in the directions I used so I now have a $150 paper weight as well....if anyone finds the stock firmware plz plz plzzzzzz let me know I would be forever gratefull....
AbErCrMbPlAyA said:
I'm in the same boat as you...unfortunately tht step was completely left out in the directions I used so I now have a $150 paper weight as well....if anyone finds the stock firmware plz plz plzzzzzz let me know I would be forever gratefull....
Click to expand...
Click to collapse
I had a amazing talk with the lg develeopers yesterday....since I am in the same boat since my lg k7 is bricked....I ask them for the kdz firmware so I can reflash my phone....you wanna know what they told me?
first they ask: whats a kdz file?
their answer: We don't make those thing you need the official lg tools to update your device firmware....so we cant help you...
Me: I am extremely pissed now since they are lying to me & then I showed them a link from their server to DOWNLOAD a kdz file firmware for another device that I had....
their answer: we dont know what you are talking about...sorry we can't help you!
I even went to my nearby metropcs store & explained to him what happen...
first. he didn't understand the following:
1-bootloader
2. boot image
3. recovery mode
4. download mode
5. kdz firmware
6. bricked & softed-bricked
the f-cking guy told me I can't do anything, but "report my phone lost or stolen" so I can get a new one....
How the hell are these idiots getting jobs when they have NO IDEA what to do on how to fix a phone
My level of anger is now over 9000.....

Possibly Bricked I9192! Can it be fixed?

Last status
Code:
Device: S4 Mini I9192
ROM: CM13 by k2wl
KERNEL: REMIX
RECOVERY: TWRP 3
So, let me tell you a sad story!
Yesterday I was talking a nap while my phone was charging. There was load-shedding, but my phone charged on IPS. But later I saw that it was showing the boot-up animation. I let it happen, but when I returned the phone was showing the "Samsung Galaxy S4 mini GT-I9192" splash screen and it was stuck there. I removed the battery, and reinserted and it was the same. I tried to boot up to my recovery, but after the splash screen, it was stuck on TWRP splash screen.
After a few try, I thought maybe I should wait for TWRP, maybe its doing something in background. Guess what, TWRP booted. When I checked log it was full of "unable to mount" error with various partitions. I was happy for a moment. So after that I tried to reboot to system. Now, there wasn't even any splash screen either. Tried to boot into recovery but even recovery isn’t booting. So I entered the download mode.
Code:
ODIN MODE
PRODUCT NAME: GT-I9192
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
CSB-CONFIG-LSB: 0x30
BOOTLOADER RP SWREV: 2
WRITE PROTECTION: Enable
Then I tried to flash the TWRP with Odin 3 v3.09 but it was stuck on:
Code:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
When I unplugged the phone while stuck, two more lines appeared:
Code:
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
At this point I lost any hope of recovering data and so I’m ready to flash a PIT file too. So I did some research and found the PIT file and tried flashing it. Odin was stuck at “Initialzation” again. After a few Google search, somebody suggested to use an old Odin, so I downloaded Odin3 v1.85 and retried. No luck but the Odin log was different
Code:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Complete(Write) operation failed.
Now I’m totally hopeless as I think the built-in storage is somehow corrupted so that even Odin can’t write it.
Few interesting things:
ADB cannot properly run while the phone is plugged in. ADB shows "server out-of-date" error. Then kills and return nothing. If repeated, same thing. Although all Odin recognizes the phone.
I tried a method of debricking with an img file on a sd card, but it fails on "parted" for some reason.
Kies keeps on showing "Connecting".
If nothing can be done, I'll just have to take my home to the repair shops. But will they be able to fix it? Any thing I'm missing?
I guess you already tried that, but if not - try reinstalling usb drivers. Skipsoft android toolkit might be helpful too. Check it out, it helped me out once in a similar situation.
komor555 said:
I guess you already tried that, but if not - try reinstalling usb drivers. Skipsoft android toolkit might be helpful too. Check it out, it helped me out once in a similar situation.
Click to expand...
Click to collapse
What exactly should I do using the Android Toolkit?
Run the software, let it download all the stuff. Next in the main menu, there are a few input options. First of all, try "I" with your phone connected and in download mode, to see what kind of device info the phone will return. If nothing shows up, try "DR", which will install drivers to work with adb, fastboot and recovery, on your local machine. You should do that even if you get the device info in the first place, just to try getting it again after driver installation for comparison.
Next, input 24 to run galaxy s4 mini module. Let the utility download and install all the module updates. After that, select DUAL SIM GSM MODEL [GT-I9192] by writing "02". It will ask for the android build, select the newest one (option 22). If you have a custom build, then you will have to unlock the Pro version by donating, but there might be no need for that, if option 22 works. Again, let it download.
Then you get access to a variety of options. First, unplug your phone, and run option 1 to install device drivers to your PC. Then, if you are lucky and ADB works, you can Install a .zip file using sideload (option 16) to your phone. Or you can just play around with other options. Maybe something will work. If the download mode works on the phone - that's usually a soft-brick, which is fixable.

Categories

Resources