Related
Alright, I am new to all of this, but finally decided to root my Epic yesterday after a fit of jealousy over my room mates new Charge. My room mate is experienced with rooting so he has been helping me with it, but some of the things going on with my phone since I started this yesterday morning (at 6 am mind you) are beyond either of us. I'll also add, while I am a noob in terms of rooting, I am not a technological retard.
I spent several hours deciding on what exactly I wanted with a root and rom on my phone, finally decided I'd go with a oneclick I found on here; I flashed and did the root, but adb would not let me do anything with the su to test as the instructions said to do. I got the "$" when I typed in "adb shell" and superuser did show up in the app drawer, so I assumed it took, despite the error I received in cmd. At the recommendation of my roommate, also installed the SDK and the required JDK for that. My phone then went nuts. I installed on my phone the ClockworkMod since it was not with the root as I had thought I read it would be. I then downloaded and installed the SyndicateROM Frozen, thinking it looked the nicest and operated in terms in I could live with/ Enter phone acting incredibly retarded. My phone got stuck in a boot, no matter what we did, it would not boot further than the first Samsung screen. I hadn't even been able to install the ROM at this point. ClockworkMod had accidentally been run in 2x not the 3x as stated (thank you roommate) and apparently, my phone did not appreciate this.
After a few hours of hunting down info and being deliriously exhausted (I had not slept in some36 hours) we finally got my phone to restore to factory defaults and started over. The root took perfectly this time, still not giving me the su cmd I had tried, but it didn't give me any other errors as before (my av software on my computer had been scrubbing the rageagainstthecage file causing the root to only half work apparently). 8 hours in and the root is good. Back it all up and I then move on to putting the SRF on. It refuses to go. CWM said it was vr 3, but when I would go to Reboot in Recovery through CWM it booted into stock recovery, which would not allow the rom to take. I gave up at this point and got some much needed sleep.
This morning I get up to give it another whirl so I can hopefully have a semi-working phone before going to work today and run into the same problem of CWM booting the stock recovery. I say eff it and try to boot into recovery by the stock options, power, camera, volume...LO' AND BEHOLD CWM3 has kicked in. This its the part that really baffels me, and maybe its my noobness, but I just don't get it, from within CWM stock recovery boots, but from booting recovery, CWM boots. I let it go though, and decided, hey, it's working, let's get that Rom on there. It installs with no errors and boots up. I would post a screenshot, but a whole new set of problems has come up now preventing me from doing so.
So if you're following me so far, we now have a successful root, and seemingly successful rom installed. Bloatware is all gone, and my favorit, the Carrier IQ crap is ripped out. YAY right? Wrong. I unlock the phone and while it does look shiney, there is something missing. Everything is stock, MINUS the wallpaper and apps. The rom installation did take outall the bloatware etc, but aside from this, it looks just the same. I saw eff this too and I'll just put a theme on with a launcher I like.
I am now unable to access the SD card on my phone through USB, it locks my windows explorer completely when I try, just the explorer though, not the computer. I cannot open the SD, or any other drive when I try. It is sitting in an endless loading loop. Extremely aggravating considering I know its not the computer as I just (literally this week) upgraded everything in my computer, added more RAM, new HDD, new Vid, new Mobo, pretty much new everything cos I couldn't do any gaming on my previous POS set up.
In short:
Running the one click that says its not joeykrim, but loads joeykrim when installing and SyndicateROM Frozen 1.1.0. I'll list what the About Phone says below since I can't get in the SD to pull the screenshot:
Model Number:SPH-D700
Firmware Version: 2.2.1
Baseband Version: S: D700.0.5S.EC05
Kernel Version:2.6.32.9
Build Number: SRF 1.1.0/TwilightZone 1.1.0
Hardware Version: D700.0.5
Please help me figure out what's wrong here cos I really don't know, and I just want to make this thing work. I was fine with what I was running before, but would like to take advantage of the root, but I can't as long as this is acting up. If any other info is needed, let me know and I will get it for you. Thanks!
**Update** I have now flashed the SD from recovery so it is completely clean. The market app changed from blue to green android, so something different there.
Also, dunno if it has anything to do with the rom, but the file launcher is gone, no biggy there, I downloaded Astro, after reinstalling the rom. Market is still green but the rom apps are back, which were previously missing due to the SD blitz I imagine. So I am back to square one. SD card will not read through phone usb mount, but reads through card reader. It is still killing my explorer, so I had my roommate check it on his through the usb reader, and it does fine.
I have no idea what you did there. My suggestion would be to watch qbking77's youtube vids on how to restore to factory, then how to root, then how to load SFR 1.1.1.
They are very easy to follow along with, and you will not have an issues. I believe they are stickied either in the Q/A section or General.
Good luck!
Edit --
I would put it into download mode and run Odin with a stock EC05 rom, and then try again.
I Have the same setup / only two known issues *
I too am running your exact same setup:
Model Number:SPH-D700
Firmware Version: 2.2.1
Baseband Version: S: D700.0.5S.EC05
Kernel Version:2.6.32.9
Build Number: SRF 1.1.0/TwilightZone 1.1.0
Hardware Version: D700.0.5
I to had the same problem when installing:
"""I got the "$" when I typed in "adb shell" and superuser did show up in the app drawer, so I assumed it took, despite the error I received in cmd."""
However, when I click on an application within the SuperUser app, it gives me the following error: "The application Superuser (process com.noshufou.android.su) has stopped unexpectedly. Please try again." (with a "Forceclose" button)
I also get this error when a incoming call happens and sometimes with text msgs.
"The application Google services Framework(process com.google.process.gapps) has stopped unexpectedly." (With a Forceclose button)
Other than these to items my phone is working fine. I know this doesnt help much, but I wanted to respond because I have the same setup and it does work, but with flaws.
abqdavid said:
I too am running your exact same setup:
Model Number:SPH-D700
Firmware Version: 2.2.1
Baseband Version: S: D700.0.5S.EC05
Kernel Version:2.6.32.9
Build Number: SRF 1.1.0/TwilightZone 1.1.0
Hardware Version: D700.0.5
I to had the same problem when installing:
"""I got the "$" when I typed in "adb shell" and superuser did show up in the app drawer, so I assumed it took, despite the error I received in cmd."""
However, when I click on an application within the SuperUser app, it gives me the following error: "The application Superuser (process com.noshufou.android.su) has stopped unexpectedly. Please try again." (with a "Forceclose" button)
I also get this error when a incoming call happens and sometimes with text msgs.
"The application Google services Framework(process com.google.process.gapps) has stopped unexpectedly." (With a Forceclose button)
Other than these to items my phone is working fine. I know this doesnt help much, but I wanted to respond because I have the same setup and it does work, but with flaws.
Click to expand...
Click to collapse
I have that set up, no problems. Sometimes you can get a bad download or a bad flash and have to start over. Remember to wipe3x also before flashing.
Thanks, it seems to be working right now, its letting me flash and install things and they are running, so I will go with it...problems were likely due to my severe lack of sleep and not really knowing what I was doing to begin with.
SD is still fubar'd for accessing via USB through my phone, but I can deal with unmounting and a just linking it up direct..
Hi All,
I am lightly experience with all of this so i will try and provide some background.
I purchased my S3 and when I first rooted CyanogenMod 10.0.0 was the current stable. I have been using that until just recently when I decided it was time to upgrade as I was experiencing some serious performance issues with SMS (not getting any) and I have a few days off work. I have also been having issues with all data connectivity dropping out all the time (an issue I have just come to live with) for probably about a year now. There is was a issue submitted to the CyanogenMod Bug tracker when it was on Google (not sure if it still is). If I can dig up the link I will edit the post but I do not belie it is really relevant to this particular issue. [Edit: This looks like it may be the Jira Case. Similar issue reported.] https://jira.cyanogenmod.org/browse/CYAN-1396
See thread title for issue.
Steps I Have Taken So Far:
1. I downloaded the latest 10.1.2 stable and copied it to my external SD.
2. Reset Factory Defaults
3. Clear Cache
4. Clear Dalcik
5. Booted to recovery (ClockWorkMod) and attempted to install...received a status 7 error.
6. Removed the assert tags as instructed here: http://highonandroid.com/android-roms/how-to-fix-status-7-error-with-cwm-recovery-on-rooted-android
7. Reset Factory Defaults
8. Clear Cache
9. Clear Dalcik
10. Attempted to install new file and not it simply failed when "Attempting to Open Update...", there was nothing in the log (under advanced in clockworkmod)
11. Looked further into the release notes of 10.1.2 and realized it might be a problem with my boot-loader (This is my active theory).
12. Went searching on how to try and "update my boot-loader" could only find topics relating to unlocking.
13. To my understanding the stock ROMs also update the boot-loader so I installed this stock ROM: http://forum.xda-developers.com/showthread.php?t=1910947&highlight=md4
14. Check to see it installed OK and then booted back into recovery and attempted steps 2-10....no success.
Thoughts?
Some more info:
Sprint Galaxy S3
Model: SPH-L710
Android Version: 4.1.2
Baseband Version: L710VPLI3
Build Version: JZ054K.L710VPBMD4
Hardware Version: L710.14
ClockWorkMod Recovery: v6.0.3.1
Don't get me wrong I would love someone to just swoop in with a solution but I would really like to understand what is happening here.
- What "version" is my boot-loader / how can you tell that?
- Is there a reference somewhere about what boot-loaders are for what versions?
I have a nandroid backup of my old 10.0.0 ROM and at this moment in time I have the stock ROM image which is listed above installed and running. I DO NOT have a backup of my IMEI or my EFS so that might be a decent next step.
Thank you,
Matthew
References:
http://forum.xda-developers.com/showthread.php?t=2179330
http://forum.xda-developers.com/showthread.php?t=1910947&highlight=md4
http://forum.xda-developers.com/showthread.php?t=1922461
http://wiki.cyanogenmod.org/w/D2spr_Info
http://wiki.cyanogenmod.org/w/Install_CM_for_d2spr
mcf747 said:
Hi All,
I am lightly experience with all of this so i will try and provide some background.
I purchased my S3 and when I first rooted CyanogenMod 10.0.0 was the current stable. I have been using that until just recently when I decided it was time to upgrade as I was experiencing some serious performance issues with SMS (not getting any) and I have a few days off work. I have also been having issues with all data connectivity dropping out all the time (an issue I have just come to live with) for probably about a year now. There is was a issue submitted to the CyanogenMod Bug tracker when it was on Google (not sure if it still is). If I can dig up the link I will edit the post but I do not belie it is really relevant to this particular issue. [Edit: This looks like it may be the Jira Case. Similar issue reported.] https://jira.cyanogenmod.org/browse/CYAN-1396
See thread title for issue.
Steps I Have Taken So Far:
1. I downloaded the latest 10.1.2 stable and copied it to my external SD.
2. Reset Factory Defaults
3. Clear Cache
4. Clear Dalcik
5. Booted to recovery (ClockWorkMod) and attempted to install...received a status 7 error.
6. Removed the assert tags as instructed here: http://highonandroid.com/android-roms/how-to-fix-status-7-error-with-cwm-recovery-on-rooted-android
7. Reset Factory Defaults
8. Clear Cache
9. Clear Dalcik
10. Attempted to install new file and not it simply failed when "Attempting to Open Update...", there was nothing in the log (under advanced in clockworkmod)
11. Looked further into the release notes of 10.1.2 and realized it might be a problem with my boot-loader (This is my active theory).
12. Went searching on how to try and "update my boot-loader" could only find topics relating to unlocking.
13. To my understanding the stock ROMs also update the boot-loader so I installed this stock ROM: http://forum.xda-developers.com/showthread.php?t=1910947&highlight=md4
14. Check to see it installed OK and then booted back into recovery and attempted steps 2-10....no success.
Thoughts?
Some more info:
Sprint Galaxy S3
Model: SPH-L710
Android Version: 4.1.2
Baseband Version: L710VPLI3
Build Version: JZ054K.L710VPBMD4
Hardware Version: L710.14
ClockWorkMod Recovery: v6.0.3.1
Don't get me wrong I would love someone to just swoop in with a solution but I would really like to understand what is happening here.
- What "version" is my boot-loader / how can you tell that?
- Is there a reference somewhere about what boot-loaders are for what versions?
I have a nandroid backup of my old 10.0.0 ROM and at this moment in time I have the stock ROM image which is listed above installed and running. I DO NOT have a backup of my IMEI or my EFS so that might be a decent next step.
Thank you,
Matthew
References:
http://forum.xda-developers.com/showthread.php?t=2179330
http://forum.xda-developers.com/showthread.php?t=1910947&highlight=md4
http://forum.xda-developers.com/showthread.php?t=1922461
http://wiki.cyanogenmod.org/w/D2spr_Info
http://wiki.cyanogenmod.org/w/Install_CM_for_d2spr
Click to expand...
Click to collapse
Is this the file u flashed when u tried to update the boot loader?
http://goo.im/devs/freeza/d2sprFirmware/Galaxy-S-fre3-MD4FirmwareModemAIO.zip
I ask because where u listed addtl info it says your build is md4 but your baseband is li3(ics) I don't think your on the latest boot loader. Flashing what I have linked above will fix that. Second I don't think u had to break down that zip and start changing assert lines. Those lines are there for a reason and shouldn't have to be altered. I would update your firmware using my link then redownload cm 10 and reattempt flashing it without altering it
billard412 said:
Is this the file u flashed when u tried to update the boot loader?
[Link redacted due to the fact Im a new member and cannot post it yet.]
I ask because where u listed addtl info it says your build is md4 but your baseband is li3(ics) I don't think your on the latest boot loader. Flashing what I have linked above will fix that. Second I don't think u had to break down that zip and start changing assert lines. Those lines are there for a reason and shouldn't have to be altered. I would update your firmware using my link then redownload cm 10 and reattempt flashing it without altering it
Click to expand...
Click to collapse
No it was not...however I had it already downloaded so I must have gotten close and decided to not go down that road.
I performed the the install of the linked file and my Baseband is now L710VPBMD4 and 10.1.2 appears to have installed correctly.
NOTE: After updating firmware I immediately attempted to install 10.1.2 and it failed. I restarted into the stock ROM and then rebooted and entered recovery and it installed fine. Not sure if it was the restart or entering into a ROM that was the solution but a good note for anyone with this issue in the future.
Yes, it's necessary to restart after flashing a new bootloader. It's really not a good idea to bypass security checks like removing those lines in the bootloader, because 4.2.2 roms are implementing a RIL that relies on the MD4 bootloader.
Sent from my S3 on Sense 5 (you jelly?)
CNexus said:
Yes, it's necessary to restart after flashing a new bootloader. It's really not a good idea to bypass security checks like removing those lines in the bootloader, because 4.2.2 roms are implementing a RIL that relies on the MD4 bootloader.
Sent from my S3 on Sense 5 (you jelly?)
Click to expand...
Click to collapse
So Any idea how to pass the status 7 error, I am trying to update to CM 10.1.2 stable and I can't pass the ROM installation because of status 7, removing the security checks doesn't work either.
EDIT: I thought i had the right boot loader, It seen like i don't...
Maturola said:
So Any idea how to pass the status 7 error, I am trying to update to CM 10.1.2 stable and I can't pass the ROM installation because of status 7, removing the security checks doesn't work either.
EDIT: I thought i had the right boot loader, It seen like i don't...
Click to expand...
Click to collapse
Lol...
February 4: Rom updated to include February security patches.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=16643
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
January 14. Rom updated to include Google's January 2016 security patches. Also, selinux not only disabled, but completely removed: the rom compiled without selinux sources/binaries.
Kernel does NOT include recovery, so use TWRP for Fota/Recovery partition.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=16217
_________________________________________________________________________________
For those who prefer to stick to bugless kitkat: Rom updated to include all "shields up" features including cleaning creepy Ips and dns defaults. Compiled just a few days ago.
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=13001
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Here is Slimkat 10 unofficial built from sources on March 2. Built using JDK-7, which turned out to be beneficial for the rom. Slim, fast, smooth and stable. For those of you who have been using Lollipop for a while, you will see how much faster, smoother and more stable kitkat is. Everything works: no reboots, no freezing, no overheating, no screen light flickering, no video recording/play problems, great battery life and abundance of features. This taken together with improved security makes a pretty darn good rom. I tried it and got rid of Lollipop.
Changes:
1. New Iptables binaries which allow to stop kernel communicating (if used with Afwall) with Google home.
2. Changes in Vold to enable 256 bit AES encryption, as opposed to default 128 bit
3. Key length increased for multiple keys
3. Kernel with disabled Selinux and enabled Tomoyo together with all ciphers/hushes/digests/random number generation tools
4. Latest changes from Google code (I was surprised finding changes pushed for kitkat while synching Google source)
5. TWRP 2.8.x integrated in boot image
Install:
1. Be on Kitkat, rooted with recovery
2. Enter recovery and wipe Cache/System/Data
3. Flash the rom and reboot
4. Enjoy and say thank you or perhaps donate
Rom is in Download section above
Credit: Slimroms
Warning: I am not responsible for your device exploding and killing everybody around. You are on your own. :laugh:
Source: https://github.com/SlimRoms/platform_manifest/tree/kk4.4-caf
Source with changes: https://github.com/HonamiZ1
XDA:DevDB Information
Slimkat 10 Final Edition, ROM for the Sony Xperia Z1
Contributors
optimumpro
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: Slimroms
Version Information
Status: Stable
Current Stable Version: 10
Stable Release Date: 2015-03-02
Created 2015-03-03
Last Updated 2016-02-04
Reserved
Believe me I have no interest in being in any of "your threads" {That's why I'm editing this post instead of posting a new one xD},
I'll leave this thread from any further discussion.... for now at least
Regards,
Omar.
OmarEinea said:
Cool, can you give us changelog of what's new between build 9.0 and build 10?
cuz latest kk build by Slim Team is 9.0 : https://github.com/SlimRoms/vendor_slim/blob/kk4.4/config/common.mk#L154
so you must have made some major changes to call it build 10, right?
Regards,
Omar.
Click to expand...
Click to collapse
Thanks. Reading the OP might help...
" you didn't get my point, did you!!"
Oh, I did get your point alright. :fingers-crossed:
Could you please do me a favor? Kindly stay away from my threads. If you feel that you need to continue to report me, that's your right, but again, stay away from my threads.
Best regards
Gonna give this a try as sounds like Kk on steroids well stable steroids.....LP still too buggy for me.
I tried it. But play store doesn't work. What is the problem...?
Rom Updated
See OP for description and download link...
thanks
the best option is in that forum for the Z1 now
First download
Thanks for all your awesome roms
I downgraded from CM12 because it feels like each LP-Rom needs more polishing.
The Rom installed successfully (did a system / data / cache Wipe) but now I am unable to get into recovery. It is stuck on the Sony Logo. Just starting the OS works fine though.
Edit:
I tried flashing TWRP 2.8.6.0 via Flashboot.
Flash was successfull, but I still get stuck on the Sony Logo when i try to get into recovery.
The Led also switches lights from purple to orange.
Xecu said:
I downgraded from CM12 because it feels like each LP-Rom needs more polishing.
The Rom installed successfully (did a system / data / cache Wipe) but now I am unable to get into recovery. It is stuck on the Sony Logo. Just starting the OS works fine though.
Edit:
I tried flashing TWRP 2.8.6.0 via Flashboot.
Flash was successfull, but I still get stuck on the Sony Logo when i try to get into recovery.
The Led also switches lights from purple to orange.
Click to expand...
Click to collapse
If you have recovery in Fota partition, it is known to collide with in boot image recovery resulting in no recovery at all. So, you need to get rid of Fota recovery to use internal one. For that do this in fastboot: fastboot erase recovery; then fastboot reboot...
optimumpro said:
If you have recovery in Fota partition, it is known to collide with in boot image recovery resulting in no recovery at all. So, you need to get rid of Fota recovery to use internal one. For that do this in fastboot: fastboot erase recovery; then fastboot reboot...
Click to expand...
Click to collapse
Thank you! That did it.
But I still dont quite understand what happened here.
So i had 2 partitions, fota and recovery, each having a recovery installed. 'fastboot erase' does delete the one in the recovery partition, leaving only the one in fota.
That sounds kind of wrong for me, because I do want to use the recovery I install via fastboot.
Xecu said:
Thank you! That did it.
But I still dont quite understand what happened here.
So i had 2 partitions, fota and recovery, each having a recovery installed. 'fastboot erase' does delete the one in the recovery partition, leaving only the one in fota.
That sounds kind of wrong for me, because I do want to use the recovery I install via fastboot.
Click to expand...
Click to collapse
Xperias don't have recovery partition. Fota is used by stock firmware only, so it is available in custom roms, hence recovery image could be installed there. However, the normal way for custom roms is to incorporate recovery into boot image, which is faster. This was until lollipop, when the not so smart folks at Cyanogen, gave up on CWM (which was always in boot image) and came up with their own recovery. CM recovery does not work, so TWRP guys figured out a way to install their recovery in Fota, instead of having users/developers decompiling boot image, replacing CM recovery with TWRP and recompiling the image again. That's what I do in CM based kernels, but Slimrom folks use TWRP in boot by default.
So, when you did fastboot erase recovery, you got rid of recovery in fota partition. Now, you have TWRP in boot image.
Running it for 2 days now and I am highly satisfied.
I downgraded from Lollipop (tried CM, crDroid, another CM-Based Rom and Custom Stock) because each Rom caused 2 main issues: Runtime decreased from 2 days to 1 day and the infamous touch screen issues.
Running this Rom, these issues are gone. I am again at 2 days runtime and I can finally write longer messages without beeing bothered by an unresponsive screen. The system feels reliable again.
Only issue i found so far, is that my headphones are sometimes not recognized. In these cases, I have to unplug and plug them in again until the system recognizes them. I had the same issue when I was on KitSlim_AMG, but not on stock. So this might be a bug in the SlimBean / CM Code-Base.
Xecu said:
Running it for 2 days now and I am highly satisfied.
I downgraded from Lollipop (tried CM, crDroid, another CM-Based Rom and Custom Stock) because each Rom caused 2 main issues: Runtime decreased from 2 days to 1 day and the infamous touch screen issues.
Click to expand...
Click to collapse
You are forgetting the heat issue, which requires RECALL. I am not a huge gamer, but CPU can easily get to 75-80 degrees after using Firefox/Fennec for about 10 minutes. Then flickering and other heat protection kick in. Note, that most users won't notice overheat, because glass is not a very good heat conduit. They just complain of backlight flickering. However, if you enable CPU stats in developer options, you can see the temperature on screen. This is a shame (overheating), especially that LP has been around for about 7 months to no avail. You can't blame the processor, since there is no heat issue on kitkat and jb.
Lollipop, in my view, is the worst ever android version: linux (which is great) + google poop (google does what it does best) = lollipop. Really, the name should be Lollipoop.
I got another question
Logcat seems to be disabled, because /dev/log/main is not created. Is there a way to activate it?
Xecu said:
I got another question
Logcat seems to be disabled, because /dev/log/main is not created. Is there a way to activate it?
Click to expand...
Click to collapse
Logging is disabled in kernel for security. You can get a few apps on f-droid for logcat...
New build
Rom updated to include January 2016 security patches. See OP for download and description.
optimumpro said:
Rom updated to include January 2016 security patches. See OP for download and description.
Click to expand...
Click to collapse
Thank you for continuing to support KitKat I'll try the new build tomorrow
So the boot image doesn't have a kernel? Do I have to fastboot flash recovery recovery.img if I don't have the bootloader update?
Gents,
Hi!! This is my first post here!
Okay so I want to start off by telling you that I am a beginner with all this. I have a Galaxy I747 which I started by rooting because the battery life sucked really bad and it was frustrating to have a dead phone by noon. So I did that and started tweaking stuff. Long story short I was getting rid of bloatware and managed to delete the logsprovider file which messed up my phone. I didn't know about titanium backup at the time but shortly found out haha now I have the paid app. I also downloaded TWRP recovery thankfully. Anyways... In the middle of trying to get the logsprovider file back my phone froze in the reboot process and it only loaded up to the ATT symbol and froze there. I was able to get into the TWRP recovery and I was going to install the stock ROM to try and get it unbricked. I couldn't get any of those zip files to load. I happened to stumble upon the ktoonsez build and it worked awesome. The only problems I have ran into is that the sim card doesn't show my contacts anymore. The phone doesn't even have that option to show contacts from the sim card. Also, when I have an incoming call, it puts a +sign in front of the phone number so I don't know who it is (unless I have everyone's phone number memorized) and when I call back it says that it is an international phone number. This is very annoying. I noticed that the build might be for a sprint phone? I don't know if this is any different from what I need since I have ATT phone with straight talk? I have googled and researched for days now and my wife is getting mad at all the time I have invested in research trying to figure out the incoming call thing. Can you please help me?
In the "About device" screen I have:
KitKat (4.4.2)
Baseband version: I747UCUFNJ2
Kernel version: 3.4.0-g2d4cae8 [email protected] #2
Build Number: KOT49H.L710VPUDND8
Hardware version: REV0.4
Thank you in advance!!
Jed Booth
Sounds like you have yourself a CDMA build on a GSM phone. If you want to run stock your best bet is to flash the nj2 ROM enewman posted.
forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006
If you want some debloated and optimized stock s3rx is a good choice, just look for the nj2 based release in the development section.
You're on the latest firmware so you are OK to flash the cm and aosp custom Roms based on lollipop and marshmallow too.
In download mode, do you see anything on the screen about warranty bit?
If you don't, you could flash a stock att rom from sammobile.com.
If you do, I recommend flashing twrp as a custom recovery and then flash cm12.1 to at least get the phone booted to make sure it still functions.
Its okay guys. I really do appreciate your help. I went ahead and got CM 12.1 on there and everything works perfectly with no bloatware or anything. Now I have lollipop installed and I also ran the google play store zip so that works too. You guys are awesome!!
http://forum.xda-developers.com/showthread.php?t=2682905&goto=newpost
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