Related
I hope I am not posting where I am not supposed to, but I desperately need help. I am a noob and have managed to brick my inspire, or at least that's my guess. I can still get in to hboot, but when I select recovery, nothing happens. This all started after trying to use the htc boot unlocker. My screen shows the following when in hboot
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MIROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Dec 22 2011,14:28:19
I have tried loading the stock images using the PD98IMG.zip files that I have found throughout the site, but nothing seems to be working. Please help, or if you can point me to someone that can I would greatly appreciate it. I hate to be a pain, but I don't know what else to do.
dalton42503 said:
I hope I am not posting where I am not supposed to, but I desperately need help. I am a noob and have managed to brick my inspire, or at least that's my guess. I can still get in to hboot, but when I select recovery, nothing happens. This all started after trying to use the htc boot unlocker. My screen shows the following when in hboot
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MIROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Dec 22 2011,14:28:19
I have tried loading the stock images using the PD98IMG.zip files that I have found throughout the site, but nothing seems to be working. Please help, or if you can point me to someone that can I would greatly appreciate it. I hate to be a pain, but I don't know what else to do.
Click to expand...
Click to collapse
YOUR PHONE IS NOT BRICKED. The term bricked means that your phone is a useful as a brick, i.e. if you can get into HBOOT, it's not bricked.
Gotta ask though, why did you not use the Hack Kit as its the only reliable method to root, my advice to you sir is when this gets cleared up READ AND EDUCATE YOURSELF before you really do brick your phone.
If you have a SDcard reader, pop out the SDcard and place one of the PD98IMG stock ROMs on your SDcard. From here you can reboot into HBOOT with the sdcard in your phone and HBOOT should pick up the PD98IMG and flash a working stock ROM. From here, you can root with the Hack Kit...
This will help you, read it and do what the stock ROM option...if you can get into HBOOT
I have tried doing that, it says loading image, then parsing, then goes back to the hboot screen, it doesn't say press volume up to update or anything else as I have read in many other posts. Am I doing something wrong? As far as not using the hack kit, I didn't really stumble on that until after it was to late, sure wish I had found it in the first place. Guess if I could just get it back to factory, I would accept that doing this isn't for me and not mess with it again. I am good at following directions, but nothing I have tried seems to work.
dalton42503 said:
I have tried doing that, it says loading image, then parsing, then goes back to the hboot screen, it doesn't say press volume up to update or anything else as I have read in many other posts. Am I doing something wrong? As far as not using the hack kit, I didn't really stumble on that until after it was to late, sure wish I had found it in the first place. Guess if I could just get it back to factory, I would accept that doing this isn't for me and not mess with it again. I am good at following directions, but nothing I have tried seems to work.
Click to expand...
Click to collapse
is the file named exactly "PD98IMG.zip"..you may also want to check the hide extension option to be sure its not hiding the .zip because if it is and you renamed it to "PD98IMG.zip" with the hide extension on, the phone will read it as "PD98IMG.zip.zip" and you would get that error.
haha and yeah man, we've all been there...I don't want to discourage you man, rooting is such an awesome experience and the hack kit is a pretty straight forward process, if you do the research and take the time to understand what you're doing, but lets see if we can help you out here first. I had the same issue you're having when I tried to flash a radio (same PD98IMG method you're trying to use) and it turned out to be the hide extension issue.
I had also verified that as well, I went under tools, folder options, view tab, scrolled down to hide extensions for known file types and unchecked... And, everything was correct, just verified to be on the safe side.
dalton42503 said:
I had also verified that as well, I went under tools, folder options, view tab, scrolled down to hide extensions for known file types and unchecked... And, everything was correct, just verified to be on the safe side.
Click to expand...
Click to collapse
hmm, so its named PD98IMG.zip caps and everything? If its not working you m ay have to get a stock RUU and run it through fastboot..
This is why you should educate yourself first. You do not need to unlock the bootloader from the HTC dev site. Now you could flash the the stock ruu from the PC and then use the hack kit. Check the stickies in the Inspire general section for more help.
Sent from my HTC Inspire 4G using Tapatalk
I understand that I should have been a little more educated first now, but I thought I had everything in order, thats what thinking gets me... I have tried running the stock ruu, but it gives the following error.
ERROR[155]: UNKNOWN ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
I did notice the Image version the program shows is on the phone is 3.13.0.0, and it is trying to put 2.47.502.7 on the phone... Is this the problem? If so, whats the solution, I am so lost now its not even funny.... I apologize everyone.
dalton42503 said:
I understand that I should have been a little more educated first now, but I thought I had everything in order, thats what thinking gets me... I have tried running the stock ruu, but it gives the following error.
ERROR[155]: UNKNOWN ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
I did notice the Image version the program shows is on the phone is 3.13.0.0, and it is trying to put 2.47.502.7 on the phone... Is this the problem? If so, whats the solution, I am so lost now its not even funny.... I apologize everyone.
Click to expand...
Click to collapse
Dalton, lock your bootloader again. Boot into fastboot and plug the phone. You will see fastboot usb at the top. Then plug your phone and open cmd session. Once there type fastboot oem relock. Once that is done, try flashing the .exe file in the HTC site (original GB update), making sure that you have HTC Sync installed.
If that fails, then I would try using the HACK Kit to gain S-OFF and root. You will then be able to revert to stock or flash a custom rom...
Had a similar problem when using aahk my own fault and I took care of it. Long winded, so short of it, are you trying to install through
1. hboot or 2. on the computer using HTC rom update?
I ended up trying 2. But ended up using aahk to finish.
HTC update errored out and the recovery portion would not work, just in a boot loop on HTC logo
This was good news as aahk could take over on USB during that HTC green letters white background.
I'd suggest reading the effen manual run the tool to get it up and going, figure out what you want to do. I've used it to return to stock with s off before go back into roms.
So look at those options know what you want and then power on the phone USB connected and during HTC screen enter your number the kit should take over and give you what you asked it.
That should give you a working rom image.
--will'm
Sent from my Inspire 4G using XDA Premium HD app
willm98G97B said:
Had a similar problem when using aahk my own fault and I took care of it. Long winded, so short of it, are you trying to install through
1. hboot or 2. on the computer using HTC rom update?
I ended up trying 2. But ended up using aahk to finish.
HTC update errored out and the recovery portion would not work, just in a boot loop on HTC logo
This was good news as aahk could take over on USB during that HTC green letters white background.
I'd suggest reading the effen manual run the tool to get it up and going, figure out what you want to do. I've used it to return to stock with s off before go back into roms.
So look at those options know what you want and then power on the phone USB connected and during HTC screen enter your number the kit should take over and give you what you asked it.
That should give you a working rom image.
--will'm
Sent from my Inspire 4G using XDA Premium HD app
Click to expand...
Click to collapse
He won´t be able to use the Kit if the bootloader is unlocked. HE MUST RELOCK Bootloader...then run the Kit...It´s worth mentioning that...
True, never ran htc s unlock option.
Sent from my Inspire 4G using XDA Premium HD app
Thanks A MILLION!!!
Thank you all for your time, finally got it working again, with stock firmware. Think I may wait a while before messing with this again. I really do appreciate the help, without you all, I would have a nice expensive paper weight....
dalton42503 said:
Thank you all for your time, finally got it working again, with stock firmware. Think I may wait a while before messing with this again. I really do appreciate the help, without you all, I would have a nice expensive paper weight....
Click to expand...
Click to collapse
Glad you have it back....yeah you'd better read and make sure what are about to do it and of course what risks are involved before making a move....
Dalton,
I would suggest following glevitan's and willm's assertion of getting s-off and root to use custom roms. Custom roms are WAY better than anything HTC has to offer, and much easier to install, if you have an issue warranty wise, you can always return to stock. Just make sure you know how to flash correctly, search for it and you will find easy instructions, and if memory serves, a youtube video which helped me greatly.
dalton42503 said:
Thank you all for your time, finally got it working again, with stock firmware. Think I may wait a while before messing with this again. I really do appreciate the help, without you all, I would have a nice expensive paper weight....
Click to expand...
Click to collapse
Can you tell me the which firmware or send me a link.I have a same problem
If you are using AT&T branded cell then go to the htc.com site and in the support section of the inspire you will find it. Otherwise, you will find stock roms in the general section of this forum
Sent from my Inspire 4G using XDA
glevitan said:
If you are using AT&T branded cell then go to the htc.com site and in the support section of the inspire you will find it. Otherwise, you will find stock roms in the general section of this forum
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
I am having a bootloader error with stock ro.(error 140)
How can i fix it
ydnbngl said:
I am having a bootloader error with stock ro.(error 140)
How can i fix it
Click to expand...
Click to collapse
if you have unlocked the bootloader then relock it...then run it again.
glevitan said:
if you have unlocked the bootloader then relock it...then run it again.
Click to expand...
Click to collapse
It is relocked and ship s-on
I had ended up using the all in one HTC One S root utility that was linked in the fourms. After following all the steps that where listed (While following the youtube guide) My phone when on bootloader will show ****Unlocked**** across the top but s=off any ideas on why that is? I havent quite been able to figure it out im just looking for more information so when I get home I can have at it again :/ just find it odd that given the steps and the fact I had done them all to the T im still having this issue. Any help would be great thanks for taking the time.
I assume this might be better fit for Q&A if your a mod i apologize if you could move it that would be great couldnt figure out how to delete the poist :/ "edit/delete" wont remove the post :/ sorry again
Well if you can post a photo of the boot loader screen that would help me in sorting out your issue.
Sent from my MIUI powered one s
If I helped you in any way please hit thanks!
Taco991 said:
Well if you can post a photo of the boot loader screen that would help me in sorting out your issue.
Sent from my MIUI powered one s
If I helped you in any way please hit thanks!
Click to expand...
Click to collapse
No worries I would be more than happy to provide one after I get home from work
smO[pdx] said:
I had ended up using the all in one HTC One S root utility that was linked in the fourms. After following all the steps that where listed (While following the youtube guide) My phone when on bootloader will show ****Unlocked**** across the top but s=off any ideas on why that is? I havent quite been able to figure it out im just looking for more information so when I get home I can have at it again :/ just find it odd that given the steps and the fact I had done them all to the T im still having this issue. Any help would be great thanks for taking the time.
I assume this might be better fit for Q&A if your a mod i apologize if you could move it that would be great couldnt figure out how to delete the poist :/ "edit/delete" wont remove the post :/ sorry again
Click to expand...
Click to collapse
Don't know what you are disappointed about. S-OFF stands for security being off. This may sound bad, but from a developer perspective, it's pretty good. If you have true S-OFF like you claim you do, you can flash ROMs, kernels, radios, etc... in a recovery with no issues at all; regardless of what hboot or custom recovery you have. Unlocked means that you can flash custom recoveries and such using fastboot, which is what you want. To sum it up, S-OFF is good; many devs are trying to get S-OFF, but NONE can figure it out. Just be happy about it.
Having this 'Unlocked' text is what you're going to get if you root/unlock the phone. No way to get around it. If you want to return to complete stock settings and re-lock, your best bet is to be on stock recovery and flash an RUU that corresponds to your network. You may also want to try 'fastboot oem lock'.
Closed Source Project said:
Having this 'Unlocked' text is what you're going to get if you root/unlock the phone. No way to get around it. If you want to return to complete stock settings and re-lock, your best bet is to be on stock recovery and flash an RUU that corresponds to your network. You may also want to try 'fastboot oem lock'.
Click to expand...
Click to collapse
Actually I think since he has s-off I think he can make it say whatever he wants.
Once you get the photo up PM me so I can help you out :laugh:
Taco991 said:
Once you get the photo up PM me so I can help you out :laugh:
Click to expand...
Click to collapse
So I can recall when I had the mytouch 4g the screen posted was exactly where you would go to flash the zip have they changed it since then? because I cant find the option to load a .zip rom file from :/
smO[pdx] said:
So I can recall when I had the mytouch 4g the screen posted was exactly where you would go to flash the zip have they changed it since then? because I cant find the option to load a .zip rom file from :/
Click to expand...
Click to collapse
Where's the S-OFF lol? And yes I think you can do that. It's PD some numbers IMG.zip..
smO[pdx] said:
So I can recall when I had the mytouch 4g the screen posted was exactly where you would go to flash the zip have they changed it since then? because I cant find the option to load a .zip rom file from :/
Click to expand...
Click to collapse
Facepalm. You do NOT have S-OFF, What the hell made you think you did. This is normal... Wow. You need to install a custom recovery to flash zips, by the way.
Hey easy on him, he was just mistaken. OP, do you need me to show you how to go back to stock?
smO[pdx] said:
I had ended up using the all in one HTC One S root utility that was linked in the fourms. After following all the steps that where listed (While following the youtube guide) My phone when on bootloader will show ****Unlocked**** across the top but s=off any ideas on why that is? I havent quite been able to figure it out im just looking for more information so when I get home I can have at it again :/ just find it odd that given the steps and the fact I had done them all to the T im still having this issue. Any help would be great thanks for taking the time.
I assume this might be better fit for Q&A if your a mod i apologize if you could move it that would be great couldnt figure out how to delete the poist :/ "edit/delete" wont remove the post :/ sorry again
Click to expand...
Click to collapse
Oh sweet jesus you're lucky as hell.
Never ever ever sell your phone, because you got your hands on a developer one or just a phone that slipped through the cracks, because you have full S-OFF.
You should be able to flash ROMs in recovery without going to fastboot to ever flash a kernel, if the ROM is set up for it.
You would do better to change thread title...
Hunt3r.j2 said:
Oh sweet jesus you're lucky as hell.
Never ever ever sell your phone, because you got your hands on a developer one or just a phone that slipped through the cracks, because you have full S-OFF.
You should be able to flash ROMs in recovery without going to fastboot to ever flash a kernel, if the ROM is set up for it.
Click to expand...
Click to collapse
Look at a couple post above urs he doesn't have soff
Sent from my HTC VLE_U using xda premium
Hello everyone,
I am in trouble but not sure if I bricked my HTC One X AT&T hboot 1.09 or not
Here is what happened:
I had Android 4.0.3 running and rooted with bootloader unlocked.
S-ON for sure.
Yesterday I tried to install custom rom or I thought if anything wrong goes bad I would upgrade it to the latest
4.2.2 from HTC.
with some commands from the fastboot I believe I distressed the entire system to the point where it cannot boot.
the only thing my device is doing now is just booting to the screen where HTC in green and the red text beneath it or I can go to the
bootloader menu.
I tried to fix this by flashing openrecovery-twrp-2.4.1.0-evita.img
it worked, and I was able to push several ROMs but non of them got installed, I kept getting error status 7.
I wiped everything from the recovery and then locked the bootleader and now I am really really stuck.
just the bootloader is showing.
One last experiment I tried to do, I put my device into fastboot and run the RUU for one of the ROM I downloaded for my device
but I only see a black screen with HTC logo and it kept me waiting more than half hour, I knew this will not work but I thought I would try.
Is my device done and I should through it away or there is a hope of fixing it?
I had this device for more than 2 years so no way AT&T would help, that's my guess.
Please guys, any suggestion? I am all for fixing it.
It was a stupid mistake ahhhh.
Thanks in advance.
Wrong forum mate, this is for the international hox quad-core version. You have to be in the at&t HTC one XL forum.
Mr Hofs said:
Wrong forum mate, this is for the international hox quad-core version. You have to be in the at&t HTC one XL forum.
Click to expand...
Click to collapse
Sorry, is there anyway someone can move this thread to the appropriate forum.
I apologize.
I will report this one to get it moved. Good luck in the correct section
Moved to: AT&T, Rogers HTC One X, Telstra One XL > One X Q&A, Help & Troubleshooting.
(mod team)
Looks like you've possibly made several mistakes there. First problem is you've been lurking in the wrong forum, which means you've probably been trying to flash ROMs that aren't for our device. Our device forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Bookmark that page and make sure you stay within our forum. Flashing ROMs/kernels/radios that aren't intended for our device can very easily result in a bricked phone.
I think your phone is fine as long as you can get it into the bootloader. Your problem when you were flashing ROMs is that TWRP 2.4.x and 2.5.x are buggy and are basically useless. This is probably a blessing in disguise if you were attempting to flash the wrong ROM, it probably saved your ass. Download at least TWRP 2.6 from here and you should be able to flash with no problems, just make sure they're actually our Evita ROMs that you're flashing.
Now, just to make sure this doesn't happen again, what were the commands you issued through fastboot that "distressed" your system? I need to know what you were doing that caused your device to falter. Also, don't ever run a jb RUU while you're s-on or you'll definitely brick your phone, doing that (SuperCID + s-on + jb RUU) has a 100% kill rate.
As a piece of advice, I'd suggest you stop "experiencing" with your device because the experiments you've been conducting could have easily bricked your phone on several occasions. You're extremely lucky. It seems to me that you need to do some research about our device and what you can and can't do with it. A good place to start would be my Evita FAQ and How-To Guide For Beginners threads in my signature, and build from there.
Sent from my Evita
You are not bricked. With this phone, as long as the screen comes on, you are almost certainly not bricked. You just don't know how to recover.
shakash3obd said:
with some commands from the fastboot I believe I distressed the entire system to the point where it cannot boot.
Click to expand...
Click to collapse
What the heck does "some commands" mean? You need to be specific about the exact steps you took. If you don't know the commands you tried, that is a problem, as it implies you are not being careful while modding the phone.
shakash3obd said:
I tried to fix this by flashing openrecovery-twrp-2.4.1.0-evita.img
it worked, and I was able to push several ROMs but non of them got installed, I kept getting error status 7.
Click to expand...
Click to collapse
That is a very outdated version of TWRP, and probably part of your problem. Use an up to date version.
shakash3obd said:
One last experiment I tried to do, I put my device into fastboot and run the RUU for one of the ROM I downloaded for my device
but I only see a black screen with HTC logo and it kept me waiting more than half hour, I knew this will not work but I thought I would try.
Click to expand...
Click to collapse
You can't (and shouldn't) just run any RUU. You should run the proper RUU for your carrier version (AT&T) and with s-on it has to be equal or later then the hboot version on the phone. Also do not run a Jellybean RUU on the phone, since SuperCID + S-on will brick the device on most Jellybean RUUs. You're okay if the screen is coming on, but don't run any RUUs unless somewhere here specifically instructs you to.
You have a couple options to proceed:
1) Re-unlock the bootloader, install an updated TWRP version, and try flashing a custom ROM.
2) If still on hboot 1.09, try running the 1.73 or 1.85 RUU (do you remember what build number you were on when you unlocked the bootloader?).
shakash3obd said:
I had this device for more than 2 years so no way AT&T would help, that's my guess.
Click to expand...
Click to collapse
AT&T warranties phones for 1 year. So you are out of the warranty period, if that is what you are wondering about. And warranty covers manufacturing defects, not damage done by the owner due to their negligence.
Besides, you don't need a repair or replacement. You just need to know how to recover properly from what you have done.
timmaaa said:
Download at least TWRP 2.6 from here and you should be able to flash with no problems, just make sure they're actually our Evita ROMs that you're flashing.
...
Now, just to make sure this doesn't happen again, what were the commands you issued through fastboot that "distressed" your system?
....
Click to expand...
Click to collapse
Thanks for stopping by,
I believe that I cannot flash any recovery mod such as clockwork or TWRP now, because as I explained. I locked the bootloader again.
I attempted to unlock it using the htcdev unlock bin file that they sent me but in the terminal I got the message
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.148s
that's why I am stock in the bootloader.
I didn't mean 'distressed' I was trying to say I destroyed, spilling correction mistake.
to be honest with you, there were 10's of fastboot commands that I tried some are related to s-off even.
but I think what killed the system is this
fastboot flash file.img
and the file was extracted from a ROM
CARBON-KK-NIGHTLY-20140319-1133-endeavoru
I now realize it's wrong. Please do not judge me :crying:
redpoint73 said:
That is a very outdated version of TWRP, and probably part of your problem. Use an up to date version.
You have a couple options to proceed:
1) Re-unlock the bootloader, install an updated TWRP version, and try flashing a custom ROM.
2) If still on hboot 1.09, try running the 1.73 or 1.85 RUU (do you remember what build number you were on when you unlocked the bootloader?).
Click to expand...
Click to collapse
Thanks for your comments.
I put the command I used in the previous reply.
As far as the version of TWRP, I originally tried the latest one, but it wont flash at at that's why I tried an older version.
Again in my previous reply i said that I am not able to Re-unlock the bootloader.
Yes I am still in hboot 1.09 but don't remember the build number unfortunately.
Because all what I am in is because of my lack of knowledge of custom roms, would you be able to
point me to where I can download 1.73 or 1.85 RUU?
Also, Do you think I will be able to run RUU even from the bootloader menu. I tried to run RUU from the bootloader and it got stock in the
black screen with HTC logo forever!!
shakash3obd said:
Thanks for stopping by,
I believe that I cannot flash any recovery mod such as clockwork or TWRP now, because as I explained. I locked the bootloader again.
I attempted to unlock it using the htcdev unlock bin file that they sent me but in the terminal I got the message
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.148s
that's why I am stock in the bootloader.
I didn't mean 'distressed' I was trying to say I destroyed, spilling correction mistake.
to be honest with you, there were 10's of fastboot commands that I tried some are related to s-off even.
but I think what killed the system is this
fastboot flash file.img
and the file was extracted from a ROM
CARBON-KK-NIGHTLY-20140319-1133-endeavoru
I now realize it's wrong. Please do not judge me :crying:
Click to expand...
Click to collapse
I won't judge you, I'm here to try and help you. Go to htcdev and try unlocking the bootloader again from scratch, hopefully that'll work. If not, I'm really not sure what you can do. In future, just be careful and make sure know exactly what you're doing before you do it. Fastboot commands have very specific functions and should only be used in specific situations, issuing random commands is a bad idea. I you're unsure about anything or if you have any question at all please feel free to ask here or in my q&a thread.
Sent from my Evita
timmaaa said:
Go to htcdev and try unlocking the bootloader again from scratch, hopefully that'll work.
Sent from my Evita
Click to expand...
Click to collapse
I just did that and I got the following message from htcdev website
Unlocking Bootloader Instructions
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
So, that's another route that will lead to no fix
Thanks again
shakash3obd said:
I just did that and I got the following message from htcdev website
Unlocking Bootloader Instructions
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
So, that's another route that will lead to no fix
Thanks again
Click to expand...
Click to collapse
That message suggests that you haven't copied the identifier token correctly. You need to make sure you copy the whole thing, including all of the arrows at the beginning and end.
Sent from my Evita
shakash3obd said:
I just did that and I got the following message from htcdev website
Unlocking Bootloader Instructions
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
So, that's another route that will lead to no fix
Thanks again
Click to expand...
Click to collapse
That error message simply means you cut and pasted the token incorrectly (included an extra character or characters that you were not supposed to). Follow the instruction very carefully and exactly for what exactly needs to be cut and pasted.
---------- Post added at 03:43 PM ---------- Previous post was at 03:37 PM ----------
shakash3obd said:
would you be able to
point me to where I can download 1.73 or 1.85 RUU?
Click to expand...
Click to collapse
All you will mostly likely ever need for this device is in my Index thread:
http://forum.xda-developers.com/showthread.php?t=1671237
shakash3obd said:
Also, Do you think I will be able to run RUU even from the bootloader menu. I tried to run RUU from the bootloader and it got stock in the
black screen with HTC logo forever!!
Click to expand...
Click to collapse
RUU is meant as a recovery tool, and therefore is intended to work while the phone is in almost any condition (as long as the screen comes on), including bootloader.
The reason the RUU did not work, is likely because it was the wrong RUU.
---------- Post added at 03:54 PM ---------- Previous post was at 03:43 PM ----------
shakash3obd said:
I attempted to unlock it using the htcdev unlock bin file that they sent me but in the terminal I got the message
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.148s
that's why I am stock in the bootloader.
Click to expand...
Click to collapse
The bootloader unlock is a bit finicky, and its known to fail for some folks for no good reason (even if you did it all correct), possibly even numerous times. I would suggest just making sure you do the steps correctly and keep trying.
shakash3obd said:
to be honest with you, there were 10's of fastboot commands that I tried some are related to s-off even.
but I think what killed the system is this
fastboot flash file.img
and the file was extracted from a ROM
CARBON-KK-NIGHTLY-20140319-1133-endeavoru
I now realize it's wrong. Please do not judge me
Click to expand...
Click to collapse
The only judgement I have of you, is that you seem to be rushing forward a bit too much, and not researching properly.
Fastboot (and phone modding in general) is not a place to be experimenting. You should not be trying fastboot commands haphazardly. I've seen more than a few devices on this forum bricked with a couple careless fastboot commands. I would recommend you not running any fastboot commands, unless you have obtained them from one of the established guides on this forum, or from a reputable/knowledgeable contributor on this forum.
redpoint73 said:
All you will mostly likely ever need for this device is in my Index thread:
http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
Hey guys, I got my device unlocked, i think I copied an extra character.
Now I have an unlocked bootloader + recovery mod 2.6.0.
What should I do next?
should I download RUU from your thread or should should I do something else?
I
I am waiting right here right now until my phone is fixed.
Thank you so much guys
EDIT:
I tried to download RUU 1.73 and the links were down
so i downloaded 1.85 for now.
Waiting for your other instructions. Sir.
shakash3obd said:
Hey guys, I got my device unlocked, i think I copied an extra character.
Now I have an unlocked bootloader + recovery mod 2.6.0.
What should I do next?
should I download RUU from your thread or should should I do something else?
Click to expand...
Click to collapse
Download a custom ROM, move it to your phone, and flash it.
If a custom ROM is what you wanted to begin with, no reason to go backward and RUU (since you were able to get the bootloader unlocked again, and custom recovery installed).
redpoint73 said:
Download a custom ROM, move it to your phone, and flash it.
If a custom ROM is what you wanted to begin with, no reason to go backward and RUU (since you were able to get the bootloader unlocked again, and custom recovery installed).
Click to expand...
Click to collapse
This is actually my original intention, I don't want to have all the junk that comes from HTC and the one from AT&T.
Any recommendation to get something like the kitkat rom that is stable and reliable.
I am asking for recommendation because after all trouble I went through last night, I just want to get my phone to something very nice and stable other than the RUU with HTC and AT&T stuff.
Really appreciate your help.
shakash3obd said:
Any recommendation to get something like the kitkat rom that is stable and reliable.
I am asking for recommendation because after all trouble I went through last night, I just want to get my phone to something very nice and stable other than the RUU with HTC and AT&T stuff.
Click to expand...
Click to collapse
Best/recommended/favorite ROM discussions are not allowed on XDA. They are each good in their own way, and everyone has different preferences. Part of the fun of flashing custom ROMs is trying them out, to see what you like the best.
Try any of the ROMs on my Index thread, and you won't need to worry about a brick. But read through the specific ROM thread as some ROMs have specific flashing procedures.
Bear in mind that KitKat means you will be on an AOSP ROM. Sense is limited to Jellybean, for now.
---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------
shakash3obd said:
Thank you so much guys
Click to expand...
Click to collapse
Feel free to click the "Thanks" button for any posts that you found helpful.
redpoint73 said:
Best/recommended/favorite ROM discussions are not allowed on XDA.
Try any of the ROMs on my Index thread, and you won't need to worry about a brick. But read through the specific ROM thread as some ROMs have specific flashing procedures.
Bear in mind that KitKat means you will be on an AOSP ROM
.
Click to expand...
Click to collapse
I will check the index of yours when I find it since I am always lost in the xda forum.
Sorry to ask for something not allowed in XDA, I will start looking for AOSP ROM since I want something like KitKat.
If we can forget about "recommendation/best ROM" will anyone can point me to where to find KitKat like ROM for my device or
give a list of names or links to threads in XDA. Or even the whole forum starting point for which i can find these type of ROMs
just to avoid bricking my device since it's S-On
redpoint73 said:
RUU is meant as a recovery tool, and therefore is intended to work while the phone is in almost any condition (as long as the screen comes on), including bootloader.
The reason the RUU did not work, is likely because it was the wrong RUU.
Click to expand...
Click to collapse
What I was afraid of is happening, I run RUU 1.85 and I am right now passed 50 minute with the phone screen is black with HTC logo on it.
is this normal?
should I be doing anything? or just wait more or unplug the phone from the PC?
OK.. here we go.. I bought my VERIZON M8 the day it was released. I came to this site, after having successfully put the viper Timon my DNA. Not exactly.new to this but I'm in a bit of a mess. I have tampered above unlocked on my bootloader screen and when I boot into the ROM I am using... A message flashes at the bottom saying for development use only and other legal stuff from HTC. What steps can I take to remove those? I have permanent s-off and weaksauce still installed. Is there a toolkit like for the m7 or am I missing something? Help is appreciated.
Joeymaz73 said:
OK.. here we go.. I bought my VERIZON M8 the day it was released. I came to this site, after having successfully put the viper Timon my DNA. Not exactly.new to this but I'm in a bit of a mess. I have tampered above unlocked on my bootloader screen and when I boot into the ROM I am using... A message flashes at the bottom saying for development use only and other legal stuff from HTC. What steps can I take to remove those? I have permanent s-off and weaksauce still installed. Is there a toolkit like for the m7 or am I missing something? Help is appreciated.
Click to expand...
Click to collapse
I see a message about "Development use only for HTC" or whatever when booting into the bootloader (or recovery...or both...I can't remember), but it doesn't affect anything. Is that what you're referring to? Also, remove Weaksauce like the S-Off instructions told you to do.
And what exactly is this "mess" you're in? If a message flashes across your screen and then your phone finishes booting into the ROM, that doesn't exactly sound like a mess to me...
sfreemanoh said:
I see a message about "Development use only for HTC" or whatever when booting into the bootloader (or recovery...or both...I can't remember), but it doesn't affect anything. Is that what you're referring to? Also, remove Weaksauce like the S-Off instructions told you to do.
And what exactly is this "mess" you're in? If a message flashes across your screen and then your phone finishes booting into the ROM, that doesn't exactly sound like a mess to me...
Click to expand...
Click to collapse
I guess I'm just ocd. I dont like seeing those messages if i dont have to.I had originally. Removed weaksauce.. but put it back on when the permanent. Root didn't take effect properly. Is everyone seeing tampered? If not I'd prefer to be able to get rid of it as well.
Joeymaz73 said:
I guess I'm just ocd. I dont like seeing those messages if i dont have to.I had originally. Removed weaksauce.. but put it back on when the permanent. Root didn't take effect properly. Is everyone seeing tampered? If not I'd prefer to be able to get rid of it as well.
Click to expand...
Click to collapse
If flashing the superuser zip didn't work correctly for you, that's an issue you should probably look into...
Like I said, I don't see it say "tampered", I just see the "This build is for development purposes only" message when I boot into recovery. You're sure you see it when booting normally into the ROM itself?
sfreemanoh said:
If flashing the superuser zip didn't work correctly for you, that's an issue you should probably look into...
Like I said, I don't see it say "tampered", I just see the "This build is for development purposes only" message when I boot into recovery. You're sure you see it when booting normally into the ROM itself?
Click to expand...
Click to collapse
go here: http://forum.xda-developers.com/showthread.php?t=2709976
kwkw480 said:
go here: http://forum.xda-developers.com/showthread.php?t=2709976
Click to expand...
Click to collapse
Yeah, but unless if he also flashed a custom boot.img (or a ROM that has a custom boot.img included), or is actually booting into recovery when he sees it, he shouldn't be seeing it when he boots into the ROM itself.
Edit: I just misread the OP, apparently he may be using a custom ROM, I didn't notice that before.
sfreemanoh said:
Yeah, but unless if he also flashed a custom boot.img (or a ROM that has a custom boot.img included), or is actually booting into recovery when he sees it, he shouldn't be seeing it when he boots into the ROM itself.
Edit: I just misread the OP, apparently he may be using a custom ROM, I didn't notice that before.
Click to expand...
Click to collapse
Sorry Guys, I should have told you which ROM I had flashed to.. SKYFALL★| |►1.12.605.11◄|4.4.2|VZW||ODEX/DEODEX||►1.2◄|April.10. I'll follow the directions pointed to in the thread above when I get home.. Still leaves me with "tampered" when I boot into recovery or bootloader.
kwkw480 said:
go here: http://forum.xda-developers.com/showthread.php?t=2709976
Click to expand...
Click to collapse
Ok.. That zip file, for the red letters worked great. thank you..
after a bunch of searching.. I found this..http://forum.xda-developers.com/showthread.php?t=2708565
thanks for everyone's help. I appreciate everything you do.
Or you can go here where there are a variety of options including making your phone look like it is still s-on
http://forum.xda-developers.com/showthread.php?t=2710503
Thanks for that tool page. I love learning new things about these phones. 20 years I've just been a PC guy.. learning how to do some of this can be tricky. Thank goodness for this forum and the people on it.
Okay so my friend asked me to fix a phone that he says one day it got stuck in boot splash screen. He claims he did not try to flash a custom Rom or something but he said he hadn't.here's some of the phones info
HTC one x
***TAMPERED***
***UNLOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Can anyone sheed some light on the subject.
I don't know how to use adb and fastboot
And I have Windows xp and Mac 10.6 and lynx
Wrong forum, the evita is the HTC one XL.. Thread reported for moving to the correct forum. This part is for the international HTC one X (quad-core model)
Good luck
Mr Hofs said:
Wrong forum, the evita is the HTC one XL.. Thread reported for moving to the correct forum. This part is for the international HTC one X (quad-core model)
Good luck
Click to expand...
Click to collapse
As if by magic, it appears in the One XL forum.
I think your friend is telling fibs, phones don't just magically stop booting for no reason. Please tell him to own up to whatever activities lead to this situation, as embarrassing as it might be, I need to know how this happened in order to help properly.
Now, just to be clear, the phone is actually the HTC One XL, not the HTC One X. They look similar but are actually very different. What recovery is installed on the device?
Another question for you, why isn't your friend posting here and attempting to fix this problem himself? If he can't recover from a simple problem like this (or can't be bothered learning/trying) he honestly has no place having a modified phone. That might sound harsh but it's the truth, this is very basic knowledge, it's flashing 101. Knowing how to recover from something like this is an essential skill for anyone who owns a modified phone. If your friend isn't interested in being honest about what lead to this situation, or interested in learning how to recover from this situation, my only advice is to return to the device to stock and leave it that way. I'd strongly urge him to get on here and post himself, and do some reading to educate himself on the ins and outs of modified devices.
Sent from my Evita
sorry for being so vauge
My friend is a lady friend who had no idea how the phone could have become modified. The phone is a HTC one X and my lady friend said she would love nothing more then to have a stock phone. My friend has no intrest in leaning how the in's and out's of HTC but, I on the other hand would love to learn about HTC and Android. I come from a n Apple community and have a little knowledge but not a lot.
Anything you can tell me would help greatly, and I would be indeed greatful.
Sincerely Nanamkin
The only option for you is to return the phone to stock, giving a modified device to someone who knows nothing about them and doesn't even want a modified device is a bad idea. I'll just reiterate though, it isn't a HTC One X, it's the One XL. Is it an at&t model? Can you please retrieve the software version from Settings/About Phone? Can you please enter recovery from the bootloader screen and tell me which recovery version is installed?
Sent from my Evita
Thank you so much
timmaaa said:
The only option for you is to return the phone to stock, giving a modified device to someone who knows nothing about them and doesn't even want a modified device is a bad idea. I'll just reiterate though, it isn't a HTC One X, it's the One XL. Is it an at&t model? Can you please retrieve the software version from Settings/About Phone? Can you please enter recovery from the bootloader screen and tell me which recovery version is installed?
Sent from my Evita
Click to expand...
Click to collapse
it is AT&T
and it has TWRP 2.14
dont know the software version but when i connect to 'htc sync manger'' it says version 2.20 but im not sure.
Nanamkin said:
it is AT&T
and it has TWRP 2.14
dont know the software version but when i connect to 'htc sync manger'' it says version 2.20 but im not sure.
Click to expand...
Click to collapse
There is no TWRP 2.14 for this device, are you confusing it with the hboot number? Go to Settings/About Phone (where I said it would be earlier), and post the software version please.
Sent from my Evita
Man your GOOD
timmaaa said:
There is no TWRP 2.14 for this device, are you confusing it with the hboot number? Go to Settings/About Phone (where I said it would be earlier), and post the software version please.
Sent from my Evita
Click to expand...
Click to collapse
I am sooo sorry. you are absulotly right, and you are good! how did you know that? lol
here is the right info.
TWRP 2.3.1.0
im sorry i cant boot into the phone to check the setting/about phone for a software version. do you know any other way?
and while i was messing around i figured out how to install ADB and FASTBOOT and use it.
I'm an idiot, completely forgot you can't boot to check the software version. Facepalm. Can you please check the CID for me? Put the phone in fastboot mode and issue this command:
Code:
fastboot oem readcid
Sent from my Evita
got it
timmaaa said:
i'm an idiot, completely forgot you can't boot to check the software version. Facepalm. Can you please check the cid for me? Put the phone in fastboot mode and issue this command:
Code:
fastboot oem readcid
sent from my evita
Click to expand...
Click to collapse
cid:11111111
Ok. To get the phone back to stock you Erik need to run an RUU, but in order to do that safely you'll first need to get s-off. To get s-off you're gonna need a booting ROM on the device. Purely for this exercise I think Kickdroid would be your best option, head to our Android Development section and find the Kickdroid thread, download it, and use TWRP recovery to install it. Look in the How-To Guide For Beginners thread in my signature for full instructions on how to flash the ROM. Please note, you'll also need to flash the boot.img from the ROM zip via fastboot after flashing the ROM.
Sent from my Evita
got it
Okay I have the Rom on my phone now what?
Nanamkin said:
Okay I have the Rom on my phone now what?
Click to expand...
Click to collapse
Now you can get s-off, head over to the Facepalm thread and follow the instructions there.
Facepalm S-off
your awesome
timmaaa said:
Now you can get s-off, head over to the Facepalm thread and follow the instructions there.
Facepalm S-off
Click to expand...
Click to collapse
oh yeah i was over there just a little awhile ago. i een your name so i tiend to fallow it but couldnt get the rom. thank you sooo much
timmaaa said:
Now you can get s-off, head over to the Facepalm thread and follow the instructions there.
Facepalm S-off
Click to expand...
Click to collapse
when i get done with step 6 i cant use the last 3 codes for the s-off flag because the phone wont boot into android?
Nanamkin said:
when i get done with step 6 i cant use the last 3 codes for the s-off flag because the phone wont boot into android?
Click to expand...
Click to collapse
I thought you said you had the ROM on your phone? Did you just mean the zip? If so, go to the How-To thread in my signature and follow the instructions to install the ROM and flash the boot.img. Then you can go back to the Facepalm thread. Just make sure you boot up the phone and set it up before doing the s-off process.
I got the rom to work
timmaaa said:
I thought you said you had the ROM on your phone? Did you just mean the zip? If so, go to the How-To thread in my signature and follow the instructions to install the ROM and flash the boot.img. Then you can go back to the Facepalm thread. Just make sure you boot up the phone and set it up before doing the s-off process.
Click to expand...
Click to collapse
I got the rom to boot after fallowing your directions(like you said)lol. but when i do steps 7 the 3 codes it says there are no directory. I got the first one to go but the other 2 would not work
Did you remember to extract (unzip) the file into your fastboot folder?
Sent from my Evita
got the os to boot
timmaaa said:
Did you remember to extract (unzip) the file into your fastboot folder?
Sent from my Evita
Click to expand...
Click to collapse
okay so i have the rom on the phone (kickdroid) and now i cant run the last 3 codes on step 7. any clue. I have soffbin zip unzipped in the directory but where exactly do i put it? i have it in the same folder as adb and fastboot is that right?