Develop Bugs

Help! Sensors turned off!

Hello everyone. I was with Android 7 on my ZS570KL and returned to 6 for a tutorial found on the internet and worked, but all the sensors of the device were disabled (screen rotation, gyroscope, approximation, fingerprint [only registers up to 93% and gives error], and all the others). How do I reactivate? I came back to Android 7, formatted the device several times, and nothing solves!

What tutorial and why?
No information = no help

{
"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"
}
I do not remember where I found the tutorial and the files, but the process is this:
1. Download http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZS570KL/UL-Z016-WW-4.12.40.1698-user.zip
2. Download https://mega.nz/#!tp9DSQ4b!3wdDLsh3BBtPju8G74xlDjLJ9QywFaoLs1T11mMt3QQ
3. Unzip FlashTools64_20161125.zip
4. Unzip UL-Z016-WW-4.12.40.1698-user.zip and move out files under firmware-update to FlashTools folder
5. Put downgrade.bat, boot.img, recovery.img to FlashTools folder
6. Reboot phone to bootloader and click downgrade.bat
The reason was to swap the conventional root SU through the Magisk. I tried to reinstall 7 just by replacing the original recovery available here in XDA, but the process was not going to restart, so I followed that one to try to return and reinstall everything. It worked, I got back to 6, but I did not know everything. It looks like a computer without the drivers installed.

I'd downgrade again, if it was me, this time I'd install a stock Rom (MM) from ASUS. Then test everything again. If everything is good to go then I'd root and upgrade.
Changing the OS in the middle doesn't help if you have a problem.
Especially if it just builds upon the foundations of the previous OS...
Did you flash a complete N rom or do an update?

The ROMs I try are exactly those of the Asus site. I tried the downgrade again to version 4.12.40.1698 and realized something when I flash in recovery mode. The following error messages appear:
Unmount of /firmware failed: no such volume
Mount: failed to mount /dev/block/bootdevice/by-name/mdtp at /firmware: No such file or directory
Unmount of /firmware failed, no such volume
What is it? How to solve?

I need the original kernel and recovery of the latest firmware released, can anyone make it available?

AndreSantoro84 said:
I need the original kernel and recovery of the latest firmware released, can anyone make it available?
Click to expand...
Click to collapse
These recovery images are from nenebear59, thanks to him !
Z016-WW-5.14.44.2212_recovery :
For 2.15GHz CPU
For 2.4GHz CPU

Thank you very much! Now I need the "persist.img" file, of the same rom, can you make it available? I thank you!

I downloaded the source code kernel from the Asus site, and the compressed file has a sensor folder. I downloaded the kernel zip file to my memory card and tried to install via recovery, however the following message appears: E: footer is wrong / E: signature verification failed. How do I get install by recovery or via flash in cmd?

I followed this tutorial (https://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061) and managed to recover the fingerprint reader, but the others are still turned off. I really need the correct file! Somebody help me, please!

I got it! I used the persist.img of the global rom of the Xiaomi Mi Mix and the sensors came back! Apparently it's a universal file that caters to any device. You can close the topic!

Hi.. i intend to downgrade my asus Zenfone 3 Deluxe to lollipop, can you upload files needed to repair issues please?
thank you!

equinoks said:
Hi.. i intend to downgrade my asus Zenfone 3 Deluxe to lollipop, can you upload files needed to repair issues please?
thank you!
Click to expand...
Click to collapse
Really??

Ryder. said:
Really??
Click to expand...
Click to collapse
sorry from nougat to marshmallow

There isn't android lollipop for the asus zenfone 3 series. They came out with marshmallow.

AndreSantoro84 said:
I got it! I used the persist.img of the global rom of the Xiaomi Mi Mix and the sensors came back! Apparently it's a universal file that caters to any device. You can close the topic!
Click to expand...
Click to collapse
HELLO! I'm having a similar issue. 5 times my Zs570kl end up stuck in Asus logo boot screen after being charging all night (with alarming overheating) . I had to wipe the device with factory reset every time to get it working again. Last time, when finally booted up, all sensor were off, and I couldn't make them work no matter how much I try factory reseting again. I think i could try to install the persist.img file you mention, could you help me to find it? Thanks so much in advance for your help.
Asus Z016D (ZS570KL) 2.15 SKU WW_user_5.15.44.2562 build

equinoks said:
Hi.. i intend to downgrade my asus Zenfone 3 Deluxe to lollipop, can you upload files needed to repair issues please?
thank you!
Click to expand...
Click to collapse
Come on. To downgrade, you need to download the official rom from the Asus website (version WW-4.12.40.1698 - do not forget to check if your device is 2.15 or 2.4 ghz). Downloaded, need to put the rom inside a micro sd card (can not be internal storage, need to be in sd). In addition, it must be with the original recovery (the version is indifferent), if it is in TWRP it will not work. Once you have done this, you will have access to recovery mode, go to the "install zip from sd card" option, locate the zip file of the rom and install it, and just wait. Having problems, report here.

cazadormoron said:
HELLO! I'm having a similar issue. 5 times my Zs570kl end up stuck in Asus logo boot screen after being charging all night (with alarming overheating) . I had to wipe the device with factory reset every time to get it working again. Last time, when finally booted up, all sensor were off, and I couldn't make them work no matter how much I try factory reseting again. I think i could try to install the persist.img file you mention, could you help me to find it? Thanks so much in advance for your help.
Asus Z016D (ZS570KL) 2.15 SKU WW_user_5.15.44.2562 build
Click to expand...
Click to collapse
Hello! To reinstall the sensors is very simple (both work to find out the way, but then it gets simple hahaha). Download the adb files (it is available here in the forum, and inside the folder put the persist.img that I will make available here.) Access the fastboot mode on the device, connect to the computer, and open the command prompt inside the folder. Open the CMD, type the following command line: fastboot flash persist persist.img and press enter. The file will be rewritten and after that the sensors will be reconfigured. Restart the device. Having problems, report here.

Solved!
AndreSantoro84 said:
Hello! To reinstall the sensors is very simple (both work to find out the way, but then it gets simple hahaha). Download the adb files (it is available here in the forum, and inside the folder put the persist.img that I will make available here.) Access the fastboot mode on the device, connect to the computer, and open the command prompt inside the folder. Open the CMD, type the following command line: fastboot flash persist persist.img and press enter. The file will be rewritten and after that the sensors will be reconfigured. Restart the device. Having problems, report here.
Click to expand...
Click to collapse
THANK YOU ANDRE!!! I'm really really happy to tell you that everything worked PERFECTLY. I wasn't sure if I need to unlock the bootloader and flash root first, so I tried to do it. I've been able to unlock the bootloader, but for some reason, when I flash the bootroot.img following the instructions from this post - https://forum.xda-developers.com/ze...v-liftoff-zs570klpro-official-unlock-t3557276 -, I get the asus logo boot loop. Anyway, without the root I flash the persist file and, as you said, all the sensors were reconfigured.
Again, muito muito obrigado!!!

cazadormoron said:
THANK YOU ANDRE!!! I'm really really happy to tell you that everything worked PERFECTLY. I wasn't sure if I need to unlock the bootloader and flash root first, so I tried to do it. I've been able to unlock the bootloader, but for some reason, when I flash the bootroot.img following the instructions from this post - https://forum.xda-developers.com/ze...v-liftoff-zs570klpro-official-unlock-t3557276 -, I get the asus logo boot loop. Anyway, without the root I flash the persist file and, as you said, all the sensors were reconfigured.
Again, muito muito obrigado!!!
Click to expand...
Click to collapse
If you want to root, flash the twrp and then supersu zip from twrp

Unable to do the initial fastboot boot "twrp.img" file

Every time I'm trying to run the "fastboot boot twrp-3.2.1-0-taimen.img" command for my Pixel 2 XL (or any twrp .img file for the P2XL for that matter except the alpha version), I am constantly stuck at "downloading 'boot.img' . . ." (attached image #2). Attached image #1 shows that I unlocked my bootloader.
On the computer terminal, the "downloading 'boot.img' . . ." message will stay there until I either start my phone again or restart the bootloader. I am also 100% certain I have been in the correct directory this entire time otherwise I don't think I would have even made it this far. Attached image #3 shows where the twrp.img file is. Line 1 on my terminal also shows that.
I'm at a loss. Any help would be appreciated.
{
"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"
}
(I'm assuming if I see "DEVICE STATE - unlocked" on the fastboot screen, the bootloader should be unlocked)

https://imgur.com/a/w4DWq
If the attached images do not load, then I have uploaded the images on Imgur

did you unlock the critical partition as well? Maybe that's the problem?

anthony.moua95 said:
Every time I'm trying to run the "fastboot boot twrp-3.2.1-0-taimen.img" command for my Pixel 2 XL (or any twrp .img file for the P2XL for that matter except the alpha version), I am constantly stuck at "downloading 'boot.img' . . ." (attached image #2). Attached image #1 shows that I unlocked my bootloader.
On the computer terminal, the "downloading 'boot.img' . . ." message will stay there until I either start my phone again or restart the bootloader. I am also 100% certain I have been in the correct directory this entire time otherwise I don't think I would have even made it this far. Attached image #3 shows where the twrp.img file is. Line 1 on my terminal also shows that.
I'm at a loss. Any help would be appreciated.
(I'm assuming if I see "DEVICE STATE - unlocked" on the fastboot screen, the bootloader should be unlocked)
Click to expand...
Click to collapse
Are you on 8.0 or 8.1? If on 8.1, did you update via OTA, side load, or factory image flash??

Badger50 said:
Are you on 8.0 or 8.1? If on 8.1, did you update via OTA, side load, or factory image flash??
Click to expand...
Click to collapse
I am on 8.1 and updated it via OTA.

anthony.moua95 said:
I am on 8.1 and updated it via OTA.
Click to expand...
Click to collapse
Hmmmm, interesting, dealing with another member on another thread having the same problem you are, except he side loaded 8.1.
I'm hoping one of the RC's or Developers can chime in. I think this is where the A/B partitions cause headaches. Reason being, after your OTA, you now are on partition B. I'm thinking that adb automatically recognizes partition A by default. So when you are trying to fastboot anything, there is essentially no OS to flash to. I think you may have to flash the stock factory image to both partitions to be able to root. Having said all that, I could be way off base, which is why I'm hoping for some help in this matter :good:

Have you tried a different cable yet?

Badger50 said:
Hmmmm, interesting, dealing with another member on another thread having the same problem you are, except he side loaded 8.1.
I'm hoping one of the RC's or Developers can chime in. I think this is where the A/B partitions cause headaches. Reason being, after your OTA, you now are on partition B. I'm thinking that adb automatically recognizes partition A by default. So when you are trying to fastboot anything, there is essentially no OS to flash to. I think you may have to flash the stock factory image to both partitions to be able to root. Having said all that, I could be way off base, which is why I'm hoping for some help in this matter :good:
Click to expand...
Click to collapse
Oh geeze, this is something I can't be bothered with at the moment with my current situation (living and working in Thailand). I appreciate all the input that you have given on this thread though! I think I will just keep my phone where it is at now then (unlocked bootloader, 0 modifications, 8.1.0). But I will continue to follow and see if there are any definitive or streamlined solutions to this potential problem in the (near) future. Adaway and Viper4Android are still very important enough reasons for me to root.
I will also add that when I tried rooting via the magisk method (patch_boot.img), I kept getting a message along the lines of
"target didn't report max-download-size
sending 'boot' (x KB)...
FAILED (remote: Requested download size is more than max allowed)
finished. total time: 0.123s"
Although even though despite always getting a message like this, I was able to somehow get root successfully one time. I decided to unroot and try to duplicate the root result but to no avail. Also got that annoying "internal problem with your device" message and followed @topjohnwu's tutorial only to get the "target didn't report max-download-size...FAILED (remote: Requested download dize is more than max allowed)" message again.
My laptop is currently running Manjaro (based on Arch Linux) but I can't imagine it being the reason I keep getting that "target didin't report max-download-size" message.

ilal2ielli said:
Have you tried a different cable yet?
Click to expand...
Click to collapse
Unfortunately I only have one USB-A to USB-C cable (a Sony one).

equlizer said:
did you unlock the critical partition as well? Maybe that's the problem?
Click to expand...
Click to collapse
I've tried numerous times and it always gave me a fail message or acknowledgement that my phone was already unlocked I'm giving up until I see a more streamlined answer to this potential problem

Make sure you adb/fastboot is up to date, it has caused many headaches for people trying to use older versions.

Badger50 said:
Hmmmm, interesting, dealing with another member on another thread having the same problem you are, except he side loaded 8.1.
I'm hoping one of the RC's or Developers can chime in. I think this is where the A/B partitions cause headaches. Reason being, after your OTA, you now are on partition B. I'm thinking that adb automatically recognizes partition A by default. So when you are trying to fastboot anything, there is essentially no OS to flash to. I think you may have to flash the stock factory image to both partitions to be able to root. Having said all that, I could be way off base, which is why I'm hoping for some help in this matter :good:
Click to expand...
Click to collapse
Exact thing happend to me. I sideloaded and I was stuck on partition B
I had to fully erase and start from scratch via full image method. Sucks but I got it going

anthony.moua95 said:
Unfortunately I only have one USB-A to USB-C cable (a Sony one).
Click to expand...
Click to collapse
I'd say try to get another cable ASAP, especially if anything else you do doesn't work.
When I first was attempting to unlock my bootloader, nothing worked when I was using third-party cables.
Luckily, my laptop had a USB-C port, so I was able to use the stock USB-C cable and I haven't had any problems since.

trim81 said:
Exact thing happend to me. I sideloaded and I was stuck on partition B
I had to fully erase and start from scratch via full image method. Sucks but I got it going
Click to expand...
Click to collapse
Kinda what I thought. How did you erase BTW? The interesting thing is that some of their adb commands won't work properly. Explain if you please how you did it so these guys can get back up to speed. Thanks for the input :good:

Badger50 said:
Kinda what I thought. How did you erase BTW? The interesting thing is that some of their adb commands won't work properly. Explain if you please how you did it so these guys can get back up to speed. Thanks for the input :good:
Click to expand...
Click to collapse
I'm on my mobile right now so I can't detail it but you would go to Google a site to download the full image. Then run the flashall command to wipe and start from scratch.
I was lucky I had a titanium backup for my apps.. I had to wipe eveything and start fresh.

trim81 said:
I'm on my mobile right now so I can't detail it but you would go to Google a site to download the full image. Then run the flashall command to wipe and start from scratch.
I was lucky I had a titanium backup for my apps.. I had to wipe eveything and start fresh.
Click to expand...
Click to collapse
Ok cool, that's the only way I know how to do it as well. Cool beans, thanks bro :good:

Hey, I had the exact same problem.
Posted a couple of times on the thread guide for root with magisk, ended with the same answer: fastboot/adb up to date ? Files where they should be ? (they dont need to be on the same folder as fastboot you know..., but they keep asking that...), and so on...
Tonight, latest attempt, instead of using my usb-c port, and my usb-a 3.0 port, I get back on my old laptop with 2.0 usb-a port and... It worked !
Just using 2.0 instead of 3.0 did the job ! You should try it

cavolo said:
Hey, I had the exact same problem.
Posted a couple of times on the thread guide for root with magisk, ended with the same answer: fastboot/adb up to date ? Files where they should be ? (they dont need to be on the same folder as fastboot you know..., but they keep asking that...), and so on...
Tonight, latest attempt, instead of using my usb-c port, and my usb-a 3.0 port, I get back on my old laptop with 2.0 usb-a port and... It worked !
Just using 2.0 instead of 3.0 did the job ! You should try it
Click to expand...
Click to collapse
Dude, if that's the answer, which it probably is, I'm gonna pull my hair out. Been trying everything I can to these folks out. And it's a flippin 8 dollar cable! Oh well, live and learn

I know tou probably did this already but I did not see it posted.
You did enable developer settings and enable oem unlock in developer settings?

Is there a solution to this issue? I have followed every set of directions I can find on XDA and beyond, wiped and wiped, locked and unlocked my phone a few different times. Tried different cables and different ports on my computer. No matter what I do, I am stuck at the "downloading boot" after trying to flash TWRP. Thanks in advance for any help.

adb/twrp issues....

Firstly, when plugging my 7t in to my windows 10 PC, I am asked to choose which mode to go in within usb preferences, as I did previously in order to achieve and ADB driver connection I chose file transfer.......
this didn't work for some reason, only when in MIDI did I get a confirmation with adb devices.....even though there is still no sign of adb interface in device manager.....
any ideas? I can get adb connection with MIDI but is this good enough to flash recoveries/boot images etc....?
I tried to flash twrp and I could successfully boot into twrp directly via fastboot but twrp couldn't seen any of my storage, despite having all security methods turned off...
all i want to do is gain root access but I am having no joy....
ever since android 10 rooting anything for me has been a pain in the ass......truly fed up....it shouldn't be this hard......
I also flashed a patched boot image in an attempt to gain root access but it all did was break my wifi........which i fixed by copying over the latest image and installing locally......
please HELP....

Everything about this issues is already said in this forum.

Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961

ontwykende said:
Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
Click to expand...
Click to collapse
sweet, ill check it out.....

ontwykende said:
Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
Click to expand...
Click to collapse
It would seem that TWRP is a no go, for awhile at least.....
anyone managed to gain root access by flashing a patched boot.img?

mediaman123 said:
It would seem that TWRP is a no go, for awhile at least.....
anyone managed to gain root access by flashing a patched boot.img?
Click to expand...
Click to collapse
Lots of people have. Just boot your version and use magisk to direct install and reboot then you have root

Josh McGrath said:
Lots of people have. Just boot your version and use magisk to direct install and reboot then you have root
Click to expand...
Click to collapse
Normally I would be able to carry out such tasks but because I now feel so fed up with it all could I trouble you to tell my step by step how that is done.....?
many thanks..

mediaman123 said:
Normally I would be able to carry out such tasks but because I now feel so fed up with it all could I trouble you to tell my step by step how that is done.....?
many thanks..
Click to expand...
Click to collapse
I made a tool to install the latest ADB, Fastboot and USB drivers for windows, its very easy to use, just double click the file to start the installation process
you can see it here:
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Screenshot:
{
"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"
}

fawazahmed0 said:
I made a tool to install the latest ADB, Fastboot and USB drivers for windows, its very easy to use, just double click the file to start the installation process
you can see it here:
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Screenshot:
Click to expand...
Click to collapse
I can operate that fine, its just how to obtain boot.img files etc, patch them and so on..

mediaman123 said:
I can operate that fine, its just how to obtain boot.img files etc, patch them and so on..
Click to expand...
Click to collapse
Oh, I thought, you are have issues with adb, and for root, you just have to flash magisk using twrp

fawazahmed0 said:
Oh, I thought, you are have issues with adb, and for root, you just have to flash magisk using twrp
Click to expand...
Click to collapse
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....

mediaman123 said:
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....
Click to expand...
Click to collapse
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access

fawazahmed0 said:
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access
Click to expand...
Click to collapse
thanks for this......want to try and avoid wiping if possible but if I really want root I will do it.....
what does the command fastboot -w do?

mediaman123 said:
thanks for this......want to try and avoid wiping if possible but if I really want root I will do it.....
what does the command fastboot -w do?
Click to expand...
Click to collapse
it wipe's the data

mediaman123 said:
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....
Click to expand...
Click to collapse
fawazahmed0 said:
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access
Click to expand...
Click to collapse
TWRP is not functional at the moment, so stay away from it.
The only way to root right now is to use the patch boot image method.

Lossyx said:
No don't do this.... This is not about encryption at all. It's about the major partitioning changes that has happened in Android 10. Wiping the system will just make everything worse.
Avoid using TWRP at all.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Oh, I didn't know this phone was on Android 10, Thanks for letting me know.
TWRP doesn't support Android 10 yet.
You can see it here
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Actually there is a twrp compiled for this phone, but that doesn't work , you can see the messages in thread:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
The steps I told, was for Android 9 and earlier devices, I assumed, this is an old device.
@mediaman123, So please wait, until twrp starts supporting the Android 10.
And for rooting, I am not sure, whether magisk supports this new phone or not.
Maybe @Lossyx can help you on that.

https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Sent from my OnePlus7TPro using XDA Labs

Lossyx said:
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Seen this, however my device, the European version, is running on 10.0.6.....
The only boot images available with that post is the 10.0.3...
wouldn't feel comfortable using them.....
I would like to know how to extract the stock boot image from either the firmware file or the phone itself...

mediaman123 said:
Seen this, however my device, the European version, is running on 10.0.6.....
The only boot images available with that post is the 10.0.3...
wouldn't feel comfortable using them.....
I would like to know how to extract the stock boot image from either the firmware file or the phone itself...
Click to expand...
Click to collapse
You can go ahead and just fastboot boot them. If it works then just proceed, if it doesn't, just hold volume up+down and power button. (To boot into fastboot or restart phone)
Nothing will change in the system because it only boots a temporary image.
If your want to extract your own boot image you can use this tool.
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs

Lossyx said:
You can go ahead and just fastboot boot them. If it works then just proceed, if it doesn't, just hold volume up+down and power button. (To boot into fastboot or restart phone)
Nothing will change in the system because it only boots a temporary image.
If your want to extract your own boot image you can use this tool.
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
So if it boots an older image successfully I can move it over to the phone to patch to then flash it or use the already patched one and flash that...?..

How To Guide Nokia G20 boot.img flashing!

Please be aware that this could damage your phone & I'm not responsible for this. So only do this if you really feel comfortable with it & you know about the risks!
This file is only for Nokia G20 TA-1365 and should not be used for any other device.
Download this file to manually Flash partition or partitions using fastboot Command.
For more detailed tutotial on how to flash this file you can read this tutorial here by senior member fipsib at XDA!
Let's say you want to flash boot.img partition so in CMD you will enter.
"fastboot flash boot boot.img" without quotes.
I have extracted OTA stock rom for my Nokia G20 and have all the files in the screenshot below. If you want all the files shown in the screenshot below I have uploaded them to Google Drive for faster and safer downloads rather than using any other file sharing service.
I have compressed all the files in a zip format and here is the Google Drive link for all the files shown below. Please request the access to the file so that I can grant access to you. I have done this to prevent Google setting an limit to download and avoid any unnecessary downloads.
{
"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"
}

Do you have to unlock bootloader to flash boot.img if you have to can you tell how????

Don't know said:
Do you have to unlock bootloader to flash boot.img if you have to can you tell how????
Click to expand...
Click to collapse
Thankyou buddy but actually this post is a guide.

mvikrant97 said:
Please be aware that this could damage your phone & I'm not responsible for this. So only do this if you really feel comfortable with it & you know about the risks!
This file is only for Nokia G20 TA-1365 and should not be used for any other device.
Download this file to manually Flash partition or partitions using fastboot Command.
For more detailed tutotial on how to flash this file you can read this tutorial here by senior member fipsib at XDA!
Let's say you want to flash boot.img partition so in CMD you will enter.
"fastboot flash boot boot.img" without quotes.
I have extracted OTA stock rom for my Nokia G20 and have all the files in the screenshot below. If you want all the files shown in the screenshot below I have uploaded them to Google Drive for faster and safer downloads rather than using any other file sharing service.
I have compressed all the files in a zip format and here is the Google Drive link for all the files shown below. Please request the access to the file so that I can grant access to you. I have done this to prevent Google setting an limit to download and avoid any unnecessary downloads.
View attachment 5450449
Click to expand...
Click to collapse
Please share download link.I need to unbrick my Nokia G20 that was bricked.I have no firmware

Download this OTA ROM and flash using Apply update from SD CARD in recovery menu.
Use external SD card.
I don't know whether this will work.
ROM link

Don't know said:
Do you have to unlock bootloader to flash boot.img if you have to can you tell how????
Click to expand...
Click to collapse
Yes need to unlock bootloader.

mvikrant97 said:
Download this OTA ROM and flash using Apply update from SD CARD in recovery menu.
Use external SD card.
I don't know whether this will work.
ROM link
Click to expand...
Click to collapse
Hi thanks for the link. But my phone is bricked, can't enter recovery or fastboot mode. So the only solution here is a read firmware or scatter file.

mvikrant97 said:
Please be aware that this could damage your phone & I'm not responsible for this. So only do this if you really feel comfortable with it & you know about the risks!
This file is only for Nokia G20 TA-1365 and should not be used for any other device.
Download this file to manually Flash partition or partitions using fastboot Command.
For more detailed tutotial on how to flash this file you can read this tutorial here by senior member fipsib at XDA!
Let's say you want to flash boot.img partition so in CMD you will enter.
"fastboot flash boot boot.img" without quotes.
I have extracted OTA stock rom for my Nokia G20 and have all the files in the screenshot below. If you want all the files shown in the screenshot below I have uploaded them to Google Drive for faster and safer downloads rather than using any other file sharing service.
I have compressed all the files in a zip format and here is the Google Drive link for all the files shown below. Please request the access to the file so that I can grant access to you. I have done this to prevent Google setting an limit to download and avoid any unnecessary downloads.
View attachment 5450449
Click to expand...
Click to collapse
Kindly grant access to [email protected] need to unbrick my device

I would like to ask how do I extract the boot.img file from the phone? I can access the internals through the adb shell. I would love to learn the strategies used to extract the firmware from android devices that do not make them available. Thanks!!

karangejo said:
I would like to ask how do I extract the boot.img file from the phone? I can access the internals through the adb shell. I would love to learn the strategies used to extract the firmware from android devices that do not make them available. Thanks!!
Click to expand...
Click to collapse
Simply... You can't without root.
To get root (permanent root) you must unlock your bootloader........
Please, read this post to understand what i'm talking about https://forum.xda-developers.com/t/nokia-g21-development.4424031/
I think that today there's no way to unlock G10/G20/G21 bootloader. Then, no root or custom recovery can be build.
Maybe, @mvikrant97 can share with us some info (PM).

I unlocked my g20 TA-1343 by taking a hundred tiny screws out , shorting the test point, and using MTK Client 1.6
hyperlink of the link i pastedhttps://github.com/bkerler/mtkclient
I only took it apart because the other option was send it back to HMD
But I don't know how to flash the bin files with magisk or whatever as they're not valid images. but the thing is basically root if i felt like learning.

jdberkzk said:
I unlocked my g20 TA-1343 by taking a hundred tiny screws out , shorting the test point, and using MTK Client 1.6
hyperlink of the link i pastedhttps://github.com/bkerler/mtkclient
I only took it apart because the other option was send it back to HMD
But I don't know how to flash the bin files with magisk or whatever as they're not valid images. but the thing is basically root if i felt like learning.
Click to expand...
Click to collapse
Do you mean the bootloader unlock?

mvikrant97 said:
Do you mean the bootloader unlock?
Click to expand...
Click to collapse
Yes I unlocked the bootloader with mtk client but i have the G20 ta-1343 and. I didn't have a stom rom for it.. and I bricked it trying to root it and corrupt the gpt it looks like, now I cant get it to load in mtk client anymore. I haven't errased the rest of the phone but it is in a/b format so i dont know if i should flash it? I was stuck in boot loop

jdberkzk said:
Yes I unlocked the bootloader with mtk client but i have the G20 ta-1343 and. I didn't have a stom rom for it.. and I bricked it trying to root it and corrupt the gpt it looks like, now I cant get it to load in mtk client anymore. I haven't errased the rest of the phone but it is in a/b format so i dont know if i should flash it? I was stuck in boot loop
Click to expand...
Click to collapse
mvikrant97 said:
Do you mean the bootloader unlock?
Click to expand...
Click to collapse
I got bootloader unlocked but when i flashed magisk i got stuck on the android one screen and then now it's back to the no OS boot loop and
Error on reading data: MMC error (0xc0040030)
in mtkclient. i cant get to fastboot anymore.

I du
mvikrant97 said:
Do you mean the bootloader unlock
Click to expand...
Click to collapse
I dumped everything from my phone to my computer except userdata super otp and flashinfo i think.
the bins would flash the same as images except I can't get them to flash. should I try another firmware or?

Question HELP - Realmeflash.exe "cannot find central directory"

Hello everyone !
I am French and my English is very bad so I will use Google translation to communicate with you!
This is what is happening.
Without doing it on purpose, I flashed the original boot with the unofficial TWRP one!
Since then, I can no longer use my phone and I no longer enter the RUI3 interface.
I used Realmeflash.exe to reinstall the firmware and it gives me an error message "cannot find central directory".
{
"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"
}
Do you know how to solve this problem?
Thank you for your help !

I had the same problem you gotta get the MCT OFP extractor tool and QFIL, you extract everything with the MCT tool and then use QFIL to flash but the super.img is broken up into multiple files which I Have no clue how to merge so I'm stuck for now but if I get it working I'll be sure to tell you

kamubendi said:
I had the same problem you gotta get the MCT OFP extractor tool and QFIL, you extract everything with the MCT tool and then use QFIL to flash but the super.img is broken up into multiple files which I Have no clue how to merge so I'm stuck for now but if I get it working I'll be sure to tell you
Click to expand...
Click to collapse
Thank you very much friend

@kamubendi
I posted the problem on this page too !
https://c.realme.com/in/post-details/1525231625514856448
If it can help for the future

I share the extraction of the firmware : RMX3363GDPR_12_C.06_2022042721590000
https://drive.google.com/drive/folders/1QpeyOBuavwC3gq25jfKnNaXqmVBMAwt-?usp=sharing

use this flash tool. put the ofp file in same folder run exe & select region start flash https://github.com/italorecife/OppoRealme-OFP-Flash

urstrulynaveen said:
use this flash tool. put the ofp file in same folder run exe & select region start flash https://github.com/italorecife/OppoRealme-OFP-Flash
Click to expand...
Click to collapse
I already tried !
According to Google the .exe is infected with a virus, but I used it anyway, because I know it can be a false positive.
During use, the flash does a lot of "Success" but also "Failed", because of data protection on certain files!
Arrived at "service.img", the flash stops and nothing advances!

I recently unbricked my GT ME using this flash tool only. Realme flash tool doesn't support AB partition & dynamic partition table. It is the only working tool to flash through fastboot. After flashing completion change slot
fastboot getvar current-slot
fastboot --set-active=a or b
fastboot reboot

urstrulynaveen said:
I recently unbricked my GT ME using this flash tool only. Realme flash tool doesn't support AB partition & dynamic partition table. It is the only working tool to flash through fastboot. After flashing completion change slot
fastboot getvar current-slot
fastboot --set-active=a or b
fastboot reboot
Click to expand...
Click to collapse
I choose slot A to do the flashing and then I have to activate slot B ?

Yup after flashing success

urstrulynaveen said:
Yup after flashing success
Click to expand...
Click to collapse
Hi, I got my phone back from this scam repairman!
He damaged my phone even more than I left him!
Could you send me a screenshot of your c:\adb\dir please!
I no longer have recovery mode and the repairman told me a lot of things that I supposedly did during the flashing to get rid of his bull****!!
Thank you.

@urstrulynaveen Otherwise I tried what you told me and I got this!

ToutanVrac said:
@urstrulynaveen Otherwise I tried what you told me and I got this!
View attachment 5618219
Click to expand...
Click to collapse
Ur already in slot a change it to b. Firmware may flashed in slot b

urstrulynaveen said:
Ur already in slot a change it to b. Firmware may flashed in slot b
Click to expand...
Click to collapse
I already did, I have this command line that appears instead !
When I launch the program for slot A, it's very random when it blocks !
On the image, it's xb1_config_a which bug !
And when I close the window, it gives me success before it disappears !
In general, I have 50% success and 50% failed !
The furthest file that gave me the bug is the "super" file !
Apparently it is cut into 5 parts with the OFP extractor.

ToutanVrac said:
I already did, I have this command line that appears instead !
View attachment 5618873
When I launch the program for slot A, it's very random when it blocks !
On the image, it's xb1_config_a which bug !
And when I close the window, it gives me success before it disappears !
View attachment 5618879
In general, I have 50% success and 50% failed !
The furthest file that gave me the bug is the "super" file !
Apparently it is cut into 5 parts with the OFP extractor.
Click to expand...
Click to collapse
Every partition flashes in both slots except super partition. Super partition only flashes in inactive slot, that's why u need to change the slot. Super partition flashing takes around 25 to 30 minutes you need to be patient. & After flashing check slot and change it

urstrulynaveen
Thank you very much for helping me, it motivates me not to give up !
Did you receive a lot of failed during flashing ?

@urstrulynaveen
Problem solved...everything works! !
I'm in the interface and everything seems fine at the moment.
The flashing problem was what you said for the "super" file, but the main problem was above all the fact that I wasn't using a USB port on the motherboard !
Were you able to root the phone ?

ToutanVrac said:
@urstrulynaveen
Problem solved...everything works! !
I'm in the interface and everything seems fine at the moment.
The flashing problem was what you said for the "super" file, but the main problem was above all the fact that I wasn't using a USB port on the motherboard !
Were you able to root the phone ?
Click to expand...
Click to collapse
Can you explain to me how to do it with pictures and writing and I will be very thankful to you

nighetspy said:
Can you explain to me how to do it with pictures and writing and I will be very thankful to you
Click to expand...
Click to collapse
It's very easy !
1. You download the latest firmware
2. You put your phone in fastboot mode
3. You connect your phone with the original cable to an available port on your motherboard
4. You open the "OppoRealme-OFP-Flash_1.0.exe"
5. You choose the "most logical" options
The files will install one by one and you may get a lot of errors!
Leave it, the program will continue and at some point there will be a "super" file which will take a long time to install (30 minutes), you wait and then you will see your phone restart as if it were brand new !

ToutanVrac said:
It's very easy !
1. You download the latest firmware
2. You put your phone in fastboot mode
3. You connect your phone with the original cable to an available port on your motherboard
4. You open the "OppoRealme-OFP-Flash_1.0.exe"
5. You choose the "most logical" options
The files will install one by one and you may get a lot of errors!
Leave it, the program will continue and at some point there will be a "super" file which will take a long time to install (30 minutes), you wait and then you will see your phone restart as if it were brand new !
Click to expand...
Click to collapse
Finally, after two weeks of trouble, the problem was solved, thank you very much