Helo!
I recently purchased a Redmi 3s which came with a fake rom so I decided to flash a new rom. I tried it via the updater app but it didnot work. Then after reading a few trick I tried the fastboot method but the process got stuck and now my phone cant boot. I was able to boot in fastboot and I see it in list of the devices but the mi flash tool keeps crashing.
Note: my bootloader is locked and I dont have any custom recover it was a stock phone.
Hi,
what means crashing? You get an error message?
You habe to try another MiFlash Version. The latest also didnt work for me.
You have to flash the latest developer rom to unlock the bootloader.
You can't flash ROMs through fastboot if your bootloader isn't unlocked... Never mind now you try to enter fastboot and flash a TWRP into it.
Yappuccino said:
You can't flash ROMs through fastboot if your bootloader isn't unlocked... Never mind now you try to enter fastboot and flash a TWRP into it.
Click to expand...
Click to collapse
I cant flash a reccovery because it says it is locked.
Apparently there's a method that involves using EDL mode and a deep flash cable, not sure if it'll work in your case or not
psychopac said:
Apparently there's a method that involves using EDL mode and a deep flash cable, not sure if it'll work in your case or not
Click to expand...
Click to collapse
Yes I heard about that but it seems a bit dangerous.
r.omega888 said:
Yes I heard about that but it seems a bit dangerous.
Click to expand...
Click to collapse
Considering that the said method restores your phone and you have a spare USB cable lying around, I'd say it's worth a try
r.omega888 said:
Helo!
I recently purchased a Redmi 3s which came with a fake rom so I decided to flash a new rom. I tried it via the updater app but it didnot work. Then after reading a few trick I tried the fastboot method but the process got stuck and now my phone cant boot. I was able to boot in fastboot and I see it in list of the devices but the mi flash tool keeps crashing.
Note: my bootloader is locked and I dont have any custom recover it was a stock phone.
Click to expand...
Click to collapse
same issue here, I was talking about my problem here
Trying to find a way to fix it, thanks!
If you have locked bootloaders, the only way to recover your phone is flashing ROM using MiFlash. To do it, you need to enter EDL. Now the only way for locked bootloader users is deep flash cable. You can google for guide how to make it. The trick is to connect green cable to the black one.
If you want to unlock bootloader and don't stuck at 50%, you need to flash a DEVELOPER ROM (International/Chinese, doesn't matter).
Forget all the complicated deep flash cable making guides. There's an ultra easy way to make one. Just strip off the outer jacket of a usb cable, about an inch or so, exposing the 4 wires inside. Then just push a pin or needle through the green and black wires like this guy has done. Easy peasy!
I made mine this way and was able to enter edl mode and flash a fastboot rom.
Related
EDL (Emergency Download) Mode has been removed/ disable from MIUI 8.1 onwards and Redmi 4A later Xiaomi devices. So you can flash MIUI Fastboot ROMs on your device by using Fastboot mode only, if your bootloader is unlocked. And, we can't use Qualcomm Jig Cable(s) also now.
So, we have only one way to know Qualcomm HS-USB QDLoader 9008 port from PC. It's Test Point Method. This method will work with every MIUI ROMs (Upgrade/ Downgrade) , Locked Bootloader/ Unlocked Bootloader and also work to recover from a Dead boot device (Bricked).
While touching these two points with a metal tweezers plugin the usb cable to the phone and PC will make the phone enter edl mode. You can then release the tweezers.
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command. Hope this helped :laugh:
rkmadotra said:
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command. Hope this helped :laugh:
Click to expand...
Click to collapse
Thanks for the explanation, in any case tere can be situations that fastboot it's not available, hard but possible, in that case that info is helpful...
TioCareca said:
Thanks for the explanation, in any case tere can be situations that fastboot it's not available, hard but possible, in that case that info is helpful...
Click to expand...
Click to collapse
In any case, the bootloader muz be unlocked to initiate EDL using ADB fastboot..
rkmadotra said:
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command.
Click to expand...
Click to collapse
:laugh::laugh::laugh:
what make you think they are so lame ? the result is :
failed ! remote device is locked. eom edl is not allowed
adrenochrome25 said:
:laugh::laugh::laugh:
what make you think they are so lame ? the result is :
failed ! remote device is locked. eom edl is not allowed
Click to expand...
Click to collapse
What makes you think I'm so lame as well. I have used this command and flashed my mi max 2 with fastboot rom. Tho I don't remember if bootloader was locked or unlocked. Probably it was unlocked. But still no issues as anyone can unlock thier bootloader officially.
i wasnt intended at you. it seems they forgot some ways when they first deployed the edl blocking access but with the most recent "roms" they have blocked every access way to edl when bootloader is locked : adb, fastboot & cable
the only way left is from internal pins, but we can expect they will hide them even better on new phones.
Today it's much worth to wait 72h (+30days if you just already unlocked another one today) than opening the models that have "non removable" batteries and risking to leave traces/damages
it's really a shame that xiaomi lock their phone this way, it's a very bad message at the users (fastboot is so much restricted that you cant even switch between stable&dev anymore with locked bootloader) but we still have the chance that they allow unlocking and that this unlocking is a real one allowing full control
Fastboot rom isn't needed untill we brick our device and we can't brick the device untill we have unlocked bootloader. So basically edl mode will work when it's really needed.
It doesn't work for my MM2. Got it since 4/12/17. Didn't know i need to login to mi acc to register my device, set usb debugging, developer's mode, unlock status...I had the phone for less than 2 hrs after updating to MIUI 9 from ver 8 (using the updater app) before it suddenly froze up, crashed and went into bootloop. I tried contacting xiaomi svc ctr but those clowns refused to help saying my device is china export.
I cldn't even get them to help me register my device on my mi acc using the imei & s/n info. So if anyone could offer some suggestions as to how I could ressurrect my phone, I wld be most grateful. Failing which the only avenue is to bring it to a svc ctr in China to get them fix it.
Rgds
My test points don't seem to work
I opened up my mi max2 and followed the steps to short the testpoints but my pc doesn't seem to pick up the Qualcomm device.
Anyway to trigger the thing so that the Qualcomm device can be detected?
Nike Lee said:
I opened up my mi max2 and followed the steps to short the testpoints but my pc doesn't seem to pick up the Qualcomm device.
Anyway to trigger the thing so that the Qualcomm device can be detected?
Click to expand...
Click to collapse
I managed to short the test points and got the Qualcomm HSB device on the device mgr, flashed the mi max2 with the latest global stable (V9.2.1) rom. But the phone is still stuck at the Android logo with 3 dots...
I wld have thought EDL flashing wld have wiped out everything on the phone and start afresh?
I am now thinking of formatting the entire phone and reflashing it again. How wld I do that?
Thanks for any inputs.
Hi, Does EDL with test point flashing refresh the boot partitions?
I have shorted the test points and successfully reflash the phone with the latest stable global ROMs (even back to MIUI 8.5.6) but just couldn't get the phone past the MI/Android logo after restarting it
If the boot partition files have been messed up and EDL flashing is not refreshing these files, no matter how many times I try to EDL flash the device, it's not going to help. Pls correct me if I am wrong.
Any other options I can try?
rkmadotra said:
Bro edl mode is not removed. It's just moved to fastboot. You can enter edl easily by "fastboot oem edl" command. Hope this helped :laugh:
Click to expand...
Click to collapse
bro thank u so muchhhhhhhhhhhhhhhhhhhhhhhh. it worked im so happy now...........was trying since hours....but u helped me mannn
Hey guys,
So the USB cable I was using to flash my fiance's ph-1 to an Oreo beta came unplugged halfway through the flash.
The phone is now in a bootloop. I can't get to recovery mode via VU+pwr or through the fastboot menu. I can use fastboot and my PC recognizes the phone. However, I forgot to tick allow bootloader unlock in Dev setting so I am unable to flash anything to the phone.
Edit: Wondering if there is still a way to get the phone recognized in QFIL with HS-USB mode... I have tried every button combination I can think of with no luck :/
Am I screwed?
Any help is greatly appreciated..
Cj250mills
cj250mills said:
Hey guys,
So the USB cable I was using to flash my fiance's ph-1 to an Oreo beta came unplugged halfway through the flash.
The phone is now in a bootloop. I can't get to recovery mode via VU+pwr or through the fastboot menu. I can use fastboot and my PC recognizes the phone. However, I forgot to tick allow bootloader unlock in Dev setting so I am unable to flash anything to the phone.
Am I screwed?
Any help is greatly appreciated..
Cj250mills
Click to expand...
Click to collapse
Ask essential for help, they should be able to sort this out. I think you'll have to send it back to them. In any case, please let us know how you manage to solve it.
Good luck
Sent from my PH-1 using Tapatalk
No luck from essential, they told me all they can do is offer an out of warranty replacement for 200 bucks. I really expected better from a company that actively promotes participating in their beta's so frequently online. :/
Doesn't make sense you must be leaving something out??
You couldn't have been flashing OB with a locked bootloader it would have just failed.
use fastboot getvar to check your bootloader status. if it is unlocked then unlock critical and flash the back to stock zip on this thread.
That will correct your issue they even have the OB3 out https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
You could even flash it through TWRP recovery as long as you bootloader is unlocked.
i shut down my device by tapping power off. then removed sim card and sd card after screen went black. but when i tried to power on, it doesnt respond.. i tried holding the power button for 10s, it gives me a black screen and vibrates and instantly closes again.. so i cant boot into recovery, i cant boot to fastboot, and its unreadable on pc, it doesnt charge, no bootlogo, nothing. just bricked..
.
i dont know why, but it just bricked by itself.. i've been using mokee 9 date of 1/1/2020 thats the last update i installed, with add on su and everything was working perfectly and even if i reboot multiple times..
bootloader was unlocked so xiaomi centers wont help me..
how is it possible to make it boot again? i mean like wtf even happened? i did nothing.. i didnt flash anything and system was READ ONLY before powering off.. all i did was remove sim and sd cards... even after flashing mokee updates yesterday, it booted normally and idk what's going on..
any help?
EDIT: the phone's hard disk IC was damaged. I went to a tech guy and he changed it but then the motherboard broke entirely after flashing the qcn file for imei. Device out of warranty of course because of the damn bootloader. Thank you xiaomi for the great phone that only lasted one month before dying completely.
attempt 2
in attempt 1 i tried force reboot as mentioned, didnt work
attempt 2 : i tried force reboot while plugged to pc, this showed up
attempt 3
i tried to flash a new firmware, but device unreadable. must be on fastboot mode for mi flasher to be able to read it. im starting to lose hope.. the device is new though it makes me sad
on some topic of a bricked phone online, someone mentioned that he should try EDL mode, by cmd command FASTBOOT OEM EDL
so i tried it many times until it said successful. but still didnt fix anything, because it didnt actually boot into EDL mode, had to open my device physically and use test points. so attempt 4 failed
does this mean fastboot works?
after attempt 4, it said successful so if fastboot works like that then i can flash stock boot.img or something.. right? which image should i start with
forum
boody shaban said:
on some topic of a bricked phone online, someone mentioned that he should try EDL mode, by cmd command FASTBOOT OEM EDL
so i tried it many times until it said successful. but still didnt fix anything. so attempt 4 failed
Click to expand...
Click to collapse
this is the forum of the bricked phone similar to mine, except that i didnt try any flash like him it just happened randomly
https://c.mi.com/thread-2334646-1-0.html
attempt 5
attempt 5 failed, i tried flashing whole firmware one by one, i started with vbmeta, then recovery but it failed. idk what to do
notice
i have noticed that it only flashes small img files, if its 100kb or more it will fail. maybe due to device restart because the only way to make it read in fastboot mode is to force restart multiple times until it flashes. what to do now?
attempt 6
so according to this video
https://www.youtube.com/watch?v=yJoIiLE_w3w
he installed a driver (name in attachment) then refreshed on mi flash so his device became readable on mi flasher
i tried that but it didnt work.
final attempt.. out of hope
found the possible solution. its called a deep flash cable, i will just go to any tech guy and ask him for help.
see attachment for info.
boody shaban said:
found the possible solution. its called a deep flash cable, i will just go to any tech guy and ask him for help.
see attachment for info.
Click to expand...
Click to collapse
In order to enter test point / EDL / 9008 mode, you have to physically open your device and connect two points on the phone's board. Search on YouTube for Redmi 7a EDL. If you get to EDL mode, you can flash original stock firmware via MiFlash.
Reason for brick
cg730620 said:
In order to enter test point / EDL / 9008 mode, you have to physically open your device and connect two points on the phone's board. Search on YouTube for Redmi 7a EDL. If you get to EDL mode, you can flash original stock firmware via MiFlash.
Click to expand...
Click to collapse
Yes, I hate tearing up my device so I took it to a professional. He failed to open ADL but he did the 9008. Now he waits some kind of credit. Not sure if for the app to work or for the bootloader to unlock, although it was already unlocked but maybe somehow got locked..
Any way, expected reason for brick is either latest magisk module, or kernel tweaks..
I gave the device to a professional, but he also failed to flash it even with test point. He said he was searching for a file.. I dont remember its name, something like IMOH..
Now I need to know any possible reason that might brick my phone again to avoid it
cg730620
Click to expand...
Click to collapse
cg730620 said:
.
Click to expand...
Click to collapse
The app he used was called ultimate multi tools
test point attempt failed
i did the test point, booted to 9008 mode but still nothing.
i think i know why the phone got bricked by itself, it got ARB stands for AUTOROLLBACK
read more about it here https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
bootloader got automatically locked again.
Never lock the bootloader if:
- your phone was delivered Chinese version and you flashed Global firmware
- your phone was delivered Global version and you flashed Chinese firmware
- you changed system, vendor, boot or recovery partition
- you installed a custom or modified stock rom
ARB isn't an issue with this phone I suppose. Because I was on 11.0.5 and rolled back to 10.2.5 without problems.
Have you tried MiFlash Pro?
See here:
https://forum.xda-developers.com/redmi-7a/how-to/miflash-pro-t4030809
---------- Post added at 04:01 AM ---------- Previous post was at 03:38 AM ----------
boody shaban said:
i did the test point, booted to 9008 mode but still nothing.
Click to expand...
Click to collapse
It seems that error is related to your computer. Reinstall drivers and MiFlash.
QDLoader Drivers:
http://www.mediafire.com/file/0jfq2r7adylnltu/QDLoader_HS-USB_Driver.zip/file
ADB driver:
http://www.mediafire.com/file/qskct06xyx1iivs/ADB%2Bdriver%2Bv1.17%2Blite.zip/file
MiFlash:
http://www.mediafire.com/file/bdjugf3zx7037yl/MiFlash2018-5-28-0.zip/file
Read about a similar problem here:
https://xiaomi.eu/community/threads/mi5-bricked-i-bricked-my-new-mi5-with-miui8.32439/
cg730620 said:
Never lock the bootloader if:
- your phone was delivered Chinese version and you flashed Global firmware
- your phone was delivered Global version and you flashed Chinese firmware
- you changed system, vendor, boot or recovery partition
- you installed a custom or modified stock rom
ARB isn't an issue with this phone I suppose. Because I was on 11.0.5 and rolled back to 10.2.5 without problems.
Have you tried MiFlash Pro?
See here:
https://forum.xda-developers.com/redmi-7a/how-to/miflash-pro-t4030809
---------- Post added at 04:01 AM ---------- Previous post was at 03:38 AM ----------
It seems that error is related to your computer. Reinstall drivers and MiFlash.
QDLoader Drivers:
http://www.mediafire.com/file/0jfq2r7adylnltu/QDLoader_HS-USB_Driver.zip/file
ADB driver:
http://www.mediafire.com/file/qskct06xyx1iivs/ADB%2Bdriver%2Bv1.17%2Blite.zip/file
MiFlash:
http://www.mediafire.com/file/bdjugf3zx7037yl/MiFlash2018-5-28-0.zip/file
Read about a similar problem here:
https://xiaomi.eu/community/threads/mi5-bricked-i-bricked-my-new-mi5-with-miui8.32439/
Click to expand...
Click to collapse
but im sure i have all drivers installed in fact i used mi flash more than once and it worked perfectly fine, and i swear i didnt try to lock it or anything, what happened is, mokee auto updates installed add on magisk and it was the latest version so i think this might have bricked it. idk..
ok i downloed all the drivers and reinstalled them, same error : "library not registered"
Hi
My phone stopped working a couple of days ago, I had been running a custom rom for 2 mths. I tried to restart and boot to recovery TWRP as I was going to reflash the rom. It charegs with no lights, for a day I couldnt boot to TWRP if it did it stayed on the start screen with no options. Today I can get options in TWRP so I tried to start fresh install but intstallation stops at step 1 ?
I have no idea what happened to the phone or why it just died, but dont understand why I can get into TWRP but cant flash rom etc. Also sometimes it say system destroyed message? but still can get into TWRP ?
Any ideas or help will much appreciated really would like to fix this rather than write the phone off.
Thanks
i think flashing firmware is the only option
ranjodhricky said:
i think flashing firmware is the only option
Click to expand...
Click to collapse
Hi, yeah I think thats what I try, is this flashing stock rom via MI flash or a different process?
try miflash if doesn't work try QFil
update
ranjodhricky said:
try miflash if doesn't work try QFil
Click to expand...
Click to collapse
Hi, been playing with this when i have time over the last few weeks.
I have been trying to flash firmware, I dont seem to be able to get QFIL to work for me, it wont reconsise the port. However MIFlash does but I get errors, sometimes it flashes but doesnt end? other times i have had error flashing modem_a or error flashing modem_b (maybe device is locked).
In ADB it says already unlocked. Also I can only boot into fastboot, not recovery so i cant intall anything from adb sideload, it wont boot into bootloader just powers off if i try this. I guess theres no recovery on it now as I cannot boot into it.
Any ideas on where to go from here , EDL? I really didnt want to attempt to open the phone.
Thanks
Try miflash 2019 with stock rom pie latest with edl mode
if bootloader unlocked You can enter edl mode via fastboot with the command 'fastboot oem edl'
Yincen said:
Try miflash 2019 with stock rom pie latest with edl mode
if bootloader unlocked You can enter edl mode via fastboot with the command 'fastboot oem edl'
Click to expand...
Click to collapse
Thanks, tried this, says success then just carries on , so i have to disconnect. However when then trying to boot the device it shows Android one logo and if im lucky after a few attempts it goes to the screeen saying Hi There, where you choose your language to set up the phone. However it nows seem to be unresponsve and frozen on that screen.
Im beginning to think its could be hardware issue and phone is just faulty, i really dont want to bin it as its imacculate condition seems a real shame, but it is 3 years old i guess.
Any further help or ideas much appreciated.
healy2k said:
Thanks, tried this, says success then just carries on , so i have to disconnect. However when then trying to boot the device it shows Android one logo and if im lucky after a few attempts it goes to the screeen saying Hi There, where you choose your language to set up the phone. However it nows seem to be unresponsve and frozen on that screen.
Im beginning to think its could be hardware issue and phone is just faulty, i really dont want to bin it as its imacculate condition seems a real shame, but it is 3 years old i guess.
Any further help or ideas much appreciated.
Click to expand...
Click to collapse
try doing a factory reset from Recovery , good luck
Hello. I have a rooted Nothing Phone 1 but as time passes, i decided i want to go back fully stock. I'm still on Nothing OS 1.1.0 and want to update to latest and (hopefully) greatest version (1.1.7). Sadly i accidentally clicked on download in the popup window that android shows you if you have outdated system version but thankfully it didn't install (otherwise i would end with bricked phone probably).
I was thinking about restoring the stock boot image right from magisk but i'm not sure about the consequences.
What is the right way to unroot Nothing Phone 1 and relock the bootloader?
PS: In case of hardbricking the device, could i simply enter the EDL mode without sorting test pins or buying custom EDL cable?
Pheggas said:
Hello. I have a rooted Nothing Phone 1 but as time passes, i decided i want to go back fully stock. I'm still on Nothing OS 1.1.0 and want to update to latest and (hopefully) greatest version (1.1.7). Sadly i accidentally clicked on download in the popup window that android shows you if you have outdated system version but thankfully it didn't install (otherwise i would end with bricked phone probably).
I was thinking about restoring the stock boot image right from magisk but i'm not sure about the consequences.
What is the right way to unroot Nothing Phone 1 and relock the bootloader?
PS: In case of hardbricking the device, could i simply enter the EDL mode without sorting test pins or buying custom EDL cable?
Click to expand...
Click to collapse
I think the safest thing would be to use directly EDL mode. You can boot into EDL with adb reboot edl if have a working phone so you don't need any fiddling with cables. I don't know if the EDL tool by @mark332 will lock the bootloader but even if it doesn't I think an EDL flash is the best thing to make sure that locking the bootloader doesn't result in a brick.