Related
I have been scouring these boards for hours and can't find my exact problem so I think I need to post this as a noob. I did Albert Wertz's method of rooting my Nook Tablet 16GB which he states will void the warranty. Afterwards I showed version 9.9.9 so I think it was rooted however I never saw superuser and such. I did something where the main menu bar no longer appears when pressing the n button too, annoying, I want it back too.
Anyway I booted into CWM from SD and then removed my boot SD and installed another SD with the img files on it. I have about 4 img files on it from throughout the day trying to update to CM7 and then tried a restore and just a CWM flash, every img file I select starts to perform it's update and somewhere around "extracting files" it says "installation aborted". At first I thought I had a bad memory card but both cards behave the same so I think they are good (creating 70MB partition on the CWM). I did a system restore on it and now it reports version 1.4.0 but I still get all the same errors, I'm stuck. I've spent about 9 hours of messing with this today and can’t think straight. I am going to bed and will try tomorrow, but if anyone could please tell me what I am missing I would very much appreciate it. Happy Easter ! Thanks, Mark O
markols said:
I have been scouring these boards for hours and can't find my exact problem so I think I need to post this as a noob. I did Albert Wertz's method of rooting my Nook Tablet 16GB which he states will void the warranty. Afterwards I showed version 9.9.9 so I think it was rooted however I never saw superuser and such. I did something where the main menu bar no longer appears when pressing the n button too, annoying, I want it back too.
Anyway I booted into CWM from SD and then removed my boot SD and installed another SD with the img files on it. I have about 4 img files on it from throughout the day trying to update to CM7 and then tried a restore and just a CWM flash, every img file I select starts to perform it's update and somewhere around "extracting files" it says "installation aborted". At first I thought I had a bad memory card but both cards behave the same so I think they are good (creating 70MB partition on the CWM). I did a system restore on it and now it reports version 1.4.0 but I still get all the same errors, I'm stuck. I've spent about 9 hours of messing with this today and can’t think straight. I am going to bed and will try tomorrow, but if anyone could please tell me what I am missing I would very much appreciate it. Happy Easter ! Thanks, Mark O
Click to expand...
Click to collapse
In CWM, you need to install from .zip files. It sound like you're trying to install .img.
Thanks... I was installing .zip files, not .img. I was pretty useless last night. I used Alberts 4_5SD recovery this morn and got it rooted to 9.9.9 and I had superuser and titanium backup so all was good. I ran NWM from internal on the tablet and told it to install ROM from the SD card. I pointed to the file and told it to backup, then install the new ROM it said an error had occured when I tried this. I then booted from another SD card to go to CWM and after the white screen with the box, it went into backup and then restored the ROM, however it took me back to a unrooted version. It looked for the ROM I wanted to load but that was on the other SD card. Now I am back at square one, frustrated...
I think I might have found the problem but I am not sure. When I was doing the original CM7 update I wrote CWM to the E drive, (MyNook) so now the drive reports a total size of .99GB with 433MB free. So CWM is installed on this drive and I think that is the proplem. Is there a way to get CWM off the E drive? If I can just uninstall it, will that be sufficient enough to get the root back and then correctly install CM7? Thanks again in advance.
I guess this is turning out to be an ongoing update from me, lol... I am back to a rooted Nook Tablet with 9.9.9 So since I am a glutton for punishment I will try again tonight to do the CM7. I simply deleted the CWM file that I found in the internal memory and it seemed to not hurt anything.
This time I am planning to download Indirect’s latest "NOOK Tab Recovery Flasher.apk" directly to my Nook Tablet, (at the inlaws now and no wifi
If I understand correctly it will install CWM direct on my tablet, I am just wondering where it will end up installed? Then I downloaded the file for internal CM7 installation, the file is named "Nook-Tablet-CM7-Alpha-Final-TEAM-B-signed" I have it and nothing else on the sd card. So when I run CWM from the Nook, I point to the .zip file on the SD card. Sounds easy but after three screw ups, I am aprehensive.
If someone could please confirm that this procedure and the files I am using are compatible and should work with my 16GB Nook Tablet. Again thanks very much and I hope all have been enjoying this Easter holiday........
markols said:
I guess this is turning out to be an ongoing update from me, lol... I am back to a rooted Nook Tablet with 9.9.9 So since I am a glutton for punishment I will try again tonight to do the CM7. I simply deleted the CWM file that I found in the internal memory and it seemed to not hurt anything.
This time I am planning to download Indirect’s latest "NOOK Tab Recovery Flasher.apk" directly to my Nook Tablet, (at the inlaws now and no wifi
If I understand correctly it will install CWM direct on my tablet, I am just wondering where it will end up installed? Then I downloaded the file for internal CM7 installation, the file is named "Nook-Tablet-CM7-Alpha-Final-TEAM-B-signed" I have it and nothing else on the sd card. So when I run CWM from the Nook, I point to the .zip file on the SD card. Sounds easy but after three screw ups, I am aprehensive.
If someone could please confirm that this procedure and the files I am using are compatible and should work with my 16GB Nook Tablet. Again thanks very much and I hope all have been enjoying this Easter holiday........
Click to expand...
Click to collapse
The steps that you have listed in this post are correct. If you do this exactly, everything should go according to plan.
Indirect's great app installs CWM to the recovery partition of your device, overwriting the B&N stock recovery. You can always go back to stock recovery if need be, though, so don't worry.
Thanks Solar.Plexus
The procedure worked as I hoped. I don't understand what went so wrong in my first attempt but the main thing is my wife doesn't look at me with THAT look anymore, since she thought I bricked her 12 hour old NT.....
markols said:
Thanks Solar.Plexus
The procedure worked as I hoped. I don't understand what went so wrong in my first attempt but the main thing is my wife doesn't look at me with THAT look anymore, since she thought I bricked her 12 hour old NT.....
Click to expand...
Click to collapse
No problem. Glad to hear your wife's happy again!
installaton aborted while installing clockmodrecovery
hii i am sagar
i want solution to this problem any body have solution means please reply
i am using micromax mad a94
when i am trying to install clockworkmod on my phone it always show like these
install/sdcard.....
finding update package......
opening update package.....
verifying update package....
installation aborted........
anybody have solution to this problem
please tell me
thank you
Did u solve it yet?
Sent from my iPod touch using Tapatalk
I've encountered weird problem: The phone doesn't boot (got stuck on bootanimation) after nandroid recovery from CWM. I've tried recoverying it over fresh install of same ROM or over formated partitions, but neither of it works. I'm using CWM v5.0.2.0 and trying to recover hephappys PRE4.
Is this caused by some incompatibility of CWM and ICS?
No, cwm 5.0.2.0 is working with ICS, using it currently (haven't tried using backup/restore, but it shouldn't cause any problems imo).
So, what exactly are you doing? Trying to restore an earlier cm9 backup? Try wiping all, including system and boot, before restoring.
Sent from my LG-P500 using XDA
Yes, I've made backup before messing with my ROM and it just fails to recover. I've already tried to wipe everything.
Is there any tool for viewing backup files on Windows? I guess that the file is somehow broken.
Is there any way how to get calls and sms from this raw data?
Here is boot logcat: https://gist.github.com/2603614
Jirrick said:
I've encountered weird problem: The phone doesn't boot (got stuck on bootanimation) after nandroid recovery from CWM. I've tried recoverying it over fresh install of same ROM or over formated partitions, but neither of it works. I'm using CWM v5.0.2.0 and trying to recover hephappys PRE4.
Is this caused by some incompatibility of CWM and ICS?
Click to expand...
Click to collapse
have the same issue with cwm...
recommand u to use amonra...gwtting best with it
When I was on cm9 and restored my cm7 backup=same thing(yes, I wiped everything)
Well, that backup image is somehow corrupted as it cant be correctly deployed. At least I've managed to extract SMS, the rest is not so important for me.
CWM is pretty much useless when it creates backups which can't be used for recovery...
I don't think that there is a specific problem with CWM and ICS- I have been making backups and recovering quite often ICS builds (including hephappy's pre4) in the last weeks, no problems so far (knock on wood ).
Do you have other/older backups that you can try to recover and see if you get stuck at bootloop?
What about reinstalling the build from scratch- just to see that everything boots? You can later try either restoring your original backup (the one causing you problems), or using TiB or similar applications that can extract applications+data from nand backups.
Could the backup file got corrupted somehow? I don't remember CWM having some inherent checking of md5 before restoring backups (I could be mistaken, as I have never had a bad nandbackup with the P500 phone so never noticed anything weird). For example, I used to have an HTC MT4G with 4ext touch recovery which would always check md5sum and let the user know if backup was corrupted, and I did got a corrupted backup file once.
Back to topic- If anything else fails and you can't recover, maybe try to copy the backup to a different sdcard? Perhaps it's a shot in the dark but worth trying, just in case the problem is in sdcard?
Older backups are only CM7 and they are working flawlessly. I don't know what happened, but it wasn't byte-level error as MD5 check passed on that image. It's more likely the recovery "forgot"/wasn't able to recover some files in /data partition.
Later I've tried to install some fresh ICS, did some changes (configuration + apps), backuped, wiped partitions, then restored and everything worked , so it's definitely not a general CWM problem. It's probably a bad luck, when you really need the backup, it just corrupt itself to annoy you...
As I wrote, I've managed to retrive my SMS and that's enough for me. I don't trust that image so I will install fresh apps via Appbrain and do the new setting by myself (I wanted to make some chcnges to phone configuration, this is just the right moment) .
I have never had much luck with the CWM recovery system. It's really buggy and sometimes only restores select partitions. Or if it couldn't mount the drive at the time of backing up, sometimes it just refuses to tell you or tells you but you have to start the backup over..
Like said above, I would try Amonra. It's a far better recovery and it has almost no bugs to speak of
Cheers mate.
A week and a half ago I used aicjofs' nifty Nabilab v2.3.3 on my niece's Nabi2 (v1.9.37). I had a driver problem but was able to take care of that using the pdanet drivers as recommended in the thread. NabiLab then worked like a charm. I used the "Install Root, Recovery and Gapps" option.
Everything functioned great for about 9 days and then the Nabi2 wifi issue appeared. The selector stays in the off position and will not turn on. I saw a Linux based fix in another thread that was mixed in with instructions about rolling back the Nabi to stock. However, our Nabilab install was in Win7 64bit and we'd also rather not end up back at stock -- the rooted and Play-capable Nabi was terrific for adding to FUHU's limited stock of good kids games.
I'd be grateful for suggestions on the best way to correct the wifi issue on a Win-7-based NabiLab-applied root, recovery and gapps. We hope to retain (or at worst re-apply) the root/gapps. Thanks!
gnomebrew said:
A week and a half ago I used aicjofs' nifty Nabilab v2.3.3 on my niece's Nabi2 (v1.9.37). I had a driver problem but was able to take care of that using the pdanet drivers as recommended in the thread. NabiLab then worked like a charm. I used the "Install Root, Recovery and Gapps" option.
Everything functioned great for about 9 days and then the Nabi2 wifi issue appeared. The selector stays in the off position and will not turn on. I saw a Linux based fix in another thread that was mixed in with instructions about rolling back the Nabi to stock. However, our Nabilab install was in Win7 64bit and we'd also rather not end up back at stock -- the rooted and Play-capable Nabi was terrific for adding to FUHU's limited stock of good kids games.
I'd be grateful for suggestions on the best way to correct the wifi issue on a Win-7-based NabiLab-applied root, recovery and gapps. We hope to retain (or at worst re-apply) the root/gapps. Thanks!
Click to expand...
Click to collapse
The wifi issue has plagued the Nabi 2 since the beginning. If you search you will see 100's of post on Facebook with people with the issue(That's where Nabi runs their support mostly.), usually stated as wifi not working and or MAC address unavailable. The official solution currently is to do a factory reset and update to v2.0.5. I personally have never had the issue and I wish I did because there has to be an easier fix then a factory reset. The factory reset has to be wiping some data that we could shortcut without wiping everything else. It could be the wpa_supplicant.conf or the entropy.bin in /data/misc/wifi, or perhaps a com.android settings that is messed up. A permission issue where the wifi user in system group isn't set right, or the read write. I always thought that the key might be in the ramdisk init files(the key to tracking it down not so much the issue itself) as the issue was happening back in the beginning when people were running mismatched kernel/ramdisk in the early patches. Regardless it's hard to guess at what it is without seeing the device.
So as to what you do...I suppose you have a few options. Use TWRP to flash back the original Nabi ROM that Nabilab backed up for you, or do the factory reset. If you want to keep what you have you use something like titanium backup or similar program from play store, back up your apps and then do one of the above, then restore everything from titanium backup. It's happened to a lot of people, both with stock and modded Nabi's. When you are done go to v2.0.5 it seems much better at the wifi issue. Since you are forced to wipe the tablet either way, you can do no harm it trying this app.
https://play.google.com/store/apps/details?id=org.wahtod.wififixer&hl=en
Sorry I wish I was more help as there has to be a shortcut to all this but most people rather then digging deep into it just do the reset and restore their apps, and we never get enough data to figure it out. Now that 2.0.5 has made the issue better there is even less troubleshooting of it. Also everything in Nabilab will work on 2.0.5. except the lockscreen modding tool.
Resolved
Aicjofs,
Thanks so much for the reply. The Nabi is now back in action.
Following your advice, I started by giving Wifi-Fixer a try. No joy. I then backed-up user apps to USB with Titanium before rebooting to Recovery Kernel and attempting a restore from my initial TWRP backup. None found! Ugh. I'm not sure if I did something wrong or skipped a step while setting it up two weeks ago. On to Plan B: NabiLab Full.
I downloaded your NabiLab Full (I had used Lite during setup) in order to restore from the included Nabi image. This worked well and resulted in a mostly stock Nabi (I say mostly because the image includes phantom media listings that need deleting). After that, I could reboot to the Nabi/Android system just fine, but trying to load Recovery Kernel from the boot menu would fail, giving me just a dead android icon. I re-installed TWRP from NabiLab without issue.
I OTA updated to 2.0.5, rebooted to TWRP to make a pre-root backup image, and then used NabiLabs to once again root and install Gapps. Finally, as you suggested, I used the previously mentioned Titanium backup to restore non-system apps/data. 'Cept for a few minor settings like wallpaper & folder names it was back to the Nabi my niece remembered.
THANK YOU for your advice and for making and supporting NabiLab.
gnomebrew said:
Aicjofs,
Thanks so much for the reply. The Nabi is now back in action.
Following your advice, I started by giving Wifi-Fixer a try. No joy. I then backed-up user apps to USB with Titanium before rebooting to Recovery Kernel and attempting a restore from my initial TWRP backup. None found! Ugh. I'm not sure if I did something wrong or skipped a step while setting it up two weeks ago. On to Plan B: NabiLab Full.
I downloaded your NabiLab Full (I had used Lite during setup) in order to restore from the included Nabi image. This worked well and resulted in a mostly stock Nabi (I say mostly because the image includes phantom media listings that need deleting). After that, I could reboot to the Nabi/Android system just fine, but trying to load Recovery Kernel from the boot menu would fail, giving me just a dead android icon. I re-installed TWRP from NabiLab without issue.
I OTA updated to 2.0.5, rebooted to TWRP to make a pre-root backup image, and then used NabiLabs to once again root and install Gapps. Finally, as you suggested, I used the previously mentioned Titanium backup to restore non-system apps/data. 'Cept for a few minor settings like wallpaper & folder names it was back to the Nabi my niece remembered.
THANK YOU for your advice and for making and supporting NabiLab.
Click to expand...
Click to collapse
Glad it worked and she is back in business and happy! Oh, that current back up you made of v2.0.5... Copy that TWRP folder to your computer
Hi all,
This is the first time I've tried installing a custom ROM on my VZW S4 (i545) (MDK firmware. Yes, I held out on the OTA since May). I've got a few thoughts and a couple of questions I was hoping could be addressed. I consider myself familiar with flashing ROM's and whatnot, so I won't need hand-holding steps in answer to my questions.
Some info:
VZW S4
MDK Firmware
Recovery: OUDhs CWM Touch Req0very v1.0.3.5
I haven't taken any OTA since I got the phone back in May. This leads me to believe (correct me if I'm wrong) that I'm on Android 4.2.2?
Current ROM: AOKP Nightly Build for 10/31/2013 (MR2)
Thoughts: Holy hell, this ROM is BLAZING fast. I am missing a few features, but none I use regularly (I don't use any of the TouchWiz "smart" features. Damn battery hogs). I was able to flash this over and install GAPPS without any problems. Loading time is incredible, and I love how clean the interface is.
Questions:
Can anyone help me figure out why I cannot install CM10.2? Not sure if that's because I downloaded the wrong version or something, but after flashing it, the screen stays stuck at the Galaxy S4 logo and doesn't move. Maybe I didn't wait long enough, but it surely didn't move in any reasonably expected time (AOKP, by comparison, loaded probably <1 minute). Any thoughts on why this might be? I really want to try CM10.2, so perhaps I should try a different build?
Another question/concern: I downloaded a few different ROMs last night -- CM10.2, AOKP and st0ckdr0id. AOKP installed fine, CM10.2 froze up, but when I installed st0ckdr0id (after wiping out, of course), I got what I think is referred to as a kernel panic. The message was similar to "This phone has software installed on it that Verizon Wireless has determined to be unsafe. Please power off the phone and take to the nearest Verizon Wireless store for help". In the top-left corner, it had in bold RED letters "Kernel secure: FAIL" (or similar wording). I fixed this by booting back into recovery, wiping out, and then installing AOKP again. Can anyone help me understand why this happened?
Why is only ~10GB of space still available when I -thought- I wiped out everything?
What I'm really searching for is an AOSP ROM that is very clean and light, but has SOME of the TouchWiz features. Any recommendations?
My phone only shows me as having a 3G connection, where normally I have 4G LTE. Anything I can do to fix this? Is this an issue with the ROM not detecting the right kind of radio? Bug report, perhaps?
I can't mount my external_sd in my CWM anymore. Yes, I used to be able to do it at one point, because I've done an external nandroid backup to it from within CWM in the past (as of October 29th, if the date on the backups is correct). I've read in other Google searches that it has something to do with the formatting of the SD card, but I haven't removed that SD card from my phone in a few months to have adjusted anything to do with formatting. I plugged the memory card into my Linux laptop this morning while diagnosing this and got an error about an unknown exfat partition. Any advice would be greatly appreciated.
Stupid question: Is there a way to -completely- wipe my internal SD card clean of all my current files? I know when I "wipe" /data I can still see all of my files from the previous installation, and I'm not ballsy enough to wipe /sdcard. I guess the question that then coincides with this is if I were able to completely wipe the phone, I assume that would wipe the recovery as well?
Sorry for some of the novice questions -- I have no problem messing with my old TF300T tablet (because NVFlash will save the day), but this is my only phone, only line of communication and SOLE way for me to answer calls for work (24/7 rotating on-call), so it is VERY important to me to ask questions and not go down for more than 1 hour.
Thanks for all help guys, its much appreciated. I hope to be able to test ROMs regularly and maybe start posting video reviews or something, who knows?
Thanks,
Opethfan89
opethfan89 said:
Hi all,
This is the first time I've tried installing a custom ROM on my VZW S4 (i545) (MDK firmware. Yes, I held out on the OTA since May). I've got a few thoughts and a couple of questions I was hoping could be addressed. I consider myself familiar with flashing ROM's and whatnot, so I won't need hand-holding steps in answer to my questions.
Some info:
VZW S4
MDK Firmware
Recovery: OUDhs CWM Touch Req0very v1.0.3.5
I haven't taken any OTA since I got the phone back in May. This leads me to believe (correct me if I'm wrong) that I'm on Android 4.2.2?
Current ROM: AOKP Nightly Build for 10/31/2013 (MR2)
Thoughts: Holy hell, this ROM is BLAZING fast. I am missing a few features, but none I use regularly (I don't use any of the TouchWiz "smart" features. Damn battery hogs). I was able to flash this over and install GAPPS without any problems. Loading time is incredible, and I love how clean the interface is.
Questions:
Can anyone help me figure out why I cannot install CM10.2? Not sure if that's because I downloaded the wrong version or something, but after flashing it, the screen stays stuck at the Galaxy S4 logo and doesn't move. Maybe I didn't wait long enough, but it surely didn't move in any reasonably expected time (AOKP, by comparison, loaded probably <1 minute). Any thoughts on why this might be? I really want to try CM10.2, so perhaps I should try a different build?
Another question/concern: I downloaded a few different ROMs last night -- CM10.2, AOKP and st0ckdr0id. AOKP installed fine, CM10.2 froze up, but when I installed st0ckdr0id (after wiping out, of course), I got what I think is referred to as a kernel panic. The message was similar to "This phone has software installed on it that Verizon Wireless has determined to be unsafe. Please power off the phone and take to the nearest Verizon Wireless store for help". In the top-left corner, it had in bold RED letters "Kernel secure: FAIL" (or similar wording). I fixed this by booting back into recovery, wiping out, and then installing AOKP again. Can anyone help me understand why this happened?
Why is only ~10GB of space still available when I -thought- I wiped out everything?
What I'm really searching for is an AOSP ROM that is very clean and light, but has SOME of the TouchWiz features. Any recommendations?
My phone only shows me as having a 3G connection, where normally I have 4G LTE. Anything I can do to fix this? Is this an issue with the ROM not detecting the right kind of radio? Bug report, perhaps?
I can't mount my external_sd in my CWM anymore. Yes, I used to be able to do it at one point, because I've done an external nandroid backup to it from within CWM in the past (as of October 29th, if the date on the backups is correct). I've read in other Google searches that it has something to do with the formatting of the SD card, but I haven't removed that SD card from my phone in a few months to have adjusted anything to do with formatting. I plugged the memory card into my Linux laptop this morning while diagnosing this and got an error about an unknown exfat partition. Any advice would be greatly appreciated.
Stupid question: Is there a way to -completely- wipe my internal SD card clean of all my current files? I know when I "wipe" /data I can still see all of my files from the previous installation, and I'm not ballsy enough to wipe /sdcard. I guess the question that then coincides with this is if I were able to completely wipe the phone, I assume that would wipe the recovery as well?
Sorry for some of the novice questions -- I have no problem messing with my old TF300T tablet (because NVFlash will save the day), but this is my only phone, only line of communication and SOLE way for me to answer calls for work (24/7 rotating on-call), so it is VERY important to me to ask questions and not go down for more than 1 hour.
Thanks for all help guys, its much appreciated. I hope to be able to test ROMs regularly and maybe start posting video reviews or something, who knows?
Thanks,
Opethfan89
Click to expand...
Click to collapse
Wow that's a lot. Let's see if we can get you answers.
1. Switch recoveries to twrp 2.5.0.2. I can't stress the importance of the particular version enough. There are others. This is absolutely the most stable. It's what the devs use. I think then your cm issue will be resolved.
Correct way to wipe with twrp.
1.wipe - >factory reset.
2. Advanced wipe - >check system, data, davlik, cache then wipe.
3. The go back to main screen and install rom.
2. Answered by answer one. Lots of people have lots of opinions about the various recoveries. All I can tell you is this is what all the devs use for their recovery. Can't argue with that.
3. Reserved space. It might say you have 16 gigs but a good size chunk is taking merely by formatting. Then the ROM and programs you have installed of course.
4. Honestly they are all freaking great. The aosp roms. You do the answer to number one and you can find out. DU is my fav @ this moment. Followed by beanstalk.
5. Go to mobile networks make sure your network mode is set to cdma +lte/evdo.
6. Answer 1.
7. You don't really want to wipe the entire internal SD card. Sounds good when you think it might screw you if you did it.
Sent from my Nexus 7 using xda app-developers app
Mightycaptain said:
Wow that's a lot. Let's see if we can get you answers.
1. Switch recoveries to twrp 2.5.0.2. I can't stress the importance of the particular version enough. There are others. This is absolutely the most stable. It's what the devs use. I think then your cm issue will be resolved.
Correct way to wipe with twrp.
1.wipe - >factory reset.
2. Advanced wipe - >check system, data, davlik, cache then wipe.
3. The go back to main screen and install rom.
2. Answered by answer one. Lots of people have lots of opinions about the various recoveries. All I can tell you is this is what all the devs use for their recovery. Can't argue with that.
3. Reserved space. It might say you have 16 gigs but a good size chunk is taking merely by formatting. Then the ROM and programs you have installed of course.
4. Honestly they are all freaking great. The aosp roms. You do the answer to number one and you can find out. DU is my fav @ this moment. Followed by beanstalk.
5. Go to mobile networks make sure your network mode is set to cdma +lte/evdo.
6. Answer 1.
7. You don't really want to wipe the entire internal SD card. Sounds good when you think it might screw you if you did it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response Mightycaptain! I used CWM as my first ever recovery and am kinda pressed on it, which is why I use it, but I have no issues going to TWRP if that means fixing my issues. Can you elaborate on how to install TWRP in place of my current CWM? I'll do some Googling in the meantime to try to find the answer myself. (I haven't done any flashing or rooting stuff since I got the phone in May!!)
Thanks for your answer in #5. Fixed the issue I was having.
My reason for wanting to wipe the entire internal SD card is there are still files, folders, logs and backups from when I had my previous ROM. I'm having issues restoring my nandroid backup from the night of the 7th so is it at all possible for me to salvage some of my settings, apps and file backups from those existing files? Once I fix my nandroid, I'm going to keep the nandroid backup in a safe place and I ideally want to have a completely clean phone to start from: That means getting rid of all those old files and other nonsense from before. Is this a possibility?
I'm going to spend my time today trying to extract data from my nandroid backups using ROM Toolbox Pro. If that doesn't work, I have a nandroid backup from the 31st that has 99% of the stuff I need so I'll try to restore that. If THAT doesn't work, then I'm going to cry myself to sleep while trying to remember all of my contacts
Wish me luck, and hopefully I can get some answers to my last few questions!
Thanks,
Opethfan89
opethfan89 said:
Thanks for your response Mightycaptain! I used CWM as my first ever recovery and am kinda pressed on it, which is why I use it, but I have no issues going to TWRP if that means fixing my issues. Can you elaborate on how to install TWRP in place of my current CWM? I'll do some Googling in the meantime to try to find the answer myself. (I haven't done any flashing or rooting stuff since I got the phone in May!!)
Thanks for your answer in #5. Fixed the issue I was having.
My reason for wanting to wipe the entire internal SD card is there are still files, folders, logs and backups from when I had my previous ROM. I'm having issues restoring my nandroid backup from the night of the 7th so is it at all possible for me to salvage some of my settings, apps and file backups from those existing files? Once I fix my nandroid, I'm going to keep the nandroid backup in a safe place and I ideally want to have a completely clean phone to start from: That means getting rid of all those old files and other nonsense from before. Is this a possibility?
I'm going to spend my time today trying to extract data from my nandroid backups using ROM Toolbox Pro. If that doesn't work, I have a nandroid backup from the 31st that has 99% of the stuff I need so I'll try to restore that. If THAT doesn't work, then I'm going to cry myself to sleep while trying to remember all of my contacts
Wish me luck, and hopefully I can get some answers to my last few questions!
Thanks,
Opethfan89
Click to expand...
Click to collapse
Check my post here for twrp 2.5.0.2.
http://forum.xda-developers.com/showthread.php?p=47275165
You can flash it in your current recovery. It overwrites CWM. I would make sure you have a flashable for CWM just in case you need to go back for some reason. Also the backups between those 2 recoveries are not compatible. But I would nandroid with CWM before flashing twrp. I would also change were you recovery is pointing to for storage to the external SD if you haven't already. After you have cut your current backup and past it there. You can use rom toolbox pro to back up your contacts and restore it once you flash a new ROM.
Now as good advice going forward I would add your contacts to your Google account. That way when you flash new stuff or drop your phone in the toilet as soon as you add your Google account to the phone all those contacts will automatically download. But it is always a good idea to use tibu or rom toolbox pro to back up all your apps and seeing and use that after flashing roms to restore apps and settings.
But honestly I'd nandroid, move my contacts to Google, make app backups. Flash twrp. Then start flashing roms. You could be doing it in an hour. After you flash twrp make another nandroid so you have a twrp compatible backup. Then in a day or so of you are happy with everything delete the CWM backups for space.
Edit: as to extracting things from your current nandroid. Not sure if that is possible for one thing it is compressed not sure how that would work unless you are doing a full restore.
Also for future reference with TWRP. When restoring nandroid wipe like your flashing a new rom before restoring.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Check my post here for twrp 2.5.0.2.
http://forum.xda-developers.com/showthread.php?p=47275165
You can flash it in your current recovery. It overwrites CWM. I would make sure you have a flashable for CWM just in case you need to go back for some reason. Also the backups between those 2 recoveries are not compatible. But I would nandroid with CWM before flashing twrp. I would also change were you recovery is pointing to for storage to the external SD if you haven't already. After you have cut your current backup and past it there. You can use rom toolbox pro to back up your contacts and restore it once you flash a new ROM.
Now as good advice going forward I would add your contacts to your Google account. That way when you flash new stuff or drop your phone in the toilet as soon as you add your Google account to the phone all those contacts will automatically download. But it is always a good idea to use tibu or rom toolbox pro to back up all your apps and seeing and use that after flashing roms to restore apps and settings.
But honestly I'd nandroid, move my contacts to Google, make app backups. Flash twrp. Then start flashing roms. You could be doing it in an hour. After you flash twrp make another nandroid so you have a twrp compatible backup. Then in a day or so of you are happy with everything delete the CWM backups for space.
Edit: as to extracting things from your current nandroid. Not sure if that is possible for one thing it is compressed not sure how that would work unless you are doing a full restore.
Also for future reference with TWRP. When restoring nandroid wipe like your flashing a new rom before restoring.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Hey thanks again for your quick response!! I'm glad I checked this first, because I'm in my ROM Toolbox app atm and it has an option to let me install TWRP 2.5.0.2 from within the app itself. Should I do it this way?
I will be adding all contacts to Google from now on. Unfortunately I saved all my stuff to my Verizon backup assistant so I just need one last shot at my phone to save all those contacts (manually, if I must) and be able to enter them onto the new ROM.
By "flash it in your current recovery" I assume you mean download the .zip, place it on my internal /sdcard, and then "flash" it just like I would flash a ROM, right?
I'm sure I have a "flashable" for CWM somewhere but like I said, I haven't done any of this stuff on this phone since I first bought it, and things have changed so much with everyone having OTA's and being locked out that I'm not sure what process is the same or what has changed. I can't afford to lose this phone so I'm hesitant to go balls to the wall to try things.
I will try the things you've listed here. Seems like a nandroid + TiBu + Google Contacts is my best bet to get up and running each time I decide to try a new ROM.
Thanks again!
opethfan89 said:
Hey thanks again for your quick response!! I'm glad I checked this first, because I'm in my ROM Toolbox app atm and it has an option to let me install TWRP 2.5.0.2 from within the app itself. Should I do it this way?
I will be adding all contacts to Google from now on. Unfortunately I saved all my stuff to my Verizon backup assistant so I just need one last shot at my phone to save all those contacts (manually, if I must) and be able to enter them onto the new ROM.
By "flash it in your current recovery" I assume you mean download the .zip, place it on my internal /sdcard, and then "flash" it just like I would flash a ROM, right?
I'm sure I have a "flashable" for CWM somewhere but like I said, I haven't done any of this stuff on this phone since I first bought it, and things have changed so much with everyone having OTA's and being locked out that I'm not sure what process is the same or what has changed. I can't afford to lose this phone so I'm hesitant to go balls to the wall to try things.
I will try the things you've listed here. Seems like a nandroid + TiBu + Google Contacts is my best bet to get up and running each time I decide to try a new ROM.
Thanks again!
Click to expand...
Click to collapse
Understand the hesitancy completely. But with nodding comes risk. It is always about whether you can accept the worst possible outcome.
Rom toolbox pro flashing recovery? I don't know never tried it.
Yes I would download the recovery. Leave it on SD card reboot to recovery and flash like a rom.
Yes nandroid tibu and saving your contacts to Google is the quickest way to get up and running again.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Understand the hesitancy completely. But with nodding comes risk. It is always about whether you can accept the worst possible outcome.
Rom toolbox pro flashing recovery? I don't know never tried it.
Yes I would download the recovery. Leave it on SD card reboot to recovery and flash like a rom.
Yes nandroid tibu and saving your contacts to Google is the quickest way to get up and running again.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Mighty, just wanted to report that flashing TWRP 2.5.0.2 from within ROM Toolbox Pro worked like a charm. I'm on TWRP as we speak.
Thank you so much for your responses. If anyone else has anything to add, or a different response to my questions, please do so! In the meantime, I'm going to try to figure out how to get my nandroid backup working...
Cheers!
*EDIT* Made a backup with TWRP (whose interface is bloody phenomenal, btw), flashed CWM and its working like a charm!! Going to try the st0ckdr0id one as well. Still working on getting that nandroid working so I can recover my stuff and get to customizing!
Hey XDA,
I am going through the process formatting my tablet for my mother to use. I may have deleted too much lol. All of my backups I had made had my account associated with them so I was trying to make some fresh backups without any accounts attached. Long story short I formatted everything in CMW and now I am stuck lol. I deleted all my backups along with everything else, no files found under Sdcard or anywhere else. All I can get into is CMW v6.0.3.6 and nothing else. Can I just transfer a rom and gapps to the tablet via computer and install?
If so, whats the latest and greatest? I had a cynogen kitkat rom installed that I really liked, but not sure of the build or anything it worked really good for me except I couldn't factory reset, it would crash.