Related
Hello
Few days ago I was prompted to install update 2.10.405.2. After the installation I can't enable wifi anymore; it simply says error. I just got my phone 2 weeks ago on an Orange contract (from mobiles.co.uk), but when I contacted HTC they said that my phone should be a branded and locked O2 Desire. HTC said that because my phone was unbranded the update messed my phone. Is that possible?
I noticed that quite a few people are affected by this, but the guy from HTC wouldn't say if they are aware of this problem or if they are working on a fix. They "escalated" the call but haven't contacted me back yet.
Is there a way to simply uninstall the update?
I read this post http://forum.xda-developers.com/showthread.php?t=779787 but I wouldn't want to downgrade to 2.1 (I just got this phone 2 weeks ago, plus this is my first Android so...) wouldn't that invalidate my warranty ?
Please advise,
Thanks
If your Desire was a previously branded handset then you need your gold card in the unit for ALL updates. This is why the handset is having issues...
I didn't know that.
Why was I given a previously branded phone in the first place, if this could cause problems like this?
Anyway, I made my main microSD card a gold card now... for future updates. Does this gold card just needs to be in the device when you update, or you need to do something else as well ?
Is there a way to simply uninstall this bloody update?
You just need the gold card in the unit...Don't suppose you happen to know the software version that was on the unit when you got it do you?
Unfortunately no. But this was the first and only update that I got, if that helps.
Same issue here, is a hard reset/reflash the only solution? I'd rather not lose my files and stuff, ofcourse.
It would be either 1.21.405.2 or 2.09.405.8 I'd imagine...
CPW own mobiles.co.uk so it should've been an unbranded device - mine was from a CPW store and was unbranded - so it may have not been a branded unit. Follow this guide and if it completes with no issues you're on an unbranded unit (it will roll you back to Android 2.1 and you can then flash the Android 2.2 RUU file directly (or try the OTA update again)*
http://forum.xda-developers.com/showthread.php?t=768256
* You will lose all data, mind, so backup what you need before doing this
Will this invalidate my warranty?
I also contacted mobiles.co.uk (as HTC suggested) to ask them why on HTC database my phone apears as a branded O2 phone, but still got no answer from them. You are saying that it should have been an unbranded Desire ?
No it won't, if it completes then you've got a generic Desire and that guide puts you back to stock 2.1...you can then update again to 2.2 and HTC won't know a thing...
I'm saying it should have been an unbranded Desire going from my experience of CPW - that's not to say EVERY Desire will be unbranded as it depends where they got the stock from
Quote from post : [HOWTO] Downgrade Froyo (2.2) to Stock 2.1 (ANY HBOOT | WIN/LINUX/MAC | ROOT)
"Further Information
If you want to flash an alternative RUU (e.g. a branded 2.1 release), just skip the downgrade section at the end by pressing vol-down on the phone when the utility has completed. Then reboot the phone and run the RUU you want. If you have an SLCD screen you should be very careful here - most RUUs don't support the screen."
Question: Do I need to skip the downgrade?
My model number is HTC Desire A8181 - is this with SLCD screen?
I have downloaded RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed.exe
Is this ok to flash after this process?
Sorry, I am a novice (got the phone 2 weeks ago) and did not expect to bump into problems like this so early.
Please help, I wouldn't want to brick my phone.
The guide downgrades you to the stock 1.21.405.2 ROM which is fine for SLCD screens. You can then either use that RUU or just do the OTA update again - whichever you prefer (personally, I use the RUU)
There should be no issues if you follow the guide to the letter
Other thing to try first, though, is a hard reset - it might fix it for you
Just did a hard-reset. It didn't help. Will try downgrading and let you know how it went.
I did the downgrade and now the wireless is working again )
I'm flashing that RUU now
Thanks so much EddyOS
No worries matey, just keep the gold card in the phone and you shouldn't have issue in future
I had the same problem.
No WiFi and hotspot after ota.
This because i forgot to put in my goldcard...
Easiest way to fix it is to make a goldcard, then get the .zip file from the 2.10.405.2 update and place it on the goldcard.
Rename it update.zip.
Put the goldcard in your phone.
Then enter recovery mode (reboot your phone, when turning on hold the lock button and volume down button)
Select recovery in the menu you get, then wait, after a while it shows you a few options. Choose the option to run the update.zip.
Done, everything works perfectly.
Its really easy, only making the goldcard out of an SD requires a little searching/reading.
Good luck!
Edit: forgot to say it doesnt erase any data, like apps and contacts.
Just be sure if you use your current SD card as goldcard to copy everything to your pc before making it. Then you can put it back later on.
Finaly back to the latest 2.2 Android. Updated using OTA.
Tried updating with RUU but for some reason after the RUU rebooted the phone to start the update, the phone got stuck on the HTC screen and the RUU timed out; tried it several times.
But I'm back on track now.
Will keep the goldcard in at all times. Lesson learned the hard way.
DaannRoz - unfortunately I already did the hard-reset...
Thanks everybody.
Thanks DaannRoz
I put a new 16gb into my phone a while back and put it through the gold card process so I thought it should work. It didnt and I got the Wifi error code. I put the original gold card in and went through the steps you provided and got my Wifi back. It saved me from reflashing the phone and wiping out all my apps and data.
I anyone gets a picture of a phone with a red triangle and a apostrophe in it you need to push and hold the volume key up and then press the power button to get to the rom select screen.
Thanks Daan..
Just stuffed my Desire. Will try the update via recovery @ home.
BTW is this the update you want me to do ??
http: / / fotadl.htc.com/OTA_Bravo_HTC_EU_2.10.405.2-2.09.405.8_releaseol2djq7rqarka2ka.zip[/url]
Cheers,
Sai
Thanks Daan...now my Wifi works...
@Sai> I used the link provided by you..thnx.. (Hope its an original one!!!)
saro
I got the same issue. After reapplying the update with an update.zip and the recovery mode --with gold card inside at this moment-- everything goes fine and my WiFi works again...
Hi
I've downloaded an HTC Europe 1.15 RRU that I used before and worked.
Now, however, it wont flash. I just get to the "waiting for bootloader" and then a "connection error". I tried rebooting into bootloader but then the RRU just counts upto 100 and then tells me there is a connection error.
The difference between now and last time is that I've updated my bootloader to Alpha-Rev bootloader and Clockwork Mod Recovery is installed. The phone is rooted and S-OFF as well.
I'm trying to restore the phone to factory condition in preparation for a return to HTC for repair.
I guess I need to resintall some bootloader and recovery mod?? or is that in the RUU?
Any ideas/advice?
Android version 2.2
Baseband 32.47.00.32U_5.10.05.23
Kernel 2.6.32.15-gf5a401c
Build 2.29.405.2 CL263770 release-keys
Software: DJ Droid v1.8 (but also tried latest MoDaco, Pinky, CM6 and LeeDroid)
Browser: WebKit 3.1
HBOOT 0.93.0001
BRAVO PVT3 SHIP S-OFF
MICROP-051d
TOUCH PANEL-SYNW0101
Clockwork Recovery v2.5.0.7
Why do you want to put the FIRST ever RUU back onto your device? Just download the latest RUU (2.29.405.2) by clicking on my signature. This is assuming your phone in unbranded from the start, if not you'll need to get the RUU for your operator
Er, because I said ...
"I'm trying to restore the phone to factory condition in preparation for a return to HTC for repair"
Factory condition means ANY ROM that was meant for the unit - you don't need to go back to the first!!! So long as you're on an x.xx.405.x ROM you'll be fine!!! LMAO!!!
If you just flash the 2.29.405.2 RUU then you're back to stock so the factory will accept it
bloody hell.
saved me a ****ty weekend there pal.
nice1
cheers
will do this tonight and report back.
My HBOOT is 0.93.001 (flashed using alpha-rev clockword mod install utility). Some older RUUs refuse to load (waiting for bootloader and a reboot to bootloader whilst the RRU is still running - doesnt fix the problem). Appears to be waiting for a special signature from the bootloader. Is your link (RRU) likely to work do youo know ??
If you're currently S-OFF, which I assume you are, then get this file instead:
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.zip
It's the same RUU but in ZIP form. Once downloaded remove everything from the name except PB99IMG (so the file is effectively called PB99IMG.zip) and copy it to the root of your SD card. Then boot into HBOOT and it will read the ZIP and ask you to continue. Say yes and once done reboot and you'll be back to stock. Then just remove the ZIP from the SD card and away you go!
Word of advice: I was S-OFF and using the N1Table and the first time I ran this it failed on the System partition and got stuck on the white HTC screen. I left it an hour, ran the PB99IMG again and it completed so if you are on anything other than the stock table I'd go back to that first using the file from AlphaRev before running the ZIP
Either way you should be fine
Yeah S-OFF.
I'm okay with the PB99 - used that when creating gold card and downgrading.
The N1Table stuf is new to me. I'll google that now.
Thanks for the tip and link.
Cheers pal.
**EDIT:
Okay, so N1table is the partition table for sram/nvram chips.
I have not knowingly modified these, but in any event will grab
the stock HTC table just in case. I can only assume the hangup
is generated because the partition table is hardcoded in the RRU
rather than being read in by the RRU - or something like that.
Anyway, thanks once again pal.
[Q] The phone was purchased on the UK Orange network although no branding on the phone (orange square logo and orange applications). The phone was locked to the Orange network and the settings SLIGHTLY different than the unbranded phone my bro has. Will I need to get hold of the Orange RRU before sending to HTC for repair (as in will the IMEI number be registered to Orange or something)?
If it had the Orange ROM on it then you will need that before sending it back...now, an Orange RUU has never surfaced BUT I might know someone getting one today so if I hear anything I'll post back on here.
If you needed a gold card to flash the stock RUU then you will need the Orange RUU
With regards to S-OFF, unless you downloaded and flashed a new table you will still be on the stock Desire one
I used alpha-rev' s-off utility (cant recall the link and didnt save it) but unsure whether the table has been modified. I'll just download the HTC one. Simples.
DAMM. I thought I may need the Orange RUU. Yes, the stock RRU wouldnt install I recall; required a gold card and a bootloader downgrade as I remember. ****!
I've been searching for Orange RUU for months to no avail.
As I said, hold out a day or so as I think someone might be getting it from Orange
Leave it with me...
Acknowledged
My gracious thanks in advance.
Good luck!
Eddy if you get a stock Orange RUU you will be god . Hope you get it.
Sent from my HTC Desire using XDA App
It won't be me but apparently someone is getting an Orange techie to debrand his phone and he's getting the RUU in case he needs to go back to stock...as soon as I hear something I'll update
ste1164 said:
Eddy if you get a stock Orange RUU you will be god . Hope you get it.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
+1 for Eddy being God
EddyOS said:
It won't be me but apparently someone is getting an Orange techie to debrand his phone and he's getting the RUU in case he needs to go back to stock...as soon as I hear something I'll update
Click to expand...
Click to collapse
Hang on; dya mean its possible to create an RUU or backup of a branded Orange phone - as indeed I had before I rooted et.al. ? Oh no, could I have created one - surely not ?
EddyOS said:
If you're currently S-OFF, which I assume you are, then get this file instead:
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.zip
It's the same RUU but in ZIP form. Once downloaded remove everything from the name except PB99IMG (so the file is effectively called PB99IMG.zip) and copy it to the root of your SD card. Then boot into HBOOT and it will read the ZIP and ask you to continue. Say yes and once done reboot and you'll be back to stock. Then just remove the ZIP from the SD card and away you go!
Word of advice: I was S-OFF and using the N1Table and the first time I ran this it failed on the System partition and got stuck on the white HTC screen. I left it an hour, ran the PB99IMG again and it completed so if you are on anything other than the stock table I'd go back to that first using the file from AlphaRev before running the ZIP
Either way you should be fine
Click to expand...
Click to collapse
Nice1 Eddy. The ZIP did the trick. The RRU method didnt work but I expected that as it was looking for an original HBOOT signature.
So, back to HTC stock. Not sure whether they would accept it for repair though given that it was sold as a branded Orange handset. Can they check?
Well, I will give this a go. The reason for the repair is that I've installed god knows how many custom ROMs and:
1. wifi doesnt always work.
2. Data connection errors.
3. Random reboots.
4. 90% reboot when navigating in the car.
5. Failure to answer some incoming calls.
6. Sometimes outgoing calls carry no voice modulation (they cant hear me)
different problems depending on ROMs.
So, lets see how the stock does before I decide to send back/or not.
Thanks again Eddy.
No, the bloke at Orange is going to give the guy getting it debranded the Orange RUU so he can go back to stock if he needs to...
HTC can tell, and my still fix it and put the Orange ROM back on it, but they may also turn around and refuse to fix it due to having a different ROM to the original
You can get to stock Orange with a very complicated method. After debranding you would root the phone. Then apply the backup on my thread. You then remove the superuser.apk with adb. You then flash the two updates orange released this unroots your phone back to stock.
Sent from my HTC Desire using XDA App
Nice1 Ste, however, mine is SLCD not Amoled. The nandroid is from an Amoled handset. Wont work with mine. Nice idea tho.
Anyone have a nandroid from an Orange set??
Hello people.
An android newbie here. I have beem doing quite a bit of reading on this forum, but this is my first time posting. I have looked around all over the place and I have reached a point where I am confused of how to go about the task I am wanting to accomplish. Here goes:
I bought a desire HD on vodafone last week, it had 1.75.161.2 firmware on it. I stumbled across these forums and decided to flash a custom ROM (Leedroid). I was successful a this task, but now i have a charging problem with my phone. If i understand correctly, my warranty is void with a custom ROM, so I would like to know how i could get back to my stock Vodafone ROM (1.75.161.2), also with the branded vodafone logo that used to appear before i flashed to custom ROM.
Again, sorry if there is stuff about this posted elsewhere, I have been reading, but i am really confused.
Any help would be appreciated.
Regards
You have to run a RUU if you want to return to stock.
I don't have any links to official RUUs atm, but check the threads in the android developement section. There should be one with vodafone branding
Sent from my Desire HD using Tapatalk
Flussen said:
You have to run a RUU if you want to return to stock.
I don't have any links to official RUUs atm, but check the threads in the android developement section. There should be one with vodafone branding
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply.
I have installed a Vodafone branded RUU, I have also found a Vodafone backup which I have tried. I get the branding back, but I cannot get any updates OTA. I'm now on 1.39.161.1. There clearly is a 1.75 update on Vodafone, I used to be on it and my friends are on it.
Any help for me to receive these OTA updates?
Regards
I think 1.75 was pulled by HTC at the same time as the 1.72 update, due to some major bugs.
Sent from my Desire HD using XDA Premium App
M
nickhammond121 said:
I think 1.75 was pulled by HTC at the same time as the 1.72 update, due to some major bugs.
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
Vodafone website states 1.75 is the latest. Last week I had 1.75 I don't think 1.75 was pulled. 1.72 was definitely pulled.
http://help.vodafone.co.uk/system/selfservice.controller?CMD=VIEW_ARTICLE&ARTICLE_ID=3818083&PARTITION_ID=1&CONFIGURATION=1058&CURRENT_CMD=BROWSE_TOPIC&PAGE_TITLE=Article%20Details
Anothe DHD noob question here. I bought a DHD off eBay and I know it is locked to Vodafone, but I'm not sure if it's branded. If I don't get the Vodafone logo when I switch it on does that mean it's not branded?
Check the firmwareversion. If it's like 1.32.405.3 it's unbranded. The important part is .405. That means that it's unbranded.
Sent from my Desire HD using Tapatalk
It's 1.72.405.3
So it's unbranded but I need to downgrade in order to root and S-OFF etc?
Yes, you need to downgrade it to 1.32. But you don't need to create a gold card
Sent from my Desire HD using Tapatalk
Hi, I've the same problem, I need to get back to voda 1.75
First of all, did you used hboot S-OFF or radio S-OFF ?? Because if you used hboot you won't be able to recover the original boot to S-ON and your phone will be out of warranty regardless of the ROM it has installed.
As I understand it, if you've flashed the 1.39 branded RUU back to the phone that should've give you the stock vodafone recovery wich is what is needed in order to get Voda Branded OTA updates, am I right?
So I don't get why aren't you receiving the 1.75 OTA, do you have superCID?
Anyone knows if there is a 1.75 Voda RUU available somewhere to flash manually?
dadon123 said:
Thanks for your reply.
I have installed a Vodafone branded RUU, I have also found a Vodafone backup which I have tried. I get the branding back, but I cannot get any updates OTA. I'm now on 1.39.161.1. There clearly is a 1.75 update on Vodafone, I used to be on it and my friends are on it.
Any help for me to receive these OTA updates?
Regards
Click to expand...
Click to collapse
Pitchb3nd said:
Hi, I've the same problem, I need to get back to voda 1.75
First of all, did you used hboot S-OFF or radio S-OFF ?? Because if you used hboot you won't be able to recover the original boot to S-ON and your phone will be out of warranty regardless of the ROM it has installed.
As I understand it, if you've flashed the 1.39 branded RUU back to the phone that should've give you the stock vodafone recovery wich is what is needed in order to get Voda Branded OTA updates, am I right?
So I don't get why aren't you receiving the 1.75 OTA, do you have superCID?
Anyone knows if there is a 1.75 Voda RUU available somewhere to flash manually?
Click to expand...
Click to collapse
Hi.
Looks like we're stuck in the same boat! I have reflashed the original radio and the original hboot. Also put my cid to stock (VODAP001), and turned radio s-on. Reflashed clockworkmod recovery to original stock recovery, got the phone back to 100% the way it was when I took it out of the box, yet still I cannot get the OTA update to 1.75.161.2
I'm on 1.39.161.1, stock Vodafone UK firmware. I followed a guide off another forum (german forum) nd thanks to Google translator I managed to follow the steps. But still stuck at the OTA issue.
yep, so it seems.
Could you post the link to that thread on the german forum?
Thanks
dadon123 said:
Hi.
Looks like we're stuck in the same boat! I have reflashed the original radio and the original hboot. Also put my cid to stock (VODAP001), and turned radio s-on. Reflashed clockworkmod recovery to original stock recovery, got the phone back to 100% the way it was when I took it out of the box, yet still I cannot get the OTA update to 1.75.161.2
I'm on 1.39.161.1, stock Vodafone UK firmware. I followed a guide off another forum (german forum) nd thanks to Google translator I managed to follow the steps. But still stuck at the OTA issue.
Click to expand...
Click to collapse
http://translate.googleusercontent.com/translate_c?hl=en&sl=de&u=http://www.handy-faq.de/forum/htc_desire_hd_forum/190019-htc_desire_hd_originalzustand_auslieferungszustand_wiederherstellen.html&prev=/search%3Fq%3D1.75.161.2%2Bvodafone%2Buk%2Bruu%26hl%3Den%26safe%3Doff%26rlz%3D1B3GGLL_en-GBGB379GB379%26prmd%3Divnsfd&rurl=translate.google.co.uk&usg=ALkJrhhBi3KYTytikXPK9TRzc9bFaCDKaA
There you go. Its the second set of instructions which i followed Have a gander.
Hi guys,
Sorry to dig this one up but I've hit a bit of a snag with my phone and could do with some assistance.
I got the phone originally with a Vodafone ROM and decided to debrand it to a plain HTC ROM - 1.72 using a de-brand pack I got from Fonefunshop. It appears that based on the fact the phone still has a Vodafone serial number but a HTC ROM I cannot receive OTA updates (I want Gingerbread ) then I need to revert back to stock. Ironically Vodafone released 2.3 earlier than HTC which was annoying to say the least.
I've been hunting round for the stock Vodafone RUU for 1.36 but I don't know if I can downgrade for starters, nor can I find any Vodafone RUU files anywhere including on here nor on Stock-ROM's.
Can anyone give me some help with this?
When I bought my phone from Vodafone on contract in November it came unbranded and unlocked. Nothing to do with Vodafone at all, apart from the CID. So if you just flash back to the stock 1.32 ROM and change the CID to the Vodafone one which I think is VODA_0001 (Dont quote me on that, its off the top of my head but there is a thread here somewhere that has it in), then make your phone S-on to get the updates.
That way you will be completely stock.
I'm in the same boat too
Flashed the non-branded software when I got the phone last year. Now I can't get the OTA update to 2.3.
Does anyone have a link the the stock 1.32 ROM and also a guide on how to change the CID and to make the phone S-on to get the updates?
Thanks
Lee
Help
dadon123 said:
Thanks for your reply.
I have installed a Vodafone branded RUU, I have also found a Vodafone backup which I have tried. I get the branding back, but I cannot get any updates OTA. I'm now on 1.39.161.1. There clearly is a 1.75 update on Vodafone, I used to be on it and my friends are on it.
Any help for me to receive these OTA updates?
Regards
Click to expand...
Click to collapse
Please can you tell me where you found the Vodafone branded RUU. I really need it and haven't been able to find it anywhere.Thanks
Hi,
Im trying to restore my phone to stock, I am currently on ARHD rom and the phone is an Optus branded phone. I have flashed the stock recovery back on and re-locked the bootloader. I then ran the Optus RUU and it got to a screen on the phone saying HTC and the PC said Sending.. After about a minute it gave an error saying the RUU could not be installed.
Any idea on what I can do to fix it?
What was the exact error? If you've updated your bootloader then you won't be able to go back
Obispal said:
Hi,
Im trying to restore my phone to stock, I am currently on ARHD rom and the phone is an Optus branded phone. I have flashed the stock recovery back on and re-locked the bootloader. I then ran the Optus RUU and it got to a screen on the phone saying HTC and the PC said Sending.. After about a minute it gave an error saying the RUU could not be installed.
Any idea on what I can do to fix it?
Click to expand...
Click to collapse
You won't be able to run the RUU because if you have updated your Optus ROM from 1.26.980.3 t01.28.980.10 the HBOOT and in the RUU is .43 compared to the updated one which is .94 in which case will give you an error. You can't downgrade the HBOOT.
You can do 2 things:
!. wait for the 1.28.980.10 RUU to come out
or
2. if you made a backup of your ROM before flashing ARHD, restore that and then flash stock recovery and then re-lock the phone.
Same here but I'm on H3G UK of course updated 1.28.... But if I seen right now available on HTC.dev the 1.28 and many others have been uploaded
Sent from my HTC One X using xda premium
Why is my HTC One x (PROTOTYPE) stuck on ICS?
Hey guys, This is my first post ever on XDA so please forgive me if I sound like an idiot
I got hold of a HTC One x which was already had an unlocked bootloader, rooted and had CWM recovery installed. I was told that I have a prototype version of the one x. Anyway that is not issue. when I got the phone it was running android version 4.0.4 HTC Sense version 4.1 and I checked software update. The 3.14.401.27 OTA update was available so I proceeded with the update and after the reboot I found my phone stuck in a bootloop and the only way for me to sort it out was by restoring my nand back up from CWM. I really wanted the new Sense 5 UI and android jelly bean so I downloaded:
RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_TW_3.14.709.20_Rad io_5.1204.162.29_release_292865_signed.exe
My CID was HTC__621 thats why I downloaded that ruu but after flashing it not was I only stuck in a bootloop but also when I entered recovery mode it was just a blank black screen with the back lights on. I even flashed different versions of CWM recovery and TWRP which gave me the same black screen so I flashed the stock recovery.img which also gave me the same black screen. I thought me maybe a different Ruu would resolve this issue so I used 'JBFWTOOL21' to change my CID to '11111111' this allowed me to flash:
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radi o_5.1204.162.29_release_298897_signed.exe
&
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Ra dio_5.1204.162.29_release_302015_signed.exe
After trying both these ruu's I still found my device stuck in a bootloop. Next I downloaded 'Endeavoru_CustomRUU' this contained a 'rom.zip' which I belive was a jelly bean rom and said it would update my image version to '3.14.401.31' after flashing this ruu, my phone booted up past the 'HTC Quietly Brilliant' screen but into a black screen but I could hear the boot sound and knew it booted up but it still gave me a black screen. barre in mind this was the only rom that booted up and didn't get stuck in a bootloop but the downside was I had no picture on the screen it was literally pitch black with the backlight on when it went past the 'HTC Quietly Brilliant' boot screen. I didn't even see the one x boot animation. I could only hear the boot up sound and once it was booted up the notification LED would flash I was receiving network settings from my operator. That was about it. I booted into recovery to see wether that worked but unfortunatelly it was also still giving me a black screen. The only thing I could boot into without a problem was 'power button + volume down' which booted into bootloader in which I chose 'fastboot' to flash all these roms.
At this point I thought my device was soft bricked so I gave it to my friends father who happened to really good with his IT skills. He managed to change my device's CID from 'HTC__621' to 'HTC__001' after doing so he downloaded this ruu and flashed it:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radi o_2.1204.135.20_release_274900_signed.exe
This ruu turned out to work perfectly fine with my device. Everything functioned once again, the device was able to boot into recovery and boot normally without a hassle. I also discovered that this was the rom that I received my phone with which put me back to the start on android 4.0.4
I was really annoyed with the fact that I was stuck on ICS so I flashed the MaximusHD 21.1.0 rom and its boot.img which put me into a bootloop again. I also tried other custom roms such as Revolution and SD secxces which all put my phone in a bootloop even though I flashed their boot.img kernels. I knew that I required a hboot 1.33.0000 or above in order to flash jb roms so I used 'JBFWTOOL21' once again before flashing these custom roms to update my hboot from 1.12.0000 to 1.33.0000. so all these bootloops still occourd after doing all this and I just had to return back to ICS. barre in mind I only tried flashing JB roms as I want sense 5 so I don't know if a custom ics rom would work on my device as I havent tried it yet but I know for a full fact that none of the jb roms work on my device.
For those who are wondering here, I uploaded some pictures of my device just check the attachments. It has all the information you may want to know about my device (HTC One X PROTOTYPE).
I really hope someone can help me update to jelly bean and get sense 5 as I am frustrated from failing and being stuck in bootloops
If you read all of this I honestly appreciate it and I Thank you for it, I hope you can help me!
all you need to do is flash the stock recovery from this post>>>>>http://forum.xda-developers.com/showthread.php?t=1975140
I did that
nogotaclue said:
all you need to do is flash the stock recovery from this post>>>>>http://forum.xda-developers.com/showthread.php?t=1975140
Click to expand...
Click to collapse
Thank you for your input, but I already done that which resulted no success for me. The only way for me to overcome these black screens was by flashing:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
This makes my device fully functional again but it just leaves me locked on ICS because when do the OTA updates, Flash JB ruu's or even flash custom JB roms I just get stuck on bootloops. I don't seem to get one JB version of android working on my device. Thats why I'm here seeking for help from geniuses like yourself. At the moment my device is back on android 4.0.4 but thats about it. It works perfectly fine on this version but I just can't update no matter what way I try I end up in a bootloop
so you have a stock recovery now? and receive ota notifications?
Yes
nogotaclue said:
so you have a stock recovery now? and receive ota notifications?
Click to expand...
Click to collapse
Yes I do and if I proceed with the update it will install without any problems but once it reboots it will be stuck in a bootloop. I ended up returning back to ICS and ignoring the update prompts when get told to update my software.
here you can see the update notification I recieve:
sN_iPower said:
Yes I do and if I proceed with the update it will install without any problems but once it reboots it will be stuck in a bootloop. I ended up returning back to ICS and ignoring the update prompts when get told to update my software.
here you can see the update notification I recieve:
Click to expand...
Click to collapse
you could try installing the update and if it bootloops go into the bootloader, vol down and power, and do a factory reset from there
alright
nogotaclue said:
you could try installing the update and if it bootloops go into the bootloader, vol down and power, and do a factory reset from there
Click to expand...
Click to collapse
alright im going to try that now, I will get back to you once I done it
nogotaclue said:
you could try installing the update and if it bootloops go into the bootloader, vol down and power, and do a factory reset from there
Click to expand...
Click to collapse
I just tried everything you told me, and I still ended up in a boot loop now I have to flash
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
to return back to ICS
sN_iPower said:
I just tried everything you told me, and I still ended up in a boot loop now I have to flash
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
to return back to ICS
Click to expand...
Click to collapse
I'm curious why you first chose an asian ruu for your first attempt and then got the european ruu. there is another ruu available but I need you to answer the above first.
I have to go to work now so I won't be able to answer you, there is another ruu available for version number, it's the 18th one down the list, release 974956 http://www.androidruu.com/?developer=Endeavor
sN_iPower said:
Thank you for your input, but I already done that which resulted no success for me. The only way for me to overcome these black screens was by flashing:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
This makes my device fully functional again but it just leaves me locked on ICS because when do the OTA updates, Flash JB ruu's or even flash custom JB roms I just get stuck on bootloops. I don't seem to get one JB version of android working on my device. Thats why I'm here seeking for help from geniuses like yourself. At the moment my device is back on android 4.0.4 but thats about it. It works perfectly fine on this version but I just can't update no matter what way I try I end up in a bootloop
Click to expand...
Click to collapse
Lock you are S-OFF try fastboot writecid HTC__032 i think is something like this and see what will happend after applay update. Or try manualy update with this RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe after changeing the CID
The other way is manualy update your hboot to high version! Download from here firmware .zip for region 401 hboot1.31 and see what will happend
nogotaclue said:
I'm curious why you first chose an asian ruu for your first attempt and then got the european ruu. there is another ruu available but I need you to answer the above first.
I have to go to work now so I won't be able to answer you, there is another ruu available for version number, it's the 18th one down the list, release 974956 http://www.androidruu.com/?developer=Endeavor
Click to expand...
Click to collapse
I flashed the asian ruu first because my CID used to be HTC__621 which requires TW ruu's (I tried the JB one) also on the back of my device it says made in Taiwan. But after flashing the rom it didn't work and put me in a bootloop so I changed my CID to 11111111 and flashed the European ruu ( I tried the JB one) which also didn't work and ended up putting me in a bootloop. It was my friends father who then changed my CID to HTC__001 and flashed the European ICS ruu which worked flawlessly. Do think I should flash the ruu you recommended? because its a ICS ruu and I'm trying to get to JB. Anyway I really thank you for trying to help me, you are the only one who replied to me
Look at this image it shows you that my device was made in Taiwan
Thant said:
Lock you are S-OFF try fastboot writecid HTC__032 i think is something like this and see what will happend after applay update. Or try manualy update with this RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe after changeing the CID
The other way is manualy update your hboot to high version! Download from here firmware .zip for region 401 hboot1.31 and see what will happend
Click to expand...
Click to collapse
sN_iPower said:
I flashed the asian ruu first because my CID used to be HTC__621 which requires TW ruu's (I tried the JB one) also on the back of my device it says made in Taiwan. But after flashing the rom it didn't work and put me in a bootloop so I changed my CID to 11111111 and flashed the European ruu ( I tried the JB one) which also didn't work and ended up putting me in a bootloop. It was my friends father who then changed my CID to HTC__001 and flashed the European ICS ruu which worked flawlessly. Do think I should flash the ruu you recommended? because its a ICS ruu and I'm trying to get to JB. Anyway I really thank you for trying to help me, you are the only one who replied to me
Look at this image it shows you that my device was made in Taiwan
Click to expand...
Click to collapse
Actually @Thant replied also, try what he suggests at the bottom of his post to update your hboot, it's a different one to the one you tried, then try a higher ruu
I am wondering why everyone, OP and those attempting to assist, are assuming that what is apparently a prototype model of the One X would even be compatible with the updates.
If it is a prototype, regardless of how it identifies itself, it may have differences that simply prevent ANY of these software versions from operating.
I think that is one possibility the OP may have to be prepared for.
Tigerlight said:
I am wondering why everyone, OP and those attempting to assist, are assuming that what is apparently a prototype model of the One X would even be compatible with the updates.
If it is a prototype, regardless of how it identifies itself, it may have differences that simply prevent ANY of these software versions from operating.
I think that is one possibility the OP may have to be prepared for.
Click to expand...
Click to collapse
Maybe you are right he must to prepear and know the chance to broke his OneX is big because is prototype.
Tigerlight said:
I am wondering why everyone, OP and those attempting to assist, are assuming that what is apparently a prototype model of the One X would even be compatible with the updates.
If it is a prototype, regardless of how it identifies itself, it may have differences that simply prevent ANY of these software versions from operating.
I think that is one possibility the OP may have to be prepared for.
Click to expand...
Click to collapse
That had crossed my mind actually, but he is receiving ota notifications and the results he posted from "getvar all" indicate everything is as it should be, same model number even.
I have come across an early prototype before and the only 2 differences were the casing and slightly larger headphone jack socket. AFAIK the hardware was the same. Unfortunately, the one I saw wasn't working so I don't know what version of android it had
nogotaclue said:
I'm curious why you first chose an asian ruu for your first attempt and then got the european ruu. there is another ruu available but I need you to answer the above first.
I have to go to work now so I won't be able to answer you, there is another ruu available for version number, it's the 18th one down the list, release 974956 androidruu/?developer=Endeavor
Click to expand...
Click to collapse
Just to ask further: i dont see ruu for 4.19.707.3 (cid htc_044) on the site androidruu? I'm looking for it but yet to find, except for odexed/deodexed stock rom.
Sent from my HTC One X using xda app-developers app
xb2 said:
Just to ask further: i dont see ruu for 4.19.707.3 (cid htc_044) on the site androidruu? I'm looking for it but yet to find, except for odexed/deodexed stock rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
No more RUU only stock rom or nandroid. You never find that RUU because HTC never release this RUU.
Thant said:
No more RUU only stock rom or nandroid. You never find that RUU because HTC never release this RUU.
Click to expand...
Click to collapse
Ah, I see. Manual flashing stock rom is still ok anyway.
Thanks for the info, Thant
Sent from my HTC One X using xda app-developers app
Welcome... this had been discussed...
http://forum.xda-developers.com/showthread.php?t=2232063
I have Htc one x Prototype only ics no custom recovery no jb
hi, i have a htc one x protoype(engineer model) i have tried many times to install custom recovery and jb ruu but result is always same. bootloop and black screen. is someone can help. i know only xda members can help. so plz