Database Users

[Q] Bricked Badly. I am new to Epic coming from Vibrant

I am reaching out to the XDA community because with my Vibrant I received so much help, knowledge, experience you name it everyone has been so awesome. I have really hit a brick wall here with this new Epic and I have to say working on an Epic is 10x harder than a vibrant. I had the syndicatefrozen rom running and all of a sudden I rebooted the phone and it would not go past custom boot. So i did what I always do in the case of reflashing in cwm doesnt work... I used odin to flash the 512 pit and DI18 stock software but it fails every time. Now I have read every post I can find that suggests using a different usb cable, a different computer, try 512 pit, victory pit, tried the tar.md5 or the .tar., try redownloading the files, everything Now trust me when I say with my vibrant I NEVER encounter problems flashing with ODIN. If someone could please take some time to go back and forth with me on troubleshooting I would be so grateful. I have been trying so hard that all the troubleshooting processes have started to run together in my head and I'm really frustrated. Can anyone help?

The very first time I flashed my epic it bricked. It turned out I needed to redownload the Rom in my case. If that didnt work for me, my next step was to get a new cable.
but because it bricked I needed to reflash to a stock rom (which in your case I would re download (FROM A TRUSTED SITE)
Just to make sure... to Odin you need to be in "download mode". You can get into it by hold the #1 key on the qwerty keyboard and holding power. By doing that odin will see your phone.

If you need help, I made a bunch of how to youtube videos. There is a sticky in the general section... check it out.
Sent from my SPH-D700 using XDA App

stevenmcneal83 said:
I am reaching out to the XDA community because with my Vibrant I received so much help, knowledge, experience you name it everyone has been so awesome. I have really hit a brick wall here with this new Epic and I have to say working on an Epic is 10x harder than a vibrant. I had the syndicatefrozen rom running and all of a sudden I rebooted the phone and it would not go past custom boot. So i did what I always do in the case of reflashing in cwm doesnt work... I used odin to flash the 512 pit and DI18 stock software but it fails every time. Now I have read every post I can find that suggests using a different usb cable, a different computer, try 512 pit, victory pit, tried the tar.md5 or the .tar., try redownloading the files, everything Now trust me when I say with my vibrant I NEVER encounter problems flashing with ODIN. If someone could please take some time to go back and forth with me on troubleshooting I would be so grateful. I have been trying so hard that all the troubleshooting processes have started to run together in my head and I'm really frustrated. Can anyone help?
Click to expand...
Click to collapse
do not use the pit, it contains partition mapping, if you use the wrong one it can BRICK your phone. but yea stock samsung cable sucks, if i were you id try heimdall

I have a good bit of experience with ODIN. I've read that you have a better chance of permanently bricking using heimdall. Is that true? Also, how does heimdall work? Basically extract the zip files and load them individually?

First off, I'm not going to tell you one rom is better than another.....they're all good. However, I have become very fond of midNIGHT roms because the developer is very precise in walking you through the flashing process. He has download links for everything that you need to flash his roms in the op, including the stock D18 files from Sprint. I would try downloading the D18 files FROM HIS SITE and use them to ODIN back to stock. By the way, make sure that ur using ODIN 1.61, that version seems to give people the best results. Don't worry, you can download that from the midNIGHT op also. Make sure that all of the Epic's drivers were successfully installed on your PC. You can also get those from midNIGHT's op. Once you've downloaded the files you need, make sure before you ODIN, that you completely shut the phone down for at least 30 sec. Then open your keyboard and press and HOLD 1 and then the POWER button until you see the android robot with the shovel pop up. That's the Epic's downloading mode. Before plugging the phone into your PC, go ahead and open up ODIN, make sure that you only have reboot checked. Then put the victory.pit file in the pit spot and the stock D18 file in the pda spot. Now you can plug your phone in, if ODIN recognizes the phone you'll see a comm:0 in the top left side of ODIN highlighted in yellow. If not, then you need to reinstall the Epic's drivers. If you do see a comm:0 in yellow, then all is good.....go ahead and click on START and wait for it to finish. When done, ODIN will automatically reset your phone. Wait for it to boot up, then continue to flash according to the rom developer's instructions.......I know this is confusing, but I can guarentee that if you explicitaly follow the directions on midNIGHT's op, you'll be enjoying a new rom in no time. Hope this helped to some degree.....Good Luck......Happy Flashing

shabbypenguin said:
do not use the pit, it contains partition mapping, if you use the wrong one it can brick your phone. But yea stock samsung cable sucks, if i were you id try heimdall
Click to expand...
Click to collapse
if you use the .pit file that is included with the stock d18 file on midnight's op, i guarentee that it will work.......just used it a couple days ago. Sounds like you used the wrong .pit file the first time

My bad, I just double checked my downloads from midNIGHT's op and the correct .pit file he includes with the ODIN 1.61 download. Just download ODIN from midNIGHT's page and you'll have all the correct files for ur Epic

Where the hell did u get the 512 .pit file?

stevenmcneal83 said:
I am reaching out to the XDA community because with my Vibrant I received so much help, knowledge, experience you name it everyone has been so awesome. I have really hit a brick wall here with this new Epic and I have to say working on an Epic is 10x harder than a vibrant. I had the syndicatefrozen rom running and all of a sudden I rebooted the phone and it would not go past custom boot. So i did what I always do in the case of reflashing in cwm doesnt work... I used odin to flash the 512 pit and DI18 stock software but it fails every time. Now I have read every post I can find that suggests using a different usb cable, a different computer, try 512 pit, victory pit, tried the tar.md5 or the .tar., try redownloading the files, everything Now trust me when I say with my vibrant I NEVER encounter problems flashing with ODIN. If someone could please take some time to go back and forth with me on troubleshooting I would be so grateful. I have been trying so hard that all the troubleshooting processes have started to run together in my head and I'm really frustrated. Can anyone help?
Click to expand...
Click to collapse
\
Take the tar.md5 and erase the md5 off the end, just to have .zip. Put this in the PDA box and check marked. This worked for me numerous times when I downloaded the DI18 file. Make sure you just have Auto Reboot checked and no others, and make sure COM port is showing up with the appropriate drivers installed, which are the same for the Vibrant I believe. So shouldn't be the problem. Dont worry bout the pit file, it is a mapping source for the md5 that isn't really needed. If that fails, try a different port on the computer on the back and another USB cable.

stevenmcneal83 said:
I have a good bit of experience with ODIN. I've read that you have a better chance of permanently bricking using heimdall. Is that true?
Click to expand...
Click to collapse
No, however based user reports, the opposite could most certainly be argued.
However in the end it just comes down to personal preference. Just use whatever you're more comfortable with.

Leeboy said:
if you use the .pit file that is included with the stock d18 file on midnight's op, i guarentee that it will work.......just used it a couple days ago. Sounds like you used the wrong .pit file the first time
Click to expand...
Click to collapse
i didnt use a wrong pit, but just fore warning as he said he did. also you do not need to use the pit. it will pull it from the phone for just flashing

Thank you for all of the responses. I think only one person suggested something that I have not yet tried. The person that said to remove "md5" from the ".tar". But now my device will not be recognized by the computer. I have uninstalled and reinstalled the drivers numerous times. tried 3 different computers. tried no battery. tried leaving the battery out for a while and putting it back in. Ive tried a different cable. Does anyone know a guaranteed way to get my pc to recognize the phone? I mean once I get past this I can finally actually work on fixing the device. Thanks again everybody that gave their input. I'm going to destroy this phone soon if something doesnt give lol (also, the phone will go into download mode so there is still hope, i think)

Ok. somehow the computer all of a sudden recognized the device. I used heimdall to flash the stock software. The flash was completely successful, the phone rebooted and showed the sprint boot animation with sound, after that the screen is just blank. Any ides? I'm so close I can feel it

i can feel it too.

stevenmcneal83 said:
Ok. somehow the computer all of a sudden recognized the device. I used heimdall to flash the stock software. The flash was completely successful, the phone rebooted and showed the sprint boot animation with sound, after that the screen is just blank. Any ides? I'm so close I can feel it
Click to expand...
Click to collapse
If you flashed the stock software and it said successful I can only imagine you need to wait longer for it to boot. I have never used heimdall, due to always having success with Odin, so I can't give any real advice past this point except to try again. If you do get Odin to work, then please try the remove .md5 at the end and flash the DI18 file WITHOUT pit and I"m pretty sure that will work.
Use this utility in Windows I've uploaded and hit Description to organize the folders. Once that is complete, scroll down to the drivers that are named "Samsung SPH-D700 Card" and others. You will see many of them. Right click on the target and Uninstall them and all and reboot your computer. Then proceed to reinstall the drivers normally. This should make your computer recognize your phone again.
Once it does, Open ODIN, untick F. Reset Time, Tick the PDA and select the file in which you removed the .md5 ( should just be .tar file) and hit start.
Here is the program to remove drivers:
http://www.multiupload.com/3PC2BBAFSO

The problem now is not getting the phone to recognize. It all of a sudden started working. When I use ODIN it fails EVERY time. I know I'm using ODIN correctly because I have flashed back to stock about 4 times previously with this phone. When I flashed with Heimdall it said it was successful and the sprint boot screen came on which is further than I have been able to get in a week so it leads me to believe I'm very close to fixing it. After the bootup animation I left the phone for 10 minutes and the screen just stays blank with the capacitive buttons lit as well as led indicator light. I've tried mulitple flashes and still nothing. Any ideas?

I think most here have good experience with Odin, not Heimdall. Either try Heimdall again, or try Odin. I also agree with Leeboy - look at the instructions on www(dot)lostandtired(dot)com/android-development (new user - can't post links yet)
There's a video tutorial on how to Odin just the modem (and a note on where/how to Odin EC05).

Hmm,Maybe try it out on a different computer.Follow the procedure which is given Here, It will definitely work. I have done it over 5-6 times in my epic without a problem even once.

odin fails eveytime i try to flash the DI18 stock. The last item to show on the odin progress box is recovery.
{
"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"
}

eMMC BrickBug on Galaxy 10.1

Since there have been several reports about bricking their tablet when doing the factory reset in recovery, I think it is useful to open the thread about this problem so we can gather all the facts in one place and keep other topics clean.
Below are the facts that I have gathered so far. I will update this post in the future with new info.
PROBLEM:
When doing factory reset in recovery the Galaxy Tab may freeze. After that it will no longer turn on. Most if not all of these problems happened when using cm-9-20120901-EXPERIMENTAL-p4.zip and ClockWork recovery 6, that was available in the same directory. But in theory this problem can also happen when doing factory reset from stock ICS.
DIAGNOSE:
It seems that the problem is in the faulty firmware of the eMMC chip. When erasing the data, a command mmc_cap_erase is executed which can corrupt data in the chip and make in unusable. After restarting the the only APX device is visible in device manager and the tab does not turn on.
Also worth noting is that the brick may happen already the first time you do the factory reset, but on the other hand you can wipe several times without any problems. So it's a little bit random.
There have been several reports with the same problem also on other Samsung devices and a lot of info on this bug can be found in the thread:
http://forum.xda-developers.com/showthread.php?t=1644364
IS YOUR CHIP DANGEROUS OR SAFE?
There is an application made which will check which eMMC chip and firmware is loaded on your tab and will tell you if you are safe or not.
App can be found in thread http://forum.xda-developers.com/showthread.php?t=1693704
WHAT TO DO IF YOU HAVE A FAULTY eMMC CHIP
There are three conditions that all need to be satisfied to for corruption to occur:
1. You have a faulty eMMC chip
2. kernel needs to support mmc_cap_erase command
3. A recovery binary that triggers calls to mmc_cap_erase()
Gingerbread recoveries don't issue this command, so if you are still on Gingerbread you are safe. Pershoot also removed support for this command from his kernels, so they should also be safe. Additionally this problem can be avoided if by flashing CWM 5 or CWM 6 from droidbasement.com CM10 folder either with mobile odin or odin.
WHAT KIND OF INFO WOULD BE HELPFUL and WHAT TO DO:
1. How many users were affected by this bug. Please report in this topic if you have encounter this problem on Galaxy Tab 10.1
2. What have you tried to solve the problem?
One possible solution which worked in the past was to fully discharge the battery. So far most of the users are still waiting for their tab to discharge, but some reports already indicate that this will not help. There have also been some users saying that their device will not charge after the battery has been completely discharged so maybe it is not the best idea to fully discharge the tab. I will update this when we will have more reports from tab 10.1 users. More about this procedure can be read in http://forum.xda-developers.com/showthread.php?t=1478361
Another approach for solving this problem would be by using nvflash utility which can work in APX mode that our tab is currently in. If you are lucky and you have unlocked bootloder
you can try to load new image and recovery. If you receive error 0x4 error it means that you bootloader is locked and this approach will not work.
Details on this procedure can be found in http://forum.xda-developers.com/showthread.php?t=1130574
3. Warranty - How many users have taken the tab to Samsung service center and did the fix it?
Also please add any other info that might be useful and I will try to keep this post updated .
---------------------------------------------------------------------------
4. Conclusions
- At the moment there is no known way to repair it yourself.
- So far those claiming warranty had not problems and tab was repaired free of charge.
- Avoiding brick:
The only danger now seems to bi if you are on stock ICS ROM and you execute factory/data reset in Samsung recovery.
If you are using custom ROMs and CWM you should be safe because all custom ROMs/krenels have now removed mmc_cap_erase() from list of capabilities.

I have installed the bootloader and CWR 6 from the p4 folder on the droidbasement.
After that I have installed three or four different ROMs through recovery without any problems.
When I finally wanted to load the CM9 rom for the last time and selected "clear data", the tab has frozen at "formatting cache ..".
I waited for a while and then pressed power button. It turned off and now I am also stuck in APX mode.
I am still waiting for battery to discharge, although based on some posts I doubt it will help.

I had this problem with cm-9-20120828-EXPERIMENTAL-p4wifi.zip and the associated recovery.tar.md5 hosted by pershoot. The device froze while doing the clear data option in CWM. It will only show up as APX in device manager.
I've been waiting about a week and a half for the battery to drain. It is still not drained yet.
Based on the Epic 4G Touch thread it looks like the draining method is not likely to work.
Background
As many of you are aware since ICS has come out, there has been a nagging issue where in some situations flashing ROMs with an ICS-based kernel and custom recovery has left the phone with EMMC corruption. This EMMC corruption is so far non-recoverable, even with JTAG bit blasting, which should bypass all but hardware issues.
...
Complicating the testing/debugging is the issue that once the problem is triggered, your phone is basically not recoverable. You can try and ODIN a stock ROM on top which will basically work for all the components except the /data partition. Once it reaches the /data partition, ODIN will hang. Similarly if you try and wipe data/factory reset, it will hang or timeout after a while. Attempts to repartition and reformat using ODIN have not changed this behavior. Attempts to edit the partition info manually have not been successful. JTAG bit blasting has not been successful.
Click to expand...
Click to collapse
The fact that this does not affect GB kernels could explain why nobody seems to have reported success with the draining method yet in the recent brick bug cases. The draining method may have worked in the past with whatever issue(s) were causing the devices to be stuck in APX mode with GB. This does not seem to be the case so far with ICS and this corruption bug. The EMMC corruption bug seems like a more serious issue than simply doing a battery drain will solve.
If this is the case then wouldn't it be inadvisable to be suggesting the battery drain method to people? I mean if the drain method is not a solution to this problem then users will be left with their devices in a worse state. There have been users saying that their device will not charge after the battery has been completely discharged.

So, ¿What do I do if I have a faulty chip?

rayoco said:
So, ¿What do I do if I have a faulty chip?
Click to expand...
Click to collapse
Either Samsung Warranty or see if Mobile Tech Video can repair. I've seen people say they were able to get their phones revived by Mobile Tech.

Link to Mobile Tech Video, please? Lost a Tab 7 to this bug.

PookiePrancer said:
Link to Mobile Tech Video, please? Lost a Tab 7 to this bug.
Click to expand...
Click to collapse
Don't know how to contact them, just read others able to get it fixed by them.
Sent from my SAMSUNG-SGH-I747 using xda premium

I have an eMMC-related issue (Galaxy Tab 10.1 Google I/O Edition/ p4wifi), which leaves the tablet as bricked, but I am not sure it is the exact same problem.
1) running pershoot's cm10, not cm-9
2) no more boot in recovery (but from an external recovery using fastboot, which is still working)
3) heimdall no longer working (see )
4) normal boot loops (only) because /data is mounted read-only (I have the adb logcat) presumably due to fs-errors
At the end, the tablet is bricked, even if it is in a boot loop. Any interest in the logcat?

RE:
nakedninja42 said:
Either Samsung Warranty or see if Mobile Tech Video can repair. I've seen people say they were able to get their phones revived by Mobile Tech.
Click to expand...
Click to collapse
My tab isn't screwed in this moment. But what I do to prevent a Brick?

fix.kowalski said:
I have an eMMC-related issue (Galaxy Tab 10.1 Google I/O Edition/ p4wifi), which leaves the tablet as bricked, but I am not sure it is the exact same problem.
1) running pershoot's cm10, not cm-9
2) no more boot in recovery (but from an external recovery using fastboot, which is still working)
3) heimdall no longer working (see )
4) normal boot loops (only) because /data is mounted read-only (I have the adb logcat) presumably due to fs-errors
At the end, the tablet is bricked, even if it is in a boot loop. Any interest in the logcat?
Click to expand...
Click to collapse
you do not have a brick.
fastboot boot the stock IO recovery and do a factory reset in there. this will format /data. you will be revived.

rayoco said:
So, ¿What do I do if I have a faulty chip?
Click to expand...
Click to collapse
From my point of view, these following steps should prevent the device to be bricked:
* Flashing CWM 5 or CWM 6 from droidbasement.com CM10 folder either with mobile odin or odin.
* Flashing A1 kernel 1.6.4 that has MMC_CAP_ERASED disabled.
These are applied for those that have Stock ICS or CM9 build 09/01.
Correct me if I'm wrong.

What I would also like to know is how many users of Galaxy Tab 10.1 are using faulty eMMC chip?
This can be simply checked with BrickBug application:
http://forum.xda-developers.com/attachment.php?attachmentid=1303502&d=1346829980
Please report in this topic which eMMC chip is used in your device.
Additionally what would also be helpful for others is information if default ICS kernel supports MMC_CAP_ERASED command and if there is any situation that this happens on stock ICS if you issue Factory reset. Maybe someone with more knowledge can answer this.

podtalje said:
Additionally what would also be helpful for others is information if default ICS kernel supports MMC_CAP_ERASED.
Click to expand...
Click to collapse
yes, the stock ICS kernel does support mmc_cap_erased (as is the published source). this is how it ships from nvidia. removing it is an after thought. the root of the issue is the chip inside.

P7510 here.
eMMC chip
Type: MAG4FA
Date: 02/2012
CID: 1501004d414734464112e20982d12f00
FwRev: 0x12
Brick Bug?
YES. Insane chip.
I'm running a memory test right now. EDIT: My test passed. Took about 10 minutes to run with the app. I was on CM10 for a short time but have since moved back to Infamous2 ICS with the A1 kernel.

djmatt604 said:
P7510 here.
eMMC chip
Type: MAG4FA
Date: 02/2012
CID: 1501004d414734464112e20982d12f00
FwRev: 0x12
Brick Bug?
YES. Insane chip.
I'm running a memory test right now. EDIT: My test passed. Took about 10 minutes to run with the app. I was on CM10 for a short time but have since moved back to Infamous2 ICS with the A1 kernel.
Click to expand...
Click to collapse
I got the same result as djmatt604 (as far as the brick bug goes that is, not tried the memory test)

podtalje said:
What I would also like to know is how many users of Galaxy Tab 10.1 are using faulty eMMC chip?
This can be simply checked with BrickBug application:
http://forum.xda-developers.com/attachment.php?attachmentid=1303502&d=1346829980
Please report in this topic which eMMC chip is used in your device.
Additionally what would also be helpful for others is information if default ICS kernel supports MMC_CAP_ERASED command and if there is any situation that this happens on stock ICS if you issue Factory reset. Maybe someone with more knowledge can answer this.
Click to expand...
Click to collapse
What now?? I don't want to brick. I'm on CM10 cwm6.
{
"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"
}

My tab have eMMC Brickbug (i tested it with the little apk soft).
I am lucky ! Three days ago i flashed A1 kernel and when i choose to wipe i selected wipe data reset factory (i did it fastly and wipe partition line is just under) !!!!!! Happy to see my previous kernel had applied git patch to disable mmc_cap_erase !!!!! so all have been ok when reboot ! ouf !!!

This happened to me about a week ago, I was flashing 'cm-9-20120901-EXPERIMENTAL-p4.zip' using TWRP, now I can only see the tab in 'apx' mode.
Trying to send commands via 'nvflash' gives an 0x4 response, which indicates a locked bootloader (I believe).
Currently trying the 'battery drain' option, but as my tab had just been fully charged this is taking a while.
Of course, my tab is over 12 months old and therefore out of warranty!

eMMC chip
Type: SEM16G
CID: 02010053454d3136479061538a135e00
Revision: 0x90
Verdict: Unknown Chip, don't know if dangerous. At least it isn't one of the chips known to be bad.
I have been using TWRP and CWM 6 various times and did a full reset (inlcuding data wipes on TWRP), no bricks. I assume my chip is safe.

I got the brick bugger.
Although oddly enough, never bricked while doing a factory reset.

[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

Galaxy S4 SPH-L720T -> twrp, root, customrom and kernel(few questions!)

Heyo, lets get started ruining this device even more! See if we can't brick it ey?
Anyways first off the battery is draining like a madman, 1% every 30 seconds or so. The thing is not getting the performance in games that it should be, using other devices with lower end hardware as a reference(1.1ghz quad core, adreno 305, 2gb ram one touch, and 1.2ghz quad core, adreno 306, 1.3gb ram kyocera), it keeps micro-stuttering while browsing chrome and doing basic actions with the UI, also when the battery is draining too(funny, sometimes while I have the charger plugged in and do basic activies such as chrome, youtube, read books, mess with menu settings the battery actually charges instead of deplete, but sometimes, seemingly always now, it depletes just as fast as though it was unplugged).
Anyways I have decided to try and customize the device with the plethora of information on here and all over the web for this device(after doing a lot more "research" of course and laying everything out for myself step by step to try to minimize failure.
First question is how much of a chance is there to brick the device installing TWRP alone? Really want to get that on there before doing anything, then install SuperSU from there with zip flash. And does it matter if I use a .tar or .img version of TWRP to flash with odin? The latest version of TWRP is in .img format and the tutorials I read say to use a .tar.
After that witch should I do try first, custom rom or custom kernel? What custom rom would be best at this point in time(5/13/2016) for this device, 100% compatible and fully tested. Also a kernel(unless overclocking can be unlocked within the custom rom, in witch case less chance of me ****ing up yet another android device).
One last thing, I really hope that even I am successful in doing all of this without ****ing up the phone that it does not turn out to be a fruitless effort, how much performance gains can I expect from all of this, custom rom, debloat after root, set sd as default storage after root(package does not belong to 2000 afterall), and then maybe a slight overclock on the cpu and gpu.
And thats all assuming that one day after getting all of this to work that one day I don't wake up and for no apparent reason boot up the phone and find its bootlooped or something without ever changing anything once all of this is done, I mean if I get the thing working as I would like it to work theres no more reason for me **** with it is there? Also I guess no reason to even have the thing if it aint gonna function how I need it to function right?
Thanks for the help though anyways, if anybody even decides to help me this time in a manner that they are not just "helping" just because the end result ****s me over.
Thanks again.

Oh one other problem I am having with the phone I was hoping a custom rom might fix, my Apps will not register as the correct size in Application manager. A 2gb game is showing up as 50mb total data, and when using "Move to SD Card" it only shows only like 200kb of data on the sd card, it does with with every single app on the phone. I know should not be like this because the last 2 phones I had were able to move every single byte of data from every one of the same exact apps to the SD card without an issue. Plus the application manager not registering the correct app size is just bugging me.

phenom2955 said:
Heyo, lets get started ruining this device even more! See if we can't brick it ey?
Anyways first off the battery is draining like a madman, 1% every 30 seconds or so. The thing is not getting the performance in games that it should be, using other devices with lower end hardware as a reference(1.1ghz quad core, adreno 305, 2gb ram one touch, and 1.2ghz quad core, adreno 306, 1.3gb ram kyocera), it keeps micro-stuttering while browsing chrome and doing basic actions with the UI, also when the battery is draining too(funny, sometimes while I have the charger plugged in and do basic activies such as chrome, youtube, read books, mess with menu settings the battery actually charges instead of deplete, but sometimes, seemingly always now, it depletes just as fast as though it was unplugged).
Anyways I have decided to try and customize the device with the plethora of information on here and all over the web for this device(after doing a lot more "research" of course and laying everything out for myself step by step to try to minimize failure.
First question is how much of a chance is there to brick the device installing TWRP alone? Really want to get that on there before doing anything, then install SuperSU from there with zip flash. And does it matter if I use a .tar or .img version of TWRP to flash with odin? The latest version of TWRP is in .img format and the tutorials I read say to use a .tar.
After that witch should I do try first, custom rom or custom kernel? What custom rom would be best at this point in time(5/13/2016) for this device, 100% compatible and fully tested. Also a kernel(unless overclocking can be unlocked within the custom rom, in witch case less chance of me ****ing up yet another android device).
One last thing, I really hope that even I am successful in doing all of this without ****ing up the phone that it does not turn out to be a fruitless effort, how much performance gains can I expect from all of this, custom rom, debloat after root, set sd as default storage after root(package does not belong to 2000 afterall), and then maybe a slight overclock on the cpu and gpu.
And thats all assuming that one day after getting all of this to work that one day I don't wake up and for no apparent reason boot up the phone and find its bootlooped or something without ever changing anything once all of this is done, I mean if I get the thing working as I would like it to work theres no more reason for me **** with it is there? Also I guess no reason to even have the thing if it aint gonna function how I need it to function right?
Thanks for the help though anyways, if anybody even decides to help me this time in a manner that they are not just "helping" just because the end result ****s me over.
Thanks again.
Click to expand...
Click to collapse
Well first it sounds like you need a new battery, I suggest having a couple and an external charger (it's great for gaming, just pop in a new fully charged battery). To install TWRP with Odin you need the tar file. The chance of Helicon with TWRP is almost zero, recovery is always overwritten when you flash a stock tar in Odin. So if something is messed up, just flash the stock tar and you are back to stock, grab it at www.sammobile.com . When you Odin TWRP make sure that you uncheck Auto Reboot in Odin. I would suggest my ROM as it is still being updated every few months, but I am biased. I use my S4 for gaming and this thing can handle PSP emulation when it is tweaked right.
Wicked X is my ROM and it's located here - http://forum.xda-developers.com/showthread.php?t=3115583
{
"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"
}

Ok thanks, a little reluctant to install an OS with the name "Wicked" though.
Any ideas why the stock Application Manager is being wacky, done several factory resets. For instance I have installed Fifa 16 about 5 times now just to see if it would fix the data readout in App manager, the Game is at least 1.5gb total data, app manager shows it as about 50-70mb, when using "Move to SD Card" it shows about 700kb of data on sd card.
Whats the deal?
Also before flashing TWRP with odin I have to unlock bootloader or something?

phenom2955 said:
Ok thanks, a little reluctant to install an OS with the name "Wicked" though.
Any ideas why the stock Application Manager is being wacky, done several factory resets. For instance I have installed Fifa 16 about 5 times now just to see if it would fix the data readout in App manager, the Game is at least 1.5gb total data, app manager shows it as about 50-70mb, when using "Move to SD Card" it shows about 700kb of data on sd card.
Whats the deal?
Also before flashing TWRP with odin I have to unlock bootloader or something?
Click to expand...
Click to collapse
No, bootloader is already unlocked. I can't tell you on the other without more information. What ROM are you on? Have you done any modifications? Have you Odined a full stock tar?

I bought this phone used on cl. Fully stock not a single mod on it as far as I am aware. The only thing I have done is factory reset.
It seems half the time as well when I Uninstall apps the data stays in misc section of storage manager. I have to go into recovery and clear cache and I get my space back. And misc section of storage manager will be back down to its normal size.
@ your comment about loader. You absolutely certain and no bs that if I attempt to flash something (even just twrp) it ain't gonna fail and go tit's up because I didn't unlock bootloader or something?
Just lost 2 phones already simply from uninstslling gltools after it failed to produce my desired results. Install went fine, but uninstslling rebooted the phones and got one caught in boot loop other just sits on manufacur er logo.
If asked why I was stupid enough to try it a second time I'll say I wasn't 100% sure it was absolutely gltools as the culprit.
Anyways this is the first device I have had with so much support with custom recoveries. Roms and kernels and even access to stock rom files. Would love to successfully apply some good stable/safe/and better running mods than the stock stuff though since I am convinced this hardware should be running better than it currently is!! But not trying anything for a while though till I've read as much as I can at least and have at least a few options for recovery should somehring go wrong.
Don't like being stuck with thumb up my ass stacking bricks, I am no mason.

Nickvanexel said:
I bought this phone used on cl. Fully stock not a single mod on it as far as I am aware. The only thing I have done is factory reset.
It seems half the time as well when I Uninstall apps the data stays in misc section of storage manager. I have to go into recovery and clear cache and I get my space back. And misc section of storage manager will be back down to its normal size.
@ your comment about loader. You absolutely certain and no bs that if I attempt to flash something (even just twrp) it ain't gonna fail and go tit's up because I didn't unlock bootloader or something?
Just lost 2 phones already simply from uninstslling gltools after it failed to produce my desired results. Install went fine, but uninstslling rebooted the phones and got one caught in boot loop other just sits on manufacur er logo.
If asked why I was stupid enough to try it a second time I'll say I wasn't 100% sure it was absolutely gltools as the culprit.
Anyways this is the first device I have had with so much support with custom recoveries. Roms and kernels and even access to stock rom files. Would love to successfully apply some good stable/safe/and better running mods than the stock stuff though since I am convinced this hardware should be running better than it currently is!! But not trying anything for a while though till I've read as much as I can at least and have at least a few options for recovery should somehring go wrong.
Don't like being stuck with thumb up my ass stacking bricks, I am no mason.
Click to expand...
Click to collapse
100%, Sprint doesn't lock bootloaders (though Samsung has started to). You may have to turn off the an option in Settings/Security, I think it's called Write Protection, it won't let you Odin anything if it is on.

I have a sprint sph-720T
I installed TWRP using ODIN
then reboot in recovery, put OCTOS-M on to internal memory and wipe the cache davik
install the OCTOS-M from zip file then install GAPPS from zip.
BOOOM! you have a rooted android 6.0.1 ! longer battery life.
EDIT: if you need direct links to the files, just ask.

Mangodreads said:
I have a sprint sph-720T
I installed TWRP using ODIN
then reboot in recovery, put OCTOS-M on to internal memory and wipe the cache davik
install the OCTOS-M from zip file then install GAPPS from zip.
BOOOM! you have a rooted android 6.0.1 ! longer battery life.
EDIT: if you need direct links to the files, just ask.
Click to expand...
Click to collapse
Have you had any issues flashing the s4 to 6.0? It would be great if you added direct links. Thanks.

ABERBER1986 said:
Have you had any issues flashing the s4 to 6.0? It would be great if you added direct links. Thanks.
Click to expand...
Click to collapse
1. Put the Custom Rom Zip and the GAPPS zip on the phones memory card and then turn off the phone
2. Put the phone in download mode, connect to the computer via usb and run ODIN
Select AP and the select the TWRP recovery file. - Click Start - Once its finished
3. Put the phone in recovery mode - go to wipe, clear cache/davik a few times
go to install and select the Custom Rom Octos 6.0.1 that you put on the phones memory.
install it and then install GAPPS zip right afterwards
once those are installed reboot the phone and you are good.
These links are for user with Sprints galaxy s4 sph-720T ONLY
This is the TWRP recovery
https://dl.twrp.me/jfltespr
This link is to 6.0.1 Custom Rom by OCTOS
https://www.teamoctos.com/download/M_release/jfltespr/OCT-M-R1-6.0.1-20160319-jfltespr.zip
This is a link for GAPPS (google apps, playstore etc) - select the "variant" you want
http://opengapps.org/?arch=arm&api=6.0&variant=micro

Mangodreads said:
1. Put the Custom Rom Zip and the GAPPS zip on the phones memory card and then turn off the phone
2. Put the phone in download mode, connect to the computer via usb and run ODIN
Select AP and the select the TWRP recovery file. - Click Start - Once its finished
3. Put the phone in recovery mode - go to wipe, clear cache/davik a few times
go to install and select the Custom Rom Octos 6.0.1 that you put on the phones memory.
install it and then install GAPPS zip right afterwards
once those are installed reboot the phone and you are good.
These links are for user with Sprints galaxy s4 sph-720T ONLY
This is the TWRP recovery
https://dl.twrp.me/jfltespr
This link is to 6.0.1 Custom Rom by OCTOS
https://www.teamoctos.com/download/M_release/jfltespr/OCT-M-R1-6.0.1-20160319-jfltespr.zip
This is a link for GAPPS (google apps, playstore etc) - select the "variant" you want
http://opengapps.org/?arch=arm&api=6.0&variant=micro
Click to expand...
Click to collapse
Please advice which version of twrp you used. Because I am unable to flash thru through odin

bump........

earthworm82 said:
Please advice which version of twrp you used. Because I am unable to flash thru through odin
Click to expand...
Click to collapse
The link for teamoctos doesn't seem to work.

vikingjerr said:
The link for teamoctos doesn't seem to work.
Click to expand...
Click to collapse
You could just go their thread in the Android Development section[emoji6]

Wicked 10.9
bilgerryan said:
You could just go their thread in the Android Development section[emoji6]
Click to expand...
Click to collapse
I just downloaded Wicked 10.9 but am not sure I have all the files needed. In the first page it mentions to load the 720t conversion file and a kernal file.
Later I saw that the kernal file was include. I don't know if I should flash one, two or three files.

vikingjerr said:
I just downloaded Wicked 10.9 but am not sure I have all the files needed. In the first page it mentions to load the 720t conversion file and a kernal file.
Later I saw that the kernal file was include. I don't know if I should flash one, two or three files.
Click to expand...
Click to collapse
Three, the v11.0 update last.