So I've had my htc one since september I bought it brand new and rooted it and put custom rom and unlocked bootloader. After a month I wanted to relock the bootloader and unroot it so I used the RUU. It worked for about a month then one day it just turned off and keeps rebooting itself. Sometimes when its off and i plug it in it starts to flash a red light on top then it just turned off. I have reinstalled the RUU many times but never worked. Its been like this since october sometimes it keeps rebooting and it actually turns on but its in safe mode. no music playin, no microphone, really fast battery drain. If someone can please help me it is the at&t version. I have also tried to factory reset it many times from the fastboot menu. thank you for reading
I've had that problem before on previous HTC devices. Unlock the boot loader and root eveeythinf/soff again. Forgot exactly how I fixed it but I know I had to root, soff, unlock boot loader again. Think it's whenever u relock the boot loader it messes things up.
Sent from the one and only HTC One
thanks ill try that out
Is there any way to flash twrp via fast-boot. Or flash stock firmware when the o.s has been deleted and only have stock recovery and oem locked boot loader. I'm trying to somehow avoid a lengthy rma
If I have no o.s due to a twrp data format and reboot why would toolkit call for oem unlock in system settings.
Anyway guys?
I was oem unlocked with twrp but after a failed firmware restore I stupidly re locked bootlaoder thinking I would boot past the Google splash screen which it won't and I realize the wugfresh firmware script malfunctioned half way thru.
Sent from my LGMS769 using XDA Free mobile app
@androidddaaron,
Do you still have TWRP installed?
Edit: Just noticed that you said you wanted to flash TWRP. Under the circumstances, you'd better start the RMA process.
androidddaaron said:
Is there any way to flash twrp via fast-boot. Or flash stock firmware when the o.s has been deleted and only have stock recovery and oem locked boot loader. I'm trying to somehow avoid a lengthy rma
If I have no o.s due to a twrp data format and reboot why would toolkit call for oem unlock in system settings.
Anyway guys?
I was oem unlocked with twrp but after a failed firmware restore I stupidly re locked bootlaoder thinking I would boot past the Google splash screen which it won't and I realize the wugfresh firmware script malfunctioned half way thru.
Sent from my LGMS769 using XDA Free mobile app
Click to expand...
Click to collapse
your only option is to fastboot format userdata and cache. but most likely it wont work, since you dont have twrp installed. the next option would be to rma.
So I didn't realize that check box for oem unlock/lock was so critical!
So when I get my New phone and oem unlock it which is wise so you can always fix firmware, how do you make a nexus stock after rooting incase you wanna return it for exchange if you oem lock after firmware flash fresh If the phone reboots fine then it must be safe to relock I understand leaving it unlocked is perfectly fine in most circumstance too besides for rma . Motorola techs won't complain I hope seeing no O.S installed and won't boot up, they hold 600$ incase you don't return it.But also I hope they don't charge that if they see its been oddly tampered with. All I said was I took the 5.1.1 OTA and it wouldn't reboot stuck on Google splash.Tho fastboot shows all info and oem locked status but will they' see something tripped kinda like Samsung Knox and suspect owner caused the issue
I already did rma waiting 4 days for advanced replacement. They said they just send it out and I send in old phone and they release the 600$ hold,upon receiving device, not after its checked out, as far as I see it oem locked and no fimware on device Not even they could fix it. I'm betting all they can do is add a new motherboard. I learned to stay far away from that lock button on the tool kit
Sent from my LGMS769 using XDA Free mobile app
androidddaaron said:
So I didn't realize that check box for oem unlock/lock was so critical!
So when I get my New phone and oem unlock it which is wise so you can always fix firmware, how do you make a nexus stock after rooting incase you wanna return it for exchange if you oem lock after firmware flash fresh If the phone reboots fine then it must be safe to relock I understand leaving it unlocked is perfectly fine in most circumstance too besides for rma . Motorola techs won't complain I hope seeing no O.S installed and won't boot up, they hold 600$ incase you don't return it.But also I hope they don't charge that if they see its been oddly tampered with. All I said was I took the 5.1.1 OTA and it wouldn't reboot stuck on Google splash.Tho fastboot shows all info and oem locked status but will they' see something tripped kinda like Samsung Knox and suspect owner caused the issue
I already did rma waiting 4 days for advanced replacement. They said they just send it out and I send in old phone and they release the 600$ hold,upon receiving device, not after its checked out, as far as I see it oem locked and no fimware on device Not even they could fix it. I'm betting all they can do is add a new motherboard. I learned to stay far away from that lock button on the tool kit
Sent from my LGMS769 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry for your troubles but there are several threads about this very issue. Next time, I suggest you do a fair bit of reading beforehand to avoid similar situations.
Not really an issue but just an annoyance. Since i updated to EMUI 5 and recovering from a soft brick to fully working every time i power off my phone i get the message above re unlocked. Is this the bootloader that is unlocked and is it an easy fix to get rid. Phone is running great with the update so far
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Sean Hicks said:
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Click to expand...
Click to collapse
Buying it "unlocked" means you bought it free of a carrier, such as Verizon, who lock the bootloader, and can't be unlocked.
But you still need to unlock the bootloader, it comes locked, for security reasons. So if you never unlocked it, it's locked.
I haven't installed beta 12 yet.
Do you have the latest SDK tools? (adb, fastboot, etc)
I was under the impression though, that you can't downgrade with a locked bootloader. But not sure.
Sean Hicks said:
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Click to expand...
Click to collapse
This probably isn't of any help now, but going forward, it may be. In Developer options, you can enable 'OEM unlocking'. As you can see now, it may well be a very good idea to enable that **before** you start messing with the phone, because if something does go wrong (as it has for you), then you can (hopefully) still get to fastboot and do 'fastboot flashing unlock'.
So, knowing this, you may want to keep an eye out for some tool or something that will allow you to possibly turn on oem unlocking (because your device won't boot).
Another thing to try is switching slots and see if the other slot boots? If you can get to fastboot try; fastboot --set-active=(a or b), then fastboot reboot. (If you don't know which slot is active, do 'fastboot getvar all', in the output it will tell you which is current.
cheers
Your bootloader being locked should not affect your ability to restore factory images/OTAs from Google. They are signed by Google and will pass the signature checks. You should try to download the latest factory image (either 11 or 12beta) and flash it via recovery => adb sideload.
Hello
Hoping somebody can help getting my phone up and running again.
I wanted to unroot my phone, because i was having issues with danish "MitId". And was a bit sloppy with it.
First i tried using SuperSU to remove root. Because i didnt feel like setting everything up again. Didnt work.
Then I locked the OEM Lock in developer settings. Not thinking this would be a fatal error.
Got home from work, and said to myself. Jusk lock the bootloader and the phone will reset itself.
But this is not the case, when you have been stupid enough to lock the OEM lock.
Now I am stuck on "No valid operating system could be found. The device will not boot"
I can get in to fastboot by pushning power+vol down. But cannot flash anything since the phone thinks the OEM Lock is locked on it.
Does anyone know of a solution for me. Or is it going to the shop tommorow and say that my phone is going this. And hope they will sort it for me?
Can't you fix stuff by using https://flash.android.com/ ?
No, unfortuantly not. It fails:
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
Pearsondk said:
No, unfortuantly not. It fails:
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
Click to expand...
Click to collapse
Try sideloading the full OTA. You don't need an unlocked bootloader for that.
Unfortuatly not, if I try to enter recovery mode. The phone just goes back to the screen saying "No valid operating system could be found. The device will not boot"
ADB is not available to me
If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.
Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
*****I apologize I just saw it's actually still locked****"
Contact U-break I-fix if I typed that correctly. The third party warranty repair center for Google's warranty. I believe they can attempt to switch the boot slot with a locked bootloader with the equipment they use to reflash these devices. If anything it's under warranty get the RMA and if the bootloader is locked on it trade someone or sell it and use it to make buying a new cheaper..
JovialQuestion said:
Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
Click to expand...
Click to collapse
No, I can get into fastboot and that is it.
But everything I try in fastboot gets rejected, since it says the phone is locked.
Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
JovialQuestion said:
Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works. Use the volume keys and power button to select it
Click to expand...
Click to collapse
Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
Google is not responsible for phone's with locked bootloaders. They make the device with the specifications the carrier that sells it stipulates. Google themselves allows the unlock.
Lughnasadh said:
If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.
Click to expand...
Click to collapse
Iam guessing the same. Phone doesnt want to do anything.
And since i cant get into the phone to oem lock i am stuck. Live in Denmark, so by law I havnt voided the warrenty by rooting.
Pixel warranty is always valid even if you unlock and root. Google doesn't void the warranty. Go to Google pixel support page. Find warranty and act as if your submitting a RMA and it will tell you after you enter the device IMEI how long your warranty is valid for
Delete
If that were true. Android flash tool https://flash.android.com/welcome
Would work as it's the same process for the browser to flash the very same file. Motorola allowed signed factory img on locked. Google had never allowed that in fastboot as far as I am aware
DroidRommer said:
All you need to do is go here Factory pixel firmwares and scroll down to pixel 7 panther assuming you're not on the pro (cheetah)
-select the latest version for your model whether that's Verizon or whatever if you have the carrier unlocked one like myself just choose the Feb firmware that doesn't have a carrier name at the end of the firmware number (you should have your phone plugged into your PC and in fastboot mode) click flash and follow the steps. These are Googles factory images so it doesn't matter if your bootloader is unlocked or not as long as you choose the latest version and the correct version for your phone. Tbh you can't really brick the pixel 7 as long as you have a PC and are able to put the phone in fastboot mode (holding the volume down and power button while powering on)
-Anytime you run into some kind of bootloop issue or wanna get rid of root flashing the stock firmware from this website will factory reset and revert your phone to the way it was the very first time it was pulled out of the box and powered on. If you have already tried this and you know forsure you did everything correctly then I must admit I have never had this happen and I'm someone who flashes custom roms and goes back to stock to get the latest security update just to turn around and flash another custom rom right after lol. If you need any help or advice feel free to pm me whenever. I have been rooting phones for a long time and have to say that the Google pixel is by far the most user friendly phone I've ever owned when it comes to custom rooms, rooting etc. You can ALWAYS go back as long as you know what steps to take. Sorry for the rant especially if you already figured it out.
Happy Customizing!
DROIDROMMER
Click to expand...
Click to collapse
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.
Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Edit: I was not aware you couldn't flash the stock firmare using googles dev page without oem unlock. I apologize for jumping to conclusions. I thought I had every possible bad scenario happen to me by now but apparently I learned something new today.
DroidRommer said:
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Click to expand...
Click to collapse
Dude. You cannot flash factory images of any kind on any Google phone with the bootloader in locked status. Please stop giving false information on here. If you want to talk up Samsung do it on a Samsung post. Let's not confuse everyone please
DroidRommer said:
Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader.
Click to expand...
Click to collapse
To use Android Flash Tool, you have to have OEM Unlocking enabled in Developer Options for it to be able to unlock the bootloader.
To flash the factory image in fastboot you must have an unlocked bootloader.
Lughnasadh said:
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.
Click to expand...
Click to collapse
Okay my bad you are right fortunately I have never had this happen. And like someone else said if he can't get into recovery then he can't sideload a factory ota... sorry I'm at a loss on this one. Some custom roms use "fastboot update file.zip" would that do anything in this case or would that command not even work with a locked bootloader I'm assuming. I apologize for trying to act like a know it all I've just never heard of this happening