ADB doesn't work on custom rom?! - Android Q&A, Help & Troubleshooting

Today I build my first (working) android rom based on CM.
When booted up the process com.android.phone keeps on crashing every second or something, I tried to use adb logcat but it keeps waiting for a device.
In the windows device manager I don't see a new device and when connecting over the network I get an error: protocol fault (status read)
Any suggestions at what it could be?
The rom that is currently running has been continued from where it errored out, I am rebuilding it now.
I will keep you up-to-date
Thanks,
Tim

Related

[Q] Wifi keeps on "Turning on wifi" and doesn't connect

Hello there and please excuse me for my bad english! As the title says, I can't connect to wifi network. Well, I can but it just work sometimes and works weird. Here's the scenario:
MIUI 3.6.7 rom on a Motorola Atrix 4G.
Android 4.1.2 JZO54K
Baseband N_01.77_38P
Kernel 2.6.32.60-MB860-CM10-ged7b511
On last sunday I tried to connect to a open wifi network, all week I was connecting to my home network. The status of wifi kept on "Turning on wifi..." for a while, but nothing happened. I restarted the phone and happened the same thing. At home, the connection worked but suddenly it closed for no reason. I tried to connect it again but kept again on the "Turning on wifi..." thing and suddenly the phone restarted! Not enough, it got stucked on the very first screen (the one with the "unlocked" text and Motorola logo), so I had to do a battery pull.
I've wiped Dalvik cache, cache partition, did some full wipes, installed again the rom (I was on 3.5.31 for then, updated yesterday to 3.6.7 and still the same), changed the Baseband, installed another kernel and I'm in the same situation. It's driving me crazy.
Got a logcat with Catlog, and found some (maybe interesting) lines (you can find the whole file in ge.tt/36KSn9j/v/0 -- sorry for be unable to post a link or uploading a file here):
06-11 15:21:54.508 W/CommandListener(1415): Failed to retrieve HW addr for eth0 (No such device)
06-11 15:21:54.508 D/CommandListener(1415): Setting iface cfg
06-11 15:21:54.508 E/WifiHW (1714): Unable to open connection to supplicant on "eth0": No such file or directory
06-11 15:21:54.508 I/wpa_supplicant(11001): rfkill: Cannot open RFKILL control device
06-11 15:21:54.508 E/wpa_supplicant(11001): Could not read interface eth0 flags: No such device
06-11 15:21:54.508 E/wpa_supplicant(11001): WEXT: Could not set interface 'eth0' UP
06-11 15:21:54.508 E/wpa_supplicant(11001): eth0: Failed to initialize driver interface
06-11 15:21:55.508 E/WifiHW (1714): Supplicant not running, cannot connect
06-11 15:21:59.508 E/WifiStateMachine(1714): Failed to setup control channel, restart supplicant
Googling about this got me to this thread (drakaz.com/forum/viewtopic.php?id=120... again sorry for the links thing) and got me thinking why the net interface is listened as 'eth0' and not 'wifi0' or something. I'm pretty noob to Android but I'm sort of an average GNU/Linux user, so I checked for what is going on in the dhcpcd.conf file and founded there the hostname was writed as 'wifi0' so I changed to 'eth0'... but this thing is still the same. Can you give me a clue about what the hell is going on? Thank you so much!
Make a nandroid backup and try a different ROM (preferrably a GB/CM7 based one).
ravilov said:
try a different ROM (preferrably a GB/CM7 based one).
Click to expand...
Click to collapse
Thank you so much for your answer! I tried CM7 (both stable and nightly, I heard the last one was a bit more stable than the first one) doing full wipe, of course. But when restarting, on both cases they only reached the very first screen (the one with the Motorola logo) and after like 5 seconds the phone rebooted automatically.
The thing is I really don't want to change MIUI. I've been using it since august, 2012 and I'm in love with it. This is the first time I got an issue so serious. Is there anything else I can do? Thank you so much!
No idea really. I'd tell you to do a full wipe before flashing but you've done that already. The only thing I can think of is flashing MROM (since its kernel has early USB enumeration) and then trying to pull out some more logcats very early on. This is quite a weird error and working out a solution will definitely involve a lot of creative thinking.
ravilov said:
No idea really. I'd tell you to do a full wipe before flashing but you've done that already. The only thing I can think of is flashing MROM (since its kernel has early USB enumeration) and then trying to pull out some more logcats very early on. This is quite a weird error and working out a solution will definitely involve a lot of creative thinking.
Click to expand...
Click to collapse
After the millionth full wipe I just got to install CM7 nightly and a clean reboot. But the wifi thing is still there... Well, a fc popup dialog appears after like 10 seconds: "Sorry! Application Settings (in process com.android.settings) is not responding.". I'm going to install MROM and catch a logcat, will be back then with a logcat. Thank you so much!
So I finally could get MROM working (I guess the thing about all GB roms rebooting when are just installed is about CWM). There's still the same thing I got with CM7. I have a logcat under MROM, and another I catched before I flased MROM (using MIUI v5): As I couldn't got MROM working just after wiping all when I was with CM7, I tried flashing MIUI. It flashed normally and at startup wifi was working, but after a while the connection closed suddenly. I got a logcat from that.
So the logcat with MIUI v5 (2013-06-14-02-26-28.txt) is here: ge.tt/6AQdiSj/v/0
And the logcat with MROM (2013-06-14-15-32-55.txt) is in ge.tt/7slxiSj/v/0
Hope this can help, I will keep pending so if you want to know something just let me know. Thank you so much for your help!
Seems that this is a problem about planned obsolescence. I'm such a noob, I hadn't seen this thread before (http://forum.xda-developers.com/showthread.php?t=1656760) where they explain many people had this issue. I can't post to that thread, but seems that they never got their wifi working again as I do sometimes. This is the weirdest s**t I've ever had with an electronic device.

Build PA for M7ul -> permanently reboots

Hi there,
trying myself on compiling my "own" PA Build for my HTC one.
Basically i found everything i needed and get the build completed.
Compared to the builds from @slick_rick, my look very similar.
But after installing the rom on my One it reboots after a couple of seconds while updating the apps.
So i wiped the one and tried again. I could select the language and hit next. Again reboot.
Already switched from BBQ Linux to Ubuntu, but the problem stayed the same
Any help is appreciated. Maybe someone can point me a direction where to find somekind of logfile,as adb does not seem to be activated that early after device boot/initial setup.
THX
Chaos

unavoidable "unfortunately the process com.android.phone has stopped"

Hi all, first of all apologies for my English ...
I have single micro sim MTK6575 I9300 800x600 Android version 4.1.19.
I tried to make do with the problem of synchronization gmail contacts and it tried to install gapps-ics-20120429-signed.zip via CWM and I returned "Error: Invalid OTA package. Missing scatter ..." probe with other versions of gapps error and gave me Signature error ...
So much reading I found behind a guy who sent the files in System had to be replaced and how many people appreciated, so I follow his advice and I copied those files ... I went to restart the message "unfortunately the process com.android.phone has stopped" very often and the phone was very unstable ... but yes, Android show me the possibility of synchronization my contacts ...
On another forum I read that this was enough to get right to make a "wipe cache partition" from recovery mode ... so in my ignorance, I did ....
The result is that the message "unfortunately the process com.android.phone has stopped" appears continuously, to the point that I can not even finish the setup tutorial... now I have a mobile where I can't do anything...but it's fine.
I have a ROM, but I SP_Flash_Tool_v3.1224.01 doesn't recognize the phone (I can not access USB debugging Setting up for your Android device) in my PC the driver is installed beacause yesterday I tried.
- I have a rom not recognize the Recovery mode to put it from "apply update from sdcard2"
Nor do I have a cwm with gapps that the recovery mode accepts.
I do not know if I'm missing something ... but the truth is that after so much error I'm pretty sure I'll brick my phone in my next try..
I would appreciate thoughts .. for sure in my ignorance I'm having an simple option ... I have the opcion of spend two days more reading about to make the convert Stock ROM flashable ZIP
Thanks in advance
Finally I get a ROM and back to 4.1.19 no syncronize contact but no crash with continuos "unfortunately the process com.android.phone has stopped" errors
If somebody know how to fix not sincronize I apretiate too much
For SP flash tool you need the correct drivers and here is the site to install the ADB drivers or you can search over the Internet its easy to find......
Can you get to the settings? Then go there and wipe the data and cache of phone and contacts under application settings
maybe you can get out of this mess:good:

[Q] AOSP Builds keep freezing

Hi Guys,
I'm currently in the process of building AOSP to just flash a basic image onto a Nexus 7.
I've done the "repo sync" to get all the relative files, and have initialized the build environment exactly as the tutorials on the Android development site asks, including downloading proprietary drivers, however whenever i'm trying to do my first "make", it either gives me an error saying a random make file received a kill signal, or my machine just freezes.
As of writing this a build has been going for 7 hours (Is this normal?) and the machine just freezes up.
Any help/advice would be greatly appreciated, i'm unsure of how to try and fix what's happening
Jay

Cynogenmod on Nexus 4 on a permanent loop!

Yesterday I updated a nightly build (cm-13.0-20151222-NIGHTLY-mako.zip) and unfortunately the phone began to show a series of problems (ouldn't make calls,couldn't access the contacts,...).
Reading on the internet i found many people suggesting to downgrade to a working build, so i downloaded the last one that was working on my phone (3 days earlier 12/19): the nightmare began!
After the boot, the phone (nexus 4) shows repeatedly "Unfortunately the process com.android.phone has stopped" and when i click on "ok" it just pops up again and again, until it automatically reboots, and the whole thing goes on for ever.
If i don't touch the phone it reboots automatically until the batteries are completely dead.
I have tried to adb push from bootloader but the terminal (from ubuntu) hangs there without signs of life. If i open nautilus and I try to copy the new build, my ubuntu freezes, only the mouse works without any use.
Is there a way to miraculously solve this problem?
shared_joy said:
Yesterday I updated a nightly build (cm-13.0-20151222-NIGHTLY-mako.zip) and unfortunately the phone began to show a series of problems (ouldn't make calls,couldn't access the contacts,...).
Reading on the internet i found many people suggesting to downgrade to a working build, so i downloaded the last one that was working on my phone (3 days earlier 12/19): the nightmare began!
After the boot, the phone (nexus 4) shows repeatedly "Unfortunately the process com.android.phone has stopped" and when i click on "ok" it just pops up again and again, until it automatically reboots, and the whole thing goes on for ever.
If i don't touch the phone it reboots automatically until the batteries are completely dead.
I have tried to adb push from bootloader but the terminal (from ubuntu) hangs there without signs of life. If i open nautilus and I try to copy the new build, my ubuntu freezes, only the mouse works without any use.
Is there a way to miraculously solve this problem?
Click to expand...
Click to collapse
use fastboot to manually flash the stock partitions, then it will be clean stock, and you can start over.
search google for how to setup fastboot on your linux machine if you dont know how, i cant help with that.

Categories

Resources