No Wi-Fi MAC adress. - Xiaomi Mi 5 Questions & Answers

I have a problem. My mi5 told me: An error occured with Google Services. So i rebooted the phone. It booted just OK. But I've seen that wifi doesn't work and the phone always reboot after 2-3 minutes. I've seen that the wi-fi MAC-adress is 02:00:00:00:00:00.
So i've tried to flash different firmwares using twrp and miflash. But there is still no MAC. How to change it and make my phone work?

if you dont have a backup of efs and efs2 partitions using twrp 1.0.3-2 or later then youre screwed...
youll have to get qualcomm diagnostic tool and manually input your original mac address to get it working again.. you can find some posts about it on miui forums

You should flash the fastboot ROM via MiFlash tool and while you will flash, you should also select the clear internal storage option or something like that. This will cause to delete all your files, applications, photos or etc. So be aware of this, firstly backup your files and apps and then flash the fastboot ROM. Your problem will be solved.

Related

Bricked mate s

PLEASE help : My phone stopped working after trying to change it to a L09 and now is dependent on the company's logo and does not accept any Software
You need to read about flashing from the bootloader using fastboot. You will be able to get it back working but you will need to get an extracted rom to flash the right parts.
Now I have a bit of time, I will tell you how I solved my issues. My phone was stuck with only the bootloader screen available or the eRecovery screen which would not find any suitable download. It said that the bootloader was unlocked yet I could not flash anything that I have extracted using the ROM extractor.
After much frustration I opened and ADB session and used Fastboot commands and re-entered the number in the Fastboot OEM Unlock command and it then confirmed that it was actually unlocked. It seems that although it said it was, it really wasn't.
Now that I knew it was unlocked, I could now start to flash parts of the extracted ROM.
I used the Huawei Rom Extractor tool to extract the Boot, Cache, Cust, Recovery, System and the Userdata image files of the ROM I needed and in this case it was the CRR-UL00470B110. I renamed the extracted files and removed the prefix numbers and put them in the ADB folder for ease of flashing.
I then used the Fastboot command to flash each part in the normal Fastboot format i.e. - Fastboot flash system system.img , and so on for each part. A reboot after brings it up in a nice new live usable phone. Well that is what I thought until I started to load the apps back on. I then noticed that I only had about 3gb left of my 64gb of memory! This took me a while to resolve and after more reading, more flashing of different ROMs I found the answer.
I had to flash the TWRP recovery using Fastboot, then format the data partition from TWRP. This restored the full size of the partition. Another flash of the correct recovery using Fastboot left me with a fully working unbricked Mate S.
I know that some of you may know all about this but I could not find any information and had to work through it myself and from various websites. I hope that this will help you to unbrick your phone.
I still think there may be something missing like the oeminfo file etc. but at least it works, you may just have to update it in future using adb and Fastboot if no OTA is available or works. Not too much of a worry now you know how to do it.
I should also add that if you ever get an 'Invalid Argument' when flashing in fastboot mode and some oparts flash while others dont, it will be your cable. Trust me, one cable workws well another gives you this Invalid Argument error! Strange but true and may catch you out.
Thank you(Sathelp) to help me to solve the problem of mate s mobile, but I found only three orders adb work when used fastboot screen, there are boot, recovery and cust but the system and other order give fault result in adb. Therefore the phone remain broken. ..sorry for language
Is it possible to provide me a complete backup copy of the phone to be downloaded to my phone via the twrp recovery , perhaps back to life again, I would be grateful to you
my p[hone is a U00 not a L09, so my back up will not work. Have you changed your cable, I had simular problem, changed cable and other ROM parts worked OK. If not, then you will need to ask for a L09 TWRP back up from here. May be someopne will make one for you.
Finally, the problem has been resolved and the phone returned to work and all this is due to the help of (Sathelp), which benefited greatly from his observations in this matter ,the issue has been resolved by updating the ADB and the execution of an order (FASTBOOT FLASH SYSTEM.IMG) , which i could not be implemented except adb updated, but the phone remained unresponsive for OTA updates and remained on the android 5. Thank to xda forums.
Glad it is now working
Huawei Mate S CRR-L09 bricked
Hi
I have a Huawei Mate S (CRR-L09) does not work and remains stuck on the android logo. Mention that is installed TWRP and I tried to "wipe data factory reset". I accidentally erased everything on it, including Systema. I did not back up your data and restore the system. I downloaded firmware B145 stock on which I copied to root your phone but, but can not flash TWRP. I entered the menu Update (Vol + Vol- and Power) but does not see that folder "dload". Can someone help me with a backup or a tutorial on how to flash TWRP firmware.
Thank you

Oneplus 3T WiFi, Bluetooth not starting, Cant make calls

My OnePlus 3T had gone into a bootloop after updating. So I used the MsmDownloadTool V3.0.exe recovery tool to unbrick my phone. Thanks to this wonderful forum.
After this I could start my phone but wifi and bluetooth were not working. I could not make or receive calls but strangely I was able to access mobile internet. I flashed an official ROM from oneplus to my device to update the firmware but no success.
I have installed TWRP and SuperSu.
MAC address is shown as 02.00.00.00....
IP address unavailable.
In Root Browser
/persist/wlan_mac.bin
/etc/firmware/wlan/qca_cld/wlan_mac.bin
files shows valid mac address.
Current situation:
No Wifi
No Bluetooth
Cant make or receive calls
Mobile internet working
Please help..!!!
Hi I am facing exactly the same issues. Have you managed to solve yours?
If you have a backup of your EFS partition, you can try if your phone works again after you have restored it.
sniperle said:
If you have a backup of your EFS partition, you can try if your phone works again after you have restored it.
Click to expand...
Click to collapse
Unfortunatley I do not have EFS backedup. Any luck without that? or can I reuse someone's else or rebuild somehow?
Thanks for your reply.
I don't know if an EFS restore would have helped, that was just an idea.
You can't use the EFS partition of another phone because it contains data like IMEI and so on.
Did you search the forum for problems with EFS already ?
Boot into fastboot mode and try typing these two commands:
Code:
fastboot erase modemst1
fastboot erase modemst2
This will force Qualcomms' modem to rebuild itself upon next boot.
Note that you have to have unlocked bootloader in order to be able to do this.
przemcio510 said:
Boot into fastboot mode and try typing these two commands:
Code:
fastboot erase modemst1
fastboot erase modemst2
This will force Qualcomms' modem to rebuild itself upon next boot.
Note that you have to have unlocked bootloader in order to be able to do this.
Click to expand...
Click to collapse
Thanks! I will try to do that today and will report back.
pokemon1122 said:
Thanks! I will try to do that today and will report back.
Click to expand...
Click to collapse
No luck, I tried all three methods as described here https://forum.xda-developers.com/oneplus-3/how-to/fix-empty-imei-unknown-baseband-sim-t3480781 but no success. No idea how to check if my EFS is really broken or not.
One thing I noticed, if I try to update to latest stock, the phone bootloops. Only os it works is that comes default with MSM tool which is pretty old. And from that os, it is not possible to connect to wifi, bluetooth etc.
pokemon1122 said:
No luck, I tried all three methods as described here https://forum.xda-developers.com/oneplus-3/how-to/fix-empty-imei-unknown-baseband-sim-t3480781 but no success. No idea how to check if my EFS is really broken or not.
One thing I noticed, if I try to update to latest stock, the phone bootloops. Only os it works is that comes default with MSM tool which is pretty old. And from that os, it is not possible to connect to wifi, bluetooth etc.
Click to expand...
Click to collapse
Did you solve the problem? I am in the same situation.
after msmdownloadtool to unbrick no wifi - I found a fix
If you unbrick your phone with msmdownloadtool and then have no wifi, the solution I found is to do a locale upgrade of the OS.
Just search google for OOS 9.0.5 for OnePlus 3T (my phone), copy it to your phone and do a locale update. Problem fixed
coolrick said:
after msmdownloadtool to unbrick no wifi - I found a fix
If you unbrick your phone with msmdownloadtool and then have no wifi, the solution I found is to do a locale upgrade of the OS.
Just search google for OOS 9.0.5 for OnePlus 3T (my phone), copy it to your phone and do a locale update. Problem fixed
Click to expand...
Click to collapse
Thank you! After many times and solutions it's works!

Factory Reset to Stock (8.0) from root 8.0 updated to 8.1 - No USB Connection

Greetings,
I recently got a Pixel 2 XL and the first thing I did was try to root with SuperSU and TWRP. I had some issues with it and someone suggested Magisk. It worked great and I was able to update from the 8.0 to 8.1 with root. I kept up with the latest Magisk installs until the past week or so.
My phones USB port appears to have failed partially. Luckily I can still charge, but there is no way to see the device storage from a PC. Support has defaulted, after much troubleshooting, to an RMA solution with a refurbished phone. Thankfully, this seems to be covered by warranty and isn't going to pose a cost issue. However, through the troubleshooting I was forced to do a factory reset. I looked up some information regarding factory reset with rooted devices. I cannot find the exact tutorial I followed or thread I gained the how-to information, I'm not sure which it was. I simply searched how to factory reset magisk 8.1 device. It was quick and most of the stuff I find now has the same information.
Open Magisk, uninstall. Open TWRP, uninstall. Device Settings, Factory Reset. Easy
This seemed to have worked. I didn't run into any locked hardware issues thankful because I don't have USB to really flash something to it.
Before I continued, prior to attempting the reset I fully backed up the device to my computer using ES File Explorers FTP transfer over the wifi. This was great, lots of photos were able to be saved with no hassle. I copied the entire root directory and have it backed up.
The problem with the reset is that while Magisk remained uninstalled, TWRP has a basic file installed that upgrades to the full app. I still have root, which would have been nice, except I still need to unroot and go back to factory settings before I can send this device in.
Before I make a mistake moving forward, I want to find the best way to unroot, (preferrably relock the boot also), and return to factory stock as it was the day I got it so I can return in it in the best state I can.
I am running rooted android 8.1.0 Pixel 2 XL with kernel 4.4.88 if the helps. When I reset to factory defaults TWRP remains installed and root persists. I cannot connect via USB and run android dev tools to flash anything directly. How can I restore this device? I should have all original kernels backed up. During the root process I remember them saying to copy the old ROMs first and I performed every step exactly. I do have access to move files to and from the device via WiFi. Is it this even possible?
PS, does anyone think the firmware and rooted install could be the problem with the USB? It seems entirely like failed hardware to me but the troubleshooting was extremely thorough and seems to indicate softare/firmware are likely to be the issue instead of the hardware issue that was determined. Could this still rooted device have corrupted the USB transfer? It seems I should do my best to rule this out as well, more so than just giving them a factory reset device. I'd rather keep my phone if it can be fixed easily, than obtain a possibly low quality heavily used refurbished model.
Regards
Did you try removing and reinstalling the drivers?
Sent from my MI 5 using Tapatalk
teddy0209 said:
Did you try removing and reinstalling the drivers?
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
I assume you mean for the PC. Yes, I have tried uninstalling and reinstalling both using Microsofts found drivers and directly sent packages from the support team. Updates and 2 different PCs. DevKit installed on the one I originally used to root and a new PC with fresh driver installs.
They wouldn't suggest drivers for the phone, if you know of a way to install new drivers for the phone, please let me know, I'd definitely give that a shot.
Regards
BlazzedTroll said:
I assume you mean for the PC. Yes, I have tried uninstalling and reinstalling both using Microsofts found drivers and directly sent packages from the support team. Updates and 2 different PCs. DevKit installed on the one I originally used to root and a new PC with fresh driver installs.
They wouldn't suggest drivers for the phone, if you know of a way to install new drivers for the phone, please let me know, I'd definitely give that a shot.
Regards
Click to expand...
Click to collapse
I should include all troubleshooting I mentioned for those that think they have a solution for the dead USB. My original request was for the OTA flash directions without USB, but I think a lot of people will want to suggest fixes for the phone as I suggested in the PS section.
Step 1: Check computer software.
Windows users, check to see if you have the latest version of Windows Media Player and have installed all recent system updates. Visit omitted for more information.
Mac users, make sure you install and are using Android File Transfer. Visit omitted for more information.
Step 2: Check for system updates.
On your device, go to "Settings" > Scroll down to "System" > Touch "About phone" (or tablet) > Touch "System updates".
If your device has a modified OS, troubleshooting may not resolve your device issue. Re-image your device back to Android factory settings using the instructions from the following link: omitted
Step 3: Restart your device in safe mode.
With the device on, hold the Power button to get the "Power off" prompt.
Touch and hold "Power off" until the "Reboot to safe mode" prompt appears.
Touch "OK" to reboot in safe mode.
Note: To exit safe mode later, simply restart the device normally.
Step 4: Unlock your device.
Before connecting the device to a computer, if your device is password protected, unlock your device. A locked device will not connect to the computer.
Step 5: Connect USB cable directly into computer.
If the USB cable is connected through a USB hub or extension, unplug the cable from the hub/extension and plug it directly to the computer.
A pop-up window should appear.
Mac users will have the Android File Transfer window appear.
Windows users may have a pop-up window appear. If not: On the computer, click the Windows Start button on the bottom left > click Computer > under Portable Devices, click on the device > click on the device's Internal Storage.
Step 6: Test if you can transfer files.
Try transferring a small file.
If file transfer works, success! No need to do the next steps.
If file transfer still isn't working (no pop-up windows to allow file transfer), proceed to Step 7.
Step 7: Change your USB computer connection settings.
Android 6+ Marshmallow only:
Plug in the device.
Slide down the notifications drawer from the top of the screen.
Touch the notification saying "USB for charging."
Touch the option for "File Transfers".
Test file transfer again (from Step 6). If the file transfer does not work, proceed to Step 8.
Older Android OS Versions:
Go to "Settings", under "Device," touch "Storage"​ > touch the "Menu" button (three vertical boxes at the top right) > touch "USB computer connection".
Only Media Transfer Protocol (MTP) should be checked. Uncheck MTP, check and then uncheck PTP, then re-check MTP.
Test file transfer again (from Step 6). If the file transfer does not work, proceed to Step 8.
Step 8: Windows Only: Install Google USB Driver.
Go to omitted and click the blue button on the right labeled "Download Google USB Driver."
After the download completes, right click the file ("latest_usb_driver_windows.zip") and select "Extract All."
Follow the USB Driver installation instructions available here: omitted
Test file transfer again. If file transfer still isn't working (no pop-up windows to allow file transfer), proceed to Step 9.
Step 9: Turn on "Developer options" and disable USB debugging.
Go to "Settings."
If using a phone, swipe down the screen with two fingers, then touch "Settings."
If using a tablet, swipe down the screen from the right side of the top of the screen, then touch "Settings."
Scroll down to "System" and touch "Developer options." If you don't see "Developer options," turn them on as follows:
Touch "About phone."
Scroll down to the "Build number."
Touch "Build number" 7 times to activate "Developer options."
Under "Debugging," verify that the box for "USB Debugging" is not checked. If it is checked, touch the checkmark to uncheck "USB Debugging."
Once USB Debugging has been deactivated, test file transfer again.
Step 10: Try different USB connections.
Try plugging the USB cable into a different USB port on the same computer.
Try connecting to the same computer but using a different/spare USB cable.
Try connecting your device to another computer.
Click to expand...
Click to collapse
My apologies on readability, I tried to include HTML formatting. I couldn't figure it out, the options support code highlighting but not the code itself.
Additionally, I tried different USB cables, safe mode, and the factory reset that I could perform.
@BlazzedTroll
Summary:
You've uninstalled Magisk, so you don't have root access when booted. TWRP still remains, so you have root access there.
If I read you correctly, what you need to do is to get rid of TWRP. Right?
Download the corresponding factory image, extract recovery.img and flash that by issuing the Install Image option in TWRP.
Just make sure you've done everything you need to before doing this, since you can't get back to a custom recovery if your USB really is busted. Other things to do could include flashing the system.img the same way to revert any possible /system modifications, etc.
Didgeridoohan said:
@BlazzedTroll
Summary:
You've uninstalled Magisk, so you don't have root access when booted. TWRP still remains, so you have root access there.
If I read you correctly, what you need to do is to get rid of TWRP. Right?
Download the corresponding factory image, extract recovery.img and flash that by issuing the Install Image option in TWRP.
Just make sure you've done everything you need to before doing this, since you can't get back to a custom recovery if your USB really is busted. Other things to do could include flashing the system.img the same way to revert any possible /system modifications, etc.
Click to expand...
Click to collapse
When you say corresponding factory image, does that mean I need the exact one that came on the device? Or just the latest factory image for the right device?
*EDIT* Never mind that, I found the backup folder in the Unified Toolkit which contains a compressed zip just like the ones on the site. I'll use that and transfer to my device over WiFi and use TWRP to flash it and come back with the results.
Thank you for your assistance
@Didgeridoohan
I have a backup locally saved that resembles those packages. I was unable to locate a recovery.img in either my saved file or the one on the site. My version that was backed up was 1.171019.011, which is 8.1. I know my phone came originally with 8.0 so I tried looking at one of the those for a recovery.img and still could not locate one.
In the zip there are several files
bootloader-taimen-tmz12a.img
flash-all.bat
flash-all.sh
flash-base.sh
another zip
radio-taimen-g8998-00164-17... .img
inside the second zip, many more .img files looked promising
abl.img
aes.img
android-info.txt
boot.img
cmnlib.img
cmnlib64.img
devcfg.img
dtbo.img
hyp.img
keymaster.img
laf.img
modem.img
pmic.img
rpm.img
system.img
system_other.img
tz.img
vbmeta.img
vendor.img
xbl.img
Same files in all 3 zips I checked.
TWRP only expects recovery.img for "BACKUP EXISTING RECOVERY"
TWRP also has "TWRP FLASH", which I did as one of my troubleshooting steps before and got the Google Pixel 2 XL (taimen) flash. These still keep the TWRP and root, which I believe is to be expected for that flash option.
DELETED
BlazzedTroll said:
I assume you mean for the PC. Yes, I have tried uninstalling and reinstalling both using Microsofts found drivers and directly sent packages from the support team. Updates and 2 different PCs. DevKit installed on the one I originally used to root and a new PC with fresh driver installs.
They wouldn't suggest drivers for the phone, if you know of a way to install new drivers for the phone, please let me know, I'd definitely give that a shot.
Regards
Click to expand...
Click to collapse
You're right, I mean for PC...
You can usually get twrp backups from same device with same rom and flash it on yours via twrp ( ask on your device forum)... You will need system.img, recovery.img, and boot.img... I'm not so sure if you can relock the device without working usb/fastboot...
Sent from my MI 5 using Tapatalk
@BlazzedTroll
My apologies... I'm still not used to these damned A/B devices. :laugh:
If I remember correctly, recovery is included in the boot image, so what you need to do is flash the stock boot.img file to slot A. Don't know if this is possible in TWRP.
teddy0209 said:
You're right, I mean for PC...
You can usually get twrp backups from same device with same rom and flash it on yours via twrp ( ask on your device forum)... You will need system.img, recovery.img, and boot.img... I'm not so sure if you can relock the device without working usb/fastboot...
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
I'll give this a shot, I have system.img and boot.img, as I said in reply to Didgeridoohan, I do not have a recovery.img in the files.
Sad news about relocking, but that should be OK.
Thanks for lending some help
Didgeridoohan said:
@BlazzedTroll
My apologies... I'm still not used to these damned A/B devices. :laugh:
If I remember correctly, recovery is included in the boot image, so what you need to do is flash the stock boot.img file to slot A. Don't know if this is possible in TWRP.
Click to expand...
Click to collapse
That's alright. I don't know much of anything about them. It's easy enough to follow tutorials and if I had my USB connection I could do as you say pretty quickly. The problem is I don't understand what TWRP even is. There doesn't seem to be an option to flash you own custom img. "TWRP FLASH" only lets you select from the latest versions and downloads the one you select and starts the flash. "BACKUP EXISTING RECOVERY" expects a recovery.img and doesn't let me select anything other than that. I could try renaming system.img to recovery.img, but until I find out what the difference between the images is, I'm not to keen on trying that one. Sounds like a good way to get hosed before I return it. At this time, I would think without having USB access the folks at Google would be happy to have root on the phone. Rather return it working, but rooted, than bricked.
So I was trying to follow some other suggestions and it seems like maybe the device is actually not rooted anymore.
There is no SU file located in system/bin or system/xbin.
When I download something like "Root Checker" it gets stuck verifying the root.
I tried to use apps like rashr and flashify to flash a stock recovery and neither app will load properly suggesting no root access.
This means when I ran the uninstalls, everything did uninstall and unroot but the TWRP install must not be very clean (I don't think it's being maintained anymore for most devices). So I need to try and find where this app is located and remove it manually before I run the recovery again. If I solve this I'll post back.
BlazzedTroll said:
So I was trying to follow some other suggestions and it seems like maybe the device is actually not rooted anymore.
There is no SU file located in system/bin or system/xbin.
When I download something like "Root Checker" it gets stuck verifying the root.
I tried to use apps like rashr and flashify to flash a stock recovery and neither app will load properly suggesting no root access.
This means when I ran the uninstalls, everything did uninstall and unroot but the TWRP install must not be very clean (I don't think it's being maintained anymore for most devices). So I need to try and find where this app is located and remove it manually before I run the recovery again. If I solve this I'll post back.
Click to expand...
Click to collapse
You don't have root access, since you uninstalled Magisk. TWRP has it's own root, so while booted to recovery you can still do root stuff...
The only way to restore the stock recovery is to flash the boot image to your device.
And TWRP is pretty much the only maintained custom recovery for most devices...
Just a small note: this demonstrates the issues with using toolkits... It's just to click away and you never really learn how things actually works. Can bite you in the bee-hind when things go south.
Didgeridoohan said:
You don't have root access, since you uninstalled Magisk. TWRP has it's own root, so while booted to recovery you can still do root stuff...
The only way to restore the stock recovery is to flash the boot image to your device.
And TWRP is pretty much the only maintained custom recovery for most devices...
Just a small note: this demonstrates the issues with using toolkits... It's just to click away and you never really learn how things actually works. Can bite you in the bee-hind when things go south.
Click to expand...
Click to collapse
At this point I've just ordered the RMA replacement and I'll send it in. Hopefully those at Google are able to verify that the hardware malfunction is entirely unrelated to the root and they still honor the warranty. If the USB hadn't failed, I would easily flash back to stock as you have suggested. It's a fairly trivial action.
I agree somewhat with the idea that toolkits can be problematic in this way. There was quite a bit involved in running through the toolkit, it wasn't that One-Click root/jailbreak type stuff. I issued all of the commands over ADB and was fairly knowledgeable about what actions I was performing. This issue lies in this toolkits maintenance. The latest update to TWRP removed a ton of features and I'm unable to find the other version. Magisk was fully uninstalled as expected. TWRP did not make it clear that the flashed recovery would in fact contain was is essentially an ad for their toolkit. The placeholder app, as they call it, is literally just an ad that pops up when your recover that says "Don't forget to install us!". You can't even remove that file from the recovery partition, you must reflash to remove it. So the problem isn't just that you don't learn how it works, it's that you aren't forced to go through the changes with a fine-toothed comb as you would creating your own recovery. Had I created my own recovery I would have left it stock so that in the event of a failure such as this you are returned to factory stock without any changes except the unlocked bootloader. I guess in the future I'll have to do this myself. I did take the easy way out and just run the defaults from the toolkit in most cases.
Thanks to you and the others who threw in some helpful suggestions.
For anyone stumbling across this in the future, the problem is a 'semi-rooted' recovery can't be flashed without USB transfer capabilities. The solution is to RMA the faulty hardware hopefully. They should be reflashing all phones they get after repair/refurbish anyway.
Best Regards
For future reference...
BlazzedTroll said:
Greetings,
I recently got a Pixel 2 XL and the first thing I did was try to root with SuperSU and TWRP. I had some issues with it and someone suggested Magisk. It worked great and I was able to update from the 8.0 to 8.1 with root. I kept up with the latest Magisk installs until the past week or so.
My phones USB port appears to have failed partially. Luckily I can still charge, but there is no way to see the device storage from a PC. Support has defaulted, after much troubleshooting, to an RMA solution with a refurbished phone. Thankfully, this seems to be covered by warranty and isn't going to pose a cost issue. However, through the troubleshooting I was forced to do a factory reset. I looked up some information regarding factory reset with rooted devices. I cannot find the exact tutorial I followed or thread I gained the how-to information, I'm not sure which it was. I simply searched how to factory reset magisk 8.1 device. It was quick and most of the stuff I find now has the same information.
Open Magisk, uninstall. Open TWRP, uninstall. Device Settings, Factory Reset. Easy
This seemed to have worked. I didn't run into any locked hardware issues thankful because I don't have USB to really flash something to it.
Before I continued, prior to attempting the reset I fully backed up the device to my computer using ES File Explorers FTP transfer over the wifi. This was great, lots of photos were able to be saved with no hassle. I copied the entire root directory and have it backed up.
The problem with the reset is that while Magisk remained uninstalled, TWRP has a basic file installed that upgrades to the full app. I still have root, which would have been nice, except I still need to unroot and go back to factory settings before I can send this device in.
Before I make a mistake moving forward, I want to find the best way to unroot, (preferrably relock the boot also), and return to factory stock as it was the day I got it so I can return in it in the best state I can.
I am running rooted android 8.1.0 Pixel 2 XL with kernel 4.4.88 if the helps. When I reset to factory defaults TWRP remains installed and root persists. I cannot connect via USB and run android dev tools to flash anything directly. How can I restore this device? I should have all original kernels backed up. During the root process I remember them saying to copy the old ROMs first and I performed every step exactly. I do have access to move files to and from the device via WiFi. Is it this even possible?
PS, does anyone think the firmware and rooted install could be the problem with the USB? It seems entirely like failed hardware to me but the troubleshooting was extremely thorough and seems to indicate softare/firmware are likely to be the issue instead of the hardware issue that was determined. Could this still rooted device have corrupted the USB transfer? It seems I should do my best to rule this out as well, more so than just giving them a factory reset device. I'd rather keep my phone if it can be fixed easily, than obtain a possibly low quality heavily used refurbished model.
Regards
Click to expand...
Click to collapse
Try downloading a stock Fastboot Image for your device then unzip it, collect boot.img, then flash just the stock boot.img from TWRP. Should solve the issue upon the following reboot with no more TWRP or root. If youre on magisk or systemless SuperSU. Not locking the bootloader though lol that's hopeless without usb function unless it's possible to lock bootloader using the terminal command with an WiFi ADB app from another device then follow with "adb reboot bootloader", "fastboot boot TWRP.img", then flash stock boot.img from there. I'm just spitballing the second one lol, but if it'll make it to the TWRP part successfully it should work in theory unless the WiFi ADB connection can't make it past reboot which I've never tried. Should probably get an unlock box like NCK Box Pro or whatever supports your device and you'll always know if the port is ****ed or not and flash back to full locked stock with the box if it isn't. It's what I do now. Handy little ****ers lol.

no custom recovery no bootloader unlock, no factory reset, need ideas

Hi,
so i got a situation here that xiaomi mi a2 (6x) out of nowhere rebooted to factory recovery with message "cant load android system. your data may be corrupt. If you continue to get this message you may need to perform factory reset deleting all data stored on this device"
Now after turning it off and on, it shows black screen "failed to boot" with option to power off or restart.
When restarting it goes to factory recovery again with that message and option to factory reset or try again (restart)
Now i cant perform factory reset before backing up the data, but i cant find the way to backup.
There is no custom recovery to download files from phone. When tried to flash custom recovery found out i cant because bootloader locked. And when found the way (dont know i it works) to unlock it without loosing data - cant do even that because developer options must be enabled to allow unlocking and debugging, so i get message in adb console FAILED (remote: Flashing Unlock is not allowed.
Is there any other way to keep the data before doing factory reset ?
Maybe try to flash with miflash keeping the data
blazessdd said:
Maybe try to flash with miflash keeping the data
Click to expand...
Click to collapse
unfortunately miflash cant do anything with locked bootloader as well. Just when starts to flash, gets error with bluetoth_a.
After research i noticed that miflash does nothing special at all just automated flash commands. In rom directory you can find flashing .bat files and run them in adb console.
When did that got all the data log, that bluetooth a is the first file that is tried to flash and stuck on locked bootloader.
Hello. Did you manage to solve your problem?
I have the same saituation.
Hi, unfortunately the only way i found is EDL mode.
https://youtu.be/i3OU4DOd7aY
When you keep those pins shorted, plug usb to your pc, and then , simply said, pc sees it as another device that can be flashed with everything locked.
So i flashed with miflash with keeping files option, but all that was saved is locking pattern. All media files lost.
Anyway, now i rooted and installed custom recovery to avoid any incident like this.
andjar said:
Hi, unfortunately the only way i found is EDL mode.
https://youtu.be/i3OU4DOd7aY
When you keep those pins shorted, plug usb to your pc, and then , simply said, pc sees it as another device that can be flashed with everything locked.
So i flashed with miflash with keeping files option, but all that was saved is locking pattern. All media files lost.
Anyway, now i rooted and installed custom recovery to avoid any incident like this.
Click to expand...
Click to collapse
you should edited rawprogram0.xml to not flash userdata (for saving your data)
Well if i only had this info 2 moths ago...
At leats others with this problem can find solution here now.

Question Can't install fastboot roms

Hi everyone, I'm writing this post to ask for your help regarding an issue that is driving me to exhaustion. I also apologize in advance for any errors. It all started after trying to overclock the gpu with the konabless app, previously the app made me make a backup of the vendor_boot image in case of post modification problems, so next i edited the frequencies of the gpu, I applied the changes, rebooted and BOOM, a phone freezed at mi logo. So I rebooted in twrp to reflash the stock vendor_boot image, and for my great intelligence I flashed it on the boot image partition, and what did I get? A phone stuck in fastboot.
Oh well, a phone that turns on in fastboot is not a big problem you'll say, and I thought the same as i previously had a problem and solved it by reflashing the stock rom in fastboot, so I took my nice computer (actually it's a 12 year old pc that runs on carbon, but that does its job), I opened the mi flash tool, connected the phone, selected the fastboot rom, precisely the EEA 12.5.7.0 (like the one natively installed before the damage) and started the installation. 20 minutes later ... error: cannot load bla bla bla, ok ok, i seached various solutions on Google and tried every metods, i changed the directory of the mi flash, of the rom, I updated the version of mi flash, i installed both on C:/ drive, reinstalled the drivers, i edited the batch file to remove the anti rollback but nothing, it arrives at flashing the super image and after some minutes it fails the flashing. Before you ask, YES, the bootloader was unlocked. I also tried to flash the rom in twrp, but ... the phone no longer had the twrp. The only way to start it was via command (fastboot boot twrp.img), the onekey injection did not make it permanent, and connecting the phone to the pc it revealed the device, but not the internal memory, I tried to make a format data but nothing. I managed to make it permanent only once, manually flashing only the vendor_boot and boot images in one of the boot_ * slots, in that case incredibly the pc also detected the internal partition, I copied the flashable rom and ... the twrp said to restart the recovery for I don't remember what, but basically I couldn't install the rom via twrp. At that point I finally gave up and took the phone to an authorized xiaomi service center where they fixed it (bye bye 25€), I don't know how exactly, I would opt through edl mode I think, and now i have my working phone...but heeeeeey, they flashed me the 12.0.1 TW version, not the EEA... Ahhhhh come on. They also re-locked the bootloader, so... agaaaain i re-unlocked the bootloader, this time i downloaded the unofficial tool xiaomi flash tool v2, it installed every needed driver, i clicked on "my phone works and i want to mod it", this time i tried to flash the global rom 12.5.7.9 and when it arrives at flashing the super image IT FAILS (fast boot flash_all failed, exit code:1, output: flash super error), and like a nightmare the phone was stuck in fastboot again, fool once but never fool twice, this time I had previously made a twrp backup of everything except the data partition, I install it and the phone restarts perfectly, I also notice that despite the attempted flash of the rom in fastboot after restoring the twrp backup without the data partition, nothing has been deleted from the data partition. So benevolent gods of xda, how the heck should I change rom region? Thanks for your attention and I hope I haven't stressed you out any more than I already am.
you are probably uploading rom miflashem pro and hence this error - I had the same. Use miflash's built-in pro miflash and it should go - it worked for me
SpYneX_ said:
Hi everyone, I'm writing this post to ask for your help regarding an issue that is driving me to exhaustion. I also apologize in advance for any errors. It all started after trying to overclock the gpu with the konabless app, previously the app made me make a backup of the vendor_boot image in case of post modification problems, so next i edited the frequencies of the gpu, I applied the changes, rebooted and BOOM, a phone freezed at mi logo. So I rebooted in twrp to reflash the stock vendor_boot image, and for my great intelligence I flashed it on the boot image partition, and what did I get? A phone stuck in fastboot.
---
Click to expand...
Click to collapse
1/ OMG, take your time, espace your words, compact your questions...
2/ For old configuration a user have fix adb/drivers/detection problem with an another driver pack, and a old is btter than the lastest for some old configuration (so if your conputeur jhave 12 years, maybe...)
So try to install this drivers here
Change your USB port and verify your cable
3/ If problem occur, change computer (family/friend computer), just for flash, for be sure it's a communication/usb/detection problem
PS : Finally, why trying to overclock a soc already overclock by Snapdragon and always overheat ? It's really want finding problems ^^

Categories

Resources