Introduction:
The padfone X was released last friday and I wanted TWRP. As you may know; @Dees_Troy is on vacation. So, I hacked together this "repack" version which should have all features in order. One caveat with this version though, when launching recovery after it's installed, the screen must time out (2-minutes) before you can push power and see it.
Warning:
Even though you may simply be using your device and just running apps, you are modifying your device. There is no 100% back to stock. You can find a fastboot flashable stock recovery here, but there is no stock system. While this mod did not trigger a "modified status" on my device, I cannot guarantee the same for you. This is a very new device and unless you're one of the few, brave and anxious, it may be in your best interest to wait until a stock firmware update, back-to-stock flash, or even an official XDA-Developers forum has been created for this device.
you will need:
1.The Unofficial TWRP recovery image
2.SuperSU installed on your device
3.TowelRoot installed on your device. You will need to enable third-party sources.
4.Terminal access (pick the one you're more comfortable with)
4a.ADB
4b.Terminal emulator
installation:
If you chose to use ADB, then use these ADB Instructions. Otherwise skip down to Terminal Emulator Instructions.
ADB Instructions
Ensure you have installed SuperSU and TowelRoot.
Launch the TowelRoot app, follow instructions, and let it reboot your device.
navigate to the folder you downloaded ADB (and dll's if you're on windows) and execute the following command.
Code:
adb shell "curl 'https://builds.casual-dev.com/files/Asus/Padfone%20X/TWRP-Nexus5repack-AO1.img'>/sdcard/recovery.img; su -c 'dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;"
check your device for any pop-ups and grant root access to shell.
wait 2 minutes after the screen is black, and then press power button. This is due to a difference between Nexus5 and PadfoneX which will be fixed in an official version later.
Terminal Emulator Instructions
Ensure you have installed SuperSU and TowelRoot.
Launch the TowelRoot app, follow instructions, and let it reboot your device.
Launch Terminal Emulator and copy-pasta the following into it.
Code:
curl 'https://builds.casual-dev.com/files/Asus/Padfone%20X/TWRP-Nexus5repack-AO1.img'>/sdcard/TWRPrecovery.img; su -c 'dd if=/sdcard/TWRPrecovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;
check your device for any pop-ups and grant root access to shell.
wait 2 minutes after the screen is black, and then press power button. This is due to a difference between Nexus5 and PadfoneX which will be fixed in an official version later.
Conclusion
Congratulations, you've got TWRP installed on your device. Now you can back up, restore, and install TWRP Flashable Zips. Please leave a comment and tell others how it worked. This worked great for me, Image below.
{
"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"
}
@Dees_Troy has a helpful suggestion:
Might be worth mentioning Settings -> Screen and lower the screen timeout to help get the screen up and running sooner
Whatever you do, don't turn off the screen timeout though
Click to expand...
Click to collapse
By turning down the screen timeout you only need to wait for two minutes, one time. Turn it down to 30 seconds to reduce the wait time.
Again, this is temporary for this unofficial build. I will update these instructions later when we have a proper solution to perform the needed hardware reset.
I can't wait to see development for this phone!!!! Thank you for all your hard work.
This is great, now all we need is a device thread.
What do we need to do , in order to get that going ? this device has great potential !!!
Adam have you put on the screen protector i saw you bought from ATT? i can't figure out how to properly place it because very time i go into tablet mode and i pull the phone out the phone protector always has a bubble or two from sticking to the tablet ... not sure if that makes sense lol
AdamOutler said:
Introduction:
The padfone X was released last friday and I wanted TWRP. As you may know; @Dees_Troy is on vacation. So, I hacked together this "repack" version which should have all features in order. One caveat with this version though, when launching recovery after it's installed, the screen must time out (2-minutes) before you can push power and see it.
Warning:
Even though you may simply be using your device and just running apps, you are modifying your device. There is no 100% back to stock. You can find a fastboot flashable stock recovery here, but there is no stock system. While this mod did not trigger a "modified status" on my device, I cannot guarantee the same for you. This is a very new device and unless you're one of the few, brave and anxious, it may be in your best interest to wait until a stock firmware update, back-to-stock flash, or even an official XDA-Developers forum has been created for this device.
you will need:
1.The Unofficial TWRP recovery image
2.SuperSU installed on your device
3.TowelRoot installed on your device. You will need to enable third-party sources.
4.Terminal access (pick the one you're more comfortable with)
4a.ADB
4b.Terminal emulator
installation:
If you chose to use ADB, then use these ADB Instructions. Otherwise skip down to Terminal Emulator Instructions.
ADB Instructions
Ensure you have installed SuperSU and TowelRoot.
Launch the TowelRoot app, follow instructions, and let it reboot your device.
navigate to the folder you downloaded ADB (and dll's if you're on windows) and execute the following command.
Code:
adb shell "curl 'http://builds.casual-dev.com/files/Asus/Padfone%20X/TWRP-Nexus5repack-AO1.img'>/sdcard/recovery.img; su -c 'dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;"
check your device for any pop-ups and grant root access to shell.
wait 2 minutes after the screen is black, and then press power button. This is due to a difference between Nexus5 and PadfoneX which will be fixed in an official version later.
Terminal Emulator Instructions
Ensure you have installed SuperSU and TowelRoot.
Launch the TowelRoot app, follow instructions, and let it reboot your device.
Launch Terminal Emulator and copy-pasta the following into it.
Code:
curl 'http://builds.casual-dev.com/files/Asus/Padfone%20X/TWRP-Nexus5repack-AO1.img'>/sdcard/TWRPrecovery.img; su -c 'dd if=/sdcard/TWRPrecovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;
check your device for any pop-ups and grant root access to shell.
wait 2 minutes after the screen is black, and then press power button. This is due to a difference between Nexus5 and PadfoneX which will be fixed in an official version later.
Click to expand...
Click to collapse
Didn't work for me. Just look like in TE it kept looking for a response back from the server. I tried to download the img manually and looks like the server is down or something.
FUZER384 said:
Didn't work for me. Just look like in TE it kept looking for a response back from the server. I tried to download the img manually and looks like the server is down or something.
Click to expand...
Click to collapse
It's working now. Server was, in-fact down earlier.
As they (nearly) share the same hardware, do you think it would be possible to compile a working recovery from Asus PadFone Infinity 2 (A86) sources?
Here is a link: http://www.asus.com/Tablets_Mobile/The_new_PadFone_Infinity/HelpDesk_Download/
(or: http://dlcdnet.asus.com/pub/ASUS/Mo...dFone_Infinity/PadFoneT004-1012394-kernel.zip for a direct link)
As Asus has not released PFX kernel sources on their site, I think it could be useful.
Demazda said:
As they (nearly) share the same hardware, do you think it would be possible to compile a working recovery from Asus PadFone Infinity 2 (A86) sources?
Here is a link: http://www.asus.com/Tablets_Mobile/The_new_PadFone_Infinity/HelpDesk_Download/
(or: http://dlcdnet.asus.com/pub/ASUS/Mo...dFone_Infinity/PadFoneT004-1012394-kernel.zip for a direct link)
As Asus has not released PFX kernel sources on their site, I think it could be useful.
Click to expand...
Click to collapse
Not without a device in-hand. I won't try to troubleshoot without it.
However, I use mkbootimg_tools and it requires a Linux system, not windows.
to get reccovery.img
Code:
adb shell su -C dd if=/dev/block/platform/*/by-name/recovery of=/sdcard/recovery.img
adb pull /sdcard/recovery.img
to uncompile original boot.img
Code:
mkboot recovery.img oringialoutput
this opens recovery.img and creates a ramdisk from it which you can freely edit. Now, do the same with TWRPRecovery.img
you will copy the following folders from the TWRP ramdisk to the originaloutput ramdisk. but heed the notes here.
/sbin -- replace only recovery, but copy all files over to the new device.
/res and /etc -- do not replace files, but add in TWRP files to this and its subdirectories.
/supersu -- this does not exist on the new ramdisk, so just copy it.
you will have to navigate to originalrecovery/ramdisk/system, then copy /system/bin into /sbin, then delete /system/bin, finally link /system/bin to /sbin. the positioning is important and you cannot use fully qualified paths to link the files here. it must be linked to ../sbin, specifying one folder up, a folder called "sbin", not /home/username/whatever...
Code:
cd originalramdisk/system/
cp ./bin/* ..//sbin
rm -rf ./bin
ln -s ../sbin
And then you're ready to repack.
Code:
mkboot originalramdisk myNewRecovery.img[code]
now you can copy myNewRecovery.img to your SDCard and flash it using the DD method I showed in the OP.
Oh, I thought you had the device, my bad.
Also, sorry, this may be off-topic (but still related to PadFone and development), but how hard do you think it would be to port CyanogenMod to a PadFone? Not for the PadFone X but for another one, knowing that I managed to build a recovery from source and that it's working, but that I've never managed to make the compiled rom itself boot?
Demazda said:
Oh, I thought you had the device, my bad.
Also, sorry, this may be off-topic (but still related to PadFone and development), but how hard do you think it would be to port CyanogenMod to a PadFone? Not for the PadFone X but for another one, knowing that I managed to build a recovery from source and that it's working, but that I've never managed to make the compiled rom itself boot?
Click to expand...
Click to collapse
This is a Padfone X forum. I can't help you any more than I have. Locate a developer with a Padfone 2 and ask him questions. I gave you instructions to try to create your own. I cannot do more.
AdamOutler said:
This is a Padfone X forum. I can't help you any more than I have. Locate a developer with a Padfone 2 and ask him questions. I gave you instructions to try to create your own. I cannot do more.
Click to expand...
Click to collapse
It's for the PadFone Infinity and I already have a CWM working, my question was about building a ROM. Also it seems that no developer has this device, as it's never beed released in the US.
But no problem, thanks anyway.
Also, sorry but I might not have said it properly in my first post: I did not ask you to build a recovery PadFone Infinity 2 (I don't have this device), I just gave you the kernel source because I thought it could help you build a PadFone X recovery from those sources, as they are both similar in hardware and from the same manufacturer.
Can anyone tell me how to build a cwm recovery for Asus Zenfone 5 ?
I cant take the recovery.img from my system ...
So I seem to have really screwed something up with a few features by trying to save space by integrating various GApps updates to the ROM. I cannot get a keyboard at all during boot-up for any purpose (eg encryption, which my employer requires to use this on their networks).
I don't suppose anyone has a stock nandroid of /system on hand I could download?
EDIT: I see there isn't one yet, but if you make one, anyone, I'd be willing to host it on my Mediafire account.
EDIT 2: Where might I find this flashable stock recovery? I must be overlooking it.
EDIT 3: I see. The link to the unofficial TWRP points to the stock DD pull. I already have a DD pull I just did so ignore that question aboug stock recoveries.
Anyone else having SERIOUS device issues after flashing this?
EDIT: Not demanding updates/etc, just asking/inquiring.
I have ADB installed but running "adb devices" does not show any device connected. My windows 7 shows the storage (internal and external SD card) but windows does not recognize the "ASUS Android Composite ADB Interface".
Any advice where to find drivers for windows 7 for my Padfone X ?
Thanks !
JD
dorj1234 said:
I have ADB installed but running "adb devices" does not show any device connected. My windows 7 shows the storage (internal and external SD card) but windows does not recognize the "ASUS Android Composite ADB Interface".
Any advice where to find drivers for windows 7 for my Padfone X ?
Thanks !
JD
Click to expand...
Click to collapse
LOL! did you ever plug it into the computer? It has the drivers on it.
AdamOutler said:
LOL! did you ever plug it into the computer? It has the drivers on it.
Click to expand...
Click to collapse
For me they installed automatically
Sent from my ASUS PadFone X using XDA Free mobile app
Does anyone have new download link for twrp recovery , link is dead
Related
SINCE FREE X10 IS NOW BETA, THIS HOW TO IS NO LONGER VALID
Hello world !
I noticed there was nothing to explain simply how to install the increible X10 Free Rom in dual-boot with your regular 2.1 rom of Zdzihu.
** No responsability for anything, you are all responsible of what you're doing !! **
** Please follow ALL these steps. Don't try to be Indiana Jones by flashing your device without all the tools needed !!! **
INSTALL
(for 1st install)
Before attempting anything, make sure you have AT LEAST 50% of battery charge. Don't try anything with low battery, you can abort the flashing and brick your device !!!
Please make sure you're also running a 2.1 rom (Generic, nordic, official, custom...)
- Download FreeX10 v0.0.1 file (NOT 002 yet !!!)
- Download Android SDK
You don't need to save the entire archive (but you can), you just need the Tools folder (because it contains ADB, the Android Debug Bridge we need to install files).
- On x10 :
Download and install Busybox (from Market), make sure it says "Done!".
Connect your x10 in USB, mount SD card, and copy files FreeX10.zip and install on the root of your SD Card.
Enable USB debugging (Parameters > Applications > Development).
- On your computer, go in the Tools folder, open a DOS prompt (for Windows 7 : hold CAPS + right click, you'll see Open a DOS prompt) and
type :
Code:
adb shell
(this will run ADB shell... You will get a "$")
- Type :
Code:
su
(this will make you super-user, you will get a "#")
- Type :
Code:
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && /data/install
(It will display "11", "1+1", or "inflating:..." ...)
- Wait, have a beer, pray for your sins for your phone not to turn into a $600 brick
- One minute after, when it shows
Code:
All done, please reboot!
, reboot ! (But you can gently quit ADB by typing
Code:
exit
twice
)
Note : regarding me, I typed "exit" to quit ADB, I turned off ADB on phone and disconnected USB. You can do, it's even safer
- Wait up to 5 minutes for the phone to boot, it is NORMAL !!!! It looks stuck on Sony Ericsson logo and/or on Free X10 logo, it's NOT stuck !!! You MUST wait !!!!
- It will finally run normal, your phone is alive and 2.2-hearted !!
You are now eligible to install v0.0.2 (as it comes as an update).
Dual Boot usage
This rom comes with a great Dual Boot, which means the 2.2.1 is installed safely apart from your original 2.1 rom. This means you can switch back anytime to stock rom. To say it simply :
- Your Android 2.1 is here, and no changes are made to it (apps, version, etc etc). It is stored as it has to be, in the internal 1Gb phone memory storage (called the "NAND").
- FreeX10 (2.2.1) is running from image files (like .ISO files) stored in your SD Card. This means the two Android are living together peacefully, without affecting (theorically) each other.
FreeX10 mainly creates a bootloader, for you to choose whether to test 2.2.1, or go back to 2.1 for your daily use.
- To run 2.2.1 : do nothing (default boot)
- To run 2.1 : press any key at boot, when it shows "Sony Ericsson".
Notes when upgrading to v0.0.2 :
- As Android is stored into image files (.IMG), upgrading will wipe out all your content (it does a fresh "install"), make backup of what you need !
- to avoid future bugs, altough you're not forced to do, do the routines to make sure Wifi, root, packages install, ... work. This is because USB debug can break, so you won't be able to use ADB to fix these bugs
- Root is strongly recommended to work, because it's cool and because the CPU performance is set to highest : stuck at 998MHz all the time, it will drain your battery like hell ! You can switch it back to original power saving plan (ondemand plan) by using (ie) SetCPU. Root required !
If your Android goes instable, does not work anymore, or you want a fresh install after lots of tests, simply drag and drop the original v0.0.2 .img files on your SD card. This will make you boot into a fully fresh install.
For all bugs, commands, etc.. Please go first to this excellent (and very easy) thread !!
Nice..
How about one on AOSP 2.1
Perceval from Hyrule said:
Hello world !
I noticed there was nothing to explain simply how to install the increible X10 Free Rom in dual-boot with your regular 2.1 rom of Zdzihu.
Click to expand...
Click to collapse
nice dummies HOW TO
and ohhh my god there is dummies
all comands needed
INSTALLATION
1. Download the rom package (FreeX10_alpha-release_0.0.1.tar.bz2)
2. Unpack it to the root (main folder) of your SD Card
3. Connect your phone in USB Debugging mode
4. Open ADB shell, switch to root user (SU)
5. Issue the command
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && ./data/install
6. Reboot when installation is finished
7. Enjoy
---------------------------------------------------------------------------------------------
CHANGE BOOT PRIORITY
Copy chargemon.txt file to
/system/bin
folder ON YOUR ORIGINAL 2.1 ROM, NOT FROYO!!!
---------------------------------------------------------------------------------------------
UPGRADE TO 0.0.2 VERSION
Boot into 2.1, unpack the content of FreeX10_alpha-release_0.0.2-UPDATE.tar.bz2 into
/sdcard/FreeX10
folder and reboot into updated 2.2!
NOTES:
1. SMS vibrate is disabled by default; open Messaging, press MENU button -> settings -> vibrate -> always
2. If you don't have radio (network) after 1st boot, please open ADB shell and issue this command:
killall servicemanager
3. If you don't have root access, please open ADB shell and issue this command:
chmod 4755 /system/bin/su
---------------------------------------------------------------------------------------------
hope it helps too
UPDATE TO v.0.0.2
Note : you can only update from 0.0.1 to 0.0.2. I mean you can't do a fresh install of 0.0.2, you MUST have 0.0.1 installed !
- Download v0.0.2 from main thread.
- Run your device on your regular 2.1 rom (while off, power on, and press any button when it displays Sony Ericsson logo)
- Mount the SD Card, then copy data.img and system.img from the archive into the folder /FreeX10. Replace the two .img files.
- Reboot into 2.2, have fun ^^
OmegaRED^ said:
Nice..
How about one on AOSP 2.1
Click to expand...
Click to collapse
I'll try to do one if I get time, but I need a fully working ROM as my phone is useful for my life (still waiting for 2.1 stable )
Thanks for your posts all, it will help everybody who want to try the 2.2
(as it is safe and running from SD card, very very very cool idea !)
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
I found drawing a pentagram in human blood and chanting a few words can do wonders too.
fastphil said:
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
Click to expand...
Click to collapse
root privileges do you have it?
unmount sdcard
OmegaRED^ said:
I found drawing a pentagram in human blood and chanting a few words can do wonders too.
Click to expand...
Click to collapse
sarcasm...love it
rendeiro2005 said:
root privileges do you have it?
unmount sdcard
Click to expand...
Click to collapse
yes mate i do have root access titanium etc works fine just cant get adb shell to run
When i installed 2.2, it rebooted and when to the sony ericsson logo for almost an hour, does this mean i have to reinstall 2.1, and if so, i would i accomplish this
fastphil said:
yes mate i do have root access titanium etc works fine just cant get adb shell to run
Click to expand...
Click to collapse
and what about sdcard?
uncheck nount/unmount
rendeiro2005 said:
and what about sdcard?
uncheck nount/unmount
Click to expand...
Click to collapse
done that too
fastphil said:
done that too
Click to expand...
Click to collapse
can you post a screenshot of cmd?
ok will do
I am still having problems also...
after I type the cmd...
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && /data/install
it just says:
1+1 records in
1+1 records out
520 bytes transferred in 0.003 secs...
#
so, where am I going wrong?
fyi, I am trying to install v001, not the update, and the phone is rooted, busybox is installed. Sorry, but I have tried for a while now and I finally have to just ask for help. Thanks guys.
here pic off cmd
{
"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"
}
fastphil said:
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
Click to expand...
Click to collapse
Does it work when your run "adb" command only ?
It looks to me your error is because you're not in the folder where adb.exe is
It is in folder tools, if you try to run it from root directory (where is the android app with nice icon) it won't work for sure
Edit: didn't see your screenshot >> you are NOT in the correct folder !! (so Windows is searching for a registered command which does not exist, I think there's a thread somewhere on how to add it as a registered (I mean global) command)
You must download Android SDK (22mb... Lmao regarding 4gb for iOS ), extract the archive and go in the tools folder. Here is adb.exe.
when i try & run adb exe it does not open it just closes right away
Note from developer: If you want to block OTA updates, just use the adb hijack app once (click the button on it once) and then you can run the OTA block part of this script and every other mod for it. The hijacker is right below this V
If you already ran this script but want to apply the mods from an update to the script: Just use this method to be able to rerun the script
NOTE: Anyone who is having problems with drivers, http://forum.xda-developers.com/showthread.php?t=1363652 <-- That explains the two most common problems.
Step by step video from my friend Albert to gain root access:
http://www.youtube.com/watch?v=1zbT1Fj38nE
This also includes a gApps install section in it incase you decide you want to run that.
You may NOT use the included script in your work without atleast asking me as of now, this may change in the future but I dont want to have to hop from thread to thread just to offer support when I can keep the answers organized for all to find. So please just ask first.
Thanks.
Information:
I have gotten zergRush to work on the nook tablet as well as created a batch script for you to run to allow you to root your tablet. This does NOT unlock the bootloader software/hardware checks this is just so you can remove whatever unnecessary crap you wish to get the **** off your device.
Features:
Root (obviously)
Gapps install
De-bloat menu
System mods (New gallery, email, keyboard, and live wallpaper support)
Launcher install (Choice of 3!)
Homecatcher installer (if you install a launcher in the previously mentioned feature)
Root check
USB Vendor ID check.
Needed files for root:
You need drivers first:
http://dl.dropbox.com/u/15069134/usbdrivers.zip
here is an app to pull up usb debugging menu
http://li362-167.members.linode.com/gapps/non_google/tgps_launcher.apk
Code:
<robertely> Also note, that while that box will remain checked, the setting is not persistant.
<robertely> So you have to flick the top 'Usb Development' box twice to get it working.
Download Link for rooting script:
http://dl.dropbox.com/u/15069134/Nook&Zergy.zip
Code:
MD5sum
5df962260797ec4e3d80e107bca1fdb2
How to get adb debugging enabled:
Download the apk provided in the second download link to be able to access the menu *if you're just installing an app the first time, it will pull up the menu anyway but this is more for AFTER you have root as a convienance to access usb debugging and whatnot. Just try to install the apk *or open it if you already set unknown sources* and you will get a prompt to allow non-market apps. Click settings then you should be able to see "Unknown sources" check that followed by going into "Development" and check the 2 "Usb Debugging" boxes and uncheck "auto mount" then your nook tablet is ready to be used in debugging mode.
Instructions to root:
1. Download the "usbdrivers" zip
2. Download the "Nook&Zergy.zip"
3. Extract both to a folder C:\ntroot\
4. Now you should see the following files and folders inside c:\ntroot:
5. Run "runmefirst.bat" and follow the instructions.
6a. When the batch file opens the device manager, If you don't see a broken device icon next to "NOOK Tablet" then you may have some other generic drivers taking over. Not sure how to remove them so you will have to move to another PC that has never had a tablet hooked up and start over.
6b. If you do see NOOK Tablet with a broken device icon.. then right click and choose "update driver". Choose "Let me specify where the driver is" and browse to the c:\ntroot\usbdriver folder and hit ok. It should install and you can click "OK" to the warning about unsigned drivers.
7. Run "NookandZergy.bat" and follow the instructions
7a. If you see a long string of numbers/letters it's your device
Now you should have root.
How to Unroot and Undo system mods: Check out this thread:
Code:
Changelog:
7.5: Added file to block OTA's directly instead of needing titanium backup and did a few script fixes as well as added brianf21's hiddensettings app.
7.0.1: Fixed minor bug where systemui mod was not being properly installed (wrong command was used) NOTE: You will get force closes from the systemui until the script finishes and reboots your tablet.
7.0: Allowed recognition of users that used ADB Hijacker app to allow for system mods to occur even if you didnt choose them with the script originally
6.0: Added ricochet1k's SystemUI mod to have perm back / menu button on status bar + have N automatically redirect to home on first click
6.0: (continued) fixed the sdcard check for users since Zerg causes auto unmount of the sdcard
5.2: Added check for sdcard to install files
5.0.1: Added option for access to the titanium backup and push them to sdcard even if you are already rooted
5.0: Added Titanium backup as well as files needed to block OTA's
4.7: New Market added (3.4.4)
4.6: Added permissions fix.
4.5.5: (Debloater): Added Extreme Debloater option
4.5: Debloated updated to be a customized menu (Has a menu included now) [URL="http://forum.xda-developers.com/showpost.php?p=20229004&postcount=625"]found here[/URL]
4.1: Removed bugs
4.0: Included de-bloater and launcher install (you get to choose!)
3.5: Updated to check for proper USB Vendor ID as well as check for root.
3.0: Updated to include system app replacements (Keyboard, Email, Gallery) As well as adding live wallpapers for other launchers. You need to choose to run this part of the script same as gApps.
2.7: Updated Gapps to latest [9/30/2011]
2.5: Fixed a few minor typo's/bugs with the script
v2.1: Added usb vendor id addition to adb_usb.ini
v2.0: Rewritten script to allow for more user choices; added Gapps installer (thanks anlog); Added busybox installer apk and debug menu puller (allows you to access debugging menu)
v1.1 Updated superuser apk
v1.0: Official release
v.75: Updated to install SU and superuser.apk
v.5: Initial release
Code:
Credits:
Gojimi for his HomeCatcher.apk
Developers of ADW launcher for their APK
Developers of Go launcher for their APK
Syndicate Apps for their Honeycomb Launcher
anlog for finding out how to get nook color drivers to work and general testing
Team Revolutionary for their exploit
B&N for using android like good little sheep
suicideclown for bearing with me while I tried to get it to work on his computer until anlog found the driver fix.
Dsstrainer for the simplified instructions.
How to do it manually instead of running the Nook&Zergy.bat file (for linux or mac users or someone who wants to do it all manually)
Install drivers and follow instructions up until running the batch file then do the following commands in order:
Code:
adb push zergrush /data/local/zergy
adb shell "chmod 755 /data/local/zergy;cd /data/local/;./zergy"
adb wait-for-device install Superuser.apk
adb remount
adb push su /data/local/tmp/
adb shell cd /data/local/tmp;chmod 777 su;cd /;mount -o remount,rw -t rootfs rootfs /;
adb push su /system/bin/su
adb shell chmod 4755 /system/bin/su
Wanna buy me a coffee or something pretty for christmas?
Unroot method can be found here
Rooted nook tablet using my method
Taken from inside of barnes and noble;
{
"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"
}
Indirect said:
Alright, I know you all are going to say "We cant find usb debugging" but allow me to assist you. I found that it's in the development menu of where you enable side-loading of applications so just check that then get the zergrush exploit ran using this.
*I do not own a nook tablet so I cannot check, I just learned alot about it tonight while at a barnes and noble store and the guy who worked there was cool enough to try and help root it with me but since you need adb permissions to run the exploit, I couldn't do anything.
Download Link:
http://dl.dropbox.com/u/15069134/Nook&Zergy.zip
Click to expand...
Click to collapse
Wouldn't still need adb drivers to work in order to do this exploit? If both are possible, I'll gladly buy a nook tablet in order to see if it works (because I intended to buy one anyway if it got root).
I think it might use the nook color drivers but again, I can't test so if anyone has the specific drivers, post them.
Very interesting. I hope someone tries this soon.
Sent from my Samsung Legendary 4G, a Universe UTES phone, running "two.three.five"
I am willing to give this a try tonight. want to get in touch? If it works I will record video.
suicideclown said:
I am willing to give this a try tonight. want to get in touch? If it works I will record video.
Click to expand...
Click to collapse
Thanks. Let us know how it goes!
Sent from my Nook Tablet using Tapatalk
Yeah, add me on Gtalk.
[email protected]
Indirect said:
Yeah, add me on Gtalk.
[email protected]
Click to expand...
Click to collapse
I'll help out as well.
gtalk: [email protected]
I tried this quickly and cannot get it working, i have usb debug enabled however the first problem is that the device does not show up in ADB Devices. Second problem or at least i think it might be is that it defaults in to usb storage mode and while plugged in it cannot be altered from that mode. If someone could create a toggle app to change the default i believe this might help. As for the drivers i am looking and will report back later.
ITFloater said:
I tried this quickly and cannot get it working, i have usb debug enabled however the first problem is that the device does not show up in ADB Devices. Second problem or at least i think it might be is that it defaults in to usb storage mode and while plugged in it cannot be altered from that mode. If someone could create a toggle app to change the default i believe this might help. As for the drivers i am looking and will report back later.
Click to expand...
Click to collapse
People hit a wall here last night on irc, May want to hop in #nookcolor to chat about it.
*cough* http://dl.dropbox.com/u/15069134/add-ons.zip *cough* Put that into your android sdk directory and you have the drivers.
Very nice
Sent from my BNTV250 using Tapatalk
905 views, someone must've tried this by now
Sent from my Samsung Legendary 4G, a Universe UTES phone, running "two.three.five"
You need to add the Nook Tablet USB vendor-id to adb_usb.ini, otherwise adb will not see the device. Do not know what the Nook Tablet vendor-id is, but you can find it with serveral utilities.
I just added a zip that I found to add usb vendor ID and gives you the drivers.
Crap...
I got into the application settings menu and was able to allow sideloading, but the window closed before i could turn on usb debugging. I can't figure out how to get back into the menu, since when I try to install an APK it actually does it now instead of spitting out an error.
Looks like I'm going to have to factory reset. I'll try the root right after that and report results here...
BTW, are those drivers 32-bit or 64-bit?
WAIT here is an app to pull up usb debugging menu
http://dl.dropbox.com/u/15069134/me.tennkia.apr-1.apk
Indirect said:
I just added a zip that I found to add usb vendor ID and gives you the drivers.
Click to expand...
Click to collapse
i got USB debugging enabled (i sideloaded AnyCut and put a shortcut to Development on my home screen)
but i cant get adb to recognize my NT... already edited adb_usb.ini with 0x2080 as vendor id.
http://legacyschool.us.to/nookdev/nookcolor-easyADB.exe
^ use that
Indirect said:
http://legacyschool.us.to/nookdev/nookcolor-easyADB.exe
^ use that
Click to expand...
Click to collapse
no dice, still not recognizing NT
Disclaimer: You are responsible for insuring you keep a backup of your stock recovery!
See Post 7 for the Stock Recovery if you failed to keep a copy for yourself: Click here
Steps for Backing up Stock Recovery:
Code:
fastboot boot /path/to/TWRP.img
The above command will only boot the recovery and will not overwrite your stock recovery making it possible to backup your stock from within TWRP. Now backup your recovery partition from within TWRP. It will be saved on your device and named, recovery.emmc.win. You can rename it to recovery.img to flash it back via usage of fastboot or apply restore within TWRP given the original filename, recovery.emmc.win.
Or within a terminal using dd (aka Data Destroyer);
Code:
dd if=/dev/block/mmcblk0p19 of=/sdcard/stockrecovery.img
TWRP for MT2-L03
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"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"
}
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
Installation (PC):
- You MUST have an unlocked Bootloader! /* See Post 2 */
- Download TWRP Recovery
- Boot to your Bootloader
- Plug your device to your PC
- Open Command Window
- Type, then Enter:
Code:
fastboot flash recovery /path/to/TWRP.img
- Also, a video to demonstrate the process of installing TWRP - Credit goes out to @superbass311:
Installation (Device)(More Experienced Users Only!):
- You MUST have an unlocked Bootloader! /* See Post 2 */
- You MUST be rooted!
- Must have Busybox installed or a properly compiled DD binary
- Download TWRP Recovery
- Install a Terminal Emulator from the Play Store
- Type, then Enter:
Code:
su
Followed By:
Code:
dd if=/path/to/TWRP.img of=/dev/block/mmcblk0p19
Download:
- TWRP 2.8.0.0
CONTRIBUTORS
@Modding.MyMind
@xordos
@Shaky156
SOURCES
- Recovery built in a OmniRom 4.4.4 environment using device trees/kernel/dtb
- Stock Kernel
- Stock DTB
- TWRP source from Omnirom
- MT2-L03 Device Configuration Folder - My Github
VERSION INFORMATION
- Status: Stable
- Created 2014-09-22
- Last Updated 2014-09-22
Unlock Your Bootloader:
As we all know, you are not required to be rooted to install TWRP, however, you must unlock the bootloader on your device.
You must email [email protected] asking:
Hello I purchased the Ascend Mate 2 and I would like my bootloader unlock code.
SN: xxxxxxxxxxxxxxxxxxx
IMEI: xxxxxxxxxxxxxxxxxx
Thank you
Click to expand...
Click to collapse
You should get a response within 24 hours. In a situation where 24 hours has passed by than simply be patient or send another email. This is the 1st step to being able to unlock your bootloader (as of now)!
Here is a video to demonstrate to you viewers how you can go about unlocking your bootloader.
- Video credit goes out to @superbass311
*Reserved Again*
I will flash tomorrow. You just made the HAM2 the hottest phone out.
Sent from my MT2L03 using XDA Free mobile app
Thanks to all involved. Re-installed root using TWRP. Now Titanium Backup is working properly.
Flashed just now!
Backing up at the moment.
THANK YOU ALL!!!
How I did it:
Win 8 pc.
Phone booted and usb debugging allowed.
typed "adb.exe reboot bootloader" in cmd terminal
typed "fastboot flash recovery c:\adb\TWRP.img" in cmd terminal
I downloaded zip to my adb directory, also had to rename it too "TRWP.img" as download was "TWRP_MT2-L03_RECOVERY.img"
back up completed in 480 seconds!
Did have to play with TWRP settings as I hadn't used it in a while .
DID I SAY THANK YOU!!!
For anyone who is lazy to backup your stock recovery, I have uploaded my stock recovery image backup here, it should be same for all our MT2-L03 phone
This is backup of stock recovery, only use this image if you want to revert back from TWRP to Huawei stock crappy recovery.
http://tinyurl.com/qzxkm4x
FileName: recovery_MT2L03_mmcblk0p19.img
md5sum: 35703a1fe81917cb7930ab1e9e93e499
Edit: 2nd thought, they should be same, but let's make sure. Can anyone did (or going to) backup your phone stock recovery post the md5sum of yours? The ES file explorer can calc md5sum for a file.
Thanks iammudd, I think it is confirmed the recovery image is same for all MT2L03 phone.
Absolutely freakin' FANTASTIC!!!
Flashed it via fastboot with no problems.
I couldn't get MTP to work, but that's not a huge surprise to me as I've NEVER seen MTP work properly in TWRP on any device I've had sofar. I'd be interested to see if it works for anyone else.
So awesome that a root method is built right in too!
I think this is the verge of some huge things happening for our MT2-L03s!!!
Thanks for the great work!
TheGeekRedneck said:
Absolutely freakin' FANTASTIC!!!
Flashed it via fastboot with no problems.
I couldn't get MTP to work, but that's not a huge surprise to me as I've NEVER seen MTP work properly in TWRP on any device I've had sofar. I'd be interested to see if it works for anyone else.
So awesome that a root method is built right in too!
I think this is the verge of some huge things happening for our MT2-L03s!!!
Click to expand...
Click to collapse
Thanks for the info, right, mtp not work during my init testing as well. So other device are running twrp 2.8.0 or later?
PS, there are another 2 known issus,
* date is ~1970
* off mode charging
xordos said:
Thanks for the info, right, mtp not work during my init testing as well. So other device are running twrp 2.8.0 or later?
PS, there are another 2 known issus,
* date is ~1970
* off mode charging
Click to expand...
Click to collapse
Check your hangouts
Well done everyone ! Excellent stuff.
I suppose you know what my question will be,lol, but is it feasible to be able to port this to the MT2-L05 or other Chinese models?
If it's likely to be feasible, would it be possible to have your permission to attempt a port, or do you think as the underlying processors are different
it would probably wiser to start from scratch?
Either way, good work again !
xordos said:
* date is ~1970
* off mode charging
Click to expand...
Click to collapse
Interesting that backup filename is 1970-03-23 but the timestamp is 1979-12-31 23:00 on the phone.
After FTP'ing them onto Win7, their last modified times are 2013-12-31 22:00.
The device configuration folder used to build TWRP is available on my github which you can find the link in the OP under "SOURCES". If you have any knowledge on this stuff then feel free to look it over and throw some patches my way. As it stands, mtp isn't working properly however, mtp has only been known to work for a very small select list of devices. A very small list. As for the time stamp, this isn't much of a concern on my part as it is merely cosmetic. However, the problem with it would most definitely be the result of the actual TWRP source and not the configuration folder (device tree). Feel free to look further in to it if it is bothersome.
Right now, my goal is to see if I can resolve the mtp issue if it happens to be at all plausible since the mtp featured in TWRP is still fairly new and has much more work to be done with it over at TeamWin.
Currently looking in to offmode charging as well. This is merely cosmetic. But would be nice to have.
xordos said:
For anyone who is lazy to backup your stock recovery, I have uploaded my stock recovery image backup here, it should be same for all our MT2-L03 phone
This is stock, only use this image if you want to revert back from TWRP to Huawei stock crappy recovery.
http://tinyurl.com/qzxkm4x
FileName: recovery_MT2L03_mmcblk0p19.img
md5sum: 35703a1fe81917cb7930ab1e9e93e499
Edit: 2nd thought, they should be same, but let's make sure. Can anyone did (or going to) backup your phone stock recovery post the md5sum of yours? The ES file explorer can calc md5sum for a file.
Click to expand...
Click to collapse
Yes, md5 are the same and fc on Win7 of your/my versions are the same.
4L0M said:
Well done everyone ! Excellent stuff.
I suppose you know what my question will be,lol, but is it feasible to be able to port this to the MT2-L05 or other Chinese models?
If it's likely to be feasible, would it be possible to have your permission to attempt a port, or do you think as the underlying processors are different
it would probably wiser to start from scratch?
Either way, good work again !
Click to expand...
Click to collapse
Hi, just saw your another post about MT2-L05 RESOURCES. I am not sure if Modding.MyMind have time or not to do this. Maybe we can do some quick test, if worked, then his build (after small update) can support L05 phone as well.
Sending you a PM.
Just flashed TWRP recovery, and it's working great!
Now we just need a CyanogenMod ROM. While I'm thinking about it, when does Android "L" officially get released? It would be nice to just jump from Jelly Bean to L.
xordos said:
Hi, just saw your another post about MT2-L05 RESOURCES. I am not sure if Modding.MyMind have time or not to do this. Maybe we can do some quick test, if worked, then his build (after small update) can support L05 phone as well.
Sending you a PM.
Click to expand...
Click to collapse
I'd be willing to be a guinea pig for the Mt2-l05 if you need more people.
I second that
Sent from my MT2L03 using XDA Free mobile app
Gir357 said:
Just flashed TWRP recovery, and it's working great!
Now we just need a CyanogenMod ROM. While I'm thinking about it, when does Android "L" officially get released? It would be nice to just jump from Jelly Bean to L.
Click to expand...
Click to collapse
L should be released sometime in October I believe, alongside the new Nexus phone and tablet.
Supposedly the HAM2 is getting an EMUI 3.0 update (KK) in November. I don't know if the US version is included though.
It's finally here! Recovery for the Fire TV 2. This is based off of TWRP and the way versions will work is I will increment the last digit in the version as I make updates. So 3.0.0-1 is my first release based off of 3.0.0. The downloads will be numbered starting at v1, and at the bottom of the post it will explain what is contained within each version.
{
"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"
}
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
Installing this requires root. If you are not rooted, please see my FireTV 2 Recovery Installer page.
Installation
You can copy the files to /sdcard, a USB storage device, or an sdcard. I will be using /sdcard in the instructions, but you can replace it with /storage/usbotg for USB or /storage/sdcard1 for an sdcard.
Copy the zip file to your destination.
Connect adb
Code:
adb connect IPADDRESS
Open an adb shell
Code:
adb shell
Run the zip file (replace vX with the actual version you downloaded). This will automatically run su, so make sure to accept the prompt if necessary.
Code:
sh /sdcard/firetv2_recovery_vX.zip
Reboot
Upgrade
You may repeat this to upgrade to a newer version, or you can install an updated pre-rooted rom, as I will be uploading new versions of those with every version of recovery.
Notes
This includes bootmenu. For everyone that loved the old FireTV 1 bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.
USB storage, USB keyboard/mice, and sdcards should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.
You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.
ROMs
Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.
Kernels
The bootloader is locked and you cannot flash kernels. If you do attempt to flash a kernel, you will brick it.
Installing zips
You can push zips to /sdcard, put it on a USB storage, put it on an sdcard, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Stuck in a loop?
If you cannot boot normally and keep going back to the bootmenu, wipe Cache from Wipe -> Advanced Wipe.
If that doesn't work, ensure Cache is not mounted from in the 'Mount' menu and run this from an adb shell:
Code:
mke2fs /dev/block/platform/mtk-msdc.0/by-name/cache
Source Code
You can find the source code here:
https://github.com/androidrbox/sloane-2ndinit
https://github.com/androidrbox/android_bootable_recovery
WARNINGS
It is extremely important you never reboot after a failure. This will most likely lead to a brick. If recovery is hung, you can use adb shell to run
Code:
killall recovery
to restart it
It is also extremely important to never reboot after wiping /system.
If you wind up bricking, you must use the Unbrick Image to unbrick.
Finally, thanks to everyone who has donated to me and those that helped to get me my FireTV 2.
Changelog and Downloads:
April 8, 2016 - v6 (md5sum: 79c1a3efbac86618fa2cdbb4901fbd77)
This should prevent auto flashing amazon updates.
This includes 2ndinit version dee776 and TWRP version 3.0.0-5.
February 14, 2016 - v5 (md5sum: 16c957c86f1f61160e14a55819610707)
This should fix the problems certain keyboard were having in recovery.
This includes 2ndinit version dee776 and TWRP version 3.0.0-4.
February 12, 2016 - v4 (md5sum: 15c6d375607839cac4b186a2b68b8b0d)
This includes 2ndinit version 743aa4 and TWRP version 3.0.0-3.
These are just changes related to the unbricking image. No other functional changes.
February 8, 2016 - v3 (md5sum: b39a4dbe0c19080a97f602f37fda63ec)
This includes an updated script. You can now just run the zip instead of needing the zip and the script.
This includes TWRP 3.0.0-2.
Added a reboot recovery option in addition to reboot system. Now reboot system will reboot straight in to Android. Reboot recovery will reboot to the bootmenu.
Fixed restoring backups.
This includes the same version of 2ndinit.
February 7, 2016 - v2 (md5sum: 762621104d158d7ce4010bea725f7181)
This includes an automated script.
This has the same versions of 2ndinit and recovery as v1.
February 6, 2016 - v1 (md5sum: 7be673dd24489080eacdd0ad00feda51)
This comes with 2ndinit version fe3362 and recovery version 3.0.0-1
Awesome work!
Will try immediately! Thanks for posting this on weekend
Thankyou Rbox, i just saw this & its put a smile on my face. Just one question do you need to reblock the updates after recovery & root have been installed? Thanks
deanr1977 said:
Thankyou Rbox, i just saw this & its put a smile on my face. Just one question do you need to reblock the updates after recovery & root have been installed? Thanks
Click to expand...
Click to collapse
As long as you don't wipe data, updates remain blocked.
rbox said:
As long as you don't wipe data, updates remain blocked.
Click to expand...
Click to collapse
I downloaded both the zips from the Github, im already rooted on the previously rooted software & updates are blocked, im not sure if to wait for AFTV News to do a guide or not, im clued up but not to ADB or Terminal savey so i gonna look at the readme & see if i should try it tonight? I rooted with the video guide before & it was a breeze, i know it sounds easy but want to do it right. Can you give me a little more info on connecting the ADB or Terminal please if you arnt busy?
deanr1977 said:
I downloaded both the zips from the Github, im already rooted on the previously rooted software & updates are blocked, im not sure if to wait for AFTV News to do a guide or not, im clued up but not to ADB or Terminal savey so i gonna look at the readme & see if i should try it tonight? I rooted with the video guide before & it was a breeze, i know it sounds easy but want to do it right. Can you give me a little more info on connecting the ADB or Terminal please if you arnt busy?
Click to expand...
Click to collapse
If you don't want to deal with adb, use the installer.
rbox said:
If you don't want to deal with adb, use the installer.
Click to expand...
Click to collapse
Thanks mate, looking at this now. Will it delete any data on the system? Kodi, Amazon apps or External Sd card? Thanks in advance
deanr1977 said:
Thanks mate, looking at this now. Will it delete any data on the system? Kodi, Amazon apps or External Sd card? Thanks in advance
Click to expand...
Click to collapse
Installing recovery and roms does nothing to data.
rbox said:
It's finally here! Recovery for the Fire TV 2. This is based off of TWRP and the way versions will work is I will increment the last digit in the version as I make updates. So 3.0.0-1 is my first release based off of 3.0.0. The downloads will be numbered starting at v1, and at the bottom of the post it will explain what is contained within each version.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
Installing this requires root. If you are not rooted, please see my FireTV 2 Recovery Installer page.
Installation
Copy the contents of the zip to /sdcard on your FireTV.
Remount /system as read-write
Code:
mount -o remount,rw /system
Make the /system/recovery directory
Code:
mkdir /system/recovery
Copy 2ndinitstub
Code:
cp /sdcard/2ndinitstub /system/bin/ext4_resize
Copy 2ndinit
Code:
cp /sdcard/2ndinit /system/recovery/
Copy the recovery ramdisk
Code:
cp /sdcard/ramdisk-recovery.cpio /system/recovery/
Remount /system as read-only
Code:
mount -o remount,ro /system
Upgrade
You may repeat this to upgrade, but it is easier to just install a new pre-rooted rom. Every update for recovery I will make a new rom.
Notes
This includes bootmenu. For everyone that loved the old FireTV 1 bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.
USB storage, USB keyboard/mice, and sdcards should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.
You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.
ROMs
Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.
Kernels
The bootloader is locked and you cannot flash kernels. If you do attempt to flash a kernel, you will brick it.
Installing zips
You can push zips to /sdcard, put it on a USB storage, put it on an sdcard, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Source Code
You can find the source code here:
https://github.com/androidrbox/sloane-2ndinit
https://github.com/androidrbox/android_bootable_recovery
Finally, thanks to everyone who has donated to me and those that helped to get me my FireTV 2.
Changelog and Downloads:
Februrary 6, 2016 - v1 (md5sum: 7be673dd24489080eacdd0ad00feda51)
This comes with 2ndinit version fe3362 and recovery version 3.0.0-1
Click to expand...
Click to collapse
the commands are entered through adb correct......Also, once recovery is installed can I flash either of your pre-rooted roms or do I have to flash the version I'm currently on....i.e. if I'm on 5.0.4 I can only flash 5.0.4
thanks again for your great work!
dk1keith said:
the commands are entered through adb correct......Also, once recovery is installed can I flash either of your pre-rooted roms or do I have to flash the version I'm currently on....i.e. if I'm on 5.0.4 I can only flash 5.0.4
thanks again for your great work!
Click to expand...
Click to collapse
Yes adb shell. You can flash either version.
rbox said:
Yes adb shell. You can flash either version.
Click to expand...
Click to collapse
Awesome thanks rbox
Not working for me. everything is copied over and after reboot there is no menu. Amazon white logo for 5 seconds, than the colored logo and system is booted in less than 15 seconds.
aboshi said:
Not working for me. everything is copied over and after reboot there is no menu. Amazon white logo for 5 seconds, than the colored logo and system is booted in less than 15 seconds.
Click to expand...
Click to collapse
Same here. No boot menu. Reboot to recovery brings up the stock recovery as well.
dk1keith said:
Awesome thanks rbox
Click to expand...
Click to collapse
first command: mount -o remount,rw /system
in adb shell returns a mountermission denied
aboshi said:
Not working for me. everything is copied over and after reboot there is no menu. Amazon white logo for 5 seconds, than the colored logo and system is booted in less than 15 seconds.
Click to expand...
Click to collapse
retyre said:
Same here. No boot menu. Reboot to recovery brings up the stock recovery as well.
Click to expand...
Click to collapse
Both of you please run:
Code:
ls -lZ /system/bin/ext4_resize /system/recovery
dk1keith said:
first command: mount -o remount,rw /system
in adb shell returns a mountermission denied
Click to expand...
Click to collapse
You need to be root...
rbox said:
Both of you please run:
Code:
ls -lZ /system/bin/ext4_resize /system/recovery
You need to be root...
Click to expand...
Click to collapse
you mean by typing su?
dk1keith said:
you mean by typing su?
Click to expand...
Click to collapse
Yes, by typing su.
Code:
-rwxr-xr-x root shell u:object_r:system_file:s0 ext4_resize
-rw------- root root u:object_r:system_file:s0 2ndinit
-rw------- root root u:object_r:system_file:s0 ramdisk-recovery.cpio
aboshi said:
Code:
-rwxr-xr-x root shell u:object_r:system_file:s0 ext4_resize
-rw------- root root u:object_r:system_file:s0 2ndinit
-rw------- root root u:object_r:system_file:s0 ramdisk-recovery.cpio
Click to expand...
Click to collapse
Hrm... can you run
Code:
ls -l /system/bin/ext4_resize /system/recovery
also?
I can confirm that this process works on Update v5.2.6.8. Any other version beyond that your mileage may vary. "ADB debugging" and "Apps from Unknown Sources" should be enabled. I would like to thank the following members because without their resources this walkthrough wouldn't have been possible: @diplomatic for the exploit, @el7145 for leaving a cookie crumb trail of clues within his comments in this thread which I had to follow like the yellow brick road in order to repeat his success, @rbox for the custom recovery and pre-rooted image, and @AFTVnews.com because if it hadn't been for your article I probably would've never gotten my AFTV device rooted in time before the 5.2.6.9 OTA update. Oh, I almost forgot... and thanks @Chainfire for SuperSU . And also @teamfresno for the advice.
ACHIEVING TEMPORARY ROOT PERMISSIONS
1. Download and install ADB on your PC.
2. Download "mtk-su_r4.zip" and extract "arm64" folder in ADB install directory (C:\adb).
3. Run command below:
Code:
adb connect 192.168.0.XX
(IP address of your Fire TV device)
4. Transfer mtk-su to your /data/local/tmp folder:
Code:
adb push C:/adb/arm64/mtk-su /data/local/tmp/
5. Open an adb shell:
Code:
adb shell
6. Change to your tmp directory:
Code:
cd /data/local/tmp
7. Add executable permissions to the binary:
Code:
chmod 755 mtk-su
8. Run the exploit:
Code:
./mtk-su
NOTE – The following line should display:
New UID/GID: 0/e
9. Ensure that mtk-su succeeded in setting selinux to permissive by typing the following command:
Code:
getenforce
INSTALLING TWRP & SLOANE
1. Download rbox's TWRP custom recovery and the latest pre-rooted ROM from your PC and copy it to the root of a USB stick [or microSD card].
2. Connect the USB stick [or microSD] to your AFTV2.
3. Change to USB Storage directory:
Code:
cd /storage/usbotg/
NOTE – If recovery is on microSD
Code:
cd /storage/sdcard1
4. Run the zip file. This will automatically run SU:
Code:
sh /storage/usbotg/firetv2_recovery_v7.zip
If recovery is on microSD
Code:
sh /storage/sdcard1/firetv2_recovery_v7.zip
NOTE – It should print out a following lines:
Extracting unzip...
Remounting /system read-write...
Extracting...
Remounting /system read-only...
5. Reboot to Recovery:
Ctrl+C (closes out previously ran script)
Code:
adb reboot recovery
6. Your AFTV2 should reboot to a black screen displaying the Amazon logo, followed by a prompt stating that the device will automatically restart, but if not to unplug then re-plug the power source. It will not automatically restart, but DO NOT unplug the device yet.
{
"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"
}
7. If you copied the recovery and ROM onto a USB stick then you will need to disconnect it from the AFTV2, and connect a USB hub with at least 2 ports to the AFTV2, and connect both a USB keyboard and the USB stick to the hub at this time. If you copied the recovery and ROM onto a microSD then connect a keyboard to the empty USB port at this time.
8. Now unplug then re-plug the power source and you will be presented with the TWRP splash screen.
9. At the boot menu, press the RIGHT arrow key on the USB keyboard to boot into TWRP recovery.
NOTE – whatever you do DON'T let your AFTV2 idle for too long on the initial recovery boot menu screen or it will time out thus restarting, requiring you to repeat the prior steps.
10. Use the arrow keys to select the "Install" in TWRP.
11. "Select Storage", and choose the location where you stored the pre-rooted ROM.
12. Select "Swipe to Confirm Flash" to start the installation.
13. Select "Reboot System" once the file has finished installing in order to restart the AFTV2.
For those feeling a little adventurous/ambitious then feel free to follow this guide created by @g422 as he discuses where to go from here by delving into other avenues to truly tap into the power of your AFTV2 such as what's "Xposed" and the benefits it offers for rooting your device, and also how to backup your current Fire OS install using TWRP.
Also shouts out to @PhoenixMark who created a guide for Mac users based on my write-up as how to enable root here.
This will work if we have a bricked device stuck on the Amazon logo?
Thanks for this! can't wait till I get home and finish the process with your guide. Other guides had my head spinning. Achieved temp root but no mention of pushing super su.
Oh wow, looks like that exploit spread like wildfire!!
Wonder if anybody will see if this works for the firestickv2 (I don't trust myself to crack the case of mine open lol)
b0ricuaguerrero said:
Thanks for this! can't wait till I get home and finish the process with your guide. Other guides had my head spinning. Achieved temp root but no mention of pushing super su.
Click to expand...
Click to collapse
Worked like a charm on my fire tv 2, but I did notice voice control seems to be broken after achieving permanent root.
Anyone else experienced this????
Thank you for putting this guide together! Also thanks to @rbox for twrp and the rom!Finally got root on my Fire TV 2!
Sent from my SM-G9650 using Tapatalk
worked flawlessly on Amazon fire tv 2, the only thing i would say about the instruction for me was that usbotg was not recognised I only had sdcard0 (int storage) sdcard1 (sd card) apart from that great job thank you
ps there was an update waiting to install from amazon which i blocked, perhaps they are patching already
JUSTINMARMER said:
This will work if we have a bricked device stuck on the Amazon logo?
Click to expand...
Click to collapse
Idk. I think we're pretty much in the same boat now: https://forum.xda-developers.com/showpost.php?p=79063299&postcount=197
Delete... duplicate comment
b0ricuaguerrero said:
Thanks for this! can't wait till I get home and finish the process with your guide. Other guides had my head spinning. Achieved temp root but no mention of pushing super su.
Click to expand...
Click to collapse
Not a problem. Just giving back where I can
b0ricuaguerrero said:
Worked like a charm on my fire tv 2, but I did notice voice control seems to be broken after achieving permanent root.
Anyone else experienced this????
Click to expand...
Click to collapse
I don't use voice activation, voice assistants, etc. as a preference. I'm just paranoid like that
huffmybrd said:
Oh wow, looks like that exploit spread like wildfire!!
Wonder if anybody will see if this works for the firestickv2 (I don't trust myself to crack the case of mine open lol)
Click to expand...
Click to collapse
It's worth looking into. Since I currently own one as well I'll see a/b performing these same instructions and post my findings at some point in time.
salsoul said:
worked flawlessly on Amazon fire tv 2, the only thing i would say about the instruction for me was that usbotg was not recognised I only had sdcard0 (int storage) sdcard1 (sd card) apart from that great job thank you
ps there was an update waiting to install from amazon which i blocked, perhaps they are patching already
Click to expand...
Click to collapse
I tried both ways, with the microSD and USB so I know it works if you followed what was stated in the instructions to the T... I know that when I attempted the USB option the first time, I had forgot to plug the USB stick in which made it show up as USB (0) which is only logical explanation I can think of for what happened to you.
Krog18 said:
Thank you for putting this guide together! Also thanks to @rbox for twrp and the rom!Finally got root on my Fire TV 2!View attachment 4718781
Sent from my SM-G9650 using Tapatalk
Click to expand...
Click to collapse
Not a problem, glad I could help
This is fantastic work!!!
Do you know if root can be 'hidden' to Netflix app won't block it's use?
n8wwd said:
This is fantastic work!!!
Do you know if root can be 'hidden' to Netflix app won't block it's use?
Click to expand...
Click to collapse
Thanks, and unfortunately, no. SuperSU is the component that enables root which can be detected by apps that disengage user functionality when they discover root is enabled. I attempted to install Magisk v18.1 to counteract this side effect, but failed miserably w/ the end result to the point that my AFTV2 does a constant boot loop as recounted here. Magisk would be the only option I'm aware of to make root 'hidden', but it's not worth it at the cost of turning your device into a boot looping paper weight.
True. Nothing like having a 'brick on a rope' so to speak. That's not a 'deal breaker' as I subscribe to IPTV services that out performs it anyway. Do you know if Hulu does the same as Netflix? The missus may take exception if it killed that...
---------- Post added at 12:22 AM ---------- Previous post was at 12:20 AM ----------
I guess the main reason I'd want root access is to take all of the preloaded apps off for room, as well as have the ability to use the external storage within apps.
---------- Post added at 12:48 AM ---------- Previous post was at 12:22 AM ----------
well...I answered my own question..seems Hulu doesn't like it either...*sigh* Time to search for a box that can hide root so my wife won't blow a gasket....
Wait, we can't use Netflix if we are rooted? Yikes.
I've had no trouble with Netflix yet since I rooted this yesterday, but of course ymmv.
Sent from my SM-G9650 using Tapatalk
---------- Post added at 08:36 AM ---------- Previous post was at 07:44 AM ----------
urbanman2004 said:
Thanks, and unfortunately, no. SuperSU is the component that enables root which can be detected by apps that disengage user functionality when they discover root is enabled. I attempted to install Magisk v18.1 to counteract this side effect, but failed miserably w/ the end result to the point that my AFTV2 does a constant boot loop as recounted here. Magisk would be the only option I'm aware of to make root 'hidden', but it's not worth it at the cost of turning your device into a boot looping paper weight.
Click to expand...
Click to collapse
Damn, sorry to hear that. I imagine what happened is the result of magisk patching the kernel on a locked bootloader. I hope you're able to get it fixed. Good luck to you!
Sent from my SM-G9650 using Tapatalk
Krog18 said:
Damn, sorry to hear that. I imagine what happened is the result of magisk patching the kernel on a locked bootloader. I hope you're able to get it fixed. Good luck to you!
Sent from my SM-G9650 using Tapatalk
Click to expand...
Click to collapse
Thanks. You never know, somebody smart enough might actually come up with a tool capable of relieving my device from its eternal boot loop hell