Develop Bugs

[Q] converted vzw M8 to Tmo, but can't update firmware

Hey everyone,
new here and to rooting/flashing in general.
I've somewhat successfully converted my verizon M8 to work on Tmobile by using weaksauce 2.0 to root, then Sunshine to gain S-off. Flashed TRWP custom recovery with flashify, backed up my stock vzw setup (4.4.4), then flashed ViperoneM8 with tmobile extras to the phone. The phone works great 90% of the time on Tmo, with 4gLTE, mms, sms, wifi all working. But I will get random dropped general mobile service (no data, can't make calls, text won't go through). This is easily fixed with airplane mode toggle.
Sooo, I wanted to see how other roms work on my phone with Tmobile service, specifically ARHD 34.0 and/or change phone to developer edition and upgrade to Lollipop. But both roms require prerequisite upgrading of firmware. My phone won't let me change the firmware via ADB or RUU. I've tried changing to superCID and going back to relocked mode, but still won't work. I get error 155 when attempting to upgrade via RUU and cannot find firmware.zip when using adv/fastboot.
I came across an old thread about other rooted models that suggest upgrading the HBOOT. Can anyone verify this suggestion and guide me toward which specific HBOOT software to change to?
Thanks for the help,
-Ant

Tritan84 said:
Hey everyone,
new here and to rooting/flashing in general.
I've somewhat successfully converted my verizon M8 to work on Tmobile by using weaksauce 2.0 to root, then Sunshine to gain S-off. Flashed TRWP custom recovery with flashify, backed up my stock vzw setup (4.4.4), then flashed ViperoneM8 with tmobile extras to the phone. The phone works great 90% of the time on Tmo, with 4gLTE, mms, sms, wifi all working. But I will get random dropped general mobile service (no data, can't make calls, text won't go through). This is easily fixed with airplane mode toggle.
Sooo, I wanted to see how other roms work on my phone with Tmobile service, specifically ARHD 34.0 and/or change phone to developer edition and upgrade to Lollipop. But both roms require prerequisite upgrading of firmware. My phone won't let me change the firmware via ADB or RUU. I've tried changing to superCID and going back to relocked mode, but still won't work. I get error 155 when attempting to upgrade via RUU and cannot find firmware.zip when using adv/fastboot.
I came across an old thread about other rooted models that suggest upgrading the HBOOT. Can anyone verify this suggestion and guide me toward which specific HBOOT software to change to?
Thanks for the help,
-Ant
Click to expand...
Click to collapse
If your stock was 4.4.4, your firmware and hboot should be fine to run ARHD. I don't think that WWE firmware (x.xx.401.x) is compatible with T-Mo (x.xx.531.x). The firmware you have now (3.32.531.2?) will be fine.

xunholyx said:
If your stock was 4.4.4, your firmware and hboot should be fine to run ARHD. I don't think that WWE firmware (x.xx.401.x) is compatible with T-Mo (x.xx.531.x). The firmware you have now (3.32.531.2?) will be fine.
Click to expand...
Click to collapse
I'll go ahead and try to flash ARHD 34 and see how it goes on TMo. It does say that firmware upgrade should be done prior. Think I'll run in to the wifi/network issues?

Tritan84 said:
I'll go ahead and try to flash ARHD 34 and see how it goes on TMo. It does say that firmware upgrade should be done prior. Think I'll run in to the wifi/network issues?
Click to expand...
Click to collapse
You shouldn't have wifi issues. ViperOne is building a Lollipop version right now, and 4.4.4 firmware works fine with it.
The ARHD thread does recommend a full wipe with the non-matching firmware/ROM base though.

xunholyx said:
You shouldn't have wifi issues. ViperOne is building a Lollipop version right now, and 4.4.4 firmware works fine with it.
Click to expand...
Click to collapse
OK cool. I'll give it a shot. I really like the Viperone rom, but it's just annoying to have a random loss of network a couple times a day and having to toggle airplane mode. Any thoughts on why that would be happening?

Tritan84 said:
OK cool. I'll give it a shot. I really like the Viperone rom, but it's just annoying to have a random loss of network a couple times a day and having to toggle airplane mode. Any thoughts on why that would be happening?
Click to expand...
Click to collapse
Probably because of the conversion from Verizon to T-Mo.

xunholyx said:
Probably because of the conversion from Verizon to T-Mo.
Click to expand...
Click to collapse
EMERGENCY!! stuck in bootloader/fastboot loop! Won't allow me to go into recovery. Won't allow factory reset. The ROM said it installed succesfully. Banner says modified/Relocked. trying to unlock via htcdev unlock code but fastboot says cannot load 'Unlock_code.bin'
Please help

Tritan84 said:
EMERGENCY!! stuck in bootloader/fastboot loop! Won't allow me to go into recovery. Won't allow factory reset. The ROM said it installed succesfully. Banner says modified/Relocked. trying to unlock via htcdev unlock code but fastboot says cannot load 'Unlock_code.bin'
Please help
Click to expand...
Click to collapse
Oh man, what did you do? In your bootloader under OS is your firmware number. Is it still your old firmware? I don't know how you re-locked.
If you are in fastboot, type fastboot reboot-recovery and see if that works.

xunholyx said:
Oh man, what did you do? In your bootloader under OS is your firmware number. Is it still your old firmware? I don't know how you re-locked.
If you are in fastboot, type fastboot reboot-recovery and see if that works.
Click to expand...
Click to collapse
OS-3.28.605.4 (4.16.1540.8)
when i put in fastboot reboot-recovery, just a long list of commands show up

Tritan84 said:
OS-3.28.605.4 (4.16.1540.8)
when i put in fastboot reboot-recovery, just a long list of commands show up
Click to expand...
Click to collapse
I was relocked previously trying to update firmware. I completely forgot to unlock it before the ROM flash. I would assume the ROM wouldnt flash though if the phone was relocked. I'm still S-off. Fastboot isn't recognizing the files i want to flash. Won't flash the unlock code. Wouldn't flash a zip file before when trying to update firmware. Can I somehow fix why fastboot isn't flashing files, then try to use unlock code?

possible progress?? I wasn't in the correct file to fastboot flash files. I moved the unlock code download to the correct file as flashboot, then flashed it. It says "unlock token check successfully." but now it seems the phone is stuck in white htc screen. Is it ok to power down the phone when in this screen? maybe loading the software from new ROM?
so I went ahead and powered down the phone. Still S-off. Now has UNLOCKED banner, but behaving the same. Stuck in bootloader loop. Won't allow me to get into recovery

Tritan84 said:
I was relocked previously trying to update firmware. I completely forgot to unlock it before the ROM flash. I would assume the ROM wouldnt flash though if the phone was relocked. I'm still S-off. Fastboot isn't recognizing the files i want to flash. Won't flash the unlock code. Wouldn't flash a zip file before when trying to update firmware. Can I somehow fix why fastboot isn't flashing files, then try to use unlock code?
Click to expand...
Click to collapse
Okay. Being S-Off you don't need to lock your bootloader to flash firmware. But since you were trying to flash Developer Edition firmware, you would have to flash a stock Dev Ed backup first, and change your MID and CID.
Leave your phone plugged into your PC.
Go here and follow the option 2 instructions. You want the APP/EXE version to download. It should fix you up.

where do you people come from..you're a self proclaimed noob who has executed an unsupported carrier switch, which ends up with a half functional device as a result.. and then you decide to crank the up the hilarity to warp drive stupid by flashing ANOTHHER unsupported ROM combination on top.
the random signal dropping is most certainly a result of this conversion as I have a couple of related support tickets saying the same.
you should be thankful that unholy is so patient and willing to help.. and that we know he has nothing better to do

xunholyx said:
Okay. Being S-Off you don't need to lock your bootloader to flash firmware. But since you were trying to flash Developer Edition firmware, you would have to flash a stock Dev Ed backup first, and change your MID and CID.
Leave your phone plugged into your PC.
Go here and follow the option 2 instructions. You want the APP/EXE version to download. It should fix you up.
Click to expand...
Click to collapse
I Got ERROR [130]: Model ID Error
The firmware update utility cannot update your android phone.
Please get the correct Firmware update utility and try again.
I should note that when I got to the prompt to upgrade current firmware to new firmware.....the new firmware was not a sequence of numbers. It looked like random symbols.

nitephlight said:
where do you people come from..you're a self proclaimed noob who has executed an unsupported carrier switch, which ends up with a half functional device as a result.. and then you decide to crank the up the hilarity to warp drive stupid by flashing ANOTHHER unsupported ROM combination on top.
the random signal dropping is most certainly a result of this conversion as I have a couple of related support tickets saying the same.
you should be thankful that unholy is so patient and willing to help.. and that we know he has nothing better to do
Click to expand...
Click to collapse
I truly do appreciate Unholy's help. He's been great.
I've definitely been humbled by this experience.

Tritan84 said:
I truly do appreciate Unholy's help. He's been great.
I've definitely been humbled by this experience.
Click to expand...
Click to collapse
I'm not going to be able to come up with a solution tonight. Sorry. I'm going to have to consult with someone who is more of a firmware expert than I am. And the guy whom I will be talking to is probably just waking up (lives in Germany). I'll get back to you as soon as I can. Crappy, I know.
---------- Post added at 11:00 PM ---------- Previous post was at 10:44 PM ----------
Tritan84 said:
I Got ERROR [130]: Model ID Error
The firmware update utility cannot update your android phone.
Please get the correct Firmware update utility and try again.
I should note that when I got to the prompt to upgrade current firmware to new firmware.....the new firmware was not a sequence of numbers. It looked like random symbols.
Click to expand...
Click to collapse
You probably just have to change your MID back to M8_VZW. There are tutorials on xda. It's 11pm here and I get up at 4:30. I'm tired and need to sleep. Like I said, sorry. I'll give you more help tomorrow if you don't figure it out before hand on your own.

xunholyx said:
I'm not going to be able to come up with a solution tonight. Sorry. I'm going to have to consult with someone who is more of a firmware expert than I am. And the guy whom I will be talking to is probably just waking up (lives in Germany). I'll get back to you as soon as I can. Crappy, I know.
---------- Post added at 11:00 PM ---------- Previous post was at 10:44 PM ----------
You probably just have to change your MID back to M8_VZW. There are tutorials on xda. It's 11pm here and I get up at 4:30. I'm tired and need to sleep. Like I said, sorry. I'll give you more help tomorrow if you don't figure it out before hand on your own.
Click to expand...
Click to collapse
I think you're right. I've tried to search how to change modelid via fastboot since I can't boot the phone to run adb, but all the tutorials seem to be based on using adb. Is their a way to change via fastboot only?

SUCCESS! Well, I was able to reinstall TWRP via the appropriate adb/fastboot commands and flash my nandroid backup.
Unholy, I know you mentioned doing this command, but I did not know I had to put the .img file name within that command....result of being such a noob. You were awesome and I greatly appreciate you help.

Tritan84 said:
SUCCESS! Well, I was able to reinstall TWRP via the appropriate adb/fastboot commands and flash my nandroid backup.
Unholy, I know you mentioned doing this command, but I did not know I had to put the .img file name within that command....result of being such a noob. You were awesome and I greatly appreciate you help.
Click to expand...
Click to collapse
Cool. I glad you got everything sorted. :good:

Yeah and the guy from Germany doesn't have the time to look into this anyway...

I locked my bootloader before unrooting my Pixel XL is it hopeless?

I can get the bootloader menu to come up but it says its locked and its a Verizon version. I've done a bunch of reading. My last resort is to file for lost but if there is a way to get it working again. I will donate to Chainfire or whoever.

Why would you u unlock then lock,??? If your phone is still operational just relock your bootloader.

just use depixel8 to unlock again and then use the firmware from googles website to flash everything back which will fix whatever else you messed up
---------- Post added at 12:52 AM ---------- Previous post was at 12:51 AM ----------
use the version for Marlin that ends in P... and unlocking isn't necessary to do flash this but I figured you want unlock which is the only reason why I said to do depixel8 again

I used Chainfires method of Unlocking and then I unrooted the phone. I was tyring to play pokemon lol with my girl so I just locked the bootloader thinking it would factory reset my root automatically now it boots straight to charging weird. But aslong as I can still see the settings screen where you can START , Recovery and all that their is still a way right? I do half understand what you guys say because I used to write software in Visual Basic. Its just I haven't really dabbled into the Android / Linux stuff much.

In the bootloader(fastboot mode), while being connected to your PC, try typing fastboot format userdata and then fastboot format cache. This will wipe your device and maybe boot up. You can't flash anything now with a locked bootloader.
Sent from my Pixel XL using XDA-Developers mobile app

KrazyBrandon said:
I can get the bootloader menu to come up but it says its locked and its a Verizon version. I've done a bunch of reading. My last resort is to file for lost but if there is a way to get it working again. I will donate to Chainfire or whoever.
Click to expand...
Click to collapse
What do you mean "My last resort is to file for lost"?
I'm hoping you're not intending to commit fraud because you screwed up you're phone. Apologies if I'm misreading your statement.

@KrazyBrandon, Benjamin150 may be able to help you. I sent him a pm so be on the lookout for his advice.
Sent from my Pixel XL using XDA-Developers mobile app

Roger that I look forward to trying. I really enjoy the phone.

none of these advices are correct... unlock using depixel8 again which might fix the issue on its own if not just go to https://developers.google.com/android/images click accept and download the image for Marlin that ends in a P and extract it place your adb and fastboot binaries inside the folder that was made by extracting.... then go to the android bootloader mode hook up to computer and do fastboot flash-all.bat this will factory reset your device but you will be completely back to stock

Mike02z said:
What do you mean "My last resort is to file for lost"?
I'm hoping you're not intending to commit fraud because you screwed up you're phone. Apologies if I'm misreading your statement.
Click to expand...
Click to collapse
this is exactly what I was thinking and a reason why we pay so much for insurance and coverages. just a disgrace to read that comment. I've reported this post.

diabl0w said:
none of these advices are correct... unlock using depixel8 again which might fix the issue on its own if not just go to https://developers.google.com/android/images click accept and download the image for Marlin that ends in a P and extract it place your adb and fastboot binaries inside the folder that was made by extracting.... then go to the android bootloader mode hook up to computer and do fastboot flash-all.bat this will factory reset your device but you will be completely back to stock
Click to expand...
Click to collapse
He locked his bootloader. You can't flash IMG files with a locked bootloader.
Sent from my Pixel XL using XDA-Developers mobile app

ko0ky said:
this is exactly what I was thinking and a reason why we pay so much for insurance and coverages. just a disgrace to read that comment. I've reported this post.
Click to expand...
Click to collapse
No need for all that. I'm sure you've done some questionable things in your life. Seriously?

Moderator Warning,
I am closing this thread down, as we do not discuss insurance fraud on this site.

Swift 2 Plus won't boot, stuck with locked bootloader

Please don't ask why (the answer will be: "because I'm stupid"), but I relocked my bootloader and now my Swift 2 Plus won't boot anymore. When turning it on, it vibrates and the Wileyfox logo flashes for less than a second. After that the screen stays black and nothing happens. Same thing when I try to boot into recovery. I can only boot into the bootloader but I can't flash any images or unlock it again ("FAILED (remote: oem unlock is not allowed)").
Is there any way I can revive my phone or is it lost?

I think your only way is to flash twrp again with fastboot install method :
//twrp.me/devices/wileyfoxswift2.html
And then flash the stock rom :
//cyngn.com/support
hope it will helps you!
---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------
Sorry, I'm a new user so I can't post link, you've just have to ad "https" at the beginning of the line.

Thanks for answering, but I can't do that, because the bootloader is locked and protected from unlocking. I guess the only thing I can do is ask the support if they can provide the mbn and xml files that are needed for unbricking with QFIL (I can boot into edl mode as I recently found out). They probably won't but it's worth a shot.

If you use the signed zip ( not the fastboot image) the default recovery should be able to install it.

It doesn't boot to recovery. Only fastboot and edl mode work.

You could try flashing fastboot image from http://cyngn.com/support
Sent from my Swift 2 using XDA-Developers mobile app

Thanks, but that doesn't work with a locked bootloader (already tried).

It seems like the only way to revive it is with QFIL, but for doing that it needs the matching mbn and xml files that aren't included in the factory images. Wileyfox support wasn't helpful, either.

xrmnx said:
Thanks, but that doesn't work with a locked bootloader (already tried).
Click to expand...
Click to collapse
Can't we put the dirty cow bug to a use now? It should work on the phone unless it has the latest security patches, right? And with root privileges you should be able to flash a new recovery or reset the phone.:fingers-crossed:

I'm actually not sure, if I still have root privileges. It could be that I turned it off inside the SuperSU app.
I tried to flash the stock rom and that didn't work, though. Do I have to do something different than usually to flash with root privileges?

boa05 said:
Can't we put the dirty cow bug to a use now? It should work on the phone unless it has the latest security patches, right? And with root privileges you should be able to flash a new recovery or reset the phone.:fingers-crossed:
Click to expand...
Click to collapse
I read a little about dirty cow, now (didn't know much about it before), but if I understand it right, I need adb to upload files onto the phone, right? Sadly, adb doesn't work. Only fastboot :/

Hmmm, there is a similar thread for the Nexus 5X. You might want to check it out if you haven't already ( http://forum.xda-developers.com/nexus-5x/help/nexus-5x-permanently-bricked-locked-t3232105/page2 ).
A few of the suggestions were to try with:
Code:
fastboot flashing unlock
or
Code:
fastboot format userdata
fastboot format cache
I don't know if it will be of any help but it is worth a shot.
You could try to flash individual portions of the stock image like the recovery or the userdata but I doubt that it will be successful.
PS: From the thread above, for some reason removing the SIM card allowed them to enter recovery.

Thanks, but none of these solutions works. Already tried all of them a couple of times....

Hmmm, how about you try to trick it then?
Grab the official signed firmware, place it on SD Card and try with:
Code:
fastboot update <path/to/zip>
or this one to try to wipe the device? (dunno if the command is still in use, though)
Code:
fastboot -w
If this doesn't work as well, I guess it will be a waiting game for QFIL files.

Pak0St said:
Hmmm, how about you try to trick it then?
Grab the official signed firmware, place it on SD Card and try with:
or this one to try to wipe the device? (dunno if the command is still in use, though)
If this doesn't work as well, I guess it will be a waiting game for QFIL files.
Click to expand...
Click to collapse
I tried to flash/update every official rom (with and without -w) there is, but I never put it on an SD-card. Does that make a difference? If so, this might be one ofhe stupidest mistakes I ever made :/
I'll try in a few days. Not much time, at the moment...
Yes... Waiting for QFIL files is what I'm prepared for...

The idea with the SDCard is just a random thought. There is a slight chance to trigger the allowed update policies.
Usually you place the update.zip through adb (not possible in this situation) but placing it on the sdcard is possible.
Still, QFIL is the safest bet once someone uploads the files.

Pak0St said:
Still, QFIL is the safest bet once someone uploads the files.
Click to expand...
Click to collapse
That's what I thought. Since I couldn't find any (yet), is there a way to extract the QFIL files from a working phone (I bought another one since I needed a phone)? I don't think so, but I hope I'm wrong...

xrmnx said:
That's what I thought. Since I couldn't find any (yet), is there a way to extract the QFIL files from a working phone (I bought another one since I needed a phone)? I don't think so, but I hope I'm wrong...
Click to expand...
Click to collapse
I'm in the same boat here, same phone and same issue. Did you find a way to fix it? already searched all internet for a fix. Thanks a lot

Sorry, but for some reason I never saw your answer... I never found a solution either, though

how to unlock bootloader
Use fast boot to unlock the bootloader again.
connect your Swift 2 to your PC and in a command prompt type the following "fastboot oem unlock"
When you press enter, check the phone and using the volume keys you need to select yes and then press power to execute.
Your bootloader should then be unlocked again. Good Luck.

I broke it

Update: The guys at Razer are just about as clueless as a retail phone carrier. They told me to do the exact same thing, the factory reset and all that, but they don't know what they're doing.
So FYI: IF YOU'RE BOOTLOADER IS LOCKED AND YOUR OS WON'T START, YOU'RE SCREWED.
Okay so I rooted the phone on Oreo, the second to last update, and tried to update it to the May update, and the update kept failing inside the system update app. So, I tried installing it by flashing it from a computer. Unsuccessfully. So, I booted into TWRP and installed every image manually through TWRP. Bootlooped it. Soooooo I tried to flash the latest stock image from the computer, and it goes through, but the phone refuses to turn on. And I can't even unlock the bootloader because in the command prompt it says it's not allowed. So I'm stuck with a paperweight that won't unlock any bootloaders and won't even boot into the OS. I think I royally screwed it up and I desperately just wanna use the phone again.
I've tried everything. My drivers are correct, and It just won't cooperate with me no matter what I do to it. It'll either keep booting into download mode or get stuck on the splash screen forever.
I'm literally desperate at this point. I can't do anything with this thing!!! I can't flash anything because it's locked and the phone won't boot into the OS for me to even unlock it.

How did you get twrp with a locked bootloader? :S is that a thing now?
You cant flash the factory images without an unlocked bootloader. So if you didn't check the OEM unlock allowed setting you won't be able to unlock it so won't be able to flash the firmware.
Honestly i think you're out of luck if you can't unlock your bootloader.

Wait how did your bootloader relock itaelf? Because that can happen only with the lock/lock_critical command.
---------- Post added at 02:07 PM ---------- Previous post was at 02:03 PM ----------
Dashaquavius said:
Okay so I rooted the phone on Oreo, the second to last update, sand tried to update it to the May update, and the update kept failing inside the system update app. So, I tried installing it by flashing it from a computer. Unsuccessfully. So, I booted into TWRP and installed every image manually through TWRP. Bootlooped it. Soooooo I tried to flash the latest stock image from the computer, and it goes through, but the phone refuses to turn on. And I can't even unlock the the bootloader because in the command prompt it says it's not allowed. So I'm stuck with a paperweight that won't unlock any bootloaders and won't even boot into the OS. I think I royally screwed it up and I desperately just wanna use the phone again..
I've tried everything. My drivers are correct, and It just won't cooperate with me no matter what I do to it. It'll either keep booting into download mode or get stuck on the splash screen forever.
I'm literally desperate at this point. I can't do anything with this thing!!! I can't flash anything because it's locked and the phone won't boot into the OS for me to even unlock it..
Click to expand...
Click to collapse
Did you say the factory images fully flash with no errors? Both "fastboot flashing unlock/unlock_critical" don't work?

You should try the flash_all.bat or flash_all.sh script from the latest images. If you want to keep your data just comment or erase the line with the "fastboot erase userdata" in the flash_all.
Be sure to have fastboot in your path

Roxas598 said:
How did you get twrp with a locked bootloader? :S is that a thing now?
You cant flash the factory images without an unlocked bootloader. So if you didn't check the OEM unlock allowed setting you won't be able to unlock it so won't be able to flash the firmware.
Honestly i think you're out of luck if you can't unlock your bootloader
Click to expand...
Click to collapse
iliais347 said:
Wait how did your bootloader relock itaelf? Because that can happen only with the lock/lock_critical command.
Did you say the factory images fully flash with no errors? Both "fastboot flashing unlock/unlock_critical" don't work?
Click to expand...
Click to collapse
waiflih said:
You should try the flash_all.bat or flash_all.sh script from the latest images. If you want to keep your data just comment or erase the line with the "fastboot erase userdata" in the flash_all.
Be sure to have fastboot in your path
Click to expand...
Click to collapse
1. I didn't flash TWRP with the bootloader in the locked state, it was while it was unlocked.
2. Out of desperation, after flashing the stock images multiple times (while it says errors and maximum download reached and stuff) I re-locked the bootloader with the command thinking it would finally at least boot into the OS, to no avail.
3. Factory images didn't flash without some kind of error.
4. I'm unable to run any kind of commands, it says it's not allowed.
5. I've flashed multiple times, flashed the previous updates and the latest updates, and there's always some kind of error or it's not allowed.
I'm just gonna contact Razer. Apparently, I can't flash anything if the bootloader is locked? And the phone won't even boot into the OS to let me tick the option? I think I'm screwed.

For what you are telling you may have an outdated fastboot version. Can you try flash_all and post the error messages? kinda difficult to help without that

waiflih said:
For what you are telling you may have an outdated fastboot version. Can you try flash_all and post the error messages? kinda difficult to help without that
Click to expand...
Click to collapse
It says flashing is not allowed for everything.

Ok that is indeed strange. Take a look at this https://insider.razer.com/index.php...afe-method-warning-rebuilds-partitions.23532/
its for the robin but since you already tried everything else you can give it a shot

waiflih said:
Ok that is indeed strange. Take a look at this https://insider.razer.com/index.php...afe-method-warning-rebuilds-partitions.23532/
its for the robin but since you already tried everything else you can give it a shot
Click to expand...
Click to collapse
I just got off with Razer support, they're just gonna send me a new one.
And apparently, absolutely NO OTG support!
Let this thread serve as a warning..

how did you manage to get razer to agree a replacement??.i had a speaker issue and had to send a video of my problem then a week later they finally agreed to replace it.you have done really well for them to accept phone back for replacemnet..as for relocking bootloader as far as i read the other day once you do this phone is bricked

parky169 said:
how did you manage to get razer to agree a replacement??.i had a speaker issue and had to send a video of my problem then a week later they finally agreed to replace it.you have done really well for them to accept phone back for replacemnet..as for relocking bootloader as far as i read the other day once you do this phone is bricked
Click to expand...
Click to collapse
Interesting. I sent 2 phones with speaker issues and they offered a replacement for both and gave me shipping labela.

Soft bricked with bootloader locked :(

Hi guys,
Please help me out, is there any way I can recover from soft brick if I have a locked bootloader and usb debugging is turned off?

Can you get into fastboot and then factory recovery? If you can get there I believe you should be able to do a reset.

timothy009 said:
Hi guys,
Please help me out, is there any way I can recover from soft brick if I have a locked bootloader and usb debugging is turned off?
Click to expand...
Click to collapse
Try booting into recovery and then from your PC sideload the latest ota zip file.
Sent from my [device_name] using XDA-Developers Legacy app

Shouldn't it be necessary to have enabled USB debugging before?

timothy009 said:
Shouldn't it be necessary to have enabled USB debugging before?
Click to expand...
Click to collapse
No. Not while in recovery mode using the "update by adb" option.

This is the stock recovery we are talking about, right?

timothy009 said:
This is the stock recovery we are talking about, right?
Click to expand...
Click to collapse
Yes
Sent from my [device_name] using XDA-Developers Legacy app

Please help me. I have pixel 3 xl joining Q beta. When the setting is pressed, the device does not work. hang like picture. My device has not been unlocked when participating in the test.

spotmark said:
Can you get into fastboot and then factory recovery? If you can get there I believe you should be able to do a reset.
Click to expand...
Click to collapse
Currently the 3xl pixel is hanging so I can't unlock the bootloader pixel to flash the original rom.

nguyenmanh287 said:
Currently the 3xl pixel is hanging so I can't unlock the bootloader pixel to flash the original rom.
Click to expand...
Click to collapse
Google "rescue ota". You use a full OTA from the Google image page and from the stock recovery using the "apply update by adb" option to send the ota from your pc to the phone. Does not require an unlocked bootloader. Does require the latest adb/fastboot binaries on your pc. Directions are right there on Google's ota download page. Best of luck! :good:

v12xke said:
Google "rescue ota". You use a full OTA from the Google image page and from the stock recovery using the "apply update by adb" option to send the ota from your pc to the phone. Does not require an unlocked bootloader. Does require the latest adb/fastboot binaries on your pc. Directions are right there on Google's ota download page. Best of luck! :good:
Click to expand...
Click to collapse
Currently my 3xl pixels are dying. it has not been unlocked yet, so I cannot adb the original google rom

nguyenmanh287 said:
Currently my 3xl pixels are dying. it has not been unlocked yet, so I cannot adb the original google rom
Click to expand...
Click to collapse
I understand your first language is not English and I am trying to help you. Please try to parse/translate the information. You do NOT need an unlocked bootloader or USB debugging to use the ADB option in stock recovery mode using the full OTA image. In too many other threads you have never stated YES, I have a working stock recovery. If you have that, follow the instructions. Yes, you can flash a full OTA image in an attempt to rescue your P3XL even though your bootloader is locked. Otherwise please state you DO NOT have access to a stock recovery instead of cross posting to at least a half dozen threads "help me"! Too many posts from you and never enough information to help you.

Thank you very much. I will ask someone who speaks English to describe the whole situation so you know my PIXEL 3XL status.
---------- Post added at 02:35 AM ---------- Previous post was at 02:34 AM ----------
v12xke said:
I understand your first language is not English and I am trying to help you. Please try to parse/translate the information. You do NOT need an unlocked bootloader or USB debugging to use the ADB option in stock recovery mode using the full OTA image. In too many other threads you have never stated YES, I have a working stock recovery. If you have that, follow the instructions. Yes, you can flash a full OTA image in an attempt to rescue your P3XL even though your bootloader is locked. Otherwise please state you DO NOT have access to a stock recovery instead of cross posting to at least a half dozen threads "help me"! Too many posts from you and never enough information to help you.
Click to expand...
Click to collapse
Thank you very much. I will ask someone who speaks English to describe the whole situation so you know my PIXEL 3XL status.

v12xke said:
Google "rescue ota". You use a full OTA from the Google image page and from the stock recovery using the "apply update by adb" option to send the ota from your pc to the phone. Does not require an unlocked bootloader. Does require the latest adb/fastboot binaries on your pc. Directions are right there on Google's ota download page. Best of luck! :good:
Click to expand...
Click to collapse
Can you guide me specifically? did you tell facebook friends then i send pictures to you? help me?
This is my Facebook
https://www.facebook.com/NGUYENMANH287

nguyenmanh287 said:
Can you guide me specifically? did you tell facebook friends then i send pictures to you? help me?
This is my Facebook
https://www.facebook.com/NGUYENMANH287
Click to expand...
Click to collapse
The post you quoted, has the link to the OTA download page which contains the best instructions available. You can run that page through an online translator if necessary.
You have gotten the help you asked for. Now it's time for you to help yourself. You can take your device to someone more knowledgeable, who is in your area if you feel you can not follow the instructions on Google's page, but there is no further instruction that can be given here that will make this any easier for you.
v12xke said:
Google "rescue ota". You use a full OTA from the Google image page and from the stock recovery using the "apply update by adb" option to send the ota from your pc to the phone. Does not require an unlocked bootloader. Does require the latest adb/fastboot binaries on your pc. Directions are right there on Google's ota download page. Best of luck! :good:
Click to expand...
Click to collapse

v12xke said:
Google "rescue ota". You use a full OTA from the Google image page and from the stock recovery using the "apply update by adb" option to send the ota from your pc to the phone. Does not require an unlocked bootloader. Does require the latest adb/fastboot binaries on your pc. Directions are right there on Google's ota download page. Best of luck! :good:
Click to expand...
Click to collapse
I have the same issue described. My bootloop started with September Android 10 update. I already sideloaded October ota from Google website, and it updated without any problem. Still bootloop. I'm on a pixel 3xl 100% stock bootloader locked no root

movilserver said:
I have the same issue described. My bootloop started with September Android 10 update. I already sideloaded October ota from Google website, and it updated without any problem. Still bootloop. I'm on a pixel 3xl 100% stock bootloader locked no root
Click to expand...
Click to collapse
Not sure why you used the October image, but with a locked bootloader your only option is the rescue OTA. You could try a factory reset from recovery. If that doesn't (or did not) work, then try the December OTA image. Make sure you are using the correct image for your phone (there may be more than one choice). If this fails you should contact Google support, or if you bought it elsewhere, contact them for any warranty you might have.

Make sure to wipe cache

v12xke said:
Not sure why you used the October image, but with a locked bootloader your only option is the rescue OTA. You could try a factory reset from recovery. If that doesn't (or did not) work, then try the December OTA image. Make sure you are using the correct image for your phone (there may be more than one choice). If this fails you should contact Google support, or if you bought it elsewhere, contact them for any warranty you might have.
Click to expand...
Click to collapse
Already tried December. Same thing. I live in Cuba. No warranty or anything. The phone was a gift, and it worked with pie without any issues
---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------
ktmom said:
Make sure to wipe cache
Click to expand...
Click to collapse
I don't have that option in recovery. Any way I've wiped data several times, I think that should wipe cache also

movilserver said:
Already tried December. Same thing. I live in Cuba. No warranty or anything. The phone was a gift, and it worked with pie without any issues
---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------
I don't have that option in recovery. Any way I've wiped data several times, I think that should wipe cache also
Click to expand...
Click to collapse
If you have done a FDR from recovery, and sideloaded a couple of valid OTA's, sorry to say I think you're pretty much done. It's too bad the bootloader is locked, as you would have more tools to work with. What is your bootloader version? 10 or Pie? If still Pie you might get lucky sideloading the correct Pie OTA that exactly matches your bootloader, and get back into System. Once up and running you could look into unlocking it if that is an option. If not wait for a 10 update to come down vs. sideloading. Nothing to lose at this point. Hang in there.