Database Users

Nexus S i9020a + CM7

Can someone please direct me to the a step by step guide on how to Root and put CM7 on the Nexus S i9020a variant? Most of the stickies are for the T-mobile version and Its getting to be a bit confusing on which guide to follow. Please help this noobie!!!

use gingerbreak then rom manager it's that simple
http://forum.xda-developers.com/showthread.php?t=1044765

Quick note once you install CM7 do not use the 2g/3g feature it will break your 3g

Break 3g? as in damage it permanently? Thanks for the link for gingerbreak so basically that will root my nexus s then I can install CM 7 with out any special instructions since it has different radio compared to the tmobile version?

i used gingerbreak then rom manager to install clockwork recovery and CM7. Do some reading the 3g bug for I9020A has been discussed a few times. Just stay away from the 2g/3g toggle and everything will be fine. I don't think it permanently breaks it just is a pain in the A to fix. I have a I9020A and this was the simplest way I've found.

don't we have to flash a clockwork compatible kernel first, before flashing cm7?
Also, doesn't clockwork rom manager fail on sns? I have cwr from the main stickies, but rom manager doesn't see it (it works), and can't download roms, unless cwr from rom manager, which I heard fails.
Sent from my Nexus S using XDA App
So I downloaded CM7 7.0.2 - and gapps - flashed in order (nandroid first) and voila! no hastle! This ROM is great!

No, those are the only steps i took

CM7 comes with its own AOSP kernel. Just flash the rom, you'll get the kernel bundled. (Of course you can always use a great kernel from the developers thread) don't forget to flash gapps.
Sent from my Nexus S using XDA Premium App

jruweaver said:
Quick note once you install CM7 do not use the 2g/3g feature it will break your 3g
Click to expand...
Click to collapse
He means don't use the 2g/3g toggle widget as that will cause some problems, it hasn't been fixed yet. If you do want to change it though, do it manually through the settings.
Sent from my Nexus S using XDA App

I tried using gingerbreak on my i9020a but it runs for longer than 15 mins so I guess it doesn't work. What are my other options for rooting?
edit: I guess it's because I installed 2.3.6.. is it possible to downgrade easily?

drleospaceman said:
I tried using gingerbreak on my i9020a but it runs for longer than 15 mins so I guess it doesn't work. What are my other options for rooting?
edit: I guess it's because I installed 2.3.6.. is it possible to downgrade?
Click to expand...
Click to collapse
Follow one of the root guides, all you really need to do is unlock the bootloader and install Clockwork Recovery.
Once that is done, download the zip for cm7 and use CWM to flash it.

Matridom said:
Follow one of the root guides, all you really need to do is unlock the bootloader and install Clockwork Recovery.
Once that is done, download the zip for cm7 and use CWM to flash it.
Click to expand...
Click to collapse
Thanks

Matridom said:
Follow one of the root guides, all you really need to do is unlock the bootloader and install Clockwork Recovery.
Once that is done, download the zip for cm7 and use CWM to flash it.
Click to expand...
Click to collapse
Exactly the steps I took. Took all of 10 minutes
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
fastboot reboot recovery
Install .zip from SD
Select CM7
reboot system

Mr Kyle said:
Exactly the steps I took. Took all of 10 minutes
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
fastboot reboot recovery
Install .zip from SD
Select CM7
reboot system
Click to expand...
Click to collapse
Agreed, but it's a matter of getting the correct CWM image for our phones. Also, for people who are setting up their phones for the first time, the drivers needed for fastboot need to be installed, fastboot/SDK needs to be downloaded etc...
Hence why i referenced the rooting guides.

Mr Kyle said:
Exactly the steps I took. Took all of 10 minutes
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
fastboot reboot recovery
Install .zip from SD
Select CM7
reboot system
Click to expand...
Click to collapse
Which recovery img file should I use from here?
http://forum.xda-developers.com/showthread.php?t=988686&highlight=i9020a
Thanks
edit: nevermind, I guess the color names are just cosmetic?

drleospaceman said:
Which recovery img file should I use from here?
http://forum.xda-developers.com/showthread.php?t=988686&highlight=i9020a
Thanks
edit: nevermind, I guess the color names are just cosmetic?
Click to expand...
Click to collapse
Yep, it's just the color you want your recovery to be. I flashed the cyan a couple of days ago for somebody else and no issues.. typical clockwork recovery

So I flashed the recovery file, but when I boot into recovery now, there's just the triangle with the ! in it and nothing happens.. did I do something wrong?
edit: reflashed it and it works

drleospaceman said:
So I flashed the recovery file, but when I boot into recovery now, there's just the triangle with the ! in it and nothing happens.. did I do something wrong?
Click to expand...
Click to collapse
How did you flash it? That's the stock recovery.. should be 'fastboot flash recovery nameof.img' without quotes obviously.

drleospaceman said:
So I flashed the recovery file, but when I boot into recovery now, there's just the triangle with the ! in it and nothing happens.. did I do something wrong?
edit: reflashed it and it works
Click to expand...
Click to collapse
somebody after reboot no CWR on recovery use this solved your problem
clockworkmodrecovery rom manager find and install
open it and touch flash clockworkmod recovery(first item)
select reboot into recovery manual
mount and storage select
mount USB storage
unmount
++++ go back +++++
install from zip sdcard
find
'' super user.zip'' flash
reboot
find and isntall ''es file explorer'' select setting mark root explorer and mount file system after
select phone in file explorer find ''etc'' folder select and find ''install-recovery.sh'' file and rename file for example ''install-recovery.sheski'' and
open rom manager again touch flash clockworkmod recovery(first item)
check it...
please click thanks button

[Q] Booting into recovery shows "no command"

Hi there,
yesterday succesfully rooted my device using the insecure boot image.
Today booted and also flashed the new CWM recovery image but now, when booting into recovery only get an android logo and the text "no command" ?
Any ideas ? Flashed back to original recovery image but no change either ?
Root remains though and working fine.
Thanks

CMW can't be flashed yet... read the official CMW thread in the N4 Original Development forum for help
Sent from my Nexus 7 using xda app-developers app

n7of9 said:
CMW can't be flashed yet... read the official CMW thread in the N4 Original Development forum for help
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Not true read here again :
UPDATE: There is an official ClockworkMod recovery for Nexus 4 now available directly by Koush, so this should all be easy as pie now and you can now safely install CWM too. I am updating the CWM method with the updated instructions.
Click to expand...
Click to collapse

has anyone reported it working?
Sent from my Nexus 7 using xda app-developers app

It seems tonight clockwork will release a new version with bugfixes which should make recovery working when flashed also.
Sent from my Nexus 4 using xda app-developers app

New clockworkmod recovery 6.0.1.8 had been released and I can confirm myself that it is working perfectly and stays when flashed !
You can download it here and follow the instructions as written here.
Good luck !

excellent, i was waiting for someone to confirm before flashing it myself
(looks like this thread is just a party for the two of us, wooohooo, let's find the hidden alcohol)

n7of9 said:
excellent, i was waiting for someone to confirm before flashing it myself
(looks like this thread is just a party for the two of us, wooohooo, let's find the hidden alcohol)
Click to expand...
Click to collapse
Meanwhile a newer 6.0.1.9 is released as well, which will hopefully also fix the backup being in the wrong location and not usable

CWM is fixed. Read this thread: http://forum.xda-developers.com/showthread.php?t=1995440

6.0.1.9 is the one i flashed and I'm still looking for my backup :s
n7'd from my n7

Disregard this post! It was meant for LBE which is a Virus or acts like one (Newest version that was translated)

I'm having the "no command" message as well. I've flashed CWM 6.0.2.3 no-touch (following this guide), and it doesn't seem to be sticking. It'll work the first time, but then revert to the "no command" screen. I've also tried flashing the stock recovery, and then I receive the same message. I have an unlocked bootloader, and I managed root via the same guide. Anybody have any ideas?

k3nav7 said:
I'm having the "no command" message as well. I've flashed CWM 6.0.2.3 no-touch (following this guide), and it doesn't seem to be sticking. It'll work the first time, but then revert to the "no command" screen. I've also tried flashing the stock recovery, and then I receive the same message. I have an unlocked bootloader, and I managed root via the same guide. Anybody have any ideas?
Click to expand...
Click to collapse
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 7 using Tapatalk HD

El Daddy said:
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Perfect! Thank you! I had just previously downloaded 4.2.1, and so renaming recovery-from-boot.p did the trick. I had to remount my /system as read/write (used Total Commander, and it worked like a charm.

k3nav7 said:
Perfect! Thank you! I had just previously downloaded 4.2.1, and so renaming recovery-from-boot.p did the trick. I had to remount my /system as read/write (used Total Commander, and it worked like a charm.
Click to expand...
Click to collapse
No problem! Glad to help!
Sent from my Nexus 7 using Tapatalk HD

No Command recovery problem
Hello im using a Canvas Magnus A117 its an amazing phone i rooted it but wanted to install chainfire 3D on it but it didnt work and now my phone is bricked. I tried flashing a custom rom but in recovery when i click on apply update from sdcard it says No command. with a dead android and a red triangle with !. So i cant use any feature in the Recovery mode and my phone is bricked. What do i do?

Stock Recovery will not Flash

Hey guys I could really use some help...I have twrp recovery but unfortuunately when i try to flash stock recoveryy back, it will not change. I have tried fastboot, nexus toolkit by wug, flashify, image flash gui, etc. Do you guys have any suggestions? Thanks so much!

Are you still unlocked or did you relock?

sfhub said:
Are you still unlocked or did you relock?
Click to expand...
Click to collapse
I am still unlocked

I don't think twrp recovery has the option to restore recovery (or I might have missed it last time I looked)
Are you doing
fastboot flash recovery stock-recovery.img

sfhub said:
I don't think twrp recovery has the option to restore recovery (or I might have missed it last time I looked)
Are you doing
fastboot flash recovery stock-recovery.img
Click to expand...
Click to collapse
Yea i did that put recovery.img in platform tools folder and executed the command....its almost like the recovery is flashed permanently...cant even flash cwm

Did you enable usb debugging in developer options before trying to flash recovery?

geckocavemen said:
Did you enable usb debugging in developer options before trying to flash recovery?
Click to expand...
Click to collapse
yes i did that...have you guys tried it? maybe its just a problem for everyone idk

slamdunksaliby said:
yes i did that...have you guys tried it? maybe its just a problem for everyone idk
Click to expand...
Click to collapse
Ive tried to reflash the stock recovery image and ended up with the same problems, anyone able to reflash the stock recovery after flashing twrp?

chuck313 said:
Have tried to reflash the stock recovery image and ended up with the same problems, anyone able to reflash the stock recovery after flashing twrp?
Click to expand...
Click to collapse
I even did a factory reset and still its sticking....i even tried to rename recovery-from-boot.bak back to .p and still nothing
I guess ill just flash cleanrom for now since the recovery is here forever lol

slamdunksaliby said:
I even did a factory reset and still its sticking....i even tried to rename recovery-from-boot.bak back to .p and still nothing
I guess ill just flash cleanrom for now since the recovery is here forever lol
Click to expand...
Click to collapse
I had a similar problem flashing the one that has "for razor" in its name. Found a different one and it worked fine.

TG2708 said:
I had a similar problem flashing the one that has "for razor" in its name. Found a different one and it worked fine.
Click to expand...
Click to collapse
interesting mine was from one of the stickies above...but ive tried multiple recoveries too...did you use fastboot? If you could maybe link the working one that would be much appreciated

slamdunksaliby said:
interesting mine was from one of the stickies above...but ive tried multiple recoveries too...did you use fastboot?
Click to expand...
Click to collapse
Yes i did use fastboot.

TG2708 said:
Yes i did use fastboot.
Click to expand...
Click to collapse
Hmm well if you could link to the working one that would be greatly appreciated I like twrp no doubt but i feel like this recovery may not even be updatable let alone changed if I ever needed to

update: after some testing It looks like the stock recovery file in the sticky above is actually twrp recovery...if someone can upload the real stock recovery file that would be great

slamdunksaliby said:
update: after some testing It looks like the stock recovery file in the sticky above is actually twrp recovery...if someone can upload the real stock recovery file that would be great
Click to expand...
Click to collapse
I've found three recoveries floating around on the forum so far. Two are in this thread -- one is in the first (1st) post under the "recovery" subtitle and the second is in the seventh (7th) post.
The other one is in this post. You have to download the Nexus_7_Restore_F.zip file and unzip it. Once you do that you will find a recovery.img file in it.
Hope one of these works. My bet is the last one will at the very least. Let us know how it turns out for you.

Thank you so much I'll let you know! Ah it looks like the stock kernel is in the last one too that's good..hopefully sometime soon we can get factory images to make things easier haha

geckocavemen said:
I've found three recoveries floating around on the forum so far. Two are in this thread -- one is in the first (1st) post under the "recovery" subtitle and the second is in the seventh (7th) post.
The other one is in this post. You have to download the Nexus_7_Restore_F.zip file and unzip it. Once you do that you will find a recovery.img file in it.
Hope one of these works. My bet is the last one will at the very least. Let us know how it turns out for you.
Click to expand...
Click to collapse
I tried flashing all of the above. With the third one (contained within the Nexus_7_Restore_F.zip), when I reboot to recovery, I get the Android with the red exclamation mark, no go. So I manually flashed TWRP back. It seems that until we get an official factory image from Google (if ever), we're stuck on TWRP. Unless there's something I haven't considered.

minazaki said:
I tried flashing all of the above. With the third one (contained within the Nexus_7_Restore_F.zip), when I reboot to recovery, I get the Android with the red exclamation mark, no go. So I manually flashed TWRP back. It seems that until we get an official factory image from Google (if ever), we're stuck on TWRP. Unless there's something I haven't considered.
Click to expand...
Click to collapse
Unless I'm mistaken the Android with a red exclamation is what you should see if you have the stock recovery installed...which means it was successful. At that point there is some combination of buttons that must be pressed to restore the recovery but I don't remember what it is (I think it might be Vol up + Power but I don't know for certain so I wouldn't try that until someone else confirms it).

minazaki said:
I tried flashing all of the above. With the third one (contained within the Nexus_7_Restore_F.zip), when I reboot to recovery, I get the Android with the red exclamation mark, no go. So I manually flashed TWRP back. It seems that until we get an official factory image from Google (if ever), we're stuck on TWRP. Unless there's something I haven't considered.
Click to expand...
Click to collapse
That is what you are supposed to see.
Please see this post for instructions:
[Info] Guide to entering safe mode, bootloader, stock recovery

geckocavemen said:
Unless I'm mistaken the Android with a red exclamation is what you should see if you have the stock recovery installed...which means it was successful. At that point there is some combination of buttons that must be pressed to restore the recovery but I don't remember what it is (I think it might be Vol up + Power but I don't know for certain so I wouldn't try that until someone else confirms it).
Click to expand...
Click to collapse
sfhub said:
That is what you are supposed to see.
Please see this post for instructions:
Info] Guide to entering safe mode, bootloader, stock recovery
Click to expand...
Click to collapse
Oh right. I actually knew that too. Been so long since I had seen stock recovery.

Verizon 4.4 OTA

I pulled this from my phone and posted it in the other thread, and someone suggested I make a thread for it. Here it is!
http://j2cool.com/mirror/files/Blur_Version.139.15.1.ghost_verizon.Verizon.en.US.zip
To install, you will need to be on the latest OTA (camera update).
Fastboot flash the original system.img and recovery,img
You can then use the volume down key to select "Recovery"
Once in recovery, press the power button and volume buttons together to bring up the menu,and select "Install from SDcard"
You can then select the OTA, and install it. Your phone will reboot, and you will have to do this again from the new recovery. You should then be able to reboot system and have your new 4.4 Kitkat Moto X!
Sent from my XT1060 using Tapatalk

Whoops. Replied while trying to edit. Mobile forum use is a pain.
Sent from my XT1060 using Tapatalk

Chrome says this file is dangerous

km8j said:
Chrome says this file is dangerous
Click to expand...
Click to collapse
Chrome is smart, Chrome knows a Verizon update image is too good to be true :laugh:

What's the install method for VZW Dev Ed?
Flash system.img but not boot.img?

Mercutio5 said:
What's the install method for VZW Dev Ed?
Flash system.img but not boot.img?
Click to expand...
Click to collapse
You don't need boot.img in either. Now, I don't know how the dev ed works, maybe it's just the exact same with an unlocked bootloader, so let me know how installing goes.

km8j said:
Chrome says this file is dangerous
Click to expand...
Click to collapse
Because it's a large zip file from somewhere no one has downloaded before. I promise you, it's safe and clean though.

Mercutio5 said:
What's the install method for VZW Dev Ed?
Flash system.img but not boot.img?
Click to expand...
Click to collapse
Dev edition you can install like any other device. The benefit is that you can flash custom files without recovery flipping its ****.
Sent from my XT1080MDEV.

Will this work on GSM dev edition?

tesselator said:
Will this work on GSM dev edition?
Click to expand...
Click to collapse
Only if you want to break your phone.
This is for Verizon.

Whats the procedure for flashing this on a rooted verizon dev edition

Gs0230 said:
Whats the procedure for flashing this on a rooted verizon dev edition
Click to expand...
Click to collapse
Put the zip in internal storage. Go into stock recovery, install zip, choose this update zip. Because one of the first things it does it flash a new recovery, you have to go into recovery again and install zip again (the second time around it knows it doesn't have to flash the recovery).
Of course, since this way uses stock recovery, you have to be running stock.

I'm on stock just rooted with unlocked bootloader twrp 2.6.3 installed will I lose root
Sent from my XT1060 using XDA Premium 4 mobile app

Gs0230 said:
I'm on stock just rooted with unlocked bootloader twrp 2.6.3 installed will I lose root
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You need to use stock recovery. After the update u can install twrp and root again

Can I keep root and how do i revert to stock recovery

Gs0230 said:
I'm on stock just rooted with unlocked bootloader twrp 2.6.3 installed will I lose root
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, you're going to lose root (the update will wipe out System). If you have an unlocked bootloader then it isn't a big deal -- just re-root after the update.
BUT don't try to flash this update with twrp installed. 1) I'm pretty sure it won't work anyway b/c it needs to verify that your System is stock and, at the very least, installing twrp changes the install-recovery script which is in System 2) this .zip file is made to be flashed from a stock recovery, so I'm not sure it would work 3) as I said before, part of this update is a new recovery - I'm not sure how well the process would go if you started from twrp

And how would I root after its done

Gs0230 said:
And how would I root after its done
Click to expand...
Click to collapse
The same way you rooted before?
I'm sorry, I've been assuming you have a Dev edition b/c you said you had twrp -- is that not the case? If you do NOT have a dev edition and you rooted via pwn- or rock- or whatever its called myMoto then NO, you will NOT be able to root after the update until someone releases another hack

piccit said:
Put the zip in internal storage. Go into stock recovery, install zip, choose this update zip. Because one of the first things it does it flash a new recovery, you have to go into recovery again and install zip again (the second time around it knows it doesn't have to flash the recovery).
Of course, since this way uses stock recovery, you have to be running stock.
Click to expand...
Click to collapse
I got this the second time (with the new recovery):
"Install aborted"
:|
Maybe the battery level is too low, so i'm gonna charge it a little and see what happens
PS: the "normal" OTA is downloading SO slow D: that's why i'm trying the one in this thread
------EDIT----
For some reason the download speed just increased, so i'm staying with it

I cannot flash this in TWRP right?

New TWRP version.

So I just noticed there's a new TWRP build up for us! Just thought I'd throw this out there, not sure what's different.
https://dl.twrp.me/shamu/

the only change is "Bring back /misc"
you should update if you are using cm14.1, cmupdater can cause bootloop with twrp 3.0.2.0 or older

8zabi said:
you should update if you are using cm14.1, cmupdater can cause bootloop with twrp 3.0.2.0 or older
Click to expand...
Click to collapse
I was struggling with this this morning. I was stuck in Recovery but managed to get back into System by doing a Reboot Bootloader, then Start. Then I downloaded the new TWRP and flashed it, all is well now. Would have been easier if I had access to a computer this morning.

psycho_asylum said:
I was struggling with this this morning. I was stuck in Recovery but managed to get back into System by doing a Reboot Bootloader, then Start. Then I downloaded the new TWRP and flashed it, all is well now. Would have been easier if I had access to a computer this morning.
Click to expand...
Click to collapse
Flashify is usually good for that!
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en

Boot into recovery
Select install
Select near the bottom IMG button
Select IMG file
Select type of IMG ( boot, recovery)
Slide to start once finished reboot to recovery and check version
Reboot to O's
Profit
Sent from my Nexus 6 using XDA Labs

Read several posts about bad download. Before flashing check the size of TWRP version 3.0.2.1. The file size is 11,3 Mb.
https://dl.twrp.me/shamu/

tsjanda said:
Boot into recovery
Select install
Select near the bottom IMG button
Select IMG file
Select type of IMG ( boot, recovery)
Slide to start once finished reboot to recovery and check version
Reboot to O's
Profit
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Put phone into bootloader mode. Hold shift and right click to "Open command window here" where you have ADB and your TWRP file (assuming Windows PC). Type "fastboot flash recovery twrp-3.0.2-1-shamu.img". Easier, quicker, and potentially safer IMO.

Dopamin3 said:
..... "fastboot flash recovery twrp-3.0.2-1-shamu.img". Easier, quicker, and potentially safer IMO.
Click to expand...
Click to collapse
That's the most basic method, but with the app FlashFire you don't need a PC.

NLBeev said:
Read several posts about bad download. Before flashing check the size of TWRP version 3.0.2.1. The file size is 11,3 Mb.
https://dl.twrp.me/shamu/
Click to expand...
Click to collapse
Thank you for this. If you are using Tapatalk latest app it opens the link in its own browser and the download is only 6.92k. Opening in chrome beta and downloading gets the whole file downloaded.
Sent from my Pixel XL using Tapatalk

NLBeev said:
That's the most basic method, but with the app FlashFire you don't need a PC.
Click to expand...
Click to collapse
Depending on version you don't even need FlashFire. TWRP can flash the updated image.

Strephon Alkhalikoi said:
Depending on version you don't even need FlashFire. TWRP can flash the updated image.
Click to expand...
Click to collapse
In this case not possible, because the flashed version of TWRP-recovery was corrupt.

NLBeev said:
In this case not possible, because the flashed version of TWRP-recovery was corrupt.
Click to expand...
Click to collapse
I guess I took your post out of context, since your post didn't mention a corrupt download, but earlier posts did.

Strephon Alkhalikoi said:
I guess I took your post out of context, since your post didn't mention a corrupt download, but earlier posts did.
Click to expand...
Click to collapse
That's imaginable, because I had to edit the post.
I have made a mistake; didn't check the file size. After reboot to recovery, I noticed that a corrupt IMG was flashed.
EDIT
Version 3.0.3-0 available see next post.

TWRP-recovery version 3.0.3-0 for Nexus 6 available.
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img.html

3.1.0-0
https://dl.twrp.me/shamu/twrp-3.1.0-0-shamu.img.html
What's new:
https://www.xda-developers.com/twrp...-support-for-adb-backup-ab-ota-zips-and-more/

Installed version 3.1.0-0. With all the changes themes need to be reworked. Also, there are rumblings in the XDA article discussion thread that Aroma does not work on this recovery. I'll have to check that.
EDIT: Aroma working perfectly here, as far as I can tell.

I am just curious. Can backups made on older version of TWRP be restored by this new version? Thanks.

chaibaby said:
I am just curious. Can backups made on older version of TWRP be restored by this new version? Thanks.
Click to expand...
Click to collapse
only one way to know, so try it and report back

wase4711 said:
only one way to know, so try it and report back
Click to expand...
Click to collapse
Will do when I am home later on tonight then report back.

chaibaby said:
I am just curious. Can backups made on older version of TWRP be restored by this new version? Thanks.
Click to expand...
Click to collapse
Usually, yes. I would backup up personal data onto PC before trying.