Database Info

[Q] Switch from 4EXT to CWM ? / Flashing boot.img ? (CM10-alpha)

Hi XDA
My device before the procedure : HTC Desire S, unbranded, Bootloader locked,
HBoot 2.00.0002, S-ON, ICS stock rom via HTC RUU tool
I unlocked the bootloader via htcdev.com.
After hours of reading and testing "everything" I found here on xda (great stuff!!),
I finally managed to have a running CM10-alpha.
(http://forum.xda-developers.com/showthread.php?t=1776256 / Version 2012-09-17)
As I am new to this flashing stuff, I first tried to follow the flashing guide
on the CM-website. Was not workable because "Revolutionary" can not be used on hboot 2...
So I continued with flashing CWM-recovery and after a wipe (factory/reset/cache/dalvik),
I flashed CM10.zip and gapps.zip.
It went through without any errors, unfortunately, the device did not boot afterwards.
I found this guide :
http://forum.xda-developers.com/showthread.php?t=1525100 (CustomROM with 4EXT-recovery)
It indicates flashing "boot.img" (from the CM10 zip-file) as a last step.
Probably the most important step for this HTC device ?!
The Desire S booted CM10 without any further problems and is running since.
(I did not flash GApps.zip, just downloaded Maps and Youtube.)
I have 3 questions :
1. Is it possible to update to a newer version of 4EXT-recovery without losing
the CM10-installation ?
(e.g. 4EXT-Touch : http://forum.xda-developers.com/showthread.php?t=1377745)
2. Is it possible to switch from 4EXT to CWM-recovery without losing
the CM10-installation ? I would like to have CWM because I could then use the ROMManager App.
(e.g. http://forum.xda-developers.com/showthread.php?t=1484753)
3. If I would stick with the current 4EXT-recovery,
do I always have to flash "boot.img" as the last step before booting up the device ?
(e.g. after the next CM10-alpha release)
"fastboot flash boot boot.img"
Click to expand...
Click to collapse
Thanks so much !
CM10 is great, so much faster than HTC-stock rom ICS (with Sense 3.6) !!
CU

1) yes
2)yep
3)si
Edit: you only have to flash the boot.img when the kernel changes from cm10 to fallout yes.
Updating cm10 no, if the dev didn't change the kernel.
After a full wipe (in 4ext format everything exept SD-card) you also have to use fastboot. Because that wipes the boot.img

Thanks !
Just to recap, I can flash CWM-recovery and then do a normal bootup (with my existing CM10 installation). No further actions required !?
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.

FrolicFrog said:
Thanks !
Just to recap, I can flash CWM-recovery and then do a normal bootup (with my existing CM10 installation). No further actions required !?
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
Click to expand...
Click to collapse
Changing recovery will not touch anything else on your device. But there were some issues reported with CWM on some ROMs.
I think one of them is a lack of /system/lib partition support, which is important if you go from a ROM that has such to a ROM without one (it will end with two conflicting /system/lib directories and the device will not boot.
Also I am not sure that CWM wipes the .android-secure directory on the SDcard which can cause issues if going from AOSP to Sense ROM

For some reason I never changed from cwm to 4ext whilst I owned a ds but I can confirm it does wipe .android-secure on the sd card

pughie said:
For some reason I never changed from cwm to 4ext whilst I owned a ds but I can confirm it does wipe .android-secure on the sd card
Click to expand...
Click to collapse
I have used it about an year ago so it is definitely improved. But there was an user with Bluetooth issues after flashing my kernel and changing the recovery solved it. Also 4EXT has a lot of minor but very useful settings over CWM. Anyway the OP can try both and stick with the one he likes more
Btw Rom Manager can be used to check for updates and ROM downloads with 4EXT if you choose "manual flash override" from the menu
Sent from my HTC Desire S

amidabuddha said:
Btw Rom Manager can be used to check for updates and ROM downloads with 4EXT if you choose "manual flash override" from the menu
Click to expand...
Click to collapse
Ah, will check on this one. Thanks !

FrolicFrog said:
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
Click to expand...
Click to collapse
Nk111 uploaded a screenshot today, that shows kernel v3.0.16
When upgrading cm10 wiping cache & dalvic cache should be enough. If you get any problems, apps fc or something like that, do a full wipe(I use format all partitions except SD card in 4ext, after that don't forget to flash the kernel with fastboot).
Btw wipe and format is the same.

Bug in CM10 Alpha by nk11
Hello XDA,
Sorry if this question is in the wrong thread.
It is regarding the cm10 alpha port by nk111.
I got it working, save one major bug, the speaker does not produce any sound output whatsoever:
This applies to ringtones, alarm tones and music.
The sound is perfectly audible through a pair of earphones.
I followed the steps in the official thread to delete the file /system/lib/hw/audio_policy.msm7x30.so and reboot
but this only aggravates the issue by disabling all audio outputs!!!
I am running clockwork mod v5 with HTC bootlocker unlocked, S-ON.
Any help would be greatly appreciated.

c.m.b said:
Nk111 uploaded a screenshot today, that shows kernel v3.0.16
When upgrading cm10 wiping cache & dalvic cache should be enough. If you get any problems, apps fc or something like that, do a full wipe(I use format all partitions except SD card in 4ext, after that don't forget to flash the kernel with fastboot).
Btw wipe and format is the same.
Click to expand...
Click to collapse
I saw the screenshot of kernel version 3, too. And was quite excited
Thanks for the hint with wiping only cache&dalvik.

Can't install ROM via TWRP

First, I have H-BOOT 1.09, and I am rooted, I have TWRP v3
Now, I had ViperROM 1.2.0 installed, and decided to install Trickdroid v7, and it failed. I thought it was weird, so I restarted the phone. It was just on the boot screen, and after rebooting into Recovery, I noticed that when I tried rebooting, it would say that no OS was installed.
I downloaded ViperROM 1.2.0 and checked the MD5 and it checked out. Thinking they might of fixed the Aroma full wipe, I ran it with a full wipe, and of course it didn't work. So, I rebooted into recovery, wiped Cache, Dalvik, Factory and System. Tried installing ViperROM again, this time with out the full wipe, it gets to 7% and then ask me to reboot. If I try rebooting, it tells me no OS is installed. Right now I am running CM10 but I don't want it. I want ViperROM.
I had this same issue before, but I was exactly sure what I did in order to get it to install. So now I am stumped, and I don't know how to use ADB.

If you use latest TWRP 2.3.x, it will not work. You need to go back to TWRP 2.2.2.0

cat2115 said:
If you use latest TWRP 2.3.x, it will not work. You need to go back to TWRP 2.2.2.0
Click to expand...
Click to collapse
I feel really stupid because I didn't check the last 30 pages of that topic, although it seems its because System is mounted, which I had absolutely no idea WTF that meant.
Does that mean that the latest TWRP is the reason why Trickdroid didn't install?

I could never get either to install using any version of TWRP and i'm on hboot 1.06. I always had to fastboot flash the boot.img first, clear caches. It's weird and no one involved could explain it...been flashing other ROMs fine via TWRP 2.3

Hgaara said:
I feel really stupid because I didn't check the last 30 pages of that topic, although it seems its because System is mounted, which I had absolutely no idea WTF that meant.
Does that mean that the latest TWRP is the reason why Trickdroid didn't install?
Click to expand...
Click to collapse
If you download gooManager from Play. it will install the latest TWRP. If you need TWRP 2.2.2.0, you can find it in ToolKit Rooting. Inside the folder there' s a TWRP 2.2.2.0
Use that img and do a fastboot
fastboot flash recovery TWRP.img
Click to expand...
Click to collapse
Hope this help you.
Or you can try
older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
Click to expand...
Click to collapse
at http://forum.xda-developers.com/showthread.php?t=1677670&highlight=twrp+recovery
below "CHANGELOG for 2.3.0.0:" you find a download link to "update-binary"

[Q] Please help! Can't mount SD in Recovery can't flash ROM

Not sure what i've done...
I wiped my System partition, and data partitions and was going to flash the latest AOKP (i had some issues with rohan's kernel so i needed to start fresh) but i can't mount my SD in TWRP and I'm pretty concerned that my built in storage is screwed. Any help ??

Prfndhatrdofman said:
Not sure what i've done...
I wiped my System partition, and data partitions and was going to flash the latest AOKP (i had some issues with rohan's kernel so i needed to start fresh) but i can't mount my SD in TWRP and I'm pretty concerned that my built in storage is screwed. Any help ??
Click to expand...
Click to collapse
go here: http://forum.xda-developers.com/showthread.php?t=1671237 and read before you do anything else. Then.. find your device specific RUU and run it. You'll have to relock your bootloader and reflash TWRP.
Which AOKP were you looking to flash?
Which hboot do you have?
and do you have the international or US version?

Myrder said:
go here: http://forum.xda-developers.com/showthread.php?t=1671237 and read before you do anything else. Then.. find your device specific RUU and run it. You'll have to relock your bootloader and reflash TWRP.
Which AOKP were you looking to flash?
Which hboot do you have?
and do you have the international or US version?
Click to expand...
Click to collapse
I was hoping to avoid doing an RUU, don't RUUs wipe USB Storage?
I have Hboot 1.09
CID 11111111
I had flashed AOKP Milestone 1 JB earlier.
I flashed a few 4.2 JB apps and upon reboot my phone would stick at the boot animation.
So I wiped my data partition and system to reflash Milestone 1 but now i can't flash anything.

Can you get into TWRP? If so, you can adb push.
Sent from my HTC One XL cellular device over clocked to 1.9Ghz

I've been trying to flash using fastboot: fastboot update blahblah.zip
fails saying there is android-info.txt

Yes, RUU wipes everything and gets rid of any corruption. Wait, are you wiping cache and delvik, and system...?
Sent from my HTC One XL cellular device over clocked to 1.9Ghz

Myrder said:
Yes, RUU wipes everything and gets rid of any corruption. Wait, are you wiping cache and delvik, and system...?
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
Click to expand...
Click to collapse
I did yes. Everything is wiped currently so im sort of in a soft brick. i can boot in and out of recovery but i cannot flash anything. my SD storage wont mount in TWRP

I figured out what i did. i accidentally hit factory reset from Bootloader. and then stopped the reset. had to flash stock recovery and flash twrp again. lost all of my stuff. pretty upset about it. my fault though i guess.

Close this thread please.

Does windows ask you if you want to format when you mount usb in twrp?
If so format fat32, transfer files over and go.
I don't know why everyone are telling people to RUU when they dont have to

because formatting in windows doesn't always fix it.

newbie mistake
So after stumbling to this thread I realized what happened with my attempt at flashing a rom. I selected Viper 2.6.0 for my newly rooted At&t one x on firmware 2.20. It was stuck on bootloop. I had backed up using TWRP 2.3.1, but the restore was stuck on a bootloop as well.
I realize now that this was because I was flashing an international rom. Is this recoverable or is this the last mistake I can make on this phone?
Any advice or links to the proper thread would be very much appreciated.

[How to] Fix corrupt/unmountable internal storage on the HTC One X/XL

I'm having the "E: Can't mount /sdcard/ problem in CWM recovery v5.8.3.1. I followed the guide to install but I find it misleading. I came from Leedroid so I had to "factory reset" but this has caused the problem. Any advice to a noob?

Bradz213 said:
I'm having the "E: Can't mount /sdcard/ problem in CWM recovery v5.8.3.1. I followed the guide to install but I find it misleading. I came from Leedroid so I had to "factory reset" but this has caused the problem. Any advice to a noob?
Click to expand...
Click to collapse
your in the wrong forum

DvineLord said:
your in the wrong forum
Click to expand...
Click to collapse
Wrong thread perhaps, right forum!

No wrong forum. Sounds like you have a tegra 3 Onex. This forum is for the s4 version
Sent from my One X using xda app-developers app

Stock 4.2.1 unlocked with TWRP 2.6.0.0

Oke, so I'm at the stage that I want to backup the Asus stock ROM and install a custom rom.
When starting the backup from TWRP, it shows 2 errors:
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
The backup does backup the other partitions, such as system, data, etc. and ends with the error:
E:Backup File size for '/.........//boot.emmc.win' is 0 bytes
So, did it backup the boot files? If not, i will not install a custom rom, which will probably overwrite the boot partifion files and leaves me with an unrestorable backup of the Stock ROM.
Any info or advise about these errors would be welcome.
TWRP version 2.6.0.0
Stock ROM 4.2.1
------
EDIT: installing TWRP 2.5.0.0 does not have this problem. Seems like a bug in 2.6.0.0, so don't use this version with 4.2.1 stock Asus Rom

remonv76 said:
Oke, so I'm at the stage that I want to backup the Asus stock ROM and install a custom rom.
When starting the backup from TWRP, it shows 2 errors:
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
The backup does backup the other partitions, such as system, data, etc. and ends with the error:
E:Backup File size for '/.........//boot.emmc.win' is 0 bytes
So, did it backup the boot files? If not, i will not install a custom rom, which will probably overwrite the boot partifion files and leaves me with an unrestorable backup of the Stock ROM.
Any info or advise about these errors would be welcome.
TWRP version 2.6.0.0
Stock ROM 4.2.1
------
EDIT: installing TWRP 2.5.0.0 does not have this problem. Seems like a bug in 2.6.0.0, so don't use this version with 4.2.1 stock Asus Rom
Click to expand...
Click to collapse
2.6.0.0 has other bugs too so you did right in going with 2.5.0.0.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

2.5 didnt fix my issue completely
remonv76 said:
Oke, so I'm at the stage that I want to backup the Asus stock ROM and install a custom rom.
When starting the backup from TWRP, it shows 2 errors:
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
The backup does backup the other partitions, such as system, data, etc. and ends with the error:
E:Backup File size for '/.........//boot.emmc.win' is 0 bytes
So, did it backup the boot files? If not, i will not install a custom rom, which will probably overwrite the boot partifion files and leaves me with an unrestorable backup of the Stock ROM.
Any info or advise about these errors would be welcome.
TWRP version 2.6.0.0
Stock ROM 4.2.1
------
EDIT: installing TWRP 2.5.0.0 does not have this problem. Seems like a bug in 2.6.0.0, so don't use this version with 4.2.1 stock Asus Rom
Click to expand...
Click to collapse
first time posting, xda has been my bible and guide for all of my unlocked adventures.
I had very similar symptoms and questions. I flashed the CM 10.2 and it worked fine (i had previously backed up my working PACrom and my CM10.1 before that)
I backed up my 10.2 and did a wipe and cache d.cache wipe. But couldn't restore (/boot & /recovery issues as well) so I then fastboot flashed twrp 2.5 back on and tried to restore from there and it wouldn't restore data, so I then wiped wiped and tried to flash the pacrom and gapps that had worked in the past with 2.5 and it worked! ( i thought ) until i realized it wouldn't get past the boot animation...I wiped and tried a CM10.1 restore and it worked again, but not really...it would get as far as the lockscreen and reboot. I was about to break my tab...and still am tempted to do so. This went on for a while until I gave up and went to bed.
After class, I did some more crawling through support and searching, and I read that flashing the original 10.1.6.15 back might help, so I did. It went through the motions, but got stuck on the boot animation, again. so I tried to get into twrp, but it was gone..
I fastboot twrp 2.5 on again, and twrp loads (hooray) and so I proceeded to wipe, cache/d.cache wipe, and install pacrom/gapps and it worked again again, but really didnt as it rebooted right after the "starting apps" screen appeared.
I know 10.2 runs 4.3, but I don't know enough about android OS to know exactly what flashing it may have changed. also I don't know why it is hanging at the startup of the os.
I tried searching but this is the closest post to what my issues are.
I don't know the ins and outs of droid partitioning/filesystems to feel comfortable just freely wiping parts, like I would a PC.
I just wish I knew a way to go back in time 36 hours and tell myself, DONT FLASH THOSE YET.
I am sorry this is such a long post, but I can't risk hard bricking this tablet like I did my old SG3 and since fastboot and twrp still load/function I have a great deal of hope someone will be kind enough to help me out.
Thank you.
EDIT/ADDENDUM:
- used "format data" on twrp, and wiped dalvik cache, cache, andsystem w.twrp 2.5, flashed new stock .27 firmware with 2.6, since the last one didnt work.
hope new firmware is twrp 2.5-friendly...2.6 lacks alot of utility features that 2.5 had

[Request] CM11 Nightly Fix

Hi, I Need Somebody Who Can Fix The Failed From TWRP.
I'm Using cm-11-20140914-NIGHTLY-bacon.zip
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E : Error executing updater binary in zip '/data/media/0//cmupdater//cm-11-20140917-NIGHTLY-bacon.zip'
E : Error installing zip file '/data/media/0//cmupdater//cm-11-20140917-NIGHTLY-bacon.zip'
Basically i've done an advanced wipe removing EVERYTHING from the phone then installed
cm-11-20140912-NIGHTLY-bacon.zip
then tried to update to Using cm-11-20140914-NIGHTLY-bacon.zip but same error happen so factory reset
and now this error happen again!
Pissed off of doing factory reset everytime.
So i need somebody who can find a way to remove the incompatible data without doing a factory reset.​

WoohWooh said:
Hi, I Need Somebody Who Can Fix The Failed From TWRP.
I'm Using cm-11-20140914-NIGHTLY-bacon.zip
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E : Error executing updater binary in zip '/data/media/0//cmupdater//cm-11-20140917-NIGHTLY-bacon.zip'
E : Error installing zip file '/data/media/0//cmupdater//cm-11-20140917-NIGHTLY-bacon.zip'
Basically i've done an advanced wipe removing EVERYTHING from the phone then installed
cm-11-20140912-NIGHTLY-bacon.zip
then tried to update to Using cm-11-20140914-NIGHTLY-bacon.zip but same error happen so factory reset
and now this error happen again!
Pissed off of doing factory reset everytime.
So i need somebody who can find a way to remove the incompatible data without doing a factory reset.​
Click to expand...
Click to collapse
Try re-downloading the update and try to install that. If that doesn't work, just wait till tonight when another update is released.

I am using PhilZ Touch to install Nightlies without issues.

If you installed TWRP 2.8.0.0 there is a bug that prevents you from flashing. Update to 2.8.0.1:
http://techerrata.com/browse/twrp2/bacon

f231f said:
If you installed TWRP 2.8.0.0 there is a bug that prevents you from flashing. Update to 2.8.0.1:
http://techerrata.com/browse/twrp2/bacon
Click to expand...
Click to collapse
Thank You Man
Fixed :good:

OK, I seem to be having the same issue as above. I've tried TWRP 2.8.0.1 and the latest Philz Recovery but neither can flash the latest Nightly (24th September). MD5s match and I get the status 7 error so not sure what else to do. I'm sure it's something in the script but thought I'd see if others are having issues
EDIT: Not to worry! Turns out you can't dirty flash CM11 over CM11S so I made a backup and flashed it new