So, was thinking to give dp5 a try since I have a OnePlus 6 as a main phone now, and get the pixel with a fresh Android 9 flavour before putting it up for sale.
But, don't know why I thought it's a good idea to lock the bootloader first then get the OTA.
But since I was running nitrogenOS, after locking the bootloader, the phone won't boot, giving the "No valid os to boot" screen.
Stock recovery is inexistent as well, can only boot to fastboot but I've tried to boot/flash with no lock, it tells me it cannot be done on a locked state.
If anyone can help me saving the phone, I'd be really thankful, can even pay for a couple of beers too.
The phone was bought 2nd hand and I can't RMA it. Please let me know if there's anything else I could try to bring it back to life. Thank you everyone.
Sent from my ONEPLUS A6003 using Tapatalk
Blue305 said:
So, was thinking to give dp5 a try since I have a OnePlus 6 as a main phone now, and get the pixel with a fresh Android 9 flavour before putting it up for sale.
But, don't know why I thought it's a good idea to lock the bootloader first then get the OTA.
But since I was running nitrogenOS, after locking the bootloader, the phone won't boot, giving the "No valid os to boot" screen.
Stock recovery is inexistent as well, can only boot to fastboot but I've tried to boot/flash with no lock, it tells me it cannot be done on a locked state.
If anyone can help me saving the phone, I'd be really thankful, can even pay for a couple of beers too.
The phone was bought 2nd hand and I can't RMA it. Please let me know if there's anything else I could try to bring it back to life. Thank you everyone.
Click to expand...
Click to collapse
You should have returned to full stock before locking the bootloader my friend. You should be able to unlock it again, and then fastboot the factory image with the flash-all.bat script to get you up and running.
Badger50 said:
You should have returned to full stock before locking the bootloader my friend. You should be able to unlock it again, and then fastboot the factory image with the flash-all.bat script to get you up and running.
Click to expand...
Click to collapse
Agreed, as long as the OP did not also uncheck the oem switch...
Please, anyone reading this... Do Not RELOCK your boot loader unless you are 100% back to stock. Again, not stock... No RELOCK!!
To the OP, please report back how you make out!
CyberpodS2 said:
Agreed, as long as the OP did not also uncheck the oem switch...
Please, anyone reading this... Do Not RELOCK your boot loader unless you are 100% back to stock. Again, not stock... No RELOCK!!
To the OP, please report back how you make out!
Click to expand...
Click to collapse
Well bruh, if he did uncheck OEM unlocking, it's....
"Turn out the lights the party's over" You are now the proud owner of a fancy paperweight! ?
I didn't messed up with the OEM unlock from developer options, but I can't unlock the bootloader from fastboot unfortunately.. tried the flash.all as well, but I'd doesn't do much , keeps telling me that the phone is in a lock state...
Sent from my ONEPLUS A6003 using Tapatalk
Blue305 said:
I didn't messed up with the OEM unlock from developer options, but I can't unlock the bootloader from fastboot unfortunately.. tried the flash.all as well, but I'd doesn't do much , keeps telling me that the phone is in a lock state...
Click to expand...
Click to collapse
Which command did you use when you locked it?
You may want to look into Deuces recovery script as well to get you out of this pickle.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Badger50 said:
Which command did you use when you locked it?
You may want to look into Deuces recovery script as well to get you out of this pickle.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Thank you, but unfortunately I've ran the script but nothing happened, still cannot get it unlocked or boot to recovery
Sent from my ONEPLUS A6003 using Tapatalk
Blue305 said:
Thank you, but unfortunately I've ran the script but nothing happened, still cannot get it unlocked or boot to recovery
Click to expand...
Click to collapse
Then possibly try different cables and USB ports. Again, which command(s) did you use to lock the bootloader???
Sometimes you have to run Deuces a few times to get it too work.
Badger50 said:
Then possibly try different cables and USB ports. Again, which command(s) did you use to lock the bootloader???
Sometimes you have to run Deuces a few times to get it too work.
Click to expand...
Click to collapse
I'll try different cables then.
I've used fastboot flashing lock, and now is locked, and can't boot to recovery or start os, just boot to bootloader.n
Sent from my ONEPLUS A6003 using Tapatalk
in fastboot, do:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Blue305 said:
So, was thinking to give dp5 a try since I have a OnePlus 6 as a main phone now, and get the pixel with a fresh Android 9 flavour before putting it up for sale.
But, don't know why I thought it's a good idea to lock the bootloader first then get the OTA.
But since I was running nitrogenOS, after locking the bootloader, the phone won't boot, giving the "No valid os to boot" screen.
Stock recovery is inexistent as well, can only boot to fastboot but I've tried to boot/flash with no lock, it tells me it cannot be done on a locked state.
If anyone can help me saving the phone, I'd be really thankful, can even pay for a couple of beers too.
The phone was bought 2nd hand and I can't RMA it. Please let me know if there's anything else I could try to bring it back to life. Thank you everyone.
Click to expand...
Click to collapse
You can give a try for RMA... they sometimes accept RMA for 2nd hand devices as well
ram4ufriends said:
You can give a try for RMA... they sometimes accept RMA for 2nd hand devices as well
Click to expand...
Click to collapse
Thanks, I didnt know that. Is there a specific number I need to call? Thanks again.
Sent from my ONEPLUS A6003 using Tapatalk
uicnren said:
in fastboot, do:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
I've tried that but it doesnt allow me to do it
Sent from my ONEPLUS A6003 using Tapatalk
Blue305 said:
I've tried that but it doesnt allow me to do it
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
What specifically is the error you receive?
If you want help, you should provide as much detail as possible.
Have you tried recovery and sideloading a full OTA image? I know you said 'stock recovery is inexistent' what does that mean, you get the 'no command' screen with red triangle?
uicnren said:
What specifically is the error you receive?
If you want help, you should provide as much detail as possible.
Have you tried recovery and sideloading a full OTA image? I know you said 'stock recovery is inexistent' what does that mean, you get the 'no command' screen with red triangle?
Click to expand...
Click to collapse
I'm sorry, you're right, I should have been more specific.
The error looks like this:
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.001s
Also, when I try to boot in the recovery, Nothing happens, the device reboots, Showing me the normal screen "Can't find valid operating system, The device will not start".
I can only get to fastboot, I've tried "adb devices" while in fastboot but nothing is detected.
Thank you for the help so far, if there's anythiing else I could try, please tell me.
This is what it looks like.
View attachment 4562979
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONEPLUS A6003 using Tapatalk
Blue305 said:
I'm sorry, you're right, I should have been more specific.
The error looks like this:
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.001s
Also, when I try to boot in the recovery, Nothing happens, the device reboots, Showing me the normal screen "Can't find valid operating system, The device will not start".
I can only get to fastboot, I've tried "adb devices" while in fastboot but nothing is detected.
Thank you for the help so far, if there's anythiing else I could try, please tell me.
Click to expand...
Click to collapse
adb commands will never work in bootloader.
try: fastboot devices
if the unlocking commands are denied, then it seems like OEM unlocking has defaulted to locked without there being a valid OS and/or no recovery.
if that is the case and you cannot unlock the bootloader, you wont be able to install an OS.
Also how are you trying to get to recovery, I will assume from the hardware buttons while in fastboot?
for fun (not that it should make a difference) try: fastboot reboot recovery
Also out of curiosity, what version of fastboot are you currently using?
uicnren said:
adb commands will never work in bootloader.
try: fastboot devices
if the unlocking commands are denied, then it seems like OEM unlocking has defaulted to locked without there being a valid OS and/or no recovery.
if that is the case and you cannot unlock the bootloader, you wont be able to install an OS.
Also how are you trying to get to recovery, I will assume from the hardware buttons while in fastboot?
for fun (not that it should make a difference) try: fastboot reboot recovery
Click to expand...
Click to collapse
YEs, the unlocking comands are denied.
I used the volume keys to try and get to recovery, but no luck..
That command doesn't work either.
I really don't know what else to do, im quite desperate
Blue305 said:
YEs, the unlocking comands are denied.
I used the volume keys to try and get to recovery, but no luck..
That command doesn't work either.
I really don't know what else to do, im quite desperate
Click to expand...
Click to collapse
Sorry, I added some questions to previous reply, what version of fastboot are you using?
try: fastboot --version
uicnren said:
Sorry, I added some questions to previous reply, what version of fastboot are you using?
try: fastboot --version
Click to expand...
Click to collapse
it's this one:
fastboot version 0.0.1-4500957
Installed as G:\platform-tools\fastboot.exe
Related
Hi, everyone been searching the forums to no avail.
I have a stock unmodified Nexus 7 2013 and was watching a video the other day when it just froze. I restart it manually and now it won't get past the "Google" screen at startup. I'm able to get to he bootloader (vol down+ pwr) but can't unlock with fastboot nor can I erase any partitions using fastboot. I'm basically preparing to wipe and re-install the stock ROM over top.
Steps taken so far:
using fastboot, the "fastboot devices" command works and returns a result
Got as far as the OEM Unlock screen, and entered Yes to perform unlock but it hangs (even overnight)
but when trying to use "fastboot erase boot" or erase any other partitions, it also hangs.
Just to be clear, this is what I'm doing
C:\fastboot>fastboot devices
079bd1ae fastboot
(This works fine)
C:\fastboot>fastboot oem unlock
(Proceed to unlock on-screen -> HANGS)
C:\fastboot>fastboot erase boot
erasing 'boot'...
(HANGS)
Thanks,
Ryan
ksin86 said:
Hi, everyone been searching the forums to no avail.
I have a stock unmodified Nexus 7 2013 and was watching a video the other day when it just froze. I restart it manually and now it won't get past the "Google" screen at startup. I'm able to get to he bootloader (vol down+ pwr) but can't unlock with fastboot nor can I erase any partitions using fastboot. I'm basically preparing to wipe and re-install the stock ROM over top.
Steps taken so far:
using fastboot, the "fastboot devices" command works and returns a result
Got as far as the OEM Unlock screen, and entered Yes to perform unlock but it hangs (even overnight)
but when trying to use "fastboot erase boot" or erase any other partitions, it also hangs.
Just to be clear, this is what I'm doing
C:\fastboot>fastboot devices
079bd1ae fastboot
(This works fine)
C:\fastboot>fastboot oem unlock
(Proceed to unlock on-screen -> HANGS)
C:\fastboot>fastboot erase boot
erasing 'boot'...
(HANGS)
Thanks,
Ryan
Click to expand...
Click to collapse
Try using Wug"s Nexus Root Toolkit
aniket0317 said:
Try using Wug"s Nexus Root Toolkit
Click to expand...
Click to collapse
Hi, thanks for the tip, I have been using it but maybe not doing it correctly?
I'm assuming that the toolkit does the same thing as my fastboot commands but I'll give it a try again.
Could you give me some direction or instructions as how to proceed?
Nobody knows how to fix the tablets that won't unlock. Many have asked, none have ever gotten an answer as far as I know.
Going with hardware failure, RMA.
You could try a different cable and USB 2.0 port. But don't hold your breath.
Aerowinder said:
Nobody knows how to fix the tablets that won't unlock. Many have asked, none have ever gotten an answer as far as I know.
Going with hardware failure, RMA.
You could try a different cable and USB 2.0 port. But don't hold your breath.
Click to expand...
Click to collapse
Well, that's an idea. I'll try it out. Thanks.
ksin86 said:
Well, that's an idea. I'll try it out. Thanks.
Click to expand...
Click to collapse
Okay, doesn't seem like it's working. Are there any tips on doing an RMA on this guy or just regular procedure?
Thanks.
Can you flash a custom recovery? (Or boot into one) flashing a new stock image will solve problems. Twrp will mount a USB OTG If you get the right one. Maybe you could flash a ROM from a USB OTG. /sdcard probably wouldn't mount.
sent from my nex7
mugzylol said:
Can you flash a custom recovery? (Or boot into one) flashing a new stock image will solve problems. Twrp will mount a USB OTG If you get the right one. Maybe you could flash a ROM from a USB OTG. /sdcard probably wouldn't mount.
sent from my nex7
Click to expand...
Click to collapse
Thanks for the reply. But unfortunately I can't even run the OEM Unlock command to be able to to flash anything...
Did you double-check how the drivers are installed? What does "fastboot devices" say?
If you can't unlock via a manual fastboot command, it's doubtful Wug's tool will do any better. I wish I had an answer for you, because while not "common," this does come up from time to time. It may or may not be hardware failure, but every time it seems something in the bootloader got corrupted/damaged. It makes me glad that with my two N7 generations, I unlocked almost immediately as part of rooting.
I think there's a "boot.img" file as part of the stock ROM package. Even though you're unlocked, maybe you can try flashing it? Just that file, not any of the others.
https://developers.google.com/android/nexus/images
Had the exact same thing happen... Help!
Unfortunately, I had the exact same thing happen. My nexus 7 is not quite a year old now. Worked perfectly before, but suddenly this week it died.
Have been trying the toolkit today to no avail as it is still locked.
If anyone knows of a solution, would be very grateful for the help. I now have a useless brick.
It might be eMMC failure. There doesn't seem to be a fix to do at home, at least not with fastboot, so hurry and get an RMA while it's still in warranty.
Pandae said:
It might be eMMC failure. There doesn't seem to be a fix to do at home, at least not with fastboot, so hurry and get an RMA while it's still in warranty.
Click to expand...
Click to collapse
Thanks guys for all the input. I'll be sending it in ASAP.
Thanks!
Hi all, i have a massive problem. I was using FreedomOS 1.6 [OOS 3.2.7] Rom and went to boot into twrp 3.0.2-0 and now i have no recovery phone doesnt boot, i can boot into fastboot/bootloader mode, i have flashed twrp again and it still dosent boot into recovery.
Please guys this is so frustrating any help is MASSIVELY appreciated
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Follow this:
http://forum.xda-developers.com/showpost.php?p=69141963&postcount=5
kgs1992 said:
Follow this:
http://forum.xda-developers.com/showpost.php?p=69141963&postcount=5
Click to expand...
Click to collapse
still no luck. still boots to a screen saying boot:failed recovery:failed
phonetech101 said:
still no luck. still boots to a screen saying boot:failed recovery:failed
Click to expand...
Click to collapse
I'd the same problem look there, solved by following @kgs1992 instructions !
keviiin38 said:
I'd the same problem look there, solved by following @kgs1992 instructions !
Click to expand...
Click to collapse
still no luck, bootloader is locked and i cant boot phone to enable oem unlock ****kkkkkkkkk
phonetech101 said:
still no luck, bootloader is locked and i cant boot phone to enable oem unlock ****kkkkkkkkk
Click to expand...
Click to collapse
Did you tried @kgs1992 answer ?
kgs1992 said:
Follow this:
http://forum.xda-developers.com/showpost.php?p=69141963&postcount=5
Click to expand...
Click to collapse
i have same problem and my phone now on bootloop how can i fix it
please help us
keviiin38 said:
Did you tried @kgs1992 answer ?
Click to expand...
Click to collapse
nope once bootloader is locked and phone cant boot into system to turm oem unlocking on ur stuffed, so i have a useless phone but open to more suggestions.
phonetech101 said:
nope once bootloader is locked and phone cant boot into system to turm oem unlocking on ur stuffed, so i have a useless phone but open to more suggestions.
Click to expand...
Click to collapse
Relocking was a bad idea, you just ran out of all options.
I'm not sure if there is any way around enabling OEM unlocking.
Try the previous suggestion.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Snapdragons are truly unbrickable. But I'm not sure I know enough to help.
kgs1992 said:
Relocking was a bad idea, you just ran out of all options.
I'm not sure if there is any way around enabling OEM unlocking.
Try the previous suggestion.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Snapdragons are truly unbrickable. But I'm not sure I know enough to help.
Click to expand...
Click to collapse
did it again, cant boot into recovery. tried "fastboot boot recovery.img came back with
error (remote: unlock device to use this command"
this is what it boot loops to and from
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
this is what i see when i boot up
I'm fairly sure fastboot boot <image> doesn't even work if the bootloader is unlocked on the op3.
Also, it looks like recovery did get flashed.
Try rebooting to recovery?
Power off by holding power button, then hold vol down + power.
Then if you are booted into stock recovery, just side load the stock ROM.
kgs1992 said:
I'm fairly sure fastboot boot <image> doesn't even work if the bootloader is unlocked on the op3.
Also, it looks like recovery did get flashed.
Try rebooting to recovery?
Power off by holding volume button, then hold vol down + power.
Then if you are booted into stock recovery, just side load the stock ROM.
Click to expand...
Click to collapse
Na it won't boot into recovery, have flashed stock recovery tried modified recovery tried twrp recovery none off them boot into recovery :/
I wish I could get into recovery then I'm fine from there
Boooommm done it, thanks everyone for your help.
mix-75 said:
i have same problem and my phone now on bootloop how can i fix it
please help us
Click to expand...
Click to collapse
Did you fix yours mate?? I have the fix. Download this https://www.androidfilehost.com/?fid=24591000424942573
Its got the boot.IMG and system.IMG files unlike the others.
This tool can not read my device all tiame no device no device
All drivers is setup on my computer but this tool not read
I have same your screen shoot below
But mype more files is filled, just 3 or 4 file is ok
I hate this problem :crying:
mix-75 said:
This tool can not read my device all tiame no device no device
All drivers is setup on my computer but this tool not read
I have same your screen shoot below
But mype more files is filled, just 3 or 4 file is ok
I hate this problem :crying:
Click to expand...
Click to collapse
My friend I had same problem.
1. Plug phone into computer
2. Turn phone off by holding down power for 40 seconds,
3. Now run unbrick tool with admin.
4. Hold volume up on phone till program reads phone then press start.
Hello, today i flashed one of the new nougat stock roms. The first boot was fine, everything worked perfectly . But after rebooting I've got the "your device is corrupt. it cannot be trusted and it may not work properly" message, and it wont boot anymore. I cant go into recovery and i cant go into download mode because i get the same the same message and the phone reboots. i can only access the fastboot mode for bootloader unlock, and apparently that my bootloader is now locked. So I've tried to unlock the bootloader again, but it says "Wrong Bootloader Unlock key". Anyone has any idea?
darkstewie92 said:
Hello, today i flashed one of the new nougat stock roms. The first boot was fine, everything worked perfectly . But after rebooting I've got the "your device is corrupt. it cannot be trusted and it may not work properly" message, and it wont boot anymore. I cant go into recovery and i cant go into download mode because i get the same the same message and the phone reboots. i can only access the fastboot mode for bootloader unlock, and apparently that my bootloader is now locked. So I've tried to unlock the bootloader again, but it says "Wrong Bootloader Unlock key". Anyone has any idea?
Click to expand...
Click to collapse
I have the exact same problem and to be honest I think we are f*****. I haven't found any way to re-unlock the bootloader since it seems that the unlock.bin doesn't match with the Device-ID anymore.
This is an IMEI problem. It goes to 0, so the unlock.bin no longer works. I also had this message but my phone was still booting. So I was able to solve the problem.
But you, you can not start your phone, so I do not know how to fix your problem. Sorry
Pif0u said:
This is an IMEI problem. It goes to 0, so the unlock.bin no longer works. I also had this message but my phone was still booting. So I was able to solve the problem.
But you, you can not start your phone, so I do not know how to fix your problem. Sorry
Click to expand...
Click to collapse
No it isn't an IMEI problem, I can reboot my phone and I can access the download mode to flash a KDZ which I did.
EDIT: Oh but I just see in the settings that my IMEI indeed turned into a zero... I do have a TWRP backup of my IMEI.
I quess it's a better idea to make my own G4 Q&A, Help & Troubleshooting thread for help.
I reply in your topic
Pif0u said:
Tutorial to restore imei
1 -Go to phone dial
2- Type *#546368#*815#
3- Go to SVC Menu
4- Go to Port Check Test
5 - Enable Port check test
6 - Download this :
Code:
https://mega.nz/#!cZ9TxBLT!v9qEfeNTeCKYw8XoAhaMOkN48pp4WtLBCU_8KlYeERs
7 - Run the program
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8 - Click to Qualcomm NV Tools
9 -
10 - Check the box IMEI, Write your IMEI in IMEI(dec) and click to write.
11 - Reboot phone
Click to expand...
Click to collapse
Oh... I just made my own thread, I didn't notice your reply because you didn't quote me... But thanks for this tutorial! I'll give it a try :good:
Pif0u said:
This is an IMEI problem. It goes to 0, so the unlock.bin no longer works. I also had this message but my phone was still booting. So I was able to solve the problem.
But you, you can not start your phone, so I do not know how to fix your problem. Sorry
Click to expand...
Click to collapse
Well, that's sad. This doesn't make any sense . RIP my loevely G4 I guess. Thank you anyway!
darkstewie92 said:
Well, that's sad. This doesn't make any sense . RIP my loevely G4 I guess. Thank you anyway!
Click to expand...
Click to collapse
Hhmm maybe you aren't totally lost, you can access Fastboot mode right, so how have you tried to access the Download mode? You pressed the Volume up button and connected your device with a USB?
It seems you have the same problem as I had, your IMEI turned into a "0", that's why your unlock.bin fails to flash. Just try to access the Download mode for a couple of times, maybe with a but of luck it wil boot into Download mode eventually.
Is there a way to change imei on nougat? Because i cant go in download mode to downgrade to mm
Having the same issue. Cant enter on download or recovery. Fking sht
---------- Post added at 02:30 PM ---------- Previous post was at 02:18 PM ----------
How r u accessing fastboot for bootloader unlock?
Mr.FREE_Bird said:
Hhmm maybe you aren't totally lost, you can access Fastboot mode right, so how have you tried to access the Download mode? You pressed the Volume up button and connected your device with a USB?
It seems you have the same problem as I had, your IMEI turned into a "0", that's why your unlock.bin fails to flash. Just try to access the Download mode for a couple of times, maybe with a but of luck it wil boot into Download mode eventually.
Click to expand...
Click to collapse
I've tried like 20 times already, unfortunately it reboots almost instantly.
We all have the same problem at this point I know that we either hold the smartphone so or we send it to assistance but considering that it is not covered by warranty do not know how long it is
pedrogcsb said:
Having the same issue. Cant enter on download or recovery. Fking sht
---------- Post added at 02:30 PM ---------- Previous post was at 02:18 PM ----------
How r u accessing fastboot for bootloader unlock?
Click to expand...
Click to collapse
press volume down while your phone is turned off, and then plug your usb cable connect to your pc.
darkstewie92 said:
press volume down while your phone is turned off, and then plug your usb cable connect to your pc.
Click to expand...
Click to collapse
Not working for me aswell
Randy_Orton91 said:
We all have the same problem at this point I know that we either hold the smartphone so or we send it to assistance but considering that it is not covered by warranty do not know how long it is
Click to expand...
Click to collapse
I don't even know if they are gonna repair it, and if they do, we will need to pay I guess, I don't how much.
darkstewie92 said:
I don't even know if they are gonna repair it, and if they do, we will need to pay I guess, I don't how much.
Click to expand...
Click to collapse
Use this guide, i solve the problem: https://forum.xda-developers.com/showpost.php?p=73498317&postcount=140
Randy_Orton91 said:
Use this guide, i solve the problem: https://forum.xda-developers.com/showpost.php?p=73498317&postcount=140
Click to expand...
Click to collapse
thank you, but i cant even boot into the ROM. It worked fine the first time,now it doesn't boot anymore.
darkstewie92 said:
thank you, but i cant even boot into the ROM. It worked fine the first time,now it doesn't boot anymore.
Click to expand...
Click to collapse
Same to me
Try this method to live your download mode - https://forum.xda-developers.com/g4/...lcomm-t3452853
You can try a last attempt before you give up if you can not fix it: write an email to [email protected] explains the problem that you've updated to nougat beta and now your bootloader has re-locked and your imei is set on 0 and so the unlock.bin file does not work, try to see if they send you a working one, yesterday I wrote the email and they also answered me asking for more info but I have now solved the problem. Attach the device id and a photo of the back of the phone where the imei is written. Try it
Hi im having a hard time figuring this out, this is a brand new 5t that bricked itself while ota updating
the device is in a boot loop (wont go any further than the oneplus logo)
if i enter to the recovery it says LOCKED, and the oem unlock option on android is not enabled
im in argentina so i cant send the phone to oneplus rma
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is there any way to unlock the bootloader? then i would be able to flash it and save the phone
Ps: a level 2 OnePlus tech guy tried a remote fix with the official brand software and it did not work
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Hope that helps. If you can get it to load in that mode, it'll fix about anything.
es0tericcha0s said:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Hope that helps. If you can get it to load in that mode, it'll fix about anything.
Click to expand...
Click to collapse
Thanks a lot! i think that oneplus did use that file and did not work but i will try it again (at least 10 times)
I think it might be tricky to get it into the QHUSB mode unless it's hard bricked. I've fixed a 3t like that but luckily haven't had issues on the 5t yet. I think the only way might be via test point (which would require some hardware work that's not recommended for beginners). Thinking about it now, this might not have been the best solution to provide for your particular issue.
Just thought about this after re-reading your post. When you say that you booted into Recovery and it says locked but you posted a picture of the Fastboot screen showing just that the bootloader is locked - which is to be expected unless you went through the bootloader unlock process.
What happens when you actually boot to recovery? Have you tried factory resetting it there? I imagine the remote desk guy might have tried to adb sideload the update?
This is why I wish we had a fastboot OEM image install option like Google provides.
Maybe we do though and I just haven't found it yet.
Haven't looked very hard.
es0tericcha0s said:
I think it might be tricky to get it into the QHUSB mode unless it's hard bricked. I've fixed a 3t like that but luckily haven't had issues on the 5t yet. I think the only way might be via test point (which would require some hardware work that's not recommended for beginners). Thinking about it now, this might not have been the best solution to provide for your particular issue.
Just thought about this after re-reading your post. When you say that you booted into Recovery and it says locked but you posted a picture of the Fastboot screen showing just that the bootloader is locked - which is to be expected unless you went through the bootloader unlock process.
What happens when you actually boot to recovery? Have you tried factory resetting it there? I imagine the remote desk guy might have tried to adb sideload the update?
Click to expand...
Click to collapse
if i boot to recovery and press the power button to select factory reset or any usefull option, the phone resets, i think that the problem is a corrupt recovery, thats why i want to unlock it, install TWRP and then try to flash android
CZ Eddie said:
This is why I wish we had a fastboot OEM image install option like Google provides.
Maybe we do though and I just haven't found it yet.
Haven't looked very hard.
Click to expand...
Click to collapse
maybe this is an anti thief security measure? (since android 6.0 )
es0tericcha0s said:
I think it might be tricky to get it into the QHUSB mode unless it's hard bricked. I've fixed a 3t like that but luckily haven't had issues on the 5t yet. I think the only way might be via test point (which would require some hardware work that's not recommended for beginners). Thinking about it now, this might not have been the best solution to provide for your particular issue.
Just thought about this after re-reading your post. When you say that you booted into Recovery and it says locked but you posted a picture of the Fastboot screen showing just that the bootloader is locked - which is to be expected unless you went through the bootloader unlock process.
What happens when you actually boot to recovery? Have you tried factory resetting it there? I imagine the remote desk guy might have tried to adb sideload the update?
Click to expand...
Click to collapse
why would i have a problem putting the 5t on qhusb? i did not know that it could be done via testpoint
the phone works, the problem seems to be a faulty file on the bootloader or maybe an internal damage from factory (i hope this is not the case)
in a few hours i will try it all and post the result
Typically a phone will only go into the Qualcomm QHUSB mode when it's hard bricked. You're only soft bricked. What happens when you actually get into Recovery?
es0tericcha0s said:
Typically a phone will only go into the Qualcomm QHUSB mode when it's hard bricked. You're only soft bricked. What happens when you actually get into Recovery?
Click to expand...
Click to collapse
I did the entire process and the result is the same as before doing it, the phone turns on and gets stuck on the oneplus logo, it does nothing else, the recovery works but doesnt do anything usefull
Do you get any errors when performing a factory reset? As in a partition not mounting? Since your baseband doesn't show in the fastboot mode, I'm thinking maybe an /efs error. If you got it new, I'd talk to 1+ about an RMA since this was caused by an official update and one of their technicians already failed to fix it.
es0tericcha0s said:
Do you get any errors when performing a factory reset? As in a partition not mounting? Since your baseband doesn't show in the fastboot mode, I'm thinking maybe an /efs error. If you got it new, I'd talk to 1+ about an RMA since this was caused by an official update and one of their technicians already failed to fix it.
Click to expand...
Click to collapse
It may well be a partition error, one+ is not being helpfull right now
I did comit an error saying that the recovery works, it doesnt work, the pone only goes into fastboot and qhusb mode, after that it will allways get stuck on the oneplus logo
On adb i get feedback if i try to flash the phone says "not allowed, locked device"
I think that the problem is a corrupt bootloader
The msmdownloader tool works, i dont know what It copies on to the terminal but i want to flash the recovery and bootloader using that tool, i dont know if it is possible
this the md5sum file that i found in a compilation for oneplusone (msmdownloader tool)
so i shoud be able to do the same with the 5t
es0tericcha0s said:
Typically a phone will only go into the Qualcomm QHUSB mode when it's hard bricked. You're only soft bricked. What happens when you actually get into Recovery?
Click to expand...
Click to collapse
that is no true, u just have the phone powered off and then hold the volume + and plug the device in, if u saw the video in the unbrick post he was not bricked at all and everything was working good and still did a restore, not sure why it is not working for the OP but it should fix it.
Yes i can enter into qhusb, and i can flash the phone with msm downloader, but i used the origibal file that oneplus technicians use amd it didnt work, now i want to flash hydrogen os or the recovery file only into the terminal but i dont know how to modify the msm downloader (the unbrick tool)
Had the same error message tonight after spontaneous reboot of my (unmodified and locked) device. Fortunately, reimaging with stock ROM from downloads.oneplus.net via adb sideload worked for me, without losing any data. Tried that?
sascha224 said:
Had the same error message tonight after spontaneous reboot of my (unmodified and locked) device. Fortunately, reimaging with stock ROM from downloads.oneplus.net via adb sideload worked for me, without losing any data. Tried that?
Click to expand...
Click to collapse
I remember that the device wouldnt flash anything because it was locked, but I will try the sideload right away
It has been impossible to fix, this is the best i got doing fastboot boot recovery.img
Hi
"Can't find valid operating system. The device will not start."
Then shows the visit g.co/ABH link.
I am not even able to boot into recovery. When selecting recovery from fastboot mode it just goes right to the same "Can't find valid operating system..." screen.
Device State: Locked
Developer Mode : Not Enabled and not possible to do now
PLease help me. As i am from Nepal , there is nothing i can't claim for warranty.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
senbros said:
Hi
"Can't find valid operating system. The device will not start."
Then shows the visit g.co/ABH link.
I am not even able to boot into recovery. When selecting recovery from fastboot mode it just goes right to the same "Can't find valid operating system..." screen.
Device State: Locked
Click to expand...
Click to collapse
Sorry, but with no working recovery and a locked bootloader you are dead in the water. There is nothing that can be done.
Are you able to unlock your bootloader? Might be able to download the factory image do it that way. Fastboot flashing unlock it something. Then run the flash all.bat from the factory image once you download it and unzipped it.
mammothjojo88 said:
Are you able to unlock your bootloader? Might be able to download the factory image do it that way. Fastboot flashing unlock it something. Then run the flash all.bat from the factory image once you download it and unzipped it.
Click to expand...
Click to collapse
I tried nothing works to unlock bootloader.. Still looking for solution..
Thank you for your time
Can't find valid operating system
senbros said:
Hi
"Can't find valid operating system. The device will not start."
Then shows the visit g.co/ABH link.
I am not even able to boot into recovery. When selecting recovery from fastboot mode it just goes right to the same "Can't find valid operating system..." screen.
Device State: Locked
Developer Mode : Not Enabled and not possible to do now
PLease help me. As i am from Nepal , there is nothing i can't claim for warranty.
Click to expand...
Click to collapse
Hi Mate,
I had the same thing happen Last Friday morning. I was just applying an OTA update, then when phone rebooted I got the same message on my Pixel 3 ( 2 weeks old ). I spent many hours over the weekend trying to figure out how to get a factory image on it. However without unlocking the bootloader ( which is not possible ), also having the recovery also corrupted, there is nothing we can do, except send it to a friend or someone we know and trust to get the phone repaired or if its under warranty still, possibly replaced by google. Sorry to be the giver of bad news. These are now expensive paper weights. It seems it becoming more common.
This is happening for more pixels. Google is must fix it remotely or pixel 4 might fail on landing.
issue resolved by google support
Hi,
i am having same issue with my pixel 3 last week, so i called Indian google service center ( 1800-419-0655 ) they pick up my phone from my place and resolve the issue.
so i will suggest you to visit/call google support team so they will resolve you issue.
---------- Post added at 06:03 AM ---------- Previous post was at 05:59 AM ----------
slysurfer said:
Hi Mate,
I had the same thing happen Last Friday morning. I was just applying an OTA update, then when phone rebooted I got the same message on my Pixel 3 ( 2 weeks old ). I spent many hours over the weekend trying to figure out how to get a factory image on it. However without unlocking the bootloader ( which is not possible ), also having the recovery also corrupted, there is nothing we can do, except send it to a friend or someone we know and trust to get the phone repaired or if its under warranty still, possibly replaced by google. Sorry to be the giver of bad news. These are now expensive paper weights. It seems it becoming more common.
Click to expand...
Click to collapse
hi there,
i had same issue last week, so i called google support. they pick up my pixel from my place and resolve the issue.
so please do the same contact google support. they will help you.
Problem in Pixel 3
They gave you a replacement or repaired the original device?? And how many days B2X took from pickup to delivering it back??
tailorhardik94 said:
Hi,
i am having same issue with my pixel 3 last week, so i called Indian google service center ( 1800-419-0655 ) they pick up my phone from my place and resolve the issue.
so i will suggest you to visit/call google support team so they will resolve you issue.
---------- Post added at 06:03 AM ---------- Previous post was at 05:59 AM ----------
hi there,
i had same issue last week, so i called google support. they pick up my pixel from my place and resolve the issue.
so please do the same contact google support. they will help you.
Click to expand...
Click to collapse
Not sure if anyone still needs help with this, but I just ran into this issue on my Pixel 4 XL and I held down the volume down button and power button to reboot into fastboot. From there you can connect to a PC and flash images or unlock/lock bootloader, etc.
From there I was able to use the flash.android.com site and flash the latest OTA to my phone and now I'm back up and running.
Hope this helps someone down the road.
bradwatson said:
Not sure if anyone still needs help with this, but I just ran into this issue on my Pixel 4 XL and I held down the volume down button and power button to reboot into fastboot. From there you can connect to a PC and flash images or unlock/lock bootloader, etc.
From there I was able to use the flash.android.com site and flash the latest OTA to my phone and now I'm back up and running.
Hope this helps someone down the road.
Click to expand...
Click to collapse
You can't do anything if you come across this problem whilst your bootloader is locked. I had a Pixel 3, applied ota via recovery and I got that error message. Couldn't do anything, flash factory image etc due to locked bootloader and recovery being corrupted.
Quite simply if it's under warranty, contact google.
kartikb said:
You can't do anything if you come across this problem whilst your bootloader is locked. I had a Pixel 3, applied ota via recovery and I got that error message. Couldn't do anything, flash factory image etc due to locked bootloader and recovery being corrupted.
Quite simply if it's under warranty, contact google.
Click to expand...
Click to collapse
Not entirely true. If OEM unlocking was previously enabled, then despite your phone being locked, it will still accept the unlocking command. Just happened to me. I am trading in my phone. I uninstalled Magisk, booted to bootloader, locked the bootloader and got the dreaded "Can't find valid operating system" alert. I thought it was toast since no response to adb at that point. The screen looked like the bootloader screen but with less text. Finally used vol down/pwr to get to bootloader, re-unlocked and re-flashed the OS. Back in business, at least getting my full trade-in price!
flash.android.com really helped, thank you!
device locked (locking the device is what caused this for me) and windows saying it doesnt recognize the device when I plugged it in while in the bootloader. For some reason flash.android.com recognized the device, not sure why
same thing happened with right now
i was trying to lock bootloader on custom rom (nonsense,i know)
so,phone wasnt being recognized by pc,and somehow android flash tool recognized and i clicked flashing and it needed bootloader to be unlocked so it did,and phone booted back on custom rom.
nice
yearn2burn said:
Not entirely true. If OEM unlocking was previously enabled, then despite your phone being locked, it will still accept the unlocking command. Just happened to me. I am trading in my phone. I uninstalled Magisk, booted to bootloader, locked the bootloader and got the dreaded "Can't find valid operating system" alert. I thought it was toast since no response to adb at that point. The screen looked like the bootloader screen but with less text. Finally used vol down/pwr to get to bootloader, re-unlocked and re-flashed the OS. Back in business, at least getting my full trade-in price!
Click to expand...
Click to collapse
Just happened to my Pixel 4a5G trade-in for Pixel 7. Completely uninstalled magisk and then tried to re-lock the bootloader. Bootloader locked and got the no operating system error. Called google and they said send it in as and I will get full amount. The dude did not sound very reassuring. I luckyly stumbled on this thread. tried to unlock the bootloader but it failed. I reset my computer and tried it again and it worked. Phone booted up. I took and OTA and tried to re-lock the bootloader and SUCCESS. This phone never had an OTA so I believe the one slot was empty, maybe that is why this happened. Moral to the story, make sure both slots has an OS on them.
Thanks
BB
bradwatson said:
Not sure if anyone still needs help with this, but I just ran into this issue on my Pixel 4 XL and I held down the volume down button and power button to reboot into fastboot. From there you can connect to a PC and flash images or unlock/lock bootloader, etc.
From there I was able to use the flash.android.com site and flash the latest OTA to my phone and now I'm back up and running.
Hope this helps someone down the road.
Click to expand...
Click to collapse
Thanks! This was exactly what I needed. I didn't realize you could get into fastboot with hardware controls and I was trying through adb
I'm an idiot and did this same thing.
bradwatson said:
Not sure if anyone still needs help with this, but I just ran into this issue on my Pixel 4 XL and I held down the volume down button and power button to reboot into fastboot. From there you can connect to a PC and flash images or unlock/lock bootloader, etc.
From there I was able to use the flash.android.com site and flash the latest OTA to my phone and now I'm back up and running.
Hope this helps someone down the road.
Click to expand...
Click to collapse
Just wanted to say thanks - had a panic moment until I read this and realized I could do that. Pixel 4 wiped and ready to go back. Thanks again, years later.