Related
Hello everyone, i'm a new member. I apologize if my english is not good enough.
After been driven insane by one pre-installed app from my Operator (Claro Peru) i decided that it was time to root my device to get rid from that pest. I'm a noob, so i started to investigate about the safest methods to not damage my phone. My Device's model is SGH I337m.
The plan was to update the FW from JB 4.3 that came with my phone to 4.4.2 and then proceed to root. I downloaded the Canadian 4.4.2 FW with build version I337MVLUFNC1 and installed manually with Odin. After the phone rebooted, my S4 was upgraded with 4.4.2 but Samsumg keyboard was going insane, so i went to the apps and solved that cleaning the cache/data. Then i noticed that the Wifi wasn't connected, i tried to turn it on, but then a message with a shield appeared saying that my device security stopped the operation. Beliving it was only a problem with KNOX, i installed autoroot (CF-Auto-Root-jfltecan-jfltevl-sghi337m) with Odin, open SuperSU and stopped it from working, but the Wifi still wouldn't connect.
So the first thing that crossed my mind was to unroot and do a factory reset, didn't work. The FW still was 4.4.2, so i´ve been searching solutions with this FW because i've read some cases of devices that stopped working completely after trying to do a downgrade. so i don't want to go to that route for now.
After a couple hours of search, some solutions i found on the forum were:
- Install Faux123 Kernel (Found on Youtube, this would be the thread i think http://forum.xda-developers.com/showthread.php?t=2273437http://forum.xda-developers.com/showthread.php?t=2273437
- Flash a modem for i337m
- Safestrap recovery and bypasslkm.zip
- Downgrade
I haven't tried any of this methods because i dont want to get into a deeper trouble. In the first solution i'm not sure what to do because this is the files the author recommends for canadian models (i337m), but when i enter here http://faux.romhost.me/jflteatt/jb42/http://faux.romhost.me/jflteatt/jb42/ only jflteatt appears, and that would be i337 model, isn't it? I thought that installing it may cause more troubles, so i didn't do it.
For the flashing modem method, i'm not really sure if installing a modem from another country would get me in trouble, so again i didn't proceed.
I found the Safestrap and recovery method on a downgrade thread for the i337, so again, didn't do it.
So, is there a way to get one of this methods working on i337m to get wifi working again, or is there any other better method to get back wifi.
I would really appreciate any help you can give me guys.
Copellius said:
... My Device's model is SGH I337m.
The plan was to update the FW from JB 4.3 that came with my phone to 4.4.2 and then proceed to root. I downloaded the Canadian 4.4.2 FW with build version I337MVLUFNC1 and installed manually with Odin. After the phone rebooted, my S4 was upgraded with 4.4.2 but Samsumg keyboard was going insane, so i went to the apps and solved that cleaning the cache/data. Then i noticed that the Wifi wasn't connected, i tried to turn it on, but then a message with a shield appeared saying that my device security stopped the operation. Beliving it was only a problem with KNOX, i installed autoroot (CF-Auto-Root-jfltecan-jfltevl-sghi337m) with Odin, open SuperSU and stopped it from working, but the Wifi still wouldn't connect.
So the first thing that crossed my mind was to unroot and do a factory reset, didn't work. The FW still was 4.4.2, so i´ve been searching solutions with this FW because i've read some cases of devices that stopped working completely after trying to do a downgrade. so i don't want to go to that route for now.
After a couple hours of search, some solutions i found on the forum were:
- Install Faux123 Kernel (Found on Youtube, this would be the thread i think http://forum.xda-developers.com/showthread.php?t=2273437http://forum.xda-developers.com/showthread.php?t=2273437
- Flash a modem for i337m
- Safestrap recovery and bypasslkm.zip
- Downgrade
I haven't tried any of this methods because i dont want to get into a deeper trouble. In the first solution i'm not sure what to do because this is the files the author recommends for canadian models (i337m), but when i enter here http://faux.romhost.me/jflteatt/jb42/http://faux.romhost.me/jflteatt/jb42/ only jflteatt appears, and that would be i337 model, isn't it? I thought that installing it may cause more troubles, so i didn't do it.
For the flashing modem method, i'm not really sure if installing a modem from another country would get me in trouble, so again i didn't proceed.
I found the Safestrap and recovery method on a downgrade thread for the i337, so again, didn't do it.
So, is there a way to get one of this methods working on i337m to get wifi working again, or is there any other better method to get back wifi.
I would really appreciate any help you can give me guys.
Click to expand...
Click to collapse
ok so you have the i337m canadian version... making anything related to safestrap and the att i337 irrelevant, completely different methods so don't get them confused lol
you were updating from stock 4.3 right? your best bet is to factiry reset and reflash stock fw for 4.4.2 before you brick your device... kitkat is very different from 4.3, maybe read up on it a bit too...
for ex, the "message with a shield appeared saying that my device security stopped the operation" isn't related to needing to root, it's an option under security settings.
to enable superuser on kitkat you need to enable developer options, then enable superuser. I prefer supersu so manually install that from play store afterwards. I recommend checking and/or enabling this as soon as the phone completes booting up after flashing.
also I think there's a known issue w/ 4.4.2 and wifi not turning on until after 2nd boot completed if I rememebr correctly, been using 4.4.4 for awhile now though so could be wrong...
good luck and check out the help section :angel:
Hi everyone, long time reader, first time poster.
First of all, i want to let you all know how i appreciate all the hard work you guys do on here. i was able to get all the info i needed to get my ATT n7105 back to stock after running CM 10.2 for the last year on it.
Back on topic...i have an S4 i337 running 4.3 MK2. when i first flashed it, for the longest time i couldnt figure out why i couldnt get signal or wifi, and found out needed to flash the MK2 modem firmware also (thanks for the info on that also). now the issue i am having is that now the phone has no sound at all, tried playing music, recieving a call (which makes the phone go total bonkers too), or even the beep it makes when adjusting the volume. I have tried searching for info on sound issues, but that was one thing i was unsuccessful with.
when i first got the phone, it had 4.2.2 (not sure of the firmware) and wanted to unlock it to use any carrier rather than just ATT. the only way of unlocking it, rather than getting an unlock code, was to go into service mode, and navigate through some menus, but i read that with 4.2.2, i could not, so i done an /ota update, which brought me straight to 4.4.3. after the unpdate, tried doing the service mode again, and had no luck, so tried downgrading to 43].3, than went to hell trying to get it working, untill coming across these forums, and got it working again with 4.3 MK2, but as mentioned, with no sound.
Any advice on what to try?
Thanks in advance.
RTyper56 said:
Hi everyone, long time reader, first time poster.
First of all, i want to let you all know how i appreciate all the hard work you guys do on here. i was able to get all the info i needed to get my ATT n7105 back to stock after running CM 10.2 for the last year on it.
Back on topic...i have an S4 i337 running 4.3 MK2. when i first flashed it, for the longest time i couldnt figure out why i couldnt get signal or wifi, and found out needed to flash the MK2 modem firmware also (thanks for the info on that also). now the issue i am having is that now the phone has no sound at all, tried playing music, recieving a call (which makes the phone go total bonkers too), or even the beep it makes when adjusting the volume. I have tried searching for info on sound issues, but that was one thing i was unsuccessful with.
when i first got the phone, it had 4.2.2 (not sure of the firmware) and wanted to unlock it to use any carrier rather than just ATT. the only way of unlocking it, rather than getting an unlock code, was to go into service mode, and navigate through some menus, but i read that with 4.2.2, i could not, so i done an /ota update, which brought me straight to 4.4.3. after the unpdate, tried doing the service mode again, and had no luck, so tried downgrading to 43].3, than went to hell trying to get it working, untill coming across these forums, and got it working again with 4.3 MK2, but as mentioned, with no sound.
Any advice on what to try?
Thanks in advance.
Click to expand...
Click to collapse
You don't have sound or the ability to call because your bootloader and non-hlos don't match. You can get sound by flashing the NB1 or NC1 modems(including non-hlos.bin) but that will break your wifi which can be fixed by using bypasslkm.
Sure, ill give that a try.
What if i were to update it to 4.4.3? any certain modems required there?
muniz_ri said:
You don't have sound or the ability to call because your bootloader and non-hlos don't match. You can get sound by flashing the NB1 or NC1 modems(including non-hlos.bin) but that will break your wifi which can be fixed by using bypasslkm.
Click to expand...
Click to collapse
Whenever i tried flashing NB1 or NC1, i get an error saying "signature verification failed, then later on give an error "unknown path \sdcard1" after wiping data, then reboots. and when the phone rebooted, it goes through the first time setup after a wipe, and then checking the modem, and its still NK2.
I really would like to get it to the current version.
RTyper56 said:
Whenever i tried flashing NB1 or NC1, i get an error saying "signature verification failed, then later on give an error "unknown path \sdcard1" after wiping data, then reboots. and when the phone rebooted, it goes through the first time setup after a wipe, and then checking the modem, and its still NK2.
I really would like to get it to the current version.
Click to expand...
Click to collapse
Follow these instructions to get to Stock, Rooted NC1: http://forum.xda-developers.com/showpost.php?p=52167774&postcount=3
muniz_ri said:
Follow these instructions to get to Stock, Rooted NC1: http://forum.xda-developers.com/showpost.php?p=52167774&postcount=3
Click to expand...
Click to collapse
Awesome! thank you very much
With the instructions you provided, i was able to get my i337 in working order.
your assistance is greatly apreciated
Here's the story
1. this phone wouldn't boot up after the OTA update, the screen read "firmware upgrade encountered an issue.
please use software repair assistant & try again."
2. used odin 3.09 to reflash pit and the latest nc4 official firmware (I know it can't be rooted, but that's the only choice I have).
3. phone came back alive, worked for t-mobile and verizon sim cards.
Problem:
after a few hours or maybe a day, or maybe a restart, phone won't detect sim card, baseband version shows unkwown, hardware
version is empty, imei, network, MIN, PRL version, ERI version, imeisv, iccid are all "unknown".
What I have done:
phone will be back to normal if I flash the firmware again, I've use odin 3.09 and kies 3 many times.
I also tried flashing different modems, for ex, MI9, MJE, NC2 even NC4. But phone will keep restarting, sometimes the phone is working after
a few restarts. But eventually I will have the same problem again.
I was wondering if someone could point me to the right direction?
nicedog said:
Here's the story
1. this phone wouldn't boot up after the OTA update, the screen read "firmware upgrade encountered an issue.
please use software repair assistant & try again."
2. used odin 3.09 to reflash pit and the latest nc4 official firmware (I know it can't be rooted, but that's the only choice I have).
3. phone came back alive, worked for t-mobile and verizon sim cards.
Problem:
after a few hours or maybe a day, or maybe a restart, phone won't detect sim card, baseband version shows unkwown, hardware
version is empty, imei, network, MIN, PRL version, ERI version, imeisv, iccid are all "unknown".
What I have done:
phone will be back to normal if I flash the firmware again, I've use odin 3.09 and kies 3 many times.
I also tried flashing different modems, for ex, MI9, MJE, NC2 even NC4. But phone will keep restarting, sometimes the phone is working after
a few restarts. But eventually I will have the same problem again.
I was wondering if someone could point me to the right direction?
Click to expand...
Click to collapse
When you flashed the different modems, did you check settings/about the phone to verify that the modem flash " took"? Recommend entering Odin from power off, especially when flashing modems. FWIW, I'm not at all sure this will fix your problem, but it's worth a shot.
cam30era said:
When you flashed the different modems, did you check settings/about the phone to verify that the modem flash " took"? Recommend entering Odin from power off, especially when flashing modems. FWIW, I'm not at all sure this will fix your problem, but it's worth a shot.
Click to expand...
Click to collapse
Yes I did. The baseband version showed MI9 when my phone was still working properly.
nicedog said:
Yes I did. The baseband version showed MI9 when my phone was still working properly.
Click to expand...
Click to collapse
OK. Hopefully someone else will chime in with some suggestions.
one more thing I've done many times so far is, sometimes a full reset will bring it back to normal too.
settings -> backup and reset -> factory data reset.
I don't mind bricking my phone, but maybe someone knows other possible way, say, flashing EFS? I don't even know what that is.
I've been searching for the right solution but I haven't found one yet.
Never ever give up!
I'm the OP and I finally got it working. I simply ran EFS Professional v2.1.73, did a backup and restore of the EFS. That's it!
Did you figure out what efs is?
Sent from my SM-N900V using XDA Premium 4 mobile app
It didn't last long, and using EFS profession for EFS backup/restore never worked again.
I then saw this page the other day,
http://forum.xda-developers.com/showthread.php?t=2610757
So I used odin to flash
pit
official kitkat rom
I also checked these two,
erase nand
erase EFS
the phone booted up fine, I then turned it off and entered recovery mode, did a data and cache wipe, then booted up the phone again, that brought back my imei, my sim card worked again.
Unfortunately I'll lose it again once I flash a custom rom, or perhaps even a reboot.
I'm still searching for a permanent solution. But at least now I can use my sim card with a stock rom
Rom based on which region?
nicedog said:
It didn't last long, and using EFS profession for EFS backup/restore never worked again.
I then saw this page the other day,
http://forum.xda-developers.com/showthread.php?t=2610757
So I used odin to flash
pit
official kitkat rom
I also checked these two,
erase nand
erase EFS
the phone booted up fine, I then turned it off and entered recovery mode, did a data and cache wipe, then booted up the phone again, that brought back my imei, my sim card worked again.
Unfortunately I'll lose it again once I flash a custom rom, or perhaps even a reboot.
I'm still searching for a permanent solution. But at least now I can use my sim card with a stock rom
Click to expand...
Click to collapse
Can you please tell the stock rom based on which CSC ? or country ?
I'm having the same issue. Lost baseband and imei, but never got it recovered. even with stock.
I use this one,
ALL_VZW_N900VVRUCNC4_N900VVZWCNC4_1487472_REV03_user_low_ship_MULTI_CERT.tar.md5
http://www.trueandroid.com/2014/05/n900vvrucnc4-android-442-kitkat.html
Same boat brother, this is what I've posted. So far I'm a week in this situation, battery pull brings it back, any mod like Xposed with module where you have to reboot looses the baseband, IMEI etc. I have backup of the EFS and restored it multiple time with no joy.
Need some advice guys for Verizon my Note 3, I'm currently stock NC4 ready to. flash this bad boy ROM, after root access with TowelRoot, installation of BusyBox and Supersu no SafeTrap yet. Once I reboot in this state, I have the Baseband unknown under Settings-About Phone status all unknown info on IME etc etc. Off course I loose 4G signal all together. I may reboot again and it comes back. I know about EFS partition corruption and have multiple backup of My note 3 EFs partition. Even with restore it would still happen. I have exhausted all my knowledge learned throughout the years from you guys. But, I'm asking some help again. I am very familiar with all the terms about flashing/rooting so please feel free to throw some genius on how I can fix this thing.
Sent from my SM-N900V using Tapatalk
Hi, I have been trying to get my s4 i9505 networked unlock. It's currently on EE. I bought it from someone who has gone abroad so can't ask them to get ee to do it. I have tried 3 online unlocking sites, the last was recommended on here but non of them can do it. I have tried to install several firmwares but hoping that would remove the ee lock But they all seem to be ee firmware. Is there a firmware that you can tell me about which will do what I want. Or is there a way I can conect to my computer and do a hardware unlock. Hope someone can help as getting desperate now.
A friend of mine has a insurance supplied s4 i9505 Which is unlocked. Is there a way we can copy the firmware on his and install on my or completely clone the phone . ?
Installing firmware will not remove a carrier unlock. Downgrading firmware from Android 4.4.2 to Android 4.2 may work if attempting to use the free unlocking methods on the forums. Naturally, using those methods have risks, up to and including totally bricking the phone. The carrier lock mechanism is part of the modem firmware as RegionLock Away modifies the modem when it functions. Hardware unlocking probably can be done, but I couldn't tell you how it's done. I also can't tell you if copying your friend's modem will help your cause. I CAN tell you that completely cloning his phone is completely illegal and you could render both his and your phones completely useless by trying it.
Strephon Alkhalikoi said:
Installing firmware will not remove a carrier unlock. Downgrading firmware from Android 4.4.2 to Android 4.2 may work if attempting to use the free unlocking methods on the forums. Naturally, using those methods have risks, up to and including totally bricking the phone. The carrier lock mechanism is part of the modem firmware as RegionLock Away modifies the modem when it functions. Hardware unlocking probably can be done, but I couldn't tell you how it's done. I also can't tell you if copying your friend's modem will help your cause. I CAN tell you that completely cloning his phone is completely illegal and you could render both his and your phones completely useless by trying it.
Click to expand...
Click to collapse
Thank you for the reply, can I install a modem . I think I have read that you can't down grade the firmware ? If this is wrong. Where can I find the 4.2 firmware . Thanks
You can try, but I don't believe it will help any. While I said that the carrier lock is part of the modem firmware, it's not as simple as installing new modem firmware. The modem firmware that people commonly install really only controls the radios, while the carrier lock is in a different part. That part doesn't usually get touched by a new firmware install. In my experience, the carrier lock reared its ugly head when I destabilized the NV memory of my S4, which caused a reset to the golden backup in the phone.
I also had a SIM tray issue which popped up at the same time, and only by rolling back the firmware to 4.2.2 was I able to get to a stage to unlock the phone, using RegionLock Away. It is possible to roll back the firmware itself, but you cannot roll back the bootloader. Using old firmware with a new bootloader results in a "Kernel is not SEAndroid Enforcing" complaint upon boot.
To cut this down to basics, you can install a 4.2.2 modem and attempt one of the unlock methods available, as long as you are fully aware of the risks involved. If you choose this route you can download a modem from the appropriate thread on XDA and install it through Odin. You'll need to do a search to find it, but it shouldn't be too difficult. Full ROMs are available from www.sammobile.com or www.samsung-updates.com.
Strephon Alkhalikoi said:
You can try, but I don't believe it will help any. While I said that the carrier lock is part of the modem firmware, it's not as simple as installing new modem firmware. The modem firmware that people commonly install really only controls the radios, while the carrier lock is in a different part. That part doesn't usually get touched by a new firmware install. In my experience, the carrier lock reared its ugly head when I destabilized the NV memory of my S4, which caused a reset to the golden backup in the phone.
I also had a SIM tray issue which popped up at the same time, and only by rolling back the firmware to 4.2.2 was I able to get to a stage to unlock the phone, using RegionLock Away. It is possible to roll back the firmware itself, but you cannot roll back the bootloader. Using old firmware with a new bootloader results in a "Kernel is not SEAndroid Enforcing" complaint upon boot.
To cut this down to basics, you can install a 4.2.2 modem and attempt one of the unlock methods available, as long as you are fully aware of the risks involved. If you choose this route you can download a modem from the appropriate thread on XDA and install it through Odin. You'll need to do a search to find it, but it shouldn't be too difficult. Full ROMs are available from www.sammobile.com or www.samsung-updates.com.
Click to expand...
Click to collapse
Ok thanhs you the info , looks like I'm a bit stuck . I don't really understand why the unlocking sites can't generate a Code. If I put another sim into the phone it doesn't tell me I an incorrect sim .
unlock
Is there anyone on here in uk who can offer to unlock this phone for me
I've got a S4 AT&T running OK2 with root and it ran my AirVoice Wireless SIM perfectly fine for a month while I researched and got a new phone. I'd now like to use it as a backup phone with a FreedomPOP SIM but it's giving me grief about "SIM network unlock PIN". This is the carrier lock correct? I found a tutorial that has you go into the Service Mode and turn off NETWORK LOCK. This tutorial doesn't seem to work (missing the options) in OK2. Do I have to downflash to 4.2.2 in order to get these options? If so, how do I go about doing that? I put OK2 with root on this phone but that process took 2 days and with all the mixed info out there and different versions, it's confusing to say the least.
My other question is, I tried flashing TWRP (jflteatt) and I believe I ended up with the "software not authorized by AT&T" error. Doing some reading, it looks like this may be due to not using a loki'd TWRP?
Any pointers/tips would be much appreciated. All this Samsung stuff is way over my head despite having rooted, recoveried and rom'd maybe a dozen Android devices. I much prefer LG and Moto
natenkiki2004 said:
I've got a S4 AT&T running OK2 with root and it ran my AirVoice Wireless SIM perfectly fine for a month while I researched and got a new phone. I'd now like to use it as a backup phone with a FreedomPOP SIM but it's giving me grief about "SIM network unlock PIN". This is the carrier lock correct? I found a tutorial that has you go into the Service Mode and turn off NETWORK LOCK. This tutorial doesn't seem to work (missing the options) in OK2. Do I have to downflash to 4.2.2 in order to get these options? If so, how do I go about doing that? I put OK2 with root on this phone but that process took 2 days and with all the mixed info out there and different versions, it's confusing to say the least.
My other question is, I tried flashing TWRP (jflteatt) and I believe I ended up with the "software not authorized by AT&T" error. Doing some reading, it looks like this may be due to not using a loki'd TWRP?
Any pointers/tips would be much appreciated. All this Samsung stuff is way over my head despite having rooted, recoveried and rom'd maybe a dozen Android devices. I much prefer LG and Moto
Click to expand...
Click to collapse
Yeah you're carrier locked. I think you can only downgrade to NB1 from OK2, not sure you can carrier unlock on NB1 or not. As for installing TWRP you can't due to the locked bootloader. You can only use safe strap recovery and boot only custom touch wiz roms. Loki only works on the MDB and MDL bootloaders, once you've upgraded the bootloader past MDL, you can't go back.
If the AT&T phone is like the i337m and m919, you may be able to flash down to 4.4.2, flash a 4.2.2 modem, root, run regionlockaway, upgrade modem back to 4.4.2.
Thanks for the replies. I grabbed NB1 from here: https://forum.xda-developers.com/showthread.php?t=2616221
and flashed it via Odin. All went well but when it came time to follow various instructions I found online, they either yielded no unlock or the options weren't in the menu. I don't think the free unlock trick via the service menu works on 4.4.2/NB1.
I researched a bit more and feel very stupid with one of the results that came up... AT&T offers online unlocking of their devices and you don't even have to be one of their customers! I figured I could go to one of their retail stores but also figured they would deny me since I'm not a customer. I'll be jiggered though, here it is: https://www.att.com/deviceunlock/
Slapped my IEMI in with my e-mail and in less than an hour or so, I got my unlock code for free. AT&T said they would e-mail it but I checked back on the status page and found the code there. Hopefully this helps other people.
So, moving forward now, is OK2 the best I can do with a locked bootloader? I ran it for a while but I found that I burned through my data real quick because when I would leave my WiFi coverage and come back, it would reconnect but for some reason wouldn't actually use WiFi (data was still on, had the 4G icon) until I restarted the phone. Basically, every time I left and came back home, I had to restart my phone. Is this a known issue, did I botch something in the install process? I may make another thread for this.
*EDIT*
Running OK2 for a while, I no longer have the WiFi issues I had before. Doing some thinking, I can only attribute the issue to either incorrectly followed steps the first time around flashing OK2 or the use of the debloater script found in the OK2 downloads thread. I've been using Link2SD to remove system apps and so far haven't removed anything that has affected WiFi.