Related
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.
Not sure anyone will be able to help with this -- it's a weird set of circumstances. But maybe someone's got an idea.
I've got a Vogue that the camera button has stopped responding on. When I press it, it gives no resistance, like the button/spring has just fallen out or moved. I'd like to take it to the sprint techs and see if they can pop it open and make sure everything lines up again (this is, after all, the reason for keeping an equipment protection plan).
However, I'm not going to bring it in running Android, so I need to flash it back to stock. How to do that? Bring up bootloader mode by holding, you guessed it, the camera button (and volume down) at startup.
I know that the RUU application can trigger a reboot into bootloader mode from WinMo -- but I'm sure it has to be hooked up to activesync to do so, so that's not much use.
Is there some other way to get from Android to bootloader? Or... is there any other way to... sort of sideload a WinMo ROM from linux, without going through the bootloader mode? (I seriously doubt that part, but I'm grasping here.)
Or is there another way to get into the bootloader that I haven't thought of? I guess I should ask this in less specific vogue forums. Searching has provided me no clues.
Thanks for any ideas.
http://forum.xda-developers.com/showthread.php?t=708376
OK, so clearly my line about searching doing no good was premature. I'm a little embarrassed now. (I failed to search this particular forum, so I feel like a heel.)
Then again, that thread doesn't do me any good... it just confirms the bad.
Anyway, thanks. So that sounds like a pretty firm no. Ugh, stepping down from 5 buttons to 4 on this phone is not a pleasant proposition. Even with the camera button, it's pretty cramped.
The EnterBootloader.exe tool (which I assume is the same as BootLoader.cab in that thread) should be able to do it... unfortunately, I do not have the disassembly chops to figure out how to replicate its functionality.
makkonen said:
OK, so clearly my line about searching doing no good was premature. I'm a little embarrassed now. (I failed to search this particular forum, so I feel like a heel.)
Then again, that thread doesn't do me any good... it just confirms the bad.
Anyway, thanks. So that sounds like a pretty firm no. Ugh, stepping down from 5 buttons to 4 on this phone is not a pleasant proposition. Even with the camera button, it's pretty cramped.
The EnterBootloader.exe tool (which I assume is the same as BootLoader.cab in that thread) should be able to do it... unfortunately, I do not have the disassembly chops to figure out how to replicate its functionality.
Click to expand...
Click to collapse
hey, makk - can you open the case enough one time to get to bootloader, flash to winmo, then take it in? you don't need it to work forever, right? just enough to get it repaired? heck, even if you shorted it closed it might work.
Yeah, that's the option I'm considering now. Just need to pop the case open... which doesn't look like tons of fun. Anyone have any advice on that count? I actually have that tiny torx screwdriver, but that's about as far as I've gotten.
Edit: Searched and found a nice looking guide. See, I can search!
Edit2: Popped it open, jammed a paperclip into the camera button, got the bootloader up, back to WinMo, easy peasy. (OK, actually, horribly frightening. I hate ribbon cables.) Thanks, guys.
Though I no longer need it, building a linux EnterBootloader executable would be pretty nice -- especially since kernel updates are a pretty common occurrence -- it'd be nice to have a utility that'd grab the voguimg.nbh, put it on the sd card, and initiate the reboot all in one fell swoop. (...after doing some pretty thorough checks to make sure you're ready to go messing with your boot partition, of course.)
I took a look at the executable in ida, hoping that it might be simple enough for me to start to get a grasp of (that'd be very simple, for the record)... it was not. That program is the purest essence of confusion (at least to this assembly noob).
Anyway, if anyone has disassembling knowledge around here, and wants to give it a look, it might be pretty simple. (It also might be not simple -- I don't really have much way of knowing.) It's attached here.
makkonen said:
Though I no longer need it, building a linux EnterBootloader executable would be pretty nice -- especially since kernel updates are a pretty common occurrence -- it'd be nice to have a utility that'd grab the voguimg.nbh, put it on the sd card, and initiate the reboot all in one fell swoop. (...after doing some pretty thorough checks to make sure you're ready to go messing with your boot partition, of course.)
I took a look at the executable in ida, hoping that it might be simple enough for me to start to get a grasp of (that'd be very simple, for the record)... it was not. That program is the purest essence of confusion (at least to this assembly noob).
Anyway, if anyone has disassembling knowledge around here, and wants to give it a look, it might be pretty simple. (It also might be not simple -- I don't really have much way of knowing.) It's attached here.
Click to expand...
Click to collapse
COUGHdzoCOUGH
I don't think I'd want to go up on the roof and turn on the dzo-signal for something so trivial as this.
Hey guys, remember those who used Tenfar's custom Recovery to format and partition their internal SD? Remember how it damages the touch screen response on the bottom half inch of the screen? Mine is fixed!!
I don't know what it does, but that particular function damages the PDS file. I've received help from a person who cannot be named and my AT&T Atrix is 100% fixed. Touch screen works flawlessly again, no Wifi issues, no Bluetooth issues and System Updates work fine.
He is working on scrubbing my personal data (serials, etc) from the PDS file and I'll be able to share it with the entire community. But if there's a dev out there who can contact me specifically I can send both the damaged and corrected file right now. I need help figuring out how to apply these serials to a blank PDS file so others in the community can fix this problem as well.
Out of respect, I will not name the person who assisted me as it compromises their work security. They went out on a huge limb and graciously assisted me without any reason other than they're a kick ass person with a huge heart. I'm no programmer by any stretch, but if anyone could assist me I know that there's about a dozen others (maybe more) who really need help fixing this issue. Someone please PM me if they can help!!
i messed up mine too...
any chance to get any help/solution?
One thing you could do is diff the two files to see if they're different. I don't know what the file is either though. Can you ask him how he fixed it? Also can you run the program strings against it? One other thing, is this fixed on changed partitions our did you change them back to the default?
Sent from my MB860 using XDA App
currently i'm in the situation that i can only flash my device, as i cannot complete motosetup, i cannot access debug option so no adb.
i read that the partition with the pds file has been already found
100% mmcblk0p3 PDS.bin 2097152 Persistent Data Storage
(from the atris sbf thread)
would be great to know what is executed in the script of tenfar for the internal sd partitioning, but my knowledge ends here.
so i guess (i'm everything but a developer )
if could be possible to flash/restore that partition with the nvflash selective option
or integrate it in a generic sbf, or the second init will save us all or the gingerbread update...dunno
but i see we are many we touched the wrong button but i don't see any dev interested here or in the thread of tenfar's recovery
i read that psd contains unique infos like the imei so maybe none of the devs wants to release a potential cloning system...
really i don't know even if what im saying is correct
bongd said:
Hey guys, remember those who used Tenfar's custom Recovery to format and partition their internal SD? Remember how it damages the touch screen response on the bottom half inch of the screen? Mine is fixed!!
I don't know what it does, but that particular function damages the PDS file. I've received help from a person who cannot be named and my AT&T Atrix is 100% fixed. Touch screen works flawlessly again, no Wifi issues, no Bluetooth issues and System Updates work fine.
He is working on scrubbing my personal data (serials, etc) from the PDS file and I'll be able to share it with the entire community. But if there's a dev out there who can contact me specifically I can send both the damaged and corrected file right now. I need help figuring out how to apply these serials to a blank PDS file so others in the community can fix this problem as well.
Out of respect, I will not name the person who assisted me as it compromises their work security. They went out on a huge limb and graciously assisted me without any reason other than they're a kick ass person with a huge heart. I'm no programmer by any stretch, but if anyone could assist me I know that there's about a dozen others (maybe more) who really need help fixing this issue. Someone please PM me if they can help!!
Click to expand...
Click to collapse
I am willing to help. This should be relatively easy to do.
in android recovery touch screen works correctly till the bottom, menu/ok button too.
the problem is in the os i guess, but damn i cannot use adb (no debug), seems that neither the early usb+shell root works for me...i can only flash using rsd
and after flashing stock rom i'm stuck at the damned motosetup
maybe are useful infos for you
god knows how i'm desperate
edit i'm reading that for old motorola phones like v3 exist a flashbackup and a psd editor, used to unlock the phones but also to revive damaged ones. maybe...
I've got my original corrupt PDS at home as well as one which has been corrected from a legit developer (can't release any of their information due to work employment security concerns).
I guarantee that it has been 100% fixed though. Bluetooth works, Wifi works, cellular data works and I was even able to upgrade from 1.26 to the latest AT&T OTA update and root everything.
When I announced this no one gave a **** so I didn't make a fuss. I know there are still a few bros with this problem though. I sent my PDS files to another member and they're looking into it. Hopefully you guys can get this working for yourselves as well!
dear friend you are promising salvation with your words, but you're not helping too much...
you gave the phone to that developer, he told what/how he solve the problem?
i understand psd is based on personal imei, so your fixed one is not working on mine etc etc
the point is that possibly your friend as legit developers has access to software to create/flash psd to the atrix.
the question is would be possible to receive the same helping hand?
there is no support in my country for this phone, and i'm not a dev.
so the only chance for me and the rest of the halfbricked people is to get the tools and the tutorial how to from you/your friend.
do you think it is possible?
KeRmiT80 said:
dear friend you are promising salvation with your words, but you're not helping too much...
you gave the phone to that developer, he told what/how he solve the problem?
i understand psd is based on personal imei, so your fixed one is not working on mine etc etc
the point is that possibly your friend as legit developers has access to software to create/flash psd to the atrix.
the question is would be possible to receive the same helping hand?
there is no support in my country for this phone, and i'm not a dev.
so the only chance for me and the rest of the halfbricked people is to get the tools and the tutorial how to from you/your friend.
do you think it is possible?
Click to expand...
Click to collapse
Sorry, I'm not helping much? I'm NOT A DEV!!! I have no obligation to help anyone whatsoever. I lack the technical know-how to help anyone. Please don't ****ing test me.
I've begged every Atrix developer here for help - NO ONE helped other than Tenfar. And unfortunately his advice took me in a completely different direction. No one can point a finger at me for not trying my best. I was so desperate that I got another Atrix because mine was dead for over a month before it was revived.
meneomic has been working feverishly to get his Atrix working as he's encountered the same problem. I've sent him my original and damaged PDS, as well as the one which has been corrected. The strings are not in plain text format and when I viewed it in a Hex editor I found nothing useful. That's all I can do. If someone knows how to put the IMEI and other serial numbers into the fixed PDS they can write it to the appropriate block and this problem will be fixed. That's all that needs to be done... but that alludes me.
I realize there are some people who are upset that their Atrix's aren't working after messing around in the recovery menu, but I've done my best. I have literally stayed up for days working continuously on this. My wife nearly smashed both my Atrix's in frustration because of all the time I've invested in it. I've done what I could and unfortunately got no where.
/rant
bongd said:
Sorry, I'm not helping much? I'm NOT A DEV!!! I have no obligation to help anyone whatsoever. I lack the technical know-how to help anyone. Please don't ****ing test me.
I've begged every Atrix developer here for help - NO ONE helped other than Tenfar. And unfortunately his advice took me in a completely different direction. No one can point a finger at me for not trying my best. I was so desperate that I got another Atrix because mine was dead for over a month before it was revived.
meneomic has been working feverishly to get his Atrix working as he's encountered the same problem. I've sent him my original and damaged PDS, as well as the one which has been corrected. The strings are not in plain text format and when I viewed it in a Hex editor I found nothing useful. That's all I can do. If someone knows how to put the IMEI and other serial numbers into the fixed PDS they can write it to the appropriate block and this problem will be fixed. That's all that needs to be done... but that alludes me.
I realize there are some people who are upset that their Atrix's aren't working after messing around in the recovery menu, but I've done my best. I have literally stayed up for days working continuously on this. My wife nearly smashed both my Atrix's in frustration because of all the time I've invested in it. I've done what I could and unfortunately got no where.
/rant
Click to expand...
Click to collapse
Chill out buddy....
Atrix ~_~
tons of words but nothing useful guys
leaving the good manners debate aside for one moment...
bongd you say you have the 2 file corrupted and corrected, but someone had to flash somehow/somewhere into your phone. who? you or your friend? what did he use to manipulate? can you ask him or not?
second easy group of questions for every dev out there,
-not interested because no reward (for the moment)?
-not interested because impossible?
-not interested because xxxx?
i'm trying to understand please...
msd24200 said:
This forum has young people, even children on it and all tho I hope you guys get this fixed you have to watch the language!
Click to expand...
Click to collapse
KeRmiT80 said:
tons of words but nothing useful guys
leaving the good manners debate aside for one moment...
bongd you say you have the 2 file corrupted and corrected, but someone had to flash somehow/somewhere into your phone. who? you or your friend? what did he use to manipulate? can you ask him or not?
second easy group of questions for every dev out there,
-not interested because no reward (for the moment)?
-not interested because impossible?
-not interested because xxxx?
i'm trying to understand please...
Click to expand...
Click to collapse
I sent my broken file to dev, he fixed it and I flashed it.
There was no exchange of phones, nothing special done, etc. I just used the dd command to write the fixed PDS file. How it was fixed, I an uncertain. I've tried for days and days to no avail. This is what you guys will have to figure out. I've invested too much time and already have a fixed phone which was sold to a friend.
If anything from that phone is needed for whatever reason, it's been sold to a coworker and I can obtain it any time.
ok we are talking now
the question is how did you extract that file?
i don't have adb access because after partitioning my phone failed to boot and i had to flash stock rom. now i cannot pass the motoblursetup (no wifi-no data, i'm stuck there) so cannot enable debugging
KeRmiT80 said:
ok we are talking now
the question is how did you extract that file?
i don't have adb access because after partitioning my phone failed to boot and i had to flash stock rom. now i cannot pass the motoblursetup (no wifi-no data, i'm stuck there) so cannot enable debugging
Click to expand...
Click to collapse
Yes you can. To bypass the motoblur activation type this when you are on the select language screen
Fn,E,Fn,E,B,L,U,R,O,F,F
Hold the Menu button to get the keyboard to pop up. That should work.
This will allow you to get to Settings > Applications and enable USB Debugging. Just make sure not to click on the wrong icon because you can't close a program once it's opened because of the bottom portion of the screen not responding.
I had to battery pull about 500 trillion times doing different things to fix this.
If you write my PDS it will fix the screen, but of course the serials will all be incorrect. And I don't know what this could do so I'd not recommend it.
mmm my phone recognizes the menu button as the bottom of the visible screen so pressing menu results in selecting the emergency call, pressing search button moves me to "next", the home or back button in the middle bottom of the visible screen...
KeRmiT80 said:
mmm my phone recognizes the menu button as the bottom of the visible screen so pressing menu results in selecting the emergency call, pressing search button moves me to "next", the home or back button in the middle bottom of the visible screen...
Click to expand...
Click to collapse
Hold the menu button down until the keyboard pops up and give this a shot.
I'm positive you'll be able to.
Please stop the foul language. Thanks.
according to this thread http://forum.xda-developers.com/showthread.php?p=15026407
you just have to open adb shell and run
Code:
su
dd if=/dev/block/mmcblk0p3 of=/sdcard-ext/pds.img
anyone backed up this partition??
I need it badly
tan G said:
according to this thread http://forum.xda-developers.com/showthread.php?p=15026407
you just have to open adb shell and run
Code:
su
dd if=/dev/block/mmcblk0p3 of=/sdcard-ext/pds.img
anyone backed up this partition??
I need it badly
Click to expand...
Click to collapse
maybe you will find what you are searching about there: http://forum.xda-developers.com/showthread.php?t=1035228&page=4
gitbrew.org is down for now
http://dev.gitbrew.org/~dasmoover/android/atrix/atrix-devkit-fs.tar.gz
do you have this file on your computer?
Hi, hi. I don't recall if this is my first post or not, but my original intent was to post on the developer's forum. I then found out I couldn't. So I'll post here and include a couple of questions/comments I have.
1. Have you noticed that XDA looks like a really happy dude puking the first letter of the alphabet? (That's totally an aside, just getting it out of the way.)
2. Due to some ridiculousness, I now have two Cricket Zios. One of them is working, the other one not. I've had the old one for a few months now and all this time I've been wondering what the heck to do with it. To specify: It went nuts when I tried the update on it (it originally had 1.6) and the corporate store flashed it when I brought it to them. Now when you turn it on, it shows the Android android and tells you to touch it (with the disembodied hand appearing, moving over it, then disappearing, as it's supposed to), but it ignores all input. Have to pull out the battery to shut it off, even. I can then turn it on (so at least I know the End Call button works and I *think* I've tried some combinations that work) and go through the process all over again. The good thing is that I now have a spare battery (go, me). In reading all the threads where developers are unsure of certain things, like whether or not the trackball can light up and whatnot, I'm wondering if it might be worth it for me to take the damn thing apart and take detailed pictures. At the very least, people would be able to see chipsets, individual chips, connections, lights, etc. Does anyone think this would be worth the effort? And, of course, complete loss of the device, though possibly I could use parts in other projects. (The screen, for instance, might be cheap, but it'd be REAL handy used as a miniature second/third monitor like those Liliput monitors.)
3. As a Linux user that doesn't give a damn whether a Windows OS can communicate with my microSD card, is there a reason I should not just format the entire card to something better than fat32?
4. As we all know, the trackball input on the Zio sucks like the Spaceball 1. Could this be improved by replacing the ball itself? It feels cheap anyway and I'm wondering if I could, for instance, take the ball out of a MyTouch 3G and put it in my Zio.
The FCC already has detailed pictures of the zio available, so that would be a waste of a phone.
If your 2nd phone doesnt work, you can always send it to me as a guinea pig phone -- it _really_ would be helpful to have an extra phone to develop with (provided I could get it working -- no guarantees but I'd be willing to try for the following reasons)-- being as any release, mod or anything for that matter I wish to test for you guys has to be done on my main phone, which Im sure any tester could tell you, is a major pain in the ass. lol. So if you really wanna help the cause, that would help me greatly
As for formatting the SDcard -- dont. Your phone saves all data to FAT. The only thing you _may_ wish to do is partition 512Mb off as an ext3 and use link2SD to symlink ur apps to the ext partition.
As for the trackball -- you can try taking it out (if you have the right screwdriver for it), cleaning the contact points, and putting it back together -- that might make it respond better (as I have no problems with my trackball.).
Hope that helps.
~Cheers!
Thank you very much! And I'll totally donate to you the phone (I appreciate a lot of what you've done anyway). Would you mind getting it without the battery?
Don't mind at all -- it'll be plugged in 100% of the time.
Not home atm, but Send me a pm m8.
Sent from my Zio using XDA App
Nice! as an openZio user I thank you
@ SilasMortimer :
Any updates m8? Havent heard from you in a while.
Cheers.
Heya. Sorry I disappeared. I kind of forgot to come back. I think I need to change my settings so I get email notifications.
It'll be sent soon.
Note 9 Exynos Purchased in India.
But my audio has stopped working.
I spent days and nights trying to see if anybody else has faced a similar situation and could not find much info.
XDA gurus my last hope.
Samsung's support is bad. here. The less said the better.
I finally pulled the trigger and did a factory re-set. That too did not help.
Here is a funny thing.
I can shoot pictures but I can't shoot Video.
If I plug my headphones in nothing happens.
The only thing that works is blue tooth headset but not for calls.
If I can figure out what parts need changing I can order them. And try replacing them.
The only Part I could find is this.
https://shopee.com.my/Krcb-98512-Fo...CUD07XjfwNIQZ3inXJADNm-X84Ea9PHVLt7NMgOSL74Fo
Update:
I finally tracked the problem down to the latest update. Soon after the update. Phone started to get hot. And also charging took longer than normal. Audio slowly stoped working.
You can try the following diagnostic tools, if anything to confirm if you have a hardware issue:
1) Dial *#0*# on you dialler and you get Test Mode from where you can test various hardware, including audio
2) In Samsung Members app go to Phone Care and select Interactive Tests. There you can find another set of hardware diagnostics that you may find useful.
Good luck!
Sent from my SM-N960F using Tapatalk
Done sir.
Im pretty sure the Audio IC is blown.
Just need to confirm the part number to order.
kta said:
You can try the following diagnostic tools, if anything to confirm if you have a hardware issue:
1) Dial *#0*# on you dialler and you get Test Mode from where you can test various hardware, including audio
2) In Samsung Members app go to Phone Care and select Interactive Tests. There you can find another set of hardware diagnostics that you may find useful.
Good luck!
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
Just in case somebody else has this problem I am sharing info as I find it.
It would seem the IC needed is MAX98512
And you can download the full Note 9 schematic from my google drive here.
https://drive.google.com/file/d/15MPFlmcnupHqU_4ZAkPOyWo5QeBj9XI-/view?usp=sharing
How do I figure out which IC to change. 98512 or 9896B
Could not find any info online. Other than 98512 is an audio amp and 9896B is audio IC.
Further reading & research seems to link this to the latest Android 10 update.
A lot of other people have faced similar problems on various phones. And 90% of the time the only solution is to have the mainboard replaced.
Just google android 10 updates broke my phone.
So far I have done 3 factory data re-sets. Each time trying something new like this time I did not update from backup. Still, my max98512 seems to be the problem.
I have placed an order for new chips from aliexpress.
Not being able to roll back really suck.
So I got this idea. To figure out if its a software issue or a hardware issue. Need to see if the device drivers are loading or not.
This info can be found by bootin up into recovery mode then view log. Open log last-kmsg
Its a pain to read. And I have not figured out a way to access the data via adb most of the instructions do not work on non rooted phones.
Can anybody with a working note see if the get this message in their log.
star-madera sound: Failed to parse codec DAI for uaif -517
@34%
max98512 6-0039 failed to read [0x0402][-121]
[max98512 _debug] max98512_i2c_probe: failed to read 0x402 [-121]
max98512: probe of 6-0039 failed with error -121
@56%
ALSA DEVICE LIST
no soundcards found
warning unable to open console
I need to know what is the text that shows up on the line after ALSA DEVICE LIST on a working phone.
The TWO ICS handling audio are max98512 and CS47L90 Ignore my earlier comments Indian Note 9 is different audio IC.
By this I can figure out if its a file corruption issue or a hardware failure issue.
RonChinoy said:
So I got this idea. To figure out if its a software issue or a hardware issue. Need to see if the device drivers are loading or not.
This info can be found by bootin up into recovery mode then view log. Open log last-kmsg
Its a pain to read. And I have not figured out a way to access the data via adb most of the instructions do not work on non rooted phones.
Can anybody with a working note see if the get this message in their log.
star-madera sound: Failed to parse codec DAI for uaif -517
@34%
max98512 6-0039 failed to read [0x0402][-121]
[max98512 _debug] max98512_i2c_probe: failed to read 0x402 [-121]
max98512: probe of 6-0039 failed with error -121
@56%
ALSA DEVICE LIST
no soundcards found
warning unable to open console
I need to know what is the text that shows up on the line after ALSA DEVICE LIST on a working phone.
The TWO ICS handling audio are max98512 and CS47L90 Ignore my earlier comments Indian Note 9 is different audio IC.
By this I can figure out if its a file corruption issue or a hardware failure issue.
Click to expand...
Click to collapse
Following here, my father Note 9 same problem and he think it very very bad work by Samsung to put out such devices to break after only 1.5 year of use, His old Nexus 4 is still working and running Android 9 custom ROM thanks to XDA Developer!
Samsung have done something bad, and it is to charge same amount to repair the phone as buying a new phone
So instead of repairing dead audio Note 9 at Samsung its better to do it unofficially I think :silly:
silvaBR said:
Following here, my father Note 9 same problem and he think it very very bad work by Samsung to put out such devices to break after only 1.5 year of use, His old Nexus 4 is still working and running Android 9 custom ROM thanks to XDA Developer!
Samsung have done something bad, and it is to charge same amount to repair the phone as buying a new phone
So instead of repairing dead audio Note 9 at Samsung its better to do it unofficially I think :silly:
Click to expand...
Click to collapse
How much did they quote because one guy was quoted 18,000 I was quoted 26,500,
Yes I agree we save up for years or take out 2-3 year EMI to pay for these phones and then they don't last even 2 years. Samsung can not even explain why it failed. My Water sensor is not tripped. Phone has never been dropped or has a single scratch on it.
Im now using a 5 year old one plus that saw my daughter thru school and collage and its still going strong. Even after multiple drops in water.
Anyway if your interested I am importing all the Audio ICs 10 of each and plan to repair it myself.
The problem with getting outside guys to work on it is they try to reball the existing IC. And if that does not work They put in used parts.
Lets see if this is a s/w issue or a hardware issue if we can get a last_kmesg log file from a working phone we should be good to go.
I found this in the log.
audio_hw_proxy_9810: fast_out-proxy_open_playback_stream: PCM Device is not ready with Sampling_Rate(48000) error(cannot open device '/dev/snd/pcmC0D2p': No such file or directory)!
I really want to go back to Android 9. I don't even mind triping my Knox now.
RonChinoy said:
So I got this idea. To figure out if its a software issue or a hardware issue. Need to see if the device drivers are loading or not.
This info can be found by bootin up into recovery mode then view log. Open log last-kmsg
Its a pain to read. And I have not figured out a way to access the data via adb most of the instructions do not work on non rooted phones.
Can anybody with a working note see if the get this message in their log.
star-madera sound: Failed to parse codec DAI for uaif -517
@34%
max98512 6-0039 failed to read [0x0402][-121]
[max98512 _debug] max98512_i2c_probe: failed to read 0x402 [-121]
max98512: probe of 6-0039 failed with error -121
@56%
ALSA DEVICE LIST
no soundcards found
warning unable to open console
I need to know what is the text that shows up on the line after ALSA DEVICE LIST on a working phone.
The TWO ICS handling audio are max98512 and CS47L90 Ignore my earlier comments Indian Note 9 is different audio IC.
By this I can figure out if its a file corruption issue or a hardware failure issue.
Click to expand...
Click to collapse
hi, please guide me how to read logs. I have note 9 SM-N960F on android Pie Indian firmware.
@34% it is showing some frequency logs and 56% about some gamma values and pannel .
---------- Post added at 11:25 AM ---------- Previous post was at 11:04 AM ----------
here i found this method on samsung website to dump the logs.
SysDump tool:
Launch the Phone app.
Enter *#9900# to launch the SysDump tool.
If the Debug Level is Disabled/LOW, tap to select MID. This restarts the device.
Reproduce the issue that you would like to troubleshoot.
Repeat steps 1 to 2 to launch the SysDump tool.
Tap Run dumpstate/logcat.
Tap Copy to sdcard. This copies a timestamped .log file to the folder /log, which you can access through My Files in your personal space.
You can send the file to Knox Support, using one of these methods:
well found max98512 6-0039
for "ALSA DEVICE LIST" please share pic, it may help to find it.
The way I got to see my last_Kmesg was to go into system recovery i.e. power on with 3 buttons pressed. You get the menu which allows you to re-set the phone or wipe cache partition in that screen there is an option to view logs. From there I read the log.
Its a tiny font and took me 2 hours lol.
But chk this out. Just google Just google android 10 mic fix or android 10 audio problems.
And you will see that a lot of phones have been hit by this.
Not just samsung. But many brands. Some have found solutions some have not.
I think the first step for us is to figure out how to go back to Android 9.
If even after doing that the problem is not resolved then we have to replace the Audio ICs.
I belive the problem was caused by the update. And then it gets bad to the point where it destroys the audio IC.
Pixel phones had a similar problem where the android 10 spoilt sensors at the hardware level.
I was not able to find a directory /log or any files following your steps.
When you google Note 9 audio IC you get this link.
https://www.deviceparts.com/9896b-audio-ic-for-samsung-galaxy-note-9-ori.html
I have placed the order for this along with Max98512 but I can not find any reference to the 9896b IC is any of the Samsung Service manuals.
Lets focus on how to roll back to android 9. Because I think there were some massive changes to how audio is handled in android 10 and that is what spoilt our phones.
Basically due to overheating after the update. It was a crapshoot to see which IC lost contact.
Some people lost on display IC and some on Audio.
My Max98512 IC has arrived.
As to Samsung Claiming offically in writing to me that there were no Audio related problems reported after the update.
Show the lying [email protected]#[email protected]@ this simple google link.
https://www.google.com/search?newwi...TIuMZgBAKABAaoBB2d3cy13aXrAAQE&sclient=psy-ab
Can we use this method to roll back to Android 9 ? I heard rollback is not possible. ?.
Can somebody clarify ?.
https://www.rprna.com/news/how-to-rollback-from-one-ui-2-0-beta-android-10-to-one-ui-1-1-android-9/
it only possible if you have beta version of andriod 10 installed in your phone. if you have updated to stable version of andriod 10 then it is not possible.
Munawar Mehmood said:
it only possible if you have beta version of andriod 10 installed in your phone. if you have updated to stable version of andriod 10 then it is not possible.
Click to expand...
Click to collapse
a. I hope the Deves on XDA can fix this problem and figure out a way for us to roll back.
b. We put enough pressure on Samsung to allow us to roll back. Which I doubt as so many failures suits their agenda of getting you to buy a new phone.
c. We just address the parts that have failed and hope that they last.
==========================
Latest Update:
I was able to get my back cover off. Without cracking the glass or scratching anything it took me an hour but I took it slow on purpose.
Right chuffed with myself. Next step is to chk the speakers with a Multi Meter Then extract the board and inspect it. Water sensors are ok they were not tripped.
The Fingerprint flex was a nightmare to get off in the end it popped off on its own. And the flex nearly tore but did not.
The next step is to try and extract the mainboard and do a physical inspection and look for any damaged parts and to try and locate the Max98512 and the Audio Codec chip.
Im struggling here without the schematics. But my suspicion was right there is heating up all over the board. At the audio and you can see where the solder paste balls have separated from components. I see it near the display chips and near the audio chips.
There are tiny balls of melted solder all over the board.
Everything from the main chips to small components like SMD caps and resistors have over heated and shed these tiny balls of lead all over the board.
Im working without a microscope using a plastic pocket scope we use to read plugs.
Plan is to clean out all these melted balls and then put some flux and re-flow the lead. The Max98512 I will have to lift to see what the heat has done to the pads below.
I can't see any conformal coating on the board. This means if you live in places like India were we see humidity off 80-90% it can wreak havoc with your phone without even tripping the water sensors.
Today's plan is to pull the main board off. Wash it in Iso. Then used compressed air to blow off all the tiny balls of lead. Then fresh flux and lead. And then if I can get it to work. To coat the complete mainboard in a moisture-proof conformal coating.
I can't imagine why they would not coat the boards.
If you open up a Honda ECU after 25 years you will find that the board is still shiny. The lead looks fresh. And the reason is that they use a conformal coating.
And the reason why the audio and display ICs are getting hit the worst is that they have zero heat sinks. Im no expert but why would you run an Audio Amplifier IC with no heat sink. Makes zero sense to me.
============================
If you have an audio problem and are working with the 98512 here are the other parts you will need around it. These are the supporting components.
SCH Part # Part Desc
C8004 2203-009859 / 22000nF,20%,10V,X5R,TP,1608,T (Damaged)
C8002 2203-009858 / 10000nF,20%,10V,X5R,TP,1005,T
L8002 2703-005505 / 1uH,20%,2016,T1,0.043Ohm,42
Top
R8052 2007-007741 / 10KOHM,1%,1/20W,TP,0603
C8006 2203-007796 / 1000NF/1uf,20%,10V,X5R,TP,0603,0.
C8014 2203-008860 / 1000NF,20%,16V,X5R,TP,0603,0.
Btm
C8000 2203-008097 / 100NF/0.1uf ,10%,25V,X5R,TP,0603,0.3
C8002 2203-009859 /22000nF /22uf,20%,10V,X5R,TP,1608,T
C8004*2203-009858 /10000nF / 10uf,20%,10V,X5R,TP,1005,T
C8077 2203-008466 / 0.033nF,5%,16V,C0G,TP,0402,0.
C8003 2203-007621 / 100nF,10%,6.3V,X5R,TP,0402,T0
Thanks guys I solved my problem.
Purchased a Microscope, a soldering station, and a Max98512 AMP IC.
It took me 3 months but I did it.
I did try taking it to a shop. He soldered the IC on so poorly that the phone stopped booting up. And one 10K resistor blew. So decided to do it myself. Samsung Service will not do board level repair. ANd those out there offering this service 90% are uneducated without the right tools for the job.