Database Info

Alcatel One Touch Evolve 5020t

I know this phone is fairly new and I was able to root it, but I'm wondering if there is any news on a cwm recovery being developed for it. Thanks for any info!

Is it a difficult task to make a CWM for a new phone?

i need help, i mixed up the system apk`s
can somebody help me out. i just need the app folder from root access. help me. i dont want to buy another device just for take a back up from it
can someone upload the apk`s or the folder. sorry for bad english. i hope somebody help me out! :crying:

I know you can build a cwm recovery image for this phone with mtk droid root & tools. The only catch is I think the boot loader is locked because if you try to dump or write with sp flash tool it talks about having a secure baseband and the need for a authentication file to be able to do anything with the flash with sp flash tool. Mtk droid root & tools does ask to prepare the device by writing to the boot.img I think, but it also states the recovery needs to be flashed with sp flash tool. I'm unsure if by writting to the boot.img file it unlocks the baseband or not but if it doesnt unlock the device you could end up with a brick.

hound_dog_420 said:
I know you can build a cwm recovery image for this phone with mtk droid root & tools. The only catch is I think the boot loader is locked because if you try to dump or write with sp flash tool it talks about having a secure baseband and the need for a authentication file to be able to do anything with the flash with sp flash tool. Mtk droid root & tools does ask to prepare the device by writing to the boot.img I think, but it also states the recovery needs to be flashed with sp flash tool. I'm unsure if by writting to the boot.img file it unlocks the baseband or not but if it doesnt unlock the device you could end up with a brick.
Click to expand...
Click to collapse
A developer over at androidforums.com looked at it extensively and said it couldn't be done because the bootloader is locked. All we can do right now is root the phone.

No roms, but once root is acheived, you can install Xposed modules to get the feel of a custom rom. Gravitybox is awesome. I have:
* enabled the buttons to be illuminated when the screen is on (no more guessing where that blasted back key is)
* modified the statusbar
among a couple other minor changes. The only thing bothering me that I have been unsuccessful with as of yet is not being able to actually uninstall the factory bloatware even though root is acheived and TiBu runs fine. Other than that, this phone is damn good for what it is and what I need it for (my Nexus 7 is my workhorse and I just use this phone for **GASP**, phone stuff as well as an MP3/Podcast player thanks to it using microsd cards). It is sluggish and clunky, but it gets the job done and $50 for a brand new GSM phone off contract? Yes please. Not to mention that the Alcatel overlay is pretty unobtrusive when compared to Motoblur, Touchwiz or Sense.
(I only posted this long diatribe here because this thread is one of the top ones to show up when googling "root alcatel one touch evolve". Information for this phone is pretty scant but seems to be popular enough that some people will start looking for that info. If I need to delete this or make my own thread, I'll happily oblige).

hooah212002 said:
The only thing bothering me that I have been unsuccessful with as of yet is not being able to actually uninstall the factory bloatware even though root is acheived and TiBu runs fine.
Click to expand...
Click to collapse
I rooted my wife's Alcatel One Touch Evolve for this purpose, but TB cannot uninstall bloatware system apps. Did any one find a work around to this?
__________________
Sent from my LIFE PLAY using Tapatalk Pro.

hooah212002 said:
No roms, but once root is acheived, you can install Xposed modules to get the feel of a custom rom. Gravitybox is awesome. I have:
* enabled the buttons to be illuminated when the screen is on (no more guessing where that blasted back key is)
* modified the statusbar
among a couple other minor changes. The only thing bothering me that I have been unsuccessful with as of yet is not being able to actually uninstall the factory bloatware even though root is acheived and TiBu runs fine. Other than that, this phone is damn good for what it is and what I need it for (my Nexus 7 is my workhorse and I just use this phone for **GASP**, phone stuff as well as an MP3/Podcast player thanks to it using microsd cards). It is sluggish and clunky, but it gets the job done and $50 for a brand new GSM phone off contract? Yes please. Not to mention that the Alcatel overlay is pretty unobtrusive when compared to Motoblur, Touchwiz or Sense.
(I only posted this long diatribe here because this thread is one of the top ones to show up when googling "root alcatel one touch evolve". Information for this phone is pretty scant but seems to be popular enough that some people will start looking for that info. If I need to delete this or make my own thread, I'll happily oblige).
Click to expand...
Click to collapse
Were you able to make a backup of the phone before installing GravityBox?

To those wondering...The reason that TB can't remove the bloatware is it isn't in the /system/app folder.
Use some other app like Root Explorer or whatever you like and go to /system/custpack/app/unremoveable.
that's where they all are.

MrPandroid said:
To those wondering...The reason that TB can't remove the bloatware is it isn't in the /system/app folder.
Use some other app like Root Explorer or whatever you like and go to /system/custpack/app/unremoveable.
that's where they all are.
Click to expand...
Click to collapse
I couldn't find the custpack folder.

Sorry, I meant /custpack/app/unremoveable.
It's not under /system. I apologize. So /custpack/app/unremoveable

MrPandroid said:
Sorry, I meant /custpack/app/unremoveable.
It's not under /system. I apologize. So /custpack/app/unremoveable
Click to expand...
Click to collapse
Thanks for clarifying!

You're welcome! Remove bloatware away!
personally i used ES File Explorer. Worked fine for me.
Obviously, be careful what you remove and such.

Can someone point me to the rooting instructions for this?
Typed on the Nexus

Mordy,
I used Cydia Impactor http://www.cydiaimpactor.com/ and once it said "done" i installed SuperSU and rebooted my phone. That was it.
Edit:
So I've had this phone roughly 2 weeks now. Rooted it on day one. Removed a LOT of crap. Replaced some apps (IE Chrome, stock messaging app, etc)
I have to say this is a decent little phone. Not bad for $40.

removing bloatware
hey so i was wondering if there was any other way to remove the bloatware ? if not what do i do once im in this folder where the system apps are can i just do a delete the apk files ? and will that uninstall all the data for that app? thanks alot

Hello,
anyone can provide boot and recovery for this phone? i have bricked my phone using mtkdroidtools.
Regards

hooah212002 said:
No roms, but once root is acheived, you can install Xposed modules to get the feel of a custom rom. Gravitybox is awesome. I have:
* enabled the buttons to be illuminated when the screen is on (no more guessing where that blasted back key is)
* modified the statusbar
among a couple other minor changes. The only thing bothering me that I have been unsuccessful with as of yet is not being able to actually uninstall the factory bloatware even though root is acheived and TiBu runs fine. Other than that, this phone is damn good for what it is and what I need it for (my Nexus 7 is my workhorse and I just use this phone for **GASP**, phone stuff as well as an MP3/Podcast player thanks to it using microsd cards). It is sluggish and clunky, but it gets the job done and $50 for a brand new GSM phone off contract? Yes please. Not to mention that the Alcatel overlay is pretty unobtrusive when compared to Motoblur, Touchwiz or Sense.
(I only posted this long diatribe here because this thread is one of the top ones to show up when googling "root alcatel one touch evolve". Information for this phone is pretty scant but seems to be popular enough that some people will start looking for that info. If I need to delete this or make my own thread, I'll happily oblige).
Click to expand...
Click to collapse
So it is safe to install the xposed module?

Smarmylamb said:
So it is safe to install the xposed module?
Click to expand...
Click to collapse
I installed it without a problem.

D1358531 said:
I installed it without a problem.
Click to expand...
Click to collapse
Ok. Thanks

ZTE Z830 (Compel) Rooting Thread

ZTE Z830: As some of you (who have recently broke your high-end devices like me!) know this is a cheap "GoPhone" you might have purchased as a replacement. As some of us know: the phones Hardware isn't bad for a low-end device. All very capable. The problem however; THE DAMN RESTRICTIONS ZTE HAS PUT ON THE PHONE.
Here are the problems in case you don't own a Z830:
No Apps are allowed on the SD-card
The bloatware cannot be uninstalled
Almost no internal memory (ZTE claims "4 Gigs of internal storage" but there is only around 800MB when disabling all unnecessary apps)
Anyways if you are stuck like me and have been suckered into buying this prepackaged paperweight. You most likely have one goal: ROOT IT. Which is the main point of this thread; as all of the other forum posts about this phone seem to be with people who have even less knowledge than I have about rooting. I want to figure out how to root this phone so it can live up to its capabilities.
I'm posting here about the methods I've been trying to root this phone with; so someone who has more knowledge about general rooting and coding then they can chime in and add some info.
First Attempt (FAILED) to Root the Device
ALSO KNOWN AS UPDATE.ZIP​The BREAKTHROUGH Information: I've managed to find the stock recovery from the phone's firmware. By pressing Volume Up + Power I got into the phones menu with various options to "update the firmware" It looks like this:
Android system recovery <
Z830V1 . 0 . 0B14
Volume up/down to move
highlight;
Press power to select.
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
apply update from sdcard
apply update from cache
md5 cache
So I tried to the original rooting method and this is what happened
-- Install /sdcard ...
(Installs about 25%)
Package corrupt.
Installation aborted.​
So anyways: I would love some help trying to discover how to root this damn thing. If you own one of these and find some more breakthrough info I would love to know; because I am as well messing with this thing to see if this will ever work.

Just Tried TowelRoot. Doesn't support the z830.

Bump
I didn't want to post a new thread, is there any new information on this front? It doesn't seem like this was a popular enough phone to warrant it's own set of instructions
**************************************
A few of us were successful in finding a perm root. I know the phone has aged a bit now, but it really is a nice cheap spare phone without the bloatware.
The following instructions for the ZMAX worked perfectly but TWRP does not support the touch screen for the z830 so you have to use an OTG mouse to use TWRP. Touch functionality works fine once the entire process is complete. Uninstalling bloatware seems to have to be done with a 3rd party app such as Purify.
https://boycracked.com/2016/04/16/how-to-root-installing-twrp-v3-0-1-recovery-on-zte-zmax-z970/

I have this phone and have been trying various automatic root programs for some time. No luck.

qaz1233 said:
I have this phone and have been trying various automatic root programs for some time. No luck.
Click to expand...
Click to collapse
Yeah it seems like the phone uses some sort of bizarre coding.

........
I try everthing... nothing works....
all apps and PC methods fail...

Does adb work on your device? What are the different modes for your devices? Can you get into the bootloader?
Sent from my Z970 using XDA Free mobile app

TecheTag said:
Does adb work on your device? What are the different modes for your devices? Can you get into the bootloader?
Click to expand...
Click to collapse
Hey, I decided to pitch in as I also have this unfortunate phone. adb does in fact work, but it is crippled. I cannot perform "adb reboot bootloader" as it will simply reboot the phone normally. I tried to boot into the bootloader by pressing volume down+power and was entered into field test mode, as I have come to understand (says FTM on a white rectangle). Volume UP + power does put me in recovery mode, which is cool. Most interestingly, hold UP+DOWN+POWER mounts on my windows machine as ZTE handset diagnostic interface DFU... which apparently is made for flashing firmware with zte's own utility. adb reboot fastboot also just rebooted it normally.
if anyone knows of a useful test i could perform or a could point me towards new strategies i would appreciate it.

Well that sounds promising. It seems like we're breaking new ground here though.

830ingarg said:
Most interestingly, hold UP+DOWN+POWER mounts on my windows machine as ZTE handset diagnostic interface DFU... which apparently is made for flashing firmware with zte's own utility. adb reboot fastboot also just rebooted it normally..
Click to expand...
Click to collapse
Do you think there is something that can be used to flash our own custom firmware on it?

Please someone bump

I have the same phone and it's about worthless without root. Hopefully someone cam figure it out. I would even donate some cash for a solution.

Sort of temporary root achieved with KingRoot
So, I have this goofy phone and I did manage to get something that appears to be root using KingRoot. The PC version didn't work, and neither did TowelRoot or OneClickRoot. Downloading the apk for KingRoot and running it gave me root access, but only until I rebooted the phone. I managed to install SuperSU which allowed me to confirm that I had root. Unfortunately I was not able to uninstall any pre-loaded software while rooted via KingRoot or KingUser. KingRoot acted like it had successfully uninstalled the pre-installed software, but all it uninstalled were the updates. I didn't get a list of software when I tried to uninstall software via KingUser.
So we can boot into Recovery, and can get temporary root. Any ideas on how to get farther with this crippled phone?

pippinstrano said:
So, I have this goofy phone and I did manage to get something that appears to be root using KingRoot. The PC version didn't work, and neither did TowelRoot or OneClickRoot. Downloading the apk for KingRoot and running it gave me root access, but only until I rebooted the phone. I managed to install SuperSU which allowed me to confirm that I had root. Unfortunately I was not able to uninstall any pre-loaded software while rooted via KingRoot or KingUser. KingRoot acted like it had successfully uninstalled the pre-installed software, but all it uninstalled were the updates. I didn't get a list of software when I tried to uninstall software via KingUser.
So we can boot into Recovery, and can get temporary root. Any ideas on how to get farther with this crippled phone?
Click to expand...
Click to collapse
Did you actually gain any space when you uninstalled items with that temporary root? I am able to uninstall updates on default apps even without root. I had one time with KingoApp where it claimed to be rooted, but I lost it with reboot and haven't gotten it back. Very frustrating. Wish I had avoided the reboot.

nothing works

I too got temporary root with kingroot, got to ambitious with uninstalling system apps and got into a force close loop. A factory reset from the stock recovery got me back in business. I didn't think that a factory reset was supposed to recover apps deleted while in root access. Also kingroot didn't work the first time for me, had to try several times, that was with latest apk, 4.1 I think.

Has anyone contacted zte about a bootloader unlock code? I know most phones it is necessary to unlock the bootloader to gain permanent root access. Plus then maybe we could get a custom recovery. I tried contacting them with no luck.

Talked to zte today, won't give unlock code since it will void warranty. Told them I didn't care about warranty since phone is worthless as is, no luck.

It could work the method used in the ZTE Z970? http://forum.xda-developers.com/general/help/zte-zmax-rooted-kingroot-t3110178

I was able to get temp root with Kingroot but doesn't stick after reboot. Today I got root to stick by using Flashify to flash superuser zip (http://download.chainfire.eu/supersu). I then deleted Kingroot apps. I was able to uninstall some ATT apps but not google apps. I tried SD Card Fix but didn't work and still can't change/mount r/w in root explorer.

[Resolved] Alcatel A460G Rooting Trouble - a lost cause.

I've totally given up on this & explain in my last post, below.
------------------------------------------------------------------------------
To start with I wish to say a few things to be as clear as possible:
I have been visiting here for a couple of years already, but never registered because frankly - I was intimidated. I am not a dev, or a coder - I am merely a guy who enjoys tinkering a bit - and I have discovered how much fun cheap Android devices can be.
Lately a chain store has an Alcatel One Touch Pixi Pulsar A460G (TCL) from tracfone.
It has a nice 4" screen, Android 4.4.2 and better specs than my LG L34C - so I got it.
Searched extensively and the closest info I found was here at this link:
http://forum.xda-developers.com/andr...icial-t3193624
It seemed to root with Kingo Root - but only temporarily and its Superuser doesn't work very well at all.
Even tried the method here - but it starts & never completes:
http://androidxda.com/replace-kinguser-with-supersu
I really want to root this phone and would be happy even if I must use the app to re-install V4.3 from here:
http://alcatelonetouch.com/global-en...0126103150.rar
Also, there is a great bit of info posted here with a de-bloated stock ROM & recovery - but how can I flash it if it will not fully root and/or SU does not work ??
It seems most likely this phone has its bootloader locked by tracfone, and that maybe it is what stops it from rooting - but I do not know enough to be sure.
Any pointers to good help will be hugely appreciated.
Thanks.

Also...
I tried Kingroot on this Alcatel One Touch Pixi Pulsar (A460G, TCL, mt6582) running 4.4.2 .
It took a few tries (as suggested) and seemed to do...something - but not enough.
I very much hope some tool or something comes along soon that will allow full access to the file system on this phone as it really seems to be a very nice device.
Best Wishes to All.

vtsnaab said:
I tried Kingroot on this Alcatel One Touch Pixi Pulsar (A460G, TCL, mt6582) running 4.4.2 .
It took a few tries (as suggested) and seemed to do...something - but not enough.
I very much hope some tool or something comes along soon that will allow full access to the file system on this phone as it really seems to be a very nice device.
Best Wishes to All.
Click to expand...
Click to collapse
Post what you can here as working via PM or email does not help anyone else facing the same issues.
Please Post. screenshots (or links to images), logs (from mdrt and spflashtool)(Just add .txt to the end if they do not have it) , The Android mt6582 scatter.txt that mdrt produced. :good:
Can you also please clarify your exact model as there seems to be different versions
Mediatek MT6572M (3G model)
Qualcomm MSM8909 (4G model)

This likely goes against the spirit of this place, but:
After quite literally wasting days trying to get past all the restrictions on this phone I've given up.
There are 2 major things which seem apparent to me from this experience=>
1 - Tracfone has made it impossible to root this phone - or at least so difficult as not to be worth it;
2- Kitkat is just plain nasty because of all the excessive restrictions it has.
End result here is that I have managed to get most everything I desired in another phone instead.
It is an Alcatel C1 AT&T Gophone.
It rooted in a minute, takes my CC sim card and instantly connects to my home Wifi.
After all this I've listed the A460G for sale, cheaply and if it does not sell that is OK as its charger & battery are the same as my new phone's and it can be used as an outside battery charger if/when I swap out batteries.
Conclusions:
- Avoid Tracfone...they and their products are just evil;
- Avoid Kitkat whenever possible or be prepared to fight it for any decent use a'tall.
Thanks for taking the time to read my query.

Hi,
Also got a Alcatel One Touch Pixi Pulsar A460G that I would like to root. I DL CPU-X and CPU-Z and both listed the Soc as a dual core 1.3GHz Mediatek MT6582.
Searching using "Alcatel One Touch Pixi Pulsar A460G" this was the only post I found.
While I have never Rooted any Android phone am willing to spend some time searching for other rooting apps and hope to be successful with some guidance from more experienced members.
Recently I have changed my search to "root MT6582" and have found a few posts that claim to be able to root any listed MediaTek hardware.
with "Graphical Auto Root tool" http://www.androiddevs.net/root-tool-mediatek-phones/ [Tutorial] Root Your Vivo Air By bmxerkid954, Senior Member on 9th February 2015, 08:23 AM
http://forum.xda-developers.com/vivo-air/general/tutorial-root-vivo-air-t3025960?nocache=1
Appreciate comments especially concerning "Graphical Auto Root tool" http://d-h.st/vvS
Thanks
Ken

I think I tried that one, but cannot be 100% certain as my list got messed up at one point.
Is yours also a tracfone ??
Seems to me that most of my problems were because of how tracfone locked it down so badly.
I will be very curious to see what you post back about your device and your success; please do tell how it goes ??
Addendum=>
This "Graphical Auto Root tool" is something that instantly 'updates' then morphs into root genius, which did not work for my phone at all.
Thanks.

Hi vtsnaab,
Yes mine is a TracFone.
Searched using "Alcatel One Touch Pixi Pulsar" and all I found was TracFone.
"Seems to me that most of my problems were because of how tracfone locked it down so badly" "After quite literally wasting days trying to get past all the restrictions on this phone I've given up." "I will be very curious to see what you post back about your device and your success; please do tell how it goes ??" As previously mentioned, I have never done this so will keep searching until find a post that has been successful.
Wonder if this same phone is sold under different brand names or networks?
Since this is a Chinese Soc am guessing if anyone has been able to Root it the post will be in Chinese. Since I am not fluent, hope some others are!
Regards
Ken

IMO, rooting is not really optional; most pre-paid devices I've ever seen or used are too crapped up as sold & therefore rather useless unless they can be de-crapified after successful rooting.
With a tool that actually works fully - it is usually quite simple from those I have done myself.
The Chinese ones I've seen & tried usually pretty obvious once opened; they connect visibly, and it has been obvious, like having a big button to click on, then wait for success or failure.
A couple of rooting tools have recently updated, but right now I am not eager to waste any more time fooling around with the very pretty glorified battery charger called 'A460G'.
Maybe if it sits & gathers dust for a time here someone will have an ah-hah moment with one & it will get resurrected, else - no biggie for me for it to sit around.
Best Wishes KenithO in your quest.
Please post back here with what you may learn ??
Thanks.

Original Poster (and others using 4G Alacatel Pixi Pulsar A460G), have you tried this:
c627627 said:
4G Alacatel Pixi Pulsar A460G
...six months ago attempts at rooting this model had been reported as failed, has anything changed as of now [May 2016], can A460G be finally rooted and if so, using what?
Click to expand...
Click to collapse
kirito9 said:
A quick search led me to this thread here and kingroot seems to work but only temporarily. I'm guessing temporarily would mean after a reboot, the root is gone. Root the phone and make a backup of recovery.img and boot.img (kernel) with the Flashify app.
Common ways of rooting if one-click methods don't work are flashing a custom recovery and then flashing SuperSU. You will need to generate a scatter file for your device then make a backup with SmartPhoneFlashTool (SPFT).
Generate scatter file
Make backup with SPFT
Click to expand...
Click to collapse

this phone is rooted
bigrammy said:
Post what you can here as working via PM or email does not help anyone else facing the same issues.
Please Post. screenshots (or links to images), logs (from mdrt and spflashtool)(Just add .txt to the end if they do not have it) , The Android mt6582 scatter.txt that mdrt produced. :good:
Can you also please clarify your exact model as there seems to be different versions
Mediatek MT6572M (3G model)
Qualcomm MSM8909 (4G model)
Click to expand...
Click to collapse
i got root on this phone NOT TELLING ON HOW DID IT EITHER. DID NOT NEED TOO USE MTK TOOLS EITHER NOR SCATTER FILES.
PRIVATE EXPLOIT i. imgur. com/ aWedZMb.png

Too funny.
No help - but unimportant as its gone to the phone recycler anyhow.

Evil-Maiden666 said:
i got root on this phone NOT TELLING ON HOW DID IT EITHER. DID NOT NEED TOO USE MTK TOOLS EITHER NOR SCATTER FILES.
PRIVATE EXPLOIT i. imgur. com/ aWedZMb.png
Click to expand...
Click to collapse
Why will you not say how it was done? Help a guy out, please...
Kenn

Generally speaking as a non-dev, this site has become less & less useful as time has passed - and that 'evil' poster is helping nobody - just making board spam.
This used to be THE place to find the best info when one wanted to gain root access.
Since the makers have come up with ever worse & worse ways to lock down their krapware there is less & less hope to gain root access anymore, basically, to sum it all up as an over-simplified generality:
If Kingo or Kingroot will not work on most any post-Kitkat device, then that's that - and even if one of those DOES work, there's a strong likelihood of being stuck with their krapware because a great deal of the time the only 'cure' for it is SuperSU-Me, and it fails quite often.
But - not to worry...
Once there are landfills with huge piles of orphaned/broken devices I'm sure someone will come up with clever ways to make them into Big Macs or something else equally useful & toxic !!
For me - the Android journey has mostly turned into keeping a list of what is useless and/or a waste of time; Alcatel & Tracfone are VERY high up that list of things & companies to avoid.

As of today's date (11-24-16) I was able to fully root my Alcatel One Touch Pixi (A460G) TracFone, running 4.4.2 KitKat, in about 5 minutes using the latest version of KingoRoot (v1.4.8.2793) with USB Debugging (PC->Phone) after two tries. Everything seems to be working: SD read/write, BusyBox, etc. The only thing I wish I could figure out now is how to replace KingoRoot's featureless default SU app with SuperSU.
If KingoRoot doesn't succeed the first time, keep trying. The second, third or fourth try usually gets it on the more difficult devices. Hope this helps someone in the future.
EDIT: PLEASE DISREGARD. See my followup post below.

Bit Shifter said:
As of today's date (11-24-16) I was able to fully root my Alcatel One Touch Pixi (A460G) TracFone, running 4.4.2 KitKat, in about 5 minutes using the latest version of KingoRoot (v1.4.8.2793) with USB Debugging (PC->Phone) after two tries. Everything seems to be working: SD read/write, BusyBox, etc. The only thing I wish I could figure out now is how to replace KingoRoot's featureless default SU app with SuperSU.
If KingoRoot doesn't succeed the first time, keep trying. The second, third or fourth try usually gets it on the more difficult devices. Hope this helps someone in the future.
Click to expand...
Click to collapse
I rooted mine the same way but, it was a temp root. Please advise.
Sent from my A462C using Tapatalk

Evil-Maiden666 said:
i got root on this phone NOT TELLING ON HOW DID IT EITHER. DID NOT NEED TOO USE MTK TOOLS EITHER NOR SCATTER FILES.
PRIVATE EXPLOIT i. imgur. com/ aWedZMb.png
Click to expand...
Click to collapse
Your a real piece of work there friend ......
All who read this know the link maiden posted does not exist they are just posting to be posting there is a site dedicated to rooting and flashing of alcatel devices
www.alcatelroot.com try there maby they have some info
It is tracfone making it so difficult to achieve root i am not sure why yet but working on it
On another note ive ordered the alcatel device and will update once ive achieved root successfully with full directions

Bit Shifter said:
As of today's date (11-24-16) I was able to fully root my Alcatel One Touch Pixi (A460G) TracFone, running 4.4.2 KitKat, in about 5 minutes using the latest version of KingoRoot (v1.4.8.2793) with USB Debugging (PC->Phone) after two tries. Everything seems to be working: SD read/write, BusyBox, etc. The only thing I wish I could figure out now is how to replace KingoRoot's featureless default SU app with SuperSU.
If KingoRoot doesn't succeed the first time, keep trying. The second, third or fourth try usually gets it on the more difficult devices. Hope this helps someone in the future.
Click to expand...
Click to collapse
I regretfully recant my earlier statement above and sincerely apologize if I mistakenly offered any others false hope. I was fooled into believing my A460G was rooted because of the strange way it mounts internal & external storage. It seems that the A460G views the external SD card as internal storage & the internal storage as an external card which allows full read/write access to the external SD card out of the box.
Currently, I am still looking for a way to root this phone. AlcatelROOT.com has nothing whatsoever on the Pixi Pulsar (A460G), neither does Google or Yahoo it seems. I am open to suggestions.
EDIT: I also request that the forum mods remove the "[RESOLVED]" tag in the subject line of this thread as the A460G has not, thus far, been successfully rooted that any of us are aware of. Thanks.

In theory, if we had a custom recovery, we could just flash recovery and install supersu. Right?

nopeski
kfjhu said:
In theory, if we had a custom recovery, we could just flash recovery and install supersu. Right?
Click to expand...
Click to collapse
sorry bud but you would still need to unlock the bootloader somehow before flashing a recovery which would mean you need to root it first or find an exploit

This phone can be rooted by first unlocking the bootloader as I did con a zte prestige phone locked to sprint/boost thanks to "farkin genius" Mr. Hroark13, the solución, it's on these forums. Afaik, it's an ADB command done while connecting phone to pc and it should work. Haven't tried it yet. Look up
"zte prestige temp root achieved xda".
It could be your ticket to rooting this bastard. Shame con you Alcatel and tracfone + bigbrother.
"This was found by me (Hroark13),I can not believe it was this easy
To turn off nand / system write protection on the ZTE ZMAX and maybe other phones
run this command in adb shell or terminal
reboot disemmcwp
to re-enable write protection issue this command
reboot emmcwpenab
I AM A FARKING GENIUS"
Massive credit goes to Mr. Hroark13
So basically use this command and then use ur favorite way to root and same as usual. Bada-boom Bada-bing permanent root. Restarted 10 times and never lost root.
Fu evilmaiden for being selfish

[ROOT][TUTORIAL] How to root your SM-T337A with SuperSU (Temporary root)

I've made this thread to teach T337A owners how to root their device with SuperSU. Please note that this is a system-less root, meaning it's temporary, but can be re-applied. Rooting only takes about 5-7 minutes and brings numerous tweaks and advantages to your device. Just remember that every time you reboot or shut the device down, you will need to repeat the rooting process. This tutorial was designed for Lollipop 5.1.1, but it should work on KitKat as well.
Before beginning, you will need to download the following file, unzip it on your pc, then transfer it to your device's internal storage/external sd card.
T337AUCU2BOH4 (Lollipop) firmware can be found here
Root Files can be found here
Lets start!
1) Install both the APK files in the file on your device, If prompted, allow installation from unknown sources.
2) Make sure your device is connected to WiFi, then open Kingroot.
3) Once Kingroot is "Done searching for the best root strategy", click the "Try Now" button and wait about 3 minutes for KingRoot to give you a "Root Successfully" message.
4) This is where it gets kinda tricky, immediately after receiving the root success message, go into SuperSU-me, and grant root permissions when prompted.
5) Click on the big blue button in the middle of the frame and wait about 1 minute for the process to complete. DO NOT UPDATE THE SUPERSU BINARY, IT WILL CAUSE YOUR DEVICE TO BOOTLOOP.
6) IMMEDIATELY after the process has completed, go into Settings and make sure KingRoot or Purify is not installed! This is an important step because Kingroot and Kingroot adware tends to install itself in the system partition which can cause problems and frustration.
7 - Recommended) Download a root file explorer (such as ES File Explorer) and search "King" under /data and /system to ensure that the KingRoot app and its bloatware has been wiped from the system. This is to ensure that Kingroot still works properly after a reboot.
8) Enjoy root access!
If this tutorial helped you please be sure to hit the :good: button. If you had any issues or troubles during this process please feel free to let me know down below.
Cheers!

@KingOfTheNet
will flashfire work? bc it wont with kingroot
also, could itit.d be enabled and run these off of a script for example on startup so we don't have to do this after each reboot/shutdown
but i believe you would have to capture kingroots data somehow in the process of rooting

toolhas4degrees said:
@KingOfTheNet
will flashfire work? bc it wont with kingroot
also, could itit.d be enabled and run these off of a script for example on startup so we don't have to do this after each reboot/shutdown
but i believe you would have to capture kingroots data somehow in the process of rooting
Click to expand...
Click to collapse
FlashFire does work on SuperSU, I've tested that for myself. It does not work with KingRoot.
For the second question, I'm not sure. I haven't looked through that file myself and I might look through it later but right now, I would just avoid rebooting the tablet if you wanna keep root without repeating the process over and over again. It's what I do, repeating the process over and over again can get very tedious and annoying.
Cheers!

I assume you're talking about 5.1.1? It won't work with kingroot versions higher than 4.8. Also, flashfire will load, but if you try to flash a zip you're screwed. You can actually use replace kingroot with supersu zip in terminal emulator on any version kingroot. Same deal with su binary, don't update it. Wish I could figure out how I had permanent for with kingroot. I had to go messing with things and lost it. Nothing really special about this method, unless there's a dev out there that can do something with it.

xjimmy said:
I assume you're talking about 5.1.1? It won't work with kingroot versions higher than 4.8. Also, flashfire will load, but if you try to flash a zip you're screwed. You can actually use replace kingroot with supersu zip in terminal emulator on any version kingroot. Same deal with su binary, don't update it. Wish I could figure out how I had permanent for with kingroot. I had to go messing with things and lost it. Nothing really special about this method, unless there's a dev out there that can do something with it.
Click to expand...
Click to collapse
Sorry for the late response. Yes, somethings I forgot to mention in the original post:
1)Updating the SU Binary will put your device in a bootloop
2)Flashing anything with flashfire (based on what I've seen) results in a soft brick
3) I know you can replace kingroot with SuperSU in terminal, but when you reboot, you're unrooted again.
4) I'm trying to figure out how I could altar the boot.img so we can get permanent SuperSU on this thing the same way Chainfire did it with the US and Qualcomm Samsung Galaxy S7's.
Cheers!

Hi, @KingOfTheNet, thanks for helping out with this device, i rooted my device on KK nk2 build and now updated to 5.1.1, thanks to you! now i would like to root 5.1.1 (am aware it is a temp. root)
i have superSu Pro, do i need Super Sume for this to work?

KingOfTheNet said:
Sorry for the late response. Yes, somethings I forgot to mention in the original post:
1)Updating the SU Binary will put your device in a bootloop
2)Flashing anything with flashfire (based on what I've seen) results in a soft brick
3) I know you can replace kingroot with SuperSU in terminal, but when you reboot, you're unrooted again.
4) I'm trying to figure out how I could altar the boot.img so we can get permanent SuperSU on this thing the same way Chainfire did it with the US and Qualcomm Samsung Galaxy S7's.
Cheers!
Click to expand...
Click to collapse
Somehow I had it permanently rooted with kingroot a while back. I had the 4.9.6 apk on my tab at the time, is all I know. I could've updated from an earlier version, and maybe that was the cause. I've tried so many different versions of kingroot with no luck, but one peculiar occurrence; if I open kingroot, get into the settings and uninstall kingroot without saving a backup of root, then delete all the files in the tablet's main directory, and reinstall kingroot version 4.8.0, it somehow retains a partial permanent root. At least on my T337A running 5.1.1 BOH4 it will, as long as I get a fresh install of 4.8.0, let it root, then hit the optimize button right after. Then wait until it finally tells me that kingroot has been deployed as a system app. After that, when I try to open any root apps, the screen will darken as it does when the root permission tab pops up, but it never pops up. The app just freezes. I can kill it in the task manager screen to just go back to using my tablet. After I restart the tab, sometimes it'll tell me an app has been granted superuser permissions. If I open up terminal emulator, type in the 'su' command and hit enter, the screen will turn dark again like it's going to ask me to allow or deny superuser permission, but it just freezes like that again. I've tried all kinds of stuff with 4.8.0, but I still can't get it to stick. If you don't hit the optimize button in kingroot right after rooting, and just wait for kingroot to install as a system app, the allow/deny prompt comes up without freezing, but the partial permanent root glitch doesn't remain. ugh, tired of messing with it though. lol
Edit: I may be wrong. It might need to be rooted with 4.8.0, optimized, then rebooted right away for the partial root. I'll try to do it again and let you know what I find.

bklyndiaz said:
Hi, @KingOfTheNet, thanks for helping out with this device, i rooted my device on KK nk2 build and now updated to 5.1.1, thanks to you! now i would like to root 5.1.1 (am aware it is a temp. root)
i have superSu Pro, do i need Super Sume for this to work?
Click to expand...
Click to collapse
I'm happy to help out! You'd need king root installed, root the tab with king root, then use SuperSU me to replace the kingroot binaries with the SuperSU ones. It is an automatic process and should only take about 30 seconds or less. Pro version of SUPERSUme is not required, free version should work just fine.
Cheers!

xjimmy said:
Somehow I had it permanently rooted with kingroot a while back. I had the 4.9.6 apk on my tab at the time, is all I know. I could've updated from an earlier version, and maybe that was the cause. I've tried so many different versions of kingroot with no luck, but one peculiar occurrence; if I open kingroot, get into the settings and uninstall kingroot without saving a backup of root, then delete all the files in the tablet's main directory, and reinstall kingroot version 4.8.0, it somehow retains a partial permanent root. At least on my T337A running 5.1.1 BOH4 it will, as long as I get a fresh install of 4.8.0, let it root, then hit the optimize button right after. Then wait until it finally tells me that kingroot has been deployed as a system app. After that, when I try to open any root apps, the screen will darken as it does when the root permission tab pops up, but it never pops up. The app just freezes. I can kill it in the task manager screen to just go back to using my tablet. After I restart the tab, sometimes it'll tell me an app has been granted superuser permissions. If I open up terminal emulator, type in the 'su' command and hit enter, the screen will turn dark again like it's going to ask me to allow or deny superuser permission, but it just freezes like that again. I've tried all kinds of stuff with 4.8.0, but I still can't get it to stick. If you don't hit the optimize button in kingroot right after rooting, and just wait for kingroot to install as a system app, the allow/deny prompt comes up without freezing, but the partial permanent root glitch doesn't remain. ugh, tired of messing with it though. lol
Edit: I may be wrong. It might need to be rooted with 4.8.0, optimized, then rebooted right away for the partial root. I'll try to do it again and let you know what I find.
Click to expand...
Click to collapse
Kingroot does allow your device to retain permanent root after a certain time. However, Kingroot is not as powerful as SuperSU, is very limited in terms of what It can do, and has it's own 'bloatware' titled Purify. I'd honestly stick with SuperSU because it's (probably) the most powerful and efficient way to root your phone. I'd also suggest avoiding having to reboot the tablet at all with temp root because you would have to take 5 minutes to install it again, which was a pain in the butt for me.
As for the kingroot app freezing, that's usually the result of a bad download or a bad root. Plus kingroot is very limited in terms of what you can do on your kingrooted device. SUPERSU is the equivalent of an IOS jailbreak. SUPERSU gives you full control of your device, with no bloatware and limits, unlike kingroot.
Kingroot does sometimes delete the su binaries upon rebooting, which is another reason I don't like it all that much.
Another theory I thought of is that it's not Kingroot that's deleting the binaries, it's actually something that's set to happen when the device boots up. Either the actual Android os or the bootloader searches for and deletes the su binaries to prevent root.
I don't know for sure, I've kinda slowed down work on this device mainly because of a project I've been working on with the Samsung Galaxy S7 AT&T (SM-G930A). I'll look into these things when I get the chance.
Cheers!

I understand the limitations of Kingroot, and certainly supersu by all means is better. In the case of flashfire with supersu in this scenario, it's merely the difference of being able to open and run it just enough to work improperly and brick your device vs. Kingroot not being able to open it at all. I posted in a thread long before this one, how to replace kingroot with supersu, only I use the zip file in terminal emulator. Pretty sure I went over flashfire as well. The terminal emulator method works with new versions of kingroot, unlike supersu me. Are you suggesting that the T337A running 5.1.1 BOH4 can achieve permanent root via kingroot after "a certain amount of time"? Because I'm the only one I've seen on xda who's ever posted that they had permanent root from kingroot, but I didn't know how I did it. After I messed with things, i softbricked and had to flash back to stock, which, no offense, the stock file was available way before you posted it. Anyway, it's not the kingroot app freezing per se, i was talking about after rebooting, and without re-rooting, when trying to use rooted apps, they actually start to engage in the kingroot request superuser permissions pop-up. So, no, it's not a bad download, etc. I believe an older version of kingroot somehow permanently rooted my tab, perhaps with the help of something I was messing with at the time, perhaps not. I've intentionally rebooted my tab an unimaginable amount of times, testing to see if I possibly regained permanent root to no avail, so I know how that works. And it's not about having a hard time deciding on kingroot or supersu for a temproot, it's the interest in permanent root, the possibility off something like safestrap, and/or flashing custom roms, etc. When people say temproot is better or safer, i say boo. How many custom roms include a root toggle in the settings? Anyway I wish I could've gotten hold of a developer while I had permanent root. Maybe I could've done a system dump, or even try replacing the permanent kingroot with supers and drying out that could've stuck. You say you slowed down on this device, do you mean you were pursuing permanent root for it? Are you a developer? I have the AT&T S7 Edge (G935A). What's your project on the 930? Is it something for rooted S7's? I still have my edge running the engboot with the echoRom. Anyway, thanks for your reply.
---------- Post added at 01:01 AM ---------- Previous post was at 12:51 AM ----------
https://forum.xda-developers.com/tab-4/help/t337a-temp-root-bootlp-fix-tar-official-t3473737
*https://forum.xda-developers.com/tab-4/general/permanent-root-t337a-5-1-1-kingroot-t3518334
A couple of threads I started a long time ago that may be of interest to you.

xjimmy said:
I understand the limitations of Kingroot, and certainly supersu by all means is better. In the case of flashfire with supersu in this scenario, it's merely the difference of being able to open and run it just enough to work improperly and brick your device vs. Kingroot not being able to open it at all. I posted in a thread long before this one, how to replace kingroot with supersu, only I use the zip file in terminal emulator. Pretty sure I went over flashfire as well. The terminal emulator method works with new versions of kingroot, unlike supersu me. Are you suggesting that the T337A running 5.1.1 BOH4 can achieve permanent root via kingroot after "a certain amount of time"? Because I'm the only one I've seen on xda who's ever posted that they had permanent root from kingroot, but I didn't know how I did it. After I messed with things, i softbricked and had to flash back to stock, which, no offense, the stock file was available way before you posted it. Anyway, it's not the kingroot app freezing per se, i was talking about after rebooting, and without re-rooting, when trying to use rooted apps, they actually start to engage in the kingroot request superuser permissions pop-up. So, no, it's not a bad download, etc. I believe an older version of kingroot somehow permanently rooted my tab, perhaps with the help of something I was messing with at the time, perhaps not. I've intentionally rebooted my tab an unimaginable amount of times, testing to see if I possibly regained permanent root to no avail, so I know how that works. And it's not about having a hard time deciding on kingroot or supersu for a temproot, it's the interest in permanent root, the possibility off something like safestrap, and/or flashing custom roms, etc. When people say temproot is better or safer, i say boo. How many custom roms include a root toggle in the settings? Anyway I wish I could've gotten hold of a developer while I had permanent root. Maybe I could've done a system dump, or even try replacing the permanent kingroot with supers and drying out that could've stuck. You say you slowed down on this device, do you mean you were pursuing permanent root for it? Are you a developer? I have the AT&T S7 Edge (G935A). What's your project on the 930? Is it something for rooted S7's? I still have my edge running the engboot with the echoRom. Anyway, thanks for your reply.
---------- Post added at 01:01 AM ---------- Previous post was at 12:51 AM ----------
https://forum.xda-developers.com/tab-4/help/t337a-temp-root-bootlp-fix-tar-official-t3473737
*https://forum.xda-developers.com/tab-4/general/permanent-root-t337a-5-1-1-kingroot-t3518334
A couple of threads I started a long time ago that may be of interest to you.
Click to expand...
Click to collapse
No offence taken on the firmware post, I was simply trying to spread the fact that the firmware for the device does exist but is very hard to find and is often posted on shady websites for money, unless you're looking in the right places. It only took me 5 minutes on Google to find one of those sites.
You asked if I was saying that the Tab 4 BOH4 firmware allows you to retain permanent root after some time, and yes, that's exactly what I was saying. I rooted my tablet with Kingroot 4.8.0 a while back and after about 4 - 5 reboots (I counted how many times I rebooted it, but the numbers could vary), It retained root. All I do today is avoid rebooting the tablet at all costs. I prefer SuperSU because, like we've said, there are almost no limitations of what you can do in terms of being rooted. I'm trying to find out how I can make root permanent on the tab with SuperSU by using the eng-boot method used to root all Qualcomm variants of the Galaxy S7, but that may take a while. Since my S7 has the eng-boot root method, I can reboot it all I want and it stays rooted with SuperSU. But at this point, It's just an Idea. I mainly need to find out whether or not the bootloader or the os is wiping the binaries on boot. Some older and newer versions of kingroot can retain root after reboot, but I have yet to find a version of the app that can do so.
Actually, some versions of Cyanogenmod and other custom roms had root pre-installed (not like SuperSU, but close enough), and like CM specifically, there was a section in the settings app for this pre-baked root. Even if I still used CM today, I still would've flashed SuperSU. But on a small number of devices, temp root really is better. However, most of those devices that would be on that list have very little to no development on them. Thus, they are not yet (and may never be) supported for permanent root.
I am partially on the road to becoming a developer, but I don't know how far that's gonna go (my prediction is not that far at all). I was doing research on how I could make an eng-boot for the Tab 4, but I became interested in my Galaxy S7 (AT&T). By that, I mean I wanted to make my own custom version of the stock Marshmallow rom ("Custom but stock OS"). To shorten it up, I wanted to create a .zip flashable "super package" which included SuperSU v2.79, Viper4Android, Overclock tools, and other stuff. I've kinda been on and off in terms of motivation to make this idea a reality, primarily because most of the things I wanted to include in this "package", can easily be installed by you in like 3 minutes, or maybe less. The original motive behind the idea was to lessen the work for power users who wanted to free their device "from the shackles". I've been on and off on work between both devices, but It's hard for me to continue the work without proper motivation. These projects are merely just an Idea at this point, but some drafts and copies do exist on my computer.
Creating a custom Android rom straight from my own head is basically an impossible task for me, considering most of the devices I work with have locked bootloaders. I am still learning Java and other Android programming languages in some of my free time but, again, the motivation to continue is something I struggle to find.
Cheers!

Upgrading OS and rooting
I am currently running my t337a on 4.4.2 with build NK2. I was able to root with towel root awhile ago. I want to upgrade my os to 5.1.1 and root after but would like to make sure I go about it the right way.
Any help would be greatly appreciated. Thanks in advance!

loc626 said:
I am currently running my t337a on 4.4.2 with build NK2. I was able to root with towel root awhile ago. I want to upgrade my os to 5.1.1 and root after but would like to make sure I go about it the right way.
Any help would be greatly appreciated. Thanks in advance!
Click to expand...
Click to collapse
You can root on the latest Lollipop firmware, but it's systemless supersu/temporary, meaning it will go away if you shutdown or reboot the device (you can re-root it, of course, but It can be annoying). The option to upgrade is up to you, and once you do upgrade, you can't downgrade (Locked bootloader & different bootloader versions. Lollipop has the new bootloader.) If you are going to upgrade, you can flash the Lollipop firmware via Odin or upgrade via OTA. If upgrading, I recommend taking it over the air, mainly because I'm still working up Odin packages for them. The Odin packages that I do have available are the BOH4 (the previous and the initial Lollipop update) ones, so if you upgrade OTA, it'll take away one step in the upgrade process, making your life a tad bit easier. Reply back if you need further help or have any more questions.
Cheers!

KingOfTheNet said:
You can root on the latest Lollipop firmware, but it's systemless supersu/temporary, meaning it will go away if you shutdown or reboot the device (you can re-root it, of course, but It can be annoying). The option to upgrade is up to you, and once you do upgrade, you can't downgrade (Locked bootloader & different bootloader versions. Lollipop has the new bootloader.) If you are going to upgrade, you can flash the Lollipop firmware via Odin or upgrade via OTA. If upgrading, I recommend taking it over the air, mainly because I'm still working up Odin packages for them. The Odin packages that I do have available are the BOH4 (the previous and the initial Lollipop update) ones, so if you upgrade OTA, it'll take away one step in the upgrade process, making your life a tad bit easier. Reply back if you need further help or have any more questions.
Cheers!
Click to expand...
Click to collapse
I'm highly considering an upgrade for the feel and hopefully a better performance. Also, a few apps I have need updates but only compatible on Android 5 and up. I have the OTA ready to go. Would I need to unroot before upgrading the OS?

loc626 said:
I'm highly considering an upgrade for the feel and hopefully a better performance. Also, a few apps I have need updates but only compatible on Android 5 and up. I have the OTA ready to go. Would I need to unroot before upgrading the OS?
Click to expand...
Click to collapse
It would be best to unroot before installing to avoid any issues during the installation. Other then that, you're in the clear! Just remember, you cannot downgrade after the install!
Cheers!

KingOfTheNet said:
4) I'm trying to figure out how I could altar the boot.img so we can get permanent SuperSU on this thing the same way Chainfire did it with the US and Qualcomm Samsung Galaxy S7's.
Click to expand...
Click to collapse
I have always been under the assumption that the boot.img for the locked BL on the s7 was literally an engineering kernel from Samsung, and not something Chainfire created. The reason Im saying this is because if Chainfire created a boot image that can get around a locked bootloader, then logic should state that he cracked Sprint/ATT's signature for the BL. So my way of thinking is the success of even one locked boot loader ... it should apply across the board for all, correct? Or am I waaaaay off? lol

leeboski44 said:
I have always been under the assumption that the boot.img for the locked BL on the s7 was literally an engineering kernel from Samsung, and not something Chainfire created. The reason Im saying this is because if Chainfire created a boot image that can get around a locked bootloader, then logic should state that he cracked Sprint/ATT's signature for the BL. So my way of thinking is the success of even one locked boot loader ... it should apply across the board for all, correct? Or am I waaaaay off? lol
Click to expand...
Click to collapse
(1st question) Actually yeah, lol. It was an engineering kernel, he didn't make it . I'm assuming that was used during the development of the phone so Samsung and AT&T could construct the OS without running into any issues with the phones locked bootloader. At the time, I thought that Chainfire thought of some "mad science" to altar the boot.img so that it wont check the signatures of any of the files on boot.
Now I'm thinking:
1) He found a way to obtain all the phones signatures so that way he knows what signature the desired files (like a build of TWRP, or instance) would have to have so it can flash and boot properly.
--OR--
2) He somehow obtained or reproduced the engineering kernel that, like I said, was most likely used during software development for the phone (constructing the OS and the rest of the software).
I've done a little research on what engineering kernels actually do and why they are so useful now (to most people, the name is enough, lol). Apparently, they completely skip some of the signature checks on boot, primarily for /SYSTEM (The OS), which is why we were able to achieve permanent root the Qualcomm Galaxy S7 & S7 edge models. I do not think they skip signature checks for /RECOVERY or /BOOT, but we know that if we either reproduce or obtain the engineering kernel for this tablet, we can achieve permanent root the exact same way. I could be wrong, as I do not know for certain the Ins and outs of engineering kernels and how to get them, but It is very possible.
(2nd question) Now, I do not have much knowledge of bootloaders and signature checks, but I would go to the best assumption that since Sprint & AT&T, for example, are 2 completely different companies and are not affiliated (as of writing this), their bootloaders and updates would not have the same signatures. If they did, then Sprint would have to go to AT&T to sign their updates and such, and AT&T would have to do the same thing for Sprint. It just wouldn't really make sense. Lets think of it this way, If Target wants to sell a product in their stores that's already sold at Walmart, then should Target have to go to Walmart to get that approved? Or if Walmart wanted to sell something that's already sold at Target, then should Walmart have to go to Target for approval? Absolutely not, that wouldn't make any sense. Once again, I could be wrong, but it would make the most sense.
Please, anyone, correct me if I'm wrong.
Cheers!

KingOfTheNet said:
(1st question) Actually yeah, lol. It was an engineering kernel, he didn't make it . I'm assuming that was used during the development of the phone so Samsung and AT&T could construct the OS without running into any issues with the phones locked bootloader. At the time, I thought that Chainfire thought of some "mad science" to altar the boot.img so that it wont check the signatures of any of the files on boot.
Now I'm thinking:
1) He found a way to obtain all the phones signatures so that way he knows what signature the desired files (like a build of TWRP, or instance) would have to have so it can flash and boot properly.
--OR--
2) He somehow obtained or reproduced the engineering kernel that, like I said, was most likely used during software development for the phone (constructing the OS and the rest of the software).
I've done a little research on what engineering kernels actually do and why they are so useful now (to most people, the name is enough, lol). Apparently, they completely skip some of the signature checks on boot, primarily for /SYSTEM (The OS), which is why we were able to achieve permanent root the Qualcomm Galaxy S7 & S7 edge models. I do not think they skip signature checks for /RECOVERY or /BOOT, but we know that if we either reproduce or obtain the engineering kernel for this tablet, we can achieve permanent root the exact same way. I could be wrong, as I do not know for certain the Ins and outs of engineering kernels and how to get them, but It is very possible.
(2nd question) Now, I do not have much knowledge of bootloaders and signature checks, but I would go to the best assumption that since Sprint & AT&T, for example, are 2 completely different companies and are not affiliated (as of writing this), their bootloaders and updates would not have the same signatures. If they did, then Sprint would have to go to AT&T to sign their updates and such, and AT&T would have to do the same thing for Sprint. It just wouldn't really make sense. Lets think of it this way, If Target wants to sell a product in their stores that's already sold at Walmart, then should Target have to go to Walmart to get that approved? Or if Walmart wanted to sell something that's already sold at Target, then should Walmart have to go to Target for approval? Absolutely not, that wouldn't make any sense. Once again, I could be wrong, but it would make the most sense.
Please, anyone, correct me if I'm wrong.
Cheers!
Click to expand...
Click to collapse
No that makes perfect sense and thanks for clearing it up.
The whole thing about the signature being the means by which the bootloader is locked is important. Atleast to me it is, so thank you for clearing that up. :good: And so, it makes sense that the System partitions Signature check being skipped IS what allows access to root. But where my opinion differs on this is the Boot and Recovery implementation of the Signatures. I believe that it IS the carriers implementation that does not allow the Recovery and Boot partitions to be modified. If it were Samsungs then how is Samsung going to incorporate a Universal bootloader that knows how to load all carriers data, policy, etc?
And possibly this is what you were saying above and I am misreading it...
***EDIT*** I see you said that the signatures would NOT be the same between carriers, so I am in line with your theory there as well.

leeboski44 said:
No that makes perfect sense and thanks for clearing it up.
The whole thing about the signature being the means by which the bootloader is locked is important. Atleast to me it is, so thank you for clearing that up. :good: And so, it makes sense that the System partitions Signature check being skipped IS what allows access to root. But where my opinion differs on this is the Boot and Recovery implementation of the Signatures. I believe that it IS the carriers implementation that does not allow the Recovery and Boot partitions to be modified. If it were Samsungs then how is Samsung going to incorporate a Universal bootloader that knows how to load all carriers data, policy, etc?
And possibly this is what you were saying above and I am misreading it...
***EDIT*** I see you said that the signatures would NOT be the same between carriers, so I am in line with your theory there as well.
Click to expand...
Click to collapse
I'm glad I could be of help, however I don't see where I stated that the signature implementations on the BOOT and RECOVERY partitions was Samsung's idea not the carriers, if you could point that out for me that would be great.:good:
The engineering kernels skip SOME signature checks, both when flashing and booting into partitions, but I do not know exactly which ones they skip. We know it skips some of the signatures for /SYSTEM, but it does not do the same for the 2 other main ones, those being /BOOT & /RECOVERY. We know because "one of our own" attempted to flash their own build of TWRP recovery to the device (SM-G930A to be specific) only to get a signature check fail when booting the phone, which of course means that the phone has a locked bootloader and that the signatures for the /RECOVERY partition are still checked, but I do not know for certain about /BOOT. If I had to assume I'd say that /BOOT isn't checked, given the fact that if your phone is rooted then you would have had to flash the engineering kernel, which, like I said, skips some signature checks.
I hope I've cleared most things up for you.
Cheers!

KingOfTheNet said:
I've made this thread to teach T337A owners how to root their device with SuperSU. Please note that this is a system-less root, meaning it's temporary, but can be re-applied. Rooting only takes about 5-7 minutes and brings numerous tweaks and advantages to your device. Just remember that every time you reboot or shut the device down, you will need to repeat the rooting process. This tutorial was designed for Lollipop 5.1.1, but it should work on KitKat as well.
Before beginning, you will need to download the following file, unzip it on your pc, then transfer it to your device's internal storage/external sd card.
Root File: https://mega.nz/#!74Jl0ZqY!knlHuexbYGFkk1f4wHxq16u3L38EtfR9scQ0H7hISTA
Lets start!
1) Install both the APK files in the file on your device, If prompted, allow installation from unknown sources.
2) Make sure your device is connected to WiFi, then open Kingroot.
3) Once Kingroot is "Done searching for the best root strategy", click the "Try Now" button and wait about 3 minutes for KingRoot to give you a "Root Successfully" message.
4) This is where it gets kinda tricky, immediately after receiving the root success message, go into SuperSU-me, and grant root permissions when prompted.
5) Click on the big blue button in the middle of the frame and wait about 1 minute for the process to complete. DO NOT UPDATE THE SUPERSU BINARY, IT WILL BOOTLOOP.
6) IMMEDIATELY after the process has completed, go into Settings and make sure KingRoot or Purify is not installed! This is an important step because Kingroot and Kingroot adware tends to install itself in the system partition which can cause problems and frustration.
7 - Recommended) Download a root file explorer and search "King" under /data and /system to ensure that the KingRoot app and its bloatware has been wiped from the system.
8) Enjoy root access!
If this tutorial helped you please be sure to hit the :good: button. If you had any issues or troubles during this process please feel free to let me know down below.
Need T337A firmware? Check out my thread here: https://forum.xda-developers.com/tab-4/general/download-sm-t337a-lollipop-firmware-t3536509
Cheers!
Click to expand...
Click to collapse
The firmware you provided saved my sm-t337A tablet from being soft bricked. Although I was able to gain temp root from this method, king root tried to disable the SELinux on my device and after trying to temp root again caused the app to implant itself as bloatware into the /systems folder and was non functional when using the app. Do you happen to know of a custom recovery (TWRP or CWM) which would work for this device?

Help to fully remove kingroot on legacy device

So I have a lg l58bl. Its supposedly unrootable. But before I knew that I tried to use kingroot on it hoping that app could do it. (I had read it could work on a nearly identical phone model in terms of hardware/processor.)
But it didnt work. Well it seemed like it halfway did. I could access some stuff I couldnt before but still my profile was not seen as rooted. I think I changed a fuse setting file and bricked.
Did a factory reset. Then my brightness would auto adjust to 65% even after I set it to 0% 50 times. Did that a minute after booting.
Then I tried searching in directories and found a lot of kingroot files. Some that are documented. Some that are not. Like a "kr." File in some place like bin. It was a file written to run every boot to restructure the permission tree and give the newly added account of kr full root. Pretty simple solution.
So this phone was abanodoned out of fear of infection. I didnt know if itd be safe to connect to internet on it. So ive isolated it until I can know.
I worried my brightness was due to some kr malware stuff. Although I read that auto brightness was a feature lg phones had for sales room display until a sim was used. But even after inserting an old sim. It still auto adjusted with auto brightness OFF. So how I fixed it was wait until it booted, change to 0. Before it could auto adjust yank batterty out and then remove sim. (Sim doesnt have to be valid). Now it doesnt auto adjust. When I powered it off by button it took an extra bit like it was rewriting a configuration for brightness. That was a problem that took a while. Now
Can anyone give me a list of all kr related files so I can delete anything fishy? I found this but it doesnt help much.I worry this method would miss some of those files. https://forum.xda-developers.com/t/2020-replace-kingroot-v5-x-or-kingo-root-with-supersu.3904880/

Re-flash Stock ROM.

Unfortunately there is no firmware download for LG Rebel 2 LTE tracfone - all links are down or fake

aIecxs said:
Unfortunately there is no firmware download for LG Rebel 2 LTE tracfone - all links are down or fake
Click to expand...
Click to collapse
So alecxs, saw you in this topic https://forum.xda-developers.com/t/kingroot-malware-adware-root.3563090/page-3
You got any ideas in your wise experience?
On that kr txt file, files I saw in my phone are not listed there. 1 was an html5 file.
Whats worse, if I recall right I did not have permission to delete 1 of the files.
If I get the courage to try ill see if I can find those files again.
So as it stands, without fastboof or download mode (lol fastboof)
And no kdz. And kr mystery. The thing might as well be bricked?
I would like to use this phone on the net but I suppose that goose was cooked unless someone knows a way.
I had tried supersume pro I think but it failed.
If only there was a way to wipe partitions in factory reset mode but it just has a white background menu.
Anybody know if I could intentionally corrupt or delete the partition with the spy files? Probably not easy without root. But I did somehow edit 1 of the main config files and move it back to the main dir renamed old file and restarted to brick. But not sure if kr was given me halfroot or the facade of root.
Hmm. if im using this online wouldnt I risk infecting others through that? Like if kr is running a background daemon couldnt they inject things into files?
jwoegerbauer said:
Re-flash Stock ROM.
Click to expand...
Click to collapse
If only it was that easy lol. Thanks though

The best you can do is root that phone with kingroot, then use the kingroots official unroot/uninstall menu within the kingroot app.
Do not try to wipe system partition without having backup or stock rom.

Hmm. Looking more and more hopeless. Becausd I bricked after root attempt(which failed) but still kingroot managed to install stuff. Some in places I dont hVe permissions to do anything with.
I would guess it used like dirtycow or w/e to install through temp?
And now that its factory reset even ifi install kr again to uninstall wont there still be the instance of kr from before brick?
Crap.
Well unless I can figure out a way I guess this phones toast. I really dont feel comfortable using it with potentially malicious files hidden in it running on boot.
Not that huge of a loss but I would like to use it

AstralA said:
even ifi install kr again to uninstall wont there still be the instance of kr from before brick?
Click to expand...
Click to collapse
Kingroot has a very clean Uninstaller and will remove itself completely. If there is any (potential) malware left this is not caused by Kingroot, it's more likely you accidentally granted root access to that malware.

Kingroot was the only app installed after factory reset. So that file could only come from kingroot. It had kr in the file name anyway. Oh well. If I do anything with it ill lock all internet and use a linux installation. But probably wont even do that. Kingroot as good as ransomware because good luck cleaning up afterwards. sounds like kingroot used to not be so bad. But maybe it was that malicious and nobody suspected until it was too late.
Edit: of course kingroot is great if you have a firmware to reinstall and all else fails. Like pos devices stuck in read only from manufacturer.
But it sucks to not feel able to safely use a device that I payed money for. Which was the problem from the manufacturer as well.
I still didnt find the files in question because it would be a crap chore but I did recall kingroot failed to get root initially, then after trying again it bricked. But I could still get to factory reset holding vol up and pow. But even though kingroot failed to get root it did manage to install files in read only directories (ro without root). Presumably adding a new user with permissions that the main user lacks. But thats the problem. Theres not a way for me to access the directories where the files are. Because kr cant give the main original user those permissions I guess...
I heard of a similar tactic to root fire hd 3rd gens that auto updated to be fstabbed stuck in ro with no bootloader access.
Use kingroot to brick the fire then after bricking fastboot works.
But if I did that with the phone I still lack a dz or kdz/img. But I could try installing a different phones kdz that uses the same board/cpu. As far as I can tell theres a resistor on those pcbs to determine brand/service provider.
The k7 is identical for instance (in terms of hardware) but the last time I tried that it did flash but then the phone is bricked hard. Lgup cant recognize the model because the k7 firmware doesnt match whatever bits are used to sign what version it is (m151 or ls675) yet the cpu and ram matches.
But I might try that in my desperation.
Also words of wisdom. Dont cross flash firmware because it will usually end in brick.
I only entertain that thought because of the situation.
Although if someone knew where I could find the bits to set phone model in firmware? Thatd help. Anyway. Thanks and cheers.