After Rooting and Unlocking my HOX by using SuperCID, there's red text on my boot screen that talks about developmental builds, etc....
sort of like the Yellow Warning Triangle after you rooted the SGSII.
I'm assuming this is normal (because of the SuperCID) and I was wondering if there's a way to remove it.
Thanks
yellowfddriver said:
After Rooting and Unlocking my HOX by using SuperCID, there's red text on my boot screen that talks about developmental builds, etc....
sort of like the Yellow Warning Triangle after you rooted the SGSII.
I'm assuming this is normal (because of the SuperCID) and I was wondering if there's a way to remove it.
Thanks
Click to expand...
Click to collapse
You're right that it's normal, we all have it after SuperCID. Anyway, I don't believe there's any way to remove it just yet.
stnguyen09 said:
You're right that it's normal, we all have it after SuperCID. Anyway, I don't believe there's any way to remove it just yet.
Click to expand...
Click to collapse
Probably not. Hopefully one of the amazing devs will find a way. However, it's definitely a small price to pay for not being stock...for all of us ATT HOX owners.
yellowfddriver said:
Probably not. Hopefully one of the amazing devs will find a way. However, it's definitely a small price to pay for not being stock...for all of us ATT HOX owners.
Click to expand...
Click to collapse
Once we're able to flash a new splash screen it may go away
stnguyen09 said:
Once we're able to flash a new splash screen it may go away
Click to expand...
Click to collapse
There might be some code somewhere that's like if CID= x, then display this warning.
I thought I read somewhere that it was possible to remove the Tampered banner on the HBOOT screen while unlocked as well.
Whatever it is, I'm sure somebody will find it.
I'm just glad that it's normal for those who have used SuperCID.
Not sure, but I think the red text boot screen is due to an insecure boot image. If I remember correctly, I don't think I got the red text after SuperCID, but did get it when going into recovery (after CWM flashed). Did not get it during normal boot until I flashed a later version of CleanROM (when scrosler started including the boot image in the zip).
---------- Post added at 10:58 AM ---------- Previous post was at 10:55 AM ----------
yellowfddriver said:
I thought I read somewhere that it was possible to remove the Tampered banner on the HBOOT screen while unlocked as well.
Click to expand...
Click to collapse
I think the only way (currently) to remove the "tampered" banner is to RUU back to stock. And the BL will always say either "unlocked" or "relocked" once BL unlocked (currently no way to change it to "locked"). Some have speculated we may be able to change these once S-Off is achieved.
Weird, I'm running Clean ROM SE 3.0 and it still shows on boot. It's no big deal...I'll see if it shows after the next Clean Rom build.
yellowfddriver said:
Weird, I'm running Clean ROM SE 3.0 and it still shows on boot. It's no big deal...I'll see if it shows after the next Clean Rom build.
Click to expand...
Click to collapse
--Post deleted because I'm not quite sure if my information was correct--
It shows because of the insecure boot image and maybe also triggered by a custom recovery.
@gunnyman: You're probably right on that one. I was wondering because as Redpoint73 had said...when he had flashed a later version of CleanROM, the red text didn't appear on normal boot. I'm running CleanROM 3.0 right now...perhaps the red text is appearing because there is no "secure boot image" for a rom based off of an unleaked RUU? As I understand, CleanROM 3.0 is based off of 1.88. Perhaps the boot.img will be included in the next release and the red text will disappear.
yellowfddriver said:
@gunnyman: You're probably right on that one. I was wondering because as Redpoint73 had said...when he had flashed a later version of CleanROM, the red text didn't appear on normal boot.
Click to expand...
Click to collapse
No, I said: "Did not get it during normal boot until I flashed a later version of CleanROM"
I had red text when going into recovery, after flashing CWM. No red text on normal boot on EARLIER versions of CleanROM (where boot.img was either not available, or had to be pushed via fastboot, which I never did). Starting on something like CleanROM 2.5 or 2.6, had red text on normal boot.
Got it?
Ah. That makes sense. My mistake. Sorry about that. AFAIK, the yellow triangle was removable from the SGSII bootscreen (I too had a SGS Epic Touch 4g which was unlocked and rooted with the yellow triangle). So I suppose it's only a matter of time
yellowfddriver said:
Ah. That makes sense. My mistake. Sorry about that. AFAIK, the yellow triangle was removable from the SGSII bootscreen (I too had a SGS Epic Touch 4g which was unlocked and rooted with the yellow triangle). So I suppose it's only a matter of time
Click to expand...
Click to collapse
it's one of the things we want S-off for. I have one of those USB shorting plugs used to reset the altered counter on the SGS phones. I'm scared to plug it in to my HOX though
---------- Post added at 01:10 PM ---------- Previous post was at 01:09 PM ----------
yellowfddriver said:
@gunnyman: You're probably right on that one. I was wondering because as Redpoint73 had said...when he had flashed a later version of CleanROM, the red text didn't appear on normal boot. I'm running CleanROM 3.0 right now...perhaps the red text is appearing because there is no "secure boot image" for a rom based off of an unleaked RUU? As I understand, CleanROM 3.0 is based off of 1.88. Perhaps the boot.img will be included in the next release and the red text will disappear.
Click to expand...
Click to collapse
I doubt it. I think insecure boot images will be with us for a long time to come. They're required I believe for nifty tricks like zipaligning and running other init.d scripts on boot up.
---------- Post added at 01:12 PM ---------- Previous post was at 01:10 PM ----------
At any rate it's easily gotten rid off when you flash the RUU it goes away.
gunnyman said:
it's one of the things we want S-off for. I have one of those USB shorting plugs used to reset the altered counter on the SGS phones. I'm scared to plug it in to my HOX though
---------- Post added at 01:10 PM ---------- Previous post was at 01:09 PM ----------
I doubt it. I think insecure boot images will be with us for a long time to come. They're required I believe for nifty tricks like zipaligning and running other init.d scripts on boot up.
---------- Post added at 01:12 PM ---------- Previous post was at 01:10 PM ----------
At any rate it's easily gotten rid off when you flash the RUU it goes away.
Click to expand...
Click to collapse
So just to be sure, if i flash a stock RUU (not sure which RUU to choose) the red text will be removed (if warranty issues ever arise). I'm not worried about them (Best-Buy) going into the boot-loader, the only thing that bothers me is the red text.
I did some re-search on this issue and found this in the evo lte section, and if we can replicate what was done it can be removed http://forum.xda-developers.com/showthread.php?t=1738462
manup456 said:
I did some re-search on this issue and found this in the evo lte section, and if we can replicate what was done it can be removed http://forum.xda-developers.com/showthread.php?t=1738462
Click to expand...
Click to collapse
Ummm, you need S-Off to do that. It hasn't been achieved for our device.
Its already been discussed here many times that the various tampered, unlocked flags can be changed if/when S-Off is achieved.
Related
I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
reflash
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp
thesm4rt1 said:
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp
Click to expand...
Click to collapse
I will definitely be trying that. Will be back in a couple of hours and let you know how it went. Thank you!
bbonline said:
I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.
Butters619 said:
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.
Click to expand...
Click to collapse
I did do the factory wipe.
By the way, I tried what I was told to do and nothing happened. It successfully flashes the boot image and recovery, but when it tries to boot into the recovery, it just freezes in the recovery with the word TEAMWIN and a blue background....No menu or options.... I did try several different ways by downloading and installing several versions of the CWM and TWRP, but no success. Any other suggestions? Will I be stuck with this piece of brick now? Please help.
bbonline said:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.
Butters619 said:
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.
Click to expand...
Click to collapse
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!
bbonline said:
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!
Click to expand...
Click to collapse
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!
Butters619 said:
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!
Click to expand...
Click to collapse
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?
bbonline said:
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?
Click to expand...
Click to collapse
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
Darn.... I just hope I don't have to deal with sending it for any repair. Gave you thanks!
Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
But only if they reboot and look, which from what I've seen here, they never seem to do.
iElvis said:
But only if they reboot and look, which from what I've seen here, they never seem to do.
Click to expand...
Click to collapse
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.
Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
Butters619 said:
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.
Click to expand...
Click to collapse
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on
trichrome1 said:
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on
Click to expand...
Click to collapse
Nope once you unlocked it won't ever say locked again. Just re-locked
gunnyman said:
Nope once you unlocked it won't ever say locked again. Just re-locked
Click to expand...
Click to collapse
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
You should probably double check that. Anybody with an AT&T One X had to have SuperCID to unlock their bootloader so that wouldn't matter. I have unlocked two AT&T One Xs and run the 1.85 RUU on both (one of them a couple times) and I have run the 2.20 RUU on one. every time it says RELOCKED.
Mine did this to when going to 4.5.
I did the following to get back into Recovery.
Use fastboot to flash the boot.img from the cleanrom 4.5 zip.
"fastboot flash boot boot.img"
I then flashed the recovery (TWRP 2.2.1.4 at the moment) again to the phone.
next I erased Cache.
"fastboot erase cache"
I then used the phone itself to reboot the bootloader and went into recovery. It took about 10 minutes but recovery finally booted.
At this point I had no access to anything on the SD card. so I selected mount and mounted the sd card as disk drive to access it through my PC. I was forced to format the drive at this point and loaded a fresh copy of the ROM onto the drive for flashing.
You probably just got a wrong recovery. The recovery on twrp website didn't work for me. The one I downloaded from the development section works fine.
Sent from my One X using xda app-developers app
trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
Screenshots PLS
I recently used the Exploit and All-in-One Toolkit with varied success. I was able to get my token, but this where things got weird.
1. The file from HTC comes in as a VLC file. I use Chrome and my local broadband service as my email. I'm not able to save it to a folder. I still was somehow able to unlock the bootloader as it says ***TAMPERED*** and ***UNLOCKED***
2. I try to use the tool to flash TWRP and my command seems to go through, but the phone never reboots itself it just stays at the fastboot. I found out later, while chosing recovery that it did somehow flash it, but i'm not able to backup anything.
3. I'm unable to send Superuser thru to perm root. It keeps telling me device not connected in ADB.
I guess my question is where is the error coming from on my side. Should I set back to stock and start over and if so how? My last phone was an HTC Inspire which I rooted and constantly swapped roms, radios, kernels, so this isn;t my first rodeo. I'm basically looking to root to future use as right now I'm not looking at roms, but would love to get the ATT crapware off the phone. The phone is operating fine since my attempt so any info would be great.
I posted in the all=in=one section, but haven't had any responses.
I came from a inspire as well. This is a different ballgame. can you get into recovery from bootloader screen?
Sent from my HOX w/CM10.1
subarudroid said:
I came from a inspire as well. This is a different ballgame. can you get into recovery from bootloader screen?
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
I can get into TWRP from the bootloader but I can't make a backup and i can't get the toolkit to push thru the superuser app to give root.
See if you can find a superuser zip and install in twrp?
Sent from my HOX w/CM10.1
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
Oops wrong one
Try this.
Sent from my HOX w/CM10.1
I went back in to recovery and was able to make a backup of my stock rom and settings. Where is a link to a superuser.zip and how to push it thru.
http://forum.xda-developers.com/attachment.php?attachmentid=1195050&d=1342168095
Sent from my HOX w/CM10.1
---------- Post added at 11:52 AM ---------- Previous post was at 11:50 AM ----------
After downloaded mount sd and copy, then install in twrp
Sent from my HOX w/CM10.1
---------- Post added at 11:54 AM ---------- Previous post was at 11:52 AM ----------
Crap. Im having a hard time shopping at wallmart and posting links.
http://forum.xda-developers.com/showthread.php?t=1742522
Sent from my HOX w/CM10.1
Thanks I finally got root and rid of the bloatware. It's weird because titanium backup won't show ATT Navigator for me to delete.
Good job. Sent you a pm if you need anymore help?
Sent from my HOX w/CM10.1
I changed my CID back to CID__001 from superCID and re-locked phone. Now when I go back to unlock with unlock_code.bin it does not work.
So I regenerate a token identifier....
C:\Users\M\HOX>fastboot oem get_identifier_token
< waiting for device >
... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
INFO639E7B248BDCAB6CBEA0577A98CD11AD
INFO0B20640D8180AB31F0B0DC2DDC62EB6A
INFO2524B5D27105D40678D5CC2C0E492220
INFO6A98F11162989E19E5F326B78E38D72E
INFO31E8D7A04B433C18C204D007D4B58689
INFO693ABAC1650EB10FC962312231F9E548
INFOF8D103A3EE4DD17F2D807751D006C739
INFO6254FA142E08F7DDBDF777300D8C8BE5
INFO4A6BA0CE58FFAAF25646B8B8A21CF068
INFO50F67F9A30A6DD984D50E497AF32485D
INFOFF19DBAB976D7F81CDC9E8320BD25E9D
INFOA56BB0B240AB81E35CD9742922C28320
INFOC02CF3A74B8589948155024DA23D31EC
INFO7620755FE9B5CA879B4968E79E239B39
INFOBFC9203AD5ED5373F568492B61B20700
INFO0C5B33DEA9E101B475EAF0E3CD4076F7
INFO<<<<< Identifier Token End >>>>>
OKAY [ 0.063s]
finished. total time: 0.063s
C:\Users\M\HOX>
On HTC site I get error code 160 mid not allowed when I try to generate a a new .bin
My Token identifier prior to the change was
<<<< Identifier Token Start >>>>
1A5036DDFCC755FA08619C55D40C47D0
A6FB8A57A0F9482C9174A6FA83921F0A
8D639270F2DCA79AD36FFB093D79F319
B9A66170322959FC5A93C12CB3500DF5
C6D42B624710F209FF4A4B70F5EAA9F3
B1947CFA26A96C7969F2788CAA631583
1C643ED6FEA902F1349AC5219AB8648C
C405010F564F16D1F63E3EA5DE089BE6
02D0CC3CBBFDDBBC74B8844144333E0E
BB70889A1F45259AE20ADCE88E7A201A
CF4BEB1A6F44E3162C63959FB800CF99
1E081824821F45DD2BEC4420A29A8F06
F4271D50F0F124EF324F5E41A34CE420
10572E09220654655A467B7AE1EAFB51
1D52CB57BA7154FB9CAC9F782494AF35
D76D2762018B42BEA736906581D9D1BE
<<<<< Identifier Token End >>>>>
The HTCDev.com site won't work with the AT&T CID, that's why it was changed in the first place.
I don't know why you changed the CID, what you hope to gain from it, and I don't recommend it. I don't see how its going to help your situation at all, really it just makes things harder for you (as you see you can't unlock the bootloader now).
I would also kindly suggest you back off from trying any new things, without at least coming on here and asking first if its a good idea. From your other thread, its apparent you are new to this phone, and are doing some things that are not necessarily the best way forward.
redpoint73 said:
The HTCDev.com site won't work with the AT&T CID, that's why it was changed in the first place.
I don't know why you changed the CID, what you hope to gain from it, and I don't recommend it. I don't see how its going to help your situation at all, really it just makes things harder for you (as you see you can't unlock the bootloader now).
I would also kindly suggest you back off from trying any new things, without at least coming on here and asking first if its a good idea. From your other thread, its apparent you are new to this phone, and are doing some things that are not necessarily the best way forward.
Click to expand...
Click to collapse
This phone is crap, from the confusing naming convention , bootloader lock, S-ON and the most fascinating that I just realized last night NO ADB IN BOOTLOADER OR STOCK RECOVERY. Way too complicated to work with.
So I am stuck now because I cannot RUU or get into past bootloader to change the recovery back to TWRP.
ADB works fine in bootloader. Looks like pilot error.
Complaining isn't going to help your case, might hurt it (discourage those of use who have been trying to help you).
Palmetto_X said:
This phone is crap, from the confusing naming convention , bootloader lock, S-ON and the most fascinating that I just realized last night NO ADB IN BOOTLOADER OR STOCK RECOVERY. Way too complicated to work with.
So I am stuck now because I cannot RUU or get into past bootloader to change the recovery back to TWRP.
Click to expand...
Click to collapse
I'm new to the onex myself, so I would like to know why you relocked it after all that work to get it unlocked? Just got mine unlocked with a custom Rom installed, and I don't know why you'd undo that.
Sent from my HTC One XL using Tapatalk 2
sizemore2000 said:
I'm new to the onex myself, so I would like to know why you relocked it after all that work to get it unlocked? Just got mine unlocked with a custom Rom installed, and I don't know why you'd undo that.
Click to expand...
Click to collapse
OP stated in another thread he bought his bootloader unlocked too.
But yes, I agree, there was not point in him relocking it. He wanted to return to stock. I suggested he flash a stock rooted ROM, but he either didn't listen, or was already too far down the relocking path (removed TWRP).
redpoint73 said:
ADB works fine in bootloader. Looks like pilot error.
Complaining isn't going to help your case, might hurt it (discourage those of use who have been trying to help you).
Click to expand...
Click to collapse
Tell me about ADB in bootloader? What do you mean pilot error?
thanks for hanging with me
I think you should PILOT the closest vehicle over the phone to end this misery for everyone
954wrecker said:
I think you should PILOT the closest vehicle over the phone to end this misery for everyone
Click to expand...
Click to collapse
Aren't you supposed to be in school?
Palmetto_X said:
Tell me about ADB in bootloader? What do you mean pilot error?
thanks for hanging with me
Click to expand...
Click to collapse
ADB should work fine in bootloader. Are you getting any error message, or no response when you try to use adb?
Does the phone show up if you type:
adb devices
If not, try to re-install HTC Sync.
---------- Post added at 12:05 PM ---------- Previous post was at 11:37 AM ----------
How did you end up with no TWRP? Did the RUU run partially, and return the phone to stock recovery? Or did you do something else to go to stock recovery?
redpoint73 said:
ADB should work fine in bootloader. Are you getting any error message, or no response when you try to use adb?
Does the phone show up if you type:
adb devices
If not, try to re-install HTC Sync.
---------- Post added at 12:05 PM ---------- Previous post was at 11:37 AM ----------
How did you end up with no TWRP? Did the RUU run partially, and return the phone to stock recovery? Or did you do something else to go to stock recovery?
Click to expand...
Click to collapse
Nothing shows up in adb devices.....I even ran adb logcat and went through all the menus on the phone seeing if it would catch
I will try to re install sync
In attempting to fix the RUU problem I have I would flash stock recovery, stock boot.img, relock, try to RUU......my last genius move was rename cid , stock recovery, boot.img, relock...........now I am dead in the water
Palmetto_X said:
Nothing shows up in adb devices.....I even ran adb logcat and went through all the menus on the phone seeing if it would catch
I will try to re install sync
Click to expand...
Click to collapse
This is the entire cause of your RUU troubles. Your computer is simply not talking to the phone.
Re-install HTC Sync, and try a different USB ports. Problems with the PC not seeing the phone are almost always due to one of these 2 things. Last resort is to use a different PC (if possible).
If adb doesn't see the phone, the RUU won't run either. Get the PC to see the phone, and the RUU will run.
---------- Post added at 01:31 PM ---------- Previous post was at 01:25 PM ----------
Wait, you said you relocked. So you must have had an adb/fastboot connection at some point.
Something is royally screwed here. It really seems to me that you are doing things to the phone, that you shouldn't. Seriously, don't do anything more to the phone, unless we tell you to. NOTHING.
How did you flash stock recovery?
What is the state of the phone now?
Flashing boot.img was not a good idea. Stock boot.img + CM10 will result in the phone not booting (wrong kernel), assume that is the state you are now in?
redpoint73 said:
This is the entire cause of your RUU troubles. Your computer is simply not talking to the phone.
Re-install HTC Sync, and try a different USB ports. Problems with the PC not seeing the phone are almost always due to one of these 2 things. Last resort is to use a different PC (if possible).
If adb doesn't see the phone, the RUU won't run either. Get the PC to see the phone, and the RUU will run.
---------- Post added at 01:31 PM ---------- Previous post was at 01:25 PM ----------
Wait, you said you relocked. So you must have had an adb/fastboot connection at some point.
Something is royally screwed here. It really seems to me that you are doing things to the phone, that you shouldn't. Seriously, don't do anything more to the phone, unless we tell you to. NOTHING.
How did you flash stock recovery?
What is the state of the phone now?
Flashing boot.img was not a good idea. Stock boot.img + CM10 will result in the phone not booting (wrong kernel), assume that is the state you are now in?
Click to expand...
Click to collapse
I just tried it on another PC and got RUU 2.2 to work. Thank you very much for your persistence.
Ouch. 2.20 RUU means you are now stuck with the 1.14 hboot. Fine if you want to stay stock, but a bit of a pain for flashing custom ROMs, as you now have to flash boot.img separately from fastboot. You also can't flash radios now.
1.73 or 1.85 would have been better. Did you try to run those RUUs on this other PC first?
He deserves hboot 1.14 after talking trash earlier. Hopefully he didn't even try the earlier ruu's
Sent from my HTC One XL
Well, he said he wanted to put it back to stock. If you never plan to root it, 1.14 isn't an issue.
iElvis said:
Well, he said he wanted to put it back to stock. If you never plan to root it, 1.14 isn't an issue.
Click to expand...
Click to collapse
He seems to know a decent amount of tricks (at least enough to be dangerous!). I'd be surprised if he never plans to root. But that's just a guess.
so... theres a way to permanently brick your CID to the point where it cant be changed/unlocked again? :/ now i'm REALLY going to read up on how to relock and get my phone back to the 2.20 RUU (came on that, no sense trying to get an earlier one) for selling it....
redpoint73 said:
He seems to know a decent amount of tricks (at least enough to be dangerous!). I'd be surprised if he never plans to root. But that's just a guess.
Click to expand...
Click to collapse
I'd like him to root his phone and brick it. Then he can come back here to whine about how crappy the phone is when he's the retard.
I have a black HTC screen with a ! triangle in each corner. Tried to ruu and it failed and I have no clue what to do now. I've never seen this before so I'm lost. . .
I was running carbon rom and was having some bad random reboot problems. I wiped and tried to flash venom and it kept rebooting. So I locked it and tried to ruu, and it failed horribly.
I should also add that I am soff.
Have you tried to get back into boot loader manually? Press and hold volume down and power at the same time. When lights stop flashing, release power while continuing to hold volume down until you enter boot loader.
You can try http://forum.xda-developers.com/showthread.php?t=1982442
Sent from my One X using xda premium
---------- Post added at 05:10 AM ---------- Previous post was at 05:03 AM ----------
You have what is called a radio brick. I don't know of any method to fix it unless you can get another ruu to flash or search around for a method to repair it.
Sent from my One X using xda premium
fadetoblack2104 said:
I have a black HTC screen with a ! triangle in each corner. Tried to ruu and it failed and I have no clue what to do now. I've never seen this before so I'm lost. . .
I was running carbon rom and was having some bad random reboot problems. I wiped and tried to flash venom and it kept rebooting. So I locked it and tried to ruu, and it failed horribly.
I should also add that I am soff.
Click to expand...
Click to collapse
First off, you are not bricked in any sense of the word. On this device, if the screen comes on at all, you are not bricked, and you can recover from it. It just takes the proper steps.
RUU should have given an error code (like "ERROR 170"). Telling what code comes up might help.
You might just try to download the RUU again.
Or you can try to re-unlock the bootloader and flash custom recovery via adb. If that works, just load a custom ROM zip (by way of mount USB in recovery) and flash it.
---------- Post added at 10:16 AM ---------- Previous post was at 10:14 AM ----------
Venomtester said:
You have what is called a radio brick.
Click to expand...
Click to collapse
Is that what the HTC screen with the red triangle with exclamation mark in each corner symbolizes? This screen is new to me.
I'm only familiar with the screen that had the big red triangle and exclamation in the middle of the screen, which is stock recovery.
I wish someone would put that you don't need to relock bootloader to RUU if you are S-OFF in the stickies somewhere.
Unfortunately, yes. The triangles in each corner with exclamation points are for radio brick. He damaged the partition in some way. Like you said, he may be able to flash over it but depends on the damage. If not it will be jewel or JTAG time.
Sent from my One X using xda premium
Venomtester said:
Unfortunately, yes. The triangles in each corner with exclamation points are for radio brick. He damaged the partition in some way. Like you said, he may be able to flash over it but depends on the damage. If not it will be jewel or JTAG time.
Click to expand...
Click to collapse
Maybe something went awry while the RUU was trying to write to the radio partition?
He should be able to just reflash a new radio.
I suspect the initial problem was trying to run a Sense rom (Venom) on top of the AOSP kernel from Carbon.
Very possible. Bad ruu or didn't flash properly. Maybe op can let us know how reflashing turns out or if the jewel kit works. And like stated above, sense and aosp radio partitions are different. Being hung up on an asop ROM while flashing a sense ruu can not be good.
Sent from my One X using xda premium
---------- Post added at 02:02 PM ---------- Previous post was at 01:40 PM ----------
I believe so. But if he still has asop boot image it will have to be asop radio. This might help http://forum.xda-developers.com/showthread.php?p=27022095
Sent from my One X using xda premium
Venomtester said:
Very possible. Bad ruu or didn't flash properly. Maybe op can let us know how reflashing turns out or if the jewel kit works. And like stated above, sense and aosp radio partitions are different. Being hung up on an asop ROM while flashing a sense ruu can not be good.
Sent from my One X using xda premium
---------- Post added at 02:02 PM ---------- Previous post was at 01:40 PM ----------
I believe so. But if he still has asop boot image it will have to be asop radio. This might help http://forum.xda-developers.com/showthread.php?p=27022095
Sent from my One X using xda premium
Click to expand...
Click to collapse
AOSP radio is part of the Rom. Sense radio partitions are not even touched by an aosp Rom. You can flash a sense radio while on aosp and have no effect. I don't know if hboot has issues with a borked radio partition though.
I don't know about that. I have never flashed a ruu not compatible with the rom I am using. Hopefully reflashing the radio will fix op's problem.
Sent from my One X using xda premium
That screen from what I can tell is what you get from a bad ruu flash. You need to flash an ruu to completion to fix it.
I left the phone overnight and I guess the battery died. Wont charge when I plug it in. Computer doesn't recognize it either.
What happened was my stupid cat knocked my phone off the computer desk when I was running the ruu and the cable came out. I tried to re run the ruu, but it wouldn't run. Adb commands also did nothing.
Since the phone wont charge and appears to be dead, I ended up using my phone insurance. . . should have a replacement in a few days.
fadetoblack2104 said:
I left the phone overnight and I guess the battery died. Wont charge when I plug it in. Computer doesn't recognize it either.
What happened was my stupid cat knocked my phone off the computer desk when I was running the ruu and the cable came out. I tried to re run the ruu, but it wouldn't run. Adb commands also did nothing.
Since the phone wont charge and appears to be dead, I ended up using my phone insurance. . . should have a replacement in a few days.
Click to expand...
Click to collapse
He was jealous because you spend too much time playing with your phone. I would keep a close eye on that cat for a few days.
S-Off Evita Chameleon OS
Yeah unplugging during ruu is a perfect way to brick. I usually keep my cats out of the room while running an ruu and I ruu often lol. I don't trust twrp.
Sent from my One X using xda app-developers app
exad said:
Yeah unplugging during ruu is a perfect way to brick. I usually keep my cats out of the room while running an ruu and I ruu often lol. I don't trust twrp.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Exad, you named your cat twrp?
S-Off Evita Chameleon OS
Venomtester said:
Exad, you named your cat twrp?
S-Off Evita Chameleon OS
Click to expand...
Click to collapse
lol no, my cats names are Kal-El and Lex lol
twrp is the recovery which I don't trust lol
I think twrp would be a cool name for a cat lol.
Sent from my One X using xda premium
Hi, I am currently running one of the clean roms and am having random restarts and random data connection issues. I would like to go back to stock and am wondering if I just leave my phone plugged in and run the 4.1.1 ATT RUU? Is it that simple? I am also security unlocked so I can always reenable root and flash to other roms right? (Every time I power on there is a statement about something in red lettering)
Does anyone also have the power button pushed in to where pressing the power is really hard. It used to be fine but now it is really hard to press the power button. How difficult is it to replace the power button?
If you have s-off you can go ahead and run the RUU to take your phone back to stock.
What do you mean by security unlocked though? That red text you see on boot just means your bootloader is unlocked.
Sent from my Evita
---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------
PS. You're posting in the wrong section. Questions go in the Q&A section.
Sent from my Evita
timmaaa said:
If you have s-off you can go ahead and run the RUU to take your phone back to stock.
What do you mean by security unlocked though? That red text you see on boot just means your bootloader is unlocked.
Sent from my Evita
---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------
PS. You're posting in the wrong section. Questions go in the Q&A section.
Sent from my Evita
Click to expand...
Click to collapse
Oh I just checked and you are right I have S-ON and the bootloader is unlocked. Is it still okay to proceed and still be able to root in the future and flash custom roms? Or will the new RUU lock that?
I just want to flash to completely stock to see if it solves my battery and data connection as well as radio issues.
If you run the RUU while you're s-on and SuperCID you'll brick your phone. You need to get s-off first.
Then when you want to run a custom ROM again you just need to flash a new recovery, and flash a custom ROM.
Sent from my Evita