Related
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Please someone help me i spend 2 days and still nothing! How can i open this phone? Stock rom, with/without root, custom rom whatever, just tell me how can i open this phone
up
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
shae23 said:
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
Click to expand...
Click to collapse
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
cannurkars said:
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
Click to expand...
Click to collapse
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
I will try it. Thank you very much.
cannurkars said:
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Click to expand...
Click to collapse
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
ConnerZhao929 said:
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
Click to expand...
Click to collapse
No it wasn't work for me. But thank for your attention. I'm glad to find a good person to help me and my problem solved about 1-2 hour ago.
Special Request
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
AniMaL92 said:
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
Click to expand...
Click to collapse
What's your firmware now?
You can get that info in Fastboot using
Code:
fastboot oem get-product-model
fastboot oem get-build-number
Since your recovery and fastboot still functions you probably will only need to use HWOTA to get back to stock.
It can be found here: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
But post your cust/build before proceeding.
Also cust.img is found in UPDATE.APP in the hw data zip.
Problem Solved - Somewhat
Hey ante. Thanks for the promt reply. I got it solved by using CHIMERA tool.
Would like to suggest others also stuck with same issue to use CHIMERA.
Note - It is a paid tool and 100% legit and it can help with all problems related to FRP, Bootloader Lock / Unlock & also flashes back to factory firmware.
However what I am facing now I have flashed another version of firmware which isn't my region and some features of my phone like fingerprint scanner and other things are not working but phone is back to live. So Im glad and looking forward to searching for clean Oreo Firmware for my region to flash using CHIMERA Again.
Also, the sick and stupid part of it. I went to the service center and a person non-technical told me straight that you lost your device and it's of no use now. We cannot fix such issues 99% but I'll still ask my team and let you know after 3 days.
Thank God I didn give them and wasted my time and money.
As soon as I returned, I followed up to things and got it done myself. :good:
Anybody can possibly suggest a official firmware Oreo EMUI for Middle East Region!? If not which one can be flashed instead and where to download from?
For those who want to try LineageOS 17.1/18.1-UNOFFICIAL-GSI . IMO stable enough to be used as your daily driver.
LOSQ/LiR is not developed nor maintained by me!
Credits: @eremitein
Requirements: basically full stock EMUI 9.1, with stock recovery_ramdisk.
Note: I prefer to install in fastboot mode, it's quick, easy and most importantly, safe.
IMPORTANT! Before booting up the ROM, you will need to perform a factory reset in stock recovery!
Install arm64-b.. only!
1. LOSQ - LineageOS 17.1-[10]-unofficial-GSI
with the GAPPS
GAPPS
without GAPPS
Vanilla
-----------------------
LiR- LineageOS 18.1-unofficial-[11]-GSI
Download
2. Extract the ROM .img file from the compressed file.
3. Flash extracted losq/lir... .img from fastboot , use command
fastboot flash system (file_name).img
4. Run command fastboot reboot, unplug your phone, when appears on screen yellow warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe data/factory reset'.Reboot .
NFC patch:
https://forum.xda-developers.com/t/losq-lineageos-17-1-unofficial-gsi.4219291/post-84394147
Magisk root (23.0):
(Note: If you don't plan to use TWRP, simply install patched Recovery_ramdisk in fastboot mode. Run command
fastboot flash recovery_ramdisk magisk_patched-23.img ),
- download and install Magisk manager-23.apk:
https://mega.nz/file/go0m2RiR#M5UTv6FPjWPtDaGPr-u2tpJMCwdf8uwnniZg69LiGfw
- Install TWRP-9.1
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
over eRecovery (it's necessary on EMUI 9.1):
- copy TWRP file to the SD card, and also copy to the SD card patched Recovery_ramdisk:
https://mega.nz/file/lp1kHLxJ#htCMaPjSsg_dy0w_jNOft-t_DZRAPwhOvwy_Wr2cjX8
- flash TWRP - run command
fastboot flash recovery_ramdisk (TWRP's_name).img
- boot into TWRP, select storage - SD Card, select "Install image", find TWRP-9.1.img file and mark eRecovery, swipe. Go back, find magisk_patched-23.img file, mark Recovery, swipe. Go back to the TWRP's main menu, select Reboot > Recovery. Done.
Note: you then need to boot your phone every time via Recovery. It'll boot into android as normal but with root.
( Note: for those who want keep the erecovery as a fail-safe:
https://forum.xda-developers.com/t/...-erecovery-with-twrp-installed-on-it.4357127/ )
To remove Magisk reinstall stock recovery_ramdisk via TWRP or fastboot , download Here
How to boot into TWRP:
- Turn off your phone, connect to the PC (or charger), then press and hold Power + Volume Up, device will reboot into eRecovery (= TWRP).
How to boot into patched Recovery :
- Restart your phone, when appears the yellow warning on the screen, press and hold Volume Up for ~ 2 sec,
release the button and immediately press and hold again for ~ 2 sec. Repeat it 6-7 times, the device will reboot into Stock Recovery (you can perform Wipe cache or Factory reset).
Tips:
https://forum.xda-developers.com/t/treble-gsi-favorite-gallery-camera-and-file-manager.4246019/
I have tried this rom - but without the magisk as I don't really care for root.. However.. This rom still has one big missing feature.. Fingerprint unlock. I can go to register fingerprint. Add the finger multible times to complete the circle.. however.. every time it misses just the last part - it will fail. If anyone has a fix for this I would be happy to use this as my daily driver as it works just fine.
whitetigerdk said:
This rom still has one big missing feature.. Fingerprint unlock
Click to expand...
Click to collapse
I'm afraid you're wrong... It works perfectly for me.
Can confirm that so far everything works flawless. Fingerprint sensor is working on the phone too.
Thank you Alf.
Just two additional questions:
How will updates be perform in future?
How to switch from LOS 16 to this rom - the other P20 lite we have is still on v.16?
Cheers
Horqai
horqai said:
How will updates be perform in future?
Click to expand...
Click to collapse
Hi, I don't know bro, I'm not a developer . But you can check the update here:
https://sourceforge.net/projects/treblerom/files/LOSQ/
horqai said:
How to switch from LOS 16 to this rom
Click to expand...
Click to collapse
Install Service ROM using dload method (9.1.0.132 recomm.) , then you can safely flash 17.1 GSI. Dload method will erase all your data and will lock the BL again!
-Alf- said:
Hi, I don't know bro, I'm not a developer . But you can check the update here:
https://sourceforge.net/projects/treblerom/files/LOSQ/
Install Service ROM using dload method (9.1.0.132 recomm.) , then you can safely flash 17.1 GSI. Dload method will erase all your data and will lock the BL again!
Click to expand...
Click to collapse
Ugh, is there a way to install emui 9 without it locking my bootloader? I unlocked my bootloader via the @huaweihax method.
[/QUOTE]
XRealX said:
Ugh, is there a way to install emui 9 without it locking my bootloader?
Click to expand...
Click to collapse
OTA update, via HiSuite, you can try also through eRecovery ...
make sure to have the stock recovery flash.
XRealX said:
I unlock my bootloader via the @huaweihax method.
Click to expand...
Click to collapse
Idk how huaweihax method works, but the BL unlock
code is permanent, it wont expire, you use the same bootloader code to unlock if your device is relocked.
Btw, with EMUI 8 installed with May 2018 security patch you should be able to use DC-Unlocker or hcu-client to get BL unlock code for 4euros.
Or, you can also unlock BL for free using
PotatoNV method
OTA update, via HiSuite, you can try also through eRecovery ...
make sure to have the stock recovery flash.
Idk how huaweihax method works, but the BL unlock
code is permanent, it wont expire, you use the same bootloader code to unlock if your device is relocked.
Btw, with EMUI 8 installed with May 2018 security patch you should be able to use DC-Unlocker or hcu-client to get BL unlock code for 4euros.
Or, you can also unlock BL for free using
PotatoNV method
Click to expand...
Click to collapse
There's no way I'm paying for unlocking!
The huaweihax method works this way: you give some information about your device and you flash a slock file to the ramdisk. It unlocks your phone.
To prevent EMUI 9 from re-locking your device, you can flash a zip file to have a custom bootloader unlock code.
Btw, I have hyperlinked the thread that describes this in the "thingy" word.
I guess that custom code should work even if my device is re-locked.
I do not start the phone only in loop TWRP mode, what solution do I have to revive the phone
I do not start the phone only in loop TWRP mode, what solution do I have to revive the phone
How can I repair the factory erecovery I am using the phenix program but it gives me recovery error
itrisev said:
How can I repair the factory erecovery I am using the phenix program but it gives me recovery error
Click to expand...
Click to collapse
Sorry, this is not the DC-Phoenix support chat, let's please remember to keep conversations and comments in this thread about LOSQ - LineageOS 17.1, thanks...
Thanks @-Alf-
I followed all your advice in the LOS 16 thread to get 16 installed, but couldn't get gapps to work. So I thought lemme give LOS 17 a shot since it includes gapps, and it works great! However I get the same issue with fingerprint as @whitetigerdk. During fingerprint enrolment it works up until the last time you have to finger it, after which I get popup "Enrolment was not completed: Fingerprint enrolment didn't work. Try again or use a different finger". I can provide a screenshot but it's literally just that text.
Apart from that everything seems to work fine. Haven't installed magisk yet, will do that next.
An3skmbi said:
During fingerprint enrolment it works up until the last time you have to finger it, after which I get popup "Enrolment was not completed: Fingerprint enrolment didn't work.
Click to expand...
Click to collapse
-Alf- said:
Tested on 9.1.0.132.
Click to expand...
Click to collapse
-Alf- said:
Clean OS
Click to expand...
Click to collapse
-Alf- said:
Install Service ROM using dload method (9.1.0.132 recomm.)
Click to expand...
Click to collapse
Most of custom ROMs require lower build number, on latest build number may or may not work correctly.
If you have followed this guide to the letter and it didn't work, i'm afraid I cant help you .
I've not had any major issue with this LineageOS.
P.S.:
If all this has worked on my device, it does not mean that it goes with everyone else, and vice versa (we are talking about Huawei devices ).
@-Alf- Thanks, that might be it. I'm on firmware 9.1.0.200(C185E4R1P8T8) as that was the recommended one for LOS 16. Let me give it a shot with 132, will update with results.
Edit: With "Clean OS" I assume you mean a clean install of the stock ROM? My approach is to install 132 via dload, unlock bootloader, then follow your installation steps.
An3skmbi said:
With "Clean OS" I assume you mean a clean install of the stock ROM? My approach is to install 132 via dload, unlock bootloader, then follow your installation steps.
Click to expand...
Click to collapse
Yes, but I'm afraid there's no .132 build number for region C185 on androidhost.ru
IMO you can get it via paid service only, for 17euros , hm...look here
.132
The difference between .132 and .200 is google patch - may 2019 vs. july 2019.
-Alf- said:
Yes, but I'm afraid there's no .132 build number for region C185 on androidhost.ru
Click to expand...
Click to collapse
What about this one? http://huawei-firmware.com/rom/huawei-p20-lite/ane-lx1/42056
It doesn't have a dload folder, it's just the update.zip basically, so I'm not sure how to flash it only unlocked my phone yesterday, not used to huawei roms yet.
Edit: they explain how here, you create the dload folder manually.
An3skmbi said:
they explain how here, you create the dload folder manually.
Click to expand...
Click to collapse
This guide is valid for Android 6 . Huawei-firmware is a really reliable website .
-Alf- said:
This guide is valid for Android 6 . Huawei-firmware is a really reliable website .
Click to expand...
Click to collapse
What do you mean really reliable when the guide is for Android 6? Is there a way to flash the 132 ROM from huawei-firmware?
Also, magisk installation worked perfectly by following your instructions. I can pass safety net with the universal safetynet fix module and got google play certification with the props module.
Is there a way to now boot into TWRP (erecovery)? Currently when booting it doesn't show the option to hold volume up to enter erecovery, it immediately says your phone is booting now. The only way to get into TWRP is to fastboot flash recovery twrp, do stuff there, then flash magisk_patched-ane-v21 over recovery and reboot.
Edit: I captured a logcat while getting the fingerprint enrollment error, there are some exceptions about the enrollment, not sure if that could mean something to the devs to help fix it?
An3skmbi said:
Is there a way to flash the 132 ROM from huawei-firmware?
Click to expand...
Click to collapse
Nope.
An3skmbi said:
Is there a way to now boot into TWRP (erecovery)?
Click to expand...
Click to collapse
Oops I thought I mentioned it in my post, mea culpa.
You have two options:
1. Turn off phone, connect to PC (or charger), then pres and hold Power + Volume Up, device will reboot into eRecovery (= TWRP).
2. Restart phone, when appears the yellow warning on screen, press Volume up, hold for ~ 2 sec,
release the button and immediately press and hold again for 2 sec, repeat it 6-7 times, the device will reboot into Stock Recovery , then you can do normal restart - Reboot system now.
I tried to upgrade my phone to Realme UI 2 with dirty flash but at first my phone get into a bootloop, I tried to reflash Vbmeta but it made it worse.
I tried this guide about unbrick : https://forum.xda-developers.com/t/...-to-stock-unbrick-and-fastboot-flash.3995285/ but not worked it just returned me to bootloop again.
I locked my bootloader accidently
My phone now only show this message and stuck till I press power button to turn off.
Is there is any way to flash stock ROM again with any tool ?
( MSM tool needs a username and password to work )
and I cannot find any QFIL files on Internet
IS there any way to re unlock my bootloader ?
shrefeltony said:
IS there any way to re unlock my bootloader ?
Click to expand...
Click to collapse
Did you managed to fix it?
shrefeltony said:
I tried to upgrade my phone to Realme UI 2 with dirty flash but at first my phone get into a bootloop, I tried to reflash Vbmeta but it made it worse.
I tried this guide about unbrick : https://forum.xda-developers.com/t/...-to-stock-unbrick-and-fastboot-flash.3995285/ but not worked it just returned me to bootloop again.
I locked my bootloader accidently
My phone now only show this message and stuck till I press power button to turn off.
Is there is any way to flash stock ROM again with any tool ?
( MSM tool needs a username and password to work )
and I cannot find any QFIL files on Internet
Click to expand...
Click to collapse
ONLY ONEWAY TO FIX THIS IS FLASHING THE PHONE WITH EASY JTAG PINOUT METHOD
PrateekPanwar64X said:
Did you managed to fix it?
Click to expand...
Click to collapse
I did managed to fix my device. Pressed power button and both volume keys while connected to PC (when bootloader was locked) and saw Q_BULK in device manager > COM ports.
After then it was flashed with original ROM using MSM tool and done.
PrateekPanwar64X said:
I did managed to fix my device. Pressed power button and both volume keys while connected to PC (when bootloader was locked) and saw Q_BULK in device manager > COM ports.
After then it was flashed with original ROM using MSM tool and done.
Click to expand...
Click to collapse
Hi @PrateekPanwar64X can you provide me the MSM tool that u used sir. I appreciate your help sir : )
iPonze said:
Hi @PrateekPanwar64X can you provide me the MSM tool that u used sir. I appreciate your help sir : )
Click to expand...
Click to collapse
Password of zip file should be 123
Although I don't have login credentials for msm tool. Paid to a telegram group to fix it.
Problem was I locked my bootloader myself with custom ROM [Following that warning while starting phone] and thought I'd bypass warning.
PrateekPanwar64X said:
Password of zip file should be 123
Although I don't have login credentials for msm tool. Paid to a telegram group to fix it.
Problem was I locked my bootloader myself with custom ROM [Following that warning while starting phone] and thought I'd bypass warning.
Click to expand...
Click to collapse
oh hi! thanks for providing a zip file. btw, how much do you pay?
can u send me the source of the RUI 2.0 firmware you got and ill try to fix it
umm download platform-tools
- Clean wipe - Flash C.14 or latest firmware (No need if already there) - Go to custom recovery terminal and write setprop ro.separate.soft 19691 - Flash Realme UI 2.0 ozip - Reboot to bootloader - Download Realme UI 2.0 vbmeta and flash it using fastboot with fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img - Reboot to system
PrateekPanwar64X said:
Password of zip file should be 123
Although I don't have login credentials for msm tool. Paid to a telegram group to fix it.
Problem was I locked my bootloader myself with custom ROM [Following that warning while starting phone] and thought I'd bypass warning.
Click to expand...
Click to collapse
Just a quick question, did you uninstall/delete the file later? And heads up for anyone using this zip. It seems to be a keylogger. In the zip under firmware, you can see all keypresses along with window it was pressed in, in a file called keylog.txt.
maxzeroedge said:
Just a quick question, did you uninstall/delete the file later? And heads up for anyone using this zip. It seems to be a keylogger. In the zip under firmware, you can see all keypresses along with window it was pressed in, in a file called keylog.txt.
Click to expand...
Click to collapse
Oh, Thankfully I didn’t need it later as I learnt my lesson and never locked bootloader. If I want to reupload zip, How can I remove it?
First let me say that I'm sorry about how this is formatted but I'm very frustrated with Oneplus right now. My troubles began when KB2005_11.C.16 downloaded. I could not take the OTA to save my life and it seems that the download disappeared before I had any opportunity to pull it off the phone. The only thing I could think of to do at this point was search the internet or unroot and try it. My searches turned up nothing useful and mostly forum posts from 2020 and 2021 but were unrelated (obviously). Unroot time it is. The phone updated with no problem but root was gone. Tried to boot a recovery through fastboot with no luck. The command rebooted the phone but hung on "Fastboot Mode". Tried other .img files just for grins and "fastboot boot" just doesn't work for me anymore. I updated the SDK Platform Tools, Xiaomi ADB bootloader interface drivers to no avail. ADB, Fastboot, and FastbootD all seem to function. Just not as I need them to. This is what I've done to rule out operator error.
Phone is Oneplus 8T (KB2005)
Restored phone from MSM to version 11.0.7.9.KB05AA (Obtained personally from Oneplus support)
Setup Wifi and only enough to check for OS updates.
Unlocked bootloader. Accidentally. All I really wanted to do was enable USB debugging. Nevertheless, it was done.
Checked for updates. Update to 11.0.11.11.KB05AA shows up.
I click Download and install
Installation paused. Installation will continue when device isn't being used. To install now, tap Resume
Tapped Resume.
Installing Security update...
Restart now button appears
I click Restart now
System update available 11.0.13.13.KB05AA. Tapped on notification.
I click Download and install
Installation paused. Installation will continue when device isn't being used. To install now, tap Resume
Tapped Resume
Installing Security update...
Restart now button appears
I click Restart now
System update available
New version:KB2005_11.C.16_1160_202204222257
I click Download and install
Installation paused. Installation will continue when device isn't being used. To install now, tap Resume
Tapped Resume
Installing System update...
Restart now button appears
I click Restart now
At this point OxygenOS is on Android 12
System update available
New version: KB2005_11.C.20_1200_202205262304
I click Download and install
Installation paused. Installation will continue when device isn't being used. To install now, tap Resume
Tapped Resume
Installing System update...
Restart now button appears
I click Restart now
Finally Phone is up to date
Unlocked bootoader and Developer options survived all updates
ADB reboot bootloader rebooted phone to bootloader (as expected)
fastboot reboot fastboot reboot phone to FastbootD mode (as expected)
fastboot boot anyimage.img just freezes the device with a black screen. Booting into a custom recovery this is the only way I know to pull boot.img from the device.
Untill then or until a new way becomes known to me, I'm unable to root my phone.
You should have rooted when you got to C.16. Because that's a full installation zip, you can take the payload.bin from it and use payload dumper to extract the boot image and patch the file with Magisk.
Then you could have followed the process to keep root with an incremental update.
Or, you could have rooted when you were on OOS 11 using TWRP, then kept root at each update.
These are explained in https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/
Fair enough. It does sound easy when you put it that way but here is what part of my complaint is about ...
i just reflashed with msm, unlocked bootloader, and rooted with magisk. Tested root with ADB shell, su
Checked updates again and updating failed, clicked "try again" and it failed again. This time after I clicked try again it shows that it is now trying to install C.16 so away we go ...
Oh wait. Fastboot boot doesn't boot any of my recoveries or boot.img files. I need a working custom recovery to extract a useable boot.img from my phone. Where can I find a recovery that works with C.16+?
Before you yell at me, I noticed that I left off the step of installing magisk to the other partition after the OTA. In fact, I didn't even try that yet but I have been here before and it didn't work. This time, however, it did work and I now have a rooted C.16 ready to update to C.20. I should say thank you but that doesn't sound like enough. Thank you, BillGoss. Sometimes just asking for help is enough.
My initial complaint was a bit clouded. I am reminded now trying to update to C.20, the truth of what happened. The C.20 incremental dropped and I tried to take it but it just kept resulting in "Couldn't update. Installation problem". It was because of this that I decided to unroot and try it. It did update but now I couldn't fastboot boot anyimg.img. I had no recovery.img or boot.img to further my cause. Then I went ballistic. I couldn't find an .Ota folder anywhere on my device. That just made matters worse.
I did discovery at this point that there is no longer a local update option on the update page. but there is an .apk developed by Oneplus themselves that installs a local update app.
So now I'm on KB2005_11_C.11. Check for updates shows 11.C.20 incremental. This one contains the may security update. I'm currently still on February.
Anyway, when I try to update it just says "Couldn't update. Installation problem.". Does anyone know how I can get this update please?
Throg said:
So now I'm on KB2005_11_C.11. Check for updates shows 11.C.20 incremental. This one contains the may security update. I'm currently still on February.
Anyway, when I try to update it just says "Couldn't update. Installation problem.". Does anyone know how I can get this update please?
Click to expand...
Click to collapse
It's clearly stated in BillGoss guide, how to install OTA and keep root.
You can pull your image through msm tool readback mode load msm tool press f8 it brings up a sub menu where you pick what you want to pull them you input oneplus all lowercase as the password on main screen press readback button then put phone into edl mode it will pull the img files out into your c:\ drive
@scottlam1 I was going to try this because this would be such a help getting the boot image when there have only been incremental updates, but MSM (OOS 11.0.7.9 for KB05AA from https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/) won't accept OnePlus as the password.
Any suggestions?
BillGoss said:
@scottlam1 I was going to try this because this would be such a help getting the boot image when there have only been incremental updates, but MSM (OOS 11.0.7.9 for KB05AA from https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/) won't accept OnePlus as the password.
Any suggestions?
Click to expand...
Click to collapse
I can zip my copy and pm you a drive link later
BillGoss said:
@scottlam1 I was going to try this because this would be such a help getting the boot image when there have only been incremental updates, but MSM (OOS 11.0.7.9 for KB05AA from https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/) won't accept OnePlus as the password.
Any suggestions?
Click to expand...
Click to collapse
I don't know if it matters for your build but for me I use admin privileges when you first load msm you use other no username password in readback OnePlus is lowercase one word
scottlam1 said:
I don't know if it matters for your build but for me I use admin privileges when you first load msm you use other no username password in readback OnePlus is lowercase one word
Click to expand...
Click to collapse
That did it! I don't run it as admin, but entering "oneplus" as the password worked.
Now to play with it.
BillGoss said:
That did it! I don't run it as admin, but entering "oneplus" as the password worked.
Now to play with it.
Click to expand...
Click to collapse
Ok you don't need the drive link then
BillGoss said:
That did it! I don't run it as admin, but entering "oneplus" as the password worked.
Now to play with it.
Click to expand...
Click to collapse
And make sure you hit the readback button not start first time I did it I hit start not thinking and ended up factory resetting phone
scottlam1 said:
And make sure you hit the readback button not start first time I did it I hit start not thinking and ended up factory resetting phone
Click to expand...
Click to collapse
No, I didn't make that mistake.
@scottlam1
Apart from struggling to get my PC to connect properly in EDL mode, once it did connect the readback process gave me the boot image. Woo hoo!
I made the mistake of asking for both boot_a and boot_b. But readback only produces files with <partition name>.img and, therefore, I was left with only one boot.img file (the second one).
But this means we can now get a stock boot image without needing a full OTA zip.
Thanks so much for sharing this method to pull partitions from the phone without needing root.
Throg said:
So now I'm on KB2005_11_C.11. Check for updates shows 11.C.20 incremental. This one contains the may security update. I'm currently still on February.
Anyway, when I try to update it just says "Couldn't update. Installation problem.". Does anyone know how I can get this update please?
Click to expand...
Click to collapse
Use the incremental update from oxygen updater apk and get OPLocalUpdate_For_Android12.apk it is a standalone app for local installs that they took out of the normal update in oos12 in magisk you restore images once update is installed don't restart go to magisk and install to inactive slot then you can restart if you had twrp or orange fox in 11 you had to manually restore stock recovery or the update would fail but as of now there is no twrp for a12 available so you don't have to worry about that yet
It was posted about 2 hours ago on Asus website, here is the direct link: https://dlcdnets.asus.com/pub/ASUS/...300-2304-user.zip?model=rog phone 5 （zs673ks）
I just updated and phone runs smooth, no data loss during upgrade, magisk and lsposed works.
MarekPietrzak said:
It was posted about 2 hours ago on Asus website, here is the direct link: https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS673KS/UL-ASUS_I005_1-ASUS-33.0210.0210.200-1.1.300-2304-user.zip?model=rog phone 5 （zs673ks）
I just updated and phone runs smooth, no data loss during upgrade, magisk and lsposed works.
Click to expand...
Click to collapse
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
rami88436 said:
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Click to expand...
Click to collapse
MarekPietrzak said:
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
Click to expand...
Click to collapse
MarekPietrzak said:
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
Click to expand...
Click to collapse
hey, Thanks for replay, i am facing now another messeges.
1- the phone does not charging at all
2- when i plug in into chrage its reboot again and again.
3- the bootloader is open, but when i try to flash any files through bootloader i get:
FAILED (Status read failed (Too many links))
or
FAILED (remote: 'Warning: battery's capacity is very low
to recovery mode i am unable to go there
i tried boot or flash the twrp.img also only boot.img also flash_raw_and_wipe_data.cmd
nothing helps me!!!
Hello, can you try to keep phone on charger for a few hours? Maybe it will charge enough to enter recovery mode. You should never flash twrp by fastboot on a/b devices as they don't have recovery partition. Please restore stock boot.img extracted from payload.bin and after this try booting into fastbootD, not fastboot and then attempt flashing complete firmware package (raw). To boot into fastbootD, keep holding volume keys, when you see a bootloader screen use volume keys to select option "recovery mode". You should now enter stock recovery. Ussing vol keys select option "enter fastboot". You should be now in fastbootD. This is possible only with boot.img without twrp installed as fastbootD is a part of stock recovery, magisk is fine.
Remember to perform all flashing operations with usb port on the left side, the bottom one does not work in bootloader. And make sure you are using latest adb/fastboot binaries, these from popular auto-installers are usually outdated and may cause errors during flashing.
MarekPietrzak said:
Hello, can you try to keep phone on charger for a few hours? Maybe it will charge enough to enter recovery mode. You should never flash twrp by fastboot on a/b devices as they don't have recovery partition. Please restore stock boot.img extracted from payload.bin and after this try booting into fastbootD, not fastboot and then attempt flashing complete firmware package (raw). To boot into fastbootD, keep holding volume keys, when you see a bootloader screen use volume keys to select option "recovery mode". You should now enter stock recovery. Ussing vol keys select option "enter fastboot". You should be now in fastbootD. This is possible only with boot.img without twrp installed as fastbootD is a part of stock recovery, magisk is fine.
Remember to perform all flashing operations with usb port on the left side, the bottom one does not work in bootloader. And make sure you are using latest adb/fastboot binaries, these from popular auto-installers are usually outdated and may cause errors during flashing.
Click to expand...
Click to collapse
I've tried leaving it on overnight and it never charges, there's even no charging lights.
Yesterday I tried flashing via Bugjeager and it didn't work either (betwenn to android devices)
Although the bootloader is unlocked, it gives me a Not Allowed In Lock State message!
the current version of the installed firmware is that old that i flashed WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw, it is non extractable so i cant get the boot.img of it!
I am attaching here the matching boot.img for your 2101.95 firmware. Your phone boots to bootloader as I can see on the video but cannot enter recovery as you have corrupted your boot partition. Can you pm me output of fastboot getvar all command? Please do not post it publicly as it may contain private data such as serial numbers. Good luck!
Are you sure that you have unlocked bootloader? I understand that you have relocked your bootloader and since then your phone never booted into working system. It is not possible to unlock bl with fastboot, only with asus app which requires working Android system
MarekPietrzak said:
I am attaching here the matching boot.img for your 2101.95 firmware. Your phone boots to bootloader as I can see on the video but cannot enter recovery as you have corrupted your boot partition. Can you pm me output of fastboot getvar all command? Please do not post it publicly as it may contain private data such as serial numbers. Good luck!
Are you sure that you have unlocked bootloader? I understand that you have relocked your bootloader and since then your phone never booted into working system. It is not possible to unlock bl with fastboot, only with asus app which requires working Android system
Click to expand...
Click to collapse
wow you are alive haha i thought you not gonna answer me again. ok just 1 second
rami88436 said:
wow you are alive haha i thought you not gonna answer me again. ok just 1 second
Click to expand...
Click to collapse
Sometimes I can be a bit slow to respond as I am on the university during day. Hopefully your issue seems to be possible to be solved just by flashing raw firmware and wiping data partition.
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
rami88436 said:
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Click to expand...
Click to collapse
if youre still stuck, try to fastboot flash raw firmware and reroot and re update again. twrp only works for me with the magisk twrp installer but then you'll have to re flash patched image as it will remove root
chairman011 said:
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
Click to expand...
Click to collapse
try root your phone through kirnal su
chairman011 said:
if youre still stuck, try to fastboot flash raw firmware and reroot and re update again. twrp only works for me with the magisk twrp installer but then you'll have to re flash patched image as it will remove root
Click to expand...
Click to collapse
hahaha, the owner of this thread had helps me a lot but no way and yesterday i have been lost my imei and isn and the rest.., that was because i tried using miflash.
I did it in the same way as you, just after OTA i installed magisk to inactive slot and rebooted. Maybe you have some incompatible magisk modules which caused bootloop on A13.
chairman011 said:
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
Click to expand...
Click to collapse
MarekPietrzak said:
I did it in the same way as you, just after OTA i installed magisk to inactive slot and rebooted. Maybe you have some incompatible magisk modules which caused bootloop on A13.
Click to expand...
Click to collapse
Oh ok ok makes sense. I had curl module installed. I loved android 13 but I'ma stay on 12 cause the modified read/write script only works on Android 12 and 11 and I need it to uninstall bloatware. Disabling them isn't good enough for me lol I gotta uninstall them completely. I can only do that if system is read/write and this script flashed through two works great to have read/write system. Thank you though
rami88436 said:
hahaha, the owner of this thread had helps me a lot but no way and yesterday i have been lost my imei and isn and the rest.., that was because i tried using miflash.
Click to expand...
Click to collapse
Oh ok ok makes sense. Usually when I face a brick problem I just flash raw firmware fastboot
Actually you can debloat fully systemless, just create magisk module which replaces bloatware directories with empty folders. Or even better use this: https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
It is an automated way to make packages fully disappear without remounting system as rw. This module replaces them with empty folders, just like in the manual solution. The packages disappear from system completely and if you install any debloated app from play store or apk it will be installed as user (non-system) app.
chairman011 said:
Oh ok ok makes sense. I had curl module installed. I loved android 13 but I'ma stay on 12 cause the modified read/write script only works on Android 12 and 11 and I need it to uninstall bloatware. Disabling them isn't good enough for me lol I gotta uninstall them completely. I can only do that if system is read/write and this script flashed through two works great to have read/write system. Thank you though
Click to expand...
Click to collapse
MarekPietrzak said:
Actually you can debloat fully systemless, just create magisk module which replaces bloatware directories with empty folders. Or even better use this: https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
It is an automated way to make packages fully disappear without remounting system as rw. This module replaces them with empty folders, just like in the manual solution. The packages disappear from system completely and if you install any debloated app from play store or apk it will be installed as user (non-system) app.
Click to expand...
Click to collapse
Oh wow thank you man I'll give it a shot.
I found a gui-based app on github to systemlessly debloat, it is easier to use than this script I posted link to. Here is the link: https://github.com/sunilpaulmathew/De-Bloater
Does anyone have the full RAW firmware, flashed via fastboot? Thank you all
ThienAn2023 said:
Does anyone have the full RAW firmware, flashed via fastboot? Thank you all
Click to expand...
Click to collapse
Mod. edit: private link removed. alecxs