Related
Hello, I am completely new so I apologize if this is the wrong place.
I wanted to be able to lock my bootloader but still use cyanogenmod, specifically, only allow roms that I have compiled myself and signed with my cert to work on my phone. I unpacked the stock recovery.img, and made the necessary changes to the ramdisk to replace the stock OnePlus key with my own. I then was then able to confirm that only my signed zips could be sideloaded, both official CM and OxygenOS zips failed - just as I wanted.
The issue is then that this only worked with an unlocked bootloader. When I locked it, the OP3 entered a boot cycle, with a strange graphical glitch appearing then the screen going black, again and again. I could then no longer boot to either recovery or cyanogenmod, nor could I unlock fastboot. This amazing guide got my phone working again.
I now have three questions. What prevented my phone booting after I locked it, how does the unbrick tool work, and is there anything I can alter, like certifications or hashes, lower down in the boot sequence to allow only my signed images to work (using the previous tool. I am unsure what QLoader is, some form of serial interface to the 820 to write to the storage chip?).
Thanks for any advice you can offer!
Update: I have unpacked boot.img provided in the unbrick tool. I cannot find any keys to modify in /res but I have found a file called "verify_keys". Does anyone know what I need to change in boot.img to allow my self-signed recovery and os to boot? Thanks
UPDATE 2:
From reading some Android notes it appears that instead of replacing the OEM key, you can also just use fastboot to flash keystores for self-signed recovery and roms. This still allows OEM signed images to run, but is certainly a step in the right direction. I have run into an issue with building a correct keystore. I can use keytool and import my previous certs, but "fastboot flash keystore examplename.keystore" fails. I saw "fastboot flash ssd keystore.dat" used, and it works with my current dot keystore file, but then after locking it fails to boot. I'm going to see how I can convert my .keystore to a .dat.
I've been meaning to ask this same question for a while now also, so I'm eager to see the response. I suspect the official OnePlus forums might be a good place to ask as well, since they are visited by engineers from OnePlus. For anyone else who's curious as to what's being discussed and better the understand the risks of an unlocked bootloader (and how to mitigate them), there's a brief article here as well as a paper.
It is always suggested that never re-lock the bootloader until there is valid reason to do it
JumboMan said:
It is always suggested that never re-lock the bootloader until there is valid reason to do it
Click to expand...
Click to collapse
Have you read any of the attached links in my last post? There are valid reasons for doing so.
Just to pose an oversimplified hypothetical, imagine going through immigration/customs in Saudi Arabia (or maybe even the U.S.) with a Android device that has an unlocked bootloader. The officer examines your possesions, then takes your laptop and phone into a back room. Your phone is powered down and encrypted so it's not like they can do anything, right? Wrong. They plug it into a forensics device and flash a surreptitious malware app onto /system before returning it back to you. Then, the next time you turn on your phone your encryption keys and all your data, all your communications are secretly transmitted. You never have a clue... With a locked bootloader and appropriate precautions, that would never be possible.
Update 3:
I am now following the official Android guide for creating a keystore. They show how to create a "keystore.img" not .dat, bu the error I got when trying "fastboot flash keystore ..." said something along the lines of the keystore not being a valid image. Hopefully this will work. After I get this working, I will move on to removing or damaging the OEM key, hence not even allowing OnePlus images to be sideloaded.
JumboMan said:
It is always suggested that never re-lock the bootloader until there is valid reason to do it
Click to expand...
Click to collapse
I do have a valid reason - security. An unlocked bootloader means any code can be flashed to my device. Even with encryption it is vulnerable to cold boot attacks, it makes it easier to bruteforce, and pulling encryption keys from memory.
chocol4te said:
I do have a valid reason - security. An unlocked bootloader means any code can be flashed to my device. Even with encryption it is vulnerable to cold boot attacks, it makes it easier to bruteforce, and pulling encryption keys from memory.
Click to expand...
Click to collapse
sir prefer not rooting and staying on stock ROM with locked bootloader.
emptyragnarok said:
sir prefer not rooting and staying on stock ROM with locked bootloader.
Click to expand...
Click to collapse
Look, I'm sorry, I don't need any more useless comments saying the solution to my problem is to not do anything like on every other forum I've tried. I am perfectly aware of how to lock the bootloader with a stock rom, but I don't want to use the stock rom. I want to use custom roms. From what I have done so far it appears to be possible, so don't tell me it's not, at least without a good reason.
In addition, the stock method isn't even the most secure the phone can be. OnePlus can still sign any code and run it on my device and hence requires my trust in a third party that I am unwilling to give. I only want my own code to run.
Update 4:
Using the unbrick utility, I have updated the MD5 partition with the checksums of my modified boot and recovery partitions. Unfortunately, I am now getting a checksum failed error, with both the MD5 and recovery partitions highlighted in red. So I was wrong about the checksum being compared with hashes in the MD5 partition. Does anyone know where the lowest level checksums are stored? Hopefully if I can change that, then locking the bootloader will be no issue.
chocol4te said:
Update 4:
Using the unbrick utility, I have updated the MD5 partition with the checksums of my modified boot and recovery partitions. Unfortunately, I am now getting a checksum failed error, with both the MD5 and recovery partitions highlighted in red. So I was wrong about the checksum being compared with hashes in the MD5 partition. Does anyone know where the lowest level checksums are stored? Hopefully if I can change that, then locking the bootloader will be no issue.
Click to expand...
Click to collapse
Bro I am not a prolike you but I understand your vision now,... and I am with you in that.... Open Source stuff and ANdroid as an Open source impify that only... We should have our custom code for locking and unlocking our bootloader so we can have the full control over our device.... If not and the guy that said that you can lock the bootloader with the stock rom didn't get that .. even with stock rom and recovery anyone can have the access of the phone by just unlocking the boot loader and that is simple. SO I GOT YOUR VISION AND I AM WITH YOU I WILL TRY TO UNDERSTAND THE LOCKING SYSTEM OF THE BOOT-LOADER AND I WILL TRY TO FIND THE LOCATION OF LOWER LEVEL CHECKSLUMS... WE will try and try untill we succeed.... I AM WITH YOU BRO!!!!!
indroider said:
Bro I am not a prolike you but I understand your vision now,... and I am with you in that.... Open Source stuff and ANdroid as an Open source impify that only... We should have our custom code for locking and unlocking our bootloader so we can have the full control over our device.... If not and the guy that said that you can lock the bootloader with the stock rom didn't get that .. even with stock rom and recovery anyone can have the access of the phone by just unlocking the boot loader and that is simple. SO I GOT YOUR VISION AND I AM WITH YOU I WILL TRY TO UNDERSTAND THE LOCKING SYSTEM OF THE BOOT-LOADER AND I WILL TRY TO FIND THE LOCATION OF LOWER LEVEL CHECKSLUMS... WE will try and try untill we succeed.... I AM WITH YOU BRO!!!!!
Click to expand...
Click to collapse
Thanks! I'm glad to hear it!
chocol4te said:
Thanks! I'm glad to hear it!
Click to expand...
Click to collapse
You're most welcome bro.
Did I just witness a major bro-down?
Awsome thread, I'd also like to put my OP3 in a state where only ROMs I signed my self will run...
Any further development??
Sent from my Pixel XL using XDA-Developers mobile app
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
indieross said:
Did I just witness a major bro-down?
Click to expand...
Click to collapse
Whats a bro down?
Sent from my Pixel XL using XDA-Developers mobile app
indroider said:
Any further development??
Sent from my Pixel XL using XDA-Developers mobile app
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
Whats a bro down?
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Sorry, other stuff came up. I am still very interested in getting this to work, but I am really stuck if I can't understand why the MD5 verification error occurs when I use Loader to flash the modified images. I looked at CopperheadOS, and in their documentation they show how to re-lock the bootloader with a custom ROM. Here is the shell script they use to upload the OS.
Code:
fastboot flash bootloader bootloader-bullhead-bhz11f.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-bullhead-m8994f-2.6.33.2.14.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-bullhead-nbd90z.zip
As you can see they flash two images, boot loader and radio, then update the main ROM. Then apparently it boots fine and the bootloader is OEM locked inside the OS. This was for the Nexus 5X, but I want to find out if a similar process is possible on the OP3.
I may also begin work on porting CopperheadOS to the OnePlus 3. I know it sounds unrealistic, but since OnePlus released the binaries and kernels it should make it slightly easier.
chocol4te said:
Sorry, other stuff came up. I am still very interested in getting this to work, but I am really stuck if I can't understand why the MD5 verification error occurs when I use Loader to flash the modified images. I looked at CopperheadOS, and in their documentation they show how to re-lock the bootloader with a custom ROM. Here is the shell script they use to upload the OS.
As you can see they flash two images, boot loader and radio, then update the main ROM. Then apparently it boots fine and the bootloader is OEM locked inside the OS. This was for the Nexus 5X, but I want to find out if a similar process is possible on the OP3.
I may also begin work on porting CopperheadOS to the OnePlus 3. I know it sounds unrealistic, but since OnePlus released the binaries and kernels it should make it slightly easier.
Click to expand...
Click to collapse
Ok.. Great to hear... Let me if you need any help.. I m here
chocol4te said:
Sorry, other stuff came up. I am still very interested in getting this to work ... ...
I may also begin work on porting CopperheadOS to the OnePlus 3. I know it sounds unrealistic, but since OnePlus released the binaries and kernels it should make it slightly easier.
Click to expand...
Click to collapse
This sounds exactly like what I was looking for. Have you been able to progress? Do you think that the bootloader and the radio are somehow linked in the boot verification sequence?
---------- Post added at 05:51 AM ---------- Previous post was at 05:43 AM ----------
chocol4te said:
UPDATE 2:
From reading some Android notes it appears that instead of replacing the OEM key, you can also just use fastboot to flash keystores for self-signed recovery and roms. This still allows OEM signed images to run, but is certainly a step in the right direction. I have run into an issue with building a correct keystore. I can use keytool and import my previous certs, but "fastboot flash keystore examplename.keystore" fails. I saw "fastboot flash ssd keystore.dat" used, and it works with my current dot keystore file, but then after locking it fails to boot. I'm going to see how I can convert my .keystore to a .dat.
Click to expand...
Click to collapse
Have you read this: https://mjg59.dreamwidth.org/31765.html
Morning all,
Im not S-off and I'm using a pretty dated firmware..
I was told that there is a way to obtain and flash a firmware WITHOUT wiping anything and without too much fuss.
My questions:
What is the COMMAND in CMD?
Where do you find the signed firmware?
How do you identify which one to use?
What does it actually change? As the phone does work on dated firmware, more optimised?
I highly doubt I'm the only one who would benefit from this, once I know the answers I'll leave them here and I'll write a guide on how to install them step by step I'll also link the firmwares do others can help themselves.
Thanks
Currently running: Viper 3.5.0
Firmware: 1.80.401.1
S-ON
Unecrypted.
Check out Krassermensch's Firmware Update Tool in the guide part of the forum.
Lindsten said:
Check out Krassermensch's Firmware Update Tool in the guide part of the forum.
Click to expand...
Click to collapse
Have come mate, but I've asked some other things plus there is apparently a way to do it without the use of a tool.
This is the specific thread for firmware update.
I think you can only flash the full stock zip since you are s-on. Do take note that flashing the stock firmware.zip will wipe your internal storage.
The firmware to flash should have matching CID and MID of your device.
To check your mid and cid type this command in cmd while the device is in download mode.
fastboot getvar all
side_flip15 said:
This is the specific thread for firmware update.
I think you can only flash the full stock zip since you are s-on. Do take note that flashing the stock firmware.zip will wipe your internal storage.
The firmware to flash should have matching CID and MID of your device.
To check your mid and cid type this command in cmd while the device is in download mode.
fastboot getvar all
Click to expand...
Click to collapse
Incorrect. All of @Sneakyghost's firmware.zips are for S-Off users only. It's stated in the OP of the thread right in the first sentence.
xunholyx said:
Incorrect. All of @Sneakyghost's firmware.zips are for S-Off users only. It's stated in the OP of the thread right in the first sentence.
Click to expand...
Click to collapse
Cheers,
Does anyone know the answers to any of the questions I've written?
sorry
side_flip15 said:
sorry
Click to expand...
Click to collapse
No reason to be sorry. You were trying to help, and I was just letting you know that it won't work for him.
---------- Post added at 06:16 PM ---------- Previous post was at 06:03 PM ----------
dladz said:
Does anyone know the answers to any of the questions I've written?
Click to expand...
Click to collapse
First make a backup. This will wipe your phone.
Then relock your bootloader. In fastboot fastboot oem lock
Download this RUU.zip
Rename the .zip to 2PS6IMG and place it onto your extSD
Boot to download mode and follow the prompts (vol up to flash ~ power button to reboot)
That's it. Super easy.
Delete the renamed .zip from your extSD or else every time you boot to download mode it'll try to update again.
Now unlock your bootloader again with the same bin code that HTC gave you when you first did it, or request a new one. Flash TWRP back onto your phone, then flash SuperSU or a custom ROM to regain root.
This is why I paid $25 for Sunshine.
For S-Off users, you just flash a small firmware package, and that's it. No data loss. No relocking the bootloader. No reflashing recovery. No re-rooting.
It really is worth the price in the amount of time and hassle saved through the lifetime of the phone.
xunholyx said:
No reason to be sorry. You were trying to help, and I was just letting you know that it won't work for him.
---------- Post added at 06:16 PM ---------- Previous post was at 06:03 PM ----------
First make a backup. This will wipe your phone.
Then relock your bootloader. In fastboot fastboot oem lock
Download this RUU.zip
Rename the .zip to 2PS6IMG and place it onto your extSD
Boot to download mode and follow the prompts (vol up to flash ~ power button to reboot)
That's it. Super easy.
Delete the renamed .zip from your extSD or else every time you boot to download mode it'll try to update again.
Now unlock your bootloader again with the same bin code that HTC gave you when you first did it, or request a new one. Flash TWRP back onto your phone, then flash SuperSU or a custom ROM to regain root.
This is why I paid $25 for Sunshine.
For S-Off users, you just flash a small firmware package, and that's it. No data loss. No relocking the bootloader. No reflashing recovery. No re-rooting.
It really is worth the price in the amount of time and hassle saved through the lifetime of the phone.
Click to expand...
Click to collapse
OK so this is where I've heard different.. There apparently isn't any need to return to stock so think you may need to read the originating post yourself mate
Otherwise how would the tool mentioned in the second post work? Appreciate you saying all that but it doesn't help my query.
As for sunshine I completely disagree, I've had every single htc bar two since the G1 and I've had S-off on all of them where available so I know the S-off method well, and have made a lot of donations to developers over the years, I also buy all my apps and support Devs when they deserve it for apps.
In regards to sunshine, I paid for this app for my m9 less than a year ago, I get one license, I can't use this for my 10 and I'll have another phone soon so see little point, they should offer more than one unlock for £25 and the only reason why they've got away with this daylight robbery is because they've monopolised the market, I'm sure I'm not the the only person who's noticed this.
Anyway, I'll wait to hear from someone who knows about the signed firmwares and how to install them. The tool can do it, so there must be a manual way, Id prefer to do that as I've had problems with tools in the past and with firmware you really want to get it right.
dladz said:
OK so this is where I've heard different.. There apparently isn't any need to return to stock so think you may need to read the originating post yourself mate
Otherwise how would the tool mentioned in the second post work? Appreciate you saying all that but it doesn't help my query.
As for sunshine I completely disagree, I've had every single htc bar two since the G1 and I've had S-off on all of them where available so I know the S-off method well, and have made a lot of donations to developers over the years, I also buy all my apps and support Devs when they deserve it for apps.
In regards to sunshine, I paid for this app for my m9 less than a year ago, I get one license, I can't use this for my 10 and I'll have another phone soon so see little point, they should offer more than one unlock for £25 and the only reason why they've got away with this daylight robbery is because they've monopolised the market, I'm sure I'm not the the only person who's noticed this.
Anyway, I'll wait to hear from someone who knows about the signed firmwares and how to install them. The tool can do it, so there must be a manual way, Id prefer to do that as I've had problems with tools in the past and with firmware you really want to get it right.
Click to expand...
Click to collapse
I think you misunderstood me. I'm sure there is a thread somewhere here with signed firmware (there is for M8), but I don't know of it. If I did, I would have linked you there.
But you asked if anyone could give you help, so I offered you a way to do it.
Even if you find a signed firmware.zip, you'll still need to re-lock your bootloader since you are S-On.
You might as well save some time searching and just run the RUU
xunholyx said:
I think you misunderstood me. I'm sure there is a thread somewhere here with signed firmware (there is for M8), but I don't know of it. If I did, I would have linked you there.
But you asked if anyone could give you help, so I offered you a way to do it.
Even if you find a signed firmware.zip, you'll still need to re-lock your bootloader since you are S-On.
You might as well save some time searching and just run the RUU
Click to expand...
Click to collapse
I'll check around, was speaking with @LeeDroid a while ago, can't remember him saying relock the bootloader, I'll ask him.
I'm pretty sure there is a way. Can't see that tool in the second post relocking your bootloader.
dladz said:
I'll check around, was speaking with @LeeDroid a while ago, can't remember him saying relock the bootloader, I'll ask him.
I'm pretty sure there is a way. Can't see that tool in the second post relocating your bootloader.
Click to expand...
Click to collapse
Actually, I have been following the method of @krassermensch's since before he started a thread about it. He posted to a different firmware thread about the method, and I've been curious about it since. In his OP he states that you need an unlocked bootloader, so his method is probably your best solution. I haven't tried it myself as I have always been S-Off on my HTC phones.
dladz said:
Have come mate, but I've asked some other things plus there is apparently a way to do it without the use of a tool.
Click to expand...
Click to collapse
My tool is on GitHub, read the content of the batch files and you know how to do it
https://github.com/nico151999/Firmware-Update-Tool-HTC10
krassermensch said:
My tool is on GitHub, read the content of the batch files and you know how to do it
https://github.com/nico151999/Firmware-Update-Tool-HTC10
Click to expand...
Click to collapse
Thanks :good:
xunholyx said:
Actually, I have been following the method of @krassermensch's since before he started a thread about it. He posted to a different firmware thread about the method, and I've been curious about it since. In his OP he states that you need an unlocked bootloader, so his method is probably your best solution. I haven't tried it myself as I have always been S-Off on my HTC phones.
Click to expand...
Click to collapse
yea same here man, looking at the tools code it seems that it asks you to back up first.
I'll check it out in the morning.
Thanks chaps
dladz said:
yea same here man, looking at the tools code it seems that it asks you to back up first.
I'll check it out in the morning.
Thanks chaps
Click to expand...
Click to collapse
The backup is necessary as the firmware update files overwrite the recovery and the boot partitions...
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Update: I have returned my device to Google and they processed a replacement
i am just curious, how were planning on flashing a rom with locked bootloader?
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
Yea, I think you may have turned it into a fancy paperweight. Been there, done that. You should have waited to uncheck OEM unlocking until after you locked the bootloader, which wiped your phone. About the only thing I can suggest is to try and run Deuces script to see if you can rescue your device. Best of luck to you.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
Sorry for your loss, but you indeed have a fancy paperweight.
However I wonder if there isnt the QCom USB mode or something like that that exist on older devices, where you can access the phone partitions at a lower level and then restore whatever partitions is broken.
Paradoxxx said:
Sorry for your loss, but you indeed have a fancy paperweight.
However I wonder if there isnt the QCom USB mode or something like that that exist on older devices, where you can access the phone partitions at a lower level and then restore whatever partitions is broken.
Click to expand...
Click to collapse
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
gee2012 said:
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
Click to expand...
Click to collapse
Yeah at that point... Not sure what is Google saying about that. Maybe RMA it ?
Saying something like that should work.
"I was using my device, and suddenly it froze and nothing responded. It suddenly rebooted and shown this error message."
gee2012 said:
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
Click to expand...
Click to collapse
Sorry didn't get, What do you mean by OP has nothing to loose?
Badger50 said:
Yea, I think you may have turned it into a fancy paperweight. Been there, done that. You should have waited to uncheck OEM unlocking until after you locked the bootloader, which wiped your phone. About the only thing I can suggest is to try and run Deuces script to see if you can rescue your device. Best of luck to you.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
How did you recover your devices from that state earlier when you did the same thing?
ram4ufriends said:
Sorry didn't get, What do you mean by OP has nothing to loose?
Click to expand...
Click to collapse
since your phone is now essentially a brick, you can try just about anything without worry of bricking your phone.
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
You cannot flash full images, but you can still flash OTAs... download the full OTA instead, and install (sideload) it from the stock recovery. Be sure to select the SAME build number you were on to begin with- eg. If you were on 8.1, use the 8.1 OTA. There will be a mode there for "Apply update from ADB". You put the phone into "sideload mode" and then send the OTA to the phone via adb. This will work regardless whether you have usb debugging enabled or not. Follow the directions given on the included link.
ram4ufriends said:
How did you recover your devices from that state earlier when you did the same thing?
Click to expand...
Click to collapse
I didn't. They are still paperweights sitting in a drawer!
I got the same message yesterday after doing... God knows what. I can't even remember what went wrong.
My first thought was to flash a factory image. But it didn't helped at first. Probably, because i was trying to flash another factory image and not the one that came as stock on my phone.
So if you don't remember, which image it was, try all of them Hopefully, you'll get your phone booted again.
My first reaction was, is this april fools day? Is this an xda style joke? unchecked oem unlock?
dontbeweakvato said:
My first reaction was, is this april fools day? Is this an xda style joke? unchecked oem unlock?
Click to expand...
Click to collapse
Meh...you know how it is bro....**it happens!
Call google and just tell them your device wont boot all of a sudden; they will probably ask you to factory restore in the recovery, say the phone wont get past the google image. They will RMA that boy for you. You totally bricked. For future reference if you unlock the bootloader, dont waste your time trying to lock it again. Should have just fastboot flashed a factory image in the bootloader and called it a day. Having a unlocked bootloader doesn't effect you in anyway negatively.
ArminasAnarion said:
Call google and just tell them your device wont boot all of a sudden; they will probably ask you to factory restore in the recovery, say the phone wont get past the google image. They will RMA that boy for you. You totally bricked. For future reference if you unlock the bootloader, dont waste your time trying to lock it again. Should have just fastboot flashed a factory image in the bootloader and called it a day. Having a unlocked bootloader doesn't effect you in anyway negatively.
Click to expand...
Click to collapse
Why is this Google's problem? This guy is at fault. Google shouldn't have to pay for it.
This is part of the reason these phones are so expensive.
Sent from my taimen using XDA Labs
mitchdickson said:
Why is this Google's problem? This guy is at fault. Google shouldn't have to pay for it.
This is part of the reason these phones are so expensive.
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
Well I never said it was the moral thing to do haha; but this guys best bet is to call Google and see if they will RMA it. They RMA'ed my Nexus 6p after the Android 7 twrp brick; and I told them my pone wouldn't boot anymore; they asked me to go to recovery and factory restore, I told them I couldn't boot into recovery and they RMA'ed it. It was my fault for the brick but they didn't care.
ArminasAnarion said:
Well I never said it was the moral thing to do haha; but this guys best bet is to call Google and see if they will RMA it. They RMA'ed my Nexus 6p after the Android 7 twrp brick; and I told them my pone wouldn't boot anymore; they asked me to go to recovery and factory restore, I told them I couldn't boot into recovery and they RMA'ed it. It was my fault for the brick but they didn't care.
Click to expand...
Click to collapse
Did you tell them it was your fault for the brick?
Sent from my taimen using XDA Labs
mitchdickson said:
Did you tell them it was your fault for the brick?
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
I told them I had an unlocked boot-loader and installed twrp. I had to send them back my old phone and they put a $500 hold on my account, once they received the device and determined the issue was real, they released the hold on my account. In that period of time they could have determined "Oh he bricked the device with twrp" lets charge him $500 for a new one, but they didn't. I mean whats wrong with calling Google and seeing if they will RMA it; sure the OP made a bad mistake but you have not because you ask not.
ArminasAnarion said:
I told them I had an unlocked boot-loader and installed twrp. I had to send them back my old phone and they put a $500 hold on my account, once they received the device and determined the issue was real, they released the hold on my account. In that period of time they could have determined "Oh he bricked the device with twrp" lets charge him $500 for a new one, but they didn't. I mean whats wrong with calling Google and seeing if they will RMA it; sure the OP made a bad mistake but you have not because you ask not.
Click to expand...
Click to collapse
What's wrong with it? You're telling him to call Google and say that for some reason, all the sudden his device won't boot.
This is why I don't fault Verizon for selling bootloader locked phones.
Sent from my taimen using XDA Labs
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.
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.