My One S is one of the ones that got ruined by MaximusROM 10.
I've been able to get it back up and running with the latest RUU, but have some severe radio problems. Dropped signal in good areas, reported strong signal but no data transfer, complete connection drop and reconnect, calls not coming through occasionally, texts only working sporadically.
Is there any way to completely wipe and reflash the radio more than the RUU itself does? My phone is nearly useless when not on wifi now.
If you previously installed a radio that altered your rcdata partition then you will need to clear that up.
Previous RUUs going all the way back to ICS don't fix it.
You didn't expand more on your phone's settings but if you're forced to be S-ON and S-OFF constantly bootloops then you're probably having an rcdata problem.
Flash this partition back into your phone.
http://forum.xda-developers.com/showthread.php?p=46045168#post46045168
If you're on the latest RUU with S-OFF and experiencing bootloop you can repeat my steps here:
http://forum.xda-developers.com/showthread.php?p=46308487#post46308487
tsphan said:
If you previously installed a radio that altered your rcdata partition then you will need to clear that up.
Previous RUUs going all the way back to ICS don't fix it.
You didn't expand more on your phone's settings but if you're forced to be S-ON and S-OFF constantly bootloops then you're probably having an rcdata problem.
Flash this partition back into your phone.
http://forum.xda-developers.com/showthread.php?p=46045168#post46045168
If you're on the latest RUU with S-OFF and experiencing bootloop you can repeat my steps here:
http://forum.xda-developers.com/showthread.php?p=46308487#post46308487
Click to expand...
Click to collapse
You're describing my symptoms perfectly, S-OFF bootloops with anything, S-ON is required.
I'll be giving this a shot RIGHT FREAKING NOW. It's the first hope I've had of getting this thing working properly, thanks.
DD'd the partition over, reflashed stock recovery so I could run the OTA update, and it looks like everything's working.
Not as fast as I'd like but that's just the area I'm in atm. Ping times are at least reasonable, and I can MMS pictures again.
THANK YOU.
I'm having the same issues. How do I flash that partition?
Sent from my HTC One S using xda app-developers app
staticmage said:
I'm having the same issues. How do I flash that partition?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
You need to get the file onto your sdcard partition. You can probably do this while S-ON on a working RUU but I haven't tried yet. If you're S-OFF you can follow what I did to get the sdcard mounted and adb working.
Then using adb:
"adb shell"
$ "dd if=/sdcard/mmcblk0p20 of=/dev/block/mmcblk0p20"
The commands in the quote of course.
Could you tell me what you mean by latest RUU? Are you referring to the tmobile RUU or the EU RUU?
Sent from my HTC One S using xda app-developers app
Well, the problem is partially fixed.
I can at least run non-stock ROMs now, and the radio (when it works) is better.
It's still incredibly unstable though. Gonna S-OFF and try updating the radio.
i've also been having few problems since i installed maximusHD 10... i'm trying anything to get it back to work... i lost 3g/4g/hspa/...
now my internet runs only on EDGE/GSM and i know that there is 4g/hspa available in the area where i am
Crap, that didn't fix it. In fact it's back where we were before I got the phone semi-working anyway.
Bootloop central.
Worried I'll never quite get it back :/
E: This was after S-OFFing it. I S-ON'd and RUU/restored backup.
The fix works by flashing the rcdata partition and re flashing firmware.zip
Sent from my One S using xda app-developers app
Killadude said:
The fix works by flashing the rcdata partition and re flashing firmware.zip
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
What hboot you have when flash rcdata partition? You flash over stock RUU or MaximusHD
Sent from my HTC One S using xda app-developers app
kant1988 said:
What hboot you have when flash rcdata partition? You flash over stock RUU or MaximusHD
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
i had 2.15. You can use any software maximus, cm10.1/2.. (not in recovery) that lets you adb shell.
once you flash the rcdata (mmcblckp20) flash the firmware.zip in this thread. You should have radio 1.11 and hboot 2.15 after flashing. Then erase internal storage and install new rom should work now
tsphan said:
You need to get the file onto your sdcard partition. You can probably do this while S-ON on a working RUU but I haven't tried yet. If you're S-OFF you can follow what I did to get the sdcard mounted and adb working.
Then using adb:
"adb shell"
$ "dd if=/sdcard/mmcblk0p20 of=/dev/block/mmcblk0p20"
The commands in the quote of course.
Click to expand...
Click to collapse
Do you need to extract the 7z file?
guys I got similar problems with the radio and unrecognizable sdcard in recovery caused by Maximus rom, I am S-off. Need to fix the phone quick cuz my work depends on it ! help me please what I need to do , just some steps I could find what I need after
Related
Hi
I'm in some sort of a probleme here...
I flash CM10 for the Ville by xkonni & intervigil everything went good ... Than I tried to go back to my nandroid backup that I did before but them the phone would be stuck a the htc one s and beats logo. I somehow manage to get almost everyting to work but , even with the bootloader re-lock and the original rom and file from my nandroid I cant restore everything using the RUU from my phone ( Rogers/fido ) . The thing is, if I look in the log from the RUU install it says : remote: 44 hboot version check fail
Any clue how to restore the original HBOOT ?
!!!!
U need use adb and flash the stock boot.img
Sent from my HTC One S using xda app-developers app
blackhartct said:
U need use adb and flash the stock boot.img
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
That does not change the HBOOT I look at that solution
I don't think you can do anything to the hboot w/o s-off
hboot and boot.img not the same
So, I doubt CM10 would have messed with it
But, it is very experimental--I have been doing this a long time and wouldn't touch CM10 yet--you are braver than me--
Did you wipe ALL including System 2 to 3x before trying nandroid--System would have to be wiped in this case or issues highly likely
rugmankc said:
I don't think you can do anything to the hboot w/o s-off
hboot and boot.img not the same
So, I doubt CM10 would have messed with it
But, it is very experimental--I have been doing this a long time and wouldn't touch CM10 yet--you are braver than me--
Did you wipe ALL including System 2 to 3x before trying nandroid--System would have to be wiped in this case or issues highly likely
Click to expand...
Click to collapse
Is there a technical explanation for the reasons multiple wipes will accomplish more than a single wipe?
In normal cases only official stock HTC RUU's will change your hboot/bootloader. So flash the appropriate RUU with the hboot you had before, first. If you was on software base 1.78 for example, flash the 1.78 RUU and you will have the right hboot.
Sent from my HTC One S using xda premium
Inferi0r said:
In normal cases only official stock HTC RUU's will change your hboot/bootloader. So flash the appropriate RUU with the hboot you had before, first. If you was on software base 1.78 for example, flash the 1.78 RUU and you will have the right hboot.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
This is the log from the RUU.
<T212848><DEBUG><OUT>INFOchecking hboot version...</OUT>
</DEBUG></T212848>
<T212848><DEBUG><OUT>FAILED (remote: 44 hboot version check fail)</OUT>
</DEBUG></T212848>
The orignal Hboot from my provider is 1.08 ( And RUU)
but I check in the rom that I use to flash CM 10 and I cant see any trace of a new HBOOT
so... Where did I get hupdated from 1.08 to 1.13 ?
Because as far as system partition is concerned the wipe does not totally get rid of all files and some stuff can be left behind. Also, installing the new Rom may not overwrite all of the partition. It can cause issues with the new Rom running well. With my N1 even some devs recommended 3 to 4 wipes. System wipe is recommended if going to different Rom or changing basebands. Definitely with coming from CM to Sense.
wiping or formatting a partition multiple times and getting any benefit from that sounds like urban legend
I've seen it recommended by numerous people but there's not any reason to think wiping a partition two times or three times is going to be more effective than one time.
Although if there's a technical explanation I'll hear it out...but stating that formatting a partition one time simply doesn't get it all gone or someone heard it from somewhere else doesn't suffice as enough evidence for me.
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
Does this hboot have any flashing restrictions like hboot 1.14?
Tmobile HTC One™ S
fmedrano1977 said:
Does this hboot have any flashing restrictions like hboot 1.14?
Tmobile HTC One™ S
Click to expand...
Click to collapse
Ya thay the same, only 1.06 and 1.09 are the good ones.
Do any off EU ruu's have 1.06 or 1.09
Tmobile HTC One™ S
You can't downgrade hboot with ruu..
Sent from my HTC One S using xda premium
Not trying to downgrade, I've done that already, currently on 1.09. Trying to rid myself of T-Mobile US firmware, tired of the signal drops that sometimes require reboot to reaquire. Didn't have that symptom while I was on HBOOT 1.14.0002
Tmobile HTC One™ S
fmedrano1977 said:
Not trying to downgrade, I've done that already, currently on 1.09. Trying to rid myself of T-Mobile US firmware, tired of the signal drops that sometimes require reboot to reaquire. Didn't have that symptom while I was on HBOOT 1.14.0002
Tmobile HTC One™ S
Click to expand...
Click to collapse
Have you tried flashing radios?
Darknites said:
Have you tried flashing radios?
Click to expand...
Click to collapse
Two latest, same story
Tmobile HTC One™ S
fmedrano1977 said:
Two latest, same story
Tmobile HTC One™ S
Click to expand...
Click to collapse
Hmm not sure why the Hboot would mess with that. Did you try 1.06 Hboot?
Ok well im on HBOOT 1.14. How do i get to one of the good ones/ Ones that wont give me any problems. Also Do I HAVE to upgrade my radio. Because its at 1.11t. I honestly really need help
tjsinghlion said:
Ok well im on HBOOT 1.14. How do i get to one of the good ones/ Ones that wont give me any problems. Also Do I HAVE to upgrade my radio. Because its at 1.11t. I honestly really need help
Click to expand...
Click to collapse
You have to downgrade the Hboot here.
please help
Darknites said:
You have to downgrade the Hboot here.
Click to expand...
Click to collapse
So is there any other way to get My Hboot downgraded easier. Also What is the restrictions on 1.14. Can i still download and flash roms with 1.14. I know i have alot of questions but i just really want to be safe
tjsinghlion said:
So is there any other way to get My Hboot downgraded easier. Also What is the restrictions on 1.14. Can i still download and flash roms with 1.14. I know i have alot of questions but i just really want to be safe
Click to expand...
Click to collapse
You can flash roms but you have to flash boot.img separately either with fastboot while in bootloader or with app called flash image GUI just befor you flash Rom. You can also change radio using Temporary radio instaler. The only problem for you could be the WiFi not working on sertain roms. But that does not happen to everybody.
Sent from my HTC One S using xda app-developers app
Wait so all I have to do is that flash boot boot.IMG process before I flash a Rom. And do I use the app while on my stock Rom . And when do I use boot.IMG processes
Sorry I just did a little research and answered my own question. Oh and is temporary radio installer an app or what
Sent from my HTC VLE_U using xda app-developers app
Yes look for Flash Image GUI App. You can flash boot.img before rebooting to recovery. Just open app, browse for your Rom, select it, wait until the app extract the boot.img, select flash boot.img, wait, the you'll get a toast message succesfull, then press reboot recovery, wipe everything a few times, flash Rom, wipe cache and dalvik cache again, reboot system.
The temporary radio installer its a zip, you can flash it in custom recovery if you need to change radio.
I also recommend to get a wiping script from ..Awesome.. ( its in devepomnent forum as well) its a zip file, flash from recovery, it will "full wipe your phone" .
I find it better then wiping in twrp recovery.
Good luck.
Sent from my HTC One S using xda app-developers app
tominozh said:
Yes look for Flash Image GUI App. You can flash boot.img before rebooting to recovery. Just open app, browse for your Rom, select it, wait until the app extract the boot.img, select flash boot.img, wait, the you'll get a toast message succesfull, then press reboot recovery, wipe everything a few times, flash Rom, wipe cache and dalvik cache again, reboot system.
The temporary radio installer its a zip, you can flash it in custom recovery if you need to change radio.
I also recommend to get a wiping script from ..Awesome.. ( its in devepomnent forum as well) its a zip file, flash from recovery, it will "full wipe your phone" .
I find it better then wiping in twrp recovery.
Good luck.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
No need for the script. You only need to factory reset and wipe system in TWRP which formats it and not delete it.
Yes, no need, but wiping in twrp did not work for me sometime so if I change roms, I run script as well. If twrp would work 100% no need to do it 2 - 3 times isn't?
Sent from my HTC One S using xda app-developers app
tominozh said:
Yes, no need, but wiping in twrp did not work for me sometime so if I change roms, I run script as well. If twrp would work 100% no need to do it 2 - 3 times isn't?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
TWRP has always worked for me and had no issues but ya wiping more then once is even more of wasted time.
Sent from my HTC One S using Tapatalk 2
TWRP has always worked for me as well. CWM has also always worked for me (on my other devices).
The only thing I wipe more than once is cache and dalvik-cache (before and after rom installation, a total of 2 times wasting ~5sec or so), and I've never had any issue, on ANY of my devices (I have access to an Xperia P in addition to the ones listed in my sign., and Ive helped a couple of friends with flashing/rooting/etc as well)
I have been searching ALL day and can't find it I have hboot 1.14 on my new replacement One S, and I desperately need to update the radio. My room is an absolute dungeon with service, but my wife's T989 works great, so it's my stupid phone not Tmobile.
I have S-OFF with 1.14HBOOT, superCID 11111111
How can I downgrade to 1.09? When I search it, I can only find for the One X/XL
theratdude64 said:
I have S-OFF with 1.14HBOOT, superCID 11111111
How can I downgrade to 1.09? When I search it, I can only find for the One X/XL
Click to expand...
Click to collapse
If you're S-Off, you can flash radios on any hboot. If you want to change your hboot anyway, you can extract an image from a RUU or OTA and dd it into mmcblk0p12. (Be careful with that.)
Find recovery-flashable radios here: http://forum.xda-developers.com/showthread.php?t=1998270
Find recovery-flashable hboots here: http://forum.xda-developers.com/showthread.php?p=38387544#post38387544
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!
Ok here it goes, my Sensation was unlocked, rooted, s-off then I had some network issues so I flashed the stock 3.32 RUU from Bell Canada and took it to a local company to fix. So apparently it had a problem and it needed some software fix. Anyways got it back all is good so my question is am I good to flash again? Bootloader is locked but I have s-off, hboot 1.27.000, I know I need to flash a recovery again but my question really is do I have to root again or am I still? and can just flash recovery then a rom and I'm good to go? Thanks :good:
Yeah you're good with just flashing recovery and then a rom, just don't forget to do a full wipe
Sent from my HTC Sensation 4G using Tapatalk 4 Beta
Right on, thanks! Time to get flashing :victory: Hmm don't know, thinking maybe it was a sim issue because after the fix it still didn't work till I got a new one, good thing they didn't charge me, just had to go out and buy a new sim card.
Yeah but I was thinking, wouldn't your fixes be wiped though?
Sent from my HTC Sensation 4G using Tapatalk 4 Beta
I'm wondering what a "software fix" even is, the guy couldn't tell me, he wasn't the one working on it. What could screw with cell and network connections? Firmware, radio, ril? Was thinking of not touching those because other than that I can't think what else would mess up connectivity that wouldn't already be fixed by RUU.
Same thing I was wondering, if it was a software fix, shouldn't it have been pushed by the carrier? But yes firmware, radio, ril can affect network connection.. If you decide to go back to flashing and experience bad connection again I suggest you start messing with radios with their corresponding rils to see which works best for you.. Last time I checked they were for sense ROMs and caused problems on cm and aosp, but you might want to read up on the thread or ask questions if you are unsure about something
Sent from my SGH-T999 using Tapatalk 4 Beta
Thanks for the help, I think I need to start over anyways now. Tried to flash recovery and fastboot gave me an error: Failed(remote: not allowed). Reading up sounds like hboot issue, solution sounds like s-off and root again.
Sent from my HTC-Z710a using xda premium
You should been able to if you are s-off already, never experienced that error before.. Good luck man
Sent from my HTC Sensation 4G using Tapatalk 4 Beta
serio22 said:
You should been able to if you are s-off already, never experienced that error before.. Good luck man
Sent from my HTC Sensation 4G using Tapatalk 4 Beta
Click to expand...
Click to collapse
I recently flashed hboot 1.29, and my new boot loader is locked even with s off. I like it this way, but until I unlock I too get failed error. It's alright
Happy to help.
mistaliu said:
Thanks for the help, I think I need to start over anyways now. Tried to flash recovery and fastboot gave me an error: Failed(remote: not allowed). Reading up sounds like hboot issue, solution sounds like s-off and root again.
Sent from my HTC-Z710a using xda premium
Click to expand...
Click to collapse
you can't use fastboot commands because now you have locked bootloader
the only thing you have to do is flash 3.33 firmware from here
http://forum.xda-developers.com/showthread.php?t=1459767
it will give you also a patched hboot which is unlocked
follow the instructions carefully
and before flashing check md5sums(important)
then you can flash the recovery using fastboot command
rzr86 said:
you can't use fastboot commands because now you have locked bootloader
the only thing you have to do is flash 3.33 firmware from here
http://forum.xda-developers.com/showthread.php?t=1459767
it will give you also a patched hboot which is unlocked
follow the instructions carefully
and before flashing check md5sums(important)
then you can flash the recovery using fastboot command
Click to expand...
Click to collapse
Ahh didn't think of that. Worked like a charm, everything is good now. Thanks for the help guys!