Hi guys,
Please help me out, is there any way I can recover from soft brick if I have a locked bootloader and usb debugging is turned off?
Can you get into fastboot and then factory recovery? If you can get there I believe you should be able to do a reset.
timothy009 said:
Hi guys,
Please help me out, is there any way I can recover from soft brick if I have a locked bootloader and usb debugging is turned off?
Click to expand...
Click to collapse
Try booting into recovery and then from your PC sideload the latest ota zip file.
Sent from my [device_name] using XDA-Developers Legacy app
Shouldn't it be necessary to have enabled USB debugging before?
timothy009 said:
Shouldn't it be necessary to have enabled USB debugging before?
Click to expand...
Click to collapse
No. Not while in recovery mode using the "update by adb" option.
This is the stock recovery we are talking about, right?
timothy009 said:
This is the stock recovery we are talking about, right?
Click to expand...
Click to collapse
Yes
Sent from my [device_name] using XDA-Developers Legacy app
Please help me. I have pixel 3 xl joining Q beta. When the setting is pressed, the device does not work. hang like picture. My device has not been unlocked when participating in the test.
spotmark said:
Can you get into fastboot and then factory recovery? If you can get there I believe you should be able to do a reset.
Click to expand...
Click to collapse
Currently the 3xl pixel is hanging so I can't unlock the bootloader pixel to flash the original rom.
nguyenmanh287 said:
Currently the 3xl pixel is hanging so I can't unlock the bootloader pixel to flash the original rom.
Click to expand...
Click to collapse
Google "rescue ota". You use a full OTA from the Google image page and from the stock recovery using the "apply update by adb" option to send the ota from your pc to the phone. Does not require an unlocked bootloader. Does require the latest adb/fastboot binaries on your pc. Directions are right there on Google's ota download page. Best of luck! :good:
v12xke said:
Google "rescue ota". You use a full OTA from the Google image page and from the stock recovery using the "apply update by adb" option to send the ota from your pc to the phone. Does not require an unlocked bootloader. Does require the latest adb/fastboot binaries on your pc. Directions are right there on Google's ota download page. Best of luck! :good:
Click to expand...
Click to collapse
Currently my 3xl pixels are dying. it has not been unlocked yet, so I cannot adb the original google rom
nguyenmanh287 said:
Currently my 3xl pixels are dying. it has not been unlocked yet, so I cannot adb the original google rom
Click to expand...
Click to collapse
I understand your first language is not English and I am trying to help you. Please try to parse/translate the information. You do NOT need an unlocked bootloader or USB debugging to use the ADB option in stock recovery mode using the full OTA image. In too many other threads you have never stated YES, I have a working stock recovery. If you have that, follow the instructions. Yes, you can flash a full OTA image in an attempt to rescue your P3XL even though your bootloader is locked. Otherwise please state you DO NOT have access to a stock recovery instead of cross posting to at least a half dozen threads "help me"! Too many posts from you and never enough information to help you.
Thank you very much. I will ask someone who speaks English to describe the whole situation so you know my PIXEL 3XL status.
---------- Post added at 02:35 AM ---------- Previous post was at 02:34 AM ----------
v12xke said:
I understand your first language is not English and I am trying to help you. Please try to parse/translate the information. You do NOT need an unlocked bootloader or USB debugging to use the ADB option in stock recovery mode using the full OTA image. In too many other threads you have never stated YES, I have a working stock recovery. If you have that, follow the instructions. Yes, you can flash a full OTA image in an attempt to rescue your P3XL even though your bootloader is locked. Otherwise please state you DO NOT have access to a stock recovery instead of cross posting to at least a half dozen threads "help me"! Too many posts from you and never enough information to help you.
Click to expand...
Click to collapse
Thank you very much. I will ask someone who speaks English to describe the whole situation so you know my PIXEL 3XL status.
v12xke said:
Google "rescue ota". You use a full OTA from the Google image page and from the stock recovery using the "apply update by adb" option to send the ota from your pc to the phone. Does not require an unlocked bootloader. Does require the latest adb/fastboot binaries on your pc. Directions are right there on Google's ota download page. Best of luck! :good:
Click to expand...
Click to collapse
Can you guide me specifically? did you tell facebook friends then i send pictures to you? help me?
This is my Facebook
https://www.facebook.com/NGUYENMANH287
nguyenmanh287 said:
Can you guide me specifically? did you tell facebook friends then i send pictures to you? help me?
This is my Facebook
https://www.facebook.com/NGUYENMANH287
Click to expand...
Click to collapse
The post you quoted, has the link to the OTA download page which contains the best instructions available. You can run that page through an online translator if necessary.
You have gotten the help you asked for. Now it's time for you to help yourself. You can take your device to someone more knowledgeable, who is in your area if you feel you can not follow the instructions on Google's page, but there is no further instruction that can be given here that will make this any easier for you.
v12xke said:
Google "rescue ota". You use a full OTA from the Google image page and from the stock recovery using the "apply update by adb" option to send the ota from your pc to the phone. Does not require an unlocked bootloader. Does require the latest adb/fastboot binaries on your pc. Directions are right there on Google's ota download page. Best of luck! :good:
Click to expand...
Click to collapse
v12xke said:
Google "rescue ota". You use a full OTA from the Google image page and from the stock recovery using the "apply update by adb" option to send the ota from your pc to the phone. Does not require an unlocked bootloader. Does require the latest adb/fastboot binaries on your pc. Directions are right there on Google's ota download page. Best of luck! :good:
Click to expand...
Click to collapse
I have the same issue described. My bootloop started with September Android 10 update. I already sideloaded October ota from Google website, and it updated without any problem. Still bootloop. I'm on a pixel 3xl 100% stock bootloader locked no root
movilserver said:
I have the same issue described. My bootloop started with September Android 10 update. I already sideloaded October ota from Google website, and it updated without any problem. Still bootloop. I'm on a pixel 3xl 100% stock bootloader locked no root
Click to expand...
Click to collapse
Not sure why you used the October image, but with a locked bootloader your only option is the rescue OTA. You could try a factory reset from recovery. If that doesn't (or did not) work, then try the December OTA image. Make sure you are using the correct image for your phone (there may be more than one choice). If this fails you should contact Google support, or if you bought it elsewhere, contact them for any warranty you might have.
Make sure to wipe cache
v12xke said:
Not sure why you used the October image, but with a locked bootloader your only option is the rescue OTA. You could try a factory reset from recovery. If that doesn't (or did not) work, then try the December OTA image. Make sure you are using the correct image for your phone (there may be more than one choice). If this fails you should contact Google support, or if you bought it elsewhere, contact them for any warranty you might have.
Click to expand...
Click to collapse
Already tried December. Same thing. I live in Cuba. No warranty or anything. The phone was a gift, and it worked with pie without any issues
---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------
ktmom said:
Make sure to wipe cache
Click to expand...
Click to collapse
I don't have that option in recovery. Any way I've wiped data several times, I think that should wipe cache also
movilserver said:
Already tried December. Same thing. I live in Cuba. No warranty or anything. The phone was a gift, and it worked with pie without any issues
---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------
I don't have that option in recovery. Any way I've wiped data several times, I think that should wipe cache also
Click to expand...
Click to collapse
If you have done a FDR from recovery, and sideloaded a couple of valid OTA's, sorry to say I think you're pretty much done. It's too bad the bootloader is locked, as you would have more tools to work with. What is your bootloader version? 10 or Pie? If still Pie you might get lucky sideloading the correct Pie OTA that exactly matches your bootloader, and get back into System. Once up and running you could look into unlocking it if that is an option. If not wait for a 10 update to come down vs. sideloading. Nothing to lose at this point. Hang in there.
Related
I just recently upgraded from lollipop to marshmallow and I have never encountered this before. I've always been able to log in. I am trying to use the account that was last used but it still tells me "This device was reset. To continue, sign in with a Google Account that was previously used on this device". I dont know what to do.
Although questions could be asked whether it is actually your device or not.. Factory reset is the only way around it.
Sent from my HTC One M9 using Tapatalk
shivadow said:
Although questions could be asked whether it is actually your device or not.. Factory reset is the only way around it.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Is that doing an RUU? Or just go back to Android KitKat? I am using the exact same log in for my Google account when it tells me to enter it. I enter it and nothing happens. I know for a fact it was the log in credentials. I have never had my cell number attached to my username account either. So I dont know if I will ever be able to use my phone again.
Access recovery and wipe data + cache.
Sent from my HTC One M9 using Tapatalk
shivadow said:
Access recovery and wipe data + cache.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Yeah I do that every time I install a new ROM. Everything was deleted off the device as usual and it still doesn't let me sign into my Google account. I have also just found an original TWRP backup of my stock ATT. Would I have to downgrade my firmware to be at kitkat for it to start up properly? How would I figure out what firmware the backup was using?
By the way this is my phone. The old official att backup I made worked flawlessly. I just dont understand why it wont work in Marshmallow...
Can you log in to your Gmail account via a pc without issues?
Sent from my HTC One M9 using Tapatalk
shivadow said:
Can you log in to your Gmail account via a pc without issues?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Yes. I just added my phone number to my Google account using my M9 from the ATT backup and linked it to my phone. I never had my number linked yet. Im thinking this is what will work. Just flashed the 14.0 version for right now to see if this will work. Just waiting till the apps optimize right now.
Im so close now. I had Google send me a text message to my phone but I cant read it since its on the setup screen. How would I look at the text message?
It says "Google will send a one-time message to confirm that (number here) is yours." Then I press the Verify button and i hear and get the text but I cant read it. It says it does it automatically. Then it says to pick an account and I did then it takes me right back to the WIFI selection...
Im going back to ATT backup to add the rest of my accounts to see if picking a different one works.
Nothing is working. It just kicks me back to the WIFI selection screen. Even after it sends the text message to make sure its the right number. I know its the correct account used. When I reflash the ATT original I see the recent apps I just downloaded a few days ago.
Can someone please help me? I'm not understanding whats going on...
FRP
There are some easy instructions how to bypass in samsung devices using usb otg but not applicable HTC. This instruction shows how to erase FRP partition using adb commands but your ROM must have Persistent ADB Enabled. If you have locked BL and OEM unlocking is disabled in Dev option, you have no other option but to retrieve your password or use XTC2Clip. It can s-off your device and remove FRP.
side_flip15 said:
FRP
There are some easy instructions how to bypass in samsung devices using usb otg but not applicable HTC = This instruction shows how to erase FRP partition using adb commands but your ROM must have Persistent ADB Enabled. If you have locked BL and OEM unlocking is disabled in Dev option, you have no other option but to retrieve your password or use XTC2Clip. It can s-off your device and remove FRP.
Click to expand...
Click to collapse
I am s-off'd and Super CID and bootloader unlocked.
Try this command via fastboot: fastboot erase frp
---------- Post added at 06:32 AM ---------- Previous post was at 06:30 AM ----------
Just noticed that on your sig
you can try this command in fastboot : fastboot erase frp
side_flip15 said:
Try this command via fastboot: fastboot erase frp
---------- Post added at 06:32 AM ---------- Previous post was at 06:30 AM ----------
Just noticed that on your sig
you can try this command in fastboot : fastboot erase frp
Click to expand...
Click to collapse
CMD output said OK
Now do I flash a ROM then the fw?
Boot to android and check if it still ask for previous google account.
side_flip15 said:
Boot to android and check if it still ask for previous google account.
Click to expand...
Click to collapse
I'm on my ATT backup at the moment so I can actually use my phone. Im at Android Version 5.0.2 Software Number 1.32.502.31 and Build Number is 1.32.401.17
How are you updating? via RUU? OTA? Custom Rom? Anyway, perform your update and check if the problem still persist.
side_flip15 said:
How are you updating? via RUU? OTA? Custom Rom? Anyway, perform your update and check if the problem still persist.
Click to expand...
Click to collapse
Custom ROM. Waiting for optimizing apps. Is that frp command used only that once or everytime you upgrade ROM's or FW?
Flash firmware (if you're not on MM firmware yet). flash latest TWRP. Flash Rom.zip
side_flip15 said:
Flash firmware (if you're not on MM firmware yet). flash latest TWRP. Flash Rom.zip
Click to expand...
Click to collapse
Flash FW in RUU Mode or Download mode?
Unoath said:
Flash FW in RUU Mode or Download mode?
Click to expand...
Click to collapse
I flash in download mode
erase FRP only if you're stuck on set-up asking for previous google account.
side_flip15 said:
I flash in download mode
erase FRP only if you're stuck on set-up asking for previous google account.
Click to expand...
Click to collapse
Alright. Im installing ROM now with Marshmallow
I can get the bootloader menu to come up but it says its locked and its a Verizon version. I've done a bunch of reading. My last resort is to file for lost but if there is a way to get it working again. I will donate to Chainfire or whoever.
Why would you u unlock then lock,??? If your phone is still operational just relock your bootloader.
just use depixel8 to unlock again and then use the firmware from googles website to flash everything back which will fix whatever else you messed up
---------- Post added at 12:52 AM ---------- Previous post was at 12:51 AM ----------
use the version for Marlin that ends in P... and unlocking isn't necessary to do flash this but I figured you want unlock which is the only reason why I said to do depixel8 again
I used Chainfires method of Unlocking and then I unrooted the phone. I was tyring to play pokemon lol with my girl so I just locked the bootloader thinking it would factory reset my root automatically now it boots straight to charging weird. But aslong as I can still see the settings screen where you can START , Recovery and all that their is still a way right? I do half understand what you guys say because I used to write software in Visual Basic. Its just I haven't really dabbled into the Android / Linux stuff much.
In the bootloader(fastboot mode), while being connected to your PC, try typing fastboot format userdata and then fastboot format cache. This will wipe your device and maybe boot up. You can't flash anything now with a locked bootloader.
Sent from my Pixel XL using XDA-Developers mobile app
KrazyBrandon said:
I can get the bootloader menu to come up but it says its locked and its a Verizon version. I've done a bunch of reading. My last resort is to file for lost but if there is a way to get it working again. I will donate to Chainfire or whoever.
Click to expand...
Click to collapse
What do you mean "My last resort is to file for lost"?
I'm hoping you're not intending to commit fraud because you screwed up you're phone. Apologies if I'm misreading your statement.
@KrazyBrandon, Benjamin150 may be able to help you. I sent him a pm so be on the lookout for his advice.
Sent from my Pixel XL using XDA-Developers mobile app
Roger that I look forward to trying. I really enjoy the phone.
none of these advices are correct... unlock using depixel8 again which might fix the issue on its own if not just go to https://developers.google.com/android/images click accept and download the image for Marlin that ends in a P and extract it place your adb and fastboot binaries inside the folder that was made by extracting.... then go to the android bootloader mode hook up to computer and do fastboot flash-all.bat this will factory reset your device but you will be completely back to stock
Mike02z said:
What do you mean "My last resort is to file for lost"?
I'm hoping you're not intending to commit fraud because you screwed up you're phone. Apologies if I'm misreading your statement.
Click to expand...
Click to collapse
this is exactly what I was thinking and a reason why we pay so much for insurance and coverages. just a disgrace to read that comment. I've reported this post.
diabl0w said:
none of these advices are correct... unlock using depixel8 again which might fix the issue on its own if not just go to https://developers.google.com/android/images click accept and download the image for Marlin that ends in a P and extract it place your adb and fastboot binaries inside the folder that was made by extracting.... then go to the android bootloader mode hook up to computer and do fastboot flash-all.bat this will factory reset your device but you will be completely back to stock
Click to expand...
Click to collapse
He locked his bootloader. You can't flash IMG files with a locked bootloader.
Sent from my Pixel XL using XDA-Developers mobile app
ko0ky said:
this is exactly what I was thinking and a reason why we pay so much for insurance and coverages. just a disgrace to read that comment. I've reported this post.
Click to expand...
Click to collapse
No need for all that. I'm sure you've done some questionable things in your life. Seriously?
Moderator Warning,
I am closing this thread down, as we do not discuss insurance fraud on this site.
Hello, my brother have a nexus 5x and one day after a night his phone stop working, it could only enter to download mode, now sometimes it cant even get there, what can i do, its been like 2 weeks since that
Could be the solder issue, there's loads of posts and thread about that. If it is and you're out of warranty, you're also sol. Sorry
Sent from my Nexus 5X using Tapatalk
berndblb said:
Could be the solder issue, there's loads of posts and thread about that. If it is and you're out of warranty, you're also sol. Sorry
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I looked into that, but is it normal that the phone go to a bootloader, then to download mode and after that get stuck in the google animation?
No, it's not normal. But if that is consistent it's probably software and fixable. Try the lgup tool to flash the firmware and/or flash the latest OTA in adb.
See if you can get into recovery from the bootloader.
If you can, flash the full OTA from the Google website in adb. You need neither an unlocked bootloader nor USB debugging enabled for it. Just as long as you use the official Google software.
If you do not have adb in recovery, use the lgup tool. For me it did not fully reflash the phone, something always failed, but it gave me adb in recovery when I did not have it before. Saved my bacon...
If neither helps or applies I'm fresh out of ideas, sorry.
I'll look for the thread I found helpful and add the link later.
Here you go, loads of good leads in this thread
https://forum.xda-developers.com/showthread.php?p=71588229
berndblb said:
No, it's not normal. But if that is consistent it's probably software and fixable. Try the lgup tool to flash the firmware and/or flash the latest OTA in adb.
See if you can get into recovery from the bootloader.
If you can, flash the full OTA from the Google website in adb. You need neither an unlocked bootloader nor USB debugging enabled for it. Just as long as you use the official Google software.
If you do not have adb in recovery, use the lgup tool. For me it did not fully reflash the phone, something always failed, but it gave me adb in recovery when I did not have it before. Saved my bacon...
If neither helps or applies I'm fresh out of ideas, sorry.
I'll look for the thread I found helpful and add the link later.
Here you go, loads of good leads in this thread
https://forum.xda-developers.com/showthread.php?p=71588229
Click to expand...
Click to collapse
Thank you sooo much, i will try this and the ill tell you how it end up:good:
my nexus is giving me the Firmware Update screen "dont unplug usb until after firmware completes". i looked this up and ran the LGUP following the instructions for it, but it always freezes at 46% progress in the application and 49% on the phone. tried going into the bootloader and throwing it into recovery mode, but it just goes straight back into the Firmware Update screen. bootloader is locked (Device State: locked) and secure boot is enabled. tried to unlock through NRToolkit but it always throws me back into the Firmware update screen with a "waiting for device" window whenever i try any of the options. apparently its recognized as a fastboot device through ADB, but i still cant flash anything on it cause its locked
heeeeeeeeelp, i wanna get this thing running again
@joeinfro: try a fresh installation as listed here
rp158 said:
@joeinfro: try a fresh installation as listed here
Click to expand...
Click to collapse
is that possible to do with a locked bootloader and/or usb debugging not enabled?
Of course, it's the factory way.
rp158 said:
Of course, it's the factory way.
Click to expand...
Click to collapse
That link is to a slim Rom. The OP is not going to be able to flash that. He's also not going to be able to flash the factory image with a locked bootloader.
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 11:15 AM ---------- Previous post was at 11:06 AM ----------
OP, were you using the LGUP tool to upgrade the firmware?
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
That link is to a slim Rom. The OP is not going to be able to flash that. He's also not going to be able to flash the factory image with a locked bootloader.
---------- Post added at 11:15 AM ---------- Previous post was at 11:06 AM ----------
[/COLOR]OP, were you using the LGUP tool to upgrade the firmware?
Click to expand...
Click to collapse
yes, i tried to use the LGUP to get around a frp , then it got stuck at 46%
joeinfro said:
yes, i tried to use the LGUP to get around a frp , then it got stuck at 46%
Click to expand...
Click to collapse
I've never used that tool so won't be much help. I did just try to install it but didn't get it completely set up. And I don't really want to try it on my 5x. Getting into the bootloader and recovery doesn't work?
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I've never used that tool so won't be much help. I did just try to install it but didn't get it completely set up. And I don't really want to try it on my 5x. Getting into the bootloader and recovery doesn't work?
Click to expand...
Click to collapse
i can get it into bootloader but it says Device: Locked and Secure Boot: Enabled, which i'm assuming means the bootloader is locked. i cant get it into recovery from the bootloader as it throws me straight back into the firmware update screen
joeinfro said:
i can get it into bootloader but it says Device: Locked and Secure Boot: Enabled, which i'm assuming means the bootloader is locked. i cant get it into recovery from the bootloader as it throws me straight back into the firmware update screen
Click to expand...
Click to collapse
I don't know what to tell you other than hope someone who has used that tool sees this thread. May I ask why you tried the tool in the first place?
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I don't know what to tell you other than hope someone who has used that tool sees this thread. May I ask why you tried the tool in the first place?
Click to expand...
Click to collapse
yep! i got the phone while it was locked by FRP and the seller did not have the login credentials of the last google account. i'm starting to understand why the price for it was so low haha
i followed a guide that recommended using the LGUP app and i gave that a shot, except i believe this phone is well and truly bricked to oblivion
i'm no stranger to messing around with fastboot/adb, and i thought i'd be able to work my way around this but its starting to seem a little out of my hands
Hello Guys,
First sry for my bad English im from Germany
Today i have downgraded my Google Pixel 2 XL 8.1 (DEZ. PATCH) to 8.0 (SEP. PATCH)
I know this isnt possible but i do it.
Here is what i do:
First i search here in the Forums a fix for the multitouch Bug since 8.1, i try all methods but nothing have work for me...
So i try to downgrade my Pixel 2 xl from 8.1 to 8.0 with the official Factory Image Files from Google but it isnt work for me because my Phone say (after i try the OTA Update via sideload) that i have already an newer Version of Android installed.
So what to do?
I Install the latest Factory Image from Google (8.1 Jan.Patch)
After the Install i stoped the First Start of my Phone and Go Back to bootloader, than i try to Lock my bootloader via ADB. After the Lock i See an Message in my Phone Like "there is noch System installed on your device, device cant Start" Or something Like that.
Now i Boot Back to bootloader and unlock my Phone again but that error stay there and my Phone will not Boot.
I think OK there noch System installed on my Phone now and maybe i can flash the factory Image from the Google Developer Site.
I downloaded the First Image File "8.0.0 (OPD1.170816.010, Sep. 2017)
Booted my Phone to bootloader and run the Script "flash-all.bat"
The installation finished without any errors and my Phone booted without any Problems.
I think "OK cant be" but i Go to settings and Check the Android Version i have installed, and i See im Back to Android 8.0.0
Ok
blaze9090 said:
Ok
Click to expand...
Click to collapse
I have a Question:
After the downgrade to 8.0 i checked the System Update in the settings, but it says that im on the latest Version of Android
Any Fix for that?
Flash latest factory images...
imex1 said:
... I think "OK cant be" but i Go to settings and Check the Android Version i have installed, and i See im Back to Android 8.0.0
Click to expand...
Click to collapse
What a very long post for nothing. Go to the Google developer website, download the latest full January build and flash it with the script according to the instructions given on the same page. Then drink a beer. Prost. :good:
alia5 said:
Flash latest factory images...
Click to expand...
Click to collapse
I dont wanna Go to 8.1 yet because of the Multitouch Bug in Games, waiting for an official fix by Google
I try to Upgrade Googles OTA Image via sideloade after the fix, Thanksgiving you
v12xke said:
What a very long post for nothing. Go to the Google developer website, download the latest full January build and flash it with the script according to the instructions given on the same page. Then drink a beer. Prost. :good:
Click to expand...
Click to collapse
Ehm thanks for the Info but i Post my way to DOWNGRADE from 8.1 to 8.0, because its NOT official possible...
But thx
imex1 said:
Ehm thanks for the Info but i Post my way to DOWNGRADE from 8.1 to 8.0, because its NOT official possible...
But thx
Click to expand...
Click to collapse
FFS, my grandmother can downgrade from 8.1 to 8.0, mate. Was this supposed to be a tutorial? haha! Again, drink another beer. Prost. :good:
v12xke said:
FFS, my grandmother can downgrade from 8.1 to 8.0, mate. Was this supposed to be a tutorial? haha! Again, drink another beer. Prost. :good:
Click to expand...
Click to collapse
Ah okay, thx for the Info, all i knew ist that its NOT possible to downgrade from 8.1 to 8.0
But seems im wrong, but hey thx to know
Now i can deleat my Post, thx Guys for Help.. good Community in XDA! Cheers
No worries mate! Ayinger Oktober Fest-Märzen | Privatbrauerei. Prost. My favorite. Still have one full case / 20 L. In Texas!
v12xke said:
FFS, my grandmother can downgrade from 8.1 to 8.0, mate. Was this supposed to be a tutorial? haha! Again, drink another beer. Prost. :good:
Click to expand...
Click to collapse
So, tell us how you're supposed to downgrade from 8.1 to 8.0? Especially since Google added safeguards to prevent this. Maybe I'm missing something, but to my knowledge it's not 'supposed' to be possible.
stumpy352 said:
So, tell us how you're supposed to downgrade from 8.1 to 8.0? Especially since Google added safeguards to prevent this. Maybe I'm missing something, but to my knowledge it's not 'supposed' to be possible.
Click to expand...
Click to collapse
Unlock bootloader, unlock critical, flash 8.0 image
TheSt33v said:
Unlock bootloader, unlock critical, flash 8.0 image
Click to expand...
Click to collapse
Is that all that's needed? Unlocking the critical partition?
Does that circumvent Google's anti roll back?
stumpy352 said:
Is that all that's needed? Unlocking the critical partition?
Does that circumvent Google's anti roll back?
Click to expand...
Click to collapse
Yes. I don't know the details of Google's anti rollback measures, but I don't think they were meant to apply to unlocked bootloaders. Google allows bootloader unlock to be friendly to developers who probably want to test their apps on different firmware versions. What would be the point of locking them out of various firmwares? In fact, what's the point of an unlockable bootloader at all if you're going to still put restrictions on flashing?
The reason why the OP thought he needed to find out a clever downgrade method was because he was trying to use an OTA to downgrade. OTAs never allow downgrading, and I don't think they ever have. This is nothing new. The factory images, however, will always work as long as both "fastboot flashing unlock" and "fastboot flashing unlock_critical" have been performed beforehand with the latest version of fastboot.
TheSt33v said:
Yes. I don't know the details of Google's anti rollback measures, but I don't think they were meant to apply to unlocked bootloaders. Google allows bootloader unlock to be friendly to developers who probably want to test their apps on different firmware versions. What would be the point of locking them out of various firmwares? In fact, what's the point of an unlockable bootloader at all if you're going to still put restrictions on flashing?
The reason why the OP thought he needed to find out a clever downgrade method was because he was trying to use an OTA to downgrade. OTAs never allow downgrading, and I don't think they ever have. This is nothing new. The factory images, however, will always work as long as both "fastboot flashing unlock" and "fastboot flashing unlock_critical" have been performed beforehand with the latest version of fastboot.
Click to expand...
Click to collapse
The only reason why i open this thread is, that after i try to downgrade to 8.0 my devise go to bootloop, after i flash back to 8.1 it works fine...so with my post i downgraded to 8.0 and its still work fine, im now on 8.0 with nov patch, the only reason why i downgrade is the stupid Multitouch Bug in games, so im waiting for official fix by google