Hello guys i ported rom 4 my device and i have bootloop. When in cmd type "adb devices" i have message 4 verifing. But when i type "adb logcat", "adb logcat -f logcat.txt" or etc. i have message -waiting for device-. I tried with AIO Logcat but, i get this : http://prntscr.com/1rp25l
with adb logcat i gotta this http://prntscr.com/1rp2h6
Any help ? Thanks in advance.
As you can see, when you type adb devices, your device appears offline. Maybe this is caused by your ROM, maybe not, but you need to solve it first (I dunno how to do it, sorry).
Maybe you can find the problem with the Dalvik Debug Monitor (DDMs). It's part of the Android SDK.
See this thread:
http://forum.xda-developers.com/showthread.php?t=2304122
Thanks but not working "DDM"
As long you keep getting offline when you type adb devices, anything will work. As I said before, you need to fix that problem first.
I don't know how to do that !
Related
I've got an Iconia tablet with a broken recovery (I've been using CWM and Thor's ICS ROM). I'm going to follow the steps outlined here
http://forum.xda-developers.com/showthread.php?t=1129873
but.... when I look up the UID from every method, all I get is 0123456789ABCDEF.
Given all the dire warnings about not being able to recover if/when things go wrong without the real UID... this 123 UID isn't the real UID.... is it safe to proceed with the repair here? Or are things really messed up?
I have not messed with ICS myself, but my understanding from reading the ICS threads in the Iconia forums is that the device is no longer using the uid for usb serial number. So it seems you can't get it that way if you have installed any of the ICS updates.
The suggestion I have seen is to look for androidboot.serialno in dmesg directly after booting, but that does not seem to help everyone.
Another option might be to get the device into APX mode and do a usb bulk read, the first read should return 8 bytes that is the UID. I would assume this to still work even after you have installed ICS but I have not tried. I pasted some code for opening the device, reading and printing the uid (using libusb, tested on Linux) on the Iconia forum earlier this week.
Hmm OK that's helpful info. Thanks.
I tried the androidboot.serialno in dmesg, but I wasn't able to find the string.... I will try that again after a clean boot.
I've been doing all the debugging from my one Windows machine... I haven't tried plugging it into my Linux PC yet... that's next... I haven't discovered APX mode yet. Time to do some more reading, thanks for the pointers.
Edit 1: OK checked lsusb -v and I serial also shows 0123456789ABCDEF
Edit 2: Clean boot and did a new dmesg dump.. parsed the output and no sign of androidboot.serialno or anything that even resembles it.
OK, things are not getting better here. I've been tinkering a lot, and in some respect I've just made things worse.
I still cannot find the UID with any of the documented methods here on XDA. I've tried
using adb devices
using Linux lsusb -v
checking the output of dmesg for androidboot.serialno
plugging in to Windows and looking at the USB mount info using USBDeview
looking at the device manager in Windows and checking the "Parent" field
I have also booted into APX mode and to discover the UID that way too... and nothing.
All I get is 0123456789ABCDEF
At this point the frustration level was getting high enough for me to be a bit reckless... I copied "itsmagic" into /data made it executable and ran it. No errors.
I rebooted into Recovery mode, and there I get scrambled graphics on the screen (it's the Acer logo duplicated several times with loads of tearing and distortion) and the tablet vibrates constantly.. non stop until I reboot it.
I can boot normally into the current ROM (Thor2002ro v96) so I haven't busted it completely. If I try to use my existing CWM manager to install any other ROM or use the manager to reboot into recovery mode, it goes back to the scrambled screen and vibrating constantly.
Does anyone have any ideas or suggestions here? I'd be happy to even roll back to stock and start fresh. There is nothing on the tablet that needs to be saved... except the functionality of the tablet itself.
When you write nothing about APX mode, does that mean literary nothing or nothing different?
If you have root you can see if you have anything interesting in /proc/cmdline.
If not I'm out of ideas on how the get the UID for now.
While i very much doubt 0x0123456789ABCDEF is the UID used to generate the SBK of the device you could try reading and decrypting the beginning of mmcblk0 using the SBK that would give (0xA9EA7E00 0xF12BEB06 0x3AD20804 0x364A5F03) to verify this.
You could probably overwrite the restore partition from your running system, I have never done that myself though.
OK, it's SOLVED.
After much swearing and crying and a little help from the forum here and in other posts the solution to fixing the broken tablet was actually quite easy.
Based on the information here:
http://forum.xda-developers.com/showthread.php?t=1459821
- I downloaded recovery-ra-iconia-3.16-gnm.img using teh links provided on the thread above
- I ran itsmagic
- Then I did these steps:
Code:
adb push recovery-ra-iconia-3.16-gnm.img /mnt/sdcard
adb shell
su
dd if=/mnt/sdcard/recovery-ra-iconia-3.16-gnm.img of=/dev/block/mmcblk0p1
sync
reboot recovery
This booted a working recovery mode (FINALLY), and I was able to successfully flash the latest Thor2002ro ICS ROM.
Thanks for your help and suggestions eppeP, they got me thinking in the right direction.
Hello guys I am trying to bypass screen lock via adb but when I write adb devices it shows "0123456789ABCDEF Device" and then when I type adb shell then it shows"$" after that whatever I type it shows permission denied(even if I write adb).Please Help
please clear up Google
account lock
whats up guyz im new/old to this forums new/old means , i dont get online to much
well i have been tweaking a little bit with my droid DNA and found out some work around for some problems people might be having trying to unlock their bootloaders
the first problem i encountered was the adb killing process , adb is out of date . there is a little work around for this , that worked with me and my friend s DNAs to resolve this we just killed the adb daemon with this command
adb kill-server
then we started the server with the command
adb start-server
allright . the only way you will not get that error of adb out of date is , if you see adb starting on some port . i forgot the port number, but thats the only way you will not be getting the error ..
the second problem i encountered in the process of unlocking my phone was the restore update not finishing , which was caused by the bug of adb out of date error. once you resolve the problem with the adb bug out of date error , then you will be able to restore the phone successfully
but hold on , there is another problem some people might be getting , when you execute the command " adb restore backup.ab " if your device is taking to long to finish the restore and the window is behind looping, dont worry about it just wait couple of minutes control -c on the window looping and control -c on the window that you waiting on the restore to finish ... i tried that couple of times then i figure that the restore did go thru ..
some people might be getting an error with this command "adb shell mv /data/DxDrm /data/DxDrm_org" if you getting the error that says failed to blah blah blah permission denied , the cause for of that error is that the restore didnt go thru . if you got that error you can reboot safely , your device is not bricked yet lolz ..
when you get to the section that you have to repeat the exploit again , you gonna start getting the error again with the adb killing the process out of date thingy , dont worry just redo the work around i posted above , i control c the restore window and the loop window
couple of times just to make sure it was working fine , and it did . it was working fine
sorry for my english guys . i just wanted to point out those little flaws in the process of unlocking the bootloader , just in case some people get the same errors , they wont have to break their heads with it ... blessed be ..
Minor audible...
I was using the video made by DroidModderX and was able to get through it basically step by step with one minor hiccup. One the step where you start the first command prompt to do that "loop of errors" and move to the second command prompt, my system had an error doing this until I unplugged the phone and plugged in again. That wasn't mentioned in the tutorial but worked great once I did that part. It seemed like ADB got a little screwed up or something but, once I unplugged/ replugged it all worked normally. One other thing I noticed was that in the video (he uses a mac) the first command prompt continues to "loop" until you hit CRTL + C and on mine as soon as did the command in "prompt 2" the loop stopped on its own although all of the commands still worked as planned. I was doing this on Windows7 32bit. Hopefully that makes sense or is helpful to someone...
all you had to do was kill, then restart adb? that's not doing the trick for me, damn
EDIT: I got mine to work by uninstalling HTC Sync, it has an adb.exe file that was causing the error
I was able to leave HTC Sync installed but I had to uninstall Droid Explorer from my Incredible days. Only then did the ADB out of date error stop.
I used this before with HTC Sync. Maybe that is why I was able to keep it installed.
The attached zip is from http://visualgdb.com/adbfix/
adb logcat read failure. hi guys i can't get logcat using adb. I've installed samsung driver . when i type adb devices i can see that my device is there but can't figured out why i can't get log.
S7
sac23 s9 port rom
Hello fellows...
I have a problem i never encountered before ...
If I try to connect to my phone by using "adb shell" I only receive this message:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
I know, I am "just" not authorized ... but thats my problem!
The phone never asks for granting the permission ...
And I can't revoke any "granted" permissions, since my dev-menu is missing this point.
About my system:
I am running windows 10 with adb 1.0.39, fastboot is working without problems.
My phone is a Cubot X18 Plus running a treble GSI of Ressurection Remix 6.2.1 (Oreo 8.1).
Since other gsi/roms are able to use this, I would even consider the gsi as the problem, but it seems to be dead since it is oreo, but I posted in the thread anyway.
I have lost my device serial number (now 1234567ABCDEF) but this shouldn't be a problem, since it is working on stock rom.
Is there any way to get adb rights granted? Or get the menu action back to revoke all granted devices?
I can use the local shell without any problems, at least I get root access over there.
Greeting
houston
I have written a blog about how to manually add adbkey.pub to phone.
There are termux with root and TWRP on rootless phone methods.
murtezayesil.me/adb_vendor_keys-is-not-set.html
I have returned to stock, since no custom rom really worked.
But tanks for your answer, maybe other ppl will be able to use your post.
I have an LG V30 (LG-H933, Android 8.0.0, no root) and I'm trying to view the log using "adb logcat" from a Mac. The device shows up when I connect it with a USB cable and I can adb shell into, pull files off, etc. However, adb logcat does not show any output. There are no errors or warnings or anything like that. I have tried restarting the device and restarting the adb server but that didn't fix anything. Have any of you run into this issue or know how to fix it?
EvilBoz said:
I have an LG V30 (LG-H933, Android 8.0.0, no root) and I'm trying to view the log using "adb logcat" from a Mac. The device shows up when I connect it with a USB cable and I can adb shell into, pull files off, etc. However, adb logcat does not show any output. There are no errors or warnings or anything like that. I have tried restarting the device and restarting the adb server but that didn't fix anything. Have any of you run into this issue or know how to fix it?
Click to expand...
Click to collapse
What are you trying to see on ADB?
LG has removed most of that ADB/fastboot functionality on North American variants -- which is why you have to Frankenstein Canada H933 to US998 (at least temporarily) for bootloader unlock.
I understand you may not be interested in bootloader unlock and root, but that's probably why you can't see anything on ADB.
I don't know anything about Macs, so that's my best guess.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
What are you trying to see on ADB?
LG has removed most of that ADB/fastboot functionality on North American variants -- which is why you have to Frankenstein Canada H933 to US998 (at least temporarily) for bootloader unlock.
I understand you may not be interested in bootloader unlock and root, but that's probably why you can't see anything on ADB.
I don't know anything about Macs, so that's my best guess.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
I am able to use adb, it's only the logcat command that's not properly working. "adb devices", "adb shell", "adb pull", etc., all work as expected so it's not the case that nothing is working through ADB.
EvilBoz said:
I am able to use adb, it's only the logcat command that's not properly working. "adb devices", "adb shell", "adb pull", etc., all work as expected so it's not the case that nothing is working through ADB.
Click to expand...
Click to collapse
I can't tell by your posts, but u do know how logcat works? You need to start it, then stop it. Then look at the output. There are parameters for starting it which can control what to log (errors, warnings, etc). Usually people start the log, then do the sequence of events (that aren't working and they want to see a log for), then stop it. Then view the log for reasons it's not working.
Not sure if that's any help, but if it does, it's better explained by searching for something like 'android how to do a logcat'.
Cheers
AsItLies said:
I can't tell by your posts, but u do know how logcat works? You need to start it, then stop it. Then look at the output. There are parameters for starting it which can control what to log (errors, warnings, etc). Usually people start the log, then do the sequence of events (that aren't working and they want to see a log for), then stop it. Then view the log for reasons it's not working.
Not sure if that's any help, but if it does, it's better explained by searching for something like 'android how to do a logcat'.
Cheers
Click to expand...
Click to collapse
I appreciate the reply but yes, I do know how logcat works
I was able to get past this issue by using the version that comes with Xamarin Forms.
Non-working:
adb --version
Android Debug Bridge version 1.0.41
Version 29.0.1-5644136
Working:
adb --version
Android Debug Bridge version 1.0.40
Version 4797878