Hi All,
I'm pretty new to Android, but not entirely new to linux and kernel development at all. I was just wondering about two things :
1. Could anybody tell me how to redirect the console messages to be able to see them through usb link (something like serial port console)? Is it possible at all in SNS ?
2. How would one display kernel messages directly on SNS' screen, instead of boot logos ?
Hope somebody keen enough will be able to write me a faq for linux. Thanks
In the same stage as you.
Wondering how can I debug my kernel over USB or print the kernel logs in the phone screen instead of the boot animation.
Any hint guys?
Even though this is contributing to a resurrected post, i will still put in my 2cents.
It is up to the bootloader to boot fb or nonfb, so you would have to hack the bootloader to get nonfb/console output.
Most of the useful stuff is in dmesg anyway, which is part of busybox and usable through terminal emulator.
Sent from my GB Galaxy Tab using Tapatalk.
Related
Hola,
looks as I am the only one having problems with that
-http://forum.xda-developers.com/showpost.php?p=14813252&postcount=52 guide.
Well, I think I went through that above procedure quite acurately but as the download link of the 'recovery zip (solarnz-R3-240511-1908)' in
-http://forum.xda-developers.com/show....php?t=1093818 never worked for me I googled for and dl anywhere else. The problem now is the tf does not start into any UI instead revolvingly reboots (screen looks scambled after some time later reboots).
As I found out now (string is displayed after booting into recovery mode) I obviously installed 'solarnz-R3-230511-1908' even though the downbload file was named ...240511... but arent OS for the UI and the one for the recovery mode two different things? Or may be the problem is I have been on the official 3.2.1 before walking the procedure above?
So my questions are what is the current state of the transformer now and what can I do to make it working?
It currently seems not to be possible to access the device via adb (POWER button and volume plus). My PC makes the USB sound but the 'adb devices' command delivers an empty list. But the transformer can be started into recovery mode (POWER button and volume minus, volume plus after).
Just from my poor understanding I would now try to flash another CWM for example the one mentioned in
-http://forum.xda-developers.com/showthread.php?t=1213723
The thing which bothers me is I cant check any versions (postings seem to make differences among different version of ROM).
--
Regards Michael
following are the specifications before I flashed solarnz file mentioned above:
Transformer TF101
Android version 3.2.1 [email protected]#1
Kernel version 2.6.36.3
Build number HTK75CN_epad-8.6.5.19-20111107
Flash back to stock
tabletromsDOTcom/forums/transformer-rom-development/1071-asus-transformer-nvflash-stock-3-1-stock-3-2-recovery-roms-unbricking-tools.html
Cant post links so the DOT is obviously .
thanx Detection
edit: the problem simply is the adb does not recognize the transformer even though the pc makes the characteristical USB sound after pushing VOLUME UP and POWER button. I did already dig myself all the way through -http://forum.xda-developers.com/showthread.php?t=1071584 ... no chance
Further on I think I lack some basic understanding:
Is it right an android ROM contains the android OS (what version ever) and a whatever set of applications? A manufacturer localized version of a ROM for a specific gadget may NOT fit that specific gadget distributed anywhere else in this world? (for example the US version of a transformer ROM may not fit the transformer distributed in japan)? Does it additionally depend on the kernel?
And finally CWMs do replace some files of those ROM and may do some changes of the configuration?
If my understanding of the above would be right I think I would not necessarily have to go back to stock (which I currently cant as adb does not connect) but find a 3.2.1 suitalbe CWM to make the necessary changes on files and configurations (which would be easy as it may be flashed from the microSD).
Please let me know!
<forget that>but what to do after going back to stock as original OS is not where I want to be in the end. The CN version of most android devices can mostly dl only chinese apps from chinese app markets and thats not what I am interested in at all...</forget that>
--
Regards Michael
Ok, obviously it does not need the ADB but those procedure above finally break my device which means now even the xreen does not switch on anymore
did that happen due to the specifications (certainly build 8.6.5.19) before I flashed solarnz? Is there still any chance?
Transformer TF101
Android version 3.2.1 [email protected]#1
Kernel version 2.6.36.3
Build number HTK75CN_epad-8.6.5.19-20111107
--
Cheers
I didn't check out all the links you posted, but I have a hunch that you are getting bootloops because you have a CN boot.img/bootloader, but are trying to load a rom with a US or WW boot.img. This is just a hunch. I suspect you'll need to get everything to match or at least match the region.
So, just to be clear, you can get into recovery, but not boot into the regular system? When you boot into recovery, there is some white text at the top- what does it say there?
Edit: please fix your links
Hola Gee one,
no, I cant get anywhere anymore. The screen remains black no matter how long I push power and volume up or down
This thread pretty much aggregates everything I did. First this have been my specifations:
Transformer TF101
Android version 3.2.1 [email protected]#1
Kernel version 2.6.36.3
Build number HTK75CN_epad-8.6.5.19-20111107
then I followed on this guide:
-http://forum.xda-developers.com/showpost.php?p=14813252&postcount=52 guide
due to the boot up loop after I then followed on
-tabletromsDOTcom/forums/transformer-rom-development/1071-asus-transformer-nvflash-stock-3-1-stock-3-2-recovery-roms-unbricking-tools.html
and since then the screen remains black. Is there still any chance?
--
Regards
[email protected] said:
Hola Gee one,
no, I cant get anywhere anymore. The screen remains black no matter how long I push power and volume up or down
This thread pretty much aggregates everything I did. First this have been my specifations:
Transformer TF101
Android version 3.2.1 [email protected]#1
Kernel version 2.6.36.3
Build number HTK75CN_epad-8.6.5.19-20111107
then I followed on this guide:
-http://forum.xda-developers.com/showpost.php?p=14813252&postcount=52 guide
due to the boot up loop after I then followed on
-tabletromsDOTcom/forums/transformer-rom-development/1071-asus-transformer-nvflash-stock-3-1-stock-3-2-recovery-roms-unbricking-tools.html
and since then the screen remains black. Is there still any chance?
--
Regards
Click to expand...
Click to collapse
What is your serial number? Look under the tablet near the charging port, there's a sticker with your s/n and should start with a BxOxxx
ie. B60, B70, B80 ect....
Its starting with B60... sorry I forgot to state before
Perhaps you are stuck in APX mode? The screen will be black until you send an nvflash command. There isn't a lot of info in one place about nvflash, but the tools are out there. Try flashing a full rom via nvflash.
sent from my cyanogen(mod) vision
hold power button for 30 seconds, release and power on as normal
no reaction. Seems a clear message
If you are on a linux/unix system, plug in your tf and type "lsusb" Post the output.
If you are on windows, sorry.
Perhaps your power button is broken?
wow thats quick responses now. I just plugged in my tf to the USB port of my PC and when I pushed the power button for a while there was at least the typical sound but its not itemized in the WIN7 device manager
If there is a chance to get it back working on a linux system I can get one I guess
but
its late here now ...11pm. So would be great U could gimme some advice for tomorrow to work on
--
Mic
could I possibly run those command from a linux live CD (I remember some like KNOPIX but dont know if its internationally well known)?
Yeah, it should work. Type it in from a terminal or command line.
Sent from my Transformer TF101 using Tapatalk
well I dont have any clue about LINUX, so I should explain.
I started the UltimateBoot CD 5.1.1 within the vmware player.
For me unexpectedly I got just a screen like DOS in old times.
The window itself states to push CTR+G in order to type in comands and when I do so and type in 'Isusb' I can not read what I type?
Is that what I am supposed to do? Should the tf (obviously it has to be connected) tried to be switched on? POWER and volume up or down?
--
Thanx for any further help
Michael
the command is lsusb (LSUSB, but in lower case) First letter is L as in laptop.
plug in your transformer and it will show you what mode your are in, if any. It might show the Asus transformer (normal) or nvidia (apx mode).
When I conncect the Tf, pus POWER and volume even the VM will show me a message a device NVIDIA (APX) can be connected but then I dont think I am doing right. No matter I am typing 'Isusb' or lsusb'
the outcome always alternates between:
!BIOS V3.20
BIOS V1.35.0
CMOSPWD V5.0
KEYDisk
WipeCMOS V1.2
and
BIOS
CPU
HDD
Memory
Others
Peripherals
System
Parted Magic V6.6...
UBCD Free DOS R1.44
User-defined
Boot next device
Reboot
GRUB4DOS
Edit: i am off for a few hours now
try typing "uname -a"
What comes out?
Edit:
alternatively I tried KNOPPIX and chose Shell there. Typing lsusb' the outcome is:
Bus 001 Device 002: ID 0955:7820 NVidia Corp
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
and more
the outcome for 'uname -a' is:
Linux Microknoppix 2.6.39.3 #21 SMP PREEMPT Sat...
:Edit
while I type 'una...' the list stated above (starting with BIOS) alters and there is only one line 'configfile /ubcd/menus/grub4dos/bios.lst'
I think as soon as I push (no matter what I tpyed before) the [ENTER] key that is about to happen but not the command U want.
As the list above very much looks like some kind of menu, I chose the grub4dos option. If then I type 'c' for command line and then type 'uname -a' the outcome is: No such command: uname
Additionally at the VM windows menu 'Virtual machine' under removable devices have one entry 'nvidia apx' and it can be successfully connected
I hope this is the right place to post, apologies if not.
I'm trying to root my Samsung Galaxy S2 from stock.
I'm running Linux [Fedora 17 64bit]
I've installed Heimdall, and I've got what I think is the nearest zImage to my kernel.
Have added the 51-android.rules file
and set phone to allow debugging via usb
Settings > Applications > Development and enable USB debugging
However Heimdall reports that it is unable to detect my device.
This is very understandable as when I try
Code:
lsusb
my phone doesn't show up.
Any ideas anyone?
As an aside I have difficulties getting fedora to connect with my phone in normal mode, and have to use this workaround: [link removed as I have under 10 posts]
so as to unbind the ehci_hcd. But I think this is quite common.
Any help greatly appreciated.
Chris
Rooted it.
I have no idea what was wrong with doing it on my main machine.
But I just tried it on an ancient laptop with lxde fedora on it.
So ancient that I had to edit the boot code to not check for machine RAM before installing the lxde.
Yet it all worked perfectly cleanly first time within seconds!
I didn't even bother setting the android rules file.
Either way, all is good, and obviously heimdall + usb = finickety
my advice to others is just try it on a different pc.
This may have been posted some where in the past but I have been searching for some time and found nothing but others looking for this information. So I though I would document what I did to get everything up and running on my note 3 and share it here.
Requirements
Rooted Note 3
Recommended
Bluetooth keyboard and mouse
From a PC
1. Download kali from the LOA website kalilinux.FULL.ext4.20131031 (5.8 GB Uncompressed) (2.0GB Download)
2. Once the download is complete extract the contents of the folder so you have a folder named “kali” then an .img and .md5 file in it then copy that to the Note 3 device storage root. I strongly recommend using USB 3.0.
On the Note 3
1. First Download Linux on Android It might be called Complete Linux Installer now
2. Then Download androidVNC and Terminal Emulator
3. Download the modified bootscript.sh from attchments and extract
4. Copy to /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh
5. Start Linux on Android
6. Swipe from the left of the screen to the right and open the menu
7. Select “Launch”
8. Using the drop down box select “Kali”
9. Press the “Settings” button on the top right
10. Select “Edit”
11. On the line that says “Image” click the “…” button
12. Select the img file you copied to the storage in the kali folder
13. Click the “Save Changes” button
14. Then you are ready to click the “Start Linux” button
15. There will be a question if you want to check the img with the MD5 I would go ahead and type “y” and do this step to verify your download was not messed up.
16. Then it will ask you to create a new password. Type it in. And again. Make it 6 char alpha numeric.
17. If all is good it will ask if you would like to start vnc and ssh servers. Select yes to both.
18. Next it will ask you if you would like to save as default settings. I would select yes.
19. After things finish loading and you have a prompt. We will have to configure ssh
20. Type “ssh-keygen –R localhost”
21. Then you will be able to connect to the linux shell via ssh
22. Type "ssh localhost"
23. It will ask you if you want to add localhost to the list of allowed hosts
24. Type "yes" then press enter
25. Type in your password
26. Once connected to the emulator you will need to setup the VNC password
27. Type "vncpasswd" then press enter
28. Type your password in. And again. I would use the same 6 char password from before
29. Then you are ready to connect to the desktop
30. Open androidVNC from them the main menu leaving the terminal running in the background
31. Create a new connection from the dropbox
32. Name it kalilinux
33. Fill in the password you created
34. Use localhost for the address and the default port
35. Select 24-bit color (4 bpp) for the color format
36. Click connect...
Great guide. My device isn't rooted (yet) but this makes me really start considering a root in near future. THIS^ is a the best reason why we need knox free devices.
Damn you Sammy with your Knox mumbo jumbo! I should start looking for an older FW/rootable SGN3....
This will not trigger the Knox bit it is running in an emulator on top of android. there are a couple of ways to root without tripping the Knox bit. And this does not need a custom rom or kernel.
Does it really work for you? I wasted almost a full day trying to get linux to run on my note 3 yesterday, I even began suspecting kitkat prohibits running linux...
On a side note, is there some smaller distro? 5+ gigs is an awful lot, I only need GCC and a few static libraries on my image...
good guide! Thanks!
Does it support packet injection out the box, or are you awaiting the modded driver as well?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
melaniel said:
Does it support packet injection out the box, or are you awaiting the modded driver as well?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
not by default i could not start monitor mode on the adapter but you can use an external wifi adapter as long as you provide external power via usb splitter
this guide should work with other distors just download one to your likeing from the linux on android site
bruce303lee said:
not by default i could not start monitor mode on the adapter but you can use an external wifi adapter as long as you provide external power via usb splitter
this guide should work with other distors just download one to your likeing from the linux on android site
Click to expand...
Click to collapse
ill wait out the driver then. bcmon is working on the nexus 5, same driver so should theoretically work on note 3
melaniel said:
ill wait out the driver then. bcmon is working on the nexus 5, same driver so should theoretically work on note 3
Click to expand...
Click to collapse
+1
I don't think there will be a driver, but let's hope and pray... Maybe a developer take some time to port the driver for the bcm 4339 chipset to get monitor mode working .
For informations about development status for the driver you can follow my link
http://forum.xda-developers.com/showthread.php?t=2602710
Greetings Tyler
TylerDurben said:
+1
I don't think there will be a driver, but let's hope and pray... Maybe a developer take some time to port the driver for the bcm 4339 chipset to get monitor mode working .
For informations about development status for the driver you can follow my link
http://forum.xda-developers.com/showthread.php?t=2602710
Greetings Tyler
Click to expand...
Click to collapse
Well its the same driver as the Nexus 5, so here's hoping!
melaniel said:
Well its the same driver as the Nexus 5, so here's hoping!
Click to expand...
Click to collapse
This project is much more interesting!!
http://w11.zetaboards.com/Pwnie_Express/forum/3714106/
I am using it with my nexus 7 (2012) witch is bcmon supported
Sent from my SM-N9005 using XDA Premium 4 mobile app
Error: Unable to create loop device!
Hello,
I installed the 4.4.2 version on Note 3 (N9005) ... when I boot Kali I receive the error below:
Code:
[email protected]:/ $
[email protected]:/ $ cd /storage/extSdCard/Linux/KaliFull
[email protected]:/storage/extSdCard/Linux/KaliFull $ su
sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /storage/extSdCard/Linux/KaliFull/kalilinux.FULL.ext4.v2.img
sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /storage/extSdCard/Linux/KaliFull/kalilinux.FULL.ext4.v2.img
Full/kalilinux.FULL.ext4.v2.img <
Checking loop device... MISSING
Creating loop device... /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[130]: /data/data/com.zpwebsites.linuxonandroid/files/busybox: can't execute: Permission denied
FAILED
Error: Unable to create loop device!
1|[email protected]:/storage/extSdCard/Linux/KaliFull #
does anyone know how to fix it?
Thanks,
Error: Unable to create loop device!
yea, me too, galaxy note3
Error: Unable to create loop device!
help,
Loop device error
My device also has that loop error.
I think that this has something to do with the kernel...
Here is my kernel version:
http://i.imgur.com/C6yF4DB.png
Can anyone confirm that this is the kernel issue?
P.S. here are the instructions for setting up Kali on Galaxy S4 with Linux Deploy app (I'll try install it using these methods...):
http://forum.xda-developers.com/showthread.php?t=2400638
EDIT:
I had no luck installing it with Linux Deploy. It just fails... It says it cannot find the directory that actually exist... xD
P.S. i think this is a kernel issue according to this (and other posts I found):
http://forum.xda-developers.com/showpost.php?p=50746675&postcount=5
You can find custom kernels and ROMs here:
http://forum.xda-developers.com/showthread.php?t=2439633
I heard that the LEAN kernel has "loop devices" setting enabled.
Also, you can modify your current kernel. Instructions here:
http://forum.xda-developers.com/showthread.php?t=1818871
Is there a easier method for enabling loop devices?
access
how can I access all kali files and folders when I usee explorer root is my sd card root and I can't see a single kali file
I tried your method and still received the same errors.
I have a rooted note 3 (I think I used the chainfire method) the device is still pretty new to me.
First it won't create the loop255
I've manged to get around that by making the loop255 device myself in terminal with the play store version of bbox (for some reason there seems to be an issue with the installer calling it's own busybox)
But then it (that is the loop device) won't mount, I'm over my head with that stuff so I haven't been able to work around this.
Some guidance would be much appreciated.
On a side note I got linux running on my old LG Motion with linux deploy and it works like a dream but for some reason there are no programs on it! I've found this odd but there are (or at least I cant find them) none of the preloaded hacking programs that are the entire point of the kali project. It's possible I just didn't find them yet but it's so hard to work with a desktop OS on a 320x480 screen, that's why I'm trying to get it on my note! I'm in love with this new 1080x1900 res!
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 11:15 PM ---------- Previous post was at 10:57 PM ----------
Okay I've seen in a few places that it has to do with the stock kernel of the note 3 can anyone either confirm or deny this and if so what do I do?
Sent from my SM-N900T using XDA Free mobile app
Root Folder
I was just wondering how you were able to copy files and folders from your pc to your root folder. Do you use a program or cmd line?
Circumventing the loop device mounting problem on the Note 3
Vinniecap974 said:
I tried your method and still received the same errors.
I have a rooted note 3 (I think I used the chainfire method) the device is still pretty new to me.
First it won't create the loop255
I've manged to get around that by making the loop255 device myself in terminal with the play store version of bbox (for some reason there seems to be an issue with the installer calling it's own busybox)
But then it (that is the loop device) won't mount, I'm over my head with that stuff so I haven't been able to work around this.
Some guidance would be much appreciated.
On a side note I got linux running on my old LG Motion with linux deploy and it works like a dream but for some reason there are no programs on it! I've found this odd but there are (or at least I cant find them) none of the preloaded hacking programs that are the entire point of the kali project. It's possible I just didn't find them yet but it's so hard to work with a desktop OS on a 320x480 screen, that's why I'm trying to get it on my note! I'm in love with this new 1080x1900 res!
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 11:15 PM ---------- Previous post was at 10:57 PM ----------
Okay I've seen in a few places that it has to do with the stock kernel of the note 3 can anyone either confirm or deny this and if so what do I do?
Sent from my SM-N900T using XDA Free mobile app
Click to expand...
Click to collapse
I ran up against the same problem and the only way I could get around it was to flash with a "permissive" ROM.
Device: Galaxy Note 3 N9005 running stock Android 4.4.2 (KitKat).
Main steps I followed were:
(1) Rooted the phone using the excellent Towelroot method;
(2) Downloaded and deployed the various files mentioned in the Kali install guide in this thread (Kali image, bootscript, busybox, etc.);
(3) Flashed a bootloader. I used Mobile Odin (from Play Store) to install the latest CWM bootloader;
(4) Downloaded and flashed the Omega V21 ROM using the CWM bootloader. I opted for "no wipe" and it seems to have worked OK.
(5) Used the Complete Linux Installer app (Play Store) to load and run the Kali image;
(6) Fixed some permissions problems with the rooted version of the FX file explorer app (Play Store);
(7) Accessed Linux using the RealVNC app (Play Store) rather than the recommended android-vnc-viewer.
Found the former worked better for me;
Of course, the ROM flash voided my warranty, but that's not an issue for me.
Hope this helps,
Ronan
As I understand it , you need to flash a permissive kernel to make this work properly.
Im on 4.4.2 with knox 0x0 and really dont want to set it to 0x1.
I managed to get linux to install but its limited in what you can do with it.
Xposed didnt set mine to permissive , neither did the playstore app .
If anyone knows of a way to set a stock kernel to permissive on a rooted device plz pm me.
I set up a Debian chroot on my CM11 Note 3 and have been using it for a long time with great success. Here's a tip, don't bother with the loopback-mounted images, it's pointless on a phone with a datamedia partition layout (where /data and /sdcard are the same partition, which the Note 3 is). Instead, just dump the root filesystem directly into the /data directory in a folder, i.e. /data/debian (or /data/arch, /data/ubuntu, /data/kali, etc). This way you don't have to have loopback device support in your kernel, you can install as much crap as you want and not have to resize your image/partition, and you can delete crap you don't want to free up space for Android apps or user storage because all of them share the same space.
Another tip, instead of VNC server which is not accelerated and pretty crap overall, use XServer XSDL. This implements an X-server at the Android app level so it can take advantage of some acceleration (not 3D but possibly 2D) and is drawing with native Android surfaces rather than rendering into a VNC buffer and such. To use it, simply run a command such as:
Code:
# env 127.0.0.1:0 mate-session
from a chroot terminal. This particular one will open a MATE desktop session in XServer XSDL (make sure you either open the app right before or right after running the command, leave it too long and it times out). There's also a libandroid_shmem.so or something library you can use to speed up the chroot->xserver memory performance. Best thing is you can configure the touchscreen to act as a trackpad like on a laptop, then use the left and right (up and down, but landscape) volume keys as left and right click.
On CM11 you can even write a script and add it to /data/local/userinit.sh to automatically start the chroot (bind mount all the devices and set up networking) and even start services if you want. I have mine automatically fire up a samba server and an SSH server on boot so I can access files remotely as well as remote in and use my Note 3 as an ARM build box for compiling stuff.
Finally, I'm looking into booting Debian natively. I've already got it working on my Note 1 and my HP TouchPad. Booting natively means you get full access to run an X server with full graphics hardware access, and with the Freedreno driver you can get actual GL and GLES acceleration. The Adreno 330 should be able to handle this pretty well. The first step towards this goal is getting dual-booting kernels to work as the native Debian kernel will need some stuff that Android doesn't want and vice-versa. I'm working towards porting Kexecboot and the kexec-hardboot patches which will allow booting of multiple kernels without reflashing. Then you can boot Debian (or other Linux) natively or you can boot Android and use services from that Linux install in chroot and easily switch back and forth by rebooting. I already have this working on the Note 1 (HP TouchPad has kexecboot but it isn't really necessary as the main bootloader supports multiple kernels already).
I have an Ethernet SMC 2208 adapter which does not work with shield out of the box. I have my shield updated to lollipop. Upon insertion I can see that the device is recognized by the system in the sense that there are messages in dmesg stating that it is "Procduct SMCSMC2208USB". After that there are some messages mentioning "audit" and "avc: denied". In contrast on my Nexus 5 (also lollipop) the device works correctly, I can see some messages mentioning pegasus driver if I got it correctly. It's a bit hard to provide complete output since I'm running the commands from android terminal and can't easily copy output here. But if that would help I'll grab it somehow.
I was thinking about compiling the module for the device but it not as easy as on regular linux. I found the driver source on that page: "edge-core.com/temp/edm/old_downloads/old_downloads.html" "edge-core.com/temp/edm/old_downloads/dr/DR_SMC2208_LinuxDRV.zip" (because this is my first post I can't insert URLs So I deleted " h t t p : / / w w w ." prefix, sorry for inconvinience)
But I don't know how to compile it for android in general and for my tablet in particular. I would greatly appreciate if someone could compile it for me or point me to steps I need to follow to do it myself.
Thanks in advance for your help
After having a really good tester @mrbtree98 I was convinced that everyone is really that good but after seeing some people on #twrp and some close friends telling their situations of their tester , and believe me its not good
So this read would explain a bunch of including :
[*]Attitude
[*]Basic Stuff
[*]Debugging
[*]Talking skills
[*]Patience
Lets start with attitude
Attitude
People may hear your words
But people feel your attitude
Click to expand...
Click to collapse
Attitude while talking to developer is very important it even sometimes decides your respect on a forum !
People on very forums highly respect the devs even if he is new to the forums , same applies to xda
IF you show your attitude then things will absolutely go wrong
What do I include when I talk about attitude ?
You throw sarcasm or even bad abuse him ! becuase his program messed anything with or phone or anything
You say you are tired of this testing stuff
You try to tell him that he is slow and inferior to other devs
I know this may seem hypothetical but its true , this does happens !
When Talking to dev always keep your temp down remember that he is doing all the work for you all guys and he wants your satisfaction
Basic Stuff
lets Boil down to basic stuff that you need to learn before testing anything in android
Adb
Adb :
Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device.
In order to use adb with a device connected over USB, you must enable USB debugging in the device system settings, under Developer options.
On Android 4.2 and higher, the Developer options screen is hidden by default. To make it visible, go to Settings > About phone and tap Build number seven times. Return to the previous screen to find Developer options at the bottom.
On some devices, the Developer options screen may be located or named differently.
Note: When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer. This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog. This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher.
Click to expand...
Click to collapse
fastboot : fastboot is a small tool that comes with the Android SDK (software developer kit) that can be used to re-flash partitions on your device. It is an alternative to the recovery mode for doing installations and updates.
Kernel :
A kernel is critical component of the Android and all operating systems. It can be seen as a sort of bridge between the applications and the actual hardware of a device. Android devices use the Linux kernel, but it's not the exact same kernel other Linux-based operating systems use. There's a lot of Android specific code built in, and Google's Android kernel maintainers have their work cut out for them. OEMs have to contribute as well, because they need to develop hardware drivers for the parts they're using for the kernel version they're using. This is why it takes a while for independent Android developers and hackers to port new versions to older devices and get everything working. Drivers written to work with the Gingerbread kernel on a phone won't necessarily work with the Ice Cream Sandwich kernel. And that's important, because one of the kernel's main functions is to control the hardware. It's a whole lot of source code, with more options while building it than you can imagine, but in the end it's just the intermediary between the hardware and the software. So basically if any instruction is given to mobile it first gives the command to kernel for the particular task execution.
Flashing a kernel :
adb reboot bootloader
fastboot flash boot boot.img
Bootloader :
The bootloader is code that is executed before any Operating System starts to run. Bootloaders basically package the instructions to boot operating system kernel and most of them also have their own debugging or modification environment. Think of the bootloader as a security checkpoint for all those partitions. Because if you’re able to swap out what’s on those partitions, you’re able to break things if you don’t know what you’re doing. So basically it commands the kernel of your device to Boot the Device properly without any issues.
Flash a kernel :
adb reboot bootloader
fastboot flash boot boot.img
Recovery :
Recovery is defined in simple terms as a source of backup. Whenever your phone firmware is corrupted, the recovery does the job in helping you to restore or repair your faulty or buggy firmware into working condition. It is also used for flashing the Rom’s , kernel and many more things.
Flash a recovery :
adb reboot bootloader
fastboot flash boot recovery.img
Radio
The lowest part of software layer is the radio: this is the very first thing that runs, just before the bootloader. It control all wireless communication like GSM Antenna, GPS etc.
taken by @jackeagle
You should know this basic stuff :good:
Debugging
Developer dont breath oxygen they breath logs
When he says recovery.log
If in normal mode (in the Operating System)
Using the phone itself :
Open a file manager app or textviwer
Navigate to /sdcard
Open the recovery.log
copy its content
paste it to paste.omnirom.og
Give him the link
If in the recovery itself :
Open up cmd or Terminal
Navigate to where adb is installed (Only windows )
Type
Code:
adb pull /tmp/recovery.log
The file would be at your folder where u navigated earlier or if on linux it would in the /home/{user}/recovery.log (if you didnt cd)
open it using a text viwer
Copy and Paste on paste.omnirom.org
Give him the link
[/INDENT
When he says last_kmsg
Open cmd
Type
Code:
adb pull /proc/last_kmsg
The file would be at your folder where u navigated earlier or if on linux it would in the /home/{user}/last_kmsg
(if you didnt cd)
open it using a text viwer
Copy and Paste on paste.omnirom.org
Give him the link
Talking skills
Dont ever give your thoughts !
Yes thats true the dev doesnt needs to know what he needs to do or not
But always report even a small change
My tester @mrbtree98 always tells me whether when booting the light is dimming or not he is getting the connect sound or not tell everything
Always talk with respect !
Patience
A rom build takes around 2 hours [highly approx , diff for everyone]
A boot.img takes me 20 mins [highly approx , diff for everyone]
So always be Patience
Even when you submit a log wait
A kmsg is around 5000 lines he / she needs to carefully see it to reach a conclusion so be patient
WIP
Flash a recovery :
adb reboot bootloader
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Shouldn't there be "fastboot flash recovery recovery.img"?