Related
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.
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"
Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.
So, basically I will make this short as possible
Due to some problems I had to sell my G6 Plus (Brazilian -8 model) but it was on a custom rom, and did the most dumb thing that I could do: Reflashing pure stock and locking it, I've used the LMSA tool then relocked in Fastboot, the thing is some files were corrupt and when locked, it doesn't boot up anymore, as i still had hope for it, I tried to LSMA again, but it doesnt recognize anymore, as the lock flag is now "Flashing_Locked", flashing manually via Fastboot gives a error related to the lock flag (also LSMA resets the device, so using my unlock key asks to enable OEM Unlock at settings, a impossible thing when OS is broken) , then searched for some solutions, first it was booting a Boot.img file from the last stock, which was the flashed one, it bootloops, then tried something on the recovery that works, but is the stock one and pretty limited, so the logical thing to do is flashing a OTA file, but only works for old versions that requires one version before the target one, so its a no go. The last thing i tried to do is booting TWRP, but it gets stuck on a red warning that indicates that system is corrupt. Then the last hope was EDL Mode, and thats the point where i want to go, i've bought a EDL Cable that's basically a green and black wire thing used on most Qualcomm based Redmi/Xiaomi devices, but it automatically boots to fastboot, so I need help to get EDL Test Points for this device, im with access to the board, i just need the right Pads to short-circuit it and blankflash it, so i can finally get it to work like normal again.
Schematics (for people who understands): https://androidfilehost.com/?fid=4349826312261726244
Any help is important, I'm sorry for some typos, english isnt my main language considering i didnt use translate
and please don't come with instructions like "have you tried LSMA?, try booting up the device and select oem unlock" because its clear that it doesnt work.
So im gonna start off by saying that im just some dumb 18 year old and have never actually posted to ask for help, only reading other peoples situations to try to figure out my own.
but introductions aside im just gonna jump in to everything wrong with my oneplus 8 pro (global)
I was on the OOS 12 beta for a while, ive been way too lazy to change it back since ive been occupied by other stuff.
I was using magisk and decided to do some fun shenanigans with it.
I get into bootloop after flying to close to the sun with modules - a common occurrence.
so I try to switch to a custom rom since I was gonna reset anyway.
I download CR droid's recovery and main rom, went into fastboot and flashed the recovery.
I notced that whenever my phone was plugged into the computer, the options would rapidly switch on fastboot's end
when I tried to boot to recovery after flashing, it would only return to fastboot
confused I thought that maybe the recovery was bad and try another rom, no dice
i submit defeat and go to msm tool to fix the issues
I get that "Sahara communication failed" error so I hold down the volume up + power for 13 seconds before trying again.
it flashed smoothly
after getting sad at all the bloatware that was on oxygen OS after a full reset, I get the motivation to try using a custom rom again, this time using a different rom.
same weird fastboot behavior
I was unable to go into recovery
I then tried downloading stock firmware to flash it manually
fixed nothing
I delete the boot and recovery partitions and flash them again, still no dice
I even make a partion called fart, before remembering that I do not know the partition structure of android so i Ctrl+C out before it makes the partition
I go back to msm tool again in shame
"Unknown Target Device"
I reinstalled drivers
switched computers and cables
changed the source of my drivers
nothing fixed this error
and every time I would try to do anything it would go directly back to fastboot.
I try reflashing partitions in this broken fastboot mode and it would only flash if I unplugged, selected reboot bootloader, and plugged it back in
I would then try to fastboot boot into TWRP or other recoveries i downloaded
they would shut off the phone
I remember a/b partitions exist so I switch over between them and try to flash stock OOS again
after more fiddling and nothing working, I noticed some more weird traits of fastboot
twrp did boot directly after switching my main slot, not specific which one just if the slot was changed.
the "this device has an unlooked bootloader" message did not appear
only on slot a would the oneplus logo show up on boot
again every option I would click would take me right back to fastboot.
I wait a day for the phone to die so I could use EDL that way, at this point the twrp method randomly stopped working so I couldn't go into edl that way.
"Unknown Target Device Param Preload"
and like I know Param Preload is a common error but nowhere could I find information on the unknown target device part.
the phone still vibrates if I hold the power and vol+
it just vibrates in a loop as if it keeps rebooting, probably fastboot just selecting the start key over and over when I hold it down.
vol- and power do nothing, and did nothing for the entirety of this story.
is there any chance of saving my poor instantnoodle professional?
## edit for people googling this
the problem I was having was that I didn't set the "target" button on the MSM tool correctly, so make sure its set to O2 or your appropriate reigon
1. Stop fastboot flashing with A12 or if you are on A12.
2. Read this: https://forum.xda-developers.com/t/...ro-8t-9r-with-oxygenos-12-coloros-12.4426167/
3. Rescue your phone using this: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
4. Stay on OOS11 (Most custom roms INCLUDING A12 custom roms require OOS11 anyway.)
5. There is not much bloat on a OOS11 rom IMO but you can always use a debloater.
xtcislove said:
1. Stop fastboot flashing with A12 or if you are on A12.
2. Read this: https://forum.xda-developers.com/t/...ro-8t-9r-with-oxygenos-12-coloros-12.4426167/
3. Rescue your phone using this: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
4. Stay on OOS11 (Most custom roms INCLUDING A12 custom roms require OOS11 anyway.)
5. There is not much bloat on a OOS11 rom IMO but you can always use a debloater.
Click to expand...
Click to collapse
Maybe I should clear on what i have tried. since I have read both articles before I made this post (i scanned through them again once you sent them tho)
Ive tried...
The unbricking Msm qualcomm 9008 tool
ive used it a ton in the past
ive switched copmputers, cables, and the qualcomm driver, as well as reset the phone several times
also yeah im not touching oos12 after this with a 9 foot pole, but is there a way of knowing wether I can save it or if its too late and the motherboard has been fried.
NatunaSushi said:
Maybe I should clear on what i have tried. since I have read both articles before I made this post (i scanned through them again once you sent them tho)
Ive tried...
The unbricking Msm qualcomm 9008 tool
ive used it a ton in the past
ive switched copmputers, cables, and the qualcomm driver, as well as reset the phone several times
also yeah im not touching oos12 after this with a 9 foot pole, but is there a way of knowing wether I can save it or if its too late and the motherboard has been fried.
Click to expand...
Click to collapse
Okay i guess this is another situation here. You are not bricked like the other peoplke as far as i can see because there devices are completly bricked. No connection to pc or vibrating at all.
Since you used MSM tool before it should work IMO. Does your pc regonize the phone? Did you tried to switch usb ports? Did you tried other versions of msm tool(eu, older verions, etc)?
Please make sure to follow all MSM instructions closely.
xtcislove said:
Okay i guess this is another situation here. You are not bricked like the other peoplke as far as i can see because there devices are completly bricked. No connection to pc or vibrating at all.
Since you used MSM tool before it should work IMO. Does your pc regonize the phone? Did you tried to switch usb ports? Did you tried other versions of msm tool(eu, older verions, etc)?
Please make sure to follow all MSM instructions closely.
Click to expand...
Click to collapse
after a week of fiddling I DID figure out the issue
unsupported Target unknown was refering to the fact that I had the MSM tool set to Target mode, which I assume tries to set the region according to what the current device has. After selecting that to O2 for the global models, the flash worked fine. I ended up coming across some C stock of a google pixel 3a and will try messing with that so I dont have to go a while without calls or texts. Glad to know I learned some bit of responsibility from this excursion.