Hi guys, I have a problem installing the STF-L09C432B150 update...
I got my Honor 9 yesterday. First, I had a look if there are any updates available. The system updater didn't find anything, so I proceeded to root the device, which I finally managed by unlocking the bootloader, flashing TWRP and installing Magisk. Afterwards, I inserted the SIM card and was greeted with a new update message: STF-L09C432B150 is available to enable VoLTE and VoWLAN. I guess it didn't show this update before because I didn't insert a SIM card...
So I flashed the original Huawei recovery and tried to install the update, but every time it fails at around 19% without a specific error message... does someone have a clue what could be the problem here? I couldn't find any similar problem in the XDA forum or elsewhere...
Regards, Christian
Hi,
you are right that update comes after inserting SIM card. How did you processed installing original Huawei Recovery? Did you made unroot and relock your bootloader?
Pa-Jo said:
Hi,
you are right that update comes after inserting SIM card. How did you processed installing original Huawei Recovery? Did you made unroot and relock your bootloader?
Click to expand...
Click to collapse
No, I extracted the original recovery from the update.app file with the Huawei update extractor (https://forum.xda-developers.com/showthread.php?t=2433454)
Do I have to relock the bootloader in order to install the update?
DocFraggle said:
No, I extracted the original recovery from the update.app file with the Huawei update extractor (https://forum.xda-developers.com/showthread.php?t=2433454)
Do I have to relock the bootloader in order to install the update?
Click to expand...
Click to collapse
You should get rid of the root, flash unSU in TWRP, uninstall also Magisk and flash Magisk Uninstaller in TWRP, relock bootloader, then flash Huawei Recovery and then your should be able to install OTA without failing.
Pa-Jo said:
You should get rid of the root, flash unSU in TWRP, install also Magisk and flash Magisk Uninstaller in TWRP, relock bootloader, then flash Huawei Recovery and then your should be able to install OTA without failing.
Click to expand...
Click to collapse
Yeah, I had a look in the recovery_log file:
Code:
...
[2017-11-28 21:47:35 704] virtual void HuaweiUIEmuiProgress::draw(),line=1168: UI percent: 16%.
[2017-11-28 21:47:38 184] virtual void HuaweiUIEmuiProgress::draw(),line=1168: UI percent: 17%.
[2017-11-28 21:47:42 892] virtual void HuaweiUIEmuiProgress::draw(),line=1168: UI percent: 18%.
[2017-11-28 21:47:46 046] virtual void HuaweiUIEmuiProgress::draw(),line=1168: UI percent: 19%.
failed to verify blocks (expected 9a2dc5ceb0f21acaef0fbc02e7dc16c947fa19c6, read 41e836f7764c23ce31a2258db97e4c358bfbbf8b)
stat "/data/update/2bdde8504898ccfcd2c59f20bb8c9c25f73bb524/9a2dc5ceb0f21acaef0fbc02e7dc16c947fa19c6" failed: No such file or directory
partition has unexpected contents
failed to read blocks for diff
...
I guess the Magisk files change the expected hash of the /data partition...
I'll try uninstalling Magisk tonight.
DocFraggle said:
Yeah, I had a look in the recovery_log file:
Code:
...
[2017-11-28 21:47:35 704] virtual void HuaweiUIEmuiProgress::draw(),line=1168: UI percent: 16%.
[2017-11-28 21:47:38 184] virtual void HuaweiUIEmuiProgress::draw(),line=1168: UI percent: 17%.
[2017-11-28 21:47:42 892] virtual void HuaweiUIEmuiProgress::draw(),line=1168: UI percent: 18%.
[2017-11-28 21:47:46 046] virtual void HuaweiUIEmuiProgress::draw(),line=1168: UI percent: 19%.
failed to verify blocks (expected 9a2dc5ceb0f21acaef0fbc02e7dc16c947fa19c6, read 41e836f7764c23ce31a2258db97e4c358bfbbf8b)
stat "/data/update/2bdde8504898ccfcd2c59f20bb8c9c25f73bb524/9a2dc5ceb0f21acaef0fbc02e7dc16c947fa19c6" failed: No such file or directory
partition has unexpected contents
failed to read blocks for diff
...
I guess the Magisk files change the expected hash of the /data partition...
I'll try uninstalling Magisk tonight.
Click to expand...
Click to collapse
You are right, Magisk touches the /data partition. Let us know how the things goes after you uninstall Magisk.
Pa-Jo said:
You are right, Magisk touches the /data partition. Let us know how the things goes after you uninstall Magisk.
Click to expand...
Click to collapse
OK, got it
1. Backup all your apps+data (Titanium)
2. Restore to factory defaults
3. Use Huawei updater to download update
4. Update the phone to the latest version
5. Unlock bootloader, it's locked again after the update; results in one more factory reset
6. Flash TWRP recovery
7. Install Magisk
8. Restore your apps
9. Done
It's a little extra work, but who cares if you get a rooted phone again
DocFraggle said:
OK, got it
1. Backup all your apps+data (Titanium)
2. Restore to factory defaults
3. Use Huawei updater to download update
4. Update the phone to the latest version
5. Unlock bootloader, it's locked again after the update; results in one more factory reset
6. Flash TWRP recovery
7. Install Magisk
8. Restore your apps
9. Done
It's a little extra work, but who cares if you get a rooted phone again
Click to expand...
Click to collapse
Nice to see that everything is working and update to B150 was successful.
Related
TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
You're the man! Props for all the hard work you've put into this.
TY!!!!
Awesome. I might have to wait a bit to install but glad to see the Pixel getting twrp.
Sent from my Pixel XL using Tapatalk
Wow, and so it begins. Thanks!
Thank you!!
Nice!!! Awesome job @Dees_Troy
Sent from my Pixel XL using Tapatalk
I just installed the IMG w/out issue.
I can't find the zip in TWRP file manager to flash though.
Everything looks encrypted.
EDIT: It went through on the 4th try of flashing the IMG, now I can see my /sdcard and install the zip.
But somehow this killed my OS.
Just flashed the flash-all.bat after removing -w so it doesn't wipe.
Now I'll try TWRP install again.
EDIT 2: Okay, after restoring to stock, the TWRP install went fine.
Maybe it didn't like my elementalx kernel or the existing root. The OP did mention something about root conflicts, I guess it may prevent TWRP installs too? But now I have OS *and* TWRP.
And I'm getting "Unspecified Error" when trying to copy my EFS backup from /sdcard/twrp/backup to my local computer. I am able to copy other non-TWRP files though.
.
.
.
Does a full backup on Pixel include System Image and Vendor Image? I don't recall seeing these on other devices.
Or do I just back up boot, system and data like usual?
***Hey ya'll, don't forget to back up EFS at least once and copy it to your computers!
Yea! Worked perfect!!!
Would the flashable SuperSU v2.78 SR3 zip work?
Looked it up and because of conflicting init binaries between TWRP and the current root method, it just wouldn't work.
While we're still on or near the first page of the thread, I'd like to clarify the whole EFS backup thing.
It's completely unnecessary. You don't need to do it. But the option is there (so no one asks where it went!)
Both the modemst1 and modemst2 partitions are merely a caching area for your modem firmware. They do not contain sensitive data like IMEI, or anything important. You can wipe them and they will be regenerated from scratch! Have no fear, your IMEI cannot be destroyed through means of bad flashes!
The issue with these partitions however is that should they ever become corrupt, the modem firmware will panic and fail to load - this is why you see your IMEI missing in such a case. The modem firmware simply refused to load due to encountering corrupt data. By clearing your modemst partitions (writing zeros to them), your modem firmware would happily load and regenerate the partitions, bringing back full call support & a visible IMEI.
Okay, I have TWRP + OS working fine after restoring to stock (getting rid of kernel + root).
Now to just wait for custom ROM's to drop. Thanks guys.
The ability to restore EFS was pretty important on some older phones.
Yep just want to let ya guys know might want return to stock before doing this. Besides that all good. Good job TWRP team! :good:
CZ Eddie said:
Okay, I have TWRP + OS working fine after restoring to stock (getting rid of kernel + root).
Now to just wait for custom ROM's to drop. Thanks guys.
The ability to restore EFS was pretty important on some older phones.
Click to expand...
Click to collapse
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
kirschdog1 said:
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
Click to expand...
Click to collapse
FYI on OP - A SuperSU update will be required to allow TWRP and SuperSU to co-exist.
kirschdog1 said:
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
Click to expand...
Click to collapse
yes
no
I stubbornly flashed v2 root and got boot hang so I put the phone up for the night.
delete
CZ Eddie said:
yes
no
I stubbornly flashed v2 root and got boot hang so I put the phone up for the night.
Click to expand...
Click to collapse
Do we still flash root the same way after we install TWRP? Or is there an su zip to flash?
Hooray! Cheers!
I've bricked my phone and am in need of help!
What I've done:
Unlocked bootloader with a code from DC-Unlocker then using minimal ADB and Fastboot to unlock
Flashed TWRP 3.1.1
Installed Magisk
Took TWRP backup - but I was unable to backup Data (I believe this was due to encryption - recovery.log shwed errors initially on Bluedorid files)
Wiped data with TWPR to try and do a factory reset
This is where my problems started and now I cant restore boot with TWPR the error is "No such file or directory"
I can ADB pull my recovery.log which says
Read info file, restore size is 12444160
Restoring 6 partitions...
Total restore size is 4512MB
I:Restore filename is: /external_sd/TWRP/BACKUPS/L5NDU17B18000539/Stock V7 2018-06-23--16-58-45/boot.emmc.win
I:Restore file system is: 'emmc'.
I:Restore file system is: 'emmc'.
Restoring Boot...
Error opening: '' (No such file or directory)
I can restore OEM recovery and do a factory reset but it hangs at 99%
power down then it goes back to factory reset and goes to 100% - message "Reset Successful!"
but... then it gets stuck in a boot loop
I've tried downloading other stock ROMS and extracting and flashing images via fastboot (Boot, cust, product, recovery, system, vendor, version)
I've tried Huawei Multi-tool but I lack the Userdata.img disk image
I've tried flashing Resurrection Remix N v5.8.5 For Honor 9 (STF) but without success, although the TWRP install says it is successful and the vendor.img flashes fine.
I've tried extracting UPDATE.app files and putting them in sd_card/dload and then 3 button resetting
I've tried the above in external_sd/dload (not sure why - desperation)
I've tried looking on as many threads as I can find on XDA but with no luck
I can always get to fastboot, flash TWRP or OEM recovery, I can also run ADB commands via Putty (in command line they display strangely)
Any suggestions would be greatly appreciated! I am at a loss an quite frustrated, and have been working on this for maybe 15 hours now.:crying:
LOL, Stop your mumbo-jumbos.
I guess you'r still with nougat partitioning because you're using a pretty much outdated twrp.
So just dload flash a nougat 'service repair firmware' from the same region you're firmware is actually, and not any random update.app you 'made' yourself.
For this you'll need a micro-sdcard (or usb-otg) exfat formated :
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Fixed!
Thank you, I think I even saw this thread but for some reason did not download the file, also the exfat formatting tip was excellent. I owe you a beer!
Can I always use this method to go back if I totally destroy things again even If I update to Oreo?
oslo83 said:
LOL, Stop your mumbo-jumbos.
I guess you'r still with nougat partitioning because you're using a pretty much outdated twrp.
So just dload flash a nougat 'service repair firmware' from the same region you're firmware is actually, and not any random update.app you 'made' yourself.
For this you'll need a micro-sdcard (or usb-otg) exfat formated :
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Click to expand...
Click to collapse
Unfortunatly, there only nougat 'service repair firmware' available publicly as far I know.
So, for now, you can only use this when on nougat.
When on oreo, you should use HuRUpdater with oreo's Twrp.
Or if you're oreo device is really messed badly, a paying app called DC-Phoenix then HuRUpdater.
Doing this quick update because today, when trying to root my phone, bricked it several times and lost all app info
If you are using android 7.11, this guide works fine: https://forum.xda-developers.com/zenfone-3-zoom/how-to/how-to-root-zenfone-3-zoom-ze553kl-t3622256
If on android 8, SuperSU will brick your phone. Use Magisk instead:
- enable usb debug mode on your phone
- unlock bootloader
- plug phone into your computer
on your pc
- Download fastboot and adb:
* Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
* macos: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
* linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
- download the latest Magisk unlock script from https://github.com/topjohnwu/Magisk/releases and copy it to a MicroSD or USB that you can attach to your phone. Look for Magisk, not Magisk Manager
- download twrp v 3.1.0-0-Z01H-20170408: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w?E81jQTCD (this is from https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w, as described in the old root guide using twrp + supersu. It is supposed to be safe)
- `adb reboot bootloader`
- `fastboot flash recovery <path to twrp image downloaded>`
- `fastboot reboot`
Right now, you should probably backup your phone.
back on your phone:
- before booting, press volume up on the bootloader, there, select Recovery. Using fastboot to reboot into recovery might cause the stock recovery image to reflash
- if prompted to enable system modifications, allow it.
- If prompted to decrypt your data in TWRP, use the PIN you setup. If it doesn't work, I can't guarantee you won't brick our phone. Feeling brave enough? In case of brick keep reading, it is easy to restore your phone to stock Android 8 using official firmware.
- press install, choose the device attached to your phone that has Magisk-xxx.zip and select it
- flash the image and it should be OK
In case of brick or unsuccessful flash from SuperSU and without backup:
- Don't panic, like I did today
- download the latest firmware from Asus: https://www.asus.com/us/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_BIOS/
- follow this guide: https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
- when the phone reboots, boot into recovery
- enable ADB sideload
- on your pc: `adb sideload <path to newest firmare>`
- now follow the root guide above before starting your phone
- ???
- profit
Note: commands using adb and fastboot assume you have put the contents from the downloaded platform tools in your PATH, else execute them from the directory in which they were extracted, for instance, on linux:
- `cd /home/$USER/Downloads`
- `unzip platform-tools-latest-linux.zip`
- `cd platform-tools`
- `./adb devices`
Bricked my phone.
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
gchamon said:
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
Click to expand...
Click to collapse
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
This is strange. Magisk is supposed to patch the boot image and install its app (by the way, if you update magisk using the app, phone enters bootloop)
Anyway, I have encountered myself many problems when installing, but nothing like this. Bootloops and corruption message on bootloader yes, but I can't seem to recall anything about partitions not being mounted. If installing stock recovery image, boot image and system doesn't do the trick, in my experience it is either bad partitioning, although unlikely, because those procedures doesn't repartition anything, or bad internal storage.
But just to be sure, you should reflash stock 7.1 image (recovery, boot and system) with fastboot, enter stock recovery and wipe cache/factory reset. If your phone is physically healthy, this should work
anonymousbsb said:
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
Click to expand...
Click to collapse
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Enrico06 said:
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Click to expand...
Click to collapse
Cool, if this fixes the issue I will update the guide with this info
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
kingairtel08 said:
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
Click to expand...
Click to collapse
Downgrade to 7.1.1 and try it again.
Already tried on 7.1.1 lot of times same error shows.
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
normal. please wait 15min max
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
I can't really help you there. This guide is supposed to work for those who are able to unlock bootloader using official asus tools. Never heard of unofficial unlock methods. It is possible that you have a hardware problem if you use those tools and they just don't work.
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
Have you used the latest official unlocking tool? I see there's a July 2019 version available.
If you are on an older version of Android (not Oreo) are you presently still getting OTA update prompts?
I tried this tool but no result.
is it possible to root ZE553KL without loosing user application's data? I have unrooted device, wanted to migrate telegram secret chats to new phone. it is doable but with rooted smartphone only. if rooting process is destructive I cannot migrate. if rooting is doable with preserving installed applications along with their data then there is a hope for successful migration.
does this method look promising or it is just fake method?
Asus Zenfone 3 Zoom ZE553KL root using Magisk [No need TWRP Recovery
How to root Asus Zenfone 3 Zoom ZE553KL with Magisk [no need TWRP recovery, easy method to rood your Android device.
www.mobilewithdrivers.com
I tried to flash TWRP using this guide: https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/
I do everything step by step, but every time after rebooting to recovery there is not TWRP but only stock recovery. I have unlocked bootloader. The device is active using the "fastboot devices" command. USB debugging mode is ON. Please help me solve this problem
install Magisk then official twrp app and flash twrp from the app to recovery
PanRyba said:
I tried to flash TWRP using this guide: https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/
I do everything step by step, but every time after rebooting to recovery there is not TWRP but only stock recovery. I have unlocked bootloader. The device is active using the "fastboot devices" command. USB debugging mode is ON. Please help me solve this problem
Click to expand...
Click to collapse
The only way it worked for me was to install official twrp app, and flash twrp-3.3.1-0-Armor_6.img from the app to recovery, then click on reboot to rrcovery also in the app.
Twrp will only be available one time after the reboot (so it is not really flashed)
(Adb flash recovery doesn't work for me)
In order to use official twrp app, i rooted with magisk
U welcome
I'm confused now. How did you root with magisk without TWRP. The Magisk installation was basically the only reason for me to flash TWRP
PanRyba said:
I'm confused now. How did you root with magisk without TWRP. The Magisk installation was basically the only reason for me to flash TWRP
Click to expand...
Click to collapse
Same as twrp
Install magisk app and do it from there:
Go to github website and download MagiskManager-v7.3.4.apk
https://github.com/topjohnwu/Magisk/releases
From the apk you will be able to flash your boot partition with magisk (it will save a boot image flashed with magisk on your phone)
The second step is simply to transfer that .img on your computer, install platform tools (in order to use adb command line)
Launch cmd.exe in platform tools folder
Connect your phone to computer via a usb cable and usb debug enabled
Type the command "adb devices" to check if your device is recognised (if a window appear on your phone to enable connection click ok)
Then type "adb reboot bootloader" (you are now in fastboot mode)
Then type "fastboot flash boot (then the name of your flashed with magisk boot image.img that you previously put in platforms tool folder in order to not search for the path)"
Then type "fastboot reboot"
Then from magisk manager app update magisk
That's it
No need for a recovery in the first place to root with magisk
finally works. thanks you dude. I really appreciate your help
PanRyba said:
finally works. thanks you dude. I really appreciate your help
Click to expand...
Click to collapse
You're welcome
Glad to help
PanRyba said:
I tried to flash TWRP using this guide: https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/
Click to expand...
Click to collapse
I also used that guide and couldn't get TWRP or Magisk to install on my new Armor 6E. I was able to use "Method 2" and SP Tool to flash TWRP 3.3.1-0, then I was able to flash Magisk using TWRP recovery.
I flashed Magisk-v20. 0(20000).zip
MD5 checksum: 56f82549e9f3c659a11f1f459e56489f
Now I seem to be stuck with the "Orange State" message at boot.
When I attempt to use TWRP to flash "no-verity-opt-encrypt-6.0.zip" I get the following :
-----
Installing zip file '[file path]'
Checking for Digest file...
Verifying zip signature...
Zip signature verified successfully.
##dm-verity and forced encryption disabler by jcadduono version 6.0##
Unpacking the installer...
Updater process ended with ERROR: 1
Error installing zip file' no-verity-opt-encrypt-6.0.zip'
Updating partition details...
... done
-----
The file has this MD5 checksum:
caea927e96c755f3568e85dbded88923
When I attempt to use TWRP to flash "orange_state_disabler_MTK Only.zip" I get the following:
-----
Installing zip file '[pathname]'
Checking for Digest file...
Verifying zip signature...
Zip signature verification failed!
Error installing zip file 'orange_state_disabler_MTK Only.zip'
Updating partition details...
... done
-----
That file has this MD5 hash:
30b01bb314d26643b6cc1dfce1d81cf5
I get nearly the same result when I attempt to install "ROMProvider.COM_orange_state_disabler 0.3.zip"
(Zip signature verification failed!)
That file also has the same MD5 hash:
30b01bb314d26643b6cc1dfce1d81cf5
TWRP asks for a password when I first boot into recovery. I also tried to contact them at the unofficialtwrp.com website (where I downloaded the zip files), but their contact page seems to loop back on itself.
Has anyone else run into this (and stuck with Orange State warning at boot)?
ndt44 said:
Now I seem to be stuck with the "Orange State" message at boot.
Click to expand...
Click to collapse
I was finally able to use TWRP 3.3.1 Install to flash file "ROMProvider.COM_orange_state_disabler_v0.3.zip" this morning and rid myself of the Orange State warning every single boot. NOTE: I had to UNCHECK zip file verification in TWRP Install in order to get it to work this time!!
This was my output:
-------------------------------
Installing zip file '[pathname]'
Checking for Digest file...
--- 'Orange State' disabler v0.3 - - -
##### Created by XopmoH97 #####
Current zip - > 'ROMProvider.COM_orange_state_disabler_v0.3.zip'.
Unzipping binaries to '/tmp'...
Success!
Set execute flag to 'tmp/sed-arm'.
Set execute flag to 'tmp/xxd-arm'.
Checking CPU architecture...
CPU architecture 'arm64-v8a' is supported!
Searching 'lk' block in GPT...
Success! 'lk' block = '/dev/block/mmcblk0p27'
Saving '/dev/block/mmcblk0p27' to '/tmp/lk.img'...
Testing NEW algorithm...
NEW algorithm is available!!!
Patching '/tmp/lk.img'...
Success!
Writing '/tmp/lk.img' to '/dev/block/mmcblk0p27'...
Success!!! Please reboot your device!
Updating partition details...
... done
-----------
Unfortunately, the no-verity.ZIP still will not flash!
ndt44 said:
I was finally able to use TWRP 3.3.1 Install to flash file "ROMProvider.COM_orange_state_disabler_v0.3.zip" this morning and rid myself of the Orange State warning every single boot. NOTE: I had to UNCHECK zip file verification in TWRP Install in order to get it to work this time!!
This was my output:
-------------------------------
Installing zip file '[pathname]'
Checking for Digest file...
--- 'Orange State' disabler v0.3 - - -
##### Created by XopmoH97 #####
Current zip - > 'ROMProvider.COM_orange_state_disabler_v0.3.zip'.
Unzipping binaries to '/tmp'...
Success!
Set execute flag to 'tmp/sed-arm'.
Set execute flag to 'tmp/xxd-arm'.
Checking CPU architecture...
CPU architecture 'arm64-v8a' is supported!
Searching 'lk' block in GPT...
Success! 'lk' block = '/dev/block/mmcblk0p27'
Saving '/dev/block/mmcblk0p27' to '/tmp/lk.img'...
Testing NEW algorithm...
NEW algorithm is available!!!
Patching '/tmp/lk.img'...
Success!
Writing '/tmp/lk.img' to '/dev/block/mmcblk0p27'...
Success!!! Please reboot your device!
Updating partition details...
... done
-----------
Unfortunately, the no-verity.ZIP still will not flash!
Click to expand...
Click to collapse
The Orange State disabler zip is news to me, and it sounds worthwhile to flash.
I successfully flashed the DM-Verity zip from an OTG USB drive after using TWRP to format the system and data partitions to EXT4. No success with ROMs yet.
Pergmen said:
The Orange State disabler zip is news to me, and it sounds worthwhile to flash.
I successfully flashed the DM-Verity zip from an OTG USB drive after using TWRP to format the system and data partitions to EXT4. No success with ROMs yet.
Click to expand...
Click to collapse
mvyrmnd said:
The 6 and 6E are very similar devices. The TWRP listed here works on the 6E. Magisk also works as described.
I cannot confirm for the 6 (but is likely), but the 6E works with all phh-based GSI ROMs.
These phones use A/B images.
Click to expand...
Click to collapse
Can't post links even when quoting so you just have to google "treble project github"
I have gotten roms to work (use A/B even if treble check says its only A for somereason).
I wasn't able to get liniageOS to work (from the pie roms, i think everyting else seems to work) and android Q ones even thou it should be able to from what i have gathered.
IMPORTANT! It seems like every rom is missing basic features like gestures, i dont know if it has to do with the kernel maybe? Im nubie.
VERY IMPOTANT!! Lost my IMEI number from messing around with the phone so be careful! Im not responsible.
Pergmen said:
The Orange State disabler zip is news to me, and it sounds worthwhile to flash.
I successfully flashed the DM-Verity zip from an OTG USB drive after using TWRP to format the system and data partitions to EXT4. No success with ROMs yet.
Click to expand...
Click to collapse
Would it be possible to get an MD5 checksum and filename which worked for you so that I might compare them? Did you get that file from the unofficial twrp page linked above then? Also were the "system and data EXT4 partitions" on the phone Internal Storage or the USB OTG?
ndt44 said:
I was finally able to use TWRP 3.3.1 Install to flash file "ROMProvider.COM_orange_state_disabler_v0.3.zip" this morning and rid myself of the Orange State warning every single boot. NOTE: I had to UNCHECK zip file verification in TWRP Install in order to get it to work this time!!
Click to expand...
Click to collapse
I obtained this file here:
https://www.google.com/amp/s/rompro...ange-state-fixer-fix-orange-state/amp/?espv=1
I just ordered this armor 6e phone. I will be able to answer my own question next week, I suppose. Bit, in the armor 6 thread it is mentioned few times that there twrp works on 6e, now I found this thread, which says twrp will not stay flashed to phone.
Which one is correct?
If the armor 6 twrp does work, does it work to flash gapps? Because the y is not pie, and as such is not system-as-root, which from other devices, I know that makes recovery see the phone file structure different
Ie : /system_root/system not just /system
This difference needs different build of twrp.
I will give it a try when I receive it I suppose.
mrmazak said:
I just ordered this armor 6e phone. I will be able to answer my own question next week, I suppose. Bit, in the armor 6 thread it is mentioned few times that there twrp works on 6e, now I found this thread, which says twrp will not stay flashed to phone.
Which one is correct?
If the armor 6 twrp does work, does it work to flash gapps? Because the y is not pie, and as such is not system-as-root, which from other devices, I know that makes recovery see the phone file structure different
Ie : /system_root/system not just /system
This difference needs different build of twrp.
I will give it a try when I receive it I suppose.
Click to expand...
Click to collapse
I have found a TWRP that stays on. And i have seen some that dont stay. Im able to flash gapps with it to my 6e.
poohju said:
I have found a TWRP that stays on. And i have seen some that dont stay. Im able to flash gapps with it to my 6e.
Click to expand...
Click to collapse
Thanks. Do you have links?
mrmazak said:
Thanks. Do you have links?
Click to expand...
Click to collapse
First maybe try out the unofficial TWRP (https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/) maybe it works. I think i didnt get it to stick but its worth a shot ig and you can also try with the TWRP app (havent tried the app way). Sadly i dont remember where i got the file that sticks for me. If unofficial dosent work i can upload it to somewhere. I used ADB tools to download TWRPs. If you use SP tools to flash it while like doing a fresh install. It will go to RED state. You can use SP tools if you first install stock then unlock bootloader and flashing then only installing the recovery. You can install gapps mostly but u cant use dm veryeti disabler it messes with the IMEI at least for me. Im not that savy to know how to fix it. Its my first phone ever messing with. MAGISK works.
poohju said:
First maybe try out the unofficial TWRP (https://unofficialtwrp.com/twrp-3-3-1-root-ulefone-armor-6e/) maybe it works. I think i didnt get it to stick but its worth a shot ig and you can also try with the TWRP app (havent tried the app way). Sadly i dont remember where i got the file that sticks for me. If unofficial dosent work i can upload it to somewhere. I used ADB tools to download TWRPs. If you use SP tools to flash it while like doing a fresh install. It will go to RED state. You can use SP tools if you first install stock then unlock bootloader and flashing then only installing the recovery. You can install gapps mostly but u cant use dm veryeti disabler it messes with the IMEI at least for me. Im not that savy to know how to fix it. Its my first phone ever messing with. MAGISK works.
Click to expand...
Click to collapse
Thanks. I looked at unofficial, and unpacked there image. It is set to terrible enabled = no, and is not setup for system-as-root.
Also the prop file says it is for armor 6 not 6e, so I will just build fresh one and use that.
mrmazak said:
Thanks. I looked at unofficial, and unpacked there image. It is set to terrible enabled = no, and is not setup for system-as-root.
Also the prop file says it is for armor 6 not 6e, so I will just build fresh one and use that.
Click to expand...
Click to collapse
Good luck to you maybe you can share it when your done
poohju said:
Good luck to you maybe you can share it when your done
Click to expand...
Click to collapse
My phone is still not delivered. But I did compile twrp from source, using the September update files from ulefone site.
I started with the device tree from the armor 6, and made few changes that I have found to work for treble devices and system as root on other recent mtk phones I have.
But I can't confirm the build works. If you want to beta test it, let me know.
Hi,
I tried to update my P6 using the magisk OTA update method:
-Unistall / Restore image
-Install OTA, no reboot
-Install magisk on inactive slot
-Reboot
My phone was on the SQ3A.220705.001.B2 update, few months old.
When I rebooted, I was prompted with the "device corrupted" message. I pressed the power key to continue, and was stuck at the Google logo boot loop.
I forced turned off the phone (hold power + vol up a few sec), and the phone rebooted, no corruption message to my surprise, and booted correctly. However, my system did not update (still on SQ3A.220705.001.B2).
I'm a rookie on device rooting, but my understanding is that my inactive slot (partition b) as the update installed but is corrupted and goes in boot loop, while partition a is not updated but not corrupted either.
The thing is, I only did "install on inactive slot", so magisk was uninstalled on partition a, and rebooting made me lost root on that partition.
Is there any way to de-corrupt partition b without losing data ? Because without root on partition a, it seems like I'll need to reinstall it, meaning a factory reset...
I've searched a bit on here, saw that it was probably an avb bug (but rookie me doesn't know what avb is), and that OTA update using magisk inactive partition was not recommended for P6 and P7.
Any help would be greatly appreciated, thanks !
SleinBuyt said:
Is there any way to de-corrupt partition b without losing data ? Because without root on partition a, it seems like I'll need to reinstall it, meaning a factory reset...
I've searched a bit on here, saw that it was probably an avb bug (but rookie me doesn't know what avb is), and that OTA update using magisk inactive partition was not recommended for P6 and P7.
Any help would be greatly appreciated, thanks !
Click to expand...
Click to collapse
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Strephon Alkhalikoi said:
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Click to expand...
Click to collapse
Strephon Alkhalikoi said:
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Click to expand...
Click to collapse
Ok I'll find out how to flash ROM using adb beacause I don't remember, and I'll do what you said.
After that, I should be able to force boot to partition b (the updated one) using adb, right? And will I be able to root without losing data ?
SleinBuyt said:
Ok I'll find out how to flash ROM using adb beacause I don't remember, and I'll do what you said.
After that, I should be able to force boot to partition b (the updated one) using adb, right? And will I be able to root without losing data ?
Click to expand...
Click to collapse
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
SleinBuyt said:
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
Click to expand...
Click to collapse
I think that the easiest way is with Pixel Flasher, it makes everything automatically with data preserve.
SleinBuyt said:
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
Click to expand...
Click to collapse
m_pastuszek said:
I think that the easiest way is with Pixel Flasher, it makes everything automatically with data preserve.
Click to expand...
Click to collapse
@SleinBuyt : Yes
@m_pastuszek : While he could do that he should learn how to do it without a tool first. That way he can understand what is going on when the tool is working.
Strephon Alkhalikoi said:
@SleinBuyt : Yes
@m_pastuszek : While he could do that he should learn how to do it without a tool first. That way he can understand what is going on when the tool is working.
Click to expand...
Click to collapse
I agree on this side, but actually editing script that makes something similar comes down to the same thing
That was the same case for me.
After latest OTA update, no matter how many time I tried to flash full factory image via fastboot, stil showing device corrupted.
A couple of things everyone having this issue should be aware of.
Currently, "Flash to Inactive Slot" breaks verification/dm-verity on the Pixel 6/7, and I believe that's responsible for the "Device corrupted" error. The Magisk devs are aware but don't have a fix yet. I haven't been able to test because there have been no OTAs since I disabled those myself (which PixelFlasher can do for you), but I believe disabling them should prevent that problem during OTAs, but be advised I think doing so requires wiping /data when you do it.
Also, if you're still getting "device corrupted" even after reflashing stock, first watch for any errors during flashing in PixelFlasher (I may have a fix for anyone that has USB issues on Windows devices, but it involves the registry so it makes some people nervous), but if it isn't working then try Google's Android Flash Tool by finding your device and desired firmware here and clicking Flash. You'll need to be using Chrome. That's never failed for me. Once you have it up and running again *then* use PixelFlasher to patch and flash the boot image.
ALSO, for anyone on T1B1/QPR2: Magisk currently is not working at all with these versions. It'll boot, but you'll have no root. No one knows why yet as far as I'm aware. You'll have to stick to earlier/non beta builds until there's an answer for that if you want root.
Jaitsu said:
ALSO, for anyone on T1B1/QPR2: Magisk currently is not working at all with these versions. It'll boot, but you'll have no root. No one knows why yet as far as I'm aware. You'll have to stick to earlier/non beta builds until there's an answer for that if you want root.
Click to expand...
Click to collapse
To root the Pixel 6 on QPR2 Beta 1 you can patch the Pixel 7 boot image and then flash that on the Pixel 6.
Compression method of ramdisk in Pixel 6 boot image is incorrect · Issue #6441 · topjohnwu/Magisk
After switching to the beta version can't patch boot img and succesfully get root, with the stable version works. Device: Pixel 6a Android version: Android 13 QPR2 Beta 1 (T2B1.221118.006) Magisk v...
github.com
UPDATE : I did it, I used ADB for the sake of trying it, next time I'll look into PixelFlasher I guess. The message is gone.
Exact step followed :
-I first trained to use adb by flashing magisk, but ended up patching the wrong boot.img (the one from the A13 update, while being on A12), which sent me in a bootloop.
-I then flashed the A13 ROM, with the modified flash-all file
-Rebooted bootloader, flashed magisk
-Rebooted device.
Took me 2h lol, each step was learning something.
Thanks everyone!
SleinBuyt said:
UPDATE : I did it, I used ADB for the sake of trying it, next time I'll look into PixelFlasher I guess. The message is gone.
Exact step followed :
-I first trained to use adb by flashing magisk, but ended up patching the wrong boot.img (the one from the A13 update, while being on A12), which sent me in a bootloop.
-I then flashed the A13 ROM, with the modified flash-all file
-Rebooted bootloader, flashed magisk
-Rebooted device.
Took me 2h lol, each step was learning something.
Thanks everyone!
Click to expand...
Click to collapse
Just make sure you have the A13 bootloader on both slots if you haven't already, since it sounds like you just updated from A12 to A13?
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Lughnasadh said:
Just make sure you have the A13 bootloader on both slots if you haven't already, since it sounds like you just updated from A12 to A13?
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Click to expand...
Click to collapse
I mean, the objective was to update my device and keep root, wich is now done. Why do I need the A13 bootloader on both slots, and if it's important how should I do it ?
SleinBuyt said:
I mean, the objective was to update my device and keep root, wich is now done. Why do I need the A13 bootloader on both slots, and if it's important how should I do it ?
Click to expand...
Click to collapse
It's important if you don't want to brick your device. Did you read the link I gave you?
Lughnasadh said:
It's important if you don't want to brick your device. Did you read the link I gave you?
Click to expand...
Click to collapse
Sorry I didn't see, I've read now.
So If ok reboot to fastboot, plug in, and with adb :
fastboot flash bootloader --slot=all flash-all.img
I should be good ?
SleinBuyt said:
Sorry I didn't see, I've read now.
So If ok reboot to fastboot, plug in, and with adb :
fastboot flash bootloader --slot=all flash-all.img
I should be good ?
Click to expand...
Click to collapse
fastboot flash bootloader --slot=all <A13 bootloader image>
My situation is a bit bizarre. I'm on beta and recently got an update notification that was 190mb. I went to magisk to restore images and magisk says stock backup does not exist. From there and went ahead and use my PC to flash my stock boot image and rebooted. Once an Android it's still says the same thing but when I go back to the update it says installation problem Even though I am on stock. That's where I'm at right now. Haven't messed with it since just rolled with no root and stock boot image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lughnasadh said:
fastboot flash bootloader --slot=all <A13 bootloader image>
Click to expand...
Click to collapse
And it's done ! Thanks for potentially saving my phone later !