I seriously hate this phone, everyone says it's the easiest to root, but I just can't seem to get this **** to work! Well first, I unlocked the phone, then went onto rooting it...Well that never worked, so then I tried installing a ClockWorkMod Recovery and everytime I tried to enter Recovery, it always brought me to a white screen with words in the red " This Build is for development purposes only Do not distribute outside of the HTC without HTC's written permission. Failure to comply may lead to legal actions. "
But my phone still worked, just no root or recovery. So I decided to install a custom kernal, well I did that and now my phone, I'm assuming, is in a semi-brick mode. So I can't start it to work, but I can access Bootloader. But I have serously tried everything! I even tried unbricking it and relocking it with this tutorial: http://forum.xda-developers.com/showthread.php?t=1674226
Nothing works, and this is starting to get aggravating.
I have rooted many phones, and this one is by far the worst.
More detail please, PrimoU or PrimoC ?
ckpv5 said:
More detail please, PrimoU or PrimoC ?
Click to expand...
Click to collapse
It's a PrimoC and it's unlocked. Virgin Mobile
For PrimoC, make sure you use the right superboot to root it. The situation that you desccribed is showing that you use the wrong superboot.
Same for recovery, you need the correct recovery for PrimoC
See : http://forum.xda-developers.com/showthread.php?t=1749798 or http://forum.xda-developers.com/showthread.php?t=1764183
Same goes for the kernel (boot.img), only use the one meant for PrimoC.
Related
Hello i have the tc one x and i have alot of problems. when i first bought the phone i rooted it and i was happy. i downloaded root apps and i was set. then i wanted to start flashing roms. so i downloaded a custom rom on my computer, followed all the instructions carefully and it did not work. i had installed clockworkmod and the whole 9 yards.When i would try to boot into recovery mode i would get a security warning and i was not allowed to. i tried many tutorials to install it on to my phone using my computer and command prompt and things like that but that did not work. So i came to the conclusion that i did not unlock my bootloader. so i went through the whole process on htcdev.com and my key was invalid. i had gotten the error 160 and mid not allowed. now i wanted to completely restore and unroot so i deleted superuser and the su files and did the whole thing with fastboot files and command prompt using a video to help me through it. When i was done my phone still said tampred on the bootloader and i got the same security warning error when i tried to restore the phone. so i cannot restore my phone to stock. now my phone cannot recieve att updates and when i try to manually update it is says htcdm has stopped and then after the button does nothing. and many apps stop unexspectedly and i am very upset about this. i have tried unrooting and unlocking bootloader at least 10 times now and nothing works!! PLEASE HELP!!! i really dont want do have to sell my phone and save up for a new one. thank you.
ewokiscool said:
Hello i have the tc one x and i have alot of problems. when i first bought the phone i rooted it and i was happy. i downloaded root apps and i was set. then i wanted to start flashing roms. so i downloaded a custom rom on my computer, followed all the instructions carefully and it did not work. i had installed clockworkmod and the whole 9 yards.When i would try to boot into recovery mode i would get a security warning and i was not allowed to. i tried many tutorials to install it on to my phone using my computer and command prompt and things like that but that did not work. So i came to the conclusion that i did not unlock my bootloader. so i went through the whole process on htcdev.com and my key was invalid. i had gotten the error 160 and mid not allowed. now i wanted to completely restore and unroot so i deleted superuser and the su files and did the whole thing with fastboot files and command prompt using a video to help me through it. When i was done my phone still said tampred on the bootloader and i got the same security warning error when i tried to restore the phone. so i cannot restore my phone to stock. now my phone cannot recieve att updates and when i try to manually update it is says htcdm has stopped and then after the button does nothing. and many apps stop unexspectedly and i am very upset about this. i have tried unrooting and unlocking bootloader at least 10 times now and nothing works!! PLEASE HELP!!! i really dont want do have to sell my phone and save up for a new one. thank you.
Click to expand...
Click to collapse
Yup.
First, your not clear with what you actually did.
IS your Phone the AT&T version? If YES, then this is the wrong forum.
Also all you need to do to get a custom ROM running is this.. (in the respective order ) -
1- Unlock using HTC. Your error is probably because you did not clearly read on how to copy the UID part. even one extra character here or there can generate an invalid key.
Follow the instructions to the letter.
2- Flash ClockWorkMod Recovery using fastboot.
3- Before flashing the ROM, from CWM, make a backup of the stock ROM, by going to Backup and Restore - Backup.
4- Wipe Date/Factory reset option in the recovery. Then Goto Mounts section and format /system.
5- Now flash your ROM from the sdcard.
6- PROFIT?
If you are not confident enough to follow each and every instruction to the letter, then flashing custom ROM's is not for you.
From your post i can clearly see that you find the whole process a little too cumbersome. I can be wrong. But please at least be clear what you exactly did. Which ROM did you try to flash? And how did you go back to stock? Which RUU did you use? Was it the correct one?
If your HBOOT says ***LOCKED*** or ***RELOCKED*** then run an RUU and it will remove all warnings, and put your phone back to it's factory state.
how do you run an ruu
Rusty! said:
If your HBOOT says ***LOCKED*** or ***RELOCKED*** then run an RUU and it will remove all warnings, and put your phone back to it's factory state.
Click to expand...
Click to collapse
how do you run an ruu?
Boot into bootloader then go into fastboot and run the ruu that's all but sure thing before doing this u have to flash the stock recovery and kernel and lock bootloader
Y U WANNA KNOW FROM WHERE SENT??
Just download one and run it, dead easy.
But he has to return the recovery and kernel and lock bootloader first
Y U WANNA KNOW FROM WHERE SENT??
His post is so disjointed it's impossible to figure out the state of his bootloader (hence mentioning it), but you don't need to replace kernel and recovery, that's the point of the RUU.
Rusty! said:
His post is so disjointed it's impossible to figure out the state of his bootloader (hence mentioning it), but you don't need to replace kernel and recovery, that's the point of the RUU.
Click to expand...
Click to collapse
ok i am in boot loader
it says
***Tampered***
***locked***
when i go into fastboot there is no RUU selection
and when i press recovery or factory reset it says legal **** then brings me back to boot loader and says
***Tampered***
***locked***
security warning
ewokiscool said:
ok i am in boot loader
it says
***Tampered***
***locked***
when i go into fastboot there is no RUU selection
and when i press recovery or factory reset it says legal **** then brings me back to boot loader and says
***Tampered***
***locked***
security warning
Click to expand...
Click to collapse
Then you haven't unlocked it properly.
Sent from my fauxed HOX running ParanoidAndroid JB
ewokiscool said:
ok i am in boot loader
it says
***Tampered***
***locked***
when i go into fastboot there is no RUU selection
and when i press recovery or factory reset it says legal **** then brings me back to boot loader and says
***Tampered***
***locked***
security warning
Click to expand...
Click to collapse
OK that means you're good to go with the RUU if you want to return to stock and have everything working again.
Dude becareful if its saying security warning then your battery is very low,becareful because if the phone drains completely while using ruu the phone would get hard bricked also u can't select ruu you just have to go into fastboot
Y U WANNA KNOW FROM WHERE SENT??
Ok. Stop.
Where did you get your phone? Is it quad or dual core? What is the model number written on the case?
Before you do more damage, let's figure out what device you have, which forum you need to ask questions in, and what procedures you need to follow.
Defo sounds like an XL to me
Sent from my HTC One X using xda premium
Given AT&T updates were mentioned in the OP, that's a given
EddyOS said:
Defo sounds like an XL to me
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Agreed. Not seen tampered on the intl x. Would also explain everything else not working.
M.
Sent from my HTC One X using xda premium
BenPope said:
Ok. Stop.
Where did you get your phone? Is it quad or dual core? What is the model number written on the case?
Before you do more damage, let's figure out what device you have, which forum you need to ask questions in, and what procedures you need to follow.
Click to expand...
Click to collapse
i have the usa version dual core
i bought it from radio shack
on the box it has a proof of purchase and says Model: Htc One X
imei: 359691041968911
sku:65383
Rusty! said:
If your HBOOT says ***LOCKED*** or ***RELOCKED*** then run an RUU and it will remove all warnings, and put your phone back to it's factory state.
Click to expand...
Click to collapse
ok i downloaded the RUU now what do i do to run it on my phone?
ewokiscool said:
i have the usa version dual core
i bought it from radio shack
on the box it has a proof of purchase and says Model: Htc One X
imei: 359691041968911
sku:65383
Click to expand...
Click to collapse
Right, well, I'm not sure what you've done to it, but this is the wrong sub forum.
If it is an AT&T phone, htcdev won't work.
Best bet is to visit the ONE XL forum. And post what you problems you have, and then what you tried to do before arriving where you are now.
Word of advice, your first post in this thread was awful. It's too long, too confusing and unreadable. Try to cut out as much as you can. I don't care how many yards, that you got instructions from a video, and that the video was hosted on YouTube. Just list what you did to the phone. Use spaces (including vertical spaces), punctuation and bullet points to good effect. End of the day, you want as wide an audience as possible.
Good luck.
So I decided to root my android desire hd phone and avail the benefits of blackout ics rom on my phone.
This is how I approached.
I unlocked the bootloader from HTC Dev.
I have the adb with me, adb devices, adb restart bootloader are working absolutely fine and cell phone was detectable.
I downloaded the aahk and blackout rom from xda forums.
But I am not able to use the aahk properly. It says in instruction to do a fastboot flash boot boot.img from command prompt with the source being the place where aahk is placed on the PC. But it still doesn't work, and probably this is the root cause of the issues I am facing.
I tried downloading the CWM to boot into recovery, but that also gave me an error stating cannot find the adbwinapi.dll file.
So after that, I did a factory reset of my cellphone and truly I got my first success and I was able to get into the bootloader and recovery.
I can reach to the bootloader screen (white screen+3 andro dummies), but when I select the fastboot option It says cannot find image(which image, is it referring to boot.img). I deleted the cache on my cell phone, but again things are pending from here on.
The description on this screen says S-ON and some other things. Does that mean the security is still on?
I have the rom loaded on the sd card with renamed to update.zip, but when I select update option from the recovery it again says cannot find image, rebooting!(what image this is referring to).
And after all this sequence I am down with a cellphone now degraded to froyo from ginger bread and back to stone age!
Please advise.
TH3_M0Nk said:
So I decided to root my android desire hd phone and avail the benefits of blackout ics rom on my phone.
This is how I approached.
I unlocked the bootloader from HTC Dev.
I have the adb with me, adb devices, adb restart bootloader are working absolutely fine and cell phone was detectable.
I downloaded the aahk and blackout rom from xda forums.
But I am not able to use the aahk properly. It says in instruction to do a fastboot flash boot boot.img from command prompt with the source being the place where aahk is placed on the PC. But it still doesn't work, and probably this is the root cause of the issues I am facing.
I tried downloading the CWM to boot into recovery, but that also gave me an error stating cannot find the adbwinapi.dll file.
So after that, I did a factory reset of my cellphone and truly I got my first success and I was able to get into the bootloader and recovery.
I can reach to the bootloader screen (white screen+3 andro dummies), but when I select the fastboot option It says cannot find image(which image, is it referring to boot.img). I deleted the cache on my cell phone, but again things are pending from here on.
The description on this screen says S-ON and some other things. Does that mean the security is still on?
I have the rom loaded on the sd card with renamed to update.zip, but when I select update option from the recovery it again says cannot find image, rebooting!(what image this is referring to).
And after all this sequence I am down with a cellphone now degraded to froyo from ginger bread and back to stone age!
Please advise.
Click to expand...
Click to collapse
You have not done anything fine...anything at all. My advice is that you'd better start reading hard buddy or you will end up with a 300 bucks paperweight.
Use the guide in my signature to start.
Tip 1:If you really downgrade to froyo and you were running gingerbread, you might have messed the bootloader..can you boot in hboot in normal times or takes ages?
Tip 2:The Hack Kit can not be run with an unlocked bootloader...that is what the manual says. The manual is there just to avoid this.
If your bootloader is still unlocked, then you have to install CWM recovery, put the rom in the sdcard (no rename is necessary) and then flash the boot.img from where that file is located (I usually put in the PC desktop) and not from the Hack Kit folder.
Then, from CWM flash the rom normally and you will be up and running.
Unlocking the bootloader will not give you S-OFF....
glevitan said:
You have not done anything fine...anything at all. My advice is that you'd better start reading hard buddy or you will end up with a 300 bucks paperweight.
Use the guide in my signature to start.
Tip 1:If you really downgrade to froyo and you were running gingerbread, you might have messed the bootloader..can you boot in hboot in normal times or takes ages?
Tip 2:The Hack Kit can not be run with an unlocked bootloader...that is what the manual says. The manual is there just to avoid this.
If your bootloader is still unlocked, then you have to install CWM recovery, put the rom in the sdcard (no rename is necessary) and then flash the boot.img from where that file is located (I usually put in the PC desktop) and not from the Hack Kit folder.
Then, from CWM flash the rom normally and you will be up and running.
Unlocking the bootloader will not give you S-OFF....
Click to expand...
Click to collapse
I had this tutorial open side by side in your signature while I was doing it. (the noob one)
I can go into Hboot normal times.
I am writing it down here from the main website from where I downloaded the aahk. And it says
Unlock the bootloader using the HTC DEV bootloader unlock process.
Download att-ace-30-isboot.zip and unzip it (don’t forget to check MD5)
fastboot flash boot boot.img
relock bootloader
But just now you told me that it should not be run on an unlocked bootloader! I am a little confused.
TH3_M0Nk said:
I had this tutorial open side by side in your signature while I was doing it. (the noob one)
I can go into Hboot normal times.
I am writing it down here from the main website from where I downloaded the aahk. And it says
Unlock the bootloader using the HTC DEV bootloader unlock process.
Download att-ace-30-isboot.zip and unzip it (don’t forget to check MD5)
fastboot flash boot boot.img
relock bootloader
But just now you told me that it should not be run on an unlocked bootloader! I am a little confused.
Click to expand...
Click to collapse
Yeah, but also says this: "...No Temproot for Inspire Build 3.20.502.52..." But you have a Desire HD, haven't you? And your build is not that one, is it?
glevitan said:
Yeah, but also says this: "...No Temproot for Inspire Build 3.20.502.52..." But you have a Desire HD, haven't you? And your build is not that one, is it?
Click to expand...
Click to collapse
Yeah.
I think i found the answers I was looking for and since I used the bugger HTC dev unlocker (which I shouldn't have used), I have to come down a step and start over again.
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
This made me realize deep down search is more important. Thanks
TH3_M0Nk said:
Yeah.
I think i found the answers I was looking for and since I used the bugger HTC dev unlocker (which I shouldn't have used), I have to come down a step and start over again.
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
This made me realize deep down search is more important. Thanks
Click to expand...
Click to collapse
No problem. Get a working phone and then you can try to run the Hack Kit...but it has to be stock or otherwise will not work. :good:
glevitan said:
No problem. Get a working phone and then you can try to run the Hack Kit...but it has to be stock or otherwise will not work. :good:
Click to expand...
Click to collapse
I am not sure if you are on right now, but i am giving a try to the steps mentioned by that gentlemen above in the link.
the phone is now stuck at signature verification. I reasearched for it but could not find a viable solution or an exploit that can overcome it(though everyone seems to be suggesting to install CWM recovery)
Not taking any chances to convert my phone into a brick! Whats the best way.
TH3_M0Nk said:
I am not sure if you are on right now, but i am giving a try to the steps mentioned by that gentlemen above in the link.
the phone is now stuck at signature verification. I reasearched for it but could not find a viable solution or an exploit that can overcome it(though everyone seems to be suggesting to install CWM recovery)
Not taking any chances to convert my phone into a brick! Whats the best way.
Click to expand...
Click to collapse
ok, Have you managed to unlock the bootloader? if you are already unlocked, do you mind if I have a look at it over teamviewer?
glevitan said:
ok, Have you managed to unlock the bootloader? if you are already unlocked, do you mind if I have a look at it over teamviewer?
Click to expand...
Click to collapse
I am following the steps sequentially as mentioned in that link by sashank. The bootloader is partially unlocked due to the HTCDEV process.
Couple of other things that I noticed. The android version is still at 2.3.5 however the device was shipped with Froyo. My mistake to have said that it is downgraded to froyo when I did the factory reset.
The facebook for HTC Sense thing is jacked up big time, I cannot find that in peoples app.
The device has (believe me) gained speed. pretty strange.
Once I reach home 3 hours from now, i'll update this thread and we can connect through Teamviewer so that you can have a look.hope thats cool!
Thanks
TH3_M0Nk said:
I am following the steps sequentially as mentioned in that link by sashank. The bootloader is partially unlocked due to the HTCDEV process.
Couple of other things that I noticed. The android version is still at 2.3.5 however the device was shipped with Froyo. My mistake to have said that it is downgraded to froyo when I did the factory reset.
The facebook for HTC Sense thing is jacked up big time, I cannot find that in peoples app.
The device has (believe me) gained speed. pretty strange.
Once I reach home 3 hours from now, i'll update this thread and we can connect through Teamviewer so that you can have a look.hope thats cool!
Thanks
Click to expand...
Click to collapse
Ok, just let me know when you are online and be arrange it.
glevitan said:
Ok, just let me know when you are online and be arrange it.
Click to expand...
Click to collapse
Yes I am online now. Let me know how to proceed.
TH3_M0Nk said:
Yes I am online now. Let me know how to proceed.
Click to expand...
Click to collapse
download the teamviewer: http://www.teamviewer.com
Get the ID and PASS and send them over a Private Message, NOT HERE
Ok so I believe I bricked my phone. Currently all it does is boot to the HTC quietly brilliant screen, blink, then HTC quietly brilliant over and over forever. I am able to enter the Hboot no problem, but Recovery and Factory Reset don't help the problem.
Just so you know what I've done:
1) Started with the intention of rooting: Which now seems impossible due to me updating to the 2012 system update released before I realized it makes all the rooting instruction impossible to do.
2) I was able to UNLOCK the Hboot but the program that you normally run before hand would not work, so I did it all manually and successfully.
Current Hboot info is:
***UNLOCKED***
MarvelC PVT SHIP S-ON RL
HBOOT 1.10.0001
Microp-0354
Radio-0.94.00.0109
Apr 17 2012, 18:21:30 - I'm assuming this is the line that ruined rooting for me.
3) Tried and read every single program/walkthrough out there nothing works at all.
4) Today I tried using Hasoon2000's HTC Wildfire All in one kit.
5) Attempted to flash the recovery - thought it worked
6) As I knew about the system update mentioned above Apr17, 2012 I attempted to Flash the kernal with the boot rom inside the "RUU_Marvel_Virgin_Mobile_1.37.351.1_Radio_47.10.3 5.3029H_7.46.35.08_release_188032_signed". It went through and said everything worked perfectly. Upon restarting my phone is now stuck on the perpetual loop mentioned above and useless.
7) Booting into Hboot and attempting Flash does nothing as everything is still blocked it seems by that damm patch. Rooting using this program did not work either. I attempted to root from the Hboot USB promt (it was my only choice after the Brick)
Any assistance or ideas or leads really anything would be nice. I hope I supplied enough details.
[the omeessco
At what point of "rooting" were you at.. and which method were you using to "root"
the 2012 update made no difference to my NON marvel C handset when rooting via the official HTCdev method.
I'm not sure what you did... clockwork mod recovery installed?
I have abused my HTC & in the last 2 weeks has had about 10 diff rooms on it... I'm finding it hard to brick.. only soft brick
Glitch_Neo said:
At what point of "rooting" were you at.. and which method were you using to "root"
the 2012 update made no difference to my NON marvel C handset when rooting via the official HTCdev method.
I'm not sure what you did... clockwork mod recovery installed?
I have abused my HTC & in the last 2 weeks has had about 10 diff rooms on it... I'm finding it hard to brick.. only soft brick
Click to expand...
Click to collapse
I've been abusing it as well, this is the first time I've run into issue, but then again this is the first time I used this program and tried to see if I could roll back that system update with the KERNEL flash. That's the point at which all hell broke loose.
Drakons said:
I've been abusing it as well, this is the first time I've run into issue, but then again this is the first time I used this program and tried to see if I could roll back that system update with the KERNEL flash. That's the point at which all hell broke loose.
Click to expand...
Click to collapse
Really I'm not going to get any help at all? The Phone can't be Rooted so it's not rooted, just Unlocked HBoot as mentioned. It's in a constant Boot Loop.
Drakons said:
Really I'm not going to get any help at all? The Phone can't be Rooted so it's not rooted, just Unlocked HBoot as mentioned. It's in a constant Boot Loop.
Click to expand...
Click to collapse
Well I was able to get the phone to reboot by Fastboot flashing after extracting the rom.zip from the
RUU_Marvel_Virgin_Mobile_1.37.351.1_Radio_47.10.35.3029H_7.46.35.08_release_188032_signed
file, but the userdata, radio and recovery portions would not pass the Signatures portion.
So I'm unable to connect with my Wifi or The Phones network. Any ideas from here?
Sounds like a boot lopped have you tried flashing any roms?
Sent from my Wildfire S A510e using xda app-developers app
hmmm Im a newbie... let me research.. lol
Drakons said:
Really I'm not going to get any help at all? The Phone can't be Rooted so it's not rooted, just Unlocked HBoot as mentioned. It's in a constant Boot Loop.
Click to expand...
Click to collapse
LOL hey sorry my phone died and I was at work all last night.
You say its just in a perpetual boot loop... I had this with a "dodgy rom" install when I first started messing around. I managed to fix the issue with a complete wipe of SD card - formatted in the PC - then dalvic cach, cache etc... some "paid for" versions of App2sd etc that are patched or cracked also give loads of probs.
Stupic question, have you formatted / cleaned all aspects of mem card and phone acsessable files using the HBOOT.
When mine did it I just installed a fresh rom (cyanogen mod 10.1) and it worked again. without the reovery / install from SD isnt there I'm stumped.... noobie strikes... sorry
I'll have a read though... see what I can come up with.
I see from the Kernal You tried was for a MARVEL not MARVELC.... im sure the two should never be mixed up or bricking will happen
i'll get back to you later if i find anything out mate.
---------- Post added at 02:03 PM ---------- Previous post was at 01:59 PM ----------
WiseCrunchyEggroll said:
Sounds like a boot lopped have you tried flashing any roms?
Sent from my Wildfire S A510e using xda app-developers app
Click to expand...
Click to collapse
From reading the tread properly, it seems a flash of the MARVEL Kernal onto a MARVELC phone is where the propblem lies.. Im pretty sure you should never mix the two... I could be wrong though - my wife tells me I often am! lol
good luck Drakons:good:
your best bet at this point is to flash a custom rom that is already rooted. you have the custom recovery already installed so just flash the rom. (whichever you like) for future reference the marvelc can be s-offed by placing the pj76diag.nbh onto the sdcard and booting to bootloader, allowing it to run and then selecting clean s58 data. once you have s-off you can supercid and then run any ruu that you want, should you ever get stuck in situations like this. where as the htcdev unlock blocks the use of ruu`s and pj76img.zips from bootloader
Drakons said:
Ok so I believe I bricked my phone. Currently all it does is boot to the HTC quietly brilliant screen, blink, then HTC quietly brilliant over and over forever. I am able to enter the Hboot no problem, but Recovery and Factory Reset don't help the problem.
Just so you know what I've done:
1) Started with the intention of rooting: Which now seems impossible due to me updating to the 2012 system update released before I realized it makes all the rooting instruction impossible to do.
2) I was able to UNLOCK the Hboot but the program that you normally run before hand would not work, so I did it all manually and successfully.
Current Hboot info is:
***UNLOCKED***
MarvelC PVT SHIP S-ON RL
HBOOT 1.10.0001
Microp-0354
Radio-0.94.00.0109
Apr 17 2012, 18:21:30 - I'm assuming this is the line that ruined rooting for me.
3) Tried and read every single program/walkthrough out there nothing works at all.
4) Today I tried using Hasoon2000's HTC Wildfire All in one kit.
5) Attempted to flash the recovery - thought it worked
6) As I knew about the system update mentioned above Apr17, 2012 I attempted to Flash the kernal with the boot rom inside the "RUU_Marvel_Virgin_Mobile_1.37.351.1_Radio_47.10.3 5.3029H_7.46.35.08_release_188032_signed". It went through and said everything worked perfectly. Upon restarting my phone is now stuck on the perpetual loop mentioned above and useless.
7) Booting into Hboot and attempting Flash does nothing as everything is still blocked it seems by that damm patch. Rooting using this program did not work either. I attempted to root from the Hboot USB promt (it was my only choice after the Brick)
Any assistance or ideas or leads really anything would be nice. I hope I supplied enough details.
Click to expand...
Click to collapse
I think you should change thread title to solved as you have solved tour problem...
Sent from my Wildfire S using Tapatalk 2
Hello,
My HTC Desire HD gets stuck on the HTC screen when I try to boot it.
I am kinda new to this, so I should not have done what I did. I got this phone used and I rooted it, and tried to install a custom ROM.
And something went wrong, likely I didn't prepeard the phone the right way.. And of course, I have been serching a lot on the web, some things don't work and other this requires tools that have a bad download link or outdated.
So my question is: How do I make my phone like normal? Like unrooting and removing everything if possible..
Would be so great if someone could help me out or just by linking me to a working tutorial.
Thank you and have a nice day. And please, ask if something is unclear or if you have questions.
I have a very similar issue
trakku said:
Hello,
My HTC Desire HD gets stuck on the HTC screen when I try to boot it.
I am kinda new to this, so I should not have done what I did. I got this phone used and I rooted it, and tried to install a custom ROM.
And something went wrong, likely I didn't prepeard the phone the right way.. And of course, I have been serching a lot on the web, some things don't work and other this requires tools that have a bad download link or outdated.
So my question is: How do I make my phone like normal? Like unrooting and removing everything if possible..
Would be so great if someone could help me out or just by linking me to a working tutorial.
Thank you and have a nice day. And please, ask if something is unclear or if you have questions.
Click to expand...
Click to collapse
Hi, I have done a similar thing, in that in an attempt to flash a custom ROM, I removed everything. Now, all ROMs just produce the HTC splash screen.
Please help as this is my only phone !!!
You both need to provide more detail on what state your phone was in to begin with and what you did to it. I have a hunch that your phones are S-On with unlocked bootloaders, and that neither of you flashed the boot.img from fastboot after flashing the ROM from recovery. But more detail on what you have and what you did is necessary.
bananagranola said:
You both need to provide more detail on what state your phone was in to begin with and what you did to it. I have a hunch that your phones are S-On with unlocked bootloaders, and that neither of you flashed the boot.img from fastboot after flashing the ROM from recovery. But more detail on what you have and what you did is necessary.
Click to expand...
Click to collapse
Yes, you are right. I just flashed the boot.img with fastboot AFTER installing from recovery. Jellytime booted up. I really have to thank you for that.
And again, you are right. The phone is S-Om and bootloader unlocked.
I used a a tool named "EasyUnlockTool". It rooted, unlocked the bootloader and some other things.
But right now, I think I am going to stick to jellytime. But to help caraar12345 and me later if I want to go back to stock room, what kind of information do you need?
Thank you for helping
You can either flash a rooted stock-like ROM from recovery, in which case you'd be mostly stock, or relock your bootloader and run a RUU from your computer in fastboot, in which case you'd be completely stock.
Check here:
http://bit.ly/186aMrl
Okay I'm really getting sick of this thing. I've totally no idea what I've done but after 2 hours of trying, I'm back to the same thing. Finally managed to get the proper USB drivers for my computer so the phone and the computer could talk to each other.
I've followed this guide on how to unroot the phone:
http://theunlockr.com/2014/07/15/how-to-unroot-the-htc-desire-816/
First, when I relock the bootloader, I still got ***Tampered*** and ***Security Warning*** although it says relocked. I couldnt boot into the OS. Can't do anything at all. Unlocking it again solves the problem.
Secondly, I wasn't able to get to S-Off mode. Anyone can shine some light on this? I'm really stuck here. I can't flash the stock RUU.zip as it says signature failed.
Would be glad that someone could assist me on this... I really need to get rid of the phone as soon as possible as I'm sick of this thing.
And, BTW, mine is the single SIM with LTE version.
Thank you.
Is yours the a5_chl or the a5_ul? The a5_chl is the one on VM.
did you flash the correct stock recovery to replace your custom recovery before you re-locked it?
also, there is no S-off for this model yet so don't waste time looking for it
edit
FoxyDrew said:
Is yours the a5_chl or the a5_ul? The a5_chl is the one on VM.
Click to expand...
Click to collapse
a5_ul.
Where can I get the files for a5_ul?
seekfind said:
did you flash the correct stock recovery to replace your custom recovery before you re-locked it?
also, there is no S-off for this model yet so don't waste time looking for it
Click to expand...
Click to collapse
I couldn't find the proper stock recovery.
But I thought S-Off needs to be off before everything else can be done?
No need for S-off to unlock/relock bootloader or flash custom/stock recovery/ROM. none of us here have S-off and yet we all use custom delights provided by XDA devs
this will probably help you with the stock recovery, tho I'm not sure if it works for single SIM or not:
http://forum.xda-developers.com/desire-816/help/how-to-install-stock-recovery-img-t2937667
This may seem like an amateur question, but how do you tell if your phone is a5_chl or a5_ul?
jamiedenton said:
This may seem like an amateur question, but how do you tell if your phone is a5_chl or a5_ul?
Click to expand...
Click to collapse
you restart your phone to bootloader.
1. Disable fastboot. Settings>Battery>uncheck fastboot.
2. Power off
3. Press and hold Volume Down and power
it's written in there