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 ?
Related
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
harddisk_wp said:
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
Click to expand...
Click to collapse
Same thing happened to me!
Thank you in advance.
Please let me know if you found the solution.
Chegger said:
Same thing happened to me!
Thank you in advance.
Please let me know if you found the solution.
Click to expand...
Click to collapse
Not the solution, but maybe a cause... did you root your device?
harddisk_wp said:
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
Click to expand...
Click to collapse
Hey my little brother just had the same problem but I managed to get the fone to boot took the battery out held Down volume down and 3 mins later it booted
harddisk_wp said:
Not the solution, but maybe a cause... did you root your device?
Click to expand...
Click to collapse
Yes I did.
I also thought that was the problem.
delox88 said:
Hey my little brother just had the same problem but I managed to get the fone to boot took the battery out held Down volume down and 3 mins later it booted
Click to expand...
Click to collapse
Can you elaborate?
Do you hold before and while turning on?
Did you hold with the battery Out with charger?
I tried to hold while booting but it just stays in the inicial image forever.
Thanks.
Chegger said:
Can you elaborate?
Do you hold before and while turning on?
Did you hold with the battery Out with charger?
I tried to hold while booting but it just stays in the inicial image forever.
Thanks.
Click to expand...
Click to collapse
Ha, same for me. Even adb comes halfway up (adb device shows up in windows' device manager, but "unauthorized", so no shell/pull/push), but it doesn't progress beyond the loading image.
Can anyone with a working B15Q please execute the command "cat /proc/mtd" in a shell or do a full(!) backup using mtkdroidtool?! I pledge €20 via Paypal to the first one who submits all of the partitions except /data up to Mega or another OCH.
harddisk_wp said:
Ha, same for me. Even adb comes halfway up (adb device shows up in windows' device manager, but "unauthorized", so no shell/pull/push), but it doesn't progress beyond the loading image.
Can anyone with a working B15Q please execute the command "cat /proc/mtd" in a shell or do a full(!) backup using mtkdroidtool?! I pledge €20 via Paypal to the first one who submits all of the partitions except /data up to Mega or another OCH.
Click to expand...
Click to collapse
At least you know this stuff that's half way trough.
I will post this in the original root thread since I already posted the issue there and they are now replying ( I will mention you).
http://forum.xda-developers.com/general/rooting-roms/root-achieved-cat-b15q-t2822015/page11
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
bigal1337 said:
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
Click to expand...
Click to collapse
I've the same problem - b15q is bricked - device was rooted to be able to use link2sd.
bigal1337 said:
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
Click to expand...
Click to collapse
I've witten you a PM - please send me your original ROM - or could you send me a link where i may download it.
huedlrick said:
I've the same problem - b15q is bricked - device was rooted to be able to use link2sd.
Click to expand...
Click to collapse
Another one here! Were you able to use link2sd after rooting the phone? Link2sd gave me a mount error when I tried to mount my sd card's 2nd ext3 partition.
Many ppl wanted the stock rom. So i uploaded it to my google drive. It´s a E01 so beware those of you who has B01 or something else.
Original 1.1010.000 rom in files with scatterfile
1.1019.000 Recovery
Original 1.1019.000 update
Scatter file
To flash the phone you only need the bootimg, recovery,android and scatterfile.
(Edit: I dont have google drive anymore)
bigal1337 said:
Many ppl wanted the stock rom. So i uploaded it to my google drive. It´s a E01 so beware those of you who has B01 or something else.
Original 1.1010.000 rom in files with scatterfile https : // drive . google . com /file/d/0ByVAMsMZdC8bdEIxWlpBeXBHNUE/view?usp=sharing
1.1019.000 Recovery https : // drive . google . com /file/d/0ByVAMsMZdC8bVXU2RzBGalV0S1U/view?usp=sharing
Original 1.1019.000 update https : // drive . google . com /file/d/0ByVAMsMZdC8bbWQ4dmhSZWVxZVE/view?usp=sharing
Scatter file https : // drive . google . com /file/d/0ByVAMsMZdC8bSkRhREEwakNhUWc/view?usp=sharing
To flash the phone you only need the bootimg, recovery,android and scatterfile.
Click to expand...
Click to collapse
Thank you very much - but how can I determine if my phone is E01/B01 without being able to boot it?
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
harddisk_wp said:
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
Click to expand...
Click to collapse
Great and congrats.
Could you, please, describe the process and which files did you use.
Thanks.
harddisk_wp said:
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
Click to expand...
Click to collapse
Can you give some hints how you unbricked it? What tools and commands have to be entered?
Best regards,
Doggy77
Uploads are not done yet. But you can prepare until I'm done... grab the driver package, spFlashTool and the 1.022 RAR from http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774.
You will need a win7 x86 machine for this to work (64-bit systems will need to disable the driver signature enforcement, but this is unreliable), and latest(!) WinRAR for unpacking.
The full backup of your device will take up ~1.5 GB, so you will need at least 3GB free and another 2GB if you also want to backup your userdata (HIGHLY RECOMMENDED).
"PMT changed for the ROM; it must be downloaded"
I'm trying to flash the files of harddisk_wp with his instructions but i keep getting the error "PMT changed for the ROM; it must be downloaded", right after I connect the phone and SP Flash Tool finishes "Download DA". I am trying with the 64bit drivers since I do not have a 32bit system, with digital signature verification disabled.
After some search, I saw in the log files that SP Flash Tool is reading the partition table on the phone and comparing it to the scatter file. There is a mismatch there and throws this exception. Now either the driver is not working correct and does not report the partition table right or there is something else going on. Anybody tried this on a 64bit system? Any ideas?
BTW the scatter file is correct for my phone. I had downloaded it myself also before the bricking and I compared it with harddisk_wp's one. They are identical.
In all other aspects SP Flash Tool works fine, I read the user partition for backup without problems.
walckenaerius said:
In all other aspects SP Flash Tool works fine, I read the user partition for backup without problems.
Click to expand...
Click to collapse
SPFT worked for me good to resurrect the phone with files from 1010 version (first firmware) raw partitions.
Phone came back to last user backup and booted fine.
I applied newer and suggested 1019 update that had bricked the phone even further into the loop of the booting logo stuck and rebooting.
SPFT tool memory scan showed that there is no NAND present. I assume that there is PRELOADER damaged. By trying to flush raw PRELOADER that was a no go area. Connection made red line on 100% and nothing happens after that.
SPFT stopped making connection via USB. Inserting the battery, power on - it didn't came back at all.
Phone is now dead black brick that on Linux shows: as MediaTek Inc. MT6227 phone.
In any case do not try to make the same mistake like me.
I will check if it works on some other Windows machine.
Not being Windows user I cannot tell if it is in USB driver or not.
Used W7 without admin pass, with MTKUsbAll driver.
Eh.
Would anyone help me get root on doogee bl 12000? This is a version without a pro so this is a different topic than this one.
No kingoroot or framaroot programs work.
I have flashtoola and rom for this phone. I tried using adb to upload files with the 12000 pro doodge but there was always some error.
I also tried to upload files via flashtoola and recovery. However, without success.
Root Doogee BL12000
Hallo there. I'm trying to root my Bl12000. I've got a TWRP from twrp builder. It works, but whatever zip file I'm trying to install I always get "failed to mount data", invalid argument. The twrp also tells me, that there's bo OS installed, but there is. Phone is working fine after reboot. SuperSu can't be installed. Full wipe is not possible, also "failed to mount" and so on.
any help ?
Tia, Chris
I think it's the encryption. Any ideas how to remove it?
Installed twrp via fastboot and sp flash tool, but I can't boot phone into it. Searched dozens of sites, no success. Flashed the twrp again with sp flash tool and according to sp it was successful. I tried several ways to boot the phone into it afterwards, no luck
My goal is to root this phone only. I'm not very experienced so if anyone could please give me a hand here and tell me where or what I'm doing wrong, that'd would be great and much appreciated. Thanks.
Ok. If I flash the twrp with Sp flash tool and type "fastboot reboot" on the adb console, sending the command while I hold vol+ and power-, the phone boots into the twrp. Next time it will be gone, so I have to flash it again. Noticed that, done.
But all this is taking me nowhere, because the encryption still prevents me from installing any zip file or format a partition. Yuck ?
Root Bl12000
Since the SuperSu method took me nowhere I decided to try Magisk. And.......HURRAY !!!!!!.......it worked.....for a moment. Booted the patched boot.img and got superuser. But with the first reboot I got stuck in bootloop. Tried again, in case I missed something, but same ****.
IT WORKS !!!!! My mistake was to assume, that Magisk works the same way as rooting with SuperSu does. So after rooting with Magisk I tried to install root apps as I was used to, but Magisk does not work that way.
Well, it'll take me awhile to figure this out ?
Why does an app keep coming back on my phone after I have done factory reset?
Christian1968.Bolz said:
Hallo there. I'm trying to root my Bl12000. I've got a TWRP from twrp builder. It works, but whatever zip file I'm trying to install I always get "failed to mount data", invalid argument. The twrp also tells me, that there's bo OS installed, but there is. Phone is working fine after reboot. SuperSu can't be installed. Full wipe is not possible, also "failed to mount" and so on.
any help ?
Tia, Chris
I think it's the encryption. Any ideas how to remove it?
Installed twrp via fastboot and sp flash tool, but I can't boot phone into it. Searched dozens of sites, no success. Flashed the twrp again with sp flash tool and according to sp it was successful. I tried several ways to boot the phone into it afterwards, no luck
My goal is to root this phone only. I'm not very experienced so if anyone could please give me a hand here and tell me where or what I'm doing wrong, that'd would be great and much appreciated. Thanks.
Lucky Patcher 9Apps VidMate
Ok. If I flash the twrp with Sp flash tool and type "fastboot reboot" on the adb console, sending the command while I hold vol+ and power-, the phone boots into the twrp. Next time it will be gone, so I have to flash it again. Noticed that, done.
But all this is taking me nowhere, because the encryption still prevents me from installing any zip file or format a partition. Yuck
Click to expand...
Click to collapse
This Recovery is only supported for Doogee BL12000
You should have either PC or Laptop.
Make sure to charge your phone for at least 50%.
Download and install latest Doogee USB Drivers on your PC/Laptop [All Android USB Drivers]
Download the SP Flash Tool Software
VCOM driver: Download – Instal the VCOM Driver on your computer (still compatible with MT67xx phones)
Before flashing a custom recovery, you need to unlock the bootloader on Doogee BL12000
Take a full backup just in case if you need it later
TWRP+root bl 12000
joachim97 said:
Would anyone help me get root on doogee bl 12000? This is a version without a pro so this is a different topic than this one.
No kingoroot or framaroot programs work.
I have flashtoola and rom for this phone. I tried using adb to upload files with the 12000 pro doodge but there was always some error.
I also tried to upload files via flashtoola and recovery. However, without success.
Click to expand...
Click to collapse
On the forum 4pda can be found for bl 12000
TWRP+ROOT
when you install twrp formatting you can not do it, but immediately install magisk and reboot ...
Since i flash twrp and install magisk i dont have sound on my mi a3. Mic not working, audio not working,music is not playing. When i try to open a video it gives an error " Something went wrong". I tried erase boot flash twrp again, factory reset my mi a3 etc. still problem exist. I downloaded 10.3.8 stock boot.img and flashed system give error in red characters and telling me Factory reset my phone. I live in mountain as a soldier now. This is the only phone that i have in this mountain. Please help
As the first attempt for a fix I'd try switching active slots. If that won't help, you'll probably need to download whole stock ROM and reflash it (for this you must change active slot to A). You can try keeping data (flash all except storage.bat), if it won't work then you'll need to reflash again with data wipe (flash all.bat).
Switching slot doesnt help. i downloaded 10.3.4 rom which has .tgz extension. miFlashtool doesnt recognize my phone and gives error about installing drivers. How to flash new rom? Can you help me little :/
sasukeob said:
Switching slot doesnt help. i downloaded 10.3.4 rom which has .tgz extension. miFlashtool doesnt recognize my phone and gives error about installing drivers. How to flash new rom? Can you help me little :/
Click to expand...
Click to collapse
Unpack the tgz file (inside is another zip if I remember correctly - unzip it as well). Then locate file "flash_all_except_storage.bat" and run it with phone connected in fastboot mode. It should start flashing all images. Do not forget to set slot A as active before booting up the phone.
_mysiak_ said:
Unpack the tgz file (inside is another zip if I remember correctly - unzip it as well). Then locate file "flash_all_except_storage.bat" and run it with phone connected in fastboot mode. It should start flashing all images. Do not forget to set slot A as active before booting up the phone.
Click to expand...
Click to collapse
when i click flash all except storage in fastboot mode. it will do everything i should do right?
sasukeob said:
when i click flash all except storage in fastboot mode. it will do everything i should do right?
Click to expand...
Click to collapse
Yes, it will reflash all partitions with correct stock images.
Guys any other solitions to tell? i cant understand how a phone doesnt play sound even i factory reset it? my hardware is working problem is software but i dont know which part of software...
You might have incorrect combination of kernel and vendor/system/dsp/.. partitions. If one of them is from different version, phone might not boot at all, or cause wifi/sound/.. issues. Have you gone through full rom flashing successfully?
i will do that but first let me find drivers for miflashtool
Generic Google ADB/fastboot drivers will work fine.
_mysiak_ said:
Generic Google ADB/fastboot drivers will work fine.
Click to expand...
Click to collapse
it didnt but i will find qualcomm drivers and install
Qualcom drivers are for EDL mode as far as I know.
i flashed stock rom and my problem solved admins can close this thread. @_mysiak_ thank you for all your help bro
Mine also same, wifi not working, mic not working, no call outgoing/receiving, no media playing, mp3 file is not supported by any player how you fixed?
sasukeob said:
Since i flash twrp and install magisk i dont have sound on my mi a3. Mic not working, audio not working,music is not playing. When i try to open a video it gives an error " Something went wrong". I tried erase boot flash twrp again, factory reset my mi a3 etc. still problem exist. I downloaded 10.3.8 stock boot.img and flashed system give error in red characters and telling me Factory reset my phone. I live in mountain as a soldier now. This is the only phone that i have in this mountain. Please help
Click to expand...
Click to collapse
Mine also have same problem after flashing twrp.
But you can solve it by flashing stock rom in fastboot mode.(Using .bat files included in tgz package after extracting)
But while flashing, If you face any error like remote failed crc error.
Just press the power key of device till it reboots again, and process continues in cmd. Wait for it. Enjoy
Hi everybody
I've got a problem...
Downloaded latest OTA update from "xiaomi.eu", agreed to install, the phone then rebooted in to fastboot mode and does nothing else.
Rebooted the phone with adb command "fastboot continue" and this went well...it rebooted the system.
Now every time i restart the phone it reboots in to fastboot mode and i have to "fastboot continue" again.
I am also not able to enter recovery because the phone always enters fastboot mode.
Reinstalled recovery (Twrp-3.4.2B_toco_by.alex.msk1407.img) via ADB succesfully, but when i "fastboot reboot recovery" it reboots back into fastboot.
I'm also not able to boot into EDL mode.
Any solution?
Thanks
"MI NOTE LITE 8GB/128GB" running "MIUI by xiaomi.eu 12.1.1 | Stable 12.1.1.0(RFNMIXM)
Hi, I 'm in the same case, same model, same version.
I investigated and I can provide more details to help the community to look where to get a match to lightning our lanterns.
I downloaded the last OTA from built-in updater then the device was trapped in fastboot loop.
Unable to reboot/boot with adb/fastboot commands, but able to flash, I tried with différents recoveries,whose the last TWRP (testing version) let us discover the "super partition" (need fastbootd implantation to see it) This is the new OTA update partitioning.
We have to set up the proper flags via adb to perform successfully the update , or cancel the update process to retrieve original partitioning (non-updating state).
The commons way to restore recovery/fastboot might don't work, because system/vendor partitions are hidden inside "super partition" so might result of unknown/doesn't exist partition.
I am still seeking (Android dev super partitioning) and I'll be back when I'll discovered more...
EDIT : Doublon ? Another thread is open
https://forum.xda-developers.com/t/...astboot-after-updating-to-android-11.4223957/
EDIT: many users had a similar issue.
Will try with any another GSI rom, downloading...
opposatto said:
Hi, I 'm in the same case, same model, same version, I investigated and I can provide more details to help the community which lantern to pickup.
I downloaded the last OTA from built-in updater then the device was trapped in fastboot loop.
Unable to reboot/boot with adb/fastboot commands, but able to flash, I tried with différents recoveries,whose the last TWRP (testing version) let us discover the "super partition" (need fastbootd implantation to see it) This is the new OTA update partitioning.
We have to set up the proper flags via adb to perform successfully the update , or cancel the update process to retrieve original partitioning (non-updating state).
The commons way to restore recovery/fastboot might don't work, because system/vendor partitions are hidden inside "super partition" so might result of unknown/doesn't exist partition.
I am still seeking (Android dev super partitioning) and I'll be back when I'll discovered more...
EDIT : Doublon ? Another thread is open
https://forum.xda-developers.com/t/...astboot-after-updating-to-android-11.4223957/
Click to expand...
Click to collapse
Thank you. I'll be for updates
salsaecoentros said:
Thank you. I'll be for updates
Click to expand...
Click to collapse
Looking around https://source.android.com/devices/tech/ota/dynamic_partitions/implement
opposatto said:
Looking around https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Click to expand...
Click to collapse
EDIT : so here is the idea, not tried yet:
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Alex msk's twrp is not compatible with android 11. Use orangefox or pitchblack recovery.
Btw i would recommend not upgrading to android 11 at the moment. It has a lot of bugs.
ApexPrime said:
Alex msk's twrp is not compatible with android 11. Use orangefox or pitchblack recovery.
Click to expand...
Click to collapse
So that's the problem....didn't think about that.
Thanks...i Will try one of them and them get back to you.
Thanks
salsaecoentros said:
So that's the problem....didn't think about that.
Thanks...i Will try one of them and them get back to you.
Thanks
Click to expand...
Click to collapse
Hi...
Sorry for the late Replay.
So i did like you said and installed new twrp and...what do you know...ir worked like a charme. No more issues.
Thank you do much.
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)