SGS 9000 dead - black screen - Galaxy S I9000 General

Dear all,
I recenetly added Voodoo and LauncherPro to my SGS. All was well. However, today after mounting the discs are USB devices, I ran into some problems after I started using it again:
1) The external SD is marked as corrupted.
2) With USB debugging enabled, the SGS does not show up in the list of devices (lsusb does not show the Samsung devices). adb devices does not list anything.
Next, I rebooted the 'phone. The device can back, the media scanner ran, and the option to unlock the SIM card was displayed, and then it went black, and this was it. Nothing happens when I press any keys.
I plugged into the USB cable and got this from the messages logs on the host computer:
Code:
Nov 23 14:15:11 AMS-L0769L kernel: [ 5351.652593] usb 2-3: new high speed USB device using ehci_hcd and address 10
Nov 23 14:15:11 AMS-L0769L kernel: [ 5351.947495] usb 2-3: configuration #3 chosen from 1 choice
Nov 23 14:15:11 AMS-L0769L kernel: [ 5352.003925] cdc_acm 2-3:3.0: ttyACM0: USB ACM device
Nov 23 14:15:12 AMS-L0769L kernel: [ 5352.127067] scsi6 : SCSI emulation for USB Mass Storage devices
Nov 23 14:15:17 AMS-L0769L kernel: [ 5357.131940] scsi 6:0:0:0: Direct-Access SAMSUNG GT-I9000 Card 0000 PQ: 0 ANSI: 2
Nov 23 14:15:17 AMS-L0769L kernel: [ 5357.139922] scsi 6:0:0:1: Direct-Access SAMSUNG GT-I9000 0000 PQ: 0 ANSI: 2
Nov 23 14:15:17 AMS-L0769L kernel: [ 5357.150786] sd 6:0:0:0: Attached scsi generic sg2 type 0
Nov 23 14:15:17 AMS-L0769L kernel: [ 5357.152738] sd 6:0:0:1: Attached scsi generic sg3 type 0
Nov 23 14:15:17 AMS-L0769L kernel: [ 5357.159490] sd 6:0:0:0: [sdb] Attached SCSI removable disk
Nov 23 14:15:17 AMS-L0769L kernel: [ 5357.162228] sd 6:0:0:1: [sdc] Attached SCSI removable disk
I can get in via "adb shell" and su to root.
The sd cards are mounted and fine, but the screen is still black:
Code:
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
I have removed the external SD and rebooted, but have the same symptons.
Any idea on how to resurrect the device? I can post the output of dmesg if required.

Problems solved by removing the SD card and SIM card, and with several reboots.

Related

WM5storage and the trinity

Hi,
Since I use Linux on all my primary workstations, I wanted to use WM5orage to export my sdcard in the trinity as an external disk. The program starts fine and the computer also recognizes it. There does however seem to be a problem because the computer starts complaining about I/O error and never succeeds in accessing the drive.
for the interested, this is what my log shows:
Dec 23 17:34:49 laptopia kernel: scsi6 : SCSI emulation for USB Mass Storage devices
Dec 23 17:34:54 laptopia kernel: Vendor: WM5torag Model: TRIN100 Rev: 1.60
Dec 23 17:34:54 laptopia kernel: Type: Direct-Access ANSI SCSI revision: 00
Dec 23 17:34:54 laptopia kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 2
Dec 23 17:34:54 laptopia kernel: SCSI device sdb: 3970048 512-byte hdwr sectors (2033 MB)
Dec 23 17:34:55 laptopia kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 2
Dec 23 17:34:55 laptopia last message repeated 5 times
Dec 23 17:34:55 laptopia kernel: sdb: Write Protect is off
Dec 23 17:34:55 laptopia kernel: sdb: assuming drive cache: write through
Dec 23 17:34:55 laptopia kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 2
Dec 23 17:34:56 laptopia kernel: SCSI device sdb: 3970048 512-byte hdwr sectors (2033 MB)
Dec 23 17:34:56 laptopia kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 2
Dec 23 17:34:56 laptopia last message repeated 5 times
Dec 23 17:34:57 laptopia kernel: sdb: Write Protect is off
Dec 23 17:34:57 laptopia kernel: sdb: assuming drive cache: write through
Dec 23 17:34:57 laptopia kernel: sdb: sdb1
Dec 23 17:34:57 laptopia kernel: sd 6:0:0:0: Attached scsi disk sdb
Dec 23 17:34:57 laptopia kernel: sd 6:0:0:0: Attached scsi generic sg0 type 0
Dec 23 17:34:57 laptopia kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 2
Dec 23 17:34:59 laptopia last message repeated 12 times
Dec 23 17:34:59 laptopia kernel: sd 6:0:0:0: SCSI error: return code = 0x70000
Dec 23 17:34:59 laptopia kernel: end_request: I/O error, dev sdb, sector 8
Dec 23 17:34:59 laptopia kernel: printk: 5 messages suppressed.
Dec 23 17:34:59 laptopia kernel: Buffer I/O error on device sdb, logical block 1
Dec 23 17:34:59 laptopia kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 2
Dec 23 17:35:00 laptopia last message repeated 5 times
Dec 23 17:35:00 laptopia kernel: sd 6:0:0:0: SCSI error: return code = 0x70000
Dec 23 17:35:00 laptopia kernel: end_request: I/O error, dev sdb, sector 16
Dec 23 17:35:00 laptopia kernel: Buffer I/O error on device sdb, logical block 2
Dec 23 17:35:00 laptopia kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 2
Dec 23 17:35:01 laptopia last message repeated 6 times
Dec 23 17:35:01 laptopia kernel: sd 6:0:0:0: SCSI error: return code = 0x70000
Dec 23 17:35:01 laptopia kernel: end_request: I/O error, dev sdb, sector 40
Dec 23 17:35:01 laptopia kernel: Buffer I/O error on device sdb, logical block 5
Dec 23 17:35:01 laptopia kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 2
Dec 23 17:35:02 laptopia last message repeated 5 times
Dec 23 17:35:02 laptopia kernel: sd 6:0:0:0: SCSI error: return code = 0x70000
Dec 23 17:35:02 laptopia kernel: end_request: I/O error, dev sdb, sector 48
Dec 23 17:35:02 laptopia kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 2
Dec 23 17:35:03 laptopia last message repeated 5 times
etc..etc..etc...
anyone that has gotten this to work correctly ?
found solution
Just to reply to my own post, but I found the solution.
I just had to turn off the advanced USB network functionality off in the usb to pc connection settings. now it works perfectly
In Hermes you need to do this before using WM5Torage:
Settings --> Connections --> USB to PC and disable "advanced USB functions"
Try to see if it's the same on Trinity.
lol
posted at the same time!
pof said:
In Hermes you need to do this before using WM5Torage:
Settings --> Connections --> USB to PC and disable "advanced USB functions"
Try to see if it's the same on Trinity.
Click to expand...
Click to collapse
Nice Trick! It works!
BTW I had to change some settings in Pocket Controller (It made the sugestions itself) but everything is working now.
Gracias Pof.
Something is not right. I click Settings --> Connections --> USB to PC but then the screen flashes once but nothing happens. Any ideas?
Never mind... got it. WisBar Advance was interfering with it and as soon as I shut WisBar down then I could get into the setting.
sorry I'm a bit slow,
On my i-Mate Jam, i used the Card Export (which allows you to let your pc see your ppc as a usb-stick)
But can i do this with the trinity without Card Export?
(cuz it doesn't matter if i enable of disable the setting above it still starts up Active Sync)
Azamat said:
sorry I'm a bit slow,
On my i-Mate Jam, i used the Card Export (which allows you to let your pc see your ppc as a usb-stick)
But can i do this with the trinity without Card Export?
(cuz it doesn't matter if i enable of disable the setting above it still starts up Active Sync)
Click to expand...
Click to collapse
Yes, WM5Storage will work on the trinity if you follow the steps above. I was having problem until I did the same. Now it works flawlessly and best of all WM5Storage is free!
card export works too with this trick.
Card export II
hmm I'm having a problem with card export and wm5storage.
Changing the advanced USB functions doesnt help. With wm5storage I was getting an f1 error..sorry cant remember the exact error message.
Card export II ver 2.20 wasnt working either
Just now I tried the latest release of Card export ver 3.00 and im getting error cant connect to driver interface.
You guys actually got either wm5storage or Card Export to work on ya trinity's? cause im having no end of trouble with it and really miss the feature since upgrading from my Magician, because we can't install active sync on my University computers.
Device
Dopod D810
ROM 1.23.707.6 DOPODASIA WWE GPS
Radio 1.35.00.11
OS 5.1.461
CPU Samsung SC32442A-400MHz
Thanks guys! got my trinity this week and I was very disappointed when WM5torage wouldn't work, its one of my most used programs!
thanks perfectly working fine!
i thought schaps rom with wm5torage is useless!
up for you bro!
wm5torage for my p3600i (and previously p3600) doesn't work
pof said:
In Hermes you need to do this before using WM5Torage:
Settings --> Connections --> USB to PC and disable "advanced USB functions"
Try to see if it's the same on Trinity.
Click to expand...
Click to collapse
Hello,
my p3600i (and previously had a p3600) doesn't work using wm5torage. I'm running tnyynt's wm6.1 rom, when i go to "Settings --> Connections --> USB to PC", i see "Enable advanced network functionality". is this the same thing you guys are referring to? i unchecked this but no luck.
wm5torage version i'm trying to use is 1.8, i also tried 1.7 before but that doesn't work either. my laptop just don't see my card. I used a 8gb microsd with a mini-sd adaptor and also a 4 gb mini-sd, both didn't work.
hopefully someone can help me out.
thanks!

Android SDK on Linux and Vibrant

I installed Android SDK for linux on my laptop, I have my vibrant connected via USB and USB Debugging is checked, when I try to see if adb detected the phone I get
~/android/android-sdk-linux_86/tools$./adb devices
List of devices attached
???????????? no permissions
~/android/android-sdk-linux_86/tools$
Any ideas?
In my logs I see it's been detected
Jul 21 11:33:08 host kernel: [343023.204148] usb 2-2: new high speed USB device using ehci_hcd and address 8
Jul 21 11:33:08 host kernel: [343023.337973] usb 2-2: configuration #3 chosen from 1 choice
Jul 21 11:33:08 host kernel: [343023.339926] cdc_acm 2-2:3.0: ttyACM0: USB ACM device
Jul 21 11:33:08 host kernel: [343023.343833] scsi11 : SCSI emulation for USB Mass Storage devices
Jul 21 11:33:13 host kernel: [343028.346328] scsi 11:0:0:0: Direct-Access SAMSUNG SGH-T959 Card 0000 PQ: 0 ANSI: 2
Jul 21 11:33:13 host kernel: [343028.346887] scsi 11:0:0:1: Direct-Access SAMSUNG SGH-T959 0000 PQ: 0 ANSI: 2
Jul 21 11:33:13 host kernel: [343028.353861] sd 11:0:0:0: Attached scsi generic sg2 type 0
Jul 21 11:33:13 host kernel: [343028.355185] sd 11:0:0:1: Attached scsi generic sg3 type 0
Jul 21 11:33:13 host kernel: [343028.358528] sd 11:0:0:0: [sdb] Attached SCSI removable disk
Jul 21 11:33:13 host kernel: [343028.360075] sd 11:0:0:1: [sdc] Attached SCSI removable disk
I had the same problem on my computer. Here is how I fixed it.
cd /android sdk/tools/
sudo ./adb kill-server
sudo ./adb start-server
sudo ./adb devices
That should fix it.
Sent from my SAMSUNG-SGH-I897 using XDA App
You have to put the sdk in the C: drive and use the command
cd C:\android-sdk-windows-2.xx_rx\android-sdk-windows-2.xx_rx\tools
http://forum.xda-developers.com/showthread.php?t=502010
http://forum.xda-developers.com/showthread.php?t=517874
alexmullins posted the quick fix - run the adb daemon as root. Or you can modify udev so your the vibrant is mounted with the correct permissions:
Create or edit the file
Code:
/etc/udev/rules.d/51-android.rules
and add the following line:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
Which states something like: "when a usb filesystem with vendor id of 04e8 (Samsung Vibrant) is mounted, apply the 0666 file permissions."
Double check that your vendor id matches "04e8" by running lsusb. Look for your vibrant in that list.
Hope this helps.
@bbwharris
I did not know about your fix. Thanks for that
Sent from my SAMSUNG-SGH-I897 using XDA App
guys,
Thanks a ton!!!
I am going to tinkle with in a bit.
And whoever pointed me to the "C" drive, I hope you like your BSOD's LOL
[EDIT]
List of devices attached
T959c9e2869c device
YES!!!!!!!!!!
[/EDIT]
lqaddict said:
I installed Android SDK for linux on my laptop, I have my vibrant connected via USB and USB Debugging is checked, when I try to see if adb detected the phone I get
~/android/android-sdk-linux_86/tools$./adb devices
List of devices attached
???????????? no permissions
~/android/android-sdk-linux_86/tools$
Any ideas?
In my logs I see it's been detected
Jul 21 11:33:08 host kernel: [343023.204148] usb 2-2: new high speed USB device using ehci_hcd and address 8
Jul 21 11:33:08 host kernel: [343023.337973] usb 2-2: configuration #3 chosen from 1 choice
Jul 21 11:33:08 host kernel: [343023.339926] cdc_acm 2-2:3.0: ttyACM0: USB ACM device
Jul 21 11:33:08 host kernel: [343023.343833] scsi11 : SCSI emulation for USB Mass Storage devices
Jul 21 11:33:13 host kernel: [343028.346328] scsi 11:0:0:0: Direct-Access SAMSUNG SGH-T959 Card 0000 PQ: 0 ANSI: 2
Jul 21 11:33:13 host kernel: [343028.346887] scsi 11:0:0:1: Direct-Access SAMSUNG SGH-T959 0000 PQ: 0 ANSI: 2
Jul 21 11:33:13 host kernel: [343028.353861] sd 11:0:0:0: Attached scsi generic sg2 type 0
Jul 21 11:33:13 host kernel: [343028.355185] sd 11:0:0:1: Attached scsi generic sg3 type 0
Jul 21 11:33:13 host kernel: [343028.358528] sd 11:0:0:0: [sdb] Attached SCSI removable disk
Jul 21 11:33:13 host kernel: [343028.360075] sd 11:0:0:1: [sdc] Attached SCSI removable disk
Click to expand...
Click to collapse
ADB has to be run with root access. sudo ./adb
bbwharris said:
alexmullins posted the quick fix - run the adb daemon as root. Or you can modify udev so your the vibrant is mounted with the correct permissions:
Create or edit the file
Code:
/etc/udev/rules.d/51-android.rules
and add the following line:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
Which states something like: "when a usb filesystem with vendor id of 04e8 (Samsung Vibrant) is mounted, apply the 0666 file permissions."
Double check that your vendor id matches "04e8" by running lsusb. Look for your vibrant in that list.
Hope this helps.
Click to expand...
Click to collapse
I implemented this work around, and no need for root to run it anymore
Credit goes to bbwharris!!!
HAHAHAHA
BUMPity bump bump BIA......
Thats not a work around; thats following the install instructions from google
http://developer.android.com/guide/developing/device.html#setting-up

[Q] unable to root nexus 7

hi, i have a 2012 nexus 7 (4.4.2). the only windows-pc i have is my work laptop which i dont have the admin password for stuff like installing drivers and mounting usb drives. so i am booting it using fedora live-usb.
usb debugging is checked in developer options and usb computer connection is set to mtp. this is what i see when it is connected to the pc while on the home screen:
Code:
[[email protected] nexus]$ uname -a -m -p
Linux schneidz 3.9.5-301.fc19.x86_64 #1 SMP Tue Jun 11 19:39:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
[[email protected] nexus]$ adb devices
List of devices attached
015d30e1223xxxxx device
[[email protected] ~]$ sudo tail -f /var/log/messages
...
Mar 16 15:59:57 schneidz systemd[1]: Started Hostname Service.
Mar 16 16:00:45 schneidz kernel: [12741.755058] usb 3-1: new high-speed USB device number 24 using xhci_hcd
Mar 16 16:00:45 schneidz kernel: [12741.783549] usb 3-1: New USB device found, idVendor=18d1, idProduct=4e42
Mar 16 16:00:45 schneidz kernel: [12741.783558] usb 3-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[COLOR="Purple"]Mar 16 16:00:45 schneidz kernel: [12741.783560] usb 3-1: Product: Nexus 7
Mar 16 16:00:45 schneidz kernel: [12741.783562] usb 3-1: Manufacturer: asus
Mar 16 16:00:45 schneidz kernel: [12741.783563] usb 3-1: SerialNumber: 015d30e1223xxxxx[/COLOR]
Mar 16 16:00:45 schneidz colord: Device added: sysfs-asus-Nexus_7
but when i reboot the tablet into fastboot mode this is what i see on the pc:
Code:
[[email protected] nexus]$ adb reboot bootloader
[[email protected] ~]$ sudo tail -f /var/log/messages
Mar 16 16:11:57 schneidz kernel: [13414.076731] usb 3-1: USB disconnect, device number 24
Mar 16 16:11:57 schneidz colord: device removed: sysfs-asus-Nexus_7
Mar 16 16:11:57 schneidz dbus[657]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Mar 16 16:11:57 schneidz dbus[657]: [system] Successfully activated service 'org.freedesktop.hostname1'
Mar 16 16:11:57 schneidz dbus-daemon[657]: dbus[657]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Mar 16 16:11:57 schneidz dbus-daemon[657]: dbus[657]: [system] Successfully activated service 'org.freedesktop.hostname1'
Mar 16 16:11:57 schneidz systemd[1]: Starting Hostname Service...
Mar 16 16:11:57 schneidz systemd[1]: Started Hostname Service.
Mar 16 16:11:59 schneidz kernel: [13416.496065] usb 3-1: new high-speed USB device number 25 using xhci_hcd
Mar 16 16:11:59 schneidz kernel: [13416.510152] usb 3-1: New USB device found, idVendor=18d1, idProduct=4e40
Mar 16 16:11:59 schneidz kernel: [13416.510163] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[COLOR="Purple"]Mar 16 16:11:59 schneidz kernel: [13416.510169] usb 3-1: Product: Android
Mar 16 16:11:59 schneidz kernel: [13416.510183] usb 3-1: Manufacturer: Google, Inc
Mar 16 16:11:59 schneidz kernel: [13416.510186] usb 3-1: SerialNumber: 015d30e1223xxxxx[/COLOR]
Mar 16 16:11:59 schneidz mtp-probe: checking bus 3, device 25: "/sys/devices/pci0000:00/0000:00:1c.7/0000:25:00.0/usb3/3-1"
Mar 16 16:11:59 schneidz mtp-probe: bus: 3, device: 25 was not an MTP device
...
[[email protected] nexus]$ adb devices
List of devices attached
[[email protected] nexus]$ fastboot oem unlock
< waiting for device >
and it hangs forever. whats weird is that it lists a different product and manufacturer (eventhough the serial numbers match what is on the tablet screen in the fastboot menu -- although product name says grouper). am i doing the wrong method to root this thing (i always thought that nexus devices were the easiest to root) ?
the problem was that i needed to be logged in as root in fedora.

Phone bricked - is this a hardware problem?

Hi,
my phone stopped working this morning pretty much out of the blue: It was working fine one moment but then switched off, even though the battery was practically full, and could not be turned on again.
I think it was stuck in a boot loop: It hung at the LG logo, the LED was alternating between blue and green, but nothing else happened. I also wasn't able to reach the recovery mode.
After some research I made it to download mode and tried to flash a stock ROM with LG Flash Tool - this had the effect that I now can't even go to download mode anymore.
When I plug the phone into my Linux laptop and run `dmesg` I get this output:
[ 5937.301262] usb 2-3.4: new high-speed USB device number 103 using xhci_hcd
[ 5937.389598] usb 2-3.4: config 1 has an invalid interface number: 20 but max is 1
[ 5937.389603] usb 2-3.4: config 1 has no interface number 1
[ 5937.389960] usb 2-3.4: New USB device found, idVendor=05c6, idProduct=9006
[ 5937.389965] usb 2-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5937.389967] usb 2-3.4: Product: QHSUSB__BULK
[ 5937.389969] usb 2-3.4: Manufacturer: LG Electronics Inc.
[ 5937.389971] usb 2-3.4: SerialNumber: 1234567890ABCDEF
[ 5937.390555] usb-storage 2-3.4:1.20: USB Mass Storage device detected
[ 5937.390864] scsi host220: usb-storage 2-3.4:1.20
[ 5938.389691] scsi 220:0:0:0: Direct-Access Qualcomm MMC Storage 1.00 PQ: 0 ANSI: 2
[ 5938.390191] sd 220:0:0:0: Attached scsi generic sg2 type 0
[ 5938.390414] sd 220:0:0:0: [sdc] 30777344 512-byte logical blocks: (15.8 GB/14.7 GiB)
[ 5938.390537] sd 220:0:0:0: [sdc] Write Protect is off
[ 5938.390540] sd 220:0:0:0: [sdc] Mode Sense: 0f 0e 00 00
[ 5938.390671] sd 220:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 5938.405959] sdc: sdc1 sdc2 sdc3 sdc4 sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 sdc11 sdc12 sdc13 sdc14 sdc15 sdc16 sdc17 sdc18 sdc19 sdc20 sdc21 sdc22 sdc23 sdc24 sdc25 sdc26 sdc27 sdc28 sdc29 sdc30 sdc31 sdc32 sdc33 sdc34 sdc35 sdc36
[ 5938.409354] sd 220:0:0:0: [sdc] Attached SCSI disk
[ 5938.469814] usb 2-3.4: USB disconnect, device number 103
[ 5938.473198] sd 220:0:0:0: [sdc] Synchronizing SCSI cache
[ 5938.473280] sd 220:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 5938.473285] sd 220:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 00 80 00 00 90 00
[ 5938.473288] blk_update_request: I/O error, dev sdc, sector 128
[ 5938.473320] sd 220:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 5938.475248] Buffer I/O error on dev sdc, logical block 16, async page read
[ 5938.475268] Buffer I/O error on dev sdc, logical block 2, async page read
So, it does show up as QHSUSB__BULK but there also seem to be some I/O errors - is that fixable or did the phone just break after 3.5 years of constant usage?
hi there, unfortunately this is a known issue that sometimes happen with LG devices.. it happens to me too and I solved it (but I have other issues, too ): this tool could help you: https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 - only Windows btw.. but PLEASE before trying anything ask for details into the thread because you the tool we'll do invasive stuff on your device! there is no other way to fix so it's a bottleneck, I fear.. the tool itself works and it's safe as long as you know what you are doing, this is what I'm trying to say

Possibly a new DZ09

So I'm new to xda, but this forum has been very helpful in my research and digging into this little gadget.
My girlfriend picked it up online on some auction site for $3, ~$10 total shipped..
I've lurked quite a bit and haven't found anyone with the exact same model as mine, although it may just be a software difference.
Anyway, here's what I've found out.
dmesg:
[ 457.431574] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003
[ 457.431579] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 457.488571] cdc_acm 3-2:1.1: ttyACM0: USB ACM device
[ 457.488894] usbcore: registered new interface driver cdc_acm
[ 457.488896] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 457.496454] usbcore: registered new interface driver usbserial
[ 457.496504] usbcore: registered new interface driver usbserial_generic
[ 457.496544] usbserial: USB Serial support registered for generic
[ 457.514004] usbcore: registered new interface driver option
[ 457.514718] usbserial: USB Serial support registered for GSM modem (1-port)
[ 460.031180] usb 3-2: USB disconnect, device number 3
[ 469.379588] usb 3-2: new full-speed USB device number 4 using xhci_hcd
[ 469.522639] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0002
[ 469.522644] usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 469.522646] usb 3-2: Product: CARNEO
[ 469.522648] usb 3-2: Manufacturer: MediaTek Inc
[ 469.522649] usb 3-2: SerialNumber: 532598606846370
[ 469.617795] usb-storage 3-2:1.0: USB Mass Storage device detected
[ 469.617894] scsi host6: usb-storage 3-2:1.0
[ 469.618060] usbcore: registered new interface driver usb-storage
[ 469.622778] usbcore: registered new interface driver uas
[ 470.640854] scsi 6:0:0:0: Direct-Access MEDIATEK FLASH DISK PQ: 0 ANSI: 0 CCS
[ 470.641722] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 470.642509] sd 6:0:0:0: [sdb] 15564800 512-byte logical blocks: (7.97 GB/7.42 GiB)
[ 470.643253] sd 6:0:0:0: [sdb] Write Protect is off
[ 470.643258] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 470.643836] sd 6:0:0:0: [sdb] No Caching mode page found
[ 470.643842] sd 6:0:0:0: [sdb] Assuming drive cache: write through
lsusb:
-Watch powered on, no selection made (usb charging)
Bus 003 Device 004: ID 0e8d:0002 MediaTek Inc.
-Watch powered on, selected com port from menu
Bus 003 Device 008: ID 0e8d:0003 MediaTek Inc. MT6227 phone
Device info from menus/dialer codes:
[VERSION]
NX9_COB_V1_1_G09_B_HC_IPS_170516_1041
[BRANCH]
11CW1352MP
GPLUS61A_11C_NX9
BUILD:BUILD_NO
SERIAL#:
[BUILD TIME]
2017/05/16 10:41
[MRE VERSION] 3100
HAL_VERNO:
mtk soft ver: 0x1308
mtk hw ver: unknown
ver: 0x74
userid: 0
os: mtk52d
osvern:
model:c1
company:f001
width:0, height:0
maxram:716800
kbd:0
touchscreen:1
cap:0x40010
macro:
fae:dongming
build date: 20170516
buildtime: 2017/05/16 10:41
MRE
[version] 3100
[build time] 2017/05/16 10:41
[mem size] 888868
[support modules]
base
resmrg
comm
sm
resmrgc
ch
draw
gfxold
image
http
IMEIini
mul
xml
aud
camera
cell
pb
sim
sms
soc
status
tel
timer
launch
Dialer codes I found in the rom and tested:
*#9966*# engineering mode ?
*#0000# english
*#00000000# menu (needs sim)
*#6810# ???
*#931# ???
*#902# ???
*#932# ???
*#903# ???
*#993646633# menu of some sort
*#1234# BT mode
*#0044# set language to eng
*#63342835# mtk logo
*#8375# build info
*#06# imei
*#9987# quick test
A2DP ACP Mode: *#1234#
A2DP INT Mode: *#1234#
[MEM TEST]
=============== Memory Detection Report ===============
Internal RAM: Size = 0x0000D000 (52KB)
External RAM: Type = SRAM
Size = 0x00400000 (4MB/32Mb)
NOR Flash: Device ID = "[Winbond] SF_W25Q32JV" (275)
Size = 0x00400000 (4MB/32Mb)
NAND Flash: ERROR: NAND Flash wasnt detected!
cpu/pcb: drive [dot] google[dot]com/file/d/0BzNc0mWX8OZGRkszQXRLZXcxbFU/view?usp=sharing
Identifying mark? drive [dot] google[dot]com/file/d/0BzNc0mWX8OZGTk44VGYxbGNmWGs/view?usp=sharing
Extracted FW: drive[dot]google[dot]com/open?id=0BzNc0mWX8OZGUzJBZEI3R21WYm8
Raw Readback: drive[dot]google[dot]com/open?id=0BzNc0mWX8OZGM0xJVnUyekdHZkU
note: my master copy of the firmware has original bootlogo, but also has my address book & contacts in it, this is a restored/cleaned fw dump, but it has a custom boot animation (rotating picture of dickbutt) I have added.
I've been digging around in the rom, trying to figure out how to remove apps from the firmware to free up space, or possibly add new apps.
I found www[dot]dr-lex[dot]be/hardware/china_phone_flashing[dot]html , which has been very helpful but I'm not able to mount the partition as described in the post.
I'm a regular linux user and have done a bit of cross compiling stuff for my raspi, so i'm kind of curious if theres any info on how to get custom code running on these.
I've found these, but haven't had a chance to dig into them as of yet.
github[dot]com/xobs/fernvale-qemu
github[dot]com/xobs/fernly
In addition to the info above I have a few questions:
Does anyone have any sort of info on how to cut stuff out of the rom or possibly swap apps?
In regards to the CPU, I'm sure its arm, but is it armv5 v6 v7 ?
Has anyone dug into the internals of the nucleus OS?

Categories

Resources