Related
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.
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.
hi guys! can you help me how to unroot my htc one sv 4g LTE... i'm from the philippines i bought it from my friend and it is rooted.. i want o unroot so i cn update officially my device.... can you please help me? a very very thank you in advance.. God bless!
Install Supersu from the app store (unless it is on the phone already). Open it, go to settings, scroll down and you will see an option to permanently unroot. Click it and let it do its thing. May need to reboot afterwards - manually.
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
If you are updating your phone in the sense of going from 4.1.2 to 4.2.2 then you do not need to unroot your device. Though, you may lose root afterwards - but I haven't had this problem personally.
Sent from my C525c using XDA Premium 4 mobile app
thank you
Modding.MyMind said:
Install Supersu from the app store (unless it is on the phone already). Open it, go to settings, scroll down and you will see an option to permanently unroot. Click it and let it do its thing. May need to reboot afterwards - manually.
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
If you are updating your phone in the sense of going from 4.1.2 to 4.2.2 then you do not need to unroot your device. Though, you may lose root afterwards - but I haven't had this problem personally.
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thank you for your reply..... i'll try it now.... i hope it won't brick my phone... i'm now in 4.0.4 ICS. and i want to upgrade it to 4.2.2 i saw a thread that there's an official update of it. but first i must unroot my phone.....thank you so much for your response.. God bless!!!
If you are S-On then you don't have to unroot. Just relock your bootloader.
But first, exactly what state is your phone currently in? S-Off? S-On? Bootloader unlocked? Bootloader locked? If you do not know then go into your settings and go to where your battery settings are. There is an option for fast boot. Make sure it is unchecked. Not shut off your device. Once it is shut off press and hold your volume down button, then press and hold your power button. Hold both until a white screen (your HBoot) shows up then release. If your bootloader is unlocked it will say unlocked at the top. If it is locked it will say locked. Also, if it says relocked then this means at one point the Bootloader had been unlocked but then relocked later on. Also check to see if it says whether or not you are S-On or S-Off. Let me know.
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 01:16 PM ---------- Previous post was at 01:12 PM ----------
To exit out of this screen use your up and down volume buttons to scroll to 'fastboot' then press the power button to select it. You will enter the fastboot screen. Scroll using your volume buttons to 'reboot' and press the power button.
Sent from my C525c using XDA Premium 4 mobile app
Modding.MyMind said:
If you are S-On then you don't have to unroot. Just relock your bootloader.
But first, exactly what state is your phone currently in? S-Off? S-On? Bootloader unlocked? Bootloader locked? If you do not know then go into your settings and go to where your battery settings are. There is an option for fast boot. Make sure it is unchecked. Not shut off your device. Once it is shut off press and hold your volume down button, then press and hold your power button. Hold both until a white screen (your HBoot) shows up then release. If your bootloader is unlocked it will say unlocked at the top. If it is locked it will say locked. Also, if it says relocked then this means at one point the Bootloader had been unlocked but then relocked later on. Also check to see if it says whether or not you are S-On or S-Off. Let me know.
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 01:16 PM ---------- Previous post was at 01:12 PM ----------
To exit out of this screen use your up and down volume buttons to scroll to 'fastboot' then press the power button to select it. You will enter the fastboot screen. Scroll using your volume buttons to 'reboot' and press the power button.
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sir... thank you again for your great tutotrial.. i followed your steps.... in the top it says locked..... and it says S-off
but before i did that i tried to update my HTCone sv.... the unit downloaded the file but upon installing for about 1/3 it pauses and shows a baterry like image and a red triangle on the side top of it.. what does it means..?
Hold up... You are 'locked'? Or are you 'relocked'? If you are indeed 'locked' then please tell me what K2_ device you have and how you went about gaining 'locked'.
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 12:46 PM ---------- Previous post was at 12:41 PM ----------
The update will fail if you have any missing system files or apps. Meaning, since you are S-OFF do you at any point remove some system apps and/or files to free up space or simply because you did not want them? If so you MUST restore them back on to your device. The OTA implements a patch verification and if something is missing from your device as stated above it will simply abort the OTA update. If you have a backup with all your stuff before you started tampering with your phone then restore your device with that backup and you will be able to proceed with the ota. In addition, you are S-OFF so it is not necessary for you to lock the bootloader when updating your device but if you wish to have it locked anyways then that is fine as well. Just make sure your bootloader is unlocked when you restore your device with your backup.
Sent from my C525c using XDA Premium 4 mobile app
Modding.MyMind said:
Hold up... You are 'locked'? Or are you 'relocked'? If you are indeed 'locked' then please tell me what K2_ device you have and how you went about gaining 'locked'.
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 12:46 PM ---------- Previous post was at 12:41 PM ----------
The update will fail if you have any missing system files or apps. Meaning, since you are S-OFF do you at any point remove some system apps and/or files to free up space or simply because you did not want them? If so you MUST restore them back on to your device. The OTA implements a patch verification and if something is missing from your device as stated above it will simply abort the OTA update. If you have a backup with all your stuff before you started tampering with your phone then restore your device with that backup and you will be able to proceed with the ota. In addition, you are S-OFF so it is not necessary for you to lock the bootloader when updating your device but if you wish to have it locked anyways then that is fine as well. Just make sure your bootloader is unlocked when you restore your device with your backup.
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hello sir... K2_U PVT sir..... i don't know how i get locked.. i don't even know what is that sir... i just bought it to my friend... and i don't know sir.. if there have been deleted files.... i'm new in HTC... this is my first time im going to use HTC sir.. and how do i get the OTA update sir..? sorry for many stupid questions... but im really glad that you are there to answer them... thank you! and God bless!!
baista23 said:
hello sir... K2_U PVT sir..... i don't know how i get locked.. i don't even know what is that sir... i just bought it to my friend... and i don't know sir.. if there have been deleted files.... i'm new in HTC... this is my first time im going to use HTC sir.. and how do i get the OTA update sir..? sorry for many stupid questions... but im really glad that you are there to answer them... thank you! and God bless!!
Click to expand...
Click to collapse
go into setting and scroll down to software updates then htc updates
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Assistance needed
Hello.
I have a few questions in regards the OTA update for Cricket HTC ONE SV that I have. My device is rooted and has bootloader. However, I cannot do the OTA update. It would install but then when it would reboot to perform any necessary actions, it will say failed or what not. I am not sure if it's because my device is rooted.
I powered down the handset. I then held the Volume Down jey and Power button and was shown the HBOOT screen. The information below is listed:
Tampered
Unlocked
K2-PLC_CL PVT Ship S-ON RL
So I do not know what to do. I am kinda new at this and I want that OTA Update, becaue I am assuming it's better than the 4.1.2 version I currently have.
I see that there is a new Venom ROm available for this phone which I might consider, but it needs the OTA 4.2.2 to be installed I think. Also, do I need to flash to the Stock Rom to perform this OTA update?
If you can walk me through it, I would really appreciate it.
quickser4u619 said:
Hello.
I have a few questions in regards the OTA update for Cricket HTC ONE SV that I have. My device is rooted and has bootloader. However, I cannot do the OTA update. It would install but then when it would reboot to perform any necessary actions, it will say failed or what not. I am not sure if it's because my device is rooted.
I powered down the handset. I then held the Volume Down jey and Power button and was shown the HBOOT screen. The information below is listed:
Tampered
Unlocked
K2-PLC_CL PVT Ship S-ON RL
So I do not know what to do. I am kinda new at this and I want that OTA Update, becaue I am assuming it's better than the 4.1.2 version I currently have.
I see that there is a new Venom ROm available for this phone which I might consider, but it needs the OTA 4.2.2 to be installed I think. Also, do I need to flash to the Stock Rom to perform this OTA update?
If you can walk me through it, I would really appreciate it.
Click to expand...
Click to collapse
The Viper Rom is for K2_U and currently having support being added for K2_UL. It is not fitted for K2_PLC_CL or K2_CL.
Being rooted is not your issue for the OTA. The OTA is most likely failing because you are S-On with an unlocked bootloader and/or are trying to install the update using a custom recovery when you must use your stock recovery.
If you do decide to relock your bootloader make sure you flash your stock recovery and stock boot.img for security reasons.
I doubt you are missing any system apps because you are S-On which means you most likely still have write protection enabled on your device that prevents such changes. However, if you do have any removed system apps then this can cause a problem as well for the update as the update uses patches and also compares the md5sum between the original apk and the new patch. If they do not match it aborts. If one is missing it aborts.
Sent from my C525c using Tapatalk
How can I revert everything back to its factory condition so that way I can update via OTA and perhaps have my phone cleared of any bugs that exist? I know I have to do the stock recovery, but I forgot the procedure and do not know what files to use for this. I need like a step by step guide to revert everything back to normal. Is that something you can assist me with. Something that can help me in my situation?
Modding.MyMind said:
The Viper Rom is for K2_U and currently having support being added for K2_UL. It is not fitted for K2_PLC_CL or K2_CL.
Being rooted is not your issue for the OTA. The OTA is most likely failing because you are S-On with an unlocked bootloader and/or are trying to install the update using a custom recovery when you must use your stock recovery.
If you do decide to relock your bootloader make sure you flash your stock recovery and stock boot.img for security reasons.
I doubt you are missing any system apps because you are S-On which means you most likely still have write protection enabled on your device that prevents such changes. However, if you do have any removed system apps then this can cause a problem as well for the update as the update uses patches and also compares the md5sum between the original apk and the new patch. If they do not match it aborts. If one is missing it aborts.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
@quickser4u619
When you attempted to updates your device with this OTA were you doing it by use of your custom recovery whether CWM or TWRP?
If yes, then what you can do is grab hold of your stock recovery image and flash it.
To flash it you must plug your device in to your PC.
Open the CMD window and change directories to where your proper adb/fastboot files are located. If using linux then those files should already be part of your path and will act immediately upon being called.
Run following command:
Code:
adb devices
This will try to establish connection from the pc to your device. If successful it will display your device serial number. If it fails it will return with a blank result.
If successful then go ahead and insure your stock recovery image is located where your proper adb/fastboot files are located at to make the next procedure simple. Rename your recovery image to stockrecovery.img. Continue with the next command:
Code:
fastboot flash [COLOR="red"]recovery[/COLOR] [B]stockrecovery.img[/B]
When it is done you should now have your stock recovery restored back to your device. At this point go ahead and reattempt to install your OTA and hopefully this will be the only thing needed from you to accomplish your task which is to bump up to 4.2.2.
Sent from my C525c using Tapatalk
Hi guys,
I'm newbie about android and please do not be angry to me for this question. I was read lots of topics from xda and another forums but I can't find anything.
I have AT&T HTC One X and i was happy with my phone. Maybe one year ago I rooted my phone and install ATT Stock Root - 3.18.502.6 - JB 4.1.1.zip. So, i followed instructions from xda's web site and everything was fine.
Last two weeks my phone starts to restarts it self. So, I decide to install everything again and open my phone in recovery mode with TWRP and wipe all data. (I don't have any backup of my original data)
I have TRWP's 2.7.1.0 version and I tried to install ATT Stock Root - 3.18.502.6 - JB 4.1.1.zip because I install it one year ago and it works fine. It installs fine but when I press restart my phone stuck at Quietly Brilliant screen and after 2 minutes my phone restarts it self.
Also I can't s-off my phone. I have unlock code bin and I applied it to my phone but something was wrong.
So please can any one help me please. I don't know why my phone acts like that.
Thanks in advance.
Ok so I know your a newbie but do you know your firmware is way out of date? We now have firmware for at&t that is at least 4 realises older than the current. I would say upgrade to a new ROM and firmware. If you don't wish to upgrade I have to ask what kernel you are using?
What he said. Also, did you flash the boot.img from the rom zip via fastboot? As you are s-on, you must perform that additional step.
I suggest he reads timaaas thread. Sounds to me like he should run a ruu to which he can still obtain s off.
Well thanks for suggestions, but I don't know what is the sequence for installing new firmware, rom and kernel. Could you guys please explain the it.
marknoll said:
I suggest he reads timaaas thread. Sounds to me like he should run a ruu to which he can still obtain s off.
Click to expand...
Click to collapse
No, no, no! He can't run an RUU while s-on because it'll brick his phone. I know you mean well but you need to increase your own knowledge before you can start giving advice here, I've seen at least a few times where you've given advice that would result in a brick. I'm sure you don't want that on your conscience.
Sent from my Evita
---------- Post added at 08:56 PM ---------- Previous post was at 08:53 PM ----------
ahrar said:
Well thanks for suggestions, but I don't know what is the sequence for installing new firmware, rom and kernel. Could you guys please explain the it.
Click to expand...
Click to collapse
You more than likely only needed to flash the boot.img from the ROM zip by fastboot. Flash the ROM, then flash the boot.img, and your phone should boot up. Once you're all booted you need to get s-off. Look in my guide thread in my signature for instructions.
Sent from my Evita
timmaaa said:
No, no, no! He can't run an RUU while s-on because it'll brick his phone. I know you mean well but you need to increase your own knowledge before you can start giving advice here, I've seen at least a few times where you've given advice that would result in a brick. I'm sure you don't want that on your conscience.
Sent from my Evita
---------- Post added at 08:56 PM ---------- Previous post was at 08:53 PM ----------
You more than likely only needed to flash the boot.img from the ROM zip by fastboot. Flash the ROM, then flash the boot.img, and your phone should boot up. Once you're all booted you need to get s-off. Look in my guide thread in my signature for instructions.
Sent from my Evita
Click to expand...
Click to collapse
No no. I didn't mean for him to run ruu. I suggested he read your thread to see what requisite is needed to do so. I wasn't suggestioning to ruu..omg no. Lol
marknoll said:
No no. I didn't mean for him to run ruu. I suggested he read your thread to see what requisite is needed to do so. I wasn't suggestioning to ruu..omg no. Lol
Click to expand...
Click to collapse
But that's exactly what you said:
Sounds to me like he should run a ruu...
Click to expand...
Click to collapse
Sent from my Evita
Yes. Run a ruu if he meets the requirementz
marknoll said:
Yes. Run a ruu if he meets the requirementz
Click to expand...
Click to collapse
But he doesn't, and that's the point. Why say that when it's clear that he doesn't meet the requirements? What if he took your advice and ran the RUU? Would you have bought him a nice new phone? Am I making sense here?
Sent via Bacon
Yep