I tried flash-all and it's not flashing a recovery. What's the special sauce for flashing the stock recovery image?
You could try fastboot. Install recovery that way. Should overwrite twrp
tcarave said:
You could try fastboot. Install recovery that way. Should overwrite twrp
Click to expand...
Click to collapse
Where does one find the factory recovery images? They aren't contained in the Factory zips.
measter said:
Where does one find the factory recovery images? They aren't contained in the Factory zips.
Click to expand...
Click to collapse
In a zip inside the zip. Boot.img
But I almost guarantee if you update to latest SDK Platform Tools thru android studio that flash-all will probably work..
Sent from my sailfish using XDA Labs
nednednerb said:
In a zip inside the zip. Boot.img
But I almost guarantee if you update to latest SDK Platform Tools thru android studio that flash-all will probably work..
Click to expand...
Click to collapse
It will work, as I've done it to return to stock
Sent from my Google Pixel XL using XDA Labs
measter said:
Where does one find the factory recovery images? They aren't contained in the Factory zips.
Click to expand...
Click to collapse
Go here > https://developers.google.com/android/images
Managed to get it back to stock with the Skipsoft toolkit. What is it that makes the toolkit different in the way it flashes the file versus the flash-all?
measter said:
Managed to get it back to stock with the Skipsoft toolkit. What is it that makes the toolkit different in the way it flashes the file versus the flash-all?
Click to expand...
Click to collapse
When I had my Nexus 6 I never used a toolkit. I'll probably never use one for my pixel either. The flash all is extremely efficient. I have heard people using toolkits before and them getting bricks because there bootloader locked and they couldn't unlock again and then they bootlooped. Edit: mostly because of Enable OEM Unlock button.
Related
I have modified the Yakju Galaxy Nexus factory images by completely wiping my Nexus, restoring using the factory images supplied by Google, rooting them and repacking the images with root intact.
After trying so many ROMs that are available, sometimes I think, especially considering the latest releases from Google, that stock is the way to go. Flashing it using these images is my preferred method, being the cleanest, and I have provided these for your convenience as I haven’t seen them anywhere else only ever seen flashable ROMs (i.e. from Recovery) based on the factory images, etc...
These are:
Factory Images “yakju” for Galaxy Nexus “maguro” (GSM/HSPA+)
Android 4.1.2 (JZO54K) with SU binary only
Android 4.1.2 (JZO54K) with SU binary and SuperSU app
Download links are here. MD5 and SHA1 sums are listed so you can check the downloads.
You have to use Fastboot to flash these to your device. The only requirement is that your device's bootloader is unlocked, which you can easily do, but be warned that this will wipe your user data as will flashing these factory images.
To Unlock Bootloader (in the terminal):
Code:
fastboot oem unlock
Unzip the factory image and just run the flash-all.sh in a Linux terminal or flash-all.bat in the Windows command line.
thanks 'mate! I'm gonna try this out in a bit last time I was on stock was still 4.1.1, and my current custom ROM is still on that version.
What are actually the differences of 4.1.1 and 4.1.2? Just thought you had any idea.. :cyclops:
In 4.1.2 I've noticed better battery life like others have reported and notifications can now be expanded and shrunk if you hold on them and drag up and down.
Sent from my Galaxy Nexus using Tapatalk 2
rhed said:
thanks 'mate! I'm gonna try this out in a bit last time I was on stock was still 4.1.1, and my current custom ROM is still on that version.
What are actually the differences of 4.1.1 and 4.1.2? Just thought you had any idea.. :cyclops:
Click to expand...
Click to collapse
Google the changelog..............
Gave you the fishing rod, fish yourself.
https://www.google.com.sg/search?q=...65784e5eeb7334&bpcl=35466521&biw=1360&bih=643
It would be really helpful if someone could help how to install this using a Mac?
Now that's more like it:good: People should start using fastboot more often other than toolkits:good:Learn to install drivers on your computer. Thanks for posting :highfive: I just hope people take the time and learn it..
harisn said:
It would be really helpful if someone could help how to install this using a Mac?
Click to expand...
Click to collapse
I'm not 100% sure as I have never used a Mac for that but there's a good guide here.
Hey, thanks for the links, just want to ask, if I'm already rooted and unlocked my bootloader, if I flash this via fastboot, will it erase my apps/internal memory/photos and such? Quite curious it's just the unlocking the bootloader that deletes all data. Will like inquiries. Thanks!
MoZuFi93 said:
Hey, thanks for the links, just want to ask, if I'm already rooted and unlocked my bootloader, if I flash this via fastboot, will it erase my apps/internal memory/photos and such? Quite curious it's just the unlocking the bootloader that deletes all data. Will like inquiries. Thanks!
Click to expand...
Click to collapse
If you just run the script as is, it will wipe everything. The best thing to do is just flash the system.img if you want to retain your data.
"fastboot flash system system.img"
Sent from my Galaxy Nexus using Tapatalk 2
chickenfeeder said:
If you just run the script as is, it will wipe everything. The best thing to do is just flash the system.img if you want to retain your data.
"fastboot flash system system.img"
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks a lot!
Encountered this error message when trying to manually flash the N Dev 3 image, not via the flash-all bat. I'm very familiar when it comes to flashing images on my devices, fwiw.
I tried rebooting my PC, redownloading the image, and updating SDK Tools. No luck.
I've been able to reflash to mtc19t successfully.
My goal was to upgrade to the N Dev 3, then flash the decrypted modified N boot.img from Tigerstown in order to root.
Your fastboot is out of date or you have a bad download.
Sent from my SM-G930V using Tapatalk
Thanks. I'll give this a shot [TOOL]Minimal ADB and Fastboot [4-27-16]:
http://forum.xda-developers.com/showthread.php?t=2317790
bostonirishguy13 said:
Encountered this error message when trying to manually flash the N Dev 3 image, not via the flash-all bat. I'm very familiar when it comes to flashing images on my devices, fwiw.
I tried rebooting my PC, redownloading the image, and updating SDK Tools. No luck.
I've been able to reflash to mtc19t successfully.
My goal was to upgrade to the N Dev 3, then flash the decrypted modified N boot.img from Tigerstown in order to root.
Click to expand...
Click to collapse
You don't need to decrypt or flash a modified boot.img in order to root.
bobby janow said:
You don't need to decrypt or flash a modified boot.img in order to root.
Click to expand...
Click to collapse
Should have mentioned I'd prefer TWRP, too.
I ended up not using the unencrypted boot.img and rooted with CF Autoroot.
had same issue use fastboot from latest sdk
Has anyone who has unlocked their bootloader successfully flashed a different factory image other than the image on their phone. I've tried numerous ways and have had no success after unlocking my bootloader. Thanks to anyone who may chime in
Sent from my Pixel XL using XDA-Developers mobile app
treIII said:
Has anyone who has unlocked their bootloader successfully flashed a different factory image other than the image on their phone. I've tried numerous ways and have had no success after unlocking my bootloader. Thanks to anyone who may chime in
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Could you be more specific about how you flashed (flash_all or each individual image file), and what happened? Error or what?
cam30era said:
Could you be more specific about how you flashed (flash_all or each individual image file), and what happened? Error or what?
Click to expand...
Click to collapse
I've tried flashing the entire P factory image and it fails. I've tried with adb and fast boot on my PC. I also tried with skipsoft toolkit to see if that would work. It also fails. I have posted screen shots in that thread if you'd like to see the error. Thanks
treIII said:
I've tried flashing the entire P factory image and it fails. I've tried with adb and fast boot on my PC. I also tried with skipsoft toolkit to see if that would work. It also fails. I have posted screen shots in that thread if you'd like to see the error. Thanks
Click to expand...
Click to collapse
I'd suggest fastboot flash each image file separately (boot, sys, etc)
cam30era said:
I'd suggest fastboot flash each image file separately (boot, sys, etc)
Click to expand...
Click to collapse
I tried that and it seems to work but nothing changes
treIII said:
I tried that and it seems to work but nothing changes
Click to expand...
Click to collapse
What is it that you are expecting to change?
cam30era said:
What is it that you are expecting to change?
Click to expand...
Click to collapse
The build number and for OEM unlocking to be pickable. My bootloader is already unlocked so I thought flashing a different factory image would make it possible in developer options
treIII said:
The build number and for OEM unlocking to be pickable. My bootloader is already unlocked so I thought flashing a different factory image would make it possible in developer options
Click to expand...
Click to collapse
I agree. That's very strange. Does fastboot indicate success after flashing each image?
cam30era said:
I agree. That's very strange. Does fastboot indicate success after flashing each image?
Click to expand...
Click to collapse
Yes for some but the system image fails. Look in skipsoft tool thread and you'll see it. There are pictures
treIII said:
Yes for some but the system image fails. Look in skipsoft tool thread and you'll see it. There are pictures
Click to expand...
Click to collapse
If you don't use skipsoft, and in fastboot do:
fastboot flash system system.img
You still get this partition error?
cam30era said:
If you don't use skipsoft, and in fastboot do:
fastboot flash system system.img
You still get this partition error?
Click to expand...
Click to collapse
Yes
treIII said:
Yes
Click to expand...
Click to collapse
Very strange. I'm at a loss.
cam30era said:
Very strange. I'm at a loss.
Click to expand...
Click to collapse
So u have Verizon version? I'd like to see someone else try to flash a factory image to know where this goes
treIII said:
So u have Verizon version? I'd like to see someone else try to flash a factory image to know where this goes
Click to expand...
Click to collapse
No. Considering buying one. That's why I'm interested in this.
cam30era said:
No. Considering buying one. That's why I'm interested in this.
Click to expand...
Click to collapse
Yeah I wish someone else would chime in and try. I can't figure it out after trying for 4 hours last night and about two today. So I gave up and posted
I flashed the google factory image. . oem unlock will stay greyed out but that is not a big deal. bunch of people did this and discussion in this other thread. http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497
zanoli99 said:
I flashed the google factory image. . oem unlock will stay greyed out but that is not a big deal. bunch of people did this and discussion in this other thread. http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497
Click to expand...
Click to collapse
Not until you want to update to newer firmwares and there is no unlock method on those bootloaders. Converting to a GPS Pixel would be ideal if it is even possible.
joderme said:
Not until you want to update to newer firmwares and there is no unlock method on those bootloaders. Converting to a GPS Pixel would be ideal if it is even possible.
Click to expand...
Click to collapse
If you unlock now and update later your bootloader will remained locked unless Google finds a way to push a bootloader update with the coming OTA's that locks your bootloader after unlocking but that's highly unlikely. Plus, if you jump the gun and install the OTA before knowing the results of the OTA, you're kind of asking for something like this to happen. Hopefully Google doesn't find a deceitful way of pushing bootloader updates to lock us back up as you know they have already learned that a backdoor was found to unlock the Verizon bootloaders. They're not stupid and Jcase already said the sunshine guys were sending the exploit to Google so they would patch it. Vulnerabilities are too common these days on Android and these exploit seekers are quick to submit patches for them.
OK. Finally was able to flash the latest pixel factory image on my PXL. Minimal and fastboot and latest drivers from Google.
i sorta need help in this department as well... do i unzip the zip inside the zip??
im getting missing recovery.img and missing boot.sig i would like to make this a non verizon device. the flash-all.bat didnt work and i tried modifying it by removing -w but still same errors. spoon feed me please or teamview? its been 2 days
Is it possible to obtain a flashable zip for the stock 7.1.1 ROM?
I'm running PureNexus as my primary ROM, but I would like to be able to flash the stock ROM as secondary ROM in multirom TWRP.
I guess it is possible. I wish someone will make it. lol. We only have debloated stock rom flashable via twrp as of now.
https://forum.xda-developers.com/showthread.php?t=3398617
Sent from my Nexus 5X using Tapatalk
Thank you very much.
That will suffice. I'm going to use it as a base ROM.
Lord_Flaya said:
Thank you very much.
That will suffice. I'm going to use it as a base ROM.
Click to expand...
Click to collapse
welcome ???
Sent from my Nexus 5X using Tapatalk
I was wondering if there is a flashable and up to date stock Oreo ROM. I searched but couldn't find one. I want to use xposed and want to update the rom through TWRP instead of flashing whole factory image and erasing all stuff. Debloated would be fine, too. Just no special featured added.
Sushi3110 said:
I was wondering if there is a flashable and up to date stock Oreo ROM. I searched but couldn't find one. I want to use xposed and want to update the rom through TWRP instead of flashing whole factory image and erasing all stuff. Debloated would be fine, too. Just no special featured added.
Click to expand...
Click to collapse
If you use the flash-all batch file to flash the factory image just go into the batch file and delete the -w paramater. Alternately you can flash each partition separately with fastboot.
To maintain twrp don't flash the recovery image. With any of this you'll have to root again.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
If you use the flash-all batch file to flash the factory image just go into the batch file and delete the -w paramater. Alternately you can flash each partition separately with fastboot.
To maintain twrp don't flash the recovery image. With any of this you'll have to root again.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Is it possible to update the system this way with encryption enabled?
Would it be possible to flash one of the full OTA images?
eg. https://dl.google.com/dl/android/aosp/bullhead-ota-opm4.171019.016.a1-510a2077.zip
(NB. This will probably replace your recovery with the stock one on the first boot after upgrading.)
If I flash the latest OTA via TWRP. That would get me back to Stock no? Then once booted I could remove my google account. Boot into fastboot then ADB lock the bootloader and that should be that. I'm I correct?
If the ota has a boot.img in it probably but I'm not positive
Sent from my Pixel 2 XL using Tapatalk
Yes it will. Twrp will be replaced (if you have it installed) with the stock recovery. But why do you want to lock the bootloader?
Edit, I just saw your other post. If you want to sell it I'd flash the factory image so it wipes your device. Then skip the Google setup and lock the bootloader.
Sent from my [device_name] using XDA-Developers Legacy app
Does flash-all with "-w" intact flash to both slots ? and then safe to relock the bootloader ? after make sure it boot alright first
Didit_Anshari said:
Does flash-all with "-w" intact flash to both slots ? and then safe to relock the bootloader ? after make sure it boot alright first
Click to expand...
Click to collapse
Yes it does. And then you'll be ok to lock I down :good:
jd1639 said:
Yes it will. Twrp will be replaced (if you have it installed) with the stock recovery. But why do you want to lock the bootloader?
Edit, I just saw your other post. If you want to sell it I'd flash the factory image so it wipes your device. Then skip the Google setup and lock the bootloader.
Click to expand...
Click to collapse
So just flash factory image via ADB? Saw a video where dude flashed radios, boot IMG. Ect. Seemed complex. Just the factory image will get me back to stock?
def-g said:
So just flash factory image via ADB? Saw a video where dude flashed radios, boot IMG. Ect. Seemed complex. Just the factory image will get me back to stock?
Click to expand...
Click to collapse
Just run the flash-all batch file.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Just run the flash-all batch file.
Click to expand...
Click to collapse
Gracias.