How do I un-brick my T337A? - Galaxy Tab 4 Q&A, Help & Troubleshooting

I have a SM-T337A that I rooted with Kingroot, after which I installed Super-SU, then rebooted it and was soft-bricked. If anyone can help me, it would be much appreciated.

Mlight123 said:
I have a SM-T337A that I rooted with Kingroot, after which I installed Super-SU, then rebooted it and was soft-bricked. If anyone can help me, it would be much appreciated.
Click to expand...
Click to collapse
Sadly, I just joined your club!! lol I wanted to comment here incase anyone else can help us or if I manage to figure it out myself I can find this thread easily. I got it rooted with newest version of Kingroot too, then I used Supersume to update to SuperSU and everything was working fine. When I tried rebooting, same thing as you I presume, I get kernel is not se enforcing I think it said and got the dreaded Unauthorized software was found running on this device, please take to att for service.

Sorry I can't help with your current problem. But, did you ever try to reboot with the kingroot SU?
This is definitely a slippery slope with no installation image.

moonbutt74 said:
Reboot to recovery, connect to pc and via adb shell , do a manual unroot.
that usually consists of
adb shell mount /system
adb shell rm /system/xbin/su
adb shell rm -fr /system/bin/.ext <----.ext is a directory
adb shell ls -al /system/bin/app_*
lrwxrwxrwx root root 2014-06-30 09:42 app_process -> /system/xbin/daemonsu
lrwxrwxrwx root root 2014-06-30 09:42 app_process32 -> /system/xbin/daemonsu <---remove this symlink
-rwxr-xr-x root shell 13588 2008-08-01 08:00 app_process32_original <---- rename to app_process32
-rwxr-xr-x root shell 73508 2008-08-01 08:00 app_process32_xposed <------ not there if you don't have xposed
-rwxr-xr-x root shell 13588 2008-08-01 08:00 app_process_init
Then search /data/app /system/app and /system/priv-app and remove the offending apk's base directory.
m
Click to expand...
Click to collapse
This is an answer to someone who had done the same thing as us, his question is on the same page.
Can anybody give more detailed instructions to this? And will it even help our situation?

Mlight123 said:
This is an answer to someone who had done the same thing as us, his question is on the same page.
Can anybody give more detailed instructions to this? And will it even help our situation?
Click to expand...
Click to collapse
Yes, the thread you got that info from I am familiar with. The Lp fix boot tar in OP of that thread will fix our issue only if you only used Kingroot then rebooted. To fix and be able to boot phone again, simply flash the lp fix boot tar. However, I also used Supersume Pro to swap kingroot for supersu and that is why even after using the lp fix boot tar I am now past the "unauthorized software detected, please power off and take to att store", message, but stuck now at the att logo on boot. I am thinking of taking it to best buy or even att and hope someone can help reflash the full 5.1.1 firmware. I do not think the above adb steps will help for me, to mount system don't we need root? after I flashed the lp fix boot.img, (It is just the stock 5.1.1 boot.img) that removed whatever Kingroot did to get me rooted. Now I am stuck without root on a tablet I cant boot. I can get into recovery but I can not get adb to see the device unless I choose adb sideload, then all I can do with that is use it to push files to the phone for recovery to flash if it is signed properly of course.

Shocked...
So... Despite what Klown80 said.. I flashed boot(LP_fix).tar from "Rooted NK2 AT&T t337a w/ Tutorial" and it booted right up but I noticed some thing the first time it booted, the unlocked custom logo was gone, and so it went through the normal boot, but it didn't get stuck at the AT&T logo, it booted to the lockscreen. So I preceded to uninstall everything root related, so that if it does get bootlooped I can take it to the store and hopefully get it restored and they have no proof of what I was trying to do, via going into SuperSU and uninstalling, then I deleted Kingroot, the SuperSU app, etc.. Then, now here is where I am really confused, I rebooted and the first thing I see is that unlocked lock logo with "Custom" under it, but at the top of my screen is says nothing about my kernal not being seandroid enforced or w/e, and it booted like normal to the lockscreen.
Sorry if that is at all confusing but I thought I'd just share my findings.. considering I have my tablet back!
Edit: I can, and will record this rebooting if anyone is curious to see what I'm talking about if they didn't understand the above statements.

Mlight123 said:
So... Despite what Klown80 said.. I flashed boot(LP_fix).tar from "Rooted NK2 AT&T t337a w/ Tutorial" and it booted right up but I noticed some thing the first time it booted, the unlocked custom logo was gone, and so it went through the normal boot, but it didn't get stuck at the AT&T logo, it booted to the lockscreen. So I preceded to uninstall everything root related, so that if it does get bootlooped I can take it to the store and hopefully get it restored and they have no proof of what I was trying to do, via going into SuperSU and uninstalling, then I deleted Kingroot, the SuperSU app, etc.. Then, now here is where I am really confused, I rebooted and the first thing I see is that unlocked lock logo with "Custom" under it, but at the top of my screen is says nothing about my kernal not being seandroid enforced or w/e, and it booted like normal to the lockscreen.
Sorry if that is at all confusing but I thought I'd just share my findings.. considering I have my tablet back!
Edit: I can, and will record this rebooting if anyone is curious to see what I'm talking about if they didn't understand the above statements.
Click to expand...
Click to collapse
Glad to hear it worked for you mate! Sadly, it didnt for me. I do have good news of my own though, I was able to have my wife take it by the local Best buy store and after they tried the normal factory reset and such, he must have had an Odin flashable 5.1.1 file or something because the tab is back to working order.
That is how I knew I was in trouble after I rebooted the first time after installing Kingroot and Supersume Pro. I also got the red lettered "Kernel is not SEandroid enforcing in top left corner too, but the next thing I saw was the " Unauthorized software detected, please power off and take to ATT ". I don't think I ever even made it to the samsung screen if my memory is correct (It might not be! lol) It sounds like either kingroot or SuperSU left something behind after install maybe? If you go to Settings > About tablet > Status and scroll all the way to bottom, the last entry says custom as well correct? The unlocked padlock on boot just means Syscope is detecting something not official installed somewhere it normally shouldn't be.

I just kept to odin folder and boot(LP_fix).tar on my pc because despite getting stuck in a boot loop you lose root after you fix it so it's kind of like a tethered root lol

Guys Iam having this same problem but I don't speak computer lingo can another walk be though step by step so I can fix my tablet?

Klown80 said:
Yes, the thread you got that info from I am familiar with. The Lp fix boot tar in OP of that thread will fix our issue only if you only used Kingroot then rebooted. To fix and be able to boot phone again, simply flash the lp fix boot tar. However, I also used Supersume Pro to swap kingroot for supersu and that is why even after using the lp fix boot tar I am now past the "unauthorized software detected, please power off and take to att store", message, but stuck now at the att logo on boot. I am thinking of taking it to best buy or even att and hope someone can help reflash the full 5.1.1 firmware. I do not think the above adb steps will help for me, to mount system don't we need root? after I flashed the lp fix boot.img, (It is just the stock 5.1.1 boot.img) that removed whatever Kingroot did to get me rooted. Now I am stuck without root on a tablet I cant boot. I can get into recovery but I can not get adb to see the device unless I choose adb sideload, then all I can do with that is use it to push files to the phone for recovery to flash if it is signed properly of course.
Click to expand...
Click to collapse
I had this same problem, I just ended up giving up, exchanging tablet for a new one. :c

Klown80 said:
Yes, the thread you got that info from I am familiar with. The Lp fix boot tar in OP of that thread will fix our issue only if you only used Kingroot then rebooted. To fix and be able to boot phone again, simply flash the lp fix boot tar. However, I also used Supersume Pro to swap kingroot for supersu and that is why even after using the lp fix boot tar I am now past the "unauthorized software detected, please power off and take to att store", message, but stuck now at the att logo on boot. I am thinking of taking it to best buy or even att and hope someone can help reflash the full 5.1.1 firmware. I do not think the above adb steps will help for me, to mount system don't we need root? after I flashed the lp fix boot.img, (It is just the stock 5.1.1 boot.img) that removed whatever Kingroot did to get me rooted. Now I am stuck without root on a tablet I cant boot. I can get into recovery but I can not get adb to see the device unless I choose adb sideload, then all I can do with that is use it to push files to the phone for recovery to flash if it is signed properly of course.
Click to expand...
Click to collapse
That's exactly the problem i had. But when i took it to best buy, they said that, their software cannot read my tablet, because of "an abnormal software has been found on this device" its probably because my tablet is custom...Any Fixes?

Can't you guys boot to download mode and flash the stock files via odin?

wp4jot said:
Can't you guys boot to download mode and flash the stock files via odin?
Click to expand...
Click to collapse
The problem is the only stock Odin file available is KitKat, and since they're on official Samsung 5.1.1, they cannot downgrade, even using the official Odin file (attempting to results in a bootloop if I've read correctly). For this reason I really want to make a 5.1.1 Odin file for this device, but I won't be able to until someone is able to make a system dump.

How about this?
http://forum.xda-developers.com/showpost.php?p=63320598&postcount=459
thisisapoorusernamechoice said:
The problem is the only stock Odin file available is KitKat, and since they're on official Samsung 5.1.1, they cannot downgrade, even using the official Odin file (attempting to results in a bootloop if I've read correctly). For this reason I really want to make a 5.1.1 Odin file for this device, but I won't be able to until someone is able to make a system dump.
Click to expand...
Click to collapse

wp4jot said:
How about this?
http://forum.xda-developers.com/showpost.php?p=65481346&postcount=606
Click to expand...
Click to collapse
Definitely worth trying but something tells me an OTA file won't be able to install on a modified system

Definitely worth trying. It's a bricked phone and there's nothing to loose.
thisisapoorusernamechoice said:
Definitely worth trying but something tells me an OTA file won't be able to install on a modified system
Click to expand...
Click to collapse

wp4jot said:
Definitely worth trying. It's a bricked phone and there's nothing to loose.
Click to expand...
Click to collapse
Agreed. Also for those following along at home, wp4jot linked to the 10.1 AT&T OTA file, for the 8.0 AT&T OTA file, please see this post:
http://forum.xda-developers.com/showpost.php?p=63320598&postcount=459

Sorry about that. Read fast and didn't notice the 537. I will edit my post with the right link. Thanks!
thisisapoorusernamechoice said:
Agreed. Also for those following along at home, wp4jot linked to the 10.1 AT&T OTA file, for the 8.0 AT&T OTA file, please see this post:
http://forum.xda-developers.com/showpost.php?p=63320598&postcount=459
Click to expand...
Click to collapse

wp4jot said:
Sorry about that. Read fast and didn't notice the 537. I will edit my post with the right link. Thanks!
Click to expand...
Click to collapse
I figured, no worries, just didn't want to confuse anyone else :good:

It has been reported that downgrading the system to kit kat will cause a bootloop but you can then apply the update.zip file for 5.1.1 on a extSD and run it in recovery and it should boot.
---------- Post added at 04:18 AM ---------- Previous post was at 04:14 AM ----------
thisisapoorusernamechoice said:
The problem is the only stock Odin file available is KitKat, and since they're on official Samsung 5.1.1, they cannot downgrade, even using the official Odin file (attempting to results in a bootloop if I've read correctly). For this reason I really want to make a 5.1.1 Odin file for this device, but I won't be able to until someone is able to make a system dump.
Click to expand...
Click to collapse
It has been reported that downgrading the system to kit kat will cause a bootloop but you can then apply the update.zip file for 5.1.1 on a extSD and run it in recovery and it should boot.

Related

Lolipop OTA capture

Update 2 after some fiddling I found that after flashing Pico Capps hdxposed is needed to make the play store work on this build http://forum.xda-developers.com/showthread.php?t=2618158
Update 1 New lolipop ota, this appears to be based on lolipop 5.1 and as such requires xposed unofficial by romracer if you want to use xposed Xposed for 5.0 would not flash for me. Same upgrade steps as before just this one instead of the bottom one and change your xposed package
https://mega.nz/#!i5RRCKQZ!NC291mcIo-2yzr23j8Vg_mLZ11ECql4lL_xen6xwXuM
update-kindle-devpreview_ariel-20.5.2.2_user_522041550.bin
siegesoldier said:
this is the developer preview, sorry if the title is a little misleading. Thanks to http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
Use at your own risk.
https://www.dropbox.com/s/38i2lqq5p...review_ariel-20.5.2.0_user_520033250.bin?dl=0
Hopefully someone can figure out how to make this thing boot when flashed from TWRP
Click to expand...
Click to collapse
Important update, the instructions below are not to be followed !!! They are historical ...
Same drill as in here :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
Replace the original META-INF/com/google/android/updater-script with the one from the zip below. Remove "images" directory. This will ensure that your bootloader stays 4.5.3 and unlocked. When TWRP asks to add root, say yes.
If for some reason you lose TWRP (recovery), reflash it from within 5.0. Since you have root, no biggie. I'll play with this a bit too, but later.
I tried yours and tried my attempt. I'm getting a bootloop with both, let me know if you have any luck. TWRP protects itself from getting replaced.
siegesoldier said:
I tried yours and tried my attempt. I'm getting a bootloop with both, let me know if you have any luck. TWRP protects itself from getting replaced.
Click to expand...
Click to collapse
OK. Does it flash successfully? Does it ask to install root? If it does and bootloops, the bootloader probably needs to be updated too. You could try to flash the new bootloader (just grab my uboot_4.5.3.zip, replace both files in /images, and re-zip).
The trick is that you install Lollipop, install root, and install the new bootloader separately. It should boot OK and you should have root in 5, but you'll lose TWRP (it won't be able to boot since the bootloader will probably be signed). To get TWRP back you'll need to downgrade to 4.5.3
bibikalka said:
OK. Does it flash successfully? Does it ask to install root? If it does and bootloops, the bootloader probably needs to be updated too. You could try to flash the new bootloader (just grab my uboot_4.5.3.zip, replace both files in /images, and re-zip
Click to expand...
Click to collapse
Yes it flashes successfully and asks to install root. Looks like I'll be trying that tonight, thanks!
Edit we have a winner.
Flashed lolipop without bootloader
Installed su
Reboot to recovery
Installed superuser flashable zip
Flashed uboot file with lolipop images folder
Fire has booted and is currently doing the very long lolipop upgrading screen
Currently booting to home screen but then back to the fire screen, etc. Probably my fault for not clearing the cache or a factory reset. I'm not at a computer at the moment but any ideas on how to fix this?
siegesoldier said:
Currently booting to home screen but then back to the fire screen, etc. Probably my fault for not clearing the cache or a factory reset. I'm not at a computer at the moment but any ideas on how to fix this?
Click to expand...
Click to collapse
Turn it off with a long press of "power" button. Then press "power" and "vol+" together, this should get you into the Amazon recovery. It should offer you a factory reset option. Your system should be pretty much stock Lollipop, so I don't see why it should be doing what it does ...
Actually, does it now have stock Amazon recovery or TWRP ? My suspicion is that it should have flashed recovery during the first upgrade cycle.
Upon reflection, there is a chance you have a bit of a soft brick. If the factory reset option does not come up, it may end up a little tricky to fix things. I wonder if you'd be able to connect via adb before it reboots.
bibikalka said:
Turn it off with a long press of "power" button. Then press "power" and "vol+" together, this should get you into the Amazon recovery. It should offer you a factory reset option. Your system should be pretty much stock Lollipop, so I don't see why it should be doing what it does ...
Actually, does it now have stock Amazon recovery or TWRP ? My suspicion is that it should have flashed recovery during the first upgrade cycle.
Click to expand...
Click to collapse
it appears to have TWRP but it will not boot to it with holding keys. I can get the device to appear in ADB but I can not authorize it. Appears to not actually be rebooting. just crashing to fire screen for some reason then back to launcher etc. I may be able to try again at home with a usb port that it remembers.
siegesoldier said:
it appears to have TWRP but it will not boot to it with holding keys. I can get the device to appear in ADB but I can not authorize it. Appears to not actually be rebooting. just crashing to fire screen for some reason then back to launcher etc. I may be able to try again at home with a usb port that it remembers.
Click to expand...
Click to collapse
I wonder if Lollipop does not update recovery at all, and just uses the one from 4.5.4 You do have your old settings around, so there is a chance that prior USB authorization will help. It looks like one should have updated to stock recovery while in TWRP as the last step, after updating the bootloader, ir order to be able to do a factory reset in a situation like this.
If it comes to worst, Amazon reps never ask "did you brick the device yourself?". They only ask if you can get to the home screen, and if not, proceed with the replacement
I think TWRP just blocked it from updating. Oh well, if the ports at home don't work, I was eventually going to get it replaced anyway since I had a blue discoloration on my screen. Glad to be of some moderate use to the community instead of a leecher for once. May the next person have some luck!
bibikalka said:
I wonder if Lollipop does not update recovery at all, and just uses the one from 4.5.4 You do have your old settings around, so there is a chance that prior USB authorization will help. It looks like one should have updated to stock recovery while in TWRP as the last step, after updating the bootloader, ir order to be able to do a factory reset in a situation like this.
If it comes to worst, Amazon reps never ask "did you brick the device yourself?". They only ask if you can get to the home screen, and if not, proceed with the replacement
Click to expand...
Click to collapse
ok I was able to get adb on a previously used port. I do not have root though. What are my options? What recovery should I flash? I also have a replacement kindle coming tomorrow so this is mostly for science now. I am also able to get into bootloader.
erased cache via fastboot. stuck on fire instead of boot to homescreen
siegesoldier said:
ok I was able to get adb on a previously used port. I do not have root though. What are my options? What recovery should I flash? I also have a replacement kindle coming tomorrow so this is mostly for science now. I am also able to get into bootloader.
erased cache via fastboot. stuck on fire instead of boot to homescreen
Click to expand...
Click to collapse
So no adb anymore? I am not sure how SuperSu comes in, there gotta be su program somewhere.
Anyway, the great news is that JMZ is going to be back soon. That's going to boost our tinkering capabilities by 300%
siegesoldier said:
Yes it flashes successfully and asks to install root. Looks like I'll be trying that tonight, thanks!
Edit we have a winner.
Flashed lolipop without bootloader
Installed su
Reboot to recovery
Installed superuser flashable zip
Flashed uboot file with lolipop images folder
Fire has booted and is currently doing the very long lolipop upgrading screen
Click to expand...
Click to collapse
And then soft brick ...
So I wonder now if one could do this :
install 5.2.0 via TWRP
install supersu.zip
and here it gets very tricky:
without any reboots, replace TEE1, UBOOT, and recovery to stock versions 5.2.0
The hope is to end up in 5.2.0 with root. If things fail, then booting into 5.2.0 recovery (which must be installed!!!) should give one an option to do 1) factory reset 2) downgrade to stock 4.5.3 as in here : http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
The problem is that I don't see a way to boot into 5.2.0, and then flash GAPPS after (since your TWRP was replaced by stock recovery earlier). So one would have to install GAPPS those via something like Titanium backup if root does work.
Please, if you already had 1 warranty replacement, don't do this. And, if you replace TEE1 and UBOOT (5.2.0) but not recovery, then you won't have any way to recover.
bibikalka said:
And then soft brick ...
So I wonder now if one could do this :
install 5.2.0 via TWRP
install supersu.zip
and here it gets very tricky:
without any reboots, replace TEE1, UBOOT, and recovery to stock versions 5.2.0
The hope is to end up in 5.2.0 with root. If things fail, then booting into 5.2.0 recovery (which must be installed!!!) should give one an option to do 1) factory reset 2) downgrade to stock 4.5.3 as in here : http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
The problem is that I don't see a way to boot into 5.2.0, and then flash GAPPS after (since your TWRP was replaced by stock recovery earlier). So one would have to install GAPPS those via something like Titanium backup if root does work.
Please, if you already had 1 warranty replacement, don't do this. And, if you replace TEE1 and UBOOT (5.2.0) but not recovery, then you won't have any way to recover.
Click to expand...
Click to collapse
Yes I've used my warranty replacement so I'll be waiting until the official release before breaking my kindle again . How do you stop TWRP from preventing the recovery from being flashed? I noticed it gave a message about protecting itself.
siegesoldier said:
Yes I've used my warranty replacement so I'll be waiting until the official release before breaking my kindle again . How do you stop TWRP from preventing the recovery from being flashed? I noticed it gave a message about protecting itself.
Click to expand...
Click to collapse
Interesting, at what stage of the update did this happen? 5.2.0 file system is slightly packaged and is pain in the neck to peak into, but in 4.5.3 the recovery is updated via a pretty specific command install-recovery.sh , and I cannot find any references to this in updater-script. So I wonder at what stage will this be run. Also, there is no direct image for recovery, one has to reconstruct it as the commands below do. A bit messy ...
install-recovery.sh
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:5888256:6d9d1bbc4172c107db3228ed8d9f97111219c617; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:5370112:c2c686ada1b194050a3c8f05e2102345df48e9ce EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery 6d9d1bbc4172c107db3228ed8d9f97111219c617 5888256 c2c686ada1b194050a3c8f05e2102345df48e9ce:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Edit: It kind of looks like /system/etc/install-recovery.sh will be run at every boot. So I wonder if TWRP just renames it to something and calls it "protection". I guess one can double check the file system after 5.2.0 update while still in TWRP, and see what happened to recovery files.
Help
If someone can please help me. I downloaded the update to 5.0, unzipped it, replaced the updater script, but when I zip it back and try to flash it says that it failed. Am I doing something wrong.
Also, if someone has the zip file already and wouldn't mind uploading and sharing it, I would appreciate it.
Thanks for all the help.
hawkazn said:
If someone can please help me. I downloaded the update to 5.0, unzipped it, replaced the updater script, but when I zip it back and try to flash it says that it failed. Am I doing something wrong.
Also, if someone has the zip file already and wouldn't mind uploading and sharing it, I would appreciate it.
Thanks for all the help.
Click to expand...
Click to collapse
Last time this procedure ended up with a soft brick. Are you sure you want to pursue this route?
Help
Maybe not, but if someone can help me with something else. The developer preview for the camera is extremely sharp and the 4.5.4 really isn't. Is there a way to make it crystal clear and sharp?
hawkazn said:
Maybe not, but if someone can help me with something else. The developer preview for the camera is extremely sharp and the 4.5.4 really isn't. Is there a way to make it crystal clear and sharp?
Click to expand...
Click to collapse
Meaning exactly what? It'd be possible to replace the camera app, one for another. Do you think some other system stuff is involved such as some sort of settings?
You'll have to find a way to mount the big 5.2.0 system update file as a filesystem, then you could read what's in there, including the camera stuff.
TWRP help
So I downloaded the zip file for 5.0 and it flashed and asked to install super user. I had to download the apk for supersu and then update it.
But the problem is that I lost my twrp. I push the volume + and power and it just reboots. I also lost my play store. Any thoughts how to get twrp back on?

moto x pure 6.0 mm ( root )

Tried everything flashing every supersu via twrp and just gets stuck at the moto logo. Tried systemless root and did the same thing. So thinking it was my kernel and flashed elementalx moto kernel ( frankenclark ) then tried to flash supersu once again with the same fail and noticed with that kernel I lost my wifi connection but ran it anyways but failed. After much forum browsing and that supersu just isn't for the MXPE I even went as far as kingroot to achieve root then slap supersu to keep root like I did with my kindle fire. I'm pretty lost for words here. I'm previously running resurection remix and works flawless but I do really like the original setup. Ps tried the stock rooted roms and they was a lil off and kept trying to ota update but failed because my bootloader is unlocked so I had to uninstall it. Just looking to root the original rom so I can keep all the moto apps. Looking forward to hearing the ideas. Thanks in advance.
Wow... So I assume you flashed back to pure stock?
Rooting is not difficult, there is only 2 ways to do it, either flash SuperSU 2.62-3 beta or the latest stable version with the "echo" command for systemless installations. Look at this thread (note the pictures in the OP are of my XT1575, I fudged a little) but the method is identical. If it doesn't work, no offense, but your not doing something right.
I have both pure stock in a restore and resurection remix in a restore which is pretty much my daily because the active display drives me nuts. And supersu 2.6.2 I haven't tried yet but the SR supersu I've flashed via twrp with the stock kernel and ( frankenclark ) kernel and it responded the same stuck at moto. I've flashed it via windroid toolkit also it shows it's installing without any failure but on boot up she says no way. And I've updated the toolkit to it's newest version and still ends up stuck at moto. I'm sure I'll figure it out and get it. And no offense on doing something wrong it's been known to happen. Some lg double tap to wake the screen would be nice over the active display.
fastjohnson said:
I have both pure stock in a restore and resurection remix in a restore which is pretty much my daily because the active display drives me nuts. And supersu 2.6.2 I haven't tried yet but the SR supersu I've flashed via twrp with the stock kernel and ( frankenclark ) kernel and it responded the same stuck at moto. I've flashed it via windroid toolkit also it shows it's installing without any failure but on boot up she says no way. And I've updated the toolkit to it's newest version and still ends up stuck at moto. I'm sure I'll figure it out and get it. And no offense on doing something wrong it's been known to happen. Some lg double tap to wake the screen would be nice over the active display.
Click to expand...
Click to collapse
It sounds like the install script for SuperSU is not doing a systemless install...
So you are flashing stock, booting at least once (this is required), the open TWRP and allow changes to system (In mounts make sure Mount System Read-Only is NOT checked), go to Advanced - Terminal and enter "echo SYSTEMLESS=true>>/data/.supersu" and press enter, then go to Install and select the SuperSU zip file and install it. It should clearly say it is doing a system-less install, patching boot image, etc. as shown in the first post of the link I shared a couple posts previous.
OK I tried this info word for word and tried multiple times and its still gets stuck on the moto logo, I don't get it.
I don't know... it's a puzzler.
2.62-3 and stop using toolkits.
lafester said:
2.62-3 and stop using toolkits.
Click to expand...
Click to collapse
I'm using twrp to obtain the root like specified. But I'll try adb commands and see if the version you mentioned will do it. I appreciate the help.
fastjohnson said:
I'm using twrp to obtain the root like specified. But I'll try adb commands and see if the version you mentioned will do it. I appreciate the help.
Click to expand...
Click to collapse
Well that worked perfectly the first try I used those terminal commands with that version SuperSU it rooted and booted right up like normal and started asking the SuperSU adb shell permission banners. Perfect guys maybe this thread will help some other poor soul to get root. Awesome advice that works. Thank you.
fastjohnson said:
Well that worked perfectly the first try I used those terminal commands with that version SuperSU it rooted and booted right up like normal and started asking the SuperSU adb shell permission banners. Perfect guys maybe this thread will help some other poor soul to get root. Awesome advice that works. Thank you.
Click to expand...
Click to collapse
Yeah, glad it's working... Did you read through the link I posted earlier? The 2.62-3 method was clearly described in the second post under Alternative Methods.
acejavelin said:
Yeah, glad it's working... Did you read through the link I posted earlier? The 2.62-3 method was clearly described in the second post under Alternative Methods.
Click to expand...
Click to collapse
No actually I didn't see it, lol probably would have helped made me not look dumb. Buy who am I kidding you guys love flexing you rooting muscles..
Deleted.

Replace Kingo Superuser with SuperSU.

EDIT: First of all, thanks for the responses. Second of all, I messed up. I ran a script that I found online called root.sh (I can't link anything until I get to 10 posts). I used that and it didn't work and unrooted me. I tried rebooting my phone(worst idea every) and now it's in a bootloop. I don't think I have root access and I've tried a factory reset. I didn't get any custom recovery and my phone is stuck in a bootloop. I have no idea how to get out of this. Any help is 100% appreciated.
I'm sorry if this is the wrong section but, I couldn't find a section for the M919V. So I recently rooted my Galaxy S4 SGH-M919V running lollipop 5.0.1 using the PC version of Kingoroot. I've been looking for a way to replace Kingo Superuser with SuperSu. I can only seem to find anything about replacing Kinguser/Kingroot (not Kingo Superuser). I would keep Kingo Superuser but, after a reboot it doesn't allow any apps to use root access even though it says it is. I have to keep uninstalling and reinstalling Kingo Superuser and waiting then it finally fixes by it's self (currently it's broken) . SuperSu-Me says I don't have Kingroot (once again, not Kingoroot). I've also tried a script but, once again, it didn't work. I know next to nothing about the inner workings of android phones so please keep any answers simple please.
Flash custom recovery.
Flash SuperSU.
Can't get any simpler.
The sgh-m919v is basically the same phone as the T-mobile S4. The sgh-m919v was issued by Canadian varriers that run an AWS network: https://www.sammobile.com/firmwares/database/SGH-M919V/
The t-mobile s4 forum is here: http://forum.xda-developers.com/galaxy-s4-tmobile
Here's what I would do: flash a stock ROM via Odin to bring the phone back to a stock state and then root using cfautoroot if you want stock recovery or flash TWRP and flash supersu from TWRP.
First of all, thanks for the responses. Second of all, I messed up. I ran a script that I found online called root.sh (I can't link anything until I get to 10 posts). I used that and it didn't work and unrooted me. I tried rebooting my phone(worst idea every) and now it's in a bootloop. I don't think I have root access and I've tried a factory reset. I didn't get any custom recovery and my phone is stuck in a bootloop. I have no idea how to get out of this. Any help is 100% appreciated.
Flash the stock ROM.
Pwnycorn said:
Flash the stock ROM.
Click to expand...
Click to collapse
Could you link me to a good tutorial to do this?
Pwnycorn said:
Flash the stock ROM.
Click to expand...
Click to collapse
Hey man, I got the flash to work. Thank you so much!
ben3759 said:
Hey man, I got the flash to work. Thank you so much!
Click to expand...
Click to collapse
Now, if you still want SuperSU, flash CF-Auto-Root.

New update to fix voLTE 911 bug...

So this morning I got an update to fix the voLTE bug. I'm unlocked with twrp installed and rooted. Just for the sake of experimenting I tried installing it. Well that didn't work. Just gets stuck in twrp recovery and you have to power the phone off completely to get it to boot. I guess my question (even though it's a little early) is there a way to install the update without reverting back to stock?
EDIT: Link to the zip
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
I don't believe so.
In the past you either had to go back to stock or wait on someone to create a compatible update for rooted devices.
Can you post link to zip?
If you are rooted, you can find the zip in cache folder in recovery.
Can you add what variant and build you are using before the update? Also the build afterwards?
KapilFaujdar said:
Can you post link to zip?
If you are rooted, you can find the zip in cache folder in recovery.
Click to expand...
Click to collapse
I got the update, but all I see on my magisk rooted G5+ in /cache/recovery are log files and the fstab files. Anywhere else to look?
gghose said:
I got the update, but all I see on my magisk rooted G5+ in /cache/recovery are log files and the fstab files. Anywhere else to look?
Click to expand...
Click to collapse
Yeah I can't find anything in that folder either.
I received the update and applied it. I am not rooted.
I have the XT1687 model.
My current build number is NPN25.137-35
My device BL unlocked, TWRP installed and rooted with magisck.
I'm getting the update notification and splash screens several times daily.
Anyone rooted try installing the update with Flashfire app?
bvsbutthd101 said:
So this morning I got an update to fix the voLTE bug. I'm unlocked with twrp installed and rooted. Just for the sake of experimenting I tried installing it. Well that didn't work. Just gets stuck in twrp recovery and you have to power the phone off completely to get it to boot. I guess my question (even though it's a little early) is there a way to install the update without reverting back to stock?
Click to expand...
Click to collapse
If you have systemless supersu, you should just be able to apply the update after reverting to stock recovery.
So I found where the zip downloads. I wonder what flashing it in twrp would do?
EDIT: Here's the link to the zip and I've put it in the OP.
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
glight0 said:
My device BL unlocked, TWRP installed and rooted with magisck.
I'm getting the update notification and splash screens several times daily.
Anyone rooted try installing the update with Flashfire app?
Click to expand...
Click to collapse
OK, so I tried flashing recovery.img from stock firmware build 33. But the OTA update will not install, instead I get an error after downloading and rebooting (red triangle at recovery mode).
So I tried fully reverting to stock firmware but I decided to skip over erasing userdata. Afterward the OTA downloaded and installed successfully. Keeping userdata does not seem to have caused an issue.
My problem now though is how to get root back without having to wipe userdata after re-flashing TWRP.
Or is this not possible and if I want to root I must first wipe userdata so that TWRP can read internal memory?
bvsbutthd101 said:
So I found where the zip downloads. I wonder what flashing it in twrp would do?
EDIT: Here's the link to the zip and I've put it in the OP.
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
Click to expand...
Click to collapse
Just tried flashing it with TWRP and no luck:
Verifying current system....
E3002: Package expects build thumbprint of 7.0/NPN25.137-35/37:user/release-keys or 7.0/NPN25.137-33/35:user/release-keys; this device has .
Updated process ended with ERROR: 7
which doesn't make much sense since I rooted the stock ROM (Build number reads NPN25.137-33).
If your using a custom recovery flash the stock recovery, then go to the stock recovery and using your computer flash using adb sideboard command. I assume you already know how to do this. Hope that helps.
gghose said:
Just tried flashing it with TWRP and no luck:
Verifying current system....
E3002: Package expects build thumbprint of 7.0/NPN25.137-35/37:user/release-keys or 7.0/NPN25.137-33/35:user/release-keys; this device has .
Updated process ended with ERROR: 7
which doesn't make much sense since I rooted the stock ROM (Build number reads NPN25.137-33).
Click to expand...
Click to collapse
I'm stuck in the same boat... no idea how to flash the stock recovery and sideboard, what that even means, or if that would break root. I just followed the step-by-step "how to root" video when I first got the phone
There's a workaround to disable the "advanced LTE" or whatever it was called, so I did that. But in the meantime until a more "user friendly" means of updating is available, is there a way I can get rid of this nag screen? Way back on an earlier device (Samsung Charge?) I remember manually editing a "build.prop" file or something to match the latest version so I wouldn't keep getting the software update nag. Is there something that will do the same here, or is there a system app I can freeze in TiB?
My best guess is freezing "Moto Actions 03.022.1.4-N" because it's showing "(updated)" on the side.
rellim113 said:
I'm stuck in the same boat... no idea how to flash the stock recovery and sideboard, what that even means, or if that would break root. I just followed the step-by-step "how to root" video when I first got the phone .
Click to expand...
Click to collapse
What he means is you need to download the stock rom, unzip it, then boot phone to bootloader mode and connect to PC. Then flash the recovery.IMG from the stock rom folder with command prompt:
Fastboot flash recovery recovery.img
Then you can on the phone tell it to boot to recovery mode. This will be a screen with Android on his back and the words NO Command on the bottom. Then plug to PC and use adb command to sideload the update zip like this:
adb sideload [nameofupdatefile].Zip
glight0 said:
What he means is you need to download the stock rom, unzip it, then boot phone to bootloader mode and connect to PC. Then flash the recovery.IMG from the stock rom folder with command prompt:
Fastboot flash recovery recovery.img
Then you can on the phone tell it to boot to recovery mode. This will be a screen with Android on his back and the words NO Command on the bottom. Then plug to PC and use adb command to sideload the update zip like this:
adb sideload [nameofupdatefile].Zip
Click to expand...
Click to collapse
Strange, reflashed the stock recovery and adb can't see it (adb devices returns nothing). And when trying to install it via the normal OTA way, the stock recovery tries to install but ends with an error.
That's what happened to me when I tried reverting to stock recovery and then trying to install update from phone Settings app.
I ended up having to revert to stock rom to get ota to apply with settings app. But now I am trying to root again but after installing TWRP data is encrypted again. So looks like I will have to wipe data before re-rooting.

Strange root / Recovery issue. Please help

Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
The axon7 has had its EDL programmer released and a leaked ZTE signed TWRP since shortly after the device went on sale. Anything is possible.
I would recommend nuking it... wipe the phone data and then install the latest full official firmware over whatever you have now. Then you can go back and start modding.
Jay_Nz said:
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
Click to expand...
Click to collapse
Thanks for replying. Just a thought is it possible to flash twrp on top of the existing set up..? And keep the root as it is.?
Should be, but it's not safe since you do not know the current root method.
Odds are fairly high that you have malware on the device. Be safe, nuke it.
Jay_Nz said:
Thanks for replying. Just a thought is it possible to flash twrp on top of the existing set up..? And keep the root as it is.?
Click to expand...
Click to collapse
Ok thanks for replying. Anti-virus shows device is clean. I'll do a clean one then as recommended . Flash official firmware first then flash twrp and probably will go for magisk root. Wish me luck as power button is mushed in and have to poke it real hard. I don't even know if bootloader is unlocked or not.. Haha
tdm said:
The axon7 has had its EDL programmer released and a leaked ZTE signed TWRP since shortly after the device went on sale. Anything is possible.
Click to expand...
Click to collapse
where to find these solutions??
Check for posts by tenfar for the signed twrp.
The firehose was included in one of the leaked update packages. I don't remember which one. I got my copy by running tcpdump while running tenfar"s twrp flasher.
Druboo666 said:
where to find these solutions??
Click to expand...
Click to collapse
tdm said:
Check for posts by tenfar for the signed twrp.
The firehose was included in one of the leaked update packages. I don't remember which one. I got my copy by running tcpdump while running tenfar"s twrp flasher.
Click to expand...
Click to collapse
also works in B32??i am on b32 and i am stuck with stock recovery as bootloader as been striped from b32 so this will give me TWRP back on B32??
Druboo666 said:
also works in B32??i am on b32 and i am stuck with stock recovery as bootloader as been striped from b32 so this will give me TWRP back on B32??
Click to expand...
Click to collapse
I don't know, you can try.
Jay_Nz said:
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
Click to expand...
Click to collapse
I just posted some huge verbose $hit on your previous post, just sayin
Hi, Thank you for your guidance so far. Question - if the previous owner just flashed stock rom then shouldn't g that get rid of root. As you can see from this 2nd post I checked on some root apps and it said it is rooted and su is phh so I downloaded phh su from play store and now rooted apps work fine. Some one pointed out chances of my phone having a malware are quite high so I just want to clean all up and have nandroid g back up. It is an awesome phone. As per your recommendation should I flash using miflash.? Would updating from sd card in phone settings not put it back to complete stock and get rid of root and everything.? When I restart I don't get that device can't be checked for corruption message. I'm on marshmallow at the moment so flashing nougat be ok whether it if from miflash or SD card firmware update.? Appreciate your assistance. Thank you
Yes, if the previous owner flashed stock only, you would not have root. He either flashed a malicious package or "helpfully" pre-rooted it for you. So you have untrusted and unknown, and regardless of what it may seem, not stock software.
There are several "return to stock" threads. I would study a couple to get a feel for how the procedure works and then follow one of them. Here's one I pulled up in a search:
https://forum.xda-developers.com/axon-7/development/rom-guide-how-to-restore-stock-a2017u-t3549227
I can't vouch for it, it's just the first one that popped up. However, it does seem to be very complete both in instructions and flashing everything from the boot stack on up to boot and system.
Note that b20 is rather old now -- I believe it's the first firmware that shipped on the device. You could make an effort to find newer files. But it's not really necessary, as you should get an OTA update notification after you boot into the stock system.
Good luck!
Jay_Nz said:
Hi, Thank you for your guidance so far. Question - if the previous owner just flashed stock rom then shouldn't g that get rid of root. As you can see from this 2nd post I checked on some root apps and it said it is rooted and su is phh so I downloaded phh su from play store and now rooted apps work fine. Some one pointed out chances of my phone having a malware are quite high so I just want to clean all up and have nandroid g back up. It is an awesome phone. As per your recommendation should I flash using miflash.? Would updating from sd card in phone settings not put it back to complete stock and get rid of root and everything.? When I restart I don't get that device can't be checked for corruption message. I'm on marshmallow at the moment so flashing nougat be ok whether it if from miflash or SD card firmware update.? Appreciate your assistance. Thank you
Click to expand...
Click to collapse
Hi thanks for the reply. I downloaded zip from zte and did an update from phone settings, it pumped me to marshmallow but next release version of zte up. Then another Ota and now I'm on nougat. Checked and root access is gone as expected but funnily enough app shows no root access but busy box binary yes.. Don't know if that's normal. Did a full factory reset too. Now I'm on full Chinese variant stock rom unrooted hence getting Ota. I pressed volume and power button together and managed to get to the screen with start in green and text screen. Other options included restart, power off, reboot to recovery and bootloader and it did show bootloader is locked. I'm thinking of unlocking bootloader, installing TWRP, then root through magisk and perhaps change to A2017U (usa firmware)... Fingers crossed. Thanks again..
tdm said:
Yes, if the previous owner flashed stock only, you would not have root. He either flashed a malicious package or "helpfully" pre-rooted it for you. So you have untrusted and unknown, and regardless of what it may seem, not stock software.
There are several "return to stock" threads. I would study a couple to get a feel for how the procedure works and then follow one of them. Here's one I pulled up in a search:
https://forum.xda-developers.com/axon-7/development/rom-guide-how-to-restore-stock-a2017u-t3549227
I can't vouch for it, it's just the first one that popped up. However, it does seem to be very complete both in instructions and flashing everything from the boot stack on up to boot and system.
Note that b20 is rather old now -- I believe it's the first firmware that shipped on the device. You could make an effort to find newer files. But it's not really necessary, as you should get an OTA update notification after you boot into the stock system.
Good luck!
Click to expand...
Click to collapse
But that's for the A2017U... Be careful with that, he can brick his phone or lose signal

Categories

Resources