Hi i need to find a kernal with usb debugging and adb setting in developer settings automatically ticked because my phone screen is completely broken and im using a program that requires the two settings to be on. Please help if you can thank you!
I don't think a kernel can enable those, only the user can.. You can probably flash a ROM that has them enabled or a script
Sent from my SGH-M919 using Tapatalk
serio22 said:
I don't think a kernel can enable those, only the user can.. You can probably flash a ROM that has them enabled or a script
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I also broke my screen and was looking for this exact thing. It's Android Control and I need adb enabled. I tried various ways I found while searching to try to enable adb through TWRP and an adb shell on my PC, but it wouldn't work ( kept getting a "~ # ?[6n" prompt and "not found" when entering "su" ).
Then I found this kernel kitchen. In that thread the dev says you can make the ramdisk insecure and make adb mode persistent. Anybody able to help me out?
brokenchains said:
I also broke my screen and was looking for this exact thing. It's Android Control and I need adb enabled. I tried various ways I found while searching to try to enable adb through TWRP and an adb shell on my PC, but it wouldn't work ( kept getting a "~ # ?[6n" prompt and "not found" when entering "su" ).
Then I found this kernel kitchen. In that thread the dev says you can make the ramdisk insecure and make adb mode persistent. Anybody able to help me out?
Click to expand...
Click to collapse
What version? Mdl mk2 or nb4? Probably already insecure boot.img unless you're running stock tho
Debugging in dev options would be a different story tho. I might be able to figure out how to enable it thru command line tho
And now that I think about it, I don't even know what would work since you're dual booting.
ShinySide said:
What version? Mdl mk2 or nb4? Probably already insecure boot.img unless you're running stock tho
Debugging in dev options would be a different story tho. I might be able to figure out how to enable it thru command line tho
And now that I think about it, I don't even know what would work since you're dual booting.
Click to expand...
Click to collapse
I figured out how to get adb shell working, but I had to switch TWRP out for CWM non-touch. That let me use adb correctly through recovery and I found a way to enable adb in the ROM that way by pulling settings.db and editing the "adb_enabled" setting there. Now I'm just caught because I can't see the screen to authorize my PC to use adb... I tried to manually put the adb key from my PC's file into the adb_keys file on the phone but that didn't work and I'm pretty sure I did it right. That process is described here for anyone curious.
Related
Can a person flash the boot image using a mac? I am only noticing it needs to be a windows machine.
sfowler39 said:
Can a person flash the boot image using a mac? I am only noticing it needs to be a windows machine.
Click to expand...
Click to collapse
Yes, I did. Actually I am using only Mac and Linux.
The procedure is exactly same, the only difference is OS.
i too use a mac, and as long as you have your path setup and fastboot in your path you can use it for boot, system,recovery, data images
Are there any tutorials on how to do this? I'm not very savy with terminal. I've installed adb and fastboot-mac but when i try to run the recovery rom it says error device not found. I've been googling and can't find a full tutorial, just bits and pieces here and there and this is as far as I've gotten. Any help would be appreciated
Mac works fine... follow instructions for everything. Actually Eclipse is easier on mac than windows --no crappy winblows driver issues.
And fyi - you prob need to put your phone in dev mode.... try ./adb devices
Settings --> Application --> Development --> USB Debugging
Working great on my Mac too... Just make sure, as mentioned above, that you have enable USB debugging ("dev mode"). If you're getting a device not found error, then sounds like you have everything working on the Mac. Just need to enable the phone to communicate with the adb program.
On your phone, go to Settings --> Application --> Development. Enable the "USB Debugging" option.
If you have any trouble, let me know. I'm relatively new myself, but pretty comfortable with *nix, so I'll help in any way I can!
Scott
the easiest way I did it was use flashrec to root the phone and then transfer the roms onto the phone and use recovery to flash them....
havent ever had a problem...
im not sure about fastboot, but adb works fine with mac terminal u just have to put "./" before u type a command
danial.aw said:
the easiest way I did it was use flashrec to root the phone and then transfer the roms onto the phone and use recovery to flash them....
havent ever had a problem...
im not sure about fastboot, but adb works fine with mac terminal u just have to put "./" before u type a command
Click to expand...
Click to collapse
and if you have all of your executables in the folder referenced in your .bash_profile then you dont need to even type the "./"
this is what my .bash_profile looks like:
export PATH=$PATH{PATH}:/android/tools
so put adb,fastboot and whatever other binaries you want to use in /android/tools
Hey guys,
Was trying to de-Carrier IQ my phone today when I made a serious rookie mistake. I renamed the following two files and rebooted, and now only get the "Samsung" logo at boot:
/system/lib/libiq_client.so -> libiq_client_old.so
/system/lib/libiq_service.so -> libiq_service_old.so
I also renamed the "/system/bin/iqmsd" daemon (to iqmsd_old), set "setprop service.iq.active 0", and "pm disabled" the various CIQ services but I don't think these changes are related (successfully rebooted afterwards).
My restore plan was to flash ACSRecovery5 using Odin (not previously loaded) and then mount the /system directory, renaming those libraries (.so's) back to their original names. While Odin reports success in flashing ACSRecovery ("ACSRecovery5-1.0.0.0-epic4g.tar.md5" under PDA), when I boot into recovery mode (VolDown-Camera-Pwr) the stock Samsung recovery menu still appears :-( Also tried experimenting with ADB--"adb devices" reports the phone as "offline" during normal boot (where it freezes at the Samsung logo) and doesn't even show the device in download or recovery modes.
PHONE DETAILS:
Samsung Epic 4G (Sprint)
Stock Eclair (DI18)
Rooted using z4root
Apps + Data backed up to SDCard via TitaniumBackup (not sure if this captured my SMSs and notes)
Trying to avoid a wipe/flash back to stock (trying to preserve SMSs and notes) but realize this might be the only option. Much thanks to all who help.
You didn't run a nandroid backup before this?
Sent from my SPH-D700 using XDA App
Sadly no, I didn't even have Clockwork Recovery / ACSRecovery loaded. Thanks for your response!
Have you tried using an adb shell to push those files back?
Sent from my SPH-D700 using XDA App
Hmm...I'm a bit new to adb, but when I try adb pull /system/lib/libiq_client_old.so it returns error: device offline. Same with other adb commands. Thanks again!
tvh2k said:
Hmm...I'm a bit new to adb, but when I try adb pull /system/lib/libiq_client_old.so it returns error: device offline. Same with other adb commands. Thanks again!
Click to expand...
Click to collapse
Sounds like USB debugging was off or a bad cable. Also try other usb ports.
Sent from my SPH-D700 using XDA App
Possible USB debugging was off, though I do remember turning it on at some point in the past. Not sure how far in the boot process it needs to go before it can respond to adb commands. Is there a way to get a console-type debug output as it boots?
Will try other cables once I get home. Thanks for your persistence
Fixed!
New cable didn't work, but was able to load CWM Recovery and mount /system via adb. Thanks again for your help
what about odin back to stock ec05?
Sent from my SPH-D700 using Tapatalk
I bet you tried to use one of those detection/removal apps in the Market, rather than using k0nane's flashable mod for our device.
You honestly would've been better off just flashing a custom rom. If you were trying to stick with something as close to stock as possible, then there are custom options in the dev forum.
Glad you were able to get CWM going again and resurrect the phone.
Hi there i really need to know how to dump my current ROM
Cause i want to make a complete Backup (kernel etc) before starting to develop for this device.
Ive already searches sammobile and the whole XDA Forums but there is no
correct ROM for that phone
Base: I8150XXLB2
Kernel : [email protected] #3
Cmon guys is there a how to ?
wizzx said:
Hi there i really need to know how to dump my current ROM
Cause i want to make a complete Backup (kernel etc) before starting to develop for this device.
Ive already searches sammobile and the whole XDA Forums but there is no
correct ROM for that phone
Base: I8150XXLB2
Kernel : [email protected] #3
Cmon guys is there a how to ?
Click to expand...
Click to collapse
Do u mean making a Nandroid Backup of ur ROM? U can use CWM Backup
Check this out
http://forum.xda-developers.com/showpost.php?p=21424744&postcount=1
Thanks for your reply
I figured it out :
ADB Method:
Connect your phone to your computer via USB and make sure USB debugging mode is enabled in Settings >> Applications >> Development.
Open a command prompt window and enter the following commands:
adb push romdump /data/local/
adb shell chmod 04755 /data/local/romdump
adb shell /data/local/romdump
You might see some output of the above command. Wait until it finishes.
Enable and then disable Wi-Fi on your Android phone. If it was already enabled, disable, enable and then disable it again.
Type this command in the command prompt window on your computer:
adb shell romdump
Now i have to figure it out how to dum the : KERNEL.IMG
use cat prog command to determine the kernel img partition system etc etc then use adb to pull it. I forgotten the exact command but this is the way to back up the whole rom manually if I'm not mistaken.
why not use cwm? it automatically backup everything from kernel to boot img.
Thanks for your reply.
Cause i really got no plan how to cook a complete flashable standalone rom with the files cwm Recovery creates. This files looking strange to me.
I started rom creating with the archos htv2 tablet (completly diffrent)
As soon as possible i will work on new roms.
Usualy i dont need much time to get into it.
Thanks for your help.
wizzx said:
Thanks for your reply.
Cause i really got no plan how to cook a complete flashable standalone rom with the files cwm Recovery creates. This files looking strange to me.
I started rom creating with the archos htv2 tablet (completly diffrent)
As soon as possible i will work on new roms.
Usualy i dont need much time to get into it.
Thanks for your help.
Click to expand...
Click to collapse
Looking forward to ur New ROM. All the best~
Galaxy Nexus GSM........
I cannot connect via ADB to my phone. ADB shells but 'adb devices' none is found. Drivers are installed correctly per device manager. Debugging is on.
The only thing I've found in the forums is that I can't select 'none' as my USB connection. The two check boxes won't un-check only behave like radio buttons.
I have always had to use "fastboot devices". Not sure if that is what u are looking for.
Sent from my Galaxy Nexus using Tapatalk 2
Uninstall all drivers and install those from the naked driver thread over in development.
'fastboot devices' is used only when on bootloader.
Sent from my i9250
no luck
No luck. Always get 'no drivers for you phone found'. I guess I should have mentioned that I'm on W7/64 I did notice that mentioned a lot in the threads........ Any need to select the type of USB connection (none is not an option) ?
TIA, Jeff
getting there......
OK I am getting further. When I enter adb devices I can see my phone until I type 'adb reboot bootloader'. As soon as I enter that command the phone does reboot into the bootloader but the USB connection drops as well.
Jeff
Try this drivers bro
Galaxy Nexus AOKP m5 Franco kernel m3
[email protected] said:
OK I am getting further. When I enter adb devices I can see my phone until I type 'adb reboot bootloader'. As soon as I enter that command the phone does reboot into the bootloader but the USB connection drops as well.
Jeff
Click to expand...
Click to collapse
That is because you just installed the "adb" driver for your device. You still need to install the "fastboot" driver. It is the same driver, it just needs to be installed twice - once when your device is booted normally, and once when it is booted in fastboot mode. I personally would use the Universal Naked Drivers by 1wayjonny that bk201doesntexist mentioned, not the PDA drivers or Samsumg drivers or any other ones. 1wayjonny's drivers do not install any other software on your PC - they are just the drivers, unlike the PDA drivers.
Thanks all getting there. Thanks efrant that got me to the next problem .
I unlocked the bootloader and pushed su.zip no problem. Now I have flashed su.zip successfully but I don't have root. I have flashed many times with no luck.
Jeff
[email protected] said:
Thanks all getting there. Thanks efrant that got me to the next problem .
I unlocked the bootloader and pushed su.zip no problem. Now I have flashed su.zip successfully but I don't have root. I have flashed many times with no luck.
Jeff
Click to expand...
Click to collapse
Use the version of su.zip from this post. I just made it yesterday with the latest binary and app, so that one will work.
Thanks efrant that worked. I have root and installed busybox.
There was a really good terminal app that showed up when you flashed Cyanogen but I can't find it in the store. Does anyone know the name? The main thing that I need out of this whole endeavor is ssh and the terminal that came on CM8 and/or 9 was perfect.
Jeff
[email protected] said:
Thanks efrant that worked. I have root and installed busybox.
There was a really good terminal app that showed up when you flashed Cyanogen but I can't find it in the store. Does anyone know the name? The main thing that I need out of this whole endeavor is ssh and the terminal that came on CM8 and/or 9 was perfect.
Jeff
Click to expand...
Click to collapse
grab a cm9 nightly zip and extract apk from /system/app
pm setinstall location 2
if you want to set install location to sd card and move all apps to sd then read my thread http://forum.xda-developers.com/showthread.php?t=1754722
Bricked asus transformer prime
Hey i get the same message and i go to devices and it shows my device in fastboot mode but when i go to use the adb shell command and the adb devices it shows no tablet
can you please help
the system is wiped and data is wiped and i cant seem to get it to read my sd card
please help
thanks
NewDev4IOS said:
Hey i get the same message and i go to devices and it shows my device in fastboot mode but when i go to use the adb shell command and the adb devices it shows no tablet
can you please help
the system is wiped and data is wiped and i cant seem to get it to read my sd card
please help
thanks
Click to expand...
Click to collapse
what tablet? this here is galaxy nexus q&a forum, thread was created 2 months ago.
oh and adb isnt available in bootloader, only recovery and android. boot to recovery.
Sent from my i9250
Solution
[email protected] said:
Galaxy Nexus GSM........
I cannot connect via ADB to my phone. ADB shells but 'adb devices' none is found. Drivers are installed correctly per device manager. Debugging is on.
The only thing I've found in the forums is that I can't select 'none' as my USB connection. The two check boxes won't un-check only behave like radio buttons.
Click to expand...
Click to collapse
Make sure that you have your drivers properly installed. View this guide to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless : http://goo.gl/2Ehso
Hope it helps
ok, I am really in dead end here. I think I spent on it more than 4 days, trying to figure it out. No luck, hopefully someone here can help.
My One isn't recognized under adb fastboot. And what I mean: under device managers it shows that the device is installed fine ( no yellow exclamation marks ). But when I try to adb, no luck. No devices recognized.
wait.. before you refer me to gadzillions of links - I've been there, seen them. What I did so far:
1) Installed linux ( live cd and normal ). When in the OS, I can browse my sd card. Once I reboot into fastboot, adb devices returns empty list.
2) installed htc drivers, naked drivers, universaladb drivers, intel usb3 drivers ( tried on both usb2 and usb3 ports )
3) various laptops and pcs
no luck. I am running out of ideas. What am I missing ? pliz help, I am desperate to adb to update recovery.
PS. Tried that on windows 7, 8, 8.1 and linux
If your just trying to update your recovery you can use flashify from the playstore.
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
mercer24 said:
If your just trying to update your recovery you can use flashify from the playstore.
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
Click to expand...
Click to collapse
checking it right now. thank you
ah, didn't work. But thank you for help. Returning the phone to the store today.. ehhh..
pRuben said:
ah, didn't work. But thank you for help. Returning the phone to the store today.. ehhh..
Click to expand...
Click to collapse
I don't recall seeing it mentioned in any of the recipes, cookbooks or how-to postings, but I found that in Linux, you should run your adb and fastboot instructions either logged in as root, or using sudo.
Make sure you don't have any phone software installed on the computer as well. HTC sync and Kies can cause problems with adb. Also make sure that adb debugging is turned on in developer settings. You probably already did that, but ya never know, I overlook the simple stuff all the time.
did you take 4.3 update
If you did I have same issue with adb but fastboot options work just fine as long as your s-off if you need any help let me know i went and reloaded hboot and a cwm and also wrote my cid to super and unlocked through htc dev then changed my cid back to verizons
thanks guys, yep, HTC sync manager was installed /uninstalled. Not sure what what's kies. Also I executed sudo on linux. Nothing freaken works. I am s-off unlocked via sonic. Drives me insanely mad. Seems like this phone just refuse to work with me.
I know this might seem like a dumb idea but have you tried a different cable? Are you using the one that came with the phone?
I don't know you so forgive me if what follows is too simplistic or unrelated to your issue. Just trying to help.
You mentioned your phone is not recognized "under adb fastboot." Do you mean under neither adb nor fastboot?
Are you trying to use adb from the bootloader? The reason I ask is you mentioned that after you "reboot to fastboot," adb devices comes up empty. I assume "reboot to fastboot" means reboot to bootloader, in which case adb commands will not work. Did you try fastboot devices instead?
You also mentioned wanting to get adb working to update recovery, but again this would require fastboot, not adb.
Hope this is the problem as it's an easy fix!
Sent from my HTC6500LVW using xda app-developers app
xenakis said:
I don't know you so forgive me if what follows is too simplistic or unrelated to your issue. Just trying to help.
You mentioned your phone is not recognized "under adb fastboot." Do you mean under neither adb nor fastboot?
Are you trying to use adb from the bootloader? The reason I ask is you mentioned that after you "reboot to fastboot," adb devices comes up empty. I assume "reboot to fastboot" means reboot to bootloader, in which case adb commands will not work. Did you try fastboot devices instead?
You also mentioned wanting to get adb working to update recovery, but again this would require fastboot, not adb.
Hope this is the problem as it's an easy fix!
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Once in a while I get humbling experience, that reminds me that simple solutions are right in the front of me Xenakis. You are correct, I was trying to get adb under fastboot, which didn't return anything. Fastboot devices did. From there it was all straight up road to what I needed. Sorry to bother you guys with this, I though it was more complicated that this. It just appears like my ignorance of basic adb commands got the best of me. Thank you for helping me out.
Merry Christmas