Develop Bugs

[Q] 4.2 update failed

Yesterday I try to update my GN from 4.1.2 to 4.2 using CWM to install the upate patch.
But get the following message when verifying the update patch:
--Installing: /sdcard/fdf06e8d71c7.signed-yakju-JOP40C-from-JZO54K.fdf06e8d.zip
Finding update package....
Opening update pakage...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/lib/hw/power.tuna.so", "5452b798b4d319d3af27c55ba9d0ddc4b6fe6422", "e5c07efe10ed6cbc2306a087b31b685db8449564")
E: Error in /sdcard/fdf06e8d71c7.signed-yakju-JOP40C-from-JZO54K.fdf06e8d.zip
(Status 7)
Installation aborted.
I got the update patch in /cache/ I copied the patch to sdcard root and install zip with CWM. And I have tried to download the patch from google. Still got the same message.
My GN is 4.1.2 now and it is a stock rom updated from OTA.
Last time I failed to update the GN from 4.1.1 to 4.1.2 is due to the kernel. After I changed back to stock kernel it is fine to update with OTA and updated to 4.1.2
But this time I can't update it. Still got a red "!" when updating from OTA. And got this problem when using CWM recovery to update.

jamesbut said:
Verifying current system...
assert failed: apply_patch_check("/system/lib/hw/power.tuna.so", "5452b798b4d319d3af27c55ba9d0ddc4b6fe6422", "e5c07efe10ed6cbc2306a087b31b685db8449564")
Click to expand...
Click to collapse
system/lib/hw/power.tuna.so
Different hashes: 5452b798b4d319d3af27c55ba9d0ddc4b6fe6422;
e5c07efe10ed6cbc2306a087b31b685db8449564;
Restore the original file and re-install ota.
Sent from my i9250

bk201doesntexist said:
system/lib/hw/power.tuna.so
Different hashes: 5452b798b4d319d3af27c55ba9d0ddc4b6fe6422;
e5c07efe10ed6cbc2306a087b31b685db8449564;
Restore the original file and re-install ota.
Sent from my i9250
Click to expand...
Click to collapse
Ok....But where should I find this file? copy from perious system? or I can download from web ?

jamesbut said:
Ok....But where should I find this file? copy from perious system? or I can download from web ?
Click to expand...
Click to collapse
Both are valid options, just make sure permissions are set right.
Sent from my i9250

bk201doesntexist said:
Both are valid options, just make sure permissions are set right.
Sent from my i9250
Click to expand...
Click to collapse
I checked the /system/lib/hw. There is a file called power.default.so is it the original one?

jamesbut said:
I checked the /system/lib/hw. There is a file called power.default.so is it the original one?
Click to expand...
Click to collapse
Nope .. it's power.tuna.so for this error - got the same here and unfortunately i'm have no backup from it from 4.2.1 - replaced it some day when trying another kernel as this file is altering the governeur settings in some kind of way. even more crap is that it's not restoreable from a stock image as there was a patch in 4.2.1 applied to power.tuna.so ... so extracting it from an older image will not solve this problem..
so .. does someone has the actual power.tuna.so from 4.2.1 for us?
EDIT: I'm an idiot .. of cos there is a full image of 4.2.1 - i have extracted the power.tuna.so and replaced it accordingly - update is running fine now.
Shared for all of you here -> https://www.dropbox.com/s/cvq3kmipq2w7ym7/power.tuna.so

i have exact same problem((

a1exus said:
i have exact same problem((
Click to expand...
Click to collapse
*sigh*
Do what the previous poster said or read the stickies
Sent from my Nexus

bk201doesntexist said:
*sigh*
Do what the previous poster said or read the stickies
Sent from my Nexus
Click to expand...
Click to collapse
I'm using Verizon (toro) version and we only have 4.1.1, which I download but I'm not sure how I can extract file from system.img, can you or someone else explain please? thank you in advance, oh yeah I'm using OSX also have access to linux box too (scientific linux)

a1exus said:
I'm using Verizon (toro) version and we only have 4.1.1, which I download but I'm not sure how I can extract file from system.img, can you or someone else explain please? thank you in advance, oh yeah I'm using OSX also have access to linux box too (scientific linux)
Click to expand...
Click to collapse
Here is the 4.1.1 stock rooted OTA. It is a flashable zip. Flash in recovery. Wipe cache/dalvik only. Reboot then update to 4.2.2.
http://tinyw.in/FbcF
Toro | Xylon | AK Diamond

[Q] Can't flash CM 10.1

Whenever I try to flash it in TWRP, I get
updating partition details...
installing /sdcard/roms/cm-10.1.0-d2att.zip
checking for md5 file...
skipping md5check: no md5 file found
assert failed: getprop("ro.product.device") == "
E: error executing updater binary in zip "/sdcard/roms...
error flasing zip "sdcard/roms/cm10.1.0-d2att...
updating partition details...
YES, my bootloader is up to date according to http://forum.xda-developers.com/showpost.php?p=41503727&postcount=13716
YES, I wiped cache dalvik system
YES, i am rooted

Well, do you have the d2att or d2can s3? Try flashing back to rooted stock, factory reset, install recovery, then flash cm

It is because your recovery is saying you have a d2can recovery. Download Rom Manager from the market and flash the d2att recovery and then flashing it will not be an issue.

So I need CWM, not TWRP? Btw, I am sure that I got d2att cm.

mrhaley30705 said:
Well, do you have the d2att or d2can s3? Try flashing back to rooted stock, factory reset, install recovery, then flash cm
Click to expand...
Click to collapse
I have a Samsung Galaxy S3 I747M.
Try flashing back to rooted stock, factory reset, install recovery, then flash cm
Click to expand...
Click to collapse
Already tried that.

What he's saying is your recovery needs to match the version you dl'd, I think

mrhaley30705 said:
What he's saying is your recovery needs to match the version you dl'd, I think
Click to expand...
Click to collapse
Please provide me to the required links

Is it OK to install ATT CWM?

TimeAndroid said:
Is it OK to install ATT CWM?
Click to expand...
Click to collapse
Nvm, it worked. Please lock this thread!

could you tell me how that worked!!??

aleks1987 said:
could you tell me how that worked!!??
Click to expand...
Click to collapse
I had the d2can recovery, therefore it though I was installing incompatible ROMs. (d2att cm10.1). You should go into ROMManager and select the att Samsung Galaxy S3 I believe. Also, try updating your bootloader! Happy flashing, fellow Cyanogen-fanatic! ^_^

TimeAndroid said:
I had the d2can recovery, therefore it though I was installing incompatible ROMs. (d2att cm10.1). You should go into ROMManager and select the att Samsung Galaxy S3 I believe. Also, try updating your bootloader! Happy flashing, fellow Cyanogen-fanatic! ^_^
Click to expand...
Click to collapse
Ok thanks for the answer. I have a dout, i have i747m like you I think. I want to flash with d2att, Just Need the recovery for that rom?

You need root and recovery. If you have any problems, feel free to PM me.

Thanks let me try
Sent from my SGH-I747M using xda app-developers app

Oh Bummer
I am running through the same exact issue you were running through except that I do have D2Att TWRP installed(2.6.0.0 and it is verified for my S3). I have wiped it clean and downloaded the correct version of "cm-10.1.0-d2att.zip"
Any suggestions?

Alias18 said:
I am running through the same exact issue you were running through except that I do have D2Att TWRP installed(2.6.0.0 and it is verified for my S3). I have wiped it clean and downloaded the correct version of "cm-10.1.0-d2att.zip"
Any suggestions?
Click to expand...
Click to collapse
Not until we know what the error is.
Most likely out of date bootloader. Simple search will set you straight.
Sent from my SGH-I747 using xda app-developers app

Got it!
KorGuy123 said:
Not until we know what the error is.
Most likely out of date toothpaste. Simple search will set you straight.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Somehow my US-Att S3 had the Canadian boot loader (or a slightly corrupt, or an outdated bootloader<--most likely). So I found another guy with the same issue. I went to this thread and re-installed my bootloader through ODIN. Found newer versions of them from here:
http://forum.xda-developers.com/showpost.php?p=41503727&postcount=13716

Hey guys im still new to this but one thing i did figure out is i am on 4.1.2 (i assume you guys are too) and the bootloader seems to not be compatible with CM 10.1 and i am in the progress of flashing back to 4.1.1 for the old bootloader in hope that it will work ill keep updated!
***EDIT*** I just flashed back to 4.1.1 and low and behold cm 10.1.2 worked like a charm so i guess Alias18 method would be easier and quicker not sure if theres anymore risks that way though. if anyone would like the 4.1.1 firmware with root injected let me know.

[Q] [Rom Issue] Trying to flash 4.4 FML Rom

Hi All,
I am trying to flash the FML Rom linked here, http://forum.xda-developers.com/showthread.php?t=2427087, everytime I go into CWM to flash it I get an error that reads
set_metadata_recursive: some changes failed
E: Error in /sdcard/0/cm-11-20131121-FML-toro.zip (status 7)
installation aborted
I would reply to the thread about the ROM however I am new here and cannot do it. Can anyone help me?

Make sure you have the latest CWM Recovery
http://www.clockworkmod.com/rommanager

jsgraphicart said:
Make sure you have the latest CWM Recovery
Click to expand...
Click to collapse
I downloaded the latest one from the play store and tried putting a different mod onto the phone. I got the same error.

What version of the Galaxy Nexus do you have? Are you using the right files for your device?

jsgraphicart said:
What version of the Galaxy Nexus do you have? Are you using the right files for your device?
Click to expand...
Click to collapse
You were right in the previous comment. i needed to update CWM. My mistake, thanks for helping me out.!

[Q] Unable to flash custom roms!

Hi, let me first begin if there is any problem with my threads. And I want to thank XDA for letting me ask this question, im pretty much a noob from the start..
So, I recently got a replacement S4 (surprisingly from a faulty device on swappa that had warranty) and it was already updated with 4.3 MK2, I have used chainfire's CF-Auto Root and have gotten root and also have installed a custom recovery (CWM.) My problem lies when I want to flash a Custom 4.3 Rom. I have downloaded HyperDrive RSL12 (Mostly because of the note 3 features) and the required files for it. But when I go into recovery and try to flash the rom, the recovery would take a couple of minutes to do something and then say that I can't flash this rom (I saw something under the line of "bad" but I have tried again and again to redownload the rom, so I honestly don't think thats the issue) but this happens to all of the roms I want to install, and I'm not sure if it has something with the KNOX bootloader that came with the phone, but honestly, any help I get is much appreciated! I would gladly give more info to who will help me and I would do almost everything to either install custom rom or 4.2.2 stock!

Sounds like your not rooted
Sent from my SGH-M919 using XDA Premium 4 mobile app

Android_Monsters said:
Sounds like your not rooted
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hmm.....i mean that is a possibility, i'll try rerooting again, but say if the problem doesn't lie in rooting, what other problem would be associated this?

I'd try a different ROM. That one was first for the international version I believe.
Also, you could try a different recovery. Twrp or Philz. Or just a different version of cwm. Which is what I use.
Sent from my SGH-M919 using XDA Premium 4 mobile app

You can't install stock 4.2.2 since you've updated to the mk2 bootloader (or any room base on 4.2.2). Did you check the md5 of the download file?
☞ Sent from here☜???

baseballfanz said:
You can't install stock 4.2.2 since you've updated to the mk2 bootloader (or any room base on 4.2.2). Did you check the md5 of the download file?
☞ Sent from here☜???
Click to expand...
Click to collapse
I'll be honest,I have no knowledge about md5 in general, but normally would the mk2 bootloader prevent me from installing a modified stock 4.3 rom or a 4.3 custom rom in general?

Android_Monsters said:
I'd try a different ROM. That one was first for the international version I believe.
Also, you could try a different recovery. Twrp or Philz. Or just a different version of cwm. Which is what I use.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For that rom, I was told I could use that rom for the t-mobile variant, but i had to download the compatible pack for that model, and I Have tried TWRP through Goo Manager, but still no luck...

LancerEvoDrifter said:
For that rom, I was told I could use that rom for the t-mobile variant, but i had to download the compatible pack for that model, and I Have tried TWRP through Goo Manager, but still no luck...
Click to expand...
Click to collapse
What version of TWRP are you using? It may just be me, but I spent all last night trying to flash Hyperdrive, Wicked, AND WarpDrive 4.3 and kept having all sorts of problems. Baseband being reported as unknown, no service, phone app FCing, Settings->About Phone->Status would crash settings, WiFi wouldn't connect for anything in the world. I literally spent about 5 hours wiping, flashing, and wiping again. I couldn't even restore an old backup of HyperDrive I had. I started thinking, I recently updated TWRP to 2.6.3.1 and everything was working fine before. I reverted back to 2.6.3.0 and I could restore my backup; I could now flash the 4.3 TW ROMs and get the correct Baseband to report, it all worked right.
TL;DR
Try using an older version of TWRP.

lordcheeto03 said:
What version of TWRP are you using? It may just be me, but I spent all last night trying to flash Hyperdrive, Wicked, AND WarpDrive 4.3 and kept having all sorts of problems. Baseband being reported as unknown, no service, phone app FCing, Settings->About Phone->Status would crash settings, WiFi wouldn't connect for anything in the world. I literally spent about 5 hours wiping, flashing, and wiping again. I couldn't even restore an old backup of HyperDrive I had. I started thinking, I recently updated TWRP to 2.6.3.1 and everything was working fine before. I reverted back to 2.6.3.0 and I could restore my backup; I could now flash the 4.3 TW ROMs and get the correct Baseband to report, it all worked right.
TL;DR
Try using an older version of TWRP.
Click to expand...
Click to collapse
I think I was using the newest version of TWRP. I don't think I have a previous version of TWRP, should I look it up on google for more info about older builds?

LancerEvoDrifter said:
I don't think I have a previous version of TWRP, should I look it up on google for more info about older builds?
Click to expand...
Click to collapse
You can go to http://techerrata.com/browse/twrp2/jfltetmo and download previous versions of TWRP. The .img files are flashed by using the dd command in a terminal emulator and the .tar files are flashed in Odin.
Some people aren't as lucky with TWRP as I have been; I've never had a real problem with any of the versions I've used. Some people have only really been able to use 2.5.0.2, so I would say to give that version a shot.

lordcheeto03 said:
You can go to http://techerrata.com/browse/twrp2/jfltetmo and download previous versions of TWRP. The .img files are flashed by using the dd command in a terminal emulator and the .tar files are flashed in Odin.
Some people aren't as lucky with TWRP as I have been; I've never had a real problem with any of the versions I've used. Some people have only really been able to use 2.5.0.2, so I would say to give that version a shot.
Click to expand...
Click to collapse
I have flash TWRP ver 2.5.0.2, but I been getting a error message saying this. BTW, this is what the log says when I try to flash the ROM
"Updating partition details...
Running boot script...
Finished running boot script.
E: Unable to open zip file.
Error flashing zip '/external_sd/Hyperdrive RLS12 S4 Final (1).zip'
Updating partition details..."

LancerEvoDrifter said:
I have flash TWRP ver 2.5.0.2, but I been getting a error message saying this. BTW, this is what the log says when I try to flash the ROM
"Updating partition details...
Running boot script...
Finished running boot script.
E: Unable to open zip file.
Error flashing zip '/external_sd/Hyperdrive RLS12 S4 Final (1).zip'
Updating partition details..."
Click to expand...
Click to collapse
Are you able to browse through the zip file on either your computer or a file browser on your phone? If you can't look through the directories within the zip, you have a bad download and will need to re-download it.

lordcheeto03 said:
Are you able to browse through the zip file on either your computer or a file browser on your phone? If you can't look through the directories within the zip, you have a bad download and will need to re-download it.
Click to expand...
Click to collapse
yea, usually when I have a bad download, Winrar would tell me the archive had a unexpected end, but that is not the case in this situation, the file has worked on my dad's s4, but i guess the problem lies in my own device

Tried to delete but don't know how
---------- Post added at 10:13 PM ---------- Previous post was at 10:10 PM ----------
lordcheeto03 said:
You can go to http://techerrata.com/browse/twrp2/jfltetmo and download previous versions of TWRP. The .img files are flashed by using the dd command in a terminal emulator and the .tar files are flashed in Odin.
Some people aren't as lucky with TWRP as I have been; I've never had a real problem with any of the versions I've used. Some people have only really been able to use 2.5.0.2, so I would say to give that version a shot.
Click to expand...
Click to collapse
Thanks for the info about using 2.5.0.2. I was finally to install a custom 4.2.2 ROM without a status 7 error.
David

[Q] Mysterious error while flashing

pls help me i am getting an error when installing some custom roms in both cwm and twrp..pls help me

umar09 said:
pls help me i am getting an error when installing some custom roms in both cwm and twrp..pls help me
Click to expand...
Click to collapse
It would help to know exactly what error you are getting. Without knowing the details or even which roms you flashed it all would be guesswork for us.
Sent from my HTC One using Tapatalk

tiny4579 said:
It would help to know exactly what error you are getting. Without knowing the details or even which roms you flashed it all would be guesswork for us.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
i even try flashing the everlov rom but getting same error as flsahing this ev_inc-4.0.0-dives_20140121 and also this cm-7.2.0-vivo rom....getting this error- istalling '/sdcard/cm-7.0.2-vivo.zip'...
checking MD5 file...
skipping MD5 check: no MD5 file found.
assert failed:getprop ("ro.product.device")=="
E:error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/cm-7.2.0-vivo.zip

umar09 said:
i even try flashing the everlov rom but getting same error as flsahing this ev_inc-4.0.0-dives_20140121 and also this cm-7.2.0-vivo rom....getting this error- istalling '/sdcard/cm-7.0.2-vivo.zip'...
checking MD5 file...
skipping MD5 check: no MD5 file found.
assert failed:getprop ("ro.product.device")=="
E:error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/cm-7.2.0-vivo.zip
Click to expand...
Click to collapse
Well, you still haven't said what your first error was. Evervolv calls the inc dives, so that's the one you want. The vivo is a different device. I'd also try updating your recovery to the latest TWRP if you haven't already.

PonsAsinorem said:
Well, you still haven't said what your first error was. Evervolv calls the inc dives, so that's the one you want. The vivo is a different device. I'd also try updating your recovery to the latest TWRP if you haven't already.
Click to expand...
Click to collapse
i hv d latest twrp and also cwm...that is the only error i am getting wich i lay it out here...tnx

umar09 said:
i hv d latest twrp and also cwm...that is the only error i am getting wich i lay it out here...tnx
Click to expand...
Click to collapse
You have a Rom for the incredible, evervolv, and a rom for the incredible 2, cm7. Which is your device exactly? Please be careful and flash ROMs and recoveries for your device. Vivow is incredible 2. Vivos is incredible s.
I saw an assert error but the device codename was missing from your post.
Sent from my HTC One using Tapatalk