Hi, I had bought the LG L9 P765 a few days ago.
Yesterday, I rooted the phone using the LGPwn.apk, which was a success
and also, I tried installing recovery using the LGRecovery.apk, which was mentioned to be working for p765
After rooting, I removed the system launcher and some other apks.
Today, i was trying to get in to recovery using the (Vol Down + Home + Power) key combination
but instead of getting in to recovery, the phone did a hard-reset.
But, now, since the home launcher is missing (I think this is the problem), the set up wizard
closes with an error saying something like, "...closed unexpectedly" and restarts the whole setup process.
I tried connecting the phone to laptop, but adb does not show any device.
Is there a way I can get the phone working again without flashing an entire rom?
I'm on Ubuntu and it's currently really difficult for me to get a windows system,
and that is kinda troubling me.
Thanks.
void00 said:
Hi, I had bought the LG L9 P765 a few days ago.
Yesterday, I rooted the phone using the LGPwn.apk, which was a success
and also, I tried installing recovery using the LGRecovery.apk, which was mentioned to be working for p765
After rooting, I removed the system launcher and some other apks.
Today, i was trying to get in to recovery using the (Vol Down + Home + Power) key combination
but instead of getting in to recovery, the phone did a hard-reset.
But, now, since the home launcher is missing (I think this is the problem), the set up wizard
closes with an error saying something like, "...closed unexpectedly" and restarts the whole setup process.
I tried connecting the phone to laptop, but adb does not show any device.
Is there a way I can get the phone working again without flashing an entire rom?
I'm on Ubuntu and it's currently really difficult for me to get a windows system,
and that is kinda troubling me.
Thanks.
Click to expand...
Click to collapse
Did you ever get into CWM before do factory reset? Factory reset don't remove it from your phone. Try power on your phone when it viberate quickly press Vol+ and Home. If yes, maybe you can put a flashable zip for some apps you removed in sdcard and flash it back.
artit said:
Did you ever get into CWM before do factory reset? Factory reset don't remove it from your phone. Try power on your phone when it viberate quickly press Vol+ and Home. If yes, maybe you can put a flashable zip for some apps you removed in sdcard and flash it back.
Click to expand...
Click to collapse
Thanks for your reply. I tried your suggestion and I got in to recovery.
Unfortunately, this is stock recovery and not CWM.
But the good news is that I can use adb.
But I can't push apps in to the /system/app folder since i'm getting a permission denied error.
I installed a launcher using the adb install command but the phone is still stuck in setup wizard.
Could you also please give me the list of default apps that comes with l9.
Any way to push apps to the system/app folder?
Thanks.
void00 said:
Thanks for your reply. I tried your suggestion and I got in to recovery.
Unfortunately, this is stock recovery and not CWM.
But the good news is that I can use adb.
But I can't push apps in to the /system/app folder since i'm getting a permission denied error.
I installed a launcher using the adb install command but the phone is still stuck in setup wizard.
Could you also please give me the list of default apps that comes with l9.
Any way to push apps to the system/app folder?
Thanks.
Click to expand...
Click to collapse
Oh sorry I forget that LGRecovery.apk cannot use with Vol+/home. Did you install busybox and while your phone boot up "back" and "home" button flashing? While it flashing press Vol- to get into recovery.
For adb, you cannot push files into /system without remount it in read/write mode first. And to remount it you need root permission. I don't think it'll work but you can try
$ su
# mount -o rw,remount /system
Here is my phone /system/app list
- AppBox.apk
- AppBoxBridgebin.apk
- AppManSettingHiddenbin.apk
- ApplicationsProvider.apk
- BackupRestoreConfirmation.apk
- Bluetooth.apk
- BluetoothServices.apk
- CameraApp.apk
- CertInstaller.apk
- ChromeBookmarksSyncAdapter.apk
- ChromeWithBrowser.apk
- CompatibilityMode.apk
- DefaultContainerService.apk
- DrmProvider.apk
- DrmService.apk
- FaceLock.apk
- FmRadio.apk
- FontServer.apk
- GMS_Maps.apk
- GalleryLG2.apk
- Gmail.apk
- GmsCore.apk
- GoogleBackupTransport.apk
- GoogleCalendarSyncAdapter.apk
- GoogleContactsSyncAdapter.apk
- GoogleFeedback.apk
- GoogleLoginService.apk
- GooglePartnerSetup.apk
- GoogleServicesFramework.apk
- GoogleTTS.apk
- HTMLViewer.apk
- HiddenMenu.apk
- HiddenSIMUnlockManu.apk
- HiddenWVTest.apk
- HomeSelector.apk
- InputDevices.apk
- KeyChain.apk
- LGAlarmClock.apk
- LGBrowser.apk
- LGCalculator.apk
- LGCalendar.apk
- LGCalendarProvider.apk
- LGContacts3.apk
- LGContactsProvider3.apk
- LGDefaultAccount.apk
- LGDownloadProvider.apk
- LGDownloadProviderUi.apk
- LGDrm.apk
- LGEIME.apk
- LGHome3.apk
- LGInstallService.apk
- LGPartnerBookmarksProvider.apk
- LGPhone_2c_JB.apk
- LGSettings.apk
- LGSettingsProvider.apk
- LGSetupWizard.apk
- LGSystemServer.apk
- LGSystemUI.apk
- LGUniTelephonyProvider3.apk
- LinkBackup.apk
- LocMgrPD.apk
- LocMgrPT.apk
- LocMgrProvider.apk
- LockScreen3.apk
- LockScreenSettings.apk
- MediaProvider.apk
- MediaUploader.apk
- Music2.apk
- MusicPlayer.apk
- MusicWidget.apk
- NativeLiveWallpapersPicker.apk
- NetworkLocation.apk
- PackageInstaller.apk
- PermissionToAccessLgeApi.apk
- Phonesky.apk
- PlusOne.apk
- QuickMemo3.apk
- SetupWizard.apk
- SharedStorageBackup.apk
- StreamingPlayer.apk
- Street.apk
- SystemBackupService.apk
- Talk.apk
- TaskManager.apk
- UniMessagebin.apk
- UserDictionaryProvider.apk
- Velvet.apk
- VideoPlayer.apk
- VoiceRecorder.apk
- VoiceSearchStub.apk
- VpnDialogs.apk
- WAPPushManager.apk
- WapService.apk
- WeatherThemebin.apk
- WeatherWidget.apk
- YouTube.apk
- com.lge.shutdownmonitor.apk
You should not remove following app
- LGSystemUI.apk
- SetupWizard.apk
- LGSettings.apk
- LGSettingsProvider.apk
- LGSetupWizard.apk
artit said:
Oh sorry I forget that LGRecovery.apk cannot use with Vol+/home. Did you install busybox and while your phone boot up "back" and "home" button flashing? While it flashing press Vol- to get into recovery.
For adb, you cannot push files into /system without remount it in read/write mode first. And to remount it you need root permission. I don't think it'll work but you can try
$ su
# mount -o rw,remount /system
Click to expand...
Click to collapse
I was able to push Home.apk to /system/app and chmod it to 644
But the problem still persists.
I tried pressing vol down when the buttons blinked and it took me to safe mode.
I'm unsure what to do now.
[strke]Btw, can you tell me the list of apks that comes default in L9?[/strike]
Thanks, didn't see the post update
Thanks.
UPDATE:
I have all those apks and odex file intact and i have not removed any of them.
I am unsure why the SetupWizard is faiing. Adb still not working when phone's switched on.
The Home.apk i pushed doesnot have any odex flle btw.
void00 said:
I was able to push Home.apk to /system/app and chmod it to 644
But the problem still persists.
I tried pressing vol down when the buttons blinked and it took me to safe mode.
I'm unsure what to do now.
[strke]Btw, can you tell me the list of apks that comes default in L9?[/strike]
Thanks, didn't see the post update
Thanks.
UPDATE:
I have all those apks and odex file intact and i have not removed any of them.
I am unsure why the SetupWizard is faiing. Adb still not working when phone's switched on.
The Home.apk i pushed doesnot have any odex flle btw.
Click to expand...
Click to collapse
Which step it fail. During setup wizard there're 2-3 apps in that process. I think they're LGSetupWizard, LGSettings and GoogleLoginService.
LGHome3 is not required to complete that setup wizard.
artit said:
Which step it fail. During setup wizard there're 2-3 apps in that process. I think they're LGSetupWizard, LGSettings and GoogleLoginService.
LGHome3 is not required to complete that setup wizard.
Click to expand...
Click to collapse
It fails in the last step.
It says done I have to press the final button
and once I press the last button, it closes saying that it has stopped unexpectedly
void00 said:
It fails in the last step.
It says done I have to press the final button
and once I press the last button, it closes saying that it has stopped unexpectedly
Click to expand...
Click to collapse
So LGHome3 is your problem. Please upload both LGHome3.apk and LGHome3.odex to your phone. Or you can upload any Home application because I've try it on my phone.
- Delete LGHome3.apk
- Do Factory reset
- Complete setup wizard
- My phone has Xperia Home, so after press "Done" in setup wizard Xperia home show up as my home.
artit said:
So LGHome3 is your problem. Please upload both LGHome3.apk and LGHome3.odex to your phone. Or you can upload any Home application because I've try it on my phone.
- Delete LGHome3.apk
- Do Factory reset
- Complete setup wizard
- My phone has Xperia Home, so after press "Done" in setup wizard Xperia home show up as my home.
Click to expand...
Click to collapse
I don't have LGHome3.apk in the system/app folder.
I had pushed a Home.apk which is actually a renamed Apex launcher
But when I restarted, it didn't work
Btw, would it be possible to upload the lghome3 apk and odex file, just so that I could check if that's the problem
void00 said:
I don't have LGHome3.apk in the system/app folder.
I had pushed a Home.apk which is actually a renamed Apex launcher
But when I restarted, it didn't ork
Click to expand...
Click to collapse
Your Home.apk is not work in your phone. I also try to delete all my home app and setup wizard fail to complete its process. It just start over again. Please upload a working home app to your phone. It's good to try to upload original LGHome3.apk and .odex to boot your phone up first. Then you can try to switch to apex later.
artit said:
Your Home.apk is not work in your phone. I also try to delete all my home app and setup wizard fail to complete its process. It just start over again. Please upload a working home app to your phone. It's good to try to upload original LGHome3.apk and .odex to boot your phone up first. Then you can try to switch to apex later.
Click to expand...
Click to collapse
Do you know where I can find the files?
I have downloaded the LGHome3.apk but I cannot find the odex file anywhere
UPDATE:
Thank you very much for the support!
Adding the LGHome3.apk did the job!
Didn't need the odex file
Big thanks again. I'm really relieved given that I bought the phone yesterday!
void00 said:
Do you know where I can find the files?
I have downloaded the LGHome3.apk but I cannot find the odex file anywhere
UPDATE:
Thank you very much for the support!
Adding the LGHome3.apk did the job!
Didn't need the odex file
Big thanks again. I'm really relieved given that I bought the phone yesterday!
Click to expand...
Click to collapse
Fine. You should install busybox to make CWM work and start backup your data.
artit said:
Fine. You should install busybox to make CWM work and start backup your data.
Click to expand...
Click to collapse
Is there a link or a guide to install CWM on P765?
Or will I have to flash an entire rom?
Thanks.
Your phone bootloader is lock so you can only use artas lgrecovery. But you should install busybox app from market to make recovery work. And you cannot flash any custom rom while bootloader is locked.
Sent from my Nexus 7 using XDA Premium HD app
Your phone bootloader is lock so you can only use artas lgrecovery. But you should install busybox app from market to make recovery work. And you cannot flash any custom rom while bootloader is locked.
Click to expand...
Click to collapse
Thanks I'll try that.
Related
Here is the Deoxed DI01 system. I have flashed this and made sure it works.
EDIT: If your camera is force closing, please refer to page 4.
******If you want the Android Stock Lockscreen on the Deodex System, download the attachment at the bottom named "Android_Stock_Lockscreen.zip" and flash it through clockwork recovery. (NOTE: Only use this on a deodex'ed phone)
I have also opt_png'ed and zip_align'ed all the apk's, as well as the framework-res and twframework-res.
Keep in mind that since I optimized the framework-res and twframework-res, that it will reapply them, therefore if you have a theme, it will take it back to stock.
I spent a great deal of time creating an update-script for the flashable zip, and I hope you guys enjoy it as it will make applying much simpler. Check bottom for instructions.
Apps Deodex'ed:
AccountAndSyncSettings.apk
ApplicationsProvider.apk
audioTuning.apk
BackupAssistant.apk
BluetoothOPP.apk
BluetoothServices.apk
BluetoothTestMode.apk
Brightness.apk
Browser.apk
BuddiesNow.apk
CallSetting.apk
Camera.apk
CameraFirmware.apk
CarHome.apk
CertInstaller.apk
ClockPackage.apk
Contacts.apk
ContactsProvider.apk
DataCreate.apk
DeskHome.apk
DialerTabActivity.apk
Divx.apk
Dlna.apk
DownloadProvider.apk
DrmProvider.apk
DrmUA.apk
DualClock.apk
DualClock2.apk
Dun.apk
Email.apk
FactoryTest.apk
FlashPlugin.apk
FlashSVGPlayer.apk
FullbatPopup.apk
Gallery3D.apk
GlobalSearch.apk
GoogleSearch.apk
GpsSetup.apk
HiddenMenu.apk
HTMLViewer.apk
HwCodec.apk
InfoAlarm.apk
InputEventApp.apk
JobManager.apk
Keytracer.apk
LatinIME.apk
lcdtest.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
LogsProvider.apk
MagicSmokeWallpapers.apk
MediaProvider.apk
Memo.apk
Mms.apk
MobileAP.apk
MusicPlayer.apk
MyFiles.apk
PackageInstaller.apk
Phone.apk
PhoneCrashNotifier.apk
PhoneErrService.apk
PhoneInfo.apk
PicoTts.apk
PVWmdrmFactoryReset.apk
PVWmdrmService.apk
SamsungMtp.apk
SamsungSetupWizard.apk
SamsungWidget_AnalogClock1.apk
SamsungWidget_AnalogClock2.apk
SamsungWidget_AnalogClock3.apk
SamsungWidget_AnalogClock4.apk
SamsungWidget_CalendarClock.apk
SamsungWidget_DigitalClock1.apk
SamsungWidget_DigitalClock2.apk
SamsungWidget_FeedAndUpdate.apk
SamsungWidget_ProgramMonitor.apk
SamsungWidget_WeatherClock.apk
SecurityProvider.apk
serviceModeApp.apk
Settings.apk
SettingsProvider.apk
shutdown.apk
SisoDrmProvider.apk
SnsAccount.apk
SnsProvider.apk
SoundPlayer.apk
SoundRecorder.apk
TATLiveWallpapersAurora.apk
TATLiveWallpapersBlueSea.apk
TATLiveWallpapersConnection.apk
TATLiveWallpapersDandelion.apk
TATLiveWallpapersFlow.apk
TATLiveWallpapersForest.apk
TATLiveWallpapersLayersOfLight.apk
TATLiveWallpapersLuminescence.apk
TATLiveWallpapersOceanWave.apk
TATLiveWallpapersSpark.apk
TelephonyProvider.apk
TouchWiz30Launcher.apk
TouchWizCalculator.apk
TouchWizCalendar.apk
TouchWizCalendarProvider.apk
TtsService.apk
UserDictionaryProvider.apk
VideoPlayer.apk
VisualizationWallpapers.apk
VisualVoiceMail.apk
VoiceRecorder.apk
VpnServices.apk
VVMService.apk
WlanTest.apk
WriteandGo.apk
Jars Deodex'ed:
am.jar
android.policy.jar
android.test.runner.jar
bmgr.jar
com.blockbuster.lib.jar
com.cequint.platform.jar
com.google.android.gtalkservice.jar
com.google.android.maps.jar
com.pv.extensions.jar
com.pv.PVWmdrmClient.jar
com.samsung.device.jar
core.jar
ext.jar
framework.jar
framework-tests.jar
ime.jar
input.jar
javax.obex.jar
libmobileap.jar
monkey.jar
pm.jar
sec_feature.jar
seccamera.jar
sechardware.jar
services.jar
svc.jar
twframework.jar
FIRST AND FOREMOST, DO A NANDROID BACKUP JUST IN CASE.
(I am not responsible for what happens to your phone, I tested this extensively and everything was fine.)
Instructions:
1. Download DI01_Deodex_CW.zip, and place it on your SD card.
2. Go into Rom Manager and reboot into Clockwork Recovery.
3. Do a Nandroid backup
4. Scroll down and select "install zip from sdcard"
5. Select "choose zip from sdcard"
6. Scroll down and select "DI01_Deodex_CW.zip"
7. Scroll down to yes and select.
8. After it is finished, go back to top menu and select reboot.
9. It will stick on the Verizon boot screen for at least a few minutes, don't panic, and it will also go to a black screen for another 30-60 seconds after the VZW screen.
10. Done.
Edit: If you are having problems with the main download link, try any of these 7 mirrors: http://www.multiupload.com/D48J71QJUS
Enjoy.
Sounds great... now that we're deodexed, are we gonna run into any issues removing apps from the phone.
ALSO: Can you maybe add a list of the apps that are safe to delete and not worry about.
Sweet, downloading now.
I assume this includes root, and are there any bing remains?
Also does this flash the whole /system or just /system/app and /system/framework?
Will I need to reinstall all my apps after this?
stanrc said:
Sweet, downloading now.
I assume this includes root, and are there any bing remains?
Also does this flash the whole /system or just /system/app and /system/framework?
Will I need to reinstall all my apps after this?
Click to expand...
Click to collapse
lol You had to be rooted to this lol and bing is gone thats the point of this rom remove all of verizons bloatware. and your apps might be on there
stanrc said:
Sweet, downloading now.
I assume this includes root, and are there any bing remains?
Also does this flash the whole /system or just /system/app and /system/framework?
Will I need to reinstall all my apps after this?
Click to expand...
Click to collapse
This doesn't include root nor remove/add bing since that file didn't have an odex.
What this does is, push the listed apk's and jar's to system/app, and system/framework, while also deleting all the odex files that will be left over.
Your files and settings will not be reset, nothing will be reset.
I know that, I'm already rooted and have removed as much bing as I can. Thats why I asked.
frostman89 said:
This doesn't include root nor remove/add bing since that file didn't have an odex.
What this does is, push the listed apk's and jar's to system/app, and system/framework, while also deleting all the odex files that will be left over.
Your settings will not be reset, nothing will be reset.
Click to expand...
Click to collapse
Great, thanks for clarification. Exactly what I needed to know.
Apps are still there guys not a data wipe
Works great thx Frost
Nice work frost, sorry I didn't get to test it last night. Looks like you got it dialed. Again good job.
Sent from my SCH-I500 using XDA App
Getting a F/C on bootup everytime... "The application DRMContentLauncher (process com.sec.android.app.drumula) and needs to close blah blah blah." Is there a way to make this go away or can we delete it?
Same here, I was just going to rename it to something else.
Is looks like there is DrmUA that didn't get deodexed.
I ended up just deleting all the DRM stuff... not sure if it's a bad idea. No issues yet. Are you planning on releasing a custom rom version at all? Possibly one maybe heavily optimized and stripped of all the unnecessary bloat and make that stuff possibly like add-ons for those that really want it? Just a thought.
Hmm never had FC on that thing. Were you guys on DI01 or without the full update applied?
I never applied that update, but I did however deodex my old system first, then applied the newer DI01 deodex on top of that. Damn complications...
frostman89 said:
Hmm never had FC on that thing. Were you guys on DI01 or without the full update applied?
I never applied that update, but I did however deodex my old system first, then applied the newer DI01 deodex on top of that. Damn complications...
Click to expand...
Click to collapse
I had not applied the update in any way before installing this.
I am on DI01, and the same thing is happening with me. I only received the force close once though. I went into Root Explorer and there was a DRM with an .odex still there, just moved all the DRM apps to disabled and all is good so far. What is that for anyway, sounds important
What are the benefits to deodexing the fascinate? Will it make the phone faster of what?
What are the benefits to deodexing the fascinate? Will it make the phone faster? Clear up system space?
I know this doesn't include root...but do we lose root? I just want to make sure before modding.
tats_06 said:
I know this doesn't include root...but do we lose root? I just want to make sure before modding.
Click to expand...
Click to collapse
Nope, root remains
zachchen1996 said:
What are the benefits to deodexing the fascinate? Will it make the phone faster? Clear up system space?
Click to expand...
Click to collapse
I believe it'll make theme-ing easier.. It will clean up a bit of space.
It will technically make it slower, but it might be so slight you can't tell a difference. It won't make it faster.
Ok (after rooting) here is how I installed GApps (Market, Google Framework, etc) on the Nook Tablet, as well as the steps I took to stabilize everything...
1. Downloaded GApps package from goo-inside.me and extracted files.
2. Deleted the setupwizard.apk file from the set of extracted files (in the system\app folder).
3. Copied "system" folder from extracted files to tablet via USB.
4. Used Root Explorer to remount /system and copy files into their designated locations, and also set permissions (644) on all copied apk's in /system/app folder.
5. Rebooted.
6. Ran the market, signed in with my Google account, and downloaded/installed Superuser. Ran the binary update within the app.
7. Install any additional apps from Android Market.
8. Profit.
Known issues...
1. If setupwizard.apk ends up on your tablet you will not be happy.
2. A factory reset is recommended after installing GApps (though probably not necessary).
3. Not all apps show in the Market. Perhaps a build.prop tweak will fix this???
Enjoy!!!
this is a second good news after rooting!
anlong:
Use either wireless adb found here: https://market.android.com/details?id=siir.es.adbWireless
or use debugging toggle found here: http://code.google.com/p/secure-set.../detail?name=ADBWidget-0.2-alpha.apk&can=2&q=
^ instructions for that:
Download ADBWidget.apk
Copy ADBWidget.apk to /system/app (you can use root explorer or something.)
Add ADBWidget to your home screen
Anlog,
I was able to get SuperUser installed following the directions on the other discussion! Thanks for much for all your hard work.
Working on getting Google Apps installed right now.
Update: Well I have SuperUser on my Nook, but whenever I try to copy anything to \system\app it tells me I don't have permissions. Looks like I can't get root to actually run.
run chmod 4755 /system/bin/su
which version of Gapps do I need Cyanogen 6 MDPI?
Make sure root is fully working before you try to install GApps. Use the latest ones for CM7 (I think its from August). You need to remount /system as RW before copying the files and setting permissions. Root Explorer lets you do all of that.
All of this could be done with an ADB script as well, but I won't have time to write one today. Anyone?
anlog said:
3. Not all apps show in the Market. Perhaps a build.prop tweak will fix this???
Enjoy!!!
Click to expand...
Click to collapse
Chainfire should fix it too, and youll be able to run all the tegra 2 also.
Drewmungus said:
Chainfire should fix it too, and youll be able to run all the tegra 2 also.
Click to expand...
Click to collapse
Do not install chainfire! I just tried it and it boot-looped, had to force factory restore.
Finally figured out what was wrong initially, root does not seem to work unless you manually enter commands. Attempted market setup, for some reason it is still force closing every time. Any chance someone who got it working could upload exact files they used.
bkerk25 said:
Finally figured out what was wrong initially, root does not seem to work unless you manually enter commands. Attempted market setup, for some reason it is still force closing every time. Any chance someone who got it working could upload exact files they used.
Click to expand...
Click to collapse
What gapps did you use?
I used the cyanogen 7 universal gapps.
Well, I may have royally screwed up. I followed this tutorial, and I copied over the entire Apps folder from the gapps download. Now I get numerous force closes, and I have no keyboard! Any suggestion?
theundeadelvis said:
Well, I may have royally screwed up. I followed this tutorial, and I copied over the entire Apps folder from the gapps download. Now I get numerous force closes, and I have no keyboard! Any suggestion?
Click to expand...
Click to collapse
I ran into issues copying the whole folder over. I am currently running the google market though.
do everything one step at a time, install the googleframework first (from the directions on the kindle page), then do the market. I ran into the first time through the market would not actually connect so I rebooted the NT.
*note*
each time you reboot your NT you need to go in and what appears is toggle the usb debugging off then on, same with the "auto mount", and I did the unknown sources as well (not sure if this is necessary). It appears a reboot resets the flags and our menu isn't actually writing the settings so you have to toggle it.
Push comes to shove, start over with fresh reboot. It took me a few times (as it probably did others as well).
ok, so can someone who is patient tell me where I need to copy the system folder? help the feeble minded, please.....
JoeM01 said:
ok, so can someone who is patient tell me where I need to copy the system folder? help the feeble minded, please.....
Click to expand...
Click to collapse
lol, i have been struggling with this exact same thing. for those of us who cant fill in the blanks of the brief instructions we need an exact step by step please
suicideclown said:
lol, i have been struggling with this exact same thing. for those of us who cant fill in the blanks of the brief instructions we need an exact step by step please
Click to expand...
Click to collapse
It needs go in system/apps
Drewmungus said:
It needs go in system/apps
Click to expand...
Click to collapse
i'm copying from the system/apps directory (unzipped gapps files), to where on the nook?
I tried copying the files into several locations, but nada.
this is literally the last thing need to knock out for me to be set until the days of ported roms.
please. halp (lelu dallas, multipass).
Drewmungus said:
It needs go in system/apps
Click to expand...
Click to collapse
that part is clearly stated but using root explorer and getting it to mount doesnt seem to work properly on my device. I have root and superuser. titanium backup works fine. for some reason root explorer on es explorer says it fails every time
-1 Go download latest Gapps and extract the contents to your HD. There will be two folders, one of which is "system."
-2 In the system folder there will be more folders, one of which is "app." Inside of app are all the system APKs.
-3 Detele SetupWizard.apk
-4 Now copy the app folder to the root of your NT SD card via USB.
-5 Next step you need to use ADB or Root Explorer...I used Root Explorer.
-6 Open root explorer, then go to sdcard and you should see the APP folder you copied.
-7 Once there, hit menu -> multi select > then put a check mark to what you want copied then hit the copy button.
-6 now hit back untill you're back in the root
-8 Then navigate to system, and at the top you should see button "Mount RW" hit that button.
-9 Then go into the App folder, and hit paste.
-10 All the selected APKs are now in the system/app folder.
-11 Now you need to give each of the copied apps permission by long-clicking on it till a menu comes up, hit permissions, then check all the check boxes next to "Owner"
-12 After you did that to all the apps hit the "mount RO" button on top of the screen
-13 Reboot the NT.
That should do it...hopefully I havent missed anything.
I designed my wall with few widgets such as honeycomb clock and memo widget. But it won't load every time i restart my NT. Does anyone know how to fix this problem?
which launcher are you using? i am using adw launcher and dont have that problem. it is the paid version though
Yep, widgets don't work on the Nook Tablet for some people. (Actually, go launcher widgets work for me, but nothing else.) I wonder if this is a go launcher paid vs not paid issue though? Hmm.. I assumed it wasn't since it affected people with ADW launcher as well (unless they also had Go Launcher installed, just not using it).
http://forum.xda-developers.com/showthread.php?t=1357009&highlight=widget
Some people fixed it with a go launcher update or downgrade, some with not using homecatcher, some with adding 160dpi fixes to their build.prop file. The only one I haven't tried for me was the 160dpi edits, and nothing else has fixed widget issues for me.
Actually, a recent post I haven't tried is moving go launcher to the system folder. *tries*
edit: Yep, that fixed it. Or at least my non-go launcher widget is still there after one reboot, whereas previously it wasn't.
Thanks guys!!
ffwalrus's post helped me to solve the problem!
So this seems to have worked for me on my Nook Tablet. Using Go Launcher 2.66 and Home Catcher to re-purpose the "n" button. Go Launcher is set as default upon boot, and upon hitting the "n" button. The 160 dpi fix mentioned above didn't work for me, and I was having this issue on all 2.65 and 2.66 of Go Launcher. This workaround seems to have fixed it for me. I got the initial idea from this post http://forum.xda-developers.com/showthread.php?t=1360036
Using Root Explorer or similar tool move your alternate launcher APK from /data/app to /system/app. Change the permissions to 777 (all 3 rows checked in root explorer). Then restart, and you should be good. I have restarted numerous times now, and had no widget problems.
Step-by-Step Directions:
Open Root Explorer
Browse to /system
Click Mount R/W button
Navigate to /data/app
Long Press launcher APK file (for me it was com.gau/go/launcherex-1.apk)
Choose Move
Navigate to /system/app
Press Paste button
Long Press freshly pasted APK file
Choose Permissions
Check all the top 9 checkboxes (Read, Write, Execute for Owner, Group, Others), leave all others as they are.
Press OK
Navigate to /system
Press Mount R/O button
Restart Nook
Usual at your own risk disclaimer applies.
This method worked for me.
Thanks, worked well, widgets keep working after a reboot.
boradori said:
Thanks guys!!
ffwalrus's post helped me to solve the problem!
So this seems to have worked for me on my Nook Tablet. Using Go Launcher 2.66 and Home Catcher to re-purpose the "n" button. Go Launcher is set as default upon boot, and upon hitting the "n" button. The 160 dpi fix mentioned above didn't work for me, and I was having this issue on all 2.65 and 2.66 of Go Launcher. This workaround seems to have fixed it for me. I got the initial idea from this post http://forum.xda-developers.com/showthread.php?t=1360036
Using Root Explorer or similar tool move your alternate launcher APK from /data/app to /system/app. Change the permissions to 777 (all 3 rows checked in root explorer). Then restart, and you should be good. I have restarted numerous times now, and had no widget problems.
Step-by-Step Directions:
Open Root Explorer
Browse to /system
Click Mount R/W button
Navigate to /data/app
Long Press launcher APK file (for me it was com.gau/go/launcherex-1.apk)
Choose Move
Navigate to /system/app
Press Paste button
Long Press freshly pasted APK file
Choose Permissions
Check all the top 9 checkboxes (Read, Write, Execute for Owner, Group, Others), leave all others as they are.
Press OK
Navigate to /system
Press Mount R/O button
Restart Nook
Usual at your own risk disclaimer applies.
This method worked for me.
Click to expand...
Click to collapse
Help me please. I think i accidentaly pasted into /system instead of /stystem/app and now i do not have goluancher. I am back to Nook UI.
---------- Post added at 12:54 AM ---------- Previous post was at 12:00 AM ----------
Okay i got it...just in case someone else makes a similar mistake and needs this help:
i went to browser and installed amazon app store and then installed root exlplorer (had to pay again 3.99 alas). Then I was able to move it from /system to /system/app.
Now my widgets are there everytime i reboot. Awesome...thanks again.
boradori said:
Thanks guys!!
ffwalrus's post helped me to solve the problem!
So this seems to have worked for me on my Nook Tablet. Using Go Launcher 2.66 and Home Catcher to re-purpose the "n" button. Go Launcher is set as default upon boot, and upon hitting the "n" button. The 160 dpi fix mentioned above didn't work for me, and I was having this issue on all 2.65 and 2.66 of Go Launcher. This workaround seems to have fixed it for me. I got the initial idea from this post http://forum.xda-developers.com/showthread.php?t=1360036
Using Root Explorer or similar tool move your alternate launcher APK from /data/app to /system/app. Change the permissions to 777 (all 3 rows checked in root explorer). Then restart, and you should be good. I have restarted numerous times now, and had no widget problems.
Step-by-Step Directions:
Open Root Explorer
Browse to /system
Click Mount R/W button
Navigate to /data/app
Long Press launcher APK file (for me it was com.gau/go/launcherex-1.apk)
Choose Move
Navigate to /system/app
Press Paste button
Long Press freshly pasted APK file
Choose Permissions
Check all the top 9 checkboxes (Read, Write, Execute for Owner, Group, Others), leave all others as they are.
Press OK
Navigate to /system
Press Mount R/O button
Restart Nook
Usual at your own risk disclaimer applies.
This method worked for me.
Click to expand...
Click to collapse
thx,this worked for me
Voyaging said:
Help me please. I think i accidentaly pasted into /system instead of /stystem/app and now i do not have goluancher. I am back to Nook UI.
---------- Post added at 12:54 AM ---------- Previous post was at 12:00 AM ----------
Okay i got it...just in case someone else makes a similar mistake and needs this help:
i went to browser and installed amazon app store and then installed root exlplorer (had to pay again 3.99 alas). Then I was able to move it from /system to /system/app.
Now my widgets are there everytime i reboot. Awesome...thanks again.
Click to expand...
Click to collapse
I'm not 100% but if you had access to standard launcher you could have used the search function to load up your original file explorer (I always use es file explorer, works a bit better in some cases than root explorer and it's 100% free), then you could have moved your software back to the correct place. I think you can even find market using search if you needed to install.
This works beautifully. Thanks so much!
Widgets are working after reboots again. I even left a couple failed widgets in place and they were restored without having to rebuild all my home screens
I agree that ES explorer is easier to use and being free doesn't hurt either.
If I do this fix will Go Launcher still update properly?
---------- Post added at 03:09 PM ---------- Previous post was at 02:56 PM ----------
I would actually recommend creating a symbolic link to the file instead of moving it. this will ensure that any changes and updates are made to the file in its original location.
I've verified that this works. follow all the steps, except instead of moving the file create a link in system/app that points to the apk in data/app.
How do you create a link with root explorer?
I use esexplorer and when I open the file manager it show me only the sd card file. How can I open the file system?
nooknut said:
How do you create a link with root explorer?
Click to expand...
Click to collapse
you long tap on the file and select "link to this file". A button will appear that says "create link"...or something like that.
Ok. Thanks. Guess that was rather "noob" of me. Should've just tried first. Thanks!
Strange, when I create the link, the system folder will not allow me to revert back to R/O. Stays in R/W mode. Is that do to the link? Is it an issue?
I've tried:
- the 160dpi fix
- getting rid of home catcher
- moving golauncher + all widgets to /system/apps and changing the permissions
Nothing has worked.
Any other workarounds out there? Would be eternally grateful.
widgets disapear
I used the link file method with root explorer, and when I rebooted there were no widgets on my screens. There were also no problem loading widget boxes either. When I tried to replace the widgets I found that the widgets were still there but invisible. When I long pressed on the screen I got the re size/delete box. I was able to delete and replace them.
I just recently pulled the GO Launcher and other apps out of the System\Apps folder, figured there was no real reason to have them their. I also updated GO launcher at the same time. I thought it was the update, that stopped the widgets on reboot, will try moving GO Launcher back to system\apps folder. I also moved all the GO themes and GO locker .APKs, should they get put into the system\apps folder as well. I am also having issues with GO Locker not coming up on reboot. does any body have an answer for GO locker?
ChillFactorz said:
I just recently pulled the GO Launcher and other apps out of the System\Apps folder, figured there was no real reason to have them their. I also updated GO launcher at the same time. I thought it was the update, that stopped the widgets on reboot, will try moving GO Launcher back to system\apps folder. I also moved all the GO themes and GO locker .APKs, should they get put into the system\apps folder as well. I am also having issues with GO Locker not coming up on reboot. does any body have an answer for GO locker?
Click to expand...
Click to collapse
I have my launcher and beautiful widgets in system\apps folder and it fixed my issues. It has nothing to do with the update.
Sent from my Nexus S using Tapatalk
HMG10 said:
I have my launcher and beautiful widgets in system\apps folder and it fixed my issues. It has nothing to do with the update.
Click to expand...
Click to collapse
I appreciate your response about GO Launcher, my question was about GO Locker. The GO Locker app turns off it's lock screen after a reboot, only the system lock screen is their. Again my question is, will moving GO Launcher app to the system\apps folder fix the GO Locker app issue? or should I move all the GO Apps, GO Themes, GO Widgets, GO Keyboard etc. .apks, to the system\apps folder to fix issue? I am a person who likes to know why as well as how. I already know how, and it's an easy fix, I just find it helpful to know as much of the why as possible. This gives me the tools to solve other issues later, and the knowledge to help others to.
I asked this once before, don't remember if I ever got an answer; If you create a symbolic link in the system/apps folder, will it have the same effect as copying the original file?
Hey,
Is it possible to install that Launcher on CyanogenMod rom or is the Xperia framework mandatory ?
I tried several posts, including serajr's great work but it doesn't appear as a Launcher option in CM9. It's installed right but it doesn't show up, even after cleaning the apps data.
Is this achievable or should I just quit ?
Thanks !
Take a custom ROM zip, under /system/app/ find "home.apk" and ADB push it to your phone to /system/app/
Make sure it has right permissions. Restart phone.
When it boots up, press middle(home) key. If it works, it should ask you what launcher you wanna use.
If it doesn't work, well.... you tried
1. copy com.sonyericsson.facebook.proxy_1.xml on /system/etc/permissions/ and change permissions to rw-r--r--
2. copy com.sonyericsson.facebook.proxy_1_impl.jar on /system/framework/ and change permissions to rw-r--r--
3. reboot
4.(optional) from recovery flash v3_ICS_Xperia_Mini_Corners_Home_Update.zip from here
5. done
If you don't have these files:
com.sonyericsson.facebook.proxy_1
com.sonyericsson.facebook.proxy_1_impl
Thanks. I already tried flashing those files and they were installed properly. I guess I should try to push them indeed...
Hello!
DannyBiker said:
Thanks. I already tried flashing those files and they were installed properly. I guess I should try to push them indeed...
Click to expand...
Click to collapse
So did you succeed in doing it? The reason I am asking is that I have been struggling for several days, but still cannot get the "4 corners" ("Corner docks") home screen.
I used root explorer to move some system apk & its corresponding odex file from /system/apk to sdcard. I rebooted and found that I have moved some essential app like the stock dialer (it wasn't possible to figure out from the apk name). So now the dialer was gone. I then moved them back from sdcard to /system/app using root explorer thinking that it would undo the mess.
However the apps didn't come back, for example the dialer. The phone still tells me that there is no dialer.
What do I need to do?
Maybe you copied framework or something that dialler need to work... Try put bac all files. If that doesn't help see if the dialer is inn apps.
Gregrin said:
Maybe you copied framework or something that dialler need to work... Try put bac all files. If that doesn't help see if the dialer is inn apps.
Click to expand...
Click to collapse
I didn't move anything from any other directory. I moved back each and every file to /system/app that I had moved from it earlier. Still no luck.
I didn't delete anything in this process. I don't see dialer in app drawer either.
Reboot?
Sent from my GT-N7000 using Xparent Skyblue Tapatalk 2
Markuzy said:
Reboot?
Sent from my GT-N7000 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Yes, umpteen number of times.
Fix permissions. if u copied everything back to original location, it should work. then remove ONLY unwanted apps
RavinduSha said:
Fix permissions. if u copied everything back to original location, it should work. then remove ONLY unwanted apps
Click to expand...
Click to collapse
Yes, you are so right.
The apk permissions have screwed up after all the moving. I issued ls -l command in adb shell and this is what I found out.
-rw-r--r-- 1 root root 3973 May 7 2012 HTMLViewer.apk
-rw-r--r-- 1 root root 8784 May 7 2012 HTMLViewer.odex
----rwxr-x 1 system sdcard_r 562553 Feb 9 04:31 LatinIME.apk
----rwxr-x 1 system sdcard_r 327896 Feb 9 04:31 LatinIME.odex
-rw-r--r-- 1 root root 14569 May 7 2012 LiveWallpapersPicker_gles20.apk
-rw-r--r-- 1 root root 21392 May 7 2012 LiveWallpapersPicker_gles20.odex
LatinIME.apk is the keyboard with screwed up permission.
Now how do I fix it? What command do I issue?
fix permissions in recovery. or in connectbot or another shell program:
chown root:root /system/app/*.apk /system/app/*.odex
chmod 644 /system/app/*.apk /system/app/*.odex
reboot
You can also change permissions in Root Explorer itself. Hold down on the files, choose permissions and tick the first column and the first box of the second one. Leave the rest blank and press ok. That's it. If it still doesn't show, reboot. Fixing permissions in recovery does exactly this, but for all files in /system/app, /data/app and /data/data. Every time you copy something to /system or /data, you have to set the right permissions. Either in a root explorer app, adb shell, terminal emulator or fixing permissions in recovery.
LatinIME is the stock Android keyboard btw.
Sent from my Desire HD using xda premium
calisro said:
fix permissions in recovery. or in connectbot or another shell program:
chown root:root /system/app/*.apk /system/app/*.odex
chmod 644 /system/app/*.apk /system/app/*.odex
reboot
Click to expand...
Click to collapse
Issued the above commands. They all now show the same as others and are back.
Unfortunately the dialer still doesn't appear. Which apk is the dialer? My phone has gingerbread.
sashank said:
LatinIME is the stock Android keyboard btw.
Click to expand...
Click to collapse
You are right. LatinIME is the keyboard. That too had got screwed up. But by changing permission, now its back.
However as I mentioned above the dialer is still absent. Under all applications, the dialer shows up. But not in drawer.
Is there any android application or windows tool to help identify which apk corresponds to which android application. Some apk files have no bearing to the actual application name. Hence all this mess happened.
Well if you open the apps folder in a root explorer, the icons of all the apps will show. So you can identify from there. It works this way in Solid Explorer for me. Also in system apps most of the apps are named according to what they are. Example, dialer is Phone.apk, contacts are Contacts.apk etc. For other Play Store downloaded apps, which names starting with com.xxxxx, you can see their icons too.
Dialer is Phone.apk in Gingerbread. The screenshot I've put below is of the /system/app folder in Solid Explorer. I think even Root Explorer shows icons like that.
Sent from my Desire HD using xda premium
sashank said:
Well if you open the apps folder in a root explorer, the icons of all the apps will show. So you can identify from there. It works this way in Solid Explorer for me. Also in system apps most of the apps are named according to what they are. Example, dialer is Phone.apk, contacts are Contacts.apk etc. For other Play Store downloaded apps, which names starting with com.xxxxx, you can see their icons too.
Dialer is Phone.apk in Gingerbread. The screenshot I've put below is of the /system/app folder in Solid Explorer. I think even Root Explorer shows icons like that.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
I can see two apks in my phone with dialer icon.
Phone.apk (& Phone.odex)
TelephonyProvider.apk (& TelephonyProvider.odex)
How do I get back the dialer? This is a dual sim phone and only the stock dialer gives the option to select sim before dialing. None of the market dialers provide this option.
phone.apk is the file.
I like using fix permissions from recovery. it fixes every permission within few seconds.
RavinduSha said:
phone.apk is the file.
I like using fix permissions from recovery. it fixes every permission within few seconds.
Click to expand...
Click to collapse
I have CWM v5.0.2.8. Pls let me know how to fix permissions from recovery.
ontherocks62 said:
I have CWM v5.0.2.8. Pls let me know how to fix permissions from recovery.
Click to expand...
Click to collapse
advanced section. look through. it should be self explanatory.
ontherocks62 said:
Issued the above commands. They all now show the same as others and are back.
Unfortunately the dialer still doesn't appear. Which apk is the dialer? My phone has gingerbread.
You are right. LatinIME is the keyboard. That too had got screwed up. But by changing permission, now its back.
However as I mentioned above the dialer is still absent. Under all applications, the dialer shows up. But not in drawer.
Is there any android application or windows tool to help identify which apk corresponds to which android application. Some apk files have no bearing to the actual application name. Hence all this mess happened.
Click to expand...
Click to collapse
the dialer is Phone.apk
calisro said:
advanced section. look through. it should be self explanatory.
Click to expand...
Click to collapse
Fixed permission. Still dialer doesn't appear. :crying:
ontherocks62 said:
Fixed permission. Still dialer doesn't appear. :crying:
Click to expand...
Click to collapse
reflash the rom. easy peasy. next time careful what you delete! sry guy.
if u have a backup just restore only system partition
RavinduSha said:
if u have a backup just restore only system partition
Click to expand...
Click to collapse
I have a backup. Unfotunately, I took a backup after messing up. So after re-flashing it with the backup, it boots in the messed up state.
I downloaded one gingerbread Phone.apk yesterday. I renamed the Phone.apk and Phone.odex in my phone to Phone.apk.bak & Phone.odex.bak. Then copied the downloaded Phone.apk to /system/app. Then fixed permissions via recovery and rebooted.
To my horror, not only did the dialer didn't appear, but also the phone wouldn't detect the sim cards. It would say no connection available...
So Phone.apk is affecting other stuff too. So I deleted the new Phone.apk and renamed the .bak to its original names, fixed permissions via recovery and rebooted. The phone still wouldn't detect the sim cards.
Then I went back to recovery, cleared Dalvik cache & user data, and performed clear data & factory reset. After reboot, the phone started detecting the sim cards again.
So this leads me to believe that something else other than permissions has a role to play.