Hi all,
I installed the SuperHero V3 Mas in my G2 (magic 32b) and it run so good and faster than all of others roms that I have tried. The problem that is the wifi cant turn on (it's normal this rom is made for G1).
Someone can help me to solve this problem and make this rom able to all G2 users.
The trick is to get and push the working wlan.ko (I think its in the sperhero 3 thread already) now why don't you tell me the trick you did to make this the fastest so I can try it
try pulling the wlan.ko file from a magic rom and pushing it through adb to /system/lib/modules, and im guessing its the fastest because he might have the magic that has the 288mb ram instead of 192, so virtually identical to the hero.
thank you for your response, I will try this right now
Thas is not work
failed to copy 'wlan.ko' to '/system/lib/modules/wlan.ko': Read-only file system
I tried to change file access using chmod and I go this message:
failed to copy 'wlan.ko' to '/system/lib/modules/wlan.ko': Read-only file system
please help
Ps: adbd is already running as root
co2gaz said:
Thas is not work
failed to copy 'wlan.ko' to '/system/lib/modules/wlan.ko': Read-only file system
I tried to change file access using chmod and I go this message:
failed to copy 'wlan.ko' to '/system/lib/modules/wlan.ko': Read-only file system
please help
Ps: adbd is already running as root
Click to expand...
Click to collapse
Try "adb remount" to mount /system as writeable.
Thank you for this information.
I tried it. the copy work OK, but the wifi problem steel here
I should have been more clear because pulling the file from any Rom isn't how you go about it. It has to match the kernel you are on and often even be further modified to the build. I think I heard either the wlan from superhero2 or the one from an earlier jachero worked. I just forget what one. Give me some time ill upload it. I had fixed and re-released this build.
Edit: Wlan.ko attatched. Belongs in system/lib/modiules
I thank you so math for your help,
I putted the file in my phone and i restart it, but wifi steel not work
Hi, I tried with JCAHero and it's same, very great rom, run so good on my magic G2, but the wifi not work
co2gaz said:
I thank you so math for your help,
I putted the file in my phone and i restart it, but wifi steel not work
Click to expand...
Click to collapse
Use the one I posted in this thread. I edited the post above ya. It should work then.
Thank you, I putted the new wlan.ko on my phone. now it seems better but it not work, now when I want to start wifi it show wifi is turning on during 4 or 5 sec, after that it show unable to start wifi.
if it was some link to explain how I can modify wlan.ko, maybe I can do some things (I'm java developer and I think it's native kernel file)
Related
For those of you having trouble seeing protected apps, I modified our fingerprint in the build.prop. What this does is spoofs the market into thinking its seeing a Droid 2 (with Froyo) It worked for me, let me know if it does for you.
1. Put build.prop into your AndroidSDK\TOOLS folder
2. Connect via USB.
3. CD (Navigate) in CMD to your tools folder
Mount your /system (adb remount) works for me
Copy and paste this
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
To test if you need this before you push the build.prop fix, search the market for Us Bank. If only 2 or 3 show up, you are not getting the full market. After this fix, you should see 10 items listed when you search for Us Bank.
Hope this helps.
2.2 Market Fix Build.Prop -- WITH STAGEFRIGHT=TRUE
This can also be done via Root Explorer.
Edit: Here is a "clean" build.prop for those of you who do not want the stagefright fix (which breaks video playback) Sorry, I was not aware it did that. Thank you.
Non Stagefright Build.prop -- WITH STAGEFRIGHT=FALSE
For everyone flipping out about Birdmans tweet and you want the stock build.prop, here ya go
Stock Build.prop -- WITH NOTHING! STOCK!
You only need the stock one if you ever plan on doing a factory reset. But, you also cant do a factory reset if you have removed or renamed apps so I feel that should be mentioned. If you've done any modding and you are planning on upgrading, your best bet is to always use the SBF anyway. I dont think birdman realizes the panic he sets in with one little tweet. Factory resets suck anyway. But then again... "you decide..."
Thanks to Jcase for giving me the original idea way back when. I just basically applied his Eris Market Fix to work with our phones.
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Found a fix
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Zaphod-Beeblebrox said:
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Click to expand...
Click to collapse
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
elkniwcire said:
i must say i take no responsibility if this causes problems but this worked for me. Do a search in the market for "eris market fix." it was designed for the eris but works just fine on my droid x. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but i assume most everyone on froyo already is rooted.
Click to expand...
Click to collapse
yes this worked for me aswell thank you
Yes this method definitely works. I have market working now and can search for protected apps etc.
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
he was just explaining where the idea comes from i think... You'd have to be crazy to use the eris market fix app on a droidx, just simply edit the build.prop fingerprint line.
I just used the root explorer meathod and now it wont boot.
I downloaded the file.
renamed my build.prob to build.prob/bak
placed the new build.prob in the system folder
rebooted and now after the M screen it just goes to a black screen with the backlight lit. Wont boot up. Im learning adb so this may be a noob question but can I access adb if the phone wont boot all the way up. That way I could change the build.prob back
Edit Delete Post: Im just retarted haha .prop not .prob :/
Could you plz give us some details on doing this with root explorer. Thanks
Prolly simple but I did try moving current build file then renaming and pasting yours without success doing us bank search. Also rebooted cleared cache and market history prior to search. Appreciate any help with doing this via root explorer.
LexusBrian400 said:
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
Click to expand...
Click to collapse
LexusBrian400 said:
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
Click to expand...
Click to collapse
I took a brief look at each file and I really don't understand how I got into trouble. As I said, I had not yet started doing any mods, just trying to install a few apps.
While I'm no computer or phone neophyte, I don't profess to be up to speed on Android yet. I do typically read through instructions pretty well, and search out multiple sources/explanations so I have a better 'understanding' of what I'm doing, rather than just "parrotting" the steps.
Having said that, I would like to know the difference between using 'adb remount' and the instructions I used in my first post. Is that just the difference in doing this via a shell command and not? ie, they perform the same action, just from a different starting point?
As for the Eris file, I did download that and all seems to be OK right now.
Sorry ahead of time for a possibly stupid question but I just wanted to be sure. Do you have to be rooted to do this fix?
Yes, it requires an edit to a file that you can only be edited when rooted
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
This works for me...thanks!
OP has been updated with original build.prop
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
will2live said:
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
Click to expand...
Click to collapse
Just use the non-stagefright one.
Just like the post says, stagefright breaks HD video playback for SOME people. However some people dont care and just want higher quadrant scores, so they use the stagefright=true build.prop
Use the =false version for better stability.
Thanks for the reply.
this script is based on the work to Danesham90 and others see link
http://forum.xda-developers.com/showthread.php?t=598026
===============================================================================
Tested on the Samsung Vibrant, Script may need modification for other phones
===============================================================================
===============================================================================
Directions:
===============================================================================
the easy way:
1. turn on USB debugging
2. plug phone in to computer
3. run the script and follow the screen pormpts
the script will download everything needed to make a
signed deodexed clockwork flashable update.zip while also
adding root and the modified 3e recovery in the proccess.
===============================================================================
the hard way:
http://forum.xda-developers.com/showpost.php?p=10986893&postcount=28
================================================== =============================
Code:
/* This program is free software. It comes without any warranty, to
* the extent permitted by applicable law. You can redistribute it
* and/or modify it under the terms of the Do What The **** You Want
* To Public License, Version 2, as published by Sam Hocevar. See
* http://sam.zoy.org/wtfpl/COPYING for more details. */
UPDATED 02/03/2010
bug fix to signupdate.jar
clockwork script tweeks
UPDATED 02/02/2011
added upload to ROM to SDCard
added reboot recovery
added test sign all apk's in ROM - see README for details
added pull "/data/app/" and install "/data/app"
UPDATED 02/01/2011
added adb on by default toggle
added data wipe toggle
updated smali/baksmali to 1.2.6
UPDATED 01/31/2011
updated adb
fix similar filename deletion when using delete.txt
added barebones_delete.txt deletes everything that
does not cause phone to crash
UPDATED 01/29/2011
add "symlink dumpstate SYSTEM:bin/dumpmesg" to update-script.
add "symlink debuggerd SYSTEM:bin/csview" to update-script.
completed secondary method to make ROM from extracted Odin files.
see this post for instructions
http://forum.xda-developers.com/showpost.php?p=10986893&postcount=28
UPDATED 01/28/2011
added auto delete apk's (bloat removal), edit bin/example_delete.txt and rename to delete.txt
added auto add apk's (pre-install or update apk's) add apk's to bin/apks directory
UPDATED 01/23/2011
fix path error when space in user name
UPDATED 01/22/2011
updated TempRoot.exe to not trigger anti-virus
updated Superuser.apk
This is fantastic! Thank you for always making things a little less troublesome.
Oooops, last minute change broke something, fixed and re-uploaded.
untermensch said:
Oooops, last minute change broke something, fixed and re-uploaded.
Click to expand...
Click to collapse
Thanks for the heads up. I was just testing this on KA5 for funsies. It looked like it went ok but there was a prob with temp root at the beginning and it looked like a few java errors at the end. I'll re-download and give it another go.
Edit: Ah, looks like it's working now. Temp root worked and it downloaded the modem and kernel.
Edit2: So it looked as though everything worked fine, but when I went to install it I got
E:Can't symlink /system/bin/cat
E:Failure at line15:
symlink toolbox SYSTEM:bin/cat
Installation aborted.
Whitehawkx said:
Thanks for the heads up. I was just testing this on KA5 for funsies. It looked like it went ok but there was a prob with temp root at the beginning and it looked like a few java errors at the end. I'll re-download and give it another go.
Edit: Ah, looks like it's working now. Temp root worked and it downloaded the modem and kernel.
Click to expand...
Click to collapse
I just tested on my laptop and got a java out of memory error
while signing the rom so I increased the heap size which seems
to have fixed it.
untermensch said:
I just tested on my laptop and got a java out of memory error
while signing the rom so I increased the heap size which seems
to have fixed it.
Click to expand...
Click to collapse
Yea I got the same thing as well. Thanks again, will give it another go.
Update: The process was more in-depth when deodexing. Signing went through np and when I flashed through clockwork it worked (goodbye splash screen!). There must be some issue with KA5 though. It got through to the Galaxy S screen and then started vibrating and then blackscreen. T_T
Thank god for this.. (Deodexer)
Thanks untermensch, your the best
Really really appreciate this. Thanks a bunch!
Most useful tool EVAR!
I T W O R K E D~!
My final attempt last night did not shoot out the "signed_ROM.zip" at the end. I ran it again this morning on KA5 and when it finished I had the signed_ROM.zip in the folder. Put that on my internal, flashed through clockwork and viola! Doedexed KA5 with root and modded 3e recovery. I can't thank you enough Untermensch for putting this together for everyone.
"Give a man fish feed him for a day. Provide him with tools to fish and feed him for a lifetime." (Yea I tweaked it but you get the idea!)
I noticed one thing. During the deodexing process I got [null] on one file in the core.odex. After it had all finished up I looked in the framework folder and core.odex was still there. So am I correct in assuming that it did not doedex properly? Other than that everything else looks golden.
Oh this is sick. i was looking for this all day the otherday when i was trying to deodex ka5! you rock and rule. i cant wait to explore the possiblities!
Whitehawkx said:
I noticed one thing. During the deodexing process I got [null] on one file in the core.odex. After it had all finished up I looked in the framework folder and core.odex was still there. So am I correct in assuming that it did not doedex properly? Other than that everything else looks golden.
Click to expand...
Click to collapse
I deleted the core.odex file and rebooted just to see what would happen and it soft bricked and is stuck at the Vibrant screen. So it seems the only issue lies in deodexing the core.jar at this point.
can i use this to port a rom? forgive me if that is a noob question. just wanted to know if i had the right idea...
Whitehawkx said:
I noticed one thing. During the deodexing process I got [null] on one file in the core.odex. After it had all finished up I looked in the framework folder and core.odex was still there. So am I correct in assuming that it did not doedex properly? Other than that everything else looks golden.
Click to expand...
Click to collapse
yep that was an baksmali error, likely you could run the script again and it
would baksmali OK.
this script is a real system stress test, any way I increased the java maxmem
setting for framework files to 1024m added error logging and the script will
now stop if there is an error. hopefully to prevent a broken ROM from being
released.
Whitehawkx said:
I deleted the core.odex file and rebooted just to see what would happen and it soft bricked and is stuck at the Vibrant screen. So it seems the only issue lies in deodexing the core.jar at this point.
Click to expand...
Click to collapse
can you reproduce this error? I have seen it once but cant reproduce it
untermensch said:
yep that was an baksmali error, likely you could run the script again and it
would baksmali OK.
this script is a real system stress test, any way I increased the java maxmem
setting for framework files to 1024m added error logging and the script will
now stop if there is an error. hopefully to prevent a broken ROM from being
released.
Click to expand...
Click to collapse
untermensch said:
can you reproduce this error? I have seen it once but cant reproduce it
Click to expand...
Click to collapse
Pretty sure the core.odex [null] error I got happened every time I ran the program. I ran it once after the 1:25am update and it happened. That is also the time it did not produce the signed_ROM.zip. I ran it again this morning after I saw the OP had been updated and it did produce the signed_ROM.zip but I still got the [null] error on core.odex. I'm going to Odin KA5 and do it again right now. I will let you know how it works out.
On a side note. I flashed the one I recieved this morning with everything being deodexed except the core.jar and it ran great until I deleted the odex file. Anywho, will test now. Also, not sure if this matters but I am running 32-bit Windows 7.
Update1: Initial news is good. Core.jar was deodexed properly with no errors. Will let you know how the entire process fairs once its completed.
Worked perfectly. I got no errors and everything deodexed properly. Flashed it on my phone and it's running just fine. You are awesome.
Thanks for retesting, glad it worked, there are thousands of files being generated
an lots of java processes being spawned so there are bound to be an occasional
error. I have added an automatic retry when there is an error to the next version
should be posted some time tomorrow.
I'm about 3/4 the way through testing this out - it seems to be working just fine with the exception that every command is appended with "ATTRIB" is not recognized as...
Hopefully it will work anyway.
One thing I noticed that might speed the script up in the beginning would be a root check, I have already rooted this rom but it still needed to run rageagainstthecage.
I've been looking for something like this forever now, thanks so much! Can't wait to play with it.
Sent from my SGH-T959 using Tapatalk
Issue 1: I'm trying to install ClockPackage.apk, Gallery3D.apk, MyFiles.apk in order to have the stock clock. I keep getting the error "Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]" when i try to use the command adb install (any of the 3).apk. I have also tried "adb push" which doesn't seem like a valid command. I tried moving the 3 apk files to my sd card on the phone and using "installer" and "eoeAppinstaller" from the market and these fail as well. Any more suggestions? I really like this di11igaf's ROM, but I cannot stand the new alarm ( i like the gradual volume increase of the stock). I have tried a couple of market clocks, but they just didn't work for me. Thank you very much in advance.
Issue 2: If I use CWM and choose Reboot into Recovery i get the following:
Android system recovery <3e>
Samsung Recovery Utils
- for BML -
Enter OK Key, Select : Vol UP / Vol Down
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
format internal sd card
update media, please wait
update media finished
-- Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
-- Applying Multi-CSC...
Installing Multi-CSC
(in red)
Installation aborted
At this point I can use the volume buttons to scroll up and down, but the power button will not select anything. The only thing I can do is remove the battery and boot the phone back up, which then takes me into CWM recovery v2.5.1.0. I was able to install the di11i add on, but I don't think that I'm supposed to be pulling the battery to get to this point.
Thanks again and sorry about the long post.
Im no expert on this type of stuff but I use di11i roms and I just transfer apk's to the root of the phone through the regular mass storage mode and use root explorer for the rest.Havent had any problems yet.
As for issue 2 is the package a .zip file? If not that may or may not be the problem.
From my own personal experience the 3dapp isn't sign so I can't install it too
System apps are best copied manually into the /system/app folder using app like root explorer. Make sure the folder is in r/w mode.
diablo009 said:
System apps are best copied manually into the /system/app folder using app like root explorer. Make sure the folder is in r/w mode.
Click to expand...
Click to collapse
+1 you can simply use root explorer to copy the apk files into \system\app folder. quick and easy.
booty hater said:
As for issue 2 is the package a .zip file? If not that may or may not be the problem.
Click to expand...
Click to collapse
It is a zip file and it installed. What concerned me was the process. Should it have frozen up like that and forced a battery pull? Nothing I've read leads me to believe that was proper behavior of the CWM.
diablo009 said:
System apps are best copied manually into the /system/app folder using app like root explorer. Make sure the folder is in r/w mode.
Click to expand...
Click to collapse
I don't have that directory. Are you creating it on the phone and then putting the files into it? I may have not been clear on what I am trying to do. I am trying to do what was posted in this forum http://forum.xda-developers.com/showthread.php?p=11207089&highlight=clockpackage#post11207089 posts #2515
I just looked into exactly what you were talking about and I got it figured out.It wasnt installing for me either but this is what I did and it works now.
Through mass storage mode I copied the 3 files to the root of the card.
Then I moved the files to the app folder which is inside the system folder.
I use root explorer for the moving.
When you move them into the app folder its gonna ask to overwrite say yes.
After you get everything moved it will work if you go to the app in the drawer.I never actually installed anything but did an overwrite.
booty hater said:
I never actually installed anything but did an overwrite.
Click to expand...
Click to collapse
Right. Apps in the system/app folder are auto-picked up
supervg3 said:
I don't have that directory. Are you creating it on the phone and then putting the files into it? I may have not been clear on what I am trying to do. I am trying to do what was posted in this forum http://forum.xda-developers.com/showthread.php?p=11207089&highlight=clockpackage#post11207089 posts #2515
Click to expand...
Click to collapse
u cannot see it in my files. u need to have root access, and something like root explorer.
So it looks like I could have just copied and pasted the files from the sdcard/Clock folder I placed them in to the /system/app folder using Super Manager. I swear I tried that and it failed before I went through all the crappy steps below. Oh well.
Ok this is going to sound pretty cheap, but I didn't want to pay the ~$4.02 for an ap that I was going to use three times. I did find another way. I used Super Manager and http://forum.xda-developers.com/showthread.php?t=877316&highlight=installing+apk post #3.
So for any other cheapskates out there.
1. Install Super Manager on phone
2. Install ADB on pc
3. Connect phone to pc and copy the three files ClockPackage.apk, Gallery3D.apk, and MyFiles.apk to the sd card. (I just drag and dropped in windows explorer)
4. Use Super Manager to move to /system/app/ and rename the existing file Gallery3D.apk (I renamed it to Gallery3D.old)
5. Use adb to copy the 3 files from the directory in which you originally placed them on the phone to /system/app/
in adb type:
adb shell
su
(accept the prompt on your screen)
cd /sdcard/whereveryoustuckfile
cp blahblahblah.apk /system/app/ (the red from Pirateghost).
6. Reboot
The clock and alarm work fine, but I cannot get Daily briefing option in alarm to work. I get a FC. I did install the "apk add on pack for 5.6" post 3 of http://forum.xda-developers.com/showthread.php?t=897416 , but I dont think Daily Briefing was included in that. Any suggestions? And one last thing - what is the di11iBrowserfix.zip from post 3 of the thread above for? Thanks again to all who contributed.
I got the daily briefing working. Everything is almost perfect, but I would like two things still.
1. Is there anyway to change the tune that is played when you have smart alarm selected? I have a different tone selected, but I think once you select smart alarm it defaults to that new age tone.
2. My alarm goes off, I stop it, but then I have to unlock it before I see the daily briefing. Can anyone think of a way to have the phone unlock when I turn off the alarm. I know it is so insignificant, but it used to do that when it was stock and it was pretty cool.
Come one guys and gals - don't make me figure this one out by myself j/k but seriously I have surprised myself already by getting this far and I really don't have skill or knowledge for the last two things. I'm learning though....slowly.
Thread etiquette
Did I do something wrong here? I got some really quick responses to my questions before, but nothing on my latest. I ask this next question with all seriousness - should I have started a new thread since it's kind of a new topic? No worries either way, I just want to post in the the most effective way. Thanks. BTW, my phone is working great. I'm getting ready to install 6.0 GPS is a little screwy - often has me west of my location by about 30 meters by I attribute that to the phones hardware. Other than that I have no complaints (except for the lame smart alarm tune)
diablo009 said:
Right. Apps in the system/app folder are auto-picked up
Click to expand...
Click to collapse
Diablo, I know this totally off topic and I´m sorry, but I´ve just seen your signature and noticed you run di11igaf´s 6.0 on Glitterballs and as I´m not able to post on development yet, here´s my question:
Will I have too much trouble on flashing another kernel over the di11picKle? I was happy with speedmod + jk4... that was the best working config for me so far...
Just keep in mind I´m a noob
ddoubt said:
Diablo, I know this totally off topic and I´m sorry, but I´ve just seen your signature and noticed you run di11igaf´s 6.0 on Glitterballs and as I´m not able to post on development yet, here´s my question:
Will I have too much trouble on flashing another kernel over the di11picKle? I was happy with speedmod + jk4... that was the best working config for me so far...
Just keep in mind I´m a noob
Click to expand...
Click to collapse
you should start a topic instead append to other's topic.
you can flash any kernel/modem using CWM, just make sure it is i9000's.
ddoubt said:
Diablo, I know this totally off topic and I´m sorry, but I´ve just seen your signature and noticed you run di11igaf´s 6.0 on Glitterballs and as I´m not able to post on development yet, here´s my question:
Will I have too much trouble on flashing another kernel over the di11picKle? I was happy with speedmod + jk4... that was the best working config for me so far...
Just keep in mind I´m a noob
Click to expand...
Click to collapse
Nope. Get the CWM flashable zip, and copy to ur sdcard. Then go to CWM recovery console, and install this zip. Reboot.
But, please take a nandroid backup, and try to avoid OC kernels if u r unsure ur phone can handle it. Phones freeze when tried to oc beyond their capability.
diablo009 said:
Nope. Get the CWM flashable zip, and copy to ur sdcard. Then go to CWM recovery console, and install this zip. Reboot.
But, please take a nandroid backup, and try to avoid OC kernels if u r unsure ur phone can handle it. Phones freeze when tried to oc beyond their capability.
Click to expand...
Click to collapse
Thanks for the info and sorry for appending to this topic!
I had a patched version of libflashplayer.so that worked fairly well with Hulu on VEGAn 5.1.1 but when I upgraded what I think was the same .so no longer worked.
So here's what you want to do:
1) Install Flash 10.2 off the market or however else you do it.
2) Get this: http://www.2shared.com/file/hW5sepYW/libflashplayer.html
3) Use your favorite method (adb, root explorer, etc.) to make a backup copy of /data/data/com.adobe.flashplayer/lib/libflashplayer.so (I named mine libflashplayer.so.bak)
4) Put the file you downloaded in step 2 over the original (that's /data/data/com.adobe.flashplayer/lib/libflashplayer.so)
5) You need to make sure the browser restarts. If you are adept, go to Settings, Applications and force close the browser. If that worries you, reboot the tablet (nuclear option).
6) Make sure the browser is set to report itself as a desktop (Depends on your browser).
Notes: If you are running Ad Free, Hulu will complain and make you wait 30-60 seconds while it complains.
If it looks like it is working but the screen is black or frozen, touch the video. The click sensitivity is ridiculously high so when you try to adjust anything or press play or full screen it will often see the press twice and just go back to pause.
Works fine with pershoot's latest kernel and VEGAn Ginger even full screen. I'm using Opera Mobile. Haven't tried others, but if they load flash should be ok.
Good luck!
Update: The "Long boot problem" winds up erasing this fix on each reboot! Until that gets figured out here's a work around:
Get Script Manager from the market. Create a script that runs as root at boot time.
Script manager already puts in the first line you need so the whole script looks like this:
#!/system/bin/sh
cp /mnt/sdcard2/libflashplayer-patched.so /data/data/com.adobe.flashplayer/lib/libflashplayer.so
Use your favorite method to put the patched so file on /mnt/sdcard2 (or where ever you want to put it). If the boot thing gets fixed you should not need this anymore.
It is wise to test the script by simply running it before rebooting. You should not get any errors. If you do, fix them before you reboot.
Awesome, thanks! I tried everything and the closest I could get was picture but no sound. This worked perfect, using stock browser. Thanks again!
For some reason, it used to work to just change AND to WIN but now you have to jimmy the version number as well, apparently.
Okay following instructions exactly....downloaded new file and using rootexplorer to rename old file (bak) and replacing with downloaded file....
When I reboot my tablet the library file is resetting back to default....the original file is put back in place and the new downloaded file and backup file (bak) are nowhere to be found.....
I'm on VeganGinger using pershoots new oc kernel.....
Any ideas?
Hmm... same thing here! I just rarely reboot because it takes so long.
So this is probably related to the boot time issue. I figured out that the boot time is long because it unpacks the native libs for everything at boot time which I don't think it should be doing. So that explains that.
Could make a new APK but it would have to be signed. What I will probably do is keep my patched copy somewhere else and do a Script Manager script at boot time to do a copy:
cp /mnt/sdcard2/libflashplayer-patched.so /data/data/com.adobe.flashplayer/lib/libflashplayer.so
(all on one line)
A hack, for sure though.
That does the trick, it looks like. You can get Script Manager on the market. Gscript would work but it can't auto run on boot as far as I know. This makes me more certain that VEGAn 5.1.1 was NOT unpacking the APKs on boot
Script manager already puts in the first line you need so the whole script looks like this:
#!/system/bin/sh
cp /mnt/sdcard2/libflashplayer-patched.so /data/data/com.adobe.flashplayer/lib/libflashplayer.so
Use your favorite method to put the patched so file on /mnt/sdcard2 (or where ever you want to put it). If the boot thing gets fixed you should not need this anymore.
The other thing I use ScriptManager for is to bind mount sdcard2 in the /mnt/sdcard/sdcard2 directory so programs that only look in /sdcard can find things in my sdcard2 folders.
Fantastic ...thanks wd!
I'll give it a try...thanks for figuring out a work around so quickly ...
QUESTION .....so I create a the new script with Script Manager and place it where? Sorry ...have done the rooting, ROMs, kernels, etc. but scripts are new territory for me...thnx.
UPDATE.....Okay....created script to match your example...placed libflashplayer-patched.so on sdcard2...not sure where created script should be placed....checked "run at boot"...placed new script file on sdcard2, but Hulu did not work after rebooting so I'm guessing script needs to be in another location to run.....
script manager puts them in its folder. what happens if you run it from script manager? I am sure it needs root checked.
first time using Script Manager so I selected "New Script" and then gave it a file name "Hulu"...then copied the script language into that file and then Run...
came back with errors:
cp: can't stat '/data/data/com.adobe.flashplayer/lib/libflashplayer.so/mnt':not a directory
cp: can't stat '/data/data/com.adobe.flashplayer/lib/libflashplayer.so/libflashplayer-patched.so': Not a directory
Those paths are not right. Missing space I think.
Here is what I have:
Code:
#!/system/bin/sh
cp /mnt/sdcard2/libflashplayer-patched.so /data/data/com.adobe.flashplayer/lib/libflashplayer.so
yep...too many spaces..fixed that..
now when I do a quick run in Script Manager I get the following error:
cp: can't create 'data/data/com.adobe.flashplayer/lib/libflashplayer.so': File exists
do you have run as root checked?
wd5gnr said:
do you have run as root checked?
Click to expand...
Click to collapse
Bingo....I had Run on Boot, but not Run as Root....
Unfortunately after running and going to Hulu...on the main page I am getting a messages saying: "Hulu requires Flash Player 10.0.32 or higher. Please download and install the latest version of Flash Player before continuing."
I have the latest Flash 10.2 available for Android....user agent is set to desktop on browser....strange...
10.2.59.1 is what I get at www.playerversion.com. Is it possible you have the wrong one in the data directory?
is that the libflashplayer-patched.so file? I'm using the one from the download link in your original post..
if that's not it let me know....thanks for your help..sorry you're having to walk me through this....
WHEN I GO TO PLAYERVERSION.COM ON MY TABLET IT SAYS I DON'T HAVE FLASH PLAYER INSTALLED. Could the replacement libflashplayer.so file be incorrect?
Its working for me. You do have Flash 10.2 installed from market first right? I'm sure you do or it wouldn't be getting overwritten.
Here's what I'd suggest.
Remove and reinstall 10.2 plain. Turn off the boot script. Reboot.
Open some flash site like the player test site with your browser of choice (I use Opera Mobile). Observe that it tells you that you are on 10.2. something.
Now turn the boot script back on. If you force close the browser, just run the script. If you prefer, just reboot. Now go back to the same site and observe that you have Flash running and it is now the patched version #. If not, Hulu isn't going to work.
Once that's working, try Hulu again.
No worries. Would be good to know that it works somewhere else ;-)
Works great!
Thanks. Works great on the stock browser. Still get the "your operating system not supported usung Opera Mobile" tho. Just downloaded latest version of opera and it no longer let's you choose type of system, so I imagine that is the problem.
Is that Opera Mobile or Opera Mini?
Okay...Hulu now up and running...
When I looked at the script and realized what it was actually doing I realized that I shouldn't have been actually naming the patched file as "-patched" as that was why after the script ran Flash no longer showed up...
I renamed to match the libflashplayer.so file it was replacing...also moved file and script reference to "sdcard" rather than "sdcard2" to see if that made a difference...now working fine on Hulu....
Thanks for the fix and walking a noob thru using scripts!
wd5gnr said:
Is that Opera Mobile or Opera Mini?
Click to expand...
Click to collapse
I think it's Opera Mini that only gives you the option of turning on or off "mobile" version of browser...tried it out earlier....
I'm using the the stock 2.3.4 from Spice website and this is by far the best considering wifi important.
My question is, can we enable init.d support or we need a special kernel for that?
I tried a tut. from zeppelin but failed miserably...
Any idea guys???
whyzee,
I followed this http://forum.xda-developers.com/showthread.php?t=1017291 and was able to use init.d without any issues.
cowsgo said:
whyzee,
I followed this http://forum.xda-developers.com/showthread.php?t=1017291 and was able to use init.d without any issues.
Click to expand...
Click to collapse
Thanks for the link but that was the one I tried without success .... Should try again when I have some real time...
whyzee
did you get an error when you ran the script? If you didn't then get root explorer from the market and see if you have the folder. It should be in the \system\etc folder. When I ran it I had no issues and followed the instructions that were on the page. Dumb question, did you reboot your phone once you ran this? If you got a error then you could try pm Zep and see if he has ideas that might help.
cowsgo said:
whyzee
did you get an error when you ran the script? If you didn't then get root explorer from the market and see if you have the folder. It should be in the \system\etc folder. When I ran it I had no issues and followed the instructions that were on the page. Dumb question, did you reboot your phone once you ran this? If you got a error then you could try pm Zep and see if he has ideas that might help.
Click to expand...
Click to collapse
The script you are executing is not meant for our device. Its trying to mount system partition as mtd type, while we need emmc partition type. Also, our device does not have moto-boot-mode file which this script is trying to replace.
So my suggestions are :
If you are using MIUI or CM, then they already support init.d scripts. (I guess)
Or
If you are using stock or andro - id then just copy following code in post boot.sh (something like that) found in /system/etc/, at the end of file.
Code:
for BOOT in "/system/etc/init.d/"*; do
.$BOOT
done
P.S. Note that you have enabled executable permission for all of your scripts placed in /system/etc/init.d
Sent from my CSL-MI410 using XDA App
Thanks for the replies guys, I've jumped to MIUI 1.10 now and as Napstar said it natively supports init.t...
whyzee said:
Thanks for the replies guys, I've jumped to MIUI 1.10 now and as Napstar said it natively supports init.t...
Click to expand...
Click to collapse
hi
correct me if im wrong. To my knowledge u need init.d to use apps2sd so u can put ur apps on ur SD and now since our phone has around 1GB phone storage which i feel is more than enough to install all the apps u need I dont see a reason why we need the init.d
haree said:
hi
correct me if im wrong. To my knowledge u need init.d to use apps2sd so u can put ur apps on ur SD and now since our phone has around 1GB phone storage which i feel is more than enough to install all the apps u need I dont see a reason why we need the init.d
Click to expand...
Click to collapse
init.d is a folder on /system/etc folder which runs whatever scripts you put in it during boot.....