Related
I honestly don't know where to start, I bought the Samsung galaxy s4 i337m from virgin mobile, and use it with my Bell carrier. I was browsing the internet when I come to a video that states that you can flash i9505 roms on my i337/i337m phone! So silly of me to try that, it actually worked. When I was tired of that ROM, I go on this forum thread and look for another ROM, a ROM that is i337m cooked, and it soft bricked my phone, 3 times for 3 different i337m ROMS, at this point I have absolutely no clue what is going on with my phone, is the bootloader unlocked? WTF IS LOKI?? WHY does a i9505 ROM work on my phone, and a i337m cooked ROM does not, I just need some answers!! I have been flashing my phone with ROMs since my s1 and now the s4 comes along and completely wipes any knowledge I had before I got the phone, if anyone can help me on which ROMS I can and/or can't flash, that would be great, sorry for english not my first language!
Read and do some research. Just because you flashed a number of other phones doesn't mean you know how to flash this one. Every phone is different. It would also help to know what roms you flashed that didn't work.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
We are in trouble.
Loki is for locked bootloaders..which you do not have..you need to do some serious reading.
TheAxman said:
We are in trouble.
Loki is for locked bootloaders..which you do not have..you need to do some serious reading.
Click to expand...
Click to collapse
I still don't understand, I have the north american version of the i337m from Canada....
Dragosmp said:
I still don't understand, I have the north american version of the i337m from Canada....
Click to expand...
Click to collapse
What roms did you try to flash? Where did you get them? The boot loader is not locked and they should flash. Did you check the md5sum? They could be bad downloads.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Loki is needed for phones purchased through at&t. The Canadian version is the same phone, but without a locked boot loader, so the Loki hack is not needed.
What I have found is that some of the custom recoveries don't wipe out the phone properly. Try using Odin and go back to stock, wipe, then restart fresh
Also make sure you do a full wipe after flashing a Rom
Sent from my SGH-I337 using xda app-developers app
Matridom said:
Also make sure you do a full wipe after flashing a Rom
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'd do the full wipe before flashing. If you wipe after DON'T wipe system or you'll be in trouble.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Actually, I totally found that the Loki fix was needed for my Canadian i337m device (Bell). Many ROMs wouldn't work without it; they'd just get stuck in the boot logo (including SlimRom and CyanogenMod).
Just flash the ROM, then flash the Loki-Fix and you should be good to go.
If you're seriously stuck and you can't get back into your custom recovery, let me know and I'll help you out.
Now I am confused. Why would the I337m need a loki anything?
It is not needed. I surprised it even flashed.
TheAxman said:
Now I am confused. Why would the I337m need a loki anything?
Click to expand...
Click to collapse
I honestly have no idea; I just found that it worked for me. I was also very frustrated at first when I started flashing ROMs, until I tried the Loki Fix.
Te3k said:
I honestly have no idea; I just found that it worked for me. I was also very frustrated at first when I started flashing ROMs, until I tried the Loki Fix.
Click to expand...
Click to collapse
Do you know what your stock firmware was before you started flashing custom roms?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Te3k said:
I honestly have no idea; I just found that it worked for me. I was also very frustrated at first when I started flashing ROMs, until I tried the Loki Fix.
Click to expand...
Click to collapse
U sure it is the canadian version? J/k. That is strange. What happens if you flash a rom and not the loki fix?
jd1639 said:
Do you know what your stock firmware was before you started flashing custom roms?
Click to expand...
Click to collapse
I didn't check the first time, but ever since I had to reflash to stock I started using this firmware: I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME and this kernel:
Samsung-Updates.com-KERNEL-SGH-I337M-BMC-I337MVLUAMDJ-1366643831. It was necessary for me to Odin back to stock completely a couple of times.
TheAxman said:
U sure it is the canadian version? J/k. That is strange. What happens if you flash a rom and not the loki fix?
Click to expand...
Click to collapse
If I flash a ROM but not the Loki Fix, one of the following scenarios happens: 1. the ROM gets stuck in a boot-loop (continually restarts), or 2. gets to the boot logo and stays there forever (10+ minutes). But if I reboot into recovery, wipe everything again, reflash the ROM and then the Loki Fix, the phone boots up in less than a minute. Is this very weird? The phone is i337m from Bell, Canada.
Te3k said:
I didn't check the first time, but ever since I had to reflash to stock I started using this firmware: I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME and this kernel:
Samsung-Updates.com-KERNEL-SGH-I337M-BMC-I337MVLUAMDJ-1366643831. It was necessary for me to Odin back to stock completely a couple of times.
If I flash a ROM but not the Loki Fix, one of the following scenarios happens: 1. the ROM gets stuck in a boot-loop (continually restarts), or 2. gets to the boot logo and stays there forever (10+ minutes). But if I reboot into recovery, wipe everything again, reflash the ROM and then the Loki Fix, the phone boots up in less than a minute. Is this very weird? The phone is i337m from Bell, Canada.
Click to expand...
Click to collapse
It behaves just like the locked boot loader on the US version.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
It behaves just like the locked boot loader on the US version.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Strange. If it's relevant, I did encounter a lot of trouble sim-unlocking this phone for use on other networks. Using the Debug Menu on the phone's keypad didn't work as a method for me, although it had been reported to work for many others, including those with i337m's. I had to use a USB tether hack (FastGSM) to finally unlock the darn thing. Perhaps some models have locked bootloaders and others don't.
Te3k said:
Strange. If it's relevant, I did encounter a lot of trouble sim-unlocking this phone for use on other networks. Using the Debug Menu on the phone's keypad didn't work as a method for me, although it had been reported to work for many others, including those with i337m's. I had to use a USB tether hack (FastGSM) to finally unlock the darn thing. Perhaps some models have locked bootloaders and others don't.
Click to expand...
Click to collapse
Which custom recovery are you using to flash with and how did you get it on your phone?
Te3k said:
Strange. If it's relevant, I did encounter a lot of trouble sim-unlocking this phone for use on other networks. Using the Debug Menu on the phone's keypad didn't work as a method for me, although it had been reported to work for many others, including those with i337m's. I had to use a USB tether hack (FastGSM) to finally unlock the darn thing. Perhaps some models have locked bootloaders and others don't.
Click to expand...
Click to collapse
This is just not true. No way. Friggin way weird.
scott14719 said:
Which custom recovery are you using to flash with and how did you get it on your phone?
Click to expand...
Click to collapse
Using Open Recovery, and put it on the phone via an ADB interface (over USB debugging) using the Canadian i337m "3way" .BAT tool (root/CWM/OpenRecov).
And Axman, I just don't know what to say, lol!
Te3k said:
Using Open Recovery, and put it on the phone via an ADB interface (over USB debugging) using the Canadian i337m "3way" .BAT tool (root/CWM/OpenRecov).
And Axman, I just don't know what to say, lol!
Click to expand...
Click to collapse
You are the first. When you were on stock, what did it identify the phone as?
What does the model # say under the battery?
---------- Post added at 07:33 PM ---------- Previous post was at 07:30 PM ----------
Te3k said:
Using Open Recovery, and put it on the phone via an ADB interface (over USB debugging) using the Canadian i337m "3way" .BAT tool (root/CWM/OpenRecov).
And Axman, I just don't know what to say, lol!
Click to expand...
Click to collapse
And this procedure worked for you? You said you had to loki, where did that come in?
TheAxman said:
You are the first. When you were on stock, what did it identify the phone as?
What does the model # say under the battery?
And this procedure worked for you? You said you had to loki, where did that come in?
Click to expand...
Click to collapse
Phone identified as i337m from settings menu prior to any flashing. Model number under battery matches: Model: SGH-I337M / IC: 649E-I337M.
Using Loki came in where I found that flashing ROMs wasn't working. I had already rooted and tried to unlock the phone through the debug menu. Unlocking didn't work, but rooting did and I could load custom recoveries without problem. I thought that I should try flashing other ROMs to see if I could unlock the device through their debug menus, but no luck. The first ROM I tried to flash was a SlimRom nightly. That one appeared to flash properly (recovery said "success"), but upon reboot I got stuck in a boot loop. I then went back to recovery and messed around trying to flash other ROMs and ran into the same issue persistently. I eventually panicked and Odined back to stock ROM and kernel (numbers previously mentioned). Everything was fine after I figured out how to make Odin work. (I even learned how to make signed-MD5 tarballs with Cygwin to try to make flashing recoveries and roots simpler by using Odin.) After wondering why I couldn't flash any custom ROMs, I dug around a bit and found out that some ROMs' first-posts mentioned that certain fixes had to be applied—some of which were labelled ROM-specific (e.g. GOLDENEYE-i337m-FiX-XXUBMF8) and others that just said that they required a Loki fix, and sometimes provided a link to download it. At the time I didn't know what Loki was, and I wasn't understanding why certain ROMs would come pre-"Lokified" (brain was full after hacking around for >6h). So in the moment it made no sense not to try flashing that to see if it would help. Lo and behold, it worked! I started flashing Loki after every ROM install from then on out. Previously not-working ROMs that I had already tried suddenly worked just fine (I didn't redownload them; I kept the same zip files and just started flashing the Loki Fix after each of them to make them work).
It's still the case that when I want to flash a new ROM, I wipe everything from recovery and flash the ROM. If it doesn't boot, I flash the Loki Fix and then it does boot properly.
I was wondering if there was any work being done with a pure AOSP rom or any other roms that will theme with a locked bootloader.
The answer is sort-of...
No, you cannot unlock the boot loader if you the latest ota.
Yes, you can root and install safestrap, then look for a desirable ROM.
The third option I played with is replace as many of the Motorola apps as you can with the aosp versions. It is dangerous, I only tried it with email and that worked great, but I moved on to contacts and totally screwed up the ROM forcing me to flash back to stock and redo everything.
Sent from my Nexus 10 using Tapatalk 2
There is a work around for the latest OTA hehehe
Flash the stock.IMG in fastboot with the toolkit. It will flash a compatible version where you can unlock and root from there.
If you want AOSP... Carbon ROM is the closest in my opinion so far...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Can you elaborate more on this process? What do you mean unlock, I thought that was impossible now? Which toolkit? So confused.
Sent from my Nexus 10 using Tapatalk 2
lukkypuggy said:
There is a work around for the latest OTA hehehe
Flash the stock.IMG in fastboot with the toolkit. It will flash a compatible version where you can unlock and root from there.
If you want AOSP... Carbon ROM is the closest in my opinion so far...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Has this method been tested and confirmed?
CrocadileUT78 said:
Can you elaborate more on this process? What do you mean unlock, I thought that was impossible now? Which toolkit? So confused.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
There is a Root Toolkit here in one of the forums, look for version 1.20
By unlock I mean unlocking the bootloader. It is only impossible if you don't flash an earlier version of the stock.img.
Yes it is confirmed, that is how I am running Carbon right now
Sent from my XT907 using XDA Premium 4 mobile app
So you had the 78 update, and downgraded, then unlocked bootloader? Everything else I read said that doesn't work. I'm so confused.
Sent from my XT907 using Tapatalk 4
I didnt think one could downgrade if they had a locked boot loader?! Anyone who had actually achieved this please chime in here.
lukkypuggy said:
There is a Root Toolkit here in one of the forums, look for version 1.20
By unlock I mean unlocking the bootloader. It is only impossible if you don't flash an earlier version of the stock.img.
Yes it is confirmed, that is how I am running Carbon right now
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Curious as well how did you go about this? I thought it was impossible to unlock on latest ota. If this is the case, why has this not been brought up earlier?
Sent from my XT907 using Tapatalk 2
CrocadileUT78 said:
So you had the 78 update, and downgraded, then unlocked bootloader? Everything else I read said that doesn't work. I'm so confused.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
lukkypuggy said:
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I might be able to test this, but can you explain, by steps, how you did this?
Sent from my XT907 using Tapatalk 2
lukkypuggy said:
Yes, I had the .78 OTA and then I downgraded to a compatible version to get root then unlock and flash a custom ROM.
I don't know if my case was for some reason special but I also never got the "Boot loader is unlocked warning" either.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you buy it used? If so, when? If you did, it may have already been unlocked...
Sent from my XT907 using Tapatalk 4
Here is the kit I use: http://forum.xda-developers.com/showthread.php?t=2249773
"Number 1 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 System, Kernel, and Radio as well we wipe your data.
Number 2 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 Stock Recovery.
Number 3 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash TWRP Recovery by Hashcode.
Number 4 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash CWM Recovery by Hashcode.
Number 5 Explained -- This is Dan Rosenberg's root exploit called 'Motochopper'. This option requires your phone to be booted normally, with USB Debugging enabled.
Number 6 Explained -- This option requires your phone to be booted normally, with USB Debugging enabled. It will install an App version of Dan Rosenberg's Motopocalypse exploit for unlocking the bootloader.
Remember, do not run this utility unless your phone is at 100% battery OR you have bought yourself one of Team Black Hat's Factory-Style Programming Adapters."
Click to expand...
Click to collapse
First backup your data and im not responsible if you cause the apocalypse
OK. chose option #1. It will flash a rootable version.
Next to root, choose option #5.
Next chose option #6 to ULOCK your bootloader.
Next chose either option 3 or 4 for a custom recovery. (I like CWM)
Have fun. that is exactly What I Did.
lukkypuggy said:
Here is the kit I use: http://forum.xda-developers.com/showthread.php?t=2249773
First backup your data and im not responsible if you cause the apocalypse
OK. chose option #1. It will flash a rootable version.
Next to root, choose option #5.
Next chose option #6 to ULOCK your bootloader.
Next chose either option 3 or 4 for a custom recovery. (I like CWM)
Have fun. that is exactly What I Did.
Click to expand...
Click to collapse
So just making sure, you were on the 4.1.2 ota prior to doing this right? Based on the notice posted on that utility thread, you are not suppose to use it if you were on the latest ota, which is the same one that locked the bootloader (unless stood corrected). So did you take a leap of faith and went ahead and did it even though it was warned to not do it, and did you ended up succeeding?
Was your phone bought new, or do you know if it's previous owner unlocked it before you got a hold of it, which would explain how you were able to, IF it wasn't used and modified prior?
Also, when you flashed the "compatible version" was it that you flashed the 4.1.2 update found in the utility or did you change it out to another image found here: http://sbf.droid-developers.org/scorpion_mini_xt907/list.php
Just wandering, because if so, this is phenomenal news for those who have do not possess the ability to unlock normally because they took the recent ota. I am sure that like everyone else, including myself, we just want to know if this is safe to follow or not, no pointing fingers or bad accusations.
Thanks
MistPhoenix said:
So just making sure, you were on the 4.1.2 ota prior to doing this right? Based on the notice posted on that utility thread, you are not suppose to use it if you were on the latest ota, which is the same one that locked the bootloader (unless stood corrected). So did you take a leap of faith and went ahead and did it even though it was warned to not do it, and did you ended up succeeding?
Was your phone bought new, or do you know if it's previous owner unlocked it before you got a hold of it, which would explain how you were able to, IF it wasn't used and modified prior?
Also, when you flashed the "compatible version" was it that you flashed the 4.1.2 update found in the utility or did you change it out to another image found here: http://sbf.droid-developers.org/scorpion_mini_xt907/list.php
Just wandering, because if so, this is phenomenal news for those who have do not possess the ability to unlock normally because they took the recent ota. I am sure that like everyone else, including myself, we just want to know if this is safe to follow or not, no pointing fingers or bad accusations.
Thanks
Click to expand...
Click to collapse
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
lukkypuggy said:
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
Click to expand...
Click to collapse
I believe you... Now the question is who is brave enough to take a leap of faith? I would love to unlock by boot loader to ensure I will get the latest Android versions moving forward. I don't trust Verizon to let an upgrade thru beyond 4.1.2. I would test your procedure myself, but I'm too dependent on my phone for work right now.
So... Anyone? Anyone? Be a hero folks, somebody take the plunge! Pretty please?
Sent from my Nexus 10 using Tapatalk 2
---------- Post added at 01:06 AM ---------- Previous post was at 12:51 AM ----------
Also, I feel obligated to mention this, and i do it with a heavy heart... A few weeks ago I seriously screwed up my phone playing with the contacts apk, breaking my ability to view my contacts or dial a number. I got desperate enough that even though I was on .78, used the utility and stock image to revert back everything fresh. I was so relieved when I saw it worked despite the warnings and being a slightly older rom version. Once I did that, I'm 75% sure I did trying unlocking the BL before installing .78 OTA, and it did not work. I figured I had nothing to lose at that point, and when it failed I just shrugged and continued getting my phone back to normal. Sorry if this discourages any brave souls, but again I am not 100% sure I followed the same steps Mentioned in this thread.
Sent from my Nexus 10 using Tapatalk 2
lukkypuggy said:
Yes, I did indeed took a leap of faith.
The phone was brand spanking new from Best Buy.
I flashed the one found in the utility.
If you dont trust it I TOTALY understand. I just wanted it so bad that I really didnt care.
Click to expand...
Click to collapse
Thank you for the response. I do plan on testing this later on today on a locked, new M so I will be able to verify completely. Everyone sit tight
Sent from my XT907 using Tapatalk 2
CrocadileUT78 said:
I believe you... Now the question is who is brave enough to take a leap of faith? I would love to unlock by boot loader to ensure I will get the latest Android versions moving forward. I don't trust Verizon to let an upgrade thru beyond 4.1.2. I would test your procedure myself, but I'm too dependent on my phone for work right now.
So... Anyone? Anyone? Be a hero folks, somebody take the plunge! Pretty please?
Sent from my Nexus 10 using Tapatalk 2
---------- Post added at 01:06 AM ---------- Previous post was at 12:51 AM ----------
Also, I feel obligated to mention this, and i do it with a heavy heart... A few weeks ago I seriously screwed up my phone playing with the contacts apk, breaking my ability to view my contacts or dial a number. I got desperate enough that even though I was on .78, used the utility and stock image to revert back everything fresh. I was so relieved when I saw it worked despite the warnings and being a slightly older rom version. Once I did that, I'm 75% sure I did trying unlocking the BL before installing .78 OTA, and it did not work. I figured I had nothing to lose at that point, and when it failed I just shrugged and continued getting my phone back to normal. Sorry if this discourages any brave souls, but again I am not 100% sure I followed the same steps Mentioned in this thread.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
BTW I never did get the unlock app to actually work (just remembered).
http://forum.xda-developers.com/showthread.php?t=2226729
http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
Download this .zip file once you have flashed the compatible stock version and have root.
As long as it says status code: 3 in the bootloader you are unlocked
Ok guys here are the results, sadly I could not achieve unlock with a unmodified, unrooted Razr M :
1. Turned off and started AP Fastboot mode. Used mattlgroff's Razr M Utility to flash to Android 4.1.2 98.15.66.XT907.Verizon.en.US system image. The flash worked perfectly I was able to downgrade to ota prior before the locked bootloader.
2. Used mattlgroff's Utility to root my device (step 5). I was able to root the device with SuperSU.
3. Used the seperate motopocalypse program by Dan Rosenberg found here http://forum.xda-developers.com/showthread.php?t=2226729. It ran and rebooted to AP fastboot mode. I received the folowing errors:
"TrustZone target address resolved to 2a020a02"
"TrustZone write failed: -11"
This indicated that the bootloader TrustZone which is needed to unlock, was still locked and that it couldn't make changes to properly unlock the device.
So for the time being, this method to unlock the bootloader does not work. I am thinking about trying the 4.1.1 system image instead, but I fear that since the bootloader is its own entity, that those that took the recent OTA had the TrustZone patched to the point where it cannot be written to period, even on a lower firmware. The best thing that could happen is for a miracle to occur and an exploit to be found to write to the TrustZone again.
MistPhoenix said:
Ok guys here are the results, sadly I could not achieve unlock with a unmodified, unrooted Razr M :
1. Turned off and started AP Fastboot mode. Used mattlgroff's Razr M Utility to flash to Android 4.1.2 98.15.66.XT907.Verizon.en.US system image. The flash worked perfectly I was able to downgrade to ota prior before the locked bootloader.
2. Used mattlgroff's Utility to root my device (step 5). I was able to root the device with SuperSU.
3. Used the seperate motopocalypse program by Dan Rosenberg found here http://forum.xda-developers.com/showthread.php?t=2226729. It ran and rebooted to AP fastboot mode. I received the folowing errors:
"TrustZone target address resolved to 2a020a02"
"TrustZone write failed: -11"
This indicated that the bootloader TrustZone which is needed to unlock, was still locked and that it couldn't make changes to properly unlock the device.
So for the time being, this method to unlock the bootloader does not work. I am thinking about trying the 4.1.1 system image instead, but I fear that since the bootloader is its own entity, that those that took the recent OTA had the TrustZone patched to the point where it cannot be written to period, even on a lower firmware. The best thing that could happen is for a miracle to occur and an exploit to be found to write to the TrustZone again.
Click to expand...
Click to collapse
Mine had the -11 error also but it also said status code 3 in the actually bootloader, Then I flashed CWM and that was it, now I have CM10.1.3 STABLE.
Maybe double check?
I do not have an S4. I ordered one from Swappa expecting to use it on Straighttalks LTE service. Already ordered the sim card as well.
However, of course right after this I started digging a bit more and found that it is currently impossible to root an S4 after it's updated to 4.4.2. The one I ordered is updated.
I'd highly prefer to have root. I don't "need" it. But, if I can achieve root without much issue I'd prefer it.
I did find a few posts about using something called Odin and safestrap. I didn't read fully through them yet. But, I'm curious if doing these methods actually work for downgrading? If they do what are the "limits"? Can I put any Rom in or is it only a specific Rom?
Will I likely run into issues doing this while using the ST LTE settings?
Just trying to cover my bases before I start on this phone. It's not here yet and I'd rather resell it if I'm better off doing that.
I am curious what would be suggested purchase for the ST LTE service since it seems the AT&T S4 is out of question if I can't even update the damn thing. I'd rather be capable of updates and having root. I don't care about being able to do Roms and stuff.
Dude, you can have root on any firmware but it may not be easy to get it. Do you know what firmware your device will have?
Odin flashes the stock firmware onto your device. Safestrap is a custom recovery that you'll need to flash custom touch wiz roms
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Dude, you can have root on any firmware but it may not be easy to get it. Do you know what firmware your device will have?
Odin flashes the stock firmware onto your device. Safestrap is a custom recovery that you'll need to flash custom touch wiz roms
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I've been reading nonstop that the 4.4.2 AT&T Galaxy s4 is not rootable? If this is inaccurate can you lead me to a post that shows the method for rooting this version?
I do not know anything about the phone other than it being updated to 4.4.2.
GamerXavier said:
I've been reading nonstop that the 4.4.2 AT&T Galaxy s4 is not rootable? If this is inaccurate can you lead me to a post that shows the method for rooting this version?
I do not know anything about the phone other than it being updated to 4.4.2.
Click to expand...
Click to collapse
It can be rooted. You'll need to downgrade thru Odin to mk2 firmware, root it with saferoot then instill safestrap and flash a 4.4.2 rooted rom Start here
http://forum.xda-developers.com/showthread.php?p=49562527
Sent from my Nexus 5 using XDA Free mobile app
And keep asking questions. You're limited to the roms you can flash but you can get root
jd1639 said:
It can be rooted. You'll need to downgrade thru Odin to mk2 firmware, root it with saferoot then instill safestrap and flash a 4.4.2 rooted rom Start here
http://forum.xda-developers.com/showthread.php?p=49562527
Sent from my Nexus 5 using XDA Free mobile app
And keep asking questions. You're limited to the roms you can flash but you can get root
Click to expand...
Click to collapse
I'm curious about Cyanogenmod? If it's worth it or possible atm?
Once I get the phone probably later this week I'll get started on the process.
GamerXavier said:
I'm curious about Cyanogenmod? If it's worth it or possible atm?
Once I get the phone probably later this week I'll get started on the process.
Click to expand...
Click to collapse
No, cm is not possible. Only touch wiz based roms
Edit, as an fyi, if your phone is on 4.4.2 it'll be on nb1 or nc1 firmware. Read up on how to downgrade to mk2. Look in the general forum. Also look at rebel1699's venom magic tool kit. There's a lot of reading and studying to do before you get your phone
Sent from my Nexus 5 using XDA Free mobile app
http://www.androidpolice.com/2014/0...ve-and-maybe-almost-any-other-current-device/
Is this going to work on the ATT S4? It's stated that it would. Would save me the trouble of doing all of this other stuff.
GamerXavier said:
http://www.androidpolice.com/2014/0...ve-and-maybe-almost-any-other-current-device/
Is this going to work on the ATT S4? It's stated that it would. Would save me the trouble of doing all of this other stuff.
Click to expand...
Click to collapse
Yes it does if you're on nc1 firmware. Seems it didn't work on nb1
Sent from my Nexus 5 using XDA Free mobile app
I shall hope to get lucky and have the NC1 firmware
First need to shout out the towelroot method for root and BL unlock: http://forum.xda-developers.com/showthread.php?t=2783157
SO easy and worked. Love it
Now that I have root AND unlocked BL, will be grabbing me some TWRP, backing up stock and trying some ROMs.
Question is: which one? I've read on some posts that only 1 or 2 ROMs work with KK-based phones. Is this accurate? I believe one post I read said only CM11 works, and its very laggy.
So which to grab? Do all KK ROMs under the development page work after the towelroot exploit? CM11, CarbonRom, Google Play Edition etc? Also, which has best,most reliable native wifi tether working? Any other big bugs among the ROMs that actually work?
You can still use the ones that don't support the new bootloader and kernel by downgrading to jb 4.1.2 since your now bootloader unlocked
ckfalls said:
First need to shout out the towelroot method for root and BL unlock: http://forum.xda-developers.com/showthread.php?t=2783157
SO easy and worked. Love it
Now that I have root AND unlocked BL, will be grabbing me some TWRP, backing up stock and trying some ROMs.
Question is: which one? I've read on some posts that only 1 or 2 ROMs work with KK-based phones. Is this accurate? I believe one post I read said only CM11 works, and its very laggy.
So which to grab? Do all KK ROMs under the development page work after the towelroot exploit? CM11, CarbonRom, Google Play Edition etc? Also, which has best,most reliable native wifi tether working? Any other big bugs among the ROMs that actually work?
Click to expand...
Click to collapse
I'm running cm11 and I've had little to no lag issues
Sent from my DROID RAZR M using XDA Premium 4 mobile app
Kitstalk at droidrzr.com i don't know if I'm allowed to post the link as it requires a registration to download... Always been my favorite...
Sent from my XT907 using xda app-developers app
Thanks guys. Yeah I know I can downgrade but happy with KK changes, esp full screen over soft keys.
Will look into kitstalk thx. Yeah seems CM11 has good results. Either of these have native WiFi tether working?
Sent from my XT907 using XDA Free mobile app
ckfalls said:
Thanks guys. Yeah I know I can downgrade but happy with KK changes, esp full screen over soft keys.
Will look into kitstalk thx. Yeah seems CM11 has good results. Either of these have native WiFi tether working?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Cm11 has a working tether setting. I haven't connected anything to the Hotspot but it turns on.
Sent from my DROID RAZR M using XDA Premium 4 mobile app
thewraith420 said:
You can still use the ones that don't support the new bootloader and kernel by downgrading to jb 4.1.2 since your now bootloader unlocked
Click to expand...
Click to collapse
So the RazrM still can't use current roms even with the bootloader unlocked ??
aaronpw0621 said:
So the RazrM still can't use current roms even with the bootloader unlocked ??
Click to expand...
Click to collapse
You can use the new or older roms with unlocked bootloader just now you need to pay attention to what bootloader + kernel your on. The test builds of cm11 coming out won't work on the old bootloader + Kernel and the older ones won't work with the new kk bootloader + kernel
thewraith420 said:
You can use the new or older roms with unlocked bootloader just now you need to pay attention to what bootloader + kernel your on. The test builds of cm11 coming out won't work on the old bootloader + Kernel and the older ones won't work with the new kk bootloader + kernel
Click to expand...
Click to collapse
Just to clarify I am using the Droid Razr M (xt907). I had already taken the ota for 4.4.2 before i used towelroot. I have so far only got one ROM from @dhacker29 to boot. Its a cm11 from him. I can't figure out exactly which ROMs to flash. Is it the ones listed for the moto_msm 8960 or the ones listed for KK???
thewraith420 said:
You can use the new or older roms with unlocked bootloader just now you need to pay attention to what bootloader + kernel your on. The test builds of cm11 coming out won't work on the old bootloader + Kernel and the older ones won't work with the new kk bootloader + kernel
Click to expand...
Click to collapse
So I'm not used to looking for BL/kernel compatability usually I don't see this in the OP for a ROM, typically only see android flavor it based on, "JB" or "kk", which I thought would dictate whether a ROM would work on a device. Guess we need to look in the post for BL/kernel version (both which get updated during an OTA update?)
Like I said CM11 was the only one I knew of that for sure worked post-towelroot, that's why I was looking to see if others knew which other ROMs worked as well.
I know we can check kernel version in setting, if kernel matches a ROM then were bound to have the BL that matches as well, correct?
Sent from my XT907 using XDA Free mobile app
Only ones listed for KK will work for you now since your on the 4.4.2 ota however if you downgrade via fxz to 4.1.2 then you'll able to run the msm 8960 builds currently there are more choices once downgraded.
Downgrade tutorial
http://forum.xda-developers.com/showthread.php?p=53474077
Hello,
My wife has RAZR M running stock and rooted 98.15.66 rom. Bootloader was never unlocked but I think it's still possible with this version of rom. am I right? Last time I was doing something with her phone was almost 2 years ago and I'm more samsung guy so need some directions here She loves this phone and doesn't want to get anything new. Phone is getting to run slower so it needs cleanup. Is it worth to upgrade it to KK rom or just do factory restore and set it up from scratch on this 4.1.2 rom? Any major bugs on stock KK rom? CM12 has too much bugs as of now for her. What about CM11, is there fully functional and bugs free version for RAZR M available?
.66 is indeed unlockable right away, but just so you could experience stock KitKat and see if it's more fitting, simply upgrade to 183.46.10 (ATTENTION: not .15!!!) and unlock the bootloader there. Guides are there in the General section. Note that you will lose data and internal storage contents, so back up properly.
After that if you feel uncomfortable with KitKat, you can freely downgrade to Jelly Bean whenever you prefer.
Haven't met any serious bugs even in CM12, let alone CM11. Don't know what kind of deal-breaking bug you're talking about.
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
.66 is indeed unlockable right away, but just so you could experience stock KitKat and see if it's more fitting, simply upgrade to 183.46.10 (ATTENTION: not .15!!!) and unlock the bootloader there. Guides are there in the General section. Note that you will lose data and internal storage contents, so back up properly.
After that if you feel uncomfortable with KitKat, you can freely downgrade to Jelly Bean whenever you prefer.
Haven't met any serious bugs even in CM12, let alone CM11. Don't know what kind of deal-breaking bug you're talking about.
Click to expand...
Click to collapse
According to Strife89 post here: http://forum.xda-developers.com/showpost.php?p=58531079&postcount=80 there are couple of bugs that I know my wife is not gonna like for example microphone level and able hear own voice when using headphones.
Do you think it's better to unlock bootloader before upgrading to KK or it's doesn't matter? Thanks.
SotYPL said:
According to Strife89 post here: http://forum.xda-developers.com/showpost.php?p=58531079&postcount=80 there are couple of bugs that I know my wife is not gonna like for example microphone level and able hear own voice when using headphones.
Do you think it's better to unlock bootloader before upgrading to KK or it's doesn't matter? Thanks.
Click to expand...
Click to collapse
I would suggest that you unlock the bootloader now before you upgrade.
Sent from my Moto G™
Unlock unlock unlock. It worth the candle. I think your wife will be happy with cleaned up 4.1.2 or 4.4.2. Last one is more stylish, and comfortable in use, as for me.
OK is that correct order to get it upgraded?
1. Unlock boot loader using apk or Motopocalypse from this thread: http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
2. Flash KK firmware using RSD Lite but I'm not sure which image from this: http://www.drdevs.com/devs/FXZ-files/XT907 (Droid RAZR M)/ website is safe to use. Can I use latest one 20.62-15.1 after unlocking boot loader or do I have to stay stay with 20.62-10?
3. Flash TWRP from this thread: http://forum.xda-developers.com/showthread.php?t=2776515
4. FLash SuperSU from recovery
Is that correct way to handle it?