I still haven't received the January Security Update, so i tried updating via the OTA. But i get the following error message. When i type adb reboot recovery. Its like my stock recovery is broken because i get a no command error. My phone isnt' recognized in win10 anymore. Anyone else having this issue? My bootloader is unlocked. Not sure why that would matter.
Tried flashing factory image. I can't install because my bootloader doesn't match. Any ideas? I'm wondering if the January update isn't ready for my phone version
It maybe a bad data cable I had the same issue kinda cable must have put out to much power or something next day I tried it and everything worked.
Adb wouldn't work but fastboot commands would sometimes then next day was able to do all the commands to root and install kernal
Sent from my Pixel 2 XL using Tapatalk
sjpritch25 said:
Tried flashing factory image. I can't install because my bootloader doesn't match. Any ideas? I'm wondering if the January update isn't ready for my phone version
Click to expand...
Click to collapse
The boot loader not matching usually means you did not fully unlock it. I would bet you did unlock, but skipped unlock critical. You need the second one to be able to flash the bootloader. Otherwise you can only flash the same bootloader.
sjpritch25 said:
Tried flashing factory image. I can't install because my bootloader doesn't match. Any ideas? I'm wondering if the January update isn't ready for my phone version
Click to expand...
Click to collapse
Saw this same issue with another user on another thread. First of all, do you have OEM unlocking and USB debugging turned on in developer options?
Did you already run BOTH bootloader unlocking commands?
Since your OTA and factory image flash didn't work, you'll need to go back to the factory image you were on before you started this process.
If your able to get this all accomplished, then you can proceed to the January update. Best of luck :good:
How do I go about fully unlocking the bootloader? My phone came with 8.0. I do recall that after unlocking I got the mo command booting into recovery.
I do have OEM unlocking turned on
sjpritch25 said:
I do have OEM unlocking turned on
Click to expand...
Click to collapse
And you ran both bootloader unlocking commands?
---------- Post added at 04:06 AM ---------- Previous post was at 04:00 AM ----------
sjpritch25 said:
I do have OEM unlocking turned on
Click to expand...
Click to collapse
You probably should read this thread my friend.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Thanks. I see things I didn't do correct
I had to re flash december ota and now i just got done flashing January. Had to wipe phone again though to fix the unlocked bootloader.
sjpritch25 said:
I had to re flash december ota and now i just got done flashing January. Had to wipe phone again though to fix the unlocked bootloader.
Click to expand...
Click to collapse
unsuccessful updated to January image. I updated adb and still got the corrupt bootloader message. flashed december image and have a phone again. I guess, I might need to relock the bootloader and then unlock again? my current working bootloader is TMZ12a. The January image is TMZ12b i believe and for some reason its not working.
sjpritch25 said:
unsuccessful updated to January image. I updated adb and still got the corrupt bootloader message. flashed december image and have a phone again. I guess, I might need to relock the bootloader and then unlock again? my current working bootloader is TMZ12a. The January image is TMZ12b i believe and for some reason its not working.
Click to expand...
Click to collapse
In fastboot mode type
Fastboot oem device-info
Is unlock critical still locked?
If so, issue the command to unlock it. If that fails, yeah it looks like you will have to do what the other thread suggests and relock it.
sjpritch25 said:
I still haven't received the January Security Update, so i tried updating via the OTA. But i get the following error message. When i type adb reboot recovery. Its like my stock recovery is broken because i get a no command error. My phone isnt' recognized in win10 anymore. Anyone else having this issue? My bootloader is unlocked. Not sure why that would matter.
Click to expand...
Click to collapse
Don't do adb reboot recovery.
Turn it off, hold volume down, press power, and when bootloader screen shows, move volume button to choose Recovery.
When little green Android symbol shows, press Power, then Volume Up for a moment. You're now in Recovery.
Choose Apply Update from ADB, then follow instructions here: https://developers.google.com/android/ota
It will update you without wiping.
michaelbsheldon said:
Don't do adb reboot recovery.
Turn it off, hold volume down, press power, and when bootloader screen shows, move volume button to choose Recovery.
When little green Android symbol shows, press Power, then Volume Up for a moment. You're now in Recovery.
Choose Apply Update from ADB, then follow instructions here: https://developers.google.com/android/ota
It will update you without wiping.
Click to expand...
Click to collapse
Or adb reboot bootloader if you happen to be there but yes most of the time I just hit power to bring up restart then I hold volume down till it loads into bootloader
Sent from my Pixel 2 XL using Tapatalk
TonikJDK said:
In fastboot mode type
Fastboot oem device-info
Is unlock critical still locked?
If so, issue the command to unlock it. If that fails, yeah it looks like you will have to do what the other thread suggests and relock it.
Click to expand...
Click to collapse
I didn't have that & that was the issue earlier. I've done that & device was wiped again. Let me try those commands & I'll post them
TonikJDK said:
In fastboot mode type
Fastboot oem device-info
Is unlock critical still locked?
If so, issue the command to unlock it. If that fails, yeah it looks like you will have to do what the other thread suggests and relock it.
Click to expand...
Click to collapse
bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.038s]
finished. total time: 0.048s
sjpritch25 said:
bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.038s]
finished. total time: 0.048s
Click to expand...
Click to collapse
Download the full factory image. Not just the OTA. Open the flash-all.bat file and look near the end and edit out the -w and save it.
As long as you remove the -w that will flash the whole factory image but save your date, apps and set up.
So after the edit put it back in fastboot mode and run the flash-all.bat file.
Tried the January image & did that. Phone won't boot & I get corrupt message at bootlicker
sjpritch25 said:
Tried the January image & did that. Phone won't boot & I get corrupt message at bootlicker
Click to expand...
Click to collapse
Have you verified the sha-256 of the image you downloaded to ensure it's not corrupt?
Goto https://developers.google.com/android/images and copy the SHA-256 checksum from the Full Image you downloaded and compare it to the file downloaded here: http://onlinemd5.com/
- Make sure to choose sha-256 on the md5 site. This will rule out if the downloaded image you have is corrupted or not.
sjpritch25 said:
Tried the January image & did that. Phone won't boot & I get corrupt message at bootlicker
Click to expand...
Click to collapse
what version of adb/fastboot are you using ?
adb version
fastboot --version
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
michaelbsheldon said:
Don't do adb reboot recovery.
Click to expand...
Click to collapse
Why should they not do that ?
Related
Hi all,
I recently picked up a new Pixel and was wanting to flash it. I ended up enabling USB debugging and set OEM unlock within Android settings.
Yet when I use fastboot flashing unlock, it keeps telling me that OEM unlock isn't set. In my haste, I ran flash-all with a new Google build and this overwrote the existing ROM, but left the bootloader intact it seems. Now when I boot, it says I have a damaged OS and I should use recovery. The problem is that even recovery is damaged and it keeps rebooting to the bootloader. So adb won't work either. The only thing that works is fastboot.
Is there anything I can do to fix this or is it completely bricked? I can't seem to use fastboot to flash any ROM to the device - keeps erroring. I tried to match a ROM with the bootloader but that didn't work either.
Any ideas?
I used Nexus Root Toolkit when I got semi-bricked.
Use erase Command on flashboot for data and system then do flash_all again
As was mentioned, if you have fastboot you are ok. You can flash as mentioned above or use this -
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
NRT is good for people like me who barely know what they're doing, enough to get bricked in the first place like I did. What i like is that it takes away a little of the uncertainty about whether I'm using the right files.
I hadn't rooted and unlocked and done all the setup in about a year so I forgot everything.
Save yourself some trouble and look at the "TWRP bootloops" thread. It's easy to avoid if you follow some specific steps, frustrating otherwise.
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
d j a said:
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
Click to expand...
Click to collapse
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
cam30era said:
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
Click to expand...
Click to collapse
Yeah didn't think NRT would work because of the locked bootloader! Fastboot continue just gets out of fastboot - what is that gonna solve? I have a damaged set of partitions it seems - going from bootloader -> recovery boots back to the bootloader so it's clear that partition is damaged.
Is there any way I can just push some build to rebuild the partitions or can I do absolutely nothing until the bootloader is unlocked. And if so, how on earth can i unlock it if the only thing that works is fastboot?
hamazoza said:
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
Click to expand...
Click to collapse
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
I'll try that tonight. FWIW, I know I copied the line from flash-all to just flash recovery.img and even the system image, and both failed.
The only difference I see between that and yours is you have '-w update'. Maybe that's the trick.
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
hamazoza said:
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
Click to expand...
Click to collapse
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
d j a said:
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
Click to expand...
Click to collapse
I don't think that'll work. OEM unlock wasn't set in developer settings.
hamazoza said:
I don't think that'll work. OEM unlock wasn't set in developer settings.
Click to expand...
Click to collapse
You don't need that. I actually unlocked mine without it. The tool also has a unlock feature. Its worth a try.
Look for this forum post: flashing to stock android npd90g twrp t3424863
This helped me too. Only difference is I had TWRP installed.
Try unlocking bootloader via termjnal, then use the fastboot command via terminal (pc) fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable fastboot, then erase the partitions manually as mentioned in the tutorial and reflash them either manually or together using skipsoft / nrt or manual commands and a factory image.
Normally there should not be anything wrong with your bootloader image since modifying it is disabled for bootloader locked devices. Let us know about your progress.
Oh, also never flash an older system image than your current one.
It is stuck on a screen with the battery. I can get to bootloader mode but cannot get into recovery. Bootloader is locked... Please help
Basically I had the bootloader unlocked and it was rooted. I unrooted the phone and then I locked the bootloader and I am here now. Just wanted to make it go back to stock.
Is it a carrier model or a play store
https://forum.xda-developers.com/pixel-xl/how-to/psa-read-ca-bootloader-t3494615
This.
chapelfreak said:
Is it a carrier model or a play store
Click to expand...
Click to collapse
Google store
ASimpleSock said:
https://forum.xda-developers.com/pixel-xl/how-to/psa-read-ca-bootloader-t3494615
This.
Click to expand...
Click to collapse
I see the thread but it doesnt seem like theres a fix in it
tryfont said:
I see the thread but it doesnt seem like theres a fix in it
Click to expand...
Click to collapse
There probably isn't, if you've altered system and relock and toggle OEM unlocking off in dev. options you get bricked.
tryfont said:
It is stuck on a screen with the battery. I can get to bootloader mode but cannot get into recovery. Bootloader is locked... Please help
Basically I had the bootloader unlocked and it was rooted. I unrooted the phone and then I locked the bootloader and I am here now. Just wanted to make it go back to stock.
Click to expand...
Click to collapse
Did you try:
fastboot flashing unlock
Since you only relocked, you unlikely toggled "OEM unlock"?!
If it fails, I think you are SOL. Maybe someone with a proper solution will chime in. Otherwise, you have to RMA your device...
Good luck...
5.1 said:
Did you try:
fastboot flashing unlock
Since you only relocked, you unlikely toggled "OEM unlock"?!
If it fails, I think you are SOL. Maybe someone with a proper solution will chime in. Otherwise, you have to RMA your device...
Good luck...
Click to expand...
Click to collapse
It just says waiting for device and hangs there... I don't think it recognizes the phone
EDIT: IT WORKED!!!!!
It wouldnt recognize it and I ran fastboot continue and it just hanged there but I went into the bootloader mode and for like a quarter of a second it recognized it and forced it to boot
tryfont said:
It just says waiting for device and hangs there... I don't think it recognizes the phone
Click to expand...
Click to collapse
Open device manager in windows. Plug your phone and see how is your phone recognized.?!
5.1 said:
Open device manager in windows. Plug your phone and see how is your phone recognized.?!
Click to expand...
Click to collapse
Im on mac but its good now I edited my comment above. Only question is how to I completely clean the OS so I can relock bootloader without running into the same problem
This is whats happening to me- https://goo.gl/photos/2kv9Xo3HM3Mqn8AQ9
tryfont said:
Im on mac but its good now I edited my comment above. Only question is how to I completely clean the OS so I can relock bootloader without running into the same problem
Click to expand...
Click to collapse
Hey... Go into recovery and perform a factory reset.
Reboot bootloader and flash stock firmware. You could flash both slots to be sure your device is completely clean.
I wrote a how-to for someone having another issue. You.can follow this:
https://forum.xda-developers.com/showpost.php?p=71849370&postcount=28
When you are finished with flashing, reboot to be sure your system boot properly and your phone works as it should...
From here you can reboot into bootloader and issue:
fastboot flashing lock
If It was me I'd leave it unlocked though... Or at least OEM unlock enabled and ADB debugging ON. Since Google tend to release messed up OTA, you can always unlock the bootloader if needed.
But if you wish you can also disable the OEM unlock.
Good luck...
5.1 said:
Hey... Go into recovery and perform a factory reset.
Reboot bootloader and flash stock firmware. You could flash both slots to be sure your device is completely clean.
I wrote a how-to for someone having another issue. You.can follow this:
https://forum.xda-developers.com/showpost.php?p=71849370&postcount=28
When you are finished with flashing, reboot to be sure your system boot properly and your phone works as it should...
From here you can reboot into bootloader and issue:
fastboot flashing lock
If It was me I'd leave it unlocked though... Or at least OEM unlock enabled and ADB debugging ON. Since Google tend to release messed up OTA, you can always unlock the bootloader if needed.
But if you wish you can also disable the OEM unlock.
Good luck...
Click to expand...
Click to collapse
I'm pretty inexperienced with this kind of stuff and so you might have to explain it a bit further than what that link says. I did fastboot reboot bootloader in terminal but it can't find my device. Also I couldnt get into recovery when it was bricked so I probably still can't
tryfont said:
I'm pretty inexperienced with this kind of stuff and so you might have to explain it a bit further than what that link says. I did fastboot reboot bootloader in terminal but it can't find my device
Click to expand...
Click to collapse
Hey...
You boot into bootloader when the Device is powered off
Just like in your video: with power + volume down
You can see infos regarding:
Bootloader
Radio
S/N
DRAM
Boot-slot=
Etc...
This is the bootloader :good:
From here, unzip the google image you have downloaded, open the folder and from here run the flash-all script. Let your device reboot. Power it down, boot into bootloader again with power + volume down. Change active slot as I described in the link I gave you previously. Run the same flash-all again... Done!
Just for safety, remove your Google account before you continue. You'll add it again later...
Good luck...
5.1 said:
Hey...
You boot into bootloader when the Device is powered off
Just like in your video: with power + volume down
You can see infos regarding:
Bootloader
Radio
S/N
DRAM
Boot-slot=
Etc...
This is the bootloader :good:
From here, unzip the google image you have downloaded, open the folder and from here run the flash-all script. Let your device reboot. Power it down, boot into bootloader again with power + volume down. Change active slot as I described in the link I gave you previously. Run the same flash-all again... Done!
Just for safety, remove your Google account before you continue. You'll add it again later...
Good luck...
Click to expand...
Click to collapse
Alright thank you so much its doing the flashing right now. I really appreciate you helping...I was worried I'd have to get a replacement through google. Have a great day lad
tryfont said:
Alright thank you so much its doing the flashing right now. I really appreciate you helping...I was worried I'd have to get a replacement through google. Have a great day lad
Click to expand...
Click to collapse
Hey... Flash both slots... Just to be sure both are clean and nothing problematic remains on your device before locking your bootloader!
It could brick installing an OTA or whatever. Better restart 100% clean. :good:
Cheers...
Just flash the flash-all, relock and call it a day. Then you'll be fully stock and locked. I would however recommend rebooting once before locking to make sure its all good.
tryfont said:
It is stuck on a screen with the battery. I can get to bootloader mode but cannot get into recovery. Bootloader is locked... Please help
Basically I had the bootloader unlocked and it was rooted. I unrooted the phone and then I locked the bootloader and I am here now. Just wanted to make it go back to stock.
Click to expand...
Click to collapse
Hey man I have the same problem you can try calling Google support they can send you a replacement if you still have a warranty
my warranty has expired so I'm on my own
Hi there ,
i unlocked the boot loader and installed twrp and rooted my pixel 3xl and every thing was fine
until i wanted to install the new update for Feb under this link https://dl.google.com/dl/android/aosp/crosshatch-ota-pq2a.190205.001-4225fb81.zip
so i flashed the update over twrp and it gave me an error then i treid with flashify same thing .
when i couldn't install the new update i wanted to lock the boot loader again and i locked it by typing fastboot flashing lock
and of course the device did't boot up, so i unlocked the boot loader again and then entered to twrp and i wiped every thing 'including the operation system i think'
so now i can just lock and unlock the boot loader and i can't install the twrp again
when i try that this error pop up
fastboot boot twrp-3.2.3-3-crosshatch.img
Downloading 'boot.img' OKAY [ 1.493s]
booting FAILED (remote: 'Error calling AvbLoadAndVerifyBootImages Load Error')
Finished. Total time: 1.606s
i'm using the last version of the fastboot > platform-tools_r28.0.1-windows and 've an original cable i used it befor for the unlock the boot loader and installing the twrp
so now what please , how can i to install a new Rom for the my pixel , and there is no operation system i think cause i deleted every thing including the system throw twrp !
thank you in advance
Bashar Bachir said:
Hi there ,
i unlocked the boot loader and installed twrp and rooted my pixel 3xl and every thing was fine
until i wanted to install the new update for Feb under this link https://dl.google.com/dl/android/aosp/crosshatch-ota-pq2a.190205.001-4225fb81.zip
so i flashed the update over twrp and it gave me an error then i treid with flashify same thing .
when i couldn't install the new update i wanted to lock the boot loader again and i locked it by typing fastboot flashing lock
and of course the device did't boot up, so i unlocked the boot loader again and then entered to twrp and i wiped every thing 'including the operation system i think'
so now i can just lock and unlock the boot loader and i can't install the twrp again
when i try that this error pop up
fastboot boot twrp-3.2.3-3-crosshatch.img
Downloading 'boot.img' OKAY [ 1.493s]
booting FAILED (remote: 'Error calling AvbLoadAndVerifyBootImages Load Error')
Finished. Total time: 1.606s
i'm using the last version of the fastboot > platform-tools_r28.0.1-windows and 've an original cable i used it befor for the unlock the boot loader and installing the twrp
so now what please , how can i to install a new Rom for the my pixel , and there is no operation system i think cause i deleted every thing including the system throw twrp !
thank you in advance
Click to expand...
Click to collapse
I would not keep locking/unlocking the bootloader unless you want to brick your phone.
If you can get to the bootloader, flash-all the latest factory image #4 'Keep data' in this guide: [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by homeboy76
Then look at #11 in the guide.
Homeboy76 said:
I would not keep locking/unlocking the bootloader unless you want to brick your phone.
If you can get to the bootloader, flash-all the latest factory image #4 'Keep data' in this guide: [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by homeboy76
Then look at #11 in the guide.
Click to expand...
Click to collapse
thanks a lot for your reply , yes i can get to the bootloader
i'm downloading now the factory image .thanks again
Bashar Bachir said:
thanks a lot for your reply , yes i can get to the bootloader
but there is no flash-all.bat inside platform-tools folder, from where can i get it please
Click to expand...
Click to collapse
- There is also no 'fastboot' nor 'adb' in your Platform-tools folder.
First, download the latest SDK Platform-tools r28.0.1 from here.
Then read #4 again, pay particular attention to #4B.
Homeboy76 said:
I would not keep locking/unlocking the bootloader unless you want to brick your phone.
If you can get to the bootloader, flash-all the latest factory image #4 'Keep data' in this guide: [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by homeboy76
Then look at #11 in the guide.
Click to expand...
Click to collapse
thanks a lot for your help , i installed the Factory image and unlocked the boot loader then the i could flash the rom finally ,
best regards
Stop locking your bootloader.
Homeboy76 said:
- There is also no 'fastboot' nor 'adb' in your Platform-tools folder.
First, download the latest SDK Platform-tools r28.0.1 from here.
Then read #4 again, pay particular attention to #4B.
Click to expand...
Click to collapse
thanks a lot for your help , the problem has been solved.
i hope all the best for you
best regards
TonikJDK said:
Stop locking your bootloader.
Click to expand...
Click to collapse
thanks a lot for you reply, maybe you mean Stop unlocking
cause the boot loader as you know is by default locked .so i returned it as it was .
thanks again
best regards
Bashar Bachir said:
thanks a lot for you reply, maybe you mean Stop unlocking
cause the boot loader as you know is by default locked .so i returned it as it was .
thanks again
best regards
Click to expand...
Click to collapse
From your first post:
"when i couldn't install the new update i wanted to lock the boot loader again and i locked it by typing fastboot flashing lock and of course the device did't boot up"
You got lucky, you locked it and it bricked. When that happens and you are locked you can often end up on a situation where you can't unlock again.
So I said what I meant, stop locking your bootloader unless you are 100 percent stock and working perfectly.
TonikJDK said:
From your first post:
"when i couldn't install the new update i wanted to lock the boot loader again and i locked it by typing fastboot flashing lock and of course the device did't boot up"
You got lucky, you locked it and it bricked. When that happens and you are locked you can often end up on a situation where you can't unlock again.
So I said what I meant, stop locking your bootloader unless you are 100 percent stock and working perfectly.
Click to expand...
Click to collapse
oh i understand now why you said that , sorry brother ,
i'll keep that in my mind , thanks for all your replays
So, long story short I recently decided to try and root my oneplus7t I unfortunately made some mistakes and somehow corrupted some files. I read elsewhere in the forum that I could download the stock rom which I did and then use flash-all and that would allow me to go back to the factory settings so I could lock the oem and just go back to normal because I was tired of the headache. Unfortunately, after using flash-all I locked the oem thinking everything should be stock and it would work properly. But it says device is corrupt and trying to unlock the oem says oem unlocking is disabled.
So did I just completely brick my phone? I don't know of anyway to fix it at this point :/.
kschmitz4 said:
So, long story short I recently decided to try and root my oneplus7t I unfortunately made some mistakes and somehow corrupted some files. I read elsewhere in the forum that I could download the stock rom which I did and then use flash-all and that would allow me to go back to the factory settings so I could lock the oem and just go back to normal because I was tired of the headache. Unfortunately, after using flash-all I locked the oem thinking everything should be stock and it would work properly. But it says device is corrupt and trying to unlock the oem says oem unlocking is disabled.
So did I just completely brick my phone? I don't know of anyway to fix it at this point :/.
Click to expand...
Click to collapse
Can you still boot into bootloader via the hardware keys, whatever that combo is on the 7t?
Boot to bootloader or recovery and factory reset it or so.
Josh McGrath said:
Can you still boot into bootloader via the hardware keys, whatever that combo is on the 7t?
Boot to bootloader or recovery and factory reset it or so.
Click to expand...
Click to collapse
I can get to the bootloader but it's Device State -locked and when I tell it to boot into recovery it says the device is corrupt. When I use fastboot to oem unlock it says I cannot, and I can't flash when oem is locked either.
kschmitz4 said:
I can get to the bootloader but it's Device State -locked and when I tell it to boot into recovery it says the device is corrupt. When I use fastboot to oem unlock it says I cannot, and I can't flash when oem is locked either.
Click to expand...
Click to collapse
Try
fastboot erase userdata and
Fastboot erase cache
Let me know if that works or not we will move on. Probably won't work since it's bootloader locked
You may have to contact OP and while you're at it, get the MSM tool for us all :good:
It says erase is not allowed in locked state . I think this is probably all she wrote for this one. I think I'm just going to send it back tbh, the whole reason I was trying to root it was because it didn't work with Sprint like they said it would. and I was wondering if I could find a way too make it work with custom software. Thanks for trying
Are you able to flash one of these Fastboot ROMs?
Maybe Sideload can work!
https://support.oneplus.com/app/answers/detail/a_id/4583/kw/7t here is official stock file.
https://forums.oneplus.com/threads/how-to-do-flash-through-adb-sideload.509377/
https://www.the***********.com/sideload-ota-update-stock-recovery-adb/
Please refer above links for your knowledge purpose maybe it can help.....
I unfortunately no longer have Twrp installed as I did a flash-all with a stock rom already . If I try and flash recovery it says "flashing is not alllowed in lock state". Sideloading wasn't functional back when I had twrp either as the functionality for it is still in progress. I'll probably try contacting support one more time and see if I can get a T2 who can unbrick it, otherwise I'm just going to send it back. Thanks for the attempts guys!
Edit: As to the flashboot roms I flash-all'ed one of them and that's how I got into this mess :/.
kschmitz4 said:
I unfortunately no longer have Twrp installed as I did a flash-all with a stock rom already . If I try and flash recovery it says "flashing is not alllowed in lock state". Sideloading wasn't functional back when I had twrp either as the functionality for it is still in progress. I'll probably try contacting support one more time and see if I can get a T2 who can unbrick it, otherwise I'm just going to send it back. Thanks for the attempts guys!
Edit: As to the flashboot roms I flash-all'ed one of them and that's how I got into this mess :/.
Click to expand...
Click to collapse
I ended up needing to flash the fastboot 10.0.3 firmware and was able to do a local upgrade to 10.0.4 that way, then flashing a patched boot.img via fastboot
I can't run any flash commands as my oem is locked. I don't suppose there's anyway around that?
kschmitz4 said:
I can't run any flash commands as my oem is locked. I don't suppose there's anyway around that?
Click to expand...
Click to collapse
How did you flash twrp with it oem locked??That doesnt make sense
I had twrp on it when the oem was unlocked, I was trying to reset the device to stock, so I did a flash-all and then oem locked it. But for some reason the repair was unsuccessful, and now it says my device is corrupted and I forgot to turn on oem unlocking in the settings on my phone after the flash-all before I did the oem-lock.
kschmitz4 said:
I had twrp on it when the oem was unlocked, I was trying to reset the device to stock, so I did a flash-all and then oem locked it. But for some reason the repair was unsuccessful, and now it says my device is corrupted and I forgot to turn on oem unlocking in the settings on my phone after the flash-all before I did the oem-lock.
Click to expand...
Click to collapse
You should have no issues reflashing the stock images
I cannot flash anything. Because my OEM state is locked.
Boot to Stock Recovery ?
Holding for a long time Volume Down + Power Buttons while booting your phone ?
Volume down plus power button takes me to "Your device is corrupt and will not boot"
kschmitz4 said:
Volume down plus power button takes me to "Your device is corrupt and will not boot"
Click to expand...
Click to collapse
Looks like you will need the MSM tool to fix this issue. You'll have to contact OP support and they will remote in your PC, load their software and flash it 100pct back to stock.
Also, disconnect them before they can delete the MSM tool so we can have it here in the community
kschmitz4 said:
Volume down plus power button takes me to "Your device is corrupt and will not boot"
Click to expand...
Click to collapse
Press volume up/down and power, reboot to fastboot. Unlock bootloader again. Install update from settings, reboot and install it again. (local install)
Factory reset in setting, reboot fastboot, lock bootloader. Reboot and untick unlock bootloader in developer settings.
Don't know if it's too late but I believe there's a working MSM tool now
Unable to relock bootloader without receiving message that says "Your device is corru
Hello all, last night I used a flash-all tool to restore my OnePlus 7T from OOS Beta 6 with root back to 10.0.11 without root. After restoring to the stable firmware, I tried relocking my bootloader, upon which I received that message I posted in the title. It doesn't matter if I reset my phone in the recovery or through the settings app, I always get that message if I try to lock the bootloader again. I'm thinking I might have to use the MSM download tool, but I was having no luck with that last night since it would stay continuously stuck on param preload despite being detected by the app. I can use my phone normally again if I unlock the bootloader again, though, so that's what I'm doing in the meantime.
I was able to relock my 7T using fastboot. If you can boot to fastboot? In linux the command was 'fastboot flashing lock'. Not sure in windows if it's the same. Worked for me. Now 'OEM unlocking' option is visible again under system / developer tools. Prior to re-locking it was grayed out, unavailable.
Are you sure with the command? Shouldn't it be "Fastboot oem lock" / "Fastboot oem unlock"? I'm not sure because I never locked my phones again but this makes more sense to me than your commands.
Gesendet von meinem HD1903 mit Tapatalk
Use the msmtoolkit it will lock your bootloader. I think that is the safest way to achieve a locked bootloader
v.konvict said:
Use the msmtoolkit it will lock your bootloader. I think that is the safest way to achieve a locked bootloader
Click to expand...
Click to collapse
I had same issue as OP so I went back to unlocked but I tried locking it through the all in one tool. Haven't attempted to do it through fastboot directly.
That msm toolkit doesn't work on the tmobile version however. Even if you flash to global, I believe the posts in the thread indicate that the model number is off and it won't work.
If there's a way for me to relock the bootloader on global, I'd definitely do it so I could get incremental updates back.
TBHSilentAce07 said:
I had same issue as OP so I went back to unlocked but I tried locking it through the all in one tool. Haven't attempted to do it through fastboot directly.
That msm toolkit doesn't work on the tmobile version however. Even if you flash to global, I believe the posts in the thread indicate that the model number is off and it won't work.
If there's a way for me to relock the bootloader on global, I'd definitely do it so I could get incremental updates back.
Click to expand...
Click to collapse
See my 1st post again. Why using all in one tools you never really know what is going on in the background when all you need are simple commands for the command line?
Just read up a little bit on adb and Fastboot, it is not so hard and the usage is very transparent, trust me. It helps you to better understand the process as well
Btw Fastboot and adb commands are the same on Windows and Linux
xe0r said:
Are you sure with the command? Shouldn't it be "Fastboot oem lock" / "Fastboot oem unlock"? I'm not sure because I never locked my phones again but this makes more sense to me than your commands.
Gesendet von meinem HD1903 mit Tapatalk
Click to expand...
Click to collapse
Don't forget, I'm on debian linux. The command syntex for ADB has to be different than the windows ADB.
---------- Post added at 11:04 PM ---------- Previous post was at 11:02 PM ----------
jones_b said:
Don't forget, I'm on debian linux. The command syntex for ADB has to be different than the windows ADB.
Click to expand...
Click to collapse
I was trying to do this with the sdk tools on a windows laptop but I never could get the USB driver to show up correctly
under device manager.
---------- Post added at 11:13 PM ---------- Previous post was at 11:04 PM ----------
xe0r said:
Are you sure with the command? Shouldn't it be "Fastboot oem lock" / "Fastboot oem unlock"? I'm not sure because I never locked my phones again but this makes more sense to me than your commands.
Gesendet von meinem HD1903 mit Tapatalk
Click to expand...
Click to collapse
Here's a snippet out of the man pages for 'fastboot' on my debian box (fastboot version 1:7.0.0+r33-1 )
the bottom two entries -
--------------------------------------------------------
COMMANDS
fastboot update filename
Reflash device from update.zip.
fastboot flashall
Flash boot, system, vendor, and (if found) recovery.
fastboot flash partition [filename]
Write a file to a flash partition.
fastboot flashing lock
Locks the device. Prevents flashing.
fastboot flashing unlock
Unlocks the device. Allows flashing any partition except bootloader-re‐
lated partitions.
------------------------------------------------------------------
fastboot flashing lock worked for me, locked and under developer tools it gave me back "OEM Locking" option.
I thought windows was something like 'fastboot OEM lock' but I'm not sure since I didn't get there.
I'm a total newb if it ain't already obvious. lol
---------- Post added at 11:17 PM ---------- Previous post was at 11:13 PM ----------
jones_b said:
Don't forget, I'm on debian linux. The command syntex for ADB has to be different than the windows ADB.
---------- Post added at 11:04 PM ---------- Previous post was at 11:02 PM ----------
I was trying to do this with the sdk tools on a windows laptop but I never could get the USB driver to show up correctly
under device manager.
---------- Post added at 11:13 PM ---------- Previous post was at 11:04 PM ----------
Here's a snippet out of the man pages for 'fastboot' on my debian box (fastboot version 1:7.0.0+r33-1 )
the bottom two entries -
--------------------------------------------------------
COMMANDS
fastboot update filename
Reflash device from update.zip.
fastboot flashall
Flash boot, system, vendor, and (if found) recovery.
fastboot flash partition [filename]
Write a file to a flash partition.
fastboot flashing lock
Locks the device. Prevents flashing.
fastboot flashing unlock
Unlocks the device. Allows flashing any partition except bootloader-re‐
lated partitions.
------------------------------------------------------------------
fastboot flashing lock worked for me, locked and under developer tools it gave me back "OEM Locking" option.
I thought windows was something like 'fastboot OEM lock' but I'm not sure since I didn't get there.
I'm a total newb if it ain't already obvious. lol
Click to expand...
Click to collapse
Being that this is Debian 9, maybe my fastboot is an old version as well. ADB and fastboot both seem to work pretty good though. No stinkin' USB driver issues like with Windows 10.
SenyorMauricio said:
Hello all, last night I used a flash-all tool to restore my OnePlus 7T from OOS Beta 6 with root back to 10.0.11 without root. After restoring to the stable firmware, I tried relocking my bootloader, upon which I received that message I posted in the title. It doesn't matter if I reset my phone in the recovery or through the settings app, I always get that message if I try to lock the bootloader again. I'm thinking I might have to use the MSM download tool, but I was having no luck with that last night since it would stay continuously stuck on param preload despite being detected by the app. I can use my phone normally again if I unlock the bootloader again, though, so that's what I'm doing in the meantime.
Click to expand...
Click to collapse
xe0r said:
See my 1st post again. Why using all in one tools you never really know what is going on in the background when all you need are simple commands for the command line?
Just read up a little bit on adb and Fastboot, it is not so hard and the usage is very transparent, trust me. It helps you to better understand the process as well
Btw Fastboot and adb commands are the same on Windows and Linux
Click to expand...
Click to collapse
Hey, all. Figured out why I couldn't relock the bootloader despite everything being stock and unrooted.
Since I was using fastboot to flash a stock image, I needed to flash any image that wasn't the newest version and let the phone boot and install an update from OnePlus to bring it up to latest and THEN lock the bootloader.
So yeah. Use fastboot to install 10.0.09 then boot the phone and download the system update to 10.0.11 through the standard update tab in settings (skip whatever set up you can when it boots) and let it do that update. Then, once that's installed direct from OnePlus rather than via a fastboot image, then you can go ahead and relock and it won't give you the corrupt error.
SilentAce07 said:
Hey, all. Figured out why I couldn't relock the bootloader despite everything being stock and unrooted.
Since I was using fastboot to flash a stock image, I needed to flash any image that wasn't the newest version and let the phone boot and install an update from OnePlus to bring it up to latest and THEN lock the bootloader.
So yeah. Use fastboot to install 10.0.09 then boot the phone and download the system update to 10.0.11 through the standard update tab in settings (skip whatever set up you can when it boots) and let it do that update. Then, once that's installed direct from OnePlus rather than via a fastboot image, then you can go ahead and relock and it won't give you the corrupt error.
Click to expand...
Click to collapse
Thanks. Confirmed this works. Needed to install an older version (went with 10.0.8 global), then skipped through most of the setup minus wifi, did a system update to 10.0.12, reboot to bootloader, fastboot oem lock, and no more corruption errors.
SilentAce07 said:
Hey, all. Figured out why I couldn't relock the bootloader despite everything being stock and unrooted.
Since I was using fastboot to flash a stock image, I needed to flash any image that wasn't the newest version and let the phone boot and install an update from OnePlus to bring it up to latest and THEN lock the bootloader.
So yeah. Use fastboot to install 10.0.09 then boot the phone and download the system update to 10.0.11 through the standard update tab in settings (skip whatever set up you can when it boots) and let it do that update. Then, once that's installed direct from OnePlus rather than via a fastboot image, then you can go ahead and relock and it won't give you the corrupt error.
Click to expand...
Click to collapse
So to be clear, can a T-Mobile converted to Global be bootloader re-locked the same way without getting the corrupt phone boot refusal screen? The wife's phone refuses to lock, but haven't tried the update from OnePlus method above?
YES.