Related
USE THIS AT YOUR OWN RISK.
I am not installing this kernel on your device. I've even gone out of my way to not give clear directions on how to install it yourself. If you decide to install this kernel, you are assuming all risks involved with it.
WARNING: THIS KERNEL IS NOT FULLY COMPATIBLE WITH THE LA3 FIRMWARE UPDATE. USING THIS KERNEL WITH THE UPDATED VERSION WILL RESULT IN WIRELESS ETHERNET BEING DISABLED.
Welcome to my custom compiled kernel for the Samsung Galaxy Tab 7.0 (wifi only.) This kernel will ONLY work for the GT-P6210 model.
The kernel should be compatible with any stock firmware or anything custom that's derived from the stock firmware. (I refuse to call it a ROM. It's not Read Only.)
First, proper credit should go to Entropy512 and his SGH-i777 kernels. It's from that work I was inspired to do this, and from that work where I'm pulling ideas and changes (when compatible.) I'd give some credit to Samsung, but they only bothered to post partial source code, and didn't even bother to post it with the proper config flags.
The idea behind this kernel is and will be to make the device more efficient. Longer battery life while running more smoothly is a Good Thing. I don't care about benchmark scores. In case someone missed that, I DO NOT CARE ABOUT BENCHMARK SCORES. Anyone can tweak a system to get a better benchmark, but that doesn't mean it'll actually work better. Concern #1 is and should always be stability. While some tweaks will be added that allow a user to make the system unstable, they won't be the default.
Differences from stock currently include:
Very slight speed increase in bootup, possibly in other areas
Support for init.d script parsing on bootup
A real busybox (with proper links) installed to /sbin (and therefore available to the system)
Undervolting and minor overclocking support (via SetCPU)
android ram_console support (useful for post-mortem of crashes.)
standard boot animation support
quicker charging with iphone chargers
Voltage and Clock Adjustments:
If you choose to tinker with the processor voltages and/or clock speeds, there will be no support in this thread. None. Yes, I'm using it myself, but I won't even support myself if I screw things up. If you find an issue with this kernel, BEFORE you post about it here, re-test after reverting all the voltage and clock speeds back to default. If it works with the default clocks/voltages, then don't waste your time or mine by posting about it to this thread. It's not supported. You can destroy your tablet by messing with the voltages and clocks.
You'll need a separate tool for voltage and clock adjustments. The one I see most frequently used is "SetCPU" (http://forum.xda-developers.com/showthread.php?t=505419.) I'm in no way affiliated with the author of that tool. You should be warned that SetCPU does not seem to be fully compatible with our tablets: There seems to be no way to bring up the menu in the program. If the program is "honeycomb compatible", this is likely due to the author making assumptions about screen dimensions on tablet devices (fairly common error.) Don't tell me about it. It's not my program.
ToDo:
Find source for the ethernet module and replace it (which will also allow adding more generic optimizations to the kernel.)
ethernet adhoc support (not really kernel specific, but not possible without the ethernet module...)
Figure out what samsung changed in the LA3 kernel (and didn't publish) so I can get the kernel working with the firmware update.
Known Issues:
Probably not compatible with stock firmware updates. (won't fix.)
NOT COMPATIBLE WITH LA3 FIRMWARE UPDATE!!
Flashing Instructions:
This is being released as an installable "update.zip" style installer. Stick the .zip file on your device, reboot into recovery, and install it from there. If this isn't enough information, please search and read the forums before changing your device kernel. (Flashing a .zip in recovery is a very basic skill that should be mastered early.)
Firmware Developers:
If you want to use it, please link to this thread and give clear indication of which version of the kernel you are including.
Legal:
This is based on the linux kernel, and therefore I'm including links to the modified source for the kernel (https://github.com/garyd9/linux_kernel_GT-P6210) and contents of initramfs (https://github.com/garyd9/initramfs_normal_GT-P6210)
PLEASE DO NOT MIRROR THE DOWNLOADS. IF YOU WANT TO REFERENCE THE KERNELS, PLEASE ONLY LINK TO THIS THREAD.
Change Log
20120128:
Support for iphone charger detection - pull up to 750mA from detected iphone chargers (1500mA from the samsung charger, and 500mA from everything else including a computer USB port.)
Testing USB "high current" charging. This is currently not enabled by default (and until I'm happy that it's stable and safe, I won't be documenting it.)
20120123: (actually posted on the 24th)
Minor adjustments related to the MMC and SD card interfaces (which includes the wifi interface)
Starting to pull in mainline kernel fixes (including fixes for some kernel panics/reboots.)
20120107:
disable mali state tracking. Doesn't seem to have any actual impact, but should reduce a small amount of overhead
add support for "reboot bootloader." Actually, the support was already there if the command sent to reboot was "download", but several android tools (such as "Quick Boot") want to send the command as "bootloader." This is only useful if you have a desire to reboot your device into "Download Mode" (aka "ODIN mode")
Replaced samsung j4fs.ko binary module with one built from sources. No impact other than easier to maintain.
20120105:
added standard bootanimation support (if bootanimation.zip is found in /system/media, it's used. Otherwise, the default samsung animation is used. Standard samsung music is played either way.)
It's now possible to tweak the conservative governor sampling rate down to 50,000 (default is still 100,000.) If done, this may make the tablet more responsive in some situations (however, there may also be a negative impact to battery life - everything is a trade-off.)
20120102:
added android ram_console support. After installing this kernel, if you reboot/crash, it should leave a file in /proc called "last_kmsg" that will show the last several kernel messages from before the reboot/crash.
20120101:
undervolting and overclocking support (only up to 1.4GHz)
If you decide that you want to overclock or undervolt your tablet, you are 100% on your own. You can easily fry your tablet's processor by messing with voltages and clock speeds. If you have issues with this kernel, remove all overclocking and voltage adjustments before you even bother posting on this thread.
Use "SetCPU" to change voltages, clocks, and governors. SetCPU can be found on the market and on XDA at the following link: http://forum.xda-developers.com/showthread.php?t=505419 (I am in no way affiliated with the author of that program.)
20111231 (initial release):
build compatible with stock ar6000.ko module
init.d script support
busybox in /sbin
cleanup of kernel config to remove excess debugging (when possible)
Frequently Asked and Anticipated Questions
Q: Will this work with the GT-P6200, GT-P6200L, or SGH-T869?
A: No
Q: Can you make a kernel for the GT-P6200, GT-P6200L, or SGH-T869?
A: I probably could if I had the hardware to test with. Without a sample of hardware, I can't even begin to guess if what I've done already will work, or what it might take to make it work. If you really want me to do one of those devices, please feel free to send me one. (Making a recovery kernel is quite a bit easier as it doesn't have to work with the ethernet, sound, modem or any other drivers.)
Q: Why doesn't this kernel include CWM Recovery?
A: On the GT7+ devices, the recovery boots from a completely seperate partition than the normal boot. When the device boots recovery, the normal boot kernel isn't ever loaded (and vice versa.) Therefore, it doesn't make sense to package them together.
Q: Why is the sky blue?
A: Please refer to: http://www.sciencemadesimple.com/sky_blue.html
reserved for even more future use
Nice.... I installed just fine. Will Play around and let you know. Thanks further kernel....
Sent from my GT-P6210 using xda premium
Nice to see! Now have a good reason to install clockwork recovery! Thanks Gary!
PLEASE IGNORE THE SIGNATURE!
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
PLEASE IGNORE THE SIGNATURE!
Click to expand...
Click to collapse
Wow, that actually made me laugh out loud. (My wife just ran in to ask if I was alright.) Thank you.
I've got a new and improved signature modified especially for you! Glad to have made you laugh! Happy New year Gary and fellow community members! I wish you and your families happiness and good health!
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
I know kernels can have an effect on colors. Gary does your kernel improve color and if not could you possible hack that part of the kernel to improve in future releases, thanks
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
I'm updating my tab in kies rite now before I flash this kernel. Your kernel should work fine? I know we can't update in kies once clockwork recovery is installed but I was wondering if kies will still recognize that I have a firmware update? I know that we have to odin back before we can update in kies but not sure about the other two questions, any help would be appreciated, thanks
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
I'm updating my tab in kies rite now before I flash this kernel. Your kernel should work fine? I know we can't update in kies once clockwork recovery is installed but I was wondering if kies will still recognize that I have a firmware update?
Click to expand...
Click to collapse
Probably, but I didn't try it. Let us know how it works out.
Thanks Gary! Recovery is up and running and even made a nandroid. I located it to make sure everything worked (took a really long time). I see your framework zip wipes the dalvik cache and I was wondering if we have to wipe both caches before flashing the kernel? Thanks for your development! Much appreciated
Sent from my GT-P6210 using xda premium
Just flashed and it feels very smooth so far thanks!
Sent from my GT-P6210 using xda premium
mike216 said:
I see your framework zip wipes the dalvik cache and I was wondering if we have to wipe both caches before flashing the kernel?
Click to expand...
Click to collapse
What framework are you referring to? I try very hard to make the stuff I do "self contained", so if a cache should be wiped, it either gets wiped automatically, or there's a message displayed telling you to do it manually.
In context of this thread, there's no need to wipe any caches before installing this kernel.
Perhaps your question is in reference to something in another thread?
It was always a big suggested instruction on wiping both the cache and dalvik cache when installing roms and other things on my nexus s and vibrant so just thought it would be the same on my tablet
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
The framework zip I was talking about was the flashable zip you put together for the theme here in the development section.
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
It was always a big suggested instruction on wiping both the cache and dalvik cache when installing roms and other things on my nexus s and vibrant so just thought it would be the same on my tablet
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
Click to expand...
Click to collapse
A kernel is not a ROM, two totally different things and you don't need to wipe to install one. An easy explanation of the difference is a kernel is what runs the hardware (cpu, memory, etc.) and a ROM is just a UI (user interface).
With ROMs the general concensus on wiping is you need to do a full system wipe as well as wipe the dalvik cache if you are switching between ROMs, say from ROM A to ROM B but do not need to wipe if it's just an incremental update say ROM A to ROM A.1 unless advised to do so by the dev.
Awesome work Gary. If I had the knowledge to do this I would. Tab feels great.
Just glad to see some little development finally kicking off.
Sent from my ICS'd themed Galaxy Tab 7+
Glad you finally got things working.
Closed-source modules piss me off... Module versioning enforcement can get even some of the best devs (netarchy and I kept missing each other on IRC, it took a week before we figured out why his Infuse kernels wouldn't boot.)
Samsung is good about releasing kernel source in a timely fashion, but they SUCK at fixing broken source releases.
(Edit: WTF? They included BCM4330 source code in your release but NOT the Atheros 6k drivers?)
Edit: This might be useful, not sure - http://linuxwireless.org/en/users/Drivers/ath6kl
After lots of testing I do find its a little quicker! Don't know if its placebo but it sure feels fast. Nice work Gary. Recovery working great but the only odd thing I noticed was how long it took to do a nandroid backup. For a minute there I thought it froze up. All is good thought
BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Kernel][Ref] Samsung Gravity Smart SGH-T589 Technical info & custom kernel project
The Samsung Gravity SMART is a low-midrange Froyo-based Android phone. It hasn't gotten a lot of attention because it's on an unpopular carrier (T-Mobile) and LOL QWERTY KEYBOARD. I intend to change that.
Technical Specifications
Below is information I've gleaned from spec sheets, Internet research, and judicious use of a loupe on my wife's broken phone.
Platform: Qualcomm S1 Snapdragon 7227 @ 800Mhz
CPU: ARM1136EJ-S
Touchscreen: ATMEL mXT224E
WiFi: Broadcom 4329
GPU: Adreno 200
RAM: 320MB, 275MB accessible
Bluetooth: ???
[more later--I'm at work and don't have all my notes]
Kernel development
I don't have anything to release yet. As a proof-of-concept, I've successfully compiled the sources provided by Samsung. It boots, but two big issues prevent me from releasing anything:
The coordinates on the digitizer are inverted--i.e. tapping the top left corner activates the bottom right, and vice versa.
The menu, back, and search capacitive buttons don't work at all.
Upcoming Features
Here's what I'm planning to add to the kernel once driver issues are resolved:
More CPU frequency scaling options
More scheduler/governor options
What's not planned
Gingerbread/ICS (phone needs updated boot loader to support 2.6.35 or later Linux kernels so we are stuck w/ Froyo for now)
I managed to hack the touchscreen driver to kinda-sorta work (at least the axes are correct now), but it's still not quite right. It's very inaccurate, which makes drawing anything (i.e. trying to play Draw Something) not work at all.
ATMEL has released drivers for the mXT series (including the 224E) but I'm having trouble getting it to work properly. Going to compare it against the kinda-working driver and see if I can fix it.
I found part of the problem, but I'm still having trouble with getting the driver to even load. Still, I discovered that the stock touchscreen driver only supports 2 simultaneous touches--the chip actually supports up to 10 simultaneous. I'm hoping to get the driver working so it's actually usable.
I have a friend with this phone i'm curious to see what you can do with it!
Man, this touchscreen driver is kicking my butt.
The official Atmel drivers don't work at all--the i2c call(s) fail during initialization and you get no touchscreen input.
The driver in the kernel released by Samsung is broken, too. In the default configuration, both axis are inverted so you have to tap the top-right of the screen to tap on something that's actually in the bottom-left. And the navigation buttons at the bottom don't work at all (menu/back/search).
So far all I've managed to do is at least get the orientation fixed, but the driver's still broken--you can't tap on anything on the edges (left/right), and the scaling is wrong so taps are mis-aligned in different parts of the screen. It's hard to describe, but comparing the output of YAMTT on stock kernel vs. compiled kernel shows glaring problems.
At this point I am trying to fix the Samsung driver, since it at least partially works. In the process, I'm doing a pretty massive code cleanup, mainly code organization and complete debug info that will make it easier to dissect exactly how the driver works and hopefully find the cause of the freaky behavior.
I've overhauled the debug output of the Samsung driver so that it's easier to parse via grep. The next trick will be actually fixing the driver.. but I'm going to be gone for annual training for the next two weeks, so things will be on hold until I get back.
I'm very excited to see what can be done with this for the phone.
This is my girlfriend's first android phone and while she's enjoying it, I want the experience to be better for her.
Good luck with your training!
SefEXE said:
I'm very excited to see what can be done with this for the phone.
This is my girlfriend's first android phone and while she's enjoying it, I want the experience to be better for her.
Good luck with your training!
Click to expand...
Click to collapse
Nice choice
This is a powerful device but unfourtuneally is an unpopular one, so there is not many developers with the Gravity
I strongly recommend you to install to follow and install this ROM on your girlfriend's phone: http://forum.xda-developers.com/showthread.php?t=1320187
Well, I've managed to get a 3.6.35.7 kernel to boot on the phone.
Samsung released the kernel source for the SGH-T589W which seems to be a Gingerbread edition of the Gravity Smart. The kernel builds successfully and manages to boot, but it gets stuck on a black screen. However, it does show up in the 'adb devices' list, so it's a start.
I believe the problem is the lack of both the OneNAND driver (AKA LinuStoreIII) and the RFS filesystem support. The modules from the stock kernel are compiled against 3.6.32.x so they don't work with the newer kernel.
My Google-Fu has turned up partial source for the same version of LinuStoreIII for the 3.6.35.7 kernel, and it successfully compiled. However, I haven't had any luck finding an RFS module.
EDIT: I think I found what I need, but I won't know until I get home!
gblues said:
Well, I've managed to get a 3.6.35.7 kernel to boot on the phone.
Samsung released the kernel source for the SGH-T589W which seems to be a Gingerbread edition of the Gravity Smart. The kernel builds successfully and manages to boot, but it gets stuck on a black screen. However, it does show up in the 'adb devices' list, so it's a start.
I believe the problem is the lack of both the OneNAND driver (AKA LinuStoreIII) and the RFS filesystem support. The modules from the stock kernel are compiled against 3.6.32.x so they don't work with the newer kernel.
My Google-Fu has turned up partial source for the same version of LinuStoreIII for the 3.6.35.7 kernel, and it successfully compiled. However, I haven't had any luck finding an RFS module.
EDIT: I think I found what I need, but I won't know until I get home!
Click to expand...
Click to collapse
NICE, keep us with update with the news :highfive:
Well, I thought I had something, but it's still not working quite right. I've got the parts for my debug cable on order. Should get here within the next week.
Well, I haven't yet gotten the serial output yet, but I do have a much more detailed output from dmesg now. I'm attaching it below.
Ugh. Samsung's OSRC is being a pain in the butt.
I contacted them requesting the correct driver. Their response: "That is the correct driver."
I responded, "Did you actually test it? Because when I compile the code you provided, the x/y axes are inverted." Their response: "Herp derp Samsung Proprietary."
My most recent response: "Don't give me that proprietary BS. The driver is GPL. If you used any of the code that's in that driver, you need to publish your modifications to it."
We'll see what happens next...
Your dedication to this project continues to provide me with a glimmer of hope for the 589. I thank you sir. Down with herp derp.
Sent from my SGH-T589 using xda app-developers app
Well, now they're claiming that the driver is the one they used in the shipping kernel. Oy!
In other news... I successfully booted Gingerbread on the phone using a stock kernel. I cheated a bit, though. I'll describe how I did it, in case anyone doubts me. The post is intentionally vague because it's not fully usable, wifi doesn't work at all, and I'm not currently at home and able to fully document the process. If anyone is actually interested in trying this out, I'll consider writing a script to automate it.
Known issues with this method:
- network time doesn't seem to work right
- wifi definitely doesn't work right
- usb mode doesn't appear at all
- The phone reports itself as a Galaxy Ace in the Settings screen.
OK, the steps:
First, the things you will need:
1) Stock SGH-T589 firmware (samfirmware.com has it)
2) Stock Galaxy Ace firmware (again on samfirmware.com)
3) unpack-bootimg.pl (google it). This is used to extract the kernel and ramdisk from boot.img
4) mkbootimg (google, or build from source). This is used to re-create the boot.img file
Steps:
- Start by unpacking each firmware package into its own folder.
- From the SGH-T589 folder, delete everything except boot.img
- From the Ace folder, delete everything except boot.img and system.rfs (MAKE SURE YOU DELETE arm11boot.img)
- Now, make an empty folder and copy the stock boot.img into it. Unpack it with unpack-boot.img.pl
- Make another empty folder and put the Ace's boot.img into it. Unpack it also.
- delete the boot.img-kernel.gz from the Ace's folder
- delete boot.img-ramdisk/lib/modules/*.ko
- copy boot.img-kernel.gz from the stock folder to the ace one.
- copy boot.img-ramdisk/lib/modules/*.ko from stock folder to corresponding dir of the ace one.
- copy boot.img-ramdisk/COOPER.rle from stock folder to ace one (optional, preserves the Gravity Smart boot splash screen)
- now, repack the boot.img-ramdisk folder into the CPIO archive
- next rebuild the boot.img file
- lastly, create ODIN archive with the rebuilt boot.img and the Ace's system.rfs
Flash the resulting tar.md5 file using Odin 4.40 USA.
Hi gblues. Very good work so far! Are you planning on porting CWM recovery? It's been ported to very similar phones, like the Ace, Gio, and Mini.
ShaunOfTheLive said:
Hi gblues. Very good work so far! Are you planning on porting CWM recovery? It's been ported to very similar phones, like the Ace, Gio, and Mini.
Click to expand...
Click to collapse
I used a similar technique (unpack, replace kernel/kernel drivers, repack) on the Galaxy Ace CWM recovery and it seems to work. Unfortunately, when I tried to use it to flash the Ace's ICS port, I get a black screen with "A N D R O I D" in the middle (note: this is after extracting the boot.img and doing the unpack/swap/repack process and flashing with ODIN). I suspect that ICS requires kernel features that simply aren't in the stock 2.6.32 kernel.
After doing some more long-term tests, my accomplishment above is a good proof-of-concept but it's not ready for prime time. Landscape mode is completely broken. Games like "Cut the Rope" only give you a black screen. The QWERTY keyboard is borked (mainly alt-keys). The SD card disappeared completely until a reboot. USB mode doesn't work. The accelerometer doesn't seem to work. The stock web browser crashes. Wifi doesn't work. The list goes on.
So that gets back to getting a custom kernel working...
This should probably be posted here, but I sadly don't have the required 10 posts to do so.
There's one issue that I noticed that is actual in 0.2.2alpha. When you choose to flash Jhinta 3.1x kernel and not 2.6x kernel, it is still linux.img that is being flashed, instead of jlinux.img.
Also there's one question (or rather a feature request). Once you have dual boot up and running it would be nice to be able to flash linux rootfs only (ubuntu.img) without changing the partition table and loosing current android install. You can't currently do that with Tubuntu, right?
Best regards,
Alex
Serkenar said:
This should probably be posted here, but I sadly don't have the required 10 posts to do so.
There's one issue that I noticed that is actual in 0.2.2alpha. When you choose to flash Jhinta 3.1x kernel and not 2.6x kernel, it is still linux.img that is being flashed, instead of jlinux.img.
Also there's one question (or rather a feature request). Once you have dual boot up and running it would be nice to be able to flash linux rootfs only (ubuntu.img) without changing the partition table and loosing current android install. You can't currently do that with Tubuntu, right?
Best regards,
Alex
Click to expand...
Click to collapse
hi!
that will be on my next release cause i flash my tubuntu image so much. i'm trying to push out a backup menu along with that new rootfs option
x3maniac said:
hi!
that will be on my next release cause i flash my tubuntu image so much. i'm trying to push out a backup menu along with that new rootfs option
Click to expand...
Click to collapse
Hi,
I'm really glad to hear that! Looking forward to the next Tubuntu release
I'd also like to ask to include cifs kernel module in your kernel build.
Thank you
Serkenar said:
Hi,
I'm really glad to hear that! Looking forward to the next Tubuntu release
I'd also like to ask to include cifs kernel module in your kernel build.
Thank you
Click to expand...
Click to collapse
new version is up with Flash rootfs only :laugh:
future release of kernel i will put cifs. right now i'm trying to get zram and overclocking right 1st.
lol i feel like a one man operation. make the program to flash ubuntu images, didn't find one i liked. so i went ahead and made one. feel that the kernel is missing too much stuff. and went ahead and i'm making that now lol... am i missing anything else i need to learn/do? hahahaha
but i'm loving it!
thanks for the support
x3maniac said:
new version is up with Flash rootfs only :laugh:
future release of kernel i will put cifs. right now i'm trying to get zram and overclocking right 1st.
lol i feel like a one man operation. make the program to flash ubuntu images, didn't find one i liked. so i went ahead and made one. feel that the kernel is missing too much stuff. and went ahead and i'm making that now lol... am i missing anything else i need to learn/do? hahahaha
but i'm loving it!
thanks for the support
Click to expand...
Click to collapse
Thank you for your effort
Speaking about your own kernel, I tried compiling one from Jhinta source, but I received odd errors at boot time. First it was this kind of errors:
lists.litmus-rt.org/pipermail/litmus-dev/2012/000215.html
it was suggested there to try changing CONFIG_DEVTMPFS_MOUNT kernel config value, I did that, and then I got some other odd errors, so I gave up
Right now I have a more or less stable 12.04 kubuntu+3.10.1 jhanti kernel with hw acceleration, sound, zram (used netinstall 0.6). I'm only missing overclocking and a cifs module, that's why I tried building my own kernel, but never got it booting. I don't know any sane methods of backing up and restoring linux on tf101 (well, dd + gzip should work, but that's rather stupid), so I'm a little hesitant about flashing your lubuntu right now. I think I'll still give it a go, but before I do that, don't you know any easy way to back up my current linux install?
Thank you
Serkenar said:
Thank you for your effort
Speaking about your own kernel, I tried compiling one from Jhinta source, but I received odd errors at boot time. First it was this kind of errors:
lists.litmus-rt.org/pipermail/litmus-dev/2012/000215.html
it was suggested there to try changing CONFIG_DEVTMPFS_MOUNT kernel config value, I did that, and then I got some other odd errors, so I gave up
Right now I have a more or less stable 12.04 kubuntu+3.10.1 jhanti kernel with hw acceleration, sound, zram (used netinstall 0.6). I'm only missing overclocking and a cifs module, that's why I tried building my own kernel, but never got it booting. I don't know any sane methods of backing up and restoring linux on tf101 (well, dd + gzip should work, but that's rather stupid), so I'm a little hesitant about flashing your lubuntu right now. I think I'll still give it a go, but before I do that, don't you know any easy way to back up my current linux install?
Thank you
Click to expand...
Click to collapse
i'm now compiling from his source. for the 3.1.10 kernel i'm using. why try to reinvent the wheel? i just recompiled and added oc and cifs, i didn't run into any compile issues but i did run into boot issues so changing the kernel to compress with lzmo instead of gzip fixed it. hope that helps
Thank you for your work on this
x3maniac said:
i'm now compiling from his source. for the 3.1.10 kernel i'm using. why try to reinvent the wheel? i just recompiled and added oc and cifs, i didn't run into any compile issues but i did run into boot issues so changing the kernel to compress with lzmo instead of gzip fixed it. hope that helps
Click to expand...
Click to collapse
x3maniac I was wondering if you have ever checked out openELEC linux. They just pushed out a new version on Distrowatch and it looks like it will have support for ARM devices. It is very lightweight at 106mb and is made to run XBMC out of the box. Might be worth a try due to its size and media streaming abilities.
Thanks
thelangosta said:
x3maniac I was wondering if you have ever checked out openELEC linux. They just pushed out a new version on Distrowatch and it looks like it will have support for ARM devices. It is very lightweight at 106mb and is made to run XBMC out of the box. Might be worth a try due to its size and media streaming abilities.
Thanks
Click to expand...
Click to collapse
thanks for the info. i will look into it, i do have a arch linux version working with 3.1 which is only about 200mb.
edit:
they have a arm version 83mb! lols
Cool
x3maniac said:
thanks for the info. i will look into it, i do have a arch linux version working with 3.1 which is only about 200mb.
edit:
they have a arm version 83mb! lols
Click to expand...
Click to collapse
Wow that is small. I have seen Roms that small but never an os. Wait, is that openELEC or Arch you are talking about.
On another note if I do end up getting around to trying your method with arch which desktop would you recommend?
Thanks
thelangosta said:
Wow that is small. I have seen Roms that small but never an os. Wait, is that openELEC or Arch you are talking about.
On another note if I do end up getting around to trying your method with arch which desktop would you recommend?
Thanks
Click to expand...
Click to collapse
openelec(rasbery pi)
if you want it to look nice then enlightment e17. for a light weight DE they make it very pretty with all the effects like compiz
or lxde
x3maniac said:
i'm now compiling from his source. for the 3.1.10 kernel i'm using. why try to reinvent the wheel? i just recompiled and added oc and cifs, i didn't run into any compile issues but i did run into boot issues so changing the kernel to compress with lzmo instead of gzip fixed it. hope that helps
Click to expand...
Click to collapse
Compression was already set to lzma. I can't figure out what I was doing wrong. Yet, you're right, no point to reinvent the wheel.
I see you've recently released your Lubuntu V1.1-rc1. The specs sound great! Could you please post the rootfs download link and also post your kernel img?
Thank you for the great work you're doing!
Serkenar said:
Compression was already set to lzma. I can't figure out what I was doing wrong. Yet, you're right, no point to reinvent the wheel.
I see you've recently released your Lubuntu V1.1-rc1. The specs sound great! Could you please post the rootfs download link and also post your kernel img?
Thank you for the great work you're doing!
Click to expand...
Click to collapse
the link to image and kernel is up. http://forum.xda-developers.com/showthread.php?t=1995157
x3maniac said:
the link to image and kernel is up. http://forum.xda-developers.com/showthread.php?t=1995157
Click to expand...
Click to collapse
I gave it a go First of all, Tubuntu flashes .\images\linux.img when choosing to flash "2.6x x3maniac kernel", I assume it should flash .\images\xlinux.img
That's not a big issue, but should be fixed
A quick list of things I noticed.
1. Things that work:
-1.2 GHz OC
-Usb mouse (when plugged before system boots, otherwise not - that's due to 3.1.10 kernel, I guess)
-cifs module
-chromium
-terminal (right clicking on your tf101linux gadget -> Shortcuts -> Terminal)
-screen brightness up/down buttons. You just have to be mindful to avoid turning the screen off this way - it won't turn on afterwards and you'll have to force reboot.
-ntfs read/write
2. Things that don't work:
-touchpad
-XF86poweroff button
-System Tools -> XTerm/UXTerm
-sound: Audacious complains "ALSA error. No suitable mixer element found. snd_mixer_find_selem failed". Gnome MPlayer just won't produce any sound, and youtube html5 videos too.
-plugging in an external usb drive. It's totally ignored. A pen drive doesn't even blink, nor the drive appears in /dev it works now. It didn't during initial launch. Don't know why, but a reboot cured this.
Also, it happens quite often that system freezes for no apparent reason and only force reboot helps. It happened twice with me already, although it's been less then an hour since I flashed lubuntu.
Tell me if you need some additional info
Regards
Serkenar said:
I gave it a go First of all, Tubuntu flashes .\images\linux.img when choosing to flash "2.6x x3maniac kernel", I assume it should flash .\images\xlinux.img
That's not a big issue, but should be fixed
A quick list of things I noticed.
1. Things that work:
-1.2 GHz OC
-Usb mouse (when plugged before system boots, otherwise not - that's due to 3.1.10 kernel, I guess)
-cifs module
-chromium
-terminal (right clicking on your tf101linux gadget -> Shortcuts -> Terminal)
-screen brightness up/down buttons. You just have to be mindful to avoid turning the screen off this way - it won't turn on afterwards and you'll have to force reboot.
-ntfs read/write
2. Things that don't work:
-touchpad
-XF86poweroff button
-System Tools -> XTerm/UXTerm
-sound: Audacious complains "ALSA error. No suitable mixer element found. snd_mixer_find_selem failed". Gnome MPlayer just won't produce any sound, and youtube html5 videos too.
-plugging in an external usb drive. It's totally ignored. A pen drive doesn't even blink, nor the drive appears in /dev it works now. It didn't during initial launch. Don't know why, but a reboot cured this.
Also, it happens quite often that system freezes for no apparent reason and only force reboot helps. It happened twice with me already, although it's been less then an hour since I flashed lubuntu.
Tell me if you need some additional info
Regards
Click to expand...
Click to collapse
i love your report! keep up the good work. this helps me narrow down the problems but without a dock i can't fix some of the issues. but try this
touchpad:
edit /etc/X11/Xorg.conf
Code:
Section "InputClass"
MatchIsTouchpad "on"
Identifier "Touchpads"
Driver "mtrack"
EndSection
should fix the touchpad issue.
i will look into fixing my script for the brightness issue. located int /usr/local/bin/tfbright
what were you doing when you freeze? i don't have a dock(still waiting for it in the mail) so i don't know if it's related to that.
i've been looking at nvidia git and downloaded there source for the linux4tegra kernel. it' compiled fine but wont boot. don't know why yet
x3maniac, I know it is off topic a bit but I just wanted to mention that I appreciate your attitude towards your work and especially criticism (aka feedback) from others about your work. Reminds me of my EVO 4G days running tommytomato's classic rom. His threads were always friendly and optimistic, much like your own.
Sent from my SPH-L710 using Tapatalk 2
x3maniac said:
i love your report! keep up the good work. this helps me narrow down the problems but without a dock i can't fix some of the issues. but try this
touchpad:
edit /etc/X11/Xorg.conf
Code:
Section "InputClass"
MatchIsTouchpad "on"
Identifier "Touchpads"
Driver "mtrack"
EndSection
should fix the touchpad issue.
i will look into fixing my script for the brightness issue. located int /usr/local/bin/tfbright
what were you doing when you freeze? i don't have a dock(still waiting for it in the mail) so i don't know if it's related to that.
i've been looking at nvidia git and downloaded there source for the linux4tegra kernel. it' compiled fine but wont boot. don't know why yet
Click to expand...
Click to collapse
Strange, but there's no /etc/X11/xorg.conf
I tried creating it with `Xorg :1 -configure`, but I get "No devices to configure. Configuration failed."
I also tried creating /etc/X11/xorg.conf with the following content
Code:
Section "InputClass"
MatchIsTouchpad "on"
Identifier "Touchpads"
Driver "mtrack"
EndSection
but touchpad wont' work.
Like I said, there appears to be no apparent reason for those freezes The only things they had in common are the following:
(as far as I can remember)
-I had a cifs share mounted
-pen drive was plugged in
-chromium was opened
I understand that isn't helpful at all, but atm I can't reproduce those freezes myself. They occur kind of randomly.
I hope linux4tegra kernel does boot after all
Thank you for your work
EDIT: 30 minutes without freezes, I hope they're gone for good! :laugh:
djlenoir said:
x3maniac, I know it is off topic a bit but I just wanted to mention that I appreciate your attitude towards your work and especially criticism (aka feedback) from others about your work. Reminds me of my EVO 4G days running tommytomato's classic rom. His threads were always friendly and optimistic, much like your own.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
+1 Totally agree
djlenoir said:
x3maniac, I know it is off topic a bit but I just wanted to mention that I appreciate your attitude towards your work and especially criticism (aka feedback) from others about your work. Reminds me of my EVO 4G days running tommytomato's classic rom. His threads were always friendly and optimistic, much like your own.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Serkenar said:
+1 Totally agree
Click to expand...
Click to collapse
as far as i see it, you guys are helping me get a working version. user/tester are as important as the devs making them. or else dev's would be out of the job. lols that's how i see it
I let lubuntu running and it froze smth like 20 minutes ago Without me doing anything. Chromium was running, pen drive plugged in and a cifs share mounted.
I'll leave it running without a pen drive plugged in, shares mounted and chromium running to see if it freezes eventually.
Serkenar said:
I let lubuntu running and it froze smth like 20 minutes ago Without me doing anything. Chromium was running, pen drive plugged in and a cifs share mounted.
I'll leave it running without a pen drive plugged in, shares mounted and chromium running to see if it freezes eventually.
Click to expand...
Click to collapse
i'm guessing jhanti's kernel is not stable. i was starting to use it more and got a random freeze. cpu1 went to sleep and wont wake up. looking into that.. i might just take nvidia's kernel 3.1.10 and try to get that working.
The title says it all, this is a great device with a lot of potential for tweaking and modding and they are very affordable as well!
I would like to mainly see a custom kernel that allows overclocking the CPU and GPU as well as double tap to lock and unlock.
I have tried flashing kernels for similar (Tegra 4) devices to no avail, I guess I do not quite know enough about the kernel to get it working.
Custom ROMs would be great as well.
Anyone out there want to give this a shot?
Thanks in advance!
imseanross1 said:
The title says it all, this is a great device with a lot of potential for tweaking and modding and they are very affordable as well!
I would like to mainly see a custom kernel that allows overclocking the CPU and GPU as well as double tap to lock and unlock.
I have tried flashing kernels for similar (Tegra 4) devices to no avail, I guess I do not quite know enough about the kernel to get it working.
Custom ROMs would be great as well.
Anyone out there want to give this a shot?
Thanks in advance!
Click to expand...
Click to collapse
I have compiled a kernel for the Tegra 4 Dreamtab that works. Haven't added any special features. There is actually a good device tree they put in the source too. It's entirely possible.
aicjofs said:
I have compiled a kernel for the Tegra 4 Dreamtab that works. Haven't added any special features. There is actually a good device tree they put in the source too. It's entirely possible.
Click to expand...
Click to collapse
Is it available on the Nab Tab Hacks site? I do not know how to modify or make kernels, I am reading about it to see if it is something I want to try or not.
Have you seen this kernel for the EVGA Tegra Note 7?
http://forum.xda-developers.com/nvidia-tegra-note-7/orig-development/kernel-t2813892
I was originally thinking I might be able to modify this kernel to wo for the Dreamtab, of course because I do not have at least ten posts I can't comment on that thread.
I know the kernel has a overclock but I don't know if it supports tap to wake.
imseanross1 said:
Is it available on the Nab Tab Hacks site? I do not know how to modify or make kernels, I am reading about it to see if it is something I want to try or not.
Have you seen this kernel for the EVGA Tegra Note 7?
http://forum.xda-developers.com/nvidia-tegra-note-7/orig-development/kernel-t2813892
I was originally thinking I might be able to modify this kernel to wo for the Dreamtab, of course because I do not have at least ten posts I can't comment on that thread.
I know the kernel has a overclock but I don't know if it supports tap to wake.
Click to expand...
Click to collapse
The initial source is here: https://www.nabitablet.com/support/source-code
However they didn't provide enough to completely build the kernel. I have made those changes here. Or at least what I did back in the beginning of October. https://github.com/aicjofs/android_kernel_fuhu_t8400n
With my source and the dreamtab defconfigs I put on there you can build a kernel. Yes the Tegra Note 7 by sharky is where you would cherrypick some mods. I will see if I can do something when I get a chance too.
Okay, thank you for the links, I will do some digging this weekend. Maybe I can figure it out!
imseanross1 said:
Okay, thank you for the links, I will do some digging this weekend. Maybe I can figure it out!
Click to expand...
Click to collapse
I added a custom branch, and added about 2300 commits to get it up to linux 3.4.110. Been running it for about 2 days and it hasn't crashed but I haven't done any major testing either. I will add some overclocking stuff in the next few days.
Actually I could use some help testing if you feel comfortable doing that.
Here is a Nvidia Dreamtab kernel.
-Linux 3.4.110
-linaro gcc 4.9 compiled.
-source for GPL reasons a few posts up.(custom branch, dreamtab_defconfig)
Just test it for stability, play games, whatever, battery life. Call it a proof of concept.
1) You HAVE to make a backup of boot and system in TWRP. It's the only way to do things as I don't have an uninstaller yet. So if it fails you will need to restore boot AND system. So make a back up of those 2.
2) Download attached zip and install in TWRP.
EDIT: Also tap2wake may not be worthwhile. From what I have read they had some issues with wakelocks decreasing battery too rapidly. Also grab some benchmarks. Antutu score or something so we have a couple reference points.
So it's just going to be impossible to root the Intel version?
Mommabeans said:
So it's just going to be impossible to root the Intel version?
Click to expand...
Click to collapse
Intel Dreamtab can be rooted.
aicjofs said:
Actually I could use some help testing if you feel comfortable doing that.
Here is a Nvidia Dreamtab kernel.
-Linux 3.4.110
-linaro gcc 4.9 compiled.
-source for GPL reasons a few posts up.(custom branch, dreamtab_defconfig)
Just test it for stability, play games, whatever, battery life. Call it a proof of concept.
1) You HAVE to make a backup of boot and system in TWRP. It's the only way to do things as I don't have an uninstaller yet. So if it fails you will need to restore boot AND system. So make a back up of those 2.
2) Download attached zip and install in TWRP.
EDIT: Also tap2wake may not be worthwhile. From what I have read they had some issues with wakelocks decreasing battery too rapidly. Also grab some benchmarks. Antutu score or something so we have a couple reference points.
Click to expand...
Click to collapse
I have flashed it, I will give an update tomorrow. So far it is stable, I have had no issues and I am running benchmarks now.
Intel Dreamtab root
aicjofs said:
Intel Dreamtab can be rooted.
Click to expand...
Click to collapse
I realize that the TEGRA version can be rooted. But I see no clear mention of the INTEL version having been sucessfully rooted.
Forgive me for not being as tech savy as you are. I have rooted devices before, but I find your "instructions" difficult to follow. You go from talking about Fuhu replacing the Intel with the Tegra to "get the recovery here." There doesn't seem to be any "click here for step by step instructions to root the Intel version" anywhere.
Mommabeans said:
I realize that the TEGRA version can be rooted. But I see no clear mention of the INTEL version having been sucessfully rooted.
Forgive me for not being as tech savy as you are. I have rooted devices before, but I find your "instructions" difficult to follow. You go from talking about Fuhu replacing the Intel with the Tegra to "get the recovery here." There doesn't seem to be any "click here for step by step instructions to root the Intel version" anywhere.
Click to expand...
Click to collapse
Where did I say that? I'll update the post if you point me to it with something more clear.
This is where I talked about rooting the intel is it this one? http://forum.xda-developers.com/showpost.php?p=57825022&postcount=25
This is a direct link to the CWM recovery that works for the Intel Dreamtab. http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Follow the instructions in his post and use the T3 option to temporary boot a custom recovery.
Download SuperSU https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Copy SuperSU.zip to device and flash in the CWM recovery.
aicjofs said:
Actually I could use some help testing if you feel comfortable doing that.
Here is a Nvidia Dreamtab kernel.
-Linux 3.4.110
-linaro gcc 4.9 compiled.
-source for GPL reasons a few posts up.(custom branch, dreamtab_defconfig)
Just test it for stability, play games, whatever, battery life. Call it a proof of concept.
1) You HAVE to make a backup of boot and system in TWRP. It's the only way to do things as I don't have an uninstaller yet. So if it fails you will need to restore boot AND system. So make a back up of those 2.
2) Download attached zip and install in TWRP.
EDIT: Also tap2wake may not be worthwhile. From what I have read they had some issues with wakelocks decreasing battery too rapidly. Also grab some benchmarks. Antutu score or something so we have a couple reference points.
Click to expand...
Click to collapse
Everything seems to be working, here are the benchmark results:
Update, got a better Antutu score this time
Antutu: 41576 (3D 4791, UX 12292, CPU 19692, RAM 4801)
Quadrant: 16099 (CPU 60019, MEM 8275, I/O 8776, 2D 1006, 3D 2418)
aicjofs said:
Where did I say that? I'll update the post if you point me to it with something more clear.
Where did you say what? I didn't say you said anything specific, and that was the problem. You didn't say anything specific.
Was this not at the bottom of your first reply to my first question? "Read my less technical and uncensored ramblings on Nabi Tablet modding
Nab Tab Hacks"
Unfortunately, "less technical" to you is not "less technical" to others. For those who are not at the level of understanding that you are, ramblings are are not helpful. When a tourist asks for directions to the Met, "Practice" is not a useful answer.
You come across very cocky and annoyed at being asked for help by someone who doesn't speak the same technical language as you do. Believe me, I will never make that mistake again and I will be sure to warn others not to disturb you either.
Click to expand...
Click to collapse
Mommabeans said:
aicjofs said:
Where did I say that? I'll update the post if you point me to it with something more clear.
Where did you say what? I didn't say you said anything specific, and that was the problem. You didn't say anything specific.
Was this not at the bottom of your first reply to my first question? "Read my less technical and uncensored ramblings on Nabi Tablet modding
Nab Tab Hacks"
Unfortunately, "less technical" to you is not "less technical" to others. For those who are not at the level of understanding that you are, ramblings are are not helpful. When a tourist asks for directions to the Met, "Practice" is not a useful answer.
You come across very cocky and annoyed at being asked for help by someone who doesn't speak the same technical language as you do. Believe me, I will never make that mistake again and I will be sure to warn others not to disturb you either.
Click to expand...
Click to collapse
@Mommabeans If you cannot be respectful please do not post in this thread any more, aicjofs did answer your question thoroughly if you look at the rest of the reply.
Your response was unnecessary and very rude.
Click to expand...
Click to collapse
Mommabeans said:
You come across very cocky and annoyed at being asked for help by someone who doesn't speak the same technical language as you do. Believe me, I will never make that mistake again and I will be sure to warn others not to disturb you either.
Click to expand...
Click to collapse
I don't get it. You said I was too brief, vague, technical, etc when I explained something somewhere. I have no idea where that somewhere is, but offered to make it more detailed if you would tell me what post/location/place on the web I said that. I even added a smiley face so you DIDN'T interrupt me as mocking you. I make 100's of post on XDA, YouTube, Nabtabhacks, etc, etc. I simply asked which of those 100's of post you thought I was not detailed enough so I could go edited it, because I honestly didn't know. Then I proceeded to give you links to how to root the Intel Dreamtab.
What part of of my reply got you so upset that you needed to attack me as a person? I respectfully disagree with your assessment. Specifically about me being annoyed to help others, as I believe you are the only person that has ever said that to me and that there is ample proof to the contrary. While we are character assassinating here, you weren't exactly detailed when answering the question I asked you, and I feel you come off a bit entitled.
There, now we have both insulted each other, can we be friends now and move forward? Where are you stuck at with the links I provided?
imseanross1 said:
Everything seems to be working, here are the benchmark results:
Update, got a better Antutu score this time
Antutu: 41576 (3D 4791, UX 12292, CPU 19692, RAM 4801)
Quadrant: 16099 (CPU 60019, MEM 8275, I/O 8776, 2D 1006, 3D 2418)
Click to expand...
Click to collapse
I have added Dynamic Fsync, exfat, f2fs(not that they are useful yet without a ROM) and a few fixes. Try the attached. You may need to enable Dynamic Fsync with kernel audtior or similiar.
aicjofs said:
I have added Dynamic Fsync, exfat, f2fs(not that they are useful yet without a ROM) and a few fixes. Try the attached. You may need to enable Dynamic Fsync with kernel audtior or similiar.
Click to expand...
Click to collapse
With this one kernel I got a score of over 55000 in Antutu, I will update later with the specific scores.
Thank you for working on this, I really appreciate it!
imseanross1 said:
With this one kernel I got a score of over 55000 in Antutu, I will update later with the specific scores.
Thank you for working on this, I really appreciate it!
Click to expand...
Click to collapse
I forgot to add the futex exploit patch, I have a kernel version with the patch I have been running. Doesn't look to hopeful for double tap or swipe to wake. I did try some overclocking but not getting the desired results so far. Tried to build a lollipop AOSP ROM the last few days but have surfaceflinger dying.
Hello
I have been able to successfully root the Fuhu Nabi Dreamtab device (IN08A), here is a simple guide step by step to do it.
Furthermore, I did it on Mac Os X, but it should works the same way on Linux or Windows as long as you can access
1. Download SuperSU latest version: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
2. Copy UPDATE-SuperSU-v2.46.zip to the device
You can either use Android File Manager or via ADB
Code:
adb push UPDATE-SuperSU-v2.46.zip /storage/sdcard0/
3. Reboot the device to the boot loader with this commande
Code:
adb reboot bootloader
4. Wait a few seconds then verify the device is detected:
Code:
fastboot devices
5. Download the Intel TWRP files at: IntelAndroid-FBRL-07-24-2015.7z
then unzip
6. Using the terminal/command, put yourself in the subfolder FB_RecoveryLauncher
Code:
cd IntelAndroid-FBRL-07-24-2015/FB_RecoveryLauncher
7. Copy/paste in the terminal the following commands, 1 line at a time (so 4 times total)
Code:
OEMCMD="stop_partitioning"
OEMTRIGGER="/system/bin/logcat"
TRIGGER=fbrl.trigger
OEMCMD="stop_partitioning"
8. Copy and paste the following command and hit Enter key:
Code:
fastboot flash /tmp/recovery.zip cwm.zip; sleep 1; fastboot flash /tmp/recovery.launcher recovery.launcher ;sleep 1; fastboot oem start_partitioning; sleep 1; fastboot flash ${OEMTRIGGER} ${TRIGGER} ; echo . ; echo "issue fastboot oem ${OEMCMD} command to start cwm recovery:" ; fastboot oem ${OEMCMD} ; echo "." ; sleep 20
PS: I tried with TWRP but the touchscreen was not reacting, so I prefered to switch back to CWM
9. If all goes well, the terminal will show these lines:
Code:
target reported max download size of 1275363328 bytes
sending '/tmp/recovery.zip' (3623 KB)...
OKAY [ 0.981s]
writing '/tmp/recovery.zip'...
OKAY [ 1.065s]
finished. total time: 2.047s
target reported max download size of 1275363328 bytes
sending '/tmp/recovery.launcher' (704 KB)...
OKAY [ 0.799s]
writing '/tmp/recovery.launcher'...
OKAY [ 1.000s]
finished. total time: 1.799s
...
(bootloader) Start partitioning
OKAY [ 1.043s]
finished. total time: 1.043s
target reported max download size of 1275363328 bytes
sending '/system/bin/logcat' (349 KB)...
OKAY [ 0.787s]
writing '/system/bin/logcat'...
OKAY [ 1.002s]
finished. total time: 1.789s
.
issue fastboot oem stop_partitioning command to start cwm recovery:
...
(bootloader) Stop partitioning
finished. total time: 1.391s
10. And the device will show loading then display CWM console.
11. Use the Volume Up/Down arrow keys to move up and down in menus, then Power to make your choice
You need here to install ZIP option
12. Select the UPDATE-SuperSU-v2.46.zip file on your storage sdcard and hit Power button
13. Wait a bit until the device confirms you are rooted
14. Reboot the device (or wipe it to factory reset and then reboot it, your choice!)
You can then install a System App Remover and get ride of all the bloatware on that tablet, turning it into a very good stock Android device
Have fun!
aicjofs said:
Where did I say that? I'll update the post if you point me to it with something more clear.
This is where I talked about rooting the intel is it this one? http://forum.xda-developers.com/showpost.php?p=57825022&postcount=25
This is a direct link to the CWM recovery that works for the Intel Dreamtab. http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Follow the instructions in his post and use the T3 option to temporary boot a custom recovery.
Download SuperSU https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Copy SuperSU.zip to device and flash in the CWM recovery.
Click to expand...
Click to collapse
Hello everyone.
Can we please get root on this phone?
Specs are:
Operating System: KaiOS
System chip: Qualcomm Snapdragon 205 MSM8905
Processor: Dual-core, 1100 MHz, ARM Cortex-A7, 32-bit, 28 nm
Graphics processor: Adreno 304
System memory: 0.5 GB RAM
Built-in storage: 4 GB
Storage expansion: up to 64 GB
sgmarouf said:
Hello everyone.
Can we please get root on this phone?
Specs are:
Operating System: KaiOS
System chip: Qualcomm Snapdragon 205 MSM8905
Processor: Dual-core, 1100 MHz, ARM Cortex-A7, 32-bit, 28 nm
Graphics processor: Adreno 304
System memory: 0.5 GB RAM
Built-in storage: 4 GB
Storage expansion: up to 64 GB
Click to expand...
Click to collapse
Im also wondering the same thing
Yes, have been able to flash my own system and it is also possible to get ADB.
I am currently working on it, but it might take some days to get something useful out of it. As I just created a new account here, I am currently not able to post any links, but you can find my stuff linked on Twitter via @nexus511.
nexus511 said:
Yes, have been able to flash my own system and it is also possible to get ADB.
I am currently working on it, but it might take some days to get something useful out of it. As I just created a new account here, I am currently not able to post any links, but you can find my stuff linked on Twitter via @nexus511.
Click to expand...
Click to collapse
Good job! :good:
0312birdzhang said:
Good job! :good:
Click to expand...
Click to collapse
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.
nexus511 said:
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.
Click to expand...
Click to collapse
This is a good news! I just bought a "banana" today, waiting for your good news :fingers-crossed:
nexus511 said:
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.
Click to expand...
Click to collapse
Sounds like you've made some impressive progress here, can't wait for more details!
Will you be posting a more detailed tutorial/how-to here or on your blog in the future?
Keep up the great work! :good:
Great work, would be great to uninstalled preinstalled *tty demo games.
@nexus511, any way you could please share the root procedure or point to some resources?
Or...at the very least when you get a spare second, how you did manage to unlock your bootloader knowing Nokia has publicly acknowledge disabling Device > Developer?
Muchas,
nexus511 said:
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.
Click to expand...
Click to collapse
fpb4 said:
@nexus511, any way you could please share the root procedure or point to some resources?
Or...at the very least when you get a spare second, how you did manage to unlock your bootloader knowing Nokia has publicly acknowledge disabling Device > Developer?
Muchas,
Click to expand...
Click to collapse
Use OmniJB can enable "Developer Mode".
Tested on sideload mode
0312birdzhang said:
Use OmniJB can enable "Developer Mode".
Tested on sideload mode
Click to expand...
Click to collapse
Cheers mate :good: , that's a step forward (and cookie points to OmniJB's dev for the firefox 52.9 esr trick) - now WebIDE lists all runtime apps in Unrestricted DevTools privileges...which is great should I be willing to debug any of those or create my own. What I am looking for though is a way to *delete/un-install/remove* (no cigar remounting /system/b2g/webapps rw without root) some of the certified pre-installed applications (assistant to start with or the bunch of packaged Gameloft bloatware). Any idea - i've pm'ed @nexus511 for some root procedure but no answer yet?
0312birdzhang said:
Use OmniJB can enable "Developer Mode".
Tested on sideload mode
Click to expand...
Click to collapse
Is there anyway I could revert installing omniJB? I'd love to be able to install factory updates again.
hello all, just give an update on how's everything regarding nokia 8110 is going
fpb4 said:
Cheers mate :good: , that's a step forward (and cookie points to OmniJB's dev for the firefox 52.9 esr trick) - now WebIDE lists all runtime apps in Unrestricted DevTools privileges...which is great should I be willing to debug any of those or create my own. What I am looking for though is a way to *delete/un-install/remove* (no cigar remounting /system/b2g/webapps rw without root) some of the certified pre-installed applications (assistant to start with or the bunch of packaged Gameloft bloatware). Any idea - i've pm'ed @nexus511 for some root procedure but no answer yet?
Click to expand...
Click to collapse
Could you remove the pre-installed apps?
Hi!
It's possible, to get full ADB-Root by injecting a patched adbd-binary. And with real swap instead of zram, the device is more responsive (background-tasks like Launcher/Homescreen are killed less often...)
As soon, as I have build my own patched adbd, I will provide an 'update.zip' -- it seems chainfire doens't like others to use his version. (OpenSource -- anyone? )
BTW: no, I don't have 'su' -- only my own priviledged additional startscript and ADB-Root but for me this is more than enough to 'work'
(my goal is to create native apps with Ada/Gnoga - meaning native but with HTML5-GUI. First tests are working well...)
I would love to have this phone without the pre-installed social media and game garbage, would your planned update.zip allow someone reasonably competent at following instructions to do this easily or is experience required?
It should be possible to remove those apps - but for me it's hard to say how. On my device there were no preinstalled apps/games other than snake. Everything else is (un)installable normally. Could be a region-thing
(I've got the european/german version)
-- but on my device the store seems to be a 'static' bunch of zips - so it could kill the store to just remove those.
(i think I would need to adjust configs for the store if I want to clean them up)
If I remember correctly, there is a flag in the app-manifest to config if an app is removeable... my first try would be to edit this flag and check if I could uninstall it normally after this
On the other hand: there is nearly no need to uninstall - KaiOS-Apps are small and with a sdcard....
(I created an extra 1GB-Swap on /data - even then enough space left)
BTW: if You have a little experience with android-stuff, rooting is simple when You know how
Enable adb --> just type *#*#33284#*#* on keypad of your phone (the digits spell 'debug' )
-- build an update.zip - sign with AOSP-Test-Keys
--- let it create '/data/opt', '/data/opt/bin'
--- put an patched adbd (chainfire's v22 works) in /data/opt/bin
--- create /data/opt/init as a shellscript, remounting / rw, replace /sbin/adbd with patched one, remount / ro kill adbd so it restarts the patched version. (you may add commands for other stuff on boot - I disable zram, enable swapfile, start en Ada-Server....)
--- and add a call to '/data/opt/init' as last line to '/etc/init.qcom.post_boot.sh' so this 'init' will start with root-rights on startup.
This way /data/opt/init will inherit root from /etc/init.qcom.post_boot.sh, so it can replace adbd - and because the patched version won't drop it's root-rights you'll have a root shell over adb.
As You see - it's quite trivial, but at the moment I don't have a patched adbd which I'm allowed to include.
(I hadn't time to build an AOSP-tree until now)
Has anyone tried installing OmniJB from 4pda.ru website? (Sorry can't post links)
If you google "4pda 890710" it will bring it up.
Also, anyway of installing whatsapp yet?
PolePolisher said:
I would love to have this phone without the pre-installed social media and game garbage, would your planned update.zip allow someone reasonably competent at following instructions to do this easily or is experience required?
Click to expand...
Click to collapse
root or create an update to edit /data/local/webapps/webapps.json
it worked on my phone no more s*** games and google stuff
Can I not just replace the /sbin/adbd from the boot.img?
(by extracting the boot.img with a flashable zip, and then unpack/repack with kitchen)