Related
To downgrade your HBOOT to go back to 2.2 visit this link http://forum.xda-developers.com/showthread.php?t=1255474
This will allow you to flash 2.2 to perm root the phone
If you wish to help with perm root status for Android 2.3.3, please visit this thread http://forum.xda-developers.com/showthread.php?t=1218580
Thanks to everyone in this post who has helped get this far. You will need to have the Android SDK installed and working knowledge of ADB and basic file system structure.
Major help from minneyar
TEMP ROOT Instructions:
Download http://tinyw.in/1lI
Unzip if required and put in your ADB folder
Launch command prompt and navigate to your ADB folder
adb push fre3vo /data/local/tmp/
adb shell
chmod 777 /data/local/tmp/fre3vo
/data/local/tmp/fre3vo -debug -start fbb58a00 -end FFFFFFFF (if this doesn't work, try rebooting phone)
Download these 2 files here and put them in your ADB directory: http://forum.xda-developers.com/showthread.php?p=14927732#post14927732
exit back to command prompt if you aren't there already
adb push Superuser3-beta1.apk /data/app/
adb push su-3.0-alpha7 /data/local/tmp
adb shell (should now see # instead of $)
cd /data/local/tmp
chmod 777 su-3.0-alpha7
./su-3.0-alpha7
cd /
mount -o remount,rw -t rootfs rootfs /
rm vendor
mkdir vendor
mkdir vendor/bin
cat /data/local/tmp/su-3.0-alpha7 > /vendor/bin/su
chmod 4755 /vendor/bin/su
You now have temp root. Disregard any notification about outdated SU binary. Root will go away if you reboot. If you reboot your phone you can obtain root again by just running the following
adb shell
chmod 777 /data/local/tmp/fre3vo
/data/local/tmp/fre3vo -debug -start fbb58a00 -end FFFFFFFF
adb shell (should now see # instead of $)
cd /data/local/tmp
chmod 777 su-3.0-alpha7
./su-3.0-alpha7
cd /
mount -o remount,rw -t rootfs rootfs /
rm vendor
mkdir vendor
mkdir vendor/bin
cat /data/local/tmp/su-3.0-alpha7 > /vendor/bin/su
chmod 4755 /vendor/bin/su
I haven't found a way to re-root after rebooting without connecting to a PC
Type su and see if it gives you root permissions
Sent from my MiuiSpeedy
says su: not found.
You are saying you cannot install the superuser app? From reading in the Evo3D forums, you could install Superuser, even without being rooted, but it obviously won't allow root access, until you run a root exploit.
Try rebooting the phone, installing superuser, run fre3vo, and then try the adb shell, and su method.
This is getting interesting. Hopefully you are on to something.
Stuke00 said:
See screenshot. Doesn't the # mean temp rooted? Tho I cannot install SU and Root Explorer isn't working. Anything else I need to do first or something?
Click to expand...
Click to collapse
Looks hopeful!
tokuzumi said:
You are saying you cannot install the superuser app? From reading in the Evo3D forums, you could install Superuser, even without being rooted, but it obviously won't allow root access, until you run a root exploit.
Try rebooting the phone, installing superuser, run fre3vo, and then try the adb shell, and su method.
This is getting interesting. Hopefully you are on to something.
Click to expand...
Click to collapse
Okay let me clarify
I can install SU but it wouldn't install the binaries. I did all of the above. Says su: not found.
I then tried something else.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cat /system/bin/sh > /system/bin/su
# chmod 4755 /system/bin/su
I was then able to get the SU binaries to install but Titanium Backup says:
"Busybox works but the "su" command does not elevate to root: "whoami" reports "app_135" instead of root/uid 0.
then su from the command prompt was saying "link_image[1935]: 3160 missing essential tablesCANNOT LINK EXECUTABLE" and now back to su: not found again....
I don't know enough about linux commands to give you any real info. Like in the other thread, talk to agrabren, to see what he has to say.
tokuzumi said:
I don't know enough about linux commands to give you any real info. Like in the other thread, talk to agrabren, to see what he has to say.
Click to expand...
Click to collapse
Yeah I tweeted him with what I could provide with 160 characters. Just waiting now.
Well here's a tweet he put out a couple of hours ago.
@agrabren: For those with the SHIFT, it's a known bug in my code that we missed the address. One too many zeroes in the list. I'll try to fix it soon.
Sent from my PG06100 using XDA App
crump84 said:
Well here's a tweet he put out a couple of hours ago.
@agrabren: For those with the SHIFT, it's a known bug in my code that we missed the address. One too many zeroes in the list. I'll try to fix it soon.
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Yeah he posted that right after I gave him the memory address for the exploit. Just means that I did it the manual way through debugging. At least I think so... hopefully soon!
Good news, everybody! I have successfully acquired temp root on my Shift!
First, fre3vo has to be pointed at the right address. After copying it over to my phone, I did "adb shell" and then ran it like so:
/data/local/tmp/fre3vo -debug -start fbb58a00 -end FFFFFFFF
That printed out a message that it found an exploit and kicked me out of the shell. After doing "adb shell" again, I got a command prompt. I tried installing the 2.3.6.3 version of Superuser, but it complained about being unable to install "su"; I tried to find a separate su binary and copy it over manually, but it didn't work due to a linker error.
After searching around, I found a beta version of Superuser 3:
http://forum.xda-developers.com/showthread.php?p=14927732#post14927732
First I uninstalled the old version of Superuser and then used adb to install the new one from that thread. I ran it and it said it was unable to install su, so I downloaded the version of su provided there and installed it manually. The process went something like:
Code:
adb push su-3.0-alpha7 /data/local/tmp
adb shell
# cd /data/local/tmp
# chmod 4755 su-3.0-alpha7
# ./su-3.0-alpha7
# mount -o remount,rw -t ext3 /dev/block/mmcblk0p26 /system
# cat su-3.0-alpha7 > /system/bin/su
# chmod 4755 /system/bin/su
I don't know if explicitly running "./su-3.0-alpha7" is necessary, it just seemed like a good idea at the time. I don't know if everybody's block device will be named "mmcblk0p26", I used "mount" to figure out what was mounted at /system.
Anyway, after all that was done, I ran Superuser again and it didn't complain. To test it out, I started up Wireless Tether. It asked me for superuser permissions, which I granted it, and it's working fine.
Root successful!
Good job!!
Sent from my Speedy HTC EVO shift on XDA Premium app
I followed those steps exactly and got what I would call a partial root. Some of the 'you need root' errors are gone but "su" still results in 'not found' even though "mkdir su" results in 'file exists.'
mmcblk0p26 exists on this unit.
The weirdest part is that Adfree will accept the device as rooted and with superuser but says it can't find a partition to modify. And after a reboot root is definitely gone.
I think you're on to it but it isn't quite there yet.
It seems to be fully temprooted to me; I have to redo it if I reboot, but otherwise it's working perfectly. After following the steps I listed above, running "ls -l /system/bin/su" should produce this output:
Code:
# ls -l /system/bin/su
ls -l /system/bin/su
-rwsr-xr-x root root 22228 2011-07-25 19:14 su
If it says "No such file or directory" instead, then the su binary isn't in the right place.
Looking back over what I wrote, I think I left out a step -- if you were following what I listed exactly, it probably won't work, because I forgot to change to the /data/local/tmp directory. I'll update that...
Update: after playing around with it for a while, something is definitely not quite right. Everything works fine at first; I've tested Wireless Tether and Titanium Backup and they're both fine. After leaving my phone for a while and coming back, though, applications that try to get root access mysteriously fail. The dialog prompt doesn't even appear.
Going back into the adb shell, /system/bin/su is still there, but trying to run "su" causes this to happen:
Code:
# su
su
link_image[1935]: 3802 missing essential tablesCANNOT LINK EXECUTABLE
But if I use cat to overwrite su and then chmod it again, everything works. su must somehow be getting modified by something else and replaced with a bad version... but I'm not sure where to look.
I caught something like that.
I think there should be a chmod 777 su-3.0-alpha7 after cd /data/local/tmp
minneyar said:
It seems to be fully temprooted to me; I have to redo it if I reboot, but otherwise it's working perfectly. After following the steps I listed above, running "ls -l /system/bin/su" should produce this output:
Code:
# ls -l /system/bin/su
ls -l /system/bin/su
-rwsr-xr-x root root 22228 2011-07-25 19:14 su
If it says "No such file or directory" instead, then the su binary isn't in the right place.
Looking back over what I wrote, I think I left out a step -- if you were following what I listed exactly, it probably won't work, because I forgot to change to the /data/local/tmp directory. I'll update that...
Update: after playing around with it for a while, something is definitely not quite right. Everything works fine at first; I've tested Wireless Tether and Titanium Backup and they're both fine. After leaving my phone for a while and coming back, though, applications that try to get root access mysteriously fail. The dialog prompt doesn't even appear.
Going back into the adb shell, /system/bin/su is still there, but trying to run "su" causes this to happen:
Code:
# su
su
link_image[1935]: 3802 missing essential tablesCANNOT LINK EXECUTABLE
But if I use cat to overwrite su and then chmod it again, everything works. su must somehow be getting modified by something else and replaced with a bad version... but I'm not sure where to look.
Click to expand...
Click to collapse
YES! I have root! I was able to install a screenshot app and test it this is amazing progress! Thanks for that.
So now when I reboot, you have to do the entire thing again? SU and all?
Stuke00 said:
So now when I reboot, you have to do the entire thing again? SU and all?
Click to expand...
Click to collapse
Yes, every time you reboot you'll have to redo the whole process, including running fre3vo and then copying su into /system/bin. Hopefully somebody will figure out a permanent root soon.
Wow those SU binaries are disappearing before I even reboot! Already gone and I haven't rebooted the phone
I think I had that issue too. I just couldn't believe the files just disappeared and thought I did something wrong somewhere.
Would a logcat help anyone at all? Anything I should look for?
Hello everyone...
I have a Motorola RAZR 201M(XT902) in Japan and use Motofail2go to root it.But it doesn't work.
(follow http://forum.xda-developers.com/showthread.php?p=32889627)
I installed Sudoku.apk and push the motofail2go to the device(also su,Superuser.apk,busybox).
when
$ run-as com.motorola.bug2go /data/local/tmp/motofail2go prep2
Here is the error message:
"run-as: exec failed for /data/local/tmp/motofail2go Error: Operation not permitted"
and i try $ run-as com.motorola.bug2go
but error message : "run-as: exec failed"
Anyone help? Thanks...
Sorry buddy. Nothing works. We 201m users are SOL.
Have you tried this?
http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit/
Thanks Paul!
No luck with that either. Appreciate the feedback, however.
I hope somebody will study the XT902 root.
goodayoo said:
I hope somebody will study the XT902 root.
Click to expand...
Click to collapse
I really want this thing rooted. How do one go about figuring out how to root it? I assume because of it's lack of popularity, no one has done it, but I'm willing to do the grunt work if there's some sort of guide or assistance. I changed over to DoCoMo with the GS4 and now have this paperweight that I would want to actually use.
Thanks!
Almalieque said:
I really want this thing rooted. How do one go about figuring out how to root it? I assume because of it's lack of popularity, no one has done it, but I'm willing to do the grunt work if there's some sort of guide or assistance. I changed over to DoCoMo with the GS4 and now have this paperweight that I would want to actually use.
Thanks!
Click to expand...
Click to collapse
There some Japanese guys doing some things to try and get root. They are active. The site has a lot of rather unpleasant (read offensive) advertisements. PM if you are interested (its in Japanese)
root
help!!!
Root and Unlocked bootloaders!
Proceed at yor own risk
hungln03 said:
help!!!
Click to expand...
Click to collapse
1)Prep
Android SDKと各種ドライバを導入する。
以下の必要ファイルをC:\***（何でも良い）に配置する。
・XT902_SBMの中身(http://www1.axfc.net/uploader/so/2991543 >>125氏)
・su（http://www1.axfc.net/uploader/so/2918729 password：f10d）
・Superuser.apk（in the above downloaded）
・busybox（in the above downnloaded）
201M Plug the phone into the comp
any port will do
2)adb pushで必要ファイルを/data/local/tmp転送
コマンドプロンプトを開く
C:\Users\（ユーザー名） >cd C:\***
adb push su /data/local/tmp
adb push Superuser.apk /data/local/tmp
adb push busybox /data/local/tmp
adb push unlock_security_module /data/local/tmp
adb push break_setresuid /data/local/tmp/
adb push mole-plough-ccsecurity.so /data/local/tmp/
adb push mole-plough-lsm.so /data/local/tmp/
3)unlock_security_module（temp root）
adb shell
[email protected]:/ $ cd /data/local/tmp/
[email protected]:/data/local/tmp $ chmod 777 *
[email protected]:/data/local/tmp $ ./unlock_security_module
[email protected]:/data/local/tmp $ ./break_setresuid
（unlock_security_moduleが動いてMIYABIとNANDロック解除）
（色々表示されるので↓が出る間で待つ）
Unlocked LSM.
Do setresuid...
OK.
[email protected]:/data/local/tmp #
（#if done correctly temp root should be achieved）
271 ：270：2013/09/15(日) 23:31:42.67 ID:tIg7fkl6
4)system putting together su，Superuser.apk，busybox
[email protected]:/data/local/tmp # mount -o rw,remount /system /system
[email protected]:/data/local/tmp # cat /data/local/tmp/su > /system/xbin/su
[email protected]:/data/local/tmp # cat /data/local/tmp/busybox > /system/xbin/busybox
[email protected]:/data/local/tmp # cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
[email protected]:/data/local/tmp # chmod 644 /system/app/Superuser.apk
[email protected]:/data/local/tmp # cd /system/xbin
[email protected]:/system/xbin # chown root.root su
[email protected]:/system/xbin # chown root.root busybox
[email protected]:/system/xbin # chmod 6755 su
[email protected]:/system/xbin # chmod 755 busybox
[email protected]:/system/xbin # mount -o ro,remount /system /system
After the opperation is done it is ok to remove the cable from the pc。
check and see if「SuperSU」was installed if it wasn't download chainfire (su) from the play store
⇒SU --> update
Fro the play store download busybox。
⇒busybox -->update
Get the right CWM.img http://forum.xda-developers.com/showthread.php?t=2298521の201M
put the CWM.img you downloaded in motoapoc file you find here
adb push unlock /data/local/tmp/
adb shell chmod 755 /data/local/tmp/unlock
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
./unlock
New Command prompt
5)Inserting CWM(PC Operation)
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak'"
adb shell "su -c 'mv /system/recovery-from-boot.p /system/recovery-from-boot.bak'"
adb push cwm.img /data/local/tmp/cwm.img > nul
adb shell "su -c 'dd if=/data/local/tmp/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'"
adb shell "su -c 'rm /data/local/tmp/cwm.img'"
adb reboot recovery
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
I don't own the 902, but it's good to see this. I know quite a few people have been looking for this. You should start your own thread with the procedures, so it will get more publicity.
Thank u!
thank u so much.!1
sbeaber4 said:
Proceed at yor own risk
271 ：270：2013/09/15(日) 23:31:42.67 ID:tIg7fkl6
Get the right CWM.img http://forum.xda-developers.com/showthread.php?t=2298521の201M
put the CWM.img you downloaded in motoapoc file you find here
adb push unlock /data/local/tmp/
adb shell chmod 755 /data/local/tmp/unlock
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
./unlock
New Command prompt
5)Inserting CWM(PC Operation)
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak'"
adb shell "su -c 'mv /system/recovery-from-boot.p /system/recovery-from-boot.bak'"
adb push cwm.img /data/local/tmp/cwm.img > nul
adb shell "su -c 'dd if=/data/local/tmp/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'"
adb shell "su -c 'rm /data/local/tmp/cwm.img'"
adb reboot recovery
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
Click to expand...
Click to collapse
Can you tell me more about this step
Confirm?
Can confirm if the latest instructions have worked for your 201m?
That your rooted and bootloader unlock.
Thanks a bunch!
Boot loader is unlocked and CWM is installed. Initially I still
Had temp root so I flashed slim beans xt907 rom. It works. I'm unable to test data with it as I don't have a SoftBank sim. Also I still can't connect to the play store.
sbeaber4 said:
Boot loader is unlocked and CWM is installed. Initially I still
Had temp root so I flashed slim beans xt907 rom. It works. I'm unable to test data with it as I don't have a SoftBank sim. Also I still can't connect to the play store.
Click to expand...
Click to collapse
Thanks for the feedback.
Still awaiting more confirmation with others. It's a step forward though.
I've had my phone for almost a year now. If I cancel my softbank service or run the contract to the end I want an option to root and unlock the bootloader in the future.
could u provide more friendly filehost?
i can't find the download button there
Root! (temp root that is...)
I'm just posting to confirm I've rooted my 201m (xt902).
Props to sbeaber4!
From my limited knowledge since it's temp root if I restart my phone I lose root access...
Next step in the future unlock bootloader.
Peace y'all.
Quick Tip
zenstarlight said:
I'm just posting to confirm I've rooted my 201m (xt902).
Props to sbeaber4!
From my limited knowledge since it's temp root if I restart my phone I lose root access...
Next step in the future unlock bootloader.
Peace y'all.
Click to expand...
Click to collapse
Found that if I a did restart my phone root was lost but I found a quick fix without going through the whole process again.
Just do these steps
unlock_security_module（temp root）
adb shell
[email protected]:/ $ cd /data/local/tmp/
[email protected]:/data/local/tmp $ ./unlock_security_module
Just enter those three steps then you're back to temp root
Also you can just to a quick reboot with link2sd or any other app that just reboots the android ui. You don't have to enter commands every time you reboot unless it's a full reboot.
Help for Gaigin rooting 201M
sbeaber4 said:
Proceed at yor own risk
...
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
Click to expand...
Click to collapse
Noob on XDA, and rooted a MT4G in the past wth help from these forums.
Can someone help translate the kanji for rooting the 201M? Will rooting allow you to change the device location and prevent random all Japanese pop-up alerts/"are you sure" messages? Thanks for any help
kprower said:
Noob on XDA, and rooted a MT4G in the past wth help from these forums.
Can someone help translate the kanji for rooting the 201M? Will rooting allow you to change the device location and prevent random all Japanese pop-up alerts/"are you sure" messages? Thanks for any help
Click to expand...
Click to collapse
Once CWM is online you might be able to flash a VZW or Aussie stock ROM. Actually, you could probably flash CM... That'll fix the Japanese popups. Of course, it also could very possibly brick it. Proper precautions must be made... On my tablet at the moment, does anyone know if sbf.droid-developers has 902 images?
Sent from my Nexus 7 using Tapatalk 4
Hi, I need to downgrade to 4.2.2 but I can not acces download mode. It just says "download mode" and nothing else happens so I cant flash the .kdz file. I can boot recovery (TWRP). I cant find a working solution anywhere.
Thanks
Turn off the device, press volume up, plug in the cable at the same time, it will enter download mode.
I tried it many times. It wont. As I said, it just says "download mode" but it wont continue to the "firmware update" part..
What is your current firmware version?4.4.2 ?
Same thing here buddy
Yes. I had 4.2.2 but I tried ported kitkat. Then I flashed the old recovery, tried to restore the backup and nothing is working. So I need to unroot it but I cannot
get to that mode. What a mystery.
Here you need to do is write in detail. I've solved this issue by examining. Your solution is here.LG has closed since way back.
http://forum.xda-developers.com/showthread.php?t=2432476
---------- Post added at 01:00 AM ---------- Previous post was at 12:56 AM ----------
I've given subject solves your problem.
Im not sure if I understand. I was already aware of that guide. Thats why I need to boot "download mode" which I cant. I cant find there the solution. I also cant boot the system.
I just tried to connect flash disk via OTG and the phone does not see it in recovery. In other phone it works. So another way is out. I either need to get the download mode working or push .zip into the phone but I have no idea how since the OTG is not working.
adb push g2_security /sdcard/
adb root
adb push loki_patch /data/local/tmp
adb push loki_flash /data/local/tmp
adb push recovery.img /data/local/tmp
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img"
adb shell "chmod 644 /data/local/tmp/aboot.img"
adb shell "chmod 755 /data/local/tmp/loki_patch"
adb shell "chmod 755 /data/local/tmp/loki_flash"
adb shell "/data/local/tmp/loki_patch recovery /data/local/tmp/aboot.img /data/local/tmp/recovery.img /data/local/tmp/recovery.lok"
adb shell "/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok"
adb shell "rm /sdcard/g2_security"
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img"
adb shell "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota"
adb shell sync
adb reboot recovery
i will post the file soon
---------- Post added at 05:27 PM ---------- Previous post was at 05:22 PM ----------
mastercut said:
adb push g2_security /sdcard/
adb root
adb push loki_patch /data/local/tmp
adb push loki_flash /data/local/tmp
adb push recovery.img /data/local/tmp
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img"
adb shell "chmod 644 /data/local/tmp/aboot.img"
adb shell "chmod 755 /data/local/tmp/loki_patch"
adb shell "chmod 755 /data/local/tmp/loki_flash"
adb shell "/data/local/tmp/loki_patch recovery /data/local/tmp/aboot.img /data/local/tmp/recovery.img /data/local/tmp/recovery.lok"
adb shell "/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok"
adb shell "rm /sdcard/g2_security"
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img"
adb shell "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota"
adb shell sync
adb reboot recovery
i will post the file soon
Click to expand...
Click to collapse
here: http://rg.to/file/1d38237a286593c5385f2a2108c021c8/fixg2.7z.html
Thank you so much. A will try it immediately.
SOLVED!!! Thanks very much..
I hereby discontinue support for my Fire TV Guides and Apps. I've been a big fan of Fire TV devices for the last 2-3 years, but Amazon has now with each firmware further limited the possibilities of a configurable Android environment and even destroyed standard Android commands. This goes too far for me now.
I can recommend the following devices to anyone who wants to have a reasonable and much better Android TV experience, which I now use myself and am enthusiastic about:
Mi Box
Mi Box S
Sony Android TV (ATV3 platform, eg. XF7, XF8, XF9 or higher)
Will be trying this tomorrow, thankyou
Awesome a new project for tomorrow. Thanks for all your hard work.
rainman74 said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The following steps installs the newest Leanback Launcher with Recommendations, Chromecast integrated, Daydream and activates the Google Voice Search with Google Assistant so that it also can be used in a current Kodi 18 Nightly Build on a Fire TV.
This is the most comprehensive and up-to-date transformation of a Fire TV into an Android TV device with almost all Google functionalities usable.
Amazon TV Launcher and Amazon Alexa voice search are completely replaced by Leanback Launcher and Google Voice Search. Xposed edge, XInstaller and HDXPosed must also be installed and activated. Before installing it is recommended to make a backup of the system and data partition via TWRP if you have connected an external sdcard. Many thanks to @SimLynks for some tips from his PlayFire modification and to @peleg for his wonderful [project] aftv2atv.
This manual is only possible with a rooted device!
Tested on a rooted Fire TV 4k box
Firmware 5.2.6.2
Instructions:
Unpack all zip files and copy all apk in the appendix to C:\adb\
1. Disabling unnecessary and blocking Amazon junk
Code:
adb shell su -c pm disable amazon.jackson19
adb shell su -c pm disable com.amazon.acos.providers.UnifiedSettingsProvider
adb shell su -c pm disable com.amazon.advertisingidsettings
adb shell su -c pm disable com.amazon.ags.app
adb shell su -c pm disable com.amazon.application.compatibility.enforcer
adb shell su -c pm disable com.amazon.application.compatibility.enforcer.sdk.library
adb shell su -c pm disable com.amazon.avod
adb shell su -c pm disable com.amazon.bueller.music
adb shell su -c pm disable com.amazon.bueller.notification
adb shell su -c pm disable com.amazon.bueller.photos
adb shell su -c pm disable com.amazon.client.metrics
adb shell su -c pm disable com.amazon.client.metrics.api
adb shell su -c pm disable com.amazon.communication.discovery
adb shell su -c pm disable com.amazon.device.sale.service
adb shell su -c pm disable com.amazon.device.software.ota
adb shell su -c pm disable com.amazon.device.software.ota.override
adb shell su -c pm disable com.amazon.device.sync
adb shell su -c pm disable com.amazon.device.sync.sdk.internal
adb shell su -c pm disable com.amazon.imp
adb shell su -c pm disable com.amazon.kindle.cms
adb shell su -c pm disable com.amazon.kor.demo
adb shell su -c pm disable com.amazon.logan
adb shell su -c pm disable com.amazon.metrics.api
adb shell su -c pm disable com.amazon.ods.kindleconnect
adb shell su -c pm disable com.amazon.recess
adb shell su -c pm disable com.amazon.tahoe
adb shell su -c pm disable com.amazon.tcomm.client
adb shell su -c pm disable com.amazon.tv.csapp
adb shell su -c pm disable com.amazon.tv.launcher
adb shell su -c pm disable com.amazon.tv.launcher/.ui.HomeActivity_vNext
adb shell su -c pm disable com.amazon.tv.legal.notices
adb shell su -c pm disable com.amazon.tv.nimh
adb shell su -c pm disable com.amazon.tv.settings/com.amazon.tv.settings.tv.AppDisableService
adb shell su -c mount -o remount,rw /system
adb shell su -c rm -r /system/priv-app/com.amazon.vizzini
adb shell su -c rm -r /system/priv-app/WhisperplayCore
adb shell su -c rm -r /system/priv-app/WhisperplayInstall
adb shell su -c mount -o remount,ro /system
(Notice: Amazon Alexa and Wisperplay will be completely deleted to make room on the system partition for Chromecast Integrated.)
2. Customize build.prop
View attachment 4481935
Code:
adb shell su -c mount -o remount,rw /system
adb push C:\adb\mod-build.prop.sh /sdcard/
adb shell su -c sh /sdcard/mod-build.prop.sh
adb shell su -c rm /sdcard/mod-build.prop.sh
adb shell su -c mount -o remount,ro /system
3. Adjust permissions for voice recognition
View attachment 4481936
Code:
adb shell su -c mount -o remount,rw /system
adb push C:\adb\tv_core_hardware.xml /sdcard/
adb shell su -c cp /sdcard/tv_core_hardware.xml /system/etc/permissions/tv_core_hardware.xml
adb shell su -c chmod 644 /system/etc/permissions/tv_core_hardware.xml
adb shell su -c chown root:root /system/etc/permissions/tv_core_hardware.xml
adb shell su -c rm /sdcard/tv_core_hardware.xml
adb shell su -c mount -o remount,ro /system
4. Install Open Google apps for Android TV
Download the matching zip file and copy it to the sdcard (I use version open_gapps-arm64-5.1-tvstock-20180423).
Open GApps for ARM (Fire TV sticks)
Open GApps for ARM64 (Fire TV boxes)
Insert this code to new "gapps-config.txt" and copy it to the same directory as the GApps on the sdcard.
Code:
forceclean
skipswypelibs
skipvendorlibs
GoogleAssistant
+extsharedstock
+keyboardstock
+provision
+packageinstallerstock
+webviewstock
+notouchauthdelegate
Include
gappspico
backdrop
#castreceiver
configupdater
googlebackuptransport
googlecontactsync
gsfcore
leanbacklauncher
overscan
secondscreenauthbridge
secondscreensetup
tvcustomization
tvetc
tvframework
tvgmscore
tvkeyboardgoogle
tvvending
tvwallpaper
tvwidget
Then install the GApps zip via TWRP and restart the device. Please don't sign up for Google Play Store yet!
5. Allow Google registration (NoTouchAuthDelegate)
View attachment 4481943
Code:
adb shell su -c mount -o remount,rw /system
adb push C:\adb\Tv-NoTouchGsf.apk /sdcard/
adb shell su -c chmod 755 /system/app/NoTouchAuthDelegate/
adb shell su -c rm /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk
adb shell su -c cp /sdcard/Tv-NoTouchGsf.apk /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk
adb shell su -c chmod 644 /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk
adb shell su -c chown root:root /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk
adb shell su -c rm /sdcard/Tv-NoTouchGsf.apk
adb shell su -c mount -o remount,ro /system
6. Install Google app to enable voice recognition (com.google.android.katniss)
Now restart the device and then sign in to Google Play Store.
Then search for and install the "Google" app on the Play Store. It'll take a while (I use current Google 2.2.0.138699360).
(Notice: The search in the Play Store does not work with the search button on the remote!)
7. Adjust the Xposed edge key configuration for the search button of the Fire TV remote
Activate the "Keys" in the Xposed edge and add the new KEYCODE_SEARCH key (simply press the search key on the Fire Remote for recognition).
Use "Single Click" with the activity "com.google.android.katniss\.search.SearchActivity" and leave "Long press" empty. This is the standard function, you first have to click and release the microphone, wait until the input is ready ("Speak Now" appears), and then press and hold the microphone and speak, then release.
More useful key assignments for the Leanback Launcher see attached photos:
View attachment 4488212View attachment 4488213View attachment 4488214View attachment 4488215
8. Install Android TV Settings modified for Fire TV
Once you have installed the aftv2atv Fire TV settings (better than the modified settings apk from PlayFire), you can choose which apps the Google Assistant is allowed to search for hits.
View attachment 4488216
Code:
adb shell su -c mount -o remount,rw /system
adb push C:\adb\TvSettings-2.1.1.apk /sdcard/
adb shell su -c cp /sdcard/TvSettings-2.1.1.apk /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c chmod 644 /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c chown root:root /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c rm /sdcard/TvSettings-2.1.1.apk
adb shell su -c mount -o remount,ro /system
9. Finish
Reboot for the last time.
That's all and now you will boot directly in Leanback Launcher and start the voice search by pressing the search button in Leanback Launcher and Kodi.
Google Assistant also now finds hits in Kodi (movies, tv shows and music, if Kodi already is running), along with other sources such as YouTube, Spotify, etc. (directly install these apps from Google Play Store)
10. Optional: Access Amazon settings
If you still need to access the Amazon settings, you can install my modified conFIREator Settings app additionally (More details click here):
View attachment 4488238
Known issues
Although the cast receivers are displayed and found correctly, no device could connect. Looks like Google has something here against unlicensed cast receivers.
.
Click to expand...
Click to collapse
After step 5 your guide says install the google app, when i log into google and search for the app it wont let me install it ? i get error code 0
sconnyuk said:
After step 5 your guide says install the google app, when i log into google and search for the app it wont let me install it ? i get error code 0
Click to expand...
Click to collapse
Did you already have an older version installed? Then simply uninstall them before.
rainman74 said:
Did you already have an older version installed? Then simply uninstall them before.
Click to expand...
Click to collapse
brand new install of latest fire tv2 rom. clean slate and following your guide.
---------- Post added at 05:12 PM ---------- Previous post was at 05:11 PM ----------
ive just tried again, im up to instaaling gapps and waiting on optomising
---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------
rainman74 said:
Did you already have an older version installed? Then simply uninstall them before.
Click to expand...
Click to collapse
no, ive just formatted and installed latest rom (fire tv2) and folowing as a clean slate.
---------- Post added at 05:15 PM ---------- Previous post was at 05:14 PM ----------
rainman74 said:
Did you already have an older version installed? Then simply uninstall them before.
Click to expand...
Click to collapse
can you tell me what i need to do after step 5 ? it says install google app but it isnt included in your guide ? thanks
sconnyuk said:
can you tell me what i need to do after step 5 ? it says install google app but it isnt included in your guide ? thanks
Click to expand...
Click to collapse
then sideload Google App 2.2.0
rainman74 said:
then sideload Google App 2.2.0
Click to expand...
Click to collapse
its asking for decription key ?
sconnyuk said:
its asking for decription key ?
Click to expand...
Click to collapse
Link with key
rainman74 said:
Link with key
Click to expand...
Click to collapse
Thanks for all the help but after i install that and go sign into google store, search google and try install i get error code 0 again, no matter what i try install i get trhe same error code, any idea ?
sconnyuk said:
Thanks for all the help but after i install that and go sign into google store, search google and try install i get error code 0 again, no matter what i try install i get trhe same error code, any idea ?
Click to expand...
Click to collapse
Code:
adb shell
chown -R media_rw:media_rw /data/media/
find /data/media/ -type d -exec chmod 775 {} ‘;’
find /data/media/ -type f -exec chmod 664 {} ‘;’4)
rainman74 said:
Code:
adb shell
chown -R media_rw:media_rw /data/media/
find /data/media/ -type d -exec chmod 775 {} ‘;’
find /data/media/ -type f -exec chmod 664 {} ‘;’4)
Click to expand...
Click to collapse
Thanks, im restoring my backup at the moment, what will this code do ? i dont get any reccomendations and i cant see any setting icons on my home screen either, will this fix those issues too ?
sconnyuk said:
Thanks, im restoring my backup at the moment, what will this code do ? i dont get any reccomendations and i cant see any setting icons on my home screen either, will this fix those issues too ?
Click to expand...
Click to collapse
restoring permissions, that is a possible solution for Error 0
rainman74 said:
restoring permissions, that is a possible solution for Error 0
Click to expand...
Click to collapse
no, restoring my backup from twrp. im going to give it 3rd and final go see if i can get it working
sconnyuk said:
no, restoring my backup from twrp. im going to give it 3rd and final go see if i can get it working
Click to expand...
Click to collapse
Best luck! I have tested my guide on 4 Fire TVs... I've never got Error 0.
rainman74 said:
Best luck! I have tested my guide on 4 Fire TVs... I've never got Error 0.
Click to expand...
Click to collapse
Ok, so i seem to have got a littel further this time, i can now install from playstore and reccomendations work (sometimes) but, i cannot see any settings icon ? and obviously my original settings are disabled.
Also i cant see my sideloaded apps anywhere or even know where to access them from ? can you shed any light on this for me please ?
sconnyuk said:
Ok, so i seem to have got a littel further this time, i can now install from playstore and reccomendations work (sometimes) but, i cannot see any settings icon ? and obviously my original settings are disabled.
Also i cant see my sideloaded apps anywhere or even know where to access them from ? can you shed any light on this for me please ?
Click to expand...
Click to collapse
Is it possible that you have not configured XInstaller correctly? Please send me screenshots of your XPosed modules and one screenshot of each XInstaller area. If the settings do not appear at the bottom of the launcher, you have not installed the Settings.apk correctly. Please scroll down in the launcher and take a screenshot.
To access all apps, press and hold the Menu key, then the app bar opens with all (even the non-leanback) apps. To do this, however, you must have configured all keys as specified in Xposed edge.
rainman74 said:
Is it possible that you have not configured XInstaller correctly? Please send me screenshots of your XPosed modules and one screenshot of each XInstaller area. If the settings do not appear at the bottom of the launcher, you have not installed the Settings.apk correctly. Please scroll down in the launcher and take a screenshot.
To access all apps, press and hold the Menu key, then the app bar opens with all (even the non-leanback) apps. To do this, however, you must have configured all keys as specified in Xposed edge.
Click to expand...
Click to collapse
Yes I've not configured xinstaller as I can't find the app xinstaller to launch. I have managed to get as far as installing settings and running all commands but I do not see any settings. If there was a way to select xinstaller I might be able to progress?
sconnyuk said:
Yes I've not configured xinstaller as I can't find the app xinstaller to launch. I have managed to get as far as installing settings and running all commands but I do not see any settings. If there was a way to select xinstaller I might be able to progress?
Click to expand...
Click to collapse
Launch the Xposed Installer
- Click on the three lines in the top left corner of the screen
- Click on Modules
- Click the check box to activate XInstaller (use Mouse Toogle for Fire TV)
Restart the Fire TV
Launch the Xposed Installer again
- Click on Modules again
- Click on XInstaller
In XInstaller click on XInstaller first
- Check Expert mode
- Press the back arrow
In the Installations page, in the "Enable" section, check the boxes for:
- Downgrading apps
- Installing unknown apps
- Then scroll down to the "Disable" section and check the boxes for:
- Checking signatures
- Checking signatures (F-Droid)
- Forward locking
- Verifying apps
- Checking SDK version
- Checking duplicated permissions
- Press the back arrow
In the Misc page, in the "Enable" section, check the box for:
- Debugging apps
- Then scroll down to the "Disable" section and check the boxes for:
- Checking permissions
- Verifying JAR
- Verifying signatures
- Checking Lucky Patcher
- Auto updating Google Play
Exit the program
rainman74 said:
Launch the Xposed Installer
- Click on the three lines in the top left corner of the screen
- Click on Modules
- Click the check box to activate XInstaller (use Mouse Toogle for Fire TV)
Restart the Fire TV
Launch the Xposed Installer again
- Click on Modules again
- Click on XInstaller
In XInstaller click on XInstaller first
- Check Expert mode
- Press the back arrow
In the Installations page, in the "Enable" section, check the boxes for:
- Downgrading apps
- Installing unknown apps
- Then scroll down to the "Disable" section and check the boxes for:
- Checking signatures
- Checking signatures (F-Droid)
- Forward locking
- Verifying apps
- Checking SDK version
- Checking duplicated permissions
- Press the back arrow
In the Misc page, in the "Enable" section, check the box for:
- Debugging apps
- Then scroll down to the "Disable" section and check the boxes for:
- Checking permissions
- Verifying JAR
- Verifying signatures
- Checking Lucky Patcher
- Auto updating Google Play
Exit the program
Click to expand...
Click to collapse
Thanks for that, its working now.
I have recomendations come up correctly, i can see and use my settings now and its now setup better than i had previously.
One question, how to make my sideloaded apps show on the homescreen ? or isnt this possible ?
Thanks for your help and for putting this together.
I have bought a new, stock Sony Xperia X Compact from a Chinese online vendor. The cell phone can send SMS messages. I have tried to follow instructions on this forum to install a custom ROM, but i have not been able (i have found many expired links).
I offer 0.001 BTC = 1 mBTC (about 20 US$ at today's rate) for who can guide me to choose and install a custom ROM. My goal is to have a simple, secure, degoogled phone.
I have a Ubuntu PC and a Windows PC.
Start by reading
Info about suzu | LineageOS Wiki
wiki.lineageos.org
Install LineageOS on suzu | LineageOS Wiki
wiki.lineageos.org
Write if you don't understand something.
ok thanks.
I will read th link you provided
I have started to follow the instructions on a ubuntu PC.
see my log below.
I mark with the characters <<<< when something failed
--------------------------------------------------------
Info about suzu | LineageOS Wiki
wiki.lineageos.org
Get LineageOS for the Sony Xperia X
Get the builds here
Download lineage-18.1-20221021-recovery-suzu.img
lineage-18.1-20221021-recovery-suzu.imglineage-18.1-20221021-recovery-suzu.img
Install LineageOS on suzu | LineageOS Wiki
wiki.lineageos.org
Make sure your computer has adb and fastboot. Setup instructions can be found here.
Using ADB and fastboot | LineageOS Wiki
wiki.lineageos.org
Up to this point all OK. Now i follow:
5. You may also need to set up udev rules: see this repository for more info.
https://github.com/M0Rf30/android-udev-rules#installation
$ git clone https://github.com/M0Rf30/android-udev-rules.git
Cloning into 'android-udev-rules'...
remote: Enumerating objects: 1164, done.
remote: Counting objects: 100% (152/152), done.
remote: Compressing objects: 100% (67/67), done.
remote: Total 1164 (delta 91), reused 128 (delta 84), pack-reused 1012
Receiving objects: 100% (1164/1164), 300.93 KiB | 3.24 MiB/s, done.
Resolving deltas: 100% (521/521), done.
$ cd android-udev-rules
$ sudo cp -v 51-android.rules /etc/udev/rules.d/51-android.rules
'51-android.rules' -> '/etc/udev/rules.d/51-android.rules'
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
$ sudo cp android-udev.conf /usr/lib/sysusers.d/
$ sudo systemd-sysusers
Creating group adbusers with gid 998.
$ sudo gpasswd -a $(whoami) adbusers
Adding user XXX to group adbusers
$ sudo udevadm control --reload-rules
$ sudo systemctl restart systemd-udevd.service
$ adb kill-server
cannot connect to daemon at tcp:5037: Connection refused <<<<<
$
# Replug your Android device and ...
the instructions have not said before to plug my Android device ! <<<<<<<
Anyway i connect my android smartphone to my ubuntu PC with a USB cable.
# You should now see your device
Where should i see my device ? <<<<<<<
On the phone, enable developer options by clicking repeatedly on the android version number, and then in the developer options enable usb debugging.
Then, after plugging in the enabled phone with a usb cable from the PC, confirm the authentication option in the pop-up window.
After executing the command
Code:
adb devices
you will receive information about the device number, which means that you have established a connection with which to perform further actions.
ze7zez said:
On the phone, enable developer options by clicking repeatedly on the android version number, and then in the developer options enable usb debugging.
Then, after plugging in the enabled phone with a usb cable from the PC, confirm the authentication option in the pop-up window.
After executing the command
Code:
adb devices
you will receive information about the device number, which means that you have established a connection with which to perform further actions.
Click to expand...
Click to collapse
Thanks, your advice worked, and i have made progress. I have arrived to the point:
Unlocking the bootloader
Step 1: On the device, dial *#*#7378423#*#* (*#*#SERVICE#*#*) to launch the service menu.
Step 2: service info --> Config :
Rooting status : Bootloader unlock allowed: NO <<<<<
So my phone is not rooted. I will search XDA how to root it, however let me know if you recommend a specific page
Since there are several different models of Xperia X show command results:
adb shell getprop ro.build.fingerprint
adb shell getprop ro.semc.version.cust
adb shell getprop ro.semc.version.cust_revision
ze7zez said:
Since there are several different models of Xperia X show command results:
adb shell getprop ro.build.fingerprint
adb shell getprop ro.semc.version.cust
adb shell getprop ro.semc.version.cust_revision
Click to expand...
Click to collapse
$ adb shell getprop ro.build.fingerprint
docomo/SO-02J/SO-02J:8.0.0/34.4.B.1.129/2043362636:user/release-keys
$ adb shell getprop ro.semc.version.cust
1305-8403
$ adb shell getprop ro.semc.version.cust_revision
R11E
I'm sorry, but there is no known way to root the Xperia X Compact (SO-02J - Japanese version).
I advise you against experimenting on your model based on the thread:
How To root and Twrp X compact Docomo so-02j
hello friends, i'm having trouble for my root and twrp because i have so-02j version. I've followed the guides trying the genesis kernel, but it just makes a stop in the sony logo when booting. does my device have a chance to root twrp and...
forum.xda-developers.com
Removing bloatware from sony Xperia SO-02J on a non-rooted Cell phone.
Adapted from
Find package names searching the app on https://www.apkmirror.com/apk/
$ adb devices
List of devices attached
BH9080Z65U device
$ adb shell
SO-02J:/ $ am get-current-user
0
SO-02J:/ $
SO-02J:/ $ pm uninstall -k --user 0 apps.r.compass
Failure [not installed for 0]
SO-02J:/ $
// try to remove Suguden :
SO-02J:/ $ pm uninstall -k --user 0 com.nttdocomo.android.phonemotion
Success
SO-02J:/ $
// try to remove chrome:
SO-02J:/ $ pm uninstall -k --user 0 com.android.chrome
Success
// try to remove Docomo Disaster kit:
SO-02J:/ $ pm uninstall -k --user 0 jp.co.nttdocomo.saigaiban
Success
SO-02J:/ $
// remove docomo dmarket:
SO-02J:/ $ pm uninstall -k --user 0 com.nttdocomo.android.store
Success
SO-02J:/ $
// try to remove docomo Application Manager
130|SO-02J:/ $ SO-02J:/ $ pm uninstall -k --user 0 com.nttdocomo.android.applicationmanager
/system/bin/sh: SO-02J:/: not found
127|SO-02J:/ $
// try rm docomo mail 127|SO-02J:/ $ pm uninstall -k --user 0 jp.co.nttdocomo.carriermail
Success
SO-02J:/ $
// docomo data copy:
SO-02J:/ $ pm uninstall -k --user 0 com.nttdocomo.android.sdcardbackup
Success
SO-02J:/ $
// Now restart the phone and try it: OK.
// Continue :
SO-02J:/ $ pm uninstall -k --user 0 com.nttdocomo.android.dhome
Success
SO-02J:/ $ pm uninstall -k --user 0 com.facebook.katana
Success
SO-02J:/ $ pm uninstall -k --user 0 com.facebook.appmanager
Success
SO-02J:/ $ pm uninstall -k --user 0 com.google.android.videos
Success
SO-02J:/ $ pm uninstall -k --user 0 com.google.android.music
Success
SO-02J:/ $ pm uninstall -k --user 0 com.touchtype.swiftkey.beta
Failure [not installed for 0]
SO-02J:/ $ pm uninstall -k --user 0 com.sonymobile.entrance
Success
SO-02J:/ $ pm uninstall -k --user 0 com.sonymobile.assist
Success
SO-02J:/ $ pm uninstall -k --user 0 com.google.android.tts
Success
// Now restart the phone and try it: all OK.
try to unistall more docomo apps.
SO-02J:/ $ pm uninstall -k --user 0 com.nttdocomo.android.areamail
Success
Now try phone: cannot make or receive calls !!
Downloadl com.nttdocomo.android.areamail_11.00.00002-12610_minAPI18(nodpi)_apkmirror.com.apk from https://www.apkmirror.com/apk/ and install it on the phone.
Restart the phone.
I can make and receive calls.
Stop unintalling apps for the moment