Forum switched to read-only as of 2020/06/01


Latest product reviews
ARCHOS 50 Diamond
ARCHOS GamePad2
ARCHOS
Smartphones
ARCHOS
TV Connect
ARCHOS 101 XS

A A A
Avatar

Please consider registering
Guest

Search

— Forum Scope —






— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

Register Lost password?

ClockworkMod (CWM) Recovery easy install for RK3066 and RK3188 -- TWRP/CWM Flash-Tool and root for RK3288

 Please donate to support OMA and CrewRKTablets firmware work, thank you !

sp_Feed sp_TopicIcon
Modifying the Arnova 10 G2 custom firmware
Avatar
finless
Stanton, Ca

Contributor
Forum Posts: 604
Member Since:
2011/12/10
sp_UserOfflineSmall Offline

Thanks Received: 2
16
2011/12/17 - 21:56
sp_Permalink sp_Print sp_EditHistory

OK I am going to try a new approach.  I have downloaded other tablet RK29 roms and I notice most of them are using ext3 for /system and not cramfs.  I think this is the secret.... Well at least I am hoping.

So the wendal tool script is easily edited for unpack and pack.  It's the .lua file which is the script.

So in the pack I can see the call to mkcramfs.  Now I have to learn how to not make a cramfs but instead a ext3.  Any tips?

 

Bob

Avatar
finless
Stanton, Ca

Contributor
Forum Posts: 604
Member Since:
2011/12/10
sp_UserOfflineSmall Offline

Thanks Received: 2
17
2011/12/17 - 22:59
sp_Permalink sp_Print

By the way I beleive the reason the rooted rom his less space is due to how they got around the cramfs read only thing.  By making a symbolic link to 2 directories I think the system is reserving the space for that!  If we can get /system to be ext3 I think we have this one solved....

 

I am doing research on it now and this is going to take a while I think 🙁
Some of my old unix days are coming back to me now (circa 1984) but MUCH has changed like file systems etc.  So it is painfully slow but fun none the less 🙂

 

Again any tips on how to take the unpacked /system from Wendals tool and make it a ext3 .img would be helpful!

 

Bob

Avatar
finless
Stanton, Ca

Contributor
Forum Posts: 604
Member Since:
2011/12/10
sp_UserOfflineSmall Offline

Thanks Received: 2
18
2011/12/17 - 23:32
sp_Permalink sp_Print

FYI I found a post from Wendal on how he got root to /system and in fact looks like I was correct.  He is doubling the file system is /sysrw and copying it over.

 

http://www.slatedroid.com/topic/22162-writable-system-for-rk29xxt760p71-et/

 

I think the real answer is getting a non-cramfs for /system but who am I to doubt Wendal and the magic he does?  FYI if you look at the stock init.rc Arnova even commented out the mnt line where /system was a ext3 before and replaced it with a cramfs mnt.

 

Bob 

Avatar
finless
Stanton, Ca

Contributor
Forum Posts: 604
Member Since:
2011/12/10
sp_UserOfflineSmall Offline

Thanks Received: 2
19
2011/12/17 - 23:40
sp_Permalink sp_Print

DING DING DING!

I just found this post and it was made after the rooted rom where Wendal explains he found a better way!

He is converting cramfs to ext3 🙂

http://www.slatedroid.com/topic/22162-writable-system-for-rk29xxt760p71-et/page__st__20__p__270126#entry270126

 

His post:

I provide a better way:
1. a new loader, I will attach it. modify package-file bootloader RK29xxLoader(L)_V1.63.bin to bootloader RK29xxLoader(L)_V2.06.bin
and replace RK29xxLoader(L).bin with RK29xxLoader(L)_V2.06.bin and put RK29xxLoader(L)_V2.06.bin into Temp
2. unpack your boot.img , open init.rc found mount cramfs mtd@system /system ro change to mount ext3 mtd@system /system wait rw
3. convert you system.img to ext3 format (in linux ): dd if=/dev/zero out=/tmp/system.img bs=1024 count=200000 /sbin/mkfs.ext3 /tmp/system.img mkdir /tmp/system mount -t ext3 -o loop /tmp/system.img /tmp/system cramfsck -x /tmp/system system.old.img umount /tmp/system
then pack the rom , flash it     


Avatar
finless
Stanton, Ca

Contributor
Forum Posts: 604
Member Since:
2011/12/10
sp_UserOfflineSmall Offline

Thanks Received: 2
20
2011/12/18 - 22:56
sp_Permalink sp_Print sp_EditHistory

OK I can tell you that hacking at this all day I cannot get the system to work with system.img as a EXT3 file system.  I don’t think that is going to work unless there are other changes needed I do not know about.  Fyi I installed Ubuntu in a VirtualBox VM so I was working in Linux properly instead of cygwin.

So here is the status and here is what I have done. 

1) I absolutely can unpack and repack boot.img using the process I explained in an above post. I have tested this many times.  I can edit default.prop and init.rc, repack boot.img and repack update.img.  Put that on my Arnova and it will boot up and takes my changes.  So I know that is not the issue. 

2) S0 once I knew that all was working and I could make good update.img files with edited boot.img files, it was time to try to edit init.rc and make the changes to try system.img as a ext3 file system.  So you know I tried a few mount options in trying to make it work.  Some of these I have seen in other ROM init.rc files.

Mount ext3 mtd@system /system
Mount ext3 mmc@system /system
Mount ext3 mtd@system /system rw remount
And the one Wendal says Mount ext3 mtd@system /system wait rw

3) OK so init.rc all edited and ready now time to convert system.img to a ext3 file system.  This was pretty easy actually.  The Wendal tool extracts system.img to a system directory as part of the update.img unpack and it roots it for you.  I then transferred that folder to Ubuntu in a tmp directory. BUT to make sure I also copied over the unpacked original system.img.  First test was to see if I could mount the original system.img cramfs file.  No issue.

Sudo mount -t cramfs -o loop system.img system
   Warning system seems to be mounted read only.

I was able to open the system folder and all files were there. So all good!  OK next is to make a new system.img file.  Went pretty easy.  Wendal suggested size of 200000 which I tried but worried that was much larger I started with size of 125000 which allowed all files to be copied into it and left 4K left just like the cramfs system is on the tablet.  Needless to say size did not matter.

sudo mkdir system1  Note: I already have a mounted system folder from the original system.img
sudo dd if=/dev/zero of=system1.img bs=1024 count=200000  Note: Makes a blank NEW system1.img file.
sudo /sbin/mkfs.ext3 system1.img   Note: Now format the system1.img file a EXT3
sudo mount -t ext3 -o loop system1.img system1  Note: Mount it. folder will be blank.
sudo cp -r system/* system1    Note: Copy all the files from mounted system folder to the new mounted system1 folder.
sudo umount system
sudo umount system1

4) OK cool.  All done.  I now have a system1.img file that is in ext3 format.  I copy that into the Wendal tool in temp/image/ Delete the original system.img and rename system1.img to system.img.  I have also copied in my new boot.img I made with the proper mount command.  We are ready to repack update.img with the Wendal tool BUT FIRST we must make a change.  We do NOT want Wendals tool to repack system.img in cramfs again.  We must make a change. Open the file rk29xx_rom_tools.lua in the Wendal tool.  Scroll down to the repack area and find this command os.execute('mkcramfs -q system Temp/Image/system.img')  Put two dashes in front of that to comment that line out --os.execute('mkcramfs -q system Temp/Image/system.img').  Now when you run the runme.bat and select #2 to repack it will use the system.img file you copied and not overwrite it with a cramfs system.img.  This is super important or everything you did is lost.

OK the new update.img is now considerably larger than the original due to system not being compressed.  But when you copy it over to the Arnova or use the RK flash tool ALAS 🙁 the system is bricked.  It JUST will not work.  I tired multiple times with many different mount commands, smaller system.img images, etc.

Note:  Per that post from Wendal on the t760 thread he also supplied a new RK29xxLoader(L).bin  His post says 2.06 which we already had in the Wendal tool but he posted an updated of 2.08 which I downloaded.  You have to replace the one in the Wendal tool root as well as in temp.  The one in temp has to be renamed from 2.08 to 2.06 or the lua script will not find it and errors out.  Anyway I tried both.  You can tell the difference as 2.06 is 136K and 2.08 is 138K.

 

Anyway.  It's a NO GO.  Not sure what else to do.  I see other rk29 tablets boot.img files out there that I have taken apart where the init.rc is mounting system as a ext3.  So I am pretty sure it possibly can work but what else needs to be changed?  I have no clue at this point....

FYI Admin.  The boot.img that is in the current ROOTED ROM you are supplying is corrupt.  Sure it works but you cannot depack it without getting a gzip end of file error.  However I found another boot.img made by Wendal for the T760 and that will unpack just fine with no errors.  It is the EXACT same boot.img file he used on that ROM.  When I unpack the one from the Arnova rooted rom it errors and is missing files like init.sh and some others.  This is why I could never repack the one from that ROM file and make it work.  So I will be making a new rooted ROM with a unpackable boot.img for you!!!  That fact that I never got the init.sh file was the problem. Wendal uses that to copy files to /sysro and without it on the repack it would never work.

Anyway TOTAL frustration at this point 🙁

Bob

Avatar
finless
Stanton, Ca

Contributor
Forum Posts: 604
Member Since:
2011/12/10
sp_UserOfflineSmall Offline

Thanks Received: 2
21
2011/12/19 - 00:41
sp_Permalink sp_Print sp_EditHistory

OMG... I AM AN IDIOT!

I got it baby! 

ONE little mistake in my process I forgot to do the entire day.....  When you repack boot.img YOU MUST open it in a hex editor and change PARM to KRNL.  I was forgetting to do this the entire time!

However, instead of a blank screen and dead, I am hung on the ARNOVA screen.  So it got a lot farther than before.

OK back to work!  This still maybe doable I hope!
Keep your fingers crossed 😉

Bob

Avatar
admin

admin
Forum Posts: 5878
Member Since:
2010/09/11
sp_UserOfflineSmall Offline

Thanks Received: 3169
22
2011/12/19 - 01:13
sp_Permalink sp_Print

Finless, reading from your last posts, this is pretty good work you have done Wink

Having a clean boot image is definitely a plus, I am looking checking your image or making myself a new one based on this proper boot image.

Regarding fixing the different brick issues you are facing, I don't have much clue until we figure a way (if there is one) to log the boot failure reason.

If you like our web site, applications and firmwares, feel free to support our site. Donations are used to pay the bills for our server hosting costs, development tools and purchase new tablets to support.

Avatar
finless
Stanton, Ca

Contributor
Forum Posts: 604
Member Since:
2011/12/10
sp_UserOfflineSmall Offline

Thanks Received: 2
23
2011/12/19 - 02:39
sp_Permalink sp_Print sp_EditHistory

Well still no go 🙁

I have tried making system.img different sizes from 125000 to 250000
I have tried different mount parameters as I posted above.

Alas I get an Arnova screen at boot and then it just hangs.
Still NO GO for system being a ext3 type.

BUT maybe a clue... In my original ROM from Arnova, the init.rc file has this commented out just before the cramfs mount command.

#mount mtd@system /system ro

I realize it is ro and can be changed to rw but they are not spcifing a file system?  So if I was to convert my system.img to a non-specified format or I guess that is a standard linux format, how do I do that?  e.g. how do I do a MK on the blank system.img I made?  Damn I hate beeing a n00b...

 

Bob

Avatar
p1ceus

Contributor
Forum Posts: 38
Member Since:
2011/11/23
sp_UserOfflineSmall Offline

Thanks Received: 1
24
2011/12/19 - 16:14
sp_Permalink sp_Print sp_EditHistory

Hello finless, that is a pretty good progress you made during three days! 😉

I was messing with all this stuff myself few days ago, but without success. If you have time you can DL this rom for Telcast T760. It's basically same HW as Arnova except audio drivers, wifi, touch screen and Gsensor. I tried to put it into Arnova (but just for safety unpack it and replace recovery.img with stock one) I get it to boot and was able to control the system (with mouse connected). So far I can tell it was pretty smooth. And for the record, this rom has fully accessible /system and another part of the system 😉

I guess only thing needed to get it to work properly is to replace drivers in kernel.img...right?

Anyway I spend whole day setting up my Ubuntu VM machine and I'm now compiling ICS for Arnova from sources! 😀 (don't know what will be the result since I never do that).

Keep up the good work 😉

 

EDIT: one more thing (I'm at work so I don't know the exact names), if you replace two lines in ?boot.conf? - placed in the root of /system folder and enable debugging, you can the access device using adb even if it's not booting. Then do adb shell - logcat and log should tell you why it cannot fully boot.

 

P.S.: regarding your first question about missing Account & Sync in settings menu, its just not as a item in Settings.apk. If you want it there, you need to unpack Settings.apk and edit .xml file. Then you will see this option in Settings 😉

btw, you can also add SNSAccounts.apk into image to have fcb, twitter and few anothers accounts there (but due to missing contacts this will be useless)...

Avatar
admin

admin
Forum Posts: 5878
Member Since:
2010/09/11
sp_UserOfflineSmall Offline

Thanks Received: 3169
25
2011/12/19 - 16:25
sp_Permalink sp_Print

ICS on Rockchip 2918, sweet Smile

For kernel, drivers etc... you may find some info in the RK2918 LGL'ed source code here

/blog/archos-tablet/lgpl-rk2918-linux-kernel-source-code-publication/

 

and from http://androtab.info/cyanogenmod/rockchip/ where fun_ / naobsd has started to work on porting the CM7 Gingerbread on RK2918 tablets. 

If you like our web site, applications and firmwares, feel free to support our site. Donations are used to pay the bills for our server hosting costs, development tools and purchase new tablets to support.

Avatar
p1ceus

Contributor
Forum Posts: 38
Member Since:
2011/11/23
sp_UserOfflineSmall Offline

Thanks Received: 1
26
2011/12/19 - 16:30
sp_Permalink sp_Print

Hey admin, thx for the link to sources 😉 I totaly forged about that post 🙂

Avatar
josbos

Contributor
Forum Posts: 57
Member Since:
2011/12/19
sp_UserOfflineSmall Offline

Thanks Received: 2
27
2011/12/19 - 18:54
sp_Permalink sp_Print sp_EditHistory

Keep it up, if it can help take a look into this init.rc

https://github.com/naobsd/cm_device_rockchip_rk2918/blob/master/init.rc

Avatar
finless
Stanton, Ca

Contributor
Forum Posts: 604
Member Since:
2011/12/10
sp_UserOfflineSmall Offline

Thanks Received: 2
28
2011/12/19 - 19:02
sp_Permalink sp_Print

p1ceus, thanks but I have played with the T760. That's how I found the boot.img that was not corrupt like the one in our current rooted rom is. I can unpack and pack that roms boot.img but the current boot.img for the Arnova rooted rom is corrupt and you can't unpack it without getting gzip errors. The T760 boot.img you can. The init.rc in both the t760 and the Arnova are exactly the same.

Anyway the T760 rom is rooted in the same way our current rooted Arnova rom is. In fact our rom was made by using the T760's boot.img file and repacking our update.img with that boot.img. The problem is you loose half your available memory. This boot.img was made by Wendal. How he got write access to /system was a trick but causes double the space needed for the /system dir. As I posted above a few posts ago he is making a directory called /sysro and is mounting that as the system directory. Then he is making a symbolic link to /system. Tricky but it causes the system to use double the memory to store the /system files.

So this is not the answer which is why I have been trying to figure out another way to get write access to /system. Wendal posted that you can convert system.img from a cramfs to a ext3 so it will be writable. I have been doing that and trying to get it to work with limited success as you can see.

Anyway thanks for the tips but I have been down that rout long ago 😉

I know about the adb thing but have not gone through all that is needed to get it running on my machine. Apparently I need to install all kinds of java dev stuff to get adb to run. I may have a go at it since I now have a rom that boots somewhat.

Any chance you want to help on that? I can send you my rom.

Bob

Avatar
finless
Stanton, Ca

Contributor
Forum Posts: 604
Member Since:
2011/12/10
sp_UserOfflineSmall Offline

Thanks Received: 2
29
2011/12/19 - 19:14
sp_Permalink sp_Print

josbos said

Keep it up, if it can help take a look into this init.rc

https://github.com/naobsd/cm_device_rockchip_rk2918/blob/master/init.rc

 

Interesting.  Thanks for that!  I am going to compare it to the Arnova init.rc but this is an interesting difference.

mount ext3 mtd@system /system noatime

Not sure what noatime is but I am going to try it now!  Wish me luck.

Bob

Avatar
finless
Stanton, Ca

Contributor
Forum Posts: 604
Member Since:
2011/12/10
sp_UserOfflineSmall Offline

Thanks Received: 2
30
2011/12/19 - 19:41
sp_Permalink sp_Print

OK it's a no go there as well... I am going to now do some camparing in detail of that init.rc and ours.  Maybe there is something else I am missing. However.....

You know and I am totally guessing here without having adb to debug and I am not sure I could or even would know what I am looking at yet.

However I am wondering if maybe it is not in the conversion from cramfs to ext3.  When I make the system.img file I am using a block size of 1024.  I wonder if that is the issue?  Maybe it should be 512 or something else?  I was reading something about nand chips and how important the block size is to them but not what it should be.

So I am going looking at other roms that have system.img as a ext3.  But how do I analyze the file system of those system.img's to determine block size?  A little linux help there please.

 

Bob

Forum Timezone: Europe/Paris

Most Users Ever Online: 749

Currently Online: ygriega
87 Guest(s)

Currently Browsing this Page:
1 Guest(s)


Devices in use: Desktop (73), Phone (15)

Top Posters:

finless: 604

DarthJabba: 551

maikal: 394

mussonero1: 350

alex: 252

damo: 243

DanielVd: 237

Mark06: 222

Newest Members:

ygriega

mhmtdg222

xsevko

jj3111

stoqn62

STOQN222

Forum Stats:

Groups: 10

Forums: 185

Topics: 6037

Posts: 60500

 

Member Stats:

Guest Posters: 43

Members: 262194

Moderators: 5

Admins: 1

Administrators: admin

Moderators: globula_neagra, exelletor, JochenKauz, Oma7144, cracktech


CrewRKTablets moderators: JochenKauz and Astralix