HELP please... HardBrick RN3SD - Xiaomi Redmi Note 3 Questions & Answers

i don't know what to do... i think i read every tutorial for unbrick my phone but nothing works...
my situation:
-i unlocked my fone by unnoficial method, instaled twrp and everything was ok.
i decided to instal sMIUI, but nowhere i read that is necesary to delete emmc file... so i bricked my phone.
bootloader got relocked, i can't turn on my phone, mi logo appears during 1 sec > screen off > again mi logo during 0.001s > screen off
when i plug in my phone into my pc, i have black screen and red led, but it's not adb mode.
i can't enter adb, my pc (windows 10 x64), i use command "adb devices" and list is empty
i can't edl
i can enter in fastboot mode.
i can't flash nothing, "failed: device is locked"
anyone can help me?
if i unlock officialy my bootloader, can i flash again stable rom or something? i just had my phone during 2 weeks.
can i do anything?
thanks.
one more thing: i had guaranty, so, if i unlock my bootloader officialy, i lose it?
i don't want to try testpoint method, because of guaranty.

Well, welcome to the party.
Irrespective of how much u search, cry for help or open millions of threads like this instead of doing a little search, there is no solution except test point method. Now don't ask how to do it. Search and read a little u will get the necessary info.

sanjib734 said:
Well, welcome to the party.
Irrespective of how much u search, cry for help or open millions of threads like this instead of doing a little search, there is no solution except test point method. Now don't ask how to do it. Search and read a little u will get the necessary info.
Click to expand...
Click to collapse
thanks a lot for this kind help, i will do it, don't worry. :good:

Don't worry bro u will certainly do what is required. I was the first who reported a bricked device while unlocking bootloader by unofficial method. After extensive search and trying different methods I came to this conclusion.

Related

[Q] How To Root Xperia U / ST25i

I bought my new Xperia U . Please Some one Tell me how to unlock bootloader & Root the Device Please Post Video / Screen Shots
=-Step bY Step-=
Thank You !!!​
rakeshnofear said:
I bought my new Xperia U . Please Some one Tell me how to unlock bootloader & Root the Device Please Post Video / Screen Shots
=-Step bY Step-=
Thank You !!!​
Click to expand...
Click to collapse
Plese search the forum.
Unlocking and rooting of X- U/P/s has already been explained many times in detail..
rakeshnofear said:
I bought my new Xperia U . Please Some one Tell me how to unlock bootloader & Root the Device Please Post Video / Screen Shots
=-Step bY Step-=
Thank You !!!​
Click to expand...
Click to collapse
Xperia U / S / P Bootloader unlocking
http://forum.xda-developers.com/showthread.php?t=1527159
Tested and perfectly working on my Xperia U
Simply select advanced tab from flashtool and root then select zergrush easiest way
I got a message saying MTP is enabled and cant root
alankstiyo said:
I got a message saying MTP is enabled and cant root
Click to expand...
Click to collapse
Flash any of the custom kernels to get root
Sent from my ST25i using Tapatalk 2
plzzzz help
Friends,i am new here and xperia u is my first android device..i know its a bit too much to ask but if anyone can please post a detailed step by step procedure for rooting xperia u..that would be really helpful for many others like me..i have already googled it so many times but still no luck with a perfect tutorial..also,the method suggested above to root by flashtools does not work..hope to see a reply from senior members and moderators soon..regards..
reply on how to unlock bootloader
xperiavish said:
Friends,i am new here and xperia u is my first android device..i know its a bit too much to ask but if anyone can please post a detailed step by step procedure for rooting xperia u..that would be really helpful for many others like me..i have already googled it so many times but still no luck with a perfect tutorial..also,the method suggested above to root by flashtools does not work..hope to see a reply from senior members and moderators soon..regards..
Click to expand...
Click to collapse
Number1) unlock bootloader, it is free and official from unlockbootloader.sonymobile.com
number 2) download flashtool, find it urself......
number3) Once clicked, you will then get a pop up where it will read “Are you really sure?”, click on “Yes, I’m sure” and there you go, you now need to open the command prompt in your computer. Dial *#06# in your phone to get the IMEI number. Note it down at the safe place as it may be required at a later stage.
•Connect your phone to the computer and then in the command prompt (shift+ right click in fastboot folder under "system c:/flashtoo"l, you now need to enter in the below mentioned command.
number 4)type this in "fastboot -i 0x0fce oem unlock 0Xkey", replace key with the key u obtained from the site
number5)“” •Ensure that the KEY which you have replaced with the IMEI is the correct IMEI number. After entering the above command in the command prompt, you need to then follow the on screen instructions so as to unlock the boot loader.
Congratulations, you have now successfully unlocked the boot loader of your device. Do let us know just in case if you need any assistance in the comments section as we will ensure that all your issues are sorted out at the earliest.
if u want to relock, search google again, google is not a "super dificult" search engine to use. hope it helps u
works?
works in 2.55 ics???
khoojunxiang said:
Number1) unlock bootloader, it is free and official from unlockbootloader.sonymobile.com
number 2) download flashtool, find it urself......
number3) Once clicked, you will then get a pop up where it will read “Are you really sure?”, click on “Yes, I’m sure” and there you go, you now need to open the command prompt in your computer. Dial *#06# in your phone to get the IMEI number. Note it down at the safe place as it may be required at a later stage.
•Connect your phone to the computer and then in the command prompt (shift+ right click in fastboot folder under "system c:/flashtoo"l, you now need to enter in the below mentioned command.
number 4)type this in "fastboot -i 0x0fce oem unlock 0Xkey", replace key with the key u obtained from the site
number5)“” •Ensure that the KEY which you have replaced with the IMEI is the correct IMEI number. After entering the above command in the command prompt, you need to then follow the on screen instructions so as to unlock the boot loader.
Congratulations, you have now successfully unlocked the boot loader of your device. Do let us know just in case if you need any assistance in the comments section as we will ensure that all your issues are sorted out at the earliest.
if u want to relock, search google again, google is not a "super dificult" search engine to use. hope it helps u
Click to expand...
Click to collapse
correct! If you want to acces root you now have to download http://forum.xda-developers.com/xpe...de-root-cwm-unlock-bootloader-custom-t2403929 that and run the runme.bat file. Connect your phone and you should be running ICS 4.0.4. I had the 89 when I rooted. Enable usb debugging, you can search on how to do that and after that you connect your device to your pc and click 1 on the runme.bat file and hit enter. Wait for the magic and if you are stuck at ''if succes i will tell you'' part, wich I was. Just unplug your phone, reboot and go to your appdrawer and find the ''make a copy and restore'' app and click on find a copy and click on ''root'' (something like that) and after that click restore. Reboot and then download kingroot, the latest is recommended. And roooooooot . After that you may want to replace the kingroot root authorizer with super su. This is optional but I recommend it. Follow http://androidmtk.com/replace-kinguser-with-supersu that tutorial and you should be good to go!
Well this thread is extremely old so I suppose it should be closed.

Kenzo Error Fix {Failed (remote: token verification failed, reboot the device)}.

Can any developer please please help me out quickly? i'm out of time seriously I need help but quick.
I'm trying to unlock my device Redmi Note 3 Snapdragon varient. All the other commands like
* adb devices
* adb reboot edl
* fastboot devices
* fastboot oem device-info
everyone of it is working fine but when I write
* fastboot oem unlock-go
I get the above mentioned error.
Does anybody know the solution to it? Before answering please consider that other commands are working except this one, I didn't found any proper solution that's why posted the problem here and I already did revoke USB debugging permissions and turned it on again but that didn't helped.
So please give me a working solution as quick as possible or else any help is appreciable.
enable oem unlock in developer options
Enable OEM Unlock option in Developer Options.
caesar13th said:
enable oem unlock in developer options
Click to expand...
Click to collapse
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
superboy123 said:
Enable OEM Unlock option in Developer Options.
Click to expand...
Click to collapse
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
Gurkirat_Singh said:
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
Click to expand...
Click to collapse
That fastboot oem unlock-go command won't work.
OK, follow these steps:-
a) Reboot to Fastboot mode by pressing Power and Vol down buttons for 10 seconds.
b) Download the MiUnlock tool and enter your credentials first. It will check whether your Mi account has permission to unlock (you must have permission from Xiaomi to unlock).
c) It will detect your phone as Mi Phone and proceed to unlock.
d) It will verify whether the Mi account in your phone and the credentials of the Mi account you entered on the PC are the same.
e) It will unlock your device for sure!
If it says some sort of verification error aka. the famous stuck at 50%, wait for some days like for a week and try again, it may work even in 2 days! Keep trying!
Good Luck!:good::highfive:
Thank you!
superboy123 said:
That fastboot oem unlock-go command won't work.
OK, follow these steps:-
a) Reboot to Fastboot mode by pressing Power and Vol down buttons for 10 seconds.
b) Download the MiUnlock tool and enter your credentials first. It will check whether your Mi account has permission to unlock (you must have permission from Xiaomi to unlock).
c) It will detect your phone as Mi Phone and proceed to unlock.
d) It will verify whether the Mi account in your phone and the credentials of the Mi account you entered on the PC are the same.
e) It will unlock your device for sure!
If it says some sort of verification error aka. the famous stuck at 50%, wait for some days like for a week and try again, it may work even in 2 days! Keep trying!
Good Luck!:good::highfive:
Thank you!
Click to expand...
Click to collapse
Thanks for the help but I don't even want to try that method first it's very problematic, it takes a lot of time and it's not even sure if it works. So if you can help me with the problem I'm having that would very very very appreciable :good:.
And why the command will not work, can you please tell me? Also this command gives the same error "fastboot OEM unlock bootloader". Hope you can help .
Gurkirat_Singh said:
Thanks for the help but I don't even want to try that method first it's very problematic, it takes a lot of time and it's not even sure if it works. So if you can help me with the problem I'm having that would very very very appreciable :good:.
And why the command will not work, can you please tell me? Also this command gives the same error "fastboot OEM unlock bootloader". Hope you can help .
Click to expand...
Click to collapse
It's not that problematic, actually it is the easiest way to unlock bootloader!
Unofficial bootloader is the very "problematic" method.
Anyhow, Are you looking for unofficial bootloader unlock? Then go here and follow the steps correctly, dont skip any step.
And for your second question, Xiaomi has complicated the bootloader unlock process by heavy encryption. That's why you couldn't unlock Redmi Note 3 as any Moto device!
superboy123 said:
It's not that problematic, actually it is the easiest way to unlock bootloader!
Unofficial bootloader is the very "problematic" method.
Anyhow, Are you looking for unofficial bootloader unlock? Then go here and follow the steps correctly, dont skip any step.
And for your second question, Xiaomi has complicated the bootloader unlock process by heavy encryption. That's why you couldn't unlock Redmi Note 3 as any Moto device!
Click to expand...
Click to collapse
OK that's why I'm having so much problem to unlock it. I just want to ask do you know any other way to fix the problem I'm having with this error. Cause the post you gave me tells how to unlock the RN3 temporary :crying: but the thread I followed helps to unlock it permanently :good: (how I know cause I used similar commands on my Canvas A1) and I followed almost every step properly.
I don't understand why companies emerged as custom ROMs stops supporting customisation, at least don't make it hard. I just wanted to flash my RN3 with a Custom ROM like CM13 cause MIUI is not supporting 4G networks properly of multiple operators that's why, for which I needed a custom recovery and for which I needed unlocked bootloader.
I just don't understand , all this so that no one could copy their ROM or I don't know for what . It's just makes things difficult for normal people and no one else. Locks can't keep a thief away. If anyone wants to break into their system than one will, if he/she uses right tools properly. Why make normal people lives' difficult?
ALSO I WANT TO ASK MORE THING, if in first case, I get into fastboot mode just after the ROM flash & before very first ROM boot and run this command and if in second case, the room gets booted and then I go into fastboot mode & run the command, DOES IT CREATES ANY CHANCE OF NON-OCCURRENCE OF THAT ERROR IN FIRST CASE?.
Gurkirat_Singh said:
OK that's why I'm having so much problem to unlock it. I just want to ask do you know any other way to fix the problem I'm having with this error. Cause the post you gave me tells how to unlock the RN3 temporary :crying: but the thread I followed helps to unlock it permanently :good: (how I know cause I used similar commands on my Canvas A1) and I followed almost every step properly.
I don't understand why companies emerged as custom ROMs stops supporting customisation, at least don't make it hard. I just wanted to flash my RN3 with a Custom ROM like CM13 cause MIUI is not supporting 4G networks properly of multiple operators that's why, for which I needed a custom recovery and for which I needed unlocked bootloader.
I just don't understand , all this so that no one could copy their ROM or I don't know for what . It's just makes things difficult for normal people and no one else. Locks can't keep a thief away. If anyone wants to break into their system than one will, if he/she uses right tools properly. Why make normal people lives' difficult?
ALSO I WANT TO ASK MORE THING, if in first case, I get into fastboot mode just after the ROM flash & before very first ROM boot and run this command and if in second case, the room gets booted and then I go into fastboot mode & run the command, DOES IT CREATES ANY CHANCE OF NON-OCCURRENCE OF THAT ERROR IN FIRST CASE?.
Click to expand...
Click to collapse
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
superboy123 said:
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
Click to expand...
Click to collapse
Thanks for all the support and help you gave me.
I got this error too but i forgot how to fix it.
Something about the 'disable driver signature' or the modified rom that you flash before you trying to unlock.
caesar13th said:
I got this error too but i forgot how to fix it.
Something about the 'disable driver signature' or the modified rom that you flash before you trying to unlock.
Click to expand...
Click to collapse
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
superboy123 said:
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
Click to expand...
Click to collapse
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
Gurkirat_Singh said:
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
Click to expand...
Click to collapse
By your name, I think you are an Indian, so which Sim you are using? You need to do a 4G pack recharge first to use LTE, VoLTE won't work in custom ROMs right now.
Edit: you could see this thread but this is a bit complicated: http://en.miui.com/thread-335643-1-1.html
superboy123 said:
By your name, I think you are an Indian, so which Sim you are using? You need to do a 4G pack recharge first to use LTE, VoLTE won't work in custom ROMs right now.
Edit: you could see this thread but this is a bit complicated: http://en.miui.com/thread-335643-1-1.html
Click to expand...
Click to collapse
I appreciate your help but the post you gave me is for non-asian countries so it will not work for me. As you already know I'm an Indian so that's why. Are you an Indian, only asking cause in that way you may already faced the problems i'm having.
I'm only familiar with only 2 4G networks for now. One is Airtel 4G, what they say have FDD LTE network, I don't what that is, but that's why it's not working on my phone, I contacted them and they said that my phone doesn't support it, I don't know why cause it support much more LTE Bands other than any smartphone in that price range. Second is Jio 4G, my sim gets detected, shows network in manual selection but doesn't get registered on them. I see only the message of 'No Service' or 'Emergency calls only' when I insert it.
@Gurkirat_Singh
It worked for me.
I had the same problem!
superboy123 said:
@Gurkirat_Singh
It worked for me.
I had the same problem!
Click to expand...
Click to collapse
What worked for you and how? Can you please answer/clarify my questions/doubts please also?
I tried that fix that I gave you and 4G started working for me. You cannot use jio on second sim slot. 2nd sim only connects to 2g.
superboy123 said:
I tried that fix that I gave you and 4G started working for me. You cannot use jio on second sim slot. 2nd sim only connects to 2g.
Click to expand...
Click to collapse
OK I'll try when got time and will update you with the result.

Redmi Note, Unlock bootloader (unoffical). oem unlock is not allowed while active

i tried to unlock my bootloader the offical way, but it apears to be impossible because their unlocking tool is very buggy and keep stucking at 50%.
so im doing it the unoffical way, after using this guide for unlocking https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492.
im stuck in a point where it says cant unlock bootloader because OEM is locked, i tried it 2 times while checking it is on in my developer settings.
the device now is soft-brick(i know how to get it out of it), and idea how to unlock the bootloader?
ty, and sry for my english i tend to be confusing sometimes.
EDIT:::: GO TO COMMENT 6, Solution for me was just waiting a couple of days(using legit method)
PIC:
http://imgur.com/a/38RsO
555satan said:
i tried to unlock my bootloader the offical way, but it apears to be impossible because their unlocking tool is very buggy and keep stucking at 50%.
so im doing it the unoffical way, after using this guide for unlocking https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492.
im stuck in a point where it says cant unlock bootloader because OEM is locked, i tried it 2 times while checking it is on in my developer settings.
the device now is soft-brick(i know how to get it out of it), and idea how to unlock the bootloader?
ty, and sry for my english i tend to be confusing sometimes.
PIC:
http://imgur.com/a/38RsO
Click to expand...
Click to collapse
Read my last post...
https://forum.xda-developers.com/redmi-note-3/help/unlocking-global-stable-rom-8-1-1-0-t3530467
You will be able to unlock officially.
And about soft brick ...
Use mi flash tool and flash mi Global stable rom.
Amirphp said:
Read my last post...
https://forum.xda-developers.com/redmi-note-3/help/unlocking-global-stable-rom-8-1-1-0-t3530467
You will be able to unlock officially.
And about soft brick ...
Use mi flash tool and flash mi Global stable rom.
Click to expand...
Click to collapse
so basiclly just wait 11 days and then try again?
555satan said:
i tried to unlock my bootloader the offical way, but it apears to be impossible because their unlocking tool is very buggy and keep stucking at 50%.
so im doing it the unoffical way, after using this guide for unlocking https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492.
im stuck in a point where it says cant unlock bootloader because OEM is locked, i tried it 2 times while checking it is on in my developer settings.
the device now is soft-brick(i know how to get it out of it), and idea how to unlock the bootloader?
ty, and sry for my english i tend to be confusing sometimes.
PIC:
http://imgur.com/a/38RsO
Click to expand...
Click to collapse
I have the same problem, I have tried countless times, but it would still show the same error, even though in the past I have performed this method countless times with 100% success rate, but now, idk why this error shows up.. I have a feeling that reinstalling the windows and then following the procedure again might solve the issue, but I dont wanna go through all that deleting and reinstalling stuff.
No need ro reinstalling windows.
Just install adb drivers and confirm u are using same sim card number in slot 1...which is used for login into mi account in phone and pc.
Amirphp said:
Read my last post...
https://forum.xda-developers.com/redmi-note-3/help/unlocking-global-stable-rom-8-1-1-0-t3530467
You will be able to unlock officially.
And about soft brick ...
Use mi flash tool and flash mi Global stable rom.
Click to expand...
Click to collapse
Amirphp said:
No need ro reinstalling windows.
Just install adb drivers and confirm u are using same sim card number in slot 1...which is used for login into mi account in phone and pc.
Click to expand...
Click to collapse
i have all adb drivers installed and working(downloaded the clockwork ones so they are legit working), tried putting in the sim in slot 1 same issue.
it seems like a lot of people are having issues with that bootlocker, it's a shame i was happy to buy this device and now i regret every moment
EDIT:
today it worked, basiclly the solution is to wait, shame they dont mention it themself, no need to insert the sim

Redmi Note 4X bricked constant reboot someone could helpme...

Hello I have a redmi note 4x completely briked..the phone has the bootloader blocked, when I turn it on it restarts and never gets to load the system, I have already flash by testpoint many rom, Miui developer, Global Stable and still in the same, The phone in fastboot mode and Revory (the original of the phone) does not restart, and during the flash by testpoint it is also maintained and never disconnected, I say this because I have read some cases that this happens. At the beginning of the problem he always came to show the three points that he is loading MIUI but there is a reboot, this is not anymore the case, now it never comes, sometimes it stays on when I leave it for a long time restarting but stuck only on the logo MI .... someone knows how to solve this problem, I can not send it to any technical service or anything in my country that does not exist ... greetings
I'm no expert, but I would go online and unlock the bootloader. Then follow this: http://c.mi.com/thread-334-1-0.html There might be other ways, but this one will work, even if getting Xiaomi to unlock the bootloader takes time.
Unlock bootloader, it takes 3 days for Xiaomi to approve it. Install twrp recovery, wipe everything and install some aosp rom.
ac00995 said:
Unlock bootloader, it takes 3 days for Xiaomi to approve it. Install twrp recovery, wipe everything and install some aosp rom.
Click to expand...
Click to collapse
I can not do that the phone don't loader the OS..
Not sure but I think you should install adb and fastboot on pc and then Connect your phone then try "fastboot devices" and if it shows you some device, it means that your device is plugged in properly then try "fastboot oem unlocking" command this would unlock your bootloader, well the big problem is that all these commands are with respect to the Linux pc, there are something similar to do with windows and worse thing is that xiaomi have different method for unlocking the bootloader as shown in other post
Bhanu_p_mishra said:
Not sure but I think you should install adb and fastboot on pc and then Connect your phone then try "fastboot devices" and if it shows you some device, it means that your device is plugged in properly then try "fastboot oem unlocking" command this would unlock your bootloader, well the big problem is that all these commands are with respect to the Linux pc, there are something similar to do with windows and worse thing is that xiaomi have different method for unlocking the bootloader as shown in other post
Click to expand...
Click to collapse
Thanks for your answer, but for unlock the bootloader of a Xiaomi Phone you need first apply and ask permissions with a mi account , after that use a sofware name Mi Unlock with the account login on the phone and on the MI Unlock software. Is the only way in Xiaomi's Phone. The big problen here is I can't get into the Android System I can't put my account in the phone for unlock the bootloader.
michelhdz9045 said:
Thanks for your answer, but for unlock the bootloader of a Xiaomi Phone you need first apply and ask permissions with a mi account , after that use a sofware name Mi Unlock with the account login on the phone and on the MI Unlock software. Is the only way in Xiaomi's Phone. The big problen here is I can't get into the Android System I can't put my account in the phone for unlock the bootloader.
Click to expand...
Click to collapse
I know that brother that's why I suggest you to use fastboot and adb as it works on some basic android phones and it is a kind of general method but I haven't tried it on mi phones
---------- Post added at 03:02 PM ---------- Previous post was at 02:54 PM ----------
Bhanu_p_mishra said:
I know that brother that's why I suggest you to use fastboot and adb as it works on some basic android phones and it is a kind of general method but I haven't tried it on mi phones
Click to expand...
Click to collapse
Have you tried any fastboot rom to unbrick your device, I have read your post where you have mentioned about flashing some ROMs but have not seen fastboot rom
you may use wipedata option in recovery mode, if you done have already backed up your data or you can sacrifise the data on phone,it will load the original recovery rom,than upgrade rom.....
michelhdz9045 said:
Hello I have a redmi note 4x completely briked..the phone has the bootloader blocked, when I turn it on it restarts and never gets to load the system, I have already flash by testpoint many rom, Miui developer, Global Stable and still in the same, The phone in fastboot mode and Revory (the original of the phone) does not restart, and during the flash by testpoint it is also maintained and never disconnected, I say this because I have read some cases that this happens. At the beginning of the problem he always came to show the three points that he is loading MIUI but there is a reboot, this is not anymore the case, now it never comes, sometimes it stays on when I leave it for a long time restarting but stuck only on the logo MI .... someone knows how to solve this problem, I can not send it to any technical service or anything in my country that does not exist ... greetings
Click to expand...
Click to collapse
Try flashing fastboot stock rom
I had same problem couple of days ago , i had custom rom installed on my redmi note 4 nd while i was reverting back to stock miui rom from my twrp backup i messed up nd ended up bricking my phone. I tried everything but gained nothing. In the end i tried flashing fastboot rom with mi flash tool and it worked. But i had my bootloaders unlock.dont know if it works with locked bootloader. I guess u should give a shot . Gud luck

A3 bricked after trying to flash stock and relock

I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
dephekt said:
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
Click to expand...
Click to collapse
I am new to this, my phone also seemed unusable and with the application "miflash" through windows, I put the official rom and came back to life.
It also happened to me that I had to change the USB port on the PC so that it didn't fail me ...
(I am using a translator)
marceloariel said:
I am new to this, my phone also seemed unusable and with the application "miflash" through windows, I put the official rom and came back to life.
It also happened to me that I had to change the USB port on the PC so that it didn't fail me ...
(I am using a translator)
Click to expand...
Click to collapse
Thanks for the reply. I actually tried this as well but it did not work. MiFlash just appears to be running the flash_all_lock.bat script on Windows and it failed because the bootloader was not already unlocked according to its debug logs when I ran it. I should have mentioned that above.
Not sure if it will help but did you try a factory reset?
Press and hold the Power+Volume Down buttons untill you see the android with the no command. Press and hold the Power button. Press and release the Volume Up button once then release the Power button. Then you should see some recovery options.
In can't get the phone to boot into recovery. Holding power and volume down just speedily reboots the phone into fastboot over and over. Using the volume up button instead just reboots the phone very fast. I never see the no command android.
dephekt said:
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
Click to expand...
Click to collapse
Try
Code:
$ fastboot set_active a
. This is an issue with the flashing script. Before the line fastboot $* flashing lock command it should have fastboot $* set_active a. Your phone is not booting to system partition because the bootloader wasn't told which partition (a/b) to boot from.
sensig said:
Try
Code:
$ fastboot set_active a
. This is an issue with the flashing script. Before the line fastboot $* flashing lock command it should have fastboot $* set_active a. Your phone is not booting to system partition because the bootloader wasn't told which partition (a/b) to boot from.
Click to expand...
Click to collapse
The issue is caused by fastboot rom containing dummy system_b image and flashing script "forgetting" to force partition A as active. If a phone has B as an active partition and someone uses flash_all_lock.bat script, the phone's screwed. No idea what brought Xiaomi to this "brilliant" idea, not only there is a higher chance to brick the phone, but the zip file is also unnecessarily larger.
With locked bootloader it isn't possible to switch active partition anymore, so the phone is a (semi)brick. EDL mode is usually used to reflash locked bootloaders.
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
debilinkredibile said:
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
Click to expand...
Click to collapse
There are two commands for setting active partition, depending on the fastboot version. It's either old
fastboot set_active a
or newer
fastboot --set-active=a
debilinkredibile said:
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
Click to expand...
Click to collapse
if you open flashing script file (.bat or .sh) in a text editor, you will see that fastboot is flashing system.img to system_a partition and system_other.img to system_b partition. That system_other.img is a dummy image and is not bootable. You either:
Option 1: Set active partition to A before running any stock flashing script.
Option 2: Replace system_other.img to system.img in the script.
Option 3: Force partition A after flashing userdata.img and before any lock or reboot command.
dephekt said:
In can't get the phone to boot into recovery. Holding power and volume down just speedily reboots the phone into fastboot over and over. Using the volume up button instead just reboots the phone very fast. I never see the no command android.
Click to expand...
Click to collapse
I am in the same exact position with my Mi A3... did you ever resolve this and if so how?
mewcatchew said:
I am in the same exact position with my Mi A3...
Click to expand...
Click to collapse
What causes led to this behavior ?
htn711 said:
What causes led to this behavior ?
Click to expand...
Click to collapse
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting). If I didnt know any better i'd think Xiaomi does this on purpose. I will never buy another Xiaomi.
mewcatchew said:
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting). If I didnt know any better i'd think Xiaomi does this on purpose. I will never buy another Xiaomi.
Click to expand...
Click to collapse
You can't blame xiaomi for your negligence.
If you don't know what you are doing then either don't do it or ask people here on the forums or do some research yourself.
Of course xiaomi are going to have the flash all lock option enabled by default because the only time people would really use mi flash is to completely revert back to stock.
All information on miflash online will tell you make slot a active slot before flashing in mi flash.
Most manufacturers are the same nowadays anyway it's not just xiaomi.
All relevant information is there you just didn't read it/weren't careful when you flashed.
Don't ever be afraid to ask a question here on the forums if your not sure, you will get help even if you think the question is too noob or stupid.
You can always try get your system up and going through edl mode but you will need someone with a verified xiaomi account to help you.
Always read the relevant information before trying anything on your device.
To say you won't buy xiaomi again is silly seeing as it was a mistake on your behalf, "I cut my finger so that means all knives are crap" is kinda how it sounds
mewcatchew said:
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting).
Click to expand...
Click to collapse
Due to the fact that i am a beginner in this business i also had my first encounter with the locked situation.
Did you read this: https://forum.xda-developers.com/showpost.php?p=81533691&postcount=22
...like garylawwd mentioned read/understand what you are doing BEFORE you do it.
After playing around with this device and read nearly everything about this topic here at xda i can say:
everything you need to know is here.
garylawwd said:
You can't blame xiaomi for your negligence.
If you don't know what you are doing then either don't do it or ask people here on the forums or do some research yourself.
Of course xiaomi are going to have the flash all lock option enabled by default because the only time people would really use mi flash is to completely revert back to stock.
All information on miflash online will tell you make slot a active slot before flashing in mi flash.
Most manufacturers are the same nowadays anyway it's not just xiaomi.
All relevant information is there you just didn't read it/weren't careful when you flashed.
Don't ever be afraid to ask a question here on the forums if your not sure, you will get help even if you think the question is too noob or stupid.
You can always try get your system up and going through edl mode but you will need someone with a verified xiaomi account to help you.
Always read the relevant information before trying anything on your device.
To say you won't buy xiaomi again is silly seeing as it was a mistake on your behalf, "I cut my finger so that means all knives are crap" is kinda how it sounds
Click to expand...
Click to collapse
Theres always a fanboy in the crowd. Whoever programmed the batch file at Xiaomi made an error on wich slot it shouldve been flashed to. I've flashed devices a 100 times and never had an issue like this until i got a Xiaomi.
Now did I miss I needed to be on slot A? Yes I did. Still its Xiaomi's error for releasing botched firmware. How exactly do I find someone with EDL authorized account in US? If you have one, or if you can point me to someone who has one i'd be happy as a clam.
As a side note, my mother is from Cork.
---------- Post added at 02:40 PM ---------- Previous post was at 02:30 PM ----------
htn711 said:
Due to the fact that i am a beginner in this business i also had my first encounter with the locked situation.
Did you read this: https://forum.xda-developers.com/showpost.php?p=81533691&postcount=22
...like garylawwd mentioned read/understand what you are doing BEFORE you do it.
After playing around with this device and read nearly everything about this topic here at xda i can say:
everything you need to know is here.
Click to expand...
Click to collapse
Did you read my posts? I get "locked state error" with fastboot commands. I can reboot bootlader in fastboot, and it tjust reboots into fastboot - thats just about all i can do. It wont let me change anything, can only get info and reboot...
mewcatchew said:
Theres always a fanboy in the crowd. Whoever programmed the batch file at Xiaomi made an error on wich slot it shouldve been flashed to. I've flashed devices a 100 times and never had an issue like this until i got a Xiaomi.
Now did I miss I needed to be on slot A? Yes I did. Still its Xiaomi's error for releasing botched firmware. How exactly do I find someone with EDL authorized account in US? If you have one, or if you can point me to someone who has one i'd be happy as a clam.
As a side note, my mother is from Cork.
Click to expand...
Click to collapse
Not a fanboy by any stretch of the imagination I just don't see it as an error on there behalf. They gave all relevant information on how to flash.
Someone already pointed out in a different thread of a guy that has the account here on XDA but I can't remember where I seen it. @_mysiak_ can you please let this guy know who has the verified mi account.
I hope you can get your device up and going and I do understand how frustrating this must be but it is fixable.
Hey maybe you can come visit Ireland with your mother and we can sort out the device then :laugh: joke
garylawwd said:
Not a fanboy by any stretch of the imagination I just don't see it as an error on there behalf. They gave all relevant information on how to flash.
Someone already pointed out in a different thread of a guy that has the account here on XDA but I can't remember where I seen it. @_mysiak_ can you please let this guy know who has the verified mi account.
I hope you can get your device up and going and I do understand how frustrating this must be but it is fixable.
Hey maybe you can come visit Ireland with your mother and we can sort out the device then :laugh: joke
Click to expand...
Click to collapse
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
mewcatchew said:
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
Click to expand...
Click to collapse
Ya I wouldn't go trusting some random Russian site either. I don't think there is anything you can do without either
A) going into edl and using a verified mi account
B) bringing it to a service centre (which nobody wants to do)
In fastboot you can't get any commands to work now right? Your device is fully locked again?
mewcatchew said:
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
Click to expand...
Click to collapse
That Russian site is run by the XDA guy from what I understood. There are other paid services which have Xiaomi service accounts, I only pointed you to the cheapest "verified" eshop. Just Google another one if you don't trust Russians. All of them will need to connect to your PC over Teamviewer and do the flashing, you will just follow the instructions (connect the phone, reboot it etc.).

Categories

Resources