yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4a Guides, News, & Discussion] DiamondJohn:
On my Rooted Pixel 4a, I can use:

Fastboot - I flashed the latest update firmware as well as the rooted boot image

ADB Over WiFi - This is the most comnon way I connect for ADB

ADB While the Android OS is running

What I cannoit get woirking is ADB while in recovery mode,

If I go to recovery and connect via a high quality cable, I can see the device with

adb devices

But none of the below works

>adb shell
error: closed

>adb connect 091XXXXXXXX490
cannot resolve host '091XXXXXXXX490' and port 5555: No such host is known. (11001)

>adv shell 091XXXXXXXX490
error: closed

What am I doing wrong? how can I connect in recovery?
[Google Pixel 4a Guides, News, & Discussion] WillisD:
Stock recovery?
[Google Pixel 4a Guides, News, & Discussion] DiamondJohn:
Yes.
[Google Pixel 4a Guides, News, & Discussion] a1291762:
I always thought that adb from recovery was a TWRP thing?

I did adb reboot recovery. My phone has an Android on its back, with "No command" on the screen.

$ adb devices
List of devices attached
xxx unauthorized
$ adb shell
adb: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

I got the same thing booting to recovery by holding Vol down at boot.

Booting to rescue (another option on the boot menu) got me the same thing on my screen and the same symptom you saw.

$ adb devices
List of devices attached
xxx rescue
$ adb shell
error: closed

Are you sure this is supposed to work with the stock recovery?
[Google Pixel 4a Guides, News, & Discussion] DiamondJohn:
Actually no, i guess it was an assumption, and the response to adb devices, gave me further hope.

However,, it does respnod to ADB. As is seen, it provides a list of devices. But, maybe one can't shell out while in stock recpvery. Which goves me an idea, maybe we can send commands from the command window in windows/linux. eg adb shell ls But it wouldn't make sense that it would allow root, which negates what I wanted to be able to do in the first place. ie recovery from a bootloop by selectively editing the data partition. in my previous case, it was to disable a single magisk module.
[Google Pixel 4a Guides, News, & Discussion] a1291762:
Yeah, it certainly seems to be speaking adb...

I didn't think to try...but maybe adb push and pull work?
[Xperia Z2 Tablet Q&A, Help & Troubleshooting] nicky-xda:
i've found it: solved.

On the stock v6.0.1 my z2 has a charging bug: not possible to charge to 100%, at 90% led blinking, display stays turned on, beginning to discharge.

Apparently there is no such bug on the older v4.4.x, that's why i want do downgrade.

Can someone help and post a link to the international / german version?
[Realme 6 Guides, News, & Discussion] mercan01:
Thank you for your efforts. Can you add the decrypted A34 file?
[Realme 6 Guides, News, & Discussion] daeSundae:
Hello! I wasn't able to find factory package (ofp) files for any version that makes sense for versions starting with A. (EU). There are A11 and A08 which according to update trackers, did never exist and the A.11 package is %50 larger than all the other files weirdly. I have contacted owner of some sites that do upload files like these and they asked for money. If it's a resonable price i will get it, decrypt it and upload here! If you were able to find any versions starting with A, feel free to message me on telegram (@ctivity) or email me!
[Realme 6 Guides, News, & Discussion] mercan01:
Hi, it gives an error when I do unbrick with a different version, when my phone was brick the version was A34.
[Realme 6 Guides, News, & Discussion] daeSundae:
Hello again. According to the site you have just sent, A.11 is the first update to EU version. I was thinking it was a mistakenly uploaded file, since userdata partitions are for some reason 9gb with this one instead of 3. If you Downgrade to A11 using SPFLASH tool and this guide and after that install any version included here using recovery, it will work. Unfortunately, these files you sent in the link are ozip files and update packages while ofp files are firmware packages and they include everything. There are only 2 ofps -decrypted and not decrypted- available for now starting with A(EU), A08 (first ever firmware for EU) and A11(first update to EU version).
[Realme 6 Guides, News, & Discussion] mercan01:
Hello again. Yes, I noticed there was an ozip file and deleted it.
[Realme 6 Guides, News, & Discussion] cmfan:
First of all, thank you daeSundae for posting this info here!

Have you actually tried to flash the decrypted A.11 version? I did according to your guide. Everything went fine including the green checkmark after successful flash.

Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device.

Linux shows a device that identifies as "18d1:d001 Google Inc. Nexus 4 (fastboot)".

Fastboot does not recognize the device, adb however does, showing the correct S/N and state unauthorized, thus it doesn't accept any commands.

So the USB controller seems to be still alive, but nothing more.

To be clear: I don't blame you in any way, I'm just trying to provide information to step forward! So, what was your experience on A.11?
[Realme 6 Guides, News, & Discussion] daeSundae:
Hello! I'm sorry for the inconvenience I have tried flashing A11 file and it caused several problems just like in your case, however if you didn't select "Format All+ Download" mode you should be able to recover your phone. So, I had the exact same issue today and due to that I will be removing the A11 file from the links. Also, never forget to select Download Mode only! Several people bricked today and their IMEIs, Serial Numbers are all gone! Never select anything else than Download Mode!

So the solution is to download B53 decrypted files, load the scatter and untick listed partitions

opporeserve

,cdt-engineering,

mycustom,

special-preload,

userdata,

super

and then start the flashing in download mode. Now, you might be wondering "How am I going to go into the download mode again?" It's very simple. All you have to do is to keep pressing on Power and Vol- for some time and then, connecting to the pc with both volume buttons pressed while brom.bat is running. If you get an error, just reinstall device filters and that should fix the problem, then you can start downloading. After downloading these partitions to the phone, you will be able to see a boot animation and as well as a realme logo. Reboot to recovery, power of your device and then go into download mode again and flash userdata, dtbo and super partitions this time around. It should boot into system. However, the version will be B.53 but you can use the latest ozip (A.48), flash it from recovery and then format your data. It will bring you back to EU version.
[Realme 6 Guides, News, & Discussion] daeSundae:
So, i just read your reply again.

"Then I held the phone's power button until it vibrated once, like a normal boot up. However the phone remained black and seems nearly completely dead now. It doesn't react to any key combinations (including Vol+-) and Windows reports a malfunctioning unrecognizable device."

i dont think it's an issue caused by the device. Can you install oppo drivers from this link and let me know what happens afterwards? Or if you're fast enough you might prefer going into device manager by right clicking on Windows button and uninstall it's driver? I will also request you to start from step 2 to ensure installing drivers. I had the same black screen but my Windows was able to detect the Download Mode when i connected while both volume buttons pressed.
[Realme 6 Guides, News, & Discussion] daeSundae:
Hello! I have uploaded B23 files both on google drive and mega. It should work for you, it is working for me at the moment. I also was on A48 firmware and both B23 and B53 versions worked without a problem.
[Realme 6 Guides, News, & Discussion] cmfan:
Well, good to hear, that your phone survived the faulty firmware. Although I select Download only of course I can't reach download mode any more. It is completely dead, Holding whatever combinations for even a minute doesn't have any effect. Normally you can force a reboot by holding Power and Vol+ for 10-15 seconds. If you keep holding it'll reboot, if you release both keys immediately after the screen went black it stays powered off. That's how I could escape the previous bootloop.

I've tried removing all devices and drivers and reinstalling them as per your guide, alas to no avail. My second, still intact phone (stock, unrooted), identifies in download mode as "USB serial device" on Windows and as "Mediatek Inc. MT6227 Phone" on Linux. The bricked always identifies as "Google Inc. Nexus 4 (fastboot)" throughout (buttons pressed or not).

It's a shame I didn't have the idea of unbricking with a B region firmware and flashing the A region later through recovery, because then I wouldn't have tried the untested A.11, but taken the verified route instead.
[Realme 6 Guides, News, & Discussion] daeSundae:
Well, as far as my knowledge goes BROM is burnt onto SoC and cannot fall into an inaccessible state. You should still be able to do access download mode even if that firmware was corrupt. Do you know if your phone has any charge or not? Can you try different volume and key combinations? A broken firmware shouldn't make the BROM Download mode inaccessible.
[Realme 6 Guides, News, & Discussion] daeSundae:
Oh wait. Is it identifying as fastboot? Then you should be able to (even if you don't have USB debugging authorization) use minimal ADB and fastboot tools to

use "fastboot reboot" command. Please keep pressing vol - button if you can while rebooting if it works. That should, if possible reboot you into recovery.

Also as you said, keeping pressing on power and vol+ buttons don't work in this state. In fact, in this state nothing visually works, there is no screen output and I'm actually pretty sure it's the same for begonia (RN8 PRO). You will need to ~ if it's detecting it as a fastboot device need to use minimal ADB and fastboot tools to get rid of that state. I didn't have the same issue as you though. While I was in same state, I kept on pressing on Vol - and Power buttons for around 30-40 seconds (obviously without a response from the device) and after that pressed both volume buttons and connected device to PC. Can you also try when your device powers off? Because clearly currently your device isn't powered off and cannot be powered off until the battery dies or you can somehow manage to escape from current situation.
[Realme 6 Guides, News, & Discussion] MEGAFON929:
MTK Bypass Universal

My screenshots were used in this post. I don't mind
[Realme 6 Guides, News, & Discussion] daeSundae:
I'm sorry for not letting you know Dinolek. I tried to create a guide but my Windows is Single Language and since it's not global version or something I cannot change its language. I had to find an English screenshot. If it's a problem, I'll just remove them.
[Realme 6 Guides, News, & Discussion] MEGAFON929:
No, I'm not Dinolek. I just talked to him and he accepted my instructions. Let the screenshots lie, I don't mind.
[Realme 6 Guides, News, & Discussion] cmfan:
Thank you daeSundae for helping me, I really appreciate that. So, what do we have:

Sounds reasonable and I hope it's true. :)

The phone was fully charged when it bricked, so yes, the battery will last several days I fear, esp. without driving the display.

Three buttons make 7 possible combinations. I've tried them all, pressing, holding and holding while connecting USB. No reaction at all, unfortunately.

This is kind of weird. The phone identifies as USB ID 18d1:d001 on Linux which is said fastboot device. fastboot does not see it, only adb does. But maybe it justs sees the device, lists it, but cannot communicate otherwise with it. I guess if the device was just silent (or dead) adb would assume unauthorized, in lack of any other behavior.

Window btw does not accept the device at all and lists an "Unknown USB Device (Invalid Configuration Descriptor)".

Sound also reasonable, however waiting for the battery to drain may last a very long time. I am out of ideas on how to force a power off otherwise (apart from sacrificing hardware integrity and disconnecting the battery of course)

Man, do I miss the old days when a ZergRush was all you needed to root and problems like this were solved by pulling the removable battery... :cool:
[Realme 6 Guides, News, & Discussion] daeSundae:
Can you try ADB reboot command on Linux? As it is identifying as a fastboot device?
[Realme 6 Guides, News, & Discussion] daeSundae:
If it's detecting a fastboot device, the device isn't dead. What I'm guessing is that your device is working, and on fastboot mode but since there's no display output in this state it will only show a black screen. Can you do ADB devices command? Im guessing adb reboot requires authorization though, but it's worth trying. What I will be requesting from you is to try pressing (and keep pressing on) different key combinations while device is in that state for like a minute or so, for example keep pressing on Vol- and power for a minute then switch to Power and Vol+ for a minute and then keep pressing on both volume buttons and connect device. Can you also see the results after plugging your device into charge and letting it stay for around a minute? I know these might make no sense technically, but in my opinion randomness is your best friend to get rid of situations like this..
[Realme 6 Guides, News, & Discussion] daeSundae:
Hello. again. So, i have asked few people about your situation. Conclusion is, if none of these work you will need to wait until battery wears off and device turns itself off, i'm afraid. I will ask you to not use your phone for like a day and not to keep it connected to a computer for a long time. After making sure it powered off (which, i'm guessing there is actually no way to do that) make sure to prepare the brom.bat file plug in your device with VOL+ - combo and go on. Before doing this make sure to Device Manager > Action > Add Legacy Hardware > Next > Install the hardware that I manually select from a list (Advanced) > Show All Devices > Have Disk > Choose the cdc-acm.inf > Choose Mediatek USB Port and install it to not waste time. I hope your problems will be fixed. I have confirmed that BROM mode shouldn't fall into an inaccessible state because there's no efuse.ini blown. It must be there, but you're probably stuck in a mode that doesn't allow doing anything for some reason.
[Realme 6 Guides, News, & Discussion] daeSundae:
No you didn't follow this guide. This guide says, and always did, to refrain from using format related stuff on sp flash tool.

You will NOT even be able to unlock your bootloader because you don't have IMEIs, and that's what "In-Depth Test" application sends to oppo/Realme servers to validate.

You can't just edit an NVRAM file, it requires specific tools. Even when you try editing your current NVRAM, it will be too complicated and you won't be able to flash it back to the device because there's no engineering ROM for this device.

Well, in the begging of the guide it says to not touch anything related to format on SPFlash tool.
[Realme 6 Guides, News, & Discussion] Jorycollins:
ERROR STATUS_EXT_RAM_EXCEPTION (0xC0050005)

I keep getting this error on my end even though I am using the correct firmware and following all steps here
[Realme 6 Guides, News, & Discussion] bx2nero:
What is your phone model ??
[Realme 6 Guides, News, & Discussion] Jorycollins:
rmx 2189 realme c12
[Realme 6 Guides, News, & Discussion] bx2nero:
This guide and.firmware is for Realme 6 series as mentioned. ..why are you flashing in other phones.
[Realme 6 Guides, News, & Discussion] Jorycollins:
no I just followed the steps but as for firmware I used mine rmx 2189
[Realme 6 Guides, News, & Discussion] bx2nero:
The error you are getting usually means you are flashing wrong firmware. Thats why I asked you your phone model.
[Realme 6 Guides, News, & Discussion] Jorycollins:
well I just discovered the problem is with the Realme c12 rmx 2189 ofp firmware

No matter which version of the firmware whether newer or older all give the same error for the incompatible firmware.

Hell even the kernel source is broken. In short for my particular problem it is on the side of realme
[Realme 6 Guides, News, & Discussion] daeSundae:
Updated BTP.rar

drive.google.com

Use this. it's compatible with all SoCs.

Comes with slightly different instructions, follow this

"1st one will give error, just reboot the device and go into download mode again while running 2nd bat file"
[Realme 6 Guides, News, & Discussion] daeSundae:
I don't think you're able to bypass using same utility?
[Realme 6 Guides, News, & Discussion] Jorycollins:
Bypassing goes through the problem comes when trying to flash in sp flash tool
[Realme 6 Guides, News, & Discussion] daeSundae:
Well

Are you sure you have that model? Have you checked what box says?
[Realme 6 Guides, News, & Discussion] Jorycollins:
yes Im totally sure on the model

i wouldnt wanna make a mistake like flashing the wrong files but thats just the thing there are no right files for rmx 2189

if sb else succeeds with this model then Ill try
[Realme 6 Guides, News, & Discussion] Jorycollins:
yes

yes including even when the phone was new thats one of the things I use to confirm what I bought
[Realme 6 Guides, News, & Discussion] HemanthJabalpuri:
@daeSundae

From where you got those firmwares?

I have Realme C12, I am searching for genuine firmwares.

Thanks
[Realme 6 Guides, News, & Discussion] mercan01:
look at there https://realmeupdater.com/downloads/archive/
[Realme 6 Guides, News, & Discussion] v. kumar:
bro can we use this method to revert back from latest b59 firmware in realme 6
[Realme 6 Guides, News, & Discussion] bx2nero:
Yes obviously !
[Realme 6 Guides, News, & Discussion] ashishlive4:
it's not due to software faulty ,otherwise you can't flash preloader to your flash chip
[Realme 6 Guides, News, & Discussion] daeSundae:
You literally can. Download only mode will still download the preloader to the device and do the flashing.
[Realme 6 Guides, News, & Discussion] iamrhy2917:
I have a problem in bypassinh

incorrect hw code, expected 0x813, found 0x707

how to fix this? thanks brother
[Realme 6 Guides, News, & Discussion] 0purple:
@daeSundae

I installed libusb-32 drivers, everything looks fine. However, it`s unable to detect my device. I followed guide exactly like you said. My device is Xiaomi Redmi 9C NFC (angelican)
[Realme 6 Guides, News, & Discussion] daeSundae:
I think xioami devices have different key combination to boot into BROM. You should have a check on the internet.
[Realme 6 Guides, News, & Discussion] Raj-v:
how to get MT6785_Android_scatter.txt???
[Realme 6 Guides, News, & Discussion] roberto888:
You can extract it from Stock Firmware OFP
[Realme 6 Guides, News, & Discussion] abzrajanmiguel:
BROM is always on constant error. I tried the MTK bypass rev 3 and rev 4. it gives me error "Handshaking Error"
[Realme 6 Guides, News, & Discussion] abzrajanmiguel:
Hi Thank you for this post. Can you help me with this error?
[Realme 6 Guides, News, & Discussion] abzrajanmiguel:
Still download incomplete. error 0x99256658 :(
[Realme 6 Guides, News, & Discussion] bx2nero:
Show ss
[Realme 6 Guides, News, & Discussion] Harida:
Realme 6i .. its stuck in recovery mode
[Realme 6 Guides, News, & Discussion] bx2nero:
The full model. .mi mean RMX2002 or something.
[Realme 6 Guides, News, & Discussion] Harida:
i chose format all and download plz help
[Realme 6 Guides, News, & Discussion] Harida:
RMX 2002 .. it selected Format all adn download ... can something be done ? plz help
[Realme 6 Guides, News, & Discussion] bx2nero:
Why did you do that. ...its clearly mentioned to not that ever. ..
[Realme 6 Guides, News, & Discussion] DFM23:
Same for me. I also encounter the same error on my realme c12.
[Realme 6 Guides, News, & Discussion] Gemi_17:
Halo i do format all by mistake is there a solution please tell me
[Realme 6 Guides, News, & Discussion] bx2nero:
Join realme 6 Telegram group . you will get your device back but no imei and stuffs .
[Realme 6 Guides, News, & Discussion] Gemi_17:
I don't understand my phone not have a imei and and sim network what should I do ?
[Realme 6 Guides, News, & Discussion] bx2nero:
Its clearly written not to do that in bold letter. .then why did you even touch that section. .its by default download only which is exactly needed. You will.boot Your phone but no imei.
[Realme 6 Guides, News, & Discussion] fossdelac:
Hello, Thank you for posting this guide. I'm trying to fix my hard bricked (Black screen, no power) Realme C12 using this procedure. I added my device on the lib32 usb filter and Bypass MTK. But when I flash the stock rom using SPFT. It always stuck at 0%. I tried different usb cable, ports, and even a different procedure using fireiso. I followed every steps and it always stuck. Did I miss something? Thanks in advance :)

Edit:

Additional info for my issue is that after I wait for at least 5 mins. The flashing will stop and an error will occur.

brom error status_download_exception(0xc0050003)​
[Realme 6 Guides, News, & Discussion] bx2nero:
Run memory diagnostic once by SPFT.
[Realme 6 Guides, News, & Discussion] fossdelac:
I will try this . Thank you.
[Realme 6 Guides, News, & Discussion] lycodesu:
i encounter this ERROR: STATUS_READ_FILE_ERR (0xC0010010) in the middle of flashing process it stop at special_preload and im trying to flash a.50

help @daeSundae @bx2_nero
[Realme 6 Guides, News, & Discussion] lycodesu:
oh btw i cant extract the b.53zip cuz im using an pc i need the non zip file
[Realme 6 Guides, News, & Discussion] bx2nero:
why did you untick few of the partitions ??
[Realme 6 Guides, News, & Discussion] bx2nero:
use winrar or 7z to extract .
[Realme 6 Guides, News, & Discussion] lycodesu:
thanks bro

from:lycodesu

telegram
[Realme 6 Guides, News, & Discussion] SAhilrmx2001:
Hello today I Have Flashed B.53 full firmware on my realme 6 and now it start rebooting in recovery again and again .I have Tried wipe data after flashing and than reboot my device but still having the same problem. One more thing when I wiped data and againg rebooted into the recovery it shows this code (r_traits<char>,std::_allocator<char>>const&,std::_1::ba) if someone have any solution please reply waiting for a solution .Thank You
[Realme 6 Guides, News, & Discussion] Andreww123:
Hello friend! I had just the same issue and after trying on three different computers I almost gave up. Nonetheless, I think it was solved after I made a clean python installation and manually added the Python directory to the path. You can easily find tutorials on youtube on how to add python to path manually. Do not install python from MS Store, just download it and do the path thingy manually as I did. It worked for me, I hope it works for you. Cheers!
[Realme 6 Guides, News, & Discussion] D4ghu:
Greetings, I ended up with the bricked cell phone for installing a firmware that asked me for a ROM, I think it was erased until the recovery, because I installed the ozip file that I downloaded from the official page trying to solve the problem, now it was in bootloop, luckily I turned it off If I follow the instructions in this publication, will I be able to repair my cell phone? Sorry if I am not understood, I speak Spanish and I am using Google Translate.
[Realme 6 Guides, News, & Discussion] bx2nero:
Yes follow the guide properly and it will be fine.
[Realme 6 Guides, News, & Discussion] D4ghu:
I am going to do it, I will inform if it goes well or badly, one more question, download the zip file B53 that weighs 6gb, and I looked at the file B37 and it weighs twice, what is the difference in size due to?
[Realme 6 Guides, News, & Discussion] bx2nero:
Use b53 .
[Realme 6 Guides, News, & Discussion] D4ghu:
I used the B 53 and it worked, my cell phone is fine, thank you very much.