Database Info

Trouble going from CM10.0 to CM10.1.3

So, after waiting about a year for the next stable CM version I decided to update my HOS from CM10.0 to CM10.1.3.
Now the first thing I did was find information about how to do it and I found out the built in updater was not going to work. I did a full backup and tried anyway in case all I needed was to flash boot.img but after downloading the update the phone just reboots and nothing changes.
The next step was to manually flash the boot.img myself and then install the .zip, so I did it and after flashing the img the phone gets stuck in a bootloop (the circular screen). I immediately rebooted into TWRP and attempted to install CM10.1.3.zip, but the phone does not allow me to. Here's the log it gives me:
I:Attempt to load settings from settings file...
I:Version number saved to '/cache/recovery/.version'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Switching packages (TWRP)
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/cm-10.1.3-ville.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Warning: No file_contexts
script aborted: assert failed: getprop("ro.bootloader") == "2.15.4444" ||
getprop("ro.bootloader") == "2.15.0000" ||
getprop("ro.bootloader") == "2.13.0000"
assert failed: getprop("ro.bootloader") == "2.15.4444" || getprop("ro.bootloader") == "2.15.0000" || getprop("ro.bootloader") == "2.13.0000"
E:Error in /sdcard/cm-10.1.3-ville.zip
(Status 7)
Error flashing zip '/sdcard/cm-10.1.3-ville.zip'
Updating partition details...
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'settings'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'settings'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/rec
Click to expand...
Click to collapse
I can flash the 10.0 boot.img back without any problems, and I can also install the CM10.0.zip stable without any problems, so the phone is not in a state of emergency, but this is really bugging me out. Can anyone help me get through this?

You need to update your firmware.
See where it fails? It is checking your hboot and wants it to be 2.15.
So the easy way is to run latest RUU.exe to update to Jellybean, or flash a new hboot.

tivofool said:
You need to update your firmware.
See where it fails? It is checking your hboot and wants it to be 2.15.
So the easy way is to run latest RUU.exe to update to Jellybean, or flash a new hboot.
Click to expand...
Click to collapse
After investigating for a bit I found this thread:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
It says after using the RUU.exe the phone will be back to stock, both the ROM and recovery. So if I go through with it I'll have to repeat the root process/recovery/rom flash again right? And after that, will I be able to put all the backed up data back into the phone without losing anything? (I'll flash 10.0 again and then do the upgrade, not sure if a 10.0 backup is compatible with 10.1.3)

Rodrows said:
After investigating for a bit I found this thread:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
It says after using the RUU.exe the phone will be back to stock, both the ROM and recovery. So if I go through with it I'll have to repeat the root process/recovery/rom flash again right? And after that, will I be able to put all the backed up data back into the phone without losing anything? (I'll flash 10.0 again and then do the upgrade, not sure if a 10.0 backup is compatible with 10.1.3)
Click to expand...
Click to collapse
Yep, you will have to lock bootloader (I assume you are S-on)
fastboot oem lock
run the ruu, then unlock, custom recovery, flash rom, fastboot flash boot boot.img.
You will need to save photos, media, wallpapers, ringtones to your pc and put them back after the process. You will lose things like text messages.
I always download apps from the play store rather than trying to restore them. (less problems)

tivofool said:
Yep, you will have to lock bootloader (I assume you are S-on)
fastboot oem lock
run the ruu, then unlock, custom recovery, flash rom, fastboot flash boot boot.img.
You will need to save photos, media, wallpapers, ringtones to your pc and put them back after the process. You will lose things like text messages.
I always download apps from the play store rather than trying to restore them. (less problems)
Click to expand...
Click to collapse
So even though I did a full backup with TWRP if I restore it nothing is saved? Then what is the point

Rodrows said:
So even though I did a full backup with TWRP if I restore it nothing is saved? Then what is the point
Click to expand...
Click to collapse
yes, you are right, if you are going to stay on CM 10.0 you can use the backup. But what is the point of upgrading your firmware?
So basically you are going to be flashing a different ROM by going with the new CM. Restoring your TWRP backup will put you back to CM 10.0. (with new firmware)
The point of a backup is to restore to a time that you wanted before changes were made.

tivofool said:
yes, you are right, if you are going to stay on CM 10.0 you can use the backup. But what is the point of upgrading your firmware?
So basically you are going to be flashing a different ROM by going with the new CM. Restoring your TWRP backup will put you back to CM 10.0. (with new firmware)
The point of a backup is to restore to a time that you wanted before changes were made.
Click to expand...
Click to collapse
I read that people on 10.0 who flash boot.img and then do the update keep their settings/data, and I was talking about doing the RUU/unlock/recovery/CM10.0 to have the exact same thing as before (except for the hboot) and then updating to 10.1.3
Now I'm doubting if the keep settings/data part is true

Rodrows said:
I read that people on 10.0 who flash boot.img and then do the update keep their settings/data, and I was talking about doing the RUU/unlock/recovery/CM10.0 to have the exact same thing as before (except for the hboot) and then updating to 10.1.3
Now I'm doubting if the keep settings/data part is true
Click to expand...
Click to collapse
That sounds reasonable, but if you have problems with apps or bugs, the first thing people will ask is if you dirty flashed or did a full wipe before the install.

tivofool said:
That sounds reasonable, but if you have problems with apps or bugs, the first thing people will ask is if you dirty flashed or did a full wipe before the install.
Click to expand...
Click to collapse
I'll keep that in mind if there are problems. Besides, if something goes wrong I can always go back to 10.0
Thanks for all the help! :highfive:

I don't understand what happened.
I downloaded the RUU for my phone based on the getvar all commands, installed it, re-unlocked the phone, re-installed TWRP, re-rooted the phone, and after an hour I'm still where I started: hboot is not 2.15 so 10.1.3 does not install.
I can still install CM10.0 and restore the backup as expected, but I'm puzzled. I don't know what is wrong with this.
Can't I just get a 2.15 hboot file/zip from somewhere and flash it via fastboot? unless it doesn't work like that, then I guess I'll have to stay on 10.0.

What is your CID? Sounds like we reed to find a newer RUU
Sent from my HTC One S using Tapatalk now Free

tivofool said:
What is your CID? Sounds like we reed to find a newer RUU
Sent from my HTC One S using Tapatalk now Free
Click to expand...
Click to collapse
I don't know about that CID thing but the file I downloaded from http://www.androidruu.com/?developer=Ville was this one:
RUU_Ville_U_ICS_40_S_Vodafone_UK_2.38.161.6_Radio_1.08es.50.02.21_10.09c.50.04L_release_280400_signed.exe
It matched the getvar info perfectly, and since I'm S-On that's the only one I can use

Rodrows said:
I don't know about that CID thing but the file I downloaded from http://www.androidruu.com/?developer=Ville was this one:
RUU_Ville_U_ICS_40_S_Vodafone_UK_2.38.161.6_Radio_1.08es.50.02.21_10.09c.50.04L_release_280400_signed.exe
It matched the getvar info perfectly, and since I'm S-On that's the only one I can use
Click to expand...
Click to collapse
Yep, that would be the RUU that your phone came with when you brought it home from the store, but that is Ice Cream Sandwich version of android.
Now we need someone who knows RUUs and can tell you if Vodafone has a Jelly Bean RUU.
Or now could be a good time to S-Off your phone, then you can run whatever RUU you want.

tivofool said:
Yep, that would be the RUU that your phone came with when you brought it home from the store, but that is Ice Cream Sandwich version of android.
Now we need someone who knows RUUs and can tell you if Vodafone has a Jelly Bean RUU.
Or now could be a good time to S-Off your phone, then you can run whatever RUU you want.
Click to expand...
Click to collapse
Time to S-Off it is

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.

[Newbie] Cannot flash [cm-12.1-20151022-NIGHTLY-taoshan.zip]

Hello Guys,
This is my first post in xda-developers. I have tried to read and understood the forum rules and will try to follow them.
I have wiped out my system partition and have installed ThunderZap ROM with TWRP recovery. With TWRP I am trying to install cm-12.1-20151022-NIGHTLY-taoshan.zip, I got the following errors:
updating partition details...
...done
Full SELinux support is present.
MTP Enabled.
Installing '/external_sd/cm-12.1.20151022-NIGHTLY-taoshan.zip'...
Checking for MD5 file...
Skipping MD5 check; no MD5 file found
This package is for device: C2105,C2104,c2105,c2104,taoshan; this device is .
E: Error executing updater binary in zip '/external_sd/cm-12.1-20151022-NIGHTLY-taoshan.zip'
Error flashing zip 'external_sd/cm-12.1-20151022-NIGHTLY-taoshan.zip'
Updating partition details...
...done
I guess this error is because I wiped out /system partition, the installer is not able to read ro.product.device correctly, so I removed the assert() that checks for the device type in META-INF\com\google\android\updater-script. This time when I recompress the cm-12.1-20151022-NIGHTLY-taoshan folder contents to cm-12.1-20151022-NIGHTLY-taoshan.zip, and try to install using TWRP installer, it throws up an error like this:
Installing '/external_sd/cm-12.1.-20151022-NIGHTLY-taoshan.1.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/external_sd/cm-12.1-20151022-NIGHTLY-taoshan.1.zip'
Updating partition details...
...done
Any help on what could be going wrong? Is there any settings that I need to follow when compressing folder contents to a zip file?
Advance Thanks,
teejbee

you are on twrp recovery? (i guess the old one 2.8.4 ? )
go to Advanced -> Terminal command -> select
there enter:
setprop ro.product.device taoshan
setprop ro.build.product taoshan
then try to flash again

SdtBarbarossa said:
you are on twrp recovery? (i guess the old one 2.8.4 ? )
go to Advanced -> Terminal command -> select
there enter:
setprop ro.product.device taoshan
setprop ro.build.product taoshan
then try to flash again
Click to expand...
Click to collapse
Thank you! It worked. I am able to flash the original unmodified cm-12.1-20151022-NIGHTLY-taoshan.zip.
Regards,
teejbee

I have a question though. I installed playstore from here http://forum.xda-developers.com/showthread.php?t=1996995
I tried with version 5.10.30 and 5.9.12, it seems to open up and close immediately.
Is there anything I am missing for getting playstore? I am new to CM.
Thanks,
teejbee

teejbee said:
I have a question though. I installed playstore from here http://forum.xda-developers.com/showthread.php?t=1996995
I tried with version 5.10.30 and 5.9.12, it seems to open up and close immediately.
Is there anything I am missing for getting playstore? I am new to CM.
Thanks,
teejbee
Click to expand...
Click to collapse
yea you need to flash it manually in recovery....
http://opengapps.org/
arm -> 5.1 -> pico is what you need to select and then download and flash it

SdtBarbarossa said:
yea you need to flash it manually in recovery....
arm -> 5.1 -> pico is what you need to select and then download and flash it
Click to expand...
Click to collapse
Thanks a lot SdtBarbarossa. My problem with flashing cm-12.1-20151022-NIGHTLY-taoshan is solved now.
Feel delighted to have entered CM arena ?

No problem and Welcome

Twrp (error=255 on restore)

Hello,
I NEED SOME HELP
I made a backup of my phone using TWRP. When I try to restore from the backup I created, I get a "E:extractTarFork() process ended with ERROR=255" error message when it tries to restore the data.
Anyone know the fix for this?
Code:
I:Restore filename is: data.ext4.win
I:Restore file system is: 'ext4'.
Wiping Data...
Wiping data without wiping /data/share ...
I:Unable to unlink '/data/bugreports'
I:Unable to unlink '/data/skin'
I:Unable to unlink '/data/light'
I:Unable to unlink '/data/.hwplace'
I:Unable to unlink '/data/bflag'
I:Unable to unlink '/data/su.img'
I:Unable to unlink '/data/stock_boot_e0f9860555e8bb7e5681625b1e4fbf547191ac19.img.gz'
Done.
Restoring Data...
I:Multiple archives
I:First tar file '/sdcard/TWRP/BACKUPS/P6Q7N14A11007468/2016-04-25--14-39-12/data.ext4.win000' not encrypted
I:Extracting uncompressed tar
prefix:
==> tar_extract_all(TAR *t, "")
E:Unable to extract tar archive '/sdcard/TWRP/BACKUPS/P6Q7N14A11007468/2016-04-25--14-39-12/data.ext4.win000'
I:Error extracting '/sdcard/TWRP/BACKUPS/P6Q7N14A11007468/2016-04-25--14-39-12/data.ext4.win000' in thread ID 0
E:Error extracting split archive.
E:extractTarFork() process ended with ERROR=255
I:Set page: 'action_complete'

Are you using TWRP 2.7.8.0 and android 6??? It happened to me too.
Update to TWRP Recovery 3.0.2-0 Mate7 Android 6.0 (http://forum.xda-developers.com/mat...overy-twrp-2-8-7-0-mate7-android-5-1-t3156779)...
I am not sure (i did not try) if backups made with 2.7.8.0 can be restored with 3.0.2-0 without errors, but I can assure that 3.0.2-0 backups works perfectly...
Ciao.

leonardus_magnus said:
Are you using TWRP 2.7.8.0 and android 6??? It happened to me too.
Update to TWRP Recovery 3.0.2-0 Mate7 Android 6.0 (http://forum.xda-developers.com/mat...overy-twrp-2-8-7-0-mate7-android-5-1-t3156779)...
I am not sure (i did not try) if backups made with 2.7.8.0 can be restored with 3.0.2-0 without errors, but I can assure that 3.0.2-0 backups works perfectly...
Ciao.
Click to expand...
Click to collapse
Well...
I have TWRP Recovery 2.8.7.0 and had made a backup of my phone on Android 5.1.1 before updating to Android 6.0. So, the backup that I'm trying to restore is Android but my phone is now on Android.
The reason I want to restore is to get a hold of a certain app and data from it.