yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 General] r2d23cpo:
[MENTION=4821597]social-design-concepts[/MENTION]

I had test flash with the droidboot that came from your package, and enethoght ot conects and reboot find it does give error when try to flash.

$ ./fastboot flash boot /home/mumble/<user>/fastboot_Test/stock/boot.img
usb=/dev/bus/usb/003/009
sending 'boot' (8290 KB)...
OKAY [ 1.355s]
writing 'boot'...
[COLOR="Red"]FAILED (remote: flash_cmds error!
)[/COLOR]
finished. total time: 2.835s

But when I try it with the compiled version of 4.2.2 of Android-ia it runs fine.

$ ./fastboot flash recovery /home/<user>/Desktop/fastboot_Test/stock/recovery-twrp.img
usb=/dev/bus/usb/003/030
sending 'recovery' (20480 KB)...
OKAY [ 2.918s]
writing 'recovery'...
OKAY [ 2.918s]
finished. total time: 5.837s
./fastboot reboot
usb=/dev/bus/usb/003/030
rebooting...

finished. total time: 0.088s
$

I seen in the fstab.recovery that you guys use "platform/intel/by-label" instead of "mmcblk0p*"

/dev/block/platform/intel/by-label/factory

So I wonder if you guys made any changes to droidboot code also?

Still also any chase that I get sources for the droidboot that you guys use?
[Galaxy Tab 3 General] social-design-concepts:
Sorry haven't been on lately my droidboot is stock ( locked bootloader ) can't flash unsigned images to my device : ( so no custom compiled droidboot for me. My devices is OSIP based images yours is AOSP images which is why it failed flashing with my devices droidboot binary. But I'll try to catch up with my reading this evening sorry I haven't been much help.
[Galaxy Tab 3 General] r2d23cpo:
Here is a test article,

I temporary renamed fastboots yes with an s. So that you can recognize it from the original.

Please UNDERSTAND this is totaly experimental. If fastboot it self is dangerous, well a modified fastboot is more dangerous!

I only tested

./fastboots -d18d1:4e20 reboot

./fastboots -d18d1:4e20 flash recovery recovery

./fastboots -d18d1:4e20 flash boot boot.img.

I try fastboots update <filename.zip> but it fail it request a zip file with some extra missing files and I guess need to be signed!

Remember to backup you device including boot.img and store it in your PC!

Now it only work with the compiled droidboot image. I will upload a file in a few minute. Currently I am testing it in boot.img to make easy the recover by then pressing power+volume+ to get into recovery. Then when I get tire of testing use recovery to return my backup original boot.img.

Edit. I am sorry I had bad INTERNET and my upload was getting lost. Here is the droidboot boot image that works with the fastboots

P5210-droidboot-booy.img-CM10_1_025.zip 16.4 MB
h__ps://mega.co.nz/#!aNVXhT4I!PfgACE_LNnb7azi6T_0KhXbx3DgGYTQVNyj665EqOJw

IMPORTANT:

1) I know we are not custom to fastboot. One thing is not mention anywhere is that fact that we need to KILL ADB SERVER before using fastboot or fastbots. If you leave it on droidboot will spit error "unknown command: CNXN " or "unknown command 'host::'". This is because adb smart engine will pole whatever device is connected for the new 4.2.2 encrypted keys. And at the time fastboot was build there where no such keys requires for authentication. So disable adb by running

adb kill-server

before trying fastboot.

2) Do not leave droidboot running for ever. I do not know why but it tend to makes TAB3 Hot after a while. Well I think is has to be because it requires a screen saver. In the droidboot of DELL it does shut down the screen, and it never get hot.
[Galaxy Tab 3 General] social-design-concepts:
Have you thought about implementing this in recovery.img instead of boot.img?

Then you could add a recovery menu option to the droidboot menu and a droidboot menu option to the recovery menu and switch between the recovery and the droidboot through and init service the you could switch between fastboot and recovery mode with out rebooting
[Galaxy Tab 3 General] r2d23cpo:
Listen [MENTION=4821597]social-design-concepts[/MENTION], I know you device is using a different boot process. I do not even understand the changes. That is fine. I did not ask you to test this. In fact for know I do not want. I do not want to feel guilty if something goes wrong in you side. I wont be able to help you in something I do not understand. I did ask you for Why!!!

But this answer of yours may have indirectly answer my question. I guess my like of understanding on your Dell boot process was the problem. Know I think that could be the reason as why Dell's droidboot do fail flash boot.img or recovery.img. uhhh!

I read in some place that your boot.img and recovery.img where not in separate mmc partitions!! That may answer the funny way you device point to it!!!

/dev/block/platform/intel/by-label/factory
/dev/block/platform/intel/by-label/recovery
/dev/block/platform/intel/by-label/boot

I know you had been busy, I just hope making money!! jijiji

In my case I am broke, unemployed and close to bankrupt. jijiji

But if you have time, can you explain the Dell/Intel weird (to us) way of image storing? Thanks

I know you have said not read the thread, that ok do not even spent that time. What you just said is exactly what I plan to do. I had explained that a few times in previous posts. And That is why I had cried for help many times and ask,

If any body can help me locate "Dell-Menue -Droidboot source". So that we can do just what you had mention. Yes I had made small test and I can ensure that the limited size of droid boot can leave and share the same recovery.img.

I only test in boot.img because is the easiest way to recovery until I have a menu that I can start recovery.

So, can you look in your Dell Open Souce to see if there is a droidboot soucer inside. I imagine it should be in <OpenSourecDir>/boot/ I had seen /bootable/ also.
[Galaxy Tab 3 General] r2d23cpo:
I could not found the source for droidboot similar to Dell. So I will leave that work for the future. Well the truth is that all this will be related due to FrameBuffer graphics! Yes another thing to learn.

So I returned main focus to linux.

Kexec is in hold as It have problem with memory allocation. The require knowledge may be to way over my head. Now kexecboot the gui may still prove useful, since I have to learn one way or the other about FrameBuffer.

So I returned to use switch_root as the mechanism to move from ramdiskfs to Linux. Last night I spent some time playing with it. I can boot into ramdiskfs, set up dev/block so that I can mount the SDCARD where Ubuntu is, Then use switch_root to continue on Ubuntu. Now the tutorial I follow pass the partial control back to Android in order to allow android to set up all devices. Once Android Flags that the devices are up Ubuntu try to restart. That is where I am hang now.

In fact, Android is running unde chroot mode, but to my understanding is that it hang up too. I does not get to the point to setup the WIFI. And from time to time it even reboots. I can access Android thru adb shell. Since Android is in chroot I can not uses it to access Ubuntu. Without wifi I can not control Ubuntu! And Neither Ubuntu nor Android access the Screen. I see just the logo of Samsung. I know that it is working partially because I force to print most commands in to a file store at the sdcard. By looking into the file I know what pass and what gives error. So I will be looking how to force Ububtu to display on the screen. I already found many post even in this forum on people that gave up because they could not make Ubuntu to display on screen. But I have my hopes.
[Galaxy Tab 3 General] r2d23cpo:
I have received emails and pm of people telling me they read this thread. But no buddy post!!

Lets see if I can motivate all. I feel lonely.

[MENTION=5864662]moonbutt74[/MENTION], [MENTION=1649190]Angel_666[/MENTION], [MENTION=4821597]social-design-concepts[/MENTION] & [MENTION=4365577]toneay[/MENTION]

So where we are: Ubuntu can execute that is a fact. But No display to prove it. That is why WE ( that is a lot of people) need to learn about "Frame Buffer".

Our frame buffer seems to be in

/dev/graphics/fb0

I have not try but we should be able to do

cp /dev/graphics/fb0 screen.img

to copy capture the screen and

cp screen.img /dev/graphics/fb0

to display it.

So for your delite here is a nice experiment,

1) Leave you TAB3 10.1 in Home Screen

2) connect you TAB310.1 to the PC via cablel

adb shell
dd if=/dev/urandom of=/dev/graphics/fb0

Now you broke it. jijiji To clean the screen just touch the screen and it shout refresh, or just do the BACK button.

So if you are interested in learning go to the documentation h__ps://www.kernel.org/doc/Documentation/fb/

I did download the kernel at h__ps://www.kernel.org/pub/linux/kernel/

In fact i did download an old version

h__ps://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.29.tar.gz

and look instead at.

linux-2.6.29/Documentation/fb/

here is what I suggest you read

framebuffer.txt

fbcon.txt

internals.txt

This one should be interestin sice it is what our device uses

pvr2fb.txt	- info on the PowerVR 2 frame buffer driver.

this ones are related!! a generic and other intel graphic boards.

vesafb.txt- info on the VESA frame buffer device

intelfb.txt

I did download h__ps://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.29.tar.gz this version because 2.6.29 been mention in a few articles. I have no idea if it is the right one. But in my agenda I am compiling this generic kernel and test it inside the tab3 instead of the opensouce.
[Galaxy Tab 3 General] r2d23cpo:
So after that nice reading in frame buffer we should had tested

Experiment 1

adb shell
dd if=/dev/urandom of=/dev/graphics/fb0

I guess before we try to own and still it to Android we should ask Android to leave us alone! I mean we do not want to compete for resources.

I found that in Android source has the toolbox. toolbox has a a nice pair of commands for stopping and starting Android(at least zygote&surfaceflinger). The sources are in <yourOpenSource>/system/core/toolbox". And they are as simple as "start" and "stop".

Experiment 2

adb shell
su
stop

You broke it again!!!!!!!!!!!!!!! And this time for good.

Black Screen of Death

. jijiji

To restart Android just do

start

And it should reboot.

Now to stop other android stuff like "media" we could use the following scripts

ile: /system/xbin/stopandroid
#!/system/bin/sh
setprop ctl.stop media
setprop ctl.stop zygote
sleep 1
setprop ctl.stop bootanim
sleep 1
setprop ctl.stop media
setprop ctl.stop zygote
sleep 1
setprop ctl.stop bootanim
exit 0

file: /system/xbin/restartandroid
#! /system/bin/sh
setprop ctl.stop media
setprop ctl.stop zygote
setprop ctl.stop bootanim
setprop ctl.start bootanim
setprop ctl.start zygote
setprop ctl.start media
exit 0

this was presented by {ajk} in his thread http://xdaforums.com/showthread.php?t=2025566

Weird nice guy and only 3 post!
[Galaxy Tab 3 General] r2d23cpo:
This TAb3 forum seems dead! Not many post.

But I am still alive, A lot of reading and test.

It is just that must of the stuff that I had found is in the negative side, many had failed recently. lets say 2012->. There where good success previously 2012. I have a felling the changes had been made in Video/FrameBuffer and/or serial console, to prevent Linux to take access of the frame buffer mechanism.

There are many small issues like no matters what I do to change commandline to show console=tty0 it gets overrides. So to other system it appears there is no console available!!

frame buffer is manipulated, for example kexecboot and droidboot apps can write with no problem to screen by at booting time. But the same applications fail to change the display once OS is active, no matters if we turn off media, zygote, bootanim etc!! The weird thing is that frame buffer seems to work as we can do dd if=/dev/urandom of=/dev/graphics/fb0.

At this point I am focusing in getting the console to work. I have the feeling this is a main issue.

Now I do simple test on the tty devices and find them unresponsive. But we know adb is capable to produce a console in host Desktop. So aat this point I am study adbd source code to see or copy the way this adbd program creates and oppen a console/tty. Then I will try to provide this info to kexecboot as first test.
[Galaxy Tab 3 General] r2d23cpo:
I still working. It is been quiet because I had nothing to say positive.

In general, I found comments that the Android video drivers in the kernel may not work for Linux. And that is the reason that we can find so many devices that had failed to get Linux natively. I can not denies or confirm yet that assumption. It is clear that we may have trouble for sure to get "3d" or "video acceleration" what ever they mean, but in general comments about HD video render problems. The reason is that there is no PowerVR Open Source Code Drivers for Linux.

I had only found a way to manipulate Kernel cmdline and disable console=sec_log_buf. I have not found yet a way to display a txt console on the screen or sb console, for example to show the pinguin and the boot process.

I am slower because I been king of sick. But I still working.

One thing, it seems Ubuntu realize this type of problems when it designed the phone os ( Touch). And selected Androids "surfaceflinger" to be used for its graphics. Having that in mind, it may be possible that Ubuntu Touch may be an easier implementation that Linux. But it is just that I do want my Native Linux on Tab3 10.1.
[Galaxy Tab 3 General] Restl3ss:
Ubuntu touch is full fledged ubuntu, just with a mobile interface. You can switch to the desktop interface I think, it switches if you plug it into a monitor / base station / whatever for sure. Either way, should be able to do what you want it for
[Galaxy Tab 3 General] r2d23cpo:
I been on bed for more than a week sick. Sorry I had not work on it. But I plan on continue.

Restl3ss

I hate to disagree with you. I consider you a MASTER, one of our good developers. '

My understanding is that the original "Ubuntu Mobile" objective was similar to you definition. But with time Ubuntu switches to "Ubuntu Touch" and went in a separate direction by adopting some of CianogenMod specific Android routines. And adopted Googles manufactured phones as prototypes. By doing that they hope to easy the implementation. It been said that program made for to Work on a Desktop will not run on Touch. But programs made for Touch are supposed to run on a Special Shell in Ubuntu Desktop. That is what I understood. I know I should had google it before this post, but I am still sick and kind of lazy. Sorry if I am wrong.

Now last time I check, there where NO official x86 devices been supported for Ubuntu Touch. But the good news is that they are offering a "Generic x86" version in their domain. But there is no instructions as to how to implement. I guess we can try to boot it and see what it does!
[Galaxy Tab 3 General] Restl3ss:
Thank you for the compliment :) you're pretty damn good yourself

The reason standard Linux desktop apps won't work on Ubuntu touch is because they decided not to use X11 for their interface. however, there's a way to set it up to have their interface run as an x11 client (with an x server running in background console) and thus have normal apps run through it. I can't remember a lot of the details but I read up on this a while ago.

You're right; much like how google does things Ubuntu has now gone in their own direction mobile wise. That being said, Ubuntu touch is much closer to desktop Linux than android. While it does take some tinkering to set up the way we're looking for, it's nothing a couple apt-gets and config tweaks can't fix
[Galaxy Tab 3 General] r2d23cpo:
Uhm! Interesting. Listen I am not asking you to dig on it. But if for any reason you see it again, please post some link. I will like to look at that.

I seen same concept in android, I think there is a x11 Apk in the market that serves as a demo x11 in android!.
[Galaxy Tab 3 General] Restl3ss:
I'll try to find the documentation, I was reading it on the Ubuntu forums so it shouldn't be too difficult. Yeah there's an X11 concept on the play store, I personally don't think that's the right approach due to it being an apk and not native console, but that's more based on opinion than hard fact (I'm a pretty biased Linux purist haha). Plus there's more fundamental issues with running Linux applications on android, some pretty basic libs / utilities present in GNU-Linux are absent in android (as android has its own java based runtime environment, either dalvik or ART)

Android works great on my phone, but Samsung's ROM for the tab 3 10.1 feels so half assed.

Actually the whole device in general feels pretty half assed. I honestly don't use it at all for anything besides tinkering these days. That being said if we can get native Linux it might breathe some life into it for me.

I'll help any way I can.

Cheers
[Galaxy Tab 3 General] r2d23cpo:
Tab3 10.1 is a big device so we do not carry it around as we do with a phone. In my case I have a Hard Drive tied to the net with around 700 movies, In the night I see my movies before going to bed. I like to have Full Linux so that I can have a full office suite, to be used when I am away from home. I like programing so having Full Ubuntu help me to keep me busy. Up to know I have it working on VNC but it is lagy. That is why I will like to have it natively. Now Lets make it clear. Ubuntu without x-windows run in acceptable manner under chroot under Android. It is the X-window part that we need to improve. So I do too do not use Tab3 10.1 as an Android device. But I do think it has it uses.

I still feel sick, but I hope to start working a little soon. It is just a pain in the ! jijiji All the Read, implement, compile, encapsulate in zip and test. Just to start again. It is time consuming just for little steps. And Kernel has so many unknown, on documented options that makes it insane.

Listen If you see any interesting part and will like to have my source please ask. In fact this goes to anyone. But I at this time I really do not have much. I had made so many test that I do not recall what files did what!!!

And please stay around and keep providing Ideas. Like now I may dedicate some time to "Ubuntu Touch" just for convincing me that it may be more useful than what I originally thought. But like I said, I know there is a generic x86 binary but have no Idea how to implemented.
[Galaxy Tab 3 General] Jacker31:
and its like as heavy as **** as we put it into our bags with powerbank and everything we need for it lol no different than carrying a small netbook like eee pc.

you just gave me a brainstorm idea, since this is a x86 intel based device, what if we can make it run windows like how we did to kali and ubuntu on our device.I remember someone did those last time https://www.youtube.com/watch?v=auIZtmbPu_Y but instead of xp we could do a windows 8.1 instead! with externel storage of course.

I am focus my time on kali and that "crappy ninja kernel" development now but you reminded me that i was having hard time on using kali liunx with those input.

But now i think i may just focus on adding in touch screen for kali so i wont have to struggle with it haha.
[Galaxy Tab 3 General] r2d23cpo:
I understand your point. But please undesatand my position. I am unemployed, I have this as gift 2 christmas ago. New an beter devices for linux, many. This is why in this part of the forum are you, me and some other gost. So I am just working with the tools I have. You could run 95, 98 and xp. Win7 & 8 required to many resources. We only have 1 gig ram to be share with Android and the emulator!

I see those videos. In fact I eventry. But the emulator isnonky Arm. I try to compile an old rusian version but faiked.
[Galaxy Tab 3 General] Jacker31:
I understand your position. But giving ideas can make no harm. I am just trying to spend my time on something useful. Wait I thought we have about 1.90gb of ram?

---------- Post added at 07:54 AM ---------- Previous post was at 07:52 AM ----------

@Restl3ss what happen to your pimpdroid project? it have been a long silenced while now....
[Galaxy Tab 3 General] r2d23cpo:
Nope only 1GB ram

h__p://en.wikipedia.org/wiki/Samsung_Galaxy_Tab_3_10.1

It been said this 1 GB ram make the tablet cheap to produce. Samsung thought the low price would end up in big sales!
[Galaxy Tab 3 General] sub77:
so just read the whole thread. in meanwhile iam compiling grub4android.

can you do a cat /sys/class/graphics/fb0/modes please.?
[Galaxy Tab 3 General] r2d23cpo:
[MENTION=3132221]sub77[/MENTION]

root@localhost:/# cat /sys/class/graphics/fb0/modes
U:1280x800p-0

Hi nice to see some one else is interested. Do you own a Tab3 10.1? Please stay with us, or at least point me to any possible solution. All help will be really appreciated.

Where I am, I been using an old tutorial that show how to run Linux from an external sdcard. The method allows android to boot, linux the waits for android to signal has finish boot process. Then try to take control. What I think is happening is that possible recent upgrades in Android are preventing this old method to work. It seems android manipulate the frame buffer an leave it in as state that xserver can not used it.

I have build some test that show that I can manipulate the frame buffer early in the kernel boot process, for example kexecboot and andridboot UI's can write and draw to frame buffers. But once Android boot they no longer are capable to draw in frame buffer. I even have a test program that fills the screen with color patterns. Same does not work after android boot up.

Been blind, no screen output, is an impediment in trouble shooting Linux. So I though in to finding the way to allow the Penguin and the boot process messages to show in the frame buffer. That is why I am studding the kernel.

To everyone.

I been sick for 2 weeks. Well i am felling better but still lazy.

I started to help jacker31 in the kernel development thread. He and the others understand the process to boot Linux in chroot environment. That is a good start. And they like to play with kernel. So I thought that helping them will end up helping us her. Similar interest.

So what I been doing is reading some blogs an a Book called LDD3 that talks about Kernel Driver Development, but that has some good info in Kernel debug and some data in the console.
[Galaxy Tab 3 General] r2d23cpo:
U:1280x800p-0

Only one mode! I guess that what the proprietary driver wants us to believe.

I guess U = User Mode

But why "p-0"? What it means?
[Galaxy Tab 3 General] rjmm13:
Good work! Could you send some images?

Excuse me, as you can see, i´m new user in this community.

I don´t really know if the project keeps going on or not..., but if it keeps going on, could you send some images?

I daily use Linux on my pc, so i hope the project keeps going on :)

Thanks,

Rafael.
[Galaxy Tab 3 General] razr2312:
Any progress here?...:confused:
[Galaxy Tab 3 General] razr2312:
welcome back [MENTION=5688554]r2d23cpo[/MENTION] many of us are waiting for updates
[Galaxy Tab 3 General] danerrickcuba@gmail.com:
Any help with testing should be no problem, willing to assist as long we have brick proof method used also by the asus infinity community!!
[Galaxy Tab 3 General] Mighty:
Hello, I know this is an old thread, but I'm facing the same issue of tty0 (in Tab 2 NOT Tab 3) but searching on internet gives no solutions, so I'm asking here. How did you manage to disable console=sec_log_buf??
[Nexus 6 Q&A, Help & Troubleshooting] calbruc:
I was wondering if there had been any workaround for adjusting minfree

settings.

From some quick googling, it seems that lollipop kind of prevents us from adjusting minfree values. The permissions are basically set to read-only, and they reset back to read-only after a reboot. This doesn't seem to be an N6 issue, but happens across the board in lollipop.

I would love a solution to this. I feel like the N6 is much too aggressive in killing apps. It's got three gigs of RAM and I've never seen more than half that being utilized.

Is this something developers can remedy in their ROMs? Are there any scripts or anything in the mean time?