Develop Bugs

[Q] Reinstalling stock ROM 2.3.5 EU

Hi!
There is a chance to reinstall HTC stock ROM 2.3.5? Already I have the newest hboot and s-off.
I'm asking because RUU shows me error 155 and on phone screen shows me: Security fail! Update fail!
Thx for reply!

use fastboot.exe with the following commands and extracted files from ROM.zip?
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img

Okay, thanks, but how can I extract this files from RUU? Already i have only recovery.img and how I can get the rest of needed files?
Or maybe anyone can send me a link to download this files from stock 2.2.5 ROM EU?
Thx for reply!

if you goto that thread, i think it's called "s-on gsm how to upgrade to 2.3.5", or something like that, download that package and it will be "Gingerbread 2.3.5 (v2.13.401.2).zip", extract that and you will have ROM.zip, extract that and you will have all 3 .img files

Thanks very much, I have last question ( maybe ) Can I flash PG76IMG.zip with 2.3.5 throught hboot, or I must extract all 3 files from this .zip and flash trought fastboot?

you can try that way yes, but if it gives you error (like CID error or similar) then use fastboot to flash manually.
also, don't forget to do factory reset from recovery first if you can and clean all cache etc.

Thanks, I Remember that

unbranded rom
my phone is US Tmobile. I saw that because of the CID I can't flash european rom, but also I can't find unbranded US rom? Any suggestions?

Stock WW 2.13.40.13.img file

Hi, I was wondering if someone could make a stock img file of ww 2.13.40.13. I seem to get system errors with the pre-rooted version and it stops me from flashing back to stock with the downloaded stock files (they come as a zip file).
Even if you could send me in the right direction to make one myself, that would be helpful.
Fixed it without the image file.
Just to let others know how,
Connected via ADB and erased system, boot.img and droid_boot.img then reflashed WW versions... All working fine now but was a few hours of frustration and hair pulling... Honestly, I look like Lex Luthor...

Same problem but didn't understand your procedure
Thank you for your solution but I didn't understand
I had the same problem : I rooted my phone by flashing pre-rooted system.img. It worked but now I want to be able to update OTA. So I need to replace pre-rooted system.img with stock one.
Can you please explain how you "erased system, boot.img and droid_boot.img then reflashed WW versions"?
I tried the following : fastboot erase system, fastboot erase cache, and then adb sideload UL-Z00A-WW-2.13.40.13-user.zip with official firmware downloaded from asus.com. But now my phone is blocked on black boot screen "ASUS in search of incredible, powered by android". I can only boot to recovery. Can you repair my phone without wiping data? Thank you.

Not even any clue
So after hours of searches, the only solution I found was to flash a pre-rooted system.img back. My phone boots again normally.
But I don't have any solution to my first problem.
When I try to flash official firmware, I do:
1. In phone recovery menu : apply adb update
2. In PC terminal : adb sideload UL-Z00A-WW-2.13.40.13-user.zip
3. At around 52% transfer, error displayed on phone :
Can't install this package (Wed Apr 1 00:14:20 CST 2015) over newer build (Fri May 29 00:14:18 CST 2015)
E:Error in sideload/package.zip
(Status 7)
Installation aborted.
Has anyone succeeded in getting back to a stock system after flashing a pre-rooted one? I searched in many thread and did not found any solution.

remidem said:
So after hours of searches, the only solution I found was to flash a pre-rooted system.img back. My phone boots again normally.
But I don't have any solution to my first problem.
When I try to flash official firmware, I do:
1. In phone recovery menu : apply adb update
2. In PC terminal : adb sideload UL-Z00A-WW-2.13.40.13-user.zip
3. At around 52% transfer, error displayed on phone :
Can't install this package (Wed Apr 1 00:14:20 CST 2015) over newer build (Fri May 29 00:14:18 CST 2015)
E:Error in sideload/package.zip
(Status 7)
Installation aborted.
Has anyone succeeded in getting back to a stock system after flashing a pre-rooted one? I searched in many thread and did not found any solution.
Click to expand...
Click to collapse
Apparently you can unroot through supersu. This should then allow OTA updates...

Already tried
ultramag69 said:
Apparently you can unroot through supersu. This should then allow OTA updates...
Click to expand...
Click to collapse
No I already tried to unroot via supersu, I have the same issue. As said in thread
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
"If you root via*METHOD 1*you can update SuperSu app as well as update binaries but*PLEASE DON'T apply any OTA updateas the phone*WILL GET STUCK IN A BOOTLOOP...Manually flash the firmware via adb..."
But it is not written how to revert METHOD 1 root.

remidem said:
No I already tried to unroot via supersu, I have the same issue. As said in thread
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
"If you root via*METHOD 1*you can update SuperSu app as well as update binaries but*PLEASE DON'T apply any OTA updateas the phone*WILL GET STUCK IN A BOOTLOOP...Manually flash the firmware via adb..."
But it is not written how to revert METHOD 1 root.
Click to expand...
Click to collapse
From what I did, the pre-root.img was fine to OTA with as long as you don't update supersu... I flashed a pre-root.img on then applied the OTA through a 32gb or FAT32 formatted sd card and it worked fine, also took out root so you will need to put back in there if you want it....

Impossible to update with sdcard
ultramag69 said:
From what I did, the pre-root.img was fine to OTA with as long as you don't update supersu... I flashed a pre-root.img on then applied the OTA through a 32gb or FAT32 formatted sd card and it worked fine, also took out root so you will need to put back in there if you want it....
Click to expand...
Click to collapse
Thank you for your reply. I tried OTA update with sdcard:
1) In Settings/About/Software information, my current version is 2.13.40
2) I dowloaded, from http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999 update from 2.13 to 2.14
3) Copied to external sd, in root folder, and renamed zip to MOFD_SDCARD.zip
4) Rebooted in recovery
5) Update failed. Here is my log:
Finding update package...
I:Update location: /sdcard/MOFD_SDUPDATE.zip
Opening update package...
E:file path:/sdcard/MOFD_SDUPDATE.zip
Installing update...
script aborted: Package expects build fingerprint of asus/WW_Z00A/Z00A:5.0/LRX21V/2.13.40.13_20150401_8390_user:user/release-keys or asus/WW_Z00A/Z00A:5.0/LRX21V/2.14.40.19_20150415_9660_user:user/release-keys; this device has asus/WW_Z00A/Z00A:5.0/LRX21V/2.18.40.12_20150529_9543_user:user/release-keys.
Package expects build fingerprint of asus/WW_Z00A/Z00A:5.0/LRX21V/2.13.40.13_20150401_8390_user:user/release-keys or asus/WW_Z00A/Z00A:5.0/LRX21V/2.14.40.19_20150415_9660_user:user/release-keys; this device has asus/WW_Z00A/Z00A:5.0/LRX21V/2.18.40.12_2015
E:Error in /sdcard/MOFD_SDUPDATE.zip
(Status 7)
SD Installation aborted.
This is because the version of system.img is 2.18 and the fimware version is 2.13.
Indeed I have 2 choices:
- override system with a system.img in version 2.13, but I cannot find any.
- try to apply OTA update 2.17 to 2.18 or 2.18 to 2.19 but it seems risky.
Finally I found!!! I think that a version of the firmware is tagged in system partition and another version (classically the same) is tagged in data partition (this is the one you see in Parameters -> About -> Firmware version). When I wanted to flash a firmware the same version as the one written in parameters (2.13), my phone refused to downgrade because the version of system was higher (2.18). So I had to format the system partition, apply update with official 2.18 firmware. And it worked! My phone was unrooted and I could apply method 3 root.
My issue occurred because I made the following:
1) bought a phone with a 2.13 firware
2) used it for months, applied OTA updates until 2.18
3) flashed a 2.18 pre-rooted system.img
4) used it for weeks until a made an update of supersu
5) my phone couldn't boot any more, so I wiped data (I could avoid that, if I knew!). It made a factory reset, ie get back firmware to 2.13, but system was still in 2.18
Here is the procedure to revert a phone flashed with a pre-rooted system.img (to sell it, send back to warranty, or root with another method):
1) Download official firmware from asus website in the same or higher version of your pre-rooted system.img. Do not rely on version in Parameters -> About -> Firmware version. Or simply download the latest version.
2) In your phone bootloader, enter the following commands with your PC:
fastboot erase system (I'm not sure it is necessary)
fastboot format system
3) With your phone, go into recovery menu, then to "Update with adb"
4) With your PC, go to the directory where you downloaded the firmware as zip, and enter the following command: adb sideload nom_du_fichier_teléchargé.zip
5) It takes about an hour
6) You can reboot
After that I used method 3 to root again, so that I can now OTA update exactly the same way I used to do before rooting. Moreover, I think I can update supersu as well.

tried this method, and it fails with a /sideload/package.zip error using the .18 zip. Trying to unlock as i took the .22 update... root works fine though

wrecklesswun said:
tried this method, and it fails with a /sideload/package.zip error using the .18 zip. Trying to unlock as i took the .22 update... root works fine though
Click to expand...
Click to collapse
Someone said you need to use fastboot to flash droidboot.img, boot.img, system.img and recovery.img to go back to an older version. Not sure if this works as I unlocked bootloader when I had the chance.
If you can't then you might have to wait for the "Official" unlock tool but ASUS will know and you will be out of warranty.

ultramag69 said:
Hi, I was wondering if someone could make a stock img file of ww 2.13.40.13. I seem to get system errors with the pre-rooted version and it stops me from flashing back to stock with the downloaded stock files (they come as a zip file).
Even if you could send me in the right direction to make one myself, that would be helpful.
Fixed it without the image file.
Just to let others know how,
Connected via ADB and erased system, boot.img and droid_boot.img then reflashed WW versions... All working fine now but was a few hours of frustration and hair pulling... Honestly, I look like Lex Luthor...
Click to expand...
Click to collapse
Can you please post the complete steps for the fix! Stuck here for hours, you wouldn't want to look let Lex Luthor

kamranyusuf said:
Can you please post the complete steps for the fix! Stuck here for hours, you wouldn't want to look let Lex Luthor
Click to expand...
Click to collapse
VERY IMPORTANT - Make sure you have checked the MD5 checksum on the boot, droid_boot and recovery image files as these are definitely needed to boot phone. If these are corrupt then you can brick your phone... You have been warned...
Download firmware from here-http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
It is pre-rooted but the other files needed are included in the folder.
2. Put phone in fastboot mode and erased droid_boot.img, boot.img, recovery.img and system.img using command "fastboot erase (put choice here)"
3. Flash the files I just erased back on using fast boot - "
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
This got me the pre-rooted 2.13.40.13. As the supersu has been inserted it is fine to use OTA to update, just make sure you don't update supersu before the OTA flash.
Good luck....
And may you retain a strand or 3 of hair like Homer Simpson....

install lineageOS -- failure on verification

Hey, I think I read all the threads that could be helpful (development, Q&A, lineageos & cm-installguides, twrp-install and so on), but I don't get my phone to work.
I have a Xperia M2 Dual c2005 and want to get LineageOS working. I have no data left that I would need, so I try to start from new...
Steps already taken:
- unlocked bootloader for both IMEIs https://zifnab.net/~zifnab/wiki_dump/Install_CM_for_nicki.html#What_does_.22unlocking.22_mean.3F --> worked
- flashed boot.img (extracted from lineage-14.1-20170131-nightly-nicki-signed.zip) in fastboot-mode and went to recovery
- wanted to copy zip to device, but adb (also with sudo!) says: unauthorized (Please check the confirmation dialog on your device. ... but there is none)
- in CM-recovery i tried to flash via sideload, but it stops transferring data at around 50% and saying: E: signature verification failed ... and E: error 21
- had the md5sum created and put it in folder, still the same
- also tried, what shouldn't be done fastboot flash boot twrp-3.0.2-0-nicki.img --> doesn't work b/c of FOTA, so how to install twrp?
Any ideas how to install clean lineageOS? Thanks in advance.

...usually this problem cause bad kernel or image .. so wipe format,data,cache,dalvik cache, make factory reset in cwm... boot again to recovery and flash TWRP 2.8.6.0 zip. file via recovery and reboot again to recovery .. now flash latest lineage os , without any extract
.. here is link for twrp..: https://forum.xda-developers.com/xp...very-cwm-twrp-recoveries-custom-roms-t3016507
..dont forget!! flash this 2.8.6.0 version ... if doesnt work this little guide, try to format sdcard via recovery in advanced option "this is partition where is everithyng set on 0 " ... and try again

Thanks a lot! For me it worked the following way, since I didn't have CWM present:
- downloaded TWRP 2.8.7.0 from the link you provided
- extracted FOTAKernel.img
- in fastboot mode: sudo fastboot flash boot FOTAKernel.img
- reboot in recovery (worked well!)
- adb push lineageos14.1.xxx.zip /sdcard/
- install and choose image
Thanks a lot, after a couple of days of trying I do now understand Sony a little more (for my own, I only use Nexus, which works quite simple ).

jeensg said:
Thanks a lot! For me it worked the following way, since I didn't have CWM present:
- downloaded TWRP 2.8.7.0 from the link you provided
- extracted FOTAKernel.img
- in fastboot mode: sudo fastboot flash boot FOTAKernel.img
- reboot in recovery (worked well!)
- adb push lineageos14.1.xxx.zip /sdcard/
- install and choose image
Thanks a lot, after a couple of days of trying I do now understand Sony a little more (for my own, I only use Nexus, which works quite simple ).
Click to expand...
Click to collapse
no problem, iam glad i could help

Question Latest Twrp pros and cons

Today the unlock time for bootloader to unlock will complete and I Intend to install TWRP. I have found the latest officially supported twrp-3.6.1_11-0-alioth.img at https://eu.dl.twrp.me/alioth/. How does it compare to TWRP-3.5.1 https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-1-20210702.4300189/.
Can anyone guide me what are the pros and cons of using twrp-3.6.1_11-0-alioth.img and its limitations as compared to TWRP-3.5.1 as I can not find any documentation on twrp-3.6.1_11-0-alioth.img. Any help will be appreciated.
Also does the following limitations of TWRP-3.5.1 also apply to twrp-3.6.1_11-0-alioth.img ?
KNOWN LIMITATIONS:
The following are some known limitations due to either the design nature of Virtual A/B or a problem with ROM themselves. Please read carefully :-
You cannot format data after flashing a ROM zip (Limitation of Virtual A/B). If you want to format, then reboot recovery after flashing ROM. Additionally, if you are encrypted, the newly flashed ROM must be able to decrypt your device. If not, then you have to format data before flashing the ROM It appears, you can actually format data after reboot even if the new ROM cannot decrypt.
You can flash only one ROM in one boot. If you wanna flash another ROM, you must boot to system once. This is again a limitation of Virtual A/B.
Once you have rebooted after flashing a ROM, you cannot write to the data partition until you boot successfully to the new ROM. Android seals the data partition after a ROM flash to prevent any accidental brick since the newly flashed ROM is actually stored in /data. Only data format is allowed in this case. Once you successfully boot to the new ROM, your storage becomes ready for writing again.
Ideally, after flashing a new ROM, you should only need to wipe your data rather than format. But, due to a problem in the device trees current ROMs are using, you will have to format data if you are currently on miui and want to switch to a custom ROM. Specifically, the roms need this commit and to set vendor security patch level to fix this issue. Switching between custom ROMs should not need format, except for hentai OS.
If you are currently on hentai OS, then before using TWRP, you must flash vendor_boot from the link provided in every hentai OS release. Otherwise, you will get black screen. This is only needed when you boot to TWRP for the first time. Do not repeat this step again. Also, do not try this with beta version of the ROM. Use it only with stable.
If you reboot to older slot after flashing new ROM, the new ROM will be cancelled and you will have to reflash again. This is because of how Virtual A/B works.
If you must flash magisk via recovery (it's not recommended now), please uncheck "Inject TWRP after install" else TWRP will remove magisk.
Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.
Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.

you dont search enough...
this is latest A12 TWRP....
https://dl.akr-developers.com/?dir=skkk/TWRP
Installation:
activateUSB DEBUGGIN and OEM unlocked on Poco
(copy all files in Adb folder) rename the long TWRP file to twrp.img
Disable all security settings like PIN, pattern, fingerprint
start Poco in fastboot
fastboot boot twrp.img"
copy twrp.img to Poco or "adb push twrp.img /sdcard/"
TWRP Menü -> Advanced -> Flash Current TWRP or Install Recovery Ramdisk -> you must test it... both should work
TWRP Menü -> Reboot -> recovery
Magisk and safety net working great...
see also....
Xiaomi devices on Android 12 via Fastboot only:
- Download our ROM zip file
- Unpack downloaded zip file in the PC using WinRAR
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
greeting

hofi01 said:
you dont search enough...
this is latest A12 TWRP....
https://dl.akr-developers.com/?dir=skkk/TWRP
Installation:
activateUSB DEBUGGIN and OEM unlocked on Poco
(copy all files in Adb folder) rename the long TWRP file to twrp.img
Disable all security settings like PIN, pattern, fingerprint
start Poco in fastboot
fastboot boot twrp.img"
copy twrp.img to Poco or "adb push twrp.img /sdcard/"
TWRP Menü -> Advanced -> Flash Current TWRP or Install Recovery Ramdisk -> you must test it... both should work
TWRP Menü -> Reboot -> recovery
Magisk and safety net working great...
see also....
Xiaomi devices on Android 12 via Fastboot only:
- Download our ROM zip file
- Unpack downloaded zip file in the PC using WinRAR
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
greeting
Click to expand...
Click to collapse
I know where the lastest TWRP for Poco F3 is and how to install it as I have already installed it. That was not the question. The question was that "does limitations of TWRP-3.5.1 also apply to twrp-3.6.1_11-0'? Limitattions like being forced to reboot TWRP after flashing a every single zip file and other limitations like it as mentioned above. Thanks for your reply anyways.

so for me, TWRP does not start again, after installing a file.
I install TWRP, boot into TWRP again and install Magisk. after that I boot into the ROM.
TWRP does not restart itself

So, still no decryption on A12?
I wanted to test new custom roms but i dont want to have to reinstall everything from scratch if i go back to my current rom (.EU).
Can twrp make a full backup and restore it despite not having decryption?
If it cant, can I make a full back up of my phone from cmd in fastboot mode? (so i can just flash it from fastboot to restore everything as it is now)

Question Find Device storage corrupted. Your device is unsafe now.( POCO F3 and Other MIUI Devices)

Last night I do have a problem with the custom rom that I have installed, because of the battery problem keeps on dropping, so I decided to go back to the official stock rom which is for global however after flashing the fastboot rom via Miflash Tool, I have a welcome message that says Find Device storage corrupted. Your device is unsafe now. I thought that I just need to activate this to the device admin, after a reboot I tried to check it out if this message if this message will still pop up, and it keeps on popping up. I have flashed the rom again and it keeps on happening.
Things that I have Tried:
So I tried to check for other ways that I could get rid of this but this doesnt work on the terminal via TWRP. "
[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now".
[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now". How to fix "Find Device storage corrupted. Your device is unsafe now" ? (At your own risk... I'm not responsible for damage or brick) Required : - Be rooted and...
forum.xda-developers.com
".
The one that works:
Things that you needed:
1. Download Mi Flash Tool(https://www.xiaomiflash.com/)
2. Minimal ADB and Fastboot
3. 7zip or BreeZip
4. TWRP A12(
TWRP A12.rar
drive.google.com
) if you are using other MIUI and devices and want to check it this will work then just use your twrp that is recommended for your mui device.
5. Global Rom (https://xiaomifirmwareupdater.com/miui/alioth/stable/V12.5.6.0.RKHMIXM/)
warning: make sure that you are using the right rom for your device, my device that I am using is a global variant so I need to flash a global version, if you are using other MIUI device and want to check it out just download the miui that works for you must be on a later update of the rom if the latest current rom that you are working on right now didnt work.
Steps to follow.
1. Extract the Rom which you have downloaded using the 7zip or BreeZip, so for me I extracted the version 12.5.6.0 take note that this is not the latest rom but for this to work we need to be in a later update this rom is an android version 11.
2. after extracting the fastboot rom file type TGZ you will notice that the one that you extracted is on a TAR file type, and you need to extract the TAR file type for you to have the folder "alioth_global_images_V12.5.6.0.RKHMIXM_20220210.0000.00_11.0_global_62b4f5d6ca"
3. Using the Mi Flash Tool, just pick the clean all and start the flashing.
4. After flashing the rom set up the phone but do not update it.
5. On your extracted folder for the rom go to the folder that says images and look for 'persist" this is an img file. copy the persist img file and paste it on your Internal memory of your phone.
6. Turn off your phone and go to fastboot by pressing the volume down as well as the power button. You will notice that the fastboot logo is the older version since we are using an older rom.
7. Extract the TWRP A12 and you should have the disc recovery image of it, copy and paste it on your Minimal ADB and Fastboot folder and rename it "recovery".
8. While you are on the Minimal ADB Fastboot folder make sure that your phone is plug in to the usb port on your computer, click the cmd here on the Minimal ADB and Fastboot Folder and you should able to run the cmd.
9. run the following commands:
fastboot devices (then press the enter)
warning: make sure that the fastboot devices is able to see your device.
after seeing the device run this command:
fastboot boot recovery.img (then press enter)
the device should boot to the twrp if its on chinese look for settings and set it to english. we are not flashing the twrp we are just going to use it temporarily thats why we are only going to boot it to twrp recovery.
10. On your twrp, go to install, click the install image and look for your persist.img that we have copied earlier to your internal memory
you should find it on the sdcard folder. just flash and you will see that you have successfully flashed the persist image and then just reboot your phone.
After rebooting your phone you will notice that the "Find Device storage corrupted. Your device is unsafe now." will not prompt. Since I already have the current fastboot rom I have tried to flash the current fastboot rom and locked my device and fixed the problem permanently without any problem.

You wrote too much for something that could be written in a few sentences. And why would anyone downgrade an android or flash a clean fastboot ROM? (Android or MIUI version doesn't matter)
Summary guide:
1. Download the fastboot ROM from here and extract the "persist.img" image or dump the "persistbak" partition from your device and rename this file to "persist.img"
2. Put persist.img into your device's internal memory and go to TWRP
3. In TWRP, go to: Install> select install image> select file persist.img> select "Persist" partition
4. Restart the device, it should work fine

uvzen said:
You wrote too much for something that could be written in a few sentences. And why would anyone downgrade an android or flash a clean fastboot ROM? (Android or MIUI version doesn't matter)
Summary guide:
1. Download the fastboot ROM from here and extract the "persist.img" image or dump the "persistbak" partition from your device and rename this file to "persist.img"
2. Put persist.img into your device's internal memory and go to TWRP
3. In TWRP, go to: Install> select install image> select file persist.img> select "Persist" partition
4. Restart the device, it should work fine
Click to expand...
Click to collapse
Wrote it down for the newbies that doesnt know how to fix anyway thanks for the summary. I have to downgraded it because the latest current rom doesnt work give me "invalid sparse file format at header magic" error as I flash the persist.img file, via twrp.

mizuhored said:
Wrote it down for the newbies that doesnt know how to fix anyway thanks for the summary. I have to downgraded it because the latest current rom doesnt work give me "invalid sparse file format at header magic" error as I flash the persist.img file, via twrp.
Click to expand...
Click to collapse
If you are using TWRP from Nebrassy then use skkk TWRP or OrangeFox. Flashing persist should work fine on both recoveries (I did it myself recently).

uvzen said:
If you are using TWRP from Nebrassy then use skkk TWRP or OrangeFox. Flashing persist should work fine on both recoveries (I did it myself recently).
Click to expand...
Click to collapse
Thats great but this is the one that works for me anyways. At least we have found out the things that we needed in order for it to be fixed. Just sharing my ideas and how did I fixed the problem myself. Thanks for sharing of your ideas. Hoping that we could share our ideas to others as well. Been on a nightmare last night cant sleep because of this problem. Trying to figure out what to do since using the cmds via terminal on twrp doesnt work for me. Need to downgrade for me to fix it.

mizuhored said:
Thats great but this is the one that works for me anyways. At least we have found out the things that we needed in order for it to be fixed. Just sharing my ideas and how did I fixed the problem myself. Thanks for sharing of your ideas. Hoping that we could share our ideas to others as well. Been on a nightmare last night cant sleep because of this problem. Trying to figure out what to do since using the cmds via terminal on twrp doesnt work for me. Need to downgrade for me to fix it.
Click to expand...
Click to collapse
Could you please confirm if flashing persist.img doesn't mess up with sensor like fingerprint, l1, compass etc..? I have seen other forums talking about possibility of losing these in case perist is flashed from rom. I have this message for some time now, but all other sensors work fine, even l1 certification and saftynet. Thanks in advance.