Database Develop

Whatever I flash I end up in a bootloop with Chinese Teclast Logo

I have already tried almost all BIOS versions even with Flash programmer attached to the tablet, but I end up in a bootloop every time. When accessing the BIOS Setup it seems to be right, but I can't save any configuration, nor do I see the attached flashdrive.
Originally it used to be an Android only Air iii without 3g (C5Jx), after installing Mireks Rom it was running ok first, then I started tinkering around with Dual Boot a couple of weeks ago.
What am I doing wrong? I can't even get back to the ANDROID only state, since it won't boot. If I install with Mireks Installer, it ends up the same.

You should flash the original BIOS first, it will show that the tablet working fine yet or not.

The only dual BIOS I can flash (with or without EEPROM Flasher) is version 1.00
As soon as I try another higher version it either stays in a bootloop or seems to be hardbricked without any functionality.
Is it a common issue with M5C5 (32GB)?

[SOLVED]Mi5 completely dead

Hello everyone,
I have-or had- MI5 with latest cm14.1 on it, today I downloaded the latest rom from xiaomi.eu -Nougat-. I rebooted into recovery, wiped partitions, flashed the new rom, flashed successfully, and then flashed a font zip, the installer hanged at unmounting system for a long time, I forced rebooting it through holding power button the phone turned off and then never worked. nothing happens, no led when connecting to charger, pc does not recognize the phone at all, no sounds when connecting it. recovery and bootloader does not open. it is completely DEAD. Any help?

same h ere except i didn't get any errors while flashing except the normal command[log] error for all nougat roms. phone is just dead with no signs of life.

iXanza said:
same h ere except i didn't get any errors while flashing except the normal command[log] error for all nougat roms. phone is just dead with no signs of life.
Click to expand...
Click to collapse
I got this error as well,
After some search it seems using a deep flash cable could, I cannot make one currently so maybe you could take a look and try it
http://forum.xda-developers.com/showpost.php?p=69727277&postcount=2
I just checked the second post in the xiaomi eu thread
"- NEVER wipe /system partition manually in your life!"
hmm, I have always done this
Edit:
Many people reporting the same issue their.

There's another way to go to EDL mode which is this
https://www.youtube.com/watch?v=ED96PJ-qYMM
I haven't tried it yet as I don't have copper tweezers.

iXanza said:
There's another way to go to EDL mode which is this
https://www.youtube.com/watch?v=ED96PJ-qYMM
I haven't tried it yet as I don't have copper tweezers.
Click to expand...
Click to collapse
People reported it worked in xiaomi eu thread, gonna try once I have the tools, I wonder why the * dev didn't write "- NEVER wipe /system partition manually in your life!" before the download links

IMTLD said:
People reported it worked in xiaomi eu thread, gonna try once I have the tools, I wonder why the * dev didn't write "- NEVER wipe /system partition manually in your life!" before the download links
Click to expand...
Click to collapse
No clue. I'm taking it to the shop for them to do it for me tomorrow.

https://www.youtube.com/watch?v=ED96PJ-qYMM
Do follow the videos, i was hard brick 2 times but now it's working

The issue is, you flashed the CM14.1 on low battery, this then messed up the battery reading, while your device showed somewhere like 50% infact it was around 10%, what need to be done is, do a hard reset with power button a few times while connected to a charger, use a new charger/cable and let it charge for a long time, itll then switch on and charge, leave it to charge till 100% then do a full wipe including internal storage and install a new OS

Shaky156 said:
The issue is, you flashed the CM14.1 on low battery, this then messed up the battery reading, while your device showed somewhere like 50% infact it was around 10%, what need to be done is, do a hard reset with power button a few times while connected to a charger, use a new charger/cable and let it charge for a long time, itll then switch on and charge, leave it to charge till 100% then do a full wipe including internal storage and install a new OS
Click to expand...
Click to collapse
I don't really think that this is the problem because the "rom" flash completely successfully. I don't think that the font flash would cause all this mess. Anyway, I left it charging overnight and I keep pressing power button with vol +/- but nothing happens. Thanks anyway. it seems I have to either use test points or deep flash cable.

Hard bricked the phone with the same ROM here, tried to solve it with the video's testpoints (making contact between the two dots and plugging the USB).
Fortunately, MiFlash with adb and qualcomm drivers recognized the device. So I flashed many fastboot ROMs (miui 7/8 dev&stable) via MiFlash, but none of them made the device wake up. The only signal of life is the led blinking red when connected to a usb.
Still trying...
EDIT: ok, got it booting now. The red blinking led is actually a good sign, it means low battery. I just let it charge for about 20 min and the led changed to yellow, and then I could boot it up.
It seems like in all that time the phone was plugged into my PC usb port for flashing, it didn't charge the battery. So I think we should take into account what Shaky156 said, just in case.

jiaming2009 said:
Hard bricked the phone with the same ROM here, tried to solve it with the video's testpoints (making contact between the two dots and plugging the USB).
Fortunately, MiFlash with adb and qualcomm drivers recognized the device. So I flashed many fastboot ROMs (miui 7/8 dev&stable) via MiFlash, but none of them made the device wake up. The only signal of life is the led blinking red when connected to a usb.
Still trying...
Click to expand...
Click to collapse
I just revived my mi5 using the test point method, it is rather simple actually.
Make sure you are using miflashtool beta,
I downloaded this rom china developer
I noticed that even though I chose save user data, I still lost my data.

IMTLD said:
I just revived my mi5 using the test point method, it is rather simple actually.
Make sure you are using miflashtool beta,
I downloaded this rom china developer
I noticed that even though I chose save user data, I still lost my data.
Click to expand...
Click to collapse
Good to know it also worked for you, I just didn't believe that my battery was depleted from 70% just by hardbriking it...

After installing TWRP it asks to decrypt data even though I did not encrypt, hmmm what now
Edit:
I just did factory reset in TWRP and now I can see sdcard.

IMTLD said:
Hello everyone,
I have-or had- MI5 with latest cm14.1 on it, today I downloaded the latest rom from xiaomi.eu -Nougat-. I rebooted into recovery, wiped partitions, flashed the new rom, flashed successfully, and then flashed a font zip, the installer hanged at unmounting system for a long time, I forced rebooting it through holding power button the phone turned off and then never worked. nothing happens, no led when connecting to charger, pc does not recognize the phone at all, no sounds when connecting it. recovery and bootloader does not open. it is completely DEAD. Any help?
Click to expand...
Click to collapse
I also had my Mi5 die earlier today. Here's what I did to get it back:
1. Popped-open the back cover, removed the screws from the top panel
2. Disconnected battery (left side)
3. Connected battery back
4. Shorted the two contacts at the right side of the board
5. Plugged original USB in
Note that using a deep flash cable is a less intrusive way of doing steps 1-5, but that's what worked for me.
At this point, the PC detected the phone in EDL mode. I then attempted to flash the fastboot ROM for Mi 5, however, I kept getting errors about Missed Hello / Issue with COM port.
6. Downloaded an up-to-date version of Mi Flash (beta didn't work for me), disable Signature Enforcement (Windows 10) and install Qualcomm drivers
7. Downloaded a MIUI 7.5 fastboot rom
8. Flashed, got an error, about storage being not enough... But the screen turned on with the Mi logo. I was finally able to get the phone into Fastboot.
9. Successfully flashed MIUI 7.5 ROM using Mi Flash.
If you are still getting the COM port issue or Hello, try disconnecting the battery again and repeating steps 3-5.
Good luck.

idmissile said:
I also had my Mi5 die earlier today. Here's what I did to get it back:
1. Popped-open the back cover, removed the screws from the top panel
2. Disconnected battery (left side)
3. Connected battery back
4. Shorted the two contacts at the right side of the board
5. Plugged original USB in
Note that using a deep flash cable is a less intrusive way of doing steps 1-5, but that's what worked for me.
At this point, the PC detected the phone in EDL mode. I then attempted to flash the fastboot ROM for Mi 5, however, I kept getting errors about Missed Hello / Issue with COM port.
6. Downloaded an up-to-date version of Mi Flash (beta didn't work for me), disable Signature Enforcement (Windows 10) and install Qualcomm drivers
7. Downloaded a MIUI 7.5 fastboot rom
8. Flashed, got an error, about storage being not enough... But the screen turned on with the Mi logo. I was finally able to get the phone into Fastboot.
9. Successfully flashed MIUI 7.5 ROM using Mi Flash.
If you are still getting the COM port issue or Hello, try disconnecting the battery again and repeating steps 3-5.
Good luck.
Click to expand...
Click to collapse
Thanks for the reply, but I already fixed it this way. I used miflashtool beta since the final release did not work.
The problem is did you lose your data after the flash? because I lost mine even though I checked save data in miflashtool

IMTLD said:
Thanks for the reply, but I already fixed it this way. I used miflashtool beta since the final release did not work.
The problem is did you lose your data after the flash? because I lost mine even though I checked save data in miflashtool
Click to expand...
Click to collapse
At that point, I didn't really care if I lost data since I didn't have much on it anyway. Nice to hear that you got yours back. Those were dark hours, yes?

Thanks for giving a hope (checking way to recover from video). I'll get proper screwdrivers soon and try do the same.

I have narrowed down the issue, its the nougat firmware thats caused these recent issues. Xiaomi has distributed an unstable bootloader. I highly recommend reverting back to marshmallow firmware and OS

Shaky156 said:
I have narrowed down the issue, its the nougat firmware thats caused these recent issues. Xiaomi has distributed an unstable bootloader. I highly recommend reverting back to marshmallow firmware and OS
Click to expand...
Click to collapse
but how my mi5 now hardbricked no fastboot no recovery no edl

IMTLD said:
People reported it worked in xiaomi eu thread, gonna try once I have the tools, I wonder why the * dev didn't write "- NEVER wipe /system partition manually in your life!" before the download links
Click to expand...
Click to collapse
I can confirm that this 100% works for me. You need to be a bit patient with the tweezers and getting the contact points right. It didn't immediately work for me, and I think I had to try a dozen times at least. But eventually it did recognize it. Once MiFlash can see it, you need to use the latest China stable rom. I tried the latest china dev, but it kept on giving errors of missing hello packets.

Need advice on HD+

I rooted my HD+ over a year ago, but stopped using it due to its sluggish performance. Yesterday, I decided to install a new ROM to see if things would work better. I did back up the old ROM using CWM before I started plus I had two other backups including a backup of the native NOOK ROM (so I have three sets of backup files: Original NOOK system, and two different versions of CM (probably both 10, but I'm not sure). Anyway, I was unable to get GApps to install yesterday so I decided to just recovery a previously working ROM.
So I went into recovery and recovered back to the second of my three recoveries and got the Nook to reboot, and it was working. However, I had intended to go back to the native NOOK ROM, so I reran recovery to my original back up, and it failed to work. The Nook kept cycling back to recovery mode reboot option. So I ran recovery a third time, and tried to go back to the second of my three recoveries which worked a just a few hours before. I started the recovery last night and went to bed.
When I woke up this morning my Nook screen showed a fully charged battery logo. I unplugged the Nook from the power and it failed to boot. I tried holding down the power button to reset, holding the power and "N" button to reset, took out the SD card and tried both. Tried both with SD card in and out and Nook plugged into a Windows PC via USB. The screen remains black no matter what. The only response I get is that when I hit the power or "N" button when hooked up to a PC via USB, I get a message on my PC screen that says "USB device not recognized".
Any suggestions?

New development. I unplugged the Nook and tried once more to restart by briefly pressing the power button. A logo flashed on the screen showing an uncharged battery and a plug, which I assume is telling me I need to charge the Nook. However, it showed the battery as fully charged when I unplugged it this morning. Anyway, I plugged it back into my power cord and will see what happens. I'm really not too concerned, as this device, other than as a book reader, has never performed very well for me at all. Surfing the web was always very frustrating due to slow performance, stalling, etc. I'm just hoping to make it usable so I can give it away.

Update 2
Nook has been on charger 2.5 hours screen still stays black after pressing power button. Light is orange. is it possible the battery is bad after such a long time (about 2 years) on non-use?

Update 3 - and I would still like some advice. Please.
My Nook finally booted into recovery. It behaved as if the battery was not charged, and I'm not sure why as it was plugged in overnight.
I did a wipe & factory reset then reinstalled the last working ROM I have Files were installed in this order:
1. NookHDplus-CWM-6046-for-internal-memory-rev0-(07-13-14).zip
2. cm-11-20150209-NIGHTLY-ovation.zip
3. pa_gapps-modular-micro-4.4.2-20140426a-signed.zip
I then rebooted and CM11 is installed and working again. Thank you leapinair and others.
When I used this version of CM11 before (back in 2015) it eventually became sluggish and stalled at lot. It was very frustrating to use.
Can someone direct me to a source of a better ROM and Gapps? I tried installing twrp and these files:
1. cm_ovation-ota-NMF26Q.161222.zip
2. open_gapps-arm-7.1-stock-20170212.zip
but it didn't work for me. I'm assuming I have the wrong files or combo of files.
I would really appreciate some advice and download links to better ROMs and Gapps. Thanks in advance for any useful advice.

Typical response for this forum

woneil said:
...
When I used this version of CM11 before (back in 2015) it eventually became sluggish and stalled at lot. It was very frustrating to use.
Can someone direct me to a source of a better ROM and Gapps? I tried installing twrp and these files:
1. cm_ovation-ota-NMF26Q.161222.zip
2. open_gapps-arm-7.1-stock-20170212.zip
but it didn't work for me. I'm assuming I have the wrong files or combo of files.
I would really appreciate some advice and download links to better ROMs and Gapps. Thanks in advance for any useful advice.
Click to expand...
Click to collapse
I'd suggest you try the LN14.1 build lnos_ovation-ota-NMF26Q.170104 ) available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3480156918) and open_gapps-arm-7.1-pico-2017[mmdd] (available at http://opengapps.org/).
You should be able to use your current CWM recovery to flash twrp-3.0.1-0-ovation.zip (available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778), then reboot into the newly flashed TWRP to perform "wipe /data & factory reset", and then flash the LM and GApps zip files.

digixmax said:
I'd suggest you try the LN14.1 build lnos_ovation-ota-NMF26Q.170104 ) available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3480156918) and open_gapps-arm-7.1-pico-2017[mmdd] (available at http://opengapps.org/).
You should be able to use your current CWM recovery to flash twrp-3.0.1-0-ovation.zip (available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778), then reboot into the newly flashed TWRP to perform "wipe /data & factory reset", and then flash the LM and GApps zip files.
Click to expand...
Click to collapse
Thanks very much for this advice. I will give it a try.

woneil said:
Thanks very much for this advice. I will give it a try.
Click to expand...
Click to collapse
See https://forum.xda-developers.com/nook-hd/general/how-to-updating-nook-hd-internal-emmc-t3562818 for more info/pointers.

Does anyone have a link to the image, I click on ROM link and it's starting that the link is removed.
I have CM13 installed it runs very slow sometimes unresponsive, how does LN14.1 run incomparison

DeDonKJC said:
I have CM13 installed it runs very slow sometimes unresponsive, how does LN14.1 run in comparison
Click to expand...
Click to collapse
FWIW, I've been running LN14.1 builds for the last couple months and am fairly happy with it. See this thread for issues/quirks that have been reported.

Mi 5 Black Screen with Fastboot MODE active and TWRP on.

Hi everyone. I've searched on the web for this issue two days, including this forum and this section. I've tried several solutions altough none has worked. My last hope is your help.
As many of you would know, this phone "suffer" about the black screen issue. Two weeks ago I've upgraded my xiaomi.eu rom as usual (altough from Nougat to Oreo Beta) and after the battery drain was higher than usual, I've found the phone switched off and unable to revive. I then, started looking for the issue and its relative solution, so I opened the phone, unplugged the battery cable, replugged and the phone started as if nothing has ever happened. This week I then update the last rom 8.3.29 (hoping in less drain battery) and the phone did the same. Only problem is that now the cable trick doesn't work anymore.
I've tried to flash many different roms from MiFlash Tools:
- MiFlash_xiaomi.eu_gemini_6.4.21_6.0
- gemini_global_images_8.3.29_20180329.0000.00_7.0_global
- gemini_global_images_V7.5.1.0.MAAMIDE_20160523.0000.23_6.0_global_85fffc8e2d (the one suggested in the "famous" unbricking video on youtube)
I've also run some commands and booted the phone in fastboot, pushed and flashed the twrp (last version) so the pc even show me the phone as sdcard, altough I wasn't able to flash the rom from command line in TWRP (see screenshot).
Anyone has any idea?
Thanks to every soul that could help me through this.
Screenshot 1: https://imgur.com/Nnld61K
Screenshot 2: https://imgur.com/qHqojwQ
EDIT1: After writing this post, the phone decided to boot (led indicating the level of charge and hardware keys lighting up, phone making sounds...altough the screen remains black. Could then be the cable?

use miflsher and flash official 9.2 firmware

[HELP] Redmi 4x won't boot.

Hello,
my Redmi 4x won't boot. I tried to find some solution for this issue, but I can't find it anywhere, so I created this new thread to ask you for your help.
Last night I was out in the city and my phone died because of low battery, so after I came home I just wanted to charge it as usual. Battery logo showed up and it was behaving as always, but when I tried to turn it on it couldn't boot again.
After pressing the power button the splash screen flashes for a brief moment and then it just turn off again. This happens all the time from the moment my phone died. I'm not sure what went wrong here. I can't get it to recovery mode either. So I wanted to do a fresh start and flash it again with new ROM here (Ressurection Remix 6 is what I have now)
I'm able to get it on fastboot mode, but once I try to flash it with MiFlash I get error message like "error:FAILED (remote: Critical partition flashing is not allowed)"
So I looked up for a solution and I found that I need to get it in EDL mode with adb.exe
I tried this solution but with no luck. Phone is restarting but it won't turn on again and the fastboot mode is lost.
I'm not really sure if I have right drivers for it. Qualcomm HS-USB Diagnostics 900E is what I have now. I can't also change the usb debugging mode obviously, so I'm also trying to find some solution for this issue either (is there any chance how to turn it on with adb.exe?)
I think it's softbricked but i'm not really sure.
Thank you for your help

p3wp3w said:
Hello,
my Redmi 4x won't boot. I tried to find some solution for this issue, but I can't find it anywhere, so I created this new thread to ask you for your help.
Last night I was out in the city and my phone died because of low battery, so after I came home I just wanted to charge it as usual. Battery logo showed up and it was behaving as always, but when I tried to turn it on it couldn't boot again.
After pressing the power button the splash screen flashes for a brief moment and then it just turn off again. This happens all the time from the moment my phone died. I'm not sure what went wrong here. I can't get it to recovery mode either. So I wanted to do a fresh start and flash it again with new ROM here (Ressurection Remix 6 is what I have now)
I'm able to get it on fastboot mode, but once I try to flash it with MiFlash I get error message like "error:FAILED (remote: Critical partition flashing is not allowed)"
So I looked up for a solution and I found that I need to get it in EDL mode with adb.exe
I tried this solution but with no luck. Phone is restarting but it won't turn on again and the fastboot mode is lost.
I'm not really sure if I have right drivers for it. Qualcomm HS-USB Diagnostics 900E is what I have now. I can't also change the usb debugging mode obviously, so I'm also trying to find some solution for this issue either (is there any chance how to turn it on with adb.exe?)
I think it's softbricked but i'm not really sure.
Thank you for your help
Click to expand...
Click to collapse
Hi, most likely your battery is faulty. Current draw during Android kernel boot up phase is above 1A whereas only around 0.2A for a working OS, that's why neither OS nor recovery can start when the battery develops high ESR (internal resistance). Do the following test:
fully recharge the battery
do not disconnect the charger
turn it on
Your Android may now actually work again but you must use a short quality cable connected to a 2A+ charger, which will support the battery at boot time - and you can disconnect it later.

k23m said:
Hi, most likely your battery is faulty. Current draw during Android kernel boot up phase is above 1A whereas only around 0.2A for a working OS, that's why neither OS nor recovery can start when the battery develops high ESR (internal resistance). Do the following test:
fully recharge the battery
do not disconnect the charger
turn it on
Your Android may now actually work again but you must use a short quality cable connected to a 2A+ charger, which will support the battery at boot time - and you can disconnect it later.
Click to expand...
Click to collapse
Thank you, but the battery wasn't the main issue, because once I was able to flash it through EDL mode to the latest stable official ROM, the battery was on 93% already.
Now I'm stuck with MI logo and powered by android with 3 blinking dots above. I watched somewhere, that it could last for 7 minutes, but for me even the 15 minutes is not enough, so I guess i'm in bootloop.
For some reason my bootloader is locked again, even though I already made the unlocking process earlier before I flashed to Resurection remix 6. My phone doesn't even appear in device manager. I can't even use it as a storage, so I could try to flash it to custom ROM.
I'm not really sure wat happened and how is it possible to brick your phone by just draining your battery to 0%

Ok, phone is alive again. It booted up right after I inersted microSD card in slot. I didn't know this was necessary...