Database Develop

[Q] Velocity 4G (VODAP120) boot loop / can't RUU

Hello all,
I'm sorry to interrupt you all, but this is rather important!
I tried to root my girlfriends Velocity 4G which she got with her contract with A1 (austrian carrier).
I already flashed a One S and knew of the complications a root for HTC could bring.
So I tried to get everything together before flashing and then I did it...
Got the bootloader unlocked, installed TWRP and flashed sun_dreams rom.
Don't worry, I wiped all clean and think I did it the right way (already flashed 4 other phones, but samsungs').
But I seem to have missed something as I got in a neverending bootanimation (white background with green htc logo).
I know, that you sometimes have to wait a few minutes, but after about 5 minutes or so, I thought I was stuck on boot loop.
So I rebooted, flashed it again and rebooted and nothing changed.
I then read about the boot.img... So I extracted the boot.img and did a full wipe, then installed it, after that the rom and then (just to be safe) three times again the boot.img.
Rebooted and now I got the reboot loop (white background with green logo, then black, then white background again and so on)
I tried everything and as I was about to give up, read about the final solution: the RUU or PH39IMG.zip.
Now the problem is: I cant get either of them to work. At all. When trying to flash the RUU (with bootloader relocked), the programm says: "ERROR 170: No device connected".
I read about some other people having the same problem, so I tried the solution given to them: go to the first screen, then to your temp data, extract the rom.zip, rename it and flash that one, via putting it on the external sd and booting into bootloader.
Didn't work either: Wrong CID. Same for all RUUs I could find even closely related to my phone.
As I couldn't find the real correct RUU, I tried to cheat and use the goldcard to overgo the cid-problem.
Because I couldn't boot up the Velocity 4G I tried to make one with my own Galaxy S2, which worked.
Seems to be the wrong way, since it's the wrong CID anyways, when trying to install the PH39IMG (still all RUUs say ERROR 170).
I might need to mention I didn't do the S-OFF thing, as I didn#t want to mess with the hardware... Is that necessary for my problem to getting fixed?
Maybe I just need the one correct RUU for my model, but I can't find it anywhere!
please help me somebody, as I feel very guilty because of wrecking my girlfriends phone! :crying:
any help is appreciated!!!
greetings

deweini said:
Hello all,
I'm sorry to interrupt you all, but this is rather important!
I tried to root my girlfriends Velocity 4G which she got with her contract with A1 (austrian carrier).
I already flashed a One S and knew of the complications a root for HTC could bring.
So I tried to get everything together before flashing and then I did it...
Got the bootloader unlocked, installed TWRP and flashed sun_dreams rom.
Don't worry, I wiped all clean and think I did it the right way (already flashed 4 other phones, but samsungs').
But I seem to have missed something as I got in a neverending bootanimation (white background with green htc logo).
I know, that you sometimes have to wait a few minutes, but after about 5 minutes or so, I thought I was stuck on boot loop.
So I rebooted, flashed it again and rebooted and nothing changed.
I then read about the boot.img... So I extracted the boot.img and did a full wipe, then installed it, after that the rom and then (just to be safe) three times again the boot.img.
Rebooted and now I got the reboot loop (white background with green logo, then black, then white background again and so on)
I tried everything and as I was about to give up, read about the final solution: the RUU or PH39IMG.zip.
Now the problem is: I cant get either of them to work. At all. When trying to flash the RUU (with bootloader relocked), the programm says: "ERROR 170: No device connected".
I read about some other people having the same problem, so I tried the solution given to them: go to the first screen, then to your temp data, extract the rom.zip, rename it and flash that one, via putting it on the external sd and booting into bootloader.
Didn't work either: Wrong CID. Same for all RUUs I could find even closely related to my phone.
As I couldn't find the real correct RUU, I tried to cheat and use the goldcard to overgo the cid-problem.
Because I couldn't boot up the Velocity 4G I tried to make one with my own Galaxy S2, which worked.
Seems to be the wrong way, since it's the wrong CID anyways, when trying to install the PH39IMG (still all RUUs say ERROR 170).
I might need to mention I didn't do the S-OFF thing, as I didn#t want to mess with the hardware... Is that necessary for my problem to getting fixed?
Maybe I just need the one correct RUU for my model, but I can't find it anywhere!
please help me somebody, as I feel very guilty because of wrecking my girlfriends phone! :crying:
any help is appreciated!!!
greetings
Click to expand...
Click to collapse
OK... Vodafone is still on gingerbread...
Soooo... You need a gingerbread ROM... And a gingerbread boot.img... Then get it to boot...
After that I would s-off, super cid, get to ICS hboot... Then flash the ROM of your choice

rignfool said:
OK... Vodafone is still on gingerbread...
Soooo... You need a gingerbread ROM... And a gingerbread boot.img... Then get it to boot...
After that I would s-off, super cid, get to ICS hboot... Then flash the ROM of your choice
Click to expand...
Click to collapse
So far so good... but where do I get it from?
I have this one:
RUU_HOLIDAY_SENSE3_5_Vodafone_DE_2.38.162.1_Radio_3.02.4740.09_34.20.701040.19_release_241518_signed
But this one won't work either...
What complicates the search, is that this phone goes by so many different names (vivid, velocity, holiday, raider, etc...)
Should I post a getvar all?
Concerning your further steps: I would be very happy to get it to run at all, maybe then think of reflashing something.
I don't know if I manage that s-off thing and I don't want to hard brick it and give it the final punch...
anyways, thanks for the fast response!

Can you get the ph39img from it?
Sent from my Vivid 4G using Tapatalk

rignfool said:
Can you get the ph39img from it?
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
I already did that with all the RUUs I found, but none worked...
EDIT: so I tried a solution offered by another poster in another forum which said to install CM10 on a clean wipe.
did that and it booted in the cm boot screen and loads the "first install wizard"... well, at least to the language selection screen, then it freezes and reboots again.
but at least we bought us some time at the start.

deweini said:
I already did that with all the RUUs I found, but none worked...
EDIT: so I tried a solution offered by another poster in another forum which said to install CM10 on a clean wipe.
did that and it booted in the cm boot screen and loads the "first install wizard"... well, at least to the language selection screen, then it freezes and reboots again.
but at least we bought us some time at the start.
Click to expand...
Click to collapse
Its because of a wrong hboot...
It will happen with all of the ICS+ ROMs...
I wish you hadn't relocked your bootloader...
Can you reunlock...
Iirc there is a thread with hboot updated... Maybe try that... Or download the Wcxroot thingy and flash the juopenut hboot...
Sent from my Vivid 4G using Tapatalk

rignfool said:
Its because of a wrong hboot...
It will happen with all of the ICS+ ROMs...
I wish you hadn't relocked your bootloader...
Can you reunlock...
Iirc there is a thread with hboot updated... Maybe try that... Or download the Wcxroot thingy and flash the juopenut hboot...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
so, you're basically saying i might be able to get it to work without any RUUs or PH39IMGs?
Wow, that would be good news at last.
I already reunlocked before i flashed the CM10 rom and i didn't forget to flash the boot.img afterwards and even went back again to recovery to wipe cache and dalvik and fixed permissions.
Which one should i try?
thank you for your help!! :good:

is updating the hboot even possible without s-off?
so it seems i have to obtain s-off to flash anything else than stock rom...
as far as i read you have to be on stock ruu to obtain s-off, is that correct?
because that would be bad, as i don't have the stock ruu for my phone.
is it possible to acquire s-off without being on stock rom and would it be possible with the state my phone is in?

deweini said:
is updating the hboot even possible without s-off?
so it seems i have to obtain s-off to flash anything else than stock rom...
as far as i read you have to be on stock ruu to obtain s-off, is that correct?
because that would be bad, as i don't have the stock ruu for my phone.
is it possible to acquire s-off without being on stock rom and would it be possible with the state my phone is in?
Click to expand...
Click to collapse
I think homeslice s-offed his phone on a non stock ROM...
Sent from my Vivid 4G using Tapatalk

rignfool said:
I think homeslice s-offed his phone on a non stock ROM...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
i already wrote a pm. do you have any ideas left? maybe try and install a gb rom and then try that ruu again?
ps: i did manage to start the ruu.exe (by reinstalling the htc sync) and it stopped with the error 131. installing the rom.zip (or PH39IMG.zip) still won't work as it says customer id check failed...

deweini said:
i already wrote a pm. do you have any ideas left? maybe try and install a gb rom and then try that ruu again?
ps: i did manage to start the ruu.exe (by reinstalling the htc sync) and it stopped with the error 131. installing the rom.zip (or PH39IMG.zip) still won't work as it says customer id check failed...
Click to expand...
Click to collapse
Okay, so I did manage to fix it, as it seems... :laugh:
This is what I did:
1. reunlocked bootloader
2. installed TWRP and booted into recovery
3. mounted the internal SD as mass storage
4. copied over VJRaiders GB rom
5. did a full wipe
6. installed VJRaiders rom
7. rebooted into bootloader
8. fastboot flashed the kernel found in the rom thread (twice)
9. rebooted and it worked...
I don't know how and why, but the problem seemed to be that I always tried to flash non-GB roms. As simple as that.
I have no idea why the RUU and PH39IMG didn't work tho...
Well. I won't touch that thing for a looong time, as it works and I had enough problems getting there!

The reason that you had problems with ics and upward roms is because your phone still has the gb hboot. This is because boss never released the ics update. To install ics roms you need the ics hboot.
Sent from my HTC One

WildfireDEV said:
The reason that you had problems with ics and upward roms is because your phone still has the gb hboot. This is because boss never released the ics update. To install ics roms you need the ics hboot.
Sent from my HTC One
Click to expand...
Click to collapse
Which I'm only able to attain with s-off, am I right?

Correct, I believe. If you didn't get an official update to ICS, you'll have to S-Off. It's honestly not as bad as it sounds, I did mine with some speaker wire...probably the worst part of it is getting the cover off of the section where you have to ground out the point. Just take your time, and make sure you're in a well lit area, with a little bit of working space, and you'll be fine.

well, the problem is, that we are not longer on a stock rom and can't seem to flash the original ruu, as we don't find it anywhere...
and as far as i know it is not recommended or possible to go s-off without being on stock rom!?

AFAIK it is UNTESTED... Not impossible
Sent from my Vivid 4G using Tapatalk

If this is anything like other HTC devices, i'd say your best shot if you're willing to try an untested idea, would be to give it a shot with a sense rom, as they tend to be (under the hood anyways) a lot closer to stock than non sense roms.

[Q] Constantly restarting at welcome screen

Hello guys,
I'm in a bit of a pickle here....
I've got a HTC One which I've rooted and unlocked though not S-Off by the looks of things and I had SinLess rom installed fine, it started playing up so I though I'd update it. Bung the new one version on there via sideload and install... Marvelous.
Only now, it gets to the welcome screen as silly ol' me did a factory wipe as well as all cache and after about 5 seconds of Welcome - Choose language. It restarts.
I then decided to try a new rom, so grabbed Android Revolution. To no avail either....
On bootloader it shows as HBOOT - 1.54
S-On
**TAMPERED**
**UNLOCKED**
What can I do to actually get a working rom on this thing?
If there is any more details I need to give please say so as this is my first time flashing something as complicated as this. All my old android devices were far far simplar :crying:
- Here's the facepalm moment - I didn't do an nandroid backup due to it not working and I wanted to put a new ROM on there so I didn't look into getting it working. If I could injure myself I would.
Any help will be greatly appreciated. :good:
Kind regards, Ian.

Jeffaruni said:
Hello guys,
I'm in a bit of a pickle here....
I've got a HTC One which I've rooted and unlocked though not S-Off by the looks of things and I had SinLess rom installed fine, it started playing up so I though I'd update it. Bung the new one version on there via sideload and install... Marvelous.
Only now, it gets to the welcome screen as silly ol' me did a factory wipe as well as all cache and after about 5 seconds of Welcome - Choose language. It restarts.
I then decided to try a new rom, so grabbed Android Revolution. To no avail either....
On bootloader it shows as HBOOT - 1.54
S-On
**TAMPERED**
**UNLOCKED**
What can I do to actually get a working rom on this thing?
If there is any more details I need to give please say so as this is my first time flashing something as complicated as this. All my old android devices were far far simplar :crying:
- Here's the facepalm moment - I didn't do an nandroid backup due to it not working and I wanted to put a new ROM on there so I didn't look into getting it working. If I could injure myself I would.
Any help will be greatly appreciated. :good:
Kind regards, Ian.
Click to expand...
Click to collapse
Hey your'e stuck in a boot loop, its usual
just download a good stable rom
clear data/ cache
flash the rom and you'll be out of it,
If this thing doesnt work out download the orignal RUU and get back to stock

Tech.Nik said:
Hey your'e stuck in a boot loop, its usual
just download a good stable rom
clear data/ cache
flash the rom and you'll be out of it,
If this thing doesnt work out download the orignal RUU and get back to stock
Click to expand...
Click to collapse
Yeah, after attempting to install 3 different roms.
Sinless, ARHD and SkyDragon, I'm going to try a different recovery as I'm currently using TWRP 2.6.3.3 and I know there is an update but also I want to see if CWM can do anything with the 6.0.4.3 version....

Jeffaruni said:
Yeah, after attempting to install 3 different roms.
Sinless, ARHD and SkyDragon, I'm going to try a different recovery as I'm currently using TWRP 2.6.3.3 and I know there is an update but also I want to see if CWM can do anything with the 6.0.4.3 version....
Click to expand...
Click to collapse
Hello,
To no avail, after trying different recoveries, nothing.
Looks like I've got a metal slab...
It just keeps restarting itself at the welcome screen, the only other thing I can think of would be to fully wipe EVERYTHING on the phone but I'm not sure that's too good of a move either...
Argh.

You have to be s-off to run these Roms

[Q] Changing CID back to original

Im sending my phone back to HTC for repair.
I have two questions...
Would they look at the CID?
Can I change it back to my original CID if I've already installed a RUU that doesn't allow my CID? (sounds like a dumb question)

stanny2k said:
Im sending my phone back to HTC for repair.
I have two questions...
Would they look at the CID?
Can I change it back to my original CID if I've already installed a RUU that doesn't allow my CID? (sounds like a dumb question)
Click to expand...
Click to collapse
I read your other post http://forum.xda-developers.com/showthread.php?t=2599739 and probably a lot of others too, no answer because I have none.
So here's a small summary:
1- you're S-ON again, so changing CID cannot be done
2- you have a .401. software version which means it cannot be CID H3G, so HTC__001 is correct for that software version
3- you've removed TAMPERED and set to LOCKED (not relocked)
4- I don't know how the service center will react, and whether they would bother checking CID, etc. (from what I've seen the UK centers are quite lenient)
If you really want to go back fully to your carrier version, and "out of the box", you can take a look at my guide: http://forum.xda-developers.com/showthread.php?t=2541082
but that means starting the procedure all the way from the start again, ie
-- unlocking (and you're gonna have to do that with HTCdev)
-- s-off using rumrunner.
then follow the rest of the guide.
Don't know if it's worth the hassle; but if you need help with it, post back there.
cheers

nkk71 said:
I read your other post http://forum.xda-developers.com/showthread.php?t=2599739 and probably a lot of others too, no answer because I have none.
So here's a small summary:
1- you're S-ON again, so changing CID cannot be done
2- you have a .401. software version which means it cannot be CID H3G, so HTC__001 is correct for that software version
3- you've removed TAMPERED and set to LOCKED (not relocked)
4- I don't know how the service center will react, and whether they would bother checking CID, etc. (from what I've seen the UK centers are quite lenient)
If you really want to go back fully to your carrier version, and "out of the box", you can take a look at my guide: http://forum.xda-developers.com/showthread.php?t=2541082
but that means starting the procedure all the way from the start again, ie
-- unlocking (and you're gonna have to do that with HTCdev)
-- s-off using rumrunner.
then follow the rest of the guide.
Don't know if it's worth the hassle; but if you need help with it, post back there.
cheers
Click to expand...
Click to collapse
Thanks for taking the time in responding mate. The issue I have is that I can't get a stock RUU for my H3G CID... It just doesn't seem to exist anywhere... I think a few other people are asking the same question... Which is why I've had to change my CID to HTC__001..

stanny2k said:
Thanks for taking the time in responding mate. The issue I have is that I can't get a stock RUU for my H3G CID... It just doesn't seem to exist anywhere... I think a few other people are asking the same question... Which is why I've had to change my CID to HTC__001..
Click to expand...
Click to collapse
Well if you checked my guide, you'd see that method 3 (CWM Backup), works, and there is a H3G__001 backup out there; as a matter of fact, the example I used was for H3G__001.

nkk71 said:
Well if you checked my guide, you'd see that method 3 (CWM Backup), works, and there is a H3G__001 backup out there; as a matter of fact, the example I used was for H3G__001.
Click to expand...
Click to collapse
In that case, I take that back I'm going to follow your guide again tonight.
The last thing I want is for HTC to say No, they cant do my repair cause I've messed about with my phone...
Oh, and have a "thanks"

stanny2k said:
In that case, I take that back I'm going to follow your guide again tonight.
The last thing I want is for HTC to say No, they cant do my repair cause I've messed about with my phone...
Oh, and have a "thanks"
Click to expand...
Click to collapse
I'm going to recommend this CWM recovery, just cause the newer versions are taking close to an hour to backup/restore:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD: 1c6afb14db3f305b0ad7d85d5af80bef
Also, please follow the instruction properly, no jumping, skipping or adding steps
The only slightly tricky part (as mentioned), is in Step 6, where when the phone reboots to "stock recovery" it could hang somewhere between 25% to 50%, and you have to manually reboot, and (possibly) again towards the end, and you have to reboot manually again.
This is a known side effect because stock recovery is not exactly the same as your version, but it's not a problem.
After the FIRST (and only the FIRST) OTA update, should you go back S-On, because hboot 1.55 has a patch that will force TAMPERED to come back if you go from s-off to s-on.
NB: after the first OTA, you're phone will be 100% stock.
If you have any trouble (hopefully not), post back in my thread, as I get instant notifications on that (and if i'm still awake, i'm 2 hours ahead), and I'll try to help out.
Cheers.
---------- Post added at 06:50 PM ---------- Previous post was at 06:48 PM ----------
stanny2k said:
Oh, and have a "thanks"
Click to expand...
Click to collapse
Thanks, I like those

nkk71 said:
I'm going to recommend this CWM recovery, just cause the newer versions are taking close to an hour to backup/restore:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD: 1c6afb14db3f305b0ad7d85d5af80bef
Click to expand...
Click to collapse
Ok, I'll grab this!
nkk71 said:
Also, please follow the instruction properly, no jumping, skipping or adding steps
Click to expand...
Click to collapse
Will do! Don't worry, word for word!
nkk71 said:
The only slightly tricky part (as mentioned), is in Step 6, where when the phone reboots to "stock recovery" it could hang somewhere between 25% to 50%, and you have to manually reboot, and (possibly) again towards the end, and you have to reboot manually again.
This is a known side effect because stock recovery is not exactly the same as your version, but it's not a problem.
Click to expand...
Click to collapse
Noted.
nkk71 said:
After the FIRST (and only the FIRST) OTA update, should you go back S-On, because hboot 1.55 has a patch that will force TAMPERED to come back if you go from s-off to s-on.
NB: after the first OTA, you're phone will be 100% stock.
Click to expand...
Click to collapse
When you say "should you go back S-On" do I let the first OTA update install, then manually go back to S-ON, then let the other updates install once I've got S-ON back?
nkk71 said:
If you have any trouble (hopefully not), post back in my thread, as I get instant notifications on that (and if i'm still awake, i'm 2 hours ahead), and I'll try to help out.
Cheers.
Click to expand...
Click to collapse
Appreciate it, thank you

stanny2k said:
When you say "should you go back S-On" do I let the first OTA update install, then manually go back to S-ON, then let the other updates install once I've got S-ON back?
Click to expand...
Click to collapse
yep, exactly, after the 1st OTA, your phone will be 100% "out-of-the-box"; once the OTA updates successfully it will mean
1- your entire firmware was updated (hboot, recovery, kernel, radio, etc)
2- your ROM will also be updated, proving everything is 100%
otherwise, the OTA would not be able to complete.
Now due to a patch in later hboots (in particular 1.55 as far as i know), going from s-off to s-on, will (after a few reboots) result in "tamper detected - rebooting" and TAMPERED is back.
so in summary, if you really need to go S-On, you do so after first successful OTA (using the command mentioned in my guide), and then you can take any OTAs you like.
hope that makes sense

Perfect sense!
I'll have a bash at this tonight! Thanks a lot

Well, that was an eventful evening
Followed your guide to the letter. Everything went ok apart from a few things..
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
I then flashed the wrong stock recovery (recovery 1.28.401.7.img) so I had to unlock the bootloader again to flash a different one, thankfully the one I did flash (recovery 2.24.771.3 - TRE.img), which matched the first OTA update, everything installed fine after that
Thanks a lot mate. I'll happy to send my device away for repair with no worries now.
Regards, Ryan

stanny2k said:
Well, that was an eventful evening
Followed your guide to the letter. Everything went ok apart from a few things..
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
I then flashed the wrong stock recovery (recovery 1.28.401.7.img) so I had to unlock the bootloader again to flash a different one, thankfully the one I did flash (recovery 2.24.771.3 - TRE.img), which matched the first OTA update, everything installed fine after that
Thanks a lot mate. I'll happy to send my device away for repair with no worries now.
Regards, Ryan
Click to expand...
Click to collapse
Sorry to hear you had some troubles , are you on Windows 8 or 8.1, is that why adb wasn't working.
Also have a two questions about stock recovery you used,
1- when you used 1.28.401.7 the OTA didnt work, or you didnt try?
2- when you used 2.24.771.3 did the OTA hang at any point, or did it reboot (twice, I believe), correctly and by itself?
would be nice if you could give me some more info, it would probably be helpful to others too.
Thanks

nkk71 said:
Sorry to hear you had some troubles , are you on Windows 8 or 8.1, is that why adb wasn't working.
Also have a two questions about stock recovery you used,
1- when you used 1.28.401.7 the OTA didnt work, or you didnt try?
2- when you used 2.24.771.3 did the OTA hang at any point, or did it reboot (twice, I believe), correctly and by itself?
would be nice if you could give me some more info, it would probably be helpful to others too.
Thanks
Click to expand...
Click to collapse
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.

stanny2k said:
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
Click to expand...
Click to collapse
hmm: it just hung on the "Entering Recovery" screenit just hung on the "Entering Recovery" screen
did you do a "fastboot erase cache", after flashing it? that's usually the only reason it could get stuck (or perhaps a corrupt download, did you check MD5; i've had some issues downloading from dev-host sometimes).
But thanks anyway, glad all worked out, and hope you get your device back soon
cheers.

nkk71 said:
hmm: it just hung on the "Entering Recovery" screenit just hung on the "Entering Recovery" screen
did you do a "fastboot erase cache", after flashing it? that's usually the only reason it could get stuck (or perhaps a corrupt download, did you check MD5; i've had some issues downloading from dev-host sometimes).
But thanks anyway, glad all worked out, and hope you get your device back soon
cheers.
Click to expand...
Click to collapse
Yup, I did fastboot erase cache before and after flashing it, both were successful as well. I didnt check the MD5, I just installed it after I downloaded it.. it was midnight by the time I got that far! I was tired!
Yeah and thanks a lot for your help mate. Really appreciate it.
I'll let you know the outcome with HTC Hopefully they find nothing untoward!

stanny2k said:
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
Click to expand...
Click to collapse
Sorry, one last question, when you manually rebooted, did you have to keep holding VOLDOWN during boot-up, or did it enter stock recovery by itself

nkk71 said:
Sorry, one last question, when you manually rebooted, did you have to keep holding VOLDOWN during boot-up, or did it enter stock recovery by itself
Click to expand...
Click to collapse
I'm not sure if it enters recovery by itself as I just followed your guide of holding VOLDOWN
My thumbs were killing me by the end of the night!

stanny2k said:
I'm not sure if it enters recovery by itself as I just followed your guide of holding VOLDOWN
My thumbs were killing me by the end of the night!
Click to expand...
Click to collapse
finger gymnastics :laugh:

stanny2k said:
Well, that was an eventful evening
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
Click to expand...
Click to collapse
Looks like I have to express my apologies on that, I believe I found the problem; the "quicker way"
I really should avoid those shortcuts, until I've tested them 100% (or at least 98%).... I'll let you know what the problem was / is when i update the guide, and sorry again for the headache!!

nkk71 said:
Looks like I have to express my apologies on that, I believe I found the problem; the "quicker way"
I really should avoid those shortcuts, until I've tested them 100% (or at least 98%).... I'll let you know what the problem was / is when i update the guide, and sorry again for the headache!!
Click to expand...
Click to collapse
:laugh: thats alright mate. No issues.
Let me know once you've updated the guide and I'll take a look at it

stanny2k said:
:laugh: thats alright mate. No issues.
Let me know once you've updated the guide and I'll take a look at it
Click to expand...
Click to collapse
problem is with the CWM i recommended, works just fine when flashed, but when using "fastboot boot CWM.img" looks like 6.0.3.2 doesnt work properly with adb, 6.0.4.5 on the other hand works with "fastboot boot"
I'll update my guide with some more "visuals" whenever I get a chance....

[Q] Htc One X Unique problem

So Long story short, I have an Htx one x(l) evita,
the wifi was not working at all(I assumed firmware issue) so I tried to flash the stock rom,
Unlocked bootloader and tampered are effective but NOT S-off(it is S-on) I tried to flash a custom rom(its rooted as well) against my better judgement, NOW the issue is it is not bricked, it reads through adb, loads to bootloader, but there is NO OS, when going through the files, the folders are there, however it will not go past the HTC splash, it reboots to my teamwin recovery OR recovery page(3 androids on bottom of the screen)
Since I bought this phone used, and now tampered with it, what are my options? When in teamwin I can do almost anything but restore has an empty folder, and when I go into the advanced. to fix permissions, it fails.
Any thoughts? ASIDE stop flashing roms, ( believe me, when or If I get this fixed, I am done playing with htc roms, samsungs are so much easier)
any help is greatly appreciated

waynold78 said:
So Long story short, I have an Htx one x(l) evita,
the wifi was not working at all(I assumed firmware issue) so I tried to flash the stock rom,
Unlocked bootloader and tampered are effective but NOT S-off(it is S-on) I tried to flash a custom rom(its rooted as well) against my better judgement, NOW the issue is it is not bricked, it reads through adb, loads to bootloader, but there is NO OS, when going through the files, the folders are there, however it will not go past the HTC splash, it reboots to my teamwin recovery OR recovery page(3 androids on bottom of the screen)
Since I bought this phone used, and now tampered with it, what are my options? When in teamwin I can do almost anything but restore has an empty folder, and when I go into the advanced. to fix permissions, it fails.
Any thoughts? ASIDE stop flashing roms, ( believe me, when or If I get this fixed, I am done playing with htc roms, samsungs are so much easier)
any help is greatly appreciated
Click to expand...
Click to collapse
wrong forum this is for HTC One M7, here's One X: http://forum.xda-developers.com/htc-one-x

nkk71 said:
wrong forum this is for HTC One M7, here's One X: http://forum.xda-developers.com/htc-one-x
Click to expand...
Click to collapse
@waynold78
btw you linked him to the Htc X Endeavoru forum, he need HTC One X(l) evita
Guess he will be redirected again lol

alray said:
@waynold78
btw you linked him to the Htc X Endeavoru forum, he need HTC One X(l) evita
Guess he will be redirected again lol
Click to expand...
Click to collapse
Thank you alray , I found it after, I tried to msg back asking a moderator to close this particular thread, but it said I had to wait, and I forgot to come back, lol...I have had alot of help and some progress is being made finally,

waynold78 said:
Thank you alray , I found it after, I tried to msg back asking a moderator to close this particular thread, but it said I had to wait, and I forgot to come back, lol...I have had alot of help and some progress is being made finally,
Click to expand...
Click to collapse
np, glad you find help there. Good luck with your X, mine died after 1 year only and I had lot of hardware issues with it .... btw if you need parts for your X let me know by pm

I may as well close this one as you've got your thread in the correct forum now
Thread Closed
Sent from my HTC One via XDA Premium

[Q] Phone reboots on HTC setup screen after flashing.

I was having trouble flashing the newest Viper Rom for my phone and decided to wipe everything and flash the Bad Boyz 4.4.2 Sense 6 using Philz Recovery. After flashing and rebooting I can unlock my phone but it is stuck on the "HTC" screen. After waiting a while it will go into set up, asking me for language and wi-fi connection, but then I get an error that says "process com.htcdialer isn't responding and then my phone reboots. Been doing the same thing for about an hour. Please help.
Edit: Actually I will get the error once and press wait or ok then it will go away. Then it will come back and that's when my phone restarts. Also if I leave my phone alone and do nothing it reboots on its own.
SOLVED: Seemed there was nothing I could do but run an RUU. Do not use the 4.06.651.4_RUU that was recently posted as there are still some issues with it. I used the 3.04.651.2 one and updated from there. After updating to 4.2.2 again I unlocked my bootloader again and ran the Dirty Unicorn ROM as I was too scared to rerun the Viper ROM lol. Worked out great. Thanks for the help.

zasuncion said:
I was having trouble flashing the newest Viper Rom for my phone and decided to wipe everything and flash the Bad Boyz 4.4.2 Sense 6 using Philz Recovery. After flashing and rebooting I can unlock my phone but it is stuck on the "HTC" screen. After waiting a while it will go into set up, asking me for language and wi-fi connection, but then I get an error that says "process com.htcdialer isn't responding and then my phone reboots. Been doing the same thing for about an hour. Please help.
Edit: Actually I will get the error once and press wait or ok then it will go away. Then it will come back and that's when my phone restarts.
Click to expand...
Click to collapse
This is exactly where Im stuck at currently. I went ahead and did a factory reset as I had flashed more than one rom already and I was thinking that one of the roms was the culprit. I flashed Android Revolution 53.0 HD and I think I didnt flash the correct zip for my phone. Jus got off work and havn't picked up the phone yet to try again, Im about to now though, hopefully somebody can help us get past this...

I wonder if your both using Philz, I'm on TWRP 2.7.0.0 and no problems, but I wonder if flashing other roms could be the culprit.
When I go from sense 6 to previous versions or vice verse, I always use superwipe:
http://forum.xda-developers.com/showthread.php?t=2237021
See if that works.
Sent from my HTCONE using Tapatalk 2

predator1584 said:
I wonder if your both using Philz, I'm on TWRP 2.7.0.0 and no problems, but I wonder if flashing other roms could be the culprit.
When I go from sense 6 to previous versions or vice verse, I always use superwipe:
http://forum.xda-developers.com/showthread.php?t=2237021
See if that works.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
Back from eating out with the girlfriend -_-...And now Im thinking maybe its my (our?) hboot. Im going to try flashing it down to 1.44 and seeing if that does anything. Mine is currently 1.56 and when I run RUU.exe i get the error 155... Here goes nothing...
Results:
M7_WLS PVT SHIP S-ON RH
CID-SPCS_001
HBOOT-1.44.0000
OPENDSP-V32.120.274.0909
EMMC-BOOT
MAY 8 2013,16:30:08:-1
Now with the hex modified hboot I just flashed I know its designed to appear to be locked and s-on, but what has legit changed besides my hboot version? It appears my dat has changed and my opendsp, whatever that is... What would be my next step now that I am 1.44? About to run the RUU again (stock) and see what happens...
Edit#2: Forgot that my phone is no longer recognized by my pc... so Im gonna update drivers again and see if that will allow me to run the RUU.exe

I'm on hboot 1.56, you guys wipe system in between differing versions of sense right??
A ghetto way to temp fix it, you could download a ROM with same sense version and extract the htcdialer.apk and put that in system/app/
Not sure if that will give different results but I'm currently driving 300 miles, will check back in later
Sent from my HTCONE using Tapatalk 2

:crying:
predator1584 said:
I wonder if your both using Philz, I'm on TWRP 2.7.0.0 and no problems, but I wonder if flashing other roms could be the culprit.
When I go from sense 6 to previous versions or vice verse, I always use superwipe:
http://forum.xda-developers.com/showthread.php?t=2237021
See if that works.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
I definitely didnt superwipe. Maybe thats my issue. I won't be home for another couple of hours. I'll try this as soon as possible. Thank you.
Also I got passed the htc set up but I dont have any network service. i'll update asap.
EDIT: I can't seem to use superwipe either. I get a message saying
assert failed: getprop("ro.product.device") == "m7wls" (Status 7)
Click to expand...
Click to collapse