Sorry for the repeating post, I know there are many threads out there regarding this problem but I had problems after following those.
I used TWRP and installed "cos-0.7-20130427-NIGHTLY-evita", bootloader is unlocked (via HTCDev) and rooted. But my phone is still returning "ROGER001" when I search for supercid and s-on, hboot 2.14.
I followed this post (to turn s-off) "http://forum.xda-developers.com/showthread.php?t=2155071", but after step 5, I got FAILED (remote: 99 unknown fail) and for the touchscreen firmware (downgrade), I need s-off.
Can anyone help step by step or should I revert back to stock ROM? If I have no other option but reverting back, is there any thread I can follow?
Thanks in advance!
You need to downgrade your touchscreen firmware to get the 4.2.2 since your on hboot 2.14. There's a sticky at the top of the original android thread. as for getting s-off it may take a couple times, I had to changes roms from cm to viper to get mine s-off(ed)
Wubbz said:
You need to downgrade your touchscreen firmware to get the 4.2.2 since your on hboot 2.14. There's a sticky at the top of the original android thread. as for getting s-off it may take a couple times, I had to changes roms from cm to viper to get mine s-off(ed)
Click to expand...
Click to collapse
I saw that post to downgrade the touchscreen firmware, but pre-req for that is to turn s-off, can you please guide me how you did the s-off.
All I can recommend is switching to a Sense based rom if your on an AOSP based one. I was on cm10 or 10.1 when I first tried it, I got the same error 99 or 96 not sure. I tried it about 5 times on cm before switching to Viper 3.2.5 and it worked first try. other than that and fallowing the directions perfectly that's all i got. If you have any other problems I'd try the thread for s-off
Wubbz said:
All I can recommend is switching to a Sense based rom if your on an AOSP based one. I was on cm10 or 10.1 when I first tried it, I got the same error 99 or 96 not sure. I tried it about 5 times on cm before switching to Viper 3.2.5 and it worked first try. other than that and fallowing the directions perfectly that's all i got. If you have any other problems I'd try the thread for s-off
Click to expand...
Click to collapse
Any thread with all the steps?
right here
Wubbz said:
right here
Click to expand...
Click to collapse
lol, that's the thread i mentioned in my first post, I am stuck at step no 5, where I get that 99 error
jashang87 said:
lol, that's the thread i mentioned in my first post, I am stuck at step no 5, where I get that 99 error
Click to expand...
Click to collapse
Press and hold power until the phone shuts off. this will simulate a battery pull. Reboot the PC and then try again. Repeat that until you get error 92. I don't want to say it's normal that you're getting error 99 but it certainly is extremely common. It's not that you're doing anything wrong, it's just the way the exploit works.
exad said:
Press and hold power until the phone shuts off. this will simulate a battery pull. Reboot the PC and then try again. Repeat that until you get error 92. I don't want to say it's normal that you're getting error 99 but it certainly is extremely common. It's not that you're doing anything wrong, it's just the way the exploit works.
Click to expand...
Click to collapse
tried that 5-6 times, still no luck. Is it windows 8 that is causing the problem or how do I check if my phone has SuperCID or not? (it returns "ROGER001" in supercid)
Then it doesn't have supercid. It needs to be 11111111.
Sent from my HTC One X using xda app-developers app
exad said:
Then it doesn't have supercid. It needs to be 11111111.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Any help how can I do SuperCID at this moment. I have OS but no touchscreen, all that available is fastboot and recovery
My phone is unlocked, I followed the instructions on HTCDev.com and it shows unlocked at bootloader screen, but still it is returning "ROGER001"
jashang87 said:
Any help how can I do SuperCID at this moment. I have OS but no touchscreen, all that available is fastboot and recovery
My phone is unlocked, I followed the instructions on HTCDev.com and it shows unlocked at bootloader screen, but still it is returning "ROGER001"
Click to expand...
Click to collapse
From where, I can get RUU for rogers htc one x (hboot-2.14) ?
jashang87 said:
From where, I can get RUU for rogers htc one x (hboot-2.14) ?
Click to expand...
Click to collapse
you need to edit your cid in mmcblck0p4. look into hex edit mmcblck0p4. There's a couple guides floating around in Q&A and General section. I am not sure if you will be able to push the file back since 2.14 introduced write protection of system files.. There was a thread where beaups helped someone to do it in Q&A but I'm at work and can't find it for you right now. If I manage to find out before you I will post it here.
exad said:
you need to edit your cid in mmcblck0p4. look into hex edit mmcblck0p4. There's a couple guides floating around in Q&A and General section. I am not sure if you will be able to push the file back since 2.14 introduced write protection of system files.. There was a thread where beaups helped someone to do it in Q&A but I'm at work and can't find it for you right now. If I manage to find out before you I will post it here.
Click to expand...
Click to collapse
Thanks for your help, I tried that already but didn't work. I flashed my phone with ViperXL rom (with Sense) and its working fine now. I will untill the release of 4.2.2 rom which will have the firmware for touchscreen.
jashang87 said:
Thanks for your help, I tried that already but didn't work. I flashed my phone with ViperXL rom (with Sense) and its working fine now. I will untill the release of 4.2.2 rom which will have the firmware for touchscreen.
Click to expand...
Click to collapse
All you need to do is change your cid in fastboot
Sent from my HTC One X using Xparent Green Tapatalk 2
False. That only works with s-off or if you already have supercid you can change it once without s-off
Sent from my Sony Tablet S using xda app-developers app
exad said:
False. That only works with s-off or if you already have supercid you can change it once without s-off
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Well I tried everything, supercid in fastboot, changing cid manually, tried htc one x all-in-one toolkit. But nothing worked for me, still if there is something else I can try, I will try that.
Downgrade your hboot with jet tool then hex edit your cid.
Sent from my One X using xda app-developers app
Related
So after having Jellybean updated on my Telstra One XL I decided to much around with recoveries and custom ROMs to see if I could get them running. I realised that this was going to cause issues, but I was fine with mucking around with it.
I unlocked the phone and got a recovery installed and of course the touchscreen didn't work in recovery. So I mucked around with it and managed to get ROMs installed via manual boot.img flashing and manual ROM flashing via:
Code:
adb shell recovery --update_package=/sdcard/rom.zip
My test was with CM10 and it got up and running. The only issue is that touchscreen doesn't work. Which made any progression through the setup phase impossible
If anyone has any clues as to how to get this up and going again I'm all ears.
I tried to use JET to roll back the HBOOT and try to roll back the firmware, but the RUUs wanted none of it.
Thanks in advance,
Anthony
Did you also fix the version number on mmcblk0p23 before attempting an older RUU?
eg:
http://forum.xda-developers.com/showthread.php?t=1671135
twistedddx said:
Did you also fix the version number on mmcblk0p23 before attempting an older RUU?
eg:
http://forum.xda-developers.com/showthread.php?t=1671135
Click to expand...
Click to collapse
No I didn't, must've missed that. Thanks, I will try that.
Didn't work with any RUU either.
EDIT: Got the RUU installed, thank you very much. I was an idiot and forgot to relock my bootloader again
I would use twrp on the hoxl for recovery. Its not failed me yet
Sent from my HTC One XL using xda premium
Hooray first success story of a downgrade.
Was this 3.17 and down to what ruu?
DESERT.TECH said:
I would use twrp on the hoxl for recovery. Its not failed me yet
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Not really relevant.
twistedddx said:
Hooray first success story of a downgrade.
Was this 3.17 and down to what ruu?
Click to expand...
Click to collapse
RUU_Evita_UL_Telstra_WWE_1.81.841.1_R_Radio_0.17a.32.09.03_2_10.85.32.16L_release_259804_signed.exe
Not really a success though. Once it pushed through the RUU, it bricked the phone. No power LED, won't start etc.
Tried the unbricking process, but it won't work. Going to get it replaced now.
Antonioffaxii said:
Not really a success though. Once it pushed through the RUU, it bricked the phone. No power LED, won't start etc.
Click to expand...
Click to collapse
Dam!
Did you try Jet again to get back to hboot 1.09 a second time?
Does it allow you to RUU again or just nothing?
I would have tried a newer RUU also, like 2.42.
twistedddx said:
Dam!
Did you try Jet again to get back to hboot 1.09 a second time?
Does it allow you to RUU again or just nothing?
I would have tried a newer RUU also, like 2.42.
Click to expand...
Click to collapse
I couldn't restore it in anyway, I had work so I took it with me and had it replaced.
Now I have one that works again!
If you were a bit silly like me, perhaps you flashed the JB OTA on your Telus HOX before you rooted, unlocked, got SuperCID and S-Off. I didn't have much luck searching the forum for exact steps on how to get that stuff after taking the OTA. All the info is here, but I was confused what applied to my Telus phone and what would work even after the JB OTA. So I figured I'd detail my steps here in case someone else wants a detailed guide. Obviously the credit for everything below goes to the original authors of the techniques. I'm just linking stuff.
Unlock
1.Register at HTCDev and follow the directions to unlock your bootloader. Its pretty straightforward. You don't need to download the whole huge 300+ Android SDK. You can just get the adb-fastboot package from this thread.
Flash Recovery
I flashed TWRP with one-click via this AIO toolkit. There is probably tons of other ways to do it.
Root
Not sure its possible to root the stock JB unless you install a different ROM. So I did a system reset in TWRP and the flashed the Viper XL ROM. Its pre-rooted.
SuperCID
Its quite easy - just follow this guide exactly.
S-Off
Follow this guide and you shouldn't have a problem.
Once you have all that, you can downgrade your touch firmware. The reason to do this is if you want to install AOSP-based ROMs like CyanogenMod or AOKP. I haven't done that yet because I'm pretty happy with ViperXL. If you want to stick with Sense-based ROMs it isn't necessary to downgrade.
As a final note, once you've got ViperXL and S-Off I'd highly recommend trying the ElementalX Kernel.
Root
Not sure its possible to root the stock JB unless you install a different ROM. So I did a system reset in TWRP and the flashed the Viper XL ROM. Its pre-rooted.
Click to expand...
Click to collapse
You can. I was able to root my stock JB (had to install SuperSU manually) after installing the custom recovery through fastboot.
JeremyNSL said:
If you were a bit silly like me, perhaps you flashed the JB OTA on your Telus HOX before you rooted, unlocked, got SuperCID and S-Off. I didn't have much luck searching the forum for exact steps on how to get that stuff after taking the OTA. All the info is here, but I was confused what applied to my Telus phone and what would work even after the JB OTA. So I figured I'd detail my steps here in case someone else wants a detailed guide. Obviously the credit for everything below goes to the original authors of the techniques. I'm just linking stuff.
Unlock
1.Register at HTCDev and follow the directions to unlock your bootloader. Its pretty straightforward. You don't need to download the whole huge 300+ Android SDK. You can just get the adb-fastboot package from this thread.
Flash Recovery
I flashed TWRP with one-click via this AIO toolkit. There is probably tons of other ways to do it.
Root
Not sure its possible to root the stock JB unless you install a different ROM. So I did a system reset in TWRP and the flashed the Viper XL ROM. Its pre-rooted.
SuperCID
Its quite easy - just follow this guide exactly.
S-Off
Follow this guide and you shouldn't have a problem.
Once you have all that, you can downgrade your touch firmware. The reason to do this is if you want to install AOSP-based ROMs like CyanogenMod or AOKP. I haven't done that yet because I'm pretty happy with ViperXL. If you want to stick with Sense-based ROMs it isn't necessary to downgrade.
As a final note, once you've got ViperXL and S-Off I'd highly recommend trying the ElementalX Kernel.
Click to expand...
Click to collapse
does this work on ONE XL international version.i have 3.17.708.5 software version on my one xl.
rkoforever90 said:
does this work on ONE XL international version.i have 3.17.708.5 software version on my one xl.
Click to expand...
Click to collapse
It should work on any S4 dual-core One XL except on AT&T.
iElvis said:
It should work on any S4 dual-core One XL.
Click to expand...
Click to collapse
But not the ATT version because they're locked from HTCdev.
ChronoReverse said:
But not the ATT version because they're locked from HTCdev.
Click to expand...
Click to collapse
Whoops--corrected.
if i have the unlock token i can root 3.18 AT T ota?
Yup, if you managed to unlock the bootloader then you're clear to go all the way to s-off (and you should).
I have a htc one S , but this SuperCID doesn't work on my device.
Does it work after the JB OTA with the One X ?
I'm unable to use my Phone without using custom ROMs, 'cause I can't flash any RUU (CID is T-MOB101).
(I had battery problems after JB OTA-Update)
This isn't the One S forum. I'd advise asking in the appropriate forum.
Ok i can bearly find any info i'm sorry if im in the wrong place but the one x plus from [email protected] just got an ota is it still posible to root after this update? I tryed hysoon200's tool kit but the htc dev website claims my unlock key is too short i coppied it perfectly several times infact the last time i almost bricked it the screen was black for a half hour and after 2-5 mins holding the power button it booted back up can someone please point my retarted a$$ to the rite direction?
Hey, the One X+ is a totally different phone so I can' t really say what's the best direction. You are best off posting in the One X+ forum.
gothicasshole said:
Ok i can bearly find any info i'm sorry if im in the wrong place but the one x plus from [email protected] just got an ota is it still posible to root after this update? I tryed hysoon200's tool kit but the htc dev website claims my unlock key is too short i coppied it perfectly several times infact the last time i almost bricked it the screen was black for a half hour and after 2-5 mins holding the power button it booted back up can someone please point my retarted a$$ to the rite direction?
Click to expand...
Click to collapse
Yea I found this one by accident with Google but yes I am looking for a one x forum that's actually active I'm wanting to smash my head in
Have you looked here?
http://forum.xda-developers.com/forumdisplay.php?f=1814
gothicasshole said:
Yea I found this one by accident with Google but yes I am looking for a one x forum that's actually active I'm wanting to smash my head in
Click to expand...
Click to collapse
yea i'm sorry i got it lol
i wound up following the htc steps and manually made a folder and it gave me the correct token so needless to say it's unlocked flashed the su.zip made a nandroid and now i got full root thanks for your help thoe but now i'm looking at roms i keep hearing viper is the thing to have but i'm impartial to cyanogen so i'm looking for unofficial portss i wish they would crack s-off so i could do a normal flash without the dang adb lol
If I do this, will I lose my SIM unlock? I am using an unlocked Telus One X with Fido. Thanks.
You can s-off. You just need to change yiur cid to 11111111 first. Aosp roms are all in the original android development section of this forum.
I believe carrier unlock is done at the bootloader layer so it should not affect your sim unlock
Sent from my Sony Tablet S using xda app-developers app
I just unlocked the bootloader. Now I want to flash TWRP, but do I need to run the X Factor exploit in the AIO toolkit? Thanks.
Just a quick question, I did all the steps including downgrading the touch firmware (thanks for the help!), but I just have one more question. I was looking at CM 10.1 ROM and it said and update to RUU 3.18 is required. How can I check my RUU? Do I need to update? Thanks for any help.
Just checked my RUU, it's 3.17.
vuga said:
Just a quick question, I did all the steps including downgrading the touch firmware (thanks for the help!), but I just have one more question. I was looking at CM 10.1 ROM and it said and update to RUU 3.18 is required. How can I check my RUU? Do I need to update? Thanks for any help.
Just checked my RUU, it's 3.17.
Click to expand...
Click to collapse
3.17 is fine. If that cm10.1 doesn't boot, ruu again, flash recovery, downgrade touchscreen and flash it again.
Hello guys, mainly developers and their friends who might mention my case between each other.
This is a quite big problem, so maybe these few lines below deserve a second read.
From the very beginning: I bought an XE in Europe from second hand. I was about to open the bootloader by using htcdev. As a good layman I found a useless thread which's misled me: I factory reset the phone and after that I did not enable USB Debugging. On the official htc site of unlocking bootloader I chose the option from the list, titled 'Sensation EU'. Since then I've already found out this is an Asian device (cid: ASIA-HK-CHT HTC__622), so I should have chosen 'All other supported device'. In the last step by unlocking bootloader I got a question about unlocking it, or not, whereupon I asked it to do so, causing immediate freeze on the screen.
So, this smartie is bricked now - even though I can reach the bootloader(h-boot 1.29) and the recovery(stock) too - considering the following: I can't unlock it anymore by using the right 'Unlock_code.bin' file either, since it shows me the same frozen screen after choosing 'yes' (by step 12 at htcdev). Nor I can S-OFF or accomplish the RUU procedure. At the latter I can go until it's checked the P58IMG.zip file, and asking me for applying the update. When I press vol_up the brick begins updating the bootloader and never finishes. I mean I like watching that screen for hours, colorful and I'm really obsessed with the phrase 'Updating...', but I'd still like to use this sensation for calls and things. If run the execute file(RUU) on PC, while the phone is connected via 'FASTBOOT USB' it gets stuck at 'rebooting bootloader...' In fastboot I can't even erase my cache, neither in recovery.
Do you think, it'll ever be able to use for its destiny again, if I'd follow the instructions you may give me?
Thank you very much in advance.
Post your bootloader details
Sent from my HTC Sensation 4G using xda premium
adamagic said:
Hello guys, mainly developers and their friends who might mention my case between each other.
This is a quite big problem, so maybe these few lines below deserve a second read.
From the very beginning: I bought an XE in Europe from second hand. I was about to open the bootloader by using htcdev. As a good layman I found a useless thread which's misled me: I factory reset the phone and after that I did not enable USB Debugging. On the official htc site of unlocking bootloader I chose the option from the list, titled 'Sensation EU'. Since then I've already found out this is an Asian device (cid: ASIA-HK-CHT HTC__622), so I should have chosen 'All other supported device'. In the last step by unlocking bootloader I got a question about unlocking it, or not, whereupon I asked it to do so, causing immediate freeze on the screen.
So, this smartie is bricked now - even though I can reach the bootloader(h-boot 1.29) and the recovery(stock) too - considering the following: I can't unlock it anymore by using the right 'Unlock_code.bin' file either, since it shows me the same frozen screen after choosing 'yes' (by step 12 at htcdev). Nor I can S-OFF or accomplish the RUU procedure. At the latter I can go until it's checked the P58IMG.zip file, and asking me for applying the update. When I press vol_up the brick begins updating the bootloader and never finishes. I mean I like watching that screen for hours, colorful and I'm really obsessed with the phrase 'Updating...', but I'd still like to use this sensation for calls and things. If run the execute file(RUU) on PC, while the phone is connected via 'FASTBOOT USB' it gets stuck at 'rebooting bootloader...' In fastboot I can't even erase my cache, neither in recovery.
Do you think, it'll ever be able to use for its destiny again, if I'd follow the instructions you may give me?
Thank you very much in advance.
Click to expand...
Click to collapse
bootloader details please
also does the phone fully boot up anymore? i assume not have you tried to factory reset from the stock recovery, or even hboot?
anything else you should know?
ganeshp said:
Post your bootloader details
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
heavy_metal_man said:
bootloader details please
also does the phone fully boot up anymore? i assume not have you tried to factory reset from the stock recovery, or even hboot?
Click to expand...
Click to collapse
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
adamagic said:
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
Click to expand...
Click to collapse
Hi,
If you can get to bootloader,you are not bricked.
adamagic said:
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
Click to expand...
Click to collapse
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
ganeshp said:
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
do you mean this link?
http://forum.xda-developers.com/showthread.php?t=1672425
ganeshp said:
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hi,
THIS ONE?
rzr86 said:
do you mean this link?
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
Not the guide
malybru said:
Hi,
THIS ONE?
Click to expand...
Click to collapse
Yes this one
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
Not the guide
Yes this one
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Thank you guys, I really appropriate your help. The only thing is when I try to run the execute file, it stops doing anything by "rebooting bootloader"... After 20 minutes the same screen, and the guide only tells me that it takes approximately 10 minutes. When I try to flash it from bootloader, I doesn't go any further then updating bootloader.
Question: the RUU on the link you post is 3.33.707. My phone is HK and not WWE, so it's 708 and not 707. In the txt the cid version is HTC__621, mine is HTC_622. Do you think is enough if I'd just write my cid number into that? I'll givi it a go anyways, but if you have any advice...
Thank guys, you're the best.
adamagic said:
Thank you guys, I really appropriate your help. The only thing is when I try to run the execute file, it stops doing anything by "rebooting bootloader"... After 20 minutes the same screen, and the guide only tells me that it takes approximately 10 minutes. When I try to flash it from bootloader, I doesn't go any further then updating bootloader.
Question: the RUU on the link you post is 3.33.707. My phone is HK and not WWE, so it's 708 and not 707. In the txt the cid version is HTC__621, mine is HTC_622. Do you think is enough if I'd just write my cid number into that? I'll givi it a go anyways, but if you have any advice...
Thank guys, you're the best.
Click to expand...
Click to collapse
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Sent from my Nexus 7 using xda premium
still nothing
malybru said:
Hi,
Click to expand...
Click to collapse
Yeah, thanks for the link, but it doesn't work either. I've written the 'cidnum: HTC__622' (without any spaces before and after that) into the txt, but after it's checked the P58IMG.zip doesn't ask me anything, just let me be in bootloader like I'd have started the device in bootloader mode without SD.
all right
ganeshp said:
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
All right, I will try to S-OFF using your guide, but the 3rd and 4th points are not available for me. So I can only connect my phone to PC with Fastboot USB. :\ What do you think?
p.s. This is the file I could go the furthest with: RUU_PYRAMID_LE_ICS_35_S_hTC_Asia_HK_3.32.708.112_R_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_253449_signed.exe
As you see, it is still 3.32, but finally 708, but the last number from that part really makes me anxious, because it's 112, and on my phone that number is 151. I really don't want to give up, so any advice will be appropriated. (Yes, I've seen the donate me button on your profile )
adamagic said:
All right, I will try to S-OFF using your guide, but the 3rd and 4th points are not available for me. So I can only connect my phone to PC with Fastboot USB. :\ What do you think?
p.s. This is the file I could go the furthest with: RUU_PYRAMID_LE_ICS_35_S_hTC_Asia_HK_3.32.708.112_R_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_253449_signed.exe
As you see, it is still 3.32, but finally 708, but the last number from that part really makes me anxious, because it's 112, and on my phone that number is 151. I really don't want to give up, so any advice will be appropriated. (Yes, I've seen the donate me button on your profile )
Click to expand...
Click to collapse
you can try it
you don't have to lose anything at all
if it doesn't work it will just throw you an error
see how it goes
ganeshp said:
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Click to expand...
Click to collapse
rzr86 said:
you can try it
see how it goes
Click to expand...
Click to collapse
Well, I'm in command: "* daemon not running. starting it now on port 5037 *|* daemon started successfully *" and it's been nothing happening since I've started the method 10 min ago.
"Hmm we need that ruu" => which numbers must match you think in the name of the file? And where the hell to find? yahoo twice better than ggl, so I found the previous one I've showed you.
adamagic said:
Well, I'm in command: "* daemon not running. starting it now on port 5037 *|* daemon started successfully *" and it's been nothing happening since I've started the method 10 min ago.
"Hmm we need that ruu" => which numbers must match you think in the name of the file? And where the hell to find? yahoo twice better than ggl, so I found the previous one I've showed you.
Click to expand...
Click to collapse
Flash the ruu with phone connected from fastboot
Thats should work
Also if the ruu flashing stuck at some point.. There will be a log generated at C:/ruu post the log here (latest modified file)
Edit: btw Donate won't work for me. You can donate to devs on my behalf if you want
Sent from my Nexus 7 using xda premium
ohh yes
ganeshp said:
Flash the ruu with phone connected from fastboot
Thats should work
Also if the ruu flashing stuck at some point.. There will be a log generated at C:/ruu post the log here (latest modified file)
Edit: btw Donate won't work for me. You can donate to devs on my behalf if you want
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Some persian guy has uploaded the file I need, but unfortunately I can't register, because I can't answer the randon question during the registration process... Somebody?
http://www.fars-gsm.com/showthread.php?t=57177
Followed the steps in Hassoon's toolkit, installed recovery, sideloaded CM, and now I have no OS. I can still access fastboot and recovery, see attached image for more info. Any more information needed, please let me know. This is pretty frustrating, no wonder I like Nexus devices.
(sorry for double posting, I also put this in Hassoon's thread, but felt it'd be more appropriate to post here)
first man... you'll only be able to use sense roms most likely, as the newer aosp roms dont mix with the upgraded touchscreen on the 3.18 firmware. so you can head to the original dev section to find the "downgrade touchscreen" thread to use aosp...
second, you have to fastboot flash the boot.img of every rom because the newer hboots dont allow it. easy solution to that is to go to original dev section and follow the s-off thread. if you can s-off you can say bye bye to fastboot for the most part
Also, you need to S-OFF to downgrade touchscreen firmware.
But yeah, if you can get into recovery just wipe everything and flash a rom.. (has to be sense until you s-off and downgrade touchscreen firmware)
exad said:
Also, you need to S-OFF to downgrade touchscreen firmware.
But yeah, if you can get into recovery just wipe everything and flash a rom.. (has to be sense until you s-off and downgrade touchscreen firmware)
Click to expand...
Click to collapse
Never thought I had to pull the boot image out, flash that through fastboot, THEN install the OS. Thanks for the help guys, I tested it out with the copy of CM I had (unofficial port on the threads) and sure enough, it booted up fine. Of course, as stated previously, I can't click anything b/c of the upgraded touchscreen, so I'm omw to flashing a sense rom and getting s-off and a downgraded touch screen. Thanks for the help guys!
Dolfan058 said:
Never thought I had to pull the boot image out, flash that through fastboot, THEN install the OS. Thanks for the help guys, I tested it out with the copy of CM I had (unofficial port on the threads) and sure enough, it booted up fine. Of course, as stated previously, I can't click anything b/c of the upgraded touchscreen, so I'm omw to flashing a sense rom and getting s-off and a downgraded touch screen. Thanks for the help guys!
Click to expand...
Click to collapse
Yea man its a pain to get everything going. But once you s-off, downgrade etc this phone really flies on aosp. There's also an (optional) thread in development section to rid the splash screen of the red text. Its a simple 3 step process that should only take 20 seconds. After that you're golden
Sent from my One X using Tapatalk 2
InflatedTitan said:
Yea man its a pain to get everything going. But once you s-off, downgrade etc this phone really flies on aosp. There's also an (optional) thread in development section to rid the splash screen of the red text. Its a simple 3 step process that should only take 20 seconds. After that you're golden
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Dolfan058 said:
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Click to expand...
Click to collapse
are you using a sense rom or aosp?
you need to be on a sense rom since your hboot is 2.14 because aosp requires you change a setting to allow you to soff which you cant since the touchscreen doesnt work.
if you are already on a sense rom. simulate a battery pull by pressing and holding power on your phone till the capacative buttons blink a bunch of times and then it shuts off. then try again.
Dolfan058 said:
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Click to expand...
Click to collapse
I feel bad, I see all these people having trouble getting s-off to work, and I did it today without any hassles at all.
Sent from my Evita using XDA Premium
exad said:
are you using a sense rom or aosp?
you need to be on a sense rom since your hboot is 2.14 because aosp requires you change a setting to allow you to soff which you cant since the touchscreen doesnt work.
if you are already on a sense rom. simulate a battery pull by pressing and holding power on your phone till the capacative buttons blink a bunch of times and then it shuts off. then try again.
Click to expand...
Click to collapse
Definitely a sense rom (http://forum.xda-developers.com/showthread.php?t=1868236), still trying to work through it. It's so annoying, I'm dying to get the unofficial CM build on here already.
Dolfan058 said:
Definitely a sense rom (http://forum.xda-developers.com/showthread.php?t=1868236), still trying to work through it. It's so annoying, I'm dying to get the unofficial CM build on here already.
Click to expand...
Click to collapse
if a simulated battery pull isnt working for you, you can paste your cmd prompt window in here and i can check if anything weird is going on.
usually it should work by the third try or so if not after the first simulated battery pull.
I read that what the s-off does is basically buy you time so you dont have to flash the boot.img on your pc. The Maximus HD rom says you must have your s-off, but how about if I have my s-on, but flash the boot.img, will it be the same thing?
Thanks
Sent from my One S using xda app-developers app
elias.acab said:
I read that what the s-off does is basically buy you time so you dont have to flash the boot.img on your pc. The Maximus HD rom says you must have your s-off, but how about if I have my s-on, but flash the boot.img, will it be the same thing?
Thanks
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
No, the reason you need S-OFF for MaximusHD is because that ROM requires a leaked unsigned firmware, which you can only flash if you're S-OFF.
dr3amsINdigital said:
No, the reason you need S-OFF for MaximusHD is because that ROM requires a leaked unsigned firmware, which you can only flash if you're S-OFF.
Click to expand...
Click to collapse
Oh I see, thanks!
Sent from my One S using xda app-developers app
Hey, listen!
Please somebody help me. I have rooted and unlocked bootloader on my HTC One S. I want to install MaximusHD ROM on my phone, but I'm pretty sure I'm not S-off.
I have CM10.1 ROM installed on my phone.
Can somebody please tell me which guide should I follow so I can be S-off and install the desired ROM (MaximusHD)???
Also, with s-off the red letters disappear from splash screen? Thanks in advance. I really hope you can help me. I want sense 5 on my phone.
Sent from my One S using xda app-developers app
rolo143 said:
Hey, listen!
Please somebody help me. I have rooted and unlocked bootloader on my HTC One S. I want to install MaximusHD ROM on my phone, but I'm pretty sure I'm not S-off.
I have CM10.1 ROM installed on my phone.
Can somebody please tell me which guide should I follow so I can be S-off and install the desired ROM (MaximusHD)???
Also, with s-off the red letters disappear from splash screen? Thanks in advance. I really hope you can help me. I want sense 5 on my phone.
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Moonshine S-OFF: http://forum.xda-developers.com/showthread.php?t=2325590
or
Facepalm S-OFF: http://forum.xda-developers.com/showthread.php?t=2155135
Absolutely right.
And how to remove the red warning text you can find here.
Keep in mind that once you're s-off and want to return to s-on (warranty, whatever...) you'll need to reflash any stock bootloader. Else you'll definitely brick your phone. Best thing is to run any RUU before you set s-on flag on your phone then. It'll automatically restore the stock bootloader that comes with it.
S-off to install Maximus then S-on for final step. It's Ok.
I must do S-on because I get boot loops. Flashed Temporary radio 1.13 because it restarted auto.
hongha_222 said:
S-off to install Maximus then S-on for final step. It's Ok.
I must do S-on because I get boot loops. Flashed Temporary radio 1.13 because it restarted auto.
Click to expand...
Click to collapse
So it's very unstable with s-off?
I mean if I'm going to have WiFi trouble and radio and bootloops I guess is better with s-on?
Sent from my One S using xda app-developers app
rolo143 said:
So it's very unstable with s-off?
I mean if I'm going to have WiFi trouble and radio and bootloops I guess is better with s-on?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Your device must have s-off without s-off you WON'T BE ABLE TO RUN ROM.
Click to expand...
Click to collapse
Try S-off first. Do it right way.
Then if you can't do anything to get it running or get boot loops, you should try S-on.
I feel it's perfect after 2 day and nothing worry about that.. Flash Temporary-Radio-Installer-V4 if your phone auto restart.
hongha_222 said:
Try S-off first. Do it right way.
Then if you can't do anything to get it running or get boot loops, you should try S-on.
I feel it's perfect after 2 day and nothing worry about that.. Flash Temporary-Radio-Installer-V4 if your phone auto restart.
Click to expand...
Click to collapse
I highly suggest AGAINST going S-ON with Maximus.
If you S-ON, you cannot flash an RUU to lower your hboot back down to hboot 2.15. This means you will be unable to revert back to an older rom or to use the current CM roms.
S-ON while on HBOOT 2.16 is a dead-end and you're forcing yourself to be on either Maximus or another rom that is compatible with 2.16 like Magio. Until someone figures out how to S-OFF while on hboot 2.16, you're stuck with it.
If you're S-OFF, installed Maximus, and you're experiencing bootloop problems and radio problems. Please look into the rcdata partition fix that me and many other HTC One S users were experiencing. Don't S-ON until you give this a try.
tsphan said:
I highly suggest AGAINST going S-ON with Maximus.
If you S-ON, you cannot flash an RUU to lower your hboot back down to hboot 2.15. This means you will be unable to revert back to an older rom or to use the current CM roms.
S-ON while on HBOOT 2.16 is a dead-end and you're forcing yourself to be on either Maximus or another rom that is compatible with 2.16 like Magio. Until someone figures out how to S-OFF while on hboot 2.16, you're stuck with it.
If you're S-OFF, installed Maximus, and you're experiencing bootloop problems and radio problems. Please look into the rcdata partition fix that me and many other HTC One S users were experiencing. Don't S-ON until you give this a try.
Click to expand...
Click to collapse
you're right but I don't see any problem when I try the rcdata fix.
b) Type "mount" to see a list of mounts. I saw that the data block (p35) was being mounted again in /sdcard, which should be (p36). Checking /etc/fstab shows that the /sdcard was commented out!
I can do S-Off with hboot 2.16.
flashed with s-on
I am very new to Android, having been converted from iOS. I had extensive experience with jailbreaking and all that.. flashing Windows Mobile with my HTC TyTn as well.
After having my One for almost 3 months I decided to root it and explore other ROMs. Rooting wasn't an issue and I flashed MaxiumusHD 14 which was replaced within 2 weeks with version 20. Everything went well and I've got battery life that certainly exceeds, by a long shot, versus stock battery consumption rate. (Juice Defender and Profile Scheduler definitely help there too). Original stock ROM consumed a lot of power with the HTCCheckIn service. Noticed that here in Brazil I believe my battery life is worse than when I purchased the phone in Canada, I believe it's due to poor service coverage areas (weak data signals, in particular).
As I learn more, I realize that I don't believe that any of the steps I performed to root and install Clockwork involved making S-OFF active. My bootloader shows S-ON. ROM works fine and I didn't get any errors in flashing. How is that possible?
Am I missing something obvious here?
Should I do moonshine S-OFF and flash again?
I've frozen the updater using Titanium Backup (purchased that, it's great) so that I don't keep getting pestered to update to Maximus 21. I just flashed 20! (and I see no issues and nothing in the change log seems to be a huge selling point).
Thanks for the assistance with this newbie.
Matt
mattdbr said:
I am very new to Android, having been converted from iOS. I had extensive experience with jailbreaking and all that.. flashing Windows Mobile with my HTC TyTn as well.
After having my One for almost 3 months I decided to root it and explore other ROMs. Rooting wasn't an issue and I flashed MaxiumusHD 14 which was replaced within 2 weeks with version 20. Everything went well and I've got battery life that certainly exceeds, by a long shot, versus stock battery consumption rate. (Juice Defender and Profile Scheduler definitely help there too). Original stock ROM consumed a lot of power with the HTCCheckIn service. Noticed that here in Brazil I believe my battery life is worse than when I purchased the phone in Canada, I believe it's due to poor service coverage areas (weak data signals, in particular).
As I learn more, I realize that I don't believe that any of the steps I performed to root and install Clockwork involved making S-OFF active. My bootloader shows S-ON. ROM works fine and I didn't get any errors in flashing. How is that possible?
Am I missing something obvious here?
Should I do moonshine S-OFF and flash again?
I've frozen the updater using Titanium Backup (purchased that, it's great) so that I don't keep getting pestered to update to Maximus 21. I just flashed 20! (and I see no issues and nothing in the change log seems to be a huge selling point).
Thanks for the assistance with this newbie.
Matt
Click to expand...
Click to collapse
I would post this question again in the HTC One section, this is the HTC One S section. They would most likely be able to help you.
tivofool said:
I would post this question again in the HTC One section, this is the HTC One S section. They would most likely be able to help you.
Click to expand...
Click to collapse
Ok, will do. Sorry I didn't notice the S. Thanks