Related
I've had my phone for about two months now without any issues. I have it rooted with the stock rom. Today I was getting a red wifi calling notification. When I finally went to check it, it was error that said cannot start so I turned it off and back on to see if that would resolve anything. Since then my phone has been constantly rebooting. It comes on and stays on for about two minutes before rebooting again. I've been able to reach the settings and turn wifi calling off but that hasn't helped. I want to try to maybe disable the app or whatever runs it and try clearing it's data, so my question finally is does anyone know which app I would be looking for under all apps so I could give that a try.
ghettovirtuoso said:
I've had my phone for about two months now without any issues. I have it rooted with the stock rom. Today I was getting a red wifi calling notification. When I finally went to check it, it was error that said cannot start so I turned it off and back on to see if that would resolve anything. Since then my phone has been constantly rebooting. It comes on and stays on for about two minutes before rebooting again. I've been able to reach the settings and turn wifi calling off but that hasn't helped. I want to try to maybe disable the app or whatever runs it and try clearing it's data, so my question finally is does anyone know which app I would be looking for under all apps so I could give that a try.
Click to expand...
Click to collapse
I'm having a very similar issue. Stock M8 running latest T-mobile firmware. Rooted. Flashed PhilzCWMtouch and now the phone reboots every 1-3 minutes. I flashed the original recovery via fastboot and it is still rebooting. Going to redownload the stock recovery and try flashing it again before I do a full restore. I really want to avoid that if possible.
cheasfridge said:
I'm having a very similar issue. Stock M8 running latest T-mobile firmware. Rooted. Flashed PhilzCWMtouch and now the phone reboots every 1-3 minutes. I flashed the original recovery via fastboot and it is still rebooting. Going to redownload the stock recovery and try flashing it again before I do a full restore. I really want to avoid that if possible.
Click to expand...
Click to collapse
Thanks for the reply, but I gave up last night trying to fix it from the current state. I restored a nandroid from the previous week and used titanium to infuse data into already installed apps and restore missing apps. I do hope you find success in getting your issue to stop. I haven't had problem using TWRP on this phone, maybe give that a try
ghettovirtuoso said:
Thanks for the reply, but I gave up last night trying to fix it from the current state. I restored a nandroid from the previous week and used titanium to infuse data into already installed apps and restore missing apps. I do hope you find success in getting your issue to stop. I haven't had problem using TWRP on this phone, maybe give that a try
Click to expand...
Click to collapse
I finally was able to fix it after flashing twrp and then doing a wipe from there. then updated superSU and everything seems fine now. sorry about the different accounts. I need to delete that other one.
Sent from my HTC One_M8 using Tapatalk
ghettovirtuoso said:
I've had my phone for about two months now without any issues. I have it rooted with the stock rom. Today I was getting a red wifi calling notification. When I finally went to check it, it was error that said cannot start so I turned it off and back on to see if that would resolve anything. Since then my phone has been constantly rebooting. It comes on and stays on for about two minutes before rebooting again. I've been able to reach the settings and turn wifi calling off but that hasn't helped. I want to try to maybe disable the app or whatever runs it and try clearing it's data, so my question finally is does anyone know which app I would be looking for under all apps so I could give that a try.
Click to expand...
Click to collapse
Lemme ask you......... did you root your phone BEFORE or AFTER receiving any OTAs?
I have T-Mobile and the M8 too. I rooted my phone AFTER getting the OTA, and I'm pretty sure that's what caused all hell to break loose. My phone wasn't like yours at first, for weeks it would randomly go into Recovery mode............ but then this past week it started doing that: constantly rebooting. I didn't have a backup that was pre-root, only post-root (rookie mistake lol), so having to replace it now. Using the post-root is just a temporary fix as it can still go back to non-stop reboot at anytime, but the new phone comes in Tuesday.
Please let me know.
Good luck! (Not sure if that's you in the other post that said it's been fixed).
Thank You,
RockStar2005
RockStar2005 said:
Lemme ask you......... did you root your phone BEFORE or AFTER receiving any OTAs?
I have T-Mobile and the M8 too. I rooted my phone AFTER getting the OTA, and I'm pretty sure that's what caused all hell to break loose. My phone wasn't like yours at first, for weeks it would randomly go into Recovery mode............ but then this past week it started doing that: constantly rebooting. I didn't have a backup that was pre-root, only post-root (rookie mistake lol), so having to replace it now. Using the post-root is just a temporary fix as it can still go back to non-stop reboot at anytime, but the new phone comes in Tuesday.
Please let me know.
Good luck! (Not sure if that's you in the other post that said it's been fixed).
Thank You,
RockStar2005
Click to expand...
Click to collapse
I rooted preOTAs. Pretty much as soon I got the phone. I have been unsuccessful in stopping the problem as of yet but am going to RUU in a few minutes. Prior to this I've only tried factory resets from within the OS and from the bootloader wiping everything including data and external sd. Hope this RUU provides me some peace.
ghettovirtuoso said:
I rooted preOTAs. Pretty much as soon I got the phone. I have been unsuccessful in stopping the problem as of yet but am going to RUU in a few minutes. Prior to this I've only tried factory resets from within the OS and from the bootloader wiping everything including data and external sd. Hope this RUU provides me some peace.
Click to expand...
Click to collapse
It almost seems like this (my) phone hates to be rooted. As soon as I restore to pre-root backup, it's fine. I hate not being rooted.
Software No: 1.57.531.7
It did the constant reboot (after about 1 minute of being loaded) with both stock, rooted and with Skydragon 2.3 rom. Very irritating. It seems to happen when I unplug it from the charger or pc, while rebooting.
chattguy said:
It almost seems like this (my) phone hates to be rooted. As soon as I restore to pre-root backup, it's fine. I hate not being rooted.
Software No: 1.57.531.7
It did the constant reboot (after about 1 minute of being loaded) with both stock, rooted and with Skydragon 2.3 rom. Very irritating. It seems to happen when I unplug it from the charger or pc, while rebooting.
Click to expand...
Click to collapse
I was having the same problems. I'm getting my replacement phone today. My current one is only working (for now) b/c I did a restore, but not far back enough for it to be working 100% right. I'm working with someone who might have a plan, so we'll see. He said he did everything, including root and S-OFF, and got Harman/Kardon sound too (on his non-Sprint phone). I'll post again here when I get more info. First gotta get my replacement phone. lol I had H/K but I think rooting it after the OTA messed it up, but we'll see. H/K did improve the sound, so I really want it back.
RockStar2005
chattguy said:
It almost seems like this (my) phone hates to be rooted. As soon as I restore to pre-root backup, it's fine. I hate not being rooted.
Software No: 1.57.531.7
It did the constant reboot (after about 1 minute of being loaded) with both stock, rooted and with Skydragon 2.3 rom. Very irritating. It seems to happen when I unplug it from the charger or pc, while rebooting.
Click to expand...
Click to collapse
Mine too. I RUU'd back to stock and unlocked bootloader. Before anything else I made a backup. Rooted and the problem presented itself again. Restored backup but chose not to root and my phone has been fine thus far. Never used an android without root so this should be interesting.
ghettovirtuoso said:
Mine too. I RUU'd back to stock and unlocked bootloader. Before anything else I made a backup. Rooted and the problem presented itself again. Restored backup but chose not to root and my phone has been fine thus far. Never used an android without root so this should be interesting.
Click to expand...
Click to collapse
Yeah man, I hope they come up with a fix for it, I don't want to be unrooted forever.
ghettovirtuoso said:
Mine too. I RUU'd back to stock and unlocked bootloader. Before anything else I made a backup. Rooted and the problem presented itself again. Restored backup but chose not to root and my phone has been fine thus far. Never used an android without root so this should be interesting.
Click to expand...
Click to collapse
He's working to help me out. Maybe he can fix your issue too? Still waiting for him to write me a guide for my specific issues, so can't verify anything, but sounds like he's helped a lot of ppl on here already. Check him out:
http://forum.xda-developers.com/showthread.php?t=2718130
Good luck!
RockStar2005
---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------
chattguy said:
Yeah man, I hope they come up with a fix for it, I don't want to be unrooted forever.
Click to expand...
Click to collapse
He's working to help me out. Maybe he can fix your issue too? Still waiting for him to write me a guide for my specific issues, so can't verify anything, but sounds like he's helped a lot of ppl on here already. Check him out:
http://forum.xda-developers.com/showthread.php?t=2718130
Good luck!
RockStar2005
So this is bugging me out. I received my Verizon Dev Edition last week. It came with NJ5 already installed, so I skipped the first step to flash custom recovery, and then I rooted. Everything is great I have a rooted stock NJ5 ROM with a custom recovery. Now when I wipe my data, system, dalvik, and cache (clean install) to install any rom (Definitive/FireKat) I get a Amazon Kindle unfortunate force close error at the start up wizard, also the samsung keyboard swipe feature and suggestions at the top do not work at all. After I let it settle I bypass the wizard by pressing skip, then I turn off auto sync. I log in to google and I try to launch Maps and I get a force close error. I tried updating it in the Play Store and it gets a download error. What is going on?? I am going kind of insane trying to fix this. I ODIN Stock NJ5 restore to get maps, kindle, and the keyboard to work correctly. I spent all day trying to figure this and I can not for the life of me get a good solid flash! I am thinking of ODINing Stock NI1 Restore to see what happens. Will I break my phone if I downgrade? Does anybody have any suggestions to fix these errors? It is only when I flash a ROM from TWRP. Thanks in advance!
jcip17 said:
So this is bugging me out. I received my Verizon Dev Edition last week. It came with NJ5 already installed, so I skipped the first step to flash custom recovery, and then I rooted. Everything is great I have a rooted stock NJ5 ROM with a custom recovery. Now when I wipe my data, system, dalvik, and cache (clean install) to install any rom (Definitive/FireKat) I get a Amazon Kindle unfortunate force close error at the start up wizard, also the samsung keyboard swipe feature and suggestions at the top do not work at all. After I let it settle I bypass the wizard by pressing skip, then I turn off auto sync. I log in to google and I try to launch Maps and I get a force close error. I tried updating it in the Play Store and it gets a download error. What is going on?? I am going kind of insane trying to fix this. I ODIN Stock NJ5 restore to get maps, kindle, and the keyboard to work correctly. I spent all day trying to figure this and I can not for the life of me get a good solid flash! I am thinking of ODINing Stock NI1 Restore to see what happens. Will I break my phone if I downgrade? Does anybody have any suggestions to fix these errors? It is only when I flash a ROM from TWRP. Thanks in advance!
Click to expand...
Click to collapse
It sounds like you have mixed firmware. I would think you would be safe downgrading as long as you use dev edition files. Make a back up of your partitions first with these instructions if you haven't already. Atleast you will a safeguard in case something goes wrong.
Misterxtc said:
It sounds like you have mixed firmware. I would think you would be safe downgrading as long as you use dev edition files. Make a back up of your partitions first with these instructions if you haven't already. Atleast you will a safeguard in case something goes wrong.
Click to expand...
Click to collapse
Thanks I will try downgrading, but not sure what to do after. I guess I should try NI1 definitive rom and see if I get the errors. I did the Aboot backup yesterday using EFS Professional so I think I should be good!
jcip17 said:
Thanks I will try downgrading, but not sure what to do after. I guess I should try NI1 definitive rom and see if I get the errors. I did the Aboot backup yesterday using EFS Professional so I think I should be good!
Click to expand...
Click to collapse
That sounds right. If there aren't any NJ5 ROMs out yet then I can almost guarantee that's the problem. I know that sort of thing happens when you mix firmwares, I had a lot of folks doing that with the S5 ROM I made.
Misterxtc said:
That sounds right. If there aren't any NJ5 ROMs out yet then I can almost guarantee that's the problem. I know that sort of thing happens when you mix firmwares, I had a lot of folks doing that with the S5 ROM I made.
Click to expand...
Click to collapse
But definitive ROM has a NJ5 version and so does FireKat V8. Even the Stock root deodexed NJ5 ROM does not install correctly. It is very weird
jcip17 said:
But definitive ROM has a NJ5 version and so does FireKat V8. Even the Stock root deodexed NJ5 ROM does not install correctly. It is very weird
Click to expand...
Click to collapse
I'm wondering if it might be your recovery version. I don't have a dev phone or root so I can't help out that much.
Misterxtc said:
I'm wondering if it might be your recovery version. I don't have a dev phone or root so I can't help out that much.
Click to expand...
Click to collapse
I understand I really appreciate the help though. So the keyboard is fixed by updating the language, for some reason lol. I am going to delete kindle and maps and try to install it through the play store and see what happens.
So deleting maps and installing it through the play store worked and once I opened maps I got a play services error and it said it needed to update. And I updated and I have the new play store icon now and everything seems stable now. I guess I will have to do this with every ROM I install. Or until lollipop fixes these issues. It seems like I am the only asshole who is experiencing these problems! lol
Short history of what I've done/where I'm at now:
The History
Wanted to upgrade rooted D855 from 4.4.2KK to 5.X Lollipop
De-rooted using SuperSU. Rebooted, and went to update center to apply update. Message saying "Phone has been noted to be rooting. Software update not available for rooted phones." or something thereabouts.
Decide to factory reset phone. Does nothing.
Follow this guide (Link) to completely wipe and start fresh. All goes well.
Bunch of bloatware comes pre-installed. What the hell?
Decide to combat this by following this guide (The KDZ way) (Link) and this Image (3 UK variant) to attempt to get back to my original version.
Used this one-click root (Link) to re-root my Android 5.0 variant (question on this later)
Goes well pretty much; everything seems about right. However, here are the problems.
The Problems
I have rooted and have Titanium Backup Pro; tried using this to remove the bloatware. Doesn't do anything, and if I try to do them individually I get the message "cannot remove System app. Failed to locate the APK file." This is my #1 problem. I have a bunch of European apps that I can't pronounce, plus rubbish like 'Orange Antivirus'. Even things like Deezer is now pre-installed system crap, listed under the Software center portion of the LG Updates area on the phone.
My 3 splash screen no longer comes up, which is fine, makes the booting either faster or just seem smoother. However, it makes me wonder whether I'm on the right version of Android now; will I miss updates to future version of Android from hereon out?
Is Android 5.0 the latest update for the EU D855? I heard 5.0 was having problems on the G3, hence why I've updated so late. However, if I'm now stuck on the version WITH the problems, that's not good.
Bump; anyone? This is driving me nuts!
Hi,
1. To uninstall the antivirus you need to remove it from the phone administrators.
2. There should be at least the LG boot animation.
3. Yes. The latest update is still 5.0.
I suggest that you move to a custom Rom based on stock like cloudy 2.5.
Much better Rom and free of bloatware.
Regards
Sent from my phone
ypsmav said:
Hi,
1. To uninstall the antivirus you need to remove it from the phone administrators.
2. There should be at least the LG boot animation.
3. Yes. The latest update is still 5.0.
I suggest that you move to a custom Rom based on stock like cloudy 2.5.
Much better Rom and free of bloatware.
Regards
Sent from my phone
Click to expand...
Click to collapse
I gave up on waiting (the bloatware was driving me crazy, not usually so impatient), and just installed TWRP, wiped it and reinstalled a fully stock ROM, so all sorted now. Any benefit to using Cloudy 2.5 over complete stock? Any performance/battery benefits?
Thanks for your response though
BRPW said:
I gave up on waiting (the bloatware was driving me crazy, not usually so impatient), and just installed TWRP, wiped it and reinstalled a fully stock ROM, so all sorted now. Any benefit to using Cloudy 2.5 over complete stock? Any performance/battery benefits?
Thanks for your response though
Click to expand...
Click to collapse
Felt faster for me plus a load of newer updated app versions for stock apps and a lot more customization options :good:
Will_Xda said:
Felt faster for me plus a load of newer updated app versions for stock apps and a lot more customization options :good:
Click to expand...
Click to collapse
Maybe I'll look into it then On another note, you're from Leicester? Where abouts you from?
Just did the ota update. Have since rebooted phone twice. Update and phone don't like each other! Chrome keeps auto-closing. And phone is lagging/freezing continuously. Phone was rooted years ago, and never any issues, even upgrading to Kitkat. This one I'm not to sure about!!!!!
Oh, and booting takes about twice looking too!
Keeps getting better...can't download anything from the play store. Says it's downloading, but never goes anywhere.
andygold said:
Just did the ota update. Have since rebooted phone twice. Update and phone don't like each other! Chrome keeps auto-closing. And phone is lagging/freezing continuously. Phone was rooted years ago, and never any issues, even upgrading to Kitkat. This one I'm not to sure about!!!!!
Oh, and booting takes about twice looking too!
Keeps getting better...can't download anything from the play store. Says it's downloading, but never goes anywhere.
Click to expand...
Click to collapse
Were you rooted? The last OTA update tried to take away root and it was really hard getting it back. It's acted strangely ever since.
wildbean98 said:
Were you rooted? The last OTA update tried to take away root and it was really hard getting it back. It's acted strangely ever since.
Click to expand...
Click to collapse
I took the update against my better judgement and sure enough soft bricked and now phone wont go into DL mode...grrrr
Major issues here as well. My SD card is now blank and doesn't want to mount. Big slowdowns as well. Any way to remove this update ?
Sent from my SHIELD Tablet using Tapatalk
Was finally able to DL apps, but at a crawl. I cleared the cache including dalvik, and everything is back to normal. And I'm still rooted!
I used Cache Cleaner NG from the play store
Soft bricked
I have bricked my phone after accidentally accepting it. Got back the phone again with lg flash tool. Once restarted the phone, rooted it, used titanium backup apk to freeze the software updater.
I don't think that it is wise to do a software update while rooted, it usually denies the process anyways.
Actually guys, its most likely that malware piece that was making its way around. Didnt anyone else read about it a few days ago? Let me hunt it down and see if i can post a link here. Standby....
Update: hold the phone, i may have been mistaken. Standby...
Now im soo broke i cant even pay attention!
ThaHawk said:
I don't think that it is wise to do a software update while rooted, it usually denies the process anyways.
Click to expand...
Click to collapse
Hi, rooting a phone does not stop the update anyway since you can unroot very easily, if it is supersu apk. But if a person installed custom recovery, it can brick the phone since the update tries to use the stock recovery. I learnt it in the hard way.
sdivk said:
Hi, rooting a phone does not stop the update anyway since you can unroot very easily, if it is supersu apk. But if a person installed custom recovery, it can brick the phone since the update tries to use the stock recovery. I learnt it in the hard way.
Click to expand...
Click to collapse
I stand corrected, your absolutely right!
ThaHawk said:
I stand corrected, your absolutely right!
Click to expand...
Click to collapse
Thanks. If you have a rooted lg e980 without custom recovery, you can use quickboot apk to enter stock recovery, which has limited features.
The problem with unlocking bootloader and use custom recovery is, if there is an update, there is no way to relock the bootloader and flash stock recovery. If sombody can shed the light on this matter, i really appreciate it.
I am looking for a way to relock the bootloader and install stock recovery without using lg flash tool.
Not that i am expecting an update from AT&T anytime soon.
+1
its better its included on CM based ROMs also
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