Database Users

[Script] AutoInstall new camera [Hastarin 8.5.1 + new cam libs]

Mods: If you think this should go in general section feel free to move it, thanks.
I built a script that will install the new camera (nexus based), it will replace all necessary files to get the camera working as well as hastarins 8.5.1 modules (to get wifi working and all) and finally liblights and libhtc_ril_wrapper (might be overkill, but it works)
Instructions: Unzip CamScript folder to SD Card (anywhere is fine) and then as su (adb shell or terminal emulator, anything you use to run bash scripts is ok) run cam_install.sh
Note: It will replace zImage in either /sdcard/HD2ONE or /sdcard/Android; it will not work if you have a kernel in a folder different to those so edit your startup.txt file if necessary.
Credit goes to hastarin for the kernel and camera files
-OCM
V1.5: Everything should work now, i've tested on stock HD2ONE_Latest. Backup versions of all modified files are saved in /data/cam_backups.

Good job
Sent from my HTC HD2

Thanks for the script,
Noticed that in the Replace_Libs function you copy liboemcamera.so to libcamera.so.old overwriting the other libcamera.so.old!!
I'm guessing you don't want to do that??
I've just tried this on my JDMS 1.5 that already had Hastarin8.5.1 old camera and my Andorid wouldn't reboot.
Anyone got any tips on troubleshooting non-restarting phones??
I've got the HTC splashscreen and I can adb into the phone but from there on I'm a bit lost.

bobjbain said:
Thanks for the script,
Noticed that in the Replace_Libs function you copy liboemcamera.so to libcamera.so.old overwriting the other libcamera.so.old!!
I'm guessing you don't want to do that??
I've just tried this on my JDMS 1.5 that already had Hastarin8.5.1 old camera and my Andorid wouldn't reboot.
Anyone got any tips on troubleshooting non-restarting phones??
I've got the HTC splashscreen and I can adb into the phone but from there on I'm a bit lost.
Click to expand...
Click to collapse
try chmod -R 777 /system/lib/*

bobjbain said:
Thanks for the script,
Noticed that in the Replace_Libs function you copy liboemcamera.so to libcamera.so.old overwriting the other libcamera.so.old!!
I'm guessing you don't want to do that??
I've just tried this on my JDMS 1.5 that already had Hastarin8.5.1 old camera and my Andorid wouldn't reboot.
Anyone got any tips on troubleshooting non-restarting phones??
I've got the HTC splashscreen and I can adb into the phone but from there on I'm a bit lost.
Click to expand...
Click to collapse
Same problem here...i've tried your script on the HD2ONE 0.3.3 Rc2 version. I've followed all the instructions and now im stuck on the green HTC logo.....Can you please tell me how to Manually apply this script because i think it doesnt work properly....thanks

I don't think this fix is going to work with build that is based on cm6 .1 rc2 because it gets boot loops on the htc screen. I will still give this fix a try and report back....
Edit
Tried it and it did not work for me, black screen on the camera...

atoore said:
Those new builds that is based on cm6.1 rc2 wont work with any new kernels with the new drivers. I will try this fix and report back...
Click to expand...
Click to collapse
What do u mean??
ocm7 reported he succefully applied new camera drivers to the HD2ONE_latest build that is based on the cm6.1 rc2...

Any solutions????

Working on it, shouldnt take more than a few minutes

ocm7 said:
Working on it, shouldnt take more than a few minutes
Click to expand...
Click to collapse
Really thanks, anyway tomorrow (now its late night here) i'm going to reinstall the latest HD2ONE build and then applying your script again (still if you told me how to manually add all the stuff it would be better for me)

Uploaded the fixed version, worked on stock HD2ONE_Latest, so it *should* work on other builds but i cant guarantee this. If you're stuck on boot screen you can try running this new script and see if it works, if it doesnt replace system.ext2 with stock from your build then run the script. Sorry about the initial errors...

So, I used your 1.5 script and this time managed to reboot back into Android.
Everything seemed fine except that my camera still had a green tinge when used with the flash.
THEN I realised that I still had the root directory in the Android folder. So assumed/guessed that the libs were being oerwritten by those in the root folder.
So I renamed root to root_old, re-ran your script, rebooted.
Hung like a mule!!
Restoed original JDMS 1.5 system.ext2, rebooted fine.
Except now my accounts don't sync, my camera takes a picture then hangs
I will get it all back thanks to Titanium Backup
--
Looking at your script it's what I've always been doing to install new Kernels. The green tinge was there when I first tried Hasatrin 8.5.1
The only thing that you do different is include a build.prop file (which is wildly different from mine BTW).
So, my question, is it something in the build.prop that is stopping the grren tinge? If so, what??
TIA

as far as i know, this new lib file in CM or MIUI build make camcorder freeze..does it? or does it not?

I have a weird problem: when i'm in terminal emulator, then su (#), but when i try to type run cam_install.sh it says....run: not found......i think it doesnt recognize the run command..is it possibile??
Is there a way to avoid using this script and SIMPLY manually put all the needed files in the correct directories??
Thanks in advance!!!
P.S. I'm doing that in a HD2ONE stock unmodified latest build...

clockcycle4mobile said:
I have a weird problem: when i'm in terminal emulator, then su (#), but when i try to type run cam_install.sh it says....run: not found......i think it doesnt recognize the run command..is it possibile??
Is there a way to avoid using this script and SIMPLY manually put all the needed files in the correct directories??
Thanks in advance!!!
P.S. I'm doing that in a HD2ONE stock unmodified latest build...
Click to expand...
Click to collapse
Try
Code:
./cam_install.sh
there is no 'run' command in linux. Programs are executable and are run by just typing their name.
Of course the file has to be chmod'd to be executable too, but the ./ gets around that mostly.

It didn't work with HD2ONE-0.3.3.RC2
Just stuched in HTC welcome page

bobjbain said:
Try
Code:
./cam_install.sh
there is no 'run' command in linux. Programs are executable and are run by just typing their name.
Of course the file has to be chmod'd to be executable too, but the ./ gets around that mostly.
Click to expand...
Click to collapse
Thanks, i've done everything....android rebooted correctly but black screen on camera application...
ocm7 tell me how you made the camera application work properly....i tried and didn't work...

Mine says on every file "file not found" or something like that.

lesjaw said:
as far as i know, this new lib file in CM or MIUI build make camcorder freeze..does it? or does it not?
Click to expand...
Click to collapse
It does if you record on the highest setting (720p)
hhhawasly said:
It didn't work with HD2ONE-0.3.3.RC2
Just stuched in HTC welcome page
Click to expand...
Click to collapse
Worked perfectly for me on a stock system, are you sure all the files got copied right (no errors printed)?
clockcycle4mobile said:
Thanks, i've done everything....android rebooted correctly but black screen on camera application...
ocm7 tell me how you made the camera application work properly....i tried and didn't work...
Click to expand...
Click to collapse
Since everyone is having such a hard time getting it to work here are the manual instructions:
Replace your current kernel with hastarins 8.5.1
Replace Camera.apk in /system/app
Replace libcamera.so, liboemcamera.so, libOmxCore.so, libOmxVdec.so, libOmxVidEnc.so in /system/lib
Optional but recommended: replace lights.qsd8k.so in /system/lib/hw and rename or remove /system/lib/hw/lights.htcleo.so also replace libhtc_ril_wrapper.so in /system/lib
replace bcm4329.ko, tun.ko and cifs.ko in /system/lib/modules
place 99complete in /system/etc/init.d and chmod it to 755 (important!)
replace build.prop to fix green tint (I got it from the green tint fix thread and just replaced some lines to match CM6)
reboot
Also, i said these libs were nexus based so if your build is desire based it simply wont work

ocm7 said:
It does if you record on the highest setting (720p)
Worked perfectly for me on a stock system, are you sure all the files got copied right (no errors printed)?
Since everyone is having such a hard time getting it to work here are the manual instructions:
Replace your current kernel with hastarins 8.5.1
Replace Camera.apk in /system/app
Replace libcamera.so, liboemcamera.so, libOmxCore.so, libOmxVdec.so, libOmxVidEnc.so in /system/lib
Optional but recommended: replace lights.qsd8k.so in /system/lib/hw and rename or remove /system/lib/hw/lights.htcleo.so also replace libhtc_ril_wrapper.so in /system/lib
replace bcm4329.ko, tun.ko and cifs.ko in /system/lib/modules
place 99complete in /system/etc/init.d and chmod it to 755 (important!)
replace build.prop to fix green tint (I got it from the green tint fix thread and just replaced some lines to match CM6)
reboot
Also, i said these libs were nexus based so if your build is desire based it simply wont work
Click to expand...
Click to collapse
Well I've done every single step you wrote but still camera app is totally black after reboot.....this is very weird since i've used the same build you used (nexus based) but my result is so different from yours....

Help Needed... Think I Bricked my Nexus S

Greetings,
Okay, so I endeavoured to root my phone last night and was successful. I ran into trouble when the clockwork recovery and superuser permissions kept getting removed each time I rebooted the phone. This morning, I tried to restore the superuser permissions by following the steps I found here on xda but after running the terminal script I rebooted my phone and when my phone wouldn't boot beyond the Google screen.
Now, I'm at the Google splash screen with no way to move forward. I'm a mac user and I don't really get the adb thing. Got adb to work with mac from a youtube video, but still not sure what commands to run.
I can't access clockwork recovery from the bootloader.
What I've done so far:
- wiped cache
- wiped/factory data reset
- retraced my steps by using terminal to setup superuser permission from this post (http://forum.xda-developers.com/showthread.php?t=927838)
What I think:
- maybe in all of my clicks I removed the ROM, so the phone doesn't have a ROM to work with.
This maybe a really infantile conclusion, but I know there's a solution (had a rooted G1 that I flashed all the time and thought I bricked once but was able to get it back to stock).
Eagerly waiting for a reply... no cell phone if this can't be fixed.
Tamaratee
__________________
Phone: Nexus
Rooted with problems

This post might help:
http://forum.xda-developers.com/showthread.php?p=9866675
It has the adb commands on how to replace the existing boot loader with cwm and all.
Hope it helps.
EDIT: If all else fails, you can try flashing a nandroid backup (2.3.3). This post would guide you:
http://forum.xda-developers.com/showthread.php?t=979851

Greetings Cygnum,
Thanks for the suggestion. I have a question: will these commands work on a Mac?

Thank you to AllGamer for suggesting that I post this question here and for the following suggestion:
AllGamer said:
please post the same question in QA or General, then we can all help you
PM is not the best place to ask for help.
The first thing to do is to download the full set of Android SDK 2.3+ for MAC
then we'll continue from there.
Click to expand...
Click to collapse
How do I proceed AllGamer? I downloaded the mac SDK from here (http://developer.android.com/sdk/index.html).

Follow steps 1-7 from here to get back Clockwork Recovery.
http://forum.xda-developers.com/showthread.php?t=878446
If your bootloader is already unlocked, you can skip those steps.
Do steps 8-9 to copy this file over to your USB drive.
http://devsforandroid.com/ip.board/index.php?/files/file/94-stock-deodexed-233-voodoo-rooted/
This rom is Master's Stock 2.3.3 ROM that is already rooted which should get you up and running.
Unmount, go back. Wipe system data, wipe cache. Go to advanced, Wipe Dalvik-cache.
Go back, choose to install zip from SD card. Locate Master's stock ROM. Flash that.
In the end, you'll have a stock deodexed rom that is rooted. Keep in mind that you will lose all your data, but that at least puts you back on track.

Also wanted to mention if you didn't already know, mac scripts are run with a "./" in front of them. So to use the adb command you would do something like, "./adb reboot bootloader" after you have changed your directory to the folder that contains the sdk files.

peeturr said:
Also wanted to mention if you didn't already know, mac scripts are run with a "./" in front of them. So to use the adb command you would do something like, "./adb reboot bootloader" after you have changed your directory to the folder that contains the sdk files.
Click to expand...
Click to collapse
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.

krohnjw said:
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.
Click to expand...
Click to collapse
Yeah my bad. Just whatever had worked for me. Pretty new to mac myself.
Sent from my Nexus S using XDA App

krohnjw said:
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.
Click to expand...
Click to collapse
Doesn't ~/ do the same as well?
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.

kenvan19 said:
Doesn't ~/ do the same as well?
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.
Click to expand...
Click to collapse
No. ~/ specifies your home directory

Thanks Everyone
Thanks for all the suggestions and help I received. I PM'd KenVan and he provided me with the script and my Nexus S is up and running.

I just had this problem on the weekend I could not get past the lockscreen so I flashed cyanogen nightly and bam booted fine
Sent from my Nexus S using XDA App

Problem Solved Over the Weekend
Thanks for the help everyone. I posted this in a couple places, so I forgot to update this thread.
I fixed the problem with detailed steps from KenVan. Thanks again though to all of you for your suggestions.

[DEV] System images

I want to collect the system images in case you must get back to stock.
Just do the following and upload your image.
Code:
su
dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img
perfect would be an nearly untouched build
IMAGES:
WIFI - US: http://forum.xda-developers.com/showpost.php?p=13427976&postcount=7
WIFI - EU: Had to remove my image because of Dropbox

I'm currently uploading one to my dropbox should be done in about an hour. I'll poist the url, or pm you should you prefer.

You may post it in public, of course - thx a lot

seraphimserapis you forgot to ask somthing from the people that upload...
plase add in the first post to add:
3g/wifi model
us/eu versions

you're right.
it's the wifi eu model
Sent from my Nexus S using Tapatalk

wee really need one of each version... I really what to compare file on all versions

mine is the wifi us
here is the link
http://db.tt/dSafLm6

common ppl we need 3g models... go for 3g models....

Stock?
How would one of these get me back to stock? I've got a corrupt file - so I am bootlooping after root. SU causes a seg fault, so I can't get root permission to remount & replace the busted files... anyone figure out getting to recovery yet?

BitVenom said:
How would one of these get me back to stock? I've got a corrupt file - so I am bootlooping after root. SU causes a seg fault, so I can't get root permission to remount & replace the busted files... anyone figure out getting to recovery yet?
Click to expand...
Click to collapse
thinking its dead... thats what i'm afraid of... got lots of ideas but cant try them without a safety net...

BitVenom said:
How would one of these get me back to stock? I've got a corrupt file - so I am bootlooping after root. SU causes a seg fault, so I can't get root permission to remount & replace the busted files... anyone figure out getting to recovery yet?
Click to expand...
Click to collapse
Use this file http://db.tt/3hqvgP1 and push it to /data/local/tmp
Then run it via ./data/local/tmp/gb
You should be root afterwards and be able to fix permissions etc
Sent from my LG-P990 using Tapatalk

borked system/bin us version 16gb
hi I borked my acer. root went smoothly, but then I made mistake of trying to enable adhoc supplicant. I downloaded es explorer and used remount to enable rewrite to system/bin. Now everything disappeared. It will still load, but wifi shows error.
How do I return to stock?

ataib said:
hi I borked my acer. root went smoothly, but then I made mistake of trying to enable adhoc supplicant. I downloaded es explorer and used remount to enable rewrite to system/bin. Now everything disappeared. It will still load, but wifi shows error.
How do I return to stock?
Click to expand...
Click to collapse
its very simple you didnt set the wpa_supplicant to the right permissions... as you were told... and please dont post in the dev section :|

nycbjr said:
mine is the wifi us
here is the link
<Link removed>
Click to expand...
Click to collapse
Thank you so much! I got stuck on the Android ! boot screen and couldn't get the OS to boot after stupidly screwing up permissions after I rooted. I downloaded your zip, renamed it to update.zip and loaded it on a microsd card. Then I put the card in, booted the tablet while holding volume down and recovery loaded the system image and I'm back in business. It did come with a few apps loaded into system I'm not familiar with including a few that weren't in English. Will a factory reset remove those, does anyone know?
Edit: This is also missing gapps including the market... You sure this is a US image?

no thats a chinese update u need to follow a link thats been post above urs a bit ago and follow the directions on how to add market to the nook color.
Sent with my Acer A500 Ti-X RC1

Thanks I found the info. And I bricked it again. Looks like it's getting exchanged at best buy tonight. I'm not going to try rooting again anytime soon.

tonight come in to the irc channel and talk to me. we will get u rooted but not bricked.
Sent with my Acer A500 Ti-X RC1

Back to stock
EDIT - removed

Hi and sorry for my poor english...
Could you explain how to put back a system.img backup in the tablet in case of a problem ?
Thanks a lot !

I don't know if that's possible while running the device. This will be good for the recovery tho
Sent from my A500 using Tapatalk

Bootsound problem - build.prop+/etc/local.init.rc+stagefright fine. ??

I had a custom boot animation and boot sound working perfectly, and then I flashed CM7.03. Now no master what I do, I cannot get the bootsound working again.
Initially I used a shell script based on a zip written by stevo for the evo (i think), and everything was fine. The shell script was a one-off that enabled bootsound.
I traced back through everything, and other than added echoed lines in both build.prop and local.init.rc, which are duplicates, but shouldn't cause any problem (and also, is it possible to edit a text file using the root explorer? I ask because I tried to clean up both of the above files this way, and my changes did not take...permissions were correct too), everything was fine--as it was before.
Thinking maybe something happened to Stagefright, I downloaded a streaming music app, but everything seemed fine, so that is not the issue.
Attached is a copy of the bash script that I used. I ran it from the terminal after cd'ing to /sdcard/root, and making sure the system wad mounted R/W.
I have been seeing-- and also getting questions from others-- whose bootsound also suddenly stopped working after the recent update to CM.
Can anyone figure this out for me?
Again, while doing all my diagnostics above, I double checked both permissions and my path variable and they were as they needed to be in both cases.
Thanks!
Syntropic
Sent from my HTC Glacier using XDA Premium App

[Q] Android is upgrading every startup

Everytime I turned on my phone or if it rebooted, I always get:
Android is upgrading
-----------------------------
Starting Apps.
I am on stock ROM, TWRP recovery, Faux kernel. I think this happens after I wiped dalvik/cache in the recovery. Any idea how to stop it? It's nothing very major though as it only takes a few seconds.

are you using any sound/volume mods? or any other flashable mods? i think awesomebeats dies this, at least others have complained about it wiping the dalvik after every reboot.

cdon2109 said:
Everytime I turned on my phone or if it rebooted, I always get:
Android is upgrading
-----------------------------
Starting Apps.
I am on stock ROM, TWRP recovery, Faux kernel. I think this happens after I wiped dalvik/cache in the recovery. Any idea how to stop it? It's nothing very major though as it only takes a few seconds.
Click to expand...
Click to collapse
That's normal if you've wiped the Dalvik cache, and no you can't stop it.
Edit: so wait, this is happening even when you reboot normally after not wiping any caches or flashing a kernel?

CMNein said:
That's normal if you've wiped the Dalvik cache, and no you can't stop it.
Edit: so wait, this is happening even when you reboot normally after not wiping any caches or flashing a kernel?
Click to expand...
Click to collapse
yes.. and it updates apps after delvic wipe.. but in my case whenever i restart I see the "Android is upgrading" box for about 3-5 sec.. no update app progress bar.. and when I wipe delvic this upgrading apps takes like a min or so with my 150+ apps.. but this "Android is upgrading" dialogue box appears only for 3-5 sec..
I am using PA 3.99 with franco kernel.. once booted every thing inside is running smoothly and no fc's...

Same here. No odex files in app folder. No wipe, no cache clearing. Plain reboot. And Android is upgrading message on every boot. (Starting apps)
No optimizing apps message though.
Sent from my Nexus 4

Wouldn't it be related to "zipalign apk on each boot" parameter ? or an other init script put in place by a dirty flash (no /system or /data format) or a kernel... ?

Seems likely. Could you explain in detail kindly?
Sent from my Nexus 4

anandbibek said:
Seems likely. Could you explain in detail kindly?
Sent from my Nexus 4
Click to expand...
Click to collapse
Have a look in the files located in this folder for example (maybe there's another location for init scripts) :
- /system/etc/init.d/
- /system/addon.d/
and open each one, to see what are the tasks contained

benbugohit said:
Have a look in the files located in this folder for example (maybe there's another location for init scripts) :
- /system/etc/init.d/
- /system/addon.d/
and open each one, to see what are the tasks contained
Click to expand...
Click to collapse
Removed the scripts present in init.d folder and then booted with empty folder, but message still present.
Checked the addon.d folder, but those scripts are only for backing up gapps etc.
Not sure where else to try. Please advise.
Thanks.

anandbibek said:
Removed the scripts present in init.d folder and then booted with empty folder, but message still present.
Checked the addon.d folder, but those scripts are only for backing up gapps etc.
Not sure where else to try. Please advise.
Thanks.
Click to expand...
Click to collapse
Did you try to re-flash your (stock) ROM (and the kernel after 2 reboots) with wiping only /cache and dalvik-cache ? with latest 2.6.2.0 TWRP ?

happens to me too
Sent from my Nexus 4

I've seen people get this with stuff like V6 Supercharger by Zepplinrox and similar scripts.

Edit : @Dungeon47: thanks for this information that users can't provide...
HeyyMyNameIs said:
happens to me too
Sent from my Nexus 4
Click to expand...
Click to collapse
A pity that so much details are missing : what did you do before it happened ?
What's your set up ? rom, kernel ? after having update your rom ? kernel ? apps ? which versions ?
Did you try to revert to a clean install after having backup up your apps+datas ?

benbugohit said:
Edit : @Dungeon47: thanks for this information that users can't provide...
A pity that so much details are missing : what did you do before it happened ?
What's your set up ? rom, kernel ? after having update your rom ? kernel ? apps ? which versions ?
Did you try to revert to a clean install after having backup up your apps+datas ?
Click to expand...
Click to collapse
im sorry, just wanted the OP to know that he is not the only one with this "problem" by the way im rooted stock rom and kernel, some apps start up when i boot like nova launcher, lucky patcher sidebar and udn. But i am not looking for a fix for this as this does not take that long and i just said that to let the OP know that he is not alone with this "problem"
Sent from my Nexus 4

Ok guys,
Here's the solution. Don't flame me for talking about unholy stuffs. I'm posting this only because it is the cause of the problem.
If you are using LP or such tools to create .odex files of some app in /app folder. It won't cause any boot msg.
But after you dirty flash a ROM, that .odex files somehow gets backdated and causes the UPGRADING msg.
Fix is, delete the odex files, and re create them if needed. Once after every dirty flash.
Sent from my Nexus 4

I have found fix for this error, it is mainly due to odex files which are created by lucky patcher so deleting these files using lucky patcher itself will surely remove this error with 50 percent success rate. Here's the fix; open lucky patcher, there in lower left section you can see Toolbox, click that Toolbox then select 4th last option i.e Remove all odex files.Thats it android will reboot on itself and vola no android is upgrading. .
Check out attachment for help.
:good:Hits Thanks If I helped u:good: