Develop Bugs

[Q] Internal Memory Reduced from 32GB to 12GB After Root

Hi All,
This is my first post. So, I apologize now if I don't do it correctly per forum requirements.
I have a U.S. T-Mobile Samsung Galaxy S3, which I've rooted. I updated to T999UVDMD5 via the method described here - http://forum.xda-developers.com/showthread.php?t=2282603. I'm running Android 4.3.1. I just updated to Cyanogenmod 10.2.1.
Everything is great operationally. However, after using this setup for several months, I just realized that my internal storage has decreased from 32GB to 12GB. I'm now getting insufficient storage messages. I don't know if this happened from the method referenced above or when I first rooted the phone as I haven't hit a wall with storage until now.
I've looked into this issue on the forum and think I might need to update my PIT file, but I'm not sure. I don't feel confident enough in this route to do it. So, I'm hoping someone can assist me with figuring out what is going on.
Please help. Thank you in advance for your time and assistance.

Internal memory may reduce due to several reasons. Pit files is just one of them.
The UVDMD5 Thread you posted is for Bootloader only. In order to clear up your issue, Please fhash Root66 via Odin. Follow this thread for details. Make sure to choose UVDMD5 version alone.
Once that's completed, flash latest recovery of your choice (either CWM or TWRP). Then flash CM version again.

Perseus71 said:
Internal memory may reduce due to several reasons. Pit files is just one of them.
The UVDMD5 Thread you posted is for Bootloader only. In order to clear up your issue, Please fhash Root66 via Odin. Follow this thread for details. Make sure to choose UVDMD5 version alone.
Once that's completed, flash latest recovery of your choice (either CWM or TWRP). Then flash CM version again.
Click to expand...
Click to collapse
Thank you for the prompt response. I've done as you said. However, Odin is hanging on aboot.mbn. I haven't touched it, but it's been like this for about five minutes. The phone still reads, "Downloading... Do not turn off target!!" What do you advise I do? Thanks again.

Keep the phone in downloading mode. Make sure your download of Root66 is valid. Follow the instructions from the thread I linked. Reboot computer and try another cable.

Perseus71 said:
Keep the phone in downloading mode. Make sure your download of Root66 is valid. Follow the instructions from the thread I linked. Reboot computer and try another cable.
Click to expand...
Click to collapse
Thank you Perseus71. I'll give this a shot tomorrow and get back to you. I appreciate your help.

Perseus71 said:
Keep the phone in downloading mode. Make sure your download of Root66 is valid. Follow the instructions from the thread I linked. Reboot computer and try another cable.
Click to expand...
Click to collapse
I went ahead and gave it a shot. I plugged the micro usb into a USB 3.0 port on the back of the machine instead of using one of the auxiliary ports on the front of my computer. That seemed to fixed the problem. I guess a direct connection with the motherboard makes a different. It flashed and I'm back up and running with the stock rom.
Quick question - I created a backup of my phone today. If I flash cyanogenmod back onto it, can I restore the phone from that backup? Or, is it no good now since I flashed it with root66?
Thank you so much!

Perseus71 said:
Keep the phone in downloading mode. Make sure your download of Root66 is valid. Follow the instructions from the thread I linked. Reboot computer and try another cable.
Click to expand...
Click to collapse
Update: I just checked and unfortunately I still have the 12gb of space. What do you recommend I do from here? Sorry. I hate to continue to bug you with this. Thank you.

If you took a Nandroid after the Root66 flash today, you can restore it anytime. As to the Space, its probably taken up by Samsung Bloat. Go ahead and flash CM. Make sure to do factory Reset, wipe Dalvik + Cache before and after the flash.
Check the space usage immediately after flash. Post a screen of Storage settings at the end.

Perseus71 said:
If you took a Nandroid after the Root66 flash today, you can restore it anytime. As to the Space, its probably taken up by Samsung Bloat. Go ahead and flash CM. Make sure to do factory Reset, wipe Dalvik + Cache before and after the flash.
Check the space usage immediately after flash. Post a screen of Storage settings at the end.
Click to expand...
Click to collapse
I know the term, but I'm not 100% confident in what you mean by Nandroid. So I will just explain what I did. Prior to flashing root66, I used CWM Recovery to create a backup file on my SD card.
I downloaded ROM Manager and re-installed CWM Recovery. I then rebooted into recovery and wipe all data, wiped the cache partition, and wiped the Dalvik Cache. Then, I restored the backup I created before I flashed root66.
Next, I rebooted the phone. It's still telling me I have 12 GB of internal memory. One thing that is different from before is I have about 9GB of free space now versus roughly 1GB of free space before. I've attached a screenshot of this.
Another issue I am having, which I had before is I'm getting an insufficient storage message when I try to install certain apps. What's weird is the error doesn't come up with all apps, only certain ones. I've attached a screenshot of this error message as well. Lastly, I put a screenshot of part of my partition table in case you are able to see something I'm not, in there.
If you have any other thoughts on what might be going on, I would greatly appreciate your insight. Thank you.

What you did in CWM is the Nandroid. I didn't want you to restore anything before flashing Root66. So please can you wipe everything again and then flash Root66 ? This time don't flash CWM after Root66. Just check the Spaces.
P.S. - Continue using the phone in that fashion (Just Root66 nothing custom). For now at least.

Perseus71 said:
What you did in CWM is the Nandroid. I didn't want you to restore anything before flashing Root66. So please can you wipe everything again and then flash Root66 ? This time don't flash CWM after Root66. Just check the Spaces.
P.S. - Continue using the phone in that fashion (Just Root66 nothing custom). For now at least.
Click to expand...
Click to collapse
Sorry, I may have miscommunicated. I restored the Nandroid after I flashed root66. I did check the internal memory space before I restored the Nandroid and it hadn't changed. I'll flash root66 again and get back to you. Please standby. Thank you.

If it still continues to be the case, this post has correct .PIT file. You use Odin to flash it. I think you know that already.

Perseus71 said:
If it still continues to be the case, this post has correct .PIT file. You use Odin to flash it. I think you know that already.
Click to expand...
Click to collapse
Thanks Perseus71! I'm on a new computer today. So I'm downloading root66 again so I can flash it. If the issue remains, I'll flash the PIT file. I downloaded the file at the link you sent me.
Do you by chance know of a good tutorial on flashing the PIT. I presume it's the same process with flashing anything and I use the PIT button on Odin. However, I'm paranoid that I'll brick my phone and prefer to be over cautious than presumptuous. Thank you sir!

And the saga continues... man this is frustrating!
I flashed root66 and checked the storage in settings. It's still at 12GB.
So, I did some digging on flashing the PIT file. Everything I read said to accompany the PIT file with the ROM. So, I rebooted into download mode, then plugged in the micro-USB, and Odin recognized the device. I unzipped the PIT file on my computer. I then clicked the PIT button on Odin and selected the PIT file on my machine. Next, I added the root66 ROM via the PDA button on Odin. Then, I clicked the Re-Partition checkbox so that the Auto-Reboot, Re-Partition, and F. Reset Time checkboxes were all checked. I hit start and then Odin failed on me.
Here's what Odin said:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDMD5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> __Xmit Write fail
<ID:0/004> Removed!!
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Am I doing something wrong here? Please help. Thank you again for your time and assistance.

Perseus71 said:
If it still continues to be the case, this post has correct .PIT file. You use Odin to flash it. I think you know that already.
Click to expand...
Click to collapse
I think I may have really screwed up. Ever since Odin failed on the re-partition, it is no longer recognizing my device. When I go into "Devices and Printers" in Windows 8, it's no longer displaying SGH-T999. Now it's displaying "Qualcomm HS-USB QDLoader 9008 (COM7)"
I'm afraid I just bricked my phone. I hope you have better news for than this. Please help when you can. Thank you.

Do All of the same above but do not hit Re-partition. Here's a good Guide. Make sure you have latest Odin ( v3.09) and its running as Admin on Windows.

Perseus71 said:
Do All of the same above but do not hit Re-partition. Here's a good Guide. Make sure you have latest Odin ( v3.09) and its running as Admin on Windows.
Click to expand...
Click to collapse
Ok. Good news. I was afraid to reboot the phone from the Download mode after Odin failed (for fear that I might not be able to get back into Download mode). However, I did reboot it, and the phone rebooted fine into Touchwiz (courtesy of root66). My computer then recognized the device as SGH-T999 once again. (Thank you Jesus!)
So, I have now rebooted back into download mode. I've download Odin v3.09 as you suggested (was using v3.07 before). I've selected the PIT file and root66 (via Odin's rebranded AP button). However, when I select the PIT file, Odin automatically checks the Re-Partition checkbox. You told me not to check that this time. Stupid question but should I just uncheck it?
I haven't done anything yet as I'm now terrified after the last experience of venturing out on my own. Waiting on your guidance. Thank you again.

Perseus71 said:
Do All of the same above but do not hit Re-partition. Here's a good Guide. Make sure you have latest Odin ( v3.09) and its running as Admin on Windows.
Click to expand...
Click to collapse
Update: I figured it was relatively low risk to uncheck Re-Partition so I went ahead and un-checked it and flashed the PIT and ROM. It succeeded. The phone booted normally. I reboot into recovery, did a factory wipe and wiped the cache partition; then reboot.
Total space is still reading 11.95GB. Although, apps do appear to be installing fine. So that issue is resolved.
I discovered an interesting piece of information. I downloaded the app Partition Table and was able to get a picture of the internal memory card (see "mmcblk0"). It says it's "unmounted." See the attached screen shot.
Any ideas on where to go from here?

If you are up to it, get a Root Explorer such as ES File Explorer. Make sure to turn on its Root Features. (That requires granting Root Access to it.)
Now go to /Proc folder. You will see 2 files. Mounts and Partitions. Post them here please.
Also see if you CWM can mount all partitions.

Perseus71 said:
If you are up to it, get a Root Explorer such as ES File Explorer. Make sure to turn on its Root Features. (That requires granting Root Access to it.)
Now go to /Proc folder. You will see 2 files. Mounts and Partitions. Post them here please.
Also see if you CWM can mount all partitions.
Click to expand...
Click to collapse
Thanks man. I'm on it, but I'll have to get back to you tomorrow. I really appreciate your continued guidance. Talk to you soon.

Guess what? I bricked my SGH-i317M :)

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!

NO OS after wiping

I installed a Rom on my Sprint Galaxy Note 4 and when I installed it, it wanted me to wipe, so I did. The rom didn't take and now I can't get any rom, factory or otherwise to not fail in odin.
I have no phone an am freaking out. I have TWRP when I load into recovery, but no rom will take.
PLEASE help me.
My phone just updated to 5.1 lollypop and I rooted after. Root took, then installed rom, now i try to start and samsung comes up, the phone buzzes over and over again

What do you see on the screen when trying to boot up? Lollipop takes forever to start when you first flash. Give it 15 to 20 minutes at least.

There is no 5.1 u mean 5.01 hehe

w7excursion said:
What do you see on the screen when trying to boot up? Lollipop takes forever to start when you first flash. Give it 15 to 20 minutes at least.
Click to expand...
Click to collapse
Just Samsung...it buzzes, then samsung, then it buzzes.
It doesn't boot. I was able to get auto root to take, but any rom
N910PVPU1ANIE_N910PSPT1ANIE_SPR
N910PVPU1ANIE_N910PSPT1ANIE_N910PVPU1ANIE_HOME.tar.md5
N910PVPU1ANK2_N910PSPT1ANK2_XAS
N910PVPU1ANK2_N910PSPT1ANK2_N910PVPU1ANK2_HOME.tar.md5
N910PVPU1ABOB7_N910PSPT1BOB7_SPR
N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar.md5
I get this...
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Odin has a problem each time...
Any suggestions?

Ok, sounds like you took the OE1 update. You can fix this.
If in fact you are on OE1 the notarized rom by @SaintZ93 will get you up and running.
It's located here in the OP:
http://forum.xda-developers.com/showthread.php?t=3099382
Wipe the usual x 3 and flash it. You'll be good to go.
Quality rom by a quality guy.

jhill110 said:
Ok, sounds like you took the OE1 update. You can fix this.
If in fact you are on OE1 the notarized rom by @SaintZ93 will get you up and running.
It's located here in the OP:
http://forum.xda-developers.com/showthread.php?t=3099382
Wipe the usual x 3 and flash it. You'll be good to go.
Quality rom by a quality guy.
Click to expand...
Click to collapse
How do I get it over to my phone? I'm not sure how to flash it since the file is a zip and odin wants a tar file.
I removed the SD card and put the rom on that from my computer
I just pushed up on the volume, held the center button, and the power button, which pulled up dowload mode,but when I flashed the Noterized rom, it says:
install sd card
finding update package
opening update package verifying update package
E:footer is wrong
E:signature verification wrong
Thanks so much for trying to help
Dave

download the zip file to your pc then extract or unzip it, you will find the .tar file inclosed.
Sent from my SM-G920V

stealyourface1 said:
download the zip file to your pc then extract or unzip it, you will find the .tar file inclosed.
Sent from my SM-G920V
Click to expand...
Click to collapse
Extracting now..I'll update in a minute
Thanks so much

stealyourface1 said:
download the zip file to your pc then extract or unzip it, you will find the .tar file inclosed.
Sent from my SM-G920V
Click to expand...
Click to collapse
I see a META-INF
noterized
system
I don't see a tar file

wascapsfan said:
I see a META-INF
noterized
system
I don't see a tar file
Click to expand...
Click to collapse
That's because it's a recovery flashable zip.
You need to flash it in recovery. If you don't have custom recovery, google "Sprint Galaxy Note 4 TWRP" or see link below. Download 2.8.6, (latest as of this date) odin it then flash the rom.
How to :
Start TWRP (vol up & home & power) , goto wipe, factory reset x 3. Goto advanced wipe, tick dalvik, system, data and cache. Wipe those x 3
DO NOT WIPE EXTERNAL SD CARD!
Go to install and find the rom zip on your external sd card , install it and give it all the time it needs to install. 10 minutes or more... Maybe 15.
EDIT: Here's the link to TWRP :
https://dl.twrp.me/trltespr/

jhill110 said:
That's because it's a recovery flashable zip.
You need to flash it in recovery. If you don't have custom recovery, google "Sprint Galaxy Note 4 TWRP" or see link below. Download 2.8.6, odin it then flash the rom.
How to :
Start TWRP (vol up & home & power) , goto wipe, factory reset x 3. Goto advanced wipe, tick dalvik, system, data and cache. Wipe those x 3
DO NOT WIPE EX SD CARD!
Go to install and find the rom zip on your ex sd card , install it and give it all the time it needs to install. 10 minutes or more... Maybe 15.
EDIT: Here's the link to TWRP :
https://dl.twrp.me/trltespr/
Click to expand...
Click to collapse
I'm looking in the right direction here.... :good:
I'm still on the Yellow Sprint Spark page..

wascapsfan said:
I'm looking in the right direction here.... :good:
I'm still on the Yellow Sprint Spark page..
Click to expand...
Click to collapse
Patients...

SUCCESS!!!!!!! You guys are AWESOME!!!!!!
THANK YOU THANK YOU

wascapsfan said:
SUCCESS!!!!!!! You guys are AWESOME!!!!!!
THANK YOU THANK YOU
Click to expand...
Click to collapse
Congrats! A small piece of advice... When a new update is released, wait a little while and watch what is being said about it.
Again, congratulations on on bringing your phone back from the dead...

jhill110 said:
That's because it's a recovery flashable zip.
You need to flash it in recovery. If you don't have custom recovery, google "Sprint Galaxy Note 4 TWRP" or see link below. Download 2.8.6, odin it then flash the rom.
How to :
Start TWRP (vol up & home & power) , goto wipe, factory reset x 3. Goto advanced wipe, tick dalvik, system, data and cache. Wipe those x 3
DO NOT WIPE EX SD CARD!
Go to install and find the rom zip on your ex sd card , install it and give it all the time it needs to install. 10 minutes or more... Maybe 15.
EDIT: Here's the link to TWRP :
https://dl.twrp.me/trltespr/
Click to expand...
Click to collapse
I'm in the same boat too and am on my way to Following the instructions here, But my question is when you sat DO NOT WIPE EX SD CARD, we're talking about the micro SD card right? i can wipe out internal Storage without a problem?

HunterKiotori said:
I'm in the same boat too and am on my way to Following the instructions here, But my question is when you sat DO NOT WIPE EX SD CARD, we're talking about the micro SD card right? i can wipe out internal Storage without a problem?
Click to expand...
Click to collapse
Yes and yes. If you wipe internal storage you'll likely lose your pic's and media.
Imo, it isn't necessary to wipe internal storage.

jhill110 said:
Yes and yes. If you wipe internal storage you'll likely lose your pic's and media.
Imo, it isn't necessary to wipe internal storage.
Click to expand...
Click to collapse
I keep my stuff on my SD card mostly. I like having a clean sorage if i flash a rom

HunterKiotori said:
I keep my stuff on my SD card mostly. I like having a clean sorage if i flash a rom
Click to expand...
Click to collapse
Then your good.

Good for you.
---------- Post added at 02:49 PM ---------- Previous post was at 02:48 PM ----------
wascapsfan said:
SUCCESS!!!!!!! You guys are AWESOME!!!!!!
THANK YOU THANK YOU
Click to expand...
Click to collapse
Good for you.:good:

What next
After flashing OE1 the notarized rom i try to downgrade again to ob7 rom or nk2 so i could unlock it for international use but won't accept the downgrade any clue pls??????

S3 will only boot to Samsung logo. Please help.

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.

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