Forum switched to read-only as of 2020/06/01
|Latest product reviews|
Just a wee warning against using an app called Quickboot - it allows the creation of desktop shortcuts for shutdown, reboot etc. On the Arnova it doesn't seem to shutdown cleanly and the tablet always seems to need to do a screen recalibration when it restarts. It's a shame because it works very well on my phone.
Break out a hex calculator unless your good at doing hex math in your head. I will teach you how the parameter file works.
Here is an example line from mine
So the first number before the @ is the size of the partition. The number after the @ is the offset.
So in the above example recovery is 4000 long and starts at offset A000. Now look at the next line which is backup. To set backups offset properly you would add the size of recovery (4000) and add it to recovery's offset of A000
So A000+4000 = E000 As you can see that is the offset for backup. Now if we look at the next one in the line Cache, it's offset is 90000. We took the length of backup 82000 and added it to backups offset. E000+82000=90000 and that becomes cache's offset. Make sense?
Now if you make a change to say recovery and make it larger, then you have to recalculate ALL the offsets that follow it. You cant just do the next one in the line. You have to adjust all offsets to the end of the paramter file.
By the way I noticed other rom parameter files and it appears the order can vary. For instance the stock 10 G2 had system after recovery. The T760 had system after Kpanic. I tried it both ways and the firmware still worked but just in case, I would leave them in the order your stock firmware came. That way if you have issues with your firmware working, you know it's not because you changed the order of things.
Hope that helps!
Hi the CF is great but i have run into a problem when i came to shut down the device. When i plug the charger in to turn it on again it always boots into recovery mode (i can tell because it is always picked up by the usb). i then tried to reinstall the official FW but now the device does not even boot up for the first time, it just simply goes into recovery mode (black screen, green charger light).
I can still use the rockchip batch tool to get the firmware onto the device and it does seem to do something as the usb disconnects, but when i come to restart it (unplug the power and plug back in) it just goes back into recovery mode again!
Have i completely bricked the device or is there some glimmer of hope?
Any help would be appreciated and i had lots of fun using the CFW before this!
Hatchy90, sounds wierd man... This unit is almost impossible to permanently brick. You should always be able to flash the stock firmware with RK Batch tool and have it come back. I have bricked mine more times that I care to count! So I am going to assume you may have possibly had some kind of hardware failure 🙁
Uloga, I doubt that issue is a firmware issue. I have read a few posts were people had problems when they let the battery get to low and it shuts down. The issue I mostly read about was inability after that to fully charge. So not sure what to tell you on this one but I bet if you went back to the stock FW this issue would be the same. Just a guess but maybe the SD Card is not getting unmounted propely when it turns off due to low power and now it has a corrupt file system? Just a guess?
Very interested in your work. I want to do the same ROM for AN8G2.
There are 2 questions.
1. Do I understand correctly that the /system in your ROM in a format as ext3, and you do it?
2. What format system.img and what it can edit?
China phone: Star A5000 => Star N8000
Tablets: Archos 7C HT - Android 2.2.1 my custom ROM => ARNOVA 8G2 8Gb capactive, s_MorkaMod JB 1.2
On the 10 G2 /system was cramfs. I converted it to EXT3. However taking apart boot.img took some work because of a header they apply to the front and back and MD5 checksum.
Read this post there how I learned to take it apart so I could edit init.rc
thanks for the replys, it turned out that there was almost definitely a hardware failure causing (i assume) the checksum on boot to fail and therefore forcing it into recovery mode!
Exchanged and now up and working again with CFW 1.1, just trying to get android market working but arctools 0.6 seems to have trouble with rooted install, not that im slagging it off, its a great app and thanks for taking the time to create it! but if theres anything that can be done, is arctools 0.57 available somewhere?
Most Users Ever Online: 749
Currently Online: lesfurets
Currently Browsing this Page:
Devices in use: Desktop (72), Phone (18)
Guest Posters: 43
Moderators: globula_neagra, exelletor, JochenKauz, Oma7144, cracktech