This thread serves the purpose of providing a flashable ZIP file for TWRP that can be flashed in CWM or an older TWRP.
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, some of the changes in 2.6.0.0 will likely not be visible with your custom theme.
- Can encrypt a backup to prevent theft of private data from your backup files
- Updated graphics / icon courtesy of shift
- Updated exFAT to latest commits
- Fixed a problem with Samsung TouchWiz decryption
- Update SuperSU binary
- Fixed saving of backup partitions list
- Fixed saving of last used zip install folder
- Fixed backup of datadata on devices that use a separate partition for datadata
- Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
- Fixed some problems with partitioning a SD card
- Various other bug fixes and tweaks
DOWNLOAD: TWRP-2.6.0.0-olympus.
Thanks!
=]
I know it's all based on personal preferences but I was wondering if anyone can give me their opinions on which in their point of view is better? This version of twrp or the current version on cwm. I have done my research on the two but was wondering in the case of the Atrix which do people prefer.
Sent from my MB860 using xda app-developers app
If you have a lot of files and folders (like I do) you will love the ability to easily browse files in TWRP. In CWM pressing the volume key is a nuisance.
Being able to name the backup within TWRP is also very helpful.
I think CWM is simpler. If your touchscreen breaks you can still flash ROMs.
For the average user TWRP is probably the better choice. I have used it for a few months with no issue.
Thanks a lot
Thank you very much atrix4g18! :good:
great job ty
May I ask how I install it over CMW? Don't want to brake anything.
Thx in advanced.
Sent from my MB860 using Tapatalk 2
DowJonesARG said:
May I ask how I install it over CMW? Don't want to brake anything.
Thx in advanced.
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
CWM? You just flash it. Select the zip like it was a ROM. You don't need to wipe anything.
atrix4g18 said:
CWM? You just flash it. Select the zip like it was a ROM. You don't need to wipe anything.
Click to expand...
Click to collapse
So, I can Flash it with CMW? Ok. Thx.
Sent from my MB860 using Tapatalk 2
Yes, you can. Or install the Goo Manager from the Market and install It automatically.
nozorrog said:
Yes, you can. Or install the Goo Manager from the Market and install It automatically.
Click to expand...
Click to collapse
Which defeats the purpose of this flashable zip.
Guys guys! Don't fight over me, it makes me blush:laugh:
Just installed with CRW, works like a charm. Thx for the help!
Cheers:good:
I don't know if there is any huge change from previous recovey...but i feel as a user that is full wipe make this time critical (not ver much). in browsing zip for flashing it always go to root menu...where previous recovery stay on that page where i left. and the lockscreen very much anoying to me....
thanks
is it possible to add scroll by volume keys??
aaurnab said:
is it possible to add scroll by volume keys??
Click to expand...
Click to collapse
Ask in the thread for TWRP. I just package a flashable zip so I can't answer your question.
atrix4g18 said:
Since the other thread hasn't been updated and I posted the last build to it I decided to make a thread here.
CHANGELOG for 2.5.0.0:
DOWNLOAD: TWRP-2.5.0.0-olympus.
Click to expand...
Click to collapse
Do you know if I can have the new one for Atrix ? Thank you very much.
http://forum.xda-developers.com/showthread.php?t=2231049
RECOVERY] TWRP 2.6.0.0 touch recovery [2013-07-11]
sintoo said:
Do you know if I can have the new one for Atrix ? Thank you very much.
http://forum.xda-developers.com/showthread.php?t=2231049
RECOVERY] TWRP 2.6.0.0 touch recovery [2013-07-11]
Click to expand...
Click to collapse
Yes you could.
If you want to be safe with the next TWRP update, you should use goomanager.
Tested: 2.6.0.0 and installed with gooManager:
openrecovery-twrp-2.6.0.0-olympus.img /devs/OpenRecovery/olympus 1cde61c469fe949d2f113ba2047a8546
http://goo.im/devs/OpenRecovery/olympus/
NOTE: inside goomanager (market), click: Flash Rom. Select "I don't have one. Install for me a recovery". Confirm (OK): openrecovery-twrp-2.6.0.0-olympus
sintoo said:
Do you know if I can have the new one for Atrix ? Thank you very much.
http://forum.xda-developers.com/showthread.php?t=2231049
RECOVERY] TWRP 2.6.0.0 touch recovery [2013-07-11]
Click to expand...
Click to collapse
Sorry this is late. OP updated.
DOWNLOAD: TWRP-2.6.0.0-olympus.
Related
ClockworkMod Recovery 3.2.0.0
Note:
Amend scripting (update-script) is no longer supported, was deprecated by Google in Android 1.5. Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Current version: 3.2.0.0-(01.06)
Recovery_Optimus_2x_3.2.0.0-(01.06).zip
MD5: 1e97b2c8a0d4b84e11ec2f31e51f83ca
SHA-1: 2f7cd8cdf8e239886e31497dcffc9e5026606155
Installation:
Unzip the archive
Plug-in the USB cable and select enable the "debug mode"
Double click on install-recovery-windows.bat if you're using windows, execute install-recovery-linux.sh if you're on linux or install-recovery-mac.sh if MacOSX.
Done!
If you want to thank me, click the Thanks button.
Old versions:
Recovery_Optimus_2x_3.2.0.0.zip
Changelog: http://goo.gl/MAuLi (2011-05-30)
Sources available here: https://github.com/CyanogenMod/android_bootable_recovery
All credits to koush for this recovery, I only compiled them!
All Ok with this version!! no /cache umount
Perfect ....
As always one step ahead....
When entering Recovery menu, device vibrates all time long. =/
Good to see you here. Gonna try tomorrow!
Sent from my LG-P990 using XDA App
Just installed. This version is perfect. Thanks.
how come i cant find it in rom manager?
Sorry for a noob question, but with previus version I cannot install CM7 #31.
Can I install this rom now?
ranrick said:
When entering Recovery menu, device vibrates all time long. =/
Click to expand...
Click to collapse
good to know i'm not alone. happens on my CWR that RomManger loads too (3.0.2.8?)!
initrd said:
good to know i'm not alone. happens on my CWR that RomManger loads too (3.0.2.8?)!
Click to expand...
Click to collapse
Yeah, 3.0.2.8 didnt work either. Only 3.0.1.4 works without vibrations.
Works like a charm.
Anyway to add this aswell: http://forum.xda-developers.com/showthread.php?t=1098745
So you have 2 option.
Internal Sd and External Sd?
That would be awesome!
USB mount doesn't work. Is it me?
Recovery shows 3.2.0.0 but the app still reports it as 3.0.2.8 - is this for compatibility?
recovery works fine, thank you, but i noticed a tiny bug:
date of backup is wrong, it shows me 27.04.2011 instead of 27.05.2011
(Time & date settings on phone are correct of course ...)
75markus said:
recovery works fine, thank you, but i noticed a tiny bug:
date of backup is wrong, it shows me 27.04.2011 instead of 27.05.2011
(Time & date settings on phone are correct of course ...)
Click to expand...
Click to collapse
yep. same thing (like at 3.1.0.1)...
just made a nandroid restore and recovery can't mount /boot during restore.
It's probably why we can't ( for exemple ) flash a CM rom ( after nandroid stock rom ) play with it and if you want to return to stock rom using your backup you get a bootloop
Quite common (and annoying), that. Happens each time I've restored a CM NANDroid, have to restore, then reflash CM.
hi. just a noob question
can i use this recovery to flash all the roms for the optimus 2x. like modaco, cm7 and other modaco based custom roms. ?
i been reading the forums and there are so many recoveries. im kinda confused.
Yes you can.
There are only 2 types of recovery in reality, this type (external SD) and the one I built for internal SD use. If you're not sure what you need, pick the external one (unless you don't have an SD card).
bit of a noob..but cant seem to be able to install it. can someone give me a guide to install this with a mac thanks in advance
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Wildfire. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications. Can be installed with unrEVOked. Installs and works well according to users in this thread. Off-mode charging works according to t0mas_.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-buzz.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-buzz.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
Flash like a normal ROM ?
Use it with unrevoked then custom recovery in the menu and use the image file in the zip
If you're testing it, let me know if it works.
Sent from my Nexus S using Tapatalk
does this include off mode charging fix?
http://forum.xda-developers.com/showthread.php?t=1014498
Well my phone was installed and works well ...
t0mas_ said:
does this include off mode charging fix?
http://forum.xda-developers.com/showthread.php?t=1014498
Click to expand...
Click to collapse
No idea. It depends on the CM7 3.2.0.0 recovery source code. I didn't change anything, and I'm quite sure j_r0dd didn't touch this.
cse.10100 said:
Well my phone was installed and works well ...
Click to expand...
Click to collapse
Great! Updating the OP.
thanks, i'll try this out when i find time
one silly question. I use as recovery clockwork 2.xxxx version for a long time now since I first rooted my device with Unrevoked tool. If I flash this new recovery or any other recovery with unrevoked will it create another superuser option that will conflict with the one that was created from the first root?
aggourodolmas said:
one silly question. I use as recovery clockwork 2.xxxx version for a long time now since I first rooted my device with Unrevoked tool. If I flash this new recovery or any other recovery with unrevoked will it create another superuser option that will conflict with the one that was created from the first root?
Click to expand...
Click to collapse
Well, the recovery image itself doesn't touch superuser, but unrevoked will. I belive that you might be downgrading the superuser binary, but (at least for CM7) a reflash with the same zip without wiping anything should restore the superuser binary that was included in your ROM. It should work on other ROMs as well, as long as they're not wiping /data or /sd-ext while flashing for some reason. Make a nandroid backup before you consider flashing this recovery, that's my advice.
Can anyone confirm if this supports off mode charging?
s0ulbl5d3 said:
Can anyone confirm if this supports off mode charging?
Click to expand...
Click to collapse
Not sure where to look, but maybe one can search for this in some type of changelog for the official cwm repository.
s0ulbl5d3 said:
Can anyone confirm if this supports off mode charging?
Click to expand...
Click to collapse
works for me
How can i update this clockwork image,i cant see the image in clockworkmod,i just can see zip files.
rseke said:
How can i update this clockwork image,i cant see the image in clockworkmod,i just can see zip files.
Click to expand...
Click to collapse
You need to use unrevoked to flash the .img file.
ok but how,what i must to do ?
i cant find step by step manual fot clockworkmod update from img file.
rseke said:
ok but how,what i must to do ?
i cant find step by step manual fot clockworkmod update from img file.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=12548919&postcount=26
Unrevoked 3.14 can be found in the same thread on the first page.
Thanx for fast reply and for help.
I have one problem now,mu super user app not working how can i fix that,i cant enter to superuser app to update su binary,force close.
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, version compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the LG Optimus 2X. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for most of the modifications.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-p990.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-p990.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
Now that Koush added backup support for internal/external sdcard I'll only build onw version (exernal sdcard in file lists) If you really want one build for internal sdcard, let me know and I'll do it.)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
As of this version, I'll only be providing one img file. It seems 5.0 has native support for internal/external SD card. Need confirmation of this, as I don't have this phone myself.
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Reverted back to ext3 for the meantime, since I didn't get ext4 working. Any suggestions are welcome!
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Two versions. One for internal storage and one for external microSD card (same zip file)
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
This recovery bricked my phone
Hell_97 said:
This recovery bricked my phone
Click to expand...
Click to collapse
Anybody with same problem?
Hell_97 said:
This recovery bricked my phone
Click to expand...
Click to collapse
How did you install it? Can you still boot into whatever ROM you were running before? What happens when you start to phone now? Exactly what did you do? Please be a bit more specific so we might have a chance of helping you fix the problem.
Sent from my Nexus S using Tapatalk
Updated recovery.fstab to allow ext4. Might work better. Try at your own risk.
zyonee said:
How did you install it? Can you still boot into whatever ROM you were running before? What happens when you start to phone now? Exactly what did you do? Please be a bit more specific so we might have a chance of helping you fix the problem.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I tried to change kernel and the device is locked on the LG screen, I solved with smartflash.
that's not even related to this recovery mod.... I had the same problem with "original" 4.0.0.5 and after flashing vorkernel had the same problem.... I solved it with restoring nandroid backup. The kernel does not work for me with CM latest nightlies.
So can someone please test the newest recovery version? I'd like to know if ext4 works as it should.
Sent from my Nexus S using Tapatalk
klubipiff said:
that's not even related to this recovery mod.... I had the same problem with "original" 4.0.0.5 and after flashing vorkernel had the same problem.... I solved it with restoring nandroid backup. The kernel does not work for me with CM latest nightlies.
Click to expand...
Click to collapse
I installed vork kernel with "original" 4.0.0.5 on CM53 without problem.
To have ext4 you also need a kernel with ext4 support (correct me if im wrong) So which kernel has the ext4 support?
Sent from my Optimus 2X using XDA App
peewster said:
To have ext4 you also need a kernel with ext4 support (correct me if im wrong) So which kernel has the ext4 support?
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
Please stay on topic. This thread is about the modified ClockworkMod recovery and possibly its ability to work with ext4, not about custom ROMs or kernels...
Sent from my Nexus S using Tapatalk
If you've changed recovery.fstab, then it should be OK with EXT4, that's all I had to do with my releases to get it working.
zyonee said:
Please stay on topic. This thread is about the modified ClockworkMod recovery and possibly its ability to work with ext4, not about custom ROMs or kernels...
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Just asking because it looks nice but then i need to know wich kernels i can use?
Sent from my Optimus 2X using XDA App
Just flashed the recovery, all ok. The confirmation menu is much better now with just 1: no line
Sent from my Optimus 2X using XDA App
peewster said:
Just flashed the recovery, all ok. The confirmation menu is much better now with just 1: no line
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
Very glad to hear it. Wipe, nandroid backup/restore and ext4, did you test all these?
Sent from my Nexus S using Tapatalk
peewster said:
Just asking because it looks nice but then i need to know wich kernels i can use?
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
Well, see, the problem isn't really which zips you can or cannot flash. It's more about whether you can flash at all or if ext4 works properly. If nandroid backup and restore works or not. I'm fairly certain that all kernels can be flashed, but how well they work is something that I don't see would be affected by this recovery.
Sent from my Nexus S using Tapatalk
Hmm doesnt seem to wipe correctly...after doing a clean install of CM7 I still have all my old apps and settings. That said I did install it in an odd way (replaced Paul's recovery with it and ran his .bat script). What is the easiest method to flash recovery?
That is the easiest way.
xAdaM-- said:
Hmm doesnt seem to wipe correctly...after doing a clean install of CM7 I still have all my old apps and settings. That said I did install it in an odd way (replaced Paul's recovery with it and ran his .bat script). What is the easiest method to flash recovery?
Click to expand...
Click to collapse
Exactly how did you wipe? Did you use the "format" commands in "mounts and storage" or did you use "clear data/factory reset"? I'm starting to think that the format command is not working.
zyonee said:
Exactly how did you wipe? Did you use the "format" commands in "mounts and storage" or did you use "clear data/factory reset"? I'm starting to think that the format command is not working.
Click to expand...
Click to collapse
Didn't go near the format command in mount and storage. In the specific "Wipe" menu --> tried factory reset etc/cache partition...all seemed to work way to quickly to actually be doing anything. Like I'd select wipe data/factory reset, hit yes and it would say completed after like 1 second (usually takes more than 5 with regular recovery). And then of course when I rebooted my device my data was still there, nothing wiped (except perhaps dalvik, but who knows).
CyanoGen Mod 10.1 LG Optimus 4x HD
21.05.2013 CyanogenMod 10.1 Official Nightly
cm-10.1-20130521-NIGHTLY-p880.zip (163.4 MB)
https://mega.co.nz/#!GV9hVJxY!aY3rIic4cKCc_IeNp47LtXkFPhQBX4ufsHY0t67-Tmk
___________________________________________________________________________________________________________________________________
GAPPS
BUILD - 01.03.2013
GAPPS Jelly Bean 4.2.2 20130301.zip (91.0 MB)
https://mega.co.nz/#!LhAlSLxK!dFZfhUQSclmpiS4Rwf5banSIDt5OMGgzzjoCEIcqsh8
___________________________________________________________________________________________________________________________________
USE KERNEL WerewolfJB Kernel v005 to get best out of your phone
I dont post a link because its not my kernel but you will find it in Android Development
How to Enable USB Debugging and Developer Options on CM10.1
Go to – Settings > About phone.
Then move on to Build number option
Tap on Build number repeatedly about 7 times.
This is enough.
After touching 7th time you will see a message that, “you are now a developer”.
___________________________________________________________________________________________________________________________________
how did you fix the problem?
nbock97 said:
how did you fix the problem?
Click to expand...
Click to collapse
yeah how DID you fixed it
Sent from my LG-P880 using xda app-developers app
he changed the update script. the official cm flashable zip checks for the codename "p880". since its not the correct codename for our phone ("x3" is correct) and all our recoveries use that codename "x3" its not flashable. what he did is changing "p880" to "x3" in the update script (in the first line) or he completely removed that check
Wasn't easier to just use the official CWM from the CM team? Unless you use twrp ofcourse
Sent from my LG-P880 using Tapatalk 2
gordon0001 said:
he changed the update script. the official cm flashable zip checks for the codename "p880". since its not the correct codename for our phone ("x3" is correct) and all our recoveries use that codename "x3" its not flashable. what he did is changing "p880" to "x3" in the update script (in the first line) or he completely removed that check
Click to expand...
Click to collapse
NO dude i Removed the Line , and not changed it to x3 , because some recoverys find it as p880 and other as x3 , so now if you remove it it works all time on every recovery
Anyway did someone test Works ?
On my Phone Works :laugh:
what recovery did you use..?? And Is this the newest cm??
New updates will come every day, so I think people should beter flash newest cwm.
No ill update right now with the latest its like 1 hour old Update
i use CWM 6.0.2.8 from Dexter
Please help
i've tried to flash CM and followed instructions in this order:
1. Place cm-10.1-20130416-NIGHTLY-p880.zip and gapps-jb-20130301-signed.zip in to your internal sdcard
2. BACKUP ALL YOUR DATA with CWM Recovery
3. In CWM Recovery make wipe data/factory reset, wipe cache partition, wipe dalvik cache, format system
4. Flashcm-10.1-20130416-NIGHTLY-p880.zip from sdcard
But i've got an error status 7 . Now my phone wont boot, and i can't copy this fixed zip file. What can i do?
batinjo said:
i've tried to flash CM and followed instructions in this order:
1. Place cm-10.1-20130416-NIGHTLY-p880.zip and gapps-jb-20130301-signed.zip in to your internal sdcard
2. BACKUP ALL YOUR DATA with CWM Recovery
3. In CWM Recovery make wipe data/factory reset, wipe cache partition, wipe dalvik cache, format system
4. Flashcm-10.1-20130416-NIGHTLY-p880.zip from sdcard
But i've got an error status 7 . Now my phone wont boot, and i can't copy this fixed zip file. What can i do?
Click to expand...
Click to collapse
Restore the backup you made in step 2, install newest official CWM via ROM Manager (download it from play store if you don't already have it) then boot back into CWM and install CM again.
---------- Post added at 08:38 PM ---------- Previous post was at 08:37 PM ----------
Also I honestly don't see any real benefit to this thread when installing official CWM solves the status 7 issue and allows for OTA updating of CM instead of having to wait for the OP of this thread to upload a fix every single day...
argh
AlderCass said:
Restore the backup you made in step 2, install newest official CWM via ROM Manager (download it from play store if you don't already have it) then boot back into CWM and install CM again.
---------- Post added at 08:38 PM ---------- Previous post was at 08:37 PM ----------
Also I honestly don't see any real benefit to this thread when installing official CWM solves the status 7 issue and allows for OTA updating of CM instead of having to wait for the OP of this thread to upload a fix every single day...
Click to expand...
Click to collapse
tnx so much for your answer, but what if i don't made backup in step 2?
Any chance to do anything by some command line or something?
batinjo said:
tnx so much for your answer, but what if i don't made backup in step 2?
Click to expand...
Click to collapse
I was afraid you were gonna say that! You can still boot into CWM though right? If you can, and your computer has an SD slot, just take out your external SD card and put it into an adapter and put the fixed version from this thread on that, then you can just install it from the external SD in CWM.
batinjo said:
tnx so much for your answer, but what if i don't made backup in step 2?
Any chance to do anything by some command line or something?
Click to expand...
Click to collapse
from CWM you can install via sideload ...
or harder way- reflash stock, root it, download rom manager, install newest cwm via it, copy files, flash in recovery
won't work
AlderCass said:
I was afraid you were gonna say that! You can still boot into CWM though right? If you can, and your computer has an SD slot, just take out your external SD card and put it into an adapter and put the fixed version from this thread on that, then you can just install it from the external SD in CWM.
Click to expand...
Click to collapse
can't mount /external_sd
When i connect phone to computer, driver is missing, it is named lgp880. I've installed all the drivers that came on my mind, and nothing.
So i'm not sure how to use the sideload command...
NIGHTMARE!!!
Bugs? And best feature?
bugs :
no mass storage mode
and some little things
best feature: Its cyanogenmod - says everything there are so much nice functions! e.g. skipping track with volume rocker, close apps with long prrss back, theme support , .... Go ahead and try it
Sent from my LG-P880 using xda app-developers app
batinjo said:
i've tried to flash CM and followed instructions in this order:
1. Place cm-10.1-20130416-NIGHTLY-p880.zip and gapps-jb-20130301-signed.zip in to your internal sdcard
2. BACKUP ALL YOUR DATA with CWM Recovery
3. In CWM Recovery make wipe data/factory reset, wipe cache partition, wipe dalvik cache, format system
4. Flashcm-10.1-20130416-NIGHTLY-p880.zip from sdcard
But i've got an error status 7 . Now my phone wont boot, and i can't copy this fixed zip file. What can i do?
Click to expand...
Click to collapse
Download the new Update and use CWM 6.0.2.8 Try that
x0BlackTeresis0x said:
Download the new Update and use CWM 6.0.2.8 Try that
Click to expand...
Click to collapse
NOT 6.0.2.8 CWM 6.0.3.1 is compatible with cm10
Sent from my LG-P880 using xda app-developers app
Sorry didnt saw that there is a newer version for clockworkmod
right use that 6.0.3.1
Hi,
I managed to build latest TWRP for N5100/N5110.
This a test build you can flash from your existing recovery.
Odin packages and flashable ZIPs are now available for n5100 and N5110.
Download:
http://www.androidfilehost.com/?w=files&flid=15631
What's new since 2.6.3.0?
What's new in 2.7.1.0:
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
Various bugfixes to backup and restore
Improvements to USB storage handling
Added a class to search for files to make finding the correct brightness file automatic in most cases
Various other bugfixes and tweaks
NOTE: This is a test version and does NOT support f2fs, but you can switch to other filesystems
What's new in 2.7.0.0:
Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
Allow sideloading from /tmp on encrypted devices
Check for a crypto footer before asking for a password to prevent user confusion
Additional checks for validity to auto generated backup names
Text wrap in the console output
Proper caps lock support in the keyboard
Mouse support via USB OTG for devices with a broken digitizer
Improve scanning of storage locations for OpenRecoveryScript
Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions
Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
Update SuperSU to 1.93 and improve installation process
Added selinux contexts restoration to fix permissions
Load RTC offset on Qualcomm devices to fix the date/time in recovery
USB Mass Storage fixes Add SELinux support checking
Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
Add 4.4 AOSP decrypt support
Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
Various SELinux fixes and bug fixes
Changelog:
Build 1:
-First release
Credits:
@sbrissen for original port and maintenance of CM11 for n5100/n5110/n5120.
@Dees_Troy & TEAMWIN for making TWRP
Reserved
i'm waiting for n5110
Is there any chance for a 5120 version, if you don't mind me asking.
Sent from my GT-N5120 using Tapatalk
Thx for your effort. Great to have a updated Recovery. Can this used for all kind of Roms? 4.1.2, 4.2.2 and 4.4.x?
Thank you for planning on including the 5110. I will patiently waiting for the addition of this device.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Build 2 is released.
Now n5100 and n5110 is supported. You can get tar files to flash via Odin or use zip files if you want to flash from your existing recovery (CWM, PhilZ or older versions of TWRP)
User_99 said:
Thx for your effort. Great to have a updated Recovery. Can this used for all kind of Roms? 4.1.2, 4.2.2 and 4.4.x?
Click to expand...
Click to collapse
I only tested with 4.4.x. But it should work with older ROMs too.
Fobz said:
Is there any chance for a 5120 version, if you don't mind me asking.
Sent from my GT-N5120 using Tapatalk
Click to expand...
Click to collapse
For now, I can't provide 5120 support.
whitemolecule said:
I only tested with 4.4.x. But it should work with older ROMs too.
For now, I can't provide 5120 support.
Click to expand...
Click to collapse
No problems!
Sent from my Nexus 4 using Tapatalk
Thanks much for flashable zips.
Works great. I've been waiting a long time for this release. Thank you. You rule.
Sent from my GT-N5110 using XDA Premium HD app
whitemolecule said:
Build 2 is released.
Now n5100 and n5110 is supported. You can get tar files to flash via Odin or use zip files if you want to flash from your existing recovery (CWM, PhilZ or older versions of TWRP)
Click to expand...
Click to collapse
Hello Sir thanks for your great work updating TWRP I been using Philz CWM recovery with no problems im thinking of trying yours which is better Philz CWM or TWRP hate to change since Philz is working let me know thanks
matthewtech770 said:
Hello Sir thanks for your great work updating TWRP I been using Philz CWM recovery with no problems im thinking of trying yours which is better Philz CWM or TWRP hate to change since Philz is working let me know thanks
Click to expand...
Click to collapse
The "better" is the one you choose.
Wow again. Quickly, I want to say, it's nice to get back to TWRP. Been using Philzs and it does a good job but not as smooth and easy as TWRP. The only rom I can't use this with is CivZ's new 4.4.2. It won't allow me to hit the "next" button when installing the rom. All other roms work perfect. This is donation good. Thank you again.
Sent from my GT-N5110 using XDA Premium HD app
Thanks for this. Seems It has problems with Aroma installers. The screen orientation specifically. The screen stays in landscape and only allows the top half of the screen to show the aroma installation, while the touch sensitivity is still in portrait. In other words you have to touch the screen as if it were in portrait and kind of guess where the buttons would be while the actual pictures on the screen are in landscape on only the top half of the screen and very stretched looking. Thanks again for your work.
kstephens98 said:
Thanks for this. Seems It has problems with Aroma installers. The screen orientation specifically. The screen stays in landscape and only allows the top half of the screen to show the aroma installation, while the touch sensitivity is still in portrait. In other words you have to touch the screen as if it were in portrait and kind of guess where the buttons would be while the actual pictures on the screen are in landscape on only the top half of the screen and very stretched looking. Thanks again for your work.
Click to expand...
Click to collapse
And that's why developers that use Aroma (like @civato) specify using Philz's Touch Recovery, which is a modified CWM, to flash their ROM's and kernels.
ramjet73
Nice observation. That is what I figured as well.. I usually have a flashable version of TWRP and Philz touch at the ready. I do a lot of testing with my tablet, with different roms and how apps work and can be modified with each.
Sent from my GT-N5110 using XDA Premium HD app
glockman4519 said:
Nice observation. That is what I figured as well.. I usually have a flashable version of TWRP and Philz touch at the ready. I do a lot of testing with my tablet, with different roms and how apps work and can be modified with each.
Click to expand...
Click to collapse
Yea, I do the same thing.
The easiest way I've found to switch recoveries is to keep "recovery.img" versions of each one on the SD card, then move the files you want to flash to the SD card, use Flashify to install the recovery needed if it's not already there, then reboot into recovery with the advanced power menu. It's still a good idea to keep the .zip version of each recovery on the SD card in case you're already in recovery before you discover that you have the wrong version installed. It would be nice to have USB OTG mount available in this version of TWRP recovery since I can't seem to get USB storage working as there appears to be some conflict with ADB.
I tend to do all my backups with TWRP though since it supports compression and restores have been more reliable for me than using CWM. The backup formats are different so it doesn't make sense to use both.
If the Samsung devices supported "fastboot boot recovery.img" like Nexus, HTC and most other brands it wouldn't be necessary to actually flash an alternate recovery since it could just be booted as needed when the tablet is connected to a computer.
Edit: I just discovered that the "fixed" 2.6.3.0 version of TWRP from this post works fine with Aroma. It doesn't have the USB storage option in mounts (explained in this post) but I can't get that to work with this 2.7.1.0 version anyway. I'd love to use this updated version of TWRP but it would be nice if the Aroma support could be included from the 2.6.3.0 version and an OTG mount option (as opposed to USB storage) could be added.
ramjet73
I was wondering if there would be a possibility of getting this recovery in portrait mode. I am wanting to use a Holofied theme that has more options that can utilize TWRP even better but it does not work with landscape layout. I have already tried to take the Grouper TWRP and used its res folder and added that to the n5110 twrp and repacked the recovery.img and flashed but recovery is still in landscape but is displaying a portrait layout which is unusable.
pimpmaneaton said:
I was wondering if there would be a possibility of getting this recovery in portrait mode. I am wanting to use a Holofied theme that has more options that can utilize TWRP even better but it does not work with landscape layout. I have already tried to take the Grouper TWRP and used its res folder and added that to the n5110 twrp and repacked the recovery.img and flashed but recovery is still in landscape but is displaying a portrait layout which is unusable.
Click to expand...
Click to collapse
Yes, I will try to build in portrait mode when I have time, I think this will also fix aroma installer issues too.