yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Oswald Boelcke:
@bbilal

Welcome to XDA. I hope you'll always get the support you require.

However, prior to your next posting please read the guidances that are stuck on top of every forum like

Note: Questions go in Q&A Forum

If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...

xdaforums.com

and the others. I've moved the thread to Android Q&A. Thanks for your cooperation.

However, I've also removed the video link as it promotes a paid application/service. Quotation from the video page:

Regards

Oswald Boelcke

Senior Moderator
[Android Q&A, Help & Troubleshooting] matchi:
View attachment 5841713
[Android Q&A, Help & Troubleshooting] w1007_k:
Bro, can you share the application with me?
[Tilt, TyTN II, MDA Vario III General] nathanofseattle:
I recently installed the eOS 4.888.FiRe ROM on my Tilt and it has been working nicely. I noticed some additional settings that weren't available to me when I was using the stock HTC ROM. What is "HSDPA" and "AGPS"? And will it cost me to leave these turned on? I notice when I turn on HSDPA, I see a an "H" icon at the top rather than the usual "3G" icon.
[Tilt, TyTN II, MDA Vario III General] RizwanKhan:
what is google???

anyways simple answer:

hsdpa is a form of data connection which is faster than 3g.

agps stands for assisted gps. it is same as normal gps except that agps uses a server to cut down on the time to requires to get ur location using gps.

both won't cost u anything extra but ur carrier does need to support them for u to be able to use.
[Tilt, TyTN II, MDA Vario III General] nathanofseattle:
Thank you. I just wanted to know if they both won't cost me anything extra. You never know these days with Cellphone companies. I turned on both HSDPA and AGPS. So far my calls have been going through just fine and my navigation software continues to function normally.

How do I know if my carrier (AT&T) supports HSDPA and AGPS? I hate having to call customer service to ask so I'd rather ask here.
[Tilt, TyTN II, MDA Vario III General] theo44001:
I used KaiserTweak to set my phone to HSDPA. I am an AT&T user. It's worked fine. No additional charges. I don't use AGPS so I can't respond to that part of your question.
[Tilt, TyTN II, MDA Vario III General] nathanofseattle:
Thanks for your response. I just use it for voice calls anyway. Do you see any improvements? Or is it specifically if you subscribe to a data plan? And do you also see an "H" icon at the top rather than a "3G" icon?
[Tilt, TyTN II, MDA Vario III General] RojasTKD:
HSDPA has to do with you data connection, so unless you have a data plan you really won’t see the benefit.
[Tilt, TyTN II, MDA Vario III General] udi1:
Google

n. company that was founded in 1998 at Stanford University by Larry Page and Sergey Brin and serves as a search engine on the Internet

x

google

v. (Computers) search for data on the Web using the search mechanism Google; search on the Internet for particulars relating to new or likely to be girlfriend or boyfriend

:D:D
[Tilt, TyTN II, MDA Vario III General] rfarnell:
HSDPA doesn't cost anything to activate, but if you are on a restrictive tariff it is a lot easier to run up over usage charges.

In the UK you need to usually be paying at least £30 a month to have the unlimited mobile broadband and e-mail. I would personally check your contract before you let the HSDPA run loose.

Rob
[Tilt, TyTN II, MDA Vario III General] kbcherry:
As mentioned multiple times, neither HSDPA or AGPS will cost you anything. You will know if you are in an area that has HSDPA because of the H icon. If it goes back to 3G then ATT does not have HSDPA in that area. If it goes to E then you are back on Edge. As also was mentioned, neither of these have any impact on your phone calls. HDSPA = Data and AGPS = using the cell towers or the internet to help you lock on your GPS location quicker.

And yes, if you had used google to search for this you would have probably got a better explanation in a less amount of time.
[Realme 7 Guides, News, & Discussion] flandolf:
Hi everyone!

Just wanted to share some steps in case you brick your Realme.

DISCLAIMER: I AM NOT RESPONSIBLE FOR ANY DAMAGES

Some prerequisites you will need:

mtkclient + python

spft (sp flash tool)

ofp extractor

Your stock rom in OFP format.

Step 1. Download all of the things mentioned above.

Step 1a. Make sure your device is turned off. DO NOT PLUG IT IN.

Step 2. Install mtkclient using the guide on GitHub.

Step 3. Run

$ py mtk payload

in your terminal.

Step 3a. When it says ***waiting for device*** hold both volume buttons and plug in your device.

This will enter BROM mode.

Step 4. Extract and open ofp extractor and extract your ofp.

Step 5. Open SPFT and click DOWNLOAD ONLY (do not I MEAN DO NOT PRESS FORMAT ALL.)

Step 6. In scatter, look for your scatter file. It should be (MTxxxxScatter.txt etc) Then select it.

Step 7. Select your auth file if you have one.

Step 8. Press Download and if the progress bar starts going the flash is going. DO NOT UNPLUG.

Step 9. Reboot after it says 'Download Ok'

Step 10. Enjoy your unbricked device!

NOTE In most cases the rom will be for android 10. Update if required through OZIP.

​
[Realme 7 Guides, News, & Discussion] czaroslaw:
I cannot download with SPFlash. Error 0xC0060001. I'm sure that I have done all steps correctly including this tutorial:

Realme 7 Unbrick

Of corse I'm doing everything with Realme 7 5G RMX2111EU.

I had problems with disabling protection as follows but I think it finally succeeded.

1. bypass_utility-v.1.4.2 gives error

[2022-05-10 22:53:51.684562] Waiting for device
[2022-05-10 22:53:59.780976] Found port = COM4

[2022-05-10 22:53:59.921376] Device hw code: 0x996
[2022-05-10 22:53:59.921376] Device hw sub code: 0x8a00
[2022-05-10 22:53:59.921376] Device hw version: 0xca00
[2022-05-10 22:53:59.921376] Device sw version: 0x0
[2022-05-10 22:53:59.921376] Device secure boot: True
[2022-05-10 22:53:59.921376] Device serial link authorization: False
[2022-05-10 22:53:59.921376] Device download agent authorization: True

[2022-05-10 22:53:59.921376] Disabling watchdog timer
[2022-05-10 22:53:59.936976] Disabling protection
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win
error: A device attached to the system is not functioning.\r\n\n'
[2022-05-10 22:54:01.028978] Payload did not reply
Press any key to continue . . .

2. mtk-client gives error:

....Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader

3. MTK Meta Utility v37 success

Waiting for mtk usb device... ok
BootMode : BootRom[COM4]
DriverName : MediaTek USB Port_V1633
DriverPath : usb\vid_0e8d&pid_0003\5&278a3c80&0&2
DriverID : wdm_usb
DriverVersion : 3.0.1504.0
DriverDate : 1-22-2015
InfPath : oem28.inf
ProviderName : MediaTek Inc.
Connecting to BootROM......
● Chipset MT6853
● Identifier Dimensity 720/800U 5G
● Info 8A00_CA00_0000_Mouton
● MEID:3EFFEA531AB22A57AB0240D8421E92B4
● SecCFG SBC+SDA
Disable BRom protection...
MTK Auth Disable(SLA/DAA) success!
now you can use SP Flash Tool or any MTK Tool

4. MTK Auth Byoass Tool v6.0.0.1 success

Waiting for mtk usb device... ok
BootMode : BootRom[COM4]
Sync with bootrom started...
● Chipset MT6853:Dimensity 720/800U 5G
● Code Mouton
● Hw Sub 8A00
● HW Ver CA00
● SW Ver 0000
● SecCFG SBC+SDA
Disable brom protection.
Bypass Payload ACK = 0xa1a2a3a4
MTK Secure Boot Bypasss success!
now you can use SP Flash Tool or any MTK Tool
[Realme 7 Guides, News, & Discussion] flandolf:
What more.info about the error code do you have? Also are you on windows because spft buggy on linux
[Realme 7 Guides, News, & Discussion] czaroslaw:
BROM ERROR : STATUS_BROM_CMD_STARTCMD_FAIL (0xC0060001)

Windows 7

SP_Flash_Tool_v5.2208_Win
[Realme 7 Guides, News, & Discussion] flandolf:
Then you haven't bypassed brom, try mtkclient again and don't unplug your device
[Realme 7 Guides, News, & Discussion] czaroslaw:
Mtk client gives error: Preloader - [LIB]: ←[31mStatus: Handshake failed
[Realme 7 Guides, News, & Discussion] flandolf:
Install mtk drivers and Libusb, also pyserial
[Realme 7 Guides, News, & Discussion] czaroslaw:
All above mentioned was installed. I tried different pack from droidwin and I get this:

Port - Device detected :)
Preloader - CPU: MT6853(Dimensity 720 5G)
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212000
Preloader - Var1: 0xa
Preloader - Disabling Watchdog...
Preloader - HW code: 0x996
Preloader - Target config: 0xe5
Preloader - SBC enabled: True
Preloader - SLA enabled: False
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: True
Preloader - Mem write auth: True
Preloader - Cmd 0xC8 blocked: True
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
Preloader - ME_ID: 3EFFEA531AB22A57AB0240D8421E92B4
Preloader - SOC_ID: DAA82CB9D5E03916132A0BE2A479C0CC0FFD2B10
1E00173F9EA9FCB44C88FC8E
PLTools - Loading payload from mt6853_payload.bin, 0x264 bytes
PLTools - Kamakiri / DA Run
Kamakiri - Trying kamakiri2..
Kamakiri - Done sending payload...
PLTools - Successfully sent payload: D:\Apk\MTK Bypass Tools\mtkclient-main\mtkc
lient\payloads\mt6853_payload.bin
[Realme 7 Guides, News, & Discussion] SubwayChamp:
Be sure to use in SPFT, in connection check USB full speed, and in general settings, uncheck the options Check LIB DA Match and Storage Life Cycle Check.

If this doesn't work, try to flash only preloader firstly, and then flash the rest, upload some screenshot if the error persists.
[Realme 7 Guides, News, & Discussion] flandolf:
That means it worked
[Realme 7 Guides, News, & Discussion] czaroslaw:
Ok. Bootloader is unlocked but now I have dm-verity corrupted.

I cannot enter recovery mode. Some error flashes on screen and immediately reboot. I cannot even read this. I have found that it might be:

the serial is not matched

fastboot_unlock_verify failed

I cannot enter fastboot mode. It gives:

Orange state

The device is unlocked and cannot be trusted

and then restarts

Normal boot gives:

dm_varity corruption

Your device is corrupted

It won't be trusted and may not work properly

Press power button to continue

Then pressing power button boots into system correctly and the phone is working.

How to get rid of these errors? How to recover access to recovery and fastboot mode? Should I flash some partitions again from stock formware?

Should I install PBRP using mtkclient as in this guide?

Install TWRP Recovery without using Fastboot Mode [MediaTek]

And then should I root it using patched Magisk as follows?

Root MediaTek Devices without using Fastboot Mode [via MTK Client]

There is some info about patched version of Magisk for MTK devices. Should I use it?
[Realme 7 Guides, News, & Discussion] flandolf:
do

fastboot flash --disable-verity --disable-verification vbmeta {your vbmeta.img}
[Realme 7 Guides, News, & Discussion] flandolf:
If it says DM-verity error, reflash with spft and on mtkclient, relock BL by using

Py mtk da seccfg lock
[Realme 7 Guides, News, & Discussion] czaroslaw:
I cannot enter fastboot mode so I cannot use fastboot flash.

Second advice: I do not want to lock bootloader.
[Realme 7 Guides, News, & Discussion] flandolf:
If you are able to boot to stock, do ADB reboot fastboot
[Realme 7 Guides, News, & Discussion] czaroslaw:
Does not work. It gives the same as VolUP+PWR. Orange state message and reboot.

I cannot enter fastboot in any way.

Should I flash something in brom mode? Recovery partition? Something else to get rid of dm_varity?
[Realme 7 Guides, News, & Discussion] flandolf:
Reflash firmware then try, idk this hasn't happened to me
[Realme 7 Guides, News, & Discussion] flandolf:
Also send the link of the firmware U got
[Realme 7 Guides, News, & Discussion] czaroslaw:
I have RMX2111_11_C.11. Updated via OTA. I cannot find such version firmware file.

The newest I found is:

RMX2111GDPR_11_C.09 EDL mode
[Realme 7 Guides, News, & Discussion] flandolf:
Relock bootloader and try using this to reunlock bl
[Realme 7 Guides, News, & Discussion] czaroslaw:
Locking bootloader at this state using mtkclient will work?

In depth test was not working for me as I have incorrect region of device. To use it I will have to change region to IN but it is not possible in A11 RUI2.0 (dialing codes does not work). The only way is downgrade to A10 RUI1.0. That is why I tried mtk-client.
[Realme 7 Guides, News, & Discussion] flandolf:
I am not even from India and this works, au region for me... The only way to get rid of DM-verity is to get to fastboot, which idk how U can't access
[Realme 7 Guides, News, & Discussion] flandolf:
Also try downloading stock firmware from a10 and update back to 2.0 with ozip
[Realme 7 Guides, News, & Discussion] czaroslaw:
In depth test gives me "Your device is not supported".

Maybe your region is supported by IDT. EU in general is not supported.

I will try again. If not I will downgrade to A10.
[Realme 7 Guides, News, & Discussion] czaroslaw:
And one more question.

Some tutorials for unbricking/downgrading (generally for flashing full firmware) say that one should untick following partitions:

opporeserve2

cdt-engineering

mycustom

special-preload

userdata

super

Is it necessary or these partitions just does not affect uploding full firmware and sometimes is required when error occurs?
[Realme 7 Guides, News, & Discussion] flandolf:
I recommend flashing all of them, but if your BL is locked U need to untick opporeserve. I suggest you flash the rest
[Realme 7 Guides, News, & Discussion] czaroslaw:
Ok. Bootloader unlocked with In depth test.

But now I'm stucked on Android 10. RMX2111_11_A.32 and no updates available (tried with vpn also). And I cannot find any OTA firmwares to download.

Any solution?
[Realme 7 Guides, News, & Discussion] flandolf:
Software Update - realme Support | realme India

Update the latest software version on your realme phone.

www.realme.com

Try this and download A.35 which should let u update to android 11 after
[Realme 7 Guides, News, & Discussion] czaroslaw:
Cannot be installed. Propably I cannot update RMX2111EU (europe) with RMX2111PU (Brazil).

edit: uptade was possible in recovery mode not via file manager. A35 installed but still cannot update to android 11 ;)

I have found stock RMX2111GDPR_11_C.09_2022011518240000.zip so I will try to flash full firmware.

But now I have another problem.

I cannot connect with Modem Meta. All drivers installed.

When trying to connect without pressing any buttons, Modem Meta stuck on boot. The phone shows charging screen and no Ports in device manager is found.

When trying to connect with volup+voldown. First Mediatek USB port is found. Modem Meta passes boot stage. Then Modem Meta stuck on kernel mode. When I release buttons, Preloader VCOM port is found and the phone is displaying coloured screens (red, yellow, blue). Same as in this video. Modem Meta show error cannot find Meta com driver.

How to boot in meta mode and force Modem Meta to work?
[Realme 7 Guides, News, & Discussion] SubwayChamp:
You don't need Meta mode to flash a stock ROM, Modem Meta is a tool to write the IMEI, you need to enter to BROM mode instead, you should follow a tutorial like this https://xdaforums.com/t/guide-unbri...india-6s-using-spflash-tool-for-free.4222027/
[Realme 7 Guides, News, & Discussion] czaroslaw:
I know how to flash firmware.

But I have to also get access to write IMEI. I need to restore it. I have no any backup. Only labels on phone box.

I tried to read nvram but I cannot find any imei stored explicitly.
[Realme 7 Guides, News, & Discussion] SubwayChamp:
Ok, It wasn´t clearly which the goal was, anyway, what steps did you try to enter to Meta mode? Also, did you have available fastboot or recovery?
[Realme 7 Guides, News, & Discussion] czaroslaw:
Yes, I have fastboot and recovery mode available.

To enter meta mode I used MtkMetaUtility. It reads meta info and shows that meta mode is active. Preloader com port is found and the phone displays coloured screens. To boot to meta I need to press volUp+volDwn and connect cable.

Connecting without pressing buttons does not work.

The same for Modem Meta. I have to press all buttons than the programs complete boot stage. The phone start displaying coloured screens. But the program is stucked in kernel stage and after a while shows meta com driver port not found.

I have also tried to enter meta mode via mtkmeta utility and then connect with modem meta. It doesn't work. But I think it is obvious because modem meta requires power on and boot stage.
[Realme 7 Guides, News, & Discussion] SubwayChamp:
There are some confusing points here that, either need a clarification or is just a typo or just me not understanding, you are saying first "To boot to meta I need to press volUp+vo..." and then "The same for Modem Meta..." But it results that both, meta mode and Modem Meta (how it's called the tool) refer to meta mode.

Across the boot stage process, the device doesn't need to power on.

From my experience, I have Realme 7, Modem Meta detected the device without pressing a button while in RUI1, and by pressing both volume buttons, while in RUI2, this is because of the kernel.

You have here two options, basically, to get the tool running and detecting the device, if you connect your device power off, you have to choose the option Smartphone, and if you, successfully, sent your device to meta mode, then you have to check the option more DUT in meta mode, the process has to be very quick, also check USB (if you don't have an UART cable) and check exactly the port where your device is attached, in my case it didn't work auto connection. Modem Meta v10.2044 was the tool that worked for me, for almost all the process.
[Realme 7 Guides, News, & Discussion] czaroslaw:
Ok. I will explain step by step what am I doing and what is the result.

RMX2111_11_A.35PU, unlocked bootloader via In depth test and rooted.

All required mtk drivers installed, libusb installed and com port filtered, UsbDk installed.

Drivers seems to be correctly installed. I was able to flash full firmware in brom mode. Mtkclient was able to bypass authentication.

1. Modem Meta v10.2044.0.2

Settings: smartphone, usb

a) Press connect -> plug usb cable without pressing any buttons -> phone turns on -> shows orange state warning -> then boots and shows charge screen -> Hid compilamt device is found in devicemanager -> modem meta get stuck on boot stage

b) Press connect -> plug usb cable with VolUP+VolDN -> phone turns on -> modem meta passes boot stage -> Mtk USB Port is found -> if buttons are still pressed, this device is repeatedly mounted/unmounted -> release Vol buttons -> shows orange state warning -> Mtk Preloader VCOM Port is found -> then boots and coloured screen are shown (red, blue, yellow) -> modem meta get stuck on get kernel port stage and shows error: cannot find meta usb com port (see file attached). I attach logs for this session.

2, MaUi Meta v10.1816.0.1

Settings: smartphone, usb

a) Press connect -> plug usb cable without pressing any buttons -> phone turns on -> shows orange state warning -> then boots and shows charge screen -> Hid compilamt device is found in devicemanager -> maui meta get stuck on boot stage

b) Press connect -> plug usb cable with VolUP+VolDN -> Mtk USB Port is found -> maui meta still in boot stage ->if buttons are still pressed, this device is permanently mounted -> release Vol buttons -> phone boot normally to system -> maui meta still in boot stage

3. MTK Meta Utility v37

a) read meta info -> plug usb cable without pressing any buttons -> phone turns on -> shows orange state warning -> then boots and shows charge screen -> Hid compilamt device is found in devicemanager -> mtkmetautility still waiting for device

b) read meta info -> plug usb cable with VolUP+VolDN -> Mtk USB Port is found -> utility found the device and reboots to meta mode -> utility is waiting for meta mode device -> buttons are released -> Mtk Preloader VCOM Port is found -> utility read merta info (see file attached)

c) the same procedure as for b) I can apply for reboot meta -> the phone boots into meta mode and shows coloured screens

Why Modem Meta or MaUi Meta do not work? MTKMetaUtility proves that the phone correctly boots into meta mode. Should I install some specific drivers?
[Realme 7 Guides, News, & Discussion] SubwayChamp:
Maui Meta never worked at all but as per Modem Meta, you have to send device to meta mode, and then you have to check the option more DUT in meta mode, the process has to be very quick, also check USB (if you don't have an UART cable) and instead of Auto connection, check exactly the port COM where your device is attached,
[Realme 7 Guides, News, & Discussion] czaroslaw:
Ok, DUT in meta mode works. The device is connected with warning, see attached file. I have no idea if this may affect imei write.

But now I have no idea how to find nvram database in stock firmware. DB from targe does not work. have no folder like system\etc\mddb.
[Realme 7 Guides, News, & Discussion] czaroslaw:
I have found where db is stored. Using MTKMetaUtility -> Dump Modem Database (meta) it gives the path:

/data/vendor_de/meta/mddb

I found there:

MDDB.META.ODB_MT6853_S00_MOLY_NR15_R3_TC16_PR1_SP_V3_P54.XML

MDDB.META.ODB_MT6853_S00_MOLY_NR15_R3_TC16_PR1_SP_V3_P54.XML.GZ

Modem meta failed to load this DB. How to fix it?
[Realme 7 Guides, News, & Discussion] SubwayChamp:
I assume that this partition is write, not read protected but...

Can you share the link for MTKMetaUtility, I will try this option and report back? For me, worked Load from Target, but, it failed in the 99 step; Failed to Write IMEI from target.
[Realme 7 Guides, News, & Discussion] czaroslaw:
Link to MtkMetaUtility

Password = mtk_meta_utility

Partition is rwxrwx--x. Here are some screenshots.

Modem Meta can read db from target. Now I noticed that in log directory it stored gz file. But it cannot load this db. I attach also log from ModemMeta.

If Modem Meta works in your case:

- do you have bootloader unlocked?

- how do you connect to modem meta? in power off state or dut in meta?

- if dut in meta how do you reboot in meta mode?

- what firmware do you have? maybe I should upgrade to Android 11?
[Realme 7 Guides, News, & Discussion] czaroslaw:
I have also used Dump NvRegions option. It dumped following files:

md1img.bin

nvdata.bin

nvram.bin

opporeserve2.bin

proinfo.bin

I have found IMEI in opporeserve2. Two the same sections and one showing that something was trying to change IMEI? I don't remember what I was doing that day but I think I was trying to use adb and AT command to change imei. Without success.

In these two identical sections there are four 15-digit numbers with 0 and 1 index. Two first numbers are the same. Next two are IMEI. I have no idea if these two identical numbers are correlated with IMEI.

I have no idea if I can simply edit this partition to restore IMEI. This partition is 128M size. In stock firmware this partition is only 5M and it does not overlap the regions where I found IMEI.