Related
hi all
first big thanks to all developers for your work.
WARNING WIPE NEEDED BEFORE INSTALLING THIS ROM
if you have v4.1 :
wipe data/factory....
wipe cache/dalvik......
wipe ext partition
wipe battery......
wipe autorotate......
ext2 to ext3
usb toggle put the rom
create new folder and name it android.tether,put the fw_bcm4329.bin on this folder
flash the rom and done.
FIRST boot is long but it is normal.wait.....
ROM BASED ON MCR3.1
KERNEL 2.6.29 UV OC R-14
ROM INCLUDED/
FULL UI SYSTEM COLOR CHANGED
ADDED WIFI_N
FLASHLIGHTALERTS
BLUE LED NOTIFICATIONS
INVERTED FACEBOOK
ALL LANGUAGES ROM VIA MORELOCALE2
NEW HTC DIALER
NEW ANDROID DIALER
SENSE MODDED
NEW WIDGETS
DIVXPLAYER-ROCK (not tested!!)
MUSIC PLAYER MODDED
NEW RINGTONES ADDED
NEW NOTIFICATIONS ADDED
AND WHAT ELSE ..?........
REMOVED
ADW.LAUNCHER
LAUNCHER PRO( if you want added,just install apk's )
FW-BCM4923.bin /
http://www.mediafire.com/download.php?grzidmznmnm
LINK ROM / http://www.mediafire.com/?lk3yanzmjiw
MD5 04C9AF30B9926265DDB37C72549B728F
IF YOU LIKE MY WORK!!!.....
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=52WDKEVC5DN2E
Very Nice Amer, I will flash this rom as soon as i get some time
thank you. but where to place the folder "android.tether"? sdcard?
Facebook app. has elongated logo at top and will crash phone everytime i try to enter login details
ownhere said:
thank you. but where to place the folder "android.tether"? sdcard?
Click to expand...
Click to collapse
Yes mate, just place the folder android.tether at the root of your SDCard and place the provided img file in that folder.
good. thank you.
thanks Amer! another great work from you. have been using your V4 for a while and will try this one later=)
Blue version is coming too I hope?
And do I really have to wipe everything?
How do I even wipe the ext partition with recovery?
V5 already.
So what are the biggest advantages of this rom above the V4???
The new HTC dialer? What's new about it? Or is it just the same dialer as the one added in the V4 rom (the one posted in the pictures you added?)
Amer_Bravox_V5_red_Tech
Eggcake said:
Blue version is coming too I hope?
And do I really have to wipe everything?
How do I even wipe the ext partition with recovery?
Click to expand...
Click to collapse
hi
if you have a V3,V4,V4.1 wipe all and wipe ext partition only
don't wipe your sdcard.
cheers.
Amer_Bravox_V5_red_Tech
hi all users
if you have probleme with divx player rock,don't worry
just push the apk above ,with adb
adb push "........apk" /system/app
work very good.
link
Already fixed after 10 minutes..
Hi Amer, thanks for the rom
ameruxxh17 said:
hi
if you have a V3,V4,V4.1 wipe all and wipe ext partition only
don't wipe your sdcard.
cheers.
Click to expand...
Click to collapse
HI there mate
I am always confused when people say wipe all
can u just bullet point all the wipes we need to do if we have v3,v4 or v4.1?
(so many different wipe options i always get confused)
hi amer, but what's a difference with your version 4.1? only the color and any programm?
I'am very satisfied of your 4.1.... why not update it?..... or works on froyo rom?
thank you so much already
i have trouble with selecting ring tones all ringtones play the same sound some kind of rapid beeping .
also with following the instructions on the wipe , it puts you into a rebooting cycle ,if you wipe dalvik and sd ext it happens to me on every time i wipe them i have to repartion sd card to fix it.
im gona reinstall to see if it fix's it .
edit ; reinstalled all is good nice work as usual ameruxxh17 love your roms.
With 4.1 and probably also with this one, battery time is really great. It's faster and lasts significantly longer than with the stock ROM.
Really great work. For me, combined with LauncherPRO, it's by far the best ROM available. If you want a stable and reliable ROM and don't want to flash every other day because of a new bug (like in many 2. 2 ROMs, no offense to the other devs and experimental-friendly people!) , this is the way to go!
I really hope you keep up your work and also release a 2.2 ROM once the official, hopefully stable version is released.
Sent from my HTC Desire using XDA App
hi amer, if i want to update beautiful widget, don't work
Great work Amer!
I also have some issues with beautiful widgets in V5. Beautiful home and smaller home mess up the template.
Cheers
Great rom, Thanks.
There is a small problem, there will be a blue framework version? I like the blue one.
ownhere said:
Great rom, Thanks.
There is a small problem, there will be a blue framework version? I like the blue one.
Click to expand...
Click to collapse
The blue version will cost more batter than the red version.
unCoRrUpTeD DATA2EXT
&
A2SD BLASTER
DATA2EXT
What is data2ext?
data2ext was started as a way to move the entire contents of the data partition to an ext partition on the sdcard. It gives you a way to increase the size of your data partition and also increase benchmark scores. This should work on most phones as it detects the block location of the sdcard, regardless if it is /dev/block/mmcblk0 or /dev/block/mmcblk1.
SETUP
The following commands are optional and need to be put in before the 1st or 2nd boot
Make sure that the data partition is mounted before issueing the commands
Code:
adb shell
mount /data
*Converting to ext3 or ext4 on first boot
Code:
echo "extA" > /data/.d2ext
A is either 2, 3 or 4, depending on what ext format you want.
In the future you can convert to ext3 or ext4 even after data is on the sdcard.
*Formatting the ext partition on first boot to ensure a clean and fresh filesystem
(Note: This does not need to be done)
Code:
echo "extA format" > /data/.d2ext
A is either 2, 3 or 4, depending on what ext format you want.
*Create a custom read_ahead speed for the sdcard.
(Info on what it does can be found here courtesy of brainmaster)
Code:
echo XXXX > /data/.sdrw
XXXX is any value you want. By default it will be set at 2048.
You will need your sdcard partitioned with at least 1 ext partition. Either you can do that through your recovery or go here to download a script that will repartition without loosing your fat32 contents.
WARNING:
Due to some changes made, you will need to either backup your apps and do a fresh install or install over my data2extV1 script. Do not try and use the a2sd-copy-and-blast method at this time.
Install on a ROM you are currently running that has a2sd or data2ext enabled:
1. Reboot into recovery
2. Flash a2sd-copy-and-blast.zip
3. Flash data2ext.zip
4. Once your phone has booted, reboot again (This is to limit the time of the first boot and the setup won't be complete until you reboot.)
Install on a ROM you are currently running that has my previous data2ext installed:
1. Reboot into recovery
2. Flash data2ext.zip
3. Reboot your phone.
Install on a ROM you are currently running that does not have a2sd or data2ext enabled:
1. Reboot into recovery
2. Flash data2ext.zip
3. Once your phone has booted, reboot again (This is to limit the time of the first boot and the setup won't be complete until you reboot.)
Install on a fresh intall of a rom:
(It doesn't matter if it has a2sd or not as this will remove all a2sd scripts if they are present)
1. Reboot into recovery
2, Wipe everything
3. Flash ROM
4. Flash data2ext.zip
5. Reboot
6. Once your phone has booted, reboot again (This is to limit the time of the first boot and the setup won't be complete until you reboot.)
[/SIZE]
A2SD-BLASTER
unCoRrUpTeD-a2sd-blaster.zip: Use this one to remove a2sd from the ROM if you are doing a fresh install or want to keep all data on your ext partition for data2ext
unCoRrUpTeD-a2sd-copy-and-blast.zip: Use this one if the ROM your are currently running is using a2sd. It will remove a2sd from it and copy all apps from the ext partition back onto your phone's /data partition.
Changelog
data2ext-V2.2:Fixed issue with V2.1 freezing on boot, due to deleting /system/bin
data2ext-V2.1:Added a check for those already using data2ext
data2ext-V2:included checks if the ROM has the needed files, included the option to change the format to ext3 or ext4 on first boot, added sdcard read ahead tweak. Reboot needed after any install, added custom_backup_list.txt for new installs or updates
a2sd-copy-and-blast_V2:changed to move data back to phone along with apps
data2ext-V1: 1st release
a2sd-blaster: 1st release
a2sd-copy-and-blast: 1st release
i'm going to test on a fresh install of liquidsense and hopefully this works b/c i just switched back to gingerbread to get the speed of data2ext and i just installed all my apps again so hopefully you found the fix....i'll post back with results
sigh....bootloops.........i'm going back to gingerbread....
someday i wish someone could get app2sd removed so that i could have data2ext working on sense 2.1
kifno said:
sigh....bootloops.........i'm going back to gingerbread....
someday i wish someone could get app2sd removed so that i could have data2ext working on sense 2.1
Click to expand...
Click to collapse
I just downloaded and flashed liquidsense and then a2sd_removal.zip. Booted right up.
It does remove busybox.a2sd, but in all testing across several different phones that has not caused any problems as the regular busybox is still in the ROM. The copy_remove.zip was missing some code to mount data before copying over, but I changed that one as well.
unCoRrUpTeD said:
unCoRrUpTeD A2SD BLASTER
&
DATA2EXT
SETUP:
You will need your sdcard partitioned with at least 1 ext partition. Either you can do that through your recovery or go here to download a script that will repartition without loosing your fat32 contents.
If you are currently running a rom with a2sd of data2ext enabled you will need to reboot into recovery and flash a2sd-copy-and-blast.zip and then data2ext.zip
If you are doing a fresh install or running a rom with a2sd disabled or nonexistent then flash data2ext.zip
If setting this up after a fresh install you will need to reboot the phone after it has booted up. This is only done to speed up the first boot startup time. Once it is running you can do whatever you want, and on the next reboot it will set everything up.
A2SD-BLASTER
unCoRrUpTeD-a2sd-blaster.zip: Use this one to remove a2sd from the ROM if you are doing a fresh install or want to keep all data on your ext partition for data2ext
unCoRrUpTeD-a2sd-copy-and-blast.zip: Use this one if the ROM your are currently running is using a2sd. It will remove a2sd from it and copy all apps from the ext partition back onto your phone's /data partition.
Click to expand...
Click to collapse
OKay so is this the correct instructions:
- wipe everything
- partition sd card to have 512mb ext2 (that's what i always use for ext)
- flash fresh install of rom
- flash data2ext.zip
- then reboot into system?
or do i
- wipe everything
- partition sd card to have 512mb ext2 (that's what i always use for ext)
- flash fresh install of rom
- reboot into rom
- reboot recovery
- then flash data2ext.zip?
thanks for all they help you've given me
kifno said:
OKay so is this the correct instructions:
- wipe everything
- partition sd card to have 512mb ext2 (that's what i always use for ext)
- flash fresh install of rom
- flash data2ext.zip
- then reboot into system?
or do i
- wipe everything
- partition sd card to have 512mb ext2 (that's what i always use for ext)
- flash fresh install of rom
- reboot into rom
- reboot recovery
- then flash data2ext.zip?
thanks for all they help you've given me
Click to expand...
Click to collapse
Updated OP.
Should be pretty clear now.
before i dive into this, bro, some questions if you will:
this moves everything in /data to sd-ext right? by everything, does this include even dalvik cache?
if, for any reason, i decide or need to return everything back to internal storage i could simply flash a2sd-copy-and-blast right?
thanks in advance!
EDIT 1:
bootloop! htc legend on cm6.1 w/ darktremor a2sd; ext3 partition. restored everything to internal storage, flashed a2sd-blaster then data2ext-V1. after restart, bootloop ..will try on ext2 partition later
EDIT 2:
bootloop also on ext2..was really hoping this mod will work on my phone
maxq1 said:
before i dive into this, bro, some questions if you will:
this moves everything in /data to sd-ext right? by everything, does this include even dalvik cache?
if, for any reason, i decide or need to return everything back to internal storage i could simply flash a2sd-copy-and-blast right?
thanks in advance!
EDIT 1:
bootloop! htc legend on cm6.1 w/ darktremor a2sd; ext3 partition. restored everything to internal storage, flashed a2sd-blaster then data2ext-V1. after restart, bootloop ..will try on ext2 partition later
EDIT 2:
bootloop also on ext2..was really hoping this mod will work on my phone
Click to expand...
Click to collapse
I'll look into it as this is also part of my dual-boot script that I am working on, which means that if this doesn't work on certain phones then the dual boot scripts won't work on all phones.
^ cool, man! i'm waiting on that as well. thanks!
this didn't give me bootloops so you've completed that step
but this didn't work at all
here's what i did:
- partition sd card
- wipe everything
- fresh install NFX stock 2.31.651.7 oxed (without apps2sd)
- install data2ext.zip
- reboot into rom
- once i approached the initial lock screen, i did adb shell reboot
- then i signed into google
- let it sync and load
- then i check application storage and it said 136mb
- so then installed titanium backup from makret
- after install i checked internal storage
- it went down to 131mb!
summary: not only did internal storage not say like 4xxmb like it does when gingerbread uses data2ext w/ 512mb, internal storage didn't even say anything different than the stock amount of internal storage
also even if the interal storage didn't correctly say how much storage we had after installing 1 app i knew this zip didn't take affect b/c of the great lost in internal storage
again i testing on nfx stock 2.31.651.7 (without apps2sd and oxed) and this did not work
edit: after fresh install method i tried the method where the rom doesn't have apps2sd.....this still doesn't work
this would be awesome if i got this to work on my rom but it doesn't even work on my rom's base.... and you haven't fixed yet....but i'll be checking up on this for fixes whenever you release a fix
I might be able to get to it tomorrow. If not it will be Wednesday. Been hard at work on my dualboot script, which uses a very complicated method of determining how to set it up. I only need to make a couple changes to this and symlink everything differently. I'm going to download nfx's Rom without a2sd as I had been testing on his a2sd stock Rom.
Sent from my dual-booted liquidsense 2.1
unCoRrUpTeD said:
I might be able to get to it tomorrow. If not it will be Wednesday. Been hard at work on my dualboot script, which uses a very complicated method of determining how to set it up. I only need to make a couple changes to this and symlink everything differently. I'm going to download nfx's Rom without a2sd as I had been testing on his a2sd stock Rom.
Sent from my dual-booted liquidsense 2.1
Click to expand...
Click to collapse
After talking with TGF about getting this to work with sense roms he said we need the correct e2fsck for sense 2.1 roms and also the libext2fs.so file for sense. Then we need to make sure busybox is intergrated into the ron by default. He couldn't help me get those files so the rest was left up to me but he did correct the script for sense roms though. Thought. I'd share that with you so that you could try and get this working for sense roms on the hero CDMA after you complete your dual boot mod.
unCoRrUpTeD said:
Install on a ROM you are currently running that has a2sd or data2ext enabled:
1. Reboot into recovery
2. Flash a2sd-copy-and-blast.zip
3. Flash data2ext.zip
4. Reboot your phone
Install on a ROM you are currently running that does not have a2sd or data2ext enabled:
1. Reboot into recovery
2. Flash data2ext.zip
3. Reboot your phone
Install on a fresh intall of a rom:
(It doesn't matter if it has a2sd or not as this will remove all a2sd scripts if they are present)
1. Reboot into recovery
2, Wipe everything...
A2SD-BLASTER[/B]
unCoRrUpTeD-a2sd-blaster.zip: Use this one to remove a2sd from the ROM if you are doing a fresh install or want to keep...
unCoRrUpTeD-a2sd-copy-and-blast.zip: Use this one if the ROM your are currently running is using a2sd...
Click to expand...
Click to collapse
Sorry to sound noobish here, but I'm running AOSP 2.2.1 on my heroc. i have moved all my apps to internal using titanium backup (in preparation for this). i have formatted by sdcard using cwm 3.0.0.5, with a 512 MB partition and 0 (zero) swap. Now I want to flash your cool data2ext! Which one do I use?
Important note! I have already tried flashing GrammarFreak's data2ext (ext2 version), and for some reason it didn't take.
And just now when I go into terminal emulator,
Code:
su
and then
Code:
data2ext -- enable
I get the following: "data2ext already enabled but not active."
Does this mess things up terribly? Can I still flash your stuff?
Yours,
Jim
[email protected] said:
Sorry to sound noobish here, but I'm running AOSP 2.2.1 on my heroc. i have moved all my apps to internal using titanium backup (in preparation for this). i have formatted by sdcard using cwm 3.0.0.5, with a 512 MB partition and 0 (zero) swap. Now I want to flash your cool data2ext! Which one do I use?
Important note! I have already tried flashing GrammarFreak's data2ext (ext2 version), and for some reason it didn't take.
And just now when I go into terminal emulator,
Code:
su
and then
Code:
data2ext -- enable
I get the following: "data2ext already enabled but not active."
Does this mess things up terribly? Can I still flash your stuff?
Yours,
Jim
Click to expand...
Click to collapse
I haven't changed what is here. It might work, might not. I tested on a couple of roms and it worked, but didn't work on others. Nandroid first. Flash a2sd-blaster.zip which removes any instance of a2sd and data2ext. Flash data2ext.zip.
Like I said I haven't changed it yet. Been working on my dualboot script. So it might work and might not.
unCoRrUpTeD said:
I haven't changed what is here. It might work, might not. I tested on a couple of roms and it worked, but didn't work on others. Nandroid first. Flash a2sd-blaster.zip which removes any instance of a2sd and data2ext. Flash data2ext.zip.
Like I said I haven't changed it yet. Been working on my dualboot script. So it might work and might not.
Click to expand...
Click to collapse
That's completely cool. Thanks for taking the time to reply!
Yrs,
Jim
...perfect...
very good apps.... i ' m very happy....
now i have used data2ext on new installation of rom and work perfectly on ideos with 1gb ext4....
it's a beautiful utility for adding space to internal memory...
excellent...
later i try with an already installed rom with a2sd....
thank you very much!!!!
update: i have a problem, apparently all work perfectly but when i active wifi the cell reboot :-(
grifovunque said:
update: i have a problem, apparently all work perfectly but when i active wifi the cell reboot :-(
Click to expand...
Click to collapse
same problem with wifi..
on my ideos script runs very very well but when i enabled wifi my phone reboot..sigh
i hope that's you can fix it..
however thanks,great script!
Works semi-great on a heavily modded Sprint stock rom. Overall, it took a few reboots, but is working. I have 409mb available. The only issue I found is that AlarmDroid does not work. I tried moving it to system/app and still not loading...i may try moving it in the actual rom, reflash everything and see what happens. The offending apk is not your fault by any means, just listing what I came across. I flashed the zip after I used your sd partitioner. On first reboot after flash, phone was normal...read that you said it takes another reboot, so I performed another reboot. On 2nd reboot, the whole system FC (just about every app came up and FC), performed another reboot. On 3rd reboot, AlarmDroid complained - but everything seemed fine...did a few more reboots, but it looks like the 3rd is the magic number for my rom...I may include this in my personal rom (obviously removing duplicate files like bb
I have one request and that is to make it more like the other scripts and allow it to be enabled, or not enabled. I am not saying have an on/off switch as the scripting for that would be extremely complicated, but have an off until enabled on switch for those looking to throw this in a rom. It is possible to put this in a rom, but some may not want it enabled right off the bat (like me)...Could it be possible to have an enabler script that upon running would move files where they needed to go? Like for instance have the tmp folder, add a file called enabled2e (or something) that runs mountpoints.sh and moves /tmp/50data2ext to system/etc/init.d...I dunno, just spitballing
evilvoice said:
Works semi-great on a heavily modded Sprint stock rom. Overall, it took a few reboots, but is working. I have 409mb available. The only issue I found is that AlarmDroid does not work. I tried moving it to system/app and still not loading...i may try moving it in the actual rom, reflash everything and see what happens. The offending apk is not your fault by any means, just listing what I came across. I flashed the zip after I used your sd partitioner. On first reboot after flash, phone was normal...read that you said it takes another reboot, so I performed another reboot. On 2nd reboot, the whole system FC (just about every app came up and FC), performed another reboot. On 3rd reboot, AlarmDroid complained - but everything seemed fine...did a few more reboots, but it looks like the 3rd is the magic number for my rom...I may include this in my personal rom (obviously removing duplicate files like bb
I have one request and that is to make it more like the other scripts and allow it to be enabled, or not enabled. I am not saying have an on/off switch as the scripting for that would be extremely complicated, but have an off until enabled on switch for those looking to throw this in a rom. It is possible to put this in a rom, but some may not want it enabled right off the bat (like me)...Could it be possible to have an enabler script that upon running would move files where they needed to go? Like for instance have the tmp folder, add a file called enabled2e (or something) that runs mountpoints.sh and moves /tmp/50data2ext to system/etc/init.d...I dunno, just spitballing
Click to expand...
Click to collapse
Creating a flag to enable or disable is pretty simple. Not sure if I put one in there. I'm not looking at it right now. All it needs is ...
Code:
if [ -f /data/.data2ext ];then
xxxx -------
xxxx /
xxxx | Existing commands
xxxx \
xxxx -------
else
# move everything back to /data
cp -a /xxx/xxxx/* /data
exit 0
I'm going to update this at one point with some checks and a different way to mount everything, which will reduce the overall script size and make it more compatible with more roms and phones. It's been a while since I looked at it , but I know that I include busybox in somethings as it has more functions than what is normally provided in the roms.
Hola peoples!!! Ok so I just thought I'd create my own thread on this matter. Mustangtim started one in apps and themes (and here is the link to that thread) but since I'm taking over this project it was brought to our attention that this should be in the dev section as its no longer just an app.. I am actually tearing .imgs apart trying to figure out what the deuce.
FIRST OFF THIS IS A WORK IN PROGRESS, WE ARE NOT YET FULLY SUPPORTED. HOWERVER I'M DOING MY BEST TO CHANGE THAT.
Secondly if you want to help get this started please visit the market and grab the app here. Its a $3 dollar app for unlimited amount of roms, based on your SD card storage capacity anyway. And speaking of which you need AT LEAST a class 4 or better SD card to make this run smoothly.
Also feel free to visit the forums at http://forum.init2winitapps.com/
Ok so here it is, Boot Manager Pro. Its been a long time coming for the g2x to dual boot. First off let me say long story short, I currently have a bootable SD Rom, known as ROM1. I have yet to be able to recreate my findings tho. But it works and it doesnt brick at all. However it is a bit laggy on my class 4 SD card. Luckily I've already done my research on this project as there are many threads of such awesome info so I'm just going to be lazy about it and quote the good people of xda versus re-writing it based off of their info.
ChrisDDD said:
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of its own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, & boot. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flash able backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
Click to expand...
Click to collapse
So basically upon installing the app you need to setup your phone so that way you can properly install a ROM, follow these steps:
1. Go into the supersu(or superuser app) and then go to settings then disable logging or click none.
2. Then go into the BMP app and press the menu button on your phone, not the app, and go to settings. Once in settings put a check mark in force large boot.img, screen on during install, and then go into variables, leave tegra alone but change the sdcard block to show mmcblk1p1. Then press finish and let the app restart. By the way I didnt change any of the sizes of the .imgs but feel free to do so. But be warned do not decrease the size of the system.img only increase it, if desired.
3.Then after you've done the above you need to setup the phone rom. Click on 'Setup Phone' under phone rom and follow that process to setup your phone rom.
4. Once your phone rom is setup you may begin to install a zip to rom1 or rom2 or whatever slot you want. This is the tricky part. I have done tons of reading and most people say that if your using CWM, which us g2x'ers do, then you will probably have a better chance of getting a bootable rom by restoring from a nandroid backup you did versus installing new.
5. So after you decide which path you will take, nandroid backup or fresh rom install, choose install. If you choose a fresh rom, wipe system, data, and cache right away. If nandroid, then wipe after the install.
6. Now once you have clicked install put your phone down, DONT MESS WITH YOUR PHONE AT ALL! PUT IT DOWN AND WALK AWAY OR SOMETHING! Don’t mess with it, text from it, xda from it, dont even use the screen as a mirror!!!! lol seriously the app is picky and while under the .img creation process you want nothing to mess that up or you will not get it booted. You may however drag down the notifications bar to follow the progress of the install.
7. Once its complete, tap the install complete notification in the notification bar and let the app do its thing to finalize the install and get you back to your rom selection screen. Now if you did a nandroid back up here is where you click 'manage slot' and then factory reset the backup you did. Just do it, dont ask why.
7.1 Also so if you desire to install gapps and/or possibly a different kernel, now would be the time to do so while your here. I have read mixed reviews of doing this process right after the rom installs. However when I set up my rom1, I booted into it first all happily then realized I had no gapps. So I had to reinstall BMP on rom1 then boot back to phone rom and then I installed GB gapps and had no issues booting back into rom1.
8. Once the above steps are done if your feelin lucky go ahead and tap on boot the rom you installed, and if all goes well it will boot up.
9. If it boots up you need to post confirmation here!!! Provided info such as phone rom and the info on the sd rom you used and slot number and such.
Hopefully it will just work for you. I have done all the above steps using HFP 2.1 as my phone rom and only been able to get 1 bootable rom. Being it was for testing I used HFP as my phone rom and as well as my rom1.
So if the above steps dont wortk out for you and your boot lopped or what ever, then turn your phone off and reboot into cwm. You have 2 options to resolve the boot issue you just created. 1, you may go to restore then advanced restore then restore your boot. Or 2. select install a zip and nav to the bootmanager folder then phone rom then flash the update zip there.. then reboot and you should be back at your phone rom.
Here is a basic run down of everything that I have done so far:
When I first started working on this project I wasn’t doing any dev'ing to change any of the stuff in the boot.img. I just changed settings in the app per all the research I did. So when all was said and done I restored HFP 2.1 to ROM1 and it actually booted!! And it works lovely btw.. I can still boot into this rom today. I then decided to pass the word and ways that I created the working rom1, well I nor anyone else I passed the info to was able to get it working. Only one other person was able to confirm that rom1 works but only after I copied all my rom1 info and sent it to him for testing.. and he was able to boot into my created rom1… As I see it, it was a blue moon event that I have yet to repeat. So I thought eff it lets do some dev'in so I unpacked the boot.img from rom1 then compared that to the unpacked boot.img from rom2 that I created in my trial and error experiences. So in doing so I noticed 4 differences; 1, the mount points obviously, 2, in the sbin folder had a ueventd file from the working rom1 was a text file viewable by gedit in ubuntu. In rom2 it was just a non-readable file. 3, in the init.rc file was also missing a chmod command for system, (the command is in rom1 but not rom2) and 4, there was a ueventd.tegra file that was in rom1 that wasn’t in rom2, but everything else is the same. So I decided to plug and play with the differences to see if she boots and no go. I don’t understand why its boot looping because I am using the same rom as phone rom as for rom1 and rom2. So it boot looped. So I had to restore my boot.img many times in cwm.
So then I said eff it lets do some more research, then I noticed in the .zips folder plus the individual rom folder there are .zips that will let you flash via cwm if you get boot loops and 'should' get you booting to your desired sdrom. I then tried that way and no go.. so then I opened up the zip and had a look at the internals.. first there is the moveboot.sh file that the app runs in cwm flash the given boot.img. I then checked out the meta-inf and opened up the updater-script thinking that the app wasn’t actually flashing the boot.img which is why it loops... Well I think im half way right. However the script itself is lil dodgy... first thing I noticed was at the end of the script they have a command to cp the log from /tmp to /sdcard/bootmanager well the command was wrong so it never copied the log. So I fixed that. I also saw that the assert command was pointing to ‘boot’ instead of mmcblk0p5, so I changed that too. Then I decided to do away with the assert command and the moveboot.sh file they have going on to utilize the same functions that the kernel zips use, which is a kernel folder that holds the boot.img and a run_program that dd's the boot.img to 0p5. plus I even updated the update-binary that the file uses. I used the one from the g2x nullifier as I know that one was made for our phone and should have no issues.. plus there was a noticeable difference in the sizes of the provided binary to that replaced binary. So with the updated.zip file I then rebooted into cwm to flash that being that I was using a different command to flash the boot.img as well as the other changed stuff and still it boot looped. So as of now the only thing I don’t think ive done was grab the boot.img from rom1 then change the mount points, only change that, and then use that for rom2 and see if it boots. I don’t think I’ve done that yet. But every dam process I do I get boot loops. So basically I have came to the conclusion that it’s now NOT a boot.img issue being that I have done everything to change the boot.img and to make sure it flashes, which it does indeed and now creates the log too… I think maybe it has issues with the system.img as that’s what comes next in the boot process. But that’s just my hypothesis. I won’t be able to confirm this till I liberate rom1’s boot.img then change the mount points to point to rom2 and then see if it boots.. if it don’t work then that would mean to me that there is an issue with system.img created. But that’s just my hypothesis…
What I don’t understand is why the eff when I didnt hack the app I got a working sd-rom, but when I do change some stuff with it still don’t work!!???!! I guess maybe ill just edit/hack the apk to see what’s up.. This is getting way more complicated than it needs to be, since it worked prior to all my major changes to the script its using for flashing and the boot.img and what not. Anyone have any ideas feel free to add them.
My next steps are to edit rom1 boot.img one last time to change the mount points to point to rom2 and then if that’s a no go then it’s got to be the system.img that’s getting created. By the way this whole process I have only been restoring my nandroid backup for HFP 2.1. I have not attempted to flash new as with thru my research more times than not people would get a bootable rom via restoring versus flashing new.. so if anyone wishes to experience an sd rom let me know, ill send you a link to download my rom1 to get it going. Mind you that its not perfect and you need a class 4 or better sdcard. Everything works but it just takes a bit longer to load things and get things cached as its on the sdcard and not nand. Also if you have any input or are wishing to help pm me I need more heads to get this sorted as I can’t be the only one who knows how to edit scripts and unpack imgs and such. Either way I will continue to do this until I get it right damit!!! Oh and I just ordered a class 10 sdcard to help with this process…
That was copied from the other thread that mustangtim started. Last night when I went home the first thing I did was change the mount points on rom1 to reflect rom2, I changed nada else, then I tried to boot it... it boot looped. So maybe its a permissions issue or the system.img.
So just as a proof of concept and before anyone calls bs on my work/findings Here is the link to my rom1 that boots and is HFP2.1. *Update, 'm just going to
leave it on my DB for now till I find something better I guess. xda wont let me attach the file since its 233MB. Oh well here is the link :
Code:
[URL="http://db.tt/eBZwrOrs"][U][B]Here it is, my Rom1 HFP 2.1[/B][/U][/URL].
I have also attached my updated script file to flash back to rom1, for now.
The boot.img points to rom1 instead of phone rom, ill add to phone rom
as well, just not the now. :) Feel free to flash this via cwm versus
restoring...
Also this is part of the this: the ‘.zips’ folder you need to replace the file in
that folder as well. It’s an update file for rom1 to flash the boot.img.
..
If you’re going to use this you need install a random rom to rom1 then replace those created files in rom1 with these files in the 7z file..
So I am doing this new thread to get the devs or people with know how to help me out with my findings. I have edited the boot.img so much I could pretty much re-write everything in there by now including using magic to create to my own kernel eff!! lol jk but seriously I need people with knowhow to provide confirmation of go or no go. Basically I have people whom have helped out but It seems that I'm the only one who has dug this far into this app(unless i've been misinformed) and I have no one on my level to talk with except the init2winit devs. Which are very helpful btw.
And lastly:
Conap said:
Guys if it's failing to make the boot.img first make sure your using the market version....others have released cracked versions of our app which they broke...if your using the actual market version just send me a pm or email [email protected] and send your log.txt from BootManager folder on sdcard and we'll get it straightened out. Thanks.
Click to expand...
Click to collapse
or post here or PM me, I'm always down to help out.
Also thanks go to the init2win team, Gflam and Conap as they started this app. and as well to Mustangtim as he brought me into the light of BMP.
So you got all that???!!!??? Now lets get this party started and get full support for dual booting. I will not rest until I get this working. Thanks for your time and possible assistance.
Ok so since I have a book above I thought this is a good place for links and such...
So just incase anyone is curious, here is the Official Boot Manager Manual
Here is a nice link for Tips and Tricks while Installing ROM's that so far has good info to help you watch via adb what the BMP is doing in its creation process.
Some FAQs:
When should I set up my phone ROM?
Set up your phone ROM EVERYTIME you install a new ROM to your phone so you can get back to your phone ROM and won't get stuck on your SD ROM.
My SD ROM seems to lag how can I fix this?
SD ROM lagging may be due to a few things which all have easy fixes. First fix is that most of you have class 2 cards which are what usually come with your phones. These have a much lower read/write then cards of a higher class, we recommend a class 6 card or above. Another easy solution is overclocking merely install a better kernel and use CPU Boost (or any other overclock app) to overclock your phone.
Can I nandroid my SD ROM slots?
Yes and no you can't nandroid them in the traditional sense of the word using recovery but this app works as a recovery for your SD ROM slots and you can back up your ROM slots within the app in the Manage Installed ROMs section which works as a nandroid for your slots by fully backing up your slots to your sdcard which can later be restored.
What if I want to change the sizes of my images, how may I determine the individual sizes easily?
Easiest way is to open up terminal emulator in your app drawer. Type 'su', then grant permissions if need be, then type 'df -h' and it will display such information. You may also use adb in the same fashion. Connect via usb, open up command prompt/terminal and get adb connected and then type 'df - h' again and the same info will show. I will say this again just because, do not decrease the size of your system.img ever! Unless you want mad issues!
Here is the changlog link and just for heck of it the info based on that link:
Code:
V3.2.6
Fixed DroidX/Droid2 Install issue
Fixed UI theme issues
Fixed issue with spaces in name of pic when selecting photo for screen shot
V3.2.5
Fix to allow continue of install if no boot.img is found.
V3.2.4
Added support for HTC Rezound
Added support for rom's with multiple boot.img's
Added support for rom's made for multiple phones
AutoDetect sdcard for usb mounting
Fix for installing ICS gapps
Optimized SDRom Install process
Added support for Motorola RAZR
Added install queue
V3.2.3
Fixed issues with rom's not showing when on emmc on Droid Incredible
Fixed issues with not showing correct booted rom in app
More improvements to sms sync(all rom's will need updated app for changes to apply)
Fix issues with loader
Fixed issue with switching to backup server when main server goes down
Fixed 1x1 widget to show unlimited rom slots
Added 2x2 widget that works with unlimited rom slots
V3.2.2
Fixed force close for img's over 1Gb when resizing
Fixed current booted rom displaying correctly on gnex
Fixed issue with wrong busybox downloading on gnex which should fix alot of install/boot issues
V3.2.1
Fix for errors causing installs to fail.
Fix for some of the licensing stuff.
Removed sdbooster prefs from Galaxy Nexus(Since they don't have sdcard).
V3.2
Changed 4 sd slots to infinite slots!
Galaxy Nexus Support
Sms and Call Log synced between ROMs (you choose what ones too also requries updating boot manager in all slots)
License Check extended to a week
ROMs do not need market installed for boot manager to run (requires updating boot manager in all slots)
Hide su toasts (superuser elite only)
Fix for force close when setting screen shot in MIUI rom's
Thunderbolt defaulted to force large boot.img
Fixed unsupported device using a key
Manually setting variables only accepts numbers
V3.1.1
Fix for various force closes in rom installs and Nand restores
V3.1
Added su binary check
User selectable colors for everything
Better navigation (press title for quick action)
Added compatability for new twrp backups
Better compatiblitlity with memory tweak scripts(i.e. supercharger script and liquids default scripts)
Fix for install process being killed by android
Fix for some themes erasing img's
Fix more force closes during install
Force smaller boot.img option in settings(Fix for some phone's who's boot.img won't fit on the phone after BootManager edit's it)
Improved gapps checker
Improved security
Boot Manager now accepts keys pay for by paypal (see http://init2winitapps.com/stories/BootManager.html)
Added Evo 3d GSM Support
Added notifcation sound/vibrate for finished install (turn on in settings)
Improved data check
V3.0.3
Fix some force closes
V3.0.2
Added backup server (Sorry our server dropped out)
Fixed some force closes
2nd init fixes for Liquid's ROMs
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes
V2.0
Install now runs from the foreground (status bar)
Restore Nandroids to slots also in the foreground
User can cancel installs as they run
4 new themes added including one by apophis9283
Some phones such as tb moved to new install code (Fix for some sense rom's)
V1.3
Added third theme to app (Red Theme)
Added 4x1 widget and new widget styling
Fixed in app messenger
Added support for Htc Evo 3D
Added support for Htc Sensation
Added Support for Htc Incredible 2
Added Support for Htc Incredible S
Added Support for Htc Desire S
Added support for LG Ally
V1.2
Added option to reboot to phone rom to install gapps in license check dialog
Better error checking and error logging
Automatically install's ext2 libs if not present
Moved Set Names to Manage rom's
Fix for add-on's not installing correctly
Better compatiblility for rom's that use data2ext or apps2sd(user must set larger img's in manual variables)
Trash cleaner added to extras
Better Fix for WiFi issues on Droid 1
Added display to show what rom you are booted into
Fix for updater-script not found errors
Added support for Htc NexusOne
Added support for Htc MyTouch4G
More compatiblity for ext4 support
V1.1
Fix WiFi issues on Droid 1
Fix bug in rom installer for setting permissions correctly
Fix bug for cache size not setting correctly in setting variables manually
Fix for decimals entered into partition sizes causing force close
Fix force close in widget
Fix force closes in installer
Added Wipe data/Factory reset to Manage Rom's section
Added code to show what file's are being unzipped in dialog
Added support for rom's that extract files to sdcard so the files actually end up on your sdcard
Added support for Htc Desire (apps2sd and data2sd rom's support is experimental. Please email if you test it and it works/doesn't work)
Added support for Htc Inspire4g
Added support for Htc DesireHD
Added option to use ext4 filesystem if rom's support it-Experimental Won't work with all rom's.
Added log.txt file to sdcard to log errors during install
V1.0
Initial Release
YEZZZ
glad to finally see this here!
jookdakang23 said:
glad to finally see this here!
Click to expand...
Click to collapse
indeed... hopefully it wont be before too long that I get this app fully supported for us!
This app will be extremely useful for G2X owners and makes the G2X more versatile and desirable.
da-pharoah said:
indeed... hopefully it wont be before too long that I get this app fully supported for us!
Click to expand...
Click to collapse
idk how you get it booted. lol i keep getting bootloops
jookdakang23 said:
idk how you get it booted. lol i keep getting bootloops
Click to expand...
Click to collapse
Are you using the files I supplied or the ones that BMP created for you?
Woo hoo good job bud
Sent from my LG-P999 using xda premium
x0xhellx0x said:
Woo hoo good job bud
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
LOL thanks bro.... Go Team Hellfire!!!!
da-pharoah said:
Are you using the files I supplied or the ones that BMP created for you?
Click to expand...
Click to collapse
i remember requesting the files but think you ever sent them
jookdakang23 said:
i remember requesting the files but think you ever sent them
Click to expand...
Click to collapse
no we had a miscommunication due to our avail times and GB's lacking ability to utilize two accounts on gtalk.... I have posted those files in the op however...
First, I want to thank everyone who has helped with us on this app. Second, I know I picked the right man for the job, did you see that OP! All kidding aside, a lot of you know I write for ACS under screen name artifintel. I just had too much on my plate to give this project the attention and direction it needs. The right guy is in charge, he's a stand up person and very knowledgeable with this app. Good luck everyone!
[email protected]
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Rafase282 said:
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Click to expand...
Click to collapse
what rom are using as phone rom? and you installed to rom1?
da-pharoah said:
what rom are using as phone rom? and you installed to rom1?
Click to expand...
Click to collapse
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Rafase282 said:
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Click to expand...
Click to collapse
and no bootloop you say?? well then it may be the stock rom your using... The app is very picky and if you get a bootloop, I feel that those can get booted with tweaks... but stuck on lg screen is just no bueno.. Try a different rom... maybe one that has its partitions at ext3 format just to try it.. I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
hands down, a badass app...
SiL3nTKiLL said:
hands down, a badass app...
Click to expand...
Click to collapse
lol +1 for sure!
da-pharoah said:
I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
Click to expand...
Click to collapse
positive on ext4
TWRP 2.3.2.0 with on-screen keyboard!
Team Win Recovery Project 2.3.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.
Note from me:
- idk who compiled v2.3.2, i couldn't find it, but it's there available.
- i'll keep monitoring this thread for saga, and if necessarily i'll compile new builds.
Phone look:
Tablet look:
CHANGELOG
Code:
[B]What's new in 2.3.2.0:
[/B]Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
Fixed a bug with deleting a backup with a space in the name
Added highlights on keyboard key presses
[B]What's new in 2.3.1.0:
[/B]Unmount system after boot to prevent some status 7 symlink failed errors on zip install
USB Mass Storage code improvements
Better handling of mounting storage during boot for some devices
Fixed a problem with sizes of images (boot & recovery) after resetting defaults
Fixed size errors during backup for some devices on recovery, etc.
Fixed a problem with restoring backups when multiple archives were present
[B]What's new in 2.3.0.0:[/B]
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)
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
- launch the app
- allow root
- press menu button and click install OpenRecovery
You can find more information and download links on our website!
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.
THEMES:
T-Ryder's MIUI v4 theme (v2): http://forum.xda-developers.com/showpost.php?p=29744031&postcount=43
Another Great One.. Looking Forward To Try It..
@ djpbx.. Keep It Up Buddy !
- EDIT -
Downloaded the Theme Reference ZIP.. Will make one when I am Free..
I like the layout ..
Here's A Guide On Making Themes : Click Me
Very nice! This is definitely one of the best alongside 4EXT. CWM has to step up their game!
Interesting, I'll try it now Great work djpbx
Great, more to choose from! A bit offtopic, but this Dumlock thing, I've read about this replacing hboot with recovery, so when you boot your phone after that as usual, it still boots in recovery as hboot is now actual recovery. And that it allows to flash another hboot then. Could this be used to s-off a 2.x phone that's now s-on? I know I can downgrade and use revolutionary for 0.98 but could this work for 2.00.0002?
[edit]
never mind, I'm an idiot. s-on is a hardware-thingie, even if 'just' flashing a hboot would work it would still be s-on. Might be possible to use this to easily move between 0.98 and 2.00 hboot's though.
[/edit]
tried it. It was ok, but feel the UI isnt my taste and feel. So ive went back to 4ext touch. Also not sure if its added already but didnt see any option to Full wipe everything except SD card which is usefull. Ill probbly come back to it once its improved a bit more, or The UI ever gets a nicer feel to it
but nice to know i dont only have the option of 4ext (Clockworkmod just isnt up to scratch in my opinion)
v2.2 is up and now with official support!
Enjoy!!!
dan-fish said:
Very nice! This is definitely one of the best alongside 4EXT. CWM has to step up their game!
Click to expand...
Click to collapse
CWM is Sh!t..just outdated and not interesting anymore,..
Im trying it right now
Edit: A lot better than CMW Touch. But the fix permission never work for me. Even 4EXT.
Sent from my HTC Desire S CoolDroid v6.0 via XDA Premium
How can i install files via goomanager?
I download the file and then nothing happens
Written in bad english with my HTC Desire S
Open GooManager, open menu, choose Install OpenRecoveryScript. Choose yes, and make sure on the next screen shows img name, with (saga) in it. Thats the right one for HTC Desire S.
Sent from my HTC Desire S CoolDroid v6.0 via XDA Premium
looks great~ good job guy ~
anazhd said:
Open GooManager, open menu, choose Install OpenRecoveryScript. Choose yes, and make sure on the next screen shows img name, with (saga) in it. Thats the right one for HTC Desire S.
Click to expand...
Click to collapse
Now it works, thanks...
When i want to install a new rom, what do i have to wipe?
noytexz said:
Now it works, thanks...
When i want to install a new rom, what do i have to wipe?
Click to expand...
Click to collapse
the same as before...
if you came from a different rom do a full wipe
or if you just update the same rom three (e.q.: IceColdSandwich 8.2 to 8.3)
only wipe cache and dalvik.
cheers,
bl4ckb1rd said:
the same as before...
if you came from a different rom do a full wipe
or if you just update the same rom three (e.q.: IceColdSandwich 8.2 to 8.3)
only wipe cache and dalvik.
cheers,
Click to expand...
Click to collapse
And full wipe is factory reset + System wipe + dalvik cache wipe?
Written in bad english with my HTC Desire S
noytexz said:
And full wipe is factory reset + System wipe + dalvik cache wipe?
Written in bad english with my HTC Desire S
Click to expand...
Click to collapse
or format boot, system, data, cache, dalvik
Thanks, but there is no format boot
Written in bad english with my HTC Desire S
noytexz said:
Thanks, but there is no format boot
Written in bad english with my HTC Desire S
Click to expand...
Click to collapse
man, if you use 4ext recovery use option to FORMAT ALL PARTITIONS except SD card (FAT). that's enough.
docertabum said:
man, if you use 4ext recovery use option to FORMAT ALL PARTITIONS except SD card (FAT). that's enough.
Click to expand...
Click to collapse
in TWRP there's no boot wipe. which comes out handy sometimes for HTC devices. new ROMs overwrite it though. lol i usually dont wipe boot and never have problems.
This is not 4EXT!
This should be the correct way of wiping in TWRP
noytexz said:
And full wipe is factory reset + System wipe + dalvik cache wipe?
Written in bad english with my HTC Desire S
Click to expand...
Click to collapse
Click to expand...
Click to collapse
noytexz said:
Thanks, but there is no format boot
Written in bad english with my HTC Desire S
Click to expand...
Click to collapse
I wipe system, then cache and then dalvik. No need factory reset as wipe system delete the old rom for good.
docertabum said:
man, if you use 4ext recovery use option to FORMAT ALL PARTITIONS except SD card (FAT). that's enough.
Click to expand...
Click to collapse
Dude, this is not 4ext thread.
Sent from my HTC Desire S CoolDroid v6.0 via XDA Premium
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.