So i was kinda scared but i knew this day would come, VZW is pushing a update to all rezounds with H-boot 2.11. Concitering we dont have S-off yet this usually wouldnt be a problem but H-boot 2.11 breaks temp root. I have been using it for a while and it fails to push SU.
Just a warning so no one gets stuck without root
What about the people who are fully unlocked with perm root ? What happens if we run the update
Update failed in recovery for me. I've deleted some bloat though.
Sent from my ADR6425LVW using XDA App
Easton999GS said:
What about the people who are fully unlocked with perm root ? What happens if we run the update
Click to expand...
Click to collapse
As far as I can tell, the update will not run. I let it download to my Rezound and then it auto-restarted after 3 minutes. Booted into recovery and said update failed. I rebooted from recovery and once booted up, I got a message saying "No new software update available" or something to that effect. Clicked "Finish" and since then, my phone has been working like before. From what I just experienced, there is no harm to your phone if you let it try to install, but nothing will happen either, so there is no benefit.
k_flan said:
Update failed in recovery for me. I've deleted some bloat though.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
were you unlocked?
i dont think it should effect anyone who is unlocked but dont hold me to that
You can only update radios when your device is locked or relocked. The ? Is can we unlock after we are on hboot 2.11
Mechadan said:
As far as I can tell, the update will not run. I let it download to my Rezound and then it auto-restarted after 3 minutes. Booted into recovery and said update failed. I rebooted from recovery and once booted up, I got a message saying "No new software update available" or something to that effect. Clicked "Finish" and since then, my phone has been working like before. From what I just experienced, there is no harm to your phone if you let it try to install, but nothing will happen either, so there is no benefit.
Click to expand...
Click to collapse
try putting stock recovery on the device.
---------- Post added at 06:14 PM ---------- Previous post was at 06:13 PM ----------
Easton999GS said:
You can only update radios when your device is locked or relocked. The ? Is can we unlock after we are on hboot 2.11
Click to expand...
Click to collapse
This is what I'm waiting to know.
Easton999GS said:
You can only update radios when your device is locked or relocked. The ? Is can we unlock after we are on hboot 2.11
Click to expand...
Click to collapse
i would assume so because the unlock is directly from HTC to anser the second part of your Q
andybones said:
try putting stock recovery on the device.
---------- Post added at 06:14 PM ---------- Previous post was at 06:13 PM ----------
This is what I'm waiting to know.
Click to expand...
Click to collapse
I am rather new... I'm not entirely sure:
1) How to get stock recovery back, haha.
2) If I even want to get it back. If HBoot is updated by this OTA, I don't know that I want it running and screwing up my root. Is that possible if I am unlocked and perm-rooted?
To be clear, I am willing to experiment for your guys' benefit, but would just like to be sure what I am getting myself into.
werdna87 said:
were you unlocked?
i dont think it should effect anyone who is unlocked but dont hold me to that
Click to expand...
Click to collapse
Yeah, unlocked. I'd be surprised if unlocked breaks it though. Im guessing its that I'm running AR recovery or because I've messed with system apps.
Sent from my ADR6425LVW using XDA App
werdna87 said:
i would assume so because the unlock is directly from HTC to anser the second part of your Q
Click to expand...
Click to collapse
If that is the case then we could get root back and get back on cusom recovery, hopefully someone who has accepted the OTA will see if they can unlock it.
I'm trying to get back to stock and test to see if we can unlock but It takes forever to get back to stock.
Mechadan said:
I am rather new... I'm not entirely sure:
1) How to get stock recovery back, haha.
2) If I even want to get it back. If HBoot is updated by this OTA, I don't know that I want it running and screwing up my root. Is that possible if I am unlocked and perm-rooted?
To be clear, I am willing to experiment for your guys' benefit, but would just like to be sure what I am getting myself into.
Click to expand...
Click to collapse
I'm not entirely sure but if you are willing to experiement that would be huge.
it does update to 2.11 hboot, so the question is can you then do the unlock and root again.
i think you need to be on stock recovery to the update to take.
but dont hold me to any of this.
andybones said:
I'm not entirely sure but if you are willing to experiement that would be huge.
it does update to 2.11 hboot, so the question is can you then do the unlock and root again.
i think you need to be on stock recovery to the update to take.
but dont hold me to any of this.
Click to expand...
Click to collapse
OK, well I can't do anything here from work, so when I get settled at home later tonight, I will see what I can do. I don't mind losing root until someone can figure out a workaround for those stuck with 2.11 hboot, mainly because a custom ROM is the only benefit I use from root at the moment. I can't figure out tethering to my Transformer Prime for the time-being anyhow, so losing Nils' ROM is a hit I'm willing to take for a bit.
If someone else does not figure out what you need before later tonight, I will do what I can.
By the way, it would help if you set up some steps for me. Like, do you want me to restore stock recovery, then check to see if stock recovery and custom ROM lets me install the update, then if it doesn't work, go back to stock everything and see if it works, then if it doesn't work go to relocked and see if it works? Just lay out each operation you want me to do to test your theories. I know far too little to be making up my own procedures. Inevitably, I'll finish and people will say, "Well, what about... and what about..."
I just don't want to waste my time or yours.
just letting everyone know, if you were one of those ppl who ran the ruu leak and get a mainversion error, your ****ed. you cant update and you cant change the text cause then it fails the sig check
Easton999GS said:
just letting everyone know, if you were one of those ppl who ran the ruu leak and get a mainversion error, your ****ed. you cant update and you cant change the text cause then it fails the sig check
Click to expand...
Click to collapse
So this happened to you?
con247 said:
So this happened to you?
Click to expand...
Click to collapse
yep yep.... we can't RUU back to stock, or apply this new update... we need the actuall RUU file for this new update before we will be able to do anything.
con247 said:
So this happened to you?
Click to expand...
Click to collapse
no but i know it wont work. it will fail when it tries to update the kernel part. i also cant even restore an RUU because the RUU gets the mainver error, and yes i relocked the phone before i tried to restore.
Easton999GS said:
just letting everyone know, if you were one of those ppl who ran the ruu leak and get a mainversion error, your ****ed. you cant update and you cant change the text cause then it fails the sig check
Click to expand...
Click to collapse
thank you for this.
---------- Post added at 06:51 PM ---------- Previous post was at 06:49 PM ----------
jskolm said:
yep yep.... we can't RUU back to stock, or apply this new update... we need the actuall RUU file for this new update before we will be able to do anything.
Click to expand...
Click to collapse
u can RUU back to stock pulling the rom.zip from the stock ruu
Damn guys... sorry about that.
Related
My phone was rooted w/ s-off, I had to take it to the Verizon store today for a warranty replacement so I unrooted and got it back to s-on before I went. They gave me a new phone and when I got home I noticed they had applied the OTA already before I left the store, must have been when they were activating the phone and new SIM.
So I have 2.11.605.9 and I try to run Revolutionary to get s-off and root and it stops saying it could not get root.
Am I stuck waiting for the Revolutionary tool to be updated or is there something else I can do?
rberry88 said:
My phone was rooted w/ s-off, I had to take it to the Verizon store today for a warranty replacement so I unrooted and got it back to s-on before I went. They gave me a new phone and when I got home I noticed they had applied the OTA already before I left the store, must have been when they were activating the phone and new SIM.
So I have 2.11.605.9 and I try to run Revolutionary to get s-off and root and it stops saying it could not get root.
Am I stuck waiting for the Revolutionary tool to be updated or is there something else I can do?
Click to expand...
Click to collapse
So when you say you can't get "root" do you mean it won't flash their custom bootloader?
Have you tried using the manual method?
Has anyone else tried this to confirm if the exploit has been patched?
I guess I could be a guinea pig and try it out for myself. Of course, if I can't root that will really put a damper on my ROM update
orkillakilla said:
So when you say you can't get "root" do you mean it won't flash their custom bootloader?
Have you tried using the manual method?
Has anyone else tried this to confirm if the exploit has been patched?
I guess I could be a guinea pig and try it out for myself. Of course, if I can't root that will really put a damper on my ROM update
Click to expand...
Click to collapse
Read it does patch it, so I won't be trying it lol
Sent from my ADR6400L using XDA App
Has anyone tried the bootloader unlocker through the HTCdev website? www.htcdev.com
rberry88 said:
Has anyone tried the bootloader unlocker through the HTCdev website? www.htcdev.com
Click to expand...
Click to collapse
Why don't you try it.
Sent from my ADR6400L using XDA App
Ok, took the plunge and tried the htcdev.com method but the Thunderbolt is not supported. It returns a "token" that is necessary to complete the unlock process that says "invalid token - device not supported". I guess I have to wait for the folks at Revolutionary to get root back.
If you don't mind having to wipe your phone... You can rooted and on 2.11.605.9... see -> http://forum.xda-developers.com/showpost.php?p=20434629&postcount=36
So if I unroot and my phone takes the latest 2.11.605..9 update, all I have to do is flash the 2.11.605.5 RUU, put phone into airplane mode as soon as it boots, then I can root again?
.9 will lock the boot loader so i realy don't follow what you are saying
Heres how i got root back using .9 radio and .5 oem
http://forum.xda-developers.com/showthread.php?t=1399044
ghamden said:
.9 will lock the boot loader so i realy don't follow what you are saying
Heres how i got root back using .9 radio and .5 oem
http://forum.xda-developers.com/showthread.php?t=1399044
Click to expand...
Click to collapse
So, is there somewhere I can download .5? And then I rename it to PG05IMG.zip so it updates from the locked bootloader which should get me back to .5?
Here is the file i used
http://www.multiupload.com/WES9PABEQF
ghamden said:
Here is the file i used
http://www.multiupload.com/WES9PABEQF
Click to expand...
Click to collapse
Worked like a charm, powered off and booted with that file on my sdcard, it updated (or downgraded in this case) and then I was able to run Revolutionary and now have root and s-off again. Thanks.
http://forum.xda-developers.com/showthread.php?p=20401056#post20401056
Similar topic. Locked bootloader. Still no solution. :l
ghamden said:
Here is the file i used
http://www.multiupload.com/WES9PABEQF
Click to expand...
Click to collapse
IT WORKED! Thank YOU SO MUCH!!!
Back to ROOT!
YAII!
2.11.605.9 Doesn't lock the bootloader if you accept it OTA. It does however patch the ZergRush exploit preventing the ability to root.
erishasnobattery said:
2.11.605.9 Doesn't lock the bootloader if you accept it OTA. It does however patch the ZergRush exploit preventing the ability to root.
Click to expand...
Click to collapse
You are correct. The problem I, and a few others, were having was we were unrooted and s-on. The OTA was applied to an already locked bootloader and thus couldn't run Revolutionary to get our phones rooted or s-off. No way I was going to chance taking my phone to the Verizon store with s-off for a warranty issue.
Every time I download 2.11.605.9, the zip is corrupted. I have tried MultiUpload and other sites. Need Help
---------- Post added at 11:04 PM ---------- Previous post was at 10:53 PM ----------
Every time I download 2.11.605.9, the zip is corrupted. I have tried MultiUpload and other sites. Need Help
Hey everyone,
Noob here. I've checked out a bunch of stuff on the forums and it seems like the only solution to the OTA 2.11.605.9 blocking of revolutionary is to downgrade to .5
However, I've had my tb for a while and don't want to wipe my contacts and data. Is there a workaround for this? If not, would it be reasonable to expect some kind of fix for the revolutionary method in the near future?
Thanks
I tried to follow what everyone was saying but don't know the Tbolt well enough. Can someone post a step by step on how to get root and S-off with a Tbolt I bought last week? I understand it to have the 2.11.605.9 software...
letmehearucaw said:
I tried to follow what everyone was saying but don't know the Tbolt well enough. Can someone post a step by step on how to get root and S-off with a Tbolt I bought last week? I understand it to have the 2.11.605.9 software...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1401959
Good evening. I am new to HTC phones (and unlocked phones in general). I am having trouble flashing a kernel using a PH98IMG.zip file. When it goes in the bootloader I get an error that says "Main Version Older Update Failed." I am able to flash a boot.img via Fastboot, but I am receiving wifi errors. Does anyone have any ideas?
Thanks in advance.
Chris
CHRIS42060 said:
Good evening. I am new to HTC phones (and unlocked phones in general). I am having trouble flashing a kernel using a PH98IMG.zip file. When it goes in the bootloader I get an error that says "Main Version Older Update Failed." I am able to flash a boot.img via Fastboot, but I am receiving wifi errors. Does anyone have any ideas?
Thanks in advance.
Chris
Click to expand...
Click to collapse
What kernel are you trying to flash?
Sent from my ADR6425LVW using XDA App
How weird that someone else would post the same issue I'm having, when I've flashed several kernels in the past few days with no problems.
At some point, I've flashed every Sense-based kernel in the Rezound dev section. And now, for some strange reason, I'm getting the error described above.
Any ideas?
Thanks,
The Beeb
I'm going to guess you flashed the leak? If you did here is another thread to check out http://forum.xda-developers.com/showthread.php?t=1446273
sent from my newly unlocked Rezound
nosympathy said:
What kernel are you trying to flash?
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
I think I have tried just about every stock kernel, and gotta the error.
pwned3 said:
I'm going to guess you flashed the leak? If you did here is another thread to check out http://forum.xda-developers.com/showthread.php?t=1446273
sent from my newly unlocked Rezound
Click to expand...
Click to collapse
No I never flashed the leak. Do you think that fixed would work? Well guess I should say if it doesn't work do you think it will cause any harm to the phone's system?
Thanks again.
Sent from my ADR6425LVW using Tapatalk
CHRIS42060 said:
I think I have tried just about every stock kernel, and gotta the error.
No I never flashed the leak. Do you think that fixed would work? Well guess I should say if it doesn't work do you think it will cause any harm to the phone's system?
Thanks again.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Try flashing the kernel in fastboot.
I am having the same issue now also after I flash the BAMF's latest ROM. Their update log says they updated to the new base, and after that I can't to flash anything in hboot anymore. I can still ADB push the boot.img but no flashing. I also tried to revert to complete stock by flashing the RUU and get the same thing. It's says my system is newer and won't flash.
jskolm said:
I am having the same issue now also after I flash the BAMF's latest ROM. Their update log says they updated to the new base, and after that I can't to flash anything in hboot anymore. I can still ADB push the boot.img but no flashing. I also tried to revert to complete stock by flashing the RUU and get the same thing. It's says my system is newer and won't flash.
Click to expand...
Click to collapse
So you can't fastboot flash boot <boot.img> from your PC??
MrSmith317 said:
So you can't fastboot flash boot <boot.img> from your PC??
Click to expand...
Click to collapse
Sorry, yes, I can do that.
That's the only way that I can push a boot.img now. I know the kernel devs have a way to flash their kernel in recovery then automatically push you into hboot to flash the PH98IMG.zip file with the boot.img inside it. Flashing anything in fastboot now results in the error message above except for the BAMF ROM.
Having the same problem after updating to bamf cubed 102.
My main version sig updated when I flashed the leaked kernel. fastboot should always work, and would have saved me from the dumb mistake had i flashed in fastboot to begin with.
But my guess is that somehow u flashed a PH98IMG.zip file that was the leaked kernel.
I'm not sure how to find out what version the sig thinks it is running but since I know what the leak was, I can edit the .txt file in the PH98IMG.zip and make it work, like said in the thread.
Well this sucks! It definitely started when I flashed the new bamf cubed rom. So does this mean I can never flash a boot.img unless I do it with fastboot and a pc? So I cant just put the file on my sdcard and reboot into fastboot? Can this be fixed? Thanks!!!!
maniac2k said:
Well this sucks! It definitely started when I flashed the new bamf cubed rom. So does this mean I can never flash a boot.img unless I do it with fastboot and a pc? So I cant just put the file on my sdcard and reboot into fastboot? Can this be fixed? Thanks!!!!
Click to expand...
Click to collapse
The same issue also started for me when I flashed BAMF Cubed. Looks like dsb mention on the BAMF Cubed Rom thread that with S-On we can't easily change the base that was changed this with update. Looks like we will be using Fastboot until more developers use the newer version. Glad to know its not something I managed to screw up lol.
http://forum.xda-developers.com/showthread.php?t=1443328&page=5
Thanks a lot for all of the help everyone.
You might be able to replace the android-info.txt in the PH98IMG.zip with the one from dsb's kernel, making the hboot think you're not flashing backwards. Not positive if that works though.
skourg3 said:
You might be able to replace the android-info.txt in the PH98IMG.zip with the one from dsb's kernel, making the hboot think you're not flashing backwards. Not positive if that works though.
Click to expand...
Click to collapse
This does work, but you have to pull the file from his cube1.02 ROM not from his kernel.
jskolm said:
This does work, but you have to pull the file from his cube1.02 ROM not from his kernel.
Click to expand...
Click to collapse
How exactly is this done?
**** someone needs to tell dsb or whoever to put it back to the old version. If your mainver gets updated, you can't run RUUs. So you could be stuck with a brick until we get the official ICS RUU
con247 said:
**** someone needs to tell dsb or whoever to put it back to the old version. If your mainver gets updated, you can't run RUUs. So you could be stuck with a brick until we get the official ICS RUU
Click to expand...
Click to collapse
YEP! I can't RUU back to stock at this point... it's ok... I will deal with it until we get an official ICS RUU, but it's just a bummer incase something does actually go wrong with my Rezound.
con247 said:
**** someone needs to tell dsb or whoever to put it back to the old version. If your mainver gets updated, you can't run RUUs. So you could be stuck with a brick until we get the official ICS RUU
Click to expand...
Click to collapse
my main sig updated, and it is far from a brick..
Infact it's not a very big deal at all, it's something that should be avoided by all costs I absolutely 100% agree with that.
but the phone will still be able to use RUU's, the update will be ICS anyway..
This is confirmed by jcase.
I completely agree with stopping this from happening to anyone else. But no need to scare them by saying your phone is a brick because the sig updated.
How exactly do you consider the phone to be a brick anyway? JW, not trying to be an a-hole by any means here.
the only problem is the need to change the PB98IMG.zip .txt file and cant use an RUU until we get an OTA, ICS will be the next OTA update anyway.
---------- Post added at 01:45 PM ---------- Previous post was at 01:43 PM ----------
jskolm said:
YEP! I can't RUU back to stock at this point... it's ok... I will deal with it until we get an official ICS RUU, but it's just a bummer incase something does actually go wrong with my Rezound.
Click to expand...
Click to collapse
Just Curious, what do you need the RUU for?
do you use Stock ROM?
also, can't you just pull the rom.zip from ruu then rename to PB98IMG.zip and replace the.txt?
andybones said:
my main sig updated, and it is far from a brick..
Infact it's not a very big deal at all, it's something that should be avoided by all costs I absolutely 100% agree with that.
but the phone will still be able to use RUU's, the update will be ICS anyway..
This is confirmed by jcase.
I completely agree with stopping this from happening to anyone else. But no need to scare them by saying your phone is a brick because the sig updated.
How exactly do you consider the phone to be a brick anyway? JW, not trying to be an a-hole by any means here.
the only problem is the need to change the PB98IMG.zip .txt file and cant use an RUU until we get an OTA, ICS will be the next OTA update anyway.
---------- Post added at 01:45 PM ---------- Previous post was at 01:43 PM ----------
Just Curious, what do you need the RUU for?
do you use Stock ROM?
also, can't you just pull the rom.zip from ruu then rename to PB98IMG.zip and replace the.txt?
Click to expand...
Click to collapse
Agreed that it's FAR from bricked, but it's just more of an annoyance. You can't use the easy flash script that all the kernel devs and ROM devs are using now. You have to manually update the .txt file yourself inoder to be able to flash it. (Or adb push it from a computer)
And yes you are correct about the RUU, you can probably just replace the txt file in it with the moded version (I didn't think of trying that even though I am doing that will the kernels that I have download from here).
I was only trying to RUU to see if it would undo what was done... just for ease of use for me. I like to browse these forums from tapatalk and download a new kernel when it's released (hasn't been for a while, come on devs ) and test it out. I can't do that now without a computer. So I was just trying to undo that is all.
Hey guys,
I was running the latest Viper rom. Every great once in a while the phone would just turn off. I could get it back fine and this happened about 5-6 times. Today the phone got stuck in a boot loop. I figured something went wrong.
I attempted to restore the phone to stock using the RUU thread found here: http://forum.xda-developers.com/showthread.php?t=2152993
I restored it once fine, said it was good. Phone only rebooted over and over. The HTC logo came up 3-4 times then screen went blank. So I flashed again. Same thing, nothing.
Now I had been playing around and think I updated my radio. Now the RUU from that thread above says it cannot upgrade my phone. I can get to fastbook and lock and unlock the bootloader. I did install latest TWRP but it never enters recovery. I had hoped to just install a basic rom from the 2.04 update and be done. But I cannot get into recovery.
I'm stuck and don't know what else to do. Is there and RUU file like the one above for the new 2.04?
I still think something else is wrong with this phone. Somehow doubt VZW will take it back and exchange.
S-ON
Phone displays HBOOT-1.33.0001
RADIO-1.01.01.0110
Any ideas what I can do next please?
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Tersanyus said:
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Click to expand...
Click to collapse
Did you take the verizon update as you mentioned 2.04? If you did you will have to wait a bit yet to root again. Your only option would be stock verizon. Their software update basically closed the previously open window. If not...You HAVE updated radio per the # you posted, not sure if that really matters with regard to recovery. It seems like you have compounded many issues. I would try relocking bootloader and flash stock RUU again. Try to get back to stock verizon. If that's a no go, would try reflashing old radio and try stock ruu. How are you getting to try bootloader/recovery, turning on phone holding down vol button? Last ditch if it's says s-on and locked, I think you would be ok to try for a new phone.
I did not take the OTA from Verizon. I never got any prompt for an update. I did the updates for Viper that turned I think just turned that off.
Getting to bootloader is fine. I can lock it and unlock it fine. I know the RUU only loads if locked. I know recovery can only be installed if unlocked I believe. And yes I do that from vol down plus power button.
If I use newest TWRP recovery just gives a whole bunch of colored lines. If I try 2.4.0.0 I can see TWRP come up briefly then the phone reboots again.
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Tersanyus said:
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Click to expand...
Click to collapse
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
---------- Post added at 10:39 AM ---------- Previous post was at 09:48 AM ----------
rootntootn said:
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
Click to expand...
Click to collapse
Can you get to fastboot? adb can communicate with the phone? Says in red fastboot usb? Also how are you doing RUU, assuming your using executable from your pc? Forgot to ask..
Yes I can get to fastboot fine. I do a "fastboot devices" and it is read. adb doesn't seem to do anything though. The RUU is the .exe I found.
For the cid I did the old one so mine reads all 1's. I didn't think I could so the new cid as I cannot boot into Android at all.
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
rootntootn said:
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Click to expand...
Click to collapse
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
BTW There was nothing wrong with your phone, it's just that when you restored, you needed to flash the boot.img from your rom that you restored. It was most likely a kernel issue that we could correct with viper.
It sounds like you just need to install the matching rom and boot.img. If you're s off, just fastboot flash the boot.img for whatever rom you currently have installed. For the OTA update, you can install the radios without an RUU if you're s off.
I ran for several hours and several reboots on the RUU .exe file. When I downloaded a custom rom from http://forum.xda-developers.com/showthread.php?t=2150262 - That fan fine for an hour or so. Then boot loop over and over again. Thankfully I made a backup in twrp. I restored that and all is well.
I can't stand this factory rom, the part that really annoys me, besides the VZW bloat, is the recent apps button. For over a year with other HTC's I am used to making that the menu button. Had that in the custom rom.
So it looks like that rebooting loop just means I need to fastboot the boot.img?
I go back to the rom I linked about and fastboot the boot.img. I really liked viper rom but am going to stick to stock that is rooted and debloated.
My cid is all 1's since I did that before all this OTA came out. I did that about 3 weeks ago the day I got the phone.
Thanks for the tips. I'll let you know what happens when I go back to the rom above.
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Sorry about the 2's info but read that the older cid apk would no longer work (from thread below) and myself put on the new one which yields the all 2's. Bottom line, glad you made progress, hopefully problem resolved
http://forum.xda-developers.com/showthread.php?t=2109862
I was running mean rom and flashed back to factory now it says my phone in not rooted when I tried to flash back. It says unlocked and now it is s-on. im not sure what happened or how to fix it so any help would be greatly appreciated.
Thanks Dave
What exactly did you do to get back to stock? Need more information. RUU?
Delakit said:
What exactly did you do to get back to stock? Need more information. RUU?
Click to expand...
Click to collapse
I had a back up and flashed it then changed some apps the tried to flash meanbean back and it would not flash it or anything else. im not sure on the ruu but my hboot is 1.12 if that helps. when I try to power down it says I have no root install su.
Do you still have custom recovery? If so, do you still have the su zip you flashed when first rooting?
Sent from my EVO using xda premium
---------- Post added at 12:23 AM ---------- Previous post was at 12:22 AM ----------
What do you mean "now s-on"? You were s-off and now not? I Dont know how that could happen
Sent from my EVO using xda premium
scottspa74 said:
Do you still have custom recovery? If so, do you still have the su zip you flashed when first rooting?
Sent from my EVO using xda premium
---------- Post added at 12:23 AM ---------- Previous post was at 12:22 AM ----------
What do you mean "now s-on"? You were s-off and now not? I Dont know how that could happen
Sent from my EVO using xda premium
Click to expand...
Click to collapse
yes I have twrp 2.5.0.0 but no on the su zip. I was s off and now im not, confuses me too.
Davek30 said:
I had a back up and flashed it then changed some apps the tried to flash meanbean back and it would not flash it or anything else. im not sure on the ruu but my hboot is 1.12 if that helps. when I try to power down it says I have no root install su.
Click to expand...
Click to collapse
A backup of...? Changed what apps and where? That sounds pretty irrelevant. How would it "not flash"? You would know if you RUU'd back to stock or not. You're also making it sound like you were S-OFF and now you're S-ON all of the sudden? That would be the result of an RUU route. Not sure why anything would prompt about being root or not while powering down a device.
Delakit said:
A backup of...? Changed what apps and where? That sounds pretty irrelevant. How would it "not flash"? You would know if you RUU'd back to stock or not. You're also making it sound like you were S-OFF and now you're S-ON all of the sudden? That would be the result of an RUU route. Not sure why anything would prompt about being root or not while powering down a device.
Click to expand...
Click to collapse
the backup was a factory nandroid I done when first rooted my device. im sure I was s off but now it is s on. the prompt about not being rooted was when im in twrp and trying to go to bootloader or power it off. I just want to get a rom back on it but it fails everytime and tells me im not rooted.
Davek30 said:
the backup was a factory nandroid I done when first rooted my device. im sure I was s off but now it is s on. the prompt about not being rooted was when im in twrp and trying to go to bootloader or power it off. I just want to get a rom back on it but it fails everytime and tells me im not rooted.
Click to expand...
Click to collapse
S-OFF only goes back to S-ON through RUU. So I don't think you were S-OFF but then again I know nothing of that HBOOT version. Just download the latest CWM/SU, put it in storage, flash it, reboot to ensure root was gained and then try installing MB again.
Davek30 said:
the backup was a factory nandroid I done when first rooted my device. im sure I was s off but now it is s on. the prompt about not being rooted was when im in twrp and trying to go to bootloader or power it off. I just want to get a rom back on it but it fails everytime and tells me im not rooted.
Click to expand...
Click to collapse
Unless you manually toggled the security flag back to s-on, I'm pretty sure there is no way to go from s-off to s-on. Not even RUU (other than Viperuu) revert you to s-on.
tilltheend714 said:
Unless you manually toggled the security flag back to s-on, I'm pretty sure there is no way to go from s-off to s-on. Not even RUU (other than Viperuu) revert you to s-on.
Click to expand...
Click to collapse
ok guess im not worried about that now, I just want to get a rom back on but it keeps failing?
Davek30 said:
ok guess im not worried about that now, I just want to get a rom back on but it keeps failing?
Click to expand...
Click to collapse
Can you go into TWRP? If you can, what version are you using?
tilltheend714 said:
Unless you manually toggled the security flag back to s-on, I'm pretty sure there is no way to go from s-off to s-on. Not even RUU (other than Viperuu) revert you to s-on.
Click to expand...
Click to collapse
Ah, that's right. I forgot that the process for the flag was seperate. VipeRUU is too easy =)
Davek30 said:
ok guess im not worried about that now, I just want to get a rom back on but it keeps failing?
Click to expand...
Click to collapse
it says failed to copy super user binary
tilltheend714 said:
Can you go into TWRP? If you can, what version are you using?
Click to expand...
Click to collapse
I am in twrp and that's all I can do im using 2.5.0.0
Davek30 said:
I am in twrp and that's all I can do im using 2.5.0.0
Click to expand...
Click to collapse
Ok. It sounds like you are Htcdev unlocked on hboot 1.12 and for some reason using the newest version of TWRP. Are you trying to flash an old ROM?
tilltheend714 said:
Ok. It sounds like you are Htcdev unlocked on hboot 1.12 and for some reason using the newest version of TWRP. Are you trying to flash an old ROM?
Click to expand...
Click to collapse
im trying to flash meanbean or anything at this point
Davek30 said:
im trying to flash meanbean or anything at this point
Click to expand...
Click to collapse
Let's get you back up and running then. First Downgrade TWRP to 2.3.3. Then flash this rom.
This is just to get you back to a rom. We'll see what to upgrade from there.
tilltheend714 said:
Let's get you back up and running then. First Downgrade TWRP to 2.3.3. Then flash this rom.
This is just to get you back to a rom. We'll see what to upgrade from there.
Click to expand...
Click to collapse
how do I down grade it? I tried through fast boot and had no luck
Davek30 said:
how do I down grade it? I tried through fast boot and had no luck
Click to expand...
Click to collapse
Fastboot is the only way for you since you can't get a rom with root. Why isn't it working?
tilltheend714 said:
Fastboot is the only way for you since you can't get a rom with root. Why isn't it working?
Click to expand...
Click to collapse
says main update is to old?
Hi all,
Hope this topic hasn't already been covered a million times.
Here's where I'm at,
I've unlocked by bootloader, that's all no root or custom recovery.
Now when i try to do a OTA update i get the dreaded red triangle. very frustrating!
I've tried fastboot oem lock, but it says relocked, not locked and my OTA update still won't work.
I've searched high and low for a RUU for Telstra Australia, to no avail..... DAM IT!!!
Can anyone help???
If I root, use firewater to soff the use scotty's to relock, will the OTA work then? How would i get rid of the root?
I have some understanding of fastboot, adb and flashing but I'm still a bit of a noob so go easy.
Sorry if i posted in the wrong place.
Can you get into a custom recovery or no
Check out my website for encouragement....
www.projectintercession.blogspot.com
---------- Post added at 09:42 AM ---------- Previous post was at 09:39 AM ----------
Because you could use Guru found in HTC One Development which can Lock, Relock and Unlock the bootloader. If your not rooted then you would be fine to receive the update after reflashing the stock recovery.
Check out my website for encouragement....
www.projectintercession.blogspot.com
Yeah I could if I installed one. I can get to the stock recovery?
Cjohn1200 said:
Yeah I could if I installed one. I can get to the stock recovery?
Click to expand...
Click to collapse
I believe stock recovery is what you need and all stock system files in place to take OTA. I had my Max S-OFF, unlocked and rooted and it still let me take the Kit Kat update, so really not sure why you can't, being only unlocked. Are you sure you didn't alter any other files?
Yeah I'm sure, definitely only unlocked. It's driving me crazy! I wasted hours trying to work this out.
Here's the error msg I get,
https://docs.google.com/file/d/0B9JXExeYQ7RGZEhOMWtyQTUxTUU/edit?usp=docslist_api
Cjohn1200 said:
Yeah I'm sure, definitely only unlocked. It's driving me crazy! I wasted hours trying to work this out.
Here's the error msg I get,
https://docs.google.com/file/d/0B9JXExeYQ7RGZEhOMWtyQTUxTUU/edit?usp=docslist_api
Click to expand...
Click to collapse
What is that TuneIn.apk i see in the error? Could be you are missing that and it is a file it looks for.
Hmmm, that was a factory installed app that seems to have gone missing since I unlocked the boot loader, along with the HTC torch app. I will install it and see what happens...
After a bit more reading, unlocking the boot loader clears all data from the phone. Including a few apps that are preloaded in a data folder. It appears the update looks for these app.
Cjohn1200 said:
After a bit more reading, unlocking the boot loader clears all data from the phone. Including a few apps that are preloaded in a data folder. It appears the update looks for these app.
Click to expand...
Click to collapse
That sucks, i wonder how I got mine to update after I unlocked, lucky I guess. Looks like you might be on the right track tho, let me know how it turns out.
I know I didn't relock to get ota. Perhaps its a device based thing. On sprint for instance I never have seen the relocked or tampered tags.
Sent from my HTC0P3P7 using XDA Free mobile app
JBS976 said:
That sucks, i wonder how I got mine to update after I unlocked, lucky I guess. Looks like you might be on the right track tho, let me know how it turns out.
Click to expand...
Click to collapse
Still battling away, no luck yet. I have rooted with custom recovery now.
So you were on the stock recovery when the update went through?
Cjohn1200 said:
Still battling away, no luck yet. I have rooted with custom recovery now.
So you were on the stock recovery when the update went through?
Click to expand...
Click to collapse
Yes I was, I had just gotten a replacement and it was still on JB. So I immediately ran Rummrunner to get S-OFF and then I was unlocked, rooted and S-OFF, everything else stock. As soon as it re booted it ran the update for KK and all was good. After that I just put TWRP on and re rooted