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.
If your recovery is working why not just install a custom zipped firmware.. after that you can reinstall a stock rom.
If you're positive you're installing something in CWM recovery for the correct device, you can disable script asserts.
get acses of pc an use odin.jus to make sure ur device is good
Sent from my GT-I9100 using xda premium
rocky23 said:
get acses of pc an use odin.jus to make sure ur device is good
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
here u go
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?
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)?
If indeed someone gave you a CWM backup it would contain a lot of personal information .
jje
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?
daperson said:
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)?
Click to expand...
Click to collapse
You could just delete the part of the script that checks what deveice you are on.
Related
8GB Nook Tablet model.
I flashed CWM via the one-click tool provided by Indirect, and I can boot into it fine. The problems arise when actually attempting to use it, however. It reboots occasionally, and I haven't been able to flash any .zip files successfully. Anytime I attempt to flash them, CWM just hangs, or in the case of the CM9 flash, creates rainbow stripes across the screen.
So, unfortunately, my NT seems to be in a soft-brick state. It'll boot to the white reading screen, but no further. CM7 SD version works fine, but I'm wondering if there's any way to recover back to factory, as well as what I did wrong.
Well, I managed to fix the soft brick by booting into the broken CMW, and using ADB to write the recovery_512MB.img from the CM9 thread to the device. That CWM worked fine, no glitches or lockups during flashes, although flashing CM7 just ending up with it continually booting into recovery.
At any rate, I was able to edit the stock 1.4.2 update's update-script, and got it flashed via CWM, so my tablet is back working.
I suppose my only real question now would be if there's an easy, working way to flash either CM7 or CM9 to the 8GB.
songjacked said:
Well, I managed to fix the soft brick by booting into the broken CMW, and using ADB to write the recovery_512MB.img from the CM9 thread to the device. That CWM worked fine, no glitches or lockups during flashes, although flashing CM7 just ending up with it continually booting into recovery.
At any rate, I was able to edit the stock 1.4.2 update's update-script, and got it flashed via CWM, so my tablet is back working.
I suppose my only real question now would be if there's an easy, working way to flash either CM7 or CM9 to the 8GB.
Click to expand...
Click to collapse
I am having the exact same problem you described in your first post. What changes did you make to the update script to get it to work? I keep getting cannot open package errors.
cheddleson said:
I am having the exact same problem you described in your first post. What changes did you make to the update script to get it to work? I keep getting cannot open package errors.
Click to expand...
Click to collapse
Assuming you have a functioning CWM Recovery, you should be able to flash the 1.4.2 update from the B&N website. Download their software zip, then unzip the contents. I don't remember the exact location of the file offhand, but it's called update-script, and should be located a few folders in.
Open the update-script with Notepad, then delete the first two lines as shown in the CM9 thread:
http://forum.xda-developers.com/showthread.php?t=1534192
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Save the changes, then rezip the contents. I wasn't sure what compression settings to use, so I just chose the "store" level. Made the update grow to about 408MB. Just flash that zip through recovery, and you should be set.
songjacked said:
Assuming you have a functioning CWM Recovery, you should be able to flash the 1.4.2 update from the B&N website. Download their software zip, then unzip the contents. I don't remember the exact location of the file offhand, but it's called update-script, and should be located a few folders in.
Open the update-script with Notepad, then delete the first two lines as shown in the CM9 thread:
http://forum.xda-developers.com/showthread.php?t=1534192
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Save the changes, then rezip the contents. I wasn't sure what compression settings to use, so I just chose the "store" level. Made the update grow to about 408MB. Just flash that zip through recovery, and you should be set.
Click to expand...
Click to collapse
Thanks, I think that's about the only thing I haven't tried yet. Can't wait for more development in the 8 gig. I'll be sure to thank you if it works for me.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Hello everyone.
It seems my transformer prime is missing an odex file and cannot run the new system update.
I have tried factory reset and everything now i can think of, nothing helped.
How the file has even got missing is beyond me, but the device is rooted and i have OTA rootkeeper and titanium backup.
the file it says is missing is the Galaxy4.odex, located in /system/app/
the error_log from failed update state:
Code:
failed to stat "/system/app/galaxy4.odex": No such file or directory.
file "/system/app/galaxy4.odex" does not have any of the expected sha1 sums; checking cache
failed to load cashe file
script aborted: assert failed: apply patch:check("/system/app/Galaxy4.odex", ---list of numbers---, --list of numbers--not the same")
E:Error in /cache/dlpkgfile
(Status 7)
Installation Aborted
I:result code 410
Does anyone have an idea how i can restore this file to do the update?, or can make some kind of copy /backup that i can install of this file?
All help appreciated!
Silverdream
FYI:
I have WW_epad-9.4.2.14-20120214
Silverdream said:
Hello everyone.
It seems my transformer prime is missing an odex file and cannot run the new system update.
I have tried factory reset and everything now i can think of, nothing helped.
How the file has even got missing is beyond me, but the device is rooted and i have OTA rootkeeper and titanium backup.
the file it says is missing is the Galaxy4.odex, located in /system/app/
the error_log from failed update state:
Code:
failed to stat "/system/app/galaxy4.odex": No such file or directory.
file "/system/app/galaxy4.odex" does not have any of the expected sha1 sums; checking cache
failed to load cashe file
script aborted: assert failed: apply patch:check("/system/app/Galaxy4.odex", ---list of numbers---, --list of numbers--not the same")
E:Error in /cache/dlpkgfile
(Status 7)
Installation Aborted
I:result code 410
Does anyone have an idea how i can restore this file to do the update?, or can make some kind of copy /backup that i can install of this file?
All help appreciated!
Silverdream
Click to expand...
Click to collapse
Do you have a root file manager of some sort, if so, check if that file is:
A) Actually present
B) Has the correct permissions
I do have that odex file on my computer from a system dump that I did at some point, but I honestly can't be sure which version it is.
You could of course download the full update from ASUS website and run it from external SDcard. Search the forum, you should find the exact method of doing this fairly easily.
You could also try to update to .15 first from ASUS website and then do the .21 update. WW versions are present in the download section of the TF201 minisite.
I hope one of these suggestions is of use to you.
Thanks for reply.
I tried most of those, before you wrote it, It just did not want to update when missing files. Then i figured out to hell with it, installed the bootload enabler and a new custom .21 ROM instead.
Bricked once, but now it seems just fine
Hi all,
assert failed: getprop("ro.product.device") =="p4wifi" ...
I can not seam to delete the first line that i read from some post using Notepad++ if i make a copy to my desktop i can delete the first line of the install script, but can not copy it back to the zip folder. Trying to load an older version of the same rom i get the same error now also.
Any help would be great. and yes i have the right file for the right tablet ver GT p7510 wifi and trying to use cm-10-20121017-exp zip.
Loaded the new recovery and bootloader also.
any help would be great.
did you try to update script directly into zip file ?
I don't know which OS you are using (maybe windows ?), with linux, you can edit a file directly a zip file (file roller for me). After saving your file, zip is automatically updated.
if you are using winzip, i guess you can drag and drop updated file into your zip.
of course, you need to edit the zip file out of your tab.
Thanks Light,
But i tried all different ways with no luck. I am on the 20121017 now i just had to use an older version of the CWM recovery.
;P
Kokapelly said:
Thanks Light,
But i tried all different ways with no luck. I am on the 20121017 now i just had to use an older version of the CWM recovery.
;P
Click to expand...
Click to collapse
Hey could you please just list files you used to make it work? I think I have the same issue as you.
Thanks in advance,
Regards,
Baptiste
BatBat said:
Hey could you please just list files you used to make it work? I think I have the same issue as you.
Thanks in advance,
Regards,
Baptiste
Click to expand...
Click to collapse
this is the path of the file : /META-INF/com/google/android/
the file name is : updater-script
Code:
assert(getprop("ro.product.device") == "p4wifi" || getprop("ro.build.product") == "p4wifi");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-num/p4", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
...
you just need to delete the first line (assert(getprop...).
Kokapelly said:
Hi all,
assert failed: getprop("ro.product.device") =="p4wifi" ...
Click to expand...
Click to collapse
If you're seeing that, then you should update your CWM. It's not recognizing your tablet device. I'm using CWM 5.5.0.4 and it does recognize the P7510 as "p4wifi".
Kokapelly said:
I can not seam to delete the first line that i read from some post using Notepad++ if i make a copy to my desktop i can delete the first line of the install script, but can not copy it back to the zip folder. Trying to load an older version of the same rom i get the same error now also.
Any help would be great. and yes i have the right file for the right tablet ver GT p7510 wifi and trying to use cm-10-20121017-exp zip.
Loaded the new recovery and bootloader also.
any help would be great.
Click to expand...
Click to collapse
If it's easier, edit the file and just insert a "#" before the "assert". That will comment it out. However, I'd recommend updating the recovery instead.
Success Story - you figure out how...
This is a SUCCESS story...
I got by this somehow, not sure what it was but will over communicate so someone else can figure out specifics.
updating my gt-p7510 from android 3.1 to Android 4.1.2 (CM 10 ROM 20121215 nightly)...
My tab was in weird state from a prior rom sequence (I had rooted it long ago.. some programs said it was rooted, but programs trying to get the permission, like titanium backup, would fail)
so I followed the instructions to root again from HERE
up to the point to the point where you load a ROM. ie. I loaded CWM 5.5.0.4 using odin3.
Then I downloaded the latest CM 10 , copied it to root folder on my tab... and tried to use CWM to install it...
got the "assert(getprop("ro.product.device") == "p4wifi" ... Failure...
went wild and tried other programs (ROM Manager, System Updater etc. avail from "Play Store" ... actually I had tried these prior to rooting again...
they failed before (not able to get root permissions) and after (not able to perform the update... assuming they got and hid similar error)
Tried to edit out the assert in the updater-script as in the prior post... but unzipping had a lot of duplicate file overrides (into clean folder) and they were not all exactly the same file (ie some had different sizes)... so gave up that path.
I had been avoiding updating CWM further because of k1mu's success above ... and avoided the "CWM Touch" flash as I thought base CWM would be better.
Went back to try to update CWM (went to www.clockworkmod.com) and was annoyed when I could not download the CWM zips... links returned characters in browser...
Finally went wild again... used ROM Manager Pro to update CWM to the latest "CWM Touch"
Surprisingly this updated CWM easily...
Then used it to Load the latest CM 10 nightly ... again shockingly easy AND successful... (no Assert failure)
ROM Manager did not automatically update the google apps ... so I got my first look at the CWM Touch interface installing gapps...
But it all worked... So LOVE ROM Manager...
(although for grins I also found and tried CM 10 downloader and retried System Updater Pro etc.. .they all work now)
But hats off to ROM Manager's update and to CWM touch for seemingly fixing all my problems.
lightman33 said:
this is the path of the file : /META-INF/com/google/android/
the file name is : updater-script
Code:
assert(getprop("ro.product.device") == "p4wifi" || getprop("ro.build.product") == "p4wifi");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-num/p4", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
...
you just need to delete the first line (assert(getprop...).
Click to expand...
Click to collapse
I open in notepad++ and here is the code from updater-script
Code:
assert(!less_than_int(1383478437, getprop("ro.build.date.utc")));
assert(getprop("ro.product.device") == "p4wifi" || getprop("ro.build.product") == "p4wifi");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-num/p4", "/system");
So do I need to delete full 1st line or 2nd line?
If I follow your instruction, I have to delete 2nd line...
EDITED:
Line 2 deleted! And done flashing
The answer to all of this: The problem is the recovery, not the update package, or the updater script.
The assert fails because CWM, TWRP, and some other modified recoveries do not include the getprop command in their small, ramdisk linux OS. So, when the assert tries to run getprop to check ANY property for the installed system, it fails.
Apparently CWM Touch has this binary included.
Custom recoveries generally don't think to include it because pretty much the only thing being flashed through them are custom roms, with their own custom installer scripts, and these rarely (have they ever?) include asserts checking for properties.
Hello professionals!
I wonder if someone please can instruct me in how to complete the 10.1 Nightly update from ICS 4.0.4.
I'm half there in the process but it always ends with this error :
Installing update...
assert failed: assert failed: getprop("ro.product.device") == "p990" || getprop("ro.build.product") == "p990"
E: Error in /sdcard/cm-10.1-20131006-NIGHTLY-p990.zip
(Status 7)
Installation aborted
I'm using latest ROM Manager and the phone is rooted ok.
How do I solve this, I'm stuck and have read for 10 hours online and on Youtube without finding a resolution!??
What am I doing wrong here and how do I solve it?
Every little help on the way will be very much appreciated!
Anna.A. said:
Hello professionals!
I wonder if someone please can instruct me in how to complete the 10.1 Nightly update from ICS 4.0.4.
I'm half there in the process but it always ends with this error :
Installing update...
assert failed: assert failed: getprop("ro.product.device") == "p990" || getprop("ro.build.product") == "p990"
E: Error in /sdcard/cm-10.1-20131006-NIGHTLY-p990.zip
(Status 7)
Installation aborted
I'm using latest ROM Manager and the phone is rooted ok.
How do I solve this, I'm stuck and have read for 10 hours online and on Youtube without finding a resolution!??
What am I doing wrong here and how do I solve it?
Every little help on the way will be very much appreciated!
Click to expand...
Click to collapse
Last time that happened to me I had to update to a newer version of clockworkmod recovery.
you might ask in the thread for your ROM to see if anyone else is having the same issue.
firefly6240 said:
Last time that happened to me I had to update to a newer version of clockworkmod recovery.
you might ask in the thread for your ROM to see if anyone else is having the same issue.
Click to expand...
Click to collapse
Thank you for your reply!
I have "some" knowledge in this (not totally stupid, that is) and I am sure I will fix this, but please tell me - how do I update Clockworkmod Recovery and where do I find information about it on the phone to know what version I have?
The directions I've read about it just does not give me a clear answer in how to do it!
Anna.A. said:
Thank you for your reply!
I have "some" knowledge in this (not totally stupid, that is) and I am sure I will fix this, but please tell me - how do I update Clockworkmod Recovery and where do I find information about it on the phone to know what version I have?
The directions I've read about it just does not give me a clear answer in how to do it!
Click to expand...
Click to collapse
the version is usually shown at the top or the bottom of the screen while in recovery mode,
it will say "clockwork Mod Recovery vx.x.x.x if its the official CM revovery.
or if its an alternate recovery it will usually say CWM based recovery vx.x.x.x
to be safe I would ask in the forum of your rom what version other people are running that have successfully updated and compare it with yours.
if you have a lower version ask where they got theirs as some roms work better with custom recoverys
as a last resort you should be able to install it from the rom manager app or from the clockworkmod website though I would think some alternate recoveries will be based on higher versions so definitely check with other users before flashing anything.
for reference I am running a MIUI port called GearUI as my Rom (android 4.1.2)
my recovery version is: CWM base version v6.0.3.7 (Gear kernel recovery)
but this will vary from rom to rom.
Thank you for reply!
This is how I do the update to CM 10.1 ;
When I connect the phone to PC it shows as 2 separate external SD-cards. E: and F:
- which am i suppose to use for the .zip? The one with DCIM / LOST DIR?
So I have tried to place cm-10.1-20131006-NIGHTLY-p990.zip0 and gapps-jb-20121212-signed.zip on both (just to be sure, but in no maps), and after that I have tried to open them separately from both E: and F: but none works.
Installing update...
assert failed: assert failed: getprop("ro.product.device") == "p990" || getprop("ro.build.product") == "p990"
E: Error in /sdcard/cm-10.1-20131006-NIGHTLY-p990.zip
(Status 7)
Installation aborted
ROM Manager is version 5.5.3.0 and is suppose to be the latest from GooglePlay, no newer versions can be found.
It's flashed and I have root access.
ClockworkMode Recovery is version 6.0.1.5
I don't get this ; In CWM I don't see the external SD card as an option, only "install zip from sdcard" but I have the zip-files on the external SD-card?
I will keep looking for answer for why updating to 10.1 is so tricky, when both rooting and updating to 4.0.4 was a piece of cake, but is also very glad for help on the way!
Anna.A. said:
(Status 7)
Installation aborted !
Click to expand...
Click to collapse
From MY Android Solutions
[27] Problem:- ClockworkMod Recovery giving Status 7 error "Installation aborted".
Quote:
Solution:- One or some of the prerequisite requirement for the needed upgrade is missing or corrupted . So you may need to identify and replace that requirement for the installation to continue. Most likely could be due to wrong bootloader, wrong CWM, Wrong IMEI, Wrong Radio etc
Check this out! You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, click on their Thanks button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks
Its easier to give "Feedback" in this manner than make an additional post.
Ok that makes sence.
However, I cannot find any other downloading sites for those files besides from here and here.
A very strange thing though! The phone now sais that I do not have a external SDcard after removing the SIM-card (to use in another while doing this update fix)!!!!
Is the SIM being used as a SDcard, that cannot be right?
So when I placed the zip-files on the SDcard root (E, the phone now sais this ;
E:Can't open /sdcard/cm-10.1-20131006-NIGHTLY-p990.zip
(No such file or directory)
Installation aborted.
But the zip-files ARE there but when being in CWM it sais that the zip-files are placed in /emmc/
What am I doing wrong???!
Anna.A. said:
What am I doing wrong???!
Click to expand...
Click to collapse
First problem is, you have not informed what is your Phone Model? which means no one in XDA can help, unless they are a magician second being, external SD card will be considered emmc, as such you should install from Ext SD card, if files were placed in External SD card or place the files in your internal Sd card and install . Most of all it must be for your phone model, not just for any brand and model.
Check this out! You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, click on their Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks
Its easier to give "Feedback" in this manner than make an additional post.
Oh I'm so sorry! But I simply just thought that it was clear on what phone model it's about by the CM-file name.
I have a LG P990 2x.
cm-10.1-20131006-NIGHTLY-p990.zip
you can try deleting the getprop line out of the updater-script file inside the zip. if you search the forums there are instructions on how to do this. but if it fails on that step it could be an indicator it is not for your phone. this line checks to make sure you are using the right build for your phone
smos08 said:
you can try deleting the getprop line out of the updater-script file inside the zip. if you search the forums there are instructions on how to do this. but if it fails on that step it could be an indicator it is not for your phone. this line checks to make sure you are using the right build for your phone
Click to expand...
Click to collapse
Very good advice, thank you! However, that didn't do the trick either.
I found excellent instructions in how to fix the updater-script but the file could not be saved as original again after removing .txt.
I renamed it to .txt and fixed the script in EditPad, but the .txt was not written out TO be removed afterwards, (as on the instruction video) and there was no way to rename it in any other way.
I use Windows 7.
I'm now stuck with 4.0.4 and a wiped out phone on all data. ;-(
I can get internet access though SIM but WiFi doesn't work no more.
When trying to re-create my Google account (to get access to all my accounts and apps) it fails too ; "com.android.vending has stopped working".
I need my Link2SD to get acccess to what needs to be fixed, but that app is also gone. Root is also gone.
Also, when logged in to Google+ account I can see all my apps being installed and everything looks fine - BUT they are not installed on the phone no more and I need to re-install them, but I havent found any information in how to do that either!
I'm very stubborn so I will get this fixed and I will upgrade to JB, and with your help I will succeed!
Anna.A. said:
Very good advice, thank you! However, that didn't do the trick either.
I found excellent instructions in how to fix the updater-script but the file could not be saved as original again after removing .txt.
I renamed it to .txt and fixed the script in EditPad, but the .txt was not written out TO be removed afterwards, (as on the instruction video) and there was no way to rename it in any other way.
I use Windows 7.
I'm now stuck with 4.0.4 and a wiped out phone on all data. ;-(
I can get internet access though SIM but WiFi doesn't work no more.
When trying to re-create my Google account (to get access to all my accounts and apps) it fails too ; "com.android.vending has stopped working".
I need my Link2SD to get acccess to what needs to be fixed, but that app is also gone. Root is also gone.
Also, when logged in to Google+ account I can see all my apps being installed and everything looks fine - BUT they are not installed on the phone no more and I need to re-install them, but I havent found any information in how to do that either!
I'm very stubborn so I will get this fixed and I will upgrade to JB, and with your help I will succeed!
Click to expand...
Click to collapse
i have been successful doing it like this. (you will need 7zip and notepad++)
right click on zip, open archive with 7zip
navigate to the updater-script file
copy to local HD (should come over as just a "file" with no extension)
right click and open with notepas++
use notepad++ to delete the entire line so there are no blank spaces at the top
save the file (ctrl+s) will not prompt for file type
go to open archive and delete updater-script from the rom ZIP (using delete button in 7zip)
drag your local copy (the one we edited with notepad++) onto the zip and it will copy it in
close DO NOT SAVE just close the window
copy rom to phone/sd then flash
Ah, so that's how to save it! "save the file (ctrl+s) will not prompt for file type" - very good to know, THANK YOU!
However, I have managed to fix iCM 10.1 t with help of AIO Tookit and have now 4.2.2 installed, but the only thing not working (and I do not find the answer to anywhere) is that the SD card is not recognized.
I have formatted it with SDFormatter but still it's not found by the camera and spent hours and hours google for answers.
Maybe you know the answer to how to fix that too?
Through bad flashes I've corrupted an SD beyond readability on any device; win/mac/and android. Just had to buy a new one.
Sent from carbon note 2 on XDA premium app
Background information:
LG K7 MS330m1 5.1.1 reception is often poor at home for both data and voice and tends to choose the weekest towers available, data is often slow to respond even in areas with good signal strength, wi-fi signal seems weak. Leaving wi-fi often makes data turn off or go into a loop where I have to manually disallow it and then re-allow it to get it to stay on. The update.zip is for a security update and contains a radio.img file, it's assumed that it at least addresses the KRACK exploit but the facts are unknown as to if it actually offers any benefits, research has been futile on this for over two years now so I'm either searching wrong or the answers are not out there.
I have a modified system partition so flashing the OTA update is a bit more than I want to undertake. So I have a few questions regarding the radio.img file in the update.zip.
1. Is it safe to just flash radio.img or could that cause a conflict and leave me with a problem?
2. Assuming it is safe, are there possible benefits to cell and wi-fi reception to be obtained with the newer radio.img, could it make reception better? Could it make it worse?
3. Assuming 1 and 2 are a go, should I bother backing up the current radio.img?
4. If 3 is advisable, what is the procedure for backing the image up?
Thanks
Edit: I think I've been able to answer some of my questions but I could use an expert on this subject matter to verify that my solution is workable.
Actually found one post saying it is completely safe.
Now I'm wondering how hard it would be to create a flashable zip to do it. Looking at their updater-script I think if it's modified leaving only the following code it should do just that?
Code:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "max_batch_time=0,commit=1,data=ordered,barrier=1,errors=panic,nodelalloc");
ui_print("Writing radio image...");
assert(qcom.backup_radio(package_extract_file("radio.img")));
lge.hammerhead.update_gpt();
unmount("/system");
Anyone have any knowledge on this as to if that would work or not? Any formatting errors, lack of needed lines or unneeded lines here?
I assume it could also be flashed via the fastboot command but I'm not certain since in this script I see "extract", anyone know anything about that?
Thanks
This is probably closer to correct...
Code:
if get_stage("/dev/block/bootdevice/by-name/misc", "stage") == "" then
set_stage("/dev/block/bootdevice/by-name/misc", "S-1/3");
endif;
ui_print("Writing radio image...");
if get_stage("/dev/block/bootdevice/by-name/misc", "stage") == "S-1/3" then
ui_print("Step_S1/3");
assert(qcom.backup_radio(package_extract_file("radio.img")));
lge.hammerhead.update_gpt();
set_stage("/dev/block/bootdevice/by-name/misc", "S-2/3");
endif;
if get_stage("/dev/block/bootdevice/by-name/misc", "stage") == "S-2/3" then
ui_print("Step_S2/3");
assert(qcom.install_radio(package_extract_file("radio.img")));
set_stage("/dev/block/bootdevice/by-name/misc", "S-3/3");
endif;
if get_stage("/dev/block/bootdevice/by-name/misc", "stage") == "S-3/3" then
ui_print("Step_S3/3");
lge.hammerhead.recover_gpt();
endif;
ui_print("Wrote new radio image.");
Added that last line but the rest is straight from the original OTA updater-script minus a section that updated the build.prop. Of course the rest of the zip is in it's original format with all of the unneeded parts removed since my goal here is just to flash the new radio.img only the updater binary and script exist in their original proper locations and the radio.img file. Anyone here that can tell me if this will work right?
Thanks
Interesting...
First I got a zip format error, I was zipping the folder instead of the files inside. After fixing that it appeared to work as expected except the baseband version under about phone in settings hasn't changed. ???WTH???