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
Related
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
gvazquez82 said:
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
Click to expand...
Click to collapse
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
MrHaPpY66 said:
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
Click to expand...
Click to collapse
First of all thank you for trying to help me, I hope you are having a good Thanks Giving.
I used the thread you linked to, and downloaded the version with out knox. I followed the instructions
transferred ROM and flashed kernel file to SD card
used odin to flash TWRP,
used twrp to flash rom and kernel file.
and it takes the file thankfully, there's only one issue. My phone can't make or receive calls/texts. Is yours able to?
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Next Update
the bootloader I flashed apparently flashed to the external sd card? I flashed another one and it is booting from the internal sd. I had to flash a different modem the one in the bootloader/modem file I flashed from the link above didnt take? I got most everything sorted out, but im getting tired, it has been an all night adventure. its 08:23 est now
sorry for the delay in updating this I had to get some rest.
theramsey3 said:
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Click to expand...
Click to collapse
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
spongdangly said:
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
Click to expand...
Click to collapse
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I will give that a shot, but what's an APN, sorry. And how do I create one, and is it needed for me to do so?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
It should be, I'm working right now so I don't have time to fine the guide on how to inject your IMEI. If I remember correctly it involves using QPST. If you have an old (or any) working Nandroid backup that should fix the problem.
FYI, make sure you don't use the guide for the international S3 as it has different hardware and folder structure/contents.
As for the APN, it should automatically fill itself in since it reads it off the SIM Card (I might be wrong).
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I tried it and it work!!!!!!!!!!!!!!!!!
67 texts just came in. Sir, I thank you oh so kindly. You have made this gloomy rainy day oh so joyous.
No problem. Glad I could help you.
The real credit should go to -Mr.X-, loserskater and anyone else(no disrespect there were alot of files) whose stuff I tried to flash lastnight thank you all in the dev community who contribute.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
gvazquez82 said:
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
Click to expand...
Click to collapse
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
flexfulton said:
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
Click to expand...
Click to collapse
do you know of a good stable kit kat like ROM I could use for the s3? And any speculation as to why the ROMs werent taking for me?
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.
Hey all,
I apologize if there is a thread for this already. I have the Sprint GS3 that I made the terrible, terrible mistake of upgrading to the stock 4.3 to give it a try and see if I like it.
After some scary moments trying to go back to the beloved CyanogenMod and bricking the device, I found I could install Cyanogenmod using their self-installer after restoring the phone to stock in Kies.
I'm running Cyanogenmod now, but there is an update available and when I try to let it update, it reboots into recovery, gives the sad broken android graphic, and reboots. I've not been able to install anything ROM related since.
Is Knox preventing the update, and is there a workaround to get the update to install without wiping the device back to stock?
emike09 said:
Hey all,
I apologize if there is a thread for this already. I have the Sprint GS3 that I made the terrible, terrible mistake of upgrading to the stock 4.3 to give it a try and see if I like it.
After some scary moments trying to go back to the beloved CyanogenMod and bricking the device, I found I could install Cyanogenmod using their self-installer after restoring the phone to stock in Kies.
I'm running Cyanogenmod now, but there is an update available and when I try to let it update, it reboots into recovery, gives the sad broken android graphic, and reboots. I've not been able to install anything ROM related since.
Is Knox preventing the update, and is there a workaround to get the update to install without wiping the device back to stock?
Click to expand...
Click to collapse
I will give you my two cents. First, rooting and installing custom ROM's should not be done using magical wonderful "one click" processes or apps that will do it for you. The Cyanogen Installer was a huge disservice to the rooted community in my opinion. Users need to get their hands dirty when rooting, so that they know how to work through problems forwards and backwards. That being said, I would highly recommend following this procedure to make sure your phone is rooted properly and running the correct recovery (Philz Touch, which is unbelievably awesome); my friend @goku2778 did a very nice job putting this tutorial together:
http://forum.xda-developers.com/showthread.php?t=2596697
After that, just download the ROM (or ROM's, I like to run various ones at any given time) from the proper sources, and flash them yourself.
I'm against one-click stuff myself. I've been rooting and running custom roms since my original Evo 4g.
If bricking my device after trying to roll back to a custom rom after Knox did it's business, and then recovering back isn't getting my hands dirty, then I don't know what is. I've spent plenty of time in adb. This issue though has me boggled. Why can the installer put a custom rom on when attempts to flash a custom rom (usually run nightlies) brick the device?
Thanks for the link, I'm taking a look into it now.
emike09 said:
I'm against one-click stuff myself. I've been rooting and running custom roms since my original Evo 4g.
If bricking my device after trying to roll back to a custom rom after Knox did it's business, and then recovering back isn't getting my hands dirty, then I don't know what is. I've spent plenty of time in adb. This issue though has me boggled. Why can the installer put a custom rom on when attempts to flash a custom rom (usually run nightlies) brick the device?
Thanks for the link, I'm taking a look into it now.
Click to expand...
Click to collapse
Didn't mean to imply that you weren't getting your hands dirty in general, just the way I word that rant every time I give it! My understanding is that there are compatibility issues between the CM installer and Knox, so yes, that is probably the basis of your problem. The combination of Philz Touch recovery and SuperSU that @goku2778 uses in his tutorial should solve your problems, it is the combination I have been recommending to VM and Boost users on Android Forums for a while now, with great success.
Mr. Struck said:
Didn't mean to imply that you weren't getting your hands dirty in general, just the way I word that rant every time I give it! My understanding is that there are compatibility issues between the CM installer and Knox, so yes, that is probably the basis of your problem. The combination of Philz Touch recovery and SuperSU that @goku2778 uses in his tutorial should solve your problems, it is the combination I have been recommending to VM and Boost users on Android Forums for a while now, with great success.
Click to expand...
Click to collapse
If memory serves there is a zip out there somewhere that flashes Knox apps away. Furthermore if it's a Boost or VM device you have to edit the updater script to make a Sprint ROM flash successfully.
Deucalion29710 said:
If memory serves there is a zip out there somewhere that flashes Knox apps away. Furthermore if it's a Boost or VM device you have to edit the updater script to make a Sprint ROM flash successfully.
Click to expand...
Click to collapse
The DeSamsungnizer zip is part of the tutorial by @goku2778, but keep in mind that this just takes care of the Knox apps, the actual bootloader is never ever going away unfortunately. And yes, for any users of VM or Boost who are reading this, there is extra work involved once the custom recovery has been installed and root has been successfully achieved.
Galaxy s3 on Virgin Mobile running cm11
I recently upgraded my s2 which was running cyanogenmod 11. I rooted and flashed everything myself with no difficulty. But after I switched that phone to an s3 I have had a ton of issues. My s3 was for Virgin Mobile (sgh-I747M) and nothing supported it. I was able to root and install clockworkmod with a little bit of difficulty. It wasn't until I tried installing cyanogenmod that it got really tough. Flashing would fail and at that point I didn't have an os so I thought I downloaded stock but was wrong when I hard bricked my phone. Anyways to the point. I ended up using the cyanogenmod installer which worked perfectly fine but now I can't update or download any nightlys. I'm not sure if it is because cyanogen had to install a custom kernel or not. When I go into system updates it says "your system is up to date. There is only one button that just checks for updates. Does anyone know how to fix this and allow me to install nightlys?
- Eric
Will CM installer work on S3-i9300(Int) version with 4.3 already installed?
Hi,
I am using the International version of SGS3- GT i9300. I dont know any of the process of rooting or installing a new version of android. But recently i have come across the cyangonmod installer app which i heard does all the work for us. I want to ask this doubt is that will the installation cause any problem if my S3 is already updated to 4.3 version? I am hearing people saying the KNOX might cause error. Should i wait for the CM 11 stable version or just give it a try ?
Thanks.
ericandbailey said:
I recently upgraded my s2 which was running cyanogenmod 11. I rooted and flashed everything myself with no difficulty. But after I switched that phone to an s3 I have had a ton of issues. My s3 was for Virgin Mobile (sgh-I747M) and nothing supported it. I was able to root and install clockworkmod with a little bit of difficulty. It wasn't until I tried installing cyanogenmod that it got really tough. Flashing would fail and at that point I didn't have an os so I thought I downloaded stock but was wrong when I hard bricked my phone. Anyways to the point. I ended up using the cyanogenmod installer which worked perfectly fine but now I can't update or download any nightlys. I'm not sure if it is because cyanogen had to install a custom kernel or not. When I go into system updates it says "your system is up to date. There is only one button that just checks for updates. Does anyone know how to fix this and allow me to install nightlys?
- Eric
Click to expand...
Click to collapse
did you figure out how to get nightly updates, from cyanogenmod installer ? I want to try the cyanogen installer to get cm 11 on my gs2 and gs3 (my specific devices are not on the cyanogenmod devices list, so i'm hesitant ) .. please respond .. anyone who can help ..
Hello All,
Due to my endless frustrations, this might be a long one so please bear with me!
So I purchased a Verizon Global HTC ONE M7 from the States, I am currently in Nigeria and the only thing that makes me sadder and more frustrated than the state of my phone right now is the incessant terror attacks in the country! Initially, almost everything worked fine when i popped in my new Etisalat sim card into the phone, except for the mobile hotspot (which just conveniently turns out to be the one of the top 3 most important features in a phone for me - probably the feature I use the most) this message kept popping up about how hotspot couldn't be used without a VZW sim, etc (also with the non-verizon sim warning when the phone boots up). I tried all I could, eventually deciding to flash a new ROM to clear out everything Verizon and start fresh.
Enter Viperone 6.2.0 - everything worked initially, but after a few weeks i noticed if I did anything like watch a youtube video or download something over a few MBs 90% of the time the data drops (no visible signs like changes from E to H or 3g or the likes, everything looks the same, just that the data stops), toggle mobile data on/off and data connection is back. It worsened and became more frequent over time. Upgraded to Viperone 6.2.1, no difference, so i figured its probably the viperone rom.
Enter Cyanogenmod - http://forum.xda-developers.com/ver...-oneplus-one-stock-rom-cm11s-verizon-t2857425 - and its the same exact issue from the beginning, so im guessing its not to do with the ROM at all (though there are one or two niggling issues with the ROM - cant change BBM display pic, etc)?! I've really tried to comb through the forum and see what makes sense that i could try without bugging y'all - I did a factory reset, wiped everything completely and its the same thing.
I've seen suggestions to similar issues like: flash stock recovery, update radio/firmware/kernel, flash back to custom recovery and some other things which are beginning to sound quite dangerous in my ignorance!! I did believe updating the firmware made sense but after digging deeper, i must honestly say i'm quite confused on what to do. what radio/firmware/kernel works with what software version, etc- most firmware that i've seen are 4.4.3 compatible, while this ROM is 4.4.4., some of them seem to be for stock ROMs only and a lot of other confusions.
So, I'm not gonna be a hero and brick my phone from trying to do what i do not understand, instead here i am, hat in hand, crying out for help after suffering for 3 months! Its really frustrating as, downloads break causing me to lose data, skype or MSLync calls always break and im beginning to look unprofessional to people! This is why I have decided to put up a post of my own specific to my case so i don't medicate for someone else's ailments. So please........ WHAT EXACTLY DO I DO??
PHONE DETAILS (typing it out as i've just realized on this ROM i can't take screenshots with Power+Home button combo anymore and can't be bothered at this point!!!)
ANDROID VERSION: 4.4.4
BASEBAND VERSION: 1.12.41.1112_2
KERNEL VERSION: 3.4.82-gfe09065; [email protected] #1; Wed oct 8 01:36:03 PDT 2014
BUILD DATE: SUN AUG 3 23:00:51 PDT 2014
BUILD NUMBER: CYANOGENMOD 11S v5 (Verizon)
SELinux status: Enforcing
Thanks
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Can you flash stock recovery from Santod's firmware thread and do a factory reset? It could be a corrupt nv partition which would only be fixed by doing a factory reset via stock recovery. (If you must, make a nandroid of system and data in your recovery of choice so you can restore your data if you wish).
Uzephi said:
Can you flash stock recovery from Santod's firmware thread and do a factory reset? It could be a corrupt nv partition which would only be fixed by doing a factory reset via stock recovery. (If you must, make a nandroid of system and data in your recovery of choice so you can restore your data if you wish).
Click to expand...
Click to collapse
Thanks for the responses folks, i'll try out your suggestions and revert..
8100
brymaster5000 said:
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Click to expand...
Click to collapse
So.. i found time to get to this and decided to go with your suggestion of Santod's stock rom... and now, i think i've done the unthinkable!! After WIPING EVERYTHING "All partitions except SD!" as the instructions stated... i attempted to reboot into bootloader and got a message saying "no OS installed, are you sure you want to reboot"... that scared me a bit, but i thought surely, it must be part of the process! I proceed to reboot to bootloader to flash the firmware and i cant seem to do anything!!
Fastboot is stuck on " waiting for device" for everything i try.
Also, i rebooted back into recovery and attempted to install the stock rom: i get the error message "unable to open zip file"..
Have i destroyed my phone with my own hands, people? :crying:
Mr HaRR said:
So.. i found time to get to this and decided to go with your suggestion of Santod's stock rom... and now, i think i've done the unthinkable!! After WIPING EVERYTHING "All partitions except SD!" as the instructions stated... i attempted to reboot into bootloader and got a message saying "no OS installed, are you sure you want to reboot"... that scared me a bit, but i thought surely, it must be part of the process! I proceed to reboot to bootloader to flash the firmware and i cant seem to do anything!!
Fastboot is stuck on " waiting for device" for everything i try.
Also, i rebooted back into recovery and attempted to install the stock rom: i get the error message "unable to open zip file"..
Have i destroyed my phone with my own hands, people? :crying:
Click to expand...
Click to collapse
FALSE ALARM FOLKS!!! I decided to attempt flashing the CM11 rom i just uninstalled and it worked. Turns out its a known issue with the .zip file for that rom - i am now re-downloading from another mirror. Meanwhile the Fastboot thing was just a driver issue - though i'm surprised because i had all the drivers installed on the system and have used fastboot successfully - anyway i reinstalled the drivers and all was well with fastboot again.
NB: Don't get tired of me just yet please!
brymaster5000 said:
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Click to expand...
Click to collapse
hello!
Thanks for your ideas guys. I'm currently running Santod's stock rom (which is brilliant, i must say, i actually wanna stay on this rom) since friday - thought i'd give it the whole weekend and see how it goes.. BUT! i still get thoseconnection drops.. and frequently too.
Any other ideas on what the issue could be?
Mr HaRR said:
hello!
Thanks for your ideas guys. I'm currently running Santod's stock rom (which is brilliant, i must say, i actually wanna stay on this rom) since friday - thought i'd give it the whole weekend and see how it goes.. BUT! i still get thoseconnection drops.. and frequently too.
Any other ideas on what the issue could be?
Click to expand...
Click to collapse
If doing factory reset from stock recovery doesn't fix it, it is most likely a burned SIM. It has happened to me. (Average 150+ GB a month in data, so I burn em easily)
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uz has it right, you need to flash a stock recovery and THEN do a factory reset, then reload your custom recovery and rom. I had the exact same issue before. Or you could flash an ruu file which would reset the partitions also.
ccarr313 said:
Uz has it right, you need to flash a stock recovery and THEN do a factory reset, then reload your custom recovery and rom. I had the exact same issue before. Or you could flash an ruu file which would reset the partitions also.
Click to expand...
Click to collapse
Hey folks, apologies for the touch and go nature of this thread - i just don't have a lot of free time on my hands and other reasons..
Anyhow, i think I want to try out ur suggestion of flashing an RUU - I noticed that im unable to actually enter recovery after flashing stock recovery from Santod's thread (i flashed the latest three recoveries). I can get to bootloader, but when i select recovery, the phone goes black for a few seconds and then i get the RED TRIANGLE WITH THE EXCLAMATION MARK INSIDE, obviously something's wrong, few seconds later the phone reboots itself into normal mode. I did do a factory reset from bootloader, but issue persists.
So now to the RUU flashing issue - could you suggest one for me to flash?
By the way though, isn't flashing an ruu gonna take me back to stock completely (as in back to S-ON, ETC..)?
Thanks a whole bunch - IM DETERMINED TO GET THIS TO WORK!!!
Mr HaRR said:
Hey folks, apologies for the touch and go nature of this thread - i just don't have a lot of free time on my hands and other reasons..
Anyhow, i think I want to try out ur suggestion of flashing an RUU - I noticed that im unable to actually enter recovery after flashing stock recovery from Santod's thread (i flashed the latest three recoveries). I can get to bootloader, but when i select recovery, the phone goes black for a few seconds and then i get the RED TRIANGLE WITH THE EXCLAMATION MARK INSIDE, obviously something's wrong, few seconds later the phone reboots itself into normal mode. I did do a factory reset from bootloader, but issue persists.
So now to the RUU flashing issue - could you suggest one for me to flash?
By the way though, isn't flashing an ruu gonna take me back to stock completely (as in back to S-ON, ETC..)?
Thanks a whole bunch - IM DETERMINED TO GET THIS TO WORK!!!
Click to expand...
Click to collapse
That is in fact stock recovery man. When you get the triangle press volume up and power at the same time. You will enter stock recovery.
Any of my ruu will run fine. You won't lose s-off or unlocked status. You flash them in boot loader fastboot mode.
dottat said:
That is in fact stock recovery man. When you get the triangle press volume up and power at the same time. You will enter stock recovery.
Any of my ruu will run fine. You won't lose s-off or unlocked status. You flash them in boot loader fastboot mode.
Click to expand...
Click to collapse
HA! and now i feel :silly: !!
Bless your soul! i'll give it a go shortly...
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