Hi,
After changing my phone's date into the future, my G2 Touch told me there was an update available, so I told it to go ahead and apply it. When the phone rebooted it came up with this message:
E:No signature (218 files)
E:Verification failed
Installation aborted
I have nandroid installed on the phone. At least I think that's what's installed - I haven't played with any ROM stuff since November I think, when I changed the bootloader (I think - if that's what's giving me the option to do a nandroid backup now) and installed the newest T-Mobile G2 ROM.
Should the phone be able to install the OTA update, or will I have to replace the bootloader in order to get the OTA update on there? If I do have to replace the bootloader, will that require a full wipe?
James
Completely the same problem with HTC Hero after European OTA update. It has been rooted while ago (by following instructions from this forum) and now after setting up date in the future and confirming update, phone reboot and I get "Android System recovery" screen with menu and this message bellow it:
Build: CyaanogenMod v1.4 + JF
Finding update package ...
Opening update package ...
Veryfing update package ...
E: No signature (218 files)
E: Verification failed
Installation aborted.
Click to expand...
Click to collapse
I have the same problem (I did not write down the message, so I'm not sure which "Build:" was listed) .
The update fails, the phone reboots and then works under the old build. Under "settings/about phone" there is also no info about the update. Can one force the phone to download the update a second time? Would this help?
Bye
Nick
P.S. I'm running the phone in Germany over e-plus as network provider. The updates was done over a WiFi connection. The phone is not branded - was from the free market and not from a provider.
Hey,
got the same problem. At least I could extract the official OTA-update-zip to publish it here (see attachment)
There also is a "recovery.img" in the update zip, so I guess usually the OTA update will kill custom recovery bootloaders. We could replace the "recovery.img" in the zip with a hacked one before applying the update.
However first we should fix the verification error...
P.S.: Also Germany, not branded, Vodafone Network
Does anyone know if I will lose all my data if I reflash the original recovery.img onto my phone?
As I used flashrec to flash ra-recovery.img I keept all my data. So I don't belive you will lost any of your data except of your actual recovery image.
At last, we can try to flash origianl RUU, but with this we lost all our personal data.
----
I tried it. I installed flasrec.apk using ASTRO and used this app to flash the recovery.img from here mentioned/linked OTA update zip. Afterwards I changed date again and was able to install OTA Update without errors and loosing personal data. Now I'm without nandroid because of changing recovery image. Keep cool at this procedure installing these flashes takes long time in boot process - I was really near an hard reset ...
Flashing the original recovery.img should not be a problem.
However, I don't want to lose root access, and thus I will wait for the official HTC 2.1-update (hoping someone publishes it online) and then flash it by myself..
I don't mind losing root access at this moment (the reason I rooted my phone was to get wifi tethering but never got it working with a mac).
Since I am total noob with android stuff, I would highly appreciate some step by step instructions or link where I can find what to do. Thanks guys.
Hi, I've been trying to install the recovery.img from the update but I get this message with flashrec 1.1.3:
Code:
"Flash FAILED: Could not run command."
I'm using WWE 405.66 flashed with ra-recovery img 1.6.2... and the rom is rooted.
What am I doing wrong?
I can't even install ra-recovery with flashrec now and I have installed ra-recovery 1.6.2 this morning (I was using 1.5)
And yes, I know I'm going to lose ra-recovery.
rseffner said:
As I used flashrec to flash ra-recovery.img I keept all my data. So I don't belive you will lost any of your data except of your actual recovery image.
At last, we can try to flash origianl RUU, but with this we lost all our personal data.
----
I tried it. I installed flasrec.apk using ASTRO and used this app to flash the recovery.img from here mentioned/linked OTA update zip. Afterwards I changed date again and was able to install OTA Update without errors and loosing personal data. Now I'm without nandroid because of changing recovery image. Keep cool at this procedure installing these flashes takes long time in boot process - I was really near an hard reset ...
Click to expand...
Click to collapse
What was the rom you were using when you flashed the official recovery?
alvaritolalala said:
Hi, I've been trying to install the recovery.img from the update but I get this message with flashrec 1.1.3:
Code:
"Flash FAILED: Could not run command."
I'm using WWE 405.66 flashed with ra-recovery img 1.6.2... and the rom is rooted.
What am I doing wrong?
I can't even install ra-recovery with flashrec now and I have installed ra-recovery 1.6.2 this morning (I was using 1.5)
And yes, I know I'm going to lose ra-recovery.
Click to expand...
Click to collapse
Try the following:
- Copy the recovery.img to your SD card
- Turn off the phone, turn it on with Buttons "HOME"+"ONOFF" pressed such that the ra-recovery which you already have starts
- connect to your phone by cable using "adb shell"
- Then with root access you can flash the image by typing "flash_image recovery /sdcard/recovery.img"
This should do it
jamesots said:
Hi,
After changing my phone's date into the future, my G2 Touch told me there was an update available, so I told it to go ahead and apply it. When the phone rebooted it came up with this message:
E:No signature (218 files)
E:Verification failed
Installation aborted
I have nandroid installed on the phone. At least I think that's what's installed - I haven't played with any ROM stuff since November I think, when I changed the bootloader (I think - if that's what's giving me the option to do a nandroid backup now) and installed the newest T-Mobile G2 ROM.
Should the phone be able to install the OTA update, or will I have to replace the bootloader in order to get the OTA update on there? If I do have to replace the bootloader, will that require a full wipe?
James
Click to expand...
Click to collapse
hey,
I had same problem
go to All programs--> Recovery Flasher--> Restore backup
then restart and update OTA
Greetings from Zagreb, Croatia
Hey guys.
So, for those of you, who do NOT care about root for now, here's what worked for me:
1.: Download the zip-file with the OTA Update, mentioned on the first page and extract it.
2.: Connect your Hero to your PC and copy the recovery.img from the OTA onto your sdcard. Disconnect from computer.
3.: Boot your phone into the bootloader (Home + PWR).
EDIT: Now connect the phone to the pc again!
4.: open the command prompt of your pc, navigate to your Android SDK folder. (If it is not installed, download it and make sure you've got the needed drivers. Otherwise: Download them, using the Setup.exe from Android SDK)
5.: Here are the needed commands:
Code:
adb shell
$su
mount -a
flash_image recovery /sdcard/recovery.img
6.: reboot your phone after exitting the command prompt.
7.: Factory reset, reboot again
8.: And well, wait for the update-window again and be happy, now it should work
EDIT 2:
Any questions? Just leave a reply
@Revoluzifer
OK I did exactly as you explained, but having problem with su command:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
I know I know, you're going to say my phone is not rooted at all But believe me it was and some apps that require root access are there (screenshot, wifi tether etc.).
I even tried to find su cmd with find:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
But got nothing as you can see.
Ideas?
@dinke:
Which bootloader / recovery console is installed?
Means, what do you see, after booting with Home + PWR?
Also try to input $su instead of just su.
But first tell me your "hack" if any
@Revoluzifer
Thanks for quick reply
I see Android system recovery screen, not sure if this is nandroid or what but have this text on the screen with following options:
Android system recovery <2>
Use trackball to highlight;
click to select.
[Home+Back] reboot system now
[Alt+S] apply sdcard:update.zip
[Alt+W] wipe data/factory reset
[Alt+B] nandroid v2.2 backup
[Alt+R] restore latest backup
[Alt+F] repair ext filesystems
-------------------------------
Click to expand...
Click to collapse
And bellow menu there is build ID:
Build: CyanogenMod v1.4 + JF
I don't remember exact procedure that I applied for rooting hero, but I followed instructions from this forum (I can try by searching for exact thread if that may help you).
Edit: I applied root procedure by following instructions on these two links:
http://forum.xda-developers.com/showpost.php?p=4257045
http://forum.xda-developers.com/showthread.php?t=559613
That sounds just perfect
CyanogenMod 1.4 is exactly the same recovery console i have had before.
(Btw, Hero is not officially supported by CM anymore, had a nice discussion yesterday in cyanogen IRC )
So, try to use $su instead of su, that's what I typed and it all worked just great.
But you definitely first booted into bootload and then connected the phone to your pc again?
Tell me if this worked for you, please...
Greetz,
Sven
dinke said:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
Click to expand...
Click to collapse
Forget about the "su". You are already root.
(You can see this, as there's a '#' in front)
Just do the mounting and flashing
Oh... You're right, nerdture... didn't see the #
I *think* I've tried mount no matter of missing 'su' cmd and it didn't work either but will try again as soon as I manage to find some cable to connect hero with macbook (no longer nearby windows machine but have sdk installed on mac so should be working as well)
Revoluzifer said:
But you definitely first booted into bootload and then connected the phone to your pc again?
Click to expand...
Click to collapse
Yes
Hi !
I've tried to flash a rom, so as usual, I went to recovery (razrbootstrap.apk), made my backup. But when I rebooted my phone, it stuck on boot Screen.
When I go back to recovery , I don't see restore option.
Please help, and sorry for my English.
---------------------------RE-EDIT- PROBLEM SOLVED :laugh: -----------------------------------------------
Hi ! I've solved the problem :
-Charged the phone manually
-Flashed a stock ROM
If anyone has the same problem, PM me, I can Help !
Kindly,
Yahiaga
Need more information please... Which model do you have cdma or gsm? what Android version were you running? What were you trying flash?
Sent from my XT910 using Tapatalk 2
It is a GSM model, I was on gingerbread, and I tried to flash miui (ics)
Sent from my HTC One X using xda app-developers app
Hope this works for you
This will take you back to stock GB 2.3.5 (then after you can upgrade easily to ICS)
Ensure debugging is enabled - I assume you did this before trying to flash anything..?
From the Eternityproject
download Blur_Version.651.167.20.XT910.Retail.en.EU
and from XDA
AlternateFlashScript-WINDOWS.
unzip these files, then copy the alternate flash script files (just the files not the folder) and paste them in the rom folder.
connect your phone via usb and make sure it is in fastboot mode
to start flashing rom first open the eprj-mfastboot file - this will open a cmd window that will disappear
now open the Windows_Fla**** file and just be patient while this flashes stock GB 2.3.5
once done you may need to root the device again.
now you need to download RSDLite5.7 then install it
and ICS 4.0.4
Install
connect phone via usb and go into fastboot mode.
now open RSDLIte5.7 and wait for it to recognise your device -
once your device is recognised you can now browse through the Filename section and select the ICS 4.0.4
next select Decompress and Start Flashing
be patient and it will tell you when its done.
now that you got ICS up and running you will need to root your device again using
EPRJ_EasyRootICS_MultiOS_v1.1 from eternity project
now you can pretty much flash any ICS you want...
Disclaimer: I am not claiming any of the above links to be mine, they all belong to very talented developers who go out of there way to make android better. I am not responsible for any damage you may cause to your phone or pc, I am simply sharing what worked for me.
Good Luck
skatterbug said:
This will take you back to stock GB 2.3.5 (then after you can upgrade easily to ICS)
Ensure debugging is enabled - I assume you did this before trying to flash anything..?
From the Eternityproject
download Blur_Version.651.167.20.XT910.Retail.en.EU
and from XDA
AlternateFlashScript-WINDOWS.
unzip these files, then copy the alternate flash script files (just the files not the folder) and paste them in the rom folder.
connect your phone via usb and make sure it is in fastboot mode
to start flashing rom first open the eprj-mfastboot file - this will open a cmd window that will disappear
now open the Windows_Fla**** file and just be patient while this flashes stock GB 2.3.5
once done you may need to root the device again.
now you need to download RSDLite5.7 then install it
and ICS 4.0.4
Install
connect phone via usb and go into fastboot mode.
now open RSDLIte5.7 and wait for it to recognise your device -
once your device is recognised you can now browse through the Filename section and select the ICS 4.0.4
next select Decompress and Start Flashing
be patient and it will tell you when its done.
now that you got ICS up and running you will need to root your device again using
EPRJ_EasyRootICS_MultiOS_v1.1 from eternity project
now you can pretty much flash any ICS you want...
Disclaimer: I am not claiming any of the above links to be mine, they all belong to very talented developers who go out of there way to make android better. I am not responsible for any damage you may cause to your phone or pc, I am simply sharing what worked for me.
Good Luck
Click to expand...
Click to collapse
Thanks for your effort , I still have a problem, when I go to fastboot mode, it says the battery is low ! And I is not getting charged even plugged.
Hi, Guys today I m going to show you how to root/ unlock bootloader/ Install CMW recovery / Install cm 10/11/AOKP/ Packman roms on your Lg l9 p765 , This tutorial is for complete noob, nothing to worry about, just follow the process, you will find it very easy, so lets get start
Before going to start remember
Lg P760= Lg p765- Nfc chip ( So dont get confuse in nos)
Lg L9 kit
https://drive.google.com/file/d/0B62BCAo0zJcASk1xWkhCTnFhUUk/edit?usp=sharing
Above zip file contains all necessary files
1) Vroot application
2) Root files
3) CMW 6.0.4.5
4) Fastboot driver
5) Lg L9 Drivers
So Download it & Extract on Drive
Before going to do anything, You must install driver first, So just double click on Lg Driver.exe in extracted folder, Follow the process n ur done
Now lets root our Device
1) Now go to extracted, Double click on v root.exe, Install it,
2) Open Vroot Application
3) Now enable USB Debugging on your Handset, Go to developers options Enable debugging
4) Now connect your phone via Usb cable
5) V root will automatically detect your phone
6) Now hit on green root button,
7) Application will show you root succesfull n your phone will reboot ( or may be not)
8) After reboot you will find couple of chinese application installed, just ignore that, install super su from google play & unistall
those applications,
9 )Done, Now you have rooted phone
Next step is unlocking Bootloader
1) Now go to extracted folder, Find root files folder, copy folder & paste it in your system drive ( In my Case c Drive)
2) Now connect you phone with usb debugging on
3) Now double click on open commant prompt
4) Now u have to enter following command ( type or paste ur call)
adb reboot oem-unlock
hit enter, ur phone will reboot into botloader mode,
now press volume up to unlock boot loader, after pressing vol + u will enter in fastboot mode
means ur bootloader is unlocked, done
at this time ur pc will detect ur phone as androide device, it will install driver automatically, if dont, then go to device manager, select androde
device, right click, update driver first select search automatically, if this process failed then u have to select brows my computer option, then
navigate to fasboot folder in extracted folder, this will install fasboot driver on ur device, now ur ready to install recovery
Now its time to Install CMW recovery
1) when ur in fastboot mode dont power off
2) Now u have to enter following command to install CMW recovery
fastboot flash recovery recovery-clockwork-touch-6.0.3.1-p760.img
hit enter & Done, congrats now u succesfully Install cmw on ur phone
3) now enter fastboot reboot to restart ur phone
4) at this stage ur phone will be factory reset, so let the process complete
5) Now u can install CM 10 varients on ur device with this recovery
6) To install cm 11 varients u need to update recovery, for dat install super su & Goomanager on ur device
7) then copy cmw 6.0.4.5 zip on ur ext sd
8) then open Goomanger press reboot recovery, u r phone will be reboot into CMW recovery
9) now go to install zip/ install zip from ext sd/ find zip file/ & install its (use vol + & Vol - to navigate, power button to select )
10) reboot ur phone & Done, Now u have CMW 6.0.4.5 touch installed on ur device, u can check by rebooting ur device in recovery by
Goomanager
For latest recovery
http://forum.xda-developers.com/show....php?t=2733471
Now lets Flash Custom Roms on ur Device
Rom links:
http://forum.xda-developers.com/showthread.php?t=2712249
1) Download both files rom and gapps
2) Copy to ext sd
3) reboot into recovery ( goomanager method)
4) then select
wipe data/ factory reset then select yes wipe all user data, then go back
5) then select wipe cache partition, then select yes wipe, then go back
6) then select advance, select wipe dalvik cache, then yes wipe dalvik cache, go back
7) then select install zip choose zip from ext sd, select ur rom zip,then select yes install,
8) done, let the process complete, it will take some time, after installation complete, reboot ur phone,
9) after intial setup, reboot to recovery, this time dont wipe or factory reset anything, just install gapps zip, then reboot
10) Finally done donnna done done, u have custom rom on ur device, do whatever u want
Enjoy.....!!!!!!
Disclaimer: All material provided in this tutorial belongs to their origional owners, all credit goes them, like artas, dhiru, mateo1111,pedja, nx...etc, i m just explaining the process as per my experience,
Does P765 India V20C work with the method to unlock bootloader???
yupp, it works, i m also on same baseband
Sent from my LG-P760 using XDA Free mobile app
What sw you had before unlocking?
Droideking said:
yupp, it works, i m also on same baseband
Sent from my LG-P760 using XDA Free mobile app
Click to expand...
Click to collapse
Hi what sw version you had installed before trying to unlock bootloader? I have the same problem and I have V20i. Thanks
dr.David said:
Hi what sw version you had installed before trying to unlock bootloader? I have the same problem and I have V20i. Thanks
Click to expand...
Click to collapse
Sorry for late reply, I didnt install any new build, i was on stock jb build with V20c baseband, thats it,
n u need to be on latest stock jb build for unlocking bootloader,
above method works on almost any baseband
there are lots of different methods for unlocking bl for l9,
simple one is, (on device)
if u r rooted,
then install teminal emulater
open that
type "sudo"
hit enter
then type " adb reboot oem-unlock "
device will boot into bootloader mode,
press volume up, done
then follow rest of process, as above.......
I got this message
Droideking said:
Sorry for late reply, I didnt install any new build, i was on stock jb build with V20c baseband, thats it,
n u need to be on latest stock jb build for unlocking bootloader,
above method works on almost any baseband
there is lots of different methods for unlocing bl for l9,
simple one is, (on device)
if u r rooted,
then install teminal emulater
open that
type "sudo"
hit enter
then type " adb reboot oem-unlock "
device will boot into bootloader mode,
press volume up, done
then follow rest of process, as above.......
Click to expand...
Click to collapse
This is the message I got:
:/ $ sudo
/system/bin/sh: sudo: not found
127|[email protected]:/ $ su
[email protected]:/ # adb reboot oem-unlock
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
and nothing happens !!!
dr.David said:
This is the message I got:
:/ $ sudo
/system/bin/sh: sudo: not found
127|[email protected]:/ $ su
[email protected]:/ # adb reboot oem-unlock
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
and nothing happens !!!
Click to expand...
Click to collapse
sure u have rooted phone & super su & busybox installed
if yes then
again open terminal
type "su"
hit enter
accept su permission
then type
adb reboot oem-unlock
thats it
hope this time it will work.....
sorry for above post, sudo command can not use in this method
still no succes
dr.David said:
This is the message I got:
:/ $ sudo
/system/bin/sh: sudo: not found
127|[email protected]:/ $ su
[email protected]:/ # adb reboot oem-unlock
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
and nothing happens !!!
Click to expand...
Click to collapse
It doesn't work !
Maybe my bootloader it's encrypted. Donno...If you have any other ideas...I am open to sugestions. Thank you !
dr.David said:
It doesn't work !
Maybe my bootloader it's encrypted. Donno...If you have any other ideas...I am open to sugestions. Thank you !
Click to expand...
Click to collapse
ok,
try last time
this time dont use adb
just
reboot oem-unlock
try this, if dont work, will try another method
which l9 varient u have?
variant
Droideking said:
ok,
try last time
this time dont use adb
just
reboot oem-unlock
try this, if dont work, will try another method
which l9 varient u have?
Click to expand...
Click to collapse
LG L9 P760 aug/2013
sw: V20i-eur-xx
hidden menu boot-loader state: lock
I tried your last suggestion, the phone turned of and nothing happened
Thanks for your help so far
Updated P765 -v20C(Indian Version) to CM11 -Kang by Dhiru
Hi All,
First of all Thank you Droideking for the detailed guide for a noob like me. :good::good:
I have updated my L9 p765 Indian version with baseband version 20c (latest JB Update India) to CM11. I have used the ROM - UnOfficial CyanogenMod 11 [KANG] 11 by dhiru1602. The experience is awesome. The GUI is liquid smooth no lags unlike the stock ROM.:victory:
About the guide I would like to confirm that it worked absolutely fine for my Indian Version p765 with v20c baseband. There were no restarts encountered in fastboot mode. Only thing which happened was that when i was running adb command in the command prompt i got the error on command prompt saying adb is outdated please update. The error was gone when i ran the command prompt with run as admin option in windows. Also i used RomManager instead of GooManager as it was not available on playstore.
One more observation - Droideking, in the guide you have mentioned that install gapps after installing ROM and restarting the phone after completing setup. I followed the same but then i realised that RomManager was done as i did a reset and wiped the cache and done a reset. So had to download the RomManager apk on the sdcard and install to boot into recovery to install the Gapps. So i guess its better to install the Gapps soon after you have installed the rom in the recovery before restart.
Here are some of the screenshots of my p765..
Error during installation
When I choose install update from ext sd card and after that there is a error occur
The error is shown in picture...
Please help...
and when i use my stock rom unfortunately the process com.android.phone has stopped. is occurred.
Niket Saini said:
When I choose install update from ext sd card and after that there is a error occur
The error is shown in picture...
Please help...
and when i use my stock rom unfortunately the process com.android.phone has stopped. is occurred.
Click to expand...
Click to collapse
God saves you buddy, this problem occurs due to wrong recovery, recovery stops itself from installing rom, n saves you from bricking device,
install latest recovery, 6.0.4.8 or twrp latest release, below is the link
recommend twrp
http://forum.xda-developers.com/showthread.php?t=2733471
dont install 2nd int
by the way if u r flashing artas cm 11 build its not going to work, go for nameless by dhiru or mokee open by nx
cheers
shirodkar8 said:
Hi All,
First of all Thank you Droideking for the detailed guide for a noob like me. :good::good:
I have updated my L9 p765 Indian version with baseband version 20c (latest JB Update India) to CM11. I have used the ROM - UnOfficial CyanogenMod 11 [KANG] 11 by dhiru1602. The experience is awesome. The GUI is liquid smooth no lags unlike the stock ROM.:victory:
About the guide I would like to confirm that it worked absolutely fine for my Indian Version p765 with v20c baseband. There were no restarts encountered in fastboot mode. Only thing which happened was that when i was running adb command in the command prompt i got the error on command prompt saying adb is outdated please update. The error was gone when i ran the command prompt with run as admin option in windows. Also i used RomManager instead of GooManager as it was not available on playstore.
One more observation - Droideking, in the guide you have mentioned that install gapps after installing ROM and restarting the phone after completing setup. I followed the same but then i realised that RomManager was done as i did a reset and wiped the cache and done a reset. So had to download the RomManager apk on the sdcard and install to boot into recovery to install the Gapps. So i guess its better to install the
Gapps soon after you have installed the rom in the recovery before restart.
Here are some of the screenshots of my p765..
Click to expand...
Click to collapse
Glad to hear that dis tut help u to get in custom rom world, the major reason behind it was just rooting n unlocking bootloader safely, rest procedures can varies person to person as per experience
Droideking said:
God saves you buddy, this problem occurs due to wrong recovery, recovery stops itself from installing rom, n saves you from bricking device,
install latest recovery, 6.0.4.8 or twrp latest release, below is the link
recommend twrp
http://forum.xda-developers.com/showthread.php?t=2733471
dont install 2nd int
by the way if u r flashing artas cm 11 build its not going to work, go for nameless by dhiru or mokee open by nx
cheers
Click to expand...
Click to collapse
Thank you for your reply.
And i solve it that day it is due to cwm recovery and atras rom need twrp recovery.
now i am using [AOSP]ParanoidAndroid4.42-FINAL.
Is nameless and mokee is better than paranoidandroid rom?
please give me suggestion
Niket Saini said:
Thank you for your reply.
And i solve it that day it is due to cwm recovery and atras rom need twrp recovery.
now i am using [AOSP]ParanoidAndroid4.42-FINAL.
Is nameless and mokee is better than paranoidandroid rom?
please give me suggestion
Click to expand...
Click to collapse
nameless, much stable, n support, i almost tried every rom on this forum and end up at this, grt rom...
Hotspot
Droideking said:
nameless, much stable, n support, i almost tried every rom on this forum and end up at this, grt rom...
Click to expand...
Click to collapse
Hey i want to know in nameless rom's hotspot is working properly and is there any problem regarding wifi Bluetooth or other fuctions...
please give me suggestion..
because in panandroid rom hotspot is not working
yupp, it works flawlessly
Sent from my LG-P765 using XDA Premium 4 mobile app
Hiw to move an app to sd
Droideking said:
yupp, it works flawlessly
Sent from my LG-P765 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey, sorry to disturb u but i have an issue in nameless rom i know ur not a developer or senior member but i think u hv the solution of my problem.
My problem is I'm not able to move my apps from phone memory to sd card in nameless rom i used other apps to move but when i open the app and click on move it goes to apps info and there is no button to move to sd...
please help....
Hey guys,
Can you help me please? Can't find a way to unlock the bl for my frickin L9.
Device is already rooted.
P760 v20i-eur-xx
Thanks
Sent from my LG-P760 using XDA Free mobile app