Related
I have a problem and hope you can help me.
I've made my device via AlpharevX S-Off. Then I flashed a custom ROM. But I had previously made a backup of my old original ROM by CLokworkMod.
But by then I played an original RUU ROM about the CUSTOM ROM. Now appears only the HTC characters on a white background and I'm just still in the boot loader.
But I'm not even in the recovery menu.
Can you help me?
Is it possible to start S-off with AlpharevX when the phone does not start, but in the bootloader or fastboot?
Can I suggest that you Post this problem into One of the existing akpharevx threads as that way one of the original developers might assist you
Sent from my HTC Desire S using XDA Premium App
BJ.Örni said:
I have a problem and hope you can help me.
I've made my device via AlpharevX S-Off. Then I flashed a custom ROM. But I had previously made a backup of my old original ROM by CLokworkMod.
But by then I played an original RUU ROM about the CUSTOM ROM. Now appears only the HTC characters on a white background and I'm just still in the boot loader.
But I'm not even in the recovery menu.
Can you help me?
Click to expand...
Click to collapse
Did you remember to wipe before you "played" the original? If you can get into recovery, wipe everything and do a fresh flash. If you cant get into recovery you will need to RUU.
I didn't wipe before i flash the original RUU...and i can not get into recovery mode.
How can i RUU without starting the telephone?
Put your RUU on your Windows desktop. Type %temp% and run. In the files that pop up look for Rom.zip, rename it PB99IMG.zip put it in the root of your gold SD card if it needs to be a gold card, and boot your phone into hboot. When asked to update press y.
Sent from my HTC Desire S using XDA Premium App
I tried it but the mobile freezes after seleting yes. Furthermore it says "hboot can not roll back"...
ask the alpharev guys what to do. they set the hboot version very high to prevent accidental overwriting. unfortunatley they seem to forget to release a downgrate hboot so the whole thing would be reversible. until they do, you a bit in a puddle.
Or try a pre-rooted RUU. This will not try and over write Hboot.
how can i get a pre rooted ruu?
BJ.Örni said:
how can i get a pre rooted ruu?
Click to expand...
Click to collapse
Search under development thread .. shipped rom for desire s
BJ.Örni said:
how can i get a pre rooted ruu?
Click to expand...
Click to collapse
Your best bet is to look on XDA in the Dev's section. I can't look for you as it depends on you version number, carrier etc.
And how to install this ruu?
BJ.Örni said:
And how to install this ruu?
Click to expand...
Click to collapse
Put it into your sd card, mount your phone as disk drive, locate the file in your sd by computer .. then double click install it.
Make sure you got the driver, how? install htc sync for the driver.
BJ.Örni said:
And how to install this ruu?
Click to expand...
Click to collapse
PB99IMG I described earlier is the best route with your issues.
BJ.Örni said:
And how to install this ruu?
Click to expand...
Click to collapse
you can use the same procedure
Telephone freezes whil eupdating and says "can not roll back hboot"
This users explanation
Valwit said:
ask the alpharev guys what to do. they set the hboot version very high to prevent accidental overwriting. unfortunatley they seem to forget to release a downgrate hboot so the whole thing would be reversible. until they do, you a bit in a puddle.
Click to expand...
Click to collapse
Coupled with the error that you're getting :
BJ.Örni said:
Telephone freezes whil eupdating and says "can not roll back hboot"
Click to expand...
Click to collapse
Seems to sum up where you are at currently.....so do whats been advised in the posts above (perhaps post both of these latest posts into the other AlphaRevx threads) and wait for the AlpharevX team to respond. I believe that they are meant to be working on a way to reverse the AlpharevX process, so should be able to help or at least inform you of your options.
I'm not condoning multiple posting, but, as the desire S was one of the last devices to achieve success you may have more success contacting them by posting in the existing Incredible S AlphaRevX thread - which see's far more activity.
THIS IS FOR UNBRANDED 401 PHONES ONLY! IT MIGHT WORK FOR OTHERS BUT I WOULD RATHER NOT TRY...
Update 2011/08/14
Added more information and details
Renamed thread into GUIDE
Using this guide will reset your device into a vanilla 2.3.4 HTC Sensation phone. Your SD-Card wont be touched and you will have S-OFF and root. This will lock your bootloader but that should not be a problem since you are still S-OFF and can flash whatever you want - except the bootloader. I tested these steps and i have a 2.3.4 401 Sensation with Locked HBOOT, S-OFF and root.
If you want S-OFF & ROOT on the latest HTC 2.3.4 ROM follow the steps:
1) Backup
2) Get S-OFF on 2.3.3 (Guide Thread)
3) Recover your phone with original 2.3.3 Update
http://www.filefactory.com/file/cc03797/n/RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.900 7.00U_10.51.9007.27_M3_release_198179_signed.exe
4) Update to 2.3.4 via "Over The Air" (OTA) or using OpenRecovery (OR). I did not use the OR-Method but you can find a lot of information about here. I do not advertise any guides for the OR-method since i did not test them myself.
4) Execute step 2.1 to 2.6 from the Sensation Guide (Guide Thread)
5) Get root again: Sensation Guide 3.1 to 3.12 (Guide Thread)
Have fun!
dacleric said:
....
4) Update to 2.3.4 via ...... using recovery.
Have fun!
Click to expand...
Click to collapse
How? Can some please explain step by step?
Thanks
anyone have a change log? google failed me for once in my life
The 2.3.4 update include an new hboot Version 1.18...
Are u sure that u can install cwm and root the phone again after applying the update?
I think u will be s-on again after the hboot get changed...
Everything I'm reading (the two other threads about this update) says the above method will NOT work. I don't think the OP even tried. Wait for a real dev to cook this up.
dacleric said:
THIS IS FOR UNBRANDED 401 PHONES ONLY! IT MIGHT WORK FOR OTHERS BUT I WOULD RATHER NOT TRY...
Using this guide will reset your device into a vanilla 2.3.4 HTC Sensation phone. Your SD-Card wont be touched and you will have S-OFF and root.
If you want S-OFF & ROOT on the latest HTC 2.3.4 ROM follow the steps:
1) Backup
2) Get S-OFF on 2.3.3 (Guide Thread)
3) Recover your phone with original 2.3.3 Update
http://www.filefactory.com/file/cc03797/n/RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.900 7.00U_10.51.9007.27_M3_release_198179_signed.exe
4) Update to 2.3.4 via OTA or using recovery.
4) Execute step 2.1 to 2.6 from the Sensation Guide (Guide Thread)
5) Get root again: Sensation Guide 3.1 to 3.12 (Guide Thread)
Have fun!
Click to expand...
Click to collapse
All perfect....but...my HBOOT shows ***LOCKED***..... What`s that?
^^ see the thread in the general section about this.
http://forum.xda-developers.com/showthread.php?t=1214707
Around page ten or so.
And this:
http://forum.xda-developers.com/showpost.php?p=16585832&postcount=123
A little more:
http://forum.xda-developers.com/showpost.php?p=16582890&postcount=31
eloyloy said:
All perfect....but...my HBOOT shows ***LOCKED***..... What`s that?
Click to expand...
Click to collapse
Oh boy Some of use knew this was gonna happen
do not flash this to a stock rooted rom - it will **** it up - wait for your favourite dev to update their rom
flashing this will give you the new locked htc bootloader and you will not be s-off anymore (even though it still says you are)
it's taken me nearly 3 hours to get back to normal
EddyOS said:
When I say I'm S-OFF again, I mean I'm back to my old 2.3.3 ROM before I flashed the new update.
Everyone, DO NOT TRY AND FLASH THIS OVER YOUR ROOTED PHONE - WAIT FOR YOUR ROM TO BE UPDATED BY THE DEVS
Click to expand...
Click to collapse
xxxxxxxxxxx
Ledroid will tell us
Sent from my HTC Sensation Z710e using XDA Premium App
Hi all,
I've just done this update
Backup with Titanium
Reflash with 2.3.3 stock ROM (my Sensation was already S-Off)
OTA update to 2.3.4
ClockWork Recovery
Root
Restore with Titanium
Reboot and that's it
No OTA
I did exactly like shown in the first post, but i wont get the update ota. It sais that my phone is actually actual.
Could I have done something wrong?
Got the Sensation from T-mobile -> debrandet it like this:
http://forum.xda-developers.com/showthread.php?t=1193033
And used the RUU version from the first post.
Thanks
done as suggested - works fine for me!
I was off this weekend.
I posted this howto cause i did it with my phone. Whyever would i post a guide when it does not work?!
Using this guide will lock your bootloader but that should not be a problem since you are still S-OFF and can flash whatever you want - except the bootloader.
At least thats the case for me.
dacleric said:
Using this guide will lock your bootloader but that should not be a problem since you are still S-OFF and can flash whatever you want - except the bootloader.
Click to expand...
Click to collapse
Are you sure you can't flash the eng hboot too?
dazweeja said:
Are you sure you can't flash the eng hboot too?
Click to expand...
Click to collapse
no - i did not try to.
I am pretty happy with my phone right now. Fast and long battery pack - replaced Sense with LP.
When testing the early (pre-soff) custom roms and test recoverys I had to flash stock RUUs a couple of times.
To get the phone back into a decent state I needed to pg58 flash eng&unsecured boot then root and fastboot recovery.
Can't for the life of me think why anyone would s-off their phone then install stock/ota for any reason (bar repair). It's like buying a track day race car, shouting "look what I've got" then pushing it around rather than thrashing it.
dazweeja said:
Are you sure you can't flash the eng hboot too?
Click to expand...
Click to collapse
If you just flash the new hboot, it will say lock at the top of the bootloader screen. But you should be able to flash eng hboot, cause I just tried it.
Sent from my HTC Sensation Z710e using XDA App
d3vilskid said:
If you just flash the new hboot, it will say lock at the top of the bootloader screen. But you should be able to flash eng hboot, cause I just tried it.
Click to expand...
Click to collapse
Thanks. That's what I thought. I removed the hboot from the OTA before flashing it so couldn't confirm for myself. There's been a lot of conflicting information about whether phones are still S-OFF after running the unmodified OTA but it appears that they are. I only ran the RUU then OTA so I could have a backup of a stock 1.45 system.img.
dazweeja said:
Thanks. That's what I thought. I removed the hboot from the OTA before flashing it so couldn't confirm for myself. There's been a lot of conflicting information about whether phones are still S-OFF after running the unmodified OTA but it appears that they are. I only ran the RUU then OTA so I could have a backup of a stock 1.45 system.img.
Click to expand...
Click to collapse
Np, i was trying to figure out how to flash pg2fs_spcustom.img and I found out that the only way to do it was to flash the new hboot first than it would read that pg2fs img.
Sent from my HTC Sensation Z710e using XDA App
This may be old news, but i followed these directions and got bootloader unlocked... now i just need to figure out s-off
http://forum.xda-developers.com/showthread.php?t=1426179
Nice find...now you should be able to root with Mr root or revolutionary
Revolutionary says I'm not supported.... ;(
Sent from my myTouch_4G_Slide using XDA App
(I will try) and make a script that downgrades your boot loader for compaitability
xmc wildchild22 said:
Nice find...now you should be able to root with Mr root or revolutionary
Click to expand...
Click to collapse
I am going to see if mr. root can help. I haven't tried your tools yet... anything I need to know before i do?
Well mr root is highly based off revolutionary's code, just tweaked to my liking....so I I doubt it will say you compaitable.....however a try won't hurt. ..but if not ill start work on a downgrade tool
Just says my bootloader is not compatable... Downgrading would be great.... I tried flashing a recovery file to backdoor it but came back as " older than current" and stopped...
Sent from my myTouch_4G_Slide using XDA App
are you able to install cwm recovery through fastboot?
nlarge said:
Just says my bootloader is not compatable... Downgrading would be great.... I tried flashing a recovery file to backdoor it but came back as " older than current" and stopped...
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
not much helpful, but on htc g2 in a similar situation, when root was done, next step was to push some changes to the partition where the Version number was stored. After that downgrading was possible the way you tried, and after that the S-Off tool worked. But as of now, i think there's no information how to cheat the version in the partition which it contains, or even which that partition is. Or maybe someone already knows this?
Then maybe we try a dd if= command on the right partition to overwrite it?
I'm not sure how you got this to work, because nobody else with the OTA has...
However, if you've gotten it to work, you can root just by flashing a superuser image from: http://androidsu.com/superuser/
You won't have S-Off, but I'm not sure of the appeal of S-Off, to be honest. The only thing you can't do with the HTC tool is flash radio files and the like.
I only tried by placing the pdsumthin.zip on SD card and it wouldn't allow it...
Theoretically an unlocked bootloader should allow that... Even if s-on
nlarge said:
I only tried by placing the pdsumthin.zip on SD card and it wouldn't allow it...
Theoretically an unlocked bootloader should allow that... Even if s-on
Click to expand...
Click to collapse
Your bootloader is still locked.
EDIT: in the unlikely event it is unlocked, you'll need to flash a custom recovery before flashing root. There's a guide somewhere on xda that explains all this.
Bootlader even says unlocked at the top... So I am free there...
nlarge said:
Bootlader even says unlocked at the top... So I am free there...
Click to expand...
Click to collapse
You found nothing. We've known about this for a while now and is "officially" (HTC) sanctioned, hence it being THEIR WEBSITE AND INSTRUCTIONS.
Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done (don't ask how, the instructions on doing this are EVERYWHERE, including google's dev site -- you can figure it out yourself with google....), you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
There is NO NEED for any kind of downgrade.
Edit: And do change your avatar... this is a hacker site, not a sex dating site. Nobody here is interested in seeing that.
Well... No one has been able to unlock it as of when I posted... It was failing... I will try flashing with fastboot... As long as I can use titanium afterwards, s-off isn't that important
Why is the 4gs community so on edge? No one was ever this rude with 4G or any other HTC forum
nlarge said:
Well... No one has been able to unlock it as of when I posted... It was failing... I will try flashing with fastboot... As long as I can use titanium afterwards, s-off isn't that important
Click to expand...
Click to collapse
I don't believe that's correct. I believe the issue is that the official HTC Bootloader Unlock process will not work -- and here's the key factor -- on devices that have already used the Revolution S-OFF procedure. I'm absolutely certain that people before you (who had not used Revolutionary) have successfully unlocked their bootloader via HTC's walkthrough.
nlarge said:
Why is the 4gs community so on edge? No one was ever this rude with 4G or any other HTC forum
Click to expand...
Click to collapse
Maybe it's because...
You created two threads that have nothing to do with doubleshot development
You didn't even check the General forum to see if there was an active thread about this (there is)
You can't even follow the rooting instructions posted in a thread on this very subject
As dhkr234 points out, all you need to do is flash the recovery zip and then flash the superuser zip. Just please try that. And then change your avatar.
HebrewToYou: I don't believe that's correct. I believe the issue is that the official HTC Bootloader Unlock process will not work -- and here's the key factor -- on devices that have already used the Revolution S-OFF procedure.[
I have been reading that it just kept hanging for everyone even with s-on... that is why I posted that I unlocked... I dont believe flashing recovery will work(yes i know how and tried zip method first).
What is the problem with my avatar? In the year that I have been on the MT4G thread no one has ever once complained about it... why you?
I'm not trying to be rude, I really just want to know why after all this time is it a problem?
ok, unlocked, SU and clockwork recovery all on board.. just stuck at S-on... directories are still read only, and I really would like to be able to use titanium!! but I am closer!!
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 there guys,
Been trying to root my XL from Telstra (AUS) but some weird things are going on.
Can't figure out why i'm unable to to SuperCid my phone, my current Supercid is TELST001
http://forum.xda-developers.com/showthread.php?t=1952038
Also, tried to root my phone using this thread below:
http://forum.xda-developers.com/showthread.php?t=1859478
So far, I have achieved to Installed S-OFF and CWM.
What i'm trying to do here is to use any 4.22 Android Rom with sense 5, like CleanROM or CyanogenMod 10
Im uploading some of the current photos taken so you guys can have more information on S-OFF and CWM.
Thanks in advance.
Ps: One of the pictures was a Failed OTA from Telstra, is there a way to go back to and be able to install the OTA from Telstra instead of any custom ROM (In case we cant find what is causing the phone to block the supercid and the super SU)
Ota won't work with a custom recovery.
I am running MagioR4 sense 5 4.2.2 you can install that now without doing anything else to your phone. There are a few others as well, but this is only one I've been running so I can't say much about others, but assume they will work out just as well.
Sent from my HTC One XL using xda app-developers app
31ken31 said:
Ota won't work with a custom recovery.
I am running MagioR4 sense 5 4.2.2 you can install that now without doing anything else to your phone. There are a few others as well, but this is only one I've been running so I can't say much about others, but assume they will work out just as well.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Hi there mate,
Tried to run Super Su and shows as the phone been not rooted, i'm a bit confused atm.
Is there a need to Super Cid and if i were to use the OTA, can i remove the custom recovery?
Desertum said:
Can't figure out why i'm unable to to SuperCid my phone, my current Supercid is TELST001
Click to expand...
Click to collapse
That's the carrier ID (CID) not SuperCID. SuperCID is 11111111 or 22222222. I think you know that, but let's get the terms right to avoid confusion.
You don't have S-off. It says right in your screenshot that the phone is still s-on.
But you it says UNLOCKED, so your bootloader is unlocked. All S-on means is that you can still install custom ROMs, you just have to flash boot.img seperately from fastboot.
As mentioned, you have to return to stock recovery in order to be able to install OTAs. Easiest way is to RUU back to stock. But be completely sure you are not SuperCID, otherwise S-on + SuperCID + Jellybean RUU = BRICK.
Personally, going stock just to install the stock 4.2.2 ROM is a step backward, not forward, as you already have an unlocked bootloader and cutom recovery. But you also seem confused about a number of things. I would suggest reading and more fully understanding the concepts and processes before proceeding with any further mods to the phone.
---------- Post added at 09:17 AM ---------- Previous post was at 09:12 AM ----------
Desertum said:
Hi there mate,
Tried to run Super Su and shows as the phone been not rooted, i'm a bit confused atm.
Is there a need to Super Cid and if i were to use the OTA, can i remove the custom recovery?
Click to expand...
Click to collapse
Unlocking the bootloader does't root the phone. You can flash an SU package in recovery to obtain root, or flash a rooted ROM.
You don't need SuperCID for anything but s-off.
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
Desertum said:
What i'm trying to do here is to use any 4.22 Android Rom with sense 5, like CleanROM or CyanogenMod 10
Click to expand...
Click to collapse
CleanROM is neither 4.2.2 nor Sense 5. CM10 is an AOSP ROM, so by definition not a Sense ROM at all.
redpoint73 said:
That's the carrier ID (CID) not SuperCID. SuperCID is 11111111 or 22222222. I think you know that, but let's get the terms right to avoid confusion.
You don't have S-off. It says right in your screenshot that the phone is still s-on.
But you it says UNLOCKED, so your bootloader is unlocked. All S-on means is that you can still install custom ROMs, you just have to flash boot.img seperately from fastboot.
As mentioned, you have to return to stock recovery in order to be able to install OTAs. Easiest way is to RUU back to stock. But be completely sure you are not SuperCID, otherwise S-on + SuperCID + Jellybean RUU = BRICK.
Personally, going stock just to install the stock 4.2.2 ROM is a step backward, not forward, as you already have an unlocked bootloader and cutom recovery. But you also seem confused about a number of things. I would suggest reading and more fully understanding the concepts and processes before proceeding with any further mods to the phone.
---------- Post added at 09:17 AM ---------- Previous post was at 09:12 AM ----------
Unlocking the bootloader does't root the phone. You can flash an SU package in recovery to obtain root, or flash a rooted ROM.
You don't need SuperCID for anything but s-off.
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
CleanROM is neither 4.2.2 nor Sense 5. CM10 is an AOSP ROM, so by definition not a Sense ROM at all.
Click to expand...
Click to collapse
Hello there,
Thanks for making things clear, for the time being i need to load the boot.img from fastboot and after that I can install a custom rom like this one?
http://forum.xda-developers.com/showthread.php?p=44053927
I remember that you need to copy the IMG file to the sd card but the Htc one xl has not got a Sd card at all, What can i do?
Thanks
Desertum said:
Hello there,
Thanks for making things clear, for the time being i need to load the boot.img from fastboot and after that I can install a custom rom like this one?
http://forum.xda-developers.com/showthread.php?p=44053927
I remember that you need to copy the IMG file to the sd card but the Htc one xl has not got a Sd card at all, What can i do?
Thanks
Click to expand...
Click to collapse
No you've got it backwards. The boot.img goes in your fastboot folder on your pc, not on your phone.
You need to fastboot flash the boot.img from each ROM you want to flash. So, if you want to install CM10.2, you must extract the boot.img from the ROM zip and put it in your fastboot folder on your pc (not your sd card in your phone). Then you put the ROM zip on your phone, and install it in recovery (after wiping cache/dalvik cache/factory reset/system), then reboot to bootloader and flash the boot.img using fastboot. You must follow this process for each new ROM you want to flash.
Do a backup of your current setup in recovery before flashing anything new though.
Sent from my Evita
---------- Post added at 11:42 PM ---------- Previous post was at 11:40 PM ----------
By the way, even though our phone doesn't have a physical sd slot, we refer to the stage as the sd card.
Sent from my Evita
Desertum said:
Hello there,
Thanks for making things clear, for the time being i need to load the boot.img from fastboot and after that I can install a custom rom like this one?
http://forum.xda-developers.com/showthread.php?p=44053927
Click to expand...
Click to collapse
It would be highly beneficial for you to read the top post of any ROM thread you want to install, as the dev usually has some important info. In the ROM you linked, it clearly says:
Installation Instructions (These are all required)
1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU.
Also, at a minimum, I will read the last few pages (most recent) of the ROM thread, just to see if there are any prominent bugs or, issues or useful tips being discussed.
Desertum said:
Hello there,
I remember that you need to copy the IMG file to the sd card but the Htc one xl has not got a Sd card at all, What can i do?
Click to expand...
Click to collapse
I think you are misunderstanding what I mean when I say "flash the boot.img using fastboot". You need to extract the boot.img from the ROM you want to flash (boot.img us often specific to the ROM). With boot.img on your computer, flash it to the phone using fastboot.
There are ways to flash boot.img without a computer. But since you specifically mentioned fastboot, the file does not go on your SD card in this case.
But again, this is not particularly applicable to CM10.2, since the dev is specifically recommending to have s-off before flashing. S-off means you do not have to flash boot.img seperately (it happens automatically when you flash the ROM in recovery).
Also, the phone does have an SD, its just not removable. Think of it as a virtual SD card.
redpoint73 said:
It would be highly beneficial for you to read the top post of any ROM thread you want to install, as the dev usually has some important info. In the ROM you linked, it clearly says:
Installation Instructions (These are all required)
1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU.
Also, at a minimum, I will read the last few pages (most recent) of the ROM thread, just to see if there are any prominent bugs or, issues or useful tips being discussed.
I think you are misunderstanding what I mean when I say "flash the boot.img using fastboot". You need to extract the boot.img from the ROM you want to flash (boot.img us often specific to the ROM). With boot.img on your computer, flash it to the phone using fastboot.
There are ways to flash boot.img without a computer. But since you specifically mentioned fastboot, the file does not go on your SD card in this case.
But again, this is not particularly applicable to CM10.2, since the dev is specifically recommending to have s-off before flashing. S-off means you do not have to flash boot.img seperately (it happens automatically when you flash the ROM in recovery).
Also, the phone does have an SD, its just not removable. Think of it as a virtual SD card.
Click to expand...
Click to collapse
Hi there,
Im trying to Update the RUU as per this thread:
http://forum.xda-developers.com/showthread.php?t=2382933
However, I'm getting an error called 155, which says that Im trying to install the wrong RUU
I was trying to update the RUU, then restart the phone, went into S-off, then into recovery and Wipe factory/data reset, then install the CM10.2 build
Is something missing here?
Thanks.
Which RUU are you trying to install? The 3.18 RUU suggested at the start of the thread?
My suggestion is to get s-off first, and you need to get SuperCID before you get s-off. Flash any rooted sense ROM from the development section, you need root to get SuperCID.
Sent from my Evita
---------- Post added at 12:41 AM ---------- Previous post was at 12:41 AM ----------
timmaaa said:
Which RUU are you trying to install? The 3.18 RUU suggested at the start of the thread?
My suggestion is to get s-off first, and you need to get SuperCID before you get s-off. Flash any rooted sense ROM from the development section, you need root to get SuperCID.
Also, what do you mean you "went into s-off"?
Sent from my Evita
Click to expand...
Click to collapse
Sent from my Evita
Desertum said:
Im trying to Update the RUU as per this thread:
http://forum.xda-developers.com/showthread.php?t=2382933
However, I'm getting an error called 155, which says that Im trying to install the wrong RUU
Click to expand...
Click to collapse
Its saying wrong RUU, because its the wrong RUU.
If you are S-on, you can only run an RUU meant for your Telstra version.
It appears you ignored my previous advice to read up on the basic concepts and procedures, before continuing to try to mod the phone.
redpoint73 said:
It would be highly beneficial for you to read the top post of any ROM thread you want to install, as the dev usually has some important info. In the ROM you linked, it clearly says:
Installation Instructions (These are all required)
1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU.
Also, at a minimum, I will read the last few pages (most recent) of the ROM thread, just to see if there are any prominent bugs or, issues or useful tips being discussed.
I think you are misunderstanding what I mean when I say "flash the boot.img using fastboot". You need to extract the boot.img from the ROM you want to flash (boot.img us often specific to the ROM). With boot.img on your computer, flash it to the phone using fastboot.
There are ways to flash boot.img without a computer. But since you specifically mentioned fastboot, the file does not go on your SD card in this case.
But again, this is not particularly applicable to CM10.2, since the dev is specifically recommending to have s-off before flashing. S-off means you do not have to flash boot.img seperately (it happens automatically when you flash the ROM in recovery).
Also, the phone does have an SD, its just not removable. Think of it as a virtual SD card.
Click to expand...
Click to collapse
timmaaa said:
Which RUU are you trying to install? The 3.18 RUU suggested at the start of the thread?
My suggestion is to get s-off first, and you need to get SuperCID before you get s-off. Flash any rooted sense ROM from the development section, you need root to get SuperCID.
Sent from my Evita
---------- Post added at 12:41 AM ---------- Previous post was at 12:41 AM ----------
Sent from my Evita
Click to expand...
Click to collapse
Hi there, I'm getting confused of what you are saying, Thought that I have already S-OFF and as previous comments, I don't need to touch SuperSid, as per the Root, I believed it was already rooted.
And yes, I'm trying to install the 3.18 RUU, currently using 3.17.
Thanks.
Desertum said:
Hi there, I'm getting confused of what you are saying, Thought that I have already S-OFF and as previous comments, I don't need to touch SuperSid, as per the Root, I believed it was already rooted.
Click to expand...
Click to collapse
I think this is a lost cause. You aren't even reading what people have replied to you. I clearly stated in post #4 above, you DO NOT have s-off.
Right in your second screen shot (white bootloader screen) it says S-ON (third line of text). This means you DO NOT HAVE S-OFF.
Desertum said:
Hi there, I'm getting confused of what you are saying, Thought that I have already S-OFF and as previous comments, I don't need to touch SuperSid, as per the Root, I believed it was already rooted.
And yes, I'm trying to install the 3.18 RUU, currently using 3.17.
Thanks.
Click to expand...
Click to collapse
Like Redpoint just said, you can't install an RUU from another carrier (the 3.18 RUU is at&t) while you're s-on. You don't have s-off, look at the screenshots you attached earlier, in your bootloader it says s-on. You have an unlocked bootloader which is an entirely different thing.
Unless you've flashed a superuser zip or flashed a rooted ROM you don't have root. Root just means that you have administrative access to system files in a ROM. The real thing you need to install custom ROMs is an unlocked bootloader and a custom recovery.
I'm gonna be honest, you're in over your head and you're ignoring good advice which was given to prevent you from damaging your phone.
You really have two choices: either do a hell of a lot of reading until you have a firm understanding of what you're doing, or leave your phone alone. The way you're going right now you're on track to destroy your phone.
Do yourself a favour and click on the link in my signature. It's a resource thread, it contains all the information you'll ever need. I'll put it this way, I read for a week or two before I even started modifying my phones.
Sent from my Evita
John uallowt
redpoint73 said:
Its saying wrong RUU, because its the wrong RUU.
If you are S-on, you can only run an RUU meant for your Telstra version.
It appears you ignored my previous advice to read up on the basic concepts and procedures, before continuing to try to mod the phone.
Click to expand...
Click to collapse
I have not ignored your advised, It rather hard to understand all this, since there is no Indication for the right RUU, since the thread i'm looking at, does not mention anything in regards of using a different RUU.
I apologise If you feel like i'm ignoring your advised, I would rather ask you now, What should I do?
Are you able to do some prompts in regards of what to do?
So far, IMAO I need to to this:
Flash the Correct RUU (Gotta find it first)
Use S-off to Install the Custom ROM (ROM is already copied to the phone's memory)
Install the new Custom ROM, however, not to sure about the GApps, which are google apps.
http://www.reddit.com/r/Android/comments/1kbeoh/gapps_20130813_for_android_43_and_20130812_for/
I guess that you need to copy them before you install the new ROM?
Thank you for your patience.
redpoint73 said:
I think this is a lost cause. You aren't even reading what people have replied to you. I clearly stated in post #4 above, you DO NOT have s-off.
Right in your second screen shot (white bootloader screen) it says S-ON (third line of text). This means you DO NOT HAVE S-OFF.
Click to expand...
Click to collapse
Fair enough, I need to read more about it.
As i Have atm S-ON and I need to have S-off to be able to install the RUU and the custom Rom, I either need to accomplish this :
SuperUser the Phone with the current Stock ROM
or
Install a Rooted ROM, correct?
Desertum said:
I have not ignored your advised, It rather hard to understand all this, since there is no Indication for the right RUU, since the thread i'm looking at, does not mention anything in regards of using a different RUU.
I apologise If you feel like i'm ignoring your advised, I would rather ask you now, What should I do?
Click to expand...
Click to collapse
As you've been told at least 3 times now, what you should do is READ READ READ.
None of this is hard to understand once you start diving into it and learning.
I'm personally not going to spoonfeed you any more steps (and suggest against doing it either), as shortcutting the learning process is only going to turn your phone into an expensive paperweight.
timmaaa said:
Like Redpoint just said, you can't install an RUU from another carrier (the 3.18 RUU is at&t) while you're s-on. You don't have s-off, look at the screenshots you attached earlier, in your bootloader it says s-on. You have an unlocked bootloader which is an entirely different thing.
Unless you've flashed a superuser zip or flashed a rooted ROM you don't have root. Root just means that you have administrative access to system files in a ROM. The real thing you need to install custom ROMs is an unlocked bootloader and a custom recovery.
I'm gonna be honest, you're in over your head and you're ignoring good advice which was given to prevent you from damaging your phone.
You really have two choices: either do a hell of a lot of reading until you have a firm understanding of what you're doing, or leave your phone alone. The way you're going right now you're on track to destroy your phone.
Do yourself a favour and click on the link in my signature. It's a resource thread, it contains all the information you'll ever need. I'll put it this way, I read for a week or two before I even started modifying my phones.
Sent from my Evita
Click to expand...
Click to collapse
Thank you, If you put it that way then it makes more clear, stay away from your phone before you bricked it!
Will read about you've said before,however I have tried several ways to Super SU this phone and nothing works.
http://ausdroid.net/2012/05/21/how-to-root-the-htc-one-xl-generic-telstra/
Tried the one above, and no good.
Thanks for the help, will leave it as it is until I feel more confident about how to get this thing going.
Desertum said:
Fair enough, I need to read more about it.
As i Have atm S-ON and I need to have S-off to be able to install the RUU and the custom Rom, I either need to accomplish this :
SuperUser the Phone with the current Stock ROM
or
Install a Rooted ROM, correct?
Click to expand...
Click to collapse
We're getting there, here are the exact steps you need to take:
1) Read a lot.
2) Read some more.
3) Flash a superuser zip on your current stock ROM, or flash a rooted Sense ROM so you have root.
4) Get SuperCID.
5) Get s-off.
6) RUU to latest.
7) Flash whatever ROM you want.
Sent from my Evita
---------- Post added at 01:18 AM ---------- Previous post was at 01:16 AM ----------
Desertum said:
Thank you, If you put it that way then it makes more clear, stay away from your phone before you bricked it!
Will read about you've said before,however I have tried several ways to Super SU this phone and nothing works.
http://ausdroid.net/2012/05/21/how-to-root-the-htc-one-xl-generic-telstra/
Tried the one above, and no good.
Thanks for the help, will leave it as it is until I feel more confident about how to get this thing going.
Click to expand...
Click to collapse
Just go to our Android Development section here and flash one of the new Sense 5 ROMs. They're already rooted.
Don't get information/software from anywhere except XDA by the way.
Sent from my Evita
He is already on 2.14 hboot I'm not even sure why he's trying to ruu.
Sent from my HTC One XL using xda app-developers app
31ken31 said:
He is already on 2.14 hboot I'm not even sure why he's trying to ruu.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Good catch. I missed that.
To the OP: you don't need to RUU to install cm10.2 on your device as you already have the required hboot/firmware. Without s-off you will need to manually flash the boot.img using fastboot though.
Sent from my Evita