**NOTE FOR VEGAN TAB USERS** Steps 1-5 are no longer necessary for you, as the build.prop file in your /system directory has a working market fingerprint out of the box. Just apply the standard Market Fix (steps 6-8) and you are good to go.
I've seen several people complaining that the "full market" we had on G Tablet after the established market fixes wasn't quite full. Well, I've solved that problem, through a mixture of reading what others have done with other devices and experimentation. I will not promise that this gives you *everything*, but I do believe it gives you apps that otherwise required the release-keys status. Some of the apps you get may of course not work. But several applications I looked for before (TV.com for example, with streaming CBS video content) were not available with the previous market fix, and are now available with this fix. In fact, TV.com even works, except for a very minor video glitch in the upper left corner of the screen, and it's a cool app to get some quick streaming video content going on your G Tablet.
**NOTE** I take no responsibility for you screwing up your G Tablet. Please backup your system in Clockwork Recovery before doing any of this!
**EDIT** Removed unneccessary steps after feedback in this thread. Process is now very simple. Edited step 1 to clarify you need paid version of Root Explorer.
Here's how to do it:
0) Backup in Clockwork Mod. Please. I don't want you mad at me if this messes up your ROM.
1) Get the paid version of Root Explorer installed on your G Tablet. Apparently the free version lacks a text editor. If you only have the free version, the text editing step will need to be done in a separate program, or you will need to copy build.prop to your desktop, edit it there, and copy it back. Or use adb to push an edited build.prop to your tablet. Just buy Root Explorer though, it makes this very easy.
2) Browse in Root Explorer to /system. Then click on Mount R/W.
3) Long click on build.prop and click on Open In Text Editor.
4) Scroll down to the line ro.build.fingerprint=....
You are going to replace that with the following text:
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys
5) Now you are going to click on Save and Exit. And then remount the /system directory as R/O.
6) Now you are going to re-do the original Market Fix. I used the simple version illustrated here: http://www.youtube.com/watch?v=7l-nySibzeA&feature=related First, make sure Market is running, and browse around in it for a few seconds. If you don't do this, there may be no cache to clear and for some reason the market fix may not work. Then, go to Settings->Applications->Manage Applications->Running and scroll down to Market. Then hit Clear Cache, followed by Force Stop **DO NOT CLEAR DATA FOR MARKET, JUST CACHE**. Then go back, scroll down to Google Services Framework, hit Clear Data, then Force Stop.
7) Now try starting Market again and you get the famous Market Error. Now shut down the G Tablet, then turned it back on. Wait for Wifi to connect to your network before doing anything! I forgot to do that on the first try, so I rebooted again, waited for wifi to connect this time.
8) Now restart Market again. It seems to have sourced the fingerprint from build.prop somewhere in steps 6-7. Searches for previously missing apps now show up. Voila! A truly full market!
And steps 6 and 7 can almost certainly be replaced by the equivalent steps using Titanium Backup that I know a lot of people have been using, particularly with TNT Lite. I am running ZPad 2.2 here, so YMMV with TNT Lite. Please keep me informed if this works/doesn't work for you if you try it!
Credit goes to: Paul at Modaco for hacking on the Advent Vega and making the Market work fully on that device and for coming up with a working build.prop for the Advent Vega, Roebeet for inspiring me to look at the Vega ROM stuff with his current work on the VEGAn ROM, Rothnic for his excellent work on the ZPad ROM that I'm currently using. Basically, I'm just hacking and slashing here, this wasn't any sort of rocket science.
Paul from Modaco is awesome -- and you are as well, for making this post!
Any apps in particular that you found after this, that were missing before? I might want to try this on my device. Thanks again!
FWIW my Nexus One running a CM 6.0 nightly from 2 days ago has
ro.build.fingerprint=google/passion/passion/mahimahi:2.2.1/FRG83/60505:user/release-keys
Note the more up-level version (2.2.1) and build (FRG83). I haven't tried this on my GTab yet but I will as soon as I can get it up and running.
roebeet said:
Paul from Modaco is awesome -- and you are as well, for making this post!
Any apps in particular that you found after this, that were missing before? I might want to try this on my device. Thanks again!
Click to expand...
Click to collapse
The only specific things I can tell you off the top of my head are TV.com which I know wasn't there because I searched for it a few hours ago. Also, I tried searching Market for Handcent before and found 14 or 15 results, and after this process I was able to retrieve 24 results.
There were a bunch of random apps I saw in the Top Apps list that I don't remember seeing earlier today. So that was enough to convince me that most of the missing 10-20% of apps are there now.
And thanks for the compliment, especially coming from the guy who made the G Tablet useful!
short/y said:
FWIW my Nexus One running a CM 6.0 nightly from 2 days ago has
ro.build.fingerprint=google/passion/passion/mahimahi:2.2.1/FRG83/60505:user/release-keys
Note the more up-level version (2.2.1) and build (FRG83). I haven't tried this on my GTab yet but I will as soon as I can get it up and running.
Click to expand...
Click to collapse
I'm sure that will work too, though the FRF91 build string seems to match the existing data in the ZPad ROM at least. I'm guessing the two signatures will produce essentially identical Market results.
rcgabriel said:
I'm sure that will work too, though the FRF91 build string seems to match the existing data in the ZPad ROM at least. I'm guessing the two signatures will produce essentially identical Market results.
Click to expand...
Click to collapse
Yeah. I may be somewhat overoptimistic going with FRG83. The build and version numbers identify the version of the system code so apps may read them and make some assumptions as to certain API characteristics. We're probably closer to FRF91 than FRG83 on TnT Lite.
This one worked ok for me
ro.build.fingerprint=samsung/SGH-T849/SGH-T849/SGH-T849:2.2/FROYO/UVJJB:user/release-keys
ewitte said:
This one worked ok for me
ro.build.fingerprint=samsung/SGH-T849/SGH-T849/SGH-T849:2.2/FROYO/UVJJB:user/release-keys
Click to expand...
Click to collapse
Is that from the Samsung Tablet? That may be closer to what we're really running.
short/y said:
Is that from the Samsung Tablet? That may be closer to what we're really running.
Click to expand...
Click to collapse
Yes this is Galaxy Tab. Probably better a Tegra tab once a full market one comes out.
I did the following:
1) Edited build.prop as described in step 4, rebooted and searched for tv.com - no results
2) I preformed the edits in step 4a, rebooted and searched for tv.com - no results
3) I stopped Market & Google Services Framework & wiped Google Services Framework, rebooted after getting Market Error, waited for wifi and opened Market to search for tv.com - no results.
I can't say if it works. I haven't had trouble finding apps, but I can't find tv.com before or after the steps above. Perhaps, I missed something.
Wait!!!! It does work. I tried again after posting and it's there! Thanks!
Is it possible to post the TV.com app? I don't want to do the mod but would love that app!
Great post man worked like a charm, I can get my slingbox app from the market now.
Edit: dammit I can't get the downloaded sling client to launch even after trying it many times which usually worked.
I'm going to give it a shot but being a newbie I'm not clear on this step:
5) Now you are going to click on Save and Exit. And then remount the /system directory as R/O
Will "remount as r/o" be an option to select at this point? If not, can you provide more detail.
The rest of the mod is easy enough to follow.
Thanks.
jdnyc said:
I'm going to give it a shot but being a newbie I'm not clear on this step:
5) Now you are going to click on Save and Exit. And then remount the /system directory as R/O
Will "remount as r/o" be an option to select at this point? If not, can you provide more detail.
The rest of the mod is easy enough to follow.
Thanks.
Click to expand...
Click to collapse
No worries its just a button on root explorer, download it and you will see it fairly quick.
NM..........
Fixed
Thanks works great
Can't get this to work. When I toto building.prop there s no option to open it in text editor. Only toopen as text. But then there is no way to edge the sentence.
ewitte said:
This one worked ok for me
ro.build.fingerprint=samsung/SGH-T849/SGH-T849/SGH-T849:2.2/FROYO/UVJJB:user/release-keys
Click to expand...
Click to collapse
Replaced this line only, did the Market fix via Settings and it worked like a charm. And Swype continues to work as well.
-=Sent from my ViewSonic G Tablet using Tapatalk=-
Worked perfectly thanks! Steps 4a and 6 are not necessary as you precicted
Related
Link: http://forum.xda-developers.com/showpost.php?p=9172522&postcount=2058
Many thanks to supagforce, for this find!!
I personally tested this on TnT Lite 1.02, with no issues in the default browser (other than high memory use, but I guess that's to be expected).
11/29/10 EDIT: Newer Flash version out, GLES optimized. See this post for details: http://forum.xda-developers.com/showpost.php?p=9476506&postcount=26
Doesn't work on cm6
akodoreign said:
Doesn't work on cm6
Click to expand...
Click to collapse
Good point. For cm6.1 beta2, just alter the build.prop as follows:
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
and reboot.
This was not my fix, and I take no credit for it - it was in the big thread. I believe that the forthcoming beta 3 is going to have this change built-in.
roebeet said:
Good point. For cm6.1 beta2, just alter the build.prop as follows:
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
and reboot.
This was not my fix, and I take no credit for it - it was in the big thread. I believe that the forthcoming beta 3 is going to have this change built-in.
Click to expand...
Click to collapse
yup that was it. TY !
I can confirm it works on CM6 with the above added to the build.prop. I've done it myself.
Wants to join the party
I have been trying to days now to get this one last piece working. I have copied the flash apk to everywhere I can think of but still can't get it to install. I have tried using ADB (INSTALL_FAILED_INVALID_APK), Droid Explorer (crashes while trying to install), made sure SYSTEM was R/W, and still I am stumped.
Any ideas what else I can try? I am running CM v6.1b2.
Gbmedusa said:
I have been trying to days now to get this one last piece working. I have copied the flash apk to everywhere I can think of but still can't get it to install. I have tried using ADB (INSTALL_FAILED_INVALID_APK), Droid Explorer (crashes while trying to install), made sure SYSTEM was R/W, and still I am stumped.
Any ideas what else I can try? I am running CM v6.1b2.
Click to expand...
Click to collapse
look at the post above about the build.prop change. Btw, there's a beta3 now that does not have this issue, tmk.
Hulu
Can this be hacked to include the mod in the hulu enabled flash apk? Can they be diffed?
http://forum.xda-developers.com/showthread.php?t=688054
Thanks for all your hard work roe...
The Dude
It worked for me in stock system
roebeet
Please thank supag for me. I am not a programmer, I purchased this item so I could show my patients video and anatomy intructional pics. There is no way I would have been able to use it with out the combined team effort from all you folks.
P.S. The only change I made to the system was loading Launcher Pro.
Thanks again
Wyngnut
Gbmedusa said:
I have been trying to days now to get this one last piece working. I have copied the flash apk to everywhere I can think of but still can't get it to install. I have tried using ADB (INSTALL_FAILED_INVALID_APK), Droid Explorer (crashes while trying to install), made sure SYSTEM was R/W, and still I am stumped.
Any ideas what else I can try? I am running CM v6.1b2.
Click to expand...
Click to collapse
I am having the same problem trying to install on full vanilla. In fact, my device will not even download the rar...it fails. I had to copy it from another device....so dumb question, i assume i just need to rename the file to apk, not unrar it?
Flash 10.1 fix
I used a RAR extractor on my windows machine then side loaded the APK into SD on system. I then used ES file explorer to find the file On the internal SD and when I opened it it gave me the option to install. Install went off without a hitch.
I have stock system with no ROM changes and I loaded launcher pro which I use instead onf TapNTap. I have now viewed many Utube video's as well as movie trailers with no problems.
Hope that helps
Wyngnut
roebeet said:
look at the post above about the build.prop change. Btw, there's a beta3 now that does not have this issue, tmk.
Click to expand...
Click to collapse
My apologies for not explaining more fully. I actually have the build.prop edit in place. I tried copying the flash apk to /system as well as /system/app. My problem is that I can't get it to install. Either I get an error, the program attempting the install crashes, or nothing happens.
By the way, you mention a beta 3 of CM. Any idea where I can find it? I did a quick 'net search but came up with nothing specific for the gtablet. Guess I need to plow through the megathread again.
Any help would be greatly appreciated.
Edit: Could it be I need to fix flash prior to installing CM? I had to do that with the wifi hack before it would work. Guess I need to get another backup going just in case.
Edit (again): Never mind about Beta 3. I see in the megathread that it is in the works.
For the APK error, not sure about vanilla (never tried it). TnT Lite is 90% vanilla so I figured it should work on full stock.
I usually install with "adb install", which is how I tested it. I assumed a sideload would also work. I haven't put it in /system yet although I probably will do that when I build out TnT Lite 2.00 - that's coming next week btw, as soon as VS sends out their new firmware update and I can get my hands on it.
roebeet said:
For the APK error, not sure about vanilla (never tried it). TnT Lite is 90% vanilla so I figured it should work on full stock.
I usually install with "adb install", which is how I tested it. I assumed a sideload would also work. I haven't put it in /system yet although I probably will do that when I build out TnT Lite 2.00 - that's coming next week btw, as soon as VS sends out their new firmware update and I can get my hands on it.
Click to expand...
Click to collapse
Yeah, the ADB install just gave me an invalid APK error so I gave up there.
I may try flashing back to stock(ish) and installing from there.
Wyngnut said:
I used a RAR extractor on my windows machine then side loaded the APK into SD on system. I then used ES file explorer to find the file On the internal SD and when I opened it it gave me the option to install. Install went off without a hitch.
I have stock system with no ROM changes and I loaded launcher pro which I use instead onf TapNTap. I have now viewed many Utube video's as well as movie trailers with no problems.
Hope that helps
Wyngnut
Click to expand...
Click to collapse
+1 on that. Same setup and very easy fix. Thanks for this!
still no luck..
roebeet said:
Good point. For cm6.1 beta2, just alter the build.prop as follows:
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
and reboot.
This was not my fix, and I take no credit for it - it was in the big thread. I believe that the forthcoming beta 3 is going to have this change built-in.
Click to expand...
Click to collapse
this doesn't work for me.. in fact i opened the build.prop file and the properties were already set to the same values.. i'm running tnt lite 2.0. any suggestions?
i'm willing to even use CM if it'll mean running flash player, but so far this rom has been the most stable.
Works on the stock "out of the box" G Tablet!!
S_C_B said:
Works on the stock "out of the box" G Tablet!!
Click to expand...
Click to collapse
I am having the same problem as iksnae. I changed the Rom to TNT Lite 2.0.2 prior to loading the 10.1 Flash Player. I get Youtube videos and even Angry Birds but I can't get flash video from CNN or Hulu? Should I flash back to stock and then add flash. If so can someone point me to that thread? Every other hack has worked perfectly.
cbrownesq said:
I am having the same problem as iksnae. I changed the Rom to TNT Lite 2.0.2 prior to loading the 10.1 Flash Player. I get Youtube videos and even Angry Birds but I can't get flash video from CNN or Hulu? Should I flash back to stock and then add flash. If so can someone point me to that thread? Every other hack has worked perfectly.
Click to expand...
Click to collapse
My GTab was configured like yours. I unintalled Flash 10.1 and loaded the vanilla "out-of-the-box" Rom version. This version also had the clockwork menu so when you Flash don't panic if you see this pop up, just follow the instructions for loading the update.zip file from the /sdcard (I think it was option 2). I then side loaded Flash 10.1.apk from the PC to /sdcard and using ES File Explorer to access /sdcard, I doubled clicked on the Flash 10.1.abk to install.
Then I reinstalled TnT_Lite 2.0, flashed and then TnT_Lite 2.02 & Flashed this update.
ESPN3 works great. Also get Flash_TV from the Android Market and you now have IPTV. I am anxious to get the docking module so I can stream HDMI 1080P to my 46" LCD. No more cable, no more monthly cable bills (I do get internet 28MB/sec service).
Still looking for an optimized Nvidia Tegra 2 video media player that will take advantage of the processors embedded video encoder functions. I expect this will play HDMI 1080P movies quite nicely. Rock Player is rumored to be working on a dual core Cortex 9 version. Right now it plays using the software control option and is slow and clunky.
I believe that Flash 10.1 is optimized for the Nvidia Tegra 2 processor and it is quite nice. The streaming videos play smoothly. Not sure how they will play in HD when using the docking module and the HGMI connection to the large screen.
Best of luck. It's easy once you figured out how to do the original Flash load(s).
EKS
roebeet said:
Link: http://forum.xda-developers.com/showpost.php?p=9172522&postcount=2058
Many thanks to supagforce, for this find!!
I personally tested this on TnT Lite 1.02, with no issues in the default browser (other than high memory use, but I guess that's to be expected).
11/29/10 EDIT: Newer Flash version out, GLES optimized. See this post for details: http://forum.xda-developers.com/showpost.php?p=9476506&postcount=26
Click to expand...
Click to collapse
Thank you for this 11/29 edit pointer to the flash apk file (rename txt to API), all I have done is rooted thus far with z4root, stock TnT, and now YouTube videos work!
There's been a lot of speculation on what can and can't be removed as well as how to remove them without causing force-closes, boot loops, and other headaches. So I wrote this script that will let you disable all of the bloat with none of the hassle.
After a few prompts to find out if there's anything you want to keep that can't be replaced in the market, it will do its magic -- renaming files to a .bak extension so they are no longer recognized by Android. This will cause some system services to fail and force-close loop until you reboot (and the script reboots for you). Also included is a script that will undo all of this.
If you select every option, including the default launcher and text messaging apps (which are confirmed safe to remove without losing SMS or MMS ability or push notifications), then here's the list of apps removed:
AdService.apk, android-syncservice-app.apk, ArcVideoEditorLite.apk, BackupAssistanceClient.apk, Blockbuster.apk, BlurHome2.apk, BlurSNMessagingEngine.apk, BlurTasks.apk, BlurUpdater_VZW.apk, BooksPhone.apk, CitrixReceiver.apk, CityID.apk, Conversations.apk, DLNA.apk, DlnaSystemService.apk, FriendFeed.apk, gotomeeting-stub-1.0.74.apk, GuidedTours.apk, HelpCenter.apk, IMPresence.apk, IndexingService.apk, Kindle.apk, MessagesWidget.apk, Messaging.apk, MOTOPRINT.apk, MSExchangeService.apk, MyVerizon.apk, NewBayVault_4.2.99.36.Market.apk, NFLMobile.apk, OnlineAlbum.apk, PhotoEditor.apk, PortalStandAlone.apk, Preloaded.apk, RichLocationVzW.apk, SkypeBourbon.apk, Slackerradio.apk, SocialMessaging.apk, SocialShare.apk, StatusWidget.apk, SuggestionsProvider.apk, SuggestionsRuleCheckerCore.apk, SuggestionsServiceScheduler.apk, Swype.apk, ToggleWidgets.apk, UniversalInbox.apk, Upgrader.apk, VCAST_TONES_4_5_7.apk, VCASTMusic.apk, VCASTVideo.apk, VSuiteApp.apk, vzw_vnav_DROID3_rel_PROD_signed.apk, VZWIM.apk, VZWInstaller.apk, WeatherWidget.apk, ZumoCast_1.0.17.apk
Make sure you run these scripts using Script Manager or a comparable app and be sure to enable it to run as root or it won't have permission to make changes to /system/app.
This is version 1 of the scripts -- if any of the apps removed wind up causing problems or more are found, I'll add it to the list. I've tested the scripts back and forth myself and have tested it as much as I can without finding any issues. Also, some apps are removed without asking, such as ZumoCast or VCAST or NFL Mobile. You can find these apps in the market, so there's no point keeping them locked down in system.
Enjoy! Comments are welcome.
UPDATE 9/1/2011: fixed a typo in one of the variables (thanks everyone who reported this), added more options to keep (Swype and Car Dock Voice Commands), split into two versions -- one for the stock 5.5.959 build and 5.6.890 update (late August OTA), added a warning about removing the home screen without a launcher and that it removes the Calendar widget.
Great, but maybe it would be nice to make a y/n option for each .apk where it asks you if you want to delete that apk
script
instructions for use?
thanks
DoubleYouPee said:
Great, but maybe it would be nice to make a y/n option for each .apk where it asks you if you want to delete that apk
Click to expand...
Click to collapse
You shouldn't delete them -- we don't have an SPF yet. Someone posted the complete /system/app contents and you could restore, technically, manually, but it's a bad idea. Renaming to a .bak is completely effective.
lodisax said:
instructions for use?
Click to expand...
Click to collapse
Read the post.
You'll want to use Script Manager -- unzip the two scripts to your SD card (internal or external), launch Script Manager (free version is fine), find the script and click it, then tick on 'root' and then run the script. Follow the prompts from there.
script
thanks for the answer
psouza4 said:
You shouldn't delete them -- we don't have an SPF yet. Someone posted the complete /system/app contents and you could restore, technically, manually, but it's a bad idea. Renaming to a .bak is completely effective.
Click to expand...
Click to collapse
Yeh sorry that's what I meant.. Option to y/n rename the apk.
I'd like to use the script once I get my droid 3 but would like to 'keep' some of the apks.
DoubleYouPee said:
Yeh sorry that's what I meant.. Option to y/n rename the apk.
I'd like to use the script once I get my droid 3 but would like to 'keep' some of the apks.
Click to expand...
Click to collapse
There's Y/N for anything you'd want to keep. About 6-7 questions in total. Anything that you can't find in the market that isn't definitely bloat has a prompt.
script
script manager that you use?
I use script manager and asked me if I want to remove each apk or not.
There is a script manager that does everything automatically?
thanks for the answer
lodisax said:
script manager that you use?
I use script manager and asked me if I want to remove each apk or not.
There is a script manager that does everything automatically?
thanks for the answer
Click to expand...
Click to collapse
Please read the thread thoroughly -- I'm going to ignore obvious questions like these.
psouza4 said:
There's Y/N for anything you'd want to keep. About 6-7 questions in total. Anything that you can't find in the market that isn't definitely bloat has a prompt.
Click to expand...
Click to collapse
So what if I wanna keep DLNA, photoeditor and socialmessaging?
DoubleYouPee said:
So what if I wanna keep DLNA, photoeditor and socialmessaging?
Click to expand...
Click to collapse
Then answer 'Y' to the prompts asking if you want to keep 'DLNA' or 'social messaging'. There are plenty of photo editors in the market, so there's no prompt on that (although if you were so inclined, you could just rename the .BAK's back to their original files). I feel you haven't actually looked at the script or read my post.
psouza4 said:
I've tested the scripts back and forth myself and have tested it as much as I can without finding any issues. Also, some apps are removed without asking, such as ZumoCast or VCAST or NFL Mobile.
Click to expand...
Click to collapse
I think the ultimate test is to do factory reset and see how device will go through initialization stage. It can be surprises which are not noticeable during normal use. Without this it is kind of premature to say what is safe to delete and what is not.
serg675 said:
I think the ultimate test is to do factory reset and see how device will go through initialization stage. It can be surprises which are not noticeable during normal use. Without this it is kind of premature to say what is safe to delete and what is not.
Click to expand...
Click to collapse
Ehh I agree with you to a point, because i made the very noobish mistake of uninstalling bloat that i knew would not effect daily use; however, I did a factory reset to test a theory for krazy and learned that something I uninstalled makes the setup process FC and wont let you get to the blur launcher, luckily other launchers work and I was able to batch install via adb.
Thing is though is if the phone reboots when this stuff is renamed then it will survive a factory reset, though it may do the same thing mine has done. If it does its no big deal to load up adb and rename the files back so that you can complete the setup.
You forgot the World Clock widget in your removal script; the only clock that thinks it needs a permanently-resident service, regardless of whether it's running or not.
Xenoproctologist said:
You forgot the World Clock widget in your removal script; the only clock that thinks it needs a permanently-resident service, regardless of whether it's running or not.
Click to expand...
Click to collapse
That messes with the dock though, so I don't consider it bloat.
I know its a lot to ask... but can someone either create a comprehensive list of what each one actually does... or point us in a direction to where there already is one?
Sent from my DROID3 using Tapatalk
Seirÿu said:
I know its a lot to ask... but can someone either create a comprehensive list of what each one actually does... or point us in a direction to where there already is one?
Click to expand...
Click to collapse
Open the script in a text editor and read my comments -- it gives each one a title.
@psouza4 - nice work, it's about time someone took a more organised approach to figuring out what apks are safe to remove.
I tried to get a similar effort going here :-
http://forum.xda-developers.com/showpost.php?p=17004394&postcount=11
but the way people behave on this forum, it's like trying to herd cats.
thingonaspring said:
@psouza4 - nice work, it's about time someone took a more organised approach to figuring out what apks are safe to remove.
I tried to get a similar effort going here :-
http://forum.xda-developers.com/showpost.php?p=17004394&postcount=11
but the way people behave on this forum, it's like trying to herd cats.
Click to expand...
Click to collapse
Thanks!
Couple of notes, too:
It was asked in IRC why I'm removing 'android-syncservice-app.apk'. This service is the extra backup stuff that Verizon added on (as evidenced inside the package in /assets/system.properties you'll find several references to verizon servers for sync, like sm_connection_url=http://syncba.myvzw.com/syncml). This service doesn't do anything beneficial for you unless you really have a hard-on for Verizon's sync stuff. I've had it disabled since we achieved root and it has no affect on account sync services (contacts, gmail, calendar, reader, etc.) nor SMS/MMS push notifications, etc.
Also, a fellow PM'd me saying he got errors that variable names were invalid -- turns out he had edited the script in Windows, saved it, and that broke the UNIX-style line endings. If you're going to modify the script, use Notepad++, UltraEdit, or something that will maintain the correct line endings. Or just use an editor on the phone, such as in Root Explorer.
Thanks a bunch man, works great. About to run a benchmark to see the results!
Hi, just got a NC today. Am a total noob to Android (no smartphone) and am hoping someone can help me out. I have read and searched a bit of the posts in these NC forums, but there is just A LOT and I'm kinda lost. To start out..
After playing around with the stock 1.2 ROM for a bit, I installed the latest nightly (177) CM7 with this guide,
http://forum.xda-developers.com/showthread.php?t=1030227
Before this, I also switched to the older 1/5GB app/data partition with DeanGibson's zips via CWM. The installs are fine, although CM7's UI is thoroughly confusing. My questions are:
By installing CM7, am I also rooted as part of the process? If not, is there any additional benefit to get root?
Is ManualNooter needed if I have CM7, or is it redundant? Can I install it on top of CM7?
I can't get most apps from the Market ("your device is not compatible"). I also went to Amazon.com to try and get its AppStore app, but it gives the same error. Is this a noob issue, or is there a real problem, and is there a workaround if the latter?
What's a simple way to access network shares on my Windows network?
Is there a way to dismount & remove the microSD w/o turning the NC off?
Links would be fine. TIA for any help.
You are rooted! You might want to install clock work mod from the market... I'm not sure about the computability issue as I have never had it myself.
Sent from my NookColor using XDA Premium App
If I'm understanding this correctly, you were able to go from completely stock to CM7 without rooting with manualnooter first? I'm buying a NC next week and i was unsure root was needed to go to CM7.
You are already rooted.
Market fixes: http://forum.xda-developers.com/showthread.php?t=1255689
Sent from my LG Optimus V using Tapatalk
@sevs753
Yes, apparently the CM7 install does the root thing for you. Still not quite sure if it's needed for anything else other than allowing custom ROMs.
I'm a little flustered with Android at the moment. Trying to edit the build.prop as some others have mentioned to temp fix the market problem, only to find that I can't download ES Explorer (what others are reportedly using) to edit the file. Was going to edit it in terminal emulator & nano, but found that the soft keyboard has no cursor keys. So I found an ES Explorer apk, and now am trying to figure out how to sideload the app--I believe that's the correct lingo for Android.
I also found that many embedded flash videos don't play (Youtube does). I thought this was a done deal with 2.3 and CM7, but apparently not. Tried to download Flash 10.3 from market, but again am blocked.
Am also trying to find the parameters of what is allowable for video playback for 2.3. For HC, you can play up to 720p and high profile H264 with "reasonable" params. I've been encoding various test clips, and it looks like the max is 854x480 at baseline profile, same as with the stock ROM.
Change your LCD density to 240 and your market will start working. It makes the icons really large but you get used to it. The best way to change the density is by editing the build.prop line that is default: qemu.sf.lcd_density=161
Change that 161 to 240 and then save your build.prop and reboot. Problem should then be solved.
I edit the build.prop with root explorer (Paid version) - you have to change from r/o to r/w first, then change back to r/o after you are done editing.
Shandon84321 said:
Change your LCD density to 240 and your market will start working. It makes the icons really large but you get used to it. The best way to change the density is by editing the build.prop line that is default: qemu.sf.lcd_density=161
Change that 161 to 240 and then save your build.prop and reboot. Problem should then be solved.
I edit the build.prop with root explorer (Paid version) - you have to change from r/o to r/w first, then change back to r/o after you are done editing.
Click to expand...
Click to collapse
That's quite a jump. Most people are changing to 160 which is also a standard density.
Until you really get familiar with the CM7 and the NC, I suggest you try CM7 off uSD card.
patruns said:
That's quite a jump. Most people are changing to 160 which is also a standard density.
Click to expand...
Click to collapse
With 160 you will be clearing Market app data daily for it to keep working. 240 seems to keep working... I guess because almost all phones are set to 240.
DizzyDen said:
With 160 you will be clearing Market app data daily for it to keep working. 240 seems to keep working... I guess because almost all phones are set to 240.
Click to expand...
Click to collapse
+1 on this. I was going forever on 240 without a hiccup.
Note that ICS has also been demonstrated to change the UI depending on the density, with 160 for a tablet UI (honeycomb-ish) and 240 for phone UI (gingerbread-ish). Came across a couple references showing that density was the only thing that needed to be changed to make this happen.
I kind of suspect this may be part of why density is becoming such a big issue. It also fits with the fact that tablet-related apps show up in the market at 160 but not at 240. Perhaps Google is setting market up ahead of ICS release to handle this?
skwalas said:
+1 on this. I was going forever on 240 without a hiccup.
Note that ICS has also been demonstrated to change the UI depending on the density, with 160 for a tablet UI (honeycomb-ish) and 240 for phone UI (gingerbread-ish). Came across a couple references showing that density was the only thing that needed to be changed to make this happen.
I kind of suspect this may be part of why density is becoming such a big issue. It also fits with the fact that tablet-related apps show up in the market at 160 but not at 240. Perhaps Google is setting market up ahead of ICS release to handle this?
Click to expand...
Click to collapse
If i remember correctly this also happens on Honeycomb.
Sent from my LG Optimus V using Tapatalk
You're at the same spot I was at earlier last week. I just got my NC, and read about and made the cm7 sd card. To get market working correctly this is what I did:
- installed cm7 and gapps using this guide - http://forum.xda-developers.com/showthread.php?t=1000957
- once that was working I went to the market and got titanium backup installed
- once that's installed, I went to applications/manage/market and force closed market, cleared the cache, and uninstalled updates
- then I went to titanium and found marketupdater.apk and uninstalled it
- after that I opened market again, if force closed once but opened fine the second time. I now have the old style market and everything seems to work well.
I haven't used manualrooter, I only followed the above guide. As for unmounting the card, I have no idea. I'm probably going to keep things as they are, I really like being able to turn the NC off, take the card out, and have it back as stock.
koopakid08 said:
If i remember correctly this also happens on Honeycomb.
Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
I believe honeycomb had the capability built in but was not supposed to be enabled. Would have to dig around for links n such.
I just want to say thanks for all those who replied. I'm taking some time trying different stuff on the NC, now that I've gotten a basic handle on CM7. I'll be sure to try some of the tips & info proffered.
Re: Market issue - I tried w/ File Expert to change file.prop's attribs so I can edit them, but the changes don't take. Since the entire /system partition is RO, I'm assuming I need to remount it to RW before I can do anything to the files, per NookDev's instruction. Am further assuming I'll need to install the SDK so I can get ADB running.
@Kingston73: I'm sure there are apps that do it more efficiently, but mount/unmount SD is in Settings | Storage.
More questions:
Is there a way to not have a wallpaper and have the default black background changed to something else? I like having just a plain background.
I'm using the default browser for now. Most of the sites with embedded Flash don't work (no Flash installed). I tried installing Flash 10.3 from the Adobe site, but it gives the same error as Market's. Can 10.3 be installed into CM7 at all, or is this because of the LCD density issue (which I'll get around to fixing)?
Thanks again for all your help. Am learning both Android and CM7 as I go along.
Noob^2 said:
I just want to say thanks for all those who replied. I'm taking some time trying different stuff on the NC, now that I've gotten a basic handle on CM7. I'll be sure to try some of the tips & info proffered.
Re: Market issue - I tried w/ File Expert to change file.prop's attribs so I can edit them, but the changes don't take. Since the entire /system partition is RO, I'm assuming I need to remount it to RW before I can do anything to the files, per NookDev's instruction. Am further assuming I'll need to install the SDK so I can get ADB running.
@Kingston73: I'm sure there are apps that do it more efficiently, but mount/unmount SD is in Settings | Storage.
More questions:
Is there a way to not have a wallpaper and have the default black background changed to something else? I like having just a plain background.
I'm using the default browser for now. Most of the sites with embedded Flash don't work (no Flash installed). I tried installing Flash 10.3 from the Adobe site, but it gives the same error as Market's. Can 10.3 be installed into CM7 at all, or is this because of the LCD density issue (which I'll get around to fixing)?
Thanks again for all your help. Am learning both Android and CM7 as I go along.
Click to expand...
Click to collapse
Flash will install fine from the market if you are in the old market. It doesn't care about the density.
More questions:
Is there a way to not have a wallpaper and have the default black background changed to something else? I like having just a plain background.
Click to expand...
Click to collapse
You can set or remove wallpaper upon your will.
I'm using the default browser for now. Most of the sites with embedded Flash don't work (no Flash installed). I tried installing Flash 10.3 from the Adobe site, but it gives the same error as Market's. Can 10.3 be installed into CM7 at all, or is this because of the LCD density issue (which I'll get around to fixing)?
Click to expand...
Click to collapse
Flash 10.3 installed and worked w/o any issue with CM7.
If you can't download it directly from Market, try to sideload it.
Oh, and, recommend trying Opera browser
patruns said:
Flash will install fine from the market if you are in the old market. It doesn't care about the density.
Click to expand...
Click to collapse
Flash should install fine with the new market too, if density is at 160 (or 240) and market data is freshly cleared. It is possible that in some cases the market will update itself too quickly for the 160 fix to stick long enough to install, and this has happened to me on occasion. If installing the basic "problematic" apps (flash, facebook, repligo, maps, etc.) for the first time, would suggest working with 240 dpi to get all the apps on your nook, then revert to 160 if that is your preferred screen sizing going forward.
Thanks for the continuing tips. I did get Flash 10.3 to install via sideloading. I still can't get Market to lift its "partial-ban", since the only version I have is 3.1.3 and there is no rollback. I did manage to edit build.prop to 160, then 240, (and cleared cache) but the ban is still present. I think us Johnny-come-latelies are just a bit screwed until some shining knight comes through with a fix.
To relate my further misadventures with CM7 and Market, I'm recounting some of my steps, in hope that they'll help someone else.
Networking to Windows boxes: I used CIFS Manager, which worked straightaway. Before that, I tried the networking function of ES File Explorer and Astro (w/ SMB plugin), but they both crashed or hung.
Finding a good file manager: I tried File Expert, ES File Explorer, and Astro File Manager. They have more functions than CM7's built-in file mgr, but the built-in mgr is the fastest at reading off large directories from the network (which still isn't that fast). This is critical for me, since most of my media will be accessed via wifi.
Finding a better terminal emulator: The built-in one is kinda barebone. Looks like Better Terminal Emulator Pro is the only game in town?
Finding a better keyboard: Since I'm a commandline guy, Hacker's Keyboard fits the bill. Well, at least until my BT keyboard arrives.
Getting USB HDD/key to work: Ordered a Tekkeon TekCharge MP1550 4xAA batt pack and a Y-cable, along with a 90-degree micro-USB cable.
Install font for Viet or any language not already on CyanogenMod 7:
I have a collection of Viet songs/movies, and most of them have UTF-8 filenames. I used this below to change the font so CM7 can see the files (it's also what I used to edit build.prop). There are easier ways to do this, but here you don't need to install anything else.
1. Get DejaVu Fonts from dejavu-fonts.org (personally, I used Arial.ttf from my Windows box since I know it covers Viet)
2. Get DejaVuSans.ttf and rename to DroidSansFallback.ttf
3. Copy DroidSansFallback.ttf to root dir of SD card
4. Insert SD card into NC and mount it (Settings | Storage)
5. Run Terminal Emulator
6. Enter su (confirm when asked) (all commands case-sensitive)
7. Enter mount. Note device node & FS for /system. For CM7, it's /dev/block/mmcblk0p5 /system ext4 (ro[...])
8. Enter mount -o rw,remount -t ext4 /dev/block/mmcblk0p5 /system (node & FS must match)
9. Enter mount again to check, it should read /dev/block/mmcblk0p5 /system ext4 (rw[...])
10. Enter chmod 4755 /system/fonts/DroidSansFallback.ttf
11. Enter dd if=/sdcard/DroidSansFallback.ttf of=/system/fonts/DroidSansFallback.ttf
12. Reboot. File and partition permissions should return to default.
I found that local UTF8 filenames are recognized, but not files over the network. After some hair pulling and a bunch more Googling, I stumbled on the extra needed step.
13. Unmount the CIFS share in CIFS Manager. Long-press to edit the share, enter iocharset=utf8 in the Options box. Save and remount.
Other apps chosen: EzPDF for PDFs, Aldiko for ePubs, FBReader for Mobis, PerfectViewers for CBRs, OverDrive for library checkouts, MoboPlayer for SD MKVs (doesn't work for AVI/XviD).
To-Do's:
. Try Opera like another had suggested. The default browser is pretty limited.
. Check out some of the compilers & editors for Android.
. Find a decent office suite.
Question:
. I'm having trouble with file associations with the built-in file mgr (am assuming it is part of ADW). The association is lost after a few files, and apparently it associates all file types in the share with the single app, regardless of extension. Is this an ADW issue, or did I just miss a setting somewhere?
Noob^2 said:
Thanks for the continuing tips. I did get Flash 10.3 to install via sideloading. I still can't get Market to lift its "partial-ban", since the only version I have is 3.1.3 and there is no rollback. I did manage to edit build.prop to 160, then 240, (and cleared cache) but the ban is still present. I think us Johnny-come-latelies are just a bit screwed until some shining knight comes through with a fix.
Click to expand...
Click to collapse
Are you actually clearing the market data specifically? if you're just clearing cache (such as through rom manager), that's a completely different thing and won't fix the problem. You need to clear the application data for the market specifically.
Would be seriously odd that you couldn't get the apps. Note that if you've flashed gapps through rom manager, it should install the old market. selecting "uninstall updates" in the application manager screen for the market should take you back to that old market, but it will update very quickly unless the market updater apk is already disabled.
I believe Amazon released an update today as my KFHD just rebooted itself and turned back on with a progress bar. My question or issue is this: does an update automatically cause a rooted KFHD to lose root access? I still have access to Google Play store and a bunch of apps I could only access through root. And most of the apps still work except LMT Launcher, which is the only one that is no longer working as far as ive noticed.So all I have to do is plug back in and root my KFHD again and I should be good, right?
Version 7.3.0 is out. Here are the specs from the Amazon page:
"Support for X-Ray for Textbooks
Explore the “bones” of your textbook, and access all the most important terms and concepts, with glossary definitions and links to relevant textbook pages.
Simplified Chinese Support
In addition to the other languages offered, you can now change your device language to Simplified Chinese.
Track your reading progress with Time To Read
Kindle Fire HD 7” calculates your reading speed to let you know when you’ll finish a chapter or book.
Support for Kindle Editions with Audio/Video
You can now read books that contain audio and/or video clips.
Print Replica Textbook Enhancements
Scroll through thumbnails at the bottom of the screen to preview pages and jump quickly between chapters, and mark important notes and highlights in your Notebook for easy reference."
None of this seems overly important, but then again I do like to have the latest version as long as there is no harm to the root.
macbranson said:
I believe Amazon released an update today as my KFHD just rebooted itself and turned back on with a progress bar. My question or issue is this: does an update automatically cause a rooted KFHD to lose root access? I still have access to Google Play store and a bunch of apps I could only access through root. And most of the apps still work except LMT Launcher, which is the only one that is no longer working as far as ive noticed.So all I have to do is plug back in and root my KFHD again and I should be good, right?
Click to expand...
Click to collapse
Anything you install as a system apk will be deleted. When amazon sends an update it typically sends system.img, recovery.img and boot.img.
That is why the lmt launcher will not work because it has to be installed as a system.apk to work, same with root access since su binary is placed within the system files.
if you want to install the 2nd bootloader, you should not update. Amazon have fixed the bootloade with the update and so it dosn't work for now. i don't know, if it perhaps work with soupkit, because the insallation is a little bit different, but the resultat is the same (I could install kinelogy 1.1 after doing that).
I'm still on 7.2.1, found Wi-Fi performance/range considerably better than on 7.2.3, unless 7.3.0 improves it I won't be updating for quite some time.
This explains why I lost root and Go Launcher HD yesterday. Regained root with the same Noob Simple guide here with little more than annoyance. The file to prevent the OTA update had been moved per the guide (otacerts.zip) but think I deleted it in a cache cleaning frenzy... that will learn me
macbranson said:
I believe Amazon released an update today as my KFHD just rebooted itself and turned back on with a progress bar. My question or issue is this: does an update automatically cause a rooted KFHD to lose root access? I still have access to Google Play store and a bunch of apps I could only access through root. And most of the apps still work except LMT Launcher, which is the only one that is no longer working as far as ive noticed.So all I have to do is plug back in and root my KFHD again and I should be good, right?
Click to expand...
Click to collapse
Ouch! I got caught by this update . . . i am now running 7.30 on my KFTT 7"
Sad, since I had a nice rooted image all set up well. Unfortunately, I became a bit lazy and did not check on whether or not I had effectively disabled updates during my last restore/reflash of 7.2.3 (I had not done that ;-(
sigh! Like you, I have all my apps and the Play store working, but anything requiring root -like root explorer or TIBU, won't work until I can reroot on this version -or flashback. . . The only question is whether the root exploitation works on this new version, I am not sure any of us has tried yet. . .oh well. . here we go (again!)
EDIT: OK, I was able to re-root the same way I did before (used the tools in prokennexusa noob threads!) All back to normal!
markbc01 said:
Ouch! I got caught by this update . . . i am now running 7.30 on my KFTT 7"
Sad, since I had a nice rooted image all set up well. Unfortunately, I became a bit lazy and did not check on whether or not I had effectively disabled updates during my last restore/reflash of 7.2.3 (I had not done that ;-(
sigh! Like you, I have all my apps and the Play store working, but anything requiring root -like root explorer or TIBU, won't work until I can reroot on this version -or flashback. . . The only question is whether the root exploitation works on this new version, I am not sure any of us has tried yet. . .oh well. . here we go (again!)
Click to expand...
Click to collapse
Same root method worked, system feels about the same with tweaks installed and benchmarked similarly (7344 vs 7444 with AnTuTu)
I just can't get my launcher off of the stock one. Nothing will take.
I simply plugged my KFHD back in and re-rooted. I regained access to applications that required system access. So my LMT is working again. I didn't lose any apps as far as I've noticed. This update turned out to be a pretty minor inconvenience.
macbranson said:
I simply plugged my KFHD back in and re-rooted. I regained access to applications that required system access. So my LMT is working again. I didn't lose any apps as far as I've noticed. This update turned out to be a pretty minor inconvenience.
Click to expand...
Click to collapse
Which method did you use to root again ?
Nop update here istill in 7.2.3
Damn just got the damn update like 5 min go
Sent from my Nexus 7 using Tapatalk 2
Has anyone had any success of their launchers working correctly since the update?
I re-rooted my kindle but I'm not able to make the launchers...well launch.
geeibara said:
Has anyone had any success of their launchers working correctly since the update?
I re-rooted my kindle but I'm not able to make the launchers...well launch.
Click to expand...
Click to collapse
I'm update ver 7.3.0 normal,apex launcher and Gplay normal .Update Chrome from Gplay very good :good:
quan_1986 said:
I'm update ver 7.3.0 normal,apex launcher and Gplay normal .Update Chrome from Gplay very good :good:
Click to expand...
Click to collapse
I'm not able to move the apk files to /system/app
When I try to move it, it only moves to /System, I tried to install it in /system, but nothing works.
geeibara said:
I'm not able to move the apk files to /system/app
When I try to move it, it only moves to /System, I tried to install it in /system, but nothing works.
Click to expand...
Click to collapse
I had this issue as well - and then noticed something else that was really weird. When I tried to move to /system/app it only moved to system - but I also noticed (at least in my case) it was renaming the file by adding "app" (which was the folder name I was trying to move it to) on the front of the file name - so... GoLauncher HD.apk was being renamed appGoLauncher.apk but was landing in the /system folder instead of /system/app
So - I created a new folder called "temp" in the /System/App directory (i.e /system/app/temp) and moved the files there. Sure enough, they landed in /system/app with the the word "temp" appended to the front of the file name, so GoLauncher.apk was now tempGoLauncher.apk. However, it was in the right directory - so I then simply renamed it by removing the "temp" from the front of the name and continued with install
I still have lots of other issues though in getting it to work. It appeared to be working for a while, but has stopped again.
#3Clara said:
I had this issue as well - and then noticed something else that was really weird. When I tried to move to /system/app it only moved to system - but I also noticed (at least in my case) it was renaming the file by adding "app" (which was the folder name I was trying to move it to) on the front of the file name - so... GoLauncher HD.apk was being renamed appGoLauncher.apk but was landing in the /system folder instead of /system/app
So - I created a new folder called "temp" in the /System/App directory (i.e /system/app/temp) and moved the files there. Sure enough, they landed in /system/app with the the word "temp" appended to the front of the file name, so GoLauncher.apk was now tempGoLauncher.apk. However, it was in the right directory - so I then simply renamed it by removing the "temp" from the front of the name and continued with install
I still have lots of other issues though in getting it to work. It appeared to be working for a while, but has stopped again.
Click to expand...
Click to collapse
haha yah I noticed that too, I had files like appappappappappappapplauncher lol. Thanks this helped a lot
modmyphone said:
I just can't get my launcher off of the stock one. Nothing will take.
Click to expand...
Click to collapse
Are you going through Google Play? I used Prokennexusa' post to get the launchers back:
http://forum.xda-developers.com/showthread.php?t=2069668
Gah.. I actually tried to deactivating the manual update and some how the update still pushed through.. which really sucks cause I hard my set up perfect..hope all I have to do is reroot.. ..all that time spend for nothing
Sent from my KFTT using xda app-developers app
BmanCV-60 said:
Are you going through Google Play? I used Prokennexusa' post to get the launchers back:
http://forum.xda-developers.com/showthread.php?t=2069668
Click to expand...
Click to collapse
Actually, I tried 3 different ways.
1) I reluctantly attempted ProKennexusa's method via the KFFFirstAide tool. I say reluctantly since I'm pretty much a Nova snob. I guess luckily for me, it wouldn't take.
2) I then moved onto downloading Nova from the store. The store claimed that both installs went good, but had no option to change my launcher. Upon inspection, the Nova launcher file was nowhere to be found on the device. The pro unlocker could be found, but no the launcher.
3) Since I had a couple of older copies in Dropbox, I figured I'd try those. Usually I could install straight from Dropbox. Not last night. I could launch the install, but the Kindle wouldn't allow me to press the install button. I then just saved the file to the device and still couldn't get it to install. It wasn't until moving it to system/app that I was able to actually install it. But still, no option to set it as my launcher.
This morning, in a bit of Kindle rage, I literally rebooted the device 23 straight times pausing between boots to see what happened. On the 23rd reboot, it finally asked me which launcher to set as default. So now I finally have gotten away from the freakish kindle launcher and am back at home with Nova.
Please find at the URL below my copy of the stock ROM (Version C) for the D415, with my modifications included.
The D415 is a great phone for the price, and it came with many cool features. However, the phone still has an amateur streak running the stock ROM. Some of LG's apps are great on this phone, but some of them are downright useless for most of us. T-Mobile added their own pushy bloatware to the mix as well. The end result, as we all know, is a usually fluid, but at times clunky and awkward experience using the device. I was impressed the first day I had it, but I wanted to make it better that first day as well. I wanted to get rid of all the useless stuff, and polish it into something I wouldn't be embarrassed to pull out in front of a client. I liked a lot of what LG did here, and wanted to hold on to that, but I also wanted a few changes:
Root:
FOTAkill
SuperSU installed on first boot
Polish:
Small UI sounds changes
Boot Animation
Replaced Flashlight App (thanks to xbmi, consider a donation in the app)
Added Heads Up
Removed foo foo themes
Added Bookmarks Sync
Replaced Stock Messenger with AOSP MMS
Debloat:
LG Memo & Widget moved to user apps
LG Music & Widget moved to user apps
Visual Voicemail moved to user apps
Weather widget moved to user apps
Apps removed completely:
LG Contacts widget
TMobile TV
Lookout
CarrierIQ
Maps
Mobile Life
Streetview
Talkback
T-Mobile My Account
T-Mobile Name ID
Voice Dialer
Youtube
Amazon
Chrome
Cloud Print
Drive
Easy Home
Gmail
Google Plus
Google Calendar
Play News Stand
Play Books
Play Game
Play Movies & TV
Play Music
Google Search
Google TTS
Hangouts
Stock Calendar
To do:
AOSP Keyboard (IDK what I'm doing here yet. It's crashing when I put it in now).
Version E (need to learn how to extract KDZ)
Instructions:
Download zip to SD
Reboot to Recovery
Wipe Dalvik, cache, data, system.
Install zip
Reboot and enjoy
Thanks to @Daisuke1988 for the original flashable stock rom.
Feedback welcome in replies!
I just got this phone today. I hate it but this should make it much better. Thanks guys!!
Sent from my SGH-M919 using XDA Free mobile app
Keep poking around with it. There are a lot of hidden gems sprinkled in by lg that will really cause you to like this phone. I came off of a nexus 5 to this. I chose it for the price tag, you can't beat $7 a month and get the build quality and battery life. I would buy again. The only thing I miss is a decent camera. But the stock camera app helps with auto focus mode.
Will it work on d405?
catbro said:
Will it work on d405?
Click to expand...
Click to collapse
Good question, it would be nice
Sent from my LG-D405 using XDA Free mobile app
I guess I have to try this evening, if nobody's trying till then I will report back
If the pure stock ROM works in the 405, this one should as well. I'm not sure myself without looking it up.
I have a D41510c and when I tried to install this rom, it failed. I'm restoring a backup, but I will try again in a while.
Sorry to hear that, I tried very hard to make the cuts fine in this. Without further info I'm gonna guess the download got corrupted. The zip itself is really straightforward (simple script, boot and system imgs.) The only part I would have thought would have failed the installer was that I repacked the system IMG (saved a few hundred MBs) instead of simply unmounting it after my changes. Otherwise, if its going to break, it should be upon first boot. Let me know what happened if it doesn't work again.
jb3p76 said:
Sorry to hear that, I tried very hard to make the cuts fine in this. Without further info I'm gonna guess the download got corrupted. The zip itself is really straightforward (simple script, boot and system imgs.) The only part I would have thought would have failed the installer was that I repacked the system IMG (saved a few hundred MBs) instead of simply unmounting it after my changes. Otherwise, if its going to break, it should be upon first boot. Let me know what happened if it doesn't work again.
Click to expand...
Click to collapse
I'm re-downloading, hopefully this will work!
I can deodex this but you will have to wait till Tuesday for me to upload it. or is it already deodexed?
I had thought about it but honestly haven't learned how to yet. Was I mistaken to think the payoff would not have been that great? Either way, I can wait til Tue, I know others will want it deodexed. Thanks!
I tried again, but it failed...
E:Error executing updater binary in zip
E:Unable to mount '/system'
EDIT: I was able to boot into the rom, but it's extremely slow
Wondering if it has to do with first botched install now that it went. Were you able to format /system again? My other thought was repairing permissions. When it failed the first time, was it before "Setting permissions for root" was displayed? If so it was in the middle of flashing /system. I flashed this on mine using twrp. IDK that I will be much help but I think if we can figure out the variables Google should at least point us in the right direction...
Before I get too far down the rabbit hole can anyone confirm they have successfully flashed this and its working out for them?
jb3p76 said:
Wondering if it has to do with first botched install now that it went. Were you able to format /system again? My other thought was repairing permissions. When it failed the first time, was it before "Setting permissions for root" was displayed? If so it was in the middle of flashing /system. I flashed this on mine using twrp. IDK that I will be much help but I think if we can figure out the variables Google should at least point us in the right direction...
Click to expand...
Click to collapse
Well, I rebooted and it's faster now. I used towelroot to get root. Nohing appeared about the permissions. I was able to update the binaries using TWRP.
It's should have already had root and SuperSU installs on first boot. Did that not happen? I'm glad your phone is doing better! So many weird things going on there!
jb3p76 said:
It's should have already had root and SuperSU installs on first boot. Did that not happen? I'm glad your phone is doing better! So many weird things going on there!
Click to expand...
Click to collapse
I use ROM Toolbox Pro, and when I went to start it the first time, it said root check had failed. That's why I used towelroot. I'll continue to test things and report back to you. So far, it's pretty smooth.
Weird. Can you tell me if the SuperSU apk is to be found in /system/apps/bootup?
I'm doing a backup so i can wipe and install fresh again. I'd like to mess around with the root stuff and see if I can figure that out. Did you happen to get a listing of which files are missing?