Hello, I recently helped a fiend out with rooting his Desire 510 and all went well until recently when he decided to try and recover the phone to a previous state without root. He ended up deleting the OS off the phone and lost his backups aswell. Anyways, I've been trying to recover it for him but have had no luck; I have tried to flash a recovery .img file onto but I don't believe that will get the OS back, as it didn't seem to help. The next step I tried was locking the bootloader and then using HTC's EUU recovery software for the model but that failed to recognize the device. So any information and help is very much appreciated, and thanks in advance. ( I will also attach some shots of the phone in recovery mode).
cdeck17 said:
Hello, I recently helped a fiend out with rooting his Desire 510 and all went well until recently when he decided to try and recover the phone to a previous state without root. He ended up deleting the OS off the phone and lost his backups aswell. Anyways, I've been trying to recover it for him but have had no luck; I have tried to flash a recovery .img file onto but I don't believe that will get the OS back, as it didn't seem to help. The next step I tried was locking the bootloader and then using HTC's EUU recovery software for the model but that failed to recognize the device. So any information and help is very much appreciated, and thanks in advance. ( I will also attach some shots of the phone in recovery mode).
Click to expand...
Click to collapse
I wonder why the RUU did not work even though you locked the bootloader. I can't think of any other reason it would fail. I have used it when I deleted my OS and there was never any problem.
You're right, the recovery.img will not get the OS back unless you use TWRP.
You should unlock the bootloader, root, and flash TWRP. Then download, extract and install the backup from here.
Related
Hi there,
I have searched high & low on the interwebs for a possible solution to my problem but have yet to yield any significant results.
I was on 4.2.2 Stock, Rooted, with bulletproof, and I had started to get random reboots and then 4 nights ago during the night it decided to get into a reboot loop. It would power up for about 20 mins and then restart again & again so when I woke up it was super hot.
So I thought it was time to update it to 4.3 now in the hope that this would resolve the issue but it didn't. I obtained the relevant RUU (Guru Reset M7 2.24.980.2 for HTC__039) from htc1guru and since I was only wanting to get the OTA in the hope that this would fix any other software issues, I only flashed the recovery. I then proceeded to do the large OTA update. This was successful. Then the reboots started again.
Time for a factory reset now, (which I realise I should have just done in the first place) but after setting up my details in the phone I am unable to get network over 3G/4G and when I go into look at the APNs, it says that no sim card is installed when it definitely is. When I go into Phone Info, it states that my EMEI is 00000000.
After looking around for what feels like hours, I read somewhere that I might need to flash the radio but I only have the radio from the previous RUU(Guru Reset M7 2.24.980.2) or can I use that since I can not find anything around RUUs for 3.63.980.2.? I don't want to make the situation any worse than it already is.
I am hoping that there is a simple explanation and fix & any help or guidance would be much appreciated.
Thanks in advance :good:
So you think the problem is that your software is upgraded and not your firmware? If so, you can solve that by dowgrading your software. If you can't find an updated RUU (nothing except a signed file from HTC should be called a RUU), there is still a solution:
- Find a system dump from a phone that is your CID and the version of Android you want. It will be a CWM or TWRP backup.
- Flash the appropriate custom recovery.
- Push the files to your phone in the appropriate directory (you may need to make a backup just to see what the right directory is).
- Restore the backup you just pushed to your phone.
Then factory reset and install the stock recovery. You may need to re-lock the bootloader (I'm not sure). Try to get the correct OTA. If you can't find it, try to download one and save as /sdcard/update.zip. Use the stock recovery to flash it. (You'll need to search for instructions on how to do that. It involves key combinations.) Finally, unlock the bootloader, make a backup, and (optionally) root. Don't install a custom kernel. If your problem persists, you likely have a hardware problem.
Thanks for your reply.
I have no idea if its software/firmware but its showing its on 4.3. I was speculating on the radio possibly needing to be reflashed due to one comment I read on a forum I randomly came across?
So I could use my very first backup I used through TWRP and push that to the phone?
While I am fairly new to Android(had to switch for the HTC ONE), I have been around idevices for a long time and have learnt to always keep multiple backups just in case
I left the bootloader unlocked as most guides say that you don't need to have it locked to get the OTA. I actually tried to find the manual OTA file and do it the way you suggested but at the time I had no luck.
I'll see what I can accomplish tonight.
Apologies on the noobness in regards to RUU.
Is it possible to use a RUU for lets say T-Mobile on an international variant? I see HTC released an RUU for T-Mobile for 4.3 but as far as I can see there isn't any others.
[email protected] said:
So I could use my very first backup I used through TWRP and push that to the phone?
Click to expand...
Click to collapse
That's the first thing I'd try, yes. But I'm guessing just as much as you are.
fenstre said:
That's the first thing I'd try, yes. But I'm guessing just as much as you are.
Click to expand...
Click to collapse
Hahahaha Well I trust your guess way more then mine
Would I need s-off to copy the previous backup back onto the phone or would I only need s-off if I had to push something to system(which I do not need to do)?
I tried last night to run rumrunner and it continually failed and basically told me I had 2 different scenarios to resolve it(the following is coming from memory and its very hazy). One was to use a different kernel and the other was to use another ROM, but that wasn't the preferred option.
At work now so will try and restore my original backup tonight at home. Thanks for your help.
[email protected] said:
Would I need s-off to copy the previous backup back onto the phone or would I only need s-off if I had to push something to system(which I do not need to do)? .
Click to expand...
Click to collapse
Sorry for my late response. You only need s-off to flash firmware that is older, for a different phone CID, or modified by a third party. Or to change other hidden partitions, like to modify the "TAMPERED" flag or to change the CID. Unlocking the bootloader is for changing partitions from fastboot mode: recovery, and maybe also system and boot. You do not need an unlocked bootloader to change these partitions from recovery if you already have a custom recovery installed. (You can definitely modify system and boot, but I'm not sure about modifying recovery with a locked bootloader.)
fenstre said:
Sorry for my late response. You only need s-off to flash firmware that is older, for a different phone CID, or modified by a third party. Or to change other hidden partitions, like to modify the "TAMPERED" flag or to change the CID. Unlocking the bootloader is for changing partitions from fastboot mode: recovery, and maybe also system and boot. You do not need an unlocked bootloader to change these partitions from recovery if you already have a custom recovery installed. (You can definitely modify system and boot, but I'm not sure about modifying recovery with a locked bootloader.)
Click to expand...
Click to collapse
No need to apologise, I'm just happy that someone has been able to assist me.
I have used one of my previous TWRP backups, unfortunately I couldn't use my very very first one as it was missing some files, it obviously didn't copy it all across for some reason
I now have my EMEI back (woohoo) but I think the backup I used has something wrong in the kernel as I think it has bulletproof installed. I am going to return it to stock but following a procedure here as I need to return it to HTC as the phone will not read any sim cards. I have tried 3 different sim cards and have also tested them in a firends HTC ONE and they all work in his. SO it looks like I do have an actual hardware issue with the phone which isn't cool just before Xmas.
I already have major withdrawals from being able to play ingress :crying:
Thanks heaps for your help.
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
hey guys, Just trying to get my bearings on where to start. A friend game me a HTC Desire 510 that was not loading for him. Just sticking on the HTC loading screen.
He managed to "unlock" it. Not sure if it has root access.
In anycase it will not loal anymore, stuck on HTC load screen. I followed a few threads and tried to reset/restore things but now it looks like i need to just reinstall the OS.
Where I am lost is where/can i get the stock OS for this phone?
If not , do i need to get root access, load in a bootloader and then load in a custom ROM?
last time I did all this before was 2 years ago on a Samsung so I am a little rusty on the steps.
details
HTC Desire 510 - europe (Irish)
HBOOT - 3.19.0.0000
Radio 01.02.012
When I load up the bootloader I have "Sofrware status: Officaial *** at the tope and UNLOCKED under that.
Cheers
check the htc website for the latest rom(update) also this thread is sprint/virgin/boost
http://forum.xda-developers.com/desire-510/development/virgin-sprint-htc-desire-510-stock-t2961521
cricket stock rom: http://forum.xda-developers.com/desire-510/help/stock-rom-cricket-htc-desire-510-t3161697
id see if the htc site works first but thats just me.
hope i was of help to you with your issues if not wait for more experanced members to assist.
roymcd said:
hey guys, Just trying to get my bearings on where to start. A friend game me a HTC Desire 510 that was not loading for him. Just sticking on the HTC loading screen.
He managed to "unlock" it. Not sure if it has root access.
In anycase it will not loal anymore, stuck on HTC load screen. I followed a few threads and tried to reset/restore things but now it looks like i need to just reinstall the OS.
Where I am lost is where/can i get the stock OS for this phone?
If not , do i need to get root access, load in a bootloader and then load in a custom ROM?
last time I did all this before was 2 years ago on a Samsung so I am a little rusty on the steps.
details
HTC Desire 510 - europe (Irish)
HBOOT - 3.19.0.0000
Radio 01.02.012
When I load up the bootloader I have "Sofrware status: Officaial *** at the tope and UNLOCKED under that.
Cheers
Click to expand...
Click to collapse
Are you in Europe? If you are that's most likely a 64 bit phone and you'll need Philz Touch Recovery unless you have one installed. You'll also need to find a 64 bit stock HTC desire 510 rom.. It should work after installing them.
Edit: The HTC websites rom updater will not work since the phones boot is unlocked.. Just try what I said above.
Yes I am in Europe.
Will give what suggested a go and let you know..
cheers
here is your man for the job
ok mthis has happen to me before alright take the sdcard out reboot to fastboot relocok bootloader by typing 'fastboot oem relock' get the ruu for your phone then it will help you if you find this helpful hit the thank you button
bcbradley12 said:
ok mthis has happen to me before alright take the sdcard out reboot to fastboot relocok bootloader by typing 'fastboot oem relock' get the ruu for your phone then it will help you if you find this helpful hit the thank you button
Click to expand...
Click to collapse
It's actually fastboot oem lock
bcbradley12 said:
ok mthis has happen to me before alright take the sdcard out reboot to fastboot relocok bootloader by typing 'fastboot oem relock' get the ruu for your phone then it will help you if you find this helpful hit the thank you button
Click to expand...
Click to collapse
MrMike2182 said:
Are you in Europe? If you are that's most likely a 64 bit phone and you'll need Philz Touch Recovery unless you have one installed. You'll also need to find a 64 bit stock HTC desire 510 rom.. It should work after installing them.
Edit: The HTC websites rom updater will not work since the phones boot is unlocked.. Just try what I said above.
Click to expand...
Click to collapse
Ok guys , getting around to trying this now but running into some small problems.
Question 1
I have installed adb.exe and it does work with my main phone (HTC m8) but when i plug in the broken phone it does not pick up that phone (when i do a ">adb.exe devices") I saw some comments saying that I need to enable debug mode but how can I do that when i cannot even load the phone up ?
Question 2
I would like to install this Philz Touch Recovery , so i can installed the new RUU but I see on some sites that I need to install ClockworkMod first. Now I am not sure if this is needed or not but i still have the problem of being unable to install it from the bootloader screen. There is no option to install from zip? So this might sound like a real n00b question but how can install anything to my phone when all i have it the bootloader screen. My options when i boot up are . . .
Fastboot
-->HBOOT
-->RAMDUMP
-->REBOOT
-->REBOOT fastboot
-->power down
recovery
factory reset
simlock
check smartSD
image CRC show barcode.
Review. . .
I would think my issue is with the broken phones connecting to my laptop and the use of adb.exe. If I could get that working i can use adb.exe to installl clockworkmod and from that I can boot up the phone and install Philz Touch Recovery, and then using phils installer I can install the original 64bit Rom and be in business?
does that seem right?
Cheers
roymcd said:
Ok guys , getting around to trying this now but running into some small problems.
Question 1
I have installed adb.exe and it does work with my main phone (HTC m8) but when i plug in the broken phone it does not pick up that phone (when i do a ">adb.exe devices") I saw some comments saying that I need to enable debug mode but how can I do that when i cannot even load the phone up ?
Question 2
I would like to install this Philz Touch Recovery , so i can installed the new RUU but I see on some sites that I need to install ClockworkMod first. Now I am not sure if this is needed or not but i still have the problem of being unable to install it from the bootloader screen. There is no option to install from zip? So this might sound like a real n00b question but how can install anything to my phone when all i have it the bootloader screen. My options when i boot up are . . .
Fastboot
-->HBOOT
-->RAMDUMP
-->REBOOT
-->REBOOT fastboot
-->power down
recovery
factory reset
simlock
check smartSD
image CRC show barcode.
Review. . .
I would think my issue is with the broken phones connecting to my laptop and the use of adb.exe. If I could get that working i can use adb.exe to installl clockworkmod and from that I can boot up the phone and install Philz Touch Recovery, and then using phils installer I can install the original 64bit Rom and be in business?
does that seem right?
Cheers
Click to expand...
Click to collapse
Never mind if figured it out. .
roymcd said:
Never mind if figured it out. .
Click to expand...
Click to collapse
Nice to see you figured it out!
MrMike2182 said:
Nice to see you figured it out!
Click to expand...
Click to collapse
Well now that you say that. I am having a strange issue. The phone will boot but only when I select "recovery" mode from the bootloader?
I presume what I have done is flashed the wrong image to the wrong section. I think i need to to flash something to boot and not to recovery when I was running the "fastboot flash recovery image.img!"
ideas?
roymcd said:
Well now that you say that. I am having a strange issue. The phone will boot but only when I select "recovery" mode from the bootloader?
I presume what I have done is flashed the wrong image to the wrong section. I think i need to to flash something to boot and not to recovery when I was running the "fastboot flash recovery image.img!"
ideas?
Click to expand...
Click to collapse
I don't get what you're trying to do. If you wanna get back up and running, all you have to do is relock the bootloader and run the RUU... That's it. Your recovery doesn't matter. You don't need a custom recovery for that. Any custom recovery you have will be replaced by the stock one when you run the RUU.
I haven't been on this forum much lately, (so please correct me if I'm wrong, somebody) but from what I remember, the only custom recovery available for the 64-bit variant 510 is Philz. If that's the case then you shouldn't be flashing CWM
Surj138 said:
I don't get what you're trying to do. If you wanna get back up and running, all you have to do is relock the bootloader and run the RUU... That's it. Your recovery doesn't matter. You don't need a custom recovery for that. Any custom recovery you have will be replaced by the stock one when you run the RUU.
I haven't been on this forum much lately, (so please correct me if I'm wrong, somebody) but from what I remember, the only custom recovery available for the 64-bit variant 510 is Philz. If that's the case then you shouldn't be flashing CWM
Click to expand...
Click to collapse
Yes you seem to be correct . I locked the bootloader and then used the command "fastboot flash boot <htc_orginal_ruu>" and it started working again.
I had lots of issues trying to get the CWM installed . It was someone else on this thread that suggested that but I think that info was wrong.
And just to conform for others that may read this someday you do not need Phils recover if you want to get the original system running. if you want to install custom ROMs then you need it then.
Thanks for the input. Half the time its just good to write out your problem so you can understand.
roymcd said:
Yes you seem to be correct . I locked the bootloader and then used the command "fastboot flash boot <htc_orginal_ruu>" and it started working again.
I had lots of issues trying to get the CWM installed . It was someone else on this thread that suggested that but I think that info was wrong.
And just to conform for others that may read this someday you do not need Phils recover if you want to get the original system running. if you want to install custom ROMs then you need it then.
Thanks for the input. Half the time its just good to write out your problem so you can understand.
Click to expand...
Click to collapse
I did say you needed philz touch recovery if you have a 64 bit phone and you never really answered the 64 bit question and I asked because you said you are in Europe (Irish) and if you do have a 64 bit phone then you do need philz if you want to use other roms like the rest (most) of us on here do.
MrMike2182 said:
I did say you needed philz touch recovery if you have a 64 bit phone and you never really answered the 64 bit question and I asked because you said you are in Europe (Irish) and if you do have a 64 bit phone then you do need philz if you want to use other roms like the rest (most) of us on here do.
Click to expand...
Click to collapse
Yeah it was a 64bit phone.
I wanted the original OS back on the phone so that is why i did not need phils tool.
roymcd said:
Yeah it was a 64bit phone.
I wanted the original OS back on the phone so that is why i did not need phils tool.
Click to expand...
Click to collapse
I kinda figured all that out on my own already but why do you just want stock? Why don't you want a rooted phone so you can do a lot more with it?
---------- Post added at 05:46 AM ---------- Previous post was at 05:28 AM ----------
roymcd said:
Yes you seem to be correct . I locked the bootloader and then used the command "fastboot flash boot <htc_orginal_ruu>" and it started working again.
I had lots of issues trying to get the CWM installed . It was someone else on this thread that suggested that but I think that info was wrong.
And just to conform for others that may read this someday you do not need Phils recover if you want to get the original system running. if you want to install custom ROMs then you need it then.
Thanks for the input. Half the time its just good to write out your problem so you can understand.
Click to expand...
Click to collapse
I've read through this entire thread more than 3 times and I never once seen anyone in this thread tell you to run CWM(ClockWorkMod).. or to even use that so where did get that idea from... The only thing I suggested was Philz Touch Recovery as did @Surj138 for a good reason cause it's the only one that's 64 bit for your phone!
MrMike2182 said:
I kinda figured all that out on my own already but why do you just want stock? Why don't you want a rooted phone so you can do a lot more with it?
---------- Post added at 05:46 AM ---------- Previous post was at 05:28 AM ----------
I've read through this entire thread more than 3 times and I never once seen anyone in this thread tell you to run CWM(ClockWorkMod).. or to even use that so where did get that idea from... The only thing I suggested was Philz Touch Recovery as did @Surj138 for a good reason cause it's the only one that's 64 bit for your phone!
Click to expand...
Click to collapse
It was from other threads that I read to install Phils recovery I would need install CWM but I think now that is for other phones. I said it was in this thread by mistake.
As for going for the original ROM as opposed to a custom ROM my reasoning is three fold. . . .
1. This phone will not be staying with me. Will be giving it back to my friend who is giving it to his daughter. She is would have no use for a root phone.
2. The last time I was using custom ROM was with my Samsung S2 about 3 years ago. I did like all the extra features, free apps and full customization that you can do with it but I did find that no matter what custom ROM I found there would be little problems with each one. Performance would slowly drop the more i switched around the custom ROMS.
3. Custom ROMs are great and all but we cannot be 100% sure there is not hidden male-ware in some of them that is robbing my data. It was going to be a spare phone for playing games then i would not mind but to give to someone as there main phone is not the best option.
roymcd said:
It was from other threads that I read to install Phils recovery I would need install CWM but I think now that is for other phones. I said it was in this thread by mistake.
As for going for the original ROM as opposed to a custom ROM my reasoning is three fold. . . .
1. This phone will not be staying with me. Will be giving it back to my friend who is giving it to his daughter. She is would have no use for a root phone.
2. The last time I was using custom ROM was with my Samsung S2 about 3 years ago. I did like all the extra features, free apps and full customization that you can do with it but I did find that no matter what custom ROM I found there would be little problems with each one. Performance would slowly drop the more i switched around the custom ROMS.
3. Custom ROMs are great and all but we cannot be 100% sure there is not hidden male-ware in some of them that is robbing my data. It was going to be a spare phone for playing games then i would not mind but to give to someone as there main phone is not the best option.
Click to expand...
Click to collapse
Understood sir!!
Hello everyone. I don't know a whole lot about HTCs, but I want one badly after rooting one for a friend. I have another friend that tried to root a 626 verizon version on 6.0 with a tutorial on the HTC site for a different phone (he didn't ask me, I assure you and I gave him a scolding) and his recovery is broken. He's not sure if he fastbooted TWRP onto it or not but I think he may have without unlocking the bootloader. Is there possibly a stock recovery that he could fastboot back on there? His system is still booting and adb and fastboot are still connecting, I just don't know if there is a stock recovery for his and since it's not mine, I don't want to spend hours looking. Also, he doesn't have a lot of understanding yet as this was his first root attempt so I'm asking for him. Thanks so much for any help with this. Any Android down makes me sad. I told him if he wants to root get something non-verizon. He just ordered an unlocked S5 and I told him thats a very good place to start. But, if possible, I hope we can get his HTC right again. I also told him not to factory reset EVER if we can't get his recovery back. Thanks so much for any help.
Hello, haven't used this site in years but I'm hoping someone could help out. I believe my HTC One M9 (T-Mobile) is in a bad state and not sure if I'm going to be able to recover it.
Current Status: The phone only boots into the bootloader, attempting to goto recovery it states there isn't one. S-ON **Relocked**
What was done: I'm sure I screwed it all up by doing a 'fastboot oem lock', which was done from my understanding that the phone wouldn't be able get OTA updates unless it was. I assume that was the culprit as before that I had TWRP and a rooted OS. I've read through this thread here (https://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022) quite a bit. But I know I messed something up and now just looking for help getting it back.
I've tried an RUU(RUU_HIMA_UL_M60_SENSE70_TMUS_MR_TMOUS_3.39.531.7), but it said my battery was under 30% yet its over 80%, trying to charge and maybe try again. Also tried the 4.27.531.6 RUU, though Error132 (assuming that didn't work because of the firmware being a 3.x and not 4.x from my reading). Current OS says " 3.39.531.7 " in download mode. This is a longshot honestly. But I don't really have any other options, kinda need the phone and want to believe there's still hope in restoring it. I'm able to do fastboot commands. I'm just not sure what I can do because I'm not able to flash due to s-on, no recovery (that i know of, that happened after the fastboot oem lock command) i can get in to, no system to boot into. Almost tried using the Unlock_code.bin, but I wasn't even able to use the fastboot oem get_identifier_code (that failed as well) in order to generate another one from htcdev. So I'm at a loss here, I've spent hours and hour on reading and not getting anywhere. ANY help would be greatly appreciated. I can give any more info that would help to restoring, but again, I can ONLY access the bootloader screen/download mode...and that's about it Fingers crossed someone could assist/guide me in getting this thing running again.
Edit: Well I managed to get the bootloader unlocked again using the code from HTC (I found out I was on the wrong screen, was in the bootloader when I needed to be in Download mode for the get_identifier_code to work.) Now that's done, it rebooted and TWRP is still there and booted back into the system. I'm probably gonna say F*@# it to OTA updates unless someone could still help out with that. Have 2.8.6.4 TWRP installed. But as is, the phone is working again so that's good enough for now.
Hello all,
Sorry to bother u all. I tried to find answer myself by reading posts but couldnt find one . I have a HTC One-M9 phone with Bootloader Unlocked,S-OFF,Rooted and on Kitkat Sense 51 2.7.531.6. I found some bugs on my phone and i want to reflash with this https://androidfilehost.com/?fid=673368273298918830 which is exactly my version. If i flash with this using fastboot
(i) Will my unlocked bootloader will be locked/relocked
(ii) Will my S-OFF turns to S-ON. I dont want this to happen because i have to install a software which needs to modify kernel.
Right now I made a Nandroid Backup using TWRP. If anything goes wrong how to restore from nandroid. Please answer my questions and help me.
After a long a arduous journey, I've finally managed to get the phone updated to Nougat, back to root with the TWRP recovery. I was able to run the 3.xx RUU after removing HTC Sync and going to Device Manager and picking the HTC Driver from list. Made a backup after the fresh install of Nougat, but I figured I could run the 4.x RUU if I ever need to OTA again. But for now, I've got the phone updated as far as I can and back to root so I'm good. Mods feel free to delete this thread, apologies if it was in the wrong section. @bsskkd, sorry but I'm not too sure, maybe someone with more knowledge will be able to help out.