Model number: GM_DSTL1
Firmware version: 1.5
Baseband version: 20/05/09,st32,x2a.m1
Kernel version: 2.6.28-svn1368
Build number: CUPCAKE.eng.long.20090720.210535.r1368
Trying to figure out how this could be rooted because I can't seem to use traditional methods like downgrading and 1-click rooting.
If I understand correctly this is possible for me due to CVE-2009-2692
In an effort to try and cover my butt I have backed up all that "adb shell" permission would let me.
Zinx's "Recovery partition flasher for Android" has not been helpful.
Getting my device to use FastBoot seems to be my first step.
Constructive comments?
still no luck
Ruled out the telnetd hack, bummer:
I run telnetd in terminal and it gives me no errors but a port scan doesn't return anything besides port 110(pop3), 25(smtp), and 21(ftp) - none of which have proved useful thus far. Must have been patched with cupcake... or something I'm missing.
Also ran cat /proc/cpuinfo for fun
--------------------------------
Processor : XScale-V3 based processor rev 2 (v5l)
BogoMIPS : 103.58
Features : swp half thumb fastmult edsp iwmmxt
CPU implementer : 0x69
CPU architecture: 5TE
CPU variant : 0x0
CPU part : 0x689
CPU revision : 2
Hardware : yuhua X2_V4 on Marvell (Littleton)
Revision : 0004
Serial : 0000000000000000
-----------------------------------------------------
103.58 is weak sauce... but apparently that is the minimum for the Marvell PXA310 RISC Microprocessor
I wonder if anyone else on this board is bumpin the DSTL1? I may be the lone fish out here
Following this guide to get Fastboot aka Engineering Bootloader
I skipped flashing the radio because I figured it had to do with the OTA stuff which doesn't affect my model...
So I downloaded spl-signed.zip and renamed it to update.zip, placed it on my sdcard in the folder "update" (these instructions are specific to my model). In recovery mode I tried to update it but it FAIL.
update.log from failed update
Starting recovery on Thu Oct 8 01:22:51 2009
framebuffer: fd 4 (240 x 400)
I:text_cols 24 text_rows 22
E:Can't open /cache/recovery/command
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.build.id=CUPCAKE
ro.build.display.id=CUPCAKE.eng.long.20090710.190105.r1322
ro.build.version.incremental=eng.long.20090710.190105.r1322
ro.build.version.sdk=3
ro.build.version.release=1.5
ro.build.date=Fri Jul 10 19:15:42 CST 2009
ro.build.date.utc=1247224542
ro.build.type=user
ro.build.user=long
ro.build.host=long-desktop
ro.build.tags=ota-rel-keys,test-keys
ro.product.model=GM_DSTL1
ro.product.brand=generic
ro.product.name=gm_x2
ro.product.device=x2
ro.product.board=x2a_v4
ro.product.manufacturer=yh
ro.product.locale.language=en
ro.product.locale.region=US
ro.board.platform=
ro.build.product=x2
ro.build.description=gm_x2-user 1.5 CUPCAKE eng.long.20090710.190105.r1322 ota-rel-keys,test-keys
rild.libpath=/system/lib/libyh-ril.so
rild.libargs=-d /dev/ttyp1
persist.gsm.dual.mode.phone=1
persist.gsm.sim.active.phone=GSM1
sms.supports.national.lang=1
wifi.interface=eth0
ro.config.sm_notification_snd=notf_gm_02.ogg
ro.config.sm_notification_snd_2=notf_gm_02.ogg
ro.config.notification_sound=F1_New_SMS.ogg
ro.config.ringtone=GM_01.ogg
ro.config.ringtone_2=GM_01.ogg
ro.config.sync=yes
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=yuhua
ro.revision=4
init.svc.recovery=running
init.svc.adbd=running
init.svc.yuhua-board-init=stopped
ro.kernel.android.qemud=0
ro.radio.use-ppp=no
ro.com.google.locationfeatures=1
RecVer:Fri Jul 10 19:15:42 CST 2009
Recovery tools:
HOME: Sd-card update
CALL: Board test
BACK: Factory reset
POWER: Reboot system
I:Key 102 pressed, alt 0
Search /sdcard/update/*
I:Find file . in /sdcard/update/
I:Find file .. in /sdcard/update/
I:Find file update.log in /sdcard/update/
I:Find file update.zip in /sdcard/update/
Find update.zip, Home to update
I:Update package /sdcard/update/update.zip
Installing /sdcard/update/update.zip
Installation failed.
Another Fastboot attempt
http://android-dls.com/wiki/index.php?title=Engineering_Bootloader
Downloaded update.xxx, renamed it to update.zip, placed it on my sdcard in the folder "update" (these instructions are specific to my model). In recovery mode I tried to update it but it FAIL... again.
From the log files it seems this stock recovery system SUCKS...
Another FAIL
Revisiting http://forum.xda-developers.com/showthread.php?t=532719 from my earlier post (#3). Tried to do the Radio Update... Downloaded ota-radio-2_22_19_26I.zip and renamed it to update.zip... yada yada yada, you know the rest.
Visit "http://www.generalmobile.com/index.asp?action=Android_Phones/DSTL1_support", and you can find how the update system work(it is not a G1). Also take some time to see the install package and hack it.
1. Unzip the package.
unzip Android_20090826_r1502.zip
2. Copy some missed property app(http://www.sendspace.com/file/dii80c get from adp1.5) to /system/app/ after diff it with the ADP image.
3. zip the new package.
zip Android_20090826_r1502_hack.zip -ry system boot.img
4. update package and wait it bootup.
Very cool!
@wineleven
THANKS!
That was very cool! Finally some progress
So I was not too off from that path, I had already downloaded the update from General Mobile and had been inspecting the zip file they were trying to shove in my face as a quick fix to their buggy ROM. I was asking the support some very hard questions, which is probably why it has taken them more than their 48 hours to reply to me. (its been 5 days now)
General Mobile's update is Android_20090826_r1502.zip
containing the following particularly interesting (to me) files:
/system/build.prop
/system/system-update-post-script
/boot.img
/update-validate-script
Attempt 1
Here I tried to zip up their unmodified package with the suggested -ry arguments and hope that stock recovery takes it and runs with it.
FAIL
I reviewed wineleven's suggestions noticed he omitted the file update-validate-script
This was probably my problem
Attempt 2
Here I omitted update-validate-script
SUCCESS!
Attempt 3
Spirits high I go for the gusto:
I downloaded superuser.zip from this forum and embedded it in the location /system/app
Flash SUCCESS, functionality FAIL
I got too excited and put Superuser.apk and su both in the same directory... silly mistake
Attempt 4
This time I put Superuser.apk in /system/app and su in /system/bin
Flash SUCCESS, functionality FAIL
running su in terminal gave me "permission denied" with the following carriage return:
here1here2here3here4$
obviously I'm missing something here... but have made progress and feel more confident about this.
More attempts to come. Suggestions and advice is welcome!
Question to those knowledgeable
Why are certain files in the /system/bin included as "links" and not actual files? save space in zip?
Can boot.img be modified? Replaced with a better (more useful) one?
Any ideas on obtaining root?
Root idea and shortcommings
After reviewing http://android-dls.com/wiki/index.php?title=Magic_Root_Access
I may have bin (lol) too hasty with slapping su in /system/bin
But logic tells me it shouldn't matter... bin or xbin
And I feel like permissions are my real issue because my current su (residing in /system/bin)
command
ls -l /system/bin/su
returns
-rwxr-xr-x root shell 34612 2008-08-01 08:00 su
command
chmod 6755 /system/bin/su
returns
Unable to chmod su: Read-only file system
^--- in hindsight I see that as a DUH, because I can't remount the /system partition as read/write
More questions
I have always understood chmod to use three digits, why are there four digits now?
Also, what is 's' in terms of permission... is that to see? like hidden files?
Main task accomplished!
After reviewing Cyanogen's experimental ROM I can see where and how he sets permission for su
Trying to emulate his method for myself has been plenty of trial and error, but I have finally done it.
system-update-post-script was the key file that set permissions.
One MUST keep the carriage return at the end of the file - I have a neatfreak habit of cleaning them up.
Also, using the su and Superuser.apk in Cyanogen's latest build kept restarting my device, must be because his kernel is newer than mine.
RapidShare is hosting for 90 days Android_20090826_r1502_rooted.zip - NEW BUILD HERE
MD5: F1DE9A270CDDF01ADEE708B6660B7AFA
PM me if not avail.
NOTE:
I am not responsible for your new paper-weight mode...
This has worked fine on my device, but I guarantee nothing for yours...
My device is General Mobile's DSTL1 - details in post #1
What you get:
Root access via su and Superuser.apk - procured from XDA forums: http://forum.xda-developers.com/attachment.php?attachmentid=211569&d=1249225060
To use:
Your sdcard must contain "update" folder, this is where you will place the zip file after you have renamed it to "update.zip"
Happy ROOT
------------------------------------------
My next task will be to get Cyanogen's ROM to work on my device... seeing as how Cyanogen codes for the popular HTC models, I am left out - and I don't like being left out.
Side quests will be to play with the boot.img, flash the SPL, and maybe get a nice recovery
Particularly I would love to try out nandroid.
@wineleven THANK YOU for the nudge in the right direction!
Thank you:
Google for the open source Android OS - without the free SDK wouldn't have been possible for me
General Mobile for the nifty device
Remote Exploit for BackTrack3/4 - I did most of my work on this Live CD distro
XDA-Developers Forum for info and resources: superuser files and Cyanogen's ROM for info
congratulation to you.
Some notice:
As this devices is deeply modified based on Android open source and hardware different to G1. So you can not rebuild any system framework APK from open source unless you can get the DSTL1 source code. As i now, one thing we can do is to add some external APK file (API compatible to device, now SDK 1.5) to system. Like the Superuser.apk you do.
crzyruski said:
After reviewing Cyanogen's experimental ROM I can see where and how he sets permission for su
Trying to emulate his method for myself has been plenty of trial and error, but I have finally done it.
system-update-post-script was the key file that set permissions.
One MUST keep the carriage return at the end of the file - I have a neatfreak habit of cleaning them up.
Also, using the su and Superuser.apk in Cyanogen's latest build kept restarting my device, must be because his kernel is newer than mine.
RapidShare is hosting for 90 days Android_20090826_r1502_rooted.zip
MD5: C3C13F6DC75BF6F86E5C9E41D7FB4C59
PM me if not avail.
NOTE:
I am not responsible for your new paper-weight mode...
This has worked fine on my device, but I guarantee nothing for yours...
My device is General Mobile's DSTL1 - details in post #1
What you get:
Root access via su and Superuser.apk - procured from XDA forums: http://forum.xda-developers.com/attachment.php?attachmentid=211569&d=1249225060
To use:
Your sdcard must contain "update" folder, this is where you will place the zip file after you have renamed it to "update.zip"
Happy ROOT
------------------------------------------
My next task will be to get Cyanogen's ROM to work on my device... seeing as how Cyanogen codes for the popular HTC models, I am left out - and I don't like being left out.
Side quests will be to play with the boot.img, flash the SPL, and maybe get a nice recovery
Particularly I would love to try out nandroid.
Click to expand...
Click to collapse
Hi crzyruski
I'm a new android and DSTL1 user and this information is cool
it's easy to do for a newbie as I?
What do you mean easy? What would you like to do?
I took General Mobile's only update: http://www.generalmobile.com/index.asp?action=Android_Phones/DSTL1_support and gave it ROOT. If this is all you want to do, I have compiled the package already for you in my post above. If you want to do it manually then read the whole thread to see how I did it.
If you want to use my compiled package, it is easy.
Then again, I don't know if anyone else has tried it. It worked for me.
You are only the second individual to inquire about it, I am not sure if the other fellow had any luck - he hasn't replied to me.
Hope this helps.
Keep in touch!
I only have 3 days with Android, but I think that I want to get root access. The only thing I have to do is a second "update" with your package, isn't it?
I'm going to look for a backup system program first...
Can I have problems to update from General Mobile support web in a future? (i.e Android 2.0)
It does not need to be second. That is your choice. You can use it in any order. This is not a patch so order is no relevant.
My package is basically the original General Mobile update + 2 files.
These two files are su and Superuser.apk - nothing special (except that you will obtain root access on demand)
I currently only utilize root access to run Advanced Task Manager.
And in the future I want to overclock because I feel the DSTL1 is greatly underclocked though it should max out at ~600Mhz.
Good luck with a backup program as I have not found any free versions and NAndroid is ideal but not not yet possible as you have to flash the SPL and I am not aware how to do this for DSTL1 though I am sure it is possible.
Please let me know what you end up using to backup, if you do.
I would like to note that I am not all knowing and if something goes wrong I am sorry, but can't take responsibility.
There is no reason you should not be able to update from my package to another like: original 1.5 or new 1.6 or future 2.0 (whenever it comes out).
Hopefully when those come out I will be able to modify them similarly and make them available.
But you mentioned you will only have the device for 3 days, do you suppose 2.0 will be released within this time?
-crzyruski
crzyruski said:
Please let me know what you end up using to backup, if you do.
But you mentioned you will only have the device for 3 days, do you suppose 2.0 will be released within this time?
-crzyruski
Click to expand...
Click to collapse
I'm going to try with My Backup Pro
And about 2.0 this all I know...
http://www.boygeniusreport.com/2009/10/16/android-2-0-screenshot-walkthrough/
Good luck to you.
I think I may begin working on some more DSTL1 hacks.
Please keep me updated with your progress
I only have to do ALL this process with your zip, isn't it?
How to Install the Product Update:
Create a folder at the top-level of your memory card called 'update' , and copy file '*.zip' into your phone's memory card.
Make sure your phone is off, and press the Home key together with the Power & End key to enter the recovery mode, do the operations following the UI indication:
1- Press the Home key to search the zip file from your memory card, and press the Home key again to update the software.
2- Press the Call key to do board test.
3- Press the Back key to restore the factory settings.
4- Press the Power & End key to reboot your phone after update finishes.
Click to expand...
Click to collapse
Looks correct to me. Tell me how it works out.
crzyruski said:
Looks correct to me. Tell me how it works out.
Click to expand...
Click to collapse
I've done it! and all seems to be ok...
Thank you crzyruski.
I'll be waitng for your future DSTL1 hacks.
Good day,
I have a problem I follow all the steps at this site tutorial to install android without windows Mobile, but It happends that android cant boot properly it gets an error
"Unable to open persistent property directory /data/property error 2"
my question is there is a way to fix it and put android back or should I reinstall WM, and how reinstall it??
I used:
KAIS-480Type3.nbh
thanks for your atention and help
root.otavio said:
Good day,
I have a problem I follow all the steps at this site tutorial to install android without windows Mobile, but It happends that android cant boot properly it gets an error
"Unable to open persistent property directory /data/property error 2"
my question is there is a way to fix it and put android back or should I reinstall WM, and how reinstall it??
I used:
KAIS-480Type3.nbh
thanks for your atention and help
Click to expand...
Click to collapse
Hello It seems you're new so welcome! (I'm pretty new myself)
You need to post this question in the build thread you are using (ie: if you are using KaiserDroid, post in that thread, if in Poly's build use that thread).
Also, if you are using Poly's build if you read the instructions thoroughly there is an easy procedure to fix this.
I am not sure about KaiserDroid because I never had this problem with KaiserDroid so I never had to look.
solved
I solved the problem, if someone is passing the same as me and your phone still booting you just need to press camera button and then with the stilus the reset button. and you will be able to reflash it
This is not a problem.
You never pressed the middle key to actually install a Android ROM(the file you flashed was under 10MB). Your phone was successfully flashed with dzo's setup, all you had to do was throw an android build in your andboot folder on your SD card..reset the phone and press when promoted, in linux, to enter the android installer.
hey everybody i tried two whole days to install android os.
i read every comment here:
http://forum.xda-developers.com/showthread.php?t=918778
tried all 3 methods there and what other worte in also the korean rom
without sucsses, this device isnt support in my contry and i have no idea how install android.
the massages that i have got:
mount: mounting /dev/block/mmcblk0p5 on /sd card failed no such device or address
"cant mount internal flash!!!!!"
Until the installation process (folder o2beta) I'll get an message "can't find ext2.tar.gz on My Storage". After reboot and starting HARET.EXE from root directory it stops at the message:
Warning: unable to open an initial console.
Failed to execute /init. Attempting defaults...
Kernel panic - not syncing: No init found. Try passing init=option to kernel.
help pls!!
Your question should be in the thread you linked to. You got the Android zImage from there, so that's where your question should be.
Closed.
trying to boot custom kernel (tried android and LK)
want to boot into native debian (irregular-expression.com/?p=30 - cant find his xda post)
-have changed cmdline in menuconfig
-have changed 'type' of cmdline (override, append, static)
-have used fastboot in combo with above to try to change
-changed root=/dev/block/mmc***, root=/dev/mmc***
-tried to boot to system (mmcblk0p10) and sdcard (mmcblk0p12)
fastboot -c 'root=/dev/mmcblk0p12 rw rootfs=ext4 init=/sbin/init rootwait noinitrd' boot zImage
i either get a hang at the google logo
or
the fone vibrates and reboots to the boot partition
can't find anything, don't know what that would be called, or how to tell what i'm doing wrong
i know rootfs doesn't mount because i don't have so much as a dmesg log in /var/log - or any other logs for that matter
edit : noticed...clearly boots LK to cyan fine...so...unless someone wants to help, can prolly close this
aug 17 edit:
well...it still follows the same title so...?
got fb console output...but i don't know enough about android and can't find anything to make sense of the init
basically edited stock initrd and changed init.rc to 'chroot /newroot /sbin/init' into my mounted debian...
get an error "Unable to open persistent property directory /data/property errno: 2 - Failed to bind socket 'property_service': No such file or directory" ... "Kernel panic - not syncing: attempting to kill init" ..."reboot in 5 seconds"
is there a better/easier way to boot into debian? as far as I can tell kernel cmdline init= doesnt do anything. can't get output and i'm assuming no /dev gets messed with at all when i don't use a modified android init with ueventd and its setup
thanks for any help
read something that says questions like these belong in dev-forum...but not having 10 post i cannot do that...
so...bump
been looking up different devices and their chrooting tricks and w/e i can find...i really don't understand. my chromebook boots gentoo fine, swapped the kernel and some modules/firmware around - works...can't get anything except initrd to print anything & make /dev.
edit:
phew...ok...some BT5(backtrack) img/initrd i found will mount my internal sdcard for root...mkdir zzz gives me a directory on /data.
so i have /dev...but no fb or display
W00T
so i found
http://forum.xda-developers.com/showthread.php?t=1075054
got the bt5kern img and extracted its initramfs
had static udev and other boot progz
made sure to compile devtmpfs in kernel (drivers > generic drivers)
waited longer than i usually would
got to gdm
now i just need to get the touchscreen working...every time i touch it goes back to tty and then gdm
bl00dy said:
W00T
so i found
http://forum.xda-developers.com/showthread.php?t=1075054
got the bt5kern img and extracted its initramfs
had static udev and other boot progz
made sure to compile devtmpfs in kernel (drivers > generic drivers)
waited longer than i usually would
got to gdm
now i just need to get the touchscreen working...every time i touch it goes back to tty and then gdm
Click to expand...
Click to collapse
Look at the xorg log, you should be able to see it now. What xorg version is that?
a manta sent this.
beekay201 said:
Look at the xorg log, you should be able to see it now. What xorg version is that?
a manta sent this.
Click to expand...
Click to collapse
i don't remember what version. i just copied my chromebook rootfs to my fone, so i gotta add evtouch or something. haven't had nix on a touchscreen before now that i think about it.
good idea, i'll look at the log and see if it's some other reason it's respawning.
edit:
Code:
(EE)
(EE) Backtrace:
(EE)
(II) evdev: barometer: Close
(II) UnloadModule: "evdev"
(EE) BUG: triggered 'if (inSignalContext)'
(EE) BUG: /var/tmp/portage/x11-base/xorg-server-1.13.1/work/xorg-server-1.13.1/os/log.c:588 in LogVHdrMessageVerb()
(EE) Warning: attempting to log data in a signal unsafe manner while in signal context.
Please update to check inSignalContext and/or use LogMessageVerbSigSafe().
The offending header and log message formats are:
%s: %s: Close
(EE)
(EE) Backtrace:
(EE)
(WW) Warned 3 times about sigsafe logging. Will be quiet now.
(II) evdev: tuna-gpio-keypad: Close
(II) UnloadModule: "evdev"
(II) evdev: proximity: Close
(II) UnloadModule: "evdev"
(II) evdev: lightsensor-level: Close
(II) UnloadModule: "evdev"
Hello fellow N5X owners,
I've just registered at XDA Developers (also I did read here a long time ago) because I experience some strange problems with internal storage of my device.
I've first noticed when I wanted to use an app which on first startup unpacks a large OBB file: Initial setup fails all the time stateing internal storage may be low. I checked storage, there is enough space left. The curious thing is that it always failed at different percentages and after countless attempts it even finished successfully once.
Further investigating it, I tried to install the app on other Android devices (including another Nexus 5X, both phones are on build OPM2.171019.029), which worked flawlessly. Also I did a a "factory reset" by unrooting and re-flashing the latest stock ROM on my device, which did not help.
I then took a closer look at the OBB (the app is open source, so this was easily possible) and tried to manually extract the OBB ZIP file on my device. This did not work either: Same behavior, Total Commander randomly fails unpacking it with message "Error unpacking: Error writing target file" (perhaps not in this wording, my Android is on German).
Since I suspected the ZIP file (although it's working fine on other devices), I created some ZIP files myself.
Unpacking them on the device, I was able to observe the following:
ZIPs containing large files (for example MP3 files, even if this is pretty pointless) work OK
ZIPs containg a lot of small files (like the original OBB, which contains several hundred files between 100 KiB and 1 MiB) will show the same error
Apart from that, I don't experience any issues with the device (no reboots, force closed apps etc).
Does anybody have an idea on what's going on here? I would RMA it (one month of guarantee left), but I'm afraid that this error will not be reproduced at the service center.
EDIT: I just noticed, that it does not seem to be related only to ZIP files. I connect the device to my PC and copied a large amount of MP3s to it, which finished successfully, everything OK. Then I copied a large amount of small files (the ones from the ZIP archive) and after some time Windows Explorer did not show progress anymore (even though the files are only a few 100 KiB large, after some time name of the file currently copied did not change anymore).
EDIT2: It did the experiment from last edit again, this time at the exact moment Windows Explorer "freezed" a background app on the phone force closed.
Some new observations:
I pushed some TAR files to the device (as before two types: one containg large files, one containg small files) and connected to the device by using ADB shell.
Then, with the following command I extracted the archives:
Code:
tar -xf archive.tar /sdcard/Download/
'Large files' archive: no problems observed.
'Small files' archive: sporadic errors.
If I put some load on the device (starting apps, incoming phone call, ...) suddenly extracting the 'small files' archive throws a lot of errors:
Code:
tar: dummy0015.txt: can't open: No such file or directory
tar: chown 0:0 'dummy0015': No such file or directoy
tar: dummy0063.txt: can't open: No such file or directory
tar: chown 0:0 'dummy0063': No such file or directoy
tar: dummy0065.txt: can't open: No such file or directory
tar: chown 0:0 'dummy0065': No such file or directoy
[...]
Also after rebooting, for a long time extracting the 'small files' archive will throw errors. At this point certainly a lot of background processes are executed, so there is also a lot of CPU load.
So somehow all seems to be traceable back to CPU load. But why?
Heat? But it won't get any worse if I let the device heat up under a pillow and also occurs right after boot.
Electromagnetic interference? If this is the case, one would expect it to be designed badly and therefore other devices affected by it, too.
Instability related to CPU clock? Probably the device clocks up, when there is load. On the other hand: The device runs with standard clock speed and was never overclocked.
Hello,
I did some flashing and was able to narrow the problem down to Android Oreo:
First, I flashed the latest Oreo factory image (8.1.0, OPM4.171019.016.A1, May 2018). Problem persists.
Then, I went back to last Marshmallow build (6.0.1, MTC20K). No problems extracting the files.
Next, I upgraded to last Nougat build (7.1.2, N2G48C, Aug 2017). Again, it works flawlessly.
Finally, I flashed first Oreo build (8.0.0, OPR6.170623.013, Aug 2017). Problem appears again.
All flashing was done using fastboot and the flash-all batch script supplied with the factory images, I did not install or configure anything after flashing, nor did I restore a backup.
So, clearly something in Oreo is 'killing' my device. And nobody else seems to undergo this issues.
Do any of you have any idea what might be causing this or what else I could do to further narrow down the problem?