Hello.
I want to ask for the correct method to go from xiaomi eu rom (xiaomi.eu_multi_HMNote10_V12.0.10.0.RKGMIXM_v12-11) and TWRP to the stock state of the device (miui_MOJITOEEAGlobal_V12.0.3.0.RKGEUXM_d15dfae454_11.0) to be sure there are no warranty issues.
The device seems to have a problem with the wifi.
At first I thought it was due to the official EEA rom, so decided to open the bootloader, install TWRP and xiaomi eu stable rom.
I have this kind of rom in other phone and it works pretty well.
But the problems persist in the new rom.
So I make a warranty call and I assume the phone needs to be as stock as posible to not have any problems of void warranty.
So this is my question.
What is the correct method to get the phone back to stock rom and stock recovery?
Answer as detailed as possible, I'm not used to do this kind of things.
(A step by step guide would be wonderful)
Do you think unlocked bootloader can void warranty?
Thanks in advance.
Download the latest Xiaomi Mi Flash Tool, e.g. here:
Download Xiaomi Flash Tool 20210226 - Official Tool
Download the Official and Tested version of Xiaomi Flash Tool, i.e., Xiaomi Flash Tool 20210226 which allows you to Flash Stock Firmware on Xiaomi Devices.
xiaomiflashtool.com
Then the corresponding fastboot ROM and unpack:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Put the smartphone in fastboot mode, connect via USB, open Mi Flash Tool, select the ROM folder and flash.
If you select "clean all and lock" in the Mi Flash Tool, the bootloader will be locked again and everything in the original state.
Unlock your phone cancels the warranty.
When requesting, you give consent to cancellation.
The original firmware and locking may not be enough.
I wish good luck.
p.s.: For new goods never believe that other firmware will fix it what doesn't work.
Xiaomi gave a different statement:
ROOTING & BOOTLOADER UNLOCK / WARRANTY (Official answer from Xiaomi)
Hello everyone: So that everyone will have a crystal clear status: Got answer (email) from Xiaomi for warranty question with bootloader unlock AND rooting: "...With respect to your concern, I would like to inform you that rooting of your...
forum.xda-developers.com
I wish it would generally pay.
It's "only" answer to one customer to email.
I've never seen a public statement from Xiaomi.
Seller may not accept anything like that.
It's good to count on everything.
Just one more question before going stock.
Is there a way to check if the wifi antennas on the phone are working badly?
I mean, to know if the wifi problem is due to the software or the hardware.
Thanks
Apk: https://play.google.com/store/apps/details?id=com.vrem.wifianalyzer
GPS enable
Well, Wifi analyzer sees the networks with a lot of signal strength (-21dBm), but the phone refuses to connect, or just connect and disconnect random.
Sometimes it doesn't even appear in the list of available networks
Can it be interpreted as a software failure?
The analyzer only sees what the system. Therefore, the problem cannot be in the system, even in the hardware.
So where does the wrong WiFi signal appear?
I would say you have a problem with the WiFi channel.
It will want to choose the best channel and set it in the router.
I tested this phone with 3 different routers in 3 different places. And 3 different configurations and wifi environments.
I don't think the router is the problem because in all of then the phone does the same things.
Random disconnects from wifi, or refuses to connect with good strength and correct passwords.
Also my other phone (note 5 xiaomi eu rom) works without issues on them at the same time.
If the analyzer sees what the system sees, how is it possible to have the network in the analyzer at full strength, and not be able to see in available networks in the phone?
Sorry if I'm being a bother, but I just don't understand how this can happen.
Don't have a battery saving on WiFi?
Android 11 uses some connection of GPS with WiFi.
For now, it is incomprehensible to me.
But it can affect your connection.
WiFi fully without GPS now doesn't work!
The WiFi setting now announces this:
{
"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"
}
In Android 10 (and older) worked WiFi search even when the location is turned off.
What's this for a meaningless condition?!
I need WiFi network monitoring on, but location turned off.
Hi.
I'm having an error during the flashing progress.
error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done
http://puu.sh/HLbuv/30bd11c733.png
It happend a couple of times, with the eea rom and also with golbal.
Installed Global 12.0.7.0 stable
in this forum there is a 2019 post about the same error and people say is ok, but it isn't
It seems to start as fresh, but gives an error during the process.
After a couple of times, the phone finishes the setup.
But there are still error.
I can't enable the wifi and search for networks.
When I switch on the wifi, the settings app stops to work.
just to options, Wait and Accept.
Tried reset and power off and on again. Same result. No wifi.
Now it is going back to factory defaults.
----
Going back to factory defaults did nothing.
Let's try reflash EEA rom, even with the error during flashing.
Try to restore the path to Files for Miflash.
I think it helped me once, although I had the way right.
Finally, Miflash restarts the phone and will notify success after you start the phone.
I don't understand what you mean "Try to restore the path to Files for Miflash."
Now it sits in D:\xiaoroms\MiFlash20210226
The roms are in
D:\xiaoroms\eea
D:\xiaoroms\global
path to Files for Miflash:
You should download this file for Miflash:
mojito_global_images_V12.0.7.0.RKGMIXM_20210416.0000.00_11.0_global_f13a7ddea1.tgzThen extract. The path is to go to this file folder.
So something like:
D:\xiaoroms\mojito_global_images_V12.0.7.0.RKGMIXM_20210416.0000.00_11.0_global
Tried again and the same error appears once more.
Any ideas?
I doing "Clean all" instead of "clean and lock", I don't know if this is a possible issue.
I personally used Miflash20181115.
boot.img now also contains recovery and other partitions.
It could help first flash boot.img from the folder firmware:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
EDIT! I thought, how do you connect the phone to Miflash?
Try this procedure:
Turn off the phone. Start MiFlash. Turned off the phone connect the USB cable to the PC. Can start charging. Press in Miflash "refresh". Repeat the "refresh" if the phone is not loaded. Test Flash. You do not use any phone buttons.
Tested the edited part
Mismatching image and device.
Could it be because the note 10 "sunny" uses "mojito" images??
Whatever, failed with an error: flash timeout.
About how to use miflash.
Generally I put the phone in fastboot mode
plug in usb directly to the motherboard backpanel
connect the phone
open miflash
phone usually appears by itself
select rom
flash and wait
Tomorrow I'll try to flash boot.img as you said
Related
Hey Guys,
tried to install LineageOS on my mothers tablet, but forgot to unlock bootloader first, so i got a softbricked device like some other guys here.
Because i haven´t found a solution/tutorial here, i tried some things out and now i got a working device
Unbrick The Brick
I found a version in this forum, which installs a ofw -> https://w3bsit3-dns.com/forum/index.php?showtopic=545744&st=2260
My Device was connected in this mode and via cmd : "adb devices" it was listet
{
"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"
}
After unzipping 0.rar, i startet a cmd as administrator, navigated with cd to the unziped folder and startet "flashall.cmd"
The Device starts again
Install OFW
Unfortunetly the Unblock Bootloader APK from Asus ended up with an error , i tried a lot with adb install *.apk and so on, but nothing worked out... Therefore i installed the latest OFW
You need an SD-Card and the latest Version (https://www.asus.com/Tablets/ASUS_MeMO_Pad_FHD_10_ME302KL/HelpDesk_Download/)
-> For me it is the "ASUS MEMo Pad FHD 10 LTE Firmware: V10.10.3.39 Only for WW SKU (Android 4.2.2)"
Copy the unzipped zip (you will see what i mean) to the SD-Card and unname it to "APQ8064_SDUPDATE.zip"
Insert the micro SD card into the tablet.
Turn off the tablet.
Press and hold Volume Up + Power Key, wait until the bootloader logo appears, and then the FW update process begins. (if this don´t work out try the APK "Recovery Reboot")
After the completion the device will automatically reboot.
Perform the factory data reset.
IUnlock Bootloader with the official APK
-> https://www.asus.com/de/supportonly/ASUS MeMO Pad FHD 10 LTE/HelpDesk_Download/ -> Utilities -> Expand -> "Unlock Device App"
Install TWRP
-> https://forum.xda-developers.com/android/general/recovery-twrp-3-1-1-0-asus-me302kl-t3609759
Install LineAgeOS
-> https://forum.xda-developers.com/an.../rom-8-0-0-lineageos-15-0-unofficial-t3693838
Enjoy
I had some hope when I saw this thread. I had problems with the bootloader unlock too.
slungshot said:
I had problems with the bootloader unlock too.
Click to expand...
Click to collapse
And it helped?
My advice to anyone trying to revive this old tablet is to just buy a new one, no matter what the cost and you will come out ahead in comparison to time wasted trying to resurrect this old beast. Still if you are like me and perhaps when you arrive here are "already in way too deep", here are some hints to get you going. I'm 2 weeks into playing with this thing but making good progress. Wishing I'd just bought a new one but since I usually forget everything I learned dealing with ROM builds a few weeks after I set it aside,I can't say I learned a valuable lesson so I'm not sure of the benefit.
First of all, to ensure you don't brick this thing, be sure to RESTORE TO FACTORY before unlocking. Then once set to factory defaults and you are configuring it anew again, when you get to the screen asking to sign into Google, then don't do it because if you do, when you run the unlock routine it will go into a loop asking for your Google ID and password. Then when you sideload in the Assus unlock app and also accept any upgrades that Asus provides if at this point you have never logged into Google, the only requirement of this unlock routine is that you have a working wifi accessed so you will never get into the Google ID loop if you don't have a Google sign-in account set up.
So, I've loaded every version, evaluated them and rejected all but 14.1 due to some quirk or another. My mistake was loading multiple zips after the unnlock (including Gapps up front, a no-no in my opinion) and this has left me yet to load any of the Gappas package yet, discovering that is what gave me my black screen initially. I now have a full suite of mapping software loaded and working plus many basic language tools and other apps that support traveling and using this device as a guide. I have side loaded about 25 apps and all is well so far without the play store. I have the GPS working (couldn't get it to work in 13.x and 15.x versions) and additionally I was able to load Magisk systemless, Xposed V25 systemless, XprivacyLUA and a long list of Xposed modules that all work perfectly, plus I have a functional root. I haven't tried any super secure apps like banking because I haven't even set up playstore. So right now I have a great functioning device that is not so Googled-up. I am not sure if I will load the 7.1 Gapps at this point now but I plan to get everything working on this device I can without Google Playstore and the other Google suite and see just how far I can get without Google apps. I do miss the voice typing, however.
Another thing that will get you confused with this tablet is the first time after flashing it with the TWRP recovery and just as you enter fastboot reboot on your computer and press the enter key for the very first time, you have to hold in the power button and up-volume button on the tablet at the same time you reboot with fastboot and if you don't when you reboot after the flash of the new recovery, the stock ROM will revert the TWRP recovery.img back to stock. I know, it sounds hard to believe but if you flash it and don't get the TWRP menu on the next recovery boot, this is what happened.
https://w3bsit3-dns.com/forum/index.php?showtopic=545744&st=2260
link not working
Hello, recently software break my Xiaomi MI 9 SE, this because when triet to boot to recovery after flashing TWRP give this message:
{
"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"
}
And when tried to reboot into recovery dosn't work, this post is because solved this problem took me almost two days so i'm trying to help someone needed
I upload all the files needed for restore your phone and install pixel clean room
Enter to this link: (Send me private to obtain, XDA doesn't let me post any link because i'm a new user... sorry for that)
Inside is necessary to download the file with name "MiFlash.zip", unzip the file and execute the MiFlash.exe
Reboot you phone in bootloader and connect to the pc
Download the file inside de google drive link, with name "grus_eea_global_images_V10.2.9.0.PFBEUXM" this is the factory system proporsionated by xioami, this case is the global flavor
Unzip the content, and in the "MiFlash" program configure the route to the folder previously unziped, with your phone connected proced to install run the program
In this moment, we have restore our phone with the stock room, not my ideal room but solve the principal problem
So, to go forward i install twrp (probed worked) and flash another room and rooting. It's not necesary follow this steps.
Reboot to bootloader the phone and connect to the pc
Download the file "recovery-TWRP-3.3.0-0421-XIAOMI9SE-CN-wzsx150.img"
Enter inside the folder with the image dowloaded previously
Run the follow command "fastboot flash recovery recovery-TWRP-3.3.0-0421-XIAOMI9SE-CN-wzsx150.img"
Run the command "fastboot boot recovery-TWRP-3.3.0-0421-XIAOMI9SE-CN-wzsx150.img" or reboot and go to the recovery
With your phone connected, download the following files ("PixelExperience_Plus_grus-9.0-20190924-1959-OFFICIAL.zip", "Magisk-v20.0.zip" and "fw-vendor_grus_miui_GRUSGlobal_V10.3.4.0.PFBMIXM_1af3c0ea1e_9.0.zip"), copy this files inside the memory of your smartphone.
With TWRP, wipe everything except the internal storage of your phone
Go to flash and install "fw-vendor_grus_miui_GRUSGlobal_V10.3.4.0.PFBMIXM_1af3c0ea1e_9.0.zip"
Flash the following zip file "PixelExperience_Plus_grus-9.0-20190924-1959-OFFICIAL.zip"
Finnaly flash the "Magisk-v20.0.zip"
Reboot your phone and wait, the magic it's happened
Well, finnaly sorry for my bad english, hope this help someone, for me took me almost 2 days to repair my phone.
Bye
walberth said:
Hello, recently software break my Xiaomi MI 9 SE, this because when triet to boot to recovery after flashing TWRP give this message:
And when tried to reboot into recovery dosn't work, this post is because solved this problem took me almost two days so i'm trying to help someone needed
I upload all the files needed for restore your phone and install pixel clean room
Enter to this link: (Send me private to obtain, XDA doesn't let me post any link because i'm a new user... sorry for that)
Inside is necessary to download the file with name "MiFlash.zip", unzip the file and execute the MiFlash.exe
Reboot you phone in bootloader and connect to the pc
Download the file inside de google drive link, with name "grus_eea_global_images_V10.2.9.0.PFBEUXM" this is the factory system proporsionated by xioami, this case is the global flavor
Unzip the content, and in the "MiFlash" program configure the route to the folder previously unziped, with your phone connected proced to install run the program
In this moment, we have restore our phone with the stock room, not my ideal room but solve the principal problem
So, to go forward i install twrp (probed worked) and flash another room and rooting. It's not necesary follow this steps.
Reboot to bootloader the phone and connect to the pc
Download the file "recovery-TWRP-3.3.0-0421-XIAOMI9SE-CN-wzsx150.img"
Enter inside the folder with the image dowloaded previously
Run the follow command "fastboot flash recovery recovery-TWRP-3.3.0-0421-XIAOMI9SE-CN-wzsx150.img"
Run the command "fastboot boot recovery-TWRP-3.3.0-0421-XIAOMI9SE-CN-wzsx150.img" or reboot and go to the recovery
With your phone connected, download the following files ("PixelExperience_Plus_grus-9.0-20190924-1959-OFFICIAL.zip", "Magisk-v20.0.zip" and "fw-vendor_grus_miui_GRUSGlobal_V10.3.4.0.PFBMIXM_1af3c0ea1e_9.0.zip"), copy this files inside the memory of your smartphone.
With TWRP, wipe everything except the internal storage of your phone
Go to flash and install "fw-vendor_grus_miui_GRUSGlobal_V10.3.4.0.PFBMIXM_1af3c0ea1e_9.0.zip"
Flash the following zip file "PixelExperience_Plus_grus-9.0-20190924-1959-OFFICIAL.zip"
Finnaly flash the "Magisk-v20.0.zip"
Reboot your phone and wait, the magic it's happened
Well, finnaly sorry for my bad english, hope this help someone, for me took me almost 2 days to repair my phone.
Bye
Click to expand...
Click to collapse
can we use another rom instead of PixelExperience?
2 things:
1 - I seriously messed up my phone with that twrp. Although I was using a more recent version, I don't recommend it. Use redispade twrp instead
2 - You can and you should use another ROM. PE is dead. Just check vendor required and,if different from the one suggested by OP, flash it instead.
rzki03 said:
can we use another rom instead of PixelExperience?
Click to expand...
Click to collapse
Of course, in the example I use this room and in phome is working with some minor bugs, but @elpaablo say that it's nor longer getting support. I recommend you use another room with active development and support
elpaablo said:
2 things:
1 - I seriously messed up my phone with that twrp. Although I was using a more recent version, I don't recommend it. Use redispade twrp instead
2 - You can and you should use another ROM. PE is dead. Just check vendor required and,if different from the one suggested by OP, flash it instead.
Click to expand...
Click to collapse
Thanks, this twrp is the only that I test and work, but I don't tested the twrd indicated. And thanks for the info about the rom, I will be updated because in this time I experimented some bugs.
Hello Everyone!
I need urgent help from you all because I am currently stuck in a very bad situation. Please please please!! Help me to get out of this. Let me start from the beginning of whatever I did. This is going to be a very long post so please bear with me.
Why did I try to root my device?
I have Realme 1 which works on Android 9 and does not support internal screen recording. So I thought rooting would help me and I would be able to create gaming videos.
1st Phase:
I researched about how to root my device.
I came to know that first I’ll have to unlock my bootloader.
I tried to unlock my bootloader and when I was running the necessary commands like fastboot reboot, it simply showed, “Waiting for device…..”
Now confused, I went to the Device Manager and uninstalled Android and its drivers from the category of other devices by mistake. Now, my problem was that, how to pass commands to my device?
Next, I deleted everything, and started from scratch. This time, I connected my device (via the same USB cable) and I did something (I don't exactly remember what I did, but ultimately it lead me to Windows Update, where I clicked on View Optional Updates and updated the driver. I am attaching a screenshot of what I had installed.
Next, I downloaded platform tools, extracted them and in the address bar typed cmd and did the following checks to ensure that my device can receive commands.
When device was powered on:
adb devices
Returned: _________ device
Next command:
adb fastboot (Something like that which took it to the fastboot mode)
Next Command:
fastboot devices
Returned: _________ fastboot
Satisfied that I was going on well, I unlocked the bootloader using the respective commands.
2nd Phase:
Now I knew, my bootloader was unlocked, so I did the next step.
I switched to fastboot mode.
Downloaded boot_patched.img for Realme 1 C.50
Next, I pasted it into the platform tools folder.
Next, booted my device into the fastboot mode, and gave the flashing command.
Confirmed it on my device using volume up key.
Gave fastboot reboot command to reboot my device.
Downloaded Magisk Manager and rooted my device successfully.
Downloaded RootChecker app to be sure and got the positive result.
I downloaded the apps I needed.
Problem Phase:
I had downloaded a banking app but it didn’t work because my device was rooted, so I searched, “How to hide root from banking apps?”
I came to know that the solution for this was on Magisk Manager itself. Magisk Hide
So, I opened the Magisk Manager and I was shown a prompt to download something (Or maybe I downloaded something from the settings? It was something like system host module or something like that) Now I don’t exactly remember whether my device rebooted or not, but let me continue.
So, I went to settings, enabled Magisk Hide, selected the app from which I had to hide root and opened the app. It didn’t work.
I searched the internet and saw that I had to reboot my device as well.
After I did that I faced a more serious problem. The app was still not working and my sim cards were disabled.
Now I panicked, I did the ultimate thing for which I had rooted my phone, I downloaded the game and the screen recorder. I chose the internal sound recording option, it told me to download some Magisk Module for it to work. So I did it.But it still didn’t work.
Now I was sad, I didn’t know what to do. Then ultimately I opened my RootChecker app and check the root status of my device and you guys won’t believe what I saw.
" No proper root access granted "
Super Problem Phase:
I decide that I’ll unroot my device. So, I set down to work.
I got to know that I had to uninstall the Magisk Manager completely. I did so and my device rebooted.
There came a wave of relief, my sim cards started to work.
I thought that my device was unrooted now, so I opened my banking app and it showed: “Your device is rooted! You can not proceed further.”
I was confused, I checked the rootChecker and it clearly said the same thing. No root access.
So, I searched the web again and I was told that if I remove some files like su and one more file (I don’t exactly remember the name) then my device will be unrooted. I donloaded the es file explorer but didn’t find those files.
I searched the internet again and found something new. If I reset my device, then the root will go away. I was very happy. I did a factory reset of my device and this time I didn’t check the banking app, I did one more thing which I was not supposed to.
Ultra problem phase:
I got to the fastboot mode using the same commands in the adb terminal and decided to lock the bootloader. I thought that the app had detected that my bootloader was locked so that may be the reason it was not working. I gave the command:
fastboot flash lock
(it was something like this, I don't quite remember)
I confirmed that I wanted to lock my bootloader.
And that led me to my doom.
I rebooted my device using the command.
My device never started.
After the logo, or to say while booting I was shown this error:
"The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer care to fix it."
Then I though maybe I could just download the original boot and recovery file again then it would be all fine. I have those files and everything, when now I try to give those commands, they just show "Waiting for device...." Moreover the computer doesn't detect my device. The only thing I can do is just go to recovery mode.
Guys, I told you all everything that I knew please give me a detailed solution to the problem. I am also attaching some images so that you can see what exactly has happened.
Thanks in advance.
{
"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"
}
Sorry to say, but ... flashing unofficial/custom firmware and rooting has risk of bricking your device. And locking the bootloader was not the right/, best option
Maybe you have a chance to get it working again by flashing a complete firmware to it. Hopefully it will be successful after locking the bootloader
I have an Oppo A51w (Oppo Mirror 5) that I just reset to factory settings, out of nowhere when I restared the phone after that it shows encryption unsuccessful, and a reset phone button, which I couldn't press.
Going into ColorOS recovery mode, I tried wiping data and cache, but wiping data doesn't work because it says I have no space it needs at least 250mb, but I remember the phone does have plenty of space, more than 7gbs, so I don't get why it shows that.
As for fastboot mode it doesn't really do anything other than show its starting logo and text and it turns off? Is there anything else I'm supposed to do I'm not sure?
Anything I could do to get past the encryption screen? I don't mind having to fully reset the phone or flash it but I might need a guide.
There is also an install from sd option in the recovery mode, if somehow it can be fixed from there then please help me with that.
The android version is 5.1.1 and ColorOS 2.1.0i
The version that shows on the ColorOS recovery is 1.2
Android 5.1 is too old. I am not sure which fastboot commands are supported for this version but you can try this even if Fastboot works for few seconds.
fastboot -w
fastboot erase userdata
If the fastboot method does not work then you need to find a MSM Download tool and correct firmware for your device model and flash it.
NextGenMagisk said:
Android 5.1 is too old. I am not sure which fastboot commands are supported for this version but you can try this even if Fastboot works for few seconds.
fastboot -w
fastboot erase userdata
If the fastboot method does not work then you need to find a MSM Download tool and correct firmware for your device model and flash it.
Click to expand...
Click to collapse
Does this need USB debugging? I don't have it enabled and can't enable it because I can't get past the encryption screen.
I tried using MSM download tool but for some reason it won't detect my phone and I'm not sure which usb driver to use and how to install it.
The phone also isn't rooted.
Update:
The phone is now stuck on boot loop. I tried to flash it from sd card using stock rom from the official website, without wiping data first because it wasn't possible (needs 250mb of storage space even though there IS enough free space). It said it was successful, but after rebooting it just gets stuck on boot loop.
- for adb I'd need usb debugging? Which can't be enabled
- the phone isn't rooted, so no cwm
- msm download tool I tried, v4 and v5 doesn't work it says "Packed image not exist" but v1.6.7 does? except even it won't detect the phone, and the rom that i downloaded for that from a different source had different phone model options which i do not recognize (oppo15008.bin etc and rawprogram0_MSM_15070.xml) so I'm not sure which one to choose. Maybe I haven't installed the driver but I don't know which to install and how to.
I really have no experience with this and just tried different guides on the internet to get the phone working. For now I don't know what to do. Any help is appreciated.
Your device seems to have Qualcomm chipset so it can be repaired in the EDL mode (9008). Search google "unbrick oppo a51w". It will give you all info you need to fix this.
If your device is not detected even after installing correct drivers, then you need to use Test Point method (shorting JTAG pins) to access EDL mode. This step needs expertise to short correct pins, if your attempts fail then your best option is the Oppo service center.
NextGenMagisk said:
Your device seems to have Qualcomm chipset so it can be repaired in the EDL mode (9008). Search google "unbrick oppo a51w". It will give you all info you need to fix this.
If your device is not detected even after installing correct drivers, then you need to use Test Point method (shorting JTAG pins) to access EDL mode. This step needs expertise to short correct pins, if your attempts fail then your best option is the Oppo service center.
Click to expand...
Click to collapse
I searched and I seem to have tried following steps like this before and it didn't detect my phone even with Qualcomm driver installed, also didn't know which phone model mine is and I'm supposed to choose between these, how do I know?
{
"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"
}
southeeast said:
I searched and I seem to have tried following steps like this before and it didn't detect my phone even with Qualcomm driver installed, also didn't know which phone model mine is and I'm supposed to choose between these, how do I know?
Click to expand...
Click to collapse
Sorry, I cannot help with selection of firmware.
Is there any reason why you can't get this repaired in the Oppo service center?
disclaimer - sorry i really have no idea what i am doing and my goal is to just go back to my normal phone
my phone is poco f1 and now i can only access fastboot and this "powered by android" screen. fastboot into twrp doesnt work because of "boot command is not allowed in lock state" error
hello all so i tried rooting my phone and then realized that its going really badly (i have a more details about it down) so i decided to flash stock rom using techno treatment's tutorial on it but along the way i have faced a couple of problems - when trying to install drivers, program crashes, and others below
first time i flashed i got an error (timeout error in logs) , so i tried to flash again but this time i left it open for some time (at around 500 seconds i pressed flash again, in logs it shows that flashing already started) and when i came back it was at 12000 seconds still flashing so i closed miflash and am flashing once again but with a shorter folder path (desktop\xiaomi\firmware).
after this i deleted 2 lines in flash_all.bat because i kept getting stuck on echo mismatching image and device. after this everytime i try to flash i get this error - error:Erasing 'boot' FAILED (remote: 'Erase is not allowed in Lock State')
and also error:Erasing 'boot' FAILED (remote: 'Erase is not allowed in Lock State') in the other log file
and after this i tried to go into fastboot but noticed that the fastboot logo is different, it was a bunny with a hat repairing android robot but now it is android robot repairing itself
{
"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"
}
(this is what it looks now)
what i did before flashing stock - sorry my memory isnt the best this is all in a span of around 5 hours and my phone is pocophone f1. so at first i followed munchys tutorial on how to root, i succesfully enabled bootloader then in twrp i flashed recovery with some errors like failed to mount /system and 3 others like this but i ignored and continued then i installed magisk and after that in the video he goes into his phone no problem but i had "no os" and i think i just clicked around like backing up, restoring and wiping. then i thought i need a rom because its an os right? so i installed lineage and that was the last time when i could put files into my phone through usb. then i flashed the zip and after that rebooted and got "cant load android system, your data may be corrupt" so i pressed format something like that and did it a few times (i think this is when i couldnt put my files) until eventually saw that its no use so i went back to twrp and again clicked around until eventually wiping everything now i have no os and i cant transfer anything through usb.
Hi @medioqre
Seems like you are in locked bootloader state. You can not flash any ROM with locked bootloader unless you are enter EDL mode. See youtube tutorial to access edl mode for Beryllium
khusika said:
Hi @medioqre
Seems like you are in locked bootloader state. You can not flash any ROM with locked bootloader unless you are enter EDL mode. See youtube tutorial to access edl mode for Beryllium
Click to expand...
Click to collapse
Hi, to confirm - entering edl mode requires me to open up my phone right? how would i do that and how would i close it up after?
Thank you!
medioqre said:
Hi, to confirm - entering edl mode requires me to open up my phone right? how would i do that and how would i close it up after?
Thank you!
Click to expand...
Click to collapse
That's right, but i recommend go to the service center if you aren't able to do it.
khusika said:
That's right, but i recommend go to the service center if you aren't able to do it.
Click to expand...
Click to collapse
Hi again, its been 10 days.
so i have not went to a service center yet, because my city is too small for that. But i have a question. i didnt do anything else with my phone but today i decided i could do something and i booted it and i found out i can access fastboot mode and recovery mode, and in here i can see -
main menu, mi-recovery 3.0
and this one option
"connect with miassistant" which just gives me a picture of a phone if its plugged or unplugged with usb and under theres is a link to this website pcsuite.mi.com which doesnt work.
does this change my situation?
medioqre said:
Hi again, its been 10 days.
so i have not went to a service center yet, because my city is too small for that. But i have a question. i didnt do anything else with my phone but today i decided i could do something and i booted it and i found out i can access fastboot mode and recovery mode, and in here i can see -
main menu, mi-recovery 3.0
and this one option
"connect with miassistant" which just gives me a picture of a phone if its plugged or unplugged with usb and under theres is a link to this website pcsuite.mi.com which doesnt work.
does this change my situation?
Click to expand...
Click to collapse
If you are still in locked bootloader, you can't write firmware through fastboot or recovery
Why don't you try unlocking the bootloader officially?