Related
I have no market on my phone and have been trying to install some apk's through amon ra console in recovery. Everything I try, which is practically everything i've read from searching, comes back with errors.
Either file/directory not found or can't open "install"
I am also having problems installing the drivers to get adb working from dangerspl. When I try to update drivers it says "This file does not contain information about your device"
Any help is much appreciated. I've been up all night trying to figure it out and feel like I'm going in circles.
Have you try installing from a file manager instead? (astro, estrongs, linda, etc..)
No I don't currently have a file browser installed, and have no market to look up/install one. I have another android phone with astro, could I pull it off of that phone and install on this with recovery console?
Why not just install it via adb or push it to /system/app
I can't connect via adb becuase I couldn't update the windows driver for dangerspl. I downloaded the drivers for dangerspl but when I tried to update, it said it didn't have information about my device. Something like that. So I can mount the sdcard in windows and put any files needed and boot into recovery and use that right? I tried making a zip with the qpks in it and use flash from zip, kinda like installing gapps, but that didnt work either. Any ideas?
Zip files will need the update scripts and signed for it to be able to be "flashed" from recovery.
Just use droidexplorer or android commander.
Code:
mount -a
or type less and read more
You can use busybox if you have the latest CM ROM installed
just type this ~~~> (busybox install /sdcard/yourapp.apk /sd-ext/app)
make sure the app is in the root of your sdcard
brios86 said:
You can use busybox if you have the latest CM ROM installed
just type this ~~~> (busybox install /sdcard/yourapp.apk /sd-ext/app)
make sure the app is in the root of your sdcard
Click to expand...
Click to collapse
Code:
su
cp /sdcard/yourapp.apk /sd-ext/app
is less typing
and
Code:
su
cp /sdcard/yourapp.apk /data/app
is a 'safer' bet as they didn't mention which rom
what about this one? update.zip creator
http://forum.xda-developers.com/showthread.php?t=717437
sleepyfu said:
Zip files will need the update scripts and signed for it to be able to be "flashed" from recovery.
Click to expand...
Click to collapse
which is not a big problem to create.
There is a TUT for it
sleepyfu said:
Have you try installing from a file manager instead? (astro, estrongs, linda, etc..)
Click to expand...
Click to collapse
you need a filemanager with root-rights. Depending on the ROM you use it might be available.
Try the app "IRSSI - connect bot". It gives you a console on the device.
login "local" and type "su".
Than you have superuser rights .... anything on commands you find in linux/android TUTs
Lol! 6 month old post?
Friends,
Having issues with flashing a custom rom to just rooted HTC One X 2.20 (ATT). First Android phone for me, got it a week ago, and first run at any and all of these issues (just switched from iPhone, but still doing all of this using a Macbook Air). Here's the spread:
Unlock went fine, no issues.
Installed TWRP, DID NOT INSTALL SUPERUSER.
Managed to choke and wipe OS (along with caches, sdcard). Fastboot and adb work. I have full access to TWRP, however I cannot mount /sd to computer (Mac simply notes, when mounting, that the device is unreadable).
I managed to push both the rom I was hoping to install (aokp_evita_jb_build-4.zip), and gapps to sdcard with ADB, however neither file would show in TWRP's file manager (I placed them in the root dir of the phone). I attempted to run the ROM via fastboot to no avail. I did push the boot.img as directed.
As I did not install SuperUser when I was supposed to, I attempted to install the superuser.apk with ADB after the fact, with the resulting error stopping me in my tracks: /sbin/sh: pm: not found. The only resolution to this issue I could find did not seem to apply to my situation.
Are the lack of permissions granted by SuperUser the reason the rom and gapp .zip files do not appear in TWRP file manager? Can/should I continue to attempt installing the superuser.apk file? After digging through all of these godawful help requests (mine included), can/should I attempt to lock the bootloader and flash RUU? What am I missing that is painfully obvious to those with real experience in this mess?
emp1re07 said:
Friends,
Having issues with flashing a custom rom to just rooted HTC One X 2.20 (ATT). First Android phone for me, got it a week ago, and first run at any and all of these issues (just switched from iPhone, but still doing all of this using a Macbook Air). Here's the spread:
Unlock went fine, no issues.
Installed TWRP, DID NOT INSTALL SUPERUSER.
Managed to choke and wipe OS (along with caches, sdcard). Fastboot and adb work. I have full access to TWRP, however I cannot mount /sd to computer (Mac simply notes, when mounting, that the device is unreadable).
I managed to push both the rom I was hoping to install (aokp_evita_jb_build-4.zip), and gapps to sdcard with ADB, however neither file would show in TWRP's file manager (I placed them in the root dir of the phone). I attempted to run the ROM via fastboot to no avail. I did push the boot.img as directed.
As I did not install SuperUser when I was supposed to, I attempted to install the superuser.apk with ADB after the fact, with the resulting error stopping me in my tracks: /sbin/sh: pm: not found. The only resolution to this issue I could find did not seem to apply to my situation.
Are the lack of permissions granted by SuperUser the reason the rom and gapp .zip files do not appear in TWRP file manager? Can/should I continue to attempt installing the superuser.apk file? After digging through all of these godawful help requests (mine included), can/should I attempt to lock the bootloader and flash RUU? What am I missing that is painfully obvious to those with real experience in this mess?
Click to expand...
Click to collapse
Check the settings in TWRP. You should have everything mounted as writeable. Root files may not show up otherwise.
iElvis said:
Check the settings in TWRP. You should have everything mounted as writeable. Root files may not show up otherwise.
Click to expand...
Click to collapse
TWRP Settings does not appear to contain an options relating to this: Zip file sig. verification/Force MD5 check/Use rm -rf/ Skip MD5 generation/Enable MD5 verification/Ignore image size errors/Simulate actions for theme testing
Tried to use ADB sideload to load the ROM, didn't work.
I've continued searching through threads to find a situation similar to mine, no luck.
EDIT: Rebooted a couple of time, retried pushing gapps-jb-20120726-signed.zip and the aokp rom mentioned above. They now appear under /sdcard
Tried to install both .zip files, and was met with a FAIL for the following reasons: E: Unable to mount '/sdcard' and E: Unable to mount storege
Hi everybody,
I upgraded to Lollipop using the original image. Everything was fine. No problem of any kind. Then I decided to flash the TWRP recovery. At the first run (just after installation) it was there and worked fine (I even made a backup). However, after a reboot when I went to the recovery I found that it was the stock recovery and TWRP was gone. The back up is also gone from my internal storage. The same thing happened when I flashed the latest version of CWM. After a reboot the flashed recovery is gone.
Please help. Thanks in advance.
joojooman said:
Hi everybody,
I upgraded to Lollipop using the original image. Everything was fine. No problem of any kind. Then I decided to flash the TWRP recovery. At the first run (just after installation) it was there and worked fine (I even made a backup). However, after a reboot when I went to the recovery I found that it was the stock recovery and TWRP was gone. The back up is also gone from my internal storage. The same thing happened when I flashed the latest version of CWM. After a reboot the flashed recovery is gone.
Please help. Thanks in advance.
Click to expand...
Click to collapse
are you using.. fastboot flash recovery recoveryname.img or fastboot boot recovery recoveryname.img?
simms22 said:
are you using.. fastboot flash recovery recoveryname.img or fastboot boot recovery recoveryname.img?
Click to expand...
Click to collapse
I have used "fastboot flash recovery recovery.img"
joojooman said:
I have used "fastboot flash recovery recovery.img"
Click to expand...
Click to collapse
well, if you used boot instead of flash, itll only boot the recovery for a one time use. flash should make it stick. if not sticking, flash a recovery 2 or 3 times, itll stick eventually.
simms22 said:
well, if you used boot instead of flash, itll only boot the recovery for a one time use. flash should make it stick. if not sticking, flash a recovery 2 or 3 times, itll stick eventually.
Click to expand...
Click to collapse
Thank you, I will try that and then report...
Do you have the latest version of the recovery and the root files?
I used CF Root as Chainfire is the man. I ran it first, then I added the recovery.
It stuck for me.
Remove the scripts etc that install recovery such as inatall-recovery.sh and recovery.boot.p in system and system/bin
Just double check your install-recovery.sh isn't one used to call su because you don't want to remove that if it is.
simms22 said:
well, if you used boot instead of flash, itll only boot the recovery for a one time use. flash should make it stick. if not sticking, flash a recovery 2 or 3 times, itll stick eventually.
Click to expand...
Click to collapse
I flashed ( flash .img ) the recovery 2 or 3 times (even more) but it won't stick. If I do not reboot to system it remains there but as soon as I reboot to system it is gone.
joojooman said:
I flashed ( flash .img ) the recovery 2 or 3 times (even more) but it won't stick. If I do not reboot to system it remains there but as soon as I reboot to system it is gone.
Click to expand...
Click to collapse
you want to find and rename or delete install-recovery.sh in /system/. thats whats replacing your recovery with stock.
simms22 said:
you want to find and rename or delete install-recovery.sh in /system/. thats whats replacing your recovery with stock.
Click to expand...
Click to collapse
I actually tried that, but had the following problem:
Code:
sudo adb shell mv /system/bin/install-recovery.sh{,.bak}
mv: rename /system/bin/install-recovery.sh to /system/bin/install-recovery.sh.bak: Read-only file system
Do you have an idea how I can come around this issue?
edit: I have figured that out, check post #15
tweaked said:
Do you have the latest version of the recovery and the root files?
I used CF Root as Chainfire is the man. I ran it first, then I added the recovery.
It stuck for me.
Click to expand...
Click to collapse
I do not want to root. Is it possible? I just want to have recovery. The problem is remained.
joojooman said:
I do not want to root. Is it possible? I just want to have recovery. The problem is remained.
Click to expand...
Click to collapse
From my understanding you need root to be able to edit files in /system. And in there is the script that "misbehaves" for us.
But I've not quite understood how to come by the read only file system problem
naro said:
From my understanding you need root to be able to edit files in /system. And in there is the script that "misbehaves" for us.
But I've not quite understood how to come by the read only file system problem
Click to expand...
Click to collapse
Does it mean that lollipop behaves differently from KitKat? I could have recovery without root there. It stuck at the first flash. But now it is removed every time I boot to the system.
I've ran into the same problem except for me I'm not even getting stock recovery. I don't even have one lol
Okay guys so I figured out how to get it to work (and the recovery to stick!)
First of all, get root. CF Auto root is your friend here.
Now to the problem: The recovery seems to be "reflashed" at every boot. (with an "empty" recovery).
To fix it, boot your phone up and connect it to a pc that has adb installed.
remember to not use sudo under windows, just keep that part out
Code:
sudo adb shell
Now you are on a shell in your android. Since /system is mounted readonly, we first have to remount it:
Code:
[email protected]:/ $ su
[email protected]:/ # mount -o rw,remount /system
now change the install script (I just added a .bak to the name so we do not have to delete it) and remount the filesystem and read only again:
Code:
[email protected]:/ # mv /system/bin/install-recovery.sh{,.bak}
[email protected]:/ # mount -o ro,remount /system
Finally flash the recovery as you are used to, it will now stick:
Code:
sudo adb reboot-bootloader
sudo fastboot flash recovery openrecovery-twrp-2.8.1.0-hammerhead.img
sudo fastboot reboot
From here on, you are back in android and your recovery should have sticked
Maybe you should go to system and find a file like this
recover --from--boot
then delete it
Alright, well the above solution definitely helped, but now when i try to enter super su, it tells me the binaries arent updated and the root needs to be done manually.....but didnt i just do this?
naro said:
From my understanding you need root to be able to edit files in /system. And in there is the script that "misbehaves" for us.
But I've not quite understood how to come by the read only file system problem
Click to expand...
Click to collapse
joojooman said:
Does it mean that lollipop behaves differently from KitKat? I could have recovery without root there. It stuck at the first flash. But now it is removed every time I boot to the system.
Click to expand...
Click to collapse
You can have a recovery without root. Also root is only "in" android. If your recovery has a file manager, it can edit /system files without root because android isn't running lg, ergo no protection. Its just like taking a hard drive out of a computer and adding it as a 2nd in another computer. You don't need that computers password to get the data.
So flash the ROM and see if you can delete them using the recovery file manager or adb whilst booted into recovery
---------- Post added at 08:45 AM ---------- Previous post was at 08:43 AM ----------
naro said:
Okay guys so I figured out how to get it to work (and the recovery to stick!)
First of all, get root. CF Auto root is your friend here.
Now to the problem: The recovery seems to be "reflashed" at every boot. (with an "empty" recovery).
To fix it, boot your phone up and connect it to a pc that has adb installed.
remember to not use sudo under windows, just keep that part out
Code:
sudo adb shell
Now you are on a shell in your android. Since /system is mounted readonly, we first have to remount it:
Code:
[email protected]:/ $ su
[email protected]:/ # mount -o rw,remount /system
now change the install script (I just added a .bak to the name so we do not have to delete it) and remount the filesystem and read only again:
Code:
[email protected]:/ # mv /system/bin/install-recovery.sh{,.bak}
[email protected]:/ # mount -o ro,remount /system
Finally flash the recovery as you are used to, it will now stick:
Code:
sudo adb reboot-bootloader
sudo fastboot flash recovery openrecovery-twrp-2.8.1.0-hammerhead.img
sudo fastboot reboot
From here on, you are back in android and your recovery should have sticked
Click to expand...
Click to collapse
This was all unnecessary.
boot recovery
Flash ROM
mount system
adb shell
rm /system/blah
That was all.
Re
I had the same problem yesterday except that i was intending to install both root and TWRP recovery. I flashed TWRP and ran it then installed supersu, the root did not work and TWRP was gone after rebooting the system.
I used the "cf auto root" utility made by chainfire. It worked (even though the root has few bugs)
I noticed that cf-auto-root flashed some boot img before installing root and twrp. I think you may want to give it a look.
rootSU said:
This was all unnecessary.
boot recovery
Flash ROM
mount system
adb shell
rm /system/blah
That was all.
Click to expand...
Click to collapse
This is what I did:
Boot to recovery-->
Flashing TWRP img-->
Then immediately going to TWRP file manager-->
Changing install-recovery.sh to install-recovery.sh.old -->
Then immediately made a backup --> reboot to system, turning the cellphone on and off several times
TWRP is there BUT:
The only point is that I cannot see the backup folder in my internal storage. It is clear that it has taken some
space (almost 2GB) but I cannot see the TWRP backup folder.
I have a Samsung galaxy tab 2.One day as I decided to wipe everything,i noticed a message in the recovery mode saying unable to mount efs.I cant open my tablet or anything.After looking on the internet,people were telling me to flash a custom recovery like CWM.In order to do that I need to root my tablet.To root my tablet I need to enable USB debugging,which I can't because I can't access it.Can you help me please?
Shedopen123 said:
I have a Samsung galaxy tab 2.One day as I decided to wipe everything,i noticed a message in the recovery mode saying unable to mount efs.I cant open my tablet or anything.After looking on the internet,people were telling me to flash a custom recovery like CWM.In order to do that I need to root my tablet.To root my tablet I need to enable USB debugging,which I can't because I can't access it.Can you help me please?
Click to expand...
Click to collapse
Boot to download mode and flash CWM or TWRP for your model number via Odin. Then you boot into CWM or TWRP and flash SuperSU.zip to root your device. I suggest TWRP instead of CWM.
Then, if you have TWRP you can use the built in file manager in TWRP to pull a copy of your build.prop file from /system, then copy it to PC then open build.prop in a text editor then find these lines in it:
persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb
Change these lines in your build.prop to match the example above. You may not have all of these lines, change the ones you have and/or type the lines you don't have in for yourself then save the edited build.prop then adb push that copy back to /system to overwrite the existing unedited build.prop. Reboot the device and USB debugging should be enabled.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Boot to download mode and flash CWM or TWRP for your model number via Odin. Then you boot into CWM or TWRP and flash SuperSU.zip to root your device. I suggest TWRP instead of CWM.
Then, if you have TWRP you can use the built in file manager in TWRP to pull a copy of your build.prop file from /system, then copy it to PC then open build.prop in a text editor then find these lines in it:
persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb
Change these lines in your build.prop to match the example above. You may not have all of these lines, change the ones you have and/or type the lines you don't have in for yourself then save the edited build.prop then adb push that copy back to /system to overwrite the existing unedited build.prop. Reboot the device and USB debugging should be enabled.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I'm having trouble flashing Supersu.zip.Everytime I flash,i type SU into the Terminal and it always says SU not found.Do I have to use adb from now on in order to replace efs?I also can't find the build.prop file that you are referring to in your comment.Thank you
Shedopen123 said:
I'm having trouble flashing Supersu.zip.Everytime I flash,i type SU into the Terminal and it always says SU not found.Do I have to use adb from now on in order to replace efs?I also can't find the build.prop file that you are referring to in your comment.Thank you
Click to expand...
Click to collapse
You don't flash SuperSU.zip with adb/fastboot.
Move the SuperSU.zip file to your device's internal storage or put it on an external sdcard, then boot into TWRP and choose the "install" option, then browse to where you stored SuperSU.zip and flash it.
In my first reply to you, I didn't say anything about flashing SuperSU.zip in a terminal, I told you to boot into TWRP and flash SuperSU.zip. Pay attention to what is told to you, word for word.
You could have easily done some searching to understand those instructions. Learn to search for answers.
You need to be rooted first, then you can find and edit build.prop.
Build.prop is very easy to find, again, learn how to search for answers.
Build.prop is located in /system/build.prop. It's in system partition, not in your internal storage.
Try using adb pull to get a copy of build.prop then edit the copy, save the copy and adb push it back to its location in /system/build.prop.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Here's where I'm at. I've got the system to give me the Mount /System option in recovery, now i just need assistance getting the build.prop pulled to my PC. What's the procedure for pulling the build.prop from the Android to PC via ADB while the system is mounted in recovery? Why am I getting one of these two ADB errors?
Error 1: Connect failed: closed.
error 2: Failed to get feature set: no devices or emulators
OR, am I approaching it wrong?
Thanks in advance,
K0mraid3
you dont need to be in recovery to do it via adb....
adb pull /system/build.prop
that will pull it to where evr you run the adb command
which would be
C;\adb more than likely
or you can choose a destination with
adb pull /system/build.prop c:\buildprop
if you create a folder called "buildprop" in the root directory of c:\
at least thats how i remember doing it many years ago, ive been away for a while at her majesties pleasure, so i cant try it currently as im not rooted
gav83collins said:
you dont need to be in recovery to do it via adb....
adb pull /system/build.prop
that will pull it to where evr you run the adb command
which would be
C;\adb more than likely
or you can choose a destination with
adb pull /system/build.prop c:\buildprop
if you create a folder called "buildprop" in the root directory of c:\
at least thats how i remember doing it many years ago, ive been away for a while at her majesties pleasure, so i cant try it currently as im not rooted
Click to expand...
Click to collapse
Thanks, so far, its still for some reason denying me permission when OS is booted. So i just cant quite figure out where im supposed to execute these commands, is my issue. I can boot directly to BL from recovery menu, but i can also mount system. i think maybe i need sto send command for r/w.. will try that now.
Another question, when i mount /system in recovery, does that carry over on boot?
no you can re mount system via adb though
Code:
$ adb shell
$ su
# mount -o rw,remount /system
gav83collins said:
no you can re mount system via adb though
Code:
$ adb shell
$ su
# mount -o rw,remount /system
Click to expand...
Click to collapse
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
dr.ketan said:
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
Click to expand...
Click to collapse
im yet to root my device so i cant test but what about
Code:
adb root
adb disable-verity
adb reboot
Then
Code:
adb root
adb remount
gav83collins said:
im yet to root my device so i cant test but what about
Code:
adb root
adb disable-verity
adb reboot
Then
Code:
adb root
adb remount
Click to expand...
Click to collapse
Do you got what I meant?
leave it.
dr.ketan said:
WTF
Do you got what I meant?
leave it.
Click to expand...
Click to collapse
look, there is no need for condescension and bad language, a simple "no" would have sufficed
Lol not meant to hurt you! but on which planet WTF is bad language
Here search WTF on xda
dr.ketan said:
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
Click to expand...
Click to collapse
So my device is strange. It doesn't have root, but it indeed shows options in recovery to apply updates from ADB, SD Card aswell as boot directly to BL and to Mount /System, but when I'm booted, the OS is denying me permission to "Su" . I have verified that USB debugging is activated. So I'm trying to see if there's a way to pull the build.prop from Recovery since the Mount /System option is available, but my computer refuses to recognize the device in while in recovery, but easily finds it in Download, BL mode. No FRP lock. No accounts on device. But also no option to unlock bootloader. This device in particular is/was a development sample so I have no clue what the current state of the bootloader etc is in terms of being unlocked prior to me working on it.
It'd also worth noting that this device was loaded with Android 11 when I received it. I'm not kidding. So idk what's going on with this FrankenGalaxy
K0mraid3 said:
It'd also worth noting that this device was loaded with Android 11 when I received it. I'm not kidding. So idk what's going on with this FrankenGalaxy
Click to expand...
Click to collapse
K0mraid3 said:
So my device is strange. It doesn't have root, but it indeed shows options in recovery to apply updates from ADB, SD Card aswell as boot directly to BL and to Mount /System, but when I'm booted, the OS is denying me permission to "Su" . I have verified that USB debugging is activated. So I'm trying to see if there's a way to pull the build.prop from Recovery since the Mount /System option is available, but my computer refuses to recognize the device in while in recovery, but easily finds it in Download, BL mode. No FRP lock. No accounts on device. But also no option to unlock bootloader. This device in particular is/was a development sample so I have no clue what the current state of the bootloader etc is in terms of being unlocked prior to me working on it.
Click to expand...
Click to collapse
These options are normal in stock recovery and can be used only for flashing official zip (OTA), To have root access on your recovery, you needs custom one (TWRP) which is in development stage on S22
Without twrp, You needs to root device (must have oem unlock option in development option) to access system files while you are booted to android.
Android 11 on S22? Can you show me screenshot of settings - about phone - software info?
dr.ketan said:
These options are normal in stock recovery and can be used only for flashing official zip (OTA), To have root access on your recovery, you needs custom one (TWRP) which is in development stage on S22
Without twrp, You needs to root device (must have oem unlock option in development option) to access system files while you are booted to android.
Android 11 on S22? Can you show me screenshot of settings - about phone - software info?
Click to expand...
Click to collapse
Thanks for the clear answer, that's kind of what I'm working on is trying to gain root access, but like you said, I need oem unlocking, which isn't on this device. So I'm trying to find a backdoor/vulnerability that will take me even one step closer to atleast finding a way to set ro.secure. prop. Something VERY interesting I did find, is that if you put the device to Debug medium or high via device keystring activity, and play with the key combos, you can get booted into a mode called RDX, if you plug it into your dev system with the right drivers, it's treats the phone as if it were a Disk and shows a bunch of VZW upgrade software ment for PCs. I've installed it but haven't got it working quite yett.
No idea what you have shown in screenshot, I'd asked something else.
dr.ketan said:
No idea what you have shown in screenshot, I'd asked something else.
Click to expand...
Click to collapse
Maybe Heindall will give me better results. I just refuse to believe the manufacturers have outsmarted us all on this.