I am not able to flash the Android P Developer image.
I was under the impression this could be done without having to unlock the bootloader by editing the script to remove -w
Clearly I must be missing something here.
Code:
bob$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader_b' (36344 KB)...
OKAY [ 0.775s]
writing 'bootloader_b'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.776s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 1.610s]
writing 'radio_b'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 1.611s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.251s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.031s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2152 MB) to disk... took 13.216s
archive does not contain 'system.sig'
extracting system_other.img (332 MB) to disk... took 2.352s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (366 MB) to disk... took 2.367s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
--------------------------------------------
Bootloader Version...: TMZ12bb
Baseband Version.....: g8998-00164-1710262031
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
FAILED
Device version-bootloader is 'TMZ12bb'.
Update requires 'TMZ20f'.
finished. total time: 0.004s
bob$
OK fine try each of the components with fastboot in the image:
Code:
fastboot flash bootloader bootloader-taimen-tmz20f.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (36344 KB)...
OKAY [ 0.957s]
writing 'bootloader_b'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.958s
bob$
So whats happening here?
You do need to unlock your bootloader in order to flash factory images. Removing -W from flash-all.bat file is just going to keep your data. Nothing else.
Obviously it's because your boot loader is locked
People like you brick systems because you don't read
You CANNOT flash a system image without unlocking your bootloader.
You CAN sideload an OTA update without unlocking your bootloader.
You can sideload the OTA for P via adb.
But, there is no OTA update for going back to O. That will happen when the public beta starts in May.
To go back before the public beta starts, you will have to flash the system image for which you will need to unlock your bootloader.
flex360 said:
Obviously it's because your boot loader is locked
People like you brick systems because you don't read
Click to expand...
Click to collapse
Flashing a stock ROM on an android phone should not require an unlocked bootloader to be fair. It's people like Google that force people to brick their systems using stupid systems. It's also people like you who offer zero help on forums.
Thanks Jonathan-H. I didn't see a OTA for Android P. I had been flashing OTA's in the past and that had me a bit confused. ("I swear I did this before, why not now"). Been a while as I had not flashed anything onto my N6P while I had it. The problem I have run into with my Pixel is that it happens to be one of those Google shipped out that can't be bootloader unlocked. My understanding is that I can do this by doing a factory reset, but I didn't want to loose all the apps and data, and go through the process of re-downloading every single one. I know its generally recommended to start clean.
Jonathan-H said:
Flashing a stock ROM on an android phone should not require an unlocked bootloader to be fair. It's people like Google that force people to brick their systems using stupid systems. It's also people like you who offer zero help on forums.
Click to expand...
Click to collapse
To be fair... Google isn't forcing anybody to unlock their bootloaders. That's up to you. Anyone who knows what they are doing flashing system images will be just fine. You don't appear to be one of those people.
borillion_star said:
Thanks Jonathan-H. I didn't see a OTA for Android P. I had been flashing OTA's in the past and that had me a bit confused. ("I swear I did this before, why not now"). Been a while as I had not flashed anything onto my N6P while I had it. The problem I have run into with my Pixel is that it happens to be one of those Google shipped out that can't be bootloader unlocked. My understanding is that I can do this by doing a factory reset, but I didn't want to loose all the apps and data, and go through the process of re-downloading every single one. I know its generally recommended to start clean.
Click to expand...
Click to collapse
https://developer.android.com/preview/download-ota.html
Be aware, while generally speaking, you should be fine doing OTA. However, with a locked bootloader, if you have any issue and something goes awry, you will have a brick.
Jonathan-H said:
Flashing a stock ROM on an android phone should not require an unlocked bootloader to be fair. It's people like Google that force people to brick their systems using stupid systems. It's also people like you who offer zero help on forums.
Click to expand...
Click to collapse
No, it's people like the OP of this thread who expect to be spoon fed information that is already covered extensively in other threads. Including the thread dedicated to this EXACT situation of trying to flash Android P. A very small amount of reading in the below thread would have quickly answered the OP's questions.
[ROM NEWS] Android P - Root+Theme Support
Quite frankly, the fact that he thinks he can flash a factory image without unlocking the bootloader shows that he shouldn't be messing with his phone at all. Absolutely none of this is Google's fault.
sn0warmy said:
No, it's people like the OP of this thread who expect to be spoon fed information that is already covered extensively in other threads. Including the thread dedicated to this EXACT situation of trying to flash Android P. A very small amount of reading in the below thread would have quickly answered the OP's questions.
[ROM NEWS] Android P - Root+Theme Support
Quite frankly, the fact that he thinks he can flash a factory image without unlocking the bootloader shows that he shouldn't be messing with his phone at all. Absolutely none of this is Google's fault.
Click to expand...
Click to collapse
Also from the official website where you download the images it has instruction which include needing to unlock the bootloader for full images. And also tells you that OTA do not require unlocking the bootloader.
Related
I was trying to flash android 8.1 to my new Pixel 2 XL after it didn't OTA well, then the device got stuck in bootloop,
then decided to go back to 8.0 and got the error: Cannot generate image for userdata
full :
target reported max download size of 536870912 bytes
sending 'bootloader_a' (55680 KB)...
OKAY [ 47.517s]
writing 'bootloader_a'...
OKAY [ 0.552s]
finished. total time: 48.072s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 51.809s]
writing 'radio_a'...
OKAY [ 0.566s]
finished. total time: 52.379s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.253s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.034s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1867 MB) to disk... took 12.752s
archive does not contain 'system.sig'
extracting system_other.img (590 MB) to disk... took 4.501s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
extracting vendor.img (341 MB) to disk... took 2.588s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
CreateProcess failed: %1 is not a valid Win32 application. (193)
error: Cannot generate image for userdata
Press any key to exit...
anyone has any idea how to solve it ?
before flashing the device was rooted with magisk and had twrp installed
I had the same error on MacOS, no idea how to resolve it so I used the skipsoft toolkit to flash-all
Make sure you have the latest fastboot binary installed from Google.
I'd try and flash January Security again. It should work if you run the flash-all
you can try this method, it really helped me when an update didn't work. I use it now to make every update, so I don't have any problems.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
thanks for the answers I tried flash-all with the latest android platform tools this is what gave me the error of image for userdata...
SkipSoft doesn't seem to support the new 2017 Pixel 2 XL..
phildenice said:
you can try this method, it really helped me when an update didn't work. I use it now to make every update, so I don't have any problems.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
yeah I tried it gave me the same error of the userdata image..
You could try to unzip system.img and flash individually
hi I also tried flashing individualy (after flash-all failed) and I got the same error - userdata.img
You could try to unzip system.img and flash individually
You might wanna try using fastboot to format the userdata partition; be sure to format partition on both a & b slots...
If you need help or more clarification, let me know...
Hope this helps...
Sorry I didn't see your answer
---------- Post added at 11:27 AM ---------- Previous post was at 11:18 AM ----------
And try :
fastboot format userdata
to see if solves the issue
REM_8 said:
I was trying to flash android 8.1 to my new Pixel 2 XL after it didn't OTA well, then the device got stuck in bootloop,
then decided to go back to 8.0 and got the error: Cannot generate image for userdata
.................................
Click to expand...
Click to collapse
A few things to check that have messed other users up as well:\
make sure you unzipped the factory image then unzip the second zip file for the boot img
make sure OEM unlock is ON
make sure USB Debugging is ON
make sure you have a 2.0 USB cable
try rebooting your PC
make sure your SDK tools are the LATEST version
make sure you're getting your command prompt in the same folder as your platform tools
not saying these will fix your issue, but have seen these trip up others..
Good luck.
Az Biker said:
A few things to check that have messed other users up as well:\
make sure you unzipped the factory image then unzip the second zip file for the boot img
make sure OEM unlock is ON
make sure USB Debugging is ON
make sure you have a 2.0 USB cable
try rebooting your PC
make sure your SDK tools are the LATEST version
make sure you're getting your command prompt in the same folder as your platform tools
not saying these will fix your issue, but have seen these trip up others..
Good luck.
Click to expand...
Click to collapse
Flash-all doesn't like unzipping the second folder. At least it didn't for me.
Larzzzz82 said:
Flash-all doesn't like unzipping the second folder. At least it didn't for me.
Click to expand...
Click to collapse
Extract the secondary zip, and place it in your SDK platform-tools folder. Then try again.
I did that. That's why I said flash-all doesn't like that. I moved the unzipped second folder into my platform tools folder and all went well.
Flashing this device is nothing like Shamu was.
Larzzzz82 said:
I did that. That's why I said flash-all doesn't like that. I moved the unzipped second folder into my platform tools folder and all went well.
Flashing this device is nothing like Shamu was.
Click to expand...
Click to collapse
I hear that bro. Not like the 6p either. But we'll manage :good:
I rooted my phone near the launch of the Pixel 2 so I could get wifi tether to work with my gUDP Verizon plan (device is from Google). I am still on 8.0 and having issues updating to 8.1. I'm having a lot of issues with crashing apps etc so I'm hoping updating will help.
I've tried a few methods unsuccessfully. I tried to do the uninstall with Magisk but it stated that the boot files weren't there. I deleted Magisk per another set of instructions and attempted to sideload and failing there as well.
I can get the phone connected with ADB. The bootloader is unlocked still. After that, I'm at a loss at what to do next. Any assistance would be appreciated its been a few years since I've messed around this stuff and obviously, things have changed and/or I've gotten dumber.
Download the full factory image, the latest.
Unzip it into your platform tools folder.
Find the flash-all.bat file and open it with notepad and edit out the -w and save it. Removing that saves your data apps and settings.
Open a command prompt in your platform tools folder
Connect the phone to the PC
Adb reboot bootloader
flash-all.bat
Reboot, redo your root and wifi tether haxk
I attempted this and the following occured. I attempted to use the Dec update and got the same errors. Do I have to start from the Nov update, then do Dec, then Jan?
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (36344 KB)...
OKAY [ 6.458s]
writing 'bootloader_b'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 6.461s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 4.517s]
writing 'radio_b'...
OKAY [ 0.572s]
finished. total time: 5.091s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.228s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.029s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1936 MB) to disk... took 21.596s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 6.476s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (349 MB) to disk... took 3.851s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
--------------------------------------------
Bootloader Version...: TMZ10n
Baseband Version.....: g8998-00164-1710262031
Serial Number........: 711KPED0781084
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
FAILED
Device version-bootloader is 'TMZ10n'.
Update requires 'TMZ12b'.
finished. total time: 0.016s
Press any key to exit...
jdougal11 said:
I attempted this and the following occured. I attempted to use the Dec update and got the same errors. Do I have to start from the Nov update, then do Dec, then Jan?
Click to expand...
Click to collapse
Did you first unlock your bootloader critical partition?
fastboot flashing unlock_critical
Same here, my apps crash like crazy and i factory reset like 3 times but still same problem except that now is only social apps and a couple games that keeps crashing and not even reinstalling and fixes the problem
Hi guys,
Please help me with my phone.
I have my pixel XL rooted and accidentally upgraded to android 10 and lost my root.
However, when i was in the process of trying to re-root the phone, i probably did something stupid and got my phone soft bricked with the phone turning into to a bootloop showing the Google sign and the screen on booting up.
I am able to enter the bootloader screen and tried to flash the Factory Stock image, from the old version such as 7.1.0 to the new version 10.0.0 but failed.
This is the message i got every time i flash the factory image.
============================================================
Microsoft Windows [版本 10.0.18362.720]
(c) 2019 Microsoft Corporation. 著作權所有，並保留一切權利。
D:\Program Files (x86)\Android\Minimal ADB and Fastboot\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32480 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.060s]
finished. total time: 2.950s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_a' (57156 KB)...
OKAY [ 1.550s]
writing 'radio_a'...
OKAY [ 0.498s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.053s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (30 MB) to disk... took 0.325s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1998 MB) to disk... took 9.441s
archive does not contain 'system.sig'
extracting system_other.img (293 MB) to disk... took 1.527s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (253 MB) to disk... took 1.275s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
CreateProcess failed: 蝟餌絞?曆??唳?摰?瑼???(2)
error: Cannot generate image for userdata
Press any key to exit...
;urgently need your help.
sam
samsam2020 said:
Hi guys,
Please help me with my phone.
I have my pixel XL rooted and accidentally upgraded to android 10 and lost my root.
However, when i was in the process of trying to re-root the phone, i probably did something stupid and got my phone soft bricked with the phone turning into to a bootloop showing the Google sign and the screen on booting up.
I am able to enter the bootloader screen and tried to flash the Factory Stock image, from the old version such as 7.1.0 to the new version 10.0.0 but failed.
This is the message i got every time i flash the factory image.
============================================================
Microsoft Windows [版本 10.0.18362.720]
(c) 2019 Microsoft Corporation. 著作權所有，並保留一切權利。
D:\Program Files (x86)\Android\Minimal ADB and Fastboot\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32480 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.060s]
finished. total time: 2.950s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_a' (57156 KB)...
OKAY [ 1.550s]
writing 'radio_a'...
OKAY [ 0.498s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.053s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (30 MB) to disk... took 0.325s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1998 MB) to disk... took 9.441s
archive does not contain 'system.sig'
extracting system_other.img (293 MB) to disk... took 1.527s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (253 MB) to disk... took 1.275s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
CreateProcess failed: 蝟餌絞?曆??唳?摰?瑼???(2)
error: Cannot generate image for userdata
Press any key to exit...
;urgently need your help.
sam
Click to expand...
Click to collapse
You installed an Android 10 factory image, please DO NOT try installing an Android 7xx factory image.
If your bootloader is unlocked try this using this Guide:
- First, remove (uninstall) Minimal ADB from your computer.
- Second, download and install SDK Platform-tools r29.0.6 on your computer. There is a link in the guide: Prerequisites c.
- You are on Android 10 Factory Image (10.0.0 (QP1A.191005.007.A3, Dec 2019)) so just do # 9 in the guide to root/reroot.
Note: Check your bootloader and radio version.
Why? You tried to flash an Android 7xx factory image and it look like the Android 7xx bootloader and radio replaced the Android 10 bootloader and radio.
If your bootloader and radio are not:
- bootloader-marlin-8996-012001-1908071822.img
- radio-marlin-8996-130361-1905270421.img
Open a command prompt #1 in the guide and flash them:
Code:
fastboot flash bootloader bootloader-marlin-8996-012001-1908071822.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-130361-1905270421.img
fastboot reboot-bootloader
Homeboy76 said:
You installed an Android 10 factory image, please DO NOT try installing an Android 7xx factory image.
If your bootloader is unlocked try this using this Guide:
- First, remove (uninstall) Minimal ADB from your computer.
- Second, download and install SDK Platform-tools r29.0.6 on your computer. There is a link in the guide: Prerequisites c.
- You are on Android 10 Factory Image (10.0.0 (QP1A.191005.007.A3, Dec 2019)) so just do # 9 in the guide to root/reroot.
Note: Check your bootloader and radio version.
Why? You tried to flash an Android 7xx factory image and it look like the Android 7xx bootloader and radio replaced the Android 10 bootloader and radio.
If your bootloader and radio are not:
- bootloader-marlin-8996-012001-1908071822.img
- radio-marlin-8996-130361-1905270421.img
Open a command prompt #1 in the guide and flash them:
Code:
fastboot flash bootloader bootloader-marlin-8996-012001-1908071822.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-130361-1905270421.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
:good::good::good:
Very GOOD man!
Just tried and i was able to restore the factory image
also rooted my phone again!!
Million thanks for your help.
pics, pardon the **** quality
Tried rooting it, fastboot works but ADB doesn't seem to recognise my device. I went to the link it gave me and followed the tutorial it gave me clicked on it hopes of at least getting back to stock, but at the step were I run the bash script (flash-all.sh) it errors out.
Spoiler: flash-all.sh output
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (4610 KB)...
OKAY [ 0.212s]
writing 'bootloader'...
OKAY [ 0.154s]
finished. total time: 0.366s
rebooting into bootloader...
OKAY [ 0.019s]
finished. total time: 0.069s
target reported max download size of 536870912 bytes
sending 'radio' (56630 KB)...
OKAY [ 1.463s]
writing 'radio'...
OKAY [ 0.535s]
finished. total time: 1.998s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.070s
extracting android-info.txt (0 MB)...
extracting boot.img (11 MB)...
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (17 MB)...
archive does not contain 'recovery.sig'
extracting system.img (1909 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (185 MB)...
archive does not contain 'vendor.sig'
wiping userdata...
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.44.5 (15-Dec-2018)
/tmp/TemporaryFile-QFwJ4m: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Where/how can I fix my mess via fastboot or something else?
Extract Android 10 rom and flash the images.
jjgvv said:
Extract Android 10 rom and flash the images.
Click to expand...
Click to collapse
Wouldn't Android 10 run like crap on the Nexus 5X, though? I've only tried some of the 8.1 ROMs, that's the highest it goes on the official page.
seething_n00b said:
Wouldn't Android 10 run like crap on the Nexus 5X, though? I've only tried some of the 8.1 ROMs, that's the highest it goes on the official page.
Click to expand...
Click to collapse
It will not run like crap but will also not be very fast.
seething_n00b said:
Wouldn't Android 10 run like crap on the Nexus 5X, though? I've only tried some of the 8.1 ROMs, that's the highest it goes on the official page.
Click to expand...
Click to collapse
custom rom, 8.1 is Google Offical firmware, offical firmware wont extract ot so
Solved on my own by realising I could just flash TWRP via fastboot. Duh.
jjgvv said:
custom rom, 8.1 is Google Offical firmware, offical firmware wont extract ot so
Click to expand...
Click to collapse
"8.1 won't work, so try 10!" You're even more of an idiot than me.
nope,8.1 is offical ota and can not be flashed in fastboot but only in recovery.
Hello, I am trying to unroot my phone and relock the bootloader, but I am having some troubles.
After some trial and error with various forums guides here on XDA, I have been trying to use the Tool All in One, the MSM, but nothing is working. Furthermore, I am worried that I have bricked my phone.
The things I have done so far are:
Initially, I rooted the phone with Magisk. During this, I made a file that told my GPS to be where an application wanted it to be, and saved is a system file.
I have since decided to resell the phone and the buyer wants it to be stock. So, I tried the above mentioned tools of Tool All In one, and tried to flash a stock rom but it gave me an error.
I tried MSM but the device comes back as an error to do with serial number or something.
Whilst playing around with these tools, I have some how sent the phone into a permanent fastboot state and I am unable to reboot into any other state, and so I tried to use the guide found here, https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/
This just lead to another failure, where it said I don't have the partitian.
If anyone can help me just get the phone to being a stock phone with no bootloader unlock, that would be great. Happy to chat over Discord if that helps!
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: c9c9ee59
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
android-info.txt syntax error: require product=msmnile
Setting current slot to 'a' OKAY [ 0.008s]
extracting boot.img (96 MB) to disk... took 0.262s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB) OKAY [ 2.328s]
Writing 'boot_a' OKAY [ 0.422s]
extracting dtbo.img (16 MB) to disk... took 0.038s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (16384 KB) OKAY [ 0.399s]
Writing 'dtbo' OKAY [ 0.059s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.012s]
Writing 'vbmeta' OKAY [ 0.003s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
extracting odm.img (100 MB) to disk... took 0.227s
archive does not contain 'odm.sig'
Sending 'odm' (102400 KB) OKAY [ 2.426s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Press any key to exit...
This is what I get when I try to use https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/
"fastboot reboot fastboot" to get into fastbootD and then reflash all partitions
In case anyone stumbles across this one day looking for a fix, I found one. My issue was that msm would not connect to sahara and tool all in one wouldn't lock the boot loader without the phone becoming corrupt. To make matters worse, through out all this I lost the ability to use adb and had to use fastboot, and even worse, I some how lost the os entirely and was only able to get into the boot loader.
So the fix for all of this, aka, how to get back to entirely stock software with no root or Bootloader unlocked is this:
1. Install lineageos recover and then os using fast boot so there is at least an operating system and ability to use adb again.
2. Start the phone entirely so you know it works
3. Go back to the bootloader and Install twrp recover
4. Format phone and then adb sideload oxygen os
5. boatload lock with Tool all in one
And wallah it was fixed. If someone needs to know the exact step by step I'm sure I might reply again one day but for now, I'm going to bed!