hey everyone, sorry for most likely making another thread on the same topic but really wondering. im stuck in "red led flashing while plugged in" mode, not edl since nothing is detected no matter what usb or computer i plug the phone into. anyway around using a deep flash cable or test point method? most likely looking at ordering a deep flash cable but hey if you guys know something i don't then i'd appreciate it
Zaccary said:
hey everyone, sorry for most likely making another thread on the same topic but really wondering. im stuck in "red led flashing while plugged in" mode, not edl since nothing is detected no matter what usb or computer i plug the phone into. anyway around using a deep flash cable or test point method? most likely looking at ordering a deep flash cable but hey if you guys know something i don't then i'd appreciate it
Click to expand...
Click to collapse
I've heard that xiaomi has locked edl since stable 8.1.
Maybe that's the reason.
Sent from Note 3, Xiaomi Redmi Note 3.
mr.loverlover said:
I've heard that xiaomi has locked edl since stable 8.1.
Maybe that's the reason.
Sent from Note 3, Xiaomi Redmi Note 3.
Click to expand...
Click to collapse
Locked EDL???? What does that mean?
I was running Global Stable 8.1.6.0 just a week before, installed Lineage OS, hated the buggy camera, and reverted back to MIUI 8.1.6. And now I officially unlocked my Bootloader. I didn't face any such problem.
I had the same situation ie hard brick...as yours... I borrowed a deep flash cable from my friend which he ordered from alibaba shopping app...it helped flashing the fastboot ROM...follow the instruction for deep flash cable ie plug the USB in the computer while pressing the button then release it after few seconds and it would load USB qdloader 9008 hopefully..then ur ready to flash...this is what I did ....I think I hard bricked because I flashed some firmware that was corrupted I guess..(note I left charging my device for few hours and after flashing I rebooted immediately plugged in for charging )
@Zaccary Does your phone's bootloader has been unlocked?
exodius48 said:
@Zaccary Does your phone's bootloader has been unlocked?
Click to expand...
Click to collapse
Ya i officially unlocked my bootloader before hardbricking..I dunno exactly why this happened..may be it relocked.
.do u have any possible reason?because strangely sometimes I had to unlock again using miunlock tool...
Hard brick, yoy need deep flash cable. You can make it yourself or buy it in aliexpress.
Rohitagni said:
Locked EDL???? What does that mean?
I was running Global Stable 8.1.6.0 just a week before, installed Lineage OS, hated the buggy camera, and reverted back to MIUI 8.1.6. And now I officially unlocked my Bootloader. I didn't face any such problem.
Click to expand...
Click to collapse
Yeah. It's not the case with every phone/rom. But I've seen people complainimg that they can't unlock bootloader because of that.
I would share the link with you, but it's not in English.
Sent from Note 3, Xiaomi Redmi Note 3.
mr.loverlover said:
Yeah. It's not the case with every phone/rom. But I've seen people complainimg that they can't unlock bootloader because of that.
I would share the link with you, but it's not in English.
Sent from Note 3, Xiaomi Redmi Note 3.
Click to expand...
Click to collapse
Is that so? I never knew that!
Evanblast said:
Ya i officially unlocked my bootloader before hardbricking..I dunno exactly why this happened..may be it relocked.
.do u have any possible reason?because strangely sometimes I had to unlock again using miunlock tool...
Click to expand...
Click to collapse
Instal twrp from fastboot if you can access fastboot. Then instal rom from twrp.
But, if you can't access fastboot nor edl, then try DFC cable.
Related
Hi guys,
I got unlock permissions from Xiaomi today, and I wanted to install Cyanogenmod 13 beta 2 as I hate MIUI with passion. Yet I couldn't unlock my device ("Couldn't verify device" on 50% of verifying). Went through some googling, found out I have to update my 7.3.2.0.0 Global to Developer version. (Yes, I have that infamous 7.3.2.0.0 rom everyone hates and I am trying hard to get rid of it.)
So I tried it. Went to Updater, chose "Choose update package" and chose the package I've downloaded from official miui site, which was located in "downloaded_rom" folder in root right as official manual said.
And the phone turned off and started again.
Yet nothing happened. It just restarted without actually doing anything. My all data are as they were, my version is still 7.3.2.0.0 Global.
Recovery mode update doesn't work, as I don't get that usual recovery mode menu, but just a picture showing me I should plug my Redmi into PC (does nothing when I do).
Fastboot update has this notice underneath it: "If your device is locked. please click here to unlock it first." ... hell, I'm trying to do that whole time, that's why I need to change that ROM first.
I've ran out of options. And so I'm turning to you guys - help me, please.
I'm not an experienced user, haven't owned Android for like 3 years, although I've flashed some roms earlier. But I need to get rid of this vendor rom. Google play services are terribly unstable on it, for example.
Ask me any additional questions you need to know. I'm not married and I own a dog, for example.
Any help is appreciated. Thank you very much.
EDIT: That title doesn't really reflect my thread at all. I just wanted to talk about the first updating option, but then I started ranting about it all and couldn't stop. Please, forgive me the title isn't really pinpoint right.
EDIT2: My recovery looks like this: choimobile *dot* vn/attachments/vao-che-do-download-redmi-3-jpg.21534/ ... as a newbie user I can't post links, so please, exchange that *dot* for an actual dot and you'll see. I don't speak chinese.
I had that too, you need to flash it via fastboot
http://en.miui.com/a-234.html
Edit: or you could flash SpaceX via fastboot without unlocking bootloader, and then flash via the TWRP installed with that. People say that works.
Thing is, I can't see my device in MiFlash. No idea why - on "adb devices" it shows up without any problems, but in fastboot mode it just doesn't cooperate.
Could that be because I'm not using the original cable? Heard it can cause some issues. Can't try it atm sadly.
Sent from my Redmi 3 using Tapatalk
Barty19 said:
Thing is, I can't see my device in MiFlash. No idea why - on "adb devices" it shows up without any problems, but in fastboot mode it just doesn't cooperate.
Could that be because I'm not using the original cable? Heard it can cause some issues. Can't try it atm sadly.
Sent from my Redmi 3 using Tapatalk
Click to expand...
Click to collapse
In normal Google fastboot.exe, I couldn't see my device, but in MiFlash's fastboot.exe, I could.
Open the folder with the fastboot.exe you want to check if it's working, shift+right click and "open command window here", then run "fastboot devices".
Also, to open fastboot mode you need to use power + vol up and it opens to that image, no menu. Or was it vol down? Try the one that opens to that image directly, no menu.
Vol down it was. Anyway meanwhile you were writing your advice I've deleted some drivers that were apparently messing with my device and now I see it in MiFlash! Yay!!!
Well, let's hope I won't screw it now. I'm in a middle of SpaceX download. Should I try to MiFlash a normal MIUI with a locked bootloader, or should I do it through SpaceX?
Barty19 said:
Vol down it was. Anyway meanwhile you were writing your advice I've deleted some drivers that were apparently messing with my device and now I see it in MiFlash! Yay!!!
Well, let's hope I won't screw it now. I'm in a middle of SpaceX download. Should I try to MiFlash a normal MIUI with a locked bootloader, or should I do it through SpaceX?
Click to expand...
Click to collapse
What I did is I installed SpaceX MIUI 8 by ManhIT and it came pre-loaded with TWRP recovery and then I booted into the recovery by MIUI 8's updater app and bam....there you go. Now you can flash any ROM you'd like. Btw, I did this while my bootloader is still locked; never went to Xiaomi to unlock it for me. I've flashed several locked bootloader roms such as CM 13, CM12.1 , and locked versions of MIUI roms and I've never encountered any bricks....yet lol
I DID IT!
Not quite your way, to be honest - the fault was in my already installed (and faulty) PC drivers. Yet I did it with your support and I really appreciate the fact you were willing to help me with the problem. Thank you very much, mate.
Anyway, good night.
*a very happy Barty*
Barty19 said:
I DID IT!
Not quite your way, to be honest - the fault was in my already installed (and faulty) PC drivers. Yet I did it with your support and I really appreciate the fact you were willing to help me with the problem. Thank you very much, mate.
Anyway, good night.
*a very happy Barty*
Click to expand...
Click to collapse
Cheers to you my friend!!
So my phone just got stuck while normal usage. Tried restarting and the phone began boot looping.
Did plenty of research and finally decided to flash. Tried to flash using mi flash in fastboot mode but failed then google search made me realise my bootloader was locked. Did more research and decided to flash using test point EDL method.
Things went pretty well and the flash (miui v8) and the process became successful and when I powered my device the phone went back to boot loop again.
Tried flashing again and the result was the same.
It would be really helpful if somebody could actually help clear the issue. Did pretty much everything I could do as a newbie to flashing.
thank you!
There are 2 varients of rn4 one is mediatek(note 4x) and the other is Snapdragon so check if u flashed right firmware
thisbearisdrunk said:
There are 2 varients of rn4 one is mediatek(note 4x) and the other is Snapdragon so check if u flashed right firmware
Click to expand...
Click to collapse
No, I have flashed the correct file(Mido) and the flashing process went quite well but the problem still exists.
M i L i N said:
No, I have flashed the correct file(Mido) and the flashing process went quite well but the problem still exists.
Click to expand...
Click to collapse
How is ur phone being recognised in mi flash tool?
A serial number appears or something else like "com_port" appears?
thisbearisdrunk said:
How is ur phone being recognised in mi flash tool?
A serial number appears or something else like "com_port" appears?
Click to expand...
Click to collapse
It's recognised as COM4 the first time I tried then sometimes when I connect it shows COM3.
M i L i N said:
It's recognised as COM4 the first time I tried then sometimes when I connect it shows COM3.
Click to expand...
Click to collapse
If it recognises ur phone like that then flashing does nothing to ur phone so the only way is to go into edl mode and then flashing
https://forum.xda-developers.com/re...ool-redmi-note-4-edl-mode-o-removing-t3684024
Use this tool to go into edl mode and then flash
This thread can help ,because i bricked my phone once without unlocking the bootloader and the miflashtool recognised my phone like how it recognised urs and this thread saved my phone
Good luck
When i flashed the Evolution X Rom to Stock rom It Got Failed And My Device Is Not Turning ON.
Whenever I Tried To Install stock Rom using mi flash tool It Is Saying "Cannot Recieve Hello Packet" & write time out,maybe device was disconnected Please Help ME To Fix
The device is off?
Try to hold volume down and up at the same time and connect the usb cable to see if going to EDL mode.
If going to EDL mode you can flash a stock rom from edl with miflash.
papsr6 said:
The device is off?
Try to hold volume down and up at the same time and connect the usb cable to see if going to EDL mode.
If going to EDL mode you can flash a stock rom from edl with miflash.
Click to expand...
Click to collapse
Is not completly true... When the edl error "... Hello packet" appear is impossible. I also recived it when i tryed to make mia3-cce9 conversion. I retry many times but no success. Qualcomm port works, miflash connection works... But it's impossible to flash. I have searched every where on internet without succes. For me only fastboot flashing mode work. Not edl... I think this hello package is a software restriction of xiaomi. But i don't understand why some devices can bypass it and other fails
A question: you can enter in fastboot? I'm not sure you have try. Is the more simply solution. It's improbably that evolutionx had erase the bootloader... Connect phone to pc, then press power+vol- if you will see the xiaomy avatar.. you can recover the system. An advice for you: before flash a custom rom read with attention the guide. I suppose you haven't do this. And your modding level is low...
wetito said:
Is not completly true... When the edl error "... Hello packet" appear is impossible. I also recived it when i tryed to make mia3-cce9 conversion. I retry many times but no success. Qualcomm port works, miflash connection works... But it's impossible to flash. I have searched every where on internet without succes. For me only fastboot flashing mode work. Not edl... I think this hello package is a software restriction of xiaomi. But i don't understand why some devices can bypass it and other fails
A question: you can enter in fastboot? I'm not sure you have try. Is the more simply solution. It's improbably that evolutionx had erase the bootloader... Connect phone to pc, then press power+vol- if you will see the xiaomy avatar.. you can recover the system. An advice for you: before flash a custom rom read with attention the guide. I suppose you haven't do this. And your modding level is low...
Click to expand...
Click to collapse
I Had Tried EDL flashing from Unlock Tool Flashing Done Perfectly But Formatting Failed..Is it a partition error ?.. The Display is not turning on.. No Signal Only The Signal is Entering EDL mode
wetito said:
Is not completly true... When the edl error "... Hello packet" appear is impossible. I also recived it when i tryed to make mia3-cce9 conversion. I retry many times but no success. Qualcomm port works, miflash connection works... But it's impossible to flash. I have searched every where on internet without succes. For me only fastboot flashing mode work. Not edl... I think this hello package is a software restriction of xiaomi. But i don't understand why some devices can bypass it and other fails
A question: you can enter in fastboot? I'm not sure you have try. Is the more simply solution. It's improbably that evolutionx had erase the bootloader... Connect phone to pc, then press power+vol- if you will see the xiaomy avatar.. you can recover the system. An advice for you: before flash a custom rom read with attention the guide. I suppose you haven't do this. And your modding level is low...
Click to expand...
Click to collapse
papsr6 said:
The device is off?
Try to hold volume down and up at the same time and connect the usb cable to see if going to EDL mode.
If going to EDL mode you can flash a stock rom from edl with miflash.
Click to expand...
Click to collapse
My Phone Is Now Like This :
hishamhsm said:
I Had Tried EDL flashing from Unlock Tool Flashing Done Perfectly But Formatting Failed..Is it a partition error ?.. The Display is not turning on.. No Signal Only The Signal is Entering EDL mode
Click to expand...
Click to collapse
What you wrote is not good... I don't know unloock tool. But before use this applications is necessary read carefully the instructions. It seems you didn't have do this. Good luck. Ps: if your phone boot into fastboot reflash stock via miflash... If you don't have made a big damage it will work. Very import is select the correct slot before flash... In my case i always select slot a to make a clean and safe installation
wetito said:
What you wrote is not good... I don't know unloock tool. But before use this applications is necessary read carefully the instructions. It seems you didn't have do this. Good luck. Ps: if your phone boot into fastboot reflash stock via miflash... If you don't have made a big damage it will work. Very import is select the correct slot before flash... In my case i always select slot a to make a clean and safe installation
Click to expand...
Click to collapse
is mi authorized account needed
hishamhsm said:
is mi authorized account needed
Click to expand...
Click to collapse
Probably... Mee to i found this... But via fastboot is not necessary. Only with edl cold be necessary
wetito said:
Probably... Mee to i found this... But via fastboot is not necessary. Only with edl cold be necessary
Click to expand...
Click to collapse
no fastboot , no charging
wetito said:
Probably... Mee to i found this... But via fastboot is not necessary. Only with edl cold be necessary
Click to expand...
Click to collapse
will you help me to flash my phone via teamviewer
Sorry if you have damage bootloader (so fastboot don't work), the only way is edl. But i don't know how to solve edl flash fail. You had ask to other user, or search with Google. Or i'm afraid for you... Buy new phone. For the future if you want modding... Do it carefully
wetito said:
Sorry if you have damage bootloader (so fastboot don't work), the only way is edl. But i don't know how to solve edl flash fail. You had ask to other user, or search with Google. Or i'm afraid for you... Buy new phone. For the future if you want modding... Do it carefully
Click to expand...
Click to collapse
Thanks Bro Thanks For Your Support,.... Love From Kerala , India
Good luck
Same thing happened to me then i went mi authorised service centre and they charged 179rs and now my phone is working fine
azeem_saifi0411 said:
Same thing happened to me then i went mi authorised service centre and they charged 179rs and now my phone is working fine
Click to expand...
Click to collapse
is that phone under warranty while it was bricked
hishamhsm said:
is that phone under warranty while it was bricked
Click to expand...
Click to collapse
Sorry no. You have the bootloader unlocked... If your restore via edl will fail, in my opinion the best choice is buy a new phone. I don't know in your country. considerating that motheborard is not damaged... But phone must be open... The minum cost of this repair i think could be 100 € (convert in your currency). On YouTube there are a lot of tutorial how to do by yourself... But i'm not shure you have all skills...
wetito said:
Sorry no. You have the bootloader unlocked... If your restore via edl will fail, in my opinion the best choice is buy a new phone. I don't know in your country. considerating that motheborard is not damaged... But phone must be open... The minum cost of this repair i think could be 100 € (convert in your currency). On YouTube there are a lot of tutorial how to do by yourself... But i'm not shure you have all skills...
Click to expand...
Click to collapse
I Have Given It to A repair shop. They told me that that is emmc/UFS chip issue. So they will reprogramme the chip fix it and give the phone to me... They Told that it should fix..
Anyway I'm from India
hishamhsm said:
I Have Given It to A repair shop. They told me that that is emmc/UFS chip issue. So they will reprogramme the chip fix it and give the phone to me... They Told that it should fix..
Anyway I'm from India
Click to expand...
Click to collapse
I suppose that was the problem. I hope the repair shop in india are cheapest than in italy for the future... Make Modding with care
wetito said:
I suppose that was the problem. I hope the repair shop in india are cheapest than in italy for the future... Make Modding with care
Click to expand...
Click to collapse
Repairing cost around 10dollars . In India repairing cost is low but the price of mobile phones and spare parts are too high due to tax.
Thank you so much for your help and support bro. Love From India❤❤
Hi fellow developers.
So,my story is quite weird and expected indeed.
Being the noob I am at flashing custom roms and recoveries,I flashed orange fox recovery on my device,even flashed a custom rom and managed to use it for about 3/4 hours.
Then I thought that my device was ready, all my changes work,and it is a good idea to relock my bootloader.So,without flashing the stock recovery back,I relocked my bootloader.
After reboot,my device is stuck on "Red state" and keeps on rebooting after every 5 secs. I can't even boot to fastboot mode,nor can I completely shut down my device.
So any ideas what can I do? Do I need to go to the service center? If yes,what would they do and how much would they charge?
Thank you!.
Kaybee2611 said:
Hi fellow developers.
So,my story is quite weird and expected indeed.
Being the noob I am at flashing custom roms and recoveries,I flashed orange fox recovery on my device,even flashed a custom rom and managed to use it for about 3/4 hours.
Then I thought that my device was ready, all my changes work,and it is a good idea to relock my bootloader.So,without flashing the stock recovery back,I relocked my bootloader.
After reboot,my device is stuck on "Red state" and keeps on rebooting after every 5 secs. I can't even boot to fastboot mode,nor can I completely shut down my device.
So any ideas what can I do? Do I need to go to the service center? If yes,what would they do and how much would they charge?
Thank you!.
Click to expand...
Click to collapse
Not that only you should have the stock recovery to relock bootloader, you should need to return completely to stock to can relock it safely.
Follow this guide carefully https://forum.xda-developers.com/t/repair-dead-hard-bricked-realme-3-3i-tutorial.4224255/ replace all the files needed when it comes to your specific model.
Kaybee2611 said:
Hi fellow developers.
So,my story is quite weird and expected indeed.
Being the noob I am at flashing custom roms and recoveries,I flashed orange fox recovery on my device,even flashed a custom rom and managed to use it for about 3/4 hours.
Then I thought that my device was ready, all my changes work,and it is a good idea to relock my bootloader.So,without flashing the stock recovery back,I relocked my bootloader.
After reboot,my device is stuck on "Red state" and keeps on rebooting after every 5 secs. I can't even boot to fastboot mode,nor can I completely shut down my device.
So any ideas what can I do? Do I need to go to the service center? If yes,what would they do and how much would they charge?
Thank you!.
Click to expand...
Click to collapse
For future reference, NEVER re-lock the bootloader when your phone isn't 100% stock. The guide SubwayChamp linked above should work.
SubwayChamp said:
Not that only you should have the stock recovery to relock bootloader, you should need to return completely to stock to can relock it safely.
Follow this guide carefully https://forum.xda-developers.com/t/repair-dead-hard-bricked-realme-3-3i-tutorial.4224255/ replace all the files needed when it comes to your specific model.
Click to expand...
Click to collapse
Hey @SubwayChamp
I did try the method you recommended. But,my phone is not recognised as a mediatek device.They show all the connected devices as usb.
Kaybee2611 said:
Hey @SubwayChamp
I did try the method you recommended. But,my phone is not recognised as a mediatek device.They show all the connected devices as usb.
Click to expand...
Click to collapse
[GUIDE] REALME 7 RMX2155 GLOBAL BOOTLOADER UNLOCK
WELCOME, ALL. After a very tiring process of swapping between ROMs and changing regions, APKs, et cetera, we have finally been able to perfect the method for unlocking the bootloader of the RMX2155! This is a detailed guide aimed to give you an...
forum.xda-developers.com
Try following step one to eight inclusive. Should then recognize your device.
Kaybee2611 said:
Hey @SubwayChamp
I did try the method you recommended. But,my phone is not recognised as a mediatek device.They show all the connected devices as usb.
Click to expand...
Click to collapse
how much will service center charge for repairing it??
Hey for me same problem now in my narzo 30a.... can u fix that problem ? @Kaybee2611
daitama said:
how much will service center charge for repairing it??
Click to expand...
Click to collapse
I didn't bring it to the repair center, in my country no one knows about. IDK which the price could be, maybe 40 buckets.
hey as per my username i'm no good at this but i got this far. so I got all the files together did sd _shadow's guide unlocked bootloader etc., RSA method doesn't work for me so i am trying the regular fastboot option but my phone cant do fastbootd also my CPU is QUALCOMM
so can i run the flashfile.bat via regular fastboot or will it brick my phone.
well forget it i hard bricked it living up to my name.hopefully ill get it fixed
purenoob said:
well forget it i hard bricked it living up to my name.hopefully ill get it fixed
Click to expand...
Click to collapse
bricked can mean several different things.
No sign of life?
Window PC?
sd_shadow said:
bricked can mean several different things.
No sign of life?
Window PC?
Click to expand...
Click to collapse
no sign of life, no power no charge, i'm on windows if plugged in its detected in the device manager.
can this be fixed by anyone i feel really bad, i know it's just a phone but ya know.
purenoob said:
if plugged in its detected in the device manager.
Click to expand...
Click to collapse
That is a sign of life
Is my device in EDL Mode?
sd_shadow said:
That is a sign of life
Is my device in EDL Mode?
Click to expand...
Click to collapse
in device manager it says quadcomm hs-usb qdloader 9008. so by the looks of this it's a candidate for EDL mode .
i don't want to mess up anymore i think ill give this to a technician. gonna be a while is it ok to let the battery die.
came across a blank flash my phone is RETLA but the flash is RETBR does it matter ?
purenoob said:
came across a blank flash my phone is RETLA but the flash is RETBR does it matter ?
Click to expand...
Click to collapse
If the bootloader is unlocked it should be fine.
Don’t worry about the battery, edl is very low power, battery can last weeks, and should still support charging
sd_shadow said:
If the bootloader is unlocked it should be fine.
Don’t worry about the battery, edl is very low power, battery can last weeks, and should still support charging
Click to expand...
Click to collapse
bootloader was unlocked before all of this happened, so does this mean i can use a android 10 back flash or use an android 11 one for avoid trouble again.
sd_shadow said:
If the bootloader is unlocked it should be fine.
Don’t worry about the battery, edl is very low power, battery can last weeks, and should still support charging
Click to expand...
Click to collapse
ok so now i'm getting this error.
Opening device: \\.\COM5 [ 0.002] Detecting device [ 34.509] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error [ 34.510] Check qboot_log.txt for more details [ 34.511] Total time: 34.514s FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
YES!! finally i got it into flashboot mode i just had to hold the pwr button 10 sec and tried blackflash again.
now im gonna dl RSA to get the correct stuff for my phone.
Might be to early to say but Thank you so much for the help!. ill post back later to update you.
update: success on flash still on a11 dont care its working again money saved.
i Wanted to downgrade becuase since this update my YouTube at higher resolutions would stutter and some of my main games started to chug in certain places.
phone lil hotter etc you know the woes oh well its working now thanks a million thanks again.
purenoob said:
YES!! finally i got it into flashboot mode i just had to hold the pwr button 10 sec and tried blackflash again.
now im gonna dl RSA to get the correct stuff for my phone.
Might be to early to say but Thank you so much for the help!. ill post back later to update you.
update: success on flash still on a11 dont care its working again money saved.
i Wanted to downgrade becuase since this update my YouTube at higher resolutions would stutter and some of my main games started to chug in certain places.
phone lil hotter etc you know the woes oh well its working now thanks a million thanks again.
Click to expand...
Click to collapse
Hey just reporting back i thought i could bear with android 11 but i just couldn't. Being really really carefull this time i managed to return to android 10.
Using the fastbootd method before i ignored it and flashed in regular fastboot. So this time i followed every step to a tee.
just wanted you too know and as all always thx sd_shadow.