I have an Alcatel Pixi3 4.5 4G model 5017O and I'm working on development for this phone.
I did a hexdump on the stock boot.img and was quite surprised to see this:
00004b80 |.......... -- Sy|
00004b90 |stem halted.Atte|
00004ba0 |mpting division |
00004bb0 |by 0!...Uncompre|
00004bc0 |ssing Linux.....|
00004bd0 |decompressor ret|
00004be0 |urned an error..|
00004bf0 | done, booting t|
00004c00 |he kernel...inva|
00004c10 |lid distance too|
00004c20 | far back...inva|
00004c30 |lid distance cod|
00004c40 |e...invalid lite|
00004c50 |ral/length code.|
00004c60 |incorrect header|
00004c70 | check..unknown |
00004c80 |compression meth|
00004c90 |od..invalid wind|
00004ca0 |ow size.invalid |
00004cb0 |block type..inva|
00004cc0 |lid stored block|
00004cd0 | lengths....too |
00004ce0 |many length or d|
00004cf0 |istance symbols.|
00004d00 |invalid code len|
00004d10 |gths set....inva|
00004d20 |lid bit length r|
00004d30 |epeat...invalid |
00004d40 |literal/lengths |
00004d50 |set.invalid dist|
00004d60 |ances set...inco|
00004d70 |rrect data check|
00004d80 |....Out of memor|
00004d90 |y while allocati|
00004da0 |ng output buffer|
00004db0 |....Out of memor|
00004dc0 |y while allocati|
00004dd0 |ng input buffer.|
00004de0 |Out of memory wh|
00004df0 |ile allocating z|
00004e00 |_stream.Out of m|
00004e10 |emory while allo|
00004e20 |cating workspace|
00004e30 |....Not a gzip f|
00004e40 |ile.header error|
00004e50 |....read error..|
00004e60 |uncompression er|
00004e70 |ror.............|
Does anyone else have an Alcatel, or any MediaTek based phone with a stock boot.img, that they can check to see if all of the phones they release are like this?
You can run a hexdump and check for yourself in Linux and let me know, or post your phone specs (MediaTek based only) here as well as a link to download your stock unmodified boot.img.
To do the hexdump cd into the dir with your stock boot.img and run the following command (in Linux):
hexdump -C "boot image name" | tee boot_dump.txt
where "boot image name" is the name of your boot image (without the quotes) that you made during a readback in SP Flash tools when you did your backup of you stock rom. The hexdump will be saved to a file named boot_dump.txt.
(You may have to run "sudo apt-get install hexdump" (without the quotes) in Ubuntu if you don't already have hexdump installed.)
If this is in the wrong section, please let me know.
Related
Phone: Alcatel Onetouch 991D
I extracted the system.img(ANDROID partition) following this guide on windows: Creating a ROM dump of your MT65x3 device (easily found by searching google, since I can't post links yet)
I then copied the system.img over to linux(ubuntu 12.10).
opened terminal and invoked the command below to see the type of image.
mkimage -l system.img
Code:
Image Type : Davinci UBL Boot Image
UBL magic : 00720019
Entry Point: 00730065
nr of pages: 0064002f
start block: 00610072
start page : 00610077
Then dried: ./simg2img system.img sys.raw
And the result...
Code:
Bad magic
Anyone know how to unpack this type of image or convert it to a raw image so then I can mount it?
If you're looking for a Tool like unpacking and repacking .img files such as boot.img maybe this helps:
http://forum.xda-developers.com/showthread.php?t=1241005
Many of 6GB RAM Nokia X6 has an issue, that you can't flash system partition properly - after 1st sparse flashed, fastboot will prompt "error flashing partition".
This guide introduces a workaround for this issue.
4GB RAM Nokia X6 / 6.1 Plus needn't to follow this guide.
And 6GB RAM Nokia 7 Plus needn't to follow this guide.
Or if your 6GB RAM Nokia X6 can flash stock firmware properly, you needn't to read this guide any further.
Click to expand...
Click to collapse
I still don't clear the pattern of 6GB RAM Nokia X6 that can't flash partitions.
Prerequisites:
- Bootloader must be completely unlocked
- You have fully unpacked firmware
- Use OST LA 6.0.4 or NOST v0.4 by @stollD
Here's how:
1. Make a copy of DRG-2XXX-0-00XX-B0X.mlf at the same directory, in this example, I made a copy of "DRG-221F-0-00CN-B03.mlf".
2. Use Notepad++ or any code editor that supports unix to open "DRG-221F-0-00CN-B03 - Copy.mlf".
3. Navigate to these codes.
Code:
[Package Info 31]
PACKAGE_NAME = "system_a"
BOOT_NAME = "system_a"
OPTION = 0x40000
IMAGE_FILE = "DRG-0-221F-00CN-system.img"
[Package Info 32]
PACKAGE_NAME = "system_b"
BOOT_NAME = "system_b"
OPTION = 0x40000
IMAGE_FILE = "DRG-0-221F-00CN-system_other.img"
And modify them to:
Code:
[Package Info 31]
PACKAGE_NAME = "system_a"
BOOT_NAME = "system_a"
OPTION = 0x4
IMAGE_FILE = ""
[Package Info 32]
PACKAGE_NAME = "system_b"
BOOT_NAME = "system_b"
OPTION = 0x4
IMAGE_FILE = ""
Save it.
4. Use OST LA or NOST to flash this - you'll definitely encounter C6DA error, but don't worry about that.
5. Download TWRP for Nokia 7 Plus that doesn't require flash from here (TBA) and execute these commands under OST LA installation directory:
NOTE: YOU MUST USE fastboot-android.exe included in OST LA - DO NOT USE fastboot.exe provided by Google.
Click to expand...
Click to collapse
Code:
.\fastboot-android format userdata
.\fastboot-android reboot-bootloader
.\fastboot-android boot D:\Nokia7plusv3.2.1.0-noflash.img
After your phone booted to TWRP, you may find the touch screen doesn't work, don't worry - we only need to use adb commands.
6. Execute following commands:
[QUOTE]
You can use adb.exe from both OST LA or platform tools.
[/QUOTE]
[CODE]
.\adb push D:\DRG-221F-0-00CN-B03.nb0_unpacked\systeminfo.img /data/systeminfo.img
.\adb push D:\DRG-221F-0-00CN-B03.nb0_unpacked\DRG-0-221F-00CN-system.img /data/system_a.img
.\adb push D:\DRG-221F-0-00CN-B03.nb0_unpacked\DRG-0-221F-00CN-system_other.img /data/system_b.img
.\adb shell
simg2img /data/system_a.img /data/system_a.img.ext4
simg2img /data/system_b.img /data/system_b.img.ext4
dd if=/data/systeminfo.img of=/dev/block/bootdevice/by-name/systeminfo_a
dd if=/data/systeminfo.img of=/dev/block/bootdevice/by-name/systeminfo_b
dd if=/data/system_a.img.ext4 of=/dev/block/bootdevice/by-name/system_a
dd if=/data/system_b.img.ext4 of=/dev/block/bootdevice/by-name/system_b
rm /data/systeminfo.img
rm /data/system_a.img
rm /data/system_b.img
reboot
That's all for the whole 6GB RAM Nokia X6 stock firmware flashing guide.
If you're a developer, 6GB RAM Nokia X6 is definitely unsuitable for developing.
Thanks for the guide, it will be very useful for me. I'm trying to flash this phone for a long time and I just can't unbrick it.
A few issues I've come over while following it:
OST_LA and NOST didn't want to flash DRG-221F-0-00CN-B03 ("you need to update your software" or something like that), so I had to unpack DRG-229D-0-00WW-B01.
I couldn't find Nokia7plusv3.2.1.0-noflash.img anywhere, so I used Twrp_N6.1plus_global_Aug.
When I try to use simg2img in adb shell, I get the following error:
Code:
~ # simg2img /data/system_a.img /data/system_a.img.ext4
error: file_write: write: Out of memory
Cannot write output file
---
Update: I've flashed 250A and it works like a charm! Just had to edit the .mlf according to this guide.
Hi @hikari_calyx,
have you tried flashing Nokia X6 6GB version to 6.1 Plus International Version (Android One)?
Anything I need to consider?
Hey I bought the Nokia x6 TA-1099 6gb Chinese variant it came with the global ROM 00WW_3_38A I believe it was flashed by the seller. When I got the phone I saw there was an OTA to update the pie to v3.45B I want to know if it's safe to update via OTA because it's meant for 6.1plus
:good: thanks
twrp fails
when iam flashing twrp it is showing that no such partiton is found recovery b
--- This is not made by me. This is an repost to XDA. ---
This is 32-bit, so you can use offical TWRP.
Made by hacker12455 and Lukapanio
Bugs:
Camera and minor bugs
Installation:
(Requires ADB + Fastboot, Linux on the PC and Git)
1. Format the data partition with ext4 (Format != Wipe)
2. Download the latest halium-boot.img from https://sourceforge.net/projects/ubports-cedric/files
3. Run
Code:
fastboot flash boot halium-boot.img
4. Download the latest ubports-touch.rootfs-xenial-armhf.tar.gz from https://ci.ubports.com/job/xenial-rootfs-armhf/
5. Download the latest system.img from https://sourceforge.net/projects/ubports-cedric/files
6. Clone https://gitlab.com/JBBgameich/halium-install git repository and go into that folder
7. Run
Code:
./halium-install -v -p ut path/to/ubports-touch.rootfs-xenial-armhf.tar.gz path/to/system.img
8. Reboot your phone.
9. Run
Code:
dmesg -w
and look for an GNU/Linux device.
10. Connect your computer to the RNDIS network that appeared when you rebooted your phone. (If not already happened.)
11. SSH onto the device:
Code:
ssh [email protected]
12. Follow that guide: http://docs.ubports.com/en/latest/porting/running-ut.html
You made it!
Source: https://github.com/ubports-on-cedric
Download: http://ubports-cedric.sf.net
Fail, ignore
Screenshots!
Note: Visual glitch already fixed, old screenshots.
About this device is coming soon.
Nice, i will try it tomorrow
[censored because imei leak, looking for new screenshot]
@nift4 the broken things are fixable?
lucki1000 said:
@nift4 the broken things are fixable?
Click to expand...
Click to collapse
Sound yes
Why authors are redacted?
nift4 said:
Why authors are redacted?
Click to expand...
Click to collapse
Follow the xda rules - telegram is not allowed on xda nor is the promotion of any other social media
XDA is a place for discussion and building of android projects - if everyone went to telegram the forums would be empty
I'd advise you remove all references to telegram
Done
EDIT: I did not want to break the rules I simply did not made it
Ok, I:
- Flashed the boot image from fastboot mode
- Booted into TWRP because the halium-install script tried to use ADB (there's no ADB in fastboot mode!)
- image flashed, i rebooted and the RNDIS appeared with
Code:
sudo dmesg -w
but ssh connection is refused on port 22, and when I connected with telnet the commands from the last guide (had to use the Wayback Machine, since the actual page doesn't exist anymore) but
Code:
/ # cat /var/lib/lxc/android/rootfs/ueventd*.rc|grep ^/dev|sed -e 's/^\/dev\///'|awk '{
printf "ACTION==\"add\", KERNEL==\"%s\", OWNER=\"%s\", GROUP=\"%s\", MODE=\"%s\"\n",$1,
$3,$4,$2}' | sed -e 's/\r//' >/usr/lib/lxc-android-config/70-cedric.rules
cat: can't open '/var/lib/lxc/android/rootfs/ueventd*.rc': No such file or directory
/bin/sh: can't create /usr/lib/lxc-android-config/70-cedric.rules: nonexistent directory
/ #
So, what am I doing wrong? Is there a more recent version?
Dual Boot ChromeOS with Linux or Windows!
Update 1: This thread has been fully rewritten for Windows too!
Update 2: Added Steps for Arch Based Distros!
This guide will tell you how you can dual boot ChromeOS with Linux or Windows! This guide is based on the official GitHub page!
Update2: Added troubleshoot section: Added ChromeOS not detecting fix
INDEX
• About
• Requierments
• Downloads
• Intel CPUs
• Types of recoveries
• AMD CPUs
• Linux Installation
• Preparing environment
• Installation
◦ Gparted
◦ Secureboot
• Windows Installation
• Preparing Linux Environment
◦ Preparing Environment
◦ Installation
◦ Secureboot
• Troubleshoot
• Fix ChromeOS not detecing
• Credits
AboutChromeOS, is an Operating system based on Gentoo Linux and designed by Google based on the ChromiumOS an open source project but unlike that ChromeOS is not open source, ChromeOS uses Google API and has intergrated Google Apps and Google Chrome as its interface! It also supports android apps!
Why chromeOS ? ChromeOS is a very smooth OS unlike other Android-x86 projects it is a fully functional and powerful OS, though it is not an ideal choice for gaming because it does not support the keymapping function. But if it ever gets Key Mapping there is no better option for running android for your PC other than chromeOS
Brunch, To keep it short and simple brunch is a framework which can help you to run ChromeOS on your Device even if its not a chromebook!
Requierments
• qs-x86_64 based computer with UEFI boot support (you can check that just search on google if you don’t know)
◦ With MBR patch your MBR/Legacy device might be supported
• Administrator Permissions
• Should have an Intel CPU (check conditions for that too)
◦ Intel 1st gen Core are supported only till ChromeOS 81 (This release may not be available anymore)
◦ Atom, Celeron and Pentium processors are supported since Baytrail and later versions!
• AMD Ryzen and AMD Stoney Ridge are supported, but it is limited
• Nvidia GPUs are not supported (if you have one then its ok, but ChromeOS won’t detect it)
• No Virtual Machines (VMs) are supported
• ARM CPUs are not supported at all, No luck guys
• Intel Core 2 Duo and older CPUs are not supported
Now if you are supported then Great! Lets move on!
DOWNLOADS
NOTE: you can even download the eve image which is the best as its the official Pixelbook recovery, but remember the boot chances are less with that so If you don't have time/data download from the below images
Intel CPUs
• If your CPU is 10th and 11th gen open this Link note the versions and proceed to download from HERE but before read below
◦ 11th gen and some 10th gen CPUs may need kernel 5.10
• If your CPU is 1st gen to 9th gen then after opening this Link, note the versions and proceed to download from HERE and before downloading read below,
Stable Builds
For daily and frequent use [Recommeneded for average users],
these builds are reliable and are pretty stable for day-to-day use and are recommended.
Beta Builds
Good for daily use and more Beta features [Recommended],
these builds are pretty stable and relaible with a few more Beta features and just a few bugs. These are recommended and also if the stable build is not availible.
Dev Builds
Buggy and more features [Power users only, Not Recommended],
these builds are not very stable and are buggy but have more features! Not recommended for daily use. These builds are ideal for developers who want to test out some features (Liveboot)
Canary Builds
Unstable! Experimental feaatures! [NOT Recommended][DEVs ONLY],
These builds have a lot of bugs but the most of the features! These builds are not intended for average users and are only for testing.
AMD CPUs
• For Stoney Ridge and Bristol Ridge Click Here but before read the above info carefully
and proceed to download from HERE
• For Ryzen Click here but read above before downloading then carefully
and proceed to download from HERE
• for Ryzen 4xxx devices you need kernel 5.10
As of I am writing this I have an Intel 10th gen CPU and the Stable builds are unavailable so I will be downloading the BETA Build which are quite stable too!
Now we have to also download Brunch, download the latest stable version from HERE
LINUX
Prerequisites,
• You should be on a Linux Distro
• Root access
• Atleast 16gb storage you can give to the OS
• Your PC should support Brunch
• Some basics of linux terminal (if not I recommend to learn because this helps in troubleshooting problems)
• Grub2 Bootloader
Preparing the Environment
Now open Terminal by Ctrl+Alt+T
and run,
Lets enable super user permissions using the following command
Bash:
sudo su
Enter password if it asks and hit enter
Debian based Distros:
Its a good thing to update and upgrade the packages by running this command,
Bash:
sudo apt update && upgrade
Lets install the required packages the command below will install pv, tar, unzip, cgpt and gparted,
Bash:
sudo apt install pv tar unzip cgpt gparted
Arch Based Distros:
Bash:
sudo pacman -Syu pv tar unzip gparted && yay -S cgpt
Side Notes
____________________________________________________________________________________
pv,
Pipe Viewer, known as pv is a package which allows the user for the monitering of data being sent through pipe, it helps the user by giving them a visual display
Tar,
tape archive. Known as tar is used to create and extract archive files in the format of .tar, .tar.gz etc...
Cgpt,
Cgpt is a tool to manipulate GUID Partition Table from command line. It also supports ChromiumOS extentions
Gparted,
Gparted is an Advanced disk manager, its simple yet powerful UI makes it easier to create, delete or modify any partition!
Unzip
unzip command simply extracts zip files!
_____________________________________________________________________________________
Now lets go into Documents using the cd command cd simply means change directory
Bash:
cd Documents
Now lets create a new folder and open that to keep things clean and tidy
mkdir command means make directory (make folder) and cd is change to directory
Bash:
mkdir ChromeOS && cd ChromeOS
now cut/move the downloaded files to documents/ChromeOS from your file manager
Installation
Now we will extract the tar.gz archive using tar we previously downloaded! Tar calles the command to run tar and zxvf is to extract the file in format of tar.gz
Bash:
tar zxvf brunch_ filename.tar.gz
Replace the brunch_filename.tar.gz from your actual bruch file’s name
now we also want to extract the chromeos zip file this file can be extracted by using the unzip command!
Bash:
unzip chromeos_ filename.bin.zip
Replace the chromeos_filename.bin.zip from your actual chromeOS file’s name
once done
if you already have an empty disk and are deciding to use that for installation then just check these things:
the partition should be ext4 or ntfs (ext4 recommended)
if not or if you don’t know what partition is it then
1. open Gparted and if under the file system your partion shows ext4 then close Gparted and if not then
2. right click the patition then
3. select format to and
4. select ext4 after that
5. click the ✓ logo and proceed after that
6. close Gparted.
If you don’t have a free partition or you want to create a different partition then,
minimize terminal and open Gparted (if you ran the first command it is automatically installed).
1. Now open Gparted and
2. Resize your storage and free up 16-100 gb of storage, to do that right click the partition you want to give storage from,
3. Click on the resize/move and
4. In the Free space following (MiB) text box enter the amount of storage you want to give to chromeOS in MB and click resize,
5. now you will notice a new space created called unallocated right click on it then click on new.
6. Now select Create as Primary Partion and File System: ext4 and click add! Now again click the ✓ Icon and proceed.
Also in Gparted note the name of your ChromeOS partition below the “Partition” table
for eg: /dev/sda11, /dev/mmcblk0p5 or /dev/nvme0n1p4
now open terminal,
now we will create a new mountpoint for that we will create a new directory using mkdir. The ~ is a symbol of your home directory so ~/tmpmount actually means home/tmpmount!
Bash:
mkdir -p ~/tmpmount
Now its time to mount the partition at the mountpoint
now this command will mount your partition named dev/partion to tmpmount!
Bash:
sudo mount /dev/partition ~/tmpmount
here replace the ‘partition’ to your partition name you saw in Gparted
Now
as we did before replace the chromeos_filename.bin to your actual file’s name and also replace the size from the amount of storage you want to give to chromeOS, minimum 16gb maximum your choice.
This command runs the chromeos-install.sh file in bash this file runs the installer! With the source (-src) being chromeos.bin file and the destination (-dst) being ~/tmpmount/chromeos.img and the size (-s) is what you desire
Bash:
sudo bash chromeos-install.sh -src chromeos_filename.bin -dst ~/tmpmount/chromeos.img -s size
Now if it asks for confirmation then type yes in the prompt
Now after it is over you should see something like this:
**************************************************************
menuentry "ChromeOS" --class "brunch" {
rmmod tpm
search --no-floppy --set=root --file /chromeos.img
loopback loop /chromeos.img
source (loop,12)/efi/boot/settings.cfg
if [ -z $verbose ] -o [ $verbose -eq 0 ]; then
linux (loop,7)$kernel boot=local noresume noswap loglevel=7 options=$options chromeos_bootsplash=$chromeos_bootsplash $cmdline_params \
cros_secure cros_debug loop.max_part=16 img_uuid=8191adfb-ab27-4e4d-a12e-b9e49aa1b466 img_path=/chromeos.img \
console= vt.global_cursor_default=0 brunch_bootsplash=$brunch_bootsplash quiet
else
linux (loop,7)$kernel boot=local noresume noswap loglevel=7 options=$options chromeos_bootsplash=$chromeos_bootsplash $cmdline_params \
cros_secure cros_debug loop.max_part=16 img_uuid=8191adfb-ab27-4e4d-a12e-b9e49aa1b466 img_path=/chromeos.img
fi
initrd (loop,7)/lib/firmware/amd-ucode.img (loop,7)/lib/firmware/intel-ucode.img (loop,7)/initramfs.img
}
menuentry "ChromeOS (settings)" --class "brunch-settings" {
rmmod tpm
search --no-floppy --set=root --file /chromeos.img
loopback loop /chromeos.img
source (loop,12)/efi/boot/settings.cfg
linux (loop,7)/kernel boot=local noresume noswap loglevel=7 options= chromeos_bootsplash= edit_brunch_config=1 \
cros_secure cros_debug loop.max_part=16 img_uuid=8191adfb-ab27-4e4d-a12e-b9e49aa1b466 img_path=/chromeos.img
initrd (loop,7)/lib/firmware/amd-ucode.img (loop,7)/lib/firmware/intel-ucode.img (loop,7)/initramfs.img
*******************************************************************
Now copy the text similar to this from your terminal and paste it in a notes app or save it somewhere.
Now the end is near!
Now run this command which will copy the given
Bash:
sudo cp /etc/grub.d/40_custom /etc/grub.d/99_brunch
Running this command will open the nano text editor to edit these files,
Bash:
sudo nano /etc/grub.d/99_brunch
Now a file will open,
1. Now paste the text you copied before in a new line
2. then press Ctrl+X then type y to save it and hit enter
Now lastly run,
Debian:
Bash:
sudo update-grub
and
Bash:
sudo update-grub2
Arch:
Bash:
sudo pacman -Syu
this will update your grub configuration!
Now for those who have secure boot enabled you will have to follow some extra steps.
Now there are 2 ways:
• Way 1 [run if Way 2 does not work]: Go to BIOS Setup and simply disable SecureBoot and boot into ChromeOS
• Way 2 [Recomended]: Download the file from this link and paste the file in the ChromeOS folder
open terminal and run:
Bash:
cd Documents/ChromeOS
Bash:
sudo mokutil --import brunch.der
and thats it!
Windows
Prerequesites,
• Administrator access
• you have to give atleast 16gb to ChromeOS minimum, the disk should be
bitlocker disabled, and the format should be NTFS
• Windows Subsystem for Linux 2 (WSL2) or use Cygwin
• pv, tar, unzip and cgpt should be installed
• Basic Linux command knowledge
Preparing the Linux Environment
• For windows 10 and 11 users
Open Powershell and run
Code:
wsl –install
thats it
NOTE: You must be running Windows 10 version 2004 and higher (Build 19041 and higher) or Windows 11.
• for Windows 7 & 8/8.1 (works for windows 10 and 11 too)
Download and install Cygwin from HERE
after this run the CygWin terminal (for CygWin users) and for WSL2 users launch it!
Preparing Environment
And run this
Bash:
sudo apt update && sudo apt -y install pv cgpt tar unzip
If the process ends with errors then run this:
Bash:
sudo add-apt-repository universe
and run
Bash:
sudo apt update && sudo apt -y install pv cgpt tar unzip
Installation
Bash:
cd /mnt/c/Users/username/Downloads
Here replace the username by your actual username
Now run,
Bash:
tar zxvf brunch_filename.tar.gz
replace the brunch_filename.tar.gz from the real filename
Now run,
Bash:
unzip chromeos_filename.bin.zip
Here replace chromeos_filename.bin.zip from the actual filename (cmon you know the drill)
Now run,
Bash:
mkdir /mnt/c/Users/username/brunch
Again replace the username from the real username (if you want to install it in C disk)
Run,
Bash:
mkdir /mnt/d/brunch
(if you want to install in Disk D)
Now run,
Bash:
sudo bash chromeos-install.sh -src chromeos_filename.bin -dst /mnt/c/Users/username/brunch/chromeos.img -s size
Here replace chromeos_filename.bin from the real one, and replace size from the storage you want to provide (give atleast 16 gb)
Now Install Grub2Win from HERE
and run it
then click on the Manage Boot Menu and then add a new entry
Select the create user section from the type section.
Now open chromeos.grub.txt saved earlier, it will be in the same directory and copy the grub boot entries saved in that file and copy them to Grub2win
then click Ok and Apply to save the entries into Grub2win
To prevent windows from locking the NTFS partition I recommend you to switch off secureboot!
Troubleshoot
ChromeOS boot fix
this fix includes:
• Grub bootloader does not show up
• PC/Laptop directly boots into the MainOS
• the menu boot time is too short
• etc
Now there is a common issue where you have installed ChromeOS but the grub menu does not show up and your PC directly boots into the MainOS (Windows/Linux) these steps will help you fix it!
open terminal and run
Bash:
sudo apt install gedit
this will install Gedit
Gedit
is a simple text editor which is commonly used to edit system files
next run,
Bash:
sudo gedit /etc/default/grub
This will open a text document in gedit
If it asks for password then type it
Now the usual default format of the text document is like this:
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
Now you will see GRUB_TIMEOUT_STYLE=hidden
here replace the hidden from menu
next
in GRUB_TIMEOUT=0 change 0 from any number this is for how many seconds the grub menu should be visible, I recommend replacing 0 from 30.
thats it! save the file and run the command:
Bash:
sudo update-grub
and
Bash:
sudo update-grub2
Reboot now you should be able to see chromeOS in your menu!
Credits,
• Google
• Android
• ChromeOS Devs
• GitHub
• XDA
• Brunch
• Project Croissant
• Me
-Manav Harsana
possible windows 11?
ismatovvsanjarbek said:
possible windows 11?
Click to expand...
Click to collapse
This thread is for linux, I will add for windows
ismatovvsanjarbek said:
possible windows 11?
Click to expand...
Click to collapse
Added tutorial for windows!
Cygwin uses less data (and storage space) than the WSL route, right?
Also from what I understand there's no need to setup a dedicated partition for brunch? I had used Puppy Linux earlier where the file system could be located in a folder.
Edit: Cygwin does indeed use very little data no more than 30MB downloaded in the default config.
Edit2: Couldn't run the commands in Cygwin. Some error about sudo not being found. WSL2 was easy to install and didn't take more than 500MB data.
amn1987 said:
Cygwin uses less data (and storage space) than the WSL route, right?
Also from what I understand there's no need to setup a dedicated partition for brunch? I had used Puppy Linux earlier where the file system could be located in a folder.
Edit: Cygwin does indeed use very little data no more than 30MB downloaded in the default config.
Edit2: Couldn't run the commands in Cygwin. Some error about sudo not being found. WSL2 was easy to install and didn't take more than 500MB data.
Click to expand...
Click to collapse
I mean we can install it but 1. Its better to keep it clean ig 2. I am lazy im not gonna add another method for sometime atleaset. For that Cygwin thing idk I use Arch btw so idk about cygwin and stuff
I cant find the way to download beta or dev image, https://chromiumdash.appspot.com/serving-builds?deviceCategory=Chrome OS only allow download stable version
oldman20 said:
I cant find the way to download beta or dev image, https://chromiumdash.appspot.com/serving-builds?deviceCategory=Chrome OS only allow download stable version
Click to expand...
Click to collapse
Thats because the dev or beta build for the model may not be their, wait it out or try someother image
So I have a few of these Kramer Panels which aren't supported anymore (The official webpage doesn't have them anymore but the same product here) and I want to wipe out the Kronomeet Software they got going on and install some other flavor of Android (I'm thinking Lineage OS).
To start I got adb and fastboot up and running with Aptitude.
Code:
$ adb --version
Android Debug Bridge version 1.0.41
Version 28.0.2-debian
$ fastboot --version
fastboot version 28.0.2-debian
Connecting fine with adb, and using lsusb we see
Bus 001 Device 037: ID 2207:0011 Fuzhou Rockchip Electronics Company SmartTab
Googling around that name led me to the Rockchip Wiki, which had an article on Fastboot and a bunch of open source repos
https://opensource.rock-chips.com/wiki_Fastboot
Which states: "Rockchip uses 0x2207 as its USB vendor ID. This VID is not in Google's original fastboot code. So every fastboot command has to use "-i" parameter to specify vid to fastboot."
However, running -i on fastboot gives me an invalid option error:
Code:
$ sudo fastboot -i 0x2207 devices
fastboot: invalid option -- 'i'
I also tried downloading the most recent version of the android platform tools with fastboot version 33.0.3-8952118, which gave the same results.
Doing any other fastboot command without the -i just has < waiting for any device >
So essentially, I'm trying to figure out how to load a custom rom onto it, and what my next steps try are.
Other Misc Info I've tried:
In the Developer Settings on the tablet, there's no option to enable "OEM Unlocking"
Tablet doesn't have a power button, just a switch, so no pressing power and volume at the same time.
Rockchip seems to have a TWRP image available to build, which I would like to be able to fastboot flash (https://github.com/rockchip-software/TWRP/tree/android-9.0)
There's also a development tool (https://opensource.rock-chips.com/wiki_Rkdeveloptool) that also lets you load firmware.
Using adb reboot bootloader reboots the tablet to a black empty screen, which I can then communicate with the rkdeveloptool.
In this mode, lsusb returns a new name:
Code:
$ lsusb
Bus 001 Device 038: ID 2207:320a Fuzhou Rockchip Electronics Company RK3288 in Mask ROM mode
$ ./rkdeveloptool ld
DevNo=1 Vid=0x2207,Pid=0x320a,LocationID=106 Loader
$ ./rkdeveloptool ppt
**********Partition Info(parameter)**********
NO LBA Name
00 00002000 uboot
01 00004000 misc
02 00006000 resource
03 0000E000 kernel
04 00016000 boot
05 00026000 recovery
06 00036000 backup
07 00050000 cache
08 00090000 kpanic
09 00092000 system
10 00392000 metadata
11 0039A000 radical_update
12 003BA000 userdata
Found some more useful thread, and am trying to use rkflashkit. But still struggling to find out what .img to use.
Firmware Upgrade Guide For RK3188 RK3288 RK3368 Devices
UPD: Rreflashing guide for linux Host PC added. BEFORE START What you need: 1. Image file 2. Host PC (Windows) 3. USB OTG Cable Supported host OS: 1. Windows XP （32/64bit) 2. Windows 7 (32/64bit) 3. Windows 8 (32/64bit) All manipulations I...
forum.xda-developers.com
[Q] has anyone had success flashing a RK3126 based tablet?
Hello, I've got an irulu X30 (expro 30 plus) running stock firmware, nougat 7.1.2 I've been trying to use rkflashtool in linux and androidtool in windows. Both programs can report some device info and read partitions, the img files created...
forum.xda-developers.com