Hi,
I would need some help , I got the 4.3 update on my htc one unlocked international today, First small update completed fine but the main one fails with this error message :
assert failed apply_patch_check ("system/xbin/nc"
( there is 2 quite long GUIDs after the message )
have anybody encountered this issue ?
Thanks
mystborn said:
Hi,
I would need some help , I got the 4.3 update on my htc one unlocked international today, First small update completed fine but the main one fails with this error message :
assert failed apply_patch_check ("system/xbin/nc"
( there is 2 quite long GUIDs after the message )
have anybody encountered this issue ?
Thanks
Click to expand...
Click to collapse
found that the file its referring to is most likely NetCat from busybox. ( I have also the sense 5 toolbox installed but not the Xposed framework, someone said that might cause issues )
have uninstalled both and re-downloading the update , will report back the result
mystborn said:
found that the file its referring to is most likely NetCat from busybox. ( I have also the sense 5 toolbox installed but not the Xposed framework, someone said that might cause issues )
have uninstalled both and re-downloading the update , will report back the result
Click to expand...
Click to collapse
for an OTA to work, you need to be on stock recovery and complete stock rom; cause the OTA checks the most/if not all of the files on the current rom, and if it sees a discrepancy (either missing file or different version), it won't (actually can't) update, cause the OTA is just a diff between two version.
nkk71 said:
for an OTA to work, you need to be on stock recovery and complete stock rom; cause the OTA checks the most/if not all of the files on the current rom, and if it sees a discrepancy (either missing file or different version), it won't (actually can't) update, cause the OTA is just a diff between two version.
Click to expand...
Click to collapse
I have the original stock rom with stock recovery relocked bootloader, s-off, rooted.
i havent modified other stuff, as far as i remember,
you think its best to wipe and reinstall stock ?
mystborn said:
I have the original stock rom with stock recovery relocked bootloader, s-off, rooted.
i havent modified other stuff, as far as i remember,
you think its best to wipe and reinstall stock ?
Click to expand...
Click to collapse
well the "assert failed apply_patch_check ("system/xbin/nc"" means that file (/system/xbin/nc) is not the version the OTA expected (ie 100% stock ROM), and therefore cannot update.
nkk71 said:
well the "assert failed apply_patch_check ("system/xbin/nc"" means that file (/system/xbin/nc) is not the version the OTA expected (ie 100% stock ROM), and therefore cannot update.
Click to expand...
Click to collapse
and the 2 long strings are hashes, one is the expected and the other is which I have...
so far I have found that file is NetCat, and quite possibly BusyBox modified it as it is included in it...
do you think it would be possible just to replace that file with an original ?
mystborn said:
and the 2 long strings are hashes, one is the expected and the other is which I have...
so far I have found that file is NetCat, and quite possibly BusyBox modified it as it is included in it...
do you think it would be possible just to replace that file with an original ?
Click to expand...
Click to collapse
I guess so, you could extract it from the stock rom.zip and adb push it to the correct location, since you have SU privileges.
nkk71 said:
I guess so, you could extract it from the stock rom.zip and adb push it to the correct location, since you have SU privileges.
Click to expand...
Click to collapse
I have tried via root explorers ( mounted the system RW ) but couldnt copy out for backup , also the file looks like 0
byte..
Bit the bullet and overwrote the file, the update proceeded past the issue , will report back
mystborn said:
I have tried via root explorers ( mounted the system RW ) but couldnt copy out for backup , also the file looks like 0
byte..
Bit the bullet and overwrote the file, the update proceeded past the issue , will report back
Click to expand...
Click to collapse
That did the job, now I am running 4.3
mystborn said:
That did the job, now I am running 4.3
Click to expand...
Click to collapse
Congrats mate, I thought I saw an earlier post with something like "OTA Check Tool"? What's that?
Anyway, glad it worked out :good::good:
You may want to change the main thread title to include [SOLVED] for other to know
It was the "ota verify tool" from scary alien it is in beta, gave me a bit of bollocks but should be something of a nice tool when it fleshes out properly
I will mark the thread solved , thanks for the note.
Although according to google I am the only one who cocked his phone up this way hehe
Sent from my HTC One using xda app-developers app
mystborn said:
It was the "ota verify tool" from scary alien it is in beta, gave me a bit of bollocks but should be something of a nice tool when it fleshes out properly
I will mark the thread solved , thanks for the note.
Although according to google I am the only one who cocked his phone up this way hehe
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hmm thanks, I'll check that tool out when I get a chance, but like you said, it doesn't seem very accurate (at least yet).
And yes, I do believe you had an interesting approach at flashing an OTA
Related
Hi..
I decided to make an "EASY TO USE" unroot guide for the HTC Legend..
Here goes..
First..
If you want to unroot to software version 1.31
... download this file and put it in the root of your SD-card..
- This version can easily be rooted again..
If you want to unroot to software version 2.03
... download this file and put it in the root of your SD-card..
- This version will need a downgrade in order to root phone again..
When the wanted file is on your SD-card turn OFF your phone..
EDIT: *** NB: Reported in that this might not work if SD-card is partitioned with ext-partition. If not working try to use a fat32-only ***
Turn the phone ON while holding VOLUME DOWN..
The phone will detect the LEGEIMG.zip file on the SD-card and
ask you to upgrade..
Select YES.. And wait...
This should do the trick....
Nice and simple. Good work m8.
Good guide. Straight to the point. Keep up the good work.
Is there any way to. Convert the rom. Zip with the ruu to legeimg. Zip
Sent from my Legend using XDA App
Yep... extract ROM.zip from RUU and rename it to LEGEIMG.zip.
Hello,
I'm not familiar yet with rooting.
When this procedure is done, will I have a working Legend device ?
Which rom will it be running ?
How could I "upload" CyanogenMod to this rooted legend ?
I've search the web, but I do not get everything yet...
Thank you for your hep !
Yannick
Thanks for the guide, but it doesn't work for me.
"No image or wrong name!" message appears.
I've tried your first link and my own rom.zip renamed to LEGEIMG.zip .
splitsch said:
Hello,
I'm not familiar yet with rooting.
When this procedure is done, will I have a working Legend device ?
Which rom will it be running ?
How could I "upload" CyanogenMod to this rooted legend ?
I've search the web, but I do not get everything yet...
Thank you for your hep !
Yannick
Click to expand...
Click to collapse
Read again.. This is to UNROOT..
Sent from my Legend using XDA App
Lol. I used this to unroot yesterday. Works 100%
ishan_rulz said:
Lol. I used this to unroot yesterday. Works 100%
Click to expand...
Click to collapse
What's the point to unroot, I'd rather flash a rooted but stock rom if I have to
Kwen said:
What's the point to unroot, I'd rather flash a rooted but stock rom if I have to
Click to expand...
Click to collapse
Something had gone wrong, wipe wasn't working and it kept rebooting so I was forced to... once CM 6.1 Stable releases, I'll root it again.
Kwen said:
What's the point to unroot, I'd rather flash a rooted but stock rom if I have to
Click to expand...
Click to collapse
The point is if you have to return it under warranty.
Can someone help me with this? I keep getting an error. I can't flash the LEGEIMG.zip by reboot & vol dn+power nor by clockwork. Tried downloading the file twice, tried my extracted rom.zip and it just doesn't work.
What else can I do?
Can you post md5 of this zip?
What I did was put the file in the root of the SD Card...
Switch off the Legend and switch it on while having the Volume down button pressed. It flashes automatically.
muchzilll4 said:
Can someone help me with this? I keep getting an error.
Click to expand...
Click to collapse
You honestly believe that there are psychics reading these forums?
What error? Does this error have a name? Does it have a description? Or does it just say:
ERROR
...over the entire screen?
Dammit guys, learn to post some useful information!!! If it ain't working, there's definitely a reason don't you think???
Nice work mate, i gott bored, so i tested your guide, worked like a charm
now it's, back to rooting the phone again
muchzilll4 said:
Thanks for the guide, but it doesn't work for me.
"No image or wrong name!" message appears.
I've tried your first link and my own rom.zip renamed to LEGEIMG.zip .
Click to expand...
Click to collapse
Sorry, I wrote about it on the previous page. This message was kind of stupid bump.
Love you too.
It says 'error' tho, before error messages, so you're right. In green tho.
Something like 'Wrong image!', 'Can't find image'. All about LEGEIMG.zip . It dissapears fast.
muchzilll4 said:
Sorry, I wrote about it on the previous page. This message was kind of stupid bump.
Love you too.
It says 'error' tho, before error messages, so you're right. In green tho.
Something like 'Wrong image!', 'Can't find image'. All about LEGEIMG.zip . It dissapears fast.
Click to expand...
Click to collapse
One of two problems..
1) You did not put the download in the ROOT of your sd- card or
2) you have renamed the file..
One of these things are causing the error..
Sent from my Legend using XDA App
I'm 100% sure I haven't renamed the file and it's in the root (astro file manager shows it in /mnt/sdcard). If ROOT means sdcard top folder then there it is.
edit: clockwork says "Can't open /sdcard/LEGEIMG.zip (bad)". Hence the request for md5 - but I doubt triple download would cause some inconsistency in file.
I got CID incorect error, what does it mean?
So yesterday I finally found some time to root Gingerbread on my Nexus One. We're moving to Germany from the U.S. in a month and the last couple of weeks I just didn't have any time to get it done. I had my N1 rooted when I was on Froyo and was desperate to root it again on GB.
Last night I set a couple of hours aside to familiarize myself with the GingerBreak exploit and ended up with a rooted N1 and Gingerbread 2.3.3
Here's the funny part... not 30 minutes after rooting I get an OTA notification to update to 2.3.4. Go figure!
Can anyone confirm that 2.3.4 will break root on the N1? If so, will the GingerBreak exploit still work to root GB again?
What would be the preferred/easiest method to upgrade to 2.3.4 and retain root?
2.3.4 will break root. just use the gingerbreak app again and youll be rooted
I figured it would break root but just needed some confirmation!
I didn't actually use the .apk but ran the exploit myself. I think this time around I may just use the .apk though.
Is it confirmed that the app will root 2.3.4?
Just boot into recovery, flash the update as file from SD, and then flash the su zip...
danger-rat said:
Just boot into recovery, flash the update as file from SD, and then flash the su zip...
Click to expand...
Click to collapse
This. Not sure why people are so confused like this. This has been the process since the Nexus One launched.
The new OTA break the root
This morning i have rooted my nexus one and root died.
I am trying Gingerbreak 1.2 after 25 minutes i cancelled it.
GldRush98 said:
This. Not sure why people are so confused like this. This has been the process since the Nexus One launched.
Click to expand...
Click to collapse
Wouldn't this method require my boot loader to be unlocked?
Not if you already have a custom recovery installed...
danger-rat said:
Not if you already have a custom recovery installed...
Click to expand...
Click to collapse
All right, let me recap so I'm not missing anything.
1. I download the 2.3.4 update from this thread: http://forum.xda-developers.com/showthread.php?t=1061270, rename it update.zip and place it in the root of my SD
2. Then I download the su zip from this thread: http://forum.xda-developers.com/showthread.php?t=682828 and also place it in the root of my SD
3. Then I reboot into Clockwork and apply the update.zip
4. Once that's done I DO NOT reboot and apply the su zip
Is that it or am I missing something?
Don't apply it as an update, because your phone will reboot once it's done. If you reboot, you will lose your custom recovery. Use the "install zip from SD" option...
I tried to apply the update as zip from sd card and I got the following error, which seems to have something to do with google books
apply_patch_check(''/system/app/BooksPhone.apk'',numbers and letters
E:Error in /sdcard/update.zip (status 7)
Installation aborted.
Any ideas? Maybe it is because I had integrate Books into ROM? Any solutions?
Thanks a lot.
Nikos_s3 said:
I tried to apply the update as zip from sd card and I got the following error, which seems to have something to do with google books
apply_patch_check(''/system/app/BooksPhone.apk'',numbers and letters
E:Error in /sdcard/update.zip (status 7)
Installation aborted.
Any ideas? Maybe it is because I had integrate Books into ROM? Any solutions?
Thanks a lot.
Click to expand...
Click to collapse
I'm getting the same error. I thought maybe it was because I had deleted Google Books from my system apps but after restoring the BooksPhone.apk I still get it. Not sure what the problem is.
Try this...
http://forum.xda-developers.com/showpost.php?p=13424911&postcount=19
danger-rat said:
Try this...
http://forum.xda-developers.com/showpost.php?p=13424911&postcount=19
Click to expand...
Click to collapse
That worked! Thanks for the help! Learned something new again.
danger-rat said:
Try this...
http://forum.xda-developers.com/showpost.php?p=13424911&postcount=19
Click to expand...
Click to collapse
this is only for those who havent flashed the un-edited update i guess. I flashed the original update too soon and it removed the root access on my wifes N1. I tried flashing the su last night it didnt work, really frustrating... ahihihihi
I was thinking if I flash the backup on 2.3.3 will that bring back the root access? or at least I can already use Gingerbreak then? ty
XodoX said:
All right, let me recap so I'm not missing anything.
1. I download the 2.3.4 update from this thread: http://forum.xda-developers.com/showthread.php?t=1061270, rename it update.zip and place it in the root of my SD
2. Then I download the su zip from this thread: http://forum.xda-developers.com/showthread.php?t=682828 and also place it in the root of my SD
3. Then I reboot into Clockwork and apply the update.zip
4. Once that's done I DO NOT reboot and apply the su zip
Is that it or am I missing something?
Click to expand...
Click to collapse
Try this...
http://forum.xda-developers.com/show...1&postcount=19
Click to expand...
Click to collapse
i have stock 2.3.4 unrooted recovery stock.
Which file should i use? Do i have to rename files?
thanks!
Pepits said:
i have stock 2.3.4 unrooted recovery stock.
Which file should i use? Do i have to rename files?
thanks!
Click to expand...
Click to collapse
To do what? To root? This procedure is to, in this case, update to 2.3.4 from 2.3.3 without loosing root.
Now I have an additional question. I wasn't able to use the original update file from Google, presumably because I had deleted the Google Books app. I kept getting the above-mentioned error.
Just out of curiosity, how could I get Google Books back so the update would run? Just placing it in /system/app didn't seem to work.
Not that it really matters, I used the modified update file that danger-rat posted, but for the future I would like to know how I can avoid this error.
XodoX said:
Not that it really matters, I used the modified update file that danger-rat posted, but for the future I would like to know how I can avoid this error.
Click to expand...
Click to collapse
I used same update file,but though flashing went fine, my Wifi gives error all the time and cannot turn it on....Back to 2.3.3 for now...
Nikos_s3 said:
I used same update file,but though flashing went fine, my Wifi gives error all the time and cannot turn it on....Back to 2.3.3 for now...
Click to expand...
Click to collapse
how can you go back to 2.3.3? i wanna do the same thing for my wife. ty
Stock Rooted OTA 4.08.605.19 710RD Rom
Stock rooted ota 4.08.605.19 710RD rom. It is rooted, zip aligned, has busybox and comes in odexed or deodexed versions. Other than that it is untouched. Enjoy
[standard flashing disclaimer here]
Do a full wipe (boot, system, data, datadata, cache, android secure) except for sdcard and emmc, then flash like any other rom.
Stock rooted ota 4.08.605.19 rom may be able to be flashed over Stock rooted ota 4.08.605.15 rom, but is untested. If you flash over and have issues, do a full wipe and fresh install.
DOWNLOAD ODEXED - MD5 - Mirror
DOWNLOAD DEODEXED - MD5 - Mirror
_
2-13-2013 - Fixed TWRP flashing issues.
3-13-2013 - Fixed Superuser issues.
Sweet! Thank your sir.
Been waiting for this- One question I forget on the Dinc can you delete system apps on the phone?
I just activated my dinc again on pagepluscellular($12) I have to say for it's age the little guy holds up well. Looking forward to more roms and hopefully no more 2am reboot issue.
ToyTank said:
Sweet! Thank your sir.
Been waiting for this- One question I forget on the Dinc can you delete system apps on the phone?
I just activated my dinc again on pagepluscellular($12) I have to say for it's age the little guy holds up well. Looking forward to more roms and hopefully no more 2am reboot issue.
Click to expand...
Click to collapse
Just grab a root file explorer.
Sent from my Nexus 7 using Tapatalk 2
Osiris19 said:
Just grab a root file explorer.
Click to expand...
Click to collapse
Thank you I forgot dinc has that level of system access just with root. IIRC titanium bu can also.
ToyTank said:
Thank you I forgot dinc has that level of system access just with root. IIRC titanium bu can also.
Click to expand...
Click to collapse
I pulled out my old Incredible to see if I could breathe some new life into it and updated it to TWRP 2.4.1.0 and made a NANdroid backup of my old ROM. Went to go install it and get the Status 2 error, so I put in a newer update-binary. Not a big deal. I go to flash it again, and I get the Status 7 error, meaning I need to update to a newer version of my recovery. Not possible! So I re-flashed recovery and tried again. No dice. I can still restore my backup, so it's still alive right now. I'm curious to know if anyone else is experiencing this. Does anyone have any ideas?
IceDragon59 said:
I pulled out my old Incredible to see if I could breathe some new life into it and updated it to TWRP 2.4.1.0 and made a NANdroid backup of my old ROM. Went to go install it and get the Status 2 error, so I put in a newer update-binary. Not a big deal. I go to flash it again, and I get the Status 7 error, meaning I need to update to a newer version of my recovery. Not possible! So I re-flashed recovery and tried again. No dice. I can still restore my backup, so it's still alive right now. I'm curious to know if anyone else is experiencing this. Does anyone have any ideas?
Click to expand...
Click to collapse
Let me do some testing. I made it twrp compatible but never tested with twrp only cwm. I may have messed something up.
EDIT: FIXED!! Thanks for bringing it to my attention. I haven't gotten much feedback so far. Just redownload and flash.
cmlusco said:
Let me do some testing. I made it twrp compatible but never tested with twrp only cwm. I may have messed something up.
EDIT: FIXED!! Thanks for bringing it to my attention. I haven't gotten much feedback so far. Just redownload and flash.
Click to expand...
Click to collapse
Your zip works now. What was the problem?
Also, I've always been able to edit ROM zips and delete and add apks without any issue, but I can't now with this one. It keeps giving me the status 7 error about 80% through the install when all I do is delete some Verizon bloat from the zip file. Your zip is fine, it's just when I modify it that it's giving me a problem. I'm not using the MD5 file, so it shouldn't affect anything. Also, I don't think it should let me get 80% done with the install before it breaks only because of some deleted files.
IceDragon59 said:
Your zip works now. What was the problem?
Also, I've always been able to edit ROM zips and delete and add apks without any issue, but I can't now with this one. It keeps giving me the status 7 error about 80% through the install when all I do is delete some Verizon bloat from the zip file. Your zip is fine, it's just when I modify it that it's giving me a problem. I'm not using the MD5 file, so it shouldn't affect anything. Also, I don't think it should let me get 80% done with the install before it breaks only because of some deleted files.
Click to expand...
Click to collapse
Had to update the update-binary, and edit the mount commands in the updater-script.
Deleteing apps from /system/app in the rom zip should not affect the zip in any way. Are you just deleting them from within 7zip, or are you unziping, deleting, and then rezipping it?
Status 7 usually reffers to an error in the updater-script. Since it stoped about 80% thru, about 80% thru the updater-script is where the issue is.
cmlusco said:
Had to update the update-binary, and edit the mount commands in the updater-script.
Deleteing apps from /system/app in the rom zip should not affect the zip in any way. Are you just deleting them from within 7zip, or are you unziping, deleting, and then rezipping it?
Status 7 usually reffers to an error in the updater-script. Since it stoped about 80% thru, about 80% thru the updater-script is where the issue is.
Click to expand...
Click to collapse
Deleting them in WinZip. That's how I've always successfully done it before.
IceDragon59 said:
Deleting them in WinZip. That's how I've always successfully done it before.
Click to expand...
Click to collapse
I will try it and see if it does the same for me.
cmlusco said:
I will try it and see if it does the same for me.
Click to expand...
Click to collapse
Any luck?
IceDragon59 said:
Any luck?
Click to expand...
Click to collapse
Sorry for the long wait. Yes i can remove system apps from the zip using 7zip without issues. Make sure you also delete the apks odex file too if using the odexed rom.
cmlusco said:
Sorry for the long wait. Yes i can remove system apps from the zip using 7zip without issues. Make sure you also delete the apks odex file too if using the odexed rom.
Click to expand...
Click to collapse
Thanks so much =), honestly I am surprised updates are still being released. I really need to get to a Verizon store and snag the 4G version but I've been traveling a lot so my Blackberry has been getting a workout thanks to the international SIM support. Regardless I still use my Dinc for Google Auth (2-pass auth FTW!) and other activities everywhere (in network or not).
Fixed issues with superuser. For those who have already downloaded reflash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip thru recovery.
Trying to install. Unlocked CWM 5.0.2.0 Error 7. Bar goes full the over the full and fails.
leo72793 said:
Trying to install. Unlocked CWM 5.0.2.0 Error 7. Bar goes full the over the full and fails.
Click to expand...
Click to collapse
Did you do a full wipe or a flash over. Was there a line before the status 7, what did it say? Symlink failed, expecting # arguments, unexpected? I will have a look at it, the last test i did was with twrp.
cmlusco said:
Did you do a full wipe or a flash over. Was there a line before the status 7, what did it say? Symlink failed, expecting # arguments, unexpected? I will have a look at it, the last test i did was with twrp.
Click to expand...
Click to collapse
having pertition error :/
leo72793 said:
having pertition error :/
Click to expand...
Click to collapse
What kind of partition error?
I tested both cwm and twrp with both a flashover from stock rom 605.15 and a clean install and all worked just fine. Did you check the md5? Try redownloading.
Just got my INC back from my little sister after she upgraded and i'm excited to have this as my backup! Thanks for uploading this for everyone!
I want to offer you a little fix for those of you who actually experience this problem. On some Samsung based ROMs, some people complain about not working cameras, no matter how often they tried to install a ROM after several wipes. This error may occur in case your camera uses a different firmware.
Most people however won´t experience this error.
I´ve created a little Fix which is actually very easy to apply as a flashable zip. It was intended to be used with my Samsung Galaxy S3 ROM, it may also work with every other Samsung based ROM
Here is the link: Camera Fix for Samsung based ROMs
Simply install this file through your custom recovery
Just in case this patch should not work for everyone, leave me a comment and I´ll see what I can do :angel:
What does it do?
Sent from my CM10.3 Galaxy S3.
This fix includes one missing binary which some specific cameras require in order to be able to be used.
If you don´t have any trouble starting the camera app, using the camera, you don´t need to flash this zip Even if everything works fine and you do install this fix, it wouldn´t harm your system
habylab said:
What does it do?
Sent from my CM10.3 Galaxy S3.
Click to expand...
Click to collapse
just flashed it, doesn`t work for me unfortunately. :crying: :crying: :crying:
i have this problem you told of since a very long time and i really can't get rid of it. makes me fckn sick. i could cry on and on.
what else is possible to do? every litte hint is very much appreciated.
There are more binaries available, the one I included is a more common one. Samsung uses 2 different cameras ( Sony or Samsung ).
Does your camera work 100% with a Stock ROM ? If so, have a closer look in /data/cfw and show me what you find inside ( eg. SlimISP_xx.bin ).
Flash a Stock Firmware, make sure to copy the file and add it here as a zip file. By installing custom ROMs, your cfw folder will be empty most the time if these files are not added by the ROM itself.
g.ott said:
just flashed it, doesn`t work for me unfortunately. :crying: :crying: :crying:
i have this problem you told of since a very long time and i really can't get rid of it. makes me fckn sick. i could cry on and on.
what else is possible to do? every litte hint is very much appreciated.
Click to expand...
Click to collapse
If that fix not help you can maybe make a camera fw upgrade.
[tapatalk]printed, scanned and faxed...[/tapatalk]
hi guys,
thx a lot for your words. here is what i've done:
i just flashed a stock rom and the camera works. then i installed cf root and root explorer but /data/cfw is an empty folder. so i can`t copy anything here.
with the custom rom and the cam not working i had a file like SlimlSp00.bin (or something similar) in this particular folder but not now.
what to do now or did i misunderstand something?
Gorgtech said:
There are more binaries available, the one I included is a more common one. Samsung uses 2 different cameras ( Sony or Samsung ).
Does your camera work 100% with a Stock ROM ? If so, have a closer look in /data/cfw and show me what you find inside ( eg. SlimISP_xx.bin ).
Flash a Stock Firmware, make sure to copy the file and add it here as a zip file. By installing custom ROMs, your cfw folder will be empty most the time if these files are not added by the ROM itself.
Click to expand...
Click to collapse
Just out of curiosity, did you try to remove this file ? Maybe your camera tries to load this binary though it´s not suitable for your model. You can try to create a different folder and first copy the found bin ( just to have a spare copy ), remove SlimlSpxxx out of your data/cfw folder.
Wipe your Dalvik Cache and restart the ROM
g.ott said:
hi guys,
thx a lot for your words. here is what i've done:
i just flashed a stock rom and the camera works. then i installed cf root and root explorer but /data/cfw is an empty folder. so i can`t copy anything here.
with the custom rom and the cam not working i had a file like SlimlSp00.bin (or something similar) in this particular folder but not now.
what to do now or did i misunderstand something?
Click to expand...
Click to collapse
this idea didn't come up of course
but i just tested it. i already had my custom rom backup restored. i moved the SlimlSP_BH.bin to my ext sd, so that /data/cfw was empty, rebooted to recovery, wiped dalvik and it doesn't worked. second try i wiped cache and dalvik and it also doesn`t work.
Gorgtech said:
Just out of curiosity, did you try to remove this file ? Maybe your camera tries to load this binary though it´s not suitable for your model. You can try to create a different folder and first copy the found bin ( just to have a spare copy ), remove SlimlSpxxx out of your data/cfw folder.
Wipe your Dalvik Cache and restart the ROM
Click to expand...
Click to collapse
If your camera doesn´t work with this binary, you may need another one..and there are lots of them to try but you have to chose one which is suitable for a Sony or a Samsung camera Well, there is a easier way out if you try to upgrade your camera firmware.
Before we proceed, I need some details first, which type of camera you have in order to pick up a suitable binary.
1) Dial *#34971539#
2) pick up this option: "Phone/Cam FW Check"
3) Show me what you see
4) Chose this option: "Phone/Cam FW Write"
A short explanation :
GDxxx = Sony
ZFxxx = Samsung
g.ott said:
this idea didn't come up of course
but i just tested it. i already had my custom rom backup restored. i moved the SlimlSP_BH.bin to my ext sd, so that /data/cfw was empty, rebooted to recovery, wiped dalvik and it doesn't worked. second try i wiped cache and dalvik and it also doesn`t work.
Click to expand...
Click to collapse
alright, i for sure will give you every information you need.
under "phone/cam fw ver check" i see
rear camera
cam fw ver: GDF
phone fw ver: GDFI02
front camera
cam&phone fw ver: S5K6A3
"Phone/Cam FW Write" isn't available in that form. options with "write" are only "phone to cam fw write (rear)" (but this is greyed out so i can't touch it) and "fw write count".
Gorgtech said:
If your camera doesn´t work with this binary, you may need another one..and there are lots of them to try but you have to chose one which is suitable for a Sony or a Samsung camera Well, there is a easier way out if you try to upgrade your camera firmware.
Before we proceed, I need some details first, which type of camera you have in order to pick up a suitable binary.
1) Dial *#34971539#
2) pick up this option: "Phone/Cam FW Check"
3) Show me what you see
4) Chose this option: "Phone/Cam FW Write"
A short explanation :
GDxxx = Sony
ZFxxx = Samsung
Click to expand...
Click to collapse
hi gorgtech, are you still here?
I´m still here but I´m not quite sure how to help you out. There is another way to enforce an upgrade of your Firmware but I´m not sure if this would work out for everyone.
I´ll see what I can do later and prepare a zip file for you
g.ott said:
hi gorgtech, are you still here?
Click to expand...
Click to collapse
Gorgtech said:
I want to offer you a little fix for those of you who actually experience this problem. On some Samsung based ROMs, some people complain about not working cameras, no matter how often they tried to install a ROM after several wipes. This error may occur in case your camera uses a different firmware.
Most people however won´t experience this error.
I´ve created a little Fix which is actually very easy to apply as a flashable zip. It was intended to be used with my Samsung Galaxy S3 ROM, it may also work with every other Samsung based ROM
Here is the link: Camera Fix for Samsung based ROMs
Simply install this file through your custom recovery
Just in case this patch should not work for everyone, leave me a comment and I´ll see what I can do :angel:
Click to expand...
Click to collapse
about time someone done this! thanks! i thought i corrupted the drivers, but thats for the fix!
Dude, brilliant, this works on KitKat roms also, I have spread the word and linked your thread to the benefit of all.
Thank you
Sent from my GT-I9300
does this really work? can someone add it to aosp code then? @XpLoDWilD @CarbonDev
ayoubij said:
does this really work? can someone add it to aosp code then? @XpLoDWilD @CarbonDev
Click to expand...
Click to collapse
Well it works perfectly for me, but @Moster2 says the md5 checksum is identical to the files already in place, but it works. I'm both happy but mildly confused! If you get the issue it's obviously with trying! You only need to flash the rom to remove it, so it's of no concern to try
Sent from my GT-I9300
metalgearhathaway said:
Well it works perfectly for me, but @Moster2 says the md5 checksum is identical to the files already in place, but it works. I'm both happy but mildly confused! If you get the issue it's obviously with trying! You only need to flash the rom to remove it, so it's of no concern to try
Sent from my GT-I9300
Click to expand...
Click to collapse
I'm wrong, this method went wayward for me in the end :banghead:
Sent from my GT-I9300
metalgearhathaway said:
I'm wrong, this method went wayward for me in the end :banghead:
Sent from my GT-I9300
Click to expand...
Click to collapse
Damn!
Sent from my Linaro SM'd CM11 Galaxy S3, with Archi's kernel. A proud Googy Beta tester.
Well done. Works perfectly.
I tried just about everything I could find regarding fixing the camera in my S3, including manually replacing the Camera2.apk and this is the first fix I tried that actually works. Thanks for putting the time and effort in to solve this annoying problem.
Can someone please upload his original 4.4.2 GPE YouTube.apk from /system/app
I can't apply the OTA.zip because somehow my YouTube.apk doesn't match the check (has unexpected contents)
apply_patch_check("/system/app/YouTube.apk", "99324614b30af24647885034d689e7c3a5008edf"
Searching for YouTube.apk:
MD5
a5d72785c39ea9ee66d529616baa9786
SHA1
99324614b30af24647885034d689e7c3a5008edf
I've downloaded 4.4.2 RUU that can be found here in the forums, but that YouTube.apk also doesn't match, so maybe there was another small patch afterwards or so?:crying:
Orginator said:
Can someone please upload his original 4.4.2 GPE YouTube.apk from /system/app
I can't apply the OTA.zip because somehow my YouTube.apk doesn't match the check (has unexpected contents)
apply_patch_check("/system/app/YouTube.apk", "99324614b30af24647885034d689e7c3a5008edf"
Searching for YouTube.apk:
MD5
a5d72785c39ea9ee66d529616baa9786
SHA1
99324614b30af24647885034d689e7c3a5008edf
I've downloaded 4.4.2 RUU that can be found here in the forums, but that YouTube.apk also doesn't match, so maybe there was another small patch afterwards or so?:crying:
Click to expand...
Click to collapse
YouTube stopping a update ? Never herd that one since no one should still have old version from last year installed . I don't think that's your issue but y can't u just go to apps/YouTube uninstall updates ? That will give u version that came on phone . good luck
Edit : did u have xposed YouTube mod installed ?
drawde40599 said:
YouTube stopping a update ? Never herd that one since no one should still have old version from last year installed . I don't think that's your issue but y can't u just go to apps/YouTube uninstall updates ? That will give u version that came on phone . good luck
Click to expand...
Click to collapse
Wrong, you have always a stock eg. system version in /system/app and then the latest version (if you updated) in the normal apps directory... I need the system one, it gets only modified (patched) on OTA-Updates.
Orginator said:
Wrong, you have always a stock eg. system version in /system/app and then the latest version (if you updated) in the normal apps directory... I need the system one, it gets only modified (patched) on OTA-Updates.
Click to expand...
Click to collapse
O really ? Thanks , I've Been doing this for awhile I no what u need . don't get y u ****ed with system file in the first place now .
I would send it to u but your WRONG pissed me off . good luck buddy .
drawde40599 said:
O really ? Thanks , I've Been doing this for awhile I no what u need . don't get y u ****ed with system file in the first place now .
I would send it to u but your WRONG pissed me off . good luck buddy .
Click to expand...
Click to collapse
Sorry, if you're so sensible and it gets you angry that someone gently corrected your statement, then fine. But then please at least don't post useless comments, saying that you would help out but won't. Thanks!
EDIT:
ohh and I don't even remember messing with the system files, so really no clue what happened there!