Database Info

Problem Flashing newer ROMs

I apologize if this has been answered before, I've been searching the better part of the afternoon/evening and haven't been able to find anything that is exactly what I'm seeing.
I have been running Jellybeans ROM for months, but recently it has been giving me fits, so I thought I'd try out one of the newer 4.4 ROMs. I have not done the 4.3 OTA update, so I figured it would be pretty easy. Here's the issue. I can install the 4.3 stock ROM without the firmware, or the Jellybeans ROM, I assume any 4.1.2 ROM. If I attempt to install any of the 4.4 ROMs, the installation aborts immediately with the following error:
Code:
Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1
Specifically, I've tried BeanStalk and the unofficial CM11. I'm using CWM v6.0.4.6. Any ideas what I'm missing? Thanks for any help you can give.

I'm using twrp so not sure if the cwm you're using is up to date. Recovery not being the latest will give people errors and you'll be unable to flash. I updated my recovery through jrummys Rom installer app
Sent from my SCH-I535 using Tapatalk

Yeah just update your recovery.
Sent from my SCH-I535 using xda app-developers app

Thanks for the responses. That is the latest CWM for the Verizon S3, but just to be sure, I installed TWRP. I am still unable to flash the ROMs. The TWRP log shows the following:
Code:
Error flashing zip '/external_sd/BeanStalk-4.4.225-20140123-d2vzw.zip'
Updating partition details...
I:Data backup size is 0MB, size: 12335MB, used: 1672MB, free: 10497MB, in data/media: 1672MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'flash_done'

sully51 said:
Thanks for the responses. That is the latest CWM for the Verizon S3, but just to be sure, I installed TWRP. I am still unable to flash the ROMs. The TWRP log shows the following:
Code:
Error flashing zip '/external_sd/BeanStalk-4.4.225-20140123-d2vzw.zip'
Updating partition details...
I:Data backup size is 0MB, size: 12335MB, used: 1672MB, free: 10497MB, in data/media: 1672MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'flash_done'
Click to expand...
Click to collapse
Tough one.
Sounds drastic, but try to Odin back to stock and reroot. I don't even think using a pit file would fix this one.
If it's still throwing an error, then repartitioning might fix the error.
Sent from my SCH-I535 using Tapatalk 2

Half bricked One Mini-Please for quick help

Hello, the phone is CID O2__102, o2 DE, came with android 4.4.2 rom version 3.10.206.6 HBOOT 2.22.000 and S-ON.Now i have **tampered** **UNLOCKED** with TWRP v2.6.3.0 and wiped memory.Cannot boot to android.I want to put back the same ROM or to do S-OFF to put another ROM with greek lang.All day I search for this ROM but can't find.Try Fuu_upgrade but gave me error.What can I do now.

sounds like your phone is not bricked, it´s just empty! when you wipe everything of course you can not boot.

Yes, but how to unlock CID to flash another ROM

you dont need to change your CID to flash another ROM, you only need this if you want to go S-OFF

OK, then how to S-OFF from this position?

vegaz said:
OK, then how to S-OFF from this position?
Click to expand...
Click to collapse
just search the different thread in the One-Mni section, you'll find a description.
BUT: Why do you want to go S-OFF?

theodorius123 said:
just search the different thread in the One-Mni section, you'll find a description.
BUT: Why do you want to go S-OFF?
Click to expand...
Click to collapse
If you know something tell me, your answer not helping me.I search all day and found nothing.How to flash not correct ROM to this phone from this position? I want to flash GREEK

vegaz said:
If you know something tell me, your answer not helping me.I search all day and found nothing.How to flash not correct ROM to this phone from this position? I want to flash GREEK
Click to expand...
Click to collapse
There are no Greek specific ROM's or RUUs. Try one of the stock ROMs on here. The stock ROMs come with Greek language packs. Forget about S-OFF and super CID your making more trouble for your self.
Sent from my HTC One mini using Xparent Green Tapatalk 2

RuffBuster said:
There are no Greek specific ROM's or RUUs. Try one of the stock ROMs on here. The stock ROMs come with Greek language packs. Forget about S-OFF and super CID your making more trouble for your self.
Sent from my HTC One mini using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Ok, I trying to use sideload this ROM "Jmz_M4_StockRooted_KK_Odex_WWE_3.10.631.5.zip" finishing, rebooting again in bootloader.
Then fastboot boot.img...rebooting in white screen HTC and freeze, I waited 5 minutes.TWRP again show me no OS

Friends I do OEM LOCK.Now is relocked just search for compitable RUU up from 3.10.206.6 PLEASE give me what you have, I will appreciate it.THANKS
P.S. I just fix OneX with the same problem, just relock and flash with RUU

Somebody, please...
Finished running boot script.
I:Can't probe device /dev/block/mmcblk0p34
I:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p34', current file system: 'ext4'
I:Failed to mount /cache for TWFunc::Update_Log_File
I:Can't probe device /dev/block/mmcblk0p34
E:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p34', current file system: 'ext4'
I:Attempt to load settings from settings file...
I:Loading settings from '/data/media/TWRP/.twrps'.
I:Backup folder set to '/data/media/TWRP/BACKUPS/HT3B5WA01720'
IataManager::SetBackupFolder zip path was /external_sd changing to /sdcard, /e
xternal_sd
I:Can't probe device /dev/block/mmcblk0p34
I:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p34', current file system: 'ext4'
I:Unable to mount '' to write version number.
I:Unable to mount '/external_sd'
I:Actual block device: '', current file system: 'vfat'
__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
I:TWFunc::Fixup_Time: not fixing time, it seems to be already okay (after year 2
000).
I:Switching packages (TWRP)
flashing MagioRom_R4 and boot.img - successful, but freeze on white screen "HTC"

Have a look at these two threads:
http://forum.xda-developers.com/showthread.php?t=2709687
http://forum.xda-developers.com/showthread.php?t=2677919
Read them carefully and completely and try to find out if this applies to you as well. Probably it does. Then you will have the solution over there as well.

OK after unzip this ROM "Jmz_M4_StockRooted_KK_Odex_WWE_3.10.631.5.zip" from here
http://androidfiles.org/?developer=M4&folder=Stock_Roms
edit updater-script file - line
run_program("/sbin/mke2fs", "-t", "ext4", "-m", "0", "/dev/block/mmcblk0p33");
mount("ext4", "EMMC", "/dev/block/mmcblk0p33", "/system");
from mmcblk0p33 to mmcblk0p35 ...(because mine /system now is "35") ziping again and flashing form external_sd (OTG usb) and boot successful.
But, when I relocked with OEM LOCK he bring me again to fastboot, after unlock again, he booted nice...I think to use revone to edit this maybe.

Soft-bricked Z5 when trying to restore a TWRP backup

Hey there,
My brother was trying to install a custom ROM on his phone but it was having issues so he went to restore a TWRP backup of an AOSP ROM he had before. Unfortunately, it was a backup of every partition, including the Firmware partition. When it got to restoring Firmware, it formatted the existing firmware partition, but then immediately failed at restoring the old Firmware partition backup with the following showing in the recovery.log:
Code:
I:Extracting uncompressed tar
==> extracting: /firmware//image/ (mode 40550, directory)
tar_extract_file(): failed to set permissions on /firmware//image/ !!!
I:Unable to extract tar archive '/data/media/0/TWRP/BACKUPS/QV7013TG03/Firm/firmware.vfat.win'
Error during restore process.
extractTarFork() process ended with ERROR: 255
After this, any attempts to start the phone result in a bootloop. We can still get into recovery but every time we try to restore the TWRP backup it fails at firmware again. Any ideas on how to get the phone working?
EDIT: Fixed!
I fixed this a while ago but if I recall correctly, we ended up flashing the stock firmware files with Flashtool. Basically go to this thread follow the steps under Part 2 and Part 2.5, then once you've created the firmware, flash it using Flashtool --> Lightning Button --> Flashmode --> Choose the firmware you made --> Wipe Userdata (not sure if we did this or not, try without it, if it doesn't work then wipe userdata) -->Flash. That should fix it.

I have never managed to restore backup on this stupid phone. Always errors with making backup or restoring backup or not detecting storage or some other crap. Sick of it

[solved] Android 9 with TWRP backup

Hello,
I use an stock android 9 ROM. When 8 try to backup this Rom I get this issue.
```
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1237
```
```
I:Error adding file '/data/vendor_ce/11' to '/data/media/0/TWRP/BACKUPS/FA6AD0307055/2018-08-28--15-30-48_PPR1180610009/data.ext4.win003'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/FA6AD0307055/2018-08-28--15-30-48_PPR1180610009/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/FA6AD0307055/2018-08-28--15-30-48_PPR1180610009/recovery.log
```
I can't make any backup.

What version of TWRP? Have you tried uninstalling and reinstalling Magisk? Have you tried backing up to an external drive, such as through a USB-OTG?

post-mortem said:
What version of TWRP? Have you tried uninstalling and reinstalling Magisk? Have you tried backing up to an external drive, such as through a USB-OTG?
Click to expand...
Click to collapse
I have the latest available version if TWRP installed. Why I must try to uninstall and reinstall Magisk? No external drive is available

Update here:
I flashed the complete firmware again, then installed TWRP and it works.

[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?