Related
Hi, after the update to froyo (in my case JP6) i found out the appbrain fast web installer wasn't working anymore. After some reading, it seems that the android_id (which this app uses) is set to a fixed number during the froyo update. This means the app cannot find a unique android_id to send the 'install instruction' to.
Source: http://forum.xda-developers.com/showthread.php?p=8604909#post86049
1. Make sure and backup your /dbdata/databases /com.android.providers.settings /settings.db file
Then in ADB or connectbot type the following
su
cd /dbdata/databases/com.android.providers.settings sqlite3 settings.db
sqlite> insert into secure (’name’, ‘value’ ) values (’android_id’,'device_id_goes_here’);
sqlite> .exit
Reboot
note 'device_id_goes_here’is your 16 digit HEX device ID
Click to expand...
Click to collapse
This fix seems to do the job, but i can't get it to work. Probably because i made a mistake with the usage of su and shell etc.
So i tried to fix it another way and this is how i did it (similar to the other fix):
1) With RootExplorer (or similar) navigate to: /dbdata/databases/com.android.providers.settings/
2) Make a backup of the file (by copying it)
3) Change the permissions of the file (using RootExplorer) ,so that it can be moved/sent to your pc using Dropbox,Gmail,Bluetooth etc. In this example i have moved it to my c:/ folder on windows.
4) When the file is on your pc. Run windows command (cmd) and navigate (using cd) to your /android/tools folder.
5) Execute: 'sqlite3 c:/settings.db
6) Now type in (after sqlite>): insert into secure (’name’, ‘value’ ) values (’android_id’,'device_id_goes_here’);
Note: 'device_id_goes_here' is a random (so you can choose whatever you want) 16 digit number.
7) Type: .exit and close the cmd box.
8) copy the settings.db file back to your phone and move it back to /dbdata/databases/com.android.providers.settings/
Choose yes when overwrite prompt pops up.
9) Reboot your device
10) Register your device using the 'Fast web installer' app on your phone.
11) DONE! You're ok again to install apps OTA using the appbrain market!
Click to expand...
Click to collapse
Note, if you don't know how to do step 4-7, read some articles about how to set up and use adb (since that also contains the sqlite3 tool)
I hope this helps for people having problems with this.
Hanness said:
Hi, after the update to froyo (in my case JP6) i found out the appbrain fast web installer wasn't working anymore. After some reading, it seems that the android_id (which this app uses) is set to a fixed number during the froyo update. This means the app cannot find a unique android_id to send the 'install instruction' to.
Source: http://forum.xda-developers.com/showthread.php?p=8604909#post86049
This fix seems to do the job, but i can't get it to work. Probably because i made a mistake with the usage of su and shell etc.
So i tried to fix it another way and this is how i did it (similar to the other fix):
Note, if you don't know how to do step 4-7, read some articles about how to set up and use adb (since that also contains the sqlite3 tool)
I hope this helps for people having problems with this.
Click to expand...
Click to collapse
Looks good. One question, how do you find out what your original device ID is? I have a UK unbranded GT-I9000... what's the ANDROID ID for that?
Ah, you just make one up. I used SQLite Editor to just edit the file, made up my own number and rebooted. Works fine now. A bit simpler than your suggestion above.
tokyogtr said:
Ah, you just make one up. I used SQLite Editor to just edit the file, made up my own number and rebooted. Works fine now. A bit simpler than your suggestion above.
Click to expand...
Click to collapse
That should indeed be easier
In the post I refer to in the captivate forum, there is mentioned an app to find out your android_id. But to know your original id, you would first have to reflash to an older firmware where the id is not touched. But it is true, you can just make up your own 16digit number. Only some games with online highscores fixed to the id instead of an account could benefit to know your old id, I think.
Worked for me!
Sent from my GT-I9000 using Tapatalk
hum
shud be easier to just download "Android ID Changer" from market after installing sqlite3. does the same trick.. but more user-friendly for people not so comfortable to use adb shell.
trasig said:
shud be easier to just download "Android ID Changer" from market after installing sqlite3. does the same trick.. but more user-friendly for people not so comfortable to use adb shell.
Click to expand...
Click to collapse
Hmm maybe Iḿ retarded, but how do I install sqlite3 to my phone?
No clue what he meant with installing sqlite3, I just downloaded the said Android ID Changer, made up and applied an ID and now Fast Web Installer works just fine.
I don't know if it is just coincidence or due to this, but before that I had tons of "download unsuccessfull" errors with the Market. Downloads failed nine out of ten times. Now, with changed ID, it works flawlessly again! My phone runs on JP6 Voodoo Doctor Edition 2.1.
Thanks for this advice!
I just installed the ID changer, entered a new code and rebooted, but the ID had not changed..
first time i tried it i got an "error editing databases".... do you have to change permissions to the folder/directory for the settings.db?
ukdtweak said:
I just installed the ID changer, entered a new code and rebooted, but the ID had not changed..
first time i tried it i got an "error editing databases".... do you have to change permissions to the folder/directory for the settings.db?
Click to expand...
Click to collapse
same problem here....
The only thing remotely related I could think of is that I had my system folder mounted as R/W with SGS Toolbox. But does that affect dbdata?
Check SGS Toolbox on mine and system was already mounted as RW...
I have tried changing the permissions with Root Explorer, to dbdata etc. but after rebooting, they are back as they were?
Beats me... but I can now confirm that the "download unsuccessfull" errors are back in place. It was just a coincidence after all, and shows that the blame is on Google, not any specific ROM or mod.
Fast Web Installer still worked though, even made it past the "unsuccessfull" barrier.
Wonderful fix!
Hanness, have you considered reporting this to Samsung? I think having the proper Android ID set and retained during firmware updates is quite important.
miki4242 said:
Wonderful fix!
Hanness, have you considered reporting this to Samsung? I think having the proper Android ID set and retained during firmware updates is quite important.
Click to expand...
Click to collapse
According to this, this may be due to ro.serialno not being set in build.prop
trasig said:
shud be easier to just download "Android ID Changer" from market after installing sqlite3. does the same trick.. but more user-friendly for people not so comfortable to use adb shell.
Click to expand...
Click to collapse
Android ID Changer did the trick for me . (I have not done anything with sqlite3.)
I used http://www.dbsoftlab.com/database-editors/database-browser/overview.html to edit settings.db as explained.
Works like a charm. Downloads & Updates are flying in!
Edit: After few downloads it stucks again, I deleted Market data. Works again. Bugs everywhere ...
Hanness said:
Hi, after the update to froyo (in my case JP6) i found out the appbrain fast web installer wasn't working anymore. After some reading, it seems that the android_id (which this app uses) is set to a fixed number during the froyo update. This means the app cannot find a unique android_id to send the 'install instruction' to.
Source: http://forum.xda-developers.com/showthread.php?p=8604909#post86049
This fix seems to do the job, but i can't get it to work. Probably because i made a mistake with the usage of su and shell etc.
So i tried to fix it another way and this is how i did it (similar to the other fix):
Note, if you don't know how to do step 4-7, read some articles about how to set up and use adb (since that also contains the sqlite3 tool)
I hope this helps for people having problems with this.
Click to expand...
Click to collapse
Thank you very much...I followed your instructions exactly and managed to fix it. Android ID changer didn't work for me.
sadly appbrain is blocked in China for whatever reason I don't know... so that won't work for me hehe
stassano said:
sadly appbrain is blocked in China for whatever reason I don't know... so that won't work for me hehe
Click to expand...
Click to collapse
oh well, the great firewall of china at work again.
FIRST THINGS FIRST:
This represents very little work that I've done on my own. It is mostly appropriating the work of others. The important thing to note is that the file works and it works well.
All I did to create this file was incorporate a modified version of stachre's updater-script into the official WiFi 3.1 update from Google (this is not the file you should flash).
I then added the kernel & all of the files from bigrushdog's HC3.1 .zip EXCEPT the system.img file (which is the vast majority of the update). BRD's HC3.1 installs the 3G version of 3.1 with Hotspot/Tethering options in the settings menu under Wireless & Networks, and I personally want to have the WiFi-only software on my WiFi XOOM. His version seems to work just fine and the only difference I noticed was in the Settings menu, but that was enough of a difference for me to prefer the WiFi only software. I'm sure more of you may feel the same. If there are any other differences between the WiFi & 3G software I'd be curious to know what, if any, there are.
I then added the code from BRD's updater-script (minus the parts relevant to flashing the system.img) on to the end of the updater-script from stachre's updater-script.
One of the benefits of this approach is that it does not require you to perform a factory data reset, as BRD's method currently does. And yes, you will have access to your external SD Card in the /sdcard/external folder.
It is super late and I am exhausted, but I wanted to share this with you before I fall asleep. If you seem to notice that these instructions are more or less copy and pasted verbatim from stachre's thread, that is because they are. This is a simplified version of his method with the addition of BRD's modified version of the stock 3.1 kernel for SD Card storage. There are fewer steps (now only 2) because more files are included in the zip.
[size=+1]DOWNLOAD HERE - FLASH IN CLOCKWORK RECOVERY:[/size]
MZ604_3.1_ROOT_update.zip
WARNING: Following this procedure may damage or permamently destroy your device. This procedure is provided with NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Perform this procedure at your own risk.
COMPATIBILITY NOTE: I have personally tested this procedure ONLY ON THE US XOOM WIFI MZ604. If other devices (i.e., Euro Xoom WiFi) implement the same Android 3.1 update file, then this procedure *should* work; some users have reported success with UK and Canadian models (see this post for more info). Know, however, that you proceed at your own risk. If you're stuck in a boot cycle, try a factory data reset in recovery.
[size=+1]SUMMARY[/size]
Here's a run-down on the current procedure:
Updates the Xoom WiFi to Android 3.1 using ClockworkMod Recovery (MZ604_3.1_ROOT_update.zip)
Resolves issue in updater-script: get_prop ro.product.device wingray
Pushes Superuser and su, sets correct permissions to enable functioning root
Flashes the system partitions to stock (required at this time)
Flashes bigrushdog modified stock boot.img (kernel) to enable external storage
Updates bootloader to include Recovery in the boot menu
Leaves user data intact
Leaves recovery intact
Outstanding Issues:
The new
Videos.apk does not appear in app drawer after update, according to Motorola this was done intentionally. Videos still play in Gallery. For some reason Motorola doesn't want us to use this app yet on the WiFi Xoom, but it's available on the 3G Xoom.
Now, without further ado...
[size=+1]ASSUMPTIONS[/size]
You've downloaded the update here: MZ604_3.1_ROOT_update.zip
You've downloaded and unzipped the stock Xoom WiFi MZ604 HWI69 images from Motorola also available via torrent
You've flashed a recent version of ClockworkMod Recovery (thanks, bigrushdog, koush, et al)
You've installed a physical SDCard in your Xoom (required for ClockworkMod Recovery updates) and have it functioning properly
You've configured the Android SDK on your PC, with adb functioning properly
You've downloaded fastboot and have it functioning properly (usually alongside adb in platform-tools)
[size=+1]PROCEDURE[/size]
Flash stock system.img & boot.img
Prior to performing the actual update, the update script checks a number of files (including bcm4329.ko, which is usually built with the kernel) in /system. If any file doesn't match what's expected, the update halts. Flashing the stock system.img ensures a smooth update.
The pre-update checks also include the boot partition. The actual update flashes this partition with a new kernel that implements the new 3.1 features.
If you are unlocked and running unrooted stock Android 3.0.1, you can skip step 1. If you are already on 3.1 and just need root and/or external SD card storage, see this thread.
Code:
adb reboot bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
Perform update
Code:
adb reboot recovery
You may need to re-enable USB debugging in the Application settings menu before you can send the above adb command. Alternately after sending 'fastboot reboot' in step 1, wait a few seconds after you see the Motorola logo and tap the Volume Down button. If you see "Android Recovery" at the top of the screen, tap the Volume Up button to boot into recovery and install from there.
Note that in recovery, you use the hardware volume buttons to navigate up and down, and the power button to select.
In ClockworkMod Recovery, select "mounts and storage"
Ensure your Xoom is connected to your PC via USB, then select "mount USB storage"
On your PC, copy MZ604_3.1_ROOT_update.zip to the root of the Xoom's SDCard ("Removable Disk" in Windows)
In ClockworkModRecovery (still on the "USB Mass Storage device" screen) select "Unmount"
In the "Mounts and Storage Menu" screen, if the option "unmount /sdcard" is present, continue to the next step; if "mount /sdcard" is present, select it then continue
Select "+++++Go Back+++++"
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select "MZ604_3.1_ROOT_update.zip"
Select "Yes - Install MZ604_3.1_ROOT_update.zip"
"Install from sdcard complete." will indicate that the update is completed.
.
Select "reboot system now"
New bootloader will install. The message, "Congratulations! Your bootloader was successfully upgraded" will be immediately followed by an automatic reboot.
Enjoy your rooted Xoom WiFi, running on Android 3.1!
CUSTOM KERNELS:
I told you guys it wouldn't be long. TDR has already released an overclock kernel for WiFi Xooms on 3.1.
Tips & Tricks for quick-booting into Fastboot & Recovery:
Booting into Fastboot:
Hold down both the power button and the Volume Down button. Fastboot support will boot and you can flash system/recovery/userdata images.
Booting into Recovery:
I haven't seen anyone else mention this. If you power up, wait a few seconds after the Motorola logo appears, then hit the Volume Down button you will see "Recovery" appear at the top of the screen. Hit the Volume Up key to boot into recovery!
Great instructions, the simplest I could see so far! The above process worked for my WIFI only XOOM which I had rooted and installed the Tiamat Xoom Kernel. I am in Australia so was impatient to wait for OTA which probably wouldn't have worked anyways from what I have read.
How does this differ from bigrushdogs procedure? I have a wifi only xoom and am not sure which method to follow. Is this for stockusers?
it is different because no wipe is needed, if you are stock (unrooted) you will have to wipe when you unlock the bootloader
This is exactly the method I used, though I did thinks manually and it took a while, but works great
I don't know about the videos.APk thing, there are some 3g users with the same problem, one current theory is that it has something to do with root
Sent from my Xoom using Tapatalk
Dubar said:
I don't know about the videos.APk thing, there are some 3g users with the same problem, one current theory is that it has something to do with root
Click to expand...
Click to collapse
I think this problem is a bit two-faced, as a few of us on the 3G/VZW XOOM have updated fine and have a working video player, but rentals purchased do not play instead throw an Error 49 license error, while local content plays fine.
The Wifi users are reporting that the videos app doesn't even show up, let alone open. General suckage, not even being able to play local content.
I've been tinkering around with logs and trying to narrow down my error 49 issue but thus far have been unsuccessful.
xoppaw said:
How does this differ from bigrushdogs procedure? I have a wifi only xoom and am not sure which method to follow. Is this for stockusers?
Click to expand...
Click to collapse
Yeah, the two main differences between this and BRD's procedure is that you don't have to perform a factory reset to get this one to work, and this method requires adb/fastboot. I don't think you should have to erase all your data just to install an official update. It's also only one file to flash.
The other difference is that this version doesn't have artifacts from the 3G version in the Wireless & Networks Settings menu (if that bothers you).
I don't know if this update would apply on an unlocked and unrooted Xoom, but if your Xoom is unlocked this version of the update should give you root. Both would be worth testing
Dubar said:
I don't know about the videos.APk thing, there are some 3g users with the same problem, one current theory is that it has something to do with root
Click to expand...
Click to collapse
tekuru said:
I think this problem is a bit two-faced, as a few of us on the 3G/VZW XOOM have updated fine and have a working video player, but rentals purchased do not play instead throw an Error 49 license error, while local content plays fine.
The Wifi users are reporting that the videos app doesn't even show up, let alone open. General suckage, not even being able to play local content.
I've been tinkering around with logs and trying to narrow down my error 49 issue but thus far have been unsuccessful.
Click to expand...
Click to collapse
You can still play videos/local content fine through the gallery app, so we are safe in that respect. I can still watch all my movies or videos filmed on the Xoom just fine.
Here are some observations that I made. The WiFi update only included the Videos.apk file while the 3G update also included a Videos.odex file as well. I chose to add the Videos.odex to the update file in the OP, but it didn't make a difference (Videos apk still doesn't show in the app drawer).
Thanks.. Worked great.
Note: I had to re-enable USB debugging on the Xoom after flashing the Stock System and Boot Images.
Land Master said:
Thanks.. Worked great.
Note: I had to re-enable USB debugging on the Xoom after flashing the Stock System and Boot Images.
Click to expand...
Click to collapse
Thanks, I updated the OP to take account of that. Ever since I figured out how to boot into recovery from the Motorola logo I haven't really needed to send the 'adb reboot recovery' command.
I used BRD update method for my wifi zoom (don't care about the extra settings) and I have a working videos.apk that plays local content. I have not yet tried to rent a video.
kev0153 said:
I used BRD update method for my wifi zoom (don't care about the extra settings) and I have a working videos.apk that plays local content. I have not yet tried to rent a video.
Click to expand...
Click to collapse
Yes, I'm pretty sure for whatever reason the Videos.apk is enabled for the 3G version of 3.1 but not for the WiFi version of 3.1. I agree that the extra settings isn't a big deal, I made this file mostly because I wanted a way around wiping all of my user data.
Rumor has it that Google has said that the Videos.apk will be working on the WiFi Xoom in a few days.
I used the method posted by stachre from yesterday, and I don't have access to my sdcard in sdcard/external. Any way I can change that? The two methods seem to be very similar...and I want my SD!
IXIKelsonIXI said:
I used the method posted by stachre from yesterday, and I don't have access to my sdcard in sdcard/external. Any way I can change that? The two methods seem to be very similar...and I want my SD!
Click to expand...
Click to collapse
Download and flash this file:
http://www.mediafire.com/download.php?2bj5taicy3buc5c
Basically do what I said to do in the OP but skip step 1.
You are beautiful, and I love you.
I installed brd's 3.1 update yesterday, and i tried to install this zip over his method because i have a wifi xoom and wanted to get rid of the hotspot settings, but when i try to flash this in cwm i get an error:
Assert failed: file_getprop("system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.0.1/hwi69/110420:user/release-keys" || file_getprop("system/build.prop", "ro.build.fingerprint") == "motorola/tervigon/wingray:3.1/hmj37/124251:user/release-keys"
E: error in /sdcard/mz604_3.1_ROOT_update.zip
(status 7)
installation aborted
What is the problem? Is it not possible to flash this over his method? Do i have to change the build.prop?
Thanks
Edit:
Solved by going back to stock 3.0.1 and installing the cwm to get updated to 3.1.
WARNING Boot Loop!
Warning. This method set me in to a boot loop. The tip at the bottom of the instructions eventually saved me as I booted in to recovery (adb stopped working after awhile) and upgraded via bigrushdog's clockwork thread. Not sure if it was my custom boot theme or something else. I reflashed twice while adb was still working. All looked good each time but then when I rebooted to do the final cwm step, this is where I looped each time. I was careful. Not sure why it messed up.
Thanks a lot for putting this together, worked like a charm.
So what about overclocking. I don't have option above 1ghz. Is this because we are back on a stock kernal. Will we have to wait for Tia to make a new one?
Sent from my Xoom using XDA Premium App
kntdookoo said:
So what about overclocking. I don't have option above 1ghz. Is this because we are back on a stock kernal. Will we have to wait for Tia to make a new one?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Bigrushdog has said that they are working on an overclock tiamat kernel for Android 3.1. So yes it is expected that you can not overclock your xoom in 3.1 currently.
A few questions since I have not updated my xoom to 3.1 yet:
1) Is everyone experiencing the Videos.apk error where they can't install the videos app?
2) How are the 3.1 updated features? Can anyone share if the overall user experience is better in 3.1 (better scrolling, smoother, etc).
I am kinda holding off updating 3.1 until I hear more of the drawbacks of 3.1.
ericdabbs said:
Bigrushdog has said that they are working on an overclock tiamat kernel for Android 3.1. So yes it is expected that you can not overclock your xoom in 3.1 currently.
A few questions since I have not updated my xoom to 3.1 yet:
1) Is everyone experiencing the Videos.apk error where they can't install the videos app?
2) How are the 3.1 updated features? Can anyone share if the overall user experience is better in 3.1 (better scrolling, smoother, etc).
I am kinda holding off updating 3.1 until I hear more of the drawbacks of 3.1.
Click to expand...
Click to collapse
1. It's weird. My understanding is that even, unrooted stock WiFi Xoom owners can't access the new Videos apk on 3.1. The Videos.apk is there it just doesn't show up in the app drawer so there isn't any way to access it. If you look for it in a file manager like Root Explorer you can see it. There are other "ghost" apps like that in Android like the SoundRecorder.apk, so that's not completely unheard of. What's puzzling is why the 3G Xoomers got one that works and we didn't. If/when this is solved I will update the OP. It does work if you use bigrushdog's update method (but you gotta wipe all your data).
The Videos apk is mostly a showcase for their Video rental service that they announced Tuesday, you can still play videos in Gallery, so you're not really missing out on any major functionality at the moment.
2. The new features are cool! It's hard to compare performance since I was overclocked before and now I'm not. I love the resizable widgets. Overall it does feel like a more polished OS, they fixed a whole bunch of little itty bitty issues here and there. I can't really think of any downsides to the upgrade, it just feels like a step in the right direction. I'm definitely looking forward to see where Honeycomb development goes in the future.
I have installed this update over my rooted wifi only 3.0. It worked great, i did get a boot loop and was forced to wipe in recovery (luckily i did a titanium backup first), apart from that it went through no problem.
I haven't used the browser extensively yet, but it does seem more stable, hasn't crashed yet and the overall browser seems much better, especially the thumb menu from labs.
Good work!!
(I have the wifi only UK version BTW)
Ok guys, so I absolutely love Hulu and other legit TV sites, some of which prohibit mobile devices based on a "flash id" similar to what you have with a User Agent string for the browser. It is based on this ID that it prohibits mobile phones from accessing content such as hulu and HBO (I think?). With this mod your phone will appear as though it is a PC running flash and I believe it also modifies your version number to be something like 99.9.999.99 for sites that try and check the version number. I also must make sure to give credit where credit is due. Credit goes to imneveral0ne who posted the modified lib files in the Thunderbolt forums http://forum.xda-developers.com/show...6#post12433036.
His mod stopped working because Gingerbread (and 10.3) copies the lib files from the APK itself back into the lib folder (/data/data/com.adobe.flashplayer/lib/) on boot, thus require the mod be redone every reboot. I simply took his mod, wrote a simple script that installs the hacked lib files to /data/flash/ at first for storage, modifies permission of /data/data/com.adobe.flashplayer/lib/ so that it can be written to by the script, and also installs a "run on boot" script at /system/etc/init.d/01-fixflash.sh which will copy the hacked lib files from /data/flash to /data/data/com.adobe.flashplayer/lib/. It also adds Hulu Bookmark app (1.0) to /data/app.
REQUIREMENTS:
Kernel with init.d support (most custom kernels with root support) and root
Busybox (for running the copy commands. If you don’t have it, install ‘busybox installer’ from the market once you are rooted)
Root explorer (recommended, not required)
NOTE: I have developed this file FOR gingerbread.
INSTRUCTIONS:
Install latest flash player (11.1.115.12) from the market FIRST and be sure to uncheck automatic updates (and don't manually either)
Make sure busybox is installed. One way to test this is to type cp –help in ADB and see if it can run the command. If it does, you’re good to go.
Next, simply flash the zip. Wipe cache/dalvik if you want (I don't believe it's necessary, although again, this is my first time and for whatever reason the script doesn't seem to want to run on its own the first time)
Upon first reboot, you MAY be lucky enough that it simply just works and you’re all set.If you still get the “Hulu not available for your platform” error, simply use either root explorer or adb to run the script for the first time manually. In root explorer, navigate to /system/etc/init.d, tap on S98fixflash and select “execute”. In ADB, navigate to /system/etc/init.d and type ‘sh S98fixflash’. Wait a sec for it to run, then try Hulu again. It should be working immediately (without a reboot required) AND the script should then run correctly on subsequent reboots.
Like I said this is my first "product" I've been able to make available to the community and am more than open to suggestions, criticisms and ideas of how I can make this script better. Enjoy guys!
EDIT: If you do have issues with the script not running on every reboot, simply install "Script Manager" from the market, navigate to /system/etc/init.d, select S98fixflash and check the "run on boot" checkbox.
NOTE: ICS Only version now (least as far as I know). May work on others, please let me and others know if it does work on GB
File is now attached to post due to multiupload being unavailable -
UPDATE 6/26/2012 for 11.1.115.12
Note: after more feedback it seems using busybox installer from the market helps if running the script, even manually does nothing.
ahh too much to do
cba
Sorry, lots of explaining. If your rooted just update flash to latest in market, uncheck auto update adobe flash, then flash the zip. Should just work like it did on my gsII.
Sent from my GT-I9100 using XDA App
A query
I was going thru your update-script. What does this line do?
Code:
set_perm(0, 2000, 0755, "/system/etc/init.d/01-fixflash.sh");
I did not find a 01-fixflash.sh in /system/etc/init.d folder, only S98fixflash?
sileshn said:
I was going thru your update-script. What does this line do?
Code:
set_perm(0, 2000, 0755, "/system/etc/init.d/01-fixflash.sh");
I did not find a 01-fixflash.sh in /system/etc/init.d folder, only S98fixflash?
Click to expand...
Click to collapse
Oops, your right. Sorry I quickly modified this script from my old one I used on my epic and forgot to change that line. Will repair and repost now...
http://www.multiupload.com/VJWDKZ23FR
compuw22c said:
Oops, your right. Sorry I quickly modified this script from my old one I used on my epic and forgot to change that line. Will repair and repost now...
http://www.multiupload.com/VJWDKZ23FR
Click to expand...
Click to collapse
No problem. I already made the necessary changes. Will help others.
Sent from my GT-I9100 using Tapatalk
Cool. Also, it did work for you after those changes correct?
Sent from my SPH-D700 using XDA App
Note: after more feedback it seems using busybox installer from the market helps if running the script, even manually does nothing.
Sent from my GT-I9100 using XDA App
update 9/5/2011 for 10.3.186.6 AND hopefully fixed data mounting issues on certain devices so it works easily on CWM on more devices
NOTE: Latest update includes a brand new flashplayer.so files freshly edited, so no more issues with youtube in the browser, and uses TRUE flash 10.3.186.6 libraries for increased performance (no longer based on 10.2)
does nothing no matter what on kh3 deodexed
I'm using it now on litening 6.1 (kh3) just fine with nymphetamine kernel. This thread is also in the epic 4g forums. Troubleshooting instructions are there a well as the op. Understand what the mod does by reading, then find out where its getting hung up. I guarantee if you read you'll find your problem. Sorry but I keep having to help people read my own posts... First guesses, reflash, check to see files were installed, run busybox installer,.try another kernel with working init.d support... Run script manually?
Nice work. Any way of getting this to work for HC on the Xoom?
Maybe, try it let me know. Our buy me a 10.1
compuw22c said:
Maybe, try it let me know. Our buy me a 10.1
Click to expand...
Click to collapse
LOL! Nah didn't work for me.
Actually I feel I remember it working fire xoom.maybe try the manual troubleshooting in the op. find and replace libflashplayer.so with what's in the zip
it won't let me even flash the file says:
E: Error in /sdcard/gb_hack_flash_hulu10.3.186.6.zip
(Status 0)
Installation aborted.
all you need to do to get it to work is to extract the libflashplayer.so from the zip the op posted and copy it to (and replace) the libflashplayer.so in
Code:
/data/flash/libflashplayer.so
and
Code:
/data/data/com.adobe.flashplayer/lib/libplayerflash.so
do this using root explorer
this also enables crackle as well
there is no need to run a script
Beautiful, tried so many things in the past, and this works beautifully! Thanks!
Um, at the risk of sounding like a complete euro-dummy: What is Hulu, what does this hack do? Perhaps a bit of description in the first post?
ogdobber said:
all you need to do to get it to work is to extract the libflashplayer.so from the zip the op posted and copy it to (and replace) the libflashplayer.so in
Code:
/data/flash/libflashplayer.so
and
Code:
/data/data/com.adobe.flashplayer/lib/libplayerflash.so
do this using root explorer
this also enables crackle as well
there is no need to run a script
Click to expand...
Click to collapse
Yes but when you reboot with 2.3 or higher it replaces those files again back to stock.
Do not ask me or anyone else on these forums about how to change your ESN! It is highly illegal! Don't do it! I will not discuss that at all in this thread.
If you have activated your Optimus V on Verizon's network, and you have any of the Optimus V Froyo roms installed, the following will show you how to mod the rom to run on Verizon smoothly. Otherwise, you won't be able to send and receive sms/mms messages, and the phone will constantly complain that it is roaming. The scope of this thread is how to mod the rom once you have already activated your phone.
Always do a backup before doing anything on this page. You will need to use root explorer or adb to install these files onto the system partition. Or you can build/mod your own rom and install it.
Using adb, you would first mount system as write-able:
Code:
adb remount
Then you would push the files to the phones with the push command:
Code:
adb push file.ext /path/file.ext
Step 1: download this file pack
Step 2: Extract the files into the same folder as adb or onto your sdcard if you are using root explorer.
Step 3:
Place apns-conf.xml inside /system/etc/
Place Phone.apk inside /system/app/
Place telephony.db inside /data/data/com.android.providers.telephony/databases/
Step 4: I've included a modded framework-res.apk from the reborn rom. If you use a different rom or if the included one does not work for you, extract the original framework-res.apk from your rom located in /system/framework/. Using winrar or 7zip, add the included eri.xml to /res/xml/. Replace the original framework-res.apk on your rom.
Step 5: Using QPST, flash the included PRL file, 52299.prl
I've been using this setup for a week now without problems. I thought I would share. I tried using the LG Vortex rom on the Optimus V, but the hardware was too different. This method should also work on the Optimus S, M, and C, but I have not confirmed.
For the CM7 roms, check here: http://forum.xda-developers.com/showpost.php?p=19992286&postcount=11
nice <3 it looks awesome
I really need to find a way to repair my esn. it reads all zeros .. please help
if it truely is all zeros,then it would not be illegal to write the phone's own esn/meid back in,but it MUST be the one on the sticker of the phone. the way to do that would be to flash a rom that lets the phone show up in diag mode. I know aospCMOD does,I don't think IHO does though. experiment and you should end up with the phone showing up as a modem. then install qxdm,if you google for it its easy to find. you need qpst also,they are both on the same page if you google for them together. once you have all that,launch qxdm,go through the menus and find communication,pick the lge diag port,then in the command box,type "spc ______"<enter>where the ______ is your SPC/MSL. you can get these using cdma workshop 2.7 which is also illegal to link here,but is easy to find,just pick the diag port,click connect,then go to the security tab and pick lg method and hit read. now back in qxdm,type "RequestNVItemWrite meid 0x_______________"<enter> where the ____ is your meid from the phone's sticker. DO NOT USE THE MEID FROM ANY OTHER PHONE OR THIS IS ILLEGAL.once that is done,which should be instant,then type "mode reset"<enter> the phone should now reboot.
Message to mods: Please do not remove this post as it does not show anyone how to change an esn/meid,it only allows them to write one in if the phone does not already have one. If the phone does already have one,this method will not work to change it,it will stay at its original.
msnuser111 said:
if it truely is all zeros,then it would not be illegal to write the phone's own esn/meid back in,but it MUST be the one on the sticker of the phone. the way to do that would be to flash a rom that lets the phone show up in diag mode. I know aospCMOD does,I don't think IHO does though. experiment and you should end up with the phone showing up as a modem. then install qxdm,if you google for it its easy to find. you need qpst also,they are both on the same page if you google for them together. once you have all that,launch qxdm,go through the menus and find communication,pick the lge diag port,then in the command box,type "spc ______"<enter>where the ______ is your SPC/MSL. you can get these using cdma workshop 2.7 which is also illegal to link here,but is easy to find,just pick the diag port,click connect,then go to the security tab and pick lg method and hit read. now back in qxdm,type "RequestNVItemWrite meid 0x_______________"<enter> where the ____ is your meid from the phone's sticker. DO NOT USE THE MEID FROM ANY OTHER PHONE OR THIS IS ILLEGAL.once that is done,which should be instant,then type "mode reset"<enter> the phone should now reboot.
Message to mods: Please do not remove this post as it does not show anyone how to change an esn/meid,it only allows them to write one in if the phone does not already have one. If the phone does already have one,this method will not work to change it,it will stay at its original.
Click to expand...
Click to collapse
thanks I will try this on my brick phone as soon as I get home.
thanks it work. thanks a billion.
how do I get M.Ip settings in QPST Service programming to stick. they always revert back to original.
not working on bumblebee rom
mereed1977 said:
not working on bumblebee rom
Click to expand...
Click to collapse
if you're having problems connecting with qxdm/qpst, try booting into recovery first.
you can also restore your first stock backup and the pst's can talk while it's turned off but still plugged into the pc.
freddysam has been a God-send..He has helped me with SOOO much pertaining to all of this..I just wanted to publicly let it be known that this guy is AWESOME and SUCH A HUGE HELP!!! Thanks again bro!!!
Thanks to freddysam, I found that this was possible and I now have another Optimus V but it is on the Verizon network via Page Plus Cellular. However, instead of using the package freddysam posted here, I have built an up-to-date ROM from the IHO/CM repo hybridized for OV on the Verizon network. It is working fine for me without any issues. Instead of going through steps 1-4, you can just flash the following ROM (updated 02/22/2012)
http://www.mediafire.com/?emblkx8bb2bcoc1
MD5sum: ab4290cdccc249a5766458841d6e2565
You can check the MiRaGe build at IHO Wiki. This is the same build with VZW mods. If you also want the theme for MiRaGe ROM for VZW, it is here. Don't use the theme on the Wiki.
You still need step 5 to flash the PRL using QPST. But after that, you can update to the latest PRL by dialing to *228 and choosing option 2.
Thanks especially to Blarf and BobZhome for creating the IHO repo and VM670, VS660 ROMs.
I am attempting to get an Optimus V on Page Plus but am having trouble with Step 4.
I keep getting a boot loop or frozen flash screen after I repack and load framework-res.apk
Here is where I am at:
1)Rooted stock ROM using Gingerbreak
2)Flashed Xionia Recovery
3)Made backup of stock ROM
4)Flashed the Mirage ROM posted above after clearing caches and formatting the appropriate partitions
5)Get stuck at splash screen during boot. Sometimes it goes into a loop if I wait long enough
6)Tried using Xionia to fix boot loop, does not work
7)Tried installing the Mirage ROM in this thread using IHO_Recovery (BobZHome update for new Optimus V), still loops.
Alternatives I have tried:
1)Flashed IHO_Recovery
2)Installed BobZHome CM7 ROM. It works fine.
3)Replaced files in BobZHome CM7 ROM with the files in this thread. Everything went fine until step 4, then I would freeze at splash screen on boot.
4)Attempted to unpack/replace eri.xml/repack framework-res.apk from BobZHome CM7 ROM. Again freezes/loops at splash screen.
Any suggestions?
depthsounder said:
I am attempting to get an Optimus V on Page Plus but am having trouble with Step 4.
I keep getting a boot loop or frozen flash screen after I repack and load framework-res.apk
Here is where I am at:
1)Rooted stock ROM using Gingerbreak
2)Flashed Xionia Recovery
3)Made backup of stock ROM
4)Flashed the Mirage ROM posted above after clearing caches and formatting the appropriate partitions
5)Get stuck at splash screen during boot. Sometimes it goes into a loop if I wait long enough
6)Tried using Xionia to fix boot loop, does not work
7)Tried installing the Mirage ROM in this thread using IHO_Recovery (BobZHome update for new Optimus V), still loops.
Alternatives I have tried:
1)Flashed IHO_Recovery
2)Installed BobZHome CM7 ROM. It works fine.
3)Replaced files in BobZHome CM7 ROM with the files in this thread. Everything went fine until step 4, then I would freeze at splash screen on boot.
4)Attempted to unpack/replace eri.xml/repack framework-res.apk from BobZHome CM7 ROM. Again freezes/loops at splash screen.
Any suggestions?
Click to expand...
Click to collapse
Try wiping the partitions several times more and flashing the MiRaGe ROM over again. I had the same trouble with a new OV and it worked after trying three-four times. I have an OV with new screen and used BobZhome's recovery, see under the heading "Alternatives" in the IHO Wiki.
Success! (Sort of )
The files in this thread do work on CM7, I just could not just copy them into the respective folders without errors. Here is how I got them to work.
Warning, it took alot of rebooting and reflashing backups to figure this stuff out, make a nandroid backup before you attempt to replace the system files.
1. Follow steps 1 and 2 in OP
2. Download NinjaMorph or other app that can unpack/repack apk files. These instructions were written for NinjaMorph.
3. Copy files from Step 3 onto phone memory (I used /system), change permissions to rw-r--r--:
- Read:User,Group,Others
- Write:User
- Execute:None
If these files are not set to the correct permissions then apps will start force closing when the files are replaced.
4.MOVE (not copy) files to the folders in OP
- Place apns-conf.xml inside /system/etc/
- Place Phone.apk inside /system/app/
- Place telephony.db inside /data/data/com.android.providers.telephony/databases/
This method would not work for framework-res.apk for me, I had to rebuild the framework-res.apk that came on CM7 with the eri.xml file from the framework-res.apk in the OP. Instructions for doing so follow.
5. Rename the framework-res.apk from the OP to something else, I used VZWframework-res.apk. Open Ninjamorph, start new project and point it to the file you just renamed. It will unpack the apk into a folder on your sdcard called /sdcard/AndroidThemes/workspace. It will ask you to select a file you want to change, back out because we will do that in the next step.
6. Create a new project in Ninjamorph, this time point it to /system/framework/framework-res.apk, it will unpack this apk and ask you to select a file you want to change. Select res/xml/eri.xml, it will then ask you which file to replace it with. Point it to /sdcard/AndroidThemes/workspace/VZWframework-res/res/xml/eri.xml, note that i used VZWframework-res, your folder will be whatever name you chose in Step 5 above.
7. Select finish project, it will repack framework-res.apk and overwrite the existing framework-res.apk in your phone.
8. Reboot Phone. If your phone reboots fine and apps don't start force closing it worked! You should see a change in the taskbar, roaming should not show when the network is Verizon Wireless if you have installed the prl as described by the OP.
I still did not have MMS working at this point and even though my phone didn't say it was roaming, Cell Connectivity Tracker indicated that it was in a roaming state and data would not work without enabling roaming data. The following steps fixed these issues:
9. Move the attached Mms.apk file to /system/app Ensure that the permissions are rw-r--r-- on the file before you move it.
10. Make a copy of your original build.prop and save it on your sdcard (you are making backups this whole time right?) Rename the build.prop.txt in this post to build.prop and move it into /system/ Ensure that permissions are rwxr-xr-x
Both of the files in this post came from the VZW MiRaGe ROM that mrg666 posted above, I did not alter them and full credit goes to him for creating them, I just made them easier to access.
edited out the following due to the help from bigsupersquid and BobZHome (thanks!)
Some Notes:
-While this method got the files onto my Optimus V running CM7.2_RC0 by BobZHome without crashing it, I still do not have mms working.
-I replaced the Mms.apk in my system/app/ directory with the one from the MiRaGe VZW in hopes to fix my mms issues, but no luck.
-Even though the taskbar does not show roaming, if I go into the phone status menu it still says roaming even though I am on the Verizon Wireless network.
-I believe the above issue can be traced to the fact that my phone still thinks it is a Virgin Mobile device. If I run STMurray Cell Connectivity Tracker it gives me "Sim provider name (MCC+MNC): Virgin Mobile" in the log results.
Does anyone know which system file holds the provider information? I never activated this phone on Virgin Mobile, so I can only assume that the setting came from the CM7 ROM I installed.
/system/build.prop
thanks for the pointer to Ninjamorph.
Add/change the following in system/build.prop
ro.cdma.home.operator.alpha=Verizon
ro.cdma.home.operator.numeric=310004
ro.HorizontalVVM=true
Thanks so much for your help guys. I have everything working now including mms and data without roaming.
The tip about build.prop seemed to be the last piece of the puzzle.
I changed the settings above, but still had indications of roaming; I ended up using the entire build.prop from the MiRaGe VZW ROM and it works fine now.
I also noticed that my data usage was dominated by "dialer and dialer storage" before I fixed this roaming issue. Dialer still uses an uncomfortably large amount of data, but it isn't the 20Mb/day that it used yesterday, more like 1Mb/day now. The dialer data usage issue doesn't seem to be fully understood from what I could find; maybe my experience above is a clue.
So I am going to try and switch my optimus v details over to a samsung epic 4g, which will leave my optimus v useless. I was wondering if I could use an old verizon lg flip phone as a donor to the optimus v just for talk and text no data (i am aware mms wont work..)
My youngest brother is on my parents verizon plan and wants a smartphone but they wont pay for the data. I was thinking I could give my phone to him and make the optimus v appear as a dumbphone on the verizon network with just talk and text w/ wifi for internet. I am not asking help on HOW to do it, just do you guys think it would work?
brooksyx said:
So I am going to try and switch my optimus v details over to a samsung epic 4g, which will leave my optimus v useless. I was wondering if I could use an old verizon lg flip phone as a donor to the optimus v just for talk and text no data (i am aware mms wont work..)
My youngest brother is on my parents verizon plan and wants a smartphone but they wont pay for the data. I was thinking I could give my phone to him and make the optimus v appear as a dumbphone on the verizon network with just talk and text w/ wifi for internet. I am not asking help on HOW to do it, just do you guys think it would work?
Click to expand...
Click to collapse
I use one OV on Verizon through Page Plus Cellular prepaid plan. Everything works (data, mms ...). I just disable data since it eats all of the money quickly. I went to Canada two weeks ago, it was also roaming there and I could call back US.
mrg666 said:
I use one OV on Verizon through Page Plus Cellular prepaid plan. Everything works (data, mms ...). I just disable data since it eats all of the money quickly. I went to Canada two weeks ago, it was also roaming there and I could call back US.
Click to expand...
Click to collapse
Good to know that it can work without data. But what I am wondering is if can i switch it with the esn and meid of my old dumbphone and not put in any of the data password/settings. All I want is talk and text on it so my brother won't get charged data and verizon would think he was using the dumbphone not a smartphone. He is part of my parents family plan.
Hello guys!!! After just receiving my amazing SGS2 i began flashing ROMs like a maniac just like any other of my phones xD and i was beginning to greatly fall deeply in love with both CM9 and AOKP but one thing which just really got under my skin was the DPI issues. Well ive done a bunch of research and i believe if you follow my steps all issues will be gone
Firstly, DO NOT SET DPI TO 160!!!!!!!
You must use a DPI of 161 or higher. I use 162.
Why? Well its cause anything lower and ICS thinks the phone is actually a tablet. Which is where a lot of the issues lie. But anyhow to the fix!
Easiest and permanent fix:
MARKET FIX
1. Download LCD Density Modder Pro from the market.
2. Set your desired DPI level
3. Click "Save as system DPI" allow device to reboot.
4. Once rebooted open up LCD Density Modder Pro again
5. Click "Fix Market Compatibility Issues"
6. Download both Modded play store AND GSF apk
7. Follow instructions....
8. Install both mods.
9. After a reboot everything should be working grand
PHONE FORCE CLOSE FIX
1. Simply visit ME and follow that thread to fix the phone. I used the latest phone.apk and have no issues
****VERY IMPORTANT FINAL STEP****
REBOOT TO RECOVERY, SELECT ADVANCED, SELECT FIX PERMISSIONS, REBOOT SYSTEM and enjoy!
Fix without LCD Modder Pro (For those who are cheap xD)
1. Change DPI using LCD Modder or editing build.prop
2. Download "hacked" market from attachment (I just googled this from when i had my HD2)
3. Using a root explorer or adb, navigate to /system/app and check to see what your market name is (Mine was Phonesky.apk) not sure if its universal though.
4. Rename attached file to whatever your market file is if not already Phonesky.apk
5. DELETE old Phonesky.apk
6. Copy the attached file to the /system/app directory
7. Reboot to recovery, and once again FIX PERMISSIONS (See above for a how to)
Well both methods work swell for me Its just the second method doesnt stick forever, and after awhile you must go into "Apps" setting and Clear the market cache. I guess there is something with the GSF mod that makes it stick. Not sure. But everything is working for me now and im a happy camper!
Any issues, feel free to post in here or PM me thanks all for looking! AND OF COURSE! HIT THANKS TO ANYONE WHO HELPS YOU!