• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Root for Fierce 2?

Worked for me first try.
 

Attachments

  • Screenshot_2015-05-14-08-45-53.png
    Screenshot_2015-05-14-08-45-53.png
    111.1 KB · Views: 139
I was able to get root access, but when i open up superuser it tells me that the superuser binary needs to be updated and to choose an installation method. It gives me the option to do a recovery install. Where do i go from here?
 
I've tried repeatedly with no success... Anyone want to native give a detailed account of what exactly you're doing...? I've tried the way it was posted... No luck still ... Done maybe 15 times
 
matx420 said:
I was able to get root access, but when i open up superuser it tells me that the superuser binary needs to be updated and to choose an installation method. It gives me the option to do a recovery install. Where do i go from here?
Click to expand...
you must use KINGUSER for now. any superuser from play store won't work. let me know if you are able to replace kinguser w/any other SU (be careful you may loose root trying it)good luck
....never give up never surrender.
 
Last edited:
I used chanocs way...

"It works Don't give up I'll try about five times before get it to work here are the steps I did
1.download the app and install it
2.run it, hit the root-blue button and wait. it will stat at 1% and so on it may reboot you phone about 17% no problem.
3.let the phone re-start and open the app again it will continue with it left 18% and on and on.
4.and the app it will stop and show you the android crying face or an orange envelope , no problem close the app and try again.
5.if the app show you the envelope an not the root blue button no problem.
6.go to settings >apps and look for the app kingroot open it and clean data/cache.
7.go back to the app and start all over again in till get rooted, it needs to go from 1% to 100% without rebooting .... even with the last build works (c6eupe0) metropcs.
good luck....never give up never surrender."
 
matx420 said:
Oh okay i didnt notice the kinguser app! Where do i go from here? Are there any roms for this device?
Click to expand...
this is just a TEMP ROOT is not full root yet. to use ROMS you need full root and I'm not there jet. but at list you can delete apps that you don't like to make more room, use lucky patcher ETC.
....never give up never surrender.
 
atomilluminati said:
All these people with success and no one to share the wealth with the how to?
Click to expand...
atomilluminati try to hard reset your phone and try again (by doing that you will loose all you data) so backup first.
1.power off you phone
2.press volume up and power buttons
3.when you hear a sound and see the alcatel logo release the buttons
4.the phone goes to system recovery
5.choose English by pressing the power button
6.then go to (wipe data/factory reset) and press power button.
7. after that's done go and follow the steps above all over again. good luck
....never give up never surrender.
 
quick question, when you're all temp rooted, do you still have /system locked? if so, here's a fix. (POSSIBLY, I havent managed to get king root to work on my fierce 2 so yeah. anyone who is temp rooted should try this.)



(Just saying, this is not my work. Credits to Jcase for doing this to the ZMAX.)

Using Kingroot 4.0, or whatever root exploit you have up your sleeve, gain root.

in android terminal or ADB Shell, input the following:

(if you're not root@draconis:/# then do "su")
root@draconis:/# id
uid=0(root) gid=0(root) context=u:r:init:s0

Ok GOOD we have root.

root@draconis:/# mount -o remount,rw /system
mount: Permission denied
(if you don't get any errors, this is good and you can write to system.)

What firmware are we on?
root@draconis:/# getprop ro.build.fingerprint
zte/P892T57/draconis:4.4.2/KVT49L/20140804.141306.18686:user/release-keys
(THIS WILL BE DIFFERENT FOR THE ONE TOUCH, THIS WAS THE ZMAX'S RESULTS!)
Ok good.

Lets use that backdoor we just talked about in the other post to make sure we can keep root through reboots

root@draconis:/# getprop ro.product.name
P892T57

(again, the zmax's, will vary for one touch. also, if you have _MPCS after, make sure to include it when setting the prop.)
root@draconis:/# setprop persist.sys.k P892T57 (Don't use that one, use whichever the result on your screen was.)
root@draconis:/# getprop persist.sys.k
P892T57 (make sure your result is the same as when you set it.)


(Now, i dont know if this is the same directory, but basically, find the directory that boot and recovery is in.)
root@draconis:/# cd /dev/block/platform/msm_sdcc.1/by-name/

Lets backup recovery

root@draconis:/dev/block/platform/msm_sdcc.1/by-name# dd if=recovery of=/sdcard/recovery.img

Lets write boot to recovery!

root@draconis:/dev/block/platform/msm_sdcc.1/by-name# dd if=boot of=recovery

root@draconis:/dev/block/platform/msm_sdcc.1/by-name# reboot recovery
^ If you boot into android, this is good.

Now, using ADB, you should have your backdoor working.

root@draconis:/# id
uid=0(root) gid=0(root) context=u:r:shell:s0

ehh the backdoor doesnt give the best context, but hey its enough to set selinux permissive

root@draconis:/# setenforce 0
root@draconis:/# getenforce
Permissive

root@draconis:/# mount -o remount,rw /system
root@draconis:/#

If my theory worked, you should have no errors like the ZMAX did.

Lets install supersu, cause the backdoor is only for adb.

root@draconis:/# exit

Jons-Mac-Pro:su jcase$ unzip UPDATE-SuperSU-v2.46.zip
Jons-Mac-Pro:su jcase$ adb push arm/su /data/local/tmp/su
1301 KB/s (133472 bytes in 0.100s)
Jons-Mac-Pro:su jcase$ adb push common/install-recovery.sh /data/local/tmp
136 KB/s (629 bytes in 0.004s)
Jons-Mac-Pro:su jcase$ adb shell
root@draconis:/# mount -o remount,rw /system
root@draconis:/# cat /data/local/tmp/su > /system/xbin/su
root@draconis:/# cat /data/local/tmp/su > /system/xbin/daemonsu root@draconis:/# cat /data/local/tmp/install-recovery.sh > /system/etc/install-recovery.sh
root@draconis:/# chmod 755 /system/xbin/su
root@draconis:/# chmod 755 /system/xbin/daemonsu
root@draconis:/# chmod 755 /system/etc/install-recovery.sh
root@draconis:/# reboot

Any time you want write to system, reboot to recovery. Want to flash an update, probably need to unroot and write back that recovery backup


again, this was Jcase's method for the ZMAX. make sure you read through this carefully and follow closely. You wouldn't want to mess your device up. However, since root method was the same Im thinking this method is the same too.
 
Glad to see progress being made. I hope you guys make perm root, this is a good phone that has yet to be rooted and maybe someone can make a 5.0 ROM with it. Keep up the good work
 
Also, tricks to get your device rooted are to clear cache and reinstall the king apps.

if it reboots you, dont touch your phone, let it open the app by itself and resume.

Another thing is download apps that will cause lag to your device. The way kingroot exploits the system is via a buffer overflow that temporarily makes system writable.
 
nutella1998 said:
I might try it soon. Any step by step video tutorials on how to do it?
Click to expand...
I can make one, i suppose. no promises though. im very busy.

ubigred said:
I need a "For dummies" version....
Click to expand...
All you really need is ADB installed (google it) and your device to be temp rooted. Im a noob with this stuff too and managed to do it myself!
You have all the commands needed, you just need adb installed and thats it.

adb shell = exactly like using android terminal
 
You must log in or register to reply here.
Back
Top Bottom