Many people like me did buy its Xiaomi Mi 5S from Chine wich official Chinese ROM. The problem of this ROM is that unless you are Chinese you dont really enjoy it. But now since the official Global ROM was released all was supposed to be saved and beautiful. Except you could not flash it using the built-in flashing (update) tool of the ROM it just would not recognize it as valid and thats that.
First and most recognized solution you would find is Unlock bootloader and flash it via fastboot (MiFlash windows app). In order to unlock a Xiaomi you have to Apply for unlock and give them specific reason to grant you your wish (pretty lame). Than after unlock it will work. It takes them less then 10 days (official Xiaomi), if not you should write on their forum. Not sure if anyone did not get it, but its still stupid.
There used to be option to do this using EDL mode (or Download mode), but there is no EDL in Mi 5s any more, so no luck here either.
So here is option number two that will always work without unlocking bootloader. It will even work with bricked phones. It is called Deep Flash. This option works only with Qualcom machines (f.e. Snapdragon) and what it does is, it connects your smartphone to your computer via one of COM ports using the Qualcom drivers. Dont ask me how exactly, I dont know, dont care. It just works The whole point of this method is the Deep Flash Cable, you need it and you either make it yourself (real easy) od buy one on Aliexpress (easier, but you have to wait long).
Here is video with the procedure of deep flashing: https://youtu.be/tdk0d2Zrm9w
Here is an OK website with the whole procedure including how to make Deep Flash cable: http://www.stupdroid.com/2016/10/make-xiaomi-deep-flash-cable-and.html
Here is link to the official FASTBOOT Global ROM: http://en.miui.com/thread-454687-1-1.html
Here is link to MiFlash tool: http://en.miui.com/thread-345974-1-1.html - I beleive the new version already has Qualcom drivers included.
If windows was making you trouble and your Qualcom driver will not install here is why: http://en.miui.com/thread-237673-1-1.html
I also attach pictures of my cable and a schematic of what you are actually doing. It is really a simple thing to do. It took me like 20 minutes. No special skills required, and I used only sharp knife, did not even have a razer. I used some random cable, not genuine Xiaomi cable as the guide says. I used non copper cables to connect B and G (I canibalized some other old USB cable).
IMPORTANT NOTE, keep with the flash procedure exactly as it says, or you will get errors ("cannot receive hello packet") when flashing like I did.
1. MiFlash is not running on your PC, Your phone is turned OFF, The two cables (B and G) are connected together, Your Device Manager is ON
2. You connect the Deep Flash cable to your PC use USB 2.0 port (USB 3.0+ are reported not to work)
3. You connect the Deep Flash cable to your Mi5S
4. Wait for 10 seconds. (just count to 13 or something) - apparently this may save you from the "hello packet" error
5. You disconnect the two cables (B and G) - in Device Manager you will see something like Qualcom HS-USB Diagnostic 9008 - keep cables disconnected
6. Only now you launch MiFlash by going to C:\XiaoMi\XiaoMiFlash and Right-clicking on XiaoMiFlash.exe and Run as Administrator
7. In MiFlash tool Press Refresh button - you will see your phone on one COM port
8. Browse to your Global Rom (f.e. capricorn_global_images_V8.0.3.0.MAGMIDI_20161222.0000.00_6.0_global) under this folder you will see folder named image
9. Press Refresh one more time
10. Press Flash and have a coffe (took mine 5 minutes)
11. After you see nice green success you turn off MiFlash
12. Disconnect the cable from phone
13. Boot the phone - dont panic first boot is very long
There ya go. You are now on Xiaomi Mi5S with Global ROM with still locked bootloader. This guide should work with Mi5S Plus, but I did it on my Mi5S only.
Special thanx to XN Logos and his post about unbricking. This one is literarly the same method. But I myself ran around that post 10 times when searching for solution to my problem and never knew this in fact is solution to my problem aswell :silly:
Thanx to awaaas for mentioning the disclaimer about USB 3.0 ports.
Thanx to cerietke for mentioning the 10 second pause in step 4.
Great guide! Unfortunately I have unlocked my device to change to global rom. Hopefully it will benefit other. UP!
I tried following these instructions but have ran into one problem which I managed to solve. In case MiFlash shows an error "cannot receive hello packet" you have to make sure adb driver is installed. More about this is written in this topic: en.miui.com/thread-299790-1-1.html
You can make a backup with built in MIUI app, then copy it to your pc and restore after flashing.
Now I can enjoy a ROM without crappy chinese apps and all notifications are working from the beginning.
Are there any advantages of deep flash method over standard with unlocked bootloader?
Rejerf said:
Are there any advantages of deep flash method over standard with unlocked bootloader?
Click to expand...
Click to collapse
Well you do not have to unlock the bootloader for once. But other than that, no, there are none. But with Xiaomi you have to be approved for unlock case by case and it takes them approx 3 days. But it is just flashing. ROM is the same.
i try this prozedre with help by simply silver paper. what should i say, this also works. xdddd
neverless, i still wait for the "deep flash" cable from aliexpress.
best regards
I tried everything, with the lots of guides, I made my own deep flash cable, I succeeded in putting my mi 5s Plus into deep flash mode but did not succeeded in flashing the Rom.
Every time there is the error message from the Mi flasher cannot receive hello packet etc. Then I applied for unlock boot loader officially. I got SMS with the unlocking permission in 15 minutes. After unlocking boot loader, I put my phone into fast boot mode and flashed fast boot Rom and everything is fine. No error ..nothing. So, I do not want to disappoint anybody, but this method did not worked for me.
Just want to add a note, this method would not work if you use USB 3.0+ port (or USB 2.0 behind USB 3.0 hub) such as on a intel's skylake/kabylake-based machine.
Maybe that's your problem @richie16171?
richie16171 said:
I tried everything, with the lots of guides, I made my own deep flash cable, I succeeded in putting my mi 5s Plus into deep flash mode but did not succeeded in flashing the Rom.
Every time there is the error message from the Mi flasher cannot receive hello packet etc. Then I applied for unlock boot loader officially. I got SMS with the unlocking permission in 15 minutes. After unlocking boot loader, I put my phone into fast boot mode and flashed fast boot Rom and everything is fine. No error ..nothing. So, I do not want to disappoint anybody, but this method did not worked for me.
Click to expand...
Click to collapse
Good point from awaas I did not know that. Try that too.
But I was getting the same error as you. What you need to do is follow my instructions religiously. It made difference to me when I skipped some point or did something parallel. Do exactly as my guide says. Disconnect and turn everything off and start from point one exactly like the guide says.
I remember it was different when I had flashing tool open before and after some point. So go exactly as the guide and you should be fine
awaaas said:
Just want to add a note, this method would not work if you use USB 3.0+ port (or USB 2.0 behind USB 3.0 hub) such as on a intel's skylake/kabylake-based machine.
Maybe that's your problem @richie16171?
Click to expand...
Click to collapse
Nope ..it was USB 2.0 and I am using laptop. I tried all the ports in the computer. Tried with another computer and not once 7 times.
---------- Post added at 02:24 PM ---------- Previous post was at 02:07 PM ----------
Seehank said:
Good point from awaas I did not know that. Try that too.
But I was getting the same error as you. What you need to do is follow my instructions religiously. It made difference to me when I skipped some point or did something parallel. Do exactly as my guide says. Disconnect and turn everything off and start from point one exactly like the guide says.
I remember it was different when I had flashing tool open before and after some point. So go exactly as the guide and you should be fine
Click to expand...
Click to collapse
I did exactly what you said 100%. As I said not once.., with driver signature off and on. I did not had any driver problem. It was showing me the port com16.
I think that is not the right port for flashing.
richie16171 said:
Nope ..it was USB 2.0 and I am using laptop. I tried all the ports in the computer. Tried with another computer and not once 7 times.
---------- Post added at 02:24 PM ---------- Previous post was at 02:07 PM ----------
I did exactly what you said 100%. As I said not once.., with driver signature off and on. I did not had any driver problem. It was showing me the port com16.
I think that is not the right port for flashing.
Click to expand...
Click to collapse
Well man, than this is the end of me :-/ I know I was getting this error when I had MiFlash turned on before I connected my phone to the PC . That gave me same error. But when it was off before and after deep flashmode a opened it up as admin (from the directory, not Start) it worked for me just fine.
Does anyone know if this works in 8.2? When I plug cable in it starts charging..
Agirretxd said:
Does anyone know if this works in 8.2? When I plug cable in it starts charging..
Click to expand...
Click to collapse
The 8,2 hasa big problem with battery drain. Mine 5s has poor battery life now. Just wait a bit.
Is there any work being done on official Lineage OS for the Mi5S?
richie16171 said:
I tried everything, with the lots of guides, I made my own deep flash cable, I succeeded in putting my mi 5s Plus into deep flash mode but did not succeeded in flashing the Rom.
Every time there is the error message from the Mi flasher cannot receive hello packet etc. Then I applied for unlock boot loader officially. I got SMS with the unlocking permission in 15 minutes. After unlocking boot loader, I put my phone into fast boot mode and flashed fast boot Rom and everything is fine. No error ..nothing. So, I do not want to disappoint anybody, but this method did not worked for me.
Click to expand...
Click to collapse
Hey,
I just tried to reflash mine and just like you said I was getting all the errors. No way to fix it But then I uninstalled (also deleted every single file) the MiFlash tool and after installing it again it worked Sooo probably there is some log file or some setting or I dont know what that is doing trouble.
@ Seehank., Thank you so much, Maybe that is the problem... otherwise so many people succeeded doing this, Only I failed.
Now no point. I already unlocked boot loader and flashed the firmware. And that also I flashed in fast boot mode.
Now I have one more Mi note3 pro. And it is the used phone. Someone already unlocked boot loader. That is why or for some reason I was not getting OTA update. Hence the boot loader is unlocked, and I tried to flash with the fast boot mode.. No.. I am getting error. In flash tool it is not showing Com Port..instead some serial number. So I flashed that in EDL mode and success. After that now I am getting OTA update.
Hope this may help others with the hello packet issue.
I was following your guide, but I was going through pretty quickly, which turned out to be relevant. I did some searching on the issue and discovered a post on en.miui.com that suggested a solution (post 32 in the "[Help]-cannot receive hello packet,MiFlash is trying to reset status" topic; as a new user I cannot post outside links). Apparently you'd need to wait at least 10 seconds between step 3 and 4. As I also did a full reboot of the phone without the cable attached that may have also been the solution. I did not further test as I got it working.
Hi guys, have locked phone on purchase, thought I might revive it with above methode but...no way I coulkd install quallcomn drivers, tried (i think) everything, phone gets into charging mode, nothing happens in Device manager...
cerietke said:
Apparently you'd need to wait at least 10 seconds between step 3 and 4.
Click to expand...
Click to collapse
I will add this to the guide. It can not harm anyone So between my guide and steps 3 and 4 wait 10+ seconds.
Hi mate, i followed your guide, everything works till the very last point, when i boot my phone (after the success message in the MiFlash), 2 strange things happen:
1) first time i press "power" button it wont start, i press a second time and it starts
2) the MI logo starts blink every x minutes, but actually is not going forward (still stuck on MI logo after more than 10 mins waiting)
can you help me somehow? Thanks
So for reference I own a 2015 shield TV 16gb model. I've debated rooting and such but never followed thru with any of it. It was running 5.0 stock and kept prompting me for the 5.1 update which could (?) be the culprit. Anyway got home from work yesterday and it wasnt booting. I tried booting into recovery and clearing the cache, nothing. Then tried a factory reset, nothing. So I found the Recovery image for it and proceeded to flash it. After flashing the staging blob (Which is successful) It gets hung up when I try to flash the boot.img. I've tried re-downloading as well as trying the 5.1 image and nothing has worked. Has anyone else experienced this?
bsutton said:
So for reference I own a 2015 shield TV 16gb model. I've debated rooting and such but never followed thru with any of it. It was running 5.0 stock and kept prompting me for the 5.1 update which could (?) be the culprit. Anyway got home from work yesterday and it wasnt booting. I tried booting into recovery and clearing the cache, nothing. Then tried a factory reset, nothing. So I found the Recovery image for it and proceeded to flash it. After flashing the staging blob (Which is successful) It gets hung up when I try to flash the boot.img. I've tried re-downloading as well as trying the 5.1 image and nothing has worked. Has anyone else experienced this?
Click to expand...
Click to collapse
What do you mean with "hung up" ?
And are you certain you have the correct image downloaded?
(And did you make sure that you didn't just execute the flashall.bat? Because that's not the best way to flash the firmware, they should have left that one out....)
So are you able to boot into fastboot/bootloader mode in a stable way or does it reboot few seconds after booted up in that mode?.
First try with other USB cables (this is a well known issue, the Shield TV is picky), use the rear usb ports or your PC (the ones that are soldered to the motherboard) and avoid using usb 3.0+ ports.
If using a 4k or UHD TV, try with an up to Full HD TV or Monitor.
Do not mess with the bootloader (blob file), there was no need for you to flash that. Only corrupted bootloader flashing will hard brick your device, so be careful with it.
While you be able to boot into fastboot mode you can fix/recover your device.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
USB cable or USB port?
I had a similar thing happen with my SATV 2015 16GB model. Turns out it ended up being the USB3.0 ports on my Dell 5510 giving me grief. Each time I tried to adb the image files it was failing at different times. I made sure and got a good USB cable and used another PC with USB2 and it flawlessly put stock back on the shield. If you can fashboot, you can bring it back.
I accidentally downloaded the wrong image file and flashed the 2017 boot, system, and vendor images to my 2015 SATV.
The system still boots Android but throws constant errors. ADB shows no devices connected so adb reboot bootloader won't work. I've also tried to boot fastboot using both the 2015 and 2017 hardware methods but neither work, probably because the 2017 boot.img isn't checking for the power button press and the 2015 gamepad or base is missing something to invoke fastboot.
My one hope is that it might be possible for a 2017 gamepad to invoke fastboot on a 2015 base but I'm wondering if anyone has other ideas or knows if that won't work.
https://youtu.be/2AzHF-uNiY8
Try with other(s) usb cables too. You can't hard brick that way if you didn't touch the bootloader.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
Unfortunately I did flash the boot.img with the wrong model file however after several more tries and making sure the PC was connected during boot I was finally able to get back into fastboot using the power button method and re-flash the correct files.
Thanks for the tip though.
kylehase said:
Unfortunately I did flash the boot.img with the wrong model file however after several more tries and making sure the PC was connected during boot I was finally able to get back into fastboot using the power button method and re-flash the correct files.
Thanks for the tip though.
Click to expand...
Click to collapse
which image did you use for the nVidia Shield TV 2015 (16gb)? I download this one: NVIDIA SHIELD ANDROID TV Recovery OS Image 5.2.0 2017/06/15 ---But for some reason I keep on getting boot loop even after restoring to stock.
The first (wrong) one I flashed was nv-recovery-image-shield-atv-2017-5.2.0.zip. The correct one for 2015 16G model is nv-recovery-image-shield-atv-5.2.0.zip
After I flashed the correct one it's been running fine with existing data in place.
kylehase said:
The first (wrong) one I flashed was nv-recovery-image-shield-atv-2017-5.2.0.zip. The correct one for 2015 16G model is nv-recovery-image-shield-atv-5.2.0.zip
After I flashed the correct one it's been running fine with existing data in place.
Click to expand...
Click to collapse
Thanks for confirming I am using the right rom. I decided to send the item for RMA.
Hello!
I've recently got a Silverstrong Android 9 Head Unit: https://www.aliexpress.com/item/32822937592.html?spm=a2g0s.9042311.0.0.328e4c4dWZb7Fi
Can someone help me on how to get adb access or a custom recovery (mainly for rooting purpose)?
I have to mention that I've tried connecting a notebook with adb via and USB cable (male USB type A to USB type A), but it seems nothing happens. I can tell that the unit's USB ports are working for USB sticks.
I have also tried some combination implying the reset hole present on the front, but I couldn't make it work.
Any help is appreciated! Thanks!
Edit: I have to mention that the unit packs a MediaTek MT8321M if it matters.
Just an update: I have followed the instructions provided here for rooting: https://forum.xda-developers.com/showpost.php?p=76725981&postcount=740 . Everything went well until I tried to reboot the device. Now it is stuck in a bootloop (it passes the kernel bootlogo but it is stuck on Android bootlogo) and I really need to access its recovery. It would be my only hope to try to unbrick it. Unfortunately the only physical switch of the unit is just a reset hole on the front which will cut the power right away (tried multiple pressing combinations, none worked). I really need to enter recovery mode and I am pretty desperate, so any advice is welcome. Thanks!
I couldn't make it boot into recovery mode, but it did boot when I placed on a usb stick a file named "ZQ_MTK1B_UPDATE_HeXinDa_EN_8003_08152051.zip" and then it started to flash it automatically. After the flash completed, the unit recovered from bootloop, but now it seems there is no sound and no radio. I posted all of this just in case somebody ever will have to deal with same kind of trouble. It seems the unit is actually branded as alps ZQ8003 and I will ask the seller for some firmware/more technical info.
Hi, I have the same problem. Did you make it?
I was looking to install LineageOS 18.1 and was having a hell of a time.
I was following the instructions, and I can get as far as booting into the LineageOS recovery, but then I can't navigate to ADB using the front button on the box. I am also finding it difficult to find a working OTG cable that works and has the ability to provide power. (so I can remove the USB cable from my laptop and plug in a USB keyboard without powering off the android box)
Anyone have any tricks or suggestions on a OTG cable or USB switch they know works on this? Or better yet, how to get the front navigation button working on the Onn Box working ot how I can enter recovery mode if I try fastboot flash (Impossible to enter recovery instead of boot to OS) instead of fastboot boot?
Here are the instructions I was using. Great until you get to the fastboot flash, since once you reboot it goes straight into the OS and will over right the custom recovery. Then when I fastboot boot, it works, but then the navigation button doesn't work to get to the next step. lol.....
Install LineageOS on dopinder | Odd Solutions Wiki
wiki.oddsolutions.us
on a side note, I have a OTG cable that splits and works on my laptop to fastboot boot the recovery. But once I am in the LineageOS recovery and connect a USB keyboard, it doesn't respond either. (So maybe the LineageOS recovery is the problem?)
I've tried both from https://updater.oddsolutions.us/#/devices/dopinder/builds
lineage-18.1-20220324-recovery-dopinder.img
lineage-18.1-20220317-recovery-dopinder.img
I also tried the 19.0 revoceries (stays in Onn fastboot even after successful fastboot boot) I also tried the earliest 18.1 recovery.
Tried:
lineage-19.0-20220228-recovery-dopinder
lineage-19.0-20220114-recovery-dopinder
lineage-18.1-20210804-recovery-dopinder
Releases ยท ods-releases/dopinder
Contribute to ods-releases/dopinder development by creating an account on GitHub.
github.com
Has anyone had success getting LineageOS 18.1 flashed on the Dopinger devices? If so, which recovery did you use? (maybe an earlier release works?) If so, where can I get it? (the above link only has the last 2 releases)
Right now I am very suspicious that the recoveries are not working properly for this device.
Here's the extra instructions after you adb reboot into the bootloader using the guide:
1) fastboot flash recovery <recovery file name >
2) fastboot boot <recovery filename> **to get into lineageos recovery mode
At this point the recovery is unresponsive to any inputs (i.e onn 4k button pushes or USB keyboards)
3) In lineageOS recovery mode you can use the basic adb command to reboot recovery into sideload mode
adb reboot sideload **Devs apparently specially enabled this as a workaround for the no input in the recovery
From here you can continue to use the official guide to sideload the lineageos. At this point I was basically dirty flashing, which worked. But I'm sure people can format and erase the stock OS via adb commands if they're motivated enough.
Two issues I noticed with Onn 4k is that plex was super stuttery for almost everything I played (never tested plex on stock OS).
I also performed a factory reset, and afterwards WiFi was unable to reconnect. So I gave up for now and went back to my mibox s until I have time to look further.
Thanks again for the information to help me get lineageos on this device!
htc_softbank said:
I was looking to install LineageOS 18.1 and was having a hell of a time.
I was following the instructions, and I can get as far as booting into the LineageOS recovery, but then I can't navigate to ADB using the front button on the box. I am also finding it difficult to find a working OTG cable that works and has the ability to provide power. (so I can remove the USB cable from my laptop and plug in a USB keyboard without powering off the android box)
Anyone have any tricks or suggestions on a OTG cable or USB switch they know works on this? Or better yet, how to get the front navigation button working on the Onn Box working ot how I can enter recovery mode if I try fastboot flash (Impossible to enter recovery instead of boot to OS) instead of fastboot boot?
Here are the instructions I was using. Great until you get to the fastboot flash, since once you reboot it goes straight into the OS and will over right the custom recovery. Then when I fastboot boot, it works, but then the navigation button doesn't work to get to the next step. lol.....
Install LineageOS on dopinder | Odd Solutions Wiki
wiki.oddsolutions.us
Click to expand...
Click to collapse
What I ended up doing was hardwiring an extra USB cable internal, wasn't too hard soldering isn't my strongest skill by any means, but it's held up. I don't know exactly what the connection beside the USB is, but if I'm remembering correctly that's where i ended up wiring to it. Actually just tried to stay as close to the other power input as possible Just because it seemed like it would be best practice.
Also in case anyone needs them. decent internal photos
Best of luck, I've been running it this way for almost 6 months now
Has this project died? I've noticed the oddsoulutions website no longer works, and I found one page that said that it was forcing updates now that would reset the device back to factory. Bummer, I bought one last year and have been moving and didn't have time to try it out. Now I have times and all the links have gone dry.
iamnotsunshine said:
Has this project died? I've noticed the oddsoulutions website no longer works, and I found one page that said that it was forcing updates now that would reset the device back to factory. Bummer, I bought one last year and have been moving and didn't have time to try it out. Now I have times and all the links have gone dry.
Click to expand...
Click to collapse
[OFFICIAL/UNOFFICIAL] LineageOS 19.1 for Amlogic G12*/SM1 Family Devices
Amlogic G12*/SM1 Family Devices - Your warranty is now void. - You have been warned. - Use at your own risk. Introduction: This is the Official Lineage OS 19.1 thread for the Amlogic G12*/SM1 SoC family of devices. Downloads: Please follow...
forum.xda-developers.com
iamnotsunshine said:
Has this project died? I've noticed the oddsoulutions website no longer works, and I found one page that said that it was forcing updates now that would reset the device back to factory. Bummer, I bought one last year and have been moving and didn't have time to try it out. Now I have times and all the links have gone dry.
Click to expand...
Click to collapse
note that on dopinder, unofficial LOS19.1 installs & works, but L1 still not working (as of today ... hopefully npjohnson & others can fix it) in the lineage19.1 version linked by BTK19 in previous post. so, if you are set on DRM content, might want to wait. I bought a Dynalink/wade while I wait, and Lineage19.1 unofficial works well on that. just costs 2X $ !