yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] guatatiboa:
Hi

I flashed cwm6028-a13-10part-v2.zip, i tried to reboot into recovery pressing volume and power button but it didn´t work so i tried "echo -e 'boot-recovery\0' > /dev/block/nandf; sync" from the terminal Emulator app.

It rebooted into recovery and got stuck. I can´t flash anyrom, mount sd, cache, data, etc. I tried to flash using livesuit and i get this error "Upgrade fails : 0x162 ÉÕÐ´Ê§°Ü2".

I tried even with phoenix card and i get this error :

sprite update error: fail to scan flash infomation

current card sprite failed

now hold the machine.

I can not get out of the cwm recovery and i don´t know whatelse to do, can anybody please help me?

Thanks
[Miscellaneous Android Development] Lannig:
Update to my post above about editing a recovery image

Seems that this tools allows for doing the job on a Windows box: http://xdaforums.com/showthread.php?t=2036528

So a Linux machine is not required.

---------- Post added at 05:18 PM ---------- Previous post was at 05:11 PM ----------

What image did you try to flash, specifically? is this a Livesuit image for your precise tablet model you've obtained from the reseller or manufacturer?

Livesuit can be moody at times. Try on a different computer. Your best bet is to use an old trusted Windows XP. Windows 7 is known to cause trouble sometimes and Windows 8 is a no-no.

Flashing a recovery

can not

have corrupted anything that would prevent you from reflashing using Livesuit. The FEL code that handles flashing from Livesuit is burnt into the SOC, so it can't be overwritten (by us mere mortals anyway). Keep trying, provided that you have the correct image, of course.

Try googling "livesuit error 0x162" too. It's a common error, you may find useful hints.
[Miscellaneous Android Development] guatatiboa:
Thanks for the hints. I´ve tried to flash a lot of img, it´s a generic chinese tablet with no brand so i had to google, i found several img for tablets with this hardware but not a single one seems to work, i wanted to try with cm but since i needed to flash it by recovery i can not. It´s a Yeahpad A13 or Q88.

Regarding the livesuit error, i googled it in the first place, i found people who solved flashing the right img and some other that just didn´t, but nothing useful. I´ll try on an xp computer but the tablet does not even get in cwm now, i think i have a nice paperweight:laugh:
[Miscellaneous Android Development] s-android:
a10,part 10

after flashing the correct recovery (even another one),it says cant mount anything (in cwm)
[Miscellaneous Android Development] Lannig:
I've managed to use the A10 variant of this CWM Recovery on another one of my tablets.

It works fine apart from the buttons. The vol+ button goes up, the vol- button selects, so does the power button. Anyway CWM menus are well-thought so they can be navigated in one direction only :)

I know that the keycode assignments are hardcoded into the ./sbin/recovery image (aren't they?), so I was wondering if there's any way to patch the binary?
[Miscellaneous Android Development] puma99dk|:
now i have tired this firmware too to see if i can get my software bricked tablet op and run and i can't :(

this firmware here:

A13_MID_nuclear_pfdq88c-eng-IMM76D-Factory_Image_[TechKnowForum.net].img @ 254img

i just get this error:

Livesuit: Upgrade fails : 0x162 ÉÕÐ´Ê§°Ü2

and if i try another firmware i found in this thread called ME-110_Android_4.1.1_JB-20130406.img @ 669mb, when that one is loaded live suit is as dead and dead it self :(

so i could really use some help here.
[Miscellaneous Android Development] ravsss:
Hi,

I played with my tablet and of course somthing goes wrong, and now my tablet still hanging on android logo. Becouse i have no idea what brand it is, and what manufacture... i've opened tablet to see what is inside (speaker lost :) :) ) but i have noticed that this is allwiner a10 chipset. So I started diging how to back to life my tablet and first what i have to do is flash cwm on my tablet. When i connect my tablet to pc (is hangin on android logo) i still can push file over adb to it, and use adb shell, so i've tried push difrent version of cwm on to tablet and try to run cwm recovery but... all the time after vol+ plus power give me screen with exclemation mark.

here is output from my console

recovery.img

reboot-recovery.sh

install-recovery.sh

# sh install-recovery.

sh install-recovery.sh

-- CWM-based Recovery

-- Installation comple

# sh reboot-recovery.s

sh reboot-recovery.sh

why i still can't run cwm recovery and put some rom on my tablet ?? Any ideas for help ?? All the time exclamation mark and no cwm :(

thanks,

ras
[Miscellaneous Android Development] dubbz82:
Thanks, in case anyone's interested, this works awesomely on the mach trio 4.3" stealth lite "tablet"
[Miscellaneous Android Development] teekex:
Works great on MyTab 7" inch (LINK)

root@android:/ # cat /proc/cpuinfo
Processor	: ARMv7 Processor rev 2 (v7l)
BogoMIPS	: 1001.88
Features	: swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x3
CPU part	: 0xc08
CPU revision	: 2

Hardware	: sun5i
Revision	: a13b

root@android:/ # cat /proc/partitions
major minor #blocks name

93 0 26384 nanda
93 8 16384 nandb
93 16 32768 nandc
93 24 524288 nandd
93 32 1228800 nande
93 40 16384 nandf
93 48 32768 nandg
93 56 262144 nandh
93 64 262144 nandi
93 72 1472752 nandj
[Miscellaneous Android Development] Shawhifox:
It doesn't work for me :(

My last NAND entry was nandj, CPU A13 sun5i so I installed the CWM for A13-10. After installing CWM the tablet only boots into the recovery with these lines at the lower part of the screen:

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 can access to the sdcard and flash new zip files. I tried to flash cyanogenmod and installs correctly (a part from two errors related to "/recovery/last_install" but still boot directly into the recovery. Also I tried to flash the rest of the A13 CWM (9 and 11) but the result is the same. And with Livesuite all the installs fail at the 5% with a 0x162 error.

Any idea? The "brand" doesn't have any firmware on his website.:rolleyes:

------------

Edit: I tried at least 15 ROMs and Livesuite is incapable of flashing a single one. I can't remove CWM.

-----------

After spending a lot of hours downloading and failing to flash the ROMs, finally found one that worked! I remembered some info about the build.prop, and with this I found a blog with a collection of ROM and data about the Alwinner CPU's. And one of the uploaded files matched the same info (Inet-86VS-REV01) printed into the board.

So if someone has the same tablet don't install CWM! And if you did, here is the link:

http://moveontechnology.com/hugoenchina/?page_id=220

http://dfiles.eu/files/mus464gwg
[Miscellaneous Android Development] sodade21:
i finally was able to install everything.. it boots normaly but the touchscreen does not work at all... nothing i touch is working... my tablet is apollo quicki 728 allwinner a13 i made all the checks before i installed and im positive i did installed the right rom...what can i do?

Also now that i cannot touch the screen i cannot enable the usb storage so basicaly i cannot access cwm!! the button combination does not work for me... so i cannot connect the device with adb shell and use the commands to access the cmw and try another rom or go back to my backup..is there any other solution or thats it,..im screwed? :/

EDIT: i managed to plug a mouse in it. and works....so i can access the CWM. i try the compatibility patches for touch screen but nothing seems to work.... any suggestions to make touch to work?
[Miscellaneous Android Development] AuGmENTor:
So, here's what I'm getting: says it installed. Doesn't bot into it, just goes back into Android recovery. And whay if the last of my nand's ends in "h"?
[Miscellaneous Android Development] DontExist:
this is what i am getting when i try to install from term emu

$su

#mnt/sdcard/install-recovery.sh

and this is the result

sh:mnt/sdcard/install-recovery.sh: cannot execute - permission denied

can anyone tell me if i am doing something wrong?
[Miscellaneous Android Development] Lannig:
Yes, you're typing the command wrongly.

Try:

$ su
# sh /mnt/sdcard/install-recovery.sh
[Miscellaneous Android Development] dolorespark:
If your last partition is "nandh", you have a non-standard partition layout (at least for Android 4.x). Sadly the result is that CWM will get installed into the wrong partition. My guess is that it ended up in the cache partition.

Does the tablet still boot and run normally? If you can get into the stock Recovery, you may want to try using the "wipe cache partition" option.
[Miscellaneous Android Development] AuGmENTor:
Yes, it still boots, and I can still boot into the recovery partition. I'll try that next.
[Miscellaneous Android Development] dolorespark:
Possible Reason for Install Failures

While CWM installs without problems for most users, some get these errors when they boot into it:

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

A possible reason may be that your tablet has a non-standard partition layout. As a result, the install script may be putting CWM in the wrong partition, or partitions like /cache may not be where this version of CWM expects them to be.

A typical layout looks like this:

93 0 26384 nanda
93 8 16384 nandb
93 16 32768 nandc
93 24 524288 nandd
93 32 1228800 nande
93 40 16384 nandf
93 48 32768 nandg
93 56 262144 nandh
93 64 262144 nandi
93 72 1472752 nandj

In standard layouts, nandg is the recovery partition and is always(?) 32.768kb; nandh is the cache partition and is usually at least 262,144kb (it could be larger). If the sizes of your tablet's nandg and nandh are significantly different, don't install this version of CWM.

For a good example of a non-standard layout, see the screen shots attached to posting nbr 113 (there, what would normally be in nandb is missing, so all the following partitions are shifted down by 1).
[Miscellaneous Android Development] sim_tcr:
I have a cheap Chinese tablet. Here is the model,

http://szstarfly.en.alibaba.com/prod...t_b_font_.html

I was trying to install CWM on it as per http://xdaforums.com/show....php?t=2189640 and it got soft bricked. If i try to reboot it it is always coming to CWM recovery. Also I see below error messages in CWM

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

It is Allwinner A13 cortex8 processor.

How do I restore it back or Load a working version of ROM to it?

cat /proc/cpuinfo

Processor : ARMv7 Processor rev 2 (v7l)

BogoMIPS : 1001.88

Features : swp half thumb fastmult vfp edsp neon vfpv3

CPU implementer : 0x41

CPU architecture: 7

CPU variant : 0x3

CPU part : 0xc08

CPU revision : 2

Hardware : sun5i

Revision : a13b

Serial : 06c19c6635373030504e59301625428d

root@android:/ # cat /proc/partitions

cat /proc/partitions

major minor #blocks name

93 0 26384 nanda

93 8 16384 nandb

93 16 32768 nandc

93 24 524288 nandd

93 32 1228800 nande

93 40 16384 nandf

93 48 32768 nandg

93 56 262144 nandh

93 64 262144 nandi

93 72 5330160 nandj
[Miscellaneous Android Development] zagi988:
After installing this recovery I got this problem...any ideas?

http://xdaforums.com/showthread.php?p=45820936#post45820936

Tought I'll got bigger support here and more ideas.
[Miscellaneous Android Development] sim_tcr:
Had same issue on my chinese allwinner a13 tab. I tried flashing several rom using livesuit and all of them failed to flash.

Finally went to http://www.manta.com.pl/en/mid705 and downloaded the rom available on that page and flashed it through livesuit. That worked!!.

However screen orientation is messed up, no sound and camera driver.
[Miscellaneous Android Development] fsebentley:
There are several Custom Roms based on that Rom on Techknow.me go have a look, they all support multiple TS and GS combinations

so should accommodate your hardware in most cases.
[Miscellaneous Android Development] Daze7:
hi i have a kocaso m9100 tablet and its Allwinner A13. I flashed the cm_a13_20130828.zip but now my screen nor my wifi works. I didnt flash a patch. How do i know which one is the correct one for my tablet? please respond quickly this is really urgent the tablet is not even my own :/
[Miscellaneous Android Development] dolorespark:
Sorry to hear about your problems, but how does this relate to a thread about CWM? For problems with Allwinner tablets, you probably do better posting at Slatedroid, FreakTab, or TechKnow

Allwinner-based tablets don't support Fastboot (at least, I haven't seen any that do). You typically flash a whole new ROM using LiveSuite.

What are you trying to do: flash CWM Recovery or just flash a new ROM?
[Miscellaneous Android Development] FishFan319:
Whatever gets it working. I'm using Livesuit 1.0.7, can't seem to get it to go after the format option. No>Select Rom> Format>Confirm Format> the bar sits @ 0%. Old version, wrong rom? Been on it all day. Thanks for the reply.
[Miscellaneous Android Development] d3mondroid:
Hi there , I flashed the cwm on my ubislate a13 10 partition tab n now my device is in a recovery bootloop, although the cwm itself works fine except for a few bugs but hw to get out of recovery bootloop, plz help..:mad::(:(:(:(:(:(:(
[Miscellaneous Android Development] Daze7:
Got mines working. http://xdaforums.com/showthread.php?p=46628964#post46628964 click the link to my post.
[Miscellaneous Android Development] keithspg:
wanted to post here. This worked perfectly on my Matricom TABNero. I did struggle to get CM10, but eventually, it all works. Thanks to the dev!

My trials and tribulations with cm10 are here http://xdaforums.com/showpost.php?p=46977501&postcount=429 (pages 43-44 document it)

Keith
[Miscellaneous Android Development] keithspg:
Ok, I am struggling to get my g sensor working and need to revert to stock rom (flashed through livesuit). I saved recovery.img, bootload.img and boot.ing before I flashed anything (from adb shell: cat /dev/block/nandg > recovery.img). I pushed this back, but cannot get livesuit to recognize the tablet. When it goes to into recovery, it shows the dead android and no text/menu to select from. I can still boot to CM10, but want to flash back to stock. Where should I put the bootload and boot images, or do I need other images to get original recovery to work?

Keith
[Miscellaneous Android Development] rashidkn:
i have same problem!!!! ... recovery bootloop ...but i cannot mount any one of my tab partitions... i have allwiner a13 with 10 partition and flashed a13-10partv2

pleeeeeeease help to get out of recovery...

edit : a13 with 10 partition go here ... :

http://xdaforums.com/showpost.php?p=43509911&postcount=6

dont download first page file :
[Miscellaneous Android Development] polabai:
HI Friends,

I would like to give my contribution to the solution (in my case) concerning the question "E: can not mount / cache / recovery / command ..." and so on.

Here are two screenshots from my A13b where you can see the schema of my partitions and the screen of the recovery.

After several days in which I could not solve the problem I experienced a trivial solution, directly from the recovery I selected wipe cache and the error has disappeared!

I hope I was helpful to someone.
[Miscellaneous Android Development] Swagg422:
I also have a a13b after wiping cache did the device finally boot normally?
[Miscellaneous Android Development] polabai:
I do not know man but you can try, anyway wiping the cache will have only a slower first start (because the cache is empty) but is not a destructive operation.

However if your device does not start I do not think it's just a problem of cache !

Good luck,

Paola.
[Miscellaneous Android Development] keithspg:
I have one of these cheap tablets and have been playing around with it. Turns out the ROM I had did not work completely and I had to spend some time to research how to 'get it back'. On reading,A13 CWM FAQ

they note that the bootloader image is not backed up. Can this be added to the CWM for this tablet so that it can be used instead of the allwinner recovery to back up ROMS completely? Has anyone here looked at this?

Keith
[Miscellaneous Android Development] sebr:
I also stuck in recovery bootloop. I picked up the correct zip (A13, 11 partitions) and flashed. Now it keeps booting into CWM and I cant get out of it. Help please!!!
[Miscellaneous Android Development] michmill:
Bootloop?

+1. Any help is greatly appreciated!
[Miscellaneous Android Development] wbrambley:
Only way I know is to flash your original ROM using live suite. It will revert the recovery to stock.
[Miscellaneous Android Development] behtash:
hi

i have this problem bootloping cwm and cant exit it ?

my tablet allwinner a10 with 10 partion

cat /proc/partitions

major minor #blocks name

93 0 32768 nanda

93 8 16384 nandb

93 16 32768 nandc

93 24 1048576 nandd

93 32 1048576 nande

93 40 16384 nandf

93 48 32768 nandg

93 56 262144 nandh

93 64 262144 nandi

93 72 1122304 nandj

....

cat /proc/cpuinfo

Processor : ARMv7 Processor rev 2 (v7l)

BogoMIPS : 59.63

Features : swp half thumb fastmult vfp edsp neon vfpv3

CPU implementer : 0x41

CPU architecture: 7

CPU variant : 0x3

CPU part : 0xc08

CPU revision : 2

Hardware : sun4i

Revision : 0000

Serial : 088393d0313930305050473916254204

not any way??

i cant find and flash stock fw
[Miscellaneous Android Development] nayrix101:
what command did you use in installing CWM via adb?
[Miscellaneous Android Development] wbrambley:
What you can do then is flash ROMs and or recoveries via livesuite until you find one that suits your hardware. Knowing things like your touchscreen and orientation sensor are an advantage.There are CM ROMs that have driver packs available for different hardware. But the recoveries that flash with them may not be 100% working for you.
[Miscellaneous Android Development] watusi:
this program compatible without hardware button tablet?thanks
[Miscellaneous Android Development] javacom:
thank you

thanks bro.........
[Miscellaneous Android Development] hybernation:
I have the same problem.i installed a13-10part zip file. now when i try to reboot, boots into the recovery mode. Someone please help.
[Miscellaneous Android Development] Herc08:
I would like to know the same thing...I only have a power button
[Miscellaneous Android Development] arusiasotto:
If we are having this issue with mounting because of a non-standard partioning scheme, is there anyway we can tailor our own copy of CWM to coincide with the one we have?
[Miscellaneous Android Development] hybernation:
same question here.
[Miscellaneous Android Development] emobog:
Machine: sun5i, boots into the recovery mode

My tablet is softwinerevb,Machine: sun5i,ARMv7 Processor [413fc082] revision 2 (ARMv7), installed a13-10part zip file. now when i try to reboot, boots into the recovery mode CWM v.6.0.1.2
[Miscellaneous Android Development] mara-:
Hi,

I have a Prestigio 5197D tablet. These are the specs:

Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 1001.88
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2

Hardware : sun4i
Revision : 0000
Serial : 09c1a35f5052484880728850162367c7

And this is the partition info:

major minor #blocks name

93 0 16384 nanda
93 8 2048 nandb
93 16 32768 nandc
93 24 393216 nandd
93 32 1048576 nande
93 40 1024 nandf
93 48 32768 nandg
93 56 261120 nandh
93 64 1024 nandi
93 72 13774848 nandj
93 73 13773824 nandj1

So, would cwm6028-a10-10part-v2.zip work for me?
[Miscellaneous Android Development] jmar8124:
heeelllpppp plz!!!! :(

Hi guys I have this tablet its the arm7 1Ghz version allwinner, its having problems with booting and its stuck on the boot screen I can not find the stock img to reflash it and I can't enter recovery properly as it will enter recovery by pressing volume + and power and iv tried it the other way around but no luck it just displays an android man with a panel open on his stomach and nothing else their is absolutely no option to factory reset, Nothing other than the recovery android symbol

Any help would be sweet!!! Cheers guys ;-p
[Miscellaneous Android Development] vinayakmt:
CWM bootloop

I think CWM bootloop is caused when the recovery is installed via recovery .On my previous device I insalled it via recvoery and got a bootloop while on a very similar device it worked when I installed via adb.
[Miscellaneous Android Development] hasan291:
I used the running from system method

then i turned it off to boot to recovery using vol+ and power, but nothing

Then i tried yanking the power button many times, and it turned on but gets stuck on android logo

So i need to boot to cwm but how

I have the a13 with 10 partitons

Any help is much needed thanks
[Miscellaneous Android Development] silentarts:
Stress! sun7i

I did this on mine and it says Hardware: sun7i...any idea of which version I can try?

Thanks!
[Miscellaneous Android Development] revanescence:
I think is allwinner a31 but im not sure that you have

Envoyé de mon SM-T310 en utilisant Tapatalk
[Miscellaneous Android Development] silentarts:
Thanks

I checked it and it said A20 sun7i

Thanks!

:cool:
[Miscellaneous Android Development] FaIzaL3040:
Hi i see u have same tablet like me..see attchment for my tab...2,3 days ago i finally revive back my dead tablet after do a lot of research and a lot of trying...

firmware u need to download :-

A13 MID nuclear pdfq88c-eng-IMM76D.img

just flash it with livesuit and follow their instruction ...then u will be fine..
[Miscellaneous Android Development] evilmastr:
Installed cwm6028-a13-10part-v2 according to instructions. Installation was successful and I can boot into CWM.

I can't mount any sd-card however. Neither sdcard nor sd-ext works!

I've attached screenshot and some info.

cat /proc/partitions
major minor #blocks name

93 0 16384 nanda
93 8 16384 nandb
93 16 32768 nandc
93 24 409600 nandd
93 32 1048576 nande
93 40 16384 nandf
93 48 32768 nandg
93 56 262144 nandh
93 64 262144 nandi
93 72 1753088 nandj

Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 1001.88
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2

Hardware : sun5i
Revision : a13b
Serial : lotsofnumbers
[Miscellaneous Android Development] Miwer:
Solved (kinda) my tablet stuck in CWM boot loop

Yeah - I had this problem with my A13 tablet as well. After flashing the the CWM from this thread, I got the same messages as you.

As someone else already stated, there's currently no way (that I know of) to get out of this, besides flashing a LiveSuit image (with format option), thus wiping your tablet. :(

So I did that... only I found that the livesuit image I used did NOT flash a new recovery image (CWM was still in nandg partition), and if I accidentally went into recovery, I was stuck again, forced to flash the livesuit image again. :eek:

So I found this other thread, where user bonfirer in post #6 posts his/her updated cwm image to install into nandg - this one have a newer nand.ko file that don't have the problem of not correctly initializing the nand memory. :good:

This alternate CWM works on my A13 tablet. I can now use CWM and mount partitions and such (haven't tested other functions), and it will now reboot system properly, not being stuck in CWM - fantastic! :victory:

Oh well... lesson learned; Don't flash anything, without at least having a full dump of the original flash content (which I didn't). Now I only have to find a proper LiveSuit image where everything works (touch screen, wifi, sensors and such).

... but at least my CWM don't lock up my tablet anymore. :D