Related
Hello,
I'm Andy, and I'm a little bit more active on other forums, but I've had my android device since November, and love it. Anyways, I had a couple of ?'s about an app I have in progress and I was wondering if what I want to do is even possible.
Basically, I want to develop a simple app, with just 1 activity. I have the graphics/XML stuff all taken care of already, thats easy peezy stuff.
Next, I want to install a file I include with the app to a specific location of the internal memory. By default, if you install a file included, it goes to /data/data/....., I would like my file to install, to /system/xbin/. I know you would need superuser permissions, thats fine, I was wondering if it was possible. If it is, would someone enlighten me as to how? If it isn't thats still fine, cause I can include the file in a flashable zip.
Next question,
Can I have my app run the file (ie. the equivalent to going into a terminal emulator and navigating to /system/xbin/ and typing the file name?) I ask this, cause all I've found is running files that located within your app, or creating files and editing them. I don't need that, I just want the file to be read.
Next, um, if the above is possible, how do I stop it?
So here is what the app would be:
usb tethering for senseui phones and 2.1. It may not work with all (probably not aria, i don't think that was included), but this method works with the Sprint Hero. I would like to make it idiot proof, as in creating the exploit into an app. One that installs the file onCreate() and then runs it with the first button press, and then kills it on the second button press and maybe adding a menu option to quit the app. Its not an app I would charge for, nor even attempt to distribute on the market. Any help is greatly appreciated. Thanks.
I dont know if this problem is known here,
all (in my opinion froyo builds) have the same android_id
In every build the id is: 9774d56d682e549c
this cause problems with some apps of the market because they use this id to identify the device. for example imobsters ;-)
see this post
forum.xda-developers.com/showpost.php?p=7251507&postcount=1110
sorry for my bad english
I think this causes a problem too with pMessenger, but I'm not sure if the Android ID or the MAC address is being used by pMessenger. However, both of them are identical on all our devices for now.
I think it should be trivial for the devs to fix it, but they are concentrating on fixing more major things now.
i am not sure, but maybe there is a way to change that id:
NOT ugly market fix
No more emulators!
Push this over to your phone, and you'll be able to get a working android ID without any sort of silly fooling around.
To repeat and clarify: You will get a fresh working Android ID, from Google, just like a phone.
From early testing it still appears SOME paid apps may be missing, but this is definitely a better solution than an ID from the 1.6 emulator as I continue to look into the issue. (I think this is actually less an Android ID issue than it is an issue with PDN being a configuration that some apps refuse to support, be it resolution, version 2.0 or whatever)
(I've also found that using your phone's ID on your PDN may "taint" what you can see in the market on your phone. Personally, I'll be moving away from sharing an ID with my phone)
Instructions
1) You'll need to remount system as R/W regardless. so let's start with that:
"adb remount"
2) If you want to start over clean, I'd recommend clearing market cache and killing your existing android ID.
adb shell sqlite3 /data/data/com.google.android.googleapps/databases/gls.db "update meta set intvalue='0' where name='androidId'";
To clear market cache: Settings->Manage Applications->press menu button->choose "Filter"->choose "All"->Scroll down to Market and select it->choose "Clear Cache"
3) Apply this hack
"adb push framework.jar /system/framework/"
4) Since we replaced a main framework, clear dalvik cache just to be safe, and reboot. Yes, the first reboot will take longer since we just cleared the cache.
"adb shell rm -r /data/dalv*"
"adb shell reboot"
5) Go ahead and log into Google Talk and use the Market to ensure all is working.
Feedback welcome!
File:
framework.jar
Click to expand...
Click to collapse
From here
I dont know if that works because its not for the hd2, but someone could try it.
I Mirrored the file in case it gets deleted:
Multimirror (Rapidshare, zshare etc.)
edit: I dont think that could work, i just tried to change to /data/data/com.google.android.googleapps/databases/ and it didnt exist at all ...
News
strazzere.com/blog/?p=217
but where can i find these "/data/data/com.android.providers.settings/databases/settings.db"
is there somebody out there who can say me how can i change my android_id on my HD2?
Whilst spending more endless hours attempting to root my wildfire, I have noticed that if I push mtd0 to sdcard as mtd0.img, and then use HxD to edit it as though to use flash_version ( I was thinking I wonder if it's possible to spoof supercid 111111) so after backing up the original I filled the entire file full of 1's (I tried 0's first, the error message tells me if i could force 0's this may be a good thing???) and flashed misc.
On entering hboot when it checks sdcard a load of 1's came up before anything else, so i repeated the experiment with stars *, and *'s is what hboot seen.
I'm thinking possiblity of some kind of alternate boot or mabye a command (fastboot oem unlock, or fastboot erase hboot) or something along those lines. Tried modifying the first line, but still came up *'s so somewhere else in the file possibly where version goes, but version doesnt usually show up on sdcheck does it.
Experiments continue
Keep up the experiments!
Thanks!
keep up doing it, you are great
thousands of people hope this work in the future...
i think unrevoked is not doing anything now
we r 4 months from 2.2....
Any more luck? How is this getting on?
dannyjmcguinness said:
Whilst spending more endless hours attempting to root my wildfire, I have noticed that if I push mtd0 to sdcard as mtd0.img, and then use HxD to edit it as though to use flash_version ( I was thinking I wonder if it's possible to spoof supercid 111111) so after backing up the original I filled the entire file full of 1's (I tried 0's first, the error message tells me if i could force 0's this may be a good thing???) and flashed misc.
On entering hboot when it checks sdcard a load of 1's came up before anything else, so i repeated the experiment with stars *, and *'s is what hboot seen.
I'm thinking possiblity of some kind of alternate boot or mabye a command (fastboot oem unlock, or fastboot erase hboot) or something along those lines. Tried modifying the first line, but still came up *'s so somewhere else in the file possibly where version goes, but version doesnt usually show up on sdcheck does it.
Experiments continue
Click to expand...
Click to collapse
I tried this a week ago and it does not seems to work :S
cid version is on "ro.cid" prop. Change cid on mtd0, flash it and then try a "getprop ro.cid"
Of course, you'll get the original CID, not the supercid. You cannot change these properties (ro.secure is another one. The ONE that prevent us from writing on system, etc)
I think these properties are Read-Only and are loaded into the system from the hboot at boot time.
I managed to change the default.prop on "/" from ro.secure=1 to ro.secure=0 but every time you reboot your phone this file goes back to ro.secure=1, so I think hboot re-load every file and prop needed for their security lock at boot.
I repeat, even with root access you won't change a single property with "ro." before.
Not a single one.
Sorry guys, we'll have to wait more...
For more information abot the proccess read my post: http://forum.xda-developers.com/showthread.php?t=1042077
As you can see, no one has answered yet so I think this is useless...
Looks promising!
Sent from my HTC Wildfire using XDA App
Think I've discovered a bit more, I'm absolutly posotive that this is the way forward. Problem is not enough people seem interested in this post.
It would appear that this can be used to issue a boot message, so please share your knowledge on what you know of boot messages, coz I'm pretty sure a boot message could be used to override certain parameters.
Please people, if you read this, HELP ME OUT
I know what are you talking about,and I think that might help you
http://runtimeworld.com/2011/04/a-complete-list-of-hboot-commands/
I could work with you on this, PM me if you are interested
edit: this command has 8 letters (like cidnum):
writemid // write model ID
The best thing u've found.. I'm feeling like we'll oly root wildfire before unrevoked.,
It'll be good if we do it our self as unrevoked has tried hard but not succeeded due to heavy lock of hboot.. If there is a luck and ability to do it, we can do it..
I dont hav knowledge in linux and android much elz i would hav joined to root wildfire with u all..
Best of luck for rooting and make sure not to brick the phone..
God, I must follow this post.
Thanks for your hard work.
Sent from my HTC Wildfire using XDA App
Maybe you'll find something interesting there
tjworld.net/wiki/Android/HTC/Vision/HbootAnalysis
sry, can't add urls i'm new
ejnreon said:
Maybe you'll find something interesting there
tjworld.net/wiki/Android/HTC/Vision/HbootAnalysis
sry, can't add urls i'm new
Click to expand...
Click to collapse
cant be THAT new if you joined in 2009 :L
I'm new to the android ecosystem but I've always been jealous of swype users, is it possible to port this feature to the nook touch?
Just replace apk file of swype with default keyboard using Root Explorer in system/app
I tried installing a keyboard apk file into system/app file by copy and paste with ES file explorer but it said failed. is there a special app or procedure I need to do this with? and where did you get the apk file? I would like a keyboard with directional arrows (for spreadsheets) and numbers for faster input. Thanks
Are you sure system is r/w?
Sent from my GT-I5700 using Tapatalk
roryn3kids using ES file explorer use the following instructions and you'll have access to r/w root files:
1. Scroll down to Root Settings and enable Root Explorer and Mount File System.
Not sure if this next step was needed but I did it anyway
2. Once again from the setting menu click on File Settings and enable "Show Hidden Files"
then copy the file from your data\app folder to your system\app folder
Swype "friendliness" to nook STR
The instructions above worked fine for me.
The problem is that I found the apk somewhere (a rather new version but still not the latest) and, even when it works, I do not get any "word list menu" like the one shown in those Swype Howto videos.
This means that, either I use an extremely short vocabulary, or I waste 50% of the time correcting the suggested word...
For instance, let's say I wanted to write f***, Swype forces me to accept the word duck.
This is good, because then I have the time to think twice before swearing but in the end... hum, let's say it's not that productive.
Of course, I checked that the options are properly configured (or I think so)
Does it happen to any of you, nook STR users?
BTW, I might also say that I cannot install the beta from swype.com/category/get-swype/
Have any of you succeeded on this?
Not that I want to re-activate a Post that was last updated in August, but it's nice to have as much information regarding swype as possible in a single post.
Thanks
I just discovered the Swype feature on my galaxy player 4.0 and it's great!
Never used Swype before this, But Since finding it a few days ago, it's all I've used! lol
Hope you get it installed, cuz its awesome.
Ok, I have further investigated the Issue and I can confirm now that it is properly configured (I compared it with some other devices) so let's ask it the other way around...
Is there any nook-STR-user who properly installed Swype?
How did you do it or, better said, where did you get your swype from?
Thanks very much, and a happy new year!
(sent using my not-that-effective-but-still-funny-to-play-with swype keyboard )
My findings with SWYPE are :
1. when you set your keyboard to SWYPE and do FACTORY reset, you might get problem in the "re_registration" your Nook. For some reason, the factory reset will not erase everything and the device is looking for SWYPE keyboard - which is obviously not there. So you won't have any keyboard to type onto !!! Having not a backup might get you in serious trouble !!!
2. As mentioned over here, the word prediction/suggestion is not visible so really, there is the small nuisance when you have to correct few words. keep an eye on it, when writing.
3. You might find a little bit frustrating the highlighting of a pressed button. Well, OK ... the truth is, that it's TOTALLY ANNOYING !!! Have a look on my video on youtube so you know, what I'm talking about :
youtube.com/watch?v=OYKjvqhxJmU&context=C3503defADOEgsToPDskIus5a7mP57B922B9wWU5cP
But, this can be fixed !!!
youtube.com/watch?v=S3vwQSvjUYM&context=C34142eeADOEgsToPDskJDd6sKkvt8EqkgO74yVfe7
Big THANK YOU goes to "djdarkknight96". His solution is to make the "highlighting" transparent, so it doesn't bother you any more. There was an attempt to make the trace line transparent as well, but without success (FC). Please, have a look at his thread for more info.
P.S. : With the youtube links -> as a new member outside links are not allowed for me yet -> so please add "www"
zholy said:
My findings with SWYPE are :
1. when you set your keyboard to SWYPE and do FACTORY reset, you might get problem in the "re_registration" your Nook. For some reason, the factory reset will not erase everything and the device is looking for SWYPE keyboard - which is obviously not there. So you won't have any keyboard to type onto !!! Having not a backup might get you in serious trouble !!!
Click to expand...
Click to collapse
My findings with this are that the swype keyboard is actually still there, so you need to use adb to delete the apk file and, if you replaced the original, find that one and use adb to add it.
Un-Bricking by Unlocking & Flashing CWM+CM7 (was: Accidentally deleted MediaProvider)
Hi!
When removing Bloatware with Titanium Backup a while ago, I accidentally missed a click (never used a touch screen...) and uninstalled MediaProvider, which I have not been able to recover since.
I tried putting the files back from a friend's HTC, which didn't work; after that I was told even the packages differ between manufacturers, so I tried getting them from a stock Bell Atrix .zip posted on these very forums, which didn't help either. Neither #android-root nor AndroidForums were able to help, thus I ask here: Can anyone tell me how to either make my system accept Bell's files, or where I can find a "vanilla" Motorola build?
(Problem is, the phone didn't come from a phone company, a friend of mine got it pre-release from his uncle who is with Motorola, so it may even be different from what hit the market later on...)
I guess the following information will help, it's a Titanium Backup info file for another componend I backupped shortly after:
#Titanium Backup
#Sat Feb 25 03:28:43 MEZ 2012
app_gui_icon=[...]
sys_ro.build.date.utc=1302536066
app_version_code=8
sys_ro.product.model=MB860
has_prefsdata_jpu=0
sys_ro.serialno=<xxx>
sys_ro.build.description=olympus-user 2.2.2 OLYEM_U4_0.44.0 578673 ota-rel-keys,release-keys
has_prefsdata=0
app_gui_label=com.android.providers.applications 2.2.2
sys_ro.build.version.release=2.2.2
app_apk_md5=1989ff2476ee73ad445760b9bef5f44e
has_dbdata=0
app_apk_codec=GZIP
app_is_forward_locked=0
app_is_system=1
app_label=com.android.providers.applications
app_version_name=2.2.2
generation=1
app_apk_location=internal
(Most of this is unnecessary, I guess, but I can't really be sure what you might need to judge what I would have to to...)
I would be very grateful for any help, it is extremely limiting not to be able to use any media capabilities.
So, thanks in advance,
David
maybe flash a new rom if your contacts are all backed up?
Hm, well, that would really be the last resort :\ In addition to losing all my data, I fear the risk of bricking it completely. Can't really be that I'd have to flash it just because two files are missing...?
Edit: I neglected to say that the files in question are MediaProvider.apk and MediaProvider.odex. I do only need to copy these to /system/app, right?
Intelensprotient said:
Hm, well, that would really be the last resort :\ In addition to losing all my data, I fear the risk of bricking it completely. Can't really be that I'd have to flash it just because two files are missing...?
Edit: I neglected to say that the files in question are MediaProvider.apk and MediaProvider.odex. I do only need to copy these to /system/app, right?
Click to expand...
Click to collapse
Yes, but you have to set the permissions same the other files in .system/app folder.
I have attached the missing files to this post. My gingerbread version is 2.3.4.
Good Luck!
Huh. Setting right permissions for the files from Bell had no effect; installing yours soft bricks it in an interesting way: Even with Early USB Enumeration, all I see is
# adb devices
List of devices attached
???????????? no permissions
Even with root. The LED flashes red, and after a minute it reboots. I had expected things not to work out, resulting in the deletion of your files, but that I screwed up _that_ bad after it didn't even seem to notice the right (?) files when they were there is kinda surprising.
The standard workarounds (adb kill/start server, MODE=0666 to udev or being root) change nothing about this. Time for hard reset?
Intelensprotient said:
Huh. Setting right permissions for the files from Bell had no effect; installing yours soft bricks it in an interesting way: Even with Early USB Enumeration, all I see is
# adb devices
List of devices attached
???????????? no permissions
Even with root. The LED flashes red, and after a minute it reboots. I had expected things not to work out, resulting in the deletion of your files, but that I screwed up _that_ bad after it didn't even seem to notice the right (?) files when they were there is kinda surprising.
The standard workarounds (adb kill/start server, MODE=0666 to udev or being root) change nothing about this. Time for hard reset?
Click to expand...
Click to collapse
I would hard reset too at this stage. I'm sorry it didn't work out.
Now, that's interesting. Factory reset didn't change anything.
Sorry for reply to self, but I was less than clear, so - help?
My next step would be to try to unlock the bootloader, then flash CWM and see if anything can be fixed that way; then, I would try flashing CM7 (or, more specifically, the Neutrino GT ROM) by CWM; then, I would try flashing it without. Is that a safe progression of attempts? Or have I possibly broken anything that would hard-brick it by any of these methods? And can you recommend any finer increments what I could do before / between / after those mentioned? I still have the option to apply an update in Recovery - is it possible, for instance, to put a .zip onto my SD that has 0 Byte MediaProvider files in it?
(I have thought about installing Neutrino for a while, and this seems to be a good time to flash it, as my data is cleared now anyways. To my understanding, this should not be any more dangerous than just re-flashing the Froyo that was there before, right?)
As an additional fact, ADB now doesn't detect any devices any more, even with Early USB. This could be because USB Debug is not a factory standard setting, though, as I reset it to factory defaults.
Also, the startup Moto screen behaves differently: It doesn't go to the point where the logo disappears in a flash, the background light switches off before that. As far as I can tell, the display still shows the animation, though, but it is not lit. Furthermore, the reboot seems to happen immediately after the animation has ended, and not 1-2 minutes later, like it was before the reset.
I would be grateful if anyone could explain what happened. To my understanding, a factory reset should clear /system, and the error started when I put some non-compatible .apks there, so I thought this would fix things. Is it possible something broke on the hardware side, when (for instance) 2.2.2 called a function that has had its parameters changes in 2.3.4?
[If a moderator reads this - does this qualify as a general Android question? I have no experience with different devices, so I'd be glad if you could decide if this thread has to stay here or if it can go to a sub-forum with a wider audience - General Android Q&A, for instance.]
Bump...
Success Neutrino up and running!