Database Users

Stock FRF72 -> FRF83 OTA

I'm not taking credit, but the OTA update from FRE72 to FRF83 can be found here:
forum.xda-developers.com/showpost.php?p=6926438&postcount=116
If someone would root it, that would be greatly appreciated.

Just use Cyanogen's quick rooter.

mortzz said:
Just use Cyanogen's quick rooter.
Click to expand...
Click to collapse
Are you sure it works?

I'll look into that, but to even install the FRF83 update I believe I need to install the stock recovery image beforehand. Since I'm not overly in the mood to do that, I'm happy to wait for a pre-rooted one to pop up.
Thanks for the suggestion, however.

link verified, just waiting for this long boot.
Everything looks good!

SBERG117 said:
Are you sure it works?
Click to expand...
Click to collapse
Quite sure:
{
"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"
}
As always, do a NANDroid first.

What was your process? Did you have to use stock recovery, or a custom one? is your WiFi working on FRF83? Were you rooted with FRF72 beforehand?

mortzz said:
Quite sure:
As always, do a NANDroid first.
Click to expand...
Click to collapse
Cool, just did a nandroid.
So i just put both FRF83 and froyo rooter on my ROOT and flash both? (frf83 first) Its that simple?
Thnx.

SBERG117 said:
Cool, just did a nandroid.
So i just put both FRF83 and froyo rooter on my ROOT and flash both? (frf83 first) Its that simple?
Thnx.
Click to expand...
Click to collapse
This is assuming you've already upgraded to FRF83. The stock builds won't flash through a custom recovery.
There's an pre-rooted update.zip floating around that you can just flash on top of whatever 2.2 build you have:
http://forum.xda-developers.com/showpost.php?p=6926772&postcount=301

thanks to mortzz
that piece is what I look for over that long thread...

mortzz said:
This is assuming you've already upgraded to FRF83. The stock builds won't flash through a custom recovery.
There's an pre-rooted update.zip floating around that you can just flash on top of whatever 2.2 build you have:
http://forum.xda-developers.com/showpost.php?p=6926772&postcount=301
Click to expand...
Click to collapse
Im on rooted FRF72 build. I have a custom recovery. I mean if its not gonna work for me then thats cool, I'll wait. Just trying to learn myself something . lol

SBERG117 said:
Im on rooted FRF72 build. I have a custom recovery. I mean if its not gonna work for me then thats cool, I'll wait. Just trying to learn myself something . lol
Click to expand...
Click to collapse
It doesn't matter what 2.2 version you're on. You can flash that update.zip and you'll be on rooted FRF83.

mortzz said:
It doesn't matter what 2.2 version you're on. You can flash that update.zip and you'll be on rooted FRF83.
Click to expand...
Click to collapse
Cool thnx for the link. Appreciate the help. Guess im one of the first guinea pigs for it. lol . Lets see what happens...

If you loose the drivers for frf83 ( adb devices doesn't show phone, fastboot devices the same).
Just flash Cyanogen's Froyo rooter and your phone will get recognized.

timal said:
If you loose the drivers for frf83 ( adb devices doesn't show phone, fastboot devices the same).
Just flash Cyanogen's Froyo rooter and your phone will get recognized.
Click to expand...
Click to collapse
Im good. Everything works fine, install went smooth. No hiccups or anything. I installed right over FRF72, no wipe, all settings retained. Couldnt have asked for a easier install. lol

Got myself up to FRF83 from rooted FRF72. I did:
pushed the FRF72 > FRF83 update zip to /sdcard/update.zip
pushed cyanogent's quick root zip to /sdcard/
Reboot into the boot loader
flashed stock recovery
rebooted into recovery
installed the update.zip
rebooted into the boot loader
flashed ra-1.7 recovery
rebooted into recovery
installed cyanogen's quick root
rebooted into FRF83 for the first time

randalla0622 said:
Got myself up to FRF83 from rooted FRF72. I did:
pushed the FRF72 > FRF83 update zip to /sdcard/update.zip
pushed cyanogent's quick root zip to /sdcard/
Reboot into the boot loader
flashed stock recovery
rebooted into recovery
installed the update.zip
rebooted into the boot loader
flashed ra-1.7 recovery
rebooted into recovery
installed cyanogen's quick root
rebooted into FRF83 for the first time
Click to expand...
Click to collapse
I didnt need quick rooter to install, does it make a difference? What will it do that the install itself wont?

This file works for me going from (nonrooted) FRF72 -> FRF83

FRF83 help
Here is my situation:
I was running FRF72 and saw that (at the time) the only way to upgrade to FRF83 was rolling back to FRF50.
I then downloaded the stock rom for the T-mobile N1 and passimg.zip to restore it.
I then tried to upgrade to ERE36B by using the update.zip method. This failed and I would see the message: "E:Can't open/cache/recovery/command" followed by an "E: Error in /sdcard/update.zip" Since this did not work I used the passimg.zip method to upgrade.
I am now on ERE36B but when I try to "update.zip" the FRF50 rom I am still seeing "E:Can't open/cache/recovery/command" and "E: Error in /sdcard/update.zip"
I know for sure I did not name the .zip file wrong (update.zip.zip)
Does anyone have any advice for updating to FRF50 from ERE36B or from ERE36B to FRF83?
Thanks!

DPUVince said:
Here is my situation:
I was running FRF72 and saw that (at the time) the only way to upgrade to FRF83 was rolling back to FRF50.
I then downloaded the stock rom for the T-mobile N1 and passimg.zip to restore it.
I then tried to upgrade to ERE36B by using the update.zip method. This failed and I would see the message: "E:Can't open/cache/recovery/command" followed by an "E: Error in /sdcard/update.zip" Since this did not work I used the passimg.zip method to upgrade.
I am now on ERE36B but when I try to "update.zip" the FRF50 rom I am still seeing "E:Can't open/cache/recovery/command" and "E: Error in /sdcard/update.zip"
I know for sure I did not name the .zip file wrong (update.zip.zip)
Does anyone have any advice for updating to FRF50 from ERE36B or from ERE36B to FRF83?
Thanks!
Click to expand...
Click to collapse
make sure you dont have two or more update files on your card.

[GUIDE] Unlocked bootloader, and new howto on rooting the HTC Evo Shift (2.3.4)

THIS THREAD IS OUTDATED.
PLEASE REFER TO
http://forum.xda-developers.com/showthread.php?t=1357157
WARNING: THIS VOIDS YOUR WARRANTY AND YOU WILL LOSE ALL DATA IN UNLOCKING THE BOOTLOADER
0) Be running stock 2.3.4 latest OTA update from HTC
1) Register at htcdev.com
2) Unlock the bootloader by choosing HTC Evo 3D for Sprint and follow instructions
3) Once you have unlocked bootloader flash clockwork recovery by downloading the following file:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-speedy.img
From the adb folder run "fastboot flash recovery recovery-clockwork-5.0.2.0-speedy.img"
4) adb reboot recovery
5) You will see the beautiful clockwork recovery screen.
6) Goto mounts/storage, mount usb storage
7) Download su from the following location:
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
8) Go back, install zip from sdcard, choose the superuser zip.
9) Reboot, open market, search for super user and install it.
10) Open superuser app go to preferences and choose update su binary.
11) Download terminal emulator and run "su" to test if you have root. $ should turn to #.
You have now rooted the Shift permanently!
Please note.. this is S-ON UNLOCKED BOOTLOADER, NOT ENGINEERING S-OFF BOOTLOADER.
Binary100100 said:
I don't know where to start with all of your questions but I will do my best.
The difference between S-OFF and Unlocked bootloader is that with S-OFF you can flash anything including a radio and supposedly it would give us the ability to update the kernel by recovery. With an unlocked bootloader we cannot update the radio or kernel but can pretty much change everything else. An unlocked bootloader is required to root your device and remove all the bloat that you don't like. You can temp root the device to remove that bloatware however they will re-appear after a reboot. It has been under some debate if in fact using the unlock_code.bin file provided by htcdev is going to void your warranty if your device would require servicing. If it's vital to know that information then call HTC to inquire before unlocking.
Regarding CM9, it is possible but slightly inconvenient since CM9 would almost certainly require a different kernel and since we cannot flash kernels by recovery it would have to be done in a very certain order. Is it currently in the works? To my understanding, yes! Any idea when you can see it as a download here in the forums? Not at this time. Check back daily because things change frequently!
Click to expand...
Click to collapse
Work arounds for unlocked s-on bootloader:
Flashing kernel/custom ROMs:
Pull boot.img from kernel or ROM zip file and run:
adb reboot bootloader
fastboot flash boot boot.img
power off
adb reboot recovery
wipe cache, wipe dalvik, (if flashing a rom format /system and do a wipe data/factory reset)
install kernel/ROM zip from sdcard in CWM
Work around for radio:
unroot, relock, take ota
{
"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"
}
thanks:
koush
nurrwick
jmztaylor
sparksco
otaking71

Have you tried flashing a kernel?
Sent from my PG06100 using Tapatalk

drob311 said:
Have you tried flashing a kernel?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Bout to try dodge kernel now and adding note about s-on now.

I can never trust that HTCdev because of I can't have s-off but that's just me not wanting to deal with workarounds. But anyhow thanks for the information VICODAN greatly appreciated
Sent from my EVO 4G

notsointeresting said:
I can never trust that HTCdev because of I can't have s-off but that's just me not wanting to deal with workarounds. But anyhow thanks for the information VICODAN greatly appreciated
Sent from my EVO 4G
Click to expand...
Click to collapse
Work arounds for s-off:
Flashing kernel:
Pull boot.img from kernel zip file and run:
fastboot flash boot boot.img
power off
adb reboot recovery
wipe cache, wipe dalvik,
install kernel zip from sdcard in CWM
Work around for radio:
unroot, relock, take ota

Stock HTC Sense GB 2.3.4, rooted, radio 1.08.01.0111 running dodge kernel 1.6:

Very nice. I noticed we don't have a ruu for this update yet. Any way to get the system out with adb so some awsome sense devs could get working on a rom for us?

Antutu benchmark:
Dodge kernel 1.6, 1.92 ghz, bfq I/O scheduler, performance governor, patriot class 10 SD card
Quadrant:
Quadrant on CFQ:
Antutu on CFQ:

just got a evo 4g shift yesterday is there anyway to downgrade from 2.3.4 to 2.3.3? i updated by mistake i was originally on 2.3.3. can i follow this guide and unlock my phone then downgrade to 2.2.3?

onsomeg**** said:
just got a evo 4g shift yesterday is there anyway to downgrade from 2.3.4 to 2.3.3? i updated by mistake i was originally on 2.3.3. can i follow this guide and unlock my phone then downgrade to 2.2.3?
Click to expand...
Click to collapse
Well apparently temproot doesn't work but I'm wondering if you used my root process and relocked the bootloader and then flashed PG06IMG.zip 2.2 would it work? Can you please try this?

VICODAN said:
Well apparently temproot doesn't work but I'm wondering if you used my root process and relocked the bootloader and then flashed PG06IMG.zip 2.2 would it work? Can you please try this?
Click to expand...
Click to collapse
would i brick trying and how would i relock the bootloader?

onsomeg**** said:
would i brick trying and how would i relock the bootloader?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1277793
try that. its much easier.

jesuscash said:
http://forum.xda-developers.com/showthread.php?t=1277793
try that. its much easier.
Click to expand...
Click to collapse
thanks, so i don't have to unlock and then run the script or i do have to unlock and run the script?
and once i run it what do i do or pick?
sorry for all the questions my old phone was easier to root and i learned about it, seems like i'm starting over on this phone.

onsomeg**** said:
thanks, so i don't have to unlock and then run the script or i do have to unlock and run the script?
and once i run it what do i do or pick?
sorry for all the questions my old phone was easier to root and i learned about it, seems like i'm starting over on this phone.
Click to expand...
Click to collapse
you run the "fre3atlast" file and follow the cmd instructions.
This temproots you (hopefully, it worked on 2.3.3) and allows you to downgrade to 2.2 which has a permroot.

jesuscash said:
you run the "fre3atlast" file and follow the cmd instructions.
This temproots you (hopefully, it worked on 2.3.3) and allows you to downgrade to 2.2 which has a permroot.
Click to expand...
Click to collapse
I talked to Indirect and fre3atleast isn't any different than fre3vo.

onsomeg**** said:
would i brick trying and how would i relock the bootloader?
Click to expand...
Click to collapse
No you wont brick. Follow the instructions on HTCDEV.com

VICODAN said:
No you wont brick. Follow the instructions on HTCDEV.com
Click to expand...
Click to collapse
i got you and the other user confused as the same person lol okay so i'm bout to unlock using htcdev.com and what other steps do i need to take after that?

onsomeg**** said:
i got you and the other user confused as the same person lol okay so i'm bout to unlock using htcdev.com and what other steps do i need to take after that?
Click to expand...
Click to collapse
Read the OP for all the instructions.
My question is can you relock and flash Scaryghouls PG06IMG.zip and downgrade to 2.2?
You might need to run 2.3 RUU, either way instructions here:
http://forum.xda-developers.com/showthread.php?t=1357157

Ah, now I hope my phone doesn't die or nothing now so I don't get a replacement, and be stuck with 2.3.4, and the htcdev bootloader unlock, reminds me of the Evo3d rooting and flashing kernel, and roms complicated, lol.. But anyways great job finding this.
Sent from my PG06100 using Tapatalk

madplaya1 said:
Ah, now I hope my phone doesn't die or nothing now so I don't get a replacement, and be stuck with 2.3.4, and the htcdev bootloader unlock, reminds me of the Evo3d rooting and flashing kernel, and roms complicated, lol.. But anyways great job finding this.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
You can always relock the bootloader.

Firmware-update JLS36I (Android 4.3.1) Nexus 7 2013 LTE available

This morning I was suprised to find a new update for my Nexus 7 2013 LTE; it brings the Android-version to 4.3.1
No changelog found yet...
{
"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"
}

Any news if this breaks root etc.? WIll flashing this from recovery and flashing supersu.zip afterwards work like last time?

Jacktheskipper said:
Any news if this breaks root etc.? WIll flashing this from recovery and flashing supersu.zip afterwards work like last time?
Click to expand...
Click to collapse
It's broken my root, though that's probably because I used the OTA update rather than flashing in recovery.

I got it too.
in the update file a some changes at:
keymaster / keystore
camera firmware
framework
services and telephony-common
what exactly has changed I do not know.
root + recovery need to be flashed again. but no problems.

if root and recovery need to be flashed again, did you just do the ota update from the sytem or did you sideload the zip and flash it from recovery?

I'm on JLS36C Rooted, with the ElementalX Kernel and Teamwin Recovery (V2.6.3.0) but the "JLS36I from JLS36C" fails to flash for me from the Teamwin Recovery. Any hints on the process to do this update?
Thanks
Nathan

jmone said:
I'm on JLS36C Rooted, with the ElementalX Kernel and Teamwin Recovery (V2.6.3.0) but the "JLS36I from JLS36C" fails to flash for me from the Teamwin Recovery. Any hints on the process to do this update?
Thanks
Nathan
Click to expand...
Click to collapse
You won't be able to until someone puts out a custom ROM for Flo/Deb.

jmone said:
I'm on JLS36C Rooted, with the ElementalX Kernel and Teamwin Recovery (V2.6.3.0) but the "JLS36I from JLS36C" fails to flash for me from the Teamwin Recovery. Any hints on the process to do this update?
Thanks
Nathan
Click to expand...
Click to collapse
First go back to stock kernel, then remove any custom modified files from stock, then try to do the OTA update.

jak3z said:
First go back to stock kernel, then remove any custom modified files from stock, then try to do the OTA update.
Click to expand...
Click to collapse
FYI - used the SkipSoft Android ToolKit to reflash the stock JLS36C then did the OTA update to JLS36I. Bit of a PITA as I now need to reinstall it all but it works!

jmone said:
FYI - used the SkipSoft Android ToolKit to reflash the stock JLS36C then did the OTA update to JLS36I. Bit of a PITA as I now need to reinstall it all but it works!
Click to expand...
Click to collapse
That was totally unnecessary,

I've updated European nexus in Russia without any problem
Have a trwp recovery and supersu binary. Check ota survivalable mode in supersu and just apply update. Trwp updates all stuff. Root works, recovery didn't check for now

jak3z said:
That was totally unnecessary,
Click to expand...
Click to collapse
Thanks.... Next time!

Update :lost trwp recovery and need to flash it again.
Отправлено с моего...

oh man! i just rooted my N7 last night. i just installed a LOT of apps .
i used wugs toolkit so right now i have twrp + root and nothing more. so im stock rooted.
i have never done this before but should i use wugs tool kit again to unroot and relock bootlader THEN ota?
or can i just update while rooted?
thanks!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

keplenk said:
oh man! i just rooted my N7 last night. i just installed a LOT of apps .
i used wugs toolkit so right now i have twrp + root and nothing more. so im stock rooted.
i have never done this before but should i use wugs tool kit again to unroot and relock bootlader THEN ota?
or can i just update while rooted?
thanks!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
You can run the OTA perfectly fine, you will lose Root and Recovery after you OTA, but you can get back those 2 anytime you want. Grab the CF-Auto-Root of chainfire (its on the Android Original Dev forum) and you will get root back.

keplenk said:
or can i just update while rooted?
p
Click to expand...
Click to collapse
you totally can, put the zip-file on your device, got to twrp-recovery and flash the zip file. if you wanna make sure you aren`t running into any trouble download the supersu.zip from here: http://download.chainfire.eu/346/SuperSU/ and flash it after flashing the update.

Jacktheskipper said:
you totally can, put the zip-file on your device, got to twrp-recovery and flash the zip file. if you wanna make sure you aren`t running into any trouble download the supersu.zip from here: http://download.chainfire.eu/346/SuperSU/ and flash it after flashing the update.
Click to expand...
Click to collapse
http://download.chainfire.eu/supersu

1. Go into SuperSu settings to enable survival mode.
2. Download the OTA directly on your Nexus as you would without root and restart to install.
3. It will be installed by TWRP, root will be kept, but TWRP will be gone.
4. Reflash TWRP in Fastboot.

Can't install recovery.

I've rooted my phone, then followed all the steps in the recovery installing guide, but then I get this message and nothing happens:
{
"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"
}
I don't know what to do. I'm trying to install CWM.

MaorSwan said:
I've rooted my phone, then followed all the steps in the recovery installing guide, but then I get this message and nothing happens:
I don't know what to do. I'm trying to install CWM.
Click to expand...
Click to collapse
Use Flashify
It just makes it so easy.

scottdanpor said:
Use Flashify
It just makes it so easy.
Click to expand...
Click to collapse
Downloaded it, now what?

MaorSwan said:
Downloaded it, now what?
Click to expand...
Click to collapse
I'm not sure which guide you're using, I installed TWRP with it. But all you need is your recovery.zip file. Choose Recovery Image, then "Choose a file" and flash your recovery zip file. You can try "Download CWM" but it might not find one for the LS980 (depends which version you have).

scottdanpor said:
I'm not sure which guide you're using, I installed TWRP with it. But all you need is your recovery.zip file. Choose Recovery Image, then "Choose a file" and flash your recovery zip file. You can try "Download CWM" but it might not find one for the LS980 (depends which version you have).
Click to expand...
Click to collapse
Can you give me a link to the newest TWRP so I'd install it?

MaorSwan said:
Can you give me a link to the newest TWRP so I'd install it?
Click to expand...
Click to collapse
Which version of LG G2 do you have?

scottdanpor said:
Which version of LG G2 do you have?
Click to expand...
Click to collapse
D802

MaorSwan said:
D802
Click to expand...
Click to collapse
Ah ok, I had a look through the thread and it looks like your best bet is to use the auto method, and if that doesn't work, you'll have to go manual. You can use flashify to update after you get the recovery on the first time.

I used this http://forum.xda-developers.com/showthread.php?t=2469995 , also on D802
and after that, i updatet via twrp to the latest verion, but i can't find the link right now.

Does flashify automatically install loki to bypass the locked boot leader? Does it work on the VS980?

Try Freegee from playstore. Very easy to use. I have d802 and used that one.
Sent from my LG-D802 using Tapatalk

mrm43 said:
Try Freegee from playstore. Very easy to use. I have d802 and used that one.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
second that , used Freegee to install twrp
just install the app and choose what kind of recovery you want , it will download and install , then press menu and reboot to recovery to test it
couldn't be easier

[email protected] said:
second that , used Freegee to install twrp
just install the app and choose what kind of recovery you want , it will download and install , then press menu and reboot to recovery to test it
couldn't be easier
Click to expand...
Click to collapse
Does this take care of Loki and the locked boot loader as well, or do you have to do that separately?

mattlach said:
Does this take care of Loki and the locked boot loader as well, or do you have to do that separately?
Click to expand...
Click to collapse
not sure to be honest , i just bought the phone 3 days ago
but it helped me install the recovery and i installed a new rom without a problem
and yes there is an option update zip in loki or something like that , do you know what is it ?

[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