anyone else having this happen?
makes backups ok but wont restore anything freezes at the white htc screen
You need to run your backups and recovery from within CWM. See Absolute_Zero's thread in the Development section for more info (last post).
Happened to me yesterday.
I thought I had corrupted my backups ...
Its not working for me no matter what i try any ideas?
Same problem here, just had to restore and couldnt. backups always made directly from recovery.
There are a lot of reports on this recently
http://forum.xda-developers.com/showthread.php?t=1179386
Visit the above link and revert back to an older recovery if you have backup from recovery pre-5.x, if not flash a rom from scratch. It will load up, just did it myself.
CWR 5.0.1.0 seems to work fine as I've said. I've restored backups from CWR4 which someone suspected to be the problem. It's not as I just did it with 3 different older backups to confirm and subsequently restored to my present backup all using RomManager (since that was more than likely what most users with problems were using).
I will continue testing a few scenarios but as of right now, I can't reproduce the problem. I'm not saying it doesn't exist. I just can't reproduce it without more details.
If you're still having problems AND you've updated to the latest RomManager (4.4.0.5 at this time) AND confirmed you've flashed the lastest CWR (5.0.1.0 at this time) then pastebin your /sdcard/clockworkmod/report.log for someone to look at.
Edit:
I suppose I should mention (although it should be clear) that if you restore a backup you no longer have the updated version of RM so you will need to update it again before it will work with your current recovery.
as far as i can tell gb sense roms with the 3.0 sense seem to be the common issue as far as not restoreing. and it is definitly a known issue... something about a ext3 or ext4 partion or some crap.....
Perhaps it's just backups of Sense-based roms in general. I haven't run Sense since 2hrs after I bought the thing so all the backups I was trying that worked perfectly fine were all aosp. This makes the most "sense" of anything I've heard so far. It may have something to do with the partition format being included in the images now so CWR5 restores older backups without that detail. I have a hard time believing koush wouldn't have included some way to handle those though.
I went back to my old recovery
Sent from my tbolt running ShiftTh3ory AOSP
It seems to be the ext4 not supported
i will also add that backups made on 5x recoveries will restore on 4x as long as its not from a ext4.
i hope that makes some kinda sense to somebody but these are the facts.
So it seems that the ext4 is just not supported on the 5x recovery. I just hope they are working on it and are aware of it
Yes, after several restore attempts of a couple sense roms using 5.0.1.0 I hang at the splash screen.
So today I installed 2 roms from scratch after not being able to restore prior backups created with with 4.x. After each fresh install today I booted into recovery and performed a backup using 5.0.1.0 (RM says that is the version installed).
Recovery will NOT restore the fresh 5.x backups either. Backup and restore were of sense roms.
Just successfully performed a restore of an aosp based rom while writing this post.
Can you see if ext4 partitions can be mounted in adb shell in recovery?
Also, are sense roms ext3 or ext4? What is the exact error?
Can someone pull a /tmp/recovery.log after a failed restore and pastebin it?
I believe I just fixed this in 5.0.2.1. Let me know.
Koush said:
I believe I just fixed this in 5.0.2.1. Let me know.
Click to expand...
Click to collapse
Koush,
The backups in 5.0.2.1 have the Cache, Data and System img files in zip format which is not the format of my other backup's made with the older versions of CWM.
Do you expect 5.0.2.1 to be able to restore the older backups or just ones made in 5.0.2.1?
Yes the last version fixed the mounting issue 5.0.2.1 is what you want!
Thanks Koush
Older backups restore just fine. Happy Days
Related
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the Nexus One. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications. I've only tested it quickly on my Nexus One, and it seems to work.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-passion.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-passion.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
Thanks for compiling and posting this update here. I hope it works better than 3.0.0.5
If you're testing it, let me know if it works.
Sent from my Nexus S using Tapatalk
did anyone test this, does it resolve the damaged sd-ext partition in 3.0.0.5 one ??
gwassef said:
did anyone test this, does it resolve the damaged sd-ext partition in 3.0.0.5 one ??
Click to expand...
Click to collapse
Not using sd-ext on my N1, so I don't know. But 3.0.0.5 never damaged it back when I was using sd-ext.
Sent from my Nexus S using Tapatalk
I got it damaged 2 times, I thought it was my S2E app, but when i sent them they told me remove the 3.0.0.5 as it is known with this issue, install an older version. Since i installed the release before this one, i have no problems at all.
zyonee said:
Not using sd-ext on my N1, so I don't know. But 3.0.0.5 never damaged it back when I was using sd-ext.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
zyonee said:
If you're testing it, let me know if it works.
Click to expand...
Click to collapse
So far I tested backing up, restoring, wiping and flashing all seemed to work fine.
Can't tell anything about compatibility to SD-ext, but a compiled version of CWM 3.0.24 from the Blandroid ROM showed no problems with SD-ext. I guess this one won't make problems either.
Need to test if ROMManager is still fully functional with this version.
Kelvino9 said:
So far I tested backing up, restoring, wiping and flashing all seemed to work fine.
Can't tell anything about compatibility to SD-ext, but a compiled version of CWM 3.0.24 from the Blandroid ROM showed no problems with SD-ext. I guess this one won't make problems either.
Need to test if ROMManager is still fully functional with this version.
Click to expand...
Click to collapse
Should work, but you'll need to try it.
For some reason, ROM manager doesn't work for me. It downloads the rom, asks me if i want gapps, wipe /etc, then it reboots but NOT in recovery, and if i select Recovery, doesn't work. (goes back to original screen)... any ideas..?
joesatri said:
For some reason, ROM manager doesn't work for me. It downloads the rom, asks me if i want gapps, wipe /etc, then it reboots but NOT in recovery, and if i select Recovery, doesn't work. (goes back to original screen)... any ideas..?
Click to expand...
Click to collapse
Is the recovery properly flashed? Works well on my NS
Sent from my Nexus S using Tapatalk
sorry, blonde moment :L
Installed this recovery in my N1, works great. Maybe stupid question...Is there any way to make recoverys font bigger....There is so many space, but the font is so small...
Spakainz said:
Installed this recovery in my N1, works great. Maybe stupid question...Is there any way to make recoverys font bigger....There is so many space, but the font is so small...
Click to expand...
Click to collapse
You'll have to ask koush or the other devs about that. I only compiled from source. I'm not that skilled at modding this kind of code...
Sent from my Nexus S using Tapatalk
This recovery works well for me. Flashed using fastboot.
I also used this recovery to reformat the sd-ext partition and now my nandroid backups complete without freezing (they would freeze on the sd-ext backups last time requiring a battery pull).
Thanks for compiling and sharing this!
-D
Kelvino9 said:
So far I tested backing up, restoring, wiping and flashing all seemed to work fine.
Can't tell anything about compatibility to SD-ext, but a compiled version of CWM 3.0.24 from the Blandroid ROM showed no problems with SD-ext. I guess this one won't make problems either.
Need to test if ROMManager is still fully functional with this version.
Click to expand...
Click to collapse
restoring doesn't work with sd-ext (1GB ext4 in my case): it's always aborting during restoring data! no cache and sd-ext restoring and no "restore completed" CWM message but jumping back to the CWM main menu.
it's the same with the other CWM3.2.0.1 for Nexus One.
:-(
This Corrupts EXT partition!
This recovery corrupts EXT partition while the 2.4.0.1 doesn't restore!!! I'm staying away from clockwork recoveries from now on! I'm sick and tried of restoring corrupt ext partitions!
sir*mez said:
This recovery corrupts EXT partition while the 2.4.0.1 doesn't restore!!! I'm staying away from clockwork recoveries from now on! I'm sick and tried of restoring corrupt ext partitions!
Click to expand...
Click to collapse
So it's safe if not using sd-ext. Sorry I can't help solve the problems...
Sent from my Nexus S using Tapatalk
accuphase said:
restoring doesn't work with sd-ext (1GB ext4 in my case): it's always aborting during restoring data! no cache and sd-ext restoring and no "restore completed" CWM message but jumping back to the CWM main menu.
it's the same with the other CWM3.2.0.1 for Nexus One.
:-(
Click to expand...
Click to collapse
Yes, now having the same problem with sd-ext backups too.
zyonee said:
Only available in standard orange, I actually can't be bothered to find out how to make different color variants.
Click to expand...
Click to collapse
Aww
But still, thanks for bringing it over to the N1.
Updated OP to version 4.0.0.0.
Has anyone discovered what's the problem with restoring nanodroid backups with romracer's Recovery?
I see many of us have the same problem, restore work almost fine, it restores the operational system, but does not restore accounts and applications...
Edit:
New information:
I created two new backups as i am trying different ROMs.
I created one for CM7 and tested the restore, everything works perfectly! All apps and accounts...
Also created one for nCrust, this one have the same problem as i reported, the system is there, but it lacks all applications and accounts...
I also noticed that the nanodroid file is 0 bytes for the cases where the error occurs, and 1kb in the case where it worked fine.
Thanks
BTW, i am not using Rom Manager...
I'm not having an issue at all. Did you use romracer's CWM to backup?
Sent from my MB860 using Tapatalk
I used it to backup and restore and it restored everything; apps and accounts included.
LordOfTheSnatch said:
I'm not having an issue at all. Did you use romracer's CWM to backup?
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Yes, i did!
I flashed the last romracer's CWM yesterday, and created the backup next...
There are other users with this problem as well, but i can't find a fix for that anywhere...
luizffgarcia said:
Yes, i did!
I flashed the last romracer's CWM yesterday, and created the backup next...
There are other users with this problem as well, but i can't find a fix for that anywhere...
Click to expand...
Click to collapse
Did you backup webtop (optional)? And upon selecting restore, are you trying to restore webtop?
luizffgarcia said:
Has anyone discovered what's the problem with restoring nanodroid backups with romracer's Recovery?
I see many of us have the same problem, restore work almost fine, it restores the operational system, but does not restore accounts and applications...
Thanks
Click to expand...
Click to collapse
I have backed up and restored twice already with no problems...what issues are you running into?
Swiftks said:
Did you backup webtop (optional)? And upon selecting restore, are you trying to restore webtop?
Click to expand...
Click to collapse
I did not selected webtop when created the backup, and did not selected the webtop upon restore.
I was actualy trying to restore everything i had installed, but i don't use webtop that much, so i decided not to include it...
gpagador said:
I have backed up and restored twice already with no problems...what issues are you running into?
Click to expand...
Click to collapse
The issue is that when i restore the backup, i get a clean Gingerbread, without any of my previously installed applications or accounts!
you aren't doing a wipe cycle after the restore are you?
diedemus said:
you aren't doing a wipe cycle after the restore are you?
Click to expand...
Click to collapse
LOL!!
No
New information:
I created two new backups as i am trying different ROMs.
I created one for CM7 and tested the restore, everything works perfectly! All apps and accounts...
Also created one for nCrust, this one have the same problem as i reported, the system is there, but it lacks all applications and accounts...
I also noticed that the nanodroid file is 0 bytes for the cases where the error occurs, and 1kb in the case where it worked fine.
Any suggestions?
Any ideas? Noone experiencing this issue??
luizffgarcia said:
Also created one for nCrust, this one have the same problem as i reported, the system is there, but it lacks all applications and accounts...
I also noticed that the nanodroid file is 0 bytes for the cases where the error occurs, and 1kb in the case where it worked fine.
Any suggestions?
Click to expand...
Click to collapse
I'm also running piCRUST (v0.7) and romracer's CWM recovery 3.2. I will try this and report back the results.
P.S. would help us if you gave ROM, kernel, and recovery versions, etc. Thanks...
i just now did a backup and restore from within romracer's v3.2 recovery and all my post-piCRUST install tweaks are still in place. WiFi even came right back up with my WPA2 connection as it was before I rebooted for the test.
Of course, if the recovery actually did nothing at all then this behavior is expected.
Seriously, this part of the recovery is probably lifted wholesale from the codebase before romracer got involved, with the exception of being able to choose the external SD card for backup storage. That's what I did this first time. Now for another test, but this time I will backup to the internal card.
BRB...
---------------
No problems either with a backup and restore to/from the internal SD card. I just stepped through the recovery menu and chose all the defaults except for the webtop part.
Looking forward to your report of installed versions OP. When you boot into the recovery the very first line should say:
"CWM-based Recovery v4.0.1.4-atrix3.2"
Is this what you see?
luizffgarcia said:
There are other users with this problem as well, but i can't find a fix for that anywhere...
Click to expand...
Click to collapse
I haven't seen a lot of complaints about this myself, but up until now I've only been monitoring romracer's original post in the dev section. Can you point us to another thread where this is mentioned?
Not doubting you, I'd just like to see if there's some pertinent info about this issue that we're missing. Thanks...
Also, if you are choosing an Advanced Restore, please tell us exactly what options you are selecting, as they are described in the recovery menu itself (e.g. not "accounts", etc.). Thanks again...
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.
I recently decided to try MROM (I currently have CM7) so I backed up my current ROM and installed MROM. When I tried to check if I could restore my previous ROM, ROM Manager did not list my latest backups, but instead, listed some really old backups. I checked the clockworkmod folder to see if the latest backups were there and they were. Now, for some reason, ROM Manager was looking in the emmc folder, and not the sdcard (where the latest backups were) and I don't know if there's a way to change where it looks for the backups. I changed the settings to use an external sdcard (I don't know if that would help but I tried) and it didn't help. I then booted into recovery and tried the restore option there and I was able to see my latest backups.
I'm not sure why ROM Manager was unable to see them but booting in recovery worked fine. I want to try MROM (and I know I can restore from the recovery console if I really have to) but I just want to understand why this was happening and if there was another way to restore my backups (ROM Manager saves backups in ext3.tar format and I don't know how to use that with adb).
Don't bother with rom manager. I always get rid of it on every cm rom I try. Its pointless. Your recovery works and its a better option IMO.
Thanks! I would still like to know what's going wrong though, if possible, and also if there's a way to restore a backup saved in ext3.tar format using adb.
mrcountdookoo said:
Thanks! I would still like to know what's going wrong though, if possible
Click to expand...
Click to collapse
Hard to tell. You may never find out. ROM Manager can indeed be weird like that, and is in my opinion unreliable.
mrcountdookoo said:
and also if there's a way to restore a backup saved in ext3.tar format using adb.
Click to expand...
Click to collapse
The backup is a regular TAR archive (as the name suggests). Most recoveries contain the tar tool which you can use to restore the backup.
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!