Well I'll be quick... So do what this video says with the files and you will have your redmi 9c alive again, I tried with hydra tool, mtk bypass and none worked but this video saved so try it.
If it works don't forget to say thanks haha
I also recommend that you don't use any kind of TWRP, they usually cause hardbricks, switch to fast boot and do everything there...
Even if it takes more work temporarily, it will cause you less headache.
It's really easy to root through fastboot and it's much safer, besides not having to format your phone, just patch the boot img through magisk, and use a vbmeta
1 -fastboot flash patched-magisk-boot.img (boot.img here)
2 -fastboot --disable-verification --disable-verification flash vbmeta (vbmeta.img here)
I'm not going to put the files, but if you look, you'll probably find it, and just follow this and it will work
Didn't work for me sadly. I have a redmi 9 activ (cattail), coudn't understand the video and the closed captions are unavailable so I tried following it visually. I downloaded the roms from xiaomi firmware updater website, all 3 available for this device, which are firmware, vendor and official. Tried to load the scatter file and on all 3 of them it keeps returning me the error STATUS_SCATTER_FILE_INVALID (-1073545215), MSP ERROE CODE: 0x00, and also tried using all 4 other flash tool versions provided on that website on the video description all of them failed.
simplydroiding said:
Didn't work for me sadly. I have a redmi 9 activ (cattail), coudn't understand the video and the closed captions are unavailable so I tried following it visually. I downloaded the roms from xiaomi firmware updater website, all 3 available for this device, which are firmware, vendor and official. Tried to load the scatter file and on all 3 of them it keeps returning me the error STATUS_SCATTER_FILE_INVALID (-1073545215), MSP ERROE CODE: 0x00, and also tried using all 4 other flash tool versions provided on that website on the video description all of them failed.
Click to expand...
Click to collapse
Are you sure that you downloaded the fastboot rom for cattail?
Here is the direct download link for the Fastboot rom for cattail - https://bigota.d.miui.com/V12.0.18....TINXM_20220826.0000.00_10.0_in_b1c7409a05.tgz
omg it was the tgz file... a format I've never seen before had no idea you could just decompress that like a .zip or .rar
I kept getting this error status_sec_img_too_large
some sources online said to disable cust
I did, it apparently flashed ok, but it still wont turn on or anything
simplydroiding said:
I kept getting this error status_sec_img_too_large
some sources online said to disable cust
I did, it apparently flashed ok, but it still wont turn on or anything
Click to expand...
Click to collapse
Can you go to fastboot mode?
Nope. No fastboot, no recovery, nothing. Only being recognized by the brom bypass and sp flash tools. Another topic on hovatek suggesting try every recovery image possible. Well, here I go try, then. Everyone available on xiaomi firmware updater website.
simplydroiding said:
Nope. No fastboot, no recovery, nothing. Only being recognized by the brom bypass and sp flash tools. Another topic on hovatek suggesting try every recovery image possible. Well, here I go try, then. Everyone available on xiaomi firmware updater website.
Click to expand...
Click to collapse
All the best
Imma sharing my experience, I recently got my cattail bricked, it came to a point where I had no choice but to believe that the device is merely dead (emmc is corrupted).
After a few days, I ended up at this post - https://www.hovatek.com/blog/my-experience-unbricking-a-dead-boot-lg-stylo-6/, and tried the command given by the OP, and my device BOOTED!
(You can get the preloader for your device by downloading the tgz file and then extracting it; inside the images/ folder)
Related
Hi my friends.
this is my story :
my phone is Redmi note 3 pro (qualqomm)
I got permissions for unlocking a week ago.
then i tried xiaomi website unlock method but it stopped at 50% and gave me couldn't verify device (different account) error.
my rom is global (MIUI 8) . then i tried to flash dev rom with updater app but it gave me couldn't verify update package error. i cleared updater data and tried again but same error.
in next step i tried mi pc suite to flash but no success.
then i used fastboot mode and mi flash and i got locked bootloader error.
then i used EDL mode to flash but in mi flash i got hello package error. (object reference not set to an instance of an object)
i completely confused . i tried all methods and read many fix like login in i.mi.com and other method that people fixed their problem but all of them not fix mine.
i read some threads about flashing twrp and root without unlocking bootloader but all of them need flashing dev rom and i can't flash.
can anyone help me?
x23are said:
Hi my friends.
this is my story :
my phone is Redmi note 3 pro (qualqomm)
I got permissions for unlocking a week ago.
then i tried xiaomi website unlock method but it stopped at 50% and gave me couldn't verify device (different account) error.
my rom is global (MIUI 8) . then i tried to flash dev rom with updater app but it gave me couldn't verify update package error. i cleared updater data and tried again but same error.
in next step i tried mi pc suite to flash but no success.
then i used fastboot mode and mi flash and i got locked bootloader error.
then i used EDL mode to flash but in mi flash i got hello package error. (object reference not set to an instance of an object)
i completely confused . i tried all methods and read many fix like login in i.mi.com and other method that people fixed their problem but all of them not fix mine.
i read some threads about flashing twrp and root without unlocking bootloader but all of them need flashing dev rom and i can't flash.
can anyone help me?
Click to expand...
Click to collapse
I just recently went through most of what you have gone through... Be patient though... It seems that the unlocking of bootloader even after you getting permission, takes atleast 2-3 weeks more.
- You can flash the miui global dev rom, you may download it from the miui forums... Here is the link for the fastboot rom http://en.miui.com/a-234.html.
- To flash the dev rom, you need to ensure you put your phone into fastboot, ensure all the fastboot drivers are installed on your computer
- Also, you need to ensure that you download the GLOBAL/DEV FASTBOOT ROM(this is different than the regular zip package) that you download.
- Then you can follow the instructions to install the ROM using miflash tool
- If the ROM installation is a success, then you just need to wait patiently atleast for 15-20 days from the time you got unlock permission sms from MI
- Then try running the flash unlock tool, it should get unlocked.
- Now flashing TWRP might be tricky, I was able to flash the official TWRP, but had issues where the internal memory wasn't getting mounted, because you keep getting asked for decryption password in TWRP to mount the data, no matter what you enter, it might not work
- After trying many TWRP types, the one that worked was "zcx twrp"
- Once you flash that, you should be able to flash any custom or miui roms you need :good:
GENiU5 said:
I just recently went through most of what you have gone through... Be patient though... It seems that the unlocking of bootloader even after you getting permission, takes atleast 2-3 weeks more.
- You can flash the miui global dev rom, you may download it from the miui forums... Here is the link for the fastboot rom http://en.miui.com/a-234.html.
- To flash the dev rom, you need to ensure you put your phone into fastboot, ensure all the fastboot drivers are installed on your computer
- Also, you need to ensure that you download the GLOBAL/DEV FASTBOOT ROM(this is different than the regular zip package) that you download.
- Then you can follow the instructions to install the ROM using miflash tool
- If the ROM installation is a success, then you just need to wait patiently atleast for 15-20 days from the time you got unlock permission sms from MI
- Then try running the flash unlock tool, it should get unlocked.
- Now flashing TWRP might be tricky, I was able to flash the official TWRP, but had issues where the internal memory wasn't getting mounted, because you keep getting asked for decryption password in TWRP to mount the data, no matter what you enter, it might not work
- After trying many TWRP types, the one that worked was "zcx twrp"
- Once you flash that, you should be able to flash any custom or miui roms you need :good:
Click to expand...
Click to collapse
tnx for reply but my problem is i cant flash.
my bootloader is locked and i cant flash fastboot rom.
therefor i must use edl mode or updater app but both of them don't work as a said in first post.
You don't need an unlocked BL to flash official fast boot miui ROMs
GENiU5 said:
You don't need an unlocked BL to flash official fast boot miui ROMs
Click to expand...
Click to collapse
mi flash show me : bootloader unlock in flashing process
x23are said:
mi flash show me : bootloader unlock in flashing process
Click to expand...
Click to collapse
You may try the steps on this link http://en.miui.com/thread-235865-1-1.html
Skip the EDL thing and go directly to the part where they explain how to use the miflash tool to flash a fastboot ROM
I should have asked this first... what's the state of your phone right now? Does it boot, stuck on boot loop, or are you able to boot into some ROM.
maybe u have a vendors rom, flash the fastboot rom using edl
finally a downloaded adb 1.4.3 and installed it and i flashed dev rom in EDL mode.
but now i have some questions:
can i change kernel with locked bootloader?
if i change kernel does fingerprint work?
You just dont have proper drivers installed im 100% sure, else it would go via edl
Hehe was right������
And why dont you ask for official unlock approval? Its approved in less than a day, anyone saying otherwise have old news
Or you can always use a method in this forum...
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
hey did you get it fixed and can you please send the link to the stock rom
yayjk said:
hey did you get it fixed and can you please send the link to the stock rom
Click to expand...
Click to collapse
TRY ASKING THE QUESTION ON THIS THREAD
https://forum.xda-developers.com/android/help/how-to-make-simple-android-apps-qna-t3776780
---------- Post added at 05:00 PM ---------- Previous post was at 05:00 PM ----------
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
TRY ASKING IN THIS THREAD
https://forum.xda-developers.com/android/help/how-to-make-simple-android-apps-qna-t3776780
How to Unbrick Lenovo K8 Plus 4GB
Hi All
I tried many stock roms and many versions of SP flash tool but none helped me to unbrick my lenovo k8 plus (4gb ram).
I was trying to downgrade it to Naugat from Oreo but it shows same error every time.
Error is (SP Flash tool version latest 5.18)
" Error_Status_Sec_Insufficient_Buffer( 0xC002004B)
[Hint]:
Verified boot is enabled.
Please download signed image (md1img-verified.img) or disable verified boot."
Plzzz help same problem
Enabled verified boot ...how to disabled
Same problem my lenovo k8plus
Enabled verified boot ...how to disabled
You need to use "Lenovo Moto Smart Assistant" instead of SPFlash tool to flash and you will be good to go. You can get the tool from the Lenovo official website.
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
Try with Lenovo Moto Smart Assistant. I too have bricked my phone... but I've successfully started my phone using this tool. you will get official signed ROM from here.
you can use LMSA tool to rescue,90% sucessfully ,don't use splashtool beacause it's many error if you choose wrong version
Had the same problem. Can confirm Lenovo's tool sucessfully recovers ohone from bricked state. A lifesaver!
Downloaded from https://lenovomobilesupport.lenovo.com/br/pt/downloads/ds101291-rescue-and-smart-assistant-lmsa
then updated to version 5.9.2.4 from inside the app itself
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Completely Bricked
Me too need a stock rom of ta 1056. Please help if you could manage to provide a helping hand... ?
I had the same issue like yours, looping in twrp. then i tried to flash it with a so called stock rom from net, guess what it went completely bricked and I donnow what to do. ??
mrabudi said:
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Click to expand...
Click to collapse
It's simple. just get the stock recovery (and boot, optional) to flash it with fastboot and go to recovery and wipe it and you'll be ok.
and also using the twrp on this phone is not a great idea to wipe.
if you wanna wipe. please use "fastboot -w" to wipe the phone while bootloader is unlocked. or stock recovery to wipe.
Because twrp built this recovery with only formatting option was ext4 to /data and /cache. So the phone cannot operate properly. Which leads to fake failed decryption notification.
Data partition must need to be formatted under f2fs format.
And finding rom for this phone is pretty easy. Just find some nb0 file for this phone (any variant of this phone should work) and extract it with "nb0 extractor" and then flash it with SP Flash tool by mediatek.
That's my way. I don't know how will you do. But normally you only need the nb0 file and then flash it with OST LA (Nokia's flash tool based off Intel's SUT L1/L3 tool).
My Nokia 1 TA-1047 stuck at Nokia logo screen
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
cuantonhonhoi said:
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
Click to expand...
Click to collapse
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047. Since it's a universal ROM so any variant of the phone can also work) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to look at line with partition "metadata" and then edit "boundary_check" to false.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
kutiz21 said:
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to hide/delete line with partition "metadata" in scatter.txt and you can flash it perfectly.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
Click to expand...
Click to collapse
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
pabloluih said:
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
Click to expand...
Click to collapse
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
kutiz21 said:
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
Click to expand...
Click to collapse
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
That's weird. If you unlocked the bootloader and install adb/fastboot (must be latest version. Older version will not recognize the phone, download platform-tools from google dev site, don't download adb tools off XDA) + Nokia's driver from emulated CD drive (every time you plug the phone to computer with official rom, you'll see it) properly then it should be able to work.
You need to check the fastboot device driver Device Manager (devmgmt.msc) and see if the driver is properly installed yet.
You can only use "fastboot -w" once the bootloader is unlocked. And booting up the phone. It will say the bootloader is in Orange state.
You need to unlock oem bootloader from developer settings when the stock rom is there. And in fastboot too
Here is how you unlock it:
Enable oem unlock from dev settings
Then reboot to fastboot mode (bootloader)
Do this:
"fastboot oem key "serial number string converted to md5, not imei strings" "
"fastboot oem unlock"
Volume up
Then you are actually unlocked the bootloader.
Unlock from developer settings only will not do the trick. It only allows you to have ability unlock the bootloader in fastboot.
If you stuck on the Encryption unsuccessful screen. Try wipe it with stock recovery or "fastboot -w" (if you properly unlocked the bootloader)
If you think you can't do anything anymore. Just flash the ROM provided you above.
If you need the extracted ROM for SP flash tool and the fastboot driver. I can link it to you.
Most of all drivers will automatically install off Windows Update if you're on Windows 10 (except the fastboot driver, and yes. SP flash tool drivers are also provided by Windows 10 too)
Also. You should update the phone to the latest software update when flashing stock rom too. Because newer builds for this phone is compatible-friendly with GSI rom (Treble ROMs like AOSP Android 9 or 8.1 by phhusson)
Updates on Android 9/10
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
Nokia might harden the security of the device so you can't use Magisk on stock rom.
After unlocking, I installed EU rom via adb, the installed unofficial TWRP 3.4.1b -0506 and rooted.
I used the phone without any probems for some days .
I then decided to get rid of MI software. After uninstalling a lot of software using App Uninstaller by Jumobile.
Also after that the phone worked well for an hour or two, but after a reboot the phone always goes into Fastboot.
I still can go into TWRP. When I try to install Curtana Global from external SD card, TWRP returns "Install zip Successful" but with an error message
"Failed to mount "/vendor" (Read-only file system)
I am very grateful for any help to unbrick my phone
Bruno
brufi said:
After unlocking, I installed EU rom via adb, the installed unofficial TWRP 3.4.1b -0506 and rooted.
I used the phone without any probems for some days .
I then decided to get rid of MI software. After uninstalling a lot of software using App Uninstaller by Jumobile.
Also after that the phone worked well for an hour or two, but after a reboot the phone always goes into Fastboot.
I still can go into TWRP. When I try to install Curtana Global from external SD card, TWRP returns "Install zip Successful" but with an error message
"Failed to mount "/vendor" (Read-only file system)
I am very grateful for any help to unbrick my phone
Bruno
Click to expand...
Click to collapse
Hello
Why not to flash a fastboot rom via Miflash? Phone will be from clean basis.
Test the new Miflashpro if you have time.
Good luck.
Note 9S not yet listed in Miflashpro; fastboot rom not found
thanks Lolo93939 for the input.
I found miflashpro under a com domain with the same name and installed the most recent version 4.3.1220.29. Selection of device does not include Redmi Not 9 S or Pro, accordingly moflashpro can not be used as of today for note 9S.
I then downloaded XIAOMIFlashTool from the com domain of the same name: miflash20191206.zip and installed
Downloaded latest fastboot rom from mifirm net / model / curtana.ttt which is V11.0.7.0.QJWMIXM.
unziped the rom 2 times until I had a folder with subfolder "Images" and shortened the folder name to V11.0.7.0.QJWMIXM and copied it under new folder c:XIAOMI
Executed XiaoMIFlash.exe, selected V11.0.7.0.QJWMIXM folder, selected "clean all" at bottom (to make sure the device is not locked again), then connected phone in Fastboot screen, refreshed in XiaoMiFlash and flashed.
Flash ended with error but phone seems to be up and running again.
brufi said:
Lolo93939, i would love too. I have searched for 3 hours now and did not find a functioning Miflash. I tried the 2 latest versions from xiaomiflash com but both give out an error "could not find flash script."
I find Stable roms for curtana but all links to fastboot roms end in 404 pages.
Could you point me to source of Miflash and a fastboot rom?
Thanks a lot!
Click to expand...
Click to collapse
It doesn't find your computer path for stating flashing.
Did you unzip the tgz and the tar file?
Place the unzipped result close to your computer C: directory and clean as much as possible the name.
That MUST work...
https://mirom.ezbox.idv.tw/en/phone/curtana/
Thank you! I did as suggested.
all worked well, but got
error: not catch checkpoint (\$fastoot -s . *lock).flash is not done
still the phone is up and running again, so things seem to be good.
:good:
brufi said:
Thank you! I did as suggested.
all worked well, but got
error: not catch checkpoint (\$fastoot -s . *lock).flash is not done
still the phone is up and running again, so things seem to be good.
:good:
Click to expand...
Click to collapse
Yeah, had the "catch checkpoint" error, too.
Don't mind, phone is running without problems after that, also when you got this error.
Biggest difference I've noticed is that I had to restart the device manually after flashing (normally without this error, it would reboot automatically) ?
By the way, have you edited your posts a few times?
That makes it hard for other users to understand the whole problem and on that way maybe your posts can't help other users with same problem, so please don't edit/change whole postings ?
Does anyone have a guide on how to root a Xiaomi Redmi Note 10? I’m a novice Android user so any help will be appreciated. Thanks
You will need a Windows PC with Fastboot and Mi unlock tool installed. Here is what you could do without a TWRP to root through Magisk:
Apply for the Unlock process. This will take 167 hours and will factory reset your device. Backup your data before you do this. After the waiting period unlock your Bootloader.
Download your matching or newer Fastboot firmware from here. I assumed you have note 10 non 5G (mojito) based on that screenshot, if not, then that website has it for different varieties as well.
The Fastboot firmware is in .tgz format. Keep a copy for future screw ups just in case (will rescue you). Extract that archived folder and find boot.img inside.
Copy that .img to your phone, and download magisk manager 21.0 or newer and install it.
When opening the Manager on your phone for the first time, it'll prompt you to install itself, choose select and patch file and select the boot.img you copied to your phone earlier.
After it does that successfully, you will find a file called magisk_patched.img on the root of internal storage. Copy that patched .img back to your PC.
Reboot your phone to fastboot mode and connect to PC, flash that patched boot.img using:
Code:
fastboot flash boot magisk_patched.img
If flashed successfully, reboot your device and update/further install magisk.
Done, Your device is rooted !!!
P.S. Don't forget to mark this answer as solved by clicking the check mark beside it if it solved your question so anyone can see this in the future.
Slim K said:
You will need a Windows PC with Fastboot and Mi unlock tool installed. Here is what you could do without a TWRP to root through Magisk:
Apply for the Unlock process. This will take 167 hours and will factory reset your device. Backup your data before you do this. After the waiting period unlock your Bootloader.
Download your matching or newer Fastboot firmware from here. I assumed you have note 10 non 5G (mojito) based on that screenshot, if not, then that website has it for different varieties as well.
The Fastboot firmware is in .tgz format. Keep a copy for future screw ups just in case (will rescue you). Extract that archived folder and find boot.img inside.
Copy that .img to your phone, and download magisk manager 21.0 or newer and install it.
When opening the Manager on your phone for the first time, it'll prompt you to install itself, choose select and patch file and select the boot.img you copied to your phone earlier.
After it does that successfully, you will find a file called magisk_patched.img on the root of internal storage. Copy that patched .img back to your PC.
Reboot your phone to fastboot mode and connect to PC, flash that patched boot.img using:
Code:
fastboot flash boot magisk_patched.img
If flashed successfully, reboot your device and update/further install magisk.
Done, Your device is rooted !!!
P.S. Don't forget to mark this answer as solved by clicking the check mark beside it if it solved your question so anyone can see this in the future.
Click to expand...
Click to collapse
Thanks mate. Will wait for the phone to be unlocked then will try these steps.
hello, I followed the whole procedure and the phone only reboots in bootloop or after several reboots it brings me back to Fastboot
Slim K said:
You will need a Windows PC with Fastboot and Mi unlock tool installed. Here is what you could do without a TWRP to root through Magisk:
Apply for the Unlock process. This will take 167 hours and will factory reset your device. Backup your data before you do this. After the waiting period unlock your Bootloader.
Download your matching or newer Fastboot firmware from here. I assumed you have note 10 non 5G (mojito) based on that screenshot, if not, then that website has it for different varieties as well.
The Fastboot firmware is in .tgz format. Keep a copy for future screw ups just in case (will rescue you). Extract that archived folder and find boot.img inside.
Copy that .img to your phone, and download magisk manager 21.0 or newer and install it.
When opening the Manager on your phone for the first time, it'll prompt you to install itself, choose select and patch file and select the boot.img you copied to your phone earlier.
After it does that successfully, you will find a file called magisk_patched.img on the root of internal storage. Copy that patched .img back to your PC.
Reboot your phone to fastboot mode and connect to PC, flash that patched boot.img using:
Code:
fastboot flash boot magisk_patched.img
If flashed successfully, reboot your device and update/further install magisk.
Done, Your device is rooted !!!
P.S. Don't forget to mark this answer as solved by clicking the check mark beside it if it solved your question so anyone can see this in the future.
Click to expand...
Click to collapse
what about vbmeta?
0purple said:
what about vbmeta?
Click to expand...
Click to collapse
I do not understand the question
0purple said:
what about vbmeta?
Click to expand...
Click to collapse
Not really necessary for Xiaomi devices (apart from the Mi series) as far as I know, but maybe they changed that with the upgrade to android 11?
titifayls said:
I do not understand the question
Click to expand...
Click to collapse
He meant disabling AVB 2.0 by flashing the vbmeta.img from the downloaded fastboot firmware by using:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I personally have encountered many problems using Magisk 22.0 stable version, if you're using that, then either update to the canary version (you can switch the update channel in the manager settings) or use the older version 21.4.
If all of the above fails, just reflash the stock boot.img and your phone will boot normally.
Slim K said:
Not really necessary for Xiaomi devices (apart from the Mi series) as far as I know, but maybe they changed that with the upgrade to android 11?
He meant disabling AVB 2.0 by flashing the vbmeta.img from the downloaded fastboot firmware by using:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I personally have encountered many problems using Magisk 22.0 stable version, if you're using that, then either update to the canary version (you can switch the update channel in the manager settings) or use the older version 21.4.
If all of the above fails, just reflash the stock boot.img and your phone will boot normally.
Click to expand...
Click to collapse
precisely I did not take magisk v22 but v21, moreover I have exactly the same version as the first poster is 12.0.1 RKGEUXM.
To root I took the boot.img from version 12.0.2, was it an error?
I tried to reflash the original boot.img file from v12.0.2 but still in bootloop
I can not find anywhere where to take my original version yet up to date v12.0.1
@titifayls The original poster had version
V12.0.1.0.RKGMIXM (Global) while you claim to have downloaded
V12.0.2.0.RKGEUXM (European) which are not interchangeable. If you want to use either global or eu. Then you would need to flash the full firmware, you can't flash the boot.img from EU to ROM of global. It won't boot.
If you don't really remember which version came with your device, then reply to me again and I can give you further instructions. Tell me which OS are you using to access fastboot and if you want to preserve your data.
Slim K said:
@titifayls The original poster had version
V12.0.1.0.RKGMIXM (Global) while you claim to have downloaded
V12.0.2.0.RKGEUXM (European) which are not interchangeable. If you want to use either global or eu. Then you would need to flash the full firmware, you can't flash the boot.img from EU to ROM of global. It won't boot.
If you don't really remember which version came with your device, then reply to me again and I can give you further instructions. Tell me which OS are you using to access fastboot and if you want to preserve your data.
Click to expand...
Click to collapse
ha , sorry indeed I may have made a mistake, now I don't remember my exact version, it seemed to me that it was EU but in 12.0.1
I use ABD in fastboot and yes I would like to keep all my data that I did not save before wanting to root: /
I bought the phone on aliexpress, I am French, can I look on the box if I have any info on the version?
titifayls said:
ha , sorry indeed I may have made a mistake, now I don't remember my exact version, it seemed to me that it was EU but in 12.0.1
I use ABD in fastboot and yes I would like to keep all my data that I did not save before wanting to root: /
I bought the phone on aliexpress, I am French, can I look on the box if I have any info on the version?
Click to expand...
Click to collapse
I asked if you're using windows or linux to connect to your phone. About losing data, maybe a clean flash could be required, but trying first won't hurt.
Here is how you do it: (you can use the downloaded fastboot firmware, because your device is unlocked, so region differences won't matter that much when flashing full firmware):
Inside that .tgz archive (that you unarchived) you'll find a script called flash_all_except_data_storage.bat for windows or flash_all_except_data_storage.sh for linux. (Do not use the flash_all_lock.bat/.sh script or risk a hard brick, so read carefully this time!!!!)
Connect your device in fastboot mode and open a CMD/Terminal where those scripts and the rest of the firmware files are. Use fastboot devices to make sure device is recognized.
If it is, then type in fastboot followed by dragging and dropping the flash_all_except _data_storage.bat to your CMD/terminal and press Enter. The process should begin automatically. If you get an error, make sure to have typed a space after the fastboot command and before the dropped script.
If it takes a long time during flash of super, don't panic!! Super.img is a very big file
Done!
If it still bootloops after that, then use the flash_all.bat script (will factory reset your phone and delete data)
It doesn't matter, it gives me the list of commands but doesn't launch anything
Wouldn't it be better to put fastboot flash?
don't bother, I'll take miflash, it'll be easier
I delivered an eea_global_images_V12.0.2.0.RKGEUXM rom with miflash by putting flash_all_except_data_storage.
I recovered everything at startup, my applications everything, so I redid the manipulation for the root and now everything works, perfect
thank you
I did the above process successfully.
Also if new update comes out, the process must be done again (not including the unlocking part of course).
The ROMs are posted here
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Slim K said:
Not really necessary for Xiaomi devices (apart from the Mi series) as far as I know, but maybe they changed that with the upgrade to android 11?
He meant disabling AVB 2.0 by flashing the vbmeta.img from the downloaded fastboot firmware by using:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I personally have encountered many problems using Magisk 22.0 stable version, if you're using that, then either update to the canary version (you can switch the update channel in the manager settings) or use the older version 21.4.
If all of the above fails, just reflash the stock boot.img and your phone will boot normally.
Click to expand...
Click to collapse
so if i use latest magisk v22.1 , do i have to disable something like vbmeta.img or not ? or it is onli Mi Series that need to disable vbmeta.img ?
how to see how many hours left to unlock the phone ? i kinda forgot about it, it is my 1st MIUI device beside Xiaomi Mi A1
pihpih95 said:
so if i use latest magisk v22.1 , do i have to disable something like vbmeta.img or not ? or it is onli Mi Series that need to disable vbmeta.img ?
Click to expand...
Click to collapse
Only MI series need that. You should not have to do that. Also yes, I meant to say that 22.0 stable magisk can make the patched boot.img unbootable. Using the 22.1 canary is the way to go.
pihpih95 said:
how to see how many hours left to unlock the phone ? i kinda forgot about it, it is my 1st MIUI device beside Xiaomi Mi A1
Click to expand...
Click to collapse
You would need to connect your phone in fastboot mode and use MI unlock tool again. It'll tell you how many hours left. Usually, you just need to wait exactly one week or 168 hours.
Slim K said:
Only MI series need that. You should not have to do that. Also yes, I meant to say that 22.0 stable magisk can make the patched boot.img unbootable. Using the 22.1 canary is the way to go.
You would need to connect your phone in fastboot mode and use MI unlock tool again. It'll tell you how many hours left. Usually, you just need to wait exactly one week or 168 hours.
Click to expand...
Click to collapse
about mi unlock tool , what version that show how many hours left ? i use latest version and it show nothing on the tool , if i remember correctly the oldest version show the time remaining to unlock , sorry if i mistaken something here >.<
pihpih95 said:
about mi unlock tool , what version that show how many hours left ? i use latest version and it show nothing on the tool , if i remember correctly the oldest version show the time remaining to unlock , sorry if i mistaken something here >.<
Click to expand...
Click to collapse
I used the latest as well. Most of the time, it errors out and I can't see the time left, but sometimes it works. Don't forget, you're giving them your imei for the freedom of your phone. Those imei's must be stored on Chinese servers and the tool must query those servers to get any info, depending on your country it may not work at all.
My experience with using an older tool has been very bad, the time was extended to 2 weeks instead of one on an another Xiaomi device. Avoid doing that and wait the requested time first.
After following the instruction my phone keeps rebooting.
I tried the flash_all.bat without success. What could I do?