Afternoon all,
A little help and advice if I may?
Running a custom ROM with HBoot 2.19 and S-On
Trying very hard to return to full blown unrooted stock so banking apps will work (I've tried every work around there is possible to fake unroot but they just don't work).
This gentleman here (http://forum.xda-developers.com/htc...m-official-stock-android-4-3-sense-5-t2837799 ) seems to be the means of getting back to stock but requires S-Off and HBoot 2.22
I've tried firewater but get an error saying HTC have put anti-firewater protection in then it bombs out. (Tried using KAngaroo kernal and SS Kernal from the dev page)
I've tried rumrunner_HTC_0.5.0 but even with Windows Firewall off, no anti-virus and even putting my laptop into a DMZ I still get the fatal error when trying to download the tool.
From what I gather I cannot get onto HBoot 2.22 to try alternative custom Roms until I S-Off the bloody thing which appears to be impossible.
Any ideas?
All comments will receive thumbs up and a cake in the post.
Thanks
That backup should still work even if you're S-on. It did for me. I'm not sure about the HBOOT but if you backup where you are now, you're no worse off if it doesn't work.
I had to do the same thing so my network's Wi-Fi calling app would work.
I only had to S-off afterwards to change my CID to get official OTA updates, you may not need to do that step in which case S-off is fine.
Related
ok...i'm trying to unroot a friends inspire as its doing nothing but give problems even after wiping and flashing multiple roms. its a faulty phone. no doubt. try to return to stock.
the s-on tool is throwing up an error.....
attempting to power cycle eMMC....failed.
module failed to load. no file or directory.
you should be s-on....
but i'm totally not s-on.
is it because i'm runnin with cm7 currently? it did scan the kernel version and came up cm.
his recovery wont stop freezing either. theres really something wrong. its frustrating as hell that i cant just wipe and flash without i freezing ****in up.
Yes, gfree requires a very specific radio and a pretty specific kernel. Gfree was built to work with the ROM that we know as the "downgrade" ROM (HTC ver 1.32.405.6). The good news is that you won't have to go through the trouble of a gold-card since you're already S-OFF. Get the ROM in PD98IMG format here:
http://android.d3xt3r01.tk/cyanogen/ace/stock/1.32.405.6/PD98IMG.zip
I have been reading about the risks of going back to S-ON, and people having issues with updating CWM from 4.0.1.4 (what I have) so here is my story. My building was condemned and my lady and I are living in a motel and searching for an apartment. I have my laptop and HTC sensation. Only means of contact but my sensation has been acting up. Calls going straight to voice with no notification. No missed call indicator. T-mobil says it's because I have no signal but then they call me and it works without the phone moving. I don't believe or trust them.
I thought I did it all but I I messed up some how. I have S-OFF and revolutionary installed but my hboot is still 1.17.1111 and CID is T-MOB010. Root checker says not rooted
Radio=10.14.9035.01_m.
emmc=boot
under simlock
fat 32 init ok
open mccmnc file failed
open cid file failed.
What would be less risky at this point or do I even have a choice? If I read correctly I must still go ahead with rooting and SuperCid before I can even think about going back to stock even though it looks like I have stock rom and hboot.
Any and all thought/insight would help.
Are you asking how to go back to pure stock so you can get warranty repair / replacement?
If you are s-off you can always do a full wipe and install a new ROM and see if that fixes it.
You might try to flash a new radio too since you're having signal issues.
I had CM10 Nightlies running, and I decided I just wanted to be done and go back to full unrooted stock. So I downloaded the 1.85 RUU, relocked the BL, and ran the RUU.exe... After that it was just fine, but I realized I missed a lot of the basic things that come from having root. So I rerooted and installed TrickDroid... But The page I was on didn't clearly explain that it was for the European HTC One S. Trick Droid 8.1.0. So I flashed this, and upon running, it was messing up in a lot of ways. Can't explain it, but the point is that it was not something I'd use as a daily driver. I then went to do a full wipe and flash Team Venom's Sense ROM. Which I did.... but the wifi didn't work. AT ALL. Just doesn't turn on. I thought it was the ROM, so I wiped and installed MIUI. (Which I'm loving) But again, no wifi. PLUS Camera crashes. No error message, just closes. Can't use it at all. I realized my mistake with TrickDroid, and tried to reflash the RUU (after flashing a stock ROM and relocking BL etc) But it gives me ERROR 155 (UNKNOWN ERROR) - On my phone it says "Hboot version is too new!" It seems to me, that my Hboot is now the one from 2.35 RUU (Which noone officially has released) The only way I can imagine getting this, is with the european ROM. Can it do that? I have Hboot 1.14.0004
I'm out of ideas, and very very frustrated. I can't flash an RUU. And we don't have S-OFF, so downgrading my hboot isn't an option, right?
Please, anybody that can help will definitely get my verbal thanks as well as click on the button. I need someone to sort this out with me.
Thanks.
EDIT: I changed my CID to SUPERCID and flashed the European 2.21 RUU and I'm all set. Thanks a TON to this thread - http://forum.xda-developers.com/showthread.php?t=1927939
Not quite the same beginning situation, so hopefully people with MY situation will find this post and be helped!
Hi Guys, I've tried to do this myself reading other posts and not creating a thread but I have failed miserably so I am in need of some advice now. I need to try and get back to stock due to a warranty issue so I was following this guide here: http://forum.xda-developers.com/showthread.php?t=1460713
It seemed to be going well and I flashed the hboot which removed the revolutionary version, the RUU I used was the only Tmobile version I could find RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed and it started running through, it updated the hboot which is now S-On version 0.98.0000 but after that point it failed with error 140.
I don't understand why this has happened though as surely the version 0.98.0000 HBoot version is what is installed by the RUU itself so how can this be the wrong version? Is there something else I'm missing here.
At this point the phone is connected by USB to my laptop still and sat in HBoot, I'm not even sure if I can safely reboot at the moment so need some advice on what to do next?
I did that, had the same problem (around 3 weeks before you). I just ran it a gazillion times and then, I ended up flashing RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068 anyway. That worked. T-Mobile/HTC never said a word, fixed it and then sent my phone back.
But beware, the phone sent back will return on:
Android 4.0.4
Sense 3.6
Hboot 2.02.0002
Radio 20.76.30.0835U_3831.19.00.110
rlzzzz said:
Hi Guys, I've tried to do this myself reading other posts and not creating a thread but I have failed miserably so I am in need of some advice now. I need to try and get back to stock due to a warranty issue so I was following this guide here: http://forum.xda-developers.com/showthread.php?t=1460713
It seemed to be going well and I flashed the hboot which removed the revolutionary version, the RUU I used was the only Tmobile version I could find RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed and it started running through, it updated the hboot which is now S-On version 0.98.0000 but after that point it failed with error 140.
I don't understand why this has happened though as surely the version 0.98.0000 HBoot version is what is installed by the RUU itself so how can this be the wrong version? Is there something else I'm missing here.
At this point the phone is connected by USB to my laptop still and sat in HBoot, I'm not even sure if I can safely reboot at the moment so need some advice on what to do next?
Click to expand...
Click to collapse
So your problem is solved ? I want go back to S-ON and would get some feedbacks before doing this
Okay....so I need to twiddle around with my trusty old HOX in order to solve the constant rebooting issues. (I also want to jump ship off of the memory-heavy Viper Venom that's on it to just straight CM or something similarly light weight)
To do that I've got to update the firmware.
And to do that... first I have to identify what bloody firmware I have so that I use the correct updating method and don't brick my one and only device.
I'm not a total noob... I've been working on a beginner/moderate level with Android for 3 years now... I can get around ADB (typos not withstanding) reasonably well, push commands, get to hboot, know fastboot and such... but I am just not finding the specific answers I need right this moment to get this work done. So if Someone can point me in the proper direction, I would be muchly appreciative.
Right Now my bootloader screen says the following
Tampered
Unlocked
Evita PVT Ship S-ON RLHboot 1.09.0000
Radio 0.20os.32.09.10_2
OpenDSP-v31.1.0.45.0815
eMMC-boot
Click to expand...
Click to collapse
So, who can tell me which firmware version contains Hboot1.09? Once I know that, I can start the process of SuperCID and S-OFF to make these updates. Barring that, anyone who can point me to a one-click unlock tool would be great too... the ones I find on the first few pages of the forum all recommend firmware newer than what I know is installed on here according to the above into, and I am leery to use them for risk of bricking my one and only phone.
Your current firmware is actually irrelevant, you need not worry about that at all. All you need to do is get s-off, which should be a sinch. Because you don't have SuperCID (I'm assuming from your last paragraph) you really only have one option, which is the Rumrunner method. It should work with Viper installed, if not it has a good success rate with the Kickdroid ROM.
Rumrunner S-off
Sent from my Evita
So I did have SuperCID... a readCID command demonstrated that.
and thanks to your assuaging my fears, timmaaaa, I was able to flash to 2.15 without a problem.
the problem now... is even after pushing TWRP every way I know how, I can't get into recovery, even with fastboot erase cache. ugh I feel like yanking my hair out.
but at least the phone hasn't randomly slowed down or rebooted since flashing the new firmware. (and the pesky double-reboot that made flashing it such a core in the first place is fixed too)
::edit:: gonna spend the next hour redownloading the venom ro so I can push the boot.img file, maybe that will fix things.
Did you check the md5 of the recovery download?
Sent from my Evita
timmaaa said:
Did you check the md5 of the recovery download?
Sent from my Evita
Click to expand...
Click to collapse
Yes I did. I also tried to install it via a few onboard solutions like goo.im. no go. it says it's been installed, fastboot insists the phone is unlocked and s-off; but it boots to the flash screen, tries to load recovery, fails, and reboots to the rom.
I am going to assume that the unlock is fubar somehow and start from scratch by installing 2.20 and using the HTC unlock, and go from there.
now if only damned downloads didn't take 5 hours on my slow rural connections... thank you isp conglomeracy.