Database Develop

Dial and Home Keys not working. ADVICE PLZ!

Before I get hounded about not reading though the forums, I haven't had any luck finding my exact problem. If you just want to post links for me that'd be awesome too!
I bought a rooted phone off ebay for cheap. In the listing it said that the 'home and back' keys didn't work after user rooted the device. When I got it I went through the steps to root it and put a new rom on it. I tried to put several roms on it. Some failed, others didn't boot, so it's back to default (maybe). Now how did I do that if my home key wasn't working? I found out that the home and back key did work if you hit it enough. Currently the back button works. Dial and home are a no go.
I tried to follow steps on how to get Cyan to work, I didn't have any luck except to update the radio. No I haven't installed any custom SPL.
After doing all this, I tried to put a JF image on it, also a ZXDonut. I wiped and put ZXDonut (I think) NOW I have the problem of the Dial (green) and Home keys not work at all. I haven't been able to get into recovery mode at all.
Is there a quick fix for this? Should I just download the DREAIMG.nbh and boot with camera button? Then start over? Try to un-root it, and start from scratch?
I'm not sure what the best move is here, I also tried to reboot into recovery with the terminal but I kept getting permission errors.

I don't know if I can help with your issue, but....
Type this in terminal to get into recovery:
su
reboot recovery
The su should take away those nasty permissions errors. However, in most recoveries, you need to be able to use your home key. :/

My G1 has done this a few times with Cyanogenmod. I would just boot into recovery (home would work for that when powered off and not when the phone was on). I would then do a full wipe then reboot. Fixed the problem everytime.

Got into recovery with su † reboot recovery but still can't do anything without the home key. Any other way of doing this?

For some reason I could get the home button to work when I blew cold air into it. Factory Reset, New rom. Works again...
Found a way to do it without factory reset.
For the benefit of anyone else with this problem, here are the full details of how to fix it without a factory reset:
1. Install AnyCut from Android Market
2. Go to the home screen
3. Long press on the wallpaper
4. Tap "Shortcut"
5. Tap "Any Cut"
6. Tap "Activity"
7. Choose "Setup Wizard" from the list of activities
8. Tap "OK"
9. There should now be a Setup Wizard icon on your home screen. Follow the wizard through to completion and the dial / home / hangup hardware keys should now be behaving normally again.
-Random Website

I had this problem when flashing the default htc build before updating to SuperD
what fixed it was wiping, using the old (not de-appified) SuperD, then flashing the new one. It causes your talk, home keys to not work, and when you hold down the power it only gives you a few options instead of the normal 4 or so it gives you normally. Also, it makes your settings refuse to save.
Try holding home when you turn the phone on, and wiping and reflashing the newest Cyanogen or something. Read the instructions on how to do that at www.cyanogenmod.com

I've had this problem several times in the past. Previously the workaround using Anycut would fix the problem. However, after having flashed to CM's 5.07 (Eclair) mod I found that the Setup Wizard didn't function the same any longer (now that you can add multiple gmail accounts) and the fix didn't work this time.
This did, though:
1. Using SUFBS or some other file manager with superuser rights, browse to data/data/com.android.providers.settings/databases, copy the settings.db file found there to /sdcard.
2. Download SQLite Database Browser from sourceforge.net/projects/sqlitebrowser and install.
3. Connect phone to PC, mount sdcard so you can read it from PC (I use "SD Split" so I can read card from PC and phone at the same time, personally).
4. Open SQLite Database Browser, File>Open Database, browse to settings.db file you copied to /sdcard and select it. Click 2nd tab, 'Browse Data'. From 'Table' dropdown menu select 'secure'. Click 'new record'. A new line will be created at the bottom of the table. Double click in the 'name' column of that new line, a box will pop up that says 'edit cell'. Type 'device_provisioned' (without the quotation marks) and click 'apply changes'. Then double click in the 'value' column, enter '1' (no quotes) and click 'apply changes'. File>Save Database.
5. Using SUFBS again, select menu>mount data as RW. Browse to /sdcard and copy the settings.db file you just modified (via longclick>copy), then browse to data/data/com.android.providers.settings, longclick on /databases and choose 'paste', thereby overwriting the settings.db file that's in /databases with the one that you modified using the SQLite Database Browser.
6. Reboot. All should be working now.

well what you have to do is..
[Download]
1. Defanged 83 - http://dx.infernix.n...se_defanged.zip
2. Cyanogen Rom 4.2.15.1 - http://n0rp.chemlab....15.1-signed.zip
[Put them into the root of your SDcard]
1. Turn off Phone
2. Start phone into recovery (Home+End Button)
3. Wipe /Factory Wipe
4. Flash Defanged 83 & then flash Cyanogen rom 4.2.15.1
5. Reboot (first option on the recovery)

Joshua E. said:
I've had this problem several times in the past. Previously the workaround using Anycut would fix the problem. However, after having flashed to CM's 5.07 (Eclair) mod I found that the Setup Wizard didn't function the same any longer (now that you can add multiple gmail accounts) and the fix didn't work this time.
This did, though:
1. Using SUFBS or some other file manager with superuser rights, browse to data/data/com.android.providers.settings/databases, copy the settings.db file found there to /sdcard.
2. Download SQLite Database Browser from sourceforge.net/projects/sqlitebrowser and install.
3. Connect phone to PC, mount sdcard so you can read it from PC (I use "SD Split" so I can read card from PC and phone at the same time, personally).
4. Open SQLite Database Browser, File>Open Database, browse to settings.db file you copied to /sdcard and select it. Click 2nd tab, 'Browse Data'. From 'Table' dropdown menu select 'secure'. Click 'new record'. A new line will be created at the bottom of the table. Double click in the 'name' column of that new line, a box will pop up that says 'edit cell'. Type 'device_provisioned' (without the quotation marks) and click 'apply changes'. Then double click in the 'value' column, enter '1' (no quotes) and click 'apply changes'. File>Save Database.
5. Using SUFBS again, select menu>mount data as RW. Browse to /sdcard and copy the settings.db file you just modified (via longclick>copy), then browse to data/data/com.android.providers.settings, longclick on /databases and choose 'paste', thereby overwriting the settings.db file that's in /databases with the one that you modified using the SQLite Database Browser.
6. Reboot. All should be working now.
Click to expand...
Click to collapse
I've had exactly this same problem, and this worked for me too!
Thanks man, you saved me many hours of stupid work (reflashing, wiping, installing, configuring etc.)!
My configuration: G1
ROM: [ROM][Gingerbread][GRJ22][07/18/2011]COS-DS (Android 2.3.4_r1)
Recovery: RA-dream-v1.7.0
hboot : 1.33.0013d
radio : 2.22.27.08

Joshua E. said:
I've had this problem several times in the past. Previously the workaround using Anycut would fix the problem. However, after having flashed to CM's 5.07 (Eclair) mod I found that the Setup Wizard didn't function the same any longer (now that you can add multiple gmail accounts) and the fix didn't work this time.
This did, though:
1. Using SUFBS or some other file manager with superuser rights, browse to data/data/com.android.providers.settings/databases, copy the settings.db file found there to /sdcard.
2. Download SQLite Database Browser from sourceforge.net/projects/sqlitebrowser and install.
3. Connect phone to PC, mount sdcard so you can read it from PC (I use "SD Split" so I can read card from PC and phone at the same time, personally).
4. Open SQLite Database Browser, File>Open Database, browse to settings.db file you copied to /sdcard and select it. Click 2nd tab, 'Browse Data'. From 'Table' dropdown menu select 'secure'. Click 'new record'. A new line will be created at the bottom of the table. Double click in the 'name' column of that new line, a box will pop up that says 'edit cell'. Type 'device_provisioned' (without the quotation marks) and click 'apply changes'. Then double click in the 'value' column, enter '1' (no quotes) and click 'apply changes'. File>Save Database.
5. Using SUFBS again, select menu>mount data as RW. Browse to /sdcard and copy the settings.db file you just modified (via longclick>copy), then browse to data/data/com.android.providers.settings, longclick on /databases and choose 'paste', thereby overwriting the settings.db file that's in /databases with the one that you modified using the SQLite Database Browser.
6. Reboot. All should be working now.
Click to expand...
Click to collapse
These instructions are so good it's worth requoting the whole lot!!
Thank you thank you.
FWIW, for those who don't have SUFBS, you can do the mount step from a shell, like this:
Code:
# mount
rootfs on / type rootfs (ro,noatime,nodiratime)
tmpfs on /dev type tmpfs (rw,noatime,nodiratime,mode=755)
devpts on /dev/pts type devpts (rw,noatime,nodiratime,mode=600)
proc on /proc type proc (rw,noatime,nodiratime)
sysfs on /sys type sysfs (rw,noatime,nodiratime)
none on /acct type cgroup (rw,noatime,nodiratime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,noatime,nodiratime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,noatime,nodiratime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,noatime,nodiratime,cpu)
/dev/block/mtdblock1 on /system type yaffs2 (ro,noatime,nodiratime)
/dev/block/mtdblock9 on /data type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mtdblock8 on /cache type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,noatime,nodiratime,size=0k,mode=000)
... see how for me it is on mtdblock9
2) remount it read/write:
Code:
# mount -rw -o remount /dev/block/mddblock9 /data
mount -rw -o remount /dev/block/mddblock9 /data
#
You can do this via adb shell, or in a terminal emulator.
Yay, my home button is working again!
GaJ

I am n00b and need more simple walkthrough
I don't have any bottom button usage with CM7, Zeus, or CatyRom but at least CatyRom has the ICS on-screen buttons (helps some) but I can't really navigate even if I go to the browser (can't hit home or back button).
I don't understand terminal (I saw terminal hub in CM7) but I don't believe CatyRom has a default one under applications.
Please break it down in more simple terms/directions please for the rest of us n00bs. Thanks.

I found this thread by luck in google, looking for a fix for my Motorola RAZR which suffered the following symptoms:
- Home key not working
- Search key not working
- Less options at the menu when shutting down
- Big lag
- 0 Smoothness when rotating
I followed the SQLite DB guide and now works like a charm! This problem happened me already twice and was an absolutely headache since I was going to reflash!
Thank you very much for such an useful guide!

[Q] JP6 doesn't recognise my SIM card???

I have gotten myself into a mess and having upgraded to JP6 my SIM card is no longer recognised. Has anyone else had this issue and does anyone know of a Fix that they could give me to sort this mess out.
Thanks

james.boot said:
I have gotten myself into a mess and having upgraded to JP6 my SIM card is no longer recognised. Has anyone else had this issue and does anyone know of a Fix that they could give me to sort this mess out.
Thanks
Click to expand...
Click to collapse
Don't panic, this is easy to fix..
Do a reset, cache erase from recovery mode (Volume up + Home + Turn on).
Root the device, install busybox and run it, install andoid terminal emulator the execute the followings in terminal emulator:
- su
- busybox chown 1001:1001 /efs/nv_data.bin
- reboot
That is it.

EXCELLENT!,
When you say wipe the cache is that option called "wipe cache partition" and where can I download busybox from etc? Im a bit of a noob with the fixing my screw ups business.

james.boot said:
EXCELLENT!,
When you say wipe the cache is that option called "wipe cache partition" and where can I download busybox from etc? Im a bit of a noob with the fixing my screw ups business.
Click to expand...
Click to collapse
Yes "wipe cache partition".
Root using the program from here (if not rooted yet): http://forum.xda-developers.com/showthread.php?t=803682
Busy box and emulator from the market. run busy box and click install and wait till it installs then run emulator. You must choose allow when prompted in both programs.

Hi, did all of this, it would not accept the reboot command so I turned the phone off and on. I dont know if the reboot command is integral to solving the problem but it has not worked. Is there something else I need to do?
it says
---------------------------------------------------------------------------------------------------------------------------------
change the owner and/or group or each FILE to OWNER and/or GROUP
Options:
-R Recurse
-h affect symlinks instead of symlink targets
-L Traverse all symlinks to directories
-H Traverse symlinks on command line only
-P Dont traverse symlinks (default)
-c List changed files
-v List all files
-f hide errors
------------------------------------------------------------------------------------------------------------------------------------------------
What does this mean?

I don't think that you have executed the commands right, maybe because that I should have written them more clearly.
Execute in emulator:
su
(hit Enter)
Choose "Allow" and exit the program when done.
Start Emulator again and execute:
su
(hit Enter)
busybox chown 1001:1001 /efs/nv_data.bin
(hit Enter)
reboot
(hit Enter)
The phone will reboot and it will accept the card if the nv_data.bin staill intact. Try the steps above and I hope that every thing is right.

Unfortunately it has not worked. Have you got any more ideas? I appreciate your help with this.

james.boot said:
Unfortunately it has not worked. Have you got any more ideas? I appreciate your help with this.
Click to expand...
Click to collapse
Did the commands execute right, no errors?
If so then check the IMEI number: Click on Phone in the home screen as when you dial a number and dial *#06# see the number that comes off, is it your correct IMEI number?

There is no IMEI number there, which is slightly worrying haha
no errors either

james.boot said:
There is no IMEI number there, which is slightly worrying haha
Click to expand...
Click to collapse
in this case you might need to read here: http://forum.xda-developers.com/showthread.php?t=780509
It might be that the nv_data.bin file in your mobile is damaged, I'm only saying that it might be that, the only way to know for sure is to check the IMEI number in the phone under "Settings"--> "About phone" --> "Status" if there is no IMEI number then a reflash might correct that, if the IMEI number is like 000044...etc then the nv_data.bin file is damaged and can only be corrected if you have backed up the /efs folder. Please read in the linked thread to find out before doing anything.

I had this problem. I just reset my phone. When it rebooted it installed Sim Toolkit and now it works fine & reconises the Sim. Do you have Sim Toolkit installed?

I had this exact problem spent 2 hours trying fixes etc, I had my SIM card in the wrong way around, I was so used to putting it in like my old phone i did not notice the little picture saying the way to put it haha I had taken it out to flash a new ROM and assumed it was the ROMS fault cause it stopped working

no mate it doesn't. Just done a quick factory reset without success.

[Q] has anyone rooted the official honeycomb 3.2 with SuperOneClick?

hello,
i have read on the forums about rooting the stock honeycomb through clockwork mod and fastboot and what not but i have tried everything know to man trying to get that to work, but no dice.
has anyone rooted successfully using SuperOneClick on a dell streak 7 with android 3.2 honeycomb official OTA update?
thanks for the help.

cboulais61 said:
hello,
i have read on the forums about rooting the stock honeycomb through clockwork mod and fastboot and what not but i have tried everything know to man trying to get that to work, but no dice.
has anyone rooted successfully using SuperOneClick on a dell streak 7 with android 3.2 honeycomb official OTA update?
thanks for the help.
Click to expand...
Click to collapse
Yes, with 2.2.2. You have to remember to take out the SD card before you do it though.
Regards,
Hans

Just tried this with the latest 2.3.1 on my Dell Streak 7 4G that came with 3.2 on it. SuperOneClick gets to:
Rooting Device Step #7 Wait for Device - and then hangs
In the output windows I see the following:
Code:
export TEMPRANDOM=92181 export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output mount: permission denied (are you root?) END:92181export PS1="" /data/local/tmp/busybox mount > /data/local/tmp/output 2>&1 export TEMPRANDOM=49649 export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output rootfs on / type rootfs (ro,relatime) tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755) devpts on /dev/pts type devpts (rw,relatime,mode=600) proc on /proc type proc (rw,relatime) sysfs on /sys type sysfs (rw,relatime) none on /acct type cgroup (rw,relatime,cpuacct) tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000) tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000) none on /dev/cpuctl type cgroup (rw,relatime,cpu) /dev/APP on /system type ext4 (ro,relatime,barrier=1,data=ordered) /dev/UDA on /data type ext3 (rw,nosuid,nodev,noatime,barrier=0,data=writeback) /dev/CAC on /cache type ext3 (rw,nosuid,nodev,noatime,barrier=0,data=writeback) /dev/SDC on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro) END:49649export PS1="" mount -o rw,remount /dev/APP /system > /data/local/tmp/output 2>&1 export TEMPRANDOM=93079 export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output mount: Operation not permitted END:93079
Any ideas?

All known exploits were patched in Android 3.0.
There have been no known exploits that work on anything newer then that since it was released.

TheManii said:
All known exploits were patched in Android 3.0.
There have been no known exploits that work on anything newer then that since it was released.
Click to expand...
Click to collapse
So back to trying to get drivers for my Streak 7 installed under Win 64 so I can fastboot is pretty much it then, eh?

Looks Confused said:
Yes, with 2.2.2. You have to remember to take out the SD card before you do it though.
Regards,
Hans
Click to expand...
Click to collapse
Fail. He asked for 3.2.
I think you should use the fastboot way

exebreez said:
Fail. He asked for 3.2.
I think you should use the fastboot way
Click to expand...
Click to collapse
Ha. You should be nicer (kidding). I meant SuperOneClick v2.2.2. Which is what I've used to root HC V3.2 a couple of times now. I've done this so I can use one of the application managers to remove some of the factory installed dross in the stock firmware (which I think requires root access).
I'm a bit puzzled about one thing: As mentioned in another post in this thread, there are no known exploits for HC. So, I don't understand how this could be working, unless I'm not really rooting my tablet, or maybe its because the boot loader isn't locked in the first place?
If anyone happens to understand what's going on, I'd be happy to listen.
Regards,
Hans

Looks Confused said:
Ha. You should be nicer (kidding). I meant SuperOneClick v2.2.2. Which is what I've used to root HC V3.2 a couple of times now. I've done this so I can use one of the application managers to remove some of the factory installed dross in the stock firmware (which I think requires root access).
I'm a bit puzzled about one thing: As mentioned in another post in this thread, there are no known exploits for HC. So, I don't understand how this could be working, unless I'm not really rooting my tablet, or maybe its because the boot loader isn't locked in the first place?
If anyone happens to understand what's going on, I'd be happy to listen.
Regards,
Hans
Click to expand...
Click to collapse
So what you are saying is super one click 2.2.2 root DS7 hc 3.2.. I tryed super one click 2.3. Whatever... And it didn't work...
Sent from my Desire HD using XDA App

s14evil said:
So what you are saying is super one click 2.2.2 root DS7 hc 3.2.. I tryed super one click 2.3. Whatever... And it didn't work...
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
TL;DR: Yes.
I went and double checked. I'm running HC 3.2 on my Streak 7. The latest version of SuperOneClick I have is 2.2, according to the file I downloaded (dunno where I got 2.2.2 from, probably some mental issue).
I enabled USB debugging, took out my SD card, plugged my tablet in, and clicked the "Root" button.
It said my tablet was rooted. I installed "Root Uninstaller" and Superuser asked me if I wanted to grant it root access. I used this to remove Evernote and Kongregate. So, I think it worked.
Regards,
Hans

Looks Confused said:
Ha. You should be nicer (kidding). I meant SuperOneClick v2.2.2. Which is what I've used to root HC V3.2 a couple of times now. I've done this so I can use one of the application managers to remove some of the factory installed dross in the stock firmware (which I think requires root access).
Hans
Click to expand...
Click to collapse
Sorry dude, i didnt read that carefully.

Looks Confused said:
TL;DR: Yes.
I went and double checked. I'm running HC 3.2 on my Streak 7. The latest version of SuperOneClick I have is 2.2, according to the file I downloaded (dunno where I got 2.2.2 from, probably some mental issue).
I enabled USB debugging, took out my SD card, plugged my tablet in, and clicked the "Root" button.
It said my tablet was rooted. I installed "Root Uninstaller" and Superuser asked me if I wanted to grant it root access. I used this to remove Evernote and Kongregate. So, I think it worked.
Regards,
Hans
Click to expand...
Click to collapse
Thanks mate
Sent from my Dell Streak 7 using XDA App

What rom did you have installed? It could have already been rooted.
Also, there's always the possibility that there is a new exploit out that SoC uses that isnt patched. If there is then it will work for the time being. I dont actually read SoCs changelogs.
It COULD get fixed in the next stock rom (dell is still making more updates, they're simply not releasing them as pkgs) though. IF they ever actually decide to release another update OTA

I tried it and it failed so I went about rooting the long way. Took a while but I got it figured out. I would recommend doing the same.

TheManii said:
What rom did you have installed? It could have already been rooted.
Also, there's always the possibility that there is a new exploit out that SoC uses that isnt patched. If there is then it will work for the time being. I dont actually read SoCs changelogs.
It COULD get fixed in the next stock rom (dell is still making more updates, they're simply not releasing them as pkgs) though. IF they ever actually decide to release another update OTA
Click to expand...
Click to collapse
One of the stock HC roms from Dell. The OEM version is: GLUNB1A350630.
I had rooted it before I did the upgrade (with the factory shipped firmware), but after upgrading, Superuser no longer worked. I did a full reset to stock 3.2 (via the recovery menu VOL+ or - (I forget which) while powering on), then did the SuperOneClick rooting procedure.
Regards,
Hans

Instead of trying to use Super one click, Why not just follow this guide. Should have no issues rooting using the following steps. Yes its more than just click and wait, but its not very difficult if you follow the steps to the letter.
http://forum.xda-developers.com/showthread.php?t=1411193
[Guide] Absolute Newbie's Guide to Rooting a Streak 7 that has Stock Honeycomb
Hope this helps someone
Noticed there was not a link to Superuser7.zip on the newbie guide to rooting.. so I'm attaching a link.
http://www.tablet-cables.com/streak/tools/root/Superuser7.zip (Cap in file name required or it won't be found.)

Superuser7.zip

[DEV-ONLY][RECOVERY]CWM 6.0.1.x Using Pseudo File System

During my time hacking on android I've discovered some nice easter eggs deep in the android platform. One such easter egg is the mounting of ext4 images directly in the init.rc script. This is a feature I have never seen used by any oems and only by one custom rom [ EDIT: and by letama in his Sony Xperia Boot Manager ]! looking at the git logs this functionality has been present since September 2010 [ commit 49b8124a1759cb8b27e0c21a1a5a54b8a81bdb19 ]. What this effectively gives us is the ability to overlay a pseudo partition layout over the top over the existing layout, thus avoiding any "Danger" of accidental bricking the device by reformatting the SDCard. This is very similar to the way archos mount the stock file system and a variation/extension on the existing methods we use for the SDE Roms.
Although the explanation assumes the use of the SD models it should be fairly straightforward to apply the the HDD models.
THE METHOD:
PART 1 - Prepare a recovery ext4 image file
1. Build CWM6 from the CM10 source.
2. Modify The Recovery's init.rc file to look something similar to this
Code:
on early-init
start ueventd
on init
export PATH /sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
symlink /system/etc /etc
mkdir /boot
mkdir /sdcard
mkdir /system
mkdir /data
mkdir /cache
mount /tmp /tmp tmpfs
mkdir /partitions 0771 system system
mount ext4 /dev/block/mmcblk0p4 /partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount ext4 [email protected]/partitions/CAC /cache nosuid nodev
mount ext4 [email protected]/partitions/DATA /data nosuid nodev
mount ext4 [email protected]/partitions/SYS /system
mount ext4 [email protected]/partitions/SDCARD /sdcard nosuid nodev
mount ext4 [email protected]/partitions/BOOT /boot
on boot
ifup lo
hostname localhost
domainname localdomain
class_start default
service ueventd /sbin/ueventd
critical
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
disabled
# Always start adbd on userdebug and eng builds
# In recovery, always run adbd as root.
on property:ro.debuggable=1
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 18D1
write /sys/class/android_usb/android0/idProduct D001
write /sys/class/android_usb/android0/functions adb
#write /sys/class/android_usb/android0/enable 1
write /sys/class/android_usb/android0/iManufacturer $ro.product.manufacturer
write /sys/class/android_usb/android0/iProduct $ro.product.model
write /sys/class/android_usb/android0/iSerial A101S_REC
#start adbd
setprop service.adb.root 1
# Restart adbd so it can run as root
on property:service.adb.root=1
write /sys/class/android_usb/android0/enable 0
restart adbd
write /sys/class/android_usb/android0/enable 1
3. Modify the etc/recovery.fstab to look like this
Code:
# mount point fstype device
/cache ext4 /dev/block/loop1
/data ext4 /dev/block/loop2
/system ext4 /dev/block/loop3
/sdcard ext4 /dev/block/loop4
4. Creating an empty ext4 image file name REC and mount it on your pc. [ 5MB should do it ]
5. Copy the contents of the built recovery/root directory to the root of your mounted image.
6. chmod init.rc , default.prop and ueventd.rc to 644 ( rw-r-r- )
7. umount the ext4 image and push it to the root of you data partition
That's stage 1 complete. Part 2 Will Follow Shortly.....
Part 2 - Make a dual boot initramfs.cpio.lzo
1. Change the name of the /data directory to /bootdata by modifying the etc/mountpoints file in the initramfs.cpio.lzo. This stops CWM getting confused when trying to un/mount the data partition
Code:
mount_name mount_dev mount_point mount_fs mount_opts volume_name error_code custom_opt
rawfs /dev/mmcblk0p1 /mnt/rawfs rawfs none 150
system /dev/mmcblk0p2 /mnt/system ext4 rw,noatime,noexec system 152
bootdata /dev/mmcblk0p4 /bootdata ext4 rw,noatime,noexec bootdata 154 crypt_compat
storage /dev/mmcblk1p1 /mnt/storage ext4 rw,noatime #storage_name# 155
storage_A80S /bootdata/media /mnt/storage bind bootdata none 155
storage_A101S /bootdata/media /mnt/storage bind bootdata none 155
storage_A101XS /bootdata/media /mnt/storage bind bootdata none 155
storage_LUDO /bootdata/media /mnt/storage bind bootdata none 155
storage_A80H /dev/hdd1 /mnt/storage ext4 rw,noatime #storage_name# 155
storage_A101H /dev/hdd1 /mnt/storage ext4 rw,noatime #storage_name# 155
usbhost_ehci /dev/storage_ehci1 /mnt/usbhost_ehci vfat rw,noatime,utf8,shortname=mixed none 156
usbhost_otg /dev/storage_otg1 /mnt/usbhost_otg vfat rw,noatime,utf8,shortname=mixed none 156
rfsext4 /dev/loop0 /new-root ext4 rw,noatime none 157
rfsext3 /dev/loop0 /new-root ext3 rw,noatime none 157
rootfs /dev/loop0 /new-root squashfs ro,cts_compat none 157
ramdisk /tmp/ramdisk /ramdisk vfat loop,rw,utf8,shortname=mixed #ramdisk_name# 158 ramdisk,ramdisk_size=256
2. Using sirduke989 dmenu initramfs you can modify the init script in the initramfs to mount /bootdata instead of /data and also add /bootdata/REC and /bootdata/BOOT to the list
of known locations , I see this a temporary measure as there are a number of other ways to enable dual ( Triple?!? ) booting
3. Flash the modified initramfs and your choice of kernel using either the recovery menu or kd_flasher, I used the 3.0.21 kernel extracted from the 4.0.24 aos file.
You should now be able to boot into CWM Recovery!
{
"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"
}
Clearly I'm a developer not a photographer!!
Part 3 - Create rest of the "partition" images.
You should have a /partitions directory in you device root, This is what is normally mounted as your /data ( /dev/block/mmcblk0p4) and contains normal android user data e.g installed app settings databases etc. This is where I've created the reset of my Partitions which are just more ext4 images files. I did this using "dd if=/dev/zero ...." and "mke2fs -text4 ...." on the device through adb whilst booted into CWM. This saved time in pushing large empty ext4 files from my pc.
I called my image CAC ( cache ) DATA ( data ) SYS ( system ) SDCARD ( sdcard ) BOOT ( boot ) you can obviously call them what you like and place them anywhere as long as you match up the image names with those in init.rc and make sure the loop numbers are correct in the etc/recovery.fstab everything should be fine.
You can play around with the files sizes, I have an 8gb my current file sizes at the moment are
BOOT = 25MB
CAC = 500MB
DATA = 3GB
SYS = 500MB
SDCARD = 2GB
The sdcard mount point is probably worth pointing at an external sd if you have one available. I have a 32GB Class 10 that I'll probably set up.
After you've setup your psuedo partitions you should then be able to reboot into recovery, if you've done things correctly you mount output should contain the following
Code:
/dev/block/mmcblk0p4 on /partitions type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/loop1 on /cache type ext4 (rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/loop2 on /data type ext4 (rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/loop3 on /system type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/loop4 on /sdcard type ext4 (rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/loop5 on /boot type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)
Everything seems to function correctly, I have successful done a backup and restore of my system partition. I have also applied CWM-SuperSU.zip through install zip from sdcard. Mounting and Remounting works although I'm not sure if Mount USB Storage works yet, I didn't on linux and I've not tested on windows and finally wiping and formating was also successful.
Part 4 - Notes on setting up rom images.
Now you may of already realized normal archos images don't come as separate the /boot and /system images so work is require to split them up.
Also if you want to split the /system from the reset of a archos image your boot partition will need to be about 50MB as archos have they /bin /lib /usr directories which contains binary files that use /lib/libuClibc-*.so as it's libc which brings there root filesystem in at around 38MB.
There is a very strong case for ditching these binaries especially when using AOSP/CM based roms. My intial tests show this is possible.
Just like the recovery init.rc Similar changes have to be made to the roms init.rc
Moving Forward:
of course, there's a lot to do but I wanted to at least get this initial information out there for people to consider. I'm currently booting a Linaro 4.1.1 rom using the split partitions. I have also been working on better booting methods which is why I haven't given any details re the initramfs init script but It's fairly straight forward to adjust and adapt. I'll write up more details soon!

More Research!
As I mentioned, I've been further looking into different booting methods and I think I'm approaching what could be a workable solution that will make the Gen9 more like standard android devices
Here's some more of my findings
1. It turns out that we can dump the existing initramfs.cpio.lzo and we can use a standard android ramdisk layout as the android init will load instead of the init script that is currently being used, this also removes the need for switch root and other nonsense that archos have in there. There was one gotcha when had me stumped for about ten minutes, I needed to add "write /sys/class/leds/lcd-backlight/brightness 75" to the init.rc to turn the screen on.
2. It's possible to stop android either using adb shell stop or stopping each service zygote etc, and start CWM while android is booted. It's probably also feasible the manage booting between recovery and android using the persist properties system which should make switching between the 2 fairly easy to control without much tweaking to any binaries. Looking at other devices, namely samsung, they seem to do something similar with recovery being in the same boot.img as the standard files, they simply load a recovery.rc instead of the main init.rc, this might mean that we have to patch CWM to load the correct init.rc I've not looked at the code properly yet but It's not going to be an issue anyway as all the code is fully available, You've gotta love open source.
3. By mounting /dev/block/mmcblk0p1 to /mnt/rawfs we are still able to use abcbox, reboot_into writes to the params file in the partition to control boot switching, so we can maintain booting into sde while leaving the stock android partition in place. I was unable to get any immediate joy from kd_flasher, that maybe because we currently have the ramdisk we want to overwrite mounted as the rootfs. Again I can't imagine it being too difficult to jig this, It can probably be worked out by looking at the current recovery ramdisk scripts should kd_flasher style functionality be required at any point.
4. Most of the binaries that rely on uClibc can be recompiled against bionic without any issue, usb_modeswitch for example. If there are any closed source ones, then the dynamic linker ld-uclibc or whatever is called, ultimately symlinks back to uClibc and we can just grab the one file and place it in the /lib directory. I tested /usr/bin/lsdvd in this way and It seemed to work fine.
I've got all this going on while still leaving a stock android fully intact, which is a great fallback Just in case.... Keeping these modifications at a safe level is one of the primary goals to enable much wider use
I'll put together some examples within the next couple of days to demostrate what I'm talking about here.
I've got a Linaro 4.1.1 ( JRO03R ) which has working powervr drivers with a 3.0.21 kernel, although that's about all that's working on it at the minute.
It's more a proof of concept than anything else, The kernel would need recompiling to add tracefs functionality which is required by jellybean but using the same magic should leave the powervr drivers functioning still, If anyone's interested I can stick that up, I've foolishly deleted ( misplaced/can't remember ) the device files I used to build this.... Too many android source trees and not using git properly leads to school boy errors.
I'm currently working on an omapzoom 4.1.2 tree using the blaze_tablet device as a base, I think this may yield the best results for the archos.
I suppose one other thing to do is the fix up a stock rom to use these methods and give it CWM, that should be pretty simple to do. Although ICS is ooold and I'm really not a fan of some of archos' methods e.g booting 4 different devices off one firmware. Although to their credit they do demostrate just what possible with deviating android from it's normal standard structures.
Hopefully this has whetted your appetites, I'm pretty excited about what's possible here as I feel it brings these archos devices in line with most others.

Me Again!
Just a cheeky little update, I been trying the figure out the best approach to handle switching between android and recovery mode. In effect I kind of wanted to create a Stage 4 bootloader! because you can never have too many bootloaders LOL I certainly wanted to do a "proper" job on it and try to avoid changes to the android platform code.
While to doing research into this I found this patch to the linux kernel which the android team submitted for review, Reading the mailing list thread I don't think it's been accepted yet! It's true what they say about the Kernel Mailing List, You need to bring your A game and be sure of what your doing..
Anyways the patch add a boot-control-block driver to kernel which check for a boot flag, which is exactly what I need to make booting into alternative configuration nice and simple. I suppose it wouldn't be too difficult to chuck in support for the fastboot protocol on one of those configurations. So a CWM Shouldn't be too far off now!!!
As a little treat I've attached a recovery based ram disk if anyone what's to play, just flash it with you favourite kernel on to your sde partition. Then You can boot into recovery and set your self up a pseudo partition image layout through adb. You won't be able to be into android, obviously until you put your old initramfs back.......
This is totally unsupported.
Click to expand...
Click to collapse
I'm just chucking up for those who want to get a feel for to do so. If your uncomfortable playing around in this area then stand well back, It's not prime time yet!!!!
However Feel free to ask questions of a technical bent but If you can't get it to boot then tough luck I'm afraid for now! :laugh:
You shouldn't be able to do any damage with this be I wouldn't go selecting wipe/format etc until you've got some partition images sorted.
I've add abcbox to sbin and symlink reboot_into. It does not seem to fully reboot but It will set the boot flag which you then follow with a call to reboot, That will reboot back into CWM (sde).
Onward
EDIT: Here's the Init.rc and etc/recovery.fstab that It attempts to use.
Code:
on early-init
start ueventd
on init
export PATH /sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
symlink /system/etc /etc
mkdir /boot
mkdir /sdcard
mkdir /system
mkdir /data
mkdir /cache
mkdir /mnt
mkdir /mnt/rawfs
mount /tmp /tmp tmpfs
mkdir /partitions 0771 system system
mount ext4 /dev/block/mmcblk0p4 /partitions
mount rawfs /dev/block/mmcblk0p1 /mnt/rawfs
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount ext4 [email protected]/partitions/CAC /cache nosuid nodev
mount ext4 [email protected]/partitions/DATA /data nosuid nodev
mount ext4 [email protected]/partitions/SYS /system
mount ext4 [email protected]/partitions/SDCARD /sdcard nosuid nodev
mount ext4 [email protected]/partitions/BOOT /boot
on boot
ifup lo
hostname localhost
domainname localdomain
class_start default
service ueventd /sbin/ueventd
critical
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
disabled
# Always start adbd on userdebug and eng builds
# In recovery, always run adbd as root.
on property:ro.debuggable=1
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 18D1
write /sys/class/android_usb/android0/idProduct D001
write /sys/class/android_usb/android0/functions adb
#write /sys/class/android_usb/android0/enable 1
write /sys/class/android_usb/android0/iManufacturer $ro.product.manufacturer
write /sys/class/android_usb/android0/iProduct $ro.product.model
write /sys/class/android_usb/android0/iSerial A101S_REC
write /sys/class/leds/lcd-backlight/brightness 75
#start adbd
setprop service.adb.root 1
# Restart adbd so it can run as root
on property:service.adb.root=1
write /sys/class/android_usb/android0/enable 0
restart adbd
write /sys/class/android_usb/android0/enable 1
Recovery.fstab
Code:
# mount point fstype device
/cache ext4 /dev/block/loop0
/data ext4 /dev/block/loop1
/system ext4 /dev/block/loop2
/sdcard ext4 /dev/block/loop3

Any words about hdd versions?

DragosP2010 said:
Any words about hdd versions?
Click to expand...
Click to collapse
I all depends how you want the structure it, What it would change is the mount point of the paritions directory. After that. everything is loop mounted and sitting on top of the existing structure.
Code:
mount ext4 /dev/block/mmcblk0p4 /partitions

Great stuff!!!!
Hey trevd,
that's fantastic... i will definitely try this CWM in a few days with my custom kernel and bootloader (mountpoint will need some tweaks as well ).
I'm very busy these days, so i gess i'll leave some longer statements to the recent developments in a few days.
Just in short... it's very pleasant to see all these open developments popping up and i really, really appreciate this kind of hacking!
Keep on your great work... you rock!!
Cheers,
scholbert

Hi Trevd,
Nice job!
I've been using the same kind of trick on my Xperia S boot manager project, recovery on loops and mount [email protected] in inits. You may want to take a look at what I did there (see my sig), it may have some use for your project.
Basically, what I do is storing multiple kernels+cpios on the regular kernel partition. I use one (trimmed down to maximize space) to handle the boot logic and cwm, and I have enough space to handle two "regular" kernels. I handle kernel switch just before they load with a small assembly loader. It works very nicely on Xperia, and it's very nice to be able to dual boot with isolated cwms. I can't remember maximum size on a g9 kernel rawfs file, but I think you could have at least enough space to have two kernels to isolate recovery.

Hey letama,
nice to read you :highfive:
letama said:
I've been using the same kind of trick on my Xperia S boot manager project, recovery on loops and mount [email protected] in inits. You may want to take a look at what I did there (see my sig), it may have some use for your project.
Click to expand...
Click to collapse
Cool stuff again...
letama said:
Basically, what I do is storing multiple kernels+cpios on the regular kernel partition. I use one (trimmed down to maximize space) to handle the boot logic and cwm, and I have enough space to handle two "regular" kernels. I handle kernel switch just before they load with a small assembly loader. It works very nicely on Xperia, and it's very nice to be able to dual boot with isolated cwms. I can't remember maximum size on a g9 kernel rawfs file, but I think you could have at least enough space to have two kernels to isolate recovery.
Click to expand...
Click to collapse
AFAIK, we got around ~30MBytes in the raws partition on our tablets so would be possible to put some more kernel+cpios here easily.
Anyway, made some experiments with my latest u-boot port for the tablet this weekend.
I was able to bring up my A80S completely from MicroSD and boot into CWM by using uImage and uInitramfs (based on trevd's CWM image).
There's also some lowlevel multiboot implemented now by using the volume keys... but i know that i use a very special setup, so this is more a proof of concept and not a suitable environment for the average user
Cheers,
scholbert

Thanks Letama + Scholbert
I'll look at all this stuff this week....As a aside, I've played around with mmcblk0p3 and given myself an mmcblk0p5 / 6 of 4MB each. I found parted to be pretty useful (read:safe) for this..... I'm dubious about playing around with the rawfs too much at this point, mainly because I don't understand it fully, yet!.
Have you guy seen this https://github.com/swetland/omap4boot ( I think it's along the line of what Scholbert been working with/on )
Like I've mentioned to ultimate goal is a solution that is "safe" for the average user and also leaves the rest of the tablet in-tact, it maybe a lofty goal but worth a shot. :good:
Thanks for the input guys!

scholbert said:
AFAIK, we got around ~30MBytes in the raws partition on our tablets so would be possible to put some more kernel+cpios here easily.
Click to expand...
Click to collapse
30 for init kernel ? That's plenty indeed! Cool!
Anyway, made some experiments with my latest u-boot port for the tablet this weekend.
I was able to bring up my A80S completely from MicroSD and boot into CWM by using uImage and uInitramfs (based on trevd's CWM image).
There's also some lowlevel multiboot implemented now by using the volume keys... but i know that i use a very special setup, so this is more a proof of concept and not a suitable environment for the average user
Click to expand...
Click to collapse
Nice job! Too bad that Archos doesn't do this on their board with a small internal switch. Would be cool for people like me with big fingers and poor soldering skills
trevd said:
I'll look at all this stuff this week....As a aside, I've played around with mmcblk0p3 and given myself an mmcblk0p5 / 6 of 4MB each. I found parted to be pretty useful (read:safe) for this..... I'm dubious about playing around with the rawfs too much at this point, mainly because I don't understand it fully, yet!.
Click to expand...
Click to collapse
Hummm... You're going to end with a full re-partitioning scheme with system and data if you continue this way . Just be careful when you recreate partitions to let the empty space at the beginning of the disk untouched, instant brick ahead if you go there...
Just in case, here is what I did with my repartition script (do you have it ?): delete p3, delete p4, re-create p3 (careful with start point, leave the hole! it should start just after p2) as extended partition, big enough to hold the new partitions, recreate p4 (same thing about the hole, it should start after p3) with what remains and then you can create p5,p6,p7 with the size you want inside p3.
Last advice: rawfs, don't touch it .
Anyway, the good thing with what I did on Xperia S is that you don't mess with rawfs and re-partition, it's just like flashing a very big SDE kernel from recovery with unmodfified sde firmware, that's all. If I find some time, I'll take a look to see if we can do the same thing here.

letama said:
Just in case, here is what I did with my repartition script (do you have it ?): delete p3, delete p4, re-create p3 (careful with start point, leave the hole! it should start just after p2) as extended partition, big enough to hold the new partitions, recreate p4 (same thing about the hole, it should start after p3) with what remains and then you can create p5,p6,p7 with the size you want inside p3.
Click to expand...
Click to collapse
Hi
Yes I have read your previous threads on the subject which provided alot of the inspiration for the work currently at hand, It is also why I am being ultra careful around the partitions
I think maybe I'm just being too clever trying too pull everything back a step into the intramfs when we can just do the old switch root method method.... It's a little messy on the inside but it will get the job done!

Well, I don't like much the switch root too, it's not a very "Android way" of doing things and make some apps not very happy with it, but yes, it will get the job done, one root for recovery, one root for firmware. And Archos stock would be difficult without switch root, they did put far too much stuff outside of system.

letama said:
Well, I don't like much the switch root too, it's not a very "Android way" of doing things and make some apps not very happy with it, but yes, it will get the job done, one root for recovery, one root for firmware. And Archos stock would be difficult without switch root, they did put far too much stuff outside of system.
Click to expand...
Click to collapse
I'm very much for the "Android Way" I believe the archos stock roms can be re-jigged as the stuff outside of the system is not required by the system, this is all stuff that is a result of the BuildRoot build system and has a dependency on uClibc.
I'm going to try and get something usable this week, can I store additional files in the rawfs partition without running into trouble?

trevd said:
I'm very much for the "Android Way" I believe the archos stock roms can be re-jigged as the stuff outside of the system is not required by the system, this is all stuff that is a result of the BuildRoot build system and has a dependency on uClibc.
Click to expand...
Click to collapse
Well, it's required. It's used inside Android, it handles audio, wifi, codecs, smb...
I'm going to try and get something usable this week, can I store additional files in the rawfs partition without running into trouble?
Click to expand...
Click to collapse
In rawfs or initramfs ? I wouldn't add any file in rawfs, it would be difficult to do and I don't know how would behave the bootloader if it sees new files there. Initramfs you're free to do whatever you want until you reach maximum size of kernel+initramfs.

trevd said:
Have you guy seen this https://github.com/swetland/omap4boot ( I think it's along the line of what Scholbert been working with/on )
Click to expand...
Click to collapse
Well kind of... while i try to stick with the MicroSD our fellow vincencb follows the omap4boot path.
He already made a port of barebox bootloader to work with this tool and pushed it to the repos.
This way you may put anything you like on the tablet's RAM by using MicroUSB for communication and file transfer.
My way is more to get a full featured u-boot and put it into a state, where it might replace stock loader.
Last step is to put it in internal eMMC... so this is also research and development for now.
trevd said:
Like I've mentioned to ultimate goal is a solution that is "safe" for the average user and also leaves the rest of the tablet in-tact, it maybe a lofty goal but worth a shot. :good:
Click to expand...
Click to collapse
Yepp that sounds like a reasonable approach.
letama said:
30 for init kernel ? That's plenty indeed! Cool!
Click to expand...
Click to collapse
To be even more precisely, there are 32512*1K blocks for the rawfs partition.
On my device there's ~12MB left...
letama said:
Nice job! Too bad that Archos doesn't do this on their board with a small internal switch. Would be cool for people like me with big fingers and poor soldering skills
Click to expand...
Click to collapse
Yeah, a real switch would be nice indeed... there's some unused testpoints giving us additional GPIO
Need to solder though...
trevd said:
I'm very much for the "Android Way" I believe the archos stock roms can be re-jigged as the stuff outside of the system is not required by the system, this is all stuff that is a result of the BuildRoot build system and has a dependency on uClibc.
Click to expand...
Click to collapse
Some stuff outside of system is quite useful and gives us something like a minimal linux ecosystem.
Very useful at console level... some tools seem to be used by the Android system as well.
trevd said:
I'm going to try and get something usable this week, can I store additional files in the rawfs partition without running into trouble?
Click to expand...
Click to collapse
Mmmh, letama maybe right with being very careful with this part of internal storage. If it get's corrupt you'll risk a brick (could be restored though by using external boot mechanism).
Anyway the best would be to mount it RW and use the kernel driver to access it... the unknown part is still the bootcode.
There's some kind of allocation table at the beginning of rawfs partition. It is yet unknown how bootcode behaves with an additional entry
Anyway, this is a real nice project and i would really appreciate to see it pushing forward.
Take your time trevd, and again thanks a lot for contribution!!
Have a nice day,
scholbert

Not to put this down in any way, but wouldn't TWRP be better for the G9? It has a full touch tablet UI, which is better than CWM's
Sent from my Galaxy Nexus using Tapatalk 2

Quinny899 said:
Not to put this down in any way, but wouldn't TWRP be better for the G9? It has a full touch tablet UI, which is better than CWM's
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi Quinny
There's nothing to stop us using whatever recovery we like.... they all work the same way ( I think ) , i.e the code is compiled into a recovery binary. Unfortunately my touch screen stopped working long ago so I wouldn't really benefit

scholbert said:
To be even more precisely, there are 32512*1K blocks for the rawfs partition.
On my device there's ~12MB left...
Click to expand...
Click to collapse
Ah, yes, but there is space reserved for each file there, what I have to figure is how much is reserved for custom file (sde kernel). I don't want to have to shift the files located after custom to make room for sde kernel , it would defeat the "no-fuss/no-risk" of the method.
Anyway the best would be to mount it RW and use the kernel driver to access it... the unknown part is still the bootcode.
There's some kind of allocation table at the beginning of rawfs partition. It is yet unknown how bootcode behaves with an additional entry
Click to expand...
Click to collapse
Definitely. Re-partitioning is much safer if space is needed.

trevd said:
.... they all work the same way ( I think ) , i.e the code is compiled into a recovery binary.
Click to expand...
Click to collapse
This is a good keyword: The recovery binary itself!
Most tools inside the recovery are simply linked to busybox, which itself is a link to recovery executable.
In other words, we have some code responsable for the menu and framebuffer stuff and we have busybox.
The strings command gave me version 1.2.0. Now my question...
How to configure this part of code?
I'd like to enhance the busybox part.
Could you please provide a little to howto for a compiler run?
Will i need all that Android stuff installed...
I you have any clue, please point me in the right direction.
Lazy,
scholbert

scholbert said:
How to configure this part of code?
I'd like to enhance the busybox part.
Could you please provide a little to howto for a compiler run?
Will i need all that Android stuff installed...
Click to expand...
Click to collapse
Yes, you need full android repo. Android Build system is messy and tightly coupled, busybox is compiled with bionic (android libc), recovery is built on top of it with few android libraries links. Isolating all this "mess" would be difficult. Except disk space required, there is no big deal in getting full android repo.
I'd suggest to take a look at this, you should do the "Prepare the Build Environment" section.
I don't know how trevd built his recovery, but what I did is create a gen9 device to get proper configuration for recovery (frame buffer config, ...). You can get mine if you want, it's a little outdated (latest cwm doesn't need a specific gfx anymore, the custom one I used has been moved to upstream for instance), but it should give you a base.
To do that, you have to create an "archos" directory in cm9/device directory, then from inside it do:
Code:
git clone git://gitorious.org/archos-ics/device-g9.git gen9
Then, you need to setup the build env once. From cm9 root, you have to do that:
Code:
. build/envsetup.sh
(it setups android build environment)
then
Code:
lunch
then choose full_gen9-eng.
(it selects device target for build)
You should have something like that:
Code:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.0.4
TARGET_PRODUCT=full_gen9
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=IMM76L
============================================
from this point, you can compile:
make -j4 recoveryimage (change j4 with the number of parallel build you want depending on your cpu).
whole recovery fs should be in out/target/product/gen9/recovery/root, with recovery command in sbin
Last, how do you want to extend it? If you want to add custom commands, take a look at cwm bootable/recovery/extendedcommands.c, it may be easier to add stuff there than in busybox.

[Q] Lg P970 Optimus Black Huge Problem

Hi all,
I have two Lg Optimus Black. One of them i already use for 6 mounts and i can update or flash it by using SmartFlashTool easily.
Second phone which i bought unfortunately from ebay, when i get it 1 mounth ago, i try to flash it. I done. Then i try to root it,but i couldnt and it bricked.
Now last one mounth i try to flash it again,again,again.. i have always strange problem.. Last rom - which i flashed before try to root- was V20_D..
Now, i try to flash it to v30 or v20 or v10, after finish flashing phone doesnt restart. I take out battery, then put it back. After this,phone geting start..
But, it starting again with V20_D..
When i try to save any contact or changing some settings on the phone, after restart, it start again like factory reset..
I checked on hidden menu (3845#*970#) firt menu VERSION INFO...
SW Version is V20_D but factory version is changing depens on which rom i flashed last..(V10 or V30 or V20)
I checked same thing also on my other P970, this two version is same..
I could do everything easily and properly on other P970..
Do you have any idea? What is the problem ? What can i do ?

ozkanyanik said:
Hi all,
I have two Lg Optimus Black. One of them i already use for 6 mounts and i can update or flash it by using SmartFlashTool easily.
Second phone which i bought unfortunately from ebay, when i get it 1 mounth ago, i try to flash it. I done. Then i try to root it,but i couldnt and it bricked.
Now last one mounth i try to flash it again,again,again.. i have always strange problem.. Last rom - which i flashed before try to root- was V20_D..
Now, i try to flash it to v30 or v20 or v10, after finish flashing phone doesnt restart. I take out battery, then put it back. After this,phone geting start..
But, it starting again with V20_D..
When i try to save any contact or changing some settings on the phone, after restart, it start again like factory reset..
I checked on hidden menu (3845#*970#) firt menu VERSION INFO...
SW Version is V20_D but factory version is changing depens on which rom i flashed last..(V10 or V30 or V20)
I checked same thing also on my other P970, this two version is same..
I could do everything easily and properly on other P970..
Do you have any idea? What is the problem ? What can i do ?
Click to expand...
Click to collapse
first of all you didnt read the rules , post in q\a section , secondly make sure its a p970 not a p970h or ku9500 , if its a p970 download any rooted cwm rom such as this and flash it , then you should be fine

Sorry for rules
rrgrrg said:
first of all you didnt read the rules , post in q\a section , secondly make sure its a p970 not a p970h or ku9500 , if its a p970 download any rooted cwm rom such as this and flash it , then you should be fine
Click to expand...
Click to collapse
Thanks for reply.. Yes you are right, i didnt read the rules. Sory about that..
And second, as i can see under the battery, it is writing P970..
So, it should be P970..
Is there any way else to learn which one it is ?

ozkanyanik said:
Thanks for reply.. Yes you are right, i didnt read the rules. Sory about that..
And second, as i can see under the battery, it is writing P970..
So, it should be P970..
Is there any way else to learn which one it is ?
Click to expand...
Click to collapse
this should be enought

rrgrrg said:
first of all you didnt read the rules , post in q\a section , secondly make sure its a p970 not a p970h or ku9500 , if its a p970 download any rooted cwm rom such as this and flash it , then you should be fine
Click to expand...
Click to collapse
Btw P970 and p970h roms are interchangeable. It doesn't matter if ROM is for Fra, EU (p970) or Mex, Bra (p970h) you can install one from p970 on a p970h and vice versa.
sent from my Optimus Black V28c

Reboot recovery
rrgrrg said:
this should be enought
Click to expand...
Click to collapse
Ok, but how can i reboot recovery now? Phone doesnt boot in recovery mode..

ozkanyanik said:
Ok, but how can i reboot recovery now? Phone doesnt boot in recovery mode..
Click to expand...
Click to collapse
Have you installed ROM manager, and inside ROM manager install alternative recovery then you can reboot in recovery.
sent from my Optimus Black V28c

re4lsk said:
Have you installed ROM manager, and inside ROM manager install alternative recovery then you can reboot in recovery.
sent from my Optimus Black V28c
Click to expand...
Click to collapse
Sorry, but i think you didnt read my main post..
Even i flash any different patched or custom rom , it start again with V20d rom..
I tried on different computer.. i tried to reinstall all usb and other drivers.. I download different SFT and tried with this...
I download different rom and tried with this..
After all, it seems like nothing happens after flashing..
So, when i flash any patched rom now, i can not reach to recovery mode..
And today i notice something else.. After flashing i tried to factory reset from settings menu.. it doesnt work.. I push button but nothing happends.And phone can not return to desktop (home)

ozkanyanik said:
Sorry, but i think you didnt read my main post..
Even i flash any different patched or custom rom , it start again with V20d rom..
I tried on different computer.. i tried to reinstall all usb and other drivers.. I download different SFT and tried with this...
I download different rom and tried with this..
After all, it seems like nothing happens after flashing..
So, when i flash any patched rom now, i can not reach to recovery mode..
And today i notice something else.. After flashing i tried to factory reset from settings menu.. it doesnt work.. I push button but nothing happends.And phone can not return to desktop (home)
Click to expand...
Click to collapse
To me it looks like your phone is read only. Can you please set up adb (one package is in my noob how to) the type: adb shell
Then type: mount
And post the output here.
Either this or the connection between your pc and your phone doesnt work for any other reason...
Sent from my LG-P970 using xda app-developers app

N00BY0815 said:
To me it looks like your phone is read only. Can you please set up adb (one package is in my noob how to) the type: adb shell
Then type: mount
And post the output here.
Either this or the connection between your pc and your phone doesnt work for any other reason...
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
$ su
su
su: permission denied
$ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,relatime,size=4096k 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p8 /system ext3 ro,nodev,noatime,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p9 /data ext3 rw,nosuid,nodev,relatime,errors=continue,barrier
=0,data=writeback 0 0
/dev/block/mmcblk0p6 /dvp/hwkey ext3 rw,nosuid,nodev,relatime,barrier=1,data=wri
teback 0 0
/dev/block/mmcblk0p6 /dvp/userdata ext3 rw,nosuid,nodev,relatime,barrier=1,data=
writeback 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p5 /lgdrm ext3 rw,nosuid,nodev,relatime,errors=continue,barrie
r=0,data=writeback 0 0
$ su

I checked from England LG Service for my P970 by using imei number and serial number.. And the answer is there is no record for this numbers..
They said it can be copy or fake LG optimus black..
Now i am trying to do something on adb server..
But after all commands after i write, phone says read only file system..
I can not wipe all data, or delete something..
((

Hi ozkan can you check your phone on this web site with your imei?
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=IMEI
Delete IMEI at the last word of the link and write your phone imei on there.And you can see your phone model and latest firmware verion number.If your phone has fake imei you will see nothing.

George Jetson said:
Hi ozkan can you check your phone on this web site with your imei?
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=IMEI
Delete IMEI at the last word of the link and write your phone imei on there.And you can see your phone model and latest firmware verion number.If your phone has fake imei you will see nothing.
Click to expand...
Click to collapse
Hi George, there is nothing open on the link.. Can you check the link please is it working or not..

ozkanyanik said:
Hi George, there is nothing open on the link.. Can you check the link please is it working or not..
Click to expand...
Click to collapse
Its working i tried it already.
You just have to DELETE the IMEI and INPUT your Phone's Imei Number.
from this
http://csmg.lgmobile.com:9002/csmg/b...2.jsp?esn=IMEI
to this
http://csmg.lgmobile.com:9002/csmg/b...2.jsp?esn=xxxx
Key in your IMEI (the "x" is where u Key in your IMEI)
its 100% working