[shelbz]

Would it be possible to port Amon_Ra's custom recovery from the HTC phones over to the aPad? It would make flashing custom roms simpler and you wouldn't need a computer at all to do it.I have no skills regarding such a task but if anyone wants to take a stab at it, the source files are here http://github.com/packetlss

 

[xaueious]

There is a working recovery on the Apad actually. But it lacks volume keys and we can't navigate through it. It only works for updating with update.img files.

 

[shelbz]

Thanks looks like I will learn more about it once mine actually arrives. Should be sometime next week.

 

[fun_]

key assign can be changed in recovery.imgchange three lines in /init.rc. e.g.

setprop KEY_CODE_UP "59" setprop KEY_CODE_DOWN "102" setprop KEY_CODE_ENTER "62"

MENU(59)/HOME(102) act as UP/DOWN, ENDCALL(62 / power button on front panel) act as ENTER.to enter menu mode, don't specify any option (e.g. --wipe_all) to recovery command. at this time I deleted a option in misc.img.

 

[xaueious]

[quote name='fun_;13836]key assign can be changed in recovery.imgchange three lines in /init.rc. e.g.MENU(59)/HOME(102) act as UP/DOWN' date=' ENDCALL(62 / power button on front panel) act as ENTER.to enter menu mode, don't specify any option (e.g. --wipe_all) to recovery command. at this time I deleted a option in misc.img.[/QUOTE'] Um I think I'll give that a shot sometime. What's that about misc.img?

 

[fun_]

misc.img is included in update.img. it will be flashed into 2nd partition of flash.([email protected])it seems to be used to enter recovery mode. once recovery mode is started' date=' 2nd partition is cleared by zero so next reboot will not go recovery mode.default (Apad 0611) misc.img contains following strings,[QUOTE']$ strings misc.imgboot-recoveryrecovery--wipe_all

so all data is wiped automatically, then reboot.if you replace "--wipe_all" with all zero in misc.img and flash it into 2nd part, recovery menu will appear.

 

[xaueious]

Or just 'adb shell reboot recovery'Thanks to naobsd for the keycodesOkay I commented some lines out of the 0611 recovery and have adb working. I also pushed a busybox into sbin: http://www.multiupload.com/7B7OBWEKAIyou should be able to mount file systems in recovery now.

 

[rogerbraun]

Nah, that's too easy ;-)

 

[xaueious]

[quote name='rogerbraun;13907]Nah' date=' that's too easy ;-)[/QUOTE'] Okay it seems like the recovery actually works. I just updated update.img from my sdcard. Not sure if it flashes over the old recovery with this method though.

 

[fun_]

I think "update misc.img", "recovery --reboot", and "adb shell reboot recovery" are same thing.misc.img is required for updater because no shell/adb is running in update mode.I don't have(setup) machine with adb for now, so I need to use misc.img or shell.

Not sure if it flashes over the old recovery with this method though.

I think "which part is updated" is described in update-script but not tested yet.

 

[xaueious]

[quote name='fun_;14068]I think "update misc.img"' date=' "recovery --reboot", and "adb shell reboot recovery" are same thing.misc.img is required for updater because no shell/adb is running in update mode.I don't have(setup) machine with adb for now, so I need to use misc.img or shell. I think "which part is updated" is described in update-script but not tested yet.[/QUOTE'] lol that is leet.

 

[Karlleopold]

I?m a novice obviously, but would very much like to be able to navigate in the system recovery utility. The reason for this is that I have an apad v2 with unresponsive touchscreen after update to fw 6-11, and I would like to test a restore to factory settings. To do this I would have to navigate in the recovery utility, and in order to do this ( if I understand correctly) I would have to remap the buttons/keys in the recovery.img. Is it possible to edit this in a Windows environment. if yes, could you please suggest appropriate software for this. I can easily enter recovery with Droidexplorer and use an otherwise functioning system with screencast.Thanks,

 

[fun_]

[quote name='Karlleopold;14140]Is it possible to edit this in a Windows environment. if yes' date=' could you please suggest appropriate software for this. I can easily enter recovery with Droidexplorer and use an otherwise functioning system with screencast.[/QUOTE']I think cygwin is required to extract/create cramfs image on windows. but I can provide modified recovery.img for you. I'm not sure recovery from backup fixes touchscreen problem.Droid Exploler seems to be GUI for adb.

 

[Karlleopold]

Would be great if you could. Maybe you?re right but I feel that I have to try at least. I find it hard to believe that it?s a hardware issue - several people have described exactly the samescenario when flashing an update, after which we?re stuck at calibration when the apad reboots.Thanks in advance!

I think cygwin is required to extract/create cramfs image on windows. but I can provide modified recovery.img for you. I'm not sure recovery from backup fixes touchscreen problem.Droid Exploler seems to be GUI for adb.

 

[fun_]

here is recovery.imgI think you can reflash old firmware, can't you?this thread may also be useful for you.finally, just FYI, backup partition should have entire update.img file. see package-file in update.img.

 

[Karlleopold]

Thanks! The recovery image works and makes it possible to access and navigate the sys recovery utility, but unfortunately you?re right in that it doesn?t change anything with the touchscreen after restore to factory settings. Still stuck at calibration, which is also impossible to do with mouse. Yes, I?ve also tried to reflash several fw?s (back to 0512) without any change. Frustrating ....

 

[fun_]

[quote name='Karlleopold;14564]Still stuck at calibration' date=' which is also impossible to do with mouse.[/QUOTE']you can skip calibration. see xaueious blog

 

[Karlleopold]

Can?t seem to find a shared_prefs folder in /data/data/com.android.settings/Neither am I able to create this folder. Using DroidExplorer. Something is either wrong with me or my pad ...Update: My slate is a blue LED 7" Rockchip machine, NOT an Apad. My posts in this thread are probably irrelevant, due to this.

 

[Asure]

I should have a dump of firmware 0612 somewhere in the end of next week for this "blue-led Apad device". Hopefully this can make your screen work again.

 

[Asure]

@xaueious: Does this recovery image work as normal ? If i have it flashed, and flash between some firmwares, the wipes do not work it seems.. or i'm missing something somewhere ?