Related
I've seen a lot of threads about this but they only have solutions for a bricked merlin with a fastboot. I've also seen a fix using sp flash tool using no auth da but they don't seem to work now. Is there a solution for this?
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
If you got bootloop after flashed TWRP, you need to flash stock rom recovery.img.
If you got bootloop (or black screen) after flashed misc partition, you need to erase misc partition.
If it keeps restarting, you've made any wrong modification. You need to follow your steps back and try to unmake your modification.
If you can't enter in fastboot mode or recovery mode, you need to flash stock rom using sp flash tool.
If you are using V12.0.4.0 or lower, you can flash without EDL and authentication.
If you are using V12.0.5.0 or higher, you need EDL and authentication for flashing.
If you are using V12.0.5.0 or higher, TWRP will not work.
If you want to use sp flash tool, you need to flash the stock rom preloader using V12.0.4.0 (or lower). (It will works perfectly with lower preloader binary version).
With an older preloader version, your phone will can receive DA files and accept flashing with NO auth.
Everything you need to do is plug your phone in usb (without press any key, if you press any key it will enter in EDL mode and requests authenticaion).
Here, are PRELOADER binaries for flashing: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4221081/
Here, are DA files for flashing using flash tool: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4209767/
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Oh wait, how can I make my pc recognize my redmi note 9 without pressing any keys and how can i use the preloaders? anyway thankyou for this sir.
CruisaderX said:
Oh wait, how can I make my pc recognize my redmi note 9 without pressing any keys and how can i use the preloaders? anyway thankyou for this sir.
Click to expand...
Click to collapse
So easy.
Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223089/
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
So easy.
Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223089/
Click to expand...
Click to collapse
My phone is not shutting down, should I remove the batteries? It continuously just looping and my pc nor sp flashtool can't detect it.
CruisaderX said:
My phone is not shutting down, should I remove the batteries? It continuously just looping and my pc nor sp flashtool can't detect it.
Click to expand...
Click to collapse
If you are using V12.0.5.0 or higher, you need EDL and authentication for flashing.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
If you are using V12.0.5.0 or higher, you need EDL and authentication for flashing.
Click to expand...
Click to collapse
I am using 12.0.04 sir.
CruisaderX said:
I am using 12.0.04 sir.
Click to expand...
Click to collapse
Try another cable.
Try USB3.0.
Try USB2.0.
TRY EVERYTHING YOU CAN.
If your pc can't detect your device, probably you need to install appropriate usb drivers.
Try this: https://androidmtk.com/download-mtk-usb-all-drivers
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
Try another cable.
Try USB3.0.
Try USB2.0.
TRY EVERYTHING YOU CAN.
If your pc can't detect your device, probably you need to install appropriate usb drivers.
Try this: https://androidmtk.com/download-mtk-usb-all-drivers
Click to expand...
Click to collapse
I tried but it can only be detected if I press the vol - button which gives brom error. Im losing hope :<
CruisaderX said:
I tried but it can only be detected if I press the vol - button which gives brom error. Im losing hope :<
Click to expand...
Click to collapse
If your pc can detect your phone with vol - button, everything is fine.
And you are NOT on V12.0.4.0.
Brom error means your bootloader will accept flashing in EDL mode only.
For use sp flash tool V12.0.5.0 or higher, you will need an authorized account for flashing in EDL mode.
You need to go the service centre for professional assistance.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
If your pc can detect your phone with vol - button, everything is fine.
And you are NOT on V12.0.4.0.
Brom error means your bootloader will accept flashing in EDL mode only.
For use sp flash tool V12.0.5.0 or higher, you will need an authorized account for flashing in EDL mode.
You need to go the service centre for professional assistance.
Click to expand...
Click to collapse
Does that mean I can't fix it alone? Oh my... any way thank you sir.
CruisaderX said:
Does that mean I can't fix it alone? Oh my... any way thank you sir.
Click to expand...
Click to collapse
Unhappy, yes.
Please, read this: https://www.xda-developers.com/xiaomi-edl-unbrick-authorized-mi-accounts/
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Try with MTK Exploit tutorial.... this will help u...
[GUIDE] How to bypass authentication and flash in EDL with NO auth for FREE
Thanks to: chaosmaster / k4y0z: GitHub / XDA xyzz / xyz`: GitHub / XDA Dinolek: GitHub / XDA How to install: 1. Download the attached file: VD171_MTK-bypass.zip. 2. Extract the file and open the folder. 3. Run and install python...
forum.xda-developers.com
Hey everyone, I no longer have this device, but, I guarantee that these steps will work and not brick your device if you follow them correctly!
PC side:-
1) Download the latest OTA update of android 10 for the Nokia 1 from here
https://android.googleapis.com/packages/ota-api/package/8f064e008ca0bb6616e4506f9c9c0f1d68257347.zip
2) Extract this file and you should see quite a few images, then copy the boot.img to your desktop for safety
Nokia 1 side:-
1) Update your Nokia 1 to the latest os either from the system update in settings or just copy over the .zip file we downloaded to a micro sd and apply the update from recovery
2) after you are on the latest update and no other updates are available, download the magisk canary apk from magisk GitHub and then install it
3) After that, copy the boot image we extracted earlier from the pc to the phone, then patch the copied boot image
4) After it's done flashing copy the patched image (from Downloads) to your pc
5)
PC side:-
1) Load any of the scatter files you have for the Nokia 1, the one from the stock rom is recommended
2) Load it in SP Flash tools
3) After that uncheck everything except the boot partition to be flashed
4) You will see a path of where the stock boot image is loaded from, if you click on it, a window will open asking you to select the boot image
5) select the patched boot image we copied to the pc earlier
and clock select
6) then click on the download button
Nokia 1 Side:-
1) Hold both volume up and volume down buttons together and connect it to your PC
PC side:-
1) It will begin flashing the boot image and will display a success message
Nokia 1 side:-
After it flashes successfully turn your device on and open magisk app, there it should say that magisk is installed
Credits to @GuyGotMadNameGame for the inspiration!
Reserved
Reserved!
Method mentioned in the OP worked 100% for me! Thanks for the amazing tip
I got hold of a discarded device and got it up running. Most of the above mentioned steps I could follow. Problem I have is that the download from the SP tool does not start. I think the exact steps for success must be slightliy different since somewhere else the method to bring the device into "download mode" is pressing volume-up and power simultaneously, not volume-up and volume-down.
What I did and what seems approximately the method for MTK devices is to power down the device and after pressing download in the SP tool to connect the device via USB. But it didn't start.
What could be wrong? Are there perhaps other prerequisites to fulfil, like unlocked bootloader? I was not yet able to achive that either.
linuxteddy said:
I got hold of a discarded device and got it up running. Most of the above mentioned steps I could follow. Problem I have is that the download from the SP tool does not start. I think the exact steps for success must be slightliy different since somewhere else the method to bring the device into "download mode" is pressing volume-up and power simultaneously, not volume-up and volume-down.
What I did and what seems approximately the method for MTK devices is to power down the device and after pressing download in the SP tool to connect the device via USB. But it didn't start.
What could be wrong? Are there perhaps other prerequisites to fulfil, like unlocked bootloader? I was not yet able to achive that either.
Click to expand...
Click to collapse
You need to have MTK USB drivers on your pc, and, I always held down volume up+down while device was fully off and then connected cable and it worked for me, not sure why it isn't working for your device
Hausemaster said:
You need to have MTK USB drivers on your pc, and, I always held down volume up+down while device was fully off and then connected cable and it worked for me, not sure why it isn't working for your device
Click to expand...
Click to collapse
Yeah, works better now. MTK drivers are included in Linux currently, but I needed to add my user to group dialout. Then the pressing of vol up and down worked.
I need to work out why the device told me at boot time that the verification failed (red state). I will try again, with option "keep forced encryption" off in Magisk.
linuxteddy said:
Yeah, works better now. MTK drivers are included in Linux currently, but I needed to add my user to group dialout. Then the pressing of vol up and down worked.
I need to work out why the device told me at boot time that the verification failed (red state). I will try again, with option "keep forced encryption" off in Magisk.
Click to expand...
Click to collapse
Hmm that shouldn't be happening, are you on latest firmware on your Nokia 1? As the boot.img from the link is for the latest Android 10 build
Hausemaster said:
Hmm that shouldn't be happening, are you on latest firmware on your Nokia 1? As the boot.img from the link is for the latest Android 10 build
Click to expand...
Click to collapse
Yes, the device is on the latest FW. Funny is, that after the failure I flashed the boot.img from the link, and the device boots again. That's prove, that the boot.img fits as well as the flashing procedure is working. The only culprit possible seems to be Magisk patching the boot.img.
What about the instructions given here: https://forum.xda-developers.com/t/unlocking-rooting-nokia-1-stock-rom-guide.3832230/post-77399813 ? I tried to unlock the bootloader, and it went as far as the command "fastboot oem key <md5>". Is it possible that it tampered the system? I could not unlock since the option in the developer settings is greyed out.
linuxteddy said:
Yes, the device is on the latest FW. Funny is, that after the failure I flashed the boot.img from the link, and the device boots again. That's prove, that the boot.img fits as well as the flashing procedure is working. The only culprit possible seems to be Magisk patching the boot.img.
What about the instructions given here: https://forum.xda-developers.com/t/unlocking-rooting-nokia-1-stock-rom-guide.3832230/post-77399813 ? I tried to unlock the bootloader, and it went as far as the command "fastboot oem key <md5>". Is it possible that it tampered the system? I could not unlock since the option in the developer settings is greyed out.
Click to expand...
Click to collapse
Did you try using both magisk canary and stable, also don't use mtp to transfer boot images, it damages them sometimes, also, don't unlock bootloader it worked fine when I did it with a locked bootloader for me...
Hausemaster said:
Did you try using both magisk canary and stable, also don't use mtp to transfer boot images, it damages them sometimes, also, don't unlock bootloader it worked fine when I did it with a locked bootloader for me...
Click to expand...
Click to collapse
I will try to use both. But how disable mtp? Do I need to transfer by SD card or cloud, bluetooth even?
linuxteddy said:
I will try to use both. But how disable mtp? Do I need to transfer by SD card or cloud, bluetooth even?
Click to expand...
Click to collapse
Transfer by Sd card is the safest
Hausemaster said:
Transfer by Sd card is the safest
Click to expand...
Click to collapse
I decided to md5-check the boot.img (patched an unpatched), and it all matches between PC and device. Therefore, I tried the Magisk 24.2 version (from stable) instead of the 24.3 canary. And now: It works.
Thanx a lot!
linuxteddy said:
I decided to md5-check the boot.img (patched an unpatched), and it all matches between PC and device. Therefore, I tried the Magisk 24.2 version (from stable) instead of the 24.3 canary. And now: It works.
Thanx a lot!
Click to expand...
Click to collapse
No problem, hope you have fun!
My Phone is bricked during the updation with fastboot enhance tool so now my phone is in powerd off state not working with button combination even no detection with my laptop please help me if anyone have or know the solution
Well i can maybe suggest you this there is a lot of help in this group if you need too maybe they can find out a solution for you
┤Mod Edit├┤Telegram link removed as it did not meet posting requirements├
Khalid Ghouri said:
My Phone is bricked during the updation with fastboot enhance tool so now my phone is in powerd off state not working with button combination even no detection with my laptop please help me if anyone have or know the solution
Click to expand...
Click to collapse
i have same problem
Khalid Ghouri said:
My Phone is bricked during the updation with fastboot enhance tool so now my phone is in powerd off state not working with button combination even no detection with my laptop please help me if anyone have or know the solution
Click to expand...
Click to collapse
What happened where did it go wrong?
Johnstan725 said:
What happened where did it go wrong?
Click to expand...
Click to collapse
when flash payload.bin, i got an error ''the following partition to flash may be unknown'' than i check the option ''ignor unknown partitions'' after complete the flashing payload.bin my phone bricked and no battery life !
Well I want to help so I copied and paste Theo from the oneplus 10 pro group on telegram what i posted here i hope this tutorial might help you
I didn't make this tutorial so if this works join the group and thank @docnok63 i don't know if this is also his XDA name if so then you can thank him on XDA
With an unlocked bootloader, Fastboot Enhance allows you to flash stock OOS without relocking the bootloader like MSM. It can also be used to downgrade your OS without losing data. To use it, download it from Github and:
1) Put the phone in fastboot mode and connect to PC
2) Launch the Fastboot Enhance app and double-click your connected device
3) Click the “Reboot to Fastbootd” button
4) Once in fastbootd, click the Flash Payload.bin button. If you get a warning about cow files, ignore and hit the Yes button
5) Select the FULL OTA.zip of your choice (incremental patches not allowed.)
6) The app will extract the payload.bin from the full zip and begin flashing automatically. Do NOT touch your device or close the app during this time or you risk bricking your device
7) Once done flashing, you will get a “Operation completed” dialogue box. Hit Okay and then hit the “Reboot to System” button. Profit.
HessNL said:
Well I want to help so I copied and paste Theo from the oneplus 10 pro group on telegram what i posted here i hope this tutorial might help you
I didn't make this tutorial so if this works join the group and thank @docnok63 i don't know if this is also his XDA name if so then you can thank him on XDA
With an unlocked bootloader, Fastboot Enhance allows you to flash stock OOS without relocking the bootloader like MSM. It can also be used to downgrade your OS without losing data. To use it, download it from Github and:
1) Put the phone in fastboot mode and connect to PC
2) Launch the Fastboot Enhance app and double-click your connected device
3) Click the “Reboot to Fastbootd” button
4) Once in fastbootd, click the Flash Payload.bin button. If you get a warning about cow files, ignore and hit the Yes button
5) Select the FULL OTA.zip of your choice (incremental patches not allowed.)
6) The app will extract the payload.bin from the full zip and begin flashing automatically. Do NOT touch your device or close the app during this time or you risk bricking your device
7) Once done flashing, you will get a “Operation completed” dialogue box. Hit Okay and then hit the “Reboot to System” button. Profit.
Click to expand...
Click to collapse
1) Put the phone in fastboot mode and connect to PC
First step is not possible for me because my phone completely turned off no option work for me, no pc detection and no any button combination to putting in fastboot mode or etc.....
Khalid Ghouri said:
1) Put the phone in fastboot mode and connect to PC
First step is not possible for me because my phone completely turned off no option work for me, no pc detection and no any button combination to putting in fastboot mode or etc.....
Click to expand...
Click to collapse
Did you install the drivers correctly because we have some drivers in the telegram group who are working properly i couldn't even find my device 9 pro with msm until I had those drivers maybe that's the problem to but I don't know I wish I could help you further i also placed your problem in the telegram and they want to help you but then you need to explain the steps you did
HessNL said:
Did you install the drivers correctly because we have some drivers in the telegram group who are working properly i couldn't even find my device 9 pro with msm until I had those drivers maybe that's the problem to but I don't know I wish I could help you further i also placed your problem in the telegram and they want to help you but then you need to explain the steps you did
Click to expand...
Click to collapse
can you please send me the driver link which is there telegram group
steps which i did
1. unlock the bootloader successfully
2. download the indian version android 12 and extract the payload.bin file
3. flash payload.bin file with fastboot enhance tool after complete the flash process device reboot and its happen for me
Khalid Ghouri said:
steps which i did
1. unlock the bootloader successfully
2. download the indian version android 12 and extract the payload.bin file
3. flash payload.bin file with fastboot enhance tool after complete the flash process device reboot and its happen for me
Click to expand...
Click to collapse
You didn't have to unpack the file you could can flash it with the zip file it fastboot enhance unpacks it self but i can't share you the drivers there already there downloaded i could download then and send then to you
I copied and paste this from the group there it's they are download links
OnePlus USB (all purpose/data transfer):
OnePlus-USB-Drivers.zip
drive.google.com
Google USB driver (for fastboot & ADB):
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Qualcomm drivers (for MSM):
Qualcomm_Drivers_Setup.exe
drive.google.com
Khalid Ghouri said:
steps which i did
1. unlock the bootloader successfully
2. download the indian version android 12 and extract the payload.bin file
3. flash payload.bin file with fastboot enhance tool after complete the flash process device reboot and its happen for me
Click to expand...
Click to collapse
same happened here without extracting payload.bin before
Same here No way on earth to turn the Phone on in any way!
i think its perma bricked
OnePlus picked up my phone. Looking forward to their reply
My phone also brick.
I also try payload.bin in fastboot enhanced tool.
Completely done.
Now my phone is not turning on.
No pc connect.
No charging connect.
No power on.
Anyone can help me.??
Zeescorpion said:
My phone also brick.
I also try payload.bin in fastboot enhanced tool.
Completely done.
Now my phone is not turning on.
No pc connect.
No charging connect.
No power on.
Anyone can help me.??
Click to expand...
Click to collapse
Nobody knows what the problem is. you are not the only one. No solution yet
Is that somebody that know a link to download that some is now.
Im not coming in in my phone, no usb
How could i start usb-dubugging on my phone??
zelma83 said:
Im not coming in in my phone, no usb
How could i start usb-dubugging on my phone??
Click to expand...
Click to collapse
Hey are you still having problems? Do you have a windows device to troubleshoot with?
I know you had a Mac before.
What state is your phone currently in? Still unable to boot?
You can force your phone off by holding the power button and both volume keys for an extended period of time, the phone will vibrate when it does, from then just hold down and power until it powers on, it may take a few seconds but it'll land you on a black page with recovery as one of the options, once in recovery choose from the 3 language options, from here with the up and down vol keys and power you should be able to wipe your system and recovery your phone, you will lose the content but this should work.
The only other option is to boot to the bootloader then use fastboot commands to put the OS back, or use fastboot enhance.
I tried installing crDroid (unlock bootloader, uploaded FW, recovery SHRP, then install ROM) and after reboot the phone would go back to recovery.
By mistake I "installed" SHRP from ZIP package (I thought I need to install latest recovery file to install ROM with android 12) and phone went into reboot loop, I can't do anything, any key combination doesn't help - I can't even turn it off.
help!
I opened the phone, disconnected the battery, but nothing happened - still bootloop
I'm planning to use SP Flash Tool
Immediately after connecting USB C, the phone boots into bootlop (after disconnecting and reconnecting the battery)
What happens when you flash the custom ROM?
Try to flash the stock firmware and miui
again. Download the latest miui recovery ROM for Lancelot and copy it to the sd card. If you can still boot into recovery you can connect the phone with a PC.
You can also try to reboot into bootloader if the reboot options work from sharp, if not connect the phone to a PC with adb and fastboot installed on it and type:
Code:
adb reboot bootloader
And now if you are in fastboot you can do anything, you can try to reflash the firmware, recovery etc.
I personally don't use SHRP, it was really buggy and not great. I use the twrp from this link: https://forum.xda-developers.com/t/recovery-twrp-unofficial-twrp-recovery-3-6-1_11-0.4421301/.
Thanks for reading and I hope u succeed,
Bye.
U can also try to flash it with MI flash tool.
Sergij-SApcPro said:
What happens when you flash the custom ROM?
Click to expand...
Click to collapse
Operation completed with status [ ]. It looks like there should be a * in the middle and then it would be a sign to me that the ROM is loaded.
Sergij-SApcPro said:
Try to flash the stock firmware and miui
again. Download the latest miui recovery ROM for Lancelot and copy it to the sd card. If you can still boot into recovery you can connect the phone with a PC.
Click to expand...
Click to collapse
At the time of writing, no key combination was working - I can't get into Fastboot or Recovery. I let the battery run out for that moment.
Sergij-SApcPro said:
You can also try to reboot into bootloader if the reboot options work from sharp, if not connect the phone to a PC with adb and fastboot installed on it and type:
Code:
adb reboot bootloader
And now if you are in fastboot you can do anything, you can try to reflash the firmware, recovery etc.
I personally don't use SHRP, it was really buggy and not great. I use the twrp from this link: https://forum.xda-developers.com/t/recovery-twrp-unofficial-twrp-recovery-3-6-1_11-0.4421301/.
Thanks for reading and I hope u succeed,
Bye.
Click to expand...
Click to collapse
Sergij-SApcPro said:
U can also try to flash it with MI flash tool.
Click to expand...
Click to collapse
That's what I'll do first, then move on to the solution below.
I opened the phone and disconnected the battery, but plugging in the USB cable immediately turns the phone on and bootloops again.
I'm using Linux and Windows, and one user hinted at hacking the USB driver so I believe it won't boot the phone, only then will I have communication? Other than that I don't know how to do it anyway.
For now, after the phone's battery runs out, I'll try with this solution
MTK Authorisation Bypass
Thanks to Dinolek ErdilS xyzz **All Steps Are Mandatory, Don't Skip Any Of Them** How to install: 1. Download the attached file: Alternate Download:https://anonfiles.com/l0yeSfD2u7/MTK-Bypass_zipAlternate Download:https://dl.uploadgram.me/6126628127c5fh?raw 2. Extract the file and open the...
telegra.ph
I've exhausted the battery, Mi Flash needs Fastboot, which I don't have.
I used
Deleted Account in Redmi Note 9 / Redmi 9 / 10X 4G Community
• Unbrick method for basically any device covered in this group. - Download SP Flash Tool from here. - Download the corresponding Engineering ROM for your device using #engrom - Download this zip and extract it. You Should find a DA file and an auth file in it. - Do the steps in this video...
t.me
I got to the point of connecting the phone to the computer and it connects (the procedure says to use the Power button, but I had to disconnect the battery because Bootloop was falling in), using the Vol- button - the phone keeps connecting and disconnecting....
For a while I tried to connect the phone via SP Flash under Linux - in administrator mode the message "memory protection violation" appears (I don't know how the message is in English).
Adding a udev exception was supposed to help - after lsusb the Mediatek device appeared, I added the exception, restarted - and the same thing happens (the program crashes).
I finally managed (with the help of a group on telegram https://t.me/HelioG85_Unified) by switching off the phone and carefully going through all the points (except the update at the very end) from this link
MTK Authorisation Bypass
Thanks to Dinolek ErdilS xyzz **All Steps Are Mandatory, Don't Skip Any Of Them** How to install: 1. Download the attached file: Alternate Download:https://anonfiles.com/l0yeSfD2u7/MTK-Bypass_zipAlternate Download:https://dl.uploadgram.me/6126628127c5fh?raw 2. Extract the file and open the...
telegra.ph
There is a little problem, because SP Flash must be from the link in this post (because it will not fit DA)
Deleted Account in Redmi Note 9 / Redmi 9 / 10X 4G Community
• Unbrick method for basically any device covered in this group. - Download SP Flash Tool from here. - Download the corresponding Engineering ROM for your device using #engrom - Download this zip and extract it. You Should find a DA file and an auth file in it. - Do the steps in this video...
t.me
Wow so many posts... Did you manage to fix the phone now? What do you mean by SP Flash will not fit the DA? Did you download the eng ROM for Lancelot? BTW I haven't done this kind of thing, but when I tried to flash my Lancelot with SP Flash tool it didn't work, because it was just waiting for device.
Sergij-SApcPro said:
Wow so many posts...
Click to expand...
Click to collapse
Often when reading threads I see "managed to fix, thanks!" but it doesn't say what and how, so that's why so many posts - so someone knows what was going on.
Sergij-SApcPro said:
Did you manage to fix the phone now?
Click to expand...
Click to collapse
Yes
Sergij-SApcPro said:
What do you mean by SP Flash will not fit the DA?
Click to expand...
Click to collapse
Other versions of SP Flash (newer) other than in the package with ENGROM didn't work with DA file with manual from links given above - it had to be the one from the package. SP Flash showed errors and crashed or informed about wrong file.
Sergij-SApcPro said:
Did you download the eng ROM for Lancelot?
Click to expand...
Click to collapse
Yes
Sergij-SApcPro said:
BTW I haven't done this kind of thing, but when I tried to flash my Lancelot with SP Flash tool it didn't work, because it was just waiting for device.
Click to expand...
Click to collapse
I think that if you go through the MTK Bypass process carefully, step by step, you may succeed, as I did.
Great to hear that you fixed the phone, congratulations!
TomekParuszewski said:
I think that if you go through the MTK Bypass process carefully, step by step, you may succeed, as I did.
Click to expand...
Click to collapse
Thanks for the info, but I don't need to flash it with SP Flash tool because that was earlier when I didn't try to install custom recovery. Now I have SHRP with CRDroid A12 and its Awesome.
Thanks for reading,
Bye
TomekParuszewski said:
Often when reading threads I see "managed to fix, thanks!" but it doesn't say what and how, so that's why so many posts - so someone knows what was going on.
Yes
Other versions of SP Flash (newer) other than in the package with ENGROM didn't work with DA file with manual from links given above - it had to be the one from the package. SP Flash showed errors and crashed or informed about wrong file.
Yes
I think that if you go through the MTK Bypass process carefully, step by step, you may succeed, as I did.
Click to expand...
Click to collapse
What version of SP Flash tools did you use? I'm running into this (status_ext_ram_exception error) kind of error while trying to flash the firmware provided in the Telegram channel.
SandShadow said:
What version of SP Flash tools did you use? I'm running into this (status_ext_ram_exception error) kind of error while trying to flash the firmware provided in the Telegram channel.
Click to expand...
Click to collapse
yes, im stuck at same error. any ideas? someone said we should let the phone completely discharge, im waiting on that, but just incase any other ideas...
voland34 said:
yes, im stuck at same error. any ideas? someone said we should let the phone completely discharge, im waiting on that, but just incase any other ideas...
Click to expand...
Click to collapse
The battery trick does'nt work for me. I can't remember exact version, sorry - but my way was going BACK with SP Flash tool version (from newest to working with file). When I found right version the rest was only going with procedure.
I did it twice: first time I was scared, second - with finding right version of SPFT, every time - like walk in the park. Looong walk all procedure was like 2-3 hours.
Second one try was after trying to load Andorid 13 (2x). Don't do it kids!
After all, my Revolut app stop working lately on my phone and Redmi is retired for now... (and also becoming unusable because slowing dramatically)
Thanks for your answer. it has worked with battery empty (though that might not have benn necessary); not on 1st atttempt v5.2020 but it did with version 5v.2216 in case it might help someone...it didnt flash miui fastboot rom 12.5 but it did flash engineering rom. and from there i will twrp and miui.
Thanks for your suggestion of trying different spflash versions.
Hi there.
I wanted to root a Redmi 10S device. Bootloader was also opened. The flash went during fastboot mode, then after the fastboot reboot command, the device restarted, but it only shows "Redmi" and the word android at the bottom. I tried to access recovery and fastboot mode, but powr+volD only restarts the device and only the Redmi inscription is visible.
I don't know what they call this state in which the device is.
If there is a suitable link on the forum, I would appreciate it.
Hi there!
What did you flash excatly?
I mean, did you flash the whole phone, or just a patched boot image?
Andris85 said:
Hi there.
I wanted to root a Redmi 10S device. Bootloader was also opened. The flash went during fastboot mode, then after the fastboot reboot command, the device restarted, but it only shows "Redmi" and the word android at the bottom. I tried to access recovery and fastboot mode, but powr+volD only restarts the device and only the Redmi inscription is visible.
I don't know what they call this state in which the device is.
If there is a suitable link on the forum, I would appreciate it.
Click to expand...
Click to collapse
reflash stock and done to enter in fastboot mode press power and volD keep presing volD until the phone start in fastboot mode and flash it
gurtnyi said:
Hi there!
What did you flash excatly?
I mean, did you flash the whole phone, or just a patched boot image?
Click to expand...
Click to collapse
Just the boot.ini. but I think this would make fastboot mode work. But it's not working
tutibreaker said:
reflash stock and done to enter in fastboot mode press power and volD keep presing volD until the phone start in fastboot mode and flash it
Click to expand...
Click to collapse
What should I use to reflash? Mi flash? This is the NS
Yes... I probably mixed up the boot file in the downloads folder and not the correct received flash
Click to expand...
Click to collapse
Then, you don't have to flash the whole phone again, just flash back the original image, and try rooting with twrp and magisk zip file (rename the apk file from magisk.apk to magisk.zip, and then flash it in twrp)
If you can't install twrp, or something went wrong, take a full backup from your phone (like using google's backup service, and Miui backup--> it 'll save the backup to internal storage/miui/backup/AllBackup) and then ypu can reflash the phone with mi flash tool, but don't lock the bootloader back, and after flash, you shuold enable oem unlock in developer settings.
One quick question:
Did you enable oem unlocking in developer settings, before trying to flash the modified image?
gurtnyi said:
Then, you don't have to flash the whole phone again, just flash back the original image, and try rooting with twrp and magisk zip file (rename the apk file from magisk.apk to magisk.zip, and then flash it in twrp)
If you can't install twrp, or something went wrong, take a full backup from your phone (like using google's backup service, and Miui backup--> it 'll save the backup to internal storage/miui/backup/AllBackup) and then ypu can reflash the phone with mi flash tool, but don't lock the bootloader back, and after flash, you shuold enable oem unlock in developer settings.
One quick question:
Did you enable oem unlocking in developer settings, before trying to flash the modified image?
Click to expand...
Click to collapse
yepp, enable oem unlock. But fastbootmode is required for all operations. But fastboot mode doesn't work.
What do you mean it doesn't work?
Can't enter into fastboot mode?
gurtnyi said:
What do you mean it doesn't work?
Can't enter into fastboot mode?
Click to expand...
Click to collapse
Can't enter fastboot mode. The device only shows "Redmi" lettering. If fatboot worked, I could have done it already. power+volume down, the device just restarts and shows "redmi".
Hmm..
And if you holding the volD and power buttons together for a longer time?
Like a min, or sth
I had a similar situation, but after a few tries it went into fastboot mode
gurtnyi said:
Hmm..
And if you holding the volD and power buttons together for a longer time?
Like a min, or sth
I had a similar situation, but after a few tries it went into fastboot mode
Click to expand...
Click to collapse
it just restarts, as long as I press and hold volume down+power, if I don't press it, it just shows the redmi text
I apologise, but I 've currently ran out of ideas. If I can find any solution, I 'll post an answer about it.
gurtnyi said:
I apologise, but I 've currently ran out of ideas. If I can find any solution, I 'll post an answer about it.
Click to expand...
Click to collapse
TXH
Hi there the forgive my on my bad english and text.
The Only thing u can do is restoring the firmware by using brom mode, Look it up or follow the steps i'll give u....
First keep in mind brom works best Without the batary conected . So remove the thin cover plate at the back u can loosen it with heat , after removing the cover move all screws and remove the housing so u can disconect the batary at the mainboard .
Next u will have to install the Vcom drivers according your chipset mediatek etc.
For the Vcom drivers and install of it u can follow https://www.hovatek.com/forum/thread-16640.html
U must download or allready have a firmware file in fastboot format , Open up SP Flash tool and go to optionsd and select connection, click the w/o battery option and close it. Open your scatter file and than click on download . Insert your phone wile holding your volume down or up , with my device a redmi note 10s it was the up and down to getter for it was flashing the rom. this should flash your device back with a working fastboot and working rom.
Hope u will succeed...
Greetsss
Pegelaar_NL said:
Hi there the forgive my on my bad english and text.
The Only thing u can do is restoring the firmware by using brom mode, Look it up or follow the steps i'll give u....
First keep in mind brom works best Without the batary conected . So remove the thin cover plate at the back u can loosen it with heat , after removing the cover move all screws and remove the housing so u can disconect the batary at the mainboard .
Next u will have to install the Vcom drivers according your chipset mediatek etc.
For the Vcom drivers and install of it u can follow https://www.hovatek.com/forum/thread-16640.html
U must download or allready have a firmware file in fastboot format , Open up SP Flash tool and go to optionsd and select connection, click the w/o battery option and close it. Open your scatter file and than click on download . Insert your phone wile holding your volume down or up , with my device a redmi note 10s it was the up and down to getter for it was flashing the rom. this should flash your device back with a working fastboot and working rom.
Hope u will succeed...
Greetsss
Click to expand...
Click to collapse
Yep, this guy here 's got the point. If you can't flash with sp flash tool because auth fail, there's a method to bypass it.
You can find the tutorial here: https://www.getdroidtips.com/bypass-mediateks-sp-flash-tool-authentication-protection/
I also got some help from this guy's post, many thanks to him too.
https://forum.xda-developers.com/t/...ad_da_fail-0x7d4-2004-for-mtk-phones.3692259/
Let us know how it's going with it! ;D
I can unbrick the device at any time. There is another problem. An incorrect boot file is probably being copied. After TWRP you will never enter android again. But TWRP also only loads up to the subtitle. I tried a lot of methods. Now I will try google p ex. android and make it root.
But, if someone can recommend a device intended for gaming, but easy to root, then I will buy one
Andris85 said:
I can unbrick the device at any time. There is another problem. An incorrect boot file is probably being copied. After TWRP you will never enter android again. But TWRP also only loads up to the subtitle. I tried a lot of methods. Now I will try google p ex. android and make it root.
But, if someone can recommend a device intended for gaming, but easy to root, then I will buytoday there is a lot of devices for gaming like rog phone and red magic
Click to expand...
Click to collapse
today there is a lot of devices for gaming like rog phone and red magic, but is you are looking for a "gaming phone" in low or mid-range you are just wasting your money
Andris85 said:
I can unbrick the device at any time. There is another problem. An incorrect boot file is probably being copied. After TWRP you will never enter android again. But TWRP also only loads up to the subtitle. I tried a lot of methods. Now I will try google p ex. android and make it root.
But, if someone can recommend a device intended for gaming, but easy to root, then I will buy one
Click to expand...
Click to collapse
There's a tutorial, that helped me installing twrp correctly to this phone, I'll link my post about this.
https://forum.xda-developers.com/t/twrp-on-android-12.4522273/
tutibreaker said:
today there is a lot of devices for gaming like rog phone and red magic, but is you are looking for a "gaming phone" in low or mid-range you are just wasting your money
Click to expand...
Click to collapse
If you can root it easily, then the expensive one is good for me! Normal root was not available for typical gamer phones for years. If I buy something for which root may not be available, then I'm wasting my money...
gurtnyi said:
There's a tutorial, that helped me installing twrp correctly to this phone, I'll link my post about this.
https://forum.xda-developers.com/t/twrp-on-android-12.4522273/
Click to expand...
Click to collapse
I will look today