Related
Hello community,
today I've made a terrible mistake. In the past I was using a HTC Desire, I got a lot of experience in flashing and ''playing'' on it.
A few weeks ago I've bought the HTC EVO3D and unlocked it with the HTC unlock method today. Up to this point it all worked very well, so in the next step I've decided to get a shiny new custom rom work on it...
I've choosen this one: http://forum.xda-developers.com/showthread.php?t=1647674
The problem was that I have not installed the 4EXT Recovery system in the right way I think, but at this moment I didn't recognize that...
In the process of flashing the rom, I have flashed the kernel manually as the developer says in post #3 on his thread, before flashing the rom itself...this was very stupid...
I flashed this boot.img with the ''fastboot-method'' (cmd) to my phone, it succesfully worked.
The problem is that now nothing happens on the phone after the first HTC-logo shows up, only a black screen. Going to a nandroid-backup isn't possible because of the ''missing'' recovery system (only black screen appears instead of recovery). When I hit the factory reset option in the bootloader it starts the process but after a while (green loading symbol) it only shows a picture with a phone and a red warning symbol.
Is there anything that can be done to get the phone in a working mode, like flashing another kernel or something over ''fastboot-method''? Or is it totally bricked?
(Sorry for bad language/tenses, I'm from Germany)
FIRST LINK. lol on the other section. lol
http://forum.xda-developers.com/showthread.php?t=1563342
YOU SHOULD have waited until we found the correct way to root instead of using the HTC method. lol. but either way. FOLLOW THE INSTRUCTIONS! DONT' FORGET YOU HAVE TO UNDO THE HTC METHOD BEFORE DOING THE ENTIRE PROCESS! or did they fix that? haha I forget.
---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------
wait a second!!!!!! SORRY just re-read some of your post! you used the HTC method TODAY!?!?!!?!?!!? lmao! like I said, follow the CORRECT instructions. the HTC method is a joke.
Sent from my PG86100 using xda premium
Go on fastboot mode. Type in fastboot boot recovery.img ( or whatever the name of your recovery image is)
*learned this the hard way*
---------- Post added at 11:49 PM ---------- Previous post was at 11:39 PM ----------
And also do you have S-ON or S-OFF ....... HBOOT 1.5 or 1.4??
Oh just a tip, never do a factory reset within the bootloader after you have rooted. Also download twrp and flash the .img through fastboot. Then flash a gingerbread Rom with probably a stock kernel. (Again the kernel through fastboot)
------
3(d)vo one s
Newts my hero.
kiewee3 is correct and also you need to be rooted before you install 4ext recovery
but don't forget that the developer never said to do it on a phone without first making sure S=off with the HTC method. it is left on. right?? or did I word that wrong? but you get what I mean. so you need to fully root your phone to prevent issues. make it easier on yourself.
Why don't you just flash the stock ROM? Copy PG86IMG.zip on the SD card via card reader, enter bootloader, let it flash and you are fine... It overwrites everything.
Then just fastboot connect the phone, type "fastboot oem writesecureflag 3" and you are back on the beginning.
Hey folks..so I want to start flashing kernels and yes I know I probably should have gone s-off way sooner but I want to do it now. I've been rooting and romming my phones for a while but this whole s-off procedure continued to scare the crap out of me. But..I don't want to limit my choices when it comes to roms and kernels so I guess I'll do it anyway.
However, I am currently running RUU 4.03.605.2 with Vigor360 1.1 s modified kernel.
Can I still go s-off even though I am now running the global leak (or is it now impossible) and if so, can someone point me in the right direction?
Thank you kind gents n ladies!
I've heard of several people being successful on 4.03.605.2 with the 3.14.605.5 ControlBear version.
Only other advice I can offer is don't give up, try different wires if you're having trouble, and pay attention to the troubleshooting page if you decide you want back out and try again later. I've S-OFF'ed three Rezounds. The first took 3 days, the second 2 minutes, and the third 30 minutes.
dplane said:
Hey folks..so I want to start flashing kernels and yes I know I probably should have gone s-off way sooner but I want to do it now. I've been rooting and romming my phones for a while but this whole s-off procedure continued to scare the crap out of me. But..I don't want to limit my choices when it comes to roms and kernels so I guess I'll do it anyway.
However, I am currently running RUU 4.03.605.2 with Vigor360 1.1 s modified kernel.
Can I still go s-off even though I am now running the global leak (or is it now impossible) and if so, can someone point me in the right direction?
Thank you kind gents n ladies!
Click to expand...
Click to collapse
i did s-off with viper's rom and the .5. i was on global too, don't let it scare you or you will not get it. i couldn't get the timing for the life of me. first two hours was a hassle, then i had to get my other battery(thought i bricked my phone) then i relized that they had a metrnome with the correct timing and it worked the first time. but use a different memory card. all of these things can be found under the s-off instructions.:good:
its really easy man you can do it. i reccemend using speaker wire as its more pliable than a paperclip.. if you need help i can walk you thru it on gtalk. just pm me for me gtalk. otherwise. goodluck and yes the 3.14.605.5 ControlBear version is the correct one just lock your bootloader, run the full ruu agan( 4.03.605.2), flash amonRA, then flash this in recovery (https://docs.google.com/file/d/0B0ZJtM40GdJ0MEpGeG1ZWi0yNDA/edit) to gain root on stock global, download root checker from the app store to be sure you got root before you begin. then boot phone and check usb debugging, connect your phone to the comp(within the stock rom), start control bear.. make sure to back up EVERYTHING as it could all get wiped. (internal sd, external sd, and your nandroid if you so choose) i reccemend using a spare sd card if you have one.. ive only done my phone but it took me all of 2 trys.. i got weird errors a couple times (other than "error: still sober" got that once) if you do just run control bear again
Thanks for the responses and moral support folks!
Collin, I may have to hit you up for that assistance soon, I'd rather be safe then sorry so I might feel better if I have someone to "hold my hand"
May not get around to it til Sat afternoon or Sunday though.
famouscollin said:
its really easy man you can do it. i reccemend using speaker wire as its more pliable than a paperclip.. if you need help i can walk you thru it on gtalk. just pm me for me gtalk. otherwise. goodluck and yes the 3.14.605.5 ControlBear version is the correct one just lock your bootloader, run the full ruu agan( 4.03.605.2), flash amonRA, then flash this in recovery (https://docs.google.com/file/d/0B0ZJtM40GdJ0MEpGeG1ZWi0yNDA/edit) to gain root on stock global, download root checker from the app store to be sure you got root before you begin. then boot phone and check usb debugging, connect your phone to the comp(within the stock rom), start control bear.. make sure to back up EVERYTHING as it could all get wiped. (internal sd, external sd, and your nandroid if you so choose) i reccemend using a spare sd card if you have one.. ive only done my phone but it took me all of 2 trys.. i got weird errors a couple times (other than "error: still sober" got that once) if you do just run control bear again
Click to expand...
Click to collapse
I'm working with the same situation as the OP. You posted a link to a second recovery to flash after Amon Ra, I've tried that link and it forces me to request access. Which recovery is it and is there another link or are you able to give me access to that one?
Hey guys.
I am a complete newb with most this stuff.
I am not sure how I look at RUU I have. I will say that my phone was pretty much stock through the official ICS release.
Currently I have CM9 flashed as my rom.
Is there anyway I can S-OFF my phone?
Sax1031 said:
Hey guys.
I am a complete newb with most this stuff.
I am not sure how I look at RUU I have. I will say that my phone was pretty much stock through the official ICS release.
Currently I have CM9 flashed as my rom.
Is there anyway I can S-OFF my phone?
Click to expand...
Click to collapse
If you haven't already, I would say start by checking out unlimited.io They have all the basic details about how to achieve S-OFF. Without knowing more specifics about your setup it would be hard someone to give a more specific answer.
neowisdom1031 said:
If you haven't already, I would say start by checking out unlimited.io They have all the basic details about how to achieve S-OFF. Without knowing more specifics about your setup it would be hard someone to give a more specific answer.
Click to expand...
Click to collapse
Yea I have went there.
I have the program downloaded. I am on Gray's CM9 rom.
Followed all the instructions. When the program runs it goes like this:
Starting up....
Connecting to device....
Searching device.....
Found device......
Backing up.....
Permission denied.....
Transferring backups....
Secondary backup FAILED!!
Press ENTER to exit.
like I said my phone was stock till the official ICS update released. After that I unlocked the boot loader and just recently flashed my first rom, through Amon Ra.
If I could kindly ask you what info you need, and possibly how to access the info, to help me out. Do I need to flash a stock rom back?
---------- Post added at 08:27 PM ---------- Previous post was at 07:29 PM ----------
I hope to god my hboot was stock. As I am running a previous RUU.
Hopefully once I do this, I will be able to S-OFF.
Sax1031 said:
Yea I have went there.
I have the program downloaded. I am on Gray's CM9 rom.
Followed all the instructions. When the program runs it goes like this:
Starting up....
Connecting to device....
Searching device.....
Found device......
Backing up.....
Permission denied.....
Transferring backups....
Secondary backup FAILED!!
Press ENTER to exit.
like I said my phone was stock till the official ICS update released. After that I unlocked the boot loader and just recently flashed my first rom, through Amon Ra.
If I could kindly ask you what info you need, and possibly how to access the info, to help me out. Do I need to flash a stock rom back?
---------- Post added at 08:27 PM ---------- Previous post was at 07:29 PM ----------
I hope to god my hboot was stock. As I am running a previous RUU.
Hopefully once I do this, I will be able to S-OFF.
Click to expand...
Click to collapse
If you're able to flash back to stock that would be the best place to start for S-OFF
neowisdom1031 said:
If you're able to flash back to stock that would be the best place to start for S-OFF
Click to expand...
Click to collapse
I flashed back to the first ICS RUU.
I think I know why it said permission denied. Because I didn't have actual root access.
At the point of trying the wire trick.
Edit: Achieved S-OFF. Thanks so much guys. Going from 3 days ago of flashing my first rom. To having to relock the device, run the first ICS Ruu, then doing the wire trick. Hell of a learning curve on these things. Thanks everyone for all the help.
Just a quick update. I was able to achieve S-Off while using this specific RUU. It took a few time flashing the RUU and a rooted rom to finally get it but it is possible with this RUU.
neowisdom1031 said:
Just a quick update. I was able to achieve S-Off while using this specific RUU. It took a few time flashing the RUU and a rooted rom to finally get it but it is possible with this RUU.
Click to expand...
Click to collapse
Fwiw I also was able to go s-off using this ruu and flashing supersu from a temporary amon ra. Not as tough as it thought.
Sent from my ADR6425LVW using xda app-developers app
.
Did you put the Juopunutbear executable and files into the same folder
that Android fastboot, adb, and other files are located?
michaelbsheldon said:
Did you put the Juopunutbear executable and files into the same folder
that Android fastboot, adb, and other files are located?
Click to expand...
Click to collapse
It shouldn't matter. ControlBear has its own versions of everything it needs.
Sent from my HTC Rezound using Tapatalk 2
So this is what i've done and its failing with the error: "Secondary backup FAILED!!"
-I reset everything by using the RUU 4.03.605.2.
-I then set the debugging mode, unlocked the bootloader
-Put AmonRa3.15 as my recovery
-Flashed the CWM SuperSU.
-Confirmed root access by using TitaniumBackup.
-Started the ControlBearRelease_vigor_ICS_3.14.605.5 for the ICS leak process.
-Then I get the fun error Secondary backup FAILED!!.
I'm using the latest version of JuopunutBear 0.4. Help?
-------------update---------------
So I re-flashed the full RUU and went through all the steps and still same outcome. "Secondary backup Failed!". I read that only version .1 may work if this error occurs?
=-\
Izeltokatl said:
So this is what i've done and its failing with the error: "Secondary backup FAILED!!"
-I reset everything by using the RUU 4.03.605.2.
-I then set the debugging mode, unlocked the bootloader
-Put AmonRa3.15 as my recovery
-Flashed the CWM SuperSU.
-Confirmed root access by using TitaniumBackup.
-Started the ControlBearRelease_vigor_ICS_3.14.605.5 for the ICS leak process.
-Then I get the fun error Secondary backup FAILED!!.
I'm using the latest version of JuopunutBear 0.4. Help?
-------------update---------------
So I re-flashed the full RUU and went through all the steps and still same outcome. "Secondary backup Failed!". I read that only version .1 may work if this error occurs?
=-\
Click to expand...
Click to collapse
i s-offed with the global ruu and and this version of control bear https://docs.google.com/file/d/0B0ZJtM40GdJ0SmVBbm40anJpRTg/edit ia got a few wierd errors but just started it up again and all went well..also make sure you have htc sync uninstalled from your computer
famouscollin said:
i s-offed with the global ruu and and this version of control bear https://docs.google.com/file/d/0B0ZJtM40GdJ0SmVBbm40anJpRTg/edit ia got a few wierd errors but just started it up again and all went well..also make sure you have htc sync uninstalled from your computer
Click to expand...
Click to collapse
Ya that's the exact same version I have, not really sure what to do? I re-did everything back to RUU again to no avail.
Izeltokatl said:
Ya that's the exact same version I have, not really sure what to do? I re-did everything back to RUU again to no avail.
Click to expand...
Click to collapse
you can try backing up your sd cards and partition them before you start the control bear process, and your sure you have root access correct? via rootchecker, tatanium backup or somethin gand usb degugging checked? if your still having issues look for apophis' thread named "so you need assistance, WE ARE HERE TO HELP" post in that thread im sure he can help you walk thru it..
When I bought my rezound used it had a constant boot loop issue. That's why I got it fairly cheap. I immediayly ran the global ruu hoping it would boot. It still boot looped. I was able to unlock, flash recovery and install newts xxx. I have tried to boot other romsand they give me issues too. Is there any way I can s off in my current configuration because I am pretty confident another ruu from my sd card just won't boot. Has anyone had success being on a custom Rom w global firmware hboot 2.27?
Here's my situation. Got this new phone yesterday. I am (was) bootloader unlocked, s-on with htcdev method. Also am (was) using twrp for recovery. Then went looking for some roms... found one, moved it to the phone, wipe, blah, blah, done this before plenty on my old evo shift. Well, there was some problem, rom couldn't be installed, which is no problem for people who do regular nand backups. That was not me. So... stuck at htc screen.
Bottom line, after many hours of different ideas and methods, I've relocked the bootloader, downloaded an ruu, and I'm stuck. In hindsight I sort of backed myself into a corner, because though I supposedly needed to relock to run an ruu, now I can't get at twrp recovery. So I need help running the ruu from fastboot. In my searches, this seems possible, but it's not working for me. The phone is recognized, because when I enter into command "fastboot find devices" or whatever that was, a phone shows up. The .exe itself just won't open though. Tried running as administrator, tried compatibility mode, tried running it from the command line, each time it will give me the blue circley thing for about 5 or 10 seconds and then just do nothing.
I'm just out of ideas, feeling like I'm stuck here.
Remember: currently my screen reads TAMPERED RELOCKED Security Warning I'm in fastboot usb mode. Oh, and I tried to find the ruu to match my Hboot, but it currently shows 1.15.0000, and there is of course no ruu with that code, so I downloaded the newest one (2 point something)
Any help is appreciated
admsteff said:
Here's my situation. Got this new phone yesterday. I am (was) bootloader unlocked, s-on with htcdev method. Also am (was) using twrp for recovery. Then went looking for some roms... found one, moved it to the phone, wipe, blah, blah, done this before plenty on my old evo shift. Well, there was some problem, rom couldn't be installed, which is no problem for people who do regular nand backups. That was not me. So... stuck at htc screen.
Bottom line, after many hours of different ideas and methods, I've relocked the bootloader, downloaded an ruu, and I'm stuck. In hindsight I sort of backed myself into a corner, because though I supposedly needed to relock to run an ruu, now I can't get at twrp recovery. So I need help running the ruu from fastboot. In my searches, this seems possible, but it's not working for me. The phone is recognized, because when I enter into command "fastboot find devices" or whatever that was, a phone shows up. The .exe itself just won't open though. Tried running as administrator, tried compatibility mode, tried running it from the command line, each time it will give me the blue circley thing for about 5 or 10 seconds and then just do nothing.
I'm just out of ideas, feeling like I'm stuck here.
Remember: currently my screen reads TAMPERED RELOCKED Security Warning I'm in fastboot usb mode. Oh, and I tried to find the ruu to match my Hboot, but it currently shows 1.15.0000, and there is of course no ruu with that code, so I downloaded the newest one (2 point something)
Any help is appreciated
Click to expand...
Click to collapse
You can get the RUU here
This will help you get twrp and SuperSU back
It's really just an incompatible ruu? I'm about halfway through downloading the 1.22 version already, I thought I would try. I'll give it a shot, but wouldn't it give an error or something instead of just not responding on my pc?
admsteff said:
It's really just an incompatible ruu? I'm about halfway through downloading the 1.22 version already, I thought I would try. I'll give it a shot, but wouldn't it give an error or something instead of just not responding on my pc?
Click to expand...
Click to collapse
To be honest I have never flashed an RUU but I would think if you flashed the wrong one it could potentially brick your phone.
Thanks, these ruu files are so damn big, it's gonna be a few minutes. We'll see how it goes.
admsteff said:
Thanks, these ruu files are so damn big, it's gonna be a few minutes. We'll see how it goes.
Click to expand...
Click to collapse
You should try uploading them haha good luck.
Wait a minute, I noticed that the link you gave me is for a .zip file, while the one I'm downloading is for a .exe file? Isn't it supposed to be a self-installing program from windows? Do I need to be entering like a fastboot flash command for a zip instead because my phone is in fastboot and not fully booted? I can't believe I forgot the nand backup, this is like a whole wasted day of my life now...
admsteff said:
Wait a minute, I noticed that the link you gave me is for a .zip file, while the one I'm downloading is for a .exe file? Isn't it supposed to be a self-installing program from windows? Do I need to be entering like a fastboot flash command for a zip instead because my phone is in fastboot and not fully booted? I can't believe I forgot the nand backup, this is like a whole wasted day of my life now...
Click to expand...
Click to collapse
Like I said I have never ran an RUU so I'm not sure how it works you could PM om4 or read Don't Panic in the Q&A section
Yeah, problem is the same with the 1.22 ruu. It just wont execcute the program from my pc. Does anybody else have any ideas?
You only had to flash the kernel or bootimg. Seperately since your s-on...look for om4 guide " don't panic"...it should answer all of your questions...as far as the ruu make sure you're on the bootloader fastboot screen when you run it.
Sent from my EVO using xda premium
---------- Post added at 02:40 PM ---------- Previous post was at 02:37 PM ----------
http://forum.xda-developers.com/showthread.php?p=31102864
mrlakadaddy said:
You only had to flash the kernel or bootimg. Seperately since your s-on...look for om4 guide " don't panic"...it should answer all of your questions...as far as the ruu make sure you're on the bootloader fastboot screen when you run it.
Sent from my EVO using xda premium
---------- Post added at 02:40 PM ---------- Previous post was at 02:37 PM ----------
http://forum.xda-developers.com/showthread.php?p=31102864
Click to expand...
Click to collapse
Yes, I realize I dug myself into a hole by relocking. I just didn't want to learn how to put a new img on my phone (of course it was wiped, with a bad rom flashed) without having the thing mounted as a media device in the gui method. I'm sure it would have been quite easy, and that's kind of how the whole thing went, I wasn't scared enough and I just kept doing what I thought was the "easiest" way to get the phone back, and just was a dumbass overall. I read the "don't panic" guide. Maybe I missed something, but I don't think it would have got me out of the specific problem I made, once I was already in it. And I was certainly on fastboot usb when trying to run the ruu, and I had it in the right folder with fastboot.exe, etc.
Anyway, I never got it to work, but I ended up just returning the device to the retailer, and no questions were asked. It was cheating, I know. It could have been done, I was far from bricked, but when the phone is 1.5 days old and I can return it to a person who has no idea why my phone is "stuck", it was just too easy.
Thanks to everyone who tried to help
I rooted my HTC One X+, and now I tried installing this update, then it just stops like 1/3 of the way and gives me a error sign (a triangle with a ! in the middle) and is there anyways to restore to stock recovery? I mean I really want this update, please help! What do I need to do to restore my phone, do I need to lock bootloader, unroot my phone? Just please help me.
ChrisFirerabbit said:
I rooted my HTC One X+, and now I tried installing this update, then it just stops like 1/3 of the way and gives me a error sign (a triangle with a ! in the middle) and is there anyways to restore to stock recovery? I mean I really want this update, please help! What do I need to do to restore my phone, do I need to lock bootloader, unroot my phone? Just please help me.
Click to expand...
Click to collapse
Relock your bootloader and flash the following RUU (1.17): HERE
This will wipe my phone totally right?
Will I be able to gain root back afterwards?
Sorry for asking obvious but not used to the single solid state memory for everything, and a bit confused by the partitions...
Sent from my HTC One X+ using Tapatalk 2
Thanks!
Steve0007 said:
Relock your bootloader and flash the following RUU (1.17): HERE
Click to expand...
Click to collapse
Thank you so much!
I try to relock and run ruu.exe but I can't get it done I get error
Sent from my HTC One X+ using xda premium
Ever since the update, my phone's touch screen is messed up. Is there a way to go back to the previous firmware?
Sharpshooterrr said:
Ever since the update, my phone's touch screen is messed up. Is there a way to go back to the previous firmware?
Click to expand...
Click to collapse
Are you having problem with scrolling? like when you scroll left it will rubberband itself or scrolling right does the same?, or does it click on stuff instead of scrolling?, this is happeneing to me and its really annoying, i did a screen test with *#*#3424#*#* and each touf=ch on the screen doesnt show up untill the next touch if you no what i mean, now, i dont know if its software related or a broken digitizer, i imagine if it was the digitizer then the touches wont show at all i suppose. This is the reason for the touch screen issues though for me, maybe you try and see if it does the same so we can rule out broken digitizer. As fopr the update, my phone wont pick it up, im thinking that its because my HBOOT is already 1.35.
---------- Post added at 12:43 PM ---------- Previous post was at 12:39 PM ----------
DamBadz said:
I try to relock and run ruu.exe but I can't get it done I get error
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
You need to get a stock recovery flashed back on your phone first. Relock bootloader, then run the ruu, or try the ota first.
boe323 said:
Are you having problem with scrolling? like when you scroll left it will rubberband itself or scrolling right does the same?, or does it click on stuff instead of scrolling?, this is happeneing to me and its really annoying, i did a screen test with *#*#3424#*#* and each touf=ch on the screen doesnt show up untill the next touch if you no what i mean, now, i dont know if its software related or a broken digitizer, i imagine if it was the digitizer then the touches wont show at all i suppose. This is the reason for the touch screen issues though for me, maybe you try and see if it does the same so we can rule out broken digitizer. As fopr the update, my phone wont pick it up, im thinking that its because my HBOOT is already 1.35.
---------- Post added at 12:43 PM ---------- Previous post was at 12:39 PM ----------
You need to get a stock recovery flashed back on your phone first. Relock bootloader, then run the ruu, or try the ota first.
Click to expand...
Click to collapse
That is the problem I can't find stock international recovery.IMG T.T
Sent from my HTC One X+ using xda premium
DamBadz said:
That is the problem I can't find stock international recovery.IMG T.T
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
download the ruu and extract form the ruu. UPDATE: Thats weird, i have rom.zip, opened with winrar, i can extract all the files execpt the signed ones, i get error sayiong they are corrupt, so you cant get the recovery img from them, you need to find another source unless you knoew of a way to extract them without a corrupt error.
---------- Post added at 01:47 PM ---------- Previous post was at 01:00 PM ----------
Why dont the checksums match with the related downloads on htcruu.com?, whats the point of putting the md5 checksum files there they dont match, im wisting my time downloading over and over, its the md5 file thats wrong.
boe323 said:
Are you having problem with scrolling? like when you scroll left it will rubberband itself or scrolling right does the same?, or does it click on stuff instead of scrolling?, this is happeneing to me and its really annoying, i did a screen test with *#*#3424#*#* and each touf=ch on the screen doesnt show up untill the next touch if you no what i mean, now, i dont know if its software related or a broken digitizer, i imagine if it was the digitizer then the touches wont show at all i suppose. This is the reason for the touch screen issues though for me, maybe you try and see if it does the same so we can rule out broken digitizer. As fopr the update, my phone wont pick it up, im thinking that its because my HBOOT is already 1.35.
Click to expand...
Click to collapse
Yes I am having a problem with scrolling - it clicks on stuff instead of scrolls. I have good reason to believe that this is a software problem because I have done nothing physical to the phone and the problem came only after updating.
Would you know how to downgrade the firmware? Or do you think a hard reset can fix the issue?
Sharpshooterrr said:
Yes I am having a problem with scrolling - it clicks on stuff instead of scrolls. I have good reason to believe that this is a software problem because I have done nothing physical to the phone and the problem came only after updating.
Would you know how to downgrade the firmware? Or do you think a hard reset can fix the issue?
Click to expand...
Click to collapse
You can downgrade using ruu 1.16.401.6 with the newest version radio, it has the same HBOOT 1.35, but theres no point because thats what version i was on and i have a scrolling issue, when doing a screen test on black background, i can touch the screen, nothing happens, when i touch it again in a different place the first touch then registers, unless we can get back to 1.14 i think were stuck with it untill new update, best thing to do is report it to HTC they may say send them to be repaired or they may acknowledge the issue, i thought it was the digitizer but now you are the same its def software, if you say it was ok untill you updated. I got a seperate camera.apk download after updating to 1.17.401.1, did you?. Mine is a week old but im scared to replace incase i get one thats worse, like wif no good or bad signal an so on. Im going to factory reset the phone, then run ruu 1.17.401.1 again.
boe323 said:
You can downgrade using ruu 1.16.401.6 with the newest version radio, it has the same HBOOT 1.35, but theres no point because thats what version i was on and i have a scrolling issue, when doing a screen test on black background, i can touch the screen, nothing happens, when i touch it again in a different place the first touch then registers, unless we can get back to 1.14 i think were stuck with it untill new update, best thing to do is report it to HTC they may say send them to be repaired or they may acknowledge the issue, i thought it was the digitizer but now you are the same its def software, if you say it was ok untill you updated. I got a seperate camera.apk download after updating to 1.17.401.1, did you?. Mine is a week old but im scared to replace incase i get one thats worse, like wif no good or bad signal an so on. Im going to factory reset the phone, then run ruu 1.17.401.1 again.
Click to expand...
Click to collapse
Just sent you a private message.
Re-Locking Bootloader
If I re-lock bootloader, and then unlock it will all my apps and data be erased?
ChrisFirerabbit said:
If I re-lock bootloader, and then unlock it will all my apps and data be erased?
Click to expand...
Click to collapse
Yes i think so, but if you want the ota, you will have to.
ChrisFirerabbit said:
If I re-lock bootloader, and then unlock it will all my apps and data be erased?
Click to expand...
Click to collapse
Yes. Everything will be erased.
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