Since apparently BN is still changing framework.jar, I'm making a thread to allow separate updates/downloads. framework.jar for 1.0.0 is already in market hack/autonooter/autoconfig
1.0.0 - http://www.mediafire.com/?1wb78ollpb1bd78
1.0.1 - http://www.mediafire.com/?37fugab7xo8s3j3
This framework.jar helps you get an Android ID when you first run the Market. You can replace it with the stock version once your market is working if you want, but leaving it shouldn't cause any issues either.
Um, this thread is remarkably empty.
Thank you for your work!
Not having to generate ID's manually is better than awesome ...
What did you have to change in Framework.jar I know your hacked version works. I'd just like to understand why.
johnopsec said:
What did you have to change in Framework.jar I know your hacked version works. I'd just like to understand why.
Click to expand...
Click to collapse
Google requests a valid phone ID and phone type when assigning an Android ID. Tablets tend to have neither, so Google doesn't assign an ID. It spoofs a valid phone type and ID so that Google is happy and will send you back an ID.
clockworx said:
Google requests a valid phone ID and phone type when assigning an Android ID. Tablets tend to have neither, so Google doesn't assign an ID. It spoofs a valid phone type and ID so that Google is happy and will send you back an ID.
Click to expand...
Click to collapse
Thanks. That makes sense now.
Can somebody post the stock version of either of the two files from the OP? I'm trying to get this working on the eLocity tab and, since I'm no developer, I need to compare the two files to see what Clockworx change... and therefore, what I should try changing in our framework.
Thanks!
Billy
JeepFreak said:
Can somebody post the stock version of either of the two files from the OP? I'm trying to get this working on the eLocity tab and, since I'm no developer, I need to compare the two files to see what Clockworx change... and therefore, what I should try changing in our framework.
Thanks!
Billy
Click to expand...
Click to collapse
If you want to post your framework.jar, it would probably be faster.
clockworx said:
If you want to post your framework.jar, it would probably be faster.
Click to expand...
Click to collapse
Fine by me! I was tying not to be a bother
http://www.slicky.net/android/elocity.a7.framework.jar
Thanks a bunch!
Billy
JeepFreak said:
Fine by me! I was tying not to be a bother
http://www.slicky.net/android/elocity.a7.framework.jar
Thanks a bunch!
Billy
Click to expand...
Click to collapse
Here it is if you want to take a shot.
http://www.mediafire.com/download.php?dd9zif5h89ve7mz
I would back up your stock one and ensure you can restore it, just in case.
This might not be the place or already covered, but is it possible to make the big button in the notification bar not pop up the B&N Soft Buttons? I tend to hit that far too often.
Personally if it was gone, or did nothing, I'd be happy. I can launch the apps from ADW myself, they're all individual apps anyway.
clockworx said:
Here it is if you want to take a shot.
http://www.mediafire.com/download.php?dd9zif5h89ve7mz
I would back up your stock one and ensure you can restore it, just in case.
Click to expand...
Click to collapse
Awesome man! Thanks a bunch!
Billy
clockworx,
can i replace framework.jar from slide_update.zip (BN 1.0.1) with yours
and also what i said in your other thread (supernooter) and then flash the ereader.
I am asking too many questions as i dont want to end up with an over sized 7" ice scraper...
I'm in the same spot as JeepFreak, but mine's a Cruz Reader.
If i upload the framework.jar can you mod it?
P.S. its Eclair-2.0 otherwise i'd try and use an existing copy off the web.
Skwurlsoft said:
I'm in the same spot as JeepFreak, but mine's a Cruz Reader.
If i upload the framework.jar can you mod it?
P.S. its Eclair-2.0 otherwise i'd try and use an existing copy off the web.
Click to expand...
Click to collapse
Are you using a custom firmware for it? I could have sworn someone had already done it for the CR over at Slatedroid. If not, feel free to upload and link.
Skwurlsoft said:
I'm in the same spot as JeepFreak, but mine's a Cruz Reader.
If i upload the framework.jar can you mod it?
P.S. its Eclair-2.0 otherwise i'd try and use an existing copy off the web.
Click to expand...
Click to collapse
We actually ended up getting the eLocity going without using the modified framework.jar.
Billy
clockworx said:
Are you using a custom firmware for it? I could have sworn someone had already done it for the CR over at Slatedroid. If not, feel free to upload and link.
Click to expand...
Click to collapse
nope, stock firmware, I've been trying to re-create the custom firmware that Velocity Micro made for it, but I'm having trouble figuring out exactly what settings they used for the kernel config. I'd like to eventually roll my own firmware image and update the device to either Éclair-2.1 or Froyo-2.2, but that will be awhile.
Until just now I'd never heard of Slatedroid, so i wouldn't know if anyone has succeeded over there or not. I've tried searching using Yahoo, Google and others to no avail, so...
here's the framework.jar, pulled from the most recent firmware update
(version 091257)
'mediafire'/?c76hrb1awmtc4mq
sorry 'bout the link being butchered, I'm a new user and it won't let me post links.
thanks in advance
Edit:I found the post at Slatedroid, but he's using a modded Cruz 102/103 Tablet firmware with Éclair-2.1, and until I get my own rom cooked, I'm going to try and stay as 'stock' as possible. besides, i don't know if the Cruz 103 firmware will work on the reader.
On another note, would it be possible to pre-mod the file in question if you were building from source?
and if so, what modifications would need to be made?
clockworx said:
Google requests a valid phone ID and phone type when assigning an Android ID. Tablets tend to have neither, so Google doesn't assign an ID. It spoofs a valid phone type and ID so that Google is happy and will send you back an ID.
Click to expand...
Click to collapse
I am working with others in another thread to determine why nootering the NC removes the access to B&N instore features.
We have been trying changes to the build.prop file but this does not seem to help. My thought is that something is changed in the framework.jar file that when instore B&N checks to see if the device is a NC. Is this a plausible thought? Can you share what lines in the hacked framework.jar are different that the stock NC framework.jar? Would it be possible to change these lines back to stock after nootering to gain access to the instore features?
Also, could changes in framework.jar also expalin why the market on NC does not have access to some apps?
nikto34 said:
We have been trying changes to the build.prop file but this does not seem to help. My thought is that something is changed in the framework.jar file that when instore B&N checks to see if the device is a NC. Is this a plausible thought?
Click to expand...
Click to collapse
Anything is possible since we don't know what they're doing, but it seems unlikely BN would check phone type and phone ID when on a regular nook they probably both return "invalid". Before you go through the trouble of investigating deeper, I suggest taking the engineering approach and change one variable: push back a stock framework.jar and see if the store works. If it does, then it's the framework.jar. If it doesn't, then it's something else.
nikto34 said:
Also, could changes in framework.jar also expalin why the market on NC does not have access to some apps?
Click to expand...
Click to collapse
No, that would be the fingerprint needed in build.prop, which I thought had already been solved and was part of Autonooter.
clockworx said:
Anything is possible since we don't know what they're doing, but it seems unlikely BN would check phone type and phone ID when on a regular nook they probably both return "invalid". Before you go through the trouble of investigating deeper, I suggest taking the engineering approach and change one variable: push back a stock framework.jar and see if the store works. If it does, then it's the framework.jar. If it doesn't, then it's something else.
No, that would be the fingerprint needed in build.prop, which I thought had already been solved and was part of Autonooter.
Click to expand...
Click to collapse
Thanks for the idea! Do you have or know where to find a stock framework.jar?
As for the fingerprint issue, we have tried returning the rooted NC fingerprint back to the stock fingerprint with no success. When replicating the stock build.prop file on a rooted NC, instore features still do not work and some apps are still not available in the market.
Related
There is a hack going around that I have been playing around with that unfortunetly I have not been able to get working. It is an edit for the Build.Prop file in \system. (this does require a root and some sort of root explorer) (I've tried some of the other "hacked" APK's, but I can't deal with crappy video)
Take a quick look at this article on Reddit:
http://www.reddit.com/r/Android/comments/ha5oh/root_how_to_edit_your_buildprop_to_make_netflix/
After looking at that for a while I started tooling around.
Changes I made :
ro.product.model=Nexus S (Replacing MB860)
ro.product.model.internal=Nexus S (Replacing MB860)
ro.product.manufacturer=samsung (Replacing motorola)
So basically, this is supposed to fool the device check by making the application think you are using an accepted device. Like I said I haven't been able to get it to work. If anyone can see any other changes to make, any input would be appreciated. Hopefully we can get this working and share it with the community, until Netflix decided to come to their senses.
I've attached the Official Netflix app if anyone needs it
Already a working app..
Someone already posted a APK that bypasses the check.. there are video issues with colors, but that is the Atrix screen not the App...
also i'm pretty sure root explorer is a paid app, so posting that here violates terms and conditions
raybond25 said:
also i'm pretty sure root explorer is a paid app, so posting that here violates terms and conditions
Click to expand...
Click to collapse
Thanks I wasn't paying attention to what I was doing. I've removed it
sublimejosh2000 said:
Someone already posted a APK that bypasses the check.. there are video issues with colors, but that is the Atrix screen not the App...
Click to expand...
Click to collapse
How is it the screen? (not arguing, I just don't know)
I was hoping that this might just fix that problem
CingZack said:
How is it the screen? (not arguing, I just don't know)
I was hoping that this might just fix that problem
Click to expand...
Click to collapse
It something to do with either hardware acceleration of how the app handles teh qHD screen. the Watch ESPN app does thes same thing.
also this method is not a good idea when compared to using the modified APK, because you are editing your actual system files through this way. and as said before this has been discussed and a different way found already on this forum.
CingZack said:
How is it the screen? (not arguing, I just don't know)
I was hoping that this might just fix that problem
Click to expand...
Click to collapse
The Atrix has a higher resolution screen than every other android phone currently available. An app, especially a graphically intensive video app, has to be designed to scale up to this resolution. Not to say it can't work, just doesn't yet.
Sent from my MB860 using XDA Premium App
what can I use to modify the apk? I have the modified apk already, but I want to take a look
CingZack said:
what can I use to modify the apk? I have the modified apk already, but I want to take a look
Click to expand...
Click to collapse
if you don't already know how to modify APKs, then you're in over your head.
dLo GSR said:
if you don't already know how to modify APKs, then you're in over your head.
Click to expand...
Click to collapse
I am trying to learn, thats why I asked, and why I come to this forum
CingZack said:
I am trying to learn, thats why I asked, and why I come to this forum
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1060199
apk Manager is a start.
jimbush3 said:
http://forum.xda-developers.com/showthread.php?t=1060199
apk Manager is a start.
Click to expand...
Click to collapse
Thanks downloading right now
I had success getting Netflix to work on Viewsonic G-Tablet running CM 7.0.3.
I used the instructions posted by natemckn at reddit. As a noob, I'm not able to post links to the XDA forum (yet), so you'll need to search for the instructions on reddit or google. The post is titled "[ROOT] How to edit your build.prop to make Netflix work on unsupported devices."
Specifically, I modified these two lines in build.prop:
ro.product.model=HTC Vision
ro.product.manufacturer=HTC
Also, I moved NetFlix to my external SD card.
Rebooted, everything works like a champ.
http://forum.xda-developers.com/showthread.php?t=994974
There's already a thread discussing all of this. Please avoid duplicate threads.
I don't know how many chefs read this side of the forum, but I know I'll get my hand slapped for posting this in the development side.
But now that Swype beta is available to pretty much everyone, why are we including the stock version anymore? Everyone seems to do it, and it's difficult to remove to install the beta.
It's obvious that the old version doesn't play nice with Gingerbread's text selection process, and the new version has solved that issue.
Can anyone explain why we're still including an almost useless version?
gspitman said:
I don't know how many chefs read this side of the forum, but I know I'll get my hand slapped for posting this in the development side.
But now that Swype beta is available to pretty much everyone, why are we including the stock version anymore? Everyone seems to do it, and it's difficult to remove to install the beta.
It's obvious that the old version doesn't play nice with Gingerbread's text selection process, and the new version has solved that issue.
Can anyone explain why we're still including an almost useless version?
Click to expand...
Click to collapse
I can cook you up a straight stock rom without it. It's only an apk you can uninstall with tb
Sent from my PG86100 using Tapatalk
aray92 said:
I can cook you up a straight stock rom without it. It's only an apk you can uninstall with tb
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Thank you, but that's not really the point. I can remove it from any ROM, just asking why we're bothering to include something that generally doesn't work with our version of the OS.
gspitman said:
I don't know how many chefs read this side of the forum, but I know I'll get my hand slapped for posting this in the development side.
But now that Swype beta is available to pretty much everyone, why are we including the stock version anymore? Everyone seems to do it, and it's difficult to remove to install the beta.
It's obvious that the old version doesn't play nice with Gingerbread's text selection process, and the new version has solved that issue.
Can anyone explain why we're still including an almost useless version?
Click to expand...
Click to collapse
+1 10chars
gspitman said:
Thank you, but that's not really the point. I can remove it from any ROM, just asking why we're bothering to include something that generally doesn't work with our version of the OS.
Click to expand...
Click to collapse
its included because its the only authorized version allowed to be distributed by the manufacturer, if the developer ( the Rom maker ) included it, swype could get pissed and ask for a take down. you need to sign up for an account and be part of the beta to get it.
so in short.. its against Swype's ToS and EULA. in order to avoid complications, rom makers dont include it
Spyderekz said:
its included because its the only authorized version allowed to be distributed by the manufacturer, if the developer ( the Rom maker ) included it, swype could get pissed and ask for a take down. you need to sign up for an account and be part of the beta to get it.
so in short.. its against Swype's ToS and EULA. in order to avoid complications, rom makers dont include it
Click to expand...
Click to collapse
That's just it, I'm not asking to include the new version... just to NOT include the old one.
The old one doesn't really work, and prevents the easy installation of the new one.
So why include broken software?
gspitman said:
Thank you, but that's not really the point. I can remove it from any ROM, just asking why we're bothering to include something that generally doesn't work with our version of the OS.
Click to expand...
Click to collapse
It's not just the APK, there's a file in system/lib that needs to go too. Last paragraph:
http://forum.swype.com/showthread.p...install-Swype-Swype-PreLoad-Production-Device
Edit: Instead of requesting the devs remove, write a quick script that will remove the old. Then you just need run it once whenever you install a new rom.
lyric911 said:
It's not just the APK, there's a file in system/lib that needs to go too. Last paragraph:
http://forum.swype.com/showthread.p...install-Swype-Swype-PreLoad-Production-Device
Edit: Instead of requesting the devs remove, write a quick script that will remove the old. Then you just need run it once whenever you install a new rom.
Click to expand...
Click to collapse
Again, I know how to remove it, I know that it's possible to remove.
The question that no one is answering is WHY INCLUDE SOFTWARE THAT IS NOT COMPATIBLE WITH GINGERBREAD?
Sorry for yelling, but I'm trying to grasp the value of having the original package.
gspitman said:
Again, I know how to remove it, I know that it's possible to remove.
The question that no one is answering is WHY INCLUDE SOFTWARE THAT IS NOT COMPATIBLE WITH GINGERBREAD?
Sorry for yelling, but I'm trying to grasp the value of having the original package.
Click to expand...
Click to collapse
Am I the only one who's seeing the same trend here that happened in the movie "Anger Management"?
He's only asking "Who you are." LOL
gspitman said:
Again, I know how to remove it, I know that it's possible to remove.
The question that no one is answering is WHY INCLUDE SOFTWARE THAT IS NOT COMPATIBLE WITH GINGERBREAD?
Sorry for yelling, but I'm trying to grasp the value of having the original package.
Click to expand...
Click to collapse
Woops. Meant to quote aray92, not you since he/she said only the apk must be removed.
lyric911 said:
It's not just the APK, there's a file in system/lib that needs to go too. Last paragraph:
ht tp://forum.swype.com/showthread.php?2287-Unable-to-uncheck-uninstall-Swype-Swype-PreLoad-Production-Device
Click to expand...
Click to collapse
Thank you for the link. The Swype beta always crashed for me and now I know why. I removed the files and now Swype works. Thanks!
I agree, I want to be able to install the latest swype. If I recall correctly, couldn't they make it so we could uninstall? I think that's how it was with OG Evo custom roms.
It's been removed from mine from day one.
I thoroughly inspect my ROM for every instance of software that I don't want.
gspitman said:
That's just it, I'm not asking to include the new version... just to NOT include the old one.
The old one doesn't really work, and prevents the easy installation of the new one.
So why include broken software?
Click to expand...
Click to collapse
1) It works just fine.
2) It takes 10 seconds to uninstall with TB.
3) Did you ever consider the possibility that some people may not have another version of swype?
nabbed said:
1) It works just fine.
2) It takes 10 seconds to uninstall with TB.
3) Did you ever consider the possibility that some people may not have another version of swype?
Click to expand...
Click to collapse
1. It doesn't work right.
2. Takes longer than that including removal of the lib files and a half dozen reboots to get the beta installed
3. F%#@ them. Majority wins and its a fantastic idea to remove it, let's get rid of car panel, Twitter, footprints, friendstream, stocks, htcfacebook, fm radio too
its not in my rom either
NewZJ said:
1. It doesn't work right.
2. Takes longer than that including removal of the lib files and a half dozen reboots to get the beta installed
3. F%#@ them. Majority wins and its a fantastic idea to remove it, let's get rid of car panel, Twitter, footprints, friendstream, stocks, htcfacebook, fm radio too
Click to expand...
Click to collapse
Done, agreed, done, may not play right, and maybe!
anyone got the new Swype beta? Haven't tried it out yet
Hello,
I own a Nook Color and plan to use it along with notebooks in school. I am getting a stylus, but the problem is the app. Is there a way to install SketchBookPro on the Nook Color? I'm running MIUI ROM. Thanks.
EDIT: Is there a way I can fake honeycomb to run this app?
You could use Sketch Book mobile but PRO requires Honeycomb.
Yeah you have to use Sketch Book Express (Free) or Sketch Book Mobile ($.99). Unless you install one of the Honeycomb roms.
Alright thanks. Boy am I sometimes dumb... figures. Thanks again!
joenathane said:
You could use Sketch Book mobile but PRO requires Honeycomb.
Click to expand...
Click to collapse
I purchased and use the Sketchbook Mobile application and find that I really like it. It scales well to the display of the NC.
I can recommend it as well.
Thanks, but I just installed Honeycomb. Just to use this app.
Just went back to MIUI for the speed. Now i'm wondering if there is a way to fake honeycomb to run this app? Or modify it to run on 2.3.3? Because I doubt it uses anything honeycomb dependent. Thanks!
ikingblack said:
Just went back to MIUI for the speed. Now i'm wondering if there is a way to fake honeycomb to run this app? Or modify it to run on 2.3.3? Because I doubt it uses anything honeycomb dependent. Thanks!
Click to expand...
Click to collapse
NO! How many times does this need answering? NO!
Right. Sorry for being a bother
/dumb
khaytsus said:
NO! How many times does this need answering? NO!
Click to expand...
Click to collapse
Instead of being rude you could explain why you can't. Things tend to stick when you explain why. I don't think we need comments like that in XDA.
Sent from my ADR6300 using XDA Premium App
ikingblack said:
... SketchBookPro on the Nook Color?
Click to expand...
Click to collapse
You can modify the AndroidManifest.xml file setting minSdkVersion="8" for froyo. I've done this for SketchBook Express free version and you can download it here: http://www.megaupload.com/?d=A5WAH4PJ
actorman46 said:
.. explain why you can't...
Click to expand...
Click to collapse
This modified apk will install fine on CM7, but force close when you try to run it because it calls on the ActionBar API, which is Honeycomb-specific. You can see this by following the logs.
ikingblack said:
... modify ... to run on 2.3.3?
Click to expand...
Click to collapse
To do this yourself next time follow these steps:
1. Use Madcat's sdk port running on Rack's SD card to install Sketchbook Express from the Market and retrieve com.adsk.sketchbookhdexpress-1.apk from /data/app
2. Get APK Manager 4.9: http://forum.xda-developers.com/showthread.php?t=695701
3. Update apktool to 1.4.1 (051511 release) for xlarge support: http://code.google.com/p/android-apktool/downloads/list
4. Extract Honeycomb framework-res.apk from any duodexed HC ROM, I used Xoom Tiamat 3.2: http://forum.xda-developers.com/showthread.php?t=1203635
5. Install HC framework for apktool per instructions here: http://code.google.com/p/android-apktool/wiki/FrameworkFiles
6. Use APK Manager to extract and decompile com.adsk.sketchbookhdexpress-1.apk
7. Modify the AndroidManifest.xml file with a text editor, I used Notepad++ in Windows
8. Use APK Manager to compile and sign apk.
ikingblack said:
... plan to use it along with notebooks in school.
Click to expand...
Click to collapse
Good luck in school.
Thank you very much. Yes, I hacked the apk before posting and it does FC. Thanks for telling me about why it FCs. Yes, thanks for the luck .
actorman46 said:
Instead of being rude you could explain why you can't. Things tend to stick when you explain why. I don't think we need comments like that in XDA.
Click to expand...
Click to collapse
It's been explained why in many other threads, including a couple others he has been involved in, possibly started. No need to waste my time regurgitating it here.
ikingblack said:
Hello,
I own a Nook Color and plan to use it along with notebooks in school. I am getting a stylus, but the problem is the app. Is there a way to install SketchBookPro on the Nook Color? I'm running MIUI ROM. Thanks.
EDIT: Is there a way I can fake honeycomb to run this app?
Click to expand...
Click to collapse
Don't bother with the stylus. They don't work well at all on the Nook... even the capacitive styluses.
khaytsus said:
It's been explained why in many other threads, including a couple others he has been involved in, possibly started. No need to waste my time regurgitating it here.
Click to expand...
Click to collapse
So i guess the rude comments you posted isnt wasting time either?
Ditto on the stylus issue...tried quite a few, haven't come across any that work well. Seems like the area the stylus touches isn't specific enough for any fine detail, or even writing properly.
I thought it might be cool if we could set the native Sense updater (In Settings>System Updates) to check for/download/install updates to roms. It would have to be modified for each rom, but probably not that hard. I did a little digging in Settings.apk, but couldn't find anything, so I started looking in Updater.apk. That is where the gold is. Everything that has to do with FOTA, System updates, anything about that is in there. On a side note, there is a smali file called PesterActivity.smali that we may be able to modify so that we don't get the notifications. Anyway, I just thought I would point the idea out so that if anyone else wants to start on it we can get it done quicker.
correct me if im wrong, but wouldn't the updater check the digital signature on the file before a flash?
koszor said:
correct me if im wrong, but wouldn't the updater check the digital signature on the file before a flash?
Click to expand...
Click to collapse
I think we could set it not to. Everything that happens inside an update can be tweaked from that app I believe.
even if we did though it couldnt give S-off could it?
This is (I assume) an idea for future use. Hope I'm not putting words in OP's mouth.
Sent from my ADR6425LVW using xda premium
YamiYaiba said:
This is (I assume) an idea for future use. Hope I'm not putting words in OP's mouth.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Yup. I'm working on it, but have nothing atm
Personally, I think it's a great idea. Checking for updates would be a lot easier lol
Isn't this already do-able through Rom Manager?
Zaphod-Beeblebrox said:
Isn't this already do-able through Rom Manager?
Click to expand...
Click to collapse
Assuming your ROM is on Rom Manager. I've never once used one that was.
YamiYaiba said:
Assuming your ROM is on Rom Manager. I've never once used one that was.
Click to expand...
Click to collapse
How hard is it for a Dev to put their Roms there? Does Koush charge for that?
Just seems a bit easier to use an already developed solution than to re-invent the wheel. Of course if its cost prohibitive, that's another story.
Zaphod-Beeblebrox said:
How hard is it for a Dev to put their Roms there? Does Koush charge for that?
Just seems a bit easier to use an already developed solution than to re-invent the wheel. Of course if its cost prohibitive, that's another story.
Click to expand...
Click to collapse
I personally don't use Rom manager, as I feel that you have more control ovrer the flashing. I have also heard stories of rom manager bricking your phone, and never felt like risking it.
Sent from my ADR6425LVW using Tapatalk
Zaphod-Beeblebrox said:
How hard is it for a Dev to put their Roms there? Does Koush charge for that?
Just seems a bit easier to use an already developed solution than to re-invent the wheel. Of course if its cost prohibitive, that's another story.
Click to expand...
Click to collapse
the biggest problem. with rom manager in my opinion.. is that it's connected only to cwr, which sucks.
dmeadows013 said:
I thought it might be cool if we could set the native Sense updater (In Settings>System Updates) to check for/download/install updates to roms. It would have to be modified for each rom, but probably not that hard. I did a little digging in Settings.apk, but couldn't find anything, so I started looking in Updater.apk. That is where the gold is. Everything that has to do with FOTA, System updates, anything about that is in there. On a side note, there is a smali file called PesterActivity.smali that we may be able to modify so that we don't get the notifications. Anyway, I just thought I would point the idea out so that if anyone else wants to start on it we can get it done quicker.
Click to expand...
Click to collapse
Thats actually a good idea. I never thoguht of that! I am going to look into it.
In my Optimus and Evo 3D ROMS I have a custom App called ROM Updater. It does exactly what you are talking about but also includes themes, ringtones, etc. And its all stored on my server and downloads to SD card then flashes.
But how cool would it be to just do updates using the HTC Built in app? I like this idea...
Here are the challanges that I see...
1. We need to to be able to get the file from the server that it parses to verify if the current version is correct. Not sure how hard that would be. We would not only need to get it but hope its in json or xml or some other human readable form so we can decipher and rebuild it.
2. Redirection to a third party server. Can it be done? I assume so. I know how to stop it from checking by nuerting the build prop so why not use the same lines to direct to another server?
Have you decompiled the APK and looked at strings.xml? Any info in there?
werdna87 said:
even if we did though it couldnt give S-off could it?
Click to expand...
Click to collapse
No... Wouldnt really do anytyhing until we had S-OFF...
koszor said:
correct me if im wrong, but wouldn't the updater check the digital signature on the file before a flash?
Click to expand...
Click to collapse
Not with a custom Reocovery. It would work fine.
YamiYaiba said:
Assuming your ROM is on Rom Manager. I've never once used one that was.
Click to expand...
Click to collapse
Zaphod-Beeblebrox said:
How hard is it for a Dev to put their Roms there? Does Koush charge for that?
Just seems a bit easier to use an already developed solution than to re-invent the wheel. Of course if its cost prohibitive, that's another story.
Click to expand...
Click to collapse
androidsupra said:
the biggest problem. with rom manager in my opinion.. is that it's connected only to cwr, which sucks.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I wont go into my ROM Manager rant like I always do... But I will just say this to answer your questions...
1. It cost nothing to put your ROM in ROM Manager
2. For a user to be able to download your submitted ROM they have to pay Koush. To me... That is so not cool he is taking cash for other Dev's ROMS. I am not fan of that.
I had one of my ROMS in ROM Manager and I was not happy to see it there. What sent me into a rampage is that someone that liked my ROM posted it in ROM manager without my permission. He accepts work from anyone with no verifiection of the author (Security Issue anyone?).
Anyways.. thats a very short synapsis of my feelings of ROM Manager.
-Scott
I looked into Strings.xml and couldn't find anything useful. I also looked into a few other .xmls and some smali files. I think that everything used to get the file downloaded is in the smalis. Not sure though, I'm not the best with smali. Strings just showed some user messages.
dmeadows013 said:
I looked into Strings.xml and couldn't find anything useful. I also looked into a few other .xmls and some smali files. I think that everything used to get the file downloaded is in the smalis. Not sure though, I'm not the best with smali. Strings just showed some user messages.
Click to expand...
Click to collapse
Yeah, most of the time the guts is in the smali but every once in a while you can find the goods in the XML's.
How many total smali files?
scrosler said:
Yeah, most of the time the guts is in the smali but every once in a while you can find the goods in the XML's.
How many total smali files?
Click to expand...
Click to collapse
I counted 103 total.
dmeadows013 said:
I counted 103 total.
Click to expand...
Click to collapse
Thats it? Thats nothing at all to look through...
Here is where I would start....
First... Look at the device build prop. Thats gioing to have the URL's of the HTC Update servers.
Second... Start searching out for either....
a) the name of those servers in the smali code
b) any strings like ".xml", ".json", "http://", "https://", ".zip" anything that would make sense (no pun).
This is just what I would do.
What are yo using for OS and app on your PC?
scrosler said:
Thats it? Thats nothing at all to look through...
Here is where I would start....
First... Look at the device build prop. Thats gioing to have the URL's of the HTC Update servers.
Second... Start searching out for either....
a) the name of those servers in the smali code
b) any strings like ".xml", ".json", "http://", "https://", ".zip" anything that would make sense (no pun).
This is just what I would do.
What are yo using for OS and app on your PC?
Click to expand...
Click to collapse
Found this in build.prop
Code:
# For FOTA setting (leave empty value to use default)
ro.htc.checkin.url = http://andchin.htc.com/android/checkin
ro.htc.checkin.crashurl = http://andchin.htc.com/android/crash
ro.htc.checkin.url_CN = http://andchin.htccomm.com.cn/android/checkin
ro.htc.checkin.crashurl_CN = http://andchin.htccomm.com.cn/android/crash
ro.htc.checkin.exmsg.url = http://fotamsg.htc.com/android/extra/
ro.htc.checkin.exmsg.url_CN = http://fotamsg.htccomm.com.cn/android/extra/
ro.htc.appupdate.url = http://apu-chin.htc.com/check-in/rws/and-app/update
ro.htc.appupdate.url_CN = http://apu-chin.htccomm.com.cn/check-in/rws/and-app/update
ro.htc.appupdate.exmsg.url = http://apu-msg.htc.com/extra-msg/rws/and-app/msg
ro.htc.appupdate.exmsg.url_CN = http://apu-msg.htccomm.com.cn/extra-msg/rws/and-app/msg
ro.config.htc.nocheckin = 1
I'm on Mac OSX 10.7 and am using Text Wrangler. I also have a Win7/Ubuntu 11.10 dualboot machine.
dmeadows013 said:
Found this in build.prop
I'm on Mac OSX 10.7 and am using Text Wrangler. I also have a Win7/Ubuntu 11.10 dualboot machine.
Click to expand...
Click to collapse
Now what you want to do is start searching the smali copde for similiar stings that are in the buildprop.
See, from my understanding, the updater looks at those build prop strings to determine where to look for and download updates.
I am assuming you have the APK decompiled?
I dont know much about Mac, a little about Ubunut but a lot about Win7.
I use Notepadd++ on Win 7 to edit smali...
What I would do next is load up the smali folder in notepadd ++. Easiest way to do this is go to the smali folder and do a search for *.smali.... when it finds them all, selct them all and choose open in Notepad++
I can get about 150 to 200 smali files open in N++ before it crashes, hehehehe
From there Notepad++ can search across all open files. I would start searching out those strings I noted and the strings in the build prop. Not sure what you will find if anything but it would be interesting to see. If you do it post any pertinent results and the file you found it in.
I'll give it a shot to but dont get out of work for another couple hours and I work 50+ hours a week for the next two weeks so time is limited but I want to see what we can figure out.
scrosler said:
Thats it? Thats nothing at all to look through...
Here is where I would start....
First... Look at the device build prop. Thats gioing to have the URL's of the HTC Update servers.
Second... Start searching out for either....
a) the name of those servers in the smali code
b) any strings like ".xml", ".json", "http://", "https://", ".zip" anything that would make sense (no pun).
This is just what I would do.
What are yo using for OS and app on your PC?
Click to expand...
Click to collapse
Found these:
In UpdaterNetworkCheck.smali
Code:
Line 13: .field private static final TEST_ADDRESS:Ljava/lang/String; = "http://apu-stage.htc.com/apu-stage/"
Line 15: .field private static final TEST_ADDRESS2:Ljava/lang/String; = "http://masd.htc.com.tw/"
Line 256: const-string v6, "http://apu-stage.htc.com/apu-stage/"
Line 308: const-string v6, "http://masd.htc.com.tw/"
Found none of the URLs. However, when looking for .zip, there was a reference to /system/etc/security/otacerts.zip. Looked inside, and it showed a release key. Looked like this:
Code:
-----BEGIN CERTIFICATE-----
MIIEnzCCA4egAwIBAgIJAIb8SbYq46gHMA0GCSqGSIb3DQEBBQUAMIGRMQswCQYD
VQQGEwJUVzEPMA0GA1UECBMGVGFpd2FuMRUwEwYDVQQHEwxUYW95dWFuIENpdHkx
GDAWBgNVBAoTD0hUQyBDb3Jwb3JhdGlvbjEMMAoGA1UECxMDU1NEMREwDwYDVQQD
EwhIVEMgQ2VydDEfMB0GCSqGSIb3DQEJARYQSHRjX0NlcnRAaHRjLmNvbTAeFw0w
ODA5MDEwODUwNTZaFw0zNjAxMTgwODUwNTZaMIGRMQswCQYDVQQGEwJUVzEPMA0G
A1UECBMGVGFpd2FuMRUwEwYDVQQHEwxUYW95dWFuIENpdHkxGDAWBgNVBAoTD0hU
QyBDb3Jwb3JhdGlvbjEMMAoGA1UECxMDU1NEMREwDwYDVQQDEwhIVEMgQ2VydDEf
MB0GCSqGSIb3DQEJARYQSHRjX0NlcnRAaHRjLmNvbTCCASAwDQYJKoZIhvcNAQEB
BQADggENADCCAQgCggEBANB9rS8wBMSZGEACPSvdQajFRPz9QPDyF26aI+W5xL7E
QX66/drzSntU0zu+M2qLBo16DYqH3irf0Pe/tvOrD3SwdTT5q25BM0tI2cEsEgR6
cw1MgEP9FvYUKhBRgqxjRXgKzdgptWSxohdli/Iq6garZhbHr0tERA1V/w3Vnj/L
hVHPdHje2svE5cGKELq+0OOZlo77jQDvXVRmdABlQrUfgam5vtYipihUY6pc1iId
yi5K8sj+KXpIcU5NMa7b1YqTfzJOdCl6BCZiZBr3JRwdC8F/J7yWlZyFtYlqKjPo
kG35rLqInp3116e195b8SJXUQflstmyN+Yv686eEhlsCAQOjgfkwgfYwHQYDVR0O
BBYEFObseus3M5qqC/iaRg7V9gTQ0KbyMIHGBgNVHSMEgb4wgbuAFObseus3M5qq
C/iaRg7V9gTQ0KbyoYGXpIGUMIGRMQswCQYDVQQGEwJUVzEPMA0GA1UECBMGVGFp
d2FuMRUwEwYDVQQHEwxUYW95dWFuIENpdHkxGDAWBgNVBAoTD0hUQyBDb3Jwb3Jh
dGlvbjEMMAoGA1UECxMDU1NEMREwDwYDVQQDEwhIVEMgQ2VydDEfMB0GCSqGSIb3
DQEJARYQSHRjX0NlcnRAaHRjLmNvbYIJAIb8SbYq46gHMAwGA1UdEwQFMAMBAf8w
DQYJKoZIhvcNAQEFBQADggEBAIfnfzMduLfgX5JCGtQ9gDsb84S6AkX7oxFA4c+T
MBqcLjwiZj168I/PB/WWMwYQls5vZnMrHCcQpz7YReK5l+DbErDE5FhqveyuhqIE
nCLJm+0bXuKdBJtjH77n8owACtafiOMBI/Ju4RKINxjLiRe1jYSwzsWcLEadWls6
bbYKbUMAdsRmH3IHkJnqwIxzsE7/TLdWCCqqVrc4aT2KvntnPG/zKL8uZuySeEmJ
ybmQeQ3D50vcNicPTVFnd43oNHUFNzdN0IKz3VedL8h/HmVqP+qoQGWaU+QF7T/y
7GpVtwjbaRo0v3aPH6t1lwxQphLHdykvt7cBzW1CGciJYcE=
-----END CERTIFICATE-----
Doubt the key would be useful, but you never know...
I am new to the android OS and havent really done much in the field of development lately... I was a BASIC and VBASIC coder back in the day... but I was going through the files on my Verizon Galaxy S4 and in /dev/_properties_ I found something labeled "ro.boot.hardware[]qcomro.boot.debug_level[]0x4f4cro.boot.cp_debug_level []0x55FFro.boot.emmc_checksum[]3ro.boot.bootloader[]i545VRUEMK2ro.boot.nvdata_backup[]ro.boot.boot_recovery... and it goes on and on. Any information would be greatly appreciated
That's code.
If I change it will it do anything?
theshedcrew said:
If I change it will it do anything?
Click to expand...
Click to collapse
Why?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Just wondering
theshedcrew said:
Just wondering
Click to expand...
Click to collapse
Its not like its just a diary from samsung... Hard to read through because your text view seems to be showing line feeds as an undisplayable characters, that box thing, whatever you want to call it.
But yeah that is one of your system files, that is data the OS uses. If you change it it will most likely just break what every thing you change from being specific code/information to random gibberish.
Just looked up the file... Thats not just a plain text file that is interpreted by the OS. I think you would have to get the source code to make changes then compile your own version.
Thanks. Like I stated above, its been a long time since ive coded (BASIC) and coding and development has come a long way since then
Use hex editor or you'll corrupt the file
theshedcrew said:
If I change it will it do anything?
Click to expand...
Click to collapse
Don't just open I with 'generic editor' and modify it and expect your device to boot properly. Use a GOOD hex editor from market and modify the values to retain proper structure or you'll regret it. You can be brave and add props not in use BUT they must present in the device for that to work. You can accomplish a lot in that file though or soft brick your device.
Yeah, I wouldn't just edit a piece of code just for the sake of editing code. Might mess your phone up.