How to Install Clockworkmod on the Scroll Tablet - NOT Excel

[gazzy21uk]

Pre-installed 1.02 and 1.02s Warning

You may not be able to install clockwork recovery we are looking into this. The recovery may boot to a blank screen and not function. there is another post with teh dfault recovery files you can use to restore them.

Hi have been following this thread with great interest wonderful work been done here but it seems to have gone a bit stale any more info on using cwm with firmware 1.02 or 1.02s would be much appreciated also off any other recovery programs for android 2.1 which are as good and reliable thanks.
Need this working before PMT rename.

7" Scroll Tablet Rooted by z4
checked Terminal Emulator
installed super manager>root explorer
setCPU clocked
End Game froyo 2.2


Model Number: Scroll(SCR051624)
Firmware Version: v1.02s
Kernal Version: 2.6.29
Build Num: Android 2.1

[Mitre]

i have clockwork on my scroll v1.02 i never had the files (From 1st post warnings) on my device so it just loaded ok if you can find the file and delete should work

As for 2.2 think were gonna be closer to 2.3 if some one can upload it somewhere from the new gingerbread scroll

[gazzy21uk]

Assorted firmwares 1.01/1.02 Warning
/system/etc/install-recovery.sh -
You will need to have a rooted tablet and delete this file if you want to install a custom recovery image! Otherwise it will flash the original recovery file back when you reboot!


yaye the post seems to refer to the wrong image being flashed and not to the recovery crash have to be pretty certain before i jump already smashed a cnm touchpad ii on the rocks maplin won't be pleased lol

Model Number: Scroll(SCR051624)
Firmware Version: v1.02s
Kernal Version: 2.6.29
Build Num: Android 2.1

[gazzy21uk]

More help needed please
Just found some more info on firmware v1.02 versus v1.02s that might be of importance.

https://scrolltabletforum.sevo.uk/site/viewtopic.php?f=10&t=1218

by bloggs » April 26th, 2011, 8:25 pm

I've just been looking at the structure of the boot/recovery images posted by evilbobbins (1.02) and bobmcdermott (1.02s) and I notice that the two firmwares are using different pagesizes for the images. This would seem to imply that the hardware is different between these two machines, specifically that machines with 1.02 are using NAND chips with a 4k page size and devices with 1.02s (like my own) are using NAND chips with 8k page size. I could be wrong about this since, I guess, the NAND driver could be designed to handle any page size, but then why change the page size between builds

RichardP's photograph of his 1.02s machine's innards
http://imageshack.us/photo/my-images/132/image13su.jpg/

I'm wondering has anyone with a 1.02s successfuly used clockworkmod Recovery on this machine and won't using a smaller page size 4k instead of 8k slow the machine down with the older 1.02 firmware this is getting a bit complex
for my tiny pea brain
I need to go back and scratch my head some more.

Model Number: Scroll(SCR051624)
Firmware Version: v1.02s
Kernal Version: 2.6.29
Build Num: Android 2.1

[DualFever]

Did you search for and delete the files in warpedflash 1st post? cos this is what causes the problem

Assorted firmwares 1.01/1.02 Warning
/system/etc/install-recovery.sh -
You will need to have a rooted tablet and delete this file if you want to install a custom recovery image! Otherwise it will flash the original recovery file back when you reboot!

Yes i did and can't find these files on the device, still no recovery mode.

Postby rammy » April 26th, 2011, 10:44 pm
Have you tried flashing the mtd0_boot file?

Do you think i should try this, could it brick my tablet?

Thanks,

-Dual

[bloggs]

@ gazzy21uk

Hi have been following this thread with great interest wonderful work been done here but it seems to have gone a bit stale any more info on using cwm with firmware 1.02 or 1.02s would be much appreciated also off any other recovery programs for android 2.1 which are as good and reliable thanks.

I finally got around to installing ClockworkMod on my v1.02s Scroll and it seems to work okay. I haven't used it to install anything yet, but it seems to back things up okay. I might even try Cyanogen 7 now

I simply took the CWM image from the originally posted zip and converted it to an 8k page size instead of 4k, so it's not the latest version of CWM. My apologies if a later version has been posted here but I don't have the time to read back through 38 pages of postings !!! If someone points me to a later version I'll be happy to convert it to 8k page format and try it out.

I've put the V1.02s image here:-

http://www.megaupload.com/?d=Z4HK1GIV

but it might be useful to include it in the original zip with suitably modified instructions on which image to use.

Eddie

[gazzy21uk]

Thanks bloggs
I'm still in the proccess of reading about all this stuff have downloaded recovery-clockwork-scroll-8k.zip from your link
am also following fun at xda so am still playing catchup will wait to see how it turns out .

7" Scroll Tablet
Rooted by z4
Terminal Emulator
super manager

Model Number: Scroll(SCR051624)
Firmware Version: v1.02s
Kernal Version: 2.6.29
Build Num: Android 2.1

[Mitre]

@ bloggs can you recover to a backup that was created with an earlier version of cmd i backed up my 2.1 scroll with 3.004 before flashing to funs cyanogenmod and cant recover to 2.1 (just for testing purposes) as the md5file is not correct

[bloggs]

@ bloggs can you recover to a backup that was created with an earlier version of cmd

I'm afraid I don't know anything about ClockworkMod version differences, but I'd be surprised if the backups weren't upward compatible, i.e. Version 3 should restore Version 2 backups. I can see that if features are added in a later version then you might not, for instance, be able to restore a Version 3 backup using Version 2 CWM.

I think the version I'm using is 2.5.something (haven't got my Scroll to hand at the moment) and I've successfully swapped back and forward between backup images a few times.

Have you renamed or moved the backup file in any way? I ask because I tried adding some meaningful text to the backup filename and found it wouldn't restore it until I changed it back to its original name. It complained about the md5sum being wrong so it obviously includes the filename (possibly even the path?) in its calculation.

Eddie

[Mitre]

yes i did rename them thats me buggered then