Hi all.
I read that my oneplus 9 was able to test the beta of android 12 and found that I could do so in developer options and choose the dsu loader. Did that and now my device won't work at all. I can't get into recovery and factory reset it or anything it just restarts itself and i get an error message saying the device is corrupted and won't boot. Is it any way to fix this or have my own foolishness killed this phone? Please help
Illusions_887 said:
Hi all.
I read that my oneplus 9 was able to test the beta of android 12 and found that I could do so in developer options and choose the dsu loader. Did that and now my device won't work at all. I can't get into recovery and factory reset it or anything it just restarts itself and i get an error message saying the device is corrupted and won't boot. Is it any way to fix this or have my own foolishness killed this phone? Please help
Click to expand...
Click to collapse
Not all hope is gone. If there is an msm tool for your variant your in luck. I have the global unlocked op9 and there isn't one yet. Although you can use a fastboot rom from xda. And there is always last resort of calling OnePlus customer service and getting a remote session . Explain to them you tried the beta release and now phone is unuseable . Hope you get it fixed as I bricked my op8 a month or so ago and it's a bad feeling. I also read the developer previews were not for north American devices. Maybe you saw that as well.
Illusions_887 said:
Hi all.
I read that my oneplus 9 was able to test the beta of android 12 and found that I could do so in developer options and choose the dsu loader. Did that and now my device won't work at all. I can't get into recovery and factory reset it or anything it just restarts itself and i get an error message saying the device is corrupted and won't boot. Is it any way to fix this or have my own foolishness killed this phone? Please help
Click to expand...
Click to collapse
If you can boot to fastboot mode. Then fastboot format userdata I think
Didn't work. Think my bootloader is locked as well since I haven't unlocked it at all. Just read online that you could test the android beta by using that dsu thing and now my phone is gone. It was completely stock hadn't touched a thing except that I got into developer options. I didn't think i could brick a phone without mixing with ROMs and stuff.
Can you get it to bootloader?
Power off completely, then 3-button hold (vol up + vol down + power) till bootloader screen.
If you can, and you can get fastboot to recognize the device, you might have a shot at fastboot oem unlock, and then possibly a fastboot rom.
If not, then you might ask Oneplus support for an MSM tool
reaper000 said:
Can you get it to bootloader?
Power off completely, then 3-button hold (vol up + vol down + power) till bootloader screen.
If you can, and you can get fastboot to recognize the device, you might have a shot at fastboot oem unlock, and then possibly a fastboot rom.
If not, then you might ask Oneplus support for an MSM tool
Click to expand...
Click to collapse
No luck with OEM unlock. Contacted oneplus here in sweden and will send the phone to them on Monday hoping they can fix it. Never thought i could mess upp a phone so much by just tinkering with settings within the phone but you live and learn all the time i guess. Bit sad since I got the phone two days ago
I have bought a used Samsung S10e (SM-G970F/DS) it came with Android 12 and it was reseted.
My goal is to install iodeOS. Even if the iodeOS website says "Update the stock firmware to the latest" I considered the instructions from LineageOS and installed the latest Android 11 version, following this (https://iode.tech/en/iodeos-installation/#1629185391421-4cf1f5c8-d900) uninstall instructions.
After Android 11 was installed I enabled the developer options. OEM-Unlock was not available. Therefore I followed these instructions (https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/) and the OEM-Unlock was available again.
Now it seemed that everything is ready to install iodeOS or LineageOS. Therefore I followed this instructions (https://wiki.lineageos.org/devices/beyond0lte/install). It worked fine until "Installing a cutom recovery using heimdall"
after the "heimdall flash --RECOVERY <recovery_filename>.img --no-reboot" command the S10e shows a bar which is filled from the left to the right and then it shows "Custom Binary (RECOVERY) Blocked By OEM Lock"
Now I have no clue what to do :-(
I would be glad for any help.
You need to unlock the bootloader. You've toggled the OEM Unlocking switch, so unlocking the bootloader is the next step.
Make sure you have the Samsung USB drivers installed on your PC.
Turn off your device.
While holding the Bixby and Volume Down buttons, connect your phone to your PC.
The device should start in Download Mode. Hold down Volume Up until you get a warning about unlocking the bootloader. Unlocking the bootloader will wipe your data. Click Volume Up to confirm.
Your device will wipe data, then reboot. At this point, you can reboot to download mode and flash a custom recovery using Odin or Heimdall.
Thanks a lot for all your help!
The problem was I entered the download mode by the adb command "adb reboot-bootloader" and this mode seems to be different to the one which can be accessed by pressing the keys.
Now everything worked fine
I have exactly the same problem here:
SM-A205G with OEM Unlock enabled
There is no unlock bootloader in the bootloader no option anymore
at least in the bootloder of this edition
And I suppose that if it is the bootloader that flashes everything, it is COMPLETELLY LOCKED, could be jailbroken by some new method, but until them... no option :sad:
V0latyle said:
You need to unlock the bootloader. You've toggled the OEM Unlocking switch, so unlocking the bootloader is the next step.
Make sure you have the Samsung USB drivers installed on your PC.
Turn off your device.
While holding the Bixby and Volume Down buttons, connect your phone to your PC.
The device should start in Download Mode. Hold down Volume Up until you get a warning about unlocking the bootloader. Unlocking the bootloader will wipe your data. Click Volume Up to confirm.
Your device will wipe data, then reboot. At this point, you can reboot to download mode and flash a custom recovery using Odin or Heimdall.
Click to expand...
Click to collapse
It seems that this <confirm> option in the bootloader is being removed by samsung, so... even if unlock oem is enabled... it will not work...
I can only reach the bootloader by going to recovery mode them selecting reboot bootloader, or by adb reboot bootloader, but it boots directly in download mode without the option to long-press volume up key
A flasher that doesn't flashes doesn't makes sense. Maybe samsung have hidden something new in there?...
Ok. I've found the solution
1 - Power the phone off
2 - Hold both volume up and down
3 - PLUG THE USB BUTTON WHILE YOU HOLD BOTH these buttons
4 - NO NEED TO PRESS POWER BUTTON
I guess this will work for all phones that don't have the option to start with power+down
Yes. A flasher that does not flash don't exists.
Good luck ! \o/
source:
HELP!!! Custom Binary (BOOT) Blocked By OEM Lock
Hi there, I've been having trouble rooting my Samsung Galaxy A20 - SM-A205GN for awhile now. I'm officially on Android Version 10 with One UI Version 2.0, I've followed the provided guide to root my device but it fails on Odin "all versions" when...
forum.xda-developers.com
wavedevice said:
Ok. I've found the solution
1 - Power the phone off
2 - Hold both volume up and down
3 - PLUG THE USB BUTTON WHILE YOU HOLD BOTH these buttons
4 - NO NEED TO PRESS POWER BUTTON
I guess this will work for all phones that don't have the option to start with power+down
Yes. A flasher that does not flash don't exists.
Good luck ! \o/
source:
HELP!!! Custom Binary (BOOT) Blocked By OEM Lock
Hi there, I've been having trouble rooting my Samsung Galaxy A20 - SM-A205GN for awhile now. I'm officially on Android Version 10 with One UI Version 2.0, I've followed the provided guide to root my device but it fails on Odin "all versions" when...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, you don't unlock the bootloader VIA the bootloader in Samsung phones.
so you know what happened? I accidentaly reset my phone! I have gone into download mode and there was additional choices: to unlock bootloader holt volup, so I did, then again to confirm unlocking press volup. I did so and then there was for a brief moment android logo and "erasing" and then after about 2 minutes of just Samsung logo phone restarted and asked me to perform setup as it was new! WTH? There was nothing mentioned about deletion
DaHansi said:
I have bought a used Samsung S10e (SM-G970F/DS) it came with Android 12 and it was reseted.
My goal is to install iodeOS. Even if the iodeOS website says "Update the stock firmware to the latest" I considered the instructions from LineageOS and installed the latest Android 11 version, following this (https://iode.tech/en/iodeos-installation/#1629185391421-4cf1f5c8-d900) uninstall instructions.
After Android 11 was installed I enabled the developer options. OEM-Unlock was not available. Therefore I followed these instructions (https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/) and the OEM-Unlock was available again.
Now it seemed that everything is ready to install iodeOS or LineageOS. Therefore I followed this instructions (https://wiki.lineageos.org/devices/beyond0lte/install). It worked fine until "Installing a cutom recovery using heimdall"
after the "heimdall flash --RECOVERY <recovery_filename>.img --no-reboot" command the S10e shows a bar which is filled from the left to the right and then it shows "Custom Binary (RECOVERY) Blocked By OEM Lock"
Now I have no clue what to do :-(
I would be glad for any help.
Click to expand...
Click to collapse
I had the same problem on my samsung tab a10.1. That's why I had to flash the stock firmware 3 times. Every time I flashed twrp with odin, I got the error (custom binary blocked by oem lock).
I write what they should do in order.
1. Turn on the phone.
2. Open Developer mode
3. USB debugging mode - on
4. oem unlocking - on
5. then turn off the phone and disconnect from usb
6. Connect the phone to the PC with USB by holding down the volume up and volume down buttons at the same time. WITHOUT PRESSING THE POWER BUTTON
7. Press and hold the volume up button according to the instructions in the pop-up window.
oem unlocked
Sorry that, I had another problem. May I know how to unlock the OEM if my S10e phone can't turn on.
My device always on "samsung" display page, can't open to index. Do you know this issue? Expecting your reply.
Hi! I have the same issue on my Xiaomi Mi 11 Pro (It was Chinese) but it came unlocked with xiaomi.eu rom.
After i installed a global rom, and google wallet nfc pay did not work, so i thought okay i will lock it then so maybe wallet would accept it, (with the eu rom it worked before) so i put the device in fastboot and used fastboot oem lock on cmd...
And from then it stucks on miui recovery 5.0 screen, and says, this miui version can't be installed on this device...
I might not enabled oem unlocking before i shut if off, but i added it to my mi account so i dont know if after a week i can maybe unlock it. But i think the other possible solution would be to sideload the original chinese stock rom, which is for M2102K1AC, Mi 11 pro, codename mars, but i couldn't find it anywhere... If someone can upload a link to it, that would be a huge help! Or any idea! thx!
geraldmany said:
HI! i got a mi 11 pro 1 year ago, and it was offically chinese, but it came unlocked with Xiaomi.eu firmware, but i could't update it via the updater app, so i searched and found the global star version and just flashed it, everything worked, only now google pay nfc didnt work, it said that its probably because of the unlocked bootloader, so i got to fastboot and in cmd i sent fastboot oem lock, and since then my phone is stuck in miui recovery 5.0 screen and says that i cannot run this firmware on the device, i tried to unlock it but failed, maybe after a week, but i think that i didnt turn on oem unlocking on the phone itself before this... So im just hoping that after a week unlocking could be done... Or my other idea is, that i could install the original chinese rom with sideload, because i managed to install another global version on it since, but the result is still the same, the only problem is that i cannot find literally anywhere a mars codenamed firmware...
Click to expand...
Click to collapse
Anyone who might have the same situation, i found a simple, but effective solution, not sure if it works on every xiaomi device, but i will write down the steps here:
You need to use XiaomiADB, here is the download link and the description for how to use it -> https://xiaomiui.net/how-to-use-xiaomiadb-8044/ (if the page is not available, then feel free to msg me!)
For xiaomi adb, you need to go to 3rd option on the miui recovery screen, NOT THE FASTBOOT
So basically i went through the steps to “xiaomiadb sideload_miui <filename>”
And I tried to install a rom, BUT IT DIDNT ACCEPT IT!
The message was:
ERROR: This rom cannot be installed, server code -> 2001, server message -> Can't install unofficial rom
after trying 4 times all the same and: Installation of this rom via stock recovery is not allowed by Xiaomi
Says Installation failed, and then i just decided to download another rom so i PLUGGED OUT THE PHONE right after this, and went to another room to connect to wired network, to download and try a different rom... when i came back, to all my surprise, the phone was turned on, so i went to the setting dev ops and enabled bootloader unlocking, linked it to my account enabled adb and everything that is needed to flash another rom later, so then i rebooted and again, miui recovery 5.0 screen, but now i enabled unlocking, so i put the phone in fastboot, and tried MI UNLOCKER TOOL again, now it says: Please unlock 168 hours later. And do not add your account in MIUI again, otherwise you will wait from scratch.
So that means, after 7 days i wll be able to unlock it, until then, i can turn it on with the above method, in short try to sideload (copy and install) a rom to it, and then after it failed, plug it out and just wait like 10-20 maybe 30 seconds and bam your device is normally booted... I hope it helps to some of you, (i have been searching for the solution for almost a week, my other option was to pay someone who can MAYBE do it or send the phone back to china and pay the repairs, so im really happy with this method! If it helps to you, please reply so i and the others will know that it worked! Have a nice day!
Condition
Phone does not turns on
Phone not detected via USB
Phone handshake/memory hash failed
Requirements
Unplug battery
Download MIUI 12.5.4.0.RCDMIXM Fastboot ROM
Download Scatter File for 12.5.4.0.RCDMIXM
Download SP Flash Tool
Download Bypass Utility
Download Bypass Configs
Download No Auth File
Steps
Put Bypass Configs into Bypass Utility folder
Put Scatter File in ROM images/ folder
Open SP Flash Tool
Select scatter file within images/
Select No Auth File for DA
Leave Auth file selection blank
In options, select UART.
Ready Bypass Utility python3 main.py; do not run it yet
Connect phone via USB
Press and hold volume - & + buttons
Run python3 main.py; wait for successful execution; release buttons
Immediately start SP Flash tool; retry from 8 if fail
Unplug USB; plug battery; charge device; turn it on and leave for 10 minutes
Done.
The bypass utility enabled my phone to COM6 but SP tool doesn't recognize that port for UART.
Any ideas?
Also, I can't do step 8 without the battery being plugged in and holding vol+ only.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SolomonMT said:
The bypass utility enabled my phone to COM6 but SP tool doesn't recognize that port for UART.
Any ideas?
Also, I can't do step 8 without the battery being plugged in and holding vol+ only.
View attachment 5731647
Click to expand...
Click to collapse
You seem to have a driver issue. Install libusb and try again. The battery should not be required for any of the steps as long as the usb is plugged in properly.
OK, it got unbricked, Im guessing Ill brick it again once I try installing ArrowOS for the second time, but for now, Ill try and sumarize what Ive done since I had the phone on OFW.
To get the phone hard-bricked:
I unloacked bootloader and installed Orange fox succesfully then I bricked my phone while trying to flash Global MIUI (as the first step to install ArrowOS but notice it is totally unrelated to ArrowOS), there is a detailed explanation of how I did it here
[ROM] A11 ArrowOS [Garden] 29-12-2021 UNOFFICIAL
I'm not responsible for damage made to your device About: ArrowOS is an AOSP based project started with the aim of keeping things simple, clean and neat. We added just the right and mostly used stuff that will be actually USEFUL at the end...
forum.xda-developers.com
Trying SPFlash Tool to unbrick my device
My xiaomi redmi 9A was bricked at this point, I described it as:
"the phone just vibrates after a while holding the power button and the screen doesnt even turn on, it isnt recognized by the computer, and if I try to boot into recovery the same happens but the screen turns on for a fraction of a second whith the redmi logo then turn off again, It is not recognized by the computer in this state either"
after gaining some experience with it, I think adecuate to say that the phone still vibrated when holding the power button, but at least the screen did not turn on and as I said; "it wasnt recognized", but just to be clear, what I mean by that is that the PC did absolutely nothing when I pluged the phone in, later after some failed attempts at fixing it, this changed, now the computer prompted me a message explicitly saying, "this device is not recognized" if it was actually recognized before or not is above me.
anyway, back to the moment right after hardbricking my phone in the first place:
I tried using SP flashing tool with this video
but the video is old and after some links died not all the files where provided, (it did however provide a functioning method to disable protection)
so what I did was mix and match different files from diferent sources, and try different methods from diferent videos using SPFlash tool, wich was admitedly a bad idea, the main issue with it was that it symply stayed long periods of time on "download da 100%" with no error message prompting, so i could only stop it change the files and try again, sometimes disconecting the phone, bypassing security with (vol+ vol-) and repeating.
but at one point, the phone did nothing (from now on by nothing I mean not even vibration), the vol+ vol- security did not work, then I tried:
power button alone; noting
power vol+; nothing
power vol-; nothing
and when connected to the PC it told me "this device is not recognized" so the device was totally unresponsive, total brick.
at this point I had already halfly gave up, I enjoy the process, but it was just so unsatisfactory to fail again and again that I just didnt want anymore.
It fixed itself (still hard-bricked but responding).
Now how this got fixed, I actually dont know, I thought maybe if I wait for a while it will respond again, so after two hours it was still the same, I thought maybe if I charge it, after a while with it charging, let it discharge for a while (some odd days), fully charge it (another day or so), and all of those did nothing.
Then I just left it on my desk for like another day when I decided to just try to turn it on one final time and it responded (I dont know what happened I dont know what worked I have several charger boxes and cables plus the pc usb ports, maybe one of them was defective, maybe the one I used lastly was just better, I dont know, but something worked) maybe it just needed around 5 days to work again, i think when it worked for the first time it was plugged to an outlet, Im sorry I cant be more helpful)
now the phone just vibrated after any of the regular button combos, but it no longer displayed anything on the screen if I tried to boot into recovery, but, the PC no longer prompted me that the phone was not recognized, so I could try again.
What actually completely un-bricked my phone.
(This first step is a substitute to the OP requiremeents 5 and 6 used on steps 1 8 9 10 11, this didnt work for me on windows 10, maybe it was just me , but it didnt work)
I installed the Python3.9.1, MTK driver and libUSB I left this files attached as "extra installs", and did it according to how its done on this video
The video is in spanish so if you need extra assistance you can ask me about it or search how to install libUSB wich is the only one I think needs special attention on how to install it (also MTK gave me an error but apparently always does, I tried putting adb on the install folder but Im pretty sure this did nothing as it just gave me a different error)
then, you extract what I left on "ByPass OFF", and run broom.bat a cmd will open up telling you its waiting for a device
(from now on you cant unplug your phone, if you do you have to restart from here)
You plug your bricked phone, and press both vol+ and vol- at the same time until the cmd tells you something like this
then you go to SPFlash tool latest version, (I used SP_Flash_Tool_v5.1924_Win but im pretty sure any one will work)
youll need the ROM that OP provided, its this one.
its 4.22 GB so download it with time, its not a quick page to download from even tho I have "good" internet (around half an hour to a full hour)
you extract it (i recomend using winrar)
and put the scatter file youll use, on the extracted ROM folder, in the image folder, you can download the three scatter files that are for 12.5.4.0 RCDMIXM from the page OP provided and try them all, i left down here the one that worked for me anyway but I dont know what will work for you.
after that I launched the SP Flash tool, and selected the "no auth .bin" provide by OP as Download agent.
(it is posible you get this error
fix it and try again)
as Scatter file you go to the extracted ROM\image and selecth the Scatter file you want to use (again, I left the one I used down here, I have no idea if its the same one that comes with the ROM, also its important it is on the right folder in the extracted ROM)
leave auth blank
I did not select UART port, It didnt work for me, auto USB worked better for me.
you change the dropdown menu to Firmware update
and finally start the program by pressing the download button.
this should work and youll get a prompt like this.
after it had finished I had to unplug my phone and plug it on an outlet for it to let me turn it on, I tried like 3 times before with it still pluged to the PC but it didnt work for some reason, I did not try with it just umpluged so who knows) it turned on to logo, and in around 10 minutes, it asked me to set up the phone as first start like when its brand new, (it was however different to how it used to be, so I know I at least installed a different ROM, do with that info what you will)
Whatts next?
I havent checked if I still have the orange fox recovery installed, tho I doubt it. and also how do I install ArrowOS now? can I do it from spflash tool? thatd be great, is there a better Custom ROM?
Thanks
Also thanks to OP: Yuarian that even if it didnt work for me as is, it still ended providing me with most if not all the tools I needed to unbrick it, and Im pretty sure the ones that didnt work failed becasue I had residual trash files from previous attempts that screwed over his.
anyway see you around.
You mean your display would still show the fastboot logo?
In my case it's completely irresponsive except it's possible to put it in bROM mode if I hold the vol+ button.
But It always stays in Downloading DA 100% then throws an STATUS_RAM exception even with your help.
I'm thinking my hard brick case is of damaged RAM since nothing seems to work.
Also, In my case, the phone won't get in bROM mode (holding vol+) if I don't keep the battery plugged.
M2006C3LG
SolomonMT said:
You mean your display would still show the fastboot logo?
In my case it's completely irresponsive except it's possible to put it in bROM mode if I hold the vol+ button.
But It always stays in Downloading DA 100% then throws an STATUS_RAM exception even with your help.
I'm thinking my hard brick case is of damaged RAM since nothing seems to work.
Also, In my case, the phone won't get in bROM mode (holding vol+) if I don't keep the battery plugged.
View attachment 5765891
M2006C3LG
Click to expand...
Click to collapse
No, the "First brick" the phone only vibrated when holdng the power button and showed nothing on screen, but if I tried to go into recovery (hold power and vol+), it showed REDMI for like a tenth of a second and it turned itself off again. it did nothing when I attempted to go into fastboot (hold power and vol-), I dont know what bROM is but I assume you mean bootloader.
The "second brick" I got after doing something terribly wrong on SPflash, it did nothing no matter what I did, and IIRC, it only vibrated when holding the power button and did nothing else no matter the button combination, it never showed anything on screen.
I have the exact same model, but I dont know how common is that model number, maybe ones made in china and other places have the smae model, I have a 32 Gb version with a single SIM but I can tell it was planed at some point to have it be dualSIM it also has 2 IMEIs
This post [https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/] says its probably an incompatible ROM for your device, but this might mean you need another official ROM I would try the chinnese one but IDK I did not get to that.
About your phone in particular, I have three questions.
Does it even do something at all? does it even vibrate when holding any key combo? did you use the libUSB tool? did you manage to use the bypass tool I provided and got the cmd code I showed in my comment? in general what does it do nd what does it not?
Do you know what bricked it? cuz I doubt its a hardware issue if it got bricked while attempting a flash, and viceversa, I doubt its a software issue if it got bricked on its own.
did something like this ever show up on your SPflash? because it always did on mine when it was working right, did you perhaps use the UART option? I think your issue is still with the computer not recognizing the phone as a phone, now that I think about it I didnt explain how to install the libUSB tool, so maybe that.
I m not an expert but Im more than willing to help and I think it would be very helpful if you described what you did and how, my bet right now is that you failed to use the libUSB driver, Im even willing to hop in a discord call to give you assistance if we somehow shhare time disponibility, I do have a pretty thicc spanish accent tho so youll have to put up with that.
Ivan.Adriazola said:
No, the "First brick" the phone only vibrated when holdng the power button and showed nothing on screen, but if I tried to go into recovery (hold power and vol+), it showed REDMI for like a tenth of a second and it turned itself off again. it did nothing when I attempted to go into fastboot (hold power and vol-), I dont know what bROM is but I assume you mean bootloader.
The "second brick" I got after doing something terribly wrong on SPflash, it did nothing no matter what I did, and IIRC, it only vibrated when holding the power button and did nothing else no matter the button combination, it never showed anything on screen.
About your phone in particular, I have four questions.
Its a redmi 9A right? this post [https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/] says its probably an incompatible ROM for your device, but this might mean you need another official ROM I would try the chinnese one but IDK I did not get to that.
Does it even do something at all? does it even vibrate when holding any key combo? did you use the libUSB tool? did you manage to use the bypass tool I provided and got the cmd code I showed in my comment? in general what does it do nd what does it not?
Do you know what bricked it? cuz I doubt its a hardware issue if it got bricked while attempting a flash, and viceversa, I doubt its a software issue if it got bricked on its own.
did something like this ever show up on your SPflash? because it always did on mine when it was working right, did you perhaps use the UART option? I think your issue is still with the computer not recognizing the phone as a phone, now that I think about it I didnt explain how to install the libUSB tool, so maybe that.
View attachment 5767183
I m not an expert but Im more than willing to help and I think it would be very helpful if you described what you did and how, my bet right now is that you failed to use the libUSB driver, Im even willing to hop in a discord call to give you assistance if we somehow shhare time disponibility, I do have a pretty thicc spanish accent tho so youll have to put up with that.
Click to expand...
Click to collapse
Its a redmi 9A right? A M2006C3LG, so yes.
Does it even do something at all? Without libUSB and MTK drivers it will show up as unrecognizable device.
does it even vibrate when holding any key combo? Not a single vibration, screen or light flick.
did you use the libUSB tool? Yes, I have to.
did you manage to use the bypass tool I provided and got the cmd code I showed in my comment? Yes, it seemingly works and when it doesn't work i usually just need to replug the battery.
in general what does it do nd what does it not? It will try to comm with the computer whenever I hold down vol+. Nothing more.
Do you know what bricked it? First I soft bricked it, then i put it into a bootloop, and then I hardbricked it by misplacing a file in the super partition.
yeah
SolomonMT said:
Its a redmi 9A right? A M2006C3LG, so yes.
Does it even do something at all? Without libUSB and MTK drivers it will show up as unrecognizable device.
does it even vibrate when holding any key combo? Not a single vibration, screen or light flick.
did you use the libUSB tool? Yes, I have to.
did you manage to use the bypass tool I provided and got the cmd code I showed in my comment? Yes, it seemingly works and when it doesn't work i usually just need to replug the battery.
in general what does it do nd what does it not? It will try to comm with the computer whenever I hold down vol+. Nothing more.
Do you know what bricked it? First I soft bricked it, then i put it into a bootloop, and then I hardbricked it by misplacing a file in the super partition.
Click to expand...
Click to collapse
sorry about asking if it was a redmi 9A when the model was the same, I actually edited the comment but you were too fast XD.
Mmm... that makes me think there is hope for you, about the chip info image, did it ever show up?
do you wanna hop in a discord call so we can work it out together?
Ivan.Adriazola said:
yeah
sorry about asking if it was a redmi 9A when the model was the same, I actually edited the comment but you were too fast XD.
Mmm... that makes me think there is hope for you, about the chip info image, did it ever show up?
do you wanna hop in a discord call so we can work it out together?
Click to expand...
Click to collapse
I'll work early tomorrow but i'll probably have time to dig again this weekend.
I didn't understand the chip info image question however.
SolomonMT said:
I'll work early tomorrow but i'll probably have time to dig again this weekend.
I didn't understand the chip info image question however.
Click to expand...
Click to collapse
On my spflash tool (I used the latest version) when I pressed Download, with the firmware update only option it showed me information about my phone, even the times it was stuck on Download DA, it always first show my phone info and then it started downloading, anyway best of luck
Also, Im not sure but its posible you erased your IMEI, changing them is kind of illegal in some places (not in my country to the best of my knoledge) so you cant discuss it in here, but try to look for the box your phone came with, or even better, if you still have the sticker it had in its back, it has the IMEIs, I dont know how you would put them back on or if you would even need to, and cant even discuss it, but there must be a way and its better if you know them before hand.
Ivan.Adriazola said:
On my spflash tool (I used the latest version) when I pressed Download, with the firmware update only option it showed me information about my phone, even the times it was stuck on Download DA, it always first show my phone info and then it started downloading, anyway best of luck
Also, Im not sure but its posible you erased your IMEI, changing them is kind of illegal in some places (not in my country to the best of my knoledge) so you cant discuss it in here, but try to look for the box your phone came with, or even better, if you still have the sticker it had in its back, it has the IMEIs, I dont know how you would put them back on or if you would even need to, and cant even discuss it, but there must be a way and its better if you know them before hand.
Click to expand...
Click to collapse
do you wanna hop in a discord call so we can work it out together? UnaPersona#7278
I have both the sticker with the actual IMEI and the original box.
Something to be noted for ArrowOS is that you cannot install it on a phone running MIUI 12.5, as far as I can tell.
To install ArrowOS you need to install a custom recovery, and there is no custom recovery for MIUI 12.5.
Moreover, Xiaomi prevents you from flashing an older version of the stock ROM, so there is no way to rollback to a version supported by a custom recovery.
Hence, I am stuck running MIUI 12.5 for the foreseeable future.
SolomonMT said:
do you wanna hop in a discord call so we can work it out together? UnaPersona#7278
I have both the sticker with the actual IMEI and the original box.
Click to expand...
Click to collapse
bro, Im sorry to leave you hanging, my college profesor finally answered and Im going to give my carrer talk to aquire the civil engineer title this wednesday, I had kind of a lot to do, are you still trying?
Ivan.Adriazola said:
bro, Im sorry to leave you hanging, my college profesor finally answered and Im going to give my carrer talk to aquire the civil engineer title this wednesday, I had kind of a lot to do, are you still trying?
Click to expand...
Click to collapse
Sorry, I ended up forgetting and rejecting your request since it was sus (?). But yes, i'll continue trying while in possession of the device. Send it again, if you are available. I'll give it a chance next weekend.
Congratulations on the (under?)grad. Thanks.
SolomonMT said:
Sorry, I ended up forgetting and rejecting your request since it was sus (?). But yes, i'll continue trying while in possession of the device. Send it again, if you are available. I'll give it a chance next weekend.
Congratulations on the (under?)grad.
Click to expand...
Click to collapse
youre welcome
I managed to flash the rom and revive my phone thanks to this guide. It booted, works perfectly
First unplugged battery. Then.
I used MTKClient on Linux, installed following instructions, https://github.com/bkerler/mtkclient
And ran command
sudo mtk payload
(then left Vol up and Vol down pressed together and plugged usb cable to unlock the SLA Authorization)
The tool runs a generic payload to the CPU, mt6765 in this case, and puts the phone on BROM mode
(This will unlock SLA authorization, allowing the Rom to be flashed)
(A message appears saying " Successfully sent payload " along with Hardware/Port info)
From there immediately used SP Flash Tool-V5-1916
sudo ./flashtool
Used DA_6765_6785_6768_6873_6885_6853.bin as DA
Used MT6765_Android_scatter--V12.5.4.0.RCDMIXM--boundary_false.txt as Scatter file.
And flashed the whole Firmware/Rom 12.5.4.0.RCDMIXM Global with UART Connection Setting.
Thank you for the guide master. God bless you.
(Its important to be patient)
(Bypass utility didn't work for me, i think it works better in Windows or Debian/Ubuntu, but not other distros)
Yuarian said:
Condition
Phone does not turns on
Phone not detected via USB
Phone handshake/memory hash failed
Requirements
Unplug battery
Download MIUI 12.5.4.0.RCDMIXM Fastboot ROM
Download Scatter File for 12.5.4.0.RCDMIXM
Download SP Flash Tool
Download Bypass Utility
Download Bypass Configs
Download No Auth File
Steps
Put Bypass Configs into Bypass Utility folder
Put Scatter File in ROM images/ folder
Open SP Flash Tool
Select scatter file within images/
Select No Auth File for DA
Leave Auth file selection blank
In options, select UART.
Ready Bypass Utility python3 main.py; do not run it yet
Connect phone via USB
Press and hold volume - & + buttons
Run python3 main.py; wait for successful execution; release buttons
Immediately start SP Flash tool; retry from 8 if fail
Unplug USB; plug battery; charge device; turn it on and leave for 10 minutes
Done.
Click to expand...
Click to collapse
hi i have a redmi k50 pro whit dimensity 9000 MT6983 can you healpe me? pllleasee
Hi, I was trying these steps with no success, maybe something was missing (this was in Windows). However, I found another way to do it with Linux where you don't need to install drivers as the system comes ready to use.
I detailed what I did to unbrick my Redmi 10A here:
Unbrick or Recover Xiaomi Redmi 10A and other MTK devices
Unbrick Xiaomi Redmi 10A and other MTK devices.
runakay.blogspot.com