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.
Related
I'm new to rooting and android in general. I'm currently running 4.4 rooted with stock I believe. Says ponury kernal in my settings.
I'm trying to flash the update for 4.4.2 via the TWRP install. I get a failed error: error executing updater binary in zip.
I've made sure my zip is the 4.4 to 4.4.2 but still no luck. Any ideas what I can do? Do I need to wipe something before I can put it on there?
On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful
tom1807 said:
On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful
Click to expand...
Click to collapse
The error was : error executing updater binary in zip. I will look into getting back to stock.
matthewordie said:
The error was : error executing updater binary in zip. I will look into getting back to stock.
Click to expand...
Click to collapse
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update
jd1639 said:
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update
Click to expand...
Click to collapse
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.
matthewordie said:
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.
Click to expand...
Click to collapse
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format
jd1639 said:
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format
Click to expand...
Click to collapse
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.
matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
Flashing the system image won't wipe anything
http://forum.xda-developers.com/showthread.php?p=14
Sent from my Nexus 5 using Tapatalk
Zepius said:
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.
Click to expand...
Click to collapse
Well I really don't know the exact steps involved in "flashing the image". That's what I'm asking.
jd1639 said:
Flashing the system image won't wipe anything
Click to expand...
Click to collapse
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?
matthewordie said:
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?
Click to expand...
Click to collapse
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it
jd1639 said:
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it
Click to expand...
Click to collapse
Ah, I was close I actually did method 1. Yeah I did leave it unlocked since i'm going to root again right away. Thanks
Hey group mates please help me
I'm currently using a nexus 5 and thought of sideloading the ota zip through nexus root toolkit so i first flashed stock recovery and then when i tried to sideload it, it started flashing till it reached 61% and which my phone said installation aborted for no reason.. Tried this more than 3-4 times but the result were all the same
I'm not sure what seems to be the issue here so it would be great if any one could help me solve this issue
Thanks in advance
drunken monkey said:
Hey group mates please help me
I'm currently using a nexus 5 and thought of sideloading the ota zip through nexus root toolkit so i first flashed stock recovery and then when i tried to sideload it, it started flashing till it reached 61% and which my phone said installation aborted for no reason.. Tried this more than 3-4 times but the result were all the same
I'm not sure what seems to be the issue here so it would be great if any one could help me solve this issue
Thanks in advance
Click to expand...
Click to collapse
Are you rooted or having custom kernel?
kaushikd said:
Are you rooted or having custom kernel?
Click to expand...
Click to collapse
I'm currently running stock recovery, stock os rooted and unlocked bootloader
I have the exact same problem. The sideload gets to 61%, then shows the following message:
"/system/bin/install-recovery.sh" has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
I have a stock recovery, was rooted using Chainfire's first method for Lollipop (patched kernel) but flashed the stock kernel (fastboot flash boot boot.img) from the N5 5.0 image before the sideload.
drunken monkey said:
I'm currently running stock recovery, stock os rooted and unlocked bootloader
Click to expand...
Click to collapse
You can't be rooted to use the OTA. Anything that is modified in the system will cause this.
I downloaded the full image and extracted just the radio, system and boot image files. Then just a few fastboot commands with bootloader reboots inbetween and 5.0.1 works.
For reference, I used the following:
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash boot boot.img
So while sideloading it should I unroot as well?
jsgraphicart said:
You can't be rooted to use the OTA. Anything that is modified in the system will cause this.
Click to expand...
Click to collapse
So to sideload I have to be in complete stock without even SuperSU.. Is that correct?
drunken monkey said:
So to sideload I have to be in complete stock without even SuperSU.. Is that correct?
Click to expand...
Click to collapse
That correct
Sent from my Nexus 5 using XDA Free mobile app
pauleyc said:
I downloaded the full image and extracted just the radio, system and boot image files. Then just a few fastboot commands with bootloader reboots inbetween and 5.0.1 works.
For reference, I used the following:
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash boot boot.img
Click to expand...
Click to collapse
I was thinking about doing this, too... but am I correct to assume that this would cause data loss? I have TWRP and SuperSU installed at the moment.
Or, if there's an easy way to ditch these and do the OTA, I'd be okay with that, too.
jrronimo said:
I was thinking about doing this, too... but am I correct to assume that this would cause data loss? I have TWRP and SuperSU installed at the moment.
Or, if there's an easy way to ditch these and do the OTA, I'd be okay with that, too.
Click to expand...
Click to collapse
It won't cause any data loss. It's about the only way to get the ota to work. But in your case, since you have twrp you should also flash the stock recovery.img
Sent from my Nexus 5 using XDA Free mobile app
No data loss (well, apart from root) if you flash just the radio, system and boot images. Worked great for me.
Thanks for the tips, guys. After extracting the full 5.0.1 firmware from the Factory Images page, there are system and boot .img files, but no radio. Is this normal?
jrronimo said:
Thanks for the tips, guys. After extracting the full 5.0.1 firmware from the Factory Images page, there are system and boot .img files, but no radio. Is this normal?
Click to expand...
Click to collapse
There's a radio. It's in the first file you extracted, not the zip you also had to extract
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
There's a radio. It's in the first file you extracted, not the zip you also had to extract
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Good thing I didn't get past this step -- I had downloaded the wrong factory image. D: That'll explain things a bit...
---------- Post added at 02:13 PM ---------- Previous post was at 01:54 PM ----------
Alrighty! New problem: After the phone boots, I get the battery and signal icons in the top right, but a black screen otherwise. If I hit the power button to put it in sleep mode and then hit the power button again, I get a quick flash of the "Welcome to Android, select your language" screen. Any pro-tips?
If I have to set up from scratch, it's no big deal. Most of the important stuff should be backed up; it'd just be annoying. All that Desert Golfing progress!!!
Finally managed to get around it. Ended up updating TWRP and re-flashing most of the .imgs a bunch, then using TWRP to first let me back up data to my computer and then wipe partitions. I'm on 5.0.1 again.
Welp, that was painful, haha. I'm sure I did something wrong leading into this, but I'm not sure what that was...
If i just flash the whole Firmware that i downloaded from Google, will i be able to flash it and loose root?
I am OK with loosing root and beeing back to stock.
At this moment i have Lolipop 5.0 that is rooted with Chainfire.
I was running rooted stock 5.0 with TWRP and had already flashed the 5.0.1 radio, so I just fastboot flashed the 5.0.1 system.img and rerooted. All is well so far.
jd1639 said:
That correct
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So if I unroot and then sideload it will I loose all my data ?
P.s I'll be rooting it back immediately after I get 5.1
So is there any way which can avoid a data loss?
I still have a doubt, I saw rootjunky's video in which he sideload 5.1 to his nexus 7 using nrt..
Even I followed the same method but it didn't succeed for me
pauleyc said:
I have the exact same problem. The sideload gets to 61%, then shows the following message:
"/system/bin/install-recovery.sh" has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
I have a stock recovery, was rooted using Chainfire's first method for Lollipop (patched kernel) but flashed the stock kernel (fastboot flash boot boot.img) from the N5 5.0 image before the sideload.
Click to expand...
Click to collapse
So after flashing your stock kernal and stock recovery did the sideload work.. I mean that it didn't get stuck at the 61% mark?
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
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!
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.