Related
Hello, I have a soft bricked (hopefully thats the case) Samsung Galaxy S6 SM-G920F xme region (Malaysia) with android 6.0.1 latest stock rom.
It started when my device suddenly restarted and got stuck at the samsung logo (first screen).
I am able to boot it into Download Mode, tried reflashing with a fresh stock rom MM 6.0.1 with odin, flashing proccess was completed with no fail but it still stuck at the same screen.
I can't even boot into recovery mode so i can't wipe the cache partition, i noticed the Reactivaction Lock status is ON, i suspect that might be the culprit?
The things i tried so far:
1- Reflash with the latest stock firmware. Ticking the NAND erase all and repartition it with pit file also didn't work.
2- Samsung Smart Switch and Kies3. Flash completed but no effect.
3- Flashing any recovery files returns with "Custom binary(recovery) Blocked by R/L".
4- Sent it to my nearest Samsung service centre, they did try to repair it but only to be told that my S6 need a new motherboard the next day, which is out of my budget limit. But i am still hoping to find some other way to fix it, i believe this is just a "soft-brick" not a hard brick device.
Ideas guys? thanks.
Try to re flash stock odin firmware with erase all ticked ok ,
Good luck ,,
thereassaad said:
Try to re flash stock odin firmware with erase all ticked ok ,
Good luck ,,
Click to expand...
Click to collapse
Already tried that, still no luck..
mrkage said:
Hello, I have a soft bricked (hopefully thats the case) Samsung Galaxy S6 SM-G920F xme region (Malaysia) with android 6.0.1 latest stock rom.
It started when my device suddenly restarted and got stuck at the samsung logo (first screen).
I am able to boot it into Download Mode, tried reflashing with a fresh stock rom MM 6.0.1 with odin, flashing proccess was completed with no fail but it still stuck at the same screen.
I can't even boot into recovery mode so i can't wipe the cache partition, i noticed the Reactivaction Lock status is ON, i suspect that might be the culprit?
Ideas guys? thanks.
Click to expand...
Click to collapse
Try Samsung Smart Switch, it has some recovery features that can automate the process for you.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Try Samsung Smart Switch, it has some recovery features that can automate the process for you.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Thank you for taking a look at my problem here, i forgot to mention that i did try Samsung Smart Switch and Kies3, both managed to succesfully flashed the stock firmware, it reboots my device and still stuck at the same first screen.
mrkage said:
Thank you for taking a look at my problem here, i forgot to mention that i did try Samsung Smart Switch and Kies3, both managed to succesfully flashed the stock firmware, it reboots my device and still stuck at the same first screen.
Click to expand...
Click to collapse
I believe it is doing that because you have a locked bootloader. Normally that shouldn't be a problem unless you're trying to flash a firmware that is older than what you had.
What stock firmware version/build number did your device have? What firmware version/build number is what you are flashing? If what you're flashing is older it might be downgrading your bootloader, bootloader can't be downgraded on most locked bootloader Samsung devices these days.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
I believe it is doing that because you have a locked bootloader. Normally that shouldn't be a problem unless you're trying to flash a firmware that is older than what you had.
What stock firmware version/build number did your device have? What firmware version/build number is what you are flashing? If what you're flashing is older it might be downgrading your bootloader, bootloader can't be downgraded on most locked bootloader Samsung devices these days.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Don't remember the build number, but it was a 6.0.1 firmware, i flashed it with the same stock firmware version.. but maybe the build number didn't match.
I read somewhere about the engineering bootloader, i know it is not so easy or even possible at the moment to find one for my current firmware version, but let's say if i have it, will it be possible for me to use it to remove the RL on my device?
mrkage said:
Don't remember the build number, but it was a 6.0.1 firmware, i flashed it with the same stock firmware version.. but maybe the build number didn't match.
I read somewhere about the engineering bootloader, i know it is not so easy or even possible at the moment to find one for my current firmware version, but let's say if i have it, will it be possible for me to use it to remove the RL on my device?
Click to expand...
Click to collapse
Did you flash a firmware from a different g920 series device? Or did you flash the firmware for your specific model number and your and carrier?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Did you flash a firmware from a different g920 series device? Or did you flash the firmware for your specific model number and your and carrier?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Only did for my specific model number and carrier
mrkage said:
Only did for my specific model number and carrier
Click to expand...
Click to collapse
Let me backtrack. Do you know if USB debugging is on?
Did you flash TWRP with a locked bootloader before this happened? Is that what caused the issue?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Let me backtrack. Do you know if USB debugging is on?
Did you flash TWRP with a locked bootloader before this happened? Is that what caused the issue?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
USB debugging and Developer Mode was never turned on that device.
Negative, i did try flashing TWRP but it was after it got stuck at the logo screen and only able to boot into Download Mode, the flashing came back failed with "Custom Binary (recovery) Blocked by RL" message.
Flashing it with the latest stock recovery i found online also gave me the same error message.
mrkage said:
USB debugging and Developer Mode was never turned on that device.
Negative, i did try flashing TWRP but it was after it got stuck at the logo screen and only able to boot into Download Mode, the flashing came back failed with "Custom Binary (recovery) Blocked by RL" message.
Flashing it with the latest stock recovery i found online also gave me the same error message.
Click to expand...
Click to collapse
Just out of curiosity, have you tried booting to safe mode? If any of the apps that you installed before this happened were causing an issue or bootloop before you flashed are still there, it/they could still be causing the bootloop. Remember, I said that it doesn't wipe data unless you are upgrading or downgrading bootloader/baseband, what you flashed wasn't an upgrade or a downgrade so your data is there. Boot to safe mode and disable/uninstall the apps that might be causing the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Just out of curiosity, have you tried booting to safe mode? If any of the apps that you installed before this happened were causing an issue or bootloop before you flashed are still there, it/they could still be causing the bootloop. Remember, I said that it doesn't wipe data unless you are upgrading or downgrading bootloader/baseband, what you flashed wasn't an upgrade or a downgrade so your data is there. Boot to safe mode and disable/uninstall the apps that might be causing the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Didn't try that... but nevermind. I accidentally damaged my screen while trying to dissasemble it last night, a very stupid mistake from me.
Thank you for trying to help me mate. Forum mods can close this thread now. Thanks all.
problem
i have too but with A/L
Hi,
I am a little new and don't really know about this subject but :
I purchased a new phone : a Gome K1.
This is not tablet but phone. This is a new brandt. This a MTK (MT6757).
For the story, it came to me with chinese ROM, all menus in chinese
I asked to the seller to give me a ROM with playstore and french. They done it.
I flashed their new ROM with a proprietary flash tool. Now I have a android 6 ROM with Playstore, french menus. Well !
But I'd like to know if there is a way to root it, and install a TWRP :
The ROM came with bootloader locked and no recovery. It is entirely blocked.
No way to unlock bootloader via the general way (fastboot oem unlock --> unknown command)
I read some articles that deal with spflashtool and porting TWRP, but I'm new to this and I don't think I will be able to make all these steps correctly to flash a TWRP ...
Does someone has an idea ?
Is my post on the good topic ?
Up, does someone have an idea of how to root it ?
Hello,i also have a Gome K1 phone and I am also interested at rooting it.
There is an ' OEM unlocking option' under the developers option in the settings, have you tried that yet?
If you managed to import twrp and rooted the phone can you pls send here the steps, Thanks
Hello, happy to not be alone with this phone ...
Yes I tried everything, after enabling unknown source, OEM unlocking and USB Debugging developer options :
- All root apks
- all existing root kits using ADB
- Method with a linux distro to access Phone filesystem as root ( cannot see my phone ... )
Now I'm trying to use SP flashtool last version, but even that cannot correctly access the phone to Readback my recovery : there is BROM error, so I think that phone is not compatible with the phone (seen on a forum ...)
So if someone has an idea, he is welcome
Inveds said:
Hello,i also have a Gome K1 phone and I am also interested at rooting it.
There is an ' OEM unlocking option' under the developers option in the settings, have you tried that yet?
If you managed to import twrp and rooted the phone can you pls send here the steps, Thanks
Click to expand...
Click to collapse
When I contacted them, they send me a non rooted custom ROM which embed Google Apps and All language, AND another flash tool.
This flash tool seems to be based on SP flash tool. It seems to have restrictions (no readback ability ...).
I'm not able to backup anything with this tool or with SP flash tool.
Whis spflashtool, when clicking ReadBack, I power off my phone, and plug USB cable.
It begins the process but I immediatly encounter a BROM error :
ERROR: status_brom_cmd_send_da_fail (0xC0060003)
I read a post which indicate to try to plug usb cable when pressing Power plus Volume Up, but I don't think it can work, because I know that their tool works without that operation.
So now I'm still stuck here. Does someone have an idea ?
Hi
On the Russian forum 4pda, the topic GOME K1 we are also discussing and trying to solve the problem of a locked bootloader. So far no results. ROOT is also not yet possible to get.
I've also ported twrp for GOME K1, but there's no point in installing it until the bootloader is unlocked. Otherwise we will get a brick.
Hi
In Developer options there is a setting to unlock bootloader, it's the third toggle down.
Hope this helps.
Amagram said:
Hi
In Developer options there is a setting to unlock bootloader, it's the third toggle down.
Hope this helps.
Click to expand...
Click to collapse
No, it's not working. This switch does not affect the boot loader state.
vsxby said:
Hi
On the Russian forum 4pda, the topic GOME K1 we are also discussing and trying to solve the problem of a locked bootloader. So far no results. ROOT is also not yet possible to get.
I've also ported twrp for GOME K1, but there's no point in installing it until the bootloader is unlocked. Otherwise we will get a brick.
Click to expand...
Click to collapse
Hello vsxby,
I was successful in flashing custom ROM that vendor uploaded for me.
So I thing I can flash just the recovery with their tool. I'm not an expert, so I'm just a little affraid to follow a guide to port a TRWP for Gome K1 and try to flash it, since it can brick the phone.
If you want, I can't send you a copy of their tool they sent to me (SPMultiPortFlashDownloadProject.exe) ...
z2x said:
Hello vsxby,
I was successful in flashing custom ROM that vendor uploaded for me.
So I thing I can flash just the recovery with their tool. I'm not an expert, so I'm just a little affraid to follow a guide to port a TRWP for Gome K1 and try to flash it, since it can brick the phone.
If you want, I can't send you a copy of their tool they sent to me (SPMultiPortFlashDownloadProject.exe) ...
Click to expand...
Click to collapse
Thank you, but I already have this tool. As I wrote before flashing TWRP we need to unlock the bootloader. While this is not impossible to do. But one of our users on 4pda is going to ask the manufacturer to unlock bootloader. In case of success, I will inform you.
If you want to experiment and flash TWRP with a locked bootloader, I can give you the TWRP I made, but I warn you, it's not safe.
Bro,Can you upload the firmware and tools to google drive or something like? It will be very helpful for dealing with this mediatek replica phone(aus6757_66_m),i got some possible factory test MTK AOSP,but the link expires ：（
@Vortex said:
Bro,Can you upload the firmware and tools to google drive or something like? It will be very helpful for dealing with this mediatek replica phone(aus6757_66_m),i got some possible factory test MTK AOSP,but the link expires ：（
Click to expand...
Click to collapse
It's link GD to multi firmware and tool
vsxby said:
Thank you, but I already have this tool. As I wrote before flashing TWRP we need to unlock the bootloader. While this is not impossible to do. But one of our users on 4pda is going to ask the manufacturer to unlock bootloader. In case of success, I will inform you.
If you want to experiment and flash TWRP with a locked bootloader, I can give you the TWRP I made, but I warn you, it's not safe.
Click to expand...
Click to collapse
Ok, hope manufacturer will accept to give bootloader unlock procedure
z2x said:
Ok, hope manufacturer will accept to give bootloader unlock procedure
Click to expand...
Click to collapse
We were unable to contact the manufacturer and the moderators of the official GOME forum do not have this information. At the moment, there are no solutions to this issue.
z2x said:
Hello vsxby,
I was successful in flashing custom ROM that vendor uploaded for me.
So I thing I can flash just the recovery with their tool. I'm not an expert, so I'm just a little affraid to follow a guide to port a TRWP for Gome K1 and try to flash it, since it can brick the phone.
If you want, I can't send you a copy of their tool they sent to me (SPMultiPortFlashDownloadProject.exe) ...
Click to expand...
Click to collapse
could you please post here what is the procedure you took to flash the rom. Seller sent me with multi language rom. i want to downgrade the rom to its original one. I used your tools in the windows 10 lap. and also in the windows 7 lap but it was useless. I am going to try the procedure in the windows 8.1 lap. can you tell me exactly how you flash your phone with that tool ?
Hey Bro,
I get my new Gome K1 with Global ROM
but have some issues with my new Gome K1 >> the GPS doesn't work proper for Google Maps / Waze, it doesnt show accurate position most of the time, but it seems work well with "offline GPS" (but offline GPS most of the time not able to find location that I ahead for meeting). Any recommendation/solution?
Thanks in advance
Hi, is there any modem file for this phone ? MDDB....
original eom (china rom).
Hello every one i buy thise phone and come with multilanguage firmware but i like the origin one, can anyone help me the link of the firmware of origin!!
vsxby said:
We were unable to contact the manufacturer and the moderators of the official GOME forum do not have this information. At the moment, there are no solutions to this issue.
Click to expand...
Click to collapse
After some time ... is there any news about his root? I wouldn' t like to change the rom, but just do the root thing would be useful ..... tks
i've disabled the google app in the settings and now the phone is stuck on boot logo... any ideas how to fix this?
---------- Post added at 06:51 PM ---------- Previous post was at 06:30 PM ----------
driska said:
i've disabled the google app in the settings and now the phone is stuck on boot logo... any ideas how to fix this?
Click to expand...
Click to collapse
found the answer on 4pda, can't post link.
Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
I had the some problem while playing with my handset I switched off OEM unlock for some reason under developer option..
Next time i reset my handset it stuck on that warning
You need to download combination file, flash it with odin, then unlock developer mode, toggle OEM unlock, than flash back your current firmware, or if you have full twrp back up restore it
JayMor81 said:
Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
Click to expand...
Click to collapse
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Dammit.. I tried to put as much detail as possible in there lol.. obviously I forgot some.. My mistake the Galaxy s7 that I am using is a Rogers Mobile (Canada) SM-G930W8. As for not signing out before modification, omfg, that makes perfect sense.. didn't even think of doing that before rooting.. I appreciate the help!! I will give this a go and see what outcome I get.. Thanks!
[/COLOR]That was nice of you to respond so helpfully, despite you having seen the scenario posted over and over.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Can't make or receive calls
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Cesilina said:
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Click to expand...
Click to collapse
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
cooltt said:
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
Click to expand...
Click to collapse
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Cesilina said:
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Click to expand...
Click to collapse
Do you still have an imei number listed in settings?
Can't make or receive calls
cooltt said:
Do you still have an imei number listed in settings?
Click to expand...
Click to collapse
Yes please I still have an IMEI number
I have tried everything, I have flashed 4 different firmware versions in odin. Did all the updates, followed the guides and all that yet the OEM unlock option does not appear and kg status is still prenormal. You are probably wondering how I got here. I flashed a GSI rom that I did not like, I flashed back my firmware INCLUDING the bootloader. Flashing the bootloader reset it's state to locked. That in it self was no problem ill just wait 7 days and it will be unlockable again. But no KG state is still prenormal and oem is not unlockable. I just reflashed my firmware and I am going to start waiting *again* hoping that a miracle will happen. How hopeless is the situation with my phone, is it worth hoping it can fix this or will i have to just use the preloaded non rooted firmware? I had a hope to port lineage 18.1 to this phone but I am losing any hope of it happening.
Hi ...... I have stucked in the same situation did you find any solution ?????
Bazzazi said:
Hi ...... I have stucked in the same situation did you find any solution ?????
Click to expand...
Click to collapse
No there is absolutely no solution, trust me. EDL method does not work anymore due to the security patch from last year having an new system. Unfortunately there is no working leaked firehose file since then. Don't even try any of the methods on youtube, rewritting the storage with the file from the factory was the only method.
thanks for your reply bro !!!!
I think 7 days up time and internet connect should fix the problem
i'm gonna try it.....
Bazzazi said:
thanks for your reply bro !!!!
I think 7 days up time and internet connect should fix the problem
i'm gonna try it.....
Click to expand...
Click to collapse
Did you get it fixed?
I think we already have a solution here on XDA portal
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com
hi, can you tell me the exact model and carrier? (csc)
hi, i updated my phone to MIUI 13.0.3 android 12 and i've noticed a bug that made all the apps that are using the camera like instagram and snapchat take blurry pictures like an effect getting applied to the pictures taken by those apps (everything normal in my stock camera app) so i decided to use MiFlash tool to flash the previous android version on my phone but i bricked my phone instead i flashed a global rom while my phone is the chinese market version and accidently checked the ClearData+lock Device check box in MiFlash. the tool flashed the rom successfully but when the phone restarted it showed me a message saying that this rom cannot be installed on this device in recovery mode i couldn't do anything after cuz the bootloader got locked too T i tried everything to unlock it (mtk Client - bootloader unlocker+ adb fastboot + Xiaomi Unlock app ...). please help me is there any way i can fix my phone and what is the righ Rom to flash on my phone (Redmi Note 11 Pro 5G China (21091116C - Pissarro). thnx
friend I'm not a star I tell you how things are 1) you can't go back with another Rom only china 2) anti-roll-back 3) MiCloud you have to disable it you can try MiflashV2 there is also to unlock the bootloader it does everything even the firmware remember if the firmware does not start. important not only china also not china for updates remember first you do the factory reset put google account do not update any app except google drive backup with drive if it has arrived update it is better by setting the time instead of downloading the package the problem is when the update occurs it fails to close all active apps and then there is MiCloud that blocks. Best wishes and good luck and that I have little time for me too much trouble here in Europe.
Braain said:
friend I'm not a star I tell you how things are 1) you can't go back with another Rom only china 2) anti-roll-back 3) MiCloud you have to disable it you can try MiflashV2 there is also to unlock the bootloader it does everything even the firmware remember if the firmware does not start. important not only china also not china for updates remember first you do the factory reset put google account do not update any app except google drive backup with drive if it has arrived update it is better by setting the time instead of downloading the package the problem is when the update occurs it fails to close all active apps and then there is MiCloud that blocks. Best wishes and good luck and that I have little time for me too much trouble here in Europe.
Click to expand...
Click to collapse
currently my phone is stuck at the logo and after seconds it loads Fastboot automatically i cant access the phone os to do anything i used the xiaomi bootloader unlocker app that works online but it didnt work . the local cell phone service shops told that they have to open the phones back case to fix it ... i dont want that i've just bought the phone didnt even use it for a whole month
they don't have to open it they use licensed or dongle software (USB type) currently I use unlocktoll.net but if the phone is under warranty and you haven't removed the bootloader before it is better for you. It is possible that others have the same problem as you. Good luck
-deleted-
Rule number 1 for Xiaomi never flash anything on Mediatek devices, it will fail. If messed up, no way back as Xiaomi locks the devices for autorized service providers or local Xiaomi branches only. If you want to play with Xiaomi custom roms/development/etc. related only buy Snapdragon based devices.
I i.e. learned it the hard way, when this all started with the Redmi Note 8 Pro, I bricked it by flashing twrp in Android 11 and Xiaomi didn't want to repair it, so I had to pay some russian guy to fix it via Teamviewer with a modified unlock tool which was able to answer the unlock requests by pasting the answer manually from a generator. It's not like I messed up at a point, it's just that Mediatek devices easily fall in a unrecoverable state. In my term it was the combination of Android version and twrp. You will note there is no Mediatek support on xda and even when your device is named like a Snapdragon version, your device is offtopic here, because trying anything on it beyond unlocking the bootloader is harakiri
how to unlock my bricked Redmi Note 11 Pro 5g (Chinaissarro) Bootloader
Congratulation. Brick without unlocked BL :/
my opinion: you are done....
Some Xiaomi devices have pins on motherboard to
switch EDL, but i dont know with this device.
Try complaint and say something like: "my phone was upgraded and then i see only logo"
Fedon said:
how to unlock my bricked Redmi Note 11 Pro 5g (Chinaissarro) Bootloader
Congratulation. Brick without unlocked BL :/
my opinion: you are done....
Some Xiaomi devices have pins on motherboard to
switch EDL, but i dont know with this device.
Try complaint and say something like: "my phone was upgraded and then i see only logo"
Click to expand...
Click to collapse
I did the same with my device. You can fix it using the MTK tools guide. Its lengthy but easy.
rakesh.aggarwal said:
I did the same with my device. You can fix it using the MTK tools guide. Its lengthy but easy.
Click to expand...
Click to collapse
rule #1 with Xiaomi - bootloader is unlocked