Related
Anyone used ChainFire's FlashFire with the One A9?
I've used it for backups successfully but have yet to restore anything with it (a little squeamish to do so :silly.
And I'll just add, if anyone has used it and could offer any tips or procedures that would be great.
FlashFire usage is straightforward, at least for me. I haven't flashed anything dangerous with it directly (bootloader, radio) yet.
It has handled flashing backups of system, boot, recovery, and even the 1.57.617.41 ota flawlessly.
Special thanks to @Chainfire!
Sent from my HTC One A9 using XDA Free mobile app
CSnowRules said:
FlashFire usage is straightforward, at least for me. I haven't flashed anything dangerous with it directly (bootloader, radio) yet.
It has handled flashing backups of system, boot, recovery, and even the 1.57.617.41 ota flawlessly.
Special thanks to @Chainfire!
Sent from my HTC One A9 using XDA Free mobile app
Click to expand...
Click to collapse
Were you already rooted? I'm rooted and xposed and want to update via flashfire. will it work?
theNdroid said:
Were you already rooted? I'm rooted and xposed and want to update via flashfire. will it work?
Click to expand...
Click to collapse
Of course. Root is required to use FlashFire. I use Xposed as well, and I've had no problems updating via FlashFire.
CSnowRules said:
FlashFire usage is straightforward, at least for me. I haven't flashed anything dangerous with it directly (bootloader, radio) yet.
It has handled flashing backups of system, boot, recovery, and even the 1.57.617.41 ota flawlessly.
Click to expand...
Click to collapse
Just for my edification, flashing a firmware update like 1.57.617.41 will wipe my data partition, correct?
eelpout said:
Just for my edification, flashing a firmware update like 1.57.617.41 will wipe my data partition, correct?
Click to expand...
Click to collapse
No not at all. Flashing the OTA will not wipe your data. I've done the .41 and .52 OTAs via FlashFire.
***Warning--if you're not currently encrypted, flashing the OTA will update your boot partition, so be sure to use the preserve recovery option in FlashFire and reboot to TWRP to patch your boot image, or your device will encrypt data on first boot.***
CSnowRules said:
No not at all. Flashing the OTA will not wipe your data. I've done the .41 and .52 OTAs via FlashFire.
***Warning--if you're not currently encrypted, flashing the OTA will update your boot partition, so be sure to use the preserve recovery option in FlashFire and reboot to TWRP to patch your boot image, or your device will encrypt data on first boot.***
Click to expand...
Click to collapse
meaning, flash this A9 boot image patcher from TWRP?
Or does using the EverRoot SuperSU option patch the boot image for us on the A9 (and then does one check "preserve recovery" using that or not)?
This can all get a bit confusing.
eelpout said:
meaning, flash this A9 boot image patcher from TWRP?
Or does using the EverRoot SuperSU option patch the boot image for us on the A9 (and then does one check "preserve recovery" using that or not)?
This can all get a bit confusing.
Click to expand...
Click to collapse
Yes, that's one way to disable forceencrypt. You could also flash the latest SuperSU or Magisk. Either one will disable forceencrypt by default. Of course, if your data is already encrypted, you won't have a problem, but I'd assume that you would like to have root, so I'd recommend SuperSU or Magisk+phh root.
CSnowRules said:
Yes, that's one way to disable forceencrypt. You could also flash the latest SuperSU or Magisk. Either one will disable forceencrypt by default. Of course, if your data is already encrypted, you won't have a problem, but I'd assume that you would like to have root, so I'd recommend SuperSU or Magisk+phh root.
Click to expand...
Click to collapse
i'm already unecrypted and rooted, but on firmware from last year. just trying to find the most efficient way to bring things up to date.
eelpout said:
i'm already unecrypted and rooted, but on firmware from last year. just trying to find the most efficient way to bring things up to date.
Click to expand...
Click to collapse
Ok, this post will go a bit off topic. That being said, I can offer two courses of action. I take no responsibility for anything in this post.
Safest--almost no risk (my personal preference)
1. Backup your data partition, including internal SD via TWRP to ext SD or USB OTG drive. Flash the latest RUU from HTC. Boot stock and apply OTAs until there are no more updates available. Fastboot flash the latest TWRP, and finally restore your data and flash the latest SuperSU via TWRP. Reboot your fully updated, rooted A9 with all your data still intact.
A little risky and untested to my knowledge--could result in a hard brick if something partially fails. FLASHING BOOTLOADERS IN FLASHFIRE IS STILL ALPHA FOR HTC DEVICES!!! This may work with s-on...but may require s-off.
Your system partition must have never been mounted r/w for this to work.
2. Download the OTA zips for your phone from the first update available to the latest and the latest SuperSU and TWRP. Use FlashFire to do everything in one shot. Select allow flashing bootloaders in FlashFire settings, select your OTAs for installation from oldest to newest (don't select restore boot and recovery), select TWRP and SuperSU for installation, disable everroot and preserve recovery. Cross your fingers and timidly press flash... If all is successful, you should have the same end result as option 1.
I STRONGLY recommend the first method, but if you're feeling lucky and decide to try the second method, please share how it goes, since this post is FlashFire related and this would be the ultimate test of FlashFire for our devices.
For me, I've found that though TWRP backups take more time, and DON'T preserve internal storage, it's still the most reliable and consistent way to backup especially for OTAs.
I've previously tried FlashFire restore but it doesn't seem to restore internal storage as claimed; deal-breaker.
The real problem is we want OTA automation to:
1) disable lock-screen (pattern or fingerprint) so emergency restore of /data don't fail to unlock after boot
2) restore OEM recovery
3) flash OTA and let it do its things of updating /system, /boot, etc
4) reflash SuperSU before normal system boot so /boot doesn't try to re-encrypt /data
5) restore whatever the original recovery was
6) boot
The problem always is catching the step between 3 -> 4 in some automated way. If the OTA goes all the way through, /data is encrypted and so time is wasted to go back to recovery after full-boot, wipe /data, restore /data, lost internal storage contents and PICTURES. If pattern-lock / finger-print lock is not disabled (1), you won't be able to get past the lock screen as it won't recognize the correct lock-pattern nor fingerprint. Solution is to adb shell in, and move/delete some files as root. PITA and I don't think FlashFire does this.
If you did manually restore /data, then /data is corrupted for some apps that use it such as Waze, LINE, KakaoTalk, Whatsapp, etc where they can't write to their data directories anymore. A reinstall of the app is the only way to fix it.
NuShrike said:
For me, I've found that though TWRP backups take more time, and DON'T preserve internal storage, it's still the most reliable and consistent way to backup especially for OTAs.
I've previously tried FlashFire restore but it doesn't seem to restore internal storage as claimed; deal-breaker.
The real problem is we want OTA automation to:
1) disable lock-screen (pattern or fingerprint) so emergency restore of /data don't fail to unlock after boot
2) restore OEM recovery
3) flash OTA and let it do its things of updating /system, /boot, etc
4) reflash SuperSU before normal system boot so /boot doesn't try to re-encrypt /data
5) restore whatever the original recovery was
6) boot
The problem always is catching the step between 3 -> 4 in some automated way. If the OTA goes all the way through, /data is encrypted and so time is wasted to go back to recovery after full-boot, wipe /data, restore /data, lost internal storage contents and PICTURES. If pattern-lock / finger-print lock is not disabled (1), you won't be able to get past the lock screen as it won't recognize the correct lock-pattern nor fingerprint. Solution is to adb shell in, and move/delete some files as root. PITA and I don't think FlashFire does this.
If you did manually restore /data, then /data is corrupted for some apps that use it such as Waze, LINE, KakaoTalk, Whatsapp, etc where they can't write to their data directories anymore. A reinstall of the app is the only way to fix it.
Click to expand...
Click to collapse
The solution for problem 1 can be handled in TWRP. The files can be deleted via TWRP's file manager or the built in terminal, which may be easier for some people.
Also, the solution for the corrupted data and internal SD is to create an image of the data partition (just like the system image backup option). This can be done via dd in TWRP or adb. It requires a large amount of storage and it takes longer, but I've had to do it, since I use VIP Access by Symantec for work. A normal file based backup in TWRP breaks that app. This also keeps the pin/fingerprint data intact.
If we could have that implemented in a user friendly manner, that would be great, but I'm sure CaptainThrowback and Chainfire both have bigger issues to deal with. I could probably figure out a solution, but the work wouldn't be worth it for my own benefit, since I'm fluent with the Linux command line.
Hi all!
Today i had to reset my phone (Magisk's fault) and therefore i installed Android O (with Funky Huawei -> should be a clean installation).
Bootloader is unlocked, TWRP and SuperSU is installed, but the internal storage is encrypted... TWRP file explorer shows random hashed files in internal storage and TWRP backup is not possible (createTarFork() ... Error: 255).
How can i decrypt my internal storage?
Is there also a decrypted boot image like before?
Hope anyone can help me...
Best regards,
Florian
So I went back to Nougat and B198 to encrypt the data partition...
But I am still interested in encrypting Android 8 for future updates.
Is there a way o do yet?
htcdesire-hd said:
So I went back to Nougat and B198 to encrypt the data partition...
But I am still interested in encrypting Android 8 for future updates.
Is there a way o do yet?
Click to expand...
Click to collapse
Yes. /vendor/etc/fstab.hi3660
Open file in a text editor (root enabled) and change:
'fileencryption=aes-256-xts:aes-256-cts' to 'encryptable'
Save file. Now you should be able to decrypt. You can remove verity and avb flags as well in that fstab.
To encrypt again, add the fileencryption flag back again and reboot.
ante0 said:
Yes. /vendor/etc/fstab.hi3660
Open file in a text editor (root enabled) and change:
'fileencryption=aes-256-xts:aes-256-cts' to 'encryptable'
Save file. Now you should be able to decrypt. You can remove verity and avb flags as well in that fstab.
To encrypt again, add the fileencryption flag back again and reboot.
Click to expand...
Click to collapse
can i make it? is it neccessary? And im running oreo b361, if i want to make decyript, will i format my phone?
mavera said:
can i make it? is it neccessary? And im running oreo b361, if i want to make decyript, will i format my phone?
Click to expand...
Click to collapse
Yes, no, partially.
You do need root. Decrypting, in my opinion, is not necessary. It's only good if you want to backup /data (I'd use titanium backup). Decrypt will format /data, which essentially is your phone. That's where all userdata is kept (all playstore apps, data, etc etc) so I would back those up using titanium backup or Huawei backup, then copy sdcard as well.
@ante0 thank you for your answer!
I made the experience that root apps are not working properly (changes in data partition are not permanently and will be lost after a reboot) when the data partition is not decrypted...
htcdesire-hd said:
@ante0 thank you for your answer!
I made the experience that root apps are not working properly (changes in data partition are not permanently and will be lost after a reboot) when the data partition is not decrypted...
Click to expand...
Click to collapse
Hmm. Then something else is wrong. Data is only encrypted, but it's not protected by avb or verity, so it shouldn't revert at all.
What were you changing if you remember?
ante0 said:
Hmm. Then something else is wrong. Data is only encrypted, but it's not protected by avb or verity, so it shouldn't revert at all.
What were you changing if you remember?
Click to expand...
Click to collapse
E.g. I removed the WhatsApp shutter sound file (/system/media/audio/ui/camera_click.otg) but after rebooting with encryption the file was there again and with decryption everything worked... This happened about a year ago and therefore I have always been decrypting until now...
Is there a disadvantage if the phone is decrypted?
htcdesire-hd said:
E.g. I removed the WhatsApp shutter sound file (/system/media/audio/ui/camera_click.otg) but after rebooting with encryption the file was there again and with decryption everything worked... This happened about a year ago and therefore I have always been decrypting until now...
Is there a disadvantage if the phone is decrypted?
Click to expand...
Click to collapse
/system is protected by verity though, if you didn't remove the verity flag it does revert things.
No real disadvantage. You still need to unlock bootloader after updating (might not be needed when you go oreo to oreo, my bootloader stayed intact when I went from B329 to b361), which requires formatting data. So you still need to redo the decryption when you update.
ante0 said:
/system is protected by verity though, if you didn't remove the verity flag it does revert things.
No real disadvantage. You still need to unlock bootloader after updating (might not be needed when you go oreo to oreo, my bootloader stayed intact when I went from B329 to b361), which requires formatting data. So you still need to redo the decryption when you update.
Click to expand...
Click to collapse
Ok thank you for your answer! I will try to remove verity flag and keep the phone encrypted, when Oreo is officially released.
EDIT:
I upgraded to Android 8 and rooted my Mate 9 and everything seems to work now. I did not test the decryption so far...
ante0 said:
Yes. /vendor/etc/fstab.hi3660
Open file in a text editor (root enabled) and change:
'fileencryption=aes-256-xts:aes-256-cts' to 'encryptable'
Save file. Now you should be able to decrypt. You can remove verity and avb flags as well in that fstab.
To encrypt again, add the fileencryption flag back again and reboot.
Click to expand...
Click to collapse
My device is rooted, but i can not write into system partition ("/system/app mover" app shows an error that it can't remound /system)...
How can i enable writing to the /system partition?
By removing the verity flag in fstab? How do i manage to do that?
ante0 said:
Yes. /vendor/etc/fstab.hi3660
Open file in a text editor (root enabled) and change:
'fileencryption=aes-256-xts:aes-256-cts' to 'encryptable'
Save file. Now you should be able to decrypt. You can remove verity and avb flags as well in that fstab.
To encrypt again, add the fileencryption flag back again and reboot.
Click to expand...
Click to collapse
Hi ante0,
As I am total noob on this matter, just one question to make sure:
Do I remove the whole fileencryption=....-cts part and replace it with the text encryptable?
Regards,
Dioky said:
Hi ante0,
As I am total noob on this matter, just one question to make sure:
Do I remove the whole fileencryption=....-cts part and replace it with the text encryptable?
Regards,
Click to expand...
Click to collapse
Yes.
wait,check,fileencryption=aes-256-xts:aes-256-cts
Should say
wait,check,encryptable
Or you can just remove it so it just says
wait,check
Troubles again and sweet victory
ante0 said:
Yes.
wait,check,fileencryption=aes-256-xts:aes-256-cts
Should say
wait,check,encryptable
Or you can just remove it so it just says
wait,check
Click to expand...
Click to collapse
It worked, but I ran into trouble again: bootloop.
This time it was my bad because I forgot to re-flash update_data_public.zip and update_all_hw.zip after the Format Data... :cyclops:
When I realised the mistake I made, I tried to make up for it by TWRP-flashing both files.
During flashing I got a few errors in red text that frightend me.
In hindsight I should have neglected them, but I tried to reflash and from that on I ran into trouble.
Because I wanted to have a nice clean install, I decided to return to base and reflash the whole stock ROM with HWOTA8 procedure.
Next I started to look around on the net for another more experiences. That led my to the German Firedance1961.
He wrote an elegant script for the latest Oreo build 363, which automates some tweaks during the flashing process.
As ante0 suggested, that script indeed does leave blank after 'wait,check'
It adds a GPS tweak, SuperSU v2.82, Busybox, AdAway, some theme-options and decrypts DATA partition that stays decrypted after reboot. All in one go.
The process for those interested:
Needed:
Unlocked bootloader.
Steps:
1. Put update_data_public.zip and update_all_HW.zip from the L09/L29B363 ROM together with the Firedance FSTAB-mod script in the root of your external SD-card;
2. Flash TWRP 3.2.1-0 Oreo with Fastboot
3. Boot into TWRP and perform Format DATA. STAY IN TWRP and return to TWRP Install menu;
4. Now flash in this order:
I. update_data_public.zip;II. updata_all_hw.zip;You'll see some red errors during the process. Don't worry.
III. Firedance FSTAB-mod script.From this moment on you can backup DATA partition in TWRP.
5. Wipe cache and Dalvic
6. Reboot, done.
Regards,
will try that Firedance, got same problem with encryption
Firedance FSTAB-mod script - link is dead or file removed.
Because on https://twrp.me/google/googlepixel.html it says:
Decrypting Android 9.0 Pie when using a PIN / pattern / password does not work yet. We do not have an ETA for fixing decrypt. Restoring a backup made with an alpha using RC1 may result in loss of data including internal storage. If you need your backups from those versions, restore the backup using alpha2, then install RC1 and run a new backup with RC1.
Click to expand...
Click to collapse
I just flashed the official Android 9/P/Pie release (it did not fix the randomly dying microphone issue) and I want to do a full nandroid backup before I take my Pixel into UBreakIFix for a $0-80 fix because they require a locked bootloader and factory reset.
So do nandroid backups work or not?
SOLVED!
Answering my own question...
roirraW "edor" ehT said:
Since internal storage, where user apps and user and system app data are stored can't be decrypted, you'd definitely have to at least disable the pin/pattern/password, although you should confirm that doing so makes the storage readable in TWRP - it should.
Click to expand...
Click to collapse
According to this person, you must disable pin/pattern/password in order to decrypt the file system and allow nandroid backup & restore.
However, I just did a fastboot boot TWRP.img and it prompted me with my unlock pattern, and then it said "Data successfully decrypted". I checked, and I have access to the filesystem, and it even mounted to my connected laptop. So I'm testing this out. Backups completed successfully. I'll be trying a restore soon.
Archangel said:
The overwhelming response to what areas to tick when you back up has been system, boot, vendor and data,,,no images just the partitions. But that struggle is still on going LOL.
Click to expand...
Click to collapse
Backup & restore these 4 partitions (no images):
System, Boot, Vendor, and Data
(Note: for system and vendor you have to uncheck "mount system as readonly")
UPDATE:
Restoring my System and Vendor TWRP backups caused boot to hang at the G logo with an endless progress bar below the G.
However, doing a fastboot flash of System and Vendor factory images then restoring only my TWRP Data backup successfully restored my phone!
Except for one issue: fingerprints don't work. I think I may have screwed myself here by not disabling pin/pattern/password when I did the backup. For some reason TWRP had no problem decrypting then. But now, trying to restore, TWRP can't decrypt unless I disable pin/pattern/pass. It wont let me delete my old fingerprints or set new ones. Trying to unlock with fingerprint, it either doesn't respond at all or says "Fingerprint hardware not available"
UPDATE 2:
Followed instructions to clear the fingerprint data: [Guide] Delete fingerprint profils via TWRP. Everything is perfectly restored now! (Note: if you disable pin/pattern/pass before backup, you shouldn't need to do this)
So I've been trying to debloat my OP6 on OOS 9.0 official using TWRP. This is what I did:
Installed a fresh copy of OOS 9 through fastboot.
Booted up into the OS to set up my apps.
Booted into TWRP via fastboot and flashed TWRP installer zip.
In Slot B, mounted system partition and deleted folders for several system apps manually (e.g. Google Play Music, YouTube, etc.) -- folder path shows /system/system/app/ & /system/system/priv-app/.
Rebooted to Slot A in TWRP and repeated the previous step.
Mounted data partition and removed any update files under /data/app/ for the apps listed above.
Rebooted to system.
Confirmed system apps not deleted. Rebooted to TWRP in each slot to check that the apps did not show up again under /system/system/app/ & /system/system/priv-app/. Indeed they were not there.
Even after doing all this, the system apps are not removed in the OS, nor are they removable.
i've read a lot about A/B partitions, and I understand how they work. So then where are the system apps stored? Is there something else I'm missing to be able to properly debloat OOS without root? (I can't root due to my corporate email policy)
Isn't just easy enough to disable the apps from the os?
whizeguy said:
Isn't just easy enough to disable the apps from the os?
Click to expand...
Click to collapse
Yes but I'm actually trying to convert some of them to user apps so I can set some to not be battery optimized by the system.
Step 0: introduction
Hello everyone. As you may or may not know, after unlocking, rebranding, updating and patching our P9's, we can now install a part of a big universe of brand new Treble ROMs into our devices. An example of that kind of ROMs is the OpenKirin team's AOSP-based ROMs, AndyYan's LineageOS or phhusson's Phh-Treble for a barebones pure Android experience.
But that experience so far is far from perfect. Aside from Q ROMs not booting yet on hi3650 devices like ours, some features may be missing such as camera support, GApps or [insert favorite mod here] which come in the form of flashable zips. A major problem now is that our phone's internal storage must always be encrypted at every ROM install. This poses some problems such as:
* Having to install Huawei's stock recovery every time you need to do a factory reset otherwise your brand new ROM is not booting when you wipe with TWRP.
* Not being able to flash ZIPs in TWRP from the internal storage.
* Having to install custom ROMs by flashing to /system through fastboot which is slow and can be interrupted
* On a fresh ROM boot, the phone takes extra time to encrypt and then on every subsequent boot it will take longer to boot.
Encryption brings extra security, but at the cost of usability and speed. Luckily for us, it can be disabled in favor of having a more traditional custom ROM + TWRP flashing workflow. This can be done by editing a fstab file in our device's vendor partition. Once the procedure is done you will be able to:
* do factory resets from TWRP without problems
* mount internal storage in TWRP and flash ZIPs without problems
* not need to juggle .img files to switch recoveries because everything will be possible from TWRP
Note: This effect is permanent. No need to do it again. You can also easily reverse it manually.
WARNING: YOUR INTERNAL STORAGE MUST BE WIPED CLEAN. BACKUP ANY IMPORTANT DATA TO AN EXTERNAL STORAGE BEFOREHAND. YOU WILL LOSE ALL YOUR FILES AND APPS.
Note: If you ever decide to reflash your stock EMUI firmware, remember that your device will be re-encrypted. If you get stuck at the boot logo after going back to EMUI from a decrypted device, reboot manually to recovery, do a factory reset in the stock recovery and try again.
Required:
* A backup of your important data
* A computer
* working Android install with root
* A working ADB/fastboot environment
* A USB-C cable with data connections
* Pretoriano80's TWRP for Treble-enabled Huawei P9
Your ROM, custom kernels and Magisk will survive the procedure. Don't worry about them.
Step 1: Modify the vendor fstab
Using MiXplorer, navigate to /vendor/etc. We're going to modify the fstab.f2fs.hi3650 file. Back it up in your SD card, because the internal storage will be wiped clean so if you mess the process up you don't want to lose it. Now open the original file with a text editor and edit it, go to the line that contains /data and change the forceencrypt word to encryptable.
Step 2: Flash TWRP
Through Fastboot, install Pretoriano80's TWRP. This is the best TWRP available for our device.
Code:
# fastboot flash recovery_ramdisk twrp.img
For the next step, we need to reboot to the recovery.
Code:
# fastboot reboot recovery
Step 3: Format internal storage
On TWRP, back your internal storage up if you haven't already. This is your last chance to do a backup.
After that, wipe your internal storage. Go to Wipe -> Format Data and confirm. The deed is done.
Now boot your system. ROMs should no longer push their encryption on you, and you can now mount the internal storage in TWRP.
Wattsensi said:
Step 2: Modify fstab and format /data
Click to expand...
Click to collapse
This part is confusing, how to modify fstab?
copy pasted a guide from other users. You shouldnt modify anything and the decryption is a one time story, it breaks after first use.
I tested it on my P9 Plus & it worked man, thank you so much <3
dkionline said:
copy pasted a guide from other users. You shouldnt modify anything and the decryption is a one time story, it breaks after first use.
Click to expand...
Click to collapse
1. No, it doesn't. I tried switching between several "Open"Kirin ROMs and GSIs using a TWRP flash+factory reset workflow, it works well.
2. This entire forum is either sparse solutions spread in deep crevices or hacks from juggling files and editing words in text...surely the guides are so unique, reformatting /data after removing its forceencrypt attribute in /etc/fstab is so unique and special! I'm not trying to throw down zgfg's effort but again, that guide was confusing and required juggling three TWRP copies. I'm just trying to make anyone unfortunate enough to still need to have one of these devices to be able to lessen the pain in the behind that is working with ancient unmaintained Treble implementations, buggy sdcardfs drivers, obscure camera interfaces, broken audio routing and drivers, and secretive ROM cooks who won't share their secret fixes restricting the universe of good ROMs to their own proprietary ROMs that don't get updated, or get updated once every 6 months. Sadly I don't have the time or resources to set a build farm or cook my own ROMs (you probably already know, hundreds of GBs downloaded and 6GB+ of RAM used) Please don't be like this, I like your work.
md sabuj said:
This part is confusing, how to modify fstab?
Click to expand...
Click to collapse
With TWRP, mount /vendor. Then, use TWRP's ADB shell capabilities. Open a command prompt in your computer, and type 'adb shell' and enter. Then, navigate to /vendor/etc/, with the command 'cd /vendor/etc'. Then using vi or nano, edit the fstab.hi3650 file.
Look for the entry that starts with /data. Replace in the same line, 'forceencrypt' with 'encryptable'. Then save, wipe /data and reboot. Remember to investigate thoroughly for consequences and side effects on everything you do.
Btw, developing discussion and instructions from early 2019 about decrypting Data and Internal memory on P9 Oreo - decryption can be done also by use of TWRP instead of manually editing fstab:
https://forum.xda-developers.com/p9/how-to/emui-8-decryption-guide-wipe-t3906245
And a revised summary:
https://forum.xda-developers.com/showpost.php?p=80029346&postcount=1843
They were not necessarily targeting GSI but (at that time) OpenKirin ROMs.
Also, doesn't matter if for EVA AL10, DL00, etc.
Also for stock EMUI 8, but to be able to fully use TWRP (nandroid backup, wiping Dalwik - it's on Data partition, installing zip or img files from Internal memory instead from SD card)
Btw, instead of Terminal and Vi editor (for most of nowadays users their parents were not born yet in the era of pre-WYSIWYG editors, and I doubt if 0.1% would be familiar to navigate with Vi to a particular line and to delete/replace or insert something), one can simply use standard tools like MiXPlorer (root explorer) with its integrated text editor.
In MiXPlorer choose Root, grant the root access, visually navigate to /vendor/etc, click on fstab.hi3650 file, open as Text and edit without frustrations like with Vi editor ?
zgfg said:
Btw, instead of Terminal and Vi editor (for most of nowadays users their parents were not born yet in the era of pre-WYSIWYG editors, and I doubt if 0.1% would be familiar to navigate with Vi to a particular line and to delete/replace or insert something), one can simply use standard tools like MiXPlorer (root explorer) with its integrated text editor.
In MiXPlorer choose Root, grant the root access, visually navigate to /vendor/etc, click on fstab.hi3650 file, open as Text and edit without frustrations like with Vi editor ?
Click to expand...
Click to collapse
Thanks for that, I revised and simplified the guide as much as possible.
btw, my P9 is now a secondary device meaning that I can experiment a little more on it. I can't build ROMs for now but will try to create a barebones kernel with useful features.
Wattsensi said:
Thanks for that, I revised and simplified the guide as much as possible.
btw, my P9 is now a secondary device meaning that I can experiment a little more on it. I can't build ROMs for now but will try to create a barebones kernel with useful features.
Click to expand...
Click to collapse
You have ECOKernel by @dkionline for Oreo
zgfg said:
You have ECOKernel by @dkionline for Oreo
Click to expand...
Click to collapse
I know, I am using it right now and it's a good kernel but I'd like to add some more things like lower minimum brightness, voltage control for undervolting and AutoSMP hotplugging. It runs pretty hot and the IPS display backlight burns my eyes even on the lowest setting
Can I use this method to decrypt P9 installed EMUI8?
md sabuj said:
Can I use this method to decrypt P9 installed EMUI8?
Click to expand...
Click to collapse
@ant0nwax and me did use decrypted storage with b540, see the post #6 above:
https://forum.xda-developers.com/showpost.php?p=83386207&postcount=6
Specially, look at the second post linked there (post was in HWOTA7 thread):
https://forum.xda-developers.com/showpost.php?p=80029346&postcount=1843
There was one catch there (was written for b540):
zgfg said:
Reboot to TWRP and perform the following, in this order:
- Wipe, Swipe to factory reset (not Advanced Wipe, neither Format Data)
- Install three ZIPs (all ogether, in queue): update_data_full_public.zip (from b540 download), b540-update_full_EVA-AL10_all_cn.zip (from b540 download, but fixed by Tecalote to be flashable by TWRP) and Enable-Huawei-OTA.zip (from Tecalote's OP instructions)
Click to expand...
Click to collapse
If I recall correctly after the long time ,(year and a half) - when you format Data you have to restore your b550 part that was installed to Data.
You must not use eRecovery bcs it would encrypt Data again.
Hence you must flash b550 by TWRP and there was a problem with that all_cn zip at that time, reporting me an error (cannot find now TWRP logs from that time to see what was the problem)
I discussed then with @Tecalote and he corrected me the script from the original update all_cn zip for b540 that TWRP was able to flash
As a result, we had EMUI 8, b540 with decrypted storage, giving to TWRP the full access to Data and Internal memory
It was also possible to go back to EMUI 8 with encrypted storage, basically by putting back stock Recovery, by installing latest firmware from eRecovery and by performing Factory reset with Wiping the cache
@Wattsensi: unfortunately, It doesn't work like this in my case. After switching to Chinese EMUI 8, I install Play Store, login to my Google Account and do Play Store things.
After modifying that file in Vendor, I go to recovery, wipe internal storage, wipe Data and restart.
At this moment, it's like after a factory reset, I have to start all over again, but I'm not encrypted.
Well, no matter what I do, I can't login to Google. I open Play Store, it tries to log me in ( the big circles started to spin), at that moment Play Store closes. I go to Accounts and try to login to my Google account from there, same thing. So, for me, Emui 8 is usable only before decryption.
I'm wondering if I'm doing something wrong.
Nightwish1976 said:
@Wattsensi: unfortunately, It doesn't work like this in my case. After switching to Chinese EMUI 8, I install Play Store, login to my Google Account and do Play Store things.
After modifying that file in Vendor, I go to recovery, wipe internal storage, wipe Data and restart.
At this moment, it's like after a factory reset, I have to start all over again, but I'm not encrypted.
Well, no matter what I do, I can't login to Google. I open Play Store, it tries to log me in ( the big circles started to spin), at that moment Play Store closes. I go to Accounts and try to login to my Google account from there, same thing. So, for me, Emui 8 is usable only before decryption.
I'm wondering if I'm doing something wrong.
Click to expand...
Click to collapse
This is indeed strange, and I do not recall the Chinese ROMs having Google services by default, you had to install GApps if I'm not wrong. Try flashing pico OpenGapps for 8.0 ARM64, wiping cache and doing a factory reset again. Sometimes GApps have issues when you don't flush the cache between fresh installs.
https://opengapps.org/
Nightwish1976 said:
Unfortunately, It doesn't work like this in my case. After switching to Chinese EMUI 8, I install Play Store, login to my Google Account and do Play Store things.
After modifying that file in Vendor, I go to recovery, wipe internal storage, wipe Data and restart.
At this moment, it's like after a factory reset, I have to start all over again, but I'm not encrypted.
Well, no matter what I do, I can't login to Google. I open Play Store, it tries to log me in ( the big circles started to spin), at that moment Play Store closes. I go to Accounts and try to login to my Google account from there, same thing. So, for me, Emui 8 is usable only before decryption.
I'm wondering if I'm doing something wrong.
Click to expand...
Click to collapse
Wattsensi said:
This is indeed strange, and I do not recall the Chinese ROMs having Google services by default, you had to install GApps if I'm not wrong. Try flashing pico OpenGapps for 8.0 ARM64, wiping cache and doing a factory reset again. Sometimes GApps have issues when you don't flush the cache between fresh installs.
https://opengapps.org/
Click to expand...
Click to collapse
Be careful. Chinese EMUI 8 does come with Google Play Services (OP posts in HWOTA7 thread) and one only needs to install Google Play app.
Google Play Services were also preinstalled for users who recently updated to b550.
Btw, you didn't write are you on Al10c00b550 or what, but you also wrote that you had Playstore working on EMUI 8 before decrypting and formatting Data
Anyway, before installing MicroG, Open GApps or something, inspect do you still have or not Google Play Services installed.
There are apps like Play Services Info to inspect if Google Play Services, Google Services Framework and Google Play Store are installed (and what are their versions).
E.g, use this app from ApkMirror (since you cannot look for them and install from Playstore):
https://www.apkmirror.com/apk/weberdo/play-services-info/
(Not sure would it work installing Open GApps if stock Google Play Services are still beneath)
Thank you, guys gor your help. Yes, Ch EMUI comes with Google Play Services, one normally has to install only Google Play.
At the moment I'm just setting up my phone with the Lineage OS MicroG Pie ROM and I'm really enjoining it, but as soon as I decide to try something else, I'll put your suggestions to use.