HTC M9 Help! No fastboot. Have had it rooted for a while - One (M9) Q&A, Help & Troubleshooting

Hi! I have been reading some write ups, but im not sure what to do.
I have a M9 Sprint version that has been unlocked for a while now, like a year, I downloaded an app this morning to delete sprint junk apps and deleted them. Well the app failed and when i reset the phone, the sprint apps just reinstalled. Shortly after, on my drive to work, I felt my phone vibrating, and noticed it was stuck in a reset loop.
I tried loading in fastboot, to re lock boot loaded and attempt to go back to stock image. I used TWRP to root it, and i have formatted my computer since then and dont have any of the associated files, including any backups.
My goal at this point is to return to a working phone, oem image or not, i really dont care. What do I need to do?
I downloaded the adb/fastboot tool to my pc, but no devices are being found, and fastboot is not an option when i go to the boot loader.
THANKS!

thehoss said:
Hi! I have been reading some write ups, but im not sure what to do.
I have a M9 Sprint version that has been unlocked for a while now, like a year, I downloaded an app this morning to delete sprint junk apps and deleted them. Well the app failed and when i reset the phone, the sprint apps just reinstalled. Shortly after, on my drive to work, I felt my phone vibrating, and noticed it was stuck in a reset loop.
I tried loading in fastboot, to re lock boot loaded and attempt to go back to stock image. I used TWRP to root it, and i have formatted my computer since then and dont have any of the associated files, including any backups.
My goal at this point is to return to a working phone, oem image or not, i really dont care. What do I need to do?
I downloaded the adb/fastboot tool to my pc, but no devices are being found, and fastboot is not an option when i go to the boot loader.
THANKS!
Click to expand...
Click to collapse
There is a dedicated thread for sprint versions, you would have better luck posting in there, but check out this thread.
https://forum.xda-developers.com/sp...print-htc-one-m9-1-32-651-17-t3073355/page106
You might want to use an ruu via SD card method.

Rogue apps.. A perfect example of why rooted phones aren't for laymen.
As long as you have download mode and the original cable the fastboot issue will be driver related. You might have to force the physical address into the drivers. Google that!. It's about a 6 on the pc illiteracy skill scale (piss, for short, thats what it makes you scream at the screen).
Beamed in by telepathy.

squ89r97 said:
There is a dedicated thread for sprint versions, you would have better luck posting in there, but check out this thread.
https://forum.xda-developers.com/sp...print-htc-one-m9-1-32-651-17-t3073355/page106
You might want to use an ruu via SD card method.
Click to expand...
Click to collapse
Thank you,
I dont use the forums much. I will check it out.

Related

[Q] Cyanogen 10.1 mod gone wrong.

AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.
chazbot7 said:
AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.
Click to expand...
Click to collapse
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
BWolf56 said:
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).
Click to expand...
Click to collapse
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
chazbot7 said:
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
Click to expand...
Click to collapse
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.
BWolf56 said:
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.
Click to expand...
Click to collapse
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?
chazbot7 said:
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?
Click to expand...
Click to collapse
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app
BWolf56 said:
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.
chazbot7 said:
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.
Click to expand...
Click to collapse
No need to apologize. Glad you got it back up! And it was mostly to keep you from making similar mistakes in the future
Sent from my SGH-I747 using xda app-developers app
also one thing you need to know
First boot after you flash will always take longer than normal. After that, it's fine

[Q] Bricked Phone...Peculiar Situation

Hey guys,
First off, I've searched far and wide for any help with my problem but it is such a peculiar situation that I have yet to find someone with a similar situation. I expect if I want to ever use my M8 again, I'll need to send it to HTC and pay a few hundred bucks to fix it. But maybe someone here will have an idea that I've missed.
Shortly after getting my M8, I unlocked my device, rooted it and installed a few roms. Everything was fine save for one major thing: no matter which PC I used (and I used MANY - 3 different windows destops, a windows desktop at the office and my Macbook Pro) the device was never able to mount and make the storage accessible. I knew at that point something at some point had gone wrong. I've long preferred to use a wireless file transfer app to send stuff to and from my phone so I wouldn't have to break out all my cables so I figured it wouldn't be a big deal. I'd make it work.
A few days ago, I decided to try a different rom than what I'd been using for months (HD Revolution - great rom!) and downloaded everything required. I booted to TWRP, wiped the usual stuff and flashed my rom. When I rebooted, I was continually met with a crash as soon as the phone started and was never able to get into the OS. No big deal - this has happened before with other devices, so I didn't sweat it. I simply powered down the phone and tried to get back to recovery. Here's where the problem really kicked in : when attempting to boot to recovery, my phone will bring up the Hboot screen but instantly try to select the first option, thus not allowing me to scroll down to "Recovery". No matter what I do, it brings up the white Hboot screen, automatically selects the first option, gives me some error (I'm at work so I don't have the device in front of me) and tries to boot to the OS. That takes us back to the automatic crash.
Now, I know usually the solution would involve USB and ADB, but like I mentioned at the start of my sad tale, connecting my phone to PC's results either in nothing (Mac) or a "the device has failed" message in Windows. I've tried removing all the phone drivers, reinstalling and using a few toolkit methods - the phone is just never ever detected.
So, that's it. I'm pretty much resigned to sending my phone in and the HTC folks quoted me about $200. I do have a functional phone at the moment so it isn't the worst situation in the world, but if I could fix this I'd be able to using it as my main device again or sell it for a good chunk of change - I just bought it in June.
Sorry for the long read!
As far as the storage issue, never seen that happen before so I'm not sure. When you plug it in to the computer does the phone ask if you want to connect it as a storage device etc?
The bootloader is a very peculiar problem. It almost sounds like you have an img file that its trying to read as soon as you boot into boot loader.
Try to install HTC sync. And make sure the computer has an internet connection when you plug it in via usb.
Try to flash stock recovery fw buddy
Maybe thats problem RUU
Cek mike blg to find all stock recovery fw
After that install custom recovery again
This sounds a little familiar.
In my experience I've found some firmware versions and ROMs very choppy.
I once had a problem with storage too, couldn't send anything over to my phone.
Fortunately I could access recovery, so used ADB sideload and installed another ROM. And went to another firmware and never looked back.
The last 401.6 firmware gave me all sorts of issue.
If you can access fastboot I'd also recommend new firmware 401.7 is working flawlessly for me with ARHD 21.
Sent from my HTC One_M8 using XDA Free mobile app
I would try putting one of the bootable ruus on your SD card so when it goes to your hboot, it'll read the RUU and install it
Awesome, some interesting suggestions here. Would I be able to somehow update the firmware via an SD card without any input from a computer? I managed to get into Recovery last night somehow (maybe letting the battery totally drain and charging it for a while did something) but plugging in my phone when in recovery still won't mount the storage or be recognized by ADB. Would I somehow be able update my firmware from recovery without the need of ADB'ing from my desktop? I've been looking at ROM threads and stuff and noticed that almost every rom requires new firmware or WiFI/radios other stuff won't work....
I'm at work right now so I'll definitely research this in depth when I get home, but if you guys could guide me in the right direction, I'd really appreciate it and maybe buy ya' a beer.
Xavierc123 said:
Awesome, some interesting suggestions here. Would I be able to somehow update the firmware via an SD card without any input from a computer? I managed to get into Recovery last night somehow (maybe letting the battery totally drain and charging it for a while did something) but plugging in my phone when in recovery still won't mount the storage or be recognized by ADB. Would I somehow be able update my firmware from recovery without the need of ADB'ing from my desktop? I've been looking at ROM threads and stuff and noticed that almost every rom requires new firmware or WiFI/radios other stuff won't work....
I'm at work right now so I'll definitely research this in depth when I get home, but if you guys could guide me in the right direction, I'd really appreciate it and maybe buy ya' a beer.
Click to expand...
Click to collapse
Download a rom that can use the 2.xx firmware. Look around and you should be able to find the roms. There's still plenty out there. Here's a little suggestion, reflash TWRP (or other recovery) through fastboot than grab a SD card and place the rom into the SD card and install the rom using through the use of a SD card. Just remember to do a full wipe before that

[Q] Help with downgrade and/or re-unlock, possible flash new OS

Hi, total noob to Android hacking and rooting here...
I'm in the US and have the HTC Desire 816 (710c) on Virgin Mobile. Really wishing I'd done better research about the Desire 816 and VM before buying this phone. It's a great phone except for the small HD. I didn't realize just how many headaches that small HD--and Virgin's tight-fisted grip regarding their unlock policy--would cause me!
Forgive the length of this, but I'm hoping more detail as to what I've done/tried will help find the right solution...
I was doing fine on KitKat and for some reason decided I wanted to upgrade to Lollipop--mistake number 1! I first installed the update over KitKat but had some issues. Nothing major, but I figured something was definitely wonky when I noticed the basic stock web browser was gone--not that I really use it, just wanted to test something with it. (I was having an issue in Habit Browser, didn't realize 'til later that it was because I had my download folder setting on external SD card. While that worked in KK, it didn't in LP.) So, I did a backup...or THOUGHT I did. HTC Backup app was supposed to have been backing up my phone every day to Drive...turns out, it wasn't, despite notifications that it was working. So, anyway... I went ahead and factory reset the phone and reinstalled Lollipop. UGH! An even bigger mistake. Over 6 GB of the HD gone, just from stock LP!
Then I thought maybe if I unlocked the phone, I could delete most of the junk, even still using the stock OS. I followed the directions on HTCDev and although the proper screen appeared on the phone and asked me if I wanted to unlock, and I replied yes, it didn't work at first. The phone rebooted and everything was the same. Reboot checker confirmed failure.
So, as I was ready to try to narrow down my list of previously installed apps to absolute essentials due to the reduced disk space, I thought to see if there was a a way to revert to KitKat. I followed the instructions here http://forum.xda-developers.com/desire-816/general/ruu-t2952058. I tried the RUU .exe first. It failed, telling me I needed to get the correct RUU and try again. However, HTC's website does NOT show any KK downloads for Virgin Mobile USA for this device. More on that in a moment...
I also tried the flashing via SD card method. It also failed. I thought, what the heck, I'll try steps 3 and 4 of the SD card method, flashing the stock recovery and lock the bootloader, even though I thought my device was locked. Well, I guess I didn't notice when I went into fastboot that the device indeed HAD at some point unlocked, after all.
After those steps, I now had the following show up:
*** Software Status: Modified ***
*** RELOCKED ***
SECURITY ALERT!
I tried flashing the ROM.zip from SD card method again. It failed spectacularly, saying something about about a large file (some of the text was beyond the edges of the screen, so I couldn't read all of it. There was also an instruction to press power to reboot. The phone went back into fast boot screen with red highlighted "!! Image Update FAIL !!" Mind you, this was with the SD card now removed. I did manage to get the phone to boot normally again, back to stock Lollipop.
Now I thought I would try flashing the WWE KK download from HTCDev. Well, I didn't get the large image fail message, but it did fail saying that it was not the right image.
I tried unlocking the phone again, via the instructions at HTCDev. Didn't work. Thought I would try the ROM.zip file from the thread here at XDA one more time. Same fail message as before, same behavior of phone getting stuck on flashboot screen with red error message on initial attempt to reboot the device. I do notice now that although phone status is still modified and relocked, the security alert message is gone.
Can anyone help? I just want KitKat back so I can reload all my previous apps! (or possibly a good KK equivalent non-stock ROM, once I get the phone unlocked again? I have no idea which one though, being a noob :/ )
Thanks!
witchywoman said:
So, as I was ready to try to narrow down my list of previously installed apps to absolute essentials due to the reduced disk space, I thought to see if there was a a way to revert to KitKat. I followed the instructions here http://forum.xda-developers.com/desire-816/general/ruu-t2952058. I tried the RUU .exe first. It failed, telling me I needed to get the correct RUU and try again. However, HTC's website does NOT show any KK downloads for Virgin Mobile USA for this device. More on that in a moment...
Click to expand...
Click to collapse
That ruu file should work it's the vm usa last kitkat version. You need to follow the directions unroot and relock phone. But depending on what you did to the phone that was non standard you might also need to wipe or format internal data before running the ruu.
I think you can:
1) unroot then boot into recovery(twrp)
2) wipe phone/format data.
3) Boot directly from twrp to bootloader so you can get to fastboot usb.
4) Flash stock recovery from your PC.
5) Relock bootloader then run the ruu.exe.
All the other stuff you did afterwards should not be necessary.
pcjunky: The phone is currently relocked. I'm not 100% sure about unrooted, but I think it is. Like I said, when it was unlocked before I didn't even realize it, and I didn't really do anything unusual with it. The phone still had stock Lollipop on it and I just changed some stock settings and preferences.
Also, as I said, I am a total noob. I don't know what you mean about twrp and booting into that to wipe the drive and then from that. I'm sure there is info about that on this site somewhere, but it might be quicker if you (or someone) could explain it briefly, or point me in the right direction.
Updating to answer my own question in this reply. You're telling me to use a custom recovery but I never installed one. So.... currently searching to see how to do that.
I don't know if it's worth you time to learn how to go back to Kitkat. There should be howto's in the general forum for most everything you need. But I think the free memory difference between Kitkat and Lollipop is almost 1GB. 4.04GB free versus 3.14GB free. If you make sure all your apps that support being moved to SD card are moved and your storage settings for supported items uses the SD card you might be able to save enough space to get by until you decide to switch phones.
Twrp is a custom recovery and backup/restore tool you can do a search to learn about it, but you might not need it. The HTC backup is OS specific and it only saves apps and data not system files. So your HTC backup under Kitkat won't restore over Lollipop. If you had installed Twrp and and made a backup of Kitkat before you installed Lollipop you could restore your kitkat backup over Lollipop.
If you still want to try to get back to kitkat you can try to reset your phone(In theory relocking your phone should do that but it wont hurt) before you run the ruu file.
pcjunky said:
I don't know if it's worth you time to learn how to go back to Kitkat. There should be howto's in the general forum for most everything you need. But I think the free memory difference between Kitkat and Lollipop is almost 1GB. 4.04GB free versus 3.14GB free.
Click to expand...
Click to collapse
Well, it's interesting to note that my phone used ~ 4.8 GB when it was new with KK installed. After the Lollipop upgrade, it was using well over 6 GB with just the stock OS, HTC apps and Virgin apps on it. Obviously, that was unacceptable, and it's what got me started on this whole quest. :silly: However, after flashing a custom recover image, rather than the stock recovery I used previously, the stock installation is using 4.97 GB, so I think I should be good to go with that.
If you make sure all your apps that support being moved to SD card are moved and your storage settings for supported items uses the SD card you might be able to save enough space to get by until you decide to switch phones.
Click to expand...
Click to collapse
I always have used the SD card as much as was supported. Switching phones is not an option for me as I have a rather limited income and the Desire was an investment. Thus another reason I embarked on trying to make these changes.
Twrp is a custom recovery and backup/restore tool you can do a search to learn about it, but you might not need it. The HTC backup is OS specific and it only saves apps and data not system files. So your HTC backup under Kitkat won't restore over Lollipop. If you had installed Twrp and and made a backup of Kitkat before you installed Lollipop you could restore your kitkat backup over Lollipop.
If you still want to try to get back to kitkat you can try to reset your phone(In theory relocking your phone should do that but it wont hurt) before you run the ruu file.
Click to expand...
Click to collapse
Well, as I said above, the stock/OME installation now, before uninstalling whatever junk it will let me, is using only 4.97 GB, so I should be fine with that.
Thanks for your efforts to help me out with this. :good:
I'm glad you got it to a workable point. It's possible to go back to Kitkat, but I personally wouldn't do it because it gives you better battery life.
From time to time you should check apps under settings and swipe left to see the apps on sd card. Sometimes new app updates will support being moved to sd card or an updated version of an app will need to be moved over to the sd card.

Phone has no OS and can't flash roms: SOLVED!

I picked up a sprint htc one m9 today. unfortunately no stock OS and no SD CARD with backup either. I booted into twrp but i can not do anything. everything fails. i tried to flash a rom and its a no go. I am stuck and have no idea what to try after looking for hours.
I have no OS
I can boot into twrp
twrp does not allow me to do anything FAILS on every operation.
zwp1990 said:
I picked up a sprint htc one m9 today. unfortunately no stock OS and no SD CARD with backup either. I booted into twrp but i can not do anything. everything fails. i tried to flash a rom and its a no go. I am stuck and have no idea what to try after looking for hours.
I have no OS
I can boot into twrp
twrp does not allow me to do anything FAILS on every operation.
Click to expand...
Click to collapse
Foremost: ugh. Sorry man - that sucks.
So it sounds like your best option would be to get an sd card and apply a RUU from there. Flippy498's Google Sheet is a great resource for where to get them and how to use them.
You might be able to use the Windows-executable RUU directly from Sprint. I'm pretty sure you'd need to be in download mode when you ran it though. It's not as straightforward as the sd card method, but they're usually my first fallback.
Keep in mind that both of these options are destructive - your phone will be brought to a factory state (stock firmware, recovery) and anything on the phone's internal memory will be wiped.
It might be worth exploring why TWRP keeps failing. If we could solve that, you could install the ROM of your choice and not worry about RUUs. But that's definitely more work and probably not necessary if you're not trying to save anything. Once the RUU has been successfully applied, you can just unlock the bootloader anew, install TWRP, and do whatever you want from there.
Thanks a ton that fixed it!
zwp1990 said:
Thanks a ton that fixed it!
Click to expand...
Click to collapse
Wonderful! Enjoy your new phone!
(If you're satisfied with the resolution, the convention in this forum is to mark a thread 'solved' in the title when an issue is resolved. This'll help folks know where to direct their help.)

Official RUU Restore to Stock FAILS Unbrick Using This Method

There is no effective RUU restoration that works once you follow the root, twrp, processes listed here on XDA. I've restored the original recovery.img, still no go. I've tried the full RUU available on HTC to no success. So be forewarned.
However, there is a way to recover your device. I'm no developer by any means, but this is the process which a kind user informed me of, so I'm sharing it at top level. See his comment below which is the true saving grace.
My 530 is a MetroPCS variant, so I went to the HTC site and downloaded RUU_A16_UL_M60_DESIRE_SENSE70GP_TMUS_TMOUS_1.01.531.25.exe
Then I used a RUU decryption tool, and extracted the files mentioned (boot.img) and (system.img).
I made sure TWRP worked on my handset still, which it did.
I put both files boot.img and system.img on the handset through the USB cable. I also copied the BETA-SuperSU-v2.74-2-20160519174328.zip to the same location.
Then I chose Install in TWRP, and chose "Image" instead of "Zip". It's a little box bottom right in TWRP on the Install screen.
First I installed the boot.img followed up by the system.img. I almost clicked reboot, and TWRP gave me this notice "Warning no Operating System installed." ---
...so I remembered the BETA-SuperSU-v2.74-2-20160519174328.zip file I copied over, and I went and installed it through TWRP.
I then rebooted the phone, and it rebooted a couple times, but then VOILA it was back to perfect, all data wiped of course, but fully rooted and ready to go.
Here is a link to the files I extracted using the RUU decryption tool. It is the T-Mobile variant, but works perfect for MetroPCS as well. https://drive.google.com/drive/folders/0B4K9JR5eVMSnWmtOMlV3Tkx1V2M?usp=sharing
Which carrier is your 530 from?
If you can boot in to TWRP you can install the system.img and boot.img from the install menu, press on install image once you are in the install menu, locate your system.img and choose the sytem partition boot for boot partition.
You can extract the system.img & boot.img using RUU decrypt tool
upperdecker said:
Which carrier is your 530 from?
If you can boot in to TWRP you can install the system.img and boot.img from the install menu, press on install image once you are in the install menu, locate your system.img and choose the sytem partition boot for boot partition.
You can extract the system.img & boot.img using RUU decrypt tool
Click to expand...
Click to collapse
Thanks, and MetroPCS. I'm going to try and decipher what you just typed and see if I can restore the handset, because it's stuck atm.
I flashed the exposed framework but my phone wasn't working right so I did twrp restore from a backup that I had previously used however now my phone is STUCK ON THE HTC logo screen.
I downloaded your files, followed your instruction and OMG! Thank You sooooo much I'm back to normal AND WITH SU. Thanks again!!
WARNING careful when messing with exposed framework its works but my phone had issues
Thanks grmiyce
Woooogh! That info was sooo helpful. I was able to restore my phone ( HTC Desire 530 - TMobile ) to normal behaviour after it was stuck at the HTC logo for 2 days. How did it get there?
Well , long story short, I installed TWRP , did not make a Nandroid backup, and installed super su v2.46. Then to help fix the problem I installed super su 2.74 , all from twrp, but that did not help the situation. I wiped all that could be wiped from TWRP but that did not help.
I tried to install my stock ROM but could not find it in a zip format so that was a failure. I was considering a custom ROM (and still am) but to this point I am uncertain as to what ROM I can use with minimal to Zero issues ( i don't wanna brick the phone). I'll gladly accept any suggestions.
Anyways I came across this info and it saved my life...I am so happy.
Also as i am back to square one, I still have to try to network unlock this phone, it is locked with TMobile device Unlock app. I have paid for an unlock service and i was told that it was good to go but i could not get the device unlock app to reach to the 'permanent unlock' screen so i can unlock the phone. And that is why i was trying to root to uninstall the app and reinstall it since it was a system preinstalled app.
Btu anyways , I'll have to figure that out, at least the phone is back up now..
Thanks.
grniyce said:
There is no effective RUU restoration that works once you follow the root, twrp, processes listed here on XDA. I've restored the original recovery.img, still no go. I've tried the full RUU available on HTC to no success. So be forewarned.
However, there is a way to recover your device. I'm no developer by any means, but this is the process which a kind user informed me of, so I'm sharing it at top level. See his comment below which is the true saving grace.
My 530 is a MetroPCS variant, so I went to the HTC site and downloaded RUU_A16_UL_M60_DESIRE_SENSE70GP_TMUS_TMOUS_1.01.531.25.exe
Then I used a RUU decryption tool, and extracted the files mentioned (boot.img) and (system.img).
I made sure TWRP worked on my handset still, which it did.
I put both files boot.img and system.img on the handset through the USB cable. I also copied the BETA-SuperSU-v2.74-2-20160519174328.zip to the same location.
Then I chose Install in TWRP, and chose "Image" instead of "Zip". It's a little box bottom right in TWRP on the Install screen.
First I installed the boot.img followed up by the system.img. I almost clicked reboot, and TWRP gave me this notice "Warning no Operating System installed." ---
...so I remembered the BETA-SuperSU-v2.74-2-20160519174328.zip file I copied over, and I went and installed it through TWRP.
I then rebooted the phone, and it rebooted a couple times, but then VOILA it was back to perfect, all data wiped of course, but fully rooted and ready to go.
Here is a link to the files I extracted using the RUU decryption tool. It is the T-Mobile variant, but works perfect for MetroPCS as well. https://drive.google.com/drive/folders/0B4K9JR5eVMSnWmtOMlV3Tkx1V2M?usp=sharing
Click to expand...
Click to collapse
it work on htc desire 530 OR not?
So did anyone end up figuring out how to unroot this phone? Have to send it in for a warranty repair, and need to restore it back to stock settings but only seem to find horror stories like OP's, when it comes to actually trying to do it. Normally I never end up having to unroot a phone, so didn't bother seeing if it was possible ahead of time. Hopefully someone knows how to do this.
m3gapxl said:
So did anyone end up figuring out how to unroot this phone? Have to send it in for a warranty repair, and need to restore it back to stock settings but only seem to find horror stories like OP's, when it comes to actually trying to do it. Normally I never end up having to unroot a phone, so didn't bother seeing if it was possible ahead of time. Hopefully someone knows how to do this.
Click to expand...
Click to collapse
First dsclaimer you find in almost every rooting thread is:
Your Warranty is now VOID
So, it is the risk you just took when decided to root your phone...
sorry mate
yurais said:
First dsclaimer you find in almost every rooting thread is:
Your Warranty is now VOID
So, it is the risk you just took when decided to root your phone...
sorry mate
Click to expand...
Click to collapse
Yeah, I've seen that disclaimer multiple times. However, the warranty portion of my post is non-consequential and unrelated to my real question: *has anyone found a way to unroot the phone successfully, yet?* HTC explicitly states on their website that unlocking the boot-loader doesn't void your warranty, in and of itself. Only damage that occurs as a result of said rooting (e.g: hard-bricking your phone by installing the incorrect ROM or over-clocking the CPU).
That being said, (according to articles like these: motherboard.vice.com/en_us/article/jailbreaking-iphone-rooting-android-does-not-void-warranty) they wouldn't be able to deny me service, even if they wanted to. Not that you asked, but my phone has a manufacturer defect (faulty usb port) and is increasingly becoming more unstable; the root had nothing to do with it.
Thanks for the heads up, I'm simply looking for help in the other matter. I'll keep it in mind when contacting them.
HTC Desire 530 (Canada - Freedom Mobile) Bricked(?)
Hey guys,
I successfully unlocked my bootloader, installed twrp, installed supersu and obtained my root. This being the first time i've really ever used an android phone, I forgot to make a backup at this point, and I moved ahead. First thing I tried doing was uninstalling some of the default HTC apps. I downloaded app remover - started uninstalling, seemed to work fine, deleted a bunch of the files out of the recycle bin and my phone reset and since then will not load past the HTC boot screen. I let it sit over night and nothing changed, I've tried this method, i've tried the RUU files on the htc website. I'm pretty sure I need to flash a custom ROM or find an official rom at this point (Which seems near impossible). I know it's my fault for not backing up, and this phone isn't my main phone or anything, but it's totally driving me nuts at this point that I can't fix it. Anyone have any suggestions?
From the download mode screen :
hTC download mode
*** UNLOCKED ***
htc_a16ul PVT S-ON
LK-1.0.0.000
RADIO-01.01_U113251341_59.01.60624G
OpenDSP-UNKNOWN
OS-1.01.1500.31
JUN 28 2016,11:30:13 (773773)
TWRP is still installed and working fine, and I am able to copy things to my phone still.
However it is saying:
NO OS INSTALLED in there somewhere.
Any help would be appreciated.
chiassoo said:
Hey guys,
I successfully unlocked my bootloader, installed twrp, installed supersu and obtained my root. This being the first time i've really ever used an android phone, I forgot to make a backup at this point, and I moved ahead. First thing I tried doing was uninstalling some of the default HTC apps. I downloaded app remover - started uninstalling, seemed to work fine, deleted a bunch of the files out of the recycle bin and my phone reset and since then will not load past the HTC boot screen. I let it sit over night and nothing changed, I've tried this method, i've tried the RUU files on the htc website. I'm pretty sure I need to flash a custom ROM or find an official rom at this point (Which seems near impossible). I know it's my fault for not backing up, and this phone isn't my main phone or anything, but it's totally driving me nuts at this point that I can't fix it. Anyone have any suggestions?
From the download mode screen :
hTC download mode
*** UNLOCKED ***
htc_a16ul PVT S-ON
LK-1.0.0.000
RADIO-01.01_U113251341_59.01.60624G
OpenDSP-UNKNOWN
OS-1.01.1500.31
JUN 28 2016,11:30:13 (773773)
TWRP is still installed and working fine, and I am able to copy things to my phone still.
However it is saying:
NO OS INSTALLED in there somewhere.
Any help would be appreciated.
Click to expand...
Click to collapse
Awesome job my man saved me from a brick last night flashed boot system then supersu and all rooted and we'll[emoji41] [emoji12]
Sent from my HTC 2PST2 using XDA-Developers Legacy app
I can confirm that the decryption tool works for update 1.36.1550.5 on the MertoPCS version
http://www.htc.com/us/support/htc-desire-530-metro-pcs/news/
RUU_A16_UL_M60_DESIRE_SENSE70GP_TMUS_MetroPCS_US_1.36.1550.5_Radio_01.01_U113251531_68.01.61229G_release_495720_signed_2.exe
*edit* it still get a notification about an update
guess ill just use htc's method
I can not install a rom on my htc desire 530 because the android version I have is 1.01.619.1 and the one on the htc page is 1.01.617.25.
help
RUU from HTC says phone wrong model, TWRP says right model, update fails!
I'm getting an update available notice on my HTC Desire 530 from MetroPCS. It says that "Software update: 1.36.1550.14 (66.88 MB) This update contains critical security updates and system enhancements to improve overall device performance."
I'm currently on 1.36.1550.5 so I tell it to Install now. It downloads, reboots into recovery, which is TWRP 3.0.2, and when I look at the log, it failed.
"This package is for "htc_a16ul" devices; this is a "a16".
M60QCT.02.003.021
E:unknown command [set_err_msg]
This package is for "htc_a16ul" devices; this is a "a16""
When I am in download mode, it says it is htc_a16ul.
So, I tried downloading the update from HTC on my computer. I grabbed this file:
RUU_A16_UL_M60_DESIRE_SENSE70GP_TMUS_MetroPCS_US_1.36.1550.14.exe
It fails basically with the same error.
How can I flash the update?
Boot into download mode and then run the .exe update
Worked great. Thanks Bennyoo

Categories

Resources