Database Develop

Qualcomm Camera Driver Install

So, i'm the guy who has been constantly trying to figure out why my camera all of a sudden died when I did my first ROM flash some time back. I have tried just about everything and it has led me to this point.
If you're wondering what everything is here you go.
1. Tried 3 or 4 different ROMS
2. Reverted back to unrooted RC29
3. Tried different camera software
4. Formatted and repartitioned my SD Card
5. UID repair under Amon's recovery.
Okay, back to my point.
When doing a logcat during an attempt at booting my camera (which always results in an FC) I noticed that the system was attempting to access a directory that wasn't there *dev/msm_camera/control0* after investigating I've found that the directory contains device files that work in conjunction or are part of the hardware driver itself.
Searching further, i found this post on the Android Wiki as to whether or not the Cupcake OS would work on the G1 (before it was released): "Need confirmation: Currently there are a number of closed source drivers that are not included. Someone with access to the source to these drivers will have to compile them with the 2.6.27 kernel that cupcake includes. Chances are that until there is an official OTA release for the G1 that is based on the changes in cupcake it will be very difficult to get it running on the G1/ADP1. These drivers include: The Qualcomm camera driver, frontend HW accel codec, h264, libhgl."
So, what I'm thinking is that i somehow have corrupted my drivers, and, the only way I am going to get them back, is if someone knows how to install them manually, or, if there is way to get back to RC30 or 33 without waiting for the OTA from T-Mobile. I went back to RC29, but, the check for system update option didn't appear in my settings window and after 5hrs I still didn't have the update. Any help with the camera driver install or with getting RC30 or 33. Please Help

thaquestion said:
When doing a logcat during an attempt at booting my camera (which always results in an FC) I noticed that the system was attempting to access a directory that wasn't there *dev/msm_camera/control0* after investigating I've found that the directory contains device files that work in conjunction or are part of the hardware driver itself.
Click to expand...
Click to collapse
I think You have bigger problems then that. Every rom includes drivers, even your RC29. Furthermore, you can rip them out of any rom and copy them into corresponding directory. If your camera doesn't work in multiple roms and after flashing DREAIMG.nbh - then it doesn't work, i.e hardware issue.
Good luck.

If all of the sufficient Camera drivers are present, then why isn't the directory specified recreated upon flashing ? Permissions issue maybe ? I'm just trying to figure it out. Also, when going from a custom ROM to RC29, I get different behavior, the camera doesn't force close, it just hangs on a backlit black screen.

You are missing the point. It was a COINCIDENCE that your camera stopped when you tried a custom rom. The camera circuit itself is FRIED WITHOUT CHANCE OF RECOVERY.
Virtually *ALL* of the DREAM/32B ROMs include the camera drivers appropriate to that device.
If the device files aren't being created, it has NOTHING to do with permissions since those device files are being created by the driver itself, which runs within the KERNEL == full control.
The differing behavior of the camera app with respect to lack of available camera is a result of differences between the two different versions of the camera APP itself and is nothing to get excited about.
The device files are created by the camera driver (kernel) when the camera hardware is initialized. The reason the device files aren't appearing is either because the kernel is unable to detect the presence of the hardware, or the driver is unable to initialize it. This is caused by a HARDWARE FAILURE.
FURTHER, the /dev path is NOT a disk filesystem. It is NOT created by adding files into your root filesystem. It is a VIRTUAL REPRESENTATION OF THE AVAILABLE HARDWARE THAT IS PRESENTED BY THE KERNEL.

Thank you very much, that is explanation I've been looking for all along, time to pack this phone back up and get a new one.

I have the exact described issues here, I have gone through the same tests except I found that my camera does work if I load the JacHeroski2.7.4r2.zip ROM.
So the camera actually functions. Any ideas what else this could be.
I did run a logcat of the Camera Start on the Hero ROM and I do not see any calls to /dev/msm_camera. which still does not exist.

[Q] Unable to reset Touchpad, even with webosdoctor

I am just about to give up any software solution and contact HP to see if they can fix this as a hardware problem.
But before I do that, i thought it might be worthwhile to post my problem here first.
My touchpad has been running fine, and operating without any problems until recently when I installed new apps or downloaded new files on the touchpad.
While the touchpad was up and running, everything was fine, the apps appeared in the menu, and the files copied could be accessed without any problems.
In terms of functionality there was nothing to suggest any problems with the TP.
However, whenever I reboot the TP (soft or hard reboot), all newly installed apps or files disappear and the TP reverts back to a previous state. Nothing that I do to the TP remains after a reboot.
So I downloaded the latest webosdoctor 3.0.5 to reset the TP but after getting to about the dreaded 12% mark, the webosdoctor fails, spewing out a lot of message about parted failure and something about the flash.
Following all the tips on using novacom to boot the uImage and accessing the TP from novaterm does not seem to work as any fix initiated is lost on the following reboot.
Even while logged in to the TP via novaterm, and using lvm.static to remove the logical and physical volume to see if I can get webosdoctor to recreate the partitions did not work.
The command lvm.static vgremove reported to successfully remove the logical drive, but on subsequent scan using lvm.static vgscan shows that the logical drive is still persistent.
Removing physical volume using lvm.static pvremove did not work.
In frustration I deleted /dev/mmcblk0p14 (and all the mmcblk0???). Consequently the lvm.static scans showed no logical drive available.... but on subsequent reboot they are all back.
Webosdoctor again failed with same problem when rebooted.
It seems like the TP is falling back to some default memory (partition) state and nothing that I do remains persistent. I can't see anyway I can force the partition tables to reset as any changes are lost on reboot.
So unless someone can suggest something different, I am resigned to having to call HP and send my TP in for repairs.
Does anyone else have similar experience?
P.S. this started after I updated to webOS 3.0.5 but I can't say this was the exact cause.

I have the same problem with my touchpad. Are there any solutions?

it looks like the only way to get it fixed is to contact HP and send your TP back for repairs.
I will be contacting them next week when I have time to organise for it to be repaired.

Have you tried to run the WebOS 3.0.0 Doctor? It will resize all of the partitions and leave you with a fresh copy of WebOS. It can be found here: "http://www.webos-internals.org/wiki/Webos_Doctor_Versions".
Here is what I did:
1.Completely shut down
2.Boot into recovery menu by holding Volume-Up button and then pressing the power button.
3.Run WebOS 3.0.0 doctor
If it halts for any reason, let me know what percentage it stopped on, and perhaps I can help you out.

As I have tried to outline in the OP, I have tried webosdoctoring from version 3.0.0 to 3.0.5
It doesn't have any effect as any changes to the partition is lost once the TP reboots.
I know webosdoctor 3.0.0 is the standard answer for all partition related problems, but I think in my case it is not a partition problem but more of the flash controller, that is hardware related. It might have gotten itself into a funny state where it is constantly going into fall back mode after every reboot.

I'm sure you probably read this , but the" Factory condition restoration" thread might be useful.

colin_404 said:
I'm sure you probably read this , but the" Factory condition restoration" thread might be useful.
Click to expand...
Click to collapse
This did not work for me. There is no way to remove /store

I'm having the same problem.
Device:
HP Touchpad 32 GB
WebOS: 3.0.4
Android: CM9 A2
Problem:
Every time the device is restarted, all data "magically" restores to how it was. Example: if I format the internal memory and I restart the device, all data remains as if I didn't format it.
Description:
My Touchpad has somehow gotten into a state of data lock, where I can't format it, nor recreate the filesystem in anyway.
What works:
- It loops while booting to Android
- It boots to Clockwork Recovery
- It boots to WebOS Recovery
- It boots to WebOS
- Everything works inside WebOS
- I can connect through Novaterm
What I've tried so far with no success:
- Recreating the file system
- Formating the internal storage
- Running a checkdisk
- Partitioning the storage
- Reinstalling Android
- Running WebOS Doctor 3.0.0, 3.0.4, 3.0.5

narci2500 said:
I'm having the same problem.
Problem:
Every time the device is restarted, all data "magically" restores to how it was. Example: if I format the internal memory and I restart the device, all data remains as if I didn't format it.
Description:
My Touchpad has somehow gotten into a state of data lock, where I can't format it, nor recreate the filesystem in anyway.
Click to expand...
Click to collapse
Nothing worked for me. Tried every trick suggested, even mixed things a bit. In the end I had to send it back to HP for it to be fixed.
All good now, it came back all fixed.

I'm having the same issue. Did they accept the return even with Android on it?

djteiwaz said:
I'm having the same issue. Did they accept the return even with Android on it?
Click to expand...
Click to collapse
yeah they accepted it with no questions asked.
But make sure you do the trouble shooting with the online chat first, it will save you time on speaking with them on the phone.

cychoi75 said:
yeah they accepted it with no questions asked.
But make sure you do the trouble shooting with the online chat first, it will save you time on speaking with them on the phone.
Click to expand...
Click to collapse
good to know, thanks

So an update:
I sent it in and they just called saying that it has a 3rd party OS installed and that my warranty is void. If I wanted them to repair it, it would cost $239 or I could have it shipped back unrepaired. So now I have a sort of bricked touchpad. Any suggestions?

djteiwaz said:
So an update:
I sent it in and they just called saying that it has a 3rd party OS installed and that my warranty is void. If I wanted them to repair it, it would cost $239 or I could have it shipped back unrepaired. So now I have a sort of bricked touchpad. Any suggestions?
Click to expand...
Click to collapse
Seems like it's stuck in some read-only mode. I have some ideas but you don't have the unit back, right?

rr5678 said:
Seems like it's stuck in some read-only mode. I have some ideas but you don't have the unit back, right?
Click to expand...
Click to collapse
Not yet. Should have it back by this weekend.

I also have this problem and have tried restoring my touchpad with numerous fixes on this site but they all fail and the touchpad just reboots to its previous state.
any help would be appreciated

Received it back. Would love some recommendations for possible fixes.

djteiwaz said:
Received it back. Would love some recommendations for possible fixes.
Click to expand...
Click to collapse
Okay. I'll gather some information now.

djteiwaz said:
Received it back. Would love some recommendations for possible fixes.
Click to expand...
Click to collapse
Bear with me. Just doing research. It's kinda hard since I don't have a device affected by this in hand.

rr5678 said:
Bear with me. Just doing research. It's kinda hard since I don't have a device affected by this in hand.
Click to expand...
Click to collapse
Not a problem. I appreciate you spending time on this for me.

Can't recognize in usb-mode

I have been running 4.0 for a long time, so i thought it was about time to get a newer version. so i ran the acmeuninstaller and was about to upload a new rom when i encountered a strange problem. i'm asked if i want to initialize the disk when i select mass storage mode. I have tried from webOS and from CWM, have also tried two usb cables, both my macbook pro and my windows 7 laptop. the original usb cable doesn't seem to be working anymore so i haven't got to try with that.
I didn't have any problems using recovery to transfer using nova com or preware. just the mass storage part that seem to be out of order.
any help is appreciated.

I'm starting to suspect something seriously wrong with the tablet.
i had ran a acmeuninstaller, but still booted into android. so i downloaded a rom and a file manager, and then a problem i've been having started to occur - processes dying etc. usually fixed by a reboot. which was one of the reasons i wanted to try something else.
so i took a reboot, and well - everything i had downloaded was gone. so i did the opposite thing, started deleting everything i've downloaded.
next reboot - everything was back in place.
More of this and i'll just use webOS which seem to work well. beside the usb connection that don't work.

I have never used any uninstaller to flash a new ROM. All I do is do a factory reset, clear cache, clear Dalvik cache then install new Rom and Gapps. I did this when I went from 10.1 to 10.2 to finally 11.0. Also, I have found that having the most current recovery installed will help also. For example...CWM version 6.0.4.7 is needed to install CM 11.0 because datamedia support is required to properly support emulated sdcard storage in 4.4. I also use CacheMate to regularly clear my caches.

This is a known occurrence with the touchpad.
DO NOT, if prompted, format the disc when connected in USB mode.
If you google your problem, there is a solution out there.
If you don't find it, let me knownand I'll try and find the link for you.
Your touchpad is not fubar !!
Peace

Nook HD+ cannot change persistent state from recovery / rootkit?

Hi,
I have a Nook HD+ which i run with CM13 (cm_ovation-ota-MOB30D.160422) and I've run now into a bizarre problem:
Last week, suddenly the nook started over night to get into an infinite reboot cycle where it goes throught nook start up screen, then cyanogemod universal boot loader screen followed by the pulsing cyanogemod logo. Sometimes it gets to the login screen, sometimes it reboots before but never did i manage to log in.
Trying to restore now older nandroid backups and/or flashing different ROMs and they all fail as they cannot properly update /system (restore fails as it fills up the filesystem even though i haven't resized /system and it definitely was not full at the time of backup; flashing ROM fails as it complains that after update /system did contain unexpected content.
Starting to tinkering with adb shell, i notice that any changes, e.g., adding or removing files, i do on the internal storage (be it /data or /system) seems to be reflected by ls in the same mount cycle but as soon as i umount and remount the device the state is restored to the old state! Similarly, any mkfs.* run without error on the various /dev/block/mmcblk0p* but nothing really changed if i remount the same device after that (i.e., content is not wiped and filesystem type is still what it was before). [the same happens if i try the various wipes/factory reset options in the recovery. No error but no effect].
Note this all happened regardless of recovery (CWM 6.0.4.6 / TWRP 2.8.7.5; the former via external sdcard, the latter internal to the nook). Also strangely, as i boot "normally" (and end up in the boot cycle) i can't run adb logcat as the device is listed as 'unauthorized'. Also for some operations with CWM it warns me at the end that ''root access possibly lost' and asks me whether i want to fix /system/xbin/su) [but either option i choose doesn't change the noticeable behaviour]. Lastly, the whole boot cycles and actions in recovery are very sluggish.
This almost sounds like there is a rootkit on the nook which masquerades the changes but ignores them to stay in control. However, googling i didn't immediately found any hits referring to such a rather sophisticated rootkit.
Did anybody ever see such a behaviour and/or have an idea what's happening? Any thoughts to reset the whole device?
-michael-

PS: Strike-out above part about unauthorized device for logcat: i was trying to do logcat from a device which apparently i've never used before for the nook; doing it on another one which i've previously used allowed for logcat to work but the log itself didn't really give any insights and the adb logcat died a few seconds before the nook rebooted, so i don't have any of these criticial parts of the log ...

Certain models of the HD+ have been known to develop a read only internal memory. It acts like it is being written to but it does not actually happen. When that happens it is not repairable.
Sent from my SM-T707V using XDA Premium HD app

leapinlar said:
Certain models of the HD+ have been known to develop a read only internal memory. It acts like it is being written to but it does not actually happen. When that happens it is not repairable.
Click to expand...
Click to collapse
Hi Leapinlar,
thanks for your feedback: Rather surprising (& unfortunate) behaviour but still better than a rootkit
I guess so my option are only to install/boot CM from an sdcard (or getting a new device)?
-michael-

BTW: to run CM from sdcard i guess i need a no-emmc ROM (even though my emmc still works read-only and i can boot recovery from it)? If so, the latest one i found is https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/ which is rather dated. Is there anywhere a new one or some pointers one what all has to be changed to make a emmc ROM turn into a no-emmc ROM so i could try changing a ROM myself? Thanks!

recover /data partition, data loss after shutdown - maybe due to f2fs

Hi
I just discovered that my phone's /data (and /cache) partitions (f2fs filesystem) seem to have gotten corrupted.
my suspicion is that it didn't shutdown safely (powerloss during shutdown, maybe the battery was already emptier than the os thought it was, starting the shutdown then increased the power usage)
The battery is less than a year old. (official replacement, not done by myself)
I didn't connect my 3T to power last night (forgot about it)
I connected it to power the next morning and went to eat breakfast, when I came back it was booted up. It still recognized my fingerprint and last app sessions still have screenshots from my apps. The home screen background is still the same. My apps are all still there as far as I can see.
But: all the data is gone. My apps start like I installed them fresh from the store and opening my file manager none of my files are there any more. only 15gb of 128gb used up. (it was closer to 100gb)
Upon noticing this I immediatly went to twrp (3.2.3-10) to use it's repair feature for the partition. -> Error 139
I did the same for my /cache partition and got the same error so I suspect it got corrupted as well.
I'm running Havoc OS 2.4, Android 9.0 (didn't get around to update it and it ran smooth without any major issues for months)
Is there any way for me to backup what is still there (maybe even sector copy (dd))?
Is it possible to repair such an image in Linux or recover some of the files from it?
Is it possible that a newer twrp version actually still can repair my /data partition?
Or is all hope lost? Did my smartphone automatically reformat /data? or has it maybe not touched the partition but cannot use it correctly?
What happens in this case on Android? Would've been nicer (for me) to run into a bootloop instead so I can figure out what's going on, before any hope is lost.
I'm pretty sure encryption was turned off due to magisk/root.
Once I set up the smartphone again I'll switch ext4. I currently blame f2fs but I'm not sure.
I have backups of the important data that was on my smartphone, but if there is any way, it would be nice to recover the rest (images, videos in original resolution etc.)
:fingers-crossed:
If anyone could contribute ways for me to look into this or show me how to proceed, I would be very greatful.
and maybe it's not even f2fs's fault after all.
Regards
EDIT:
in twrp's file manager the file system looks the same btw. (/storage or /sdcard look like factory default)
EDIT2:
I managed to create an .img file from my userdata partition by using the adb command from twrp's adb shell
adb shell 'dd if=/dev/block/sda15 2>/dev/null' > sda15.img
Click to expand...
Click to collapse
I hope that will help
I'll try https://www.forensicfocus.com/Forums/viewtopic/t=17133/ once it finished transfering the img file