We are looking for users that is still on STOCK ROM and Kernel. BOTH AT&T and Roger. We are trying to see what errors are in STOCK so we can crush out bugs we might have introduce in modified Kernel or ROM
If you are a user still running STOCK ROM/KERNEL please run this command and post your dump.txt files
adb logcat -d *:E > dump.txt
You must have adb running. USB Drivers installed either by KIES package or Samsung USB Package, ADB should be in your folder if you used Zergberg Root method. Or can be downloaded via the Android SDK package
Your help will only future help the developing
mbze430 said:
We are looking for users that is still on STOCK ROM and Kernel. BOTH AT&T and Roger. We are trying to see what errors are in STOCK so we can crush out bugs we might have introduce in modified Kernel or ROM
If you are a user still running STOCK ROM/KERNEL please run this command and post your dump.txt files
adb logcat -d *:E > dump.txt
You must have adb running. USB Drivers installed either by KIES package or Samsung USB Package, ADB should be in your folder if you used Zergberg Root method. Or can be downloaded via the Android SDK package
Your help will only future help the developing
Click to expand...
Click to collapse
Here ya go
oh ok lol thank u i found it dugh
silver03wrx said:
im trying to do this i keep getting the message the process cannot access the file because it is being used by another process?. i did adb kill-server then adb start server it started then i typed in adb logcat -d *:E > dump.txt. and i can not find the dang text file on my sd card lol sorry have not used adb much
Click to expand...
Click to collapse
the text file will be located in the directory where you ran the command from and not in the sdcard or in the phone
ok thanks bud here ya go
Attached my dump file.
I may need to google some of the crap that was in it.
Hey Guys,
here is the stock kernel from XXKQ7 including init.d and custom bootanimation support.
Root and Busybox needed
HOW-TO
1. Download one of the following zips
2. Put the zip on your internal SDCard
3. Shut down your phone
4. Go into Recovery-Mode: First power off your Phone, then hold Power + VolumeUp. Release the two buttons 3 seconds after the samsung logo is shown.
5. "install zip from sdcard" -> "choose zip from internal sdcard" -> "stockkernel_init.d_bootanimation_KQ7"
6. Reboot your phone
Downloads
KQE Kernel
KQB Kernel
KQ7 Kernel
Further Instructions
1. Create /system/etc/init.d place some script in it or flash any other init.d script package
2. To change the bootanimation place your favorited sanim.zip in /system/media/
After that you can flash Thunderbolt or AdrenalineShot and use their advantages.
Please give some Feedback it is working correctly because im really new to this stuff. I have a GT-I9001 and at the moment everything seems to run as it should. I had no bootloops as it sometimes was the case with FeaMod or N00b.
what’s this kernel‘s CPU frequency ，OC?
Why you are concerned?
Sent from my GT-I9001 using XDA App
crybert said:
Why you are concerned?
Sent from my GT-I9001 using XDA App
Click to expand...
Click to collapse
sorry, some mistakes in front of my words
Nice, been looking all over for stock kernel..How its prforming? Im currently on latest feacore, with batt drain all the time. Can u post ur batt stats pic?Would love to have usable phone than some short lived super fast phone..
Nice man......thansk is ok on my phone.
can i use it on another phone???
safwanjin said:
can i use it on another phone???
Click to expand...
Click to collapse
u can't be serious , right ?
safwanjin said:
can i use it on another phone???
Click to expand...
Click to collapse
I'm soooo tempted to say yes... but dude, the answer really is NO WAY MAN (unless you want a device which can only be used for throwing in your neighbors windows)
For the ones that want to automate uploading boot.img, here's a batchfile (untested). Just use attached, drag your boot.img ontop of it and ready it is...
Code:
for %%i in (%1) do set onlyfilename=%%~nxi
adb push %1 /sdcard/%onlyfilename%
adb -d remount
adb -d shell dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
adb -d remount
echo all ok?
echo rebooting...press a key to continue...
pause >nul
adb -d reboot
pause
crybert said:
Hey Guys,
I cooked this Kernel with dsixda's Android Kitchen because I wanted a stock kernel with init.d. So here it is.
Root and Busybox needed.
How-To with TerminalEmulator
1. Download boot.img here
2. Place boot.img on your SD-Card
3. Download TerminalEmulator from Market: https://market.android.com/details?id=jackpal.androidterm
4. Run TerminalEmulator and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
reboot
How-To with adb
1. Download boot.img here
2. Place boot.img on your SD-Card
3. Connect your Phone to your PC with the USB-cable (USB-Debugging has to be enabled)
4. Download adb-tools on your PC and extract the files to C:/adb
5. Run cmd on your PC and type
Code:
cd c:/adb
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
reboot
After that you can flash Thunderbolt or AdrenalineShot and use their advantages.
Please give some Feedback it is working correctly because im really new to this stuff. I have a GT-I9001 and at the moment everything seems to run as it should. I had no bootloops as it sometimes was the case with FeaMod or N00b.
Click to expand...
Click to collapse
hmm I can install this over your ROM ?
chasemyass said:
hmm I can install this over your ROM ?
Click to expand...
Click to collapse
You should be able to install it over any rom. Although as you are asking this, I wonder why you'd need it
nikagl said:
You should be able to install it over any rom. Although as you are asking this, I wonder why you'd need it
Click to expand...
Click to collapse
well because I think it could be same kernel version or maybe better than mine if it`s not same
chasemyass said:
well because I think it could be same kernel version or maybe better than mine if it`s not same
Click to expand...
Click to collapse
it's only if you want to tinker with init.d stuff ... and trust me: you don't
nikagl said:
it's only if you want to tinker with init.d stuff ... and trust me: you don't
Click to expand...
Click to collapse
maybe...maybe not i will see
@Crybert:Y dont u integrate CF-ROOT ramdisk with ur kernel,it makes things a hell lot easier
Can be fixed in kernel skype issue with upside-down video from front camera?
prescott66 said:
Can be fixed in kernel skype issue with upside-down video from front camera?
Click to expand...
Click to collapse
just turn the phone around
nope!
what is 'vbus_wake_lock', 'msm_otg' and 'usb_bus_active'?
this 3 kernal are the huge cause of my wakelock.
annoymous1234 said:
what is 'vbus_wake_lock', 'msm_otg' and 'usb_bus_active'?
this 3 kernal are the huge cause of my wakelock.
Click to expand...
Click to collapse
whoa,these are not kernels!
First off, this may seem a noob question, but I am definitely not.
I have an Iconia A200 that now has a broken lcd screen. No display, no touch. I am able to get into the tablet from TWRP via adb, but not from Android (Jelly Bean). It seems I never enabled usb debugging when I installed the custom rooted rom.... I can access the file system and modify anything... Which files need to be modified to enable debugging in Android? Here is what I tried:
Added to default.prop and /system/build.prop
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
Edit: Must have had typos... It now works.
workdowg said:
First off, this may seem a noob question, but I am definitely not.
I have an Iconia A200 that now has a broken lcd screen. No display, no touch. I am able to get into the tablet from TWRP via adb, but not from Android (Jelly Bean). It seems I never enabled usb debugging when I installed the custom rooted rom.... I can access the file system and modify anything... Which files need to be modified to enable debugging in Android? Here is what I tried:
Added to default.prop and /system/build.prop
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
Edit: Must have had typos... It now works.
Click to expand...
Click to collapse
Ok Sounds good for you. Can you changed the title of your thread by [SOLVED]
Thanks in advance
philos64 said:
Ok Sounds good for you. Can you changed the title of your thread by [SOLVED]
Thanks in advance
Click to expand...
Click to collapse
Ooops.... :good:
How would i do this with my skyrocket? same problem, broken screen, adb disabled. Some instructions would be sweet, cause im not really clear with what you did here.
workdowg said:
First off, this may seem a noob question, but I am definitely not.
I have an Iconia A200 that now has a broken lcd screen. No display, no touch. I am able to get into the tablet from TWRP via adb, but not from Android (Jelly Bean). It seems I never enabled usb debugging when I installed the custom rooted rom.... I can access the file system and modify anything... Which files need to be modified to enable debugging in Android? Here is what I tried:
Added to default.prop and /system/build.prop
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
Edit: Must have had typos... It now works.
Click to expand...
Click to collapse
MikeMobes said:
How would i do this with my skyrocket? same problem, broken screen, adb disabled. Some instructions would be sweet, cause im not really clear with what you did here.
Click to expand...
Click to collapse
MikeMobes said:
How would i do this with my skyrocket? same problem, broken screen, adb disabled. Some instructions would be sweet, cause im not really clear with what you did here.
Click to expand...
Click to collapse
I'm going to stay general and assume that a skyrochet is a phone, you have a linux or windows pc with ADB installed (and the drivers to connect to your phone) and have TWRP or CWM Recovery installed already...
1) Start the phone in recovery mode - mine is power down and vol
2) Connect you cable to the pc and start a console terminal or cmd prompt
3) Run the following
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
Once you reboot into Android you should be able to connect via adb.
If you google vnc over adb you can get a usable but very slow vnc connection then install Andriod VNC server for a little better performance.
That's the best I can do from memory ...
workdowg said:
I'm going to stay general and assume that a skyrochet is a phone, you have a linux or windows pc with ADB installed (and the drivers to connect to your phone) and have TWRP or CWM Recovery installed already...
1) Start the phone in recovery mode - mine is power down and vol
2) Connect you cable to the pc and start a console terminal or cmd prompt
3) Run the following
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
Once you reboot into Android you should be able to connect via adb.
If you google vnc over adb you can get a usable but very slow vnc connection then install Andriod VNC server for a little better performance.
That's the best I can do from memory ...
Click to expand...
Click to collapse
I'm booted into twrp 2.6.3 and when i try to run adb devices i just get this
Code:
[email protected]:~$ adb devices
List of devices attached
???????????? no permissions
That Baker Guy said:
I'm booted into twrp 2.6.3 and when i try to run adb devices i just get this
Code:
[email protected]:~$ adb devices
List of devices attached
???????????? no permissions
Click to expand...
Click to collapse
Enter the following commands:
Code:
adb kill-server sudo ./adb start-server adb devices
The issue is your not running adb server as root.
Hello. Does possible enable accesibility and set default tts via adb shell, and edit default.prop and build.prop?
Thanks and best regards.
workdowg said:
I'm going to stay general and assume that a skyrochet is a phone, you have a linux or windows pc with ADB installed (and the drivers to connect to your phone) and have TWRP or CWM Recovery installed already...
1) Start the phone in recovery mode - mine is power down and vol
2) Connect you cable to the pc and start a console terminal or cmd prompt
3) Run the following
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
Once you reboot into Android you should be able to connect via adb.
If you google vnc over adb you can get a usable but very slow vnc connection then install Andriod VNC server for a little better performance.
That's the best I can do from memory ...
Click to expand...
Click to collapse
OMG! After my screen broke, i raged and became hulk. After 3 hours of internet-searching the hulk found your post and released me to become bruce banner again...
The thank you button was just not enough!
Sorry to resurrect a dead thread, but I need a bit more help with this. I've successfully followed these instructions to enable the adb service on my i9505 with a dead screen, however it hasn't authorised it. When I try to connect I get the following error: error: device unauthorized. Please check the confirmation dialog on your device.
Is there anyway to bypass this confirmation dialog from ADB in recovery (Philz Touch)?
Thanks.
pnz said:
Sorry to resurrect a dead thread, but I need a bit more help with this. I've successfully followed these instructions to enable the adb service on my i9505 with a dead screen, however it hasn't authorised it. When I try to connect I get the following error: error: device unauthorized. Please check the confirmation dialog on your device.
Is there anyway to bypass this confirmation dialog from ADB in recovery (Philz Touch)?
Thanks.
Click to expand...
Click to collapse
I Googled it a little and it seems to be a Samsung thing. Apparently it isn't booting to recovery. Sorry for the lack help
From my Debloated Stock Kitkat VS980 4G VZN
workdowg said:
I Googled it a little and it seems to be a Samsung thing. Apparently it isn't booting to recovery. Sorry for the lack help
From my Debloated Stock Kitkat VS980 4G VZN
Click to expand...
Click to collapse
No, I'm quite sure it is booting to my custom recovery, as I have full ADB access to that. What I'm trying to do is enable ADB access to the Android 4.4.2 proper from my custom recovery. So far following the instructions in this thread I've managed to enable ADB there, but whenever you try to connect to this phone a dialog box is meant to come up asking if you want to accept incoming ADB requests from your computer's key. Unfortunately I have no way of selecting accept (or even seeing that dialog box), so I'm hoping there's a way to bypass it.
Hey mate,
Sorry to necro-bumb the thread. I have been reading and have much similar issue to your self. Maybe some drivers that automatically enable adb, android usb or MTP without debugging enabled might be something to take a look at?
Check this thread out >>> here
Hope that might help (you and I both?)
Besides that I am still searching for a post I saw where you can edit the init-rc in the kernel (the guy explained how to extract the boot.img) and then decompile the kernel, edit the init-rc, recompile the kernel and then flash it back in recovery.
At the moment I am really stuck with a customer device that is bricked, so have a bash script and busybox binary that loads from a signed update.zip that should allow editing of the init-rc and add the lines mentioned in this thread to the build.prop and system.prop.
Fingers crossed it works for a completely stock device :fingers-crossed:
Jarmezrocks said:
Hey mate,
Sorry to necro-bumb the thread. I have been reading and have much similar issue to your self. Maybe some drivers that automatically enable adb, android usb or MTP without debugging enabled might be something to take a look at?
Check this thread out >>> here
Hope that might help (you and I both?)
Besides that I am still searching for a post I saw where you can edit the init-rc in the kernel (the guy explained how to extract the boot.img) and then decompile the kernel, edit the init-rc, recompile the kernel and then flash it back in recovery.
At the moment I am really stuck with a customer device that is bricked, so have a bash script and busybox binary that loads from a signed update.zip that should allow editing of the init-rc and add the lines mentioned in this thread to the build.prop and system.prop.
Fingers crossed it works for a completely stock device :fingers-crossed:
Click to expand...
Click to collapse
Hi mate, did you manage to get into the customers mobile? I have the same problem as I'm locked out with no access to enable USB debugging and a home button which does not work, meaning I can't load recovery mode to wipe the phone
Sent from my C6903 using XDA app
workdowg said:
Code:
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
Click to expand...
Click to collapse
Thank you, I had no clue how, but my phone's (MUCH Snail, aka MUCH W1, aka MUCH 78P01) manufacturer (China's Snail Mobile) had removed from Android's Developer Options menu the option to Enable/Disable USB Debugging.
I was looking all over the web for days, this was the only way I could effectively turn on USB debugging in my phone. Thanks!
There's only one difference, instead of performing the above steps from an ADB console window (for obvious reasons) I did it with Build.prop Editor, but first I needed to change permissions to 666 on the default.prop file (otherwise it wouldn't save my changes).
Curiously, every time I do a full reboot the default.prop file somehow is overwritten with the manufacturer's original settings - that doesn't happen when I soft reboot my device though. Any clues as to what could be reversing my changes at boot?
wmoecke said:
Thank you, I had no clue how, but my phone's (MUCH Snail, aka MUCH W1, aka MUCH 78P01) manufacturer (China's Snail Mobile) had removed from Android's Developer Options menu the option to Enable/Disable USB Debugging.
I was looking all over the web for days, this was the only way I could effectively turn on USB debugging in my phone. Thanks!
There's only one difference, instead of performing the above steps from an ADB console window (for obvious reasons) I did it with Build.prop Editor, but first I needed to change permissions to 666 on the default.prop file (otherwise it wouldn't save my changes).
Curiously, every time I do a full reboot the default.prop file somehow is overwritten with the manufacturer's original settings - that doesn't happen when I soft reboot my device though. Any clues as to what could be reversing my changes at boot?
Click to expand...
Click to collapse
Everytime you boot your phone, the root path is extracted from ramdisk which is usually bound to kernel. As a result, your modification is overwritten. In order to modify files under root path(such as default.prop), you must change the file in ramdisk.
There is many tools and tutorials about this task, I think this is a good point to google.
Addition:
The poster of this thread try to edit default.prop via adb, which is not possible to achieve, at least, for every android device I has hold.
For the unauthorized issue, It's because secure adb, which could be disabled via ro.adb.secure=0, but if there is a ro.adb.secure=1 in default.prop, modification of ramdisk is needed.
Given92 said:
Everytime you boot your phone, the root path is extracted from ramdisk which is usually bound to kernel. As a result, your modification is overwritten. In order to modify files under root path(such as default.prop), you must change the file in ramdisk.
There is many tools and tutorials about this task, I think this is a good point to google.
Addition:
The poster of this thread try to edit default.prop via adb, which is not possible to achieve, at least, for every android device I has hold.
For the unauthorized issue, It's because secure adb, which could be disabled via ro.adb.secure=0, but if there is a ro.adb.secure=1 in default.prop, modification of ramdisk is needed.
Click to expand...
Click to collapse
I had edited both default.prop AND /system/build.prop not knowing which one to use. This worked for me on JB and I used the tablet for a while after that.
From my Nexus 9
workdowg said:
I had edited both default.prop AND /system/build.prop not knowing which one to use. This worked for me on JB and I used the tablet for a while after that.
From my Nexus 9
Click to expand...
Click to collapse
In my view, the /system/build.prop works.
I am a huge noob and i dont really understand where i am inputing that code ?
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Windows\system32>adb shell
'adb' is not recognized as an internal or external command,
operable program or batch file.
C:\Windows\system32>su
'su' is not recognized as an internal or external command,
operable program or batch file.
C:\Windows\system32>mount -o remount,rw /system
'mount' is not recognized as an internal or external command,
operable program or batch file.
C:\Windows\system32>cd /
C:\>echo "persist.service.adb.enable=1" >> default.prop
C:\>echo "persist.service.debuggable=1" >> default.prop
C:\>echo "persist.sys.usb.config=mtp,adb" >> default.prop
C:\>echo "persist.service.adb.enable=1" >> /system/build.prop
The system cannot find the path specified.
C:\>echo "persist.service.debuggable=1" >> /system/build.prop
The system cannot find the path specified.
C:\>echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
The system cannot find the path specified.
C:\>
Getting this on S$..any1 here to help me!
persist.service.adb.enable=1 anytime i add it into the default prop and pack the boot image and try to test it it just hangs on the boot screen.. need some assistance in figuring out how to add persist.service.adb.enable=1 to the default prop in ramdisk.
CoffeeNAndroid said:
persist.service.adb.enable=1 anytime i add it into the default prop and pack the boot image and try to test it it just hangs on the boot screen.. need some assistance in figuring out how to add persist.service.adb.enable=1 to the default prop in ramdisk.
Click to expand...
Click to collapse
If you want to start adb on boot add adb to the USB config line , it will be similar to this :
persist.sys.usb.config =mtp,adb
messi2050 said:
If you want to start adb on boot add adb to the USB config line , it will be similar to this :
persist.sys.usb.config =mtp,adb
Click to expand...
Click to collapse
I added the adb and the persist.service.adb.enable=1 and got stuck on the boot screen. Maybe just persist.sys.usb.config =mtp,adb will do the trick.
CoffeeNAndroid said:
I added the adb and the persist.service.adb.enable=1 and got stuck on the boot screen. Maybe just persist.sys.usb.config =mtp,adb will do the trick.
Click to expand...
Click to collapse
Exactly
messi2050 said:
Exactly
Click to expand...
Click to collapse
That worked.. thanks.. booted right up..
CoffeeNAndroid said:
That worked.. thanks.. booted right up..
Click to expand...
Click to collapse
You are welcome
Im getting closer to my goal.. i got adb shell to work and the device to show up as a reconized device with adbd insecure cause the way it patches it makes the device as a attacted device even though the rsa fingerprint never asked you to allow the computer/laptop which is what is giving the unauthorized device errors and vendor keys not set. Thats why adb root access would only work with a custom recovery but now i see it works with adbd insecure and bypasses the rsa fingerprint. Ive got alot of testing to do..
Getting there slowly
Is it possible to enable root debugging from the command line. The rom that I'm using is missing the setting in developers options. When trying adb root I get the
Code:
ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options
I don't believe it's totally disabled because I don't get the "adb root is not allowed in production builds". I think it's there but no switch to toggle. Haven't found anything searching for setting name and would need correct value and table if it can be set. Anybody know how to toggle it on from shell ?
Command adb root works in development builds only ( i.e. eng and userdebug which have ro.debuggable=1 by default ). So to enable the adb root command on your otherwise rooted device just add the ro.debuggable=1 line to /system/build.prop file.
If you want adb shell to start as root by default - then add ro.secure=0 as well.
jwoegerbauer said:
Command adb root works in development builds only ( i.e. eng and userdebug which have ro.debuggable=1 by default ). So to enable the adb root command on your otherwise rooted device just add the ro.debuggable=1 line to /system/build.prop file.
If you want adb shell to start as root by default - then add ro.secure=0 as well.
Click to expand...
Click to collapse
Thanks, actually looking into it, I don't know what to think about it. It is a user build of crdroid. I can not and absolutely do not understand the point of building a user build to post on XDA. The fact that someone is installing a custom rom kinda throws a user build out the window AFAIFC. It didn't even dawn on me to check if it was userdebug or not, in my mind, of course it is. That's what I get for thinking I guess. I like CrDroid so syncing source now, time to sync and build I should have an eng build in about 3 hours.
Take note that if adbd in your phone's firmware is build without ALLOW_ADBD_ROOT then you're wasting your time.