Database Users

Phone not resonding whilst doing the Upgrade

Guys,
I'm in need of help fast.....
Just tried to do the Froyo Upgrade and have hit an almighty problem.
Kies downloaded and went to the next stage 'Upgrade'.
It got about 5% into doing this when the bar stopped moving and the phone switched off.
It's been like this now for over 30mins..... The phone won't power up (it's still connected to the PC).
HELPPPP.

Well you get my sympathy vote! But other then that I think you know yourself what to do. You've been around... Good luck!

Yes..... Bloody Phone, Bloody Kies, Bloody Samsung.
I unplugged the phone in the end and Kies offered to do a Firmware Recovery so I thought why not give it a try.
I went into Download mode, reconnected and Kies started the recovery procedure only for again the bar to stop moving again and it's stopped doing the recovery.
The screen on the phone remained a constant bright Yellow.
I unplugged it again and tried once more... It again stopped about a quarter way into the recovery only this time the screen has turned a constant Green.
Damn.................

The sad thing is that this reminds me so much of my sinclair zx81. 25 years later and we still have to deal with the same problems. Never sure the data gets from point A to point B.

Right.... Now I need to find the address for UK returns.
Don't have my warranty card info with me either so looks like I'll have to Google the returns.... but I'm busy as hell and have an Op to carry out soon.
If anyone comes up with it (or the link) I'll be grateful.
Bugger....

I'm probably teaching the teacher, but are you using the USB lead supplied with the phone? I tried to download some music using another lead and the download stopped halfway.
Sorry if this is too obvious.

Geryatrix said:
I'm probably teaching the teacher, but are you using the USB lead supplied with the phone? I tried to download some music using another lead and the download stopped halfway.
Sorry if this is too obvious.
Click to expand...
Click to collapse
No problem on the 'techer', any advise or assistance is better than nothing.
Yes, I used the cable supplied by Samsung... Nothing seems to sort this out.

As you are thinking of returning it, I conclude you can't get to any recovery/download mode. I don't know if Kies messed up the bootloader or keymappings but there is still the diy jig you might try. Also I have come across many devices in my day that needed repetitive flashing to get to the 100%. It would be bad if this was the case with a 2010 phone but hey its a Samsung.

sargasso said:
As you are thinking of returning it, I conclude you can't get to any recovery/download mode. I don't know if Kies messed up the bootloader or keymappings but there is still the diy jig you might try. Also I have come across many devices in my day that needed repetitive flashing to get to the 100%. It would be bad if this was the case with a 2010 phone but hey its a Samsung.
Click to expand...
Click to collapse
Well I've tried the Firmware Recovery at least a dozen time, each time it starts and stops at different parts.
I nearly got to three-quarters through when the bloody thing hung again.
No problem with the 3 Botton access and getting the Yellow Android Man on screen.. No problems connecting to Kies but as soon as you try the recovery it stops at some point during the process simply saying "An unexpected error has caused firmware upgrade to fail. Do you want to perform firmware recovery now?"....... and that came up whilst doing the firmware recovery.

Doesn't work to flash with odin either?

xExisioNx said:
Doesn't work to flash with odin either?
Click to expand...
Click to collapse
I don't want to use Odin if possible.
With that many different phones and ROMS available I don't want to end up screwing the phone totally.

Well Kies does not have a reputation to be very functional but there are two or three other tools to flash your phone. Although I am not a compulsive flasher, I did use Odin a couple of times. I am not sure exactly why you are having stage fright (referring to your other post on this matter).
Bringing it back to Eclair with a stock rom, using the rom, pit and instructions on http://www.samfirmware.com might help you to restore sanity. Once you are sure you haven't lost your phone you can then retry to use Kies.
The problem for you might be a partialy broken bootloader or incompatibility between the rom mappings and your phones current setup. Flashing a low rom might solve that. (As I understand from heimdall there are high and low packages, the low packages contain a bootloader and are more risky to flash since replacing the bootloader might truly brick your phone)
Also I read about people just flashing a pit file to force a repartition and format of the phone.
Make sure to get it fixed before op, I wouldn't want my doctor to worry about his phone, stiching me up with a pair of siccors stil in me ;D

Don't be scared of Odin. It has recovered my phone a million times
Really, the time and effort of getting a replacement when you can fix it in 2mins with odin in your own home... seems crazy.
You can flash a UK firmware if theres one available, or otherwise flash any firmware and update to UK firmware using kies reg hack, as far as i understand.

sargasso said:
Well Kies does not have a reputation to be very functional but there are two or three other tools to flash your phone. Although I am not a compulsive flasher, I did use Odin a couple of times. I am not sure exactly why you are having stage fright (referring to your other post on this matter).
Bringing it back to Eclair with a stock rom, using the rom, pit and instructions on http://www.samfirmware.com might help you to restore sanity. Once you are sure you haven't lost your phone you can then retry to use Kies.
The problem for you might be a partialy broken bootloader or incompatibility between the rom mappings and your phones current setup. Flashing a low rom might solve that. (As I understand from heimdall there are high and low packages, the low packages contain a bootloader and are more risky to flash since replacing the bootloader might truly brick your phone)
Also I read about people just flashing a pit file to force a repartition and format of the phone.
Make sure to get it fixed before op, I wouldn't want my doctor to worry about his phone, stiching me up with a pair of siccors stil in me ;D
Click to expand...
Click to collapse
Thanks... Need to find out now which is the right PIT to download.
I was on JF3.
God... if only I had more time on my hands.

Okay... got to go guys... Surgery to do.
I'll do the Odin later.
To save me time searching could someone please post below the relevant links I need to get Odin and the procedure....
Cheers.

When you flashed did you remove your sim card? I had that same problem with ki es. Removed the sim card and redid the flash and it continued on it's way.
How this helps.
Sent from my GT-I9000M

Well, if you have an account at samfirmware you can use this link http://www.samfirmware.com/WEBPROTECT-i9000.htm.
Make sure before you do anything to check your phone model is the one I linked to. Making a backup of your efs directory is not possible anymore but normally that should be done also. As a precaution I always remove my external sd card and sim card before flashing and - as you know - have the battery loaded to the max.
It might be an idea to skip jf3 and go to JM8 with a 512 pit and repartition on. This because it seems to be the recommended way of doing things at samfirmware as preparation for the flashing of current froyo releases.
I have never had problems with their way of doing things but opinions differ.
[EDIT]
I downloaded their JF3 package to see if there was a pit file included as there is some discussion what PIT file to use 512 vs 513. The package contains no information on that. It does however contain the word LOW in one of the filenames ...

Beards said:
Okay... got to go guys... Surgery to do.
I'll do the Odin later.
To save me time searching could someone please post below the relevant links I need to get Odin and the procedure....
Cheers.
Click to expand...
Click to collapse
I don't think you need to use a pit, odin should use the information from the phone assuming partitions remain intact. I've flashed a dozen times without one. If you do use one then use 512.
First off, get into recovery try and clear, reset what you can. Remove the sim and external SD as a precaution. Then back to download mode without the phone usb connected.
Grab the JPO firmware > http://www.multiupload.com/MX8XW7BG24
Grab odin 1.3 > http://www.megaupload.com/?d=MADK0XTB
Extract the firmware somewhere, open odin then select JPO_JPO_U_JPP.tar as PDA. Leave everything un-ticked except reboot. Plug the phone into your PC make sure Kies is not running and the battery is charged. In odin you should see a yellow window under ID:COM with a COM port open. If you do hit start, if all goes well a green bar will move across until the phone reboots. Leave it to do its thing at the big S (I usually unplug USB by now, to avoid problems) wait upto 10mins first time. If it hangs try a reset and cache clear and reformat SD. That's all I do, worked with all the firmwares I've downloaded from Samsung's FUD server.
The PIT files are templates for partition information so Odin can manage the size of the internal device partitions. Your standard device should already be on 512 layout, the other PIT's were development hacks. Like I said you shouldn't really need to repartition, but if you do > http://www.multiupload.com/I5WICSBFJ1

Fornowagain said:
I don't think you need to use a pit, odin should use the information from the phone assuming partitions remain intact. I've flashed a dozen times without one. If you do use one then use 512.
First off, get into recovery try and clear, reset what you can. Remove the sim and external SD as a precaution. Then back to download mode without the phone usb connected.
Grab the JPO firmware > http://www.multiupload.com/MX8XW7BG24
Grab odin 1.3 > http://www.megaupload.com/?d=MADK0XTB
Extract the firmware somewhere, open odin then select JPO_JPO_U_JPP.tar as PDA. Leave everything un-ticked except reboot. Plug the phone into your PC make sure Kies is not running and the battery is charged. In odin you should see a yellow window under ID:COM with a COM port open. If you do hit start, if all goes well a green bar will move across until the phone reboots. Leave it to do its thing at the big S (I usually unplug USB by now, to avoid problems) wait upto 10mins first time. If it hangs try a reset and cache clear and reformat SD. That's all I do, worked with all the firmwares I've downloaded from Samsung's FUD server.
The PIT files are templates for partition information so Odin can manage the size of the internal device partitions. Your standard device should already be on 512 layout, the other PIT's were development hacks. Like I said you shouldn't really need to repartition, but if you do > http://www.multiupload.com/I5WICSBFJ1
Click to expand...
Click to collapse
Surgery postponed until tonight so I have some free time.....
Okay, I got Odin 1.3 & JPO Firmware.
I loaded the JPO into Odin (in the PDA section).
Next I put the SGS into Download Mode and connected via USB and sure enough the ID:COM came up yellow with COM7 so I hit Start.
The green line went so far across under KERNAL but just as it was about to finish that box the SGS screen changed to a solid Blue screen and nothing further is happening in Odin.
Any advice??

Odd never seen that before, maybe your root problem. Should have rebooted automatically once the progress bar reached the end assuming you had the reboot option selected. Try a manual reboot, hold the power button down until it restarts. My next step would be the repartition and try again, load the PIT file (as PIT). Same flash procedure as before just using the 512 PIT, reset it all and try again.

Galaxy S will not boot past the "Galaxy S" screen on startup

Hi Everyone
my Galaxy S will not boot past the "Galaxy S" screen on startup. I have read several posts with the same problem and I have tried all suggestions that I have come across. Here is what I have tried so far:
Removed battery and sim card for several hours - no change
Went into recovery mode (volume up + power + home button). Received a "E:Can't mount /dev/block/mmcblkOp1 (No such file or directory)" and "E:copy_dbdata_media:Can't mount SDCARD: copy default media content failed." error messages.
In recovery mode, performed a "wipe data/factory reset" to restore the phone back to default - still no change
Do i need to send my phone back to Samsung or take it to a phone shop? or can it be sorted at home?
Brian

Did this just randomly start to occur? did you drop the phone? or did you try to flash another rom & thus got stuck on boot?
If not, have you tried going in to download mode? (volume down + power + home button)

Go into download mode and flash a new ROM including bootloader. You should also tick 'Re-Partition' in Odin and use a PIT-file.
Sent from my GT-I9000 using XDA Premium App

Lunchbox115 said:
Go into download mode and flash a new ROM including bootloader. You should also tick 'Re-Partition' in Odin and use a PIT-file.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
This would have of course been my next suggestion assuming he can get in dl mode

Try this.

J 3 M said:
Did this just randomly start to occur? did you drop the phone? or did you try to flash another rom & thus got stuck on boot?
If not, have you tried going in to download mode? (volume down + power + home button)
Click to expand...
Click to collapse
I have tried this and can get into the menu but no matter what option i said pick nothing works
Tbh i am not very good at all this lol
It happened because when i conected to Kies it said i need to update so i did and half way through the 2nd update 29% it crashed and now wont work
So the phone can be sorted?
Brian

jamesythfc said:
I have tried this and can get into the menu but no matter what option i said pick nothing works
Tbh i am not very good at all this lol
It happened because when i conected to Kies it said i need to update so i did and half way through the 2nd update 29% it crashed and now wont work
So the phone can be sorted?
Brian
Click to expand...
Click to collapse
Well if you can get into the dl menu your phone is just fine.
Did you read jcspecs posted link?
When you go into download mode it means your phone is ready to flash new software, roms etc, it requires the use of a simple program called Odin (3.1 being the usual preferred choice), from there you install selected roms into it's interface, you then plug in your phone (in download mode) & you let it do it's thing, all being well you'll reboot & your Galaxy S will be born again, only bigger, better, stronger & faster
Let me encourage you into a simple set up to get your phone up & running before you do anything else, once done you can then spend more time reading a lot of stuff just like most of the rest of us has had to do, once you read you'll will be in a better position to decide whether to stick with what works or whether to change, the key is finding what you can & can't do, what works for you etc, trust me you'll get the hang of it & it's well worth it!
I'm assuming your phone is Galaxy S I9000? READ CLICK--> THIS <--CLICK GUIDE THOROUGHLY!
Also take a look at THIS for I9000 models
The idea is to flash your phone back to stock firmware using the correct tools & to then flash over it with seriously better software to show you just what it can & should look & behave like, it'll also hopefully stop you from ever connecting to Kies again.... READ, READ, READ
Also watch the youtube videos by Totallydubbed provided in the links, they will seriously help you out.

simply, Brian, I want to introduce this method for you.
Make yourself understood what is ODIN flash. Please try to search this forum or do a google search. I suggest you use the offical 2.3.4 JVP rom.
ODIN to flash the room.
1st of all, make sure your phone model definitely I9000, no T959 or others.
2nd, don't connect the KIES, and in the settings-->application-->(click this) USB debugging.
3. Download the relevant files for flashing rom. Sorry, I have no link 4 U yet, but I hope it can help.

minishe said:
2nd, don't connect the KIES, and in the settings-->application-->(click this) USB debugging.
Click to expand...
Click to collapse
You should also close all Kies-processes (the one in the taskbar right at the bottom (Win7) too.
Sent from my GT-I9000 using XDA Premium App

Thanks for all the replies its all becoming a bit clearer lol
I have just done the 3 button's and i have on the screen the following
Android system recovery <3e>
Enter:OK key, select : vol up/down
Reboot system now
apply update from sd card
wipe data/factory reset
wipe cache partition
coping mdeoa files...
successfully copied media files.
#manual mode#
appling multi-csc
installing multi-csc
can't access to '/system/csc/ora/system/'.
successfully applied multi-csc
Is this the down load mode people are on about?
Brian

No its not when u have ur phone off press volume down the middle button and power button at same time it will get u into download mode pressing up volume and middle button and power will get u into recoverymode get it? So from download mode hook up ur phone to the computer use odin to flash a new rom to your phone using a pit file a pda file a phone file and csc file load those on odin and press start button make sure u got repartition cheked on and the other two auto reboot and freset time amd press start and you are good to go.... u can get those specific files on the xda website it depends what u want to flash u can go back to 2.2 froyo 2.3.4gingerbread is newest hope this help
Sent from my GT-I9000 using XDA Premium App

jamesythfc said:
Is this the down load mode people are on about?
Brian
Click to expand...
Click to collapse
No that is recovery mode
{
"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"
}
This is download mode
As I said, You should watch the great videos by Totallydubbed in those links to get familiar with a few things.
The button sequence for download mode is long press (volume down + power + home button) until that image appears, be careful not to press too hard on those keys m8, you're gonna need them, let us know how you get on.

Thanks mate, i have managed to get into the download mode, just need to sit and go through what i actually have to do now
Brian

Is Odin3_v1.3.exe any good have found one but not sure
All the others have far too many links for me to understand lol
Brian

to be honest, if kies crashed your phone, and you aren't very tech, take it back and while you are at it remind samsung what a piece is sh*t kies is! It happens all too often and its about time they sorted it, failing that you can try as a above posts, and use odin to flash brew firmware
Insanity cm 016/glitchv10c

slaphead20 said:
to be honest, if kies crashed your phone, and you aren't very tech, take it back and while you are at it remind samsung what a piece is sh*t kies is! It happens all too often and its about time they sorted it, failing that you can try as a above posts, and use odin to flash brew firmware
Insanity cm 016/glitchv10c
Click to expand...
Click to collapse
Hah yeah couldn't agree more m8, I found that out 2 weeks after buying the phone, still, it's better to learn the fix now & just how to get the best out of the phone
jamesythfc said:
Is Odin3_v1.3.exe any good have found one but not sure
All the others have far too many links for me to understand lol
Brian
Click to expand...
Click to collapse
Brian, give THIS a go & READ!
Odin & pit HERE free download & then unzip/unrar it.

J 3 M said:
Hah yeah couldn't agree more m8, I found that out 2 weeks after buying the phone, still, it's better to learn the fix now & just how to get the best out of the phone
Brian, give THIS a go & READ!
Odin & pit HERE free download & then unzip/unrar it.
Click to expand...
Click to collapse
Duly agree as you will see from my sig, however he did say he was non tech so sometimes the safe route is the best!
Insanity cm 016/glitchv10c

I have downloaded Darky Resurrection 10.1 file i have used Bitzipper to extract it but when i open Odin 1.7 i can find the PIT file but not the PDA file?
Please help this is driving me mad lol
Brian

At first you have to flash a Gingerbread-firmware from Samsung (NO custom-ROM) containing Gingerbread-bootloader with Odin (flash with PIT-file and Re-Partition ticked) and then anither kernel that brings CWM to you and finally flash the custom-ROM with CWM.
Sent from my GT-I9000 using XDA Premium App

Brian,
It's easy to get confused with too much reading but the answer to your problem is already provided for you in the links however we'll try this.....
Flash Ficeto's Odin JVH base rom here it will root your phone & ready to go to Darky's
As provided
1. use Odin 3.1.3 to be 100% safe, make sure phone is not connected! then press pit file & track to the pit 512 & make sure repartition is ticked!
2. press PDA & track to the TAR file in the Ficeto folder, (do not unzip it!), assuming you've done this correctly you can put the phone into download mode
3. Once in download mode connect phone & wait 10-15 seconds before pressing start.
4. Assuming all of the above steps have went well the phone will be up & running & you can begin to set it up, accounts, wifi, settings etc, once you've done that check back here & let us know & we can then get you to the next step.
Please also say how strong/good your wifi, 3G, call & internet signals are too as you may need to flash through a few different modems to get back to the same quality you had before, then again you may not, however this is a minor step after so just get flashing the roms first.
If for any reason you cannot find Ficeto's PDA/TAR file in the folder it means you've downloaded the CWM version = (clockworkmod) instead, CWM is how you flash roms from an already up & running phone via the power button, so if this is the case just make sure you download the THIS ODIN VERSION from the link provided.

[GUIDE] Baseband/Radio "stuck" and not updating? Here's how to fix it!

Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Remember: This guide is specifically for those of you who have tried other methods and are still stuck on an old baseband. If you're just looking how to flash your radio, there are easier and less involved methods that don't require any wiping - I strongly advise you to try those first.
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
{
"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"
}
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.

Nice....it helped me :good:
Thanks :highfive:

neoKushan said:
Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.
Click to expand...
Click to collapse
No need this，too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband

nforce4 said:
No need this，too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband
Click to expand...
Click to collapse
Thanks, but unfortunately that didn't work for me.

neoKushan said:
Thanks, but unfortunately that didn't work for me.
Click to expand...
Click to collapse
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.

IzArsha said:
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.
Click to expand...
Click to collapse
Believe me when I say that I tried that, I tried just about everything before it would finally stick. Removing battery, leaving it off for 10s+ (I did this numerous times as TriangleAway demands it due to the risk if bricking your phone and one time left it off/unplugged for a good 20mins to no avail). There was some kind of write protection in place, Mobile ODIN (yeah tried that as well) mentioned it when trying to flash the Radio - hence why TriangleAway is needed.
Before it got "Stuck", I had manually updated my Modem a few times without issue. I've had the Note 3 since launch and voided Knox within about 2 days of getting it - believe me, I've been there and done that

Nothing worked for me also until I tried this method...
Sent from my SM-N9005 using XDA Premium 4 mobile app

Here's what I don't like, and what I "Do" Like...
Like....
1) A post in the proper forum that seems to help a few people fix their issue when other methods didn't seem to work.
Dislike...
1) Somebody coming in touting their own method (which may or may not work for a particular user). This, believe it or not, only adds to confusion when a person looks for an answer. Now there are different methods in the same thread topic.
2) 2 pages of back and forth arguing as a result of the above ^^^
So, I'll delete all posts concerning this debate on procedures.
Folks, don't go poaching other users threads please. If they provide a solution that helps a few users, then that is GREAT!!! Not all normal solutions work for all users. Stick around long and you will discover this on your own one day.
Cleaned thread, please don't make me come back and do it again.
MD

Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.

neoKushan said:
Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.
Click to expand...
Click to collapse
Much better. I didn't mean to start an argument... But it happened somehow.
Good detailed guide however. See you around XDA.

I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks

MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?

neoKushan said:
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?
Click to expand...
Click to collapse
I've done almost every method, but not yours. BTW I don't have any other triangle icon except the yellow triangle at the start of Download mode.

MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Unpack the tar file, and flash just the modem.bin into phone (not pda) in Odin.

not working on SM-N900w8
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?

jsecruzvalencia said:
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=53632129&postcount=1
In the first box.

Samsuage Galaxy S5 SM-G900W8 - Google/Random Apps Crashing [4.4.2-6.0][Same Result]

Hello, So I am having a very strange issue with this phone (Samsung Galaxy S5). For the pass 3 days I have been trying to diagnose this problem and I can't seem to figure it out. I was wondering if someone could help me or guide me to the right path.
I went from stock 5.1 lollipop that came with the phone. Used ODIN to flash TWRP and flashed CM 12.1. Then I flashed GApps then everything was fine booted into it. Then the welcome screen came up and immediately noticed "google play service has stop" and this would happen every 1 min or so. I just kept ignoring it. With every reboot a variety of crashes would happen. For example most of the google apps would crash along side with some simple apps like facebook. For every reboot the crashes would be more or less the same. The crashes are native and the stack trace are some what different but don't really tell much of a story.
So I went from CM 12.1 to CM 13 with the same results. I clean flashed it, installed gapps ( The recommend opengapps ) and the same results. Varitey of google apps crashing again and again and again. So I tried different roms that were not based on CM and the same thing. I flashed back to stock and same thing. Which was very werid, so at this point I was stuck I didn't know what else to think of. I tried every method to ensure that all the cache was clear on google play services and other apps that were crashing. The interesting thing is that sometimes when download an app I get a variety of errors unable to download or install ranging from error code 902, 960, -2 so I used adb debugger to see what the heck was going on. I noticed that the md5 hash from installing apps (From google play store) weren't matching. So I assume okay perhaps corrupt wireless card but I used my mobile data same thing and still doesn't fix the constant google apps crashing. These issues that I have described are the exactly same thing for all the different roms I have tried from stock > CM12.1 > CM13 > Blisspop > OmegaRom > Stock (Again)> (Stock kitkat 4.4.2) so this issues doesn't seem like a software issue as the same results happen every time. I was wonder if anyone could shed some light into this issue its a strange issues and I am speculating it is a hardware issue. Thank you very much

Flash this PIT file along with the stock ROM (At the same time / together)
http://forum.xda-developers.com/attachment.php?attachmentid=2800218&d=1402859206
Extract it to .pit, add to PIT section in ODIN 3.10.7, flash both stock ROM in AP or PDA section, and PIT file in PIT section
--
For the custom ROMs, are you sure you 100% wiped everything and formatted in TWRP before flashing the ROMs? (Including DATA?)

*Detection* said:
Flash this PIT file along with the stock ROM (At the same time / together)
http://forum.xda-developers.com/attachment.php?attachmentid=2800218&d=1402859206
Extract it to .pit, add to PIT section in ODIN 3.10.7, flash both stock ROM in AP or PDA section, and PIT file in PIT section
--
For the custom ROMs, are you sure you 100% wiped everything and formatted in TWRP before flashing the ROMs? (Including DATA?)
Click to expand...
Click to collapse
Yes and I will proceed to flash the pit. I actually I was a thread about flashing the pit with the stock before I posted ill try it out and flash it with stock to see the results and yes I formatted everything including data

Ok so I reflashing it along side with the pit file you gave me. I think I did it wrong as I unticked the "Re-Partion" because it was giving me error "Re-Partition operation failed" and on the phone it says "Secure check fail : PIT" the device is fine on stock same crashing results. I know the pit didn't flash at all I am assuming lol

If you unchecked repartition, then the PIT was useless as that is what it is for
Which provider is the phone with? Some have locked bootloaders and might not allow the PIT to be flashed

*Detection* said:
If you unchecked repartition, then the PIT was useless as that is what it is for
Which provider is the phone with? Some have locked bootloaders and might not allow the PIT to be flashed
Click to expand...
Click to collapse
I am with Fido, and download the stock ROM under "Fido" on sammoblie and on one of the links on the fourm. And yes I figured unchecking it wouldn't do anything I just thought I would try it out lol.

Just realised you already flashed TWRP and custom with ODIN, so your bootloader is not locked
You can try flashing just the PIT file on it's own, and then the Stock ROM again on its own after that
Make sure you run ODIN as Administrator (Right click > run as admin)
And use ODIN 3.10.7
You can try any stock ROM, as long as it's for your model S5, doesn't have to be FIDO
Double check in download mode, that it does say G900W8

*Detection* said:
Just realised you already flashed TWRP and custom with ODIN, so your bootloader is not locked
You can try flashing just the PIT file on it's own, and then the Stock ROM again on its own after that
Make sure you run ODIN as Administrator (Right click > run as admin)
And use ODIN 3.10.7
You can try any stock ROM, as long as it's for your model S5, doesn't have to be FIDO
Double check in download mode, that it does say G900W8
Click to expand...
Click to collapse
I have tried that and it fails ODIN saying " Re-Partition operation failed " phone saying " secure check fail : PIT"

100% it says G900W8 in download mode
You're using a native PC?
Phone is definitely in Download mode, and not recovery?
Feel like I've seen others with a similar problem in this forum, have a read through some threads, see if you can find any - I`ll post back if I come across them
Until then, hopefully someone who has seen this error before can chip in
EDIT - Hidden partition rings a bell..

*Detection* said:
100% it says G900W8 in download mode
You're using a native PC?
Phone is definitely in Download mode, and not recovery?
Feel like I've seen others with a similar problem in this forum, have a read through some threads, see if you can find any - I`ll post back if I come across them
Until then, hopefully someone who has seen this error before can chip in
EDIT - Hidden partition rings a bell..
Click to expand...
Click to collapse
Yes 100 percent download mode with the combos vol down + home + power. I also tried using link2sd to actually move all apps to my external SD card and same results constant random google apps crashes with other apps. Along with that issue I also have random "unable to download" issues on google play store using adb to capture the logs and verified that the issues were occurring because of a MD5 hash not being match to the source which leaves me to believe that it can either be a storage issues corrupted the data as it is being written to or the wireless nic in the phone itself. Thank you very much ill also look into it on the threads to see if anyone has a similar issues. Its a very strange issue, if anything I will be doing more debugging to see of I can for sure verify it is a issues of the internal storage of the device. Also I would like to mention that I used TWRP "Repair" partion on all directory from /system to /data
Also yes I am using a native PC Windows 10 Pro

If we can figure out the PIT issue, I feel it would probably solve it, I'm thinking that TWRP has done something to the files system / partition table
I know with my TF101 tab, G Play will error out if the storage is not formatted with a specific TWRP version prior to flashing the ROM
I've had problems with apps crashing on my S5 when I tried clearing the caches using stock recovery, nothing would fix it until I flashed the same stock ROM over the top, then flashed TWRP 2.8.7.0 with ODIN, and cleared caches with TWRP instead
Seems the stock recovery is buggy

*Detection* said:
If we can figure out the PIT issue, I feel it would probably solve it, I'm thinking that TWRP has done something to the files system / partition table
I know with my TF101 tab, G Play will error out if the storage is not formatted with a specific TWRP version prior to flashing the ROM
I've had problems with apps crashing on my S5 when I tried clearing the caches using stock recovery, nothing would fix it until I flashed the same stock ROM over the top, then flashed TWRP 2.8.7.0 with ODIN, and cleared caches with TWRP instead
Seems the stock recovery is buggy
Click to expand...
Click to collapse
Alright, sounds good, ill look into the PIT issue see if there is some way to flash it. After that I will flash stock then install TWRP with ODIN.

Franco093 said:
Alright, sounds good, ill look into the PIT issue see if there is some way to flash it. After that I will flash stock then install TWRP with ODIN.
Click to expand...
Click to collapse
Found a thread with the same issue for the S3, and the guy used a HEX Editor to remove that hidden partition section in the PIT file
Don't ask me how, Hex editors are confusing

*Detection* said:
Found a thread with the same issue for the S3, and the guy used a HEX Editor to remove that hidden partition section in the PIT file
Don't ask me how, Hex editors are confusing
Click to expand...
Click to collapse
I JUST saw the same thread doing it right now!

Good luck
Remember though, the PIT file wipes and recreates all the partitions on your phone, so if you get it wrong, and the original will not flash, you could end up with a brick

*Detection* said:
Good luck
Remember though, the PIT file wipes and recreates all the partitions on your phone, so if you get it wrong, and the original will not flash, you could end up with a brick
Click to expand...
Click to collapse
Well good news I MANGE TO DO IT! I removed the padding and flashed the PIT! Thank you! Ill keep you updated going to install PIT with stock at the same time then install TWRP!

Franco093 said:
Well good news I MANGE TO DO IT! I removed the padding and flashed the PIT! Thank you! Ill keep you updated going to install PIT with stock at the same time then install TWRP!
Click to expand...
Click to collapse
I installed the pit file with stock rom again same crashes occured. So I flashed TWRP then formated everything then installed PIT first then stock and same crashes. I am going to install cm 12.1 and try again.

Franco093 said:
I installed the pit file with stock rom again same crashes occured. So I flashed TWRP then formated everything then installed PIT first then stock and same crashes. I am going to install cm 12.1 and try again.
Click to expand...
Click to collapse
And you are not doing anything else other than flashing stock?
You're not letting Google backup restore your apps or anything? Just 100% stock?
If it's still doing it after flashing the PIT (Nice job btw )it's either a buggy stock ROM, but if it was doing it with custom too, that rules that out,
Or a hardware issue
Have you tried creating a new Google account to test, in case something with your account is messing with settings/apps (Unlikely, but only thing I can think of atm)
Have you tried formatting or just removing your MicroSD card, and then factory resetting stock again, so you have 100% just the phone, purely with stock ROM, with a new Google account - to remove any traces of anything you've done since buying it

I do not have a microsd card connected to it. And I tried a custom ROM and same crashes google services and google app constantly crashing, I also get random download errors.
{
"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 notice also that one of the google service crash was a memory violation error. Maybe the ram is corrupted

It is sounding more and more like a hardware fault, we've done just about all that can be done to rule out firmware (ROM)
KNOX will be tripped from you flashing custom too, so I'd say your only option is to pay for it to be fixed, or sell it as faulty and buy another one unfortunately, unless any other Android gurus have any ideas
Good luck
EDIT - One last thought, when you flashed the modded PIT on it's own, did you check to see if it had actually wiped the phone clean before flashing stock again? (Did it hang on the logo / black screen?)
Just wondering if the PIT did actually do it's job or not, after being modded

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