4.3 OTA ML2 Root Method!
- Thread starter meraz9000
- Start date
Yes I got that earlier before I ran Sunderwear's method, already allowed access for my laptop...once done you don't have to keep doing this right?
do we need to be in download mode to run this install.bat file? (this 2 min between post bs is frustrating)
Last edited:
Did it reboot your phone and tell you to grant superuser access to adb shell. Then tell you to open SU and allow it to update?
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
don't recall seeing that msg, it just rebooted to normal mode of use
I turned off phone, disconnected and turned it back on and reconnected, I'm good to go on USB, and have MTP mode selected, had PTP mode previously...
Last edited:
Thats where the process stopped and you have no root access because of this. Run the install bat again I would clear allowed devices in developer settings before connecting your phone. When your device is recognized it will tell you then it will say sending files follow the prompts on your phone while you run the install bat
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
So you're saying to revoke debugging authorization and redo after reconnecting?
I would. Dont plug in your phone until the bat is open
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
---------- Post added at 02:05 PM ---------- Previous post was at 02:02 PM ----------
Also make sure you have first flashed the pwned.kernel it will not work on the stock kernel
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
I was probably so focused upon Odin and forgot about those steps on saferoot and su
Last edited:
You flash the pwned.kernel reboot your phone run saferoot then flash back to the stock kernel
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Done deal, thanks my friend...I'm out of "Thanks" for the day but count on getting handful tomorrow :good:
Under SuperSU apps I have ADB Shell and Titanium Backup
Last edited:
Glad to help thats what its all about
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Yep I really appreciate your time through all of this, I just got a bit ahead of myself and skipped those steps, but glad you were around.
Question, I did of course update SuperSU binaries and disabled KNOX but is there a place to see that KNOX is indeed disabled (is an app in the store for this) and also what about safestrap and other recovery tools, TWRP etc?
Last edited:
Safestrap 3.71 apk is the only available recovery
http://xdaforums.com/showthread.php?t=2607006
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
This is recommended to install then, how do we install these .apk files again, transfer them to the phone via Kies3 etc?
Edit: I copied it to my SD card and installed it from there, seemed to work well.
Last edited:
Has anyone got their hands on the ML2 modules needed to flash Roms?
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Hopefully someone can put something together soon
Found them
http://xdaforums.com/showthread.php?p=51401818
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Last edited:
If you're on AT&T ML2 it'll work to root your phone no matter how it was applied and should work on any other 4.3 version that may come out before 4.4 (though I doubt there will be any).
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
36Hello there fellow XDA peeps. I figured out the way to root the OFFICIAL OTA 4.3 Update. Build Number UCUBML2.
1. Download the the following file http://www.mediafire.com/download/x4n952wzyr3eobd/pwnedkernel.tar.md5 and flash it with odin under PDA. I pulled the boot.img from the 4.3 leak and as we all know it is vulnerable to saferoot and other root method around.
2. After phone reboots enable USB debugging mode try using saferoot or Vroot..google it... it will work .
3. Because this is an older kernel, wifi and some other stuff dont work but dont panic. Flash the next file https://www.mediafire.com/?08j1wqn0x7igjq0 with odin under PDA . This is the stock ML2 kernel.
4. After phone reboots launch Supersu and allow the binary to get updated. Also disable that pesky Knox :laugh:
5 .???
6. Profit. Enjoy your rooted apps and safestrap :good::good:
P.S. I have the 4.2.2 modem because I had to repair the imei of the phone..but just ignore it. and again enjoy
Credits to all the people that came up with the kernel exploits like Saferoot etc.2I guess I only partially answered your question, so I'll go through your post line by line to make sure I convey what I was unable to last time.
I don't think it's a matter of preference for people whether they choose 4.3 or 4.4, on some phones 4.4 just flat out doesn't work so they are forced to use 4.3 if they want a working phone.
As I tried to say in my previous post, the 4.4 OTA was released on April 16 and subsequently pulled by AT&T on April 19 due to bugs. This OTA was captured and anybody who wants update to 4.4 manually is able to do so. Additionally root has been achieved on 4.4 and there are many people who are running rooted 4.4.2 right now. You can find more information on downloading and rooting the 4.4.2 update in the i537 Firmware Thread. So it's not so much that 4.3 provides more flexibility (both 4.3 and 4.4 have been rooted), but the fact that on some phones 4.4 doesn't work properly.
It sucks that you bricked your phone, but for future reference you can always flash the 4.3 ML2 Odin package and it should save your phone. Again you can find links to more information about ML2 and the Odin packages in the i537 Firmware Thread. If you're worried about bricking your phone after rooting, I would suggest looking into SafeStrap. To summarize what it does, it basically creates a second ROM on your phone that is independent of your original (stock) ROM. This way you can mess with your second ROM and do pretty much anything you want to it, even completely corrupt it, and you'll still be able to fall back to your working stock ROM and still have a working phone. It's a really great alternative to having a locked phone and not being able to flash custom ROMs. I would do a bit of research about SafeStrap, how to use it and how it works, it could save you headaches in the future.
Root methods for every version of firmware is linked to in the i537 Firmware Thread.
Just so you're aware, once you change your system files in any way (i.e. rooting) you will no longer be able to receive OTA updates. For some people this is a deal breaker, but you can always flash the 4.3 ML2 Odin package to return to a stock, untouched system that will be able to receive OTA updates again. The only downside to this is that the Odin package will completely wipe your phone when you flash it.
I hope this answered your questions, but my suggestion again is to look at all the links in the i537 Firmware Thread and read everything 3 or 4 times before you do anything. People have done everything you are trying to do and have run into the problems that you will inevitably run into. There are solutions for everything posted in this forum you just need to make sure you read about what you're going to attempt before you actually do it to minimize your risk.2the instructions its very clear dont need to some one make a video first download the the file 4.3 ML2 then unzip the file you will see 4 files open Odin go to the download mode press volume up & power botton
BL. goes to the bootloder
AP. goes to the PDA
CP.goes to the phone
CSC . goes to the CSC
about root 4.3 ML2 .. download the 2 files first flash pwnedkernel via Odin put in PDA then download saferoot on you computer unzip it then open the file go to the install open it ..you will see command put your phone on USB debugging plug on you computer press enter a few mints your phone will reboot when your phone get root flash the originalkrenel same thing on PDA your done... sorry about my English
Sent from my SAMSUNG-SGH-I537 using xda app-developers app1
Rename wssyncmldm.apk and wssyncmldm.odex to wssyncmldm.apk.bak and wssyncmldm.odex.bak respectively.
Or just update to 4.4.2 and root with towelroot. It's a lot easier than you think.
