Related
OK so please please help me out here. I have a moto g xt1064 and I first installed twrp to flash titan prime ROM 1.0.2 beta and everything was good for about a month or two and then the phone apps started stopping and crashing especially the Google apps (unfortunately, play store has stopped)
So I restored it back to stock 4.4.4 and it was fine for along time and then the apps started crashing again. I literally can't even factory reset or even enable USB debugging. It won't let me install twrp, every time I try to install twrp with adb and fast boot it says its finished but when I go to recovery its still the stock recovery. I tried to install every single ROM and it still won't let me! I don't think its bricked because it powers on and everything. please for the love of phones help me out. Plz answer me
Is your bootloader unlocked.? You cannot flash recovery if you have locked bootloader.
I do have an unlocked bootloader.
Akwardbanana said:
I do have an unlocked bootloader.
Click to expand...
Click to collapse
Try to flash this firmware http://forum.xda-developers.com/mot...riginal-motorola-firmware-collection-t3153533
Run these commands as admin. If you are downgrading it is normal first two give you a preflash verification error.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
Ive done everything correctly but when it rebootednothing changed. I have the same apps and keeps crashing. I've also tried changing run time to Art but that didn't help
Akwardbanana said:
Ive done everything correctly but when it rebootednothing changed. I have the same apps and keeps crashing. I've also tried changing run time to Art but that didn't help
Click to expand...
Click to collapse
You can't reflash the firmware and still have the same apps, you have done something wrong
KuranKaname said:
You can't reflash the firmware and still have the same apps, you have done something wrong
Click to expand...
Click to collapse
Like I said its pretty much impossible to change something. I can't even remove the password from the phone because the next time it reboots the password reappears
Akwardbanana said:
Like I said its pretty much impossible to change something. I can't even remove the password from the phone because the next time it reboots the password reappears
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
KuranKaname said:
Try this: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
I did that a while ago a couple of times but nothing changed. I really don't know what to do :crying:
Akwardbanana said:
I did that a while ago a couple of times but nothing changed. I really don't know what to do :crying:
Click to expand...
Click to collapse
Then I think that your memory chip is gone.
Is there any way to buy a emmc chip and solder it direvtly to the motherboard?
gbb14 said:
Is there any way to buy a emmc chip and solder it direvtly to the motherboard?
Click to expand...
Click to collapse
Well, maybe from another XT1068, you can buy dead ones from amazon and other sites and if you really know what you are doing you can unsolder the broken chip and solder the new one
gbb14 said:
Is there any way to buy a emmc chip and solder it direvtly to the motherboard?
Click to expand...
Click to collapse
If you have a lot of experience soldering electronics and have the proper equipment, maybe. If not, you can forget it, not a chance.
I've seen a lot of threads about dead emmc... I think it's a hardware defect
fburgos said:
I've seen a lot of threads about dead emmc... I think it's a hardware defect
Click to expand...
Click to collapse
So its impossible to fix?
Just handed my phone to a friend of mine , which works at a GSM SERVICE,and today he will try to flash a new firmware using a service box, by COM port. Probably the flashing will take place at a low level.
I'll come back to you to tell if it worked or not.
Normally if the emmc is physically corrupted , nothing can be dine, except soldering a new emmc chip or changing the phone's motherboard which costs a lot...
Thanks
gbb14 said:
Just handed my phone to a friend of mine , which works at a GSM SERVICE,and today he will try to flash a new firmware using a service box, by COM port. Probably the flashing will take place at a low level.
I'll come back to you to tell if it worked or not.
Normally if the emmc is physically corrupted , nothing can be dine, except soldering a new emmc chip or changing the phone's motherboard which costs a lot...
Thanks
Click to expand...
Click to collapse
Please let me know asap. Thanks
Akwardbanana said:
Please let me know asap. Thanks
Click to expand...
Click to collapse
we are on the same brickboat, let's hope somehow it works
so, came back from the gsm service, I'll have to wait 1 more day.
because the phone was sent to another guy .
my friend thinks that my phone is 90% done but until i will get it back i am not celebrating
of course i want to get all the details in what he has done,
brickboats won't sink !!!
so, Yesterday I got the news that i have a problem with my internal memory (surprise surprise!).
So the guys said that they will try to fix the problem, hopefully monday I will have the device back, either in the same state, broken, or fully functional. anyways, I will keep you updated
hi,i need this version ale-l21c113b130,i have search on internet but,i can found,any idea????
try here, http://huaweip8lite.blogspot.co.uk/ just use google to translate & scroll down for rom list
gordonyoung53 said:
try here, http://huaweip8lite.blogspot.co.uk/ just use google to translate & scroll down for rom list
Click to expand...
Click to collapse
Thanks for your reply,i will try with version ale-l21v100r001c432b136a,to see if can i unbrick my phone
cristi.blidariu said:
hi,i need this version ale-l21c113b130,i have search on internet but,i can found,any idea????
Click to expand...
Click to collapse
To unbrick your phone the fastest way is to unlock bootloader which takes you 10-15 mins, and fastboot flash any rom. Easy peasy.
pilililo2 said:
To unbrick your phone the fastest way is to unlock bootloader which takes you 10-15 mins, and fastboot flash any rom. Easy peasy.
Click to expand...
Click to collapse
i have bootloader unlock,i have try many firmware to flash via adb,but when i type fastboot reboot only led blink red for 2 sec and then green for 10 sec,after that the phone shutdown,if i try to turn on same thing,led blink red the green,i dont have any clue what is the problem
To flash a firmware you must use Fastboot commands NOT adb. ADB commands are for when android is already booted. First flash boot.img, recovery.img... etc and then reboot your phone. Its should be working or at least booting. You should check out the mega-thread recently posted in the general section. It might help you.
pilililo2 said:
To flash a firmware you must use Fastboot commands NOT adb. ADB commands are for when android is already booted. First flash boot.img, recovery.img... etc and then reboot your phone. Its should be working or at least booting. You should check out the mega-thread recently posted in the general section. It might help you.
Click to expand...
Click to collapse
here what i use
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot(i have try all version based on single sim and dual sim,the same error,when is try to boot the led indicator blink red then green and is shutdown,if i try to turn on same error led indicator blink red then green,the only option that i have is just to putt the phone in fastboot/rescue mod,so i don't know what is the problem )
Wow ive never heard of that :/ Have you tried flashing recovery before cust? Thats what I usually do. And I also use mfastboot instead of fastboot.
pilililo2 said:
Wow ive never heard of that :/ Have you tried flashing recovery before cust? Thats what I usually do. And I also use mfastboot instead of fastboot.
Click to expand...
Click to collapse
is not my phone,and to be honest with you i have upgrade and downgrade my phone(ale-l21c432b170) many times with out problem,but with this one i dont have any idea what is the problem,so this is his history,it was on ale-l21c113b130 single sim and my friend try to make dual sim by flash version b41c>>b46b>>b052,at the end she will end up with balong error,so his restart phone and from there the phone wont boot up,not even in recovery,so what is the problem????
I have balong bug in my phone and it doesnt really do anything, just a wrong build.prop but phone works perfectly, im on 565 single sim. Im sorry but a really have no idea on what is happening to your friends phone since ive never had that error. Maybe you could try talking to some more experienced users such as Sokkoban to see if he can help you. Sorry
pilililo2 said:
I have balong bug in my phone and it doesnt really do anything, just a wrong build.prop but phone works perfectly, im on 565 single sim. Im sorry but a really have no idea on what is happening to your friends phone since ive never had that error. Maybe you could try talking to some more experienced users such as Sokkoban to see if he can help you. Sorry
Click to expand...
Click to collapse
k,thanks for your reply
pilililo2 said:
I have balong bug in my phone and it doesnt really do anything, just a wrong build.prop but phone works perfectly, im on 565 single sim. Im sorry but a really have no idea on what is happening to your friends phone since ive never had that error. Maybe you could try talking to some more experienced users such as Sokkoban to see if he can help you. Sorry
Click to expand...
Click to collapse
Balong bug -> make sure your 1 on the right location or 2 install the vendor file from your build (vendor MM should do)
cristi.blidariu said:
is not my phone,and to be honest with you i have upgrade and downgrade my phone(ale-l21c432b170) many times with out problem,but with this one i dont have any idea what is the problem,so this is his history,it was on ale-l21c113b130 single sim and my friend try to make dual sim by flash version b41c>>b46b>>b052,at the end she will end up with balong error,so his restart phone and from there the phone wont boot up,not even in recovery,so what is the problem????
Click to expand...
Click to collapse
charge battery. check if bootloader is unlocked correctly ( connect device to pc -> hold volume down while powering up)
open console and type
Code:
fastboot oem get-bootinfo
you should get this
Code:
...
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
if that's the case...
install Twrp 3.0.2
boot into twrp (volume down and volume up while powering on)
wipe everything (dalvik/cache/data/system/internal)
unbrick.
to make everything easier here is a thread.
take those files. it's all prepared (just click once )
also sorry for the noob explaining. you probarly are wellkown with android but it's a custom by now
---------- Post added at 19:19 ---------- Previous post was at 18:59 ----------
btw your problem is that you flashed the custom.img before the recovery it should be in this order.
boot.img
recovery.img
cust.img
system.img
Lordbannakaffalatta said:
Balong bug -> make sure your 1 on the right location or 2 install the vendor file from your build (vendor MM should do)
charge battery. check if bootloader is unlocked correctly ( connect device to pc -> hold volume down while powering up)
open console and type
Code:
fastboot oem get-bootinfo
you should get this
Code:
...
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
if that's the case...
install Twrp 3.0.2
boot into twrp (volume down and volume up while powering on)
wipe everything (dalvik/cache/data/system/internal)
unbrick.
to make everything easier here is a thread.
take those files. it's all prepared (just click once )
also sorry for the noob explaining. you probarly are wellkown with android but it's a custom by now
---------- Post added at 19:19 ---------- Previous post was at 18:59 ----------
btw your problem is that you flashed the custom.img before the recovery it should be in this order.
boot.img
recovery.img
cust.img
system.img
Click to expand...
Click to collapse
i have try with many firmware(extract files from update.app)but,none was work,every time the same error,I think it might be a problem with the partition,or maybe if i can find someone with version c113b130 and try to flash boot an recovery i will have a chance
cristi.blidariu said:
i have try with many firmware(extract files from update.app)but,none was work,every time the same error,I think it might be a problem with the partition,or maybe if i can find someone with version c113b130 and try to flash boot an recovery i will have a chance
Click to expand...
Click to collapse
it goes the same way.
as i told you try installing twrp first wipe everything and then flash it but do it in the order i gave you.
first boot.img
second recovery.img
third cust.img
fourth system.img
this problem occured before. (cant find the thread anymore) but it should work.
and the way is see it you have nothing to lose at this point so
I also told him that. Usually when I flash a rom I also flash recovery before custom, but for no reason at all haha didnt know it could cause a bootloop if done cust before recovery :/
pilililo2 said:
I also told him that. Usually when I flash a rom I also flash recovery before custom, but for no reason at all haha didnt know it could cause a bootloop if done cust before recovery :/
Click to expand...
Click to collapse
K,thanks for the point,it no mater wich order i flash files,the problem is the boot partition wich meen that i am not able to boot in recovery(not even in stock revcovery)i have try to wipe data by using command fastboot -w and press enter but he gave me command not alowed
Sent from my ALE-L21 using XDA-Developers mobile app
pilililo2 said:
I also told him that. Usually when I flash a rom I also flash recovery before custom, but for no reason at all haha didnt know it could cause a bootloop if done cust before recovery :/
Click to expand...
Click to collapse
Yeah i'm not sure eather but they use to hammer this into us that it become an OCD thing for me
and it wwas the only thing i could see what was wrong.
cristi.blidariu said:
K,thanks for the point,it no mater wich order i flash files,the problem is the boot partition wich meen that i am not able to boot in recovery(not even in stock revcovery)i have try to wipe data by using command fastboot -w and press enter but he gave me command not alowed
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
weird that's mostly the case when your bootloader is locked. altough it says PHONE unlocked" it isn't always the case. what do you get when you type
fastboot oem get-bootinfo
could you post it?
rip? http://forum.xda-developers.com/showthread.php?t=2456665
it's with the P6 i know but... those are the same symptones
Lordbannakaffalatta said:
Yeah i'm not sure eather but they use to hammer this into us that it become an OCD thing for me
and it wwas the only thing i could see what was wrong.
weird that's mostly the case when your bootloader is locked. altough it says PHONE unlocked" it isn't always the case. what do you get when you type
fastboot oem get-bootinfo
could you post it?
rip? http://forum.xda-developers.com/showthread.php?t=2456665
it's with the P6 i know but... those are the same symptones
Click to expand...
Click to collapse
i run command fastboot oem get-bootinfo and show bootloader unlock
my narzo 50 got hardbrick can someone help me?
You should better explain, how you ended with your device as it is right now, which modes you have available to enter to, how is acting your device...
please help i accidentally deleted the whole android via mtk client GUI and flashed RMX3151GDPR_11_A.44 on sp flash tool and it booted successfully but the touch stopped working and when i put it on charging it restarts automatically after a few seconds is it HW or SF? I really don't know what to do, do you have any solution?
SubwayChamp said:
You should better explain, how you ended with your device as it is right now, which modes you have available to enter to, how is acting your device...
Click to expand...
Click to collapse
it just like a brick, i cannot access fastboot or any modes
Be sure to try download mode, so you can use SPFT. Also, you have this tool to try it https://github.com/bkerler/mtkclient
SubwayChamp said:
Be sure to try download mode, so you can use SPFT. Also, you have this tool to try it https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
i cannot access anything , download mode, too :/
hoangnguyen320 said:
i cannot access anything , download mode, too :/
Click to expand...
Click to collapse
Sorry. But, are you sure, did you try to enter the download mode? What method did you try? Did you install the drivers for MediaTek? Did you check the devices were listed/updated in the Device Manager on Windows?
All the MediaTek devices, even in a serious brick state, can enter in download mode. Provide some screenshot, so someone can help you better.
Also, Realme devices have a "special" AKA different way to enter the fastboot mode, Which method did you try?
I think you need to disable protection for download mode to work,
if it worked for me, it must work for you.
also on the sp flash tool it booted to the welcome screen successfully, but after the flash the touch stopped working and when I put it on charge it automatically restarts after a few seconds
so I finally fixed it, it was a problem with the software because I had some empty partitions there that were important for touch and charging or for more things, and then I flashed them from the unofficial Realme ui 3.0, for Realme 8i, finally we touch and charging works.
User_Player_126 said:
so I finally fixed it, it was a problem with the software because I had some empty partitions there that were important for touch and charging or for more things, and then I flashed them from the unofficial Realme ui 3.0, for Realme 8i, finally we touch and charging works.
Click to expand...
Click to collapse
how did you manage to fix yours? I have the same issue on realme narzo 50 (RMX3286) where did you download your firmware? i need global rom
Can anyone please help me? I did the all steps but nothing works and I get the STATUS_EXT_RAM_EXCEPTION (0xC0050005) error... The only solution I found is to drain the battery while the device is bootlooping but sadly, my phone vibrates 1 second and dies because there is no fastboot or recovery or nothing to boot with, I tried SP Flash Tool but it stucks at Download DA 100% then shows me the ram error. PLEASE HELP ME
P.S: I know people will say MTK Bypass is a virus but please ignore it and focus on my main subject
Use latest fastboot rom and download agent to mtk all.bin
Restart phone by power+ volume key
Also usb dk driver and libusb tool
Or remove back cover and battery take care with fingerprint
Already done everything you said, nothing works.
iOussamato_ said:
Already done everything you said, nothing works.
Click to expand...
Click to collapse
Try again
faisal9666 said:
Try again
Click to expand...
Click to collapse
What do you mean try again? I tried it 50 times and still doesn't work, tried so many other roms and DAs and NOTHING
iOussamato_ said:
What do you mean try again? I tried it 50 times and still doesn't work, tried so many other roms and DAs and NOTHING
Click to expand...
Click to collapse
Very strange
STATUS_EXT_RAM_EXCEPTION (0xC0050005)
1.
Hello bro, I only registered on XDA to inform you and gonna post on other thread for people suffering from this error.
2.
I have redmi 9c angelica
3.
I had the same issue like yours. Just fixed it 2,3 mins ago after many days of suffering. I tried 3 fastboot roms in which only this work (angelica_global_images_V12.0.12.0.QCRMIXM_20210412.0000.00_10.0_global). I hope it also work with you. Give a try
i followed this and boom now all of my stress has been released.
Firmware link
How to Unbrick Redmi 9C (angelica) without using auth account. Tested and working! - OmBob Opreker
This is tutorial how to unbrick Xiaomi Redmi 9C (angelica) using mediatek bypass tool and sp flash tools without using mi auth account using global stock
ombob.my.id
iOussamato_ said:
Can anyone please help me? I did the all steps but nothing works and I get the STATUS_EXT_RAM_EXCEPTION (0xC0050005) error... The only solution I found is to drain the battery while the device is bootlooping but sadly, my phone vibrates 1 second and dies because there is no fastboot or recovery or nothing to boot with, I tried SP Flash Tool but it stucks at Download DA 100% then shows me the ram error. PLEASE HELP ME
P.S: I know people will say MTK Bypass is a virus but please ignore it and focus on my main subject
Click to expand...
Click to collapse
use this video 100% working
Device locked and need test point. You can't use MTK bypass and SP Flashtool directly. Your device may have patch on July 2022 and newest version (12.5.3 and above).
And if you see 3 dot pin for TP, it's Redmi 9c but if you found only 1 point (for TP), it's Redmi 9c NFC.
Remember to use TP for any operation and if not work, TP with Professional software.
demoimoet said:
Device locked and need test point. You can't use MTK bypass and SP Flashtool directly. Your device may have patch on July 2022 and newest version (12.5.3 and above).
And if you see 3 dot pin for TP, it's Redmi 9c but if you found only 1 point (for TP), it's Redmi 9c NFC.
Remember to use TP for any operation and if not work, TP with Professional software.
Click to expand...
Click to collapse
where are test points located?
Exact same issue,
exact same error,
exact everything.
I ended up flashing using KERDISH Team's SP Flash Tool BUT it still does not wanna boot
When I press the combination to boot into fastboot it vibrates but and shows a screen for a split second.
When I try to boot it up normally it just shows again a screen for a split seccond
And when I try to boot into recovery using again the combination it shows AGAIN the screen for a split secconds
Any help appriciated!
ax0 said:
Exact same issue,
exact same error,
exact everything.
I ended up flashing using KERDISH Team's SP Flash Tool BUT it still does not wanna boot
When I press the combination to boot into fastboot it vibrates but and shows a screen for a split second.
When I try to boot it up normally it just shows again a screen for a split seccond
And when I try to boot into recovery using again the combination it shows AGAIN the screen for a split secconds
Any help appriciated!
Click to expand...
Click to collapse
did you try Yurian's post info, my phone was totally bricked and thats what kinda worked, I left extensive guides on how I did it on there too
also, here are the files that worked for me (redmi 9a, not the exact same but its pretty similar)
your ROMs should be these (use the fastboot one, to the best of my knoledge, the recovery one only changes the recovery hence, its useles to unbrick) if that doesnt work try ROMs for different regions or a one previous version (I dont recomend this because MI is super against downgrading so they f-up your phone if you try) always with the fastboot one
the scatter should be on ROM/images
if that scatter doesnt work, try the ones I provided, theyre for a different version but hey, in for a pound, if its already hard bricked you may as well try crazy stuff, I would suggest you look for the correct scatters online, but I have some slight experience looking for android files and I couldnt find any that are the correct ones.
Lastly, Im just a nobody that unbricked his device and got a little confident, I know next to nothing about phone config, that said, I do think I know more than most but I dont know if scatter files are completely imposible to be compatible between versions or even the ROMs, most Custom ROM work in both 9a and 9c so I think they might, but IDK.
Ivan.Adriazola said:
did you try Yurian's post info, my phone was totally bricked and thats what kinda worked, I left extensive guides on how I did it on there too
also, here are the files that worked for me (redmi 9a, not the exact same but its pretty similar)
your ROMs should be these (use the fastboot one, to the best of my knoledge, the recovery one only changes the recovery hence, its useles to unbrick) if that doesnt work try ROMs for different regions or a one previous version (I dont recomend this because MI is super against downgrading so they f-up your phone if you try) always with the fastboot one
View attachment 5859871
the scatter should be on ROM/images
if that scatter doesnt work, try the ones I provided, theyre for a different version but hey, in for a pound, if its already hard bricked you may as well try crazy stuff, I would suggest you look for the correct scatters online, but I have some slight experience looking for android files and I couldnt find any that are the correct ones.
Lastly, Im just a nobody that unbricked his device and got a little confident, I know next to nothing about phone config, that said, I do think I know more than most but I dont know if scatter files are completely imposible to be compatible between versions or even the ROMs, most Custom ROM work in both 9a and 9c so I think they might, but IDK.
Click to expand...
Click to collapse
Hello! Thanks so much for replying
I still get the same issue, it just shows a screen for a split secconds and then turns off
if you wan
ax0 said:
Hello! Thanks so much for replying
I still get the same issue, it just shows a screen for a split secconds and then turns off
Click to expand...
Click to collapse
t to some day we could hop on a discord call and see if I can help you in any way, although I doubt it since our hardwares arent exactly the same
Ivan.Adriazola said:
if you wan
t to some day we could hop on a discord call and see if I can help you in any way, although I doubt it since our hardwares arent exactly the same
Click to expand...
Click to collapse
sure my discord is axon#7061
same problem but fixed,try tft free tool.here are the steps.
1.remove battery connection,do not connect untill flashed
2.open tft tool,go to mtk section flash scatter
3.connect mobile while holding both volume bouttons
4.now tft tool starts flashing but failed & rebooting device
5.now remove cable & connect battery,bootup
Hoping this should work for you,mine is fixed that way
brav3h3ar8 said:
same problem but fixed,try tft free tool.here are the steps.
1.remove battery connection,do not connect untill flashed
2.open tft tool,go to mtk section flash scatter
3.connect mobile while holding both volume bouttons
4.now tft tool starts flashing but failed & rebooting device
5.now remove cable & connect battery,bootup
Hoping this should work for you,mine is fixed that way
Click to expand...
Click to collapse
thank you so much
idk why but TFT managed to fix it!
ax0 said:
thank you so much
idk why but TFT managed to fix it!
Click to expand...
Click to collapse
It's my pleasure
ax0 said:
sure my discord is axon#7061
Click to expand...
Click to collapse
Hello, please add me, I'm desperate how to do this :-(
ax0 said:
Exact same issue,
exact same error,
exact everything.
I ended up flashing using KERDISH Team's SP Flash Tool BUT it still does not wanna boot
When I press the combination to boot into fastboot it vibrates but and shows a screen for a split second.
When I try to boot it up normally it just shows again a screen for a split seccond
And when I try to boot into recovery using again the combination it shows AGAIN the screen for a split secconds
Any help appriciated!
Click to expand...
Click to collapse
Hi,
Just follow the steps and you'll be good.
[Guide] How to unbrick redmi 9C by flashing with SP Tools without Auth file(Tested Working)
This is a last ditch effort to restore your phone to working order. This should only be used if your phone DOES NOT BOOT AT ALL or if you are unable to boot into FASTBOOT. If you can boot into Fastboot mode then I would encourage you to flash...
forum.xda-developers.com
I already tried it with my device and it works well.
I have redmi note 10s. I bacame bored of miui because of several bugs. So i decided to mod the device with a nice custom rom. I started the process. Because it is a mtk device, it has complicated flashing process than snapdragon devices. I entered the fastbootD mode and cleared the system by using adb command(which i dont remember). Then i flashed the custom rom. By mistake, I locked the bootloader by typing adb command fastboot oem lock. But now due to complicated case, the device is showing your system has been destroyed and when i try to force reboot it into fastboot, it still give systen destroyed error(means fastboot mode is inaccessible). Can anyone please help me to fix this issue without using edl pins? I am in a great issue
I cant go to service center as my device is out of warranty
in google there is a pc program than can unlock bootloader of mediatek devices, search for it
Bro i cant access the bootloader, so unlocking it doesnt make any difference
I want to restore the bootloader.
Manmeet_2008 said:
I have redmi note 10s. I bacame bored of miui because of several bugs. So i decided to mod the device with a nice custom rom. I started the process. Because it is a mtk device, it has complicated flashing process than snapdragon devices. I entered the fastbootD mode and cleared the system by using adb command(which i dont remember). Then i flashed the custom rom. By mistake, I locked the bootloader by typing adb command fastboot oem lock. But now due to complicated case, the device is showing your system has been destroyed and when i try to force reboot it into fastboot, it still give systen destroyed error(means fastboot mode is inaccessible). Can anyone please help me to fix this issue without using edl pins? I am in a great issue
Click to expand...
Click to collapse
Okay so first of all download "mtk client"
Than open the mtk client
It will give you instructions on how to connect your phone, take back of everything except system(super),vendor and userdata. Tap on flash tab there you'll notice a option called unblock bootloader tap on it and your bootloader will be unlocked
Bro Will this restore my bootloader or only unlock it because if it only unlocks then your help wont work.
Manmeet_2008 said:
Bro Will this restore my bootloader or only unlock it because if it only unlocks then your help wont work.
Click to expand...
Click to collapse
you dummy, you need to unlock the bootloader in orden to restore it installing the firmware with miflashtool or mtk client .
Ok bro thanks for your help
tutibreaker said:
you dummy, you need to unlock the bootloader in orden to restore it installing the firmware with miflashtool or mtk client .
Click to expand...
Click to collapse
Manmeet_2008 said:
I have redmi note 10s. I bacame bored of miui because of several bugs. So i decided to mod the device with a nice custom rom. I started the process. Because it is a mtk device, it has complicated flashing process than snapdragon devices. I entered the fastbootD mode and cleared the system by using adb command(which i dont remember). Then i flashed the custom rom. By mistake, I locked the bootloader by typing adb command fastboot oem lock. But now due to complicated case, the device is showing your system has been destroyed and when i try to force reboot it into fastboot, it still give systen destroyed error(means fastboot mode is inaccessible). Can anyone please help me to fix this issue without using edl pins? I am in a great issue
Click to expand...
Click to collapse
try some sp flashtool that come with miflashtool , turn off phone and press volume- and plug the cable in , some type of mtk download mode
Ok bro i will try tomorrow
Hello everyone, today i used the tool but when i went through the tool i saw a 'erase flash' option in mtk universal tab. Can anyone please tell that what this option is used for and ticking it will lead to any sort of issues?
Manmeet_2008 said:
Hello everyone, today i used the tool but when i went through the tool i saw a 'erase flash' option in mtk universal tab. Can anyone please tell that what this option is used for and ticking it will lead to any sort of issues?
Click to expand...
Click to collapse
dont use it, will erase all the device data and partitions turning it into a useless brick, dude, in youtube there a lots of tutos to how restore original firmware go check them first
tutibreaker said:
dont use it, will erase all the device data and partitions turning it into a useless brick, dude, in youtube there a lots of tutos to how restore original firmware go check them first
Click to expand...
Click to collapse
Ok bro thanks for telling, will not use it for flashing
Did it work is it debricked?
Manmeet_2008 said:
I have redmi note 10s. I bacame bored of miui because of several bugs. So i decided to mod the device with a nice custom rom. I started the process. Because it is a mtk device, it has complicated flashing process than snapdragon devices. I entered the fastbootD mode and cleared the system by using adb command(which i dont remember). Then i flashed the custom rom. By mistake, I locked the bootloader by typing adb command fastboot oem lock. But now due to complicated case, the device is showing your system has been destroyed and when i try to force reboot it into fastboot, it still give systen destroyed error(means fastboot mode is inaccessible). Can anyone please help me to fix this issue without using edl pins? I am in a great issue
Click to expand...
Click to collapse
You need to sSee this video,
Make sure Disconnect your phone battery then start flash
hookkrox said:
You need to sSee this video,
Make sure Disconnect your phone battery then start flash
Click to expand...
Click to collapse
You need to see the PM I've sent to you. You will find it here.
Start from BROM mode - that is always available. Then you can use mtktool to restore everything. I have an article about it on my blog, but I am not supposed to post it here... find it in my profile, or send me a PM for help.