[EDIT:] I actually ended up solving this, as mentioned in the lower post, but I'm still having a bit of trouble with the part below where trying to flash twrp gives the error "FAILED (remote: Not allowed to flash (recovery))" so I'd still like help with that if possible. Thanks!
Hello,
I have a Pixel 3 that I got when it first came out, there was only one custom rom for it which I installed with TWRP, but the rom was kind of broken, so i just used the phone as a media player for a couple years, until I thought to check for new roms, and there are lots now. So I'm following the PixelDust installation instructions which say I absolutely must start by reverting stock rom. On my Samsung I used Odin, but there's nothing like that for this, except sources pointing to Android Flash Tool website, but after I tried flashing with that site, it just went into bootloader and said "no valid slots to boot", so it evidently failed. So my next thought was to flash it manually, so I downloaded the latest Blueline image from here. I'm using this guide, but it says to extract the zip and use the flash-all command, but when I extract this image I only get these files (see screenshot attachment). Another guide says there will be a file in that folder that I should extract that too but the only one that makes any sense is payload.bin and 7zip doesn't recognize that. And I haven't been able to get anything really comprehensible through Google searches. So I'm at a dead end. :/
So basically I'm hoping someone can give me a step-by-step instruction how to flash this rom. I'm not really a tech guy but I have a basic understanding, I've used ADB and fastboot before, following instructions though. If you can take the time to give me an idiot-proof instruction I'd really appreciate it because at the moment the phone's useless
Thanks!
EDIT:
I actually tried to at least flash TWRP so I could try to restore my nandroid of the other rom, but when I tried, I got the error:
Code:
D:\D Backup\Misc\nandroid\adbfastboot samsung a5>fastboot flash recovery
twrp-3.4.0-0-twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (4560 KB)...
OKAY [ 0.255s]
writing 'recovery'...
[B]FAILED (remote: Not allowed to flash (recovery))[/B]
finished. total time: 0.317s
And searches on that said it was because the bootloader is locked... but it's not. So I don't know why I can't even do that. :/ I'd like to at least get to something functional. >.< So I'd appreciate any help. Thanks!
Okay, well good news, I figured the main thing out by accident. I didn't realize there was a difference between factory image and ota image and I guess I got the ota, not the factory, which was when I unzipped it it just had meta-inf and not flash-all. But I also discovered how to sideload that ota and i did that, and now the phone is back to stock, hooray!
But I'm still having trouble getting TWRP back on it for the same reason listed above, so can you guys help me with that part?
lol thanks ^^;
PistolSlap said:
Hello,
I have a Pixel 3 that I got when it first came out, there was only one custom rom for it which I installed with TWRP, but the rom was kind of broken, so i just used the phone as a media player for a couple years, until I thought to check for new roms, and there are lots now. So I'm following the PixelDust installation instructions which say I absolutely must start by reverting stock rom. On my Samsung I used Odin, but there's nothing like that for this, except sources pointing to Android Flash Tool website, but after I tried flashing with that site, it just went into bootloader and said "no valid slots to boot", so it evidently failed. So my next thought was to flash it manually, so I downloaded the latest Blueline image from here. I'm using this guide, but it says to extract the zip and use the flash-all command, but when I extract this image I only get these files (see screenshot attachment). Another guide says there will be a file in that folder that I should extract that too but the only one that makes any sense is payload.bin and 7zip doesn't recognize that. And I haven't been able to get anything really comprehensible through Google searches. So I'm at a dead end. :/
So basically I'm hoping someone can give me a step-by-step instruction how to flash this rom. I'm not really a tech guy but I have a basic understanding, I've used ADB and fastboot before, following instructions though. If you can take the time to give me an idiot-proof instruction I'd really appreciate it because at the moment the phone's useless
Thanks!
EDIT:
I actually tried to at least flash TWRP so I could try to restore my nandroid of the other rom, but when I tried, I got the error:
Code:
D:\D Backup\Misc\nandroid\adbfastboot samsung a5>fastboot flash recovery
twrp-3.4.0-0-twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (4560 KB)...
OKAY [ 0.255s]
writing 'recovery'...
[B]FAILED (remote: Not allowed to flash (recovery))[/B]
finished. total time: 0.317s
And searches on that said it was because the bootloader is locked... but it's not. So I don't know why I can't even do that. :/ I'd like to at least get to something functional. >.< So I'd appreciate any help. Thanks!
Click to expand...
Click to collapse
PistolSlap said:
Okay, well good news, I figured the main thing out by accident. I didn't realize there was a difference between factory image and ota image and I guess I got the ota, not the factory, which was when I unzipped it it just had meta-inf and not flash-all. But I also discovered how to sideload that ota and i did that, and now the phone is back to stock, hooray!
But I'm still having trouble getting TWRP back on it for the same reason listed above, so can you guys help me with that part?
lol thanks ^^;
Click to expand...
Click to collapse
If you flashed the latest image, you are on Android 11. TWRP will not work with Android 11. There is not even an official Pixel 3 TWRP for Android 10.
dcarvil said:
If you flashed the latest image, you are on Android 11. TWRP will not work with Android 11. There is not even an official Pixel 3 TWRP for Android 10.
Click to expand...
Click to collapse
THIS! theres no functional twrp and it looks like there may not be one at all. i recently reverted to android 10 so that i could go back to DirtyUnicors. i recommend waiting awhile longer for stable R ROMs.
Ok but this happened with Android 8. I didn't flash the latest image but actually the earliest. And come to think of it it happened even before the flash when there wasn't even an OS at that point. (The phone was wiped but no OS was installed.) so I tried it both then and after I got Android 8 installed and same disallowed error.
dcarvil said:
If you flashed the latest image, you are on Android 11. TWRP will not work with Android 11. There is not even an official Pixel 3 TWRP for Android 10.
Click to expand...
Click to collapse
PistolSlap said:
Ok but this happened with Android 8. I didn't flash the latest image but actually the earliest. And come to think of it it happened even before the flash when there wasn't even an OS at that point. (The phone was wiped but no OS was installed.) so I tried it both then and after I got Android 8 installed and same disallowed error.
Click to expand...
Click to collapse
Are you sure you are on Android 8? The Pixel 3 shipped with Android 9. There is no Android 8 for the Pixel 3 listed in the link you gave in your original post.
If you really are on Android 8, or even Android 9, try the instructions on the Pixel 3 TWRP website at https://twrp.me/google/googlepixel3.html. The instructions you listed in your original post are for a Nexus 6, not a Pixel 3.
dcarvil said:
Are you sure you are on Android 8? The Pixel 3 shipped with Android 9. There is no Android 8 for the Pixel 3 listed in the link you gave in your original post.
If you really are on Android 8, or even Android 9, try the instructions on the Pixel 3 TWRP website at https://twrp.me/google/googlepixel3.html. The instructions you listed in your original post are for a Nexus 6, not a Pixel 3.
Click to expand...
Click to collapse
Ah sorry I meant Android 9.
Okay, cool I followed those instructions and it worked. Thanks! I'm not sure what I did wrong before.
One other question: My older phone is a Samsung Galaxy A5, which doesn't have A/B slots, and I've looked into it but I'm still not exactly sure how they work. Is it correct that they're both system images? So if I have stock in slot A can I install a custom rom in slot B and switch between them? Or have I got that wrong?
Also, when I was first flashing a rom onto this Pixel 3, I tried to do a nandroid backup, which for some reason failed to restore properly, and someone mentioned it was because it was a slot device? So does that mean nandroid backups don't work on the PIxel 3?
Thanks for your help. I'm not a compsci guy or android dev, so this stuff takes a bit more for me to quite understand. :")
PistolSlap said:
Ah sorry I meant Android 9.
Okay, cool I followed those instructions and it worked. Thanks! I'm not sure what I did wrong before.
One other question: My older phone is a Samsung Galaxy A5, which doesn't have A/B slots, and I've looked into it but I'm still not exactly sure how they work. Is it correct that they're both system images? So if I have stock in slot A can I install a custom rom in slot B and switch between them? Or have I got that wrong?
Also, when I was first flashing a rom onto this Pixel 3, I tried to do a nandroid backup, which for some reason failed to restore properly, and someone mentioned it was because it was a slot device? So does that mean nandroid backups don't work on the PIxel 3?
Thanks for your help. I'm not a compsci guy or android dev, so this stuff takes a bit more for me to quite understand. :")
Click to expand...
Click to collapse
I have no experience with TWRP on a Pixel 3, so I can't answer your question about nandroid backups. Perhaps someone else can answer. The question on the A5 should be asked in a different forum.
The difference in the instructions for the Nexus 6 and Pixel 3, is that you boot TWRP, then install from TWRP for the Pixel 3.
Related
Hi Everyone!
Because of having issues i can´t fix on my OnePlus, i´m finally asking for some professional help here, as it´s getting more and more complicated and i don´t want to ruin my phone.
What was my plan?
Installing CM11S 44S on my OPO, which had the 05Q Version as factory setting.
Also i wanted to install a franco kernel.
I hoped, if i do both steps successfully, my OPO will have a good battery life (44S seemed to be the most efficient version, according to some forums).
What did i do so far?
First i set up an adb backup for my data, but not for the OS. However, i installed SDK plus tools and drivers.
Next step was installing a new recovery, which is able to flash a new version of CM11S, so i set up TWRP with fastboot, which means my device is "unlocked" now.
Everything worked well so far, i also made an backup in TWRP.
The problem:
I wanted to reboot my OPO at some point and TWRP asked me for rooting my device. Accidentally i swiped over so it started rooting process, but i didn´t want to root it, so i immediately shut the device down.
By now TWRP recovery/fastboot is working, but my OS 05Q is lost and i can´t install a new ROM because im getting the Report:
--
Checking for MD5 file...
Skipping MD5 check; no MD5 file found
Error flashing zip /<path to .zip file>
--
Can anyone help me to get 05Q back or the 44S with the franco kernel?
I know there might be some other threads that deal with similar problems, but actually none of them helped me so far. For example: do i need a fastboot image or signed flashable zips (which i have)? In which order do i install the kernel and the ROM?
Some Information:
I can access my device via fastboot and my OPO is also shown as a adb device on my MAC.
When starting in TWRP, i can also access the device in USB Mode, transfering files is also possible.
I´m not really competent with android modding or programming, so i will need some noob-friendly answers, but i bet you guys know how to help me out here.
Thank you very much for your help, i really don´t know what to do anymore.
EDIT:
I found out how to place a md5 file to the referring version, but it still sais: MD5 does not match.
I´m so done with it right now that i wish i had my OPO back as it was few days ago.
Well, i cant really help here as i have not face this problem but ur mistake was that u Immediately shut the device down the moment it was installing root. It may have corrupted the partitions of the phone and left it at that state, so maybe restoring the partitions of that section may help. Like i said im not knowledgeable about this
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Heisenberg said:
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Thyrix said:
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Click to expand...
Click to collapse
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Heisenberg said:
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Click to expand...
Click to collapse
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Thyrix said:
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Click to expand...
Click to collapse
You need the fastboot images.
Heisenberg said:
You need the fastboot images.
Click to expand...
Click to collapse
Got stuck at step 2: It Terminal said error: cannot determine image filename for sbl1.mbn - although the name is correct and the file is in the correct folder :/
EDIT:
Fixed it, forgot to type sbl1 2 times, im sorry
And it worked, thank you sooooo much!!!
I have a Google version Pixel 2 and have unlocked the bootloader (unlocked/relocked multiple times) and cannot flash any bootloader. I have tried flashing the "production" BL and the Dev Preview BL. I get the same error each time.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.110s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.125s
I have tried using the fastboot flashing unlock and fastboot flashing unlock_critical commands. I have relocked the BL then booted into the OS and used ADB to reboot to the BL, I still get the same error. I have tried changing the active slot to with no change.. I have tried the google version of platform tools, minimal adb, and another adb version I had from previous phones. I have downloaded the latest drivers from google no change.. I can flash and format other partitions, just not the BL (although I haven't tried format/erase bootloader, and I don't plan to)
I have tried different USB C cables, Google OEM, Samsung OEM, AUKEY .. different USB ports, different computers (although both with Windows 10 64bit).
Any suggestions?
lazarus2297 said:
I have a Google version Pixel 2 and have unlocked the bootloader (unlocked/relocked multiple times) and cannot flash any bootloader. I have tried flashing the "production" BL and the Dev Preview BL. I get the same error each time.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.110s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.125s
I have tried using the fastboot flashing unlock and fastboot flashing unlock_critical commands. I have relocked the BL then booted into the OS and used ADB to reboot to the BL, I still get the same error. I have tried changing the active slot to with no change.. I have tried the google version of platform tools, minimal adb, and another adb version I had from previous phones. I have downloaded the latest drivers from google no change.. I can flash and format other partitions, just not the BL (although I haven't tried format/erase bootloader, and I don't plan to)
I have tried different USB C cables, Google OEM, Samsung OEM, AUKEY .. different USB ports, different computers (although both with Windows 10 64bit).
Any suggestions?
Click to expand...
Click to collapse
Your not the only one there are others that have had similar issues, though i don't know the fix.
There is a script somewhere on another thread that might help. I will link.
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
Hey you go.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Hopefully something in that will help
Just to be clear, are you using the latest fastboot? That's often an issue.
Some have had trouble with computers with usb-c ports. Have you tried a computer with usb-a and, of course, a usb-a to usb-c cable.
razrlover said:
Your not the only one there are others that have had similar issues, though i don't know the fix.
There is a script somewhere on another thread that might help. I will link.
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
Hey you go.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Hopefully something in that will help
Click to expand...
Click to collapse
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
foosion said:
Just to be clear, are you using the latest fastboot? That's often an issue.
Some have had trouble with computers with usb-c ports. Have you tried a computer with usb-a and, of course, a usb-a to usb-c cable.
Click to expand...
Click to collapse
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
lazarus2297 said:
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
Click to expand...
Click to collapse
I'm not sure if this question will help, are you flashing the bootloader into the correct slot? I had issue early on with this and found that I needed to direct the flash to the correct slot. Just a thought
phonefreedom said:
I'm not sure if this question will help, are you flashing the bootloader into the correct slot? I had issue early on with this and found that I needed to direct the flash to the correct slot. Just a thought
Click to expand...
Click to collapse
Not exactly sure but I have tried changing the active slot to a or b.
I am using the command Fastboot flash bootloader "filename.img" (no quotations) I don't know how I would tell it to flash a specific slot other than whatever is the current active slot..
lazarus2297 said:
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
Click to expand...
Click to collapse
lazarus2297 said:
Not exactly sure but I have tried changing the active slot to a or b.
I am using the command Fastboot flash bootloader "filename.img" (no quotations) I don't know how I would tell it to flash a specific slot other than whatever is the current active slot..
Click to expand...
Click to collapse
+Natahranta had shared the following with me and I hope it helps in your case...
"Download factory image from Google, unpack it, insidebis another zip, there is boot.img file
Flash it to both slots A and B. It must be the same version/update your phone was on.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
If you're not sure which exactly stock rom build your phone is on, use the flash_all.bat to flash the whole image on your phone, to be sure you have no mismatch between system and boot. Just remove "-w" from the bat file so it doesn't erase your user data"
So i got it working here is what I did..
I used the factory image to flash back 100% stock and relocked the bootloader, I then signed my device up for the Dev Preview, and surprisingly I got the notification to install DP pretty quickly. After DP installed I rebooted into the bootloader and noticed that my bootloader version had changed to the DP BL version. I then unlocked with the standard Fastboot Flashing Unlock command and unlocked the bootloader. After the phone rebooted I shut it down and booted into the BL and flashed the stock BL (a downgrade) it was successful, so i flashed the DP BL version and it was successful as well. Rebooted normally into the OS and all is well.
Hopefully this will help anyone else having the same problem.
lazarus2297 said:
I have relocked the BL then booted into the OS
Click to expand...
Click to collapse
I don't have any suggestions for your issue. But don't relock it, ever. You are playing with fire, if it goes bad and it's locked you are done.
lazarus2297 said:
So i got it working here is what I did..
I used the factory image to flash back 100% stock and relocked the bootloader, I then signed my device up for the Dev Preview, and surprisingly I got the notification to install DP pretty quickly. After DP installed I rebooted into the bootloader and noticed that my bootloader version had changed to the DP BL version. I then unlocked with the standard Fastboot Flashing Unlock command and unlocked the bootloader. After the phone rebooted I shut it down and booted into the BL and flashed the stock BL (a downgrade) it was successful, so i flashed the DP BL version and it was successful as well. Rebooted normally into the OS and all is well.
Hopefully this will help anyone else having the same problem.
Click to expand...
Click to collapse
I had this problem and created a thread about it a month ago: https://forum.xda-developers.com/pixel-2/help/failed-remote-command-flash-error-t3701929. A couple other people in that thread are now also reporting the problem.
No one seemed to know what the " FAILED (remote: Command Flash Error)" means. I never figured it out.
At the time of the November update, however, I was able to sideload OTA images with adb without problem. I assume that the OTA method also updates the bootloader, like the Dev Preview did for you. I couldn't tell with the November update, though, because it had the same version of the bootloader in it as the one that shipped with the phone.
So I'm wondering if simply sideloading the current December OTA image with adb would accomplish the same thing you did, without having to lock the bootloader, unlock it again, and go through the pain of wiping the device. I wonder if there was just something weird about the original version of the bootloader. Weirdness like this was discussed early on with the Pixel 2 in this XDA article: https://www.xda-developers.com/pixel-2-failing-flash-factory-images/ If I'm right, then once one sideloads the December OTA image and gets a new bootloader, there may not be an issue flashing bootloaders with fastboot in the future. I assume that the Dev Preview also used the OTA method to update the device.
In other words, I'm wondering if the step of unlocking and relocking the bootloader was not necessary. You just had to do it to get the Developer Preview (right?).
Just guessing here. I haven't had time yet to try this.
Okay, I tried my idea above and I was correct. Simplying sideloading the December OTA image updates the bootloader. After that the problem is solved. I can successfully flash the bootloader .img file directly (from the factory image zip) using fastboot. So I assume going forward there should not be any problems flashing factory images, instead of sideloading OTA images.
This solution also avoids having to lock and unlock the bootloader and wipe the whole device in the process.
cb474 said:
Simplying sideloading the December OTA image updates the bootloader.
Click to expand...
Click to collapse
My problem is that I have TWRP installed and it won't sideload nor flash the OTA file. I am trying to figure out how to flash the factory recovery. Unlike the factory images of before, there is no obvious recovery image in the zip.
-----------
Nevermind. I figured out that recovery is part of boot now. I flashed the factory boot and flashing OTA now.
snovvman said:
My problem is that I have TWRP installed and it won't sideload nor flash the OTA file. I am trying to figure out how to flash the factory recovery. Unlike the factory images of before, there is no obvious recovery image in the zip.
Click to expand...
Click to collapse
I'm not really sure how to solve that problem. Perhaps you should ask in the TWRP thread. I thought that when you install TWRP it backs up the recovery and has a way to restore it. But I could be wrong about that. You're correct that the recovery image does not seem to be included in the factory image zip like it used to be. I have seen other people mention that.
cb474 said:
I'm not really sure how to solve that problem. Perhaps you should ask in the TWRP thread. I thought that when you install TWRP it backs up the recovery and has a way to restore it. But I could be wrong about that. You're correct that the recovery image does not seem to be included in the factory image zip like it used to be. I have seen other people mention that.
Click to expand...
Click to collapse
Thanks for replying. Silly me, I was thinking the old way of doing business, where the recovery had its own image/partition. I figured out that recovery is part of boot, so I flashed boot and got the factory recovery back. I'm on 8.1 now.
snovvman said:
Thanks for replying. Silly me, I was thinking the old way of doing business, where the recovery had its own image/partition. I figured out that recovery is part of boot, so I flashed boot and got the factory recovery back. I'm on 8.1 now.
Click to expand...
Click to collapse
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
cb474 said:
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
Click to expand...
Click to collapse
So you know, TWRP for the first gen Pixels never left beta. They worked well enough... For Pixel 2s, I use the current beta for backups and they are handy for certain things. For now I am booting to TWRP to flash Magisk. For me, it is more convenient than patching.
cb474 said:
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php
kendong2 said:
https://forum.xda-developers.com/showpost.php
Click to expand...
Click to collapse
That link leads to nothing.
---------- Post added at 01:13 AM ---------- Previous post was at 01:11 AM ----------
snovvman said:
So you know, TWRP for the first gen Pixels never left beta. They worked well enough... For Pixel 2s, I use the current beta for backups and they are handy for certain things. For now I am booting to TWRP to flash Magisk. For me, it is more convenient than patching.
Click to expand...
Click to collapse
Yeah, I saw that. I'm just hoping with what was learned from the original Pixel and given that supposedly most phones will eventually use the A/B partition scheme that maybe TWRP will advance further on the Pixel 2. I really miss nandroid backups. I miss LineageOS too. Everything was so much simpler on my old Nexus 4. And I wasn't constantly feeling like I was going to brick my device every time I tried to do something.
cb474 said:
That link leads to nothing.
Click to expand...
Click to collapse
Sorry, did that on the phone. Was supposed to go here: https://forum.xda-developers.com/showpost.php?p=74704694&postcount=155
TWRP 3.2.0.0 final release (as I understand it) has been announced a few days ago. Don't know why the thread title still says beta.
This is freaking weird. Anyway, followed post #11 to sideload DEC OTA zip in stock recovery, and now finally I have a bootloader that is 0066 on both slot a and b. Thanked @cb474 !
Hey Guys,
I know there are some older threads but im getting a bit confused and a bit desperate. My op6 arrived a few days back and I decided to flash a custom rom today. Got twrp and magisk installed. Tried to flash omnirom and I also flashed twrp again (got confused at the time). Now my phone only boots into fastboot. If anyone could help I would greatly appreciated it, panicking ever so slightly about this. I was on Android oos 9.0 when i tried to flash omnirom 9.0.
I tried to fastboot boot into twrp via the cmd but its giving me an error of (Failed to load/authenticate boot image: load error)
Thanks in advance.
Did you have pie on both slots? And also, if you know there is threads regarding this, why don't you read the sulotions provided?
whizeguy said:
Did you have pie on both slots? And also, if you know there is threads regarding this, why don't you read the sulotions provided?
Click to expand...
Click to collapse
Hey thanks for the quick reply. I looked through some of the other threads and most of them seem to assume that the person does not have an unlocked bootloader and such. Atm im reading through this thread and trying to understand exactly what to do. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/page61
Came from a oneplus 5 so not used to the whole slot system.
But yeah couldnt find a thread that fits my situation for android 9.0
Edited:
From what I understand it should be a pi setup on both if they are both populated.
Edit2:
So good news. Got the phone working again. Used an unbrick tool over on the oneplus forums. If anyone ever finds themselves in the same situation look for the Mega unbrick guide on the oneplus forums.
I'm having the same issue. After watching multiple videos, reading multiple XDA threads, I'm still confused as to what to do. Here is everything that I have done, and continue to have the same issue (reboots into bootloader)
1. Installed latest Oxygen OS via OTA.
2. OEM unlocked.
3. Installed TWRP (Blu Spark 3.2.3)
4. Wiped System, Caches and Data
5. Installed Lineage 16.0 on both slots via TWRP
6. Flashed TWRP.zip
Upon rebooting the phone, it boots straight into the bootloader. Am I doing something wrong or missing something?
Also coming from Nexus 6P and unfamiliar with the slot system...
Edit: 'Unbricked' device by using the method found in this thread...
So I just picked up a Pixel 3 while on sale to replace my failing Nexus 5 that was literally falling apart. I managed to unlock the bootloader easily. Used a USB C to USB A cable from my Nintendo Switch used for charging the controller for unlocking the bootloader. Next step was to install TWRP and eventually Magisk.
So I followed the instructions to install TWRP from the TWRP website and grabbed the latest image and zip. Initially when I ran the command to boot the image, I would get a "too many links" error. Everything I found in relations to this said I needed a better cable. Odd but okay. I had planned to pickup a new one anyways for transferring music and pictures and such. Got it today, reboot into fastboot and now the command completes successfully with no error. Unfortunately instead of booting into TWRP temporarily as per the instructions, to then install the ZIP for TWRP, the phone boots straight into Android. I have tried the following commands. The first being from the official TWRP guide, and the second being from another guide I had found.
fastboot.exe boot twrp-3.2.3-0-blueline.img
fastboot.exe boot recovery twrp-3.2.3-0-blueline.img
Obviously both result in the same issue. Namely the phone simply reboots right into Android. I am using the latest Platform SDK tools from google, and am using the most up to date drivers for the phone. I am at a loss of what I might be missing. I do see info about boot slots A and B (My phone is B), but nothing in relation to that as far as installing TWRP is concerned. Any help would be appreciated!
What Android version is your Pixel 3 device running?
BobPony said:
What Android version is your Pixel 3 device running?
Click to expand...
Click to collapse
Android 10. Latest OTA.
Ultratails42 said:
Android 10. Latest OTA.
Click to expand...
Click to collapse
Twrp doesn't work on 10. Maybe it will some day but not now.
jd1639 said:
Twrp doesn't work on 10. Maybe it will some day but not now.
Click to expand...
Click to collapse
Yeah. I see that now. Looked it up after they asked the android version. Here's hoping they update it soon to work with 10.
Ultratails42 said:
Yeah. I see that now. Looked it up after they asked the android version. Here's hoping they update it soon to work with 10.
Click to expand...
Click to collapse
If you want, you can downgrade to Android 9 using the factory images with the flash-all script. But, it requires to have the bootloader unlocked.
Hey y'all,
I'm switching back to Android after 3 years on iOS and I'm a bit stuck on some changes.
First off, battery life on OOS was terrible and they ended support for OP7Pro this year, with no more major (or even security updates) so I decided to get a custom ROM, and I got this Pixel Experience ROM from here. I'm stuck with a few things:
Trying to root it, looks like the procedure is as simple as patch the boot image in that link with Magisk and flash it from the bootloader via "fastboot flash boot patched.img" but every time I do that and reboot, I get the 1+ splash screen and then nothing, black screen. If I boot back in bootloader and flash the original boot image via "fastboot flash boot original.img" it boots again. Same happens if I just run "fastboot boot patched.img", completely black until I reboot. Does anyone know what could be going wrong here?
Is there any way to install TWRP and make a NAND backup with this ROM? I've been out of the game for a while and I'm confused about why there's no recovery partition but there's A and B partitions, and I keep reading that TWRP can't decrypt data or something like that (I'm pretty sure it could 3 years ago tho)
Thanks!
I would never switch to an iphone for a personal phone because I can't stand it.
I have'nt had to root op7 pro till now because I had enough options. now with support ending I'm on 12.
If you have already upgraded to 12 like me you will probably have to downgrade to 11 first to unlock the bootloader if you haven't unlocked it already. I will not try till may when I get back from my vacation because I can't afford for the phone to go crazy right now. before you attempt to downgrade if you do make sure you back up everything to another spare phone or tablet and make sure you have a backup plan in case you soft brick before you attempt it. https://droidwin.com/downgrade-oneplus-7-7t-7t-pro-android-12-to-android-11-2-methods/ . Man if there is a new way to not have to first downgrade to android 11 someone please chime in, as it would reduce my headaches. Also I need someone to clarify if after I unlock the bootloader, I'll have to flash back to 12 via twrp and reformat the phone again to install Pixel experience?
dragancla said:
boot image in that link
Click to expand...
Click to collapse
That is probably where the problem is.
Which boot image to use depends on exactly which OS version you’re using, and the exact model number of your device.
A lot has changed in the Android world in the last 3 years.
TheMystic said:
That is probably where the problem is.
Which boot image to use depends on exactly which OS version you’re using, and the exact model number of your device.
A lot has changed in the Android world in the last 3 years.
Click to expand...
Click to collapse
Yeah, but that IS the boot image for that OS version and that device, that's why you can download both the ROM and the boot image for that ROM from the same link I posted. If I boot that specific image the device works fine. If I patch that same boot image and boot it, it doesn't work.
dragancla said:
Yeah, but that IS the boot image for that OS version and that device, that's why you can download both the ROM and the boot image for that ROM from the same link I posted. If I boot that specific image the device works fine. If I patch that same boot image and boot it, it doesn't work.
Click to expand...
Click to collapse
Then it means that the patching is not happening properly. Something is not right with the patched image, even if you don't get any errors. Search for this problem on Google. Also see if you can extract the boot image of your device yourself, instead of using the one you have in that link.
billperrotta said:
I would never switch to an iphone for a personal phone because I can't stand it.
I have'nt had to root op7 pro till now because I had enough options. now with support ending I'm on 12.
If you have already upgraded to 12 like me you will probably have to downgrade to 11 first to unlock the bootloader if you haven't unlocked it already. I will not try till may when I get back from my vacation because I can't afford for the phone to go crazy right now. before you attempt to downgrade if you do make sure you back up everything to another spare phone or tablet and make sure you have a backup plan in case you soft brick before you attempt it. https://droidwin.com/downgrade-oneplus-7-7t-7t-pro-android-12-to-android-11-2-methods/ . Man if there is a new way to not have to first downgrade to android 11 someone please chime in, as it would reduce my headaches. Also I need someone to clarify if after I unlock the bootloader, I'll have to flash back to 12 via twrp and reformat the phone again to install Pixel experience?
Click to expand...
Click to collapse
I already have Pixel Experience installed, so my bootloader is unlocked. Has been since I bought the phone 3 years ago
TheMystic said:
Then it means that the patching is not happening properly. Something is not right with the patched image, even if you don't get any errors. Search for this problem on Google. Also see if you can extract the boot image of your device yourself, instead of using the one you have in that link.
Click to expand...
Click to collapse
Google yielded no results, decided to post here to see if anyone else ran into this, I'll try to extract it myself somehow.
Coming out of left field but maybe you need to return to stock with bootloader unlocked. Flash 12 ota then rewipe for PE to get 12 latest firmware? https://www.xda-developers.com/oneplus-7-7t-end-of-life-final-update/
used to flash otas through TWRP when I had a rooted op5T with an unlocked bootloader. So Sad, Oxygen was so good till this last crummy update. Now they are forcing my hand to return to custom roms since OP insists on abandoning Support for the best phone they ever made.
Nothing worked, so I fixed it by wiping the phone and starting from scratch. Guess something bugged out.
thats usually the end all solution. but I have seen situations where you have to be on latest stock firmware to continue. I assume you don't have to copy any partitions because this software is already past Android 10 where treble was first introduced? I'm just asking as many questions as possible because I'm planning to overhaul in may. Did you use the pixel experience flashing instructions from pixel experience.org?
ill probably flash the ota back to twelve through twrp. then flash pixel experience recovery over that when I wipe and start over after the downgrade and bootloader unlock.
billperrotta said:
thats usually the end all solution. but I have seen situations where you have to be on latest stock firmware to continue. I assume you don't have to copy any partitions because this software is already past Android 10 where treble was first introduced? I'm just asking as many questions as possible because I'm planning to overhaul in may. Did you use the pixel experience flashing instructions from pixel experience.org?
Click to expand...
Click to collapse
I was on latest stock (12) before I started doing this. Had my bootloader unlocked since Android 9. Since it's impossible to do anything without unlocking it, that's your first step. I posted the link to PE website in my first post. Didn't copy any partitions. I just installed it and rooted it with a few commands from terminal (with the phone connected):
adb reboot bootloader
fastboot flash boot BOOT.img
fastboot reboot recovery
-- on the phone: wipe data, select install from sideload --
adb sideload ROM.zip
adb reboot
-- on the phone: wait for it to boot, enable developer options --
adb install MAGISK.apk
adb push BOOT.img sdcard/Download
-- on the phone: patch the boot image with Magisk --
adb pull sdcard/Download/magisk_patched-25200_xxxxx.img
adb reboot bootloader
fastboot flash boot magisk_patched-25200_xxxxx.img
fastboot reboot
That's it, installed and rooted. Stop at step 6 if you don't want root.