Related
Ive been spending way to much time researching my problem and my wife is really mad at me. Basically at this point i would be happy to just manually extract data for about 10 apps from a nandroid that wont restore. Can someone point me in the right direction please?
Edit:
Ok, now that I am at computer, heres my story. Prior to flashing the gingerbread leak, I backed up using Titanium Backup and made a Nandroid backup. Somehow, all the files backed up in my PREVIOUS 2 backups on titanium backup where all 0kb-10kb, so they were completely borked for some reason. Some old backups of apps that I have since uninstalled still remained and those seem ok.
Prior to reading about the SD card failures with the gingerbread leak, I backed up my SD card to my computer. Only 1 error came up during the backup about a file with a name that was too long. I clicked on ignore and finished the backup. About 1 hour later my SD card fried.
I used a spare sd card, and transfered my clockwork mod folder and a few other folders to it. I then ODIN a DL09 stock image, flashed the newest Clockword mod 3.xx via odin, flashed UKB 2.0, then flashed PBJ -50 recovery/kernel (which was what I had when I made the backup) and tried to restore it. When I try to restore it hangs somewhere in the data restore portion saying CACHE. I saw it flash cache a few times during the restore, so I am not sure why it hangs on that one in particular. I know that the cache image file is only 16.5kb so I dont know if that has something to do with it.
I then installed the newest IMNUTS recovery since I heard there were problems restoring the the PBJ recovery, and it seems to hang in the same spot.
At this point, I have a few of my old programs back, but most force close.
My main goal here is to just extract some gamesave progress and a few other pieces of data (I can redownload basically all the apps I need), run clean until a better gingerbread leak comes along, then use titanium backup to backup what I have (and verify the backups and make backups of the backups )and install a better gingerbread rom.
So anyway, If i can figure out how to go into the datadata.img files, I guess I can extract the data I need and push it through ADB or ROOT EXPLORER? Should that work?
- nevermind...
There are computer applications that can read and explore image files, or .img files, and the file systems within image files. Your best bet would be software like that, that could open, edit, and explore image files. I dont know the names of any software like that, even though I have come across some before, but im sure you could turn up some results with the query "image file editor," or ".img file editor." From there you're just have to feel your way through.. Try similar queries if those don't turn up what you need, etc. If you got an app that could explore image files, then you could get your .apk files from /data/app folder, and any other data you might need from /data/data, if its just user apps you're wanting to restore.
Sent by way of unspeakably black magic.
ssmaster said:
Ive been spending way to much time researching my problem and my wife is really mad at me. Basically at this point i would be happy to just manually extract data for about 10 apps from a nandroid that wont restore. Can someone point me in the right direction please?
Edit:
Ok, now that I am at computer, heres my story. Prior to flashing the gingerbread leak, I backed up using Titanium Backup and made a Nandroid backup. Somehow, all the files backed up in my PREVIOUS 2 backups on titanium backup where all 0kb-10kb, so they were completely borked for some reason. Some old backups of apps that I have since uninstalled still remained and those seem ok.
Prior to reading about the SD card failures with the gingerbread leak, I backed up my SD card to my computer. Only 1 error came up during the backup about a file with a name that was too long. I clicked on ignore and finished the backup. About 1 hour later my SD card fried.
I used a spare sd card, and transfered my clockwork mod folder and a few other folders to it. I then ODIN a DL09 stock image, flashed the newest Clockword mod 3.xx via odin, flashed UKB 2.0, then flashed PBJ -50 recovery/kernel (which was what I had when I made the backup) and tried to restore it. When I try to restore it hangs somewhere in the data restore portion saying CACHE. I saw it flash cache a few times during the restore, so I am not sure why it hangs on that one in particular. I know that the cache image file is only 16.5kb so I dont know if that has something to do with it.
I then installed the newest IMNUTS recovery since I heard there were problems restoring the the PBJ recovery, and it seems to hang in the same spot.
At this point, I have a few of my old programs back, but most force close.
My main goal here is to just extract some gamesave progress and a few other pieces of data (I can redownload basically all the apps I need), run clean until a better gingerbread leak comes along, then use titanium backup to backup what I have (and verify the backups and make backups of the backups )and install a better gingerbread rom.
So anyway, If i can figure out how to go into the datadata.img files, I guess I can extract the data I need and push it through ADB or ROOT EXPLORER? Should that work?
Click to expand...
Click to collapse
unfortunately, you won't likely receive much sympathy posting a question in the development section. Please post your question in the Q & A section and you'll get some help. Just a friendly heads up.
Sent from my SCH-I500 using XDA Premium App
Well I'll go ahead and point you to the right direction, or what I'd imagine should work for your needs. You'll need unyaffs, I'm assuming you're on windows so this here would be the right one for you http://www.box.net/shared/1eighqsh4s. Now take the data.img from your clockwork backup on your sdcard, drag and drop it onto the unyaffs.exe, it should unpack right there into a crapload of files. Navigate to the /data folder and find the ones you want to keep (they should be listed by the package name for the apps, "com.blah.asfkje.etc" rather than the name of the app so keep that in mind when looking for what you want), then adb push (root explorer would be fine too) the folders into your phone where they should be.
Headcase8911 said:
unfortunately, you won't likely receive much sympathy posting a question in the development section. Please post your question in the Q & A section and you'll get some help. Just a friendly heads up.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
Sorry I posted this in the wrong forum, I was waiting for the train when I posted and wasn't thinking too straight. How can I move it?
ssmaster said:
Sorry I posted this in the wrong forum, I was waiting for the train when I posted and wasn't thinking too straight. How can I move it?
Click to expand...
Click to collapse
The mods will move it once they notice.
Another Fascinating post by my XDA app...
Just curious because of my personal interest...
Did you happen to try the nandroid Advanced Restore option, and select Data only? If not, it might be worth a shot. If it gets far enough, you might try wiping after the restore, and before booting up.
I always wipe my cache/Dalvik before I backup, to try to avoid conflicts with possible future ROMs. Something to think about, anyway.
Sorry about the trouble.
ssmaster said:
Sorry I posted this in the wrong forum, I was waiting for the train when I posted and wasn't thinking too straight. How can I move it?
Click to expand...
Click to collapse
Report your post stating that it should be moved, and the mods will notice right away.
Robtao said:
Just curious because of my personal interest...
Did you happen to try the nandroid Advanced Restore option, and select Data only? If not, it might be worth a shot. If it gets far enough, you might try wiping after the restore, and before booting up.
I always wipe my cache/Dalvik before I backup, to try to avoid conflicts with possible future ROMs. Something to think about, anyway.
Sorry about the trouble.
Click to expand...
Click to collapse
i did try the nandroid advanced data only option and it hung at what seemed to be the exact same point.
I was attempting to mod my build prop to look as the phone was a different phone. Well, like an idiot. I deleted it all together from the system folder. But, I did make a copy of it. But, My phone goes into a boot loop. Any ideas as to how i can push the backed up build prop to my system folder? I can get into CWR. if this helps.
[Edit] So, here is what I have tried so far.
While in CWR I made a Nandroid backup of the broken system. Then i connected the phone to my computer. And i copied all of my Nandroid backups over to it. A little info on my backups. The ROM that I was running before I killed it was BAMF SoAb 1.04. I had made a backup of that ROM when i first installed it. So I opened the good Nandroid and extracted the build prop from that. Then i went into the broken ROM and did and Un RAR of the system folder. I then took the build prop and inserted it into the system folder. I attempted to Re RAR it. But, I keep getting error messages. So, what i am looking for is a fool proof way to Re RAR/ZIP or what ever is the best course of action in my case.
So, I might as well give the answer that I was not looking for to the question. But non the less it did work. So, this is what I had to do to get it back to what looks like the working version of the ROM that I broke.
What I did was an advanced restore. I would suggest one thing that every one do. Once you load a ROM onto your phone and you see that all the basics are working. I would do a Nandroid of that ROM. That way in the future, you will have the base to build off of if something goes wrong in a mod.
If you never did a Nandroid of the ROM when you first loaded it. I would suggest downloading or finding the copy of the ROM in question. Installing it on the phone and then doing a Nandroid of it.
So, lets say that you make it so that you can not boot into your current ROM after doing something dumb like. I don't know, like deleting the build prop file. LOL
Here are the steps that I took after semi bricking this thing.
Step one- Boot into clockwork recovery
Step two- Make a Nandroid of the ROM that you broke. Reason being is because that ROM is set up just the way that you like it.
Step Three- Go to mounts and storage then mount USB storage and backup everything you deem important for that just in case scenario. But most importantly, backup the nandroids that are in your clockwork folder.
Steep Four- Go to wipe data/factory reset and after that wipe the cache partition
Step Five- Go to backup and restore. Select advanced restore and select the original just out of the box ROM that you had made a back up of when you first loaded it to your phone. Select restore system. After that restore has completed back out of there.
Step Six- Select backup and restore again. Then advanced restore again. Now select the ROM that you had broken. Select restore boot,data and cache. Do not select system. That part of the image in this case is broken.
After you have completed these steps boot the phone. You should be good to go. I know that I am now. I know that depending on what it is that you broke will depend on what you do and do not load to your phone through the advanced restore options. But I suppose if we did things correctly . Like making a Nandroid before we went messing with things, we would not have had to go through this in the first place. But, some of us get a little to impatient at times and jump the gun. Any way, lesson learned. Well at least for now.
I would hope that no one has to look for a post such as this. Because it most likely means that you are going insane looking for ways to get back all that you have lost. I know that I was a bit irked. And I literally spent all day looking for help. And to no avail. So I decided to experiment with things. Luckily, I had the patience to not give up. Now I am right back to where I started before I messed the phone up. Oh by the way. I suggest making a backup now. You don't want to have to do this again. Not that it was hard or anything. But do the smart thing and save your self a hand full of steps and time. If I had done the proper thing last night. I would have been able to go to work today. Yes, me working is dependent on me having my cell. Why? Because, I use tethering on my Thunderbolt to connect my Xoom to the internet. And Google maps is in need of data to work properly. And i drive allover New England. Any way, enough about me. I hope this was helpful to whom ever found this.
recovery just says something is wrong, look at log?
I tried a few versions (of the backup sets), same error.
What am I doing wrong? How do I fix it? :crying:
Log from recovery run...
Starting recovery on Thu Aug 16 21:58:52 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
RA Revamped
Build : RA-VIGOR-v3.15-getitnowmarketing
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
fuzzynco said:
recovery just says something is wrong, look at log?
Click to expand...
Click to collapse
This happens all the time to people.
You can't simply restore a backup from another device because then your new device will actually appear as your old device on Google and Verizons servers, which will cause all sorts of problems if Verizon were to ever successfully restore your old phone and try and send it off to someone else. To avoid this problem, the recovery won't even let you restore a backup from another phone, even if its the exact same hardware.
Go to play.google.com, go to view your devices in the settings section. You should see two Rezounds. One will have been activated in the past, and one whenever you first turned on your replacement after receiving it and logging in with your account. So the one that was activated in the past is clearly your original Rezound that you've returned. You can give it a name, like "DEAD REZOUND" so that you know by looking at the name which Rezound Google thinks you're using.
There is a workaround that will let you restore the backup anyway if you want to search for it, but I highly recommend you don't. If you do, you can then go to play.google.com again, view your existing devices in the settings section, and you'll see that Google thinks your new phone is the same one you just sent back to Verizon. It should show "DEAD REZOUND" as being registered again today (or whatever day you successfully restored a backup from your old phone)
To sum up: Don't restore a backup from another Rezound. You pretty much have to start over again.
I kind of follow... RA is an image backup
so it would duplicate the serial and device specific data.
I could do a TiBu of the user apps and data (and the
new xml files of the call log and sms's), though.
Use an app to export the calendar data to an
.ics (iCal file) and the phone book to a .vcf
for import on the 'new' phone.
Since Google added some 800+ empty
phone book entries and messed up my phone
book, I don't sync with it. I export the whole
thing to a vcf.
So the missing /dev/tty0 device file
error from the restore is just AR not
letting me shot myself in the foot,
right?
I'll need to install my ROM, then
restore the user apps and data
from TiBu then rebuild my 'desktop'?
Is it worth doing the RUU for ICS
to get there? The new phone was
offered the upgrade OTA, but I think
it was wiped by the unlock prior to
S-Off process. Would I flash
the ICS RUU, then flash the ICS/JB
hboot, to get fastboot commands,
then reflash recovery?
I have seperate micro cards for
the 600mb RUU zip and the
ICS firmware/radio/hboot(JB)
zip.
I'm thinking since I have to rebuild
the desktop anyway, maybe doing
the ICS RUU first is a good idea.
fuzzynco said:
so it would duplicate the serial and device specific data.
I could do a TiBu of the user apps and data (and the
new xml files of the call log and sms's), though.
Use an app to export the calendar data to an
.ics (iCal file) and the phone book to a .vcf
for import on the 'new' phone.
Since Google added some 800+ empty
phone book entries and messed up my phone
book, I don't sync with it. I export the whole
thing to a vcf.
So the missing /dev/tty0 device file
error from the restore is just AR not
letting me shot myself in the foot,
right?
I'll need to install my ROM, then
restore the user apps and data
from TiBu then rebuild my 'desktop'?
Is it worth doing the RUU for ICS
to get there? The new phone was
offered the upgrade OTA, but I think
it was wiped by the unlock prior to
S-Off process. Would I flash
the ICS RUU, then flash the ICS/JB
hboot, to get fastboot commands,
then reflash recovery?
I have seperate micro cards for
the 600mb RUU zip and the
ICS firmware/radio/hboot(JB)
zip.
I'm thinking since I have to rebuild
the desktop anyway, maybe doing
the ICS RUU first is a good idea.
Click to expand...
Click to collapse
In reply to the bolded part: Basically, yes. AR's nandroid places the backups in a folder with your phone's serial as the folder name. Attempting to restore any backup from a folder with any other name will fail to prevent the issues I mentioned above.
I do not and have not ever used Titanium Backup, so in regards to that, I can't be of any help.
If you have a linux machine, you can mount the data.img from any of your backups and then copy all the files from /data/app and data/data to your phone. This will restore most of your apps, and app data/settings. There will still be a few things you'll have to redo from scratch, and this may not work 100% for every app on your phone, but at least this way you don't have to redownload every single app and manually redo all your settings...
I did the RUU zip (it restarted itself, as expected), the firmware/radio/hboot(JB) zip
and then reflashed AR 3.15 from fastboot. Everything seems to be working now.
Do you know if the debloat script (freeze VZW apps) works for ICS OTA ROM?
fuzzynco said:
I did the RUU zip (it restarted itself, as expected), the firmware/radio/hboot(JB) zip
and then reflashed AR 3.15 from fastboot. Everything seems to be working now.
Do you know if the debloat script (freeze VZW apps) works for ICS OTA ROM?
Click to expand...
Click to collapse
not sure...
I couldn't get ViperROM 1.0.3 to not crash (com.android.phone kept crashing).
Trying a couple of others that are prerooted and deboated. So far the ICS &
Sense 3.6 looks fine. Still have the 'social network' stuff to freeze though,
Could I do something like make a zip (from adb shell) of the user apps
/data/app & /data/data directories (to preserve the unix permissions).
and leave that on fat32 sd card? Then merge that into the zip for the
rom to be installed so the installer will reload them?
Would I need to add lines to the installer script to have it load /data (with
the subdirs ../app and ../data)?
hmms maybe better to make a seperate zip to preinstall my saved
/data subdirs? Can I copy the ROMs installer binary and build
a installer script to mount /data, then install the /data directory,
umount /data?
a.mcdear said:
This happens all the time to people.
You can't simply restore a backup from another device because then your new device will actually appear as your old device on Google and Verizons servers, which will cause all sorts of problems if Verizon were to ever successfully restore your old phone and try and send it off to someone else. To avoid this problem, the recovery won't even let you restore a backup from another phone, even if its the exact same hardware.
Go to play.google.com, go to view your devices in the settings section. You should see two Rezounds. One will have been activated in the past, and one whenever you first turned on your replacement after receiving it and logging in with your account. So the one that was activated in the past is clearly your original Rezound that you've returned. You can give it a name, like "DEAD REZOUND" so that you know by looking at the name which Rezound Google thinks you're using.
There is a workaround that will let you restore the backup anyway if you want to search for it, but I highly recommend you don't. If you do, you can then go to play.google.com again, view your existing devices in the settings section, and you'll see that Google thinks your new phone is the same one you just sent back to Verizon. It should show "DEAD REZOUND" as being registered again today (or whatever day you successfully restored a backup from your old phone)
To sum up: Don't restore a backup from another Rezound. You pretty much have to start over again.
Click to expand...
Click to collapse
not really. im on my third rezound and i restored the same viper rom i had before.
this is what i did with AR
1. back up current rom
2. boot into rom
3. use root explorer and find the nandroids
4. noticed 2 folders in the same nanadroid folder ( light bulb)
5. move old back up to the location where the new one was.
6. boot into recovery and did a full wipe
7. restored old back up.
8 boot phone
9. BAM!
This app might work. I use it and it works great but I'm not sure if it restores data.
synisterwolf said:
not really. im on my third rezound and i restored the same viper rom i had before.
this is what i did with AR
1. back up current rom
2. boot into rom
3. use root explorer and find the nandroids
4. noticed 2 folders in the same nanadroid folder ( light bulb)
5. move old back up to the location where the new one was.
6. boot into recovery and did a full wipe
7. restored old back up.
8 boot phone
9. BAM!
Click to expand...
Click to collapse
Yeah this works perfectly fine, but can cause the new phone to register on the network as if it were the old one. It is perfectly possible to restore a backup from another phone, and it works fine... its just a bad idea because if your old phone is ever "recovered" and turned back on, VZW might see two identical devices on the network, which will cause problems in the future.
a.mcdear said:
Yeah this works perfectly fine, but can cause the new phone to register on the network as if it were the old one. It is perfectly possible to restore a backup from another phone, and it works fine... its just a bad idea because if your old phone is ever "recovered" and turned back on, VZW might see two identical devices on the network, which will cause problems in the future.
Click to expand...
Click to collapse
Good to know. Thanks
In my case, the backup is from a device that i bricked totally. couldnt get into download mode so im thinking they will just use it as parts
Sent from my iPhone...
I rooted my xperia x10 mini around a year ago, and all was fine. I recently unlocked the bootloader, and decided to try flashing a new rom and kernal as Sony refuse to do any further updates. I backed everything up on titanium back up, videos, contacts, apps etc. And also followed the instructions to do full back up when I flashed the new rom. I followed everything to the letter, but when the new rom was installed, I could find no contacts, music, apps or anything? I thought the best option was to use cwm and restore back? That looked as if it had gone ok, but there was a message at the end to say something? img? could not be found, and it didn't revert back, just hung at nAa screen, and would do nothing else.
After reading a few threads, I thought I'd go back to SE stock firmware - better than a dead phone! But although the sd card is showing all my back ups, including titanium back up, nothing is showing in the phone apps, or folders, all my contacts are missing, pictures, notes, everything :crying:
How do I get everything back to where it shoud be?? It may be a stupid question, but I hope you can offer some advice please.
The phone is rooted again. Thanks in advance from a newbie flasher
Did you restore your backup using Titanium again then?
The other way is to do advanced restore from CWM and choose data only.
SmG67 said:
Did you restore your backup using Titanium again then?
The other way is to do advanced restore from CWM and choose data only.
Click to expand...
Click to collapse
I wasn't sure how to restore from Titanium, but I've now downloaded Titanium backup app, and it has restored some of the things I lost, not everything :crying:
It hasn't restored any of my text messages and I have quite a lot of pictures missing. Is there anyway to get messages or pictures back?
Thanks :fingers-crossed:
alittleblonde said:
I wasn't sure how to restore from Titanium, but I've now downloaded Titanium backup app, and it has restored some of the things I lost, not everything :crying:
It hasn't restored any of my text messages and I have quite a lot of pictures missing. Is there anyway to get messages or pictures back?
Thanks :fingers-crossed:
Click to expand...
Click to collapse
Pictures are usually stored on the sd-card, so they won't get affected if you change your rom or kernel, not sure what happened with that, but the best way to get everything back would be to use CWM and choose advance restore to get your data back I suppose, it will restore everything that was on internal memory.
The reason you got stuck at the nAa-kernel logo when you restored from cwm previously is because you also restored your old rom, which doesn't run with the nAa-kernel.
the protelli
SmG67 said:
Pictures are usually stored on the sd-card, so they won't get affected if you change your rom or kernel, not sure what happened with that, but the best way to get everything back would be to use CWM and choose advance restore to get your data back I suppose, it will restore everything that was on internal memory.
The reason you got stuck at the nAa-kernel logo when you restored from cwm previously is because you also restored your old rom, which doesn't run with the nAa-kernel.
Click to expand...
Click to collapse
Thanks for your reply. I got most of the pictures back, but some seem to have vanished, and something a little weird happened, as in my photo gallery, I now have pics of little android men, a tick, camera, tools etc Guess I should just delete them??
Do you know of any way to get text messages back?
alittleblonde said:
Thanks for your reply. I got most of the pictures back, but some seem to have vanished, and something a little weird happened, as in my photo gallery, I now have pics of little android men, a tick, camera, tools etc Guess I should just delete them??
Do you know of any way to get text messages back?
Click to expand...
Click to collapse
It may be that just the thumbnails of those pictures are messed up, not the pictures itself. I would suggest copying your pictures to a folder on your computer, deleting them from sd-card and open the gallery, so it can update it's thumbnails (it will delete them all). If you then move back your pictures to your sd-card it will generate proper thumbnails again.
The txt-messages should be in your CWM-backup.
I don't know if you had CWM installed on your phone before you flashed the kernel, and what kernel you used when you made the backup. It can be a bit tricky if you tried JellyBean, but not impossible. I need a bit more information from you to be sure about how to go about that.
SmG67 said:
It may be that just the thumbnails of those pictures are messed up, not the pictures itself. I would suggest copying your pictures to a folder on your computer, deleting them from sd-card and open the gallery, so it can update it's thumbnails (it will delete them all). If you then move back your pictures to your sd-card it will generate proper thumbnails again.
The txt-messages should be in your CWM-backup.
I don't know if you had CWM installed on your phone before you flashed the kernel, and what kernel you used when you made the backup. It can be a bit tricky if you tried JellyBean, but not impossible. I need a bit more information from you to be sure about how to go about that.
Click to expand...
Click to collapse
Hi. Yes, I installed CWM before hand, and did a complete back up, I used the miniCM7 robyn rom and the nAa-2.6.29.6-nAa 14 kernal. I had considered jelly bean, but thought I'd just start with this one, before working my way up! Someone suggested ST15i 4.2.0.A.62 but it didn't sound right for the X10mini? I only bought the phone 18 months ago, so its a shame there are no further updates.
I did try to restore through the advanced setting on cwm, but it didn't work, I had the same message as before about something being missing.
I noticed another thread about a similar problem, a mismatch between numbers?? Not too sure, but it sounded similar to the problem I had.
At least I have back most of my pictures Thanks for your help.
alittleblonde said:
Hi. Yes, I installed CWM before hand, and did a complete back up, I used the miniCM7 robyn rom and the nAa-2.6.29.6-nAa 14 kernal. I had considered jelly bean, but thought I'd just start with this one, before working my way up! Someone suggested ST15i 4.2.0.A.62 but it didn't sound right for the X10mini? I only bought the phone 18 months ago, so its a shame there are no further updates.
I did try to restore through the advanced setting on cwm, but it didn't work, I had the same message as before about something being missing.
I noticed another thread about a similar problem, a mismatch between numbers?? Not too sure, but it sounded similar to the problem I had.
At least I have back most of my pictures Thanks for your help.
Click to expand...
Click to collapse
hmm, it sounds almost like your sd-card is experiencing some problems, maybe you could copy the whole thing to your computer and reformat it. but i don't think the backup will be valid anymore.
The number mismatch is the md5-checksum, The backup calculates a number when the backup is created, which is stored alongside your backup.
The restore function then uses the same method to create a checksum from the backup-file and compare it to the number created when the backup was made. If they don't match, the most likely option is a corrupt backup file, which is a pain.
And no, the st15 is the 2011 xperia mini i think, you better stick with E10-kernels and robyn-ROMS for the x10mini (if it doesn't have a hardware keyboard)
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!