So. Entirely new to the all of this. I've managed to get OctOS running on my SPH-L710T, I'm running TWRP custom recovery, and that's all very nice. The problem I'm having is that I'm only getting basic cellular and 3G service. I'm completely unable to connect to any sort of LTE. My google-fu has gotten me as far as:
-I need to flash a different modem because oh boy tri-band
-That modem might be ND8 or NDC, and I can get ahold of those with a quick search.
-I Can easily brick my phone if I don't do this right.
I'm uncertain of what to do with this. I don't know which recovery I should use to odin in the modem. Do I flash the modem first, then reinstall OctOs? Are there other things I need to do? Are either of these even the right modem?
Any and all help would be super appreciated. And remember, I'm a total n00b with this stuff so... be gentle?
Nope the t has nf4, oh1 modems
hilla_killa said:
Nope the t has nf4, oh1 modems
Click to expand...
Click to collapse
Okay, so is there a way to flash in nf4/oh1 firmware without going back to full on stock? Feel like it kinda defeats the entire point of the project otherwise.
But again, I'm new to all this.
There is a stock rom for the DataDoneRight? If so I may give it a try, VM support asked me to do a PRL update and I can't so now I have no service at all.
Warning: There is NO working StockROM for the Data Done Right Virgin Mobile Triband using the OH1 baseband. If you flash any rom with any other modem, your doomed.
I luckily made a backup of my Tri-Band OH1 Modem for this rare phone. Here it is for anyone else that needs it:
http://d-h.st/O2Yo
Flashing Oct-L + This modem I managed to get rid of the "No Sim Card" error that occured when flashing other roms.
(Note: This will only get your 3G service back due to OcOS limitations, they do not have 4G LTE working on VMDDR)
However, I still can't get back to stock to execute data provisioning. Without it my phone can't make calls or get data. No PRL, No HiddenMenu.apk... so keep in mind if you sell that phone, or the number changes you are bricked just like me.
Epic Battle and Recovery of My Triband Phone (Required if changing phone numbers)
INCREDIBLE! :victory: The only words I have to describe my 3 week battle to recover my Virgin Mobile Data Done Right Tri-Band phone (THE CRAPPY ONE FROM WALMART). OK, if you need a PRL update and have to update "Profile" to get a new number - once again there are NO stock roms. Here's what worked for me... this is not for the faint of heart:
1) Have the d2refreshspr TWRP recovery from Oct-OS thread installed. You can flash it with heimdall.
Pro-Tip: You CANNOT flash a non-triband L710 rom from Hiemdall or Odin, so that's why we need recovery. People will say your phone has bad memory and junk, they're wrong. It fails with errors " ERROR: Failed to confirm end of file transfer sequence!" and "sw rev check fail fused 2 binary 1" respectively.
2) Wipe --> Advanced Wipe --> Check Dalvik Cache, System, Data, and Cache. Flash NDC modem for L710 Sprint. (This will completely break the SIM/modem! But allows you to boot 4.4.2 TouchWiz roms) For good measure, Reboot the recovery. (Do NOT attempt to install SuperSU if asked by TWRP, at this point as it seems to cause bootloops)
3) Flash TouchWiz based ROM: Conquest: Singularity 10 (beta 9) Full, choose Virgin Mobile as the carrier during install, and then flash the 10 (b10) Update. (Do NOT attempt to install SuperSU if asked by TWRP, at this point as it seems to cause bootloops)
4) Boot the phone it will take awhile, but it should come up. If it does, half of the battle is done.
5) Go through setup, connect to Wifi, and wait for everything to finish installing in the background.
6) Power off phone, your baseband is completely shot. Boot back into TWRP recovery.
7) Flash OH1 Modem, and then flash Universal_vmu_ApnFix-v.R2.zip
.
8) Reboot. If it boots, it's a miracle. Acknowledge all errors, there will be quite a few about failing apps that don't work with your OH1 modem.
9) Make sure Wifi is on and working, there will be no data to force an OTA otherwise since our modem is still not provisioned.
10) Go to Settings --> System Update --> Update PRL. If it works awesome! Do the same for "Update Profile".
Phone will reboot.
Done! Your L710TVPU0AOH1 should now have fixed baseband and data + phone number. Good Luck!!!
From here I plan to go back to OctOS and try a few other ROMS out. No one but @moonknightus 's amazing Conquest: Singularity could have saved this phone. All props go to the man and his team of rom helpers. :good:
Can I have a copy of the OH1 modem? The server where it is hosted is offline and I need it now as I hosed my Virgin Mobile Galaxy S3 Triband, installed another ROM without backing up my modem, I did a full nandroid through TWRP, but forgot to backup the modem through Partitions Backup and Restore.........
EDIT: Nevermind, I managed to resolve the issue alternatively. I downloaded the following Stock Image:
ALL_SPT_L710TVPU0ANF4_L710TSPT0ANF4_1683363_REV00_user_low_ship.tar.md5
Extracted the MODEM.bin file, then compressed it to MODEM.tar and through ODIN I flashed this file, the modem got flashed successfully, I flashed the Virgin Mobile APN fix, and voila! Modem works now.
I am stating this for others who managed to hose their Triband modem with non triband roms, there is another solution.
Related
Hi Guys (and Gals),
I'm sooooo tired. I have a couple of Sprint D700 phones that I am trying to customize and I'm stuck. I've been reading forums and Googling for hours over several days and weeks and I just can't seem to get to the next step. FYI, I'm a software developer by trade, so I'm frustrated that I cannot figure this out.
I'm trying this on a guinea pig phone first (not currently active on an account). So, it has all of the latest Sprint upgrades. Then, I did a factory reset. I was able to gain root access using Framaroot 1.6.1. Then, I downloaded Root Explorer, Terminal Emulator and ROM Manager.
I want to experiment with some Custom ROMs, but everything I do so far is blocked by the existing stock recovery (3e?). From what I've read, I need CWM 5.0.2.7. So, I tried to load that version of CWM via ROM Manager. However, it will not boot to CWM - it keeps going into stock.
Then, I recently read something that the Samsung phones need an updated Kernel in order for the CWM install to work? And if I understand correctly, the only way to do that is via ODIN (which I've also downloaded on my PC)? Or is there a version of recovery manager that has a digital signature that will pass the check by the stock recovery and let it install?
I've tried to find some versions of Kernels and really don't know what to try - a lot of the download links are dead.
I want to hang on to these phones a little longer because I like the size and the qwerty keyboard, so I've refused to give up so far.
I realize that the answers are somewhere in these threads, but I am having trouble sifting through information that is sometimes outdated or has dead links to files. Please help - what do I need to do next?
Thanks so much!
Making progress but still confused...?
OK, I have just tried to ODIN a new Kernel. I tried Shadow Kernel v2.0. Everything appeared to work properly in ODIN. However, when I reboot, the phone still goes into the old recovery (not CWM). When I look in the settings, the Baseband and Hardware versions both say "Unknown".
My current build is GINGERBREAD.FC09, Firmware 2.3.6.
What Kernel do I need to flash?
BrianN_Cols_OH said:
Hi Guys (and Gals),
I'm sooooo tired. I have a couple of Sprint D700 phones that I am trying to customize and I'm stuck. I've been reading forums and Googling for hours over several days and weeks and I just can't seem to get to the next step. FYI, I'm a software developer by trade, so I'm frustrated that I cannot figure this out.
I'm trying this on a guinea pig phone first (not currently active on an account). So, it has all of the latest Sprint upgrades. Then, I did a factory reset. I was able to gain root access using Framaroot 1.6.1. Then, I downloaded Root Explorer, Terminal Emulator and ROM Manager.
I want to experiment with some Custom ROMs, but everything I do so far is blocked by the existing stock recovery (3e?). From what I've read, I need CWM 5.0.2.7. So, I tried to load that version of CWM via ROM Manager. However, it will not boot to CWM - it keeps going into stock.
Then, I recently read something that the Samsung phones need an updated Kernel in order for the CWM install to work? And if I understand correctly, the only way to do that is via ODIN (which I've also downloaded on my PC)? Or is there a version of recovery manager that has a digital signature that will pass the check by the stock recovery and let it install?
I've tried to find some versions of Kernels and really don't know what to try - a lot of the download links are dead.
I want to hang on to these phones a little longer because I like the size and the qwerty keyboard, so I've refused to give up so far.
I realize that the answers are somewhere in these threads, but I am having trouble sifting through information that is sometimes outdated or has dead links to files. Please help - what do I need to do next?
Thanks so much!
Click to expand...
Click to collapse
Success - Finally got CWM - Ready to play with ROMs
OK, I finally got to where I needed to be. I'm not sure if I'd ODIN'd incorrectly or what. However, I did a factory reset from the stock recovery. Then, I tried ODIN with Shadow again. This time I did it with ODIN 3.07 instead of 3.09. I don't know if I did something wrong with the 3.09 version - the button names were abbreviated - maybe I hit the wrong selection for "PDA".
This time it booted right into CWM 5.0.2.7. Geez, I'm supposed to be smarter than this.
If anyone is starting this fresh and has this phone with all of the latest OTA updates (no root - stock everything), then I think this is the path to take. For those of you that have read my rantings, thank you for your time. Any comments (including humor at my expense) will be joyfully appreciated.
BrianN_Cols_OH said:
OK, I have just tried to ODIN a new Kernel. I tried Shadow Kernel v2.0. Everything appeared to work properly in ODIN. However, when I reboot, the phone still goes into the old recovery (not CWM). When I look in the settings, the Baseband and Hardware versions both say "Unknown".
My current build is GINGERBREAD.FC09, Firmware 2.3.6.
What Kernel do I need to flash?
Click to expand...
Click to collapse
BrianN_Cols_OH said:
OK, I finally got to where I needed to be. I'm not sure if I'd ODIN'd incorrectly or what. However, I did a factory reset from the stock recovery. Then, I tried ODIN with Shadow again. This time I did it with ODIN 3.07 instead of 3.09. I don't know if I did something wrong with the 3.09 version - the button names were abbreviated - maybe I hit the wrong selection for "PDA".
This time it booted right into CWM 5.0.2.7. Geez, I'm supposed to be smarter than this.
If anyone is starting this fresh and has this phone with all of the latest OTA updates (no root - stock everything), then I think this is the path to take. For those of you that have read my rantings, thank you for your time. Any comments (including humor at my expense) will be joyfully appreciated.
Click to expand...
Click to collapse
Steps to Root FC09
Odin v3.09 doesn't work that well with the D700, as that version no longer has the "PDA" field. Version 3.07 and lower work fine.
Flashing a kernel will not also flash a recovery; unless the kernel dev packaged CWM or TWRP in his zip file. The kernel thread will state if it comes packaged with a recovery.
Typically, all custom roms for the Epic are pre-rooted. So you would only have to download Superuser or SuperSU from the Play store to keep it updated.
More updates...
Thanks for that addtional info. I will get rid of my version of ODIN 3.09.
So... I am doing all of this on a "practice" phone - one that is spare and not currently connected to Sprint. It appears that what I did may have wiped the /EFS folder and no, I don't think I backed it up. I didn't back up anything on this phone because it was just a practice phone (the kind of mistake you only make once). So, my phone does not display an IMEI (MEID).
Do you think that restoring a stock image and starting over will help me restore my NV_DATA.BIN info? I have another one of these phones (currently active), but I'm guessing that I cannot just steal the NV_DATA.BIN file from that phone and edit the contents to change the IMEI and MAC Address, etc. That would be too easy.
Is there any way to do a new gen of the NV_DATA info? I will try ODIN back to stock tonight when I'm home, but in the mean time if anyone has any suggestions let me know.
This is quite a learning process. I'm getting much more familiar with how these things work now, so that can only be good.
nikon120 said:
Steps to Root FC09
Odin v3.09 doesn't work that well with the D700, as that version no longer has the "PDA" field. Version 3.07 and lower work fine.
Flashing a kernel will not also flash a recovery; unless the kernel dev packaged CWM or TWRP in his zip file. The kernel thread will state if it comes packaged with a recovery.
Typically, all custom roms for the Epic are pre-rooted. So you would only have to download Superuser or SuperSU from the Play store to keep it updated.
Click to expand...
Click to collapse
New issues - need help with CM 10.1...
OK, I've made progress and learned a lot. Essentially restored the bricked phone by going back to stock. Then, I started my process again.
- Used ODIN to flash rooted kernel with CM 5.0.2.7
- Flashed Cyanogenmod 10.1.3
- Flashed correct Gapps (dated 8/12 I think)
Software great, but modem not working. So, then I found the forum for the NS4G modem patches. I've tried several and I did get one to work. But, the latest version of CM 10.1 has SU built-in. When I do the modem repair, it breaks my SU root.
I've tried the nitest kernal (by the way, I like the TWRP recovery better than CM - it). I've tried several of the modem patches.
Do I need to go back to a certain stable version of CM 10? What order to I need to apply things?
Here's what I have on the phone at the moment. It has SU/root but no modem.
- Android 4.2.2
- 3.0.79-JB42-nitest-nr kernel
- CM 10.1-20130526-NIGHTLY-epicmtd (although I've tried several other builds)
I was sooooooo close. Please help? How do I get my modem working AND keep my SU/root?
BrianN_Cols_OH said:
Thanks for that addtional info. I will get rid of my version of ODIN 3.09.
So... I am doing all of this on a "practice" phone - one that is spare and not currently connected to Sprint. It appears that what I did may have wiped the /EFS folder and no, I don't think I backed it up. I didn't back up anything on this phone because it was just a practice phone (the kind of mistake you only make once). So, my phone does not display an IMEI (MEID).
Do you think that restoring a stock image and starting over will help me restore my NV_DATA.BIN info? I have another one of these phones (currently active), but I'm guessing that I cannot just steal the NV_DATA.BIN file from that phone and edit the contents to change the IMEI and MAC Address, etc. That would be too easy.
Is there any way to do a new gen of the NV_DATA info? I will try ODIN back to stock tonight when I'm home, but in the mean time if anyone has any suggestions let me know.
This is quite a learning process. I'm getting much more familiar with how these things work now, so that can only be good.
Click to expand...
Click to collapse
ROM is not dependent on modem. Modem is dependent on kernel patches though.
Be sure you have a compatible kernel for your modem, whether NS4G or Epic modem. Are you using Odin or recovery to flash your modem? I've read in the NS4G modem thread a while ago, that users had to flash the modem multiple times to get it to stick. I'd suggest keep flashing and checking.
Here is SuperSU v1.69 download link. Place on SD card and flash in recovery once you get modem working.
Modem issues...
Thanks for the response. Am I wrong, or are there kernel patches that are part of the CM 10.1 install? So, I do understand what you are saying - that the ROM itself shouldn't break the modem. However, I believe there were some kernel patches in the CM install - maybe I'm totally wrong?
When I did have one of the modem patches working, I tried to separately download SuperSU, but it didn't seem to work. I really liked seeing the SU functionality built in to the ROM (it is available right from the settings menu near the developer options). Is it actually part of the kernel or part of the ROM? When it was broken, it was as if I still had root access but couldn't use it because there wasn't an SU manager. So, I don't know that root was broken so much as the SU piece that seems to manage it.
In any event, I suspect you are right about needing ODIN for the modem. So, what file should I flash as the "modem" in ODIN? I think that is the next thing I should try as I was only doing the modem patch via recovery before.
Also, is there a tuturiol somewhere that would help me understand the entire Android file system? I am a developer by trade, but I'm not super-experienced in the Linux (and Unix) realm. I would like to read up on things like
- how the storage is partitioned
- what files are part of the kernal
- what files are part of the modem
- what files are part of the ROM
- what files are part of the recovery platform
I'm guessing I won't find a CONFIG.SYS and AUTOEXEC.BAT - LOL.
Thanks so much for replying - I'm still learning and hopefully I'll be able to give back to others once I become an expert. I apologize as I am probably asking questions that have been answered, however I've really poured through several forums and there are so many posts that I may have missed just what I needed. Once I've mastered this phone I may move on to my daughter's GS2 and maybe think about a GS3 or GS4 in the future...
nikon120 said:
ROM is not dependent on modem. Modem is dependent on kernel patches though.
Be sure you have a compatible kernel for your modem, whether NS4G or Epic modem. Are you using Odin or recovery to flash your modem? I've read in the NS4G modem thread a while ago, that users had to flash the modem multiple times to get it to stick. I'd suggest keep flashing and checking.
Here is SuperSU v1.69 download link. Place on SD card and flash in recovery once you get modem working.
Click to expand...
Click to collapse
More info...
OK, after some further reading, I believe what I need to try next is to load a new modem.bin file using ODIN. I would use "Phone" (not "PDA").
I think I downloaded 2 different modem versions that hopefully have what I need. I can't check them at the moment, but will try one of those tonight. if you have any suggestions as to which modem to use, please let me know (my kernel version is shown previously).
I also found some good info on the Android file system and I understand a little better how the paritions work for kernel, system, storage, cache...
Also, what is this JB Big Mem fix that I've seen in some of the patches?
BrianN_Cols_OH said:
Thanks for the response. Am I wrong, or are there kernel patches that are part of the CM 10.1 install? So, I do understand what you are saying - that the ROM itself shouldn't break the modem. However, I believe there were some kernel patches in the CM install - maybe I'm totally wrong?
When I did have one of the modem patches working, I tried to separately download SuperSU, but it didn't seem to work. I really liked seeing the SU functionality built in to the ROM (it is available right from the settings menu near the developer options). Is it actually part of the kernel or part of the ROM? When it was broken, it was as if I still had root access but couldn't use it because there wasn't an SU manager. So, I don't know that root was broken so much as the SU piece that seems to manage it.
In any event, I suspect you are right about needing ODIN for the modem. So, what file should I flash as the "modem" in ODIN? I think that is the next thing I should try as I was only doing the modem patch via recovery before.
Also, is there a tuturiol somewhere that would help me understand the entire Android file system? I am a developer by trade, but I'm not super-experienced in the Linux (and Unix) realm. I would like to read up on things like
- how the storage is partitioned
- what files are part of the kernal
- what files are part of the modem
- what files are part of the ROM
- what files are part of the recovery platform
I'm guessing I won't find a CONFIG.SYS and AUTOEXEC.BAT - LOL.
Thanks so much for replying - I'm still learning and hopefully I'll be able to give back to others once I become an expert. I apologize as I am probably asking questions that have been answered, however I've really poured through several forums and there are so many posts that I may have missed just what I needed. Once I've mastered this phone I may move on to my daughter's GS2 and maybe think about a GS3 or GS4 in the future...
Click to expand...
Click to collapse
Modem.bin
Actually, the 2 modem/radio files I have are zip files and there is no modem.bin file inside. What exactly do I flash with ODIN?
BrianN_Cols_OH said:
OK, after some further reading, I believe what I need to try next is to load a new modem.bin file using ODIN. I would use "Phone" (not "PDA").
I think I downloaded 2 different modem versions that hopefully have what I need. I can't check them at the moment, but will try one of those tonight. if you have any suggestions as to which modem to use, please let me know (my kernel version is shown previously).
I also found some good info on the Android file system and I understand a little better how the paritions work for kernel, system, storage, cache...
Also, what is this JB Big Mem fix that I've seen in some of the patches?
Click to expand...
Click to collapse
BrianN_Cols_OH said:
OK, after some further reading, I believe what I need to try next is to load a new modem.bin file using ODIN. I would use "Phone" (not "PDA").
I think I downloaded 2 different modem versions that hopefully have what I need. I can't check them at the moment, but will try one of those tonight. if you have any suggestions as to which modem to use, please let me know (my kernel version is shown previously).
I also found some good info on the Android file system and I understand a little better how the paritions work for kernel, system, storage, cache...
Also, what is this JB Big Mem fix that I've seen in some of the patches?
Click to expand...
Click to collapse
Yes, use the Phone slot for flashing the modem.bin.
As for the kernel patches, there are swap files that you can flash in recovery that will use the proper blobs for your preferred modem type. Typically, roms will state in the thread title if they are NS4G or not. Always assume the ROM is Epic modem.
BigMem is for capturing video from the camera app.
BrianN_Cols_OH said:
Actually, the 2 modem/radio files I have are zip files and there is no modem.bin file inside. What exactly do I flash with ODIN?
Click to expand...
Click to collapse
Give me about 2 hours. I'll reupload all modem files to my devhost account, located in my signature.
Sent from my Nexus 7 using Tapatalk 4
Thanks!
Great, thanks so much. I will look for the modem files a little later.
nikon120 said:
Yes, use the Phone slot for flashing the modem.bin.
As for the kernel patches, there are swap files that you can flash in recovery that will use the proper blobs for your preferred modem type. Typically, roms will state in the thread title if they are NS4G or not. Always assume the ROM is Epic modem.
BigMem is for capturing video from the camera app.
Give me about 2 hours. I'll reupload all modem files to my devhost account, located in my signature.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
BrianN_Cols_OH said:
Great, thanks so much. I will look for the modem files a little later.
Click to expand...
Click to collapse
Ok, all Epic modems and NS4G modems are reuploaded. I also included the swap files for each. Everything with (Flashable) means to be flashed within recovery. Those swap files are the blob changes I mentioned earlier. This way you can swap modems using recovery, rather than relying on Odin.
Everything in the Odin folder can be placed in the phone slot and flashed as-is. (No need to extract the .bin file from the archive.)
As for the built-in root manager in CM, I'd try reflashing the rom first, and then messing with the modem.
Hey guys I am a bit confused on a couple of things backup related.
I just Rooted my phone to stock using Mr. Robinson's ROM and I am now 4.1.2 rooted on a 4.1.2 BL
I want to use Sky Note Air ROM (4.3.3 based) due to its Air command feature but don't want to get the 4.3 BL. From what I understand, it can be done using Mobile Odin and downloading a wifi patch but I want to backup my phone before I take the plunge
What I'm wondering is, how do I do this without tripping the warranty counter with TWRP. I don't understand how custom recovery works. What I know is that I want to:
backup my phone in it's working condition and if somewhere in the flashing process it doesn't turn out well, I want to go back tothe place I was when it was working on 4.1.2 rooted It seems I need nandroid backup?
Do I need to install TWRP and the recovery in order to do this or are there any other programs that can give me what I want (ie: Titanium backup). Again I'm just a bit concerned about TWRP recovery messing up the phone warranty status.
Install a custom recovery such as TWRP or CWM. Once there choose backup and select the partitions you wish to backup. I always back up boot, cache, system, and data. Reboot as normal.
Once in android I use an md5 verifier to check the validity of the backup. Android File Verifier or Nandroid Manager are two that can do the job. It will take a while as the files add up to about 5gb or so. Once that is done throw your backup onto an external storage solution (PC or cloud). Be confident.
Additionally I do a titanium backup from within android. Once I flash my new ROM I will install my apps from the play store and restore app data to the ones I simply can't do with starting over.
WiFi patch... Don't think that mobile Odin will do be able to apply it. PC Odin or Heimdall are your only options for touching the bootloader.
For WiFi on 4.3 TW ROMs I run agni kernel which gives WiFi back with no bootloader funny business.
Hastily spouted for your befuddlement
Coug76 said:
Install a custom recovery such as TWRP or CWM. Once there choose backup and select the partitions you wish to backup. I always back up boot, cache, system, and data. Reboot as normal.
Once in android I use an md5 verifier to check the validity of the backup. Android File Verifier or Nandroid Manager are two that can do the job. It will take a while as the files add up to about 5gb or so. Once that is done throw your backup onto an external storage solution (PC or cloud). Be confident.
Additionally I do a titanium backup from within android. Once I flash my new ROM I will install my apps from the play store and restore app data to the ones I simply can't do with starting over.
WiFi patch... Don't think that mobile Odin will do be able to apply it. PC Odin or Heimdall are your only options for touching the bootloader.
For WiFi on 4.3 TW ROMs I run agni kernel which gives WiFi back with no bootloader funny business.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
So TWRM will make the backup on my internal storage, which I then need to transfer to my SD card?
And titanium backup backs up app data that you can use to go back to the status of your apps on the new ROM?
And you're saying while I can install a 4.3 ROM via mobile Odin, I cannot install a wifi patch without PC Odin which will trigger a custom status if I'm not mistaken?
I was under the impression I can use this wifi patch without a need for touching kernels?: http://forum.xda-developers.com/showpost.php?p=48468121&postcount=204
And finally: On the app store I see TWRP manager and I install it from the play store but is this the only step I need for installation, or do I need to install other components to be able to do a proper backup? And with TWRP do you use it to flash a custom ROM or is it used to restore your stock ROM and does either mess up the official status/warranty status of the phone? Thanks in advance
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
My modem?
So I did flash successfully but my 4G modem aint working, any tips on how to fix this if it is a common problem. I already flashed latest modem but still no dice. Still on 4.1.2 BL if I'm not mistaken
edo101 said:
So TWRM will make the backup on my internal storage, which I then need to transfer to my SD card?
And titanium backup backs up app data that you can use to go back to the status of your apps on the new ROM?
And you're saying while I can install a 4.3 ROM via mobile Odin, I cannot install a wifi patch without PC Odin which will trigger a custom status if I'm not mistaken?
I was under the impression I can use this wifi patch without a need for touching kernels?: http://forum.xda-developers.com/showpost.php?p=48468121&postcount=204
And finally: On the app store I see TWRP manager and I install it from the play store but is this the only step I need for installation, or do I need to install other components to be able to do a proper backup? And with TWRP do you use it to flash a custom ROM or is it used to restore your stock ROM and does either mess up the official status/warranty status of the phone? Thanks in advance
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
Click to expand...
Click to collapse
You can have TWRP save to external SD by changing your directory to save to prior to backup.
TB can restore app data as well as system data. I don't usually restore apps from TB. I will do some app data and SMS/MMS from TB Pro. Messing with TB restores can make for flaky installs should the wrong stuff be restored especially between Android versions.
Mobile Odin will not touch the bootloader. The WiFi patch is applied to the bootloader. You can try all day long and not do anything other that kill your battery and need to recharge. Odin has 0 to do with custom status. Custom status is a TW root detection thing and not an Odin thing.
The WiFi patch will allow the use of TW stock kernel with WiFi. It *can* be buggy. I just run Agni kernel with TW ROMs and avoid the whole issue that way. I don't see the down side but some stuff like all share might not work with a custom kernel I guess.
I don't know what TWRP manager is. I just checked in the Play Store (the App Store is what iPhone users are stuck with) and it looks like that app is not real useful. I wouldn't give it a second look. If you MUST use an app to install recovery use Goo Manager, it's the official TWRP install app. The rest of the custom recovery functionality is best done in TWRP. Only use the recovery version prepared specifically for your device's model number. Once you install that don't use an app to update the recovery version while on a non TMo based GN2 ROM. The build.prop for the non TMo devices can cause the app to apply the wrong version to your phone.
Also don't flash any modem for a device other that the specific model number on your device. Note 2 has myriad versions. The T-Mobile version is the SGH-T889. ROMs for GSM LTE Note 2 versions are OK (AT&T/SGH-I317 or N7105). Modem or recovery are not.
Custom recovery is what installs and backs up then restores our devices. The act of rooting or installing absolutely voids warranty (in the eyes of Samsung). That doesn't mean that we can't get back to stock and clear flash counters to be warranty valid. If there is a hardware issue that needs to be addressed you can almost always get back to stock. If the device is broken, you aren't covered by warranty anyway.
Hastily spouted for your befuddlement
---------- Post added at 02:24 AM ---------- Previous post was at 02:23 AM ----------
edo101 said:
So I did flash successfully but my 4G modem aint working, any tips on how to fix this if it is a common problem. I already flashed latest modem but still no dice. Still on 4.1.2 BL if I'm not mistaken
Click to expand...
Click to collapse
What did you flash? How did you do it? Need more detail.
Hastily spouted for your befuddlement
Coug76 said:
You can have TWRP save to external SD by changing your directory to save to prior to backup.
TB can restore app data as well as system data. I don't usually restore apps from TB. I will do some app data and SMS/MMS from TB Pro. Messing with TB restores can make for flaky installs should the wrong stuff be restored especially between Android versions.
Mobile Odin will not touch the bootloader. The WiFi patch is applied to the bootloader. You can try all day long and not do anything other that kill your battery and need to recharge. Odin has 0 to do with custom status. Custom status is a TW root detection thing and not an Odin thing.
The WiFi patch will allow the use of TW stock kernel with WiFi. It *can* be buggy. I just run Agni kernel with TW ROMs and avoid the whole issue that way. I don't see the down side but some stuff like all share might not work with a custom kernel I guess.
I don't know what TWRP manager is. I just checked in the Play Store (the App Store is what iPhone users are stuck with) and it looks like that app is not real useful. I wouldn't give it a second look. If you MUST use an app to install recovery use Goo Manager, it's the official TWRP install app. The rest of the custom recovery functionality is best done in TWRP. Only use the recovery version prepared specifically for your device's model number. Once you install that don't use an app to update the recovery version while on a non TMo based GN2 ROM. The build.prop for the non TMo devices can cause the app to apply the wrong version to your phone.
Also don't flash any modem for a device other that the specific model number on your device. Note 2 has myriad versions. The T-Mobile version is the SGH-T889. ROMs for GSM LTE Note 2 versions are OK (AT&T/SGH-I317 or N7105). Modem or recovery are not.
Custom recovery is what installs and backs up then restores our devices. The act of rooting or installing absolutely voids warranty (in the eyes of Samsung). That doesn't mean that we can't get back to stock and clear flash counters to be warranty valid. If there is a hardware issue that needs to be addressed you can almost always get back to stock. If the device is broken, you aren't covered by warranty anyway.
Hastily spouted for your befuddlement
---------- Post added at 02:24 AM ---------- Previous post was at 02:23 AM ----------
What did you flash? How did you do it? Need more detail.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
I flashed http://forum.xda-developers.com/showthread.php?t=2584533
http://skynote.camattin.com/)?
SKy Note Air G2 and I flashed it with the T889 MK7 modem along with Agni Kernel.
However Everything else is working except for the modem. I'm still on 4.1.2 BL it looks like (not sure how to check) but my mobile stuff is in tact. It just says mobile network state (disconnected) but all my phone info is correct. It even still has my MetroPCS/Tmo as my Network
Although now, my phone shows as ATT model
I was thinking, should i flash the 4.1.2 modem to see if it will work? I am I believe still on the 4.1.2 BL since I used TWRP to flash not PC Odin or Heimdall
edo101 said:
I flashed http://forum.xda-developers.com/showthread.php?t=2584533
http://skynote.camattin.com/)?
SKy Note Air G2 and I flashed it with the T889 MK7 modem along with Agni Kernel.
However Everything else is working except for the modem. I'm still on 4.1.2 BL it looks like (not sure how to check) but my mobile stuff is in tact. It just says mobile network state (disconnected) but all my phone info is correct. It even still has my MetroPCS/Tmo as my Network
Although now, my phone shows as ATT model
I was thinking, should i flash the 4.1.2 modem to see if it will work? I am I believe still on the 4.1.2 BL since I used TWRP to flash not PC Odin or Heimdall
Click to expand...
Click to collapse
Your APN is still wrong. SkyNote is an I317 ROM. It has APN settings for AT&T. The reason your device thinks that it's an I317 is because your ROM is built for the I317. The build.prop is for i317. You can either live with it or change the build.prop to T889. If your baseband shows the MK7 modem you are on the MK7 modem. Don't mess with it.
Hastily spouted for your befuddlement
Coug76 said:
Your APN is still wrong. SkyNote is an I317 ROM. It has APN settings for AT&T. The reason your device thinks that it's an I317 is because your ROM is built for the I317. The build.prop is for i317. You can either live with it or change the build.prop to T889. If your baseband shows the MK7 modem you are on the MK7 modem. Don't mess with it.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Oh I'm not even sure if it was MK7 from the get go. I just fashed it without checking to MK7.
Anyway, I don't mind it being AT&T but I need to get the radio working again. How do I fix the APN issue? Or do I need to know my APN settings beforehand?
edo101 said:
Oh I'm not even sure if it was MK7 from the get go. I just fashed it without checking to MK7.
Anyway, I don't mind it being AT&T but I need to get the radio working again. How do I fix the APN issue? Or do I need to know my APN settings beforehand?
Click to expand...
Click to collapse
You need to determine what the metro APN settings are in advance of being able to change them. The APN settings are under settings > wireless and networks > more > access point names. Fill in the blanks accurately then reboot.
Hastily spouted for your befuddlement
am I able to flash this StockMOD Custom ROM 4.3 RLS2.1 for att or tmobile, over my existing stock 4.4.2, my modem as of now is i747UCUFNE4 but the rom description says to flash the 4.3 modem or it wont get data? someone help me out
heres the rom url http://forum.xda-developers.com/showthread.php?t=2504903
do not flash the older modem. just flash the rom and youll be good to go.
DocHoliday77 said:
do not flash the older modem. just flash the rom and youll be good to go.
Click to expand...
Click to collapse
since im coming from stock 4.4.2 do I only wipe cache n dalvik before flashing
You will most likely have to factory reset since you are downgrading.
You can try just wiping dalvik, but if it hangs at boot youll have to factory reset.
one more question
DocHoliday77 said:
You will most likely have to factory reset since you are downgrading.
You can try just wiping dalvik, but if it hangs at boot youll have to factory reset.
Click to expand...
Click to collapse
Thank You I tried wiping cache n dalvik, it hung but I went back in to twrp n wiped cache n dalvik again after install, worked like a charm!!!!!
hank you very much but can you answer me one question is there anyway you or another could port the revolutionary s5 v3 to the i747 it looks so amazing they only have it for the s3 i9300 not the s3 i747
Afaik, porting from tbe i9300 is a pretty difficult process. The device is very different from ours. Not saying it isnt possible, but I dont think we've really ever had any ports from that device.
I wont be able to try as I just have too much on my plate already and not enough time as it is. Sorry....maybe someone else will tackle it....
DocHoliday77 said:
Afaik, porting from tbe i9300 is a pretty difficult process. The device is very different from ours. Not saying it isnt possible, but I dont think we've really ever had any ports from that device.
I wont be able to try as I just have too much on my plate already and not enough time as it is. Sorry....maybe someone else will tackle it....
Click to expand...
Click to collapse
well thank you very much for responding you've been a very patient n helping hand if you could maybe you could pass it around to some of the other developers you are in contact with I know of about 30 people personally that would love to have that on there i747 not counting the people ive seen on here asking for a rom from the s5 but no big deal THANKS AGAIN
I was watching this thread because I had the exact same question. I tried installing the "StockMOD Custom ROM 4.3 RLS2.1" and my S3 wouldn't even boot past the Samsung screen. I left it there for 15 minutes and nothing. I tried wiping dalvik/cache from recovery and then it wouldn't even get that far. From that point on when I tried to reinstall the ROM it would go by and then when it got to the rebooting stage it would tell me "No OS installed. Are you sure you want to reboot?", or something of that nature. I then installed the Deodex Debloat Version from here: http://forum.xda-developers.com/showthread.php?t=2540998 and it installed/booted on the first try. Only problem is that Wi-Fi does not work & not sure of what my next step should be to get Wi-Fi working. I came from 4.4.2 OTA. Should I install the 4.3 modem or try flashing the StockMOD Rom again? I'm confused because it was stated that it didn't need to be installed.
Edit: I installed the StockMOD ROM directly over top without wiping anything and it worked. If I just want the "Deodex Debloat" version should I wipe, reinstall that ROM, then install the 4.3 modem since it didn't work before?
Edit: Second time flashing the Deodex Debloat ROM & Wi-Fi is working but now I have no data/4G. Help! LoL.
plastic_green_head said:
I was watching this thread because I had the exact same question. I tried installing the "StockMOD Custom ROM 4.3 RLS2.1" and my S3 wouldn't even boot past the Samsung screen. I left it there for 15 minutes and nothing. I tried wiping dalvik/cache from recovery and then it wouldn't even get that far. From that point on when I tried to reinstall the ROM it would go by and then when it got to the rebooting stage it would tell me "No OS installed. Are you sure you want to reboot?", or something of that nature. I then installed the Deodex Debloat Version from here: http://forum.xda-developers.com/showthread.php?t=2540998 and it installed/booted on the first try. Only problem is that Wi-Fi does not work & not sure of what my next step should be to get Wi-Fi working. I came from 4.4.2 OTA. Should I install the 4.3 modem or try flashing the StockMOD Rom again? I'm confused because it was stated that it didn't need to be installed.
Edit: I installed the StockMOD ROM directly over top without wiping anything and it worked. If I just want the "Deodex Debloat" version should I wipe, reinstall that ROM, then install the 4.3 modem since it didn't work before?
Edit: Second time flashing the Deodex Debloat ROM & Wi-Fi is working but now I have no data/4G. Help! LoL.
Click to expand...
Click to collapse
if you flashed it without wiping cache n dalvik- dirty flash then it should have worked unless u came from another 4.4.2 rom mine is working fine
correct me if im wrong
If ypu updated to 4.4.2, and then flashed a 4.3 rom, you have to use either the MJ2 or kt747 kernel or wifi wont work.
DocHoliday77 said:
If ypu updated to 4.4.2, and then flashed a 4.3 rom, you have to use either the MJ2 or kt747 kernel or wifi wont work.
Click to expand...
Click to collapse
that's not entirely true im not using either n my wifi is fine im on
kernel 3.0.31.1804024
[email protected]#1
i upgraded ota to 4.4.2 n never flashed any kernel at all
DocHoliday77 said:
If ypu updated to 4.4.2, and then flashed a 4.3 rom, you have to use either the MJ2 or kt747 kernel or wifi wont work.
Click to expand...
Click to collapse
Why exactly will it not work to flash a MJB kernel?
Boston78 said:
that's not entirely true im not using either n my wifi is fine im on
kernel 3.0.31.1804024
[email protected]#1
i upgraded ota to 4.4.2 n never flashed any kernel at all
Click to expand...
Click to collapse
I would get either no wifi or no data depending on which modem was used after flashing the rom.
01 - Via TWRP (2.7.1.0) dirty flash d2att_4.3_MJB_Debloat_Deodex_v1.2.zip
02 - Reboot without wiping cache/dalvik = freeze at AT&T logo
03 - Wipe cache/dalvik = freeze at AT&T logo
04 - Factory Reset = success with the exception of no wifi
05 - Flash MJB modem = Wifi now enabled but no data. (baseband unknown/imei null)
06 - Flash NE4 modem = data/baseband/imei restored, but no wifi again
07 - Flash UCUEMJ2_Insecure_kernel.zip + wipe cache/dalvik & reboot = somplete succcess (wifi+data all working)
At least for my experience Doc is 100% correct. Not sure how you were able to flash the StockMOD ROM without having to flash a kernel. Especially when "How to flash" on the StockMOD page says "5. Flash Kernel (For WiFi)". Not saying you are lying, just that I don't understand why you didn't need to.
Boston78 said:
that's not entirely true im not using either n my wifi is fine im on
kernel 3.0.31.1804024
[email protected]#1
i upgraded ota to 4.4.2 n never flashed any kernel at all
Click to expand...
Click to collapse
Are you using this rom along with the included kernel? Or something different?
plastic_green_head said:
Why exactly will it not work to flash a MJB kernel?
I would get either no wifi or no data depending on which modem was used after flashing the rom.
01 - Via TWRP (2.7.1.0) dirty flash d2att_4.3_MJB_Debloat_Deodex_v1.2.zip
02 - Reboot without wiping cache/dalvik = freeze at AT&T logo
03 - Wipe cache/dalvik = freeze at AT&T logo
04 - Factory Reset = success with the exception of no wifi
05 - Flash MJB modem = Wifi now enabled but no data. (baseband unknown/imei null)
06 - Flash NE4 modem = data/baseband/imei restored, but no wifi again
07 - Flash UCUEMJ2_Insecure_kernel.zip + wipe cache/dalvik & reboot = somplete succcess (wifi+data all working)
At least for my experience Doc is 100% correct. Not sure how you were able to flash the StockMOD ROM without having to flash a kernel. Especially when "How to flash" on the StockMOD page says "5. Flash Kernel (For WiFi)". Not saying you are lying, just that I don't understand why you didn't need to.
Click to expand...
Click to collapse
As for why, starting in 4.3 (MJB) samsung moved the modules required for wifi to work. They are now included in a different partition. Custom kernels (or rather any kernel but the original stock) look for the modules (drivers) to be in /system/lib/modules (the location on earlier builds). Since they are not there, the system doesnt know how to use the wifi radio resulting in no working wifi.
We got lucky with the MJ2 kernel. It was the first 4.3 leak, and just by chance I tried it on a different leak (for the T999) while trying to figure out the wifi issue and it worked! They simply had not made the change in that test build. Pure luck! The kt747 kernel works because it was built from source and modified to use its own modules which are included in the kernel package.
It has been a good while, so as for where the modules are located now im not suren. But if you browse to /system/lib/modules and find wlan.ko, youll see it is symlinked to /system/lib/modules/prima/prima_wlan.ko. Youll also notice there is no prima folder or file. In older builds, the wlan.ko file was actually there.
Hope that made sense and hope I got most of it correct. (Going from memory)
DocHoliday77 said:
Are you using this rom along with the included kernel? Or something different?
As for why, starting in 4.3 (MJB) samsung moved the modules required for wifi to work. They are now included in a different partition. Custom kernels (or rather any kernel but the original stock) look for the modules (drivers) to be in /system/lib/modules (the location on earlier builds). Since they are not there, the system doesnt know how to use the wifi radio resulting in no working wifi.
We got lucky with the MJ2 kernel. It was the first 4.3 leak, and just by chance I tried it on a different leak (for the T999) while trying to figure out the wifi issue and it worked! They simply had not made the change in that test build. Pure luck! The kt747 kernel works because it was built from source and modified to use its own modules which are included in the kernel package.
It has been a good while, so as for where the modules are located now im not suren. But if you browse to /system/lib/modules and find wlan.ko, youll see it is symlinked to /system/lib/modules/prima/prima_wlan.ko. Youll also notice there is no prima folder or file. In older builds, the wlan.ko file was actually there.
Hope that made sense and hope I got most of it correct. (Going from memory)
Click to expand...
Click to collapse
whatever kernel that was built into the rom is what im on I listed it in my reply before, I haven't flashed anything else ONLY THE ROM, mine booted right up n works great,
The more I think about it, it makes sense to me in both situations.
Id expect it to work on 4 4.2 because the wifi drivers are still in the same location, so as long as youre on 4.3 or above, it should work, as it apoears to do for you. But there are ithers who it did not work for and they have to use one of those other kernels. So it could be newer drivers not being compatible. Either way, if wifi is not working, I do know the kernel change will fix it.
DocHoliday77 said:
The more I think about it, it makes sense to me in both situations.
Id expect it to work on 4 4.2 because the wifi drivers are still in the same location, so as long as youre on 4.3 or above, it should work, as it apoears to do for you. But there are ithers who it did not work for and they have to use one of those other kernels. So it could be newer drivers not being compatible. Either way, if wifi is not working, I do know the kernel change will fix it.
Click to expand...
Click to collapse
well I have a twrp backup of it on my phone if you have some way of opening it, maybe somehow I could send it to you n whatever you find may be a tremendous help to you in how to fix the wifi n not having to flash the other kernels
I dont think there would be anything in a nandroid backup that would help. But tbh, right now I have no intention of digging into it any further. First because we already do have a pretty simple solution, and second because im already swamped with other projects and problems I've promised others I would work on.
So my wifes i747 was running 4.0.4 so I decided to upgrade it for her a bit. Im not new to rooting and flashing roms so I figured why not just put a custom KK rom onto it in order to freshen it up a bit for her. I also have to add that it is a ATT S3 unlocked and being used on Tmobile network.
Came to the forums and downloaded SlimKat rom and installed CWM and flashed the new rom. Everything went fine, but in the end my wife didnt like the feel of it and just wanted a new phone. So I traded her my phone and got hers. Well i wasnt a huge fan of the SlimKat rom either, nothing particularly wrong I was just always a CyanogenMod fan. Im having issues right now because I cannot get it to flash any new ROMs without messing up. Ill either get an error in CWM saying it cant flash the new rom or it will Flash but then never leave the LOGO screen. Ive let it sit for 45mins before.
I was able to always restore to a backup and just keep using SlimKat, but just tonight Im no longer able to restore to the backup. CWM sits at "Restoring data... c7ac6bd9.0..." but never actually finishes the restore.
So am I bricked? or what should I try? and also can someone just tell me what Rom/Kernal/Modem I need to flash in order to get it working. Id really like to use the Cyanide L, with Shift kernal but im not sure which modem I need. Tmobile modem or Att modem and which number.
Any help would be great thanks.
Additional info: I wiped cache, dalvik, and system/data everytime I tried to flash new rom, I made a backup and saved to my external before the flash. It is carrier unlocked and rooted. model number is the i747. CWM is v6.0.1.2
Your CWM is outdated.
Flash the latest Philz tar.md5 file in Odin: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
The latest KK ROMs will also need an updated bootloader and modem to function properly.
Hello everyone,
After a long fight to try and get this phone back to normal, everything seemed good,
except not really
I started on a buggy CM11 version. Sick of it, I downloaded a 4.4.4 stock rom. I had to disable firewall and defender, but I got Odin to flash my md5. I got through everything and it booted successfully. After signing in and all that jazz, I find out that my WiFi isn't working. After a few reboots, My 4G finally works and everything seems to be steady.
Then, after exploring the rest of the phone I find out that all my apps from last ROM are still there. I know that you are supposed to wipe before flashing, but I was told that Odin will take care of that. It obviously didn't.
After THAT, I try to boot into Recovery as the next sensible step is to try to wipe my data and cache. I turn the phone off and press (Vol up + Home + Pwr) and the first boot screen shows for a moment. It says in blue "RECOVERY BOOTING" in the corner. Right after, it disappears and in another second it does the same screen without the "RECOVERY BOOTING". And as presumed, it does a regular boot.
What did I miss? How can I wipe my phone from recovery? How can I fix my problem with Wifi?
Reflash in Odin.
Make sure you have the correct stock rom. If you flash the "md5" you may have flashed the wrong thing. The md5 is not tge firmware, that is just the code that verifies your firmware file is not corrupted.
If your old apps were still there, you flashed the wrong thing. There is no way to flash stock firmware in odin and not wipe the data partition.
You are correct then
Yeah, I flashed a tar.md5 in Odin. It gave me a new ROM but all my apps are there. After all that, I still can't go to recovery. I tried using the terminal and ROM Toolbox to go there, both didn't work. Can I just leave it as it is and find a way to recovery or is the only way to go to bootloader and flash a correct file to get to recovery?
Flash twrp and see if it will reboot into recovery, then factory reset and flash latest firmware with Odin right after. Odin will NOT wipe data. It has to be done manually
serio22 said:
Flash twrp and see if it will reboot into recovery, then factory reset and flash latest firmware with Odin right after. Odin will NOT wipe data. It has to be done manually
Click to expand...
Click to collapse
It depends on what you ate flashing.
If you are flashing a full stock factory image it will wipe user data. If you are just flashing a system partition it won't.
Essem G said:
Hello everyone,
After a long fight to try and get this phone back to normal, everything seemed good,
except not really
I started on a buggy CM11 version. Sick of it, I downloaded a 4.4.4 stock rom. I had to disable firewall and defender, but I got Odin to flash my md5. I got through everything and it booted successfully. After signing in and all that jazz, I find out that my WiFi isn't working. After a few reboots, My 4G finally works and everything seems to be steady.
Then, after exploring the rest of the phone I find out that all my apps from last ROM are still there. I know that you are supposed to wipe before flashing, but I was told that Odin will take care of that. It obviously didn't.
After THAT, I try to boot into Recovery as the next sensible step is to try to wipe my data and cache. I turn the phone off and press (Vol up + Home + Pwr) and the first boot screen shows for a moment. It says in blue "RECOVERY BOOTING" in the corner. Right after, it disappears and in another second it does the same screen without the "RECOVERY BOOTING". And as presumed, it does a regular boot.
What did I miss? How can I wipe my phone from recovery? How can I fix my problem with Wifi?
Click to expand...
Click to collapse
Fkash twrp and format system, data, cache and preload and install a deodexed stock os
g7755725 said:
Fkash twrp and format system, data, cache and preload and install a deodexed stock os
Click to expand...
Click to collapse
Also this. This gives you more control over the whole process
Skipjacks said:
Also this. This gives you more control over the whole process
Click to expand...
Click to collapse
How do I know whatever I download is deodexed? And I went to a page of ROMs someone gave me and I downloaded the NK2 version, which also gave me a tar.md5. If I want the correct thing to flash, what should I flash?
Essem G said:
How do I know whatever I download is deodexed? And I went to a page of ROMs someone gave me and I downloaded the NK2 version, which also gave me a tar.md5. If I want the correct thing to flash, what should I flash?
Click to expand...
Click to collapse
The first post of any customized stock rom will tell you if its deodexed. If it doesn't say it...its not.
@Essem G:
Any updates for us? I'm following this thread because I have similar problems with my WiFi not working after upgrading from 4.2.2.
Any luck getting TWRP flashed?
Also I believe that the stock firmwares do come as tar.md5's, as in the file: M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar.md5 from ShinySide's stock firmware thread.
As for the WiFi issue, from the hours of reading I've done it looks like this problem occurs when you upgrade your firmware, but it no longer matches the bootloader. Such as bootloader (Baseband) showing MDL, but Build Number showing NH7, NK2, etc. What does your show?
This thread may be of use to you when you get back to a working ROM. Good luck!
@RavenMind1
Everyone has been saying different answers and i've put off fixing my device for a while. I'm just afraid i'll brick it forever and have another nightmare after this current one. So no, there has been no progress. I think i'm gonna try to flash Philz and format my system, then flash a deodexed rom. @g7755725 said that you can flash TWRP, but I usually use Philz. It appears to be that I have lost root access because no root features work and SuperSU won't recognize it. Will everything work or am I setting my self up for disaster?
Edit: Where can I find a deodexed rom? I desperately need one, thanks
Essem G said:
@RavenMind1
Everyone has been saying different answers and i've put off fixing my device for a while. I'm just afraid i'll brick it forever and have another nightmare after this current one. So no, there has been no progress. I think i'm gonna try to flash Philz and format my system, then flash a deodexed rom. @g7755725 said that you can flash TWRP, but I usually use Philz. It appears to be that I have lost root access because no root features work and SuperSU won't recognize it. Will everything work or am I setting my self up for disaster?
Edit: Where can I find a deodexed rom? I desperately need one, thanks
Click to expand...
Click to collapse
Look in the forums for deodexed rom theirs a bunch and untouched as well i had philz but it eoukdnt boot my s4 so i had to switch to twrp because it does better then any recovery
g7755725 said:
Look in the forums for deodexed rom theirs a bunch and untouched as well i had philz but it eoukdnt boot my s4 so i had to switch to twrp because it does better then any recovery
Click to expand...
Click to collapse
Thanks for the support so far, but has this problem occured before? do you think the steps i've listed will solve this? Im just trying to make sure that I know exactly what to do before I go in. Thanks
Essem G said:
Thanks for the support so far, but has this problem occured before? do you think the steps i've listed will solve this? Im just trying to make sure that I know exactly what to do before I go in. Thanks[/Q] it should
Click to expand...
Click to collapse
@g7755725 I downloaded a deodexed rom from the SkipJacks guy (different page than what you sent me) and it's a little under 9MB... how could this possibly be a ROM?
Essem G said:
@g7755725 I downloaded a deodexed rom from the SkipJacks guy (different page than what you sent me) and it's a little under 9MB... how could this possibly be a ROM?
Click to expand...
Click to collapse
Have you tried my gamerrom Ultimate 1 its basically stock touchwiz of if Official NK2 M919UVUFNK2 with stweaks and no bloatware here is the thread gru 1 is in.the botyom of the thread http://forum.xda-developers.com/galaxy-s4-tmobile/development/stock-os-gamerrom-ultimate-2-touchwiz-t3078467
Sounds cool but i would have been interested a few months ago. I'm trying to sell the phone so I need to get it back to stock. Appreciate all the help and I think it's cool that you make ROMs
Essem G said:
Sounds cool but i would have been interested a few months ago. I'm trying to sell the phone so I need to get it back to stock. Appreciate all the help and I think it's cool that you make ROMs
Click to expand...
Click to collapse
If you're trying to go back to complete stock then just Odin NK2 firmware. http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508 I used the NK2 from here about 2 days ago to go back to stock.