Related
Anyone been able to apply a method for connecting a Galaxy tab to a ad hoc wifi network?
I've rooted my tab and poked around for the various fixes but can't get anything to work. I tried the compiled Froyo fix for this but it throws an error when I try to flash the fix using Rom Manager: "failed to verify whole-file signature".
Will this patch need to be resigned for the tab? I'll admit I'm new to the Android world and I'm hoping there's an easy fix for this.
i also want to know how to connect to an ad hoc network. Please help us.
I tether mine using wireless tether on my dinc you just need to enable access control and it will work.
By wireless tether, you mean Bluetooth? What do you mean by "enable access control"?
I have a rooted droid incredible I use "wireless tether" from the market. When you open the app hit menu then access control and just hit enable.
Nope...had me going for a minute though. Funny though,my girlfriends DX can see my ad-hoc tether from my d1?
I would also like to know...
ad-hoc on Galaxy Tab
Having the Galaxy Tab recognize/connect to ad-hoc wireless network is critical for me. Anyone have the answer??
Verizon galaxy tab ad hoc working
After rooting my tab I found this link on the forums: forum.xda-developers.com/showpost.php?p=7711198&postcount=6
Grabbing the wpa_supicant file from there all I did was use root explorer, which can be found in the android market, to back up my existing wpa_supplicant found in the
/system/bin/ directory at the bottom. Then I copied the newly downloaded file
(after extracting it) and placed it in the above mentioned directory. You will have to press
The r/w button at the top of root explorer in order to enable read write permissions in
/system/bin . I tested this with the wireless tether on my droid original and it works
as advertised.
I am not the one who created this solution nor am I the one who compiled wpa_supplicant
All credit goes to the original author of the solution. I merely wish to convey to you that this solution worked for me. I hope this helps.
*It is important to note th at this was done using a rooted verizon galaxy tab. You will
Have to be at least rooted for this solution to have any chance of working. I used z4root
in order to root my device which can be found by searching these forums or the android market and again I dont claim any credit or participation in the creation of that app.
Posted from my Samxung Galaxy Tab
Esxna said:
After rooting my tab I found this link on the forums: forum.xda-developers.com/showpost.php?p=7711198&postcount=6
Grabbing the wpa_supicant file from there all I did was use root explorer, which can be found in the android market, to back up my existing wpa_supplicant found in the
/system/bin/ directory at the bottom. Then I copied the newly downloaded file
(after extracting it) and placed it in the above mentioned directory. You will have to press
The r/w button at the top of root explorer in order to enable read write permissions in
/system/bin . I tested this with the wireless tether on my droid original and it works
as advertised.
I am not the one who created this solution nor am I the one who compiled wpa_supplicant
All credit goes to the original author of the solution. I merely wish to convey to you that this solution worked for me. I hope this helps.
*It is important to note th at this was done using a rooted verizon galaxy tab. You will
Have to be at least rooted for this solution to have any chance of working. I used z4root
in order to root my device which can be found by searching these forums or the android market and again I dont claim any credit or participation in the creation of that app.
Posted from my Samxung Galaxy Tab
Click to expand...
Click to collapse
I wish someone would do a step by step for dummies on how to do this. Thanks!
Esxna said:
After rooting my tab I found this link on the forums: forum.xda-developers.com/showpost.php?p=7711198&postcount=6
Grabbing the wpa_supicant file from there all I did was use root explorer, which can be found in the android market, to back up my existing wpa_supplicant found in the
/system/bin/ directory at the bottom. Then I copied the newly downloaded file
(after extracting it) and placed it in the above mentioned directory. You will have to press
The r/w button at the top of root explorer in order to enable read write permissions in
/system/bin . I tested this with the wireless tether on my droid original and it works
as advertised.
I am not the one who created this solution nor am I the one who compiled wpa_supplicant
All credit goes to the original author of the solution. I merely wish to convey to you that this solution worked for me. I hope this helps.
*It is important to note th at this was done using a rooted verizon galaxy tab. You will
Have to be at least rooted for this solution to have any chance of working. I used z4root
in order to root my device which can be found by searching these forums or the android market and again I dont claim any credit or participation in the creation of that app.
Posted from my Samxung Galaxy Tab
Click to expand...
Click to collapse
awesome. anyone else get this to work this one with incredible? it should be the same i would guess.
thx for this, Esxna
its working for me.
bye
mach330 said:
awesome. anyone else get this to work this one with incredible? it should be the same i would guess.
Click to expand...
Click to collapse
Yea, you're changing a file on the tab, so as long as you can tether with your inc, you'll be good. This definitely works and is incredibly simple, I'm tethered right now off my droid x.
Sent from my Galaxy Tab using Tapatalk
No luck on rooted tmobile galaxy tab
Maybe this is a total noob problem but, I rooted my tab, followed the instructions and nada. The file says it copied but the date of the file did not change. I refreshed and checked again. I tried to see if the tab would now see my wifi tether from my droid1. No go. My laptop and ipod see the droid wifi but not the galaxy. Any ideas?
joecpu said:
Maybe this is a total noob problem but, I rooted my tab, followed the instructions and nada. The file says it copied but the date of the file did not change. I refreshed and checked again.
Click to expand...
Click to collapse
i had this issue with RootExplorer 2.12.2. After updating to 2.12.4 it now works.
joecpu said:
Maybe this is a total noob problem but, I rooted my tab, followed the instructions and nada. The file says it copied but the date of the file did not change. I refreshed and checked again. I tried to see if the tab would now see my wifi tether from my droid1. No go. My laptop and ipod see the droid wifi but not the galaxy. Any ideas?
Click to expand...
Click to collapse
Assuming u backed up the original file first to ur sdcard, I actually deleted the one in
/system/bin then copied the modified file there afterward in order to make sure it was replaced and to avoid overwrite issues like that. Give that a try?
And dont forget to mount the folder in "r/w"
Sent from my GT-P1000 using XDA App
This worked great for me. Had to use adb shell and some command line tricks but got the new wpa_supplicant copied and can now use the wifi tether on my phone for internet. Good times.
Thanks!
Esxna said:
After rooting my tab I found this link on the forums: forum.xda-developers.com/showpost.php?p=7711198&postcount=6
Grabbing the wpa_supicant file from there all I did was use root explorer, which can be found in the android market, to back up my existing wpa_supplicant found in the
/system/bin/ directory at the bottom. Then I copied the newly downloaded file
(after extracting it) and placed it in the above mentioned directory. You will have to press
The r/w button at the top of root explorer in order to enable read write permissions in
/system/bin . I tested this with the wireless tether on my droid original and it works
as advertised.
I am not the one who created this solution nor am I the one who compiled wpa_supplicant
All credit goes to the original author of the solution. I merely wish to convey to you that this solution worked for me. I hope this helps.
*It is important to note th at this was done using a rooted verizon galaxy tab. You will
Have to be at least rooted for this solution to have any chance of working. I used z4root
in order to root my device which can be found by searching these forums or the android market and again I dont claim any credit or participation in the creation of that app.
Posted from my Samxung Galaxy Tab
Click to expand...
Click to collapse
Thanks, this worked great.
kkrammer said:
i had this issue with RootExplorer 2.12.2. After updating to 2.12.4 it now works.
Click to expand...
Click to collapse
Right on the money! As soon as I updated Root Explorer, bada bing Baby!
Thanks for the help!
**NOTE FOR VEGAN TAB USERS** Steps 1-5 are no longer necessary for you, as the build.prop file in your /system directory has a working market fingerprint out of the box. Just apply the standard Market Fix (steps 6-8) and you are good to go.
I've seen several people complaining that the "full market" we had on G Tablet after the established market fixes wasn't quite full. Well, I've solved that problem, through a mixture of reading what others have done with other devices and experimentation. I will not promise that this gives you *everything*, but I do believe it gives you apps that otherwise required the release-keys status. Some of the apps you get may of course not work. But several applications I looked for before (TV.com for example, with streaming CBS video content) were not available with the previous market fix, and are now available with this fix. In fact, TV.com even works, except for a very minor video glitch in the upper left corner of the screen, and it's a cool app to get some quick streaming video content going on your G Tablet.
**NOTE** I take no responsibility for you screwing up your G Tablet. Please backup your system in Clockwork Recovery before doing any of this!
**EDIT** Removed unneccessary steps after feedback in this thread. Process is now very simple. Edited step 1 to clarify you need paid version of Root Explorer.
Here's how to do it:
0) Backup in Clockwork Mod. Please. I don't want you mad at me if this messes up your ROM.
1) Get the paid version of Root Explorer installed on your G Tablet. Apparently the free version lacks a text editor. If you only have the free version, the text editing step will need to be done in a separate program, or you will need to copy build.prop to your desktop, edit it there, and copy it back. Or use adb to push an edited build.prop to your tablet. Just buy Root Explorer though, it makes this very easy.
2) Browse in Root Explorer to /system. Then click on Mount R/W.
3) Long click on build.prop and click on Open In Text Editor.
4) Scroll down to the line ro.build.fingerprint=....
You are going to replace that with the following text:
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys
5) Now you are going to click on Save and Exit. And then remount the /system directory as R/O.
6) Now you are going to re-do the original Market Fix. I used the simple version illustrated here: http://www.youtube.com/watch?v=7l-nySibzeA&feature=related First, make sure Market is running, and browse around in it for a few seconds. If you don't do this, there may be no cache to clear and for some reason the market fix may not work. Then, go to Settings->Applications->Manage Applications->Running and scroll down to Market. Then hit Clear Cache, followed by Force Stop **DO NOT CLEAR DATA FOR MARKET, JUST CACHE**. Then go back, scroll down to Google Services Framework, hit Clear Data, then Force Stop.
7) Now try starting Market again and you get the famous Market Error. Now shut down the G Tablet, then turned it back on. Wait for Wifi to connect to your network before doing anything! I forgot to do that on the first try, so I rebooted again, waited for wifi to connect this time.
8) Now restart Market again. It seems to have sourced the fingerprint from build.prop somewhere in steps 6-7. Searches for previously missing apps now show up. Voila! A truly full market!
And steps 6 and 7 can almost certainly be replaced by the equivalent steps using Titanium Backup that I know a lot of people have been using, particularly with TNT Lite. I am running ZPad 2.2 here, so YMMV with TNT Lite. Please keep me informed if this works/doesn't work for you if you try it!
Credit goes to: Paul at Modaco for hacking on the Advent Vega and making the Market work fully on that device and for coming up with a working build.prop for the Advent Vega, Roebeet for inspiring me to look at the Vega ROM stuff with his current work on the VEGAn ROM, Rothnic for his excellent work on the ZPad ROM that I'm currently using. Basically, I'm just hacking and slashing here, this wasn't any sort of rocket science.
Paul from Modaco is awesome -- and you are as well, for making this post!
Any apps in particular that you found after this, that were missing before? I might want to try this on my device. Thanks again!
FWIW my Nexus One running a CM 6.0 nightly from 2 days ago has
ro.build.fingerprint=google/passion/passion/mahimahi:2.2.1/FRG83/60505:user/release-keys
Note the more up-level version (2.2.1) and build (FRG83). I haven't tried this on my GTab yet but I will as soon as I can get it up and running.
roebeet said:
Paul from Modaco is awesome -- and you are as well, for making this post!
Any apps in particular that you found after this, that were missing before? I might want to try this on my device. Thanks again!
Click to expand...
Click to collapse
The only specific things I can tell you off the top of my head are TV.com which I know wasn't there because I searched for it a few hours ago. Also, I tried searching Market for Handcent before and found 14 or 15 results, and after this process I was able to retrieve 24 results.
There were a bunch of random apps I saw in the Top Apps list that I don't remember seeing earlier today. So that was enough to convince me that most of the missing 10-20% of apps are there now.
And thanks for the compliment, especially coming from the guy who made the G Tablet useful!
short/y said:
FWIW my Nexus One running a CM 6.0 nightly from 2 days ago has
ro.build.fingerprint=google/passion/passion/mahimahi:2.2.1/FRG83/60505:user/release-keys
Note the more up-level version (2.2.1) and build (FRG83). I haven't tried this on my GTab yet but I will as soon as I can get it up and running.
Click to expand...
Click to collapse
I'm sure that will work too, though the FRF91 build string seems to match the existing data in the ZPad ROM at least. I'm guessing the two signatures will produce essentially identical Market results.
rcgabriel said:
I'm sure that will work too, though the FRF91 build string seems to match the existing data in the ZPad ROM at least. I'm guessing the two signatures will produce essentially identical Market results.
Click to expand...
Click to collapse
Yeah. I may be somewhat overoptimistic going with FRG83. The build and version numbers identify the version of the system code so apps may read them and make some assumptions as to certain API characteristics. We're probably closer to FRF91 than FRG83 on TnT Lite.
This one worked ok for me
ro.build.fingerprint=samsung/SGH-T849/SGH-T849/SGH-T849:2.2/FROYO/UVJJB:user/release-keys
ewitte said:
This one worked ok for me
ro.build.fingerprint=samsung/SGH-T849/SGH-T849/SGH-T849:2.2/FROYO/UVJJB:user/release-keys
Click to expand...
Click to collapse
Is that from the Samsung Tablet? That may be closer to what we're really running.
short/y said:
Is that from the Samsung Tablet? That may be closer to what we're really running.
Click to expand...
Click to collapse
Yes this is Galaxy Tab. Probably better a Tegra tab once a full market one comes out.
I did the following:
1) Edited build.prop as described in step 4, rebooted and searched for tv.com - no results
2) I preformed the edits in step 4a, rebooted and searched for tv.com - no results
3) I stopped Market & Google Services Framework & wiped Google Services Framework, rebooted after getting Market Error, waited for wifi and opened Market to search for tv.com - no results.
I can't say if it works. I haven't had trouble finding apps, but I can't find tv.com before or after the steps above. Perhaps, I missed something.
Wait!!!! It does work. I tried again after posting and it's there! Thanks!
Is it possible to post the TV.com app? I don't want to do the mod but would love that app!
Great post man worked like a charm, I can get my slingbox app from the market now.
Edit: dammit I can't get the downloaded sling client to launch even after trying it many times which usually worked.
I'm going to give it a shot but being a newbie I'm not clear on this step:
5) Now you are going to click on Save and Exit. And then remount the /system directory as R/O
Will "remount as r/o" be an option to select at this point? If not, can you provide more detail.
The rest of the mod is easy enough to follow.
Thanks.
jdnyc said:
I'm going to give it a shot but being a newbie I'm not clear on this step:
5) Now you are going to click on Save and Exit. And then remount the /system directory as R/O
Will "remount as r/o" be an option to select at this point? If not, can you provide more detail.
The rest of the mod is easy enough to follow.
Thanks.
Click to expand...
Click to collapse
No worries its just a button on root explorer, download it and you will see it fairly quick.
NM..........
Fixed
Thanks works great
Can't get this to work. When I toto building.prop there s no option to open it in text editor. Only toopen as text. But then there is no way to edge the sentence.
ewitte said:
This one worked ok for me
ro.build.fingerprint=samsung/SGH-T849/SGH-T849/SGH-T849:2.2/FROYO/UVJJB:user/release-keys
Click to expand...
Click to collapse
Replaced this line only, did the Market fix via Settings and it worked like a charm. And Swype continues to work as well.
-=Sent from my ViewSonic G Tablet using Tapatalk=-
Worked perfectly thanks! Steps 4a and 6 are not necessary as you precicted
Hi! I found a way to make any Sense 3.6 skins work on Incredible S (4.0.4) and decided to share this with you guys
As you might know, most of the 3.6 skins on the Play Store and xda work only on 4.0.3 and NOT on stock and unrooted Incredible S. And the best part is that the solution I'll give you doesn't require root access or any superior developer skills I don't know if this is obvious for most of you but I hope someone will find some use for this tutorial.
All you need is:
-some existing skin that you can download from the Play Store or this Forum (just search for sense 3.6 skins)
-Virtuous Ten Studio ([search Google, can't post links sorry )
-com.htc.resources.apk from your phone (system/framework) and place it anywhere on your computer
1. After installing and opening the VTS you just have to go to File>Open Settings>Frameworks and add the framework (com.htc.resources.apk). Name it for example "skin". Then Import and OK.
2. Then on VTS selecet File>New Project>Apk-Project and choose a name for project and solution and location where you wanna save it. Then from the left select Import and find the apk of the skin you have downloaded. After that select Apk-Tool and select the framework (the one you named "skin" in step 1.) Then go to M10-Engine and check the box (probably not necessary). Select OK and it starts to decompile the apk.
3. Double click the AndroidManifest.xml in the Solution Explorer. Now the most important part: change the android:versionCode=xyz to 282066944 so that it is "android:versionCode=282066944". Now click the little x on the androidmanifest.xml tab and save changes.
4. Right click your project and choose Reload Project just to make sure your changes are applied.
5. Right click your project and choose Build apk. It automatically recompiles and signs your apk (easy huh?).
6. Click Binary in the Home tab and select your project. It opens up the folder where your new apk is located. Take that apk and move it to your phone and install. The skin should now show up on the skin chooser (Settings/Personalize/Skin). THAT'S IT!
There you go, hope this solution works for you too and you find this tutorial helpful And it's really easy guys, so don't worry if your not a developer (I'm not in any way). Now enjoy your new, fabulous skins on your Incredible S!! :victory:
That's kind of the hard way to do this and you can run into signature issues depending on how the developer signed the file.. Yes the issue with skins from one phone to another with the same version of sense is the Android code listed in the manifest..this is also the reason why we can't post a update to a skin, but instead have to post any new as a whole new app... Most of us with skins in the market try to keep multiple versions of the apps uploaded in play to accommodate all phones..but is a lot of work.. Your phone and the thunderbolt share and have shared before the ICS update the same version code..I'm currently working on a new collection of skins for play that will be including versions for your phone..so within the next few days, there will be options for you without messing with the manifest and risking messing something up that may not know about
Tikruli said:
Hi! I found a way to make any Sense 3.6 skins work on Incredible S (4.0.4) and decided to share this with you guys
As you might know, most of the 3.6 skins on the Play Store and xda work only on 4.0.3 and NOT on stock and unrooted Incredible S. And the best part is that the solution I'll give you doesn't require root access or any superior developer skills I don't know if this is obvious for most of you but I hope someone will find some use for this tutorial.
All you need is:
-some existing skin that you can download from the Play Store or this Forum (just search for sense 3.6 skins)
-Virtuous Ten Studio ([search Google, can't post links sorry )
-com.htc.resources.apk from your phone (system/framework) and place it anywhere on your computer
1. After installing and opening the VTS you just have to go to File>Open Settings>Frameworks and add the framework (com.htc.resources.apk). Name it for example "skin". Then Import and OK.
2. Then on VTS selecet File>New Project>Apk-Project and choose a name for project and solution and location where you wanna save it. Then from the left select Import and find the apk of the skin you have downloaded. After that select Apk-Tool and select the framework (the one you named "skin" in step 1.) Then go to M10-Engine and check the box (probably not necessary). Select OK and it starts to decompile the apk.
3. Double click the AndroidManifest.xml in the Solution Explorer. Now the most important part: change the android:versionCode=xyz to 282066944 so that it is "android:versionCode=282066944". Now click the little x on the androidmanifest.xml tab and save changes.
4. Right click your project and choose Reload Project just to make sure your changes are applied.
5. Right click your project and choose Build apk. It automatically recompiles and signs your apk (easy huh?).
6. Click Binary in the Home tab and select your project. It opens up the folder where your new apk is located. Take that apk and move it to your phone and install. The skin should now show up on the skin chooser (Settings/Personalize/Skin). THAT'S IT!
There you go, hope this solution works for you too and you find this tutorial helpful And it's really easy guys, so don't worry if your not a developer (I'm not in any way). Now enjoy your new, fabulous skins on your Incredible S!! :victory:
Click to expand...
Click to collapse
actually, works just perfect! thanks!
great !
Its good to see it.
But I'm not expert like you people.If possible then please provide a video tutorial.
Another thing is that default themes which I've found on google doesn't load in VTS.Request help in this topic.
In order to access system/framework you need root.
Flawed.
Sent from my Nexus 5
LamboBull said:
In order to access system/framework you need root.
Flawed.
Sent from my Nexus 5
Click to expand...
Click to collapse
You do know that you can browse and copy files from /System without root right?
LiebenGeist said:
You do know that you can browse and copy files from /System without root right?
Click to expand...
Click to collapse
Can you show me an explorer that will allow you to copy files from /system without root??
Because last time I checked, every explorer that require r/w access to /system and whatnot required root
072665995 said:
Can you show me an explorer that will allow you to copy files from /system without root??
Because last time I checked, every explorer that require r/w access to /system and whatnot required root
Click to expand...
Click to collapse
FX File Explorer non-root. I did not say WRITE, I said READ/COPY from. Also, you can be less jerky about it or have actually read the post.
LiebenGeist said:
FX File Explorer non-root. I did not say WRITE, I said READ/COPY from. Also, you can be less jerky about it or have actually read the post.
Click to expand...
Click to collapse
You could also be less jerky in the fact that:
1. You could have introduced said explorer because I have personally never heard of it and have used ES File Explorer or Root Explorer (which in my opinion is just much cleaner in everything)
2. Are you perfect? Because last time I checked, no 1 person on XDA has had a clean perfect record of not accidentally saying something false and that goes for real-life too.
072665995 said:
You could also be less jerky in the fact that:
1. You could have introduced said explorer because I have personally never heard of it and have used ES File Explorer or Root Explorer (which in my opinion is just much cleaner in everything)
2. Are you perfect? Because last time I checked, no 1 person on XDA has had a clean perfect record of not accidentally saying something false and that goes for real-life too.
Click to expand...
Click to collapse
1) I'm not being jerky, you rolled your eyes at my statement which was rude. You could've asked "is that possible?"
2) It doesn't matter if it's a file explorer, browser, whatever, as long as you're not writing to non-user space you don't need root. ANY app that can read the sd card can read /system
3) Who said anything about being perfect? I made a very clear statement that was misconstrued. I didn't persecute you over it.
4) This is XDA Developers, not XDA Debators. If you want to argue, that's what PM is for.
Hi there anyone!
This is my first post ever so I'm sorry if it's not the right place, but I really need help with this thing.
I used to have XPosed Framework running on my old Doogee DG550, and it was real fun. Now I got a Doogee F5 running Android 5.1 and I decided to put XPosed it too.
However, I'm finding it extremely difficult, as I got "stuck" while trying to follow the guide in this post.
I've installed the XPosed Installer just fine, I can see it in my apps, but of course it still says I need to install the Framework. So I downloaded the version mentioned in that post, which is xposed-v85-sdk22-arm64.zip and then the Official TWRP App I found on the PlayStore.
Then I simply tried to open the app and find the file while searching through my folders, but the app couldn't recognize it. So I tried extracting it in a folder and then pointing out the entire folder to the app, and this failed too. I tried opening every single folder within the .zip file, but yet no usable file was found.
Now I'm kinda stuck: I don't really know what I'm doing wrong, and as you might have already figured out I'm a real noob at this.
If any of you people can help, that would be great!
Dear forum readers, geeks & developers,
I have been trying to seek for that one thread that could solve my issue which the title said it all. I have followed many guides & use multiple different tools, both on device & PC but to no success. Most of the threads would just say; "recompile after finished editing whatever you want". But that's definitely not the proper way. Some guides there were hints of keeping/replacing the Manifest.xml & META-INF folder, yes I kept it somewhere else & replace it just before I want to recompile, no it didn't work too.
One of the guides said decompile the APK, copy the *_src folder somewhere else & recompile it back right away, edit the copied _src folder & edit whatever you want. After editing, open/view the recompiled APK as zip & drag/drop the files you edited, yes it was recompiled successfully but when I apply it to the device it FC right away & were unable to boot up although I wiped Dalvik and Art Cache. One more example was, instead of replacing the edited files, this guide replaced the META-INF & Manifest.xml. The problem was I can't even get it to recompile successfully.
Something could be really wrong with me, my PC or my device, if only some generous kind soul would spare some knowledge to help this poor soul I would appreciate it very much, thank you for whoever spared the time for reading this, I hope my noobness made your day.
Cheers all,
- Merry Xmas &
A Happy New Year
DaRdamnDoG said:
Dear forum readers, geeks & developers,
I have been trying to seek for that one thread that could solve my issue which the title said it all. I have followed many guides & use multiple different tools, both on device & PC but to no success. Most of the threads would just say; "recompile after finished editing whatever you want". But that's definitely not the proper way. Some guides there were hints of keeping/replacing the Manifest.xml & META-INF folder, yes I kept it somewhere else & replace it just before I want to recompile, no it didn't work too.
One of the guides said decompile the APK, copy the *_src folder somewhere else & recompile it back right away, edit the copied _src folder & edit whatever you want. After editing, open/view the recompiled APK as zip & drag/drop the files you edited, yes it was recompiled successfully but when I apply it to the device it FC right away & were unable to boot up although I wiped Dalvik and Art Cache. One more example was, instead of replacing the edited files, this guide replaced the META-INF & Manifest.xml. The problem was I can't even get it to recompile successfully.
Something could be really wrong with me, my PC or my device, if only some generous kind soul would spare some knowledge to help this poor soul I would appreciate it very much, thank you for whoever spared the time for reading this, I hope my noobness made your day.
Cheers all,
- Merry Xmas &
A Happy New Year
Click to expand...
Click to collapse
Are you still having issues with this? If so can I suggest using my decompiling tool Tickle My Android? The link's in my signature.
Yes, I'm advertising my work but I also think it could help so..
Ticklefish said:
Are you still having issues with this? If so can I suggest using my decompiling tool Tickle My Android? The link's in my signature.
Yes, I'm advertising my work but I also think it could help so..
Click to expand...
Click to collapse
Well, you're back in business! I was letting you finished off your "Xmas & new year's off" with your 3 sons. I was trying to venture into Linux, hoping it would be more convenient to get tools & because it's free! However, I was wrong. 2 weeks later I am still installing/testing out different distributions. I have kinda abandoned my device most of the time now, unless you fix Toad & deodex my rom i wont be motivated to do anything
P/S: Im not even bothered of you advertising. Google is the main advertiser here, the main mastermind of Android.
The guides & tutorials needs a spring clean too.
DaRdamnDoG said:
Well, you're back in business! I was letting you finished off your "Xmas & new year's off" with your 3 sons. I was trying to venture into Linux, hoping it would be more convenient to get tools & because it's free! However, I was wrong. 2 weeks later I am still installing/testing out different distributions. I have kinda abandoned my device most of the time now, unless you fix Toad & deodex my rom i wont be motivated to do anything
P/S: Im not even bothered of you advertising. Google is the main advertiser here, the main mastermind of Android.
The guides & tutorials needs a spring clean too.
Click to expand...
Click to collapse
Things are still really busy at work so I'm not back to normal right now. But I'm trying to get as much done here as I can.
I don't know enough about Linux really - I just don't have the time or a free PC to play with so I can work it out. Which is a shame as it'd be great for modifying Android.
I did reply to your post on the TOAD thread though. You said about moving apps away and I asked for more clarity about what you were moving and how.