Database Users

4.2.2 update

Will the 4.2.2 OTA for my Nexus 7 take away root access?
Sent from my Nexus 4

Yes.
http://forum.xda-developers.com/showthread.php?t=2144330
There's a long thread on 4.2.2 already.

What about the bootloader? Will it relock it? Or is it left alone?
Sent from my Nexus 4

Also, I was just reading through that thread and it said if you have SuperSU that it won't unroot. Is that true? Or do I need to use ota rootkeeper? I know that thread may have the answers I'm looking for, but I'm too tired to read through it all. I ask all these questions because I have no computer to reroot and reunlock the bootloader with.
Sent from my Nexus 4

Slender Troll said:
Also, I was just reading through that thread and it said if you have SuperSU that it won't unroot. Is that true? Or do I need to use ota rootkeeper? I know that thread may have the answers I'm looking for, but I'm too tired to read through it all. I ask all these questions because I have no computer to reroot and reunlock the bootloader with.
Sent from my Nexus 4
Click to expand...
Click to collapse
Afaik it won't relock your bootloader.
Sent from my HTC One X

I flashed back to stock.
Flashed the update
Flashed a SuperSU.zip
Rebooted
Then reinstalled twrp through goo.Im app
When I flashed update I lost root and recovery
And all is good again
Sent from my Nexus 7 using XDA Premium HD app

Slender Troll said:
Will the 4.2.2 OTA for my Nexus 7 take away root access?
Sent from my Nexus 4
Click to expand...
Click to collapse
I was on JOP40D (4.2.1) Stock, rooted, with CWM 6.0.2.3. I downloaded this OTA file http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip from the link in the other 4.2.2 thread (http://forum.xda-developers.com/showthread.php?t=2144330)
I booted into CWM, and flashed the downloaded ZIP file as normal
When I told CWM to reboot, CWM warned me the update would flash stock Recovery and do I want to STOP this from happening and I said YES.
It then said I had lost root, and do I want to restore root, and I said YES.
It then booted into Android and continued with the upgrade.
I now have 4.2.2 stock installed (JDQ39), and still have root and custom recovery, and an unlocked bootloader.
From what I have read, if you 'sideload' the update using ADB, or do a normal OTA update, you will lose root and custom recovery. However, using the steps above will keep root and recovery for you

What if I'm using TWRP?
Sent from my Nexus 4

Slender Troll said:
What if I'm using TWRP?
Sent from my Nexus 4
Click to expand...
Click to collapse
im in the same boat,
im on 4.1.2 twrp what do i need to do to get to 4.2.2? just use that ota root keeper?

Slender Troll said:
What if I'm using TWRP?
Sent from my Nexus 4
Click to expand...
Click to collapse
TWRP is same to CMW, but for sure you should install Voodoo OTA Rootkeeper, backup SU then flash the 4.2.2 update.zip. Finally, open Voodoo and restore the backup SU --> your Root is kept. Just in case you need to verify root will work or not. Go to Play Store, install Root Checker (joeykrim) and check your root permisson.
I updated my N7 to 4.2.2 without removing root by these steps above.

Benjoy Ericsson said:
TWRP is same to CMW, but for sure you should install Voodoo OTA Rootkeeper, backup SU then flash the 4.2.2 update.zip. Finally, open Voodoo and restore the backup SU --> your Root is kept. Just in case you need to verify root will work or not. Go to Play Store, install Root Checker (joeykrim) and check your root permisson.
I updated my N7 to 4.2.2 without removing root by these steps above.
Click to expand...
Click to collapse
Can I do this without a computer?
Sent from my Nexus 4

Slender Troll said:
Can I do this without a computer?
Sent from my Nexus 4
Click to expand...
Click to collapse
Yes, if you can put your 4.2.2 OTA update.zip in your N7 Internal Storage.
Maybe by downloading the zip through wifi connect.

Benjoy Ericsson said:
Yes, if you can put your 4.2.2 OTA update.zip in your N7 Internal Storage.
Maybe by downloading the zip through wifi connect.
Click to expand...
Click to collapse
Wi-Fi connect? And where do I put it once I have it?
Sent from my Nexus 4

Slender Troll said:
What if I'm using TWRP?
Sent from my Nexus 4
Click to expand...
Click to collapse
I don't think it matters...
I used TWRP to flash the update.
Afterwards, the bootloader was still unlocked... but had been updated from 4.13 to 4.18.
And I had to reflash TWRP as the update had wiped it out, effectively resetting recovery back to Googles default recovery.
Rgrds,
Ged.

Slender Troll said:
Wi-Fi connect? And where do I put it once I have it?
Sent from my Nexus 4
Click to expand...
Click to collapse
This is OTA link for N7 Wifi Only.
Connect to wifi, download the 4.2.2 update.zip to your internal storage from this link http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip (anywhere is ok, be sure to remember the path). Reboot your N7 to recovery mod (TWRP), choose install and browse to where you put your zip in internal storage.

Benjoy Ericsson said:
Connect to wifi, download the 4.2.2 update.zip to your internal storage from this link http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip (anywhere is ok, be sure to remember the path). Reboot your N7 to recovery mod (TWRP), choose install and browse to where you put your zip in internal storage.
Click to expand...
Click to collapse
Just to clarify, I can leave it in the download folder?
Sent from my Nexus 4

So I'm in recovery and at the part where it gives me the option to flash. Is there anything I need to do or back up before I flash the OTA so that I don't lose root?
Sent from my Nexus 4

Success!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using Tapatalk HD

Just downloaded the OTA zip, went to recovery and tried "install" (both checkmarks to check md5 and zip off) and got FAILED! The device booted normally afterwards. I copied file via USB cable in standard media mode... what am I doing wrong? On 4.2.1, stock, rooted, 16gb Wifi only N7.

dalanik said:
Just downloaded the OTA zip, went to recovery and tried "install" (both checkmarks to check md5 and zip off) and got FAILED! The device booted normally afterwards. I copied file via USB cable in standard media mode... what am I doing wrong? On 4.2.1, stock, rooted, 16gb Wifi only N7.
Click to expand...
Click to collapse
Try downloading it using Wi-Fi from the link above, and then back everything up. what recovery are you using? I left the zip in the download folder, so I wouldn't lose it.
Sent from my Nexus 4

Cannot install CWM over TWRP

I've been at this for about 5 hours now, and I can't seem to get CWM installed.
I decided to flash to stock fw (4.2.2) so I could carrier unlock my phone. After I flashed to stock, I used the CASUAL tool to do this.
After I had root, I tried getting CWM back so I could restore my backup, prior to this whole process, however every time I have attempted to flash CWM the phone reboots to TWRP.
I thought I knew about this kind of stuff, but now it's just starting to get to me
Has anyone encountered this or know of a fix?
Thanks.

tasiv said:
I've been at this for about 5 hours now, and I can't seem to get CWM installed.
I decided to flash to stock fw (4.2.2) so I could carrier unlock my phone. After I flashed to stock, I used the CASUAL tool to do this.
After I had root, I tried getting CWM back so I could restore my backup, prior to this whole process, however every time I have attempted to flash CWM the phone reboots to TWRP
I thought I knew about this kind of stuff, but now it's just starting to get to me
Has anyone encountered this or know of a fix?
Thanks.
Click to expand...
Click to collapse
You messed up. You have an i337 and are now on mf3 firmware. You can't put on a custom recovery. Safestrap is you're only option
Sent from my Nexus 5

jd1639 said:
You messed up. You have an i337 and are now on mf3 firmware. You can't put on a custom recovery. Safestrap is you're only option
Sent from my Nexus 5
Click to expand...
Click to collapse
I'm currently running JDQ39.I337UDUAMDB (galaxy s4 stock FW v4.2.2). I came from the latest Google Edition rom posted by Danvdh.
When I run CASUAL that flashes a recovery. If I now have a mf3 device, how could I have flashed TWRP with CASUAL?
I have somehow managed to get another recovery installed using the following instructions:
download the two files in the instructions
su
cd /data/local/tmp
chmod 755 *
./lok_flash recovery recovery.lok
reboot recovery
That allowed me to change the recovery, but I really have no idea what that did.
I don't think I have an mf3 device now. Is there any way to verify this?

Check your baseband. You probably still are on mdb. Are you flashing a zip to get back to cwm? Which one
Sent from my Nexus 5

jd1639 said:
Check your baseband. You probably still are on mdb. Are you flashing a zip to get back to cwm? Which one
Sent from my Nexus 5
Click to expand...
Click to collapse
baseband = I337UCUAMDB
I'm not flashing a zip, it's apparently a (IMO) bastardized version of clockwork mod. Hell, it could be a zip, but I know I'm running a terminal command to write the recovery. I don't think I can paste links...
I have no problem flashing the google edition firmware or AOSP based firmware when I have TWRP installed. It's just trying to get rid of TWRP and go back to CWM that I want to do (because I backed up my phone in CWM and now I can't get back).

tasiv said:
baseband = I337UCUAMDB
I'm not flashing a zip, it's apparently a (IMO) bastardized version of clockwork mod. Hell, it could be a zip, but I know I'm running a terminal command to write the recovery. I don't think I can paste links...
I have no problem flashing the google edition firmware or AOSP based firmware when I have TWRP installed. It's just trying to get rid of TWRP and go back to CWM that I want to do (because I backed up my phone in CWM and now I can't get back).
Click to expand...
Click to collapse
Flash this in your current twrp, it'll replace twrp and put in cwm 6.0.4.7
Edit, PS to carrier unlock I think you need to be on mdl firmware

jd1639 said:
Flash this in your current twrp, it'll replace twrp and put in cwm 6.0.4.7
Edit, PS to carrier unlock I think you need to be on mdl firmware
Click to expand...
Click to collapse
OK, so I have TWRP right now, and I ran that utility you created for me. It failed.
here's what I can make out of the log:
assert failed: package_extract_file("orecovery-clockwork-6.0.4.7-jflteat
E:Error executing updater binary in zip '/sdcard/Download/jjd-recovery-c
Error flashing zip "/sdcard/Download/jjd-recovery-clockwork-6.0.4.7-jflt
updating partition details...
it's cut off on the right, but I think you can tell that...

tasiv said:
OK, so I have TWRP right now, and I ran that utility you created for me. It failed.
here's what I can make out of the log:
assert failed: package_extract_file("orecovery-clockwork-6.0.4.7-jflteat
E:Error executing updater binary in zip '/sdcard/Download/jjd-recovery-c
Error flashing zip "/sdcard/Download/jjd-recovery-clockwork-6.0.4.7-jflt
updating partition details...
it's cut off on the right, but I think you can tell that...
Click to expand...
Click to collapse
Sorry, I had a typo in it try this

jd1639 said:
Sorry, I had a typo in it try this
Click to expand...
Click to collapse
I feel useless.... Now It's giving me the "system software not authorized by AT&T has been found on your phone" I attempted to flash lokidoki, but I think that's just for the rom...

tasiv said:
I feel useless.... Now It's giving me the "system software not authorized by AT&T has been found on your phone" I attempted to flash lokidoki, but I think that's just for the rom...
Click to expand...
Click to collapse
Does your baseband and build number both say your on mdb firmware?
Sent from my SAMSUNG-SGH-I727

jd1639 said:
Does your baseband and build number both say your on mdb firmware?
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
currently my baseband = I337UCUAMDB
and my build number = JDQ39.i337UCUAMDB
so, yes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

tasiv said:
currently my baseband = I337UCUAMDB
and my build number = JDQ39.i337UCUAMDB
so, yes
Click to expand...
Click to collapse
Idk, what to say now. I'm thinking it's because you're on mdb and not mdl. Mdb is really old. You might try flashing mdl. You'll still be able to put on a custom recovery and flash roms just like you currently are. Just don't flash mf3 or higher. If you go that route you'll want to make sure to freeze the update.apk so the ota didn't work.
Sent from my Nexus 5

jd1639 said:
Idk, what to say now. I'm thinking it's because you're on mdb and not mdl. Mdb is really old. You might try flashing mdl. You'll still be able to put on a custom recovery and flash roms just like you currently are. Just don't flash mf3 or higher. If you go that route you'll want to make sure to freeze the update.apk so the ota didn't work.
Sent from my Nexus 5
Click to expand...
Click to collapse
I appreciate the help you've given me.
I think I may try that, I'll just have to find a copy of it somewhere. I've got my phone back into a state where I (almost) left it thanks to titanium backup and the ROM I've been using. I really liked CWM, but the features of TWRP seem promising. I've been having a little trouble backing up the phone though (I think I'm exceeding max file size of backup?) but I'm sure it'll eventually work.

[VK810] Official Kit Kat Update Information

We're all in the process of receiving and installing this update, and there are many questions about recoveries, rooting, etc. This is a thread to gather all the info we know so people don't have to be searching through tons of posts.
(I'm in the process of installing now, so I'll answer as many of these questions as I can. I will also update the OP with info from other users. If anything I state is untrue, please post and let me know.)
Can I take the update while rooted?
Yes! If you are on 4.2 and rooted but on STOCK RECOVERY, you can take the OTA and keep root.
Can I take the update with TWRP installed?
No! You will bootloop into recovery.
Is there an alternative/manual/TWRP method of installing?
Yes, see below post.
How am I supposed to update if I installed TWRP?
See below post, "README if you are currently on JB4.2.2"
Alternative method: "download flashify from the play store, backup twrp, then flash the recovery.img from OP. No pc needed & 100% pain free." Thank you to 86shelby. Then take the OTA.
Can I root the 4.4 version?
As of 8/26, yes! Stumproot works with the Bruteforce method. http://forum.xda-developers.com/show....php?t=2850906
Can I downgrade from 4.4 to 4.2?
Yes
If anyone else has questions they'd like posted, please let me know, and I'll put them in.

NOTE: If you want root/twrp in KK4.4.2, you'll need to pre-root in JB4.2.2 before OTA update(towelroot works in JB4.2.2, but not in KK4.4.2)
Looks like Stumproot works with KK4.4.2
README if you have a non-booting device
If you tried OTA update with TWRP recovery and get stuck in a bootloop for TWRP
Do one of the options below:
A) If you still want 4.4.2 via Verizon OTA, flash stock recovery
Go into TWRP, restore stock recovery via link below
http://forum.xda-developers.com/showpost.php?p=52975059&postcount=65
B) If you want to stop the bootloop, and flash 4.4.2 via TWRP backup from below...
Go into TWRP, wipe OTA partition (which signals the device to keep going into recovery)
http://forum.xda-developers.com/showthread.php?p=51749086#post51749086
Click to expand...
Click to collapse
If I mess everything up and device doesn't boot
Restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)​
README if you are currently on JB4.2.2
If you already have TWRP, you can flash 4.4.2 via the TWRP backup below (probably can just flash over 4.2.2 without factory reset... do factory reset only if something goes wrong)
http://forum.xda-developers.com/showthread.php?p=53043541#post53043541
If you want to apply update via Verizon OTA, READ below first
If you have TWRP installed, you'll need to flash stock recovery. Either (A)
restore stock recovery only, or restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)
NOTE: some people have problems with OTA even after restoring stock recovery. You'll have to restore using the (B) method, and lose everything
[*]If you want root in 4.4.2, you'll need to apply root BEFORE OTA (via towelroot, ...?). root is allowed during OTA, will be maintained after OTALooks like stumproot works
Apply OTA, hope nothing goes wrong
Yay!
Click to expand...
Click to collapse
README if you are currently on KK4.4.2
Splitwindow/multiwindow on 4.4.2
http://forum.xda-developers.com/lg-...10-splitwindow-multiwindow-stock-4-4-t2837326
Root on 4.4.2: Use Stumproot
TWRP on 4.4.2
Root ? (Towelroot isn't working though)
Flash 4.2.2 aboot.img and TWRP.img
A) Upload aboot.img from 4.2.2 to device, then do
Code:
adb shell
su
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
B) Follow steps in TWRP thread to install TWRP
Click to expand...
Click to collapse
4G LTE does not work on 4.4.2?
Flash modem from 4.2.2 -> http://forum.xda-developers.com/showpost.php?p=54584896&postcount=5
Going from 4.4.2 back to 4.2.2
Install TWRP (see section above)
Get 4.2.2 TWRP backup from here and restore
or restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)
Click to expand...
Click to collapse
​

Guess I got lucky - never got around to installing the custom recovery. I MEANT to do that....

https://pvzwmdmcdn.vzw.motive.com/firmware/LG_VK810_11A_TO_22B.bin
in case you want to poke around
Verizon LG G2 users say it's okay to be rooted, just need stock recovery for OTA update... let's see what happens..
yeah, 0x136 error when it tries to update. people say 0x136/0x13E errors are because of unlocked bootloaders... i guess we need to flash completely stock via KDZ file, then take ota, then use stuff like towelroot

So this is what I get when I check for update. I'm stock unrooted I even did a FDR. Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my XT1080 using Tapatalk

Towelroot doesn't work yet with the new update. I took the update completely stock and unrooted and I'm not able to root now.

modus81 said:
Towelroot doesn't work yet with the new update. I took the update completely stock and unrooted and I'm not able to root now.
Click to expand...
Click to collapse
have you tried other root methods?
ioroot, or this root below? (
http://forum.xda-developers.com/showthread.php?t=1886460&highlight=4+2+2

paperWastage said:
https://pvzwmdmcdn.vzw.motive.com/firmware/LG_VK810_11A_TO_22B.bin
in case you want to poke around
Verizon LG G2 users say it's okay to be rooted, just need stock recovery for OTA update... let's see what happens..
yeah, 0x136 error when it tries to update. people say 0x136/0x13E errors are because of unlocked bootloaders... i guess we need to flash completely stock via KDZ file, then take ota, then use stuff like towelroot
Click to expand...
Click to collapse
How do I install this?
Sent from my VK810 4G using Tapatalk

gfullwr70 said:
How do I install this?
Sent from my VK810 4G using Tapatalk
Click to expand...
Click to collapse
you don't. go through Settings-> System update

paperWastage said:
you don't. go through Settings-> System update
Click to expand...
Click to collapse
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk

gfullwr70 said:
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Same here

Flashing comletely stock via .kdz file
I'm getting the 0X13E error. Does anyone have the the process for this? I saw a different thread that directed to a droidreviews.com website but one of the files it said to download, my Chrome browser scanned as malicious so I stopped pursuing that route.

ssinn said:
Same here
Click to expand...
Click to collapse
gfullwr70 said:
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123

paperWastage said:
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123
Click to expand...
Click to collapse
Thanks this is what I was looking for. I'll give it till tonight to see if the ota shows up then I'll try this method.
Sent from my XT1080 using Tapatalk

paperWastage said:
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123
Click to expand...
Click to collapse
So is this only if you can't download the ota update or if you get an error while trying to install it after downloading it?

prana22 said:
So is this only if you can't download the ota update or if you get an error while trying to install it after downloading it?
Click to expand...
Click to collapse
first one.... my tablet wasn't able to find an OTA on 4G LTE (on t-mobile's network), but wifi works fine

Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.

rjkmadison said:
Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.
Click to expand...
Click to collapse
That's interesting, and good to know. Can anyone else verify this? I didn't think the update would go through if you were rooted. Now I might downgrade through kdz again and root before I take the OTA.

rjkmadison said:
Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.
Click to expand...
Click to collapse
go flash TWRP, make backup of stock and share it please?

How can I revert to stock recovery in OSX? All I see is the LG Mobile tool for windows?

[Q] SuperSU can't detect su binary after reboot

I rooted my phone with Kingroot, and ran this script to replace the Kinguser with SuperSU: http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html?m=1
After launching SuperSU it updates the binary and everything works fine until I reboot my phone. Now when I launch SuperSU it says no su binary installed. Using es file explorer I can see the su is in /system/xbin where it should be but SuperSU can't see it.
After rerooting with Kingroot and doing the same process over SuperSU will once again work fine until I reboot my phone. Anyone know what's going on and how I can get SuperSU to work properly?

Anyone?
I tried flashing the SuperSU.zip, but when I launch the app it fails to update the binary. I've also tried installing ChainsDD Superuser but it also fails to update the binary. I've even tried manually copying, setting permissions, and symlinking the files found in the SuperSU.zip, but it still fails to update.
I don't like using Kingroot because apps like Titanium Backup and Lucky Patcher don't work with it's su binary. Has anyone encountered this before? Why won't SuperSU update? And when it does update why can't it survive past a reboot? This is stressful ha. Any help is very much appreciated.
By the way I'm using a Cricket Galaxy S4 (SGH-I337Z). It's a weird model that few people seem to know about (I337ZTUUBOA1). The only root method that works on it is Kingroot otherwise I would have just rooted it some other way.

I had an idea wile reading your post could u try flashing TWRP for ur phone then rooting with the built in installer might be worth a try but u might need to Un root or flash back to what ever firmware ur using to remove root so that TWRP sees that ur not rooted

xstokerx said:
I had an idea wile reading your post could u try flashing TWRP for ur phone then rooting with the built in installer might be worth a try but u might need to Un root or flash back to what ever firmware ur using to remove root so that TWRP sees that ur not rooted
Click to expand...
Click to collapse
I've got twrp flashed. How do I use the built in root installer??

When u boot into system from TWRP it will ask you if u want to root the system but it only asks if TWRP can't detect root.

xstokerx said:
When u boot into system from TWRP it will ask you if u want to root the system but it only asks if TWRP can't detect root.
Click to expand...
Click to collapse
I unrooted and rerooted with twrp. It installed su binary, but when I install SuperSU and launch it it still gives the no binary installed error

Nihilian said:
I unrooted and rerooted with twrp. It installed su binary, but when I install SuperSU and launch it it still gives the no binary installed error
Click to expand...
Click to collapse
Try rooting with kingroot, then uninstall king user by going into king user and unrooting. Once that is done, download the newest version of SuperSU.zip (update-supersuv2.46.zip I think is newest) then copy to phone storage, reboot to twrp and then flash the SuperSU zip. Reboot and profit!
Hope this helps!
Sent from my A0001 using XDA Free mobile app

Nihilian said:
I unrooted and rerooted with twrp. It installed su binary, but when I install SuperSU and launch it it still gives the no binary installed error
Click to expand...
Click to collapse
Sorry to hear was worth a shot I can't think of any thing else right now :crying:

Klown80 said:
Try rooting with kingroot, then uninstall king user by going into king user and unrooting. Once that is done, download the newest version of SuperSU.zip (update-supersuv2.46.zip I think is newest) then copy to phone storage, reboot to twrp and then flash the SuperSU zip. Reboot and profit!
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Still no luck I think it's an issue with the SuperSU app. Something during a reboot causes it to break for some reason. I really hope it can be fixed :/

Well only thing I can think of is odin to stock and start over or find a nice custom rom that works with your phone that comes pre rooted if there are any.......

xstokerx said:
Well only thing I can think of is odin to stock and start over or find a nice custom rom that works with your phone that comes pre rooted if there are any.......
Click to expand...
Click to collapse
Finally found a working custom rom and everything is working. Thanks

Nihilian said:
Finally found a working custom rom and everything is working. Thanks
Click to expand...
Click to collapse
Awsome to hear u found something that works for u and ur welcome ?

I don't wanna open new topic coz I have similar problem.....
I have huawei g630, rooted and unlocked bootloader, but no cwm.... and supersu gives me this messages.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and when I click on that phone restarts and nothing happens..... when I cancel that this is msg.....
what could be the problem?

jabre said:
I don't wanna open new topic coz I have similar problem.....
I have huawei g630, rooted and unlocked bootloader, but no cwm.... and supersu gives me this messages.....
and when I click on that phone restarts and nothing happens..... when I cancel that this is msg.....
what could be the problem?
Click to expand...
Click to collapse
I'm sorry but I probly can't help I know nothing about your phone this is the att/Canadian s4 forum how did u get your phone rooted? U can try unrooting and rooting with a different method or retry with same method

MMB29K 6.0.1 OTA Lottery Wait Room : Here We Are Again!

Please post below when you got the OTA and what carrier you're on!
I always love to watch how the OTA's hit peoples devices. From where they're located to what carrier they're on, its interesting to see who gets it first and sadly last.
I am stock, MDB08L 6.0.0, T-Mobile US. The wait begins.

Here we go again! People *****ing about updates!

Hahaha [emoji23]
Sent from my Nexus 5X using Tapatalk

Updated via fastboot. Root + xposed work just fine

mymusicathome said:
Updated via fastboot. Root + xposed work just fine
Click to expand...
Click to collapse
Which type of root and which boot image are you using?

mymusicathome said:
Updated via fastboot. Root + xposed work just fine
Click to expand...
Click to collapse
Did you wipe your data of did you just flash the system?

kbbeer said:
Which type of root and which boot image are you using?
Click to expand...
Click to collapse
Chainfire systemless boot+root
Alaris said:
Did you wipe your data of did you just flash the system?
Click to expand...
Click to collapse
Nope. Flashed everything but userdata

Thinking about manually flashing this since I'm rooted on the modified boot.img.
What steps do I need to take? Unroot then flash everything then reflash modified boot then reroot?

Flash bootloader, radio, boot, cache, system, vendor and then systemless root boot. No need to unroot. Flashing the OEM boot might not be needed but I do it anyway. I boot into Android and then boot to recovery and flash superuser

good 6.0.1 factory image flash-all install
Sent from my Nexus 5X using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

antiseen said:
Thinking about manually flashing this since I'm rooted on the modified boot.img.
What steps do I need to take? Unroot then flash everything then reflash modified boot then reroot?
Click to expand...
Click to collapse
I flashed using the flash-all.bat script. Deleted "-w" from the script to get rid of the data wipe. Reinstalled TWRP and re-rooted using the traditional root method. I used the modified boot image for MDB08M.

windows8k said:
good 6.0.1 factory image flash-all install
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Niceeee

ING3NIEUR said:
I flashed using the flash-all.bat script. Deleted "-w" from the script to get rid of the data wipe. Reinstalled TWRP and re-rooted using the traditional root method. I used the modified boot image for MDB08M.
Click to expand...
Click to collapse
How did you get the flash-all.bat script to work? It never did for me.. Do you have to get bootloader unlocked?

Encrypted11 said:
How did you get the flash-all.bat script to work? It never did for me.. Do you have to get bootloader unlocked?
Click to expand...
Click to collapse
Yes. Beware, doing so will wipe your phone.
Sent from my Nexus 5X using Tapatalk

Encrypted11 said:
How did you get the flash-all.bat script to work? It never did for me.. Do you have to get bootloader unlocked?
Click to expand...
Click to collapse
Bootloader must be unlocked. It's even in the flashing instructions on the Factory Images download page.
---------- Post added at 06:38 PM ---------- Previous post was at 06:29 PM ----------
PiousInquisitor said:
Yes. Beware, doing so will wipe your phone.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
No wipe if you delete "-w" from the script.

PiousInquisitor said:
Here we go again! People *****ing about updates!
Click to expand...
Click to collapse
He wasn't *****ing at all.

I'm on Telus but I bought it from the google store so carrier-free. no OTA yet, currently on build MDB08L. Please hurry googs, I want the new emoji

ING3NIEUR said:
Bootloader must be unlocked. It's even in the flashing instructions on the Factory Images download page.
---------- Post added at 06:38 PM ---------- Previous post was at 06:29 PM ----------
No wipe if you delete "-w" from the script.
Click to expand...
Click to collapse
I was warning him about unlocking the bootloader.

Just updated via fastboot and regular root using BETA SuperSU 2.52 with the modified boot.img from the MDB08I/MDB08M builds and everything was working well but I just now noticed my camera shows a black screen. Rebooting didn't help so I'm wiping cache in TWRP and if that doesn't work going to redownload and reflash the images.
Edit: Seems to be an issue with using the old modified boot image from MDB08I/MDB08M for root from Chainfire, exploring now....
Edit 2: Just loaded the boot.img from the MMB29K build but now it seems like I'm in a bootloop. Going to reflash everything again to confirm it's the modified boot.img from MDB08I/MDB08M causing the camera not to work.
Edit 3: Reflashed System and Boot from MMB29K build which obviously removes system root but the Camera is working again. Looks like we will need a modified boot.img from the MMB29K build for system root to work.

ING3NIEUR said:
I flashed using the flash-all.bat script. Deleted "-w" from the script to get rid of the data wipe. Reinstalled TWRP and re-rooted using the traditional root method. I used the modified boot image for MDB08M.
Click to expand...
Click to collapse
I manually flashed everything, but essentially the same process. I also used the 8m modified boot.img