What am I able to do with those in terms of roms and kernels?
doesn't matter for ROMs, but kernels and radios can't be flashed through recovery on that hboot.
Cid just means you're rooted. Your hboot means you can flash kernels and ROMs with an extra step. You'll have to fastboot flash the boot.img then install the .zip from twrp.
To save you from doing that, you can downgrade your hboot and then RUU downgrade to 1.85 so you can flash a radio. Go to the eMMC JET tool in the android dev forum if you want to downgrade your hboot.
Sent from my One X using xda app-developers app
Myrder said:
Cid just means you're rooted. Your hboot means you can flash kernels and ROMs with an extra step. You'll have to fastboot flash the boot.img then install the .zip from twrp.
Click to expand...
Click to collapse
I've had a good amount of luck with Aroma installers taking care of the boot.img flashing for me. Between CleanRom and BeastKernel, I only had to flash the zips from twrp.
Instead of creating a new thread, I thought I'd just bump this one.
Anyway, just bought a used AT&T HTC One XL and it has CID: 11111111 and S-ON. I need to update my HBOOT so I can run CM10. I just want to know what exact firmware/HBOOT to use so I can use the phone.
Thanks in advance!
The easiest thing to do would be to s-off. Then you can flash whatever you want.
Sent from my HTC One X using xda premium
You shouldn't need to update your hboot to run cm10 but I'd be lying if I said I hadn't encountered people with phones that wouldn't boot cm10 unless they updated to the 2.14 HBOOT.
Bear in mind on the 1.14 hboot, you need to extract the boot.img from the rom and flash it using fastboot before most roms will boot. If it still doesn't boot or you don't like the idea of flashing boot.img separately every time you flash a rom then yes I would agree to S-OFF and use the 3.18 ruu.
Sent from my One X using xda app-developers app
ratsack said:
Instead of creating a new thread, I thought I'd just bump this one.
Anyway, just bought a used AT&T HTC One XL and it has CID: 11111111 and S-ON. I need to update my HBOOT so I can run CM10. I just want to know what exact firmware/HBOOT to use so I can use the phone.
Thanks in advance!
Click to expand...
Click to collapse
Thank you for not creating a new thread. Let everyone else said, it would be wise to do s off while you are this far.
Sent from my Carbon-ize Evita using xda-developers app
I think it is my old HBoot as it's doing the same thing my wife's HTC One X did the other day when I tried to put CM10 on it. Updating HBoot fixed that.
I can't boot into Android as it isn't working. Is there a way to S-Off (that's easy) where I don't need to boot into Android? All I really want is to update HBoot and I'll be happy.
---------- Post added at 01:44 AM ---------- Previous post was at 12:48 AM ----------
Well, I think the issue was I that I wasn't using the correct recovery to flash the CM10 & GApps. Was using the recovery for a One X, not XL. Put the correct recovery on and now I'm typing this message on my phone. Yay!
Thanks for the help peoples! Now to find out how to remove the red text on start-up!
Sent from my One X using Tapatalk 2
Related
Recently I rooted a friends One S just curious before I start flashing if I go from a sense rom to cyanogenmod or vice versa, Will I have to do anything with Hboot or can I switch between roms without any issues?
You can switch between roms , regardless of your Hboot. If you're on a higher Hboot after 1.09 I think then you have to fasboot flash the boot.IMG or use flash image GUI, even if you're restoring to a previous ROM. Doesn't matter if its cyanogenmod or a stock sense ROM. If you don't want to flash the boot.IMG then you can S-OFF http://forum.xda-developers.com/showthread.php?t=2155135
Sent from my Nexus 4 using xda app-developers app
Thanks, thats what I needed to know.
I got a question regarding this topic:
My brother's One S is still on HBoot 1.09 and currently running an ICS ROM.
If he want to install a JB ROM, does he need to change his HBoot or anything else?
Because with my One X, I had to upgrade HBoot to be able to install newer ROMs.
Yes, Hboot update is required to install JB
Sent from my HTC One X using xda app-developers app
zakvoline said:
Yes, Hboot update is required to install JB
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thank you, is there an easier way than going back to stock and updating via OTA?
don't get hboot's and boot images mixed up
you can flash jb or ics or whatever on .09 and most likely will not have to flash boot images separate. that usually occurs on .13 or higher
i have .06 and flash everything including radios
obviously can't change hboots without s-oo
I've been running AOSP ROM's on my evita for a while now, but apparently with the 3.4 kernel you now need hboot 2.14 or higher and mine's at 1.09. My phone was unlocked with S-ON, but I did "fastboot oem lock" this morning because I read that it's necessary for an RUU. I downloaded the 2.20 RUU and tried to run the installer but I always get an Error [170] USB Connection Error. I have the HTC and adb drivers installed successfully and have tried to run the RUU as admin in both Sense and fastboot (bootloader). I'm a bit stumped and would really like to get AOSP back on my phone.
You need to S-off first.
Sent from my HTC One X using xda premium
tlazarus said:
You need to S-off first.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Should I use facepalm for that then?
EDIT
I got s-off, but still no go. Still the error 170.
I know on my old Incredible I was able to rename the rom.zip from the RUU as PB99IMG.zip and put it on the root of my sdcard. Then in hboot it would detect it and ask to flash it. This isn't happening on my evita though. Is there a way to do that, or is that only for older htc devices?
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Venomtester said:
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Where can I find this error log? It did see my device, I did that command (which ended at the black htc screen) and I ran the RUU again but I still get the error 170. I'm also using this RUU http://bugsylawson.com/index.php/fi...320911-2-101053225l-release-271865-signedexe/
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Venomtester said:
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It is that size, though I may try the link you gave.
EDIT
Okay, I think I found out what I've been doing wrong. I found this link http://forum.xda-developers.com/showthread.php?t=2119610 and it turns out that the file I've been trying does NOT include the 2.14 hboot that I need. The one I need is the latest JB release, but someone said that if you flash it with superCID and S-ON that it will brick your device. I have superCID but S-OFF, does anyone think that will brick my device? Should I flash the RUU with the 1.09 hboot (which I'm running) first, and then flash the newest RUU? Also, it looks like the link I provided offers flashable OTA's of each update. Would those work/be recommended for TWRP?
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Venomtester said:
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
dshoe said:
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
Click to expand...
Click to collapse
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
31ken31 said:
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
dshoe said:
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
Click to expand...
Click to collapse
Just make sure you are s-off before running ruu or risk a brick..
Sent from my HTC One XL using xda premium
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
For what it's worth, I was on stock 2.20, got s-off and unlocked bootloader with superCID, and ran the 3.18 RUU with no problems. I didn't need to relock or anything.
knanda said:
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
Click to expand...
Click to collapse
You can go ahead and run the RUU. No real risk because you're s-off. Maybe make a backup though.
Sent from my Evita
I am looking for a Stock T-Mobile Jelly Bean image that won't brick my phone. I tried searching for one, but I couldn't find anything or I found RUUs for outdated versions of HBoot. I am trying to revert back to stock, but I am sorta scared to do so with an outdated RUU. I have HBoot version 2.15 and Radio version 1.13.50.05.31. Thanks in advance.
Would this be the RUU I have to download? http://bugsylawson.com/files/file/1...531-10305008l-release-309489-signed-ics-2exe/
I would just prefer a nandroid backup of the stock image that I can just flash with CWM.
I downloaded the RUU, I just need to know if that is the correct one for my phone before I use it. I really don't want a bricked phone. I checked the MD5sum already and it matches, that is the only thing holding me back.
Sent from my One S using xda premium
I have ran that RUU with the same hboot and radio as you. Why do you think it would brick your phone? you haven't supercid and have locked your bootloader right?
(didn't download from that site though)
http://forum.xda-developers.com/showthread.php?t=2094414
Okay, thank you for the reassurance. I just am pretty paranoid about bricking my phone. I have been looking up how to use RUUs for the last day or so, I just couldn't find anything on how to select the right one. Thanks again.
I just checked out your link and I am downloading now. I do not have SuperCID and I will be looking my boot loader.
Sent from my One S using xda premium
OccupyDemonoid said:
Okay, thank you for the reassurance. I just am pretty paranoid about bricking my phone. I have been looking up how to use RUUs for the last day or so, I just couldn't find anything on how to select the right one. Thanks again.
I just checked out your link and I am downloading now. I do not have SuperCID and I will be looking my boot loader.
Sent from my One S using xda premium
Click to expand...
Click to collapse
If you are on TMOB US then it's for you. Furthermore, you can match thr CID of your phone to that in the RUU.exe --> Firmware.zip --> android-info.txt.
You'll have to extract firmware.zip from temporary files when you run RUU without connecting phone.
Sent from my Nexus 7 using Tapatalk HD
I ended up using that RUU that was linked earlier in this thread and everything went fine. I just don't have the stock recovery. I guess that isn't that much of a problem though.
Sent from my HTC VLE_U using xda premium
OccupyDemonoid said:
I ended up using that RUU that was linked earlier in this thread and everything went fine. I just don't have the stock recovery. I guess that isn't that much of a problem though.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
The RUU installs the Stock Recovery automatically. You don't have to do anything extra.
You can find stock recovery (if you want to keep it for any purpose) inside the RUU (extraction would require you to run the RUU and then extract the recovery from Temporary Files)
OR
you can find it in the forums.
Hmmm, that's strange. Oh well I guess. When I tried to go into the recovery it just showed a red exclamation mark with a phone under it. I don't really need a recovery right now. Thanks for letting me know where I can find it.
Sent from my HTC VLE_U using xda premium
OccupyDemonoid said:
Hmmm, that's strange. Oh well I guess. When I tried to go into the recovery it just showed a red exclamation mark with a phone under it. I don't really need a recovery right now. Thanks for letting me know where I can find it.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
I believe that is the stock recovery. The red exclamation mark is telling you that you don't have access to it. Perfectly normal.
tivofool said:
I have ran that RUU with the same hboot and radio as you. Why do you think it would brick your phone? you haven't supercid and have locked your bootloader right?
(didn't download from that site though)
http://forum.xda-developers.com/showthread.php?t=2094414
Click to expand...
Click to collapse
Can I also run this same RUU as quoted in this thread ?
I have the same radio but different hboot ...
SuperCID = HTC__001 <---- I got this right now, I will have to put in TMO CID before I run RUU, is that true?
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
I would like to go back to Stock becuase after rooting and putting custom ROM (AOKP, I lost 4g, it was working before)
DroidLuvver said:
Can I also run this same RUU as quoted in this thread ?
I have the same radio but different hboot ...
SuperCID = HTC__001 <---- I got this right now, I will have to put in TMO CID before I run RUU, is that true?
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
I would like to go back to Stock becuase after rooting and putting custom ROM (AOKP, I lost 4g, it was working before)
Click to expand...
Click to collapse
Yes, I think it will give you an error with that cid. Someone could correct me, but with s-off you can run whatever ruu you want.
tivofool said:
Yes, I think it will give you an error with that cid. Someone could correct me, but with s-off you can run whatever ruu you want.
Click to expand...
Click to collapse
I am planning on changing the CID to match what's in the firmware and then running this RUU but... what about my hboot.. it's different than what you guys have. Its 1.13
DroidLuvver said:
I am planning on changing the CID to match what's in the firmware and then running this RUU but... what about my hboot.. it's different than what you guys have. Its 1.13
Click to expand...
Click to collapse
It will install the newer hboot to 2.15
tivofool said:
It will install the newer hboot to 2.15
Click to expand...
Click to collapse
So I should be able to run the RUU with lower boot like mine and it will upgrade the boot to 2.15 -
Is it true that with 2.15 hboot, modifying the CID is not allowed ?
Any reason why I should stay with 1.13 HBOOT and not go to 2.15 Hboot? Meaning any disadvantages of upgrading to HBOOT 2.15 ?
Well, say you updated your phone via ota & your cid is European or something. And all of the ruus for that CID are lower hboots. If u are s-on and and needed to ruu you wouldn't be able to.
But there is a guide to run a ota.zip for those people, so it isn't hopeless.
So not too many disadvantages.
In fact I just installed the newest Rom and firmware today. So my hboot is 2.16.
And the gossip is that update will be officially put out by HTC in a few weeks.
Sent from my HTC One S using Tapatalk 2
Remember this.
if you want to go stock again in future (warranty purpose)
some providers have only provided an ota (only ruu with lower hboots) when upgrading to jb. So downgrading gets hard
It's not that easy to flash an ota as is a ruu.
If your s-off downgrading is no issue.
Verstuurd van mijn HTC One S met Tapatalk
Hi Guys
I am trying to get SuperCID, S-Off, then --> 3.18RUU and TWRP2.6.0.0 --> CM10.1 or 10.2
I have a phone that i Unlocked bootloader on HTCDev a long time ago. Rooted, TWRP2.6.0.0 running CM10.1 but because newer kernels require newer HBOOT so i am trying to get it.
I have TELST001 as CID
the phone in bootloader shows
****TAMPERED*****
****UNLOCKED****
EVITA PVT SHIP S-On RL
HBOOT-1.09.0000
Radio 0.20os.32.09.15
OpenDSP-V251.0.32.0405
eMMC-boot
Apr 2 2012,, 21:08:24
i have tried fastboot oem writecid 11111111 comes up with failed
I have also tried the oneclick SuperSID http://forum.xda-developers.com/showthread.php?t=1952038 - didn't work
any ideas whats the best step to take to get to the elusive cm10.2?
Thank you for your help!
You can try the hex edit method, which can be found here:
http://forum.xda-developers.com/showthread.php?t=2212737
Sent from my Evita
timmaaa said:
You can try the hex edit method, which can be found here:
http://forum.xda-developers.com/showthread.php?t=2212737
Sent from my Evita
Click to expand...
Click to collapse
This should work too:
Code:
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
Once you get Super CID, you can get S-Off using the method found here: http://forum.xda-developers.com/showthread.php?t=2155071
which worked wonderfully for me just this morning.
Then, once you've verified that you have S-Off, you can update your HBoot using this method: http://forum.xda-developers.com/showthread.php?t=2156686
I used the third zip listed, worked just fine.
If you do not have S-Off and you attempt this, the chance of bricking your phone is incredibly high.
When you get to green bar, as mentioned in the instructions, let it sit for a few seconds, and then move on to the next step without waiting for it to go away (because it won't...).
Once you're done with that, I would clear the cache using <fastboot erase cache>, flash your recovery software using <fastboot flash recovery "recovery software name here"> and then boot to that to flash your rom.
As I said, I just did this all this morning, and I'm happily running a rom that requires the updated HBoot. So best of luck!:good:
That's not entirely correct. It's not just the hboot you're meant to update. You really should run an RUU.
Sent from my Evita
Thank you all!
I have successfully superCID and S-Off then RUUed to the latest 3.18
now it says
*Unlocked*
EVITA PVT SHIP S-OFF RL
CID 11111111
HBoot 2.14.0000
Radio 0.24p.32.09.06
open DSP v34.1.0.45.1219
eMMC-Boot
Nov 26 2012 18:37:14:-1
but when i go into recovery it gives me a big exclamation mark
so presumably the TWRP is gone
So i used goomanager to install. that didn't work.
there's no root (after RUU) presumably normal
what is the best way to get TWRP on, then flash latest CM10.1
Many thanks for your help!
Download twrp and flash in fastboot.
Fastboot flash recovery recoveryfilename.img
Sent from my HTC One X using xda app-developers app
exad said:
Download twrp and flash in fastboot.
Fastboot flash recovery recoveryfilename.img
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Legendary.
Worked like a charm.
on latest CM10.1 nightly now.
Appreciate all of the above help!
Hello everyone..I would like to see if someone could help me..I have a one x with supercid, s-off, and bootloader unlocked..I want to flash a custom Rom like viper but wouldn't know where to start..would I ruu 3.18 or relock bootloader? Any help will be appreciated.
Sent from my HTC One X
xViiZe said:
Hello everyone..I would like to see if someone could help me..I have a one x with supercid, s-off, and bootloader unlocked..I want to flash a custom Rom like viper but wouldn't know where to start..would I ruu 3.18 or relock bootloader? Any help will be appreciated.
Sent from my HTC One X
Click to expand...
Click to collapse
All you need to do is flash the ROM from recovery....
Sent from my Evita
Ok so the hboot version wouldn't matter? I have ics 2.20 hboot 2.14. And viper xl is jb.
Sent from my HTC One X
No it doesn't matter.
Sent from my Evita
Alright thank you ..I appreciate it
Sent from my HTC One X
---------- Post added at 11:26 PM ---------- Previous post was at 11:08 PM ----------
ohh im sorry i was about to install the rom but then i checked my hboot version and it is 1.14 ..i read in a couple of threads that with 1.14 u need to install the boot img with the rom is this true? or would i need a hboot upgrade?
No, you're s-off so you don't need to do that.
Sent from my Evita
Ok let me try and I'll post results when I'm done
Sent from my HTC One X
So I flashed it and it did boot..thank you. So from now on if i would like to flash a different Rom, I would just got to twrp again right?
Sent from my HTC One X using xda app-developers app
xViiZe said:
So I flashed it and it did boot..thank you. So from now on if i would like to flash a different Rom, I would just got to twrp again right?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Correct
Sent from my HTC One XL using xda premium
Yeah just boot into TWRP, do a full wipe (cache/dalvik cache/system/factory reset), and flash your ROM (and gapps if it's an aosp ROM).
Sent from my Evita
Ok thank you guys..
Sent from my HTC One X using xda app-developers app
Heisenberg said:
Yeah just boot into TWRP, do a full wipe (cache/dalvik cache/system/factory reset), and flash your ROM (and gapps if it's an aosp ROM).
Click to expand...
Click to collapse
I accidentally flashed a ruu you while my phone was super CID. Now it won't boot. Is there a way that I could force my phone into fastboot? That is without having to do a j tag on it
Hi guys, I've been off from this forum for quite some time.....And I see alot of Dev along the way.....ok to the point.....I believe I have Hboot 1.09 rooted with superCID when I Did hex editing CWS__001 to 111111 (unlocked bootloader) now in order to update to newest firmware what is the best or the right way to do it? For everyone that success updated their phone without bricking it. A Guide that would be very much appreciated and link that's would be helpful for me or other user ......Thanks
Swyped from T3DRO1CS RedHoXence
What is the purpose of updating the firmware? If you just want to be on the latest Android 4.2.2 Sense 5 update you can flash one of the ROMs from our development section.
Sent from my Evita
ted77usa said:
Hi guys, I've been off from this forum for quite some time.....And I see alot of Dev along the way.....ok to the point.....I believe I have Hboot 1.09 rooted with
superCID (unlocked bootloader) now in order to update to newest firmware what is the best or the right way to do it? For everyone that success updated their phone without bricking it. A Guide that would be very much appreciated and link that's would be helpful for me or other user ......Thanks
Swyped from T3DRO1CS RedHoXence
Click to expand...
Click to collapse
Only real reason to upgrade with ruu is if you want to run certain cm10 roms. Being they require 2.14 hboot and certain firmware updates to run properly.
Sent from my HTC One XL using XDA Premium 4 mobile app
ted77usa said:
Hi guys, I've been off from this forum for quite some time.....And I see alot of Dev along the way.....ok to the point.....I believe I have Hboot 1.09 rooted with
superCID (unlocked bootloader) now in order to update to newest firmware what is the best or the right way to do it? For everyone that success updated their phone without bricking it. A Guide that would be very much appreciated and link that's would be helpful for me or other user ......Thanks
Swyped from T3DRO1CS RedHoXence
Click to expand...
Click to collapse
You just need to s-off, then run the ruu. You won't have to relock bootloader anymore before ruu anymore after you s-off, you just need to reflash recovery and flash your rom afterwards. S-off is super easy also takes only minutes.
DvineLord said:
You just need to s-off, then run the ruu. You won't have to relock bootloader anymore before ruu anymore after you s-off, you just need to reflash recovery and flash your rom afterwards. S-off is super easy also takes only minutes.
Click to expand...
Click to collapse
Any link please.....
timmaaa said:
What is the purpose of updating the firmware? If you just want to be on the latest Android 4.2.2 Sense 5 update you can flash one of the ROMs from our development section.
Sent from my Evita
Click to expand...
Click to collapse
Swyped from T3DRO1CS RedHoXence
Search for "Facepalm s-off" within our forum.
Sent from my Evita
ted77usa said:
Any link please.....
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1671237
timmaaa said:
Search for "Facepalm s-off" within our forum.
Sent from my Evita
Click to expand...
Click to collapse
redpoint73 said:
http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
So like u guys suggested.....either updated firmware to 2.15 or just flash the jb sense 5 ROM with beastmode kernel on top to overcome the signal drop and bootloop issue.
In case I'm fail.....would I be able to go back to bootloader using power + volume down? then recovery ...and restore my backup?
Swyped from T3DRO1CS RedHoXence
Yeah that's right, if you're going to update the firmware you'll need s-off first though. And yes, you can always get to the bootloader (and then recovery) issuing that button combo.
Sent from my Evita
timmaaa said:
Yeah that's right, if you're going to update the firmware you'll need s-off first though. And yes, you can always get to the bootloader (and then recovery) issuing that button combo.
Sent from my Evita
Click to expand...
Click to collapse
In order to do s-off I need supercid first right? And seem like I already have supercid when I did hex editing cws__001 to 111111 but it not show on my bootloader since I'm still S-ON right?
Is there any way to check if I'm supercid?
Swyped from T3DRO1CS RedHoXence
ted77usa said:
In case I'm fail.....would I be able to go back to recovery using power + volume down? And restore my backup?
Click to expand...
Click to collapse
That button combo gets you into bootloader. From there you can boot recovery. There is no button combo for recovery.
The 2 are related, but separate, and completely different things.
But yes, depending on what "fails" you should be able to get to recovery and restore your nandroid.
Keep in mind, that since you are S-on, you will need to flash boot.img for the ROM using fastboot, and same thing if you try to restore a nandroid. One more reason why S-off should be considered.
---------- Post added at 02:23 PM ---------- Previous post was at 02:21 PM ----------
ted77usa said:
In order to do s-off I need supercid first right? And seem like I already have supercid when I did hex editing cws__001 to 111111 but it not show on my bootloader since I'm still S-ON right?
Is there any way to check if I'm supercid?
Click to expand...
Click to collapse
I already answered that question when you posted it in another, non-related thread.
redpoint73 said:
That button combo gets you into bootloader. From there you can boot recovery. There is no button combo for recovery.
The 2 are related, but separate, and completely different things.
But yes, depending on what "fails" you should be able to get to recovery and restore your nandroid.
Keep in mind, that since you are S-on, you will need to flash boot.img for the ROM using fastboot, and same thing if you try to restore a nandroid. One more reason why S-off should be considered.
---------- Post added at 02:23 PM ---------- Previous post was at 02:21 PM ----------
I already answered that question when you posted it in another, non-related thread.
Click to expand...
Click to collapse
On nandroid backup files I saw boot.emms and recovery.emms files do do I still need to flash boot.img seperately incase in failing ? Or just restore my backup? I'm sorry that's y i reposted here and deleted the other post......
Swyped from T3DRO1CS RedHoXence
As long as you have a backup of the boot.img you can flash it via fastboot after restoring your system backup. You need to rename it to boot.img though. It's probably worth getting s-off to be honest, it only takes a few minutes and it'll save you a ton of hassle in the future.
Sent from my Evita
ted77usa said:
On nandroid backup files I saw boot.emms and recovery.emms files do do I still need to flash boot.img seperately incase in failing ?
Click to expand...
Click to collapse
You will still need to flash it with hboot.
boot.img will not flash in recovery, due to the s-on limitations.
redpoint73 said:
You will still need to flash it with hboot.
boot.img will not flash in recovery, due to the s-on limitations.
Click to expand...
Click to collapse
Just wondering why on ICS ROM I can restore my back up without flashing boot .img with S-ON?
Swyped from T3DRO1CS RedHoXence
ted77usa said:
Just wondering why on ICS ROM I can restore my back up without flashing boot .img with S-ON?
Click to expand...
Click to collapse
Because the boot.img that was still on the phone was the same (or similar enough) that it worked with the ROM that was on your nandroid.
BTW, of course I meant "flash with fastboot" not hboot.
he was on hboot 1.09 that is why he didn't need to flash boot.img separately.
DvineLord said:
he was on hboot 1.09 that is why he didn't need to flash boot.img separately.
Click to expand...
Click to collapse
That's what I thought......
Swyped from T3DRO1CS RedHoXence
DvineLord said:
he was on hboot 1.09 that is why he didn't need to flash boot.img separately.
Click to expand...
Click to collapse
Ahh, crap. Forgot that boot.img was flashable in recovery on hboot 1.09. That hboot was so long ago, and rarely pops up here anymore. And it was the hboot I was on at one time!
Forget everything I said about boot.img!
But if you ever update hboot to any version 1.14 or higher, everything I said becomes true again.
Sent from my HTC One XL using xda app-developers app
redpoint73 said:
Ahh, crap. Forgot that boot.img was flashable in recovery on hboot 1.09. That hboot was so long ago, and rarely pops up here anymore. And it was the hboot I was on at one time!
Forget everything I said about boot.img!
But if you ever update hboot to any version 1.14 or higher, everything I said becomes true again.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
So your saying is better to keep my 1.09 hboot for now like timmaa said on earlier post.....just install JB ROM sense 5 and flash beastmode kernel on top of it if I have signal drop and reboot issue......
Swyped from T3DRO1CS RedHoXence