Related
So I'm not sure what's going on, but when trying to click "software update" in ny about phone settings, nothing happens. I'm not taken to a new screen or given a force close/failed attempt message. It's almost just there for show.
After hours of scavenging the internet for answers, I'm starting to think I might have accidentally deleted it with Titanium Backup by mistake not knowing it's importance. I've download many "stock" roms hoping to extract the apk from there but none seem to contain it.
I'm not an amateur to this and am completely aggravated by my dead end situation which has abandoned me with no option other than to plead for help via post. If anything could alleviate my situation and either provide the apk or a solution to my problem, I would be forever grateful.
FYI: I'm running out-of-box software with root and CWM recovery. I have stumbled upon the "apply 4.1.2 update manually" thread but the no wipe process requires a stock recovery as to allow /cache flashing (thus not forcing a wipe) and I'm hesitant to backtrack out of CWM.
Thank you for any help in advance.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
unlocatedfile said:
So I'm not sure what's going on, but when trying to click "software update" in ny about phone settings, nothing happens. I'm not taken to a new screen or given a force close/failed attempt message. It's almost just there for show.
After hours of scavenging the internet for answers, I'm starting to think I might have accidentally deleted it with Titanium Backup by mistake not knowing it's importance. I've download many "stock" roms hoping to extract the apk from there but none seem to contain it.
I'm not an amateur to this and am completely aggravated by my dead end situation which has abandoned me with no option other than to plead for help via post. If anything could alleviate my situation and either provide the apk or a solution to my problem, I would be forever grateful.
FYI: I'm running out-of-box software with root and CWM recovery. I have stumbled upon the "apply 4.1.2 update manually" thread but the no wipe process requires a stock recovery as to allow /cache flashing (thus not forcing a wipe) and I'm hesitant to backtrack out of CWM.
Thank you for any help in advance.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
I believe the expression is "you can't have your cake and eat it too" my friend.You can't get software updates the old fashioned way now even if you have the apk.The OTA checks your phone before it will push an update,if anything is out of place it won't push.If you were rooted only,you could probably still get the OTA but as you already said you have manipulated the file system and you have CWM .You will have to do updates thru zips or flash one of the awsome stock rooted updated roms.There are some roms with the newest updates close to stock or just plain stock rooted,I would try one of those bro,it might be easier,that way you can keep root and custom recovery always without having to go back and fourth.I think it is better that way anyway unless you have to send in the phone for warranty service.
Try this
I have a stock ATT Galaxy Note II except that I am rooted so I could use Titanium Backup and a few other things. Also I hid or deleted some ATT Bloatware (not sure which ones -- probably should have recorded what I did). Anyway, the previous OTA update from ATT worked fine. But this time the update to I317UCAMH3 always fails. It downloads, reboots and then fails about when it says 25%. I have been searching here for ideas what to do. Tried to unhide the ATT apps that I could find. That didn't solve the problem. Used Triangle Away to get the counters back. Still no luck.
Did a lot of searching on threads here on what to do but none of the suggestions seemed to work. I think I still have stock recovery but not sure. Is there any way to tell?
Any ideas? Do I need to reinstall the ATT ROM from scratch (including reinstalling apps, etc)?
Based on what I am hearing from friends, I expect ATT to soon release the 4.3 update for this phone. So I think I would like to be stock for now plus root.
Any help would be appreciated.
Thanks
-- Charley
Your answer is here:
http://forum.xda-developers.com/showthread.php?t=2448927
I'll be doing this shortly as well.
I had the same trouble. I made a TiBU backup of user apps and their data (no system apps or system data). I made the zip file also.
Then I did a factory reset. After that, the phone completed the update.
charley000 said:
I have a stock ATT Galaxy Note II except that I am rooted so I could use Titanium Backup and a few other things. Also I hid or deleted some ATT Bloatware (not sure which ones -- probably should have recorded what I did). Anyway, the previous OTA update from ATT worked fine. But this time the update to I317UCAMH3 always fails. It downloads, reboots and then fails about when it says 25%. I have been searching here for ideas what to do. Tried to unhide the ATT apps that I could find. That didn't solve the problem. Used Triangle Away to get the counters back. Still no luck.
Did a lot of searching on threads here on what to do but none of the suggestions seemed to work. I think I still have stock recovery but not sure. Is there any way to tell?
Any ideas? Do I need to reinstall the ATT ROM from scratch (including reinstalling apps, etc)?
Based on what I am hearing from friends, I expect ATT to soon release the 4.3 update for this phone. So I think I would like to be stock for now plus root.
Any help would be appreciated.
Thanks
-- Charley
Click to expand...
Click to collapse
The MH3 OTA update will fail if any of the files it attempts to patch or replace is missing on the phone. It also expects to see the stock version of kernel, modem, and recovery from whichever firmware it detects - typically MC3 or MA4.
If you don't have those missing system apps available for restore in TiBu, your only current option to get to MH3 is to use Odin to load UCALJ2 or UCAMA4 firmware (available from sammobile.com), then run the OTA process. This will wipe your phone back to pure stock and ymmv on what tibu can restore (stay away from restoring system apps, use caution when restoring data along with any other apps - i.e. only when necessary).
Lastly - I wouldn't be surprised to see the 4.3 update come with a locked bootloader. There may be a way to get into that firmware with root intact but the current state of the sgs4 is a pretty good indicator of what to expect when 4.3 arrives on our att i317.
rangercaptain said:
I had the same trouble. I made a TiBU backup of user apps and their data (no system apps or system data). I made the zip file also.
Then I did a factory reset. After that, the phone completed the update.
Click to expand...
Click to collapse
Well tried that. Still fails.
I suspect there is some app or setting that I have to have for ATT to allow me to do it. Others have commented that you need all the ATT Bloatware and other stuff. I am not sure what I have wrong.
Read back one.. I was typing while you were sending
Zen Arcade said:
The MH3 OTA update will fail if any of the files it attempts to patch or replace is missing on the phone. It also expects to see the stock version of kernel, modem, and recovery from whichever firmware it detects - typically MC3 or MA4.
If you don't have those missing system apps available for restore in TiBu, your only current option to get to MH3 is to use Odin to load UCALJ2 or UCAMA4 firmware (available from sammobile.com), then run the OTA process. This will wipe your phone back to pure stock and ymmv on what tibu can restore (stay away from restoring system apps, use caution when restoring data along with any other apps - i.e. only when necessary).
Lastly - I wouldn't be surprised to see the 4.3 update come with a locked bootloader. There may be a way to get into that firmware with root intact but the current state of the sgs4 is a pretty good indicator of what to expect when 4.3 arrives on our att i317.
Click to expand...
Click to collapse
Thanks. Probably the best thing for me to do is just to wait until after 4.3 comes out. By that point, you guys will have figured it all out. Then I can either go from scratch (Odin to stock and the update) or I can pick the best ROM from here. I will probably do the latter.
I am leaning towards one of the ROMs that is close to stock such as Clean Rom or Jedi unless someone has a better suggestion.
Thanks everyone for your help.
Zen Arcade said:
The MH3 OTA update will fail if any of the files it attempts to patch or replace is missing on the phone. It also expects to see the stock version of kernel, modem, and recovery from whichever firmware it detects - typically MC3 or MA4.
If you don't have those missing system apps available for restore in TiBu, your only current option to get to MH3 is to use Odin to load UCALJ2 or UCAMA4 firmware (available from sammobile.com), then run the OTA process. This will wipe your phone back to pure stock and ymmv on what tibu can restore (stay away from restoring system apps, use caution when restoring data along with any other apps - i.e. only when necessary).
Lastly - I wouldn't be surprised to see the 4.3 update come with a locked bootloader. There may be a way to get into that firmware with root intact but the current state of the sgs4 is a pretty good indicator of what to expect when 4.3 arrives on our att i317.
Click to expand...
Click to collapse
Thanks for this info, very helpful.
Though I am rooted and on a custom ROM and all that, I'm far from an expert on this stuff. I plan on trying the AT&T 4.3 update when it drops, but I am also currently contemplating trying to go to MH3 stock, and maybe then re-root on MH3 and make a full Rooted stock backup available "just in case"...
With that in mind - Question: Can you tell me if getting the stock LJ2 or MA4 firmware via sammobile and loading it via Odin takes care of *completely* "stock"-ing your phone, all in one shot, including resetting the flash counter to "0" and all that good stuff? OR - would I still need to then CF-Auto-Root, Triangle Away, and then do a "Full Unroot" in SuperSU to accomplish all this? Just want to make sure I get it right
Thanks in advance. Been searching but have not found a clear-cut answer to this just yet.
Anonymously_Unknown said:
Your answer is here:
http://forum.xda-developers.com/showthread.php?t=2448927
I'll be doing this shortly as well.
Click to expand...
Click to collapse
Will this work if I have TWRP installed?
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.
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