Backup+ Lets You Backup Your App Data on Android Lollipop

Even though Android 5.0 Lollipop hasn’t yet seen its official release, quite … more

TechTalk Compiles All the Android News You Need in One App

If you’re as obsessed with mobile devices as the vast majority of our forum … more

Android App Review: Google Inbox to Improve Your Life – XDA TV

Recently, Google+ exploded with the announcement of Google Inbox, as … more

Damp the LG G3 Thermal Throttling

As our mobile devices grow thinner and more powerfulwith each passing generation, it’s inevitable … more
Post Reply

Anyone got a CWM backup handy?

OP daperson

29th April 2012, 01:43 AM   |  #1  
OP Junior Member
Thanks Meter: 0
 
4 posts
Join Date:Joined: Apr 2012
I have failed rather spectacularly trying to reflash my phone using heimdall. (This has worked previously, but now it decided to break my phone)

Long story short, it will no longer flash the factoryfs.img of anything I try and make it flash (it fails at 42%, oddly). clockworkmod recovery mode still works (version 5.0.2.7), however I did not make a backup of the phone while it was in a workable state. When I attempt to install an update.zip file using clockworkmod I get an assertation failed error whinging that my build.prop file does not contain the proper device identifier string (Seems I managed to bork that, too).

I had the idea that I might be able to edit a factoryfs.img of an existing ROM and put in a build.prop file that has the required property, however have been unable to mount it. Those things seem to be structured oddly.

Using Odin is not an option. I do not have access to a windows computer.

Does someone have a clockworkmod backup of a working SGS2I9100, then? It is my hope that if I can procure one of these and stick it on the SD card clockworkmod will be able to load it (And then, provided this fixes the whole build.prop thing, I can install something from a zip).
Does there exist a way of editing build.prop from the computer? All I can seem to find are instructions of the form "Install this app and do it from your phone" - not much use when the thing won't boot.
Does anyone have any thoughts about why heimdall no longer works? It has worked before, but now, as I said, fails consistently at 42% of the way through factoryfs.img for whatever ROM I try to use.

Any other ideas? This thing's been bricked for a while now and I'm fresh out of ideas on how to fix it. Heimdall does seem to still be able to flash other things (just not factoryfs). So other plausible solutions would seem to be some way of flashing a working build.prop with heimdall or some update.zip of a working system that precludes the entirely sensible assertations that check the file.
29th April 2012, 02:52 AM   |  #2  
bored_stupid's Avatar
Senior Member
Flag Hereford
Thanks Meter: 184
 
668 posts
Join Date:Joined: Jul 2011
More
If your recovery is working why not just install a custom zipped firmware.. after that you can reinstall a stock rom.
29th April 2012, 03:27 AM   |  #3  
Senior Member
Thanks Meter: 713
 
1,847 posts
Join Date:Joined: May 2011
If you're positive you're installing something in CWM recovery for the correct device, you can disable script asserts.
29th April 2012, 03:32 AM   |  #4  
Senior Member
Flag hyderabad
Thanks Meter: 130
 
823 posts
Join Date:Joined: Dec 2010
More
get acses of pc an use odin.jus to make sure ur device is good

Sent from my GT-I9100 using xda premium
29th April 2012, 04:16 AM   |  #5  
Senior Member
Flag hyderabad
Thanks Meter: 130
 
823 posts
Join Date:Joined: Dec 2010
More
Quote:
Originally Posted by rocky23

get acses of pc an use odin.jus to make sure ur device is good

Sent from my GT-I9100 using xda premium

here u go
Attached Files
File Type: apk CWMManager.apk - [Click for QR Code] (157.7 KB, 6 views)
29th April 2012, 02:19 PM   |  #6  
OP Junior Member
Thanks Meter: 0
 
4 posts
Join Date:Joined: Apr 2012
Thank you all for your responses, but alas these all seem not to have worked :-

bored_stupid: As mentioned in my first post, I cannot use CWM recovery mode to install a zip from the sd card because of the assertation failure problem.

oinkylicious: Great idea! But rather strangely this had no effect on the problem - the same assertation failure error was always produced.

rocky23: That is certainly worth a try, but I wasn't kidding when I said I have no access to a windows pc. I really, really don't. Only Linux. (And it seems distinctly odd that I'd have to use Windows to fix the Unix based OS on my phone).

Thank you for the apk, however isn't that apk simply the clockworkmod recovery manager app? I am unsure how this is useful when my phone does not boot? Or did I miss something?
When I requested "a CWM backup" I was hoping for an actual system bacup, as generated by CWM recovery by it's "create backup" function. My reason for requesting this is that it is my belief that this would be installed without checking the (apparently broken) build.prop file, or at the very least would correct it so I'd be able to install an update zip in the usual way.


Thank you again - any other ideas?
29th April 2012, 02:25 PM   |  #7  
OP Junior Member
Thanks Meter: 0
 
4 posts
Join Date:Joined: Apr 2012
In case it is helpful, the precise assertation failure error produced when attempting to install an update zip with CWM recover:
Code:
assert failed: getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" || getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2"
As you can see, it appears the installer is (rather sensibly) checking that my phone really is a galaxy s2 I9100 (Which it is, I promise), and the phone seems to be incorrectly reporting that it is not.
As mentioned, I think this is because I managed to ruin my build.prop file somehow. Any ideas on how to correct that (Or any other alternative solutions)?
29th April 2012, 02:58 PM   |  #8  
Senior Member
Thanks Meter: 4,421
 
23,043 posts
Join Date:Joined: Oct 2010
If indeed someone gave you a CWM backup it would contain a lot of personal information .

jje
29th April 2012, 03:02 PM   |  #9  
OP Junior Member
Thanks Meter: 0
 
4 posts
Join Date:Joined: Apr 2012
Potentially so, yes, unless work was done to prune that out at the start. I am unfamiliar with the structure of these backups - could one that consisted only of /system be created?
29th April 2012, 04:05 PM   |  #10  
Senior Member
Thanks Meter: 141
 
544 posts
Join Date:Joined: Jun 2010
Quote:
Originally Posted by daperson

In case it is helpful, the precise assertation failure error produced when attempting to install an update zip with CWM recover:

Code:
assert failed: getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" || getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2"
As you can see, it appears the installer is (rather sensibly) checking that my phone really is a galaxy s2 I9100 (Which it is, I promise), and the phone seems to be incorrectly reporting that it is not.
As mentioned, I think this is because I managed to ruin my build.prop file somehow. Any ideas on how to correct that (Or any other alternative solutions)?

You could just delete the part of the script that checks what deveice you are on.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes