hi,all I'm new here
i hive samsung galaxy S4 i337, my phone is factory unlock. I'm on ATT carr, two days ago i was at 4.2.2 and rooted, and today my phone it updating itself.
when was on 4.2.2 i was getting the same thing at boot ""the custom screen with the lock that was unlocked showed up"" but was working ok and rooted.
after the update, i still get the same thing at boot. Now i can't root my phone on 4.3 because of the security issue to keep blocking. anything i do.
Please can someone explain how can I bypasses and rerooted phone, I tried all the method that is available to me but unable to rooted, security block.
I appreciate the help.
akihiko_51 said:
hi,all I'm new here i hive samsung galaxy S4 i337, my phone is factory unlock. I'm on ATT carr, two days ago i was at 4.2.2 and rooted, and today my phone it updating itself. when was on 4.2.2 i was getting the same thing at boot ""the custom screen with the lock that was unlocked showed up"" but was working ok and rooted. after the update, i still get the same thing at boot. Now i can't root my phone on 4.3 because of the security issue to keep blocking. anything i do. Please can someone explain how can I bypasses and rerooted phone, I tried all the method that is available to me but unable to rooted, security block. I appreciate the help.
Click to expand...
Click to collapse
Which baseband are you on now? MF3? MJ6? Before which baseband were you on MDL? or MF3? What root method did you use?
It sounds like you rooted your phone, but did not take measures to prevent over the air (OTA) updating.
That OTA updating will destroy root, and lately also locks your bootloader in a manner that is even more restrictive.
It does not sound like you used any custom rom, and did not use Safe Strap either, but you need to provide more info for folks to work with.
akihiko_51 said:
hi,all I'm new here
i hive samsung galaxy S4 i337, my phone is factory unlock. I'm on ATT carr, two days ago i was at 4.2.2 and rooted, and today my phone it updating itself.
when was on 4.2.2 i was getting the same thing at boot ""the custom screen with the lock that was unlocked showed up"" but was working ok and rooted.
after the update, i still get the same thing at boot. Now i can't root my phone on 4.3 because of the security issue to keep blocking. anything i do.
Please can someone explain how can I bypasses and rerooted phone, I tried all the method that is available to me but unable to rooted, security block.
I appreciate the help.
Click to expand...
Click to collapse
You need to read all threads about 4.3, MJ6, and MJ9 in the "General" and " Q & A" sections of the forum to learn about what is happening with your phone.
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,
Its been a long time since the bootloader was version MDL. As you may be aware this was the last version that could be fully rooted and custom recovery'd before the MF3 firmware locked everybody down. Well a year and a half later and my MDL Phone is having an issue that I can't fix. The Phone keeps failing to recognize the SIM card that is in it (Image), and previously it would randomly disconnect (Image). I've tried getting a new SIM card and that failed to fix the issue; I clean-installed by ROM to eliminate that as a cause, but no luck.
I'm fairly sure my only option now is to go to AT&T and have them fix or more likely replace the phone. Is there any possible way I could get a phone with MDL still? Or are there any alternatives I could try? I don't know what to do now. Thank you.
Tryer1234 said:
Hi everyone,
Its been a long time since the bootloader was version MDL. As you may be aware this was the last version that could be fully rooted and custom recovery'd before the MF3 firmware locked everybody down. Well a year and a half later and my MDL Phone is having an issue that I can't fix. The Phone keeps failing to recognize the SIM card that is in it (Image), and previously it would randomly disconnect (Image). I've tried getting a new SIM card and that failed to fix the issue; I clean-installed by ROM to eliminate that as a cause, but no luck.
I'm fairly sure my only option now is to go to AT&T and have them fix or more likely replace the phone. Is there any possible way I could get a phone with MDL still? Or are there any alternatives I could try? I don't know what to do now. Thank you.
Click to expand...
Click to collapse
I wouldn't go to at&t. The first thing they'll do is "upgrade" you to nj4. You said you Chan installed the rom, does that mean you odin'd the stock firmware? If not I'd flash the mdl firmware in Odin
Sent from my Nexus 9 using XDA Free mobile app
Well, there are several options; if you are on mdl, with a custom recovery like CWM or TWRP, you can flash updated modem firmware (see http://forum.xda-developers.com/showthread.php?t=2496517), to see if it is just the firmware (this will not affect the bootloader); you might also be suffering from the "sim removed" problem, documented here and here
Good luck!
Hey Guys, I'm brand new to these forums, and to this whole community so bare with me.
Basically I bought my T-Mobile Samsung Galaxy S5 phone around the time it came out, and I also had installed root on it via towelroot when Towel Root was first released. I did not update the phone at all for a long period of time and everything was working fine, until one day I was browsing under settings and accidentally tapped the "Software Update" button, then T-mobile auto-pushed an update onto my phone.
This update has caused the root on my phone to not work at all (Deemed useless) So I clicked SU and only a black screen popped up when I tried to open the app, so I uninstalled it, reinstalled it then got a message saying "There is no SU binary installed, and SuperSU Cannot install it. If you just upgraded to Android 4.3 you need to manually re-root your device" So I tried to re-root via towelroot method again. It seems the T-mobile update made my phone "Unsupported/Uncompatible" with TowelRoot's obsolete techniques, so now I'm in dire need of help.
My phone tried to push another t-mobile update (This time to upgrade to Lollipop) but it failed after attempting to install it after a reboot. So not only will my phone not update to Lollipop, but I'm not even rooted anymore and am unsure on how to get back rooted, or what to do next since I used rooting as a primary source to store apps on my SD Card. Kind of like i'm stuck in one spot? (Can't update your phone/can't root it the old method)
I'm brand new guys, Please can you break down to me what I should do, in order to obtain root again, and possibly be able to upgrade to Lollipop As well as prevent further pushed T-mobile updates? Here's some info if you need it
S5 Model Number: SM-G900T
Android Version:4.4.2
Kernel Version:3.4.0-262.. etc. (Tell me if you need the full kernel details)
Any help would be greatly appreciated! Thank YOU!
Flash this with ODIN
http://download.chainfire.eu/407/CF-Root1/CF-Auto-Root-kltetmo-kltetmo-smg900t.zip
(Will trip KNOX and void warranty)
Or flash a pre-June 2014 KK Kernel, root with Towelroot again, then flash back your current Kernel
Is this the only solution? And also is it the right one? o.o
Can anyone else please give me some feedback on the situation? I want to make sure I do this right, please just a little helps.
Bump
bump
*Detection* said:
Or flash a pre-June 2014 KK Kernel, root with Towelroot again, then flash back your current Kernel
Click to expand...
Click to collapse
Hey I did exactly what you said and it worked I got root back, but I was wondering how to flash back to my current kernel and keep Root?
I received a new phone since I broke my old GS4 (I337). It was on AT&T 4.2.2 and I rooted it using motochopper. It was fine. It automatically updated while I was asleep to 4.4.2. I had rooted my old GS4 on the same update. So I figured I'll just root it again. So I used the method where I flash the NC1 kernel, use towel root, then flash NJ4 back. Now my WiFi will not turn on, but I do have root access. Also, a message saying "Unauthorized actions have been detected" and it tells me to restart to undo these changes. I don't want to do it in fear of bricking my device. I'm really scared now and I desperately need to fix this. I just want to go back to complete stock 4.4.2. I've tried reflashing the NJ4 file twice and WiFi will still not turn on. I've attached pictures of the notice and my device info. Please help. I cannot brick this device. I will answer to any questions as fast as possible. At the moment, I am debating whether or not to flash this because I am unsure if it will be compatible. ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_user_low_ship_MULTI_CERT.tar
http ://i.imgur.com/68B7MNM. png?1
http ://i.imgur.com/6Cjnzug. png?1
brandon1999 said:
I received a new phone since I broke my old GS4 (I337). It was on AT&T 4.2.2 and I rooted it using motochopper. It was fine. It automatically updated while I was asleep to 4.4.2. I had rooted my old GS4 on the same update. So I figured I'll just root it again. So I used the method where I flash the NC1 kernel, use towel root, then flash NJ4 back. Now my WiFi will not turn on, but I do have root access. Also, a message saying "Unauthorized actions have been detected" and it tells me to restart to undo these changes. I don't want to do it in fear of bricking my device. I'm really scared now and I desperately need to fix this. I just want to go back to complete stock 4.4.2. I've tried reflashing the NJ4 file twice and WiFi will still not turn on. I've attached pictures of the notice and my device info. Please help. I cannot brick this device. I will answer to any questions as fast as possible. At the moment, I am debating whether or not to flash this because I am unsure if it will be compatible. ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_user_low_ship_MULTI_CERT.tar
http ://i.imgur.com/68B7MNM. png?1
http ://i.imgur.com/6Cjnzug. png?1
Click to expand...
Click to collapse
Bricking is almost impossible. So stop stressing out. You are in the wrong forum.
http://forum.xda-developers.com/galaxy-s4-att
Usually you have a wrong modem flashed or something with that problem. Stop stressing out and take your time to find the solution. You will not brick it.
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.