Android 11 beta1 update error
flash google pixel 2 factory images
pixel2 reboot ,error slot unbootable load error
Flashing process is different
send system_b 1/1
what's happen?
{
"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"
}
hww44 said:
Android 11 beta1 update error
flash google pixel 2 factory images
pixel2 reboot ,error slot unbootable load error
Flashing process is different
send system_b 1/1
what's happen?
Click to expand...
Click to collapse
I got the same error, unable to solve it.
jwchen119 said:
I got the same error, unable to solve it.
Click to expand...
Click to collapse
what version of adb tools are you using
andy hall said:
what version of adb tools are you using
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.41
Version 30.0.2-6538114
hww44 said:
Android Debug Bridge version 1.0.41
Version 30.0.2-6538114
Click to expand...
Click to collapse
The 11 Beta only refers to the Android Flash Tool I cannot find any instructions for using ADB and Fastboot, are you using that tool if not then try that
Or going back to a factory image using normal fasboot and then using the flashtool.
Unusually it also says you need to enable oem unlock as well as usb debugging in developer options before starting.
Other than that, I have run out of ideas as it is 11 beta.
This is where I started https://developer.android.com/preview/download loads of info nothing like the usual flash instructions.
andy hall said:
The 11 Beta only refers to the Android Flash Tool I cannot find any instructions for using ADB and Fastboot, are you using that tool if not then try that
Or going back to a factory image using normal fasboot and then using the flashtool.
Unusually it also says you need to enable oem unlock as well as usb debugging in developer options before starting.
Other than that, I have run out of ideas as it is 11 beta.
Click to expand...
Click to collapse
Thank you.
I will non restore the factory image because the data is important.
I found the same problem with DP4 and BETA1.
Why did not use OTA ?
theasters said:
Why did not use OTA ?
Click to expand...
Click to collapse
Already rooted.
i got the same problem here and i'm unable to solve it , the Pixel 2 is the most forgetten phone i got .
no support here on xda and nothing cool , Kernels and roms are bs
i used to have Hammerhead , bullhead , C'mon even OnePlusOne aka Bacon is still up with new things updated it's a phone from 2014 or something
Related
Well i downloaded the new developer preview for m
and tried to flash the usual way
Then i encountred this error
{
"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"
}
tried running cmd in admin mode too, no effect.
The method i used is as follows
I extract the zip in the folder to get access to the images inside and then flashed them manually.
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system sysytem.img (did not work)
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
Running Fastboot and adb v 1.4 from here
http://forum.xda-developers.com/showthread.php?t=2588979
Kindy someone assist thank you
Your image doesn't show
Sent from my Android M Nexus 5 yo!
Try to reboot to your bootloader, and then flash system.img.
Schoat333 said:
Try to reboot to your bootloader, and then flash system.img.
Click to expand...
Click to collapse
i try this and still get the error
Schoat333 said:
Try to reboot to your bootloader, and then flash system.img.
Click to expand...
Click to collapse
I tired that.
I actually even tried restarting the bootloader after flashing every component.
Seems this fastboot has some issues with android m.
Can anyone who has flashed it provide some input.
Sent from my A0001 using XDA Free mobile app
I had the same problem. Not just with android M, other Google OEM Roms. I was only able to get it to work by doing it on my Mac. I would think that Linux would have no problem either.
I had no issues flashing M through fastboot - even used flash-all.sh.
I couldn't get M to boot until I individually erased each part using fastboot, and then individually flashed each part, extracted from Google's zip, also using fastboot.
lnchbx said:
I had the same problem. Not just with android M, other Google OEM Roms. I was only able to get it to work by doing it on my Mac. I would think that Linux would have no problem either.
Click to expand...
Click to collapse
I can't get it to work on my Mac! I keep getting the data length too large error when trying to flash system.mg. Everywhere I've looked has said update the sdk, but I'm on the latest version.
theChief_ said:
I can't get it to work on my Mac! I keep getting the data length too large error when trying to flash system.mg. Everywhere I've looked has said update the sdk, but I'm on the latest version.
Click to expand...
Click to collapse
You need to pass the '-s' argument to fastboot to be able to flash system.
Redownload the file could be corrupt. Only other thing try using mfastboot(google it)
Hello everybody
Well, I have his issue. I tried to flash some new roms into the OPO yesterday and I had some issues with one, so I decided to flash other one, but when I wiped the things I also wiped the internal storage and I didnt know that that would erase my OS, now i'm trying to flash a rom but it wont let me with the bootloader because it says its locked, and if i try to unlock it using OPO toolking via ADB sideload the phone shows it requires ADB 1.0.32 which is the same that i have installed on my computer and if I try it using the bootloader option it just restarts and it keeps being locked. If I try to send a rom with the CMD on my pc it says "error: closed"
I have done some research and found some similar cases but not simiilar enough to have the same fixes
I have windows 10 and TWRP is 2.8.7.0
If anybody helps me that would be pretty useful
Thanks!
minor9719 said:
Hello everybody
Well, I have his issue. I tried to flash some new roms into the OPO yesterday and I had some issues with one, so I decided to flash other one, but when I wiped the things I also wiped the internal storage and I didnt know that that would erase my OS, now i'm trying to flash a rom but it wont let me with the bootloader because it says its locked, and if i try to unlock it using OPO toolking via ADB sideload the phone shows it requires ADB 1.0.32 which is the same that i have installed on my computer and if I try it using the bootloader option it just restarts and it keeps being locked. If I try to send a rom with the CMD on my pc it says "error: closed"
I have done some research and found some similar cases but not simiilar enough to have the same fixes
I have windows 10 and TWRP is 2.8.7.0
If anybody helps me that would be pretty useful
Thanks!
Click to expand...
Click to collapse
SOLUTIONS THAT MIGHT WORK
1) Use Fastboot instead of Sideload
Cmd
Go to Fastboot folder with CD
Boot into Fastboot , then type fastboot devices.
If you see the Oneplus One, then just download a random ROM and FLASH the ZIP
2) [Toolkit] Wug's Bacon Root Toolkit v1.0.3 [Updated 04/16/15] by WugFresh ---> LINK
Screenshots 1
{
"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"
}
Screenshot 2
3) [GUIDE] How to unbrick or make your phone 100% stock by vigneshvar1
This installing Android CM11s but you can afther that installing a other rom of your choise. --> LINK
Hi,
I never saw this problem
My phone is unlocked (since a year more or less) and I can't install TWRP nor CWM. I tried many tutorials such as all the root methods listed on XDA for this smartphone.
{
"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"
}
Any idea would be really appreciated!
Thanks
There might be a problem with your drivers. You can try uninstalling and reinstalling them. Also, try using fastboot commands manually
Sent from my Mate
unlock again
Thank you. I'd like not to have to relock it as it's already done and rooted. Could you please tell me what drivers to install? I tested many of them (https://i.imgur.com/wBgsezr.png) but it seems I don't have the right ones then.
I'm using Win7 64bits.
Thanks again!
Use adbdriveinstaler and when it's install you can push recovery to add folder and try this command
cd C:/adb
Fastboot flash recovery recovery.img
Change name your twrp or cwm to recovery
Send frome globe
Okay. Here we go
ADB driver installed (https://i.imgur.com/PWrZoHH.png)
Went to flash and... still not allowed.
And in fastboot/rescue mode on my phone it's written PHONE Unlocked.
WTF
BTW, is there any other way to upgrade the phone? Cause every time I go to the software update in the menu i'm told it's up-to-date, but it's not... Android 4.4.2 & EMUI 3.0.
I read about a "local update" but can't find out how to update from the SDcard, I only have OTA.
Bud64 said:
Okay. Here we go
ADB driver installed (https://i.imgur.com/PWrZoHH.png)
Went to flash and... still not allowed.
And in fastboot/rescue mode on my phone it's written PHONE Unlocked.
WTF
BTW, is there any other way to upgrade the phone? Cause every time I go to the software update in the menu i'm told it's up-to-date, but it's not... Android 4.4.2 & EMUI 3.0.
I read about a "local update" but can't find out how to update from the SDcard, I only have OTA.
Click to expand...
Click to collapse
In your screen you have locked bootloader. Unlock againg
Send frome globe
Okay, I sent an email to Huawei, I'll get back in a few days.
Sorry for bad grammar or lack details
Hello this night I got a notification from magisk to update magisk manager to v22. When I install it, it says magisk unsupported ....... (I forgot what it says) magisk will act as its not downloaded. So I tried to uninstall it and downgrade to 8.0.4 and it required me to reboot. After automatically reboot I'm stuck on fastboot. So I go to TWRP and try to uninstall magisk and I got error 1 and I tried to install and it did the same message. ERROR 1. can someone help me as fast as possible? It's 8:51 PM at the moment and I have school at 6 AM
{
"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"
}
Cocomug_ said:
Sorry for bad grammar or lack details
Hello this night I got a notification from magisk to update magisk manager to v22. When I install it, it says magisk unsupported ....... (I forgot what it says) magisk will act as its not downloaded. So I tried to uninstall it and downgrade to 8.0.4 and it required me to reboot. After automatically reboot I'm stuck on fastboot. So I go to TWRP and try to uninstall magisk and I got error 1 and I tried to install and it did the same message. ERROR 1. can someone help me as fast as possible? It's 8:51 PM at the moment and I have school at 6 AM
Click to expand...
Click to collapse
As the screenshot you provided implies, your boot partition seems corrupted.
Trying to figure out why can come at a later time, in the meantime try flashing a boot.img extracted from your current ROM (i.e a TWRP backup) or stock firmware (if you're on Stock). Using TWRP or fastboot should solve this issue.
Slim K said:
As the screenshot you provided implies, your boot partition seems corrupted.
Trying to figure out why can come at a later time, in the meantime try flashing a boot.img extracted from your current ROM (i.e a TWRP backup) or stock firmware (if you're on Stock). Using TWRP or fastboot should solve this issue.
Click to expand...
Click to collapse
Since I'm stuck on fastboot there's no way to extract it, so i just flashed the ROM zip file, and it worked. Thank You
Cocomug_ said:
Since I'm stuck on fastboot there's no way to extract it, so i just flashed the ROM zip file, and it worked. Thank You
Click to expand...
Click to collapse
how did you flashed it?
So I have become member of the bricked-my-phone family. I have followed this tutorial https://www.getdroidtips.com/unbrick-oneplus-6/ and successfully unbricked it.
I have downloaded latest oxygen os (I tried two latest - one with android 11 and one with android 10), I have added the zip to the root directory and from system update I selected it, but in both cases I instantly get "System update installation failed" at 0%. It also says I am up do date from OTA (it it android 8.1 lol)
what should I do?
I want to install latest oxygenOS only for firmware, then I will be installing LineageOS again. I am afraid If I do it the other way around (LOS first than firmware) I will brick it again.
{
"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"
}
Download the latest OOS11 full version and install through Settings-- System Update -- Local Update.
Hope it helps.
mm_rajesh said:
Download the latest OOS11 full version and install through Settings-- System Update -- Local Update.
Hope it helps.
Click to expand...
Click to collapse
That's exactly what I did and the result, you see on screenshot..
But later in the evening, I found the solution here https://forums.oneplus.com/threads/oneplus-6-system-update-installation-is-failed.1314311/:
The OP6 must be on 9.0.9 before upgrading to Android 10.
You are still on Oreo/Android 8.
There is a link for 9.0.9 on this website:
https://www.getdroidtips.com/download-oxygenos-9-0-9-9-0-17-update-for-oneplus-6-and-6t/
Click to expand...
Click to collapse
If you are able to boot to Fastboot as well as able to unlock bootloader than do unlock the bootloader and flash this msm file
[ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via stock recovery (with twrp is possible but not recommended). The updates will be done on the slot not used for example...
forum.xda-developers.com
And after that reboot to recovery stock and factory reset. This will fix your issue than after lock the bootloader(if it's unlock after flashing the file) and update to latest rom (download the rom from oneplus updater app with advance setting "on")