[STOCK][DUMPS][FIRMWARE] Essential stock firmware and rom dumps

[ktmom]

If I remove this line fastboot -w in the .bat file, will it work fine and not wipe my phone or cause any issue? But just technically update my phone. I don't keep up to date with Essential as it's my backup phone but will like to get it up to date now as I'm using it soon for a trip.

There's never a guarantee that a problem won't develop. As repeated over and once, removing the -w prevents the script from wiping the device. It works fine for me and others. Just make sure to use a good USB A to USB C cable.

 

[dragynbane222]

No... Custom ROMs do not bundle their own bootloader...

On this device they are system, vendor, and boot.img

Ah, alright, I always thought the boot.img was part of the bl, thanks for setting me straight

 

[CamoGeko]

Ah, alright, I always thought the boot.img was part of the bl, thanks for setting me straight

Boot.img contains the Kernel and Ramdisk, core components to load the device.

 

[dragynbane222]

Boot.img contains the Kernel and Ramdisk, core components to load the device.

So it's basically like the vmlinuz/initramfs in the /boot partition on most x86 Linux system

 

[rignfool]

Boot.img contains the Kernel and Ramdisk, core components to load the device.

Boot.img contains kernel and recovery...

We use SAR... sur

 

[CamoGeko]

Boot.img contains kernel and recovery...

We use SAR... sur

Thanks for the correction.

Tbh no idea why I said ramdisk. Running on somewhat lack of sleep atm.


Sent from my mata using Thebear Blue XDA Labs

 

[aleph23]

Thanks for the correction.

Tbh no idea why I said ramdisk. Running on somewhat lack of sleep atm.

Having just read Google's documentation on this, boot.img does indeed contain a ramdisk. The recovery partition is a ramdisk, plus the kernel. There are typically two bootloaders that initiate prior to boot.img, primary and secondary. Their partitions under /dev are usually 'pbl' and 'sbl'. Primary passes to secondary and secondary passes to boot.img <=- This would be the point (@ secondary bootloader) at which verity is confirmed. Starting with Android 10 recovery itself handles the initial boot process. Also in 10, fastboot is partly broken out of the bootloader and brought into the boot.img/recovery.

See
source.android.com/devices/bootloader/fastbootd#unified_fastboot_and_recovery

 

[rignfool]

Having just read Google's documentation on this, boot.img does indeed contain a ramdisk. The recovery partition is a ramdisk, plus the kernel. There are typically two bootloaders that initiate prior to boot.img, primary and secondary. Their partitions under /dev are usually 'pbl' and 'sbl'. Primary passes to secondary and secondary passes to boot.img <=- This would be the point (@ secondary bootloader) at which verity is confirmed. Starting with Android 10 recovery itself handles the initial boot process. Also in 10, fastboot is partly broken out of the bootloader and brought into the boot.img/recovery.

See
source.android.com/devices/bootloader/fastbootd#unified_fastboot_and_recovery

Ok...

Except the fact that Cam was referring about boot instructions... Or.. initramfs I think... Which is a "traditional" ramdisk

 

[aleph23]

Ok...

Except the fact that Cam was referring about boot instructions... Or.. initramfs I think... Which is a "traditional" ramdisk

Hmm.... I guess I don't understand the difference. Boot.img has a kernel and what AOSP calls "recovery", right? And Recovery is, actually the INITial RamDisk, like a standard initrd, right? ...Or am I missing something?

 

[onema]

Hello all is the latest Nov update going to be available for bts? I have a Sprint and the one on the essential site doesn't flash well for me

 

[eKeith]

Would also appreciate the November BTS. Thanks!

 

[handisnacks]

Seriously, where's November?

 

[ktmom]

https://www.essential.com/developer/current-builds

 

[sga999]

I have gotten the dreaded red verity warning. But I cannot find the file with the fix. I believe I'm supposed to go to http://gg.gg/ai7m1. But that just returns a weird error message. Does someone have this file?

I got this Essential phone from eBay a couple of weeks ago, and I'm wondering if it has more problems than this. This red warning did not occur until today when I was flashing Android 10. I have been flashing stock pie and Q for the last couple of weeks. But for most of that time, fastboot seems to randomly fail when writing various partitions. I'm thinking it is possibly a problem with one of the slots, but I haven't really proved that. The cable that I am using is a good one, not the one that came with the phone. After some of those write failures today, the red warning started to appear.

I hope someone can give me that file to fix the red warning, but I don't think that's going to help me with these other issues.

I had successfully unlocked the bootloader right after I got this. But unfortunately, I did not do the critical unlock. Just a failure on my part to read well enough. But it sounds like that should not be an issue for me right now because I have never tried going backwards from a custom rom to the stock rom.

 

[ktmom]

I have gotten the dreaded red verity warning. But I cannot find the file with the fix. I believe I'm supposed to go to http://gg.gg/ai7m1. But that just returns a weird error message. Does someone have this file?

I got this Essential phone from eBay a couple of weeks ago, and I'm wondering if it has more problems than this. This red warning did not occur until today when I was flashing Android 10. I have been flashing stock pie and Q for the last couple of weeks. But for most of that time, fastboot seems to randomly fail when writing various partitions. I'm thinking it is possibly a problem with one of the slots, but I haven't really proved that. The cable that I am using is a good one, not the one that came with the phone. After some of those write failures today, the red warning started to appear.

I hope someone can give me that file to fix the red warning, but I don't think that's going to help me with these other issues.

I had successfully unlocked the bootloader right after I got this. But unfortunately, I did not do the critical unlock. Just a failure on my part to read well enough. But it sounds like that should not be an issue for me right now because I have never tried going backwards from a custom rom to the stock rom.

Look at the post here.

 

[sga999]

Look at the post here.

Thanks for looking for the file. I did see the link to the patch, but I wasn't sure what I would do with that. However, when reading it, it seemed to imply that we needed to do the same thing that is mentioned in post 1386 of this thread. That post mentions issuing command:
adb reboot "dm-verity enforcing"

I tried that, and it worked perfectly. However, I'm not sure if this just gets rid of the red warning, but does not fix the actual problem. Maybe the solution you put there about the universal disabler would actually fix it?

EDIT: I was replying while you were posting your new message. I will try to find that file later, but I do think that the command probably did the same thing that the missing boot.img did. Do you agree?

 

[ktmom]

@sga999, if the verity warning is gone, no need for more

 

[krak3n77]

WTF

Yesssss

Dude legit, i thought that an actual bug on my screen!! I tried to smash it with my finger and I got really confused when there was nothing there! XD

 

[raoulbhatia]

What bootloader/vendor do you guys use for pie based custom ROMs like AICP/RR? I remember why I quit using this device: Endless lower level firmware issues that makes hardware like the audio, earpiece, touchscreen, or the radio completely give out depending on certain kernels/bootloaders/ROMs. I can never get the perfect combination that actually allows this thing to be usable as a daily driver...

I'd be interested as well - i.e. are people using https://sourceforge.net/projects/mata-bts/files/Pie/August/ ?

EDIT: I flashed the August NOVENDOR package and things Seen to work well. LTE/WLAN/Calls are working.

Thanks,
Raoul

 

[rocketrazr1999]

I'd be interested as well - i.e. are people using https://sourceforge.net/projects/mata-bts/files/Pie/August/ ?

Thanks,
Raoul

WOW!!!! Now I understand what my problems are due to!!!! I have problems with EVERYTHING on my Essential!!! From the A/B being a mess, ( continually stops booting and defaults to the bootloader after Magisk module flashing, etc) to apps not working right (Titanium Backup only backs up data), and BusyBox not installing (Viper won't work without it), and a plethora of other examples of hardware and software issues, notably the terrible audio crackle and touchscreen responsiveness. Oh, anyone know why the screen is cut off on the right side? This phone is so rough around the edges (and insides) that it's nearly impossible to like. Such a contrast to my beloved N5, which I finally sold both of (Almost 7 year old phones that can still handle ported Android updates and run BETTER than this Essential!!!

Mike