Ill try to describe my situation as best I can but if I miss something feel free to ask.
So a tried to root my phone and flash a new rom a few days ago, everything was going well until I flashed the rom (Android Revolution).
It took me back to the bootloader and now its stuck in bootloop. I can get to recovery just fine but whenever I try to flash anything or sideload it says it can't find my device.
When I'm in fastboot it can find my phone just fine and it works from there, but if I try ADB it cant find it.
My phone is Sprint HTC One on 1.31, with 4.2 update, unlocked with TWRP recovery, S-ON, and what seems like no OS.
I'm sorry if this has been asked before but after spending 2+ days trying to fix my phone and digging the forums to no avail all I think I can do is ask for help.
[Fixed]
bigdaddy619 helped me out, think the problem was that I was missing some ADB files on my computer and didn't have the latest the Android SDK.
He changed it to work with the 1.29 update with the command:
adb shell
echo 1.29.00 | dd if=/dev/block/mmcblk0p19 bs=1 skip=160
adb reboot bootloader
NotSneakyNinja said:
Ill try to describe my situation as best I can but if I miss something feel free to ask.
So a tried to root my phone and flash a new rom a few days ago, everything was going well until I flashed the rom (Android Revolution).
It took me back to the bootloader and now its stuck in bootloop. I can get to recovery just fine but whenever I try to flash anything or sideload it says it can't find my device.
When I'm in fastboot it can find my phone just fine and it works from there, but if I try ADB it cant find it.
My phone is Sprint HTC One on 1.31, with 4.2 update, unlocked with TWRP recovery, S-ON, and what seems like no OS.
I'm sorry if this has been asked before but after spending 2+ days trying to fix my phone and digging the forums to no avail all I think I can do is ask for help.
Click to expand...
Click to collapse
It's been asked about 1500 times by people who don't take the time to read before they flash. You flashed a GSM Rom on your CDMA phone.
Now to fix it follow this guide
http://forum.xda-developers.com/showthread.php?p=44243635
To make your life easy you will need drivers for your phone the best are the universal naked drivers for HTC One
http://forum.xda-developers.com/showthread.php?t=2263822
If installed, uninstall HTC sync, and disable any anti virus or firewalls including Windows firewall. You will also need to download ADB if you don't have it minimal ADB is great
http://forum.xda-developers.com/showthread.php?p=42407269
Next time read before you flash!
Sent from my HTCONE using xda app-developers app
Related
Yep, I broked it.
So, wanna hear a fun story?
I got a free Hero, and tried to root it. First thing I tried was z4root. It failed. Then I tried RegawMod. Fail. Perhaps it didn't help that I had the latest stock version of the Hero, 2.32.651.x
So, then, me being a wise guy, decided that I'd just try doing it myself through ADB. I tried to follow CyanogenMod adb rooting instructions HERE. I kept getting stuck at step 5:
chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
Click to expand...
Click to collapse
It kept saying something about how it couldn't chmod "/data/local/tmp/rageagainstthecage-arm5.bin" because it wasn't a directory. Well, duh, this I know...but I couldn't figure out how to make adb understand that.
Well of course, because I couldn't chmod rageagainstthecage, I couldn't move on to the next step, actually running ratc:
/data/local/tmp/rageagainstthecage-arm5.bin
Click to expand...
Click to collapse
Now, this is where the fun really begins. I rebooted the Hero, just to see if that would help, and then I was going to try again. Trouble is, the phone wouldn't boot. Kept getting stuck on an endless boot on the HTC screen. So, I went into clockworkmod, wiped everything (except boot), and then restored the nandroid backup I had made before I started this whole process. Still no dice. Still stuck at an endless HTC boot screen. I tried a hard reset on the fastboot menu just for ****s and giggles...but still nothing doing. I also tried running the RUU app on my computer to install an older version of the stock ROM, but RUU would not recognize my device (even though HTC sync and ALL of the drivers are installed, and I had it mounted to the computer in clockworkmod).
So...I guess my question is - does anyone have any clue how to fix this? I still want to root the damn thing, but right now I'd be happy just to get the stock rom back up and running. I know if I could find a stock ROM I could probably flash it through clockworkmod...alas, the only one I found turned out to be a corrupt zip file.
Any help is appreciated. Thanks!
u do realize if u have clockwork mod u are rooted right...
Bierce22 said:
u do realize if u have clockwork mod u are rooted right...
Click to expand...
Click to collapse
I'm not sure how, as all three methods I tried to root failed. I even tested it with terminal emulator, got all $, no #. Of course, that was back when I could actually get to Terminal Emulator.
Bling_Diggity said:
I'm not sure how, as all three methods I tried to root failed. I even tested it with terminal emulator, got all $, no #. Of course, that was back when I could actually get to Terminal Emulator.
Click to expand...
Click to collapse
look here for the RUU.zip made by tehdarkknight, get it. Then run in with the instructions from jasonmaloneys thread about fastboot without s-off. http://forum.xda-developers.com/showthread.php?t=1063843
EDIT: that *should" unroot you back to stock. Then follow the REAL rooting thread (adb method) by regaw leinad.
PLEASE DISREGARD this thread. I'm an idiot...apparently the damn thing was rooted before I got it...which explains why my attempts to root it weren't working. Flashed CM7 in clockworkmod and it booted up with no problems.
Bling_Diggity said:
PLEASE DISREGARD this thread. I'm an idiot...apparently the damn thing was rooted before I got it...which explains why my attempts to root it weren't working. Flashed CM7 in clockworkmod and it booted up with no problems.
Click to expand...
Click to collapse
Yeah, that's what bierce22 was saying - if you already had clockworkmod, you were already rooted. But it was a good learning experience for you, right?
no one ever listens to me around here lmao.
Lmao thats hilarious. I fail. Bierce FTW.
sent from a series of tubes.
Bling_Diggity said:
Yep, I broked it.
So, wanna hear a fun story?
I got a free Hero, and tried to root it. First thing I tried was z4root. It failed. Then I tried RegawMod. Fail. Perhaps it didn't help that I had the latest stock version of the Hero, 2.32.651.x
So, then, me being a wise guy, decided that I'd just try doing it myself through ADB. I tried to follow CyanogenMod adb rooting instructions HERE. I kept getting stuck at step 5:
It kept saying something about how it couldn't chmod "/data/local/tmp/rageagainstthecage-arm5.bin" because it wasn't a directory. Well, duh, this I know...but I couldn't figure out how to make adb understand that.
Well of course, because I couldn't chmod rageagainstthecage, I couldn't move on to the next step, actually running ratc:
Now, this is where the fun really begins. I rebooted the Hero, just to see if that would help, and then I was going to try again. Trouble is, the phone wouldn't boot. Kept getting stuck on an endless boot on the HTC screen. So, I went into clockworkmod, wiped everything (except boot), and then restored the nandroid backup I had made before I started this whole process. Still no dice. Still stuck at an endless HTC boot screen. I tried a hard reset on the fastboot menu just for ****s and giggles...but still nothing doing. I also tried running the RUU app on my computer to install an older version of the stock ROM, but RUU would not recognize my device (even though HTC sync and ALL of the drivers are installed, and I had it mounted to the computer in clockworkmod).
So...I guess my question is - does anyone have any clue how to fix this? I still want to root the damn thing, but right now I'd be happy just to get the stock rom back up and running. I know if I could find a stock ROM I could probably flash it through clockworkmod...alas, the only one I found turned out to be a corrupt zip file.
Any help is appreciated. Thanks!
Click to expand...
Click to collapse
My story is similar. Boot into hboot stay in fastboot mode and DO NOT VOL DOWN. once youve booted into hboot, plug the hero In and get the ruu started up. Once you've started the ruu, if you get the connection error message, click the action button (trackball) on 'fastboot usb mode' and for some reason, the ruu seemed to connect to it then. Hope it works out for ya.
Sent from my HERO200 using XDA Premium App
Also, when rooting with z4, do a temporary first then after a successful temporary root, hit the permanent button. That's done the trick for me in countless seemingly hopeless situations.
Sent from my HERO200 using XDA Premium App
Hi all. Yesterday I tried to flash ARHD with TWRP and got an error that others seemed to experience with this ROM on TWRP: at 99% it sent me back into bootloader and I couldn't do anything, it was pretty much stuck there. I relocked my bootloader and tried to flash the stock RUU, but since I had already gotten the update from Sprint the versions were different and it wouldn't go through. I couldn't find another RUU for the newest version, so I re-unlocked my bootloader and took off TWRP to replace it with CWM. At this point, I am able to get back into recovery. I thought I would try to sideload a stock ROM but adb can't seem to find my device. I keep getting the error "device not found". I updated drivers with the All-In-One Toolkit (which may not be up to date, but I can't find any other sources) and I uninstalled and reinstalled HTC Sync Manager. I also tried every USB port and even unplugging every USB except for the one connected to my phone.
Does anybody have any other suggestions for solutions? I've been browsing similar topics but I can't seem to find a method that makes my phone usable yet. Thank you for your time!
If I'm not mistaken,ARHD is a GSM Rom,it messed up your partitions,search for the thread on 4.2 downgrade and there's files you have to move
Sent from my HTCONE using xda premium
Oh, man. I am such a dolt. You're absolutely right. I'll see what I can find, thanks for pointing that out.
Ok here goes, I unlocked my phone flash viper ROM I remember it like yesterday then the new ota update came out flash the ruu to back to stock everything was fine updated the phone unlocked the phone both on win8 and win 7 but I can't flash a custom recovery, any tips are great
Sent from my GT-N8000 using xda app-developers app
Grab a copy of TWRP or CWM recoveries, links are available in original dev section. Put it in the same folder as ADB - which you used in the console/terminal/command line to unlock the phone. Fire up ADB in console, just as you did to unlock the phone, and type:
adb reboot-bootloader
Your phone should go to that white screen with colorful text. Next type:
fastboot flash recovery nameOfRecoveryImage.img
As long as you're unlocked, which you are, this should work flawlessly.
cant get phone to load
I tried to install the maximushd 12.1 on my sprint htc one. I tried to do it thru twrp recovery and now the phone only loads to boot loader. Any suggestions to get the phone back working. I was using viper rom at the time.
I'm going to assume maximushd is some rom for the international HTC One. I would highly recommend against flashing international roms for obvious reasons.
Either way, RUU the phone. If you're on the new firmware (1.31), you'll need to listen to this guy. Then download the 1.29 RUU from one of the dev sections, wherever the hell it is. Then everything will be back to how it was the day you bought it. Then, just do it all again but don't **** it up - ha.
edit: I just reread, you can't get to the recovery from the bootloader? If all you did was install an international rom, you should still be able to access recovery unless twrp has the ability to repartition, which I suppose it possible. I'll do some reading.
edit2: Others were able to fix the problem utilizing the method I outlined. One of them even links directly to the guide above. Should work alright.
sshede said:
I'm going to assume maximushd is some rom for the international HTC One. I would highly recommend against flashing international roms for obvious reasons.
Either way, RUU the phone. If you're on the new firmware (1.31), you'll need to listen to this guy. Then download the 1.29 RUU from one of the dev sections, wherever the hell it is. Then everything will be back to how it was the day you bought it. Then, just do it all again but don't **** it up - ha.
edit: I just reread, you can't get to the recovery from the bootloader? If all you did was install an international rom, you should still be able to access recovery unless twrp has the ability to repartition, which I suppose it possible. I'll do some reading.
edit2: Others were able to fix the problem utilizing the method I outlined. One of them even links directly to the guide above. Should work alright.
Click to expand...
Click to collapse
Thanks I will try not to screw it up this time
---------- Post added at 04:46 PM ---------- Previous post was at 04:31 PM ----------
sshede said:
I'm going to assume maximushd is some rom for the international HTC One. I would highly recommend against flashing international roms for obvious reasons.
Either way, RUU the phone. If you're on the new firmware (1.31), you'll need to [URL="http://forum.xda-developers.com/showthread.php?t=2390821"listen to this guy[/URL]. Then download the 1.29 RUU from one of the dev sections, wherever the hell it is. Then everything will be back to how it was the day you bought it. Then, just do it all again but don't **** it up - ha.
edit: I just reread, you can't get to the recovery from the bootloader? If all you did was install an international rom, you should still be able to access recovery unless twrp has the ability to repartition, which I suppose it possible. I'll do some reading.
edit2: Others were able to fix the problem utilizing the method I outlined. One of them even links directly to the guide above. Should work alright.
Click to expand...
Click to collapse
I cannot get into recovery. It just keeps going in a vicious cycle. I can choose fastboot or recovery but noting happens.
Did you try to flash a new one with fastboot? fastboot will work in the bootloader.
sshede said:
Did you try to flash a new one with fastboot? fastboot will work in the bootloader.
Click to expand...
Click to collapse
my computer won't recognize the phone as usb
I'll give a try when I can, thanks man
After I did ruu I still had s-off do you that make a big difference
Sent from my HTCONE using xda app-developers app
skevin101 said:
I tried to install the maximushd 12.1 on my sprint htc one. I tried to do it thru twrp recovery and now the phone only loads to boot loader. Any suggestions to get the phone back working. I was using viper rom at the time.
Click to expand...
Click to collapse
Just a quick pro-tip for you... if you didn't find the ROM in this forum (because you didn't) then DON'T FLASH IT!
If you found it in the international forums (which you did.) DON'T FLASH IT
Next time do a search because about a hundred other people who aren't good at reading before flashing have done it too.
felacio said:
Just a quick pro-tip for you... if you didn't find the ROM in this forum (because you didn't) then DON'T FLASH IT!
If you found it in the international forums (which you did.) DON'T FLASH IT
Next time do a search because about a hundred other people who aren't good at reading before flashing have done it too.
Click to expand...
Click to collapse
granted I didn't follow the instructions. that's what I get for thinking I know what im doing. just because ive flashed some before. but I didn't realize this was an international forum ( http://forum.xda-developers.com/forumdisplay.php?f=2115&nocache=1&z=3553232956118556)
sshede said:
Grab a copy of TWRP or CWM recoveries, links are available in original dev section. Put it in the same folder as ADB - which you used in the console/terminal/command line to unlock the phone. Fire up ADB in console, just as you did to unlock the phone, and type:
adb reboot-bootloader
Your phone should go to that white screen with colorful text. Next type:
fastboot flash recovery nameOfRecoveryImage.img
As long as you're unlocked, which you are, this should work flawlessly.
Click to expand...
Click to collapse
i uninstalled the drivers install them used different usb port, phone does say fastboot usb and shows up in fastboot devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
With the new 4.3 OTA I thought I might be good to delve into updating my phone today. That was around Noon, it's now 9PM, and I just don't know where else to turn. I know where I screwed up a few things and I feel like I've tried everything. Hopefully you guys will have some helpful suggestions, if not I guess I'll have to bite the bullet.
I'm a noob at rooting. I did root my HTC Evo Shift a year or two ago. Put CM 7.something on it, but I really wasn't happy with the performance so I just RUU'd back to stock and haven't messed with it since. I did leave it rooted for some root required apps though.
I rooted my HTC One a couple months ago using this method:
On gizmodo how-to-root-your-nexus-htc-one-or-samsung-galaxy-s4-990847878 (can't link it because I just signed up)
With 4.3 out I thought I would be able to find a modified update and keep my phone Stock rooted or try InsertCoin or something. My first mistake, I believe, was thinking that root was fine without S-Off.
I've got Drivers and Android SDK on my Win7 machine (I have a Mac and Fedora box if anyone knows any solutions using those OS's). I have on the phone TWRP 2.5.0.0, root, S-On. I try to upgrade to TWRP 2.6.0.0 and that doesn't work so well. I read somewhere that the M7WLS doesn't like that build, and I should try 2.6.0.1, I just strait to 2.6.3.0.
Read some articles on TWRP, watched some videos, so I go to do factory data wipe, cache wipe, dalvik cache wipe, and I do system wipe thinking I need to do that too. Whenever I reboot I basically stop at the HTC splash screen. Mistake number two, I have no OS now.
I hunt down a recovery.img from a site that is supposedly offical Sprint, flash it, try to do a factory restore, no good.
I try getting it back to stock with this:
How to Unroot / Unbrick the HTC One M7: Back to Stock by C4Etech
youtube.com C0G0hKY4P9Y
fastboot oem rebootRUU
fastboot flash zip <rom>.zip
I get errors whether locked or unlocked. I still have S-On and I'm guessing that's why I'm getting signature validation errors.
I try TWRP and ClockworkMod 6.0.4.3 to see if I can mount to my PC, no go.
Fastboot devices recognizes the M7WLS so after more reading I'm going to try ADB sideload. ADB devices does not see my phone. HT Sync is already installed, I remove it and try HTCDriver_4.2.0.001, no go. I remove it and try Universal_Naked_Driver_0.73, still nothing on adb devices. Whether TWRP or ClockworkMod Recovery I can't side seem to sideload.
I go to the store and pick up a cable:
Staples.com Belkin-4-Ports-USB-20-External-Flex-Hub product_IM1QZ5590 (Can't link)
Put
insertcoin-m7-4.0-4.zip AND
Guru_Reset_M7_Sprint_1.29.651.10.zip
on a USB stick, but the phone doesn't recognize it so I can load from either recovery.
I'm sure I've missed a few things in there. Right now I'm sunk, I'm tired, and suggestions are appreciated.
Try buy a USB to go and put a Rom on a Memory stick them using TWRecovery flash the Rom if you have any questions feel free to ask
Demo3827 said:
Try buy a USB to go and put a Rom on a Memory stick them using TWRecovery flash the Rom if you have any questions feel free to ask
Click to expand...
Click to collapse
Thanks for the input Demo. I actually connected it to OSX and the adb devices came right up so I was able to do a rom side load. Thanks again though.
your welcome
pwjohnston79 said:
Thanks for the input Demo. I actually connected it to OSX and the adb devices came right up so I was able to do a rom side load. Thanks again though.
Click to expand...
Click to collapse
your welcome =] anytime :good:
Hi everyone,
I'm hoping that someone can provide some assistance with my HTC One that won't load past the HTC One logo. I've never done any rooting or unlocking, the phone was stock when this happened. Last week the battery drained on me (not the first time it happened), I came home and put the phone to charge and when I tried to turn it on it wouldn't load past the HTC logo. I don't have any custom recovery on the phone. I am able to access the bootloader menu. I tried resetting the phone and wiping the cashe but that didn't help.
I downloaded ABD setup but would like some assistance before I try anything. I've been reading and "googling" a lot over the past week but it all seems a little over my head.
I'm a total noob when it comes to cell phones but I'm willing to learn.
Any help is greatly appreciated! Thanks in advance for your time.
xdabrainiak said:
Hi everyone,
I'm hoping that someone can provide some assistance with my HTC One that won't load past the HTC One logo. I've never done any rooting or unlocking, the phone was stock when this happened. Last week the battery drained on me (not the first time it happened), I came home and put the phone to charge and when I tried to turn it on it wouldn't load past the HTC logo. I don't have any custom recovery on the phone. I am able to access the bootloader menu. I tried resetting the phone and wiping the cashe but that didn't help.
I downloaded ABD setup but would like some assistance before I try anything. I've been reading and "googling" a lot over the past week but it all seems a little over my head.
I'm a total noob when it comes to cell phones but I'm willing to learn.
Any help is greatly appreciated! Thanks in advance for your time.
Click to expand...
Click to collapse
Honestly, if this is not a result of tampering, you might want to check into warranty. HTC Sync might have a recovery option, never used it, you could check there. Any solution I would have would void said warranty. It's not entirely uncommon for software to corrupt upon power loss.. rare indeed but it happens. See if you warranty is good have a new one in no time.
How about this ?
MrLizm said:
Honestly, if this is not a result of tampering, you might want to check into warranty. HTC Sync might have a recovery option, never used it, you could check there. Any solution I would have would void said warranty. It's not entirely uncommon for software to corrupt upon power loss.. rare indeed but it happens. See if you warranty is good have a new one in no time.
Click to expand...
Click to collapse
I have pretty much the same issue except the fact that mine was nit battery drained. It just crashed on some app and then device went to boot loop. Deleted the cache and factory reset thing. No luck.
Best bet is warranty get it replaced. Bloody so many devices going blank just like that !!! Htc should now make a statement on this!!
Else there is a long way , Some steps broadly.. if you on the latest android version and with a never tampered device.
Spend some time on this forum for each of those steps.
Unlock Bootloader (htcdev.com)[all data is gone] - Twrp recovery flash (2.7.1 recommended) -> Adb Sideload - Custom Rom (Android revolution 8.1 recommended)- If okay with custom rom stop here. And enjoy your device.
Else continuing ... Custom Rom -> Use firewater to do S-off --> RUU.exe of the latest Stock Build of your CID and MID (htc1) guru.com --> OTA updates to latest builds by HTC.
Notes :
1) RUU doing with S-on on a older version of android will leave you with bricked device.
2)Adb is needed to run the S-off firewater. So you need a working Android OS , thus the custom rom.
3)Once S-off , make sure you clear the tampered flag and relocked flag in bootloader. Just in case you need to visit the HTC service center later.
I want to the above as same situation. Stuck at the adb sideload step.
anirudhgargi said:
I have pretty much the same issue except the fact that mine was nit battery drained. It just crashed on some app and then device went to boot loop. Deleted the cache and factory reset thing. No luck.
Best bet is warranty get it replaced. Bloody so many devices going blank just like that !!! Htc should now make a statement on this!!
Else there is a long way , Some steps broadly.. if you on the latest android version and with a never tampered device.
Spend some time on this forum for each of those steps.
Unlock Bootloader (htcdev.com)[all data is gone] - Twrp recovery flash (2.7.1 recommended) -> Adb Sideload - Custom Rom (Android revolution 8.1 recommended)- If okay with custom rom stop here. And enjoy your device.
Else continuing ... Custom Rom -> Use firewater to do S-off --> RUU.exe of the latest Stock Build of your CID and MID (htc1) guru.com --> OTA updates to latest builds by HTC.
Notes :
1) RUU doing with S-on on a older version of android will leave you with bricked device.
2)Adb is needed to run the S-off firewater. So you need a working Android OS , thus the custom rom.
3)Once S-off , make sure you clear the tampered flag and relocked flag in bootloader. Just in case you need to visit the HTC service center later.
I want to the above as same situation. Stuck at the adb sideload step.
Click to expand...
Click to collapse
How exactly are you stuck at adb sideload?
assuming you have your custom rom, you would:
boot to recovery, select advanced then sideload...
from your pc you goto your ADB folder open cmd and type: adb sideload filename.zip
this pretty much sums it up
So I've been fiddling with the phone trying to fix it, looking at youtube videos and reading the forums but I'm still stuck. It's a Telus phone and it is not under warranty anymore... or it would have gone back already. I almost want to just give it back hahaha :laugh:
I managed to unlock to bootloader... that was pretty simple. The next thing I tried to do was do an adb sideload of twrp... it worked fine until I went into recovery mode and the phone was frozen there. I used an older version of twrp that was suggested 2.7.1 I believe. I noticed on the twrp website that in order to get it on your phone you need to be S-off.
How do I get some sort of custom recovery on my phone? It feels like whatever I do there is always some glitch or little thing that I failed to do.
xdabrainiak said:
So I've been fiddling with the phone trying to fix it, looking at youtube videos and reading the forums but I'm still stuck. It's a Telus phone and it is not under warranty anymore... or it would have gone back already. I almost want to just give it back hahaha :laugh:
I managed to unlock to bootloader... that was pretty simple. The next thing I tried to do was do an adb sideload of twrp... it worked fine until I went into recovery mode and the phone was frozen there. I used an older version of twrp that was suggested 2.7.1 I believe. I noticed on the twrp website that in order to get it on your phone you need to be S-off.
How do I get some sort of custom recovery on my phone? It feels like whatever I do there is always some glitch or little thing that I failed to do.
Click to expand...
Click to collapse
TWRP 2.7.1.1 is here, http://forum.xda-developers.com/showthread.php?t=2173870
Main advise is to follow steps, Do them no matter how trivial. Usually things go wrong for the littlest reason. You want to make sure you have the most current version of fastboot and adb tools on your computer when working with your HTC. Other good things to pay attention is use OEM cables and take note that you are plugged directly into a USB 2.0 on the board, not a port on the front of PC, a hub or extender..
xdabrainiak said:
So I've been fiddling with the phone trying to fix it, looking at youtube videos and reading the forums but I'm still stuck. It's a Telus phone and it is not under warranty anymore... or it would have gone back already. I almost want to just give it back hahaha :laugh:
I managed to unlock to bootloader... that was pretty simple. The next thing I tried to do was do an adb sideload of twrp... it worked fine until I went into recovery mode and the phone was frozen there. I used an older version of twrp that was suggested 2.7.1 I believe. I noticed on the twrp website that in order to get it on your phone you need to be S-off.
How do I get some sort of custom recovery on my phone? It feels like whatever I do there is always some glitch or little thing that I failed to do.
Click to expand...
Click to collapse
Download the latest version of TWRP for your phone
Place in your adb folder
Reboot to bootloader
Fastboot flash recovery "name_of_recovery".img
Fastboot erase cache
Reboot bootloader again and boot into recovery