While twrp 2.x has been out on a large number of devices, since our team never had a N1 it's been absent from our list. Now we are happy to serve up a version to the last Nexus device on our list.
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:
v2.2.1 - various bugfixes and HTC Dumlock support now built in for latest hboots that don't support flashing to /boot.
CHANGELOG (for 2.2.0):
- On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
- Name new backups and rename existing backups
- Rename files and folders in the file manager
- Pseudo-terminal emulator
- Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
- Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
- Simplified XML layout support between resolutions
- Added dual storage selection radio buttons to zip install, backup, and restore pages
- Improved zip install compatibility
- Updated update-binary source code
- Numerous small bug fixes and improvements
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app
For downloads and instructions please visit our TWRP website and choose your device in the dropdown menu
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.
Taking this one too for device specific faqs.....
I compiled this build with the Twrp source against the CM7 source tree.
Very Nice - !!!
sbaeder said:
Very Nice - !!!
Click to expand...
Click to collapse
Glad you like it. I know it's a little late to the party, but I figured better late than never.
I must say I was pretty sceptical this could be better than 4ext, but I am pleasantly surprised how much I like it. It is my new favorite recovery for now.....till I need to reformat my SD ext....4ext just does that better. To not have to wipe the fat partition is invaluable to me...but maybe that will be a possibility one day too. I really prefer every other aspect of this over 4ext though...very well done!
Sent from my Nexus One using xda premium
ctfrommn said:
I must say I was pretty sceptical this could be better than 4ext, but I am pleasantly surprised how much I like it. It is my new favorite recovery for now.....till I need to reformat my SD ext....4ext just does that better. To not have to wipe the fat partition is invaluable to me...but maybe that will be a possibility one day too. I really prefer every other aspect of this over 4ext though...very well done!
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
Thanks! It's been in dev for little over a year now on different devices. As for sd-ext, we'd be happy to merge a pull request with a better method, but given that most newer devices have large amounts of internal storage it's not likely we'll get to it anytime soon.
But twrp is 100% open source and we are more than happy to get people started compiling!
Sent from my HTC One S using xda premium
Im no developer and dont know what a pull request is, but the difference I am speaking of lies in 4EXT's ability to re-partition the SD card either completely (which this also does) or only the ext partition and leaves the FAT partition untouched (which this does not do). What that would entail is way beyond anything I could hope to know or figure out, but Im certain it can be done. Again, thanks for your hard work on this and for bringing it to us!
ctfrommn said:
Im no developer and dont know what a pull request is, but the difference I am speaking of lies in 4EXT's ability to re-partition the SD card either completely (which this also does) or only the ext partition and leaves the FAT partition untouched (which this does not do). What that would entail is way beyond anything I could hope to know or figure out, but Im certain it can be done. Again, thanks for your hard work on this and for bringing it to us!
Click to expand...
Click to collapse
Oh I see what you mean. Not to re partition ot, but just format/wipe just the ext.
Sent from my HTC One S using xda premium
What about hboot updates from this tread? working?
ViViDboarder said:
Oh I see what you mean. Not to re partition ot, but just format/wipe just the ext.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Sorry I was not clear, with 4EXT you can re-partition JUST the ext partition without completely wiping the whole card. So you can actually change partition size, type, etc....without reformatting the who SD card.
athost said:
What about hboot updates from this tread? working?
Click to expand...
Click to collapse
Haven't tried, but I don't see why it wouldn't work.
ctfrommn said:
Sorry I was not clear, with 4EXT you can re-partition JUST the ext partition without completely wiping the whole card. So you can actually change partition size, type, etc....without reformatting the who SD card.
Click to expand...
Click to collapse
That's interesting as most methods of repartitioning a disk cause the entire disk to be wiped. I know there are some ways around it though, but we haven't looked at them I don't think.
ViViDboarder said:
Haven't tried, but I don't see why it wouldn't work.
That's interesting as most methods of repartitioning a disk cause the entire disk to be wiped. I know there are some ways around it though, but we haven't looked at them I don't think.
Click to expand...
Click to collapse
4EXT is the only one Ive heard of....is very nice too.
So, basically, it is just adjusting the content of the partition table to make it smaller (or use any other "free" space after the FAT partition, and then to format the new partition.
Reminds me of all the old DOS based (i.e. ranish?) partition manager tools...basically a lot of low level manipulation of the data in the partition table.
I love TWRP!
Having an issue installing it on my N1, though - goomanager seems to stall at "Installing recovery image." So I need to do it manually I guess.
I'm assuming I should be able to fastboot flash recovery openrecovery-twrp-2.2.1.4-passion.img - right?
---------- Post added at 04:33 PM ---------- Previous post was at 04:28 PM ----------
JeremyNT said:
I love TWRP!
Having an issue installing it on my N1, though - goomanager seems to stall at "Installing recovery image." So I need to do it manually I guess.
I'm assuming I should be able to fastboot flash recovery openrecovery-twrp-2.2.1.4-passion.img - right?
Click to expand...
Click to collapse
And, to answer my own question, that's exactly what I needed to do.
JeremyNT said:
I love TWRP!
Having an issue installing it on my N1, though - goomanager seems to stall at "Installing recovery image." So I need to do it manually I guess.
I'm assuming I should be able to fastboot flash recovery openrecovery-twrp-2.2.1.4-passion.img - right?
---------- Post added at 04:33 PM ---------- Previous post was at 04:28 PM ----------
And, to answer my own question, that's exactly what I needed to do.
Click to expand...
Click to collapse
Glad you figured it out. The issue has been that goo.im had a mishap when updating their hardware. So a lot of data was lost. Our other download on teamw.in should point to a backup source at techerrata files.
I've been using 4ext for a long time but I recently discovered twrp (installed it on my Kindle and love it). One question before I put it on my N1: Are my nandroid backups from 4ext forward-compatible with twrp? E.g. Will twrp be able to restore old backups?
Thanks for all your work!
Related
Warning: whether you preform these steps correctly or incorrectly, you may be left with a device which cannot be recovered to a previous state. Because this process operates on the recovery partition it leaves you with little room to recover if flashed incorrectly, especially if your normal Android mode doesn't boot.
(although realistically you can just flash ESPRIMG.zip from HBOOT to recover, or fastboot)
So here it is ladies and gentlemen: Clockwork 3.0.0.5, based on a git version pulled/compiled on January 6th, 2011 from the CyanogenMod 7.x (CM7) repository. So what's new? Nothing that I can tell! Not sure why it deserves version 3.x, but I guess changing the text color and background is considered a 'major upgrade'.
This is provided in .img format - NOT an update.zip format. That means you'll have to flash it to your recovery partition using flash_image. Obviously that means you first need root AND S-OFF. No, I won't tell you how to root your phone or what S-OFF is.
Instructions:
Code:
$ su
# flash_image recovery recovery-cw3-test1.img
'flash_image' isn't included intentionally - if you're smart enough to know how to flash this properly and understand the risks, then you might be smart enough to know where to get 'flash_image'.
How'd I do it? Top Secret - I'd have to kill you if I told you.
Download link: [REMOVED - use one from CM7]http://dl.dropbox.com/u/14943973/recovery-cw3-test1.img
Need to revert back to 2.5.0.1? Flash this: http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.1-espresso.img
Enjoy it? Thank me!
Is it possible to get it in an update.zip format ? I don't want to mess with s-off for now.
SKAm69 said:
Is it possible to get it in an update.zip format ? I don't want to mess with s-off for now.
Click to expand...
Click to collapse
Not from me, sorry. I don't see any point in supporting the legacy method, especially when this version of CW doesn't give any readily-apparent advantages to the older one.
Nice find. I actually have S-OFF but when I start this recovery it is telling me error mounting system, data and others. Is this normal or is something wrong with my setup?
JAWheat411 said:
Nice find. I actually have S-OFF but when I start this recovery it is telling me error mounting system, data and others. Is this normal or is something wrong with my setup?
Click to expand...
Click to collapse
It IS a test build. I'm about to flash it now, I'll let you know if it's just you or not
And FLASH_IMAGE is indeed included, at least its built into cm6.
Edit: it isn't just you, the recovery is practically nonfunctional haha. There are errors all over when you boot into it, mount usb storage crashes it, and it can't mount anything, including the sd card, so its virtually pointless to flash at this point
MusicMan374 said:
It IS a test build. I'm about to flash it now, I'll let you know if it's just you or not
And FLASH_IMAGE is indeed included, at least its built into cm6.
Edit: it isn't just you, the recovery is practically nonfunctional haha. There are errors all over when you boot into it, mount usb storage crashes it, and it can't mount anything, including the sd card, so its virtually pointless to flash. Might even be as bad as arayrays gingerbread port, that hardly works either
Click to expand...
Click to collapse
But the only new features you see would be the new color?
Ace42 said:
But the only new features you see would be the new color?
Click to expand...
Click to collapse
Pretty much yeah. It was orange instead of green. Some of the menus had different names, easier to understand for noobs, but they had the same content. But don't flash it until it's more functional.
Sent from my T-Mobile myTouch 3G Slide
Ok well can someone post an older Clockwork recovery.img so we can reflash it? We can't use this one to do anything.
MusicMan374 said:
It IS a test build.
Edit: it isn't just you, the recovery is practically nonfunctional haha. There are errors all over when you boot into it, mount usb storage crashes it, and it can't mount anything, including the sd card, so its virtually pointless to flash. Might even be as bad as arayrays gingerbread port, that hardly works either
Click to expand...
Click to collapse
I was at work when I uploaded the image and because of that I only briefly tested it. The errors at the beginning aren't critical, but I'll look into the overall functionality being broken, at some point tonight.
Hence this being a "TEST".
Thanks
I appreciate that. I like beta testing new things. It does seem to have a few more functions. I just couldn't revert back.....
Sent from my T-Mobile myTouch 3G Slide using XDA App
Flash this to go back to 2.5.0.1: http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.1-espresso.img
Actually.. i see a new option to partition SD card straight from the recovery menu... this is a very useful feature... and i think thats why it deserves that build jump from 2.5 to 3.0..... but at this point... it is in an UNUSABLE state.. i understand it is a test build... but i cannot test anything because it crashes on every single option you can possibly choose... will go back to 2.5 and wait for a stable, or at least more functional test build... hope to see some improvements soon... I do not doubt that you guys can have this thing up and running in no timee.. its a good starting point.. Keep the work going... looking forward to it...
was anyone else hoping for a terminal like in good ol' amon_ra? I was...
Be nice to have it in update.zip form for the ones without s_off
Sent from my T-Mobile myTouch 3G Slide using XDA App
elry567 said:
Be nice to have it in update.zip form for the ones without s_off
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
S-off really is a must have. I attached the working build of 3.0.0.5, you have to either use flash_image with it, or fastboot flash, both of which require s-off.
Thnx
Sent from my T-Mobile myTouch 3G Slide using XDA App
mymomma8 said:
it crashes on every single option you can possibly choose
Click to expand...
Click to collapse
Sounds like youre doing it wrong. You can no longer use the power button to select options but rather the trackball
Sent from my T-Mobile myTouch 3G Slide using XDA App
I don't think that file was cw3 I flashed it and still have 2.5 (file by musicman)
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
MusicMan374 said:
S-off really is a must have. I attached the working build of 3.0.0.5, you have to either use flash_image with it, or fastboot flash, both of which require s-off.
Click to expand...
Click to collapse
I flashed it... it seems to be CW 2.5.... not CW 3.0 :/
guitarist5122 said:
Sounds like youre doing it wrong. You can no longer use the power button to select options but rather the trackball
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
No, i select the options with the trackpad... the problem is a bunch of recovery/cache errorss... that i cannot seem to fix, i tried wiping recovery/cache... and problem still persistess
EDIT: FOUND A TRULLY WORKING BUILD Thanks to whoareyou and can be downloaded from
http://forum.xda-developers.com/attachment.php?attachmentid=490785&d=1295154563
No crashes, everything works... sucessfully partitioned SD card. Will create a guide on how to partition SD card using this recovery.
mymomma8 said:
I flashed it... it seems to be CW 2.5.... not CW 3.0 :/
No, i select the options with the trackpad... the problem is a bunch of recovery/cache errorss... that i cannot seem to fix, i tried wiping recovery/cache... and problem still persistess
EDIT: FOUND A TRULLY WORKING BUILD Thanks to whoareyou and can be downloaded from
http://forum.xda-developers.com/attachment.php?attachmentid=490785&d=1295154563
No crashes, everything works... sucessfully partitioned SD card. Will create a guide on how to partition SD card using this recovery.
Click to expand...
Click to collapse
Alright thanks it works now!
It seems that there are a lot of ROMs out there that are doing some funky stuff from the edify scripting in CWM and providing a poor user experience. This overall hurts the entire custom NookColor community and puts a bad taste in peoples mouths.
This post is to point out best practices when creating CWM flashable zips in a consistant way allowing the user to upgrade and migrate between roms in a predictable way.
Rule #1: Don't touch /data!
There are many reasons why you don't want to touch /data but the most important is to allow the user to be able to upgrade your rom without completely wiping your data.
If you want to bundle in an applications (first of all... don't but if you reaally think it is necessary) put it in /system/app as a system app.
Rule #2: Don't overwrite /boot/uRecRam and /boot/uRecImg!
ROM and CWM should be separate. Users should be able to use your rom with CWM or even the stock recovery if they wish to. Allow the user to choose what version of CWM they want to run and allow them to upgrade it independently of your rom.
This allows you to not re-release roms every time a new version of CWM is released.
Exceptions to the rule are update zip that are intended to install CWM (which is ok) or zips that will restore the entire system to stock.
Rule #3 Learn edify
Edify scripting is quite powerful. It saddens me to open up the updater-script of a rom and see it extracting a script and then executing the script.
Don't store your roms as .tars and require a script to extract them to the right locations, you should be doing this all from edify scripts.
Rule #4: Only touch /system and /boot/uImage and /boot/uRamdisk
All other files should be off-limit! This goes back to rule #1 and rule #2. A rom should consits of a kernel, a ramdisk to boot the system and /system files for running the rom!
Rule #5: NEVER EVER EVER modify partitions or wipe the EMMC completely!
I cannot stress this one enough. Use stock partition scheme for your rom. It may seem like a "waste" to you but this is what will make all our roms compatible with each other!
Also the Nookcolor stores NVRAM type information on /dev/block/mmcblk0p2 and factory restore information and a backup of p2 on /dev/block/mmcblk0p3.
If you wipe these directories in your update.zip you WILL BRICK THE USERS NC! It may work for you but they can never return to stock. Their serial number and mac addresses will be lost!
Just don't even think about doing anything with the partition map or these partitions!
Rule #6: When in doubt look at the CM update.zips
A good example of the rules above is portrayed in the CyanogenMod nightly roms for the NC. Look at the updater-script in META-INF/com/google/android and see how things are done.
If we all agree to follow these rules the NC users will get a better and more consistent experience and you will have more users for your rom.
For the users I will list the ROM that are compatible with the list above and list ROMs that don't follow these rules.
ROMs that follow proper packaging
These rom have been built properly according to the rules in the OP. I highly recommend testing any of these out.
Cyanogenmod Nightlies
phiremod nook V5.2
Nookie Froyo 0.6.8
(Utility Update.zip) Nook Color SDcard and emmc swap
ROMs that DON'T follow proper packaging
Use these roms at your own risk!
Flashable eMMC dual boot ROMs
Dual booting roms violates changing the the parition table! If you want to dual boot I would use a bootable SD. If you get a class 6 or higher SD card the performance difference should be pretty low. The perceived speed boost i believe is negligible.
Avoid this rom if you are new to Android or the NookColor. I would call this rom an "Advanced user" rom and not for new members of the community who are unfamiliar with Android, Linux, or the NookColor
Click to expand...
Click to collapse
HC v4 eMMC 2nd ed. - Flashable ZIP
This rom packaging is the poster child for how to do it wrong. They overwrite your /data for app customization. It uses an external script and tar files for extraction and overwrites all of /boot!
AVOID THIS ROM PACKAGE!
Click to expand...
Click to collapse
This looks very wise and in accord with general programming principles.
In the same area of discussion, can you talk about whether or not to clear cache while doing this same update process.
In fact, some explanation of /cache and Dalvik Cache and Market Cache might help to alleviate confusion, especially in regards to specifically what they are, and when one should clear them.
Sure, a "cache" is a piece of data that is frequently used, and so put in a more accessible place, but in typical confusing fashion, that general term is being used in a specific way in Android.
Thanks !
Nice. Good guidelines.
It would, in a perfect world, be nice if a standard CWM recovery would give a choice to either write to SD or EMMC. Then we would not have many of these more involved boot file and CW file edits and changes that are making things more complicated.
If everyone used CW to right to EMMC, this would be easy. But users like myself are running ROMs from SD and are always looking for a way to easily update and flash mods or ubdate ROMs to SD. Yes I use ADB, and other methods, but often I am traveling and away from my office or studio were my PC's are.
Any ideas on CWM to keep things more unified as the op suggests and be able to write to bootable SD cards?
Thanks for starting the discussion.
12
Good explanation/write-up, nemith. Not being a dev, but a user, it helps me to better understand which ROMs to use on my NC. I really liked HC EMMC, but did not realize that it would make it so I could never return back to stock (losing my S/N and such).
Also concur with ADude about cache....a good explanation would be helpful here. I only clear the cache/Dalvik when installing a new kernel. Not sure if even necessary? And, I clear AFTER installing, not before, so not sure if I am even doing that in the correct order. Setting the record straight would go a long way for us non-devs.
Sorry, one more thing, it would be great to have a consistently updated bootable SD card with latest/greatest of CWR on it. I am still on 3.0.0.6 and I am not sure why??
Thanks!
~ Razir
Could have used this a few months ago.
Thank you.
Nemith, your thread is directed at devs. If you want to make sure people don't flash my HC v4 2nd edition, you might want to invite users to read this as well.
nemith said:
ROMs that DON'T follow proper packaging
Use these roms at your own risk!
Flashable eMMC dual boot ROMs
Dual booting roms violates changing the the parition table! If you want to dual boot I would use a bootable SD. If you get a class 6 or higher SD card the performance difference should be pretty low. The perceived speed boost i believe is negligible.
I would avoid dual booting roms if you can!
Click to expand...
Click to collapse
I have this installed..... I am going to run the dual boot removal zip when I get home.
Am I screwed? Anthing I need to worry about?
12paq said:
Nice. Good guidelines.
It would, in a perfect world, be nice if a standard CWM recovery would give a choice to either write to SD or EMMC. Then we would not have many of these more involved boot file and CW file edits and changes that are making things more complicated.
12
Click to expand...
Click to collapse
I've thought of this. CWM would require a major rewrite to do this and the changes would never be sucked in.
Maybe one of these day's I will may my own CWM Kang that can do this, or better yet a desktop application that takes a update.zip and splits out a SD image!
cromanorn said:
I have this installed..... I am going to run the dual boot removal zip when I get home.
Am I screwed? Anthing I need to worry about?
Click to expand...
Click to collapse
No you are just in the "I am smart enough to use these roms without posting big "help me" posts on XDA.
These roms are not really harmful, but they should be avoided by people who don't understand the nook and how it works.
If you understand Android and how the NC is laid out then there should be minimal risk to using these roms. I just want to spell it out for people who are new to the NC or Android that these are "advanced" roms.
nemith said:
No you are just in the "I am smart enough to use these roms without posting big "help me" posts on XDA.
These roms are not really harmful, but they should be avoided by people who don't understand the nook and how it works.
If you understand Android and how the NC is laid out then there should be minimal risk to using these roms. I just want to spell it out for people who are new to the NC or Android that these are "advanced" roms.
Click to expand...
Click to collapse
THANKS!!! I had the NC for about 4 days now and would hate to have messed it up in the long run. I have a Droid Incredible that has been flashed more times than I can remember. It would be nice if the warnings were incorporated into the OP of these roms. I read the entire thread before flashing and I may not have flashed if this warning was there. I like having the option of going back to Stock without repercussions.
edit: Just saw the update you put in your OP about advanced users. I don't consider myself advanced but I am not a beginner either.
nemith said:
I've thought of this. CWM would require a major rewrite to do this and the changes would never be sucked in.
Maybe one of these day's I will may my own CWM Kang that can do this, or better yet a desktop application that takes a update.zip and splits out a SD image!
Click to expand...
Click to collapse
Yup. That would be very nice.
The Nook having SD boot priority really makes it versatile for testing, and quite recoverable. It also satisfies a unique situation where many users have a family device with Nook magazines and children's books not available on the Nook app, so many like myself are booting experiments and daily runners from SD and keeping the wife happy. LOL.
cromanorn said:
edit: Just saw the update you put in your OP about advanced users. I don't consider myself advanced but I am not a beginner either.
Click to expand...
Click to collapse
If you go digging at nookdevs.com and on your own NC you should be able to figure out what is safe and what is not.
nemith said:
Rule #6: When in doubt look at the CM update.zips
A good example of the rules above is portrayed in the CyanogenMod nightly roms for the NC. Look at the updater-script in META-INF/com/google/android and see how things are done.
If we all agree to follow these rules the NC users will get a better and more consistent experience and you will have more users for your rom.
Click to expand...
Click to collapse
the ironic thing is CM Roms don't fully follow Rule #3 since they have multiple scripts that run inside their packages during rom installation.
I'm not sure you are correct in saying that if you flash one of the HC emmc roms you can not revert back to stock. I know for a fact I have done both the dual boot, and HC emmc roms and reverted back to stock multiple times after doing so
I'm not saying you are wrong but I don't think i did anything to "advanced" to get back.
Quoted:
(I have this installed..... I am going to run the dual boot removal zip when I get home.
Am I screwed? Anthing I need to worry about?)
I had it installed and got back to stock no problem... i'm not sure what he is talking about.... i could be wrong though...
It was dualbooted CM7 and HC
went back to stock, registered with BN and all was well.
nooted it and then install HC on emmc
reverted back to stock to set up the ubuntu on NC
got bored of that and am back on HC on emmc
I went back to stock after both as well. Has anyone not been able to after using one of those two roms? I work at b&n and I had to spend time with the stock since they wanted me on the nook counter. I've been back and forth between all the roms more times then I can count.
Sent from my NookColor using Tapatalk
To the OP again i'm not trying to be rude, but could you respond to the last few commenter on this thread, it seems like my self a few others are having an experience that is quite different from what you described in your first post.
Could you help me understand why it hasn't been that difficult to get back from the roms that you specifically said can make it very hard to go back to stock from for us?
I'm currently on HM on emmc and if i did something fancy to get back the last time i restores i'd like to know if i need to do it again.
(edit) I bring this back up only because I saw this thread referenced again recently, which means it is having an effect on peoples work so i'm just trying to understand it.
[Edit] It was the SD card's fault. It seemingly worked fine in the laptop and it mounted fine in CW Recovery, but as soon as I used a different SD card I could flash zips again.
So, now I'm playing with phiremod v6 and loving the Nook again.
I believe I just bricked my Nook through use of the dual boot script.
I can only boot from SD into CW but not a single zip can be applied to the internal storage. Not even the "reverse dual boot" zip will run. They all error out.
I believe this is due to unexpected partitioning.
I even formatted boot, system and cache and still it will not restore any Roms.
So now I'm hoping to access the Nook through USB and repartition the internal storage manually. But before I do that, I need to learn about ADB and what the correct settings are.
jlt220 said:
To the OP again i'm not trying to be rude, but could you respond to the last few commenter on this thread, it seems like my self a few others are having an experience that is quite different from what you described in your first post.
Could you help me understand why it hasn't been that difficult to get back from the roms that you specifically said can make it very hard to go back to stock from for us?
I'm currently on HM on emmc and if i did something fancy to get back the last time i restores i'd like to know if i need to do it again.
(edit) I bring this back up only because I saw this thread referenced again recently, which means it is having an effect on peoples work so i'm just trying to understand it.
Click to expand...
Click to collapse
I don't think Nemith was saying that the existing dual boot installer is going to prevent you from returning to stock. He singled it out as a "ROM" that modifies the partition table, which can be a dangerous thing to do. There is information stored in the /dev/block/mmcblk0p2 and /dev/block/mmcblk0p3 partitions that is specific to each device and required by the B&N software. This information can't be rebuilt easily if lost.
The dual boot install and removal tools (in their current versions) appear to leave these partitions in tact. They are modifying the partition table though, so they're not recommended for novice users. You were able to install and uninstall it with no problems, so you're clearly not one .
The other point is that future versions of the dual boot (doubtful since it has a good dev) or other similar style "ROMs" may not be so careful with your 0p2 and 0p3 partitions.
Hey this is gonna sound dumb but can we use hd2 cwm builds
sent by DAN SWAGGER via tapatalk/simple mobile
dswaggz said:
Hey this is gonna sound dumb but can we use hd2 cwm builds
Click to expand...
Click to collapse
No. Neopeek already has made CWM for the RHOD. It's still based on the SD card tho...
If you think we can "just use" the HD2's NAND ROM's, you are kidding yourself...
Ok well I was in the x1 section will there builds work an what is the difference or benifit from using cwm over XDANDROID
sent by DAN SWAGGER via tapatalk/simple mobile
I think you are asking the difference between cwm builds and looped builds.
well IMO updating files like test libs is much easier in cwm but reverting test libs is much easier in looped system. On the whole i think cwm should be used by expert users who know how to use adb and unix commands to repair stuff when things go wrong.
There should be no problem running xdandroid as a cwm build but someone has to be motivated enough to do that.
tovarish said:
There should be no problem running xdandroid as a cwm build but someone has to be motivated enough to do that.
Click to expand...
Click to collapse
Indeed, the X1 is running CWM from Neopeek - SD card installs.
I made a FRX06 CWM build but it was really buggy. I didn't give it the attention it deserved, but since I couldn't get it off the ground on my phone I never posted it.
There's nothing holding anyone back from doing it... It booted for me, just had a ton of bugs - much more than the normal FRX06 build did, so I put it off to the side.
I can confirm frx06 cwm build is working for me
yankees2450 said:
I can confirm frx06 cwm build is working for me
Click to expand...
Click to collapse
Oh nice, i thought that the rootfs differences would be the main cause of problems. was that your experience.
I am running frx06 via cwm too (the same FRX06 build I only made a .zip package of it). Everything works fine for me just like the normal FRX06 build. If people want it, I can post a link.
But this is a bit off topic.
The answer on your question is no, we can't use hd2 cwm builds (if i'm right )
tovarish said:
Oh nice, i thought that the rootfs differences would be the main cause of problems. was that your experience.
Click to expand...
Click to collapse
the roofts is the same. I think neopeek change a few things, like init, initrd etc....
I'm using. [BUILD] **Complete Froyo Bundle!!** FRX06 - "Stable" - Minor Fixes http://forum.xda-developers.com/showthread.php?t=951962
here
frx06 cwm build
http://www.multiupload.com/PGZ7H8KTIT
tovarish said:
I think you are asking the difference between cwm builds and looped builds.
well IMO updating files like test libs is much easier in cwm but reverting test libs is much easier in looped system. On the whole i think cwm should be used by expert users who know how to use adb and unix commands to repair stuff when things go wrong.
There should be no problem running xdandroid as a cwm build but someone has to be motivated enough to do that.
Click to expand...
Click to collapse
I agree to a certain degree. But just to add, with cwm if you mess up it is very easy to fix. Their is a backup/restore function. When you get your build working you backup. Then if you have messed something up or currupted your data you don't even need to reinstall! Just restore the data partition. If you are messing around with the system and you mess up just restore the system partition, your data will even be safe. I find this very handy, it is a pain to havta reinstall everytime something breaks
Well how big can you make the partions
sent by DAN SWAGGER via tapatalk/simple mobile
dswaggz said:
Well how big can you make the partions
Click to expand...
Click to collapse
I don't know if there's an upper limit, AFAIK there's only a lower limit... 120-150mb for system, and at least 250mb I'd say for data...
dswaggz said:
Well how big can you make the partions
sent by DAN SWAGGER via tapatalk/simple mobile
Click to expand...
Click to collapse
This is recommended, but if you want larger partitions, it's also good:
Code:
1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / about 150MB -> depends on the build )
3rd partition: EXT2 (data / about 250MB)
4th partition: EXT2 (cache / about 50MB)
You have to make the partitions in that order. If you want a bigger data part, just make it about 500MB or 1GB.
I would recommend a much larger /cache partition (100+ MB) if you plan on installing many apps. This is because the dalvik cache is mounted on the cache partition.
Yes maybe thats better, but I just posted the sizes that are recommended by neopeek (who made CMW avaible on our devices).
But yes, if you have a 2GB sd card or something, it's better to make the partitions larger.
This works faster than the pure FRX06 on the main page. You should post it so others can use this version
bleuleon said:
This works faster than the pure FRX06 on the main page. You should post it so others can use this version
Click to expand...
Click to collapse
It seems faster to me, too... but I don't know if I'm just imagining it or not. Is there a reason it would be faster? I don't really know enough about these things to hazard a guess...
ppcfly said:
It seems faster to me, too... but I don't know if I'm just imagining it or not. Is there a reason it would be faster? I don't really know enough about these things to hazard a guess...
Click to expand...
Click to collapse
I guess because the partitions are dedicated, instead of loop mounts? I wouldn't think this would net much speed... Perhaps it does. Perhaps it's just snake oil and that's your perception .
arrrghhh said:
I guess because the partitions are dedicated, instead of loop mounts? I wouldn't think this would net much speed... Perhaps it does. Perhaps it's just snake oil and that's your perception .
Click to expand...
Click to collapse
I think after switching to partitions on FRX, I have seen a speed improvement. It's very hard to say for sure on this sorta thing, especially since I only spent a few days with FRX (coming from GRX) before partitioning.
However, the amount of times where I wonder whether my device is frozen or just didn't recognize my input has gone down to bearable levels recently, and the only change that seems relevant I've made recently is partitioning.
arrrghhh said:
I guess because the partitions are dedicated, instead of loop mounts? I wouldn't think this would net much speed... Perhaps it does. Perhaps it's just snake oil and that's your perception .
Click to expand...
Click to collapse
A strong possibility... perhaps someone needs to make an app with an dummy dial I can turn up to 11.
Have you tried the cwm fx6 yet arrrghhh? Just curious if you think it's faster or not...
Well, hallo there!
It's been a while since I've posted a release thread on XDA... I've been lurking in the shadows (and on IRC) for quite some time.
Here, I present to you a teaser of things to come:
ClockworkMod Recovery (non-touch) 6.0.1.5 for the AT&T Optimus G.
What is this?
This is a "recovery" for your phone, it allows you to install custom ROMs, back up your phone, fix it when it breaks, and much more.
This specific version is "ClockworkMod", which was created by the CyanogenMod team and Koush.
There are many recovery versions out there, I have picked ClockworkMod because it is very easy to compile and debug.
I will compile other recoveries as time permits.
Click to expand...
Click to collapse
Where can I get it?
UPDATE: I am now providing download links.
Please go here to download it: http://downloads.codefi.re/thecubed/lgoptimusg/att/recoveries/
Note: this is a "tethered" build of CWM, as you can not flash it. You must use fastboot to boot the image every time you wish to enter recovery.
This is due to the locked bootloader on this device.
READ THE INSTRUCTIONS BEFORE DOING ANYTHING!
This is *not* safe, and should *not* be done by anyone unsure of what they are doing.
I will post links once I have ironed out bugs, but I WILL NOT SUPPORT anyone using it to modify their phone.
Please don't use this if you don't know how to LGNPST your phone back from the dead, should you accidentally kill it.
(Also, I will find somewhere to mirror LGNPST and the related files, as I can't host them from my server due to legal reasons. I will, however, mirror the .TOT file in case LG decides to take it down.)
Click to expand...
Click to collapse
Instructions
Check back here in a few hours, I'll have something done by then
Click to expand...
Click to collapse
The goods!
Here's a (semi-arty) pic of it running on my Optimus G:
And, here's a video for extra proof
Luckily the video quality isn't potato, but the audio sure is. My explanation is that my HTC Vivid doesn't like me. An engineer's explanation would be that I was speaking softly, as it was 1:30AM at the time of recording, and the phone merely decided that my meek volume was purely background noise... at least, I think that's what an engineer would say, as I haven't graduated yet.
Click to expand...
Click to collapse
SPECIAL THANKS!
Here's my favorite section of an XDA post: the "special thanks to" section.
Without the help of these awesome people, I would have nothing of interest to say, and would just be a random guy with a phone.
Seriously, these guys are awesome.
Here's the list (in no special order, and by IRC name):
Shelnutt2
sextape
xboxfanj
jonasl
kmdm
synergy
DeamonFish
chachin
..and Zanzibar (because why not?!)
If I've forgotten anyone, please let me know-- I want to make sure everyone who had a hand in this gets a shout-out.
Please, support these awesome people if you get a chance, or drop by the IRC channel and say hi
Click to expand...
Click to collapse
How can I contact you?
Need to get a hold of me, or anybody else? Come on IRC -- just go to http://webchat.freenode.net and use #lg-optimus-g as the channel name. Pick a nice nickname and say Hi
I'm IOMonster on IRC, and if I'm around, just say my name and I'll probably say hi back.
Click to expand...
Click to collapse
Alright everyone, hope you enjoy
Wow that does look pretty nice.
Looking forward to the fruits of your continued endeavor regarding this device, sir. Well done.
Very nice, cubed. That's some good, and fast, work.
Awesome work! Can't wait to see more progress on this. I'm assuming a Sprint version will be available eventually.
Sent from my PG86100 using xda app-developers app
Very cool!
subbed hopefully this will work with the Rogers version as well or one will come out of this,
either way spectacular work
BloodBaron said:
subbed hopefully this will work with the Rogers version as well or one will come out of this,
either way spectacular work
Click to expand...
Click to collapse
Great start! I can't wait to see how it progresses, looks like it's going fairly quickly at this point.
Delete post
So it boots cwm even with a locked bootloader?
That's peculiar. Either way great job!
Sent from my HTC_Flyer_P512_NA using xda app-developers app
can't wait
Can't wait. Great job!
Awesome work....you guys are amazing
Sent from my LG-E970 using xda app-developers app
Snow_fox said:
So it boots cwm even with a locked bootloader?
That's peculiar. Either way great job!
Sent from my HTC_Flyer_P512_NA using xda app-developers app
Click to expand...
Click to collapse
Apparently fastboot BOOT will accept any unsigned image regardless of bootloader status.
Sent from my LG-E970 using Tapatalk 2
I think this thread is for AT&T version, here's International.
Although placeholder threads are generally not allowed in the Dev section, we will allow this one, as the OP has stated he will provide the link if asked. (He does not want people to brick their device.)
Woot, so I patched CWM with a little homegrown patch to enable you to mount the external SD card.
This is necessary since CWM disables USB mounting by default on devices with an internal storage card that is shared with the /data partition.
Here's the status update:
What works:
Backups to Internal and External SD card
Restore from Internal or External SD card
ADB Shell Access
Battery charging (it's part of the kernel, I merely verified it's working)
Volume Keys / Power Key
Zip install from internal/external SD
USB Mounting
(in theory) Wipe Data ***see note***
What doesn't works:
Softkeys
Party mode
***Note: I have NOT tested "Wipe Data" or "Format /data". I do not suggest you try either for the moment.
This is because the internal SD card resides in /data/media. Erasing /data has a chance of erasing your internal SD. There are checks in CWM for this, but until I investigate, let's just be safe. If you need to erase your phone, let the stock recovery do that.
I am still working on some instructions for a safe way to get into CWM without the potential of getting stuck in some unknown mode. I will write up the instructions tomorrow and post links to the recovery.
Thanks everyone for your kind words on IRC as well, I appreciate all your moral support!
Thats a great start.. i do hope it is possible for the Japanese (L-01E) Version.... though the Japanese version already has microSD card support up to 64GB via SDXC
Wow, this is awesome! Keep up the great work!
thanks for all the work, I look forward to this device as I am getting it today, I do have some background in Linux and could possibly be building a ROM soon.
I love you right now. So stoked.
Sent from my LG-E970
I wanted to post this here since I've been busting my tail on an update for a week now. This WILL flash, Backup & Restore android 4.4 roms! USB mounting, internal & external sdcard mounts as well. There are still a few bugs to work out but give it a go & some feedback. It's still a WIP but plenty stable to use daily for now.
Also anyone interested in flashing the CandyKat sweetener packs, you may now do so with this recovery!!
TWRP 2.8.7.0
I am not responsible for misuse, bricks, or exploding devices! Flash at your own risk! You can download the zip file & flash it from within your existing recovery & reboot to recovery.
CREDITS: Javelinanddart for fixing mounts, f2fs, & for fixing vibration for 5.0 & up Disconnecktie && Santod040 I have bugged these guys to death to get this working so Please stop in & thank these guys as well. They are a huge part of the success of this! Obviously this couldn't happen without Omniroms Source! And a huge thanks for
Dees_Troy for his guide to compiling twrp recovery!!
TWRP Themes have changed a bit & if you use a them then you'll want to checkout this link.
THEMING TWRP THE NEW WAY!
What's new in 2.8.7.0
- Initial ground work for software drawn keyboard (_that)
- Fix handling of wiping internal storage on datamedia devices (xuefer)
- Allow DataManager to set and read values from the system properties (xuefer)
- Fix crash when taking screenshots on arm64 devices (xuefer)
- Fix error message after an ORS script completes (Dees_Troy)
- Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
- Add system read only option - more details below (Dees_Troy)
- Add resize2fs and GUI option to run resize2fs (Dees_Troy)
- Fix crash loop caused by empty lines in AOSP recovery command file (_that)
- Prevent duplicate page overlays such as multiple lock screens (mdmower)
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won't prompt to install SuperSU and TWRP won't try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don't take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
THEMING?
USE 1080P THEMES
Yeah!!
This is working perfect! Damn I missed TWRP. So freaking sweet!!
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Works well except mount memory
Liwais said:
Works well except mount memory
Click to expand...
Click to collapse
Mounting which partition? Anyone that finds an error or a bug should try posting the recovery log after said error. Don't post the entire log in a post but put it on pastebin or something similar. Having the logs greatly increases the likely hood the issue will be fixed. Thanks.
Liwais said:
Works well except mount memory
Click to expand...
Click to collapse
What do you mean by mount memory? Where you add something from the pc to the sd card & it shows up on the internal when in twrp? The internal sd card mounts when connected to the pc, not the external sd. I don't know if that's how it's suppose to work or not. This is my first twrp attempt and I had to build it from scratch basically. Like Disconnecktie stated, a log may be helpful.
Great work. Missed TWRP. Just had to tick off my internal sd. Panicked when my partition wasn't visible with my ROMs to flash. LOL.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
I had in mind when're in rekaveri not mount the memory to your PC
Maybe this Problem just me, let me know
Updated OP with better mount paths & usb mounting working better. Guys if you all test this latest and give feedback, I'm working on getting this to the official site and in Bigbiff's thread. I appreciate your input. I have worked tirelessly to make this work but I may be missing something. Let me know what you find, working or not. I know the vibrate isn't currently working in recovery but I am looking into that.
gimmeitorilltell said:
Updated OP with better mount paths & usb mounting working better. Guys if you all test this latest and give feedback, I'm working on getting this to the official site and in Bigbiff's thread. I appreciate your input. I have worked tirelessly to make this work but I may be missing something. Let me know what you find, working or not. I know the vibrate isn't currently working in recovery but I am looking into that.
Click to expand...
Click to collapse
For some reason (most likely that I'm a dummy, or missed reading somewhere)
Recently my SD card took a poo, so I've been saving to internal memory.
I flashed TWRP. When I look in sdcard I have no files visible. When I am booted into CandyKat I can see my files with my file explorer. Am I missing a valid mount somewhere? When I go to / I don't see a folder called storage, and in my /sdcard all I see is a folder called TWRP which is empty.
THanks!
skearton said:
For some reason (most likely that I'm a dummy, or missed reading somewhere)
Recently my SD card took a poo, so I've been saving to internal memory.
I flashed TWRP. When I look in sdcard I have no files visible. When I am booted into CandyKat I can see my files with my file explorer. Am I missing a valid mount somewhere? When I go to / I don't see a folder called storage, and in my /sdcard all I see is a folder called TWRP which is empty.
THanks!
Click to expand...
Click to collapse
When you are in TWRP recovery are you selecting "Internal SDcard" or "MicroSD card"
Edit: Latest twrp recovery with vibrations enabled!
gimmeitorilltell said:
Updated OP with better mount paths & usb mounting working better. Guys if you all test this latest and give feedback, I'm working on getting this to the official site and in Bigbiff's thread. I appreciate your input. I have worked tirelessly to make this work but I may be missing something. Let me know what you find, working or not. I know the vibrate isn't currently working in recovery but I am looking into that.
Click to expand...
Click to collapse
Haven't tried your update yet but on the last build in order to use themes I had to load them into /data/media/0/TWRP/theme/ which I believe will be overwritten as soon as I flash another ROM. Is this one of your corrected paths?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
developweb said:
Haven't tried your update yet but on the last build in order to use themes I had to load them into /data/media/0/TWRP/theme/ which I believe will be overwritten as soon as I flash another ROM. Is this one of your corrected paths?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
No it was not. I've been waiting on more feedback from the update or any of my twrp builds. Now that I'm aware of it, I'll look into that so we can get it official in Bigbiffs twrp thread. I think it's close enough for him to release it as an official but this is my personal feelings. It'll be a couple days maybe before I get back to it since I've spent the last week concentrating on this, it's time for me to move on to other things for a moment.
Sent from my HTC One Max using Tapatalk!
Newest build is working g sweet gimme. Love how ya added the button vibrate too. So far I've done 3 full wipes/flashes and your twrp has been flawless thanks for bringing this to us gimme.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
developweb said:
Haven't tried your update yet but on the last build in order to use themes I had to load them into /data/media/0/TWRP/theme/ which I believe will be overwritten as soon as I flash another ROM. Is this one of your corrected paths?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
We can probably keep this here until the bugs are worked out. Have you tried the latest here yet? I don't theme my recovery but I'm willing to so I can get it correct.
Also that may be something you can set in twrp, set a different default path for themes but I'm not 100% sure.
gimmeitorilltell said:
We can probably keep this here until the bugs are worked out. Have you tried the latest here yet? I don't theme my recovery but I'm willing to so I can get it correct.
Also that may be something you can set in twrp, set a different default path for themes but I'm not 100% sure.
Click to expand...
Click to collapse
Default path in latest is correct now. Themes work from the correct directory now (/sdcard/TWRP/theme/ui.zip ) so they won't get deleted. Love button vibration as well! Excellent work.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
developweb said:
Default path in latest is correct now. Themes work from the correct directory now (/sdcard/TWRP/theme/ui.zip ) so they won't get deleted. Love button vibration as well! Excellent work.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
Thank you for the feedback, it is very much appreciated! If you run into anything else, good or bad, Please feel free to give a shout out. I have OCD and with the vibration as an option, well it just was NOT an option to NOT work.. Lol
gimmeitorilltell said:
Thank you for the feedback, it is very much appreciated! If you run into anything else, good or bad, Please feel free to give a shout out. I have OCD and with the vibration as an option, well it just was NOT an option to NOT work.. Lol
Click to expand...
Click to collapse
I tried to install the full aroma rom patch by pollution and it seemed to work but gave com.android.phone error on boot. So I thought easy fix, I'll restore the backup I made with TWRP yesterday and got even more errors. Yes, I factory reset before restoring. It seems that this TWRP is not doing everything like it used to under the 4.2's. I'm going to go back to CWM and restore a CWM backup, regroup, recharge.......and try again from scratch to test this thing out again. Wish me luck.
Liwais said:
I had in mind when're in rekaveri not mount the memory to your PC
Maybe this Problem just me, let me know
Click to expand...
Click to collapse
I'm not sure that I understand what you're saying? The internal sd mounts to the pc once you go into twrp & mount it.
developweb said:
I tried to install the full aroma rom patch by pollution and it seemed to work but gave com.android.phone error on boot. So I thought easy fix, I'll restore the backup I made with TWRP yesterday and got even more errors. Yes, I factory reset before restoring. It seems that this TWRP is not doing everything like it used to under the 4.2's. I'm going to go back to CWM and restore a CWM backup, regroup, recharge.......and try again from scratch to test this thing out again. Wish me luck.
Click to expand...
Click to collapse
Best of luck to ya! I have restored my nandroid with twrp but not in my latest version. I'll give it a try this evening and see what happens on my end. I have not used the aroma installer because I personally would rather not use it. I just use the camera fix from Pollution since I don't have the screen flicker or any other issues with my phone.