Database Develop

MyGuide 3100 ROM sample

This is a FLASH-able ROM sample. My question is : Is there any way to edit this and add more programs to it ? (the flash is for some of the MyGuide 3100 devices on the market. another question : is it the same for my device ?)
I tried to flash my device with this... it worked but it still does'n boot. only the boot image has changed. it's still frozent at about 8-10%.
Here is the sample :
http://rapidshare.com/files/140578865/MYGUIDE_3100_DACH_Inand_Update.rar

Guess no one is able to give a hand with this ?
the persisent registry do not want to go away even after flashinf it. i guess it just replaces the os and bootloader anl does not touch the partition that holdes the registry. any ideea how can i make it delete/replace the registry too ?
the device has 3 partitions (it copies the windows folder on RAM) :
1. The bootloader
2. the registry
3. the OS ( called BINFS - i can see but not edit or copy)

hello,
once i received my myguide 3100, it did NOT start.
it rested on a bootscreen showing some kind of "progress bar".
i managed to fix this by installing the firmware again, downloaded at the manufacturers website http://www.myguidegps.com/
it worked for a few months properly. since last week, i've got the same problem again....
but unfortunateley, the manufactuerer does NOT provide any more support...
seems they are insolvent or some...
could one of you guys gife me the original firmware for this device to get it working?? the one in this thread does not.... dont know why
would be SOOO nice

myguide3100 - arival naca400
Hello!
I have a similar problem with a A_rival naca400 which is said to be a clone of myguyde3100. Can you help me with a rom and drivers for myguide3100 try to write in arival?

Bricked my device using the downloaded firmware
Hello. I also have a big problem with My 3100: I downloaded the firmware attached to the first post and fleshed it to my device. Unfortunatelly, something really is wrong , because the update never reached 100%, it allways stops at 98%. Since then (about 2 weeks) i searched all around the web but couldn't find anywhere another firmware (a good one this time). forumleecher, you mentioned you have a valid firmware. Could you be so kind to upload it somewhere for me and others who need it? The original source, www.myguide.com is no longer available, since the company bancrupted and all it's sites are gone. Would be a great help.

Please help us with some good rom for myguide3100.
Looking for a few weeks and yet I found something that works.

You should be very careful by downloading and flashing devices by accident.
There are different hardware platforms of MyGuide 3100 on the market and flashing the wrong ROM will cause boot failures.
Afaik there are no ROMs available in the net (haven't discovered yet) and MyGuide is insolvent.
Cheers

sdr you solve this problem??? and how

MyGuide 3100 GO
same problem here, i am looking 4 a good rom

OK guys. I know how to do total hard reset registry and rest MyGuide 3100(i had the same problem with registry boot keys)
Download this first
http://rapidshare.com/files/299528735/myguide_3100_total_reset.rar
1. First You have to open PNA, disconnect power supply, SD-card etc.
2. After that You have to desolder this big metal cover.
3. Under this cover You will find k9f2g08 Chip.
4. Now you have to connect pin 9 to GDN and connect the battery.
5. Now wait until progress bar start moving, after he start, disconnect Pin 9 from GND.
6. The progress bar should load normal to the end and on the screen should be picture with SD-card.
7. Disconnect battery, assemble PNA and have fun
CHIP ENABLE RUlezz
[email protected]

hi
Mice20 said:
OK guys. I know how to do total hard reset registry and rest MyGuide 3100(i had the same problem with registry boot keys)
Download this first
http://rapidshare.com/files/299528735/myguide_3100_total_reset.rar
1. First You have to open PNA, disconnect power supply, SD-card etc.
2. After that You have to desolder this big metal cover.
3. Under this cover You will find k9f2g08 Chip.
4. Now you have to connect pin 9 to GDN and connect the battery.
5. Now wait until progress bar start moving, after he start, disconnect Pin 9 from GND.
6. The progress bar should load normal to the end and on the screen should be picture with SD-card.
7. Disconnect battery, assemble PNA and have fun
CHIP ENABLE RUlezz
[email protected]
Click to expand...
Click to collapse
unfortunately not functional on MyGuide 3100 go

What exactly is happening with your PNA??>
Maybe You did something wrong.... GND connection or wrong PIN..?
Tell me what display is viewing ???

Hello
My daughter had a problem with her MYGuide 3100, it simply would not switch on any more.
I stripped the unit down and removed the big metal cover (not very well but it worked anyway) and then found this...
You can see a different chip to the Samsung one noted but I have guessed that it is just a matter of where they sourced the chips from.
Chip used to ground pin 9...
So I ground pin 9 and followed the instructions to now find that I get this...
The unit now boots but the progress bar will no longer progress beyond the amount shown in the above photo.
THe unit can no longer be switched off, but just reset. It also is not recognised by Windows and thus is not accessible.
It gives me the impression that sadly the unit is dead

In this type of nand FLASH memory, You have to connect pin nr 30 to GND and fallow with step's .
Pin 9 is NC(non connected) so that's reaction for GND connection is totally normal.
PS. I don't have email notification about post's here so if You can give me a shot about progress on my mail too ([email protected])

Thanks for what you have posted but alas it simply does not work. I found details of the chip too and realised that I needed to short a different pi, the one that you have so kindly noted, but it still does not allow the unit to boot.
This has also been noted here...
http://forums.ebuyer.com/showthread.php?t=11402&page=66
I am guessing that the ROM image is somehow corrupt and even though there is RomUpdate_RD_R01.exe available without a working USB connection, or an image to upload, then it is just a dead GPS.

Ok. So You have broken rom......Last chance to wake him up is desoldering the chip and write rom file on it in external programmer (Willem, cheapest one).
My solution is working for wrong writed registers(but rom must be ok).
Write , if You need deeper details

I appreciate your help. However the sourcing of a programmer and then the likelihood of me being able to desolder that chip has made in beyond my levels of skill to repair.
Thank you again for your help

write with what?
Mice20 said:
Ok. So You have broken rom......Last chance to wake him up is desoldering the chip and write rom file on it in external programmer (Willem, cheapest one).
My solution is working for wrong writed registers(but rom must be ok).
Write , if You need deeper details
Click to expand...
Click to collapse
I still can't find a rom image for 3100 go....

You will find him on working PCB of 3100go. This is the fastest way

Thanks Mice
Mice20 said:
You will find him on working PCB of 3100go. This is the fastest way
Click to expand...
Click to collapse
Thank you for the fast reply, unfortunately I don't have another one....
If you have a hex file or someting like that and you can post it please do it.
Now I try to find a jtag solution.

What's In This Directory

So, i've been working tirelessly to get my camera going again, a number of people have had this same problem, so, I'd like to fix it for them as well. I've finally found my starting point, so, first off, could someone with a working camera please tell me what's in this directory
/dev/msm_camera/control0

Well in the /msm_camera/ folder I have 3 files:
config0
control0
frame0
each with a size of 0, and no extension... and I am unable to copy them anywhere... hope it helps somehow...

Those are device files. Pipes into or out of the HARDWARE DRIVER.
Pipes don't take up space. They can be READ if your device is pumping data out, and the driver can READ data that you send into them.
If you don't know what they are for, chances are good that you should just IGNORE them. In fact, I can guarantee that you should just ignore ***EVERYTHING*** in the /dev path.
dev = short for "device", which is another word for HARDWARE.
EDIT: judging from the file names, the frame0 file is an output -- take a picture and it shows to be read from frame0. The other two appear to be inputs -- configuration (i.e. resolution, mode), and control (i.e. focus, aperture, etc.).

thaquestion said:
So, i've been working tirelessly to get my camera going again, a number of people have had this same problem, so, I'd like to fix it for them as well. I've finally found my starting point, so, first off, could someone with a working camera please tell me what's in this directory
/dev/msm_camera/control0
Click to expand...
Click to collapse
I just want to say I was having camera problems and decided to send it in under warranty. It took me less than an hour to unroot and get Donut back running. They sent me a new (or refurb) one, I put mine in the box, and done. If you still have warranty left, I recommend that path.

[Q] E15 No display after boot loader and seen as cd drive

Hello everyone, I would like to take the time to say that this is my first post, as normally any queery I have a simple search of the site or google would produce a result. Please take the time to read the WHOLE of the following post as there are already similar topics but not exactly the same symptoms showing all at once.
I have a Experia E15i, the phone came with generic (world) software and has only ever been on a stock rom.
The complaint is that when you turn the phone on the post (Sony ericson) comes up as if it were booting, then the screen goes out (including back light) but you can press the menu button and press apps in the app drawer and feel the feedback via the vibrator.
Now I have read a couple of threads on various sites saying that there is a hardware issue and reference to a new screen has been made.
HOWEVER this is where this phone differs when you go in to 'my computer' it shows up as a CD drive and a flash drive (the sd card) but you can't access the 'cd drive' as it asks you to "insert disk".
Now I have done the following thing to try and rectify.
First of all I used the SE "pc companion" and used the 'repair' function and still the exact same problem exists.
Secondly I installed the new 015 baseband (and matched it with the stock 2.1.1.A.0.6 and then did a reboot, the phone still shows up as this fault.
Thirdly I downgraded the baseband to the older one for 2.0.2.A.0.24, and still it stays the same.
I have also done a B.I.T.E test and it seems that the display is U/S I have been able to mirror another phone and the display does not work, so it seems that the screen can't cope with displaying the OS, but when you charge the phone the screen works perfectly.
I have got a hold of all the diagrams required to tracing the system and will update tomorrow when I wake up. But it still doesn't explain the CD drive phenomenon.
I have been in the phone to see if I can see any obvious signs of damage the only signs I can see is on the top side (with the heat shielding) the top left and chip (can't remember it's name) as a slight marking on the outer coating, now normally this would not cause any issues with the chip, unless it has cracked underneath, but then if it had the whole phone wouldn't work, as I believe it to be the rom chip. I have been in there with the appropriate alcohol based cleaner and cleaned it up as best I can with out de-soldering the heat shield.
The only reason I am holding back on buying a new screen is that I can't see how it can be a physical screen error as the controller clearly works (other wise SE wouldn't show) and I can't see how that would effect the fact it is now showing it's a cd drive.
Now if anyone can shed any light on this issue, or combined issues I would be very grateful.

First morning tests
In reply to my own post for clarity, there is stby power present on the correct pin and there is stby return on the correct pin, I am also seeing a date out put in the pins aswell, so it seem to be that the screen in U/S which is good news, as they are easy enough to come by, however it would be nice to find the wiring diagram for the screen (I know sony don't make them and they are a peripheral item) and they are a disposable item so why would they bother, but for the sake of one chip being to blame it would be a lot cheaper for me to replace the chip than the whole screen/display.
As for the phone been seen as a Cd drive, I have still yet to work this out, however the screen is wired in from the second NAND CHIP N1500 [MSM7227/-MDDI] VIA R7000 and R7001 which is where the bootloader is held (this phone is 11w12 and appears to be an unlocked bootloader; could this be clashing with something inside the N1500 and N2400 NAND Chips?) or is it just changing how the pc sees the chipset and assigns a cd drive label to it?
Well I shall order a new screen and keep you all posted how it goes. In the mean time if any one can help then please let me know

No mmcblk0 device being created after emmc connection to PC for debricking [SOLVED]

I have a KF2 which I managed to get twrp on, but the partitions seem to be messed up in some way. When I boot to recovery and do an adb shell, ls /dev/block, there are only loop and ram devices shown. The emmc chip seems OK though, since I can transfer a CM rom to it, but I can't write it to become 'working'.
When I try to wipe or factory reset from recovery, I get an error to the effect that none of the partitions can be mounted. IE
unable to mount /data, /cache, /system, /efs, storage, /data/media during gui startup
also:
unable to find partition size for /boot, /recovery, /bootloader
So I should probably describe how I got here. I was sold a KF2 as a KF1 so assumed it was KF1 and hence bricked it (didn't check for the otter2 id). I opened it, soldered to the main board as described in other threads, dd'ed the working otter2-u-boot-prod-10.2.4 file directly to /dev/sdf2 on the emmc from my ubuntu desktop. Then put it back together and used fast boot to get otter2-twrp-2.6.3.1-recovery.img and otter2-freedom-boot-10.4.6.img on it. Then transferred CM rom to /sdcard with adb push. Rebooted and tried to continue the CM install but when I get to the wipe part, it fails with the above errors. Even from 'advanced wipe' it still says the same (unable to mount etc). Factory reset the same too.
So I took it apart again, connected it back to the computer, and used gparted to examine the file system. It seems OK, it had an error at first (primary gpt corrupt or something, using backup - I think gparted fixed that for me) fairly consistent with what the guys in the emmc soldering thread see. Then back to the kindle boot, same thing happening as before. Eventually I reformatted each ext4 partition using gparted (from the desktop) to try to fix it, still no joy.
So reading lots of threads here by soup and hash, I tried several of their solutions, like fastboot oem format (I had to put the device ID in there to make it work). None of them have worked.
So when I do a:
adb shell parted /dev/block/mmcblk0 print all
I get:
Error: Could not stat device /dev/block/mmcblk0 - No such file or directory.
(and /dev/block/mmcblk0 does not exist - the only files in that dir are ram0, ram1 etc, and loop0, loop1 etc)
That seems like the problem to me. Twrp is not seeing the emmc at all it seems - even though its loaded off the emmc AFAIK? Which seems weird. Surely the device is able to see the emmc and the first few partitions if its booting to twrp - but once in twrp, none of the partitions - or even the device mmcblk0 - is showing up at all. But when I connect it back to the PC, gparted is happy with it all - although all the partitions show up as microsoft type which seems odd. But I can mount them and browse them (the ext4 ones).
Anyone throw any light on this? BTW the wiring is unlikely to be causing this problem because I disconnect all the wires from any 'interconnections' when I put the kindle back together. Although the wires are still connected to the main board, there are no bridges between dat0, dat1 etc, as I am using a connector to isolate them.
EDIT: And theres this in dmesg, which seems suspicous:
<4>[ 1.053588] mmc0: host doesn't support card's voltages
<3>[ 1.053588] mmc0: error -22 whilst initialising MMC card
<4>[ 1.067321] wifi_set_power: 1
<4>[ 1.118896] mmc1: card claims to support voltages below the defined range. These will be ignored.
Thanks, Pete

Well I fixed it, thought I should post back here as its an interesting fault.
Turned out 2 of the pullup resistors were open circuit, obviously my fat fingers and bad soldering! I found it because looking through the datasheet for the emmc chip last night, I noticed that the chip needs pullup resistors on several of the pins (last page of KLM8G2FE3B datasheet which you can find online). Thinking back to the mainboard in the KF2, I remembered the grid of resistors and thought maybe they were the pull up ones. Reason I was thinking about this at all was I wondering if the chip can be ripped out and replaced with a very large SD card, but thats for another day.
Anyway I thought I might buzz out the data lines and CMD as these are the ones with the pullup resistors, to check my soldering. IE I should see the same resistance on each (with respect to +ve). Well 3 of them were 10k, which seems about OK although the datasheet recommends 50k, but this seems in the right range. But 2 were 450k ish. Far too high. If the resistors were blown then this is the kind of resistance I expect to see, back through the memory chip rather than through the pull up resistors to +ve. The bad lines were data1 and CMD btw. Really hard to solder, and I ended up having to solder to the resistor on both, with the result that the resistors blew.
The reason the emmc chip seemed ok when plugged into the computer is probably because the SD card reader provides these pull up resistors in it, making the ones on the board redundant. When the SD is unplugged, there is no pullup on those lines, and the chip is hence not readable - although I am still confused as to how it booted at all, maybe initial boot is only at a reduced data rate which didn't need the pullups, I don't know.
Anyway I put a couple of 10k resistors I had laying around between the still soldered on SD adapter and +ve, so effectively replacing the on board pull up resistors with the external ones. I was then able to install CM and get the tablet running. Since there was not room in the tablet for these large resistors etc, I spent several hours today trying to solder on tiny wires, and solder a couple of smt 10k resistors in place of the test ones. I succeeded eventually, with the wires coming from the rear of the main pcb where most of the wires connect in the 'rescue kf2 with soldering to chip' thread, and then the wires go round the pcb edge to the other side (that you see when you take the back off the tablet). Theres more room this side, and I soldered the new smt resistors on to the wires, and eventually got it working again.
I didnt replace the smt resistors where the old ones went because I simply can't solder this small. It was hard enough connecting those 2 wires to the 2 solder pads. Took hours. Not worth it considering I only paid 13 quid for this tablet but satisfying to fix.
I put this here in case anyone ever finds it useful - perhaps for other things. I still wonder very much could the emmc chip be ripped out - perhaps a large soldering iron held on the back of it for a couple of mins would allow it to float off - and could a micro SD be connected to the 8 solder points used for the rescue project? Looking at the emmc datasheet it seems exactly like an SD card. It can be read and written like an SD by an external computer as we can see from the success of the recovery project. I have made microcontroller circuits (atmega etc) which read and write SD cards and its not rocket science. Part of me wishes this KF2 had been unrecoverable so I could try it. Its something I might try if I pick up another kf2 sometime. But for now enjoying tinkering with this one. I intend to study the datasheet a bit more, see if its completely compatible with the SD protocol, and if so try it. Might post another thread sometime asking some of the more experienced guys here if they have any idea if it will work.

@peterpion you probably saved my day! been pulling my hair trying to figure out why fastboot would work with flash but TWRP wouldn't see the MMC card at all. I essentially destroyed one of the pull up resistors during soldering. Must be this!

My HTC One Mini 2 (memul) screen won't turn on. How to troubleshoot?

Hello.
The full story is here:
Just before the new years eve, me and some friends went to the mountain where under light snowfall and temperatures close to -10°C, we enjoyed putting our youngsters sliding downhill with their sleds. Some of us even went for a little bit of easy snowboarding as all the other tracks were closed. I did not do any snow sledding nor any snowboarding but was strolling around there with my phone in my open pocket so there might was some slight snowfall on the phone.
After that, while we were returning to our urban homes, I was sitting in the back seat of my friend's car and had the phone resting on a niche on the passenger's door. When we stopped at a gas station to refuel under HEAVY snowfall I got off the car to buy some some chocolate and coffees for the travelling party. When I got back home, after about 1 hour, I discovered that my phone wasn't there. A quick recall of my previous actions lead me to the conclusion that my phone must have fell there while the door was open.
I made a phone call to the station where I was told that the phone was found, was working but the screen was not working. I went back there to retrieve the phone which meanwhile had died due to the battery outtage. So under all scenarios my phone could have been exposed to some snowfall while always inside its leather flip case.
tl;dr
My phone was exposed to lower temperatures and snowfall in its flip leather case.
So, now I have a phone that it's screen has died. No cracks or dents or bents or anything like that.
How would you suggest I should troubleshoot?
What are your guesses about what's faulty?

If Im guessing correct the screen might slightly cracked in 1 of the corners, if so the crack will be very light and not easily visible, due to drop.
Thats what I can think of now.

TryllZ said:
If Im guessing correct the screen might slightly cracked in 1 of the corners, if so the crack will be very light and not easily visible, due to drop.
Thats what I can think of now.
Click to expand...
Click to collapse
I will closely examine and report back.
But I have the feeling there were absolutely no cracks.

Like I said the screen looks Ok.
I have plugged it into the USB port and the Notification LED blinks orange.
I will at least try to extract what's within my phone via adb to move to my new Motorola Moto G4.

olspookishmagus said:
Like I said the screen looks Ok.
I have plugged it into the USB port and the Notification LED blinks orange.
I will at least try to extract what's within my phone via adb to move to my new Motorola Moto G4.
Click to expand...
Click to collapse
if it blinks then it lives, the bad news is its not charging.
How long did you leave it charging? could take a while until it starts actually charging due being so empty.
Could be battery its gone due temperatures. but dont see reason why.

kativiti said:
if it blinks then it lives, the bad news is its not charging.
How long did you leave it charging? could take a while until it starts actually charging due being so empty.
Could be battery its gone due temperatures. but dont see reason why.
Click to expand...
Click to collapse
It's charging OK.
The phone was rooted and was running CM, however even though I'm white-listed for USB debugging for this PC, when I reboot to recovery to get a full backup I'm getting this:
Code:
$ sudo adb devices
List of devices attached
_HTC_SERIAL_ unauthorized
$sudo adb shell
error: device unauthorized. Please check the confirmation dialog on your device.
If I reboot into normal again I get full adb rights and now I'm struggling to bypass my lock-screen pattern.
Best adb screenshot so far here: http://i.imgur.com/TOMPNROg.png

olspookishmagus said:
It's charging OK.
The phone was rooted and was running CM, however even though I'm white-listed for USB debugging for this PC, when I reboot to recovery to get a full backup I'm getting this:
Code:
$ sudo adb devices
List of devices attached
_HTC_SERIAL_ unauthorized
$sudo adb shell
error: device unauthorized. Please check the confirmation dialog on your device.
If I reboot into normal again I get full adb rights and now I'm struggling to bypass my lock-screen pattern.
Best adb screenshot so far here: http://i.imgur.com/TOMPNROg.png
Click to expand...
Click to collapse
sorry my bad missread.
Ok so its comming to life.
i would leave the phone charging for a few hours. the heat from the battery will warm the components. Maybe its just bad connection.

olspookishmagus said:
Like I said the screen looks Ok.
I have plugged it into the USB port and the Notification LED blinks orange.
I will at least try to extract what's within my phone via adb to move to my new Motorola Moto G4.
Click to expand...
Click to collapse
Perhaps the cable connecting the LCD to the board might have jolted, a bad connection as @kativiti said.

I will try and backup whatever is possible with ADB while the phone allows it.
Then I will try to pry it open and clean and remove whatever residue I'll find.
And then I will try and replace the faulty parts (starting with the cheapest part first).
But if the screen will still not function that would rule out the digitizer and I should go straight for the LCD, right?

olspookishmagus said:
I will try and backup whatever is possible with ADB while the phone allows it.
Then I will try to pry it open and clean and remove whatever residue I'll find.
And then I will try and replace the faulty parts (starting with the cheapest part first).
But if the screen will still not function that would rule out the digitizer and I should go straight for the LCD, right?
Click to expand...
Click to collapse
yes since the image is in the LCD.
Good luck