Hi Guys,
I have been having issues pretty much since I got my phone.
This has been to do with reception, it will say that it has full reception but just won't send messages, make calls or have any connectivity.
I was silly in thinking that maybe flashing a custom rom would help, I still have the issue.
I assume this is a hardware issue so I am at the point where I want to return the phone to Telstra.
I believe if it is a hardware fault I can return it no dramas, just have to flash it back to stock Rom?
Cheers for any help
Alex
Yeah I'd return it to Telstra and try your luck. But I'm not sure whether they'll replace/repair it under warranty though. I've worked at a mobile repair centre for one of the majors here in Australia, they do check whether the handset has been altered. Their excuse for not covering it under warranty will most likely be that the changes you made could have affected the handset, thus causing the issue you're having. It would have been best to send it back before rooting it, then they wouldn't really have a leg to stand on.
Sent from my One XL using XDA Premium
timmaaa said:
Yeah I'd return it to Telstra and try your luck. But I'm not sure whether they'll replace/repair it under warranty though. I've worked at a mobile repair centre for one of the majors here in Australia, they do check whether the handset has been altered. Their excuse for not covering it under warranty will most likely be that the changes you made could have affected the handset, thus causing the issue you're having. It would have been best to send it back before rooting it, then they wouldn't really have a leg to stand on.
Sent from my One XL using XDA Premium
Click to expand...
Click to collapse
Yeah, I was silly to think that I would be able to fix it with a root..
I have heard of people getting repairs after rooting though.
What's the best way to return it to stock?
Root wouldn't fix anything. Flashing a custom ROM wouldn't fix anything more than running an RUU would fix either.
If you didn't have to supercid to root you can just run the RUU. there's a few ruu threads linked in the resource compilation thread. There's a link in my signature.
Sent from my One X using xda app-developers app
exad said:
Root wouldn't fix anything. Flashing a custom ROM wouldn't fix anything more than running an RUU would fix either.
If you didn't have to supercid to root you can just run the RUU. there's a few ruu threads linked in the resource compilation thread. There's a link in my signature.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I've heard of it fixing peoples reception issues, but sadly not mine.
I've currently got Hboot 1.110000
Can I flash the stock Telstra 3.17 RUU on this hboot?
alexc2005 said:
I've heard of it fixing peoples reception issues, but sadly not mine.
I've currently got Hboot 1.110000
Can I flash the stock Telstra 3.17 RUU on this hboot?
Click to expand...
Click to collapse
Yes.
And rooting would not fix Radio reception, Flashing a new Radio might improve reception but for the most part I wouldn't say it would be a drastic change.
exad said:
Yes.
And rooting would not fix Radio reception, Flashing a new Radio might improve reception but for the most part I wouldn't say it would be a drastic change.
Click to expand...
Click to collapse
Thanks for that.
I appear to have my terminology mixed up.
By "rooting" I was referring to the installation of a custom rom and radio.
Hi Exad,
Thanks for your help so far.
I am planning to flash stock recovery and then the stock telstra RUU.
Do you know where I can get the stock recovery from?
Thanks
Alex
I suspect I have found it.
I will extract it from the stock RUU
Thanks!
alexc2005 said:
Hi Exad,
Thanks for your help so far.
I am planning to flash stock recovery and then the stock telstra RUU.
Do you know where I can get the stock recovery from?
Thanks
Alex
Click to expand...
Click to collapse
It included in the ruu just run the ruu it will flash everything for you
Sent from my HTC One X using Tapatalk 2
This might be a dumb question, but my RUU is a zip file...
How do I "run" it?
Note: I changed it from a .zip to a .exe, but apparently there was a file compatibility issue..seems to be an issue with windows, perhaps cause I run 64bit win 7?
alexc2005 said:
This might be a dumb question, but my RUU is a zip file...
How do I "run" it?
Note: I changed it from a .zip to a .exe, but apparently there was a file compatibility issue..seems to be an issue with windows, perhaps cause I run 64bit win 7?
Click to expand...
Click to collapse
If it's a .zip it's an OTA. Those need to be flashed using stock recovery. If you don't have a stock recovery image you can extract it from that zip file, it may be buried deep. It'll be called recovery.img or recovery_signed.img I believe.
You would need to fastboot flash the recovery, then boot to that stock recovery and install the zip file like you would flash a ROM. It could take a while too.
exad said:
If it's a .zip it's an OTA. Those need to be flashed using stock recovery. If you don't have a stock recovery image you can extract it from that zip file, it may be buried deep. It'll be called recovery.img or recovery_signed.img I believe.
You would need to fastboot flash the recovery, then boot to that stock recovery and install the zip file like you would flash a ROM. It could take a while too.
Click to expand...
Click to collapse
Hmm that's interesting.
I have downloaded 2 RUU's, based on filesize (one was 600mb, one was 90mb) both appear to be "OTA"
At this point I have extracted the recovery.img from the OTA zip (in firmware) and flashed that using fastboot and done the oem lock thing too. So it now says relocked.
The point I am up to I believe is flashing the full RUU to the phone, which I believe you have to do through fastboot?
Do I need to flash this via stock recovery? I tried to get into stock recovery last night but it just came up with a red triangle with a ! in it and a phone underneath.
EDIT: ok I got into stock recovery. I don't see a way of flashing it as it doesn't appear to be able to mount my SD Card.
Is there anywhere I can get the RUU and not the OTA? I got the OTA from a thread on here with all of the RUU links. They all seemed to be .zip for Telstra Aus..
I'm going to just use the 1.89 RUU and then upgrade as neccesary.
Can't find the 3.17 .exe.
Should be able to just OTA the newer updates when I boot into the rom.
alexc2005 said:
Hmm that's interesting.
I have downloaded 2 RUU's, based on filesize (one was 600mb, one was 90mb) both appear to be "OTA"
At this point I have extracted the recovery.img from the OTA zip (in firmware) and flashed that using fastboot and done the oem lock thing too. So it now says relocked.
The point I am up to I believe is flashing the full RUU to the phone, which I believe you have to do through fastboot?
Do I need to flash this via stock recovery? I tried to get into stock recovery last night but it just came up with a red triangle with a ! in it and a phone underneath.
EDIT: ok I got into stock recovery. I don't see a way of flashing it as it doesn't appear to be able to mount my SD Card.
Is there anywhere I can get the RUU and not the OTA? I got the OTA from a thread on here with all of the RUU links. They all seemed to be .zip for Telstra Aus..
Click to expand...
Click to collapse
The ruu is a .exe file
Sent from my HTC One X using xda app-developers app
It's possible they didn't release an RUU, I would download an older RUU and then update over the air.
Here's a link to the 1.89 ruu: http://bugsylawson.com/files/file/2...8c320901-1093a3220l-release-266699-signedexe/
Just check for updates after and let it update if you want to go to 3.18
exad said:
It's possible they didn't release an RUU, I would download an older RUU and then update over the air.
Here's a link to the 1.89 ruu: http://bugsylawson.com/files/file/2...8c320901-1093a3220l-release-266699-signedexe/
Just check for updates after and let it update if you want to go to 3.18
Click to expand...
Click to collapse
Yeah, that's my plan . Thanks for all the help mate!
Related
Hi, firstly I apologise for being an idiot.
I rooted my XE last week and have been trying to install ROMs onto it since. I followed numerous guides (not very well apparently) and still cannot get it to work. The problem being every ROM i try to flash after it has installed, during the reboot the white htc screen comes up over and over again.
I've tried numerous ROMs, stock ROMs and nothing has worked. I tried to locate the original backup I made but it seems to be gone too
Any help would be appreciated, otherwise I've blown a couple of hundred quid.
Do you know how to run a log cat and post the results as this would help people help you better. But then again there is always the option to just download the correct RUU for your Sensation, flash the stock ROM with it, and then start all over.
T-Macgnolia said:
Do you know how to run a log cat and post the results as this would help people help you better. But then again there is always the option to just download the correct RUU for your Sensation, flash the stock ROM with it, and then start all over.
Click to expand...
Click to collapse
What / how would I start all over if I had the correct RUU and ROM (both of which I think I have). The RUU is an exe file? Is that correct and the ROM I just put on the root of my SD?
Grrrrr. I feel very stupid, usually nae bad at techy stuff!
Yes the RUU is a .exe file that will flash the stock ROM to your Sensation, notice I said stock ROM wich means you will not be rooted anymore, you will have the stock recovery again, and you will more than likely be S-on again. This is why I said you would have to start over again if you use the RUU.
The ROM does go on your SD card but if it is a stock ROM you will have to have the stock recovery to flash it, if it is a custom ROM you will have to have S-off and a custom recovery.
T-Macgnolia said:
Yes the RUU is a .exe file that will flash the stock ROM to your Sensation, notice I said stock ROM wich means you will not be rooted anymore, you will have the stock recovery again, and you will more than likely be S-on again. This is why I said you would have to start over again if you use the RUU.
The ROM does go on your SD card but if it is a stock ROM you will have to have the stock recovery to flash it, if it is a custom ROM you will have to have S-off and a custom recovery.
Click to expand...
Click to collapse
So apparently I have the wrong RUU? How would I find out which is the correct one?
Thanks for your help and patience so far!
Have you made sure you have the correct firmware for the Rom you are trying to install?
Sent from my HTC Sensation XE with Beats Audio using xda premium
radixon said:
Have you made sure you have the correct firmware for the Rom you are trying to install?
Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
Yeah I'm pretty sure it is! PG58IMG?
When I run the RUU it comes up with current image version: 1.73.401.2
Then when it goes to update the ROM it comes up saying unknown error 155, wrong RUU???
It sounds like you may have the wrong RUU, who is your carrier and what is the region did your Sensation originate from. This is the information you need to get your correct RUU.
T-Macgnolia said:
It sounds like you may have the wrong RUU, who is your carrier and what is the region did your Sensation originate from. This is the information you need to get your correct RUU.
Click to expand...
Click to collapse
It is unlocked from the UK, probably 02 but unlocked as I said, using an orange sim. Where could I find this info?
lewento said:
It is unlocked from the UK, probably 02 but unlocked as I said, using an orange sim. Where could I find this info?
Click to expand...
Click to collapse
Ok if it is from the UK you probably need the "RUU_Pyramid_O2_UK_1.34.206.1_Radio_10.43a.9007.00U_10.51.9007.27_M", you can find it here. Remeber you will have to have the HTC Sync drivers installed on your computer, and you will have to boot into the Hboot then the bootloader and connect your Sensation via USB to your computer before running the RUU.
Ok,
So I've used roms on my hd2 and one x, so I thought this would be simple on a friends sensation, oh how wrong was I.
I have unlocked the sensation via htcdev, installed clockworkmod and installed pyramids jellybean rom.
Now I have all sorts of issues, the rom boots then drops somehow straight to clockworkmod. I can't mount the sd card within clockworkmod to try a different rom and the phone is now useless, doh.
How can I fix this please guys?
Did you update the firmware? Are you s off or s on? If your s on you must flash boot image. Download 4 ext recovery, enable smart flash in 4ext. This way you can flash boot image. Please read flashing roms with s on. Also for that rom the firmware must also be upgraded. Let me link you to the guide to flashing roms with s on. This will help http://forum.xda-developers.com/showthread.php?t=1631861
Someone more knowledgeable than myself can give you step by step instructions to get you out of this pinch. But in the mean time read the link I posted about flashing with s on. It will help in the future. Best wishes not to worry I'm sure you can fix this.
Sent from my HTC Sensation using xda premium
daz1uk said:
Ok,
So I've used roms on my hd2 and one x, so I thought this would be simple on a friends sensation, oh how wrong was I.
I have unlocked the sensation via htcdev, installed clockworkmod and installed pyramids jellybean rom.
Now I have all sorts of issues, the rom boots then drops somehow straight to clockworkmod. I can't mount the sd card within clockworkmod to try a different rom and the phone is now useless, doh.
How can I fix this please guys?
Click to expand...
Click to collapse
HTC Dev doesn't really unlock it. It only partially unlocks it.
It doesn't s-off the device so you don't have access to the system partition, meaning you can't properly install a custom ROM without a few extra steps. And I don't think you can do it at all with clockworkmod. You need 4EXT Recovery which can flash a ROM with s-on. There's a few extra steps to doing it but it works.
You also have to make sure you have the correct firmware. So if the device was previously on a Gingerbread ROM and you didn't upgrade firmware, it won't work.
Now, the part where it boots then drops back into recovery is weird.
Tell us exactly what steps you did so we can better determine where something went flukely.
I'm CERTAIN it's fixable though.
realsis said:
Did you update the firmware? Are you s off or s on? If your s on you must flash boot image. Download 4 ext recovery, enable smart flash in 4ext. This way you can flash boot image. Please read flashing roms with s on. Also for that rom the firmware must also be upgraded. Let me link you to the guide to flashing roms with s on. This will help http://forum.xda-developers.com/showthread.php?t=1631861
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Thanks for responding.
I've got S-OFF and flashed boot.img with adb.
Will 4EXT allow me to mount the sd card?
Yes it should
Also some roms require 4ext it's a super easy touch recovery to use. You can download from here or the playstore.
Sent from my HTC Sensation using xda premium
Skipjacks said:
HTC Dev doesn't really unlock it. It only partially unlocks it.
It doesn't s-off the device so you don't have access to the system partition, meaning you can't properly install a custom ROM without a few extra steps. And I don't think you can do it at all with clockworkmod. You need 4EXT Recovery which can flash a ROM with s-on. There's a few extra steps to doing it but it works.
You also have to make sure you have the correct firmware. So if the device was previously on a Gingerbread ROM and you didn't upgrade firmware, it won't work.
Now, the part where it boots then drops back into recovery is weird.
Tell us exactly what steps you did so we can better determine where something went flukely.
I'm CERTAIN it's fixable though.
Click to expand...
Click to collapse
Yeah I'm certain it's fixable too , just not sure how, lol. I'll give 4EXT a shot. I have no idea how or why it drops straight to clockworkmod either, I would expect it to reboot to clockworkmod if anything, but it just kind of switches from the rom straight to it, very odd.
If you could point me to a firmware I might need I would be very grateful.
It is universal 3.33 let me get link also 3.32 will work on most ics roms but 3.33 is the newest I'm running jelly bean and use 3.33
http://forum.xda-developers.com/showthread.php?t=1459767
Sent from my HTC Sensation using xda premium
daz1uk said:
Thanks for responding.
I've got S-OFF and flashed boot.img with adb.
Will 4EXT allow me to mount the sd card?
Click to expand...
Click to collapse
If you are s-off you shouldn't have to flash boot.img separately. It will do all that with the ROM flash.
Maybe that's what's screwy. Though a borked up ROM still shouldn't affect SD card mounting in recovery...that is really weird. Do you have a card reader that you can use to check the card out in your computer? I'm wondering if somehow you screwed up the card when flashing the ROM. Maybe it wont' mount because the card isn't formatted properly anymore. Stuff like that has happened before.
daz1uk said:
Yeah I'm certain it's fixable too , just not sure how, lol. I'll give 4EXT a shot. I have no idea how or why it drops straight to clockworkmod either, I would expect it to reboot to clockworkmod if anything, but it just kind of switches from the rom straight to it, very odd.
If you could point me to a firmware I might need I would be very grateful.
Click to expand...
Click to collapse
Hi,
What does your bootloader say?
hboot etc.
Yes if your s off you simply flash from recovery without boot img. But do update your firmware.
Sent from my HTC Sensation using xda premium
malybru said:
Hi,
What does your bootloader say?
hboot etc.
Click to expand...
Click to collapse
Bootloader says:
S-ON
Ok, so I think I need to update the firmware?
I've installed EXT4, still cant mount sd, so can't revert to another rom.
daz1uk said:
Ok, so I think I need to update the firmware?
I've installed EXT4, still cant mount sd, so can't revert to another rom.
Click to expand...
Click to collapse
Hi,
If you are s-on,you cannot update your firmware.
What is your hboot?
malybru said:
Hi,
If you are s-on,you cannot update your firmware.
What is your hboot?
Click to expand...
Click to collapse
hboot 1.18.0000
Unlocked
S-ON
As far as I was aware S-ON just prevented the boot.img from being written via recovery, which can be done with adb. So the only reasons for these issues must be firmware version right?
daz1uk said:
hboot 1.18.0000
Unlocked
S-ON
Click to expand...
Click to collapse
Hi,
It is a pity you went to HTC to unlock your phone.
I wonder if you can still s-off using revolutionary.
You are going to need to run a RUU,and hopefully get a working phone again.
Try and find a RUU HERE that matches your area and carrier.
daz1uk said:
hboot 1.18.0000
Unlocked
S-ON
As far as I was aware S-ON just prevented the boot.img from being written via recovery, which can be done with adb. So the only reasons for these issues must be firmware version right?
Click to expand...
Click to collapse
Yup. If you have the 1.18 hboot you have Gingerbread firmware, which won't support Jellybean or ICS.
The good news is that you can flash a gingerbread rom and get the phone back to a working state right away if you need to get the phone back to the owner.
The RUU to restore is pretty simple. Then Revolutionary s-off proceedure is also extremely painless.
Reverting back to stock and starting over to s-off shouldn't take more than 15 minutes if you do it right. Then flashing the ICS/GB firmware (3.32 or 3.33) takes 3 minutes. Then the new rom takes 3 more minutes.
Just make sure you RUU to gingerbread and not to ICS. The ICS Hboots are harder to s-off. It's worth adding the extra step to flash the ICS/JB firmware later.
This is driving me nuts, tried 2 ruu's, both failed, if it was my phone it would be out the window!
daz1uk said:
This is driving me nuts, tried 2 ruu's, both failed, if it was my phone it would be out the window!
Click to expand...
Click to collapse
Hi,
Are you Sensation,or Sensation XE?
daz1uk said:
This is driving me nuts, tried 2 ruu's, both failed, if it was my phone it would be out the window!
Click to expand...
Click to collapse
Doh, my fault forgot to re-lock it, update is installing as I type, phew!
Sent from my HTC One X using Tapatalk 2
I decided to downgrade to 1.85 for a fresh start after downgrading hboot to 1.09.000. 1.85, 1.73 RUUs failed and im trying 2.20 as we speak :// if this fails what are mmy options?
thanks
Did you relock the bootloader?
Sent from my HTC One XL using xda app-developers app
RUU's still fail after Jet to 1.09 due to version reported on mmcblk0p23.
Fix here:
http://forum.xda-developers.com/showthread.php?t=1671135
Note one user reported that going from 3.17 back to 1.81 ended in a bricked phone.
After Jet to 1.09 and altering mmcblk0p23 version, RUU accepted flashing, but bricked phone.
area51avenger said:
Did you relock the bootloader?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
yes
twistedddx said:
RUU's still fail after Jet to 1.09 due to version reported on mmcblk0p23.
Fix here:
http://forum.xda-developers.com/showthread.php?t=1671135
Note one user reported that going from 3.17 back to 1.81 ended in a bricked phone.
After Jet to 1.09 and altering mmcblk0p23 version, RUU accepted flashing, but bricked phone.
Click to expand...
Click to collapse
I did this and I keep getting error 140- per this I am stuck in bl and I cant get adb
anyone? im in need of desperate help..
You don't need to run an ruu.... you downgraded your boot loader so just go on to flashing ROMs
You can flash the old radios and you should be set
No reason to put yourself through all this trouble
Sent from my One X using Tapatalk 2
superchilpil said:
You don't need to run an ruu.... you downgraded your boot loader so just go on to flashing ROMs
You can flash the old radios and you should be set
No reason to put yourself through all this trouble
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
that's the problem, I relocked the BL, so now m stuck in fastboot with a locked boot loader any way I could get to adb so I can re unlock it?
Kole_Ackerson said:
that's the problem, I relocked the BL, so now m stuck in fastboot with a locked boot loader any way I could get to adb so I can re unlock it?
Click to expand...
Click to collapse
If you still have your unlock token
Fastboot flash unlocktoken unlocktoken.bin
Replace unlocktoken.bin with the location of your old unlock token
If you don't have it go through the steps on HTC dev to get a new one. You don't need to boot up the phone, just need fastboot
Sent from my One X using Tapatalk 2
superchilpil said:
If you still have your unlock token
Fastboot flash unlocktoken unlocktoken.bin
Replace unlocktoken.bin with the location of your old unlock token
If you don't have it go through the steps on HTC dev to get a new one. You don't need to boot up the phone, just need fastboot
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
ok, I got the unlock token but its hanging on sending (0kb)
Kole_Ackerson said:
ok, I got the unlock token but its hanging on sending (0kb)
Click to expand...
Click to collapse
Make sure you're in fastboot not hboot
If that doesn't work reset your computer to make sure not programs are interfering with it
Sent from my One X using Tapatalk 2
it is in fastboot usb so ill reset my comp.
If it fails again, try running
Fastboot devices
To see if your device is showing up
Sent from my One X using Tapatalk 2
superchilpil said:
If it fails again, try running
Fastboot devices
To see if your device is showing up
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
wow,i got it. it was my usb port... and ive been in 1.14 for so long I forgot that I can just unlock with 1.09... ill be buuying you a beer when I get paid.
Kole_Ackerson said:
wow,i got it. it was my usb port... and ive been in 1.14 for so long I forgot that I can just unlock with 1.09... ill be buuying you a beer when I get paid.
Click to expand...
Click to collapse
Nah don't worry about it!
Just helping out where I can
Sent from my One X using Tapatalk 2
Can only boot to bootloader and all RUU failed
I am in a bit of trouble at the moment. I will try to describe what I have done to end up where I am now.
I have a Telstra HTC One XL. Recently upgraded an already unlocked, rooted HOXL to JB using the OTA update (big mistake I know now). This upgraded the hboot to 2.14 and software to 3.17.8xxx.
Spent a lot of time trying to re-root. TWRP didn't work (no touch response). So I eventually found the Interim CWM Recovery (no touch) by Modaco. This seemed to work well and I managed to root the phone.
Then i followed the instructions to flash to KingBeatZ 1.2.0 ROM. Booted fine but had no touch response too.
So I wiped KingBeatZ 1.2.0 and went for the nightly CM10. Again, booted fine but no touch response.
OK, so I figured I should just go back to my restored data. Tried that but apparently no restore data (didn't realise a wipe wiped the restore data as well, what is the point of that?)
So I decided to wipe CM10 to try flashing the Stock Rooted Telstra ROM by pablo11. This wipe however seems to have wiped incorrectly and this is where my real problem begins. I can now only boot to BL and Recovery. I cannot mount the sdcard so I have no way of pushing ROMS to my phone. I have tried a Telstra RUU and the latest Asia one. About to try the 1.89 Telstra RUU but I don't think that will make any difference. The setups do not detect an existing version on my phone, and all fail with Error 155. I have read that this error generally occurs due to unlocked bootloader so I have already relocked it.
I do not know what I should do now to restore any functionality to my HOXL. Any help would be greatly appreciated.
o0okiato0o said:
So I decided to wipe CM10 to try flashing the Stock Rooted Telstra ROM by pablo11. This wipe however seems to have wiped incorrectly and this is where my real problem begins. I can now only boot to BL and Recovery. I cannot mount the sdcard so I have no way of pushing ROMS to my phone. I have tried a Telstra RUU and the latest Asia one. About to try the 1.89 Telstra RUU but I don't think that will make any difference. The setups do not detect an existing version on my phone, and all fail with Error 155. I have read that this error generally occurs due to unlocked bootloader so I have already relocked it.
Click to expand...
Click to collapse
You can't run the RUU for a different carrier (CID), and you can't run an RUU for an older version. So neither 1.89 Telstra or an Asia RUU will work. You may be stuck waiting for the 3.17 RUU (don't think its been posted yet?).
You might also be able to make your own RUU by sticking the ROM in the Development forum in an RUU package. I don't know the specifics, and haven't done it myself. But I think it was done for Rogers, which never had a proper RUU package. So others might be able to advise you better on this.
redpoint73 said:
You can't run the RUU for a different carrier (CID), and you can't run an RUU for an older version. So neither 1.89 Telstra or an Asia RUU will work. You may be stuck waiting for the 3.17 RUU (don't think its been posted yet?).
You might also be able to make your own RUU by sticking the ROM in the Development forum in an RUU package. I don't know the specifics, and haven't done it myself. But I think it was done for Rogers, which never had a proper RUU package. So others might be able to advise you better on this.
Click to expand...
Click to collapse
You would need the .img files EX: system.img boot.img
Since our ROMs aren't packaged that way it won't work.
There's a way to create the system.img but its beyond me, and I do believe if it isn't signed it will fail
The only thing you can flash in hboot by ruu without s-off without being signed would be a boot.img
I would suggest trying to flash a stock ROM and a different kernel, or waiting for the ruu
Sent from my One X using Tapatalk 2
superchilpil said:
You would need the .img files EX: system.img boot.img
Since our ROMs aren't packaged that way it won't work.
There's a way to create the system.img but its beyond me, and I do believe if it isn't signed it will fail
The only thing you can flash in hboot by ruu without s-off without being signed would be a boot.img
I would suggest trying to flash a stock ROM and a different kernel, or waiting for the ruu
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Could you elaborate on the different kernel bit? I have just tried flashing a stock rom via the fastboot flash zip rom.zip method, but it fails the hboot check. Cheers
o0okiato0o said:
Could you elaborate on the different kernel bit? I have just tried flashing a stock rom via the fastboot flash zip rom.zip method, but it fails the hboot check. Cheers
Click to expand...
Click to collapse
Take a stock ROM and pull out the boot.img
And fastboot flash boot boot.img just to make sure it flashes
Then flash the ROM in recovery
Sent from my One X using Tapatalk 2
Hi everyone,
I don't quite have 10 posts yet, so I can't post in the UrDroid thread.
I had UrDroid 1.8, and it worked just fine, had some wifi issues (sometimes after turning the wifi off, it wouldn't turn on again unless I rebooted), so I upgraded to 1.9
Now I have a few issues:
It stays "connected" to a wifi network even after losing connection
Occasionally, after rebooting, my Beautiful Widgets go away and my default keyboard reverts to the stock keyboard (from swype)
occasionally I cannot turn the wifi back on after turning it off without a reboot
That's about it. If anyone has any ideas, please let me know. Thanks! :good:
Could be just bugs in the software. Recommend trying different ROMs
Sent from my Carbon-ize Evita using xda-developers app
I really wish I could try other roms, for some reason UrDroid is the only one that actually works, I have no idea why this is!
For instance, when flashing any verison of CM, after flashing and rebooting, it stays stuck on the loading screen, and doesn't go further, even after waiting a half an hour. AOKP and the others basically brick my phone. I think it has something to do with the UrDroid using Aroma Installer that seems to work well with my phone and twrp. I'm a bit of a n00b, so don't know for sure.
Was hoping someone else had these issues and could tell me how they fixed them.
Herc08 said:
Could be just bugs in the software. Recommend trying different ROMs
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
What recovery are you using and version?
What hboot do you have?
Sent from my One X using xda app-developers app
Sorry for the late reply,I've had the darndest time getting into recovery since installing UrDroid 1.9!
I have HBOOT-1.14.002 and TWRP v. 2.3.1.0
Thanks for any help you could offer- I like UrDroid, but would like to try CM or the other ones!
exad said:
What recovery are you using and version?
What hboot do you have?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
choeffe said:
Sorry for the late reply,I've had the darndest time getting into recovery since installing UrDroid 1.9!
I have HBOOT-1.14.002 and TWRP v. 2.3.1.0
Thanks for any help you could offer- I like UrDroid, but would like to try CM or the other ones!
Click to expand...
Click to collapse
Because of your hboot version you need to flash the boot.img seperately. It is possible that you are doing this but still encountering bootloops and the reason for that would be Hboot compatibility. I have noticed that some ROMs just do not play nice with certain hboots. The most compatible hboot that I've seen is 2.14 which seems to be the same accross all carrier phones.
That being said, my suggestion to you is to S-OFF if you aren't already, then, while keeping your bootloader unlocked, RUU up to 3.18 or 3.17 or whatever is the latest for your carrier which will update your hboot to 2.14 and then downgrade your touchscreen firmware which is super easy and there's a sticky for the process in the Original Android Development section.
After that, you should be able to run all roms without much issue AND you won't have to fastboot flash boot boot.img anymore.
That explains it- I literally have just been going into TWRP, installing the zip file, and then rebooting. I'm not even sure where I would find the boot.img, would that be inside the zip file?
So to S-OFF, should I follow the directions here: http://forum.xda-developers.com/showthread.php?t=2155071
I'm not sure how to RUU, any chance you or someone might have a link on instructions to do that? (I have an AT&T phone that I use on Straight Talk)
Thanks for your help, and if I'm asking for too much information, I'll keep doing some reasearch. I think the RUU is what kind of puzzles me (I'm clearly pretty green when it comes to rooting, I've only ever done it on this phone, not very successfully!
exad said:
Because of your hboot version you need to flash the boot.img seperately. It is possible that you are doing this but still encountering bootloops and the reason for that would be Hboot compatibility. I have noticed that some ROMs just do not play nice with certain hboots. The most compatible hboot that I've seen is 2.14 which seems to be the same accross all carrier phones.
That being said, my suggestion to you is to S-OFF if you aren't already, then, while keeping your bootloader unlocked, RUU up to 3.18 or 3.17 or whatever is the latest for your carrier which will update your hboot to 2.14 and then downgrade your touchscreen firmware which is super easy and there's a sticky for the process in the Original Android Development section.
After that, you should be able to run all roms without much issue AND you won't have to fastboot flash boot boot.img anymore.
Click to expand...
Click to collapse
choeffe said:
That explains it- I literally have just been going into TWRP, installing the zip file, and then rebooting. I'm not even sure where I would find the boot.img, would that be inside the zip file?
Click to expand...
Click to collapse
Yes it's in the zip. You extract it then fastboot flash boot boot.Img right before or after flashing the rom in recovery. Before flashing the rom and boot.img you should wipe cache, dalvik, system and factory reset. And only ever flash roms for the one xl or you risk bricking.
choeffe said:
So to S-OFF, should I follow the directions here: http://forum.xda-developers.com/showthread.php?t=2155071
Click to expand...
Click to collapse
Yes
choeffe said:
I'm not sure how to RUU, any chance you or someone might have a link on instructions to do that? (I have an AT&T phone that I use on Straight Talk)
Thanks for your help, and if I'm asking for too much information, I'll keep doing some reasearch. I think the RUU is what kind of puzzles me (I'm clearly pretty green when it comes to rooting, I've only ever done it on this phone, not very successfully!
Click to expand...
Click to collapse
To ruu, just download the ruu exe file and run it. But make sure you're s-off first or you'll brick.
Reading the stickies is suggested. You picked a ***** of a phone to be your first to root.
Sent from my One X using xda app-developers app
Thanks for your help thus far! I'm going to give it a try and see how it goes.
Yeah, I definitely wish I would have started with a Nexus or Sony device, but I changed from T-Mobile (worse decision of my life to go with them in the first place) to Straight Talk SIM with AT&T, and the HTC One X looked so pretty! Next phone is going to be a Nexus!
exad said:
Yes it's in the zip. You extract it then fastboot flash boot boot.Img right before or after flashing the rom in recovery. Before flashing the rom and boot.img you should wipe cache, dalvik, system and factory reset. And only ever flash roms for the one xl or you risk bricking.
Yes
To ruu, just download the ruu exe file and run it. But make sure you're s-off first or you'll brick.
Reading the stickies is suggested. You picked a ***** of a phone to be your first to root.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Hello all,
So finally, I have managed to S-OFF my phone using JuonoputBear (I never get this spelling right!). Downloaded the latest version for Ubuntu and can't believe I only did the wire trick once and it was done.
But anynow, to my surprise, the JB tool went on installing the JB hboot itself. Initially I thought it would ask me to install it or not and I would refuse it but... it didn't even give me the option. So now I am stuck with the JB hboot which I dont want.
So the questions is, is there any way I can revert back to the stock hboot?
Thanks guys, all your help made it possible for me to S-OFF my phone.
Regards
just to know that with patched hboot you are fully unlocked and you can use all fastboot commands
i don't find a reason to return to official hboot
rzr86 said:
just to know that with patched hboot you are fully unlocked and you can use all fastboot commands
i don't find a reason to return to official hboot
Click to expand...
Click to collapse
Thanks for the reply. The reason I wanted to go back to stock hboot was that its highly unlikely that I would be using those extra fastboot commands. Besides, I dont like the Juoponutbear logo on top of the hboot.
Also, now that I am S-OFF, I am kind of gone sensitive to installing any ROM. I intend to install Android Revolution HD ROM but I dont want to flash anything wrong on my device like Radio etc. I only want to flash whats need to run that new custom ROM. I guess that doesn't include the kernel as I already have ICS stock ROM.
Can anyone point me to the right direction? Where I can find the steps to install custom ROM without any risk of flashing something wrong?
Thanks.
Jeanz Sensation said:
Thanks for the reply. The reason I wanted to go back to stock hboot was that its highly unlikely that I would be using those extra fastboot commands. Besides, I dont like the Juoponutbear logo on top of the hboot.
Also, now that I am S-OFF, I am kind of gone sensitive to installing any ROM. I intend to install Android Revolution HD ROM but I dont want to flash anything wrong on my device like Radio etc. I only want to flash whats need to run that new custom ROM. I guess that doesn't include the kernel as I already have ICS stock ROM.
Can anyone point me to the right direction? Where I can find the steps to install custom ROM without any risk of flashing something wrong?
Thanks.
Click to expand...
Click to collapse
Hi,
There is no way you can "Accidently" install a radio.
You are not in bootloader for any length of time normally,so ,it should not matter what is written at the top.
That is just the way Juoponutbear operates and leaves it's mark.
It is the only way to s-off for you,so ,you are stuck with it.
Unless you s-on again.
As for flashing ROMS,put it on the root of your sd card,choose zip,install zip.
That's it.
EDIT:
Someone correct me if I am wrong.
If you flash Kohr-Ah's Universal 3.33 firmware,does it say Universal at the top?
malybru said:
As for flashing ROMS,put it on the root of your sd card,choose zip,install zip.
That's it.
Click to expand...
Click to collapse
Is that all? I thought that once you have flashed the zip package, you have to extract the "boot.img" from that zip package of the ROM and flash it separately?
Jeanz Sensation said:
Is that all? I thought that once you have flashed the zip package, you have to extract the "boot.img" from that zip package of the ROM and flash it separately?
Click to expand...
Click to collapse
Hi,
That is the beauty of s-off.
No separate flashing.
malybru said:
Hi,
That is the beauty of s-off.
No separate flashing.
Click to expand...
Click to collapse
Ahh I get it now. Thanks mate.
malybru said:
Hi,
There is no way you can "Accidently" install a radio.
You are not in bootloader for any length of time normally,so ,it should not matter what is written at the top.
That is just the way Juoponutbear operates and leaves it's mark.
It is the only way to s-off for you,so ,you are stuck with it.
Unless you s-on again.
As for flashing ROMS,put it on the root of your sd card,choose zip,install zip.
That's it.
EDIT:
Someone correct me if I am wrong.
If you flash Kohr-Ah's Universal 3.33 firmware,does it say Universal at the top?
Click to expand...
Click to collapse
if i remember well last time kohr-ah said that it it says firmware 3.33(i am not sure)
malybru said:
Hi,
That is the beauty of s-off.
No separate flashing.
Click to expand...
Click to collapse
Sorry I had to come back on this one. I was checking the Android Rev. HD thread and in the download section it said it is necessary to flash new firmware package before flashing this ROM/ And the firmware package also contains radio flashing.
Since I am on Stock ICS at the moment and my firmware is 3.32. Do I still need to flash my firmware?
Jeanz Sensation said:
Sorry I had to come back on this one. I was checking the Android Rev. HD thread and in the download section it said it is necessary to flash new firmware package before flashing this ROM/ And the firmware package also contains radio flashing.
Since I am on Stock ICS at the moment and my firmware is 3.32. Do I still need to flash my firmware?
Click to expand...
Click to collapse
it is not necessary
the rom will boot with that firmware too:good: