Hi,
I have a samsung s3 sprint 4.3 MK3
it is already rooted and has CWM recovery
i want to change the modem but i make a wrong flash using LG2 Modem
and now my mobile has IMEI and BASEBAND UNKNOWN even the wifi is not working anymore
Please someone help me to fix this problem
thank you
sobri46 said:
Hi,
I have a samsung s3 sprint 4.3 MK3
it is already rooted and has CWM recovery
i want to change the modem but i make a wrong flash using LG2 Modem
and now my mobile has IMEI and BASEBAND UNKNOWN even the wifi is not working anymore
Please someone help me to fix this problem
thank you
Click to expand...
Click to collapse
try a factory wipe/reset maybe? you'll still be rooted after that...couldn't hurt till someone else may chime in
this is also why you always, always, always make nandroid backups via recovery before doing anything to change your system
goku2778 said:
try a factory wipe/reset maybe? you'll still be rooted after that...couldn't hurt till someone else may chime in
this is also why you always, always, always make nandroid backups via recovery before doing anything to change your system
Click to expand...
Click to collapse
i had flash back to MK3 modem back but no change on imei and baseband
i had make a factory reset but also no change
sobri46 said:
i had flash back to MK3 modem back but no change on imei and baseband
i had make a factory reset but also no change
Click to expand...
Click to collapse
damn...hopefully someone can help you out before I would say use my 2nd link in my signature and completely reinstall the entire 4.3 operating system and then root all over again...did you attempt while on the stock rom, going to settings>more>system update and then update your prl and profile?
edit...actually, you can try this, 4.3 mk3 stock roms already rooted...see what happens, it has some other stuff too in it that might help you out with your errors:
http://forum.xda-developers.com/showthread.php?t=2541900
PRL and Profile reset-from the dialer on a TW ROM, dial ##72786# it will reset itself after two automatic reboots (don't touch anything while process is occurring).
Do you mean I should flash tw rom first ?
Then call ##72786# and the phone will work fine as before
Can I flash tw rom because my stock rom is 4.3 ?
And I hear that if we have 4.3 rom we cannot downgrade to anyrom
sobri46 said:
Do you mean I should flash tw rom first ?
Then call ##72786# and the phone will work fine as before
Can I flash tw rom because my stock rom is 4.3 ?
And I hear that if we have 4.3 rom we cannot downgrade to anyrom
Click to expand...
Click to collapse
Yes, you need to be running any TW based ROM (stock, Wicked Sensations, MOAR, etc.) to run a PRL and Profile reset from your dialer, this function does not work on AOSP based ROM's. Hopefully you have a backup of your stock ROM, otherwise you will need to download one, and be patient because the file size is huge.
As to the second part of your post, stock is TW, and the downgrade rumor is only applicable if you 1) Have the Knox bootloader and 2) try to use Odin to change to a different firmware version that contains a non-Knox bootloader. You can flash any Android version of any ROM that you want when using custom recovery like Philz Touch.
Are you on 4.3? If so, no modem lower than MK3 will give you data if you do that
thank you guys and especially mr struck i already make the phone work again after dial ##72786#
and also i use someone trick that i should take out the battery for an hour after dial the code , so i take it out for a whole day and when i try the phone everything is working normally again.
thank you
Related
For those of you who keep getting stuck on the splash screen after trying to restart your phone after installing a 4.3 ROM.
My steps were (and I take no credit for this, I can't remember who had said to do this and I wasn't logged in so I couldn't click the thank you button):
*Note* If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone. The Stock ROM contains the Bootloader which should never be downgraded. Fyi: the Bootloader is not the Baseband, the Baseband is just what Modem you're using.
1. Use Odin to flash the latest stock ROM
2. Enter the stock recovery and do a factory reset and clear the cache (I did both twice just to make sure)
3. Use Odin to flash the stock rooted ROM.
4. Enter the stock recovery and do a factory reset and clear the cache. (This might not be necessary but I did anyways just to make sure)
5. Use Odin to flash a custom recovery (TWRP 2.6.0.0 was the newest recovery when I did this last week)
6. Enter the custom recovery and wipe everything, then flash whatever 4.3 based ROM and then flash GApps if you want.
*Note* It seemed like the phone was hanging on the splash screen after either the initial boot or the first restart (I can't remember which, it's been a week) but it did boot and reboot fine.
I hope this helps out some people since I found it to be quite irritating that I could install a 4.3 ROM and set everything up but when I went to restart it would hang at the splash screen (going into the recovery and clearing the cache/dalvik cache wasn't helping).
Are you basically saying to revert back to stock settings and redo the entire root process again?
Sent from my SGH-I747 using xda app-developers app
bullet2binary said:
Are you basically saying to revert back to stock settings and redo the entire root process again?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah, from what I had read that seemed to be necessary since I had used Odin to update the bootloader (MF1 since my phone is the M variant) by itself when the newest Stock ROM had come out a while ago. I still flashed the newest Stock ROM (same MF1 bootloader for the M variant) but the first time I did it I forgot to enter the Stock Recovery to do a Factory Reset and Clear the Cache and ended up stuck on the splash screen of a 4.3 ROM after flashing a custom recovery. So I needed to reflash back to stock and start over.
Going into the Stock Recovery and doing a Factory Reset and Clearing Cache is necessary and doesn't take much time at all so you may as well do it just to be sure. I also recommend backing up your IMEI if you haven't done it yet.
spongdangly said:
Yeah, from what I had read that seemed to be necessary since I had used Odin to update the bootloader (MF1 since my phone is the M variant) by itself when the newest Stock ROM had come out a while ago. I still flashed the newest Stock ROM (same MF1 bootloader for the M variant) but the first time I did it I forgot to enter the Stock Recovery to do a Factory Reset and Clear the Cache and ended up stuck on the splash screen of a 4.3 ROM after flashing a custom recovery. So I needed to reflash back to stock and start over.
Going into the Stock Recovery and doing a Factory Reset and Clearing Cache is necessary and doesn't take much time at all so you may as well do it just to be sure. I also recommend backing up your IMEI if you haven't done it yet.
Click to expand...
Click to collapse
This seems to have done the job. Running PAC 4.3 right now. I've rebooted successfully once so far.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Exactly what I ended up doing after nothing else was working. After getting it hanging the first time, even flashing 4.2 roms was giving me boot issues. After reverting back to stock and reflashing I'm now running the 9/1 Pac nightly and the 8/31 kt747 kernel.
I'm probably 10+ reboots in without issue and I flashed the kernel separately!
bullet2binary said:
This seems to have done the job. Running PAC 4.3 right now. I've rebooted successfully once so far.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
exodus454 said:
Exactly what I ended up doing after nothing else was working. After getting it hanging the first time, even flashing 4.2 roms was giving me boot issues. After reverting back to stock and reflashing I'm now running the 9/1 Pac nightly and the 8/31 kt747 kernel.
I'm probably 10+ reboots in without issue and I flashed the kernel separately!
Click to expand...
Click to collapse
I'm glad to hear that this seems to be the proper fix. That's odd that you were having trouble with 4.2 ROMs, but then again I'd been running 4.2 ROMs on my phone since they first started rolling out. It's kind of annoying that everyone's S3 seems to be slightly different then the next.
Yeah this was a weird one all right. Just glad this post had a solution
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
glad i found this otherwise my first noob post would have truly been a noob move. Thanks wouldn't have guessed that fix for a few days at least.
verified it works. but it did require some weird time dealing with a bootloop issue on stock recoveries. had to find a .tar version of CWM to flash via odin for the final result.
Still Stuck at Splash Screen after trying to upgrade to 4.3
Background:
I had been running task's rom since 4.1.x. Upgraded to 4.2 with not problems and I kept the rom current. Tried to upgrade to 4.3 and that is where the problems started. It appeared to work, saw that Google was updating a number of apps but then then I kept getting error messages regarding various about various processes stopping unexpectedly. Rebooted the phone and it came up with Task's kernel splash screen where it remains frozen.
I can get into TWRP (v2.3.3.1) recovery and into Download mode.
I have tried wiping Cache and Dalvik Cache
I have wiped System
I have done a Factory Reset
I have Formatted Data
I have used Odin twice to get back to stock (I747UCDLK3) and both times it says "passed."
When I try to reboot it, however, it comes back to Task's Kernel splash screen (I do not see the Samsung screen)
Any help or suggestions would be great.
UPDATED: Found an older update from April and was able to restore it. Still wondering why 4.3 wouldn't take.
This Works
I was skeptical, but this actually works! Now running Task's 4.3 on my bell i747m without any problems!
Thanks for the tip OP :good:
spongdangly said:
For those of you who keep getting stuck on the splash screen after trying to restart your phone after installing a 4.3 ROM.
My steps were (and I take no credit for this, I can't remember who had said to do this and I wasn't logged in so I couldn't click the thank you button):
1. Use Odin to flash the latest stock ROM
2. Enter the stock recovery and do a factory reset and clear the cache (I did both twice just to make sure)
3. Use Odin to flash the stock rooted ROM.
4. Enter the stock recovery and do a factory reset and clear the cache. (This might not be necessary but I did anyways just to make sure)
5. Use Odin to flash a custom recovery (TWRP 2.6.0.0 was the newest recovery when I did this last week)
6. Enter the custom recovery and wipe everything, then flash whatever 4.3 based ROM and then flash GApps if you want.
*Note* It seemed like the phone was hanging on the splash screen after either the initial boot or the first restart (I can't remember which, it's been a week) but it did boot and reboot fine.
I hope this helps out some people since I found it to be quite irritating that I could install a 4.3 ROM and set everything up but when I went to restart it would hang at the splash screen (going into the recovery and clearing the cache/dalvik cache wasn't helping).
I hope I posted this in the right section but apologies if it's not.
Click to expand...
Click to collapse
If this works you're a life saver! I've been posting around 4.3 threads about this for weeks and no one came up with a decent answer....
Tried reflashing stock with root but didn't work... i'll try your way, see if that works
Gonna try this tonight!!!
Thanks!
I posted in the CM thread about this, but thought I would pass it along.. I didn't have to go back to stock non-rooted. What I did:
I odin'd Mr. Robinson's LK3 rooted
Factory reset from the 3e recovery
Rebooted
Odin'd twrp
Restored nandroid of CM
Good to go.
Solved
Thanks, also works for i727 skyrocket
wont this brick people phones flashing back 4.1.1 stock ? im on stock 4.3 stuck on samsung galaxy s3 logo meaning flashing back to latest stock rom using odin 4.1.2? 4.3 stock rom or 4.3 custom roms?
Kastro1784 said:
wont this brick people phones flashing back 4.1.1 stock ? im on stock 4.3 stuck on samsung galaxy s3 logo meaning flashing back to latest stock rom using odin 4.1.2? 4.3 stock rom or 4.3 custom roms?
Click to expand...
Click to collapse
spongdangly said:
1. Use Odin to flash the latest stock ROM
Click to expand...
Click to collapse
If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone.
I'll add a note to the OP about not attempting to downgrade to an older Stock ROM though.
spongdangly said:
If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone.
I'll add a note to the OP about not attempting to downgrade to an older Stock ROM though.
Click to expand...
Click to collapse
what framware did you flash to get 4.3 back working ? a leaked 4.3 Rom with no root ? thien reflash the stock 4.3 ?
Kastro1784 said:
what framware did you flash to get 4.3 back working ? a leaked 4.3 Rom with no root ? thien reflash the stock 4.3 ?
Click to expand...
Click to collapse
When I had done this back in August, I flashed the Rogers 4.1.2 Stock ROM since that was the latest stock firmware at the time and I have a Canadian S3.
If you had already flashed or been on the Stock AT&T 4.3 ROM, I'd recommend reflashing the latest Stock AT&T 4.3 ROM and following the instructions in the OP. Just make sure that you don't attempt to flash an older version of the Stock ROM that you were already on since you will brick your phone. The Stock ROM contains the bootloader and that cannot be downgraded. I don't have an American S3 since I'm Canadian so I don't know which 4.3 bootloader is the newest although I'm sure a quick search would answer that for you.
spongdangly said:
When I had done this back in August, I flashed the Rogers 4.1.2 Stock ROM since that was the latest stock firmware at the time and I have a Canadian S3.
If you had already flashed or been on the Stock AT&T 4.3 ROM, I'd recommend reflashing the latest Stock AT&T 4.3 ROM and following the instructions in the OP. Just make sure that you don't attempt to flash an older version of the Stock ROM that you were already on since you will brick your phone. The Stock ROM contains the bootloader and that cannot be downgraded. I don't have an American S3 since I'm Canadian so I don't know which 4.3 bootloader is the newest although I'm sure a quick search would answer that for you.
Click to expand...
Click to collapse
There is no latest Stock AT&T 4.3 ROM right now to reflash if you're already on the Stock AT&T 4.3 ROM. We cannot keep telling people this. If so, tell us how, because no one has, as of yet.
I've seen entirely too many posts telling people who are having trouble or phone is soft bricked on the Stock AT&T 4.3 ROM to flash or Odin back to stock. Then when asked how, the discussion ends.
That's also one of the reasons why I refuse to upgrade to 4.3 right now. At least I can still Odin back to stock as an option if something does goes wrong, but who am I to tell anyone to stay away from the latest toy, I mean update?
shortydoggg said:
There is no latest Stock AT&T 4.3 ROM right now to reflash if you're already on the Stock AT&T 4.3 ROM. We cannot keep telling people this. If so, tell us how, because no one has, as of yet.
I've seen entirely too many posts telling people who are having trouble or phone is soft bricked on the Stock AT&T 4.3 ROM to flash or Odin back to stock. Then when asked how, the discussion ends.
That's also one of the reasons why I refuse to upgrade to 4.3 right now. At least I can still Odin back to stock as an option if something does goes wrong, but who am I to tell anyone to stay away from the latest toy, I mean update?
Click to expand...
Click to collapse
I'm sorry that I'm unable to help. As I had mentioned I have a Canadian Rogers phone (since I'm in Canada) so I don't know what's going on with the AT&T Stock 4.3 ROMs other then the fact that lots of people are having problems.
If you never flashed or did an OTA update to 4.3 then I'd suggest flashing the Stock 4.1.2 ROM. That or try what Ozark_8125 did since it saves you a couple steps (just make sure that LK3 isn't an older ROM than the one you were on).
If you're unsure what bootloader is currently on your phone and your phone is rooted I'd highly recommend downloading one of the many Root Check apps from the Play Store to verify which bootloader you're currently on.
*Note* I don't know which bootloader is for the 4.1.2 AT&T ROM nor do I know which bootloader came with the 4.3 ROMs. I'm sure a simple search would answer that for you.
Ozark_8125 said:
I posted in the CM thread about this, but thought I would pass it along.. I didn't have to go back to stock non-rooted. What I did:
I odin'd Mr. Robinson's LK3 rooted
Factory reset from the 3e recovery
Rebooted
Odin'd twrp
Restored nandroid of CM
Good to go.
Click to expand...
Click to collapse
Samsung fixed my phone free thanks for the help
Sent from my SAMSUNG-SGH-I747 using Tapatalk
ok so as you all know ive been having this problem with my note 2 eversince i flashed a mk4 rom and updated prl firmware version i guess it updated my baseband and all sorts of things i flashed the odin wifi fix and it made mk4 wifi work and everything was glee.. well i wanted aosp 4.4.2 back because it was simply gorgious i guess i had a thing for it. well i went to flash it after wiping factory data reset and after it flashed i let it run for over 30 minuts and it never made it past the cyanogenmod boot screen so i assumed it was a bootloop or bad download. my answer to this is i believe its the baseband or prl version not letting me run this. because before i ran mk4 and did all the updates i could always revert back to 4.4.2 without a problem now all the sudden i cant even load any aosp 4.4 rom. i can load all of 4.2.2 4.1.2 all those aosp roms but not the newest rom which is frusterating. if anyone has a fix or a recamended solution please help me because i have done just about every factory reset availible such as billiards back to stock and some other one. both not helping.
below here is the data i have recorded from my phone
PRL 2011
Baseband L900VPAMC2
PRL and baseband should both be irrelevant. Your problem is most likely a corrupt download. Have you checked hash sums?
Skripka said:
PRL and baseband should both be irrelevant. Your problem is most likely a corrupt download. Have you checked hash sums?
Click to expand...
Click to collapse
i have redowloaded roms 2x and still no luck i reset the phone back to stock 5 times and still no luck it still bootloops makes me wonna sell the phone and be done with samsung.i should of never did the 4.3 rom because it gave me nothing but problems. i downloaded another aosp rom to my internal sd to see if my sd card was currupt and it did the same Bootloop. i have no clue what it could be. ive used CMW and tWrp and both did the same
How many times you've downloaded is completely irrelevant. You've either verified the md5 hash and thereby confirmed your downloads are good or you have not. I presume you have yet to do so.
Before any other steps can be advised you have to do that 1st basic step.
The download is good
im not sure what to do about this stupid problem but its aggrivating me to no end. ive done just about everysingle thing there is to make this work but it fails
zachdees said:
The download is good
im not sure what to do about this stupid problem but its aggrivating me to no end. ive done just about everysingle thing there is to make this work but it fails
Click to expand...
Click to collapse
One question...your baseband says MC2, did you unroot at any point following the MK4-upgrade (and wifi "fix") back to MC2? I have a theory, if you have not unrooted to MC2 firmware, and that is just because you didn't update radios...you might not like it...
The MK4 radio works fine IME with 4.4 ROMs FWIW.
i chose the oldest return to stock from billiards. i wanted to see if that fixes anything and it doesnt do squat. i just wonna figure out a resolution to this mess. my current baseband and prl and firmware version are
About device_______
Software version
L900VPALJC
Hardware version
L900.09
Baseband version
L900VPALJC
PRL IS STILL 2011
Device status custom
i did everysingle return to stock possible today and when i flash with either twrp philz recover cmw i still get bootloop. it doesnt load any further than the Samsung logo,
this leads me to belive that i have no clue
zachdees said:
i chose the oldest return to stock from billiards. i wanted to see if that fixes anything and it doesnt do squat. i just wonna figure out a resolution to this mess. my current baseband and prl and firmware version are
About device_______
Software version
L900VPALJC
Hardware version
L900.09
Baseband version
L900VPALJC
PRL IS STILL 2011
Device status custom
i did everysingle return to stock possible today and when i flash with either twrp philz recover cmw i still get bootloop. it doesnt load any further than the Samsung logo,
this leads me to belive that i have no clue
Click to expand...
Click to collapse
Crap...you just shot down my working theory.
In flashing 4.4 builds, you're using complete wipes? What GApps package are you using? ParanoidAndroid 4.4 Apps?
im doing a complete wipe and flashing the rom first to see if it even boots. and no go.
This doesnt make sense at all and makes me revert back to the baseband theory. i think somthing with the version of my phone has somthing to do with it.
the wifi patch wasnt the problem the recovery isnt the problem the only think i can think of is my phone is corrupt and wont flash 4.4.2 roms which aggrivates me. i want to get to the bottum of this
literally any aosp 4.4.2 rom bootloops.
the only one that booted up fine was omni rom and it didnt even have mobile data or signal seemed like it was for att or a gsm company because it had no support for my phone.
if i could just get ahold of a 4.4.2 kernal such as carbons trinity kernal or pretty much any 4.4.2 flashable kernal i think i could fix it as it seems that might also be the case
Did you try wiping your internal memory? I had a similar problem once, that was the solution.
Sent from my SPH-L900 using Tapatalk
zachdees said:
literally any aosp 4.4.2 rom bootloops.
the only one that booted up fine was omni rom and it didnt even have mobile data or signal seemed like it was for att or a gsm company because it had no support for my phone.
if i could just get ahold of a 4.4.2 kernal such as carbons trinity kernal or pretty much any 4.4.2 flashable kernal i think i could fix it as it seems that might also be the case
Click to expand...
Click to collapse
The 2.05b kernel of Plasma works fine with Omni. I've been using Omni builds for the last full month on my L900. Baseband is MK4 and PRL here is 2006.
No radios working sounds like you were using TWRP and not CWM or PhilZ recovery to a T. Maybe the latest TWRP has fixed its compatibility problems with 4.4+, but last I tried using TWRP to flash any 4,4 build-all it got me was no wifi/cell service. Be sure to use the recommended Paranoid Android GApps package for 4.4 with Omni.
Could you provide me with a link to the kernel that will work with cyanogen mod omni doesn't have data or mobile service
I have the philz
I don't flash any Google apps until i see that the rom is working which I've had no success. The weird thing with omni is that it doesn't even support sprint it only supports gsm
zachdees said:
Could you provide me with a link to the kernel that will work with cyanogen mod omni doesn't have data or mobile service
I have the philz
Click to expand...
Click to collapse
Plasma 2.05b0 can be found here, select the version appropriate to your device:
http://forum.xda-developers.com/showpost.php?p=48991763&postcount=866&nocache=1&z=8858325940594172
zachdees said:
I don't flash any Google apps until i see that the rom is working which I've had no success. The weird thing with omni is that it doesn't even support sprint it only supports gsm
Click to expand...
Click to collapse
Something has to be bizarre with your handset. Seriously, there's no other way to describe it. OmniROM for L900 is NOT GSM only, something in your flashing got altered in the middle of all your flashing. See my screencaps below if you don't believe me.
My only theory is that that "wifi fix" scrambled something in your radio for AOSP 4.4 ROMs....and that whatever it is isn't purged by a normal flash of a new/old baseband. It can't be the PRL as that is irrelevant and if you had a bad PRL it wouldn't work even under stock ROMs, and the baseband shouldn't matter but as you can see below I'm on baseband MK4 and I work fine.
let me revert back to stock one more time and do the 4.3 update and get the latest baseband version and ill report back to you after rooting and trying the omnirom or cm ok? i dont have a clue what the hell is going on as of now but its boggling my mind
OK so I'm on the latest baseband I flashed cm and no go kept sticking at the cm logo animation nothing else
I flash the kernel and it does the exact same. Fwi I'm using clockwork mod recovery
ok so i managed to get omni running without a problem the only issue is Root privilages. it doesnt have root. ive installes super su but it doesnt go into recovery and flash the binaries which doesnt make sense. ill try one more rom before i flash back to mk4 smoothest for a while. wish i could get this sorted out
zachdees said:
ok so i managed to get omni running without a problem the only issue is Root privilages. it doesnt have root. ive installes super su but it doesnt go into recovery and flash the binaries which doesnt make sense. ill try one more rom before i flash back to mk4 smoothest for a while. wish i could get this sorted out
Click to expand...
Click to collapse
Just flash supersu installable zip from recovery
i dont have the flashable zip
didnt see anything on the omni post either.
my question is why did this rom run without a flaw but when cm or pa flashes it has issues
I have the phone up and running and do not have a modem.
Here is where it is at:
CWM installed
SU installed
Android 4.2.2
Baseband M919UVUEMK2
Kernel 3.4.0-440244
Build JDQ39.M919UVUAMDB
I wish to move to 4.4.2 with the phone rooted.
I have tried to move to MDL with odin, but get a FAIL!
Could someone please help.
Thank you
Restored to factory and working with original image from TMobile.
williambs said:
I have the phone up and running and do not have a modem.
Here is where it is at:
CWM installed
SU installed
Android 4.2.2
Baseband M919UVUEMK2 Modem version
Kernel 3.4.0-440244
Build JDQ39.M919UVUAMDB Build ID
I wish to move to 4.4.2 with the phone rooted.
I have tried to move to MDL with odin, but get a FAIL!
Could someone please help.
Thank you
Click to expand...
Click to collapse
It looks like you already have the MK2 modem installed. You don't want MDL for TW4.3 or AOSP 4.4.x builds.
Your Build ID: Build JDQ39.M919UVUAMDB will change depending on which ROM you flash and has nothing to do with the modem.
lordcheeto03 said:
It looks like you already have the MK2 modem installed. You don't want MDL for TW4.3 or AOSP 4.4.x builds.
Click to expand...
Click to collapse
WIFI is not working and I wish to move to 4.4.2.
How do I get there?
Thank you
williambs said:
WIFI is not working and I wish to move to 4.2.2.
How do I get there?
Thank you
Click to expand...
Click to collapse
From what you posted, you are already on 4.2.2.
Also, when you say WiFi isn't working... do you mean it won't connect? Does it connect but you don't get any data? Are you getting the "connection unstable" warning? Could try using a different kernel.
lordcheeto03 said:
From what you posted, you are already on 4.2.2.
Also, when you say WiFi isn't working... do you mean it won't connect? Does it connect but you don't get any data? Are you getting the "connection unstable" warning? Could try using a different kernel.
Click to expand...
Click to collapse
WIFI will not turn on at all. switch does not move to ON when I slide it over
Thank you
Correction, wish to move to 4.4.2
williambs said:
WIFI will not turn on at all. switch does not move to ON when I slide it over
Thank you
Correction, wish to move to 4.4.2
Click to expand...
Click to collapse
In that case, I would say to go ahead and download whichever 4.4.2 ROM you want to run from either the Android Development or Original Development section. No TouchWiz ROMs are 4.4.2 so that means no WiFi calling if that's important. Grab a custom recovery (TWRP, CWM, etc) if you don't already have one. Make a backup of your current setup via recovery, then follow the installation instructions for whichever ROM you choose to go with.
You already have the correct modem for using 4.3+ and I see no reason why your WiFi issue should persist through a different ROM. I'd say you're ready. If you do still have WiFi issues once you update, try using a different kernel.
lordcheeto03 said:
In that case, I would say to go ahead and download whichever 4.4.2 ROM you want to run from either the Android Development or Original Development section. No TouchWiz ROMs are 4.4.2 so that means no WiFi calling if that's important. Grab a custom recovery (TWRP, CWM, etc) if you don't already have one. Make a backup of your current setup via recovery, then follow the installation instructions for whichever ROM you choose to go with.
You already have the correct modem for using 4.3+ and I see no reason why your WiFi issue should persist through a different ROM. I'd say you're ready. If you do still have WiFi issues once you update, try using a different kernel.
Click to expand...
Click to collapse
Alright, I will give it a try and reinstall KOT49H【4.4.2】Danvdh and see how it goes. Of course after doing a backup.
Thank you
Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/
dreammaster252 said:
Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/
Click to expand...
Click to collapse
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486
Larry2999 said:
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help
dreammaster252 said:
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help
Click to expand...
Click to collapse
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991
Larry2999 said:
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991
Click to expand...
Click to collapse
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?
dreammaster252 said:
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?
Click to expand...
Click to collapse
just to confirm, you re on ucuemjb bootloader, and installed/running Task650 4.4.4 rom 7.21.2014 (at this writing thats the latest update for the rom)
right?
sorry last time i tried to flash task650 rom, i got errors concerning the bootloader, went back to CM11 which has been my go-to-go rom and everything works fine, after you respond i will flash and get back to you on the network issues
thanks
Hello I want to back to the stock mod but I already build the kitkat.
Can I go back to stock mod? Please help me!
also I found this rom
http://forum.xda-developers.com/showthread.php?t=2766242
but my phone is from at&t, can I install this?
please help me!
That is my Sprint port (StockMod kk) just repackaged for flashing in odin.
To your original question, if updated to kk firmware, you can still run all the roms as before. Just you can only use the 4.4.2 modem. Some 4.3 rom threads say to use the 4.3 modem, but ignore that if updated to the new firmware.
Thank you
DocHoliday77 said:
That is my Sprint port (StockMod kk) just repackaged for flashing in odin.
To your original question, if updated to kk firmware, you can still run all the roms as before. Just you can only use the 4.4.2 modem. Some 4.3 rom threads say to use the 4.3 modem, but ignore that if updated to the new firmware.
Click to expand...
Click to collapse
Thank you! so I can not use this mod ;(
yesterday I tried to back to stock mod but my phone hard bricked ;(
I tried some of image flash thing so get back to normal phone but still don't have imei or data
*sigh* I have to find fix shop
If you have got the phone booting again you don't need a fix shop. The imei problem is probably due to flashing back to mjb modem. See this thread: http://forum.xda-developers.com/showthread.php?p=53851558
Sent from my SAMSUNG-SGH-I747 running TMS3KK-1.1