Hello,
I try to connect my V10 (F600L) to my Mac, I've used G4 before and it's work normally but not for V10. Always see this message : Please connect your Android device with a USB cable to get started.
Any help?
Thank you!
Make sure you set the usb connection in the phone to media sync(MTP). After you plug it into the computer. Usually by default it connects "as an installer". It wont work this way.
From my experience, it won't work if you has installed LG Bridge on your mac
in99flames said:
Make sure you set the usb connection in the phone to media sync(MTP). After you plug it into the computer. Usually by default it connects "as an installer". It wont work this way.
Click to expand...
Click to collapse
Yes, I've set to MTP but AFT still doesn't work.
magicbb said:
From my experience, it won't work if you has installed LG Bridge on your mac
Click to expand...
Click to collapse
Checked again but I didn't install LG Bridge before
hanpro said:
Yes, I've set to MTP but AFT still doesn't work.
Checked again but I didn't install LG Bridge before
Click to expand...
Click to collapse
I had a ton of issues as well. Finally gave up and put my micro sd into a sd converter and put the necessary files on my sd card that way.
sickorsane1 said:
I had a ton of issues as well. Finally gave up and put my micro sd into a sd converter and put the necessary files on my sd card that way.
Click to expand...
Click to collapse
Me too. LG is really bad on this point, are we supposed to use only WiFi & LG bridge? This thing can't handle properly big data transfers, and it takes sooooo loooooonnnnnng!
Here's how I fixed it,
Uninstall the LG Unified driver with the driver install .dmg file found here http://www.andromods.com/download-files/latest-lg-g4-drivers-usb-adb-win-mac.html
turn on USb debugging.
Android File Transfer will then find the phone.
gunnyman said:
Here's how I fixed it,
Uninstall the LG Unified driver with the driver install .dmg file found here http://www.andromods.com/download-files/latest-lg-g4-drivers-usb-adb-win-mac.html
turn on USb debugging.
Android File Transfer will then find the phone.
Click to expand...
Click to collapse
this did not work for me
when i ran the uninstaller
i got this
LG United Mobile USB drivers Uninstall Script
Removing the Library Receipts
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
Removing the Installed folder
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
removing the bus driver
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
removing the ACM control driver
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
removing the ACM Data driver
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
removing the Network control driver
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
removing the Network Data driver
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
removing ccl file
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
removing Serial driver
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
removing the bus driver
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
removing the ACM control driver
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
removing the ACM Data driver
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
removing the Network control driver
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
removing the Network Data driver
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
removing ccl file
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
removing Serial driver
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
logout
[Process completed]
gunnyman said:
Here's how I fixed it,
Uninstall the LG Unified driver with the driver install .dmg file found here http://www.andromods.com/download-files/latest-lg-g4-drivers-usb-adb-win-mac.html
turn on USb debugging.
Android File Transfer will then find the phone.
Click to expand...
Click to collapse
thanks, this is work for me
after remove driver, I turn on USB debugging on my phone, then Android File Transfer recognize my LG v10
gunnyman said:
Here's how I fixed it,
Uninstall the LG Unified driver with the driver install .dmg file found here http://www.andromods.com/download-files/latest-lg-g4-drivers-usb-adb-win-mac.html
turn on USb debugging.
Android File Transfer will then find the phone.
Click to expand...
Click to collapse
Thanks man!!! its worked for lg g5 (h820)
gunnyman said:
Here's how I fixed it,
Uninstall the LG Unified driver with the driver install .dmg file found here 'andromods'
turn on USb debugging.
Android File Transfer will then find the phone.
Click to expand...
Click to collapse
Worked for me, thanks. The uninstall file was included in the "LG United Mobile Mac" download. Had to reboot to get it to connect. Was backing up before a clean install of 7.0 on my v10 and trying to use LG Bridge was so slow it would never finish.
I'm running AFT now and in minutes I have over 15 GB already moved. That would have been days with LGB.
Related
Hi,
I went back to factory settings using CWM to try to root again and update ota to .62, but after I went back to factory I can't get it to root anymore
I am trying to use DooMLoRD_v4_ROOT-zergRush-busybox-su
This is what I get:
Code:
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir: permission denied
--- cleaning
rm: permission denied
--- pushing zergRush
461 KB/s (23060 bytes in 0.048s)
--- correcting permissions
chmod: permission denied
--- executing zergRush
./data/local/tmp/zergRush: permission denied
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
2945 KB/s (1075144 bytes in 0.356s)
--- correcting permissions
chmod: permission denied
--- remounting /system
/data/local/tmp/busybox: permission denied
--- checking free space on /system
87 KB/s (439 bytes in 0.004s)
chmod: permission denied
./data/local/tmp/makespace: permission denied
--- copying busybox to /system/xbin/
dd: permission denied
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
chmod: permission denied
--- installing busybox
/system/xbin/busybox: not found
rm: permission denied
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
chmod: permission denied
--- correcting symlinks
rm: permission denied
ln: permission denied
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
rm: permission denied
--- rebooting
ALL DONE!!!
Any ideas?
USB Debugging turned on? Unknown sources allowed? ADB drivers properly installed?
usb debugging was on, unknown sources allowed and I could adb shell... so I guess no problem there either.
For now I recovered the cwm backup I did before I tried going back to 'new'. 58 (to root and update to. 62)
I'll probably start trying again tomorrow.
Just to be clear I now reverted to a rooted .58
But I would like to be able to start over with. 58 (been messing around to much ), root it and update to. 62 (hoping to keep root).
I do have cwm installed, but no unlocked bootloader
All tips are welcome
Thanks
I tried to use a .58 firmware file and flashtool yesterday, but got problems with drivers.
Where can I get the correct driver for sk17i?
TIA
I got one step further using flashtool on my work pc, it rooted, but when trying to update ota, it gives 'could not install new software'...
It worked
Just to keep you guys updated, I downloaded the .58 ftf from http://forum.xda-developers.com/showthread.php?t=1529049 and installed it using flashtool...
I hate that moment when flashtool says 'Please wait. Phone will reboot' ... and it didn't, but just disconnecting it and pressing the power button worked fine
Next I used flashtool to force zergRush exploit: Got stuck at Waiting for device...
Then i rebooted manually with volume down button pressed as is sugested in
http://forum.xda-developers.com/showthread.php?t=1557924 while 'waiting for device.... this didn't work, I must have misunderstood the post.
After the reboot with volume down and failing to complete the root I tried it again and it worked, just to be sure I went to adb shell and tried su... it worked.
Time for a backup with cwm
Which got apparently uninstalled when using flashtool to go to .58 ... that's a lesson learned and probably logical,so I reinstalled it from the market ...
Strangely cwm installer had a force closed, but it didn't seem to affect anything.
Now for OTA update to .62 ... Done
Root still there? Yes
time for another CWM backup...
And I can go about messing with it again, freezing/uninstalling apps...
Thanks for the help
angelofhope said:
Just to keep you guys updated, I downloaded the .58 ftf from http://forum.xda-developers.com/showthread.php?t=1529049 and installed it using flashtool...
I hate that moment when flashtool says 'Please wait. Phone will reboot' ... and it didn't, but just disconnecting it and pressing the power button worked fine
Click to expand...
Click to collapse
Phone is restarted again to flashmode
That's why you have to disconnect and power up.
angelofhope said:
Next I used flashtool to force zergRush exploit: Got stuck at Waiting for device...
Then i rebooted manually with volume down button pressed as is sugested in
http://forum.xda-developers.com/showthread.php?t=1557924 while 'waiting for device.... this didn't work, I must have misunderstood the post.
After the reboot with volume down and failing to complete the root I tried it again and it worked, just to be sure I went to adb shell and tried su... it worked.
Click to expand...
Click to collapse
Phone has to be turned on in order to root
Just turn it on, make sure USB debugging and Unknown Sources are allowed and leave it on home screen for example.
Please has anyone gotten root on the mytouch by huawei/
Use a standard mode. If you have the adb drivers use any rooter.
Sent from my RK29 tab...
Bump
Sent from my T-Mobile myTouch using xda app-developers app
superbart007 said:
Bump
Sent from my T-Mobile myTouch using xda app-developers app
Click to expand...
Click to collapse
Sorry for my short answer but I recommend you to try (if you have adb drivers working) z4root or superoneclick.
The root process in Android is not as difficult as it seems. Just use a exploit to adb push files and change to rw system.
Sent from my RK29 tab...
I just attempted both of those root methods and also ZergRush nothing seems to work
darklink528 said:
I just attempted both of those root methods and also ZergRush nothing seems to work
Click to expand...
Click to collapse
Make sure to have the correct Adb drivers, sometimes the google drivers doesn't work with the oems driver...
If it doesn't work try with doomslord method. I'm getting without ideas
Sent from my RK29 tab...
Tried that one too nothing :/
What said the log, you get sucked at waiting for device ? Or were ?
Sent from my RK29 tab...
SferaDev said:
What said the log, you get sucked at waiting for device ? Or were ?
Sent from my RK29 tab...
Click to expand...
Click to collapse
I took a screenshot of where it gets stuck this one is Zergrush but superoneciclick gets stuck at waiting for device on step 7.
http://puu.sh/XigH
^^
Screenshot
darklink528 said:
I took a screenshot of where it gets stuck this one is Zergrush but superoneciclick gets stuck at waiting for device on step 7.
http://puu.sh/XigH
^^
Screenshot
Click to expand...
Click to collapse
Have you enabled USB debugging ?
Sent from my RK29 tab...
Yeah of course
darklink528 said:
Yeah of course
Click to expand...
Click to collapse
Then May be the vendor Id in the drivers !
Sent from my RK29 tab...
I'm having the same problem. I've rooted many Android devices. Yes USB debugging is enabled. Yes I can get adb access to the phone with a user level shell prompt. Yes it shows up in device manager as an Android Composite ADB interface. Yes I've added the PID and VID to android_winusb.inf.
Superoneclick gets stuck at step 7.
This phone seems like a decent phone for my wife (as a replacement for her stolen Samsung Galaxy S 4G), but it's LOADED with bloatware. I really need to figure out how to root this thing.
jb0ne said:
I'm having the same problem. I've rooted many Android devices. Yes USB debugging is enabled. Yes I can get adb access to the phone with a user level shell prompt. Yes it shows up in device manager as an Android Composite ADB interface. Yes I've added the PID and VID to android_winusb.inf.
Superoneclick gets stuck at step 7.
This phone seems like a decent phone for my wife (as a replacement for her stolen Samsung Galaxy S 4G), but it's LOADED with bloatware. I really need to figure out how to root this thing.
Click to expand...
Click to collapse
Try the doomslord method then. This method works pretty fine in lots of unnoficial or non tested devices.
SferaDev said:
Try the doomslord method then. This method works pretty fine in lots of unnoficial or non tested devices.
Click to expand...
Click to collapse
Thanks for the suggestion. Downloaded latest version of it (version 4). No luck.
Here's the output:
[*] Sending 149 zerglings ...
bugreport dir[/data/local/tmp] exist.
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
4038 KB/s (1075144 bytes in 0.260s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
32 KB/s (439 bytes in 0.013s)
df: /mnt/secure/asec: Permission denied
--- Free space on /system : 98% bytes
test: 98%: bad number
--- NOT enough free space on /system!!!
--- making free space by removing Google Maps
rm: can't remove '/system/app/Maps.apk': Read-only file system
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
After that mount error I adb shelled in tried su for the heck of it and got permission denied. Also confirmed normal user can run mount. Checked df and /system is 370M, but only has 7M free. I wonder if that's the problem? How much space is needed for the zergrush method? Obviously I can't remove anything from /system if that is the problem. Also the df output is standard unix output so doesn't look like his bat file does very good error checking or does something odd.
For some problem the exploit doesn't works... Sniff...
make a request in ready2root.com
Sent from my RK29 tab...
I cannot root my phone for the past 2 months.... Am trying the best by searching most of the web sites.... but i cant root it...
While am using flashtool it notifies me "WAITING FOR DEVICE".....
When using doomlord v1.0 for ICS... I done the following instructions as per the (runme.bat) file, but it doesn't install any of the file.
Drivers installed? If not use drivers from flashtool folder.
What fw version(build)? Don't you think it's kinda important to give some info about your phone
Q:What f/w version(build)? Don't you think it's kinda important to give some info about your phone
A:Am using f/w :4.1.B.0.431
kernel version :2.6.32.9-pref
[email protected]#1
Then you didn't do a good search in those 2 months. Since you didn't find sticky thread in general section.
First rule of modding phone, read sticky threads.
If the flashtool does not recognise ur phone its definately cuz ur drivers arent installed correctly.
I used the above method 2 root my phone... Eventhough after enabling both "unknown sources" n "USB debugging" mode
:cyclops:NOTE: # -> Error occurs
# ""-> Error Operation begins n ends
---------------------------------------------------------------
Xperia 2011 ICS Easy Rooting toolkit (v1.0)
created by DooMLoRD
"andorid emulator" trick
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using "andorid emulator" trick
(2) install Busybox (1.18.4)
(3) install SU files (ICS specific)
(4) do some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Developer Options\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Security)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- symlinking tmp directory
failed on '/data/local/tmp' - Permission denied #
link failed File exists #
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- enabling emulator hack
/system/bin/sh: cannot create /data/local.prop: Permission denied #
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
3952 KB/s (1075144 bytes in 0.265s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?) #
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
--- Free space on /system : 73552 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system # ""
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/bin/sh: /system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory # ""
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Have you flashed 562 kernel before rooting?
O yes
:victory: :good: I've installed 4.0.3 on my device n got rooted....
Now am having 2 more queries after rooting!
1. Can I install other device f/w like xperia S/arc/ray or Samsung f/w?
2. I can't update my phone to 4.0.4.
2day I install 4.0.3 on my device n got a "NEW SOFTWARE UPDATE AVAILABLE FORUR DEVICE" but I can't update my device.
Could u say me is there any way to cure this problem to install the 4.0.4 firmware.
1) not really,
2) yes you can, you can have 4.0.4 and rooted, if only you read what people suggest to you.
Greetings-
I just built my first image of AOSP for a Samsung Note 3. I have, in the past deployed a Cyanogenmod nightly release on my phone. Now I am trying to deploy my image. I used this link to build my environment http://forums.androidcentral.com/verizon-galaxy-nexus-rooting-roms-hacks/189699-guide-ubuntu-compiling-android-source-12.html . But the install does not go well. I am moving the zip file to the external sd card, and using TWRP to install it. I get the following messages: E: Unable to mount '/usbstorage' Full SELinux is present In istalling '/external_sd/full_toroplus-ota-eng.root.zip checking for MD5 file Skipping MD5 check: no MD5 file found. assert failed: getprop ('ro.product.device") == "toroplus" || getprop ("ro.bild.product") ==toroplus" e:error executing updater binary in zip 'external_sd/full_toroplus-ta-eng.root.zip' error flashing zip '/external_sd/full_toroplus-ota-eng.root.zip Updating partition details.. E:unable to mount 'usbstorage'
What am I doing wrong? Is there some other way I can do this?
Sean
sansari123 said:
Greetings-
I just built my first image of AOSP for a Samsung Note 3. I have, in the past deployed a Cyanogenmod nightly release on my phone. Now I am trying to deploy my image. I used this link to build my environment http://forums.androidcentral.com/ve...guide-ubuntu-compiling-android-source-12.html . But the install does not go well. I am moving the zip file to the external sd card, and using TWRP to install it. I get the following messages: E: Unable to mount '/usbstorage' Full SELinux is present In istalling '/external_sd/full_toroplus-ota-eng.root.zip checking for MD5 file Skipping MD5 check: no MD5 file found. assert failed: getprop ('ro.product.device") == "toroplus" || getprop ("ro.bild.product") ==toroplus" e:error executing updater binary in zip 'external_sd/full_toroplus-ta-eng.root.zip' error flashing zip '/external_sd/full_toroplus-ota-eng.root.zip Updating partition details.. E:unable to mount 'usbstorage'
What am I doing wrong? Is there some other way I can do this?
Sean
Click to expand...
Click to collapse
What phone do you have? Toroplus is galaxy nexus of course that won't ever flash on a note 3 you should be building hlte for note 3
Sent from my SM-G900P using Xparent BlueTapatalk 2
Epix4G said:
What phone do you have? Toroplus is galaxy nexus of course that won't ever flash on a note 3 you should be building hlte for note 3
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Thanks. Are you saying hlte is an option for the lunch command? Here is how I got toroplus; I saw it in the android source site. https://source.android.com/#q=sprint samsungese
Basically, these are my options:
[email protected]:~/WORKING_DIRECTORY# lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_x86-eng
3. aosp_mips-eng
4. vbox_x86-eng
5. aosp_deb-userdebug
6. aosp_flo-userdebug
7. full_grouper-userdebug
8. full_tilapia-userdebug
9. mini_armv7a_neon-userdebug
10. mini_mips-userdebug
11. mini_x86-userdebug
12. full_mako-userdebug
13. full_maguro-userdebug
14. full_manta-userdebug
15. full_arndale-userdebug
16. full_toroplus-userdebug
17. full_toro-userdebug
18. full_panda-userdebug
Which would you like? [aosp_arm-eng]
sansari123 said:
Thanks. Are you saying hlte is an option for the lunch command? Here is how I got toroplus; I saw it in the android source site. https://source.android.com/#q=sprint samsungese
Basically, these are my options:
[email protected]:~/WORKING_DIRECTORY# lunch
You're building on Linux
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_x86-eng
3. aosp_mips-eng
4. vbox_x86-eng
5. aosp_deb-userdebug
6. aosp_flo-userdebug
7. full_grouper-userdebug
8. full_tilapia-userdebug
9. mini_armv7a_neon-userdebug
10. mini_mips-userdebug
11. mini_x86-userdebug
12. full_mako-userdebug
13. full_maguro-userdebug
14. full_manta-userdebug
15. full_arndale-userdebug
16. full_toroplus-userdebug
17. full_toro-userdebug
18. full_panda-userdebug
Which would you like? [aosp_arm-eng]
Click to expand...
Click to collapse
This is not a nexus device so Google would not have it in there. .... if you want to build aosp and not cyanogen or some other flavor that had already supported hlte then you will have to add support yourself
Sent from my SM-G900P using Xparent BlueTapatalk 2
Epix4G said:
This is not a nexus device so Google would not have it in there. .... if you want to build aosp and not cyanogen or some other flavor that had already supported hlte then you will have to add support yourself
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Thanks. I started to use Cyanogenmod, and went through this link: How To Build CyanogenMod Android for Samsung Galaxy Note 3 LTE ("hlte")
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
When I issue breakfast to get the device specific modules, I get the following message:
#:~/android/system# breakfast hlte
including vendor/cm/vendorsetup.sh
ls: cannot access device/*/hlte/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_hlte". Stop.
Device hlte not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_hlte
Default revision: cm-10.2
Checking branch info
Default revision cm-10.2 not found in android_device_samsung_hlte. Bailing.
Branches found:
cm-11.0
stable/cm-11.0 Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
ls: cannot access device/*/hlte/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_hlte". Stop.
** Don't have a product spec for: 'cm_hlte'
** Do you have the right repo manifest?
--------------------------------------------------------------------------------------------------------------------------------------------------------------
I am now downloading version 11.0 instead of 10.2. Do you think that would fix my issue? I do not know what it is complaining about.
sansari123 said:
Thanks. I started to use Cyanogenmod, and went through this link: How To Build CyanogenMod Android for Samsung Galaxy Note 3 LTE ("hlte")
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
When I issue breakfast to get the device specific modules, I get the following message:
#:~/android/system# breakfast hlte
including vendor/cm/vendorsetup.sh
ls: cannot access device/*/hlte/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_hlte". Stop.
Device hlte not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_hlte
Default revision: cm-10.2
Checking branch info
Default revision cm-10.2 not found in android_device_samsung_hlte. Bailing.
Branches found:
cm-11.0
stable/cm-11.0 Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
ls: cannot access device/*/hlte/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_hlte". Stop.
** Don't have a product spec for: 'cm_hlte'
** Do you have the right repo manifest?
--------------------------------------------------------------------------------------------------------------------------------------------------------------
I am now downloading version 11.0 instead of 10.2. Do you think that would fix my issue? I do not know what it is complaining about.
Click to expand...
Click to collapse
I don't remember if their was ever a 10.2 that worked so yes I think it best to use 11.0 ... cyanogen should build with no problem. .. what os are you using that may be a problem I think most use 12.04 Ubuntu ... but I use 14.04 and the difference is a few different things ....
Sent from my SM-G900P using Xparent BlueTapatalk 2
Epix4G said:
I don't remember if their was ever a 10.2 that worked so yes I think it best to use 11.0 ... cyanogen should build with no problem. .. what os are you using that may be a problem I think most use 12.04 Ubuntu ... but I use 14.04 and the difference is a few different things ....
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I am using 12.04. Do you think I should upgrade?
I just noticed a comment about fastboot. Will I need it for this task? I just can not get fastboot working on my laptop. I think it is because I only have usb 2.0.
I have tried 11.0 twice now, and I get this error:
* [new branch] cm-11.0 -> github/cm-11.0
Fetching projects: 100% (447/447), done.
Traceback (most recent call last):
File "/root/android/system/.repo/repo/main.py", line 408, in <module>
_Main(sys.argv[1:])
File "/root/android/system/.repo/repo/main.py", line 384, in _Main
result = repo._Run(argv) or 0
File "/root/android/system/.repo/repo/main.py", line 143, in _Run
result = cmd.Execute(copts, cargs)
File "/root/android/system/.repo/repo/subcmds/sync.py", line 690, in Execute
project.Sync_LocalHalf(syncbuf)
File "/root/android/system/.repo/repo/project.py", line 1158, in Sync_LocalHalf
lost = self._revlist(not_rev(revid), HEAD)
File "/root/android/system/.repo/repo/project.py", line 2178, in _revlist
return self.work_git.rev_list(*a, **kw)
File "/root/android/system/.repo/repo/project.py", line 2335, in rev_list
p.stderr))
error.GitError: CyanogenMod/android rev-list ('^bf81824cd948e185fdc86626f237a8c3e85a4687', 'HEAD', '--'): fatal: bad object HEAD
What should I do?
Epix4G said:
I don't remember if their was ever a 10.2 that worked so yes I think it best to use 11.0 ... cyanogen should build with no problem. .. what os are you using that may be a problem I think most use 12.04 Ubuntu ... but I use 14.04 and the difference is a few different things ....
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Hey Epix, thank you so much for your help so far. I was able to download cd-11.0. I had to delete the .repo directory a number of times ( about ten ), and it still did not work. I then deleted other git related files. I used this linke http://stackoverflow.com/questions/1213430/how-to-fully-delete-a-git-repository-created-with-init I hope this helps others.
I would really appreciate it if you can help me with fastboot issue. I posted a comment earlier. I am also now running into some other potential issues when I issue "./extract-files.sh" command. Below you see the result of grep for the words permission, and failed. Would this cause me issues? The permission issue is related to my device.
[email protected]:~/android/system/device/samsung/hlte# more typescript | grep -i permission
failed to copy '/system/bin/mpdecision' to '../../../vendor/samsung/hlte/proprietary/bin/mpdecision': Permission denied
failed to copy '/system/bin/rfs_access' to '../../../vendor/samsung/hlte/proprietary/bin/rfs_access': Permission denied
failed to copy '/system/bin/thermald' to '../../../vendor/samsung/hlte/proprietary/bin/thermald': Permission denied
failed to copy '/system/bin/thermal-engine' to '../../../vendor/samsung/hlte/proprietary/bin/thermal-engine': Permission denied
failed to copy '/system/bin/gsiff_daemon' to '../../../vendor/samsung/hlte/proprietary/bin/gsiff_daemon': Permission denied
Extracting /system/etc/permissions/com.qualcomm.location.xml ...
failed to copy '/system/bin/efsks' to '../../../vendor/samsung/hlte/proprietary/bin/efsks': Permission denied
failed to copy '/system/bin/ks' to '../../../vendor/samsung/hlte/proprietary/bin/ks': Permission denied
failed to copy '/system/bin/qcks' to '../../../vendor/samsung/hlte/proprietary/bin/qcks': Permission denied
failed to copy '/system/bin/qmuxd' to '../../../vendor/samsung/hlte/proprietary/bin/qmuxd': Permission denied
failed to copy '/system/bin/rild' to '../../../vendor/samsung/hlte/proprietary/bin/rild': Permission denied
failed to copy '/system/bin/rmt_storage' to '../../../vendor/samsung/hlte/proprietary/bin/rmt_storage': Permission denied
failed to copy '/system/bin/time_daemon' to '../../../vendor/samsung/hlte/proprietary/bin/time_daemon': Permission denied
failed to copy '/system/bin/mm-qcamera-daemon' to '../../../vendor/samsung/hlte/proprietary/bin/mm-qcamera-daemon': Permission denied
failed to copy '/system/bin/qseecomd' to '../../../vendor/samsung/hlte/proprietary/bin/qseecomd': Permission denied
failed to copy '/system/bin/mm-pp-daemon' to '../../../vendor/samsung/hlte/proprietary/bin/mm-pp-daemon': Permission denied
[email protected]:~/android/system/device/samsung/hlte# more typescript | grep -i failed
failed to copy '/system/bin/mpdecision' to '../../../vendor/samsung/hlte/proprietary/bin/mpdecision': Permission denied
failed to copy '/system/bin/rfs_access' to '../../../vendor/samsung/hlte/proprietary/bin/rfs_access': Permission denied
failed to copy '/system/bin/thermald' to '../../../vendor/samsung/hlte/proprietary/bin/thermald': Permission denied
failed to copy '/system/bin/thermal-engine' to '../../../vendor/samsung/hlte/proprietary/bin/thermal-engine': Permission denied
failed to copy '/system/bin/gsiff_daemon' to '../../../vendor/samsung/hlte/proprietary/bin/gsiff_daemon': Permission denied
failed to copy '/system/bin/efsks' to '../../../vendor/samsung/hlte/proprietary/bin/efsks': Permission denied
failed to copy '/system/bin/ks' to '../../../vendor/samsung/hlte/proprietary/bin/ks': Permission denied
failed to copy '/system/bin/qcks' to '../../../vendor/samsung/hlte/proprietary/bin/qcks': Permission denied
failed to copy '/system/bin/qmuxd' to '../../../vendor/samsung/hlte/proprietary/bin/qmuxd': Permission denied
failed to copy '/system/bin/rild' to '../../../vendor/samsung/hlte/proprietary/bin/rild': Permission denied
failed to copy '/system/bin/rmt_storage' to '../../../vendor/samsung/hlte/proprietary/bin/rmt_storage': Permission denied
failed to copy '/system/bin/time_daemon' to '../../../vendor/samsung/hlte/proprietary/bin/time_daemon': Permission denied
failed to copy '/system/bin/mm-qcamera-daemon' to '../../../vendor/samsung/hlte/proprietary/bin/mm-qcamera-daemon': Permission denied
failed to copy '/system/bin/qseecomd' to '../../../vendor/samsung/hlte/proprietary/bin/qseecomd': Permission denied
failed to copy '/system/bin/mm-pp-daemon' to '../../../vendor/samsung/hlte/proprietary/bin/mm-pp-daemon': Permission denied
[email protected]:~/android/system/device/samsung/hlte#
I tried to fix the permission issue by issuing the command mount, which according to the Cyanogenmod wiki here, http://wiki.cyanogenmod.org/w/Doc:_Building_Basics mounts the directories as read/write. But I ended up with the same amount of permission denied'sssssssssss so I used adb shell and issued mount -o remount,rw /system, and then issued the Cyanogenmod script command "./extract-files.sh'. But I still get the same number of permission denied messages. Any ideas?
sansari123 said:
Hey Epix, thank you so much for your help so far. I was able to download cd-11.0. I had to delete the .repo directory a number of times ( about ten ), and it still did not work. I then deleted other git related files. I used this linke http://stackoverflow.com/questions/1213430/how-to-fully-delete-a-git-repository-created-with-init I hope this helps others.
I would really appreciate it if you can help me with fastboot issue. I posted a comment earlier. I am also now running into some other potential issues when I issue "./extract-files.sh" command. Below you see the result of grep for the words permission, and failed. Would this cause me issues? The permission issue is related to my device.
[email protected]:~/android/system/device/samsung/hlte# more typescript | grep -i permission
failed to copy '/system/bin/mpdecision' to '../../../vendor/samsung/hlte/proprietary/bin/mpdecision': Permission denied
failed to copy '/system/bin/rfs_access' to '../../../vendor/samsung/hlte/proprietary/bin/rfs_access': Permission denied
failed to copy '/system/bin/thermald' to '../../../vendor/samsung/hlte/proprietary/bin/thermald': Permission denied
failed to copy '/system/bin/thermal-engine' to '../../../vendor/samsung/hlte/proprietary/bin/thermal-engine': Permission denied
failed to copy '/system/bin/gsiff_daemon' to '../../../vendor/samsung/hlte/proprietary/bin/gsiff_daemon': Permission denied
Extracting /system/etc/permissions/com.qualcomm.location.xml ...
failed to copy '/system/bin/efsks' to '../../../vendor/samsung/hlte/proprietary/bin/efsks': Permission denied
failed to copy '/system/bin/ks' to '../../../vendor/samsung/hlte/proprietary/bin/ks': Permission denied
failed to copy '/system/bin/qcks' to '../../../vendor/samsung/hlte/proprietary/bin/qcks': Permission denied
failed to copy '/system/bin/qmuxd' to '../../../vendor/samsung/hlte/proprietary/bin/qmuxd': Permission denied
failed to copy '/system/bin/rild' to '../../../vendor/samsung/hlte/proprietary/bin/rild': Permission denied
failed to copy '/system/bin/rmt_storage' to '../../../vendor/samsung/hlte/proprietary/bin/rmt_storage': Permission denied
failed to copy '/system/bin/time_daemon' to '../../../vendor/samsung/hlte/proprietary/bin/time_daemon': Permission denied
failed to copy '/system/bin/mm-qcamera-daemon' to '../../../vendor/samsung/hlte/proprietary/bin/mm-qcamera-daemon': Permission denied
failed to copy '/system/bin/qseecomd' to '../../../vendor/samsung/hlte/proprietary/bin/qseecomd': Permission denied
failed to copy '/system/bin/mm-pp-daemon' to '../../../vendor/samsung/hlte/proprietary/bin/mm-pp-daemon': Permission denied
[email protected]:~/android/system/device/samsung/hlte# more typescript | grep -i failed
failed to copy '/system/bin/mpdecision' to '../../../vendor/samsung/hlte/proprietary/bin/mpdecision': Permission denied
failed to copy '/system/bin/rfs_access' to '../../../vendor/samsung/hlte/proprietary/bin/rfs_access': Permission denied
failed to copy '/system/bin/thermald' to '../../../vendor/samsung/hlte/proprietary/bin/thermald': Permission denied
failed to copy '/system/bin/thermal-engine' to '../../../vendor/samsung/hlte/proprietary/bin/thermal-engine': Permission denied
failed to copy '/system/bin/gsiff_daemon' to '../../../vendor/samsung/hlte/proprietary/bin/gsiff_daemon': Permission denied
failed to copy '/system/bin/efsks' to '../../../vendor/samsung/hlte/proprietary/bin/efsks': Permission denied
failed to copy '/system/bin/ks' to '../../../vendor/samsung/hlte/proprietary/bin/ks': Permission denied
failed to copy '/system/bin/qcks' to '../../../vendor/samsung/hlte/proprietary/bin/qcks': Permission denied
failed to copy '/system/bin/qmuxd' to '../../../vendor/samsung/hlte/proprietary/bin/qmuxd': Permission denied
failed to copy '/system/bin/rild' to '../../../vendor/samsung/hlte/proprietary/bin/rild': Permission denied
failed to copy '/system/bin/rmt_storage' to '../../../vendor/samsung/hlte/proprietary/bin/rmt_storage': Permission denied
failed to copy '/system/bin/time_daemon' to '../../../vendor/samsung/hlte/proprietary/bin/time_daemon': Permission denied
failed to copy '/system/bin/mm-qcamera-daemon' to '../../../vendor/samsung/hlte/proprietary/bin/mm-qcamera-daemon': Permission denied
failed to copy '/system/bin/qseecomd' to '../../../vendor/samsung/hlte/proprietary/bin/qseecomd': Permission denied
failed to copy '/system/bin/mm-pp-daemon' to '../../../vendor/samsung/hlte/proprietary/bin/mm-pp-daemon': Permission denied
[email protected]:~/android/system/device/samsung/hlte#
Click to expand...
Click to collapse
You have to setup android sdk ..and add it to bash and path so that in any terminal you can type android and it opens sdk ... Until then you can't extract files
Sent from my SM-N900P using Xparent BlueTapatalk 2
I am running Ubuntu 14.04 x64. I installed the ADB packages through apt-get:
sudo apt-get install android-tools-fastboot
sudo apt-get install android-tools-adb
Then I downloaded ioroot.zip, extracted it and did:
chmod +x ioroot.sh
When I run ioroot.sh I get the following errors:
Determining device model and firmware version...
./ioroot.sh: line 93: SLEEP: command not found
./ioroot.sh: line 94: ./adblinux: Permission denied
./ioroot.sh: line 95: ./adblinux: Permission denied
./ioroot.sh: line 96: ./adblinux: Permission denied
No matching phone found. Full device info below.
Post device info in IOroot thread.
./ioroot.sh: line 1683: ./adblinux: Permission denied
./ioroot.sh: line 1684: ./adblinux: Permission denied
./ioroot.sh: line 1685: ./adblinux: Permission denied
./ioroot.sh: line 1686: ./adblinux: Permission denied
Press enter to continue...
So, what does that mean?
My main goal is to root, install recovery and install Cyanogenmod.
I have Googled like crazy. Can't figure out what the problem is. I guess I leave it alone. The phone works fine without CM, just a lot of bloat from LG. I don't think I have the skills for this.
mooreted said:
I have Googled like crazy. Can't figure out what the problem is. I guess I leave it alone. The phone works fine without CM, just a lot of bloat from LG. I don't think I have the skills for this.
Click to expand...
Click to collapse
I had the same problems. I found the solution and posted it here. It may help you :
forum.xda-developers.com/showpost.php?p=59374674&postcount=43