Related
I'm building CM10 from sources for encore. The build completes ok, and I can flash the image to sd card. After flashing, I get the boot loader working correctly, but the OS does not boot - black screen with screen backlight turned on. From the original fat-tire manifest.
The only suspicions thing during the build are the packaging scripts warnings about /sbin/modprobe not being found. This is normal since I'm on OS X and there is no modprobe, and even if it was it would be useless to try inserting arm modules on x64 kernel. On the other hand, if during the build process there is some chrooting going on, this might mean that a modprobe for the android did not get build/saved properly and it could easily explain why the device does not load the OS. I tried looking trough the make files, but cant find which one produces these. (I've already fixed some unportable use of sed in these files)
Any suggestions will be appreciated. Thanks.
This is a simple tool/script used to:
1. convert .png files into the format used for the splash screen on your device.
2. Make a full backup/restore of your device.
3. Flash the new image to your device.
I have only tested this on the HTC Droid DNA, if anyone wants to test it for another device and post results that would be great.
This script is based on the work done by TrueBlue_Drew, but since I am on a Mac, I got tired of booting a virtual machine every time that I wanted to make a new splash screen. So I decided to "convert" his script to a bash script to make my life easier. After testing several boot screens and all of the functions myself to make sure they all work, I decided to share the script with everyone here on XDA. I have been using this site since I got my first Android phone just a few years ago (and it was a Motorola Citrus...one of the worst "smart" phones ever created!), and have learned a ton - I figured it is time that I start giving back to the community.
Since the creation of my script for the Mac, I decided to port it to Linux as well since they both use the bash shell. The only difference was having to find the compiled adb, fastboot, and ffmpeg tools for Linux.
If you like my work, don't be afraid to click the "Thanks" button. If you see any way to improve the script or have suggestions for other functions, leave a comment. If you have a question about bash scripting or using adb, leave a comment (I may or may not be able to help, but I will try...and there are many others here that can help).
Thanks again to TrueBlue_Drew for writing a nice little batch file that got me started on the path to creating this tool for myself.
The flash/backup splash option should work for any HTC devices that use a 1080x1920 splash screen but has ONLY been confirmed working with the HTC Droid DNA (I will add others to the list if anyone else confirms they work. I am already thinking about a way to select an option for the boot screen size you want to convert in order for this to work on more devices. :fingers-crossed:
REQUIREMENTS
1. Written on Linux Mint 16, but should work on any version of Linux with a bash shell
2. Rooted HTC device with S=OFF and Eng Hboot
3. 1080x1920 png image
INSTRUCTIONS
1. Download the attached zip and unzip it somewhere on your computer.
2. Create or find the 1080x1920 image you want for your splash screen.
3. Go into the "Splash Flasher Mac" folder you unzipped and place your image
in the "place-image-here" folder.
4. Run the file "splash_flasher.sh" file in the terminal and follow the on screen instructions.
I am currently having trouble uploading the file, I will try again tomorrow. In the mean time, the script can be downloaded from my dropbox.
RESERVED
Do you by any chance know how to extract the splash screen from another device's firmware update?
Sent from my Droid DNA using Tapatalk
jamiethemorris said:
Do you by any chance know how to extract the splash screen from another device's firmware update?
Sent from my Droid DNA using Tapatalk
Click to expand...
Click to collapse
Not sure if this works with the DNA or not, but try the tools in CNexus' post. I am not on my Linux machine right now, so I can't test. If the tools work, I will see if I can incorporate them into my tool. I am also working on converting the script to use easybashgui to give a graphical interface.
Hello,
THBK1-10 is a cheap dual system (Android 4.2.2 /Windows 8.1) tablet based on Bay Trail (Intel Atom Z3740D). More details http://www.thomsoncomputing.eu/dualboot.html
I'm trying to hack it, and especially get root and use non-signed zip in recovery. Basically i'm stuck at theses points, and i'm requesting directions to continue the work.
I have posted in W8 section, but obviously, this is no longer the place
General
------------
* i can use a work-around to write system (/system, /data) partitions
* i can flash signed updates via recovery
* google apps are working flawesly. Only thing is to keep original files (stock keyboard and layout)
-> i would like to flash non-signed zip via recovery, but i guess i have to build a custom recovery, or can i exploit something else ?
Root:
-------
* no auto root is working (z4root, towelRoot). Regarding towelRoot, i tryed each 8 common parameters, and i don't really know how to do others. I have also heard this is only working in 4.4.2+
* pushing su is not working. When i'm launching it, let's say from terminal, i have a code 255 return (-1). Tested with both arm and x86 version (i'm still wondering why arm su is also returning -1, i would have expect a non valid binary. Or perhaps my x86 version is bad ?
-> i'm still trying to dig this issue, and idea on how i could do ? i believe running SU was enough... but it seems not. Any idea ?
Many thanks !
Bump. the way it is booting is based on ramdisk images (one for normal android boot, one for android recovery).
I have acces to theses img, and i can, with hexedit (perhaps mounting them directly at a filesystem), view the whole init sequence.
My question is : what triggers the root invalidation ? AFAIK, everything is done as root (mounting FS, updating permissions, etc....). Basically i can't really figure how it is handled.
Thank you !
Solved !
Graveen said:
Solved !
Click to expand...
Click to collapse
Woaw ! I'm very happy to see that somebody tried and succeed to root the THBK1 ! Please can you share your method in a tutorial when you'll have time ? :laugh:
Hello, yes !
I'm actually writing a GAPPS tuto, which is intensively tested by Zeksaine. Root will be added, as this is only a simple step inside the whole process.
This is a bit technical (read boring), but it worths the try. My TODO list is here: http://forum.xda-developers.com/showthread.php?t=2799404 , and while i'll take a little break, i hope soon to have custom recovery allowing you to directly flash gapps or supersu.
Yes ! I confirm ! Graveen has installed GAPPS on Thomoson THBK1 / Danew Dualboot tablet with sucess ! I'm not familiarised with linux environnement and realize it, but it requires some knowledges of linux command (coLinux especially)
Graveen is the only one users identified that it can put GAPPS on android environnement concerning this tablet.
Big thanks to him !
Graveen said:
Hello, yes !
I'm actually writing a GAPPS tuto, which is intensively tested by Zeksaine. Root will be added, as this is only a simple step inside the whole process.
This is a bit technical (read boring), but it worths the try. My TODO list is here: http://forum.xda-developers.com/showthread.php?t=2799404 , and while i'll take a little break, i hope soon to have custom recovery allowing you to directly flash gapps or supersu.
Click to expand...
Click to collapse
7600
I own a Cube U100GT and it's one of the many Chinese brothers of your THBK1-10. But mine came only with W 8.1.
I just start looking for a dual boot solution and I'm happy to know that it's is possible.
I don't need root for while, just play some games and apps.
So the original Android "ROM" of the tablet can do the job.
My version have 64Gb SSD and I've already resize the Win partition to make room for a new system.
Where can I look for a dual boot tuto and find this Android version?
Heya, can you post your partition list ?
What is the bios of your tablet ? Can you wire an USB keyboard to see this at boot ?
Basically, they effectively seems identical.
For partial update, you can find one here: http://www.danew.com/support-pilotes-manuels.php?type=218&produit=219 but it relies on existing android partitions i still have not dumped.
Android-x86 could worth a try also, although i doubt you will have all drivers (touch, gyro, etc..)
Graveen said:
Heya, can you post your partition list ?
What is the bios of your tablet ? Can you wire an USB keyboard to see this at boot ?
Basically, they effectively seems identical.
For partial update, you can find one here: but it relies on existing android partitions i still have not dumped.
Android-x86 could worth a try also, although i doubt you will have all drivers (touch, gyro, etc..)
Click to expand...
Click to collapse
The partition list is the standard for a windows installation (but no windows image on the end):
1: 300 Mb (Windows RE)
2: 100 Mb (System)
3: The rest (Windows). My SSD is 64Gb.
My tablet already comes with a dedicated keyboard cover, so I have full access to to UEFI Bios.
There's a lot of numbers:
Aptio Setup Utility Version 2.16.1242
Vendor - AMI
Core Version - 5.008
Project Version - 3BAGR 0.03
EC FW Version - 201401101A
Intel GOP driver - 7.0.1029
Sec RC Version - 00.05.00.00
TXE FW Version - 01.00.02.1060
I found the drivers pack for windows 8 and so I could install my PT-BR edition of W81. And reserve 20Gb at the end for another OS.
It's my first UEFI machine and I'm completely lost. There's a lot of options and I can't understand a quarter of that.
On the Tabletrepublic forum someone said that my bios recuse everything except a Windows pendrive. If is true, there's no way to put Android but changing/patching the UEFI.
Android x86 is for desktops right? And the Intel site, can I find Android images there?
Thank you. What i'll do is to check if my bios is identical to yours, because there are effectively numerous options. Then, i could finsh to dump my android partitions and let you play with them.
Honestly, the trick is the OS selection system, which is bring by the EFI bootloader (and certainly a dedicated partition). Once selection is done, another EFI bootloader (windows only) is called.
let's continue here: http://forum.xda-developers.com/showthread.php?t=2799404
This is not an Android project so I don't feel that posting it in the Android Development forum would be appropriate.
ArchLinuxARM for the manta (Samsung/Google Nexus 10) - Native Boot
Working:
Wi-Fi (with NetworkManager)
Audio (requires manual intervention)
Not Working:
Bluetooth
2D & 3D Accelerated Graphics
Installation (to a subfolder of the /data partition)
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_manta_20141210_root.tar.gz is in the root of your internal storage (/data/media/0).
Code:
su
mkdir /data/local/arch
tar -C /data/local/arch -xpzvf /data/media/0/arch_manta_20141210_root.tar.gz
Booting
Since there is no workable multiboot solution for the Nexus 10 yet, you can take one of two routes to boot this thing:
Option 1: Flash the arch_boot.img to either the recovery or the boot partition of the internal flash chip. Due to risk of BRICKING if you flash to the wrong partition, I will not provide instructions here. I might make a flashable zip later on. Note that this removes access to Android.
Option 2: Use Fastboot to tethered boot the provided kernel from another computer where it is installed:
Code:
fastboot boot boot_arch_manta.img
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
To make audio work after booting and logging in, run "fix_audio.sh" in a terminal.
Read Me
If you WIPE DATA, it will also WIPE OUT THIS PORT, all its applications, and any files you may have stored within it!
Downloads
root filesystem archive: https://drive.google.com/file/d/0B4WUjKii92l2Qkd6S3c3M2tDcTQ/view?usp=sharing
kernel for fastboot or flashing: https://drive.google.com/file/d/0B4WUjKii92l2UGhIWTlVam5vSk0/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_manta
Also available for:
Nexus 7 2013: http://forum.xda-developers.com/nex...fficial-archlinuxarm-release-n7-2013-t2969301
Galaxy S3 LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483
Free space required?
Started with 5GB+ before downloading the 1.5 tar.gz, thought it will be enough but I'm supposed it wasn't cuz I'm getting "No space left in the device" although I still have 537MB free left.
Hmm, shouldn't do that. The archive itself is 4,060 MB uncompressed according to gzip -l.
Try booting it anyway, maybe? Also, perhaps I uploaded a truncated archive. I'll have to check.
Edit: Wait, you'd need upwards of 5.5 GB free to have both the archive and the extracted files on /data.
So, I deleted my nandroid backup and was able to install it. Actually it runs very well, I think even better than when ubuntu was being officially developed by canonical for the nexus 7. Of course it was easier to run because of the MultiRom solution, always wonder why Nexus 10 it's not supported, like Nexus 4, 5, 7 and even som non-nexus devices.
tavocabe said:
So, I deleted my nandroid backup and was able to install it. Actually it runs very well, I think even better than when ubuntu was being officially developed by canonical for the nexus 7. Of course it was easier to run because of the MultiRom solution, always wonder why Nexus 10 it's not supported, like Nexus 4, 5, 7 and even som non-nexus devices.
Click to expand...
Click to collapse
I don't know, honestly. After I'm done with the HD2 flash-image port of this, I'm looking at porting kexec hardboot from a random old Epic 4G kernel to my kernel_manta on github, because that's the only ready-made Exynos hardboot patch I can find through google. Then, we could boot this with a script similar to the Galaxy S III LTE port, and someone could theoretically port MultiROM, though that someone is probably not going to be me.
Thank you, Castwilliam! It run good , with some gitch on screen, but better than ubuntu phone devReview .
But when I run pacman -Syu ( update packages), reboot and it become blackscreen, try many taps in middle touch screen, intensity light of screen is something change. What wrong when update packages in pacman ?_?.
Is the booting option 2 temporary? Can I just turn off nexus and boot back to android? Can I unplug the nexus from PC while running linux?
I have no idea what I am doing here (and you probably dislike dealing with noobs flooding forums with questions right? :silly: )
Dri0m said:
Is the booting option 2 temporary? Can I just turn off nexus and boot back to android? Can I unplug the nexus from PC while running linux?
I have no idea what I am doing here (and you probably dislike dealing with noobs flooding forums with questions right? :silly: )
Click to expand...
Click to collapse
Yes, yes and yes
Hello,
This is awesome work! It booted properly, connected to a network, and programs run just fine. But as the tablet's pixel density is pretty high, it isn't too comfortable to use. I tried adding a new resolution using xrandr, but it throws something along the lines of "failed to get gamma size for display default". I've tried googling for it, but nothing worked. What can I do to resolve this?
Thanks,
Vedanth
Just as the title says, I'm curious if there exists a touch (or hardkey, i.e. volume up/down and windoes key) enabled bootloader.
Currently i have to press arrow keys and enter to select either windows or android.
Is there such a thing? It would be amazing. Id rather not have to stop at the keyboard to boot to an os from grub.
Thanks in advance!
Well .. I had suffered from this problem for longtime and finally I solved by an app called android-x86 installer it's the only way to boot from your Windows tablet without keyboard at last what I ended up with .. so yo have to download an old version I recommend the ALPHA version and install it with android-x86 installer 2.4 UEFI version after finished installing you have to download the latest version of remix OS and extract with 7zip or winrar then replace all file with the same name in folder androidOS that the direction of ALFA you already installed now You can boot with two ways either from settings/update / recovery and then press restart now at advanced startup then after reboot choose "use a device " and last thing chose android OS wait 9 seconds in grub2 an finally the remixOS will boot or by simply choose android OS from boot menu by volume Up/down
Boot solution for XPS 12 9250
Will thank you for this post when my 'Thanks!' get replenished on XDA. I'm still only using windows 10 on this tablet PC.
It is not clear to me is this is dual boot Android/Windows, my understanding is that this particular usage of the Linux grub bootloader only boots to Remix OS which is android. Grub, as you know does have dual boot capabilities, but maybe not yet on the XPS 12 9250.
Sorry, but the instructions are not step-by-step details for me, and I seem to be not smart enough to follow them. Could you point me to a 1..., 2..., 3.... please?
Please update or PM me whenever you feel you have found a better boot solution for our 9250's. I will be most grateful.
namitutonka said:
Will thank you for this post when my 'Thanks!' get replenished on XDA. I'm still only using windows 10 on this tablet PC.
It is not clear to me is this is dual boot Android/Windows, my understanding is that this particular usage of the Linux grub bootloader only boots to Remix OS which is android. Grub, as you know does have dual boot capabilities, but maybe not yet on the XPS 12 9250.
Sorry, but the instructions are not step-by-step details for me, and I seem to be not smart enough to follow them. Could you point me to a 1..., 2..., 3.... please?
Please update or PM me whenever you feel you have found a better boot solution for our 9250's. I will be most grateful.
Click to expand...
Click to collapse
Grub can chainload the entry just fine. And when using the official tool it auto-adds an entry if it detects Windows is installed, which it will be as it's a windows tool [unless running via wine] it'll add an entry for it.
Without the tool you can do it manually. Personally I have a second easy to access efi partition that I use, if you want to do the same download a partition manager like minitool and confirm that you have 16MB of unallocated space between your efi and C: drive and I'll dig up a post/walk you through the rest tomorrow
HypoTurtle said:
Grub can chainload the entry just fine. And when using the official tool it auto-adds an entry if it detects Windows is installed, which it will be as it's a windows tool [unless running via wine] it'll add an entry for it.
Without the tool you can do it manually. Personally I have a second easy to access efi partition that I use, if you want to do the same download a partition manager like minitool and confirm that you have 16MB of unallocated space between your efi and C: drive and I'll dig up a post/walk you through the rest tomorrow
Click to expand...
Click to collapse
Very excited to pursue this, but this week is filled with close family coming here to stay for our only holiday celebration. Will post back here when I get that unallocated space, after creating a backup of the current system. May use Gparted, but will check out minitool as well.
Walk through, dual boot Remix OS + Win10 on XPS 12 9250
@HypoTurtle
Waiting on a second USB-C to USB cable so I can boot a Macrium Reflect flash drive and backup a restorable PC image to an external Hard drive. After I'm sure I can restore this image I'll try to install Remix OS.
This youtube link is straightforward and simple to follow for the dual boot installation process. I've seen many reporting hardware/software issues on the many XDA forum threads branching off of "Remix OS for PC". So obviously one size does not fit all. Compiling and replacing different Linux kernels, editing grub.cfg, initrd.img, system.img, data.img.... The very worse thing on xda forums are ignorant end-user whiners like me who want instant gratification with their perfectly working phone or tablet. This vast forum has so many xda-developers, steeped in code, gaining and sharing trial and error knowledge. So many thousands of threads where xda-developers are taken for granted to lay solutions into end-user's laps. So many of us end-users are oblivious to this baby sitting. I will try the time consuming and painstaking learning curve. The least knowledgeable member on xda-forums should try to learn and not be spoon fed. It is essential, whatever our capacity, to all become developers interested in expanding the usefulness of our devices over and above the limited and constrained manufacturer's parameters.