I am trying to restore my pixel to factory stock, i unrooted and relocked bootloader. but now i am trying flash the factory image, using flash-all.bat but it complains about no recovery.img or recovery.sig, etc.
what can i do, please help
I had this problem for a while. Relocking the BL wasn't required. Make sure you have the latest SDK and Fastboot from Google. I also had to factory reset to get it to finally restore.
FernBch said:
I had this problem for a while. Relocking the BL wasn't required. Make sure you have the latest SDK and Fastboot from Google. I also had to factory reset to get it to finally restore.
Click to expand...
Click to collapse
wait, so what i do is flash-all.bat, the bootloader is unlocked, can you tell me the steps of what you did to get it working? thanks
I downloaded the latest N and SDK from Google for my device from here and put it in a folder on my desktop (easier to find).
https://developers.google.com/android/images
I extracted the zip and placed all the files in the same folder as the platform tools (too lazy to edit the path statement in Windows).
Factory reset my device from settings (I was coming from PN) and just ran the flash-all.bat (from a command prompt window). I wasn't concerned about not wiping data because I'm trying to get to the bottom of an unrelated issue so I didn't remove the -w from the zip. I haven't made the jump to O yet because of battery life complaints. When I was done I booted to NHG47Q (Verizon) and my BL is still unlocked. Of course if you want TWRP, root, etc. You have to flash them again, just be sure to boot the system once before you install them.
thrgk said:
I am trying to restore my pixel to factory stock, i unrooted and relocked bootloader. but now i am trying flash the factory image, using flash-all.bat but it complains about no recovery.img or recovery.sig, etc.
what can i do, please help
Click to expand...
Click to collapse
The error sort of makes sense because there really is not a recovery image to flash. How long have you waited after getting those errors? It may take a few, or even 15 or so minutes before your computer gets over it and continues. My old laptop took closer to 15 but my new one is much faster.
It won't take 15 but just walk away and then come back. It'll complete on its own.
Sent from my Pixel using XDA-Developers Legacy app
Why i can't turn on oem unlocking
iamshovonmandal said:
Why i can't turn on oem unlocking
Click to expand...
Click to collapse
Verizon phone on 7.1.1 or higher? You can't, its locked.
Isn't there any way?
If you have a Google Play edition unlocking the BL is simple.
If you have a Verizon Bought Pixel and it is running any version later than 7.1.0 you cannot unlock the bootloader. Period. Verizon closed the exploit that allowed BL unlocking with the 7.1.1 release. There is no method available, no one is looking for another vulnerability, it's just not going to happen.
Sorry
Related
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
Do you have a custom recovery or flashed a kernel? You must be 100% stock
Sent from my Nexus 5 using XDA Free mobile app
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
eatcyanide said:
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
Click to expand...
Click to collapse
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
rahul9five said:
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
Click to expand...
Click to collapse
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
wantabe said:
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
Click to expand...
Click to collapse
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
rahul9five said:
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
Click to expand...
Click to collapse
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
wantabe said:
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
Click to expand...
Click to collapse
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
rahul9five said:
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
Click to expand...
Click to collapse
Flashing the factory image or a system image will always unroot your device. Lock the bootloader using the sdk. The command is fastboot oem lock.
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Yea, you can't flash the ota through a custom recovery anymore
Sent from my Nexus 9 using XDA Free mobile app
beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
rahul9five said:
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
Click to expand...
Click to collapse
Err... I didn't suggest that you flash a custom ROM. Read what I said.
I was running the latest Beta version, DP3 ut I was having all sorts of issues. Went to opt out of beta program, but did not receive an OTA for over a week, so I decided to revert back to 7.1.2 manually. I went through the whole process, unlocked my bootloader, flashed the bootloader.img file, flashed the radios, but when I got to flashing the factory image zip file, I'm getting an Error. Falied to load [name of file]. Not Enough Space.
What could be wrong here? How can I get the factory image to flash? Any help would be appreciated.
NickPorter said:
I was running the latest Beta version, DP3 ut I was having all sorts of issues. Went to opt out of beta program, but did not receive an OTA for over a week, so I decided to revert back to 7.1.2 manually. I went through the whole process, unlocked my bootloader, flashed the bootloader.img file, flashed the radios, but when I got to flashing the factory image zip file, I'm getting an Error. Falied to load [name of file]. Not Enough Space.
What could be wrong here? How can I get the factory image to flash? Any help would be appreciated.
Click to expand...
Click to collapse
Now, relock the bootloader, unlock it again.
Download full 7.12 image
Unzip to where Android SDK locates
Run fastboot flash-all
Wait to end
bush911 said:
Now, relock the bootloader, unlock it again.
Download full 7.12 image
Unzip to where Android SDK locates
Run fastboot flash-all
Wait to end
Click to expand...
Click to collapse
Is this something I would be able to do from a command prompt? That's what I have been doing. I am able to access fastboot, i.e. I can [fastboot reboot-bootloader] and it works on my device. Thanks.
Damn, you shouldn't relock the bootloader. ??
You don't even need to opt in/out, just flash all
Sent from my Pixel using XDA-Developers Legacy app
piperx said:
Damn, you shouldn't relock the bootloader. ?
You don't even need to opt in/out, just flash all
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
I just attempted the flash-all method, everything seemed to go smoothly but, once again, when it came to flashing the system image, Error: not enough space...
NickPorter said:
I just attempted the flash-all method, everything seemed to go smoothly but, once again, when it came to flashing the system image, Error: not enough space...
Click to expand...
Click to collapse
You are using the wrong version of fastboot. Get it from google.
https://developer.android.com/studio/releases/platform-tools.html
And yea, NEVER relock the bootloader unless you are about to put it in a box and send it in for warranty. That is horrible advice.
TonikJDK said:
You are using the wrong version of fastboot. Get it from google.
https://developer.android.com/studio/releases/platform-tools.html
And yea, NEVER relock the bootloader unless you are about to put it in a box and send it in for warranty. That is horrible advice.
Click to expand...
Click to collapse
I'm not familiar with Android SDK much at all, I have it installed. Where do I begin? Any help would be great.
I don't know about windows, but in linux you don't need android sdk, or driver's, it just works, someone that uses that other operating system will chime in
Sent from my Pixel using XDA-Developers Legacy app
Does anyone have a way I can back out of this process at the very least? My bootloader is unlocked and bootloader.img and radios have been flashed to my device. Since I cannot flash the system image, I know the phone will not boot if I leave the bootloader menu.
Let me preface this by saying I'm an idiot, I know just enough to be dangerous. Rooted and I wanted to restore and relock the bootloader. Instead of flashing the factory image first, I skipped that step and relocked the bootloader thinking it would wipe everything anyway. Of course now I realize I'm an idiot and I should not have skipped that step. Now I am soft bricked in the bootloader, and nothing will flash properly. Pretty sure I damaged the bootloader.
So my plea for help is, is there any way to repair or restore the bootloader?
I'm pretty sure as long as you can get into fastboot you can run the flash all bat.
You will have to download and extract the full factory image tho...and it should be like starting from fresh.oem
Also if you just wanted to flash a new bootloader you would just have to make sure it was the one extracted from the factory image you were already on.
noXcape said:
I'm pretty sure as long as you can get into fastboot you can run the flash all bat.
You will have to download and extract the full factory image tho...and it should be like starting from fresh.oem
Also if you just wanted to flash a new bootloader you would just have to make sure it was the one extracted from the factory image you were already on.
Click to expand...
Click to collapse
Well I've tried flash-all multiple times, it runs almost as normal except for one fail in the script (I'll show a pic of that after I go home and try again), and finishes as though it worked but when it reboots it can't get past bootloader. I'll try flashing the bootloader separately too.
Plus whenever I lock or unlock bootloader now it goes through the motion and then says "locked" or "unlocked" but it's faster than it should be and doesn't do that wiping animation at all.
Might be time to delete the old factory images and redownload new stuff
noXcape said:
Might be time to delete the old factory images and redownload new stuff
Click to expand...
Click to collapse
Already using the most recent, been playing around with that twrp beta, magisk, and v4a
Are you on current fastboot/adb?
cntryby429 said:
Are you on current fastboot/adb?
Click to expand...
Click to collapse
I think so, I downloaded it fresh a few weeks ago
trhacker01 said:
I think so, I downloaded it fresh a few weeks ago
Click to expand...
Click to collapse
Check again, I think a new version (late October) is in the most recent package.
I ran into the "stuck in bootloader" issue earlier today after running flash-all, but got out of it using some script by someone named Deuce that flashes the images one by one. I'll try and find a link.
Edit: here it is. This worked for me. Read carefully - you have to unzip the factory image that you've downloaded, then unzip the zip file that's in THAT zip.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
JayBlack_686 said:
Check again, I think a new version (late October) is in the most recent package.
I ran into the "stuck in bootloader" issue earlier today after running flash-all, but got out of it using some script by someone named Deuce that flashes the images one by one. I'll try and find a link.
Edit: here it is. This worked for me. Read carefully - you have to unzip the factory image that you've downloaded, then unzip the zip file that's in THAT zip.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Trying this now but still not working for me. Everytime where it fails is writing the bootloader, and everything else works fine. The bootloader writing fails in this deuce script, the regular flash-all, and flashing the bootloader separately.
Attached pics, 2 during deuce script, one during flash-all, and one during separate bootloader flash.
trhacker01 said:
Trying this now but still not working for me. Everytime where it fails is writing the bootloader, and everything else works fine. The bootloader writing fails in this deuce script, the regular flash-all, and flashing the bootloader separately.
Attached pics, 2 during deuce script, one during flash-all, and one during separate bootloader flash.
Click to expand...
Click to collapse
Sorry to hear that. I also got a bunch of failures during the process, and I don't think it automatically rebooted at the end of the process, but it ended up working on the first try (I was shocked when it did, since I saw so many failure warnings). He says in the thread that if it doesn't work, try formatting user data when prompted...I didn't have to, but may be worth a try, since you expected everything to be wiped anyway. Good luck.
trhacker01 said:
Trying this now but still not working for me. Everytime where it fails is writing the bootloader, and everything else works fine. The bootloader writing fails in this deuce script, the regular flash-all, and flashing the bootloader separately.
Attached pics, 2 during deuce script, one during flash-all, and one during separate bootloader flash.
Click to expand...
Click to collapse
A locked boot loader means you can't flash anything, that's the point. You can still flash an OTA.zip if you can get into stock recovery (you can still side load it in stock recovery I believe). Otherwise, you'll need to unlock the boot loader, and if it won't, and you can't get into Android to allow unlocking, then I'm not sure what, if anything, you can do.
Sent from my Pixel 2 using Tapatalk
danaff37 said:
A locked boot loader means you can't flash anything, that's the point. You can still flash an OTA.zip if you can get into stock recovery (you can still side load it in stock recovery I believe). Otherwise, you'll need to unlock the boot loader, and if it won't, and you can't get into Android to allow unlocking, then I'm not sure what, if anything, you can do.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Exactly.
At this point I'd try sideloading the latest ota.zip. If that doesn't work, I'd consider calling support and telling them your phone won't boot, without mentioning how you got there.
foosion said:
Exactly.
At this point I'd try sideloading the latest ota.zip. If that doesn't work, I'd consider calling support and telling them your phone won't boot, without mentioning how you got there.
Click to expand...
Click to collapse
yeah, good point. If I remember correctly, the Deuce script prompts you to unlock the bootloader at the beginning of the process - have you done that?
JayBlack_686 said:
yeah, good point. If I remember correctly, the Deuce script prompts you to unlock the bootloader at the beginning of the process - have you done that?
Click to expand...
Click to collapse
Yes, it's unlocked whenever trying to flash deuce or anything else. That's one of the strange things actually, it will respond to locking and unlocking, but it goes too quickly, skipping the process of wiping. Yeah I think I might be out of luck on this one.
JayBlack_686 said:
Sorry to hear that. I also got a bunch of failures during the process, and I don't think it automatically rebooted at the end of the process, but it ended up working on the first try (I was shocked when it did, since I saw so many failure warnings). He says in the thread that if it doesn't work, try formatting user data when prompted...I didn't have to, but may be worth a try, since you expected everything to be wiped anyway. Good luck.
Click to expand...
Click to collapse
Yeah I formatted to no avail.
Btw I ran out of my daily thanks, I'll continue as I get more. Thank you all very much for bothering to help me with this!
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.
Can I use TWRP to reformat my memory and reinstall stock? I had Grapheneos installed, decided to go back to stock. Even though I followed the instructions for uninstall, If I flash stock ROM I get bricked. If I flash latest ota, my phone boots up and restores OK, but I can't re- lock OEM lock (grayed out) If I try the same things on slot B neither one will boot. So I am thinking maybe Graphene reformatted something? It's been years since I messed with this stuff, back when android would let me install viper4android! I rescued my Moto x4 several times and still have it running as a music streamer. Not so easy on Pixel 6a. I don't really want to root right now, I have considered Lineage, but would just like to get back to stock with OEM locked for now. BTW latest android 13
LankiCat said:
Can I use TWRP to reformat my memory and reinstall stock? I had Grapheneos installed, decided to go back to stock. Even though I followed the instructions for uninstall, If I flash stock ROM I get bricked. If I flash latest ota, my phone boots up and restores OK, but I can't re- lock OEM lock (grayed out) If I try the same things on slot B neither one will boot. So I am thinking maybe Graphene reformatted something? It's been years since I messed with this stuff, back when android would let me install viper4android! I rescued my Moto x4 several times and still have it running as a music streamer. Not so easy on Pixel 6a. I don't really want to root right now, I have considered Lineage, but would just like to get back to stock with OEM locked for now. BTW latest android 13
Click to expand...
Click to collapse
There is no TWRP for this device. To get back to stock and re-lock your bootloader you can try Android Flash Tool or Pixel Flasher.
LankiCat said:
Can I use TWRP to reformat my memory and reinstall stock?
Click to expand...
Click to collapse
No, you can't use TWRP
What means brick? Bootloop or dead phone?
Did you erase the GrapheneOS Android Verified Boot key before you went back to stock?
GrapheneOS CLI install guide
Command-line installation instructions for GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
grapheneos.org
At the bottom of the articel is described how to erase the key.
WoKoschekk said:
No, you can't use TWRP
What means brick? Bootloop or dead phone?
Click to expand...
Click to collapse
I starts to boot, then it goes to white Google screen and stays there until I force it to reboot.
WoKoschekk said:
At the bottom of the articel is described how to erase the key.
Click to expand...
Click to collapse
WoKoschekk said:
At the bottom of the articel is described how to erase the key.
Click to expand...
Click to collapse
I'm not 100 percent sure I did that. Is there way to do it if I didn't? Re-install and then uninstall Graphene again? Or just try Android Flash Tool or Pixel Flasher as Lughnasadh suggested?
LankiCat said:
I'm not 100 percent sure I did that. Is there way to do it if I didn't? Re-install and then uninstall Graphene again? Or just try Android Flash Tool or Pixel Flasher as Lughnasadh suggested?
Click to expand...
Click to collapse
It's described on that page. Just do what the say and all is fine.
It's just one fastboot command. Thereis no reason to find a workaround or sth.
WoKoschekk said:
It's described on that page. Just do what the say and all is fine.
Click to expand...
Click to collapse
I really appreaciate the help, but, the page says: Before flashing the stock factory images and before locking the bootloader, you should erase the custom Android Verified Boot key to untrust it. Since I have already flashed the factory stock image I want to be sure that will work and not cause more problems. It takes a really long time to flash stock with all the setup, updates, restore, and re-loading apps to get back where i need to be. Thanks again for you input.
LankiCat said:
Since I have already flashed the factory stock image
Click to expand...
Click to collapse
Then it is no longer necessary to delete this key or it has already been removed before. The only job of that key is to verify the device before something gets flashed.
Does your phone still stops booting?
WoKoschekk said:
Then it is no longer necessary to delete this key or it has already been removed before. The only job of that key is to verify the device before something gets flashed.
Does your phone still stops booting?
Click to expand...
Click to collapse
No, It's running. The original problem was it locked up when I flashed factory image, once I was able to get it to recovery, I sideloaded the OTA and that worked to get it up and running. Just no OEM lock -greyed out
OK I decided to try the Graphene cutom key erase. CLI said it was successful but as I suspected OEM still greyed out as "Bootloader is already unlocked"
LankiCat said:
No, It's running. The original problem was it locked up when I flashed factory image, once I was able to get it to recovery, I sideloaded the OTA and that worked to get it up and running. Just no OEM lock -greyed out
OK I decided to try the Graphene cutom key erase. CLI said it was successful but as I suspected OEM still greyed out as "Bootloader is already unlocked"
Click to expand...
Click to collapse
Then run fastboot flashing lock
WoKoschekk said:
Then run fastboot flashing lock
Click to expand...
Click to collapse
yeah, tried that too. I'm going to have to wait until this weekend when I can afford some downtime on my phone.