Hey Guys,
I´m using a Motorola One xt1941-4. I tried to flash my phone since extensive googling suggested that this would be the only remedy for the issue of my phone only charging in fastboot mode.
I tried to do this with a locked bootloader since the $ fastboot oem get_unlock_data return failed: Unlock data unavailable. I flashed with what was the newest update from the lolinet servers via the sequence of commands given in the servicefile. During that i was unable to flash the boot.img though, which is, I imagine due to the locked bootloader. i still went through with the flashing.
Obviously it didn´t work though since my phone is now alwys going directly into fastboot showing this:
AP Fastboot Flash Mode (Secure)
SSM: boot image roll back: 11,12
failed to validate boot image
I thought this might be because i have to flash the exact firmware update i had installed preflash. I´m not sure which one that was though. I tried to flash all the available firmware on lolinet for my xt1941-4 to get the correct one- unsuccessfully. Help?
PirxRaumpilot said:
Hey Guys,
I´m using a Motorola One xt1941-4. I tried to flash my phone since extensive googling suggested that this would be the only remedy for the issue of my phone only charging in fastboot mode.
I tried to do this with a locked bootloader since the $ fastboot oem get_unlock_data return failed: Unlock data unavailable. I flashed with what was the newest update from the lolinet servers via the sequence of commands given in the servicefile. During that i was unable to flash the boot.img though, which is, I imagine due to the locked bootloader. i still went through with the flashing.
Obviously it didn´t work though since my phone is now alwys going directly into fastboot showing this:
AP Fastboot Flash Mode (Secure)
SSM: boot image roll back: 11,12
failed to validate boot image
I thought this might be because i have to flash the exact firmware update i had installed preflash. I´m not sure which one that was though. I tried to flash all the available firmware on lolinet for my xt1941-4 to get the correct one- unsuccessfully. Help?
Click to expand...
Click to collapse
Try fastboot getvar all command.
It should at least give you info about which update channel you're on and probably fingerprint as well. This would hopefully help in finding the right firmware for your device.
Related
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
doctajay said:
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
Click to expand...
Click to collapse
You need to unlock again in order to flash back a custom recovery. You also need to have the stock splash screen before you ruu. Had the exact same issue you had. Stock h-boot, stock splash screen and relock and all should be good.
That is my main problem. All of the unlock methods require me to load load an apk to change the CID. I can't do that in fastboot. Is there another unlock method I'm missing that allows you to do it from the fast boot mode?
Sent from my LG-D800 using Tapatalk
if u have your original unlock code from htc dev I think u can fastboot flash that code to unlock again. its in the forum somewhere just not sure where it is.
try this thread, good luck
http://forum.xda-developers.com/showthread.php?t=2160677
You don't have to run a apk to change the cid just Google change cid commands, you do it through adb change it to 22222222 then redo the HTC dev to get your unlock.bin again if u don't have it.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
doctajay said:
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
Click to expand...
Click to collapse
You device most likely can't downgrade due to having a locked device. Have you tried flashing the 2.07 ruu
Thank you for all of the replies. Actually the change of the CID command might have worked but I didn't see that reply before I had tried another method found in this thread: http://forum.xda-developers.com/showthread.php?t=2570548.
I was truly stuck in fastboot and couldn't flash a custom recovery at all. Well I used the advice from a previous thread and edited the firmware .zip posted in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2314771. I had initially tried to flash the .zip posted but when I tried to boot into the recovery it wouldn't work. So I opened the .zip file without extracting it and removed the recovery.img from the .zip, I then took the TWRP custom recovery and inserted it into the .zip (if you extract the zip this will not work; you need to use software that can edit a zip without extracting it. On the Mac, which I was using, I used Spring). I renamed the TWRP recovery to "recovery.img" to match what I had previously deleted.
Then I flashed this edited firmware.zip by using the following command in usb fastboot mode (here's the link for my edited file):
fastboot oem rebootRUU
fastboot flash zip YOUREDITEDFILE.zip
fastboot reboot
This then allowed me to boot into recovery. I thought I had figured it out and could now sideload a ROM using the "adb sideload" command and flash some type of ROM that would boot. This failed miserably; it would allow me to push the file, but the install would always fail before it completed.
So then I found this thread here: http://forum.xda-developers.com/showthread.php?t=2570548. I first flashed the two .zip files that were posted in post #44. then I flashed the full RUU posted in post #1. This gave me a bootable stock ROM. Praise God!!!
Finally I went back to this thread: http://forum.xda-developers.com/showthread.php?t=2293919, and flashed the following code.
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Not sure why I had such a terrible time, but I'm glad its over and the DNA is finally sold. Thank you for all your help!
trying to restore my dna back to stock
I got my dna locked again and now I am running the ruu file and i am stuck at 6%. Can someone help please!! Tried it by double clicking the ruu file and running it like that, and i also ran it in administration and both ways i am stuck at 6%
Hi,
First of all sorry for crappy links, but as a new user I cannot post them.
I have got a chinese phone called Haier W858 (imei.info/phonedatabase/15302-haier-w858/). Few days ago I found out that it is similar to Smartfren Andromax I3S and managed to modify stock ROM by fastboot without any problems (current ROM: needrom.com/download/smartfren-andromax-ad682h/). After that when I tried to turn on fastboot mode I got information that bootloader is locked and I need verify.zip file on sdcard to unlock it. Few searches later I found correct verify.zip file and put it on sdcard. Everything should be great, because now when I try to run fastboot mode I get information that verify.zip file is correct and phone turns into some kind of fastboot mode, but I cannot write anything to it.
For example, I get messages like:
Code:
> fastboot flash modem modem\NON-HLOS.bin
sending 'modem' (31985 KB)... OKAY
writing 'modem'... [B]FAILED (remote: can't flash Partition)[/B]
When I check if bootloader is unlocked by fastboot oem device-info I get:
Code:
>fastboot oem device-info
... INFO Device tampered: true
[B]INFO Device unlocked: true[/B]
INFO Charger screen enabled: true
OKAY
so it looks like everything should be alright.
Whatsmore, I can write any ROM by doing it like so:
- turn into that weird fastboot mode,
- boot up into TWRP or CWM by writing: fastboot boot recovery.img (because of this problem I cannot flash it permanently so I boot it up),
- install ROM from recovery.
What my question is - is it possible to flash previous fastboot mode where I could write anything to phone without problems and without checking any verify.zip file?
I do not know if it could help in anything but this is shot made when I did not have correct verify.zip file: postimg.org/image/u7thz6tq7/. Now it says that it is OK and boots up into that weird fastboot mode.
Thanks in advance.
Are you trying to flash a modem from a Samsung phone? Haven't seen NON-HLOS.bin files used in other phones before. That would explain why it wouldn't flash through fastboot...
es0tericcha0s said:
Are you trying to flash a modem from a Samsung phone? Haven't seen NON-HLOS.bin files used in other phones before. That would explain why it wouldn't flash through fastboot...
Click to expand...
Click to collapse
Hard to say if it is modem from Samsung phone, because all of ROMs for this kind of phone got that file. Maybe it is based on Samsung soft... I did not have any problems with flashing this and other files once with fastboot (first flash that I made was with ROM from this site: needrom.com/download/smartfren-andromax-ad682h/) and it was successful, but after that I get messages that I wrote in 1st post.
Any advices?
So I relocked my bootloader after upgrading to marshmallow and forgot that I did that..... I tried to flash a stock boot img so I could utilize the ota, and it sort of bricked my tablet. Being a total dumbass I didn't realize that was the problem. Having had a similar issue before on my galaxy s4 where I follow a similar solution. I already have twrp installed, and it was asking for encryption for which there was none. So I wiped data and formatted to get past the encryption. On my s4 I was then able to reinstall the stock firmware and software. However when I tried to push the bootloader to my nexus I got this weird error.. can someone pleeeeeeease spare me and help me out. This tablet is my lifeline for college...
Don't get me in trouble for posting this image please lol, I just don't have enough posts. http ://i67.tinypic.com/v80vwl.jpg[/B][/B]
I figured it out, I was just being dumb. I just needed to use the fastboot commands and not try to use twrp
tdct12 said:
So I relocked my bootloader after upgrading to marshmallow and forgot that I did that..... I tried to flash a stock boot img so I could utilize the ota, and it sort of bricked my tablet. Being a total dumbass I didn't realize that was the problem. Having had a similar issue before on my galaxy s4 where I follow a similar solution. I already have twrp installed, and it was asking for encryption for which there was none. So I wiped data and formatted to get past the encryption. On my s4 I was then able to reinstall the stock firmware and software. However when I tried to push the bootloader to my nexus I got this weird error.. can someone pleeeeeeease spare me and help me out. This tablet is my lifeline for college...
Don't get me in trouble for posting this image please lol, I just don't have enough posts. http ://i67.tinypic.com/v80vwl.jpg[/B][/B]
I figured it out, I was just being dumb. I just needed to use the fastboot commands and not try to use twrp
Click to expand...
Click to collapse
If your able to access the bootloader menu or the fastboot menu, you could flash the stock and would fix the brick,soft brick or boot-loop.
Head to Google developer nexus image. Download the factory image of your devices on your devices. Extract all the files and copy paste the fastboot and adb files. Head to your devices and open the fastboot menu.
Type the following commends to restore your devices if the flashall did not work.
Fastboot oem unlock
Fastboot flash bootloader bootloader....
Fastboot reboot-bootloader
Fastboot erase boot
Fastboot flash boot boot.img
Fastboot erase recovery
Fastboot flash recovery recovery.img
Fastboot erase system
Fastboot flash system system.img (this could take up to 15 minutes, don't do anything to stop the process you can make your devices and a worst state)
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot erase vendor
Fastboot flash vendor vendor.img
Fastboot reboot
This should fix your devices. I did not and it save each time I broke my device or anything similar.
If you want after all that. You can enter the following commends to relock your devices but don't make the same mistake you did before. If you want to avoid that same mistake just don't enter the commends.
What the guy above me said, also pro tip, some times not all the files will extract just keep extracting till all the image files are there.
i know there are other threads on this topic. But after going through them I cant find the fix.
I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works.
I used lmsa to download the stock rom. installed magisk and ran the boot.img to get the patched boot. Then flashed the patched boot and when i rebooted the device...no touchscreen.
I tried to reflash the original boot.img but that didnt help.
I tried to use LMSA to rescue. but when i connect the phone it says "unable to match firmware. Some key information cannot be read from device."
The original adb fastboot was old. So I did update to the r30 version and tried flashing everything again. but it still boots up and no touchscreen.
Im obviously at a loss here. so any help would be appreciated. Just to even get it back to stock would be fine.
Or do I try to install twrp and throw a custom rom on? would that work. Again, at a loss...
TIA
UPDATE: ive gotten everything sorted. no more bootloop. touchscreen working. connecting to lmsa. and rooted. Thank you for all the responses.
I think what happened is that when i started all this i was not using the latest adb. That seemed to not be an issue for unlocking bootloader, but a major issue for rooting. When i tried to root,i got the no touchscreen. So I followed directions and went to manually flash the stock firmware. I didnt know how to do this and couldnt find instructions for the g power. but did find instructions for the g8 power and assumed it would be the same...its almost the same, but not, so i got the bootloop.
These are the instructions:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
I added fastboot flash super super.img_sparsechunk.15, because the g8 power only has 14 sparsechunks and thats why i kept getting the bootloop. very stupid mistake that was driving me nuts! Once i added that 15th line the phone booted up and touchscreen worked again.
Then i installed magisk manager. Took the boot.img file from my stock rom and put it on my phone. back in magisk i clicked on install a patch file, chose the boot.img and created a magisk_patched.img which i put back into the adb folder i previously used to flash the firmware.
Then went back to fastboot and flashed the magisk_patched.img and the phone is now working and rooted...THANK GOD
cnoevl21 said:
i know there are other threads on this topic. But after going through them I cant find the fix.
I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works.
I used lmsa to download the stock rom. installed magisk and ran the boot.img to get the patched boot. Then flashed the patched boot and when i rebooted the device...no touchscreen.
I tried to reflash the original boot.img but that didnt help.
I tried to use LMSA to rescue. but when i connect the phone it says "unable to match firmware. Some key information cannot be read from device."
The original adb fastboot was old. So I did update to the r30 version and tried flashing everything again. but it still boots up and no touchscreen.
Im obviously at a loss here. so any help would be appreciated. Just to even get it back to stock would be fine.
Or do I try to install twrp and throw a custom rom on? would that work. Again, at a loss...
TIA
Click to expand...
Click to collapse
Flash stock ROM manually, it will fix the problem
riyan65 said:
Flash stock ROM manually, it will fix the problem
Click to expand...
Click to collapse
The US stock ROM does not have a 'flash all' option. So i have no idea how to flash it. ugh
cnoevl21 said:
The US stock ROM does not have a 'flash all' option. So i have no idea how to flash it. ugh
Click to expand...
Click to collapse
I just ran into the same problem and asked you about it in the other thread. Right after, I tried the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC and got my touchscreen back.
https ://mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/
I found out more of what's going on and posted in the other thread:
I just did the same exact thing. LMSA gave me SOFIA_RETAIL_QPMS30.80_51_8. Lost touchscreen with the patched boot. Used the stock 30.80_51_8 boot and didn't fix it. Also tried the older QPMS30.80-51-3, no dice.
Oh and LMSA can't rescue... key information cannot be read from device.
I'd appreciate any help. Thanks.
UPDATE - found the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC got the screen working again.
UPDATE 2 - patching -5 still left me no touchscreen. Went back to stock -5 and didn't work. Tried -8 and works again... I'm confused.
UPDATE 3 - when phone booted up, it notified me -8 was just installed... Patched -8 boot again and everything appears to be working fine. Moral of story - LMSA downloads the correct firmware if you give the phone enough time to finish auto-updating before rooting. SMH
haanjamin said:
I found out more of what's going on and posted in the other thread:
I just did the same exact thing. LMSA gave me SOFIA_RETAIL_QPMS30.80_51_8. Lost touchscreen with the patched boot. Used the stock 30.80_51_8 boot and didn't fix it. Also tried the older QPMS30.80-51-3, no dice.
Oh and LMSA can't rescue... key information cannot be read from device.
I'd appreciate any help. Thanks.
UPDATE - found the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC got the screen working again.
UPDATE 2 - patching -5 still left me no touchscreen. Went back to stock -5 and didn't work. Tried -8 and works again... I'm confused.
UPDATE 3 - when phone booted up, it notified me -8 was just installed... Patched -8 boot again and everything appears to be working fine. Moral of story - LMSA downloads the correct firmware if you give the phone enough time to finish auto-updating before rooting. SMH
Click to expand...
Click to collapse
good info to know. but now ive gone i screwed my phone up even worse. cuz now im stuck in boot loop. i was trying 105-5, but ill try 51-5, then -8. maybe one of them is the right stupid firmware for my phone
Do not panic.
Follow this guide to flash correct ROM, and patch boot from the ROM to get root
https://forum.xda-developers.com/moto-g-power/how-to/moto-g-power-flashing-guide-t4159301
mingkee said:
Do not panic.
Follow this guide to flash correct ROM, and patch boot from the ROM to get root
https://forum.xda-developers.com/moto-g-power/how-to/moto-g-power-flashing-guide-t4159301
Click to expand...
Click to collapse
ive tried this. i either dont have (and dont know) which is the correct rom. or some other issue. i can get into fastboot mode, no problem. but when i type fastboot reboot fastboot i get that long list of commands, as if im typing in a bad command. and it does not go into fastbootd. i can, however, get into fastbootd through recovery. but every time i try to flash something there, it fails (no file or directory).
And i cant use LMSA cuz when i try to connect, it says the phone has incorrect firmware.
I have a US Unlocked Nord N200 5G that I bought recently.
I was trying to flash a GSI ROM to it, but apparently the ROM was in the wrong format or otherwise incompatible, because it just kept boot-looping with the OnePlus logo instead of actually booting into the ROM. (I got one that said it was "A/B format")
So, thankfully I get the Fastboot screen when I try to turn it on now. Either that or the Qualcomm CrashDump screen.
Easiest way would be to use the MSM tool, however only the T-Mobile variant of that has leaked. The program immediately told me I had the wrong model when I tried it.
I contacted OnePlus support, and after about 48 hours they said "sorry, we can't help you, wait for the next firmware update" so the idea of having them do a remote session to use the MSM tool is out of the question.
I have the extracted stock firmware files, however I don't have the fastboot commands to flash them. I tried to wing it, and get various errors.
So instead I followed the commands from this thread about converting the T-Mobile one to stock, and this is what I get.
First, "fastboot reboot fastboot" doesn't work - somehow the stock "recovery" thing got corrupted, so it's just the one that has START written in ASCII art at the top.
>fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (689036 KB) OKAY [ 17.058s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Click to expand...
Click to collapse
And it does the same for the other ones too. It won't let me flash "bluetooth" saying "Flashing is not allowed for Critical Partitions"
Other stuff gives me "fastboot: error: Could not check if partition vbmeta has slot all"
I'm using a current version of fastboot.exe.
I think the issue is I'm stuck in that fastboot mode, not the "fastbootd" mode with the fancier text on it... that seems to have been erased. "fastboot reboot recovery" takes me right back to the original fastboot screen.
I can put the phone in EDL mode, but without the right files I can't do anything else with it. What do you guys suggest? I have the OxygenOS 11.0.5.0.DE17AA files.
Sounds like the phone's not booting because the GSI you flashed doesn't match with the signatures in the stock vbmeta image. To fix this, you should flash a blank vbmeta image such as the one I attached with the following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta AOSPvbmeta.img
After that, your phone should stop bootlooping or crashdumping every time you try to boot it. After that, you can either flash a GSI or use the guide for converting the T-Mo N200 to stock to restore back to OxygenOS.
lzgmc said:
Sounds like the phone's not booting because the GSI you flashed doesn't match with the signatures in the stock vbmeta image. To fix this, you should flash a blank vbmeta image such as the one I attached with the following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta AOSPvbmeta.img
After that, your phone should stop bootlooping or crashdumping every time you try to boot it. After that, you can either flash a GSI or use the guide for converting the T-Mo N200 to stock to restore back to OxygenOS.
Click to expand...
Click to collapse
Thanks for the blank vbmeta.
I was able to flash that fine; but the phone still doesn't do anything. As I explained, my tinkering with it trying to follow the T-Mobile instructions to reflash partitions, I somehow managed to delete almost everything from the phone. Even doing "fastboot reboot fastboot" *does not get me into fastbootd mode*, just back to the original "dumb" fastboot mode.
Nothing is booting anymore because there's nothing left to boot!
And I can't use the MSM tool because this is not a T-Mobile phone, and the program knows that. It immediately fails saying the target model doesn't match the ROM I'm flashing to it.
Is there a way to override that with the MSM tool? Or am I SOL until OnePlus helps me? I was able to use fastbootd to delete the partitions but then it errored trying to remake them, and I'm left with basically nothing usable.
Possible answer Here
drfsupercenter said:
I have a US Unlocked Nord N200 5G that I bought recently.
I was trying to flash a GSI ROM to it, but apparently the ROM was in the wrong format or otherwise incompatible, because it just kept boot-looping with the OnePlus logo instead of actually booting into the ROM. (I got one that said it was "A/B format")
So, thankfully I get the Fastboot screen when I try to turn it on now. Either that or the Qualcomm CrashDump screen.
Easiest way would be to use the MSM tool, however only the T-Mobile variant of that has leaked. The program immediately told me I had the wrong model when I tried it.
I contacted OnePlus support, and after about 48 hours they said "sorry, we can't help you, wait for the next firmware update" so the idea of having them do a remote session to use the MSM tool is out of the question.
I have the extracted stock firmware files, however I don't have the fastboot commands to flash them. I tried to wing it, and get various errors.
So instead I followed the commands from this thread about converting the T-Mobile one to stock, and this is what I get.
First, "fastboot reboot fastboot" doesn't work - somehow the stock "recovery" thing got corrupted, so it's just the one that has START written in ASCII art at the top.
And it does the same for the other ones too. It won't let me flash "bluetooth" saying "Flashing is not allowed for Critical Partitions"
Other stuff gives me "fastboot: error: Could not check if partition vbmeta has slot all"
I'm using a current version of fastboot.exe.
I think the issue is I'm stuck in that fastboot mode, not the "fastbootd" mode with the fancier text on it... that seems to have been erased. "fastboot reboot recovery" takes me right back to the original fastboot screen.
I can put the phone in EDL mode, but without the right files I can't do anything else with it. What do you guys suggest? I have the OxygenOS 11.0.5.0.DE17AA files.
Click to expand...
Click to collapse
i have a bricked unlocked phone myself .. having the latest platform-tools is not enough for me to get anything on this phone .. mine is also rebooting on loop as i made the mistake and didn't unlock the OEM