Okay so obviously to use any of the AOSP Roms with the 3.4 kernel, you have to s-off then RUU, ect.. ect...ect...
I'm on vanilla root-box 6/11 right now and it just refuses to keep apps in memory. I don't have time to really try a new ROM or learn how to s-off and stuff ATM. I plan to sometime next week., but in the mean time, I was wondering if I flash a ROM that uses the 3.4 kernel and then immediately flash a different kernel before even booting. Would that get me past the previous requirements?
kyleallen5000 said:
Okay so obviously to use any of the AOSP Roms with the 3.4 kernel, you have to s-off then RUU, ect.. ect...ect...
I'm on vanilla root-box 6/11 right now and it just refuses to keep apps in memory. I don't have time to really try a new ROM or learn how to s-off and stuff ATM. I plan to sometime next week., but in the mean time, I was wondering if I flash a ROM that uses the 3.4 kernel and then immediately flash a different kernel before even booting. Would that get me past the previous requirements?
Click to expand...
Click to collapse
Nope, you'll probably brick doing that.
kyleallen5000 said:
Okay so obviously to use any of the AOSP Roms with the 3.4 kernel, you have to s-off then RUU, ect.. ect...ect...
I'm on vanilla root-box 6/11 right now and it just refuses to keep apps in memory. I don't have time to really try a new ROM or learn how to s-off and stuff ATM. I plan to sometime next week., but in the mean time, I was wondering if I flash a ROM that uses the 3.4 kernel and then immediately flash a different kernel before even booting. Would that get me past the previous requirements?
Click to expand...
Click to collapse
You can't flash a different kernel because those ROMs require the 3.4 kernel. There are a few lucky individuals that have been able to flash the newer 3.4 ROMs without going through the s-off & RUU process but that is definitely not the norm. You could try it but you will probably end up in a boot loop just like I did. I was already s-off so I just had to run the RUU. But even doing the whole process isn't a very time consuming ordeal. I did the whole process on a friend's phone yesterday and it took around 30 minutes and was very easy.
RollTribe said:
Nope, you'll probably brick doing that.
Click to expand...
Click to collapse
Yeah i figured it was a long shot, glad i asked first lol. Thanks dude!
pside15 said:
You can't flash a different kernel because those ROMs require the 3.4 kernel. There are a few lucky individuals that have been able to flash the newer 3.4 ROMs without going through the s-off & RUU process but that is definitely not the norm. You could try it but you will probably end up in a boot loop just like I did. I was already s-off so I just had to run the RUU. But even doing the whole process isn't a very time consuming ordeal. I did the whole process on a friend's phone yesterday and it took around 30 minutes and was very easy.
Click to expand...
Click to collapse
Oh I'm sure it's not to bad, but I have no idea how to use fastboot or adb (I've lucked by without having to use either, at least to my knowledge). Plus I don't readily have a windows PC, I just want make sure I know what I'm doing before I even attempt it. I've been looking over gunnyman's adb for noobs (http://forum.xda-developers.com/showthread.php?t=1754018), I'll give it a shot sometime next week when I've worked up the courage. Thanks for the advice!
pside15 said:
There are a few lucky individuals that have been able to flash the newer 3.4 ROMs without going through the s-off & RUU process but that is definitely not the norm.
Click to expand...
Click to collapse
3.4 kernel requires only 3.18/2.14 hboot.
If you already meet those requirements there is no need to RUU to 3.18
If you don't need to RUU to 3.18, you don't need to S-OFF.
It's really just that simple.
exad said:
3.4 kernel requires only 3.18/2.14 hboot.
If you already meet those requirements there is no need to RUU to 3.18
If you don't need to RUU to 3.18, you don't need to S-OFF.
It's really just that simple.
Click to expand...
Click to collapse
I meant there are people who have gotten it to work on an older hboot. Also, you can't just update your hboot without doing the ruu. There's something else in the update that it requires. So if you were s-off and just updated your hboot to 2.14 like I tried, the 3.4 kernel ROMs still won't flash correctly. I had an 2.14 hboot and still had to run the ruu.
Sent from my One X using Tapatalk 2
pside15 said:
I meant there are people who have gotten it to work on an older hboot. Also, you can't just update your hboot without doing the ruu. There's something else in the update that it requires. So if you were s-off and just updated your hboot to 2.14 like I tried, the 3.4 kernel ROMs still won't flash correctly. I had an 2.14 hboot and still had to run the ruu.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Yes, you require all the files in the firmware zip. It's not so much the hboot that matters hence why I put 3.18 software/2.14 hboot.
The people who managed to do it with lower hboot did the 3.18 update at some point and then downgraded just the hboot using the modded hboot file.
exad said:
Yes, you require all the files in the firmware zip. It's not so much the hboot that matters hence why I put 3.18 software/2.14 hboot.
The people who managed to do it with lower hboot did the 3.18 update at some point and then downgraded just the hboot using the modded hboot file.
Click to expand...
Click to collapse
Not trying to start an argument or anything but, I have seen and responded to users that have gotten a 3.4 kernel ROM to boot on an older hboot without ever having done the 3.18 update. It's definitely not the norm and I wouldn't even recommend trying it but there are a few people that have done it successfully.
pside15 said:
Not trying to start an argument or anything but, I have seen and responded to users that have gotten a 3.4 kernel ROM to boot on an older hboot without ever having done the 3.18 update. It's definitely not the norm and I wouldn't even recommend trying it but there are a few people that have done it successfully.
Click to expand...
Click to collapse
The ones I've seen pull that off had run the 3.18 ruu then downgraded the hboot. If it was that simple I doubt the the Rom would say it was required. And even if it was pulled of it was done by not following directions. Noobs with this phone that don't know how quirky it is can brick it. So I recommend following the steps the Rom calls for. There are more bricks from people skipping steps or not following directions
Sent from my HTC One XL using xda premium
31ken31 said:
The ones I've seen pull that off had run the 3.18 ruu then downgraded the hboot. If it was that simple I doubt the the Rom would say it was required. And even if it was pulled of it was done by not following directions. Noobs with this phone that don't know how quirky it is can brick it. So I recommend following the steps the Rom calls for. There are more bricks from people skipping steps or not following directions
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I'm not saying it's that simple and yes, I agree about following the steps. That's why I said I wouldn't even recommend trying the newer ROMs without updating first. I have seen it work though. That's all I'm saying. Maybe those users were ignorant on exactly what they did but I'm just going on what I've read and responded to.
Same ken. I have not seen anyone manage without having 3.18 at some point and I chill on here and in facepalm quite often. In fact, I don't even have a physical body. I am just a conciousness who lives within a hoxl. j/k
Pside if you say you've seen it, that's cool. But it is true that I live on these forums and find it odd that I have not encountered that situation yet.
Sent from my HTC One X using xda app-developers app
exad said:
Same ken. I have not seen anyone manage without having 3.18 at some point and I chill on here and in facepalm quite often. In fact, I don't even have a physical body. I am just a conciousness who lives within a hoxl. j/k
Pside if you say you've seen it, that's cool. But it is true that I live on these forums and find it odd that I have not encountered that situation yet.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Go to my profile and look at my quoted posts or just go back a bit in the Carbon thread. You will see where I quoted someone who was s-on and on the 1.14 hboot that flashed one of the 3.4 nightlies successfully. He was wondering if his phone was going to mess up now. That's the only specific one I remember off the top of my head but I know I've seen others as well. Like I said I'm just going by what I read. They could be completely wrong, lying, or just ignorant noobs. I live on these forums as well and have absolutely no reason to make something like this up.
Sent from my One X using Tapatalk 2
Related
I'm currently running hboot 1.14, and I've been having issues with my cell connection, and my wifi. I'm wondering if this is being caused by people not being able to flash radio's on 1.14. Is there a way to downgrade to it looks like 1.09? Is there anything wrong with using 1.14, other then not being able to flash radios, and manually having to flash boot.img? If i dont have to change it, I'd like not to, since it seem's to be kind of dicey at this point.
As always,
Thanks for the information.
If its a reception issue you should propably try to flash a new radio. Search for the jet tool to downgrade the bootloader. Flashing boot.img seperately is a hastle anyway.
Sent from my HTC One XL
ECEXCURSION said:
If its a reception issue you should propably try to flash a new radio. Search for the jet tool to downgrade the bootloader. Flashing boot.img seperately is a hastle anyway.
Sent from my HTC One XL
Click to expand...
Click to collapse
I am having reception issues, and the wifi issues, which most people don't seem to have. Does flashing the radio's do anything about the wifi on phones?
Yup, that's actually why I started flashing radios in the first place. My WiFi kept randomly disconnecting.
Sent from my HTC One XL
is the Jet tool the only way to downgrade tp 1.09 or is there another way like flashing a older Ruu that has 1.09?
If we had s off we could downgrade out hboot like you said right there by flashing a diff ruu..but we don't so only way to downgrade hboot is through jet...take your time and read instructions and there's always people willing to help in the unrbicking evita thread
a box of kittens said:
If we had s off we could downgrade out hboot like you said right there by flashing a diff ruu..but we don't so only way to downgrade hboot is through jet...take your time and read instructions and there's always people willing to help in the unrbicking evita thread
Click to expand...
Click to collapse
i was hoping i didnt have to mess with linux, im familiar with it and it can be a pain in the a$$ speacialy with drivers and libs
davidjz87 said:
i was hoping i didnt have to mess with linux, im familiar with it and it can be a pain in the a$$ speacialy with drivers and libs
Click to expand...
Click to collapse
Having done it myself, if you stick to the latest 32bit ubuntu stable release on a live USB. you'll be fine. Just read everything before starting then make sure to follow every step to the letter.
Also, avoid USB3
exad said:
Having done it myself, if you stick to the latest 32bit ubuntu stable release on a live USlibsou'll be fine. Just read everything before starting then make sure to follow every step to the letter.
Also, avoid USB3
Click to expand...
Click to collapse
Ill try doing it again this weekend .I was running 12.10 64bit I was having a hard time trying to install ia32 libs.ill try with 12.04 32bit
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!
So I am a noob to HTC phones. I understand what S-Off is but I am not entirely sure what I could with my phone with it that I can't do now. I am trying to understand whether I should go through the process since there is always the risk of bricking. Thanks!
I have no idea what S-Off is :/ i need some enlightenment
Sent from my One XL using Tapatalk
S-Off is the main thing that allows u 2 root yr phone...
Sent from my GT-I9300 using xda app-developers app
a simple search on the net can tell you what it does
but it does a lot of "techie" things you're not suppose to do
mrjayviper said:
a simple search on the net can tell you what it does
but it does a lot of "techie" things you're not suppose to do
Click to expand...
Click to collapse
I did do that. It said that I could flash ROMs, Radios, stop my bootloader from saying unlocked. Most of this things with the exception of the last I can already do. I was just wondering if there is something that I could be missing out from. Thanks!
Contrary to popular belief, s-off actually has very little to do with your phone being rooted. S-OFF stands for Security-Off, which basically allows you to modify any partition on the device, and changes will not be reset upon a reboot. Also, the signature checking of the firmware zips is disabled, allowing users to flash unsigned firmware zips containing the separate images of the partitions.
Very simply put, that's what it is. There is a lot more to it that you guys can probably look up. For a user on an hboot below 1.14 it really doesn't do all that much, but it's very useful for devs and people post-hboot 1.14
I'm not totally sure what it will do for us, but it was easy enough for me to go through with it, took about 5 minutes if you've already got ADB/Fastboot set up.
I heard it could take away that stupid red paragraph when I boot and that was all I needed to hear haha
I feel like I just got a new toy but can't read the instruction manual... can I flash a new radio? do I need to do something special like flash through fastboot?
I know I sound like a broken record but
I'd love to see someone create a dual boot program for our phone.
Sent from my HTC One XL
BobbyDukes707 said:
I feel like I just got a new toy but can't read the instruction manual... can I flash a new radio? do I need to do something special like flash through fastboot?
Click to expand...
Click to collapse
You got to wait for the new tools to be released. Nothing happens automatically AFAIK.
You can flash ROMs on newer hboot without fastboot
Sent from my One X using Tapatalk 2
so how do you get rid of the red text on boot??? and also how can the unlocked/ tampered flags be reset (while staying unlocked)
31ken31 said:
so how do you get rid of the red text on boot??? and also how can the unlocked/ tampered flags be reset (while staying unlocked)
Click to expand...
Click to collapse
Things will come, just have to give the devs a chance since we just got s-off.
SouL Shadow gave an excellent response to the question here:
http://forum.xda-developers.com/showpost.php?p=38169711&postcount=2462
But as already indicated, things will come in the future, it really doesn't gain much at the moment. Especially for those still on pre-1.14 hboot (and can already flash radios, kernels from recovery).
So this is a general word of caution that i'd like to relay to everyone.
Back in October or Nov of '12, I bought a One XL. I did not know you needed to be S-OFF after unlocking to run a RUU after installing the 3.18 OTA without bricking my phone. Lesson learned. I got a warranty replacement. I loaded the 3.18 OTA not realizing that the old exploit wouldn't work. I decide to wait until the new exploit/3.18 RUU/successful S-OFF/whatever comes out and decided to wait a few months after that for Hasoon to update his all in one kit.
That time has come and passed, and last night I decided I wanted to try it again. I read, read, and read some more, redownloaded everything, checked the md5s on everything, and started to unlock the bootloader. Ok, Easy enough, I've done this before. I flashed recovery, and successfully got S-OFF. No big deal.
Ok. So far, so good! Now, i just need to make a nandroid backup, and flash the rom, right? Not so fast... I read that people were having trouble installing ASOP based roms when on newer hboot (updated from taking the 3.18 OTA). But, this was nothing to be worried about if you already have S-OFF successfully done (which I have). I wanted to install Cleanrom or ViperXL (both sense based) so I should be good, right? All posts I found said this was the case, don't worry, no need to flash the boot.img separately.
WRONG, WRONG, WRONG, NO. NO. STOP. FAIL. You are a moron, and everything you have researched is wrong, stupid!!!!!--this is what I felt like my phone was trying to tell me.
The install took like 2 seconds, and it was stuck at the htc boot screen after a reboot. I had to RUU and start over (my nandroid got accidentally deleted because I checked the wrong box during a wipe).
It doesn't matter if you already have S-OFF, or if you don't want to even mess with AOSP roms, you have to (or at least I had to) use adb/fastboot to manually flash boot.img first, then install the rom. It took me many hours of frustration to realize I had to do this.
Now, my question is, if I do this once, do I have to do this every time I flash a new ROM? It just pisses me off how everyone in multiple threads said this wasn't necessary at all, and not to worry, when it totally meant failure for me. The point is, you can do all the reading, research, over and over, and still it might completely fail.
If you have s-off you never have to flash boot image.
Sent from my evita
If you have s-off you never have to flash boot image.
Click to expand...
Click to collapse
The whole point of my post was that, for reasons unknown to me, I couldn't successfully install a custom rom without doing. just. that.
No clue why...I spent all night trying to figure it out, but as soon as I flashed the boot image, bingo. everything worked like it was supposed to.
I'm not saying it is the case for everyone, just wanted people to know my experience.
That's really weird... That shouldn't happened. You could try ruuing again. Idk that is odd.
Sent from my evita
I'm guessing it has something to do with the fact that I started the whole process (unlock/S-OFF) with the 3.18 OTA installed. maybe since I RUUd, it will be ok.
I'm going to try another ROM tonight and see what happens. Seeing as I've never actually restored from a nandroid backup (I'm offloading them to my laptop each time), I hope it won't take too long.
I agree with leogibson.
My phone is exactly the same, even with s-off I still need to flash boot.img separately.
I can also not install radios since hboot 2.14 except via RUU or ruu mode.
My phones also did not brick with 3.17 OTA, supercid and s-on. Although personally I am not sold that any update except AT&T 3.18 does that in the first place (it probably has something to with why there is 2 packages delivered in AT&T 3.18).
I just installed another rom, I did not have to flash the boot separately this time.
new htc one xl user
Good day, i m a new htc one xl user, i was wondering if any could be of help. I need jelly bean on my xl( it is not a carrier phone). I also do not want to root my phone in the process. Is this visible??
slumbee said:
Good day, i m a new htc one xl user, i was wondering if any could be of help. I need jelly bean on my xl( it is not a carrier phone). I also do not want to root my phone in the process. Is this visible??
Click to expand...
Click to collapse
Don't hijack other peoples threads. Start your own.
Sent from my HTC One XL using Xparent Red Tapatalk 2
ImagioX1 said:
Don't hijack other peoples threads. Start your own.
Sent from my HTC One XL using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
I m sorry about that, i m stl very new here
Stuck...just displays the HTC logo on white screen.
I had cleanrom 5.0 final. TWRP, super SU, rooted, unlocked. Firmware 2.20.
I dropped in the new ROM, did a factory reset in TWRP, and installed new rom. I read that that would work with my current setup, but apparently not. I am unclear on the part where it says "Highly recommend latest Jellybean firmware and S-Off!" Not sure how to determine this or proceed. Things here seem to be getting increasingly more jargoned rather than step by step for those of us that do this once a year or so :/
I flashed back to 5.0 with no issues, but I would really like to try to get the cleanrom 7 working if possible. Any ideas?
It sounds like you're s-on, if so you'd need to flash the boot.img via fastboot. Is this the first ROM you've flashed? Please post your bootloader details.
Sent from my Evita
timmaaa said:
It sounds like you're s-on, if so you'd need to flash the boot.img via fastboot. Is this the first ROM you've flashed? Please post your bootloader details.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for your reply. You are correct, I am s-on. But I was able to re-load CleanROM 5. This is my second custom rom on this phone (the first being CleanROM 5). But this is only my third custom rom ever, so I am pretty much of a noober. :cyclops:
klaypigeon said:
I am unclear on the part where it says "Highly recommend latest Jellybean firmware and S-Off!" Not sure how to determine this or proceed. Things here seem to be getting increasingly more jargoned rather than step by step for those of us that do this once a year or so :/
Click to expand...
Click to collapse
The ROM threads are to inform you of the features and requirements of the ROM, not to be a step-by-step guide. There are plenty of step-by-step guides in various places, for those that care to read and look.
If you don't flash often, a good resource is my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
My Index will at least point you to the s-off process. I intend to add some info about the 2.15 firmware (as people keep constantly asking about it), but work has been chaotic, to say the least.
Another good thing to do, is read through the more recent pages of the ROM thread, or do a search on the thread.
Thanks, I am subscribed to your index, that's where I found the ROM and what I used during my first flash.
I did the process for unlocking the 2.20 firmware about a year ago as that is what my phone came with. I assume that would have given me superCID and s-off in order to install my old ROM (CleanROM 5).
'CID Getter' says I have no CID, which I read means I have superCID.
Firmware : 2.20
SuperSU installed and functioning (I have root)
Current ROM: CleanROM 5 Final
S-ON
TWRP 2.3.1.0
So you think I need to do s-off as described here? http://forum.xda-developers.com/showthread.php?t=2155071
If I brick this phone I am using a clam-shell for a year until contract renewal :/
klaypigeon said:
I assume that would have given me superCID and s-off in order to install my old ROM (CleanROM 5).
Click to expand...
Click to collapse
You shouldn't be assuming anything. You just said the CID Getter says S-on. You can also confirm s-on or s-off by going into bootloader.
The main reason CleanROM7 will not boot, is that you forgot to extract boot.img from the ROM file, and flash it separately using fastboot. Some older versions of CleanROM didn't require this (boot.img was flashed in the AROMA installer), so that may be why you don't remember doing this.
S-off removed the requirement to flash boot.img separately (will flash in recovery automatically when you flash the ROM). It will also allow you to install hboot 2.15 and associated firmware, if you happen to suffer from signal drops or random reboots while on Sense 5 ROMs.
Further to that, CID Getter doesn't show your actual CID. The proper way to display your CID is by using the fastboot command "fastboot oem readcid". Like Redpoint said, you shouldn't be assuming anything.
Sent from my Evita
Well...its pretty much dead. I verified supercid and then I flashed the bootloader and now it is just in a slow bootloop. It shows the HTC developer splash screen and then shuts down then a few minutes later does it again and so on. Looks like I am clamshell bound.
What did you flash?
Sent from my Evita
Muahahaaha, WORKING! Had to hold down volume through 5 reboot cycles and it finally picked up bootloader. set S-OFF. Tried CleanROM every which way and flashed boo.img as well, never could get it to make it past google boot animation. Installed ViperXL and boot.img without issue. Jelly Bean 4.2.2 sweetness! I lost hope there for about an hour, glad I didn't launch phone into the woods.
timmaaa said:
Further to that, CID Getter doesn't show your actual CID.
Click to expand...
Click to collapse
Ha, that's not a very useful app, then. What is it actually reading?
---------- Post added at 09:24 AM ---------- Previous post was at 09:21 AM ----------
klaypigeon said:
Well...its pretty much dead. I verified supercid and then I flashed the bootloader and now it is just in a slow bootloop. It shows the HTC developer splash screen and then shuts down then a few minutes later does it again and so on. Looks like I am clamshell bound.
Click to expand...
Click to collapse
Do you mean "locked the bootloader" instead of "flashed"?
If you locked the bootloader, this is what is supposed to happen. Locking the bootloader assumes you will be running RUU, and renders the phone unable to boot normally.
I know you got it back up and running. But for future reference, this phone is almost never bricked, as long as the screen comes on.
---------- Post added at 09:26 AM ---------- Previous post was at 09:24 AM ----------
klaypigeon said:
Muahahaaha, WORKING! Had to hold down volume through 5 reboot cycles and it finally picked up bootloader. set S-OFF. Tried CleanROM every which way and flashed boo.img as well, never could get it to make it past google boot animation. Installed ViperXL and boot.img without issue. Jelly Bean 4.2.2 sweetness! I lost hope there for about an hour, glad I didn't launch phone into the woods.
Click to expand...
Click to collapse
Flashing boot.img manually is not necessary with s-off, it should happan automatically when you flash a ROM. I suspect you may be having trouble with CleanROM due to a buggy or outdated TWRP version. What version of TWRP are you using?
It also seems that you are pretty unclear about some of the basic concepts around flashing ROMs on this phone. It would probably benefit you to read and learn a bit more before something bad actually happens due to negligence.
I'm not sure what CID Getter is actually reading, but when I used it it came up with the incorrect CID, can't remember exactly what it was now but it was definitely incorrect because I already had SuperCID.
Sent from my Evita
Flashing boot.img manually is not necessary with s-off, it should happan automatically when you flash a ROM. I suspect you may be having trouble with CleanROM due to a buggy or outdated TWRP version. What version of TWRP are you using?
It also seems that you are pretty unclear about some of the basic concepts around flashing ROMs on this phone. It would probably benefit you to read and learn a bit more before something bad actually happens due to negligence.
Click to expand...
Click to collapse
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do. As far as read and learning, I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
klaypigeon said:
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do. As far as read and learning, I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
Click to expand...
Click to collapse
If you have s-off you don't need to flash the boot.img via fastboot, that's only required if you're s-on. It might be worthwhile updating your TWRP to the 2.6 version though.
What Redpoint was saying is that you need to have a firm understanding of what you're doing when it comes to modifying your phone. If you only do it once a year that's cool, but that probably means that once a year you need to brush up before making any changes to your device. Rushing in without the required knowledge is how bricks occur. This is only being suggested to help you, for your own good.
Sent from my Evita
klaypigeon said:
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do.
Click to expand...
Click to collapse
Only with hboot 1.14 or later and s-on. If s-off the protection which prevents boot.img from being written in recovery is bypassed.
I believe TWRP 2.3.1 was a pretty trustworthy version (although older). So not sure why CleanROM didn't flash. Might not be a bad idea to update to 2.6.0 (although the latest 2.6.4 seems to have some bugs).
klaypigeon said:
I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
Click to expand...
Click to collapse
Yeah, I understand that you only do this on a seldom basis. And its a lot of esoteric knowledge to have to relearn (or take in, since things have likely changed since lasts time). However, that doesn't change the fact that not fully understanding all the concepts and steps can have dire consequences for your phone.