Database Users

Market problem with Roto JME v3

Dear all.
First off Roto's JME v3 is great. I give it a 9/10. The one missing point is because of the following problem I immediately faced after flashing from my German stock firmware (I don't have this verison # here atm, but can get it later, if needed).
Android Market:
Problem 1:
NHL Gamecenter app not found in Android Market. The app was available to me on the stock firmware but now I can't find it in the market. Not current under paid apps NOR under app search. It simply is not there. It is on my Desire Z and also can be found of my friend's Galaxy S.
Solution:
??
Problem 2:
Not able to download NitroDesk's TouchDown License Key. Program is found but not the key. Was found on my stock fw and also on my Desire Z.
Solution:
Got a license number from NitroDesk. Still unable to find the program in market tho!
I would really appreciate any help as the NHL Gamecenter is THE app I used to use on my gal tab!

Leaked firmware versions aren't know by the android market. To fix this you need to edit the build.prop file. There are several apps who can do that for you.
I myself use Eris Market Fix. Be aware though that the roto packages contains a buggy busybox. If you use that with Eris Market Fix your tab won't start up.
First update your busybox with the BusyBox app on the market place (17.1 is the most stable version) than run Eris Market Fix, reboot your Tab and you're done. All apps will be visible again.

Eris fix is also not showing in market..

Sorry if this is trivial but have you set your csc to XEU. Default is KOR and *could* lead to something like that.
*#272*<IMEI># afair
This will wipe your internal sdcard so do a TB backup first.
I would try that first. No roto-jme has been seen to cause that before...
Cheers,
Hal.
Sent from my GT-P1000 using XDA App

Have you checked your CSC Code?
# cat /sytem/csc/sales_code.dat
Should be DBT for germany.
to change the sales code, you can simply remount the system filesystem read/write ,
echo "DBT" >/system/csc/sales_code.dat
and reboot.

julianLo said:
Have you checked your CSC Code?
# cat /sytem/csc/sales_code.dat
Should be DBT for germany.
to change the sales code, you can simply remount the system filesystem read/write ,
echo "DBT" >/system/csc/sales_code.dat
and reboot.
Click to expand...
Click to collapse
Damit.. and there was I vi'ing the file..

kånda said:
Dear all.
Android Market:
Problem 1:
NHL Gamecenter app not found in Android Market. The app was available to me on the stock firmware but now I can't find it in the market. Not current under paid apps NOR under app search. It simply is not there. It is on my Desire Z and also can be found of my friend's Galaxy S.
Solution:
??
I would really appreciate any help as the NHL Gamecenter is THE app I used to use on my gal tab!
Click to expand...
Click to collapse
Open /system/build.prop in Root Explorer's text editor on the Tab, change XXJME to XXJK5, or whatever your stock version was (XXJK5 should work fine though), in ro.build.fingerprint. This will allow you to see your missing and protected apps in the market.
You can also edit build.prop by pulling it to your computer with ADB, editing it and pushing it back, but Root Explorer is much faster and easier to work with.
Edit: this issue has nothing to do with the CSE or what it is set to.

Thanks
rgbc said:
Open /system/build.prop in Root Explorer's text editor on the Tab, change XXJME to XXJK5, or whatever your stock version was (XXJK5 should work fine though), in ro.build.fingerprint. This will allow you to see your missing and protected apps in the market.
You can also edit build.prop by pulling it to your computer with ADB, editing it and pushing it back, but Root Explorer is much faster and easier to work with.
Edit: this issue has nothing to do with the CSE or what it is set to.
Click to expand...
Click to collapse
Thanks, that solved my problem!!!

rgbc said:
Open /system/build.prop in Root Explorer's text editor on the Tab, change XXJME to XXJK5, or whatever your stock version was (XXJK5 should work fine though), in ro.build.fingerprint. This will allow you to see your missing and protected apps in the market.
You can also edit build.prop by pulling it to your computer with ADB, editing it and pushing it back, but Root Explorer is much faster and easier to work with.
Edit: this issue has nothing to do with the CSE or what it is set to.
Click to expand...
Click to collapse
Problem solved! Thank you so much! I think I'm fast becoming a fan of these forums

biopsin said:
Eris fix is also not showing in market..
Click to expand...
Click to collapse
Lol, how funny !! It does on mine though when I've flashed new firmware.

let me get this straight. so i edit out anything that says xxjme with xxjjb in build.prop. ?
ever since ive been using roto's jme i can never find atomic bomber
i have market enabler. but i fake us tmobile and verizon and i can never see atomic bomber. going through withdrawals

b0ricuaguerrero said:
let me get this straight. so i edit out anything that says xxjme with xxjjb in build.prop. ?
ever since ive been using roto's jme i can never find atomic bomber
i have market enabler. but i fake us tmobile and verizon and i can never see atomic bomber. going through withdrawals
Click to expand...
Click to collapse
No just edit the ro.build.fingerprint. That did it for me. I just replaced JME with JK5.

kånda said:
No just edit the ro.build.fingerprint. That did it for me. I just replaced JME with JK5.
Click to expand...
Click to collapse
I am having the same issue as op. Where do I find the ro.build.fingerprint file to edit?
Sent from my GT-P1000 using Tapatalk

balto said:
I am having the same issue as op. Where do I find the ro.build.fingerprint file to edit?
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Wow, I am slow today, re read the post and figured it out.

julianLo said:
Have you checked your CSC Code?
# cat /sytem/csc/sales_code.dat
Should be DBT for germany.
to change the sales code, you can simply remount the system filesystem read/write ,
echo "DBT" >/system/csc/sales_code.dat
and reboot.
Click to expand...
Click to collapse
Does it mean that you can change CSC without doing *#272*IMEI# and a full wipe ? Is it working for samsung app as well ?

Interestingly I changed my code from JME to JJ4 which is the original firmware my GT came with, but still wouldn't find b0ricuaguerrero's game. Changed it to JK5 and it popped up.
The idea obviously works well though, cheers!

rgbc said:
Open /system/build.prop in Root Explorer's text editor on the Tab, change XXJME to XXJK5, or whatever your stock version was (XXJK5 should work fine though), in ro.build.fingerprint. This will allow you to see your missing and protected apps in the market.
You can also edit build.prop by pulling it to your computer with ADB, editing it and pushing it back, but Root Explorer is much faster and easier to work with.
Edit: this issue has nothing to do with the CSE or what it is set to.
Click to expand...
Click to collapse
I can't open then file using the text editor as it tells me it is a read-only file, and i am not comfortable using ADB, any other suggestions?
EDIT: ok never mind i was able to do it, but when i launch the market i only see 2 apps that installed and nothing else....
EDIT: ok i think either market is started to work properly on its own or i may have fixed it but all i did was re-flash JME v4 and so far it seems to work, but sure was a pain in the you know what.......

[Q] Buying apps from Android Marketplace

I've checked as well as I could in KF forum and haven't run across this problem. When I try to download select apps Google Play it tells me they aren't compaible with my device. One was Draw something and I could use an .apk I got from 4shared before they updated it so I know it works. Is there a known solution to this. I've read about changing a file in \system but as far as I can tell that dir doesn't exist. I would think KF would have to have that, I just can't get to it.
Also what exactly does the Replace Framework-res in the KFU do? Does in just replace everything if you screw it up?

I remember when I had my nook color I was able to change some txt file to make the nook appear as a another device allowing more access to apps I didn't have before. I believe Paul O'Briens rom currently does that. Not sure how its being down now but you might find something there.
Sent from my Amazon Kindle Fire using xda premium

Yeah I figured out the whole \system business and feel retarded from that. Ill try editing tomorrow and if that's too much ill just check out that mod. Thanks for the help.

Comprehensive guide to rooting and configuring the Nook Touch. For new bees.

After many hours of reading and searching these forums for answers to various questions I had when rooting my new nook, I decided to write out all the answers the average user (like me) will wish he had known before he started. So here you go, I present all you need to know about rooting and configuring your nook from the box to the promised land of awesomeness.
This is for the Nook Simple Touch (also called NST, N2E) non-glowlight version. After you root your nook, the software advice should be the same, but if you have a glowlight version, see the post by ladykayaker below. http://forum.xda-developers.com/showpost.php?p=36035695&postcount=2
A. Rooting
1) Backing up
--- noogie.img
--- nookmanager
--- reclaiming and reformatting your micro sd after using winimage.
2) Firmware version
--- does version matter?
--- updates
3) Touchnooter
B. First Configuration
--- what to expect
--- getting google play and web browsing to work.
--- installing apps from micro sd
C. Make it awesome
--- apps you'll need to patch missing nook functions
--- Multi-touch, fast ink modes, and kernal mods
--- Battery
D. Phone specific apps
--- whatsapp, and getting an IMEI on your nook
--- Phone contacts
E. List of current unsolved problems
--- Media scanner
--- scrolling
--- keyboards
--- video support in certain apps
--- audio
A. Rooting
Part 1. Backing up.
Q: Can I get my device back to stock?
A: Yes, if you take backups before you start.
Step 1. Take your nook out of the box
Step 2. Register for a barnes and noble account
Step 3. http://forum.xda-developers.com/showthread.php?t=1142983
--- Noogie.img full partition backups ---
In English, this means you have to download noogie.img, and download winimage and use it to (CAREFULLY) write the image to a micro sd card. Boot your nook with the micro sd card. Then use winimage again to copy the physical disk (1.8gb) to a file. Now you can always go back to your stock nook, apparently.
--- Easy Backups and Restoring with Nook Manager ---
You can never be too safe. I suggest you backup with 2 methods.
Search "nookmanager for 1.21 and beyond".
Download nookmanager and write it to a micro sd card just like you did for noogie. Nook manager has a brilliant backup and restore feature and works on all versions, so boot into it and follow the menu to take a backup, it creates a second backup partition on your micro sd. So when you're done, plug in your nook and copy the backup file off and the md5 hash. Follow the previous step to reclaim your micro sd.
--- Reclaiming Your Micro SD ---
To reclaim your micro sd, on windows click start menu, search partition, and open the partition manager. Find your micro sd card which now has a small partition on it, select the partition, and delete it. Right click >> create simple partition >> fat32
Backup(s) finished.
2. Firmware
--- Firmware Version ---
Q: Does firmware version matter?
A: Yes it does, make sure you search for 1.1 update and update your version to 1.1 before rooting with touchnooter. Don't bother with 1.21 yet because all the cool things you've seen and want are done with 1.1 and 1.21 root needs more time to mature and become more user friendly (noob friendly).
To check your firmware version go into settings > device info.
--- updates ---
Q: How do I update to 1.1?
First check your firmware version, if it's 1.0.1, update to 1.1 by downloading the 1.1 firmware (it's a zip file) and moving it into the nook drive on your computer. It will update automatically. Don't wait too long to backup or move to 1.1 because it might automatically update to 1.21. You should update to 1.1 and root immediately. If your device came with 1.2, try this to flash and install 1.1: http://forum.xda-developers.com/showthread.php?t=1475613
--- touchnooter ----
Once you're on 1.1, download touchnooter and like noogie and nookmanager, make an image on your microsd with winimage and boot the device. the screen will turn black, and then you can take the card out and reboot. However, I found that after running the root once, many /most of the applications didn't function, I had to boot three times with touchnooter for most apps to work. It doesn't hurt so just do it if you have any problems.
B. First Configurations
--- What To Expect ---
Now that you're rooted and running in android, you're probably thinking, "well this sucks, the web browsers don't work and neither do the app stores...."
Calm yourself, it will get better.
--- Getting GAPPS and web browsing ---
Add a google account in gmail, sync it, sign into the same google account with youtube (nobody knows why). Then you will have to "wait a day" for it to work...
Q: Wait a day? FUUUUUU
A: Just joking, you can add another google mail account and sync that, your google play will now work without the wait, but it can be a bit tricky to hit the agree to tos button.
Reclaim your micro sd, you'll need it to install apps if your Opera Mini isn't working.
Search google for opera mobile, download the apk onto your micro sd, it's on opera's website, you should also download opera mini so you can re-install the one that comes loaded if it doesn't work. Rooting several times fixed my opera mini, but if yours is broken re-installing should fix it.
--- installing apps from micro sd ---
Q: How to install apps from micro sd?
A: Find the super manager, open it up, click the button to grant super user privileges, on the second or third tab from the left there is a file manager. Go into it, click the apk, click install.
C. MAKE IT AWESOME
Now that you have opera mini/mobile, can browse the web and google play works, what next?
--- apps you'll need to patch NST broken functions ---
1. Google play search function is broken, before you can start installing apps quickly, use opera mini to search for "search market" , you'll find the google play link, click it, install it.
2. default android home screen looks bad and custom wallpaper support is broken.
Now you probably want a decent looking home screen because face it, adk looks like crap, and you probably noticed you can't set the wallpaper because the media scanner doesn't detect any media = empty gallery = can't select a wallpaper.
use search market to find legacy launcher, install it
search for "wallpaper changer" and "es file explorer", install them. You can now set the wallpaper to any file on your sd card, and your android launcher looks great. Try adusting the font size in settings and adding widgets later.
3. Gallery doesn't work because media scanner is broken.
Some apps require the gallery to work to select images.
Your solution is to download the app "Quickpic" - it will allow you to choose pictures in apps that need a gallery.
4. The default keyboard is not very good, and the nook disables all spelling suggestion bars from keyboards. This makes t9 and chinese input impossible, and can make typing a pain in any language. The solution is to download a back-port keyboard.
Jellybean keyboard is a good back-port, search and install it, it's fully functional with lots of languages. No t9 though
1/2 OF GUIDE. CONTINUED IN MY NEXT POST

notes for Nook Simple Touch with Glowlight
If you have the US Nook with glowlight, firmware version 1.1.5, then follow these instructions :
backup
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
root
http://blog.the-ebook-reader.com/20...using-glownooter-includes-googles-app-market/

2/2 OF GUIDE.
--- Kernel, fast ink modes, and multitouch---
If you want multi touch and fast ink, search for oc kernel 1.66 with fastmode. it includes all you need for multitouch and overclocks the cpu. slightly.
FYI: You will need something called "Clockwork mod" or CWM to install the kernel. Google it, you'll need to image it to your micro sd just like you did for noogie.img. After you're done, copy the oc kernel zip file into the root directory, boot up your nook with the CWM sd inserted and follow the instructions to install package from zip.
Fast ink options:
Fast mode vs no refresh
fast mode is highly dithered, and as a result small text is unreadable. however it affects the system wide and it doesn't have any compatibility issues. No refresh is high contrast, low dithering means low dynamic range but text is very readable and sharp. The disadvantage is it seemed very buggy and it's application specific, ie- you have to enable it in each application and it gets a bit buggy or laggy when it switches on and off. It has a lot more configuration potential than fast mode though. I prefer fast mode because it's simple, and very fast. It just works.
--- Battery ---
You'll notice your battery suck as soon as you root. This isn't widely discussed, but it turns out it's do to certain phone system resources being active. This can eat up 10 times more battery than your screen, and a hundred times more than anything else, even using fast mode liberally. Go into file manager and rename /system/app/phone.apk and telephonyprovider.apk. Reboot immediately.
I suggest you also download the app "deep sleep" as well. Battery manager plus is also a good application to keep track of applications individual battery useage.
D. Phone Specific APPS
Q: I want whatsapp
You need to install a static IMEI, google imei nook touch xda and you'll find the thread. Download the exe, install it.
On your phone use search market to install "wifi adb" in wifi adb select on, note the ip address.
Run the imei app you got from xda dev and it will give you a static imei.
install the latest version of whatsapp. You'll notice you can't message anyone or add contacts because nook contacts doesn't work.
download go contacts ex and it will be ok.
E. Current major issues to consider and how to fix them:
--- Scrolling: ---
problem: Scrolling does not work properly, if you use chat programs, or google voice etc. you'll find yourself scrolling through the conversation manually every time. Some apps have difficulty scrolling at all.
Solution: No known fix at this time
--- Media scanner (media storage) ---
Problem: Media scanner fails to add media files from sd card into the media database. This means the default gallery and music applications won't detect any media.
Solution: No known direct solution, although you can edit the db manually using sql.
A better solution is to download an application which includes it's own embedded media search function. An example being quickpic as a gallery replacement.
--- Keyboards ---
problem: Keyboards are missing the text suggestion bar, this means that t9 input and language input like chinese are difficult/impossible.
Solution: Download a back-ported keyboard. Jellybean keyboard is by far the best, have extensive mutli-language support, and the text suggestion bars displays properly. The only downside is it does not have a t9 layout. Baidu, sougou, or any chinese t9 keyboard software will not work on the nook until the proper dependencies/support is patched somehow.
---video support ---
Q: Can I play video?
You can, but you'll be limited to about 10-15 fps with no audio and it will be 1 bit dithered. Download rockplayer to play various video formats. There appears to be a problem with hardware video decoding and only software video players work at the moment. If I discover a fix for broader video support I'll update this.
--- audio ---
Q: Can I play audio?
A: There are some people working on audio implementation through usb host and a cheap 2 or 3 dollar dongle. However, it seems like it's very 'alpha' at the moment, until someone writes an app to automatically configure audio through usb hosts, you can probably forget about it unfortunately.
I'll update this later.

Hi nice so far
You say " make sure you search for 1.1 update and update your version to 1.1 before rooting with touchnooter. Don't bother with 1.21 yet because all the cool things you've seen and want are done with 1.1"
But what if you bought your device lately and it already came with FW 1.2.0 then what do you do?

180 people read this thread and only 6 bothered to click on thanks?? Come on guys!

bentwand said:
But what if you bought your device lately and it already came with FW 1.2.0 then what do you do?
Click to expand...
Click to collapse
+1
Sent from my GT-N7000 using xda premium

apap said:
+1
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I used this
forum.xda-developers.com/showthread.php?t=1475613

fosselman said:
I used this
forum.xda-developers.com/showthread.php?t=1475613
Click to expand...
Click to collapse
Thanks for the input, did your device come loaded with 1.2 or was it the result of an automatic update? I updated my guide with a link to touch-formatter.

jun127 said:
Thanks for the input, did your device come loaded with 1.2 or was it the result of an automatic update? I updated my guide with a link to touch-formatter.
Click to expand...
Click to collapse
Mine was on 1.0.x and I manually updated to 1.2.0 and then found out about rooting and wanted gapps so I downgraded to 1.1.0.

bentwand said:
But what if you bought your device lately and it already came with FW 1.2.0 then what do you do?
Click to expand...
Click to collapse
fosselman said:
I used this
forum.xda-developers.com/showthread.php?t=1475613
Click to expand...
Click to collapse
I bricked my new 1.2.0 device and the thread in the link above saved my butt. That said, it convinced my NSTG that it was a standard Simple Touch (no more glowlight function). I've been looking around for an update to NSTG 1.5 firmware to start over with, hoping the light features will come back. If any of you old salts can let me know if that's even possible I'd appreciate it.
If you're still at 1.2, this thread looks promising: http://forum.xda-developers.com/showthread.php?t=1675706&highlight=nstg&page=12

Looking at the ;ast pages of the NookManager rooting process it appears that the Amazon App store is US based and doesn't work for UK users (for example). Is there any simple method to fix that so it works outside of the US?
(Post i'm referring to - http://forum.xda-developers.com/showpost.php?p=36210882&postcount=110)

Thanks for clearing up the fastMode/noRefresh situation!

I have rooted NST by NookManager. The first step after that was to register device in DeviceRegistrator.apk. Next I installed ale stuff (gapps, amazon ect.) If I decide to flash kernel, it will be necessary to do it again?

Thanks, very in-dept
Renaming Phone.apk and TelephonyProvider.apk to avoid battery drain didn't work for me. I had to delete both and reboot. Now I can use my nook without losing too much battery
Used Total Commander app as my file manager to access /system/app/
Do you have a recommendation for a launcher other than ReLaunch?

dalovar said:
Renaming Phone.apk and TelephonyProvider.apk to avoid battery drain didn't work. I had to delete both and reboot. Now I can use my nook without losing too much battery
Used Total Commander app as my file manager to access /system/app/
Do you have a recommendation for a launcher other than ReLaunch?
Click to expand...
Click to collapse
I use lightning launcher it is lite weight and works well for me.

dalovar said:
Renaming Phone.apk and TelephonyProvider.apk to avoid battery drain didn't work for me. I had to delete both and reboot. Now I can use my nook without losing too much battery
Used Total Commander app as my file manager to access /system/app/
Do you have a recommendation for a launcher other than ReLaunch?
Click to expand...
Click to collapse
I've used ADW Launcher EX for years, and still loving it. Best customizability on any Nook Touch-compatible launcher, at least in my opinion.

Guys after successfully rooting my device and using it for some time it occurred to me that I would spend the $5 gift that comes with every NST. After buying books on B&N and turning on my nook I realized that nook's original software can't connect to the internet even when connected to my home's wifi connection.
I get the error: "Sorry, a problem has occurred. Please try again" in both the B&N library or B&N's shop.
Has anyone been able to download/sync books from B&N AFTER rooting your device?
Is this just a problem that I'm experiencing?
Thank you

dalovar said:
Guys after successfully rooting my device and using it for some time it occurred to me that I would spend the $5 gift that comes with every NST. After buying books on B&N and turning on my nook I realized that nook's original software can't connect to the internet even when connected to my home's wifi connection.
I get the error: "Sorry, a problem has occurred. Please try again" in both the B&N library or B&N's shop.
Has anyone been able to download/sync books from B&N AFTER rooting your device?
Is this just a problem that I'm experiencing?
Thank you
Click to expand...
Click to collapse
"Can't connect to the internet" at all or just to the B&N sites? If you've disabled/deleted some of the B&N apps you could have problems of this sort. There are all kinds of unlikely dependencies in the B&N system that can break functionality if something is missing.
I'm working with a rooted and modified NST running FW 1.21 and the only limitation I've seen so far is not being able to connect in-store (but I intentionally altered the QuickNav buttons to eliminate "Shop"). I haven't purchased books from B&N but have selected "Free Friday" offerings from the website and they come right down to my NST when it's online, no problem.
I assume you had no problem registering your device, otherwise I would suggest that maybe that error was due to B&N blacklisting the serial number. That's happened before with used/refurbished devices. Then a phone call is in order to B&N to get them to reverse that.

nmyshkin said:
"Can't connect to the internet" at all or just to the B&N sites? If you've disabled/deleted some of the B&N apps you could have problems of this sort. There are all kinds of unlikely dependencies in the B&N system that can break functionality if something is missing.
I'm working with a rooted and modified NST running FW 1.21 and the only limitation I've seen so far is not being able to connect in-store (but I intentionally altered the QuickNav buttons to eliminate "Shop"). I haven't purchased books from B&N but have selected "Free Friday" offerings from the website and they come right down to my NST when it's online, no problem.
I assume you had no problem registering your device, otherwise I would suggest that maybe that error was due to B&N blacklisting the serial number. That's happened before with used/refurbished devices. Then a phone call is in order to B&N to get them to reverse that.
Click to expand...
Click to collapse
Can't connect to B&N only. The rest of the internet is accessible. I can install apps from Google play from my computer to my device without problem too. The only system apps that i remember deleting are android apps (Phone.apk and TelephonyProvider.apk).
I don't think my serial number is black listed, because I was able to register my nook without problem. But is there any tool online where I could check my serial # statues that would be nice. I'm thinking of resetting to factory settings and rooting again if necessary. thanks for your help

dalovar said:
Can't connect to B&N only. The rest of the internet is accessible. I can install apps from Google play from my computer to my device without problem too. The only system apps that i remember deleting are android apps (Phone.apk and TelephonyProvider.apk).
I don't think my serial number is black listed, because I was able to register my nook without problem. But is there any tool online where I could check my serial # statues that would be nice. I'm thinking of resetting to factory settings and rooting again if necessary. thanks for your help
Click to expand...
Click to collapse
I have both of those apps disabled (.apk --> .OLD) so that's probably not it. To my knowledge there is no on-line way to check on the status of your serial number and now that I come to think of it, if you had no problem registering when you set up your Nook before rooting, there should be no problem with the serial number.
Seems like there was a post similar to yours not too long ago and going back to factory and rooting again fixed the problem, as much of a nuisance as that is. The only other thing that comes to mind is: you're not in the UK are you? Someone else posted a similar problem and it turned out that he needed a UK firmware update to account for changing B&N-UK URLs before he could connect.
If you get the problem sorted, I can't emphasize enough the importance--and convenience--of making a backup with NM. Backup early and often, especially when trying out something new. It saves so much time and hassle in the long run. But first....you need to get it in working condition

Flixster SKY GO Netflix

How the hell do i get these working. I have the MK808b
Flixster -
The app will let me play trailers but will not let me watch my own videos ? error states "we dont support your device for streaming" ..... strange that as I can watch your bloody trailers easy enough !!!!
Tried running it through the dolphin web browser and it looks like its going to work and then nothing.
SKY GO -
Same as Flixster ... on the app says not supported and through the website says i need to install silverlight
Netflix -
The app works but keeps coming up with an error. I clear the app and re-login and it works again.

Try editing build.prop model # to something like N7100 or a phone you know will be supported, it will also give this message if rooted, you need to use ota root keeper
Sent from my N7100

nitr0genics said:
Try editing build.prop model # to something like N7100 or a phone you know will be supported, it will also give this message if rooted, you need to use ota root keeper
Sent from my N7100
Click to expand...
Click to collapse
Is this easy enough to do? is it a phone or is it a tablet you edit it to ? does it screw anything else up ?

Try ota root keeper from the market first, failing that use Rom toolbox lite/pro to safely edit build.prop
Sent from my N7100

nitr0genics said:
Try ota root keeper from the market first, failing that use Rom toolbox lite/pro to safely edit build.prop
Sent from my N7100
Click to expand...
Click to collapse
I went to the latest finless ROM and I believe the build prop is already edited to a samsung phone/tablet. I think it should work but doesnt. It went further with teh SKY GO but eventually said "doesnt support HDMI" ... so somehow its detecting the hardware hdmi ? ..... Flixster is still the same .... just says device not supported.

tried OTA rootkeeper and no joy again ..... actually ended up screwing up the rooting and had to reflash the damn thing.
I wonder if it is because the ROM is pre-rooted that is causing the problem?

OK here's how to do it, this is tested working by myself on several different devices running rooted custom firmware!
Disclaimer: I'm not responsible if you brick your device!
As with anything system related make a nandroid backup first! Just incase...
Apps needed from market -
es file explorer Or any file manager with root functions to backup build.prop
Voodoo OTA RootKeeper
ROM toolbox lite/pro - pro is worth the money! But editing can be done with any text editor this just simplifies it.
Make sure your system locale is set to UK this can be found in build.prop also
Step One: backup build.prop it can be found in /system/ with file manager I recommend backing it up to an sd card
Step Two: find the following entries in build.prop and edit accordingly
ro.build.product=GT-N7000
ro.product.brand=Samsung
ro.product.device=GT-N7000
ro.product.model=GT-N7000
ro.product.name=GT-N7000
ro.product.manufacturer=Samsung
ro.product.locale.region=UK
Step Three: open up voodoo OTA RootKeeper and temp unroot device
Step Four - REBOOT YOU MUST REBOOT
Step Five: open voodoo OTA RootKeeper and make sure your device is still unrooted
Step Six: enjoy flixster (not tested with SkyGO)
Note: some of the build.prop edits may not be necessary but I'm an overkill kinda guy lol
Tapped out on my RootBox'd GT-N7k

nitr0genics said:
OK here's how to do it, this is tested working by myself on several different devices running rooted custom firmware!
Disclaimer: I'm not responsible if you brick your device!
As with anything system related make a nandroid backup first! Just incase...
Apps needed from market -
es file explorer Or any file manager with root functions to backup build.prop
Voodoo OTA RootKeeper
ROM toolbox lite/pro - pro is worth the money! But editing can be done with any text editor this just simplifies it.
Make sure your system locale is set to UK this can be found in build.prop also
Step One: backup build.prop it can be found in /system/ with file manager I recommend backing it up to an sd card
Step Two: find the following entries in build.prop and edit accordingly
ro.build.product=GT-N7000
ro.product.brand=Samsung
ro.product.device=GT-N7000
ro.product.model=GT-N7000
ro.product.name=GT-N7000
ro.product.manufacturer=Samsung
ro.product.locale.region=UK
Step Three: open up voodoo OTA RootKeeper and temp unroot device
Step Four - REBOOT YOU MUST REBOOT
Step Five: open voodoo OTA RootKeeper and make sure your device is still unrooted
Step Six: enjoy flixster (not tested with SkyGO)
Note: some of the build.prop edits may not be necessary but I'm an overkill kinda guy lol
Tapped out on my RootBox'd GT-N7k
Click to expand...
Click to collapse
Did all as you said and still no joy :crying:. Are you using an MK808b and which FW are you using ?

Not tested on 808 will see how my ug007 fairs when it arrives it may be something to do with Chinese firmware if my 007 fails rest assured I'll find a work around for it
Tapped out on my RootBox'd GT-N7k

nitr0genics said:
Not tested on 808 will see how my ug007 fairs when it arrives it may be something to do with Chinese firmware if my 007 fails rest assured I'll find a work around for it
Tapped out on my RootBox'd GT-N7k
Click to expand...
Click to collapse
Cool ! .... its a real bloody pain how they have obstructed my use. I mean they are my "purchased" videos. By doing this all they bloody well do is encourage people to go and get it by less legal means ...... muppets !
Out of interest what is the difference between ug007 and the MK808b ? ..... are they the same thing ?

They do it to avoid piracy via rooted devices
Tapped out on my RootBox'd GT-N7k

nitr0genics said:
They do it to avoid piracy via rooted devices
Tapped out on my RootBox'd GT-N7k
Click to expand...
Click to collapse
Thats what I mean .... counter-productive. I have a perfectly good copy on Flixster but because they have blocked it from me how else would I get to watch it ?
Bloody stupid

Yes but with a rooted device you can distribute that legal movie illegally - piracy
There's other mediums to watch it on, pc laptop tablet smartphone
Tapped out on my RootBox'd GT-N7k

nitr0genics said:
Yes but with a rooted device you can distribute that legal movie illegally - piracy
There's other mediums to watch it on, pc laptop tablet smartphone
Tapped out on my RootBox'd GT-N7k
Click to expand...
Click to collapse
None as convenient as my MK808b though. I have these on the backs of all my TV's now and would like to be able to access paid content. I also think its a driver for pushing people to part with more £'s. Why have one phone supported and another not. I doubt its purely to do with conflicts etc and more license fee. I suppose in that context that any of us try to fool the system by saying your device is not what it is .... is that also piracy ?
I am happy to pay .... which I have .... but I dont like being told how and on what I watch the content. Where does it end ? Android becomes Apple.

They have to cover their own asses, if they don't provide protection how long do you think they'll last with universal or Sony's lawyers? Check the FAQ on Gloucester there's very few devices not supported I think it's something to do with the firmware being Chinese based, copyright doesn't exist in China lol leave it with me my ug007 will be here soon n the fix should be generic may be because the device has HDMI output? Don't know until I play
Tapped out on my RootBox'd GT-N7k

nitr0genics said:
They have to cover their own asses, if they don't provide protection how long do you think they'll last with universal or Sony's lawyers? Check the FAQ on Gloucester there's very few devices not supported I think it's something to do with the firmware being Chinese based, copyright doesn't exist in China lol leave it with me my ug007 will be here soon n the fix should be generic may be because the device has HDMI output? Don't know until I play
Tapped out on my RootBox'd GT-N7k
Click to expand...
Click to collapse
look forward to it m8 ... certainly havent found a solution yet

They'll be one don't worry lol
Just an after thought here but there is an app on the market called device spoofer it's not free but may work for spoofing the device before you unroot and reboot
----------------
Tapped out on my RootBox'd GT-N7k

nitr0genics said:
They'll be one don't worry lol
Just an after thought here but there is an app on the market called device spoofer it's not free but may work for spoofing the device before you unroot and reboot
----------------
Tapped out on my RootBox'd GT-N7k
Click to expand...
Click to collapse
Is it ready yet ? .... jkn lol :laugh:
Had a look at that app and a bit dubious of it given the reviews it has

If you can sort out something for SKY GO on top of Flixster I will worship you as an earthly god !

KanesFist said:
Did all as you said and still no joy :crying:. Are you using an MK808b and which FW are you using ?
Click to expand...
Click to collapse
I have a mk802 IIIS I updated with the latest firmware after reboot installed superuser, rom manager and busybox.
installed busybox 1.20.x the latest one updated superuser and fixed permission with rom manager and I was rooted.
Maybe it'll work with your MK too. :fingers-crossed:

[Q] Modifying Buil.prop for App Install

Hello there. I'm not new to the Android rooting scene but am brand new to Nook. My Nook came Wednesday night and it was rooted Thursday night. My main goal of root was to install an app (Moon+ Reader) that would give me reading statistics such as time till end of chapter and till end of book. My wifes Kindle has this feature and I want it now .
So Moon+ Reader has a min-SDK version of 8 (Android 2.2). I decompiled and built it using APKTool 1.5.2 changing the min-SDK version to 7; but the app will not install on my phone or the Nook. My next step is to modify build.prop setting 'ro.build.version.sdk=8.' Now, I've modified other parameters in build.prop, but never the sdk version. Will this have any adverse reactions for the Nook? In my mind it will be fine and if the app installs and doesn't function I can uninstall the app and restore the backup of build.prop. Am I crazy here, is there another app that keeps track of statisticts? I've tried Kindle, but it did not work.
--
Mooney

JMooney5115 said:
... the app will not install on my phone or the Nook.
Click to expand...
Click to collapse
Well, why don't you find out what the problem is?
What does your logcat say?
Changing build.prop doesn't make much sense.

I may have misrepresented myself in my OP. The problem in question here is not the install of the modified APK, rather the modifying of the build.prop and the troubles (if any) associated with changing the min-SDK. Sorry I posted a thread on this because I have moved past getting this app working.

JMooney5115 said:
I may have misrepresented myself in my OP. The problem in question here is not the install of the modified APK, rather the modifying of the build.prop and the troubles (if any) associated with changing the min-SDK. Sorry I posted a thread on this because I have moved past getting this app working.
Click to expand...
Click to collapse
I just tried changing the minsdk in build.prop on my HTC One to try and install an 'incompatible app' and now I'm in a bootloop. Need to wait til I get home from work now to fix it.
Doh!

Android checks for incompatibilities between system version and app minimal required version.
Obviously, to make these congruent you can change either one.
The thing is, this will only have any utility if the app maker overestimated the level of API that they are using.
If an app is using Jellybean introduced API features no amount of lying is going to get that app to work.
So if you still want to play with lying about versions, do yourself a favor and modify the app, not the system.