Will there be a Custom Rom?

[ignalop1983]

Will it help to develop a ROM?
https://xdaforums.com/mi-note-10/development/firmware-xiaomi-mi-note-10-pro-mi-cc-9-t4096347
I Hope to have a ROM in a future.

 

[veimus]

50 euro (BRL 298) more from me

Transaction ID
3JF645249L149984A

 

[Hlcpereira]

Will it help to develop a ROM?
https://xdaforums.com/mi-note-10/development/firmware-xiaomi-mi-note-10-pro-mi-cc-9-t4096347
I Hope to have a ROM in a future.

Firmwares in that case are a bunch of binaries for bootloader and modem. Those are flashed before the ROM to avoid issues further down.

 

[se7en48]

I'm throwing in another 20€. We got this far guys, just a little more!

 

[Hlcpereira]

Ok, a bit of updates, mainly because I do feel that you guys deserve.

First one: I'm going to temporary close the crowdfunding. "Why? The goal wasn't reached yet neither is being one and a half month" I know, yet @Genomey could found a cheap Mi Note 10 on eBay and got it for about 252 USD. I'm going to wait for him get the device on his end and check and if everything is ok I'll send the money to him while he send me the device. "What will happen with the remaining amount?" 63.74 USD (or 347.01 BRL) are from me, I already had it or got it by my own in the meanwhile.

The total amount donated was of 267.22 USD. (1454.61 BRL).

Second is: In the meanwhile me and @0201m were working on the device sources and testing (huge shout out for him for helping in testing and troubleshooting) and so far: Kernel boots, everything builds, but yet depending of which blobs/vendor binaries you use the device reboots to recovery. Also when we managed to make it boot, the display service was dead (which means it's stuck on the Mi logo while the system already booted) XD (Not joking at all, me and him almost lost our minds cause of that ;_; ). At least the vibrator is confirmed to be working. So far that's the progress.

 

[iFlashed]

Ok, a bit of updates, mainly because I do feel that you guys deserve.

First one: I'm going to temporary close the crowdfunding. "Why? The goal wasn't reached yet neither is being one and a half month" I know, yet @Genomey could found a cheap Mi Note 10 on eBay and got it for about 252 USD. I'm going to wait for him get the device on his end and check and if everything is ok I'll send the money to him while he send me the device. "What will happen with the remaining amount?" 63.74 USD (or 347.01 BRL) are from me, I already had it or got it by my own in the meanwhile.

The total amount donated was of 267.22 USD. (1454.61 BRL).

Second is: In the meanwhile me and @0201m were working on the device sources and testing (huge shout out for him for helping in testing and troubleshooting) and so far: Kernel boots, everything builds, but yet depending of which blobs/vendor binaries you use the device reboots to recovery. Also when we managed to make it boot, the display service was dead (which means it's stuck on the Mi logo while the system already booted) XD (Not joking at all, me and him almost lost our minds cause of that ;_; ). At least the vibrator is confirmed to be working. So far that's the progress.

Congratulations for the crowfounding, and thanks for your interest on this device. Good luck :good:

 

[ViRUS2015]

Ok, a bit of updates, mainly because I do feel that you guys deserve.

First one: I'm going to temporary close the crowdfunding. "Why? The goal wasn't reached yet neither is being one and a half month" I know, yet @Genomey could found a cheap Mi Note 10 on eBay and got it for about 252 USD. I'm going to wait for him get the device on his end and check and if everything is ok I'll send the money to him while he send me the device. "What will happen with the remaining amount?" 63.74 USD (or 347.01 BRL) are from me, I already had it or got it by my own in the meanwhile.

The total amount donated was of 267.22 USD. (1454.61 BRL).

Second is: In the meanwhile me and @0201m were working on the device sources and testing (huge shout out for him for helping in testing and troubleshooting) and so far: Kernel boots, everything builds, but yet depending of which blobs/vendor binaries you use the device reboots to recovery. Also when we managed to make it boot, the display service was dead (which means it's stuck on the Mi logo while the system already booted) XD (Not joking at all, me and him almost lost our minds cause of that ;_; ). At least the vibrator is confirmed to be working. So far that's the progress.

Thank you so much for the update, and for all the troubles, man! Makes me glad having donated to someone so nice like you :angel:

Hopefully you can get Lineage working on the Mi Note 10

 

[Arcee-kun]

Hoping everything will turn out great. Thank you for all the support on this device. It has a lot of potential.

 

[Deniska621]

Will wait custom rom,s .....Havoc.RR...

 

[WaldenGaming]

I hope everything is going well! @Hlcpereira Could you please update how far you got it to work?

 

[Hlcpereira]

I hope everything is going well! @Hlcpereira Could you please update how far you got it to work?

Only headaches so far. I stopped for awhile in order to not burn myself. Yet the problem so far is: Seems we'll have to wait Xiaomj release the q-oss branch of tucana sources in order to get anything working properly. I tried also using prebuilt kernel (and vendor) from MIUI but that seems to be no luck at all (it didn't boot, while building vendor and kernel from source is booting already but display and audio dead). Plus doing blindly without the device (yes I didn't receive it yet... @Genomey still working on getting rid of the Mi Account block to send me the device yet) is asking for taking leaps in the dark.

Sent from my MI 8 using XDA Labs

 

[ndzaky]

Only headaches so far. I stopped for awhile in order to not burn myself. Yet the problem so far is: Seems we'll have to wait Xiaomj release the q-oss branch of tucana sources in order to get anything working properly. I tried also using prebuilt kernel (and vendor) from MIUI but that seems to be no luck at all (it didn't boot, while building vendor and kernel from source is booting already but display and audio dead). Plus doing blindly without the device (yes I didn't receive it yet... @Genomey still working on getting rid of the Mi Account block to send me the device yet) is asking for taking leaps in the dark.

Sent from my MI 8 using XDA Labs

So it's impossible without q-oss branch from Xiaomi ? I'm not asking ETA btw, I just eager to know whether this device have a hope for Custom ROM or not.

 

[Hlcpereira]

So it's impossible without q-oss branch from Xiaomi ? I'm not asking ETA btw, I just eager to know whether this device have a hope for Custom ROM or not.

Well, it seems so at least. I'm looking on what to do and yet: I can try doing pie builds first as Pie is already stable and then move to 10 Q after, or even try another stuff kernel related on my range.

 

[iSonik]

Well, it seems so at least. I'm looking on what to do and yet: I can try doing pie builds first as Pie is already stable and then move to 10 Q after, or even try another stuff kernel related on my range.

Since GSI are semi working, you could try starting with an GSI. Only thing not really working is the overlay

 

[alibei]

I tried to compile, boot and fix the problem but I hadn't luck.
I'm only getting these errors:

649 649 E SDM : DRMAtomicReq::Commit: drmModeAtomicCommit failed with error 22 (Invalid argument).
649 649 E SDM : HWDeviceDRM::NullCommit: failed with error -22
649 649 E SDM : HWDeviceDRM:owerOn: Failed with error: 11
649 649 E SDM : HWCDisplay:repareLayerStack: Prepare failed. Error = 11
647 647 E HWComposer: prepare: presentOrValidate failed for display 19261101167563905: BadDisplay (2)
647 647 E SurfaceFlinger: prepareFrame failed for DisplayDevice{19261101167563905, primary, "xiaomi f4 41 "}: -2147483648 (Unknown error -2147483648)

Full log: mediafire.com/file/39y5zzfiqyyb6ij/log.txt/file

 

[Hlcpereira]

I tried to compile, boot and fix the problem but I hadn't luck.
I'm only getting these errors:

649 649 E SDM : DRMAtomicReq::Commit: drmModeAtomicCommit failed with error 22 (Invalid argument).
649 649 E SDM : HWDeviceDRM::NullCommit: failed with error -22
649 649 E SDM : HWDeviceDRM:owerOn: Failed with error: 11
649 649 E SDM : HWCDisplay:repareLayerStack: Prepare failed. Error = 11
647 647 E HWComposer: prepare: presentOrValidate failed for display 19261101167563905: BadDisplay (2)
647 647 E SurfaceFlinger: prepareFrame failed for DisplayDevice{19261101167563905, primary, "xiaomi f4 41 "}: -2147483648 (Unknown error -2147483648)

Full log: mediafire.com/file/39y5zzfiqyyb6ij/log.txt/file

Where are your vendor/xiaomi folder from?

 

[alibei]

Where are your vendor/xiaomi folder from?

I used your gitlab.

 

[ItsBen12000]

Since GSI are semi working, you could try starting with an GSI. Only thing not really working is the overlay

> GSI

 

[alibei]

Where are your vendor/xiaomi folder from?

I think you missed something in the kernel. But i don't know if it is necessary.

For example in dsi_panel.c:
https://ibb.co/BK6LLSJ

 

[iSonik]

> GSI

Yes, but GSIs are better than nothing