Database Users

[ROOT] Howto root easily your Gen8 device [fw 2.0.71 - 2.4.83] + R/W FILESYSTEM

Hello community
First of all, thanks to dogmaphobia for his initial work (click for fw 2.0.71)
Don't forget: I'm not responsible for anything
Installing SDE or rooting your Archos device in any way may or definitly will void your warranty. You can find more information about it on the Archos website: link
Now here we go, you need four things:
An Archos Gen8 device (e.g. A101IT)
Archos Firmware
- 2.1.02: [Archos server]
- 2.1.03: [Archos server, Mirror #1]
- 2.1.04: [Archos server, Mirror #1]
- 2.1.08: [Archos server]
- 2.3.20: [Archos server]
- 2.3.26: [Archos server]
- 2.3.81: [Archos server]
- 2.4.19: [Archos server]
- 2.4.65: [Archos server]
- 2.4.80: [Archos server]
- 2.4.81: [Archos server]
- 2.4.82: [Archos server]
- 2.4.83: [Archos server]
Archos SDE
- [Archos server], [Mirror #1]
Rooted initramfs + kernel
- [fw 2.0.71 +rw]
- [fw 2.1.02]
- [fw 2.1.02 +rw]
- [fw 2.1.03]
- [fw 2.1.03 +rw]
- [fw 2.1.04]
- [fw 2.1.04 +rw]
- [fw 2.1.08]
- [fw 2.1.08 +rw]
- [fw 2.3.20]
- [fw 2.3.20 +rw]
- [fw 2.3.26]
- [fw 2.3.26 +rw]
- [fw 2.3.81]
- [fw 2.3.81 +rw]
- [fw 2.4.19]
- [fw 2.4.19 +rw]
- [fw 2.4.65]
- [fw 2.4.65 +rw]
- [fw 2.4.80]
- [fw 2.4.80 +rw]
- [fw 2.4.81]
- [fw 2.4.81 +rw]
- [fw 2.4.82]
- [fw 2.4.82 +rw]
- [fw 2.4.83]
- [fw 2.4.83 +rw]
*: +rw = permanent root, changes to filesystem will be stored in /dev/mmcblk0p2. it has ~30 megabytes free, this should be sufficient for most changes and scripts.
BE CAREFULLY: if you delete or corrupt important system files and aren't able to boot anymore, you have to flash the "non-rw" root kernel+initramfs, go to /mnt/system/unionfs and remove the changes.
Then you have to the following:
Install SDE (you only have to do this only once, it will even survive a full reformat)
reboot Archos device and hold down "Vol-" button after screen went black
choose "Update Firmware"
connect your Archos device by USB to your computer
upload the SDE firmware file to your device
safely disconnect the USB connection
press ok on Archos device
reboot
Install android firmware
reboot Archos device and hold down "Vol-" button after screen went black
choose "Update Firmware"
connect your Archos device by usb to your computer
upload the Android firmware file to your device
safely disconnect the USB connection
press ok on Archos device
reboot
Install the custom kernel + initramfs
reboot Archos device and hold down "Vol-" button after screen went black
Go to "Recovery Menu" and then "Developer Edition Menu"
choose "Flash Kernel and Initramfs"
connect your Archos device by USB to your computer
upload zImage and initramfs.cpio.gz to your device
safely disconnect the USB connection
press ok on Archos device
reboot and hold down "Vol-" button after screen went black
choose "Developer Edition"
now you have temporary root (you always have to boot "Developer Edition" to get root again)
(optional!) permanent root
thus it will boot always the custom kernel (to revert, reinstall Android firmware)
reboot Archos device and hold down "Vol-" button after screen went black
Go to "Recovery Menu" and then "Developer Edition Menu"
choose "Remove Android Kernel"
reboot
For Updates:
Just go like this:
chulri said:
@Techngro
I was in the same situation as you are: 2.1.03 and permanent root.
Then did a firmware upgrade from the rescue menu, flashed the new kernel and initramfs and removed again the stock android kernel --> working
If it says "update failed" the aos file might be corrupt
Click to expand...
Click to collapse
Have fun!
Big thanks to jfmcbrayer for helping me out!
Links for developers:
[DEV] Thread
Project site at code.google.com

Quick Question: If I remove Android's kernel would I also get rid of the firmware?
TIA!

chemical1der said:
Quick Question: If I remove Android's kernel would I also get rid of the firmware?
Click to expand...
Click to collapse
No, of course it does not. Because if it would, what should the device boot then?

that's what i thought. my Archos gave me a rather ominous warning about removing the kernel. i'm used to flashing kernels on my DINC but am brand new to doing so on my Archos. thanks for the quick response and the root solution!

Update and temp-root worked on Archos 32
chulri said:
...
You need four things:
An Archos Gen8 device (e.g. A101IT)
Firmware 2.1.02
Archos SDE
My custom initramfs + kernel
Click to expand...
Click to collapse
* Sorry - can't post links - me = newbie here - lol
Many thanks for the links and the how to...
My first android device, first time flash/upgrade (2 weeks old). Took a guess that when uploading the files, they just go onto the root, it wasn't mentioned anywhere. Figured if it was the wrong location, nothing would be damaged.
Worked like a charm, even though I messed up the order due to file naming issues, downloaded in the order listed above, so file and file(2) were in the wrong order . Both the firmware and SDE have the same filename, and I mixed them up on upload the first time due to listed and downloaded order above, but it just updated the firmware to 2.1.2, saved all my applications and settings. I then went back, put on the SDE, missed the reboot Vol- and it loaded the alt-OS Armstrong or something , rebooted and did the firmware again just to be funny, then the temp-root, and it all work really well.
I luckily didn't brick it, although it took a super long time at the archos boot screen after the first push of firmware 2.1.2, seemed hung, so I restarted it, and it booted, checked and was upgraded. Not sure if I farked the process by restarting it while in that Archos boot screen or not, not sure if it was actually doing anything after 10 minutes, so took the chance. The firmware update progress bar goes quick, just took ages on that reboot. I hope it wasn't trying to convert the fs or something.
My quadrant score is still the same, between 1328 - 1447 depending on junk running in background when testing.
Market and Youtube
I had installed the market using that gApps4Archos2.apk when on 2.0.71 then killing the youtube.apk and downloading it from the market. Didn't have to do anything after the 2.1.2 firmware update this time since everything was in place. Tested youtube and it works.
SMB
Also tested the SMB issues that I and others were having, and they are not resolved. I can pull media from a Vista and XP accessing shares via SMB, but after playing a couple videos, it give either media server error, or file incomplete or damaged error. If I clear the media library and reboot, I can play those same files again until something is overloaded. Long files names, paths, or mixed, nested both seem to quicken the need for a reboot in my case. I have not tested on my debian box to see if it is a windows (mainly Vista) thing or not. I have noted that once I get these media server errors, even locally stored video give the error until rebooted. FWIW.
Mount
/dev/block/mmcblk0p1 on /mnt/rawfs type rawfs (rw)
/dev/block/mmcblk0p2 on /mnt/system type ext3 (rw,nosuid,noexec,noatime,errors=continue,data=ordered)
/dev/block/mmcblk0p4 on /data type ext3 (rw,nosuid,noatime,errors=continue,data=ordered)
At least the battery now can reach 100% and show "charged" instead of only reaching 99%. That is a plus.
Thanks again, I am just coming up to speed on this device and look forward to hacking it. I wonder if I can safely disassemble and upgrade the storage to a high speed mmc.
dmesg: mmc0: card is mmc v4 but doesn't support any high-speed modes.
this is going to be fun....
Keep up the great work...

To do this, do you each step right after the other? I was going to allow my 101 to boot into the newly installed 2.1.02 after a full system wipe but i'm getting a bootloop when trying to start.
EDIT: Followed from the beginning again (already had the SDE firmware installed), & still ends in bootloops =\ Guess i'm trying a few more times but i was wondering if anyone else had success?

Veritas06 said:
To do this, do you each step right after the other? I was going to allow my 101 to boot into the newly installed 2.1.02 after a full system wipe but i'm getting a bootloop when trying to start.
EDIT: Followed from the beginning again (already had the SDE firmware installed), & still ends in bootloops =\ Guess i'm trying a few more times but i was wondering if anyone else had success?
Click to expand...
Click to collapse
This has nothing to do with rooting.. it is a problem many are having, including myself with the new firmware. It might be because the kernel is a little bigger and it won't fit in some boot partitions that may have bad blocks. I've contacted Archos support so they know of the problem and hopefully they'll get a fix out soon.

good job!
But Rotating the device took about 10 seconds for the home screen to update all the icons. Any way to imporve the speed?
Thanks much for help!
chulri said:
Hello community
First of all, thanks to dogmaphobia for his initial work (click)
Don't forget: I'm not responsible for anything
Now here we go:
You need four things:
An Archos Gen8 device (e.g. A101IT)
Firmware 2.1.02 ([Archos server], [Mirror #1])
Archos SDE ([Archos server], [Mirror #1])
My custom initramfs + kernel ([archos-gen8-dvb project], [Mirror #1])
Then you have to the following:
Install SDE (you only have to do this only once, it will even survive a full reformat)
reboot Archos device and hold down "Vol-" button after screen went black
choose "Update Firmware"
connect your Archos device by USB to your computer
upload the SDE firmware file to your device
safely disconnect the USB connection
press ok on Archos device
reboot
Install android firmware 2.1.02
reboot Archos device and hold down "Vol-" button after screen went black
choose "Update Firmware"
connect your Archos device by usb to your computer
upload the Android firmware file to your device
safely disconnect the USB connection
press ok on Archos device
reboot
Install the custom kernel + initramfs
reboot Archos device and hold down "Vol-" button after screen went black
Go to "Recovery Menu" and then "Developer Edition Menu"
choose "Flash Kernel and Initramfs"
connect your Archos device by USB to your computer
upload zImage and initramfs.cpio.gz to your device
safely disconnect the USB connection
press ok on Archos device
reboot and hold down "Vol-" button after screen went black
choose "Developer Edition"
now you have temporary root (you always have to boot "Developer Edition" to get root again)
(optional!) permanent root
thus it will boot always the custom kernel (to revert, reinstall Android firmware)
reboot Archos device and hold down "Vol-" button after screen went black
Go to "Recovery Menu" and then "Developer Edition Menu"
choose "Remove Android Kernel"
reboot
Have fun!
Click to expand...
Click to collapse

Tesla74 said:
This has nothing to do with rooting.. it is a problem many are having, including myself with the new firmware. It might be because the kernel is a little bigger and it won't fit in some boot partitions that may have bad blocks. I've contacted Archos support so they know of the problem and hopefully they'll get a fix out soon.
Click to expand...
Click to collapse
Thanks for the heads up. I have an EVO so i've seen users with bad blocks but assumed this was after flashing a few dozen times, guess i was wrong =\. Hopefully we'll see a modified update soon.
Thanks again!

sorry for the noobish question...
does this method gain full root access to the system partition, so that adfree, rootexplorer, ... will work correctly?

yes you get root access and yes you can modify the system files, but after a reboot, everything is reverted

thx for the quick reply
but if i use step 4 of your howto:
(optional!) permanent root
thus it will boot always the custom kernel (to revert, reinstall Android firmware)
* reboot Archos device and hold down "Vol-" button after screen went black
* Go to "Recovery Menu" and then "Developer Edition Menu"
* choose "Remove Android Kernel"
* reboot
Click to expand...
Click to collapse
then should be everthing fine...

changes to system directories / files aren't saved on disk (tmpfs) so after a reboot all changes are reverted, even if you boot again into root.

ok.
is there allready a way, or will there be a way someday with full access without tmpfs?

either you go with the very custom UrukDroid or wait some time until myself or someone else starts investigating into this (my approach would be, using stock archos firmware and add simple but persistent r/w acces, no less no more)

chulri said:
either you go with the very custom UrukDroid or wait some time until myself or someone else starts investigating into this (my approach would be, using stock archos firmware and add simple but persistent r/w acces, no less no more)
Click to expand...
Click to collapse
Slightly OT but am currently using UrukDroid and am pretty happy with it. However, it is always good to see different people's ways of implementing things, so if you do decide to look into rooting your way, I'd certainly be up for giving it a try!

+1
I'm always up for testing. Let me know!

Anyone tried with the 250GB A70?
I will do tonight, but away from my charger to connect for the initial upgrade.

UPDATE
Now compatible with 2.1.03

thank you very much for this!
works perfectly on my 101

[Q] Accidentally bought a demo unit, any way to fix it?

I bought the NST online from a forum and the punk sent me a demo unit. It just scrolls through the various promotional screens. I've tried doing the software update and factory reset but neither of them work. Is there any way I can "unlock" everything?

couchlife said:
I bought the NST online from a forum and the punk sent me a demo unit. It just scrolls through the various promotional screens. I've tried doing the software update and factory reset but neither of them work. Is there any way I can "unlock" everything?
Click to expand...
Click to collapse
Try this:
1. turn it off completely
2. press at the same time the power button (back side) and the two lower side buttons (bottom left and bottom right page)
3. it should start the recovery and restore your device to stock
Link: http://forum.xda-developers.com/showthread.php?t=1137967
Let us know if it works.

hi,
now i don't have the Nook available (i'm at office), but yesterday i was playing with ADB and having a look at nook system folders; i remember seeing a property file in which there is a property like demoMode=enable/disable or something like that (i'm not sure, but if i remember well this file should be in the same folder where also other device specific properties like serial number, mac address, etc.. are stored).
Until reading your message i didn't even know such a mode existed. But now i think that maybe it could be possible to edit that file and enable the "regular" mode on your Nook.
Of course, even if that is possible, you would need to get root and ADB access to to that, and there is the risk of bricking the unit (even though if you can create a backup image to be on the safe side).
When i'll be back home, i will try to find further info about the above mentioned file.
Regards

hi,
i don't know if you already solved, in any case i had a better look at the system folders of Nook, and it seems to me that the Demo Mode is managed by a dedicated application (/system/app/DemoMode.apk). Baksmaling the source code of this app, it seems that it is activated on any Nook unit after boot, but in case the value of setting "demo_mode" is not set to "on", it just exits without doing anything; on contrary, the demo mode is activated (i.e. the continuous loop through a set of images).
So, to get rid of demo mode is activated, you could launch a script to change the relevant value of the setting "demo_mode", to set it to "off"; and then reboot the Nook:
Code:
echo *************************
echo * Setting Demo-Mode off *
echo *************************
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db "update secure set value='off' where name='demo_mode';"
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
del settings.db
Of course, to be able to launch it, you need to have your Nook already rooted, so that ADB is enabled.
The script is inspired from similar scripts present in the batch file "xe-autoroot.bat" from user xboxexpert of this forum. Therefore, in case you still don't have rooted your Nook, i suggest you to use its script to get it (link to the thread). In this case, you can easily launch the script to disable demo mode from the same folder where you have xe-autoroot.bat, since yu already have all the needed software (sqlite3).
Another possible solution could be just to remove DemoMode.apk from /system/app folder (but i'm not 100% sure this would have side effect).
In any case, not having a demo mode Nook unit, i cannot be sure these methods would work.
Hope this help

That doesn't work
When I have tried to root it I can't because I can not get to the menu to setup the wifi it won't let me get away from the screen saver my mom ordered one of these off ebay for like $40

Figured it out
If it is on an older version you can just drop the official firmware on your nook let it update and it worked like a charm
https://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175/

how to disable DEMO mode on Nook simple touch
couchlife said:
I bought the NST online from a forum and the punk sent me a demo unit. It just scrolls through the various promotional screens. I've tried doing the software update and factory reset but neither of them work. Is there any way I can "unlock" everything?
Click to expand...
Click to collapse
a lot of time passed since other guys had a problem of demo mode on nook. i got my nook (simple touch) as secondhand, unfortunately locked to demo mode.
below is step-by-step how to switch it back to 'normal' mode >>>>>>
--- turn your Nook ON
--- go to Settings - Screen - on Screen window press-and-hold top-right button AND same time keep tapping the "Screen" caption (on a top of display)
--- Demo Mode will pop up on your display
--- undo 'Toggle the demo mode'
--- now to activate "normal" mode switch off-and-on your Nook !
that's It :good:

[FIX] SOUND ISSUE in NexusHD2-ICS-4.0.3-CM9 V1.4

Hello dears. Finlay i succeed famous [SOUND & AUDIO ISSUE in NexusHD2-ICS-4.0.3-CM9 V1.4] after very hard work and search, But very lucky & with a yummy test...
[Question] = After i enter to [NexusHD2-ICS-4.0.3-CM9 V1.4] every sounds & alarms include Vol+ & Vol- are deactivate?
[Question] = Why in [NexusHD2-ICS-4.0.3-CM9 V1.4] any Sounds are Silent even Calls whereas Volumes show it must been OK?
[Answer] = Just be careful when you want to switch from WM to Android you must be run [CLRCAD.exe] before [HARET.exe] Just this! And if you want to be sure you can run [CLRCAD.exe] 2 time and then [HARET.exe]
This problem being from some user mistake etc:
- You think this is not many important!
- You forget to run this!
- or like as me you created a short script with MortScript or create a shortcut from this files to your WM home screen to run Android easy and thats not work true.
Anyway my problem resolving whit this. Please test & if answered please recommend this thread to Developer Forum.

HistoryPassage said:
Hello dears. Finlay i succeed famous [SOUND & AUDIO ISSUE in NexusHD2-ICS-4.0.3-CM9 V1.4] after very hard work and search, But very lucky & with a yummy test...
[Question] = After i enter to [NexusHD2-ICS-4.0.3-CM9 V1.4] every sounds & alarms include Vol+ & Vol- are deactivate?
[Question] = Why in [NexusHD2-ICS-4.0.3-CM9 V1.4] any Sounds are Silent even Calls whereas Volumes show it must been OK?
[Answer] = Just be careful when you want to switch from WM to Android you must be run [CLRCAD.exe] before [HARET.exe] Just this! And if you want to be sure you can run [CLRCAD.exe] 2 time and then [HARET.exe]
This problem being from some user mistake etc:
- You think this is not many important!
- You forget to run this!
- or like as me you created a short script with MortScript or create a shortcut from this files to your WM home screen to run Android easy and thats not work true.
Anyway my problem resolving whit this. Please test & if answered please recommend this thread to Developer Forum.
Click to expand...
Click to collapse
Thanks for the post... but I don't think this would be the problem... HaRet won't load if you don't run CLRCAD.exe before HaRet. if you don't then it will give you an error.
I always double tap CLRCAD.exe (as you have mentioned above ) just to make sure since tapping this app don't show/run any GUI/App/Program.

[WIP] Open Bootloader Development for Archos Gen8

Hey geeks,
you might know my hardware hacking thread already:
http://forum.xda-developers.com/showthread.php?t=1199450
Some time ago i started thinking about starting with an open bootloader for Archos Gen8.
So i started from scratch and made use of external boot mode to completely start from external MicroSD and leave the internal memory alone.
Remark: This is a geek project, there's no GUI or something. So don't expect anything useful right now.
At the moment you'll need some hardware hacking, because you'll need a serial console over uart3.
Unfortunately you'll also need a dirty hack to power up the MicroSD permanently.
Don't hesitate to ask for details about it.
So this is for the weird ones out there...
Right now there's work in progress, because stock kernel stucks at some point in the boot process.
Maybe there's some setup missing in the bootcode (it's very basic at the moment) or stock kernel relies heavily on avboot at some point.
I will work on this issue whenever i'll find some time.
Anyway it might be still an interesting project for at least a very few of you, so here's the source code:
- x-loader-archos
- u-boot-2011.09-archos
As pointed out the Archos implementation is very basic at the moment, but the code itself works very well and had been tested on A101IT Gen8.
To further devices, e.g. A70S Gen8, the machine id had to be included in the board file, the rest of the setup in early stage should be very similar.
The code bases:
- x-loader (https://gitorious.org/x-loader/x-loader)
- u-boot (taken from this archive: http://www.technexion.com/images/downloads/ARM_CPU_Modules/TDM-3730/linux-2.6.32-tdm3730.tar.xz)
I'd like to switch to official u-boot release 2011.09 as a base soon.
To start playing with it:
- open your case and start hacking, to get serial console working
- tweak the hardware to power the MicroSD slot permanently
- create a bootable MicroSD for OMAP systems
- place the binaries on your card
- insert the card and use vitalifs kernel module to reboot your device in external bootmode
Please refer to these posts from vitalif (thanks a lot for contributing!!!):
http://forum.xda-developers.com/showpost.php?p=22719203&postcount=105
http://forum.xda-developers.com/showpost.php?p=22765441&postcount=108
You might start digging in the source code and create your own loader:
- use a linux machine with a recent distribution
- setup a cross environment with ARM cross compiler suitable for ARMV7
- extract the sources to directory of your choice
- to compile x-load:
Code:
cd ./x-loader-archos
make archos_config
make
- to compile u-boot-2011.09-archos:
Code:
cd ./u-boot-2011.09-archos
make a101it_config
make
It might be required to tweak the top-level Makefiles to point at your toolchain.
I used my ready to work toolchain (for 32-bit linux only) here:
http://forum.xda-developers.com/showthread.php?t=1328027
Unfortunately i haven't found some time to create a project page at gitorious,
but hopefully i'll manage to do so in the next weeks...
I know this is a very very special project, but anyway if there's some interest, this might lead to something useful in the end.
If the bootcode is working very nice some day, it might also be possible to replace stock loader, but that's fiction yet.
You might ask what for...
I say... it's just for fun!
cheers,
scholbert

Boot console output... so far
Hey,
it had been posted already but her again for completeness...
The console log on UART3 starting custom kernel configured with stock config:
Code:
Texas Instruments X-Loader 1.5.1 (Mar 26 2012 - 20:41:11)
Found 0256 MB
Archos Gen8
Reading boot sector
Loading u-boot.bin from mmc
Done!
U-Boot 2011.09 (Mar 23 2012 - 18:53:39)
OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
Archos 101IT Gen8 + LPDDR/MMC
I2C: ready
DRAM: 256 MiB
MMC: OMAP SD/MMC: 0
Using default environment
In: serial
Out: serial
Err: serial
Die ID #144800029ff800000160a4bb18027009
Hit any key to stop autoboot: 0
reading boot.scr
** Unable to read "boot.scr" from mmc 0:1 **
reading uImage
2987000 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-2.6.29-omap1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2986936 Bytes = 2.8 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux.............................................................
................................................................................
..................................................... done, booting the kernel.
<6>Initializing cgroup subsys cpu
<5>Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.1 (GCC) ) #1
PREEMPT Thu Mar 22 23:59:34 CET 2012
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Archos A101IT board
fixup_archos: [console=ttyS2,115200n8 androidboot.console=ttyGS0 init=/linuxrc d
ebug omapdss.debug=0 vram=4915200 omapfb.vram=0:4915200 omapfb.debug=0 mmc_block
.split=0.0001:512M]
Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 65536
<7>free_area_init_node: node 0, pgdat c05fd368, node_mem_map c06a5000
<7> Normal zone: 512 pages used for memmap
<7> Normal zone: 0 pages reserved
<7> Normal zone: 65024 pages, LIFO batch:15
<4>L2 CACHE is enabled in bootloader
<6>OMAP3630 ES1.2
<6>DIE ID: 144800029FF800000160A4BB18027009
<6>FEATURE_STATUS: 00000c00
<6>SRAM: Mapped pa 0x40200000 to va 0xfc800000 size: 0x100000
<6>Reserving 4915200 bytes SDRAM for VRAM
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
<5>Kernel command line: console=ttyS2,115200n8 androidboot.console=ttyGS0 init=/
linuxrc debug omapdss.debug=0 vram=4915200 omapfb.vram=0:4915200 omapfb.debug=0
mmc_block.split=0.0001:512M
<3>Unknown boot option `androidboot.console=ttyGS0': ignoring
<3>Unknown boot option `omapdss.debug=0': ignoring
<6>Clocking rate (Crystal/DPLL/ARM core): 26.0/332/600 MHz
BTW, i extracted the function from Archos loader setup up PLL and MPU stuff.
Need some time to extract the stock setup for PLL at early stage.
Maybe this will give some answers.
One of my next plans is, to build some kind of bare bone kernel (console only), which may be used for recovery and debug purpose.
Maybe this gives it a kick and things start up to a login shell
TBC
Have fun!
scholbert

One of my next plans is, to build some kind of bare bone kernel (console only), which may be used for recovery and debug purpose.
Maybe this gives it a kick and things start up to a login shell.
Click to expand...
Click to collapse
Seems like an internal monologue... but i like to point out that i stopped this project for a while.
So don't expect anything like a brick recovery tool or similar.
If others will join in it might be possible that it would led to something,
but as long as no one even starts hacking the hardware this is just for me...
Happy days!
scholbert

scholbert said:
Seems like an internal monologue... but i like to point out that i stopped this project for a while.
So don't expect anything like a brick recovery tool or similar.
If others will join in it might be possible that it would led to something,
but as long as no one even starts hacking the hardware this is just for me...
Happy days!
scholbert
Click to expand...
Click to collapse
Shame you stopped your efforts for now, I always followed your posts with much interest. However I can understand it is frustrating being on your own.
Thanks for what you did this far and for posting your info .
divx118

Sorry to read that, this was a very very interesting reading.
But I don't have the knowledge to make the necessary hardware hack, and above all, my wife would kill me if she saw me opening the tab
Thanks again for all that amazing information scholbert

Hey,
first off all thanks for your interest and your replies
Some words on your comments though...
divx118 said:
Shame you stopped your efforts for now, I always followed your posts with much interest. However I can understand it is frustrating being on your own.
Click to expand...
Click to collapse
I did not want to sound frustrated, because i'm not.
All i do with the device and all that hacking stuff is fun and mostly for educational purpose
Maybe i'll continue working with this stuff, but for now i wanted to point out to not expect too much.
Some guys out there, bricked their devices and were looking for a solution.
That's why i wrote it down.
Basically it should be possible to recover bricks by using external boot procedure, but it's still far from a simple solution.
grim-a101 said:
Sorry to read that, this was a very very interesting reading.
But I don't have the knowledge to make the necessary hardware hack, and above all, my wife would kill me if she saw me opening the tab
Click to expand...
Click to collapse
Yeah that's a good point, the barrier for this kind of hacking is little high.
Unfortunately you'll have to tweak the hardware, to gain access to the serial debugging port and cheat the power management of the MicroSD slot.
Most of you simply want to use the device and do some less harder tweaks at system level.
Anyway, there are some other possibilities as well (e.g. using USB and TI Flash) to access the platform. Maybe i'll do some research here as well.
Thanks again for appreciation!!!
Regards,
scholbert

[Q] Disable Touch To Wake

Is there a way to disable touch to wake on my LG G Watch R?
I like to cross my arms and when wearing a t-shirt it constantly wakes the screen.
I want to avoid Theatre Mode as I want to be able to glance at the screen and see the time.
Any suggestion will be greatly appreciated.
Thanks in advance

mark3180 said:
Is there a way to disable touch to wake on my LG G Watch R?
I like to cross my arms and when wearing a t-shirt it constantly wakes the screen.
I want to avoid Theatre Mode as I want to be able to glance at the screen and see the time.
Any suggestion will be greatly appreciated.
Thanks in advance
Click to expand...
Click to collapse
+1 intrested to this. I have a lg g watch r.
In Cinema Mode i have Touch2Wake disabled but watch dont show anything and does not vibrate. It becomes really useless if it does not vibrate In Cinema Mode.

mark3180 said:
Is there a way to disable touch to wake on my LG G Watch R?
I like to cross my arms and when wearing a t-shirt it constantly wakes the screen.
I want to avoid Theatre Mode as I want to be able to glance at the screen and see the time.
Any suggestion will be greatly appreciated.
Thanks in advance
Click to expand...
Click to collapse
I am also searching for this:good:

I've been looking everywhere for a solution to this. I hasn't even considered it as an issue, but just a couple of days is enough to make me realise this is a requirement. I can't believe it didn't come up in development! Aside from your own accidental touches, there's also the issue of inquisitive fingers from children touching that nice shiny screen... Tapping the side button to wake the screen would be perfect (whilst retaining the monochrome screen and notifications).

Cinema mode is really dumb. Just very poorly thought out. There has got to be a way to disable touch to wake. Or even enable vibrating notifications in cinema mode.

Yes there is a way
First you have to install twrp on your watch. Because you need the acces to some files. When you have installed, start in recovery mode, and go to mount and press system. Connect your watch to your computer and open adb,
adb root
adb push /system/usr/idc/sec_touchscreen.idc <choose where you want to have the file in your pc>
Click to expand...
Click to collapse
Make a copy of the file, and open it with notepad++ or other file editor. YOU will se a think like this
# Copyright 2014 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# Input Device Calibration File for the Dory touch screen.
#
device.internal = 1
touch.deviceType = touchScreen
touch.orientationAware = 1
touch.wake = 1
Click to expand...
Click to collapse
So remove the part of ( touch.wake = 1 ) and save (make first a copy of the file), Go to adb
adb pull <where you have the file> /system/usr/idc/
Click to expand...
Click to collapse
Restat the watch and you will se that the screen is not goin to turn off, pressing the button of your watch. Restart other time the watch and go to recovery.
With the copy of the file, mount other time system on twrp and go to adb
adb pull <where you have the copy> /system/usr/idc/
Click to expand...
Click to collapse
Restart the watch other time. This work for my, but i am using an alpha for gear 2 neo with android, so probably this might be a bug.

dataonlycod said:
First you have to install twrp on your watch. Because you need the acces to some files. When you have installed, start in recovery mode, and go to mount and press system. Connect your watch to your computer and open adb,
Make a copy of the file, and open it with notepad++ or other file editor. YOU will se a think like this
So remove the part of ( touch.wake = 1 ) and save (make first a copy of the file), Go to adb
Restat the watch and you will se that the screen is not goin to turn off, pressing the button of your watch. Restart other time the watch and go to recovery.
With the copy of the file, mount other time system on twrp and go to adb
Restart the watch other time. This work for my, but i am using an alpha for gear 2 neo with android, so probably this might be a bug.
Click to expand...
Click to collapse
After you restart the second time you can use the button to wake and not the touch screen?? I will try this then thank you.

-RioT- said:
After you restart the second time you can use the button to wake and not the touch screen?? I will try this then thank you.
Click to expand...
Click to collapse
Yep you can use it to wake up the device. But as I say, make a backup because this happen with my alpha of the gear 2 neo, so probably this is not going to work with other devices. Just in case xD

Works for me on LG G Watch R
The file name is different "synaptics_rmi4_i2c.idc"
Same edit, copied to sdcard and moved in recovery to /system/usr/idc/ as mentioned above.
I have swipe menu still available and I can swipe down for the quick toggles.
Button is used to wake (and I use screen always on)
Going to be interesting how this performs in the shower and in general. Thanks to the suggestion posted.

Any update on this after using it for a while? Looking to apply this to my LG G watch R running the Urbane port.

Ok well i tried it any ways and i still have the problem when my arms are crossed my arm starts doing things on my watch...

Starting from version 1.6 this app supports wake on touch changing - https://play.google.com/store/apps/details?id=com.sssemil.advancedsettings (here is apk - View attachment AdvancedSettings-v1.6-11.apk)

I downloaded the advanced settings app tried the disable touch wake... it doesn't wake but you can still scroll notifications and long press to change the face.
Any chance of completely turning off the touch screen while in sleep...

..

castructuraleng said:
I tried the Advanced Settings app on my LG Watch Urbane 2nd Edition with Android 6.0.1, which is not rooted. It has an option for "Touch to wake screen" that I tried to set to "off"; however, when I go back to look at it, it is always set to "on". Do I need to root to have this stay, or is the app just not compatible with 6.0.1?
Update... just answered my own question. It appears you need to be rooted to do this.
Click to expand...
Click to collapse
Yep, it works on Marshmallow 6.0.1 when Rooted. Just tested it on my Huawei Watch.

..

I installed "Showear". You can set a simple touch pattern to unlock the watch. Crossing your arms will no longer trigger any action on your watch (except making the screen on).

..

..

Hi m8. I've done this on my LG urbane and works just fine ty a lot... but i modified a little your steps...
1) My lg urbane is rooted
2) I went to the ADB folder in my PC (using windows explorer) then using shift+right click i select "open command window here"
3) in this command window i did:
adb reboot bootloader
fastboot flash recovery (starts twrp)
in the TWRP:
Go to "Mount"
tick the "system" box
In the command window :
adb pull /system/usr/idc/synaptics_rmi4_i2c.idc (Dont need to select the folder, will appear in the ADB folder used to open the command window)***
*** When i tried to write the destination folder have not worked so i strongly advise not to fill this part, the command in the beginning is PULL not PUSH to take from the device and the file to be taken from the device had a different name as someone have stated before ***
4) In the notepad i did
I opened the file with the notepad and edit "touch.wake = 1" to "touch.wake = 0" (I did not delete this part just change the value)
5) in the command window:
adb pull <where you have the file> /system/usr/idc/
6) Reset my phone and works great!