Database Develop

[Q] Nexus 6 Factory Images

I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.

GuardianUSMC said:
I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.
Click to expand...
Click to collapse
No, you cannot ad root to the image before flashing.
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.

gee2012 said:
No, you cannot ad root to the image before flashing.
Click to expand...
Click to collapse
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.
Click to expand...
Click to collapse
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.

GuardianUSMC said:
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.
Click to expand...
Click to collapse
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.

gee2012 said:
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.
Click to expand...
Click to collapse
Got it, thank you very much for your assistance.
Too bad the Factory Images from Google are not already rooted.

GuardianUSMC said:
So the factory images provided directly by Google are NOT at root already either?
Click to expand...
Click to collapse
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
So for example on a linux machine you will have the root directory:
/
Within root, you will have other directories such as:
/bin
/etc
/usr
See here for more information:
http://www.thegeekstuff.com/2010/09/linux-file-system-structure/
So root is kind of like the C:\ drive on a Windows PC. Everything to do with the OS and User directories are within there.
Your Android device is the same, however, /bin, /etc (etc) are not at the root of the device. They sit within the system partition, which sits within root. so /system/bin, /system/etc. When you flash a factory image, it flashes the images to /system, /cache, /userdata (and a few other places) where as the root of the device remains largely untouched.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.

@rootSU,
Excellent mini tutorial. I wish this could be stickied on the General roll up thread. Thank you very much.

rootSU said:
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
Click to expand...
Click to collapse
I appreciate that and forgive me I know I used the terms interchangeably and that's my bad.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
Click to expand...
Click to collapse
yes I am familiar with that and I was using the term to mean having root privileges, again my bad.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
Click to expand...
Click to collapse
Understood, I have done that and my device is currently rooted. I was more looking into making an image that is already rooted, to borrow a term from Windows, slipstream the root functionality pre-flashing. I was told not going to happen, that's fine. Although when I had my HTC Evo 4G, I had pre-rooted images that I had created with the bloat removed and I was flashing them with root functionality out of the box, but that's another story, I guess Nexus 6 is a different animal and dealing with Lollipop probably more difficult than Gingerbread.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.
Click to expand...
Click to collapse
No but I appreciate you taking the time, thank you.
Right now mostly I am frustrated with the fact that the factory images provided by google will not flash right and keep *****ing about missing .sig files. I have tried flashing them individually by taking the root, system, recovery images out of the zip file and doing them individually as been suggested all over the place but no luck there there, keeps *****ing about the partitions instead, makes no sense. The bootloader and radio images go through without a hitch but the rest is just a mess.

Just to share, I am trying to flash the factory image that I mentioned in my original post, so I won't repost it. Here is what did so far to no avail, so any assistance would be greatly appreciated:
I issue the command adb reboot bootloader and it successful reboots the phone into the bootloader
Extracting the folder shamu-lmy47i containing the following files:
bootloader-shamu-moto-apq8084-71.08.img
flash-all.bat
flash-all.sh
flash-base.sh
image-shamu-lmy47i.zip
radio-shamu-d4.0-9625-02.95.img
Opening the batch file you see the following (I have removed the copyright header for sake of brevity)
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy47i.zip
echo Press any key to exit...
pause >nul
exit
Since the only thing I want to add to this is root, I add this after the image update:
Code:
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
So we let it rip and this is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.548s]
finished. total time: 0.674s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.720s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.102s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
downloading 'boot.img'...
OKAY [ 0.393s]
booting...
OKAY [ 0.024s]
finished. total time: 0.419s
Press any key to exit...
As we can see, bootloader image flashes just fine
The radio image flashes just fine
System image on the other hand does not update complaining about missing .sig files:
fastboot -w update image-shamu-lmy47i.zip said:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
Click to expand...
Click to collapse
The files inside this system zip are:
android-info.txt
boot.img
cache.img
recovery.img
system.img
userdata.img
Ironically the SuperSU image flashes just fine and reboots the phone
I am frustrated by the fact that the system image update step fails and nothing out there explains why? I have even tried to extract each of those images from the zip file and flashing them individually using the fastboot flashall but getting the same error as well as other errors.
Can anyone lend an assist on this and help me figure out how to overcome that hurdle PLEASE?

Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.

Evolution_Freak said:
Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.
Click to expand...
Click to collapse
I did provide everything step by step the only thing I didn't provide was the errors on the individual images that are within the update zip file. Which I suppose is my bad:
Code:
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
and I have tried flashall last because documentation states it will do boot, recovery and system but I have also done them using individual commands too. But more on that after I take a look at what you posted in the link. Stay tuned. Thank you.

Alright, good news, it worked and thank you for pointing to the resource that allowed me to figure out why I was getting the partition errors, now I know.
I modified the batch file as follows:
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
adb reboot bootloader
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
echo Press any key to exit...
pause >nul
exit
it went through the whole process and here is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
< waiting for device >
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.508s]
finished. total time: 0.632s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.722s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.110s]
finished. total time: 3.834s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
target reported max download size of 536870912 bytes
sending sparse 'system' (522196 KB)...
OKAY [ 22.442s]
writing 'system'...
OKAY [ 7.691s]
sending sparse 'system' (510114 KB)...
OKAY [ 21.723s]
writing 'system'...
OKAY [ 6.674s]
sending sparse 'system' (514997 KB)...
OKAY [ 21.128s]
writing 'system'...
OKAY [ 7.778s]
sending sparse 'system' (189177 KB)...
OKAY [ 7.652s]
writing 'system'...
OKAY [ 2.328s]
finished. total time: 97.428s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 11.844s]
sending 'userdata' (138868 KB)...
OKAY [ 4.518s]
writing 'userdata'...
OKAY [ 1.949s]
finished. total time: 18.315s
target reported max download size of 536870912 bytes
sending 'boot' (7681 KB)...
OKAY [ 0.247s]
writing 'boot'...
OKAY [ 0.110s]
finished. total time: 0.359s
target reported max download size of 536870912 bytes
sending 'recovery' (8273 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.116s]
finished. total time: 0.384s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.045s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.013s]
sending 'cache' (6248 KB)...
OKAY [ 0.204s]
writing 'cache'...
OKAY [ 0.097s]
finished. total time: 0.318s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.399s]
booting...
OKAY [ 0.035s]
finished. total time: 0.436s
Thank you for everyone's input and assistance here, you rock.

Noob difficulty in flashing stock marshmallow

I'm having some difficulty flashing Marshmallow onto my Nexus 6. It is the first time I am flashing a rom onto this.
I'm running Linux for this. (Mint 17.2) as I ran into trouble with Windows 10 and OSX El Capitan and recognising my device.
I've got the rom unpacked but when I go to flash with flash-all.sh I get an error.
Code:
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 4.620s
It then dumps me back to the bootloader on the device. I did come across this thread from a while back.
http://forum.xda-developers.com/nexus-6/help/flash-factory-images-flashing-image-t2948624/page3
It hasn't resolved my problem. I've tried following the long method for installing the rom but it isn't working. I can't get the first stage to execute. I don't seem to actually have a file called bootloader.img anywhere. Is that the problem? Is it missing in this rom?
I'm perfectly happy to completely wipe the device. (It is only 3 days old) I just want to get the stock firmware up and running.

spudbynight said:
I'm having some difficulty flashing Marshmallow onto my Nexus 6. It is the first time I am flashing a rom onto this.
I'm running Linux for this. (Mint 17.2) as I ran into trouble with Windows 10 and OSX El Capitan and recognising my device.
I've got the rom unpacked but when I go to flash with flash-all.sh I get an error.
It then dumps me back to the bootloader on the device. I did come across this thread from a while back.
http://forum.xda-developers.com/nexus-6/help/flash-factory-images-flashing-image-t2948624/page3
It hasn't resolved my problem. I've tried following the long method for installing the rom but it isn't working. I can't get the first stage to execute. I don't seem to actually have a file called bootloader.img anywhere. Is that the problem? Is it missing in this rom?
I'm perfectly happy to completely wipe the device. (It is only 3 days old) I just want to get the stock firmware up and running.
Click to expand...
Click to collapse
Looks like your fastboot binary is out of date. Did you get it from the latest sdk?

I've downloaded the SDK, but (yes, noob alert) I can't figure out how to actually install it.
I've downloaded fastboot from the terminal and it says I have the latest version.

OK - I installed the SDK. I followed the instructions here
When attempting to flash it seems to go a little bit further but is still failing.
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.394s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.693s]
finished. total time: 1.087s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (115487 KB)...
OKAY [ 4.084s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.555s]
finished. total time: 5.639s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: moto-apq8084-71.15
Baseband Version.....: D4.01-9625-05.27+FSG-9625-02.104
Serial Number........: ZX1G425T8L
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (8197 KB)...
OKAY [ 0.269s]
writing 'boot'...
OKAY [ 0.125s]
sending 'recovery' (8915 KB)...
OKAY [ 0.300s]
writing 'recovery'...
OKAY [ 0.133s]
sending 'system' (2043261 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.841s
From there I went into the "long way" and flashed the files individually from system.img
I selected recovery and rebooted. I got an Android with a red triangle but held power and volume up. The phone rebooted without me being asked to wipe data/factory reset.
Currently booted up and restoring. How do I check this is stable? I want to make sure I get OTA updates...

So the bootloader and radio worked, then it failed. Is this using the flash-all script?
I'd try extracting the contents of image-shamu-mra58k.zip and flashing each of them manually with fastboot. I've had trouble like that when using the flash-all script.

KnifeSkills said:
So the bootloader and radio worked, then it failed. Is this using the flash-all script?
I'd try extracting the contents of image-shamu-mra58k.zip and flashing each of them manually with fastboot. I've had trouble like that when using the flash-all script.
Click to expand...
Click to collapse
Sorry, I edited my post with an update...

This seems to be working OK now on Marshmallow.
How do I ensure I get OTA updates from here? Do I need to lock the bootloader again?

spudbynight said:
This seems to be working OK now on Marshmallow.
How do I ensure I get OTA updates from here? Do I need to lock the bootloader again?
Click to expand...
Click to collapse
Nope. Just stay 100% stock. No root, no mods.

Cheers

Device Locked in fastboot even with unlocked bootloader

Hi,
I was trying to reflash everything on my phone and wipe. When I boot into fastboot and run fastboot -w, I get an error saying Download is not allowed on locked device. Im using platform tools 29.05.

ahsank128 said:
Hi,
I was trying to reflash everything on my phone and wipe. When I boot into fastboot and run fastboot -w, I get an error saying Download is not allowed on locked device. Im using platform tools 29.05.
Click to expand...
Click to collapse
Does the bootloader screen show unlocked?
Have you tried to run the flashing unlock again?

Mackay53 said:
Does the bootloader screen show unlocked?
Have you tried to run the flashing unlock again?
Click to expand...
Click to collapse
Okay, so I locked the bootloader, and unlocked it again. Successfully flashed. But I am geting the following message
"Erase successful, but not automatically formatting. File system type raw not supported"
I cant run the fastboot format (partition) command. I am on latest platform tools and latest factory image

ahsank128 said:
Okay, so I locked the bootloader, and unlocked it again. Successfully flashed. But I am geting the following message
"Erase successful, but not automatically formatting. File system type raw not supported"
I cant run the fastboot format (partition) command. I am on latest platform tools and latest factory image
Click to expand...
Click to collapse
Does your phone boot up? If so, I would check to see if your still getting good recognition from your pc. What does adb devices show when you enter that with your phone in transfer data mode?

Badger50 said:
Does your phone boot up? If so, I would check to see if your still getting good recognition from your pc. What does adb devices show when you enter that with your phone in transfer data mode?
Click to expand...
Click to collapse
Yes, the factory image gets flashed, but now everything seems to be on partition B as opposed to A. I believe everything was going to A when I first got the phone and did the unlock. ADB working fine, managed to root the phone. i enter ADB devices and shows serial. I can boot to fastboot. I wanted to see what would happen if I run fastboot flashing unlock again, and it said device is unlocked

ahsank128 said:
Yes, the factory image gets flashed, but now everything seems to be on partition B as opposed to A. I believe everything was going to A when I first got the phone and did the unlock. ADB working fine, managed to root the phone. i enter ADB devices and shows serial. I can boot to fastboot. I wanted to see what would happen if I run fastboot flashing unlock again, and it said device is unlocked
Click to expand...
Click to collapse
Well, then I guess all is well for you again. Just FYI going forward, when you fastboot the factory image without the -w, it only flashes to your active slot, whereas, if you leave the -w, it'll flash to both slots, but wipe your device. This is why when I update the factory images every month without the -w, I manually change slots so I get a full flash to both slots. Many think this is overkill, however, I have never had any wonky problems for the last 2+ years with my P2XL, and now my P4XL by using this methodology :good:

Badger50 said:
Well, then I guess all is well for you again. Just FYI going forward, when you fastboot the factory image without the -w, it only flashes to your active slot, whereas, if you leave the -w, it'll flash to both slots, but wipe your device. This is why when I update the factory images every month without the -w, I manually change slots so I get a full flash to both slots. Many think this is overkill, however, I have never had any wonky problems for the last 2+ years with my P2XL, and now my P4XL by using this methodology :good:
Click to expand...
Click to collapse
Right, but the thing is I left the -w in the bat file. Even so it only flashed to b, saying device is locked. I think there is some internal issue going. Im the same guy who cant get the blackenedmod script to run properly lol

ahsank128 said:
Right, but the thing is I left the -w in the bat file. Even so it only flashed to b, saying device is locked. I think there is some internal issue going. Im the same guy who cant get the blackenedmod script to run properly lol
Click to expand...
Click to collapse
I know who you are? At least your up and running again. But yeah, sounds like your internals might be a little wonky for sure. ?

Badger50 said:
I know who you are At least your up and running again. But yeah, sounds like your internals might be a little wonky for sure. ?
Click to expand...
Click to collapse
Any idea on the best way to completely wipe the internals and flash again? This would be easy with TWRP or custom recovery, but we've some time before that is made for Android10

ahsank128 said:
Any idea on the best way to completely wipe the internals and flash again? This would be easy with TWRP or custom recovery, but we've some time before that is made for Android10
Click to expand...
Click to collapse
Personally, I would factory reset from stock recovery, and then fastboot the factory image with the -w included. In essence, wiping everything twice :good:

Badger50 said:
Personally, I would factory reset from stock recovery, and then fastboot the factory image with the -w included. In essence, wiping everything twice :good:
Click to expand...
Click to collapse
Will attempt this, my attempt last night was to do factory reset within the settings (when phone is booted up) and then flashed with -w. But I will try again using the stock recovery. I even changed computers, this stuff is wonky sometimes

Badger50 said:
Personally, I would factory reset from stock recovery, and then fastboot the factory image with the -w included. In essence, wiping everything twice :good:
Click to expand...
Click to collapse
Code:
C:\Users\akhan37\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 5.477s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.203s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 6.178s
Also, hitting adb reboot fastboot takes to to fastbootd screen but I can't flash there (where I get the message can't write to locked device), but I can use flash-all bat from the bootloader screen.
Code:
Sending 'bootloader_b' (8761 KB) OKAY [ 0.349s]
Writing 'bootloader_b' (bootloader) Flashing Pack version c2f2-0.2-5940465
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition msadp_b
(bootloader) Flashing partition logfs
OKAY [ 0.435s]
Finished. Total time: 1.046s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
Sending 'radio_b' (82676 KB)

DELETED

ahsank128 said:
Also, hitting adb reboot fastboot takes to to fastbootd screen but I can't flash there (where I get the message can't write to locked device), but I can use flash-all bat from the bootloader screen.
Click to expand...
Click to collapse
Interesting. Just a simple experiment if your willing. Go into your platform-tools, and just double click the flash-all.bat file and see if you get the same result, or if it even initializes

ahsank128 said:
Code:
C:\Users\akhan37\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 5.477s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.203s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 6.178s
Also, hitting adb reboot fastboot takes to to fastbootd screen but I can't flash there (where I get the message can't write to locked device), but I can use flash-all bat from the bootloader screen.
Code:
Sending 'bootloader_b' (8761 KB) OKAY [ 0.349s]
Writing 'bootloader_b' (bootloader) Flashing Pack version c2f2-0.2-5940465
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition msadp_b
(bootloader) Flashing partition logfs
OKAY [ 0.435s]
Finished. Total time: 1.046s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
Sending 'radio_b' (82676 KB)
Click to expand...
Click to collapse
If you have done a factory reset, you also need to make sure you enable "oem unlocking" in Developer options and usb debugging before you do anything else. Flashing a factory stock image which includes the '-w' in your flash-all.bat file would come afterwards.
I am assuming you are not flashing any kernals on top? Check to make sure you are flashing the correct image, Nov and December had 3 different images each month.

Badger50 said:
Interesting. Just a simple experiment if your willing. Go into your platform-tools, and just double click the flash-all.bat file and see if you get the same result, or if it even initializes
Click to expand...
Click to collapse
Wont work from home screen (this is fine? should be in fastboot)
Looks like it flashed this time from the fastbootd screen (so damn strange)
from fastbootd screen:
Code:
Sending 'bootloader' (8761 KB) OKAY [ 0.218s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.004s
Sending 'radio_b' (82676 KB) OKAY [ 2.180s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g8150-00041-191016-B-5945070
(bootloader) Flashing partition modem_b
OKAY [ 0.650s]
Finished. Total time: 3.090s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.051s
--------------------------------------------
Bootloader Version...: c2f2-0.2-5940465
Baseband Version.....: g8150-00041-191016-B-5945070
Serial Number........: 99171FFAZ006J5
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.069s]
Checking 'version-bootloader' OKAY [ 0.069s]
Checking 'version-baseband' OKAY [ 0.068s]
Setting current slot to 'b' OKAY [ 0.077s]
extracting boot.img (64 MB) to disk... took 0.387s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.139s]
Writing 'boot_b' OKAY [ 0.455s]
extracting dtbo.img (8 MB) to disk... took 0.025s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.310s]
Writing 'dtbo_b' OKAY [ 0.117s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (8 KB) OKAY [ 0.138s]
Writing 'vbmeta_b' OKAY [ 0.072s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.101s]
Writing 'vbmeta_system_b' OKAY [ 0.072s]
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.069s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.006s]
Resizing 'product_b' OKAY [ 0.004s]
Resizing 'system_b' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.004s]
Resizing 'vendor_b' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.004s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (2127 MB) to disk... took 15.801s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.005s]
and got stuck there
One more thing: When on stock boot image, OEM Unlock frozen on bootloader already unlock. But after flashing magsik, I can switch between allow and not allow. This is normal?

bb709394 said:
If you have done a factory reset, you also need to make sure you enable "oem unlocking" in Developer options and usb debugging before you do anything else. Flashing a factory stock image which includes the '-w' in your flash-all.bat file would come afterwards.
I am assuming you are not flashing any kernals on top? Check to make sure you are flashing the correct image, Nov and December had 3 different images each month.
Click to expand...
Click to collapse
No, this issue happens on stock kernel. And yes USB debugging and OEM Unlock both are checked. I believe the image is correct. US Unlocked Pixel from google store. file ends in 011

ahsank128 said:
Wont work from home screen (this is fine? should be in fastboot)
Looks like it flashed this time from the fastbootd screen (so damn strange)
from fastbootd screen:
and got stuck there
One more thing: When on stock boot image, OEM Unlock frozen on bootloader already unlock. But after flashing magsik, I can switch between allow and not allow. This is normal?
Click to expand...
Click to collapse
Yes, it only works in fastboot mode.
I don't think it's strange at all. I've never come across the..fastboot -w..command that you were using, which is why I suggested what I did.
Sometimes it takes a while for the script to finish. You might no have been stuck per-se, but just not patient enough. December was a big update, so it takes a little longer.
Yes, this is normal for OEM unlocking while rooted.
So...are you up and running now?

Badger50 said:
Yes, it only works in fastboot mode.
I don't think it's strange at all. I've never come across the..fastboot -w..command that you were using, which is why I suggested what I did.
Sometimes it takes a while for the script to finish. You might no have been stuck per-se, but just not patient enough. December was a big update, so it takes a little longer.
Yes, this is normal for OEM unlocking while rooted.
So...are you up and running now?
Click to expand...
Click to collapse
I am up and running, I'll check to see if I can get that script running later on

ahsank128 said:
I am up and running, I'll check to see if I can get that script running later on
Click to expand...
Click to collapse
Kinda sounds like you already got the script to work

Development [OFFICIAL] BlissRoms 16 [Typhoon] [barbet][Android 13]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BlissRoms comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience.
Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customization's across all platforms you run Bliss on.
BlissRoms Barbet Download
BlissRoms Fastboot Images
BlissRoms Boot Image
​
Clean Flash (If coming from other Rom's/Stock)
- Download BlissRoms Factory zip
- Reboot to bootloader
- Run flash-all.sh (Linux) and flash-all.bat (Windows)
- Once flashing is complete reboot your device and wait until bliss boots
- #StayBlissful
Dirty Flash (If you where on BlissRom already!)
- Download Recovery boot.img from above download link.
- Reboot to bootloader and flash boot.img via fastboot using following command
Code:
fastboot flash --slot all boot boot.img
- Reboot to recovery
- Select Apply Update -> Apply Update from ADB to flash BlissRom zip and then run following command
Code:
adb sideload blissrom-zipfilename.zip
- Wait till installation is completed.
- Reboot
Wait for Bliss logo to show up....
#StayBlissful
Create Bug Report on our Issues Tracker
BlissRoms Github
BlissRoms Gerrit
Kernel Source
| Website | Blog | Docs
| Facebook | Twitter | Instagram | Telegram Group | Telegram Channel |
If someone wants to donate, please do so via this PayPal link
Thank you for using BlissRoms! And as always: #StayBlissful​

Cool, thank you for your job, finally we have ROM with lots of customization, tomorrow I will install it

jackeagle said:
BlissRoms comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience.
Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customization's across all platforms you run Bliss on.
BlissRoms barbet Download
BlissRoms Factory Image
​Clean Flash (If coming from other Rom's/Stock)
- Download BlissRoms Factory Images
- Download factory tar.gz and extract it and go to extracted folder.
- Reboot to bootloader
- Run flash-all.bat for Windows or flash-all.sh script if you are using Linux OS.
- Once flashing is complete reboot your device and wait until bliss boots
- #StayBlissful
Dirty Flash (If you where on BlissRom already!)
- Download Recovery boot.img from above download link.
- Reboot to bootloader and flash boot.img via fastboot using following command
Code:
fastboot flash --slot all boot boot.img
- Reboot to recovery
- Select Apply Update -> Apply Update from ADB to flash BlissRom zip and then run following command
Code:
adb sideload blissrom-zipfilename.zip
- Wait till installation is completed.
- Reboot and #StayBlissful
Create Bug Report on our Issues Tracker
BlissRoms Github
BlissRoms Gerrit
Kernel Source
| Website | Blog | Facebook | Twitter | Instagram | Telegram Group | Telegram Channel | Docs
If someone wants to donate, please do so via this PayPal link
Thank you for using BlissRoms! And as always: #StayBlissful​
Click to expand...
Click to collapse
Hello, how to install magisk?

i would probably just fastboot boot this twrp https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-barbet.4387057/ then adb sideload the magisk app or rename it to zip then sideload it.

rchris494 said:
i would probably just fastboot boot this twrp https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-barbet.4387057/ then adb sideload the magisk app or rename it to zip then sideload it.
Click to expand...
Click to collapse
Hello, so you mean to flash this ROM using TWRP as dirty flash? I thought use 1st option clean flash, I'm currently on linage os A12.

[email protected] said:
Hello, so you mean to flash this ROM using TWRP as dirty flash? I thought use 1st option clean flash, I'm currently on linage os A12.
Click to expand...
Click to collapse
to flash magisk. after you have installed it, by their method.

rchris494 said:
to flash magisk. after you have installed it, by their method.
Click to expand...
Click to collapse
ok, thank you, I will try

I got error when try to use flash-all.bat
After reboot, it still loading me to linage os
Code:
C:\Tools\Bliss-v15.6-barbet-OFFICIAL-gapps-20220622>flash-all.bat
Sending 'bootloader_b' (8762 KB) OKAY [ 0.321s]
Writing 'bootloader_b' (bootloader) Flashing Pack version b9-0.4-8351079
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition featenabler_b
(bootloader) Flashing partition logfs
OKAY [ 0.455s]
Finished. Total time: 0.971s
rebooting into bootloader OKAY [ 0.050s]
Finished. Total time: 0.050s
< waiting for any device >
Sending 'radio_b' (149796 KB) OKAY [ 3.563s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g7250-00202-220422-B-8489468
(bootloader) Flashing partition modem_b
OKAY [ 0.821s]
Finished. Total time: 4.830s
rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
< waiting for any device >
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: b9-0.4-8351079
Baseband Version.....: g7250-0020
Serial Number........: 17071
--------------------------------------------
Checking product OKAY [ 0.070s]
extracting boot.img (96 MB) to disk... took 0.490s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (16 MB) to disk... took 0.109s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
extracting product.img (1844 MB) to disk... took 14.879s
archive does not contain 'product.sig'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (991 MB) to disk... took 7.576s
extracting system_other.img (22 MB) to disk... took 0.211s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (764 MB) to disk... took 6.119s
archive does not contain 'vendor_other.img'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
Sending 'boot_b' (98304 KB) OKAY [ 2.313s]
Writing 'boot_b' OKAY [ 0.494s]
Sending 'dtbo_b' (16384 KB) OKAY [ 0.460s]
Writing 'dtbo_b' OKAY [ 0.133s]
Sending sparse 'product' 1/8 (262140 KB) OKAY [ 6.145s]
Writing sparse 'product' 1/8 FAILED (remote: 'Partition product not found')
Finished. Total time: 44.382s
Press any key to exit...

So I flashed it using 2nd method, by recovery and ADB. Using TWRP it failing, that can't mount some partitions
Code:
C:\Tools>adb sideload Bliss-v15.6-barbet-OFFICIAL-gapps-20220622.zip
* daemon not running; starting now at tcp:5037
* daemon started successfully
serving: 'Bliss-v15.6-barbet-OFFICIAL-gapps-20220622.zip' (~47%) adb: failed to read command: No error

@jackeagle BlissRoms Factory Image fails to install. i originally tried coming from pixel experience. then tried again after a fresh factory wipe. both had the same results. bootloader is unlocked & using platform-tools_r33.0.2-windows. any suggestions?
C:\htc>flash-all.bat
Sending 'bootloader_a' (8762 KB) OKAY [ 0.453s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b9-0.4-8351079
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition uefisecapp_a
(bootloader) Flashing partition featenabler_a
(bootloader) Flashing partition logfs
OKAY [ 0.266s]
Finished. Total time: 0.969s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
Sending 'radio_a' (149796 KB) OKAY [ 5.719s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g7250-00202-220422-B-8489468
(bootloader) Flashing partition modem_a
OKAY [ 0.531s]
Finished. Total time: 6.500s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
--------------------------------------------
Bootloader Version...: b9-0.4-8351079
Baseband Version.....: g7250-00202-220422-B-8489468
Serial Number........: 17121JECB0xxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.062s]
Setting current slot to 'a' OKAY [ 0.094s]
extracting boot.img (96 MB) to disk... took 0.297s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB) OKAY [ 3.812s]
Writing 'boot_a' OKAY [ 0.313s]
archive does not contain 'init_boot.img'
extracting dtbo.img (16 MB) to disk... took 0.062s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.734s]
Writing 'dtbo_a' OKAY [ 0.125s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (8 KB) OKAY [ 0.141s]
Writing 'vbmeta_a' OKAY [ 0.078s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.141s]
Writing 'vbmeta_system_a' OKAY [ 0.078s]
archive does not contain 'vbmeta_vendor.img'
extracting vendor_boot.img (96 MB) to disk... took 0.250s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (98304 KB) OKAY [ 3.828s]
Writing 'vendor_boot_a' OKAY [ 0.297s]
archive does not contain 'vendor_kernel_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.062s]
< waiting for any device >
Sending 'super' (4 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Press any key to exit...

rchris494 said:
@jackeagle BlissRoms Factory Image fails to install. i originally tried coming from pixel experience. then tried again after a fresh factory wipe. both had the same results. bootloader is unlocked & using platform-tools_r33.0.2-windows. any suggestions?
C:\htc>flash-all.bat
Sending 'bootloader_a' (8762 KB) OKAY [ 0.453s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b9-0.4-8351079
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition uefisecapp_a
(bootloader) Flashing partition featenabler_a
(bootloader) Flashing partition logfs
OKAY [ 0.266s]
Finished. Total time: 0.969s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
Sending 'radio_a' (149796 KB) OKAY [ 5.719s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g7250-00202-220422-B-8489468
(bootloader) Flashing partition modem_a
OKAY [ 0.531s]
Finished. Total time: 6.500s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
--------------------------------------------
Bootloader Version...: b9-0.4-8351079
Baseband Version.....: g7250-00202-220422-B-8489468
Serial Number........: 17121JECB0xxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.062s]
Setting current slot to 'a' OKAY [ 0.094s]
extracting boot.img (96 MB) to disk... took 0.297s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB) OKAY [ 3.812s]
Writing 'boot_a' OKAY [ 0.313s]
archive does not contain 'init_boot.img'
extracting dtbo.img (16 MB) to disk... took 0.062s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.734s]
Writing 'dtbo_a' OKAY [ 0.125s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (8 KB) OKAY [ 0.141s]
Writing 'vbmeta_a' OKAY [ 0.078s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.141s]
Writing 'vbmeta_system_a' OKAY [ 0.078s]
archive does not contain 'vbmeta_vendor.img'
extracting vendor_boot.img (96 MB) to disk... took 0.250s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (98304 KB) OKAY [ 3.828s]
Writing 'vendor_boot_a' OKAY [ 0.297s]
archive does not contain 'vendor_kernel_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.062s]
< waiting for any device >
Sending 'super' (4 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Press any key to exit...
Click to expand...
Click to collapse
Hi,
The install log says your device bootloader is locked that is why it failed to install. Unlock it properly and try.

[email protected] said:
I got error when try to use flash-all.bat
After reboot, it still loading me to linage os
Code:
C:\Tools\Bliss-v15.6-barbet-OFFICIAL-gapps-20220622>flash-all.bat
Sending 'bootloader_b' (8762 KB) OKAY [ 0.321s]
Writing 'bootloader_b' (bootloader) Flashing Pack version b9-0.4-8351079
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition featenabler_b
(bootloader) Flashing partition logfs
OKAY [ 0.455s]
Finished. Total time: 0.971s
rebooting into bootloader OKAY [ 0.050s]
Finished. Total time: 0.050s
< waiting for any device >
Sending 'radio_b' (149796 KB) OKAY [ 3.563s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g7250-00202-220422-B-8489468
(bootloader) Flashing partition modem_b
OKAY [ 0.821s]
Finished. Total time: 4.830s
rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
< waiting for any device >
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: b9-0.4-8351079
Baseband Version.....: g7250-0020
Serial Number........: 17071
--------------------------------------------
Checking product OKAY [ 0.070s]
extracting boot.img (96 MB) to disk... took 0.490s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (16 MB) to disk... took 0.109s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
extracting product.img (1844 MB) to disk... took 14.879s
archive does not contain 'product.sig'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (991 MB) to disk... took 7.576s
extracting system_other.img (22 MB) to disk... took 0.211s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (764 MB) to disk... took 6.119s
archive does not contain 'vendor_other.img'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
Sending 'boot_b' (98304 KB) OKAY [ 2.313s]
Writing 'boot_b' OKAY [ 0.494s]
Sending 'dtbo_b' (16384 KB) OKAY [ 0.460s]
Writing 'dtbo_b' OKAY [ 0.133s]
Sending sparse 'product' 1/8 (262140 KB) OKAY [ 6.145s]
Writing sparse 'product' 1/8 FAILED (remote: 'Partition product not found')
Finished. Total time: 44.382s
Press any key to exit...[/CODE
[QUOTE="rchris494, post: 87076459, member: 4067147"]
[USER=5216756]@jackeagle[/USER] BlissRoms Factory Image fails to install. i originally tried coming from pixel experience. then tried again after a fresh factory wipe. both had the same results. bootloader is unlocked & using platform-tools_r33.0.2-windows. any suggestions?
C:\htc>flash-all.bat
Sending 'bootloader_a' (8762 KB) OKAY [ 0.453s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b9-0.4-8351079
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition uefisecapp_a
(bootloader) Flashing partition featenabler_a
(bootloader) Flashing partition logfs
OKAY [ 0.266s]
Finished. Total time: 0.969s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
Sending 'radio_a' (149796 KB) OKAY [ 5.719s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g7250-00202-220422-B-8489468
(bootloader) Flashing partition modem_a
OKAY [ 0.531s]
Finished. Total time: 6.500s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
--------------------------------------------
Bootloader Version...: b9-0.4-8351079
Baseband Version.....: g7250-00202-220422-B-8489468
Serial Number........: 17121JECB0xxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.062s]
Setting current slot to 'a' OKAY [ 0.094s]
extracting boot.img (96 MB) to disk... took 0.297s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB) OKAY [ 3.812s]
Writing 'boot_a' OKAY [ 0.313s]
archive does not contain 'init_boot.img'
extracting dtbo.img (16 MB) to disk... took 0.062s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.734s]
Writing 'dtbo_a' OKAY [ 0.125s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (8 KB) OKAY [ 0.141s]
Writing 'vbmeta_a' OKAY [ 0.078s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.141s]
Writing 'vbmeta_system_a' OKAY [ 0.078s]
archive does not contain 'vbmeta_vendor.img'
extracting vendor_boot.img (96 MB) to disk... took 0.250s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (98304 KB) OKAY [ 3.828s]
Writing 'vendor_boot_a' OKAY [ 0.297s]
archive does not contain 'vendor_kernel_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.062s]
< waiting for any device >
Sending 'super' (4 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Press any key to exit...
[/QUOTE]
I got the same error and my bootloader is unlocked. Anyone get this ROM to install and boot?
[/QUOTE]
Click to expand...
Click to collapse

I got the same error and my bootloader is unlocked. Anyone get this ROM to install and boot?

Nevermind, I factory resetted, extracted the boot from payload.bin with payload dumper, flashed that boot to both slots and adb sideloaded the gapps rom in recovery and it works. Couldn't get it to work with method 1, kept saying that my device bootloader is locked which it's not.

jackeagle said:
Hi,
The install log says your device bootloader is locked that is why it failed to install. Unlock it properly and try.
Click to expand...
Click to collapse
my bootloader hasn't been locked in 6 months. i have been hoping around between pixel experience, calyxos and building my own pixel experience. trying to find one where the stupid google text messaging app actually works and my text messages do not disappear or the keyboard. after flashing to many times i have have determined that it is a google problem. the only company i know that doesn't update their base apks when they release an update to their rom.

rchris494 said:
my bootloader hasn't been locked in 6 months. i have been hoping around between pixel experience, calyxos and building my own pixel experience. trying to find one where the stupid google text messaging app actually works and my text messages do not disappear or the keyboard. after flashing to many times i have have determined that it is a google problem. the only company i know that doesn't update their base apks when they release an update to their rom.
Click to expand...
Click to collapse
Sorry and thanks for confirmation this is indeed weird that it does give device is locked error when using factory images. probably something is blocking it. for now i will take down factory image later today so just use method 2.
Will attach boot.img download link in OP
Sorry for all inconvenience caused due to this
Cheers!

jackeagle said:
Sorry and thanks for confirmation this is indeed weird that it does give device is locked error when using factory images. probably something is blocking it. for now i will take down factory image later today so just use method 2.
Will attach boot.img download link in OP
Sorry for all inconvenience caused due to this
Cheers!
Click to expand...
Click to collapse
i figure while i had some time i would test drive your rom. then ran into that error.
i must be having bad lucky. i did fastboot flash --slot all boot boot.img from the downloaded boot.img and it will not boot into the custom boot/recovery. it just keeps booting back into my pixel experience i had loaded. then i tried again after a fresh factory wipe and it goes to the stock recovery. after fastboot flash --slot all boot boot.img
edit: so i did manage to get this rom to install. i had to use twrp and do a factory wipe in twrp then adb sideload the rom. recovery included with the .zip does load and work.

I would like to translate the additional settings into Russian, turn off the "most important" widget turns off only the weather, the day and date remain. Overall good, fast firmware
There is a long unlock after the print, so it was on one of the updates to the stock firmware, then fixed
P. S But the battery holds decently, like)Does the author have a telegram channel? For feedback

jackeagle said:
Sorry and thanks for confirmation this is indeed weird that it does give device is locked error when using factory images. probably something is blocking it. for now i will take down factory image later today so just use method 2.
Will attach boot.img download link in OP
Sorry for all inconvenience caused due to this
Cheers!
Click to expand...
Click to collapse
Hello @jackeagle do you know when will be next build 15.7? I saw that many phones received it.
In any case currently this is best custom ROM for me, ACIP for example not booting, other ROMs have luck of customization

How does a battery life compare to the stock rom?

Question Help Recovering Data From Device with no Display/Touch

Hi there. My Pixel 5a has a motherboard issue, and needs to be returned to Google for warranty. I am trying to recover my files from the device before I send it in, but I'm having issues. For some reason, even though I have enabled usb debugging and issued commands through this laptop before, it says adb unauthorized when I issue the command "adb devices". So I downloaded my factory image, removed the "-w" from the flash all bat file, and attempted to flash to see if that would fix issue. However, it appears that for some reason I'm missing fastboot d. Here is the screen I get when attempting to flash.
Sending 'bootloader_b' (8762 KB) OKAY [ 0.122s]
Writing 'bootloader_b' (bootloader) Flashing Pack version b9-0.4-7758098
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition featenabler_b
(bootloader) Flashing partition logfs
OKAY [ 0.343s]
Finished. Total time: 0.771s
Rebooting into bootloader OKAY [ 0.029s]
Finished. Total time: 0.056s
Sending 'radio_b' (149780 KB) OKAY [ 0.970s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g7250-00161-211008-B-7807492
(bootloader) Flashing partition modem_b
OKAY [ 0.782s]
Finished. Total time: 2.058s
Rebooting into bootloader OKAY [ 0.038s]
Finished. Total time: 0.053s
--------------------------------------------
Bootloader Version...: b9-0.4-7758098
Baseband Version.....: g7250-00161-211008-B-7807492
Serial Number........: 19241JEG503250
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.061s]
Checking 'version-bootloader' OKAY [ 0.057s]
Checking 'version-baseband' OKAY [ 0.055s]
Setting current slot to 'b' OKAY [ 0.071s]
extracting boot.img (96 MB) to disk... took 0.384s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB) OKAY [ 0.623s]
Writing 'boot_b' OKAY [ 0.472s]
extracting dtbo.img (16 MB) to disk... took 0.104s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.192s]
Writing 'dtbo_b' OKAY [ 0.120s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (8 KB) OKAY [ 0.126s]
Writing 'vbmeta_b' OKAY [ 0.062s]
extracting vbmeta_system.img (0 MB) to disk... took 0.002s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.122s]
Writing 'vbmeta_system_b' OKAY [ 0.059s]
archive does not contain 'vbmeta_vendor.img'
extracting vendor_boot.img (96 MB) to disk... took 0.536s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (98304 KB) OKAY [ 0.625s]
Writing 'vendor_boot_b' OKAY [ 0.469s]
extracting super_empty.img (0 MB) to disk... took 0.002s
Rebooting into fastboot OKAY [ 0.049s]
< waiting for any device >
And then it hangs there indefinately. The only way I can get out of here is by pressing the power and volume down simutaneously. Then the dialogue adds this line
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Press any key to exit...
Can anyone help me get to a point where I can recover my data? Please, and thanks in advance.

Edit: Was obviously assuming your bootloader is unlocked, but I guess it's not your case if your'e returning your phone to Google.
Experiencing a similar problem. adb unauthorized means you need to approve the adb connection on the android device, which you unfortunately can't.
If you haven't set a password/pin/pattern on your lock screen and your data is not encrypted you can:
1. Reboot to bootloader (Power + volume down for 15-20 seconds)
2. Use fastboot to boot TWRP (Do not flash)
3. Use ADB there
However if you have set a lock screen password/pin/pattern then your data will be encrypted and you wont be able to decrypt it as TWRP does not support encryption/decryption for A12+. What you can probably do is backup your encrypted data partition to your PC (Using the twrp command in shell) and restore it when your phone is back.

danielhatzor said:
Edit: Was obviously assuming your bootloader is unlocked, but I guess it's not your case if your'e returning your phone to Google.
Experiencing a similar problem. adb unauthorized means you need to approve the adb connection on the android device, which you unfortunately can't.
If you haven't set a password/pin/pattern on your lock screen and your data is not encrypted you can:
1. Reboot to bootloader (Power + volume down for 15-20 seconds)
2. Use fastboot to boot TWRP (Do not flash)
3. Use ADB there
However if you have set a lock screen password/pin/pattern then your data will be encrypted and you wont be able to decrypt it as TWRP does not support encryption/decryption for A12+. What you can probably do is backup your encrypted data partition to your PC (Using the twrp command in shell) and restore it when your phone is back.
Click to expand...
Click to collapse
Hi there, thanks for responding. Actually, yes, my bootloader is unlocked. The phone is rooted. I have enabled usb debugging in the past, but for some reason it is still unauthorized. I currently cannot even get the os to boot, but I cannot figure out why because no screen. When I try to flash the factory image, removing the "-w" so my data isn't wiped, the process hangs att the portion where it boots to fastbootd and will not go any further.
I'm going to try to boot into twrp again. I seem to remember that I tried this, but let's see.
If you have any other info or advice, it would be greatly appreciated.
Edit: I just tried to boot into twrp, and I get an error message. It is : (bootloader) boot.img missing cmdline or OS version
I have attached a picture of the command line messages. Maybe someone here can see something that would point to something that would help

Is it possible you flashed an incompatible / corrupted factory image for your phone?
https://www.reddit.com/r/LineageOS/comments/kn257b

Yeah, I just went and double checked, and then reflashed to see. I def have the July barbet image, which is for the 5a, my device. It just won't work.
Google is trying to get me to either take the device to ubreakifix, which when I try tell me that they do not do motherboard issues, or send the device to them, which I am hesitant to do because I feel they are going to wipe the device. Very frustration situation. I've always used nexus/pixel devices becuase of the readily available info on here, but this just doesn't seem to be a popular development device, and I can't seem to find a way. I know there is some command or series of commands that will fix this issue, I just can't seem to find it.
Thank you again for replying and attempting to help. Truly appreciated. Hopefully someone will stumble across this and let me know.