Database Develop

MIUI Global 7.2.4.0.0 uses A LOT of RAM. (?)

Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John

jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.

proag said:
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.
Click to expand...
Click to collapse
Thank you. I didn't notice the extra zero and didn't think it was unoffical.
Sincerely
John

jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You are on an un-official modefied version.
The fake version is 7.2.4.0.0 <- your version.
The real official and supported by Xiaomi version is 7.2.4.0

Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!

androFRUST said:
Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!
Click to expand...
Click to collapse
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.

TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all

TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
Thanks for the reply! Before proceeding, I actually received the SMS to unlock the bootloader but im still at work so I cant go back and attempt the unlock. So just trying to manage my expectations here.
Is it safe to assume that all I need to do now is log in to the unlock tool by miui and unlock? because im still on 7.2.4.0.0 (the unofficial discontinued rom) and I have no way of flashing it to any other roms. My last attempt last night was again, stuck at 52% after a nights worth of wait! TT
---------- Post added at 03:01 AM ---------- Previous post was at 02:49 AM ----------
xtachix said:
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all
Click to expand...
Click to collapse
Thanks for the help. I will attempt this as a last resort. I just received the SMS to unlock my bootloader. Hopefully its as simple as logging in and unlocking so I can get rid of this pesky 7.2.4.0.0 supposed "Global" rom.

i have successfully flashed to global rom!!! but now i have no audio coming from the speakers!!!! is it just my luck!!!??? and after reflashing again.. its completely dead.. its goes into the sign in to miui welcome page and just goes insane.. like to the point where i cant even select options and and random menu sounds keep coming up.. cant even turn off i had to reboot to fastboot.. is a goner? sighs..

7.2.4.0.0 to Resurrection Remix (CM13)
- unlock bootloader
- flash TWRP with fastboot
- install Resurrection Remix
- install GApps
- reboot, now it's say Google play stopped.
- go back to TWRP
- wipe data
- reboot and everything is working

Rooting DOOGEE X5 MAX Pro

Hi,
I'd love to know if someone has already rooted'n'rommed this phone.
Please let us know! :fingers-crossed:

TT TT said:
Hi,
I'd love to know if someone has already rooted'n'rommed this phone.
Please let us know! :fingers-crossed:
Click to expand...
Click to collapse
Hi, on russian site they have already done it
ttp://4pda.ru/forum/index.php?showtopic=749517&st=560#entry51150598
Add "h" in the beginning (I don't have permission to publish links )
And use google translate
PS. Don't forget to create backup before all manipulations. Especially IMEI

HoboMoe said:
Hi, on russian site they have already done it
ttp://4pda.ru/forum/index.php?showtopic=749517&st=560#entry51150598
Add "h" in the beginning (I don't have permission to publish links )
And use google translate
PS. Don't forget to create backup before all manipulations. Especially IMEI
Click to expand...
Click to collapse
Nice!!
Good reason to practice my Russian :victory:
Thanks a lot, Sir!

altrom also has a rom can be installed via TWRP. Not sure how legit it is though.

TT TT said:
Hi,
I'd love to know if someone has already rooted'n'rommed this phone.
Please let us know! :fingers-crossed:
Click to expand...
Click to collapse
I finally made it to flash TWRP with a flash tool I found via a doogee-blog, a official doogee Q&A site and a blog on doogeemobile.
Why do I have to verify so often?
EDIT: I had a look at my documents, got the flash tool from dogeemobile.com and the TWRP 3.0.2 from needrom. You have to pay attention that you use ROMs for the particular processor of the maxpro (MT6737 M). SU from here of course. :good:
HTH
Why do I have no verification to do any more??

still cant do it
messing around for a week and still no sucess.
flash tool says !sucessful! but i reboot and get stock recovery - not what i expect (twrp)...
also cpu-z says is mt6735- but if i try that one i get :
chip type not match
targetef use value 0xA4020000
but it works with mt6737 - it just dont reboot into that other loader....
any ideas
mlcrip co uk/DooGee/i1.jpg
also tried both x5pro and x5maxpro...
(TWRP-Doogee-X5-MAX-PRO.zip)
(TWRP_Recovery_X5_Pro.rar)
dev enabled, usb debugging, oem unlocking on,
also yes, i do imediately go for bootloader (volume up while turning on)- doesnt work no matter what.
UPDATE:
DooGee X5Max_Pro MT6737M (Android 6.0, 20161123, kernel 3.18.19+)
i sorted it. turns out i had to use x32TWRP (fund it here somewhere on this site)
MT6737M_Android_scatter.txt (plus image come with it)
SuperSU-v2.78-SR3-.zip
also i randomly went for adb commandline to 'unlock rom' not sure if it was necessary, but wont hurt.
so if any noob wanna easy way,
1. 'minimal adb and fast boot' to unlock rom (few cmd commands and you done)
2. start flash tool, set CORRECT scatter file (MT6xxx- if you set wrong model it will give you error popup)
3. set DOWNLOAD ONLY' on drop down box. press DOWNLOAD button.
4.REMOVE BATTERY off your phone. Plug usb cable. youll get 'sucess' pop up window. close the flash tools. disconnect phone but keep it OFF!
5.pop in the battery. press volume up+on button.
at this point you should get some proper user interface, not the black screen with some letters (stock bootloader) something went wrong.
what you should see imediately once you turn it on- just google TWRP images lol.
techbeasts.com/wp-content/uploads/2014/10/TWRP-Recovery.bmp
also all files needed (incl flash tool) i dropped here:
one by one (in case if someone needs scatter file or something)- or inside 'all' folder- all tools compressed into rar
mlcrip.co.uk/android/rooting/files/

Flashlight don't work - How to test if it is broken

Hi, first of all, sorry for my bad english.
I hope you understand
I've installed LineageOS 14.1 and all work's great
Then I've installed a new nightly and the camera led flash didn't work anymore.
Not as flashlight and also not as camera flash.
So I did a "factory reset" and installed the first LineageOS build.
The LED still doesn't work.
I wan't to test the Hardware if the LED is broken.
I used following code to open service menu but nothing happens. *#*#197328640#*#*
The entered code dissapear and that's it.
How can I test the Hardware? some tipps to reactivate the LED?
Thanks a lot

Noone?
I need some help, please.
How can I test the Flashlight to find out whats wrong. Is it a soft- or a hardware issue?

nierewa said:
Hi, first of all, sorry for my bad english.
I hope you understand
I've installed LineageOS 14.1 and all work's great
Then I've installed a new nightly and the camera led flash didn't work anymore.
Not as flashlight and also not as camera flash.
So I did a "factory reset" and installed the first LineageOS build.
The LED still doesn't work.
I wan't to test the Hardware if the LED is broken.
I used following code to open service menu but nothing happens. *#*#197328640#*#*
The entered code dissapear and that's it.
How can I test the Hardware? some tipps to reactivate the LED?
Thanks a lot
Click to expand...
Click to collapse
Factory reset is not enough. Recommended is clean install, wipe at least system, cache and dalvik, then flash previous ROM. If it still doesn't work, flash KDZ.

lidde said:
Factory reset is not enough. Recommended is clean install, wipe at least system, cache and dalvik, then flash previous ROM. If it still doesn't work, flash KDZ.
Click to expand...
Click to collapse
First of all, thank you.
With "factory reset" I mean I made the following:
Code:
1. Boot into TWRP
2. choose wipe
3. choose advanced wipe
4. select: Dalvik/ART Cache
System
Data
Internal Storage
Cache
5. swipe to wipe
6. flash previous ROM
So it doesn't work. How can I flash KDZ?
The same way like LIneageOS?

nierewa said:
First of all, thank you.
With "factory reset" I mean I made the following:
So it doesn't work. How can I flash KDZ?
The same way like LIneageOS?
Click to expand...
Click to collapse
No its different look around on xda for this device flashing kdz and you'll find it.

If installed D40520a_00.kdz
Flashlight still does't work. So it seems to be broken :crying:

nierewa said:
If installed D40520a_00.kdz
Flashlight still does't work. So it seems to be broken :crying:
Click to expand...
Click to collapse
Yeah it probably is.

Hey there. Your flashlight is not broken. Trying adding the widget to your lock screen. Or if you want to test type this in your dialer 3845#*405# and a hidden menu will appear from where you can test the features of your device. But if you reboot your phone they reset. I hope this helps you.

Gaptain4 said:
Hey there. Your flashlight is not broken. Trying adding the widget to your lock screen. Or if you want to test type this in your dialer 3845#*405# and a hidden menu will appear from where you can test the features of your device. But if you reboot your phone they reset. I hope this helps you.
Click to expand...
Click to collapse
Hi there.
You're right.
I've flashed the new LineagoOS nightly and the Flaslight turns on for about 1 or 2 seconds and then turn out.
This happens every time i've tested it.
The code 3845#*405# doesn't work.
I see a message saying "USSD code running". That quickly disappears and then nothings happens.
It seems that I can't add the flashlight widget to lock screen.
any suggestions how I get the flashlight work?

nierewa said:
Hi there.
You're right.
I've flashed the new LineagoOS nightly and the Flaslight turns on for about 1 or 2 seconds and then turn out.
This happens every time i've tested it.
The code 3845#*405# doesn't work.
I see a message saying "USSD code running". That quickly disappears and then nothings happens.
It seems that I can't add the flashlight widget to lock screen.
any suggestions how I get the flashlight work?
Click to expand...
Click to collapse
Hey there the code won't work in custom roms. It is only for stock roms.It opens hidden menu. Custom ROMs take the advantage of your phone while it mat offer you a faster phone.Please revert back to stock ROM. Ik stock ROMs are slow.But it is much better to stay with stock ROMs with root and custom recovery and xposed.Check flash light once you flash stock recovery.
Hope this helps ?

First of all: Thanks a lot.
Gaptain4 said:
... But it is much better to stay with stock ROMs with root and custom recovery and xposed. ...
Click to expand...
Click to collapse
What means xposed? Some kind of app?
I've flashed D40520a_00.kdz ago but Flashlight also didn't work.
It "works" since I've flashed ne nightly...
If I flashed the stock rom all Preferences would be reset, right?
So why did flashlight not worked if I installed D40520a_00.kdz?

nierewa said:
First of all: Thanks a lot.
What means xposed? Some kind of app?
I've flashed D40520a_00.kdz ago but Flashlight also didn't work.
It "works" since I've flashed ne nightly...
If I flashed the stock rom all Preferences would be reset, right?
So why did flashlight not worked if I installed D40520a_00.kdz?
Click to expand...
Click to collapse
Hey take a backup of your internal storage.Then in Lg flash tool do a csc flash.Flash correct kdz file.
Try some Google play apps for turning on flashlight

OK. I try it once again.
I usethis guide to flash KDZ. Is it OK?
What is a CSC flash?
Is it an other choose for "3GQCT"?

Hi there.
I think you mean CSE Flash?
I flashed my phone descripted in this Guide.
Type: CDMA
Phonemode: Diag
KDZ: D40520a_00.kdz
Upgrade with CSMG Client: CSE Flash
After the first setup wizzard I get a software update. Now the software version is: v20b-EUR-XX
Android-version: 5.0.2
Kernel-Version: 3.4.0+
Where in the hidden menu 3845#*405# can I found a entry to test the flashlight?
( No apps for turning on flashlight works )

nierewa said:
Hi there.
I think you mean CSE Flash?
I flashed my phone descripted in this Guide.
Type: CDMA
Phonemode: Diag
KDZ: D40520a_00.kdz
Upgrade with CSMG Client: CSE Flash
After the first setup wizzard I get a software update. Now the software version is: v20b-EUR-XX
Android-version: 5.0.2
Kernel-Version: 3.4.0+
Where in the hidden menu 3845#*405# can I found a entry to test the flashlight?
( No apps for turning on flashlight works )
Click to expand...
Click to collapse
Test your phone features one by one in hidden menu

Test your phone features one by one in hidden menu
Click to expand...
Click to collapse
I've tested every menupoint and I found nothing.
With the stockrom I have no Torchlight symbol in quick settings (when you move from the top to the bottom where you can activate wlan, bluetooth etc.)
I add a torchlight widget to the homescreen. It turns on for about 2 seconds then turns off if I activate it.
The SOS-function works. Lollipop or KitKat stock. always the same result.
Is it possible to flash the complete smartphone.
It seems like there's a progamming block or some kind of settings that's wrong and that won't reseted with stockrom flash.

Download flashlight from playstore and test

it is always the same with every app.
The LED works for about 1 second than turns off.
Flickering works at all.

Try contacting lg service centre for a possible fix.Try flashing a bootstack or a custom kernel.I know they are not related to flash light but still trying is not bad at all.

Gaptain4 said:
... Try flashing a bootstack or a custom kernel...
Click to expand...
Click to collapse
Where can I get some?
Is there a tutorial for that?

[DEV][9.0] LineageOS 16

DISCLAIMER:
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
INTRODUCTION
This thread is mainly intended for devs (pro devs don't really belong here because they're pro and this thread is useless), for someone who need help to continue the work for Nova and fix the bugs on Pie (not many left). I'll help as long as you can speak English xD (no google translate because it can cause misunderstandings). However, don't expect me to spend the same time into this as i''ve did when i've had the phone. Yes, i no longer have the phone (it's still dead) and if you're not up to date with that, then you can read the announcement here and i've mentioned that i've got a new phone here. On top of this, i can't build anymore because i can't sign up on Google Cloud Platform anymore. I've wrote about this here at the hidden content (below as a side note).
Users can also help with doing researches, testing things and logs.
I don't know if i'll consider to continue working on it myself alone without the phone. I'd need at least to be able to build and then i'd need people to test new builds / flashable zips. At some point i might consider that because i'm missing this phone and the community xD.
SOURCES
Device: https://github.com/skinzor/android_device_huawei_hwcan/tree/lineage-16.0-last
Vendor: https://github.com/skinzor/proprietary_vendor_huawei/tree/lineage-16.0-last
Kernel: https://github.com/skinzor/android_kernel_huawei_msm8953-1/tree/lineage-16.0-last
Click to expand...
Click to collapse
There's two branches:
1) lineage-16.0: those ones were used when i've booted Pie the first time. Remember that i've wrote about it here? Those ones were updated from mido's ones.
2) lineage-16.0-last. those ones are the last ones and updated, which i've used in my last build. Those ones were continued from previous branch and updated from tissot ones which were / are updated by another dev (not the same dev as on mido). I recommend to continue with this branch, but it's up to you. You might not be able to get a successful or bootable build anymore with lineage-16.0 branch anyway because lineage's sources were updated since then.
I've used mido's trees as reference for lineage 14 and 15 trees too. You can figure that yourself if you check mido's trees and then Nova's ones, as i've cherry-picked the commits. Why did i use mido's trees? Because:
1) It has the same qcom chipset as Nova.
2) It is a popular phone.
3) A good dev was working on it.
4) It has official lineage support.
Now you might ask why i haven't did myself everything from scratch. Well, as a newbie dev, it would've been much harder and would've took much more time. Also, i'd say that there's no point at all to do something from scratch when it was already done unless you want to go the "hard" way, assuming you have time and want to learn more. I've still learnt a lot since i've started.
There are "universal" commits which are about fixes / improvements that can be related to e.g. the android version or the qcom chipset and those commits are usually found in many device trees, so you just cherry-pick them. A good example would be this commit: hwcan: Use mke2fs to create ext4 images.
FIXING THE BUGS OF LINEAGE 16 / PIE
I assume that you've used lineage-16.0-last branch as i've recommended. I no longer remember what bugs had my last build, but i think that the bluetooth was working, while it wasn't working in the build made from old lineage-16.0 branch. However, i remember that it had a new bug and as far as i remember, it was the RIL, but the baseband was showing up. I think i've tried to fix it and i've got it working (i remember that it was about the blobs), but i don't remember how. As of typing now, i've looked into the logcat which i still have and i've seen this:
Code:
F linker : CANNOT LINK EXECUTABLE "/vendor/bin/tftp_server": library "liboemaids_vendor.so" not found
That kind of error is self explanatory: the blob / lib is missing. After i've seen this, i've remembered that it's a new blob which got added in the original commit and which i've cherry-picked here. I didn't include that blob for a reason, but i don't remember that reason lol (it's not that i've forgot it, but i've skipped it for a reason). I remember that back then i've added the blob manually after i've seen the error, but i don't remember if that's what fixed the RIL, so you can try that and let me know.
As i've said already, i don't remember what bugs had that build besides the RIL, so you can try it and let me know.
At the introduction i've mentioned that i can help. I'll help only here on XDA in this thread because it may help other people too if they're having the same error / problem and after all, it's nice to have a thread like this in my opinion.
You can attach the log or paste it to gist github, pastebin, del.dog or any pasting website, but don't paste it in the XDA post because it just sucks.
Click to expand...
Click to collapse
DOWNLOADS
MEDIAFIRE | ANDROIDFILEHOST
As i've recommended to use lineage-16.0-last branch to build / continue the development, i also recommend to flash that build.
The build from lineage-16.0 branch folder doesn't boot. Back then, when i've seen that it doesn't boot and took a look at the logcat, i've tried the graphic blobs from the tree of zenfone 3 and that one was using them from nokia 7 plus (based on the commit). I had two zips in my PC and i've uploaded both. The first one created is graphic_pie_blobs_zenfone3_nokia_7_plus.zip and the second one sdm_blobs_zenfone3_nokia7_plus.zip, so you flash them in that order. As i've mentioned in that post in which i've said that i've booted Pie, there is some lag / glitches while scrolling, due the display / graphic blobs.
ENDING
As i've promised, i've pushed the tree sources and uploaded my first and last build. The reason i'm willing to help in fixing the bugs is because i'm missing this phone and this community here on XDA (as i've expected xD). It was fun and thanks to this phone and y`all for your support and kind words, i've learnt so many things in this journey. That's simply unforgettable for me.
Hopefully someone will jump on and continue the development further. I'll be here to help.
XDA:DevDB Information
[DEV][9.0] LineageOS 16, ROM for the Huawei Nova/Nova Plus
Contributors
#Henkate
Source Code: https://github.com/skinzor/android_kernel_huawei_msm8953-1/tree/lineage-16.0-last
ROM OS Version: 9.x Pie
ROM Firmware Required: Unlocked bootloader, TWRP
Version Information
Status: Testing
Created 2019-01-02
Last Updated 2019-01-05

Reserved

Reserved

Thank you for all the hard work you put into this. I would try to follow the leads, but for me this phone is dead now. I had hoped it would be something, but naw, just a hunk of something. Maybe someone can pick it up and go with it, encouraged everyone to try. If you are thinking about it Robert @#Henkate will help you. Great person, and this phone got me to know him so boom, good phone.
Maybe this should be in off topic thread, but I will post here.

Thank you for the great work that you have done. You gave us nougat, oreo, almost a pie. LineageOS 15.1 is the best firmware I have ever used. EmUi far behind. Thanks again a lot. Pie is full of bugs (I have already tried), counted a huge list of 10 items, but I think it's time to relax. You gave nova a second life and for that I am grateful to you. I found out that you are switching to another phone. Good luck in developing it, you are a good developer, the main thing is to believe in yourself!

Hi enkate... does wifi calling work on 16 ?
thanks

virusdunil said:
Hi enkate... does wifi calling work on 16 ?
thanks
Click to expand...
Click to collapse
He has no way to check. Maybe someone who has flashed it could test.

wow！thx a lot，I will try it now！

Hey Henkate !, Yesterday I installed LOS16, the last build that you compiled, botched and everything, but at the moment of continuing with the initial configuration, the screen does not give an image, the touch works, but it runs out of image: /

Alee.se said:
Hey Henkate !, Yesterday I installed LOS16, the last build that you compiled, botched and everything, but at the moment of continuing with the initial configuration, the screen does not give an image, the touch works, but it runs out of image: /
Click to expand...
Click to collapse
With the first build go two files, except for the firmware, responsible for the display. Flash them after flash lineage 16 last build and everything will work

Logcats
Hey there!
Finally tried it. I flashed just the latest build and there is what I got:
After flashing only ROM, it booted, but nothing was drawn at the display. Ok, that was expect
Then I wiped system and data again, flashed the build and both of the other zips (from the first build folder)
It booted fine, RIL was working at start, wifi ok. Many other things couldn't be tested, because randomly (one time taking photos, other when scrolling settings, other when trying to test bluetooth) screen went black the blue led got lit up.
I took a logcat only with errors and it seems there is a lot to fix. Still today (just a lot later today, I have to work) I'm gonna fetch los 16 trees, but I still have no idea how to solve any of the bugs. I'll do a lot of search though.
Here is the gist I made with the logcat I took. Any help would be appreciated.
EDIT
just forgot to mention that besides RIL working, I couldn't make a call (display went black and blue led). When rebooted it, I had no signal reception at all

Vinnom said:
Hey there!
Finally tried it. I flashed just the latest build and there is what I got:
After flashing only ROM, it booted, but nothing was drawn at the display. Ok, that was expect
Then I wiped system and data again, flashed the build and both of the other zips (from the first build folder)
It booted fine, RIL was working at start, wifi ok. Many other things couldn't be tested, because randomly (one time taking photos, other when scrolling settings, other when trying to test bluetooth) screen went black the blue led got lit up.
I took a logcat only with errors and it seems there is a lot to fix. Still today (just a lot later today, I have to work) I'm gonna fetch los 16 trees, but I still have no idea how to solve any of the bugs. I'll do a lot of search though.
Here is the gist I made with the logcat I took. Any help would be appreciated.
EDIT
just forgot to mention that besides RIL working, I couldn't make a call (display went black and blue led). When rebooted it, I had no signal reception at all
Click to expand...
Click to collapse
Also to the list of bugs: personally, my phone did not work with a SIM card, constant crash of applications. The YouTube crash, the camera does not take a photo (camera stock), after restarting, the fingerprint disappears (it is not deleted from memory, but it can only be unlocked if you make a new fingerprint) Any heavy application will crash after a while

Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x

penk3 said:
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
Click to expand...
Click to collapse
Disable out sim card

AssasinAkindinov said:
Disable out sim card
Click to expand...
Click to collapse
ye, phone in airmode workrd normally,

AssasinAkindinov said:
Also to the list of bugs: personally, my phone did not work with a SIM card, constant crash of applications. The YouTube crash, the camera does not take a photo (camera stock), after restarting, the fingerprint disappears (it is not deleted from memory, but it can only be unlocked if you make a new fingerprint) Any heavy application will crash after a while
Click to expand...
Click to collapse
penk3 said:
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
Click to expand...
Click to collapse
Sorry guys, no mean to be rude here, but this thread is for development purposes. My point in posting was to give a logcat and receive help to try and fix the bugs I found. I know that when possible, #Henkate gonna take a look and give some directions, so work can be done. So, if you wanna test and see if the rom works for you, that's fine, but provide logs, please. It's good to have other logs and be able to compare if the bugs are the same and I think it can help development a lot (no need to flood with logs either, be reasonable).

Unbrick no screen.
To repair the phone (when there is more image) it must start in fastboot mode and then flash boot image) wait for the phone to go off or remove the battery. When it is off plug the usb cable c on your huawei nova and the phone will show that the phone is charging. Now you can reflash another rom but not lineage os 16. Sorry i use google translation

Android 9 with jdi screen
Android 9 with jdi screen
Amazing near.
As it is known, custom firmware was not friends with the jdi screens.
And here came LOS16 on Android 9. Read reviews that it is now not usable even on smartphones with "normal" screens, what can we say about JDI
But from the realization that he had bought a new phone and having a lot of time, the thought crept in to try to put a fresh custom for total disappointment in his smartphone and quiet use of the new.
However, not everything is so simple. After the first launch, the screen began to flicker well, I thought everything had arrived, now it will get dark and the sensor will fail. Cured with just one reboot. more of this did not happen.
Sim cards did not pull out (I have 2 of them), some wrote that because of them there were some problems crashing and rebooting the system (I don’t have that)
After a night out, the interface began to respond with a delay of 0.5 seconds. (It was cured by a complete reboot) ..
Quickstep launcher is often closed with an error
The camera does not remove the drain, installed from the playlist of the market works without comments.
The navigation bar disappeared after a telephone conversation, when the interlocutor first completed the call (It was decided to reboot)
Vkontakte application crashes, but I use Kate Mobile, it flies with a bang.
YouTube crashes
The sound from the conversational dynamics is quiet, I think you can fix it in the mixer_paths but this is not exactly
Waiting for the moment until the screen fails.

All right, testing 9 android is over!
Discharged the battery to 0, the phone turned off, when turned on, the painfully familiar symptom with the diagnosis "JDI", no image, the screen backlight is on.
Hope no more. I return the phone to the stock and sell it, turn to Meizu pro 7. Thank you all!

R0mi4 said:
All right, testing 9 android is over!
Discharged the battery to 0, the phone turned off, when turned on, the painfully familiar symptom with the diagnosis "JDI", no image, the screen backlight is on.
Hope no more. I return the phone to the stock and sell it, turn to Meizu pro 7. Thank you all!
Click to expand...
Click to collapse
Ты все посты будешь переводить и сюда кидать?) (It is joke)

How To Guide Unlock BL on Realme GT2 RMX3311(GDPR)

First thanks to the creator of the script, original post here! I just systematized the steps:
What you need to have - PC(windows or linux), USB cable, and battery above 60%.
1. Download the starberryperl.
2. Download the deeptesting-junk.pl script.
3. Start the "perl command prompt" (it should be the first result when you type "perl" in window's search box) or just standard CMD.
4. Inside the command prompt change to the directory where you had downloaded the script, example:
Code:
cd C:\Users\Admin\Downloads\RMX3311_Unlock
5. Then change to UTF-8 with:
Code:
chcp 65001
6. Run the commands and follow the instructions from the github page. Take care to replace the dummy SERIALNM/HHH... and IMEI1NUMBERHERE/DDD... with your actual serial number and IMEI1!
Quote of the steps:
- Go to Settings/About Device/Status and copy Serial number and IMEI 1
- Then run in the command prompt:
Code:
perl deeptesting-junk.pl pcb 0xSERIALNM imei IMEI1NUMBERHERE cmd applyLkUnlock
- If the answer is
Code:
{"resultCode":0,"msg":"SUCCESS"}
, continue with
Code:
perl deeptesting-junk.pl pcb 0xSERIALNM imei IMEI1NUMBERHERE cmd checkApproveResult
- If the answer is somethink like
Code:
{"resultCode":0,"msg":"SUCCESS","data":{"unlockCode":"0345af...lots of hexdigits"}}
then go to next step.
7. Now follow the official guide how to unlock.
I did it on RMX3311_11.C.10_EU_202303171905 and work fine, the orange warning at boot is there(about unlocked BL).
The attachment contain the script and the apk from links above.

Backing everything up and going to try it right now, so pissed at Realme for locking us out of the Device.
I don't even care if it bricks anymore, gonna report if it works.
//It's 04:14 am, and it worked. I've followed the Instructions, but had the problem, that the device wasn't getting recognized in fastboot mode.
Problem: Phone does not get recognized in fastboot mode on Windows System
That is because the OnePlus Fastboot USB Drivers are NOT SIGNED!
Solution:
You have to restart Windows with advanced startup settings, and deactivate driver signing. So that Windows trusts unsigned drivers.
Then you can restart Windows in that mode, Settings -> windows update -> advanced options -> reset options -> advanced restart.
Go to advanced boot -> deactivate usb driver signing (option 7), start the pc with that option.
AND THEN you can boot your device into fastboot mode, go into your drivers and if it's still coming up as unrecognized, right click it and update it's drivers manually with the oneplus drivers.
Then it should work for you, too. Gave me lots of Headaches.
Thanks for the Guide @b0nb0n3v
/edit: linking here, i've uploaded the boot.img and Oneplus drivers that i used for fastboot mode.
"This phone model does not support deep testing." Is it possible to bypass that screen in the Realme's deep testing app?
Update: after a break for a couple of days, this appears to work again. But probably not for long -- so better try it if and while it's still up ;-) I was able to do just that (and unlock the bootloader on my phone) some two months ago (in...
forum.xda-developers.com

Tried and worked perfectly here! Huge thanks to the creator of the script and the guide!

Oh wow, can we get some development for this device now xd

This is great news! Thank you for posting this!

Worked for me too ! What now ? There arent many ROM available. I need to flash a rom with Call recording. What should I do ? Also is there a way to root ?

Fixed my call recorder issue with BCR module for magisk. Working perfect.
Last thing is battery life. Hope it will be fixed with custom roms.
This is really the worst phone i ever had, with bad battery life an Locked bootloader.

Hi,
I am having trouble with google pay not working because of root i guess. I already cleared cash and had it working twice, but after a while it somehow notices the root and stops working. What am i doing wrong here.

I had similar issues, I've tested if the device passes safetynet and it failed. I've solved it by loading a magisk module, universal safetynet fix 2.4 from here: https://github.com/kdrag0n/safetynet-fix/releases
Now my banking apps and NFC payment work fine. Make sure to put all banking apps in magisk denylist.

wizard8400 said:
I had similar issues, I've tested if the device passes safetynet and it failed. I've solved it by loading a magisk module, universal safetynet fix 2.4 from here: https://github.com/kdrag0n/safetynet-fix/releases
Now my banking apps and NFC payment work fine. Make sure to put all banking apps in magisk denylist.
Click to expand...
Click to collapse
Did the same and it worked a while. I made it work twice, but both times it stopped working after using it a few times.

karayemis said:
Did the same and it worked a while. I made it work twice, but both times it stopped working after using it a few times.
Click to expand...
Click to collapse
I noticed that Play-services is being removed uit denylist by magisk by its self. That mught be the issue

Mine is also unchecked, no issues with banking apps, NFC payments or safetynet. Make sure you select every option under every app so that the blue bar is full and also rename/hide magisk app. Does it pass safetynet?

Yes it passing the test,but somehow play services is being removed from the denylist by its self. I have to select it each time. Also I see that you selected a lot is there any reason for that. I only selected Google Play, play services, Google Pay and wallet

Besed in latest news from realme they stop temporary unlocking for all, to upgrade the server and may be will fix this "exploit"/method. So who unlock it till now is lucky.

Doesn't work anymore for me. Script is working, deep testing app is successfully approved, but the "Start deep testing" button doesn't work as intended, it reboot the phone, show a fastboot message for a split second, and boot to the OS. Fastboot reboot bootloader/fastboot does the same. After reboot, OEM Unlock is automatically activated tho, so it's still doing something.
I've successfully unlocked another GT2 (EU) two days before they did their server "upgrade", so there is definitly something wrong/patched, or maybe the upgrade isn't done yet.

Lightning- said:
Doesn't work anymore for me. Script is working, deep testing app is successfully approved, but the "Start deep testing" button doesn't work as intended, it reboot the phone, show a fastboot message for a split second, and boot to the OS. Fastboot reboot bootloader/fastboot does the same. After reboot, OEM Unlock is automatically activated tho, so it's still doing something.
I've successfully unlocked another GT2 (EU) two days before they did their server "upgrade", so there is definitly something wrong/patched, or maybe the upgrade isn't done yet.
Click to expand...
Click to collapse
They said they'll try to bring back the applications by next week, wait till then

Lightning- said:
Doesn't work anymore for me. Script is working, deep testing app is successfully approved, but the "Start deep testing" button doesn't work as intended, it reboot the phone, show a fastboot message for a split second, and boot to the OS. Fastboot reboot bootloader/fastboot does the same. After reboot, OEM Unlock is automatically activated tho, so it's still doing something.
I've successfully unlocked another GT2 (EU) two days before they did their server "upgrade", so there is definitly something wrong/patched, or maybe the upgrade isn't done yet.
Click to expand...
Click to collapse
Not working for me too, all working but when you click on the "Start deep testing" it reboot and appear the fastboot for a second a reboot instantly on the os.
Waiting next week maybe someone find something

BR4UTAL said:
They said they'll try to bring back the applications by next week, wait till then
Click to expand...
Click to collapse
Any update?

Luigi2201 said:
Any update?
Click to expand...
Click to collapse

Based on this chat, may be this is the end of global BL unlock.