Related
Hi,
I have HTC Desire that was rooted and I want to restore the ROM to factory default so I will be able to receive the FROYO OTA.
My BaseBand ver. is: 32.36.00.28U_4.06.00.02_2
Kernel ver. is: 2.6.29-82821fb5
I'll appreciate your help.
shpits said:
Hi,
I have HTC Desire that was rooted and I want to restore the ROM to factory default so I will be able to receive the FROYO OTA.
My BaseBand ver. is: 32.36.00.28U_4.06.00.02_2
Kernel ver. is: 2.6.29-82821fb5
I'll appreciate your help.
Click to expand...
Click to collapse
just flash one of the rooted ones from here
shpits said:
Hi,
I have HTC Desire that was rooted and I want to restore the ROM to factory default so I will be able to receive the FROYO OTA.
My BaseBand ver. is: 32.36.00.28U_4.06.00.02_2
Kernel ver. is: 2.6.29-82821fb5
I'll appreciate your help.
Click to expand...
Click to collapse
Put in the Goldcard and then run the official RUU (you can get one from here: http://forum.xda-developers.com/showpost.php?p=6703172&postcount=1)
It should let you install the stock 2.1. Then connect to wifi, go to settings->About Phone->System software updates and hit Check Now.
I did it that way, worked for me.
Thank you for the reply,
How can I be sure what is the ROM RUU that I need?
Hi AndroHero,
Can you please link me to the rooted versions you mentioned...
shpits said:
Thank you for the reply,
How can I be sure what is the ROM RUU that I need?
Click to expand...
Click to collapse
I used the WWE version (Link: http://shipped-roms.com/shipped/Bra...00.28U_4.06.00.02_2_release_126984_signed.exe). When i booted the 2.1 rom after going back to stock, I got options to choose the carrier so it could apply the internet and mms settings. Am on Voda UK. Didnn want to install the Voda ROM as i think voda always release the updates much later than the official releases. After setting up the 2.1, I did update and it worked.
Hi,
1. While installation i got an error message 171 (connection lost), it was waiting for the bootloader when it threw the error
2. I retried the whole process twice and the same thing happened.
Can any one assist me?
Thanks ahead.
shpits said:
Hi,
1. While installation i got an error message 171 (connection lost), it was waiting for the bootloader when it threw the error
2. I retried the whole process twice and the same thing happened.
Can any one assist me?
Thanks ahead.
Click to expand...
Click to collapse
Reboot the phone in fastboot mode, i think its press and hold the volume down button as you switch the phone on. then use volume keys to select fastboot and select it with the power button. When you leave this on there, run the RUU and it should work. WITH A GOLDCARD (IMPORTANT).
My desire is unlocked, why do I need a GOLDCARD?
I did exactly what you suggested. I moved it to fastboot but I still get the same
ERROR[171]:USB CONNECTION ERROR
This happens after the PC restart the device so it is not a 'physical Connection' issue.
I have my phone unlocked and the SIM working. From what I read, I need goldcard if I wan't to unclock my SIM...
Please advise
I successfully installed the RUU ROM, but I'm not getting the 2.2 OTA... What should I Do?
My phone is unbranded and unlocked, do I still need a gold card to restore to factory state for warranty purposes?
Sent from my HTC Desire using XDA App
If you purchased the Desire and it was on an x.xx.405.x software version then you don't need a gold card.
Don't people bother to actually absorb information as this is pretty n00b stuff...
I keep offering to help out with FAQs because this sort of information is not clearly stated. But thanks for letting me know. And I presume HTC read this forum and would know our tricks but apparently its still not a problem.
Sent from my HTC Desire using XDA App
EddyOS said:
If you purchased the Desire and it was on an x.xx.405.x software version then you don't need a gold card.
Don't people bother to actually absorb information as this is pretty n00b stuff...
Click to expand...
Click to collapse
How would anyone know what version of the software his phone had when he purchased it? I, for instance, knew nothing of the "rooting world" when I got my unbranded unlocked desire, so now, after the OTA upgrade, I don't think I can retrieve that information: am I correct?
In order to absorb information, someone has to give it to you. The process is long (for some longer maybe), but I'm sure you were a n00b once and I hope nobody treated you this way.
Luca
That is correct but if you'd read all threads/information logic would dictate that perhaps it's wise to make a note of what it comes with out the box and make sure you have a back up route in case things go pear shaped/need to be reversed. If all you've done is root the phone and not flashed a ROM then you can still check but if you're now on a custom ROM then you're kinda screwed (unless you just wanna be on an unbranded ROM then you can obviously so this).
Easy way of at least finding out if you're branded or not is to just try and flash a stock WWE RUU without a gold card - if it completes then you're unbranded
Yes, I was a n00b once (Android n00b April this year) but I didn't ask any questions - I just lurked and read other posts and learnt by others mistakes and only asked if I wasn't sure what I was doing. I've had previous mobile phones and so knew about checking version numbers so always make sure I know what I have before trying anything like rooting (or the equivalent term for other makes)
Thank you Eddie.
As a matter of fact, I haven't rooted the phone yet: still in the info gathering stage as I just purchased the phone a month ago. I come from "stupid" phones so never had this problem/opportunity before.
I know for a fact that my phone is not branded, but I don't know:
1) which is the software + radio I should download to restore my phone in case I don't like what I get with rooting;
2) which rom to install: in this specific case, the more you read, the more you get confused. I read some people installing the same rom and one saying it is slower than Luancher Pro + stock rom, others that claim that it is faster than anything they've ever tried (and, mind you, they are talking about the same rom!)
3) last but not least, all guides I found in Italian are relative to using unrevoked with windows 7, while I still run xp and it seems that xp poses some additional problems. I just created a virtual machine on my pc to start using ubuntu, but I never even seen the thing!
However, thanks for the help and sorry about being a little snappish in my previous post. I guess we all approach this problem with different attitudes: some would like it to be a real one-click easy procedure and so keep on asking until they find somebody who does it for them!
Ciao
Luca
Yeah I agree to anti-n00b remarks are getting really old. I'm sure many of us have tried searching threads and doing the right thing, so can we all just get over it? I've offered 6 times now to help create FAQs and not one of the anti-n00bs has offered to help.
Anyway, so I understand then that for those with unbranded / unlocked phones it is a simple matter to restore to factory state. Just thinking in case the USB connector broke or something, which worries me a lot because often connections are rather wobbly although I'm not sure how much that has to do with cheap cables or what.
Hi all, would like to know if, after installing a custom ROM, if i use a RUU will the recovery image be restored to default?
Thanks in advance!
Yes it Will
Yay! thank you! so just using the RUUs i will totally reset my desire, so HTC won't be able to tell if it's been rooted before?
Don't know whether they can't tell, whether they look if they've no need to I don't know...so long as it's on a stock ROM I don't think they'd check
lambdafreak said:
Hi all, would like to know if, after installing a custom ROM, if i use a RUU will the recovery image be restored to default?
Thanks in advance!
Click to expand...
Click to collapse
What is a RUU and how can I do it, as I'm having the same problem.
I rooted to allow Titanium Backup to have root after using unrevoked but wasn’t aware that meant I also had a custom rom installed now.
I’ve been told I need to RUU as well.
RUU = ROM Upgrade Utility
It's the official way of flashing a ROM. Each phone has a software version running on it when you first get it and you should make a note of the one on yours before doing anything root-related for the very reason that if something goes wrong you can revert back to stock. Not all versions are available, e.g. there are no Orange RUUs about, but the ones that are can be found here:
http://shipped-roms.com/index.php?category=android&model=Bravo
If you didn't happen to make a note of yours then it's hard to say what it came with. If you've only rooted and NOT flashed a new ROM yet then if you go to Settings>About phone>Software information and post the software version we might be able to help
Thanks for all the information it helps fill in some blanks.
I dont think I have put a different rom on it, I only rooted using revoked- does that mean it has a different rom now?
and my settings show
Android 2.2
Baseband version 32.46.00.32U_5.10.05.17_2
Kernel version 2.6.32.15-gd96f2c0 [email protected] #1
Build number 2.12.110.2 CL232610 release-keys
Software number 2.12.110.2
on a side note the link you posted - what do the numbers correspond to, my Kernel or build
Right you're on a T-Mobile FroYo ROM but the issue is there isn't that versions RUU available...how long have you had your Desire?
Damm.
I got mine in April this year, why do you ask.
Can I not use RUU_Bravo_Froyo_TMO_AT_2.12.112.1_Radio_32.46.00.32U_5.10.05.17_2_release_143754_signed.exe?
You CAN use that but it's the Austrian one...the reason I ask is to find out the screen type, you should be on an AMOLED screen so you can flash the older 1.21.110.4 RUU if you need to - you'll need a gold card to do it, though, I believe
http://shipped-roms.com/download.ph...00.28U_4.06.00.02_2_release_127570_signed.exe
If I do flash the older 1.21.110.4 version, are there any drawbacks, or will I just be able to update through OTA updates that will then be available to me through T-mobile to get me back to normal?
Also is there a best way to do this RUU as I have seen a few guides, can you recommend any to follow.
The way I'd do it is:
1. Download that RUU
2. Have gold card in your phone and HTC Sync installed on your PC
3. Connect phone to PC and select 'HTC Sync' from the options on the phone
4. Once HTC Sync on the PC shows connected, run the RUU
5. All being correct it'll flash the ROM
6. Assuming it's worked, you should get the OTA updates again as you did before
Replying on here and androidforums is getting confusing!!!
Thanks for all the help and I hope those instructions were meant for me and not some one else
Maybe you have to downgrade your hboot to 0.75.
Sent from my HTC Desire using newest version of swype and the XDA App
digo21 said:
Thanks for all the help and I hope those instructions were meant for me and not some one else
Click to expand...
Click to collapse
Yes they're for you but there's someone on androidforums with EXACTLY the same issue - you sure you're not the same person??
Nope thats not me
I followed all the procedures. But the RUU gave me an error after a few minutes saying 'Error 140 Bootloader version error'.
What does that mean and how can I fix it.
Which RUU are you trying to use? And which HBOOT are you on now?
Im trying to use the one you recommended above RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed.exe
Bootloader version I found out by holding the back key and power button to swithc on, it says HBOOT - 0.93.0001
Evening folks.
I was running a rooted and ROM'd One X with ARHD 9.x and quietly waiting for T-Mobile UK to release their version of JB. Now it's out, I've reverted to stock from Nandroid, gone back to stock recovery and stock boot image and waited for a system update OTA from T-Mob.
My phone picked up an update which was about 28mb. I figured this might be to update my hboot as I'm on 0.43 and I understand that needs to be updated before I can update to JB. I ran the install, the phone rebooted and then I got the following message flash up:
"This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action."
Since then I can't do anything like a factory reset (I get the same message flash up). The phone boots fine but tells me I have an update waiting to be applied.
Given that the phone was reverted completely to stock, I'm not quite sure what the update is that it picked up.
I'm thinking about doing it all manually but I'm frankly confused by all the information that's around - it's hard to work out what relates to my phone, and what I need to do. Here are the things I need to understand:
How do I get the hboot to a later version?
What version do I need to get it to to be able to then install JB?
Can I go directly from 0.43 to the one that will allow the JB install or does it need to be done in stages?
version-main: 1.26.110.5
CID = T-MOB005
hboot = 0.43
I'd really like to wrap my head around this and any help would be very much appreciated.
Edit: I've just noticed that I can no longer get into the stock Recovery...
You can flash this ruu
http://www.htcruu.com/securekey.php...Radio_1.1204.105.14_release_260731_signed.exe
It will bring your hboot to at least 0.95 or 0.96, from there you have to try and update to android 4.0.4 hboot 2.17 and from there to JB
Put the phone in fastboot usb mode and lock the bootloader
Fastboot oem lock
Stay in the fastboot usb mode and execute the RUU.exe from pc ... right click it and select
Run as administrator
It will flash the phone to full stock, you lose all data on the phone !
Thanks Mr Hofs, that worked. I've now got 1.29.110.11 on the phone, however it doesn't seem to be installing the 4.0.4 update (which it picks up OTA).
It downloaded it, rebooted, looked like it was installing but when the phone restarted it was still on 4.0.3 and picked up the system update again...
Edit: Ran it again and it's worked! I'm on 4.0.4 and 2.17.110.5. Next I'm hoping it picks up the T-Mobile OTA for JB. Then I can let it sort the hboot, unlock it, flash it and *done* hopefully!
Edit 2: Superb, it's picked up the Jelly Bean update. Downloading now!
Thanks for your help Mr Hofs!
No problem mate ! Enjoy the JB experience
Hi, I've got a Desire HD phone which I got unlocked and unbranded from the start and it came with some version of Froyo out of the box. Since then I've updated it through via wifi and currently it's on GB 2.3.5 and after the last update the phone has been telling me that it has no updates available. Furthermore, I have never flashed or rooted this phone so it's still a virgin
Further information on my phone is as follows:
Android Version: 2.3.5
HTC Sense Version: 3.0
Software Number: 3.13.707.4
AND some pics of the specs are in the attachment, please check them out.
Now due to some performance issues I wanted to reinstall either 2.3.5 or lower version of gingerbread or if possible the latest version of Froyo available for my phone. I have already tried restarting, taking out the battery, doing factory reset, wiping the phone and sdcard both from within the phone settings and from the HBoot and Recovery menu as well to no avail.
So I would like to ask you guys for steps and possible links to correct RUU for re-flashing the stock version of unbranded 2.3.5 or lower version of gingerbread or if possible the latest version of Froyo. I don't want to mess with the phone too much by going into the rooting and installing custom ROMS just yet, but that would be my last resort if all else fails.
I'm a newbie so please be gentle in replies
Thanks in advance!
STOP STOP STOP DONT DO ANYTHING!
don't flash any froyo ruu or wwe this will mess your hboot and you'll be in a whole world of hurt.
If you've done a factory reset you shouldn't be having performance issues as that takes you back to factory condition of course.
How ever
Your first course of action now should be goto market and get emmc checker and see if you have the bad chips (sain I think).
If you dont have issue I suggest you do HTCDEV unlock and root your phone or flash a new rom, ive only used SVHD which is ics sense rom which is pretty damn awesome, but im moved on to samsung galaxy s4 (unrooted) now so haven't used newest version yet.
Have a look around the dev forum there are a few really good guides .
Sent from my GT-I9505 using xda app-developers app
I recommend getting s-off and unlocking the HBoot to get the best performance from your phone. I must say that this is not for the faint-of-heart and things sometimes can and do go wrong .
I bought a second hand Desire HD running stock Telus GB for very little money so I didn't have much to lose if I pooched the phone. If you do decide to unlock the HBoot, make sure you upgrade to 2.00.0029 first.
What performance issues were you having?
ranger4740 said:
STOP STOP STOP DONT DO ANYTHING!
don't flash any froyo ruu or wwe this will mess your hboot and you'll be in a whole world of hurt.
If you've done a factory reset you shouldn't be having performance issues as that takes you back to factory condition of course.
How ever
Your first course of action now should be goto market and get emmc checker and see if you have the bad chips (sain I think).
If you dont have issue I suggest you do HTCDEV unlock and root your phone or flash a new rom, ive only used SVHD which is ics sense rom which is pretty damn awesome, but im moved on to samsung galaxy s4 (unrooted) now so haven't used newest version yet.
Have a look around the dev forum there are a few really good guides .
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Ran that app and it says " Brick Bug? NO. Sane Chip "
So I'm guessing my phone is good, right?
I've been having some major bugs popping up on my phone ever since I upgraded to the 2.3.5 update. My phone camera gets stuck while taking pictures, at times it has restarted my phone when I take a picture, the GPS/Location keeps popping up at every boot and I can't seem to disable it, the Connect To Computer message which used to let me select in which mode I want to connect my phone to the PC has stopped showing up and the phone only connects in charging mode to the PC, the speaker phone keeps turning itself on whenever I make a call or receive a call. I've read up on all these bugs on many forums and tried all the solutions to no avail, I have already done factory resets, battery pulls, cleaning of the usb connector, tried different usb cables on different computers, formatted the memory card etc, but none of these things worked for me.
So I'm left with one choice only, that is to erase everything on this phone and flash a fresh ROM onto it to see if it fixes the issue. And just to be on the safe side I want to install anything lower than 2.3.5 since that's when all these bugs popped up one by one for me. And I don't want to root my phone just yet or unlock it or do any experiments with it yet.
So my question is, how do I backup my current ROM in case if anything goes wrong I could revert back to this one and then how do I flash an official earlier version of GB compatible with my phone and where to get this ROM. Since my phone came unbranded and unlocked, I'm assuming the WWE versions would work well for me right? I once saw in my phone somewhere that it told me I have htc_asia_WWE version on my phone, if that helps. But I would rather get an English only version which has no other language settings in it, like chinese, vietnemese etc etc which my phone currently has.
Thanks in advance!
vxdesigns said:
Ran that app and it says " Brick Bug? NO. Sane Chip "
So I'm guessing my phone is good, right?
I've been having some major bugs popping up on my phone ever since I upgraded to the 2.3.5 update. My phone camera gets stuck while taking pictures, at times it has restarted my phone when I take a picture, the GPS/Location keeps popping up at every boot and I can't seem to disable it, the Connect To Computer message which used to let me select in which mode I want to connect my phone to the PC has stopped showing up and the phone only connects in charging mode to the PC, the speaker phone keeps turning itself on whenever I make a call or receive a call. I've read up on all these bugs on many forums and tried all the solutions to no avail, I have already done factory resets, battery pulls, cleaning of the usb connector, tried different usb cables on different computers, formatted the memory card etc, but none of these things worked for me.
So I'm left with one choice only, that is to erase everything on this phone and flash a fresh ROM onto it to see if it fixes the issue. And just to be on the safe side I want to install anything lower than 2.3.5 since that's when all these bugs popped up one by one for me. And I don't want to root my phone just yet or unlock it or do any experiments with it yet.
So my question is, how do I backup my current ROM in case if anything goes wrong I could revert back to this one and then how do I flash an official earlier version of GB compatible with my phone and where to get this ROM. Since my phone came unbranded and unlocked, I'm assuming the WWE versions would work well for me right? I once saw in my phone somewhere that it told me I have htc_asia_WWE version on my phone, if that helps. But I would rather get an English only version which has no other language settings in it, like chinese, vietnemese etc etc which my phone currently has.
Thanks in advance!
Click to expand...
Click to collapse
No actually read what EMMC chip you have, that app is made for samsung phones and will only check for those.Type out the one you have
audit13 said:
I recommend getting s-off and unlocking the HBoot to get the best performance from your phone. I must say that this is not for the faint-of-heart and things sometimes can and do go wrong .
I bought a second hand Desire HD running stock Telus GB for very little money so I didn't have much to lose if I pooched the phone. If you do decide to unlock the HBoot, make sure you upgrade to 2.00.0029 first.
What performance issues were you having?
Click to expand...
Click to collapse
If I want to flash the stock ROM, do I still need to do s-off and unlock the HBoot or are these only necessary to flash custom ROMS???
Steam. said:
No actually read what EMMC chip you have, that app is made for samsung phones and will only check for those.Type out the one you have
Click to expand...
Click to collapse
Not sure what you are saying ...
The eMMC app shows this info:
Phone Model
HTC htc_ace
eMMC chip
Type: SEM04G
Brick Bug?
NO. Sane chip
vxdesigns said:
Not sure what you are saying ...
The eMMC app shows this info:
Phone Model
HTC htc_ace
eMMC chip
Type: SEM04G
Brick Bug?
NO. Sane chip
Click to expand...
Click to collapse
I guess you could run the RUU but since you think its wwe_asia it will be tricky to get a proper link for your RUU.I'd suggest unlocking the BL and if you're only after the stock ROM, flash Android Revolution HD 6.6, it's stock.First you need to upgrade the HBOOT though, you need .0029 for the unlocking process.You unlock the BL via HTC's site afterwards.
http://forum.xda-developers.com/showpost.php?p=38947050&postcount=10
Download HBOOT Update Kit and rom.zip from attachments there.Put the rom.zip exactly in C, and the update kit doesn't really matter, aslong as it's in a folder.Make sure you have your drivers installed, found here , install them.Run the hboot update.bat, but turn on usb debugging first.
Steam. said:
I guess you could run the RUU but since you think its wwe_asia it will be tricky to get a proper link for your RUU.I'd suggest unlocking the BL and if you're only after the stock ROM, flash Android Revolution HD 6.6, it's stock.First you need to upgrade the HBOOT though, you need .0029 for the unlocking process.You unlock the BL via HTC's site afterwards.
http://forum.xda-developers.com/showpost.php?p=38947050&postcount=10
Download HBOOT Update Kit and rom.zip from attachments there.Put the rom.zip exactly in C, and the update kit doesn't really matter, aslong as it's in a folder.Make sure you have your drivers installed, found here , install them.Run the hboot update.bat, but turn on usb debugging first.
Click to expand...
Click to collapse
I did get a RUU which meets my specs exactly, or so I think:
http://www.shipped-roms.com/downloa...60.29_26.14.04.28_M_release_234022_signed.exe
I ran it, updated my phone, it's the same version which is already on my phone, it completed without any issues, but the bugs are still there. So I'm assuming it didn't really reinstall the software from scratch, it just updated the software without making much changes to it, pretty much like a factory reset, right???
Can you please tell me why we need to unlock the HBoot??? Is it to enable us to flash custom roms???
What I want to do is erase the 2.3.5 GB software completely from my phone so it has no trace of it, then install stock/untouched 2.3.3 GB or any other GB version compatible with my phone. So please provide steps and insight into this process.
Thanks
Steam. said:
I guess you could run the RUU but since you think its wwe_asia it will be tricky to get a proper link for your RUU.I'd suggest unlocking the BL and if you're only after the stock ROM, flash Android Revolution HD 6.6, it's stock.First you need to upgrade the HBOOT though, you need .0029 for the unlocking process.You unlock the BL via HTC's site afterwards.
http://forum.xda-developers.com/showpost.php?p=38947050&postcount=10
Download HBOOT Update Kit and rom.zip from attachments there.Put the rom.zip exactly in C, and the update kit doesn't really matter, aslong as it's in a folder.Make sure you have your drivers installed, found here , install them.Run the hboot update.bat, but turn on usb debugging first.
Click to expand...
Click to collapse
Updated and unlocked my Hboot and now it's on 29 with S-Off.
I flashed CWM recovery, installed SuperUser and flashed the latest version of SVHD and rebooted but phone won't start, after the HTC logo with a white background, the screen goes black as if the ROM can't boot.
Could this be a SuperUser issue or a S-Off issue? I'm not sure if SVHD requires S-On to function properly and it's nowhere mentioned on the thread either.
Advice required :crying:
vxdesigns said:
Updated and unlocked my Hboot and now it's on 29 with S-Off.
I flashed CWM recovery, installed SuperUser and flashed the latest version of SVHD and rebooted but phone won't start, after the HTC logo with a white background, the screen goes black as if the ROM can't boot.
Could this be a SuperUser issue or a S-Off issue? I'm not sure if SVHD requires S-On to function properly and it's nowhere mentioned on the thread either.
Advice required :crying:
Click to expand...
Click to collapse
Never mind your actually s-off...
Did you do full wipe before flash?
Apparently you really should be using 4ext recovery on dhd as clockwork doesnt quite do the job right?.
Sent from my GT-I9505 using xda app-developers app
vxdesigns said:
Updated and unlocked my Hboot and now it's on 29 with S-Off.
I flashed CWM recovery, installed SuperUser and flashed the latest version of SVHD and rebooted but phone won't start, after the HTC logo with a white background, the screen goes black as if the ROM can't boot.
Could this be a SuperUser issue or a S-Off issue? I'm not sure if SVHD requires S-On to function properly and it's nowhere mentioned on the thread either.
Advice required :crying:
Click to expand...
Click to collapse
Choose full wipe in aroma installer. i recommend you to used SVHD 1.70 then upgrade OTA 1.73. does not flash version 1.74. this got so much error.
vxdesigns said:
Updated and unlocked my Hboot and now it's on 29 with S-Off.
I flashed CWM recovery, installed SuperUser and flashed the latest version of SVHD and rebooted but phone won't start, after the HTC logo with a white background, the screen goes black as if the ROM can't boot.
Could this be a SuperUser issue or a S-Off issue? I'm not sure if SVHD requires S-On to function properly and it's nowhere mentioned on the thread either.
Advice required :crying:
Click to expand...
Click to collapse
Flash 4ext, wipe everything and reflash 1.7.0, and then update to 1.7.3.CWM never wiped my partitions properly, it blows compared to 4ext.
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