Database Info

[Recovery] TWRP 3.1.1 for Xperia X Compact

Greetings!
I'd like to present a TWRP recovery for the Xperia X Compact. This release should work on Xperia X single and dual-SIM variant of the device. I am an owner of Xperia X, but some users reported that my recovery works just fine on its smaller brother.
DISCLAIMER:
I'm not responsible for any damage done to your device. You have been warned.
REQUIREMENTS
Unlocked bootloader
Working ADB and Fastboot (You can get the latest version through Android Studio or by visiting this site)
FEATURES
MTP support
ADB Sideload
Backups and restores almost every partition
Full SELinux support
Working encryption. You can access /data within recovery
USB-OTG
DOWNLOADS
INSTALLATION
Unlock the bootloader
Download the file
Put the following code in CMD/Terminal:
Code:
fastboot flash recovery twrp-3.1.1-kugo-*.img
//Replace * with the version you want to flash
Unplug the cable
Press Volume Down + Power to activate the recovery. When installed properly, the device should vibrate funnily, purple LED should appear and after a couple of seconds, you should see the TWRP screen.
Enjoy!
BUILD
You need to sync the OmniROM and vendor blobs from DonkeyCoyote. You can find my sources on GitHub.
android_device_sony_loire_common
https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Thanks:
@grayleshy - for initial TWRP
@AndroPlus for some of his flags
OmniROM team for sources
If you find my work useful, consider buying me a cup of coffee

it works perfectly! well can't say I tried all functions yet, but it certainly seems so.
thank you so much. finally a proper lastest version of twrp for XC that supports encryption on nougat.
btw. you have to flash it over fotakernel as described in OP. (hotbooting did not work. blank screen.)
I did try other regular X twrp versions with the same result in the past in hopes of finding something better, so the issue was likely the same since I hotbooted them too for a fast test. I guess that's what you get for being lazy. doh.
thanks again for posting it here.
/tuxen

Thank you for sharing.

thanks
Thanks for sharing brother
Working ⚒ perfectly on stock 7.0
no problem

Perfect, thanks. Only annoyance is that I can only reboot the system or power off now.

XperienceD said:
Perfect, thanks. Only annoyance is that I can only reboot the system or power off now.
Click to expand...
Click to collapse
That shouldn't work anyway. I can enable these flags if you want.

eagleeyetom said:
That shouldn't work anyway. I can enable these flags if you want.
Click to expand...
Click to collapse
For all I use the other options there's no need to go out of your way, but if you do make another for whatever reason having the options would be nice.

XperienceD said:
For all I use the other options there's no need to go out of your way, but if you do make another for whatever reason having the options would be nice.
Click to expand...
Click to collapse
It didn't work for me on X. I can enable them in the next version.

realtuxen said:
it works perfectly! well can't say I tried all functions yet, but it certainly seems so.
thank you so much. finally a proper lastest version of twrp for XC that supports encryption on nougat.
btw. you have to flash it over fotakernel as described in OP. (hotbooting did not work. blank screen.)
I did try other regular X twrp versions with the same result in the past in hopes of finding something better, so the issue was likely the same since I hotbooted them too for a fast test. I guess that's what you get for being lazy. doh.
thanks again for posting it here.
/tuxen
Click to expand...
Click to collapse
What do you mean by hot booting? I did this to boot to twrp without installing and have no problem
Code:
fastboot boot twrp.img
Thanks for the twrp, with this I can make full backup before trying to update to 7.1 or 8.0 later :good:

MTP is not working in this version. Everything else is top notch, will test backup/restore a bit later and report back.

trewelu said:
What do you mean by hot booting? I did this to boot to twrp without installing and have no problem
Code:
fastboot boot twrp.img
Thanks for the twrp, with this I can make full backup before trying to update to 7.1 or 8.0 later :good:
Click to expand...
Click to collapse
Exactly. I know hotbooting is not the best description, but you understood anyway.
Strange, I am not a flashophile so I usually just booted twrp this way after a upgrade with flashtool. When the phone was connected to the pc anyway.
But it only works for me with the androplus version, oshmoun's version won't boot that way either. It's not the first time I have talked odd twrp behaviour though, as another guy could not get the androplus one to work at all. I have no reason to doubt him, as this is pretty casual stuff.
I see you are still on MM, I have been on N since it came out and if I remember correctly I backed up ta just before N came out (exploit and N came out very close to each other), took the ota, and unlocked BL. So I performed all the 'fastboots' (better word? heh) on that and 7.1.1. Perhaps the bootloader changed someway? I have no idea.
Edit: if I learned to read properly the first time, you are NOT on MM (doh) but 7.0. Sorry and even more strange. Does MTP work for you? (see below)
---------- Post added at 20:00 ---------- Previous post was at 19:58 ----------
kekistaneerefugee said:
MTP is not working in this version. Everything else is top notch, will test backup/restore a bit later and report back.
Click to expand...
Click to collapse
MTP works absolutely fine here..

This version uses Sony init, so you can see the Sony screen and led indicator while entering the recovery mode. I'm not planning to change it before creating an official TWRP.

eagleeyetom said:
This version uses Sony init, so you can see the Sony screen and led indicator while entering the recovery mode. I'm not planning to change it before creating an official TWRP.
Click to expand...
Click to collapse
Is this in response to something functional, or just general cosmetics info? Doesn't the sony screen origin from the bootloader? How should a official twrp look while booting it? I get the sony boot and led then the TWRP boot image, isn't that normal when booting fotakernel replaced by TWRP? ie. the bootloader handles it when turning the phone on while holding vol down.
An official version would sure be nice. I more than appreciate what you already done. So just take your time.

realtuxen said:
But it only works for me with the androplus version, oshmoun's version won't boot that way either. It's not the first time I have talked odd twrp behaviour though, as another guy could not get the androplus one to work at all. I have no reason to doubt him, as this is pretty casual stuff.
Edit: if I learned to read properly the first time, you are NOT on MM (doh) but 7.0. Sorry and even more strange. Does MTP work for you? (see below)
Click to expand...
Click to collapse
Strange, I don't have problem booting twrp without installing for either of twrp.
I'm on 7.0. I tried to update to 7.1, but I don't get signal if I do the ta_poc + tobias drm fix method, and the drm is still marked as broken.
I really hate mtp and avoid it. I don't think I even have mtp working properly on my pc. I can't help you test that one. Sorry.

trewelu said:
Strange, I don't have problem booting twrp without installing for either of twrp.
I'm on 7.0. I tried to update to 7.1, but I don't get signal if I do the ta_poc + tobias drm fix method, and the drm is still marked as broken.
Click to expand...
Click to collapse
Why are you running it through both ta_poc and Tobias rootkernel with drm fix?
Either you use ta_poc to mount your ta backup from before the bootloader was unlocked thereby bringing the whole trim area back including drm.
Or you use Tobias rootkernel to fix or 'emulate" drm.
Both tools can disable dm verity, sony ric, etc. there is no reason (other than likely creating trouble) to run the kernel image though both tools?!
If you for example run a boot.img with drm fix through ta_poc it will remove the drm fix first. So I imagine things could go wrong of you apply drm fix again (if that is what you're doing) after using ta_poc.
I really hate mtp and avoid it. I don't think I even have mtp working properly on my pc. I can't help you test that one. Sorry.
Click to expand...
Click to collapse
Lol I hate it general too, it can come in handy when only twrp is booted though. I am not sure I have any drivers installed either. Regardless I can access a drive resembling my phone labeled 'mtp device' in 'my computer' when I boot twrp.
Edit: sorry for sidetracking the thread a bit.

eagleeyetom said:
NEEDS TESTING
USB-OTG
Click to expand...
Click to collapse
Thanks! and i can confirm that USB OTG works well.

Working on Sony Nougat
This is the only TWRP I can decrypt my data with on Sony Nougat Stock ROM, Thanks !

realtuxen said:
Both tools can disable dm verity, sony ric, etc. there is no reason (other than likely creating trouble) to run the kernel image though both tools?!
Click to expand...
Click to collapse
Using both tools stems from users reporting they had to to get Magisk to work.

XperienceD said:
Using both tools stems from users reporting they had to to get Magisk to work.
Click to expand...
Click to collapse
There was an info in one of threads, that you should get the stock kernel first through TA_POC and then through kernel repack tool. If you did not, it would work, but occassionally reboots. I am now on 7.1.1 build 206 with Genesis Kernel 1.05 (no_DRM patch version) and it works ok.
As for TWRP, thanks for this! It works ok. Can not fastboot it, must be flashed in recovery parition, but no deal for me. Only thing that I wonder, there are options to backup system, data etc, but not Internal SD (/data/data). Why?

Hi I have a question, I have N 7.1.1, and i want to root it, so i need the twrp, if I flash this twrp, its okay? Ty!

Unable to install OTA updates since unlocking bootloader

Hello everyone!
Since I've unlocked and rooted my Pixel 2 it keeps failing the OTA update. I get the notification and the update is downloaded but when it's being installed, there is an undefined error. For all updates I had to sideload the OTA file via ADB. Honestly, I don't really know what could have caused this issue, as the first OTA update when I got the phone with all stock settings and roms it worked fine. Currently I can only instal the OTA.zip updates via ADB.
Things I did so far which could have caused the issue:
flash boot.img via fastboot (Magisk Root)
unlock bootloader via fastboot
Things I tried to resolve the issue:
Lock the bootloader again
Flash full stock rom with fastboot and official google script (failed "couldn't write bootloader.img" altough I had it unlocked)
Factory reset
Also, everytime I reboot my phone i get the message that something is wrong with my phone and I should check it with my vedor. But everything is working perfectly - except for the updates.
Does anyone else have similar experiences?

ekalz said:
Things I did so far which could have caused the issue:[/B]
flash boot.img via fastboot (Magisk Root)
unlock bootloader via fastboot
Click to expand...
Click to collapse
My understanding is that anytime you modify the file system, etc (rooting patches some files) then it will fail the integrity check and not OTA.
ekalz said:
Also, everytime I reboot my phone i get the message that something is wrong with my phone and I should check it with my vedor. But everything is working perfectly - except for the updates.
?
Click to expand...
Click to collapse
Yes! I have that exact same message when I reboot. I flashed TWRP, rooted with Magisk Manager. I can't tell any negative concequences either.

SweetSofie said:
My understanding is that anytime you modify the file system, etc (rooting patches some files) then it will fail the integrity check and not OTA.
Yes! I have that exact same message when I reboot. I flashed TWRP, rooted with Magisk Manager. I can't tell any negative concequences either.
Click to expand...
Click to collapse
The error you see about system integrity (or whatever it is ) when you boot the phone is due to Magisk patching the dtbo partition. It's a bug and will most likely get fixed eventually. It's nothing to be concerned about though. You can safely ignore it.

Can you root without patching or unlocking the bootloader so you don't fail the integrity check?

robocuff said:
The error you see about system integrity (or whatever it is ) when you boot the phone is due to Magisk patching the dtbo partition. It's a bug and will most likely get fixed eventually. It's nothing to be concerned about though. You can safely ignore it.
Click to expand...
Click to collapse
Thanks for the clarification! I would love to learn more about that stuff, I'm just not sure where to start learning.

I have the same problem with my pixel 2. I have tried full factory reset by flashing stock image. I have tried the recovery script some user posted in the p2 forum.
I contacted Google support about it and now i am waiting for 2nd line to contact me.
I will post here if/when i get a solution.

With an unlocked bootloader, you will not be able to update via Android; you must sideload. However, sideload will fail if you do not have the factory boot and dtbo.
So, assuming you are rooted:
0. You must start with factory boot and dtbo images; if you are running custom, download the factory image that corresponds to your build, unpack and flash boot and dtbo
1. Download the latest ota.zip from the Google Developers website
2. Connect phone to computer, use ADB to reboot into bootloader
3. Once in bootloader, hit Power + Vol Up to bring up menu, use volume buttons to scroll to Apply update via ADB
4. Use ADB to sideload:
Code:
adb sideload update.zip
5. Select Reboot System in recovery when complete

socal87 said:
With an unlocked bootloader, you will not be able to update via Android; you must sideload. However, sideload will fail if you do not have the factory boot and dtbo.
So, assuming you are rooted:
0. You must start with factory boot and dtbo images; if you are running custom, download the factory image that corresponds to your build, unpack and flash boot and dtbo
1. Download the latest ota.zip from the Google Developers website
2. Connect phone to computer, use ADB to reboot into bootloader
3. Once in bootloader, hit Power + Vol Up to bring up menu, use volume buttons to scroll to Apply update via ADB
4. Use ADB to sideload:
Code:
adb sideload update.zip
5. Select Reboot System in recovery when complete
Click to expand...
Click to collapse
That would explain a lot but are you sure its the unlocked bl that causes this problem? Google support told me it should not matter. Would it work with ota if i lock the bl again?

smorgar said:
That would explain a lot but are you sure its the unlocked bl that causes this problem? Google support told me it should not matter. Would it work with ota if i lock the bl again?
Click to expand...
Click to collapse
I am not certain, but with unlocked bootloader and stock kernel, the OTA still failed to install within system. I was able to sideload it, but the kernel had to be stock.
I just posted a guide how to get around this by using the factory image, as it does not appear to perform signature checks.
Thread

socal87 said:
I am not certain, but with unlocked bootloader and stock kernel, the OTA still failed to install within system. I was able to sideload it, but the kernel had to be stock.
I just posted a guide how to get around this by using the factory image, as it does not appear to perform signature checks.
Thread
Click to expand...
Click to collapse
I tried relocking BL and proceeded to install OTA but same error presists. (OTA: Feb patch -> Mar patch)

smorgar said:
I tried relocking BL and proceeded to install OTA but same error presists. (OTA: Feb patch -> Mar patch)
Click to expand...
Click to collapse
Did you try to sideload via ADB?

socal87 said:
Did you try to sideload via ADB?
Click to expand...
Click to collapse
No I am waiting to get it resolved by Google so that I can install OTA in the future.

smorgar said:
No I am waiting to get it resolved by Google so that I can install OTA in the future.
Click to expand...
Click to collapse
Why don't you try sideloading the OTA? It worked for me. As for the future, you might not able to take OTAs without a completely stock image, but if you're just trying to get the March security update, either sideload the OTA, or flash the stock system image from the most recent factory ROM as described in my thread.

socal87 said:
Why don't you try sideloading the OTA? It worked for me. As for the future, you might not able to take OTAs without a completely stock image, but if you're just trying to get the March security update, either sideload the OTA, or flash the stock system image from the most recent factory ROM as described in my thread.
Click to expand...
Click to collapse
I was trying to fix the problem permanently so that i dont have to sideload if i dont want to.
**** went to ****... I did factory reset as the Google support person told me. Tried installing OTA again but it did not work. So they left me waiting for second line support to contact me but its now been the whole weekend and no support.
After support told me to do reset the last time the phone began to freeze and crash apps randomly. So i tried to install full factory image via fastboot but that was the last time the phone booted up. Now its completely dead.
When i try to boot the phone nothing happens. If i hold power button for 20-30 sec i sometimes get a short vibration and a line of pixels flashing by on the screen then nothing more happens. Now im waiting for Google support for real. Pray for my dead pixel2
If anyone have some tips for me im willing to try. The phone does not seem to boot and the PC does not recognize it at all.

You'll need to go into fastboot mode. Download the latest factory image and unzip. You'll find a flash all batch file to run in Windows. It will then do its magic. Remove the "-w" parameter at the end of it so that it doesn't wipe your system. You can always manually factory reset. That parameter has been known to have issues.

davidisflash said:
You'll need to go into fastboot mode. Download the latest factory image and unzip. You'll find a flash all batch file to run in Windows. It will then do its magic. Remove the "-w" parameter at the end of it so that it doesn't wipe your system. You can always manually factory reset. That parameter has been known to have issues.
Click to expand...
Click to collapse
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant

smorgar said:
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant
Click to expand...
Click to collapse
And so how did everything work out for you? Were they able to get you resolved, or are they just RMA'ing your phone?

No resolution. I sent it back to uk for replacement via seller.

smorgar said:
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant
Click to expand...
Click to collapse
How are you trying to turn on the phone? What about it just holding the power button for like 30 seconds, releasing, then again but this time holding power button AND volume down? Is the battery charged?
There are two separate drivers for Windows. When the phone is in fastboot mode, you'll need to use the separate adb / fastboot drivers. In fact in device manager, this will appear as a separate device (that's because the device will register under a different device ID).
The main Windows driver is here:
https://developer.android.com/studio/run/win-usb.html
The adb driver is here:
Good page I used to debug it not being recognized:
https://forum.xda-developers.com/pixel-2-xl/help/device-recognized-adb-fastboot-t3698716

davidisflash said:
How are you trying to turn on the phone? What about it just holding the power button for like 30 seconds, releasing, then again but this time holding power button AND volume down? Is the battery charged?
There are two separate drivers for Windows. When the phone is in fastboot mode, you'll need to use the separate adb / fastboot drivers. In fact in device manager, this will appear as a separate device (that's because the device will register under a different device ID).
The main Windows driver is here:
https://developer.android.com/studio/run/win-usb.html
The adb driver is here:
Good page I used to debug it not being recognized:
https://forum.xda-developers.com/pixel-2-xl/help/device-recognized-adb-fastboot-t3698716
Click to expand...
Click to collapse
I have done all the basic and advanced stuff. I had it dead for about a week to play around with. Used to work in a mobile repair shop so this isnt something new for me.

[GUIDE] How to Flash the Pixel Experience ROM on Nokia 7 Plus & Nokia 7

Hey guys i know the Pixel Experience rom has been released for a long time, more information about this Pixel Experience rom https://forum.xda-developers.com/project-treble/trebleenabled-device-development/8-1-0-pixel-experience-t3796011
but unfortunately we could not boot on nokia devices after we flashed this rom
Congratulations that bootloop problem has been solved right now, we are not tired to flash roms
DOWNLOAD TWRP https://drive.google.com/open?id=1-e7zNrXp_mi468h-Zu1X5gbwQtgE17I6
follow these steps
1: unlock your bootloader
thank for @hikari_calyx
2: erase data/factory reset
3: connect your computer with adb and flash any roms based on project preble ( AOSP or RR )(why this step ? my friend told me that this twrp has a bug which can't boot recovery on official firmware)
Code:
fastboot flash system system.img
4: flash this TWRP supported project treble with
Code:
fastboot flash boot_a TWRP.img
Code:
fastboot flash boot_b TWRP.img
5: boot into the twrp
6: extract rom image from PE zip and download Magisk-v16.6.zip, after that move them to Internal Storage
7: format data and flash the Pixel Experience image, choose "System image" Notice: Don't do a reboot before flash Magisk.zip
8: flash the magisk.zip
9: wipe all data and reboot. Done !
Notice: you may see Your Device Is Uncertified when you intend to login Google on this device
Just Do This
Download and install Device ID.apk
copy your Google Service Framework ID
fill your GSF ID on this web and Clink on REGISTER
reboot some times you will be able to use google apps
btw all project treble roms do not include Adaptive brightness and Ambient display
fix them at here https://forum.xda-developers.com/project-treble/trebleenabled-device-development/overlay-enable-night-light-adaptive-t3741965
I'm on this rom for three days and every things go fine unless fingerprint control bug (that means you can control your phone easily with fingerprint)
thanks for viewing, sorry for my english is poor but I've been improving it, I wrote this GUIDE without translate tool
thanks for every member which develop the project treble rom and TWRP and something else

some amazing screenshots

The image does not load

12345wxj said:
The image does not load
Click to expand...
Click to collapse
什么？哪一个镜像不加载？

1452686579 said:
什么？哪一个镜像不加载？
Click to expand...
Click to collapse
我這邊圖片一個都加載不出來

I have a Little problem at step one ._.
No way to unlock BL?

Why is the TWRP upload locked behind a google drive link that you need to request access for?

pitt93 said:
I have a Little problem at step one ._.
No way to unlock BL?
Click to expand...
Click to collapse
there is a way. but you need to pay.

donjamal said:
there is a way. but you need to pay.
Click to expand...
Click to collapse
Do they accept ETH/BTC?

shubham412302 said:
Do they accept ETH/BTC?
Click to expand...
Click to collapse
i have no idea. i don't think so, you need to ask them. it's 5 dollars, they for sure accept paypal

Has anyone flashed this yet? This thread was the straw that broke the camel's back for me and I unlocked my bootloader today.
Now just waiting to hear if anyone other than the op has been successful with this guide.

Doktaphex said:
Why is the TWRP upload locked behind a google drive link that you need to request access for?
Click to expand...
Click to collapse
I don't know why. ? Maybe it is shared right now

Doktaphex said:
Has anyone flashed this yet? This thread was the straw that broke the camel's back for me and I unlocked my bootloader today.
Now just waiting to hear if anyone other than the op has been successful with this guide.
Click to expand...
Click to collapse
Trust me dude ,it works fine I and my Chinese friends tested this guide on Nokia 7 plus and Nokia 7
And there is anotber guide to flash pixel experience rom, but that mode is complex and sometimes does not work

1452686579 said:
Trust me dude ,it works fine I and my Chinese friends tested this guide on Nokia 7 plus and Nokia 7
And there is anotber guide to flash pixel experience rom, but that mode is complex and sometimes does not work
Click to expand...
Click to collapse
It might take me a couple of days as I am quite busy at the moment.

Thank you for your development for the Nokia 7 plus. Really appreciated.

Well, I installed the system image, but now my SIM is not recognized.
I will go through setup and see if the SIM works afterwards?
EDIT: No IMEI on SIM slot 1, there is an IMEI on slot 2 but this slot also does not work.
And of course, I did not do a backup of my working system. (You'd think I would have learned by now, but NO )

Doktaphex said:
Well, I installed the system image, but now my SIM is not recognized.
I will go through setup and see if the SIM works afterwards?
EDIT: No IMEI on SIM slot 1, there is an IMEI on slot 2 but this slot also does not work.
And of course, I did not do a backup of my working system. (You'd think I would have learned by now, but NO )
Click to expand...
Click to collapse
LOL always do backup man, i learned the hard way Please update if you got sim 1 to work!

sublimeace said:
LOL always do backup man, i learned the hard way Please update if you got sim 1 to work!
Click to expand...
Click to collapse
I got my entire system back up and running using the July patched boot image flashed into boot a and b and then sideloaded rollback zip etc, etc....
In general I have found that when I get my self into these situations, if I actually have a back up it ends up failing anyway.
It's always more fun walking the tightrope.
Anyway, both SIM slots are fine on stock ROM rooted with magisk, xposed etc.
I won't be flashing any treble images until I hear more success stories in that respect, I feel that our twrp still has some kinks that need to be ironed out.

9: wipe all data and reboot. Done ! you mean factory reset?

donjamal said:
there is a way. but you need to pay.
Click to expand...
Click to collapse
so, no way

FIX WIFI not connecting/ MAC ADDRESS 02:00:00:00:00:00/

FIX WIFI not connecting/ MAC ADDRESS 02:00:00:00:00:00 / bluetooth / calibration sensor / drivers missing from phone/ wlan mac and ip unavailable..
There is the FIX:
1. Download your stock firmware android
2. Flash OrangeFox recovery for your phone
3. In your stock firmware folder find file persist.img
4. Put persist.img in your phone and flash it with OrangeFox recovery..image option not zip..check persist-image option and flash it
5. Restart your phone
That's it, enjoy your fix

thank you, buddy, you really saved me you are a fkn hero

fawzy ahmed said:
thank you, buddy, you really saved me you are a fkn hero
Click to expand...
Click to collapse
I'm glad i could help you :good:

i tried on mine ( xiaomi mi 8 ) didn't help

malesh said:
FIX WIFI not connecting/ MAC ADDRESS 02:00:00:00:00:00 / bluetooth / calibration sensor / drivers missing from phone/ wlan mac and ip unavailable..
There is the FIX:
1. Download your stock firmware android
2. Flash OrangeFox recovery for your phone
3. In your stock firmware folder find file persist.img
4. Put persist.img in your phone and flash it with OrangeFox recovery..image option not zip..check persist-image option and flash it
5. Restart your phone
That's it, enjoy your fix
Click to expand...
Click to collapse
the problem is, i cannot find any persist.img in the firmware folder i installed (50.1.A.4.76_R1A)

malesh said:
FIX WIFI not connecting/ MAC ADDRESS 02:00:00:00:00:00 / bluetooth / calibration sensor / drivers missing from phone/ wlan mac and ip unavailable..
There is the FIX:
1. Download your stock firmware android
2. Flash OrangeFox recovery for your phone
3. In your stock firmware folder find file persist.img
4. Put persist.img in your phone and flash it with OrangeFox recovery..image option not zip..check persist-image option and flash it
5. Restart your phone
That's it, enjoy your fix
Click to expand...
Click to collapse
didn't help bro, i used twrp recovery to flash persist img

Chouiyekh said:
didn't help bro, i used twrp recovery to flash persist img
Click to expand...
Click to collapse
and you found persist.img just in the folder of the firmware, or on the phone, after you flashed it, ot where?

layalala said:
and you found persist.img just in the folder of the firmware, or on the phone, after you flashed it, ot where?
Click to expand...
Click to collapse
I'll tell what i did, i downloaded the last global version and flash it to phone using miflash tool, then i flash twrp and take persist.img from the firmware ( last global version) and put it on phone memory, then flash it using twrp, but the problem still exist

Chouiyekh said:
I'll tell what i did, i downloaded the last global version and flash it to phone using miflash tool, then i flash twrp and take persist.img from the firmware ( last global version) and put it on phone memory, then flash it using twrp, but the problem still exist
Click to expand...
Click to collapse
ok, i don't even found persist.img
try that, i will try that later
https://forum.xda-developers.com/showpost.php?p=79378001&postcount=121

layalala said:
ok, i don't even found persist.img
try that, i will try that later
https://forum.xda-developers.com/showpost.php?p=79378001&postcount=121
Click to expand...
Click to collapse
It will definitely be safer to post your issue on your device forum
These generic 'fixes' will not work for every phone and may even result in your phone being soft bricked or hard bricked.

what does soft bricked and hard bricked mean, please ?
https://shareit.onl/ https://mxplayer.pro/

beyonslay said:
what does soft bricked and hard bricked mean, please ?
Click to expand...
Click to collapse
Where your phone becomes:
1. Useless due to software issues = soft brick but can be fixed
2. Useless due to major hardware failure = hard brick and very difficult to fix or completely dead
The term "brick" is exactly as you'd think - literally like stone

hello,
These two are the most vulnerable things that can happen to an android device.
SOFT-BRICKING:
When your fone gets soft-bricked, it means that the operating system you were going to install has not been installed properly.
Some of the reasons may be :
1. ROM not compatible with your device.
2. Phones battery going down in the middle of a OTA or normal update
3. ROM not properly installed in your device.
The most common things one can observe in a soft bricked fone is BOOT-LOOP
it means your fone boots up, and gets stuck in booting mode.
Assume you own a SONY device , if your fone is stuck in boot loop then, the SONY logo will show up on the screen for some time and the the fone will automatically turn off and after some time it will turn on again repeating the same process.
HARD-BRICKING:
It generally means all the data in your fone is wiped out. This just dosent mean the operating system but also the system used to load the operating system, also called as recovery. Therefore, you will have no way to install your custom OS or ROM. This generally happens when you try flasing ROMS in a mobile device that has a weak recovery system.
One of my friends tried to flash custom ROM in Yu-Yureka and ended up hard-bricking the fone.
If you softbrick a mobile device, you can have the liberty of using softwares like flashing tools to install ROMs and Recoverys and make your fone work.
If you ended up hard-bricking your device, the mobile even wont respond to any physical holding or tapping of the buttons on your phone and all that can be done is getting a good fast wifi connection to do a strong research for your next mobile.
i hope this is helpful for you.

Chouiyekh said:
i tried on mine ( xiaomi mi 8 ) didn't help
Click to expand...
Click to collapse
I have same problem like you.
If you solved it, can you tell me how?

Anyone ever solve this ?

malesh said:
FIX WIFI not connecting/ MAC ADDRESS 02:00:00:00:00:00 / bluetooth / calibration sensor / drivers missing from phone/ wlan mac and ip unavailable..
There is the FIX:
1. Download your stock firmware android
2. Flash OrangeFox recovery for your phone
3. In your stock firmware folder find file persist.img
4. Put persist.img in your phone and flash it with OrangeFox recovery..image option not zip..check persist-image option and flash it
5. Restart your phone
That's it, enjoy your fix
Click to expand...
Click to collapse
I tried this way, but I can't fix it.
greeneyez15o said:
Anyone ever solve this ?
[/QUO
Click to expand...
Click to collapse

I was having this problem for at least 1 month. Tried everything that is posted in xda forums. Gave up and was using cellular connection, Until I found your post and gave it a shot. Now, my wifi is back to normal , Many thanks to you. You are truly a lifesaver.
I also tried this method before, but it didn't work. Before I was using TWRP recovery. But after flashing with OrangeFox my wifi was fixed.

Edit MAC

Hello! I have a Lenovo Xiaoxin Pad M10 Plus but wifi is not turning on.
There's no MAC address on the wifi interface, but bluetooth is working.
I flashed the original ZUI_13.5.365_ST_220526, TWRP and Magisk.
I'm trying to find a way to hardcode a new MAC address to the wifi card.
Or maybe the persist or modem partitions were bricked by the previous owner?
I was thinking if I flash these partitions from a working device I can get the wifi to work again?
Can someone help me please. Thanks!

can anyone help me root my samsung Galaxy a20e

Hi could anyone give me instructions on how to root my samsung Galaxy a20e please

Wazzer21 said:
Hi could anyone give me instructions on how to root my samsung Galaxy a20e please
Click to expand...
Click to collapse
This might help. https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root

Spaceminer said:
This might help. https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Click to expand...
Click to collapse
The third step is doesnt work for me. (Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.)

triumfanto said:
The third step is doesnt work for me. (Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.)
Click to expand...
Click to collapse
You might not have an unlockable bootloader, or it might just be a different key combo. If you got one that was already carrier branded by Verizon or At&t then you're probably out of luck. You might want to try reading this too. (The middle response.) This is how the regular A20 users are unlocking theirs.

Spaceminer said:
You might not have an unlockable bootloader, or it might just be a different key combo. If you got one that was already carrier branded by Verizon or At&t then you're probably out of luck. You might want to try reading this too. (The middle response.) This is how the regular A20 users are unlocking theirs.
Click to expand...
Click to collapse
Thanks! Linked method works for me.
(1 turn off phone
2 Hold down Volume Up and Volume down both at same time.
3 While holding down both those buttons attach USB cable to computer (easier if you already have it plugged in to the phone)
4 wait for Aqua screen to come up that says to long press (hold down several seconds ) the Volume UP key to unlock bootloader.)
Maybe the root with magisk is possible too.
After few hours later I have a rooted a20e phone! (A202FXXU2ASG1)
When bootloader is really open odin can rewrite original boot.img with the magisk patched one.
TWRP is only need for me now.

triumfanto said:
Thanks! Linked method works for me.
(1 turn off phone
2 Hold down Volume Up and Volume down both at same time.
3 While holding down both those buttons attach USB cable to computer (easier if you already have it plugged in to the phone)
4 wait for Aqua screen to come up that says to long press (hold down several seconds ) the Volume UP key to unlock bootloader.)
Maybe the root with magisk is possible too.
Click to expand...
Click to collapse
I love hearing good news! I'm willing to bet that whatever they're doing to get root will also work for you too. You'll have to do a little digging over there. You also have the same chipset as them and they have twrp already! It should be portable to your device without much of an issue. It really sounds like anyone with an A series can rejoice. I'm tempted to get one myself at this point.

Flash failed
Hello,
I have also a Samsung galaxy a20e and I followed the instructions, but the flash at step 7 fails. The firmware that I used is provided by this sammobile. It's works when I use it normaly, but fails when I use the magisk generated file for the AP . The operation stop when Odin reading the recovery image.
I uncheck the Auto Reboot option like specified
Can someone help me please?

Have a look at this:
https://unofficialtwrp.com/galaxy-a20e-sm-a202fd-root-twrp/
this is what i am trying now, seems to be working to get TWRP and root in one go
(You May also need this: https://www.youtube.com/watch?v=mF2Nxck4FtM
because when i tried this the OEM Unlocking option in Developer Options was missing, follow the instructions in this link, get the OEM Unlock Enabled then follow the first link)

The OEM unlocking option was already active for me. Unfortunately the flash with TWRP that you give still doesn't work. Have you succeed on your side ?

smda said:
The OEM unlocking option was already active for me. Unfortunately the flash with TWRP that you give still doesn't work. Have you succeed on your side ?
Click to expand...
Click to collapse
Hi,
No I am still having the same issue as you, OEM Unlocked, but the flash at step 7 fails. The firmware that I used is provided by this sammobile. It's works when I use it normally, but fails when I use the magisk generated file for the AP.
It says "Can only flash official images"

1. extract the boot.img from the firmware of your device
2. unzip with zarchiver
3. download magisk manager and choose install then select the boot.img file
4. flash the patched boot.img in Odin
Done
there is no TWRP yet cause it would need to be build from source.

triumfanto said:
Thanks! Linked method works for me.
(1 turn off phone
2 Hold down Volume Up and Volume down both at same time.
3 While holding down both those buttons attach USB cable to computer (easier if you already have it plugged in to the phone)
4 wait for Aqua screen to come up that says to long press (hold down several seconds ) the Volume UP key to unlock bootloader.)
Maybe the root with magisk is possible too.
After few hours later I have a rooted a20e phone! (A202FXXU2ASG1)
When bootloader is really open odin can rewrite original boot.img with the magisk patched one.
TWRP is only need for me now.
Click to expand...
Click to collapse
Can you post the files for root? matching the AP via magisk doesnt work, Kingroot doesnt work, I have tried everything, please cam someone help me get this phone rooted!!! the phone is useless as it is as i need titanium backup to work!!!

ParadoxLogic said:
Can you post the files for root? matching the AP via magisk doesnt work, Kingroot doesnt work, I have tried everything, please cam someone help me get this phone rooted!!! the phone is useless as it is as i need titanium backup to work!!!
Click to expand...
Click to collapse
I have the same problem please help to root and put my hand I have tried to do things has this mobile to see if we give a little life thanks

Hello,
Sorry for chiming in, but maybe there is a misunderstanding? The original boot.img file (extracted from the stock firmware) needs to be first patched by the Magisk app. Only after it has been patched, the boot.img file should be flashed by Odin. Maybe the guide over there helps to make it clearer: https://www.getdroidtips.com/root-galaxy-a20-a20e/
EDIT1: I see posts about "vbmeta warning", so there might be some further hurdles, see e.g. there:
https://forum.xda-developers.com/galaxy-a20/help/root-method-twrp-samsung-a20e-help-t4017763
EDIT2: You might also want to have a look into the A20 (i.e. without the "e") section:
https://forum.xda-developers.com/showpost.php?p=80021195&postcount=4
EDIT3: vbmeta.tar attached there:
https://forum.xda-developers.com/showpost.php?p=80188834&postcount=237
Good luck!
PS:
I understood that no TWRP or other custom recovery was needed for this, but I assume that by unlocking the bootloader via the developer options (before flashing) or/and by flashing the patched boot.img (and vbmeta.tar?) file via Odin, the Knox counter is triggered, voiding warranty and some apps not working anymore (e.g. Samsung billing etc.), and OTA updates by Samsung not working anymore. Is that correct?

This thread was started by @Wazzer21. Actually, his first post so far remains the only one. And interestingly, I found this website:
https://www.androidinfotech.com/root-samsung-galaxy-a20e-pie/
...
How to Root Samsung Galaxy A20e Pie 9.0 (SM-A202F, SM-A202K)
First of all, thanks to Wazzer21 – XDA developer for TWRP support and topjohnwu – this genius is a one who discovered and maintaining Magisk. Samsung Galaxy A20e International variants come with a flexible bootloader.
...
Click to expand...
Click to collapse
Er, what does this mean?
When you read further through that page and come to the comments, you learn:
Chris says December 1, 2019 at 3:32 am
This does not work…..at all…
once completing, there is an error VBMETA error…..
Click to expand...
Click to collapse
Selva Ganesh says December 1, 2019 at 11:53 am
The problem is Magisk 20.0. Did you use that Magisk version? If so, Try with Patch version 20.1.
Click to expand...
Click to collapse
Can somebody please confirm this? Or is this all a hoax? Sorry for asking so bluntly, but I have mixed feelings (and still do not want to appear rude or something).
PS:
On this website about rooting the Samsung A20e ("SM-A202")...
https://www.flashfilebd.com/2019/07/samsung-a20-root-file.html
... there are several files for download and the following info:
...
Here You Find Samsung A20e Root File With Magisk Manager Apk. Samsung SM-A202/F/FN/S/K Binary U1 And U2 Root File Available Here.
...
Click to expand...
Click to collapse
What do "U1" and "U2" binaries mean, i.e. how do they differ? There is no explanation (unless I have missed something).

According to some hints from @physwizz in the A20 forum, the root methods described for the A20 also work for the A20e as pointed out in several posts there.
However, currently neither TWRP nor custom kernel seem yet to be available/working for the A20e.

triumfanto said:
Thanks! Linked method works for me.
(1 turn off phone
2 Hold down Volume Up and Volume down both at same time.
3 While holding down both those buttons attach USB cable to computer (easier if you already have it plugged in to the phone)
4 wait for Aqua screen to come up that says to long press (hold down several seconds ) the Volume UP key to unlock bootloader.)
Maybe the root with magisk is possible too.
After few hours later I have a rooted a20e phone! (A202FXXU2ASG1)
When bootloader is really open odin can rewrite original boot.img with the magisk patched one.
TWRP is only need for me now.
Click to expand...
Click to collapse
Hello, i read that you have root your phone, i am trying to do the same thing now but i don't know how please can you give me the process that you followed

I'm curious if at least the 20e version can be rooted, thank you all

ninowebs said:
I'm curious if at least the 20e version can be rooted, thank you all
Click to expand...
Click to collapse
Yes it can be rooted, just install TWRP, then dowbload magisk and flash it in TWRP.

which TPWR?