(I have removed the guide as requested by AFTVNEWS but please use the link below to see more information via there web page)
The link for the original post at AFTV if you wanna go there & leave them credit or ask questions feel free -
http://www.aftvnews.com/how-to-block-updates-on-a-rooted-fire-tv-or-fire-tv-stick-by-setting-a-custom-fire-os-version-number/
This is great news & another step to stay protected & keep root for our FireTv.
deanr1977 said:
I take no credit for this work I just noticed this new work over at AFTVNews & am passing on the info for everyone over here at XDA FireTv forums. The dev behind this is rbox & AFTVNews was posting & making the guides for everyone to use.
Here's all the information -
This is a new method of blocking software updates on a rooted Fire TV or Fire TV Stick. It involves setting a custom software version number in the device’s build.prop configuration file. Rbox came up with this idea and asked me to test if it works. The main advantage to this update blocking method is that it can be implemented from within TWRP custom recovery before the device boots. That means, if you factory reset (i.e., wipe data partition) a Fire TV, you can ensure the device does not update during the initial setup process. Prior to this method, you had to rely on external router or OpenDNS update blocking methods when going through the Fire TV initial setup process after factory reseting. Now you can block updates internally before starting the initial setup process. If you have a rooted device and are blocking updates using the “pm disable …” method (method 1 in my blocking guide), it’s a good idea to also follow this guide to have an additional update blocking method in place.
Important
This update blocking method MUST BE REDONE EVERY TIME YOU INSTALL A ROM. That is why it’s best to use both this method and the “pm disable …” method (method 1) from my blocking guide. This blocking method does survive a factory reset, which method 1 does not. So this method will cover you when factory resetting your device, and method 1 will cover you if you flash a new ROM but forget to re-apply this method, since method 1 survives installing a new ROM.
You can implement this update blocking procedure from within TWRP or within Fire OS. Obviously, if you are following this method to block updates during the initial setup process, you need to implement this update block from within TWRP. If your device is already setup and you are following this guide to just have an additional blocking method in place, then it’s actually simpler to implement this method from within Fire OS.
NOTE: I will be updating this guide with screenshots for each step within the next few days. So if it’s difficult to understand, you should wait for the screenshots to be added.
Guide using TWRP
Boot into TWRP Custom Recovery. Be sure you are following this guide AFTER you’re done installing a ROM. Installing a ROM will remove this blocking method, so it should be done last, just before you boot into Fire OS.
Select Mount from the TWRP main menu.
Check the box next to System and then return to the main menu by pressing the home shaped button in the bottom center.
You now need to transfer the file /system/build.prop from your Fire TV to your PC. You can do this using ADB or by copying it to a microSD card or USB drive connected to your device.
To transfer the file using ADB:
Connect to your device via ADB. You will need to be connected over ethernet and the IP of your device is displayed in the upper left of the main TWRP menu.
Transfer the file to your PC by running the command:
adb pull /system/build.prop [PATH-ON-YOUR-PC]
Be sure to replace [PATH-ON-YOUR-PC] with the directory on your PC where you want the file to be saved.
Mac example:
adb pull /system/build.prop /Users/AFTVnews/Downloads/
Windows example:
adb pull /system/build.prop C:\Users\AFTVnews\Desktop\
To transfer the file using a microSD card or USB drive:
Insert the microSD card or USB drive into your Fire TV.
Select Mount from the TWRP main menu.
If it is not already checked, check the box next to Micro SDCard or USB (depending on which one you’re using). Then return to the main TWRP menu by clicking the home shaped button in the bottom center.
Click Advanced from the TWRP main menu.
Click File Manager from the menu.
Click the system directory.
Click the build.prop file.
Click Copy File from the menu.
Click the external_sd if you’re using a micro SD card, or select usb if you’re using a USB drive.
Click the Select Current Directory button in the lower right.
Click the Swipe to Confirm button to copy the file to your external storage device.
Press the home shaped button to return to the main TWRP menu. Go back into the Mount menu and uncheck your external storage device. You can now remove your microSD card or USB drive and connect it to your PC.
Now that you have the build.prop file on your PC, open it with a plain text editor.
Find the line (near the top) that starts with ro.build.version.number=
Replace the numbers on that line with 987654321 and save the file.
Now you need to transfer the file back to your Fire TV.
To transfer the file back using ADB:
Run the command:
adb push [PATH-TO-build.prop-ON-YOUR-PC] /system/build.prop
Be sure to replace [PATH-TO-build.prop-ON-YOUR-PC] with the location on your PC where the build.prop file is stored.
Mac example:
adb push /Users/AFTVnews/Downloads/build.prop /system/build.prop
Windows example:
adb push C:\Users\AFTVnews\Desktop\build.prop /system/build.prop
To transfer the file using a microSD card or USB drive:
Insert the microSD card or USB drive into your Fire TV.
Select Mount from the TWRP main menu.
If it is not already checked, check the box next to Micro SDCard or USB (depending on which one you’re using). Then return to the main TWRP menu by clicking the home shaped button in the bottom center.
Click Advanced from the TWRP main menu.
Click File Manager from the menu.
Click the external_sd if you’re using a micro SD card, or select usb if you’re using a USB drive. (You may need to select “Up A Level” first.)
Click the build.prop file.
Click Copy File from the menu.
Click the system directory. (You may need to select “Up A Level” first.)
Click the Select Current Directory button in the lower right.
Click the Swipe to Confirm button to copy the file to your /system directory.
Press the home shaped button to return to the main TWRP menu.
That’s it. To confirm the custom version number is saved correctly, do one of the following:
If you’re connected via ADB, run the following command:
adb shell cat /system/build.prop | grep number
Or, within TWRP, go to Advanced, then to Terminal, and type the following command:
cat /system/build.prop | grep number
You should see ro.build.version.number=987654321 printed out. If you get the original version number printed out, then you did something wrong and need to repeat this guide from the beginning.
Guide using ES File Explorer within Fire OS
It will be a lot easier to follow this guide if you have a keyboard and mouse connect to your device. First, install the app ES File Explorer onto your Fire TV or Fire TV Stick from the Amazon Fire TV appstore.
Open ES File Explorer.
Scroll down the menu on the left and turn on the “Root Explorer” option under the “Tools” sub-menu.
Grant su permission if you’re asked.
Press back or escape to dismiss the popup menu.
Scroll up the menu on the left and select “Local”.
Select “Device” from the options that appear.
Scroll down and select the “system” folder.
Scroll down and select the “build.prop” file.
Select to open it with “ES Note Editor”
Select the pencil icon in the top right to edit the file.
Find the line that starts with ro.build.version.number and replace the number on that line with 987654321. It’s best to use the error keys on your remote or keyboard, instead of clicking with a mouse, to edit the number.
Click the back arrow icon in the upper left. Not the one in the upper right.
Click “Yes” when asked if you want to save.
Click the back arrow icon in the upper left again.
To verify your changes were saved, open the build.prop file again and ensure the number next to ro.build.version.number is still 987654321
Here is the original post on AFTV if you wanna go there & leave them credit on there post -
http://www.aftvnews.com/how-to-block-updates-on-a-rooted-fire-tv-or-fire-tv-stick-by-setting-a-custom-fire-os-version-number/
@rbox & @AFTVnews.com if you would like me to remove this let me know or if you would like to post on the below comments & I will link the thanks to the comment post number so you get the proper credit for your work.
This is great news & another step to stay protected & keep root for our FireTv.
Click to expand...
Click to collapse
Not trolling you extremely long guide but wouldnt it be a whole lot easier doing this from within Fire OS to open the build.prop from within root explorer and use the built in text editor? Just a thought, might save some people a few hours work.
---------- Post added at 01:11 PM ---------- Previous post was at 01:05 PM ----------
Or you could even use build.prop editor apk, if you wanted to keep things very simple.
Sure rbox or AFTVNews will comment here soon but if you want a quicker reply follow the link above over to aftvnews.com & leave the comment there if you like? Like I said I'm just passing on the info this is not my guide, I'm not bothered about thanks & take no credit for this guide
Sent from my SM-G900F using Tapatalk
Stupid request, but can you add "July" to the title? The date as written hasn't occurred yet in the US [emoji6]
ldeveraux said:
Stupid request, but can you add "July" to the title? The date as written hasn't occurred yet in the US [emoji6]
Click to expand...
Click to collapse
Done mate
sconnyuk said:
Not trolling you extremely long guide but wouldnt it be a whole lot easier doing this from within Fire OS to open the build.prop from within root explorer and use the built in text editor? Just a thought, might save some people a few hours work.
---------- Post added at 01:11 PM ---------- Previous post was at 01:05 PM ----------
Or you could even use build.prop editor apk, if you wanted to keep things very simple.
Click to expand...
Click to collapse
My guide has two parts: Doing it within TWRP and doing it within Fire OS. deanr1977 just copy and pasted my entire guide, which lost the formatting, which makes it difficult to actually tell the guide has multiple parts. That's why I asked him to remove the copy and pasted part of his post.
AFTVnews.com said:
My guide has two parts: Doing it within TWRP and doing it within Fire OS. deanr1977 just copy and pasted my entire guide, which lost the formatting, which makes it difficult to actually tell the guide has multiple parts. That's why I asked him to remove the copy and pasted part of his post.
Click to expand...
Click to collapse
I understand it has 2 parts, i just wondered why the need to drag over to a pc the build.prop to edit then push it back over, when the same thing could be done with build.prop editor apk or from within root explorers built in text editor, which would be a whole lot quicker ?
First thanx to AFTV for working @ this device and discovering another method to block updates.........
Second @ sconniyuk it was already mention that the guide has 2 parts 1 if you like to work on a PC and a keyboard (which I prefer) and another to work directly on the device ...your choice..... not mine
htchd2fix said:
First thanx to AFTV for working @ this device and discovering another method to block updates.........
Second @ sconniyuk it was already mention that the guide has 2 parts 1 if you like to work on a PC and a keyboard (which I prefer) and another to work directly on the device ...your choice..... not mine
Click to expand...
Click to collapse
Ah, now I get it.... You cleared it all up for me @htchd2fix ?
I know I should of realised there are people who love climbing a mountain instead of flying over it......
I myself and probably speak for 99.9 % of people (apart from you of course) would like to do a tedious thing like blocking updates the simplest, quickest and shortest way possible.
I was in no way discrediting anyone or the guide. When @AFTVnews.com replied and said it was in 2 parts here I said I already new this, I dont know why you felt the need to tell me its in 2 parts also?
sconnyuk said:
Ah, now I get it.... You cleared it all up for me @htchd2fix ?
I know I should of realised there are people who love climbing a mountain instead of flying over it......
I myself and probably speak for 99.9 % of people (apart from you of course) would like to do a tedious thing like blocking updates the simplest, quickest and shortest way possible.
I was in no way discrediting anyone or the guide. When @AFTVnews.com replied and said it was in 2 parts here I said I already new this, I dont know why you felt the need to tell me its in 2 parts also?
Click to expand...
Click to collapse
Can you let it go already? Leave the thread alone. If you don't want to use his method, go elsewhere. Don't lump other users into your crazy hangups.
ldeveraux said:
Can you let it go already? Leave the thread alone. If you don't want to use his method, go elsewhere. Don't lump other users into your crazy hangups.
Click to expand...
Click to collapse
Theres no need to bite @ideveraux I will actually use the guide but will do it an easier method. Im not lumpimg any users with crazy hang ups and im not letting anyone try to get one over on me when all I originally did was ask why not complete the editing of the build.prop with 1 of 2 very simple methods and im getting the crap for it.
No thanks
sconnyuk said:
Ah, now I get it.... You cleared it all up for me @htchd2fix ?
I know I should of realised there are people who love climbing a mountain instead of flying over it......
I myself and probably speak for 99.9 % of people (apart from you of course) would like to do a tedious thing like blocking updates the simplest, quickest and shortest way possible.
I was in no way discrediting anyone or the guide. When @AFTVnews.com replied and said it was in 2 parts here I said I already new this, I dont know why you felt the need to tell me its in 2 parts also?
Click to expand...
Click to collapse
....ok i do not have time for this....this is my last one.......
......quickist and shortest????????????????...are you sure????????? how much sure you are?
''''I garanti you that the time you download the app to edit build.prop.....I have already edited and pushed over my 4 devices ...while you still walking around your house....
htchd2fix said:
....ok i do not have time for this....this is my last one.......
......quickist and shortest????????????????...are you sure????????? how much sure you are?
''''I garanti you that the time you download the app to edit build.prop.....I have already edited and pushed over my 4 devices ...while you still walking around your house....
Click to expand...
Click to collapse
Very childish but very very amusing.
By the time anyone gets through that essay the next fire device is out dated.
Have you got anymore jokes? That one was excellent ?
Related
Notice:
Click to expand...
Click to collapse
Sorry guys this no longer works...
Ubuntu removed alot of the files needed to run it on a phone off of their website which is why you are getting the errors on the script to try and install it.
Recapped:
Here's what I mean the website the script is going to to get the files no longer exists...
Heres an example to see for yourself: http://ports.ubuntu.com/ubuntu-ports/pool/universe/t/tightvnc/tightvncserver_1.3.9-4_armel.deb
I will try and find a new link to plug in but for now it DOES NOT WORK!
Thank you for your patience on the thread,
StrumerJohn
==== How to Install Ubuntu Linux on your HTC EVO 3D / Sensation 4G ====
Table of Contents
Post 1
1: Disclaimer
2: Pre Requirements
3: PC Guide to push to phone
4: MAC Guide to push to phone
5: Additional Scripts
6: Credits
Post 2
1: FAQs
2: Recognitions
Post 3
1: News and Updates
2: Additional Notices
Click to expand...
Click to collapse
-Disclaimer-
This has been tested on my phone and runs perfectly fine, I am not responsible for you breaking, bricking, or dropping your phone on the floor and causing the USB cable to fall out and blow up your device.
Pre Requirements:
A rooted HTC EVO 3D or Sensation 4G
A S-off'd HTC EVO 3D or Sensation 4G
netarchy's kernel (Silverneedle Test5)
Android SDK
The USB drivers for your phone. (x32) (x64)
A microSD Card
2.3 GB Free of space on your microSD card
Know how to read to directions
Click to expand...
Click to collapse
The intense Procedure:
1. Download this version of Ubuntu. [Download #1] [Download #2]
2. Unzip the Ubuntu folder to your desktop and if you want, delete the compressed one you downloaded.
3. On your phone go to Settings > Applications > Development and turn on USB debugging.
4. Plug in your USB cable (from your computer to your phone) and mount your (mirco)SD card.
5. Move or copy over the unzipped / normal Ubuntu folder. This will take a long time unless you have a class10 microSD card.
6. After moving / copying that file over, tell your phone to unmount the (micro)SD card / Set the phone to Charge Only mode.
7. Now on your computer, go to where you have Android SDK installed. (Example on my computer: E:\Program Files (X86)\Android\android-sdk )
8. When in the main SDK folder, hold shift and right click a blank area and then click on "open command window here". It should of opened the command line window with the directory of your SDK already put in. If not type cd "C:\Your directory or location of your SDK"
9. Now type "cd platform-tools"
9.5. (Optional) "type adb devices" and check if the computer recognizes your phone. If not you need to reinstall your drivers from the download link above in the requirements.
10. Type "adb shell"
11. Type "su" so we have superuser permissions
12. Type "cd /sdcard" so the directory is changed to the (micro)SD card
13. Type "cd ubuntu" so the directory is changed to the Ubuntu File
14. Type "sh ubuntu.sh" so we can install Ubuntu
15. Type "bootubuntu" to start up Ubuntu. Next time you enter Ubuntu, you just need to type "bootubuntu" from your /sdcard/ubuntu directory, there is no need to run ubuntu.sh again.
16. If you got "[email protected]" in the command line, you have sucessfully installed Ubuntu. If not make sure you installed netarchy's kernel. If it still does not install correctly please try a different ROM, I have only tested this on SteelROM 1.1. *AFTER INSTALLING ANY ROM, YOU NEED TO REINTALL THE KERNEL.*
17. Now type "apt-get update" to update Ubuntu to the latest version. Then "apt-get upgrade" to apply the update.
18. Type "apt-get install tightvncserver" to install the vncserver. (Your telling your phone to read off it self pretty much.)
19. Type "export USER=root" To make yourself a user / the user
20. Type "vncserver -geometry 1024×800" to set the screen resolution you want to display on your phone. Remember you can always zoom in by pinching, so you don't need to make this that much smaller. You should also get prompted to set a password, do so. You will need to remember this password to log in.
21. Download the AndroidVNC Viewer off the Market here.
22. Open the viewer, and put in a nickname, your PASSWORD FROM ABOVE, and for the IP Address put: 127.0.0.1 for the port put 5901. THEN SCROLL DOWN and make the COLOR FORMAT 24-bit colors (4bpp).
And finally, hit Connect to launch Ubuntu on your phone!
For Mac users:
Finder -> Applications -> Utilities (folder) -> Terminal
When you cd to where your adb is located, cd is lowercase as are most all unix commands.
If you're unsure where to go, get to adb in your Finder, right-click, get info, the pop-up will show you the path. Note in unix that the folders (subdirectories) are separated by / and not by \ like in Windows.
Once you're there, the only trick you need to know is to tell unix that adb is located where you are, so you change the adb shell command like this:
./adb shell
That's about it, all other instructions once you're inside the phone shell are the same.
OBTW - after the unzip of the initial file from the OP, just drag and drop the whole ubuntu folder to your NO NAME drive (normal sd card formatting doesn't get a name at the factory, so by now you know that your sd card mounts like that anyways I'd suppose - just put it here in case).
Click to expand...
Click to collapse
Additional Scripts
Danaff37's
danaff37 said:
That's the script catted out.
I posted a different script a few pages back that I think will help you guys. I modified it so we should have no trouble with apps in sd.. I finally got a bigger sdcard so I can test this stuff and this script works great. Please guys try this script. If you download it in phone it will change the name and add a bin on it I think, so rename it accordingly and make sure it gets into /system/bin with the right permissions (755 or rwxr-xr-x), then run it
http://db.tt/gin57Gd
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Credits:
Ubuntu Modded and Guide by: Me
Mac Guide Written by: EarlyMon
danaff37's Script by : danaff37 (of course)
Original dev of Ubuntu: Zedomax
If you have any problems beside the slow downloads because of the blown up servers, let me know below. Also I tried to type this fast, so if there is any typo's or broken links let me know too! Thanks!
Also feel free to hit the Thanks button or Donate for more Guides
FAQS
FAQS
Do I need to have everything in the android-sdk downloaded and installed?
No, you just need to have the base sdk.
When I tell the command prompt to adb devices, my phone does not show up!!
Make sure you have installed the proper drivers for your phone and for your correct operating system
I'm not getting "[email protected]" when I type / copy-&-paste "bootubuntu"
Well, this could be for a various amount of reasons, first make sure you have a rooted HTC EVO 3D/Sensation. And by root, I mean a full root, not just a temp root or S-off. If you still do not get "[email protected]", flash your device (or go though your data folder and delete all the ubuntu files, then delete the ubuntu file off of your sd card and clear your caches.), and retry the above steps. If the problem still persists, then please PM me with your exact problem.
I'm having issues within the VNC, and I get an error message when I hit "connect".
Make sure you typed your password correctly, the passwords are case sensitive. If you still cannot get in, make sure your IP Adress is set to "127.0.0.1" and your Port(s) are "5901".
The colors on my screen look all weird and disorientated, how do I fix this?
Close Ubuntu, and re-open the VNC application, then scroll down to "Color Format" and tap on "24-bit color (4 bpp)".
The on-screen keyboard does not work and I get a different letter or character for whatever character I type!
The on-screen keyboard will work now, if you install LXDE.
I'm not good with reading text! I need a video demonstration!
For a video head here: http://www.youtube.com/watch?v=YbunTRzEQCI
How do I close Ubuntu?
Two options here:
1.Logout of the server and go to your homescreen and push menu, then go to settings, then Applications, then Running Services and close any remaining open part of the server program. The service may re-open later, do not close it though. It won't use up a noticable amount of RAM, just enough to make sure the application opens quick again.
2. Logout of the server and use your favorite task killer to close the server process. The service may re-open later, do not close it though. It won't use up a noticable amount of RAM, just enough to make sure the application opens quick again.
FAQS should be in order chronologically (until the end of them).
I would like to give a huge thanks to EarlyMon, for helping out lost members. This thread would not be as peaceful if it were not for him.
And it seems I have forgotten to list another VERY helpful person here, danaff37. I am really grateful to both of these two for all of the help and work they have done to aid others.
Am I missing a question that you are pretty sure is asked ALOT (lol)? Then PM me please and I'll get it up here ASAP!
Upcoming Change log for final release:
(StrumerJohn's Zedomax Ubuntu Mod)
Made a launchable .exe for easier updating and installing of Ubuntu
Default mode LXDE for fixed keyboard
Pushes Server application to your phone
Fixed a few problems that caused people to have an error in installing
Server application updated
Fixed port issues for log in errors
News update 11/13/11
Bad news and Good News:
Ubuntu was successfully updated
Update brakes keyboard
Update breaks Apps2SD
Update takes up less space (1GB instead of 2GB)
Update ONLY works on MIUI so far
Updated script to add work around for those facing issues
Computer .exe only working on x64 Windows 7 computers ;-;
Thank you for those of you testing! Might make this open Beta...!
Version as of 12/12/11
Alpha Build 1.0
What Doesn't Work so far:
Boots to latest version only to lock up phone (Unless you are running MIUI)
Keyboard borked
Doesn't work on ICS
Audio Broken
Apps Saved on SD
What works:
Everything else
Sweeeeet.
Appreciate my help? Thank me
Wow this is amazing! Never used linux before tho...
Haven't looked at the bootubuntu script yet, but I know a lot of these couldn't work if you had any apps on sdcard at all. Each app moved to sd takes a loop device.
Sent from my PG86100 using XDA App
maazing will try tonight!!!!!!
danaff37 said:
Haven't looked at the bootubuntu script yet, but I know a lot of these couldn't work if you had any apps on sdcard at all. Each app moved to sd takes a loop device.
Click to expand...
Click to collapse
Just moved partially like moving to the SD or Actually having them Downloaded and Installed to the SD?
Interesting. Nice write up
Sent from my PG86100 using XDA Premium App
Cool...
But, why.
Cause you can?
Sent from my 3vo via Tapatalk
Because Ubuntu has some computer applications you can't normally use on your phone. In the browser download Java and check out runescape runs like shizzle but once we get new quad phones out I'm sure it would run fine. lol
This is what I wanted. Million thanks....
Sent from my PG86100 using www.psvitahacks.co app
Added to my 'Complete LIST' thread: http://forum.xda-developers.com/showthread.php?p=16132451
StrumerJohn said:
Just moved partially like moving to the SD or Actually having them Downloaded and Installed to the SD?
Click to expand...
Click to collapse
Using the stock apps to sd like under manage applications (like the same as is available on a non rooted phone). The script for ch rooting can be made to work around it though. But most aren't.
Sent from my PG86100 using XDA App
danaff37 said:
Using the stock apps to sd like under manage applications (like the same as is available on a non rooted phone). The script for ch rooting can be made to work around it though. But most aren't.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
If there are any small minor problems like that and it's not working proper, let me know. I'll mess around with some things and release a patch.
Installed successfully and works great except I can't type cause of the keyboard glitch. Anyway around it?
Sent from my PG86100 using XDA Premium App
Working with shooter rewind
akiradavis said:
Installed successfully and works great except I can't type cause of the keyboard glitch. Anyway around it?
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
The only way to get around it atm (at the moment) is to use a bluetooth keyboard.
Very sweet! I will test this tomorrow when I get home. It should work on my ROM as well
Nice....can't wait for the keyboard fix.
***Solved*** I ended up using Albert's 4.5 along with his videos, worked great!!
Thanks again for all the help.
Believe it or not I have searched and read much in attempting to answer these questions without starting another thread. Probably because I am such an android noob I am not able to find answers I understand.
Primary questions:
Using windows SD card flash method from this thread:
http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14
I am able to flash the SD card with the image fine.
Not sure what the note under instruction step 2 means
Instruction 2 "NOTE: Do not extract the .zip with superuser and su."
step 6 says to put "the zip" in the root of the sd card. What zip are we talking about? There was only a single download zip with all the files including the image so I assume it means this complete download zip even though it makes references later to "update.zip" (I do not have a file named "update.zip".
When I reboot after inserting the sd card I get the screens as described but the verbiage is not exactly as listed in the instructions.
Options I receive:
"install zip from sd card"
"choose zip from sdcard"
"apply /sdcard/update.zip"
selecting /sdcard/cwm_sd_flash_and_exe.zip
receive
"finding update package"
"opening update package"
"installing update...
"installation aborted"
Secondary questions:
o Do all of the many rooting options get you to the same end result?
ie same version of android, market access, updates blocked, additional apps, loader options, etc
o Are we close enough to a true dual boot sd option (leaving base device untouched) as referenced in the cm7 release thread that I should just wait for that?
Thanks much for any help for a noob, and I beg forgiveness if I am treading ground that has been explained many times before.
As i see that you can boot into CWM i would suggest to get a more finished ROM for yourself, i have posted one of them. They are in development section you might want to take a look, there are 2 roms for 1.4.0 and one for 1.4.1.
All the root methods are not the same, and it all relies on what you want, for example keep B&N content or debloat B&N content, also there are some methods that don't include all google apps. So take a look at what they offer and pick what best suits you.
As for dualboot sdcard it is possible as everything in life but its not close. First let devs release a beta of CM7 and wait for CM9, eventually we will get there just be patience.
~ Veronica
Noob Root Questions me too!
I haven' t tried this yet but had the same basic questions about the instructions (i.e. which zip is being referred to). I believe you are told not to click on the su, super user zip cause you should install that AFTER you have established the basic root (i.e., get CWM and install Nook/Zergy). I could be wrong, maybe one if the kind people that know more can clarify this. In the meantime I think I am going to use the video AlbertWeitz made on youtube with accompanying links to scripts for root. Check youtube or development threads, he offers videos on rooting NT with an SD card to include or not include access to the Barnes and Noble software for your library. I think having the video will help. This is not really a different root method but based on the work of Indirect (whose post you are following) and many others...Albert did add some apps I think. Indirect also released a Superuser Tool recently (in dev thread) which has root in it but no specific instructions when you select the root process...just what you find in the post you are looking at (no offense to Indirect....you are a god!) Albert's mission has been to help us noobs along with the root already developed by making videos. I think he intends to make one for Indirect's Supertool but why wait? Once you've rooted you will b able to instsll beta ROM theoretically coming this Tuesday internally. External ROM as suggested in previous posts, is sometime off in the future.
I hope this info helps. I've pmed Albert to make sure that OP is up to date as far as the links go, I checked the whole thread and don't see any subsequent changes. Hopefully he will have time to respond and I will repost reply here (if I can figure out how to do that)! Still unsure of how to attach links to posts...how do you do that?
L
---------- Post added at 12:21 AM ---------- Previous post was at 12:09 AM ----------
Checked your suggested ROM and looks great...just too chicken to try it without a video to follow! Noob jitters....
From the thread you jsut quoted, it took me a day to figure it out the first time I rooted
I've been keeping up on that forum as much as I can since I got my Nook Tablet two weeks ago. In order to get my install to work, I ended up having to read that entire thread, bouncing between instructional posts, downloading repetative files, and getting confused over some personal issues. So I think I'll toss in my personal version of how to install things using Windose, an SD card, and the file links scattered throughout that thread:
In summary, read the folllowing posts:
Original Thread (Post #1)
Post #14
Post #141
Wach this Youtube as well:
http://www.youtube.com/watch?v=I403bagL9rw
Assuming you have a brand new microSD card, plop it into the cormer or your nook. Don't worry about formatting it, you'll be re-formating it again. Connect your Nook to your PC with the USB, and your PC will recognize two new drives:
MyNOOK, and whatever your new microSD card happens to be factory named.
Stage 1: Mounting the boot image
1. From Post #14, download the linked file "CWM_SD_flash_and_exe.zip"
2. Extract the zip and run "Win32DiskImager.exe"
3. Select the "cwm_sd_flashing_boot.img" and ensure that the Device drive is the correct one (like I: and not your C
**Reading through other threads, there are links (now dead) to other image files, and an appended "update.zip" file. Do not worry about these, as the packaged image is all you need.
4. Your miscroSD card will now be named "boot" and only have a size of about 70MB.
**Your nook will think your SD card is bad at this point. A Warning popup will say, "SD card format required - This memory card is unrecognized and needs to be formatted.
5. Ignore the message to format, and reboot your Nook. Either hold down the power key and power back on, or hold the power+N key.
6. The moment your nook powers back on, hold down the N key until you get a white screen with a cardboard box. This will bring up the boot menu
**You do not need your USB plugged in, despite other posts instructing you as such. As long as you hold down the N key within 3 seconds of it rebooting, you get a box on a white bachground that leads to the boot loader.
7. usign the volume buttons to scroll, select the "update.zip". Use "N" to select and tap the power button to back out of a menu.
After you've finished, you'll boot up with the option of going to "Home" or "ADW.Launcher"
That should be it!
---------- Post added at 04:24 AM ---------- Previous post was at 04:17 AM ----------
P.S. I have a brand new Nook Tablet with 1.4.1 preinstalled.
I've rerooted my NT a few times already in the last week, and I now think the best version is actually Albert's 4.5 found here:
http://forum.xda-developers.com/showthread.php?t=1439630
... at least until CM7 is ready.
**Solved** Thanks much!!
Thanks everyone for the help, I certainly appreciate it!!
I am about to try the process again. Just to confirm:
ZirbMonkey -
1st, I am assuming the recommended method you describe in your post is a more recent recommendation than the one in your sig (Albert's 4.5).
CWM_SD_flash_and_exe.zip is the same file name I have been using. I realize it may be a different version and will check it as I go through the process you detailed so well, but the version I used before didn't have an "update.zip" in it. Am I expecting that there will be an update.zip on the SD card after taking the steps you've detailed, is there already a file with that name on the NT, or something else? Also, am I browsing to an "update.zip" file on the sd card or taking the menu option that has "update.zip" in the name?
Maybe this will all become evident as I go thru the process but I'd like to understand as much as I can before I start so I don't screw up.
Again, thank you for your patience dealing with my lack of knowledge in this area.
If using Albertwertz 4.5 root Update Hidden settings to block OTA updates
I finished root too using Albertwertz's 4.5, very easy with video. If you used this be sure to update your hidden settings app from the market then block OTA updates. This app in the currently uploaded zip is earlier version and does not block OTAs. Check your software version in About Your Nook in settings after your root is complete. If it does not indicate that OTAs are blocked you need to do this by updating hidden settings app already installed with root by downloading the app update from the Android Market......then going in app to choose OTA updates block, otherwise a future update could kill your root! It does not roll it back to V 9.9.9, but stays V1.41 (with note below version number stating OTAs are blocked) when you are done.
There is a separate post by Albert (in dev thread...look for key word OTA updates) indicating he updated the hidden settings app (after uploading Root 4.5 zip). You also need to go into DEVELOPMENT option in updated Hidden Settings app and click on both USB debugging boxes. Don't forget to enable Unknown Sources too!
Geez really need to learn how to embed links in his site!
Thanks to Albert, Indirect and everyone else involved in root and bootloader crack!
L
prsa01 said:
**Solved** Thanks much!!
Thanks everyone for the help, I certainly appreciate it!!
I am about to try the process again. Just to confirm:
ZirbMonkey -
1st, I am assuming the recommended method you describe in your post is a more recent recommendation than the one in your sig (Albert's 4.5).
CWM_SD_flash_and_exe.zip is the same file name I have been using. I realize it may be a different version and will check it as I go through the process you detailed so well, but the version I used before didn't have an "update.zip" in it. Am I expecting that there will be an update.zip on the SD card after taking the steps you've detailed, is there already a file with that name on the NT, or something else? Also, am I browsing to an "update.zip" file on the sd card or taking the menu option that has "update.zip" in the name?
Maybe this will all become evident as I go thru the process but I'd like to understand as much as I can before I start so I don't screw up.
Again, thank you for your patience dealing with my lack of knowledge in this area.
Click to expand...
Click to collapse
The "update.zip" is for the original method, where there was a file with that name in the base directory of the flashed card. I believe this is/was the second option on the rooting menu.
But the new (4.5) method uses a different zip file, so you have to "update from a .zip" (first menu option?) and select the zip that shows up at the bottom of the next menu. Sorry, but I'm working from memory as I reset my memory card after I flash it to get full use of it back again.
It's still not working for me - Like prsa01, I found no such "update.zip" file, so I tried "CWM_SD_flash_and_exe.zip" (the only "zip" file on the SDcard).
It starts to install, then aborts:
Code:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
what am I doing wrong?
---------- Post added at 06:14 PM ---------- Previous post was at 05:51 PM ----------
I couldn't get this method to work (is it because I didn't enable debugging first? Enabling debuggin is not mentioned in the instructions. CWM loads, but I get an "Installing update... Installation aborted." message - see prev post)
This method says you have to enable USB debugging first, but the instructions for doing so don't work for me. You're supposed to download and install an apk, then click "settings" when you see the "install blocked" message - trouble is, my installs are NOT blocked - not since the first time I sideloaded an app. Is there another way to get to the hidden settings menu? or do I need to do a factory reset and start over?
KyleK...
Perhaps you have this taken care of this issue by now. I just rooted my Nook and used the Hidden Settings apk I think you are referring too. I see that others on the forum have reference the Play Store as the source for the apk.
here is the link: https://play.google.com/store/apps/details?id=com.brianf21.nthiddensettings&hl=en
Once installed you can use your file manager to locate the app. Going into settings/development where you find the selectable states for USB debugging (on) and Auto Mount (off).
There are notes in the forum about keeping track of these settings to make sure they stay set. I noticed before I rooted the setting would change on every re-start.
In my case I use ES explorer to look at my files. I launch it from the search tab, the Hidden Settings app icon is sitting on my home directory. Every time I use this application it says it will re-install and retain all previous data. You may find that a bit odd.
Hi all,
EDIT
Thanks to techdudester on the second page, getting rid of the malware is now even easier!
Just flash the image he found here with the following procedure and you're good to go!
Instruction:
1. Flash the new ROM.
a. Get the ROM here . (Use this ROM only if you have a Venstar V140D tablet!)
b. Follow the linked tutorial to install the flash software and flash the new ROM on your device with: Phoenix Suit.
Voila, ready!
Enjoy your malware free tablet!
Tips and tricks. (or something...)
Get adb working (needed for all the other tricks down below):
1. Download the Google development tools (sdk) here and install them on your computer. I assume you have windows 7 installed during the rest of this tutorial.
2. Connect your device to your computer and make sure it is installed correctly.
a. Connect your device while its powered on via USB to your pc.
b. Go to Start, right click "My Computer" and select "Properties". Click "Device Manager".
c. Right click the Android device with the exclamation mark and select "Update Driver Software...".
d. Select "Browse my computer for driver software".
e. Select "Let me pick from a list of device drivers on my computer".
f. Keep "Show All Devices" selected and click Next.
g. Click "Have Disk..." and click "Browse..."
h. You can find the drivers in the "SDKInstallLocation"\sdk\extras\google\usb_driver directory and click OK. Replace SDKInstallLocation with the location that you selected during installation of the SDK.
i. Select the "Android ADB Interface" driver from the list and click Next.
j. Confirm installation by clicking on "Yes". Sometimes you also have to click on "Install" if a screen pops up to ask you again if you really want to install the driver...
k. Click "Close".
To use it:
Open a command prompt (in search type "cmd" followed by ENTER) and go to the following directory ""SDKInstallLocation"\sdk\platform-tools".
If you want a backup of your tablets system directory (highly recommended!) use:
"adb pull /system C:\system"
where C:\system is the target location on your local computer where you want the backup of the system directory.
Remove the update package (this doesn't work for updating the tablet, so, useless.)
adb remount
adb shell
cd system/app
rm Update.apk
exit
Remove the unwanted apps (dragonfire.apk etc)
adb remount
adb shell
cd system/preinstall
rm *
exit
If you would like to have your tablet in the correct time zone after factory reset, you will have to adjust the build.prop file.
First you need to get it to your pc so you can edit it:
in the command prompt window and at the same location as in the tutorial above type "adb pull /system/build.prop C:\temp\build.prop".
Just in case, make a copy of the build.prop in Windows Explorer so you always have the original file if something goes wrong.
Now you can edit the build.prop, but DON'T EDIT IT WITH THE WINDOWS NOTEPAD! Use Notepad++ or similar to edit the build.prop.
After you made the changes (and be careful here, you could end up with a tablet that does not want to boot up, solution further down below) you have to upload the file back to your tablet.
in the command prompt type:
adb remount
adb push C:\temp\build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
Don't forget the last line! If you do not chmod the file (set the correct permissions) your tablet will not boot up.
Changes in the build.prop:
Time zone:
Default time zone is "persist.sys.timezone=Europe/London"
you can change this to your locale time zone like "persist.sys.timezone=Europe/Amsterdam" (for the netherlands )
Search the internet for valid time zones.
Change the default language:
The default language is determined by these two values in the build.prop:
persist.sys.language=en
persist.sys.country=US
For dutch change them to:
persist.sys.language=nl
persist.sys.country=NL
and again, search the internet for valid language values.
Higher brightness after factory reset:
Add the following line to the build.prop file (at the top of the file)
ro.ph.def_brightness=225
You pushed the build.prop without changing the permissions:
No problem. Just connect your booting tablet to the PC, install the driver if its not installed correctly like explained in the tutorial, and then change the rights via adb. It's no problem that it's not fully booted!
in a command prompt in the adb directory:
adb remount
adb shell chmod 644 /system/build.prop
adb reboot
If you pushed a wrong non functioning build.prop, just use this method to push the original build.prop (you know, the copy you made ) back to the device (followed by setting the correct permissions of course).
Remove the (in my opinion) irritating boot sound:
adb remount
adb shell
cd system/media
rm boot.wav
exit
rom download
can you provide another way to download the rom file ,i cant seem to get the registration process to work
stevethesignguy865 said:
can you provide another way to download the rom file ,i cant seem to get the registration process to work
Click to expand...
Click to collapse
I have dropped it here. Hope this helps
I bought the same tablet for my daughter. She's (and so am I) suffering from a lot of annoying popups and ads.
Thanks for sharing your instructions here, very hard to find them!
Since I'm a complete newbie: one important question. When you flash the ROM, all of the apps (games) will be removed I guess?
Second question: can you put the stock rom on a different location? Both of the links (including Filedropper) don't contain any files...
Thanks!
1ce/ said:
I bought the same tablet for my daughter. She's (and so am I) suffering from a lot of annoying popups and ads.
Thanks for sharing your instructions here, very hard to find them!
Since I'm a complete newbie: one important question. When you flash the ROM, all of the apps (games) will be removed I guess?
Second question: can you put the stock rom on a different location? Both of the links (including Filedropper) don't contain any files...
Thanks!
Click to expand...
Click to collapse
Yes, all applications will be removed. As soon as you configure the tablet again with the same gmail account, it will probably start installing the applications and games automatically, but in game progress will be lost for most (not online) games.
I am re-uploading the file. Will update this post with the link as soon as it finishes
edit: upload finished, get it while its there LINK
BlueFlame said:
edit: upload finished, get it while its there LINK
Click to expand...
Click to collapse
Great! Thanks for the swift response. The file is about 307 MB. Is this correct? I'll start working on it, probably this weekend. I'll keep you posted.
1ce/ said:
Great! Thanks for the swift response. The file is about 307 MB. Is this correct? I'll start working on it, probably this weekend. I'll keep you posted.
Click to expand...
Click to collapse
Yes, thats correct. Once unpacked it will be around 520 MB.
Good luck!
Hi BlueFlame,
Thanks for the post. Is it possible to get the image uploaded again? Would be much appreciated.
Maylar said:
Hi BlueFlame,
Thanks for the post. Is it possible to get the image uploaded again? Would be much appreciated.
Click to expand...
Click to collapse
On request. You can find it here. (Adjusted link. Stored on Google Drive)
Thanking you. Very much appreciated.
Thank's for a fantastic procedure... Worked very well.
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
1ce/ said:
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
Click to expand...
Click to collapse
Is that the firmware that I provided?
If not, try to download it again.
If so, I think that your tablet has a newer firmware than this one. You could contact the seller of your tablet for the current (latest) firmware for this tablet.
If you get a newer firmware, please share
Image file invalid
Hi Blueflame,
I've tried to re-flash, but at some point i'm getting the message at livesuit V1.11 that the image file is invalid.
It's the 3rd time i have downloaded the file, what could be cause of this error?
Greetz Mike
mcwheelz said:
Hi Blueflame,
I've tried to re-flash, but at some point i'm getting the message at livesuit V1.11 that the image file is invalid.
It's the 3rd time i have downloaded the file, what could be cause of this error?
Greetz Mike
Click to expand...
Click to collapse
Not sure. Will upload it again this weekend just to be sure that it's not my uploaded image. (I will let you know once I've done that)
You can, on the other hand, contact the supplier (where you bought the tablet) and ask them for the latest version of the ROM. I would also be interested in that
BlueFlame said:
Not sure. Will upload it again this weekend just to be sure that it's not my uploaded image. (I will let you know once I've done that)
You can, on the other hand, contact the supplier (where you bought the tablet) and ask them for the latest version of the ROM. I would also be interested in that
Click to expand...
Click to collapse
Uploaded again! same link (just made it a new version in Google Drive).
Open Firmware failed - possible solution
1ce/ said:
First step doesn't work for me: Phoenixsuit gives an error: 'Open Firmware failed'
with three possible reasons:
- firmware version is too old
- firmware format is broken
- firmware is used by other application.
Version used: 1.0.6
Firmware file: a33_599x_v11_1024x600_gc0308_2035_1015a.img
Any ideas?
Click to expand...
Click to collapse
Try to put the image file in a directory without special characters (i.e. c:\temp). Worked for me.
wundabua
Te real FIX is In!
Ok, i have one of these allwinner, Venstar, "whatever", A33 D140v tablets. It had all the usual problems and more, because the first thing I tried, was to use the built in recovery to "restore to factory". This made things even worse, because after the recovery, I couldn't reach the Google authentication servers.
I am pro tech with 25 years in the trenches and I have to admit this thing really threw me for a loop, because I spent an entire day researching the solution, installing Android SDK, drivers, Phoenix Suit, Live Suit, etc. These were all very complicated "solutions" that took me exactly nowhere. I finally found the answer in a rather stupid Youtube video.
The REAL answer is actually very quick and easy compared to all these other recommended methods.
In the first place, model V140d image is only used for these infected tablets. The actual model is V11 and once you use the quick restore method I discovered, you will have a malware free V11 model. The whole secret to this method, is the fact that these units were designed to be quickly, automatically and completely restored in less that 5 minutes through the use of their built in micro SD slot.
Imagine that!
If you check your tablet that came new in the box as something other than V140d, the method I used will most probably not work for you.
Anyway, the quick method I discovered, can be seen on my own tech support site. To find it, Google: Just Call Techdude
Then click on the support link at the top of the page on my site and all will be revealed.
techdudester said:
Ok, i have one of these allwinner, Venstar, "whatever", A33 D140v tablets. It had all the usual problems and more, because the first thing I tried, was to use the built in recovery to "restore to factory". This made things even worse, because after the recovery, I couldn't reach the Google authentication servers.
I am pro tech with 25 years in the trenches and I have to admit this thing really threw me for a loop, because I spent an entire day researching the solution, installing Android SDK, drivers, Phoenix Suit, Live Suit, etc. These were all very complicated "solutions" that took me exactly nowhere. I finally found the answer in a rather stupid Youtube video.
Click to expand...
Click to collapse
Hi techdudester,
The combination "pro tech with 25 years in the trenches" and "very complicated "solutions"" sounds a bit strange.
But either way, a THANK YOU is in order!
The ROM you found works on my tablet (flashed yesterday) and so far so good. No popups and no unwanted application downloads!
I will adjust my initial post to incorporate this image.
The multi user and guest account feature is not available on either of the two recent releases of Lollipop for the Z3v. I did some research and it appears this is the case, not only on other Verizon handsets like the Droid Turbo and the Galaxy S5 / S6, but a few other non-VZW devices as well. I'm not sure why it was removed but apparently it's just hidden. It can be enabled and I followed the instructions for doing this for the various other devices and can report that it works for our Z3v (see attached screenshots).
I've kind of cleaned up the instructions and put them below. Usual disclaimer - I'm not responsible for anything that may happen to you or your cat if you choose to do the following. You DO need root access to edit and write to the system file.
** To be safe, please make a backup of your phone and/or a copy of the build.prop file that you are going to edit.
Get ES File Explorer. Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)
With ES File Explorer, go to device/system/ and find the file: build.prop
Choose to edit it with ES Note Editor.
Scroll to the end of the file and type in the following:
fw.max_users=5
fw.show_multiuserui=1
Save the file.
I'm not sure if the next step is required but it was in half the instructions I saw, and I did it myself: Click and hold the file, go to Properties, and then change the permissions to Read, Write & Execute. [all three]
Reboot your phone.
When you're up and running, access multi user mode by pulling down your notification shade and then clicking on your user icon at the top right corner.
Notes so far:
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Therefore, an app such as Movie Creator can and will create a "highlight" movie that is composed from photos that are saved on the external SD Card. Just keep this in mind as far as privacy.
There is a per user option that lets you decide whether or not the additional users can use the phone and access the text messages. If you disable this ability, while they cannot open the phone app to make a call, the CAN receive an incoming call.
You can find out more about the nuances of additional users with your Google Fu.
Enjoy!
Wow! Great work!
AddictedToGlass said:
Wow! Great work!
Click to expand...
Click to collapse
Thanks! I really wanted this feature and it seemed like not many people care too much about it. It's my way of circumventing the awful permissions control we currently have in Android. That is, there are apps I want to use but refuse to install because of their overreaching permission requirements (contacts, etc) and so I can now create a second user with a new "dummy" Gmail account that has no sensitive information and install these apps without worrying.
By the way, something neat I figured out about this. Additional user accounts are not allowed to side load apps (the toggle to install from unknown sources is grayed out). I figured out that if the main user / owner restores an app through Titanium Backup, any other currently existing user will have it installed for some reason. I don't know why this happens but it's a neat glitch that gets you around that restriction.
Well I think most people simply don't let others touch their phones and so don't have a use for multiple user accounts. I find that my phone, as big as the screen is, is becoming more and more of a computer / tablet replacement. I like the idea of a multiuser functionality, but mostly to hide my own stuff. I'll silk never let anyone else touch my phone!
The use for multi-user that I've seen that makes the most sense is people with children. They will create a user profile for the child so they can't get into any of the parent's stuff or settings. That or the guest profile which will let them do whatever the heck they want without screwing up the phone.
Aside from that I have read that devs find the feature very useful for testing. Heck, that's not a bad idea to install and test apps, in general.
uh oh.
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
rpelljr said:
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
Click to expand...
Click to collapse
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Tigerhoods said:
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Click to expand...
Click to collapse
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
rpelljr said:
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
Click to expand...
Click to collapse
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
it is guys if done right your system needs to be switched to r/w then go back to r/o after modifying the build prop if you modify in r/o you will get bootloop to a hard brick it depends.
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
Well I kinda fixed it. I went and bought a HTC M9. Lol but not yet, I'm still working on it. I have found scripts to run, even a specific build.prop fix to push, but I have windows 10 and couldn't get adb to find the device. Plus I'm a little rusty. So I broke out my old windows 7 laptop I have used just for rooting an modding phones and tablets. I did get adb and fastboot to find it once. Then some reason lost it. I didn't have it ready to go. But I'm almost 100 percent sure I can get it. Just need to play around with it a little bit more. Having trouble with drivers etc. I will let you know when I have it.
And didn't really hurt my feelings getting the phone I truly want. I never had problems with HTC since I was flashing roms on my old window phones. I just want my pictures I cannot replace.
"Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)"
Alas- I am not rooted, and therefore can not enable "Root Explorer" option. Unless someone has some other suggestions- I think I can't do this unless I'm rooted.
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
AddictedToGlass said:
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
Click to expand...
Click to collapse
a backup usually means going into your twrp and hit the back up button and make a copy of your system including data and all that. This is mandatory before messing with the build prop. If you want Pm me your build prop and I will send it back to you. With multi user enabled.
Yup, I know what a back-up is and how to do it, and I know it's a must before messing with the build.prop. I just really thought I had done it recently...
-and I had! But I forgot that a few days ago I bought myself a Christmas present; a 200 Gb micro SD, and copied most of the contents to the new card from my old one. I chose not to copy the backup because I had planned to make some changes and create a more recent backup. Never happened though because I got side tracked loading music and such. Lol!
So I'm all back together, but would still like to play with this feature. So I'm going to give it another shot.
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Click to expand...
Click to collapse
Perhaps the wrong thread but: enabled multi user on a Cube T8 only to find that guest and other user can access INTERNAL sd but not external sd. I'd rather have it the other way round. So the kids (other users) can use the whole of 32 GB sd card rather than me having to share the small internal sd with them.
Any ideas how to fix this? Phablet is not rooted btw.
got bootloop..... but i'm safe as i've backup.... through recovery..
I've inserted two lines and fell in bootloop
Thanks bro.. working....!!!! but second step is not needed...
None of this is my work and all recognition goes to the awesome developers that made this possible, I will link their guides in here with some minor notes for newbies like me that may had some issues trying to unlock and root the Fire Stick (FS) 4K
DISCLAIMER: BE WARNED THAT YOU HAVE TO OPEN YOUR FIRE STICK AND IT WILL VOID YOUR WARRANTY, THIS IS NOT FOR THE FAINT OF HEART AND NEITHER THE DEVELOPERS OR MYSELF ARE RESPONSIBLE IF YOU BRICK YOUR DEVICE OR VOID YOUR WARRANTY
Ok, now let's begin:
UPDATE: Per Sus_i, this makes perfect sense:
"Since the exploit can't be patched, it's in my opinion the best to do the setup at the beginning, pair the remote, then update to the latest over fireOS. That way you avoid a pending update nag setup screen after doing the exploit. Then enable ADB and unknown sources. After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen)."
First very important, I wish I would have known this before but make sure you have a Laptop and a Monitor to Connect the FS to, so basically the USB Power cable from the FS connect it to your laptop and connect the HDMI portion to a monitor or TV
I also strongly recommend to have your FS deregistered before continuing as this will prevent your FS from automatically updating after rooting
In order to unlock the bootloader follow "THIS GUIDE"
I made a quick video on how to open your device and how to Short it using Aluminum Foil:
https://www.youtube.com/watch?v=h4I6ifBLWJ4
Process is pretty self explanitory, make a USB ISO from the image provided on that thread, boot into it and open terminal, make sure you put the file he provides on a RW location, my mistake was that I put it inside a RO folder and it would not load the script, so I mounted the kamakiri-mantis-v1.2.zip unto the /mnt directory of the usb and I was able to run the script successfully, make sure to run the commands quickly as the first time that I it finished the ./bootrom-step.sh script and I left it sitting for 10 minutes to grab a bite, I couldn't run the second script and had to start all over. After the second ./fastboot-step.sh script, your device will be on the TWRP recovery, now on the same terminal page or a new one enter these commands:
Code:
adb devices
adb shell
exit
You should see your device's serial number from the first command with "device" to the right of it and the second command will basically put you inside the device's directory assuming you have established a successful connection. The last command just put you back to your starting point, now open the firefox browser on the FireOS USB and navigate to the URL below
Download the Pre-Rooted Image from "HERE" This image contains Magisk already so you don't have to worry about installing it separately, the image is larger than the available partition on this USB so this is a good time to either get a second USB or if you want to download the file to your local hdd and pull them from there its up to you, then run these commands:
Code:
adb push <your download location you decided earlier here>/mantis-6.2.6.8-rooted_r1.zip / sdcard/
adb reboot recovery
adb shell
twrp install /sdcard/mantis-6.2.6.8-rooted_r1.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
This basically installs the pre-rooted image to your device, after the last command, you should see on your monitor the Fire Stick Reboot and boot to the Amazon GUI Splash Screen, now very important if you followed my previous instructions of deregistering your device before performing all these steps, it should bring you up to the Amazon Initial Setup Screen, now what you want to do is do the following commands before continuing on terminal:
Code:
adb devices *you should see something your screen where the FS is connected to, click accept or enter can't remember*
Now it should show you in terminal your serial number and "device" next to it, meaning you can run adb commands in which you will run the following to disable OTA updates:
Code:
adb shell
su *after this command you should see something again on your screen, click the check the box "Always Remember" and click ok" *
if "su" was successful, you should see something like this:
mantis:/ $ su
mantis:/ # *the hash means you're running as root, if you don't have a "#" you are not running as root"
Than continue with these commands and should get the following results:
pm disable com.amazon.tv.forcedotaupdater.v2
***Package com.amazon.tv.forcedotaupdater.v2 new state: disabled***
pm disable com.amazon.device.software.ota
***Package om.amazon.device.software.ota new state: disabled***
pm disable com.amazon.device.software.ota.override
***Package com.amazon.device.software.ota.override new state: disabled***
After running all these commands exit adb and continue with the normal Amazon Setup including adding your amazon account. After you get to the screen where you can see all the apps, open a new web page browser in firefox and download "This Add-On" , this one is less than 200MB so it should fit on the Fire OS USB, so I would download it and copy it to /mnt for ease of access, go back to terminal and type this:
Code:
adb devices
adb push <your download location you decided earlier here>/AFTV-MM-1.7-6.2.6.8.zip/ sdcard/
adb reboot recovery *it will boot into TWRP*
adb shell
twrp install /sdcard/AFTV-MM-1.7-6.2.6.8.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
Your device will reboot and if everything went smoothly, you should have a rooted amazon fire stick 4k, Congrats :good:
Nice guide
Here are a few thoughts from me...
It's important to use the latest kamakiri. The mentioned prerooted 6.2.6.5 is probably a downgrade. A few sticks needs an update of the TZ in order to play prime video. The TZ update is only in the v1.2 Kamakiri or in the 6.2.6.6 prerooted.
Edit: S̵i̵n̵c̵e̵ ̵t̵h̵e̵ ̵e̵x̵p̵l̵o̵i̵t̵ ̵c̵a̵n̵'̵t̵ ̵b̵e̵ ̵p̵a̵t̵c̵h̵e̵d̵,̵ ̵i̵t̵'̵s̵ ̵i̵n̵ ̵m̵y̵ ̵o̵p̵i̵n̵i̵o̵n̵ ̵t̵h̵e̵ ̵b̵e̵s̵t̵ ̵t̵o̵ ̵d̵o̵ ̵t̵h̵e̵ ̵s̵e̵t̵u̵p̵ ̵a̵t̵ ̵t̵h̵e̵ ̵b̵e̵g̵i̵n̵n̵i̵n̵g̵,̵ ̵p̵a̵i̵r̵ ̵t̵h̵e̵ ̵r̵e̵m̵o̵t̵e̵,̵ ̵t̵h̵e̵n̵ ̵u̵p̵d̵a̵t̵e̵ ̵t̵o̵ ̵t̵h̵e̵ ̵l̵a̵t̵e̵s̵t̵ ̵o̵v̵e̵r̵ ̵f̵i̵r̵e̵O̵S̵.̵ ̵T̵h̵a̵t̵ ̵w̵a̵y̵ ̵y̵o̵u̵ ̵a̵v̵o̵i̵d̵ ̵a̵ ̵p̵e̵n̵d̵i̵n̵g̵ ̵u̵p̵d̵a̵t̵e̵ ̵n̵a̵g̵ ̵s̵e̵t̵u̵p̵ ̵s̵c̵r̵e̵e̵n̵ ̵a̵f̵t̵e̵r̵ ̵d̵o̵i̵n̵g̵ ̵t̵h̵e̵ ̵e̵x̵p̵l̵o̵i̵t̵.̵ ̵T̵h̵e̵n̵ ̵e̵n̵a̵b̵l̵e̵ ̵A̵D̵B̵ ̵a̵n̵d̵ ̵u̵n̵k̵n̵o̵w̵n̵ ̵s̵o̵u̵r̵c̵e̵s̵.̵ ̵ After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen).
Edit: Update: meanwhile, the fix for the mentioned 'contact manufacturer' error is known...
Take a look here and here.
Edit/Update: Due to efuses (blocking the bootrom access), it isn't recommended to do any update infront of the unlock...
Sus_i said:
Nice guide
Here are a few thoughts from me...
It's important to use the latest kamakiri. The mentioned prerooted 6.2.6.5 is probably a downgrade. A few sticks needs an update of the TZ in order to play prime video. The TZ update is only in the v1.2 Kamakiri or in the 6.2.6.6 prerooted.
Since the exploit can't be patched, it's in my opinion the best to do the setup at the beginning, pair the remote, then update to the latest over fireOS. That way you avoid a pending update nag setup screen after doing the exploit. Then enable ADB and unknown sources. After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen).
Click to expand...
Click to collapse
Ops Typo let me edit it, I meant to put 6.2.6.8 on the command lol, and aaaa I see I didn't know the exploit couldn't be patched great info, so than yes I will revise my instructions thank so much
UPDATE: I just checked my FS and I'm on 6.2.6.8v1 and didn't receive contact the manufacturer, is it because I sideloaded the manager app after?
nandroidint said:
UPDATE: I just checked my FS and I'm on 6.2.6.8v1 and didn't receive contact the manufacturer, is it because I sideloaded the manager app after?
Click to expand...
Click to collapse
No. If I remember correct, it has something to do with flashing, i.e. the vendor partition wasn't flashed propperly.
Maybe you flashed not the prerooted!? With the Kamakiri TWRP version is flashing full ota update packages (renamed to zip) also possible... and in the prerooted thread is such a full 6.2.6.8 ota linked.
Edit: Could be that this error is prime video related, idk. rbox said he looks into it soon...
Just for clarification: The prerooted rom is a perfect thing since years.
My suggestion 'avoid any rom flashing' from my last post is just an attempt to keep it simple for beginners.
By the way, if the stick gets all updates in front of the unlock, it makes no sense to update it after the unlock again (unless addon.d support is needed).
I hope that has become clear I very much appreciate all the prerooted stuff
thanx for the tut nandroidint this is exactly what I needed, I wasn't sure how to do the shorting so the video helped out a lot now I'm ready to do this. But I'm sorta a noob when it comes to android so I got few questions tho, 1) what are the main benefits in rooting the fIrestick 4K 2) are there different roms to install? 3) are there root only .apks? 4)also one main thing I would like to be able to do is spoofing the Mac address any idea if that's possible?
5)Oh and lastly what OTB cable do you recommend? sorry for all the questions ?
'std::bad_alloc'
After running the adb push of the manthis.zip Im getting terminate called after throwing an instance of 'std::bad_alloc'.... What Im I doing wrong?
i gave root can i remove amazon services
i dont want google launcher jsut remove services
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable ?
Can I please get some support guys ? previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Hello, after root i got massage on screen
: android system
There is na internal problem with Your device. Contact Your manufacturer for detalis.
And when im trying to register in Amazon it bringing me back to pairing screen, farest i can go it is wifi connection.
Did i brick my Stick?
davinci2798 said:
Hello, after root i got massage on screen
: android system
There is na internal problem with Your device. Contact Your manufacturer for detalis.
And when im trying to register in Amazon it bringing me back to pairing screen, farest i can go it is wifi connection.
Did i brick my Stick?
Click to expand...
Click to collapse
Did you deregister before rooting like the tut says? This is why I’ve been hesitant on rooting because of the lack of support on this forum
Yep, it was new Stick, out from box. Not registered at all. I managed massage, but still comminng to pairing screen.
itsyaboy said:
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable
Can I please get some support guys previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Click to expand...
Click to collapse
You can use adoptable storage on 4K stick with Add-Ons installed and activated AFTV-XM Xposed Module. It brings adoptable storage support to Settings UI.
tsynik said:
You can use adoptable storage on 4K stick with Add-Ons installed and activated AFTV-XM Xposed Module. It brings adoptable storage support to Settings UI.
Click to expand...
Click to collapse
Nice! That’s awesome thanx for the info and reply.
davinci2798 said:
Yep, it was new Stick, out from box. Not registered at all. I managed massage, but still comminng to pairing screen.
Click to expand...
Click to collapse
Hey so have you figured out what was the problem yet? If so could u explain how you managed to fix it? I’m going to root sometime this week and would hate to run into this issue.
USB drive for storage
itsyaboy said:
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable
Can I please get some support guys previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Click to expand...
Click to collapse
Yes, You can use a USB drive for App loading and Movie storage.
See Troypoint.com for good video.
I suggest a single USB OTG Cable and a USB HUB for your drive.
Then you can add a Keyboard and Mouse which make it MUCH easier to type commands.
Good Luck
How might one do this on a Mac?
Thanks
gogorman said:
How might one do this on a Mac?
Thanks
Click to expand...
Click to collapse
Do what? The only thing u can do on the MacOS is to create the bootable iso usb, you can follow these steps to do so https://www.google.com/amp/s/www.le...-on-an-apple-mac-os-x-from-an-iso?hs_amp=true
After your create the bootable usb just reboot and hold down option and select the bootable usb, once in open up Firefox and download the kamakiri-mantis-v1 and open a terminal window and change the directory to where u have the kamakiri folder, in terminal type cd then just drop in the kamakiri and hit enter. From there u can just follow the tut, FYI the bootable usb you create is a Linux OS so that’s how you can do it on a Mac, you just can’t do the rooting on MacOS, just clarifying Incase that was your question.
Sorry I haven't rooted phones in a while and am trying to root my fire stick 4k. Can we get some pictures tutorial pretty please
Sent from my ONEPLUS A5010 using Tapatalk
Step by step instructions would be great?
chinkster said:
Sorry I haven't rooted phones in a while and am trying to root my fire stick 4k. Can we get some pictures tutorial pretty please
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
I would love that too, I have rooted with Unix before but that was on a Drone(Solo).
I understand about creating a bootable USB drive and booting my PC/Mac by changing the bios to boot first off the USB as step 1.
Step 2 is loading software onto the USB while booted under Unix/Linux???
Step 3 How do you then connect to the firestick?
When do you plug the firestick into the tv and when do you short out the jumper??
I know to some of you these sound very basic but it would be helpful for those of us just learning this environment.
Thanks in advance...
RPM99 said:
I would love that too, I have rooted with Unix before but that was on a Drone(Solo).
I understand about creating a bootable USB drive and booting my PC/Mac by changing the bios to boot first off the USB as step 1.
Step 2 is loading software onto the USB while booted under Unix/Linux???
Step 3 How do you then connect to the firestick?
When do you plug the firestick into the tv and when do you short out the jumper??
I know to some of you these sound very basic but it would be helpful for those of us just learning this environment.
Thanks in advance...
Click to expand...
Click to collapse
The link he provided explains all that https://forum.xda-developers.com/fire-tv/orig-development/unlock-fire-tv-stick-4k-mantis-t3978459 all except for when to connect to the tv, but I assume it’s after running the kamakiri script, btw it’s not software, you just download the kamakiri mantis while in the Linux usb os, open a terminal and change the directory of the terminal to the kamakiri folder in order to run the ./bootrom-step.sh and ./fastboot-step.sh commands
Edit: just follow the main guide from the link above then read this guide after, that’s the best way to understand it.