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!
Hey guys
So, long story short, i ended up in a bootloop after trying to install cm13 (it seems the problem is i forgot to wipe dalvik cache after flashing rom), my phone doesn't get past the manufacterer's logo si i can´t use adb and every time i try to get in to the recovery, it sticks on the TWRP logo for a while and then starts over rebooting, i can never get past the TWRP screen. The only place where it doesn't start rebooting again is at fastboot menu. Also, i read that i could always use RSD Lite, but despite i wouldn´t like to, i haven´t been able to get RSD to recognize my phone.
I don´t now is there is any obvious solution, i'm kind of a noobie.
Any help is appreciated, thank you very much
bazanster said:
Hey guys
So, long story short, i ended up in a bootloop after trying to install cm13 (it seems the problem is i forgot to wipe dalvik cache after flashing rom), my phone doesn't get past the manufacterer's logo si i can´t use adb and every time i try to get in to the recovery, it sticks on the TWRP logo for a while and then starts over rebooting, i can never get past the TWRP screen. The only place where it doesn't start rebooting again is at fastboot menu. Also, i read that i could always use RSD Lite, but despite i wouldn´t like to, i haven´t been able to get RSD to recognize my phone.
I don´t now is there is any obvious solution, i'm kind of a noobie.
Any help is appreciated, thank you very much
Click to expand...
Click to collapse
Flash a stock ROM, preferably LP and see if it works, this is done through fastboot, look around.
bazanster said:
Hey guys
So, long story short, i ended up in a bootloop after trying to install cm13 (it seems the problem is i forgot to wipe dalvik cache after flashing rom), my phone doesn't get past the manufacterer's logo si i can´t use adb and every time i try to get in to the recovery, it sticks on the TWRP logo for a while and then starts over rebooting, i can never get past the TWRP screen. The only place where it doesn't start rebooting again is at fastboot menu. Also, i read that i could always use RSD Lite, but despite i wouldn´t like to, i haven´t been able to get RSD to recognize my phone.
I don´t now is there is any obvious solution, i'm kind of a noobie.
Any help is appreciated, thank you very much
Click to expand...
Click to collapse
I faced the same problem here is what i did
flash the twrp2.8.x again in fastboot mode
boot into recovery
restore your backup if you have backedup your previous rom
Rohit99 said:
I faced the same problem here is what is did
flash the twrp2.8.x again in fastboot mode
boot into recovery
restore your backup if you have backedup your previous rom
Click to expand...
Click to collapse
Thanks man, as simple as it was, it worked <3
I have update my rooted OP 3T by flashing the complete rom through TWRP.. But the problem is whenever I flash the Supersu version : SuperSU-v2.79-201612051815 or SR3-SuperSU-v2.79-SR3-20170114223742, I am getting bootloop.
Please anyone advise me.
I checked that without flashing SuperSU phone is able to Boot safely.
Thank you in advance.
It's normal if it bootloops once or twice
But if it's more than that then it's problematic
So which one is it
Another thing you can try is try magisk root instead of supersu and see if gets the same result
Phone was stucked in bootloop for an hour without any reboot.
I am not fond of magisk yet... So dont have any plan for it.
Just want to know if this happens to only me or there are many others with same issue.
Edit:
Finally installed Magisk for root... Issue closed.
help!?
hi guys i am amber
yesterday i was trying to unroot my device [op3t] i locked the boot loader but after that my device started
bootlooping i was able to get to fastboot but none of the commands were working i can not boot into recovery coz there is no recovery on my device i am not able to flash any thing .
plzz can anyone help me
amber sachdeva said:
hi guys i am amber
yesterday i was trying to unroot my device [op3t] i locked the boot loader but after that my device started
bootlooping i was able to get to fastboot but none of the commands were working i can not boot into recovery coz there is no recovery on my device i am not able to flash any thing .
Click to expand...
Click to collapse
That is not the proper way to unroot (go back to stock). Relocking the bootloader while rooted was asking for trouble. There is a guide on how to return to stock in the Guides section.
Also, fastboot commands will only work while in fastboot mode, if the phone is looping, or otherwise stuck on any other screen/mode, than fastboot commands will not work. It's also a bit irrelevant, as your ability to flash anything with a locked bootloader is very limited. That's the whole purpose of a locked bootloader.
I'd start by making sure you are in fastboot, get fastboot working, and unlock the bootloader again. Then follow the proper process to return to stock.
redpoint73 said:
That is not the proper way to unroot (go back to stock). Relocking the bootloader while rooted was asking for trouble. There is a guide on how to return to stock in the Guides section.
Also, fastboot commands will only work while in fastboot mode, if the phone is looping, or otherwise stuck on any other screen/mode, than fastboot commands will not work. It's also a bit irrelevant, as your ability to flash anything with a locked bootloader is very limited. That's the whole purpose of a locked bootloader.
I'd start by making sure you are in fastboot, get fastboot working, and unlock the bootloader again. Then follow the proper process to return to stock.
Click to expand...
Click to collapse
well i tried unlocking bootloader but it says failed (remote: oem unlock not allowed)
Iam i stuck here for ever ?
can u tell me the command that i can try on an phone with a locked bootloader
I forgot this is an edit the first time Gentlemen, I am absolutely at wit's end now I am no geek with a capital G however I have been modifying phones for some 3 years now and I can't even tell you how many times I flashed ROMs my beloved 3T 3T has had been acting glitchy lately like when I would reboot the circle that turns - instead of just turning evenly it would twitch, it was such a small thing I ignored it but I think now that that's must be have been indication something was not right few other things like that. I flashed the Freedom ROM cuz I'm so sick a Google and Google Assistant when I came out I was in a bootloop so I wiped everything except OTG everything and formatted data did the ROM Flash again the a boot Loop still abides and I've done it a dozen times now sometimes a couple of times it it just it kept recycling the bootloop another time and got hung up on the OnePlus it just sat there on the logo and if I miss something obvious I do apologize I'm tired and I'm at wits end because I'm not used to not being able to solve my own problems I guess so any help at all or just even a heading in the right direction would be so much appreciated that I don't even know how to call it quantify it thank you
By the way I seldom post or even post questions but when I do I always pretty much say the same thing you guys are the best this is the one place I can come for Andrew Android advice or or guidance and I just I absolutely trust what I read so thank you thank you thank you thanks for being there
Edit - I'm so tired I forgot the first time I went to reflash the ROM it told me that my 3T was in fact not a 3T that it was a three and I read someplace so I'm XDA that that's just Corruption of the install script so I downloaded it again I ran 7-Zip it said it was coherent so I flash it again if that's important but thanks again
Help required
kunal1540 said:
it's normal if it bootloops once or twice
but if it's more than that then it's problematic
so which one is it
another thing you can try is try magisk root instead of supersu and see if gets the same result
Click to expand...
Click to collapse
sir, i have oneplus 3t a3010. Last night my phone was crashed and after crashing it restarts and jumps to recovery mode. In recovery mode i wipe all data and restart my phone. But i still doing the restart thing. Please help, what to do now.
Plzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
My oneplus 3 is stuck in recovery mode
My bootloader is locked
Everytime i switch on my phone there is a message
Which is on photo below
My device is stuck in the initial boot sequence in which the logo will show as if it is booting normally, then it will stay on this screen until it goes completely blank, at which point I have to hold the power button for a long period of time to get it back to the boot sequence. My phone is unlocked and I was trying my first time at flashing a custom recovery and OS, I flashed my device with TWRP and successfully installed it along with a flash of pixel experience, After using pixel experience I wanted to try lineage OS since it wasn't as good as I hoped, so I tried to get into the TWRP and I could not do it at all I tried every method I could search. After an hour of trying different methods of getting to twrp I tried to re-flash the recovery and that is when the phone because unresponsive and does what I have described above. I currently have access to fast boot and I dont want to go ****ing my phone up more than I have. If anyone can give me a step by step guide on how to fix this it would help so much since im new to android and I cant afford another £400 phone.
Thanks
BJack0 said:
My device is stuck in the initial boot sequence in which the logo will show as if it is booting normally, then it will stay on this screen until it goes completely blank, at which point I have to hold the power button for a long period of time to get it back to the boot sequence. My phone is unlocked and I was trying my first time at flashing a custom recovery and OS, I flashed my device with TWRP and successfully installed it along with a flash of pixel experience, After using pixel experience I wanted to try lineage OS since it wasn't as good as I hoped, so I tried to get into the TWRP and I could not do it at all I tried every method I could search. After an hour of trying different methods of getting to twrp I tried to re-flash the recovery and that is when the phone because unresponsive and does what I have described above. I currently have access to fast boot and I dont want to go ****ing my phone up more than I have. If anyone can give me a step by step guide on how to fix this it would help so much since im new to android and I cant afford another £400 phone.
Thanks
Click to expand...
Click to collapse
try booting twrp
'fastboot boot img name' then flash recovery from there. hope it works.
BJack0 said:
My device is stuck in the initial boot sequence in which the logo will show as if it is booting normally, then it will stay on this screen until it goes completely blank, at which point I have to hold the power button for a long period of time to get it back to the boot sequence. My phone is unlocked and I was trying my first time at flashing a custom recovery and OS, I flashed my device with TWRP and successfully installed it along with a flash of pixel experience, After using pixel experience I wanted to try lineage OS since it wasn't as good as I hoped, so I tried to get into the TWRP and I could not do it at all I tried every method I could search. After an hour of trying different methods of getting to twrp I tried to re-flash the recovery and that is when the phone because unresponsive and does what I have described above. I currently have access to fast boot and I dont want to go ****ing my phone up more than I have. If anyone can give me a step by step guide on how to fix this it would help so much since im new to android and I cant afford another £400 phone.
Thanks
Click to expand...
Click to collapse
Don't worry, things can be recovered easily. Until you get more knowledgeable and you understand more about flashing use this failsafe to recover from (almost) anything
Go here and get the latest fastboot ROM for your phone.
https://xiaomifirmwareupdater.com/miui/raphael/
For now make sure you get the one that matches the region for your phone.
Then follow this guide to flash it
https://c.mi.com/thread-1857937-1-1.html
Use the fastboot flashing section.
Make sure you change the flash option to 'clean all' when flashing. The default option will lock the bootloader again after flashing. If you do the default option with any ROM that is not the same region as the phone you will hard brick the phone, this is why I recommend getting the ROM that matches your phone.
When unpacking the fastboot ROM, it is a Linux/Unix zipped tarball, most Windows zip software will need to extract it twice. The first time will give you a single .tar file (if it doesn't have an extension then rename it and add .tar to the end) You will then need to extract everything from the tar file, which you give you the folder, containing the ROM data, to point the Mi Flash Tool at.
After doing this you, if you've remembered to change the flash option to 'clean all', then you'll have restored to stock and kept the bootloader unlocked. Now you're good to try again.
Keep a copy of the fastboot ROM on your PC and back everything up on your phone before flashing. Then if you get in a mess you know how to easily recover things.
Once you get more experienced there will be other things you might be able to do, depending on the situation, that allow you to get things working without losing everything and needing to start from scratch.
Thanks
Robbo.5000 said:
Don't worry, things can be recovered easily. Until you get more knowledgeable and you understand more about flashing use this failsafe to recover from (almost) anything
Click to expand...
Click to collapse
Thank you so much for the details post, I will try what you have said above and will report back with my results. I have one question if you know the answer ( My phone is the UK edition of the Mi 9T pro ) Would I need to download the global or EEA fastboot version.
BJack0 said:
Thank you so much for the details post, I will try what you have said above and will report back with my results. I have one question if you know the answer ( My phone is the UK edition of the Mi 9T pro ) Would I need to download the global or EEA fastboot version.
Click to expand...
Click to collapse
For safety download the EEA ROM.
I also suggest you immediately flash dm_verity (https://forum.xda-developers.com/k20-pro/how-to/flashing-orangefox-recovery-mi-9t-pro-t3980579), after you flash twrp, wipe data and then flash that
Sent from my Redmi K20 Pro using Tapatalk
Robbo.5000 said:
For safety download the EEA ROM.
Click to expand...
Click to collapse
Everything you said worded flawlessly and your a life saver. If you dont mind do you have a link to a set of guides on how to correctly flash a custom recovery and lineage OS? since when I try to research these guides I get 5 different versions of TWRP and lock my phone out :laugh:
ishaqtkr said:
I also suggest you immediately flash dm_verity after you flash twrp, wipe data and then flash that
Click to expand...
Click to collapse
If you dont mind me asking could you go into slightly more detial on that since I have seen orange fox but I dont understand what dm_verity is.
Please ignore all reply's above as I am going to make another separate post about lineage OS
Thank you for replying and resolving my issue.
Have tried flashing various miui and a few custom roms, all get stuck on animation. Have tried miui fastboot roms first build and latest, pretty much everything I can think of to no avail. Am I missing something? Open to any suggestions to get this phone working again. Fastboot and recovery (custom and stock) all work, flashing works it just won't get past that loading screen.
hoopsnake said:
Have tried flashing various miui and a few custom roms, all get stuck on animation. Have tried miui fastboot roms first build and latest, pretty much everything I can think of to no avail. Am I missing something? Open to any suggestions to get this phone working again. Fastboot and recovery (custom and stock) all work, flashing works it just won't get past that loading screen.
Click to expand...
Click to collapse
If flashing a fastboot ROM isn't working, then maybe something physically has gone wrong with the phone. Are you using the clean all or the keep data option, when flashing? Make sure you're using the clean all option (but definitely not the clean and lock option).
Fastboot ROMs are normally the last resort, failsafe way to recover the phone, so it's unusual for them not to work.
Also how long are you waiting at the initial animation screen?
Also try a different, good quality USB lead and/or a different USB port and/or a different PC if you can.
Robbo.5000 said:
If flashing a fastboot ROM isn't working, then maybe something physically has gone wrong with the phone. Are you using the clean all or the keep data option, when flashing? Make sure you're using the clean all option (but definitely not the clean and lock option).
Fastboot ROMs are normally the last resort, failsafe way to recover the phone, so it's unusual for them not to work.
Also how long are you waiting at the initial animation screen?
Also try a different, good quality USB lead and/or a different USB port and/or a different PC if you can.
Click to expand...
Click to collapse
Something more than likely broke hardware wise.
Always clean all, but unfortunately after many hours of trying I misclicked and locked a few hours ago, on the stock rom but which would of been lucky if I wasn't already stuck in bootloop.
Next option, took back panel off and had a look, red water indicator near headphone jack, the rest are still white so many some sort of water damage has happened idk how, everything else is clean and dry.
Next best bet is edl with a authorized mi account (no luck yet) or just ship it off to Xiaomi.
Umm, what did you do before you got this problem?
tbh, most users just skip a step and then nothing works. I'm assuming this is the case?
What is your phone variant? previous ROM? ROM you tried to apply?
what vendor are you using? and most importantly, what steps are you doing to flash the new rom.
Sandeeep Kiran said:
Umm, what did you do before you got this problem?
tbh, most users just skip a step and then nothing works. I'm assuming this is the case?
What is your phone variant? previous ROM? ROM you tried to apply?
what vendor are you using? and most importantly, what steps are you doing to flash the new rom.
Click to expand...
Click to collapse
Literally nothing, flashed global stable zip a week before with f2fs, and dfe, it was about a week without modifying anything or even entering twrp and it just did a random reboot then just died and started boot looping.
K20 Pro, previous was lineage os, format data to get back to miui, flash miui, f2fs, dfe.
Now since bootloop, and edl, fastboot, recovery all work but with locked bootloader, I guess only option is edl flash.
My mi account must be magic or something, so downloaded mi unlock and bootloader unlocked immediately, no wait time. Was very surprised so to double check did fastboot OEM device-info and indeed bootloader is unlocked. Now flashing fastboot rom fingers crossed.
IT BOOTED, I have my phone backkkkkk. No idea how or what happened, happened but it's back up and running hopefully for good.
Somehow locking and unlocking bootloader fixed it.