Database Users

[DEBUNK] The USB Jig

I'm seeing lots of people on these fora either saying they're getting a USB jig or advising somebody to get a USB jig to fix a problem they're having with firmware. I just wanted to take the time to explain a few things.
It is true that a USB jig was needed to get the phone into download mode with the i9000 (Galaxy S) and all it's variants, this was because download mode wasn't freely accessible and required special hardware (The USB jig simulates what the Samsung programmer does). It appears as if Samsung has dropped this policy and on our devices, the i9100 (Galaxy S2), download mode is freely accessible by using the key-combo at boot.
What Samsung has done instead is implement a counter which counts the times you flash an INSECURE kernels onto the device. Insecure means anything which isn't official and didn't come from Samsung. So if you flash an insecure ROM onto your device this counter goes and, if you then break your device and bring it in for servicing Samsung can see you flashed an insecure ROM onto your device. What the USB jig does on our devices is reset this counter, nothing more nothing less.
So onto the important part. If you can't get into download mode by using the key-combo the USB jig won't work either. The USB jig is not a magical device which will fix your bricked unit with fairy dust, also it will not allow you to access an ultra secret menu which will allow you to debrick your device. This might change with future updates to the bootloader but current it's like this.
I wanted to share this information because I'm seeing too much people placing their hopes on an USB jig, wishing it will allow them to debrick their device. This isn't so. Our devices are pretty idiot proof and real hard to brick. Unless you did something really dumb download mode is always available and this will allow you to debrick your device. If download mode is a no go, then debricking at home is a no go too.
So remember, no download mode through key-combo equals no download mode through USB jig which in turn equals to no debricking at home.

I am about to buy a SGS2 and i have a self-made jig that saved both my SGS1's numerous times before. I will try it anyway to confirm if it does or does not.
EDIT:
also, im not sure about my argument but these jigs are made with mostly electrical engineering in mind, NOT software engineering. the self-made jigs
are made of soldered resistors (301k total resistance) onto a microUSB's 4th and 5th pins to sort of SHORT the microUSB port of the i9000s making
the phone boot on download mode (which is activated by a switch once the SHORT is done). i have ZERO experience with the i9100s so i can't prove if my statement is true for i9100s as well.

atlaswingpasaway said:
I am about to buy a SGS2 and i have a self-made jig that saved both my SGS1's numerous times before. I will try it anyway to confirm if it does or does not.
Click to expand...
Click to collapse
This post is dumb and you should feel dumb.
OP is 100% right, if you can't access download mode through the keycombo a USB jig will not work.
If you want to confirm it, make sure to flash some SGS1 files to your SGS2 and pull the battery in the process, then see if your magical USB jig will save you.

Download mode was infact freely available on many SGS I9000s without the jig. However a notable portion have a fault with the bootloader. Samsung (Canada I think?) did release an official patch for this I believe.
The common 301k resistor jig, does interact with a micro controller, that can not be overwritten and can force download mode if that part (download mode) of the bootloader is not damaged, even if the button controls were. The JIG was a proven method of repairing the device in some but not all cases of devices that no longer responded to the 3 button combination.
Assuming the SGS2 uses the same system (which to my knowledge it does, but I haven't looked into it extensively), then the 301k jig may not be a blanket solution but should not be discounted as useless.
EDIT: Some of the OP is outright fallacious when dealing with the S1 but I don't have much to say about its effectiveness on the S2

Even if it does not boot into download mode on a phone that fails to answer the key combo its a useful tool at the cheap price to remove yellow triangle and rom count .
jje

All these problems with bricked phones can easily be avoided by repackaging leaked firmwares to not update included bootloaders unless absolutely neccessary. So remove sbl.bin and boot.bin and flash away and you'll never not be able to get to download mode.
Sent from my GT-I9100

Idan73 said:
All these problems with bricked phones can easily be avoided by repackaging leaked firmwares to not update included bootloaders unless absolutely neccessary. So remove sbl.bin and boot.bin and flash away and you'll never not be able to get to download mode.
Sent from my GT-I9100
Click to expand...
Click to collapse
OP: LOL! Only a small portion of SGS 1 handsets had the bootloader issue most of the time you could enter recover/download mode with 3 button combo. There was a fault with many batches of SGS 1 phones that could not boot into recovery/download modes. In some occasions after flashing new firmwares you might face the same issue and the only way to get into download mode would be through ADB if the handset was still on or with a JIG cable if the phone was off. Plus the JIG cable now resets the flash stats and yellow triangle so I am happy to still have it around for my SGS 2
Idan73: param.lfs can also create a dead phone if interrupted during flash

Lol.
Not completely correct. My phone wouldn't stay off due to a dodgy usb port long enough to do the three button combo. Pulled battery, jig inserted, battery inserted, into download mode.
Sent from my GT-I9100 using XDA App

I think the vast majority of people on here know what the jig is for. People get them to reset the flash counter, not to go into download mode.

Hell for a couple of Quid its handy to have around, i used it to get rid of the triangle 2 secs done good money well worth spent

Oh My Yellow Triangle!
Same here used it on my Captivate as it was hard to get into download mode, on my SGS2 it is convenient with the added bonus of getting rid of the yellow triangle (which is the main use now)!!

There is a few things not right in the OP:
1) "insecure kernel": an insecure kernel is a kernel that runns ADB with root privs's, has nothing to do with who made it. "secure kernels" run adbd with only user privs.
2) the counter counting: has nothing to do with secure/insecure kernels! The counter counts how may not-Samsung-signed (=custom) kernels have been flashed
3) unbrick: the SGS2 has 2 secondary bootloaders, there's a theory that the JIG may cause the phone to boot into the backup when the current active one is corrupted
@OP: please check your facts before making such a thread, thank you.

Also OP, you're not right. I've been able to force download mode on SGS II that wouldn't enter into download mode with the 3 button combo after a failed flash using a Jig and reflashed the firmware. So you should make stupid statements without checking your facts.

uppon2 said:
OP: LOL! Only a small portion of SGS 1 handsets had the bootloader issue most of the time you could enter recover/download mode with 3 button combo. There was a fault with many batches of SGS 1 phones that could not boot into recovery/download modes. In some occasions after flashing new firmwares you might face the same issue and the only way to get into download mode would be through ADB if the handset was still on or with a JIG cable if the phone was off. Plus the JIG cable now resets the flash stats and yellow triangle so I am happy to still have it around for my SGS 2
Idan73: param.lfs can also create a dead phone if interrupted during flash
Click to expand...
Click to collapse
I don't know what the situation was in Australia but here the bootloader was locked through an update. Download mode was available at first but was later on disabled. I'm not sure which specific update it was I think it came after the 2.1 update or something.
HellcatDroid said:
There is a few things not right in the OP:
1) "insecure kernel": an insecure kernel is a kernel that runns ADB with root privs's, has nothing to do with who made it. "secure kernels" run adbd with only user privs.
2) the counter counting: has nothing to do with secure/insecure kernels! The counter counts how may not-Samsung-signed (=custom) kernels have been flashed
Click to expand...
Click to collapse
Did I go into details about insecure kernels? Without going into too much tehcnical detail I think I explained it quiet well, don't you think?
3) unbrick: the SGS2 has 2 secondary bootloaders, there's a theory that the JIG may cause the phone to boot into the backup when the current active one is corrupted
Click to expand...
Click to collapse
Please open your SGS2 and point me to the physical location of this second chip? Or else point me to the locations within the PIT file? Or anything that might even hint at the presence if this secondary loader.
Intratech said:
Also OP, you're not right. I've been able to force download mode on SGS II that wouldn't enter into download mode with the 3 button combo after a failed flash using a Jig and reflashed the firmware. So you should make stupid statements without checking your facts.
Click to expand...
Click to collapse
Make me a video then. I'll even ship you a JIG. Brick your device and recover it with a JIG. I dare you!
drspikes said:
Lol.
Not completely correct. My phone wouldn't stay off due to a dodgy usb port long enough to do the three button combo. Pulled battery, jig inserted, battery inserted, into download mode.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
That has nothing todo with this issue, you said it yourself, dodgy USB port. Hardware failures are not included.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

GIR said:
Did I go into details about insecure kernels? Without going into too much tehcnical detail I think I explained it quiet well, don't you think?
Click to expand...
Click to collapse
No, I don't
GIR said:
Please open your SGS2 and point me to the physical location of this second chip? Or else point me to the locations within the PIT file? Or anything that might even hint at the presence if this secondary loader.
Click to expand...
Click to collapse
Partitions 2 and 3, SBL1 and SBL2 respectively, that's the Secondary BootLoaders. Two of them, one active, one backup in case of corruption of active one.

HellcatDroid said:
No, I don't
Click to expand...
Click to collapse
Everybody has an opinion.
Partitions 2 and 3, SBL1 and SBL2 respectively, that's the Secondary BootLoaders. Two of them, one active, one backup in case of corruption of active one.
Click to expand...
Click to collapse
Except for the fact that SBL stands for Secure Bootloader, you might be right.... oh no you are not! SBL1 and 2 are just a safeguard. When you're updating the SBL it doesn't flash to the active but to the other one and once verified as being operational it's marked as being active.
You can read all about it here.
http://forum.xda-developers.com/showthread.php?t=1104139
Doing a wrong flash to one of the SBL's will still allow you to access download mode through the key-combo.
/edit:
Oh btw, just so you know, the PIT file suggestion was a trick. The phone will always be able to access download mode unless you destroy your partitioning by pulling the battery mid process or using a wrong pit file, this is the only way to brick your device.
If you do either and destroy your partitioning then those SBL's wont help you either. The only way to have a secondry bootloader is by having a secondary flash chip on the device. And guess what? There is none!

OK, I stand corrected on that one.
Doesn't change the fact the original post is flawed and wrong at many things as well.

HellcatDroid said:
OK, I stand corrected on that one.
Doesn't change the fact the original post is flawed and wrong at many things as well.
Click to expand...
Click to collapse
Boohoo cry me a river! Point of the post was to debunk the jig debrick myth. If you want to get into side issues you'll find your livingroom wall will be more interested. If you want to claim these side issues as being many, well then you apparently can' t count because it's just one, the secure kernel thing.
Sent from my GT-I9100 using XDA Premium App

A bit agressive, aren't we?

CM7 Wifi Error

My post count is low or I would be posting this in the CM7 thread.
I upgraded from Alien, and wifi worked then, but it now gives me an error in CM7(as in it doesn't work, and just says "error"). It does the same with bluetooth. The cell data connection works.
To fix this, would I need to reinstall CM7 or the radio or what? Thanks!

Did you follow instructions and clear everything before installing CM7? (Like the cache and dalvik cache?)

Yes, I have wiped everything, before and after the installation(I've tried reinstalling several times since, with no change). I'm also curious about which kernel to use... Does it come with it's own..?

jefesaurus said:
Yes, I have wiped everything, before and after the installation(I've tried reinstalling several times since, with no change). I'm also curious about which kernel to use... Does it come with it's own..?
Click to expand...
Click to collapse
it comes with its own

I had this issue as well. It is not a good sign that the bluetooth is not turning on either. For me, it was a hardware issue and I had to get a replacement. Try reinstalling kernel/wiping dalvik cache. If that doesn't work, try a fresh install of stock 1.8.3 or alien. If that doesn't work, you are SOL.

I've had this a couple times. It seems to be related to something with ext4 and the kernel. Try downloading the faux 1.9 kernel and re-installing that, if not, you could try re-installing the rom. If all that still doesn't work, try wiping everything from fastboot, and do a re-install from scratch. I really doubt it's hardware related. I"ve had this error twice and each time it was related to the kernel.
Make sure you have the right recovery installed too. I'm just thinking as I type this that that may be related. You can use the version from rom manager if you want.
Fastboot commands to wipe everything so you can start from scratch.
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase cache
fastboot erase preinstall
fastboot erase webtop
Good luck!
Edit, you didn't say which version of the atrix you have, but It might be an idea to download the corresponding radio for your phone.
For example, I have a bell atrix, and my install would go as follows:
I would wipe the phone using fastboot, then install the cm7 zip file, then install the faux 1.9 kernel, and then install the latest bell radio.

Anamnesis said:
I've had this a couple times. It seems to be related to something with ext4 and the kernel. Try downloading the faux 1.9 kernel and re-installing that, if not, you could try re-installing the rom. If all that still doesn't work, try wiping everything from fastboot, and do a re-install from scratch. I really doubt it's hardware related. I"ve had this error twice and each time it was related to the kernel.
Make sure you have the right recovery installed too. I'm just thinking as I type this that that may be related. You can use the version from rom manager if you want.
Fastboot commands to wipe everything so you can start from scratch.
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase cache
fastboot erase preinstall
fastboot erase webtop
Good luck!
Edit, you didn't say which version of the atrix you have, but It might be an idea to download the corresponding radio for your phone.
For example, I have a bell atrix, and my install would go as follows:
I would wipe the phone using fastboot, then install the cm7 zip file, then install the faux 1.9 kernel, and then install the latest bell radio.
Click to expand...
Click to collapse
I agree with everything except installing faux's 1.9 kernel. It's not optimized for the CM7 beta, so I would recommend against that.

So are you trying to say I didn't have a hardware problem? Re-installing stock 9 times (using the fastboot erase commands) and even flashing back to 1.8.3 did not solve my bluetooth/wifi issue. I've heard of people having the wifi error, but no trouble with bluetooth. The OP is having both, which is what I had. The only way I could get it to work (for 10/15 minutes) was to rub the back of the phone under the cover. It would work, connect, and then the wifi module would crap out.

I didn't realize that, sorry. I'm running it with no issues, but if your having issues then I would listen to Kraise.
---------- Post added at 03:48 AM ---------- Previous post was at 03:44 AM ----------
jiggytom said:
So are you trying to say I didn't have a hardware problem? Re-installing stock 9 times (using the fastboot erase commands) and even flashing back to 1.8.3 did not solve my bluetooth/wifi issue. I've heard of people having the wifi error, but no trouble with bluetooth. The OP is having both, which is what I had. The only way I could get it to work (for 10/15 minutes) was to rub the back of the phone under the cover. It would work, connect, and then the wifi module would crap out.
Click to expand...
Click to collapse
I'm not sure if my Bluetooth was or wasn't working when I had the issue. I have horrible reception in my condo so when I have issues with wifi I try to fix it immediately. Yours sounds like hardware.
To be honest though, my suggestions were directed at the OP. He JUST installed a new rom, and it was all working previously. The bluetooth, wifi, 3g, ect are all part of the radio. It seems much more likely to be related to software than hardware, as others have had the same problems. You really seem to take what I said personally, like it was an attack on you or something, but I was honestly just trying to help out and contribute in a positive fashion. My comments could not have been directed at you, as you didn't even post what your experiences were in the thread. Try to chill out a bit.

I was having issues with my wifi and bluetooth out of nowhere before I ever unlocked or rooted my phone. It was a little over a month after AT&T/Motorola released the Gingerblur(2.3.4) update to my phone which I had to download using a wifi connection. Out of nowhere, it stopped working... Bluetooth would not turn on, and Wifi always says "error" underneath it. I believe mine may actually be a hardware related issue.

DAMN! I just started experiencing this. Bluetooth won't turn on and Wifi "ERROR." This came out of no where. Actually, thinking back, I dropped my phone this AM, but I am almost 100% sure it was working after that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Kraize said:
I agree with everything except installing faux's 1.9 kernel. It's not optimized for the CM7 beta, so I would recommend against that.
Click to expand...
Click to collapse
Try the Faux 1.0GHz stopgap kernel. I use that and it works better for me with CM7 than the packaged kernel because you can UV.

J-man67 said:
DAMN! I just started experiencing this. Bluetooth won't turn on and Wifi "ERROR." This came out of no where. Actually, thinking back, I dropped my phone this AM, but I am almost 100% sure it was working after that.
Click to expand...
Click to collapse
check if you have the correct permissions for /data/misc/wifi/wpa_supplicant.conf. Try fixing permissions first through ROM Manager. Hope it helps.

Yeah, I was looking into that and modified/changed some settings around to no avail. I am going to try wiping and re-flashing and starting from scratch. It may be related to me dropping it this am. Wasn't a big fall, but that it the only thing I can think of at this point.

PHUCK!!! Just completed a COMPLETE wipe and re-install and same thing. Looks I am picking up a set of tools to crack this baby open. Maybe the lead from the radio to the board became disconnected when I dropped it. Worth a shot before I rely on Best Buy to warranty exchange it.

J-man67 said:
PHUCK!!! Just completed a COMPLETE wipe and re-install and same thing. Looks I am picking up a set of tools to crack this baby open. Maybe the lead from the radio to the board became disconnected when I dropped it. Worth a shot before I rely on Best Buy to warranty exchange it.
Click to expand...
Click to collapse
I have the same error - as I imported the phone, I don't have much in the way of warranty.
This guide shows there's no direct lead from the radio to phone - http://www.ifixit.com/Teardown/Motorola-Atrix-4G-Teardown/4964/2

Thanks! I am going to open her up and make sure that chip is still intact. Might be soldering it back in if need be. Seems that it will be the issue as Bluetooth does not turn on either.

While I haven't had the problem, I have a friend who from what he's telling me has the same WI-Fi error problem ever since updating to the AT&T 2.3.4. He has never rooted or unlocked and wants to update to the new 2.3.6 OTA, but can't due to the Wi-Fi error. Anyone make any headway on a solution?

It's a hardware issue.

Hi,
i experience the same problem with my friend's htc mytouch 3g, when i tried to install cm7 on it,
after that i tried fastboot erase system -w, then installed another ROM to be sure, i found that the WiFi now working fine,
so before opening her up try to install another rom like Dark-Side 2.3.5 or GingerMod 2.3.6, if the problem go away then it's cm related not hardware,

[Solved] Encryption Unsuccessful error for samsung vibrant.

Ok, Tonight i tried to install ICS Passion rom on my old samsung vibrant( is running bionix 2.2 rom). Following the instruction from ICS Passion rom thread , - First i tried to install CW7 gingerbread rom ( got some boot loop, ..)
- Then i boot to recovery mode again , install ICS passion rom, screen flashed like crazy and got boot loop one more time.
- Reboot to recovery again, reinstall ICS passion , everything went though perfectly this time.
- Finally, my phone booted up and show me this screen ( WTF***** )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- I tried to press the reset button , phone turned off/on and showed me this screen again. Tried this 3-4 time but nothing changed .
How i solve this problem ?
- I tried to search google to get more information about what is going with my phone. Basically, there are alot of people have exactly same problem as mine.
- I found one instruction that told me to fixed the problem, i need to flash 2.1 stock rom by using ODIN ( download everything from this link: http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/.)
1st Attempt: :
- Open ODIN, load file, put my phone into download mode..Hit start.Nothing happened. ODIN recognized my phone but the process stopped
2nd Attempt: :
- Changed usb port, did exactly same thing , the process now stopped at "analysis file" ..step
3rd Attempt: :
- Looked up google again, someone suggested that using Eugene_2E_JK2_Froyo.tar.md5 instead the stock 2.1 firmware might help. So i downloaded Eugene file, ran ODIN again. Still out of luck, process stopped at "leave CS.." step. At this point, i thought i bricked my phone already. So i unplugged usb cable from my phone. Tried to turn off, turn on my phone again, and it show me this screen (
4th Attempt: :
- I took the battery off, put it in, put my phone into download mode one last time. Open ODIN, load 2.1 stock file this time, hit start button and then BUMP..ODIN started to re-flash the firmware..And now my phone back to stock 2.1 .
P/s:
- sorry for my English, but hope this might help other people who get this error when trying to install ICS on their Vibrant.
- Any suggestion for me to install ICS again in correct way ? Thank in advance!

Does your internal sd card mount and can you access it? If yes, then you probably are the first one to get through this error. Congrats! Eugene's froyo has saved many many phones.
Edit: Strike that, it was a silly question.

No no really, do you have access to everything?? Cause i havent heard of a single person yet that got thru this bug with their sd card intact
Sent from a cell tower to the XDA server to you.

Finally, I successfully installed ICS on my vibrant. When i open setting, storage, it show my internal internal storage(about 2GB) - usb storage (about 14GB) - and my 8GB external sdcard. When i connect my phone to my computer, turn on usb storage, i can acces internal SD and external SD card ( can copy, paste, transfer files..) The gallery is able to show/view/play both video and image i have on my internal-external SD card but i can only access the internal one. I tried to find the external SD card but don't know where is it located. Is it mount as folder external_sd ?
****************
Ok, i found it. On ICS, the external sd card is mount as /emmc. Now i am able to access both of them. Nothing is broken in here.

In Passion your external is now EMMC.
So you can get to your internal just fine? When you pull up settings->storage you get readings for internal AND external.

Woodrube said:
In Passion your external is now EMMC.
So you can get to your internal just fine? When you pull up settings->storage you get readings for internal AND external.
Click to expand...
Click to collapse
Yes, it show me both internal and external.

tritran18518 said:
Yes, it show me both internal and external.
Click to expand...
Click to collapse
Now the question is...were you able to recover all your data from your internal storage? Or did it get wiped out in the process?
I wouldn't necessarily say you have solved the bug. I would rather say...you are extremely lucky sir The reason why i say that is because i could flash back to 2.1 as you did in your 4th attempt and would still get the same results (bootloop). I would really like to know what it was that you did...i have tried everything you've mentioned in your post numerous times in the past and still haven't found a proper fix for this bug. From your post it appears to be more like trial and error...in other words you just got lucky and somehow fixed your phone. Can you please elaborate and be more specific as to what you did. I and the many other people affected by this bug could really use your help since you are probably the only person who has successfully squashed the bug so to speak.
Good to hear your phone is functioning properly. This could only be good news.
Sent from my Galaxy Nexus using XDA

Merio90 said:
Now the question is...were you able to recover all your data from your internal storage? Or did it get wiped out in the process?
I wouldn't necessarily say you have solved the bug. I would rather say...you are extremely lucky sir The reason why i say that is because i could flash back to 2.1 as you did in your 4th attempt and would still get the same results (bootloop). I would really like to know what it was that you did...i have tried everything you've mentioned in your post numerous times in the past and still haven't found a proper fix for this bug. From your post it appears to be more like trial and error...in other words you just got lucky and somehow fixed your phone. Can you please elaborate and be more specific as to what you did. I and the many other people affected by this bug could really use your help since you are probably the only person who has successfully squashed the bug so to speak.
Good to hear your phone is functioning properly. This could only be good news.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
- Because i did a factory reset so all kind of system data is clear, but photo, video, music...other files in both external and internal sd card still there and accessable. Just like you wipe your phone when you install a new rom.
- I think the key in here is :
+ i got the error message, and i tried to press the reset button 3-4 times without take off my sd-card from my phone. And it's still give the error message
+ I odin to stock 2.1 . fail - tried 2 time
+ change usb port, flash 2.1 again. fail - tried 2 time
+ flash eugene 2.2 ...fail. And while my phone still show me the downloading screen , i just took battery off, put it on, turned on and it show me the new screen ( computer-phone)
+ turn off, put to download mode, flash 2.1 again and success.
==> that is pretty much everything i remember. And i'm sure i remember it right.

Passion is based on an early cm9 base. Until they update I feel you would be better off flashing cm9 since it has nightly updates now.(nightlies)

ferhanmm said:
Passion is based on an early cm9 base. Until they update I feel you would be better off flashing cm9 since it has nightly updates now.(nightlies)
Click to expand...
Click to collapse
i always pick rom base on the view of rom's thread. roms updated daily doesn't mean it is more stable than other roms ( this is what i learn from XDA)

This bug seems to happen with several diff ics roms, not just passions....
If i may venture my uneducated guess as to what happened to you:
As your odin was writing something on your phone and you pulled the batt, you corrupted the data... that means that the encrypted data and all that stuff got wiped on the next attempt and its like you had a new phone..
Prob wrong tho
Sent from a cell tower to the XDA server to you.

tritran18518 said:
i always pick rom base on the view of rom's thread. roms updated daily doesn't mean it is more stable than other roms ( this is what i learn from XDA)
Click to expand...
Click to collapse
Best ics roms out IMO are br1ck'd and team DD's ICZenwich or Team Kangs AOKP build 31, both with MP's sub zero build 61 kernal.
Sent from my SGH-T959 using xda premium

You are a very lucky man. I got mine working with cm7 after bricking it like that just enough to sell to someone as "a portable wifi hotspot for whatever plan you want." For $50
Sent from my SAMSUNG-SGH-T989 using XDA

YESSS!
I had this issue today october/31/2012, i followed OP instructions and it works! Thank you very much. The only difference is that i pressed the reset phone button and when i realized that was a mistake ( you know, when installing something and you just click and say:yeah, yeah, whats next?) i pulled out the battery as soon as i can, i searched on the web, found this thread and instead of flashing stock firmware (eclair) i flashed froyo straight.
I hope this helps somebody like it help me.

So you have access to your internal SD?
Also what ROM were you running?
Did it happen after flashing or was it random?
Please give as much info as possible as this issue (EU) is still, for the most part, a bit of an enigma.
I approve this message.

Hello there
Yes, i have access to internal and external sd card
Before the issue I was running chimera v2.2 and chimera kernel but i wanted to flash aokp lastest releases so i used odin to stock, then flashed cm7 (here it give me bootloops but i just went to next step) then chimera 2.2 (here was when EU appears, my intention was after flashing chimera 2.2 flash aokp )
If you need more details just ask me.

You're actually very fortunate to still have Int SD access esp. after pressing the EU reset button. Since EU has been primarily associated with ICS for our Vibes (and theoretically wiping /data with CWM5), you can just skip Chimera altogether. After restocking and flashing CM7 (vibrantmtd), either go straight to AOKP JB or use a recent CM10 as an interim flash.

I know im fortunate, the reason i pulled out the battery after pressing the reset button is because i knew about the EU issue.
About flashing CM7 and then AOKP JB i did not know that i can do it that way, thank you.

My LG G2 is COMPLETELY bricked.

So after 20 hours of fiddling... I can safely say that this LG G2 D803 is completely done.
Given by a friend, the phone started off by booting straight to fastboot, and had download mode available after he flashed a ROM designed for a tablet.
I attempted the .TOT method described here, where I used LGTools. I then only realized that this method was only suitable for an US device, such as AT&T, T-Mobile, or Verizon (couldn't find a Rogers .TOT). I didn't modify the phone in any way.
I then continued to download the Rogers KDZ file here. Using the method described in the same post above, I performed the upgrade, only to realize that this was method wasn't working either.
I then did some scouring to find a way to boot into TWRP (which was already installed). I found this trick: If you hold the power button down until the phone turns off, you can hold power and down until you see the LG symbol, and then depress and press them again immediately to get into TWRP!
In TWRP... I realized that the partitions were all messed up. It was showing 6GB internal, and countless errors were popping up. Another dead end. ADB was working, but I was unable to push anything.
I then realized I should attempt to flash updated partitions using fastboot. Using the cmd line in Windows, I erased and flashed partitions I downloaded here after putting the phone in fastboot mode.
This is where I did something stupid.
Instead of clicking and downloading on that site, I right-clicked "save-as" and downloaded 8kb corrupted partition files. I continued and flashed them unknowingly... and right after, the phone decided to not boot at all.
Using VMWARE and Ubuntu 14.04, I attempted to reflash the partitions using Linux commands described here. Unfortunately, the device would not show the /sd* partitions. Certainly, the bootloader that communicates with the PC does not allocate the partitions properly anymore.
Alright, the phone wont boot, because I flashed a bad bootloader. No biggie right? I would see the device as Qualcomm hs-usb qdloader 9008.
That's when I scoured for a new method to fix the partitions. I came across QPEST and eMMC Software App to get this device back alive.
I spent hours trying to find the right .hex and .mbn file on Chinese websites. I found 8974_msimage.mbn, MPRG8974.hex, flash.xml, rawprogram0.xml and patch0.xml. I had to create accounts of a bunch of sites to finally download the correct files.
Carefully using QPST, I was able to get the phone in Download Mode (Qualcomm download mode, not LG download mode), and pushed the instructions to the device.
... too bad. I thought I did everything right. The device times out in the process EVERYTIME.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The phone is officially dead, there isn't a way I know of to get it started (at least to fastboot again). It really pays off to check what you're flashing before you do it. The internet is full of crap.

BuffMcBigHuge said:
So after 20 hours of fiddling... I can safely say that this LG G2 D803 is completely done.
Given by a friend, the phone started off by booting straight to fastboot, and had download mode available after he flashed a ROM designed for a tablet.
I attempted the .TOT method described here, where I used LGTools. I then only realized that this method was only suitable for an US device, such as AT&T, T-Mobile, or Verizon (couldn't find a Rogers .TOT). I didn't modify the phone in any way.
I then continued to download the Rogers KDZ file here. Using the method described in the same post above, I performed the upgrade, only to realize that this was method wasn't working either.
I then did some scouring to find a way to boot into TWRP (which was already installed). I found this trick: If you hold the power button down until the phone turns off, you can hold power and down until you see the LG symbol, and then depress and press them again immediately to get into TWRP!
In TWRP... I realized that the partitions were all messed up. It was showing 6GB internal, and countless errors were popping up. Another dead end. ADB was working, but I was unable to push anything.
I then realized I should attempt to flash updated partitions using fastboot. Using the cmd line in Windows, I erased and flashed partitions I downloaded here after putting the phone in fastboot mode.
This is where I did something stupid.
Instead of clicking and downloading on that site, I right-clicked "save-as" and downloaded 8kb corrupted partition files. I continued and flashed them unknowingly... and right after, the phone decided to not boot at all.
Using VMWARE and Ubuntu 14.04, I attempted to reflash the partitions using Linux commands described here. Unfortunately, the device would not show the /sd* partitions. Certainly, the bootloader that communicates with the PC does not allocate the partitions properly anymore.
Alright, the phone wont boot, because I flashed a bad bootloader. No biggie right? I would see the device as Qualcomm hs-usb qdloader 9008.
That's when I scoured for a new method to fix the partitions. I came across QPEST and eMMC Software App to get this device back alive.
I spent hours trying to find the right .hex and .mbn file on Chinese websites. I found 8974_msimage.mbn, MPRG8974.hex, flash.xml, rawprogram0.xml and patch0.xml. I had to create accounts of a bunch of sites to finally download the correct files.
Carefully using QPST, I was able to get the phone in Download Mode (Qualcomm download mode, not LG download mode), and pushed the instructions to the device.
... too bad. I thought I did everything right. The device times out in the process EVERYTIME.
The phone is officially dead, there isn't a way I know of to get it started (at least to fastboot again). It really pays off to check what you're flashing before you do it. The internet is full of crap.
Click to expand...
Click to collapse
there is a lot of crap on the internet but when you start fastbooting or dding partitions without verifying the integrity of the stuff you downloaded you will eventually brick something. Perhaps this experience will goad you into checking md5 or sha1 before you go about flashing things.

DeathmonkeyGTX said:
there is a lot of crap on the internet but when you start fastbooting or dding partitions without verifying the integrity of the stuff you downloaded you will eventually brick something. Perhaps this experience will goad you into checking md5 or sha1 before you go about flashing things.
Click to expand...
Click to collapse
It's very rare that I ensure the md5 is correct. In this case, the file sizes were completely off (8kb rather than 512kb), which is more noticeable than the hash. You're absolutely right. I sent the phone to MobileTechVideos for a JTag repair. I'll post the results when I get it returned.

You made a valiant effort, good luck man.

My hat goes off to you, man. Is it under a warranty that covers accidental damage? A good smashy-smashy would cover your tracks and relieve your stress all at once

I tell you though - fine attempt. Made my day reading this. Never stop at no. Hope you get your phone fixed.
Onward.
Sent from my LG-D802 using XDA Premium HD app

1 LG G2 down
20 million+ units still in combat working the daily grind!

Now phone is dead so go to the warranty method.

BigBoyPL said:
Now phone is dead so go to the warranty method.
Click to expand...
Click to collapse
he did the RIGHT thing and sent it to be repaired at his cost. to do what you are implying is to be a thief.

xlr8me said:
1 LG G2 down
20 million+ units still in combat working the daily grind!
Click to expand...
Click to collapse
make it 2 lg g2 mine is dead too...
mine is back to life finally

Can you not use a fastboot cable and re flash the correct partition images from there. I used that method to recover a completely bricked Kindle fire recently.

ClawOfDoom said:
Can you not use a fastboot cable and re flash the correct partition images from there. I used that method to recover a completely bricked Kindle fire recently.
Click to expand...
Click to collapse
I think this are the cases when the warranty should be used. The phone is not on it's best condition, so that should take care of this.

Any updates on the repair? I have a bricked D801 too...

zPacKRat said:
he did the RIGHT thing and sent it to be repaired at his cost. to do what you are implying is to be a thief.
Click to expand...
Click to collapse
I respectfully disagree. everything described is software related. The hardware is still fine. At least from what I was reading. Which means the phone could be sent back, under warranty and repaired in probably under 5 minutes. It might get a dollars worth of new plastic on it. Repackaged up and sent off to somebody else to replace their broken phone. The losses on the replacement phone would be recouped almost instantly.
Sent from my VS980 4G using Tapatalk

Can you help me.
Dear BuffMcBigHuge!
I have a situation same you, Now my LG G2 L-01F - NTT DOCOMO total Dead, it show Qualcomm HS-USB QDLoader only.
I searched many forum, but havent find out these file.
Can you give me these file for me to try unbrick My G2.
My email: [email protected]
Many thanks you.

dm6939 said:
Dear BuffMcBigHuge!
I have a situation same you, Now my LG G2 L-01F - NTT DOCOMO total Dead, it show Qualcomm HS-USB QDLoader only.
I searched many forum, but havent find out these file.
Can you give me these file for me to try unbrick My G2.
My email: [email protected]
Many thanks you.
Click to expand...
Click to collapse
+1 = I have the same here...

So after sending the device to MobileTechVideos, I was able to get it fully repaired and back into working order! They converted it to a D801, and its back in full working order!
Highly recommended!

BuffMcBigHuge said:
So after sending the device to MobileTechVideos, I was able to get it fully repaired and back into working order! They converted it to a D801, and its back in full working order!
Highly recommended!
Click to expand...
Click to collapse
Fantastic news glad there are still teams that are dedicated to there work and know what they are doing
Danzano's happy place

Danzano said:
Fantastic news glad there are still teams that are dedicated to there work and know what they are doing
Danzano's happy place
Click to expand...
Click to collapse
Any more updates here ? looks like we need 2 important files specific to the G2 . The .hex and the mnb file to enable writing to eMMC.

zathus said:
I respectfully disagree. everything described is software related. The hardware is still fine. At least from what I was reading. Which means the phone could be sent back, under warranty and repaired in probably under 5 minutes. It might get a dollars worth of new plastic on it. Repackaged up and sent off to somebody else to replace their broken phone. The losses on the replacement phone would be recouped almost instantly.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
bc OP stated:
"Given by a friend, the phone started off by booting straight to fastboot, and had download mode available after he flashed a ROM designed for a tablet"
so when a device is broken, (whether it be hardware or software) by the user, that is not a manufacturer defect. That is misuse, nonwarranty. thats why the guy you responded to said "he did the RIGHT thing and sent it to be repaired at his cost. to do what you are implying is to be a thief." and i agree with him. I actually cringe when i see people on here brick their phones, then ask for ways to unroot so they can get it repaired under warranty. Manufacturers are going to continue to make it harder to gain root access bc im sure theyre tired of wasting time on people who broke their phones themselves, then want it repaired for free. sigh...

This means it's dying, right?

Had this N4 for years. Flashed countless times. No emmc faults. Rock-solid reliable, until now.
The past week, it started stalling badly or rebooting. Mostly stalling, 1 in 10 bringing a reboot. Just freezes randomly for a few seconds. No common denominator. Clean-flashed another ROM with the same effects. Freezing and occasionally rebooting. This means it's dying, right?

Hello.
I never had the "emmc_read" fault either, but I had the same problems as you.
When you clean flash, you only wipe /data /cache /system ... But some essentials partitions are untouched like /EFS.
Let suppose (as an example) that you have a corrupted block somewhere in /EFS (/dev/block/mmcblk...) Any ROM you'll use will read your IMEI, and if the corrupted block is there, any ROM you'll flash will try to read your IMEI, get stuck, and will result the same problem : reboot, hang, etc.
Now my 1 cent advice : Make a backup from your partitions using EFS Professional : https://forum.xda-developers.com/ga...ol-updated-09-06-14-efs-professional-t1308546
And also using TWRP (better be safe than sorry)
(You'll need a specific version of BusyBox for EFS Pro)
And then, try to simply flash a stock rom using Odin, but with .PIT file for your model : https://forum.xda-developers.com/no...te-4-pit-files-repartiton-f-g-c-t-w8-t3282641
Flash a 1 file rom + pit and select "nand erase", and then a 4 files roms using the .pit and select "nand erase".
The whole nand is not really erased, you'll still have flashmode and your EFS safe.
It will repartition your device.
It may relocate the corrupted block somewhere else on the 32Gb internal storage.
It has fixed the issue for me... Hope it will fix yours as well.
Good luck.

PasSlert said:
Flash a 1 file rom + pit and select "nand erase", and then a 4 files roms using the .pit and select "nand erase".
Good luck.
Click to expand...
Click to collapse
I'll try this! Thank you! One question. What does the second half of this mean?
First half, simple enough. Flash a ROM and PIT, with Nand Erase checked. Got it. What does "then a 4 files roms using the .pit" mean?
ETA: Did not work.
Odin: "FAIL! Re-Partition operation failed."
Phone in Download mode: "SECURE CHECK FAIL : PIT"

O's said:
I'll try this! Thank you! One question. What does the second half of this mean?
First half, simple enough. Flash a ROM and PIT, with Nand Erase checked. Got it. What does "then a 4 files roms using the .pit" mean?
ETA: Did not work.
Odin: "FAIL! Re-Partition operation failed."
Phone in Download mode: "SECURE CHECK FAIL : PIT"
Click to expand...
Click to collapse
An official ROM can come in 2 ways :
4 files (+pit) : BL, AP, CP, CSC
1 file (+pit) : HOME
If you had a problem while flashing 1 file ROM + PIT, then try 4 files + pit.
You can find everything you need here : https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
Your Odin screen should look like this while flashing the ROM :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You should be able to complete the "SECURE CHECK FAIL : PIT" using this method.
If not, you can still grab the PIT from your phone, but that's not the goal.
GL.

Thank you again! But I don't see a PIT file in the example image, or checks for Re-Partition and Nand Erase. What of those?
ETA: Thank you again, but I'm spending hours chasing dead links and bad leads. Do you have a working link to a 4-files ROM? That thread has only dead links for N910T files. A post says to use a program on a different thread to use phone info to find newest firmware on Samsung servers. Installed program. Won't read phone info. Thread suggests to install Qualcomm drivers. Installed. Program still won't read phone info. Inputting phone info manually requires specs I can only find with Phone INFO app from Play Store. That requires a working ROM. I somehow flashed MagMa even though TWRP said it couldn't mount anything. (Still doing stall/reboot issue.) Logged into Play Store, downloaded Phone INFO. Entered info from app. Firmware program kept saying "Could not send BinaryInform. Status code 200/401."
Edit 2: I found the EQI2 BL and CP. Still need the CSC. Got a stock EQI2 .tar. Got Odin 3.09 per screenshot (was on 3.13.3). Tried to flash with those 3 + PIT. Still "Re-Partition operation failed." It just immediately rejects the PIT file every time. Losing hope here. Can't even flash stock, let alone check the stall issue.
Edit 3: Progress! Tried 3 different N910T PIT files before one worked. Odin PASS! with BL/CP/AP/PIT (no CSC). Initial boot now.
Edit 5,000: Worse than before.
At first, it seemed great. Stock booted OK, randomly rebooted once, and then seemed fine. I stress-tested it with all the usual steps that froze it up before on N7 port ROMs, and stock did fine. So I thought it moved a bad sector as you said. Clean-flashed a reliable favorite N7 ROM, and it turned off during the flash. Tried again, and it flashed but didn't reach ROM boot animation; Samsung logo then black for a half-hour. Pulled the battery, tried to reboot, same thing: Samsung logo then endless black. Attempted to restore an old backup to see if still acted up in regular use. Didn't even get there: Stayed on the gears "Android is starting" screen a half-hour. Wiped cache/dalvik, same outcome. Not sure what to do with it at all now.
Thinking it's time to put this phone out to pasture, unless you have other observations or ideas. Thank you again for the help.

Hello,
So you've flashed stock ROM.
If repartition succeded it went into bootloop on Stock ROM, if you did not went into bootloop : repartition didn't work.
(Bootloop can be 'fixed' by entering stock recovery and wipe data/factory reset.)
If flashing stock succeeded, you had to re-flash TWRP 3.3.1 using Odin : https://forum.xda-developers.com/note-4/snapdragon-dev/recovery-twrp-3-3-1-0-t3933427
(1) From TWRP, you can select wipe (top right) a select every partition (make backup of your internal memory) but don't select sdcard and OTG.
Then reboot > recovery.
Then install > zip > your note 7 ROM, but check md5 value because your N910T turning off while flashing is a problem.
The 'kernel' from TWRP doesn't handle temp really well, sometimes the phone can become really hot... Or the flashing tried to use the bad sector again. And as it's randomly moved while repartitionning, there's not a lot of solution : flash stock rom 4 files with pit.
To isolate the problem, I suggest you to let your phone be cool before flashing N7 ROM. If while cold, the flash of the same N7 ROM (assuming md5 is correct) makes the phone turn off, then I'd say bad sector.
Edit : beside phone turning off while flashing, being stuck on 'android is starting' could be solved by a factory reset from TWRP (wipe > swipe to factory reset) after a flash of custom ROM. It's sometimes recommended. Mainly if you get stuck on optimising android.
Also Odin version doesn't matter, some says 3.07 is better for a specific android version, 3.09 is better for others (source https://www.**********.com/odin-version-samsung-device-compatibility-list/) ... Use at least 2 different ones, just to be sure to eliminate every possibility. Same for 4 files rom, try to find a 4.4.4. and a 5.0.1 for example. You never know.
If you have hard times finding on xda, google give a lot of 4 files rom while searching for "4 files n910t".
Edit2 : you had a hard time with Qualcomm drivers because your phone is not bricked. As long as you have a working flashmode to communicate with your phone using Odin : you don't need Qualcomm drivers. This driver is only when your download mode is not even accessible, and the APQ8084 is the only way to communicate with your device.
Edit3 : sometimes, a pit file can be inside the CSC file. You can open the CSC.tar.md5 using 7zip or WinRar. Try to "4 files + pit" method, and if doesn't work the "within the CSC.tar.md5 pit file" method, in both cases repartition should be checked in Odin tool.
Hope you'll fix it.

PasSlert said:
Hello,
So you've flashed stock ROM.
Click to expand...
Click to collapse
Hello,
Wiped everything but sdcard and OTG x3. N7 ROM installed successfully this time, but the phone turned off by itself while I let it sit at the Welcome screen.
Thank you again.
ETA: I used a different battery that time just to rule that out, too.

I also started having this issue where phone will reboot while in use.
I did used this emmc bug app and it said I am fine
One thing i noticed when my phone would reboot is that the middle right side of screen was warm
When it does reboot like that , it goes into bootloop.... Right after Samsung logo.
The only way to get out of bootloop was to take the battery out and let the phone cool down. After that the phone boots successfully without any issue.
So I am assuming that warming up of phone somehow loosens flash chip solder point leading to reboots and bootloop. Cuz if phone can reboot fine on cooling down maybe that bad solder point would hardens just enough for good connections to be made with motherboard... Just my theory that's it's due to poor quality control or chip balling.
However the last time it happened, I couldn't boot my phone no matter what. So had to flash stock firmware ( 1 file method) but as OP mentioned the phone got into bootloop at welcome screen.. Again i noticed that phone was warm at right top/ middle point of screen.
What I did was to take back cover off and put the phone screen down on cold floor or marble counter top to let the heat dissipate. Only then the phone boots fine.
Maybe try that or get the motherboard changed ( with one with good emmc chip)

It's a wakelock.....not mmc

trinilu27 said:
It's a wakelock.....not mmc
Click to expand...
Click to collapse
Sorry?

Search XDA article is on here somewhere you have to go to the Play Store and download a certain wakelock detector... it magically fixes the phone and I'm not even kidding... I've owned probably 30 no fours and all of them I thought emmc was crashing and I follow the instructions in the article and it worked every time

trinilu27 said:
Search XDA article is on here somewhere you have to go to the Play Store and download a certain wakelock detector... it magically fixes the phone and I'm not even kidding... I've owned probably 30 no fours and all of them I thought emmc was crashing and I follow the instructions in the article and it worked every time
Click to expand...
Click to collapse
That's app keeps the cpu and memory engaged hence the name wake lock
And yes it works with some minor battery drain
But let the phone get hot/very warm from use and it will crash nonetheless with or without this app.
Even those who have custom kernel and have changed the governors and such still experience this problem... Meaning it's hardware level issue
And this wake lock app is like a bandaid to that problem

eMMc problems are not that bad. I had it, ordered a board from Alibaba for ~$25, installed it, and all was well again.

ghostwheel said:
eMMc problems are not that bad. I had it, ordered a board from Alibaba for ~$25, installed it, and all was well again.
Click to expand...
Click to collapse
What garentee you have that the said board will be good?

fizzingbees said:
What garentee you have that the said board will be good?
Click to expand...
Click to collapse
None.
Mine was good, and several years later, still working.

O's said:
Had this N4 for years. Flashed countless times. No emmc faults. Rock-solid reliable, until now.
The past week, it started stalling badly or rebooting. Mostly stalling, 1 in 10 bringing a reboot. Just freezes randomly for a few seconds. No common denominator. Clean-flashed another ROM with the same effects. Freezing and occasionally rebooting. This means it's dying, right?
Click to expand...
Click to collapse
There is a way to see if it is a emmc fail.
Start up the device to the bootloader (home + start + volume down, then volume up), and in the upper left side of the screen there are some system messages. If emmc chip is faulty there will be corresponding message there (se Picture, second row. Altho i can't remember android logo looking like that.. LOL).
Certain faults i have personally experienced gave exactly the same symtoms like a busted emmc chip:
A bad battery - but you say that you already tried replacing it?
Firmware - i went back to original stock from sammobile and that solved it.
There are some fixes for the bad emmc chip, but in my experience they are all temporary. The only thing that worked permanently was to replace motherboard. I ordered from aliexpress, didn't choose the cheapest nor the most expensive ones. A bit tricky, but doable. I replaced a few so far, they all worked and are holding on almost a year after.

prkfsz said:
There is a way to see if it is a emmc fail.
Start up the device to the bootloader (home + start + volume down, then volume up), and in the upper left side of the screen there are some system messages. If emmc chip is faulty there will be corresponding message there (se Picture, second row. Altho i can't remember android logo looking like that.. LOL).
Certain faults i have personally experienced gave exactly the same symtoms like a busted emmc chip:
A bad battery - but you say that you already tried replacing it?
Firmware - i went back to original stock from sammobile and that solved it.
There are some fixes for the bad emmc chip, but in my experience they are all temporary. The only thing that worked permanently was to replace motherboard. I ordered from aliexpress, didn't choose the cheapest nor the most expensive ones. A bit tricky, but doable. I replaced a few so far, they all worked and are holding on almost a year after.
Click to expand...
Click to collapse
Would you consider sharing the link.
I have snapdragon varient.
Regarding this error mmc_read fail... This only appears when emmc chip is beyond use.
If e.g you have a loose solder that cause transient problems, then this message wouldn't appear.
If it does that means your chips is goner or going to be goner soon.
The signs of emmmc chip fail should be recognized at the earliest and data backup up along with replacing motherboard when wallet and time allows