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

Search This thread
By:
Advanced…
R

raoulbhatia

Member
Sep 28, 2014
31
15
rocketrazr1999 said:
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
Click to expand...
Click to collapse

Hi Mike - I am not sure what this has to do with my question about the bootloader/vendor images people use.

However, I am using my Essential PH1 with Lineage for a loooong time and experienced only a few issues that I was able to overcome with the help of the community. I haven't had any real issue since it got official Lineage support [1] - i even dirty flashed from an unofficial build (thanks @invisiblek!) to the official build w/o real issue. (I only had to use lineage-migration-signed.zip, i believe).

If you share more details, perhaps to a relevant thread, people might be able to help you, i.e. https://forum.xda-developers.com/essential-phone/development/lineageos-16-0-appears-to-live-t3939150.
If not, then at least you have a phone that has strong support from the vendor w/ fast updates, etc.

Good luck with making your phone work!
Raoul

[1] https://wiki.lineageos.org/devices/mata
 
T

the_Pan

Senior Member
Dec 23, 2014
126
49
I just tried to flash, but I only get:
Code: 
./flashallnowipe.sh 
error: cannot load 'nvdef': No such file or directory
error: cannot load 'nvdef': No such file or directory
error: cannot load 'boot': No such file or directory
error: cannot load 'boot': No such file or directory
error: cannot load 'system': No such file or directory
error: cannot load 'system': No such file or directory
error: cannot load 'bluetooth': No such file or directory
error: cannot load 'bluetooth': No such file or directory
error: cannot load 'abl': No such file or directory
error: cannot load 'abl': No such file or directory
error: cannot load 'dsp': No such file or directory
error: cannot load 'dsp': No such file or directory
error: cannot load 'modem': No such file or directory
error: cannot load 'modem': No such file or directory
error: cannot load 'vendor': No such file or directory
error: cannot load 'vendor': No such file or directory
target reported max download size of 536870912 bytes
sending 'cmnlib_a' (221 KB)...
OKAY [  0.101s]
writing 'cmnlib_a'...
OKAY [  0.003s]
finished. total time: 0.103s
target reported max download size of 536870912 bytes
sending 'cmnlib_b' (221 KB)...
OKAY [  0.100s]
writing 'cmnlib_b'...
OKAY [  0.003s]
finished. total time: 0.103s
target reported max download size of 536870912 bytes
sending 'cmnlib64_a' (292 KB)...
OKAY [  0.103s]
writing 'cmnlib64_a'...
OKAY [  0.003s]
finished. total time: 0.106s
target reported max download size of 536870912 bytes
sending 'cmnlib64_b' (292 KB)...
OKAY [  0.101s]
writing 'cmnlib64_b'...
OKAY [  0.003s]
finished. total time: 0.105s
target reported max download size of 536870912 bytes
sending 'tz_a' (1868 KB)...
OKAY [  0.192s]
writing 'tz_a'...
OKAY [  0.100s]
finished. total time: 0.293s
target reported max download size of 536870912 bytes
sending 'tz_b' (1868 KB)...
OKAY [  0.185s]
writing 'tz_b'...
OKAY [  0.078s]
finished. total time: 0.263s
error: cannot load 'devcfg': No such file or directory
error: cannot load 'devcfg': No such file or directory
target reported max download size of 536870912 bytes
sending 'hyp_a' (264 KB)...
OKAY [  0.102s]
writing 'hyp_a'...
OKAY [  0.002s]
finished. total time: 0.105s
target reported max download size of 536870912 bytes
sending 'hyp_b' (264 KB)...
OKAY [  0.099s]
writing 'hyp_b'...
OKAY [  0.002s]
finished. total time: 0.101s
error: cannot load 'keymaster': No such file or directory
error: cannot load 'keymaster': No such file or directory
error: cannot load 'mdtp': No such file or directory
error: cannot load 'mdtp': No such file or directory
error: cannot load 'mdtpsecapp': No such file or directory
error: cannot load 'mdtpsecapp': No such file or directory
error: cannot load 'pmic': No such file or directory
error: cannot load 'pmic': No such file or directory
target reported max download size of 536870912 bytes
sending 'rpm_a' (228 KB)...
OKAY [  0.100s]
writing 'rpm_a'...
OKAY [  0.003s]
finished. total time: 0.103s
target reported max download size of 536870912 bytes
sending 'rpm_b' (228 KB)...
OKAY [  0.098s]
writing 'rpm_b'...
OKAY [  0.065s]
finished. total time: 0.163s
error: cannot load 'xbl': No such file or directory
error: cannot load 'xbl': No such file or directory
rebooting into bootloader...
OKAY [  0.000s]
finished. total time: 0.050s
I'm still on pie with August 2019 firmware. Do I need to flash the september firmware(first Q release) first to get it working?
 
CamoGeko

CamoGeko

Retired Forum Moderator
Dec 10, 2010
15,977
8,371
Establishing Battlefield Control... Standby!
Nexus 7
Essential Phone
the_Pan said:
I just tried to flash, but I only get:
Code: 
./flashallnowipe.sh 
error: cannot load 'nvdef': No such file or directory
error: cannot load 'nvdef': No such file or directory
error: cannot load 'boot': No such file or directory
error: cannot load 'boot': No such file or directory
error: cannot load 'system': No such file or directory
error: cannot load 'system': No such file or directory
error: cannot load 'bluetooth': No such file or directory
error: cannot load 'bluetooth': No such file or directory
error: cannot load 'abl': No such file or directory
error: cannot load 'abl': No such file or directory
error: cannot load 'dsp': No such file or directory
error: cannot load 'dsp': No such file or directory
error: cannot load 'modem': No such file or directory
error: cannot load 'modem': No such file or directory
error: cannot load 'vendor': No such file or directory
error: cannot load 'vendor': No such file or directory
target reported max download size of 536870912 bytes
sending 'cmnlib_a' (221 KB)...
OKAY [  0.101s]
writing 'cmnlib_a'...
OKAY [  0.003s]
finished. total time: 0.103s
target reported max download size of 536870912 bytes
sending 'cmnlib_b' (221 KB)...
OKAY [  0.100s]
writing 'cmnlib_b'...
OKAY [  0.003s]
finished. total time: 0.103s
target reported max download size of 536870912 bytes
sending 'cmnlib64_a' (292 KB)...
OKAY [  0.103s]
writing 'cmnlib64_a'...
OKAY [  0.003s]
finished. total time: 0.106s
target reported max download size of 536870912 bytes
sending 'cmnlib64_b' (292 KB)...
OKAY [  0.101s]
writing 'cmnlib64_b'...
OKAY [  0.003s]
finished. total time: 0.105s
target reported max download size of 536870912 bytes
sending 'tz_a' (1868 KB)...
OKAY [  0.192s]
writing 'tz_a'...
OKAY [  0.100s]
finished. total time: 0.293s
target reported max download size of 536870912 bytes
sending 'tz_b' (1868 KB)...
OKAY [  0.185s]
writing 'tz_b'...
OKAY [  0.078s]
finished. total time: 0.263s
error: cannot load 'devcfg': No such file or directory
error: cannot load 'devcfg': No such file or directory
target reported max download size of 536870912 bytes
sending 'hyp_a' (264 KB)...
OKAY [  0.102s]
writing 'hyp_a'...
OKAY [  0.002s]
finished. total time: 0.105s
target reported max download size of 536870912 bytes
sending 'hyp_b' (264 KB)...
OKAY [  0.099s]
writing 'hyp_b'...
OKAY [  0.002s]
finished. total time: 0.101s
error: cannot load 'keymaster': No such file or directory
error: cannot load 'keymaster': No such file or directory
error: cannot load 'mdtp': No such file or directory
error: cannot load 'mdtp': No such file or directory
error: cannot load 'mdtpsecapp': No such file or directory
error: cannot load 'mdtpsecapp': No such file or directory
error: cannot load 'pmic': No such file or directory
error: cannot load 'pmic': No such file or directory
target reported max download size of 536870912 bytes
sending 'rpm_a' (228 KB)...
OKAY [  0.100s]
writing 'rpm_a'...
OKAY [  0.003s]
finished. total time: 0.103s
target reported max download size of 536870912 bytes
sending 'rpm_b' (228 KB)...
OKAY [  0.098s]
writing 'rpm_b'...
OKAY [  0.065s]
finished. total time: 0.163s
error: cannot load 'xbl': No such file or directory
error: cannot load 'xbl': No such file or directory
rebooting into bootloader...
OKAY [  0.000s]
finished. total time: 0.050s
I'm still on pie with August 2019 firmware. Do I need to flash the september firmware(first Q release) first to get it working?
Click to expand...
Click to collapse

Hmm...

Can you right click the flashallnowipe.bat and click edit, then screenshot the contents?

Coz it sure doesn't look like ur using my zip.
 
T

the_Pan

Senior Member
Dec 23, 2014
126
49
CamoGeko said:
Hmm...

Can you right click the flashallnowipe.bat and click edit, then screenshot the contents?

Coz it sure doesn't look like ur using my zip.
Click to expand...
Click to collapse

The file is looking good to me, the only difference seems that some files, like "abl" or "bluetooth" are now .img files, while in older builds they've got no extension.
It seems this is something with Q, because the files are looking the same in the first Q realease, I just checked.

EDIT: Wait, I just looked into the .bat file, over there you changed the filenames, but not in the .sh file. I'll change them and try again.

EDITx2: With edited scriptfile, it also works on linux! ;)
 
Last edited:
  • Like
Reactions: CamoGeko and avd
CamoGeko

CamoGeko

Retired Forum Moderator
Dec 10, 2010
15,977
8,371
Establishing Battlefield Control... Standby!
Nexus 7
Essential Phone
the_Pan said:
The file is looking good to me, the only difference seems that some files, like "abl" or "bluetooth" are now .img files, while in older builds they've got no extension.
It seems this is something with Q, because the files are looking the same in the first Q realease, I just checked.

EDIT: Wait, I just looked into the .bat file, over there you changed the filenames, but not in the .sh file. I'll change them and try again.

EDITx2: With edited scriptfile, it also works on linux! ;)
Click to expand...
Click to collapse

The Linux script had errors in it which have now been fixed, this is because I natively use Windows and didin't test the SH script before uploading. All sorted now though.

Glad you got it flashed fine. ?


Sent from my mata using Thebear Blue XDA Labs
 
Last edited:
  • Like
Reactions: the_Pan and RandomPooka
T

Talnoy

Member
Jun 13, 2011
32
1
34
Hey can someone maybe give me a hand on how to actually use these 'back to stock' packages?

I've got an essential with a TWRP.img file flashed to slot A on my essential but slot B is the booting slot. No matter what I try, TWRP simply refuses to install anything to the B slot and nothing boots from it except the stock recovery, but now I can't load a rom or go back stock since it's been wiped.

How do I either get TWRP on to slot b, or use these back to stock packs? I've tried using the 'cmd-here.exe' files and running the 'flashallwipe.bat' command but it just sits at 'waiting for device'


Update: Seems I've figured out how to use the stock restoration zip files via fastbook but now my phone just doesn't do anything - I can still get into fastboot but I can't boot on either slot for recover - I just get a dead android with "no command" sitting there. Trying to boot to system does the same thing.

Help?

Is there something I'm missing? I'm so confused at this phone. *Everything* I've read has said the TWRP zip file was supposed to install TWRP on BOTH the A and B slots but mine just never worked.
 
Last edited:
C

chanh2018

Senior Member
Jan 19, 2018
532
146
Talnoy said:
Hey can someone maybe give me a hand on how to actually use these 'back to stock' packages?

I've got an essential with a TWRP.img file flashed to slot A on my essential but slot B is the booting slot. No matter what I try, TWRP simply refuses to install anything to the B slot and nothing boots from it except the stock recovery, but now I can't load a rom or go back stock since it's been wiped.

How do I either get TWRP on to slot b, or use these back to stock packs? I've tried using the 'cmd-here.exe' files and running the 'flashallwipe.bat' command but it just sits at 'waiting for device'


Update: Seems I've figured out how to use the stock restoration zip files via fastbook but now my phone just doesn't do anything - I can still get into fastboot but I can't boot on either slot for recover - I just get a dead android with "no command" sitting there. Trying to boot to system does the same thing.

Help?

Is there something I'm missing? I'm so confused at this phone. *Everything* I've read has said the TWRP zip file was supposed to install TWRP on BOTH the A and B slots but mine just never worked.
Click to expand...
Click to collapse
If you want to use TWRP in future, use Jan stock rom, if not, use Feb stock rom
- Make sure you install Essential driver to your PC
- Use fastboot package from Essential
- Unzip the stock rom
- Put phone in boot loader mode
- Run "flashall.bat" in unzip folder
- Let the scrip does installation itself and after phone reboot, you should be back to stock.
 
  • Like
Reactions: mrrocketdog
mrrocketdog

mrrocketdog

Senior Member
Oct 27, 2013
4,975
2,330
also ; @Talnoy make sure you flash the twrp-installer-mata-3.2.3-0.zip ; after you flash twrp and after you set active your initial slot ; from twrp. which will patch both slots. (after flash , hit reboot and on that screen select your initial slot).
 
T

Talnoy

Member
Jun 13, 2011
32
1
34
mrrocketdog said:
also ; @Talnoy make sure you flash the twrp-installer-mata-3.2.3-0.zip ; after you flash twrp and after you set active your initial slot ; from twrp. which will patch both slots. (after flash , hit reboot and on that screen select your initial slot).
Click to expand...
Click to collapse

Awesome! So to get this straight I'm going to do the following:
- reboot to fastboot mode
(As of now, my active booting slot is slot a.)
- Flash the TWRP.img file to slot b
- flag slot b as the active slot
- boot to recovery in slot b
- install the TWRP.zip file
- switch to slot A
- reboot to system
- reboot to bootloader and then ensure slot a is active and boot to recovery
- once in recovery, I'll then be able to flash a custom rom - do a wipe and flash away
 
mrrocketdog

mrrocketdog

Senior Member
Oct 27, 2013
4,975
2,330
well just -boot to recovery.
then select install and flash the twrp.zip file. go back to twrp's home screen. hit reboot and select slot A.
if thats what you were saying then , yup.
then yup , wipe and flash away [emoji111]

---------- Post added at 08:55 PM ---------- Previous post was at 08:52 PM ----------

here is link to twrp-installer.zip if you dont have.
?https://www.dropbox.com/s/gw8bkyzvfc6z5hz/twrp-installer-mata-3.2.3-0.zip?dl=0
 
natetokes

natetokes

Senior Member
May 4, 2011
80
29
Toronto/Durham
steamcommunity.com
Essential Phone
Samsung Galaxy Note 9
Talnoy said:
Awesome! So to get this straight I'm going to do the following:
- reboot to fastboot mode
(As of now, my active booting slot is slot a.)
- Flash the TWRP.img file to slot b
- flag slot b as the active slot
- boot to recovery in slot b
- install the TWRP.zip file
- switch to slot A
- reboot to system
- reboot to bootloader and then ensure slot a is active and boot to recovery
- once in recovery, I'll then be able to flash a custom rom - do a wipe and flash away
Click to expand...
Click to collapse
Are you THAT talnoy? If so, whatchu doin in my waters?
 
natetokes

natetokes

Senior Member
May 4, 2011
80
29
Toronto/Durham
steamcommunity.com
Essential Phone
Samsung Galaxy Note 9
Talnoy said:
Amazing! Hit me up on telegram friend!
Click to expand...
Click to collapse
Ok give me a bit I have to install it and go outside to get a signal to set it up. I'm not sure how precious time is but if that phone can wait until after work tomorrow I can send you my fastboot folder and the rom zip I used etc. I have to be at work in 6hrs.
If not, look up "daze one TWRP" on YouTube. I got january stock (found it by using a cached copy of essentials site) replaced the boot with this guy's pre rooted image, set up the phone after flashing in fastboot, flashed the TWRP and root IMG to the current slot in fastboot, used TWRP installer in the booted TWRP, rebooted to recovery, formated data, flashed Evo x in twrp. Rebooted to system.
 
  • Like
Reactions: IronRoo
You must log in or register to reply here.

Similar threads

invisiblek
[ROM][UNOFFICIAL] LineageOS 15.1 for the Essential PH-1 (mata)
Replies
2K
Views
263K
rophiroth
rophiroth
Dees_Troy
Official TWRP 3.2.3-0 for Essential PH-1
Replies
476
Views
100K
G
gk1984
G
Paranoid Android Quartz 5 - Essential PH-1
Replies
406
Views
66K
Pairman
Pairman
N
[OFFICIAL] LineageOS 18.1 for the Essential Phone
Replies
349
Views
56K
M
malerocks
R
[ROM][10][UNOFFICIAL] LineageOS 17.1 for the Essential PH-1 (mata)
Replies
331
Views
47K
robsonline
robsonline

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 152
    6
    63c
    I am not responsible if you break your phone in any way, these are here for your aid. I will help as much as i can, but it is on YOU, the user to read the OP and understand exactly what it is you are doing at ALL times.

    READ THIS: http://mata.readthedocs.io/en/latest/ LEARN FROM IT, DONT EVEN CONTINUE UNLESS YOU HAVE READ THIS

    These can be used to return to 100% stock as long as you can get into fastboot mode on the device, and have unlocked the bootloader and critical partitions. All images contained in the zips are directly from the essential Fastboot zips and OTA's, and dumps for the rest

    Prerequisites:
    1.     Working fastboot environment in bootloader: (test using the command fastboot devices should return your s/n) Windows drivers are at the bottom of the OP.
    Essentials windows drivers contain working ADB/Fastboot and places an environment variable to link to these binaries, i would HIGHLY recommend ditching any and all adb/fastboots you may have (minimal, HTC, etc) and use what is supplied by essential, they just work (Not gonna help you either if your hellbent on using your adb/fastboot).
    The zips contain all the firmware (19 Images), TWRP11.img (the latest version), and a stockboot.img (so you can conveniently place on your phone and flash in twrp) when rooting with magisk, and boot.fix.red.img (In case you kill verity).

    2. Bootloader unlocked: run the command fastboot flashing unlock in bootloader (THIS WIPES USER DATA, BACKUP BEFOREHAND), conversely fastboot flashing lock will relock the bootloader. I dont recommend this, as there are lots of bricks from messing up a flash and locking yourself out afterward.

    3. Critical partition unlocked: run the command fastboot flashing unlock_critical in bootloader (THIS WIPES USER DATA, BACKUP BEFOREHAND), conversely fastboot flashing lock_critical will relock the critical partition flashability. I dont recommend this, as there are lots of bricks from messing up a flash and locking yourself out afterward.

    4. Common Sense: Use IT!!!!!

    Downloads
    Android 10 BTS Folder: https://sourceforge.net/projects/mata-bts/files/10
    Q Beta BTS Folder: https://sourceforge.net/projects/mata-bts/files/Q-Beta/
    Pie BTS & Novendor Folder: https://sourceforge.net/projects/mata-bts/files/Pie
    P Beta BTS: https://sourceforge.net/projects/mata-bts/files/P-Beta/
    Oreo BTS & NOVENDOR: https://sourceforge.net/projects/mata-bts/files/Oreo/

    The Files below are OLD as dirt BTS

    OPM1.180104.010 mega.nz (oreo 8.1 beta1)
    OPM1.170911.254 mega.nz (oreo 8.0 beta3)
    OPM1.170911.213 mega.nz (oreo 8.0 beta2)
    OPM1.170911.130 mega.nz (oreo 8.0 beta)

    NMK32F AFH (latest nougat 7.1)
    NMJ88C mega.nz (nougat 7.1)
    NMJ51B AFH (nougat 7.1)
    NMJ32F AFH (nougat 7.1)
    NMJ20D mega.nz (nougat 7.1)
    NMI81C AFH (nougat 7.1)

    Drive Folder of Patched Essential Boot images Credit Goes to @dazeone

    Some OLD AS DIRT Novendor zips aswell... if anyone still cares

    OPM1.180104.010 mega.nz (oreo 8.1 beta1)
    OPM1.170911.254 mega.nz (oreo 8.0 beta3)
    OPM1.170911.213 mega.nz (oreo 8.0 beta2)

    Windows Drivers
    drivers


    Unzip this and check out the flash-all.[bat,sh] scripts for win/lin (they're identical but provided for easier flashability).
    They're set up to flash to both slots. Most people will want to do this on a back to stock mission, but they can be adjusted if your goal is something else.

    If coming from some other rom, you're also going to want to wipe your data, or you're not going to boot. This can be accomplished by the command in the bootloader: fastboot -w keep in mind there are multiple scripts to wipe for you in the zips.

    These can also be used to make custom roms/rooted boot images/etc too, so have fun with it!

    Thanks:
    @invisiblek - aer0zer0 stole his thread, he put most of it together
    @aer0zer0 - i stole the thread from aer0, his 2yr old son makes more use of the PH-1 than he does.
    @bmg1001 - Root thread, found here root
    @dazeone - Provides independent patched boot images and has an awesome YouTube Channel of Guides! DazeOne Youtube Channel

    Enjoy :)
    View
    18
    aer0zer0
    aer0zer0
    this thread is mine!!!!!!!!! all mine now. Ill update the OP soon.
    View
    16
    aer0zer0
    aer0zer0
    OP updated with December BTS and NOVENDOR. Also, over int he root thread, i have provided my patched stock boot.img as well. They are all over the place nowadays..lol

    Enjoy :)

    dec_patched_stock_twrp_ianmacd1203_magisk

    https://www.androidfilehost.com/?fid=11410963190603865614
    View
    16
    aer0zer0
    aer0zer0
    OP Updated with January BTS and Novendor.

    Storytime: I purchased a OP6T early December, and I hadn't planned on selling my PH1 (the working one). Got 350 for it on Craigslist. Because I still wanna be productive on this device, I started trying to follow through on my original claim I started in October for my brick (To this day, I still don't know what happened). And since they aren't selling the device anymore, 199.00 brick replacement is gone. I got frustrated with the level of incompetence "chief hooligan" and friends have displayed lately (You can't seriously tell me that they don't have the qcom Sahara tool for their own device....)

    All I want is for them to just flash my phone again. I'm a little disappointed in how they have absolutely run this company into the ground. I'm not a Andy Rubin Homer, I had no idea who he was until people were like, "omfg the father of Android is making a phone, der der derr".

    A minimalist phone, with great design and timely updates, I couldn't ask for more. They instead, teased and promoted various peripherals, that never panned out (dock, 360 camera, let's face it, DAQ, they wasted the window of excitement there). For the first flagship device, it was great, the PH2 could be/could have been amazing. Now I'm not so sure.

    Let us hope, for essentials sake, if/when the ph2 pipedream is ever realized, they have a good idea of what their fanbase/niche wants in a device.

    fin, aer0zer0

    p.s. I'll do what I can with BTS and NoVendors, there are some amazing devs that own this device, but it's hard without one of my own, can't test anything I make.
    View
    15
    aer0zer0
    aer0zer0
    DP#2 Is up

    Enjoy :)
    View

New posts