Related
Hi all,
So I spent like the whole afternoon tryin to unlock bootloader on my MB860 (rooted) with no luck. This is international version with 2.3.4 system updated OTA.
I tried to unlock bootloader with fastboot - no luck:
Code:
OEM Unlock is not implemented
So i tried flash unlocked sbf file (intl-fix-try1.sbf), still no luck:
Code:
Failed to boot 1
So, I've flashed whole sbf file: 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.20-release-keys-signed-NonEFIGSRetail-EU.sbf
Phone started and all was same as before this operation,
next - I tried another full sbf's:
1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31-release-keys-signed-Retail-GB.sbf
1FF-olympus_latam-user-2.3.6-4.5.2A-51_OLL-17.8-111109-release-keys-signed-BellMobility-CA-GAS_NA_OLYMPUSGBCANADABELL_P019.sbf
On both - failed to boot 1
so in the end only sbf that actually allows me to boot my cell is 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.20-release-keys-signed-NonEFIGSRetail-EU.sbf
And the question is - how to get unlocked bootloader for this one?
You really should have searched and read up ahead of time. "Failed to boot XXX" is a perfectly normal and expected thing to happen when unlocking the BL. You shouldn't have messed with any more SBFs. You can still try running the fixer script as mentioned in that thread, hopefully you didn't mess it up too bad.
Thank you ravilov, but isn't this script only for ATT devices?
I am fairly certain it can be used on an international device as well.
Thanks, will try later on today, so what I'm lookin for is this thread:
http://forum.xda-developers.com/showthread.php?t=1182871
and option no.3 is what i should use from this script to have it fixed?
just for the records - the phone is working after i installed only sbf working, all setings and data were not affected, only will need to root it again
stingu said:
so what I'm lookin for is this thread:
http://forum.xda-developers.com/showthread.php?t=1182871
and option no.3 is what i should use from this script to have it fixed?
Click to expand...
Click to collapse
Yes.
stingu said:
just for the records - the phone is working after i installed only sbf working, all setings and data were not affected, only will need to root it again
Click to expand...
Click to collapse
Yeah, that's to be expected.
I think the worst case scenario would be that you won't be able to unlock, in which case you might be one of the unlucky people with the non-unlockable bootloader. If not, this script should help in unlocking your BL.
so, with the script and option number 3 i got the same thing:
Code:
(bootloader) OEM unlock is not implemented
OKAY [ -0.000s]
finished. total time: -0.000s
Or should i first flash small sbf and then use the script?
any other suggestions or am I stuck with soft 2.3.4?
You did flash the pudding/ihop SBF, right? If not, try doing that before you attempt to run oem unlock. If you did already... Well, I'm out of ideas then. I guess while waiting for someone else to chime in, you might as well start mentally preparing that you might indeed stay stuck with the stock firmware.
Well, made it unlocked, it was little bit tricky, so what I did:
-flashed IHOP
-got failed to boot 1 error message again - here, where i was not aware of - I pressed vol up and it switched to fastboot protocol support with boot error present
-did the script, fail to boot error was still there after reboot
-did those 2 points with flashboot application (whole instruction available here http://forum.xda-developers.com/showthread.php?t=1302423):
Code:
13.back in your command prompt window type "fastboot oem unlock" no quotes
14.You will now receive a warning along with a unique device ID
15.Type the following commands using your unique device ID (the numbers in the command prompt) in place of the ####•
fastboot oem unlock ####
fastboot reboot
Now its time to install CWM somehow...
Your device is corrupt. It can’t be
trusted and may not work properly.
Visit this link on another device:
go.co/ABH
Problem:
This is the ultimate warning, and you likely don’t want to see this message show up on your screen. Shall this appear, it would mean your device is not safe to use, not trusted and/r corrupted. The OS could still work, but there’s high chances you will encounter performance and security issues.
Consequence:
Before your device begins to start it will be shown:
Android system
There’s an internal problem with your device. Contact your manufacturer for details nexus 6p
Also:
The camera may be no longer properly work
Fixxed:
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
mfastboot flash system system.img
reboot bootloader
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastboot reboot-bootloader
fastboot flash vendor vendor.img
Important:
fastboot flashing lock_critical
Enjoy!
@tlip
A couple of notes. You should never advise anyone to flash the userdata.img, it'll result in the minimum commercially available storage size (32gb) being allocated to the device regardless of the actual storage size. So flashing userdata is only compatible with 32gb devices. The correct way to wipe/format the userdata is with this command:
Code:
fastboot format userdata
Also, bootloader reboots are only required after flashing the bootloader and the radio, so the sequence should be like this:
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
fastboot format userdata
fastboot reboot
And one more thing, you need to take more care when typing these instructions, you made a few errors, I'll highlight them:
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xxx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
[Color=red]m[/color]fastboot flash system system.img [Color=blue](extra m at beginning of command)[/color]
[Color=red]reboot bootloader[/color] [Color=blue](missing "fastboot" prefix, and hyphen between reboot and bootloader (fastboot reboot-bootloader))[/color]
fastboot flash cache cache.img
[Color=red]fastboot flash userdata userdata.img[/color] [color=blue](incorrect command as outlined above)[/color]
[Color=red]fastboot reboot-bootloader[/color] [Color=blue](unnecessary)[/color]
[Color=red]fastboot reboot-bootloader[/color] [Color=blue](another one?)[/color]
fastboot flash vendor vendor.img
I have that message when rebooting. Is this something I should be concerned about? My ignorance had me believing this was a standard screen for all unlocked bootloaders.
sandfreak said:
I have that message when rebooting. Is this something I should be concerned about? My ignorance had me believing this was a standard screen for all unlocked bootloaders.
Click to expand...
Click to collapse
Yes its a standard thing when you unlock b/l, I have it too. I think its just a security measure by Google. Relock b/l and the message should go.
Also you can just lock it with fastboot flashing lock, no need for the critical step unless you unlocked the b/l in the same way. Critical is only if you want to flash a custom bootloader, I believe.
EDIT: This info only applies for "Bootloader MAY BE Corrupt" and not "IS Corrupt". Different situation from the OP
Thanked @Heisenberg
Please OP, you give instructions that you expect people to follow and if they type in the wrong info could be fatal...
Seriously, this thread needs closed asap. All the above info( besides Heisenberg) is careless in itself, let alone posting it for others. Stop....just stop. Smh
Heisenberg said:
@tlip
A couple of notes. You should never advise anyone to flash the userdata.img, it'll result in the minimum commercially available storage size (32gb) being allocated to the device regardless of the actual storage size. So flashing userdata is only compatible with 32gb devices. The correct way to wipe/format the userdata is with this command:
Click to expand...
Click to collapse
I have for sure made this mistake before... One lesson learned the hard way
Dissmeister said:
Yes its a standard thing when you unlock b/l, I have it too. I think its just a security measure by Google. Relock b/l and the message should go.
Also you can just lock it with fastboot flashing lock, no need for the critical step unless you unlocked the b/l in the same way. Critical is only if you want to flash a custom bootloader, I believe.
Click to expand...
Click to collapse
I was under the impression that it was a bad idea to re-lock the BL after flashing. Something about not being able to flash stock images anymore? Whats the official word on this?
CNLiberal said:
I was under the impression that it was a bad idea to re-lock the BL after flashing. Something about not being able to flash stock images anymore? Whats the official word on this?
Click to expand...
Click to collapse
That's exactly right, locking the bootloader means you can't flash anything to the device.
CNLiberal said:
I was under the impression that it was a bad idea to re-lock the BL after flashing. Something about not being able to flash stock images anymore? Whats the official word on this?
Click to expand...
Click to collapse
Your post made me google this and I did find some people who did have issues like that, though they mention they cant unlock again. If this is what you're talking about, I'd say its a device specific issue; technically as far as Nexus (or correct flashing protocol) is concerned, you should be able to unlock and re-lock as you see fit. As Heisenberg mentioned, you cant flash anything on a locked b/l in the first place.
Personally I've never seen a reason to relock b/l after unlock but it depends on your circumstances.
Dissmeister said:
Yes its a standard thing when you unlock b/l, I have it too. I think its just a security measure by Google. Relock b/l and the message should go.
Also you can just lock it with fastboot flashing lock, no need for the critical step unless you unlocked the b/l in the same way. Critical is only if you want to flash a custom bootloader, I believe.
Click to expand...
Click to collapse
Actually if it says your bootloader may be corrupt which is normal. If it says your bootloader is corrupt that's bad. It can say Two different things. He said the second one
dontbeweakvato said:
Actually if it says your bootloader may be corrupt which is normal. If it says your bootloader is corrupt that's bad. It can say Two different things. He said the second one
Click to expand...
Click to collapse
That is one hell of a silly mistake. You're right, I apologize for not seeing that earlier. Will fix my previous reply so others dont get the wrong info from it. Thanks for that :good:
Dissmeister said:
Your post made me google this and I did find some people who did have issues like that, though they mention they cant unlock again. If this is what you're talking about, I'd say its a device specific issue; technically as far as Nexus (or correct flashing protocol) is concerned, you should be able to unlock and re-lock as you see fit. As Heisenberg mentioned, you cant flash anything on a locked b/l in the first place.
Personally I've never seen a reason to relock b/l after unlock but it depends on your circumstances.
Click to expand...
Click to collapse
The way I understood it, after I re-lock then need to unlock again, the phone will force a wipe. The old app Unlock Bootloder would lock and unlock in Android. You wouldn't have to reboot. I guess the developer believes that the new 6P can't perform this same function due to the nature of new locking/unlocking.
Hi Heisenberg,
as being rather new to the topic of unlocking and stuff that means, that I have to follow this (your) sequence for not running into that issue?
Does this hold true also for already having this problem, though?
Cheers, Rovaine
Rovaine said:
Hi Heisenberg,
as being rather new to the topic of unlocking and stuff that means, that I have to follow this (your) sequence for not running into that issue?
Does this hold true also for already having this problem, though?
Cheers, Rovaine
Click to expand...
Click to collapse
This "guide" is very poorly written, don't follow the instructions here. If you need instructions you can visit my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
As long as you're careful and follow my instructions properly you shouldn't haven't this problem.
Heisenberg said:
This "guide" is very poorly written, don't follow the instructions here. If you need instructions you can visit my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
As long as you're careful and follow my instructions properly you shouldn't haven't this problem.
Click to expand...
Click to collapse
Actually, I've tried to follow your guide to the point, but did -obviously- something wrong, hence this issue.
You've got any advice for starting all over -propperly- for getting rid of this issue?
I had this issue too after having "dirty flashed" Android 6.0.1 over Android 6.0.
I flashed system.img and boot.img, as usual through fastboot and never had any problems on "older" devices.
On my Nexus 6P I got this error too and the camera did not work. Having checked the logs I found the error.
You need to flash vendor.img too in order to fix it. You don´t have to relock your bootloader.
Gorgtech said:
I had this issue too after having "dirty flashed" Android 6.0.1 over Android 6.0.
I flashed system.img and boot.img, as usual through fastboot and never had any problems on "older" devices.
On my Nexus 6P I got this error too and the camera did not work. Having checked the logs I found the error.
You need to flash vendor.img too in order to fix it. You don´t have to relock your bootloader.
Click to expand...
Click to collapse
Just for getting it straight...
Initial situation:
Rooted device, latest Cyanoge installed, showing the described issue
How to solve:
Get angler-xxxxxx-factory-xxxxxxxx, unzip ...
"fastboot flash vendor C:\angler\images\vendor.img"
Gratulation issue solved?
Or do I have to get back to a certain state, like factory image fully restored or alike, of my device?
Exactly, you need the latest Factory Image for the Nexus 6P. Extract all content and only flash the vendor.img through fastboot.
Rovaine said:
Just for getting it straight...
Initial situation:
Rooted device, latest Cyanoge installed, showing the described issue
How to solve:
Get angler-xxxxxx-factory-xxxxxxxx, unzip ...
"fastboot flash vendor C:\angler\images\vendor.img"
Gratulation issue solved?
Or do I have to get back to a certain state, like factory image fully restored or alike, of my device?
Click to expand...
Click to collapse
Rovaine said:
Actually, I've tried to follow your guide to the point, but did -obviously- something wrong, hence this issue.
You've got any advice for starting all over -propperly- for getting rid of this issue?
Click to expand...
Click to collapse
Flash the factory images, instructions are in my guide.
Avoid and pass by a fool and a madman
wga0 said:
There's lots of posts about 'how to downgrade' at this forum, even I wrote it several times, but still many asks or complains there's nothing. Plz search it again. There're lots of info here. I write here a few ways again.
Most Simple, Fast, Safest way
1. Reboot your phone into bootloader
2. Change your active slot
Code:
adb reboot bootloader
fastboot getvar current-slot
fastboot set_active x
-- If your current-slot is a, x means b, and vice-versa
3. Reboot and do factory reset
These steps will revert your phone to the version exactly before the upgrade. That's your last, well worked version before upgrade. No root, No unlock, No flash required. All model, Any version possible.
Limitation: If you flashed the upgrade more than once, your previous version was deleted and this will not work. Then try next method.
Search Factory ROMs
Fortunately, BS Android 10 has no version info, and it seems that it doesn't check the region & model also. It means you can change the region & model, although it's not recommended.
https://forum.blackshark.com/discus...l-rom-joyui11-to-china-rom-joyui11-vice-versa (all the mega links he wrote here are from my post, and he said he tested it 100%... Just for info & not recommended)
So, find the Factory OTAs for your region first and flash it.
If there's none, then search it for most similar region and flash it.
If there's none also, then you can search it for most similar model, but it's not recommended. I guess it's better you to try next method
Limitation: Even if there's factory ROMs for your region, it doesn't guarantee the forward compatibility. You need to try find most good one. (Plz refer this post)
Search Fastboot ROMs
If you lost your previous version, if you can't find the factory ROMs, still you can downgrade with the Fastboot ROMs. BS team never release the Fastboot ROMs, but some people backed it and shares, or you can build it by yourself always. (Plz search about payload_dumper or image extractor)
But be careful. It doesn't check the sign(stock or modified), doesn't check the region, doesn't check the model. Even it doesn't check the image is a real image or not. It only requires 'Unlock bootloader'. If you unlocked your bootloader, you can use this method 100% possible, but it's dangerous if you don't know it exactly.
Limitation: It requires 'unlock'. After unlock, it's 100% possible, but be careful. It off all safeguard.
Click to expand...
Click to collapse
it really has a lot of tutorials, but with this new version and several variants, it is complicated to guide everyone ... I will test it on my DLT-H0 BS2 PRO and come back to talk ...
---------- Post added at 06:24 AM ---------- Previous post was at 05:34 AM ----------
Log error:
c:\adb>fastboot set_active a
Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
Nice tutorial, well done.
wga0 said:
Code:
fastboot getvar current-slot
fastboot set_active x
Click to expand...
Click to collapse
You can also run this command, it will change the slot to the other one, with just one command.
Code:
fastboot set_active other
Just tried this tuto for SKR-A0 without root JOYUI11 Android 10. The message: Slot Change is not allowed in Lock State appeared in ADB. Is there any way to downgrade without root or just to make my gps works again with GAPPS? Thx
I have an ANE-LX2 build number C636E4R1P5 (I live in Europe), latest security patch installed is from July 2020 and the OTA updater can't find any new update. It seems like on European firmware C432 the updates are released regularly. Is it possible to switch to this region and keep receiving updates?
I've read may threads but don't know where to start. Thanks in advance
ImFrengo said:
I have an ANE-LX2 build number C636E4R1P5 (I live in Europe), latest security patch installed is from July 2020 and the OTA updater can't find any new update. It seems like on European firmware C432 the updates are released regularly. Is it possible to switch to this region and keep receiving updates?
I've read may threads but don't know where to start. Thanks in advance
Click to expand...
Click to collapse
You have to unlock the bootloader first , for free or using paid service ,
info .
If you choose paid service , you have to download to EMUI 8 via HiSuite. If the rollback option is not available with your HiSuite ("switch to the older version" or "Earlier version"), you must downgrade to the lower EMUI 9.1 build number doing the dload method flashing Service ROM.
I can't give you a link because of forum rules, but you can google it, search for 'ANE-LX2 9.1.0.209(C636E4R1P5T8) FULL STOCK' (password: ministryofsolutions.com ).
Note: This process will erase your phone!
Then try again downgrade with HiSuite.
After successfully downgrading to Oreo you need downgrade to 8.0.140 , download here .
Running 8.0.140 you should be able to use HCU-Clent etc., get code and unlock your bootloader.
Only then will the difficult part of debranding come .
The question is whether it is worth doing...
-Alf- said:
You have to unlock the bootloader first , for free or using paid service ,
info .
If you choose paid service , you have to download to EMUI 8 via HiSuite. If the rollback option is not available with your HiSuite ("switch to the older version" or "Earlier version"), you must downgrade to the lower EMUI 9.1 build number doing the dload method flashing Service ROM.
I can't give you a link because of forum rules, but you can google it, search for 'ANE-LX2 9.1.0.209(C636E4R1P5T8) FULL STOCK' (password: ministryofsolutions.com ).
Note: This process will erase your phone!
Then try again downgrade with HiSuite.
After successfully downgrading to Oreo you need downgrade to 8.0.140 , download here .
Running 8.0.140 you should be able to use HCU-Clent etc., get code and unlock your bootloader.
Only then will the difficult part of debranding come .
The question is whether it is worth doing...
Click to expand...
Click to collapse
Thank you, HiSuite allows me to downgrade to 8.0.0.192.
After downgrading to 8.0.0.140 as well and unlocking the bootloader, is the debranding part particularly difficult?
ImFrengo said:
Thank you, HiSuite allows me to downgrade to 8.0.0.192.
After downgrading to 8.0.0.140 as well and unlocking the bootloader, is the debranding part particularly difficult?
Click to expand...
Click to collapse
Read the instructions carefully and completely, check unfamiliar terminology by google or xda.
Here you go
Ok, just one doubt: the files in the procedure are for ANE-LX1 while mine is ANE-LX2, does it make any difference?
ImFrengo said:
does it make any difference?
Click to expand...
Click to collapse
Of course.
Are all those 4 files (oeminfo, TWRP, stock recovery, service ROM) model-dependent? If yes, do you know where I can find the files for ANE-LX2?
Thank you
ImFrengo said:
Are all those 4 files (oeminfo, TWRP, stock recovery, service ROM) model-dependent?
Click to expand...
Click to collapse
Oeminfo and Service ROM only.
ImFrengo said:
If yes, do you know where I can find the files for ANE-LX2?
Click to expand...
Click to collapse
I thought you wanted to do a rebrand to ANE-LX1 C432 ...
P.S.: You might be better off staying on the C636
-Alf- said:
I thought you wanted to do a rebrand to ANE-LX1 C432 ...
Click to expand...
Click to collapse
Sorry about the confusion, I thought there was a specific C432 for ANE-LX2... I'm still new to this.
Does this mean my ANE-LX2 would "become" an ANE-LX1 C432?
ImFrengo said:
Does this mean my ANE-LX2 would "become" an ANE-LX1 C432?
Click to expand...
Click to collapse
Exactly.
-Alf- said:
Exactly.
Click to expand...
Click to collapse
Ok here's what I've done so far:
downgraded to 8.0.0.192 from HiSuite
downgraded to 8.0.0.140 following this
unlocked bootloader using HCU client (attached photo of phone in fastboot mode).
So now all I need to do is follow these steps?
Just double-checking before I do any damage to the phone
ImFrengo said:
So now all I need to do is follow these steps?
Click to expand...
Click to collapse
Yes, or these steps: Chapter 2.
"Chapter 2." is maybe simpler...
(I recommend reading the whole post!).
First flash oeminfo in TWRP, then continue with Chapter 2. !
These steps seem quite clear:
- In fastboot install TWRP, run
fastboot flash recovery_ramdisk TWRP-oreo-smart.img
fastboot reboot .
- Boot into TWRP and flash it over eRecovery :
-- select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe. Go back, find RECOVERY_RAMDISK-ANE-OREO file , mark Recovery, swipe. Reboot system, when yellow warning appears press and hold Volume Up.
- In TWRP select Install image and flash oeminfo.img file (mark oeminfo, swipe). Go back to main TWRP's menu, select Reboot > Power Off.
- Flash Service ROM using three buttons combo.
THE PROCESS WILL LOCK THE BOOTLOADER AGAIN!
Only thing is, what do you mean by "Flash Service ROM using three buttons combo."?
----
Edit: I guess it's standard dload method?
Also, should I add the ".img" at the end of the oeminfo file?
ImFrengo said:
Only thing is, what do you mean by "Flash Service ROM using three buttons combo."?
----
Edit: I guess it's standard dload method?
Click to expand...
Click to collapse
Power + both volume; standard.
ImFrengo said:
Also, should I add the ".img" at the end of the oeminfo file?
Click to expand...
Click to collapse
Yes.
Followed all the steps, bootloop after trying to install service rom
Is there a way to just take it back to the original state?
-Alf- said:
Power + both volume; standard.
Yes.
Click to expand...
Click to collapse
Either restoring the original or fixing the C432, either one is fine.. I'm still able to access TWRP, I don't know if that's useful
ImFrengo said:
Followed all the steps, bootloop after trying to install service rom
Click to expand...
Click to collapse
Your bootloader is locke or unlocked ? In fastboot run command
fastboot oem get-build-number
fastboot getvar vendorcountry
and post results.
ImFrengo said:
Is there a way to just take it back to the original state?
Click to expand...
Click to collapse
Only using the same procedure - oeminfo for C636 and service ROM 8.0.0.xxx C636 etc.
-Alf- said:
Your bootloader is locke or unlocked ? In fastboot run command
fastboot oem get-build-number
fastboot getvar vendorcountry
and post results.
Click to expand...
Click to collapse
C:\platform-tools>fastboot oem get-build-number
(bootloader) :System 8.0.0.046(0CXB)
OKAY [ 0.006s]
Finished. Total time: 0.008s
C:\platform-tools>fastboot getvar vendorcountry
vendorcountry: hw/eu
Finished. Total time: 0.005s
Fastboot screen on the phone shows "phone locked"
i have a pixel 6 verizon and need to downgrade the firmware to android 13 october 2022. The only way to do that is via OTA image flash but whenever i try it does not flash since it cannot downgrade bootloader. the phone cannot be oem unlocked. my only chance is to edit/remove boot.img and/or modify the script to prevent the bootloader flash. i've found payload file dumpers but only to extract the images within. is there any way to do this? i know it can be don for the full system images rather easy.
ronclone said:
i have a pixel 6 verizon and need to downgrade the firmware to android 13 october 2022. The only way to do that is via OTA image flash but whenever i try it does not flash since it cannot downgrade bootloader. the phone cannot be oem unlocked. my only chance is to edit/remove boot.img and/or modify the script to prevent the bootloader flash. i've found payload file dumpers but only to extract the images within. is there any way to do this? i know it can be don for the full system images rather easy.
Click to expand...
Click to collapse
are you looking for a way to edit the extracted images?
If so I think you might be able to edit the extracted boot images with a text editor although not sure how reliable my information is for that
catcatjpg said:
are you looking for a way to edit the extracted images?
If so I think you might be able to edit the extracted boot images with a text editor although not sure how reliable my information is for that
Click to expand...
Click to collapse
yes, i would like to edit the image to skip flashing the bootloader. however, OTA images are different than full factory images. they do not have an easy way to modify a "flash-all.bat" file or equivalent. therefore my question, i would like to know if something like this is posible at all.
ronclone said:
i have a pixel 6 verizon and need to downgrade the firmware to android 13 october 2022. The only way to do that is via OTA image flash but whenever i try it does not flash since it cannot downgrade bootloader. the phone cannot be oem unlocked. my only chance is to edit/remove boot.img and/or modify the script to prevent the bootloader flash. i've found payload file dumpers but only to extract the images within. is there any way to do this? i know it can be don for the full system images rather easy.
Click to expand...
Click to collapse
The bootloader has to be unlocked to manually flash a factory image or OTA. Since you have a Verizon device you cannot unlock your bootloader, so attempting to flash any image of any kind will fail. Worse, even if you did have an unlocked device, without a custom recovery you won't be able to flash modified factory images. The stock recovery checks for the presence of Google's signature in the factory image and, if it doesn't find it, will refuse to flash the package.
Modifying flash-all.bat to not flash the bootloader by commenting out the proper line in the batch file will work since you're not modifying the images themselves, but the point is moot anyway since you cannot manually flash factory images due to that pesky bootloader.
That's the issue. However just to clarify, I absolutely can flash OTA images via fastboot even with a locked bootloader, I've done it multiple times. What I can't do is flash full factory images, the ones that need an unlocked bootloader.
I stand corrected regarding the flashing of OTA update files. Flashing full OTA images is conceivably possible, considering that I forgot Google gave device owners that capability. However, this doesn't change the fact you cannot alter Google-supplied ROM images without losing Google's signature on those files. So you won't be able to flash an OTA without also flashing the bootloader.
So is there a specific reason you have to have that particular bootloader?
It's not a bootloader problem per se. It's an Android version problem for me. I wouldn't mind downgrading the bootloader, is just that pixel devices apparently cannot downgrade bootloeader so it must be done with some kind of trickery.
Your on a device with an unlockable bootloader.
You can only flash official ota zips in recovery provided you are not downgrading.
Any attempt to manipulate the OTA zip will break the Google signature, and therefore any attempt to flash it on a locked bootloader will fail.
Tldr: forget about it
shoey63 said:
Your on a device with an unlockable bootloader.
You can only flash official ota zips in recovery provided you are not downgrading.
Any attempt to manipulate the OTA zip will break the Google signature, and therefore any attempt to flash it on a locked bootloader will fail.
Tldr: forget about it
Click to expand...
Click to collapse
yeah i think you're right. unfortunately.