Related
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted!
I copied the modified 3e recovery into the correct place and rebooted. I than downloaded rom mngr and installed i9000.
I get that error message when I boot into clockworkmod.
what am i doing wrong? Thanks.
I have samsung infuse 4g ATT.
You're skipping ahead. Go back to 3E, drop the modded 3E recovery in the right location, reboot into recovery, install packages (twice, if necessary), and then you can work on getting CWM.
Thankfully I got it to work.! Thanks.
I am having the same issue. When I dropped the modified 3e into the phone and tried to copy and paste it in it replaced my old recovery even though I renamed it. I am thinking this was a mistake? Other then that I when I am in recovery I re-install packages and get the verification error.
jnwhatle said:
I am having the same issue. When I dropped the modified 3e into the phone and tried to copy and paste it in it replaced my old recovery even though I renamed it. I am thinking this was a mistake? Other then that I when I am in recovery I re-install packages and get the verification error.
Click to expand...
Click to collapse
Did you have the system directory mounted to allowed R/W? If you don't allow that, it won't change anything. I would suggest renaming the old recovery file and then pasting in the modified one. Don't just paste it over the other one. This way you know the process completes properly.
Remember to set the read/write privileges though or it won't work.
Depending on what your plans are, you could always use Odin to go back to stock with the modified recovery preinstalled if you use h8rift's Odin files that are available in Development.(Mind you this method will wipe all of your system files though and put you back to stock. So, if you are wanting to keep what you have, but just modify the recovery, I would suggest the other route.)
I am fairly confident that I am mounted as read/write. As far as what you are saying as not just copying and pasting it, that is one thing that confuses me. I have tried various methods to get the verified recovery onto the phone. The most recent was using drop box. I used root explorer>copied recovery from dropbox>went to system/bin> renamed old recovery recovery.orig> and pressed paste. In various youtube videos I watched it would just paste next to the old recovery.orig, but mine would then proceed to ask if I wanted to overwrite the old one, and I said yes. I am hoping I did not mess things up.
jnwhatle said:
I am fairly confident that I am mounted as read/write. As far as what you are saying as not just copying and pasting it, that is one thing that confuses me. I have tried various methods to get the verified recovery onto the phone. The most recent was using drop box. I used root explorer>copied recovery from dropbox>went to system/bin> renamed old recovery recovery.orig> and pressed paste. In various youtube videos I watched it would just paste next to the old recovery.orig, but mine would then proceed to ask if I wanted to overwrite the old one, and I said yes. I am hoping I did not mess things up.
Click to expand...
Click to collapse
Use this instead easy peezy
http://forum.xda-developers.com/showthread.php?p=14053463
infuse.....infused.......infusion.......
That will root ya and install 3e
Fyi I would download rom you want and then.do that method once ur in cwm install rom boom
infuse.....infused.......infusion.......
I extracted all my files from my data.img backup and made it into a .zip. Is there anyway
i can cwm flash that data.zip to get all my data back? I tried just flashing the zip and it says,
"(bad) Installation Aborted."
Any help would be greatly appreciated
mafo5000 said:
I extracted all my files from my data.img backup and made it into a .zip. Is there anyway
i can cwm flash that data.zip to get all my data back? I tried just flashing the zip and it says,
"(bad) Installation Aborted."
Any help would be greatly appreciated
Click to expand...
Click to collapse
Here's a few things you could do assuming that what you want is even in this zip file.
1) Get a working cwm format zip file and take a close look at it because you need to use it as a template if this is going to work. In particular, check out updater-script in META-INF\com\google\android\*. Updater-script is what directs the restore operation so it needs to match what you want to do. You can get the idea by looking at one that restores say, some data or system files, like a kernel will always restore some /system/lib/module files.
2) Since you've got some sort of zip file, make sure it matches the general format of a working cwm zip file and then just make sure step 1) is right.
3) I don't know if this is still a search for .android_secure folder on /sdcard, but if it is you're probably not going to get there from here, because the tf101 generallyl doesn't have that file since there's no need for tf101 -> sdcard app storage. For example, mine never had that folder either on internal or external storage.
4) Kernels aren't in the data or system archives from cwm, so that is possibly some sort of show-stopper too. I'm working on the cwm source today a bit to try to create a boot.img (or in the newer cwm lingo, boot.*.tar) archive. That archive will use blob and boot tools to be able (via the direction in updater-script) burn the blob onto block m*4.
I hope that helps.
Oh yeah, another thing you can try: If you wanted just the 'apps' from the cwm archive, you shouldn't even need the zip file. All you need to do is run Titanium Backup (assuming you've got it or can get it), and use the new feature in options called restore from cwm backup (or something like that). I've used it and it works fine on 3.x and 5.x cwm backups.
-- good luck
hachamacha said:
Here's a few things you could do assuming that what yowant is even in this zip file.
1) Get a working cwm format zip file and take a close look at it because you need to use it as a template if this is going to work. In particular, check out updater-script in META-INF\com\google\android\*. Updater-script is what directs the restore operation so it needs to match what you want to do. You can get the idea by looking at one that restores say, some data or system files, like a kernel will always restore some /system/lib/module files.
2) Since you've got some sort of zip file, make sure it matches the general format of a working cwm zip file and then just make sure step 1) is right.
3) I don't know if this is still a search for .android_secure folder on /sdcard, but if it is you're probably not going to get there from here, because the tf101 generallyl doesn't have that file since there's no need for tf101 -> sdcard app storage. For example, mine never had that folder either on internal or external storage.
4) Kernels aren't in the data or system archives from cwm, so that is possibly some sort of show-stopper too. I'm working on the cwm source today a bit to try to create a boot.img (or in the newer cwm lingo, boot.*.tar) archive. That archive will use blob and boot tools to be able (via the direction in updater-script) burn the blob onto block m*4.
I hope that helps.
Oh yeah, another thing you can try: If you wanted just the 'apps' from the cwm archive, you shouldn't even need the zip file. All you need to do is run Titanium Backup (assuming you've got it or can get it), and use the new feature in options called restore from cwm backup (or something like that). I've used it and it works fine on 3.x and 5.x cwm backups.
-- good luck
Click to expand...
Click to collapse
OK Ill see if the titanium backup way works. I'll report back to you if it works. Also if I do get all my apps back is there a way to get the app data?
Hi - If Titanium is bringing up the selections screen then the usual choices for each app are data/app/data+app, so yes.
The titanium back option is called "extract from Android backup" I can't do
It right now because I don't have my tf with me. But I don't think it will work because
The Android backup I made was currupted. I would get the .android_secure error
And couldn't restore. So if titanium takes the data.img from my Android I'm thinking
It won't work but if I can give it the zip it probably will. I won't be home for a couple
Hours.
thank you so much i got all my stuff back using titanium backup!
mafo5000 said:
thank you so much i got all my stuff back using titanium backup!
Click to expand...
Click to collapse
Cool! --
Congrats.
Hey all. I did something silly and deleted a file in system/bin folder while troubleshooting a problem. I made a backup of the file before deleting it in sdcard/download but my phone wont boot so I can copy the backup file back to system/bin. I am able to get my phone into download mode and I believe I could copy the file via adb. However I do not know how to get adb to recognize the phone in download mode. I type...
adb devices
and it states "List of devices attached" and there is nothing under the list but when I plug my phone via USB it shows "SAMSUNG Mobile USB CDC Composite Device" in device manager so I know my pc is recognizing it. I have used adb before with batch files like 1click root and things like that so I know its just me not knowing the right commands to get my device recognized.
Any and all help is appreciated! I just need to copy 1 file from sdcard/download to system/bin and I would assume it would boot back up with no problem!
Thanks!
do u have cwm installed?
I just installed CWM v5.5.0.4 via download mode using this method. http://www.theandroidsoul.com/skyrocket-root-clockworkmod-cwm-recovery/
So now that I am in CWM I am trying to mount things like /system and it shows an error mounting /sdcard and I get that error messaging for mounting all except mount usb storage which works great. I was however able to get the file off my phone but now how do I get the file back to system/bin?
Yes.. you can (and really should) flash CWM from download mode via your PC/laptop. A few weeks ago I did something very similar and soft-bricked my SR by renaming an in-use file (framework-res.apk)... I also only had 3e, so couldn't just restore a nandroid or flash a rom zip. Go to the Dev section and find the thread by Copperhed ("Root the ATT SGH-I727 Skyrocket..."). read through the OP and follow instruction exactly. You will be Odin3 flashing just the CWM recovery partition... this will NOT trip your flash counter. If you are already rooted, you should retain root... if not, you can root via his OP. After you have CWM recovery, there's a way you can mount the sdcard so you can transfer files between your PC and SR... then, you can put the sbin file back and see if it reboots fine... if not, with CWM installed, you can flash (via zip.. not Odin) any rom/kernel/modem zip package you want.
Even though I installed CWM from a different source I thanked you anyways DoctorQMM! Now that I have CWM installed how to I transfer the file from my pc to the system/bin directory? I have been able to mount usb storage and it show up as a drive on my pc but when I mount /system nothing shows up. What am I missing?
Thanks for all your help! I am almost there! ^_^
hey, I recommended it first . Seriously though, download a kernel from the dev section, any kernel. Open it up in winrar, winzip, etc... and delete everything except the system folder. Now take the bin file u copied to ur computer and put it in a folder called bin. Put this bin in the kernel zip inside the system folder. Now delete everything else in the system folder. Put this file on a microsd, slip it in ur phone and flash it through cwm. this will put the bin back, and allow u to reboot phone
JDub... PM cdshepherd.... he's the one who shared with me you can use the mounts and storage option in cwm (then click "mount USB storage")... then you can copy files between your sd and computer without having to do what I did (which was pull external sd out of SR, mount in micro adapter, plugged into laptop and loaded files on the sd... then put sd back in phone.. booted into CWM and flashed the rom zip I put on there). Yes.. you are close! If you can't get that one file back to sbin on root, you could try to flash a stock rom/kernel zip (KK1 or LA3)... you only need to put that rom/kernel zip on your sd or external sd so CWM will see it.
icenight89 your right you provided the inspiration so I thanked you as well and appreciate the explanation. I will perform it now and see where I get. Let me understand this correctly in steps..
1. Download a kernel, any kernel.
2. Open it up, delete everything except the system folder.
3. Create a folder named bin and put the backed up file in the bin folder.
4. Delete everything else within the system folder except the bin file and bin folder. So it should be /system/bin/xxx.file
5. Put this on a microsd card and flash it through cwm. I assume I do this by selecting "install zip from sdcard?"
Thanks for the continual help! ^_^
I am having trouble with the kernel part. I downloaded a i727 kernel from here http://forum.xda-developers.com/showthread.php?t=1340114&page=2. Opened it up and it has boot.img in it. Am I missing something?
Alright. I downloaded the kernel from here http://www.mediafire.com/?85g701ate11zdc9. The kernel contained a folder named system and deleted everything else. I then added the folder bin and added the backed up file I deleted to the system/bin/ directory. I then mounted usb storage via CWM and put the new .zip in there. I then selected "install zip from sdcard", "choose zip from internal sd card" located the zip file and selected "yes." I then get the following read outs...
Installing update...
Installation aborted.
--Installing: /emmc/sgh-1727-skyrocket-att-original-kernel_2.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
So it looks like it is not installing. Am I doing something wrong?
wrong kernel, download this one:
http://faux.androidro.ms/sky-kernel-010b1.zip
delete everything from in there except system folder, including boot.img, and follow instructions again, should work
JDubbed said:
icenight89 your right you provided the inspiration so I thanked you as well and appreciate the explanation. I will perform it now and see where I get. Let me understand this correctly in steps..
1. Download a kernel, any kernel.
2. Open it up, delete everything except the system folder.
3. Create a folder named bin and put the backed up file in the bin folder.
4. Delete everything else within the system folder except the bin file and bin folder. So it should be /system/bin/xxx.file
5. Put this on a microsd card and flash it through cwm. I assume I do this by selecting "install zip from sdcard?"
Thanks for the continual help! ^_^
Click to expand...
Click to collapse
these steps are exact, nice
Unfortunately I get the same error message with the kernel you supplied. x.x
010b1.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
Are you sure I can just delete and add stuff like that and It will work? I mean it makes sense to me but since it keeps aborting there may be something crucial missing that I need to keep in the .zip file. Any ideas?
Here is a link of my modified zip. http://dl.dropbox.com/u/6778642/Android/sky-kernel-010b1.zip
pm me when u get a chance
JDubbed said:
Unfortunately I get the same error message with the kernel you supplied. x.x
010b1.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
Are you sure I can just delete and add stuff like that and It will work? I mean it makes sense to me but since it keeps aborting there may be something crucial missing that I need to keep in the .zip file. Any ideas?
Here is a link of my modified zip. http://dl.dropbox.com/u/6778642/Android/sky-kernel-010b1.zip
Click to expand...
Click to collapse
download a rom from Dev section. Doesn't matter which one. Try silvers rom you'll like it. Mount USB storage in cwm. Copy rom to sd. Eject SD from computer. Go back to main menu in cwm. Wipe data/factory reset. Wipe cache partition. Wipe dalvik cache(under advanced in cwm) format system under mounts and storage. Back to main menu in cwm. Install zip from sdcard. Choose zip(rom) you just placed on your SD. Flash it. Reboot device. Enjoy. And make a nandroid after it boots for the first time.
Sent from my SAMSUNG-SGH-I727 using xda premium
Did you make a cwm backup of rom you were using prior to this?
Sent from my SAMSUNG-SGH-I727 using xda premium
No, I did not make a nandroid backup. I had to install CWM from download mode and then I was able to get into CWM all without booting.
I appreciate your time in writing a solution however I am not interested in wiping everything and starting from scratch which is what your proposing. I simply deleted a file in system/bin named mediaserver so system/bin/mediaserver. When I rebooted the phone would not boot. I made a backup of the mediaserver before deleting it and placed it in the sdcard/download folder. All I need to do is copy the mediaserver file back to system/bin/ directory and phone should boot backup as if nothing ever happened. That's is how I understand it. Its just missing a file and I know what the file is and I have the file I just need to figure out how to copy it back over to where it belongs.
I do know how to install stock and other roms but after spending numerous hours on my first phone, SGS Captivate, to experience others roms like Darky's Rom the end result was that it was not worth me having to keep up with all the releases and bug fixes, loading in working kernels to make things work correctly and the like. I would rather just stick with stock. Its just a personal preference.
If anyone knows how to copy a file from my pc or from internal sdcard to my Skyrocket using Download mode or ClockWorkMod using any means but without wiping my data please let me know. Eventually if I do not get a solution I will be forced to revert back to the stock rom but I would rather leave that as a last resort.
I look forward to any other suggestions!
Thank you!
Without the ability to push/pull with adb your running out of solutions. I do hope that you get your skyrocket up and running no matter what method you use. And I do hope that someone with the ability comes along to help you. My way is prob the easy way out. If it were me ide cut my losses. Start from scratch, and try to figure out where my prob starts. Good news is there is a great community with plenty of help. Good luck mate.
Sent from my SAMSUNG-SGH-I727 using xda premium
Since my zip suggestion didn't work, try flashing a different kernel, romracer stockish 0.3 is a good choice, from cwm
JDubbed said:
No, I did not make a nandroid backup. I had to install CWM from download mode and then I was able to get into CWM all without booting.
I appreciate your time in writing a solution however I am not interested in wiping everything and starting from scratch which is what your proposing. I simply deleted a file in system/bin named mediaserver so system/bin/mediaserver. When I rebooted the phone would not boot. I made a backup of the mediaserver before deleting it and placed it in the sdcard/download folder. All I need to do is copy the mediaserver file back to system/bin/ directory and phone should boot backup as if nothing ever happened. That's is how I understand it. Its just missing a file and I know what the file is and I have the file I just need to figure out how to copy it back over to where it belongs.
I do know how to install stock and other roms but after spending numerous hours on my first phone, SGS Captivate, to experience others roms like Darky's Rom the end result was that it was not worth me having to keep up with all the releases and bug fixes, loading in working kernels to make things work correctly and the like. I would rather just stick with stock. Its just a personal preference.
If anyone knows how to copy a file from my pc or from internal sdcard to my Skyrocket using Download mode or ClockWorkMod using any means but without wiping my data please let me know. Eventually if I do not get a solution I will be forced to revert back to the stock rom but I would rather leave that as a last resort.
I look forward to any other suggestions!
Thank you!
Click to expand...
Click to collapse
Based on your first post, I don't think your pc is FULLY installed your device. Download mode requires additional drivers.........adb devices should return a serial number.
I have not tried adb on my skyrocket...I will do that for your sake and reply with my experience..
So I think I made a stupid mistake.
I was trying to reset google wallet and It hung at 97% and wasn't able to reset. I used the google wallet installer to basically change my build prop to the nexus build prop. I figured it would just overwrite my original wallet app anyway, and once my build prop was changed to the nexus build prop I could simply reset the app from there.
Anyways, phone rebooted and it's stuck in a bootloop and isn't getting passed the boot animation screen. I can get into recovery mode and download mode just fine. I tried restoring a backup I had with CWM and it says "md5 mismatch error". I really have no idea what to do at this point, and would rather not go completely to stock since I know my data is still there. Also I'm concerned to even restore a backup because i'm pretty sure my build prop was changed. I'm also wondering if it would be possible to simply factory reset and flash a new rom on top of it.
Any help would be greatly appreciated.
which rom are you using?
extract its build.prop and flash manually (if you know how to create a flashable zip)
if you are using a cm based rom, just reflash the rom without deleting anything..
and avoid using space while renaming backups... it gives md5 mismatch error
Khizar Amin said:
which rom are you using?
extract its build.prop and flash manually (if you know how to create a flashable zip)
if you are using a cm based rom, just reflash the rom without deleting anything..
and avoid using space while renaming backups... it gives md5 mismatch error
Click to expand...
Click to collapse
No idea how to create the flashable zip. However I did notice a tutorial, I guess now would be a good time to learn.
I'm using darthstalker X1, it's a touchwiz based rom so I can't simply flash the rom again.
I saved all of my backups on my external SD card, can I just simply hook it up to my computer and change the backup names? And is my build.prop included in the backup I made?
Thank you for responding.
BadUsername said:
No idea how to create the flashable zip. However I did notice a tutorial, I guess now would be a good time to learn.
I'm using darthstalker X1, it's a touchwiz based rom so I can't simply flash the rom again.
I saved all of my backups on my external SD card, can I just simply hook it up to my computer and change the backup names? And is my build.prop included in the backup I made?
Thank you for responding.
Click to expand...
Click to collapse
renaming the backups again might not fix
i believe to have seen a script for sgy which fixes md5 mismatch error. but you need to give commands from terminal emulator.
if you have more than one backup of the rom, try to restore system only
if any one of them works your phone will boot up again
Edit: your backups contain the build.prop file in system.(partition type).tar
just extract this
and partition type may be rfs or ext4
Khizar Amin said:
renaming the backups again might not fix
i believe to have seen a script for sgy which fixes md5 mismatch error. but you need to give commands from terminal emulator.
if you have more than one backup of the rom, try to restore system only
if any one of them works your phone will boot up again
Edit: your backups contain the build.prop file in system.(partition type).tar
just extract this
and partition type may be rfs or ext4
Click to expand...
Click to collapse
No idea how that is even done. I think I need windows and ADB in order to extract the build.prop, I have a mac.
I found a restore that worked, I just forgot to rename it and it wasn't too old thankfully.
I really appreciate you helping. And now I know of this mismatch error so I can name my backups correctly.
BadUsername said:
No idea how that is even done. I think I need windows and ADB in order to extract the build.prop, I have a mac.
I found a restore that worked, I just forgot to rename it and it wasn't too old thankfully.
I really appreciate you helping. And now I know of this mismatch error so I can name my backups correctly.
Click to expand...
Click to collapse
to extract backups u need a tar extractor
if the backup format is something like .tar.a or .tar.md5 rename it to .tar first
and restoring the system only of your working backup would have booted your phone (in advance restore in recovery)
anyway this was an experience too for you.. so you would be carefull next time
Khizar Amin said:
to extract backups u need a tar extractor
if the backup format is something like .tar.a or .tar.md5 rename it to .tar first
and restoring the system only of your working backup would have booted your phone (in advance restore in recovery)
anyway this was an experience too for you.. so you would be carefull next time
Click to expand...
Click to collapse
Restoring my system partition only from advanced restore worked perfectly. All my apps stayed how they were and I didn't have to update all of my apps after I restored. Way better than doing a full restore in this case.
Thank you for this advice, this will be a very helpful method to me if I make any mistakes while messing with anything in my system folder. And yes, it was certainly an experience for me.
Sent from my SCH-I535 using Tapatalk 2
I have a clockworkmod file in the root of sdcard. I can see it in ES File Explorer but I cannot see it when I connect the phone to my computer. I use clockworkmod recovery only by booting into it when I need to...not by flashing it.
Although it dissappears when I delete it in ES File Explorer, if I refresh the screen it is still there. Anyone know what this file is exactly and how to get rid of it for good?
I tried another app called File Manager by Gira.me. It shows this file as ...
Path: /storage/emulated/0/clockworkmod
Type: */*
Size: 0 B
Last modified: Unknown
Permissions: ---
MD5: Unknown
When I try to delete it it says "Not enough permissions". There must be some way to delete this file.
Boot cwm, adb shell, rm the file
beekay201 said:
Boot cwm, adb shell, rm the file
Click to expand...
Click to collapse
I get the same message in adb shell "permission denied". I finally got rid of this by flash booting into TWRP. The file manager included allowed me to delete the clockworkmod folder. However, there was now also a TWRP folder so I deleted that one also before rebooting the system.
Thanks for the suggestion.
xda6969 said:
I get the same message in adb shell "permission denied". I finally got rid of this by flash booting into TWRP. The file manager included allowed me to delete the clockworkmod folder. However, there was now also a TWRP folder so I deleted that one also before rebooting the system.
Thanks for the suggestion.
Click to expand...
Click to collapse
Stuff like this happens when recoveries (or anything that stores files on your SD), puts files in the wrong place. CWM is doing it because it's designed for Jellybean systems.
It's time to move on to TWRP.
Aerowinder said:
Stuff like this happens when recoveries (or anything that stores files on your SD), puts files in the wrong place. CWM is doing it because it's designed for Jellybean systems.
It's time to move on to TWRP.
Click to expand...
Click to collapse
I like TWRP better now but it did the same thing. After leaving Recovery, when I looked at the contents of the sdcard in a File Manager, I had a 0 byte folder that I couldn't delete. I was then forced to boot back into TWRP and delete from there. I wish these recoveries would clean up after themselves when you exit them.
xda6969 said:
I like TWRP better now but it did the same thing. After leaving Recovery, when I looked at the contents of the sdcard in a File Manager, I had a 0 byte folder that I couldn't delete. I was then forced to boot back into TWRP and delete from there. I wish these recoveries would clean up after themselves when you exit them.
Click to expand...
Click to collapse
There isn't anything to clean up, TWRP makes that folder because that's where it stores nandroids.
Try this in a terminal emulator:
su
restorecon -FR /data/media/0/*
Reboot into recovery to recreate TWRP folder, then see if you can delete from Android.
Aerowinder said:
There isn't anything to clean up, TWRP makes that folder because that's where it stores nandroids.
Try this in a terminal emulator:
su
restorecon -FR /data/media/0/*
Reboot into recovery to recreate TWRP folder, then see if you can delete from Android.
Click to expand...
Click to collapse
Do you need to be rooted for that? If you don't, the next time it happens I will try it but it's clean now so I will leave it as is. Can a nandroid backup be used just to restore app data? I don't flash custom recoveries, I just boot into them. I would boot into TWRP, do a Nandroid of my app data, then copy the contents of the TWRP folder to my PC. Then I could do a complete wipe of the phone, recreate the TWRP folder, put the Nandroid backup in it, install the apps and restore their data.
xda6969 said:
Do you need to be rooted for that? If you don't, the next time it happens I will try it but it's clean now so I will leave it as is. Can a nandroid backup be used just to restore app data? I don't flash custom recoveries, I just boot into them. I would boot into TWRP, do a Nandroid of my app data, then copy the contents of the TWRP folder to my PC. Then I could do a complete wipe of the phone, recreate the TWRP folder, put the Nandroid backup in it, install the apps and restore their data.
Click to expand...
Click to collapse
Yes, you need to be rooted for restorecon command (su). A lot of people had troubles like yours when they moved to Lollipop (me too). Now that the recoveries have been updated, it's no longer an issue for most. You may still need to run the command, though. I suppose if you did a full wipe in stock recovery, it would fix the problem.
Your question about restoring app data with nandroid is vague and could be answered in a few ways. With your issue, the data partition is actually where the problem is, so I wouldn't recommend restoring the partition.
Instead, you might use Titanium Backup or something similar to back up only app data. But you need root for that.
Easiest solution is to root, fix issue, then, if you really want to, unroot. Don't need to wipe anything.