Database Develop

[Guide] Replacing "G-Tablet" boot logo (UPDATED)

In response to some requests, I have added some pre-made boot.img files. They need to be flashed with nvflash, but at least you don't have to mess around with linux and coverting the files.
The files attached below have this logo that replaces the "G-Tablet" boot logo:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TNT Lite 3.0 Tegra.zip
TNT Lite 3.1 Tegra.zip
VEGAn beta 3 Tegra.zip
VEGAn beta 5.1 Tegra.zip
(attached to bottom of post)
-----------------------------------------------------------------------------
ADVANCED USERS ONLY - NVFLASH REQUIRED
I would like to reiterate the importance of when I say this is not for the faint of heart. You should be familiar with nvflash, know how to pull the partition table, know how to do a full restore, etc. You are directly and blindly flashing a partition. A small percentage of devices have a different partition table, which this guide would not work for. -Rothnic.
Thanks Rothnic! I couldn't say it better myself, so I didn't!
Thank you to JSZESZE for the image I used. It can be found here.
If you need help getting NVFLASH to work, you can find it here.
This will show you how to change the second boot screen or the "G-Tablet" screen with an image of your choice. I have attached the tools you need to do it, to565 needs to be compiled. Do not ask me how, I had to search google since I never compiled anything before, but I have included the to565.c so you don't need to go looking for it.
1. Extract the boot.img out of the rom zip you are using (update.zip) to your desktop
2. Place the boot.img, unpack-bootimg.pl, to565, and the boot folder on your desktop
3. Open a terminal
4. type in terminal
Code:
perl unpack-bootimg.pl boot.img
5. You should then have boot.img-ramdisk, boot.img-kernel.gz and boot.img-ramdisk.cpio.gz on your desktop
6. Delete boot.img-ramdisk.cpio.gz
7. Open the boot.img-ramdisk directory
8. Remove and save initlogo.rle
9. Open the photo you want to use in GIMP
10. Resize to 1024 x 600
11. Click save as...
12. Name the file splash.raw
13. Select file type "raw image data" and save to your desktop
14. RGB Save Type should be Standard (R,G,B)
15. Indexed Palette type should be R,G,B (normal)
16. In terminal:
Code:
./to565 -rle < splash.raw > initlogo.rle
17. You should now have ititlogo.rle on your desktop
18. copy that file to boot.img-ramdisk directory
19. Move boot.img-ramdisk folder and boot.img-kernel.gz to the boot folder
20. In terminal:
Code:
cd boot
perl repack-bootimg.pl boot.img-kernel.gz boot.img-ramdisk boot.img
21. Should have a boot.img file in the boot directory now.
22. In terminal:
Code:
./nvflash --bl bootloader.bin --download 10 boot.img
If you read through all of this and are lost, but really want that G-Tablet screen gone, I may help you out if you ask nicely.
Roebeet, Rothnic and Gojimmy... I would love to create something with your guys' roms.

Worked a treat. Thanks again!

How about just uploading the rom with it done?

movieman123 said:
How about just uploading the rom with it done?
Click to expand...
Click to collapse
It really depends on which rom you have because the boot.img file is different in every rom.
I would invite the rom builders to incorporate these changes into their roms and I have offered via this thread to help include different initlogo.rle for the rom builders.

Hi! How to make it all in Windows? Nothing with Linux near...

KirMit said:
Hi! How to make it all in Windows? Nothing with Linux near...
Click to expand...
Click to collapse
Can't... unless you can cross-compile to565. If you manage to do that, I am not sure how you would run the perl scripts in windows because they are written to use the linux binaries.
or... you could run a VMware virtual machine with a linux dist on it. That really how I did it. I have Ubuntu running on a VM machine on Windows 7. But then again, you run into the problems of possibly never running linux before.
or... tell me which rom you are on and post the picture you want here and I can do it for you. You'll still need to do NVFLASH to get it installed on your tab.

Ok... You're right! I have 2 ways to decide this. Just find any linux based computer right now or ask you to compile boot.img from this firmware http://forum.xda-developers.com/showthread.php?t=859884 I've just flashed
I need just a g-tablet logo has been removed or replaced by simple standart nvidia or android logo.
rayden25 said:
Can't... unless you can cross-compile to565. If you manage to do that, I am not sure how you would run the perl scripts in windows because they are written to use the linux binaries.
or... you could run a VMware virtual machine with a linux dist on it. That really how I did it. I have Ubuntu running on a VM machine on Windows 7. But then again, you run into the problems of possibly never running linux before.
or... tell me which rom you are on and post the picture you want here and I can do it for you. You'll still need to do NVFLASH to get it installed on your tab.
Click to expand...
Click to collapse

KirMit said:
Ok... You're right! I have 2 ways to decide this. Just find any linux based computer right now or ask you to compile boot.img from this firmware http://forum.xda-developers.com/showthread.php?t=859884 I've just flashed
I need just a g-tablet logo has been removed or replaced by simple standart nvidia or android logo.
Click to expand...
Click to collapse
I can send you my one for VEGAn beta 3 with the black tegra+android logo when I get home in about 8 hours. You still need nvflash setup to flash it.

WickedStyx said:
I can send you my one for VEGAn beta 3 with the black tegra+android logo when I get home in about 8 hours. You still need nvflash setup to flash it.
Click to expand...
Click to collapse
It will be great! Thank you a lot! Nvflash works fine on my win laptop right now.

This image in Vegan B3 boot.img
delete the .zip off the end of the file name and flash to partition 10 with nvflash.

works great rayden thanks man

thanks for the tutorial worked great finally got rid of that logo!
Sent from my VEGAn-TAB-v1.0.0b3 using Tapatalk

aver2one said:
thanks for the tutorial worked great finally got rid of that logo!
Click to expand...
Click to collapse
That G-Tablet logo is the most unappealing logo I have ever seen... It's horrible! LOL!

Great FAQ thanks for all your good work!

rayden25 said:
... tell me which rom you are on and post the picture you want here and I can do it for you. You'll still need to do NVFLASH to get it installed on your tab.
Click to expand...
Click to collapse
I would like the attached BMP for VEGAn-TAB b5.1 please
Thanks

Agreed -- I'd like to show off the fact that this tablet has a Tegra2 inside!
...but wouldn't it be easier to implement in the bootanimation file?

nice guide gonna try this when i get home

TeutonicWolf said:
Agreed -- I'd like to show off the fact that this tablet has a Tegra2 inside!
...but wouldn't it be easier to implement in the bootanimation file?
Click to expand...
Click to collapse
Yes, it would be easier. but my point is to get rid of the gtablet boot logo. advertising viewsonic gtablet is enough on the back for me. and i would also like to keep the vegan tablet bootanimation to show what ROM i'm running

Can you do the same image posted above for the TNT Lite 2.1.2 rom? Mucho appreciated if you can! I just hate the white backgrounded logo... Thanks!

cnathanw said:
Can you do the same image posted above for the TNT Lite 2.1.2 rom? Mucho appreciated if you can! I just hate the white backgrounded logo... Thanks!
Click to expand...
Click to collapse
I will do it for you, but please verify your rom version. TNT Lite 2.12 never existed and 2.1 is very old. Do you mean 3.12?

SoupKit (again)...When you're fed up with trying to get ADB to connect in Windows.

The SoupKit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is SoupKit? At it's heart, SoupKit is for those who are tired of messing around with Windows and are ready to do try something that works. It was created to be "sort of" modular in that after the ADB installer has been installed, other Linux scripts can be installed and run from the command line by just typing the name of the script and without worrying about changing directories or dealing with permissions. It's intended to make the transition from Windows to Linux for Android a little bit easier.
How does it work?
The SoupKit ADB Installer --- FOR ALL KINDLE FIRES
This puts everything where it needs to be, installs any necessary dependencies, installs drivers, configures Linux to run adb and fastboot commands, puts the SoupKit in your $PATH and cleans up after itself, all while taking a fraction of the space needed for the Android SDK. What this means for you is, you will be able open any terminal window and start entering adb or fastboot commands immediately. There's no need to change directories, add sudo commands or certain operators that are confusing to command line newbies ( ./ ). You can enter commands just as you see them in tutorials. No more worrying about “ADB Offline”, “Status Unknown” or “List of devices attached ????????????????”. This alone can make a huge difference for anyone having Kindle Fire problems that can't be fixed in Windows or those who are overwhelmed by the technicalities of configuring Linux for Android.
What you need:
First, you need Linux. Don't worry, it's not as bad as you may think.
Luckily, all Linux distros are free to download and install on your computer. It can also be booted from a USB flash drive so you don't have to wipe out your current OS (although you probably should anyway). You can use a VM, but the only VM that I've found that can detect the Kindle Fire in fastboot mode is Parallels. Vmware won't cut it, and VirtualBox sure as hell won't cut it so don't waste your time with them if you ever need to do anything in fastboot (if you're bricked, you need fastboot).
Probably the best method to get Linux running for a new user is by setting up a Linux LiveUSB.
I'm not going to teach you how to set up a Linux LiveUSB, but there are plenty of FREE programs out there that will not only create a Linux LiveUSB for you, but will download your choice of distro as well, and all you need is a USB flash drive (preferably 8GB or larger). A Google search of “Linux LiveUSB” will offer plenty of choices, although, PendriveLinux seems to be a favorite among most. Just be sure to add plenty of “persistence” (1 or more gigabytes) or you will lose everything every time you reboot. And the better quality of flash drive you can use, the better it will be in the long run. Some flash drives just don't do well and can cause some file system corruption over time (not something you want to be dealing with while you're having Kindle Fire problems).
You'll also have to figure out how to boot your computer from a USB. Check your computer's BIOS manufacturer website for instructions on how to do this.
If you're using a LiveUSB, there is no root/sudo password, just hit enter.
Do not use a USB 3.0 port
Once you have Linux installed and booted, you need to make sure your Internet is working. It may take some configuration on your part but it is necessary for the SoupKit to install properly. Luckily, once you have an Internet connection in Linux, the hard part is over.
Don't put the SoupKit.zip on the USB drive before creating the LiveUSB. Instead, use the web browser to navigate to this page and download it once you have Linux running and your Internet connected. Once it's downloaded, you'll likely find it in your Downloads folder.
SoupKit has been tested extensively on all the latest versions of Ubuntu and Mint, but it hasn't really been tested on anything outside of that. Try other distros if you will, but be warned.
To install:
Right-click the “SoupKit.zip”, select “Extract here” open the SoupKit folder and follow the instructions in the README.
Is that all?
NOPE. What SoupKit would be complete without a little something to go with it? SEE POST #2

Due to recent updates, I've decided to remove the option to install Hashcode's 2nd bootloader. There are too many areas where things can go wrong so I think it would be best to let the user follow the small handful of instructions in the 2nd bootloader thread to get it done. IMO, it is not worth the risk to rely on the user to make sure a downgraded stock bootloader is installed before running the script. Plus I think using a script toinstall the downgraded bootloader gives users a false sense of safety in what is potentially very dangerous to do.
​
ROOT PLUS for 2nd Generation Kindle Fires
That's right. This works for ALL 2nd generation Kindle Fires
What does it do?
The screenshot above should answer that question pretty quickly.
What do you need to know?
Since Hashcode's bootloader hack is device specific, you must download the version for your device. Each one has the exact same script but the stack, boot and recovery images are different for each particular device. You must have the SoupKit installed for this to work properly. It installs in the same way as the SoupKit; unzip, double click, run in terminal, blah blah.
Make sure you have ADB enabled under “Security” in the settings.
Anything else?
At any point after installation, if you need to run the utility again, just type "rootplus" in the terminal.
What's next?
I have a few more things in store for you guys and they will all be made for the SoupKit. As packages are installed, just type the name of the package in any terminal to launch them at any point (hence "modular"). Everything will be easy to install, easy to launch, and new user friendly.
Don't be skerrd. Move out of your comfort zone a little and give Linux and SoupKit a try. I'm sure you won't be disappointed.
Credits:
* Bin4ry - of course, for providing the root exploit
* prokennexusa and his team - for testing this out on all of the second generation devices
* Thepooch - for extensive testing and always being there to lend a hand
Downloads:
SoupKit - http://d-h.st/PbX
RootPlus for all Kindle Fires - http://d-h.st/jOe

Changelog:
04-23-2013 - Update (RootPlus)
* Removed option to install Hashcode's 2nd bootloader, for safety reasons. There is absolutely nothing wrong with Hashcode's 2nd bootloader. The risk lies in recent updates from Amazon.
03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error
03-16-2013 - Bugfix: (RootPlus)
* Fixed issue with permissions on the rootplus script
03-10-2013 - Update: (RootPlus)
* Added extra safety measures, including MD5 check on 2nd bootloader install
02-23-2013 - Initial release

worked great. thanks for a great tool. easy to use.

Awesome...thank you..just set this up on my ubuntu netbook...going to try it today when I update twrp

Update 3-10-2013: Added extra safety measures, including MD5 check on 2nd bootloader install

Works great!

ok just got a new laptop and tried installing this and no go. i know its my fault..i have a fresh install of ubuntu 13.04 and i followed the instructions but when i double click the install.sh file all it does is open a document... when i installed this on my netbook with ubuntu 12.10 i had no issue. any help would be appreciated. i am new to linux

wojo797 said:
ok just got a new laptop and tried installing this and no go. i know its my fault..i have a fresh install of ubuntu 13.04 and i followed the instructions but when i double click the install.sh file all it does is open a document... when i installed this on my netbook with ubuntu 12.10 i had no issue. any help would be appreciated. i am new to linux
Click to expand...
Click to collapse
Yeah, when I updated the script, I forgot to change the permissions...
Give me a little while and I'll fix it for you.

3-16-2013: Fixed issue with permissions on the rootplus script

the issue wasnt with the rootplus it was with the soupkit itself the install.sh script

wojo797 said:
the issue wasnt with the rootplus it was with the soupkit itself the install.sh script
Click to expand...
Click to collapse
That's interesting. I checked the permissions for all scripts and executables before uploading.
I just checked on it again and they are all executable. Perhaps it has something to do with your settings or the version of Ubuntu you are using (only tested on 12.10 and earlier).
You can make a file or script executable by entering the following in the terminal:
Code:
sudo chmod a+x <file>
Or you can right-click on the file, select Properties > Permissions > "Allow executing file as program"

[OK thankOTE=soupmagnet;39303980]That's interesting. I checked the permissions for all scripts and executables before uploading.
I just checked on it again and they are all executable. Perhaps it has something to do with your settings or the version of Ubuntu you are using (only tested on 12.10 and earlier).
You can make a file or script executable by entering the following in the terminal:
Code:
sudo chmod a+x <file>
Or you can right-click on the file, select Properties > Permissions > "Allow executing file as program"[/QUOTE]
Ok thank you.. Appreciate the help and all then work...I'll try as soon as possible

03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error

03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
If you downloaded yesterday's update, please install this one. There was a bug preventing the 2nd bootloader install. It is fixed now.
Sorry for the inconvenience.

04-23-2013 - Update (RootPlus)
* Removed option to install Hashcode's 2nd bootloader, for safety reasons.
By the way, there is absolutely nothing wrong with Hashcode's 2nd bootloader. The risk lies in recent updates from Amazon and the requirement to downgrade the stock bootloader before continuing with the 2nd bootloader install process.

Hi,
I'm totally new to linux, and i managed to install the latest Linux mint (v14.0) I was also able to connect to the internet and i downloaded both the soupkit and rootplus using linux. I extractred the files and doubled clicked on the install.sh as per the readme file however, after i double click it, all the contents of the folder disappear and i don't get any options as per the readme file. The same happens with the rootplus install.sh file, all the files disappear.
These are the steps i've followed.
Installed Linux Mint v14.0 on the system after making necessary partitions(ext4 journal)
Internet connectivity present.
Downloaded both the files into the downloads folder and extracted them
double clicked on the install.sh file and everything disappeared fro the respective folders.
Please guide me as i'm completely blank here.
Regards,
CD

Hi,
I was able to make it work. Instead of double clicking the .sh file, i opened the terminal window in the extracted folder, got super user access and executed this command:
sh install.sh
So now my kindle is rooted and ads free.
Thanks a lot @soupmagnet.
Regards,
CD

So, is it safe to assume this will work on a Kindle Fire HD 8.9" running 8.3.1 fw? Thanks!

anacondo said:
So, is it safe to assume this will work on a Kindle Fire HD 8.9" running 8.3.1 fw? Thanks!
Click to expand...
Click to collapse
Sorry to answer an old post but yes.

[ROM] [4.3.1] CyanogenMod 10.2

Hi, if anyone would like to run a 4.3.1 Google OS on a Archos G9 80S device (and currently only this), download and extract this file:
19_01_2014-13_32_32
Installation (tested only with linux) :
- reboot into SDE menu and under "Format System" perform a "Reset Android & Storage" to clear all data of previous installations (this is really important!).
- reboot into SDE menu and under Developer Edition Menu -> "Export Data Partition"
- mount this usb drive
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/local/archos.ext4
sudo sync
sudo umount <Mount_Path>
- wait until the unmount process is done
- reboot into SDE menu and under Developer Edition Mernu , Flash Kernel and Initramfs : copy zImage and initramfs.cpio.lzo on the new driver that appears on desktop/laptop
- Wait for reboot your devices : after reboot you can see Android prepares the system for a while .....be patient !
What's new ?
------------ since 19_01_2014-13_32_32 -------------
Last attempt to satisfy "H" model users. Wrong fstab definition file was used.
ArchosControlCenter: Alternate command for enabling disabling 3G service activation/deactivation.
------------ since 17_01_2014-20_17_32 -------------
KSM (Kernel samepage merging) support. (Enable it in CM performance options).
HDMI enable for 101 models too.
WLAN MAC address taken from device. Until now in my releases, the MAC address where the same for all devices. (gave some conflicts, when two devices are used in parallel).
------------ since 22_12_2013-13_29_20 -------------
Deactivated PCB temperature sensor. It is not part of the devices, and (my) default setting gives the cpufreq
module a wrong view of the situation. Now it should reduce the reboot which is caused by critical temp, by reducing core speed.
------------ since 19_12_2013-23_43_36 -------------
Using CPUFreq from 3.0.31 omapzoom reference kernel
Included app from @mordesku (modified by me) -> 3G should work!
Note that if you only pushed the image as update, please make sure to delete the /data/data/com.android.providers.telephony/databases/telephony.db
(adb shell rm /data/data/com.android.providers.telephony/databases/telephony.db) and reboot the device to rebuild.
I forgot to include the apns-conf.xml so there are no APN's available (as result no data connection can be established).
Removed my Widget to not affect the archos control center app
Some kernel changes.
Enabled zram and init.d
Initial support for H models (testing and patches are welcome).
Newest CM Updates: Changes since last release
------------ since 02_12_2013-22_56_07 -------------
Removed clicks when audio driver is closed
Reduced the volume a little bit to avoid scratches
Removed default dpi setting on build
Newest CM Updates: Changes since last release
------------ since 21_11_2013-21_45_53 -------------
Using new pvr library SGX-BIN: DDK binaries and KM source [email protected]
HWComposer 1.1 interface
No ICS audio blob anymore. Adapted omap upstream audio HAL.
Some internal audio extensions by TI (omap_enhancement)
Kernel audio sources updated to 3.0.31 omap upstream release.[/INDENT]
------------ since 08_11_2013-22_14_52 -------------
CM10.2
Upstream init.rc
TI Openlink WLAN driver R5.SP6.01
Temporary disabled ClockworkMod Recovery
A widget "Archos Control Center" where the user can activate the deep sleep behavior. Warning: If you use the archos as alarm clock you will oversleep! (It only will wake up, when pressing the power button).
Also the 3G port can be activated with this widget. I discovered some hangs, which can only solved by removing and re-adding the widget on the screen. If someone can help me with this widget, please have a look at: github It's my first app ever... so it is very ugly =)
Initial A101s support.
Something I've not tried...
3G USB Stick is working.
Issues:
- GPS not reliable (as usual for every release....) -> After complete new system ("Reset Android & Storage") the GPS is working very good. Subsequent boots later it gets worse at my device(s):
My Workaround: Go into Settings->Apps->All->Google Service Framework and delete data and cache. Then reboot and GPS should e working. Also I get sufficient results with the GPS Toolbox App.
21_11_2013-21_45_53:
Microphone as degraded sound quality compared to the stock rom.
Some sound clicks here and there when system sounds are turned on.
Audio sound is a little bit quiet compared to the stock rom. (Needs to be adjusted by myself).
Can't test HDMI (both audio/video). (It's also not an use case for me). If someone would like to help....
HDMI scaling issues
"H" models doesn't seem to work.
Rebuild: All used revisions for this release are stored in a separate folder in the archive.
Additions:
Archos Control Panel App from @mordesku: http://forum.xda-developers.com/showpost.php?p=47789812&postcount=88
Archive:
17_01_2014-20_17_32
22_12_2013-13_29_20
19_12_2013-23_43_36
02_12_2013-22_56_07
21_11_2013-21_45_53
08_11_2013-22_14_52
07_11_2013-22_53_33
Archos CM10.2 - 26_10_2013-23_26_11

Thanx for your work now i'm bakcig up my data and will test as soon as possible. Is this build run from disk images or it replace original archos system?

mordesku said:
Thanx for your work now i'm bakcig up my data and will test as soon as possible. Is this build run from disk images or it replace original archos system?
Click to expand...
Click to collapse
As usual for the custom Android releases for this archos device , they don't replace the original partitions. But it is not possible to run both in parallel. So practically yes, it replace the original system.

Quallenauge said:
- Wait for reboot your devices : after reboot you can see Android prepares the system for a while .....be patient !
Click to expand...
Click to collapse
Hi again. My tab is displaying archos logo for long time (about 10-15 minutes) now is this normal. I have question where exacty i should put the update file. In debian i put it to /media/data/data/local where /media/data is my mount point.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mordesku said:
Hi again. My tab is displaying archos logo for long time (about 10-15 minutes) now is this normal. I have question where exacty i should put the update file. In debian i put it to /media/data/data/local where /media/data is my mount point.
Click to expand...
Click to collapse
Sorry, my fault.....
Can you please rename the file while you copy? (I have corrected my first post).
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/data/local/[B]archos.ext4[/B]

Quallenauge said:
Sorry, my fault.....
Can you please rename the file while you copy? (I have corrected my first post).
Code:
sudo mkdir <Mount_Path>/data/local
sudo cp archos.ext4.update <Mount_Path>/data/local/[B]archos.ext4[/B]
Click to expand...
Click to collapse
(Just for reference, when using the update mechanism the file has to placed here:
Code:
sudo cp archos.ext4.update <Mount_Path>/data/[B]media[/B]/archos.ext4.update
)

Quallenauge said:
Sorry, my fault.....
Can you please rename the file while you copy? (I have corrected my first post).
Code:
sudo mkdir <Mount_Path>/data/local
sudo cp archos.ext4.update <Mount_Path>/data/local/[B]archos.ext4[/B]
Click to expand...
Click to collapse
Renamed file as you said but still tab is stuck on archos logo.
--- edit
My bad . Got to many data directories. Rom boots form /media/data/local/archo.ext4 before was /media/data/data/local/archos.ext4

mordesku said:
Renamed file as you said but still tab is stuck on archos logo.
--- edit
My bad . Got to many data directories. Rom boots form /media/data/local/archo.ext4 before was /media/data/data/local/archos.ext4
Click to expand...
Click to collapse
Thanks for your reply. I corrected the paths in previous posts.

Is it stable for very day use???
Everithing working lie Cam and HW video?

Using it since yesterday. It's very smooth and fast. No freezes at all.
Sent from my ARCHOS 80G9 using Tapatalk 4

Installation on Mac OS X
For those of you who want to brave installation from a Mac, you can use FUSE to mount the data partition. You'll need to follow the directions here to be able to mount the partition with write access. Once the partition is mounted, follow @Quallenauge's fabulous instructions! I'm watching a spinning CyanogenMod logo right now!
Note: If you copy the file from the command line, you'll probably get a message saying "could not copy extended attributes to data/local/archos.ext4: Operation not permitted". Don't worry, the file copied just fine. If you're really paranoid, run md5sums on the file to verify.
- Dave

stealthdave said:
For those of you who want to brave installation from a Mac, you can use FUSE to mount the data partition. You'll need to follow the directions here to be able to mount the partition with write access. Once the partition is mounted, follow @Quallenauge's fabulous instructions! I'm watching a spinning CyanogenMod logo right now!
Note: If you copy the file from the command line, you'll probably get a message saying "could not copy extended attributes to data/local/archos.ext4: Operation not permitted". Don't worry, the file copied just fine. If you're really paranoid, run md5sums on the file to verify.
- Dave
Click to expand...
Click to collapse
Damn to install it yesterday i installed debian on virtualbox on my macbook
Sent from my ARCHOS 80G9 using Tapatalk 4

My tablet is still showing the snazzy CyanogenMod bootloader image after an hour and refuses to load the Android GUI. I tried starting the process over again with the same results. I am able to get to an adb shell and play around there, but Android never finishes loading. I'm running a G9 80S with 1GHz OMAP 4430 and 512MB of RAM. Logcat attached.

Hi,
thank you for building this and all your other ROMs.
Quallenauge said:
Code:
sudo mkdir <Mount_Path>/local
sudo cp archos.ext4.update <Mount_Path>/data/local/archos.ext4
Click to expand...
Click to collapse
This is inconsistent.
Is it local/ or data/local/?
I tried to install the ROM following your instructions.
I renamed "archos.ext4.update" to "archos.ext4".
I reset Android and Storage, exported the USB storage, on my machine it was mounted on /media/username/data.
I then used the following commands:
Code:
sudo mkdir /media/username/data/local
sudo cp archos.ext4 /media/username/data/local/
Then I selected "OK" in the tablet and "Flash Kernel and Initramfs" followed by:
Code:
sudo cp zImage /media/username/A80S_REC/
sudo cp initramfs.cpio.lzo /media/username/A80S_REC/
Then I rebooted the tablet.
Now the tablet was flashing the Archos logo for a second and then rebooting, in a loop.
So I guessed the local/ directory was wrong and I might have to use data/local/.
I repeated the steps above, replacing "local/" with "data/local".
This time the tablet didn't reboot in a loop, but I only got the static Archos logo, not the animated Archos logo or the CyanogenMod logo.
I probably missed a step or misread some instruction.
Any idea where I made the mistake?

@esque: Sorry for the confusion... Your first attempt was right:
Code:
sudo mkdir /media/moronoxyd/data/local
sudo cp archos.ext4 /media/moronoxyd/data/local/
@all: Please perform an unmount before pressing "OK" on the device. If not, the image is broken!
Just to be sure, reboot the tab and mount the drive and perform a
Code:
md5sum <Mount_Path>/local/archos.ext4
and verify that value with the image on your host.
If there are the same values, we have to find another solution for the problem.
@stealthdave: Your logcat file looks very close to the problem above (file image broken).

Quallenauge said:
@stealthdave: Your logcat file looks very close to the problem above (file image broken).
Click to expand...
Click to collapse
Yes, that was the issue. umount for everyone!!!

Thanks.
Great job, like buying a new tablet.
The only thing I would add is to sudo sync before unmounting.

Quallenauge said:
@all: Please perform an unmount before pressing "OK" on the device. If not, the image is broken!
Click to expand...
Click to collapse
D'oh! I knew I made a rookie mistake.
Yes, that did the trick.
Thanks Again!

Hi,
Great job.
Is there a possibility to have the same ROM for the 101 version ?
Regards
Sent from my Galaxy Nexus using xda premium

Hi,
After two days of using this rom I must say it is very fast and smooth. But on idle after 6 hours I got -40% battery drain. Also I can feel heat from it. Got installed only 2 apps and one game. Is there any chance to implement deep sleep in this rom, to minimize batery drain?

How to dual boot on me176cx part 1

This is only first part. In this part, I will NOT mention any OSes. I will teach you how to run rEFInd on this device.
In other parts, I will edit rEFInd's config file to make it really "work". BUT, after this tutorial, you may fell happy that dual boot will most likely work on the device you just hod in your hands.
This guide is for me176cx only. Steps for other devices may be similar, only try to do this on other devices if you are sure you know where the differences are and how to change the commands!
So let's begin!
My tablet before doing anything
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
on http://www.rodsbooks.com/refind/getting.html , click on get binary zip file
Extract the downloaded zip
look for the folder "refind" inside the extracted folder
////////////////////////////////////////////////////////////////////////////
Now, we need to move it to Efi System Partition.
Istall busybox. Then, install Android Terminal Emulator.
Using some file browser with root rights, make a folder in the root of your device's memory called "esp"
Then, mount Efi System Partition on it:
Run the Android Terminal Emulator, type su, and confirm the SuperUser dialog.
Then, type: busybox mount /dev/block/mmcblk0p3 /esp
it should have no output.
Then, copy the "refind" folder to file system root.
Then (using terminal emulator) copy the refind folder to the ESP.
Then, make sure it is really there
Then write: busybox umount /esp
///////////////////////////////////////////////////////////////////////
Now, add rEFInd's binary to bootorder and set the bootorder to !!!NOT!!! boot it first, becouse you have to test it first (and you do not want to run and buy the first powered hub to be able to get back in android some complicated way)
Download this file and move it to some location where you will execute it from:
http://forum.xda-developers.com/showpost.php?p=62429430&postcount=2740
(Thanks to social-design-concepts for compiling this to work on android)
Issue this command (the paste function does not work in terminal emulator so you have to rewrite it by hand)
Then, make sure the path is set well:
Then, set the boot order to boot Android first by ./efibootmgr64 -o 0001,0000
Then, set the next boot (only next boot) to rEFInd
////////////////////////////////////////////////////////////////////
Now, just power off the tablet, (do not restart) and power it on again. You will see rEFInd, but you cannot do much without powered hub.
So if you have one, look around with keyboard. If you do not have one (like me), just power off the tablet by holding the power button, power it on again and wait for the next part of this tutorial
EDIT:
tuxic001 edited rEFInd binary so you can select what to boot.
http://forum.xda-developers.com/showpost.php?p=62463032&postcount=60
\\\_///
P.S If you use nandroid backup to update, you only update kernel and ROM (or recovery, fastboot, esp partition and whatever the other partitions are), depends on what you backup. And I don't think UEFI is stored on EMMC, so if UEFI update (or bootloader, recovery, etc. update) is present, you are totally ignoring it. On the other hand, UEFI update is a risk of not being able to access it..

Is refind working with touch or volume\power keys?

A powered hub is non-optional. OTG power is super finicky on this tablet, especially if you're adding a flash drive on top of mouse and KB

t68kv said:
Is refind working with touch or volume\power keys?
Click to expand...
Click to collapse
Voume keys work, but power key doesn't. But tuxic001 is working on editing the source code so it will. Maybe tomorrow this time it will work

Good And Bad news
Which you want to hear first?
Look fo EDIT in the main post.

I also got my tablet down, it boots only to UEFI as there's no efi bootloader to load anymore.... I'll run and get a powered usb hub to try to use the UEFI, cause the vol keys don't cut it.

Awesome guide @Mis012. I got it working on my Lenovo Tab S8-50F.
Did you have a chance to try dual booting anything yet?
EDIT: Making progress

Shump said:
Awesome guide @Mis012. I got it working on my Lenovo Tab S8-50F.
Did you have a chance to try dual booting anything yet?
EDIT: Making progress
Click to expand...
Click to collapse
Yeah I have run grub 2, it was nice. I got stuck somewhere in kali linux booting process, and then ubuntu-based dostros said bad kernel magic number blah blah. So I tried abother grub. First I found was nice, but still not working with ubuntu. So I tried to use ununtu's grub. It didn't show up in rEFInd. Now I can't find the good grub again What about your progress? Did you need to use powered OTG cable?
EDIT: found working grub again, kali linux stuck at this error: http://unix.stackexchange.com/quest...o-find-a-medium-containing-a-live-file-system

Any new?? This tutorial works on Lollipop?? If do this tutorial exist any risk for example brick??
Can you do a tutorial and upload to youtube??
or someone explain me the process?
Thanks in advance.:good:

I get invalid argument on the first command lenovo tab s8

Somewhat more wrong the error invalid argument to execute the first command and at least a thousand times but nothing works I have root and I do everything to the letter I tried on the asus tablet of the same model and my Lenovo Yoga Tab 3 and same error

jet_98 said:
Somewhat more wrong the error invalid argument to execute the first command and at least a thousand times but nothing works I have root and I do everything to the letter I tried on the asus tablet of the same model and my Lenovo Yoga Tab 3 and same error
Click to expand...
Click to collapse
have you installed busybox? as simple as that.

Windows ARM64 on fajita

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
oneplus 6/6t 都可用
警告！不当操作可能会导致手机变砖！
-
20210822 updata
-
project address : https://github.com/edk2-porting
and
Tool download :https://drive.google.com/drive/folders/1GrX9JTVpKwo3WNshqIljPRc9Q6dPJDJJ?usp=sharing
boot download : https://github.com/edk2-porting/edk2-sdm845/releases/tag/v1.0.2
drives download : https://github.com/edk2-porting/WOA-Drivers/archive/refs/heads/main.zip
-
Installation tutorial
new tutorial!(English) https://forum.renegade-project.org/t/faq/95
-
article(Chinese) : https://forum.renegade-project.org/t/6-windows/194
-
Device support status
Renegade Project
Renegade Project
renegade-project.org
-
The drive is gradually improving
有问题我会不定期来看的，欢迎提问。
Questions are welcome

How are you doing with the driver ports. Nice work tho!

Keno_I said:
How are you doing with the driver ports. Nice work tho!
Click to expand...
Click to collapse
The driver is currently only basic
Such as wifi, GPU, battery, etc. are all unavailable
But this will gradually improve in the future!
-
驱动目前只有基础的
比如wifi,GPU,电池等都是不可用的
但这会在之后慢慢完善！

Nice. Good work on that, I'm assuming this port will be easier when windows arm devices get more widespread and supported

Good work. This is really great.
Will try that out the next days.
One thing I am just wondering.
How is it handled to boot Windows and Android?
So when you boot up the phone will it boot to Windows or to Android?
Or will it boot to Android and to boot to Windows you will need to fastboot the boot-fajita.img again?
Thanks!

Given it a go, it's not going bad is it? Very nice.
It took a while to set up so I wrote some scripts to partition and boot to recovery, along with scripts within recovery to deal with bootloader config. The only thing that wasn't automatic at this point was running DISM++
Good work. This is really great.
Wishmasterflo said:
Will try that out the next days.
One thing I am just wondering.
How is it handled to boot Windows and Android?
So when you boot up the phone will it boot to Windows or to Android?
Or will it boot to Android and to boot to Windows you will need to fastboot the boot-fajita.img again?
Thanks!
Click to expand...
Click to collapse
By default it will boot Android, unless you flash the windows bootloader img to boot.
I cannot recommend flashing the windows bootloader img at the moment- it worked and windows boots by default but from this point on I was unable to start TWRP, even via fastboot boot, so I'll have to MSM tool it to restore, which *does* wipe windows.
Other thoughts: This is almost usable, however, battery drain is through the roof and the touch screen driver is misconfigured for the display, so touch events are in the wrong place.
Keep going guys!

damiensturdy said:
Given it a go, it's not going bad is it? Very nice.
It took a while to set up so I wrote some scripts to partition and boot to recovery, along with scripts within recovery to deal with bootloader config. The only thing that wasn't automatic at this point was running DISM++
Good work. This is really great.
By default it will boot Android, unless you flash the windows bootloader img to boot.
I cannot recommend flashing the windows bootloader img at the moment- it worked and windows boots by default but from this point on I was unable to start TWRP, even via fastboot boot, so I'll have to MSM tool it to restore, which *does* wipe windows.
Other thoughts: This is almost usable, however, battery drain is through the roof and the touch screen driver is misconfigured for the display, so touch events are in the wrong place.
Keep going guys!
Click to expand...
Click to collapse
Great. Thanks for the answers. I will try that out as well.
I saw in the Tools folder there is a file "TouchScreen.reg" . Does that not fix the touchscreen issues or what does that do?

Wishmasterflo said:
Great. Thanks for the answers. I will try that out as well.
I saw in the Tools folder there is a file "TouchScreen.reg" . Does that not fix the touchscreen issues or what does that do?
Click to expand...
Click to collapse
Actually, the last time I did it I didn't have any touchscreen issues- I must have skipped the reg file!

I just bought a USB-c HUB to connect Mouse, keyboard, USB stick to my phone when setting this up.
So if I see this correct now and the boot file can only be booted via Fastboot and flashing it to boot is not recommended due to issues to boot TWRP afterwards there is no way now to boot that without having the phone connected to a Computer or?
OK I gave that a try now. I could boot to the EFI environment and tried to apply the Windows 11 arm64 image in Dism++.
After done the steps to select the ISO file and target C: it starts to copy files and after like 1 minute I get an error Message but all the text in the message is in Chinese letters so I dont know what the error means.
How can I set the language in Dism++ to english?
Thanks!

Wishmasterflo said:
我刚买了一个 Usb - c Hub 来连接鼠标， 键盘， Usb 粘在我的手机上， 当设置这个。
因此，如果我现在看到这个正确的启动文件，并且引导文件只能通过 Fastboot 启动，并且由于启动 TWRP 的问题而不建议将其闪烁到启动，那么现在没有办法启动该启动，而没有将手机连接到计算机或？
好吧， 我现在试了一下。我可以启动到 EFI 环境，并试图应用 Windows 11 手臂 64 图像在 Dism+.
完成选择 ISO 文件和目标 C 的步骤后：它开始复制文件，1 分钟后我收到一条错误消息，但邮件中的所有文本都以中文字母表示，因此我不知道错误是什么意思。
如何将 Dism+中的语言设置为英语？
谢谢！
Click to expand...
Click to collapse
Sorry for taking so long to reply you But this software seems to be only in Chinese

hehedi233 said:
View attachment 5390973Sorry for taking so long to reply you But this software seems to be only in Chinese
Click to expand...
Click to collapse
Thanks for the reply.
I guess Dism++ is taking the language settings from the Windows PE or boot.img and therefor it is set to Chinese.
I see when booting up the img file that that is set to Chinese. So if that can be changed to English I guess the Dism tool will be english aa well.

Wishmasterflo said:
Thanks for the reply.
I guess Dism++ is taking the language settings from the Windows PE or boot.img and therefor it is set to Chinese.
I see when booting up the img file that that is set to Chinese. So if that can be changed to English I guess the Dism tool will be english aa well.
Click to expand...
Click to collapse
you can go online to find the English version of Dism++, and then pass it in via USB disk

hehedi233 said:
you can go online to find the English version of Dism++, and then pass it in via USB disk
Click to expand...
Click to collapse
I already did that but it is in Chinese as well after launching it when booted the boot.img file therefor I guess it it fetching the language setting from the booted IMG or WinPE already.

Wishmasterflo said:
I already did that but it is in Chinese as well after launching it when booted the boot.img file therefor I guess it it fetching the language setting from the booted IMG or WinPE already.
Click to expand...
Click to collapse
If you downloaded the windows that I uploaded, it is the Chinese version, you can go to uupdump to download the corresponding version of windows. Note that it is arm64

hehedi233 said:
If you downloaded the windows that I uploaded, it is the Chinese version, you can go to uupdump to download the corresponding version of windows. Note that it is arm64
Click to expand...
Click to collapse
Yes that I already did. Its more the WinPE which is in Chinese causing that Dism++ is launching in Chinese as well.
So I assume when I push the English WinPE files/Version to my phone I will have everything in english then and Dism++ will launch in English as well.
Can you provide WinPE in english?

Wishmasterflo said:
Yes that I already did. Its more the WinPE which is in Chinese causing that Dism++ is launching in Chinese as well.
So I assume when I push the English WinPE files/Version to my phone I will have everything in english then and Dism++ will launch in English as well.
Can you provide WinPE in english?
Click to expand...
Click to collapse
winpe-EN.7z
drive.google.com

I laughed when I saw the BSOD
---
当我看到死亡的蓝屏时，我笑了。