yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] henge.:
No, no /proc/mtd either.

Here's the output of 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 /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p1 /system ext3 ro,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p2 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p3 /data ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/block/mmcblk0p4 /.secure ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=0,data=writeback 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
debugfs /debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p5 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:17 /mnt/sdcard/removable_sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:17 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/removable_sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[Miscellaneous Android Development] wiederre:
Hey.

with cat /proc/mtd is the same
[Miscellaneous Android Development] gmarkall:
Henge,

Thanks for this - I'll put together a recovery.fstab based on this for now!
[Miscellaneous Android Development] henge.:
Glad if I could help! :)
[Miscellaneous Android Development] tinybeetle:
Nice to see someone working on this. Thank you! There is a somewhat active community of users at this link on XDA that I'm sure are going to be pleased to see this thread. :)
[Miscellaneous Android Development] Wascha:
Keep us updated on your efforts please and thanks a ton in advance! Looking forward to your progress!

Gesendet von meinem A1_07 mit Tapatalk
[Miscellaneous Android Development] gmarkall:
I updated the recovery.fstab according to the information that Henge provided and rebuilt the recovery. I think one piece of information that I'm currently missing is the erasesize for the emmc, but I'm not sure what command should be used to find out what it is since there was not /proc/emmc or /proc/mtd.

I've also been examining the OTA update to see how it flashes partitions. It appears as if there is a utility included called "fuse" that writes partition images. It looks as though the fuse binary isn't on the system partition in the OTA, but my present thinking is that it might still work for flashing the recovery ramdisk. I've made the fuse binary available on the download page linked from the github repository, but I'd still recommend against trying to flash the recovery unless you're really sure you know what you're doing, as I haven't been able to test it yet.
[Miscellaneous Android Development] sinanju:
Happy to help when you get to the CM stage. Post or PM if there's anything I can do. At the moment, I've got the ear of a Lenovo customer advocate who is working on getting the code properly published. I'll ping him after the holiday and report back.
[Miscellaneous Android Development] gmarkall:
Hi Sinanju,

Thanks! When I posted the message on the Lenovo forum I mentioned that I was personally after the Linux kernel sources - however, subsequently I noticed that the tablet also uses the u-boot bootloader, which I believe is also GPLed and the sources may be helpful - have you heard any mention about this?
[Miscellaneous Android Development] sinanju:
I have not. When I ping the Lenovo guy I'll add it to the list of source they'll need to release.

Update: Email sent.
[Miscellaneous Android Development] imritechere:
This CWM has been a long time comming thanks for the effort. Keep us informed
[Miscellaneous Android Development] TDO:
The Nook Color uses almost the same hardware (but no gps and camera).

It has a really good working CM7 build. So maybe this would be a good starting point.

It also uses u-boot and has a includes a modified one in CM7 (booting from sd or internal).
[Miscellaneous Android Development] jaysus145:
Thank you for this effort!
[Miscellaneous Android Development] gmarkall:
Hi TDO,

Thanks - I had noticed the CM7 for the Nook Color - I've been using it to guide me so far in building the recovery. I had also seen that it includes the modified u-boot but I wasn't sure what the purpose of it was.

Edit: Apologies, I misunderstood your post at first. Re-reading it, I understand that the purpose of the modified u-boot is to allow booting from the internal or external SD card.
[Miscellaneous Android Development] gmarkall:
Since I'm not a new user anymore, I can now post links to the repository and hosting for the built recovery:

Repository: https://github.com/gmarkall/android_device_ideapad_a1

Hosting: http://www.doc.ic.ac.uk/~grm08/ideapad/

(I still wouldn't recommend attempting to try out the recovery yet, but it's there if anyone has any other purpose for it).
[Miscellaneous Android Development] Wascha:
FYI - rumor, fake or truth, who knows - but there's a youtube video showing ICS on an Ideapad A1 which is said to have been leaked on a chinese website and that there's news from Lenovo they will release Android 4.0 for A1 later.
[Miscellaneous Android Development] gmarkall:
You need to follow the instructions in the first post to install CWM. ROM manager doesn't support the A1.
[Miscellaneous Android Development] jpisini:
I have always meant to ask if ROM manager does not support the A1 why is it included in the CM7rom?
[Miscellaneous Android Development] gmarkall:
The cyanogenmod build system includes it. We could strip it out by forking one of the repositories and modifying it to not include RM but then there is more work to do merging changes from the upstream repo.
[Miscellaneous Android Development] jpisini:
Makes perfect sense thanks.
[Miscellaneous Android Development] regnick:
Many thanks to you, gmarkall :) Everything works like a charm !
[Miscellaneous Android Development] patuan:
How can I install stock ROM on CWM 5.0.2.7? I've tried many time but cannot install 2643 ROW via CWM 5.0.2.7 rev 3.
[Miscellaneous Android Development] barrielui:
This more like to be a feature, not an issue, but I can't get rid of it.

On 5.0.2.7 , sometimes the power key won't select the option. Instead, it hide out the menu, which reappears after pressing another key. What should I do when I get into the case?
[Miscellaneous Android Development] geoponer:
Press volume + and - at the same time, and the power button will act again as a selection button.
[Miscellaneous Android Development] gmarkall:
Download http://download.lenovo.com/slates/a1/OTA/A107W0_A234_001_015_2643_ROW.zip then put it on your SD card (internal or external) then use the "Install zip from SD card" option to install it.
[Miscellaneous Android Development] jpisini:
Maybe I am doing something wrong but I can only install things from the external card. Which is fine I just have to remember to copy over the files before rebooting but I see people say you can install from the internal and CWM doesn't even see that card.
[Miscellaneous Android Development] patuan:
I did it. But only effect with CM Rom, not effect with Stock Rom. I think that's problem of CWM 5.0.2.7 because that trouble does not appear on previous (CWM 3.0.0.5).
[Miscellaneous Android Development] barrielui:
Sorry to disturb, but after I install CWM Recovery 5.0.2.8 and the modified partition table in Recovery 5.0.2.7, I can no longer find the internal storage.

It shows unavailable in Setting-Storage. What should?
[Miscellaneous Android Development] gmarkall:
This sounds like the behaviour of an older version of CWM. Do you have the rev3 version?
[Miscellaneous Android Development] jpisini:
I am pretty sure I do have rev 3. I will double check.
[Miscellaneous Android Development] jpisini:
Checked I definitely have rev 3 so not sure why it doesn't work. Not a real issue like I said I just copy it to the external and it works perfectly.
[Miscellaneous Android Development] gmarkall:
I find it a little concerning - what happens, for example, when you try and use "install zip from internal SD card" or backup/restore using the internal SD card?
[Miscellaneous Android Development] jpisini:
It just flashes and then shows the menu again. I will try re-downloading and installing again to see if that makes a difference. All the other functions seem to work fine. I have flashed CM7 and stock with it. As well as making and restoring backups.

I did wonder at one time if wiping worked correctly as I wiped cache and installed a newer version of CM7 and the notification bar went all wonky, I couldn't read it. I did a restore and tried again and it worked fine so I could not replicate the issue.

I will let you know after I try again. It's a beautiful day out here I am going to go out and do some yard work in a few minutes.
[Miscellaneous Android Development] barrielui:
The problem is still there after formating /emmc in recovery. Anyone can help me?
[Miscellaneous Android Development] jpisini:
Redownloaded and reinstalled I can now see the internal card. I haven't tried installing anything yet. I am just glad I never bricked the tablet up to this point it must have been a bad download.
[Miscellaneous Android Development] jpisini:
Go back to the old partition table and CWM. There is a zip in this thread that will put the partition back.
[Miscellaneous Android Development] devrajp:
Help me to root

Dear gmarkall

First of all thanks for yr support and help on lenovo a1. I had a1 which was upgraded to 2643 us. And like yr post says i installed cwm and then rooted with a1 rooter.zip. No problem

But after some time i had a horizontal line in my screen and i had to intall stock recovery and unroot it by installing 2643 us rom again.

Now as company has given me a new tab. Which has Build number

A107w0_A234_001_017_2644_us And now i want to root again

So my quation is how i can root 2644 ?
[Miscellaneous Android Development] thebreezer:
Hi Gmarkall,

Now this is my problem. When try to install CWM (renamed to update.zip). Power volume-, I get the android with the arrow coming out of the box, but I get no progress bar, then it just shuts down. What can I do? Only want to revert back to stock. Seems many people are having this same problem and it seems it only happens on certain tablets. All this happens after I installed ICS. Thanks for your help.
[Miscellaneous Android Development] xbdesign:
follow me
[Miscellaneous Android Development] ehsangolpesar12:
Hi, any body tried cwm v3 for backing up and restoring on ota ics?
[Miscellaneous Android Development] alvenlkk:
hi,

i have one problem, now i have use CWM v5.0.2.8 boot in Lenovo A1, and i have do the wipe, for wipe all the thing,

then i press power off, now my A1 can't power on back.... :crying: anyone can help!!
[Miscellaneous Android Development] milaq:
new recovery build (testing)

a new recovery version (6.0.1.2) for the a107 is available for everyone to check out.

please report any bugs (touch calibration is not yet included but it should work fine w/o).

the update.zip can be aquired here:

http://milaq.exnet.me/downloads/android/a107/cwm-6.0.1.2-ideapad-a1.zip
[Miscellaneous Android Development] jpisini:
What has been changed?
[Miscellaneous Android Development] milaq:
this version was compiled from the ics base.

new features mainly consist of a new backup format option (dup) and menu enhancements
[Miscellaneous Android Development] milaq:
link fixed
[Miscellaneous Android Development] gmmurphy:
ramdisk

I have quite a problem. I have cm 7 on my a1. Trying to get back to stock so I can take ICS. But I do not remember what row I have so I can flash the ram disk. How do I know what row I had? I tried to flash stock recovery then the ICS zip. But I get boot loop. Reinstalled cm zip via cwm tablet is back but want to try ICS. What can I do thank you
[Miscellaneous Android Development] jpisini:
Download both. Flash the older one if you notice any strangeness flash the newer one. Once booted with the old one you can also check the installed version and flash the newer if needed
[Miscellaneous Android Development] andres.rios:
Hi, I've been following these instructions, but I could only get my A1 boot up into CMW. I can't flash CMW to the A1 (process finish ok but when A1 reboot into recovery mode, original stock recovery apears). In other hand, I've been trying to flash stock ROM or ICS Rom (Custom and Original ICS) and process shows "Error 7" and stops installing (ICS), with stock 2.3.4 flashing process finished ok, but, everything apears with my old stock ROM (Apps, Settings, etc.). In fact, I proceed to format system, data, cache, wipe everything, etc. but, only system could be performed. Data and Cache partitions shows error when I tried to format through CMW.

Somebody has this issues?

Help Please.....

Regards,
[Miscellaneous Android Development] jouwheld:
After months of using a version of CM7 its time to try out some other ROMs. The thing is I'm still on CWM-based recovery v5.0.2.8 with the altered partitioning so without access to my internal SD. What would be the best upgrade path to the newest version so my partitioning will be "normal" again or so that I will have access to my internal SD from android.

In the OP I see that I should just upgrade but I want to know if I should first do something else.
[Miscellaneous Android Development] jpisini:
Make sure to make backups. There shouldn't be any issues.
[Miscellaneous Android Development] vmaxept:
CWM will not backup

cwm 6.0.1.2 Installed. Boost to recovery. Try to run a backup to external SD. Msg shows it started to copy image. Nothing for 20 minutes.

Hit on/off msg says there is an error with the backup

Tried to BKUP to internal SD - same problem.

I have a back up file on the sd

How do I know it is good?

Thanks

edit backup file is empty

edit#2 Flashed 5.0.2.7 rev3 that version works

made backup

on to installing cm7
[Miscellaneous Android Development] vmaxept:
CWM 6.0.1.2 Will not backup

I hope this thread is not dead?

I installed CM7 works well. I used v6.0.1.2 to install as older versions gave me the 'error 7'.

I had to use cwm v 5.0.2.7 to backup the stock os.

.

As above post, I cannot back up current os with 6.0.1.2. It appears I have to flip versions of cwmr - old ver to backup new version to install - a real pia

Is there any advice to help me resolve this problem

Thanks
[Miscellaneous Android Development] bnbhaohao90:
:laugh:thanks a lot
[Miscellaneous Android Development] geoponer:
I managed to accidentally delete my backup of setup files and it seems that CWM v6.0.1.2 by Milaq is not anymore available in the original link; I would be grateful if anyone could upload it somewhere so that I can download it.

Thanks in advance!

::edit:: I just found it here: http://milaq.exnet.me/downloads/a107/misc/
[Miscellaneous Android Development] Janis:
Wakey, wakey....

My sister's A1107 (completely virgin stock) is stuck in a boot loop. I've redownloaded both 6.0.1.2 and 5.0.2.8 pushed and pulled both (/sdcard/update.zip. and I tried mnt/sdcard/update.zip). I also plugged in an external sd with both (at separate times) in its root dir. It's really there.

When I boot into stock recovery, I get a split-second flash of progress bar with yellow just on the tiniest left slice, then the progress bar disappears, and it sits in stock recovery.

There is one other post regarding this with no responses. I'm stumped. Any help is gratefully accepted!
[Miscellaneous Android Development] jpisini:
What type of sdcard is it? What format is it in? I will do some research and see what I can come up with.
[Miscellaneous Android Development] Janis:
Thank you!!!

If I'm following the instructions, it shouldn't be looking at the external sd at all; the stock recovery should be using the internal sd and that's it. I've copied & confirmed the cwm update files straight from Windows 7 using adb.

About a year ago I got rid of any micro sd's that weren't class 10. I had too many, and I figured that was good culling criteria. I have the bootable image on a 1Gb SanDisk, but it's not marked as a class 10. I have the update.zip on a 4 GB SanDisk formatted Fat32.

I didn't try another one because I was only checking on that reversal of sdcard/emmc (which, if I'm not mistaken is a remnant of adapting Cyanogen's/Steve Kondik's ROMs to phones that actually had internal user-usable storage from the G1, which only had enough built in memory for cupcake, so only one sd, the external one. Remembering that is the only way I can remember which is which).

I'll try another card, but I don't have high hopes. I do appreciate your willingness to search!

---------- Post added at 01:05 PM ---------- Previous post was at 12:41 PM ----------

EDIT: I got it. I did two things: I cleaned the external sd of all the other stuff. All I had was update.zip and update5.zip. I also held the volume button through what looked like more than a recovery load cycle.

Tools in place. Now it's on to getting the device to read the img file it can't read on the 1GB file.

Thanks again for the offer!
[Miscellaneous Android Development] jpisini:
Glad you got it. Good luck
[Miscellaneous Android Development] spiegeleixxl:
On related note: Since the A1 contains the regular OMPA3621 EVT1A, isn't there a chance that it simply uses a regular OMAP3 u-boot?

Found some git repository on the internet at omapzoom, not sure if that helps us much.

@ git.omapzoom.com/?p=repo/u-boot.git;a=summary

TI has his own page for the X-loader (which we have version 1.41 on the A1)

@ gforge.ti.com/gf/project/bootloader/wiki/?pagename=X-Loader

Additional infos are at omappedia.org/wiki/Bootloader_Project where the TI page migrated to after 2009.
[Miscellaneous Android Development] otsego_amigo:
+1 ;) thank you!
[Miscellaneous Android Development] spiegeleixxl:
OK, inserting a SD formated with FAT32 + a partition with ext2/3 definitly causes it to do \something\. I compiled a x-booter and a u-boot according to the wiki (omappedia.org/wiki/Bootloader_Project) for the OMAP3630SDP. The tablet now turns white and then slowly fades to black (you know, the kind of stuff you get when you punch a old LCD screen) and gets stuck when I try to boot, so I assume it tries to load u-boot.bin or ML0/xloader and prolly dies somewhere along the way. I'll try to inject some of the parameters from the original /proc/cmdline from the stock kernel, maybe I just forgot a couple of modules to bring it to show something.

On related note: if you boot the A1 into recovery mode (adb reboot recovery), it will identify itself as "Texas Instruments OMAP3630" and requires new drivers to install. Does anyone happen to know any Windows XP drivers for that? I know it doesn't matter if i use my linux VM, but it appears, and after a couple of seconds it disappears again.

I'll try to investigate this issue a bit more, with some luck we might be able to boot images from SDCards. It definitly reacts to the fact that i shoved a formated SDCard in.
[Miscellaneous Android Development] darxkies:
Correct me if I am wrong, but as far as I know the A1 has no Flash Chips only a built in SD Card. You can also insert a second SD Card using the external slot. I am a bit confused. What exactly did you do? Did you replace the built-in SD Card or did you use the external slot to boot from? If the later is true, how did you force it to boot from the external SD Card?

From the following page you can apparently download the update.zip file which is supposed to install ClockworkMod

bit . ly/ vQ6Nvw

(I had to mangle the address as I am not allowed to post links.)
[Miscellaneous Android Development] gmarkall:
spiegeleixxl,

Nice work - it would be helpful if we could boot from the SD card!

Regarding what happens when we reboot into recovery with ADB, I tried it on mine (just got it, straight out of the box :-) ), I saw it appear as 0451 : D00E. A bit of searching led me to this post on OMAPPedia: http://www.omappedia.org/wiki/Talk:Embedded_MMC_(eMMC)_boot

According to the OMAP U-boot utils reference manual, http://omap-u-boot-utils.googlecode.com/files/omap-u-boot-utils-refman.pdf , pUSB seems to be a tool for transferring u-boot.bin over USB - so another possibility may be to boot over USB as well.
[Miscellaneous Android Development] gmarkall:
I had a look at that and I was a little reluctant to try it as at the moment as I don't currently see a way to recover things if I were to mess up both the recovery and the system partitions. So instead I had a look at the update.zip that is intended to install clockworkmod recovery.

It appears as though it doesn't install clockworkmod recovery, but rather it replaces the standard recovery in memory with clockworkmod, kills the original recovery and then starts up clockworkmod. So I don't think it's really a recovery that actually installs to the recovery partition, unfortunately. (However I could have misunderstood its operation - have you tried using it?)

At the moment I'm looking for a way to make sure that we can safely test things, partly following speigeleixxl's suggestion of trying to boot from sd card, and also seeing about booting from USB. So far I have got the pUSB tool to recognise the device when it reboots and briefly announces itself as the TI OMAP3630, but for some reason I haven't figured out yet it doesn't actually send the file to the device. It might be that the USB device is disappearing too quickly for it to respond.

I also thought it might be useful to get an idea of where the partitions are on the internal storage, so I dumped the first 32MB of flash thinking that most of the important ones lie there, and examined it to correlate it with the partitions that are flashed by the OTA. So far, I found:

Start End Size Name

0x00000000 0x0001ffff 0x00020000 mbr
0x00020000 0x000201ff 0x00000200 mbr_boot
0x00020200 0x0003ffff 0x0001fe00 xloader
0x00040000 0x0007ffff 0x00020000 truncated linux kernel, possibly junk/part of xloader
0x00080000 0x002fffff 0x00280000 uboot
0x00300000 0x00bfffff 0x00900000 kernel
0x00c00000 0x013fffff 0x00800000 recovery
0x01400000 0x017fffff 0x00400000 logo
0x01800000 ramdisk starts here, not sure yet where it ends or what comes next.
[Miscellaneous Android Development] darxkies:
How did you do that dump? The mbr is actually the GPT/EFI. After the ramdisk are the 5 partitions (system, cache...)

You are right about the recovery image. It does not install it. The original recovery image is actually a ramdisk.

The nook color is able to load xloader, uboot and everything else directly from the external sd card, as long as it is configured properly. Unfortunately I can't test that yet, as I have no uSD.

What I have found out so far is that the internal SD Card really uses GPT/EFI.

The u-boot version is "1.1.4 (Sep 24 2011 - 21:39:18)"

The xloader version is "1.41 (Sep 9 2011 - 19:26:08)"
[Miscellaneous Android Development] gmarkall:
I did the dump with:

dd if=/dev/block/mmcblk0 bs=1048576 count=32 of=/sdcard/mmcdump.img

The GPT table doesn't seem to give all the partitions - only those that are visible to the android kernel, unless I missed something.
[Miscellaneous Android Development] darxkies:
My question was rather how did you identify the addresses where the files are stored?

You are right. The GPT includes only the partitions that are supposed to be visible and accessible by android. The other files are stored without any partitions. U-Boot loads them using "hardcoded" addresses.