hi guys unfortunately i need to send my phone in warranty (sniff)
previously i'm rooting my ds with revolutionary
and now i follow this
i flashed eng boot and next i use android flasher flashing the hboot in the root of the folder..
anyway i'm now with:
***security warning***
saga pvt ship s-on rl
hboot-0.98.0002
radio-3831.19.00.110
emmc-boot
bla bla bla...
i'm tryng to use the ruu to revert the rom back to stock
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed.exe
but it says "unable to update"
now i think i have the h boot 98.0002 and the ruu have 98.0000
so it didn't work but i can't find the ruu thread on xda (i remember there it was some time ago)
any help?
Is it that link you are looking for ? : HTC Saga Shipped Roms
kiss!!!! xD
i have an error....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but before i have:
someone have a solution?
i think i have a newer version of the misc version am i right?but what i can do to downgrade it?
i'v try
adb push misc_version /data/local/tmp
but it'says error device not found
Husky34 said:
i have an error....
but before i have:
someone have a solution?
i think i have a newer version of the misc version am i right?but what i can do to downgrade it?
i'v try
adb push misc_version /data/local/tmp
but it'says error device not found
Click to expand...
Click to collapse
Do you have goldcard? The same problem I also had. After making a goldcard, I've installed the official RUU successful.
Sent from my HTC Desire XS using Tapatalk 2
NVardan said:
Do you have goldcard? The same problem I also had. After making a goldcard, I've installed the official RUU successful.
Sent from my HTC Desire XS using Tapatalk 2
Click to expand...
Click to collapse
mmm no...what is it? (i think i'v heard it...is something inside the sd right?)
[GUIDE] Create a GOLDCARD for your HTC DESIRE S
hipp0po said:
[GUIDE] Create a GOLDCARD for your HTC DESIRE S
Click to expand...
Click to collapse
yep but in this condition my phone doesen't boot..only reboot in bootloader...
Husky34 said:
yep but in this condition my phone doesen't boot..only reboot in bootloader...
Click to expand...
Click to collapse
run the ruu in fastboot?
Sent from my supercharged :tank:
hisname said:
run the ruu in fastboot?
Sent from my supercharged :tank:
Click to expand...
Click to collapse
yep is it correct? it works for a while and then bam error 140..
Husky34 said:
yep is it correct? it works for a while and then bam error 140..
Click to expand...
Click to collapse
well there is still hopes...
try misc. version? or maybe CID doesn't match?
Sent from my supercharged :tank:
hisname said:
well there is still hopes...
try misc. version? or maybe CID doesn't match?
Sent from my supercharged :tank:
Click to expand...
Click to collapse
i'll put the screen in the first page of this thread...and i even try to change misc version without success..
Ok you have made a very common mistake (that I have made once too, but then there was no ICS RUU, so I was forced to do some mumbo-jumbo) - not lowering your version, which is a must-have in the downgrade process
Anyway you have now much easier path now:
1) Run the ICS RUU
2) unlock the bootloader via htc-dev
3) flash a custom recovery
4) root it manually or with the AIO tool (temp root will not work)
5) lower your main version using the misc_version binary
6) relock the bootloader
7) run the RUU
8) disable the update check in the Settings, otherwise if upgraded the SC will spot the relocked bootloader
Good luck
amidabuddha said:
Ok you have made a very common mistake (that I have made once too, but then there was no ICS RUU, so I was forced to do some mumbo-jumbo) - not lowering your version, which is a must-have in the downgrade process
Anyway you have now much easier path now:
1) Run the ICS RUU
2) unlock the bootloader via htc-dev
3) flash a custom recovery
4) root it manually or with the AIO tool (temp root will not work)
5) lower your main version using the misc_version binary
6) relock the bootloader
7) run the RUU
8) disable the update check in the Settings, otherwise if upgraded the SC will spot the relocked bootloader
Good luck
Click to expand...
Click to collapse
but i want to send into warranty man...i can't unlock bootloader via htc dev
Husky34 said:
but i want to send into warranty man...i can't unlock bootloader via htc dev
Click to expand...
Click to collapse
I am afraid you are out of options. There is no way to lower your version without root.
If you are lucky and still have the custom recovery you can use the misc_version there (it has root). Otherwise you cannot flash anything with this version, only the ICS RUU. You cannot use Revolutionary again when your OS does not boot
EDIT: as I said I have made the same mistake and now my hardware buttons are almost broken and I cannot take it to a repair due to my Unlocked bootloader. But when you downgrade to 1.28.x or 1.47.x there is no "RELOCKED" flag shown in the booltoader screen. So if you keep the older version and do not update there is a chance that the SC will not check it.
amidabuddha said:
I am afraid you are out of options. There is no way to lower your version without root.
If you are lucky and still have the custom recovery you can use the misc_version there (it has root). Otherwise you cannot flash anything with this version, only the ICS RUU. You cannot use Revolutionary again when your OS does not boot
Click to expand...
Click to collapse
can i fire my mmc in some way?if my phone doesen't boot i think they can change my motherboard...:'(
i know is a hard decision....but i think is the only one...
OR
i can flash ics ruu and send it into warranty!!!!but when it comes back i can't root it....no?
Husky34 said:
OR
i can flash ics ruu and send it into warranty!!!!but when it comes back i can't root it....no?
Click to expand...
Click to collapse
Well as far as I remember the ICS RUU disclaimer says that it drops the warranty on the software side. If you have a hardware problem it should be acknowledged and repaired. But you have to recheck that.
amidabuddha said:
Well as far as I remember the ICS RUU disclaimer says that it drops the warranty on the software side. If you have a hardware problem it should be acknowledged and repaired. But you have to recheck that.
Click to expand...
Click to collapse
of course i check
thanks for the info and have a good day all!
amidabuddha said:
I am afraid you are out of options. There is no way to lower your version without root.
If you are lucky and still have the custom recovery you can use the misc_version there (it has root). Otherwise you cannot flash anything with this version, only the ICS RUU. You cannot use Revolutionary again when your OS does not boot
EDIT: as I said I have made the same mistake and now my hardware buttons are almost broken and I cannot take it to a repair due to my Unlocked bootloader. But when you downgrade to 1.28.x or 1.47.x there is no "RELOCKED" flag shown in the booltoader screen. So if you keep the older version and do not update there is a chance that the SC will not check it.
Click to expand...
Click to collapse
What are you talking about? He can just use tacoroot. Either way, he was S-OFF, so he can just S-OFF again, change miscversion, and then roll back to S-ON.
Related
Hi all,
I am trying to recover an HTC Sensation XE (PG58130), but I have no history on the unit, so I don't know if it's been modified or is genuinely faulty.
When you power the phone on, all you get is the HTC logo. Nothing else happens.
Vol Down + Power displays the following info:
*** LOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.02_2
eMMC-boot
Aug 2 2011,22:35:52
Click to expand...
Click to collapse
I have tried "Factory Reset". I also put the phone into Recovery, then wiped data and cache, but still only get the HTC logo.
Does anyone have any suggestions? Also, does the information above suggest the phone hasn't been modified?
It hasn't been modified. It still is S-on and has the original hboot 1.18
Sent from my Kindle Fire using Tapatalk 2
Ah, thanks for letting me know.
So, is there any way I can fix this boot loop problem?
blastcomms said:
Ah, thanks for letting me know.
So, is there any way I can fix this boot loop problem?
Click to expand...
Click to collapse
you need to soff your device which will let you flash a custom rom....
so that you can bring back your phone from hell
here is the guide to all the basic steps which are required to flash any rom
guide link
Thanks - I'll take a look.
Does that void the warranty with HTC? I would like to retain the warranty where possible, but if that's the only option then I don't mind.
blastcomms said:
Thanks - I'll take a look.
Does that void the warranty with HTC? I would like to retain the warranty where possible, but if that's the only option then I don't mind.
Click to expand...
Click to collapse
all the things you are doing are reversible but you need to be careful while doing it
Follow step by step for successful soff
Also STEP 5 in the guide helps you in reversing the process which will help you in claiming the warranty
PS: Read each and every step carefully and execute them ...then it'll be a piece of cake
Sorry, another question, but I want to make sure I get this right.
It says in the guide to run revolutionary and then connect the phone. However, it says the phone should be on and in HTC Sync mode.
Obviously this phone isn't powering on so that's a problem.
Any ideas?
blastcomms said:
Sorry, another question, but I want to make sure I get this right.
It says in the guide to run revolutionary and then connect the phone. However, it says the phone should be on and in HTC Sync mode.
Obviously this phone isn't powering on so that's a problem.
Any ideas?
Click to expand...
Click to collapse
oops forgot about that
try this
keep your phone in hboot mode (i.e. power + vol down button) you'll get a white screen
then run revolutionary (hopefully revolutionary detects the phone)
if it doesn't work (i mean if revolutionary didn't recognize your device) let me know..
Im currently looking for any other method and ill post you if i got any leads
EDIT:
found the guide (follow steps carefully)
http://forum.xda-developers.com/showthread.php?t=1469296
There seems to be different headers indicating different steps. Which steps should I follow in my case?
By the way, I saw your post before you edited it, and followed these steps to setup adb and fastboot: http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
When I type 'adb devices' into cmd I get nothing (when in HBOOT), but when I go to fastboot and type 'fastboot devices' it shows me the phone's serial number. Is that normal?
Yeah that is normal.
Adb works when you are on your OS ie either GB or ICS and fastboot works when you are on bootloader..as fastboot was able to recognize your device can you post the cid
Command is "fastboot getvar cid"
Edit:
The thing is now you require a GB Rom which can be flashed which supports. your hboot and radio but by flashing that your hboot version should not change as that is the final version where soff works.
So try unlocking your device by using HTC dev and flash a stock 2.3 Rom mentioned in the guide.
Try the way where he mentioned about a member flashing rom (he has the same scenario hboot 1.18 and ics Rom on top of it with gb firmware)
sent from my blazing fast pyramid through sonic waves
Hi, sorry I was away yesterday.
My CID is HTC__001.
Does that make any difference to flashing, etc?
blastcomms said:
Hi, sorry I was away yesterday.
My CID is HTC__001.
Does that make any difference to flashing, etc?
Click to expand...
Click to collapse
yeah cid does require some changes...but have you tried
revolutionary by keeping your phone connected to your pc through usb ???
i mean when you ran revolutionary was it able to identify your device and asked for beta key??
if it did recognized your device then you'll be not having issues anymore
so just try revolutionary first and let me know the result
In the mean time i'll figure out the best solution for you
EDIT: Also you got recovery installed ?? can you check that by going into recovery from HBOOT -> (if it is an exclamatory mark with inverted triangle then stock recovery)
I ran revolutionary in HBOOT and it didn't do anything, just said it was waiting for the device.
Should it be in a different mode?
My recovery screen looks the same as this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
blastcomms said:
I ran revolutionary in HBOOT and it didn't do anything, just said it was waiting for the device.
Should it be in a different mode?
My recovery screen looks the same as this:
Click to expand...
Click to collapse
what about fastboot mode?
just try that too
let me know ASAP
(im online and ill give you further steps)
EDIT:
"I have tried "Factory Reset". I also put the phone into Recovery, then wiped data and cache, but still only get the HTC logo."
how did you wiped data and cache if you got stock recovery (fyi i haven't exploited stock recovery as i ran revolutionary and installed custom recovery the next minute i got my phone )
Even in fastboot mode, revolutionary just says "Waiting for device..."
To wipe data and cache I entered recovery, then pressed Vol Up + Power which brought up further options to wipe, etc.
blastcomms said:
Even in fastboot mode, revolutionary just says "Waiting for device..."
To wipe data and cache I entered recovery, then pressed Vol Up + Power which brought up further options to wipe, etc.
Click to expand...
Click to collapse
finally i got the ruu which installed should give you the GB on it
1.here is the link to download the RUU (it will be big file 358 MB)
RUU link
this RUU.exe is based on your CID and Radio so it will run fine
2.Guide to install RUU
guide
3.if any issue persists (there is 1 common one which was fixed by a guy)
here is the link for the fix if you run into issue
RUU running issues fix
run the ruu.exe and your phone will be reverted back to GB rom
then if you want to update to ICS there are some basuc steps to be done...
i.e SOFF and all so follow the "Guide to SOFF ,supercid ...." thread
after that you can take take this guide as reference for installing any custom rom
EDIT:
ahh man the RUU may be wrong ( will update you about this)
i got another ruu
download this also...this seems more proper for your CID
RUU 2 LINK
Thanks, will reply once I've done all that. The file is downloading now. It says I have to ensure an ActiveSync connection is established, so here's hoping it lets me do that in HBOOT/Fastboot/Recovery.
UPDATE:
1.72 RUU one was for XE version
and 1.52 one was for normal sensation
Oh this one is XE so I need the first link you gave, right? And what mode do you recommend it to be in? Recovery, Fastboot or HBOOT?
EDIT: first link doesn't work once download is supposed to commence.
blastcomms said:
Oh this one is XE so I need the first link you gave, right? And what mode do you recommend it to be in? Recovery, Fastboot or HBOOT?
Click to expand...
Click to collapse
from HBOOT (as that is the default bootloader that pops up)
if this didn't work then try FASTBOOT
How to return to stock to return to stock
1. Download HTC One S All-In-One Toolkit V1.0.
2. Unzip it and run it.
3. Please make sure you have your Unlock_code.bin in One_S_All-In-One_Kit_v1.0 data folder
4. Highlight stock under recovery and click flash recovery.
5. Your phone will reboot then click relock bootloader.
6. after you relock bootloader run carrier ruu
T-Mobile USA RUU.
Roger RUU
Correction: run your carrier's RUU...
http://forum.xda-developers.com/showthread.php?t=1543588
Sent from my HTC One S using xda premium
Any options for Mac/Linux users since there's no intentions of bringing this tool to us? It'd be greatly appreciated.
NienorGT said:
Correction: run your carrier's RUU...
http://forum.xda-developers.com/showthread.php?t=1543588
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
No I think you misunderstand what OP has done...... Toolkit I'm assuming that locks your bootloader back and also runs the ruu.exe. thanks. OP
Sent from my HTC VLE_U using XDA Premium HD app
alwayshalfway said:
Any options for Mac/Linux users since there's no intentions of bringing this tool to us? It'd be greatly appreciated.
Click to expand...
Click to collapse
these are all commands achieveable through terminal and fastboot, its just nicely packaged for windows in this.
JDenson77 said:
No I think you misunderstand what OP has done...... Toolkit I'm assuming that locks your bootloader back and also runs the ruu.exe.
Click to expand...
Click to collapse
Nah he previously said in it's tutorial to run the T-Mobile RUU, which applies only to T-Mobile users. He did correct that little ambiguity
Sent from my HTC One S using xda premium
I follow step by step, but i cant instal the RUU, it give me error 155. 3 uk Htc one s! Help please!
Sent from my HTC one s using xda premium
Do you have the right RUU
There's no longer a need to go back to stock. If you're looking for the radio file, it's here.
The kernel will probably be baked into the next AOKP and CM9 roms, and I'm sure there'll be a flashable zip of the new kernel coming out very soon as well.
NOTE: If you're flashing the new radio, you need to use TWRP. Clockworkmod will NOT work properly for this, so don't bother trying.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i got the right ruu for the us htc one s for tmobile but for some reason i must be missing something cause my pc keeps asking me what program would i like to run the ruu with lol. does anyone know why it wont open the ruu? its been so long since ive ran the file.
The RUU is an .exe file.
RUU are very useful to reset the phone to stock before returns/selling it. It's also useful to go back to see if an issue was provocked by the Rom/root/whatever and not the phone itself.
Sent from my HTC One S using xda premium
s10shane said:
i got the right ruu for the us htc one s for tmobile but for some reason i must be missing something cause my pc keeps asking me what program would i like to run the ruu with lol. does anyone know why it wont open the ruu? its been so long since ive ran the file.
Click to expand...
Click to collapse
Ruu.exe', you mast remove (')
Sent from my HTC one s
cbetso said:
Do you have the right RUU
Click to expand...
Click to collapse
Yes for 3uk! :-(
Sent from my HTC one s
I get error 140 when running RUU because I upgraded to 1.84 today. Is it safe to downgrade to a 1.53 ROM and then run RUU?
Tells me the files are gone now.
---------- Post added at 09:20 PM ---------- Previous post was at 09:03 PM ----------
cbetso said:
How to return to stock to return to stock
1. Please make sure you have your Unlock_code.bin on your sdcard root
2. Download HTC One S All-In-One Toolkit V1.0.
3. Unzip it and run it.
4. Highlight stock under recovery and click flash recovery.
5. Your phone will reboot then click relock bootloader.
6. after you relock bootloader run carrier ruu
T-Mobile USA RUU.
Roger RUU
Click to expand...
Click to collapse
Why do you keep the unlock bin on the phone? Also don't you need to get a new one after you do this to unroot it?
Minor corrections. Just relock the bootloader. Let the phone turn on after it is relocked. Run the RUU for your device's carrier. No need to flash stock recovery.
andorinho said:
I get error 140 when running RUU because I upgraded to 1.84 today. Is it safe to downgrade to a 1.53 ROM and then run RUU?
Click to expand...
Click to collapse
+1 I'm in the same boat. Want to get back to 1.53 but the ruu gives me the same error.
HTC Android Phone ROM Update Utility 1.0.5.2011
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
michaelh99 said:
+1 I'm in the same boat. Want to get back to 1.53 but the ruu gives me the same error.
HTC Android Phone ROM Update Utility 1.0.5.2011
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Click to expand...
Click to collapse
If your rooted just restore the 1.53 Nandroid floating around the dev section.
No, not rooted
michaelh99 said:
No, not rooted
Click to expand...
Click to collapse
Sorry, root is your only option to downgrade. If your having issues then I would pursue a replacement from T-Mobile as my phone works perfectly fine on 1.84.
I've been trying to restore back to stock for over a day now and still havn't figured it out.
All of the guides start talking about adb or fastboot right in the middle of the guide without any explanation.
Aruwizard keeps saying bootloader version fail when I try to flash whats supposed to be stock rogers rom, but everything i see is telling me to download the one im already using.
1. download rogers ruu.zip
2. get supercid or downgrade follow http://forum.xda-developers.com/showthread.php?t=1671135
3. use the windows ruu tool ..... or .... get adb and fastboot installed correctly. google this if you dont know how
4a. for windows ruu tool follow my post in dev section
4b. for adb and fastboot do
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip ruu.zip
it will ask u to run the last command again...
Berserk87 said:
I've been trying to restore back to stock for over a day now and still havn't figured it out.
All of the guides start talking about adb or fastboot right in the middle of the guide without any explanation.
Aruwizard keeps saying bootloader version fail when I try to flash whats supposed to be stock rogers rom, but everything i see is telling me to download the one im already using.
Click to expand...
Click to collapse
Have you relocked your bootloader?
1. make sure fastboot in android is turned off under power.
2. power off device
3. power phone on by holding down the volume down key + pressing power - don't release the volume down key until you see the bootloader screen
4. select fastboot
5. connect phone usb
6. screen should now read fastboot usb in red
7. type fastboot oem lock
Phone might restart back into fastboot can't really remember but now you can run the RUU.
The RUU should be an .exe for the above
im on 1.73 trying to flash reflash 1.73, so i shouldnt need to use super cid (?).
I download the rogers stock rom (PJ83IMG_Evita_UL_Rogers_WWE_1.73.631.1_Radio_0.16a.32.09.06_10.81.32.14L_release_254934_signed.zip)
and I downloaded ARUwizard to flash it.
I keep getting random errors from aruwizard.
ive tried finding adb tools or fastboot, but they all look like they're for specific phones.
Berserk87 said:
im on 1.73 trying to flash reflash 1.73, so i shouldnt need to use super cid (?).
I download the rogers stock rom (PJ83IMG_Evita_UL_Rogers_WWE_1.73.631.1_Radio_0.16a.32.09.06_10.81.32.14L_release_254934_signed.zip)
and I downloaded ARUwizard to flash it.
I keep getting random errors from aruwizard.
ive tried finding adb tools or fastboot, but they all look like they're for specific phones.
Click to expand...
Click to collapse
for aruwizard....did you install htc sync? and relocked your bootloader?...
u need both ...
niceppl said:
for aruwizard....did you install htc sync? and relocked your bootloader?...
u need both ...
Click to expand...
Click to collapse
I did.
and my bootloader has never been unlocked.
its giving me something about incorrect bootloader version. even though its the rogers rom.
Do i need to super cid if im flashing the same version? (1.73 to 1.73)
aruwizard just keeps saying "wrong bootloader version"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is what im getting everytime i try to use aruwizard.
Berserk87 said:
this is what im getting everytime i try to use aruwizard.
Click to expand...
Click to collapse
where did u get the aruwizard tool seems its not the one for hox...too old maybe...try the adb amd fastboot method i mentioned above
Sent from my HTC One X using xda app-developers app
niceppl said:
where did u get the aruwizard tool seems its not the one for hox...
Click to expand...
Click to collapse
downloaded it from your other thread. http://forum.xda-developers.com/showthread.php?t=1658929
using fastboot it starts doing the checks, then gets to :
Code:
INFOchecking main version...
FAILED (remote: 43 main version check fail)
looks like even though im trying to flash 1.73 to 1.73 i still need to do the downgrading firmware stuff...
im curious if my failed update upgraded some stuff and failed on the rest...
now its giving me
Code:
FAILED (remote: 44 hboot version check fail)
anyone?
$5 to anyone that can tell me how to fix this (get back to full stock)
Berserk87 said:
$5 to anyone that can tell me how to fix this (get back to full stock)
Click to expand...
Click to collapse
unlock
twrp
root
supercid (search in dev)
downgrade to 1.00.000 (search in dev)
relock
run ruu
everything should be back to stock
if you want to change supercid back to roger001
do previous steps again and change the cid to roger001 rather than supercid
Sent from my HTC One X using xda app-developers app
Berserk87 said:
$5 to anyone that can tell me how to fix this (get back to full stock)
Click to expand...
Click to collapse
Lol $5 thought a twenty was the customary amount
Sent from my HTC One XL
niceppl said:
unlock
twrp
root
supercid (search in dev)
downgrade to 1.00.000 (search in dev)
relock
run ruu
everything should be back to stock
\
Click to expand...
Click to collapse
I don't want to unlock, id rather keep my warranty as I might be RMA'ing it because of the bluetooth issues im having.
Berserk87 said:
I don't want to unlock, id rather keep my warranty as I might be RMA'ing it because of the bluetooth issues im having.
Click to expand...
Click to collapse
You need to unlock, but alas once you flash the ruu ... The unlocked/tampered proof will be rewritten to stock as well...
From my HTC One X possessed by the Illuminati hybrid kernel
It will show relocked instead of locked.Not sure if warranty accept it
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
The official Build
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
for the AT&T HTC One XL.
Click link here>> Link to Development Thread <<Click link here
Please feel free to share issues, questions and offer help
It is always best to thank a ROM OP, in lieu of simply posting "Thank you".
Please keep discussion focused, on the topic described in the OP
For the new kernel is it possible to flash the newest HBoot from this thread just to make life easier? http://forum.xda-developers.com/showthread.php?t=2156368
Would that be the 2.14 HBoot?
thanks again!
BTW I know I already posted this in the AOKP thread...Just wanted clarification from both devs.
mikelebz said:
For the new kernel is it possible to flash the newest HBoot from this thread just to make life easier? http://forum.xda-developers.com/showthread.php?t=2156368
Would that be the 2.14 HBoot?
thanks again!
BTW I know I already posted this in the AOKP thread...Just wanted clarification from both devs.
Click to expand...
Click to collapse
afaik, you MUST flash the RUU in its entirety. I believe h8 did something like just flash parts of the RUU and that bricked his phone. As long as your s-offed, no reason why you wouldn't want to RUU to 3.18.
I don't know if this is the correct place to ask this but I tried to RUU but I keep getting an error.
Torch not working
Anyone else getting FC's when trying to use the torch?
Misterowl said:
I don't know if this is the correct place to ask this but I tried to RUU but I keep getting an error.
Click to expand...
Click to collapse
What Error?
SuperCID? Yes or no?
S-ON or S-OFF?
Is s2w available on this kernel? My power button has been sticky so I've to move to the sense5 rom which I like. But definitely not as much as i love CM10.1
exad said:
What Error?
SuperCID? Yes or no?
S-ON or S-OFF?
Click to expand...
Click to collapse
Error 170
S-OFF
CID 11111111
ClassicalGas said:
Anyone else getting FC's when trying to use the torch?
Click to expand...
Click to collapse
Yeah, I'm pretty sure camera flash is broken too.
Misterowl said:
Error 170
S-OFF
CID 11111111
Click to expand...
Click to collapse
boot to bootloader/fastboot, ruu
So Girlfriend is finally getting tired of her Sense and is open to the idea of me rooting. Besides the camcorder resolution, hdmi, are there any bugs that would keep this from being a good dd. Thanks for the help guys
Hey whats up everybody I have a couple questions, Is it absolutely necessary to upgrade to 3.18 RUU for this ROM? The only reason I'm hesitating to ditch 1.09, is because I'm a bonafide flashaholic, and I'm not looking forward to fastboot flashing the boot image again, every time I want to try a new rom! (been there done that and it is totally NOT the business ) Which brings me to my second question, Does updating to 3.18 require you to fastboot flash the boot image before flashing new rom's? Evita/hboot 1.09/S-Off
JayDream said:
Hey whats up everybody I have a couple questions, Is it absolutely necessary to upgrade to 3.18 RUU for this ROM? The only reason I'm hesitating to ditch 1.09, is because I'm a bonafide flashaholic, and I'm not looking forward to fastboot flashing the boot image again, every time I want to try a new rom! (been there done that and it is totally NOT the business ) Which brings me to my second question, Does updating to 3.18 require you to fastboot flash the boot image before flashing new rom's? Evita/hboot 1.09/S-Off
Click to expand...
Click to collapse
Nah, with S-Off you don't need to fastboot flash anything.
Yesterday I was S-On, 1.09, now I'm S-Off 2.14 hboot (after using the 3.18 RUU). I've never had to fastboot flash the boot.img on this phone.
Sent from my One X using Tapatalk 4 Beta
ClassicalGas said:
Nah, with S-Off you don't need to fastboot flash anything.
Yesterday I was S-On, 1.09, now I'm S-Off 2.14 hboot (after using the 3.18 RUU). I've never had to fastboot flash the boot.img on this phone.
Sent from my One X using Tapatalk 4 Beta
Click to expand...
Click to collapse
OK thanks! Now can I fastboot flash the hboot using this method http://forum.xda-developers.com/showthread.php?t=2156686 or do I have to actually run the ruu?
JayDream said:
OK thanks! Now can I fastboot flash the hboot using this method http://forum.xda-developers.com/showthread.php?t=2156686 or do I have to actually run the ruu?
Click to expand...
Click to collapse
I RUU'd as per H8's recommendations, so can't confirm if that method works or not.
Sent from my One X using Tapatalk 4 Beta
So I RUU'd and downgraded the touch panel firmware and tried to flash a new recovery but my bootloader is locked.
I tried unlocking the bootloader in HTCdev and I keep getting this in my terminal.
ERROR: could not get pipe properties
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.013s]
finished. total time: 0.013s
ClassicalGas said:
I RUU'd as per H8's recommendations, so can't confirm if that method works or not.
Sent from my One X using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks man I appreciate it. But I think I'm gonna have to sit back on this one tho :/ at least until I have a better idea of what I'm getting into...
Sent from my HTC One XL using xda app-developers app
Misterowl said:
Error 170
S-OFF
CID 11111111
Click to expand...
Click to collapse
I kept getting an error that "Android phone is not connected"
Then i booted the phone into bootloader mode and tried it
That seemed to get it to work.
Still in the procees of downgrading and getting back to CM10.1
Just wanted to let you know
JayDream said:
Thanks man I appreciate it. But I think I'm gonna have to sit back on this one tho :/ at least until I have a better idea of what I'm getting into...
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Yeah I was a bit worried but was patient and followed all instruction instructions below (from the CarbonRom thread).
InflatedTitan said:
1. Download the 2 files for s-off and place in adb folder.
2. Download the recovery of choice and put in adb folder.
3 (optional) download the remove red text file and put in adb folder.
4. You'll have to downgrade touchscreen if you want to use aosp. Head to original dev sticky to download files from h8rift. Put those in adb folder
_________________________________________
1. S-off! Make sure you confirm in bootloader (it usually works easier from a sense rom btw.) 4.2.2 roms need updated adb but it may work.
2. When you ruu, it doesn't touch sdcard. But I would quickly mount and backup your pics and whatnot just in case.
3. Enter fast boot. Run the ruu on the computer. It'll bring you back to 100% stock.
4. Once you up and running, enter fast boot again and send twrp.
5. I recommend to get rid of the ugly ass red text on splash. Follow Liam's thread to rid it.
6. While in fastboot go ahead and downgrade touchscreen following h8rifts instructions.
7. Now you're golden to flash anything you want :thumbup:
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I used the RUU from here
I used a windows computer instead of a Mac to unlock and it worked. So yeah Mac bad.
Sent from my One X using xda app-developers app
Hello everyone! So here's the deal..
I recently bought an unlocked HTC One XL, which came installed with TWRP and AOKP. I noticed that the device performance was really slow and decided to erase some things. Problem is I deleted the ROM + Recovery. I have tried multiple times to install both recovery and image files. I know how to transfer files using fastboot, but there are a couple of problems:
1.) When I type in "adb devices" it doesn't say 'device not recognized' but instead it shows the apparent list of devices - which my XL is not in. This elevates the problem because I cannot just push files through adb, instead I am stuck on sending files through fastboot every single time.
2.) I have sent recovery.img's and my phone is stuck in "bootloop" - it just turns off and on in the same screen. When I try to access recovery from bootloader, this exact same problem of repetition happens. I can't change the state of the S-On.
3.) I'm still fairly new when it comes to ROM installation, but I wouldn't consider myself a complete retard either when it comes to this.
___________________________________________
Phone State:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.19as.32.09.11+2
OpenDSP-c28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
I don't think I bricked my device, though I might of have softbricked it. I know I messed up by deleting TWRP + AOKP, but I knew that it was (should've been) just as easy as flashing the files back into the phone. If anyone can help me by possibly providing ROMs and recovery files that actually work on boot it would be greatly appreciated.
** Update
I managed to install TWRP = Progress
I would suggest flashing sense 5 stock rom first ..That would get ur adb working n then go for s-off before proceeding further
It worked for me earlier
Sent from my HTC One XL using xda premium
Firstly, you can't just delete the recovery, it doesn't work like that. Anyway, looks like you got TWRP installed again do all you need to do now is install a ROM and away you go. Once you have a ROM installed you can use the phone as normal, but it's pretty strongly suggested you get s-off.
Sent from my Evita
timmaaa said:
Firstly, you can't just delete the recovery, it doesn't work like that. Anyway, looks like you got TWRP installed again do all you need to do now is install a ROM and away you go. Once you have a ROM installed you can use the phone as normal, but it's pretty strongly suggested you get s-off.
Sent from my Evita
Click to expand...
Click to collapse
The problem is I'm having a bit of trouble finding a ROM and getting S-OFF. I have looked up countless guides and I'm either doing something wrong when I follow guidelines, or they just aren't working.
Using firewater method I get an error the file "not being in directory" when it is in the exact same ADB folder.
Also another thing, if I just get a ROM that support HBOOT 1.09, can I install it with S-ON?
You should be able to install any Sense ROM with your current hboot. Aosp ROMs will require a firmware upgrade though which requires s-off. Trust me, you're gonna want s-off in the long run.
Exactly which ROMs have you tried? What errors are you getting upon installation?
Please note: while Sense ROMs will install, they will not run properly without a firmware upgrade (which requires s-off).
Sent from my Evita
timmaaa said:
You should be able to install any Sense ROM with your current hboot. Aosp ROMs will require a firmware upgrade though which requires s-off. Trust me, you're gonna want s-off in the long run.
Exactly which ROMs have you tried? What errors are you getting upon installation?
Please note: while Sense ROMs will install, they will not run properly without a firmware upgrade (which requires s-off).
Sent from my Evita
Click to expand...
Click to collapse
I tried installing the most recent CyanogenMods and ended up stopping because of HBOOT. I then tried installing AOKP most recent ROMs for my device - from their website.
I'm currently installing Sense 5, I'm following all the rules that HTC Support says.
Don't worry about HTC support, their rules don't really apply to modified phones. Just read my Evita FAQ thread and my How-To Guide For Beginners thread, both links are in my signature.
Sent from my Evita
timmaaa said:
Don't worry about HTC support, their rules don't really apply to modified phones. Just read my Evita FAQ thread and my How-To Guide For Beginners thread, both links are in my signature.
Sent from my Evita
Click to expand...
Click to collapse
Gotcha man, thanks a bunch! I stumbled onto a problem though, How do I enable USB Debugging through TWRP? Using Rumrunenr it says i have to enable it. It says "Debugging On? Latest Drivers?" So yeah.
Friezan said:
Gotcha man, thanks a bunch! I stumbled onto a problem though, How do I enable USB Debugging through TWRP? Using Rumrunenr it says i have to enable it. It says "Debugging On? Latest Drivers?" So yeah.
Click to expand...
Click to collapse
You can't, you can only enable that when booted into Android. So first you need to install a ROM, then you can get s-off. So you're gonna need to install a Sense ROM purely to get s-off, then you can upgrade your firmware and flash whatever you like.
timmaaa said:
You can't, you can only enable that when booted into Android. So first you need to install a ROM, then you can get s-off. So you're gonna need to install a Sense ROM purely to get s-off, then you can upgrade your firmware and flash whatever you like.
Click to expand...
Click to collapse
It says I need the correct rom is there not a HTC One XL from AT&T Sense 5 rom?
Friezan said:
It says I need the correct rom is there not a HTC One XL from AT&T Sense 5 rom?
Click to expand...
Click to collapse
Rumrunner says that? Don't use Rumrunner, try the Facepalm method instead, it's much less temperamental.
Facepalm S-off
timmaaa said:
Rumrunner says that? Don't use Rumrunner, try the Facepalm method instead, it's much less temperamental.
Facepalm S-off
Click to expand...
Click to collapse
Alright this is really frustrating now. I'm getting this error when I'm trying to flash Sturge's Stock Sense 5 ROM. If it's a USB Debugging Problem then how am I supposed to flash it into the SDcard? Should I try pushing it through adb?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That isn't how you flash a ROM. Did you not read the threads in my signature like I suggested?
Sent from my Evita
timmaaa said:
That isn't how you flash a ROM. Did you not read the threads in my signature like I suggested?
Sent from my Evita
Click to expand...
Click to collapse
What I did is just copy and pasted the zip into the Sd card and just installed it from recovery. I've got most of it working timaaa, I get fine signal over WiFi but I'm not getting 3g. Any idea? I've got the Apn settings fine
If you're not getting any data signal, I'd revisit your APN settings, triple check them, they're usually the culprit.
Sent from my Evita