Database Develop

How to Flash F/W after bricking my phone

Hello,
Well i'm new here and i had a little problem with my new Samsung Galaxy S i9000. Today i wanted to flash my phone but after the first time my 3G connection wouldn't work. So after that i did a second try but this time something went wrong and i pulled the cable of the phone (i know u shouldn't do that!). Now when i start up my phone it shows a picture that i need to connect my phone to my computer. But when i do that trying to reflash it, it takes ages and nothing happens, Odins shows only these Command lines and nothing more even after 15 minutes:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
Click to expand...
Click to collapse
I tried al kind things like these follow:
20.WHAAAA! I think I bricked my phone. My flash was unsuccessful/My device boots to a black screen/similar scenarios. Can I still save my device?
Most likely: YES! In almost any case, you should still be able to turn off the device (if necessary by removing the battery) and start into download-mode (VolumeDown+Home+Power) or recovery-mode (VolumeUp+Home+Power). After (for example) an unsuccessful flash, you can retry the flash in download-mode (same steps as when flashing a functioning device). If a flash to a function f/w (without apply any update.zip) doesn't help or you cannot get you PC to flash at all, you can ask for help here. (Please try to reboot your PC as well if you cannot flash and try FAQ8 if you have trouble with getting the phone recognized on Windows 7/Vista x64)
If you see a symbol asking you to connect to the PC, depending on how you arrived at this point, it may be sufficient to connect to the PC and run Odin (i.e. press "start" when the phone is recognized) without adding any files. This may, however, leave some residual issues if (for example) had an incorrect/incomplete flash so you may want to do a normal flash after this!
Click to expand...
Click to collapse
But still nothing works, but though i still can get the phone into download mode, Recovery mode (VolumeUp+Home+Power let me show the sign that i need my phone connect to the Pc).
Please help me i really could use some help with this!

http://forum.xda-developers.com/showthread.php?t=723596

Wait, what? So you're saying that the first time you flashed, everything worked but you forgot to put the correct APN settings from settings menu to enable 3G. If so,

it's hard to brick the phone.
I tried repartition the storage, while flash an small flash file, so in theory, a "clean" partition of storage w/o any kernel and what not, and I could still flash the f/w.
that said, when it happens to me (when it's an empty partition), the phone will appear not to be boot up, and then you may find yourself not being able to go into download mode. chances are, the phone might appear to be power off, but its probably in a panic mode at the previous boot up, so there's no way you can change to download mode.
just take out the battery, leave it for 30s-1min, and then put battery back and then do the volumne down + home button + power button to bring the phone into the download mode.

RTFFAQFFS!

I managed to get my SGS back to life after taken my battery out for like 2 minutes or more...
I'm flashing atm and still working great!
Now i need only make shore that my modem (3g connection) will work, last time i couldn't set my settings back for APN.
But still a question here,
Does anybody knows the best working firmware for europe, The Netherlands?
Thanks for the help Guys!!! i really do!

buddy01 said:
Wait, what? So you're saying that the first time you flashed, everything worked but you forgot to put the correct APN settings from settings menu to enable 3G. If so,
Click to expand...
Click to collapse
Haha indeed... just fill in the APN settings hahaha

[Q] keep rebooting and no recovery mode

Purchased two Bell Canada Samsung Galaxy S as-is from local kijiji.
They all performing the same thing, rebooting at Galaxy S logo, GT-I9000M page, it won't go any further. and there is no recovery mode at start-up.
Here are the steps which I have played with for past two days.
1. Trying to get to recovery mode
- tried ADB, but it doesn't work, since "USB debug" is not on, and it won't accept as a device, and I am not able to turn that on, since I can't even get on the main screen.
- tried three key combo, vol up + home + power on, at least a hundred times for past two days, it doesn't work. fortunately download mode is working (at least I have more option to try). and I know how to get to recovery mode, I played with my friend's before.
2. Trying to use ODIN to flash the firmware
- unchecked "re-partition", unchecked "bootloader", pick 512 as PIT and then choose following as PDA
JH2, JK3, JK4, JL2
always successful on refresh, but phone still does the same, stuck at LOGO page
- also tried, checked "re-partition", and checked "bootloader", pick 512 as PIT and repacking following into PDA, Phone/Modem, CSC, still won't work...
JP series, JH, JK series, JL
At the beginning I though it was problem on CSC, I didn't use correct one to match my phone model #, but what's mine??? I can't go into my phone to check. I checked my friend's I9000, he used I9000BMCJK4, and I assume all JK series should work with me, since our IMEI are similar. And I tried many times on different cache.rft as CSC.tar, still no luck for me
I go crazy now, $400 USD gone. Seriously needing help. Any help is highly appreciated.

try the one jl2 download file and samsungfirmwares.com it flashes a special bootloader that may fix things.. it should be a single file you put in as pda nothing else..
if not they may have permantely trashed internal memory and you are sol.

lgkahn said:
try the one jl2 download file and samsungfirmwares.com it flashes a special bootloader that may fix things.. it should be a single file you put in as pda nothing else..
if not they may have permantely trashed internal memory and you are sol.
Click to expand...
Click to collapse
I have tried one of JL2 file from somewhere (don't remember where), but I will get one JL2 file from samsungfirmwares.com again, see if that works.
Do you mean, only choose the file for PDA, left PIT empty, and get everything uncheck?
permantely trashed internal memory? are these the common problem with this model? I got two of these, and both of them have the same issue, I think, there should be a way to slove it, right? Should I give up these thoughts???
anyways, thanks anyways, I will report back after I flesh JL2 from samsungfirmwares.com

Ok, you need to flash jl2 with pda, repartition, pit file and the secondary boot loader... The SBL(secondary boot loader) is what will actually fix your phone
Hopefully it will work.
Sent from my GT-I9000m using XDA App

<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.rfs
<ID:0/005> Sbl.bin
<ID:0/005> zImage
<ID:0/005> factoryfs.rfs
<ID:0/005> modem.bin
<ID:0/005> param.lfs
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Still no luck on this firmware, I9000UGJL2, by the way, should be samfirmware.com instead of samsungfirmwares.com
above message I got from ODIN3 v1.30, it looks fine for refresh, but it doesn't work. the phone keep rebooting, it won't pass LOGO page, again, only download mode I can use.
HELP! HELP! HELP!
any leads???

is "<ID:0/005> Sbl.bin" secondary boot loader???
I got the file for PDA, I9000UGJL2, is this the one? if not, where should I get it? how do I update it?
I did it again, with "re-partition" checked, PIT choosed as s1_odin_20100512.pit, I9000UGJL2_homebinary_add_param.tar (which I just downloaded from samfirmware.com), it still doesn't work.
anything else I can try? maybe something simple I didn't do???

I too am a bell user I had the same problem a few weeks back. This is going to sound messed up, but i'm going to do my best to explain how I solved the problem.
DO NOT MULTI-TASK ON THE COMPUTER WHILE DOING THIS. CLOSE ALL OTHER APPLICATIONS.
-remove external sd and sim card
-go into download mode (hold vol down+power+home).
-turn on ODIN
-plug in usb (both computer and phone)
-check re-partition
-ONLY use the 512 pit file. DO NOT use a rom.
-start ODIN and it should only take a minute. this will wipe your device completely but still allow you to access download mode.
- remove usb close ODIN
- start up ODIN again and connect usb
- use 512 pit and JP1 or JP2 rom.
- After flashing, this SHOULD give you an error and send you straight into recovery mode. you're looking for a specific error code. you need the error to have "sl01" or "sl10" (whichever, i forgot which it was) at the end of the path. if the end of the path has "m(something)" then use a different rom till you get the "sl10".
these errors are internal sd errors which your phone is experiencing right now, but the phone is fixable from the "sl10" error.
continuing...
- once you get the "sl10" error, close ODIN, unplug USB, turn off phone.
- go back into download mode.
- boot up ODIN with 512 pit and ULG2 rom.
- plug in phone
- start flashing.
this can give you two outcomes:
1) fixed galaxy S
2) error code with "m(something)" at the end of the error path.
if it's #2 do this all over again until it works.
This took me 3 days to figure out these steps, 10 hours each day. although it doesnt seem to make sense, my phone is working right now and it is where I am writing all this from. My only explanation is that Bell gets ****ty product from samsung. it's almost impossible to flash custom roms on a bell galaxy i9000 because the internal SD seems to have trouble being mounted.
i hope this helps and i hope it doesnt take long for you to fix this problem.
btw, if it does get fixed data connection wont be available. to enable it go to your apn settings. create new named "Bell" with apn as "pda.bell.ca" and leave all other options blank. data should be restored after that.
Sent from my GT-I9000M using XDA Premium App

jt_kyle said:
I too am a bell user I had the same problem a few weeks back. This is going to sound messed up, but i'm going to do my best to explain how I solved the problem.
DO NOT MULTI-TASK ON THE COMPUTER WHILE DOING THIS. CLOSE ALL OTHER APPLICATIONS.
-remove external sd and sim card
-go into download mode (hold vol down+power+home).
-turn on ODIN
-plug in usb (both computer and phone)
-check re-partition
-ONLY use the 512 pit file. DO NOT use a rom.
-start ODIN and it should only take a minute. this will wipe your device completely but still allow you to access download mode.
- remove usb close ODIN
- start up ODIN again and connect usb
- use 512 pit and JP1 or JP2 rom.
- After flashing, this SHOULD give you an error and send you straight into recovery mode. you're looking for a specific error code. you need the error to have "sl01" or "sl10" (whichever, i forgot which it was) at the end of the path. if the end of the path has "m(something)" then use a different rom till you get the "sl10".
these errors are internal sd errors which your phone is experiencing right now, but the phone is fixable from the "sl10" error.
continuing...
- once you get the "sl10" error, close ODIN, unplug USB, turn off phone.
- go back into download mode.
- boot up ODIN with 512 pit and ULG2 rom.
- plug in phone
- start flashing.
this can give you two outcomes:
1) fixed galaxy S
2) error code with "m(something)" at the end of the error path.
if it's #2 do this all over again until it works.
This took me 3 days to figure out these steps, 10 hours each day. although it doesnt seem to make sense, my phone is working right now and it is where I am writing all this from. My only explanation is that Bell gets ****ty product from samsung. it's almost impossible to flash custom roms on a bell galaxy i9000 because the internal SD seems to have trouble being mounted.
i hope this helps and i hope it doesnt take long for you to fix this problem.
btw, if it does get fixed data connection wont be available. to enable it go to your apn settings. create new named "Bell" with apn as "pda.bell.ca" and leave all other options blank. data should be restored after that.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
great!!! Another option I can try. Thank you.
I will try it out right after my work. so the idea behind this, is bricking it into recovery mode and S10 error code. and then fresh right back with correct ULG2 (is this correct? frist time heard about this rom)
anyways, I will post back with result.

Where can i find this ULG2 rom?

did it work?

Thananjeyen said:
Where can i find this ULG2 rom?
Click to expand...
Click to collapse
I think jt_kyle meant I9000UGJL2
and you can get them from samfirmware.com

Paallikko said:
did it work?
Click to expand...
Click to collapse
yes, lucky I got one of my Bell Samsung phone work. Since I done a million times of refreshing and rebooting and etc... I am not sure what I did, now I still trying to remember last 10 steps I did to make this work.
But definitely, I could not have done this repair without jt_kyle. Thank you so much, jt_kyle.

jt_kyle, Thank you!!!
but none of JP1 or JP2 is givining me the error "tl10", I tried
I9000DXJP1
I9000TGYZSJP2
I9000XXJP1
I9000XXJP2
it come out error started with "m..."
I just keep refreshing each on PDA 3 to 4 times, and choose with re-partition or without. At the end I try a few another ROMs as well, I still get no "tl10", but somehow, just that magicical moment, the screen come out a set of commands that look like format sd card, so I got excited, fresh it with JL2. It is back to work.
still no clue the steps of fixing the problem.
one done, the another one to go.
any more ideas please, and I think I am really close to solve this one now.
Thank you All

FIX
Look for a file called I9000UGJL2Complete follow the same steps pit and so on after your phone boots up youll have a blank baseband then you get the I9000UGJL2 modem and flash it where it says phone this has unbricked a few for me hope this helps

EVERED78 said:
Look for a file called I9000UGJL2Complete follow the same steps pit and so on after your phone boots up youll have a blank baseband then you get the I9000UGJL2 modem and flash it where it says phone this has unbricked a few for me hope this helps
Click to expand...
Click to collapse
if you have a way for me to give you this file i do have it just not sure how to do so because its 286MB

Could it be dead?
Since you have one of the infamous i9000m's it might also just be a dead SD card? You might try calling samsung and trying to get it repaired under warrenty as they are all under a year old (try and flash jl2 first even it will not boot up). It sounds like no receipt may not be an issue.
Lots of info from allgamer's list of i9000m issues in the general section.
At least you have one in the meantime!

same problem
Hey ive got pretty much the same problem that you had. Only differences are that I'm from Australia and am on Virgin network.
My phone became semi bricked one day when it restarted and since the 3 button combinations did not work i ordered in a USB jig which i received today. I used odin 1.8 to try and flash to I9000BVJJPD which i got from samfirmware.com but it ended up stuck on the logo screen vibrating once in a while. I decided to repeat it with no avail and began to use other roms and use .PIT.
This is where my phone became even worse and is now in it's current position; rebooting at the GT-I9000 page. I tried the method that jt_kyle suggested, substituting australian roms instead but it is still in the same position.
Does anyone have any other suggestions or should i just try getting a warranty?

Look for the ugjl2 complette and repeat what I said
Sent from my GT-I9000 using XDA Premium App

EVERED78 said:
if you have a way for me to give you this file i do have it just not sure how to do so because its 286MB
Click to expand...
Click to collapse
I think I have this I9000M_JL2_JL2_JL2_JL2_UG_BMC file, is the same file that you are talking about? JL2 Complete?
I tried this file many times, it won't work neither.

for past one hour I played around this phone, trying to repeat the steps I did for the first phone. Unfortunately, nothing is working for me AGAIN!
but I got these error page all the time, like following...
update media, please wait
E:Can't mount /dev/block/mmcblk0p1
(I/O error)
E:copy_dbdata_media:Can't mount SDCARD:
I think that's bigest problem in my case, and for a lot of people in this forum. Do any people has a good solution for this???

[Q] Bricked Verizon tab, black screen of death after trying to flash stock firmware

Well, I've bricked my three week old Verizon galaxy tab trying to flash the stock firmware back to the device to try and get the recent Verizon update working, which has been failing consistently. I've thoroughly read through every thread on the forum I could about the black screen of death, so I understand there's a good chance I'm pretty screwed here. I have a couple more questions on the subject, but I understand that I might not be able to get answers for them past the information that's already available.
I'll start by describing my setup and how the flashing process went wrong. I was using the stock Verizon ROM with Boushh's Voodoo Plus kernel v3, converted to ext4 of course. After the recent Verizon update failed to install on my Tab I followed through all the suggestions on the CDMA VZW Tab update thread, downloaded the update zip, put it on the sdcard, ran from rescue manager, unrooted, reflashed stock, wiped data and cache, re-ran from rescue manager at first boot... nothing worked. Things went really wrong when I tried flashing the entire ROTO backup of the Verizon stock ROM. I had the bright idea of setting up Heimdall to flash every file of the backup it had a slot for, including the pit file, zImage in kernel and recovery, factoryfs, param.lfs, cache.rfs, dbdata.rfs, modem.bin, boot.bin in primary bootloader slot and sbl.bin in secondary bootloader slot. When I pressed the start button it grayed out and nothing was happening. I waited a few minutes and finally turned the tab off. When I turned it back on again and tried to put it in download mode, the phone -x- computer logo showed up which freaked me out as I've never seen it before. Still, the computer did recognize the tab as composite USB device and so, unwittingly, I tried flashing with heimdall again. The flash went along perfectly well, but when it was finished both heimdall and the tab just hung there. I waited a few more minutes and turned off the tab again. After that it never turned on again. My questions, based on what I've read about the black screen of death so far are these:
* I've seen it suggested that the tab be left to drain for days or weeks, but not many reports that this worked out in the end. My battery was at about 45% percent when this whole thing went down. Should I even bother waiting? My only alternative at this point is to send the thing to Samsung for repairs which breaks my heart. Verizon won't replace it as I've had it for over two weeks.
* Could a homemade USB jig help me in this situation? I have some soldering experience but I heard that it won't help if the screen won't turn on. Ideally I'd buy it online, but I couldn't find one for the Galaxy Tab on ebay.
That's it I guess, but any information you can offer pertaining to this problem would be appreciated. Thanks!

to be honest, i do not know why people think they can brick the tab.......the only way is to throw it from a building.
Just go to overcome forum and follow this (i 'bricked' my tab a 1000 times):
IF your Tab does not boot after flashing the kernel and hangs at the Samsung Galaxy Tab screen, you must follow the following procedure
1.Get a stock rom package (any of Rotohammer's firmwares will work)
2.Get P1_add_hidden.zip attached to this post and extract the P1_add_hidden.pit file
3.Using Odin 1.7, put stock rom (Roto-JME-Full-v4.tar for example) in PDA slot.
4.Put P1_add_hidden.pit in Pit slot
5.Check repartition box
6.Put Tab in download mode by holding Volume Down and Power, connect to the computer, and press start.
7.After this, the Tab will reboot normally. Shut it down and return to download mode.
you also get the link for the p1 file you need.......easy

This sounds like very useful information, thank you. I'll definitely do this if I can get the Tab to respond to anything I do, which I can't so far. It won't turn on regardless of what volume button I press or not press. I'm pretty sure I had it connected to the PC while trying to put it in download mode just to see if it would be recognized as USB device despite the screen not turning on, but I'll try again to make sure when I get home.
Edit: Yeah, no luck. Not recognized as a USB device, which makes sense seeing as the screen doesn't even turn on.

I am having the same issue... My daughter put my computer to sleep while I was flashing back to stock using heimdall. Any luck getting your Tab to power on?

nirslsk said:
I had the bright idea of setting up Heimdall to flash every file of the backup it had a slot for, including the pit file, zImage in kernel and recovery, factoryfs, param.lfs, cache.rfs, dbdata.rfs, modem.bin, boot.bin in primary bootloader slot and sbl.bin in secondary bootloader slot. When I pressed the start button it grayed out and nothing was happening. I waited a few minutes and finally turned the tab off. When I turned it back on again and tried to put it in download mode, the phone -x- computer logo showed up which freaked me out as I've never seen it before. Still, the computer did recognize the tab as composite USB device and so, unwittingly, I tried flashing with heimdall again. The flash went along perfectly well, but when it was finished both heimdall and the tab just hung there. I waited a few more minutes and turned off the tab again. After that it never turned on again. My questions, based on what I've read about the black screen of death so far are these:
Click to expand...
Click to collapse
same problem

If your tab is showing any sign of life then you are not bricked and just need to keep at it until you find a solution. When you have exhausted all other resources you can send it off to get it fixed. I ended up bricking my tab when a flash was interrupted to the point that there was no sign of life at all. I found someone here who could fix it for $50 and had it back within the week working as it should. I highly recommend his service as a last resort.
His screen name is connexion2005 and here is a link to his profile.
http://forum.xda-developers.com/member.php?u=1602851

Mmc read fail... please help

I'm getting the occasional mmc read fail when I turn on my phone... it goes straight into download mode... i have to remove the battery and turn it back on then it would work... is there any fix for that?
Sent from my SM-N910T using Tapatalk

Did you find a solution?
I was having the same issue. I flashed N910TUVU1COD6_N910TTMB1COD6_TMB then immediately got an OTA update and I havent seen the problem for like a week.

willyx said:
Did you find a solution?
I was having the same issue. I flashed N910TUVU1COD6_N910TTMB1COD6_TMB then immediately got an OTA update and I havent seen the problem for like a week.
Click to expand...
Click to collapse
Problem is back

I'm having the same issue. I'm going to reflash to stock KK then see if that works... we'll see...

HellsBells said:
I'm having the same issue. I'm going to reflash to stock KK then see if that works... we'll see...
Click to expand...
Click to collapse
Same problem.
did reflashing stock KK fix it?

People if you find a solution or not to a problem, please come back to thread and post solution so others can get help from your success.
This is how forums work.
Pp.

PanchoPlanet said:
People if you find a solution or not to a problem, please come back to thread and post solution so others can get help from your success.
This is how forums work.
Pp.
Click to expand...
Click to collapse
my gf's note 4 had the same problem with emmc error. I tried to flash the heck out of it in odin and failed numerous times. Passed once on odin but refused to boot into android. Flashed odin again and that was the last time... it refused to turn on at all. It did not charge when i plugged it in also. Dead. People have a lot of this problem apparently. Only solution is replacement. Luckly t-mobile was nice enough to replace her's as a one time courtesy even though my warranty was out months ago. Im just glad i pushed its death early and found out why she started having reboots after the lollipop 5.1.1 update. Good luck with yours.

Good info.
Pp.

I know I'm beating a dead horse/thread, but after playing with a phone that has this problem I'm thinking it's a power issue. Specifically, with the battery prongs. I had this problem and would sometimes have to wait 5-10 minutes for the phone to be responsive to rebooting after a battery pull. Sometimes it would boot to say mmc read fail, and other times it would boot without a problem. I found that pushing in the prongs a couple times with a coin our even sometimes with the battery corner would let it boot right away after I put the battery back in. Weird, and still a hardware issue that would require a new motherboard unless you're a solder-master, but it could be useful info for someone. Another symptom the phone has is that it wouldn't survive the reboot process very often, but a hot reboot worked every time. That was another thing that made me think it was a power issue.
Sent from my SM-N910T using XDA-Developers mobile app

Guys, I think I fixed my Note 4 by reflashing to stock DOK2. I did this before many times with a full reset, but this time I used a slightly different method and another cable.
Here were my symptoms-
1. mmc read fail most of the time - 80-90% on cold boots.
2. The Wakelock app had to be running at all times to hold a partial wakelock, or the phone would freeze when going into deep sleep.
3. Phone would not charge when powered-off.
4. Freeze on reboot. Only hot reboots worked.
5. Unable to power on without removing sd-card, sim, battery, and power drain (vol-up, vol-down, home button, power for 20-30 seconds)
I have not seen any of these symptoms since I reflashed the phone about 12 hrs ago. Shutdowns/restarts no longer causes the phone to freeze. Deep-sleep works.
These are the EXACT steps I took, and I really hope this helps someone out. Some steps/options may be unnecessary, but I'm not leaving anything out just in case. I spent way too much time troubleshooting this problem, and I gave up on the phone about a month ago. I was actually looking for mainboards to buy on ebay.
1. Start with a cold Note4. Remove everything from the phone and leave it alone for an hour. Mine was sitting on my desk for a month. I don't know if this helps or not.
2. Use a good cable. My original Note4 cable still worked, but I found out it was going bad by using the Ampere app on my Galaxy S5. My Galaxy S5 would only charge at 450ma using the Note4 cable, which is ridiculously slow. My Anker cable charged at 1800ma.
3. Download the DOK2 firmware and unzip it using the SamFirm program. (Model SM-N910T, Region TMB)
http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
4. Use Odin v3.10.7 to flash.
i. DESELECT Auto-Reboot, and SELECT Re-Partition. F.Reset Time can be left checked.
ii. Get the T-Mobile 910T Pit file and select it in Odin.
iii. Click on AP and select the firmware unzipped from Step 3.
iv. Flash away!
5. When Odin completes (hopefully successfully), wait about a minute or so.
6. Restart the phone and immediately go into stock recovery.
i. Hold down all buttons until the phone resets (vol-up, vol-down, home, power)
ii. Let go of the vol-down button and the phone will go into recovery.
7. Wait a couple minutes for recovery to do what it needs to do. The phone will restart automatically.
8. Wait for the phone to boot into Android, but don't bother going through the setup wizard. Skip as much as you can.
9. Do a factory reset from inside Android. Settings/General/Backup and reset/ Factory data reset.
10. Wait for the phone to boot into recovery and wipe all data. I noticed when the phone was in recovery that it installed some kind of system update before wiping data.
After these steps, hopefully you'll have a working bone-stock Note4!

mtran1977 said:
Guys, I think I fixed my Note 4 by reflashing to stock DOK2. I did this before many times with a full reset, but this time I used a slightly different method and another cable.
Here were my symptoms-
1. mmc read fail most of the time - 80-90% on cold boots.
2. The Wakelock app had to be running at all times to hold a partial wakelock, or the phone would freeze when going into deep sleep.
3. Phone would not charge when powered-off.
4. Freeze on reboot. Only hot reboots worked.
5. Unable to power on without removing sd-card, sim, battery, and power drain (vol-up, vol-down, home button, power for 20-30 seconds)
I have not seen any of these symptoms since I reflashed the phone about 12 hrs ago. Shutdowns/restarts no longer causes the phone to freeze. Deep-sleep works.
These are the EXACT steps I took, and I really hope this helps someone out. Some steps/options may be unnecessary, but I'm not leaving anything out just in case. I spent way too much time troubleshooting this problem, and I gave up on the phone about a month ago. I was actually looking for mainboards to buy on ebay.
1. Start with a cold Note4. Remove everything from the phone and leave it alone for an hour. Mine was sitting on my desk for a month. I don't know if this helps or not.
2. Use a good cable. My original Note4 cable still worked, but I found out it was going bad by using the Ampere app on my Galaxy S5. My Galaxy S5 would only charge at 450ma using the Note4 cable, which is ridiculously slow. My Anker cable charged at 1800ma.
3. Download the DOK2 firmware and unzip it using the SamFirm program. (Model SM-N910T, Region TMB)
http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
4. Use Odin v3.10.7 to flash.
i. DESELECT Auto-Reboot, and SELECT Re-Partition. F.Reset Time can be left checked.
ii. Get the T-Mobile 910T Pit file and select it in Odin.
iii. Click on AP and select the firmware unzipped from Step 3.
iv. Flash away!
5. When Odin completes (hopefully successfully), wait about a minute or so.
6. Restart the phone and immediately go into stock recovery.
i. Hold down all buttons until the phone resets (vol-up, vol-down, home, power)
ii. Let go of the vol-down button and the phone will go into recovery.
7. Wait a couple minutes for recovery to do what it needs to do. The phone will restart automatically.
8. Wait for the phone to boot into Android, but don't bother going through the setup wizard. Skip as much as you can.
9. Do a factory reset from inside Android. Settings/General/Backup and reset/ Factory data reset.
10. Wait for the phone to boot into recovery and wipe all data. I noticed when the phone was in recovery that it installed some kind of system update before wiping data.
After these steps, hopefully you'll have a working bone-stock Note4!
Click to expand...
Click to collapse
I have the same problem and if i try thing u said i got this msg :
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/014> Added!!
<ID:0/014> Odin engine v(ID:3.1100)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Set PIT file..
<ID:0/014> DO NOT TURN OFF TARGET!!
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> SingleDownload.
<ID:0/014> aboot.mbn
<ID:0/014> NAND Write Start!!
<ID:0/014> sbl1.mbn
<ID:0/014> rpm.mbn
<ID:0/014> tz.mbn
<ID:0/014> sdi.mbn
<ID:0/014> NON-HLOS.bin
<ID:0/014> boot.img
<ID:0/014> recovery.img
<ID:0/014> system.img.ext4
<ID:0/014> FAIL! (Write)
<ID:0/014>
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/014> Removed!!
Only thing i manage to do its to flash only pit ( works fine) flash recovery ( works fine) from recovery i can flash any !! But if i turn phone i have random resets, random turn off's, cant power on need to discharge!
Random freezes for like 10-15s, if i turn camera on camera is working fine but i cant use any batons like record take picture or even physical batons if i w8 15s then it can be used! Phone is trash now and cant fix it... any1 got some solution?

saky90 said:
any1 got some solution?
Click to expand...
Click to collapse
I believe you'll find that the only solution is to replace your motheboard. The emmc is dead. No fix for that. I went through it too, as have many others. It seems Note 4's did not have the best quality control.

Hmm... I Just had that happen to my 910t3 after flashing marshmellow. The kies message popped up saying there was an error with the firmware update and told me to use the emergency restore thing... I pulled my battery and flashed it from another source and everything went fine scared the cap out of me.

thanks...it work for me
mtran1977 said:
Guys, I think I fixed my Note 4 by reflashing to stock DOK2. I did this before many times with a full reset, but this time I used a slightly different method and another cable.
Here were my symptoms-
1. mmc read fail most of the time - 80-90% on cold boots.
2. The Wakelock app had to be running at all times to hold a partial wakelock, or the phone would freeze when going into deep sleep.
3. Phone would not charge when powered-off.
4. Freeze on reboot. Only hot reboots worked.
5. Unable to power on without removing sd-card, sim, battery, and power drain (vol-up, vol-down, home button, power for 20-30 seconds)
I have not seen any of these symptoms since I reflashed the phone about 12 hrs ago. Shutdowns/restarts no longer causes the phone to freeze. Deep-sleep works.
These are the EXACT steps I took, and I really hope this helps someone out. Some steps/options may be unnecessary, but I'm not leaving anything out just in case. I spent way too much time troubleshooting this problem, and I gave up on the phone about a month ago. I was actually looking for mainboards to buy on ebay.
1. Start with a cold Note4. Remove everything from the phone and leave it alone for an hour. Mine was sitting on my desk for a month. I don't know if this helps or not.
2. Use a good cable. My original Note4 cable still worked, but I found out it was going bad by using the Ampere app on my Galaxy S5. My Galaxy S5 would only charge at 450ma using the Note4 cable, which is ridiculously slow. My Anker cable charged at 1800ma.
3. Download the DOK2 firmware and unzip it using the SamFirm program. (Model SM-N910T, Region TMB)
http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
4. Use Odin v3.10.7 to flash.
i. DESELECT Auto-Reboot, and SELECT Re-Partition. F.Reset Time can be left checked.
ii. Get the T-Mobile 910T Pit file and select it in Odin.
iii. Click on AP and select the firmware unzipped from Step 3.
iv. Flash away!
5. When Odin completes (hopefully successfully), wait about a minute or so.
6. Restart the phone and immediately go into stock recovery.
i. Hold down all buttons until the phone resets (vol-up, vol-down, home, power)
ii. Let go of the vol-down button and the phone will go into recovery.
7. Wait a couple minutes for recovery to do what it needs to do. The phone will restart automatically.
8. Wait for the phone to boot into Android, but don't bother going through the setup wizard. Skip as much as you can.
9. Do a factory reset from inside Android. Settings/General/Backup and reset/ Factory data reset.
10. Wait for the phone to boot into recovery and wipe all data. I noticed when the phone was in recovery that it installed some kind of system update before wiping data.
After these steps, hopefully you'll have a working bone-stock Note4!
Click to expand...
Click to collapse
thanks a lot....
it work for me...

mtran1977 said:
Guys, I think I fixed my Note 4 by reflashing to stock DOK2. I did this before many times with a full reset, but this time I used a slightly different method and another cable.
Here were my symptoms-
1. mmc read fail most of the time - 80-90% on cold boots.
2. The Wakelock app had to be running at all times to hold a partial wakelock, or the phone would freeze when going into deep sleep.
3. Phone would not charge when powered-off.
4. Freeze on reboot. Only hot reboots worked.
5. Unable to power on without removing sd-card, sim, battery, and power drain (vol-up, vol-down, home button, power for 20-30 seconds)
I have not seen any of these symptoms since I reflashed the phone about 12 hrs ago. Shutdowns/restarts no longer causes the phone to freeze. Deep-sleep works.
These are the EXACT steps I took, and I really hope this helps someone out. Some steps/options may be unnecessary, but I'm not leaving anything out just in case. I spent way too much time troubleshooting this problem, and I gave up on the phone about a month ago. I was actually looking for mainboards to buy on ebay.
1. Start with a cold Note4. Remove everything from the phone and leave it alone for an hour. Mine was sitting on my desk for a month. I don't know if this helps or not.
2. Use a good cable. My original Note4 cable still worked, but I found out it was going bad by using the Ampere app on my Galaxy S5. My Galaxy S5 would only charge at 450ma using the Note4 cable, which is ridiculously slow. My Anker cable charged at 1800ma.
3. Download the DOK2 firmware and unzip it using the SamFirm program. (Model SM-N910T, Region TMB)
http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
4. Use Odin v3.10.7 to flash.
i. DESELECT Auto-Reboot, and SELECT Re-Partition. F.Reset Time can be left checked.
ii. Get the T-Mobile 910T Pit file and select it in Odin.
iii. Click on AP and select the firmware unzipped from Step 3.
iv. Flash away!
5. When Odin completes (hopefully successfully), wait about a minute or so.
6. Restart the phone and immediately go into stock recovery.
i. Hold down all buttons until the phone resets (vol-up, vol-down, home, power)
ii. Let go of the vol-down button and the phone will go into recovery.
7. Wait a couple minutes for recovery to do what it needs to do. The phone will restart automatically.
8. Wait for the phone to boot into Android, but don't bother going through the setup wizard. Skip as much as you can.
9. Do a factory reset from inside Android. Settings/General/Backup and reset/ Factory data reset.
10. Wait for the phone to boot into recovery and wipe all data. I noticed when the phone was in recovery that it installed some kind of system update before wiping data.
After these steps, hopefully you'll have a working bone-stock Note4!
Click to expand...
Click to collapse
SamFirm will only get epg2?

[/COLOR]
Pinan said:
I believe you'll find that the only solution is to replace your motheboard. The emmc is dead. No fix for that. I went through it too, as have many others. It seems Note 4's did not have the best quality control.
Click to expand...
Click to collapse
Believe me...that's what i thought and everybody else until...i saw mtran1977 solution and try it myself. It's really working guys... it's definitely sofware issue not hardware. Cheers

<ID:0/014> system.img.ext4
<ID:0/014> FAIL! (Write) 1/3 of the bar than FAIL
<ID:0/014>
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/014> Removed!!
Sometimes stuck on
<ID:0/004> boot.img
<ID:0/014> FAIL! (Write)
Assuming it still have something to do with Emmc Chip or Power IC chip.
I will try to take it apart and reheat those chips tomorrow could be pins under the chip got disconnected after drops

monkeyass408 said:
my gf's note 4 had the same problem with emmc error. I tried to flash the heck out of it in odin and failed numerous times. Passed once on odin but refused to boot into android. Flashed odin again and that was the last time... it refused to turn on at all. It did not charge when i plugged it in also. Dead. People have a lot of this problem apparently. Only solution is replacement. Luckly t-mobile was nice enough to replace her's as a one time courtesy even though my warranty was out months ago. Im just glad i pushed its death early and found out why she started having reboots after the lollipop 5.1.1 update. Good luck with yours.
Click to expand...
Click to collapse
update: the same thing is happening with my note 4 now. Although it didnt fail completely like hers, it has reboots and extreme stutters. Tired going lollipop and MM. Nothing has work. I even tried to repartition my emmc. Same shiet. POS samsung has really poor quality. Its definitely a hardware issue. I think the mainboard is failing. Damn two note 4s down to crap. My family bought a total of 4. I hope my other family members' notes last. I highly doubt it. I loved these phones too and babied it. We bought it day one. All the model sm-n910t.
mtran1977 said:
Guys, I think I fixed my Note 4 by reflashing to stock DOK2. I did this before many times with a full reset, but this time I used a slightly different method and another cable.
Here were my symptoms-
1. mmc read fail most of the time - 80-90% on cold boots.
2. The Wakelock app had to be running at all times to hold a partial wakelock, or the phone would freeze when going into deep sleep.
3. Phone would not charge when powered-off.
4. Freeze on reboot. Only hot reboots worked.
5. Unable to power on without removing sd-card, sim, battery, and power drain (vol-up, vol-down, home button, power for 20-30 seconds)
I have not seen any of these symptoms since I reflashed the phone about 12 hrs ago. Shutdowns/restarts no longer causes the phone to freeze. Deep-sleep works.
These are the EXACT steps I took, and I really hope this helps someone out. Some steps/options may be unnecessary, but I'm not leaving anything out just in case. I spent way too much time troubleshooting this problem, and I gave up on the phone about a month ago. I was actually looking for mainboards to buy on ebay.
1. Start with a cold Note4. Remove everything from the phone and leave it alone for an hour. Mine was sitting on my desk for a month. I don't know if this helps or not.
2. Use a good cable. My original Note4 cable still worked, but I found out it was going bad by using the Ampere app on my Galaxy S5. My Galaxy S5 would only charge at 450ma using the Note4 cable, which is ridiculously slow. My Anker cable charged at 1800ma.
3. Download the DOK2 firmware and unzip it using the SamFirm program. (Model SM-N910T, Region TMB)
http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
4. Use Odin v3.10.7 to flash.
i. DESELECT Auto-Reboot, and SELECT Re-Partition. F.Reset Time can be left checked.
ii. Get the T-Mobile 910T Pit file and select it in Odin.
iii. Click on AP and select the firmware unzipped from Step 3.
iv. Flash away!
5. When Odin completes (hopefully successfully), wait about a minute or so.
6. Restart the phone and immediately go into stock recovery.
i. Hold down all buttons until the phone resets (vol-up, vol-down, home, power)
ii. Let go of the vol-down button and the phone will go into recovery.
7. Wait a couple minutes for recovery to do what it needs to do. The phone will restart automatically.
8. Wait for the phone to boot into Android, but don't bother going through the setup wizard. Skip as much as you can.
9. Do a factory reset from inside Android. Settings/General/Backup and reset/ Factory data reset.
10. Wait for the phone to boot into recovery and wipe all data. I noticed when the phone was in recovery that it installed some kind of system update before wiping data.
After these steps, hopefully you'll have a working bone-stock Note4!
Click to expand...
Click to collapse
i tried this. everything went though successfully but no change. Its a hardware issue.

monkeyass408 said:
update: the same thing is happening with my note 4 now. Although it didnt fail completely like hers, it has reboots and extreme stutters. Tired going lollipop and MM. Nothing has work. I even tried to repartition my emmc. Same shiet. POS samsung has really poor quality. Its definitely a hardware issue. I think the mainboard is failing. Damn two note 4s down to crap. My family bought a total of 4. I hope my other family members' notes last. I highly doubt it. I loved these phones too and babied it. We bought it day one. All the model sm-n910t.
i tried this. everything went though successfully but no change. Its a hardware issue.
Click to expand...
Click to collapse
Thanks for your follow-up. Did either of the phones ever get dropped? I'm wondering about the battery prong suggestion by 'upncoming' earlier in the thread.
I'm scheduled for a replacement next week for similar issues. This'll be my third Note 4, hopefully it'll last.

duh-rel said:
Thanks for your follow-up. Did either of the phones ever get dropped? I'm wondering about the battery prong suggestion by 'upncoming' earlier in the thread.
I'm scheduled for a replacement next week for similar issues. This'll be my third Note 4, hopefully it'll last.
Click to expand...
Click to collapse
mines- never dropped. hers- dropped many times. Both still pristine condition. As soon as i am able to get another phone im going to sell my replacement because its pointless to pay insurance for an old phone. I love the note 4 but two phone failing on me is not acceptable. I just dont know what to get now. Very little choice in phones with removable battery now a days. Going to miss that IR blaster too. LG v20 or V10 i suppose. BTW my gf and i share three batteries over the course of a year and some months. All three batteries deteriorated at and shuts down at 15-20%. Heavy users like my other two family member , the battery would die at 30-40%. So i am strongly against sealed batteries. It pisses me off that a 700-800 dollar device cannot even last 2 years.

Unusual Boot Loop - No Recovery, Odin Flash Appears to Succeed but Doesnt Fix Loop

Hello,
For the past few days I've been reading up on XDA and other forums to attempt to solve my boot loop issue. I'm hoping this forum can help me.
Hardware/Locale:
AT&T S6 Edge (USA)
Android 5.1.1, Stock
G925AUCU3BOJ7 firmware version
Issue:
At some point after completing a call using a paired Bluetooth device, the phone entered and remains stuck in a boot loop, exhibiting the following behaviors:
Phone powers on when plugged in to either phone or wall outlet
Upon power on, phone attempts to boot, getting as far as the Samsung Galaxy S6 Edge screen (NOT the Samsung logo screen)
After a few seconds, the phone reboots, and repeats the pattern
No LED lights activated on the phone; no "Blue" LED, or other colors, flash at any time
...with complications/other factors:
Cannot access Recovery - pressing the standard combination of buttons (Power-Home-VolumeUp) at any/all points in the process fails to start recovery; tested procedures on my spouse's identical S6 Edge with identical firmware, and was able to start Recovery
Cannot access Safe Mode - pressing the standard combination of buttons does not cause the phone to enter Safe Mode
EDIT:
Tried Kies - claims device is Unsupported.
EDIT:
Tried Smart Switch - claims device is Unsupported.
Fixes Attempted:
Discharge the phone completely and try again - No effect; problem remains
Charge the phone using a different wall charger, USB cable, or even laptop as power source - No effect; problem remains
Boot to Download Mode and flash G925AUCU3BOJ7 stock firmware obtained from XDA in combinations of 1) Just AP, 2) AP + BL, and 3) AP, BL, CP, and CSC - Appears to flash successfully, based on ODIN behavior, but No effect; problem remains
Boot to Download Mode and try previous versions of stock firmware for my device obtained from XDA - Same behavior as above
Were there not currently a blizzard raging outside my house, I'd drive over to the AT&T store and ask for help. But there's that whole blizzard thing. Not going anywhere.
Any ideas?

wmbutler said:
Hello,
For the past few days I've been reading up on XDA and other forums to attempt to solve my boot loop issue. I'm hoping this forum can help me.
Hardware/Locale:
AT&T S6 Edge (USA)
Android 5.1.1, Stock
G925AUCU3BOJ7 firmware version
Issue:
At some point after completing a call using a paired Bluetooth device, the phone entered and remains stuck in a boot loop, exhibiting the following behaviors:
Phone powers on when plugged in to either phone or wall outlet
Upon power on, phone attempts to boot, getting as far as the Samsung Galaxy S6 Edge screen (NOT the Samsung logo screen)
After a few seconds, the phone reboots, and repeats the pattern
No LED lights activated on the phone; no "Blue" LED, or other colors, flash at any time
...with complications/other factors:
Cannot access Recovery - pressing the standard combination of buttons (Power-Home-VolumeUp) at any/all points in the process fails to start recovery; tested procedures on my spouse's identical S6 Edge with identical firmware, and was able to start Recovery
Cannot access Safe Mode - pressing the standard combination of buttons does not cause the phone to enter Safe Mode
EDIT:
Tried Kies - claims device is Unsupported.
EDIT:
Tried Smart Switch - claims device is Unsupported.
Fixes Attempted:
Discharge the phone completely and try again - No effect; problem remains
Charge the phone using a different wall charger, USB cable, or even laptop as power source - No effect; problem remains
Boot to Download Mode and flash G925AUCU3BOJ7 stock firmware obtained from XDA in combinations of 1) Just AP, 2) AP + BL, and 3) AP, BL, CP, and CSC - Appears to flash successfully, based on ODIN behavior, but No effect; problem remains
Boot to Download Mode and try previous versions of stock firmware for my device obtained from XDA - Same behavior as above
Were there not currently a blizzard raging outside my house, I'd drive over to the AT&T store and ask for help. But there's that whole blizzard thing. Not going anywhere.
Any ideas?
Click to expand...
Click to collapse
Wish i Could Help..anyways found an article
http://thedroidguy.com/2015/09/gala...n-download-mode-other-charging-issues-1049588

Hi. Did you find the solution / explanation for this situation?

Same problem
facing the same problem, did you find any solution. please help me out.

same thing happened to mine on Jan 2. Phone did its usual all night charge (so was fully charged). I used it a little that morning to check facebook etc. Laid it down, that afternoon needed to make a phone call, hit the power button and now i'm in this loop. ATT was ZERO help. To add, i have red and black lines as my background (which is usually just black) when booting up. I have done all the things you have and phone continues to cycle. This phone has been an absolute piece of poo poo. The laminate started to peel off the front at one of the corners. I keep my phone in a case and don't drop it or haven't in a long time. The camera lens is cracked, so is my sons. You can't root it. Now this...i will never own another samsung product again. I moved back to my son's old htc one ( i gave mine away ...stoopid me). This morning it had a software update (it hasn't been on in 1.5 years) so I said yes. Now it won't boot. GRRR!!!! Keep us posted. I'll do same if I figure it out.
Edit: meant to add, my blue light stays on until eventual total power drain.

Same issue
Hi Guys,
I'm facing the same issue. I tried re-flashing different roms, odin says success but i'm stuck with bootloop. I can go into only download mode, no recovery, no hard reset. I visited the samsung service center and they said that they can't help since KNOX counter is tripped: 1 (0x0500) . Were you guys able to fix this issue. ?
If anyone has a solution please share it here.

stuck in bootloop also
I am having the same problems as you guys for the last 4 days, it doesn't go into recovery mode, only thing it does is go into ODIN mode ,I have also tried flashing the stock firmware through ODIN and it passes but it's still stuck in a boot loop. Please let me know if one of you guys fixed your phone.

its same here anybody can show a guide how to fix this or jtag needed ? or need to return service?

Hi
same problem for me...

same here tired many things and cannot boot nor in recovery

Facing the same issue with my s6 edge. No safe mode, no recovery, just download mode. Also did what everyone else did. Installed the latest ROM for it. Odin looked quite happy with itself for passing the download successfully, but in my case, the phone doesn't boot loop, it just stays on the S6 edge startup screen and doesn't budge until I unplug it. Doesn't appear that the battery is charging either, even though a new one was installed recently, so I am at a loss as to what needs to be done to fix this thing and apparently so is everyone else. Hope we get some answers soon!

Any update on this issue? I assume no other solution than replacing the motherboard has been found. This phone has been only trouble for me...

gunmoule said:
Any update on this issue? I assume no other solution than replacing the motherboard has been found. This phone has been only trouble for me...
Click to expand...
Click to collapse
Apparently not! I guess that seems to be where I'm headed too, but not until the prices of motherboards come down. On ebay I'm still seeing working mobos for around $100. In my opinion, that's way to much for a phone this old.

Viking8 said:
Facing the same issue with my s6 edge. No safe mode, no recovery, just download mode. Also did what everyone else did. Installed the latest ROM for it. Odin looked quite happy with itself for passing the download successfully, but in my case, the phone doesn't boot loop, it just stays on the S6 edge startup screen and doesn't budge until I unplug it. Doesn't appear that the battery is charging either, even though a new one was installed recently, so I am at a loss as to what needs to be done to fix this thing and apparently so is everyone else. Hope we get some answers soon!
Click to expand...
Click to collapse
I used Heimdall. Download any stock rom preferably the higher version from installed rom. Unpack all the DOT.tar.DOT.md5 get the full image at least : sboot.bin system.img recovery.img boot.img param.bin flash it on download mode:
Code:
$ heimdall flash --BOOTLOADER sboot.bin --PARAM param.bin --RECOVERY recovery.img --SYSTEM system.img --BOOT boot.img
if the room version is higher, flashing bootloader is mandatory, if the rom version at the same level bootloader not neccessary. Modem is not neccessary but optional can also flash.

x1123 said:
I used Heimdall. Download any stock rom preferably the higher version from installed rom. Unpack all the DOT.tar.DOT.md5 get the full image at least : sboot.bin system.img recovery.img boot.img param.bin flash it on download mode:
Code:
$ heimdall flash --BOOTLOADER sboot.bin --PARAM param.bin --RECOVERY recovery.img --SYSTEM system.img --BOOT boot.img
if the room version is higher, flashing bootloader is mandatory, if the rom version at the same level bootloader not neccessary. Modem is not neccessary but optional can also flash.
Click to expand...
Click to collapse
I tried through the GUI of Heimdall, but it never actually flashes anything. It says it's "Beginning Session....." waits for a couple minutes and then releases the device. The SM-G925T I have has these files in the tar file when unpacked.
boot.img
cache.img
cm.bin
modem.bin
recovery.img
sboot.bin
system.img
Could you show me what the syntax would look like in the CMD for these files?
Ex. $ heimdall flash --BOOTLOADER sboot.bin --RECOVERY recovery.img --SYSTEM system.img --BOOT boot.img etc. etc.
Clayton
NEW INFO:
I tried to flash just the recovery to see if it would install, but Heimdall in the cmd does the same thing as the GUI.
Initializing connection....
Detecting device....
Claiming interface....
Setting up interface....
Initializing protocol....
ERROR: Failed to send data! Releasing device interface....
MORE INFO: (About 30 minutes later)
I tried a different version of ODIN, (3.10) and I was able to successfully load G925TUVS6FRC1_G925TTMB6FRC1_G925TUVS6FRC1_HOME.tar, but it just sits at the Samsung Galaxy S6 Edge screen forever like it did before. Not sure what to do at this point. Any other suggestions would be welcomed!