Forum switched to read-only as of 2020/06/01
|Latest product reviews|
Thanks p1ceus! OK here is a rom file I created with ONLY 2 changes. Boot.img was changed and in it I edited init.rc to this; I commented out the cramfs mount and added the ext3 mount.
aaa I see now, I read that post in the morning and thought I see you uploaded only system.img 😀
anyway, I flashed you ROM and its stucked on the ARNOVA logo. It seems you forget to enable debuging in build.prop, so I can only see mounted drives, no adb :/
OK new rom with default.prop edit to enable the following
OTHERS! THIS WILL BRICK YOUR ARNOVA!
I removed the other firmware but names this update1.img to keep track.
OK finless...strange thing just happened 🙂 I flashed your FW, and do logcat to device and only this line is shown:
--------- beginning of /dev/log/main
I/DEBUG ( 58): debuggerd: Sep 6 2011 21:48:01
I didn't see this anytime I did logcat on my builds...for me it seems that it didnt even try to do something...it just hang right after the boot :/
EDIT: just tried to go into recovery mode (nothing happened just arnova logo on the display) and this message appeared in logcat:
- exec '/system/bin/sh' failed: No such file or directory 2 -
Well as I suspected it is not mounting the ext3 system.img. The question is why?
That has been plaguing me the entire time. Wendal said in late November his better way was to convert system to ext3 and mount it. He has yet to come back to anyone saying it worked or provided a rom even for the T760 he was providing roms for before. So something some where wont let us mount system as a ext3. Does adb allow you to see mounted images and what not?
If you take apart my update.img you will see you can mount system.img as a ext3 in linux.
Yes I saw that in that rom and looked at everything I could to see any other changes. I have tried that extact mount command and many others I have seen in other roms. They all do the same thing hang on Arnova logo then after a bit you get a dong that a usb device is connected.
Maybe it's how I am converting to ext3 format or something?
I tried to load that rom and no luck it bricks it. However I was able to flash with the nextbook rom but the screen was upside down and did not work. Alas after analyzing that rom system.img is also a cramfs system. I am going to poke around with the t760 a little more.
FYI the other RK tool called RKAndroid Tool V1.29 is awesome! It allows you to flash specific images so you dont have to build an entire rom. You can flash just say system.img or boot.img etc. So I am going to try some ideas but honestly.... I am about to give up 🙁
OK I was able to flash the telecast T760 V3.00 using the RKAndroidtool 1.29. Unlike a update.img where Arnova says "Invalid rom file" this force flashes it. Guess what it boots! But the touch screen doesnt work etc obviously due to the hardware differences.
OK this is promsing! Now to look at files and see whats going on! FYI system.img is a ext3 file system. I was just able to mount in in linux!
Back to work!
YES! I got it baby!!!!!! DANCING IN THE STREETS!
So I used the RKAndroid tool and flashed the Arnova with my system.img and my kernal.img. I used the T760's boot.img, misc, recovery. It's up! and wow is it FAST!
Storage setting reports 2.55GB nand space and 486mb internal storage. Way more storage than the stock Arnova firmware. So I think Arnova needs to fix that myself.
OK now to edit init.rc to make /system RW.
stay tuned progress has been made!
UPDATE! SUCCESS! We are rooted baby!
All my work was FINE! The entire time it was the Wendal tool. When it packs an update.img it is not packing based on the sizes and offsets in the parameter file or at least not properly. So when I converted system to ext3 thus making system.img 132KB instead of 67KB it was getting bashed by the other .imgs as they were getting packed into the update.img. Unbelieveable.
Admin you gave me that tip and I hand edit the parameter file to attempt to make more room for system. It didnt work. The reason was the Wendal tool was not using it right! The ONLY file I am now using from the T760 is the parameter file. Again I am flashing the system with the RKAndroid tool not making a update.img with the Wendas tool. So I have yet to make an update.img. I will have to use the RK29 SDK tools to do that not the Wendal tool.
RkAndroid tool was a savior! It allowed me to one by one replace .img's untill I found which one was causing the problem.
So that was the hang up all along! Wendals tool 🙁 SOrry Wendal but thats is for sure wht was causing my problems making an update.img
So we are on our way! Give me some more time to clean up and see if I can make an update.img properly.
ROCKIN in the rockchip house baby! FULLY ROOTED and in control of our destiny now 🙂
Admin, you were correct the parameter file controls how much space is available for internal memory taking away from NAND memory. You just have to calculate the offsets correctly! Right now I have the rom set for 460mb. I can increase that even more! So what is everyone thinking on how large that should be? Maybe a 1gig?
Never mind! We cant go higher. Seems T760 got it right and allocated the memory to the max already. Arnova did not. So the most I can set internal memory to is about 460mb. Any higher and it wont boot.
So as Rosana Rosanadana use to say... NEVER MIND 😉
On to more... expect a fully rooted rom tomorrow sometime. I am doing more looking to make sure everything is cool and as close to Arnova capabilities as possible.
Amazing work finless,great to see you got working !
Looking forward checking this new firmware
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.
Going to bed now.... Here is the bummer.
I cannot seem to make a update.img that works even using the RK tools or Wendals tool. So it turns out this is not a Wendal tool issue. It looks like its the AFPtool (comes with the RK29 kit) issue. The stock RK29 tools and Wendals tool uses the RK29 AFPtool to pack the update.img. When thats done then the loader is handled and a MD5 checksum and the final update.img if finished.
Alas, the update.img hangs just like before. However if I flash using the RKAndroid tool 1.29 using all the same files, no issues. So to me it appears the AFPtool will not pack this update using the edited boot.img and system.img.
I think the issue is the boot.img when it is repacked is not 100% correct. Remember I am using some tips I read on how to unpack and repack the boot.img. Anyway I think the repacked boot.img and the AFPtool is having some compatability issues. I remember a few days ago I read about boot.img having a footer on it and people said it was not needed. I do not believe I am rebuilding that footer and it is missing thus screwing up AFPtool's ability to repack a proper update.img.
Anyway I will work on this more but it may be my rom comes out with having to use the RKAndroid tool which means people will have to install the drivers to get into "flash" mode. My thoughts are so what! as they should have the drivers installed anyway incase they need to recover! Look how many posts are about just that! A bad flash and having trouble getting the drivers installed to go into "flash" mode. Maybe first having the drivers installed and working before you update will save some people some grief if they need to recover.
Well it will be what it will be but I will try to make a update.img that works so people that are lazy don't have to worry about drivers 😉 No gaurentees but I will try.
Man that's awesome 😉 You're the man! I was using Wendals tools all the time and do not use this tool (I guess I was just too lazy to put all .img files into it :)) ) I will try flash with that tool too and see what results I get.
Question, are you using SDK 2.1 FW from T760?
Also, if you have space on your server, do you think it will be possible to upload your images so I and maybe admin can test them too? More heads know more 🙂
Most Users Ever Online: 749
Currently Browsing this Page:
Devices in use: Desktop (87), Phone (18), Tablet (1)
Guest Posters: 43
Moderators: globula_neagra, exelletor, JochenKauz, Oma7144, cracktech