Database Info

Please help: Windows 7 not recognizing Hero, after 6 months of working fine

Alright this is gonna sound stupid, but I've done my looking around already. It's the same ol' Windows 7 USB issue that many people have had. I plug my phone in and I get an error message regarding it not being recognized etc...
The thing is...I've been using this computer for my dev'ing for like 6 months now without a single issue after the original driver work around. Haven't loaded any roms or anything for a couple months. ****, havent even plugged my phone into my computer at all. Nevertheless, it doesn't work anymore and I've done all the steps to try to fix it. Removed all drivers, downloaded latest driver (64 bit), updated, manually updated, etc... I've pretty much tried everything.
I saw a post regarding a bad power/date cord and that being an issue. My cord is sorta frayed at the usb connector, but seems to work fine so I really don't think that is it.
The only other thing I've seen is editing my registry. It's not that I'm worried about doing it, it just says it's a bit time consuming and I'm not positive it's the answer I'm looking for.
All I want to do is update to stupid CM 6 and sure enough my computer is laughing in my face. So annoying.
Any advice or help is much appreciated.

Try deleting all HTC drivers and reinstall them. I'm running Win7 Home Premium 64-bit and have never had this issue. Hope this helps!
Sent from my CricKet Hero using XDA App

Try other usb port or replace the usb cable
Sent from my HERO200 using XDA App

Why not just dl on your phone and flash via recovery? It's not the fastest option, but it is faster than a pc that won't recognize your hero.
Sent from my CDMA Hero. I got some hot Froyo on Hero action here!

I'd definitely cover the bases with the USB cord, I've had 3 of the stock cords, all have gotten "frayed" at the USB connector and have stopped working for me numerous times.
edIT: Also, try removing other USB devices or switching ports. It may not be receiving enough power.
Shots in the dark, but have proven to be the cause of the problem enough times to warrant an extra 5 minutes troubleshooting.

I had a hassle getting the Hero connected to Windows 7. I did so many things that I can't remember exactly what made it work in the end.
These are among the things I tried:
Switching USB ports. (Plug directly into machine.)
Installing and running sync (HTC provided Outlook sync).
Uninstalling android device (especially the unknowns) and updating drivers from Device Manager.
Googling the web for different versions of the USB driver.
On my system, when I plug the HERO to the computer, it shows up in three places under Device Manager:
Android USB Devices (HTC.Corp 6/10/2009 2.0.7.1 driver)
Disk Drives (microsoft driver)
Portable Devices (microsoft driver)
I hope some of this helps!
thesubliminaljuggalo said:
I'd definitely cover the bases with the USB cord, I've had 3 of the stock cords, all have gotten "frayed" at the USB connector and have stopped working for me numerous times.
edIT: Also, try removing other USB devices or switching ports. It may not be receiving enough power.
Shots in the dark, but have proven to be the cause of the problem enough times to warrant an extra 5 minutes troubleshooting.
Click to expand...
Click to collapse

dynamicpda said:
I had a hassle getting the Hero connected to Windows 7. I did so many things that I can't remember exactly what made it work in the end.
These are among the things I tried:
Switching USB ports. (Plug directly into machine.)
Installing and running sync (HTC provided Outlook sync).
Uninstalling android device and updating drives from Device Manager.
Googling the web for different versions of the USB driver.
Click to expand...
Click to collapse
That reminds me... When I first got Win7, I had trouble getting it to recognize my Hero as well. After some googling, I remember doing something like downloading both the Win7 and the WinVista drivers and replacing some of the Win7 drivers with a few of the WinVista drivers and then rebooting and that got my computer to recognize my Hero.
Not sure if you could find the same thing, but worth a shot.

Try the advice in this thread, the part about installing HTC Sync and getting it working:
http://forum.xda-developers.com/archive/index.php/t-659888.html

I hate to be the bad one but this is in the wrong section..belongs in Q&A section
Sent from my HERO200 using XDA App

Sorry!
I actually thought about that immediately after posting. Was browsing mulitple forums and just slipped my mind. If admin wants to move it, it's not a problem.
I'll investigate the usb ports. Shortly after discovering it was magically not recognizing my phone, a bunch of my usb peripherals stopped working. And upon reboot, actually reinstalled some of them.
I guess it could def still be the cord, too. Although, it charges fine.
And if it comes down to it, I'll just do it ota. Haven't really looked into it, but apparently it's possible. And at this point this usb crap is so annoying, it sounds like a great idea.
I've removed all drivers, all anything htc, and still can't even install the driver. Even if I point directly to it via "have disk", it gives some error about having the correct driver. I've downloaded mulitple drivers from multiple places, as well.
Thanks for the advice. I'll try a few more things and be in touch.

If you can, try it on another computer. It could definitely be the USB cable if it has been working and now isn't. It can still charge but not have data work because they use different parts of the cable

[Q] Install stock kernel without any method which uses charging port?

Greetings to all of you. I hope you be very patient with my poor english (I write and speak spanish) and this long post (please, read all of this) and please help me with this question, my first question here.
I am a XDA user a time ago, 2 years or least; I have flashed the kernel or the ROM of a lot of Android devices (+10, tablets and phones) using your knowledge posted on this wonderful community and I talk about this to prove that I'm not a totally noob and I never had a problem like this before; sadly, this happens with my own phone: SGH-T959V.
The charging port stopped working as data transfer port and just worked as charging port, this occurred just 2 months ago; but it was not relevant for me because I did not use the function in a long time, I used to charge my phone when it requires energy and nothing else. But I read about a CyanogenMod update (unofficial) for my phone and decided try it. Then I download it, install it via CWM and it worked successfully; I had a beauty JB 4.2 running on my 3 years old phone. I noted that there was a trouble with the RAM size, the new CM ROM just recognizes 346 MB of the RAM and the last ROM (CM 9) could recognize the 512 MB. I looked for a post here which talked about my problem and I found it, they suggest to install another kernel and I proceeded to do it. It was the 3 am or close, I was tired and here comes the first big mistake: I download and install a wrong kernel, a kernel for the T959, not the T959V. I cannot remember the name of the wrong kernel (because I deleted it from my PC) but since I installed it, the phone is always on recovery mode and the title of menu is: “Devil touch recovery v6.0.1.9”.
I tried to install the last kernel which worked fine (hefe-kernel-v0.8.1) and I always get the following messages: (as with any other kernel or ROM)
E:Can’t mount /cache/recovery/last_log
E:Can’t open /cache/recovery/last_log
E:failed to find “cache” partition to mount at “/cache”
Status 4 error and Status 7 error appeared too. (I solved the status 7 error modifying the Meta.inf data into the zip)
I formatted the SD card, put the kernel there and tried again to install it, but I have no success. I fixed permissions, tried to wipe data, wipe cache, but the same messages appeared. I look for a solution on some threads here and read about the cache format, they talk about ext3 and ext4 but I cannot find the way to reformat the phone with a kernel which has the right format to then, finally, install the right kernel for the phone. Well, at this point, I thought about all the mess up and then I conclude: Why the hell I don’t just recover the phone via download mode and Odin? If you remember, the charging port just worked for charging, not for data transfer or any other usb function; yep, I got it on that dawn: I was screwed.
Next morning, I carried the phone to the technical service (here in Cali, Colombia. It is not from Samsung) looking for a new charging port, the technician told me that he had the right repairing part; he said that was the same of the SGS3 (IFC700). I returned the next day for my phone and I found a major disaster: the “technician” did not apply properly the heat gun and all the electric conducting lines (the 7) were pasted at the pins of the old and damaged port.
I searched for another technician and thanks God could find one that gave me hope, although somewhat unreal, for my bad luck. He suggested me that if we could detect the origin of the electric conducting lines on the mainboard (unit U701, specifically) we could make a bridge between them and the pins of the new charging port; the problem is that I surf and surf through all internet and found only this pdf: On bit ly :/1dS7M61 (I cannot post links yet.)
But here, they do not give information about the PCB and the specific connections for pins, so, here comes my first question:
Do you know the specific origin of the seven electric conducting lines of the charging port? And, if you do, do you know if possible make a bridge with them?
In case this does not work, do you know how to recover the phone to the original kernel and ROM (as Odin does) but without using the usb cable, just the SD card?
I will stay watchful. Thank you for your time, your patience and your help.

Most of the lines for the pins are on the surface layer and go right up to the connector so unless you have ripped them all the way off you should be able to tell what goes where. The first and last connections are GND and there's a big area of gnd on either side of the connector. There are 2 other lines that are VCC I can't remember which lines now from memory but it should be fairly obvious to a technician. The last 3 are the tougher ones. TX and RX each have a tiny little line on the surface layer which leads up to the corresponding pin. The last one is the host mode pin which actually comes out from inside the board into the pin itself. If you look really close it looks like a little dot where the pin would sit. That last one I found nearly impossible to repair, but the other lines you can peel off the coating and solder a really small wire on top of them to complete the connection. All the more important lines are visible so unless somebody really jacked up your phone a decent tech should be able to repair it mostly.
If this doesn't work you're screwed. And even if you can repair 6 of the 7 lines the one that tells the phone to be in dock or download mode is necessary if you can't get into download mode with the volume buttons.

TwitchyEye said:
Most of the lines for the pins are on the surface layer and go right up to the connector so unless you have ripped them all the way off you should be able to tell what goes where. The first and last connections are GND and there's a big area of gnd on either side of the connector. There are 2 other lines that are VCC I can't remember which lines now from memory but it should be fairly obvious to a technician. The last 3 are the tougher ones. TX and RX each have a tiny little line on the surface layer which leads up to the corresponding pin. The last one is the host mode pin which actually comes out from inside the board into the pin itself. If you look really close it looks like a little dot where the pin would sit. That last one I found nearly impossible to repair, but the other lines you can peel off the coating and solder a really small wire on top of them to complete the connection. All the more important lines are visible so unless somebody really jacked up your phone a decent tech should be able to repair it mostly.
If this doesn't work you're screwed. And even if you can repair 6 of the 7 lines the one that tells the phone to be in dock or download mode is necessary if you can't get into download mode with the volume buttons.
Click to expand...
Click to collapse
Thanks for the fast answer! I will show this to the techinician and I hope that he can repair it; although I really think it is almost impossible, the lines are all deeply ripped, just the third and fifth line survived the attack.
Again, I want to answer just one more time about fixing the problem of installing kernels or ROMs via recovery mode (please read again the first post): "E:Can’t mount /cache/recovery/last_log
E:Can’t open /cache/recovery/last_log
E:failed to find “cache” partition to mount at “/cache”
Status 4 error and Status 7 error appeared too. (I solved the status 7 error modifying the Meta.inf data into the zip)"
Do you know how to fix this? Or install a stock kernel without those problems?
Thank you!
PD: I will post the answer of the technician to this.

Yeah the kernel you flashed screwed up your phone and the only way to recover is through heimdall or Odin which you'll need usb for.

Thank you again for your attention. Unfortunately the technician could not find the download mode pin, so it's official: my phone is a paperweight. I thank you again for your help and interest, have a good weekend.

First of all, fo ur problem, I believe that the only way u can save ur phone is using heimdall to flash another mtd kernel (if u can luckily boot into download mode) but sad that ur usb port was doom (correct me if I am wrong).
In addition, why on new kernel the phone just shows 384MB of RAM? Just fyi, new aries kernels changed the way counting RAM as they don't count the reserved RAM that the init system took but just the remain. As if u look into the kernel, there is somewhere says that RAM = total subtract reserved (in a specific calculation not words). That's why u saw 384MB even in fact we have 512MB. N why it is 384 but not 400 or 450, idk lol. So if anyone is curious bout this can have this rep as an answer as well
Sent from my SGH-T959V using Tapatalk 2

You don't need the download pin if you can get into download mode by holding the volume buttons. If you need a usb jig to get into download mode then you're out of luck. Otherwise your phone will function normally except when you put it in a dock or try to use otg which as far as I know we don't have support for anyway.

[Q] phone not being recognized at ALL as usb? (cm11)

hi..
after installing cm11 it would appear my phone is not being recognized as usb device at all? neither as usb mass storage device or as mtp , i does charge the phone, but that's it.
i've enabled MTP in usb comptuer connection, and tried to connect it to 2 different computers.

Hmmm. I haven't seen an answer to this question posted yet. Emaayan, did you ever get a resolution to this? I actually have run into this twice in the past, and the answer is to shut the phone down, and do a battery pull to reset the hardware completely. Had me scratching my head for months, and even had me develop a way to do a full unroot and return to stock without ever touching USB or terminal, until I took the battery out of my fiancee's phone since we were planning on returning it, and using it on what would've been her backup phone. When I returned the battery to it, the USB worked again. It's not a CM issue, or a software issue at all. It's definitely a Samsung not-initializing things properly issue. I've seen it happen on stock, I've seen it happen in the old 4.3.1 FatToads, and the 4.4.X FatToads.

Let me know if the above works (battery pull).
I had this issue too, didn't realize it until I tried updating different roms...
I put on Carbon after OmniRom ... OmniRom was overheating my phone and battery and it was at that time I actually pulled it apart and wrapped it in a gel ice pack to cool it down.
I don't recall if Carbon had worked, but I'm back on CM11 now and am getting USB working.
I also updated to the latest CWM per OmniRom thread in development forum.
I trust Magamo, though, in providing the right diagnosis and solution.

mod please delete

REV3NT3CH said:
i believe OmniRom caused my phone to brick...flashed it to see the issue people were having to help with a fix....apparently lbcoder is breaking stuff again lol...when i get either a new relay somehow or fix mine..i may look in their code to see what it is...im almost assuring its how MTP is not being handled correctly.... i respect @Magamo and most the other devs.. but all i can do is suggest a fix and get disrespected by lbcoder
Edit: like this for example https://github.com/TeamApexQ/androi...mmit/b9d389cca9f241d778f1d8206195e16dfcb3dee8
Click to expand...
Click to collapse
OmniRom was not the cause of your bricking, I hate to break it to you. The commit you just linked actually has very little to do with the kernel. It was an update to fstab to match a change in paths. There was no driver functionality change in anything that was dependant upon. If you respect me, I would appreciate it if you were to stop spreading FUD about us, and my work. I'm starting to become personally insulted here. Bricks more often happen due to faulty hardware. No properly booting kernel would have been the cause of what happened to you. I assure you, our kernel is working properly.
This is also completely off topic to the question asked. As stated, I've personally seen this happen on several images, Stock included. This particular issue is a Samsung hardware initialisation issue, and is resolved by a battery pull.
Since it is off topic for this question, I will not ask here what you feel is wrong with our MTP code. We can start another thread, and stop hijacking this one. Better yet, as always, the best place to discuss this with us would be on IRC.

Surprisingly, pulling the battery fixed the problem!
After spending the last few days without my phone being recognized by multiple computers and considering a factory reset on a Samsung Galaxy Relay, I came across the post here mentioning that pulling the battery worked to fix the problem with phones not being recognized through USB.
I can vouch that pulling the battery does fix the problem with devices not being recognized.
Perhaps these devices should have a more convenient way to pull the battery if doing so makes them work properly.

Autolooper said:
After spending the last few days without my phone being recognized by multiple computers and considering a factory reset on a Samsung Galaxy Relay, I came across the post here mentioning that pulling the battery worked to fix the problem with phones not being recognized through USB.
I can vouch that pulling the battery does fix the problem with devices not being recognized.
Perhaps these devices should have a more convenient way to pull the battery if doing so makes them work properly.
Click to expand...
Click to collapse
It's not working for me. I have the MTP available, but not simple USB Mass Storage with CM11. Any other ideas?

xob3444 said:
It's not working for me. I have the MTP available, but not simple USB Mass Storage with CM11. Any other ideas?
Click to expand...
Click to collapse
Android 4.0+ no longer supports USB Mass Storage out of the box for the internal storage, and neither do any of the custom images that I can think of. MTP is the answer here. The fact that you are getting MTP means that the device is talking over USB, which means that you are not suffering from the problem described in this thread.

USB connection issues

Hi all,
I've been running my Xtrons unit for a while now, with Malay v2 Android 8 for a few months. Everything used to work great, but since last week (without changing anything) my USB connection works crappy. My USB with music and DAB are connected directly through the two USB connections at the rear with an extension. They both stopped working suddenly, but the USB stick I have connected still has its power LED on. So there is power to it.
A few reboots later it worked again, but the next day it was gone again. I then checked the MCU settings and disabled PVR USB (I believe), and it worked again after a reboot. When it works, it works great by the way. The next day it still worked, so I was thinking I solved it.
However, the same afternoon same issue... Few minutes later (without a reboot) it worked again... Tried to disconnect everything and plug in either the DAB or the USB stick, but same result.
I strongly think its a software issue since I can 'solve' it with rebooting it sometimes. Anyone ever had something like this?

No one? Same problem today. Started my car and no USB whatsoever. 10 minutes later without doing anything everything worked fine for the remaining part of my journey to work.

Is it a "XRC" units (MTCE_XRC_...) i think were having issues woth the usb controller.
https://forum.xda-developers.com/an...icane-px5-oreo-wifi-bluetooth-waking-t3852206

tw39515 said:
Is it a "XRC" units (MTCE_XRC_...) i think were having issues woth the usb controller.
https://forum.xda-developers.com/an...icane-px5-oreo-wifi-bluetooth-waking-t3852206
Click to expand...
Click to collapse
It's a GS unit. Not sure if they're the same perhaps. Weird that it suddenly appeared.

I have the same issue.
when I connect USB/64GB and 3G dongle USB constantly reconnects. I'm on dasaita px5/4GB

1st up and not to be one of the thread patrol guys we seem to have running round the Android auto forums..
But general help questions like this should be in the QA area..
Maybe mods should shift it..
But to answer the question with a bit of experience lately..
In my USB thread on SSD's and the USB M2 casing I have used.. I found a similar thing going on with the USB ports..
As reported there.. plug in the M2 SSD (which of course is plugged into the controller in the housing)
And it's seemily pulling too much power as it affected the ability for a GPS lock..
Unplug it and GPS works..
My thinking there is as said..to me it is like it is either a software glitch and or power interruption. I am leaning more towards the power theory.
There is a bit of reading around on USB port burn out on some of the boards.. so it's almost like a case of being careful on actually plugging in to much to ...
In my case 3 USB ports..
This does bring up another point that has been bothering me the last few days as I hunt for a better storage situation..
My reading on 128g USBs via the comments section is showing up extremely hot usb's.. thus it's something to think about . As in these things in a glove compartment could end up being a fire hazard..
And or even in the case here, causing sort of interference back through the system..
Some of the more electronically minded techies with the right testing equipment would be able to have more input.. and I can bet you that the engineers in the factories making these things are not talking or reporting back to their bosses anything along these lines.. as they will be all about protecting thier jobs.. and no one is going to want to put thier hand up and say.. hey..I think we have a problem..

tw39515 said:
Is it a "XRC" units (MTCE_XRC_...) i think were having issues woth the usb controller.
https://forum.xda-developers.com/an...icane-px5-oreo-wifi-bluetooth-waking-t3852206
Click to expand...
Click to collapse
Tried the 'fix' from here, which should restart the usb hub, but all it does it restart the wifi, as can be seen in the code. The problem is that USB worked fine for me now twice while testing. So couldn't test if the 'fix' actually does help.
I can't seem to get Tasker to run with root... It says that my device is not rooted, although other apps give the SuperSU pop-up that ask for root access...

Tried the .sh file in the other tried, and an app to reset the USB hub, but no luck. Rebooting a few minutes later worked.

I have the same issue. I figured out that it is temperature related. When the outside temperature is ABOVE 11-12°C the USB works fine. When its colder It constantly reconnect every 20(?) Seconds. When the Car Heat Up enough the Error is gone again.

Still no solution for my issue. Also have it in the nice (12-14 degrees C) weather in the past few days. What else can I try before I bin it and go to another HU?
edit: Oh, and how can I get this to hardware?

Bose321 said:
Still no solution for my issue. Also have it in the nice (12-14 degrees C) weather in the past few days. What else can I try before I bin it and go to another HU?
edit: Oh, and how can I get this to hardware?
Click to expand...
Click to collapse
We need to replace the USB Controller Chip GL850 to GL852. You can get the Chip in AliExpress.
€ 3,47 11%OFF | 5 stücke GL852 GL852G USB hauptsteuerspan SSOP-28 SMD
https://s.click.aliexpress.com/e/cPrldP21

EDGN said:
We need to replace the USB Controller Chip GL850 to GL852. You can get the Chip in AliExpress.
€ 3,47 11%OFF | 5 stücke GL852 GL852G USB hauptsteuerspan SSOP-28 SMD
https://s.click.aliexpress.com/e/cPrldP21
Click to expand...
Click to collapse
Yeah I've seen that, but it's too small for me to try. I'm not that great in soldering, so don't want to ruin my unit haha.

Install the Hal9k Rom, where you can restart the internal USB hub on startup and then USB devices will work again.

Ati_gangster said:
Install the Hal9k Rom, where you can restart the internal USB hub on startup and then USB devices will work again.
Click to expand...
Click to collapse
Already tried that, and I have the Malaysk ROM which also has the 'fix'. Also tried to run it manually. Also have a USB Controller app that can do this.
Worked a few times but doesn't anymore now.

check this thread
https://forum.xda-developers.com/an...x5-mcte-low-temperature-fix-wifi-usb-t3868388
there are at least two solutions. one is mentioned before - to swap the GL850 chip. second is not checked yet.

mahtew said:
check this thread
https://forum.xda-developers.com/an...x5-mcte-low-temperature-fix-wifi-usb-t3868388
there are at least two solutions. one is mentioned before - to swap the GL850 chip. second is not checked yet.
Click to expand...
Click to collapse
Already tried the second 'solution'. Didn't work for me.
My best bet now is the new chip. I've ordered 5 of them, gonna check if I can solder it, or let it be soldered once it's arrived.

Bose321 said:
Already tried the second 'solution'. Didn't work for me.
My best bet now is the new chip. I've ordered 5 of them, gonna check if I can solder it, or let it be soldered once it's arrived.
Click to expand...
Click to collapse
It's good feedback (that second method doesn't work ). also ordered three chips and going for swap.
i have other issues though. when using USB dongle or copying files from usb to internal mem my screen is blinking (like darker-brighter in fast pace).
i hope that swap will help with this issue also

mahtew said:
It's good feedback (that second method doesn't work ). also ordered three chips and going for swap.
i have other issues though. when using USB dongle or copying files from usb to internal mem my screen is blinking (like darker-brighter in fast pace).
i hope that swap will help with this issue also
Click to expand...
Click to collapse
Sounds weird as well! Good luck.

My unit disconnect USB with vibrations on the road. I also try replace USB chip.

karolp1993 said:
My unit disconnect USB with vibrations on the road. I also try replace USB chip.
Click to expand...
Click to collapse
I think you need to see very closely in where the usb cable is welded in the morherboard and try to find cold weldings. I had same problems with my pumpkin and when i completely dissasemble it i saw a ton of cold welding and i reweld everything and its rock solid now.

PX5 cannot boot anymore (SOLVED)

UPDATE 24.11.20
I have recovered my HU by reading the whole night on this forum and TO THE AMAZING work of several people here.. especially GREAT GREAT thanks to marchnz and to scorillo_ro I build myself the USB cable and followed all the instructions I could find. With some moments of headache .. finally I flashed a new ROM and it booted up!!!
I have to go down on my knees to you guys for the super AMAZING work you have done. Wihtout you I woulld be now 180€ poorer. (new HU).
___________________________
When booting I get this errors...
I got a MTCE_LM PX5 unit (8Core A53 CPU 2GB RAM)
It is always very difficult to enter Recovery so I tried several times but it doesnt work. Either I just didnt mage it right or the recovery is broken.
In the pictures you can see 2 different messages. I have the feeling the long message version is when it normally tries to boot into the OS but fails.
The short message looks like when I managed to get into recovery reboot but it fails too.
Or its the same message .. it just blinks up for 10ms or something and dissapears and then blinks back after 5 secods ... I had to take like 20 photos to catch it. So maybe its the same actually.
Anyone has a clue what I can do from now on?

Great to hear another success story.
It took alot of effort to develop the method, for which was made possible by a member posting the schematic diagram to the forums for the benefit of all. Your post helps other too, so thanks!

Thanks again for the endless hours you put into developing the esiest method possible (for this SOM).
I am REALLY pissed at the Chinese somehow. They develop great stuff sometimes but fail to think over the edge. It is so easy to destroy your OS by small or stupid mistakes. And then there is no OTG to easily reflash the rom. I mean the hardware supports it. They could (and luckily and finally some new models support OTG on at least one USB port right away). But why was this not implemented right from the first designs for the headunits is puzzling me.
I would love to help anyone who needs help. But I have the PX5 HCT V4 SOM so you people wrote exactly how to do it for this specific SOM... I am not sure I can add anything of what wasnt said already.
I just had 2 main issues. The USB cable was found but not recognized at first.
So what I figured out was that you should not use more than 2 resistors to make the voltage division (thats what I did first) and I just had 2.8V on the division. I did it fast and not clean, means. No really good soldering connections.
Then I rebuild the whole thing used a good cable just 2 resistors (2kOhm and 3.3kOhm) and I soldered everything as clean and as compact as possible with least distanced to each part. So it gave me 3.1V on the division.
This was recognized immediately. Ahh.. and it helps too if you can use some contact spray for electronic parts. Because the pins sometimes do not sit well inside the SOM board.
Then the flashing of the ROM didnt want to work. It gave me an error on downloading the firmware.
Solution was to simply erease the flash memory.
But everyone who goes to your thread and reads at least the first 20 pages gets rather the clue on the minor issues. But its actually all written in there... just need to read it