Hi
I've been using the Omni roms since about 26th Dec 2013 and updating every few days without any issues.
Today I updated and I cant make calls/ its showing as not connected to a network. When I look in the about phone section it says baseband:unknown. If I restore my original samsung image I don't have any problems, sms/calls/mobiledata work normally.
There is a mention on the main page about a baseband issue, I'm assuming this is what I am experiencing. I've tried to run the commands as per the first page but I keep getting errors.
Commands are -
adb reboot && adb wait-for-device && adb root && sleep 2 && adb shell cat /proc/kmsg | tee kmsg_baseband.log
adb reboot && adb wait-for-device && sleep 2 && adb logcat | tee logcat_baseband.log
I've downloaded fastboot adb and am running these commands via windows cmd. I'm getting an error such as "unknown command, sleep not supported" something like that..
Can someone please help me run these commands and/or assist in fixing this issue.
Cheers
same issue
mouzzi said:
Hi
I've been using the Omni roms since about 26th Dec 2013 and updating every few days without any issues.
Today I updated and I cant make calls/ its showing as not connected to a network. When I look in the about phone section it says baseband:unknown. If I restore my original samsung image I don't have any problems, sms/calls/mobiledata work normally.
There is a mention on the main page about a baseband issue, I'm assuming this is what I am experiencing. I've tried to run the commands as per the first page but I keep getting errors.
Commands are -
adb reboot && adb wait-for-device && adb root && sleep 2 && adb shell cat /proc/kmsg | tee kmsg_baseband.log
adb reboot && adb wait-for-device && sleep 2 && adb logcat | tee logcat_baseband.log
I've downloaded fastboot adb and am running these commands via windows cmd. I'm getting an error such as "unknown command, sleep not supported" something like that..
Can someone please help me run these commands and/or assist in fixing this issue.
Cheers
Click to expand...
Click to collapse
Hey i'm also facing this issue. Can someone reply.
jsjagdey said:
Hey i'm also facing this issue. Can someone reply.
Click to expand...
Click to collapse
I went to cyanogen mod. It has happened once on cm but restoring the backup/wiping caches and reapplying the update sorted the issue.
U could try that process.
Bug reports belong on JIRA, and we can't help you because:
WE ARE NOT TELEPATHIC AND CAN'T READ YOUR MIND TO FIGURE OUT WHICH DEVICE YOU HAVE.
Hey sorry for not mentioning the device number. I'm using Samsung galaxy note GT n7000 omni rom 4.4.2 20140430 nightly
Sent from my GT-N7000 using XDA Free mobile app
Hey can reply. Now u know my handset details. Sorry for last incomplete post.
Sent from my GT-N7000 using XDA Free mobile app
jsjagdey said:
Hey can reply. Now u know my handset details. Sorry for last incomplete post.
Sent from my GT-N7000 using XDA Free mobile app
Click to expand...
Click to collapse
I'll try and update my N7000 this weekend to see if I can reproduce this - but I would have expected to see a lot more posts if it were broken for everyone.
Hi Entropy512 any update?
Sent from my GT-N7000 using XDA Free mobile app
Related
I saw a quick cmd fix for this recently, but cannot find it now anywhere in the forums. Anybody remember how to reconnect the device to adb?
Thanks in advance,
Rugger
sudo -i //makes you super user
cd /dir/of/androidSDK/tools
./adb remount
./abd shell
I guess I should mention that I'm running through windows, and don't have ubuntu
Ensure USB Debugging is enabled:
Settings -> Applications -> Developement -> USB Debugging
Windows what, what OS r u running? If its win7 use vista drivers to update. Worked for me
-------------------------------------
Sent via the XDA Tapatalk App
i have adb set up on my linux mint box adb works for all my other devices except the fire. jcases method seems quite easy buite it wont recognize my device any help. and yes I have java and sdk and everything installed perfectly ive been searching many hours with no solution any help is greatly appreciated im not a novice to adb or rooting but this is driving me crazy please help. thanks im oon 1.6.2 by the way
Find one of the old guides to rooting, with instructions on getting it recognized by adb. Mostly need to edit a config file, iirc.
Sent from my Kindle Fire using xda premium
oxlong27 said:
i have adb set up on my linux mint box adb works for all my other devices except the fire. jcases method seems quite easy buite it wont recognize my device any help. and yes I have java and sdk and everything installed perfectly ive been searching many hours with no solution any help is greatly appreciated im not a novice to adb or rooting but this is driving me crazy please help. thanks im oon 1.6.2 by the way
Click to expand...
Click to collapse
adb kill-server
sudo -s
adb devices
---
or add it to your udev rules
jcase said:
adb kill-server
sudo -s
adb devices
---
or add it to your udev rules
Click to expand...
Click to collapse
What exactly do I add to the udev rules in my 51. Android rules? Any way someone can type it exact so I can copy and paste? I never ran into issues like this usually rooting my devices on Linux is smooth as butter. Thanks jcase
Could u elaborate a little I'm a little new to linux
Sent from my ADR6425LVW using xda premium
i have done everything correct i have been at this all day! in cmd it says device not found and i have tried adb kill-server > adb start-server > adb devices and i get nothing
Install pda net on pc with nexus hooked to usb and it will install drivers for u.
Sent from my Nexus 7 using xda premium
Since we already have Android 4.2 working on HD2, is there a way we can port Ubuntu on it as instructed below.
http://blog.gsmarena.com/canonical-releases-ubuntu-and-android-dual-boot-developer-preview/
The steps are listed in link below
https://wiki.ubuntu.com/Touch/DualBootInstallation
If someone can do it on our dear HD2, that would be awesome..:good:
"Someone". If you're so interested, why won't you give it a try? Definitely won't hurt. Maybe you'll learn something new, even if you don't succeed.
Hey Guys, how are you?
I tried port this before but no luck, when it boots, the boot stuck in black screen and red square in the center I can move it by touch.
IAMLEGENDZ said:
Hey Guys, how are you?
I tried port this before but no luck, when it boots, the boot stuck in black screen and red square in the center I can move it by touch.
Click to expand...
Click to collapse
i too wanna try it but not able to find the tool..:crying:
stucks in detect_device() { - method
DEVICE=$(adb wait-for-device shell getprop ro.product.device)
this returns 'leo'
I have started from computer via adb shell:
adb shell "sh /NativeSD/ubuntu/dualboot.sh FULL" (as described on canonical website )
After I checked the sh script I have tried also this (with same result)
adb shell "sh /NativeSD/ubuntu/dualboot.sh INSTALL_SU"
In both cases the scripts stucks with comment:
"Connect device to install Ubuntu installer to."
which is at the beginning of the shell function "detect_device() {"
So it stucks in thes function.
I have thought now to change the shell script:
instead of the line: DEVICE=$(adb wait-for-device shell getprop ro.product.device)
I would try: DEVICE=$(mako)
so it should end up in the if statement:
if [[ "$DEVICE" == mako* ]]; then
echo "Detected connected Nexus 4"
RECOVERY_URL=$URL_CMW_PATH_MAKO
Any other ideas? Had anyone success in installing dual boot on HD2 or other threads/ ideas?
Hi Folks,
I'm trying to send AT command and retrieve it's output via adb shell or an app.
I tried several stuff I already found here, like service ATFwdCmd but it didn't exist in MTK device.
I found with getprop that the "baseband" device must be on /dev/ttyC0 but on my device it didn't exist.
output of getprop
[rild.libargs]: [-d /dev/ttyC0]
[rild.libpath]: [/system/lib/mtk-ril.so]
So I started reversing the mtk-ril.so and found that there is a "property_get("mux.debuglog.enable")", and I tried to set this property with setpropex but it's not working too.
I tried using atinout tool at sourceforge with echo 'at+cops?' | atinout - /dev/ttyGS0 -. I also tried the MTK Engineering App and tried to enable full modem log, without luck again.
I'm stuck at here now, if anyone has an idea, i will be very happy to speak with him
PS: sorry for my bad english
Cheers,
Jon
hi, did you solved this ?
I also need to send AT commands on a MTK device, but I have no luck .
Using "cat /dev/pts/4 &" & "echo -e 'ATI\r' > /dev/pts/4" approach gives me no predictive response (the output is sent to logcat and ...partially to the above background process (even when calling "stop ril-daemon", i suspect this is doing nothing, the mtkrild process is still running, killing the mtkrild ..is no solution, the connectivity is lost).
Is there any reliable way we can use mtkrild directly to send AT Commands "