Related
Hello everyone. I'm quite new to this whole fiddling with my S3 thing. I mean, I successfully flashed a previous version of Danvdh's Dandroid ROM a few months ago but was not pleased when it would not pick up ANY GPS satellites even after 20 minutes of waiting to get a fix. Of course I tried everything from tightening screws (none of my screws were loose) to that aGPS patch (for which it gave me the wrong location even after trying what the notes suggest).
Having said that, yesterday, I tried flashing other ROMs (like Beanstalk) in hopes of getting better GPS. Now Beanstalk worked fine and gave me GPS, but with that I then ran into problems mounting and formatting a new SD card. So then I flashed the newest version of Dandroid and successfully mounted the SD card, but it still gave me GPS problems, at which point I was kind of disheartened and decided to give saranhai's StockMOD ROM a try.
I ran into all kinds of problems.
1. I'm sure this isn't the dev's fault, but my CWM version 6.0.3.7 (is that old?) won't recognize any kind of change in my internal SD card since late yesterday. My desktop and ES file explorer both register the same files and folders, but CWM still sees old files like the zip files for Beanstalk and Dandroid which don't appear on my computer??? And it won't see any new files??? What did I do wrong? Therefore, I flashed things from my external SD card from there. (Was that wrong to do?) Also, every time I try to reboot through CWM, it says root access may have been lost and asks if I want to try and fix it. I say no because my SuperSU still works?
2. After FIRST flashing Dandroid 5.1 I noticed Wi-Fi wasn't working. A post from the Dandroid thread said to flash a kernel "or update to the newest bootloaders." I flashed the kernel he provided and found out too late that it was for T999L or something and my phone is T999. I'm kinda surprised my phone didn't brick then. Anyway, I got Wi-Fi, but whenever I tried to turn on mobile data, it said to insert a SIM card?? I'm sure it's because I flashed that wrong kernel. When I go into Settings > About Device it says the Baseband version is unknown and the Kernel version is as follows:
3.0.31-1804024
[email protected]
Sat Oct 5 00:13:48 KST 2013
and the build number: JSS15J.T999UVUEMJC
EDIT: I FOUND OUT MY PHONE WAS ACTUALLY T999L NOT T999. Currently trying to fix things. I'll get back to the thread.
3. So hoping saranhai's StockMOD ROM would give me the fresh start I so desperately needed, I followed his instructions step by step from flashing the right modem FIRST then flashing the ROM, but alas, the same "Insert SIM card...." error still plagued me. You would not believe how sad I got. (I'm still pretty sad.) At that point I tried REALLY hard to familiarize myself with what I was doing, reading the thread carefully, looking through that glossary thread to help me keep up with the techie terms, and searching for instructions on how to get it fixed, but I couldn't find anything and I was stuck.
4. This morning I flashed the Insecure kernel the StockMOD ROM thread provided and I still get the error.
5. I tried to restore from a backup I made last week on CWM, but it kept saying "checking MD5 files" and them giving me an error about not being able to restore.
As you all can see, I probably made a HUGE mess out of my phone and it might come as a huge surprise that I haven't bricked it completely. I'm extremely desperate at this point and I've admitted that I don't know what I'm doing. :crying:
It's come to the point where I just want a stable handset that will give me the services I want (GPS, mobile data, Wi-Fi, etc.) and I'm beginning to think this root lyfe isn't for me. I searched for guides on how to return to stock and unroot, but all the guides are different and I'm so confused and overwhelmed as to what I should do at this point. Please, please, please! A little guidance would be GREATLY appreciated!
Thanks for your time!
First off don't get disheartened. You did demonstrate a genuine attempt to help yourself and try your best on your own. Yes mistakes happen. We all do that. For what its worth, no one is born knowledgeable in these areas. We all learn.
Ok so what do we do next ? Lets start with a clean slate and put that all behind you. Yes your current recovery CWM is indeed dated and that's the reason for some of the issues you have.
Follow these steps.
1. Take UVDMD5 version of Root66 from here. Use ODIN to flash it to your phone. If you need a guide on how to use ODIN, read this thread carefully.
2. Once that Stock firmware has been updated and your phone boots fine, check if you have GPS and all the other features working to your satisfaction. Given your problems with GPS, I strongly recommend taking a GPS fix at this time.
3. Once that's working fine, flash the latest CWM Touch Recovery (version 6.0.4.5 for D2TMO). You can use Rom Manager from Play store.
4. Take a Nandroid before proceeding. When you do, uncheck the generate MD5 and enable Compression.
5. Now its your choice. You could flash Saranhai's Stock Mod or Danvdh's Dandroid. Both are good Roms and its your call. Check the GPS working after you flash Rom of your choice.
If you do choose to go after Saranhai's Rom and get into the Wi-Fi Problems, post here before you try any solutions. With Danvdh's Rom, there are certain steps to enable Root. You can't just flash SuperSU and hope to gain Root.
Perseus71 said:
First off don't get disheartened. You did demonstrate a genuine attempt to help yourself and try your best on your own. Yes mistakes happen. We all do that. For what its worth, no one is born knowledgeable in these areas. We all learn.
Ok so what do we do next ? Lets start with a clean slate and put that all behind you. Yes your current recovery CWM is indeed dated and that's the reason for some of the issues you have.
Follow these steps.
1. Take UVDMD5 version of Root66 from here. Use ODIN to flash it to your phone. If you need a guide on how to use ODIN, read this thread carefully.
2. Once that Stock firmware has been updated and your phone boots fine, check if you have GPS and all the other features working to your satisfaction. Given your problems with GPS, I strongly recommend taking a GPS fix at this time.
3. Once that's working fine, flash the latest CWM Touch Recovery (version 6.0.4.5 for D2TMO). You can use Rom Manager from Play store.
4. Take a Nandroid before proceeding. When you do, uncheck the generate MD5 and enable Compression.
5. Now its your choice. You could flash Saranhai's Stock Mod or Danvdh's Dandroid. Both are good Roms and its your call. Check the GPS working after you flash Rom of your choice.
If you do choose to go after Saranhai's Rom and get into the Wi-Fi Problems, post here before you try any solutions. With Danvdh's Rom, there are certain steps to enable Root. You can't just flash SuperSU and hope to gain Root.
Click to expand...
Click to collapse
Thanks so much for your detailed reply!
After a little bit of browsing the forum, I found that my IMEI seems to be missing and simply flashing the correct modems/kernels/whatever you call them does not fix it. I will go through your instructions and then report the results.
I read on here that sometimes it just happens randomly after flashing 4.3 ROMs? Well I certainly hope I get back my IMEI and hope it's not blacklisted :/ Apparently I can't access signal or data without it.
Thank you again!
EDIT: Does an "Unknown" IMEI mean I've totally lost it?
EDIT 2: Okay now I know God hates me. I downloaded the Root66 file and Odin will NOT let me flash it onto my phone. Keeps giving me aboot (???) errors no matter what port I use! I know I took a risk tinkering with my phone but I don't think I deserve this!
Honestly now I don't want anything to do with rooting and custom ROMs anymore. I think I'm too stupid for this. I think I just want it back to the way it was when I bought it. Could you please help me to do that?
I'm done with this root stuff, I can't do it anymore.
Sorry, I honestly don't mean to come off as whiny or ungrateful, I've just spent two days trying to figure this stuff out and it's getting me VERY tired and VERY irritated.
Oops I think I forgot to mention that you will have to put the phone in Download mode before you plug it in for ODIN. In order to get into Download mode you turn off the phone and press Volume Down AND HOME AND POWER simultaneously. If you are doing it for the first time, it may seem hard. Be patient.
Yes I suspected you to be "Missing IMEI". That's why suggested going to Stock. Your Call & Data problems come from there.
My steps do take you back to Stock.
So I've been happy for a couple of years with previous ROM. Installed Airdroid and it totally killed it. Just bootlooping now.
I'm going on a trip tomorrow and need the hotspot. Can anyone point me to a ROM that is stable and has the hotspot rolled into it. Data, and roaming required, working bluetooth would be good too. .
I've been reading for hours as usual (it's 3:30am and I'm running out of time), but am not sure the current state of the development of the ROMs for a phone this old.
syco123 said:
So I've been happy for a couple of years with previous ROM. Installed Airdroid and it totally killed it. Just bootlooping now.
I'm going on a trip tomorrow and need the hotspot. Can anyone point me to a ROM that is stable and has the hotspot rolled into it. Data, and roaming required, working bluetooth would be good too. .
I've been reading for hours as usual (it's 3:30am and I'm running out of time), but am not sure the current state of the development of the ROMs for a phone this old.
Click to expand...
Click to collapse
WickedX and Wicked S5, both have it. If you want AOSP, most if not all have it as well
Thank for the reply,
The one click update update to ND8 is hanging (odin not responding).
The original Blue Kuban Files I installed are 404 and the backups I had stored on my PC were lost when the PC died.
I don't need the latest greatest version of anything, I just need a working phone. Even the hotspot is optional at this point. I run my own business and the voicemails are backing up hence the ASAP request for help.
Any help anyone can give me to make this quick and easy would be appreciated. Thread lengths for these are now in the 1000s of pages so reading all isn't practical. Particularly when each page leads to another, and another, and another, which after a couple of hours of reading, then has dead file links.
syco123 said:
Thank for the reply,
The one click update update to ND8 is hanging (odin not responding).
The original Blue Kuban Files I installed are 404 and the backups I had stored on my PC were lost when the PC died.
Click to expand...
Click to collapse
I don't like using the one clicks, use regular Odin from here:
https://www.androidfilehost.com/?fid=23501681358547889
Make sure you download all the necessary files before you start this
Download NJ2 stock to update bootloader and modem from this thread: http://forum.xda-developers.com/showthread.php?p=58297282
Once it is flashed, Odin Philz Recovery from here:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.tar.md5
put it in the PDA or PA slot unchecked auto reboot, after flash pull battery and manually go into recovery.
Then from within Philz Recovery flash Wicked S5 from this thread:
http://forum.xda-developers.com/showthread.php?p=57728620
It says you need to be on ND8/NDC, but that is what you need as a minimum, NJ2 is newer than both of them.
NONE of these are my work, I just searched around for you to get you what you need, let me know if you need more help or have questions.
I did kind of dig myself out of the hole today and got Gummy installed. Had to update CWM and install following this page http://galaxys3root.com/galaxy-s3-roms/gummy-rom-for-galaxy-s3-4-4-4asop/ Tried open garden hotspot but Gummy kept crashing so was very glad to see your post.
mattzeller said:
I don't like using the one clicks, use regular Odin from here:
https://www.androidfilehost.com/?fid=23501681358547889
Make sure you download all the necessary files before you start this
Download NJ2 stock to update bootloader and modem from this thread: http://forum.xda-developers.com/showthread.php?p=58297282
Once it is flashed, Odin Philz Recovery from here:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.tar.md5
put it in the PDA or PA slot unchecked auto reboot, after flash pull battery and manually go into recovery.
Then from within Philz Recovery flash Wicked S5 from this thread:
http://forum.xda-developers.com/showthread.php?p=57728620
It says you need to be on ND8/NDC, but that is what you need as a minimum, NJ2 is newer than both of them.
NONE of these are my work, I just searched around for you to get you what you need, let me know if you need more help or have questions.
Click to expand...
Click to collapse
Followed your awesome instructions. This message coming to you via the hotspot on the Wicked ROM.
Thank you mattzeller, you Sir are a gentleman!
Glad I could help get you back up and running. Remember DO NOT try to flash any lower bootloaders via any flavor of Odin, if you will brick your device. You can flash any ROM you like, be it a JB, KK, or LP as they do not contain bootloader.
Hello. When my device was updated to KitKat, the WiFi stopped turning on. It doesn't fail to connect, it just will not turn on at all. I tried an app called "WiFi Fixer", which didn't work, but in the "Known Issues" section it said this was caused by the "Android framework not interacting with the WiFi driver" and said to flash a custom ROM.
I rooted, installed TWRP, and flashed CM 12.1 successfully. The WiFi still wouldn't turn on. I then decided it was probably a hardware issue that coincidentally showed itself at the same time as the update. So then, I installed Cheetah Mobile launcher, and one of their themes, and was resigned to not having WiFi.
I got bored with the CM theme, and installed the Dark Material theme. At this point the phone started acting buggy, not waking from wakelock, force closing, and randomly rebooting. So i then deleted cache and dalvick cache, and re-flashed from the CM 12.1 zip i had saved on my SD. The bugs would not stop, almost making my phone unusable. The only bright side of this was that my WiFi was turning on and working! I thought maybe the hardware problem had fixed itself somehow, but I still wanted to have a usable phone. I kept re-flashing from the existing CM 12.1 zip, the WiFi kept working, but the buggy behavior wouldn't go away.
I figured that maybe the CM 12.1 zip on my SD was corrupted, so I downloaded another copy from CyanogenMod, installed it on my SD, and erased the old copy. Then, I wiped everything and re-flashed with the new zip. The buggy behavior went away, but WiFi stopped working again! I'm thoroughly confused now.
If it's a hardware issue, why does it come and go with ROMs/ themes? I thought it may be a kernel issue, so I flashed Ktoonsez K747 kernel, which is working fine, but I still don't have WiFi. Did the themes I installed earlier change the kernel in some way to make my WiFi work temporarily? Is there a fix for this? Is it a known problem? I researched the forums but the only answers I found for similar problems were from earlier versions (2013) of Android/ CyanogenMod ROMs.
At this point, I'm willing to give anything a try, I've even opened the phone, inspected, un-plugged, and replugged the WiFi antenna. If it was a hardware issue, would I expect to see any damage, like a fried circuit or something? Is there any test to check if it's hardware vs. software?Can I buy a replacement antenna?
I'm pretty broke and can't afford a new phone, which is why I'm trying to resuscitate this one When it works, it's sufficient for my use.
Please help, I really want WiFi back! Thanks in advance for any advice.
Full odin back to stock. Best solution.
Get odin here at the bottom of the page. The firmware is there too. If you create a free account the download goes much faster.
Also, re flashing the same cm12.1 over and over won't help. Have you tried the newest nightly? After odin back to stock, if you want cm, use the latest.
If you don't have a pc, you can try flashfire, but I haven't tried it.
madbat99 said:
Full odin back to stock. Best solution.
Get odin... at the bottom of the page. The firmware is there too. If you create a free account the download goes much faster.
Also, re flashing the same cm12.1 over and over won't help. Have you tried the newest nightly? After odin back to stock, if you want cm, use the latest.
If you don't have a pc, you can try flashfire, but I haven't tried it.
Click to expand...
Click to collapse
Thanks, I'm downloading it now. Does it matter that this is an older build? I started with L710VPUDOH1, but this download is a previous version, L710VPUDNJ2.
I found this, which has the L710VPUDOH1 build in a zip...
Google > "L710VPUDOH1 opensource samsung" > first result (I'm too new on XDA to post outside links!)
within the zip is Kernel.tar and Platform. tar. which I have done nothing with, as I'm not sure if it's what I need. Do you think I should flash these? or just go with the NJ2 build?
Thank you for your insight, and taking the time to help me!
dieseldeeznutz said:
Thanks, I'm downloading it now. Does it matter that this is an older build? I started with L710VPUDOH1, but this download is a previous version, L710VPUDNJ2.
I found this, which has the L710VPUDOH1 build in a zip...
Google > "L710VPUDOH1 opensource samsung" > first result (I'm too new on XDA to post outside links!)
within the zip is Kernel.tar and Platform. tar. which I have done nothing with, as I'm not sure if it's what I need. Do you think I should flash these? or just go with the NJ2 build?
Thank you for your insight, and taking the time to help me!
Click to expand...
Click to collapse
No. For many reasons. First, its not the rom, its just the update. No one has made a flashable rom zip. Second, official updates won't flash in custom recovery and it would never flash because you're rooted.
So basically its not the full rom, its the official update zip, just a patch.
Gotta flash a .tar. Unless your on the triband model, nj2 should be fine
madbat99 said:
No. For many reasons. First, its not the rom, its just the update. No one has made a flashable rom zip. Second, official updates won't flash in custom recovery and it would never flash because you're rooted.
So basically its not the full rom, its the official update zip, just a patch.
Gotta flash a .tar. Unless your on the triband model, nj2 should be fine
Click to expand...
Click to collapse
Flashed back to stock, and updated to OH1 successfully, but still no wifi. It's greyed out and won't turn on
I would think it was a hardware problem, except that it all started when my phone updated to 4.4.2. I've found many others with this problem online, but no fixes. Can I flash back to 4.3? or can I flash a new modem/radio(?) file. I thought I saw one in my searches but can't seem to find it now
Thanks again
dieseldeeznutz said:
Flashed back to stock, and updated to OH1 successfully, but still no wifi. It's greyed out and won't turn on
I would think it was a hardware problem, except that it all started when my phone updated to 4.4.2. I've found many others with this problem online, but no fixes. Can I flash back to 4.3? or can I flash a new modem/radio(?) file. I thought I saw one in my searches but can't seem to find it now
Thanks again
Click to expand...
Click to collapse
No, do not try to flash 4.3. You will hard brick, and your phone will be a paperweight. Same thing if you try flashing any pre Knox modems/radios.
Are you flashing something else with this? It's something on your device if a tar flash in odin didn't fix it. Did you factory reset after odin?
madbat99 said:
No, do not try to flash 4.3. You will hard brick, and your phone will be a paperweight. Same thing if you try flashing any pre Knox modems/radios.
Are you flashing something else with this? It's something on your device if a tar flash in odin didn't fix it. Did you factory reset after odin?
Click to expand...
Click to collapse
Yes, I factory reset, cleared all caches, rebooted into safe mode, changed wifi settings in service mode... did an ancient Indian wifi fixing dance, spoke soothingly to it, then cursed at it :laugh: maybe it's a hardware problem with coincidental timing that's also happened the same exact way to other people
dieseldeeznutz said:
Yes, I factory reset, cleared all caches, rebooted into safe mode, changed wifi settings in service mode... did an ancient Indian wifi fixing dance, spoke soothingly to it, then cursed at it :laugh: maybe it's a hardware problem with coincidental timing that's also happened the same exact way to other people
Click to expand...
Click to collapse
Lmao, funny. I heard it happening to people a while back. Can't remember what caused or fixed it. Some fixed it with custom kernel but the kernel is waaay outdated now. But it was kt747 by ktoonsez. But its so old. What carrier are you on? Sprint, virgin Mobile, boost?
madbat99 said:
Lmao, funny. I heard it happening to people a while back. Can't remember what caused or fixed it. Some fixed it with custom kernel but the kernel is waaay outdated now. But it was kt747 by ktoonsez. But its so old. What carrier are you on? Sprint, virgin Mobile, boost?
Click to expand...
Click to collapse
I'm on Sprint.
this just happended to me the other night actually, did you find solution? Apparently just taking out the battery and resetting solved it for a lot of people, but not me. I will tell you what did work though! (keeps randomly doing it again but at least i can gfet it to work aghain even if only for a littlw bit)
First check with root explorer if you have this fike "data\misc\wifi\wpa_supplicant.conf "
I guess it has something to do withthis file, and your android not writing to the right spot, but i honestly have no idea so ill continue. what i did (i saw i didnt have the file either) i dialed *#0011# then hit menu, and then hit wifi, and turned off the bottom switch "wifi power save mode". I exited service menu tried wifi a couple times still same thing, so i went back into service menu and reenabled the switch, then i turned off the phone by pulliung out battery. I logged into my custom recovery and checked out the file explorer in twrp, and voila there that mysery file was! So i cleared dalvick and cache, rebooted into rom, (wicked x v8.2) and attempted wifi and it was working again. so take whatever conclusion youd like but im too tired to keep my eyes open at the moment and good luck, pissed me off cuz wifi was all i had no service, of course
skinnykinney said:
this just happended to me the other night actually, did you find solution? Apparently just taking out the battery and resetting solved it for a lot of people, but not me. I will tell you what did work though! (keeps randomly doing it again but at least i can gfet it to work aghain even if only for a littlw bit)
First check with root explorer if you have this fike "data\misc\wifi\wpa_supplicant.conf "
I guess it has something to do withthis file, and your android not writing to the right spot, but i honestly have no idea so ill continue. what i did (i saw i didnt have the file either) i dialed *#0011# then hit menu, and then hit wifi, and turned off the bottom switch "wifi power save mode". I exited service menu tried wifi a couple times still same thing, so i went back into service menu and reenabled the switch, then i turned off the phone by pulliung out battery. I logged into my custom recovery and checked out the file explorer in twrp, and voila there that mysery file was! So i cleared dalvick and cache, rebooted into rom, (wicked x v8.2) and attempted wifi and it was working again. so take whatever conclusion youd like but im too tired to keep my eyes open at the moment and good luck, pissed me off cuz wifi was all i had no service, of course
Click to expand...
Click to collapse
I have that file on my phone. So I understand, you originally didn't have that file, but after doing the steps you listed it magically appears, and then wifi works? I really wish I could get it to work. Also, you said it keeps happening... so the file keeps dissappearing on you? Thanks for the response.
USE THIS IF YOU WANT TO USE DR.KETAN COMPLETELY ON SPRINT NETWORK
I got the rom working on my N910P here are the EXACT steps and links to files i used.
1) Make sure you are on OK1 bootloader: I flashed BOTH the baseband and the Firmware.tar with ODIN
Failure to flash both could lead to WIFI not turning on and Camera not focusing
provided here: http://forum.xda-developers.com/note-4-sprint/development/basebandsbootloaders-ok1-pc1-pb5-t3358357 BIG THANKS TO @freeza
2) Flash the M5 rom
Provided here: http://forum.xda-developers.com/note-4/snapdragon-dev/n910g-dr-ketan-custom-rom-t2928568 another big thanks to @dr.ketan for the great rom!
3)Flash just the H-Vitamin Kernel alone not the MM5 fix or anything just the kernel
Provided Here: http://galaxynote4root.com/t-mobile-note-4-roms/how-to-convert-galaxy-note-4-into-galaxy-s7-edge/2/
Special Thanks to @zedomax! He also has a good video on this if you want to follow there, just use the files I give you rather than the ones he does!
3) Flash the Verizon data fix V2 ( located in attached files under first paragraph). I know you want the phone to work on sprint but for some reason this lead to me getting the rom to work.
provided here: http://forum.xda-developers.com/note-4/snapdragon-dev/marshmallow-6-0-1-ports-data-fixes-t3379978 Thank you @louforgiveno
4) Flash SuperUser I used beta 2.74
provided here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
@chainfire thank you!
5) Boot the phone and set up APN. You don't have to speed through set up, I went ahead and did a full restore before doing all of this.
Name-Whatever you want
APN-n.ispsn
MMSC-http://mms.sprintpcs.com
Multimedia message proxy- 68.28.31.7
Multimedia message port- 80
MCC-310
MNC-120
everything else leave as is go ahead and save.
6)Set Network Mode to LTE/CDMA then go ahead and try to test SMS and MMS
if it doesn't work boot to recovery and go to next step. It didn't work for me but hey you guys might get lucky.
*Note that stock messages app may not work, in my case if i went to attach a file the app crashed so every time so i continued on with Google Messenger*
7)Flash this fix: http://forum.xda-developers.com/note-4-sprint/development/steps-to-install-dr-ketans-rom-g-t3379659/post67086423#post67086423
Thank you @KLPFL
I'm not sure if this fix overwrites what the Verizon V2 fix does, or if its the same thing but like i said these are the steps and files that worked for me!
8)Reboot phone go to settings make sure network is LTE/CDMA, check and make sure APN is set right, now try texting if nothing happens turn off mobile data for a minute. Turn it back on and you should be good to go with sending SMS and MMS (calling and receiving and data work)
Took me a week to figure out all the files and all the fixes to use! I don't take credit for any of the files or fixes or rom I simply got things to work!
@redxblood85 Check your Inbox.
redxblood85 said:
USE THIS IF YOU WANT TO USE DR.KETAN COMPLETELY ON SPRINT NETWORK
I got the rom working on my N910P here are the EXACT steps and links to files i used.
1) Make sure you are on OK1 bootloader: I flashed BOTH the baseband and the Firmware.tar with ODIN
Failure to flash both could lead to WIFI not turning on and Camera not focusing
provided here: http://forum.xda-developers.com/note-4-sprint/development/basebandsbootloaders-ok1-pc1-pb5-t3358357 BIG THANKS TO @freeza
2) Flash the M5 rom
Provided here: http://forum.xda-developers.com/note-4/snapdragon-dev/n910g-dr-ketan-custom-rom-t2928568 another big thanks to @dr.ketan for the great rom!
3)Flash just the H-Vitamin Kernel alone not the MM5 fix or anything just the kernel
Provided Here: http://galaxynote4root.com/t-mobile-note-4-roms/how-to-convert-galaxy-note-4-into-galaxy-s7-edge/2/
Special Thanks to @zedomax! He also has a good video on this if you want to follow there, just use the files I give you rather than the ones he does!
3) Flash the Verizon data fix V2 ( located in attached files under first paragraph). I know you want the phone to work on sprint but for some reason this lead to me getting the rom to work.
provided here: http://forum.xda-developers.com/note-4/snapdragon-dev/marshmallow-6-0-1-ports-data-fixes-t3379978 Thank you @louforgiveno
4) Flash SuperUser I used beta 2.74
provided here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
@chainfire thank you!
5) Boot the phone and set up APN. You don't have to speed through set up, I went ahead and did a full restore before doing all of this.
Name-Whatever you want
APN-n.ispsn
MMSC-http://mms.sprintpcs.com
Multimedia message proxy- 68.28.31.7
Multimedia message port- 80
MCC-310
MNC-120
everything else leave as is go ahead and save.
6)Set Network Mode to LTE/CDMA then go ahead and try to test SMS and MMS
if it doesn't work boot to recovery and go to next step. It didn't work for me but hey you guys might get lucky.
*Note that stock messages app may not work, in my case if i went to attach a file the app crashed so every time so i continued on with Google Messenger*
7)Flash this fix: http://forum.xda-developers.com/note-4-sprint/development/steps-to-install-dr-ketans-rom-g-t3379659/post67086423#post67086423
Thank you @KLPFL
I'm not sure if this fix overwrites what the Verizon V2 fix does, or if its the same thing but like i said these are the steps and files that worked for me!
8)Reboot phone go to settings make sure network is LTE/CDMA, check and make sure APN is set right, now try texting if nothing happens turn off mobile data for a minute. Turn it back on and you should be good to go with sending SMS and MMS (calling and receiving and data work)
Took me a week to figure out all the files and all the fixes to use! I don't take credit for any of the files or fixes or rom I simply got things to work!
Click to expand...
Click to collapse
i m already on stock PE1 .... is it necessary to go back to lollipop OK1 and then again move upwards?
n70shan said:
i m already on stock PE1 .... is it necessary to go back to lollipop OK1 and then again move upwards?
Click to expand...
Click to collapse
Yeah you gotta be on OK1, any marshmallow bootloader will cause the phone to not boot. Once it's set you can try flashing back to PE1. I ran the rom with Beast mode kernel, and PC1 and it worked once it was set up. But yeah for initial set up you need to be on OK1
hey red, I did the install the way you have it set, but after I installed everything and let it boot, I cant access the settings portion? It just says unfortunately settings has stopped? and there is no way to access through the apps launcher because its not there? Where did I go wrong? I started from fresh OK1 as well.
divineazn716 said:
hey red, I did the install the way you have it set, but after I installed everything and let it boot, I cant access the settings portion? It just says unfortunately settings has stopped? and there is no way to access through the apps launcher because its not there? Where did I go wrong? I started from fresh OK1 as well.
Click to expand...
Click to collapse
I've never heard of that happening. I would try reflashing the rom and kernel then letting that boot alone. If that boots then go back and flash the fix. Also just to make sure, wipe your data, cache, system, and dalvik before flashing everything
Hey red, sorry for the late reply, I just got out of work, but to update you on my issue, I went to ok1 stock it I didn't wipe data and cache stuff etc. I finally received did it and I have phone calls and data. When I sms it takes forever to send, like 7 minutes to be exact, I know this by texting my wife and seeing how long it takes. It does eventually send the text, but also I tried to send mms and that does NOT send? I'm not sure why? I did the mobile setup the way you said in the beginning. Then I had to flash the mod afterwards because I was not able to send sms. Afterwards I decided to turn off mobile data for a minute to see if it helped but it was the same. I also tried turning mobile data off and rebooting and turned it back on but still no luck. Is there anything else you suggest I try? I greatly appreciate your work!
divineazn716 said:
Hey red, sorry for the late reply, I just got out of work, but to update you on my issue, I went to ok1 stock it I didn't wipe data and cache stuff etc. I finally received did it and I have phone calls and data. When I sms it takes forever to send, like 7 minutes to be exact, I know this by texting my wife and seeing how long it takes. It does eventually send the text, but also I tried to send mms and that does NOT send? I'm not sure why? I did the mobile setup the way you said in the beginning. Then I had to flash the mod afterwards because I was not able to send sms. Afterwards I decided to turn off mobile data for a minute to see if it helped but it was the same. I also tried turning mobile data off and rebooting and turned it back on but still no luck. Is there anything else you suggest I try? I greatly appreciate your work!
Click to expand...
Click to collapse
are you using the stock messaging app? If so then try a third party like google messenger. For OK1 did you flash both baseband and firmware? Also are you using KLPFL data fix for the second fix flash?
Yes I tried the stock and then I downloaded the Google messenger app. Was Dr kreton rom suppose to already have the Google messenger? Yes I flashed ok1 full. I didn't do it separately, I have a tar file from back then to flash it full. Should all this information be correct?
redxblood85 said:
Yeah you gotta be on OK1, any marshmallow bootloader will cause the phone to not boot. Once it's set you can try flashing back to PE1. I ran the rom with Beast mode kernel, and PC1 and it worked once it was set up. But yeah for initial set up you need to be on OK1
Click to expand...
Click to collapse
ok i was on 6.0.1 PE1 and then i turned off my phone and flashed OK1 baseband and firmware then i flashed twrp recovery and then this rom etc but my phone is not booting up it is stuck at samsung logo... now what?
n70shan said:
ok i wan on 6.0.1 PE1 and then i turned off my phone and flashed OK1 baseband and firmware then i flashed twrp recovery and then this rom etc but my phone is not booting up it is stuck at samsung logo... now what?
Click to expand...
Click to collapse
Hey I ran into that problem too, after you went back to the OK1, did you wipe as stated before you flashed the rom? make sure you wipe first or else you'll have problems.
divineazn716 said:
Hey I ran into that problem too, after you went back to the OK1, did you wipe as stated before you flashed the rom? make sure you wipe first or else you'll have problems.
Click to expand...
Click to collapse
yes when i installed twrp i first wiped system, data, cache etc and then installed rom but my phone is stuck at samsung... now what should i do? i have to odin back PE1 to make my phone alive for now
n70shan said:
yes when i installed twrp i first wiped system, data, cache etc and then installed rom but my phone is stuck at samsung... now what should i do? i have to odin back PE1 to make my phone alive for now
Click to expand...
Click to collapse
Did you try to ODIN OK1 again? after you ODIN OK1 again let it run and see if it boots up with stock OK1. If it doesnt and it keeps bootlooping try going to wipe the usual and THEN ODIN OK1. I had to try so many things to figure it out, isnt it fun? lol even though it takes up hours of your day.... =/
n70shan said:
yes when i installed twrp i first wiped system, data, cache etc and then installed rom but my phone is stuck at samsung... now what should i do? i have to odin back PE1 to make my phone alive for now
Click to expand...
Click to collapse
i think this is issue with downgrading from PE1 to OK1 but on contrary they are saying this is how it works... i m confused now... @dr.ketan can confirm
---------- Post added at 05:51 PM ---------- Previous post was at 05:25 PM ----------
divineazn716 said:
Did you try to ODIN OK1 again? after you ODIN OK1 again let it run and see if it boots up with stock OK1. If it doesnt and it keeps bootlooping try going to wipe the usual and THEN ODIN OK1. I had to try so many things to figure it out, isnt it fun? lol even though it takes up hours of your day.... =/
Click to expand...
Click to collapse
ok i tried again to wipe everything then flash rom , kernel , fixes and then powered off my phone and flashed OK1 baseband and firmware but still stuck at samsung logo, nothing is working
FYI.... Sprint N4 User(s): You need to be in OK1 or older BL/FW (LP). You can't be on MM BL/FW it will give you bootloop. You can Odin the BL/FW (getting from Freeza in Dev Thread).
1. Wipe everything Except Internal & External SD
2. Flash Rom
3. Flash Data Fix ( Verizon V2 - One I posted which I edited the APN - (All credit go LouForgiveNo)) Don't ask me but that is the only thing I found to work perfectly for our Sprint Phone
4. Flash Kernel ( Vitamin-H, AEL 10.3 (somehow is not really stable), Nameless MM (in N4 Snapdragon thread under the rom, 2 post), Freeza Beasmode (lost Wifi))
5. Do you Normal Setup
6. After complete go to Setting -> Mobile Network -> Network Mode ( Select LTE/CMDA (MUST). Then Access Point Names and select LTE - SPRINT test IPS (last one on the list)
7. Reboot.. Test mms and sms by sending it to yourself. It will take a little bit to go but once it go, it will work find afterward
8. Option - The network has as Roaming Indicator Off... If you want to say Sprint, You would need to flash eri.xml file ( I found this on the web, I only edit to match Sprint. I'm not taking any credit on this.. don't remember who credit too).. User @JWnSC is the one who found the fix.
n70shan said:
yes when i installed twrp i first wiped system, data, cache etc and then installed rom but my phone is stuck at samsung... now what should i do? i have to odin back PE1 to make my phone alive for now
Click to expand...
Click to collapse
Okay try flashing stock OK1, let it get to initial set up screen. Then flash twrp, wipe dalvik, system, data, and cache, then flash the rom, kernel, verizon v2 fix. See if it boots.
Ok I got it all working. These are the steps I took.
Odin ok1 if you haven't and let it boot up so you know it's working
Next after you have twrp installed,
Wipe everything except internal and external so
I wiped 3 times and then factory reset 3 times. Sorry just a habit.
Next I installed the Dr kreton rom
Next I installed the @KLPFL mod data fix he adjusted.
Next I installed vitamin h
Then I rebooted.
I didn't install supersu yet like @KLPFL directed.
I let it boot and put in the information.
When the Dr kreton window fix popped up I just ignored it for now and went to do what @KLPFL said and made sure his access points that he created at the bottom was clicked.
Then made sure to change from global to the Lte/CDMA.
Then I rebooted after the searching lte/CDMA popped up briefly.
After it rebooted I tested everything and it worked fine. Thank you guys for us support!
Oh yea I installed supersu after I made sure everything was connected and then installed Dr kreton fix.
divineazn716 said:
Ok I got it all working. These are the steps I took.
Odin ok1 if you haven't and let it boot up so you know it's working
Next after you have twrp installed,
Wipe everything except internal and external so
I wiped 3 times and then factory reset 3 times. Sorry just a habit.
Next I installed the Dr kreton rom
Next I installed the @KLPFL mod data fix he adjusted.
Next I installed vitamin h
Then I rebooted.
I didn't install supersu yet like @KLPFL directed.
I let it boot and put in the information.
When the Dr kreton window fix popped up I just ignored it for now and went to do what @KLPFL said and made sure his access points that he created at the bottom was clicked.
Then made sure to change from global to the Lte/CDMA.
Then I rebooted after the searching lte/CDMA popped up briefly.
After it rebooted I tested everything and it worked fine. Thank you guys for us support!
Oh yea I installed supersu after I made sure everything was connected and then installed Dr kreton fix.
Click to expand...
Click to collapse
Glad you got it to work.. The only reason I said flash supersu is because sometime you don't get root and you can't apply the fix on your initial bootup.
Hello, anyone using this rom on sprint?
http://forum.xda-developers.com/showthread.php?t=3374171
Sent from my SM-N920P using XDA-Developers mobile app
KLPFL said:
FYI.... Sprint N4 User(s): ...
6. After complete go to Setting -> Mobile Network -> Network Mode ( Select LTE/CMDA (MUST). Then Access Point Names and select LTE - SPRINT test IPS (last one on the list)
Click to expand...
Click to collapse
I followed the instructions in the OP and reference your procedure here. Everything seems to be working, except I cannot get mobile data. I don't see the APN "LTE - SPRINT test IPS".
I do see the APN I configured from Step 5 in the OP.
Could I have missed something obvious? On OK1 bl and fw.
Thanks!
mike
Greetings,
I really don't want this to be a repeat post, so I have spent many days now searching for this answer, not just here on XDA if I was honest, I have links to prove it
The aim is to give a little new life to my old phone, and get off the 4.1 build it is on.
With that said, in summary, I have tried a few different custom ROMs; Cyanogenmod 11 - 13, stable to nightly. PAC MAN ROM for Lollipop, some other roms for KitKat I found else where, but in all these I have not been able to get 4G to work. I understand about updating the Modem, and got the latest version from DocHoliday77's post for the Galaxy S3, in point of fact I tried every modem version for 4.3+ on there
But for all this, and it's been time consuming I never managed to actually get 4G to work as stated
I tried playing with settings in Test Mode (*#*#4636#*#*), changed preferred settings, added APN's, rebooting during certain phases of the moon ... but somehow it all avails me diddly.
Finally I have genuinely tried searching for info on if this just isn't going to happen and that's how it is, but somehow I found lots of posts about other models or networks that made it work more than something saying this won't work (putting aside the info on CM 11 that states it's a known issue and won't work on some build I forget).
Which leads me to this post: I wondered if anyone could point me in either the direction of a 4.4+ custom ROM or other ROM, compatible for SGH-T999 (T-Mobile Galaxy S3), that has working 4G. Or how I can get 4G to work on one of the ROMs I have already tried, kind of partial to a nice CM but I am willing to venture.
Also happy to just hear other input about giving new life to the phone so any feedback welcome
Thanks for your time!
NOTES
======
Using TWRP 3.x for flashing
Phone is rooted
IMEI is visible & fine on custom ROM
4G works on stock ROM
not experienced at this but willing to read
Edit: something I had not noticed before, I install Gapps for most of my tests but never use it. I just tried to download from Play Store, it acts as though I have no connection; waiting to download appears, then eventually it says waiting for network. Yet I am able to browse the net fine with the phone floating between 3G & H+. I don't know if that might help, so figured I should add it.
Is the phone running the latest bootloader and modem? Maybe both are needed to properly get 4g on all Roms?
audit13 said:
Is the phone running the latest bootloader and modem? Maybe both are needed to properly get 4g on all Roms?
Click to expand...
Click to collapse
That's a really good question, let me see if I can find out how to get my bootloader info and I'll get back to you.
May I ask what the latest bootlader is for the SGH-T999, or where I could find this so I can compare it? I couldn't seem to find it, though the most resourceful post I did find related was T999 UVDMD5 Firmware / Bootloader by mnasledov, though it is also a little outdated it appears, I haven't read my entire way through it yet sorry, I also know the phone is a little outdated too .
So that wasn't too bad to find out
I don't have the latest bootloader if that should match the baseband I install.
Where after a ROM install I get my baseband to T999UVUEOH1, but the bootloader stays on T999UVDLJA.
I haven't quite found where to get the latest bootloader just yet, though I did really spend the last few minutes discovering about the bootloader; if you or someone could find the time to point me in that direction that would be awesome
Simplest way to make sure you have the latest would be to flash the most recent stock rom from sammobile.com in Odin.
Thank you very much @audit13, I do appreciate the time you took out to help me and I also appreciate the point in the direction of what next.
I'll go dig into that for a while and see what to do to be sure, before I start
Looks like this is the latest one, so I will give this a shot : PDA T999UVUEOH1 & CSC T999TMBEOH1, version 4.3.
So just as a quick question, since I've never upgraded the bootloader in this fashion etc., from what I have read this is a one way street correct? And since I am upgrading to stock, then I guess will I lose root, which I will have to go back down the path of for a reinstall, or could I flash my old back up over this from TWRP and in that fashion have the latest bootloader, but keep everything I have for the moment as I investigate a ROM that will offer 4G.
I guess what I am getting at is even if having the latest bootloader and some other ROM with the latest baseband doesn't give me 4G still, can I go back in terms of the OS version to my 4.1.1 and keep things as is with a newer bootloader?
I will investigate this myself too, I just always preferred some additional input when discovering things where possible.
I do appreciate your time, thanks again!
No, you cannot run stock 4.1.1 on a 4.3 bootloader unless it is a custom 4.1.1 rom based on a stock touch wiz rom.
I do not think it is a problem to run the latest bootloader and modem as the latest custom ROMs often require an updated bootloader and modem.
Once on a 4.3 bootloader, you can't downgrade to something older.
Thanks again @audit13, that matches what I have read, I appreciate the confirmation!
Looks like I will be undergoing a re-root etc. so I'll get my information together, have a little more read, see what I need to back up and then jump down the rabbit hole
I'm grateful for your time and help.
If you decide to run a custom rom, just flash a stock rom, then immediately flash twrp via Odin, then install the rom and gapps. No need to root before hand.
Ahh ok, that would have made the most sense. However I didn't have an opportunity to check back on this thread until now so even though you had awesome speedy reply I missed it.
I did manager to successfully flash the stock ROM from Sam's. It did also update the bootloader so THANK YOU very much for that.
I had to fiddle a little to get Odin to recognize the my Galaxy S3 in the end it was simple: after I installed Kies to get the drivers on, I disabled WI-Fi (I use it for my dev work, and then it didn't try to spend time getting other drivers and it all went great. But that's just a note incase maybe one day someone else reads the thread and wonders how, this might help.
I'm just actually restoring a couple f things on the stock ROM, I figured I would have it ready in the event a custom ROM doesn't suit immediately, as I find one I like, then I have a back up of the stock ROM on 4.3 to revert to. Incidentally I just used TWRP manager from Google play store to install TWRP, hopefully it's the same as the flash, except now I know I rooted when I didn't have to
@audit13 Thanks, I know I keep saying that but I appreciate your time the same way I would hope someone else appreciated mine.
Incidentally once ready I will post an update here about the success of getting 4G on Cyanogenmod 12 or even 13 maybe, or someone of the other custom ROM I try, to share that info.
So just an update, I can confirm even with both an updated bootloader and matching updated baseband there is still no 4G on Lollipop Cyanogenmod 12, haven't quite tried any other yet, that was the one I liked the most but I will carry on and get a list as I have time then update here.
If there are any further suggestions I'm all open to them
Thanks [email protected]
Do you get 4G on a stock ROM? You have an LTE capabale sim? You get 4G on another phone with the same sim card?
Right, this SIM gets 4G on 2 other phones it's been in, on this phone on stock ROM it gets 4G too. Reverting back to stock backup in TWRP, from CM12 looks like it tripped knox I think it is, so now the warranty bit is 1 oops. But I managed to Odin back to 4.3 stock, so now I also need to see if I can try to flash maybe to CM 11, which is 4.4.x, or if maybe I'm stuck here. If I can find out I certainly will update the result of 4G testing.
You've been really patient & helpful thanks!
First let me say I'm a noob. I've rooted and jailbroken devices but I admit it's all from falling instructions. I rooted my s3 a while ago and installed twrp 1.0.8.7 yesterday. I did a full wipe including system and all catches and installed the latest nightly of cm13. Everything is running great. I don't know if this helps but maybe it's your process. Good luck!
Sent from my Amazon Jem using Tapatalk
Shack70 said:
First let me say I'm a noob. I've rooted and jailbroken devices but I admit it's all from falling instructions. I rooted my s3 a while ago and installed twrp 1.0.8.7 yesterday. I did a full wipe including system and all catches and installed the latest nightly of cm13. Everything is running great. I don't know if this helps but maybe it's your process. Good luck!
Sent from my Amazon Jem using Tapatalk
Click to expand...
Click to collapse
That's really helpful thanks @Shack70, since updating to 4.3 I have only tried CM 12, I can certainly give 13 a shot, & you have 4G working then please?
incidentally I have actually recorded every step I performed, in the event I repeat this again or I had to explain it. But my process maybe at fault I agree; I rooted my phone with towelroot. Installed TWERP manager (3.0.2 something, maybe I should try 1.0.8?), rebooted into recovery & first thing was take a full backup on stock. Then I did a factory wipe, & advanced wipe. Then installed the ROM, wiped dalvik/cache. Installed Apps, wipe dalvik/cache, reboot
Hopefully that's not too much? I just wonder if any of those steps raise alarm?
Edit: mind if I throw a few questions on here at you please @Shack70?
what do you wipe from the options please?
after the install, do you run any other wipes please?
how did you get TWRP on your phone? Not sure if that or version matters but I'm willing to try
Morrigon said:
That's really helpful thanks @Shack70, since updating to 4.3 I have only tried CM 12, I can certainly give 13 a shot, & you have 4G working then please?
incidentally I have actually recorded every step I performed, in the event I repeat this again or I had to explain it. But my process maybe at fault I agree; I rooted my phone with towelroot. Installed TWERP manager (3.0.2 something, maybe I should try 1.0.8?), rebooted into recovery & first thing was take a full backup on stock. Then I did a factory wipe, & advanced wipe. Then installed the ROM, wiped dalvik/cache. Installed Apps, wipe dalvik/cache, reboot
Hopefully that's not too much? I just wonder if any of those steps raise alarm?
Edit: mind if I throw a few questions on here at you please @Shack70?
what do you wipe from the options please?
after the install, do you run any other wipes please?
how did you get TWRP on your phone? Not sure if that or version matters but I'm willing to try
Click to expand...
Click to collapse
In twrp I wiped system and all caches before installing the rom and gapps. I installed an older version of twrp using Odin and updated it to 2.0.8.7 using the twrp app in the play store. Yes I have 4g/lte. I've seen it switch from lte to h+ to 3g depending on my location so I'm sure it's working correctly. The camera and Bluetooth also work fine. I hope this helps, I'm still learning and most of what I've done is just by following others instructions here at XDA.
Sent from my Amazon Jem using Tapatalk
I definitely appreciate the reply thanks!
I gave the latest nightly CM 13 a shot just now, 7/31/16 version essentially. Not finding any issues with the ROM, can't get 4G to show up no matter what though , even with changes and attempts to APN settings etc. None the less maybe to give my phone a rest I'll just stick with this a while and decide if a newer nightly comes out I want to try, or better yet a stable version at some point. Then I can verify how much I really miss my 4G I guess.
All the previous attempts, including this one always results in 3G to H+ network with no issue, it's just that 4G that never shows up for me.
Incidentally without a serious search around I couldn't even find TWRP 2.0.8.7, it's not on the TWRP manager version I have so curious, I ended up just going with 2.8.0.7, thinking maybe it was a typo?
Otherwise I basically run the same type of install you mention, I also clean dalvik, cache, system & data in my case. Just to confirm that.
I have a slightly off topic question here, if I decide to go back to to stock I was wondering, if i went from UVUEOH1 4.3 JB build, to the previous UVUENC2 4.3 JB build; because I've seen this available as a clean route 66 version, is this still considered a downgrade and a bad idea? I'd be flashing with Odin from @DocHoliday77 post here.
@Shack70, thanks for the input, thanks for the guide on your steps, glad I've confirmed I'm doing the same even if I can't get my 4G, hopefully someone on a Galaxy S3 T-Mobile, went through this found a solution, and maybe will let me know what they did too, not sure if you are on T-Mobile or not.
@audit13, also thanks, you've been replying plenty too and I appreciate that also!
One small thing I just came across looking over the logs of the install.
When flashing CM 13 with TWRP, I noticed it said the Target: samsung/d2tmo/d2tmo:4.3/JSS15J/T999UVUEMJC:user/release-keys.
Is it normal and OK for it the be referencing a different baseband/bootloader than what I actually have on my phone?
UVUEMJC vs the UVUEOH1? Where the one as named by TWRP flash is 2 versions older than what I have installed? Not necessarily stating this is an issue, just asking please if this is normal, and I also understand it could be something I have overlooked in my reading, it's been a lot of reading
I would not worry about the referenced baseband as flashing CM13 does not change the bootloader or baseband during the flash process.
audit13 said:
I would not worry about the referenced baseband as flashing CM13 does not change the bootloader or baseband during the flash process.
Click to expand...
Click to collapse
That makes sense thanks @audit13, just a few of the questions I had building up.
So that my previous question doesn't get lost, and although I know it's a dying phone for users hopefully this might get some visual
if I decide to go back to to stock I was wondering, if i went from UVUEOH1 4.3 JB build, to the previous UVUENC2 4.3 JB build; because I've seen this available as a clean route 66 version, is this still considered a downgrade and a bad idea? I'd be flashing with Odin from @DocHoliday77 post here.
Click to expand...
Click to collapse