Question Bootloader is unlocked but can't access fastboot mode

Search This thread

GIutton

Senior Member
Dec 26, 2021
73
11
OnePlus 8T
Samsung Galaxy S21 FE
Edited on 8/26:

Cannot boot the phone into fastboot which I believe is because I turned off OEM unlocking then unrooted the phone. Now OEM unlocking is off and greyed out probably because the magisk safetynet fix module is gone. Deep testing app didn't help it just tells me to run fastboot flashing lock. Factory defaulting or flashing with the MSM tool didn't help either. Everything else works fine, the bootloader is still unlocked, recovery mode works and I can get into the system just cannot get into fastboot mode.

I think the only way to fix this is to restore magisk root with safetynet fix so I can click OEM unlocking back on. So I either need to find a way to root the phone without access to fastboot mode (Rapper_Skull had a way to temporarily root but said that was just to change the phone model), or find a way to get QFIL to work with a magisk patched boot image, or repack the stock firmware ofp file with a magisk patched boot image so I can flash it with the MSM tool, or repack a nv_id 10100110 MEA firmware update with a magisk patched boot and use local install in system update. Another idea I had was to somehow mess up the active _b slot to maybe force the phone to boot on slot _a which has a magisk patched image on it? Any of that possible or just wishful thinking?
 
Last edited:

zorbakun

Senior Member
Jul 19, 2009
399
94
can you try the below

open the dialer and type code *#899# then choose SoftwareVersion and take a screenshot and post it here.
 

GIutton

Senior Member
Dec 26, 2021
73
11
OnePlus 8T
Samsung Galaxy S21 FE
can you try the below

open the dialer and type code *#899# then choose SoftwareVersion and take a screenshot and post it here.
Here is what I got.
Screenshot_2022-08-17-15-59-55-73_40dbc481ca5b738a325e5182fc08a331.jpgScreenshot_2022-08-17-16-00-04-24_40dbc481ca5b738a325e5182fc08a331.jpg
 
Last edited:

GIutton

Senior Member
Dec 26, 2021
73
11
OnePlus 8T
Samsung Galaxy S21 FE
I think I figured out what I did wrong to end up here. I had it magisk rooted with the safetynet fix module and while messing with the phone I think I clicked off "OEM unlocking" in dev options then I uninstalled magisk without clicking it back on. Now "OEM unlocking" is turned off and is greyed out so I cant turn it back on. At least the bootloader is still unlocked but no matter what I do I cannot get into fastboot mode. Have already tried factory reset and flashing the stock rom back with the MSM tool and that did not work. So I need to find a way to root or temporarily root the phone without using fastboot, or somehow ungrey/turn back on "OEM unlocking," or find a way to replace the boot.img of the stock firmware with a magisk patched image then either use local system update, the MSM tool or QFIL to install it. Does someone have any ideas on how to do this?

Or is there a way to force the phone to go back to the inactive slot where I have a magisk patched boot image installed, as in mess up slot _b to force it back to slot _a? What if I were to flash with the MSM tool to slot _b but unplug the cable before it finished to mess it up, could that make the phone revert back to slot _a?
 
Last edited:

zorbakun

Senior Member
Jul 19, 2009
399
94
I think I figured out what I did wrong to end up here. I had it magisk rooted with the safetynet fix module and while messing with the phone I think I clicked off "OEM unlocking" in dev options then I uninstalled magisk without clicking it back on. Now "OEM unlocking" is turned off and is greyed out so I cant turn it back on. At least the bootloader is still unlocked but no matter what I do I cannot get into fastboot mode. Have already tried factory reset and flashing the stock rom back with the MSM tool and that did not work. So I need to find a way to root or temporarily root the phone without using fastboot, or somehow ungrey/turn back on "OEM unlocking," or find a way to replace the boot.img of the stock firmware with a magisk patched image then either use local system update, the MSM tool or QFIL to install it. Does someone have any ideas on how to do this?

Or is there a way to force the phone to go back to the inactive slot where I have a magisk patched boot image installed, as in mess up slot _b to force it back to slot _a? What if I were to flash with the MSM tool to slot _b but unplug the cable before it finished to mess it up, could that make the phone revert back to slot _a?
try using the testing apk used to unlock the bootloader, it may help you access fastboot again
 

Quake94

Senior Member
Jan 24, 2009
83
18
Here are some ideas:
- What happens when you run adb reboot bootloader?
- Cache and userdata wipe?
- Read through this, maybe helpful:
- Do you have root access? If so, you could maybe try
- Going to system - upgrade - local update, and feeding it A.18.
Here is a stock 300mb a.17 - a.18 update file, I don't have the 5GB one unfortunately.
-In addition to above, maybe you could extract it and replace boot.img with a patched one, and pack back up as update file. Although this may throw out a checksum error when attempting to install..
 
  • Like
Reactions: GIutton

GIutton

Senior Member
Dec 26, 2021
73
11
OnePlus 8T
Samsung Galaxy S21 FE
Here are some ideas:
- What happens when you run adb reboot bootloader?
- Cache and userdata wipe?
- Read through this, maybe helpful:
- Do you have root access? If so, you could maybe try
- Going to system - upgrade - local update, and feeding it A.18.
Here is a stock 300mb a.17 - a.18 update file, I don't have the 5GB one unfortunately.
-In addition to above, maybe you could extract it and replace boot.img with a patched one, and pack back up as update file. Although this may throw out a checksum error when attempting to install..
When I run adb reboot bootloader the phone tries but then the screen glitches for a second then reboots into the system. I get the same result when I hold power and volume down buttons. Have tried factory defaulting from the settings menu and also tried wiping data from the recovery.

I do not have root access but the bootloader is unlocked. I tried using the exploit shared by Rapper_Skull to get temporary root access and it said it had worked but the magisk app does not recognize it as rooted and "adb shell su" is not recognized either. Rapper_Skull explained it was not within the scope of the exploit. Maybe it could be modified to do it somehow but that is beyond me.

I would love to try a local update with a patched boot image but I can't seem to find the proper OTA for my nv_id 10100110 MEA and because of the nv_id the Android 13 beta and rollback packages wont work either. Not too hopeful on this though as you said it will likely give a checksum error. From what I have read the MSM or QFIL tools should be able to do it, but would need to repack the ofp file with a patched boot for the MSM tool and nodoby has gotten QFIL to work that I have seen.

I will definitely read through the URLs you posted but turning on OEM unlocking from fastboot wont be an option for me since I can't get into it. In desperation I also scrolled through every single adb shell list settings <system/secure/global> output on this phone and my old OP 8T looking for a line item for OEM unlocking I could modify or add but alas there isn't one. Also tried talking to realme and they basically told me to go kick rocks because I am in the US so no support or warranty. They wouldn't even sell me a motherboard!

I have tried the MSM tool a couple times but it never worked. I am like 80% sure the tool kept flashing to active _b slot so I think my inactive _a slot should still contain my patched A.17 boot.img. I am very tempted to try flashing with the MSM tool again but unplugging the cable when it goes to clear/write the boot partition to mess it up. My thinking being that it would force the phone back onto slot _a just like it would do if an update fails, but that just sounds like such a dumb idea that it couldn't possibly work lol. Even if I do it and mess something up I should still be able to flash it with MSM again to fix it right? EDIT: Never mind my active slot is _a. When I took the A.18 update it went into slot _b meaning A.17 with my patched boot was on slot _a so the MSM tool must have been writing to the inactive slot and I only paid attention on the second flash to slot _b.
 
Last edited:
  • Like
Reactions: Quake94

Quake94

Senior Member
Jan 24, 2009
83
18
Try this
1. Run: adb shell pm disable-user com.qualcomm.qti.uim
2. Go to Developer Options and flip the OEM Unlock toggle
3. Now run: adb shell pm enable com.qualcomm.qti.uim
4. From now on the toggle will be disabled again, but now in "on" mode
5. Reboot to fastboot
 

Quake94

Senior Member
Jan 24, 2009
83
18
I gave it a try but OEM unlocking remained greyed out.
From what I seen you should try pressing OEM unlock toggle with the qualcomm service disabled, despite ithe toggle being greyed out, have you tried that?
I found this method in OnePlus forums, since OnePlus/Oppo/Realme it's all the same.

 

GIutton

Senior Member
Dec 26, 2021
73
11
OnePlus 8T
Samsung Galaxy S21 FE
From what I seen you should try pressing OEM unlock toggle with the qualcomm service disabled, despite ithe toggle being greyed out, have you tried that?
I found this method in OnePlus forums, since OnePlus/Oppo/Realme it's all the same.

I just tried it but still can't get into fastboot mode. Thank you for suggestion though I really appreciate your help.
 

GIutton

Senior Member
Dec 26, 2021
73
11
OnePlus 8T
Samsung Galaxy S21 FE
Someone suggested I try adb shell reboot fastboot and that booted the phone into fastbootd mode but I get no output from "fastboot devices". As far as I can tell it looks just like recovery only the title says Fastbootd Mode instead of "RECOVERY".
 
Last edited:

GIutton

Senior Member
Dec 26, 2021
73
11
OnePlus 8T
Samsung Galaxy S21 FE
Well I updated my drivers and that got the phone recognized in fastbootd mode. I tried fastboot boot magisk-patched-boot.img but that failed, however, fastboot flash boot magisk-patched-boot.img did work so I was finally able to root the phone and apply the safetynet fix which ungreyed OEM unlocking and allowed me to flip it back on. Unfortunately that did not fix the bootloader/fastboot issue. No matter what I still cannot get into fastboot mode.

I was thinking of trying fastboot flashing lock to see if I can relock the bootloader from fastbootd mode but I would rather not make things worse by doing something I shouldn't be doing in fastbootd mode.
 
Last edited:
  • Like
Reactions: Quake94

bubundas17

Member
Sep 14, 2016
37
6
Well I updated my drivers and that got the phone recognized in fastbootd mode. I tried fastboot boot magisk-patched-boot.img but that failed, however, fastboot flash boot magisk-patched-boot.img did work so I was finally able to root the phone and apply the safetynet fix which ungreyed OEM unlocking and allowed me to flip it back on. Unfortunately that did not fix the bootloader/fastboot issue. No matter what I still cannot get into fastboot mode.

I was thinking of trying fastboot flashing lock to see if I can relock the bootloader from fastbootd mode but I would rather not make things worse by doing something I shouldn't be doing in fastbootd mode.

Have you tried EDL flash? It should be able to restore it back to stock.
 

Quake94

Senior Member
Jan 24, 2009
83
18
I replied in the other thread already, but from what it appears, there is a lot of confusion with the boot modes.

bootloader/fastboot -> adb reboot bootloader (or the key combo) -> This is the mode with the green START button on top
fastbootd - adb reboot fastboot, or fastboot reboot fastboot (from being already in bootloader/fastboot) ->This is the mode with selection of "Wipe Data", "Reboot" and "Power Off", same as Recovery but the label is "Fastbootd"
recovery - adb reboot recovery (or the key combo) -> Shows "Wipe Data", "Reboot" and "Power Off", label is "Recovery"
EDL - adb reboot edl / fastboot oem edl / short testpoints or modify boot entry -> This is for QCIL / MSM or any other Qualcomm firehose flashing.

So can you confirm:
When I run adb reboot bootloader the phone tries but then the screen glitches for a second then reboots into the system.
When you ran adb reboot bootloader, did you see a "mascot", or did it look like a screen glitch?
adb reboot bootloader should get you to the regular fastboot with green START

The "mascot" would show only when the phone was starting fastboot
The "glitch" happened to me when I've installed OTA and then I tried to boot to second slot via Magisk or "set_active" command. And what fixed it was selecting "Install" in OEM updater.
 

GIutton

Senior Member
Dec 26, 2021
73
11
OnePlus 8T
Samsung Galaxy S21 FE
I replied in the other thread already, but from what it appears, there is a lot of confusion with the boot modes.

bootloader/fastboot -> adb reboot bootloader (or the key combo) -> This is the mode with the green START button on top
fastbootd - adb reboot fastboot, or fastboot reboot fastboot (from being already in bootloader/fastboot) ->This is the mode with selection of "Wipe Data", "Reboot" and "Power Off", same as Recovery but the label is "Fastbootd"
recovery - adb reboot recovery (or the key combo) -> Shows "Wipe Data", "Reboot" and "Power Off", label is "Recovery"
EDL - adb reboot edl / fastboot oem edl / short testpoints or modify boot entry -> This is for QCIL / MSM or any other Qualcomm firehose flashing.

So can you confirm:

When you ran adb reboot bootloader, did you see a "mascot", or did it look like a screen glitch?
adb reboot bootloader should get you to the regular fastboot with green START

The "mascot" would show only when the phone was starting fastboot
The "glitch" happened to me when I've installed OTA and then I tried to boot to second slot via Magisk or "set_active" command. And what fixed it was selecting "Install" in OEM updater.
When I try the button combo the screen shows the realme logo then glitches and reboots to the system and from there if I try adb reboot bootloader I get a mascot looking thing with chinese letters then the screen glitches and it reboots right back into the system.

So you are calling the button combo "fastboot mode" and adb reboot bootloader/fastboot reboot bootloader the "bootloader" but both of these show the same start menu?
 
Last edited:

Quake94

Senior Member
Jan 24, 2009
83
18
When I try the button combo the screen shows the realme logo then glitches and reboots to the system and from there if I try adb reboot bootloader I get a mascot looking thing with chinese letters then it reboots right back into the system.

So you are calling the button combo "fastboot mode" and adb reboot bootloader/fastboot reboot bootloader the "bootloader" but both of these show the same start menu?
Holding Volume Down + Power button starts the "fastboot mode", same mode as the command adb reboot bootloader.
My understanding is that bootloader mode is same as fastboot mode.

On a side note, when I run fastboot oem device-info, I have the following: information
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false

Also, running fastboot getvar all:

platform-tools>fastboot getvar all
(bootloader) parallel-download-flash:yes
(bootloader) hw-revision:20002
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:7904
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) erase-block-size: 0x1000
(bootloader) logical-block-size: 0x1000
(bootloader) variant:SM_ UFS
(bootloader) partition-type:eek:plusreserve5:raw
(bootloader) partition-size:eek:plusreserve5: 0x4000000
(bootloader) partition-type:eek:plusreserve4:raw
(bootloader) partition-size:eek:plusreserve4: 0x2000000
(bootloader) partition-type:eek:plusreserve3:raw
(bootloader) partition-size:eek:plusreserve3: 0x4000000
(bootloader) partition-type:eek:plusreserve2:raw
(bootloader) partition-size:eek:plusreserve2: 0x10000000
(bootloader) partition-type:eek:plusreserve1:raw
(bootloader) partition-size:eek:plusreserve1: 0x800000
(bootloader) partition-type:mdm1oemnvbktmp:raw
(bootloader) partition-size:mdm1oemnvbktmp: 0x200000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x20000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x300000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x300000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x300000
(bootloader) partition-type:eek:plusstanvbk_a:raw
(bootloader) partition-size:eek:plusstanvbk_a: 0x1400000
(bootloader) partition-type:eek:plusdycnvbk:raw
(bootloader) partition-size:eek:plusdycnvbk: 0x1400000
(bootloader) partition-type:ALIGN_TO_128K_2:raw
(bootloader) partition-size:ALIGN_TO_128K_2: 0x1A000
(bootloader) partition-type:apdp_full:raw
(bootloader) partition-size:apdp_full: 0x40000
(bootloader) partition-type:xbl_sc_logs:raw
(bootloader) partition-size:xbl_sc_logs: 0x20000
(bootloader) partition-type:xbl_sc_test_mode:raw
(bootloader) partition-size:xbl_sc_test_mode: 0x10000
(bootloader) partition-type:rtice:raw
(bootloader) partition-size:rtice: 0x80000
(bootloader) partition-type:spunvm:raw
(bootloader) partition-size:spunvm: 0x2000000
(bootloader) partition-type:tzsc:raw
(bootloader) partition-size:tzsc: 0x20000
(bootloader) partition-type:connsec:raw
(bootloader) partition-size:connsec: 0x20000
(bootloader) partition-type:mdcompress:raw
(bootloader) partition-size:mdcompress: 0x1400000
(bootloader) partition-type:vm-data:raw
(bootloader) partition-size:vm-data: 0x20A4000
(bootloader) partition-type:secdata:raw
(bootloader) partition-size:secdata: 0x7000
(bootloader) partition-type:uefivarstore:raw
(bootloader) partition-size:uefivarstore: 0x80000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x20000000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:limits-cdsp:raw
(bootloader) partition-size:limits-cdsp: 0x1000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x1000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x1000
(bootloader) partition-type:xbl_ramdump_b:raw
(bootloader) partition-size:xbl_ramdump_b: 0x200000
(bootloader) partition-type:splash_b:raw
(bootloader) partition-size:splash_b: 0x20A4000
(bootloader) partition-type:recovery_b:raw
(bootloader) partition-size:recovery_b: 0x6400000
(bootloader) partition-type:eek:plus_sec_b:raw
(bootloader) partition-size:eek:plus_sec_b: 0xA00000
(bootloader) partition-type:qweslicstore_b:raw
(bootloader) partition-size:qweslicstore_b: 0x40000
(bootloader) partition-type:vendor_boot_b:raw
(bootloader) partition-size:vendor_boot_b: 0xC000000
(bootloader) partition-type:featenabler_b:raw
(bootloader) partition-size:featenabler_b: 0x20000
(bootloader) partition-type:cpucp_b:raw
(bootloader) partition-size:cpucp_b: 0x100000
(bootloader) partition-type:vm-bootsys_b:raw
(bootloader) partition-size:vm-bootsys_b: 0x10625000
(bootloader) partition-type:shrm_b:raw
(bootloader) partition-size:shrm_b: 0x20000
(bootloader) partition-type:imagefv_b:raw
(bootloader) partition-size:imagefv_b: 0x200000
(bootloader) partition-type:uefisecapp_b:raw
(bootloader) partition-size:uefisecapp_b: 0x200000
(bootloader) partition-type:dtbo_b:raw
(bootloader) partition-size:dtbo_b: 0x1800000
(bootloader) partition-type:vbmeta_b:raw
(bootloader) partition-size:vbmeta_b: 0x10000
(bootloader) partition-type:qupfw_b:raw
(bootloader) partition-size:qupfw_b: 0x14000
(bootloader) partition-type:devcfg_b:raw
(bootloader) partition-size:devcfg_b: 0x20000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0xC000000
(bootloader) partition-type:keymaster_b:raw
(bootloader) partition-size:keymaster_b: 0x80000
(bootloader) partition-type:dsp_b:raw
(bootloader) partition-size:dsp_b: 0x4000000
(bootloader) partition-type:abl_b:raw
(bootloader) partition-size:abl_b: 0x100000
(bootloader) partition-type:mdtp_b:raw
(bootloader) partition-size:mdtp_b: 0x2000000
(bootloader) partition-type:mdtpsecapp_b:raw
(bootloader) partition-size:mdtpsecapp_b: 0x400000
(bootloader) partition-type:bluetooth_b:raw
(bootloader) partition-size:bluetooth_b: 0x400000
(bootloader) partition-type:modem_b:raw
(bootloader) partition-size:modem_b: 0x12C00000
(bootloader) partition-type:hyp_b:raw
(bootloader) partition-size:hyp_b: 0x800000
(bootloader) partition-type:tz_b:raw
(bootloader) partition-size:tz_b: 0x400000
(bootloader) partition-type:aop_config_b:raw
(bootloader) partition-size:aop_config_b: 0x80000
(bootloader) partition-type:aop_b:raw
(bootloader) partition-size:aop_b: 0x80000
(bootloader) partition-type:uefi_b:raw
(bootloader) partition-size:uefi_b: 0x500000
(bootloader) partition-type:xbl_ramdump_a:raw
(bootloader) partition-size:xbl_ramdump_a: 0x200000
(bootloader) partition-type:splash_a:raw
(bootloader) partition-size:splash_a: 0x20A4000
(bootloader) partition-type:recovery_a:raw
(bootloader) partition-size:recovery_a: 0x6400000
(bootloader) partition-type:eek:plus_sec_a:raw
(bootloader) partition-size:eek:plus_sec_a: 0xA00000
(bootloader) partition-type:qweslicstore_a:raw
(bootloader) partition-size:qweslicstore_a: 0x40000
(bootloader) partition-type:qmcs:raw
(bootloader) partition-size:qmcs: 0x1E00000
(bootloader) partition-type:vendor_boot_a:raw
(bootloader) partition-size:vendor_boot_a: 0xC000000
(bootloader) partition-type:featenabler_a:raw
(bootloader) partition-size:featenabler_a: 0x20000
(bootloader) partition-type:cpucp_a:raw
(bootloader) partition-size:cpucp_a: 0x100000
(bootloader) partition-type:vm-bootsys_a:raw
(bootloader) partition-size:vm-bootsys_a: 0x10625000
(bootloader) partition-type:shrm_a:raw
(bootloader) partition-size:shrm_a: 0x20000
(bootloader) partition-type:imagefv_a:raw
(bootloader) partition-size:imagefv_a: 0x200000
(bootloader) partition-type:uefisecapp_a:raw
(bootloader) partition-size:uefisecapp_a: 0x200000
(bootloader) partition-type:dtbo_a:raw
(bootloader) partition-size:dtbo_a: 0x1800000
(bootloader) partition-type:vbmeta_a:raw
(bootloader) partition-size:vbmeta_a: 0x10000
(bootloader) partition-type:qupfw_a:raw
(bootloader) partition-size:qupfw_a: 0x14000
(bootloader) partition-type:devcfg_a:raw
(bootloader) partition-size:devcfg_a: 0x20000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0xC000000
(bootloader) partition-type:keymaster_a:raw
(bootloader) partition-size:keymaster_a: 0x80000
(bootloader) partition-type:dsp_a:raw
(bootloader) partition-size:dsp_a: 0x4000000
(bootloader) partition-type:abl_a:raw
(bootloader) partition-size:abl_a: 0x100000
(bootloader) partition-type:mdtp_a:raw
(bootloader) partition-size:mdtp_a: 0x2000000
(bootloader) partition-type:mdtpsecapp_a:raw
(bootloader) partition-size:mdtpsecapp_a: 0x400000
(bootloader) partition-type:bluetooth_a:raw
(bootloader) partition-size:bluetooth_a: 0x400000
(bootloader) partition-type:modem_a:raw
(bootloader) partition-size:modem_a: 0x12C00000
(bootloader) partition-type:hyp_a:raw
(bootloader) partition-size:hyp_a: 0x800000
(bootloader) partition-type:tz_a:raw
(bootloader) partition-size:tz_a: 0x400000
(bootloader) partition-type:aop_config_a:raw
(bootloader) partition-size:aop_config_a: 0x80000
(bootloader) partition-type:aop_a:raw
(bootloader) partition-size:aop_a: 0x80000
(bootloader) partition-type:uefi_a:raw
(bootloader) partition-size:uefi_a: 0x500000
(bootloader) partition-type:engineering_cdt_b:raw
(bootloader) partition-size:engineering_cdt_b: 0x100000
(bootloader) partition-type:dinfo:raw
(bootloader) partition-size:dinfo: 0x4000
(bootloader) partition-type:eek:cdt:raw
(bootloader) partition-size:eek:cdt: 0x20000
(bootloader) partition-type:engineering_cdt_a:raw
(bootloader) partition-size:engineering_cdt_a: 0x100000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:cdt:raw
(bootloader) partition-size:cdt: 0x20000
(bootloader) partition-type:ALIGN_TO_128K_1:raw
(bootloader) partition-size:ALIGN_TO_128K_1: 0x1A000
(bootloader) partition-type:apdpb:raw
(bootloader) partition-size:apdpb: 0x40000
(bootloader) partition-type:multiimgoem_b:raw
(bootloader) partition-size:multiimgoem_b: 0x8000
(bootloader) partition-type:multiimgqti_b:raw
(bootloader) partition-size:multiimgqti_b: 0x8000
(bootloader) partition-type:xbl_config_b:raw
(bootloader) partition-size:xbl_config_b: 0x35000
(bootloader) partition-type:xbl_b:raw
(bootloader) partition-size:xbl_b: 0x600000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:multiimgoem_a:raw
(bootloader) partition-size:multiimgoem_a: 0x8000
(bootloader) partition-type:multiimgqti_a:raw
(bootloader) partition-size:multiimgqti_a: 0x8000
(bootloader) partition-type:xbl_config_a:raw
(bootloader) partition-size:xbl_config_a: 0x35000
(bootloader) partition-type:xbl_a:raw
(bootloader) partition-size:xbl_a: 0x600000
(bootloader) partition-type:userdata:f2fs
(bootloader) partition-size:userdata: 0x37F450F000
(bootloader) partition-type:splash_odm:raw
(bootloader) partition-size:splash_odm: 0x20A4000
(bootloader) partition-type:rawdump:raw
(bootloader) partition-size:rawdump: 0x10000000
(bootloader) partition-type:metadata:raw
(bootloader) partition-size:metadata: 0x1000000
(bootloader) partition-type:vbmeta_vendor_b:raw
(bootloader) partition-size:vbmeta_vendor_b: 0x10000
(bootloader) partition-type:vbmeta_vendor_a:raw
(bootloader) partition-size:vbmeta_vendor_a: 0x10000
(bootloader) partition-type:vbmeta_system_b:raw
(bootloader) partition-size:vbmeta_system_b: 0x10000
(bootloader) partition-type:vbmeta_system_a:raw
(bootloader) partition-size:vbmeta_system_a: 0x10000
(bootloader) partition-type:super:raw
(bootloader) partition-size:super: 0x2A0000000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-type:persist:raw
(bootloader) partition-size:persist: 0x2000000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x2000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:no
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:6
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:58e3XXXX
(bootloader) product:taro
(bootloader) snapshot-update-status:none
(bootloader) is-userspace:no
(bootloader) max-download-size:805306368
(bootloader) kernel:uefi
all:
Finished. Total time: 0.561s

Not sure if useful...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Here are some ideas:
    - What happens when you run adb reboot bootloader?
    - Cache and userdata wipe?
    - Read through this, maybe helpful:
    - Do you have root access? If so, you could maybe try
    - Going to system - upgrade - local update, and feeding it A.18.
    Here is a stock 300mb a.17 - a.18 update file, I don't have the 5GB one unfortunately.
    -In addition to above, maybe you could extract it and replace boot.img with a patched one, and pack back up as update file. Although this may throw out a checksum error when attempting to install..
    1
    Here are some ideas:
    - What happens when you run adb reboot bootloader?
    - Cache and userdata wipe?
    - Read through this, maybe helpful:
    - Do you have root access? If so, you could maybe try
    - Going to system - upgrade - local update, and feeding it A.18.
    Here is a stock 300mb a.17 - a.18 update file, I don't have the 5GB one unfortunately.
    -In addition to above, maybe you could extract it and replace boot.img with a patched one, and pack back up as update file. Although this may throw out a checksum error when attempting to install..
    When I run adb reboot bootloader the phone tries but then the screen glitches for a second then reboots into the system. I get the same result when I hold power and volume down buttons. Have tried factory defaulting from the settings menu and also tried wiping data from the recovery.

    I do not have root access but the bootloader is unlocked. I tried using the exploit shared by Rapper_Skull to get temporary root access and it said it had worked but the magisk app does not recognize it as rooted and "adb shell su" is not recognized either. Rapper_Skull explained it was not within the scope of the exploit. Maybe it could be modified to do it somehow but that is beyond me.

    I would love to try a local update with a patched boot image but I can't seem to find the proper OTA for my nv_id 10100110 MEA and because of the nv_id the Android 13 beta and rollback packages wont work either. Not too hopeful on this though as you said it will likely give a checksum error. From what I have read the MSM or QFIL tools should be able to do it, but would need to repack the ofp file with a patched boot for the MSM tool and nodoby has gotten QFIL to work that I have seen.

    I will definitely read through the URLs you posted but turning on OEM unlocking from fastboot wont be an option for me since I can't get into it. In desperation I also scrolled through every single adb shell list settings <system/secure/global> output on this phone and my old OP 8T looking for a line item for OEM unlocking I could modify or add but alas there isn't one. Also tried talking to realme and they basically told me to go kick rocks because I am in the US so no support or warranty. They wouldn't even sell me a motherboard!

    I have tried the MSM tool a couple times but it never worked. I am like 80% sure the tool kept flashing to active _b slot so I think my inactive _a slot should still contain my patched A.17 boot.img. I am very tempted to try flashing with the MSM tool again but unplugging the cable when it goes to clear/write the boot partition to mess it up. My thinking being that it would force the phone back onto slot _a just like it would do if an update fails, but that just sounds like such a dumb idea that it couldn't possibly work lol. Even if I do it and mess something up I should still be able to flash it with MSM again to fix it right? EDIT: Never mind my active slot is _a. When I took the A.18 update it went into slot _b meaning A.17 with my patched boot was on slot _a so the MSM tool must have been writing to the inactive slot and I only paid attention on the second flash to slot _b.
    1
    Someone suggested I try adb shell reboot fastboot and that booted the phone into fastbootd mode but I get no output from "fastboot devices". As far as I can tell it looks just like recovery only the title says Fastbootd Mode instead of "RECOVERY".
    Update your fastboot drivers.
    1
    Well I updated my drivers and that got the phone recognized in fastbootd mode. I tried fastboot boot magisk-patched-boot.img but that failed, however, fastboot flash boot magisk-patched-boot.img did work so I was finally able to root the phone and apply the safetynet fix which ungreyed OEM unlocking and allowed me to flip it back on. Unfortunately that did not fix the bootloader/fastboot issue. No matter what I still cannot get into fastboot mode.

    I was thinking of trying fastboot flashing lock to see if I can relock the bootloader from fastbootd mode but I would rather not make things worse by doing something I shouldn't be doing in fastbootd mode.