modify build.prop - Transformer TF300T Q&A, Help & Troubleshooting

Hi,
would it work to modify CM10 build.prop in the archive and just change the model from TF300T to TF300TG and it would make it flashable on the TF300TG? I now it would be without 3G, but just theoretical question

push ? Cannot be the case none of you has an idea about it...

Related

[Q] help making .zip to flash wpa_supplicant

Good evening dev community, I'm trying to create a flashable .zip that will replace the wpa_supplicant file with one that can connect to Ad-hoc networks. Replacing the file is actually really easy to do but I want to make a flashable .zip for others who don't want to mess with root explorer or ADB.
I have taken a .zip that works for the CWM 2.x for my phone but that won't flash on the xoom because CWM 3.x doesn't support the amend language so I converted it using amend2edify by nubecoder and I was so excited when it seemed to work but it will look like it's flashing and not actually do anything.
I was wondering it someone who knows more than me might want to lend a hand.
Please take a look and see if you can see anything wrong with my updater-script
Here is what I have so far. (see attachment)
Disclaimer: I got bored with not getting anywhere so I changed some of the display text so it's goofy so try to ignore that.
You shouldn't need to be afraid to flash it, it's harmless... that's the problem.
But as always you do so at your own risk.
Bump?
Sent from my Xoom using Tapatalk
Take a look at this thread. There is a link to a generic update script that works on the xoom. Just put your file in the right folder / subfolder and you should be good to go.
http://forum.xda-developers.com/showthread.php?t=1041205
I'll take a look at it. Thanks.
Sent from my Xoom using Tapatalk
Thanks for the help. It's exactly what I needed. I put a thank you in my new thread on this http://forum.xda-developers.com/showthread.php?t=1106130.
Do you know where I can get the wpa_supplicant file that will work with my Toshiba Thrive Tablet running Android Stock ROM 3.1? Thanks!

[Q] [HELP] Need TW 3.2 OTA dlpkgfile

I'm still not able to get OTA notification for my TW sku asus transformer
Anybody here can upload and share it please ?
and is it posible to copy it to microsd and rename it to EP101_SDUPDATE.zip will it update through stock recovery method ?
Thanks

Replacing framework-res.apk on Stock Android 4.1.1

Hi all -
I'm using a GSM Galaxy Nexus with stock Android 4.1.1, and I'm trying to reduce the dim level, which kills my eyes at night. This is determined by a value "config_screenBrightnessDim" found in framework-res.apk. (In the source tree, it is found at frameworks/base/core/res/res/values/config.xml.)
I tried using apktool to decompile/recompile the stock framework-res.apk, but it doesn't seem to work with Jelly Jean. So, I instead attempted to replace the stock framework-res.apk with one I compiled from AOSP. When I do this, I get stuck at the boot animation. I assume this has something to do with the fact that my AOSP framework-res.apk is signed with a different certificate than the stock one. However, I also noticed that my AOSP file was ~10MB, while the stock one is only ~9.8MB, so there could be some other issue.
Any help with this would be greatly appreciated. Thanks!
(PS: Another modification I made was successful: I replaced the stock audio.primary.tuna.so with one I built from AOSP with a higher maximum volume. So, I think I am at least replacing the files correctly!)
Don't sign the framework file. Leave it unsigned and just move the cert from the stock framework. Also I would be interested in your audio boost file if you wouldn't mind sharing.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks for the advice –*I'll try it out. I'll "unsign" my framework-res.apk by removing all the META-INF files in it. If it doesn't work, do you know a way to find the logs from the failed boot? Also, is there anything I should do (wipe cache, etc) after copying over the new framework-res.apk?
I've attached a zip containing three versions of the library audio.primary.tuna.so, found at /system/lib/hw/audio.primary.tuna.so: orig, loud, and aosp. "orig" was pulled from my phone with stock 4.1.1, "aosp" was built from aosp (the command you need is "make audio.primary.tuna"), and "loud" was made from aosp with the "device/samsung/tuna/audio/audio_hw.c" file altered to change the volume. Enjoy!
Geo411m said:
Don't sign the framework file. Leave it unsigned and just move the cert from the stock framework. Also I would be interested in your audio boost file if you wouldn't mind sharing.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
This worked! Thanks so much!
Great! Glad it worked for you. Also thanks for the Audio file.
How do you build just framework-res.apk from AOSP?
I've followed a tutorial and built the whole system, but I don't know where fraemwork-res.apk is built from in the source or how to only build it.
Edit:
figured out to build specific packages:
make (package name)
...omg
If you figure out how to use a framework-res.apk built from AOSP to replace one on the stock rom, let me know. I never did get that method to work.
michaelmotes said:
How do you build just framework-res.apk from AOSP?
I've followed a tutorial and built the whole system, but I don't know where fraemwork-res.apk is built from in the source or how to only build it.
Edit:
figured out to build specific packages:
make (package name)
...omg
Click to expand...
Click to collapse
There are some (most) things that you can modify in framework-res.apk and just copy over the old META-INF.
There are some things (like AndroidManifest.xml) that you can not modify and use the old META-INF.
The most radical solution is to resign your entire system with a new signature.
If the particular APK (not FW-R) does not use a sharedid, you might get away with just signing that.
(The above observations might be different on different versions Android.)

flashable zip to apk??

i am newbie so dont mind if i ask silly questions since i dont know much about this apk and flashable zips. i want to install sony xperia s keyboard on my tf300 , there is a flashable zip for that available , so my doubt is
is there any way that we can convert the flashable zip into apk so that we can install it directly as an app on side loading without rooting or bl unlocking etc stuff.??
[email protected] said:
i am newbie so dont mind if i ask silly questions since i dont know much about this apk and flashable zips. i want to install sony xperia s keyboard on my tf300 , there is a flashable zip for that available , so my doubt is
is there any way that we can convert the flashable zip into apk so that we can install it directly as an app on side loading without rooting or bl unlocking etc stuff.??
Click to expand...
Click to collapse
That's a good question. I'm not familiar with development, but I will make a guess that it is not possible - reason I say that is I found even with root, coping files to /system resulted in error, even after setting the mount as read-write. Flashing can put files in there without actually getting into the os so that might be why its not possible, but someone else feel free to clarify further.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
you should have the apk in the zip file. But when you put it in the system app folder by hand you also have to give the apk the needed rights. So its beter you choose the simple flash a zip way.

someone who can create a flashable zip?

someone could create a flashable .zip with the kernel, the modem, the libraries , and the build.prop ,
eh I been trying but it causes an error in the updater scrip I have no idea ,
if anyone has more knowledge, I provide the files and routes it only takes the updater script
the reason for this zip, easy to everyone else. to install roms of Any Other model
sorry for my bad English
The zip would need to be bumped before it could work. Once they get the bump site up and running you should be able to make a working flashable zip.
sent from the Bacon Pope's LG G3
@cwhitney24
I'm not sure but I thought out it was stock kernel. There was no reason for the zip file to be bumped. Did I misunderstand?

Categories

Resources