Database Info

Firmware Update FRD-L09C432B401

Anybody tried to install it? Is it possible that this is the oreo Update we have been waiting for since it ends with B401 instead of the usual B3XX?

Lukke2804 said:
Anybody tried to install it? Is it possible that this is the oreo Update we have been waiting for since it ends with B401 instead of the usual B3XX?
Click to expand...
Click to collapse
UPDATE: I tried to install it, doesnt work.(Via Dload)

It's nougat.
Changelog: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1774/g1755/v111861/f1/full/changelog.xml

It looks like security patches. The best thing is that we are not receiving these updates, they only showss on FF...i'm still waiting for B399 in Italy..

Giuskiller said:
It looks like security patches. The best thing is that we are not receiving these updates, they only showss on FF...i'm still waiting for B399 in Italy..
Click to expand...
Click to collapse
Same here in Germany. I am still on B394 and have the security patch from August. This is awful. The worst thing is to see them every month making a version with the current security patches but dont rolling them out. How hard could it be. Seriously, Honor has to improve this.

Lukke2804 said:
Same here in Germany. I am still on B394 and have the security patch from August. This is awful. The worst thing is to see them every month making a version with the current security patches but dont rolling them out. How hard could it be. Seriously, Honor has to improve this.
Click to expand...
Click to collapse
What more can i say? Just totally agree with you. Today i've read that Honor 8 Pro has received official beta Oreo in India, and we don't even know if we're in or out. We just know "the device is under testing phase". What the hell, i'm not an exited guy about updates and i know i shouldn't "expect" Oreo because usually Huawei/Honor just give one major update, but i can't give up to marketing needs. I can't believe and i can't give up to the idea that one day they could easily tell us that our device "hasn't passed the compatibility test" because we all know the our H8 can handle oreo on the hardware side. Even lower specs device can, why could our device be "incompatible"? Well, i think that a company has to put users first rather than money. If they made the same thing about H7 i can't trust them anymore and i will look to other companies.
P.s i know hat the CEO told H8 is in list to be updated, then removed this part...but without any official news at today i won't believe it.
P.P.s I know i bought a great device that works well and still better compared to other, in fact i'm not judging the product itself but the market strategy behind Honor products, wich should really be revisioned because you can't produce for example 10 device a year and fully support just few of them and for less time than they deserve.

I tried it by TWRP, i get error 7 on update.zip Someone know why?

I think this is the Spectre patch for this device. How b**tards the people are at Huawei/Honor that they can't release this critical security update for the Honor 8 (FRD-L09C432)!

The update is still Nougat with the Android patch level now at 1st January 2018. Attached is the screenshot from About Phone.

Anonshe said:
The update is still Nougat with the Android patch level now at 1st January 2018. Attached is the screenshot from About Phone.
Click to expand...
Click to collapse
You flashed it ? if so how.

Anonshe said:
The update is still Nougat with the Android patch level now at 1st January 2018. Attached is the screenshot from About Phone.
Click to expand...
Click to collapse
please tell us how you made to flash it. I tried it with TWRP and i bricked my phone :laugh:

Sheldd said:
please tell us how you made to flash it. I tried it with TWRP and i bricked my phone :laugh:
Click to expand...
Click to collapse
How did you brick your phone? I bricked my phone too when trying to flash B140 I was able to recover it only with DU Phoenix, nothing else worked xD

You could just proxy update to B398 via FF. It's the december security patch but better than nothing
Sent from my OnePlus5 using XDA Labs

Sheldd said:
please tell us how you made to flash it. I tried it with TWRP and i bricked my phone :laugh:
Click to expand...
Click to collapse
Just extracted the .img for UPDATE.APP then converted using simg2img and booted into recovery to use dd to copy to the right partition following the guide here

Rommco05 said:
Hi mate, when I try to use simg2img... What they mean, see attachement. thx
Click to expand...
Click to collapse
Code:
simg2img source.img destination.img
P.S. Please proceed with caution otherwise you may end up bricking.

Del

Lukke2804 said:
How did you brick your phone? I bricked my phone too when trying to flash B140 I was able to recover it only with DU Phoenix, nothing else worked xD
Click to expand...
Click to collapse
I tried to flash the update.zip in TWRP and i got error 7, then my phone bootloped, even with factory reset didnt worked. So i made wiped even the system partition, i flashed the recovery.img by ADB and after i flashed the service rom. I made the B131 rollback and updated back to B399. headache......

Sheldd said:
please tell us how you made to flash it. I tried it with TWRP and i bricked my phone :laugh:
Click to expand...
Click to collapse
The safest method is to use my Flashing Unapproved Firmwares guide. With it, you not only update the partitions but also the data partition.

hackslash said:
The safest method is to use my Flashing Unapproved Firmwares guide. With it, you not only update the partitions but also the data partition.
Click to expand...
Click to collapse
Can you post a link to your guide please?

Hey guys, some italian sites report that's EMUI 5.1 instead 5.0.1. Is that correct? I can't tell anything about because i haven't received the update yet

Oreo 8.1 out of Beta!!!

FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.

electrogiz said:
FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
Click to expand...
Click to collapse
Just got the OTA notification!

electrogiz said:
Just got the OTA notification!
Click to expand...
Click to collapse
I'll wait until I can manually flash.

Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.

Updating now!!!

dhorgas said:
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Click to expand...
Click to collapse
Already disappointed on the modem firmware front. No upgrade there. Also, no ability to force full-screen. Going to pass judgement on stand-by bug after 48 hour or so, unless obviously an issue.

The fact that it was not released to beta first makes me think it may just be an official release of the beta

crixley said:
The fact that it was not released to beta first makes me think it may just be an official release of the beta
Click to expand...
Click to collapse
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.

I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.

dhorgas said:
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
Click to expand...
Click to collapse
Hopefully. SoT and Deep-sleeps issues were horrendous!

epicbeardman911 said:
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
Click to expand...
Click to collapse
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are

tanker666 said:
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
Click to expand...
Click to collapse
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
E: Package is for source build essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but expected essential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys
Installation aborted.
Click to expand...
Click to collapse
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.

GospelNerd said:
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
Click to expand...
Click to collapse
I was in the same boat as you. I was on 8.1B1 rooted so I fastboot flashed the boot.img, then rebooted , downloaded the OTA which wouldn't install.
Went back to boot-loader, flashed the boot.img to both slots, rebooted, took OTA, and it still won't work. I get "couldn't update installation problem"
I didn't have an issue getting the last OTA, the same way.
I dunno
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....

NaterTots said:
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
Click to expand...
Click to collapse
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)

Wonder if Essential pushed it since Pixel is now offering pre release of Android P?

My radio has noticeably improved, instead of VZW its finally showing Verizon wireless. And the new developer options are nice

GospelNerd said:
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Click to expand...
Click to collapse
My install wasn't working either at first (same boat as you guys, Magisk rooted with custom kernel). At first I just did a Magisk uninstall and reboot but it wouldn't install. Thought maybe I still had a custom recovery installed, but there was no TWRP in recovery. So, I just did a sideload install of the 8.1 beta using adb and then rebooted. That put me back on stock 8.1b1 and retained all my settings/data. Then I made sure my settings were correct in developer options (USB debugging, etc.), and it's finally installing. Not sure, maybe I just didn't hold my mouth right the first couple times, but it's working now.

Can anyone tell me if stable has multitouch issues that were on beta?

Rooted 7.1.1 took the update just fine, lost root and twrp

Looking at META_INF\com\android\metadata, it's expecting essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but, based on the text at the top of the screen when sideloading, the device is at ssential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys. Changing it is pointless, since META_INF\MANIFEST.MF contains a SHA-256 hash of of the metadata file. I'm going to try recomputing the hash and updating the OTA zip.
Edit: Didn't work. But has someone on reddit confirm Jank4AUs situation.

September Update is out!!

https://www.essential.com/developer/current-builds
Also, just received it on my phone this very moment.

Downloading now! Came to post this exact thing.

UPDATE
Screen shot for those interested

changelog?

mookiexl said:
changelog?
Click to expand...
Click to collapse
Check the screenshot one post right before your!

Magisk install to inactive slot is supposedly fixed in the new version released a few days ago. Installing the OTA now. Will report back if it works.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
edit: hey it works

ziddey said:
Magisk install to inactive slot is supposedly fixed in the new version released a few days ago. Installing the OTA now. Will report back if it works.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
edit: hey it works
Click to expand...
Click to collapse
I'm stock rooted with elenentalX. Can I take the OTA now and just reroot and reflash after? Or do I need to unroot prior?

If I try to unroot by restoring images it says "Stock backup does not exist!"

sruel3216 said:
I'm stock rooted with elenentalX. Can I take the OTA now and just reroot and reflash after? Or do I need to unroot prior?
Click to expand...
Click to collapse
I believe you'd fail the OTA if you have an altered boot, but you can try.
oracleoftruth said:
If I try to unroot by restoring images it says "Stock backup does not exist!"
Click to expand...
Click to collapse
I dumped the old boot before rebooting just in case: https://drive.google.com/file/d/11MjB4kTOHuxbUyHe_kIwZ1d0wqp6-Nmf/view?usp=sharing
You can flash it to your boot slot while rooted, take the OTA, and then install magisk to the other slot before rebooting.
Drop a shell.
Determine current boot slot: getprop |grep boot.slot
Flash the boot: dd if=/path/to/boot_b.img of=/dev/block/by-name/boot_b (change to boot_a if that's your slot)
Of course, don't reboot since you'll lose root. Instead, you should now be able to take the OTA, and then use magisk to patch the other slot before rebooting.
Magisk should now have a backup for next time, so you can uninstall/ota/install in the future.

Nice...4 days in, and patched with the security update already.

ziddey said:
I believe you'd fail the OTA if you have an altered boot, but you can try.
Click to expand...
Click to collapse
Was curious cuz I was able to update the OTA on my pixel when rooted with custom kernel.

For some reason after I ran the magisk uninstaller and made sure to flash the stock boot image I still ran into problems updating via OTA and after sideloading the OTA for the Sept Update with success I found that TWRP would seem to freeze whenever it got to the main screen for some reason. I was able to use adb commands to reboot to bootloader and flash the stock kernel for the update and was able to boot normally. Just wondering if anybody else is having issues with TWRP freezing after installing the security update and yes I did remove fingerprint and lock screen security before booting into TWRP so I know its not something from that causing it to freeze.

Anyone try to Fastboot install the Sept update?
Tried 3 times and the screen was unresponsive every time after booting to setup
Finally went back to last months original P release and everything was as normal and updated from there...........

Just installed patch. Scrolling feels so much better, especially when scrolling slow.

gorm said:
Anyone try to Fastboot install the Sept update?
Tried 3 times and the screen was unresponsive every time after booting to setup
Finally went back to last months original P release and everything was as normal and updated from there...........
Click to expand...
Click to collapse
That's exactly what happened to me.. a user on /r/essential said they had the same issue; frustrating!
I'm going to be going back to 8.1 via fastboot, and then flashing 9.0 august, THEN fastbooting september, and if that doesn't work, I'm going to fastboot 9.0 august and then try OTA to
get my screen back.
Really weird stuff.
EDIT: Here's a supposed fix for those with the touchscreen issue - https://www.reddit.com/r/essential/comments/9d0lg3/for_anyone_having_trouble_with_touchscreen_not/
I don't know if we're allowed to link to reddit or not, but I'm doing that fix now.
Thanks!

my PH-1 is no longer recognizing my T-Mobile SIM.
i bought this used & my SIM worked fine up until OTA install. i've tried a different T-Mo SIM & it produces same Invalid SIM error.
the bootloader does show Variant = Sprint. i never did check the bootloader after I purchased it a little more than a month ago.
i'm currently reinstalling August 2018 Release via fastboot & see if that helps.
EDIT:
August 2018 Release resulted in no touch response & unable to progress through setup.
giving June 2018 Release (Oreo 8.1 ) a try via fastboot.
i just want a working phone back

jon_ybanez said:
my PH-1 is no longer recognizing my T-Mobile SIM.
i bought this used & my SIM worked fine up until OTA install. i've tried a different T-Mo SIM & it produces same Invalid SIM error.
the bootloader does show Variant = Sprint. i never did check the bootloader after I purchased it a little more than a month ago.
i'm currently reinstalling August 2018 Release via fastboot & see if that helps.
EDIT:
August 2018 Release resulted in no touch response & unable to progress through setup.
giving June 2018 Release (Oreo 8.1 ) a try via fastboot.
i just want a working phone back
Click to expand...
Click to collapse
Hey Jon,
Go ahead and take a look at my post I just made above yours. It might be able to help
Check the link out in the edit, I'm doing that process now to make sure I get my touchscreen back too.
Thanks!

beard805 said:
Hey Jon,
Go ahead and take a look at my post I just made above yours. It might be able to help
Check the link out in the edit, I'm doing that process now to make sure I get my touchscreen back too.
Thanks!
Click to expand...
Click to collapse
thanks for the info.
touchscreen works again but i still get an Invalid SIM message
i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community
thanks in advance

jon_ybanez said:
thanks for the info.
touchscreen works again but i still get an Invalid SIM message
i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community
thanks in advance
Click to expand...
Click to collapse
Sadly, I don't know much about the SIM side of the issue
Hope someone with more knowledge can chime in!

jon_ybanez said:
thanks for the info.
touchscreen works again but i still get an Invalid SIM message
i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community
thanks in advance
Click to expand...
Click to collapse
Are you rooted? Here are the unlocked modemst files: https://drive.google.com/file/d/1LQC-2QOC-PWX7vza-82tpwFrnUjaGZVq/view?usp=sharing
You can try to dd them:
Code:
dd if=/path/to/modemst1.img of=/dev/block/by-name/modemst1
dd if=/path/to/modemst2.img of=/dev/block/by-name/modemst2
Would be a good idea to backup your current images
from https://forum.xda-developers.com/essential-phone/how-to/discussion-brainstorm-sim-unlock-t3724135

[GUIDE] How to install Internal Android 10 build for Nokia 7 Plus

If you want to repost this internal OTA to other websites (other than XDA itself), please ask me for permission, thanks.
Click to expand...
Click to collapse
WARNING!
This is early internal test build, so LATER OTA UPDATES CAN'T BE GUARANTEED!
If you don't have unlocked bootloader, you'll unable to roll back to stable build!
Please be careful when testing!
Click to expand...
Click to collapse
Now I think it's time to bring you back to canary labs faster than beta labs.
Internal build version: B2N-4040-0-00WW-B01
It will be updated from: B2N-354K-0-00WW-B01, which is not pushed to public
As I've warned before - having an unlocked bootloader is strongly recommended.
So recent builds removed handy 874 dialing codes, we have to install them under recovery or Nokia Extensions.
Non-Chinese speaking users should ignore this quote.
中国用户如需从百度网盘下载，这些内测包发布在了诺记吧。
Click to expand...
Click to collapse
UPDATE: Thanks everyone. To fix microphone bug, please disable the microphone permission of the "Google" app.
You'll lose "OK Google" ability, but you can make telephone call properly.
Click to expand...
Click to collapse
Let me tell you how to verify:
1. Dial *#*#227#*#* to check current Version. If older than B2N-354J-0-00WW-B01 (check if the letter is greater than J), update to 354J before proceed.
FYI, 354J is August 2019 Security Update.
Alternately, you can use command "fastboot oem getversions" under fastboot mode / Download mode to check current firmware version.
If newer than 354J (probably 354N when this post released), you'll need to downgrade your phone back to at most 354H - which can't be done easily without unlocked bootloader.
2. Install B2N-354K-0-00WW-B01-354J-0-00WW-B01-update.zip with Nokia Extensions OTA Update module or adb sideload under recovery.
3. Reboot your phone.
4. Install B2N-4040-0-00WW-B01-354K-0-00WW-B01-update.zip with Nokia Extensions OTA Update module or adb sideload under recovery.
5. Reboot your phone.
That's it.
If minor fixes released, I will upload them as well, then use the same method to install it.
To root the phone, you may want to use Magisk 20 released today (October 12th, 2019) or newer.
Download link:
This thread is now deprecated.
https://android.googleapis.com/pack.../afd338bfb14d447b716c220424b2ad2c66213183.zip (B2N-410C-0-00WW-B03-update.zip)
https://www.androidfilehost.com/?w=files&flid=299363

could you please describe how to downgrade from 354M to 354H with unlocked bootloader? i have no idea...

About rollback to stable release
You said "it can't be easily done without unlocked bootloader"
Soz should ai consider the possibility of "it STILL can be done but with much difficulty " ???

Liftedcorn said:
About rollback to stable release
You said "it can't be easily done without unlocked bootloader"
Soz should ai consider the possibility of "it STILL can be done but with much difficulty " ???
Click to expand...
Click to collapse
For detailed, there's a backdoor left for customer care to allow them flash your phone with locked bootloader, but need to be elevated from server side, which can't be done by average person.

Oh .. thank you for the info.

Tried on TA-1055
Downgrade not permitted ?

ExaHamza said:
Tried on TA-1055
Downgrade not permitted
Click to expand...
Click to collapse
why did you want to downgrade? did you also try to flash the "old" rom to the other slot? https://forum.xda-developers.com/nokia-7-plus/how-to/finally-downgrade-phone-official-t3849437

well, okay, nokia extensions doesn't see the update zip (yes, superuser granted), sideloading doesn't work as it's asking for 354J version which i have. what am i doing wrong,
---------- Post added at 08:58 PM ---------- Previous post was at 08:36 PM ----------
ExaHamza said:
Tried on TA-1055
Downgrade not permitted ?
Click to expand...
Click to collapse
How did you manage to flash this? I simply can't, though I'm on version 354J aug patch

Bro you said we cant roll to stable version unless we have our bootloader unlocked ..
My question is can i flash stable android 10 when its released after flashing beta one ??

donjamal said:
well, okay, nokia extensions doesn't see the update zip (yes, superuser granted), sideloading doesn't work as it's asking for 354J version which i have. what am i doing wrong,
---------- Post added at 08:58 PM ---------- Previous post was at 08:36 PM ----------
How did you manage to flash this? I simply can't, though I'm on version 354J aug patch
Click to expand...
Click to collapse
Tried different ota packages on adb sideload and failed I'm on 00WW_354H_SP3

@hikari_calyx so how's Android 10 so far (build 4040) ?
Major bugs to be aware of ?
Nokia apps are ported already and working properly ?

so we'll never learn anything about this, will we? like we can't flash it (or at least i could not), no feedback if all good or if there are any major issues, nada. maybe i'm impatient

I'm running 4040 build and the only bug I have is the camera doesn't work...

Micahvdm said:
I'm running 4040 build and the only bug I have is the camera doesn't work...
Click to expand...
Click to collapse
So, we can expect an early surprise release for nokia 7 plus ?

Probably not...camera locks up most of the phone functionality...quite a few wakelocks too

Micahvdm said:
Probably not...camera locks up most of the phone functionality...quite a few wakelocks too
Click to expand...
Click to collapse
There's ONLY one bug of camera. And no other major bugs. And no daily life functionality is affected unless you do no other work with your phone except taking photos.( No offense ) ?
There might be a possibility that even after this camera bug is resolved, hmd might carry out extended testing and only release 10 at the time they've already mentioned.
Just a possibility.

Wakelocks are also a bit of an issue with regards to battery life...and I also work from my phone daily...not just used for camera, which is why I'm still on this build

Micahvdm said:
Wakelocks are also a bit of an issue with regards to battery life...and I also work from my phone daily...not just used for camera, which is why I'm still on this build
Click to expand...
Click to collapse
Oh. ?

Micahvdm said:
I'm running 4040 build and the only bug I have is the camera doesn't work...
Click to expand...
Click to collapse
Have you tried this magisk module for the camera ?
Found it on N7P Telegram group
It contains 3 libraries related to camera2 and a SEpolicy rule.
CamFix-Android10.zip

The fix doesn't work and the selinux thing was my discovery. Not a single freeze since. Camera remains broken. Still working on a fix

october security update Android 9 Mi A2 Lite

So I just received a new security update, I don't think there's anything more than just the latest security package

same here, just 65 MB. couldn't find any new features yet.

Scrolling is definitely smoother.

It seems like booting up takes shorter time to load unlike with the previous update patches.

any improvements in unlock speed?

Did they bring back d2tw?

loop4444 said:
any improvements in unlock speed?
Click to expand...
Click to collapse
Phone is somewhat smoother / faster in general.
coolwei1 said:
Did they bring back d2tw?
Click to expand...
Click to collapse
Nope.

stuck
I am stuck on september update, everytime i try to install the october update it says installation problem (i have an unlocked bootloader) what to do i am a newbie when it comes to tinkering with android on this level.

peshovich said:
I am stuck on september update, everytime i try to install the october update it says installation problem (i have an unlocked bootloader) what to do i am a newbie when it comes to tinkering with android on this level.
Click to expand...
Click to collapse
Same here. Maybe it's because I'm rooted...
I'm waiting for the next (official) fastboot image...

downloadonlyaccount said:
Same here. Maybe it's because I'm rooted...
I'm waiting for the next (official) fastboot image...
Click to expand...
Click to collapse
Well at least i am not alone in this one, hopefully Xiaomi will fix this issue and we can update it normally. Gonna follow this thread.

Especially if you've rooted, you probably have modified system or vendor partitions.
You can see what the OTA doesn't like by looking at adb.
Code:
adb logcat | grep update_engine
There's been no 10.0.14.0 fastboot image but I do have backups of these partitions I made myself. They're huge but I might be able to get them on the internet if needed...

peshovich said:
Well at least i am not alone in this one, hopefully Xiaomi will fix this issue and we can update it normally. Gonna follow this thread.
Click to expand...
Click to collapse
So, now with 10.0.16.0 released, I was able to skip the .15 version. I had to download the complete package (around 1 GB) but now I'm on latest version. Just need to root again .
'