Database Info

[RECOVERY][HeroC]TWRP 2.2.2.0 touch recovery [2012-08-24]

Team Win Recovery Project 2.2, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG (for 2.2.2.0 compared to 2.2.0.0):
Mostly bugfixes:
Significantly improved sd-ext handling (ext partitions on sdcards)
Changes to kinetic scrolling in file selectors
Fixed a problem with using periods in backup names
Fixed problems in XML layouts with mounting system and USB storage
Fixed a problem with unmounting a partition before formatting during restore
Add Jelly Bean decrypt support
Updated 320x480 theme to match others (thanks to Llewelyn)
Improve "symlinking" of /data/media to either /sdcard or /emmc
Added sanitizing of device IDs for invalid characters (thanks to bigbiff)
Fixed free space calculation when switching backup devices on /data/media devices
Fixed a problem with using OpenRecoveryScript to create a backup without providing a backup name
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
NOTE: If you're coming from another build of TWRP, you may need to go into settings and tap reset defaults to reset the storage paths so that you can see your zip files.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

thank you for this, ill test asap
if anyone wants a flashable zip, lemme know. i already have it done
edit: works good. only thing is i was flashing a rom (attempting to anyway) and somehow my zip got corrupted and unreadable. never had that happen before. any thoughts? (it was fine when i put it on my sd card, was flashing a 2nd time, so zip had worked previously and all other files on my sd are fine)

Going to flash this now and give it a try. Hopefully it works out good.

whoshotjr2006 said:
if anyone wants a flashable zip, lemme know. i already have it done
Click to expand...
Click to collapse
Throw it up brother!

thanks, always wanted a touch recovery and this one is great, if i could make a recovery touch it would be like this one again thanks

I flashed this a week or two ago and been working awesome! I love it.

i have been using cw recovery all time and always wanted to have a touch screen recovery and this one is sick, my only thing i have found is when i go to restore a backup it cannot find it,(one from cwm recovert). is it that it just cant restore those or did i miss something? no big deal to me ,just wanted to put it out there.
again thanks for this

they are in different folders on the SDCARD, im not even sure they are compatible.

ok cool im trying to do differant things and ill update you either way
would you know off hand where twrp folder would be? im looking if i get it before a reply ill post it
i got it twrp folder

alsp cani get the twrp 2220 in a zip format?

will this recovery work with firerats? on heroc?

dankdank11 said:
will this recovery work with firerats? on heroc?
Click to expand...
Click to collapse
Yes, Firerats has nothing to do with the recovery. Firerats just resizes your data/system/cache portion of the system really so you can install more apps.
I am using it and love it and works awesome on my Hero. :good:

thanks im trying it now, love the use of touch

I am going to leave the automated GooManager install for the Hero on version 2.2.2.0 due to the age of the device and the problems with recovery API 3 and older zips. TWRP 2.3.0.0 does work fine on the HeroC but I'm willing to bet that most zips are using old update binaries that will not install on the new version. If anyone wants to try, you're welcome to download and flash the newer versions manually:
http://techerrata.com/browse/twrp2/heroc

I was going to give 2.3.0.0 a try but like you stated, and someone in IRC said, that most of the zips online for the old Hero are prob all older so going to stick with 2.2.0.0 I think. Thanks for the update though.

Does TWRP require any particular hboot version, or will it function with any of them? I know you need to be on Android 2.3 in order to install TWRP, but I'm wondering... does it also mean that if you flash back to a stock ROM that TWRP won't work properly?
EDIT: My question was obviously stated with some knowledge missing. Recovery is obviously not dependent upon the ROM, as the ROM is loaded after the recovery program is done! But... I'm curious to know, if I made a nandroid backup with TWRP 2.2.2.0, will TWRP2 be able to restore it?

* DELETE *

There has been a small oversight with the GooManager route of distribution and the original post for this particular phone. You must have a PC or have a phone that can flash .zips or has a 2.3 or up ROM installed so it can run GooManager, even though this phones last OTA was Android 2.1, so it probably should have a .zip posted instead.
For example, I have a stock but rooted HTC Hero from Sprint as my backup with the latest OTA. So I can't use this method of install for this recovery without flashing a different recovery first, and then either flashing it as a .zip or upgrading my ROM to a 2.2 or 2.3 based ROM. In reality, I think most will just stick with whatever recovery must be flashed first in this situation as I will, even though I wanted TWRP. That said I think most of the users that use this will just want a .zip.
But there is no .zip posted for the guys that can flash it. This also makes it an overly cumbersome option if the handset is in stock state. As I said, I probably won't bother re-flashing, I kind of like sticking to one recovery on a phone and prefer to do minimal NAND writes.

DizturbedOne said:
There has been a small oversight with the GooManager route of distribution and the original post for this particular phone. You must have a PC or have a phone that can flash .zips or has a 2.3 or up ROM installed so it can run GooManager, even though this phones last OTA was Android 2.1, so it probably should have a .zip posted instead.
That said I think most of the users that use this will just want a .zip.
But there is no .zip posted for the guys that can flash it. This also makes it an overly cumbersome option if the handset is in stock state. As I said, I probably won't bother re-flashing, I kind of like sticking to one recovery on a phone and prefer to do minimal NAND writes.
Click to expand...
Click to collapse
As stated a couple of posts before you:
Dees_Troy said:
I am going to leave the automated GooManager install for the Hero on version 2.2.2.0 due to the age of the device and the problems with recovery API 3 and older zips. TWRP 2.3.0.0 does work fine on the HeroC but I'm willing to bet that most zips are using old update binaries that will not install on the new version. If anyone wants to try, you're welcome to download and flash the newer versions manually:
http://techerrata.com/browse/twrp2/heroc
Click to expand...
Click to collapse
Sent from my SCH-I535 using xda app-developers app

Hippie459MN said:
Yes, Firerats has nothing to do with the recovery. Firerats just resizes your data/system/cache portion of the system really so you can install more apps.
I am using it and love it and works awesome on my Hero. :good:
Click to expand...
Click to collapse
That's good to know. I think I'll give it a shot.

[i9103][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Special thanks to @Adam77Root for his work to make this possible
Download links
Last version can be found here:
i9103
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
http://d-h.st/users/philz_touch/?fld_id=18564#files
Click to expand...
Click to collapse

Great to see Philz at R forum. First Adam's Official Cm10.1 then Official PAC now Official Support of Philz recovery.:good:
Edit: status 0 error occurs when i flash using cwm.

Disturbed™ said:
Edit: status 0 error occurs when i flash using cwm.
Click to expand...
Click to collapse
Replace the update-binary with this.
Sent from my GT-I9103

Adam77Root said:
Replace the update-binary with this.
Sent from my GT-I9103
Click to expand...
Click to collapse
Sorry,
Missed this from your feedback PM
Just fixed the zip on download server
Now, it should flash correctly
Many thanks for the support :good:

Finally Flash it (Thanks Adam)
Working Great.
1) Touch is working great. - It will work after 5-6 Seconds.(If possible just press back Hardware key)
2) Its Superfast.
3) Approx 90% functions are working.(A normal day user can flash it without any problem.
4) Taking backing up normally & deleting data & caches also.
Few bugs:
1) you can't view what you are flashing ( Texts are going quickly downwards to front page & hence you can't see it)
2) 1 or 2 functions aren't working(might be my R problem).
I m attaching the zip file with Adam's Update - binaries.
Flash it & Enjoy. :good:

Disturbed™ said:
Finally Flash it (Thanks Adam)
Working Great.
1) Touch is working great. - It will work after 5-6 Seconds.(If possible just press back Hardware key)
2) Its Superfast.
3) Approx 90% functions are working.(A normal day user can flash it without any problem.
4) Taking backing up normally & deleting data & caches also.
Few bugs:
1) you can't view what you are flashing ( Texts are going quickly downwards to front page & hence you can't see it)
2) 1 or 2 functions aren't working(might be my R problem).
I m attaching the zip file with Adam's Update - binaries.
Flash it & Enjoy. :good:
Click to expand...
Click to collapse
- About text going too fast: try to enable both "Easy Log View" and "Pause on Logs" options. This should fix it. In a future version, ui_print text will have its own row height, not shared with menu height
- About non working functions: provide a description + log (Advanced / Report Error and attach file here)

Phil3759 said:
- About text going too fast: try to enable both "Easy Log View" and "Pause on Logs" options. This should fix it. In a future version, ui_print text will have its own row height, not shared with menu height
- About non working functions: provide a description + log (Advanced / Report Error and attach file here)
Click to expand...
Click to collapse
Thanks for the quick response buddy. I will provide you the same. But its time for my B'day party.:laugh:

run's on stock ics?
Is a awesome recovery y test in s2

Sesme said:
run's on stock ics?
Is a awesome recovery y test in s2
Click to expand...
Click to collapse
Didn't get you buddy, come again.?

Sesme said:
run's on stock ics?
Is a awesome recovery y test in s2
Click to expand...
Click to collapse
This recovery is particularly for the galaxy r. Do not flash it on the s2
Sent from my GT-I9300

pulley06 said:
This recovery is particularly for the galaxy r. Do not flash it on the s2
Sent from my GT-I9300
Click to expand...
Click to collapse
no run's on stock ics no format no flash rom's...return to CWM 5

will this file works on n7100 to?
Disturbed™ said:
Finally Flash it (Thanks Adam)
Working Great.
1) Touch is working great. - It will work after 5-6 Seconds.(If possible just press back Hardware key)
2) Its Superfast.
3) Approx 90% functions are working.(A normal day user can flash it without any problem.
4) Taking backing up normally & deleting data & caches also.
Few bugs:
1) you can't view what you are flashing ( Texts are going quickly downwards to front page & hence you can't see it)
2) 1 or 2 functions aren't working(might be my R problem).
I m attaching the zip file with Adam's Update - binaries.
Flash it & Enjoy. :good:
Click to expand...
Click to collapse
do you know if this file works on n7100 to?

xastunts said:
do you know if this file works on n7100 to?
Click to expand...
Click to collapse
No buddy.

xastunts said:
do you know if this file works on n7100 to?
Click to expand...
Click to collapse
But n7100 version exists since months now...
Sent from my GT-I9100 using Tapatalk 2

Phil3759 said:
But n7100 version exists since months now...
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
yes but we have previous version philz_touch_5.06.1-n7100.zip
they got the philz_touch_5.07 which i believe has exfat support for ext sd and thats why i wanted it

xastunts said:
yes but we have previous version philz_touch_5.06.1-n7100.zip
they got the philz_touch_5.07 which i believe has exfat support for ext sd and thats why i wanted it
Click to expand...
Click to collapse
Please read change log carefully. If there were really needed things, i'd have updated. Exfat works on n7100 since first release, months ago.
Last version has even a bug in custom restore that no one even noted (it doesn't affect integrity and nandroid function by the way)
Sent from my GT-I9100 using Tapatalk 2

Phil3759 said:
Please read change log carefully. If there were really needed things, i'd have updated. Exfat works on n7100 since first release, months ago.
Last version has even a bug in custom restore that no one even noted (it doesn't affect integrity and nandroid function by the way)
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
AAh damn it! i apologize! i mixed this up with the devil dual boot recovery! that one didnt have exfat support so i needed to mount another ext sd card in fat32 and swap it when i was in other roms. pretty annoying!
no ur right urs works! i know cause my exfat is inserted and booting through ur recovery all day long trying to find my soul mate os lol.
thx alot for the stuff you do for us! ur our hero!

is there a 100% full format option in ur recovery?
Phil3759 said:
Please read change log carefully. If there were really needed things, i'd have updated. Exfat works on n7100 since first release, months ago. http://icons.media.xda-developers.com/images/editor/separator.gif
Last version has even a bug in custom restore that no one even noted (it doesn't affect integrity and nandroid function by the way)
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
dr phil! i got you a question ! . is there a 100% full format option availible in ur recovery? if it is please state where.
even after using clean to install new rom i can see alot of junk files on my phones folders when connected to the pc. some photos from viber and alot of empty folders from apps i have uninstalled months ago.
is there no way to make a real clean whipe and have nothing at all left except important os file tree?
thx for reply! i try to pay you back in a good favour

xastunts said:
dr phil! i got you a question ! . is there a 100% full format option availible in ur recovery? if it is please state where.
even after using clean to install new rom i can see alot of junk files on my phones folders when connected to the pc. some photos from viber and alot of empty folders from apps i have uninstalled months ago.
is there no way to make a real clean whipe and have nothing at all left except important os file tree?
thx for reply! i try to pay you back in a good favour
Click to expand...
Click to collapse
remaining files are sdcard contents. YOu can remove by formatting sdcard. That won't be done automatically to avoid people loosing their data

Phil3759 said:
remaining files are sdcard contents. YOu can remove by formatting sdcard. That won't be done automatically to avoid people loosing their data
Click to expand...
Click to collapse
thx alot for reply! deeply appreciate it!:angel: how about using ur aroma browser that is built in inside the recovery and mark all files and just delete them ? will i be able to reboot into recovery mode after that? i was thinking that recovery files where flashed into a flash memory outside the phones internal memory to be a fail safe place harmless for beeing erased unless flashed with odin or flashed with any compatible recovery we got availible. am i right about this?
so my short question again is can i mark all folders and files and delete them directly through the built in aroma browser?
:good:
im willing to write you good comments and review here or on youtube if it is in ur demands.

[RECOVERY][FLASHABLE]ClockworkMod 6.0.4.9 for Flo - Touch/Non-touch (Swipe) (6/10)

Both of these are flashable zips, meaning you can flash in TWRP or upgrade from an older CWM.
CWM_flashable_swipe_6.0.4.9- https://drive.google.com/uc?export=download&id=0BxS5PetHg8JpQk8zWGhRQnM5VjA
CWM_flashable_touch_6.0.4.7- https://docs.google.com/uc?export=download&id=0BxS5PetHg8JpVENWZFkzRGdfUGs
If you do not have a recovery installed either download
6.0.4.3 non-touch: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-flo.img
6.0.4.3 touch: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.3-flo.img
Or even TWRP if you want to...http://techerrata.com/browse/twrp2/flo
Make sure to have your BOOTLOADER UNLOCKED and ADB/Fastboot installed
Reboot to your bootloader
Code:
fastboot flash recovery "whatever recovery you chose"
Reboot to bootloader again
Select Recovery and check if everything flashed fine
osm0sis said:
CWM Unofficial "Nightlies" Changelog - maguro:
https://github.com/CyanogenMod/android_bootable_recovery/commits/cm-11.0
Jan 29, 2014 - 6.0.4.7 is the most recent on ROM Manager, adds fixes to "mounts and storage" menu hiding certain mounts like /efs and /radio by default and adds ro.cwm.forbid_format and ro.cwm.forbid_mount properties to adjust these per device, enable performance mode in tgz extract/compress only, disable performance mode for package installs.
Apr 10, 2014 - 6.0.4.8 display improvements for overlay devices and high res, f2fs support fixes, reboot command fixes, yaffs2 backup support, general cleanups and compile fixes, USB adb+ums fixes, support upstream minui changes, revert fallback update-binary and instead create a legacy property environment, loki updates, add native dualboot if supported.
Jun 4, 2014 - 6.0.4.9 swipe controls fixes, prevent changes to swap partitions, menu fixes, code cleanups, keep show log option on screen until dismissed, add SELinux context support to dup format backups, format non-vold extra storage to ext4 (if not otherwise specified), fix backup of directories named "media" that aren't /data/media, add SELinux context support to tar format backups, fix f2fs restore, (ramdisk mod by myself to hide /factory,/boot,/sbl,/xloader from the format list).
(For an unofficial list of other changes between recent versions, see my previous changelog.)
Known Bugs / Notes:
- Key test does not have a confirmation, so if triggered by mistake a hard reset is required if no USB connection is available to make it exit.
- SELinux in JB4.3+ changes the permissions of su on every boot, so after any boot back to Android you will get a su warning in CWM; it can be ignored.​
Click to expand...
Click to collapse
Thanks to:
Koush
CM Team
@osm0sis
Anyone who contributed​

Awesome. I'm not a fan of TWRP... For whatever reason. I just like Clockwork.
Update: Anyone try this yet?
Sent from Nexus 7 FHD from XDA Premium HD

will try it now

Can some one make a flashable zip of this?
Sent from my Nexus 7 using Tapatalk 4 Beta

Wtf is "flo"?

Our code name
Sent from my Nexus 7 using Tapatalk 4 Beta

aimfire72 said:
Wtf is "flo"?
Click to expand...
Click to collapse
That annoying chick from Progressive commercials.

player911 said:
Awesome. I'm not a fan of TWRP... For whatever reason. I just like Clockwork.
Update: Anyone try this yet?
Sent from Nexus 7 FHD from XDA Premium HD
Click to expand...
Click to collapse
Already did this last night working fine via fastboot
Sent from my Nexus 7 using xda app-developers app

So no problems flashing over TWRP? I'll admit it, I'm an old dog that doesn't like new tricks. I've always had Clockwork and that's what I'm used to.

No prob at all i just flaahed over my twrp working fine
Sent From My Fresh Nexus 7(2013)

This should probably be moved over to Development so it can be seen.
Nice to have options.
Sent from Nexus 7 FHD from XDA Premium HD

Thanks for posting just rooted. I was waiting for clockwork to be posted. Not a fan of twrp.
Sent from my HTC One using Tapatalk 4 Beta

player911 said:
This should probably be moved over to Development so it can be seen.
Nice to have options.
Sent from Nexus 7 FHD from XDA Premium HD
Click to expand...
Click to collapse
I posted it here, simply because I didn't actually compile it. If a mod wants to move it, he/she are gladly welcome too.

CharlyDigital said:
Thanks for posting just rooted. I was waiting for clockwork to be posted. Not a fan of twrp.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Delete
Sent From My Fresh Nexus 7(2013)

what i don't get is, if it's in the brance to be built why doesn't koush himself compile a build and host it in rom manager. thanks for linking this tho

smirkis said:
what i don't get is, if it's in the brance to be built why doesn't koush himself compile a build and host it in rom manager. thanks for linking this tho
Click to expand...
Click to collapse
That's my concern as well.

CharlyDigital said:
Thanks for posting just rooted. I was waiting for clockwork to be posted. Not a fan of twrp.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
me either, installed, and seems to have went smoothly

Installed CWM and rooted with no problems.

Hmm, so I flashed over TWRP, but now in a boot loop in CWM.
If I reboot while pressing volume up I get into twrp, if I don't it automatically goes into CWM.
I can still browse through my files via twrp.
Any thoughts?

I've installed it, but I can't seem to pick up a zip from sd?
Anyone else have this issue?

[HOW-TO]Alter updater-script to flash 3.4 kernel based ROMs on lower hboots/firmware

Hi there.
As most of you already know, starting some time ago, CM team has decided to include a script check for firmware/hboot that will allow to flash a CM based ROM only on newer firmware/hboots (2.13.0000, 2.15.0000, 2.15.4444). This is valid for all 3.4 kernel based ROMs (CM 10.2, PACman, PA, Odyssey and so on). This check was introduced because some were reporting problems by flashing such ROMs on lower hboots and it was assumed that you MUST have the latest firmware in order to flash and run them.
This leaves few options for those having lower hboots: either upgrade to latest firmware OR not flashing the ROMs at all.
What if, someone has a lower hboot/firmware and IS able to run those ROMs without issues? The previous assumption that having lower hboot will make the ROM not working/booting is wrong...at least for me and I don't think I'm unique. I'm sure that there are more users having lower hboots that could run the latest ROMs without having to upgrade their firmwares. I'm on 1.06.0000 hboot S-On and I'm happy with it. I didn't had any single ROM flashed on my device that didn't run. I don't like the idea of being forced to upgrade (going through a procedure that for some proved to be difficult or bricked their phones) without needing to
Well there is still hope....
DISCLAIMER
PLEASE BE AWARE THAT I DO NOT RECOMMEND TO TRY THIS IF YOU DON'T KNOW WHAT YOU'RE DOING. EVEN IF FOR SOME USERS THE 3.4 KERNEL BASED ROMS WILL WORK ON LOWER HBOOT/FIRMWARE, CM DIDN'T PUT THAT CHECK THERE FOR NOTHING. I SHOULD NOT BE HELD RESPONSIBLE IF YOU FLASH SUCH ROM AND IT WON'T WORK. ALSO DO NOT REPORT ANY BUGS IN CASE YOU FLASH A ROM THIS WAY
Now, what people maybe thought already (but some don't know how to do it) is that you need to get rid of that script check in order to flash such ROM. Following the steps below anyone can get rid of the check and enjoy the newest ROMs without upgrading their firmware, presuming such a ROM will run on their firmware/device
Prerequisites:
In order to do this properly anyone will need two tools
- PPCGeeks Android Signer application (or similar) - DOWNLOAD
- Notepad ++ (or similar) - DOWNLOAD
Download and install both from links above then you're ready to go...
Steps to change the script & flash ROM:
1. Download the ROM of your choice and save it on your PC
2. Create a folder with a distinctive name (say CM 10.2) and extract the ROMs ZIP there
3. Look for the file "updater-script" located in \META-INF\com\google\android folder where you have previously extracted the ROM
4. Open the file using Notepad++
5. You will usually find the check for firmware at the beginning of the file and it'll look like something like below:
assert(getprop("ro.bootloader") == "2.15.4444" ||
getprop("ro.bootloader") == "2.15.0000" ||
getprop("ro.bootloader") == "2.13.0000");
That means that, only the users having hboot 2.15.4444, 2.15.0000 and 2.13.0000 will be able to flash that ROM, anyone else will be receiving an error and ROM won't flash
6. Delete those lines with Notepad++ then save the file
7. ZIP the whole ROM again and give the ZIP a name
8. Sign the ZIP with Android Signer then copy the signed ZIP on your phone's sdcard
9. Flash the ROM
This should do it and you'll be able to flash such ROM.
There is an alternative method of extracting the file from the ZIP, deleting the lines then putting it back in the ZIP...this will skip the unzipping and signing steps but depending on how you'll do it it could also give you script errors when flashing (Status 7 or Status 6 errors). Steps to be followed for this "quick" method are:
1. Extract the updater-script from the ZIP and save it on your PC
2. Edit it with Notepad++ like I've described above
3. Open the ZIP with WinRAR and navigate to the place where updater-script is (\META-INF\com\google\android) and delete it from the ZIP
4. Using drag&drop, take the modified updater-script and drop it onto the opened WinRAR window in the location where it should be. There will be a popup windows to confirm adding the file to the ZIP, just press OK.
5. Close the ZIP and flash it
Well many of you might already know and do this one way or another but there might also be some users that don't know how to do it and either ask for help in various ROM Development threads or just quit flashing the ROM
So this is for all those that would like to try the new 3.4 kernel based ROMs and don't know how to do it. It won't guarantee that such ROM WILL WORK on their devices, it just allows flashing it even if they don't meet the firmware requirements. If after flashing, the ROM won't boot or it'll boot loop, there's almost sure need for a firmware upgrade in order to run it.

Thanks rapier. This helps me tons.
I guess the only annoying part about it is that we have to delete those lines each time there's an update/nightly that comes out. But for the time being this will suffice until I have the luxury to upgrade my firmware.
Sent from my HTC One S using xda app-developers app

I too am on Hboot 1.06 and S-on and have never had problems with other ROMs. Being away from the community for several months i'm a bit bewildered by all the risky processes I have to carry out to get my phone to accept the new 3.4 kernel.
So I will give your method a try right away!
Many thanks

RichardW1992 said:
I too am on Hboot 1.06 ...
So I will give your method a try right away!
Click to expand...
Click to collapse
Have you had any success? I am very curious.
Thanks
Patrick

This looks interesting and looks much less complicated than the whole upgrade process.
I'm on HBOOT 1.13 and S-ON; I tried to flash CM 10.2 just for fun but I got the error message (script related).
I read that those who had no problem running the latest Trickdroid and Viper can use this ROM without upgrading their firmware. TD and Viper are the 2 latest ROMS I've been using.
I'm gonna try this this weekend or next week lol - although I prefer the features of Sense ROMS.

androidsigner doesnt work
after dragging the modified zip, it get "Unable to locate file"
---------- Post added at 09:54 PM ---------- Previous post was at 09:11 PM ----------
Ok so on a forum I've found that workaround - no extraction-rezipping-signing.
This is known about theme'd files, you cannot sign them even with command line. They must be opened with 7zip as not to break the signature and edited that way, then close and flash.
Click to expand...
Click to collapse
I did that, so I guess I dont need to re-sign the file
I'll flash another day, Im really tired
By the way, question : I deleted the 2.15 verification lines in the script updater, which moved the next line "mount .... etc" up to Line 2 (Notepad++)
Should leave it as it is, or move it to Line 1?
Thanks

salutcemoi said:
androidsigner doesnt work
after dragging the modified zip, it get "Unable to locate file"
...
Click to expand...
Click to collapse
This error is because AndroidSigner uses the Java JRE and it cannot find in on the path variable. Install latest Java JRE from official site and it'll work.
salutcemoi said:
...
Ok so on a forum I've found that workaround - no extraction-rezipping-signing.
I did that, so I guess I dont need to re-sign the file
...
Click to expand...
Click to collapse
You can extract the file, modify it with Notepad++ (or equivalent) and add it back to the zip using an archiving program (I use WinRar). No need for signing in this case
salutcemoi said:
...By the way, question : I deleted the 2.15 verification lines in the script updater, which moved the next line "mount .... etc" up to Line 2 (Notepad++)
Should leave it as it is, or move it to Line 1?
...
Click to expand...
Click to collapse
After deleting the check lines, the next line in the script should be on line 1 (no blank line at the beginning of the script)

Rapier said:
This error is because AndroidSigner uses the Java JRE and it cannot find in on the path variable. Install latest Java JRE from official site and it'll work.
You can extract the file, modify it with Notepad++ (or equivalent) and add it back to the zip using an archiving program (I use WinRar). No need for signing in this case
After deleting the check lines, the next line in the script should be on line 1 (no blank line at the beginning of the script)
Click to expand...
Click to collapse
thank you !
Much appreciated :good:

I did all the zipping/unzipping through my phone with the help of es file explorer. I got cm 10.2 sept 05 nightly to work but the only thing that's being funky is my wifi. I can turn on the Wifi and it scans all the available network just fine but after placing the password to my designated internet, it doesn't connect.
I'm not sure if it's this method of flashing roms or the way I performed my zip that's causing the issue.
Sent from my HTC One S using xda app-developers app

cougzzz said:
I did all the zipping/unzipping through my phone with the help of es file explorer. I got cm 10.2 sept 05 nightly to work but the only thing that's being funky is my wifi. I can turn on the Wifi and it scans all the available network just fine but after placing the password to my designated internet, it doesn't connect.
I'm not sure if it's this method of flashing roms or the way I performed my zip that's causing the issue.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Shouldn't be affected by the script change. This change only allows you to flash the ROM, nothing else. You can try a WiFi fix or reflash kernel for this kind of issue. I had CM10.2 running well on my phone and didn't have any problems with WiFi. Same for Odyssey ROM which is also Android 4.3 with same kernel as I know

hi
i've tried this metod to install cm10.2 over cm 10.1 on hboot 1.13 htc one s.
After flash rom+gapps and flash boot.img via fastboot i'm on htc logo bootloop
any suggestion?
Tnx in advice

I also had exactly the same issue with CM...could not fix it even after flashing kernels....gave up and went to AOKP ..now Wi-Fi works, still no 4g..but that wasn't working with CM either
Sent from my HTC One S using xda app-developers app

okaiuz said:
hi
i've tried this metod to install cm10.2 over cm 10.1 on hboot 1.13 htc one s.
After flash rom+gapps and flash boot.img via fastboot i'm on htc logo bootloop
any suggestion?
Tnx in advice
Click to expand...
Click to collapse
Same here
I'm also hboot 1.13
Sent from my HTC One S using xda app-developers app

I've read it in the forum for either AOKP or CM that lower HBOOT like 1.13 is going to cause bootloops....I was hoping that using this method, in the OP thread, I'd be able to upgrade to newer ROM...but I wasn't able to (bootloops)
Sent from my HTC One S using xda app-developers app

Bootloops mean you need to upgrade your firmware. This method is only for the rare few with lower hboots and newer firmware.

el_smurfo said:
Bootloops mean you need to upgrade your firmware. This method is only for the rare few with lower hboots and newer firmware.
Click to expand...
Click to collapse
Yup
I rooted my phone and flashed custom roms before the official JB firmware update.
Sent from my HTC One S using xda app-developers app

[MOD][CM11] Classic sdcard mount

This mod for CM11 on moto_msm8960 brings back the classic sdcard mount we know from devices like the Nexus One.
No more cluttering of /data with files which should go to sdcard.
Features:
- External sdcard mounted as /sdcard
- Internal memory fully available for /data
Installation:
- Have a nandroid backup of /boot and /system at hand if something goes wrong
- Simply flash the zip over your existing CM11 installation
- Wipe data is not necessary but will help if you have problems.
Deleting only the data of the concerned apps should be sufficient. (Only apps storing data on sdcard are effected)
- Files which were on the emulated sdcard can be found at /data/media/0. This is also the location where you have to put your zip files to be able to flash them with OpenRecovery.
Method:
Adjusting of following CM11 files to be in line with Nexus One example configuration according to:
http://source.android.com/devices/tech/storage/config-example.html
boot.img
- init.qcom.rc
- fstab.qcom
framework-res.apk
- storage_list.xml
See my github for details: https://github.com/S-I-M-O-N/android_device_motorola_moto_msm8960
Disclaimer:
This was developed and tested on a Photon Q but should work on all moto_msm8960 devices with CM11.
I cannot be held responsible if anything goes wrong while using this mod.
Thank you to everyone this work is based on: Cyanogenmod team for providing CM11, Google for providing Android and everybody else
Download
I will try to keep this thread updated and provide a flashable zip for the latest CM11 snapshot.
See attachment at the bottom.
Regards,
Simon
Downloads for:
cm-11-20140609-SNAPSHOT-M7-moto_msm8960.zip
cm-11-20140708-SNAPSHOT-M8-moto_msm8960.zip
cm-11-20140916-SNAPSHOT-M10-moto_msm8960_jbbl.zip cm-11-20141008-SNAPSHOT-M11-moto_msm8960_jbbl.zip
cm-11-20141112-SNAPSHOT-M12-moto_msm8960_jbbl.zip

Cool, Thank you

Any updated version for CM11 M8 build?

I am downloading M8 right now. Expect an update within the next days.
Until then it should be relative safe to flash the M7 sd-mod over CM11 M8, you will just miss the updates concerning the kernel and framework.
EDIT: Well, it's not. Stuck in Boot. Stay tuned for an update.

S-I-M-O-N said:
I am downloading M8 right now. Expect an update within the next days.
Until then it should be relative safe to flash the M7 sd-mod over CM11 M8, you will just miss the updates concerning the kernel and framework.
EDIT: Well, it's not. Stuck in Boot. Stay tuned for an update.
Click to expand...
Click to collapse
Yeah..I've tried it over M8 and my phone stucked in bootloop. Thanks for your work. I've missed my sdcard as primary storage since JellyBean days. I'm glad I can use my 32gb sdcard usefully.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app

Download for M8 added.

S-I-M-O-N said:
Download for M8 added.
Click to expand...
Click to collapse
Thanks a lot..Downloading it now.

Hmm so I'm guessing the likelihood of this working on nightly builds isn't good?

You could give it a try.
Nandroid backup boot and system, then flash the mod.
If it screws up, just go back and restore boot and system.
Apart of that I think we should wait a few days to see if we get a moto_msm8960_jbbl M9 build. If yes I will, make the patch for it. If no, I will pick the latest nightly.

After reading that we won't get a M9 build I made an update for nightly 20140814.
It seems the ramdisk is growing and abootimg was already complaining that it was too large. I had to delete copyrights and disclaimers to squeeze out some bytes. I hope that this trend does not continue, otherwise I need to find other means to bild the boot.img.
Regards
Simon

Please...!
A new version.
The M10 CM is out now for the Photon Q!
S-I-M-O-N said:
After reading that we won't get a M9 build I made an update for nightly 20140814.
It seems the ramdisk is growing and abootimg was already complaining that it was too large. I had to delete copyrights and disclaimers to squeeze out some bytes. I hope that this trend does not continue, otherwise I need to find other means to bild the boot.img.
Regards
Simon
Click to expand...
Click to collapse

Download for M10 added. Have fun!

Download for M11 added. Enjoy!

Are there any issues with this mod when flashing a new ROM? Say you're going from a snapshot build to a newer snapshot build, or even from a snapshot build to to a stable build?

Flashing a new ROM will overwrite the mod. So you are using the emulated sdcard on internal memory. Apps which stored data on the sdcard will not find their data, just like when you install the mod the first time.
Nevertheless if you stick to CM11 snapshots for which the mod has been adapted and you flash another release, just flash the mod for this release while you are still in recovery and you will have no problems.

Made the mistake of installing a nightly restored my backup. But can't get the classic sdcard back. Have re flashed no joy. Is there a way to get it back, with out doing a clean install?

Did you create the backup including the mod?
Did you restore system and boot?
Did you try to just flash CM11 M11 + MOD for M11?
Do you have bootloops?

YDid you create the backup including the mod?
No
Did you restore system and boot?
Not sure about the boot, will check.
Restored backup m11 and flashed sddcard mod.zip.
Do you have bootloops?
No
Might be a mute point.
The restore is eating my battery!
Doing a clean m10 updating to m11 Now.
Will install sdcard mod and see how it goes.
Thanks.
I should know here in the next 15 min.
OK!
With out flashing sdcard mod after m11 installed I now have
4 gig.
My guess is my back up was not m11 or JB bootloader?
Thanks for the fast reply!

The PQ has no KK bootloader, so every (working) ROM for the PQ is based on the JB bootloader.
As long as you haven't modified your /system after updating to M11 and flashing gapps and sdcard_mod, you should be fine by just do the same again.
But it's always risky, from a nightly to a snapshot. Downgrades are also risky and might not work.
You might just wait until M12 comes out and use your backup to restore it.

M12 is here