Related
I know this is probably posted in the wrong forum but i only have 5 posts....
i flashed the bulletproof kernal from the HTC ONE forum and now my phone is in a boot loop..
i can get into the bootloader but when i try to go into recovery it wont load.
also device is not recognized by pc when connected by usb...
how can i get into twrp to factory reset and flash the viperrom or stock rooted rom?
Seeing as our sprint variant HTC one doesn't have any custom kernels as of yet, you flashed something that does not belong. This is a big no no and you've probably killed your device. You can try hard resetting by holding down the power button until the capacitive buttons stop blinking, then holding volume down and power to get to boot loader, then navigate to recovery. I'm pretty sure you're SOL though.
Sent from my HTCONE using xda app-developers app
whew!! ADB Fastboot saved me, loaded TWRP again through the command prompt and then reflashed the viperrom....!! restoring TB now!
Noted that i will not flash anymore kernals that are not for my phone!
Crisis averted!!
bsjmcconnell said:
whew!! ADB Fastboot saved me, loaded TWRP again through the command prompt and then reflashed the viperrom....!! restoring TB now!
Noted that i will not flash anymore kernals that are not for my phone!
Crisis averted!!
Click to expand...
Click to collapse
Did you do :
"fastboot flash recovery recovery.img" ?
I'm still bootlooping...
Once I got the bootloader to connect fastboot usb, I direct download the twrp recovery .img then In the command prompt
Fastboot flash recovery twrp.img
Then I was able to get into recovery from the bootloader and wipe and reflash viperROM
Sent from my HTCONE using xda app-developers app
Wow. Before bricking your phones, please read my post here:
http://forum.xda-developers.com/showthread.php?p=40678263
Hey guys
I just rooted my HTC One yesterday and installed a custom rom on it, all went well until my brain went stupid and formatted data, system, sdcard and i had no nandroid backup in place. I just upgraded from a HTC One X and from what i know, previously i could just flash CWM and mount usb and it'll go work normally. However, for my situation now, none of the recoveries actually allow me to mount usb.
Also, i'm on 1.29.404 and i can't find any RUUs that is the same as this. I also cant execute adb push for rom because my computer doesnt recognise my phone in adb devices. Can anyone help me out with this issue ?
cheers!
Hi
Greetings,
Install HTC drivers for abd to recognize your phone, this will help you to atempt abd sideload and also fastboot commands
Flash the recovery againg
"fastboot flash recovery name-of-recovery-.img"
And try again by adb sideload this is your last option before flashing a ruu
Sent from my HTC Sensation Z710e using xda premium
mfadhil said:
Hey guys
I just rooted my HTC One yesterday and installed a custom rom on it, all went well until my brain went stupid and formatted data, system, sdcard and i had no nandroid backup in place. I just upgraded from a HTC One X and from what i know, previously i could just flash CWM and mount usb and it'll go work normally. However, for my situation now, none of the recoveries actually allow me to mount usb.
Also, i'm on 1.29.404 and i can't find any RUUs that is the same as this. I also cant execute adb push for rom because my computer doesnt recognise my phone in adb devices. Can anyone help me out with this issue ?
cheers!
Click to expand...
Click to collapse
I'm in a similar boat, did a "format data" in TWRP and now I can't boot. I can access the phone via ADB tho. I'll let you know if I find a solution.
Same thing here
I also did the same thing. However, I can't boot into recovery at all; It says its about to boot into recovery, then the phone just turns off. The only thing I can do is boot into the bootloader, and lock or unlock it. Right now, its unlocked. I've tried everything. I would love to just use an ruu exe., but the only one I've found isn't working for my phone for whatever reason. I kept getting error 132 signature error. The ruu I was using was "RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3" I was using a similar version ( I think it was 1.29.300 or something), and yes, I relocked my bootloader before using the ruu; If anyone knows of a different, newer version, or really, anything at all that can help, it would be greatly appreciated.
Hi
Greetings,
Have to tried this code after installing the recovery
"fastboot erase cache" if not unlock your bootloader install recovery and try this code
Sent from my HTC Sensation Z710e using xda premium
shrex said:
Hi
Greetings,
Have to tried this code after installing the recovery
"fastboot erase cache" if not unlock your bootloader install recovery and try this code
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Hey thanks for replying; Unfourtently, even after reflashing twrp and clearing the cache, it still just shows the entering recovery mode and the restarts. In fact, now it is constantly restarting until I boot it into bootloader and power the system down that way. Any other suggestions?
Thanks
NoDroid4U said:
I also did the same thing. However, I can't boot into recovery at all; It says its about to boot into recovery, then the phone just turns off. The only thing I can do is boot into the bootloader, and lock or unlock it. Right now, its unlocked. I've tried everything. I would love to just use an ruu exe., but the only one I've found isn't working for my phone for whatever reason. I kept getting error 132 signature error. The ruu I was using was "RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3" I was using a similar version ( I think it was 1.29.300 or something), and yes, I relocked my bootloader before using the ruu; If anyone knows of a different, newer version, or really, anything at all that can help, it would be greatly appreciated.
Click to expand...
Click to collapse
that RUU won't work because you have to match your version-main to the RUU you are about to flash, if that version-main doesn't match than you will get that error 132 which is normal in your case... if you want to know which is your version main just type
Code:
fastboot getvar version-main
matt95 said:
that RUU won't work because you have to match your version-main to the RUU you are about to flash, if that version-main doesn't match than you will get that error 132 which is normal in your case... if you want to know which is your version main just type
Code:
fastboot getvar version-main
Click to expand...
Click to collapse
Thanks; I've found the correct ruu, but now I have a new problem. As of right now its .zip and not .exe; I cant boot into recovery and adb isnt working either. Any suggestions for getting it on the phones memory, seeing as there is no sd card I can remove?
I had my phone booting the entering recovery screen for about half a sec and would always boot back into the OS so I installed TWRP through fastboot than went to factory reset in the hboot menu and it booted into recovery it worked for me but Idk if it will work for you
Sent from my HTC One using xda app-developers app
NoDroid4U said:
Thanks; I've found the correct ruu, but now I have a new problem. As of right now its .zip and not .exe; I cant boot into recovery and adb isnt working either. Any suggestions for getting it on the phones memory, seeing as there is no sd card I can remove?
Click to expand...
Click to collapse
i think you downloaded an OTA and not a RUU
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
bradr00lzd00d1 said:
I had my phone booting the entering recovery screen for about half a sec and would always boot back into the OS so I installed TWRP through fastboot than went to factory reset in the hboot menu and it booted into recovery it worked for me but Idk if it will work for you
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
i won't suggest to hit that factory reset button! causa actually it soft-bricked some devices... you've been lucky
bradr00lzd00d1 said:
I had my phone booting the entering recovery screen for about half a sec and would always boot back into the OS so I installed TWRP through fastboot than went to factory reset in the hboot menu and it booted into recovery it worked for me but Idk if it will work for you
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
No such luck; Is there anyway at all to push it to the internal memory using fastboot?
NoDroid4U said:
No such luck; Is there anyway at all to push it to the internal memory using fastboot?
Click to expand...
Click to collapse
as long as i know the only file that you can flash in that OTA is the firmware.zip that will update your bootloader but i'll do it after some more tries...
please paste here the output of
Code:
fastboot getvar all
NoDroid4U said:
No such luck; Is there anyway at all to push it to the internal memory using fastboot?
Click to expand...
Click to collapse
Have you tried "fastboot -w" this will factory reset your phone from fastboot. Then try re-flashing recovery again.
NoDroid4U said:
Hey thanks for replying; Unfourtently, even after reflashing twrp and clearing the cache, it still just shows the entering recovery mode and the restarts. In fact, now it is constantly restarting until I boot it into bootloader and power the system down that way. Any other suggestions?
Thanks
Click to expand...
Click to collapse
I've had this problem on the one x plus, what I did and please bear with me, it does work Firstly flash cwm and clear cache, once you have done that you should be able to boot recovery. Once in cwm format everything including data! yep I said data! then reboot back to fastboot and flash TWRP and rewipe everything again (including data) then sideload or push your rom across to your phone.
Done this twice now on mine when I got bricked (for no reason!) I can only think the file system becomes corrupt somehow.
alright guys, i solved the issue and my phone is back to normal !
to those guys still facing the issue, i suggest you flash the latest cwm then try using the sideload function > adb sideload <filename.zip>
mine came back to life after that, heh
cheers!
Also fixed
Hey guys, thanks so much for everyones help last night. I also got mine all fixed and set away. For anyone interested, I used the ruu and steps in this thread: http://forum.xda-developers.com/showthread.php?t=2250904
Thanks again to everyone for their help!
I've searched everywhere and can't seem to find anything that works for me.
I unlocked my device's bootloader normally through htcdev.com. I then flashed TWRP in fastboot with the following commands:
fastboot flash recovery openrecovery-twrp-2.6.0.1-m7.img
fastboot erase cache
After flashing I can't boot into recovery no matter what. I tried the option from bootloader and adb reboot recovery and the phone simply boots into Android. I have flashed CWM and TWRP many many times.
What's interesting is that my bootloader screen only says unlocked instead of unlocked and tampered. I have M7_UL with hboot 1.44
Any help would be appreciated!
kevdliu said:
I've searched everywhere and can't seem to find anything that works for me.
I unlocked my device's bootloader normally through htcdev.com. I then flashed TWRP in fastboot with the following commands:
fastboot flash recovery openrecovery-twrp-2.6.0.1-m7.img
fastboot erase cache
After flashing I can't boot into recovery no matter what. I tried the option from bootloader and adb reboot recovery and the phone simply boots into Android. I have flashed CWM and TWRP many many times.
What's interesting is that my bootloader screen only says unlocked instead of unlocked and tampered. I have M7_UL with hboot 1.44
Any help would be appreciated!
Click to expand...
Click to collapse
Is fastboot unchecked in Settings -> Power? Make sure it's unchecked then power down. Once it's powered down, enter bootloader, then recovery.
Sent from my HTC One using xda premium
redbull123 said:
Is fastboot unchecked in Settings -> Power? Make sure it's unchecked then power down. Once it's powered down, enter bootloader, then recovery.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yes it was. I finally managed to fix it by repeatedly flashing it over and over and over. I don't even know how doing the same thing many times can produce different results but I guess it did here.
Thanks for the reply.
Hope I can find some help as I ran into what seems to be a pretty serious issue. I haven't been able to find any steps that gets my phone back into booting the actual OS, so posting my specific problem seems to be the only option. A lot of thanks for anyone that can possibly help.
So, followed these instructions to root my phone and get it ready for installing a new ROM, but got stuck at instruction 18.
Which says: (a few before too)
16. OK Now the bootloader is unlocked. Time to install a recovery. In Terminal ./adb reboot bootloader
17. In terminal ./fastboot flash recovery name_of_the_recovery.img (I used recovery-clockwork-6.0.3.1-m7.img)
18. After recovery has flashed POWER DOWN PHONE COMPLETELY Then restart it
Once I did that, I restarted my phone and it loaded up clockwork recovery screen. This seemed fine, but every time I clicked to restart system it keeps on putting me back to this screen.
* I've tried clearing cache and booting, creating a backup and restoring and booting,
* I've got to the bootloader of the OS, but when I go to recovery, it brings me back here.
* I can't connect via the terminal w/ adb or fastboot as it complains it can't connect to device or just waiting for device.
* Neither the Android File Manager nor HTC Sync Manager can connect.
* I've tried only having one application installed for file management hoping that it's just a conflict, but to no avail.
* Can't use an sdcard load since there's no sdcard
* Trying a sideload doesn't work because I can't connect to the device.
I'm afraid I bricked my phone. I hope someone can offer some suggestions.
Again, thank you for your time.
Chris
You can't reboot into bootloader with a longpress of Power + Vol- button under a strong light?
I can get there, to bootloader by using the power and volume down, but no matter what option i pick it gets me back to clockworkmod. I've tried connecting then via terminal, but still nothing. Pretty frustrating.
In fastboot with the command:
Code:
fastboot devices
you can't see your phone?
If yes, flash the latest TWRP/CWM, do an erase cache and flash or sideload a rom
Right, nothing is output w/ that. Neither in bootloader or clockworkmod screen.
You've the right driver installed?
And, in device manager you can see your phone without any yellow triangle?
p.s. are you using windows, right?
Forgot to mention that, I'm on a Macbook Pro.
So Fastboot flash different recovery does not work?
When you where in recovery, did you flash any new ROM?
Sent from my HTC One using XDA Premium 4 mobile app
herrfricke said:
Forgot to mention that, I'm on a Macbook Pro.
Click to expand...
Click to collapse
So you have to add a
Code:
./
before the fastboot/adb command.
In fastboot type:
Code:
./fastboot devices
and check if you can see your device
Sindroid said:
So Fastboot flash different recovery does not work?
Click to expand...
Click to collapse
If atm he can't recognize his device how he can flash a recovery?
Sindroid said:
So Fastboot flash different recovery does not work?
When you where in recovery, did you flash any new ROM?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the command... sadly it just says waiting for device. The core problem it seems now is that my computer won't recognize the USB connection for this device.
I think I just found out what I did wrong
instead of running this:
./fastboot flash recovery recovery-clockwork-6.0.3.1-m7.img
I ran this:
/fastboot flash boot recovery-clockwork-6.0.3.1-m7.img
based on command history. Crap.
If atm he can't recognize his device how he can flash a recovery?[/QUOTE]
Yeah, I know, only way you can get the whole process working is by adding ./ or if you wanted to put it on your $PATH variable, but that would be pointless.
Well your op says you attempted to do backups and restore, so you obviously seem to have CWM installed.
Sent from my HTC One using XDA Premium 4 mobile app
Sindroid said:
Well your op says you attempted to do backups and restore, so you obviously seem to have CWM installed.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, it's installed. Just I think now because it was put on as a boot vs recovery it's treating it as the OS, possibly, so when I try to boot the system,it just boots CWM. The OS is there though, if I do a backup you can see all the files (especially proprietary stuff from HTC) still on the drive. But w/o access to it via terminal I don't know if there's a way to fix the boot problem. I can get to the bootloader,if I only it could mount to my computer from there (or even in CWM). Access to the phones drive seems to be the only way to clean it up.
herrfricke said:
Hope I can find some help as I ran into what seems to be a pretty serious issue. I haven't been able to find any steps that gets my phone back into booting the actual OS, so posting my specific problem seems to be the only option. A lot of thanks for anyone that can possibly help.
So, followed these instructions to root my phone and get it ready for installing a new ROM, but got stuck at instruction 18.
Which says: (a few before too)
16. OK Now the bootloader is unlocked. Time to install a recovery. In Terminal ./adb reboot bootloader
17. In terminal ./fastboot flash recovery name_of_the_recovery.img (I used recovery-clockwork-6.0.3.1-m7.img)
18. After recovery has flashed POWER DOWN PHONE COMPLETELY Then restart it
Once I did that, I restarted my phone and it loaded up clockwork recovery screen. This seemed fine, but every time I clicked to restart system it keeps on putting me back to this screen.
* I've tried clearing cache and booting, creating a backup and restoring and booting,
* I've got to the bootloader of the OS, but when I go to recovery, it brings me back here.
* I can't connect via the terminal w/ adb or fastboot as it complains it can't connect to device or just waiting for device.
* Neither the Android File Manager nor HTC Sync Manager can connect.
* I've tried only having one application installed for file management hoping that it's just a conflict, but to no avail.
* Can't use an sdcard load since there's no sdcard
* Trying a sideload doesn't work because I can't connect to the device.
I'm afraid I bricked my phone. I hope someone can offer some suggestions.
Again, thank you for your time.
Chris
Click to expand...
Click to collapse
As I gathered from your description, you are using a MAC.
I think you should use your friends PC to use the command to install the recovery and see if it solves the problem.
Alternatively you can use Heimdall Terminal fir MAC, which is sort of ODIN for MAC and try to reinstall your firmware.
Sent from my GT-I9070 using xda app-developers app
redndian said:
As I gathered from your description, you are using a MAC.
I think you should use your friends PC to use the command to install the recovery and see if it solves the probkem.
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
I can use virtual box now... i'll give it a try.
I use Mac as well and I ran into same connectivity problems as you do, but it was not during unlocking, rooting.. I had a Bootloop going with some mods conflicts, anyway, not important. I used my missus win 7 laptop and there it would see it and I could fix my problems there. Mac has had issues with SdK not working.
Alas, do run the Fastboot flash recovery command if you get it talking, as you temporarily can access CWM before flashing it permanently.
Sent from my HTC One using XDA Premium 4 mobile app
redndian said:
As I gathered from your description, you are using a MAC.
I think you should use your friends PC to use the command to install the recovery and see if it solves the problem.
Alternatively you can use Heimdall Terminal fir MAC, which is sort of ODIN for MAC and try to reinstall your firmware.
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
Wait, heimdall is for samsung as i know.
And is different flash firmware for samsung and htc
Sent from One with Tapa4
Guich said:
Wait, heimdall is for samsung as i know.
And is different flash firmware for samsung and htc
Tried googling, and I found that it is samsung specific
I stand corrected.
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
I have a similar problem
My specs:
M7_WLS PVT SHIP S-ON RH
HBOOT 1.44 UNLOCKED
RADIO 1.00.20.0626
OpenDSP v31.120.274.0617
eMMC-boot
Jul 5 2013, 17:19:22:-1
TWRP v2.6.3 - working correctly
I have no backup and no ROM on my phone
I can access HBOOT just fine via power + vol down
Team Win Recovery also seems to function properly
My phone is not listed under adb devices
and the worst of all, my phone won't connect to my PC!!
Here is the problem,
I got bored with my stock ROM, so I decided to try CyanogenMod 10.1. Having installed a few ROMs in the past, I felt comfortable tampering with the software on my HTC One (Sprint). I first had clockworkmod flashed and I booted to HBOOT and wiped everything I had an option to wipe. I fear this was my mistake, I also did not create a backup prior to my tampering. After wiping my phone with clockwork, I tried moving the Cyanogen zip to my phone. This is when I noticed my phone would not connect to the PC. I tried different PC's and cords. I am using USB 2.0 and the laptop even makes a ding noise when I enter fastboot usb. My phone is not listed in C: drive, device manager, or adb devices.
I now have flashed TWRP and made sure all my drivers are up to date. I installed HTC Sync Manager, which can not find my phone. I tried to send the cyanogen zip to my phone via fastboot flash zip cm-10.1.3-m7spr.zip. This failed to pass signature verification test. I thought being unlocked bypassed the sig check but I guess not. I tried to gain S-OFF using revone. I couldn't send revone to my phone either. I also tried installing the stock ruu. I got my phone to the black HTC screen and ran the ruu.exe and whammo! ERROR [155] UNKNOWN ERROR...
I'm looking for a way to move my rom zip file to my phone so I can install via TWRP. Any help would be GREATLY appreciated! Thank you!
NWC83 said:
My specs:
M7_WLS PVT SHIP S-ON RH
HBOOT 1.44 UNLOCKED
RADIO 1.00.20.0626
OpenDSP v31.120.274.0617
eMMC-boot
Jul 5 2013, 17:19:22:-1
TWRP v2.6.3 - working correctly
I have no backup and no ROM on my phone
I can access HBOOT just fine via power + vol down
Team Win Recovery also seems to function properly
My phone is not listed under adb devices
and the worst of all, my phone won't connect to my PC!!
Here is the problem,
I got bored with my stock ROM, so I decided to try CyanogenMod 10.1. Having installed a few ROMs in the past, I felt comfortable tampering with the software on my HTC One (Sprint). I first had clockworkmod flashed and I booted to HBOOT and wiped everything I had an option to wipe. I fear this was my mistake, I also did not create a backup prior to my tampering. After wiping my phone with clockwork, I tried moving the Cyanogen zip to my phone. This is when I noticed my phone would not connect to the PC. I tried different PC's and cords. I am using USB 2.0 and the laptop even makes a ding noise when I enter fastboot usb. My phone is not listed in C: drive, device manager, or adb devices.
I now have flashed TWRP and made sure all my drivers are up to date. I installed HTC Sync Manager, which can not find my phone. I tried to send the cyanogen zip to my phone via fastboot flash zip cm-10.1.3-m7spr.zip. This failed to pass signature verification test. I thought being unlocked bypassed the sig check but I guess not. I tried to gain S-OFF using revone. I couldn't send revone to my phone either. I also tried installing the stock ruu. I got my phone to the black HTC screen and ran the ruu.exe and whammo! ERROR [155] UNKNOWN ERROR...
I'm looking for a way to move my rom zip file to my phone so I can install via TWRP. Any help would be GREATLY appreciated! Thank you!
Click to expand...
Click to collapse
I once had a similar problem with my samsung abd tried this ..
1. Remove sd card from your phone.
2. Put the sd card in a card reader and copy your firmware on sd card through yout pc
3. Refit the sd card in your phone
4. Flash firmware through recovery.
I hope this helps.
Sent from my GT-I9070 using xda app-developers app
My Mi 5 was working just fine (and it is, right now), I've flashed RR for a few months, today I wanted to update it by flashing the latest zip but suddenly touchscreen does not work on twrp recovery (it was fine before. nothing particular happend before)! I let the screen to turn off (on twrp) and then turned it on so it might be fixed but it didn't. So I tried to flash the leatest twrp (it was 3.0.2.0) using adb but my phone turns off after a few seconds on fastboot mode! any idea?
SOLVED, USING OFFICIAL TWRP APP.
catalizgar said:
My Mi 5 was working just fine (and it is, right now), I've flashed RR for a few months, today I wanted to update it by flashing the latest zip but suddenly touchscreen does not work on twrp recovery (it was fine before. nothing particular happend before)! I let the screen to turn off (on twrp) and then turned it on so it might be fixed but it didn't. So I tried to flash the leatest twrp (it was 3.0.2.0) using adb but my phone turns off after a few seconds on fastboot mode! any idea?
Click to expand...
Click to collapse
Latest official twrp is v3.0.2-3 you can try flash and download it from here https://dl.twrp.me/gemini/
Sent from my MI 5 using Tapatalk
I've downloaded it
JJeamy said:
Latest official twrp is v3.0.2-3 you can try flash and download it from here https://dl.twrp.me/gemini/
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
I've downloaded it, but the fastboot mode is not stable and after a few seconds the phone turns off
catalizgar said:
I've downloaded it, but the fastboot mode is not stable and after a few seconds the phone turns off
Click to expand...
Click to collapse
Just try flashing it with quick..prepare typing "fastboot flash recovery twrp.img" first then get your phone into fastboot mode, connect then enter..
Alternative way is..if your bootloader still at unlocked state..you can try boot into edl mode by command "fastboot oem edl" the flash miui fastboot rom to revert back to the original state again first..then see if fastboot issue stikk there..if not you can continue repeat the step to unlocking BL again (if the boooader already relocked after flashing) if not..just try reboot into fastboot then flash twrp again.
Sent from my MI 5 using Tapatalk
JJeamy said:
Latest official twrp is v3.0.2-3 you can try flash and download it from here https://dl.twrp.me/gemini/
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
For me that also does not work.
oktaya said:
For me that also does not work.
Click to expand...
Click to collapse
What you mean that also doesn't work..?, what part..?, installing twrp..or what else..?
catalizgar said:
My Mi 5 was working just fine (and it is, right now), I've flashed RR for a few months, today I wanted to update it by flashing the latest zip but suddenly touchscreen does not work on twrp recovery (it was fine before. nothing particular happend before)! I let the screen to turn off (on twrp) and then turned it on so it might be fixed but it didn't. So I tried to flash the leatest twrp (it was 3.0.2.0) using adb but my phone turns off after a few seconds on fastboot mode! any idea?
Click to expand...
Click to collapse
i have the same problem. I can go to TWRP but touchscreen not work. In my case fastboot is stabile, but when i plug in my mi5 to computer (w10) its don't see him on adb fastboot.
Marcinek91 said:
i have the same problem. I can go to TWRP but touchscreen not work. In my case fastboot is stabile, but when i plug in my mi5 to computer (w10) its don't see him on adb fastboot.
Click to expand...
Click to collapse
solved it. :highfive::victory:
use twrp official app to flash latest recovery image. (root is required)
Marcinek91 said:
i have the same problem. I can go to TWRP but touchscreen not work. In my case fastboot is stabile, but when i plug in my mi5 to computer (w10) its don't see him on adb fastboot.
Click to expand...
Click to collapse
JJeamy said:
Just try flashing it with quick..prepare typing "fastboot flash recovery twrp.img" first then get your phone into fastboot mode, connect then enter..
Alternative way is..if your bootloader still at unlocked state..you can try boot into edl mode by command "fastboot oem edl" the flash miui fastboot rom to revert back to the original state again first..then see if fastboot issue stikk there..if not you can continue repeat the step to unlocking BL again (if the boooader already relocked after flashing) if not..just try reboot into fastboot then flash twrp again.
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
solved it using twrp official app
JJeamy said:
What you mean that also doesn't work..?, what part..?, installing twrp..or what else..?
Click to expand...
Click to collapse
Sorry I haven't been on the site after using TWRP through ADB and taking care of my needs that way. What doesn't work is the same thing that didn't work for me with any TWRP image. Touchscreen does not respond to anything and letting it idle does not make a difference. I tried all of the available TWRP images (at the time) and did not find one that works. Luckily I found a tutorial showing how to use TWRP through ADB and frankly that is more user friendly in some ways since I've worked on Linux for a long time.