Related
Hi everyone.
I've been having very bad problems with by battery life lately (I mean BAD) across nearly virtually all ROMs and configurations... so I'm thinking it's time to RUU and see if it solves the problem before sending my phone off.
Currently, I'm bootloader unlocked, SuperCID, S-OFF, rooted, custom recovery, etc.
I've done an RUU before, before I got S-OFF, and I know that if you have an unlocked bootloader you have to 're-lock' it before running the RUU.
Since I'm S-OFF, are there any other prerequisites to RUUing?
Can I simply re-lock my bootloader, RUU, then unlock my bootloader, root, and I'll be good?
And will I remain S-OFF throughout the RUU? Will my S-OFF mess anything up?
Hydromea said:
Hi everyone.
I've been having very bad problems with by battery life lately (I mean BAD) across nearly virtually all ROMs and configurations... so I'm thinking it's time to RUU and see if it solves the problem before sending my phone off.
Currently, I'm bootloader unlocked, SuperCID, S-OFF, rooted, custom recovery, etc.
I've done an RUU before, before I got S-OFF, and I know that if you have an unlocked bootloader you have to 're-lock' it before running the RUU.
Since I'm S-OFF, are there any other prerequisites to RUUing?
Can I simply re-lock my bootloader, RUU, then unlock my bootloader, root, and I'll be good?
And will I remain S-OFF throughout the RUU? Will my S-OFF mess anything up?
Click to expand...
Click to collapse
From what i understand, you don't even need to relock your bootloader, while S-OFF, but I did it anyway when I RUU'd.
RUUing will not mess with S-OFF or anything.
After RUUing, I also Took the latest OTA from Telus (I'm with Telus, you may not be) And I noticed ROMs using a 3.17 base run much smoother and with less bugs. I did not, however, notice much difference in battery life with AOSP roms.
Hope this helps ya
exad said:
From what i understand, you don't even need to relock your bootloader, while S-OFF, but I did it anyway when I RUU'd.
RUUing will not mess with S-OFF or anything.
After RUUing, I also Took the latest OTA from Telus (I'm with Telus, you may not be) And I noticed ROM using a 3.17 base run much smoother and with less bugs. I did not, however, notice much difference in battery life with AOSP roms.
Hope this helps ya
Click to expand...
Click to collapse
OK, so you mean that after RUUing, you took the OTA, and Sense 3.17 ROMs ran smoother and better than before you took the OTA?
I'm thinking about using the 3.18 RUU. Since I'm S-OFF, am I safe to use any RUU I want since I can revert easily?
As in, I can safely use the 3.18 RUU (which is currently regarded unrootable), and if it turns out to be bad I can just go back to an older RUU?
Basically, will using the 3.18 OTA/RUU mess anything up if I'm S-OFF?
Hydromea said:
OK, so you mean that after RUUing, you took the OTA, and Sense 3.17 ROMs ran smoother and better than before you took the OTA?
I'm thinking about using the 3.18 RUU. Since I'm S-OFF, am I safe to use any RUU I want since I can revert easily?
As in, I can safely use the 3.18 RUU (which is currently regarded unrootable), and if it turns out to be bad I can just go back to an older RUU?
Basically, will using the 3.18 OTA/RUU mess anything up if I'm S-OFF?
Click to expand...
Click to collapse
Yes, I did find Viper and clean rom both ran much better than they did previously.
I'm sorry, I don't know about the 3.18 OTA... Hopefully someone else here can shed more light?
Theoretically, Since you're S-OFF, you should be able to update just fine. I haven't seen anyone actually do it yet though. I would test if I could.
I didn't relock I just ruu'd and after the process was done I just pushed twrp to my phone in fastboot and flashed viper. Only took a few mins top
Sent from my Elemental Venomized S-off HTC One XL
If I decide to update to a complete 3.18 base, is it better to use a 3.18 RUU or OTA? And if I use the OTA, how exactly do I 'flash' it (it's a ZIP file). Do I just put it on the top level of my internal storage, and boot into recovery, and select 'update' or whatever?
Hydromea said:
If I decide to update to a complete 3.18 base, is it better to use a 3.18 RUU or OTA? And if I use the OTA, how exactly do I 'flash' it (it's a ZIP file). Do I just put it on the top level of my internal storage, and boot into recovery, and select 'update' or whatever?
Click to expand...
Click to collapse
I used the ruu for 3.18 and haven't regretted it yet. My battery life has gotten much better.
Sent from my Elemental Venomized S-off HTC One XL
OTA just downloads through the phone. IE: Go to settings about phone, check for updates and it updates. You don't have to do anything else, it prompts you and updates for you.
If there was already a 3.18 RUU that would be the fastest way. Telus is slow with releasing RUU's so I had to use ICS myself. Neither way should give you trouble.
Here's to hoping my phone doesn't brick. Running the RUU as we speak (bootloader unlocked, s-off, super-cid)...
Well it worked. Twrp 2.2.2.0 doesn't though. Ugh, 2.3x is so ugly.
Sent from my HTC One X
ECEXCURSION said:
Well it worked. Twrp 2.2.2.0 doesn't though. Ugh, 2.3x is so ugly.
Sent from my HTC One X
Click to expand...
Click to collapse
Did you use the 3.18 RUU?
ECEXCURSION said:
Well it worked. Twrp 2.2.2.0 doesn't though. Ugh, 2.3x is so ugly.
Sent from my HTC One X
Click to expand...
Click to collapse
If you're hellbent on TWRP 2.2.2.0, downgrade the touchscreen firmware.
Hydromea said:
Did you use the 3.18 RUU?
Click to expand...
Click to collapse
Yeah I did. Maybe I'll look into downgrading the touchscreen firmware.
Sent from my HTC One X
If I'm S-OFF and use the 3.18 RUU, in order to use AOSP-based 4.2.2 ROMs, will I have to downgrade my touchscreen firmware?
Hydromea said:
If I'm S-OFF and use the 3.18 RUU, in order to use AOSP-based 4.2.2 ROMs, will I have to downgrade my touchscreen firmware?
Click to expand...
Click to collapse
yes you will here is how
http://forum.xda-developers.com/showthread.php?t=2159863
If I use the 3.18 RUU, how will I obtain root afterwards?
I'm already S-OFF and bootloader unlocked BTW.
And since I'm S-OFF, can I easily revert back to an older RUU without any extra steps?
Hydromea said:
If I use the 3.18 RUU, how will I obtain root afterwards?
I'm already S-OFF and bootloader unlocked BTW.
And since I'm S-OFF, can I easily revert back to an older RUU without any extra steps?
Click to expand...
Click to collapse
after ruu just fastboot flash a recovery transfer a rooted rom to your phone and flash in recovery
and with s-off you can run any ruu dont even need to relock bootloader
jerrycoffman45 said:
after ruu just fastboot flash a recovery transfer a rooted rom to your phone and flash in recovery
and with s-off you can run any ruu dont even need to relock bootloader
Click to expand...
Click to collapse
What he said lol
Sent from my Elemental Venomized S-off HTC One XL
this is all great info i would like to thank all of you
does this go for the rogers model as well?
babarnard said:
this is all great info i would like to thank all of you
does this go for the rogers model as well?
Click to expand...
Click to collapse
Yes.
Just an update. I successfully ruu'd to 3.18, downgraded hboot to 1.09, downgraded the touchscreen firmware, installed twrp 2.2.2.0 and all is well.
I'm sort of back where I started but maybe something good has come of it.
Sent from my HTC One X
Bonjour everyone, here's a little guide on how to unbrand your phone in order to get the OTA updates notifications directly and be able to install them.
If you want to get S-OFF one day on your One SV, read this first. You need to change CID to SuperCID to do so, and it's not possible (for the moment) if you upgrade to JB
Basically this works as long as your phone model is sold unbranded somewhere in the world and that the people having such a phone got an OTA update.
For now, ther's no way to change CID if you're running JB and are S-ON. That means that this only work for One SV's running ICS who want to get the OTA updates.
As far as I know, it works on K2_U and K2_UL, since they both got an OTA update to JB.
The trick is simple, I didn't invent it and haven't been able to find its original founder, but thanks a lot to her or him !
I'm basically just a messenger here since I only tried out some stuff that worked with other phones, so thanks a lot to bkcokota, old.splatterhand and jmztaylor
Don't try it if you're worried, bricks happen, you'd be the only one responsible !
Here we go :
1. First you need to root your phone, here's how.
2. Change you CID using the same method than for the One S.
Personnaly, I changed it to "HTC__203", which is the CID unbranded HTC phones have in France (HTC-FRA).
For example, "HTC__001" is HTC-WWE, which stands for World Wide English.
You can change it to whatever CID you like : choose it well. I can only recommend to use HTC__203 since it's the only one I tried and that it worked, but do as you please !
3. Flash stock recovery back. You'll find it here or here. Flash it like you flashed CWM recovery (into fastboot, using fastboot flash recovery xxxxxx.img).
4. Relock your bootloader. It's possible that it's not necessary, but it can't hurt ("fastboot oem lock", when in fastboot usb)
5. Run a RUU that matches you unbranded CID to get an "unbranded" rom.
You'll find them here, for example. The "RUU_K2_UL_ICS_40_HTC_Europe_1.17.401.5_R....exe" one will work with HTC__203 and HTC__001 CIDs.
6. Go ask your phone if he can find any updates
WARNING : for the moment there's no way to change CID if you upgrade to JB since the newer HBOOT (v2.00) don't let you do it. That means that for now you won't be able to S-OFF if you upgrate to JB using this method. For now...
Nice one!
Only thing i would add for people to know:
if somebody want to get S-Off, they should change the CID to SuperCID 11111111 (or if you want 22222222,...).
old.splatterhand said:
Nice one!
Only thing i would add for people to know:
if somebody want to get S-Off, they should change the CID to SuperCID 11111111 (or if you want 22222222,...).
Click to expand...
Click to collapse
Done, sir.
It was only said at the bottom of the message at first, but now I put it at the beginning as well.
There's one thing that I'm trying to get though : according to a lot of people and forums, you don't get OTA when you have SuperCID... but some poeple say they do.
It probably changes depending on the type of HTC phone, but also depending on the OTA (some got the first ones, but not the latest...).
I got the ota notification with SuperCID, i think it depends on more things.
But there i'm not far enough into it.
I have had no success at all. My story:
Updated a branded phone to JB, rooted. Then I did a moonshine S-off and changed CID to HTC__001 (even tried 11111111).
I have downloaded a ICS RUU (couldn't find stock K2_UL so I thought that I would download ICS first and then do OTA to JB) but I am getting error 158. I have checked md5 sum and it matches (http://androidfiles.org/ruu/getdown...0.14_2_10.49.40.11L_release_301902_signed.exe). Any ideas?
If you're on jb and hboot 2.00, that's normal... and written in the first post.
There is information that it is impossible to change CID while on JB and with 2.0 hboot, but I guess that I have had success in changing to superCID (at least this is what I can read in bootloader and using fastboot oem readcid command.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Is there any chance to make this for the k2cl ( boost mobile ) version?
idr666 said:
Is there any chance to make this for the k2cl ( boost mobile ) version?
Click to expand...
Click to collapse
Can you be more specific, what you mean with "this".
old.splatterhand said:
Can you be more specific, what you mean with "this".
Click to expand...
Click to collapse
Sorry, I was wondering if there is a way to update this phone ( the k2cl ) to JB
idr666 said:
Sorry, I was wondering if there is a way to update this phone ( the k2cl ) to JB
Click to expand...
Click to collapse
Boost has no official jb, but i know that there is work for an custom jb rom for boost.
Oh, thank you for the info. Is there any link about this work in progress?
idr666 said:
Oh, thank you for the info. Is there any link about this work in progress?
Click to expand...
Click to collapse
Look here
szympro said:
There is information that it is impossible to change CID while on JB and with 2.0 hboot, but I guess that I have had success in changing to superCID (at least this is what I can read in bootloader and using fastboot oem readcid command.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Click to expand...
Click to collapse
old.splatterhand, you seem to know this and that about One SV. No chance for older RUU, right? I can't seem to find a clean WWE JB OTA update. I just want a clean, stock, not modified ROM from HTC and I thought RUU is the only way to go :crying: Any advices?
szympro said:
There is information that it is impossible to change CID while on JB and with 2.0 hboot,...
Click to expand...
Click to collapse
This was before moonshine was available. With S-Off i think it should be possible.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Click to expand...
Click to collapse
I think so.
szympro said:
old.splatterhand, you seem to know this and that about One SV. No chance for older RUU, right? I can't seem to find a clean WWE JB OTA update. I just want a clean, stock, not modified ROM from HTC and I thought RUU is the only way to go :crying: Any advices?
Click to expand...
Click to collapse
To get it a bit clearer.
At this point i'm not very up to date, thats why i didn't answer til now.
I think (but i'm not sure) you can flash the ruu, if you are on hboot 1.0.
And as you are S-Off you should be able to downgrade hboot. But this is a very risky point, you can easily brick your device. Here is, how you have to do:
rollon76 said:
To change hboot you will need a PL80IMG.zip on sdcard with android-info.txt and hboot.img inside it.
reboot to bootloader and flash.
Click to expand...
Click to collapse
The thing what makes it difficult, is to get the hboot.img (its inside ics ruu), cause the htc ruu's encrypted and i only have heard about tools for linux which can decrypt it.
Thanks to your reply I did some research and I have managed to do what I wanted. I have downgraded hboot first (by extracting and encrypting ICS RUU using linux), then I could run RUU and now I am stock ICS with S-off and superCID
Should I post some files from RUU? 1.0 hboot or stock recovery? You guys need something?
Thanks for your helping hand old.splatterhand!
szympro said:
Thanks to your reply I did some research and I have managed to do what I wanted. I have downgraded hboot first (by extracting and encrypting ICS RUU using linux), then I could run RUU and now I am stock ICS with S-off and superCID
Should I post some files from RUU? 1.0 hboot or stock recovery? You guys need something?
Thanks for your helping hand old.splatterhand!
Click to expand...
Click to collapse
Glad, it worked for you.
Yes, of course, everything is appreciated! You can use this thread, please post ruu name too. You can look at my posts there. Hboot, boot.img, recovery, radio, would be fine.
HERE have other ruu
https://www.dropbox.com/sh/1t2zswod7tc97az/5hbzEgTv80
szympro said:
I have downgraded hboot first (by extracting and encrypting ICS RUU using linux)
Click to expand...
Click to collapse
Wow, that's cool !
Did you use rollon's method and flashed PL80IMG.zip in bootloader mode ?
If yes, which android-info.txt did you use ?
If not, how did you do it ?
szympro said:
then I could run RUU and now I am stock ICS with S-off and superCID
Click to expand...
Click to collapse
Even cooler for you.
Did you get the ota update notification for JB then ?
Did you manage to apply it ?
Thanks and congratulations !
Hi everyone.
Just a quick message to confirm that rollon's method works.
To downgrade you need to be S-OFF, extract and decrypt (with ruuveal, using linux or a linux virtualbox runned in windows) hboot and androidinfo from ICS RUU, put them in a zip named PL80IMG.zip, put it on your sd card and boot into bootloader. Then you can run the ICS RUU normally and you'll be back to stock ICS, with a "*** LOCKED ***" bootloader (not relocked !), will be able to go back to S-ON using "fastboot oem writesecureflag 3" (thanks to JMZ)...
You'll then have a locked S-ON out of box phone running 100% stock ICS with original boot, recovery and all that... who'll get the 2 JB OTA's...
In case anyone's interested
Hi, I have a HTC ONE XL for AT&T with S-OFF and unlocked bootloader. I have the nocturnal ROM based on ICS. Also HBOOT 1.01.0000.
I want to install a rom based on JB (This particular CleanROM 6.5 - ★ | Jellybean 4.1.1! |).
My question is with this hboot, can i flash a jb rom from ICS? Because I'm not sure if flash from recovery the zip of this rom bricked me.
It won't brick you. I'm not sure if you'll experience issues using such an old firmware with a ROM based on the latest softwate
Sent from my One X using xda app-developers app
Thanks. Is there any way to update the software?
Rafanjani said:
Thanks. Is there any way to update the software?
Click to expand...
Click to collapse
Yes install the Ruu, then push twrp, then install CR. This will give you the latest firmware. CR by itself does not so it, and some gave experienced random reboots with older wifi firmware. Just be aware that a small subset of HOXL phones do not work well with Maps/nav under JB
between ynelsol
GroovyGeek said:
Yes install the Ruu, then push twrp, then install CR. This will give you the latest firmware. CR by itself does not so it, and some gave experienced random reboots with older wifi firmware. Just be aware that a small subset of HOXL phones do not work well with Maps/nav under JB
Click to expand...
Click to collapse
thanks for reply! I did brick my phone when i try to install an official ruu 2 months ago, but i did fix this ($$$$). The problem is that I can not install because I have CID 111111 and CR root, bootloader unlocked etc
With s-off you won't brick running an ruu. Though my phone will no longer ruu properly but that's another story. I may post a thread about it in case others experience it so they know how to recover.
Sent from my HTC One X using xda app-developers app
exad said:
Though my phone will no longer ruu properly but that's another story. I may post a thread about it in case others experience it so they know how to recover.
Click to expand...
Click to collapse
I'm curious about this. What happened?
Sent from my HTC One
ECEXCURSION said:
I'm curious about this. What happened?
Sent from my HTC One
Click to expand...
Click to collapse
Something went wrong while RUUing and my hboot partition cannot be written over without clearing the cache first. So the RUU will get to the end and then fail. Everything flashed except the hboot. It's kind of funny because it looks like a brick when it happens but it remains in RUU mode so I can just fastboot flash the hboot seperately after and everything works but RUUs will no longer complete successfully Always half bricks.
How did it happen? Well I think it's because I was RUUing in a VM as I was running linux exclusively at the time. But during RUU the phone looses connection and I have to manually reconnect to my phone and I didn't realize so it interrupted the RUU. I'm just lucky I didn't end up with a full brick! ^_^
exad said:
Something went wrong while RUUing and my hboot partition cannot be written over without clearing the cache first. So the RUU will get to the end and then fail. Everything flashed except the hboot. It's kind of funny because it looks like a brick when it happens but it remains in RUU mode so I can just fastboot flash the hboot seperately after and everything works but RUUs will no longer complete successfully Always half bricks.
How did it happen? Well I think it's because I was RUUing in a VM as I was running linux exclusively at the time. But during RUU the phone looses connection and I have to manually reconnect to my phone and I didn't realize so it interrupted the RUU. I'm just lucky I didn't end up with a full brick! ^_^
Click to expand...
Click to collapse
how i can flash hboot using fastboot? I wish to have jb
Rafanjani said:
how i can flash hboot using fastboot? I wish to have jb
Click to expand...
Click to collapse
flashing hboot with fastboot won't give you JB......
Is your phone S-ON or S-OFF?
SuperCID? Yes or no?
Bootloader locked or unlocked?
exad said:
flashing hboot with fastboot won't give you JB......
Is your phone S-ON or S-OFF?
SuperCID? Yes or no?
Bootloader locked or unlocked?
Click to expand...
Click to collapse
I know! but it's the first step to upgrade to jb
Rafanjani said:
I know! but it's the first step to upgrade to jb
Click to expand...
Click to collapse
No it isn't
hey friends i would like to know how to update hboot to latest on XL
since my friend is having S-off and Super CID device
he would like to update his Hboot and try some custom roms..
so please tell and share link to latest Hboot
imranaryan said:
hey friends i would like to know how to update hboot to latest on XL
since my friend is having S-off and Super CID device
he would like to update his Hboot and try some custom roms..
so please tell and share link to latest Hboot
Click to expand...
Click to collapse
I'd your s-off just run latest ruu. No need to relock bootloader either. After ruu flash recovery via fastboot. And your set
Sent from my HTC One XL using xda premium
31ken31 said:
I'd your s-off just run latest ruu. No need to relock bootloader either. After ruu flash recovery via fastboot. And your set
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
wats the latest RRU for HTC ONE XL .. and link to stock recoveries please
You don't need to update hboot to install custom ROMs.
RUU is recommended for some ROMs, as it seems to help with random reboots on some ROMs. But RUU is not strictly required.
Everything you will likely ask for is here: http://forum.xda-developers.com/showthread.php?t=1671237
Device will return to stock recovery when you RUU. But now sure why you are asking for that.
redpoint73 said:
You don't need to update hboot to install custom ROMs.
RUU is recommended for some ROMs, as it seems to help with random reboots on some ROMs. But RUU is not strictly required.
Everything you will likely ask for is here: http://forum.xda-developers.com/showthread.php?t=1671237
Device will return to stock recovery when you RUU. But now sure why you are asking for that.
Click to expand...
Click to collapse
where can i find only latest HBOOT package..
imranaryan said:
where can i find only latest HBOOT package..
Click to expand...
Click to collapse
Here:
http://forum.xda-developers.com/showthread.php?t=2156686
imranaryan said:
where can i find only latest HBOOT package..
Click to expand...
Click to collapse
You are not getting my main point. There is no reason you need to update hboot. Why do you think you need to?
redpoint73 said:
You are not getting my main point. There is no reason you need to update hboot. Why do you think you need to?
Click to expand...
Click to collapse
Agree. Follow advice above to flash latest RUU (here: http://forum.xda-developers.com/showthread.php?p=37227608 ), and re-flash recovery . You will get a newer hboot along with that, but other elements of the RUU are more beneficial to some of the newer ROMs - hboot won't give you anything by itself.Make sure you are S-OFF before RUU or you may brick.
Hello.
I have an htc one xl (evita) which will not boot certain roms. I can boot some roms such as miui v5 and magiRom but I can not figure out why it will not boot roms such as CyanogenMod, ChameleonOS or TeamBaked BB9 as examples. These that will not boot will only boot loop and I'm going froot loop.
I am S-off, HBoot 1.09. Using TWRPv2.3.1.0.
I have tried TWRPv2.5, Hboot >1.09 and flashing boot.bin separately.
I have also tried some suggestions from these posts with no success so far ..
http://www.smartphonejam.com/2013/0...-on-HTC-Screen-Logo-Bootloop-after-Flash.html
http://forum.xda-developers.com/showthread.php?t=2159863
Any suggestions on how to boot other roms?
Thanks in advance for your help.
ps. I'm on mac - so if you have any suggestions and tools, please keep the mac in mind.
andason said:
Hello.
I have an htc one xl (evita) which will not boot certain roms. I can boot some roms such as miui v5 and magiRom but I can not figure out why it will not boot roms such as CyanogenMod, ChameleonOS or TeamBaked BB9 as examples. These that will not boot will only boot loop and I'm going froot loop.
I am S-off, HBoot 1.09. Using TWRPv2.3.1.0.
I have tried TWRPv2.5, Hboot >1.09 and flashing boot.bin separately.
I have also tried some suggestions from these posts with no success so far ..
http://www.smartphonejam.com/2013/0...-on-HTC-Screen-Logo-Bootloop-after-Flash.html
http://forum.xda-developers.com/showthread.php?t=2159863
Any suggestions on how to boot other roms?
Thanks in advance for your help.
ps. I'm on mac - so if you have any suggestions and tools, please keep the mac in mind.
Click to expand...
Click to collapse
3.18 ruu.
Sent from my One X using xda premium
jacobas92 said:
3.18 ruu.
Sent from my One X using xda premium
Click to expand...
Click to collapse
man i've looked at a lot of stuff regarding how to get to 3.18 but i keep finding a bunch of conflicting info that my brain is busted. If anyone can reply to some answers with my further info I would appreciate it...
My CID is 11111111
I'm S-off
hboot 1.09
What steps do I need to take to get to 3.18?
I can't seem to find a stock evita recovery image. My understanding is I need to relock boot loader, install stock recovery, upgrade to 3.18 and then restart the process of unlocking. Is this correct? Is the stock recovery located in an original at&t update?
andason said:
man i've looked at a lot of stuff regarding how to get to 3.18 but i keep finding a bunch of conflicting info that my brain is busted. If anyone can reply to some answers with my further info I would appreciate it...
My CID is 11111111
I'm S-off
hboot 1.09
What steps do I need to take to get to 3.18?
I can't seem to find a stock evita recovery image. My understanding is I need to relock boot loader, install stock recovery, upgrade to 3.18 and then restart the process of unlocking. Is this correct? Is the stock recovery located in an original at&t update?
Click to expand...
Click to collapse
As long as you're s-off, just go ahead and run this http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/ I know you wrote s-off, I'm just being double sure because if you're s-on it'll brick you. S-off you'll be fine. You won't have to relock or anything like that. With s-off you can just do whatever you want :good:
RollTribe said:
As long as you're s-off, just go ahead and run this http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/ I know you wrote s-off, I'm just being double sure because if you're s-on it'll brick you. S-off you'll be fine. You won't have to relock or anything like that. With s-off you can just do whatever you want :good:
Click to expand...
Click to collapse
Thanks. I'll find me a windows pc tomorrow and go for it. After I flash this in windows, do i then just flash any custom rom I want to go to which has the 3.4 kernel and will I be limited only to those now?
andason said:
Thanks. I'll find me a windows pc tomorrow and go for it. After I flash this in windows, do i then just flash any custom rom I want to go to which has the 3.4 kernel and will I be limited only to those now?
Click to expand...
Click to collapse
Yeah any 3.4 ROM, but you can also use non-3.4 if you so choose.
RollTribe said:
Yeah any 3.4 ROM, but you can also use non-3.4 if you so choose.
Click to expand...
Click to collapse
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
andason said:
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
Click to expand...
Click to collapse
Yeah, man, Wine doesn't work, I tried back when I used Mac for my Android needs. Everything is SO much easier with a windows PC
after flashing the 3.18 ruu, i can still flash any custom roms i want? aosp, sense base. what about ics version roms?
claudiuslu2011 said:
after flashing the 3.18 ruu, i can still flash any custom roms i want? aosp, sense base. what about ics version roms?
Click to expand...
Click to collapse
Yup all Roms
is there any advantage on the 3.18ruu?
Yeah, you need it to run AOSP 3.4 kernel roms
andason said:
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
Click to expand...
Click to collapse
Thanks. Everything seems to work fine now.
A couple of things to note for others who make look at this thread - After flashing the rom in your link: http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/
1. Hboot will be at 2.14 - So if you wish, downgrade back to 1.09, otherwise you will need to flash the boot.img and then the rom when trying new roms.
2. The after market recovery (will now be oem recovery) will be gone so be sure to reinstall your preferred recovery (TWRP or CW)
3. The touchscreen may not respond in some roms, so you may have to downgrade your touchscreen panels firmware http://forum.xda-developers.com/showthread.php?t=2159863
exad said:
You only need to downgrade touchscreen firmware if:
You're on 2.14 hboot + You are flashing an AOSP ROM not yet on 3.4 Kernel.
Click to expand...
Click to collapse
Thanks again for the help.
andason said:
Thanks. Everything seems to work fine now.
A couple of things to note for others who make look at this thread - After flashing the rom in your link:
1. Hboot will be at 2.14 - So if you wish, downgrade back to 1.09, otherwise you will need to flash the boot.img and then the rom when trying new roms.
2. The after market recovery (will now be oem recovery) will be gone so be sure to reinstall your preferred recovery (TWRP or CW)
3. The touchscreen may not respond in some roms, so you may have to downgrade your touchscreen panels firmware http://forum.xda-developers.com/showthread.php?t=2159863
Thanks again for the help.
Click to expand...
Click to collapse
You actually don't need to downgrade your hboot, if you're s-off you don't need to manually flash boot.img no matter what your hboot version is.
Sent from my Evita
odd that rom would not boot with 2.14..but with 1.09 no problems?
andason said:
odd that rom would not boot with 2.14..but with 1.09 no problems?
Click to expand...
Click to collapse
There was probably some other factor causing the issue. I boot all roms with 2.14 no problem.
andason said:
odd that rom would not boot with 2.14..but with 1.09 no problems?
Click to expand...
Click to collapse
Which ROM? After s-off?
Sent from my Evita
timmaaa said:
You actually don't need to downgrade your hboot, if you're s-off you don't need to manually flash boot.img no matter what your hboot version is.
Sent from my Evita
Click to expand...
Click to collapse
do i need to downgrade my touch firmware?
claudiuslu2011 said:
do i need to downgrade my touch firmware?
Click to expand...
Click to collapse
You only need to downgrade touchscreen firmware if:
You're on 2.14 hboot + You are flashing an AOSP ROM not yet on 3.4 Kernel.
timmaaa said:
Which ROM? After s-off?
Sent from my Evita
Click to expand...
Click to collapse
It may be I am mistaken. I thought it was baked but i was also trying a rom I was trying to port. During the time i was flashing from 1.09 to 2.14 and also seen that baked required 2.14. So with all that going on i was just trying boot.img and then the rom to ensure no errors.