Related
Q&A for [RECOVERY] TWP 2.7.1.0 for One Mini 2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] TWP 2.7.1.0 for One Mini 2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
new twrp's won't work
Hi there,
I just tried to root my htc mini 2 with and it says that it is tampered now and I can't reboot my recovery. So I tried the newest twrp and some in between because I've read in this forum that somebody had the same problem and he just got the newest twrp but that didn't work for me at all.
Is there any way to undo the whole thing by replacing the twrp with the original one or do I have to wait till there is gonna be a root for the htc mini 2?
When I try to recover everything it says that this build is for development purpose only...
Does somebody have an idea?
I would appreciate it a lot if somebody has an idea.
Hornochse7958 said:
Hi there,
I just tried to root my htc mini 2 with and it says that it is tampered now and I can't reboot my recovery. So I tried the newest twrp and some in between because I've read in this forum that somebody had the same problem and he just got the newest twrp but that didn't work for me at all.
Is there any way to undo the whole thing by replacing the twrp with the original one or do I have to wait till there is gonna be a root for the htc mini 2?
When I try to recover everything it says that this build is for development purpose only...
Does somebody have an idea?
I would appreciate it a lot if somebody has an idea.
Click to expand...
Click to collapse
When the bootloader says "tempered" means that it was unlocked. when you see " this build is for development purpose only" its referring to TWRP because you now using a custom recovery. Not sure the nature of your problem but to undo, simply boot into boot loader and flash original recovery.img you can find in the forum.
I can't you open TWRP?
kativiti said:
When the bootloader says "tempered" means that it was unlocked. when you see " this build is for development purpose only" its referring to TWRP because you now using a custom recovery. Not sure the nature of your problem but to undo, simply boot into boot loader and flash original recovery.img you can find in the forum.
I can't you open TWRP?
Click to expand...
Click to collapse
Thank you for the quick respond and I wanted to try and undo everything but no my problem is that my phone completely froze in the twrp screen. I can't do anything, I can't unlock it nor shut down my phone or start the bootloader... that kind of sucks. Any suggestions now? Is it possible to open the htc one mini 2 and take out the battery? or do I have to wait till it runs out by it self and than start it again?
Hornochse7958 said:
Thank you for the quick respond and I wanted to try and undo everything but no my problem is that my phone completely froze in the twrp screen. I can't do anything, I can't unlock it nor shut down my phone or start the bootloader... that kind of sucks. Any suggestions now? Is it possible to open the htc one mini 2 and take out the battery? or do I have to wait till it runs out by it self and than start it again?
Click to expand...
Click to collapse
Read this tread. Someone had the same problem
http://forum.xda-developers.com/one-mini-2/help/rooting-htc-one-mini-2-t2880936
Unresponsive after boot up from dead battery
THanks to U-ra I get the enjoy my fav DSP Viper!!!
Cheers Man,
I have a small niggling problem that I can't work out, My battery tends to die alot, once I place the phone on charge after a flat battery, the phone auto boots to Twp, I am really cool with that but the annoying thing is buttons and screen are unresponsive? I can't do a thing, just have the Twp menu. The power of button does turn the screen off/on but thats its. Tried doing factory resets, reboots holding down power, vol buttons. Just nothing.
only way around it is to use adb and reboot command.
Is anyone else experiencing this problem.
http://forum.xda-developers.com/one...recovery-twp-2-7-1-0-one-mini-2-t2801370/page 4 here's the answer, so far
@u-ra is there any clue about getting official twrp support? (I was thinking about that problem of the self-booting recovery when phone is off and plugged in)
gibihr said:
@u-ra is there any clue about getting official twrp support? (I was thinking about that problem of the self-booting recovery when phone is off and plugged in)
Click to expand...
Click to collapse
I'll try to get to it this weekend.
HELP TWRP stuck at swipe to unlock
Hello all,
for unknown reason the phone restarded and now is stuck at swipe to unlock but it is not working. I try to hold power+volume down, but no way to turn it off. What can I do?
Thanks in advance
PS: well, it restarted... I don't know what happend but now it's ok
sorry for sounding like a newb
i have the verizon htc one remix, which i believe is the same as the one mini 2 . will this work on it?
akubenz said:
i have the verizon htc one remix, which i believe is the same as the one mini 2 . will this work on it?
Click to expand...
Click to collapse
you can try but i think someone here couldn't unlock bootloader trough HTC Dev.
Help: Stock rom updated between boots, TWRP non responsive, fastboot doesnt recognise
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
snorglamp said:
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
Click to expand...
Click to collapse
A kind member replied to me in another post indicating that fastboot commands only work in the bootloader, and that adb commands only work in TWRP which is why I am having problems re-flashing TWRP (requiring the "fastboot flash recovery TWRP.img" command). However I thought TWRP replaced the bootloader, so I seem to be locked out of re-flashing TWRP because i have TWRP. This seems not to make a lot of sense, can anyone else confirm or otherwise explain what I have misunderstood about that? As stated neither adb nor fastboot recognises the device is attached to the computer any more, so commands are not executing...
snorglamp said:
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
Click to expand...
Click to collapse
I think I have found the solution for myself: I went back into the stock rom and did a factory reset (from within android booted up as normal), which after completion rebooted me into TWRP which now works fine (is responding to touch again, and i can flash the Cyanogen image now). Hopefully this helps someone else in this situation one day, or maybe I am the only idiot that needed to ask hehe. I should clarify that after flashing TWRP I lost access to the fastboot screen and could not push anything over ADB or fastboot commands from windows (plugged in via USB). Holding down volume down and power booted directly into TWRP, and i had no way to get to fastboot screen. After doing factory resent from within the Android OS, holding volume down and power booted me to the fastboot screen, and only when I selected "Recovery" did it take me to TWRP, and I was again able to run fastboot and ADB commands from PC. Weird (or maybe not if you know more than me), but there it is...
snorglamp said:
A kind member replied to me in another post indicating that fastboot commands only work in the bootloader, and that adb commands only work in TWRP which is why I am having problems re-flashing TWRP (requiring the "fastboot flash recovery TWRP.img" command). However I thought TWRP replaced the bootloader, so I seem to be locked out of re-flashing TWRP because i have TWRP. This seems not to make a lot of sense, can anyone else confirm or otherwise explain what I have misunderstood about that? As stated neither adb nor fastboot recognises the device is attached to the computer any more, so commands are not executing...
Click to expand...
Click to collapse
Sorry, but it seems to me that you don't know the difference between bootloader and recovery. I apologize if you do. If not, search in CM wikis or ask here for explanations.
corbeau56 said:
Sorry, but it seems to me that you don't know the difference between bootloader and recovery. I apologize if you do. If not, search in CM wikis or ask here for explanations.
Click to expand...
Click to collapse
I do indeed know the difference between the bootloader and recovery, its just that the bootloader (Hboot) was not longer accessible in my situation and TWRP (the recovery) was imposing itself when you would normally expect to find the bootloader (i.e. my bootloader was for all intents and purposes replaced by my recovery, while I am sure this is not true in fact, it was in effect). As I say, doing a factory reset from within the OS restored the bootloader (HBoot) and I was able to continue modding. I am today extremely happy with my fully secured cyanogenmodded HTC One Mini 2 via TWRP recovery method. I hope that is somewhat clearer.
Can you enter bootliader now? I got stuck in a bootloop once and couldn't enter bootloader because I continued pressing power and Volume down like I did on my One S. For Mini 2, we have to hold the Volume UP and Power buttons until HBOOT appears, then release the buttons.
corbeau56 said:
Can you enter bootliader now? I got stuck in a bootloop once and couldn't enter bootloader because I continued pressing power and Volume down like I did on my One S. For Mini 2, we have to hold the Volume UP and Power buttons until HBOOT appears, then release the buttons.
Click to expand...
Click to collapse
That may well have been an alternative solution to my problem, however it was fixed by the factory reset and volume down and power then took me to HBoot (this would appear to contradict what you have said above, but maybe volume down and power does different things depending on how what you have done to the phone, not sure), so I cannot confirm whether or not that also would have worked for me. Good suggestion though, especially if you are not in a position to do a factory reset. and it would certainly be easier if it worked...I am convinced my problem was the result of a conflict between the TWRP version i installed (downloaded from here) and the android update that occurred between boots.
I am indeed able to get into bootloader/hboot and successfully flashed cyanogenmod from TWRP. I can confirm post flashing TWRP and Cyanogenmod, holding volume down and power takes me to HBoot (and then the option to go to fastboot or recovery).
Holding power up and power just loads cyanogenmod for me now as if I had just pressed power.
I thought I should confirm whether or not holding volume up vs volume down with power results in bootloader vs recovery loading. For me, they both took me to TWRP.
Also, TWRP doesnt seem to work on HTC One Mini 2 after you do anything to set up your phone. It just doesnt recognise touch input any more so you cant do anything with it. However the fix i noted earlier (factory reset) even works with other roms installed, confirmed for cyanogenmod 11 and 12 nightlies as at the date of this post. After factory reset TWRP works again, but if you go through the setup steps and start installing apps, TWRP goes unresponsive again. I hope we might get an official TWRP update soon!
Hi all! I was playing with my L90 D415 (as usual), and I wanted to try stock & debloated Lollipop. I found a zip, flashed it, and TWRP said "/system failed to mount", or something along those lines. I then thought "No biggie, I'll just go to fastboot, reflash download mode, then flash my problems away"
...except I can't get to fastboot.
...nor can I get to the LG splash.
I now have a very shiny paperweight, that can do literally nothing but tell me when there is no battery found. I cannot go into recovery, nor can I get to fastboot. No prompts, no booting whatsoever.
Specific info:
Running a modded D415 Lollipop (found here)
Disabled download mode, for fastboot access
Using shoxxy's TWRP build
By the way, I cannot get any logcats or anything. The darn thing is literally a shiny glass & plastic brick.
Same happened to me.
After it charged to 100%, it started bootlooping showing me 0% battery and that was it. Basically the same as the no battery message when the battery was pulled.
I've tried everything I've read. I wonder if I have to let the battery completely discharge.
Best of luck, update me if you get anywhere.
toddphilip said:
Same happened to me.
After it charged to 100%, it started bootlooping showing me 0% battery and that was it. Basically the same as the no battery message when the battery was pulled.
I've tried everything I've read. I wonder if I have to let the battery completely discharge.
Best of luck, update me if you get anywhere.
Click to expand...
Click to collapse
Absolutely no luck, unfortunately. I have tried virtually everything; the only thing I can imagine is that the actual bootloader (LG logo) was wiped off, which is scary as I cannot see any way to fix this, other than with some sort of hardware disassembly and flashing the actual boot ROM, which is too much work...
I think this is officially a dead phone!
I have ran into this issue before and managed to recover. Once I get my current issue squared away I'll help you out. /system mount:error actually isn't fatal, I would have recommended rebooting your recovery, wiping your partitions, and installing or recovering from a backup.
I hate asking the obvious, but do any devices relevant show-up under device manager? You also can not enter TWRP because the initial Boot does not show either, correct?
FiniteDGk said:
I have ran into this issue before and managed to recover. Once I get my current issue squared away I'll help you out. /system mount:error actually isn't fatal, I would have recommended rebooting your recovery, wiping your partitions, and installing or recovering from a backup.
I hate asking the obvious, but do any devices relevant show-up under device manager? You also can not enter TWRP because the initial Boot does not show either, correct?
Click to expand...
Click to collapse
It does not show up under device manager, but my Linux system picks it up as
Code:
Bus 003 Device 004: ID 05c6:f006 Qualcomm, Inc.
under lsusb. This seems to also affect some HTC devices, and a fix has been found for them, so possibly a similar fix could be applied here?
Potentially useful links I've found:
LG G2 is UNBRICKABLE NOW! [FIX REAL HARD BRICK]
[UNBRICK] HTC Unbricking Project
You may want to check these threads:
http://forum.xda-developers.com/showpost.php?p=60010801&postcount=230
http://forum.xda-developers.com/showpost.php?p=60072439&postcount=4 (not sure if it's a D415 tho)
lfom said:
You may want to check these threads:
http://forum.xda-developers.com/showpost.php?p=60010801&postcount=230
http://forum.xda-developers.com/showpost.php?p=60072439&postcount=4 (not sure if it's a D415 tho)
Click to expand...
Click to collapse
I can't let it drain, and I think my LAF partition is trashed somehow, preventing it from booting. It can only display a 0% battery and Battery Not Found screen, nothing else.
In the first post I've linked, the guy said that he had laf.img in the adb folder, and he was able to boot using fastboot in download mode. Tried that too?
Related info:
http://forum.xda-developers.com/showpost.php?p=60044367&postcount=10
These guides may help as well:
http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
http://forum.xda-developers.com/lg-l90/development/hack-reocvery-fastboot-t3059684
lfom said:
In the first post I've linked, the guy said that he had laf.img in the adb folder, and he was able to boot using fastboot in download mode. Tried that too?
Click to expand...
Click to collapse
I can't get to fastboot, any attempt to boot it results in a 0% battery warning, even though it is charged.
Also (recover lost laf.img in TWRP):
http://forum.xda-developers.com/showpost.php?p=60051741&postcount=122
got the same problem, almost 7 month with a brick by phone and find nothing in the web
Hi.
I've been searching for a solution on how to fix my phone for already almost a year now. I didn't even do anything to it, no custom recoveries or OS (wanted to get CM, but at the time it wasn't available on it, not sure if now is).
The problem - the phone is stuck in a bootloop with an empty battery. The battery wasn't empty at the beginning, but it died in the process of trying to make it work, since the only thing I can boot is "fastboot&rescue" mode, in which the phone doesn't charge - how sweet. Now, I've read just about every thread here on how to flash custom (and original) recoveries, all the DLOAD folder versions and everything, and somewhere in between all that I found that it's impossible to flash anything if the battery is low (or totally empty).
The question - how do I charge the battery if it doesn't boot in anything other than fastboot, and when I plug it in the wall it just loops and loops and loops, and doesn't even charge? It's also impossible to turn it off while it's plugged in the charger. WTF, Huawei, really?
Any help appreciated. Cheers,
Can you Boot into recovery through pressing power + volume+?
You may have to remove the back of your phone and buy a new battery. The disassambling process is pretty simple, but of course you will loose any guarantee..
l3Nni said:
Can you Boot into recovery through pressing power + volume+?
You may have to remove the back of your phone and buy a new battery. The disassambling process is pretty simple, but of course you will loose any guarantee..
Click to expand...
Click to collapse
No, can't boot into recovery, only fastboot. If I could, I guess I would've already fixed it, heh.
I actually got it to charge, at least that's what I think. There was a *.bat script somewhere here that was repeatedly doing these two things:
1) fastboot getvar battery-voltage
2) fastboot reboot-bootloader
So, I ran that (while the phone was plugged in my computer and running fastboot mode), and it began looping and looping and looping. Left it like that for the night. Now, in the morning, when I unplugged it and tried to do someting, the red "battery low" LED wasn't glowing/blinking anymore! Since "fastboot getvar battery-voltage" returned an error all the time (remote: command not allowed), I don't exactly know how much power I have in it, but I'll just leave it like that for a day or two now, and then try some of the methods I've already tried before. Got any new ones I could try?
I already removed the back and removed the battery - wanted to see if I can charge it externally, but has a very small connector to connect it to the mother board, and I can't just put it in any external charger - I actually didn't find any external chargers that can charge the battery of this phone, really strange.
About the warranty - don't even care anymore. Somehow I managed to get a small crack on the glass on the back of the phone just a few days after getting it. Screen is not damaged, just the back cover. And, you don't know Latvia, but this is how it goes here. I took it to a repair shop - the one I needed to take my device for warranty repair. However, in Latvia that means it's just an another small repair shop, which just happens to have a contract with the company who sold me the phone (mobile phone operator). So, they take my phone, say they'll do a diagnostic and get back to me. Three weeks pass, and they call me telling that the only thing they can do is replace the motherboard, which is gonna cost me about 250 euros. That, or nothing. I don't agree. That means, if I don't agree to their suggested method of repairing, I have to pay for the diagnostic (about 20 euros).
Well, good idea, looks like you will get your phone running..
To unbrick your device you need to flash a recovery that matches with the firmware you had been on. So, if you had a B1xx Rom running try flashing TWRP 2.8.1.0 and MyRom 1.2. After that flash the stock emui 2.3 recovery and B133 through dload. If you were on a B6xx Ron flash TWRP 2.8.7.0 and MyRom 3.3, then emui 3.0 Recovery and B621.
When you didn't try this way until now, do it. It should work if the device isn't hardbricked.. I wish you the best.
l3Nni said:
Well, good idea, looks like you will get your phone running..
To unbrick your device you need to flash a recovery that matches with the firmware you had been on. So, if you had a B1xx Rom running try flashing TWRP 2.8.1.0 and MyRom 1.2. After that flash the stock emui 2.3 recovery and B133 through dload. If you were on a B6xx Ron flash TWRP 2.8.7.0 and MyRom 3.3, then emui 3.0 Recovery and B621.
When you didn't try this way until now, do it. It should work if the device isn't hardbricked.. I wish you the best.
Click to expand...
Click to collapse
Just flashed TWRP 2.8.1.0, it's already getting better. Now when I tried turning it on in recovery mode, it's not just simply bootlooping all the time, but is stuck on the Huawei logo. At least I hope that's better If I try to turn it on normally it just bootloops again. Omg omg omg.
l3Nni said:
Well, good idea, looks like you will get your phone running..
To unbrick your device you need to flash a recovery that matches with the firmware you had been on. So, if you had a B1xx Rom running try flashing TWRP 2.8.1.0 and MyRom 1.2. After that flash the stock emui 2.3 recovery and B133 through dload. If you were on a B6xx Ron flash TWRP 2.8.7.0 and MyRom 3.3, then emui 3.0 Recovery and B621.
When you didn't try this way until now, do it. It should work if the device isn't hardbricked.. I wish you the best.
Click to expand...
Click to collapse
Well, tried everything again. Flashing all those recoveries, nothing, can't get a recovery. Put a dload folder with update.app in it, magic 3 button combo just gives me some more of that good old bootloop. Extracted everything from the update.app, flashed recovery, system and boot with fastboot - all showed success. I got the most excited when it got to flashing system - it was quite big and took quite long, and returned success, so I really hoped that really did something - but no. Downloaded P7 kernel. Tried "fastboot flash:raw boot P7_kernel" ("P7_kernel" is the name of the file). It created a boot image (544985088 bytes), sending 'boot' returned "OKAY [20.622s]", then "writing boot" returned "FAILED (remote: flash write failure)". Is this the thing that's really broken? The boot flash partition? If so - what can I do, if anything?
God I hate this phone. The best is that I only used it for 3 months, and I still have to pay for it for more than a year. It's been in this condition for 7-8 months already. FML.
edzjins said:
Well, tried everything again. Flashing all those recoveries, nothing, can't get a recovery. Put a dload folder with update.app in it, magic 3 button combo just gives me some more of that good old bootloop. Extracted everything from the update.app, flashed recovery, system and boot with fastboot - all showed success. I got the most excited when it got to flashing system - it was quite big and took quite long, and returned success, so I really hoped that really did something - but no. Downloaded P7 kernel. Tried "fastboot flash:raw boot P7_kernel" ("P7_kernel" is the name of the file). It created a boot image (544985088 bytes), sending 'boot' returned "OKAY [20.622s]", then "writing boot" returned "FAILED (remote: flash write failure)". Is this the thing that's really broken? The boot flash partition? If so - what can I do, if anything?
God I hate this phone. The best is that I only used it for 3 months, and I still have to pay for it for more than a year. It's been in this condition for 7-8 months already. FML.
Click to expand...
Click to collapse
Hi, is your bootloader unlocked??? I think you cant write the boot partition if tour p7 is not unlocked, hace you tried flashing stock recovery? Try the b135
SiulGKT said:
Hi, is your bootloader unlocked??? I think you cant write the boot partition if tour p7 is not unlocked, hace you tried flashing stock recovery? Try the b135
Click to expand...
Click to collapse
Hi. Yes, bootloader unlocked, 100% sure. Have tried flashing the stock recovery, no changes. Tried to find the b135 now - I actually failed to find a real, valid download link! All I found were some russian ****up sites, which downloaded some russian ****ing malware! WTF? I'm about to give up on this phone. Just destroy it with all my hate for it. **** this ****ing piece of **** to hell. There is no hope, and **** my life. Whatever.
Be patient. I'll give you link soon but give me answers for this questions.
What was yours last valid ROM ?
Dude you can't flash any recovery you want.... It's not simply working between different ROMs.
Second question. Do you unplaged usb cable before flashing ROM by force update (3 buttons) ?
PS
I am not sure but battery isn't charging even fastboot mode or if totally device is off ?
Sent from my HUAWEI P7-L10 using Tapatalk
Ziolek67 said:
Be patient. I'll give you link soon but give me answers for this questions.
What was yours last valid ROM ?
Dude you can't flash any recovery you want.... It's not simply working between different ROMs.
Second question. Do you unplaged usb cable before flashing ROM by force update (3 buttons) ?
PS
I am not sure but battery isn't charging even fastboot mode or if totally device is off ?
Sent from my HUAWEI P7-L10 using Tapatalk
Click to expand...
Click to collapse
My last valid ROM is the only one I ever had - EMUI, whichever was the latest about a year ago.
After flashing recovery in fastboot mode, I unplugged the cable and pressed the power button and helt it until it turned off. Waited for a minute to see if it doesn't turn on, to make sure it's completely off - just what the instructions say. Then I tried the force update with 3 buttons, cable unplugged. With stock ROM it was still bootlooping, no changes at all, but with TWRP 2.8.1.0 it got stuck at Huawei logo - but no bootloop. Just Huawei logo, nothing else.
Battery is not charging in fastboot mode because that's how it is on all phones. But it's also not charging when it's totally off, because when I plug it in the charger, it automatically tries to turn on, and starts bootlooping. It's impossible to charge it then. However, with the .bat script I guess I have solved the charging problem - at least the red LED doesn't light/flash anymore.
Emui 3.0 beta release was at the end of 2014, official B609 in January 2015. It's important what rom you have been on. Trying different ones is just a waste of time..
You may try to extract and flash Bxxx part for part (depends on what rom you were) and then TWRP 2.8.1.0/2.8.7.0.I have no other idea, unfortunately.
It's a stupid question, but did you, when trying to boot into recovery, press volume+ for a longer time?
edzjins said:
My last valid ROM is the only one I ever had - EMUI, whichever was the latest about a year ago.
After flashing recovery in fastboot mode, I unplugged the cable and pressed the power button and helt it until it turned off. Waited for a minute to see if it doesn't turn on, to make sure it's completely off - just what the instructions say. Then I tried the force update with 3 buttons, cable unplugged. With stock ROM it was still bootlooping, no changes at all, but with TWRP 2.8.1.0 it got stuck at Huawei logo - but no bootloop. Just Huawei logo, nothing else.
Battery is not charging in fastboot mode because that's how it is on all phones. But it's also not charging when it's totally off, because when I plug it in the charger, it automatically tries to turn on, and starts bootlooping. It's impossible to charge it then. However, with the .bat script I guess I have solved the charging problem - at least the red LED doesn't light/flash anymore.
Click to expand...
Click to collapse
Than you probably have EMUI 2.3 ROM version.
Try flashing B135 recovery from here.
Next try to install B135 ROM from this link.
l3Nni said:
Emui 3.0 beta release was at the end of 2014, official B609 in January 2015. It's important what rom you have been on. Trying different ones is just a waste of time..
You may try to extract and flash Bxxx part for part (depends on what rom you were) and then TWRP 2.8.1.0/2.8.7.0.I have no other idea, unfortunately.
It's a stupid question, but did you, when trying to boot into recovery, press volume+ for a longer time?
Click to expand...
Click to collapse
No, it broke down before EMUI 3 came out, then. I guess I had the ROM which was just before EMUI 3.
Usually when trying to boot into recovery I press the volume+, hold it for about 10 seconds, and then press and hold the power button until it starts turning on. Then I hold both of them for some time, then release the power button but keep the volume button pressed. I've tried doing it differently - holding both buttons for longer time, releasing both as soon as it starts turning on, nothing I've tried works.
edzjins said:
No, it broke down before EMUI 3 came out, then. I guess I had the ROM which was just before EMUI 3.
Usually when trying to boot into recovery I press the volume+, hold it for about 10 seconds, and then press and hold the power button until it starts turning on. Then I hold both of them for some time, then release the power button but keep the volume button pressed. I've tried doing it differently - holding both buttons for longer time, releasing both as soon as it starts turning on, nothing I've tried works.
Click to expand...
Click to collapse
B135 recovery
http://forum.xda-developers.com/ascend-p7/general/trying-to-update-rom-1-2-t3222485
I uploaded it couple days ago...
OK, I left it "charging" for 2 days straight, hoping maybe battery was too low to flash partitions or whatever. Just wanted to make sure the battery is charged enough. I can't check the voltage or the percentage, because "fastboot getvar battery-voltage" always says that it's forbidden, no permissions, whatever.
So, I left it to charge for 2 days, and now I tested all the things you guys have posted here. Carefully, one by one. Every fastboot flash command returned success, but in the end nothing changed. Doesn't matter which recovery and/or boot I flash, it's just stupidly bootlooping all the time. Nada.
Finally, you can buy a defect P7 (with a broken screen or anything like this) for pretty low money on eBay and change the motherboard.
But I could also understand it well if you just throw it out of the window.. You had really bad luck.
Probably i have the same problem..... You solve yours problem with this ?
Nop, didn't solve the bootloop. I managed to get a donor phone for 55eur though, which had a bent body and wasn't functioning well because of that, and the screen was a bit cracked too. So I did a motherboard swap. Worked perfectly, but the battery connector protecting case screw doesn't hold in anymore, so sometimes it just turns off because it loses connection, or something. I tried to fasten it with some duct tape, hoped it'd help, and put a hard case on it - got better, but still fails sometimes.
I try give it back on warranty, i hope thei repair it.
I am in the EXACT same boat as edzjins. I have wasted 4 days of my precocious life trying to flash stuff on a phone with a completely dead battery.
I just doesn't work, period!
The only possible fix is to buy a new battery, replace the old one, and after the new battery is installed, have all of the flashing software ready to go and fired up before the new battery dies, too!
Its a time game.
Just like edzjins, there was a brief period of time when I thought I could stop the bootloop via TWRP recovery, but was unable to and the battery completely died.
Be wary of trying to flash "EdXposed" framework with TWRP. Instead, flash it only through Magisk.
I have learned the hard way : (
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.
Hey!
I was using my phone as normal, and installed an update for PixelPlusUI, it was working fine and all, until earlier today, i tried going into recovery to fix an app issue. After that, the phone just bootlooped. I figured that going into Fastboot would fix that, but the problem is, i can't reach any of those modes. It just goes to the Redmi logo, reboots, and repeats that infinitely.
I heard about EDL mode, but that seems atleast so far, unreacheable.
Is there any way for me to reach it? Maybe by letting the battery dry out and then plug the powered off phone with Volume -, or am i out of luck here? Im pretty sure this is caused by the stupid VBMeta checks XIAOMI phones has.
Matsilagi said:
Hey!
I was using my phone as normal, and installed an update for PixelPlusUI, it was working fine and all, until earlier today, i tried going into recovery to fix an app issue. After that, the phone just bootlooped. I figured that going into Fastboot would fix that, but the problem is, i can't reach any of those modes. It just goes to the Redmi logo, reboots, and repeats that infinitely.
I heard about EDL mode, but that seems atleast so far, unreacheable.
Is there any way for me to reach it? Maybe by letting the battery dry out and then plug the powered off phone with Volume -, or am i out of luck here? Im pretty sure this is caused by the stupid VBMeta checks XIAOMI phones has.
Click to expand...
Click to collapse
Vbmeta means Android Verified Boot.
Vbmeta is default for all android devices and it was made by Google.
It is not specific made by Xiaomi.
Android Verified Boot 2.0
https://source.android.com/security/verifiedboot/avb
What changes did you do when you fixed the app issue?
Couldn't do any, just tried to boot into recovery, then got into that bootlooop cycle, couldn't reach anything.
Managed to get into EDL and SP Flash Tool mode, however, im a bit confused on what i need to flash to get it back to life with stock MIUI or atleast boot to main system to use ADB.
My IMEI is fixed on the phone stickers so i can reasily recover that aswell, any help is appreciated.
EDIT: Now i just need help flashing as it seems, what do i need to do to properly re-flash / re-boot the phone without losing IMEI and that sorta stuff? I plan on switching back to Pixel Plus UI again so, it isn't an issue.
EDIT2: Completely fixed, followed VD's guide on EDL/Mediatek Bypass method and flashed a normal GLOBAL rom, all was fixed, no IMEI lost.