So I have a Nexus 7 32GB wifi and I unlocked the bootloader and rooted it last night and had CWM touch installed. The problem is, when I boot the tablet back into recovery, it doesn't load CWM, it just displays the stock recovery screen with a weird android logo.
What I'd like to accomplish at this point is to install the latest version of CWM Touch 6.0.1.9, which I already downloaded from the official site, it seems to be an img file, and after all that is done, I'd like to install the latest version of CleanROM.
I have no access to a computer at this time, so would this still be possible?
Can anybody please walk me through it?
so I acutally managed to download cwm from the market, and it installed, its not the touch version, but it works. I also used es file explorer and went into the system folder, and renamed the recover-from-boot.p file.
Now, what I'd like to do is install cwm touch, but I only have an img file of it downloaded, any ideas on how i can install it without a pc?
have you tried the Rom Manager app, is that how you installed CWM from the market? Rom Manager might have the touch version, but i haven't looked myself.
otherwise, you could probably install the .img file using Terminal Emulator on the phone. sorry i can't give you the exact command, but it would be a dd command and you would need to know the name of the recovery partition to write the image file to.
yogi2010 said:
have you tried the Rom Manager app, is that how you installed CWM from the market? Rom Manager might have the touch version, but i haven't looked myself.
otherwise, you could probably install the .img file using Terminal Emulator on the phone. sorry i can't give you the exact command, but it would be a dd command and you would need to know the name of the recovery partition to write the image file to.
Click to expand...
Click to collapse
So yea...I got rom manager from the market, and installed cwm that way, its not the touch version, but it was enough for me to install CleanRom 3.0
Now, regarding Rom manager, it has an option to flash the latest recovery mod, and I used es file explorer and found the following directory:
/sdcard/clockworkmod/download/download2.clockworkmod.com/recoveries/
inside was the following file:
recovery-clockwork-6.01.9-grouper.img
Now, I wonder if I can simply replace that img file with the following:
recovery-clockwork-touch-6.0.1.9-grouper.img
would I need to rename it and remove the touch part of the file name?
I was thinking of just replacing and flashing via rom manager, you think it'll work?
just tried my above theory, and rom manager is actually smart, it downloads a new copy when you want to flash cwm
I've done something like this (though I forget exactly what) using Android Root Toolkit app.
AcuraKidd said:
just tried my above theory, and rom manager is actually smart, it downloads a new copy when you want to flash cwm
Click to expand...
Click to collapse
Yeah, I'm sure it checks hashes before flashing anything, and since they didn't match, it downloaded a new copy.
I thought you could buy the pro version of rom manager and it would then flash the touch versions for you?
When I go into Rom Manager and choose flash CWM it gives me the option to flash the touch version or the normal version. Maybe you need to flash the normal version with Rom Manager first then it'll give you the option for touch?
if you have the .IMG file for w/e recovery you want to install, download Terminal Emulator app from gPlay and fire off the following commands:
Code:
su
dd if=/sdcard/shineynewrecovery.img of=/dev/block/mmcblk0p1 bs=4096
Alter the /sdcard/shineynewrecovery.img to wherever you saved the .IMG of the recovery.
I just created a zip. Testing now to make sure its all good and then I'll post the link
*edit*
Here's the link
http://db.tt/xEIWqXFe
I know that when I did this for 6.0.1.0 people had trouble flashing this from TWRP but if you have CWM non-touch already installed flash this and you're god to go. Feel free to mirror
Sent from my Galaxy Nexus using xda app-developers app
HellcatDroid said:
if you have the .IMG file for w/e recovery you want to install, download Terminal Emulator app from gPlay and fire off the following commands:
Code:
su
dd if=/sdcard/shineynewrecovery.img of=/dev/block/mmcblk0p1 bs=4096
Alter the /sdcard/shineynewrecovery.img to wherever you saved the .IMG of the recovery.
Click to expand...
Click to collapse
Thanks, this method worked perfectly.
mrich137 said:
I just created a zip. Testing now to make sure its all good and then I'll post the link
*edit*
Here's the link
http://db.tt/xEIWqXFe
I know that when I did this for 6.0.1.0 people had trouble flashing this from TWRP but if you have CWM non-touch already installed flash this and you're god to go. Feel free to mirror
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Thanks, I'll hold onto the zip for the future.
Related
Hello XDA,
So I was following a youtube guide that shows how to root nexus s. (http://www.youtube.com/watch?v=GSD92Qjt5Og). This is one click verison. So after unlocking the bootloader, when its time to select flash CWM, the CMD window would just close. I guess the file i was using were bad. So then i switched over to another youtube video (http://www.youtube.com/watch?v=EA6DlAqYUeo). In this video, (using the files in video's description), I mananged to flash CWM (but i used the latest verison of CWM 5023-cyan.img). Then pretty much followed the video and got superuser installed on my nexus. Now when i tried to boot into recovery, it will not boot into CWM. it shows the android with exclamation mark and there when i press volume up and power, i am taken to the stock recovery i guess.. So now I am confused if my phone is rooted. I do have superuser installed on my phone right now (version that was included in the 2nd youtube video) but I don't have CWM. I am interested in flashing other ROMS. How and what should i do? Sorry for the long explanation. Thanks for your help
Use root explorer or similar program to rename the file "/system/etc/install-recovery.sh" to anything you like (e.g. install-recovery.sh.bak), as this script is run on boot and replaces a custom bootloader if it is installed. After this just flash CWM again and you can be free
You'll have to do this anytime you install a Google Stock ROM.
Harbb said:
Use root explorer or similar program to rename the file "/system/etc/install-recovery.sh" to anything you like (e.g. install-recovery.sh.bak), as this script is run on boot and replaces a custom bootloader if it is installed. After this just flash CWM again and you can be free
You'll have to do this anytime you install a Google Stock ROM.
Click to expand...
Click to collapse
I installed ES File Explorer and I cannot locate any folder called system.. the only 3 folders I see are "android", "clockworkmod", "Lost.DIR". root explorer is paid app. do you know any other free app. I don't know if this ES File explorer allows me to see system files. Its only showing whats on SD card...
NVM... i managed to get another app.. that allowed me to change the file name as you suggested.. then i installed ROM manager.. Flashed CWM from there.. and rebooted into recovery.. and GUESS WHAT.. I GOT CWM.. .. thanks buddy..
No worries mate. BTW, for ES, you need to go to options and tick the two options all the way at the bottom (enable root, mount /system).
So I've installed a custom ClockworkMod recovery and ROM on my Nexus 7 tablet. Life was good. Recently, I was running out of space and decided to delete my CWM backup (after saving it to my computer). And then, I realized I couldn't.
I went into ES File Explorer to try. I couldn't do it there.
I went into the ADB shell as root to try to remove it. No luck again, just the message when I finally DID try to remove one file:
Code:
# rm boot.img
rm failed for boot.img, Operation not permitted
What am I doing wrong?
Edit: This looks like it's ClockWorkMod (5.8.??)'s fault, but besides reading that another backup won't make the current one much larger, I don't actually know how to delete the current one.
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
BillGoss said:
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
Click to expand...
Click to collapse
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
I did this in a way not mentioned here that still deserves mentioning... First I updated to the latest version of CWM available (via the Nexus 7 Toolkit) and then booted into recovery, opened the backup option, deleted the backup that was there, then cleaned the nandroids.
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
erica_renee said:
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
Click to expand...
Click to collapse
primetechv2 said:
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
Click to expand...
Click to collapse
Sorry for re-opening an old thread, but I am having a problem where I have files that I cannot delete from the clockworkmods/blobs folder on my external sd card. So far, I have tried deleting them from a file explorer, deleting them as root from a file explorer, root and non-root deletes from terminal emulator, deleting through windows, adb shell deletes (with system booted).
I also wanted to try adb shell while booted into cwm, but I could not get the adb connection to work from recovery.
I also tried to find the zip file in the developer section and that's the real reason why I revived this thread...Does anyone know where the thread is with the zip file to remove these files?
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Kodiack99 said:
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
When I booted to recovery, I am able to delete each of the backups that I created. These all deleted correctly. I then went to Free unused backup files (to delete the files/folders in the blobs folder) and ran that and most of the files are gone. When I boot back into the phone, there are still some files/folders there and they seem to be taking up about 4-5 GB on the card. When I try to delete them through the file manager apps (either as root or not) they will not delete and the manager reports an error (before clicking delete, the manager displays a statistics report that says that the size of the files are over 2TB so obviously something is very messed up about them). I have also tried to delete them through the terminal (again as root and regular user) and they will not delete there either and they totally mess up the terminal window with unprintable characters (the only way to recover is to exit out of the current window and start a new one).
I finally fixed this problem last night by backing up all of my stuff (except the clockworkmod folder) to my computer. I then rebooted into recovery (latest version of CWM non-touch) and formatting the ext SD Card. When I rebooted there were still some folders there (including the clockworkmod folder). I did a format from within the OS and that cleared everything out. I copied all of my stuff back from my computer and I'm now good to go. Not sure how it got messed up to begin with, but the problem is fixed now. I think I'm going to stick with TWRP from now on.
this Inc. has CWR 5.0.2 on and. 4.1.
how do u download the latest twrp on this?
my usb cable seems to be charging only.
since you seem to have gotten that far, you must be unlocked, rooted and have cwm and some alternate CM 10.0 ROM installed succesfully, right?
did this thread
http://forum.xda-developers.com/showthread.php?t=1404464
not have all the info you need about TWRP? All you are doing is replacing CMW with TWRP. I think you can do this even without a USB cable by downloading the img file to your phone's sd card via goo manager and issuing this command in the terminal app-refer to post #142 in this thread
http://forum.xda-developers.com/showthread.php?t=1404464
the steps are as follows
Flash it through terminal. It's in the Goomanager folder. Rename it as recovery.img.
Open terminal, type:
su, enter,
change directory to goo manager by typing-assuming you downloaded it to sdcard.
cd /sdcard/goomanager
flash_image recovery recovery.img, enter.
Should show a list with no errors.
CM 10.1 has not installed yet.
Is goo manager apps?
Goo play store does not launch.
tekweezle said:
since you seem to have gotten that far, you must be unlocked, rooted and have cwm and some alternate CM 10.0 ROM installed succesfully, right?
did this thread
http://forum.xda-developers.com/showthread.php?t=1404464
not have all the info you need about TWRP? All you are doing is replacing CMW with TWRP. I think you can do this even without a USB cable by downloading the img file to your phone's sd card via goo manager and issuing this command in the terminal app-refer to post #142 in this thread
http://forum.xda-developers.com/showthread.php?t=1404464
the steps are as follows
Flash it through terminal. It's in the Goomanager folder. Rename it as recovery.img.
Open terminal, type:
su, enter,
change directory to goo manager by typing-assuming you downloaded it to sdcard.
cd /sdcard/goomanager
flash_image recovery recovery.img, enter.
Should show a list with no errors.
Click to expand...
Click to collapse
Splash01 said:
CM 10.1 has not installed yet.
Is goo manager apps?
Goo play store does not launch.
Click to expand...
Click to collapse
goomanager is a separate app for downloading roms onto your phone. it;s an app that can be found on Google Playstore
you said you have 4.1 installed-what is that? is that Jellybean? or are you still on Gingerbread 2.34?
if Google Playstore doesn;t load, try clearing the data for that app.
It's JB.
i had cm7, gingerbread before JB was installed.
and
i clicked 'storage' in settings,
PB31MG.zip is in SD card.
Are apps. on this device from Gapps?
tekweezle said:
goomanager is a separate app for downloading roms onto your phone. it;s an app that can be found on Google Playstore
you said you have 4.1 installed-what is that? is that Jellybean? or are you still on Gingerbread 2.34?
if Google Playstore doesn;t load, try clearing the data for that app.
Click to expand...
Click to collapse
Splash01 said:
It's JB.
i had cm7, gingerbread before JB was installed.
and
i clicked 'storage' in settings,
PB31MG.zip is in SD card.
Are apps. on this device from Gapps?
Click to expand...
Click to collapse
what exact ROM is on the device? did you flash it yourself or did you buy it flashed by someone else?
do you have the apps Superuser and Terminal Emulator on the device? If so, I think you can just extract the recovery.img file and put it on the sdcard, then run the set of commands listed above inside Terminal Emulator.
GAPPS refers to Google Apps-the built in stuff coming from Google like Google Playstore, Email, Messaging. But on the Incredible, since it;s limited in the amount of disk space for the OS to about 260 mb, we have to use a version created by the maker of the ROM to fit in this tiny space. When you flash a ROM onto the incredible, it;s a 2 or 3 step process. In recoveryy(either CWM or TWRP)You flash the ROM, it;s associated GAPPS and then optionally, the Low space fix. You also wipe Cache and Dalvik Cache.
can anyone advise? i want to install a custom rom and root my tf300t
i have unlocked it but now i need to install the mod twrp but apparently i need a pc. is there another way? via .apk file or something...
i then need to put my rom and gapps file on sd card, reboot to recovery and install the zip files right? and i am done????
wakkaday said:
can anyone advise? i want to install a custom rom and root my tf300t
i have unlocked it but now i need to install the mod twrp but apparently i need a pc. is there another way? via .apk file or something...
i then need to put my rom and gapps file on sd card, reboot to recovery and install the zip files right? and i am done????
Click to expand...
Click to collapse
Yes you can do that, all you need is a "terminal emulator" app, there are plenty available just search for them. Depending on the custom ROM some already provide updated gapps so be sure to use the right one and not just the one given in tools like goomanager.
I would recommend the following.
1. Backup your apps + data using Titanium Backup
2. Boot into recovery and create a backup of your system
3. Wipe cache/davlik/data + system
4. be aware of the right "flashing order" FIRST the ROM file, then add more zips and choose gapps
5. enjoy your custom ROM
frankgreimes said:
Yes you can do that, all you need is a "terminal emulator" app, there are plenty available just search for them. Depending on the custom ROM some already provide updated gapps so be sure to use the right one and not just the one given in tools like goomanager.
I would recommend the following.
1. Backup your apps + data using Titanium Backup
2. Boot into recovery and create a backup of your system
3. Wipe cache/davlik/data + system
4. be aware of the right "flashing order" FIRST the ROM file, then add more zips and choose gapps
5. enjoy your custom ROM
Click to expand...
Click to collapse
Something tells me he hasnt rooted yet. If im not mistaken, he can't use a terminal app with the dd command if he isnt rooted. I know you can root using adb though with debugging enabled but im not sure he can root without a pc.
Here is a good place for him to start :
http://forum.xda-developers.com/showthread.php?t=2228613
Sent from my SGH-T889 using xda app-developers app
pyraxiate said:
Something tells me he hasnt rooted yet. If im not mistaken, he can't use a terminal app with the dd command if he isnt rooted. I know you can root using adb though with debugging enabled but im not sure he can root without a pc.
Here is a good place for him to start :
http://forum.xda-developers.com/showthread.php?t=2228613
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the correction, assumed he's already rooted sorry.
TWRP 2.8.7.0 custom recovery
thanx to user @Unjustified Dev we have TWRP custom recovery for our phone.
download HERE
So anyone who download the TWRP should send him a dollar for beer or at least thank him!
Of course you do everything on your own!
To test before installation (linux users need sudo before fastboot):
Code:
fastboot -i 0x1bbb boot twrp-2.8.7.0-idol3.img
To install (linux users need sudo before fastboot):
Code:
fastboot -i 0x1bbb flash recovery twrp-2.8.7.0-idol3.img
!BEFORE YOU START, PLEASE READ THIS!
And don´t forget to thank Famewolf for the tutorial, because this could save your phone when something go bad!
Thanks, tried it. It worked.
I also just installed SU directly, bypassing the previous root thread.
1. Download the .zip package from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
2. Put it on the root of my SD card.
3. In TWRP click install and find the .zip.
Wonderful. Just a question: is this recovery for Idol 3 4.7 (6039) or 5.5 (6045) ?
Gynoid said:
Wonderful. Just a question: is this recovery for Idol 3 4.7 (6039) or 5.5 (6045) ?
Click to expand...
Click to collapse
It's for 6045. For 4.7 TWRP, see this post: http://forum.xda-developers.com/showpost.php?p=61976520&postcount=18
Thanks!
is it functional for backing up our system in TWRP?
@DallasCZ could you please provide the original link to TWRP. That was a bit unfair to upload it elsewhere as I tend to track the number of downloads.
Sent from my LGMS395 using Tapatalk
gecko702 said:
is it functional for backing up our system in TWRP?
Click to expand...
Click to collapse
Yes although to my knowledge noone has actually done a restore yet. He's fixing some minor bugs and will be releasing a new version at some point.
famewolf said:
Yes although to my knowledge noone has actually done a restore yet. He's fixing some minor bugs and will be releasing a new version at some point.
Click to expand...
Click to collapse
i am in touch with the dev and allready downloading the new build..will be soon on my google drive
Unjustified Dev said:
@DallasCZ could you please provide the original link to TWRP. That was a bit unfair to upload it elsewhere as I tend to track the number of downloads.
Sent from my LGMS395 using Tapatalk
Click to expand...
Click to collapse
sorry, i corrected the link...
Convert TWRP Backup into flashable rom zip
I found these instructions that explain how to take a TWRP backup and turn it into a flashable zip file. This would allow someone to create a "factory" rom pre-rooted to be flashed.
For TWRP Backup
Transfer the TWRP backup from Phone to PC.
You’ll see a file named system.ext4.win which is the System partition backup of your device. Rename it to system.ext4.tar (Changing its extension from .win to .tar)
Extract the system.ext4.tar using an archive software like Winrar or 7zip.
If your TWRP backup is not in compression mode, you will directly get the system folder, else you will get a file named system.ext4, which should be renamed again to system.ext4.tar and extract it to get the system folder.
Take the boot.emmc.win file and rename it to boot.img.
Now collect a META-INF folder from any custom ROM which is made for your device. Make sure you get the correct Meta-Inf folder, else the Zip won’t work and might worsen the condition of your device.
Select the META-INF, System folders and the boot.img and right click your mouse and select add to Archive.
In the Archive settings, choose the extension of the compressed file as Zip (Make sure of this part)
Now you can use this Zip file to flash it on your Custom recovery.
we dont have the meta-inf folder...there is one in the update i got, but i dont know if this id the right one.
and we dont have custom rom to get meta-inf from.
also the main thing is, that i cannot unpack the system win file when renamed to .tar i dunno why (i got latest 7-zip app).
DallasCZ said:
we dont have the meta-inf folder...there is one in the update i got, but i dont know if this id the right one.
and we dont have custom rom to get meta-inf from.
also the main thing is, that i cannot unpack the system win file when renamed to .tar i dunno why (i got latest 7-zip app).
Click to expand...
Click to collapse
What they primarily want is the "update-binary" which is device specific. I don't remember if the update had one....I did take apart an update-supersu.zip and it uses a script as it's update binary...thought about trying to convert that. Theoretically you could take a meta-inf for another device's rom...and use it's meta-inf making sure to replace the update-binary. It also has an installer script that tells it to mount system and data....extract files from the zip and where to put them. I learned a bit when I was trying to make an update.zip to fix my build.prop.
It untar'd fine for me on my linux pc:
[email protected]:/workarea/android/idol3/TWRP/BACKUPS/408adcbe/1970-01-01--22-28-53_LRX22G_release-keys/work > tar -xvf ../system.ext4.win000
tar: Removing leading `/' from member names
/system/app/
/system/app/AntHalService/
/system/app/AntHalService/AntHalService.apk
/system/app/AntHalService/arm64/
/system/app/AntHalService/arm64/AntHalService.odex
/system/app/BasicDreams/
/system/app/BasicDreams/BasicDreams.apk
/system/app/BasicDreams/arm64/
/system/app/BasicDreams/arm64/BasicDreams.odex
/system/app/Bluetooth/
/system/app/Bluetooth/Bluetooth.apk
/system/app/Bluetooth/arm/
/system/app/Bluetooth/arm/Bluetooth.odex
famewolf said:
What they primarily want is the "update-binary" which is device specific. I don't remember if the update had one....I did take apart an update-supersu.zip and it uses a script as it's update binary...thought about trying to convert that. Theoretically you could take a meta-inf for another device's rom...and use it's meta-inf making sure to replace the update-binary. It also has an installer script that tells it to mount system and data....extract files from the zip and where to put them. I learned a bit when I was trying to make an update.zip to fix my build.prop.
It untar'd fine for me on my linux pc:
[email protected]:/workarea/android/idol3/TWRP/BACKUPS/408adcbe/1970-01-01--22-28-53_LRX22G_release-keys/work > tar -xvf ../system.ext4.win000
tar: Removing leading `/' from member names
/system/app/
/system/app/AntHalService/
/system/app/AntHalService/AntHalService.apk
/system/app/AntHalService/arm64/
/system/app/AntHalService/arm64/AntHalService.odex
/system/app/BasicDreams/
/system/app/BasicDreams/BasicDreams.apk
/system/app/BasicDreams/arm64/
/system/app/BasicDreams/arm64/BasicDreams.odex
/system/app/Bluetooth/
/system/app/Bluetooth/Bluetooth.apk
/system/app/Bluetooth/arm/
/system/app/Bluetooth/arm/Bluetooth.odex
Click to expand...
Click to collapse
i allready build some roms for my older device, so i know what it is about.
For the proper rom zip you have to make the updater script with all the simlinks and metadata ...in the latest update there were no simlinks in the updater script...
without them you can brick your phone.
for example simlinks from 4.4.2 Os from zte V5
Code:
symlink("/data/misc/audio/mbhc.bin", "/system/etc/firmware/wcd9306/wcd9306_mbhc.bin");
symlink("/data/misc/audio/wcd9320_anc.bin", "/system/etc/firmware/wcd9306/wcd9306_anc.bin");
symlink("/persist/WCNSS_qcom_cfg.ini", "/system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini");
symlink("/persist/WCNSS_qcom_wlan_nv.bin", "/system/etc/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin");
symlink("/system/lib/modules/pronto/pronto_wlan.ko", "/system/lib/modules/wlan.ko");
symlink("Roboto-Bold.ttf", "/system/fonts/DroidSans-Bold.ttf");
symlink("Roboto-Regular.ttf", "/system/fonts/DroidSans.ttf");
symlink("libGLESv2.so", "/system/lib/libGLESv3.so");
symlink("mksh", "/system/bin/sh");
this you cannot copy from another device....
Never mind. I installed the second build.
How do I boot into the custom recovery? Is it power up + power button on the Idol 3?
Acreo Aeneas said:
Never mind. I installed the second build.
How do I boot into the custom recovery? Is it power up + power button on the Idol 3?
Click to expand...
Click to collapse
Reboot or power on till you see the alcatel screen pop up....right away hold down up arrow and it should go into recovery.
Thank you so much...been waiting for this....
so now let ROM's start pouring in )))))))
Hmm odd. I had to reflash it. For some reason it didn't take the first time I flashed the second build TWRP to my Idol 3.
What partitions should I backup using TWRP? I'd assume: Boot, System, and Data? Should I include System Image too?
Acreo Aeneas said:
Hmm odd. I had to reflash it. For some reason it didn't take the first time I flash the second build TWRP to my Idol 3.
What partitions should I backup using TWRP? I'd assume: Boot, System, and Data? Should I include System Image too?
Click to expand...
Click to collapse
The default of boot, system and data should be fine for personal use however if you have not yet rooted please read here first! http://forum.xda-developers.com/idol-3/help/want-to-able-to-install-ota-updates-t3163745
So Awesome! best looking twrp Ive seen yet xD. Also, works well too. I havent tested backing up data, but I did a successful restore of the system and boot So far so good!