OMG I think Ive Killed it!!!!

Discussion in 'Gome Flytouch II' started by leeb, Aug 24, 2011.

  1. leeb

    leeb Member

    Joined:
    Jul 16, 2011
    Messages:
    463
    Likes Received:
    21
    Trophy Points:
    87
    Well, its finally happened...

    I had it JUST like I wanted... except that the GPS still did nothing. Thru terminal the only modules running were the WIFI and something called galcore....

    Since I didnt know what galcore was and I couldnt figure out how to get MODPROBE to work on these Fkng things, I decided to attempt a return to ORIGINAL firmware and see if another module was running there...

    Did a FULL titanium backup (the only smart thing Ive done since I got this beast!) and proceeded to try the install... which naturally failed miserably.

    But, in the process, I fear that the NOR flash has completely given out... as it seems there is NO room for the /system (mtdblock3) to use...

    Here's what it gives out on the 2-pass reload (which would have worked FINE until last nite!)
    (EDITED for brevity and added comments... remind me to do editing IN WORDPAD!!)

    Code:
    Tar extraction failed
    APx200 BBT: Bad block detected(IB): 0xd91
    [COLOR=#ff0000]...[/COLOR]
    [COLOR=#ff0000]ALL THE WAY to[/COLOR]
    [COLOR=#ff0000]...[/COLOR]
    iMAPx200 BBT: Bad block detected(IB): 0xffd
    0x00007ff00000-0x000080000000 : "panic"
    iMAPx200 BBT: Bad block detected(IB): 0xffe
    iMAPx200 BBT: Bad block detected(IB): 0xfff
    imapx200_ssim0 imapx200_ssim0.0: bitbang at c8bbdb08
    gmac-univ Ethernet Driver, V1.0
    eth0: gmac-univ at d0838000 IRQ 32 MAC: 00:1b:14:52:19:26 
    PPP generic driver version 2.4.2
    PPP MPPE Compression module registered
    NET: Registered protocol family 24
    usbmon: debugfs is not available
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    imapx200_usbhost20 imapx200_usbhost20: Infotm Ehci Controller
    imapx200_usbhost20 imapx200_usbhost20: new USB bus registered, assigned bus number 1
    imapx200_usbhost20 imapx200_usbhost20: irq 44, io mem 0x20c81000
    imapx200_usbhost20 imapx200_usbhost20: USB 0.0 started, EHCI 1.00
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 4 ports detected
    ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    imapx200_usbhost11 imapx200_usbhost11: Infotm Ohci Controller
    imapx200_usbhost11 imapx200_usbhost11: new USB bus registered, assigned bus number 2
    imapx200_usbhost11 imapx200_usbhost11: irq 26, io mem 0x20c80000
    usb usb2: configuration #1 chosen from 1 choice
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 4 ports detected
    usbcore: registered new interface driver cdc_wdm
    Initializing USB Mass Storage driver...
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    usbcore: registered new interface driver usbserial
    usbserial: USB Serial Driver core
    USB Serial support registered for GSM modem (1-port)
    usbcore: registered new interface driver option
    option: v0.7.2:USB Driver for GSM modems
    mice: PS/2 mouse device common for all mice
    input: gpio-keys as /devices/platform/gpio-keys/input/input0
    ads7846 spi0.0: touchscreen, irq 1
    input: ADS7846 Touchscreen as /devices/platform/imapx200_ssim0.0/spi0.0/input/input1
    ~~~~~~~~~~~~~~~~~~ power:625, power:624 ,power:624, power:624, power:623~~~~~~~~~~~~~~~~~~~~~~
    iMAPx200 RTCv2, (c) 2009, 2014 InfoTM Microelctronics Co., Ltd
    using rtc device, imap, for alarms
    imapx200_rtc imapx200_rtc: rtc core: registered imap as rtc0
    i2c /dev entries driver
    Linux video capture interface: v2.00
    usbcore: registered new interface driver uvcvideo
    USB Video Class driver (v0.1.0)
    hwid is 6.1.5
    gt2005_xyc_reset
    [SDHCI0]:infoTM sdhci host driver init.
    [sdhci]-SDIO MAX CLOCK RATE = 86400000
    Registered led device: mmc0::
    mmc0: SDHCI controller on info_sdi0 [imapx200_sdi0.0] using ADMA
    [SDHCI1]:infoTM sdhci host driver init.
    channel 1 doesn't work right now
    [sdhci]-SDIO MAX CLOCK RATE = 86400000
    Registered led device: mmc1::
    mmc1: SDHCI controller on info_sdi1 [imapx200_sdi1.1] using ADMA
    [COLOR=#ff0000]wifi_switch module init[/COLOR]
    switch_gpio is 47
    usbcore: registered new interface driver usbhid
    usbhid: v2.6:USB HID core driver
    logger: created 64K log 'log_main'
    logger: created 256K log 'log_events'
    logger: created 64K log 'log_radio'
    logger: created 64K log 'log_system'
    [COLOR=#ff0000]****************************************[/COLOR]
    [COLOR=#ff0000]*** IT IS in here! (just doesnt work!) ***[/COLOR]
    [COLOR=#ff0000]IX210 iDSP driver (c) 2009, 2014 InfoTM[/COLOR]
    [COLOR=#ff0000]IX210 iGPS driver (c) 2009, 2014 InfoTM[/COLOR]
    [COLOR=#ff0000]*** Perhaps the wrong one for this pad? ***
    is this the galcore.ko that I found running?
    ****************************************[/COLOR]
    Advanced Linux Sound Architecture Driver Version 1.0.21.
    **********   iis_clock_rate is 19bfcc00
    es8328: Audio Codec Driver v0.12
    asoc: es8328 <-> imapx200-i2s mapping ok
    mmc1: new high speed SD card at address 0002
    mmcblk0: mmc1:0002 00000 971 MiB 
     mmcblk0: p1
    ALSA device list:
      #0: imapx200 (es8328)
    TCP cubic registered
    NET: Registered protocol family 17
    VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
    imapx200_rtc imapx200_rtc: setting system clock to 2011-08-24 19:42:32 UTC (1314214952)
    Bosch Sensortec Device detected!
    BMA150/SMB380 registered I2C driver!
    bma150 device create ok
    Freeing init memory: 128K
    FOUND calc 114583, divisor 36
    FOUND calc 114583, divisor 36
    iMAPx200 BBT: Bad block detected(IB): 0xffe
    nand_erase_nand: attempt to erase a bad block at page 0x0007ff00
    mtdblock: erase of region [0x0, 0x80000] on "panic" failed
    iMAPx200 BBT: Bad block detected(IB): 0xffe
    nand_erase_nand: attempt to erase a bad block at page 0x0007ff00
    mtdblock: erase of region [0x0, 0x80000] on "panic" failed
    init: Unable to open persistent property directory /data/property errno: 2
    iMAPx200 BBT: Bad block detected(IB): 0xffe
    nand_erase_nand: attempt to erase a bad block at page 0x0007ff00
    mtdblock: erase of region [0x0, 0x80000] on "panic" failed
    iMAPx200 BBT: Bad block detected(IB): 0xffe
    nand_erase_nand: attempt to erase a bad block at page 0x0007ff00
    mtdblock: erase of region [0x0, 0x80000] on "panic" failed
    FOUND calc 114583, divisor 36
    *********imap_add_timer!
    ~~~~~~~~~~~~~~~~~~ power:625, power:624 ,power:624, power:623, power:623~~~~~~~~~~~~~~~~~~~~~~
    yaffs: dev is 32505859 name is "mtdblock3"
    yaffs: passed flags ""
    yaffs: Attempting MTD mount on 31.3, "mtdblock3"
    iMAPx200 BBT: Bad block detected(IB): 0x250
    block 1 is bad
    ... all the way to ...
    iMAPx200 BBT: Bad block detected(IB): 0x32e
    block 223 is bad
    *********imap_add_timer!
    ~~~~~~~~~~~~~~~~~~ power:625, power:624 ,power:624, power:623, power:623~~~~~~~~~~~~~~~~~~~~~~
    yaffs_read_super: isCheckpointed 0
    yaffs: dev is 32505860 name is "mtdblock4"
    yaffs: passed flags ""
    yaffs: Attempting MTD mount on 31.4, "mtdblock4"
    yaffs: restored from checkpoint
    yaffs_read_super: isCheckpointed 1
    [COLOR=#ff0000]....[/COLOR]
    [COLOR=#ff0000]A WHOLE BUNCH OF these...[/COLOR]
    [COLOR=#ff0000]....[/COLOR]
    yaffs tragedy: no more erased blocks
    !!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!
    ~~~~~~~~~~~~~~~~~~ power:625, power:624 ,power:624, power:623, power:623~~~~~~~~~~~~~~~~~~~~~~
    *********imap_add_timer!
    ~~~~~~~~~~~~~~~~~~ power:615, power:614 ,power:613, power:613, power:612~~~~~~~~~~~~~~~~~~~~~~
    *********imap_add_timer!
    ~~~~~~~~~~~~~~~~~~ power:614, power:614 ,power:613, power:612, power:612~~~~~~~~~~~~~~~~~~~~~~
    init: untracked pid 2003 exited
    [COLOR=#ff0000]*********[/COLOR]
    [COLOR=#ff0000]Then it loads what it has room for....[/COLOR]
    [COLOR=#ff0000]*********[/COLOR]
    35    /mnt/system/lib/libopencorehw.so
    46    /mnt/system/lib/libdecx170v.so
    31    /mnt/system/lib/libril.so
    149    /mnt/system/lib/libssl.so
    336    /mnt/system/lib/libopencore_net_support.so
    497    /mnt/system/lib/libbluetoothd.so
    23    /mnt/system/lib/libopencore_mp4localreg.so
    112    /mnt/system/lib/bluez-plugin/audio.so
    22    /mnt/system/lib/bluez-plugin/input.so
    138    /mnt/system/lib/bluez-plugin
    14    /mnt/system/lib/libthread_db.so
    14    /mnt/system/lib/libigps.so
    10    /mnt/system/lib/libwpa_client.so
    4301    /mnt/system/lib/libicudata.so
    381    /mnt/system/lib/libopencore_author.so
    114    /mnt/system/lib/libvorbisidec.so
    6    /mnt/system/lib/libmountproc.so
    54    /mnt/system/lib/libcutils.so
    60    /mnt/system/lib/libaudio.so
    51    /mnt/system/lib/libavutil.so
    6    /mnt/system/lib/libJNIforHDMIService.so
    128    /mnt/system/lib/libomx_amrdec_sharedlibrary.so
    163    /mnt/system/lib/libbinder.so
    50    /mnt/system/lib/libstagefright_omx.so
    25    /mnt/system/lib/libandroid_servers.so
    331    /mnt/system/lib/libsonivox.so
    564    /mnt/system/lib/libasound.so
    54    /mnt/system/lib/liba2dp.so
    167    /mnt/system/lib/libsurfaceflinger.so
    26    /mnt/system/lib/libomx_radec_sharedlibrary.so
    190    /mnt/system/lib/libFFTEm.so
    132    /mnt/system/lib/libomx_m4vdec_sharedlibrary.so
    2404    /mnt/system/lib/libccplayer.so
    453    /mnt/system/lib/libandroid_runtime.so
    5    /mnt/system/lib/libreference-cdma-sms.so
    40    /mnt/system/lib/libmedia_jni.so
    14    /mnt/system/lib/libdrm1_jni.so
    30    /mnt/system/lib/libdecx170p.so
    2879    /mnt/system/lib/libopencore_flvlocal.so
    19    /mnt/system/lib/libopencore_flvlocalreg.so
    479    /mnt/system/lib/libcamera.so
    7    /mnt/system/lib/FlvPlugin.dex
    14417    /mnt/system/lib
    4    /mnt/system/lost+found
    14425    /mnt/system
    8    /mnt/sdcard/android/userdata.img
    2620    /mnt/sdcard/android/uImage
    8    /mnt/sdcard/android/system.img
    1452    /mnt/sdcard/android/ramdisk.img
    4092    /mnt/sdcard/android
    4    /mnt/sdcard/LOST.DIR
    62536    /mnt/sdcard/stage2/system.tar.gz
    328    /mnt/sdcard/stage2/ramdisk_stage2.img
    4    /mnt/sdcard/stage2/system.tar.gz.md5
    4    /mnt/sdcard/stage2/ramdisk_stage2.img.md5
    4    /mnt/sdcard/stage2/data.tar.gz
    4    /mnt/sdcard/stage2/data.tar.gz.md5
    62884    /mnt/sdcard/stage2
    4    /mnt/sdcard/system_tar_out.txt
    124    /mnt/sdcard/fail_reason.txt
    67112    /mnt/sdcard
    
    I have been allowing to re-run in hopes that it clears up again, presuming that it will, but I fear the chip has finally said ENOUGH!!!

    Will just have to see...
    May need to attempt the chip-ectomy after all! :(
     
    Last edited: Aug 24, 2011
  2. leeb

    leeb Member

    Joined:
    Jul 16, 2011
    Messages:
    463
    Likes Received:
    21
    Trophy Points:
    87
    I have it completely disassembled right now, trying to decide if I want to pull chips, since it will not complete an installation now...
    and,
    the CPU shows
    imapx210bm1-80

    How could that possibly be a 1GB cpu when it obviously is 800?

    It looks like even finding the NOR flash for this thing is gonna be a challenge...
    The only source Ive seen lists an 800 (not 400) and Im VERY leery about expanding the capacity when I no NOTHING about the memory map on these beasts...

    The 'replacement' unit should be arriving in a couple of days... hope its memory is better!
    :D
     
  3. leeb

    leeb Member

    Joined:
    Jul 16, 2011
    Messages:
    463
    Likes Received:
    21
    Trophy Points:
    87
    This is the 'last known good' partition of the internal storage. It is also the reason that the pad will not operate... supposedly.

    Code:
    dev: size erasesize name
    mtd0: 00200000 00080000 "ramdisk".............2097152 2MB
    mtd1: 00600000 00080000 "kernel"..............6291456 6MB
    mtd2: 08000000 00080000 "resv"............134217728 128MB
    mtd3: 0c000000 00080000 "system"..........201326592 192MB
    mtd4: 3d800000 00080000 "userdata".......1031798784 984MB
    mtd5: 04000000 00080000 "cache".............67108864 64MB
    mtd6: 1ff00000 00080000 "Local-disk"......535822336 512MB
    mtd7: 00100000 00080000 "panic"...............1048576 1MB
    
    You can see from the total below:

    (NAND) Memory usage [TOTAL] 1980760064 1889MB

    that these storage locations MUST be in the 2GB NAND flash (Samsung)
    and could NOT possibly fit into the 512KB NOR flash (whoever-makes-it)... which I think is the home of U0 and U-Boot...

    SOOOOO.....
    Since the failure of the last install is due to a lack of available flash for /system, I can only conclude that the SAMSUNG NAND flash is at fault.

    Fortunately this makes things a bit easier to test... as finding that
    Samsung K9GAG08U0E (or UOE) is MUCH easier to do... in fact I have a couple available on other devices right now...

    If anyone wants to argue the point Id be willing to listen!
    :cool:
    EDIT: I cannot BELIEVE how much effort I had to put into getting that table lined up! :p
     
    Last edited: Aug 25, 2011
  4. leeb

    leeb Member

    Joined:
    Jul 16, 2011
    Messages:
    463
    Likes Received:
    21
    Trophy Points:
    87
    Just call me 'frawnkensteen'...
    Im almost ready to attempt the NAND swap... tho I have to get the replacement part(s) removed first... Yes, I said partS... as I expect to sacrifice at least ONE to the 'practice god'...

    Why you ask?
    Well, the replacement pad I got from ebay has a defective touchscreen (doesnt respond)... and the problem seems to be on the mainboard... using my 'known good' screen/touchscreen also does nothing at the calibrate... which makes it impossible to use it.

    The guy I bought it from said only that it wouldnt work after an attempted upgrade... but when I got it, the plugs were out with scratches at the holes... obvious signs of having been opened. The only question is: Was it opened because of a bad touchscreen, or did the touchscreen fail because it had been opened?
    We may never know...

    Plus, it also shows a bunch of bad block errors... far too many for any decent device, in my opinion.
    Im beginning to suspect that InfoTM called Samsung and said 'Send me what you have... I dont care how bad they are!' In chinese, of course.... :rolleyes:
    Only partly kidding...

    Anyway, I have a few devices that have this chip on them, and I am willing to 'rob Peter to pay Paul' (as my Mom used to say) to get BOTH of these units working properly and WELL...

    Presuming THIS exercise doesnt destroy the PAD, I will look into the t/s chip (which I found online) and attempt repair of that one.

    My eyes are NOT good for this... but hey, one works with what one has...
    :D
     
    Last edited: Aug 26, 2011
  5. leeb

    leeb Member

    Joined:
    Jul 16, 2011
    Messages:
    463
    Likes Received:
    21
    Trophy Points:
    87
    Up until last nite the 'new unit' had a non-functioning touchscreen...
    Here is why...

    $SUC50147.JPG

    SOMEBODY (and not ME) solder-bridged the ENTIRE connector...

    Probably thought Id get software loaded, find the hardware was broken, and demand to send it back with software installed...
    But... they dont know me very well....
    Never know, huh?
    :D
     
  6. mid

    mid Member

    Joined:
    Aug 28, 2010
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    60
    Location:
    NULL
    Jeez! Why would someone solder-bridge an entire connector? o_0
    And what would they gain from you returning it with software installed?

    It pisses me of seeing people being dishonest while selling stuff on ebay. -_-''

    Did you manage to solder the chips and is it working or are you simply going to use this one if you've already fixed it?
     
  7. dlzc

    dlzc Member

    Joined:
    Feb 10, 2011
    Messages:
    71
    Likes Received:
    8
    Trophy Points:
    72
    Tablet / Device:
    ican 10
    I once tried to assemble a van de Graaf generator using "Liquid Solder", the adhesive.

    I doubt they figured you could do anything without a display. What worries me, is that people are shipping other's rejects...
     
  8. leeb

    leeb Member

    Joined:
    Jul 16, 2011
    Messages:
    463
    Likes Received:
    21
    Trophy Points:
    87
    WHY?
    Ineptitude. Didnt you read the title? LOL

    No, I dont truly BELIEVE the guy planned to do that... thats just my paranoia talking... What I THINK happened is:
    Someone opened the pad, broke the connector 'hold-in' piece and attempted to remove the connector.
    Made it worse (likely with a sledgehammer for a soldering tool) and sold it as 'software defective'. THAT was his mistake. If he had said ANYTHING about the touchscreen not working also, I wouldnt have started a case against him.
    Ebay got him by the skruff of the neck (I guess, lol) and told him to make it right. He wanted a return for a full refund.
    By then I had found this and gotten it working, so I said 'UH unh... I dont think so. I have successfully repaired the SOLDER-BRIDGE damage that had been done and I do NOT intend to return the unit now.'
    Suspect it got him in some hot water with EBAY tho... as it should. FULL DISCLOSURE is the ebay seller's friend!


    brb... googling 'van der Graff generator....

    Ah yes! I remember them having one of those in Biology class once (why? IDK)...
    We all lined up hand-in-hand and the last guy held a flourescent light... the guy on the other end touched the globe and the light glowed. Kewl! LOL

    (so... did it work? or too much resistance...?)

    In fact, I couldnt do much w/o the touchscreen either, until I got it fixed long enough to calibrate.
    NOW, although the repair has failed and I will require a new connector (from somewhere), iCAN (lol) connect mouse and keyboard and, that way, it is operational.

    I was also correct about the asessment RE storage.... IT's failures directly affect the user-installed apps... it will only take about 6 of 'em before it says it is out of room.

    What bothers ME is that INFOTM is shipping Samsung's rejects...

    I have NOT as yet done anything on the NAND... it is going to require MUCHO delicacy and, likely, I will need to build a 'hot air solder gun' IOT do it right with the least amount of collateral damage. I have already lost a solder pad on the 'new unit' t/s connector (which I can bridge to the test-points with success), so I want to be able to say THAT IS GOING TO BE THE LAST CASUALTY.

    Famous last words. :rolleyes:
    :D
     
    Last edited: Aug 31, 2011
  9. dlzc

    dlzc Member

    Joined:
    Feb 10, 2011
    Messages:
    71
    Likes Received:
    8
    Trophy Points:
    72
    Tablet / Device:
    ican 10
    Liquid solder is just a name for a silver looking glue, with no conductive properties. And if it wets to metal at all, it will wick in and "sever" even a good mechanical joint. Too much resistance. The oscillator tube's heater did not even glow.

    I used to believe what Marketing people said... (well, they did say "solder"...). Of course I thought the Titanic was made of titanium for a long time...
     
  10. leeb

    leeb Member

    Joined:
    Jul 16, 2011
    Messages:
    463
    Likes Received:
    21
    Trophy Points:
    87
    My bad...
    :eek:
    I was thinking of JB Weld... It DOES conduct ... and rust... just like 'real' metal!
    Has been a lifesaver many times.
    :cool:
     
  11. leeb

    leeb Member

    Joined:
    Jul 16, 2011
    Messages:
    463
    Likes Received:
    21
    Trophy Points:
    87
    I have (2) donor chips ready to go... 'borrowed' from a couple of el-cheapo Chinese netbooks...
    (at least the parts wont feel lonely!) :rolleyes:

    Have the 'difficult' part to go... removal of the old NAND without damaging the board, (chip-quick is good for this!) and THEN the installation of the replacement.

    THEN, hoping Im right and the U0/u-boot are in the 512k NOR! :eek:

    Impatience with soldering is a big problem for me... particularly when I have to use the battery-powered, more-accurate, finicky-as-shyt gun... it runs down SO FAST... and I get frustrated with it... then I make mistakes like trashing pads...

    Of course, the 'big' one has such a wide tip I cant use it on SMT devices without bridging pins...

    Having trouble finding a suitable replacement for the 'new' tablet's touchscreen connector... and have now lost 2 connector pads from the above issue... lucky there are test-points close that can be called upon to make contact!

    I think I will wait until my days off again before I actually dismember the device...
    MUST BE PATIENT with this!!!
    :D
    EDIT:
    I FINALLY found a source for the 4-pin connector for the 'new' tablet's touchscreen!!!!
    http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=A100834CT-ND
    (Just in case anyone is interested....)
    :D
     
    Last edited: Sep 1, 2011
  12. leeb

    leeb Member

    Joined:
    Jul 16, 2011
    Messages:
    463
    Likes Received:
    21
    Trophy Points:
    87
    Last nite I thought I needed to reload the clockwork recovery I got installed not-too-long-ago, so I hooked things up and opened the folder...
    Loaded it up...

    SURPRISE!!!

    It was v4.0.1.5 !!!! (The previous copy was 2e!)

    AND, it SEEMS to work correctly!!!

    Unsure if that means anything to these pads since they are still questionable, but it seems to have all the abilities I would need from it, AND runs!

    Happy Camper is Me!
    (I have SO MANY COPIES of SO MUCH 'STUFF' on my computer Im lucky I havent loaded 95 on the tablet!)
    :D

    EDIT:

    Things are more interesting every minute...
    In a fit of dispair, I intentionally dropped the 'memory-issue' pad on its back on a hard carpeted floor (here at work). When I did, it wouldnt come up past the INFOTMIC screen...
    So...

    I dropped it again, on its FRONT, from the same distance (well, okay. Twice. :rolleyes: ). THEN I attempted a reload of the straggulus 2-parter (which for the last month-or-so has ALWAYS FAILED on the 2nd pass from lack of space)...

    NOW, it seems to have enough useable space to load up. :confused:
    (It isnt running b/c it doesnt like the 6.1.2(672) u-boot it has in it now, and the install doesnt modify the U0 or u-boot...)

    Managed to get the 6.1.5(587) loaded and IT IS RUNNING!!! Had to stop due to battery drain! Once I get it 'just right' I can use the CWM I found and BACK THIS PIG UP!!!! :)

    Im beginning to think that, before actual NAND surgery, I should perhaps simply re-wet the leads on the NAND and see how it does after that. Perhaps it is just a case of 'bad connections'!
    :D
     
    Last edited: Sep 2, 2011
  13. leeb

    leeb Member

    Joined:
    Jul 16, 2011
    Messages:
    463
    Likes Received:
    21
    Trophy Points:
    87
    It looks like the 4.0.1.5 CWM will not run on the 0.6.1.x(587) U0/u-boots
    *** ON THESE MACHINES ***...
    and,
    the stragulus 2-part install will ONLY run on the 587 version(s)
    *** ON THESE MACHINES ***
    (or so it seems!)...
    and, right now, it is the ONLY version I am able to bring up and run... (storage issue is likely culprit again)

    So I plan to try other versions 2c if they:
    1) will run in the 587 environment, and
    2) are configured with the same partitions...

    Still looking at NAND-surgery, but for the moment, and as long as this one pad will run with 'what it has', I think Ill work for a 'transferable backup' so that the 2nd pad will be able to use it as well.

    :D
     
    Last edited: Sep 4, 2011
  14. leeb

    leeb Member

    Joined:
    Jul 16, 2011
    Messages:
    463
    Likes Received:
    21
    Trophy Points:
    87
    Finally got the new touchscreen cable connector(s) I ordered. Will confirm that the t/s is working again before I start the NAND surgery, tho I have decided that this one will be the first guinea-pig...

    Would hate to lose it but better this one than one that is more-or-less in one piece.
    (The other has a defective WIFI switch but it does not prevent operation, so I leave it alone!)
    :D
     
  15. leeb

    leeb Member

    Joined:
    Jul 16, 2011
    Messages:
    463
    Likes Received:
    21
    Trophy Points:
    87
    I have been intentionally delaying the work until the weekend, as I do NOT want to feel rushed about doing this/these fixes/changes...
    and I would, knowing that I have to stop so I can work tomorrow, etc.

    Tonite I will attach (one of) the new ribbon connector(s) and then confirm that the touchscreen works properly.
    Once that is done... it is 'under the anesthesia' and then, 'the knife'! :eek:
     

Share This Page

Search tags for this page
cwm 613 recovery for tablet one touch c
,

galcore daemon

,
galcore daemon what is
,
galcore daemon wikipedia
,
galcore demon
,
galcoredeamon
,
imapx210bm1-80 firmware
,
imapx210bm1-80 jtag
,
usbusb1 not feund tablet
,
yaffs tragedy