Tried to re-flash my factory boot image to my Pixel 2, and am now stuck in bootloader. I cannot find my old factory image anymore and need help. Please let me know what I can do. I already downloaded the newest platform tools, but still nothing. Here is what I can see on my phone right now.
Are or were you on the latest software and trying to flash the latest?
Stuck
enzyne said:
Are or were you on the latest software and trying to flash the latest?
Click to expand...
Click to collapse
I was on android version 8.0.0, and I tried flashing the factory 8.0.0, but no luck. now I'm just trying to figure out what to do.
solved
FoolishMove said:
I was on android version 8.0.0, and I tried flashing the factory 8.0.0, but no luck. now I'm just trying to figure out what to do.
Click to expand...
Click to collapse
Finally figured it out, just downloaded the wrong factory software. Got the right one, did the flash all and it worked.
Related
So ive been racking my brain for the last 2 hours trying to figure this out and im still stuck. I just finished unlocking my boot loader on a completely stock nexus 5 running 4.4.4
i used this methodfor unlocking my bootloader
https://www.youtube.com/watch?v=2cOUseflKNE
I then downloaded 5.0.1
785a2f7af3718dba7e569decde8b6c4dc476a309.signed-hammerhead-LRX22C-from-LRX21O.785a2f7a.zip
i then tried side loading the zip using this method
https://www.youtube.com/watch?v=uvch38KDmTk
but i get one of 2 messages, no device found or waiting on device. nothing happens either way
i then tried
http://www.androidcentral.com/how-manually-upgrade-your-nexus?pg=4#content
and got the same message
what am I doing wrong or missing. My boot loader is showing as unlocked
You have to upgrade to 5.0, and then sideload 5.0.1 on top of 5.0. Or you can flash the 5.0.1 factory image.
EDIT: The messages you're getting are probably because you don't have the correct ADB drivers: http://forum.xda-developers.com/showthread.php?t=2588979
I re downloaded that version of adb and im currently downloading 5.0
I got it! I did what u said and download 5.0 and restarted my pc and everything worked, Ill try to sideload 5.01 later
Why flash the 5.0 image just to flash the 5.0.1 OTA when you can just flash the 5.0.1 image?
Wakamatsu said:
Why flash the 5.0 image just to flash the 5.0.1 OTA when you can just flash the 5.0.1 image?
Click to expand...
Click to collapse
Because its so easy, we must insert unnecessary steps to get a feeling of achievement
Wakamatsu said:
Why flash the 5.0 image just to flash the 5.0.1 OTA when you can just flash the 5.0.1 image?
Click to expand...
Click to collapse
Don't think he flashed the image. I think he applied the 5.0 OTA via sideload, then he's going to apply the 5.0.1 OTA in the same manner. Doing that will allow him to not wipe his data. Kinda makes sense since that's how Google intends for it to progress if he just waits for the updates.
Yaz75 said:
Doing that will allow him to not wipe his data.
Click to expand...
Click to collapse
He unlocked his bootloader in fastboot. The phone is wiped.
Yaz75 said:
Kinda makes sense since that's how Google intends for it to progress if he just waits for the updates.
Click to expand...
Click to collapse
Google intended things to be easy with OTA, not optimal, imo.
Background: My phone is rooted and I have TWRP installed as my recovery.
Android 6.0 rolled out to my phone, and I really want to update it. However, everytime I try to install it, my phone boots into TWRP and does nothing. After booting into Android, my phone will boot into TWRP on its own again, and after repeating this for a while it will read something along the lines of, "There was a problem with the update" My question is this: how do I install the software update sent to my phone?
AliRockz said:
Background: My phone is rooted and I have TWRP installed as my recovery.
Android 6.0 rolled out to my phone, and I really want to update it. However, everytime I try to install it, my phone boots into TWRP and does nothing. After booting into Android, my phone will boot into TWRP on its own again, and after repeating this for a while it will read something along the lines of, "There was a problem with the update" My question is this: how do I install the software update sent to my phone?
Click to expand...
Click to collapse
You can't flash the OTA with a custom recovery or root. You'll have to flash a stock recovery to get the OTA.
Tel864 said:
You can't flash the OTA with a custom recovery or root. You'll have to flash a stock recovery to get the OTA.
Click to expand...
Click to collapse
How would I do this?
AliRockz said:
How would I do this?
Click to expand...
Click to collapse
Search, or look around in the 2015 General Forum.
So I have a few questions about the android P beta program. I was wondering if anyone could answer before I opt into it
1) if I opt into I get ota updates which won't be Verizon variants so would I be able to jump back to Oreo?
2)would this allow me to unlock my bootloader possibly?
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
dbrohrer said:
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
Click to expand...
Click to collapse
Thanks so much for this information I'm gonna opt in for the hell of it
dbrohrer said:
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
Click to expand...
Click to collapse
Im not sure i understood this properly, I've already unlocked the bootloader of my Verizon pixel 2 on 8.1, if I update to P, will the bootloader be locked back? Or I can update and still enjoy the unlocked bootloader?
Thanks!
daede86 said:
Im not sure i understood this properly, I've already unlocked the bootloader of my Verizon pixel 2 on 8.1, if I update to P, will the bootloader be locked back? Or I can update and still enjoy the unlocked bootloader?
Thanks!
Click to expand...
Click to collapse
If you unlocked the bootloader already, it will stay unlocked until you lock it via fastboot from your computer. Flashing firmware will not relock it. Don't worry, updating to Android p won't mess with that.
I'm really enjoying this beta so far. The new navigation gestures are cool. Nothing so far that makes me want to go back to 8.1.
dbrohrer said:
If you unlocked the bootloader already, it will stay unlocked until you lock it via fastboot from your computer. Flashing firmware will not relock it. Don't worry, updating to Android p won't mess with that.
I'm really enjoying this beta so far. The new navigation gestures are cool. Nothing so far that makes me want to go back to 8.1.
Click to expand...
Click to collapse
thanks so much! i've installed android p but i'm not able to root the phone.. i've installed magisk but it fails while patching boot.img.. any idea?
thanks again!
daede86 said:
thanks so much! i've installed android p but i'm not able to root the phone.. i've installed magisk but it fails while patching boot.img.. any idea?
thanks again!
Click to expand...
Click to collapse
What version of magisk are you flashing? You should be using the beta magisk. Looks like people are having some success rooting with version 16.4.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hope this helps.
dbrohrer said:
What version of magisk are you flashing? You should be using the beta magisk. Looks like people are having some success rooting with version 16.4.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hope this helps.
Click to expand...
Click to collapse
thanks so much!!
i'm trying to flash magisk using this tutorial https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535 but as soon as i launch fastboot boot [twrp image filename].img, it loads up twrp (i see the splash screen) but right after it crashed and reboot.. so i'm not able to flash magisk beta
is there a way to install magisk manager (beta) and being able to patch the boot.img without passing through twrp?
thanks again and sorry for all my questions!
daede86 said:
thanks so much!!
i'm trying to flash magisk using this tutorial https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535 but as soon as i launch fastboot boot [twrp image filename].img, it loads up twrp (i see the splash screen) but right after it crashed and reboot.. so i'm not able to flash magisk beta
is there a way to install magisk manager (beta) and being able to patch the boot.img without passing through twrp?
thanks again and sorry for all my questions!
Click to expand...
Click to collapse
Do you have the Pixel 2 or 2 XL? Are you booting with twrp 3.2.1-2 img?
dbrohrer said:
Do you have the Pixel 2 or 2 XL? Are you booting with twrp 3.2.1-2 img?
Click to expand...
Click to collapse
i have a pixel 2 verizon with bootloader unlocked trying to boot twrp-3.2.1-2-walleye.img. am i doing something wrong?
thanks again!
daede86 said:
i have a pixel 2 verizon with bootloader unlocked trying to boot twrp-3.2.1-2-walleye.img. am i doing something wrong?
thanks again!
Click to expand...
Click to collapse
That's correct. Just checking. You need to boot to twrp to flash magisk. There isn't another way that I know of. Maybe download twrp img again? I doubt its a corrupt download since you get the twrp splash screen, but its worth a try.
dbrohrer said:
That's correct. Just checking. You need to boot to twrp to flash magisk. There isn't another way that I know of. Maybe download twrp img again? I doubt its a corrupt download since you get the twrp splash screen, but its worth a try.
Click to expand...
Click to collapse
no luck
should i try to flash again the factory image?
or maybe opt out from androind p beta, install back oreo, root and flash android p without deleting my data?
daede86 said:
no luck
should i try to flash again the factory image?
or maybe opt out from androind p beta, install back oreo, root and flash android p without deleting my data?
Click to expand...
Click to collapse
You can boot into the OS right? Are you're platform tools the latest version?
Reverting back to oreo, rooting, and updating to p beta will either fail or wipe out root. You won't end up with p beta and root. Don't do that.
dbrohrer said:
You can boot into the OS right? Are you're platform tools the latest version?
Reverting back to oreo, rooting, and updating to p beta will either fail or wipe out root. You won't end up with p beta and root. Don't do that.
Click to expand...
Click to collapse
ok thanks again, really appreciated.
yes, at least i can boot and use my pixel with no problem, i'd only like to root it and restore my backup
daede86 said:
ok thanks again, really appreciated.
yes, at least i can boot and use my pixel with no problem, i'd only like to root it and restore my backup
Click to expand...
Click to collapse
I understand that. I am not sure whats going on then. Sorry.
i've solved the problem!! just to share, i had installed handbrake in my mac to share files via usb and i guess it caused some incompatibility issue.. i've just uninstalled it and i've managed to flash it properly!
I need some help with my Honor 6x. I'm trying to get a solution or procedure to reset my phone. the firm where says generic _a15 when connecting it to the computer. The manager won't update it either just keeps giving me a fail error. I have tried to root it but I think since the software is wrong it's not taking the root. can anyone help or point me in the direction o what I need to do. If this has already been answered My apologies and can I get the link. thank you.
Do you have an unlocked bootloader? What's your Android version?
Mannan Qamar said:
Do you have an unlocked bootloader? What's your Android version?
Click to expand...
Click to collapse
yes, the boot loader is unlocked. I believe it was rooted before. android 7.0
slimjimz81 said:
yes, the boot loader is unlocked. I believe it was rooted before. android 7.0
Click to expand...
Click to collapse
Flash the two small update zips via TWRP
Not the update.zip which is 1+ GB in size but the two small zips via TWRP
I been trying to get twrp to take but it keeps giving me the erecovery.
slimjimz81 said:
I been trying to get twrp to take but it keeps giving me the erecovery.
Click to expand...
Click to collapse
What command you use. You have Android 7 or 8 right now
Android 7.0 I have been using that app. That boots it into recovery then tries to flash it. I tried to get the adb cmd to work but it doesn't find the file. I know this all sounds like gibberish but that's why I'm lost.
My phone is boot-looping after i did android 9.0 update using odin.I had PrometheusOneUI V2.0 as a custom rom before but i had no imei and baseband so i needed that back so i downloaded the newest filmware of sammobile and i flashed the filmware using Odin.I got a pass but the phone is now bootlooping.When i go to download mode now FRP Lock and OEM lock are off.and when i try to flash root it now shows me <Only official released binaries are allowed to be flashed (Recovery)>.It wont let me flash anything other than the stock rom that results in bootlooping.Did anyone else have this problem,Can someone please help me with my bricked SM-J530F
kevin50206 said:
My phone is boot-looping after i did android 9.0 update using odin.I had PrometheusOneUI V2.0 as a custom rom before but i had no imei and baseband so i needed that back so i downloaded the newest filmware of sammobile and i flashed the filmware using Odin.I got a pass but the phone is now bootlooping.When i go to download mode now FRP Lock and OEM lock are off.and when i try to flash root it now shows me <Only official released binaries are allowed to be flashed (Recovery)>.It wont let me flash anything other than the stock rom that results in bootlooping.Did anyone else have this problem,Can someone please help me with my bricked SM-J530F
Click to expand...
Click to collapse
Flash the device via Odin, when it bootloop, turn the device off, then boot your device into stock recovery and then choose the factory reset option.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Flash the device via Odin, when it bootloop, turn the device off, then boot your device into stock recovery and then choose the factory reset option.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I already tried that and i wiped catch,i also tried another filmware form the uk still its bootlooping
kevin50206 said:
I already tried that and i wiped catch,i also tried another filmware form the uk still its bootlooping
Click to expand...
Click to collapse
Ok, you've got something else going on.
Have you previously modified the device or flashed anything on the device that wasn't stock? If so, did the modifications or whatever you flashed cause an issue and that is now the reason you are flashing the firmware?
Are you certain that your firmware is for your specific device and is it the most up to date version for your device?
Droidriven said:
Ok, you've got something else going on.
Have you previously modified the device or flashed anything on the device that wasn't stock? If so, did the modifications or whatever you flashed cause an issue and that is now the reason you are flashing the firmware?
Are you certain that your firmware is for your specific device and is it the most up to date version for your device?
Click to expand...
Click to collapse
Yes i matched the model number and no i was not running anything that isn't for it
kevin50206 said:
Yes i matched the model number and no i was not running anything that isn't for it
Click to expand...
Click to collapse
But are you using the most up to date firmware? Older/downgraded firmware won't work, it has to be exactly the same binary as what is already on the device or a firmware with a newer binary, it can not be a firmware that has an older binary than the firmware that is already on the device.
Sent from my SM-S767VL using Tapatalk