yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] crazyscientist:
Nice to hear that, looks like what ever hardware was playing up has decided to play nice :D It's just temperature shifts I think from what i've heard from lots of people with this problem. Moisture forming inside the PDA. Or so I think
[Touch Diamond, MDA Compact IV ROM Development] tommm:
But my Diamond didn´t fix itself for 3 days..... Unfortunatelly after that I couldn´t do anything more than to send it for repair:(
[Touch Diamond, MDA Compact IV ROM Development] tommm:
Ok so today I got a message from our HTC service centre that they have found HW problem, changed display and the whole front panel n sending my Diamond back to me:)

And it was classified like a standard warranty repair;)
[Touch Diamond, MDA Compact IV ROM Development] MRE-net:
What country do you live in and where did you send your device to (which repair centre) ?

In Holland official HTC support sends it to Eurotwice in Belgium. I had the same microp error and when I got it back, the problem was still there. Eurotwice couldn't find any problem.

So I'm curious where you sent your device.

Also look at this post: http://xdaforums.com/showpost.php?p=3048690&postcount=1

It metnions that the bootloader displays a microp version. My bootloader never displays this.
[Touch Diamond, MDA Compact IV ROM Development] private69:
For Microp ERROR

Hello,

Im in france "FRENCH", if you leave in france and your diamond have a MircropERROR no probleme you can contact me i can repair it.

@+++
[Touch Diamond, MDA Compact IV ROM Development] tommm:
I´m from Czech and here we have only one service centre (www.vspdata.cz) and this is only for us...I still don´t have it - it´s somewhere on the way so I can´t say if it is really without problems or not but I hope that it will be ok - when they changed whole front panel with display...

It seems that this centre works very well - it took only one week:)
[Touch Diamond, MDA Compact IV ROM Development] theorie:
UPDATE:

the only way to fix this is to send in your phone for warranty repair.

this is a HARDWARE issue.

i just got my phone back from repair. they had to replace the main board.

just wanted to share!
[Touch Diamond, MDA Compact IV ROM Development] rnenjoy:
I took out the battery and pushed on several places where the battery should be. Took in the battery and now it worked. I still get the microp error, but the backlight works.

BUT! As soon as i input my USB cable, it goes "black" again. Ive tried it 3 times, works, but then goes black when inserting the USB.
[Touch Diamond, MDA Compact IV ROM Development] archeopetrix:
hi tommm, so finally did your diamond work ? if so the 'display' should be changed for this MicroP error

or is it, as theorie says, a 'Mainboard' problem? :confused:

am asking all this because mine is neither under warranty nor is insured.. will have to get it repaired from 3rd party source, and if they are not able to spot the prob, may be i could point them out the solution(to replace display or board) :(
[Touch Diamond, MDA Compact IV ROM Development] VlaJko79:
MICROP Problem

I dont think they even know whats causing it since if u change the display and motherboard whats left :eek: and since it happens on brand new TouchHD (mine 2weeks old), I can only describe this problem as "mysterious" after alot

time spent searching for solution, so far only able to use it w/out screen..
[Touch Diamond, MDA Compact IV ROM Development] nissan.y:
found a sulution!

put a piece of paper betwin the battery and the body...

its something with the connectors.

works for me!
[Touch Diamond, MDA Compact IV ROM Development] VlaJko79:
Nope, doesnt work for me...tried couple of times...:cool:
[Touch Diamond, MDA Compact IV ROM Development] fabyanyway:
Salut,

J'ai le même problème (Microp version mismatch....).

Tu dis qu'il faut démonter le telephone. Mais quelles parties exactement?

Merci
[Touch Diamond, MDA Compact IV ROM Development] Sardunya:
Hello friends.

My Diamond device, It do MicropError error; the last few weeks.

But removing the battery and plug is the correct.

We currently have not this error.

Send to guarantee this time, this error does not exist.

But what can I do if this error increases.
[Touch Diamond, MDA Compact IV ROM Development] cristsc:
microp error solved

this error is hardware fault caused by flex connectors. make good connexions and all ok. it work for me. dont try if is covered by waranty
[Touch Diamond, MDA Compact IV ROM Development] charliewynn:
Old thread but I wanted to confirm this..

I took apart my TP almost completely, blowing out all the ribbon cables and presto; working again.

If it helps I got as far as taking the screen half apart from the keyboard part. opening the screen part and disconnecting the 2 ribbon cables near the top 1/2 of the device. I tested it and it worked.

It might have been different connectors, like on the back of the mb, but I didn't test until I got to this point.

-cw
[Touch Diamond, MDA Compact IV ROM Development] Liquid s0u1:
Have the same problem on my Touch Pro. Being an IT dude I said eff it after argueing with my service provider + the manufac. to replace I decided to take a stab at identifying what caused the problem. I broke the phone down fully twice. Touch Screen is still fully responsive, no problems with the Diffuser at all. I've been running a program on the PC to display the screen remotely w/mouse interaction. I've crawled over the internet sifting through information and I'm currently compiling a Wiring Diagram, How-To: disassemble an HTC TP, A component identifier, the Remote Phone screen prog etc. Let me know if any of you would like this bundle posted. I don't feel like buying a new phone, I like this one an I've only had it for 5 months.
[Touch Diamond, MDA Compact IV ROM Development] siddharthsai:
Solved

http://xdaforums.com/showthread.php?t=657514 :rolleyes:
[Introductions] Blokewed:
Hi!

Starting off with a fact tha english isnt my mother. So i'm a zero knowledge but allwsts curious how things work. But mainly im gonna need some help with ma projects that involve Android.
[Google Pixel 4 XL Questions & Answers] killahax:
How can i dual boot? So i can boot into testing roms/kernals with out messing with my working main boot, using twrp. Im on 3.7 twrp
[Google Pixel 4 XL Questions & Answers] danerrickcuba@gmail.com:
A few methods exist, some very dangerous, all safe unless very careless, what device? If one plus you lucky there's already a full guide for that device, same for HUAWEI, basically learn how to use sgdisk or parted to resize/repartition, understand your device first, vendor ext4 or erofs?
[Xiaomi Mi 8 Questions & Answers] MertKaya:
I switched to 12.5 ROM like a year ago after Xiaomi didn't deliver it as an update from the stock 12.0 ROM as they promised. I first checked the Google Pixel OS and did not enjoy the extremely basic UI then decided to turn back to MIUI since I actually like how it looks. While I was at it I decided to load the latest version possible.

I rooted the thing to experiment but ended up not being able to find much to gain with it since it is a failed product that didn't sell well, there were not many software stuff for it. Anyway out of curiosity I recently installed 3DMark and it performed very bad compared to average score. It looked like it wasn't boosting to max clock speeds so I tried forcing it to max clock speeds for both GPU and CPU with root Android toolbox. This somehow made it worse and get 800 points which is only better than %1 Mi8 phones that finished this test. So I reverted the changes and got the same 1140 ish score I got before. Tried testing it again while it was plugged to the charger with no difference. Max temperature was 33C which makes me believe it is not boosting to right clock speeds.

To be honest phone still feels ok to use and battery life is enough for me since I recently replaced the battery. So I will not be installing another OS if it is the only reason for the low score since I don't really care benchmark scores as long as I have a smooth experience. But I would like to know why it is so bad and if there is a way to solve the issue without re-flashing the whole thing. I also don't want to re-flash it since last time I tried loading back the stock ROM from the whole backup I created and it somehow randomly failed in the middle of it and corrupted the partition that was responsible to making it connect to SIM and Wifi and it was a pain in the ass to figure out what happened and fix it from the old save file I had.

I am also very bored by using this thing but don't really want to buy a new phone while they stagnated this much over the past years in terms of technological advancement. I am planning to make a custom 3D printed back for it and install like a 10K mah battery to BMS board of my old battery and unlock all the clock limits on the software to fully unlock its potential. Does anyone know where can I get a CAD file for this phone so I can design the stuff I need for this.
[Realme 5 Pro Questions & Answers] Deleted member 12499091:
Hi everyone, I have a question can I flash a global firmware of realme 5 Pro on my chinese varian realme Q RMX1971CN? Thanks!.
[Android Q&A, Help & Troubleshooting] Iraklizh:
Is it possible to create an application where I can speak (without recording audio) and hear my own voice at the same time?
[Introductions] Iraklizh:
Good day, i am Iraklizh from Georgia, Tbilisi ( not US). I am new in android development. My background is only system andministrator and networking.
[General Topics] ajeetraina:
I have HTC Touch on which I can browse internet. CAn I connect my htc through USB cable to my Laptop and start accessing the internet on my Laptop.

Pls Suggest the steps if possible.
[General Topics] Rudegar:
if settings-usb to pc

have

enable advanced network functionality

checked

then it should have access to the pc's network when connected with usb
[ASUS ROG Phone 3 Questions & Answers] azharkhalid118:
Hi all,

I've rooted my device a few months ago. Unlocked bootloader, flashed TWRP and installed magisk. After that I have removed root because I couldn't use any payment or banking applications. Now my device heats up everytime i play games like pubg or CODM and getting lag. Also there is sound issue while calling. People can hear my background noise but cannot hear what i'm saying. I don't know if it's related to the rooting but I want to revert back to the factory settings. Can anyone help me do that? Downloading the firmware file from ASUS website and flashing the update will reset my recovery? I could not find anything from the net.
[ASUS ROG Phone 3 Questions & Answers] Andrologic:
Yes you can roll it fully back to factory. Doing a RAW flash and re-locking BL is probably the easiest way, and then upgrading to the ROM you need via the official way.

Banking/payment apps can be handled with root however even if tricky, so you could probably have kept your root, but that's a different topic...
[Vivo X Fold] Liran Israel:
from the last update the audio is less strong. can it be fixed?

View attachment 5888907
[General Questions and Answers] peoro:
My phone's LCD touchscreen is broken and the phone seems stuck in bootloop. I have access to a custom recovery (OrangeFox is installed, but I should be able to `fastboot boot` into any other).

I have read on this reddit post that it should be possible to flash a new ROM, push my computer's ADB public key to it, boot it and use `scrcpy` to control my phone.

However I'm stuck on the first step: how can I flash a new ROM to my phone via command line from OrangeFox or other recoveries?
[General Questions and Answers] xXx yYy:
You can't flash a Custom ROM via ADB, you've to do this via FASTBOOT or Custom Recovery.
[General Questions and Answers] peoro:
Yes, when I said "ADB", I meant the ADB of a Custom Recovery. I can boot into OrangeFox and then `adb shell` into it. I'm wondering how to install a ROM from there.

Installing the ROM from Fastboot would work too, if it's simpler.
[General Questions and Answers] WoKoschekk:
TWRP uses dd to flash raw images and tar + gzip to backup/restore userdata partition. It's all done with shell scripting and adb shell is nearly the same.
[General Questions and Answers] WoKoschekk:
@peoro The custom rom zip archive is build as OTA update.zip and either has a payload.bin (A/B slots) or *.dat.br compressed images for A-only devices. Both can be unpacked to get the raw images. Those images can be flashed via ADB or via fastboot.
[General Questions and Answers] xXx yYy:
Don't confuse things:

adb shell

is used to run Android ( Linux ) system commands on Android devices.
[General Questions and Answers] peoro:
Thank you for the replies. My phone is A-only (it's a Poco X3 Pro).

I just downloaded a new ROM (the latest crDroid 12 for my device) and I could find a number of `.dat.br` files in its zip:

$ unzip -Z1 crDroidAndroid-12.1-20230106-vayu-v8.12.zip | grep '.dat.br$'
odm.new.dat.br
product.new.dat.br
system.new.dat.br
system_ext.new.dat.br
vendor.new.dat.br

However I'm not sure where or how to flash these files and what other commands I need to use to e.g. format the various partitions or whatever is needed.

OrangeFox offers a `fox` command line tool (I believe it's a fork of TRWP's command). I believe it should help me with all of this, but I'm too much of a noob to know what to do and how.

Would you know where to find a good guide about installing a ROM via command line?

Otherwise could you tell me what commands I'm supposed to run and/or what operations I'm supposed to do?

I know my way around Linux pretty well, can write and read bash, but am a complete noob for anything related to android. Don't even know what the various partitions are, how they map to the contents of the drive and in general how the boot process works...
[General Questions and Answers] peoro:
Yeah. ADB gives me access to a shell on the phone. I can have a shell while the phone is in the Custom Recovery (OrangeFox, currently) and I believe I should be able to flash a new ROM from there. That's what I'm trying to do.

Any way to install a new ROM would work for me: `dd`, the `fox` command line tool, or fastboot.

I'm good with bash, but don't know much at all about Android's internals. But I'd love to find a noob-friendly guide on how to flash to a ROM using whatever tool.
[General Questions and Answers] peoro:
😭​

Which part?

While my phone is running a custom recovery (OrangeFox, TWRP, whatever), that recovery is able to flash a new ROM. It offers a UI to do so. Right? I can't use the UI, but can run anything on the recovery, via the shell opened by ADB.

Am I saying anything wrong?

I have access both to `fastboot` and to the shell of a running custom recovery. But I don't know how to install the ROM (the content of crDroidAndroid-12.1-20230106-vayu-v8.12.zip ) with either tool, without using the custom recovery's UI.
[General Questions and Answers] WoKoschekk:
The tool scrcpy installs *.odex compiled Java code on your device. This code isn't executable in any recovery.

Options for flashing your ROM:

– TWRP:

1. Put the raw images of your custom ROM into the ADB folder on your desktop and adb push them to the phone or use MTP to copy them.

2. Then you can use the openrecoveryscript.html (TWRP's commandline tool) to flash images.

TWRP Commandline Guide

</style>CLIENT SIDE/SCRIPTinstall FILENAME :	install FILENAME zip file.

twrp.me

– ADB:

1. copy all raw images into ADB folder

2. use adb push to flash the images on your device.

– ABD (adb shell):

1. copy all images via adb push or via MTP to your device

2. enter the device's shell with adb shell

3. You said you are familiar with bash scripting. Do you know the dd command and its syntax?

CAUTION: The command dd overwrites EVERYTHING and without a warning!! Be careful and only use it if you know what you're doing.
[General Questions and Answers] WoKoschekk:
Creating RAW images:

You need this tool to convert *.dat.br to raw image.
[General Questions and Answers] WoKoschekk:
Flash custom ROM via fastboot:

1. convert the *.dat.br to RAW images.

*.dat.br files

​

RAW images

​

partition

​

odm.new.dat.br​

odm.img​

odm​

product.new.dat.br​

product.img​

product​

system.new.dat.br​

system.img​

system​

system_ext.new.dat.br​

system_ext.img​

system_ext​

vendor.new.dat.br​

vendor.img​

vendor​

2. Use command

fastboot flash PARTITION RAW_IMAGE

to flash them all.
[General Questions and Answers] WoKoschekk:
Using ADB commands or adb shell to run commands in the device's shell (#!/system/bin/sh) doesn't matter. Both passing commands through adb.exe to the adbd on the device. Killing the adbd will kill the connection anywhere.
[General Questions and Answers] xXx yYy:
You must NOT teach me what ADB is and/or how it works.
[General Questions and Answers] peoro:
Thank you a lot for the detailed answer.

I used the TWRP approach as it seems the simpler.

I know `dd` and can read its man, but I'd rather not mess with the phone's partitions and block devices, unless it could result in a different outcome than using the `twrp` tool.

I tried to install two different ROMs (Lineage and crDroid), but neither manages to boot.

I can see that the few visible pixels on the broken LCD are in different colors for the two ROMs (so it did manage to install something), but neither ROM ever reaches a point where the power button turns the monitor on or off: they're both stuck on the bootloader.

What I did is basically this:

$ twrp wite cache
$ twrp wipe system
$ twrp install $ROM.zip
$ twrp format data
$ twrp wipe dalvik
$ twrp wipe cache
$ reboot

If that's a correct way to install a ROM, then I guess I have my answer: some of my phone's hardware is broken :(
[General Questions and Answers] WoKoschekk:
Use the adb sideload option to flash your ROM. That's the usual way to install it.

adb shell twrp sideload # to activate the process on client
adb sideload <ROM_PACKAGE> # to activate the process on host

Flashing starts automatically.

I'm not teaching. I just gave arguments.
[General Questions and Answers] WoKoschekk:
Yes, it's the correct way to install. All you need to wipe/format is data.
[General Questions and Answers] alecxs:
Seems you already found the solution yourself ;)

How do you know the ROM does not boot? note first boot takes up to 10 minutes.
[General Questions and Answers] peoro:
When the screen broke, I could tell that the ROM didn't work, because:

1. My phone didn't connect to my router. I can tell by looking at the router's log or at internet services that tell me the last time the device was online.

2. If I try to call or send SMS to SIM on the phone, the phone doesn't ring or vibrate.

3. The screen never turns off. Not even when I press the power button.

All those points still hold with the newly flashed ROM too. Of course now it can't connect to anything, but it still doesn't react to incoming calls or to the power button.

I can kinda see from the glitchy colors on the bottom of the broken LCD that the bootloader animation is displayed, but it seems that it's stuck there...

If you have any ideas on how to debug this, I'm very interested.

This is a dump of `dmesg` (from the custom recovery). It shows a bunch of errors, but I can't tell whether any is about real hardware issues.
[General Questions and Answers] peoro:
Damn :/

I'll start shopping for a new phone.

In any case, thank you so much for all the help!

At least I learned something and didn't waste money on a new LCD screen.
[General Questions and Answers] alecxs:
You cannot receive calls until the sim pin is unlocked. even without pin this doesn't tell you something, because you haven't finished the initial setup. Some custom ROMs enforce dm-verity so they cannot boot straight after flashing. dmesg of recovery is useless, but you can capture it during boot with init.rc script. if system or vendor is mountable, place a custom.rc in etc/init, otherwise patch the boot.img with magisk and use overlay.d
[General Questions and Answers] peoro:
OK, thank you for the suggestion. I tried to find a way to debug a ROM but couldn't find anything yet. You're giving me hope again.

...By the way, is there a decent source of information for this kind of stuff? Something like the Arch Wiki, for Android?

I'm not sure where `etc/init` is in Android (is it in what the recovery mounts as `/system`?), nor what's the syntax of those rc files (I can't simply put a `dmesg > /dmesg` in there, can I?). Similarly I'm not sure how to use Magisk for any of this.

I'm trying to look up information on this on the internet, but I'm unable to find clear documentation: everything is written in forum posts that don't have enough context for an Android noob such as myself...
[General Questions and Answers] alecxs:
Yeah I am too searching for a thread that fits best... but only found for Magisk (1, 2)

first mount system and check the mount point. it's either /system or /system_root.

once mounted rw, there is system/etc/init directory inside where you can place own .rc scripts that will executed automatically.

you can exec dmesg or logcat straight from .rc with exec or create a shell script that is executed from .rc

write logs to /cache partition and adb pull the log file to PC later.

in case you can't mount system rw, get a backup of boot partition to another android device.

patch the image with Magisk app (no root needed)

then unpack the magisk_patched.img with AIK. you will notice Magisk has created overlay.d directory in ramdisk.

place your .rc script in overlay.d and repack the image. flash it back into boot partition with fastboot or dd

if you have access to /data partition you can enable usb-debugging and authorize it by placing adb_keys directly. then you could just get a logcat straight from adb during boot.
[General Questions and Answers] peoro:
Thank you so much!

It's already deep in the night over here and I'm afraid that if I start this, another hour will go by.

I'll play with this tomorrow morning.
[General Questions and Answers] Renate:
Nobody mentioned:

Take your update.zip

Extract META-INF\com\google\android\update-binary

Put both update-binary and update.zip somewhere

chmod 755 update-binary

./update-binary 2 1 update.zip
[General Questions and Answers] WoKoschekk:
@peoro Let's focus on your basic problem: You need a bootable ROM for installing and using screencopy due to your broken LCD. At the moment you are stuck on installing/booting a ROM.

For a better understanding of your problem I downloaded the LineageOS ROM for the Poco X3 Pro.

The most important thing to know is that your device has a dynamic partition (/super) layout!! AFAIK it's

not possible to flash any dynamic partition

like /system directly via a custom recovery.

In other words: Using the ADB command twrp install <ANY DYNAMIC PARTiTION> won't succeed. Even if your cmd line gives you an error code 0 after executing this command. That's not a proof that the dynamic partition was flashed successfully! I'm pretty sure that therefore you are stuck while booting the ROM.

To flash those dynymic partitions in the correct way you must use the installation/update routine of the installer.zip (find it in META-INF/com/google/android/updater-script). Therefore you must use ADB sideload (it should be the easiest way for that) as I already mentioned in this post before.

If you still have problems, then you should consider flashing the stock ROM first before flashing a custom ROM. Although I'm wondering why you don't use the stock ROM directly? There's no need to install a custom ROM, isn't it?

But once you install a bootable ROM it will be easy to activate USB debugging and install scrcpy.

@peoro That's right what @alecxs said. As long as the setup wizard is running, many features are disabled by default due to security issues related to bypassing FRP (factory reset protection). Every additional feature, option, linked URL etc. could enable a way to bypass FRP. Don't take options/functions for granted as long as the setup wizard is running! An incoming call/SMS could be a security issue in that state.
[General Questions and Answers] alecxs:
No need to sideload, twrp install does exactly this. same as TWRP > Install > in GUI