Related
Hi
This topic has been created to address FAQ in regards to Feeyo's Cronos Droid.
This will allow Feeyo to work and post relevant updates on his thread in Development.
Basics:
To ensure the update goes as smoothly as possible, please ensure you carry out the following:
Feeyo has recommended you setup your SD card as follows:
first partition :ext2
Rest FAT32
Some users have advised ext3 has worked, if so great
Installation Instructions
1) Do a backup
2) Make sure you wipe everything. (also battery and rotating settings)
3) Flash Cronos
4) Reboot.
5) When finished booting for the first time make sure to reboot it one last time to update all caching and settings.
Are u updating the rom from an older Cronos Droid version?
1) Flash Cronos
2) Reboot.
3) When finished booting for the first time make sure to reboot it one last time to update all caching and settings.
I update from Cronos Droid Version 1.4 to 1.4.1
In 1.4 rom ，there was about 140M left in my telephone memory
after the update ， there is only 108M left in the telephone memory
then I did this：
adb shell
su
cp -a /data/app /system/sd/
rm -r /data/app
ln -s /system/sd/app /data/app
reboot
there is still 108M left
Then I find the apks exist under data/app also exist under system/sd/app
if i delete the apk under data/app,the same apk will also disappear
WHY
PS after full wipe and I flash the 1.4.1 ,reboot,flash the app2sd.zip ,the phone died,the 1.4.1 means this one :StableCronos_4.1_528_fix_sign.zip
SD：swap 32M ；ext3 512；fat32 some rest
jyhwai said:
I update from Cronos Droid Version 1.4 to 1.4.1
In 1.4 rom ，there was about 140M left in my telephone memory
after the update ， there is only 108M left in the telephone memory
then I did this：
adb shell
su
cp -a /data/app /system/sd/
rm -r /data/app
ln -s /system/sd/app /data/app
reboot
there is still 108M left
Then I find the apks exist under data/app also exist under system/sd/app
if i delete the apk under data/app,the same apk will also disappear
WHY
PS after full wipe and I flash the 1.4.1 ,reboot,flash the app2sd.zip ,the phone died,the 1.4.1 means this one :StableCronos_4.1_528_fix_sign.zip
SD：swap 32M ；ext3 512；fat32 some rest
Click to expand...
Click to collapse
Feeyo has advised not to flash the aps2sd zip (first post) with 1.4.1
Q: Im in love with Feeyo, what do I do
A: get in line behind Rhamsterman
Q: All apps that need SU access on the SU request screen - hanging
A: enable usb debugging
akhtar1817 said:
Feeyo has advised not to flash the aps2sd zip (first post) with 1.4.1
Click to expand...
Click to collapse
yes，I know it ，now I am using the room without flashing the aps2sd zip
but,the problem still exists
jyhwai said:
yes，I know it ，now I am using the room without flashing the aps2sd zip
but,the problem still exists
Click to expand...
Click to collapse
you mean apps2d is not working? I think he is working on it as a few people have posted the issue
akhtar1817 said:
you mean apps2d is not working? I think he is working on it as a few people have posted the issue
Click to expand...
Click to collapse
yeah, that is the point wired
normally ,if the apks you install are all under /system/sd/app,it means the app2sd works
but this time they were under /system/sd/app and also under date /app which
takes up the phone memory
supposed to be QA thread right?
Only questions with answers here please.
Q1: I want the vanilla lockscreen like the one on previous builds of feeyo rom?
Q2: I also need a solution for stopping the alarm on this new lockscreen?
Q3: My phone freezes after the phone starts after applying this update?
A1: Read here. http://geekfor.me/fixes/vanilla-lockscreen/ (works on every 2.1 rom, tested myself manytimes)
A2: Alarm in sense clock is connected to sense lockscreen. If you disable this by installing vanilla lockscreen you won't be able to stop the alarm when it starts. So download also the default clock app (found in link above) and set the alarm in that clock app and disable the alarm in sense clock app.
A3: This lockscreen does not have a pin unlock screen built in. So if you want to use, disable the PIN before flashing the update.
IMPORTANT: If you do this you will lose HTC lockscreen. If you want it back it is only possible by reflashing the rom you use (no wipe needed!). Also (i couldn't find it now), but there is also a solution for having a non transparent lockscreen. It somwhere in the web. Use google.
Q: How do I get MMS working?
A: (Full credit to Goose247 for this)
Copy your data/data/com.android.providers.telephony/databases/telephony.db over to your computer.
Download this http://sourceforge.net/projects/sql...0 beta1/sqlitebrowser_200_b1_win.zip/download
extract it and run "SQLite Database Browser 2.0 b1"
Open up telephony.db
Click on "Browse Data"
Next to table, click on the dropdown menu and select "carriers"
in table 2 (production) you want to change only these settings (apn, user, password, mmsproxy, mmsport, mmsc and just check that type is set to mms) - I didn't have type anything in user and password, guess that depends on your carrier (tmh)
Scroll down the list of carriers to find your settings for the above.
To change any value just double click in the relevant box and input your value and remember to click on "Apply Changes"
Once you have change all your settings save, upload your new modified telephony.db to your phone and then reboot phone.
Click to expand...
Click to collapse
Q: My market seems to load up very slow.
A: When starting the market just press search, and enter a program name. dont wait for it to load up. It will speed it up right away.
Q: Nope it is still being slow...
A: Is your gmail syncing at the same time when using the market? That will slow down market.
akhtar1817 said:
Installation Instructions
1) Do a backup
2) Make sure you wipe everything. (also battery and rotating settings)
3) Flash Cronos
4) Reboot.
5) When finished booting for the first time make sure to reboot it one last time to update all caching and settings.
Are u updating the rom from an older Cronos Droid version?
1) Flash Cronos
2) Reboot.
3) When finished booting for the first time make sure to reboot it one last time to update all caching and settings.
Click to expand...
Click to collapse
I follow this instruction but final can't boot, stop in HERO screen after flash, I was tried many time.
Normal for this version how long to fist boot???
Feeyo said:
Q: My market seems to load up very slow.
A: When starting the market just press search, and enter a program name. dont wait for it to load up. It will speed it up right away.
Click to expand...
Click to collapse
does not work for me
at market startup
i press the search button, enter a name...
after 1 minute i get a result
apps install slow, and after it is installed, it still says 'installing' in the market
Q: My 3G seems unstable / slow Internet
A: The automated APN settings are probably not correct. Remove the automated APN's from your system and enter them manually.
where is this apps2sd.zip file ?
Is it possible to remove / hide the clock in the top right corner? I don't need this, while having a clock widget.
Is it possible on Android at all or specific for this rom?
NoClaim said:
Is it possible to remove / hide the clock in the top right corner? I don't need this, while having a clock widget.
Is it possible on Android at all or specific for this rom?
Click to expand...
Click to collapse
what clock widget are you using instead?
wieben said:
what clock widget are you using instead?
Click to expand...
Click to collapse
Any clock widget will display a clock on the home screen....the clock in the top right corner is useless then, while I don't need to read the time twice...
UPDATED 12/23
---------------------------
1) Added automatic fixing of devicemanager.apk sql databases to prevent OTA root (thanks for the SQL tweak suggestions, Indirect)
2) Added otaban.sh script for those who are already rooted and just want to tweak the sql databases (you will need to put your device back in USB debug mode)
3) Added getroot.sh to just dump the nook back in to rooted/adb mode
INSTRUCTIONS
(Please follow these to the letter; over 500 people have downloaded this script and very few have reported issues)
On the NOOK
Disconnect from USB
Factory restore & initial setup
Browse to this:
http://goo.gl/vTNpJ
Click on notifications center, wait for the file to finish downloading.
Press on downloaded go_launcher_ex_v2.66.apk file
Select Complete action using package installer
It should say "install blocked"
Press settings
Tick unknown sources (press ok)
Pick Development
Tick USB debugging (press ok)
Tick the other USB debugging further down
Untick Automount
Back/Back
Connect the Nook to the MAC. On the nook you should see "USB debugging connected" in notifications center
On the MAC
Download the nooktablet-mac-root-0.6.zip file from http://goo.gl/qyYDB
Open Terminal, and change in to the directory where the zip file was downloaded. Unzip and cd in to the directory created. EG:
Code:
[B]cd ~/Downloads
unzip nooktablet-mac-root-0.6.zip
cd nooktablet-mac-root-0.6[/B]
Start the rooting script:
Code:
[B]./go.sh[/B]
Sometimes adb doesn't wake up immediately. Just try go.sh again if it says it can't find your Nook and you are sure it's in debug mode and plugged in properly. Also don't connect via a USB Hub.
When the script is finished, it should say "Done. Unplug from USB now"
The Nook will reboot.
You are now rooted and the following is auto-installed for you
1) Go Launcher Ex (Rooted App Launch/Desktop)
2) Market Place (The Android "App Store")
3) Button Savior (adds tiny button on right of screen for nagivation home/back etc)
4) Home Catcher (makes 2 clicks of the Nook N bring up the new Launcher)
5) Nook Color App Menu (allows you to install sideloaded apps to the Nook home screen/Library)
6) Dolphin HD Browser (Replacement web browser)
In addition, some tweaks have been made to prevent OTA updates from working, preserving your root state.
trying this now..
thanks a lot! i spent 2 hours last night trying to get the other method working and it gave me the headache of the gods.
edit: that mediafire link is crawling for me (dl is at like .2kb/s) can anyone mirror it for others who may have similar issues?
Worked beautifully! Where can I send a donation to?
beatlesfan01 said:
Worked beautifully! Where can I send a donation to?
Click to expand...
Click to collapse
Tempting and appreciated as that is, there is no neeed. Good luck,
Sent from my BNTV250 using Tapatalk
i can confirm this works guys
yes.. someone please start a thread and aggregate donations for some roms on this bad boy.
t-r-i-c-k said:
Tempting and appreciated as that is, there is no neeed. Good luck,
Sent from my BNTV250 using Tapatalk
Click to expand...
Click to collapse
You are a good man. Thanks again for all of your help and great work. You're an invaluable asset to this community.
Sent from my BNTV250 using Tapatalk
Thanks for the tutorial. It works extremely well!
This worked great, thanks!
I had one minor glitch. I was doing this on an old MBP running Leopard and for whatever reason it wouldn't create the ~/.android directory when I ran the script.
I created the directory manually and re-ran the script and it worked perfectly! Thanks again!
jdubr said:
This worked great, thanks!
I had one minor glitch. I was doing this on an old MBP running Leopard and for whatever reason it wouldn't create the ~/.android directory when I ran the script.
I created the directory manually and re-ran the script and it worked perfectly! Thanks again!
Click to expand...
Click to collapse
Ah, I just looked at the script, I realized now I missed out the mkdir -p ~/.android in it, hence your issue. I will likely fix that and update the script/zip file when I get a minute.
I'm currently considering whether to make the script install busybox at the moment. I don't really need it myself, but I see other people might.
Part of the problem is that if I develop the script any further I ought to test it before releasing it... but I really don't want to keep re-rooting my nook. I want to actually use the damn thing!!
t-r-i-c-k said:
Part of the problem is that if I develop the script any further I ought to test it before releasing it... but I really don't want to keep re-rooting my nook. I want to actually use the damn thing!!
Click to expand...
Click to collapse
I totally get that. I had just gotten done side-loading tons of stuff and getting my launcher screens setup the way I wanted and then I saw your script and thought about it for a day before breaking down and wiping my NT and starting over.
It was worth it! Thanks again!
I'm confused... rooting on PC using other method didn't work for me and now I'm stumped on Mac as well.
This part stumped me:
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Can someone explain the steps in greater detail? I tried runing the adb fiel via terminal, it goes through the script but does nothing on installing files to the device.
Thanks.
Minor problems encountered
I followed the directions and it mostly worked. First, had the problem with the missing:
[ ! -d ~/.android ] && mkdir ~/.android
Then I wasn't sure about the step where it says to click on the golauncher icon in the notifier. I clicked on the LauncherPro.apk entry and choose the package installer. That seemed to work but I'm not sure that's what you meant.
Then found out I should have unplugged the USB cable before rebooting otherwise the launcher chooser is covered by some wrning message. (I can't remember the exact wording now.)
Installed Button Savior. Not sure what that does. I can't figure out where it's suppose to be on the screen.
And worst of all, LauncherPro keeps crashing on me, dumping me back into native Nook mode. That requires a reboot.
But despite all that, I'm happy and will now probably keep my NT.
Big thanks!!
Mike
lanceot said:
I'm confused... rooting on PC using other method didn't work for me and now I'm stumped on Mac as well.
This part stumped me:
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Can someone explain the steps in greater detail?
Click to expand...
Click to collapse
Sent from my BNTV250 using Tapatalk
lanceot said:
I'm confused... rooting on PC using other method didn't work for me and now I'm stumped on Mac as well.
This part stumped me:
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Can someone explain the steps in greater detail? I tried runing the adb fiel via terminal, it goes through the script but does nothing on installing files to the device.
Thanks.
Click to expand...
Click to collapse
Literally type
unzip nooktkablet-mac-root-0.4.zip
cd nooktablet-mac-root-0.4
mkdir -p ~/.android
./go.sh
Sent from my BNTV250 using Tapatalk
kisstek said:
Then I wasn't sure about the step where it says to click on the golauncher icon in the notifier. I clicked on the LauncherPro.apk entry and choose the package installer. That seemed to work but I'm not sure that's what you meant.
Then found out I should have unplugged the USB cable before rebooting otherwise the launcher chooser is covered by some wrning message. (I can't remember the exact wording now.)
Installed Button Savior. Not sure what that does. I can't figure out where it's suppose to be on the screen.
And worst of all, LauncherPro keeps crashing on me, dumping me back into native Nook mode. That requires a reboot.
But despite all that, I'm happy and will now probably keep my NT.
Big thanks!!
Mike
Click to expand...
Click to collapse
Launcher: that's what I meant.
Unplug: if you dont before you reboot it probably wants to media sync
Button savior: installs a tiny button on the right of the screen. Gets you back/home
LAUNCHER: certain things crash for me. Cant change dock shortcuts for example
I'm sure this will all get smoother in time. Pretty good already though.
Sent from my BNTV250 using Tapatalk
Thanks. I found the little tiny button savior icon while trying out an ssh client. It shows up well on a black background.
And that does make it real easy to get back and forth between Android and Nook. Thanks again for making this easy and the button savior recommendation.
I may have to break down and try the Amazon store now.
t-r-i-c-k said:
Connect the Nook to the MAC. On the nook you should see "USB debugging enabled" in notifications center
On the MAC
Download the nooktablet-mac-root-0.4.zip file
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Sometimes adb doesn't wake up immediately. Just try go.sh again if it says it can't find your Nook and you are sure it's in debug mode and plugged in properly.
On the NOOK
Click on Notification center again, and press on the Golancher Icon again. Install the Goauncher
Reboot
After reboot, slide to unlock and it should ask "complete action using..". Pick LauncherPRO
Open Marketplace which should be on the launcher screen
Sign in with your google credentials, attach the device to your account
Install button savior from the Marketplace.
Browse to amazon.com/app-email
Click notifications and watch for Amazon appstore apk download
Click and install.
You should now be live with Android Market & Amazon Market.
Click to expand...
Click to collapse
Hey! Noob here. Thanks so much for this! Just have a few questions...is this a permanent fix? I currently have the amazon appstore, but not android, so is this going to be set up the same way (i.e. have to click search and then go launcher to find the apps)?
When I connect to my mac, the usb debugging prompt will come up right away (like the screen for file xfer normally does)?
After unzipping, are those instructions to enter into the mac's terminal command prompt? Sorry, that's where u lost me! Is "cd" short for something? Thanks again for your help. Just want to make sure I do this right the first time. I think swype is the first thing I will install. Hating this keyboard!!!
First, I want to openly thank t-r-i-c-k for this. Even with little to no knowledge of this kind of stuff, after futzing with terminal for a while I got it to work in two tries. Finally, freedom from another lock-in service/device. But I am having a little glitch that I don't understand.
It's intermittent, but now and then I'm getting a crash on the launcher. It happens when trying to adjust settings/preferences. No big deal as it comes right back, and maybe its the app itself. Anyone else facing this?
t-r-i-c-k said:
LAUNCHER: certain things crash for me. Cant change dock shortcuts for example
I'm sure this will all get smoother in time. Pretty good already though.
Click to expand...
Click to collapse
I installed the ADW Launcher because LauncherPro wouldn't let me change the dock shortcuts. ADW is letting me modify just about everything--dock shortcuts, icons, etc., without issue.
I get an occasional crash but not as many as before.
jdubr said:
I installed the ADW Launcher because LauncherPro wouldn't let me change the dock shortcuts. ADW is letting me modify just about everything--dock shortcuts, icons, etc., without issue.
I get an occasional crash but not as many as before.
Click to expand...
Click to collapse
ADW seemed slow to me. I just switched to Launcher Ex anf thsts is working nicely. No crashes yes.
Sent from my BNTV250 using Tapatalk
Hi,
I cannot post on the development forums so I am posting here.
I have installed the new hidden setting application and have rooted the 1.4.1 firmware for the nook tablet. However nothing I do (reboot / wait) gets the unknown sources hack to work. Every time the button is unchecked as if the fix did not work. I do not get any errors when it runs but the firmware never recognizes that it has happened.
Does anyone happen to have any ideas on how this can be fixed?
Thanks!
silvermist805 said:
Hi,
I cannot post on the development forums so I am posting here.
I have installed the new hidden setting application and have rooted the 1.4.1 firmware for the nook tablet. However nothing I do (reboot / wait) gets the unknown sources hack to work. Every time the button is unchecked as if the fix did not work. I do not get any errors when it runs but the firmware never recognizes that it has happened.
Does anyone happen to have any ideas on how this can be fixed?
Thanks!
Click to expand...
Click to collapse
Did you check to see if it definitely works with 1.4.1?
Same problem here. Unknown sources won't work @ routed 1.4.1
setting unknown sources value
I had the same problem with the "Hidden Settings" app from brian21. I have both root explorer and SQLite installed. So I used root explorer to modify the value of 'install_non_market_apps' of "1" in /data/data/com.android.providers.settings/databases/settings.db. I then rebooted and the "install no-market apps" setting now persists. I could step-by-step this process if what I'm saying is not clear.
Pogodog, please list your step by step. I would love to see if this allows Amazon apps to install. Sideloading them is a real pain...
Step by step Changing "unkown Sources db"
First you have to have root explorer and SQlite installed. I had these already with the rooted 1.4.0 using Android Market.
First I ran the hidden settings app from brian21 and went ro "Application Settings" and set "Unknown Sources". I doubt this step is really necessary, but I was just doing what I could to duplicate the process used in brian21's app.
Then I ran root explorer which starts at root.
Traverse to: /data/data/com.android.providers.settings/databases/settings.db
press data
press data
press press com.android.providers.settings
press databases
press settings.db (Note SQlite will be invoked)
press secure
Find the line with "install_non_market_apps" and press and hold the "value" entry.
Select "Edit Field" and change from "0" to "1" press save.
Back out of root explorer and reboot.
Hope this helps!
Any working solution if we don't have SQlite?
I tried copying settings.db to SD card, making the change with another free db program, and copying the modified file back to nook.
This resulted to a frozen nook when rebooted.
The only thing I can suggest is to get the SQlite apk and install it via adb.
Thanks Pogodog, this fix worked great. I now can use dropbox again to install apps.
Thanks so much pogodog! This solved two issues for me:
1) "Allow unknown sources" now stays checked
2) I can (finally) install from the Amazon Appstore directly rather than the tedious process I'd been using.
I did have to buy SQLite and Root Explorer. I tried a few of the free alternatives and none would give me the needed access.
"NT Hidden Settings" will do this for you in the "Hacks"->"Unknown Sources Hack". Just run that and reboot. The thing it doesn't tell you is that you should install busy box first.
Hi,
When I go to gPlay on the Q and click on "Apps" I only get like 150,000 results available for download, only a small fraction of the total apps available. When I go there on my computer browser to try to download an app to the Q it says "This app is not compatible with this device" for 90% of the apps. So, no dice with either method.
I have been sideloading apps and most of them work just fine. So I want to get around this gPlay restriction on the Q so I can just download apps directly from gPlay rather than having to sideload them.
(I am fully aware that the reason why gPlay keeps track of which devices are compatible is to avoid more "broken" apps than necessary, but in the case of the Q their own system appears to be broken itself, so I want to get around it.)
So, I bought the Device Spoofer app for $1.50USD
https://play.google.com/store/apps/details?id=com.scheffsblend.devicespoof&hl=en
which, despite the reviews worked just fine for me on both the Nexus 7 and on Nexus Q. It changes your build.prop file to spoof Google Play into thinking you are a different device of your choosing. Note that, as it says in the instructions, you need to spoof the device using the app, reboot, go to gPlay, *download an app* (any app), and from then on gPlay will register your device as a different one.
That works for me -- I select for example "Galaxy Nexus", go thru the steps above, and voila, gPlay in my computer's browser has now replace "Nexus Q" with "Galaxy Nexus". Pretty cool.
HOWEVER, and I am now getting to the point, this doesn't allow me to download any more apps than I had access to before! It still says "This app is not compatible with this device ["Galaxy Nexus"]" for the same apps that were incompatible before. Browsing gPlay on the Q also doesn't yield any new opportunities for downloading apps.
I think what is happening is that even though the build.prop file is being changed, the Q is still reporting to gPlay that it doesn't have, for instance: GPS, phone functionality, etc etc, long list of items. And that means that any apps that require any one of those functionalities is "not compatible" (despite the fact that sideloading many of them means they work just fine).
So, my point is, does anyone know how to spoof gPlay so that the Q reports to gPlay that it has all of the bells and whistles? (GPS, phone functionality, etc etc)
Thanks
I downloaded all the .xml files from my Q's /system/etc/permissions folder and compared them to those downloaded from my Nexus 7. There are about half the number of files and indeed many things are not supported, no surprise.
Is it safe to just copy all the .xml files from my Nexus7 to my NexusQ? (plus a few .jar files that are linked to in the .xml files).
And perhaps then gPlay will show more apps?
OK sorry for multiple posts, but what the heck I just tried it. And can't see any more apps on gPlay. Tried downloading one that was visible as I thought it might only report its permissions at download-time, but nothing changed after the download. Drawing blanks here.
FIGURED IT OUT!
That's right folks, you can now download any app directly onto the Q! No sideloading, no adb.
Followed these instructions for a different device. Basically I was on the right track but needed to change the .xml's file permissions back to rw-r-r and then clear gPlay cache, reboot, etc, then it worked.
Pasting the steps from this page http://www.slatedroid.com/topic/34849-guide-to-fix-market-to-get-more-apps-compatible/ below, with the small modification that I got my .xml files from my Nexus 7, not from his/her link, and I only loaded the tablet_core_hardware.xml so far (I have not attempted loading on any of the Nexus 7's other .xmls but most of them don't seem useful). Thanks go out to bosondehiggs of slatedroid.com. I have made a note in square brackets at which point my Nexus Q gPlay started suddenly showing all apps.
A. Backup /system/etc/permissions (just take a copy with ES file explorer or root explorer.recommended just in case)
B. copy the xmlfiles files into /system/etc/permissions (android.hardware.location.gps.xml, android.hardware.location.xml, com.android.location.provider.xml, tablet_core_hardware.xml) agree to over write all of them
C. Make sure the file permission are rw-r-r (with ES file explorer, long tap then change properties on each file..to help you out all files in that directory need to be rw-r-r)
D. Go to settings->apps->all and tap Google Play Store
E. Click on Clear data
F. REBOOT tablet
market still not working
Go to settings->apps->all Go to “Google Play Store” again
‘Clear Cache’ if it lets you then ‘Force Stop’ — DO NOT Clear data
back and Go to “Google Services Framework”
‘Clear data’ then ‘Force Stop’
REBOOT your machine. [After rebooting, the Nexus Q worked with gPlay just fine!]
Then after reboot market is still not working.. then go into..
settings->apps->all google play store again open it but this time clear data if it lets you..
thats it exit open market up, login and you should now have full market access....Youtube...Facebook....
Click to expand...
Click to collapse
hey, this looks cool I want to give it a try.
do you mind posting the instructions from beginning to end?
and the xml file needed too?
sonikot said:
hey, this looks cool I want to give it a try.
do you mind posting the instructions from beginning to end?
and the xml file needed too?
Click to expand...
Click to collapse
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
First you need ES File Explorer app (get es_file_explorer_v1_6_1_7.apk or latest version from the publisher at http://www.estrongs.com/en/download.html).
adb connect to your device if not already. Type "adb devices" to check you are connected.
adb install the ES File Explorer .apk, and run it using the Trebuchet launcher.
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Download this file: http://www.davidnhutch.com/tablet_core_hardware.xml. It's one of the .xml permissions files from the Nexus 7. You may also try other .xml files from other devices at your own risk. Or you can try mine, I guess also at your own risk.
Let's go back to adb. "adb shell"
"su"
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
"exit"
"exit". You should now be out of shell but still in the command window.
"adb push <path-to-that-xml-file>/tablet_core_hardware.xml /sdcard/tablet_core_hardware.xml"
"adb shell"
"su"
"cat /sdcard/tablet_core_hardware.xml > /system/etc/permissions/tablet_core_hardware.xml"
If you want, check it's there: "cd /system/etc/permissions" "ls"
"exit"
"exit"
Next we will change the file permissions for that file we just copied. Open ES File Explorer, click "Up" once to get to the root directory, click System > etc > permissions. Right click or long-press on tablet_core_hardware.xml. Scroll to the bottom of the list that comes up and select Properties. Click the Change button. Select the following boxes, and only the following boxes: User read, User write, Group read, Other read. Click OK, OK. The other files in that directory also need to be rw-r-r, but they should be fine.
Go to Settings > Apps > All > Google Play Store
Click Clear data
Reboot the Q by typing "adb reboot". If you did that using adb-over-wifi, then you'll probably need to do the "adb connect" thing again to reconnect.
Open Google Play. If it's still not working (still shows only a few apps), then continue.
Go to Settings > Apps > All > Google Play Store
Click Clear cache if it lets you, then click Force stop. DO NOT Clear data
Go back once and go to “Google Services Framework”
Click Clear data then Force stop
Reboot the Q again in the same way. After rebooting, my Nexus Q worked with gPlay just fine! However if you still don't see new apps, continue.
Go to Settings > Aapps > All > Google Play Store
Clear Data if it lets you
That's it! Now just Open Google Play, login and you should be able to see and download almost any app either directly on the Q or remotely through a browser on your computer. You may need to download just one app (any app) in order to be able to get the remote download via browser thing working, as Google Play appears to update its knowledge of which devices you have only when you download something.
davidnhutch said:
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
Click to expand...
Click to collapse
I have now put that list here: http://davidnhutch.com/sandbox/blog/how-to-make-google-play-show-you-more-apps/
I will attempt to maintain the instructions at the above link (in case there are errors, or in case the non-GoogleIO Nexus Q's behave differently to the GoogleIO NexusQ (which I have)).
davidnhutch said:
I have now put that list here: http://davidnhutch.com/sandbox/blog/how-to-make-google-play-show-you-more-apps/
I will attempt to maintain the instructions at the above link (in case there are errors, or in case the non-GoogleIO Nexus Q's behave differently to the GoogleIO NexusQ (which I have)).
Click to expand...
Click to collapse
hey step 3 isnt working on the assumption I know how to lauch trebuchet on Q.
How would I launch trebuchet?
sonikot said:
hey step 3 isnt working on the assumption I know how to lauch trebuchet on Q.
How would I launch trebuchet?
Click to expand...
Click to collapse
bump can somebody upload the file for trebuchet and explain how to run this launcher so we can run .apks
thanks
UKROB86 said:
bump can somebody upload the file for trebuchet and explain how to run this launcher so we can run .apks
thanks
Click to expand...
Click to collapse
Sorry, I assume you have already followed the instructions by kornyone here to root and install a launcher:
http://forum.xda-developers.com/showthread.php?p=28484300
There are other ways of doing this too. Some folks have gotten CM9 working on it.
I just made this quick video which shows Trebuchet and the Google Play showing most apps available, near the middle of this video.
What Can You Do with the Nexus Q? : http://youtu.be/6rb4iQDBom0
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Click to expand...
Click to collapse
Can you provide us with the link to your keyboard page so I can mimic these steps on my Q. Also to navigate around on the Nexus Q does it still require a USB mouse to be plugged in to it? I rooted my Q but I'm in the process of trying to add AOSP's Jelly Bean ROM ( http://forum.xda-developers.com/showthread.php?t=1776202 ) and use CM9's Trebuchet Launcher ( http://forum.xda-developers.com/showthread.php?t=1410674 ).
I don't want to get in a position where its all on there and I can't navigate the damn thing. The goal is to use what you provided along with these other resources and work it wirelessly via an app like tablet remote or droid input type app.
mrjaymillz said:
Can you provide us with the link to your keyboard page so I can mimic these steps on my Q. Also to navigate around on the Nexus Q does it still require a USB mouse to be plugged in to it? I rooted my Q but I'm in the process of trying to add AOSP's Jelly Bean ROM ( http://forum.xda-developers.com/showthread.php?t=1776202 ) and use CM9's Trebuchet Launcher ( http://forum.xda-developers.com/showthread.php?t=1410674 ).
I don't want to get in a position where its all on there and I can't navigate the damn thing. The goal is to use what you provided along with these other resources and work it wirelessly via an app like tablet remote or droid input type app.
Click to expand...
Click to collapse
Sorry, I mean the keyboard page on my website: davidnhutch.com/nexusq, click on Keyboard > Special Keys.
Basically, the "menu" button on android is mapped to the same keycode as the "menu" button on Windows keyboards, which usually has an icon that looks like a drop-down menu with a pointer hovering over it. (http://en.wikipedia.org/wiki/Menu_key)
You also can do all this from the command line without ES File Explorer, I'm just trying to make it a bit more visual, plus, ES is useful.
I am very interested in what you described you are working on, as I am hoping to try the same thing when I get some time. Please post your results and steps!
davidnhutch said:
Sure, happy to. I'll include in greater detail than an expert hacker needs, so it's more noob-friendly.
First you need ES File Explorer app (get es_file_explorer_v1_6_1_7.apk or latest version from the publisher at http://www.estrongs.com/en/download.html).
adb connect to your device if not already. Type "adb devices" to check you are connected.
adb install the ES File Explorer .apk, and run it using the Trebuchet launcher.
Press "settings" (see my keyboard page to see how to do that). Scroll down and click Settings and enable "Up to root". Also enable "Root Explorer". OK we're done here for now, we'll use this app later.
Download this file: http://www.davidnhutch.com/tablet_core_hardware.xml. It's one of the .xml permissions files from the Nexus 7. You may also try other .xml files from other devices at your own risk. Or you can try mine, I guess also at your own risk.
Let's go back to adb. "adb shell"
"su"
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
"exit"
"exit". You should now be out of shell but still in the command window.
"adb push <path-to-that-xml-file>/tablet_core_hardware.xml /sdcard/tablet_core_hardware.xml"
"adb shell"
"su"
"cat /sdcard/tablet_core_hardware.xml > /system/etc/permissions/tablet_core_hardware.xml"
If you want, check it's there: "cd /system/etc/permissions" "ls"
"exit"
"exit"
Next we will change the file permissions for that file we just copied. Open ES File Explorer, click "Up" once to get to the root directory, click System > etc > permissions. Right click or long-press on tablet_core_hardware.xml. Scroll to the bottom of the list that comes up and select Properties. Click the Change button. Select the following boxes, and only the following boxes: User read, User write, Group read, Other read. Click OK, OK. The other files in that directory also need to be rw-r-r, but they should be fine.
Go to Settings > Apps > All > Google Play Store
Click Clear data
Reboot the Q by typing "adb reboot". If you did that using adb-over-wifi, then you'll probably need to do the "adb connect" thing again to reconnect.
Open Google Play. If it's still not working (still shows only a few apps), then continue.
Go to Settings > Apps > All > Google Play Store
Click Clear cache if it lets you, then click Force stop. DO NOT Clear data
Go back once and go to “Google Services Framework”
Click Clear data then Force stop
Reboot the Q again in the same way. After rebooting, my Nexus Q worked with gPlay just fine! However if you still don't see new apps, continue.
Go to Settings > Aapps > All > Google Play Store
Clear Data if it lets you
That's it! Now just Open Google Play, login and you should be able to see and download almost any app either directly on the Q or remotely through a browser on your computer. You may need to download just one app (any app) in order to be able to get the remote download via browser thing working, as Google Play appears to update its knowledge of which devices you have only when you download something.
Click to expand...
Click to collapse
Hey David, the .xml file you linked isn't downloadable, can you take a look into this? Also can you provide some clarification on steps 6-15 above, do I enter ADB then type su and everything else as one command? Can you provide a command prompt code showing every entry step by step?
Also as a side not I can't open google play on the launcher or a matter of fact I can't even get a keyboard to show up on the screen to sign in to my google account. Any ideas? I am using a wireless mouse to navigate and tablet remote via my nexus 7 for other inputs.
Like the previous post stated... The xml file isn't available. Can someone post theirs please?
Sent from my Galaxy Nexus using xda app-developers app
[Edit]
I went ahead and downloaded an AOSP Nexus 7 ROM and extracted the file for myself. I don't know what Box's limitations are, but here's a link to the tablet_core_hardware.xml
https://www.box.com/s/e5e0da606448340fd736
xMemphisx said:
Like the previous post stated... The xml file isn't available. Can someone post theirs please?
Sent from my Galaxy Nexus using xda app-developers app
[Edit]
I went ahead and downloaded an AOSP Nexus 7 ROM and extracted the file for myself. I don't know what Box's limitations are, but here's a link to the tablet_core_hardware.xml
https://www.box.com/s/e5e0da606448340fd736
Click to expand...
Click to collapse
Thanks for the .xml file, box link works with no issues. By the way would you happen to have any ideas on how to get a keyboard to appear on screen for the nexus q? Currently I can't type/enter any information I can only navigate with my wireless mouse. Clicking on Gmail/Google Play/ Messages/ or anything else that requires a keyboard just seems to close the program within 5 seconds (almost like a force close just without the error message).
mrjaymillz said:
Thanks for the .xml file, box link works with no issues. By the way would you happen to have any ideas on how to get a keyboard to appear on screen for the nexus q? Currently I can't type/enter any information I can only navigate with my wireless mouse. Clicking on Gmail/Google Play/ Messages/ or anything else that requires a keyboard just seems to close the program within 5 seconds (almost like a force close just without the error message).
Click to expand...
Click to collapse
I didn't get a chance to play with it too much yesterday, I would imagine that if you install a 3rd party keyboard and set it to your primary input method it (might) work. I'm going to have a better chance to really look at the Q tonight here in a few hours, so I'll report back with what I can figure out.
[Edit]
I still have had no time to test this yet. The company I work for is at deadline with new software and we have been working 65+ hour weeks here recently, so my Q has just been sitting there. I'm still anxious to test it, but it might still be a few days before work slows back down and I can really get after it again.
mrjaymillz said:
Hey David, the .xml file you linked isn't downloadable, can you take a look into this? Also can you provide some clarification on steps 6-15 above, do I enter ADB then type su and everything else as one command? Can you provide a command prompt code showing every entry step by step?
Also as a side not I can't open google play on the launcher or a matter of fact I can't even get a keyboard to show up on the screen to sign in to my google account. Any ideas? I am using a wireless mouse to navigate and tablet remote via my nexus 7 for other inputs.
Click to expand...
Click to collapse
Hm, weird that two people have said the .xml file is not downloadable -- I tried today and yesterday and it was available both times. Maybe the hosting site was down or something. Anyway it looks like someone else offered the same .xml file at another link so we're all set. I'll leave the .xml file there for a year or so though.
Steps 6-15: Yes, enter everything as quoted. No extra "adb" or "su" or anything is needed, other than what I wrote there. Just follow one step at a time, typing each one and then hitting enter. Shouldn't need a command prompt code entry as it is already, just without the code tags and with extra double-quotation marks. Please let me know if there are any errors though.
As for your last paragraph, it seems there are two issues. 1) Not being able to open gPlay on the launcher. Can you please provide more info? What happens? Does it try to open then crash? Is the gPlay app missing? 2) Can't get a keyboard to show up on the screen. -- You will never have an on-screen keyboard on the Q. You need an external keyboard, plugged into the USB port. If you want mouse + keyboard simultaneously, you need a "unifying mouse and keyboard wireless receiver" -- just search amazon for that -- what it is is a mouse+keyboard with just one USB dongle that serves both.
Don't think this will get off topic, but if Google updates the software to Jellybean and adds all the the things you can do in the video, will this method still work?
On a side note, dont think google will add all the functionality as you showed on the video.
Edit: Why is Trebuchet needed for this?
Sent from my ADR6425LVW using Tapatalk 2
300k said:
Don't think this will get off topic, but if Google updates the software to Jellybean and adds all the the things you can do in the video, will this method still work?
On a side note, dont think google will add all the functionality as you showed on the video.
Edit: Why is Trebuchet needed for this?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
You're right, you technically don't need Trebuchet. It just makes life easier than launching everything (e.g. gPlay) via "adb shell am start ..." commands from your computer.
Regarding Google updating to JB, perfectly possible. Possible that everything will be standard in the next Q hardware release. However the real questions are, why was this functionality not included in the first place? Why was the hardware so very limited by the software? And the bigger question, why was the public release of the first Nexus Q sales indefinitely postponed? Presumably they are coming out with something better than what they showed at IO. Whether it's much better or just marginally better remains to be seen.
The best app/function in the video is being able to use OnLive (3D streamed games) in my opinion. Now, OnLive is expensive and I did have a few problems with the keyboard mapping, the mouse not working while OnLive was playing, etc, but it works and shows the potential for streamed games. The Q doesn't have to be the core device either, presumably a tablet would work too. I just think they should have done the hardware differently and made an Xbox competitor (Xsphere?) instead of a competitor to precisely no-one.
On steps 8 and 9 I get
sh: cannot create /sdcard/permissionsbackup: Is a directory
I don't think that I am typing it in wrong and I have copied and pasted as well just in case...The directory is made correctly... Thanks for your help.
"mkdir /sdcard/permissionsbackup"
"cat /system/etc/permissions > /sdcard/permissionsbackup"
(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 ?