yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Tataarujin:
Hi there.

I made newest CWM recovery for devices with nonstandart button mapping (where vol+ is select and vol- is cursor down), originally was made for mine tablet only, it will also suit to other problems. Buttons mapping is fixed.

But there is problem. This recovery won't pass to boot system, instead of this, it will boot into itself. It can't mount inner partitions, like nanda, nandb and so on. I don't know how to fix it, I had no experience with this stuff. If anybody knows how to fix it, tell me or do it by yourself.

Recovery is in attachment.
[Miscellaneous Android Development] Artago:
I'm getting cache errors. On reboot it goes to CWM. Any advice for me? Thanks
[Miscellaneous Android Development] Saife El:
hi [MENTION=5094650]dolorespark[/MENTION] can you please help me I installed your recovery with Allwinner A10 and 10 partitions, after I check it in adb shell, and I can't access to recovery mode it shows a foto of a droid, I tried rebooting from rom manager app, and from the power and Vol+ .. but nothing works .. please help me I need this recovery very much, you can check the foto in the atachments.

thank you vey much
[Miscellaneous Android Development] dolorespark:
The image of the droid on its side comes from the stock recovery - it doesn't exist in CWM. That means that CWM was not installed. Follow the instructions in the original post for installing CWM manually from a running system.
[Miscellaneous Android Development] anancr:
I flashed this one cwm6028-a10-11part-v2.zip, because my tablet is like this

and I could boot into the cmw recovery, but couldn't mount anypartition. and then I couldn't go out of the recovery, had to flash stock rom with livesuit.
[Miscellaneous Android Development] ker_:
thanks, work perfectly on mediacom 736i SmartPad. (allwinner a10)

i can't boot directly into recovery from a powered off state (no key combination works)

i get it only from reboot menu.
[Miscellaneous Android Development] defiant07:
[MENTION=5094650]dolorespark[/MENTION] thanks again this version of cwm, it is a real lifesaver and works perfectly, but I have a request - I was wondering if it was possible for you to incorporate a touchscreen driver into the recovery images so as to allow for the use of AROMA File Manger and Installer?
[Miscellaneous Android Development] fsebentley:
[MENTION=5094650]dolorespark[/MENTION]

I have used the Provided CWM's and recommended to many others requesting support on working CWM for A13's and

for the most part they have been flawless as long as directions are followed.

I have now run across an instance where this no longer holds true, I recently aquired a JB 4.2.2 Rom and customized it

and had a difficulty while attempting to use the 10part CWM, it gave errors with mounting /cache and /emmc. In the end

after much research I had to modify it in order to get proper operation. Essentially I had to change the recovery.fstab to

mount the /emmc to nandi the actual /databk partition, in the normal CWM's you prodive the /emmc is mounted to nandj

or the sdcard partition.

My question is have you any idea why this might be so ? In my research I could not find any reference to why the CWM's

mount the /emmc to the sdcard partition. (in the case of the 10 part nandj) And as I do not know the internals of CWM that

well I cannot explain to users of my Rom why the Normal 10 Part one does not work.

There are some Utilities that leverage the mount of /emmc to /sdcard actual partition for backup and restore functions and I

would like to be able to understand why the normal way may not work on these newer JB firmwares and whether it will be

a common issue with JB 4.2.2 or isolated to this particular Version

This issue was present in the Rom with the unaltered Factory Image as well so was not related to the Modifications made.

Here are links to both the Recovery image as modified:

http://www.4shared.com/file/v81JS9wK/recovery.html

and the Rom concerned:

http://www.4shared.com/archive/ZJnZpCyn/CookedRom_422_v13aaimg.html

Further testing has shown that the difference is Not due to the recovery.fstab settings, although the ones I used worked

they were not the issue. The issue it seems would have to be the drivers and kernel used in the CWM 10 part vs

the ones used in the JB 4.2.2 Rom. Apparently whatever partitioning scheme is used in this new version is not properly addressed or readable using the CWM 10 part for A13 available here. Once madded with drivers and Kernel from the

Target JB 4.2.2 Rom it worked fine.

Further testing has proven that the recovery.fstab had nothing to do with the problem, it turns out it was strictly the drivers used particularly the nand.ko and kernel. With only those changes the CWM works fine in its original form.
[Miscellaneous Android Development] dolorespark:
That's what I was hoping to do when I built it but then I discovered that the touchscreen code appears to be proprietary. It wasn't in the CM10 repo or anywhere else I looked.

As part of the CM infrastructure, Koush has a page somewhere on the CM site that builds CWM on demand for your device (sorta) and lets you specify the touchscreen version if you want. I tried it and wasn't impressed:

- none of the hardware buttons worked because there was no way to specify key mappings

- I could only see 3 menu entries at a time (out of perhaps 7) because the touch version uses an extra-large font

- the scrolling was really clunky because it lacked the sophisticated ergonomics you've come to expect; instead of scrolling smoothly, the entries went ker-plunk, ker-plunk, ker-plunk.

Regardless, there's another problem with building a touch version of CWM for these no-name Chinese tablets: there are probably 30 different touchscreen controllers in use, each requiring a different driver. Sure, you could release a version with the 5 or 6 most common drivers and satisfy 35% of the users, but then there'd be a never-ending stream of postings like "it don't work" (sic) or "can you build a version for my CrapTab-1000?" (without any mention of what driver that tablet uses). It's a strong disincentive to even try.
[Miscellaneous Android Development] Sine.:
Ask [MENTION=4666971]Phil3759[/MENTION], he may help you with his GUI version of CWM6, as he explained here :)
[Miscellaneous Android Development] defiant07:
Makes good sense, I see your point and totally understand. Too bad though, aroma file manager would be a handy tool. Thanks again for all your labours, I really do appreciate it...keep up the good work :highfive::laugh:!
[Miscellaneous Android Development] Saife El:
+1 the same here
[Miscellaneous Android Development] diogo.c:
It is possible to use this CWM with a usb mouse?

I like to use it in my A10 tv box but don't have hardware keys so the only way to use cwm is with a usb mouse/keyboard.

Thanks
[Miscellaneous Android Development] 215Aphillyated:
Im currious to know what happens if the wrong recovery is flashed....Im stuck in recovery...and its a A13b mid tablet(ebay)model..any help is appreciated
[Miscellaneous Android Development] StonedYoda:
I'm also stuck at the 1st boot screen and I've tried reset but nothing works. I was able to get into recovery once and all I did was wipe battery stats then tried to reboot back into recovery but now I get nothing. I'm not familiar with adb or anything but I'll donate to anyone who can help me get back to stock or even just able to turn my tablet back on. It's a dragon touch 10 inch.
[Miscellaneous Android Development] 215Aphillyated:
So i found a rom that i flashed and the installation says sucessfull but i am still stock in recovery..., anybody have a sugestion on what to try next???

Sent from AREA CODE 215
[Miscellaneous Android Development] 215Aphillyated:
So will this modded version work on a annpad a13 nandj?im stuck in recovery as well and would like as much help as possible..the tablet is nuthin like my htc one...wich isnt that hard to work with
[Miscellaneous Android Development] whiskerp:
The only CWM which works! :)

I'm running Po_ROM_Pompero_JB_1_0.img (JB 4.1.1) on a NATPC M013RTB (Protab2XXL clone).

This is the *only* CWM recovery I have managed to get working with this firmware (which comes with basic 3e but also with the buttons not mapped properly). I have installed the A10 10-partition version.

I have installed other versions of CWM but the tablet doesn't boot beyond the smiley face screen afterwards.

Thank you!
[Miscellaneous Android Development] 215Aphillyated:
I flashed through livesuit...my problem now is the touch screen is not working and adb is not seeing my device...any sugestions?thanks in advance
[Miscellaneous Android Development] :
Cant boot into android goes straight to cwm and reports cant mount cache recovery last_install cant open cache recovery last_install. Can I push the cache recovery folder to my device cause I can use sideload.
[Miscellaneous Android Development] 215Aphillyated:
I had the same exact.problem.bro.....you have to.download.livesuit.for.windows...change some.pc settings to get the drivers installed...find a working rom.for.your device.and.flash the image with live suit
[Miscellaneous Android Development] :
Already did that and just happen to find jellybean 4.1.1 img that works. Whats strange is I have 2 tablets that are same and cwm flashed fine but other boots into cwm might try installing without sdcard in.
[Miscellaneous Android Development] 215Aphillyated:
Is your touchscreen working also?can you post a link for that download?ive foubd pkent of images for the a13b mid...but none of them were full downloads of the image
[Miscellaneous Android Development] :
Everything works but recovery https://rapidshare.com/#!download|8...|0|1|referer-03AF343C355E2FC307B68D75EFF89F0E
[Miscellaneous Android Development] craigmoly:
Here's a link to the firmware for my a13 mid it may fix your TS , It's worth a shot my friend :)

http://www.filefactory.com/file/6d3...eng-IMM76D-Factory_Image_TechKnowForum_net_7z
[Miscellaneous Android Development] 215Aphillyated:
Do you know the name of the app that flashes img files and also recoveries for our tablets???think its like novotool7..cant seem to find it tho
[Miscellaneous Android Development] craigmoly:
I use livesuit 1.11. here u go :)

Livesuit 1.11.

http://www.4shared.com/rar/s4IVIxGc/livesuitpack_111__a10_and_a13_.html

---------- Post added at 09:39 AM ---------- Previous post was at 09:28 AM ----------

There's a thread on another forum with links to all the a13 firmwares , I had to register and spend some time flashing but I did eventually find one that worked tho without an installed recovery , just find one that works and then follow the instructions on this thread to find which recovery is right for u, eg (sun5i , nanj ) .

I hope u get it sorted soon

Link to firmwares

http://www.techknow.me/forum/index.php?topic=4499.0
[Miscellaneous Android Development] 215Aphillyated:
How do we choose what patches(batches)to use on our tablets?reead through this post and didnt find anything
[Miscellaneous Android Development] cmvcarlos88:
What should I do if recovery doesn't have any button to accept and install recovery? I've tried through terminal and I didn't get it, doesn't find files.

Enviado desde mi w30hd(QuadCore) usando Tapatalk 2
[Miscellaneous Android Development] chemahg7:
Hi, i try this with my tablet and the recovery installs correctly but can't mount the "internal sd" and the sdcard, i have this partitions:

So i install the 10 partitions recovery. The log from the recovery says this:

Also, i try with the other 2 recoverys (9 and 11 partitions) but no one seems to work :(
[Miscellaneous Android Development] inkyadrian:
stuck on bootloader

My Allwinner a31/Colorfly CT132 Q is stuck on the bootloader screen too, after installing from the terminal on the Tablet. I hope I can find a correct recovery.img!
[Miscellaneous Android Development] 215Aphillyated:
My sugestion would be to revert back to stock if possible meaning if you made a back up...as i was stuck for weeks on recovery bootloop till i ised livesuit and flashed a image that works but now camt get the touch screen to function properly...until this recovery is mastered i advise leave it alone
[Miscellaneous Android Development] Simba.7:
Just curious, but I have a Polaroid PMID705. I currently have CWM installed on it, but was wondering how to get into it upon bootup. I only have a HOME and POWER button.
[Miscellaneous Android Development] Half Alive:
Ampe A76 (A 13 )

I can boot into recovery but everything doesn't work, And I can't boot to the system now.

I'm forced to enter the recovery. Will flash the system now.

Thank you for your work.
[Miscellaneous Android Development] n.m.t.u.1986:
hi

i installed recovery but cant't Getting into Recovery by holding vol+ and power button

then i entered this command "echo -e 'boot-recovery\0' > /dev/block/nandf; sync" on terminal emulator and now when i power on tablet it always go into recovery

how could i boot normally my tablet?
[Miscellaneous Android Development] is0l4ted:
both.. Hope it works :fingers-crossed:

Sent from my Micromax A116
[Miscellaneous Android Development] n.m.t.u.1986:
anybody can help?!!

recovery have error on my tablet

E:can't mount /cache/recovery/command
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log

i tried to install this rom http://www.techknow.me/forum/index.php?topic=6182.0 and recovery said installation complete but after reboot tablet goes into recovery again!!!

what i should do?
[Miscellaneous Android Development] fsebentley:
For the Particular Rom You are attempting the OP for that tells you to start with a specific partitioning scheme, Your Factory Rom likely does not have the correct Partitioning for the ROM(it must be a JB 4.1.1 10 part) and even tells you what Base Rom to flash first using the Format

option in Livesuite (referenced image is Faastjb v1 for JB 4.1.1)

If you do the above then install the correct CWM, then flash the CWM Rom according to the OP for it you will have more success but will likely

still need to identify a compatibility patch for your tab's hardware (Method also in the OP and author supports in the post).

Note: CWM is of limited use on these tabs, it cannot flash a Livesuite image and most firmwares are in that format. It Can be used

to install CWM Modifications that are Generic or designed for these Tabs(such as the one you are attempting). It Does not flash or back-up

the bootloader.img This is fine unless you change from ICS or earlier to one of the JB Images. If you install a JB 4.2.2 You are likely to not be

able to use these CWM Images on that JB version. You can modify the provided Images using the kernel and drivers from the JB 4.2.2 stock

recovery and it will work. I have done this for a ROM Mod I released called CookedRom based on JB 4.2.2 it comes with the modified CWM as

part of the Livesuite image. If interested you can have a look in TechKnow.me forums as that is where it is supported.

One more note, although Livesuite has the format option as the not recommended method, that is simply because it assumes you are installing

an Update to the original Firmware, when you are installing a Firmware that is Not an Update then the Format option is almost always the

Preferred flash method in order to accommodate differences in the Partitioning.

I hope that helps.
[Miscellaneous Android Development] nacxo:
Here too, please help!
[Miscellaneous Android Development] lauri_ylonen:
my tablet is cpu a13b

​

and

​

but i do not know how install recovery??
[Miscellaneous Android Development] puma99dk|:
i get this on my Allwinner A13b tablet and i can't flash any rom bcs they don't install, i when i plug it in and wanna use LiveSuitPack to flash the stock rom the drivers don't work, i hope there is a solution out there and i hope someone can help.

i am using Windows 7 SP1 64bit.
[Miscellaneous Android Development] zenxus31:
Help Sire

E:Can't mount /cache/recovery/command

E:Can't mount /cache/recovery/log

E:Can't open /cache/recovery/log

E:Can't mount /cache/recovery/last_log

E:Can't open /cache/recovery/last_log

I have first tryed to do a factory reset which comes up with:

-- Wiping data..

Formatting /data...

E:format_volume: make_extf4fs failed on /dev/block/nande

Formatting /cache...

E:format_volume: failed on /dev/block/nandh

Formatting /sd-ext...

Formatting /sdcard/.android secure...

Data wipe complete.

E:Can't mount /cache/recovery/command

E:Can't mount /cache/recovery/log

E:Can't open /cache/recovery/log

E:Can't mount /cache/recovery/last_log

E:Can't open /cache/recovery/last_log

whenever i am trying to use download mode..it just go to cwm recovery again and again..it cant enter the download mode..how to solve this? i been stuck for 2 days..i need my a13 for my work..please help me :crying::crying:
[Miscellaneous Android Development] idulkoan:
Thanks!

---
[Miscellaneous Android Development] joao2c:
Hi lauri_ylonen. You have nandj, so you have 10 part.... if you processor is a13, so cwm6028-a13-10part-v2.zip is correct for you.
[Miscellaneous Android Development] puma99dk|:
i guess there ain't any solution to my problem so i now of a paper weight :(
[Miscellaneous Android Development] :
Tell me your what you're having trouble with?
[Miscellaneous Android Development] puma99dk|:
and the only way i can get it to look like this is when i reboot from CWM and hold vol. down while connecting the power cable but then Livesuit don't pick it up :(
[Miscellaneous Android Development] :
okay easy fix first make sure you turn off antivirus then have the latest version of livesuit. then uninstall all drivers that go with plug-in devices. then make sure your device is fully powered down don't use CMW to power off. hold volume down then plug USB in volume down does not work hold volume up then plug the device in.
[Miscellaneous Android Development] puma99dk|:
i will try that when i come home, later today.
[Miscellaneous Android Development] puma99dk|:
oki, volume up while putting the usb in got me this, just installed the driver and Livesuit 1.09

but if i start Livesuit after i plugged in the tablet it's not starting up, but if i start it up before plugin in the tablet nuth happens with livesuit :(

but if i use power botton too, i get unknown device, instead of USB DevicE (VID_1f3a_PID_efe8) and if i click System Upgrade it says "No device available!" :(

and i can detect my table like one out of a 100 times.
[Miscellaneous Android Development] puma99dk|:
when i get popup if i wanna format the tablet and click yes double time this happens with LiveSuit V1.09 and all the other versions i tried :(
[Miscellaneous Android Development] :
also make sure you have right firware to flash or it wont work.
[Miscellaneous Android Development] puma99dk|:
i got these 4 to lay, and tried more but if none of them works, i dunno which i should use then :(

Android for A13 allwinner 4.0.4.img @ 306mb

F1-4.1.1-20130319.2.0.6-A721_V4.2.img @ 403mb

F1-20121129.1.1.1-A721_V4.2.img @ 286mb

F1HD-4.1.1-20130319.2.0.6-A721_V4.2.img @ 404mb

is there a way to find the right firmware then out of some numbers on the mainboard or something?
[Miscellaneous Android Development] :
First do this then ill post an img. While still holding down the VOL+ plug usb in press the POWER button at least 10 times while holding voulme
[Miscellaneous Android Development] puma99dk|:
i don't need to touch the power botton for Livesuit to pick up the tablet when i get it detected properly.
[Miscellaneous Android Development] puma99dk|:
when will u post the img?
[Miscellaneous Android Development] Lannig:
Stuck into recovery on Polaroid MIDC407 PR008

Just wanted to share that this CWM Recovery

should not

be installed as is on the Polaroid MIDC407 PR008. The kernel built into the recovery obviously can't access the internal NAND properly if at all, so no partition can be mounted and no action can't be performed whatsoever (and yes, I'm fairly sure I chose the right version for my tablet).

More annoying, it can't reset the "boot to recovery flag" in the misc partition so the tablet now is stuck to booting into recovery.

There is no escape apart from flashing a new image using Livesuit (a dump is useless because the recovery can't restore it).

Since Polaroid doesn't publish Livesuit images for their tablets sold here in Europe, I was lucky enough to find a compatible tablet: the MANTA MID701, sold in Poland, has a firmware available for download that works perfectly. This saved me from a bricked tablet.

I have built my own recovery image since then. using the kernel found in the tablet's original recovert partition and the recovery program executable found in this CWM recovery. With a few tweaks, that eventually lead me to a usable CWM Recovery.
[Miscellaneous Android Development] Swagg422:
how did you create your own version of the CWM im having the same problem. I can boot into my Sanei n91 recovery but cant get CWm to install properly without looping into CWM with no cache
[Miscellaneous Android Development] Lannig:
Well, there are different ways.

Usually I just dump my existing recovery partition using

adb shell dd if=/dev/block/nandg of=/mnt/sdcard/recovery.img

then I submit it to the online CWM Recovery generator at http://builder.clockworkmod.com/

This usually produces a bootable recovery but key assignments are wrong (can't move in the menu and/or can't select items).

What I did in this case is that I have edited the ramdisk in the generated boot image to replace the existing 'recovery' executable by the one taken from this source (or another one).

The process is :

- split the boot image between kernel and ramdisk using the well-known split_bootimg.pl Perl script

- gunzip recovery.img-ramdisk.gz and extract the compressed cpio image that the ramdisk is:

cpio -id <recovery.img-ramdisk

- do whatever file replacement/edition is needed : in this case replace the ./sbin/recovery file

- rebuild the compressed cpio archive, from the root of the extracted ramdisk:

find . -print | cpio -o -H newc | gzip -9 >recovery.img-ramdisk.gz

- rebuild the boot image using the mkbootimg command:

mkbootimg --kernel recovery.img-kernel.gz --ramdisk recovery.img-ramdisk.gz --cmdline 'console=ttyS0,115200 rw init=/init loglevel=8' --base 0x40000000 -o recovery.img.new

Although I've heard that people have been able to do all of this under Windows, I use a Linux box for this job.
[Miscellaneous Android Development] Swagg422:
I only have windows don't think I have room on pc for a Linux box. Would it be possible for me to send you my recovery image and have you fix it. My tablet only has 3 buttons Power Volume + and Volume -. Currently I can only scroll in my recover I can't select with the power button. The select key us mapped for a theoretical hone button that the didn't add to the elite version of my tablet only the vase model has home.
[Miscellaneous Android Development] vinayakmt:
I have the exact same problem and i dint keep a backup of the stock recovery.Please help.
[Miscellaneous Android Development] Swagg422:
You have to flash over a fresh version of your stock rom with livesuites or phoenix usb pro. Which device do you have?
[Miscellaneous Android Development] Lannig:
Do you have the same exact tablet ? (Polaroid MIDC407 PR008)

If not, can't help, sorry.
[Miscellaneous Android Development] vinayakmt:
Brand - g tab

Model P900i

running ics ,800/480,sun5i,11parts

I dont have the stock rom ,nor the Polaroid MIDC407 PR008.

Really tensed ,Cant believe I bricked my tab in a month.
[Miscellaneous Android Development] Swagg422:
I hope you made a back up. If you did search Google for uberizer use that to restore tablet. Or go to techknow.me and see if someone has the same tablet.
[Miscellaneous Android Development] alimooghashang:
thanks

i installed cwm6028-a13-11part-v2.zip but when i want to install update.zip it says cannot mount sdcard

what to do now?