The device did not reboot into fastboot but in stock recovery. When I choose Reboot to fastboot in the recovery menu the process continues in the rominstaller:
When I restart the device it boots up into fastbootmode. I do not know what the problem is. Are there alternatives that can help me to flash a ROM? I am open to all sugestions.
I am not entirely sure. When mine rebooted, it rebooted into the stock recovery as well, but it continued with the rest of the installation while it was in stock recovery. I think the partition not found errors is due to being manually rebooted into fastboot mode. The install should continue on it's own after it reboots without you having to do anything.
You may also need to update the adb drivers. I had recently installed the ADB, Fastboot and Drivers from the thread below while trying to get things to work, so that may help.
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
I am not entirely sure. When mine rebooted, it rebooted into the stock recovery as well, but it continued with the rest of the installation while it was in stock recovery. I think the partition not found errors is due to being manually rebooted into fastboot mode. The install should continue on it's own after it reboots without you having to do anything.
You may also need to update the adb drivers. I had recently installed the ADB, Fastboot and Drivers from the thread below while trying to get things to work, so that may help.
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
I am going to update the driver's and will let you know.
Just curious how long was the installation with your phone when you rebooted to stock recovery and did you see something happening in the cmd window? Last message in nu cmd window was <waiting for any device>
I am not entirely sure. When mine rebooted, it rebooted into the stock recovery as well, but it continued with the rest of the installation while it was in stock recovery. I think the partition not found errors is due to being manually rebooted into fastboot mode. The install should continue on it's own after it reboots without you having to do anything.
You may also need to update the adb drivers. I had recently installed the ADB, Fastboot and Drivers from the thread below while trying to get things to work, so that may help.
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
I am going to update the driver's and will let you know.
Just curious how long was the installation with your phone when you rebooted to stock recovery and did you see something happening in the cmd window? Last message inmy cmd window was <waiting for any device>
I am going to update the driver's and will let you know.
Just curious how long was the installation with your phone when you rebooted to stock recovery and did you see something happening in the cmd window? Last message in nu cmd window was <waiting for any device>
Thanx raptor7056,
I am going to update the driver's and will let you know.
Just curious how long was the installation with your phone when you rebooted to stock recovery and did you see something happening in the cmd window? Last message inmy cmd window was <waiting for any device>
I can't remember how long for sure, it was probably another 5 - 10 min. And yes, the CMD window continued to show what was being flashed similar to how it does before the reboot.
I can't remember how long for sure, it was probably another 5 - 10 min. And yes, the CMD window continued to show what was being flashed similar to how it does before the reboot.
Ok in the cmd window it continued... wondering why the flashing stops when I am trying to flash... it seems my device is not recognized when it reboots into stock recovery.
Ok in the cmd window it continued... wondering why the flashing stops when I am trying to flash... it seems my device is not recognized when it reboots into stock recovery.
Doing a quick Google search I wonder if it's because adb is not enabled in the stock recovery of the room you're using. You can take a look at the thread below, it might be helpful.
While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery but with ADB enabled...
Doing a quick Google search I wonder if it's because adb is not enabled in the stock recovery of the room you're using. You can take a look at the thread below, it might be helpful.
While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery but with ADB enabled...
Doing a quick Google search I wonder if it's because adb is not enabled in the stock recovery of the room you're using. You can take a look at the thread below, it might be helpful.
While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery but with ADB enabled...
I can't really answer that for sure. But I think the problem you're having now is that when it reboots back into the stock recovery there is no adb connection which is needed so it can continue installation after reboot.
You could try using the recovery from that thread in place of the recovery that is included in your fastboot rom to see if that works.
I can't really answer that for sure. But I think the problem you're having now is that when it reboots back into the stock recovery there is no adb connection which is needed so it can continue installation after reboot.
You could try using the recovery from that thread in place of the recovery that is included in your fastboot rom to see if that works.
Just tried the whole thing. My device boots to the recovery which I downloaded from the thread you mentioned...same issue the flashing does not continue and in the cmd window I see again <waiting for any device>.....
Just tried the whole thing. My device boots to the recovery which I downloaded from the thread you mentioned...same issue the flashing does not continue and in the cmd window I see again <waiting for any device>.....
Based on everything I am finding online it seems like this might be an issue with your drivers. It seems your phone isn't being recognized when it is booted into recovery.
The thread below might be helpful, otherwise I think you will have to do more research on why you have no adb when it reboots into recovery.
I had my phone rooted with the first official Android 11... I uninstalled root and completely reset the phone. Now I am on the second release of Android 11 and when I try to flash modified boot image in fastboot mode it says "Waiting for device"...
I don't know if it works but you could try to boot again into recovery to switch slots and flash again.
Before you boot to recovery you can see in TWRP (if you use this recovery) the current slot. After rebooting into recovery again you can check if you switched to the other slot.
Based on everything I am finding online it seems like this might be an issue with your drivers. It seems your phone isn't being recognized when it is booted into recovery.
The thread below might be helpful, otherwise I think you will have to do more research on why you have no adb when it reboots into recovery.
I had my phone rooted with the first official Android 11... I uninstalled root and completely reset the phone. Now I am on the second release of Android 11 and when I try to flash modified boot image in fastboot mode it says "Waiting for device"...
The only way from custom android 11 rom back to stock is via MSM unbrick tool. I was on Pixel Experience A11 and I tried many times flash to stock via fastboot and always got bootloop.
Is it ok to flash the EU version on top of a chinese device?
I'm asking this because I see partitions such as modem which might be problematic I guess..
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 8 Pro in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 8 Pro to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
REMEMBER "Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
Is it ok to flash the EU version on top of a chinese device?
I'm asking this because I see partitions such as modem which might be problematic I guess..
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 8 Pro in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 8 Pro to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
REMEMBER "Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
I want to thank all those who supported me, in 2 days I have already managed to buy the OnePlus 8 Pro, I will receive it in about a week and then I will immediately get to work. I will remove the link of the Paypal moneybox and let it close by itself so as to keep it in the historical (it will close tomorrow). A big thank you to everyone.
Step 1: Download your official firmware
Step 2: Extract payload.img
Step 3: Use Payload dumper to dump payload.image
Step 4: Copy dumped files to the root of the Fastboot rom directory
Step 5: Flash
As i told you privately the chinese TWRP is breaking TWRP gpl license and it has nothing to do with TWRP, it is wrong to even call it TWRP.
However yes, super can be mounted, decryption is a working in progress, the .zip flash was never tried for now, maybe some months it will be ready
forum.xda-developers.com
