Related
ok so heres the deal. i bricked my last gt540 but was able to bring it to the store and swap it out.
lol so here we are on the new one and i have it rooted, latest recovery i can find 3.0.2.4...i managed to flash mur4ik's cm7 2.3.3 but now it seems as if im stuck with it. whether i try and flash from clockwork or rom manager i always get a failed attempt. once i noticed it was cause the rom wasnt signed so i toggled the option to off and still it failed. any help would be awesome.
thanks gents!
any help would be super!
try flashing roms using the fastboot method
lol it seems like a major task for me. cant seem to figure out how to do.
ive similar problem,
installed euro 2.1 build using KDZ image. recovery comes up.
If i try to restore zip from sd using update-cm-7.0.2-GT540-MUR4IK-signed.zip i keep on getting:
Installing update
assert failed: getprop("ro.product.device" == "swift" || "ro.build.product" == "swift" || "ro.product.board" == "swift" ||
E:Error in /sdcard/clockworkmod/backup/update-cm-7.0.2-GT540-MUR4IK-signed.zip
(Status 7)
Installation aborted
anyone ?
tmuehlhoff said:
ive similar problem,
installed euro 2.1 build using KDZ image. recovery comes up.
If i try to restore zip from sd using update-cm-7.0.2-GT540-MUR4IK-signed.zip i keep on getting:
Installing update
assert failed: getprop("ro.product.device" == "swift" || "ro.build.product" == "swift" || "ro.product.board" == "swift" ||
E:Error in /sdcard/clockworkmod/backup/update-cm-7.0.2-GT540-MUR4IK-signed.zip
(Status 7)
Installation aborted
anyone ?
Click to expand...
Click to collapse
i used the same method. sounds like the same issues. i think we need some help lol.
kdm212 said:
i used the same method. sounds like the same issues. i think we need some help lol.
Click to expand...
Click to collapse
ive read about different hardware used in gt540/swift types.. .maybe thats the issue here?!
so then what should we do? where did you read this stuff?
dunno- therere millions of threads out there. maybe someone feels like and gives us a hint what to do....
ok so i managed to figure out fastboot via cmd. i was overthinking it. anyway i get to the step where i need to send and write the fastboot flash boot boot.img. it sends it but fails to write to the phone.
(remote: flash write failure)
any suggestions?
Have you tried downloading the files again. Sometimes the download is corrupt which will cause a fail in the recovery. I have had it a few times myself. After downloading the file again (often from another source) the recovery completes itself succesfully.
i have tried to redownload. im actually going to bring the phone all the way back to stock and see what happens. kinda start from scratch.
Try this way go to market and Download bt file manager and seleact the update package and extract to a folder then try install zip from sD method try and rply
Sent from my GT540 using XDA Premium App
kdm212 said:
i have tried to redownload. im actually going to bring the phone all the way back to stock and see what happens. kinda start from scratch.
Click to expand...
Click to collapse
Get in emergency mode and reflash boot.img via CMD with fastboot commands and you will get the same error probably, but you just reboot it, let it boot it will work
Sent from my GT540 using XDA App
OK, just for background info, my Nexus 4 is currently rooted, running the hybrid radio firmware (so I've got LTE, that's working), and my current firmware is build JWR66V.
I'm trying to upgrade to the newer firmware (the newest 4.3), which supposedly has some minor security updates to the PRNG & such, but I'm getting an error when I try the OTA update.
When the phone boots up to the bootloader (Team Win 2.6.0.0), I get the following messages in its terminal:
Code:
Updating partition details...
Processing AOSP recovery commands...
Installing zip vile /cache//6136cbe0fb2199........
Installing '/cache/6136cbe0fb2199........signed-occa
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Warning: No file_contents
Verifying current system...
assert failed: apply_patch_check("system/build.prop". "e336e937...
E:Error executing updater binary in zip '/cache//6136cbe...
E:Error installing zip file '/cache/6136cbe0fb2199........
Done processing script file.
Any ideas how to fix this so I can update my phone's firmware?
When Kit Kat comes out, I do want to be able to update to it.
meldroc said:
OK, just for background info, my Nexus 4 is currently rooted, running the hybrid radio firmware (so I've got LTE, that's working), and my current firmware is build JWR66V.
I'm trying to upgrade to the newer firmware (the newest 4.3), which supposedly has some minor security updates to the PRNG & such, but I'm getting an error when I try the OTA update.
When the phone boots up to the bootloader (Team Win 2.6.0.0), I get the following messages in its terminal:
Code:
Updating partition details...
Processing AOSP recovery commands...
Installing zip vile /cache//6136cbe0fb2199........
Installing '/cache/6136cbe0fb2199........signed-occa
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Warning: No file_contents
Verifying current system...
assert failed: apply_patch_check("system/build.prop". "e336e937...
E:Error executing updater binary in zip '/cache//6136cbe...
E:Error installing zip file '/cache/6136cbe0fb2199........
Done processing script file.
Any ideas how to fix this so I can update my phone's firmware?
When Kit Kat comes out, I do want to be able to update to it.
Click to expand...
Click to collapse
You will need to flash back the 0.84 radio, and replace the build.prop file with the original. (You must have flashed something that modified it.)
Where would I find an original radio file and build.prop?
Sent from my Nexus 4 using xda app-developers app
meldroc said:
Where would I find an original radio file and build.prop?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What I would do if I were you is get the JWR66Y factory image from Google's developer page, and flash the system.img, boot.img and modem.img files (only those three) using fastboot. Have a look at the return to stock link in my signature. (You will need to flash a superuser zip again afterwards if you want root.)
Is the boot.img file the stock bootloader? I may just flash the system and modem images if that's the case, to make re-rooting easier.
Sent from my Nexus 4 using xda app-developers app
meldroc said:
Is the boot.img file the stock bootloader? I may just flash the system and modem images if that's the case, to make re-rooting easier.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No it is not. The boot.img file contains the kernel and ramdisk. In any case, you can flash the bootloader.img file as well the 3 mentioned above. It doesn't affect your ability to get root...
efrant said:
No it is not. The boot.img file contains the kernel and ramdisk. In any case, you can flash the bootloader.img file as well the 3 mentioned above. It doesn't affect your ability to get root...
Click to expand...
Click to collapse
Got it. I'll flash all three, though since I've got the Team Win bootloader, I'll probably keep that.
Next time I have some quality time to tinker with my phone, I'll try the updates you suggested.
meldroc said:
Got it. I'll flash all three, though since I've got the Team Win bootloader, I'll probably keep that.
Next time I have some quality time to tinker with my phone, I'll try the updates you suggested.
Click to expand...
Click to collapse
That would be the TeamWin recovery.img, not bootloader. Recovery is not a bootloader.
Sent from my Nexus 4 using Tapatalk 2
Looks like it's all working! Flashed the three .img files you suggested using fastboot, wiped the Dalvik cache, rebooted, now the setting show I'm running JWR66Y.
Thanks for the help!
Hi, i'm trying to cook a n9005 rom (deodex, root, busybox, init.d support, data/app support) using dsixda kitchen version 0.224 (updated with this package) but, after rom installation in CWM, at reboot, i get the message "could not do normal boot" in odin mode.
This is what i do:
1. setup working folder and follow instructions to extract system and cache img
2. deodex using api level 18
3. add root permissions (choosing "f" - chainfire-update)
4. install busybox
5. add /etc/init.d support
6. add /data/app support
7. delete some apks from system folder (like polaris office, chrome, etc)
8. build rom, option 99, using "1" interactive mode (zipaligning, creating update.zip and signing, all whitout errors)
9. install in cwm without errors
10. reboot
11. odin mode with message "could not do normal boot"
I think i miss something, maybe during root or init.d support processes, but i don't get any error message while cooking.
What can i do? Thanks.
Hi,
I have the same problem. Also i used kitchen version 224 but not updated with that package.
Seem to work everything ok, but when i want to flash it, it hooks up, sometimes with an cwn error, and sometimes with the same message you got.
After trying a lot with other custom roms the solution for me is that the update-binary is not correct. Copied over from other rom, edited updater script to my needs and everything is fine....
Still do not know where tje problem is.... always take clean samsung stock rom, doesn't matter if i use windows or ubuntu, result is the same
So i use the workaround and it works at least for me...
Sent from my SM-N9005 using xda premium
I'll try, thank you! Do you know how update binary is created?
Inviato dal mio SM-N9005 utilizzando Tapatalk
No sorry, i can't help you out with that, i am really a noob on Android-stuff.... i put that mod on my kitchen.... now update binary fits, but boot.img won't work... i get a cwm error 7
... i read all the messages about error 7, and.it would be easy to handle if those lines which you should delete were there )) nothing helped out, till i testet a boot.img from another custom rom....
Finally i got my "own" rom working.... ))
Best regards..
Sent from my SM-N9005 using xda premium
daywalker386 said:
No sorry, i can't help you out with that, i am really a noob on Android-stuff.... i put that mod on my kitchen.... now update binary fits, but boot.img won't work... i get a cwm error 7
... i read all the messages about error 7, and.it would be easy to handle if those lines which you should delete were there )) nothing helped out, till i testet a boot.img from another custom rom....
Finally i got my "own" rom working.... ))
Best regards..
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
Thank you! Finally i solved my problem using original samsung boot.img (in some way the kitchen modify/corrupt the boot.img)
jackyaway said:
Thank you! Finally i solved my problem using original samsung boot.img (in some way the kitchen modify/corrupt the boot.img)
Click to expand...
Click to collapse
i get an error 6 on cmw, can you or anyone help me find the syntax error? also, it only installs using cmw, any clue as to why twrp wont work?
hi guys, i want to updata to cm11,so i install the twrp 2.6.3.2, and wiped dalvik,system, data and cache without backup. but after that when i try to install the CM11, it told me
set_metadata_recursive: some changes failed
E: error excuting updater binary in zip <my cm11 rom>
error flashing zip
and failed at last.
cuz there is no os on my phone, i don't know how to deal with it.
i looked it up and found that might be a TWRP issue, but i don't know which version should i use and how can i install it? cuz everytime i try to use adb push, it told me error: closed.
i m really anxious now,need your help.
forgive my bad english, and please give me some advice asap!!!!!!thanks!!!!!!!!!!!!!!!!!!
crixus3811227 said:
hi guys, i want to updata to cm11,so i install the twrp 2.6.3.2, and wiped dalvik,system, data and cache without backup. but after that when i try to install the CM11, it told me
set_metadata_recursive: some changes failed
E: error excuting updater binary in zip <my cm11 rom>
error flashing zip
and failed at last.
cuz there is no os on my phone, i don't know how to deal with it.
i looked it up and found that might be a TWRP issue, but i don't know which version should i use and how can i install it? cuz everytime i try to use adb push, it told me error: closed.
i m really anxious now,need your help.
forgive my bad english, and please give me some advice asap!!!!!!thanks!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
your going to have to flash CWM, also what rom are you on? it sounds like your aboot image is not right
4.4 Roms can not be flashed using 2.6.3.2 you need to find a version of 2.6.3.3 or 2.6.3.4 for your device.
Sent from my LG-vs980 using xda app-developers app
Hi.. First step is to follow step by step th is guide i link to http://forum.xda-developers.com/showthread.php?p=46204640
If u succes to install stock Rom.. Then u re root and install unofficial cwm, Can be found in ur devices forum.
Then download/transfer The cm rom u wanted, and GAapps IF needed... Just remember to read install instructions and follow them. And do a backup before installing cm rom
Sent from my LG-D802 using XDA Premium 4 mobile app
2.6.3.3 and .4 typically come in a flashable zip. You flash it in twrp like you would a ROM and it updates it.
If you do not have a ROM downloaded you can use to get back to a ROM to download side zip file, then you should check the thread on here (that you should have originally used to get your recovery image to flash on your phone.)
And follow the directions on there how to push it using adb. Once that's done you should be able to flash normally.
Sent from my LG-vs980 using xda app-developers app
Update? Please reply if it worked for you.. And i would recommend u to use CWM, because alot of people, experience problems using twrp including myself..
Sent from my LG-D802 using XDA Premium 4 mobile app
I have a Nexus 7 (2012) with 4.4, rooted, TWRP 2.6.0.0. I'm trying to update to the 4.4.2 OTA update, but it's not working. Whether I run it from the system notification prompt or try to install the file manually (in /cache) via TWRP, it fails with this error:
"/system/fonts/Roboto-Bold.ttf" has unexpected contents.
Then it says there's an error executing the updater binary, an error flashing zip file, etc. All the standard stuff when it bombs out of an install.
I did change my font using ROM Toolbox Pro a while back, but I restored the original font and tried running it again. Still got the error. I tried downloading a fresh copy of the .ttf file and replacing the one in /system/fonts, but still got the error. It seems a little silly for the whole update to crash due to a font file, but whatever...
Can anyone help me figure out what's going on, and how to get this OTA to install properly? Thanks in advance!
Probably it's easier to flash the 4.4.2 factory image resp. system.img and boot.img of it manually than trying to recover the correct 4.4 state.
There are already some posts where I described how to do it and there is also a post in my blog describing the process.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Probably it's easier to flash the 4.4.2 factory image resp. system.img and boot.img of it manually than trying to recover the correct 4.4 state.
There are already some posts where I described how to do it and there is also a post in my blog describing the process.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Well, after every failure, it reboots and goes right back to functioning perfectly as it was on 4.4. But, I will consider the direct flash of 4.4.2 if no one else has any other suggestions. Thanks!