yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] VlaJko79:
MICROP RIP problem

Ok...listen guys...whoever wanna put 600e brick for MICROP ina fridge I'm ok with that:eek:...

But b4 that u have to know that HD has NON VOLATILE chips that you cant "reset"

(ROM&bootloader) with cold, except RAM memory chips who dont have anything to do wth da problem (passed all tests fine). After 7 months of research me personally bet on some sort of bootloader problem thats crashing

the phone but who knows..everything works fine for some time and when the screen goes off it shows some problems when rebooted and connected to MTTY in bootloader mode (look@ some of mine previous posts - "task 2 a" "boot" if I recall correctly)..

So...beware of extreme cold, watch for condensation of moisture inside the phone, and good luck. And please do share the results,

Cheers!
[Touch Diamond, MDA Compact IV ROM Development] turbogade:
solved

u just need a screwdriver,scissor and a thin card board (cigarette box like card board)

1. open your diamond

2. check whether your LCM and NAVI board is connected with the main board.

3. if those two items did not connect, u need to connect it.

to connect those two items, it can be a bit difficult. u need to pull out the ribbon first to see it clearly below.

4. here's the scissor and card board will come useful. Cut the card board as the exact size of the LCM and NAVI socket and place it below the socket. This is to make the LCM and NAVI socket a bit higher so that u can easily connect it with the main board.

5. make sure all flex cable connected in order to use wifi and gps.

6. assemble back ur housing..and ure done.

as far as i know, this problem mainly bcz u dropped ur diamond.

if this method cant fix the problem, then u should send it to htc service center. (recommended for those who still have warranty)

here is the website where u can find htc diamond service manual as ur guide

http://www.mikechannon.net/page1.htm

hope this will help u guys..:)
[Touch Diamond, MDA Compact IV ROM Development] Franceschiello:
Hi, in this link http://www.pdacenter.ru/razborka/razbor-htc-touch-diamond/ are all image of disassembly, can you indicate on pictures the LCM and NAVI connection to do?

Thx.
[Touch Diamond, MDA Compact IV ROM Development] turbogade:
LCM and NAVI sockets

on the image no 22, the top socket is for the NAVI and below the NAVI is LCM socket. Make sure both sockets are connected tightly with the main board.

By the way, the main board is attached with the flex cable and u will have to connect the ribbon again after u connected LCM and NAVI.
[Touch Diamond, MDA Compact IV ROM Development] turbogade:
LCM and NAVI sockets

place the card board below the sockets in order to level up it a bit so that u can easily connect with the main board...
[Touch Diamond, MDA Compact IV ROM Development] littlej:
hy, today this problem apeared to me also, used the phone fine, did a reset, and when it started micro-p error but all was ok, screen was bright and so on, so i did a reset, and micro-p error again but screen was verry dark, what i did was uncheck auto-adjust blacklight, and reseted again, voila micro-p error was gone... u might give it a try maybe works for u guys also

edit well it seems wireles aint turning on... so problem aint fixed...
[Touch Diamond, MDA Compact IV ROM Development] juju35:
why is it an hardware issue?

Backlight work when I start my diamond. The backlight go out when the phone goes in inactive mode and there is nothing to do to make the backlight working again.

A mastering light soft shouldn't work? (or new key in register...).

I can't put my phone to the after-sales service anymore

what could we do to get backlight again?
[Touch Diamond, MDA Compact IV ROM Development] lecosmique:
I just had this problem today. For the past couple of weeks I have had weird problems with my TP, but never seen this error.

Mostly I have seen that the keyboard does not work. Opening the keyboard flips the screen, but does not work. Sometimes it backlights for the the first three seconds or so, sometimes not. I found resetting the device, remove/replace battery would sometimes solve this. Sometimes not.

I also experience the "illuminated black screen" syndrome. The screen is backlit, but nothing on there, just black. Sometimes booting fixes this, sometimes not. I believe sometimes it just boots with no screen function at all.

It's been quite frustrating. Not sure if this is a hardware of software problem. I have not used any cooked roms and my device is not unlocked.
[Touch Diamond, MDA Compact IV ROM Development] minoo66:
The manipulation from turbograde worked very fine for me, my problem was that the backlight from my diamond was off, and i couldnt see anything frommy screen, after 20min to open my phone, reconnect the LCM and NAVI socket, my phone is working correctly now! TY for the solution!
[Touch Diamond, MDA Compact IV ROM Development] littlej:
can u post a quick how-to or something on how to open and reconect navi and other stuf? :D thanks
[Touch Diamond, MDA Compact IV ROM Development] juju35:
You should Follow this link.

you can traduce the notes with google.

It's pretty easy to reconnect the sockets but it didn't work for me.

Good Luck
[Touch Diamond, MDA Compact IV ROM Development] MattJ1989:
So... how do you all think the Navi and LCM are getting loose?

My Touch HD is doing this also (after being in repair!)
[Touch Diamond, MDA Compact IV ROM Development] kaotickid:
Same thing is happening to my HTC Touch Pro from Telus . Might seem obvious , but has anyone tried a hard reset ?
[Touch Diamond, MDA Compact IV ROM Development] Turtl3sh3ll:
im having the same error with my touch pro but will try all of the afformentioned teqniques. i do know that it is not the ribbon cables, and it is not rom related. the error survived 3 stock rom flashes. whats strange is it goes away for a few hours then comes back suddenly.

whats strange for me is about 2 weeks ago (before i screwed with the new 6.5.1 rom) it did it so i put it on the charger overnight and it worked in the morning but it was dim so i turned off the auto adjust on the backlight (never saw the microp error)

that fixed it for about 2 weeks

the microp error didnt show up till after i installed nuekb (http://nuerom.com/BlogEngine/page/nueKBLight.aspx) when i saw the error it didnt bother anything but 2 days later no screen!! now im here trying to figure it out.....
[Touch Diamond, MDA Compact IV ROM Development] Marne Jr:
Hi ... I have a blackstone (touch hd) and have the same problem ... this problem starts after I droped my phone of about 1,5 meter of height ... I tryed 9 ROM (2 original) and many HSPL but nothing solving it ... I noticed that some day after another drop .. it stop to happen (this ****ing Microp messag) and for 1 month it not happened until my phone falls again and the nightmare returns ... I tryed throw it to the floor again but it didn´t got better ... I learned that this problem is caused by a miss contact between parts of the hardware (i can´t specify ...) the best is to uy another ... or hope for a saving fall to the floor ...

Bye, all !!!
[Touch Diamond, MDA Compact IV ROM Development] Podge:
Hi all,

I had the same problem last year with my stock WWE Diamond. It failed within a few days after purchase.

The problem lies in the lightsensor and cannot be caused nor solved by a ROM update.

I had the phone sent back to the vendor, they sent it to a HTC repair centre. Eventually HTC sent me a brand new phone, apparently the problem is not fixable.

So, bring your faulty devices back to the vendor and have it replaced.

Podge.
[Touch Diamond, MDA Compact IV ROM Development] djomla:
Hello

Has anyone solved the HTC Touch HD error Microp firmware?:confused:
[Touch Diamond, MDA Compact IV ROM Development] gregianos:
Microp Error

Hi,

I had this error about a month and a half ago, but i had just got my new TD2 so i just left it, however i have now managed to smash the screen on the TD2 by getting it trapped in my car door, so i wish to sort this phone out. I'm getting the Microp error as seen below from a screen shot in MyMobile:

The screen stays black all the time, and no lights at all show.

What i've done so far:

This phone has never been flashed beyond the manufacturers ROMs so i downloaded the latest ROM from O2 and flashed it to no avail.

I have dismantled the phone as per instructions here up to step 21. The picture indicating 'disconnect navigation fees from motherboard' seemed to be already disconnected on mine and i am having great trouble reconnecting to to get it back working.

Could this be the problem? Might the person who created the guide have mixed up the nav chip and the LED chip and the LCD screen has simply slipped out of the mobo and won't go back in? I've tried several times, but due to the awkwardness of the fitting, i can't get that back into the mobo, however the 1 indicated that it is the 'cable screen communicator' slips in and out quite easily.

Any thoughts would be appreciated!

Update: I read through the thread again and noted turbogade's comments about the piece of card under the chips, gave that a whirl and that worked a treat! My Diamond is back up and running! I just needed to ensure the LCM and NAVI board connectors were connected. There is a disassembly/assembly instructions here which people may find useful
[Touch Diamond, MDA Compact IV ROM Development] dtrtz:
It really worked. Got the same problem here - one day the HTC Diamond stoped displaying things ... Reconected the cables as desribed and it's FIXED :) Thanks for the research
[Touch Diamond, MDA Compact IV ROM Development] Idimmu:
Touch Pro2

I have the same error. Really don't want to send it in!
[Touch Diamond, MDA Compact IV ROM Development] tonyfung820:
Ok, my Diamond had the same problem since yesterday. After reading some posts here. I decided to open up my Diamond myself and tried to figure it out.

Nothing special but just try to reconnect those two connectors which are underneath the motherboard. My Diamond back to life again with backlight when booting up and the MicroP message gone.

Try if you have confidence to do so. Hope it helps!
[Touch Diamond, MDA Compact IV ROM Development] chiloco:
Glad to hear people get it to work in Diamond..

My Touch HD aka Blackstone is facing the same problem for the past 1 week due to water damage.. The phone is still working but the screen is blank. In my warranty card say that it will not cover water damage so I'm contemplating whether to open up my HD or not. I had Miri rom on it but I've reflashed with Stock ROM (very difficult to align the screen with a blank screen) manage to do it using mDesktop while trying my best to figure out which point to tap on the blank screen.

Eventhough a lot of people say that better to change the Mobo, i will try other measure first.

BTW.. Nexus One is really tempting. hopefully I can fix this and trade it in with a Nexus One or maybe Desire... arghhhhh
[Touch Diamond, MDA Compact IV ROM Development] ngc3773:
I also had the same problem...

I reconnected the NAVI and LCM as shown in the thread, didn't work...

but here was my mistake, the card board i cut was too large... so carefull, cut it the SAME SIZE AS YOUR SOCKET !!!! (so it lift up only the soket to have a proper connection again)

I cut it again, right size this time, and here it was, my diamond, just as good as new!!!
[Touch Diamond, MDA Compact IV ROM Development] Gezzas:
did anyone solve this?
[Touch Diamond, MDA Compact IV ROM Development] VlaJko79:
If ure reffering to Diamond, try that trick with reconnecting contacts on the mobo...if u have Touch HD aka Blackstone, so far, only changing the mobo works.
[Touch Diamond, MDA Compact IV ROM Development] XL3N7:
On a diamond that wouldn't work with reconnecting the flex cables, I replaced the keypad with it's pcb and flex cable and it worked.

Something like this

http://cgi.ebay.co.uk/Keypad-keboar...ries_MobilePhoneBatteries?hash=item2a05f095de
[Touch Diamond, MDA Compact IV ROM Development] ramass:
i solved this problem

Hi.

sorry for my english.

i have a htc touch hd (blackstone) and i start see that message and that prblems (no backlight, take a lote of time to start up), so i do a cople of tests and, luckly or not, i solve the problem and put mt PDA work fine.

so, its what i did:

first i noticed if i put the phone on the freeze and wait half hour the phone works fine and after that and turn off or do a soft reset the problems shows again. so the first thing i did was put the phone on the freeze in a plastic bag and wait a little bit.

the second step was startup the phone and now i had backlight and all things worked fine. so when enter to wm i run a game teeter cause the one of all things stop work was g-sense and leave the phone in the game and plug to my USB cable to charge battery and wait more half hour.

next step was update firmware of the phone. i put the SSPL-Manual-TouchHD file in the phone and run it. the phone was open to received the upgrade, so i run HSPLWrapper_Blackstone_156OliNex. finish whitout problems.

then the phone startup automatically and the backlight gone again......

the next step was put a newer version of wm. my choise was Energy.BLACKSTONE.23559.Sense2.5.MaxManila.Apr.17 cause my phone is a cdma and i enjoy the screen shots.

so i wait until windows mobile device center connect to the phone and run it. finish again without problems and the device reboot. without backlight....

so i wait until listen the phone ring, that means the first steps of the new firmware was finished. my WMDC (windows mobile device center) connect to the phone and i can run my mobiler to see what the was doing. complete all steps (align the screen, accept the terms and conditions.....) without back light.

after that i put in the freeze again, wait more half hour and torn on. did a hard reset (in my mobile is volume up+volume down+reset) and complete the steps.

when finish the phone reboot with backlight complete the first steps again (align the screen..........) and never show the problems again.

u can say was luckly and the problem was not solve, was adjourned.....

but i say loudly work with my phone. looks fine now and stable.

if you have the same problem try this. u lost anithing.

the soft i mention before was in this forum. i cant put the links cause i m a new member and have restrictions. (for moderators of this forum: i'm not a SPAM)

i hope this can help least one guy.
[Touch Diamond, MDA Compact IV ROM Development] siddharthsai:
@ above

http://www.xda-developers.com/windows-mobile/infamous-microp-screen-error-for-htc-diamond-fixed/
[Touch Diamond, MDA Compact IV ROM Development] aidebe1:
Did you try flashing it with the original stock Rom ...you can download it from the HTC site...
[Touch Diamond, MDA Compact IV ROM Development] XL3N7:
Your method was mentioned in this thread months ago m8, here but it doesn't work for all people. I personally disassembled and reassembled a friend's diamond with no luck. I tried putting small screwdrivers under the flex cables and pushing from above with no result. Eventually I bought a donor diamond with a broken screen and heavily damaged body. I transplanted everything and isolated the problem on the smaller PCB on under the keypad. You point to the motherboard PCB which was fine in my case. After that, the phone was fine.

Also, knowing what the problem was, I looked in here for a dead/bricked diamond to get the keypad pcb with no luck. You can check my posts if you wish as I made a WTB thread in the marketplace forum.

Eventually I bought off ebay a new white housing, a screen along it's digitizer and a keypad like the one I linked above and now I have a fully working diamond with no problems in the past few months.

Hope this helps other people who can't fix their phones with the flex reattachment method. I guess the problem may be the flex cable that connects the keypad pcb (probably the dreaded microprocessor?) to the mainboard pcb.
[Touch Diamond, MDA Compact IV ROM Development] ahmgsk:
best way to fix it

1 remove battery panel

2 remove battery n simcard

3. in middle of ur diamond on lower cover press it with pressure now turn it on prob will be fixed
[Touch Diamond, MDA Compact IV ROM Development] beckhome:
Microp Error fixed for now

Deep in this post was a solution to open the phone and reseat the connectors for the lcd, etc; I just cracked mine open and it's working for now. Try it and see what happens if you are havig the microp error. Reboot after reinstalling my microSD and all seems well.
[Touch Diamond, MDA Compact IV ROM Development] Android*XDA:
Problem fix for you, i think

try here ==>> http://www.free-gsm-unlock.com/2010/02/htc-diamond-rom-original.html

For original rom 6.1 profesional diamond,( diamond P3700 )

and choose you Rom carefully for CDMA or GSM phone,

and after instal the original rom, instal Hard SPL 1.24 is very good for cooked rom

Good luck
[Touch Diamond, MDA Compact IV ROM Development] roma2:
Hello,

Did you find a solution?

Touch HD gives me my start "version mismatch Micropr 3, Please update Latest Microp frimware"

A solution please? thank you...
[Touch Diamond, MDA Compact IV ROM Development] VlaJko79:
send to service or warranty, no other solution :(
[Touch Diamond, MDA Compact IV ROM Development] roma2:
Ok, thank you my friend, but I'm out of warranty.
[Android Q&A, Help & Troubleshooting] beinfo:
Hi all

i want to install TWRP on my Doogee N20PRO . i cannot find a TWRP File on the internet to install. I could find some for the N20 but not for the N20PRO. it´s an Helios P60 Processor with an MTK6771. I tried to install the HAVOC 3.7 but i get the Message "writing 1/15 failed (remote: this partition doesn´t exist)
[Android Q&A, Help & Troubleshooting] DragonPitbull:
This is simple about TWRP: Your phone have МТК Helio Р60 MT6771V/CA WITH Android 10.0 and it's a NEW phone now. So no developments yet.

For install GSI ROMs your need unlock bootloader and after follow the correct instructions to new phones shipped with A10!

If you only want install GSI so I suggest:

1- Have stock ROM first, always!!;

2- With security 1- you should unlock bootloader;

3- You can install GSI with stock recovery without problems.

The only part is: you cannot backup userdata.....
[Android Q&A, Help & Troubleshooting] beinfo:
Cool This helps already a lot.

i unlocked the Bootloader properly, but then i got a partition error. I assume i´ve an error in the command line. The phone was anyway only an interim solution till my POco F2 was back from repair. now i use it as a playground.

fastboot erase system - there i get a partition error.

erasing the User data was sucessful

but then

fastboot flash system system.img it stops at step 1/15 again for the partition error (partition doesn´t exist) Stock rom is available.

somebody knows the options i´ve to add to the command line?
[Android Q&A, Help & Troubleshooting] DragonPitbull:
Try but REMENBER I am not responsible for any errors. Bootloader should unlocked by adb-fastboot!!

Spoiler content hidden.
[Android Q&A, Help & Troubleshooting] philngai:
I also have an N20 Pro which I received Dec 2020. Had some trouble setting it up. I got the OEM ROM from Doogee customer support and was able to extract the boot image and patch it with Magisk. I then burned it with the SP Flash tool. It wouldn't boot until I burned a special vbmeta.img to turn off encryption. Now it's working fine.

Sorry this doesn't help you with TWRP but I think most people looking for TWRP are really looking to root their phone.
[Android Q&A, Help & Troubleshooting] flairepathos.info:
Okay so what ive seen is that you should avoid flashing custom roms via adb fastboot especially with our doogee phones, and also there are many incompatiable roms so what you will need is to unlock bootloader and do the whole twrp install thing adn also install magisk

before hand install treble info from google playstore and take down the information "arm64 a/b" and search for roms with that information to install custom os/rom/gsi properly. GSI versions are more preferred if your phone supports treblle

if your twrp keeps getting wiped after reboot open file :mount your system and connect to pc via usbcable (mtp if not showing disable mtp and re- enable it )

now got to where build.prop is saved there will be a file called recovery from boot.p , copy the file to pc , open with notepad, remove everything , save and copy back to phone (overwrite)

then go ahead and install magisk

make sure your magisk is working install edxposed, riru core , and busybox ndk get the apps you need for them (edxposed manager...) and then instal and activate a module which you can test if its working(if framework is active in edxposed manager and the module working correctly then you can go ahead and

Install custom os through twrp

follow these instructions ( https://xdaforums.com/t/guide-flashing-rom-pixelexperience-10-gsi-android-10-stable.4081685/ ) with your custom rom (corvus, havoc, lineage...

(the g-apps didnt flash for me (error code 64) but i just rebooted and everything was working fine (including gapps but camera sucked (doogee's rear camera setup was just terrible))

https://xdaforums.com/t/guide-flashing-rom-pixelexperience-10-gsi-android-10-stable.4081685/

** i can confirm follow instructions properly and it should work (i used this pixel experience on my doogee n20 make sure you unzip the .xz file and youre flashing a .img file

**also make sure its the gsi file (
[Google Pixel 5 Questions & Answers] I7210I:
Hi

I saw strange thingat the usage of whatsapp, two things

1. when I hear voice messege it makes some ticking when i hear it

2. sometimes, when a voice messege come to whatsapp, i open the screen , click to hear, and then thewhatsapp crashed and close and immediately openes again and than I click again to hear...

two strange problems
[Google Pixel 5 Questions & Answers] ulxerker:
I don't see this issue on my P5 ... of course, you already tried to re-install WhatsApp and your system incl. Google is up-to-date, right?
[Google Pixel 5 Questions & Answers] I7210I:
yes, it was even from day one of the device
[Google Pixel 5 Questions & Answers] I7210I:
quick update, I wrote to whatsapp support and they answer me that they aware to the problem and working to fix these
[Philips, Sony, TCL Android TV] ariacat:
Hello

I have a TCL 49P3cf running android 4.4 now.

I need to update it in any android version +5.

The TV update checking didn't give me anything same as the TCL website.

There is anything you can help me with?
[Philips, Sony, TCL Android TV] stasiof:
Post your TV firmware installed.
[Philips, Sony, TCL Android TV] ariacat:
Currect Version is: V8-T56FT07-LF1V036
[Philips, Sony, TCL Android TV] stasiof:
V042....

http://as-update.cedock.com/apps/resource2/V8T56FT07/V8-T56FT07-LF1V042/FOTA-OTA/V8-T56FT07-LF1V042.zip

build.date=Jun 10 2019
[Philips, Sony, TCL Android TV] ariacat:
thanks. and where can I find the updating guide?
[Philips, Sony, TCL Android TV] stasiof:
This is OTA update,so maybe something like this:

https://tclnordic.zendesk.com/hc/en-us/articles/360012916240-Perform-a-local-update-TCL-Smart-TV-3

Btw, read in your Manual.

Edit:

Don't unzip file.....

must be copied to USB FAT32 as you download.

Basic update....

1. Press Settings

2. Go to Option

3. Go to Software update

4. Go to USB Upgrade

5. The software will upgrade to the TV
[Philips, Sony, TCL Android TV] ariacat:
note. Shoud connect to USB/Services Port

Thanks. it's working and install. but I have 2 more problem.

in my TV manu I never have Home and Video Section. just TV and App showed. after I update for some min I have them, but then they are gone again.

the 2nd problem is the android version. as the TV running on 4.4, I have several problem with apps. is the any way to update the android version?
[Philips, Sony, TCL Android TV] stasiof:
First....some your configuration or setting maybe doing this.

If you don't have many apps, do factory reset and see again.

Second....Android is in firmware version, if you know anybody with Android 5?

I found V042 with Android 4.4.3, maybe can help me if in your TV now is

stated full version, as (sample).... V8-T56FT07-LF1V042.

00xxxx