Database Info

[Q][RK2818|Archos 7HTv2] "No Space left on Device" during flash

A little background, I am trying to flash a Honeycomb rom to my Archos 7HTv2. This is a custom rom that I put together. I know that Honeycomb requires much more power than my Archos can give me. I know that it would probably be unusable, but I was curious, and it brought up a problem.
The system.img for the HC rom is ~112mbs, the total update.img is ~123mbs
The system.img for the stock rom is ~51mbs the total update.img is ~54mbs
I first tried to flash it and got a "not enough space" error when flashing the system. I assumed that the stock rom barely fit in the system partition, so I went looking for how to make it bigger.
Flashing on the Archos is by putting an update.img in the SDcard, or by using the "BatchUpgrade" utility from the computer, which copies it to some temp on the device. Then the recovery takes over and installs the rom.
Code:
Writing KERNEL:...
Checking KERNEL:...
Writing BOOT:...
Checking BOOT:...
Writing SYSTEM:...
E:Write failed(No space left on device)
E:Failure at line 16:
write_image PACKAGE:system SYSTEM:
Update failed, please reboot and update again!
Line 16 refers to the update-script file which has the list of Writing & Checking.
When I flash the rom from the computer using "BatchUpgrade" it fails before it can attempt unpacking. It just tells me "FAILURE" and no specifics as to why. Because the img never begins unpacking makes me believe it might be the temp area is not big enough for the .img and the extracted components.
I found this mtd information in the HWDEF file (part of update.img)
Code:
#Format: part_name offset:size
parameter 0x00000000:0x00002000:fh
misc 0x00002000:0x00002000:f
kernel 0x00004000:0x00004000:f
boot 0x00008000:0x00002000:f
recovery 0x0000A000:0x00004000:f
system 0x0000E000:0x00030000:f
backup 0x0003E000:0x0003A000:
cache 0x00078000:0x0003A000:
userdata 0x000B2000:0x00100000:
user 0x001B2000:0xFFFFFFFF:
END
I changed the system and backup partitions to be bigger (the above is stock) but nothing happened. I then found the PARAMETER file which had a similar string of mtd definitions, I updated them as above. Still no luck.
Anyone have any ideas?
Thanks

Do you had any luck?

CWM-based Recovery 6.0.1.5 for A700 (JB compatible)

EDIT: These links are no longer available because some people copy these links to forums with "questionable" contents and some company scrape links from those forums and DMCA them all without actually checking them first. Please use the official CWM from now on. Download the official version at http://www.clockworkmod.com/rommanager.
This image is built via unofficial CM10 source linked here
Download
Recovery image: http://www.mediafire.com/?w707lr78by1bbd6 (MD5: 34a2caff881dfa7faf941cb1d34ec3b8)
Recovery image (touch): http://www.mediafire.com/?ff304ho7h9pbapg (MD5: f9aab0807bb5350c5b69d795906fecb5)
Use fastboot to flash
Code:
fastboot flash recovery recovery-a700-6015.img
Enter recovery via vol down + power or
Code:
adb reboot recovery
Old Download
6.0.14
Recovery image: http://www.mediafire.com/?9g39c74cc1smq10 (MD5: b2688a47f5a754e5374df4f2abd3b445)
Recovery image (touch): http://www.mediafire.com/?gtfmvb6on1ivgrq (MD5: 534f7d73d5a77fcec6ab2c21a8a48a71)
6.0.11 Update 1: http://www.mediafire.com/?o5skj3acsatq633 (MD5: 52b61d78940101d72eab20689d47f2ba)

Congratulations, it unfortunately can not test because I have an A510. Is the recovery from a510/a700 the same? Actually, the tablets are different only in the display, right? Has anybody tried to flash a recovery from an a700 to a A510? Where did you get the two files, especially the fstab?
Thanks!

Thanks, have you fully tested it ? We've had a couple of recos that managed to bricked tablets so far
Edit : you have not tested the wipe ? Those one bricked my A700 so be careful.

Rembold91 said:
Congratulations, it unfortunately can not test because I have an A510. Is the recovery from a510/a700 the same? Actually, the tablets are different only in the display, right? Has anybody tried to flash a recovery from an a700 to a A510? Where did you get the two files, especially the fstab?
Thanks!
Click to expand...
Click to collapse
The boot.img was dumped from my device using dd, recovery.fstab was based on Nexus 7's and modified to suit our device. I'm not sure about the A510 since I don't have one.
paugustin said:
Thanks, have you fully tested it ? We've had a couple of recos that managed to bricked tablets so far
Edit : you have not tested the wipe ? Those one bricked my A700 so be careful.
Click to expand...
Click to collapse
Wipe works both from system and recovery itself.

OK thanks for the info.
Too bad my tablet is still unable to boot

paugustin said:
OK thanks for the info.
Too bad my tablet is still unable to boot
Click to expand...
Click to collapse
Are you able to boot into fastboot? Are you able to boot into recovery using the orientation lock + volume down + power?
EDIT: Oh wait, this device has no way of booting into fastboot without a working system?

pawitp said:
Are you able to boot into fastboot? Are you able to boot into recovery using the orientation lock + volume down + power?
Click to expand...
Click to collapse
Yes fastboot and recovery mode are available. I can flash rom but they won't boot and whenever I use wipe/format on a partition the process will freeze.

paugustin said:
Yes fastboot and recovery mode are available. I can flash rom but they won't boot and whenever I use wipe/format on a partition the process will freeze.
Click to expand...
Click to collapse
Hmm, can you add me on GTalk [email protected]?

Just checking procedure please....
I got the OTA update today to Image version: Acer_AV043_A700_RV07RC06_PA_CUS1 Build: Acer_AV043_A700_1.029.00_PA_CUS1
I had to unlock the bootloader and root again. ***OTA Rootkeeper WILL NOT keep the root! The bootloader is re-written and root removed***
I just downloaded the Recovery.img file and want to be SURE I do this correctly, so please forgive me if I sound "noobish"!
1. Copy Recovery.img to root of SD Card
2. Use ADB Fastboot to get tablet into flashboot mode
3. Once tablet has entered flashboot, Type -fastboot flash recovery recovery.img
4. Process should allow me to enter Recovery mode
Am I correct here? I don't want to brick my tab! I appreciate any input and thanks in advance!

paugustin said:
OK thanks for the info.
Too bad my tablet is still unable to boot
Click to expand...
Click to collapse
Have you tried using nvflash in apx mode ?

Well we don't have a fully working nvflash for tegra 3 with sbk support yet. If you have one I'm interested
Sent from my S300 using xda app-developers app

paugustin said:
Well we don't have a fully working nvflash for tegra 3 with sbk support yet. If you have one I'm interested
Sent from my S300 using xda app-developers app
Click to expand...
Click to collapse
Did you check the a700 service rom? It seems it has the NVFlash support as near as I can tell. Should be the same for the 701. Looks like it has support for the blocks.
I can't do anything with it. Tab is still in for repair. Hope maybe this week,
MD

pawitp said:
Wipe works both from system and recovery itself.
Click to expand...
Click to collapse
Sounds good. However, let me be a little more specific.
The problem with all the previous recoveries happened when you tried to wipe /Data. All the other functions seemed to work well. Seemed to.
1. Recovery backup took longer than usual, especially on a bare stock install.
2. The first time you restore a recovery image, it would take "forever". Usually, it would complete the first time, but Data apps didn't function once the Rom booted. Nor could you download ANY apps. Any additional attempts to do a restore would hang at "formatting data". Once that happened, you basically could not install anything nor restore from a recovery. /Data corrupted.
So the question again, have you tested the /data wipes and formats via CWM? Several times after downloading apps, backups, restores?
Please don't take this the wrong way. We appreciate taking the time developing a workable recovery for the 70x. But the previous attempts caused needless bricked tabs. 1 dev, didn't even own a 70x to test it on and he pushed it out. And the other guy, well, whereabouts unknown, and knowing the previous issues, he also never bothered to check all functions before releasing his version. Claimed "I don't have a need to wipe data".
So please clear this issue, before we get into the flashing portion. You have to understand, some of us, are a little "gun-shy" right now.
Thanks for taking the time to develop a recovery! I hope it works well!
MD

paugustin said:
Well we don't have a fully working nvflash for tegra 3 with sbk support yet. If you have one I'm interested
Sent from my S300 using xda app-developers app
Click to expand...
Click to collapse
I'll take a guess, that if the /data issue is working in the new recovery, and you can get it installed, you may be able to wipe the corrupted /data, and restore your previous recovery backup. If you used a CWM based recovery.
Also, I think I may still have my stock recovery CWM backup from my 701 on my PC (build .015) (I think). But considering it was done with CWM, you may be able to restore it. Might work, might not.
MD

OK I spent some time this morning with pawitp. He was able to make my A700 boot but the /data partition is reduced to 126Meg and if I try to format any partition it will break things again.
So it's a start...
Regarding restore, I have a CWM backup of my system but so far my attempts at restoring it have failed, even with pawitp recovery. The partition is broken so it won't take any data.

paugustin said:
OK I spent some time this morning with pawitp. He was able to make my A700 boot but the /data partition is reduced to 126Meg and if I try to format any partition it will break things again.
So it's a start...
Regarding restore, I have a CWM backup of my system but so far my attempts at restoring it have failed, even with pawitp recovery. The partition is broken so it won't take any data.
Click to expand...
Click to collapse
Well, that's a bit of good news. Similar to the SGS II and their leaked kernel. They had to flash a modified PIT that ignored the corrupted sectors. Lost 2gb in the process, but still a start.
MD

Partitions on the A700
Just to shed some light on the partitions of our new toy.
Maybe it's of use as a reference.
Block devices:
/ # ls -l /dev/block/platform/sdhci-tegra.3/by-name/
lrwxrwxrwx root root 2012-07-24 10:28 AKB -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-07-24 10:28 APP -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-07-24 10:28 CAC -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-07-24 10:28 DE2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-07-24 10:28 FLX -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-07-24 10:28 LNX -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-07-24 10:28 MSC -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-07-24 10:28 SOS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-07-24 10:28 UDA -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-07-24 10:28 USP -> /dev/block/mmcblk0p8
Partition sizes:
/ # cat /proc/partitions
major minor #blocks name
179 0 31260672 mmcblk0
179 1 6144 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 614400 mmcblk0p3
179 4 1253376 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 102400 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 20480 mmcblk0p8
179 9 10240 mmcblk0p9
179 10 29204480 mmcblk0p10
179 32 15558144 mmcblk1
179 33 15558136 mmcblk1p1

Moscow Desire said:
Sounds good. However, let me be a little more specific.
The problem with all the previous recoveries happened when you tried to wipe /Data. All the other functions seemed to work well. Seemed to.
1. Recovery backup took longer than usual, especially on a bare stock install.
2. The first time you restore a recovery image, it would take "forever". Usually, it would complete the first time, but Data apps didn't function once the Rom booted. Nor could you download ANY apps. Any additional attempts to do a restore would hang at "formatting data". Once that happened, you basically could not install anything nor restore from a recovery. /Data corrupted.
So the question again, have you tested the /data wipes and formats via CWM? Several times after downloading apps, backups, restores?
Please don't take this the wrong way. We appreciate taking the time developing a workable recovery for the 70x. But the previous attempts caused needless bricked tabs. 1 dev, didn't even own a 70x to test it on and he pushed it out. And the other guy, well, whereabouts unknown, and knowing the previous issues, he also never bothered to check all functions before releasing his version. Claimed "I don't have a need to wipe data".
So please clear this issue, before we get into the flashing portion. You have to understand, some of us, are a little "gun-shy" right now.
Thanks for taking the time to develop a recovery! I hope it works well!
MD
Click to expand...
Click to collapse
Don't worry, the data partition is never actually formatted because the internal sdcard lies in /data/media. All the recovery does is delete all the files not in /data/media.
Sent from my A700 using xda app-developers app

pawitp said:
Don't worry, the data partition is never actually formatted because the internal sdcard lies in /data/media. All the recovery does is delete all the files not in /data/media.
Sent from my A700 using xda app-developers app
Click to expand...
Click to collapse
Sorry, I meant User Data/Factory Reset (as CWM calls it).
This is why when on the first attempt at restoring a recovery, the downloaded apps would not function. You had the icons, but Force Close on them all. The system apps were fine. Any attempt to restore any previous backup failed (would hang on that partition). Couldn't wipe the partition in CWM after that.
MD

Moscow Desire said:
Sorry, I meant User Data/Factory Reset (as CWM calls it).
This is why when on the first attempt at restoring a recovery, the downloaded apps would not function. You had the icons, but Force Close on them all. The system apps were fine. Any attempt to restore any previous backup failed (would hang on that partition). Couldn't wipe the partition in CWM after that.
MD
Click to expand...
Click to collapse
And that basically clears data. I've tested it, it works (and mentioned it on first page).

No longer able to install ICS, stuck on HC.

I recentlly attempted to update my P6800 from ICS LQ1 to LQ2 via Mobile Odin.
The result was a tablet that would only boot as far as the Samsung Logo and boot chime and would hang there.
Many attempts were made to clear caches, reset data via both stock recovery and CWM versions 5 .5 and even 6 with no change.
Tried using PC Odin to go back to LQ1 and has the same exact results. suspected an error in a partition and used a stock p6800 .pit along with stock LQ1 .tar and still have same problem. Cm9 and 10 gives same results.
However I am able to install stock Honeycomb via PC Odin which seems to work fine except CWM backup is unable to restore a backup and hangs just after starting.
I still suspect a bad partition somewhe but dont see a way of verifying this. Have read many posts both here and in the Galaxy Note forum but none have solution that has worked for me.
Does anyone know if the .pit file actually recreates your partitions? Or does someone have instructions on how I can manually do this via adb shell? Specifically the cache, data and system partitins.
Any help is appreciated.

Try this.
- In HC use Locerra' CWM v5.x
In recovery:
- Clear cache.
- Dalvik.
- Data reset.
- Flash rom: http://www.androidtablets.net/forum/showthread.php?p=223379
- Fix permission.
- Reboot.
If stuck after reboot...boot to cwm recovery again.
- Full wipe.
- Reboot and wait a while.
Hope it help and keep us posted

Astrix Ashburn said:
Try this.
- In HC use Locerra' CWM v5.x
In recovery:
- Clear cache.
- Dalvik.
- Data reset.
- Flash rom: http://www.androidtablets.net/forum/showthread.php?p=223379
- Fix permission.
- Reboot.
If stuck after reboot...boot to cwm recovery again.
- Full wipe.
- Reboot and wait a while.
Hope it help and keep us posted
Click to expand...
Click to collapse
followed above and got non stop rebooting.
wonder if ics uses a different partition structure.

While at recovery do u have testbend?
Sent from my GT-P6800 using xda premium

I faced your situation before, here's what you should do
1 Install official HC 3.2 using PC odin
2 boot in to HC stock recovery
3 factory reset / Data & Cache wipe
4 do full boot into HC till you see your desktop
5 use your PC odin or Mobile odin pro to Install ICS over HC
6 Now you should be good to go.
Note if you can successfully boot into HC then your paritions are good, dont mess with them.

zorbakun said:
I faced your situation before, here's what you should do
1 Install official HC 3.2 using PC odin
2 boot in to HC stock recovery
3 factory reset / Data & Cache wipe
4 do full boot into HC till you see your desktop
5 use your PC odin or Mobile odin pro to Install ICS over HC
6 Now you should be good to go.
Note if you can successfully boot into HC then your paritions are good, dont mess with them.
Click to expand...
Click to collapse
This has been tried several times with the same results each time. Boot loops.
Thats what I don't get, HC works but as soon as ICS is put on I get /Data partition errors. More specifically /data cannot be mounted.

Josvaz said:
While at recovery do u have testbend?
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
Yes , in stock recovery I do. Was not sure what that did.

Looking at my partitions via adb it looks like /dev/block/mmcblk0p10 is empty. Perhaps this is the issue? If so, does anyone know how to recreate?
~ # parted /dev/block/mmcblk0p10
parted /dev/block/mmcblk0p10
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p10
Welcome to GNU Parted! Type 'help' to view a list of co
(parted) print
print
print
Error: /dev/block/mmcblk0p10: unrecognised disk label
(parted) print list
print list
print list
Error: /dev/block/mmcblk0p10: unrecognised disk label
(parted)

kable said:
Looking at my partitions via adb it looks like /dev/block/mmcblk0p10 is empty. Perhaps this is the issue? If so, does anyone know how to recreate?
~ # parted /dev/block/mmcblk0p10
parted /dev/block/mmcblk0p10
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p10
Welcome to GNU Parted! Type 'help' to view a list of co
(parted) print
print
print
Error: /dev/block/mmcblk0p10: unrecognised disk label
(parted) print list
print list
print list
Error: /dev/block/mmcblk0p10: unrecognised disk label
(parted)
Click to expand...
Click to collapse
its look like the /data partition is screwed... try running e2fsck -fDC0 /dev/block/mmcblk0p10 to check the partition...

this is the EXACT problem i was having. here's what i did to fix it*:
disclaimer: i am waiting for HC filefactory slow-*ss download to take another F*CKING hour.... so i have yet to FULLY recover my tab... BUT i think i'm onto something.
i COULD get a full flash from odin with no hanging up...then i corrupted my /data and /system partition... don't ask me how: i knew to stay away from wiping with 3e stock ICS recovery, i used cwm 5.8.1 temporary zip that i flashed from stock recovery, IT messed up everything.... then i started trying to follow androguide.fr's revive from superbrick guide. (will post link later)
after days and days and DAYS of frustration trying to remove and remake /data and /system, /cache eventually corrupted. i was ready to blow my brains out.... just on a whim, without having read any of this stuff, i:
1) flashed the original pit file,
2) flashed ATO-ICS firmware
3) flashed CWM 6.0.1.1
4) wiped /data /factory /dalvik SUCCESSFULLY!!!!
5)....after wiping, e2fsck checking and getting clean partitions with every ICS CM9/10 rom i could find, and STILL getting stuck on the boot animation...
i finally read in a gNote forum that people with this problem were flashing back to GB (original firmware for the Note) and solving their problem, then they could go back to ICS... if you can't i'm SORRY!!! but i'm even just trying to get ANYTHING to boot at this point. YOU'RE POST GIVES ME HOPE!!!!
so try: flashing the original pit file, flash cwm 6.0.1.1, wipe data/factory reset, wipe dalvik cache, reboot and JUST do the e2fsck section of the NOOB friendly guide to recovering your tab from superbrick. --will post link later. that should at LEAST get rid of the corrupt filesystem. e2fsck every partition that you were having trouble with.

zorbakun said:
I faced your situation before, here's what you should do
1 Install official HC 3.2 using PC odin
2 boot in to HC stock recovery
3 factory reset / Data & Cache wipe
4 do full boot into HC till you see your desktop
5 use your PC odin or Mobile odin pro to Install ICS over HC
6 Now you should be good to go.
Note if you can successfully boot into HC then your paritions are good, dont mess with them.
Click to expand...
Click to collapse
Thank you for this, it got me working again. I didnt think to do any wipes after going back to stock HC but it was exactly what it needed.

nutley said:
Thank you for this, it got me working again. I didnt think to do any wipes after going back to stock HC but it was exactly what it needed.
Click to expand...
Click to collapse
You should change your topic by adding ( Resolved ) to it so others know you got it figured out .

Fluxcore said:
You should change your topic by adding ( Resolved ) to it so others know you got it figured out .
Click to expand...
Click to collapse
It's not my topic. Just saying thanks as it sorted my own issue out

[Resolved] Resize recovery partition on Lenovo K30W

I want to increase size of recovery partition on Lenovo K30W so I can flash larger recovery image created for Lenovo A6000. I have devised a way, but I would be grateful if someone could look it over and spot possible flaws.
Here is the current partition table.
Code:
Model: MMC Q8XSAB (sd/mmc)
Disk /dev/block/mmcblk0: 15634268160B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67108864B 134217727B 67108864B fat16 modem
2 134217728B 134742015B 524288B sbl1
3 134742016B 135266303B 524288B sbl1bak
4 135266304B 136314879B 1048576B aboot
5 136314880B 137363455B 1048576B abootbak
6 137363456B 137887743B 524288B rpm
7 137887744B 138412031B 524288B rpmbak
8 138412032B 138936319B 524288B tz
9 138936320B 139460607B 524288B tzbak
10 139460608B 139984895B 524288B hyp
11 139984896B 140509183B 524288B hypbak
12 140509184B 141557759B 1048576B pad
13 141557760B 143130623B 1572864B modemst1
14 143130624B 144703487B 1572864B modemst2
15 144703488B 145752063B 1048576B misc
16 145752064B 145753087B 1024B fsc
17 145753088B 145761279B 8192B ssd
18 145761280B 156247039B 10485760B splash
19 201326592B 201359359B 32768B DDR
20 201359360B 202932223B 1572864B fsg
21 202932224B 202948607B 16384B sec
22 202948608B 219725823B 16777216B boot
23 219725824B 1830338559B 1610612736B ext4 system
24 1830338560B 1863892991B 33554432B ext4 persist
25 1863892992B 1998110719B 134217728B ext4 cache
26 1998110720B 2014887935B 16777216B recovery
27 2014887936B 15634251263B 13619363328B ext4 userdata
Luckily, recovery and data partition are next to each other. Here is the procedure, please tell me if it is viable.
1. Boot into recovery
2. Create nandroid backup of data partition
3. Make sure that data partition is unmounted in recovery
4. Using parted, delete recovery and data partitions, and then recreate them with new sizes
5. Format data partition
6. Make sure that "use rm -rf instead of formatting" is enabled in recovery settings
7. Restore nandroid backup
8. Flash new recovery
9. Reboot
These are the commands I would use:
Code:
adb shell
parted /dev/block/mmcblk0
unit b
rm 27
rm 26
mkpart primary 1998110720 2031665151
mkpart primary 2031665152 15634251263
name 26 recovery
name 27 userdata
quit
mke2fs -t ext4 /dev/block/mmcblk0p27

As there were no replies, I took a risk and went ahead with resizing the partitions. The described procedure worked without problems.

Could you make a guide on how you did this exactly for noobs?
I understand that you posted the steps you used, but i'm not familiar with what you did.
Also, what rom are you using currently?
I got a rom working for this phone, It works well, but is not ideal.
https://forum.xda-developers.com/general/help/k3-note-question-k30w-t3531158

addict1337 said:
Could you make a guide on how you did this exactly for noobs?
I understand that you posted the steps you used, but i'm not familiar with what you did.
Also, what rom are you using currently?
I got a rom working for this phone, It works well, but is not ideal.
https://forum.xda-developers.com/general/help/k3-note-question-k30w-t3531158
Click to expand...
Click to collapse
Well, making an even more detailed guide will take some effort. I'll do it when I find the time.
I am using this ROM: https://forum.xda-developers.com/lenovo-a6000/development/rom-resurrectionremix-5-8-1-t3555184
It's great, but I do have problems with updating it. Hopefully it'll be resolved soon.

Here is a more detailed procedure. However, if you are not familiar with Linux command line and the Android partition layout, I strongly recommend that you stay away from this.
First, you need Android platform tools from here. Download for your platform (I am going to assume Windows) and extract to a folder of your choosing (for example C:\Android).
You also need parted utility, download from here. It's best to extract it to the same folder as Android platform tools.
Next, open Windows command prompt and go to the platform tools folder. The easiest way to do it is to open the folder in Windows Explorer, right click in the empty space while holding shift and choose "Open command window here". Reboot your device in recovery mode and connect it to the computer USB port.
While in recovery, make a backup of your data partition.
Copy the new recovery image to external SD if you have one, or else to internal memory. You can do it using Windows Explorer.
Copy parted utility to the device.
Code:
adb push parted /.
Next, enter device shell.
Code:
adb shell
Make parted executable.
Code:
chmod a+x parted
Start parted utility.
Code:
./parted /dev/block/mmcblk0
Be extremely careful from now on. Every parted command is executed immediately, so if you type something wrong, you could brick your device.
Change size unit to byte.
Code:
unit b
Print your current partition layout. If it's not the same as in my original post, abort now as you'll mess things up.
Code:
p
Remove recovery and data partitions.
Code:
rm 27
rm 26
Recreate partitions with new sizes (recovery is now 32MB instead of previous 16MB).
Code:
mkpart primary 1998110720 2031665151
mkpart primary 2031665152 15634251263
Give partitions the same names as before.
Code:
name 26 recovery
name 27 userdata
Exit parted utility.
Code:
quit
Format the data partition.
Code:
mke2fs -t ext4 /dev/block/mmcblk0p27
Make sure that "use rm -rf instead of formatting" is enabled in recovery settings. This may not be necessary, but I've seen it in some tutorial, and it can't hurt.
Restore data partition from backup.
Flash new recovery using current recovery (go to install and choose "install image").
Reboot and hope for the best.

Thank you very much
I will give it a try.

All worked well, however I am never able to boot into recovery from my phone itself (before i attempted this, and after).
I always need to use my pc/usb to boot into recovery via a batch file.
Even if I install recovery from the recovery I just booted.
Getting into recovery is holding volume up and the power button right?
I installed the software you mentioned, however it is stuck at the bootscreen

addict1337 said:
All worked well, however I am never able to boot into recovery from my phone itself (before i attempted this, and after).
I always need to use my pc/usb to boot into recovery via a batch file.
Even if I install recovery from the recovery I just booted.
Getting into recovery is holding volume up and the power button right?
I installed the software you mentioned, however it is stuck at the bootscreen
Click to expand...
Click to collapse
To get into recovery, you need to keep BOTH up and down volume keys, and then power on. After a few seconds, you can release volume keys.
As far as the ROM is concerned, make sure you wipe data and cache before installing it. That's all I can think of.

CrazyNik said:
To get into recovery, you need to keep BOTH up and down volume keys, and then power on. After a few seconds, you can release volume keys.
As far as the ROM is concerned, make sure you wipe data and cache before installing it. That's all I can think of.
Click to expand...
Click to collapse
Thanks.
I managed to install a CWM recovery for A6000, witch is working fine now (32MB)
I had problems with GPS on my Cyanongenmod Rom modified for K30-W, but after installing gapps all is working fine now.
Thank you for your help!

I hate to bother you any more, but I would like to use the same rom you are using, however I can't get it to flash.
I got TWRP 2.8.6.1 working (any other version I tried will not work)
I wipe DATA DALVIK and CACHE
When I try to install: 20170403-a6000-Official it gets stuck on:
Patching system image unconditionally....
I am able to flash Cyanogenmod, but that's a much older version.
If you could help me with what I am doing wrong, that would be much appriciated.
There are not many people running this phone.
I am also interested in the recovery you are using.

addict1337 said:
I hate to bother you any more, but I would like to use the same rom you are using, however I can't get it to flash.
I got TWRP 2.8.6.1 working (any other version I tried will not work)
I wipe DATA DALVIK and CACHE
When I try to install: 20170403-a6000-Official it gets stuck on:
Patching system image unconditionally....
I am able to flash Cyanogenmod, but that's a much older version.
If you could help me with what I am doing wrong, that would be much appriciated.
There are not many people running this phone.
I am also interested in the recovery you are using.
Click to expand...
Click to collapse
You must use TWRP 3.1.0, but even with it, RR 20170403 will not install on K30W firmware, I don't know why. I managed to install it by flashing A6000 firmware first. I will post the tutorial on RR thread when I find the time.

addict1337 said:
I hate to bother you any more, but I would like to use the same rom you are using, however I can't get it to flash.
I got TWRP 2.8.6.1 working (any other version I tried will not work)
I wipe DATA DALVIK and CACHE
When I try to install: 20170403-a6000-Official it gets stuck on:
Patching system image unconditionally....
I am able to flash Cyanogenmod, but that's a much older version.
If you could help me with what I am doing wrong, that would be much appriciated.
There are not many people running this phone.
I am also interested in the recovery you are using.
Click to expand...
Click to collapse
I've posted the tutorial here.

CrazyNik said:
I've posted the tutorial here.
Click to expand...
Click to collapse
Awesome, I was waiting for it
Thank you very much.

[RECOVERY] [TWRP] Android system recovery <3e> universal checksum disabler

This is a Flashable Zip for restoring backups created from different recoveries. No more problems with checksums, checksums will be ignored.
- Android system recovery <3e>
- CWM
- TWRP
- ADB Backup
- MIUI Backup
This is a alpha release, in this state you can test it for Android system recovery <3e> only!
I need testers for proof of concept. If you have a Mediatek Phone with encrypted userdata_20160823_100259.backup, please try to restore with bckp2raw.zip from TWRP. Please give feedback if failed or vote :good: if worked.
bckp2raw.zip (v1.0.3) 32-bit
bckp2raw.zip (v1.0.5) universal
(other backup formats following soon, feel free to request)

TUTORIAL - under construction

aIecxs said:
TUTORIAL - under construction
Click to expand...
Click to collapse
Is this solves problem of Android 7 stock recovery backup?
I got second phone stock recovery problem for 7 version
stock recovery do not want to recover his backup. complains - "it is corrupted, please reset your phone"
I install twrp recovery and try to install this .zip
bit it give error 134 (or something like that)

sorry this project is abandoned. in generally, backup can not restored to other device because of the checksum mismatch. Thats where this zip comes in game. If you upload recovery.log right after installing this zip i will try to fix the errors..

aIecxs said:
sorry this project is abandoned. in generally, backup can not restored to other device because of the checksum mismatch. Thats where this zip comes in game. If you upload right after installing this zip i will try to fix the errors..
Click to expand...
Click to collapse
I meant - I got another (second) phone looped reboot, same as in 2018. And try to stock recovery backup (55Gbyte and ) restore.
BTW - first phone is still waiting to restore 11Gbyte stock recovery backup!
last file: userdata_20191106_110350.backup27
Android 7 again same as in topic: https://forum.xda-developers.com/showthread.php?t=2528969&page=7
I copied lines from recovery.log:
I: operation_start: 'Flashing'
Installing zip file '/external_sd/bckp2raw.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:Update binary zip
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Archive: /external_sd/bckp2raw.zip
inflating: bckp2raw.sh
Archive: /external_sd/bckp2raw.zip
inflating: busybox-arm
Archive: /external_sd/bckp2raw.zip
inflating: tar-arm
CANNOT LINK EXECUTABLE "/system/bin/sh": "/system/lib/libc++.so" is 32-bit instead of 64-bit
Aborted
Updater process ended with ERROR: 134
I:Legacy property environment disabled.
I:Install took 0 second(s).
Error installing zip file '/external_sd/bckp2raw.zip'
Dont want to boring and get you, if you would give help - you can save many people with same problem with android-7

ah i see, script does not even start. i don't have a x64 device for testing, i assume twrp is not able to run mksh from /system. i have added paths please try this one instead...
update-binary
Code:
LD_LIBRARY_PATH=/system/lib64:/system/vendor/lib64:/system/lib:/system/vendor/lib
bckp2raw.zip (v1.0.5) universal

for those who want to quickly convert TWRP ADB backup.ab into data.ext4.win
usage for unpacking files (don't do this on windows disk)
Code:
bash twab.sh backup.ab
cd 20*
mkdir data
sudo tar --ignore-command-error --numeric-owner --selinux --xattrs -xpf data.ext4.win -ivC data 2> /dev/null

data partition is encrypted
Hi , I've been trying a lot of methods to get my data back from my .backup files. All with no results. Your bckp2raw script seems to be one of the most successfull , but it ends by a " data partition is encrypted" ... Do you think I can still recover my files ... The original phone is actually working but it has been factory wiped ...

that message just means that your current /data partition is encrypted (message for encrypted backup is different)
- do a backup of metadata partition (just in case)
- do a backup of /sdcard to PC (adb/mtp)
- format userdata partition
- reboot TWRP
- check userdata partition is unencrypted
- restore userdata*.backup from zip
- restore metadata partition from backup
- restore /sdcard backup
the restoring process will deny if userdata is not empty. please note if backup is encrypted it is most likely useless without corresponding backup of metadata partition

aIecxs said:
that message just means that your current /data partition is encrypted (message for encrypted backup is different)
- do a backup of metadata partition (just in case)
- do a backup of /sdcard to PC (adb/mtp)
- format userdata partition
- reboot TWRP
- check userdata partition is unencrypted
- restore userdata*.backup from zip
- restore metadata partition from backup
- restore /sdcard backup
the restoring process will deny if userdata is not empty. please note if backup is encrypted it is most likely useless without corresponding backup of metadata partition
Click to expand...
Click to collapse
Thank you very much for your quick reply. Ok so I tried it , the restoring part worked , but when I rebooted it asked me for my code and said "password is correct but data is corrupted" ....
Do you have any idea for me to get my data back .... at least my pictures ...?

sounds like the backup is encrypted, can you confirm? more important is this the source phone of this backup? or do you try to restore on other device?

aIecxs said:
sounds like the backup is encrypted, can you confirm? more important is this the source phone of this backup? or do you try to restore on other device?
Click to expand...
Click to collapse
I'm pretty sure it is encrypted. Yes the phone is the source phone of the backups

encryption should work in theory, but you need a copy of metadata partition from the day you created backup. you most likely don't have it, therefore your data is lost forever

aIecxs said:
encryption should work in theory, but you need a copy of metadata partition from the day you created backup. you most likely don't have it, therefore your data is lost forever
Click to expand...
Click to collapse
Yes I don't have the metadatas from that day, is there a chance that they have been backup with the android backup ?
Thanks for your help anyways, I'm sad

no, nothing you can do. even a old metadata from the first day when you buyed this device would probably do it. metadata partition is formatted on factory reset.
for some devices the crypto footer is not located at separate partition, but at the end of userdata partition instead. But this is not the case for your device, otherwise this zip would have restored. you can double check, search with hex editor in last -16384 bytes of last file for string aes-cbc-essiv:sha256 (or aes-xts)

aIecxs said:
no, nothing you can do. even a old metadata from the first day when you buyed this device would probably do it. metadata partition is formatted on factory reset.
for some devices the crypto footer is not located at separate partition, but at the end of userdata partition instead. But this is not the case for your device, otherwise this zip would have restored. you can double check, search with hex editor in last -16384 bytes of last file for string aes-cbc-essiv:sha256
Click to expand...
Click to collapse
Cannot find anything like this but i'm not used to HEX reading .... Is there a chance that the metadata is on the SD card i was using for (external) storage on the phone (not the ones for the backups) ?

Hello there and thanks for creating such a productive thread, just what I needed for my current situation. so am trying to retrieve .backup files on cxAir android 7.0 after root through twrp but apparently, when running the script from the zip file you've shared I get the Error: data partition not mounted.
I'm still new in the dev world but am totally excited about it and I may not understand a lot of things but am willing to work my ass off to figure out the most of what I can so please I'd really appreciate it if I could get some help on this one, thanks in advance

mount data partition and try again?