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.....
Related
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.
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.
I had a relatively good OmniROM on my Samsung Galaxy Note 2 SGH-I317M for a while. I was in the middle of listening to some music that my phone crashed and rebooted and it got stuck at the OmniROM logo. I waited but then as I noticed it's not getting anywhere, I rebooted the phone. Then it got stuck at the Samsung GN2 logo.
I can go to download mode and I do have TWRP 2.6.3.1 as recovery mode and it's working. The weird thing is that, when I go to TWRP it asks for a password which I'm sure I've never set up in first place! Using File Manager of TWRP, I can browse but all critical folders are empty (system, data, etc, ...). Even if I insert my external SD card, the sdcard1 folder doesn't show anything! Worse than all, I can't wipe, backup, restore, install or mount or pretty much any of the functionalities in TWRP as folders are empty and external microSD card is not mounted. I can confirm all folders exist but are empty as I said. Apparently, it is unable to mount any folder!!!
In download mode, I tried to flash the stock ROM for 4.1.1 and 4.3 but it always fails with NAND Write started Operation fail error. And just to make sure I have tried different versions of Odin, different cables and 2 computers, all same error. I appreciate if someone can help me. This phone is new.
Another symptom is that when I power off the phone and charge it by plugging it in, the battery logo shows up but it's always show empty. I know the battery is being charged because when in TWRP, it shows percentage on top of screen, say 83%. Please help.
I can even adb from my PC to the phone.
Here is what Odin shows:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLUCMK5_I317MOYACMK5_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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
idoit said:
I had a relatively good OmniROM on my Samsung Galaxy Note 2 SGH-I317M for a while. I was in the middle of listening to some music that my phone crashed and rebooted and it got stuck at the OmniROM logo. I waited but then as I noticed it's not getting anywhere, I rebooted the phone. Then it got stuck at the Samsung GN2 logo.
I can go to download mode and I do have TWRP 2.6.3.1 as recovery mode and it's working. The weird thing is that, when I go to TWRP it asks for a password which I'm sure I've never set up in first place! Using File Manager of TWRP, I can browse but all critical folders are empty (system, data, etc, ...). Even if I insert my external SD card, the sdcard1 folder doesn't show anything! Worse than all, I can't wipe, backup, restore, install or mount or pretty much any of the functionalities in TWRP as folders are empty and external microSD card is not mounted. I can confirm all folders exist but are empty as I said. Apparently, it is unable to mount any folder!!!
In download mode, I tried to flash the stock ROM for 4.1.1 and 4.3 but it always fails with NAND Write started Operation fail error. And just to make sure I have tried different versions of Odin, different cables and 2 computers, all same error. I appreciate if someone can help me. This phone is new.
Another symptom is that when I power off the phone and charge it by plugging it in, the battery logo shows up but it's always show empty. I know the battery is being charged because when in TWRP, it shows percentage on top of screen, say 83%. Please help.
I can even adb from my PC to the phone.
Here is what Odin shows:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLUCMK5_I317MOYACMK5_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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You're only kinda hosed....
You need to find an ODIN package WITHOUT the sboot.bin. That's the bootloader that is not flashing....
dicksteele said:
You're only kinda hosed....
You need to find an ODIN package WITHOUT the sboot.bin. That's the bootloader that is not flashing....
Click to expand...
Click to collapse
By reading around, I was getting the impression that I need to flash .pit file along with the stock ROM but as I don't want to get things worse I was reluctant to do it. My searches for odin package without sboot.bin takes me no where. Not that I am a super Android toddler but any help is certainly more than appreciated. Well Ok, I'm noob. admit it. :good:
Edit: I found out about N7100UBALJ2_N7100TCEALJ1_TCE ROM from http://forum.xda-developers.com/showthread.php?t=2523366 but not sure if that solves the problem or that's relevant as it's for N7100 and mine is SGH-i317m... same family but who knows maybe different ROMs! ?
Can you connect to your pc and transfer rom files?
If not, in download mode you can use adb.exe and "adb push / mnt/sd card rom name" if you can't transfer.
Don't use a pit file. That partitions all of your phone.
rangercaptain said:
Can you connect to your pc and transfer rom files?
If not, in download mode you can use adb.exe and "adb push / mnt/sd card rom name" if you can't transfer.
Click to expand...
Click to collapse
Update: I uploaded the recovery.log file from TWRP by accessing with adb in recovery mode.
Nothing happens when I connect it to PC in normal mode... I mean just connecting it as it is. (NOT in recovery mode or download mode).
Right now, I am in Windows and when I connect it in download mode, I try to adb but it says device not found. In recovery mode, I can adb but as I said in first post, I can't read or write. MicroSD is not recognized, so I can't put stock ROM there either. Is there any hope to get my phone back?
Don't use a pit file. That partitions all of your phone.
Click to expand...
Click to collapse
Well, I did try to flash a pit file from here, but it fails with same NAND Write error!
I have a good news.
So I went to /dev/block folder when ADBing and noticed mmcblk0 device. I manually mounted mmcblk0p1 and yoohoo it is mounted. It means now i can put my TWRP backup files there and run TWRP restore. Is that a good idea?! Does it make sense at all? I mean I am desperate for any way to get this thing back, a shadow of hope is huge for me too now.
Update: Ahhh damn it! I mount the MicroSD from adb to /external_sdcard (this is the folder where it used to mount my external microSD) in TWRP. Using File Manager provided by TWRP, I confirm the folder is there. But when I go to Restore section, it doesn't show any partition and it doesn't let me choose external memory. It's like this:
- Internal Memory (0MB)
- External Memory (0MB)
- USB OTG (0MB)
Any thoughts? I feel I am so close but not there yet.
The reason adb doesn't work is you need a setting checked in developer options. I wish that was a default setting.
You're not bricked if there's any lifesigns.
Have you used the Kies website? I generally don't recommend Kies, but when your operating system is borked, Kies has an emergency firmware recovery option.
Before you go to Kies, copy down the information on the sticker under your battery, and it will be case sensitive when Kies asks for that info.
rangercaptain said:
Before you go to Kies, copy down the information on the sticker under your battery, and it will be case sensitive when Kies asks for that info.
Click to expand...
Click to collapse
Alright, done.
The reason adb doesn't work is you need a setting checked in developer options. I wish that was a default setting.
You're not bricked if there's any lifesigns.
Have you used the Kies website? I generally don't recommend Kies, but when your operating system is borked, Kies has an emergency firmware recovery option.
Click to expand...
Click to collapse
When in Kies, it can't connect to my device. tried all usb cables and all 3 modes: Normal, download and recovery. Always says connecting... spinning forever. I suppose I should work in download mode anyways, right? Anyway, I went to Tools > firmware emergency recovery and entered the serial number. It finishes to 100% but it the end prompts with this error:
<Firmware emergency recovery stopped due to error. If the problem persists, please contact the Samsung service center.>
Now to report back the result from Kies FER:
I follow the instructions word by word. As the screenshot shows, Kies tells me to put phone into "Recovery mode"by pressing on power button. Well, either Samsung doesn't know what recovery mode is or ... Anyways, I take battery out and etc and boot to normal phone by pressing on power button... and "Free Upgrade"button is still grayed out. I go to Recovery mode (Power + Home + Volume Up) and it is still grayed out. (first screenshot attached below)
It's only in Odin Download mode (Power + Home + Volume Down and then Volume Up) that it becomes available.
After some time, the following error appears. I have done it a couple of times now and I restarted my Windows too. but no dice.
(second screenshot attached below)
idoit said:
Alright, done.
When in Kies, it can't connect to my device. tried all usb cables and all 3 modes: Normal, download and recovery. Always says connecting... spinning forever. I suppose I should work in download mode anyways, right? Anyway, I went to Tools > firmware emergency recovery and entered the serial number. It finishes to 100% but it the end prompts with this error:
<Firmware emergency recovery stopped due to error. If the problem persists, please contact the Samsung service center.>
Click to expand...
Click to collapse
And you're on an i317M on ATT?
Was this an original Rogers or Bell phone???
dicksteele said:
And you're on an i317M on ATT?
Was this an original Rogers or Bell phone???
Click to expand...
Click to collapse
I have i317M and it was originally for Bell. I got rid of stock ROM and then installed OmniROM until this happened.
Kies is not helping the poor smartphone either (well now it is dumbphone ). Keeps giving that error too.
idoit said:
I have i317M and it was originally for Bell. I got rid of stock ROM and then installed OmniROM until this happened.
Kies is not helping the poor smartphone either (well now it is dumbphone ). Keeps giving that error too.
Click to expand...
Click to collapse
Cool.... So where did you get this
I317MVLUCMK5_I317MOYACMK5_HOME.tar.md5
The ODIN file that's blowing up on the bootloader?
dicksteele said:
Cool.... So where did you get this
I317MVLUCMK5_I317MOYACMK5_HOME.tar.md5
The ODIN file that's blowing up on the bootloader?
Click to expand...
Click to collapse
I have to say this: When my phone was alive, in order to unlock the carrier from Bell, I had to flash a 4.1.1 modem and I flashed one from Rogers to unlock. So my under setting in my Phone was showing Rogers brand. Now with this in mind:
I downloaded that file from here under heading I317MVLUCMK5 4.3 Stock Firmware. I noticed it is for Rogers. (where for Bell was available too but I downloaded Rogers one.
I have tried some other original i317m stock roms (from sammobile.com), 4.1.1 for Bell but no luck same NAND error. I simply guess ODIN can't write anything, and the eMMC is corrupted! ?
idoit said:
I have to say this: When my phone was alive, in order to unlock the carrier from Bell, I had to flash a 4.1.1 modem and I flashed one from Rogers to unlock. So my under setting in my Phone was showing Rogers brand. Now with this in mind:
I downloaded that file from here under heading I317MVLUCMK5 4.3 Stock Firmware. I noticed it is for Rogers. (where for Bell was available too but I downloaded Rogers one.
I have tried some other original i317m stock roms, 4.1.1 for Bell but no luck same NAND error. I simply guess ODIN can't write anything, and the eMMC is corrupted! ?
Click to expand...
Click to collapse
It's trying write the sboot.bin file which is the bootloader.
The 4.3 bootloader slaps down any attempts to overwrite it. That's why you're seeing the fail.
I'm downloading a 4.1.2 to see if sboot.bin is in there
---------- Post added at 08:58 PM ---------- Previous post was at 08:23 PM ----------
Good news the I317M_RWC_I317MVLBMA3_I317MOYABMA3_Original.zip from the
Rogers – 4.3 Jelly Bean RWC_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3 download does not have the sboot.bin.
That should bring you back.. Or at least get past the ODIN flash fail
---------- Post added at 09:02 PM ---------- Previous post was at 08:58 PM ----------
idoit said:
I have to say this: When my phone was alive, in order to unlock the carrier from Bell, I had to flash a 4.1.1 modem and I flashed one from Rogers to unlock. So my under setting in my Phone was showing Rogers brand. Now with this in mind:
I downloaded that file from here under heading I317MVLUCMK5 4.3 Stock Firmware. I noticed it is for Rogers. (where for Bell was available too but I downloaded Rogers one.
I have tried some other original i317m stock roms (from sammobile.com), 4.1.1 for Bell but no luck same NAND error. I simply guess ODIN can't write anything, and the eMMC is corrupted! ?
Click to expand...
Click to collapse
Awesome on the firmware site BTW !
dicksteele said:
It's trying write the sboot.bin file which is the bootloader.
The 4.3 bootloader slaps down any attempts to overwrite it. That's why you're seeing the fail.
I'm downloading a 4.1.2 to see if sboot.bin is in there
---------- Post added at 08:58 PM ---------- Previous post was at 08:23 PM ----------
Good news the I317M_RWC_I317MVLBMA3_I317MOYABMA3_Original.zip from the
Rogers – 4.3 Jelly Bean RWC_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3 download does not have the sboot.bin.
That should bring you back.. Or at least get past the ODIN flash fail
---------- Post added at 09:02 PM ---------- Previous post was at 08:58 PM ----------
Awesome on the firmware site BTW !
Click to expand...
Click to collapse
Thank you very much dicksteele! I'm downloading it too and it will take 8 hours I believe, so I'll report back later. Now, here is the thing: Reading some comments from that page makes me be careful though.
Specifically, talking about the following comments:
Hi Guy, my problem is that my phone lost baseband version and IMEI number. I download the stock rom: TLS_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3; The rom did not fix the issue. After I install it, the baseband version and IMEI number still shown Null. Could you please help me? Thousands thanks!
Click to expand...
Click to collapse
This was posted long before the 4.1.2 came around, but you have all the guts there when trying to roll back to 4.1.1 not even aware that there might be a new bootloader added on 4.1.2 I317MVLBMA3 update and returning back to 4.1.1 is quite risky
If you did not touch your device before using rooted kernels and/or custom. I suggests that you must stay on 4.1.2.
Click to expand...
Click to collapse
Now, what should I do now to make sure I will be able to make calls, assuming (hopefully) I'll get this sucker back to life?
Oh boy, will I ever again install OmniROM on it? Hell NOOO!
You won't lose your baseband or IEMI. What you are doing is returning your phone to 100% factory stock (except for the 4.3 bootloader). You can deal with any other issues as they arise/if they arise from a working phone easier than you can from a borked phone.
Why eight hours to download?
idoit said:
Thank you very much dicksteele! I'm downloading it too and it will take 8 hours I believe, so I'll report back later. Now, here is the thing: Reading some comments from that page makes me be careful though.
Specifically, talking about the following comments:
Now, what should I do now to make sure I will be able to make calls, assuming (hopefully) I'll get this sucker back to life?
Oh boy, will I ever again install OmniROM on it? Hell NOOO!
Click to expand...
Click to collapse
The losing the IMEI was because of a different issue I believe.... The /efs partition holds all the important cel info. As long as that's not hosed you're fine...
OMNIROM should not have touched that.
Backing up your /efs can be done a couple of ways.
http://www.xda-developers.com/android/backup-your-efs-partition-with-easy-to-use-app/
So I downloaded that file and it took almost 8 hours. But it still has sboot.bin and boot.img file inside! Obviously flashing with Odin gave same error. @dicksteele: Can you please share with me the link I can download? I downloaded this file (http://rg.to/file/c036fd8b51b8836bf0a399eee83ee680/%20I317M_RWC_I317MVLBMA3_I317MOYABMA3_Original.zip.html) from http://androidromupdate.com/2012/11...-sgh-i317m-canada-original-stock-romfirmware/ under I317MVLBMA3 4.1.2 Stock Firmware, Rogers – 4.3 Jelly Bean RWC_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3
P.S. I opened the tar.md5 file with 7-zip.
@rangercaptain: My internet speed is good, it should have been because of the download link above (from rapidgator) which made it so slow. Where do you guys download from that's faster?!
Thanks everyone.
idoit said:
So I downloaded that file and it took almost 8 hours. But it still has sboot.bin and boot.img file inside! Obviously flashing with Odin gave same error. @dicksteele: Can you please share with me the link I can download? I downloaded this file (http://rg.to/file/c036fd8b51b8836bf0a399eee83ee680/%20I317M_RWC_I317MVLBMA3_I317MOYABMA3_Original.zip.html) from http://androidromupdate.com/2012/11...-sgh-i317m-canada-original-stock-romfirmware/ under I317MVLBMA3 4.1.2 Stock Firmware, Rogers – 4.3 Jelly Bean RWC_I317MVLBMA3_I317MOYABMA3_I317MVLBMA3
P.S. I opened the tar.md5 file with 7-zip.
@rangercaptain: My internet speed is good, it should have been because of the download link above (from rapidgator) which made it so slow. Where do you guys download from that's faster?!
Thanks everyone.
Click to expand...
Click to collapse
I'm a dumbass It was
I317M_RWC_I317MVLALJ2_I317MOYAALJ2_Original
And you're right it was rapidget that was slow.... I have a download manager that I use and it pulls it down quick.
Another location is here
http://www.sammobile.com/firmwares/3/?download=8176
I know I know RC.
You need a login to download, registration is free.
I'm trying to upload the one I downloaded but upload dies 3 MB into it.
If you have probs with the sammobile one, I'll try and get the other one downloaded so you don't have to waste another 8 hours because I'm a dumbass.
And 7zip to verify was good, that's what I did.
dicksteele said:
I'm a dumbass It was
I317M_RWC_I317MVLALJ2_I317MOYAALJ2_Original
And you're right it was rapidget that was slow.... I have a download manager that I use and it pulls it down quick.
Another location is here
http://www.sammobile.com/firmwares/3/?download=8176
I know I know RC.
You need a login to download, registration is free.
I'm trying to upload the one I downloaded but upload dies 3 MB into it.
If you have probs with the sammobile one, I'll try and get the other one downloaded so you don't have to waste another 8 hours because I'm a dumbass.
And 7zip to verify was good, that's what I did.
Click to expand...
Click to collapse
This is being downloaded quickly. Until that download is finished, I knew yesterday I downloaded I317M_BWC_I317MVLALJ2_I317MOYAALJ2_Original (Similar to the one you just said to download but for Bell). You're right, this one doesn't have sboot.bin but it does have boot.img. Anyways, I tried to flash it with Odin3 v3.04, and it fails on me!
Firmware update start...
boot.img
NAND Write Start!
Complete(Write) operation failed.
Now, I have no idea what to do next! Wow, phones and even products from big companies like Samsung are so fragile.
[Off-topic]
Boy, these last 3 days had been hectic. First this happened to my Phone. Then today, when I was in Windows (which I rarely use, I went on Disk Management and made my C partition active). Stupid Windows, wiped all my partition table!!! And now my laptop is a piece of brick too. Oh boy, you know, when it rains it pours!
I recently lost my S4. Loved that phone! Still hoping that some good samaritan will return it. This S3 was my son's phone. When power button is pressed, it freezes at the Samsung Galaxy SIII logo. It can only power on to recovery and download modes. Tried everything in recovery, but don't know what to do in download mode. It says ODIN MODE, PRODUCT NAME: SGH-I747, CURRENT BINARY and SYSTEM STATUS: Custom, QUALCOMM SECUREBOOT: ENABLE, Warranty Bit: 1, BOOTLOADER AP SWREV: 3 When plugged into charger, the phone powers on and a gray battery image appears before SAMSUNG and Samsung logo. The phone will only turn off when the battery is removed. He tried everything he could to get the phone to work. For my own satisfaction, I would like to learn more about the process and try to get this operational. I am not familiar with the technical language, but am eager to learn. Right now, I'm using my S2. Is there anyone who can help me with the S3?
Here's what I recommend:
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.
If you cannot get a signal, you probably need to update the modem and bootloader.
The above is assuming that your bootloader is unlocked, if it is not then the above operation would be less than ideal, so the first thing you need to know is if indeed a previous unlocking procedure has been performed because if not you need to load a stock OS.
Sent from my SM-N910F using Tapatalk
The ATT s3 bootloader has never been locked.
There is no stock ATT ROM beyond 4.1.1 that can be flashed in Odin. The only way to flash a stock ROM beyond 4.1.1 would be via TWRP or CWM.
Thank you for your recommendation Audit 13.
On Step 1), I could not download the Odin 3.07. Do you have another link?
On Step 2), I downloaded twrp-2.8.7.0-d2att.img.tar to my computer.
On Step 3), I extracted the 20151230 Nightly files to my micro sd.
On Step 4), I thought my OS was Android 4.0 (Ice Cream Sandwich). I selected download from version CyanogenMod 12.1 (Android 5.1) Open GApps. On the Open GApps page, there are choices. Would I select ARM platform, 4.4 android, and stock variant? I am not sure.
Odin 3.07: http://forum.xda-developers.com/attachment.php?attachmentid=1168421
Files that are to be flashed from TWRP must not be unzipped. They are flashed by TWRP in their zipped format.
Your OS could not have been ICS because I see that warranty bit is mentioned in your posts which means the phone was running at least a JB bootloader and modem.
Gapps are optional at the moment as they are not required for the phone to boot CM. The important thing is to get your phone up and running so you can determine the bootloader and modem currently installed on the phone.
If you want to install gapps, choose ARM, 5.1, and nano: http://opengapps.org/?api=5.1&variant=nano
Thanks audit13! I have gone through step 10. In Odin, it says PASS! in the upper left. In the status window below it says:
<ID:0/008> Added!!
<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> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/008> Removed!!
<ID:0/008> Added!!
Am I supposed to click on RESET in Odin? I have not seen the word RESET in the status window. The phone is still connected via USB. Should I continue to wait, or should I press EXIT?
Sorry, if I'm not understanding. I chose not to download the Gapps at this time. I just want this phone to boot to the home screen.
audit13 said:
Odin 3.07: http://forum.xda-developers.com/attachment.php?attachmentid=1168421
Files that are to be flashed from TWRP must not be unzipped. They are flashed by TWRP in their zipped format.
Your OS could not have been ICS because I see that warranty bit is mentioned in your posts which means the phone was running at least a JB bootloader and modem.
Gapps are optional at the moment as they are not required for the phone to boot CM. The important thing is to get your phone up and running so you can determine the bootloader and modem currently installed on the phone.
If you want to install gapps, choose ARM, 5.1, and nano: http://opengapps.org/?api=5.1&variant=nano
Click to expand...
Click to collapse
see step 7 and 11 of my post above.
Yay!! My phone works. Thank you Audit 13.
Great! Are you running CM or some other ROM?
It is running CM. But I would like to get it back to the android OS, when we first got the phone. Is that possible?
Also, somewhere during the process, it said my phone was unrooted and asked if I would like to root it. I declined, since I wasn't sure what that was. Sorry for my lack of knowledge.
audit13 said:
Great! Are you running CM or some other ROM?
Click to expand...
Click to collapse
I've been exploring the phone with the CM 12.1 and I am very satisfied. Thank you, Audit 13! Although at first, it looks so different, I am finding many positives. Most importantly, it's operational, which is what I wanted. It is running android 5.1.1, and I have so much storage. Over 11 gbs! Sorry for my ignorance, but a newer android OS is better, right?
I am planning to flash thru TWRP the Gapps you suggested. ARM, 5.1, and nano. I will make a backup before, in case something weird should happen. I copied the unzipped files to my micro sd. If I should succeed, I will go to At&t to get a sim card. Can't wait to use this phone!
I will let you know what happens.
karene said:
It is running CM. But I would like to get it back to the android OS, when we first got the phone. Is that possible?
Also, somewhere during the process, it said my phone was unrooted and asked if I would like to root it. I declined, since I wasn't sure what that was. Sorry for my lack of knowledge.
Click to expand...
Click to collapse
For root on cm13, you need to enable developer options and enable root access for apps, adb, or both.
For cm12.1, just flash supersu from twrp.
I installed gapps on cm 12.1, but did not flash supersu. I am so happy to have this phone working. Thank you Audit 13!!
audit13 said:
For root on cm13, you need to enable developer options and enable root access for apps, adb, or both.
For cm12.1, just flash supersu from twrp.
Click to expand...
Click to collapse
You're very welcome. We are all here to help.
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.