Database Info

[ROM][EBI1/32A] CyanogenMod EBI1/32A Port 4.2.4 [Nov 12]

This is a new thread for kernel ports of CyanogenMod 4.1.99 and greater versions only.
This kernel port will now work on any EBI1 kernel: this includes both the HTC Magic 32a and Rogers Dream.
If you wish to port earlier versions of CyanogenMod - please see Bcrook's thread. Bcrook has asked me to start a new thread for 4.1.99+ and ongoing versions as I've been doing the recent ports for it.
This is a kernel port from the 32b ION/HTC Magic/mytouch3g version of CyanogenMod that should work on any EBI1 (32a/rogers dream) device.
In most cases our hardware is identical, but we have twice the memory and so the kernel and wlan modules need to be rebuilt.
The steps for installing CyanogenMod on a 32a are much the same and are listed below for your convenience:
I have tested these steps personally, as have a number of people:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
NEW INSTALL (ie. never installed CM 4.1.99 or greater before):
Download HTC ADP 1.6 DRC83
(http://www.androidspin.com/downloads...ooted_base.zip)
Download CyanogenMod 4.2.4
(http://n0rp.chemlab.org/android/update-cm-4.2.4-signed.zip)
Download the Kernel Port file (see below)
Copy all three .zip files to your SD and reboot in recovery mode (press Home+Power at the same time or fastboot into your recovery)
Do a "Wipe data/factory reset"
Do a "Wipe SD: ext partition" ** (see below)
(it is recommended to wipe your Apps2SD partition for this release)
Apply Zip: HTC_ADP_1.6_DRC83_rooted_base.zip
Apply Zip: update-cm-4.2.4-signed.zip
Apply Kernel Port Zip: rad-4.xxxx.zip or bc-4.xxxx.zip
Reboot
Either grab some popcorn and watch adb lolcat as it goes past, or go do something else.. this might take a while
UPGRADE INSTALL (ie. already installed 4.1.99 or greater):
Download latest CyanogenMod update (now 4.2.4)
(http://n0rp.chemlab.org/android/update-cm-4.2.4-signed.zip)
Download the associated Kernel Port file (see below)
Copy both .zip files to your SD and reboot in recovery mode (press Home+Power at the same time or fastboot into your recovery)
Apply Zip: update-cm-4.2.4-signed.zip
Apply Kernel Port Zip: rad-4.xxxx.zip or bc-4.xxxx.zip
Reboot
Either grab some popcorn and watch adb lolcat as it goes past, or go do something else.. this might take a while
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The following Kernel Ports are available:
CyanogenMod 4.2.4 EBI1 kernel for 32a/Rogers Dream (recommended) (give thanks to bcrook for porting this one!)
Download: http://www.briancrook.ca/magic/bc-4.2.4-ebi1-signed.zip
md5: 174dd7403052f9173660b817232b47e6
Older kernel ports:
CyanogenMod 4.2.3.1 EBI1 kernel for 32a/Rogers Dream (now with USB tethering!)
http://fdsfiles.com/temp/rad-4.2.3.1-EBI1.zip
(md5sum: 0d52bc8986e11c0382b3f6336d6d71d4)
CyanogenMod 4.2.2 EBI1 kernel for 32a/Rogers Dream with no BFS
http://fdsfiles.com/temp/rad-4.2.2-EBI1.zip
(md5sum: 38c52bedceef516a03bd07e034ae9b13)
CyanogenMod 4.2.1 EBI1 kernel with no BFS
http://fdsfiles.com/temp/rad-4.2.1-EBI1.zip
(md5sum: 39c536b93425f8c1f94bc79cc97b9baf)
CyanogenMod 4.2 EBI1 kernel with BFS 304
http://fdsfiles.com/temp/rad-4.2-bfs-ebi1.zip
(md5sum: 8875e2e8a25d394455f2d4864d9c6c67)
CyanogenMod 4.1.9999 EBI1 kernel with BFS 304 (now with full EBI1 support and fixed ramdisk)
http://fdsfiles.com/temp/rad-cm4.1.9999-EBI1.zip
(md5sum: 48e4d30e81c0b531e00dde05d1108416)
CyanogenMod 4.1.9999 with BFS 304 (Hacked - doesn't work for Rogers Dream)
http://fdsfiles.com/temp/rad-4.1.9999-32a-bfs304.zip
(md5sum: 54c225da975a08ae8cf7e006e97caf41 )
CyanogenMod 4.1.99 and 4.1.999 with BFS 303 (N.B. this port file will work fine with both releases - Cyanogen's just catching up to me
http://fdsfiles.com/temp/rad-4.1.99-32a-bfs303.zip
(md5sum: ced37f39fd419a4b11fa3f64eb7f93e9 )
CyanogenMod 4.1.99 with BFS 302:
http://fdsfiles.com/temp/rad-4.1.99-32a-bfs302v3.zip
(md5sum: 2b33a2d57b1497c167e50dfbec23953f )
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Please Note: I have started including AudioPara4.csv in my package once more as it does seem to be needed.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
HTC IME: Hero Keyboard
For those who want the HTC IME back you need to download HTC_IME.apk and Clicker.apk from here:
http://n0rp.chemlab.org/android/apps
then either ADB install them or use an app like ASTRO to install them.
Do not use any other versions of HTC_IME - they will force-close.
Then go to Menu->Settings->Locale and Text->Touch Input and activate for it to appear, then long press on a text box to switch to it by default.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Special thanks go to Cyanogen, bcrook, TigerTael, Amon_RA, jerpelea, hakyuro, TheStrider, redglasses, and all the people who have contributed towards making these roms possible for us.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
** After a bit of inspection it looks like no 32a recovery rom has this option at present.
if your recovery rom doesn't have the option 'Wipe SD: ext' then you can duplicate it by doing (while in your recovery rom):
$ adb shell
# mount /system/sd
# rm -rf /system/sd/*
# unmount /system/sd
Click to expand...
Click to collapse
Basically this is done to make sure you have no previous apps, nothing to foul things up and you're truly starting from scratch.

[Reserved for future use]

Hello,I flashed my HTC Magic(32A) using signed-google_ion-ota-14721.zip, which I download here:http://developer.htc.com/google-io-device.html.
Then,My phone can't boot into normal mode and can't boot into recovery mode too.
Do you known how to repair it?

Thanks~support you~!

imake said:
Hello,I flashed my HTC Magic(32A) using signed-google_ion-ota-14721.zip, which I download here:http://developer.htc.com/google-io-device.html.
Then,My phone can't boot into normal mode and can't boot into recovery mode too.
Do you known how to repair it?
Click to expand...
Click to collapse
How did you try to reboot in recovery mode? Have you tried using fastboot? You don't have to write the recovery image to the phone, you can use fastboot.
Basically you turn off the phone, then press the Back+Turn on keys and you should be in fastboot.
Then at the computer cd into the directory where you have the recovery image then type:
fastboot boot <recovery.img>
(replace recovery.img with the actual recovery image name; make sure the phone is connected via usb to the computer and adb "sees" it, check with adb devices).
Then you should be able to follow the procedure as described in the first post.
If you didn't copy all the zips on the memory card first, you need to take out the memory card and use a card reader to copy them first.
Hope this helps!
S.

siancu said:
How did you try to reboot in recovery mode? Have you tried using fastboot? You don't have to write the recovery image to the phone, you can use fastboot.
Basically you turn off the phone, then press the Back+Turn on keys and you should be in fastboot.
Then at the computer cd into the directory where you have the recovery image then type:
fastboot boot <recovery.img>
(replace recovery.img with the actual recovery image name; make sure the phone is connected via usb to the computer and adb "sees" it, check with adb devices).
Then you should be able to follow the procedure as described in the first post.
If you didn't copy all the zips on the memory card first, you need to take out the memory card and use a card reader to copy them first.
Hope this helps!
S.
Click to expand...
Click to collapse
Hi,thanks.But when I press the Back+Turn on keys, my phone boot into a htc magic screen,not the fastboot mode.

Do we also need the two extra reboots?
9- Once at home screen.....Reboot 2 more times. This will mix everything together, just like making soup =) You will get the true speed of this rom.
Click to expand...
Click to collapse

Thank's Radix999....great work's !!!!

BUGabundo said:
Do we also need the two extra reboots?
Click to expand...
Click to collapse
I would say yes as this thread only adds the 32A kernel and I doubt the requirement of booting 2 more times has anything to do with the kernel.
On the other hand, I've rebooted actually more than 2 times (for other reasons) and it doesn't seem faster to me. Too bad cyanogen didn't say what exactly will/should be faster so that we can test.

so my journey is finally complete.
in the past 24 hours since the update came out, i have managed to :
1. brick my phone
2. sent it for warranty repairs
3. live (like an undead) for a bit without my beloved 32A magic
4. gotten back my 32A magic
5. figured out how to restore my old nandroid of 4.1.11.1 while still keeping the perfect SPL (i am still on .0010)
6. gotten 4.1.99 to work without wiping (still lost my my HTC_IME dictionary which is a minor thorn is the behind)
7. will live happily ever after.
so thanks for the people who figured out what to do. what are the steps.
mad mad props goes out to Radix999 for the porting files.
now for my lockscreen and black status bar

What about all the google programs, this might be a stupid question. Think i have read somewhere online that we who have google programs need to take a backup of those or else they want be "transfered" to the 4.1.99 ROM. Am i right or just me that haven't understood anything?
Per

str4vag said:
so my journey is finally complete.
in the past 24 hours since the update came out, i have managed to :
1. brick my phone
Click to expand...
Click to collapse
how the heck did u do that?
did u get that ION roms that applied a radio update?

perevers said:
What about all the google programs, this might be a stupid question. Think i have read somewhere online that we who have google programs need to take a backup of those or else they want be "transfered" to the 4.1.99 ROM. Am i right or just me that haven't understood anything?
Per
Click to expand...
Click to collapse
cyanogenmod installer extracts it from the oficial ROM, thats why you need to install that 1st!

BUGabundo said:
cyanogenmod installer extracts it from the oficial ROM, thats why you need to install that 1st!
Click to expand...
Click to collapse
Ahh, thanks alot

It's all done transparently by Cyanogen's install script.

BUGabundo said:
how the heck did u do that?
did u get that ION roms that applied a radio update?
Click to expand...
Click to collapse
yea..basically that..thank god it was covered by the warranty..

I'm just curious....is there a version of this rom that doesn't require apps2sd (and by extension, doesn't require a partitioned sd card) ?
The reason I ask is since it's for a 32A board, is it really necessary?
Thanks for any info.

Err, I don't think it requires apps2sd. You're right, most 32a users don't need it. It will install automatically should it find the ext partition on the card, but it's not required. I'd be interested to know if otherwise.
DT

Wipe SD and loose Apps?
Radix999 said:
[*]Do a "Wipe data/factory reset" and then a "Wipe SD: ext partition"
(it is recommended to wipe your Apps2SD partition for this release)
Click to expand...
Click to collapse
I understood everything about the instructions for the ROM update except this one.
I have cyanogen's recovery 1.4 and I can't find the Wipe SD: ext partition option. By this you mean that we have to manually wipe the partition on a linux OS or that there's a recovery ROM with this option? If we have to wipe it we will loose our installed apps that we had before, right?
Thanks for your work radix!

To be quite honest, I don't know how to wipe the ext2/3 partition for the Apps2SD users - I'm just using the instructions from the mytouch3g installs and they did recommend any partition you may have.
If you have an Apps2SD partition you'll need to figure it out (you'll probably find you can 'adb shell' in Amon_RA's recovery rom and there's a script for formatting your apps2sd partition somewhere, but you'll need to check with his recovery rom and what's included)
Personally I don't use Apps2SD and never will
And for the record I'm still using Amon_RA's 1.2.0 recovery - never bothered changing as it works fine for me

[recovery] CWM for Betelgeuse v0.3 - Now with USB support

I have made some modifications to the famous ClockworkMod recovery that enable to chose internal storage or sd-card for backup and flashing. I think this is quite useful. I also want to try to add usb-drives to this list, but that will take some more coding.
The source code is availlable in my gihub.
WARNING: USB does not seem to be hotplugable. Plug before boot and don't remove till reboot. I managed to get a complete lockup (had to remove battery to get out) by not obeying this.
USB Disk must have exactly one vfat partition.
Download v0.3:
Image file
update.zip (flash with ClockworkMod as included in CM7)

Changelog
v0.3
- Add USB support
v0.2
- Based on ClockworkMod Recovery v3.0.2.8
- Add menu items to chose sd or internal drive

Your idea is great and keep up!!! I'll flash your recovery when its become more stable. I just make it usable after lots of problems and I want to brick it again. I think you understood me.
Sent from my Folio 100 using Tapatalk

Dual boot command in CWM possible ?
MBlaster
First of all, thank you for your work and efforts.
Since you seem to be familiar with adding features to CWM, I have one question : would it be possible to add a menu-entry for choosing an alternative boot (like for example ubuntu installed on a SD-Card ...) ?
Regards,
eRaph

v0.3
- Add USB support
Have Fun!

mblaster said:
I have made some modifications to the famous ClockworkMod recovery that enable to chose internal storage or sd-card for backup and flashing. I think this is quite useful. I also want to try to add usb-drives to this list, but that will take some more coding.
The source code is availlable in my gihub.
WARNING: USB does not seem to be hotplugable. Plug before boot and don't remove till reboot. I managed to get a complete lockup (had to remove battery to get out) by not obeying this.
USB Disk must have exactly one vfat partition.
Download v0.3:
Image file
update.zip (flash with ClockworkMod as included in CM7)
Click to expand...
Click to collapse
Thanks for this job. Just a question: what is the procedure for recovery update ? I start with a stock rom rooted and with recovery from foliomod1.4 installed via ADB.
Thanks
miazza

Hello to everybody. I need this recovery but the links are boken. can someone help by reaupload or send as PM.
Thanks

4EXT Recovery Classic v2.2.7 RC5 | TAR BACKUPS | 4EXT Recovery Control | Convert FS

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Quick note about themes:
Available themes as of Oct/17:
Themes by pravus_nephilim
Themes by Apaquette420
Themes by Whiskey103
Themes by Amresh
Themes by Apaquette420
Themes by CWhitney24
Themes by DaMyth
Themes by Blindndumb
To uninstall any "flashed theme" and to revert to your own custom settings you had before flashing, just use this Theme Uninstaller in recovery.
It will clear any theme you might have flashed and revert to your own custom settings you had before flashing that theme!​​
THANKS:
All credits and my deepest respect go to Koush for his extremely great code!
Without him 4EXT Recovery wouldn't have been possible!
Biggest thanks possible go to Sebastiaan15 for his brilliant ideas and who spent whole weeks testing my buggy code with his Desire
Without you I could never have made it!!!
So BIG THANKS to SEBASTIAAN15 and KOUSH for his hard work with CWMR !!!
Many credits to the Desire S community ( especially to loveboatcaptain - LBC Mod Android Development and Marylandcookie ) for testing, very nice ideas, feature suggestions and helping to get the code running on the Desire S!
Special big thanks to RAVENNA from android-hilfe.de board for hours of testing for the Desire!
BIG Thanks to Hussainmushahid who helped me a lot spending much of time with solving a bug I could not reproduce on my device.
And many thanks to all users who reported and helped to identify problems ( can't any longer list all of you here since the list has grown too large )!
Even more thanks to people who 've bought me some beer YOU ROCK!! ZEEKIZ, A USER, PHILOS64, STEVEATHOME, PREACHER65, BEN_PYETT, ULTRA DROID, PTR_HAMILTON, BEANBEAN50, SEBASTIAAN15 and LOVEBOATCAPTAIN
​
v2.2.6 RC4 Released: Oct/01
Rare Superuser problem when tar backups were enabled (disabled by default) was fixed.
Converting partitions between ext3 and ext4 without data loss now correctly calculates the space needed to successfully complete the operation
New option: check and optionally repair the file system on your sdcard (fat32)
Removed duplicate format cache option inside the format menu (wipe cache does the same)
When formatting fat32 it will now save your 4ext.prop settings and restore them afterwards
Changed partitioning of the sdcard to not use LBA mode for new fat32 partitions as requested by Ghiki
Added new size option (128mb) to the partitioning menu per request
Parted is no longer used to format fat32 in the partition menu
-> This solves a bug where sometimes the creation of the fat32 file system failed and produces better quality results​
4EXT Recovery themes should now stay when formatting /system or flashing new roms
New option: format /sdcard fat32
New 4EXT Recovery Control API because I'm forced to drop "extendedcommand" (see App for the reason why)
enables file names and directories to include spaces for installations​
calculates needed space to complete a full or advanced backup at the beginning of the backup.​
This ensures that you are not left with a non working backup.​
Size for recovery greatly reduced
New 4EXT Recovery Control Features
Please see www.4ext.net for more.
Fix permissions
Calculate real values for the space needed to create a new full or advanced backup
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.​
As an example, the following would be possible to do in just one session:
Restore a backup, set to create a backup / advanced backup before the restore,
format all partitions with a file system of your choice before the restore process starts,
flash additional zip files afterwards, fix permissions and select to stay inside recovery or to reboot automatically once all actions are complete.​
Features: Use 4EXT Recovery Control or Recovery Updater for complete Changelogs and Known issues!
not all features may be relevant for all devices
Displays additional information:
Identifies your current rom and displays its name
Current filesystems on your partitions
Free space remaining of all of your volumes
Current battery charge level
Backup | Restore:
Correctly calculates free space needed to complete a backup ( version > 2.2.6 RC4 )
Tar backups (can be switched on or off)
Complete CWMR5 compatibility
All Backups you create will be named after your currently installed Rom for easier identification.
Never unwillingly get "downgraded" to EXT3 again
Always restores backups using the file systems you HAD on your partitions at the time of creation!
-> all partitions formatted with ext4 at that time, will be restored to ext4. The same is true for ext3.​
You can manually change any existing Backup to ext4 or ext3
-> so that after a restore, all partitions and up with the file system you wanted!​
Advanced Backup: backup only a single partition
Convert any of your partitions to EXT4 or EXT3 without data loss.
Formatting:
When you wipe or format it will always use the same file system you currently have.
-> but you can change that​
When you format ext4 it will always create an aligned file system
Correctly identifies unformatted sd-ext partitions
-> if it finds one it displays a warning and suggests you may format them by visiting the 4EXT menu​
Filesystem check and repair option in advanced menu
Partitioning:
Alignment check of your partitions
Full support for up to 2 sd-ext partitions + swap (Backup/restore/format/convert, fsck, et.c.)
(RE-) Partition your sdcard for sd-ext without removing your fat32 partition.
All partitions created with 4EXTRecovery will be perfectly aligned to 4k
Installing:
Integrated md5sum checking option
Themes:
Customize all colours used throughout recovery
Use your own icons, background images, progress bars.. more to come.
Assign different backgrounds to different menu categories (version >= 2.1.2)
Create a flashable zip for others to flash your theme.
Menus:
Most popular menu items rearranged
Format menu
Power Menu + option to reboot into bootloader
Less "No's" in confirmation dialogues
Changed Advanced Restore: first select what you want to restore, then select the backup
-> Useful for restoring from "Advanced Backups"​
4ext.prop:
Configuration file on your sdcard where you can set options to be used by 4EXTRecovery
Change all settings conveniently with 4EXT Recovery Control
Many more options to come
Share your settings / themes by packing your config into a flashable theme
Other stuff:
USB Storage Autostart (must be switched on)
Mount usb storage exposes all partitions on your sdcard to the os (not just fat32)
-> you could even partition your sdcard from your PC while connected via USB​
Switch haptic feedback on/off
You don't need to reboot recovery if you transferred a file to show up in the install menu.
-> This bug affected only some users with either CWMR or previous versions of 4EXT.​
Button backlights (Desire S, Desire HD and Incredible S only)
​
Download:
All downloads are now available through 4EXT Recovery Updater. It's free, no ads, no tracking, no nothing, don't worry
.. and of course via 4EXT Recovery Control
This ensures that your downloads are ok by automatically verifying md5sums and that known issues and changelogs are easily accessible
It also notifies you when there are any new critical bugs found
Recovery images will be uploaded for download soon too, but they can also be acquired easily by using Updater or Control.
You can for example just download a recovery.zip containing the image. The download will be automatically verified for correct md5sums!
4EXT Recovery Control
Free version: Recovery Updater
Fully featured version: 4EXT Recovery Control
For a list of its many features, visit www.4ext.net
Some examples :
Flash as many zip files you want in one go
Automatically calculate and display the md5sums of all zip files you are going to flash
Check your backups' health to ensure they will restore later when you need them, by verifying their md5sums!
Optionally, but highly not recommended:
If md5sums don't match but you REALLY NEED that backup BADLY, you might want to restore it anyway.
You can you this app to fix the md5sums of a given backup to "forcefully" restore it!​
Calculate real values for the space needed to create a new full or advanced backup
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.​
Identifies and adds your romname so you don't need to type so much when chosing a meaningful name for your backup
As an example, the following is possible to do in just one session:
Restore a backup, set to create a backup / advanced backup before the restore,
format all partitions with a file system of your choice before the restore process starts,
flash additional zip files afterwards, fix permissions and select to stay inside recovery or to reboot automatically once all actions are complete.​
Much, much more! See www.4ext.net
Recovery theming
Uninstall and Install themes with live preview and the option to change their colours without the need to reboot into recovery.
Change all colours with live preview and a nice colour picker.
​

great job....
just converted a ext3 data img to ext4 without loosing any data.
perfect mod.
now we have 3 cool recovery mods... could you merge j_r0dd´s menu redesign and arco´s advanced backup options?
sources:
[MOD-RECOVERY] Clockworkmod Recovery modded Versions.
arco: https://github.com/arco/
j_r0dd: https://github.com/zyonee/android_bootable_recovery
would be great to have this all together...
could you please also share your source code on github?
regards and thx

loveboatcaptain said:
great job....
just converted a ext3 data img to ext4 without loosing any data.
perfect mod.
now we have 3 cool recovery mods... could you merge j_r0dd´s menu redesign and arco´s advanced backup options?
sources:
[MOD-RECOVERY] Clockworkmod Recovery modded Versions.
arco: https://github.com/arco/
j_r0dd: https://github.com/zyonee/android_bootable_recovery
would be great to have this all together...
could you please also share your source code on github?
regards and thx
Click to expand...
Click to collapse
Thank you very much!
Yes I will post them, but please give me 2-3 days (max.). Don't have much time at the moment because of very much work and I'd like to update it first with current code
Edit: yes I can merge them/add those changes

madmaxx82 said:
Thank you very much!
Yes I will post them, but please give me 2-3 days (max.). Don't have much time at the moment because of very much work and I'd like to update it first with current code
Edit: yes I can merge them/add those changes
Click to expand...
Click to collapse
wooohooo
this beer is yours if you could merge all 3 versions to a superhero custom recovery
take your time... i know what you mean... job, family and cooking rom´s for android is hard work
if you need someone to test... i´m your man, or just share your github. i´m able to compile it myself for desire s
regards and 1000 times thank you

loveboatcaptain said:
wooohooo
this beer is yours if you could merge all 3 versions to a superhero custom recovery
take your time... i know what you mean... job, family and cooking rom´s for android is hard work
if you need someone to test... i´m your man, or just share your github. i´m able to compile it myself for desire s
regards and 1000 times thank you
Click to expand...
Click to collapse
Hahaha
Okay, I took a look at the features.
An Advanced backup is an extremely good idea!!
And as it won't need so much code not already there from Koush, it shouldn't take long I hope
Well nothing I did required so much additional code. CWMR already has so many great functions you can use, biggest respect!
A wipe menu with all the wiping is also a really nice idea.
But full wipe?/system/data and cache? Could you give any example when someone would need that?
BTW: I don't even have a github account yet
I will send you the source as soon as I got it done, then do some cleaning, register and upload it.
Good night

Looking forward to the updates madmaxx82

madmaxx can you make this recovery for the desire

Good morning
Although I should really get to work You motivated me enough that I was excited trying out the advanced backup recovery.
I repacked it with an IS kernel and tried the advanced backup function.
I saw that if you do an advanced backup, it creates a backup folder named like any other full backup.. so you wouldn't know it contains only one partition..
and when you want to restore that, you would also need to use advanced restore and know which (lonely) partition was backed up in which folder ..
if you select the wrong one it fails and you also don't know which one it was just by using the menu..
I have some suggestions, please tell me what you think would be best:
- Create a distinct folder structure for advanced backups like that:
/sdcard/clockworkmod/backup/advanced/data
/sdcard/clockworkmod/backup/advanced/system
/sdcard/clockworkmod/backup/advanced/cache
/sdcard/clockworkmod/backup/advanced/boot
/sdcard/clockworkmod/backup/advanced/.android_secure (do we need that?)
So when you did an advanced backup of data it would create the usual <date-time> folder, but inside /sdcard/clockworkmod/backup/advanced/data
- Just create /sdcard/clockworkmod/backup/advanced/ and put all advanced backups in there..

sebastiaan15 said:
madmaxx can you make this recovery for the desire
Click to expand...
Click to collapse
Yes, but extremely busy at the moment
I don't know what to do first (very inconsequent type of person ).
-work
-add those features
-desire
Porting for the desire wouldn't take long I guess.. hmm

madmaxx82 said:
Yes, but extremely busy at the moment
I don't know what to do first (very inconsequent type of person ).
-work
-add those features
-desire
Porting for the desire wouldn't take long I guess.. hmm
Click to expand...
Click to collapse
just asking
-work
-desire s ->add those features
-and if you have some free time the desire or not no hard feeling
but keep up the good work

sebastiaan15 said:
just asking
-work
-desire s ->add those features
-and if you have some free time the desire or not no hard feeling
but keep up the good work
Click to expand...
Click to collapse
Thank you

Thanks!
Working fine
(used only mount, converted data to ext4, backup, wipe cache and apply zip so far)

dont know said:
Thanks!
Working fine
(used only mount, converted data to ext4, backup, wipe cache and apply zip so far)
Click to expand...
Click to collapse
Thanks for the feedback and testing.
Did you install using the "OneClick" method maybe and could confirm this works?
Can't think of why it shouldn't but I can only test it on the IS..
The rest of the recovery should really work as it does on the IS as everything but the button-lights is the same on both devices..

madmaxx82 said:
Thanks for the feedback and testing.
Did you install using the "OneClick" method maybe and could confirm this works?
Click to expand...
Click to collapse
Did flash it via recovery...

I flashed via recovery too, converted all to ext4(they had all been converted to ext3 by a restore) and its now definately quicker. Backed up by an extra 200 points in quadrant

Tried the oneclick all appeared to go ok and booting into recovery showed new version!
(log shown below)
ECHO is off.
ECHO is off.
ECHO is off.
pushing files with adb..
ECHO is off.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1157 KB/s (92632 bytes in 0.078s)
1571 KB/s (5154816 bytes in 3.203s)
ECHO is off.
ECHO is off.
writing recovery..
ECHO is off.
removing leftover files..
finished
No Errors? Then it should have worked.. reboot into recovery to check
Press any key to continue . . .

ben_pyett said:
Tried the oneclick all appeared to go ok and booting into recovery showed new version!
(log shown below)
ECHO is off.
ECHO is off.
ECHO is off.
pushing files with adb..
ECHO is off.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1157 KB/s (92632 bytes in 0.078s)
1571 KB/s (5154816 bytes in 3.203s)
ECHO is off.
ECHO is off.
writing recovery..
ECHO is off.
removing leftover files..
finished
No Errors? Then it should have worked.. reboot into recovery to check
Press any key to continue . . .
Click to expand...
Click to collapse
Thank you for testing

Malooga said:
I flashed via recovery too, converted all to ext4(they had all been converted to ext3 by a restore) and its now definately quicker. Backed up by an extra 200 points in quadrant
Click to expand...
Click to collapse
Glad it could help you Thanks for the feedback

madmaxx82 said:
Glad it could help you Thanks for the feedback
Click to expand...
Click to collapse
Guess it was worth it in the end then?

Could I suggest that it might be worth getting LBC to incorporate a link to this thread and excellent recovery from within the already existing [RECOVERY] sticky, preferably within the first post.
Unless you want to request that the moderator smokestack76 makes this another sticky.

[EXPERIMENTAL] MultiROM v19 (discontinued)

This project is now discontinued and will recieve no further updates nor support.
First of all, thanks petter (https://github.com/havlenapetr), Czech Samsung Galaxy developer, for idea and source codes.
What do I mean?
You have one ROM in internal memory as usual, and another one in folder on SD card ext partition. You can easily switch between them - just move rom from ext partition to some backup folder.
See guide in second post
How is it done?
Lets look on how android boots - its (roughly) like that:
1. Bootloader - forks between recovery, fastboot and normal boot
2. Linux kernel - Unpacks its initrd, loads drivers and many more things, not important now
3. Init - kernel runs this program, which mounts android partitions, sets correct permissions to files, starts services, and in the end, starts android itself
4. Android - Dunno much about it yet, anyway not important now​
So, what we need to do is mount something else than internal memory in init. Init parses & runs simple scripts, which makes it simpler to mount sdcard folders.
We need to add mknod and bind mounting to init binary. Unfortunately, we dont have sources of init modified by LG (that thing is three(!) times larger than init compiled from AOSP, what the hell is in there?!). That is solved by running modified init, which parses "preinit.rc" with mounts and then runs LG init.
Commit: https://github.com/Tasssadar/init/commit/aa3604ca90f5ef9b688fdc2e3cc865aa29a54809
preinit.rc: https://github.com/Tasssadar/init/blob/b4e701e8bc4831fadbefa64be48300139dcc2023/ramdisk/preinit.rc
This would be all, if original LG init would not remount /system and /data from internal memory. Also, nearly every ROM has different init.rc, and wont boot without it.
To solve this, I created "import_boot" command in init, which copies *.rc files and LG init from ramdisk(well, its only folder with these files extracted from ramdisk for now) on sdcard ext partition. This command also puts comments out every line with mount /data, /system or /cache in init.rc file, so LG init wont remount them.
Commit: https://github.com/Tasssadar/init/commit/dc3fa50d65d1221a4fb819d8ee616765ee043e83, https://github.com/Tasssadar/init/commit/f7bc141b1e4b7d214e49d4bb005c71237231436c and https://github.com/Tasssadar/init/commit/1cde6b6a093d4ac1f961e610c5229605bc517b52
Format of ROM on ext partition:
All files from paritions in internal memory copied to sd ext partition with preserved owners and permissions(!).
So, when I copy data, I do "cp -r -p /data/* /sd-ext/multirom/rom/data/" (I suggest to run this via adb shell while in recovery).
Currently, I mount /system, /data and /cache from sdcard. If one or more of these folders does not exist, its equivalent from internal memory is used.
It would be nice to have *.img files from nandroid backups instead of this, but as far as I know, they cant be just mounted.
As for *.rc files, I put them into /sd-ext/multirom/rom/boot folder. I would like to just copy boot.img and extract files in init, but I did not find way to extract it when I have hardly STL usable in init. I'd like to use kernel's internal decompressor, but I dont know how.
Limitations
- Both ROMs must be compatible with one kernel - kernel is already loaded in init
- ROMs must be for same baseband, obviously
- Kernel modules(wifi, for example) of both ROMs must be compatible with one kernel. That can be easily solved by copying modules from one ROM to another, though.
- It will be slower than internal memory.
Integration with recovery
Definitely possible & usefull. This is integration in my modified AmonRa recovery: https://github.com/Tasssadar/Amon-R...mmit/bd0232f7379993c296b0223973b81e8c55dc3ee2
Security risk
/system on sdcard can't be mounted read-only - I'd have to mount whole sdcard read-only. This is possible security hole, but you cant do much without root anyway, because of permissions. And if you have root, it does not matter if its read-only or not.
Conclusion
So, it is possible to have dual-boot. You can use it to develop ROMs(you can directly edit data in /data and /system), as backup ROM when you are testing something in internal memory which does not boot, and you need to call someone or when our devices will be so old that bad blocks in internal memory wont allow us to boot
But, as you can see, It is not something that average user could do, at least not yet. Maybe I could modify recovery to do everything for the user (copy data from /system, /data and /cache, extract *.rc files from boot) and create some flashable ZIPs which would modify the init.
But there are some problems - some ROMs may not be compatible with this and there are multiple recoveries out there, but theres not single one which is only for our phone - both AmonRa and ClockworkMod are developed for wide range of devices. Yes, both of them can be modified, but I doubt they creators would accept such inflexible and device-specific thing.
What do you think, is it worth it?
Tested ROMs (first one is in internal memory, second one is on SDcard)
Working:
Megatron and stock v10a ROM - stock rom is slow
Megatron and devoid #froyo-final - like ten times faster than stock xD
LightRom(2.2.2) and devoid #froyo-final (and vice versa)
Megatron and Megatron - both ROMs can have a2sd
Megatron and Mik's CM7 6.5.8 - since v2
Gingerbread 2.3.4 from Optimus Net and CM7 6.6.1 (thx eduardogouveia for testing)
Stock 2.2.2 and CM7 6.5.8 (thx eduardogouveia for testing) - if you have ext4 partition, you need custom kernel for stock ROM.
.void 2.3.4 and stock V20B (thx diazneoones for testing)
CM7 6.5.8 and .void 2.3.4 (thx diazneoones for testing)
CM7 nightlies and Lupohirp's СM9 (thx aquapp for testing)
Not working
None found yet, but when CM7 is on sdcard, it looses root. Trying to figure out why. - fixed in v10
PS: I hope I explained it correctly, not exactly good at this. Do not fear to ask, if you don't understand something.

OK, here goes guide for average user. This is still highly experimental feature, keep that in mind. Backup, backup backups and backup them to PC, read whole guide first, I am not responsible for your bricked phone etc.
GUIDE:​1. Requirements
Ext4/Ext2/Ext3 partition on SDcard big enough to hold all files from /system and /data, which is from 170mb to 400mb (depends on ROM and apps installed), so I think 512mb partition is minimum (if its 90% or so free).
Modified recovery. Only AmonRa and CWM version is available at this time, TeamWin is coming "soon". You can find flashable zip at the bottom of this post, flash it before you proceed to next move. If something goes wrong, you can restore your recovery with zips from here.
Kernel with ext2/3/4 support, which is basically every but stock
Both ROMs you wanna use must be compatible with same kernel. See Limitations in previous post
2. MultiROM instalation
- Via MultiROM Mgr application
I recommend you do nandroid backup before installing via this app.
Download MultiROM Manager (link at the bottom of this), tap to "Tap to install via this app" and wait. As simple as that. Mgr will also install recovery for you (It will ask you which one, you can select AmonRa, CWM and none). App can check & install update, too.​- Via recovery
Just download multirom.zip at the bottom of the post, make nandroid backup and flash it. Your current ROM will be the one in internal memory, we will setup the one on the SDCard in next move.
Now, try to reboot the phone (boot will take little longer, because it has to mount ext partition). If it boots up correctly, then its OK - your ROM is supported. If not, then restore your nandroid backup and post your ROM name here, maybe I'll try to make it working.​
3. Setup ROM on the sdcard
Make nandroid backup (I am not kidding, you will need this one), flash ROM which you wanna to have on SDcard, do the first boot (because it will create dalvik-cache, and you dont wanna do that when its already on sdcard) and reboot to recovery again.
Go to "MultiROM options" menu and select "Create from current ROM". It will do everything for you (it takes time, though). ROM on the sdcard is placed in /sd-ext/multirom/rom/, backups are in /sd-ext/multirom/backup/.
Restore nandroid backup from beggining of this step and reboot. Wait until Boot manager shows up, and select SDcard as boot location. ROM from sdcard should boot. If your ROM from internal memory boots or if its stuck, something got wrong and you should restore from backup.
4. MultiROM recovery menu description
Active/deactive state is for recovery only, you can boot ROMs from backup in boot manager - that means its N-times boot rather than dual-boot.
When not active(boot from internal memory):
Activate (move from backup) - when you already have backup, this will move it to active folder (fast).
Activate (copy from backup) - same as above, but it copies it instead of moving
Create from current ROM - pretty self-explanatory
Create from ZIP file - see http://forum.xda-developers.com/showthread.php?p=22194117#post22194117
When active(boot from sdcard):
Deactivate (move to backup) - Moves current ROM to backup folder, so next boot will be from internal memory
Backup - Creates backup of current ROM
Erase current ROM - Deletes current rom, next boot will be from internal memory
Copy modules from int mem - Copies modules from ROM in internal memory to SDcard. Try this if WiFi does not work in SDcard ROM.
Flash ZIP - flash ZIP file to ROM on SD card, for example gapps.
5. Config file:
It is recommended to use Multirom Manager(see bottom of this post) to change config file.
File itself is placed on sdcard and its name is multirom.txt. Description of its contents is in this post(post is updated if something changes): http://forum.xda-developers.com/showthread.php?p=20045183#post20045183
6. Key bindings:
Since v11, you also can control MultiROM via touchscreen.
Anywhere: Hold Power button to shut down the phone
While on main screen:
VolUp/Down - list between actions
Menu - Confirm action
Back - Reboot to recovery
Power button - Sleep mode
While playing tetris
VolUp - return to main screen
VolDown - pause
Menu - move the piece to left
Home - hard-drop
Back - rotate piece
Search - move the piece to right
FAQ:​Q: It is slow!
A: Its sdcard. It just is slower than nand memory.
Q: It does not work with my ROM
A: Post your ROM combination here, maybe I'll see to it.
Q: When do I need to reflash?
A: When you flash new ROM or do something which rewrites boot partition. Most (if not all) kernels are using Koush's AnyKernel, so they should not cause any problems.
Changelog & Download:​(Always flash newest version)
Uninstaller: http://www.mediafire.com/?3eco51f2t0at77o (info here)
Changelog AND DOWNLOAD LINKS have moved to github: http://tasssadar.github.com/multirom/
Recoveries
AmonRa - based on 3.06: http://www.mediafire.com/?ld9g81igvze7na0 (9th March 2012 21:57)
AmonRa - based on 2.2.1: http://www.multiupload.com/7Y5HHNEPOT (20th October 2011 22:29)
CWM: http://www.mediafire.com/?6rfw0qbrddzq5d8 (9th March 2012 21:57)
TWRP: http://www.mediafire.com/download.php?o8kphxmfk9l01tl (21st October 2012 23:49)
MultiROM Manager app
http://forum.xda-developers.com/showthread.php?p=20610052#post20610052
(Always use newest version)
v24 - http://www.mediafire.com/download.php?1xy52tamzepibrx (TWRP support)
v21 - http://www.mediafire.com/?u9c3bmfbtf57dtm (Add charger settings)
v18 - http://www.mediafire.com/?g1lpsp66jc1cb1b (Add boot location settings)
v17 - http://www.mediafire.com/?l1li51sseaisz5j (Add brightness setting)
v15 - http://www.multiupload.com/B65WPFMFXP (Show & reset tetris high score)
v14 - http://www.multiupload.com/FWB5UBSMO1 (Updater now also check for app update, some minor fixes)
v13 - http://www.multiupload.com/NYYBX9CAFD (Update translations, add support for optimus V - http://forum.xda-developers.com/showthread.php?p=20657898#post20657898)
v11 - http://www.multiupload.com/1L3294ZAU7 (Fix mount issues on some roms, add menu to main screen, add link to xda)
v10 - http://www.multiupload.com/B3AVSFKDOW (Create /sd-ext/multirom folder on install)
v9 - http://www.multiupload.com/WW7TUNP7RY (read http://forum.xda-developers.com/showthread.php?p=20624306#post20624306)
v8 - http://www.multiupload.com/6OD7RQ74OE
v7 - http://www.multiupload.com/DJKMUGIVJ0

Something like this have the Xperia series. Maybe u find something u can use there.
Sent from my LG-P500 using XDA App

so this means we can test roms without replace current ??

Yes. Is my english so bad or you just don't read what I wrote?

Tasssadar said:
Yes. Is my english so bad or you just don't read what I wrote?
Click to expand...
Click to collapse
For the last time,you're speaking english perfectly p)

how to install your zip of amonra recovery i try but the recovery says that the zip dont have updatescript so it gives error....
i dont understand how to do this but ii´m searching this for a long time,if you can make a more frindley all user guide it will be very cool thankyou and hope you could doot....

*sigh* once again, this is [dev] thread, this is not something you can flash, at least not yet. You would know that, if you'd read whole post.

eduardogouveia said:
how to install your zip of amonra recovery i try but the recovery says that the zip dont have updatescript so it gives error....
i dont understand how to do this but ii´m searching this for a long time,if you can make a more frindley all user guide it will be very cool thankyou and hope you could doot....
Click to expand...
Click to collapse
[dev] means this is not something ordinary. Don't know what it is, don't mess with it.
Tasssadar said:
*sigh* once again, this is [dev] thread, this is not something you can flash, at least not yet. You would know that, if you'd read whole post.
Click to expand...
Click to collapse
Don't worry, you'll get more "hao cán i flush this into ma phones?" questions, good luck.

sounds like fun
thanks for bringing it for optimus one
but i have one question for you
I think in future kernel changing will also possible
because if we can flash kernel then we can make it to change
right?

Tasssadar said:
Yes. Is my english so bad or you just don't read what I wrote?
Click to expand...
Click to collapse
Maybe you just helped us with boot manager app
Sent from my LG-P500 using xda premium

I read the post but since the download you have is of a amonra recovery modified by you,i thougt that was a regular zip and only then make by abd the tutorial,thats why hi also ask a more friendly use because i now its not for averager use no need to get obset however im still happy hi was searching for that so hi dont mind waiting you make it more simple... sorry if that ofend you or franco lol we have to learn and its very hard now how to develop without having the proper nowledge like you all devs have and hi respect every dev even of he just make a simple app,by the way just dont send me to school lol where could i learn the bases to umderstand how to program java and then develop im asking this because all books hi find rekire previous nowleged of some progaming could some dev. Pointing me somewhere where i could learn and please dont be rude im just asking because i just dont love i want and hi will learn...
And baking to the thread what you find for me is one of the best and most important for our phones thanks a lot now just wainting a day everybody could use your work thank you
Sent from my LG-P500 using XDA Premium App

So your main question is: "Is it worth it?"
I would say, "Hell yeah it is!" but then again I do not have the know-how to pull something like this off.
If you decide to go ahead with it, I wish you the best of luck =P

I just modified Koush's AnyKernel so that it can modify ramdisk's content, so it is possible to install it with .zip file via recovery. I will add some modified version of CWM & AmonRA, create some walkthrough video and write some guide soon(c).
By the way, that kernel which is in devoid #froyo-final cant mount ext4 partition in init, dunno why, I'll look into it after raid.
EDIT: wtf, it just works now, and I did nothing Oo
EDIT2: Changes commited, now It can installed/controlled only by flashable ZIPs and recovery(well, only my modified AmonRa recovery for now). I'll do the rest soon, but I dont know when - maybe tomorrow (oh my, it is today actually already), maybe next month.

Flashable zips and guide added, see first and second post.

keep going I wanted something like this waiting when it can boot stock<froyo> and cm7....
thanx

gingerbread test
well i try with V20C,2.3.4 port(both with a2sd)and didnt woork after flash multiromv1.zip,when reobooting always return to recovery,so in recovery i go to multirom options and says no multirom folder so i start to think a2sd imcompatibelity,so i grab 2.3.3 V20G without changes oficial as lg give us but the results where the same no a2sd problem....
well later i will flash oldbaseband and try one of your combinations but i think its not compatible with gingerbread.....

I think I found it - on GB, there is "on fs" trigger in init.rc, which has only mounts in there, but I need to comment them out - all of them, so "on fs" trigger is empty, and init parser cant handle that. Will update soon.

Ok i will remain in new baseband to try when you update your exclente work...
Sent from my LG-P500 using XDA Premium App

v2 released, I have tested it with CM7 6.5.8, problem with stock GB should be the same as with CM7.

[TWRP] Recovery on the LG Viper

TeamWin Recovery Project
v2.3.2.3
Description:
As stated on the team win site
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Click to expand...
Click to collapse
Key Features:
Graphical touchscreen interface with buttons and drag-to-scroll!
Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times)
Compressed backups that can save you up to 50% disk space
Ability to choose which partitions to back up and which to restore
Custom names for backups, rename and delete backups inside recovery
Integrated Terminal Emulator
Install queues allow you to install multiple zips in one go (e.g. CM9 zip together with gapps zip)
Easy one-button cache & dalvik cache clearing after an installation
Recovery settings are saved to the sdcard and persist through reboots
File Manager that allows you to move, copy, delete and rename files and change their permissions
Battery percentage indicator, charging indicator and clock (set your timezone in settings!)
Reboot into download mode (bootloader)
Decryption of /data
Easy selection of internal/external storage
ADB support
Sideloading for automated ROM install: No outside links.
Detailed logfile
XML-based GUI that allows full customization of the layout – true theming!
See changelog below for 2.3 features
What's new in 2.3:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
What works:
Backup & restore
Mount & Unmount partitions
Mount USM
What does not work:
Any sort of power functionality(reboot recovery, reboot system..)
Install:
Automatic
Download twrp-lge-ls840.zip
Extract and run install-linux.sh | install-windows.bat
Reboot into recovery by either using
Code:
adb reboot recovery
Or pressing the vol- and power keys simultaneously then letting go when you see an instructions screen then pressing power twice
Manual
from console(linux/windows)
Code:
adb push recovery.img /data/local/tmp/recovery.img
adb shell "su -c 'dd if=/data/local/tmp/recovery.img of=/dev/block/mmcblk0p13'"
adb reboot recovery
Note: By downloading and installing the recovery package you take sole responsibility for any damages caused to your device.
Addendum: ICS compatibility is yet to have been worked out so as of now this is GB only.
Download: Attached because outside links not allowed.
Decided to release public build as it seems backup & restore work well enough. Have fun with it and tell me what you think.
Source:
Here's the github for anyone interested or wanting to help out
Can't post links my name is L0rdWaffles on github.​

JoshCo1n said:
TeamWin Recovery Project
v2.3.2.3
Description:
As stated on the team win site​
Key Features:
Graphical touchscreen interface with buttons and drag-to-scroll!
Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times)
Compressed backups that can save you up to 50% disk space
Ability to choose which partitions to back up and which to restore
Custom names for backups, rename and delete backups inside recovery
Integrated Terminal Emulator
Install queues allow you to install multiple zips in one go (e.g. CM9 zip together with gapps zip)
Easy one-button cache & dalvik cache clearing after an installation
Recovery settings are saved to the sdcard and persist through reboots
File Manager that allows you to move, copy, delete and rename files and change their permissions
Battery percentage indicator, charging indicator and clock (set your timezone in settings!)
Reboot into download mode (bootloader)
Decryption of /data
Easy selection of internal/external storage
ADB support
Sideloading for automated ROM install: No outside links.
Detailed logfile
XML-based GUI that allows full customization of the layout – true theming!
See changelog below for 2.3 features
What's new in 2.3:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
What works:
Backup & restore
Mount & Unmount partitions
Mount USM
What does not work:
Any sort of power functionality(reboot recovery, reboot system..)
Install:
Automatic
Download twrp-lge-ls840.zip
Extract and run install-linux.sh | install-windows.bat
Reboot into recovery by either using
Code:
adb reboot recovery
Or pressing the vol- and power keys simultaneously then letting go when you see an instructions screen then pressing power twice
Manual
from console(linux/windows)
Code:
adb push recovery.img /data/local/tmp/recovery.img
adb shell "su -c 'dd if=/data/local/tmp/recovery.img of=/dev/block/mmcblk0p13'"
adb reboot recovery
Note: By downloading and installing the recovery package you take sole responsibility for any damages caused to your device.
Addendum: ICS compatibility is yet to have been worked out so as of now this is GB only.
Download: Attached because outside links not allowed.
Decided to release public build as it seems backup & restore work well enough. Have fun with it and tell me what you think.
Source:
Here's the github for anyone interested or wanting to help out
Can't post links my name is L0rdWaffles on github.​
Click to expand...
Click to collapse
Thank you! Just to let you know, I do not have the Viper ls840, I have the Lucid vs840, and besides system and sdcard mounting, it works fine.