Ok, I have a Nexus 5. I have been trying to port (Zip style, not Source) the CM11S build for the OnePlus One. I used the 20140615 CM11 nightly build as the base, but it keeps getting stuck at the boot animation. My issues are that I need to know how to activate ADB Debugging through the build.prop so I can get a logcat on first boot (while it's stuck on the boot animation). Also, once I can get a logcat, I would love some help debugging my port. I will upload a copy of my Zip in it's current form, if anyone has any advice, feel free to pass along some advice.
My CM11S Port (AndroidFileHost)
Don't think you can do it in build prop.. You would need use sqlite3 to write it to settings.db
Sent from my Nexus 5 using Tapatalk
rootSU said:
Don't think you can do it in build prop.. You would need use sqlite3 to write it to settings.db
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Can this be done without the ROM booting fully?
TekGadgt said:
Can this be done without the ROM booting fully?
Click to expand...
Click to collapse
Yeah you can adb pull the db and use sqllite to edit it on a pc and push it back
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yeah you can adb pull the db and use sqllite to edit it on a pc and push it back
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I am having issues with adb over recovery, my device in device manager appears as 'AOSP on Hammerhead' and does not recognize adb interface. I have tried CWM, TWRP, and Philz.
TekGadgt said:
I am having issues with adb over recovery, my device in device manager appears as 'AOSP on Hammerhead' and does not recognize adb interface. I have tried CWM, TWRP, and Philz.
Click to expand...
Click to collapse
search on google for: xda naked usb drivers 0.73, download it and install those drivers in device manager for AOSP on hammerhead device. If you are running running win 8 or 8.1 then you have to turn off the driver signature enforcement.
Tapatalk-kal küldve az én Nexus 5-el
bitdomo said:
search on google for: xda naked usb drivers 0.73, download it and install those drivers in device manager for AOSP on hammerhead device. If you are running running win 8 or 8.1 then you have to turn off the driver signature enforcement.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
I got the adb over recovery issue sorted out, now I just need to figure out why when I use adb logcat, I get /sbin/sh: exec: line 1: logcat: not found
Any ideas? Thanks in advance. Also, if I try to save the logcat to a file, adb logcat -v long > logcat.txt, I get Access is denied.
Related
Hey!
I followed the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2514396
My problem is that I can't use adb in recovery. In device manager, it shows "AOSP on hammerhead". I saw someone that had a solution for this
problem in that thread but it wasn't clear enaugh for me (using windows 7). Can anybody help me out?
Thanks!
Lxve said:
Hey!
I followed the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2514396
My problem is that I can't use adb in recovery. In device manager, it shows "AOSP on hammerhead". I saw someone that had a solution for this
problem in that thread but it wasn't clear enaugh for me (using windows 7). Can anybody help me out?
Thanks!
Click to expand...
Click to collapse
thats because you cant use adb in recovery at all. you can use adb when in the bootloader.
simms22 said:
thats because you cant use adb in recovery at all. you can use adb when in the bootloader.
Click to expand...
Click to collapse
Sorry, think you got mixed up there.
You can only use fastboot in the bootloader. You can only use adb in recovery or android... Although not sure if adb can be used in stock recovery.
simms22 said:
thats because you cant use adb in recovery at all. you can use adb when in the bootloader.
Click to expand...
Click to collapse
Revise it, I can use adb push/ pull etc...
you explained that to someone long ago
rootSU said:
Sorry, think you got mixed up there.
You can only use fastboot in the bootloader. You can only use adb in recovery or android... Although not sure if adb can be used in stock recovery.
Click to expand...
Click to collapse
I'm using TWRP. My problems with drivers keeps increasing it seems :\
Lxve said:
Hey!
I followed the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2514396
My problem is that I can't use adb in recovery. In device manager, it shows "AOSP on hammerhead". I saw someone that had a solution for this
problem in that thread but it wasn't clear enaugh for me (using windows 7). Can anybody help me out?
Thanks!
Click to expand...
Click to collapse
you can go to device manager and update the driver, choose Browse my computer, Let me pick from a list of device drivers, and choose one that says adb.
rootSU said:
Sorry, think you got mixed up there.
You can only use fastboot in the bootloader. You can only use adb in recovery or android... Although not sure if adb can be used in stock recovery.
Click to expand...
Click to collapse
GUGUITOMTG4 said:
Revise it, I can use adb push/ pull etc...
you explained that to someone long ago
Click to expand...
Click to collapse
right.
was concentrating on work. i messed up
simms22 said:
right.
was concentrating on work. i messed up
Click to expand...
Click to collapse
We all do it
Lxve said:
Hey!
I followed the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2514396
My problem is that I can't use adb in recovery. In device manager, it shows "AOSP on hammerhead". I saw someone that had a solution for this
problem in that thread but it wasn't clear enaugh for me (using windows 7). Can anybody help me out?
Thanks!
Click to expand...
Click to collapse
OK as you said you have followed the steps in the linked post. I will assume you have already downloaded and extracted the latest_usb_driver_windows.zip.
I Use windows 8 but the procedure should be the same for Vista / 7 / 8
Here is what to do.
1. Put your phone in recovery.
2. Plug into PC
3. Go To Device Manager
4. Right click "AOSP on hammerhead".
5. Choose "Update Driver Software..."
6. Click "Browse my computer for driver software"
7. Click "Let me pick from a list of device drivers on my computer"
8. Click "Have Disk..."
9. Click "Browse..."
10. Navigate to the extracted Driver you downloaded. (in my case V:\Downloads\latest_usb_driver_windows\usb_driver\)
11. Double click on android_winusb.inf
12. Click "OK"
13. Click "Android Composite ADB Interface" and press Next. (If it is not in the list, untick the "Show compatible hardware button at the top)
Your driver will now install and you should be able to use ADB normally in recovery
To make adb works in recovery you need the naked usb drivers
Tapatalk-kal küldve az én Nexus 5-el
You don't need the naked USB drivers at all.
I use the Google USB drivers and they work fine in recovery.
The problem he is having is that windows has automatically installed a different driver than what is needed for adb to work.
Manually updating the driver to the Google adb driver as shown in my previous post will get the op running without having to download anything extra
Sent from my Nexus 5 using xda app-developers app
Alex240188 said:
OK as you said you have followed the steps in the linked post. I will assume you have already downloaded and extracted the latest_usb_driver_windows.zip.
I Use windows 8 but the procedure should be the same for Vista / 7 / 8
Here is what to do.
1. Put your phone in recovery.
2. Plug into PC
3. Go To Device Manager
4. Right click "AOSP on hammerhead".
5. Choose "Update Driver Software..."
6. Click "Browse my computer for driver software"
7. Click "Let me pick from a list of device drivers on my computer"
8. Click "Have Disk..."
9. Click "Browse..."
10. Navigate to the extracted Driver you downloaded. (in my case V:\Downloads\latest_usb_driver_windows\usb_driver\)
11. Double click on android_winusb.inf
12. Click "OK"
13. Click "Android Composite ADB Interface" and press Next. (If it is not in the list, untick the "Show compatible hardware button at the top)
Your driver will now install and you should be able to use ADB normally in recovery
Click to expand...
Click to collapse
Can you check if you can use adb remount when the phone is fully booted? I'm using naked drivers and everything works except this command. Adb root doesn't work also.
This has nothing to do with the drivers. The kernel you use has to be built with the ro.secure=0 flag for remount to work
Sent from my Nexus 5 using xda app-developers app
hi.
i have question that bothered me now and then.
how do you mount internal storage in pc. for example i wipe out everything, including internal storage (read as sd ext in recovery), evrytime i go in to recovery pick mount usb. it doesnt show any activities in my windows explorer. i go to my computer --> properties --> device manager there is icon nexus 5 with yellow warning on it. try to update driver but return in fail "windows was unable to instal nexus 5"
is there because linux partition on internal storage? so windows cannot load it? or i got wrong version of "usb driver"? or do you have better method? i'd like to know
now everytime i'm flashing rom wipe all data + cache + sd ext, reboot system, after to home screen or my device is on, my pc can transfer files, after done with transferring i reboot to recovery again and then apply rom
This phone doesn't support USB mass storage. Instead there is MTP, but this can only be used while the phone is booted into android. Therefore the only way to copy files to the device while in recovery is to use adb push.
Sent from my HTC Desire using xda app-developers app
Chromium said:
This phone doesn't support USB mass storage. Instead there is MTP, but this can only be used while the phone is booted into android. Therefore the only way to copy files to the device while in recovery is to use adb push.
Click to expand...
Click to collapse
yes i's trying using method adb push, but my nexus doesnt recognize by pc when phone is turn off or in recovery mode, my pc or adb push only work if my nexus is turn on or booted up.
any sugestions?
Private.Indo said:
yes i's trying using method adb push, but my nexus doesnt recognize by pc when phone is turn off or in recovery mode, my pc or adb push only work if my nexus is turn on or booted up.
any sugestions?
Click to expand...
Click to collapse
Search for this on google: naked usb driver 0.73 xda
Click on the first search resault then download the driver.
If you have windows 8 or 8.1 turn off driver signature enforcement.
Open device manager and install the driver for the unknown android device.
Tapatalk-kal küldve az én Nexus 5-el
Private.Indo said:
yes i's trying using method adb push, but my nexus doesnt recognize by pc when phone is turn off or in recovery mode, my pc or adb push only work if my nexus is turn on or booted up.
any sugestions?
Click to expand...
Click to collapse
Did you see this thread at the top of the Q&A section?
http://forum.xda-developers.com/showthread.php?t=2514396
bitdomo said:
Search for this on google: naked usb driver 0.73 xda
Click on the first search resault then download the driver.
If you have windows 8 or 8.1 turn off driver signature enforcement.
Open device manager and install the driver for the unknown android device.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
wow, thx, work like a charm
i knew it i just need correct usb driver package
:victory:
Do i need it? Yes my phone is rooted and has bootloader and everything.
C drive keeps filling up
Yes you can. You only need adb and fastboot which is very small. Use the 15 second installer available in my "adb a a fastboot what is it?" thread which you can find via my signature
Sent from my Nexus 5 using Tapatalk
The only thing most people will need is adb and fastboot, and those are part of platform-tools. No need to install the whole SDK.
Sent from my Nexus 10 using Tapatalk
Accidentally wiped everything using TWRP and have no OS now. Can't use ADB or fastboot as when I boot to it it says device not found. Any suggestions PLEASE?
Is it a driver issue? You have to get the drivers loaded or you may be stuck. What steps have you taken so far.
I had this happen to me as well on another device but I loaded up drivers and then used adb to push files back over on a N4
playya said:
Is it a driver issue? You have to get the drivers loaded or you may be stuck. What steps have you taken so far.
I had this happen to me as well on another device but I loaded up drivers and then used adb to push files back over on a N4
Click to expand...
Click to collapse
Basically all you can do there is re-install the drivers, cause it seems they're non-existent or incorrect.
-reload the drivers [force them perhaps if on win 7]
-connect to pc with phone in fastboot
-in twrp go to advanced > sideload > start process
-add your rom to your adb folder
open a command window in your adb folder [shift + right click for short] then type adb sideload myfile.zip , and the phone will flash the file, and you can reboot.
Nosferatu1923 said:
Accidentally wiped everything using TWRP and have no OS now. Can't use ADB or fastboot as when I boot to it it says device not found. Any suggestions PLEASE?
Click to expand...
Click to collapse
teh roxxorz said:
Basically all you can do there is re-install the drivers, cause it seems they're non-existent or incorrect.
-reload the drivers [force them perhaps if on win 7]
-connect to pc with phone in fastboot
-in twrp go to advanced > sideload > start process
-add your rom to your adb folder
open a command window in your adb folder [shift + right click for short] then type adb sideload myfile.zip , and the phone will flash the file, and you can reboot.
Click to expand...
Click to collapse
I believe above post was meant for you OP
Sent from my A0001 using Tapatalk
After unsuccessfully attempt to flash identity crisis phone not able to flash any other rom seems to me bricked, any solution?
Sent from my MI PAD using XDA Free mobile app
Fastboot flash the XT1033 5.0.2 Firmware Image for your phone from here:
http://forum.xda-developers.com/mot...y-firmware-t3110795/post60792279#post60792279
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
If you have problems, provide a full and complete fastboot log (copy and paste the fastboot screen)
I am on cm 12.1 now.
I wanted to use your rom.
Sent from my MI PAD using XDA Free mobile app
Nishblueweapon said:
I am on cm 12.1 now.
I wanted to use your rom.
Click to expand...
Click to collapse
Something has happened to your phone. If you do what I describe above, any custom ROM should work.
Will try buddie
Sent from my MI PAD using XDA Free mobile app
lost101 said:
Something has happened to your phone. If you do what I describe above, any custom ROM should work.
Click to expand...
Click to collapse
in fastboot mode it says waiting for device.
To be sure i have installed latest drivers via motorola device manager.
Nishblueweapon said:
in fastboot mode it says waiting for device.
To be sure i have installed latest drivers via motorola device manager.
Click to expand...
Click to collapse
@lost101 i hope this could help him
it won't work that easy. On what window you are ?? I don't give a damn which driver you installed http://forum.xda-developers.com/showthread.php?t=2588979
just install the latest version from here.... Let it download and then i
MAKE SURE YOU HAVE USB DEBUGGING ON FROM DEVELOPERS SETTINGS
it will ask you for something like installing system wide adb and fastboot devices. Let it install at last skip the installing device software.
Now just go to c drive of your system or drive in which you have your window installed(drive) installed. Now you see adb named folder on the root of the drive.
Just press shift key first and right click then, you will see there a option of opening with command prompt or something.
Voila !!! you are now in adb .
To check you have right driver installed
give coomand like: adb devices this will show your device in the window...
if you see your device then type command: adb reboot bootloader this will bring you into bootloader menu...
TO check here that you are properly set yourself type command: fastboot devices
sachoosaini said:
@lost101 i hope this could help him
it won't work that easy. On what window you are ?? I don't give a damn which driver you installed http://forum.xda-developers.com/showthread.php?t=2588979
just install the latest version from here.... Let it download and then i
MAKE SURE YOU HAVE USB DEBUGGING ON FROM DEVELOPERS SETTINGS
it will ask you for something like installing system wide adb and fastboot devices. Let it install at last skip the installing device software.
Now just go to c drive of your system or drive in which you have your window installed(drive) installed. Now you see adb named folder on the root of the drive.
Just press shift key first and right click then, you will see there a option of opening with command prompt or something.
Voila !!! you are now in adb .
To check you have right driver installed
give coomand like: adb devices this will show your device in the window...
if you see your device then type command: adb reboot bootloader this will bring you into bootloader menu...
TO check here that you are properly set yourself type command: fastboot devices
Click to expand...
Click to collapse
I am on win. 7. It first gave me an error adpwinal.DLL file is missing from your PC while I was trying to flash those commands in cmd window, so I installed that file on my PC. Whenever I am in fastboot mode now it doesn't recognise me device. & normally it does. I think the problem with fastboot files, it shows USB connected. Will try what u said.
Sent from my Moto G using XDA Free mobile app
while flashing the system files it says file too large
To be sure i was on cm 12.1 (5.1.1) & i have flashed ASia retail 5.0.2?
Where i am wrong?
Nishblueweapon said:
while flashing the system files it says file too large
To be sure i was on cm 12.1 (5.1.1) & i have flashed ASia retail 5.0.2?
Where i am wrong?
Click to expand...
Click to collapse
Use mfastboot.exe: https://www.androidfilehost.com/?fid=24052804347778493
lost101 said:
Use mfastboot.exe: https://www.androidfilehost.com/?fid=24052804347778493
Click to expand...
Click to collapse
Got it to boot successfully. Thank u
What I did was flashed 1 more system I.e. 0 not mentioned in the op
Sent from my MI PAD using XDA Free mobile app