Develop Bugs

AT&T Fusion 2 U8665 Root - General/Q&A

I will be editing this post, and organizing everything, so stay put.
EDIT: I am no longer using my Fusion 2 as my primary phone, but I will still be able to update this thread. If you need any help, just post here, or shoot me a PM.
Links and Guides
Root your Fusion 2
Installing CWM 6
How to install CM7.2
Q&A
Q1.How do I root my phone?
A1.There are several ways to root your phone.
Shagerty's Guide
RoboticBuddy's Guide
Q2.How do I install a Custom Recovery?
A2. User Oct3178 has discovered that the Y201 CWM works with our U8665. Check out his post here, and follow "Installing CWM Recovery":
User Shagerty has made a step-by-step guide for installing CWM.
Oct3178's Post
Shagerty's guide
Q3. Are there any ROMs for my phone?
A3. The post in A2 gives you that answer. You can use Huawei Y200 ROMs for the U8665.
RFE has also dumped a pre-rooted stock ROM.
NEW:Shagerty has developed CM7.2 for this device. Please refer to the links above the Q&A.
Oct3178's Post
RFE's Post
Thanks to RFE, who made rooting the Fusion 2 possible!

RoboticBuddy said:
I have made this thread to compile all the posts on rooting/custom ROMs for the Fusion 2.
Q1. How do I root my device?
A. I have put all the necessary files together in one package for rooting. https://www.dropbox.com/s/lm11rrn3z5c2j6v/Huawei-Fusion-2-Recovery-Root.zip
Q2. Is there any Custom Recovery?
A. There is no CWM or TWRP as of now, but you can boot into CWM via fastboot. http://forum.xda-developers.com/showpost.php?p=36534284&postcount=4
Q3. Is there any Customs ROMs for this phone?
A. As of now, there are NO developed custom ROMs for this phone, yet. There is a pre-rooted stock ROM, for anybody who has a bricked phone. http://forum.xda-developers.com/showpost.php?p=36533895&postcount=46
Will add more later, when I have the time.
Thanks to RFE, who made rooting the Fusion 2 possible!
Click to expand...
Click to collapse
Thank you for creating such a nice organized thread in a good place. I've bricked a few phones now and just successfully flashed the FIRST FUSION2 ROM EVER. All that is required to apply the new ROM is fastboot & fastboot tools working.
Thanks,
RFE

RFE said:
Thank you for creating such a nice organized thread in a good place. I've bricked a few phones now and just successfully flashed the FIRST FUSION2 ROM EVER. All that is required to apply the new ROM is fastboot & fastboot tools working.
Thanks,
RFE
Click to expand...
Click to collapse
If you could, please PM me the Rom, so I can add it to the OP.
Thank you,
-RoboticBuddy

Hello, super fresh noob here. I bought the "AT&T Fusion 2 GoPhone" three days ago, and successfully used this method of gaining root access on my device. I am an experienced linux user/developer who just bought his first Android phone.. :laugh: Instead of trying to remove the factory installed components, would it be possible to build a custom version of basic/minimal Android for this device? If this is what RFE is currently doing, I would be willing to help test/bug report any such images and/or help with development. You guys are awesome by the way.. really didn't expect this phone to turn out to be such a good deal.

statussticks said:
Hello, super fresh noob here. I bought the "AT&T Fusion 2 GoPhone" three days ago, and successfully used this method of gaining root access on my device. I am an experienced linux user/developer who just bought his first Android phone.. :laugh: Instead of trying to remove the factory installed components, would it be possible to build a custom version of basic/minimal Android for this device? If this is what RFE is currently doing, I would be willing to help test/bug report any such images and/or help with development. You guys are awesome by the way.. really didn't expect this phone to turn out to be such a good deal.
Click to expand...
Click to collapse
I do believe that RFE is working on a custom ROM that removes all the CrapWare that was pre-installed on the phone. Hopefully after that, he will be able to start to build CM for it.
If I could, I would attempt to start building CM for the Fusion 2, but I do not know how to setup a build environment.

Thanks for your response robo buddy. I have done some poking around myself over ssh and a sshfs mount. After researching a bit about 'standard/common' Android filesystem layouts, I'm starting to think the stock ROM on this phone is pretty screwy. There is only one flash memory block device (/dev/block/mmcblk0), and it is partitioned into nearly 20 different slices:
Code:
Device Boot Start End Blocks Id System Analysis
/dev/block/mmcblk0p1 * 1 40 20 4d Unknown ?
/dev/block/mmcblk0p2 41 640 300 45 Unknown ?
/dev/block/mmcblk0p3 641 266880 133120 c Win95 FAT32 (LBA) contains fat16 volume with arm9 radio software
/dev/block/mmcblk0p4 266881 7634943 3684031+ 5 Extended extended partition
/dev/block/mmcblk0p5 270336 294911 12288 6a Unknown ?
/dev/block/mmcblk0p6 294912 688127 196608 83 Linux /cache
/dev/block/mmcblk0p7 688128 696319 4096 63 GNU HURD or SysV ?
/dev/block/mmcblk0p8 696320 702463 3072 58 Unknown ?
/dev/block/mmcblk0p9 704512 712703 4096 46 Unknown ?
/dev/block/mmcblk0p10 712704 718847 3072 4a Unknown ?
/dev/block/mmcblk0p11 720896 727039 3072 4b Unknown ?
/dev/block/mmcblk0p12 729088 1515519 393216 83 Linux /system
/dev/block/mmcblk0p13 1515520 3088383 786432 83 Linux /data
/dev/block/mmcblk0p14 3088384 3096575 4096 47 Unknown ?
/dev/block/mmcblk0p15 3096576 3112959 8192 48 Unknown ?
/dev/block/mmcblk0p16 3112960 3153919 20480 60 Unknown ?
/dev/block/mmcblk0p17 3153920 3162111 4096 6c Unknown ?
/dev/block/mmcblk0p18 3162112 3325951 81920 83 Linux /cust
/dev/block/mmcblk0p19 3325952 7634943 2154496 6b Unknown /HWUserData (vold? mounted to /mnt/sdcard)
Partitions 1-4 do not end on cylinder boundary
This is a dump using fdisk with some minor comments at the end of each line. So my question is... where the heck are the 'boot', 'system', and 'recovery' partitions? This layout doesn't make any sense. Where does the bootloader find 'boot.img' at startup?
On top of that, I'm trying to make sense of all this Android jargon. I'm on 64 bit Arch linux with a dev setup and ADB communication with my U8665 working. Found a file "open source-kernel-2.6.38.6-U8815- Gingerbread.tar.gz" on the Huawei website. Contains what appears to be the source for the kernel version running on my U8665 right now. Many comments by authors who appear to be employed by Huawei. Grepping the source tree for 'U8665' nets results in a file 'fs/proc/app_info.c':
Code:
{ /* machine_arch_type s_board_id hw_version_id */
...
{MACH_TYPE_MSM7X27A_U8655_EMMC, "MSM7225A_U8665", "HD2U8655M"},
Searching google for the string "HD2U8655M" nets the device's PTCRB certification of some kind ..?
Ahem. I'm not exactly sure where to go from here. I am wondering if I can somehow compile this kernel along with CM 7 and build an image that way. From what I can understand from what I've read, this phone supports the ARM7 instruction set and has an Adreno GPU, so it's possible to eventually support ICS/JB..
P.S. I have some references to research I've been doing, but alas the forum wont let me insert hyperlinks until I make 10 posts
Edit: Alright, so I went further. mmcblk0p15 and mmcblk0p16 contain android images..
Code:
[[email protected] U8665]$ split_bootimg.pl mmcblk0p15
Page size: 2048 (0x00000800)
Kernel size: 3521448 (0x0035bba8)
Ramdisk size: 701945 (0x000ab5f9)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttyDCC0 androidboot.hardware=huawei
Writing mmcblk0p15-kernel ... complete.
Writing mmcblk0p15-ramdisk.gz ... complete.
[[email protected] U8665]$ split_bootimg.pl mmcblk0p16
Page size: 2048 (0x00000800)
Kernel size: 3501096 (0x00356c28)
Ramdisk size: 1690977 (0x0019cd61)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttyMSM0,115200,n8 androidboot.hardware=qcom
Writing mmcblk0p16-kernel ... complete.
Writing mmcblk0p16-ramdisk.gz ... complete.
So p15 is 'boot' and p16 is 'recovery', right? I should be able to build a ClockworkMod image with one of these kernels and then either fastboot flash it to recovery or just dd it into the proper device, correct?

Thanks
I just made an account to thank you guys for helping me root my fusion2. I am just a complete freeloader who has helped nothing whatsoever, but if i could i would! thanks guys i just hope you know you are appreciated for your hard work, and i hope a custom rom is made because i dont know how to get rid of some bloatware apps that have nand security and i have no idea how to turn that off O.O
best 100 bucks ive spent in a while for the fusion 2, i use the app pinger and i pay $0 dollars a year for texting and calling as long as i use wifi!!
well i hope u guys proceed more with this phone, if not, either way thanks guys

still bricked
sounds like theres some more interest in the phone now thx RFE. I'm still bricked with this one tried every way I could think of to flash those rooted stock system files they took every time via fastboot flash system but I havent been able to get the phone to load past white at&t. I'm assuming my boot.img / recovery.img / system.img either not existing or not correct for phone so unable to load. Could someone give me simple instructions to flash that or possibly rip those img files and or create an update.zip containing everything and signed properly so fastboot can flash as simply as fastboot update that'd be awesome and a quick and easy fix for anyone that bricks in the future experimenting with customs or whatever... wish I could help but new to most of this thx guys keep up the good work!

BOOOYA, well done! Rooted WiFi homephone.. thank you!

Lmao, so rad

statussticks said:
Thanks for your response robo buddy. I have done some poking around myself over ssh and a sshfs mount. After researching a bit about 'standard/common' Android filesystem layouts, I'm starting to think the stock ROM on this phone is pretty screwy. There is only one flash memory block device (/dev/block/mmcblk0), and it is partitioned into nearly 20 different slices:
Code:
Device Boot Start End Blocks Id System Analysis
/dev/block/mmcblk0p1 * 1 40 20 4d Unknown ?
/dev/block/mmcblk0p2 41 640 300 45 Unknown ?
/dev/block/mmcblk0p3 641 266880 133120 c Win95 FAT32 (LBA) contains fat16 volume with arm9 radio software
/dev/block/mmcblk0p4 266881 7634943 3684031+ 5 Extended extended partition
/dev/block/mmcblk0p5 270336 294911 12288 6a Unknown ?
/dev/block/mmcblk0p6 294912 688127 196608 83 Linux /cache
/dev/block/mmcblk0p7 688128 696319 4096 63 GNU HURD or SysV ?
/dev/block/mmcblk0p8 696320 702463 3072 58 Unknown ?
/dev/block/mmcblk0p9 704512 712703 4096 46 Unknown ?
/dev/block/mmcblk0p10 712704 718847 3072 4a Unknown ?
/dev/block/mmcblk0p11 720896 727039 3072 4b Unknown ?
/dev/block/mmcblk0p12 729088 1515519 393216 83 Linux /system
/dev/block/mmcblk0p13 1515520 3088383 786432 83 Linux /data
/dev/block/mmcblk0p14 3088384 3096575 4096 47 Unknown ?
/dev/block/mmcblk0p15 3096576 3112959 8192 48 Unknown ?
/dev/block/mmcblk0p16 3112960 3153919 20480 60 Unknown ?
/dev/block/mmcblk0p17 3153920 3162111 4096 6c Unknown ?
/dev/block/mmcblk0p18 3162112 3325951 81920 83 Linux /cust
/dev/block/mmcblk0p19 3325952 7634943 2154496 6b Unknown /HWUserData (vold? mounted to /mnt/sdcard)
Partitions 1-4 do not end on cylinder boundary
This is a dump using fdisk with some minor comments at the end of each line. So my question is... where the heck are the 'boot', 'system', and 'recovery' partitions? This layout doesn't make any sense. Where does the bootloader find 'boot.img' at startup?
On top of that, I'm trying to make sense of all this Android jargon. I'm on 64 bit Arch linux with a dev setup and ADB communication with my U8665 working. Found a file "open source-kernel-2.6.38.6-U8815- Gingerbread.tar.gz" on the Huawei website. Contains what appears to be the source for the kernel version running on my U8665 right now. Many comments by authors who appear to be employed by Huawei. Grepping the source tree for 'U8665' nets results in a file 'fs/proc/app_info.c':
Code:
{ /* machine_arch_type s_board_id hw_version_id */
...
{MACH_TYPE_MSM7X27A_U8655_EMMC, "MSM7225A_U8665", "HD2U8655M"},
Searching google for the string "HD2U8655M" nets the device's PTCRB certification of some kind ..?
Ahem. I'm not exactly sure where to go from here. I am wondering if I can somehow compile this kernel along with CM 7 and build an image that way. From what I can understand from what I've read, this phone supports the ARM7 instruction set and has an Adreno GPU, so it's possible to eventually support ICS/JB..
P.S. I have some references to research I've been doing, but alas the forum wont let me insert hyperlinks until I make 10 posts
Edit: Alright, so I went further. mmcblk0p15 and mmcblk0p16 contain android images..
Code:
[[email protected] U8665]$ split_bootimg.pl mmcblk0p15
Page size: 2048 (0x00000800)
Kernel size: 3521448 (0x0035bba8)
Ramdisk size: 701945 (0x000ab5f9)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttyDCC0 androidboot.hardware=huawei
Writing mmcblk0p15-kernel ... complete.
Writing mmcblk0p15-ramdisk.gz ... complete.
[[email protected] U8665]$ split_bootimg.pl mmcblk0p16
Page size: 2048 (0x00000800)
Kernel size: 3501096 (0x00356c28)
Ramdisk size: 1690977 (0x0019cd61)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttyMSM0,115200,n8 androidboot.hardware=qcom
Writing mmcblk0p16-kernel ... complete.
Writing mmcblk0p16-ramdisk.gz ... complete.
So p15 is 'boot' and p16 is 'recovery', right? I should be able to build a ClockworkMod image with one of these kernels and then either fastboot flash it to recovery or just dd it into the proper device, correct?
Click to expand...
Click to collapse
I do believe so, but I'm not too sure. Maybe you can help out RFE, since I'm no developer.
ericrazy2000 said:
I just made an account to thank you guys for helping me root my fusion2. I am just a complete freeloader who has helped nothing whatsoever, but if i could i would! thanks guys i just hope you know you are appreciated for your hard work, and i hope a custom rom is made because i dont know how to get rid of some bloatware apps that have nand security and i have no idea how to turn that off O.O
best 100 bucks ive spent in a while for the fusion 2, i use the app pinger and i pay $0 dollars a year for texting and calling as long as i use wifi!!
well i hope u guys proceed more with this phone, if not, either way thanks guys
Click to expand...
Click to collapse
sinco54 said:
BOOOYA, well done! Rooted WiFi homephone.. thank you!
Click to expand...
Click to collapse
gigilie said:
sounds like theres some more interest in the phone now thx RFE. I'm still bricked with this one tried every way I could think of to flash those rooted stock system files they took every time via fastboot flash system but I havent been able to get the phone to load past white at&t. I'm assuming my boot.img / recovery.img / system.img either not existing or not correct for phone so unable to load. Could someone give me simple instructions to flash that or possibly rip those img files and or create an update.zip containing everything and signed properly so fastboot can flash as simply as fastboot update that'd be awesome and a quick and easy fix for anyone that bricks in the future experimenting with customs or whatever... wish I could help but new to most of this thx guys keep up the good work!
Click to expand...
Click to collapse
Thanks for all your support! Looks like we have potential developer (statussticks) for this phone. :good:

RoboticBuddy said:
I do believe so, but I'm not too sure. Maybe you can help out RFE, since I'm no developer.
Thanks for all your support! Looks like we have potential developer (statussticks) for this phone. :good:
Click to expand...
Click to collapse
I hope so, i bought this phone at frys for 59.99 on a crazy 1 day sale for no good reason. lol... Its actually a pretty little impressive piece for the price and a custom bare bones aosp/aokp/cm would be the meow meow!!! cool little phone for sure!!

I have to be honest, I know nothing about Android development. I just jumped into this because I was forced to replace my flip phone GoPhone (submerged) and ended up with a smartphone. I am going to PM RFE once more, see if I get a response.
See the thing is.. at this point I'm supposed to be able to issue the command
Code:
fastboot boot out/target/product/u8665/recovery.img
to load a test image over USB into the phone's memory and boot it (?), essentially to test a build before you flash it. I've tried this with both the 'boot' and 'recovery' kernels (p15 and p16), building a CyanogenMod-gingerbread Recovery image (apparently) successfully. When I issue the above mentioned fastboot command it reports success, but nothing happens. Phone just sits at the ATT logo, and is no longer accessible by any fastboot commands. Requires me to unplug the phone, remove the battery. Hard freeze.
So it's like.. do I really wanna run the risk of trying to flash this to recovery and bricking my phone? I'm still not sure if I can just reflash the superrecovery backup if things don't go well. I have heard incidents of people saying 'fastboot won't respond anymore, screen always stuck at the logo.'
I may just go for it a little later. Hell, I'll buy another $99 phone if I have to. I wish RFE would chime in and drop the knowledge carpet bomb or something..

statussticks said:
I have to be honest, I know nothing about Android development. I just jumped into this because I was forced to replace my flip phone GoPhone (submerged) and ended up with a smartphone. I am going to PM RFE once more, see if I get a response.
See the thing is.. at this point I'm supposed to be able to issue the command
Code:
fastboot boot out/target/product/u8665/recovery.img
to load a test image over USB into the phone's memory and boot it (?), essentially to test a build before you flash it. I've tried this with both the 'boot' and 'recovery' kernels (p15 and p16), building a CyanogenMod-gingerbread Recovery image (apparently) successfully. When I issue the above mentioned fastboot command it reports success, but nothing happens. Phone just sits at the ATT logo, and is no longer accessible by any fastboot commands. Requires me to unplug the phone, remove the battery. Hard freeze.
So it's like.. do I really wanna run the risk of trying to flash this to recovery and bricking my phone? I'm still not sure if I can just reflash the superrecovery backup if things don't go well. I have heard incidents of people saying 'fastboot won't respond anymore, screen always stuck at the logo.'
I may just go for it a little later. Hell, I'll buy another $99 phone if I have to. I wish RFE would chime in and drop the knowledge carpet bomb or something..
Click to expand...
Click to collapse
A working twrp would be straight drug deala pimp style.. I'm gonna reach out to a couple of devs that may be willing to help out but I don't know, I may have to get him loaded and bribe him with cheap hookers. Also, if you go for it and your phone explodes into puppies then is be willing to help on a 2 device for development.. ill run by frys and see if they are on sale or if I can weasel the sales guy into hookin a sale price up today after I close the store.. stand by sweetie pie.
Sent from my HTC One XL using xda premium

Got Root/Trying to build CWM
sinco54 said:
Lmao, so rad
Click to expand...
Click to collapse
Got root no problem, but dumping the files necessary to build CWM is puzzling me.. help?
---------- Post added at 08:45 AM ---------- Previous post was at 07:48 AM ----------
RoboticBuddy said:
I have made this thread to compile all the posts on rooting/custom ROMs for the Fusion 2.
Q1. How do I root my device?
A. I have put all the necessary files together in one package for rooting. https://www.dropbox.com/s/lm11rrn3z5c2j6v/Huawei-Fusion-2-Recovery-Root.zip
Q2. Is there any Custom Recovery?
A. There is no CWM or TWRP as of now, but you can boot into CWM via fastboot. http://forum.xda-developers.com/showpost.php?p=36534284&postcount=4
Q3. Is there any Customs ROMs for this phone?
A. As of now, there are NO developed custom ROMs for this phone, yet. There is a pre-rooted stock ROM, for anybody who has a bricked phone. http://forum.xda-developers.com/showpost.php?p=36533895&postcount=46
Will add more later, when I have the time.
Thanks to RFE, who made rooting the Fusion 2 possible!
Click to expand...
Click to collapse
After using this http://www.mediafire.com/?irr4cc14xy9ygs9 which is a method to get cwm on the first fusion. I lost the recovery.img including the stock one.. However when I replaced the CWM build for the fusion 1 found in the "INSTALLADOR" CWM thing with a build intended for the fusion 2 I am back on stock recovery! (found in a random forum don't feel like finding now will post if anyone wants PM ME)

Shagerty said:
Got root no problem, but dumping the files necessary to build CWM is puzzling me.. help?
---------- Post added at 08:45 AM ---------- Previous post was at 07:48 AM ----------
After using this http://www.mediafire.com/?irr4cc14xy9ygs9 which is a method to get cwm on the first fusion. I lost the recovery.img including the stock one.. However when I replaced the CWM build for the fusion 1 found in the "INSTALLADOR" CWM thing with a build intended for the fusion 2 I am back on stock recovery! (found in a random forum don't feel like finding now will post if anyone wants PM ME)
Click to expand...
Click to collapse
I'm trying /a friend of mine/ is to get a twrp to function..
Also, these phones were on sale at Fry's again but were 79.99.. I picked 1 more up solely for development.
Sent from my One X using xda premium

Thank you! Rooted my phone without any problems following your instructions!
Probably it is a wrong place to ask such questions, but could you point me to any information how to unlock network on this phone (currently it is locked for AT&T, and can be used with their SIM cards only)?
Thank you!

I'm still looking for that info too...
Sent from my HTC One XL using xda premium

Got unlocking code from one unlocking services for $15 in 24hours.
And then used Titanium Backup and Root Uninstaller to remove AT&T apps.

Aknodx said:
Got unlocking code from one unlocking services for $15 in 24hours.
And then used Titanium Backup to remove AT&T apps.
Click to expand...
Click to collapse
Where did you buy the unlocking code?

[Q] Advice on updating rooted FTV without going to 51.1.2.0 to

I have a FTV that is rooted and still at 51.1.0.1 I want to upgrade to 51.1.1.0_user_511070220, but don't want to risk going to the latest 51.1.2.0 unrootable version. Can I use adb to copy the upgrade to /cache and upgrade locally with the box disconnected from the internet or does it need to call home when I am doing the local upgrade? I can also block the update sites in the router firewall:
amzdigitaldownloads.edgesuite.net
softwareupdates.amazon.com
once this is done, I can re-run towelroot and disable OTA.
Any advise on the best way to proceed is appreciated.
Thanks in advance for everyone's help!

Yes, do the manual upgrade to the latest rootable firmware. Follow the directions on http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ That is the best way to upgrade without jumping through each upgrade.
It will need internet connection, I removed mine before upgrade and it would not let me proceed and get stuck on the network selection pickup. Maybe after you have pushed the upgrade.zip to your cache and send it a recovery reboot command, you can disconnect the internet. I did not, so not sure if that works.
Before you do anything, make sure you have blocked those 2 sites. Re-verify it before you proceed.
Once you upgrade, immediately disable the FTV upgrade package. I would suggest to keep the blocks on those 2 sites even after you disable the FTV auto upgrade.

dbdoshi said:
Yes, do the manual upgrade to the latest rootable firmware. Follow the directions on http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ That is the best way to upgrade without jumping through each upgrade.
It will need internet connection, I removed mine before upgrade and it would not let me proceed and get stuck on the network selection pickup. Maybe after you have pushed the upgrade.zip to your cache and send it a recovery reboot command, you can disconnect the internet. I did not, so not sure if that works.
Before you do anything, make sure you have blocked those 2 sites. Re-verify it before you proceed.
Once you upgrade, immediately disable the FTV upgrade package. I would suggest to keep the blocks on those 2 sites even after you disable the FTV auto upgrade.
Click to expand...
Click to collapse
If you have dcp blocked before doing the update, it should remain blocked after the update.

rbox said:
If you have dcp blocked before doing the update, it should remain blocked after the update.
Click to expand...
Click to collapse
Thanks, that is good to know and comforting.

rbox said:
If you have dcp blocked before doing the update, it should remain blocked after the update.
Click to expand...
Click to collapse
You are probably right, I am a novice to this. But, I swear to God, I seem to remember not dcp blocking it on a friend's FTV when I upgraded his to the latest rootable firmware and checking the system on FTV did not generate the error or "Checking now..." message (His was blocked before the OTA upgrade). So, to clarify, the block remains for OTA and manual upgrade both?

dbdoshi said:
You are probably right, I am a novice to this. But, I swear to God, I seem to remember not dcp blocking it on a friend's FTV when I upgraded his to the latest rootable firmware and checking the system on FTV did not generate the error or "Checking now..." message (His was blocked before the OTA upgrade). So, to clarify, the block remains for OTA and manual upgrade both?
Click to expand...
Click to collapse
The block *should* remain. I can't imagine why it wouldn't. But I haven't really done any extensive testing on it. Doing the OTA and doing the manual upgrade are the same. The manual upgrade is manually doing exactly what the OTA does. The OTA downloads the .bin file, and tells recovery to flash it and reboots to recovery. The problem comes if you get an OTA update to the unrootable firmware. The dcp will remain blocked, but you won't be able to gain root anymore.

rbox said:
If you have dcp blocked before doing the update, it should remain blocked after the update.
Click to expand...
Click to collapse
I updated the box to 51.1.1.0_user_511070220 last night. No problems at all. I used this process to update the box:
http://forum.xda-developers.com/showthread.php?t=2796067
I used ftp to binary transfer the update file to /cache/update.zip and I set r/w permissions on this file.
the /cache/recovery folder did not exist (needed in tutorial above) so I created it and did a chmod 777 /cache/recovery
Once the update completed, I re-rooted the box - towelroot, Let it rain button.
I forgot to check if the dcp package was still disabled. I ssh'ed to the box and disabled it just to make sure.
I also had to run busybox to re-install it.
I was using the install-recovery-2.sh trick to mount my usb stick, so I lost this and had to recreate /system/etc/install-recovery-2.sh (set execute permission on it and add the line:
mount -t ext4 /dev/block/sda1 /data/sdext2
install-recovery-2.sh is a non-existent file that is called in the last line of install-recovery.sh. This is executed during the boot process and can be used to execute commands when booting. To take advantage of this, create the install-recovery-2.sh file and add the lines you want executed. you have to set execute permission on the file.
su
mount -o rw,remount /system
create and add commands to /system/etc/install-recovery-2.sh
( I added: mount -t ext4 /dev/block/sda1 /data/sdext2 (where /data/sdext2 is where I want my flash drive to show up)
chmod 755 /system/etc/install-recovery-2.sh
mount -o ro,remount /system
exit

Can this be used to exploit much more interesting commands?
Such as making a backdoor for rooting the unrootable OTA update and even unlocking the bootloader/Custom ROM?
Edit:What about overclocking by permanently modifying the related files to set GPU to minimum 400Mhz and maximum 500Mhz and overclocking the CPUs to a maximum of 1.9Ghz or 2.0Ghz?
If it can be used to overclock,please elaborate on how you can do it?
I posted the directory of the related files in a topic a while back.

retroben said:
Can this be used to exploit much more interesting commands?
Such as making a backdoor for rooting the unrootable OTA update and even unlocking the bootloader/Custom ROM?
Click to expand...
Click to collapse
So that is a good idea, but unfortunately the first thing that happens when you install the OTA is it wipes /system. But once you have root, anything you could put in that script, you could manually run as root, so it can't let you do anything extra.
As for custom roms, the good news is that the OS on the Fire TV is pretty much stock CAF android. The kernel can boot AOSP/CM as is. And using a similar but different script earlier in the boot process, I'm able to get Safestrap working. I currently have Clockwork mod working, but Safestrap uses TWRP and as of yet I have been unable to get TWRP to display anything on the TV. I'm going to try to work on it some more this weekend.

rbox said:
So that is a good idea, but unfortunately the first thing that happens when you install the OTA is it wipes /system. But once you have root, anything you could put in that script, you could manually run as root, so it can't let you do anything extra.
As for custom roms, the good news is that the OS on the Fire TV is pretty much stock CAF android. The kernel can boot AOSP/CM as is. And using a similar but different script earlier in the boot process, I'm able to get Safestrap working. I currently have Clockwork mod working, but Safestrap uses TWRP and as of yet I have been unable to get TWRP to display anything on the TV. I'm going to try to work on it some more this weekend.
Click to expand...
Click to collapse
Rbox,
Sounds very interesting. Keep the good work.

rayosx said:
Rbox,
Sounds very interesting. Keep the good work.
Click to expand...
Click to collapse
So I was finally able to get TWRP booting and displaying (in the correct colors). As you can see, it doesn't fill the screen. The problem is TWRP needs theme files to match the resolution, and it currently has no support for 1080p, although adding support for 1080p isn't the problem. It's figuring out if I should add in dynamic switching support to let it switch between 1080p and 720p. Which is why I need people to fill out the poll I created here.
The other problem with 720p is my TV is 1080p, so I can't really test it. Does anyone know if there is TWRP support for any of the other android based TV devices like OYUA or whatever?

What?
The 720p mode works on 1080p TVs since I used that mode briefly until switching to 1080p for better quality.

retroben said:
What?
The 720p mode works on 1080p TVs since I used that mode briefly until switching to 1080p for better quality.
Click to expand...
Click to collapse
Unfortunately in recovery, if the graphics are 720p then it won't fill the screen at 1080p. Although now that I think about it, I wonder if I could set it up to just scale up from 720 to 1080. That would probably be easiest.

[Q] Is My AFTV Bricked??? Reward

Hi, I came home today and my AFTV is stuck on the white & yellow AFTV logo (Ctrl+i+Prt Screen just send me back to CWM). I haven’t done anything to it recently. I am wondering how to fix it. I have CWM-based Recovery v6.0.5.1.4a on it and tried to reinstall the last ROM I installed, and it did install but still will not boot. Should I run that or the restore from backup option in CWM? I never made an official back up to my knowledge it’s “1970-01-01.00.40.56/”. I just don’t know what I should do bc the boot kernal is obviously corrupted. Should I “image restore” in CWM or is there a 3rd option? I'm hoping there is still a chance to recover the boot image since I can still access CWM and can use a usb hub to upload zip files (no ADB connect). I have SPMC with bootloader running, and am debating reinstalling that zip file, but I do not think it will work. I think what caused my issue was setting my Android Screen Saver to Shutdown instead of sleep, since it happened the next morning. I tried looking on this forum for clues but the only guy to have a similar issue said it fixed itself, which does me no good.
I am offering a $11.11 reward (Paypal donation) to anyone who can guide me in fixing this.

Kul-Aid23 said:
Hi, I came home today and my AFTV is stuck on the white & yellow AFTV logo (Ctrl+i+Prt Screen just send me back to CWM). I haven’t done anything to it recently. I am wondering how to fix it. I have CWM-based Recovery v6.0.5.1.4a on it and tried to reinstall the last ROM I installed, and it did install but still will not boot. Should I run that or the restore from backup option in CWM? I never made an official back up to my knowledge it’s “1970-01-01.00.40.56/”. I just don’t know what I should do bc the boot kernal is obviously corrupted. Should I “image restore” in CWM or is there a 3rd option? I'm hoping there is still a chance to recover the boot image since I can still access CWM and can use a usb hub to upload zip files (no ADB connect). I have SPMC with bootloader running, and am debating reinstalling that zip file, but I do not think it will work. I think what caused my issue was setting my Android Screen Saver to Shutdown instead of sleep, since it happened the next morning. I tried looking on this forum for clues but the only guy to have a similar issue said it fixed itself, which does me no good.
I am offering a $11.11 reward (Paypal donation) to anyone who can guide me in fixing this.
Click to expand...
Click to collapse
http://androidflagship.com/3217-fix-damaged-bricked-android-device
Maybe read through the link above.
I'm not an Android expert. Aftv was my first experience then I bought a phone and then rooted kfhd. But I have heard you should wipe dalvik cache and heard it's essential to even factory reset in recovery before flashing a new Rom. That is NOT stressed in any of the aftv guides I read and it may not be necessary but if for no other reason than to learn I'd like to know why???
But like I said. I'm the equivalent of a kindergartner when it comes to android so ask questions before you try anything. I don't want to cause more issues for you.

Kul-Aid23 said:
Hi, I came home today and my AFTV is stuck on the white & yellow AFTV logo (Ctrl+i+Prt Screen just send me back to CWM). I haven’t done anything to it recently. I am wondering how to fix it. I have CWM-based Recovery v6.0.5.1.4a on it and tried to reinstall the last ROM I installed, and it did install but still will not boot. Should I run that or the restore from backup option in CWM? I never made an official back up to my knowledge it’s “1970-01-01.00.40.56/”. I just don’t know what I should do bc the boot kernal is obviously corrupted. Should I “image restore” in CWM or is there a 3rd option? I'm hoping there is still a chance to recover the boot image since I can still access CWM and can use a usb hub to upload zip files (no ADB connect). I have SPMC with bootloader running, and am debating reinstalling that zip file, but I do not think it will work. I think what caused my issue was setting my Android Screen Saver to Shutdown instead of sleep, since it happened the next morning. I tried looking on this forum for clues but the only guy to have a similar issue said it fixed itself, which does me no good.
I am offering a $11.11 reward (Paypal donation) to anyone who can guide me in fixing this.
Click to expand...
Click to collapse
Start Recovery CMM and select the rom.zip in Sdcard/0. that should bring you back with the boot menu thus saving your root, but you will have to setup everything again. remember disable updates using /su disable commands. i wouldn't mind helping you if you live closeby to Los Angeles.

navigates said:
Start Recovery CMM and select the rom.zip in Sdcard/0. that should bring you back with the boot menu thus saving your root, but you will have to setup everything again. remember disable updates using /su disable commands. i wouldn't mind helping you if you live closeby to Los Angeles.
Click to expand...
Click to collapse
Hey, I appreciate the input but I have already tried that, I mentioned it in my original post. I am not sure exactly as to what happened. It says it installed but same ****. I am assuming my AFTV updated to the new firmware, even though I thought I had updates blocked on my device. I also had the 3 urls blocked via my router. The only thing I can think of is my Asus router limits the characters so it's blocking amzdigitaldownloads.edgesuite.ne instead of .net. Or if it uses a different URL for Canada bc I use a DNS service on my router so I can watch local and playoff hockey games through NHL GCL. I also changed my screen saver in SPMC (which is what my AFTV boots to) to android power off instead of sleep a day before this happened. I was curious about maybe clearing the cache then trying to reinstall the rom again or try a different Rom file. Or maybe even hard mod if it would fix it. I'm in StL btw, Thank You though.

Kul-Aid23 said:
Hey, I appreciate the input but I have already tried that, I mentioned it in my original post. I am not sure exactly as to what happened. It says it installed but same ****. I am assuming my AFTV updated to the new firmware, even though I thought I had updates blocked on my device. I also had the 3 urls blocked via my router. The only thing I can think of is my Asus router limits the characters so it's blocking amzdigitaldownloads.edgesuite.ne instead of .net. Or if it uses a different URL for Canada bc I use a DNS service on my router so I can watch local and playoff hockey games through NHL GCL. I also changed my screen saver in SPMC (which is what my AFTV boots to) to android power off instead of sleep a day before this happened. I was curious about maybe clearing the cache then trying to reinstall the rom again or try a different Rom file. Or maybe even hard mod if it would fix it. I'm in StL btw, Thank You though.
Click to expand...
Click to collapse
I cant block a domain name on my router either. I need to ping the domain name--that yields an IP address then I copy that into the appropriate box to block internet access.
But, if you're blocked on the box itself, I really don't think you got an update, ESPECIALLY if you have custom recovery. It will attempt to install it but it will fail and the box will boot itself to recovery. It happened to me before when I forgot to pm disable after wiping data. I think there's a slim chance of an update sneaking through but I doubt they found a way. Otherwise a lot more people would be reporting your issue right now.
BTW--our problems aren't really similar. I'm not bricked. I've got something going on that I narrowed down to my usb port. I thought it was a corrupted usb drive but every drive I plug in, unmounted, causes the box to boot into a snow/static screen then hang on amazon. Unplug it and it boots fine. Still working on a solution. Good luck!

You should be able to adb with a network cat5/6 ethernet cable from your computer/router to firetv, you will need to activate a hotspot that shares via Ethernet in an app such as connectify if you directly from CPU to firetv. There is also command line commands to do the same thing but I do not know how.
Or if have xposed installed and you recently activated something but did not reboot you try the xposed uninstaller located in the sdcard/android/... de.com.Xposedinstalled or whatever folder xposed is.
Adb shell in recovery
Then
cd /data/app
ls -lt
Click to expand...
Click to collapse
Find the last apps you installed
And to uninstall them
rm com.apps.name.apkfilename
Click to expand...
Click to collapse

smartymcfly said:
You should be able to adb with a network cat5/6 ethernet cable from your computer/router to firetv, you will need to activate a hotspot that shares via Ethernet in an app such as connectify if you directly from CPU to firetv. There is also command line commands to do the same thing but I do not know how.
Or if have xposed installed and you recently activated something but did not reboot you try the xposed uninstaller located in the sdcard/android/... de.com.Xposedinstalled or whatever folder xposed is.
Adb shell in recovery
Then
Find the last apps you installed
And to uninstall them
Click to expand...
Click to collapse
Oh snap, this may work. I didn't realize I could ADB into it still ( posted this on reddit and someone said I could too), I've tried before but was over wifi, so I will have to give this a shot. By any chance would you know of an article that has this info in a little bit more detail?

Our issues do seem somewhat similar. You altered the normal sleep options which thinking about it now...that's one of the functions in elmerohueso launcher. As long as I don't leave a flash drive plugged in everything works normally Except Display/Screensaver on home screen. But I've used that repo before and that specific option. It never highjacked the fire display options (could always access and change them) so I don't see how deleting anything in the repo would effect that? My instinct is telling me to reinstall xposed and it might correct itself. My anxiety is yelling I'm gonna end up not being able to boot it up normally if I try. Sorry don't mean to intrude but can you confirm you had xposed installed when this happened?

I had xposed, towel root, super SU, and all the other good stuff installed. I also had used the power off option before too. I'm just going to install kodi 14.1 with the boot loader and hope it overwrites whatever happened after I get home from work. The thing has been running great since mid-December and I hadn't really changed anything at all, except for that power option.

smartymcfly said:
You should be able to adb with a network cat5/6 ethernet cable from your computer/router to firetv, you will need to activate a hotspot that shares via Ethernet in an app such as connectify if you directly from CPU to firetv. There is also command line commands to do the same thing but I do not know how.
Or if have xposed installed and you recently activated something but did not reboot you try the xposed uninstaller located in the sdcard/android/... de.com.Xposedinstalled or whatever folder xposed is.
Adb shell in recovery
Then
Find the last apps you installed
And to uninstall them
Click to expand...
Click to collapse
Can you be more clear or link to something that explains this better, I've tried what you are saying but I am messing something up. Can you be less vague?

Kul-Aid23 said:
Can you be more clear or link to something that explains this better, I've tried what you are saying but I am messing something up. Can you be less vague?
Click to expand...
Click to collapse
If you need it.
connectify
Run an Ethernet cable to your firetv. Then you will have adb while in recovery if needed. You will need to go into connectify or your router....never mind cwm shows the IP right on the screen.
So after you get your firetv connected via Ethernet cable then you will be able to connect.
http://www.reddit.com/r/fireTV/comments/2ux6vx/i_bricked_and_unbricked_my_firetv_using_an/
You can block the domains by blacklisting it in adaway
---------- Post added at 05:21 PM ---------- Previous post was at 05:13 PM ----------
What do you mean spmc running? That is just a version of gotham/kodi right? Do mean the prerooted ROM by rbox? I would flash the latest version of that.
You might need to go back to aftvnews.com to download and older version of the ROM and then follow the steps on there from the part where CWM recovery is installed. Did you install the boot menu that allows you to choose what you want to boot? If not you should probably also do that.

smartymcfly said:
You should be able to adb with a network cat5/6 ethernet cable from your computer/router to firetv, you will need to activate a hotspot that shares via Ethernet in an app such as connectify if you directly from CPU to firetv. There is also command line commands to do the same thing but I do not know how.
Or if have xposed installed and you recently activated something but did not reboot you try the xposed uninstaller located in the sdcard/android/... de.com.Xposedinstalled or whatever folder xposed is.
Adb shell in recovery
Then
Find the last apps you installed
And to uninstall them
Click to expand...
Click to collapse
This is what I got:
C:\Users\Vladimir\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb conn
ect 192.168.1.219
already connected to 192.168.1.219:5555
C:\Users\Vladimir\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb shel
l
error: protocol fault (no status)
error: protocol fault (no status)
C:\Users\Vladimir\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb conn
ect 192.168.1.219
connected to 192.168.1.219:5555
C:\Users\Vladimir\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb shel
l
~ # cd /data/app
cd /data/app
/data/app # ls -lt
ls -lt
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
-rw-r--r-- 1 system system 10609976 Feb 2 2015 com.splashtop.m360.amz-
1.apk
-rw-r--r-- 1 system system 6691947 Jan 30 2015 net.gtvbox.videoplayer-
1.apk
-rw-r--r-- 1 system system 6793950 Jan 25 2015 com.nuclearheart.robree
dflippinawesome-2.apk
-rw-r--r-- 1 system system 26916397 Jan 16 2015 com.msherwin.traversal-
1.apk
-rw-r--r-- 1 system system 849239 Jan 16 2015 com.koushikdutta.cast.r
eceiver-1.apk
-rw-r--r-- 1 system system 15314637 Jan 10 2015 com.entwicklerx.perrypi
gjumptv-1.apk
-rw-r--r-- 1 system system 16953271 Jan 10 2015 air.com.tangerinepop.ru
nic-1.apk
-rw-r--r-- 1 system system 169316954 Jan 5 2015 com.frogmind.badland-1.
apk
-rw-r--r-- 1 system system 132039052 Jan 5 2015 com.jackboxgames.ydkjpa
rty-1.apk
-rw-r--r-- 1 system system 37907298 Jan 5 2015 com.concretesoftware.pb
achallenge_amazonfree-1.apk
-rw-r--r-- 1 system system 13859655 Jan 5 2015 com.amazon.weather.tv-1
.apk
-rw-r--r-- 1 system system 7165418 Dec 30 2014 com.pbs.video-2.apk
-rw-r--r-- 1 system system 49309428 Dec 27 2014 com.sega.sonic2-1.apk
-rw-r--r-- 1 system system 50121408 Dec 27 2014 com.halfbrick.ageofzomb
ies-1.apk
-rw-r--r-- 1 system system 33200359 Dec 27 2014 com.fallentreegames.ama
zon.quellreflect-1.apk
-rw-r--r-- 1 system system 76108096 Dec 25 2014 com.digitalx.chichiledf
ish-2.apk
-rw-r--r-- 1 system system 29096021 Dec 15 2014 com.hg.farminvasionc-1.
apk
-rw-r--r-- 1 system system 57260455 Dec 15 2014 com.hg.frozenfront-1.ap
k
-rw-r--r-- 1 system system 46766549 Dec 15 2014 com.hg.ninjaherocats-1.
apk
-rw-r--r-- 1 system system 25019798 Dec 15 2014 com.hg.savethepuppiesc-
1.apk
-rw-r--r-- 1 system system 31679186 Dec 15 2014 com.hg.aotlpremium-1.ap
k
-rw-r--r-- 1 system system 22356882 Dec 14 2014 com.nhl.gc1112.free-1.a
pk
-rw-r--r-- 1 system system 27404 Dec 10 2014 rbox.xposed.firetvmods-
1.apk
-rw-r--r-- 1 system system 4595035 Dec 7 2014 com.estrongs.android.po
p-1.apk
-rw-r--r-- 1 system system 595059 Dec 7 2014 com.adrise.profilms-1.a
pk
-rw-r--r-- 1 system system 2758702 Dec 7 2014 com.kebab.Llama-1.apk
-rw-r--r-- 1 system system 32168267 Dec 7 2014 com.android.chrome-1.ap
k
-rw-r--r-- 1 system system 728857 Dec 7 2014 de.robv.android.xposed.
installer-1.apk
-rw-r--r-- 1 system system 8042116 Dec 6 2014 com.netflix.ninja-1.apk
-rw-r--r-- 1 system system 2577850 Dec 5 2014 stericson.busybox-1.apk
-rw-r--r-- 1 system system 113099 Dec 5 2014 com.geohot.towelroot-1.
apk
/data/app # rm com.splashtop.m360.amz-1.apk

That splashtop is not something that would have caused a problem.
Did you flash the ROM but you didn't wipe the data beforehand. Also did you clear the cache & dalvik cache before flashing?
amazon doesn't ship the firetv with splash top or the other apps you installed.
http://www.aftvnews.com/start/
---------- Post added at 05:35 PM ---------- Previous post was at 05:34 PM ----------
You will have to start over because when you wipe system/data/cache/dalvik it will uninstall root unless you flash a prerooted version.
I do not believe you had the latest ROM because you said you used Ctrl print I to get to cwm but now on the latest bootloader it gives you the option to boot into recovery.
What was the last version of the ROM that you installed?
---------- Post added at 05:46 PM ---------- Previous post was at 05:35 PM ----------
This is required to install the latest prerooted rom
http://www.aftvnews.com/how-to-install-a-kernel-boot-menu-on-the-amazon-fire-tv/

smartymcfly said:
That splashtop is not something that would have caused a problem.
Did you flash the ROM but you didn't wipe the data beforehand. Also did you clear the cache & dalvik cache before flashing?
amazon doesn't ship the firetv with splash top or the other apps you installed.
http://www.aftvnews.com/start/
---------- Post added at 05:35 PM ---------- Previous post was at 05:34 PM ----------
You will have to start over because when you wipe system/data/cache/dalvik it will uninstall root unless you flash a prerooted version.
I do not believe you had the latest ROM because you said you used Ctrl print I to get to cwm but now on the latest bootloader it gives you the option to boot into recovery.
What was the last version of the ROM that you installed?
---------- Post added at 05:46 PM ---------- Previous post was at 05:35 PM ----------
This is required to install the latest prerooted rom
http://www.aftvnews.com/how-to-install-a-kernel-boot-menu-on-the-amazon-fire-tv/
Click to expand...
Click to collapse
I had "51.1.4.1_514013920 fixed" rom when this happened. I have not cleared anything, should I? Also my AFTV is acting really weird, when I run adb shell it tells me I dont have SU, and when it connect to the utility, it says I have amazon updates turn on (though I am also in CWM so maybe thats default, idk). Also, I tried doing that crtl+i+prnt scrn again and nothing happens. I think I was mistaken on that bc it does not work. I probably just press ctrl+atl+delete and it just rebooted to the boot menu. My friend is bringing over his AFTV and I'm just going to make a back up and load it on mine, basically try to clone it. If that doesn't work I'm just taking a hammer to it and buying one of these next month:
http://www.cnet.com/products/intel-compute-stick/
I'm not a patient man, hence the reward.

Kul-Aid23 said:
I had "51.1.4.1_514013920 fixed" rom when this happened. I have not cleared anything, should I? Also my AFTV is acting really weird, when I run adb shell it tells me I dont have SU, and when it connect to the utility, it says I have amazon updates turn on (though I am also in CWM so maybe thats default, idk). Also, I tried doing that crtl+i+prnt scrn again and nothing happens. I think I was mistaken on that bc it does not work. I probably just press ctrl+atl+delete and it just rebooted to the boot menu. My friend is bringing over his AFTV and I'm just going to make a back up and load it on mine, basically try to clone it. If that doesn't work I'm just taking a hammer to it and buying one of these next month:
http://www.cnet.com/products/intel-compute-stick/
I'm not a patient man, hence the reward.
Click to expand...
Click to collapse
You already have su when in recovery, or else you need to mount system in cwm.
Well you have access to cwm so should not be bricked right?
You can wipe system/data/cache/dalvik and then flash it otherwise whatever is causing the problem will still be there. Make sure to have the supersuv1.94.zip so you have root when you boot.
Not sure it would be a good idea to try flashing a copy of your friends backup before you try to wipe and flash. You will keep the contents of sdcard, just everything else will be wiped.

STOP all the nonsense you were told to do. Download this and put it on a usb stick. Boot into recovery and wipe cache and dalvik cache. Then VERY CAREFULLY wipe system. DO NOT REBOOT!!!! Flash the prerooted rom I just told you to download. When its done reboot and you will be on 51.1.4.0_514006420+updated. You can STOP NOW with a working FireTV. Or you can proceed to make sure you have most recent recovery, bootloader unlocked, and the the most recent 51.1.4.1_514013920+fixed rom. Make sure you follow the guides carefully.

Kul-Aid23 said:
I had "51.1.4.1_514013920 fixed" rom when this happened. I have not cleared anything, should I? Also my AFTV is acting really weird, when I run adb shell it tells me I dont have SU, and when it connect to the utility, it says I have amazon updates turn on (though I am also in CWM so maybe thats default, idk). Also, I tried doing that crtl+i+prnt scrn again and nothing happens. I think I was mistaken on that bc it does not work. I probably just press ctrl+atl+delete and it just rebooted to the boot menu. My friend is bringing over his AFTV and I'm just going to make a back up and load it on mine, basically try to clone it. If that doesn't work I'm just taking a hammer to it and buying one of these next month:
http://www.cnet.com/products/intel-compute-stick/
I'm not a patient man, hence the reward.
Click to expand...
Click to collapse
So I just cloned my buddies AFTV by making a recovery file and saving it to a usb. I found an article on here talking about cloning. It worked out real well. Everything was still saved with even the same SPMC settings, just changed my IP address and amazon account. Idk why it messed up because the power off option is still there and it works fine. It worked real well.

Es File Explorer issue

I'm having a problem with es file explorer and root explorer. Last night my fire tv kept booting to home screen and rebooting, so I had to re-install 5.0.5.1 prerooted rom thru recovery. I reinstalled all my apps, and when trying to enable root explorer, I get the superuser request as usual, I grant and get the notification that it's been granted. Root explorer access is enabled for about 6 seconds before disabling with the message "Sorry, test failed. This feature cannot run on your device". Adaway works fine when asking for su permission. Only thing I did differently this time around with installation of the rom is I installed Es file explorer and tried to enable root explorer before doing the SU command from adb shell. I've since uninstalled and reinstalled ES file explorer and reacquiring SU permission but it does the same thing. I went and installed a much older version and it does the exact same thing. Anyone else come across this problem?

The only thing I could suggest would be to remove the manager app es file explorer & reinstall the prerooted rom again? Then start fresh, Su, then after you get access then reinstall es? Only other thing I would say if that don't work is do a factory reset (but only do it from within TWRP Recovery!) Then reinstall the prerooted, block updates, grant Su & then see if that works for you? I use ES pro & Root Explorer & haven't had no problems at all.

deanr1977 said:
The only thing I could suggest would be to remove the manager app es file explorer & reinstall the prerooted rom again? Then start fresh, Su, then after you get access then reinstall es? Only other thing I would say if that don't work is do a factory reset (but only do it from within TWRP Recovery!) Then reinstall the prerooted, block updates, grant Su & then see if that works for you? I use ES pro & Root Explorer & haven't had no problems at all.
Click to expand...
Click to collapse
Thanks for your reply. I'll do what another user suggested and use Total Commander instead as I have it installed and granted root access for it, and it does the same functions. I haven't had any issues with es file explorer on my ftv 2 at all, but another user reported the exact same problem in a different thread on this forum so I'm not alone.

Ok mate no worries, just a note I have both manager apps working on 2 sticks (1 rooted & 1 not, both updates blocked but on different firmware) & also on my prerooted AFTV2 so dunno what happened with yours & the other forum member?
Sent from my SM-G900F using Tapatalk

i have this same issue on 2 firebox's after a full conversion from os3, running rbox latest 5.2.x
both give the identical error, yet other apps are getting su control just fine?
any idea's? @rbox

I am having this problem on my first FTV1 I upgraded from PreRooted FireOS 3 to latest PreRooted FireOS 5. It is a fully rooted with fully unlocked bootloader FTV1. ES File Explorer is giving me this error when trying to turn on its Root Explorer option and all though Total Commander & Root Explorer are not giving me this error. They are not letting me copy files from a Root folder into regular storage. I can view them & choose them but it errors out when trying to copy over. I had to copy them thru TWRP.
I plan to do a Factory Reset thru TWRP & reinstall the latest PreRooted Rom again. But this time after doing the TWRP special build number update blocking tweak. I plan to run the SU command before installing any apps. Will see if that helps at all or not. If not I will post more detail info in case someone can help. This is the last bug I've encounter since doing the move from FireOS 3 to FireOS 5.

@d3adpool , @deanr1977 , @LittleBill21
Where you guys ever able to come up with an answer or fix for this issue ??

Unfortunately no, I'm sure reinstalling the rom via twrp would've fixed it but never did. That ftv has since stopped working.

Y314K said:
I am having this problem on my first FTV1
Click to expand...
Click to collapse
ESFE's root explorer has worked fine for me on multiple sticks, running various firmware versions (5.0.5, 5.2.1.0, pre-rooted 5.0.5_r1)
I didn't see mention of which device the OP was using -- but I'm going to go out on a limb and say FTV1 as well.
The same apk on pre-rooted 5.0.5 FTV1 box gives me that error message.
It seems like this just affects 1st-gen firetv boxes.
The question is whether it's linked/limited to pre-rooted bueller ROMs or just AFTV1's in general.
I didn't use ESFE until I was already on bueller-5.0.5_r2, I wonder if it works on stock 5.x.x rooted with kingroot?

d3adpool said:
Unfortunately no, I'm sure reinstalling the rom via twrp would've fixed it but never did. That ftv has since stopped working.
Click to expand...
Click to collapse
Sorry to hear that, thanks for responding. I had already done a few reinstalling of the latest PreRooted Rom via TWRP without that fixing it. Will keep at it, though.
phresch said:
ESFE's root explorer has worked fine for me on multiple sticks, running various firmware versions (5.0.5, 5.2.1.0, pre-rooted 5.0.5_r1)
I didn't see mention of which device the OP was using -- but I'm going to go out on a limb and say FTV1 as well.
The same apk on pre-rooted 5.0.5 FTV1 box gives me that error message.
It seems like this just affects 1st-gen firetv boxes.
The question is whether it's linked/limited to pre-rooted bueller ROMs or just AFTV1's in general.
I didn't use ESFE until I was already on bueller-5.0.5_r2, I wonder if it works on stock 5.x.x rooted with kingroot?
Click to expand...
Click to collapse
This is definitely an FTV1 Bueller on FireOS 5 PreRooted Rom problem. And in my case it is tied to the "unable to access the /sdcard and other directories while in su mode" bug. But the .zip fix provided over @ the PreRooted Rom OP is not fixing the issue. Gonna post a more detail assessment of what I am encountering & what I've tried to fix the issue & failed so far in a bit.
---------- Post added at 01:07 AM ---------- Previous post was at 12:17 AM ----------
@RBox ; @AFTVnews.com
Decided to upgrade my first TowlRoot Rooted Bueller FTV1 on the last FireOS 3 PreRooted Rom (v51.1.6.3) to the latest FireOS 5 PreRooted Rom (v5.2.1.1_r1). I verified that I meet all the requirements. My bootloader was FULLY unlocked & I was on the latest CWM (v6.0.5.1.4a) with BootMenu (v1.0). I decided I wanted from the start the upgrade on as a clean as possible FTV1. So I uninstalled all programs except for SuperSU. Then I went into CWM & did a Factory Reset (Wipe Dalvik, Cache, Factory Reset) from within CWM & Reinstalled the last FireOS 3 PreRooted Rom (v51.1.6.3). All that was left after the Factory Reset was SuperSU.
Then I pushed over the TWRP bueller-twrp_3.0.0-7.img to the /SDCard & verified it's hash to make sure it was not a corrupt upload. Then I ran the command to switch to the TWRP recovery & everything installed perfectly.
I had ready a USB stick (Fat32) so I could install & md5 verify the FireOS 5 PreRooted Rom (v5.2.1.1_r1) on installation. Booted into TWRP & first did a wipe from within TWRP of Dalvik, Cache, Data & Internal Storage. Then installed the FireOS 5 PreRooted Rom (v5.2.1.1_r1) without any errors. Then I rebooted into system & it went thru it's paces. I did hit a road block when it came to check updates. This was because I was blocking the HTTPS update address from both my router & thru OpenDNS. I did a few re-flashes of the FireOS 5 PreRooted Rom (v5.2.1.1_r1) until I figure out that since this was the latest Rom version I should just let it talk to the update servers or do the PropBuild mod. So finally I got past the update nag. I first turned on ADB Debuging & I first did the SU command & chose to GRANT SuperUser rights. Then I did the update block command from SU. I installed my apps & the only bug I found after that was that ES File Explorer, even after it has been granted SuperUSer rights. It will error out "Sorry, test failed. This feature cannot run on your device". I thought this problem was just with ES file Explorer. But it seems to happen to a lesser degree on Total Commander & Root Explorer too. On those I can see the Root directories. But if I ever try to copy something over from /Root to /SDcard or to /USB it won't allow it. They will have some type of error that stops it. Or makes /SDCard disappear.
Then I notice the "Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it." post in the PreRooted Rom's OP. And decided to do the SU test of "[email protected]:/ # ls -al /sdcard" & sure enough. I always get the non SU response of:
"lrwxrwxrwx root root 1970-01-06 19:40 sdcard -> /storage/emulated/legacy"
I tried flashing the bueller-fixsusdcard.zip thru TWRP on that install but nothing changed on the test response. Then I tried to do a full reinstall of the PreRooted Rom with the bueller-fixsusdcard.zip as a secondary .zip to flash during the installation. And same... Then I re-verified that I do have a unlocked bootloader. And that I am rooted. Passed on both. I was able to verified I am rooted by using an SDCard app while trying to see what size my MBCache.db file was. I was able to find it in /Data/Data/ without any problem.
So this is where I am at. I wonder if the bueller-fixsusdcard.zip file needs an update for FireOS 5 PreRooted Rom (v5.2.1.1_r1). Or should we try to install SuperSU as a secondary .zip file in TWRP or what can possibly be the answer to getting SU & Root working properly.
I would appreciate any ideas to try.

Y314K said:
This is definitely an FTV1 Bueller on FireOS 5 PreRooted Rom problem. And in my case it is tied to the "unable to access the /sdcard and other directories while in su mode" bug. But the .zip fix provided over @ the PreRooted Rom OP is not fixing the issue. Gonna post a more detail assessment of what I am encountering & what I've tried to fix the issue & failed so far in a bit.
Click to expand...
Click to collapse
I had the su & /sdcard/ problem too.
I'm going to guess that things went something like this (they did for me):
1] installed twrp & pre-rooted bueller ROM
2] discovered that the included superSU had no GUI
3] replaced superSU with another version to access a GUI
4] discovered su/sdcard bug
5] found & flashed the zip fix
6] tried to su /sdcard/ & still doesn't work
But if I ever try to copy something over from /Root to /SDcard or to /USB it won't allow it. They will have some type of error that stops it. Or makes /SDCard disappear.
Then I notice the "Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it." post in the PreRooted Rom's OP. And decided to do the SU test of "[email protected]:/ # ls -al /sdcard" & sure enough. I always get the non SU response of:
"lrwxrwxrwx root root 1970-01-06 19:40 sdcard -> /storage/emulated/legacy"
Click to expand...
Click to collapse
I was able to remedy this part of the problem; at this point, I still can't access Root Explorer within ES File Explorer..
However, I am able to access /sdcard/ and other previously invisible folders, as well as using RootBrowser and RootExplorer apps.
I'm pretty sure the reason that the zip flash didn't work is because (assuming swapped versions of superSU) your installed superSU binaries are different from the ones the zip was intended to fix.
You have a couple of options, both will give pretty close to the same end result:
First option:
1. re-flash your firmware ROM
2. flash the zip to fix the mount namespace problem
3. install a different SuperSU with a GUI
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps

phresch said:
...
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
Click to expand...
Click to collapse
I searched for a download of v2.05 and could only fine sources that I did not trust. Do you have a link to that version?

phresch said:
I had the su & /sdcard/ problem too.
I'm going to guess that things went something like this (they did for me):
1] installed twrp & pre-rooted bueller ROM
2] discovered that the included superSU had no GUI
3] replaced superSU with another version to access a GUI
4] discovered su/sdcard bug
5] found & flashed the zip fix
6] tried to su /sdcard/ & still doesn't work
Click to expand...
Click to collapse
I haven't tried to change or flash to a different SuperSU then the one that comes stock with the PreRooted Roms. Which is v2.46. Trying my best not to loose having a Fully unlocked bootloader. Are you flashing/testing the different versions of SuperSU thru TWRP or are you just flashing APK's just to try to see which one's GUI might still work ?
I notice the SU /SDCard bug only after trying out Total Commander & Root Explorer. Others said those where working fine for them. But for me it looked like they where gonna work fine. But as soon as any of those went to Root mode. I started to see bugs in those programs too. Although in those programs I can at least view Root files. And this last time Root Explorer is letting me copy files over from Root to /SDCard. Total Commander is still hanging when trying to copy files from Root to /SDCard. Like I said this last time I installed the /SDCard SU .zip fix right after I flashed the PreRooted Rom. So it did changed something. But from ADB I still get the same response from the SU List command.
phresch said:
I was able to remedy this part of the problem; at this point, I still can't access Root Explorer within ES File Explorer..
However, I am able to access /sdcard/ and other previously invisible folders, as well as using RootBrowser and RootExplorer apps.
I'm pretty sure the reason that the zip flash didn't work is because (assuming swapped versions of superSU) your installed superSU binaries are different from the ones the zip was intended to fix.
Click to expand...
Click to collapse
I have not swapped SuperSU from what comes with the PreRooted Rom. Trying other SuperSU versions might be something I do after getting some feedback from @rbox since I really do not want to accidentally loose my Fully unlocked bootloader.
phresch said:
You have a couple of options, both will give pretty close to the same end result:
First option:
1. re-flash your firmware ROM
2. flash the zip to fix the mount namespace problem
3. install a different SuperSU with a GUI
Click to expand...
Click to collapse
Are you doing the SuperSU changing thru APK flashing or thru TWRP zip flashing ? Do you know a link to where we can find most versions of SuperSU from v2.16 (used when we towelrooted) to v2.78 ? I see v2.79 is the latest version. Have you tried v2.79 on your FTV1 ? Is there a version of SuperSU we shouldn't go beyond ?
phresch said:
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
Click to expand...
Click to collapse
Please post v2.05. I wonder if we can go down to v2.05 for that option. And then when things are working right go back to v2.46.
Either way ES File Explorer / Root Setting will not work for your right. Not matter what?
Hope I can get past this bug before updating my other 3 FTV1's.

Just ran into something else that is very odd. I've been using Amazon FireTV Utility App v0.66 to access ADB non-Root & Root Shell. Decided to switch to the stand-alone "adb-setup-1.4.3" to see if that would help with the SU commands. But I found that as soon as I give it the "adb shell su" command. Even if SuperSU has been granted full access on a fresh install of the PreRooted Rom on the FTV1. The "[email protected]:/ # _" line gives me a blinking _ & it won't let me input anything else. On the FTV1's screen it says "ADB Shell (2000)" was granted root access each time. But I can't get past that. Is like ADB never receives the granted access response. Then I have to CTRL+C to be able to input anything & exit. This happens whether I opened the CMD with & without Admin rights on my Windows 8.1 PC.
Gonna try downgrading to adb-setup-1.4.2 but I doubt it will make a difference. So the bugs are bunching up. Seems SuperSU is not being installed or allowed to work properly. Any help would be appreciated.
Forgot that on FireOS 5 you have to break the command.
First "adb shell" to get "[email protected]:/ $" & then just "su" to get to "[email protected]:/ #" without it freezing.
The /SDCard list still had the same response though.
"lrwxrwxrwx root root 1970-01-07 19:45 sdcard -> /storage/emulated/legacy"

Solution:
First let me start by Thanking @rbox , @AFTVnews.com , @zroice , @phresch for all their work & feedback.
Was finally able to test multiple options & found a reproducible solution to this problem. The key was in @zroice post about Holo Themer.
https://forum.xda-developers.com/fi...w-to-supersu-xposed-app-t3552590#post71703744
Basically you got to make sure you install or have installed the latest version of BusyBox & XPosed & HDXPosed Module. And to have activated Holo Themer from within XPosed so you can run the SuperSU APK that comes with the PreRooted Rom. SuperSU should ask you to update. Once you have done a "Normal" update like we did when we first rooted our FTV1's then that should fix the Root Option fail that ES File Explorer & other apps have had. I am guessing the problem comes when we uninstall or wipe our FTV1's during our FireOS 3 to FireOS 5 update. Some of us thought BusyBox & Xposed would not be as important to functionality on FireOS 5 as it was on FireOS 3.
Make sure you only activate Holo Themer on a per needed basis. Since it will make your FTV reboot randomly if you leave it on all the time.
And like always. As long as you installed TWRP correctly. You can always start anew with a wipe (NEVER WIPE SYSTEM) & install of the latest PreRooted ROM. I would also recommend having all the files you know you will need in a USB drive or SDCard in FTV2's case ready to go & in separate folders before you start flashing away. Makes things much easier.
If you forgot how to install BusyBox or XPosed you can always find how in the many guides over @ AFTVNews.com . For me even the old FireOS 3 guides & FTV2 guides help as a good refresher or visual confirmation.

Android 10 0 bytes available in "root"

I rooted my Pixel 3a XL with magisk on Android 10, and after when looking at my file browser I see that the "root" directory has 0 bytes free? What the heck?
I re-flashed stock factory image and checked again and it still says 0 bytes available. Anyone know what is going on here?
EDIT: I figured it out.

Ravoz88 said:
I rooted my Pixel 3a XL with magisk on Android 10, and after when looking at my file browser I see that the "root" directory has 0 bytes free? What the heck?
I re-flashed stock factory image and checked again and it still says 0 bytes available. Anyone know what is going on here?
EDIT: I figured it out.
Click to expand...
Click to collapse
It would be nice if you posted your solution, in case others have the same situation.

poncespr said:
It would be nice if you posted your solution, in case others have the same situation.
Click to expand...
Click to collapse
I'll be honest, when I wrote that edit I was pretty frustrated. I couldn't figure out what was wrong, and I posted my question to several websites and didn't get any responses.
But you are correct, I should have posted what I learned here.
With Android 10, I've now read, that they switched to a new ext4 file system. And "system" is now read only, and can not be written to. Because it is now read only, file browsers see "root" as having 0 bytes of available space.
I have read that even with administrative access (root), the partition still can not be written to. Considering adaway could not modify the host file, with root access, this is obviously true.
Root programs, like adaway, will need to use a "systemless" method now. Which adaway does have in its settings.
I am not an expert, but this is what has happened as far as I understand it.